Database Setup

Bathymetry / Snippets / Water Column

1. Add a new "Multibeam Echosounder" system to the object in your template database.
2. Select driver "Reson Seabat 7K (TCP/Network)" unless an Integrated Dual Head (IDH) system is used.
   In that case the port head should use the "Reson Seabat 7K (TCP/Network)" driver and
   the starboard head should use the "Reson Seabat 7K Head II (TCP/Network)" driver.
3. The port number should always be 7000, even if dual head systems are interfaced.
4. The IP address should be the IP address of the Seabat 7K System.
   For dual head systems different IP numbers are required unless an Integrated Dual Head (IDH) system is used.
   In that case the same IP address should be used for both heads. Examples of these are the IDH T50-R and T20-R systems.
   
   

• On the Seabat 7k Settings page we can select which raw packets are stored in the database:
  

  1. System
     Select the system you are using with this driver. 

  2. Packet storage for processing
     Here you can select which processing tool (if any) you want to use. When a specific processing tool is selected, the raw packets required by that tool are automatically stored in the database. 
     Only the processing tools which are supported by the device you are using are shown.
     Supported processing tools include:
     • FMGT - FlederMaus Geocoder Toolbox 
     • FMMW - FlederMaus Mid Water

     • XTF - Processing tools that can handle eXchange Triton Format import (CARIS / PDS / etc.)
       
       

       Grayed out

       When FMGT is selected the snippets will be grayed out because the format is automatically selected.

       This also applies to FMMW (water column).

  3. View data in Qinsy
     Here you can select if you want to view water column or snippet data in Qinsy. Some devices support multiple types of data (for instance 'normal' water column and compressed water column).
     If this is the case, you can select which one you want to view here.
     If you have selected a processing tool in the previous step, some options may be disabled as a specific data packet is required by that processing tool.
     It is not possible to record multiple packets of the same data type (e.g when both 'normal' water column and compressed water column data are supported by the unit, only one can be recorded).
  4. Snippet sample window size
     It is strongly advised to use the auto setting (0), then the Sonar will intelligently determine the optimal number of samples, balancing image quality and size.

  5. Synchronize recording with Qinsy
     If this checkbox is ticked, recording will be synchronized between Qinsy and the multibeam manufacturer's software.
     The file name of the S7k file will match the name of the database file used in Qinsy.

     Urgent

     Qinsy is only able to communicate that recording should start/stop plus the desired name of the recording file.

     Please make sure to manually set up all other recording parameters in the manufacturer's software (for example, which packets are included in the recording) prior to using this feature.

     Urgent

     Not all systems supported by this driver may support this feature.

     Norbit systems, for example, do not currently support external starting/stopping of recording.

  If these presets of settings do not suit your needs, there is a possibility to manually select which raw packets should be stored in the database.
  In order to do this, tick the 'Manually select recorded packets (advanced)' check box.
  The dialog will change to allow you to manually choose which packets are stored for bathymetry, water column and snippets:
  
  
  Only the record types supported by the chosen device will be available for selection.
  The following options may be available:

  Setting	Option (bold=default)	Description	FMGT	FMMW	XTF
  Raw Bathymetry Storage*	None	No Additional Raw packets are stored. The bathymetry is still decoded, but only the necessary information for Qinsy is decoded and stored in the recorded database file.
  	7000/7027 (New)	Stores the 7000 and 7027 in separate packets in the database for XTF Export usage and Fledermaus.
  	7006/7004/7000 (Old)	Stores the legacy 7006/7004 concatenated message for XTF Export usage and to support bringing data from older sonars into Qimera, FMGT, and FMMW. Note: This option does not affect the decoding for Qinsy, which will always use the 7027 message if it is available.
  Raw Snippet Storage	None	No Raw Snippet packets are stored.
  	7058 (Normalized)	Stores the 7058 message in the database. These can be viewed in Qinsy and can be processed in FMGT since version 7.7.0 .
  	7028 (New)	Stores 7028 message in the database. Both for XTF Export and Fledermaus.
  	7008/7004/7000 (Old)	Store the legacy 7008/7004 concatenated message for XTF Export.
  Water Column Usage	None	No Water column data is decoded and stored by the driver.
  	7042 (Compressed)	Stores the 7042 message in the database. These can be viewed in Qinsy and can be processed in FMMW since version 7.7.0 .
  	7018	When the 7018 Option is chosen the Water Column Data can be shown in Qinsy and stored in the database for further processing in Fledermaus.

  * see Format Description for more information!

  Warning: Storing Water Column Imagery

  Please note that because of the possible size of water column packets, an additional step is needed to actually store the raw packets in the database.
  Selecting a water column package in Database Setup will make it available for online viewing, but to actually store the raw packets in the database you will need to change the following setting in the Controller when online:

  Session Setup >> Storage >> Database >> 'Store MBE Water Column Imagery'
  

  Note: Roll/Pitch/Heave stabilization
  

  Roll/Pitch/Heave stabilization options can not be set in Database Setup.

  This is not necessary since the new 7027 Bathymetry message will report the actual steered beam angles (relative angles to the sonar Rx surface) to Qinsy.

  Qinsy can correct these relative angles by applying the reported MRU attitude angles. This results in absolute beam angles.

1. Enter the location of the Multibeam on the object (Vessel / ROV / AUV):
   
   
   

   Separate Transmit and Receiver transducer node offsets

   For optimum calculation results we strongly advise to enter separate Transmit and Receiver transducer node offsets. This is also true for circular array transducers like the Seabat 7101 uses.
   Refer to the operation manual for the details on the acoustic centers of the transducers.
   The only case where it is not advisable to use separate Transmit and Receiver transducer node offsets is when the 7027 bathymetry datagram is not available or desired and the older datagrams (7004/7006) are used.
   In this scenario, the driver should be set up to use a common acoustic center since the older datagrams report travel times and angles that are corrected by Reson for the separation between the transmitter and receiver.
   The node location of the common acoustic center should be that of the reference point specified in the Reson Operator's manual.

