The different KMall drivers only differ in the network protocol they use to connect to the PU:

• UDP
  This is the preferred connection method for newer systems. Kongsberg refers to this as 'UDP multiport' as the data is divided over multiple ports.
  Make sure to set the IP address either to 255.255.255.255, or the IP of the machine running Qinsy.
  Make sure that the port configured in the K-Controller or SIS-5 is the same as the port set in Database Setup.
• UDP Multicast
  This is the original network protocol supported by Kongsberg. Older systems may only support this protocol. The PU uses UDP multicast to send data to multiple clients.
  Newer systems still support this method, but 'multiport UDP' is advised.
  Should you want to use the multicast driver with a newer system, make sure that the 'Enable UDP/TCP data multiport' setting in the K-Controller or SIS-5 is turned off.

• TCP
  TCP is a more robust protocol than UDP when it comes to connection loss, but because of this, there is a risk of connection problems when the data can't be read at the speed it comes in.
  From Kongsberg documentation:

  If SIS is unable to process data from the PU fast enough, the PU may start buffering datagrams.
  If the PC running SIS is used for other tasks than running SIS, e.g. transferring data to or from the PC, 
  the logging process may not be able to read data quickly enough and this may cause the PU to start buffering datagrams.
  Storage resources in the PU are very limited. When buffers are full, 
  the produced data will be discarded. The PU will send a message to inform the client when this happens.
  If SIS is used, this message will be shown in the SIS Message View.
  It is advised to refrain from using the PC to other CPU or disk intensive tasks when the echo sounder is pinging.

  For this reason we advise the use the 'UDP' driver over the use of the TCP driver.
  Should you want to use TCP anyway, then please make sure that if you also use SIS-5, that oth Qinsy and SIS-5 use TCP.
  From Kongsberg documentation:

  The TCP protocol can be enabled for all datagrams by setting “Use TCP for data from PU” to 1. 
  This is done in “Parameter Setup”. 
  Start from SIS’ tools menu or launch Setparameters.exe in the SIS5\bin folder.

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:

Estimated standard deviation as % of the detected depth. Quality Factor (QF) is calculated from IFREMER Quality Factor (IFQ): 
QF=Est(dz)/z=100*10^-IQF

This value is multiplied by 128 and capped on 255 in order to translate it from a 'real number' to a byte value. 

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.

• Please vote on FQI-559 - Getting issue details... STATUS .

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:

1. Go to the Network Connections view
2. Go to the Properties of the network adapter you want to prioritize
3. Open up the Properties of Internet Protocol Version 4 (TCP/IPv4)
4. Click the Advanced button
5. Uncheck the 'Automatic metric' and assign a priority value for the adapter
   
   A lower 'Interface metric' number means higher priority.

Packet loss

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.

Auxiliary data

Please note that the driver does not decode auxiliary sensors interfaced into the unit, such as position, motion, heading, etc. They are updated in a burst every second and we need updates as a continuous stream. 

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:

1. Changes in cabling: User can rewire the SV sensor to the processing unit directly.
2. 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.
3. How to use the K-Controller: Kongsberg has a reference manual available: 'K-Controller Installation and runtime controller for EM multibeam echo sounders'.
4. 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.
5. Which Kongsberg multibeam models are supported: Beginning 2019 the EM 2040P is supported with EM2040C; EM2040 and EM712 expected later during the year.
6. Qinsy databases will be larger in size. More data is being sent and stored when raw data logging is on.

Info

Please use the Preset so the needed data packages are decoded.

Info

The xml-files above are only visible when logged in to the QPS website, not when viewing the Drivers Manual from the Qinsy Console.

Info

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