Driver that decodes bathymetry data, seabed imagery (for raw storage) and water column data from the latest models Kongsberg multibeam echosounders equipped with firmware that supports the new "KMall" protocol.
For raw data processing the driver can optionally store raw bathymetry and seabed image records in the Qinsy database.
Supported systems (that QPS is aware of):
- Kongsberg is working on releasing the format for other systems
|Driver||Kongsberg KMALL||Interface Type||UDP||Driver Class Type|
|UTC Driver||Yes||Input / Output||Input||Executable||DrvQpsFreeBase.exe|
Driver decodes the following datagrams:
Raw range and depth, #MRZ
Bathymetry and imagery data
Water column #MWC
Water column data
The #MRZ message contains both 'raw' data (beam angle and travel time) and geo-referenced footprints (X,Y,Z). Of these two, only the raw data is decoded by the driver.
Since Qinsy 9.3.0 the driver decodes a quality indicator for each beam and supports filtering footprints on quality.
This quality indicator is based on the 'qualityFactor' field in the KMALL data. The content of this field is described by Kongsberg as
This value is multiplied by 128 and capped on 255 in order to translate it from a 'real number' to a byte value.
The following items are licensed by Kongsberg. The data is not sent from the PU if the license is not there. Note that Kongsberg supports soft licenses.
- Water column logging
- Water column display
- Extra detections
Extra detections are supported by Qinsy when using the KMALL format.
When using the ALL format (Kongsberg EM2040-EM710-EM712-EM302-EM122 - 20) the detections are stored as normal footprints.
Kongsberg also has an option to classify the extra detections. This is currently not supported by QInsy.
The multibeam system can be controlled from Kongsberg's K-controller utility.
This utility is also used to configure IP addresses and ports used.
Please note that due to the communication technology used by Kongsberg (UDP multicast), you will need to select an IP address from the multicast range (220.127.116.11 to 18.104.22.168).
Phase Center offsets (PCO) used by Qinsy
The x,y,z positions for the 3 TX line arrays are relative to the center of the sonar head face.
EM2040P Installation Offsets
For the EM 2040P, the TX and RX arrays are integrated into a common sonar head. The transducer arrays are not placed at the center of the sonar head.
For most EM echosounders separate x,y,z installation parameters are given for the RX and the TX arrays.
For EM 2040P the installation parameters entered by the operator refer to a reference point on the face of the sonar head. This point is not marked on the sonar head.
The reference point used is the intersection between two diagonal lines drawn between the bumpers on the sonar head face.
Acknowledgement: Text and Figure by Kongsberg EM Series Multibeam echo sounder EM datagram formats, 850-160692/V July 2016 © Kongsberg Maritime AS
Preferably a direct cross-over network cable should be used to transfer the data. This will minimize the chances of any dropped packets.
In case you are experiencing connection problems, i.e. data not coming into Qinsy please have a look at the following tip.
Connection issue between Qinsy 9.2.0 and K-Controller
This was supposed to have been fixed and improved in Qinsy 9.2.0 but it turned out this is not yet working correctly.
The solution was that in Qinsy 9.2.0 it would check all the network cards for the multicase port, but that does not yet work properly.
A component has been made available under the Qinsy 9.2.0 - Known Issues to resolve this.
Please contact QPS Support in case you require assistance.
Connection loss between K-Controller and Qinsy 9.1.1
Currently Qinsy will only check the network adapter with the highest priority because the communication technology used is UDP multicast.
It is advised to change network priorities when there are multiple network adapters available to ensure that the network adapter connected to the PU has the highest priority.
To change priority of a network adapter use the following steps:
- Go to the Network Connections view
- Go to the Properties of the network adapter you want to prioritize
- Open up the Properties of Internet Protocol Version 4 (TCP/IPv4)
- Click the Advanced button
- Uncheck the Automatic metric and assign a priority value for the adapter
A lower Interface metric number means higher priority.
A 'Balanced' (default) power plan on the PC can cause package dropouts from the second head.
This can be solved by changing the power plan on the PC from 'Balanced' to 'High Performance' when using a Windows 7 or Windows 10 pc.
Please note that the driver does not decode auxiliary sensors interfaced into the unit, such as position, motion, heading, etc.
These external sensors will have to be interfaced directly to Qinsy as well.
FAQ ON UPGRADING TO USE K-CONTROLLER AND KMALL FORMAT
Coming from an old setup (either using SIS as controller or using the EM Controller in Qinsy) the following needs to be considered:
- Changes in cabling: User can rewire the SV sensor to the processing unit directly.
- Entering geometry in the K-Controller: For a Qinsy setup it is not necessary to enter the full geometry. However, for Kongsberg support purposes it could be useful.
There is the option of logging in KMall format in the K-Controller, and Kongsberg prefers that when supporting with problems. Problem finding is made easier if the offsets are correct.
- How to use the K-Controller: Kongsberg has a reference manual available: 'K-Controller Installation and runtime controller for EM multibeam echo sounders'.
- It is no longer possible to use the EM-controller in Qinsy with the new format. It is not possible to change settings from Qinsy.
- Which Kongsberg multibeam models are supported: Beginning 2019 the EM 2040P is supported with EM2040C; EM2040 and EM712 expected later during the year.
- Qinsy databases will be larger in size. More data is being sent and stored when raw data logging is on.
Copy the IP address and port number settings from the 'Input Setup' page of the K-Controller:
Only single head systems are supported at this time.
Driver Specific Parameters
|Selected preset||Raw Bathymetry Storage||Raw Seabed Image Storage||Water Column Usage|
|FM Geocoder Toolbox (FMGT)|
|FM Midwater (FMMW)||
|FM Geocoder Toolbox (FMGT & FM Midwater (FMMW)||
Please use the Preset so the needed data packages are decoded.
|For the systems in this list you can now enter the reference point as node. See Knowledge Base document 'How-to Kongsberg Multibeam - Reference Position'|
|Raw Bathymetry Storage*||Disabled/Enabled||
When Enabled the Raw (original) Bathymetry packets (#MRC) and the Runtime Settings (#IOP) are stored in the database for usage in Fledermaus.
|Raw Seabed Image Storage**||Disabled/Enabled||When Enabled the Seabed Image (#MRC) is stored in the database for usage in Fledermaus.|
|Water Column Usage||Disabled/Enabled||When Enabled the Water column data is decoded by the Driver.
The STORAGE of the water column is activated with a setting in the Controller's Session Setup - Database page.
Multibeam Echosounder Parameters
The offset of the transmit and receive transducers are known by Qinsy.
Therefore you only need to enter the Reference node of the Head.
|Roll/Pitch/Heading offset||These are the offsets between the reference frame of the Motion sensor (which is usually aligned with the vessel frame) and the reference frame of the multibeam head.|
|Max. Beams per ping||This is the maximum amount of points we decode from the multibeam.|
|Sound Velocity||We use the sound velocity from the unit (measured near the head).|
|Echosounder Stabilization||Not applicable.|
Echosounder Accuracy Parameters
Multibeam Echosounder Corrections
Difference SIS5 vs K-controller
It is important that logging can only be started if SIS5 is running together with the K-controller:
- In SIS-5 you can remotely Start/Stop both Pinging and Logging.
In the K-Ctrl you can remotely Start/Stop Pinging only.
To record valid *.all and *.db files (without ping dropouts), we have to start and stop logging via Qinsy, however an output system is required .
Add the XML files in the table below to this location:
The xml-files above are only visible when logged in to the QPS website, not when viewing the Drivers Manual from the Qinsy Console.
Create an Output system:
Keep in mind that this has been tested on one pc which ran Qinsy and SIS simultaneously, with IP address 127.0.0.1
- This PC was running both the K-controller and SIS-5