2. Enter the 'Max. beams per ping' applicable for the system.
   Since Qinsy 9.2.0, 1024 beams are supported
   
   
3. On the next page, Echosounder Accuracy Parameters, you can enter the parameter used for the TPU calculation.
   The results of the TPU calculations are used for IHO filtering, CUBE, etc.
   
   
4. On the Next page, Multibeam Echosounder Corrections, you could select sensors that would be used for adjustable alignments of the multibeam installation.
   Some vessels can rotate the multibeam for quay wall / jetty / breakwater inspections.
   
   
5. When finishing the setup wizard you will be prompted by a dialog that will offer you the option to install other systems that use the same driver executable:
   
   When you click on OK a new wizard will be started to set up the related Sidescan Sonar system.

Sidescan

If the backscatter data is to be visualized then:

1. If you cancelled the prompted additional driver wizard mentioned above you have two options:
   1. Right click with your mouse on the MBES system you have set up and select the related Sidescan Sonar driver:
      
      1. Driver type, Driver, Port number and IP are already selected for you and correspond with the related MBES driver
      2. In case you have a dual head system (i.e. SeaBat IDH T20/50-R) you need to:
         • Manually add a second Sidescan system to decode the sidescan data from the second head (see point b. below)
         • Select the associated Multibeam System (head) (see point 2 below).
           
           
   2. Manually add a Side Scan Sonar (SSS) system
      1. Select driver "Reson Seabat 7K (TCP/Network)",
      2. The port number should always be 7000, Enter the IP address of the Seabat 7K System. 
         
         
2. Select the same object as you have selected for the related MBES driver and select the associated MBES system:
   
   
   
3. Add a Port side and Starboard channel. (Read more about SSS systems in 'How-to Sidescan Sonar / MBES Backscatter' in the Qinsy Knowledge Base).
   
   (Associated system: T50 Stbd)

Time Synchronization System

1. When Qinsy software is running on the same PC as the Reson 7K software (e.g. for 8125 Hybrid system) and the latter is synchronizing the MSWindows clock, it is possible to select a special Time Synchronization driver that will use only the Windows system time and not synchronize it.
   Select driver "Third party synchronized Windows system time".
   
   
2. When Qinsy is running on a separate PC then don't use the driver mentioned above, but use a Time Synchronization driver that does synchronize the PC clock.
   1. When all time critical systems are interfaced with Time Synchronization and Time message (ZDA / UTC / RMC) one does not need a QPS-TTL Time Synchronization adapter.
   2. The use of the QPS-TTL Time Synchronization adapter will make identifying timing errors easier.

Read more about timing in Qinsy in the Drivers Manual and the Qinsy Knowledge Base:

• Drivers Manual:
  
  • Time Synchronization Drivers
    
    
• Knowledge Base:

  • How-to Timing in Qinsy

  • How-to Time Synchronization Display

Reson Remote IO (RRIO)

RRIO is a protocol used for distribution of raw data messages. The RRIO is used by the RESON SeaBat 7K, the RESON T-series and the Odom MB2 sonar system.
With the RRIO it is possible to receive the device data as interfaced to the RESON SeaBat or Odom MB2 RTA by Qinsy.
RRIO can be used as an alternative to the S7K driver for position, attitude and gyro.

There are a couple of drivers where there is the option to set another system which the data is acquired by.
For instance the NMEA Position and Heading driver shown below:

Interfacing Example

Pan and Tilt

Adding the driver

1. Add a new Rotation Angle Sensor system to the object in your template database.
2. Select driver Reson Seabat 7K (TCP Network) - Pan & Tilt
3. Fill in the device's port and IP address
   
   
   

Setting up the the observations

This driver decodes both the Pan and Tilt which correspond to the following rotations in Qinsy:

1. Add an observation
   
   
   
2. Define the observation
   
   1. Select the type of observation;
   2. Define a name for this observation;
   3. Select to which vessel object this observation is relevant;
   4. Select at which node this observation is observed;
   5. Confirm your settings and press OK.
      
      
3. Assign the appropriate slots to the observations
   

Database Setup

Bathymetry / Snippets / Water Column

1. Add a new "Multibeam Echosounder" system to the object in your template database
2. Select driver "Reson Seabat 7K (TCP/Network)" unless you use a Dual Head Norbit system.
   In that case use the same driver for both heads
   1. Port Head "Reson Seabat 7K (TCP/Network)" 
      1. Port 7000
   2. Starbord head "Reson Seabat 7K (TCP/Network)"
      
      1. Port 7001
3. The IP address should be the IP address of the Norbit system.
4. Used IP address should be the computer that is running the WBMS Software, leave at 127.0.0.1 if running on the same machine.
   
   
   

• On the Seabat 7k Settings page we can select which raw packets are stored in the database:
  

  1. System
     Select the system you are using with this driver. 

  2. Packet storage for processing
     Here you can select which processing tool (if any) you want to use. When a specific processing tool is selected, the raw packets required by that tool are automatically stored in the database. 
     Only the processing tools which are supported by the device you are using are shown.
     Supported processing tools include:
     • FMGT - FlederMaus Geocoder Toolbox 
     • FMMW - FlederMaus Mid Water

     • XTF - Processing tools that can handle eXchange Triton Format import (CARIS / PDS / ect.)