• | NMEA GGA The NMEA GGA datagram transfers time-, position- and fix-related data from a global positioning system (GPS).
|
• | NMEA GLL The NMEA GLL datagram transfers the latitude and longitude of vessel position, the time of the position fix and the current
status from a global positioning system (GPS).
|
• | GGK This third party datagram format contains the vessel’s current position with the assigned coordinated universal time (UTC)
of position, as well as a selection of position quality factors.
|
• | NMEA VTG The NMEA VTG datagram contains the actual course and speed relative to the ground.
|
• | NMEA HDG The NMEA HDG datagram provides heading from a magnetic sensor. If this reading is corrected for deviation, it produces the magnetic heading. If it is offset by variation, it provides the true heading.
|
• | NMEA HDM The NMEA HDM datagram provides vessel heading in degrees magnetic. The datagram is no longer recommended for use in new designs. It is often replaced by the NMEA HDG telegram.
|
• | NMEA HDT The NMEA HDT datagram provides the true vessel heading. The information is normally provided by a course gyro.
|
• | EM Attitude 3000 The Kongsberg EM Attitude 3000 is a proprietary datagram format created by Kongsberg Mesotech for use with digital motion sensors. It holds roll, pitch, heave and heading information. The datagram contains a 10-byte message.
|
• | Octans STD1 This is a third-party proprietary datagram format for heading, speed, and motion. It was created by iXSea (http://www.ixblue.com) for use with their Octans gyrocompass.
|
• | Teledyne TSS1 Teledyne TSS1 is a proprietary datagram format for heave, roll and pitch compensation. When you select this protocol, the number of sensor variables is fixed, and there is no token associated with it.
|
• | EM Attitude 3000 The Kongsberg EM Attitude 3000 is a proprietary datagram format created by Kongsberg Mesotech for use with digital motion sensors. It holds roll, pitch, heave and heading information. The datagram contains a 10-byte message.
|
• | Octans STD1 This is a third-party proprietary datagram format for heading, speed, and motion. It was created by iXSea (http://www.ixblue.com) for use with their Octans gyrocompass.
|
• | Valeport This is a third-party proprietary datagram format created by Valeport Ltd. for use with their sound velocity sensors. The file format is ASCII. There are three formats: standard format (millimetres per second), alternative format #2 (metres per second with two decimal
places), and alternative format #3 (metres per second with three decimal places). For more information, see http://www.valeport.co.uk.
|
• | NMEA DBT The NMEA DBT datagram provides the current depth under the transducer. In new designs, this datagram format is frequently used to replace the DBK and DBS formats.
|
• | NMEA DPT The NMEA DPT datagram provides the water depth relative to the transducer, and the offset of the measuring transducer.
|
• | .mmb This is raw element data, not beamformed, in a 16-bit fixed-point complex format. This format allows great flexibility in how the data is processed and allows you to do your own beamforming or profile-point
extraction. The data body size is determined by the number of elements and the number of samples.
|
• | .imb This format consists of beamformed data.
You can choose between a 32-bit floating point complex or 8-bit integer magnitude format. Select the 8-bit format only if you are interested in imaging pixel data and want a reduced data file size. The 8-bit format takes up a quarter of the 32-bit format's size.
Data body size is determined by the number of beams and samples. Different modes may form a different number of beams. Therefore, data body size may change depending upon the mode.
|
• | .ALL This is the proprietary Kongsberg EM series datagram format. The M3 software can output this data format to be compatible with third-party post-processing software.
|
• | PRI Sync PRI Sync (set with Trigger Mode on the Sonar Setup page of the System Configuration dialog box) provides ping synchronization with another Sonar Head or other acoustic source that supports synchronization (for example, EK60, Sidescan, DVL, etc.). PRI Sync is a level-sensitive method of synchronization. When the sync is held high, the sonar will not transmit. The PRI Sync INPUT must be held low for 25μs in order to trigger the Sonar Head. The Sonar Head will transmit a 100μs sync OUTPUT pulse when configured as Master on the Sonar Setup page. The sync OUTPUT is generated each time the Sonar Head transmits.
|
• | Host Time Sync Mode Host mode synchronizes the Sonar Head time with the computer time. This mode is critical for Bathymetry applications. Host mode only works if the computer is connected to an accurate time source, such as a GPS or network time server. When connecting to the Sonar Head, it takes two minutes to synchronize the time to within five milliseconds.
|
• | 1PPS Time Sync Mode 1PPS is a 0 to 5 VDC pulse, with a 50% duty cycle. The Sonar Head time can be synchronized to external 1PPS pulses.
The time is synchronized to the rising edge of the 1PPS pulses. When the rising edge of a 1PPS pulse is detected then the ns, us and ms counters are set to zero. The second counter is set to zero if the ms counter is < 500 and increased by 1 if the ms counter is >= 500.
1PPS synchronization requires ZDA input over UDP to the Sonar Head (not to the M3 software) on UDP port 31100 at 1Hz.
The 1PPS signal must be sent to the Sonar Head using the 1PPS input on one of the following cables.
The Sonar Head must be upgraded to the latest firmware version (version 1.5 or later).
|
• | Computer Time Sync If ZDA is configured, the M3 software will use the time in the ZDA message to synchronize the computer clock automatically in the background. However,
you may need to run the M3 software as an administrator (right-click on the icon and select Run as administrator) or Windows may not allow the software to change the system clock. Computer time sync can be useful when data is being logged on more than one computer and synchronized timing is required. This method is not recommended for Bathymetry applications as it is not accurate enough.
Note
Computer time sync requires both GGA and ZDA input.
|