Mu Gapsm7 An 005 I
Mu Gapsm7 An 005 I
Positioning System
User Guide
Gaps M7 - User Guide
Revision History
Copyright
All rights reserved. No part of this manual may be reproduced or transmitted, in any form or by
any means, whether electronic, printed manual or otherwise, including but not limited to
photocopying, recording or information storage and retrieval systems, for any purpose without
prior written permission of iXblue.
Disclaimer
iXblue specifically disclaims all warranties, either expressed or implied, including but not
limited to implied warranties about merchantability and fitness for a particular purpose with
respect to this product and documentation. iXblue reserves the right to revise or to make
changes or improvements to this product or documentation at any time without notify any
person of such revision or improvements.
In no event shall iXblue be liable for any consequential or incidental damages, including but not
limited to loss of business profits or any commercial damages, arising out of the use of this
product.
Export Control
This product is subject to export control regulations. Please refer to the commercial offer or
contact iXblue for details about the applicable export control regulations and restrictions.
Guide Overview
This document is the User Guide for Gaps M7. It must be read and understood prior to using
the system. The manufacturer shall in no case be held liable for any application or use that
does not comply with the stipulations in this guide. Gaps M7 User Guide is divided into the
following parts:
● Introduction - This section contains a general and technical description of Gaps M7.
● Conventions and Specifications - This section gathers all important information about
reference center, reference axes, signs of attitude angles etc.
● Installing Gaps M7 - In this section, you find the procedure to install the Gaps M7
system, to assess its geometrical configuration parameters, and to plan all connections to
external systems.
● Configuring Gaps M7 - In this section, you find the procedure for configuring Gaps M7
with the help of the Web-based User interface. It describes all required parameters before
operating the system.
● Setting Gaps M7 to Work - This section gathers all tasks that have to be gone through
before the start of the survey.
● Visualizing USBL Data with DELPH RoadMap - This section describes how to use
DELPH RoadMap software in order to visualize USBL data coming out of Gaps M7.
● Coupling Gaps M7 and Subsea INS - This section describes the connection between
Gaps M7 and a subsea INS installed on an ROV.
● Operating Gaps M7 - This section provides the full description of operation of Gaps M7.
● Maintenance - This section provides the preventative and corrective maintenance for
Gaps M7.
Text Usage
Bold text is used for items you must select or click in the software. It is
Bold
also used for the field names used into the dialog box
Text in this font denotes text or characters that you should enter from the
Courier keyboard, the proper names of disk drives, paths, directories, programs,
functions, filenames and extensions
Italic text is the result of an action in the procedures. It is also used for ref-
Italic
erencing to other document titles
Icons
The Note icon indicates that the following information is of particular interest
and should be read with care.
Important
The Important mention indicates that the following information should be read
to forbid or prevent a product dysfunction or a faulty operation of the equip-
ment.
The Caution icon indicates that the following information should be read to for-
bid or prevent product damage.
The Warning icon indicates that possible injury or death could result from fail-
ure to follow the provided recommendation.
Table of Contents
1 INTRODUCTION 14
1.1 PRINCIPLE 14
1.2 EQUIPMENT DESCRIPTION 16
1.2.1 Overview 16
1.2.2 Gaps M7 Head 17
1.2.3 Gaps Box 18
1.2.4 Web-Based User Interface 18
1.2.5 Acoustic Transponders 19
1.2.6 Optional Integrated DGPS 20
1.2.7 USBL Telemetry 20
1.2.8 Ping Stacking 20
1.2.9 Optional HiSys Hoisting System 20
2 CONVENTIONS AND SPECIFICATIONS 22
2.1 CONVENTIONS 22
2.1.1 Center of Measurements, Acoustic Center and Reference Axes 22
2.1.2 Hydrophones and Reference Frame 22
2.1.3 Attitude 23
2.2 SPECIFICATIONS OF GAPS M7 ACOUSTIC ANTENNA 24
2.2.1 General Characteristics 24
2.2.1.1 Positioning 24
2.2.1.2 Operating / Environment 24
2.2.2 Mechanical Specifications 24
2.2.3 Electrical Specifications 25
2.2.3.1 Main Cable 25
2.2.3.2 Optional Repeater Box for the Main Cable 27
2.2.3.3 Optional Gaps M7 GPS Cable 29
2.2.3.4 Optional Gaps M7 Y Cable 29
2.2.3.5 Gaps Box 31
2.2.3.6 Power Supply 33
2.2.3.7 Synchronization Signals 34
2.2.3.8 Serial Link Wirings 34
3 INSTALLING GAPS M7 35
3.1 CHECKING THE DELIVERY 35
3.2 INSTALLING THE ACOUSTIC ANTENNA 36
3.2.1 Recommendations 36
3.2.1.1 Cable Curvature 36
3.2.1.2 Environmental Noise 36
3.2.1.3 Reflective Surfaces 36
3.2.1.4 Corrosion 37
3.2.2 Principles 37
3.3 INSTALLING THE GAPS BOX 39
3.3.1 Electromagnetic Compatibility Recommendations 39
3.3.2 Cable Curvature 39
3.3.3 Connecting the Gaps Box 40
5.1.5.1 Description 77
5.1.5.2 Procedure 78
5.1.5.3 Ping Stacking Limitations 78
5.2 ENTERING A SOUND VELOCITY PROFILE 79
5.2.1 Loading a Profile from a Data File 79
5.2.2 Entering Manually a Profile 80
5.3 SETTING UP THE TRANSPONDERS 82
5.3.1 Adding a Transponder 85
5.3.2 Configuring a Transponder 86
5.3.2.1 Parameters 86
5.3.2.2 Procedure 88
5.3.3 Activating a Transponder 90
5.3.4 Deleting a Transponder 90
6 VISUALIZING GAPS M7 DATA IN DELPH ROADMAP 91
6.1 INTRODUCTION 91
6.2 DELPH ROADMAP FEATURES 92
6.2.1 Navigation Menu 92
6.2.2 Toolbars and Panels 92
6.2.2.1 Equipment Toolbar 93
6.2.2.2 Panels 93
6.2.2.3 Mobile Toolbar 95
6.3 REAL -TIME MODE 96
6.3.1 Defining an Equipment 96
6.3.2 Configuring the Connection 97
6.3.3 Configuring the Logging 99
6.3.4 Connecting Equipment and Logging Data 100
6.3.5 Editing the Display 102
6.4 REPLAY MODE 104
6.4.1 Importing a Navigation Data File 104
6.4.2 Replaying a Dataset 105
6.5 VISUALIZATION TOOLS 106
6.5.1 Mobile Immersion 106
6.5.2 Vertical Axis 107
6.5.3 Range Circle 108
6.5.4 Uncertainty Ellipse 109
6.5.5 LBL Range 110
6.5.6 North Oriented View 112
6.5.7 Heading Oriented View 113
6.5.8 Mobile Information 114
6.5.9 Relative Positioning 115
6.5.10 Event Marks 116
6.5.10.1 Creating an Event Mark 116
6.5.10.2 Managing Event Marks 118
6.5.11 Waypoints 119
6.5.11.1 Creating a Waypoint 119
6.5.11.2 Managing Waypoints 121
1 Introduction
1.1 Principle
The Global Acoustic Positioning System Gaps is a portable Ultra Short Base Line (USBL) with
an integrated Inertial Navigation System (INS inside Gaps M7) or an Attitude and Heading
Reference System (AHRS inside Gaps M5) and Global Navigation Satellite System (GNSS).
Plug and Play Gaps M7 system is recommended for mobile or fixed installations. It can be combined with an
additional hoisting system. It is a plug & play installation. No calibration is required before
using your Gaps M7.
Accuracy Gaps M7 system is used to deliver:
● The position of one or more underwater objects or vehicles, which can maneuver at depth
up to 3,000 meters. Deeper is possible depending on the type of beacon used.
● Accuracy is up to 0.06 % of the slant range depending on operational conditions.
● The heading, attitude, motion and position of the support vessel or buoy.
Operation The underwater objects or vehicles are tracked using acoustic transponders. Gaps M7
Principles
antenna is deployed underwater and is usually mounted below the ship hull.
Gaps M5 vs. M7 In the table below are gathered the main differences between Gaps M5 and Gaps M7.
Gaps M5 Gaps M7
Heading / Roll / Pitch accuracy 0.5 / 0.1 / 0.1° 0.01°
Maximum positioning range 995 m 3,000 m
Weight in air / water 14 / -5 kg 16 / -7 kg
Housing height 520.8 mm 638 mm
32 W nominal 37 W nominal
Consumption < 100 W at starting up < 100 W at starting up
50 W transmission 60 W transmission
iXblue MT8
iXblue MT9
iXblue ET / RTAx2
iXblue ZTA02C
iXblue RAMSES
iXblue CANOPUS
iXblue STAx2
iXblue MTBx2
* Only the “software permitting”. Make sure your Applied beacon has the iXblue codes
compatibility before operating.
2.1 Conventions
2.1.1 CENTER OF MEASUREMENTS, ACOUSTIC CENTER AND REFERENCE AXES
Center of The Gaps M7 center of measurements is in the center of the mounting flange of the acoustic
measurements
antenna. In the Web-User Interface, the Gaps M7 center of measurement is equivalent to the
CRP (Common Reference point). The Gaps M7 center of measurement is the reference point
for the determination of external sensor (i.e., GPS) lever arms.
Acoustic The distance between the center of the measurements (center of the top flange) and the
Center
acoustic center is approximately 0.6 m (589.3 mm). The acoustic center is at the barycenter of
the four hydrophones.
Reference The lever arms of the external sensor with respect to the Gaps M7 center of measurements is
frames
represented by three lengths LV1, LV2, LV3 defining the position of the external sensor in the
(XV1, XV2, XV3) vessel reference axes.
Misalignment The misalignments of the acoustic antenna are measured between the reference frame of
Gaps M7 and the reference frame of the vessel. The three misalignment angles are entered by
the operator in the Web-User Interface (MECHANICAL PARAMETERS menu).
2.1.3 ATTITUDE
The attitude angles are defined as follows:
● Roll is positive when Port goes up.
● Pitch is positive when the bow is down.
● Heading is positive when it goes to Starboard.
37 W nominal
Consumption < 100 W at starting up
60 W transmission
Operating temperature -5 °C to 35 °C
Insulation Tests are performed at 500 VDC for conductor to conductor, conductor to shield and
Values
conductor to body (SOURIAU). Accepted result above 200 MΩ. All measured values are
above or equal to 500 MOhm.
SUBCONN Maximal diameter: 42 mm (diameter of the red locking)
Connector
Minimal rigid length with dummy plug: 200 mm
Minimal rigid length without dummy plug: 150 mm
SOURIAU Maximal diameter: 45 mm, molding diameter thicker than the plug
Connector
Minimal rigid length plug and molding: 170 mm
To remove the connector: hold the molding, push the connector toward the box and unscrew at
the same time. If you do not push the connector, the unscrewing is difficult.
1 N Ethernet Rx-
2 X Ethernet Tx-
3 Not Connected
4 Not Connected , used by iXblue GPS
5 C Sync PPS–
6 B Sync IN 1-
7 K Sync OUT 1–
8 F Sync OUT 2–
9 Not Connected
10 Not Connected
11 M Ethernet Rx+
12 Y Ethernet Tx+
13 Not Connected
14 Not Connected , used by iXblue GPS
15 T Sync PPS+
16 A Sync IN+
17 J Sync OUT 1+
18 U Sync OUT 2+
19 Not Connected
20 R,W Power Supply -
21 Z,S Power Supply +
D,E,G Ethernet and Synchro pairs shield
H,L,P,V Reserved by iXblue
Specifications The general characteristics of the Repeater box are the following:
● Weight 2.15 kg
● Size: 217 x 188 x 68.5 mm
● Operating temperature: -20°C / +70°C
● Storage temperature: -20°C / +80°C
● IP rating classification: IP65
The mechanical drawing of the Repeater box is available in appendix K.
Power Supply Power supply from Gaps box: 32 to 38.5 VDC (for 1 repeater box and two 95 m cables).
Connectors The SOURIAU 23-points connector (SOURIAU UT061823SH) and its wiring are the same as
on the Gaps box. The wiring description is to be found in the Gaps user guide.
The SUBCONN 21-points connector (SUBCONN MCOM21M) and its wiring are identical on
the Gaps M7 antenna. See wiring description in section 2.2.3.1
Installation The Repeater box is classified IP65. We recommend an indoor installation. The repeater box
may be installed on any vertical or horizontal surface.
Electrical The Repeater box must be connected to the electrical ground and shield via the threaded rod.
Ground
1 1 Ethernet Rx-
2 2 Ethernet Tx-
3 3 Not Connected
4 7 GND Signal
5 7 GND Signal
6 6 Sync IN 1-
7 7 Sync OUT1-
8 8 Sync OUT2-
9 9 Not Connected
10 Shield
11 11 Ethernet Rx+
12 12 Ethernet Tx+
13 13 Not Connected
14 4 TxA GPS - RS232
15 8 Sync PPS+
16 16 Sync IN+
17 17 Sync OUT 1+
18 18 Sync OUT 2+
19 19 Not Connected
20 20 2 Power Supply -
21 21 1 Power Supply +
3 RxA - GPS RS232
5 RxB - GPS RS232
6 TxB - GPS RS232
Characteristics Values
24 to 36 VDC / 5.6 W
Power supply / Consumption
100-240 VAC
Weight 4.6 kg
Operating temperature -5 °C to 50 °C
Label Type
PPS
SYNC OUT 2 status light
SYNC IN Status light
ON / OFF Status switch and light
Label Type
The 100 – 240 V socket-outlet shall be installed near the equipment and shall be easily
accessible. The Gaps box must be power supplied with either VAC or VDC but not both
simultaneously.
Table 8 - Connector and wiring of the 24 – 36 VDC external power supply connector
B GND
C Earth
D Earth
If Gaps M7 is triggered in responder mode from the outside, with a transponder in responder
mode triggered on the sync IN input (the triggering pulse length must be higher than 5 ms), the
synchro shift between the recurrence and the transponder lasts 100 µs maximum. For this
reason, it is strongly recommended to trigger the transponder on the Sync OUT.
External GPS An optional external GPS may be connected to the external optional GPS message input
serial link. Baud rate, parity and bit stop are adjustable from the Web-based User Interface.
The message expected by Gaps is the standard NMEA $GPGGA message and GPZDA is
automatically taken into account for the update of the Gaps internal time if available.
3 Installing Gaps M7
Before installing Gaps M7 for the first time, we recommend that you check all the parts in the
delivery box, 3.1. The installation is then achieved in four steps:
● Gaps M7 antenna, 3.2
● Gaps box, 3.3
● Optional DGPS Antenna, 3.4
● Transponders, 3.5
On receipt of the equipment, its overall condition should be checked and iXblue informed of
any damage suffered during shipping. Check that every parcel shock label is still white. In the
opposite case it is highly recommended to contact the insurance company.
3.2.1.4 Corrosion
Gaps M7 is an electrical equipment that goes underwater. It may be submitted to differences
of potential that can lead to corrosion of the antenna mechanical structure.
It is your responsibility to minimize the differences of potential between the Gaps M7 antenna
and the surrounding structures. The Gaps M7 antenna must benefit from the electrolytic
protection of the vessel.
Contact iXblue technical support if you notice corrosion damages on the 8 titanium screws
holding the Gaps M7 or directly on the antenna housing (blisters of the paint).
3.2.2 PRINCIPLES
H1 When you set up Gaps M7 on the ship, it is recommended to set the hydrophone H1 towards
the bow of the ship. Positioning H1 towards the bow generates more drag but, in this position,
the acoustic noise is reduced.
Electrical In case Gaps M7 is fixed on metallic plates of different materials (electro-chemical potential,
Insulation
aluminum for example) it is necessary to electrically insulate it in order to avoid any electro-
galvanic reaction that will result in structure corrosion and Gaps M7 acoustic array fouling.
Location and There must be enough space for the wire way on the connector side of Gaps M7. is fixed using
Dimensions
the eight M8 screws.
The torque to mount the eight M8 screws must be from 15 Nm to 17 Nm. There is no need to
use Loctite glue or similar.
Figure 18 - Gaps M7 fixed on the hull and a transponder on a ROV or tow fish
The Gaps box is classified as IP 51 (NF EN 60529 2000). The Gaps box must be installed
inside the ship. If you have to operate the Gaps box on the deck, make sure to use the
appropriate protection for the Gaps box.
The exchange of one Gaps box by another requires that you reboot the computer on which
runs the Web based User Interface before powering the new Gaps box.
Figure 21 - Ferrite cores set up on the serial cables of the Gaps box
Figure 25 - Architecture of Gaps system with the use of the optional iXblue GPS
Flexible link This is typically when Gaps is held by a rope. In that case, the height value (h) must also be
set to 0 (to avoid the calculation of the offset). The accuracy of the positioning decreases if the
position of Gaps relative to the GPS antenna changes.
The closer Gaps is to the GPS, the better is the accuracy of the measurement of the heading
of the acoustic array.
The required precision on the lever arm is below 10 cm.
A PPS can be interfaced with the Gaps box in order to improve the time stamping.
4 Configuring Gaps M7
The configuration of Gaps M7 is carried out from the Web-based User Interface. Before having
access to the interface, you have to connect a computer to the system via the Ethernet link.
Once the system is inserted in the local network, you can launch the Web-based User
Interface and you configure the installation parameter and the survey parameters.
The color code applies for the indicators and text labels displayed in these pop-up windows.
When a problem occurs, the color of the logo changes and these pop-up automatically appear
showing immediately which equipment has raised the problem. Close the pop-up windows by
clicking on the logo.
While tracking, repetitive clicks on the main logo or on the STATUS label on the left of the
main logo display alternatively the SYSTEM DETAILED STATUS and the list of the active
transponders and their associated parameters. A click on the frame of a transponder of the list
allows the display of another set of parameters of the transponder.
Color Definition
Grey Inactivity
You can also use the up / down arrows[↑] [↓] keys to scroll the list.
Text box By typing it in the dedicated area:
You may also use the up / down arrows [↑] [↓] keys to change the numerical values. An
incorrect value is immediately indicated by red color:
Expanding In order to keep each web-based page as small as possible, only the main parameters are
hidden area
default visible. You can expand the hidden area by clicking on its text label title:
OK / Cancel Each command page contains the same buttons. The buttons appear as soon as a
buttons
modification or a selection has been made in the command page:
To validate the new configuration and store it in the electronic of the system.
Tool Tips Move your pointer above some parameters and logo to access its tool tip.
Other Button On “mouse over” action, orange color may surround a button to indicate that the action
performed on the button has important consequences. Example: the system restarts.
2. In Display, select the Language and the Day or NightMode in the scrolling list.
6. In Dynamic Positioning select between Automatic(default); GPS Only, LBL Only and
USBL OnlyMode.
7. Click on OK to validate your choice and to apply it to the Web User Interface.
Make sure to ZIP the options files when sending them by mail in order to avoid any file
corruption caused by mail applications.
Make sure to UNZIP the options files that you have received by mail before loading them into
Gaps M7.
2. In the SAVE SETTINGS frame, edit the Filter and the default File name of the text file in
which you want to save the product settings.
3. Click on the Save Settings button. A window opens offering you to select the location where
to store the file, choose this location and click on the OK button.
The product settings are now saved in a text file at the chosen location.
Gaps M7 settings are not compatible with Gaps M5 Web User Interrface and vice versa.
2. In the RESTORE SETTINGS frame, click on Browse… to select the CNF_ file.
Once selected the name of the file appears in the File field.
A Sending File frame appears briefly. Once the frame has disappeared, the product settings
or options are loaded in the Web-based User Interface.
If you have loaded an option, then the new option is listed in the MAINTENANCE page inside
the SYSTEM OPTIONS frame. See below for the Sonardyne Wideband® 1 option.
Equipment Needed:
● 1 x computer or Laptop (with an unused Ethernet port)
● 1 x Cat 5 Cross Ethernet Cable
By default, Gaps M7 is already assigned with an IP address. When connecting only one
computer to Gaps M7, it is only necessary to adapt the computer to Gaps M7 configuration.
If you have lost Gaps M7 IP address, you can easily recover this address by connecting an
hyper terminal (115200, 8 bits, no parity, 1 stop) to one of the four serial links of the Gaps box
. When you switch OFF and ON the BOX, the IP address of the system is displayed in the
hyper terminal as well as the firmware version and the ID of the serial link.
4. Select the option Use the following IP address and enter 192.168.36.20 for the IP address
field and 255.255.255.0 for the Subnet mask.
The computer IP address used here takes into account that Gaps M7 is using its default
configuration with its default IP address. You may change the IP address and subnet mask of
Gaps M7. In either case the subnet masks of both computer and Gaps M7 must be identical.
If you have no idea on which IP address Gaps M7 has been configured, you may recover this
IP address by connecting a HyperTerminal on the computer to one of the RS232 connector
and configuring the terminal to the following settings: 115200 bauds, 8, none, 1. The IP
address is then being broadcasted by Gaps M7 on the HyperTerminal.
Equipment Needed:
● One Cat 5 Straight Ethernet Cable to set between the BOX and the switch
● A free slot in the local network switch
You configure the Gaps M7 to make it compatible to your local network.
Restrictions on the choice of Gaps M7 IP address and mask are detailed in annex B.
Gateway IP address is the address of the workstation connected to other networks of the
vessel.
2. Edit the IP Address by clicking in the fields and entering new values.
3. Edit the Net Mask by clicking in the fields and entering new values.
4. Edit the Gateway by clicking in the fields and entering new values.
1. Connect physically Gaps M7 to the local network as shown in section 4.2.2. Gaps M7 being
in default network configuration that is not compatible with your local network, Gaps M7 is not
visible from any computer present in the network.
2. Select one computer from which you are going to access and configure Gaps M7. Note the IP
address of this computer. You need this IP address in step 7.
3. Follow the procedure of section 4.2.1to set the computer to see Gaps M7 from this computer.
Gaps M7 is now visible from this computer.
4. Choose an IP address compatible to the local network. You are going to assign this address
to Gaps M7.
5. Add this address to the list of IP addresses of the elements present in the local network.
7. See section 4.2.2.1 to edit Gaps M7 network parameters. Once the computer is configured
and that you can see Gaps M7 from the computer, assign the new IP address to Gaps M7.
For the Net Mask, enter the local network mask.
8. Configure back the computer in its original IP network configuration (before step 3).
Now all computers in the network can see Gaps M7.
It is necessary to fill the GAPS Depth field even if you use only the altitude of the
transponder for a correction of the sound velocity profile.
2. In Misalignments (optional), enter the values of Roll, Pitch and Heading. Input only angles
between -45° and +45°.
3. In GAPS Depth, enter the Distance of the flange of the antenna to the water surface.
4. If it is needed, enter the Lever arm for relative coordinates, the LV1, LV2 and LV3
coordinates in meters.
5. Click on OK to validate your input data configuration and send this data to the Gaps M7.
The heading of Gaps is different from the heading of INS inside Gaps M7 if you have entered
an offset in the Web-based User interface.
The following inputs (Position , UTC , Pressure, Telemetry and Hoisting System ) are
configured here:
Position Position data input comprises position, time and date. GPS is plugged directly to the Gaps
M7 antenna or to the Gaps box. The GPS antenna broadcasts data on Ethernet or serial link.
GPS lever arms are input in the User Interface or in a navigation software but not in both!
UTC External sensors delivering UTC are connected to a serial plug or via the Ethernet network.
Pressure Pressure data input allows the computation of immersion (see Appendix H.2). Pressure
comes from a pressure sensor installed on the underwater vehicle or is broadcasted on an
Ethernet or serial link. A pressure offset can be added to the incoming data.
Telemetry Under Telemetry , set the identical configuration than in the equipment that output the
telemetry datagram. Only one protocol ITS TELEMETRY is available.
Hoisting Sys. State of the hoisting system is displayed as antenna status in the CONTROL menu.
5. For a Serial link, enter the Parity, Stopbits, Standard and Baudrate.
6. For a Ethernet link, select the Transport Layer, IP address and Port.
7. Lever Arms, enter LV1, LV2, LV3 separating GPS from the CRP. Make sure the GPS lever
arms have not been input in a third party navigation software. See note below.
8. You may set the Gaps M7 in Forced Mode by selecting the corresponding check box. All
GPS positions are input in the INS
9. Click OK to validate your input configuration and send this data to Gaps M7.
You may enter the lever arms in the Gaps Web-based User Interface or in the third party
navigation software. The drawing below describes the two options.
4. In Protocol, select the Protocol and the PPS in the corresponding scrolling lists.
7. Click on OK to validate your input configuration and send this data to the Gaps M7.
4. In Protocol, select the Protocol and the Timeout in the corresponding scrolling lists.
6. For a Serial link, enter the Parity, Stopbits, Standard and Baudrate.
7. For an Ethernet link, enter the Transport Layer, possible IP and Port.
8. Click on OK to validate your input data configuration and send this data to the Gaps M7.
7. Click on OK to validate your input data configuration and send this data to the Gaps M7.
The ITS TELEMETRY protocol is produced each time telemetry data is received.
4. In Protocol, select NMEA 183 / PMEVL and enter a Timeout (from 1 to 10 s).
7. Click on OK to validate your input data configuration and send this data to the Gaps M7.
4. If you have selected a Serial link, enter the parameters of this link:
5. If you have selected an Ethernet link, enter the parameters of the link:
http://IP.IP.IP.IP/ins_restricted_area/
Please refer to Phins Web-based User Interface for a complete description of the configuration
of the internal INS of Gaps M7.
This chapter concerns the actions and procedures to be carried out just before starting
positioning operations. These actions are as follows:
● Definition of the tracking parameters, see section 5.1
● Configuration of transponders (USBL and L/USBL modes), see section 5.3
● Measurement and input of profile celerity of sound, see section 5.2
The configuration of positioning parameters is carried out in the TRACKING component from
the menu SETUP.
R is the recurrence. TAT is the turn around time (90 ms most of the time, 20 ms in deep water).
The blanking time of the transponders sets the transponders acoustic reception window.
These windows must be as short as possible in order to avoid multipath detections and long
enough to allow the motion of the transponder between two interrogations of Gaps M7.
The recurrence is to be defined before the blanking time.
Choice of the recurrence:
The choice for the recurrence is mainly made upon the maximal travel distance.
1 1,365 682
2 2,865 1,432
3 4,365 2,182
Recurrence (s)
4 5,865 2,932
5 7,365 3,682
6 8,865 4,432
When telemetry data is received during the positioning cycle, keep in mind that the decoding
of the telemetry data takes approximately three seconds. The choice of the recurrence must
take this time into account.
Choice of the blanking time
The choice of the blanking time depends on
● Recurrence of Gaps M7
● Number of different interrogation frequencies used for the active transponders
● Repetition factor
One rule might be to remove 200 ms to the interrogating rate of each transponder in order to
find the blanking time. A series of examples is given in appendix E.
4. From the Activation pull-down list, set the type of edge on which the acoustic emission is to
be set off to Rising Edge.
5. Select the value of the Min. Duration from the associated pull-down list.
5.1.5.2 Procedure
3. Enter a ping stacking Recurrence (internal synchro mode) or Inhibition (external synchro
mode) in the corresponding field.
It is necessary to fill the GAPS Depth field (section 4.3) even if you use only the altitude of
the transponder for a correction of the sound velocity profile.
1. Click on Browse… and select the file containing the sound velocity profile.
The speed profile is pre-processed when uploaded. This processing removes outliers and
duplicated values, sorts the data in a depth growing order and optimizes the number of couples
to 55 for computing purposes without altering the accuracy of the profile.
Message Action
4. Click on [Tab].
The velocity corresponding to the depth value entered is highlighted.
5. Enter the new velocity value (between 1,375 and 1,900 m) matching the entered depth.
6. Click on [Tab].
The depth value of the following line is highlighted.
7. Go back to step 3 until you have entered all the depth and velocity data from your profile.
8. Click on OK to validate your choices and to send this data to the system.
One value which is outside validity appears in red. It will be impossible for you to validate the
speed profile before having replaced these values with valid data.
Applied 1019
28% (60) of
Sonardyne
Sonardyne COMPATT 5 COMPATT6 Wideband® 1 codes*
F1 – F14, CIF
(CRF and IRS)
100% of
Sonardyne
Wideband® 1
codes* (CIF &
IIF)
The Gaps M7 positions the immersed transponders. Before starting positioning, you have to
list, configure and activate the transponders via the web user interface.
Access the management of transponders in the TRANSPONDER component from the
SETUP menu. Transponders which are already present in the data base are listed in this
window and you can see at a glance how these transponders were configured and whether
they are still active or not. See the transponder window below.
Multi Several transponders can be simultaneously interrogated. The interrogation then takes place
Transponders
on as many cycles as there are various frequencies. The transponders are separated thanks
to different MFSK reply codes and Individual Interrogation Frequencies (IIF). Two
transponders cannot have the same interrogation frequency and reply codes. If different
interrogation frequencies are used simultaneously, the Gaps M7 makes a recurrence for each
interrogation frequency. We can also mix responder and transponder modes to interrogate the
transponders. In addition the repetition factor parameter can be used to increase the acoustic
update rate for one specific interrogation frequency.
Below is listed the limitations of the system in terms of multi transponder configuration:
● 500 transponders simultaneously configured (not activated)
● 18 recurrences per cycle
● 40 activated transponders
● 15 different response codes per cycle
● 15 different response codes per recurrence
You can interrogate transponders in transponder mode and in responder mode in the same
configuration.
When the two interrogation frequencies are different, the blanking time is higher than the
acoustic recurrence. In a single transponder mode, you cannot have a blanking time higher
than the acoustic recurrence. So when you use two transponders with two different
frequencies, make sure to have the correct settings in the transponder hardware.
Codes There are, see table above, several families of interrogation/reply codes:
● Codes 22 / 23
● Codes 0 to 45
● Codes Sonardyne Wideband®1
It is recommended to use codes from only one family in the frequency plan. iXblue guarantees
the intercorrelation properties only within the same family of codes.
From this window, you can carry out the following tasks:
● Add a transponder to the list
● Configure a transponder (interrogation, reply, dynamic positioning mode, filtering)
● Activate a transponder
● Remove a transponder from the list
4. Select one of the transponders listed under Type (optional) and click on Create.
If you have the Sonardyne Wideband® 1 option*, select WB 1 for the Type (optional) in order
to configure Gaps M7 for a transponder using Sonardyne Wideband® 1 signals.
The configuration window opens.
* Check on the maintenance page if you have the Sonardyne Wideband® 1 option:
Reply Under Reply are the acoustic parameters that characterizes the transponder response.
● Code: defines a medium frequency MFSK signal, for all possible reply codes depending
of the transponder type.
● Turn Around Time : Inactivity period between the start of the interrogation signal
reception and the beginning of the response emission. Between 20 and 200 ms.
Filtering The filtering heading enables you to apply a filter on positional data. The available options are:
None, Fixed and Mobile:
● None (with rejection): Default mode, the system outputs raw position but filter the outlier
position.
● None (without rejection): outlier filter is fully disabled, the system outputs all raw
positions.
● Fixed or Mobile: In both cases, the measured position is input in a Kalman filter. This
option artificially increases the output rate of positions and achieves a prediction of the
position. These output positions are not the measured acoustic positions.
By default, do not activate the filter. Activate the filter if the unfiltered positioning is stable and
if the increase of the output rate is necessary.
5.3.2.2 Procedure
4. In Reply, select Code and Turn Around Time from the scrolling lists.
6. In Dynamic Positioning, set the Mode to L/USBL if you use the current transponder to
compute the position of the USBL antenna.
Enter manually the Latitude, Longitude, Depth and Accuraciesof the transponder or click on
Get Current Position to get the transponder USBL position.
If no reference has been set yet, select Use as reference transponder to set the current
transponder as reference. The antenna position is computed with the reference transponder.
8. In Other,
● Enter an 8-characterLabel
● Select a Repetition Factor in the scrolling list
● Set the Position Management to Sent by Telemetry if you wish to send to the
transponder its own USBL position so the transponder can possibly transmit its position
to other device.
9. Click on OK to validate your choices and to send the data into the system.
6.1 Introduction
Delph This section describes the visualization of USBL data in Delph RoadMap application. For a
RoadMap
complete description of the Delph RoadMap application and of all its generic functions, please
refer to the specific Delph RoadMap User Guide.
Visualization Delph RoadMap is designed to visualize in three dimensions all kinds of geographical data.
You can visualize in Delph RoadMap the USBL geographic positions in real-time as well as in
off-line mode. Delph RoadMap displays the USBL data with the navigation of the ship as well
as any background images and coastlines.
Visualization These are the ways to visualize USBL data in Delph RoadMap:
modes
● Real-time mode: the real-time data is sent via the Ethernet or serial link, transmitted to
Delph RoadMap and displayed in Delph RoadMap main display area.
● Replay mode: the data is directly imported in Delph RoadMap and all at once displayed in
the main graphic area.
6.2.2.2 Panels
Enable or disable automatic tracking of the selected mobile. Centers the map on the
current position of the selected position source and the centering is updated as the position
changes. Only in real time mode.
Show or hide the mobile on the immersion panel . The immersion of the different
sources of position are gathered in the immersion panel so their evolutions are compared one
to the other, you can choose with this button which source of position to display in the
immersion panel. Only in real time mode.
Show or hide the vertical axis. A vertical axis is displayed at the current position of the
selected position source. Only in real time mode and in 3D view.
Show or hide the range circle. This tool draws a circle at a certain distance from the
mobile. The distance is editable in the mobile Properties. Only in real time mode.
Show or hide the uncertainty ellipse around the selected mobile in the 3D view. Only in
real time mode.
Show or hide the LBL range of the selected mobile towards the system mobile (if
available) in the 3D view. Only in real time mode.
Clear the track history for the selected mobile. Removes all displayed past positions of the
selected position source. The track keeps being displayed starting at the position where you
have clicked on the button. Only in real time mode.
Switch to a 2D north up display mode. Switches the current view to a view which is seen
from above and in which the North is oriented to the top.
Create an event. Keeps track of a particular event and display a sign in the geographic view
at the location of the selected position source. All related information is recorded in a KML
data file. Only in real time mode.
1. Select the Navigation > Add equipment… menu or in the Project view panel, right click on
Navigation and select Add equipment… in the menu that opens.
The Equipment window opens. The General tab is by default opened.
5. Click on OK.
The chosen equipment is defined. An item with the Label as name and with a red icon is
added under the Navigation in the Project view.
3. Select the Connection between Ethernet TCP, UDP and PC Serial Port.
4. If you selected Ethernet TCP, enter a Communication Port and the IP address.
6. If you selected PC Serial Port, select the Port Number and click on the button to open the
serial port configuration window. Select the Bits Per Second, Data Bits, Parity and Stop
Bits parameters.
2. Select the Type of data to be stored. The choice has to be made between All datagrams (all
received data is stored) and Interpreted datagrams only (all decoded data is stored).
4. Select the path of the Output Folder where to store the logged files.
5. Select an Automatic Switching Mode between None, File Size or Duration and the
corresponding limit of file Size (ko) or limit of Duration.
● In the equipment toolbar, select the piece of equipment or All equipment (if you wish to
● In the equipment toolbar, select the equipment or All equipment (if you wish to log data
The symbols of all the pieces of equipment that are logging are displayed as follow: .
Open the Logging panel to display the size and recording duration of the logging files as well as
the logging status or remaining disk space available when critical.
Switch to new There are two ways to manually switch the logging to a new file outside the duration and file
log file
size limit that you might have configured:
● Right click on the equipment item under Navigation and select Switch to a new log file
in the menu that opens.
● In the equipment toolbar, select the equipment device or All equipment (if you wish to
switch to a new log file for all equipment devices at once) and click on the switch button
.
As soon as one of the two limitations described above is reached, the current log file is closed
and a new file is opened for recording the incoming data flow.
1. Right click on a mobile under Navigation > Equipment in the Project view panel and select
Properties in the pop-up menu that opens.
2. In the Mobile properties window, in the Source tab, select the proper geodesy.
7. Select the Label tab, activate or not the display of the label. If you set it to Active, edit the
Font Name, Size, Bold and Italic parameters.
It is recommended to set a limitation of the track size (number of points or duration) in order to
avoid decreased performance over time.
1. Define the equipment from which you import data as detailed in section 6.3.1.
2. In the project view panel, under Navigation, right click on the name of the equipment and
select the Import > Navigation Data… menu.
In the Project view panel, the mobiles that are present in the file are listed below the selected
equipment. Below the mobiles are listed the imported data files.
1. Select Display > Panels > Time or right click in the ribbon and select Time in the menu.
2. Move the two cursors at each side of the time scale and place them at the locations of the
time interval of your choice. You may also directly enter, in the Start Time and End Time
fields, the Date and Time of the interval of your choice.
Double click on the scale bar resets to the full extent.
Only data from the imported file acquired during the chosen time interval is displayed.
which you have clicked on the button are present in the Mobile Immersion. The panel
is automatically rescaled as data comes in to optimize the visualization of the immersions for
the last received position. You can add or remove a mobile by clicking on .
The Mobile Immersion panel is configurable via the Settings window. The units of the
positions, latitude longitude angle distances, distances and depth are editable in the
application settings.
You can display a vertical axis for a specific mobile by clicking on the button after
having selected the mobile in the scrolling list. This axis helps you to visualize the depth of a
mobile. The vertical axis has an automatic scaling in order to optimize the visualization. See
an example of such a display below.
Figure 46 - The vertical axis displays the immersion of the selected mobile
1. In the Project View panel, right click on the mobile and select Properties.
2. In the Properties window, select the Track Properties tab and activate the Display vertical
axis option.
1. In the Project view, right click on the mobile around which you want to draw a circle and
select Properties in the menu that opens.
2. Open the Track Properties tab. Under Range circle, edit the Display range circle of radius
field.
The tool is accessible via the button in the Equipment toolbar and via the mobile
properties window.
Access the tool via the Equipment toolbar button or the mobile properties window.
The objective is to visually check the residuals of the range to the transponders to help
determine whether sound velocity is under-estimated or over-estimated.
The range residuals are the difference between the following distances:
● Acoustic distances measured by Ramses
● Distances computed by Ramses between the acoustic-inertial position of the vehicle and
the known position of the received transponder
Figure 51 - Range circular arcs from the beacons to the positioning system
the button or by selecting the menu Display > 2D View North up. This view is a 2D
view in which the top side is oriented to the North. See below the orientation of the compass
(in the top right corner) and the 3D axis in the bottom right corner.
the button or by selecting the menu Display > 2D View Heading up. This view is
centered on the selected mobile. The heading of the position source stays always directed to
the top of the display. Equidistant concentric circles are drawn to indicate the distance to the
tracked mobile. Rays of these circles are drawn at regular angular intervals to indicate the
angle with respect to the heading of the mobile.
● Click on the button to auto scale the display of the mobile track.
● Click on the button to hide or show the link between the vessel (0) and the current
position of the mobile.
Keep in mind in this graph that the vessel is moving. The displayed track(s) includes, without
showing it, the motion of the vessel.
Click on to create an event mark. The event mark is displayed at the current location of
the selected mobile at the time when you clicked on the button. A KML file is created. This file
can contain several event marks. Another file can be created to store other marks. The mark
can be labeled (the label appears on the display), described and its width, style, color and
transparency can be edited. Date, time, position and immersion of the mark are displayed in
the Feature Data tab.
1. During real-time display, if an event occurs and you want to create a mark to keep track of
3. In Label tab, set the label to Active or Inactive. Edit the Font of the label (Name, Size, Bold
or Italic).
4. In Style tab, you may choose to use a Style. In this case, select a Style in a style File to
apply to the mark.
5. In Points tab, select the Width and Style in the corresponding scrolling lists. Click on the
arrow in front of Color to open the Select Color… window. Click OK.
6. In Display properties tab, move the cursor along the Transparency scale to choose a value
between 0 and 100%.
If you do not want the next created event mark to be written in the same file, unselect Active
in the pop-up menu. At the creation of the next event mark, a new KML file is created.
If you remove an event mark data file, all the event marks written in the data file are also
removed from the Project view panel.
Event Mark You can perform a few operations directly on an event mark. In the Project view panel, under
Edition
Annotations / Features, if you right click on one event mark, a pop-up menu opens:
From the event mark pop-up menu you have access to the following items:
● Remove: the mark does not appear anymore in Delph RoadMap (but is not deleted from
the KML file).
● Visible: you can hide or show the mark.
● Zoom to: you can set the view of the main graphic display to focus on the event mark.
● Delete: Event is deleted from the KML file and from the application.
● Properties: you edit the same parameters as explained during the event mark creation.
6.5.11 WAYPOINTS
6.5.11.1 Creating a Waypoint
Click on to create a waypoint. The waypoint is displayed at the current location of the
mouse cursor. A KML file is created. This file can contain several waypoints. Another file can
be created to store other waypoints. The waypoint can be labeled (the label appears on the
display), described and its width, style, symbol, color and transparency can be edited. Date,
time, position and immersion of the mark are displayed in the Feature Data tab.
1. Click on to select the waypoint mode. Move the mouse cursor at the location where you
want to create a waypoint and double click.
The waypoint is created and the waypoint creation window opens.
2. In Feature tab: enter the Label of the waypoint. You may enter a Description. You may edit
the associated KML File and Folder.
3. In Feature data tab, the coordinates of the waypoint are available. You may edit the
Immersion value set to zero by default.
4. In Label tab, set the label to Active or Inactive. Edit the Font of the label (Name, Size, Bold
or Italic).
5. In Style tab, you may choose to use a Style. In this case, select a Style in a style File to
apply to the mark.
6. In Symbol tab:
● Select the Style in its scrolling list. For User-Defined, provide the .3ds file.
● Select the Color in the Select color … window that opens when you click.
● Select the File to define the style of the mobile. This option is only active when the User-
Defined Style is selected.
● You may check the Wireframe display and Apply Vertical exaggeration options.
● In Model Size tab, enter a Length (m), Width/Radius (m) and the Height (m) values.
● In Offsets tab, enter the optional Offsets X, Y, Z in meters and/or degrees.
7. In Points tab:
● Select a Width in the scrolling list.
● Select a Style in the scrolling list.
● Select the Color in the Select color … window that opens when you click.
8. Open the Display properties tab and move the cursor along the Transparency scale to
choose a value between 0 and 100%.
If you do not want the next created waypoint to be written in the same file, unselect Active in
the pop-up menu. At the creation of the next waypoint, a new KML file is created.
If you remove a waypoint data file, all the waypoints written in the data file are also removed
from the Project view panel.
Waypoint You can perform a few operations on a waypoint. In the Project view panel, under
Edition
Annotations > Features, if you right click on one waypoint, a pop-up menu opens:
From the waypoint pop-up menu you have access to the following items:
● Remove: The mark does not appear anymore in Delph RoadMap.
● Visible: Hide or show the waypoint.
● Zoom to: Set the view of the main graphic display to focus on the waypoint.
● Delete: Waypoint is deleted from the KML file and from the application.
● Edit: Change the coordinates, altitude and name as well as the geodesy
● Properties: Edit the same parameters during the waypoint creation.
Global Edition In the Project view, Right click on the Waypoints folder to open the edition window. In this
window, you may edit the coordinates, altitude and geodesy of all the existing waypoints.
6.5.12 MEASUREMENTS
The measurement window is used to follow the distance between two displayed objects.
These objects may be mobile or not. All items in the Navigation Data , point type
Annotations, waypoints, events, sonar targets may be selected to compute measurements
among them.
Measurement The following procedure details how to make measurements with the pair selection window.
Pair Selection
1. Select the menu Navigation > Add Measurement… or click on the measurement toolbar
button .
The Measurement Pair Selection window opens.
2. Select a Navigation or Annotation item in the #1 Project Item list and another Navigation
or Annotation item in the #2 Project Item list.
Icon Task
In the Project view the right click pop-up menu allows the user:
● To Flip the two objects between which the measurement is computed
● To make the measurement Visible or not
● To Remove the measurement
● General
> File Name: the name of the source navigation file
> Equipment: label of the selected equipment
> Mobile: label of the selected mobile
> Z Level: if you have selected Google Earth (KML) as a File Format, you may select
the source of the exported depth, the default value for other File Formats than
Google Earth (KML) is Surface:
- Clamp to sea level the trajectory is displayed on the surface,
- Clamp to seabed the trajectory is displayed on the seabed
- Relative to sea level the trajectory is displayed relatively to the surface
> Track: this option includes the track in the output, a Color may be selected (Color is
set by default to white for other File Formats)
> Positions: this option includes the positions in the output, a Color may be selected
(Color is set by default to white for other File Formats)
● Output
> File Format: three formats are available
- Google Earth (KML) you may then choose the type of Z Level above
- ESRI Shape File (SHP)
- Autocad DXF File (DXF)
1. In the Project View panel, under Navigation, right click on the file from which you want to
export the trajectory.
The Trajectory Export window opens.
2. If the export File Format is Google Earth (KML), select the Z Level in the corresponding
scrolling list.
3. You may activate the Track and/or Positions options. If the export File Format is Google
Earth (KML), select the Color of these two options.
4. Expand the Output item and select a File Format, enter a Storage Folder path and choose
a File Name type.
5. Click on Start to run the export. You may select the Close window at the end of the
processing option and/or the Open processing result option if the File Format is Google
Earth (KML).
The completion state of the export process is displayed on the progress bar.
Rovins Nano
Rovins
Phins Subsea
In this section, is detailed how to connect Gaps M7 to the INS in order for Gaps M7 to provide
to the INS the needed absolute positioning. Gaps M7 must be configured to output data to the
INS and the INS must be configured to input data coming from Gaps M7. The protocols that
must be used are the following:
● GAPS STANDARD: this protocol has several drawbacks :
> ASCII format (not optimal in term of bandwidth in an umbilical or acoustic modem)
> Many telegrams are not used by the INS
> Standard deviation is estimated in INS
> Positions are time stamped so it is mandatory that Phins and Gaps M7 receives ZDA
● IXSEA USBL INS 1:
> Binary (optimal in term of bandwidth in an umbilical or acoustic modem)
> Positions are time stamped so it is mandatory that the INS and Gaps M7 receives
ZDA
> Standard deviation is estimated by USBL
● POSIDONIA 6000:
When post-processing Gaps M7 and the INS data files, keep in mind that a lever arm must be
included in the parameters. See appendix J
7.3 Procedures
7.3.1 OUTPUT CONFIGURATION IN GAPS M7 WEB-BASED USER INTERFACE
Make sure that for each used transponder, the filter on the positions is set to None:
3. Select IXSEA USBL INS 1 or POSIDONIA 6000 for the Protocol and the Minimum
Frequency of your choice from the pull-down list:
4. If you have selected a Serial link, enter the parameters of this link:
5. If you have selected an Ethernet link, enter the parameters of the link:
2. Select a port among the ports A to E and click in the table, in the column of the selected port
and in the USBL line.
The selected table cell is highlighted.
The protocol appears now in the first line of the table. All the other cells of the selected port
column are grayed because only USBL data will enter this port.
5. For a Serial link, set up the Parity, Stopbits, Standard and Baudrate.
6. For an Ethernet port, select the Transport Layer, the IP address (in the case of a TCP
Client Transport Layer) and the Port number.
8. In Lever Arms enter the LV1, LV2 and LV3 values in meters.
9. Click on OK to validate your choices and to send the configuration in the INS.
2. Configure the INS subsea with USBL input (protocol iXblue STD BIN).
3. In the Gaps M7 Web-based Interface, select SETUP > TRANSPONDER and add a MTB.
4. In the list of transponders, click on Change settings for the MTB. Configure the transponder.
In Other, for the Position management, select Send by Telemetry.
8.1 Definition
Gaps M7 can be used as an external hydro acoustic position reference for the Dynamic
Positioning (DP). Gaps M7 is directly interfaced to the DP and outputs the position of the
vessel to the DP using referenced moored acoustic transponders.
The purpose of this mode is that DP cannot only trust the GNSS data. If there is a GNSS
failure or outage, the hydro acoustic position reference still provides an accurate positioning of
the surface vessel. These hydro acoustic position references are essential for DP class 2 and
3. The INS becomes the core component of the positioning system and achieves the data
fusion of all available sensors (LBL, USBL and GNSS).
When L/USBL or L/USBL/INS mode is activated, Gaps M7 can still simultaneously track
mobile transponder in USBL.
Depending on the selected output protocol, the LBL computed position is either given with
respect to the position of a reference transponder, or directly the absolute georeferenced
vessel position (with GNSS data available).
There is no constraint on the number of transponders to deploy. Only a single transponder can
be used. The addition of several transponders increases the redundancy and accuracy of the
final position. Figure below presents examples of performances that can be reached
depending on the number of deployed transponders.
Fixed transponders are placed in order to give maximum observability for surface positioning.
Vessel position is centered into the field of transponders.
Subsea array size (distance between subsea fixed transponders) is in same order of magnitude than water depth.
USBL SNR = 30 dB, N = 100 (number of USBL recurrences for the box-in of fixed transponders).
8.4 Procedure
Prerequisite The INS of Gaps M7 must be aligned (see section 9.2.1).
Box-in Once the transponders have been deployed, they must be calibrated. Box- in of one
transponder typically requires 100 USBL fixes. Once calibrated, the positions of the fixed
transponders have to be input in the dynamic positioning parameters. There are two ways to
input these parameters:
● Recover these coordinates by clicking on the Get Current Position button (only
available when the USBL system is tracking) to fill these fields automatically with the
current USBL position of the transponder.
● Input manually the position of the transponder in the dedicated fields.
Only one transponder can be set as a reference at a time. The position of the USBL antenna is
computed with respect to the position of the reference transponder.
DP Protocols The protocols to select in the output configuration and that can be read by a DP system are :
● HIPAP HPR 400
● HIPAP HPR 418 fix or mobile
● KONGSBERG BCD
1. Click on options.
2. Under Dynamic Positioning, select Automatic (default), GPS Only, LBL Only or USBL
Only..
4. Moore the transponder(s) and sail the vessel to the center of the field of transponders.
8. Click on Start Tracking and wait 100 USBL fixes without any filter reset status.
The displayed position is the average position of all USBL fixes (if no reset of the filter).
For a more precise transponder position, the median of the positions of the transponders can
be estimated and entered manually in the transponder window. To calculate the median, use
the positions information given in the message starting with $PTSAG of the log repeater
document recorded during the tracking. Each transponder can be recognized by its
transponder number included in the $PTSAG message (description in the DATA STANDARD
protocol in appendix I.4).
10. Select INSTALLATION > OUTPUTS, configure an output serial or Ethernet (see section
4.4.2) and select a DP Protocol (HIPAP HPR 400, 418 fix or mobile, KONGSBERG BCD).
Click OK to validate your choice.
11. Configure the moored transponders (see section 5.3.2). In Dynamic Positioning, select a
Mode. Make sure one transponder is configured as a reference transponder (check box Use
as reference transponder activated).
12. Finish configuring the survey (see section 9.2). Run the DP survey.
9 Operating Gaps M7
Every operation starts by the initialization and the survey configuration of the system (see
section 5.1). During the survey, you can control the incoming data (see section 9.1).
Do NOT sail faster than 12 knots with the Gaps M7 head in the water. It is the mechanical
limit of the Gaps M7 unit.
The inertial sensor status light turns green at the end of the coarse alignment. You can then
start to operate with Gaps M7. The accuracy of the INS is optimal at the end of the fine
alignment. At the end of the fine alignment, the message “fine alignment” disappears from the
inertial sensor tool box.
If you turn off Gaps M7 by pressing the power switch on the Gaps box, make sure to wait at
least 20 s before turning it on again.
4. Configure (or check if it has already been done) the Gaps M7 network interface. See section
4.2.
5. If an arm or an hydrophone has been replaced, Gaps M7 antenna must be calibrated. Please
check Gaps M7 Maintenance User Guide for complete calibration procedure. In the other
case, no calibration is needed for Gaps M7 before using it. Enter the misalignments and
immersion of the antenna. See section 4.3.
6. Configure the input and output if there are new sensors during this mission. See section 4.4.
8. Configure the transponders to be positioned during the mission. See section 5.3.
11. Open the navigation window in order to check the acquired data. See section 9.3.
12. Perform the alignment of the INS (see section 9.2.1). Remain in static position or drifting (no
acceleration, no heading change) for the rough alignment (5 minutes). Perform the fine
alignment if necessary (20 minutes while performing steps or eight-shaped trajectory).
The time of last detection is displayed for each transponder in the figure above, note that the
elapsed time since this last detection is also displayed between brackets: (< 01”) for less than
one second, (~ xx”) for the number of seconds and (> 99”) for more than one minute.
Data Definition
Latitude
Geographic coordinates of the transponder
Longitude
Depth Depth computed with acoustic data and optional external sensors data
X Rel. Antenna Transponder coordinates with respect to the frame centered on the
Y Rel. Antenna antenna and to the antenna axes
X Rel. North Transponder coordinates with respect to the frame centered on the
Y Rel. North antenna and to the geographical axes
Transponder angle seen from the antenna with respect to the along
Bearing
track axe of the ship
Azimuth Transponder angle seen from the antenna with respect to the North
Vertical Angle Transponder angle seen from the antenna with respect to the vertical
Travel Time Travel time of the acoustic wave to reach the transponder
1. Even during tracking, click on options in the top right corner of the application.
ELECTRONIC:
5 V Analog Supply Internal electrical problem Switch off the rack and contact iXblue.
5 V Digital Supply Internal electrical problem Switch off the rack and contact iXblue.
12 V Analog Supply Internal electrical problem Switch off the rack and contact iXblue.
Clock Updating System time is not up to date Configure a UTC sensor.
Internal problem coming from the sig- Switch off the rack and turn it on again. If the
DSP Communication
nal processing module. problem remains, contact iXblue.
Internal problem coming from the sig- Switch off the rack and turn it on again. If the
DSP Configuration
nal processing module. problem remains, contact iXblue.
Internal problem coming from the sig- Switch off the rack and turn it on again. If the
Signal Processing
nal processing module. problem remains, contact iXblue.
DSP Overload Data processing is overloaded.
Telemetry Overflow
USBL Net. Overflow Network is overloaded Reduce number of output protocols and rates
Too many layers or depth not strictly
Profile consistency I, II Correct the velocity profile
increasing
At least 2 transponders with com-
Transp. consistency I, II Check / correct transp. parameters
mon interr. Parameters.
Interrogation Overflow Too many interr. by recurrence. Lower interrogation number per recurrence.
Transponders Overflow Too many transp. by recurrence. Lower number of transp. by recurrence.
Lower number of interrogated transp. by
Response Overflow Too many answers in a recurrence.
recurrence.
Transp./Int. Overflow Too many transp. by interrogation. Reduce number of transp. by interrogation.
Response not supported Unknown ID of acoustic response
Outputs consistency Too many output signals. Reduce number of outputs.
Sensors consistency Too many sensors in input. Reduce number of sensors in input.
LBL Base Not enough transp. for a LBL base. Add more transponders.
DP Triangulation Wrong geometry of DP transp. field. Inappropriate DP base for DP operation.
DP Reference No DP reference transponder. Add a DP reference transponder.
Timeout Synchro IN PPS Delay on incoming trigger pulse
ANTENNA:
Transponder Int. The system is not triggered. Check that the synchro is sent to the rack.
Internal problem coming from the signal Switch off the rack and turn it on again. If
Data Sampling
processing module. the problem remains, contact iXblue.
One or several detections are close to
Maximum Range Increase the interrogation rate.
the end of the acquisition period.
If message appears for a short time, it may
The system does not detect the signal be due to external environment. If problem
Channel 1/2/3/4 detection coming from the transponder on the remains continuously, there might be a
channel 1, 2, 3 or 4. problem with the antenna or with the
antenna cable. Contact iXblue.
Error occurred on one of the four chan-
Hydrophone broken or a lot of noise detec-
Channel 1/2/3/4 NIS Error nels 1, 2, 3 or 4. 5 dB detected between
ted by one hydrophone.
two channels.
Ship sails too fast, antenna mechanical
Speed Limit (12 kt) Reduce speed.
limit might be reached.
Stacking Init Discovery mode for the ping stacking
Stacking Ping stacking mode active
TRANSPONDERS:
Gaps box:
The range of the measurement is precise between 60 and 100 dB. Any noise measurement
outside this range may have degraded accuracy.
3. Click on the Hydro selection button to select which hydrophone you want to display the
frequency spectrum. You may select Hydro x, Hydro mean x or Hydro max x.
The graph of the selected data is displayed.
Set up the logging file and folder, session name, automatic log, date and hour format.
Set up the time out configuration, time stamping, segmentation options, log report.
Set up the display options and files lock. Click on OK.
Click on the Stop tracking button before any recovery operation. The USBL antenna must not
be pinging while the remote control is operating.
Gaps M7 sends commands to the transponders. Commands are configured by the input of the
following parameters:
● Bit0 and Bit1: two frequencies defining the 0 and 1 values of the coded signals
● CAF: acknowledgment signal send by the transponder
● ARM: hexadecimal value of the arming command that wakes the transponder up
● CMD: hexadecimal value of the command
● Acknowledgment Timeout: from 1 to 60 s in which the device waits for an
acknowledgment signal of the command from the transponder
Transponder Command codes can be found on the manufacturer label stuck on the transponder. These
Label
codes are in hexadecimal format. Table below links hexadecimal values to code numbers.
Table 16 - Correspondence between frequencies and hexadecimal codes
Code 0 1 2 3 4 5 6 7 8 9 A B C D E F
kHz 19.5 20 20.5 21 21.5 22 22.5 23 23.5 24 24.5 25 25.5 26 26.5 27
3. Under Codes, set ARM and CMD codes (RELEASE) in the corresponding drop-down lists.
5. Click on Send to validate your choice and to send the parameters to the USBL system.
10 Maintenance
● Connector greasing: Spray silicone grease LOCTITE 8021 must be regularly applied on
the male and female part of the SUBCONN connector.
● Dummy Plug: When the cable is not connected to Gaps M7, make sure to use the
dummy plug to protect the cable termination.
● Handling: The best way to carry Gaps M7 is to hold it by the upper disc in one hand and
one of the arms in the other hand.
● The equipment must be placed back in its transport box and stored in a dry area until it is
installed. The equipment must always be stored in its packaging. The limits of storage
temperature are the following:
1. Put the first probe of the multitester on a conductive part of the housing of the Gaps M7
antenna. It can be the transducer titanium plate or the titanium screws.
If the voltage between the Gaps M7 antenna and the hull of the ship is below 1.0 V, the system
is electrically well installed.
If the voltage between the Gaps M7 antenna and the hull of the ship is greater than 1.0 V,
corrosion will impact your system. Contact iXblue technical support.
2. Connect the new Gaps box to the Gaps M7. See section 3.3.
Maintenance level: 1
Subject: Cleaning and greasing
Periodicity: Every time before mating
SUBCONN connectors
Duration: 5 minutes
Preliminary None
Steps
1. Remove any accumulated sand or mud on the connector using spray based contact cleaner
(isopropyl alcohol).
2. Apply a layer of grease corresponding to approximately 1/3 of socket depth to the female
connector.
All sockets should be completely sealed, and transparent layer of grease left visible on the
face of the connector.
3. After greasing, fully mate the male and female connector and remove any excess grease from
the connector joint.
If one or several hydrophones have been replaced by other ones, your Gaps M7 antenna
needs to be calibrated again. Please refer to the maintenance user guide for complete details
on the calibration procedure.
ZIP the update files when mailing them to avoid file corruption caused by mail applications.
UNZIP update files received by mail before loading them into Gaps M7.
If both TQ and G4W firmware have to be updated: make sure that you download the
Gen4Ways (G4W) firmware before the PowerPC (TQ) firmware into Gaps M7.
3. In front of File, click on the Browse button and select the update file “.srec”.
4. Click on Update.
The logo flashes alternatively gray and blue. A Sendingfile label appears in the UPDATE
SYSTEM area. After a while the file is uploaded and the updating is complete.
5. Check that all the versions numbers listed above the Load File button are updated.
6. Empty the cache of your browser and reload the page before using the User Interface.
Appendices
Here is detailed a procedure to follow in order to prevent the security warning box from Java to
appear when you click on the Data Logging menu.
Table below gather reply codes from Sonardyne Wideband® 1 transponders partly compatible
with Gaps M7. Note the compatible area.
D CHORUS Codes
In order to address all operational needs without ambiguity, it is necessary to have access to a
pool of codes allowing the maximum number of transponders. With Canopus, it is possible to
address a maximum of 9 families of 15 transponders, 135 transponders.
The Chorus codes are made of:
● 144 interrogation codes (9 * 15 IIS + 9 CIS)
● 144 response codes (9 * 15 IRS + 9 CRS)
Each transponder is characterized by its family ID and its individual ID: Chorus XX.YY
● XX carries information on CIS and CRS codes
● YY carries information on IIS and IRS codes
Example All transponders from the 01 family can be interrogated on the CIS 0100 and every transponder
can answer on the CRS 0100 code.
CIS 00.00 01.00 02.00 03.00 04.00 05.00 06.00 07.00 08.00
00.01 00.02 00.03 00.04 00.05 00.06 00.07 00.08 00.09 00.10 00.11 00.12 00.13 00.14 00.15
01.01 01.02 01.03 01.04 01.05 01.06 01.07 01.08 01.09 01.10 01.11 01.12 01.13 01.14 01.15
02.01 02.02 02.03 02.04 02.05 02.06 02.07 02.08 02.09 02.10 02.11 02.12 02.13 02.14 02.15
03.01 03.02 03.03 03.04 03.05 03.06 03.07 03.08 03.09 03.10 03.11 03.12 03.13 03.14 03.15
IRS 04.01 04.02 04.03 04.04 04.05 04.06 04.07 04.08 04.09 04.10 04.11 04.12 04.13 04.14 04.15
05.01 05.02 05.03 05.04 05.05 05.06 05.07 05.08 05.09 05.10 05.11 05.12 05.13 05.14 05.15
06.01 06.02 06.03 06.04 06.05 06.06 06.07 06.08 06.09 06.10 06.11 06.12 06.13 06.14 06.15
07.01 07.02 07.03 07.04 07.05 07.06 07.07 07.08 07.09 07.10 07.11 07.12 07.13 07.14 07.15
08.01 08.02 08.03 08.04 08.05 08.06 08.07 08.08 08.09 08.10 08.11 08.12 08.13 08.14 08.15
00.01 00.02 00.03 00.04 00.05 00.06 00.07 00.08 00.09 00.10 00.11 00.12 00.13 00.14 00.15
01.01 01.02 01.03 01.04 01.05 01.06 01.07 01.08 01.09 01.10 01.11 01.12 01.13 01.14 01.15
02.01 02.02 02.03 02.04 02.05 02.06 02.07 02.08 02.09 02.10 02.11 02.12 02.13 02.14 02.15
03.01 03.02 03.03 03.04 03.05 03.06 03.07 03.08 03.09 03.10 03.11 03.12 03.13 03.14 03.15
IIS 04.01 04.02 04.03 04.04 04.05 04.06 04.07 04.08 04.09 04.10 04.11 04.12 04.13 04.14 04.15
05.01 05.02 05.03 05.04 05.05 05.06 05.07 05.08 05.09 05.10 05.11 05.12 05.13 05.14 05.15
06.01 06.02 06.03 06.04 06.05 06.06 06.07 06.08 06.09 06.10 06.11 06.12 06.13 06.14 06.15
07.01 07.02 07.03 07.04 07.05 07.06 07.07 07.08 07.09 07.10 07.11 07.12 07.13 07.14 07.15
08.01 08.02 08.03 08.04 08.05 08.06 08.07 08.08 08.09 08.10 08.11 08.12 08.13 08.14 08.15
CRS 00.00 01.00 02.00 03.00 04.00 05.00 06.00 07.00 08.00
Figure below gathers screen shots of the windows dedicated to the configuration of a
Sonardyne Wideband® 1 transponder in different software interfaces.
The interrogation and reply codes, the turn around time (TAT) and the name of the transponder
are highlighted.
A Sonardyne Wideband® 1 transponder interrogated by CIS signal, replies with IRS signal.
A Sonardyne Wideband® 1 transponder interrogated by a IIS signal, replies with CRS signal.
F Settings Examples
Distance max (m) < 682 < 1432 < 2182 < 2932 < 3682 < 4432
Gaps Recurrence 1s 2s 3s 4s 5s 6s
Distance max (m) < 682 < 1432 < 2182 < 2932 < 3682 < 4432
Gaps recurrence 1s 2s 3s 4s 5s 6s
Blanking time TP1 0.8 s 1.8 s 2.8 s 3.8 s 4.8 s 5.8 s
Blanking time TP2 0.8 s 1.8 s 2.8 s 3.8 s 4.8 s 5.8 s
Distance max (m) < 682 < 1432 < 2182 < 2932 < 3682 < 4432
Gaps recurrence 1s 2s 3s 4s 5s 6s
Blanking time TP1 1.8 s 3.8 s 5.8 s 7.8 s 9.8 s 11.8 s
Blanking time TP2 1.8 s 3.8 s 5.8 s 7.8 s 9.8 s 11.8 s
Distance max (m) < 682 < 1432 < 2182 < 2932 < 3682 < 4432
Gaps recurrence 1s 2s 3s 4s 5s 6s
Blanking time TP1 2.8 s 5.8 s 8.8 s 11.8 s 14.8 s 17.8 s
Blanking time TP2 2.8 s 5.8 s 8.8 s 11.8 s 14.8 s 17.8 s
Blanking time TP3 2.8 s 5.8 s 8.8 s 11.8 s 14.8 s 17.8 s
Blanking time TP4 2.8 s 5.8 s 8.8 s 11.8 s 14.8 s 17.8 s
Distance max (m) < 682 < 1432 < 2182 < 2932 < 3682 < 4432
Gaps recurrence 1s 2s 3s 4s 5s 6s
Blanking time TP1 0.8 s 1.8 s 2.8 s 3.8 s 4.8 s 5.8 s
Blanking time TP2 0.8 s 1.8 s 2.8 s 3.8 s 4.8 s 5.8 s
Blanking time TP3 3.8 s 7.8 s 11.8 s 15.8 s 19.8 s 23.8 s
Blanking time TP4 3.8 s 7.8 s 11.8 s 15.8 s 19.8 s 23.8 s
Here are several pieces of advice for configuring Qinsy connected to Gaps M7:
● GPS level arms must be set in Gaps M7 OR in QPS ( not both)
● Select a geodetic parameter in QPS according to your working area
● Gaps M7 is set as a POSITION NAVIGATION SYSTEM in QPS
● Add a Tp by adding a new object in QPS data base
● Associate a POSITION NAVIGATION SYSTEM to this beacon and select the pilot QPS
for Gaps M7 ( for example iXSea GAPS $PTSAG)
● The receiver number (Tp number) must be the same in the Gaps M7output string and in
QPS
H Input Protocols
H.1 GPS
Standard Input ASCII
Data received Time, latitude, longitude, altitude, hemisphere, quality factory, number of satellites, HDOP,
depth, Geoidal separation, Checksum NMEA
The ZDA is not taken any more into account when screens UTC are received. If no screen
UTC is received during 60 seconds, the ZDA can again be taken into account.
$__GGA $--GGA,hhmmss.ss,llmm.mm,a,LLLmm.mm,b,q,ss,y.y,x.x,M,g.g,M,a.a,zzzz*ck
$__ZDA $--ZDA,hhmmss.ss*ck
hhmmss.ss UTC time of the GGA fix associated with this sentence
x.x RMS value of the standard deviation on pseudo-ranges
x.x Standard deviation of semi-major axis of error ellipse
x.x Standard deviation of semi-minor axis of error ellipse
x.x Orientation of semi-major axis of error ellipse
x.x Standard deviation of latitude error, in meters
x.x Standard deviation of longitude error, in meters
x.x Standard deviation of altitude error, in meters
ck Hexadecimal checksum ('*' precedes the checksum value)
If the receiver is not tracking satellites, the time tag is based on the receiver clock. In this
case, a and b are represented by “??”. The time readings from the receiver clock are less
accurate than time readings determined from the satellite signals.
$__GLL $--GLL,llll.ll,a,yyyyy.yy,a,hhmmss.ss,A,a*ck
llll.ll Latitude
a N : North S : South
yyyyy.yy Longitude
a E : East W : West
hhmmss.ss UTC time of position
A A= data valid; V= data invalid
*ck Hexadecimal checksum ('*' precedes the checksum value)
Important notes
● Very often for TRIMBLE GPS the 1 PPS signal must be associated to the UTC telegram
and not the ZDA. If the iXblue inertial navigation system receives at the same time ZDA,
UTC and RMC time telegram it uses the telegram with the following priority: UTC, ZDA,
RMC.
● For TRIMBLE GPS, the proper settings is Time + PPS Rising while using PPS + UTC.
Avoid using ZDA only on TRIMBLE GPS.
● If no GST string is received, the quality factor is interpreted by INS as follow. At input INS
converts quality factor to standard deviation on position according to correspondence
table.
$PMEVL,XP,MEA,C,VVVVV*cc<CR><LF>
$PTLMT,T,bal,typ,ndu,duk*ck<CR><LF>
$PTLMT,R,bal,typ,nds,nqs,ndu,nqu,dsi,…,qsj,duk,…,qul,…*ck<CR><LF>
Transponder ID
bal >0 T version: Telemetry is sent when the transponder bal is interrogated
R version: bal is the ID of the transponder from which the answer carries data.
qs j {0hex , …, Fhex } Quality of data with j ∈ {1, …, nqs } 0 : worst quality, F : good quality
qul {0hex , …, Fhex } Quality of data with l ∈ {1, …, nqu} 0 : worst quality, F : good quality
Checksum The following definition stands for all protocols based on a NMEA sentence. The information is
computation
stored between the "$" and the "*" characters. The checksum is the 8-bit exclusive OR (no
start or stop bits) of all characters in the sentence, including "." delimiters, between but not
including "$" and the "*" delimiters. The hexadecimal value of the most significant 4 bits of the
result is converted to two ASCII characters (0- 9, A- F (upper case)) for transmission. The
most significant character is transmitted first.
Code example :
char checkSum(String theseChars)
{
char check = 0;
// iterate over the string, XOR each byte with total sum:
for (int c = 0; c < theseChars.length(); c++)
{
check = char(check ^ theseChars.charAt(c));
}
// return the result
return check;
}
Data integrity The telemetry signal modulation is using channel coding techniques (mainly based on
verification
checksum verification). The goal is to add redundant information to a message to compensate
for noise on the communication channel. Consequently, when the beacon receives a
telemetry message, it is able to validate or not the content of decoded information. 3 cases
can happen:
● The checksum is correct: the received information is transferred onto its output port (to
the INS or to the AUV controller) and the acoustic acknowledgment is sent to the Gaps.
● The checksum is not correct: nothing is transferred onto the output ports but the acoustic
acknowledgment is sent to the Gaps. This acknowledgment contain the information that
decoded checksum was not correct.
● The beacon never receives the telemetry: nothing happen (no transmission of information
on output port and no acknowledgment).
Return code Answer to a request provides a return code giving the request status in the first byte. In the
case of a datagram having a code = 0 for user data, the first byte for the status is not filled
because the user data uses all the available 20 bytes.
User data The du field represents actual useful data of the datagram. Below are described all these data
(20 bytes) for each type of datagram.
Code = 0
$PTLMT,T (transmit → typ = 0x0000): All 20 bytes are dedicated to the user
$PTLMT,R (reception → typ = 0x8000): All 20 bytes are dedicated to the user
Position Code = 1
$PTLMT,T → typ = 0x0004
Pressure Code = 2
$PTLMT,T → typ = 0x0008
Temperature Code = 3
$PTLMT,T → typ = 0x000C
Celerity Code = 4
$PTLMT,T → typ = 0x0010
Inclinometer Code = 5
$PTLMT,T → typ = 0x0014
Transponder Code = 6
Release
$PTLMT,T → typ = 0x0018
Ranging - Code = 9
Collect data
$PTLMT,T → typ = 0x0024
Transponder Code = 11
Status
$PTLMT,T → typ = 0x002C
$PMEVL,0,MEA,type,%e1e2e3e4e5*ck<CR> <LF>
$PMEVL,0,MEA,type,%e1e2e3e4e5<CR> <LF> (1)
$PMEVL,0,MEA,10,%01010<CR> <LF> (2)
(1) When the computation of the checksum is not possible, it is OK to omit the checksum, in
this case, the [*] must be omitted as well.
(2) Example of a datagram from a fully deployed hoisting system without checksum
Baud rate (bps) 600 1200 2400 4800 7200 9600 14400 19200 28800 38400 57600 115200
Messages Size (number of characters)
GAPS Std 764 21010 10510 5260 2630 1760 1320 880 660 440 330 220 110
GPGGA 57 1570 790 400 200 140 100 70 50 40 30 20 10
HiPap 15 420 210 110 60 40 30 20 20 10 10 10 10
Nautronix 76 2090 1050 530 270 180 140 90 70 50 40 30 20
Gyrocompass 72 1980 990 500 250 170 130 90 70 50 40 30 20
Haliburton 233 6410 3210 1610 810 540 410 270 210 140 110 70 40
Navigation 113 3110 1560 780 390 260 200 130 100 70 50 40 20
HEHDT 16 440 220 110 60 40 30 20 20 10 10 10 10
PHINS Std 498 13700 6850 3430 1720 1150 860 580 430 290 220 150 80
SIMRAD 6 170 90 50 30 20 20 10 10 10 10 10 10
Autosub 29 800 400 200 100 70 50 40 30 20 20 10 10
Post Proc. 14 390 200 100 50 40 30 20 20 10 10 10 10
Posidonia 6k 26 720 360 180 90 60 50 30 30 20 20 10 10
USBL-INS 1 26 720 360 180 90 60 50 30 30 20 20 10 10
Interr. freq. Reply TAT Blanking Pos. rate Blanking Pos. rate
code
1 beacon
Ship ID X X
Transponder ID X X X X X X X X X X
Nb of recurrences X X X X X X X
Time X X X X X X X X X X
Date X X X X X X
Latitude X X X X X X X X
Longitude X X X X X X X X
Accuracy of position X X X X X X
Depth of transponder X X X X X X X X X
Depth of sensor X X X X X X
Accuracy of depth X X
Roll X X X
Pitch X X X
Heading X X X X X X
Roll correction X X
Pitch correction X X
Heading correction X X
Speed X X X
Figure 81 - Output protocols containing the transponder position and the INS positions
I.4.1 PTSAG
Transponder Absolute Positioning Message (geographical coordinates and depth)
$PTSAG,#nnnnn,hhmmss.sss,dd,mm,yyyy,bbb,ddmm.mmmmm,h,dddmm.mmmmm,d,a,dddd.dd,a,ss
ss.ss*ck
$PTSAG,#16068,124544.449,18,12,2017,1,4305.25355,N,00631.76852,E,F,1013.10,1,9999.00*23
$PTSAG,#16071,124546.173,18,12,2017,0,4305.25123,N,00631.79102,E,F,0002.89,1,9999.00*25
● Position validity: The value represents the acoustic hydrophone validity on 4 bits (from
0000 to 1111). 0 means channel not valid and 1 hydrophone operating properly. Gaps M7
can still output valid positions even if the validity is not 1111 (three channels are enough).
All output positions are valid.
> 1111 --> F (all 4 hydrophones OK)
> 1110 --> E (hydrophone #1 NOK)
> 1101 --> D (hydrophone #2 NOK)
> 1011 --> B (hydrophone #3 NOK)
> 0111 --> 7 (hydrophone #4 NOK)
● Calculated depth / Sensor depth: The antenna knows only one depth that is the fusion
of both depths (calculated and sensor). This “optimized” depth is in the “Calculated depth”
field.
● Sensor depth: if the Acoustic Transponder has no sensor, the value is 9999.
● In case of ship, the Calculated / Sensor depth is the depth of the acoustic center
(barycenter of the hydrophones). The Gaps Depth field in the INSTALLATION >
MECHANICAL PARAMETERS tab of the Web-based user interface is the depth of the
top flange of theGaps M7 unit. The distance between the top flange and the acoustic
center is approximately 0.6 m (589.3 mm).
I.4.2 PTSAX
Transponder relative Positioning Message relative to the acoustic array (Relative coordinates
and depth)
$PTSAX,#nnnnn,hhmmss.sss,dd,mm,yyyy,bbb,xxxxx.x,yyyyy.y,p,oooo.oo,d,cccc.cc*ck
Example: $PTSAX,#16069,124544.449,18,12,2017,1,17.95,-25.58,F,1013.10,1,9999.00*27
● Position validity: The value represents the acoustic hydrophone validity on 4 bits (from
0000 to 1111). 0 means channel not valid and 1 hydrophone operating properly. Gaps M7
can still output valid positions even if the validity is not 1111 (three channels are enough).
All output positions are valid.
> 1111 --> F (all 4 hydrophones OK)
> 1110 --> E (hydrophone #1 NOK)
> 1101 --> D (hydrophone #2 NOK)
> 1011 --> B (hydrophone #3 NOK)
> 0111 --> 7 (hydrophone #4 NOK)
● Calculated depth / Sensor depth: The sensor knows only one depth that is the fusion of
both depths (Calculated and sensor). This “optimized” depth is in the “Calculated depth”
field.
● Sensor depth: if the Acoustic Transponder has no sensor, the value transmitted is 9999.
I.4.3 PTSAY
Transponder Relative Positioning Message relative to the sensor – NORTH orientation
(Relative coordinates and depth)
$PTSAY,#nnnnn,hhmmss.sss,dd,mm,yyyy,bbb,xxxxx.x,yyyyy.y,p,oooo.o,d,cccc.c*ck
Example: $PTSAY,#16057,124541.449,18,12,2017,1,8.89,-31.39,F,1013.22,1,9999.00*1E
● Position validity: The value represents the acoustic hydrophone validity on 4 bits (from
0000 to 1111). 0 means channel not valid and 1 hydrophone operating properly. Gaps M7
can still output valid positions even if the validity is not 1111 (three channels are enough).
All output positions are valid.
> 1111 --> F (all 4 hydrophones OK)
> 1110 --> E (hydrophone #1 NOK)
> 1101 --> D (hydrophone #2 NOK)
> 1011 --> B (hydrophone #3 NOK)
> 0111 --> 7 (hydrophone #4 NOK)
● Calculated depth / Sensor depth: The sensor knows only one depth that is the fusion of
both depths (Calculated and sensor). This “optimized” depth is in the “Calculated depth”
field.
● Sensor depth: if the Acoustic Transponder has no sensor, the value transmitted is 9999.
I.4.4 PTSAZ
$PTSAZ,#nnnnn,hhmmss.sss,dd,mm,yyyy,#PTSAW,r,c.ccc,r.rrr,t.ttt,L.LLLL,l.llll,x.xxx,y.yyy,z.zzz*ck
I.4.5 PTSAH
This message is used to transmit the heading to applications such as Delph RoadMap. This
message is sent at the same rate as the PTSAG ship.
$PTSAH,0,hhh.hh,ss.ss*ck
Example: $PTSAH,0,38.22,1.77*78
I.4.6 PIXOG
$PIXOG,CONFIG,TIME,hhmmss.sss,dd,mm,yyyy*ck
$PIXOG,CONFIG,TIME USBL
hhmmss.sss Interrogation time
dd Day
mm Month
yyyy Year
*ck Checksum in hexadecimal ('*' precedes the checksum value)
I.4.7 PTSAQ
Description Ellipse error of USBL positions
$PTSAQ,hhmmss.sss,dd,mm,yyyy,bbb,XX.XX,YY.YY,AAA.A,ZZ.ZZ*ck
Example:
$PTSAH,0,46.967,0.000*78
$PTSAG,#01396,000352.028,01,01,1970,0,4819.27243,N,06725.63359,E,F,0000.6,1,9999.0*22
$PTSAZ,#01397,000352.029000,1,1,1970,#PTSAW,R,-
0.8197,0.0122,0.0003,0.84336416,1.17682711,0.03,0.0017,0.0017,1*52
$PTSAG,#01398,000352.029,01,01,1970,1,4819.34848,N,06725.62896,E,F,0101.1,1,9999.0*21
$PTSAX,#01399,000352.029,01,01,1970,1,100.37,99.12,F,0101.1,1,9999.0*30
$PTSAY,#01400,000352.029,01,01,1970,1,140.95,-5.72,F,0101.1,1,9999.0*24
$PTSAQ,000352.029,01,01,1970,1,1.40,5.72,192.5,1.54*7E
I.4.8 PIXSE,LABEL
$PIXSE,LABEL,aa,aaaa,c--c,aaaa,c--c,....*hh<CR><LF>
LABEL, String ID
aaaa, ID 1 Integer
aaaa, ID 2 Integer
...
Example:
$PTSAX,01,00100,00199,F,0301,1,9999*16
$PTSAX,01,00100,00199,F,0301,1,9999*16
$PTSAX,04,-0010,00004,F,1135,1,9999*0F
$PTSAX,04,-0010,00004,F,1135,1,9999*0F
● Position validity: The value represents the acoustic hydrophone validity on 4 bits (from
0000 to 1111). 0 means channel not valid and 1 hydrophone operating properly. Gaps M7
can still output valid positions even if the validity is not 1111 (three channels are enough).
All output positions are valid.
> 1111 --> F (all 4 hydrophones OK)
> 1110 --> E (hydrophone #1 NOK)
> 1101 --> D (hydrophone #2 NOK)
> 1011 --> B (hydrophone #3 NOK)
> 0111 --> 7 (hydrophone #4 NOK)
● Calculated depth / Sensor depth: The Gaps M7 knows only one depth that is the fusion
of both depths (Calculated and sensor). This “optimized” depth is in the “Calculated depth”
field.
● Sensor depth: if the Acoustic Transponder has no sensor, the value is 9999.
● In case of ship, the four last fields are set to zero.
PTSAX Transponder relative Positioning Message relative to Gaps array - Gaps orientation (Relative
coordinates and depth).
$PTSAX,#nnnnn,hhmmss.sss,dd,mm,yyyy,bbb,xxxxx.x,yyyyy.y,p,oooo.oo,d,cccc.cc*ck
Example: $PTSAX,#16069,124544.449,18,12,2017,1,17.95,-25.58,F,1013.10,1,9999.00*27
● Position validity: The value represents the acoustic hydrophone validity on 4 bits (from
0000 to 1111). 0 means channel not valid and 1 hydrophone operating properly. Gaps M7
can still output valid positions even if the validity is not 1111 (three channels are enough).
All output positions are valid.
> 1111 --> F (all 4 hydrophones OK)
> 1110 --> E (hydrophone #1 NOK)
> 1101 --> D (hydrophone #2 NOK)
> 1011 --> B (hydrophone #3 NOK)
> 0111 --> 7 (hydrophone #4 NOK)
● Calculated depth / Sensor depth: The Gaps know only one depth that is the fusion of
both depths (calculated and sensor). This “optimized” depth is in the “Calculated depth”
field.
● Sensor depth: if the Acoustic Transponder has no sensor, the value transmitted is 9999.
PTSAY Transponder Relative Positioning Message relative to Gaps – NORTH orientation (Relative
coordinates and depth)
$PTSAY,#nnnnn,hhmmss.sss,dd,mm,yyyy,bbb,xxxxx.x,yyyyy.y,p,oooo.oo,d,cccc.cc*ck
Example: $PTSAY,#16057,124541.449,18,12,2017,1,8.89,-31.39,F,1013.22,1,9999.00*1E
● Position validity: The value represents the acoustic hydrophone validity on 4 bits (from
0000 to 1111). 0 means channel not valid and 1 hydrophone operating properly. Gaps M7
can still output valid positions even if the validity is not 1111 (three channels are enough).
All output positions are valid.
> 1111 --> F (all 4 hydrophones OK)
> 1110 --> E (hydrophone #1 NOK)
> 1101 --> D (hydrophone #2 NOK)
> 1011 --> B (hydrophone #3 NOK)
> 0111 --> 7 (hydrophone #4 NOK)
● Calculated depth / Sensor depth: The Gaps M7 knows only one depth that is the fusion
of both depths (calculated and sensor). This “optimized” depth is in the “Calculated depth”
field.
● Sensor depth: if the Acoustic Transponder has no sensor, the value transmitted is 9999.
PTSAX Transponder relative Positioning Message relative to Gaps array - Gaps orientation (Relative
coordinates and depth).
PTSAY Transponder Relative Positioning Message relative to Gaps – NORTH orientation (Relative
coordinates and depth)
This output protocol only includes a GPGGA string corresponding to the position of the
transponder with ID = 1.
The difference between the mobile and fixed protocols is made in the Byte 3 Bit 5. The bit is
equal to 1 in the mobile case and 0 in the fixed case.
Message
Byte 0 0xDF Start of message
Byte 1 0x01 Head byte
1- SSBL position
Transponder position message: the frame contains 32 bytes in binary format. This message is
sent every 20 seconds and if any change in the sequence.
Message
1 DF 1: SOT
2: Head byte.
2 01
1 - SSBL position
5: TP. inf.
0 - Transponder
1 - Depth TP Optional Data 1
2 - Inclinometer TP Optional Data 1&2
3 - Diff.inc.TP Optional Data 1&2
5 02 4 - Compass TP Optional Data 1
5 - Acoustic control transponder
6 - Beacon
7 - Depth beacon
10 - Responder driver 1
13 - Responder driver 4
6 01 6: TP ID
7 33 TP from 1 to 299
8 00 7: X POS RAW
11 D0 8: Y POS RAW
14 01 9: Z POS RAW
16 45 1234.5 m depth.
17 35 10: HEADING
32 FF 16: EOR
1 Slave = 1 only when Slave Transmit enabled, otherwise no data from Slave
Example: Transponder position relative to vessel: X. 123.4m, Y. -567.8m
1 DF 1: SOT
2: Head byte.
2 02
2 - LBL position
5: TP. inf.
0 - Position of Vessel
1 - Position of ROV 1
::
5 15 16 - Position of ROV 16
17 - Position of Relay 1
18 - Position of Relay 2
19 - Position of Relay 3
20 - Position of Relay 4
6: TP. array
1 - Array 1
6 01
::
4 - Array 4
10 34
15 87
19 45 1234.5 m
20 05 10: HEADING
32 FF 17: EOR
2 Slave = 1 only when Slave Transmit enabled, otherwise no data from Slave
The local coordinates are relative to the center (i.e. the origin) of the LBL array. For vessels,
the position is normally the position of the CG. For ROVs, the position is normally the position
of the transducer. Example: N. 1234.56 m , E. -987.65 m
TP in sequence telegram
To be sent every 20 s, and if any changes in the sequence. List of active transponders to be
packed. Tp ID 300 is used to identify an LBL position. HAIN positions are not included in the
transponders in sequence telegram.
Example: TP 001/103/ 207/133/300 in use.
1 DF 1: SOT
2: Head byte.
2 03
3 - TP in sequence telegram
3 05 3: No of TP in use.
4 00 4: TP 1.
5 01 TP 1
6 01 5: TP 2.
7 03 TP 103
8 02 6: TP 3.
9 07 TP 207
10 01 7: TP 4.
11 33 TP 133
12 03 8: TP 5.
13 00 TP 300
14 00
9: TP 6.
15 00
16 00
10: TP 7.
17 00
18 00
11: TP 8.
19 00
20 00
12: TP 9.
21 00
22 00
13: TP 10.
23 00
24 00
14: TP 11.
25 00
26 00
15: TP 12.
27 00
28 00
16: TP 13.
29 00
32 FF 18: EOR.
Latitude (deg)
3, 4, 5, 6 LLLLLLLLhex 32 180/232 -90° 90x(1-232)°
(Two-complement coded)
ZZZZZhex
(8+8+4 bits:
0m +10485,75 m
- byte11, 20 Z(m), immersion 0.01 m
(0000hex ) (FFFFFhex )
- byte12,
- bits 3 to 0 of 13)
Bit 4 1 Reserved
11, 12 Major axe XY: long axe (in m) of the error ellipse representing the
standard deviation on the position in the XY plane
13 000: 0 m < standard deviation < 0,5 m
001: 0,5 m < standard deviation < 1,5 m
010: 1,5 m < standard deviation < 3 m
Bits 7 to 5 3
011: 3 m < standard deviation < 6 m
100: 6 m < standard deviation < 12 m
101: 12 m < standard deviation < 25 m
110: 25 m < standard deviation < 50 m
111: standard deviation > 50 m
Bit 0 1 Reserved
Minor axe XY: small axe (in m) of the error ellipse representing the
standard deviation of the position in the XY plane
000: 0 m < standard deviation < 0,5 m
001: 0,5 m < standard deviation < 1,5 m
010: 1,5 m < standard deviation < 3 m
Bits 3 to 1 3
011: 3 m < standard deviation < 6 m
14
100: 6 m < standard deviation < 12 m
101: 12 m < standard deviation < 25 m
110: 25 m < standard deviation < 50 m
111: standard deviation > 50 m
Bit 0 1 Reserved
Bits 7 to 4 4 Reserved
16 PPhex 8 Reserved
Checksum
21 SShex 8
exclusive OR by byte for the whole 20 first bytes thus header included.
Immersion The immersion corresponds to the mobile depth with respect to the mean sea level (thus
definition
heave corrected). This data is coherent with the one that would be given by a depth sensor on
the underwater mobile. But it does not allow to deduce the absolute position as there is no
compensation for tide.
Field 1 Transponder ID
Field 7 Angle between the North and the major axe of the Resolution: 180/24
XY error ellipse Domain: [0 .. 15/16 x 180]
Field 8 Standard deviation of the Z(m) position 0: 0 m < standard deviation < 0,5 m
1: 0,5 m < standard deviation < 1,5 m
2: 1,5 m < standard deviation < 3 m
3: 3 m < standard deviation < 6 m
4: 6 m < standard deviation < 12 m
5: 12 m < standard deviation < 25 m
6: 25 m < standard deviation < 50 m
7: standard deviation > 50 m
Immersion The immersion corresponds to the mobile depth with respect to the mean sea level (thus
definition
heave corrected). This data is coherent with the one that would be given by a depth sensor on
the underwater mobile. But it does not allow to deduce the absolute position as there is no
compensation for tide.
Immersion = Measured depth (by the USBL acoustic array) - Heave + USBL immersion
Field 4 Status 0
Message <Sync><F1><F2>…..<F8><Ch1Ch2>
Data Field 2
Transponder latitude +/-232 = +/-Pi signed 32 bits
Bytes 2 to 5
Data Field 3
Transponder longitude +/-232 = +/-Pi signed 32 bits
Bytes 6 to 9
Data Field 5
Latitude standard deviation IEEE floating point format , meters
Bytes 12 to 17
Data Field 6
Longitude standard deviation IEEE floating point format , meters
Bytes 18 to 21
Data Field 7
Depth standard deviation IEEE floating point format , meters
Bytes 22 to 25
Data Field 8
Delay IEEE floating point format , seconds
Bytes 26 to 29
I.18 USBL_POSTPRO
Terminology ● CRP: Common Reference Point
● BRD: Acoustic Antenna Mounting Flange
● CAC: Acoustic center of the acoustic antenna
● RIXI: iXblue Reference Frame
> X+: towards the bow (axis of the ship)
> Y+: towards starboard
> Z+: upward
> Roll+: port goes down
> Pitch+: bow goes down
> Heading+: Bow goes to port.
● RANT: Acoustic antenna reference frame
> X+ towards H1
> Y+ towards H4
> Z+ downwards
● RIXI o CRP : iXblue reference frame centered on common reference point
● RANT o BRD : Acoustic antenna reference frame centered on the center of the mounting
flange
● RANT o Hx : Acoustic antenna reference frame centered on hydrophone x
Overview USBL_POSTPRO protocol comprises all necessary data for post processing:
● Configuration data (supposed invariant)
> System characteristics
> Beacon characteristics
● Operational environment data
> System Installation
> Sound speed profile
● Input data
> Time
> Raw navigation data
> Detection characteristics
> Ancillary data
Protocol The protocol comprises binary datagrams produced by the equipment. It contains the
Structure
sufficient and necessary data for playback of the applied real time processing.
The datagrams comprise :
● Header for identification and characterization
● Main body of data described in the header
● Checksum (bytes sum)
Type Description
● 16 and 32 bytes encoded data are described with the Big endian convention (strong
weight byte sent first)
● NaN have a value of Ox7FC00000
System Identification: This datagram gathers the configuration elements of the system.
0 Unknown
1 Gaps - TITAN - CL
2 Gaps - CARBON - ML
Equipment Type ushort
Identification 3 Gaps - TITAN - ML
4 U-BOX - FLUSH
5 U-BOX - CAGE
Checksum ushort
System Characteristics: This datagram gathers the identification elements of the system.
Checksum ushort
Transponders Characteristics
Transponder ID short
-1 Generic
0 RT8 MF
1 Monotonal MF
2 RT9 MF
3 MT9 MF
Transponder type short 4 BT8 MF
5 RT9 BF
6 RAMSES 6000 BF
7 ET9 BF
8 RTT4 BF
9 RT8 BF
0 None
Transponder Operational behavior byte 1 Fixed transponder
2 Mobile transponder
0 Transponder
1 Primary responder
Interrogation mode byte
2 Spontaneous (pinger)
3 Secondary Responder
0 No known depth
1 Pressure sensor
Depth management byte 2 Not used
3 Acoustic telemetry
4 Configuration depth
Checksum ushort
Checksum ushort
System Installation
This protocol gathers all the elements describing the system geometry.
Checksum ushort
Checksum ushort
Transponder ID short
H1 float s interrogation
H2 float s interrogation
Arrival time
H3 float s interrogation
H4 float s interrogation
H1 float radian
H2 float radian
Phase
H3 float radian
Acoustic H4 float radian
detection
(49) H1 float dB
Noise
H2 float dB
Signal
H3 float dB
Ratio
H4 float dB
Checksum ushort
Transponder ID short
Checksum ushort
I.19 PIFM-POPSN
$PIFM,POPSN,JJ/MM/AAAA,HH:MM:SS,DDD,ddd.dd,±vv.vv,±vv.vv,CCCC,nn,
JJ/MM/AAAA,HH:MM:SS.DDD,s,dd,mm.mmmm,s,ddd,mm.mmmm,mmmm,c,c, mmmm,
[CR][LF]
Header ID $PIFM,POPSN, 12
Date JJ/MM/AAAA, 11
Time HH:MM:SS,DDD, 13
* ID: transponder ID in 4 characters (example for transponder 1: « 0001 », for transponder 26: «
0026 »)
The output data protocols that contain the INS position are to be found in Phins User Guide.
Here is the list of the protocols output by Gaps and understandable by Phins: