Driver for decoding various telegrams from the Kongsberg-Simrad EA400/500/600 Echosounder family via a network connection.
The following telegrams are supported:
Simrad Ping Based Binary Depth.
The RAW0 and Q datagram are described in the sidescan chapter.
Note that the RAW0 message can also be used for the bottom classification algorithm.
Refer to Sidescan Systems chapter for more details.
|Driver||Network - Simrad EA-series||Interface Type||UDP + TCP-IP||Driver Class Type||Counted/Terminated|
|UTC Driver||Yes and No||Input / Output||Input||Executable||DrvSimradEAxxxSocket.exe|
The quality indicator of the depth observation will be the reflectivity value (in case of D#-message) which can be monitored with an Observation Physics Display or the Generic Display.
For time-tagging purposes the time from the message will be used if the driver "(With UTC)" has been chosen. If the other drivers (without the UTC) have been chosen, local computer time (or PPS if it is connected to QINSy) will be used for time-tagging.
Notice that for the depth message all other fields (like transducer number, athwart ships angle) are not used by QINSy.
The position from an SSG message is assumed to be the transducer position on WGS-84 datum. The Driver will calculate the target sample position with a range-bearing calculation from the decoded position and the decode heading (+/-90 degrees) and ground range. The target sample position is stored as part of the event information in the database. The comment of the event is filled with some information of the message type and the fields.
The position from a VGR message is assumed to be on WGS-84 datum and is stored directly as part of the event information. Comment of the event is filled with some information of the message type and the fields. The Channel Id is not used.
On the Simrad Echosounder you must also define, besides the Port number, the IP Address of the Remote Computer.
It is recommended to use a mask for the last field of the address.
VGR and SSG messages can be interfaced as events. First step in this process is to create an event definition file (XML) with the"I/O Driver Editor". While this program is normally used for creating INI files it can also be used to create eventing XML definitions (on the first page of the program set the type selection to "Event Output"). The event definition should contain at least one event. Note that the driver will always generate an event ID of 1, this is always the first event in the definition. Note that the event should contain the properties: Target Height, Target Length and Comment. These fields will be filled by the driver
After creating the Xml, add an "Eventing System" to the template in DbSetup. Next select driver "Simrad EA series (SSG & VGR)", with or without UTC, same as your depth and or sidescan driver. Select the previously created Xml with the event definition.
Make sure that the EA400 software is set up properly to output SSG and/or VGR messages over the network. If set up correctly every time the user clicks a target in either the Sidescan waterfall or the vertical echosounder profile an appropriate event is generated with the correct position.
Further, the (Network UDP) Port number must be the same as the Remote Computer Port number, where the Simrad Echosounder is sending the data onto the network.
During testing the following settings have been used for the network interface of the QINSy PC.