Scribd
Upload
272 views7 pages

NaviPac and IXBLUE GAPS

Uploaded by

ozed99
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
272 views7 pages

NaviPac and IXBLUE GAPS

Uploaded by

ozed99
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 7

½

NAVIPAC
AND IXBLUE GAPS DATA FORMAT

Last update: 19/03/2020


Version: 4.2
Contents

1 General ........................................................................................................................ 3

2 Data input .................................................................................................................... 3

3 Data filtering................................................................................................................ 6

4 Version descriptions .................................................................................................. 7

Page 2 of 7
1 General
NaviPac supports the IXBLUE GAPS Standard exchange format.
The GAPS Standard protocol contains the position of the transponder(s).

$PTSAG,12,132810.234,71,03,2006,11,5650.55281,N,0900.01200,E,B,0123.4,1,0122.3*<c
heck sum>

See GAPS User Manual for details on the format.

2 Data input
We have modified the ordinary Remote dynamic objects x to support the $PTSAG.

The GAPS can be configured by adding a Remote dynamic object driver to the vessel.
Then add beacons by clicking on the Plus sign on the vessels Remote dynamic object
and assign to another vehicle.

Figure 1 Adding a beacon

NaviPac and IXBLUE GAPS.docx


Page 3 of 7
Last update: 19/3/2020
Figure 2 Dynamic Positioning: Remote dynamic objects x driver

The driver will analyse the input automatic and select the format, as it now supports:
1) NaviPac
2) Winfrog
3) Pseudo NMEA
4) Expanded NaviPac
5) NaviPac SCS France
6) Apache $SFPOS
7) NaviPac Plus
8) IMCA Standard
9) Thales Tracks $PRPS,POSN
10) Century Subsea Spar
11) iXBlue GAPS ($PTSAG Message)
12) IxBlue Phins ($PIXSE,POSITI)
13) Acergy $ACGDAT
14) Kongsberg HUGIN AUV data ($PKMSLLD)

Page 4 of 7
The unit may read one or more inputs based on the TP code (between 1 and 128)

Figure 3 Driver1

The objects will be treated as any other object in NaviPac.

Figure 4 NaviPac Object Monitor

The TUG1 in the above dump is positioned via GAPS. Please note that the following
information is taken from the input

Delta X - The data latency (based on computer clock vs. time in telegram)
Delta Y- The Position Validity (0 – 15)
Delta Z - The Sensor Depth
Height - The Calculated Depth

Please note that the calculation of the latency/age only will work if the two systems are
synchronized to the same clock. The timestamp in the GAPS telegram are assumed to be
UTC.

NaviPac and IXBLUE GAPS.docx


Page 5 of 7
Last update: 19/3/2020
Figure 5 NaviPac Helmsman’s display with TUG1 positioned by GAPS

3 Data filtering
If the GAPS unit outputs more than the one interesting telegram – e.g. also some of the
other GAPS messages, then you must add a filter in the NaviPac system. This is done in
NaviPac Remote object driver properties.

Page 6 of 7
Figure 6 Remote dynamic object properties view

Go to Properties, scroll down to the String details section and modify the Driver Type to
NMEA: Prefixed ASCII String with 'cr' +'lf'.
This allows you to enter a String prefix, e.g. $PTSAG. If set, then only strings starting with
the prefix are feed into NaviPac. All others will be rejected.

4 Version descriptions
Version Date Author Description
3.9 01-01-2000 OKR Initial document

4.2 05-03-2020 ROEL Reviewed and moved to new EIVA template

NaviPac and IXBLUE GAPS.docx


Page 7 of 7
Last update: 19/3/2020

You might also like