Skip to main content
Skip table of contents

AutoPilot (with turning track) - NMEA APB - 15

Description


Active driver with user interface to communicate with your Auto Pilot System on board.

  1. Main purpose of this driver is to continuously send track offset information to the Auto Pilot so the unit knows what course to steer to stay on the survey line.
  2. Secondly the user has the option to use a turning track during a line-change: a smooth track can be calculated to steer to the SOL of the next line.
  3. And thirdly in the so-called Swath Coverage Mode you can direct the vessel to steer automatically, based on the previous swath coverage of your multibeam system, which means surveying an area without line planning.

Driver Information


Click here to expand driver information...
Driver AutoPilot (with turning track)Interface TypeSerial / Network (UDP/TCP)Driver Class TypeOutput
UTC Driver (question) NoInput / OutputOutput ExecutableDrvOutAutoPilotUI.exe

DrvOutAutoPilotUIUDP.exe
DrvOutAutoPilotUITCP.exe

Related Systems
Related Pages

Output Formats

The following output formats are supported:

- NMEA APA format - Autopilot Sentence "A"
- NMEA APB format - Autopilot Sentence "B"
- NMEA RMB - Recommended Minimum Nav Info
- NMEA XTE format - Cross track Error, Measured
- Euro500 format
- RobNav-AP9 format
- RobTrack / STS500 format
- Kongsberg TNT ($PRTNT,X)

 NMEA output formats can be combined with an additional NMEA RMB/RMC output format in order to support autopilot units requiring this additional information.


Click here for all format descriptions...

NMEA APA - Autopilot Sentence "A"

Encoding Notes

  • The NMEA Talker (1st field), normally consisting of two characters, should be entered once under Settings in the driver's dialog.
  • The outputted cross track error (4th field) can be multiplied with a scale factor: this XTE Scale factor is by default 1, but may be changed in the Settings pane.
  • The unit for the outputted cross track error value (XTE) is default set to Meters ('M') but can be changed under Settings in the driver's dialog.
Format
$--APA,A,A,x.x,a,N,A,A,x.x,a,c--c[*hh]<CR><LF>

Format Description

 Field

Format

Description

1

--

NMEA Talker identifier

2

A

Status, 'A' = data valid, 'V' = reliable fix not available

3

A

Status, always 'A'

4

x.x

Magnitude for cross track error (XTE). Always a positive value

5

a

Direction to steer 'L' = Left, 'R' = Right

6

N

XTE units, 'N' = Nautical miles, 'M' = Meters, 'f' = International Feet

7

A

Status: 'A' = Arrival circle entered, always set to 'V'

8

A

Status, perpendicular passed at way point, always set to 'V' when on the line, will be 'A' when after the line/route

9

x.x

Bearing origin to waypoint

(See also Advanced Setting 'Smooth Bearing Output')

10

a

Magnetic / True, 'M' or 'T'. Always set to True

11

c---c

Destination waypoint ID, set to main line ID

12

*hh

Checksum, controlled by Drivers.io command line


<CRLF>

Carriage Return and Linefeed character

Format Example
$GPAPA,A,A,8.30,L,M,V,V,11.7,T,Turning Track to Ijmuiden 1*1B
$GPAPA,A,A,8.99,L,M,V,V,11.7,T,Turning Track to Ijmuiden 1*18
$GPAPA,A,A,9.78,L,M,V,V,11.7,T,Turning Track to Ijmuiden 1*16
$GPAPA,A,A,10.35,L,M,V,V,11.7,T,Turning Track to Ijmuiden 1*27
$GPAPA,A,A,11.04,L,M,V,V,11.7,T,Turning Track to Ijmuiden 1*24
$GPAPA,A,A,11.65,L,M,V,V,11.7,T,Turning Track to Ijmuiden 1*23
$GPAPA,A,A,12.44,L,M,V,V,11.7,T,Turning Track to Ijmuiden 1*23
$GPAPA,A,A,13.09,L,M,V,V,11.7,T,Turning Track to Ijmuiden 1*2B

NMEA APB - Autopilot Sentence "B"

Encoding Notes

  • The NMEA Talker, normally consisting of two characters, should be entered once under Settings in the driver's dialog.
  • The cross track error being output (4th field) can be multiplied with a scale factor: this XTE Scalefactor is by default 1, but may be changed in the Settings pane.
  • The unit for the output cross track error value (XTE) is default set the Meters ('M') but can be changed under Settings in the driver's dialog.
  • Field #14 (Heading-to-steer to destination waypoint) is always equal to field #12 (Bearing. Present position to destination).
    An advanced user may change field #14 in order to output a so-called corrected heading-to-steer: relative to the bearing of present position to destination.
    I.e when your vessel is heading straight to the destination waypoint, the value in field #14 will be zero.
    The formula used is then: field #12 minus the vessel heading.
    In order to change this field #14, open the registry editor (Start, Run..., regedit) and change registry key HKEY_CURRENT_USER\Software\QPS\QINSy\8.0\Drivers\DrvOutAutoPilotUI\<Driver's Name>Settings\NMEA_HeadingToSteerCorrected from 0 to 1.


Format
$--APB,A,A,x.x,a,N,A,A,x.x,a,c--c,x.x,a,x.x,a,a[*hh]<CR><LF>

Format Description

 Field

Format

Description

1

--

NMEA Talker identifier
(See comment under Encoding Notes)

2

A

Status, 'A' = data valid, 'V' = reliable fix not available

3

A

Status, always 'A'

4

x.x

Magnitude for cross track error (XTE). Always a positive value

5

a

Direction to steer 'L' = Left, 'R' = Right

6

N

XTE units, 'N' = Nautical miles, 'M' = Meters, 'f' = International Feet
(See comment under Encoding Notes)

7

A

Status: 'A' = Arrival circle entered, always set to 'V'

8

A

Status, perpendicular passed at way point, always set to 'V' when on the line, will be 'A' when after the line/route

9

x.x

Bearing origin to waypoint

(See also Advanced Setting 'Smooth Bearing Output')

10

a

Magnetic / True, 'M' or 'T'. Always set to True

11

c---c

Destination waypoint ID, set to main line ID

12

x.x

Bearing. Present position to destination

13

a

Magnetic / True, 'M' or 'T'. Always set to True

14

x.x

Heading-to-steer to destination waypoint
(See also comment under Encoding Notes)

15

a

Magnetic / True, 'M' or 'T'. Always set to True

16

a

Mode indicator ('D' when the position used for the XTE is valid, otherwise 'E')

17

*hh

Checksum, controlled by Drivers.io command line


<CRLF>

Carriage Return and Linefeed character

Format Example
$GPAPB,A,A,0.02617,R,N,V,V,210.0,T,Vlissingen,236.6,T,236.6,T,D*5D<CR><LF>
$GPAPB,A,A,0.02620,R,N,V,V,210.0,T,Vlissingen,236.7,T,236.7,T,D*59<CR><LF>
$GPAPB,A,A,0.02003,R,N,V,V,210.0,T,Vlissingen,227.6,T,227.6,T,D*5E<CR><LF>
$GPAPB,A,A,0.00536,R,N,V,V,210.0,T,Vlissingen,213.4,T,213.4,T,D*5F<CR><LF>

NMEA RMB - Recommended Minimum Navigation Info

Encoding Notes

  • The NMEA Talker, normally consisting of two characters, should be entered once under Settings in the driver's dialog.


Format
$--RMB,A,x.x,a,c--c,c--c,llll.ll,a,yyyyy.yy,a,x.x,x.x,x.x,A,A[*hh]<CR><LF>

Format Description

 Field

Format

Description

Comments

1

--

NMEA Talker identifier

User-defined setting

2

A

Status, 'A' = data valid, 'V' = Navigation warning

Always 'A'
3x.xCross Track error - Meters, Nautical miles or FootUnit depends on the selected unit
4aDirection to Steer, 'L'eft or 'R'ight
5c--cTO Waypoint IDNot Used - Field empty
6c--cFROM Waypoint IDNot Used - Field empty
7llll.llDestination Waypoint LatitudeEOL or EOS co-ordinate
8aN or S
9yyyyy.yyDestination Waypoint LongitudeEOL or EOS co-ordinate
10aE or W
11x.xRange to destination - Meters, Nautical miles or FootUnit depends on the selected unit
12x.xBearing to destination in degrees - True
13x.xVelocityNot Used - Field empty
14AArrival StatusAlways 'V'
15APosition Mode - 'D' or 'E''E' when node status becomes predicted

16

*hh

Checksum, controlled by Drivers.io command line



<CRLF>

Carriage Return and Linefeed character


Format Example
$GPRMB,A,47.957,R,,,5222.5927270,N,00502.5584527,E,298.5,280.9,,V,D*63
$GPRMB,A,48.317,R,,,5222.5927270,N,00502.5584527,E,295.1,281.0,,V,D*63
$GPRMB,A,48.045,R,,,5222.5927270,N,00502.5584527,E,291.6,281.1,,V,D*65
$GPRMB,A,47.982,R,,,5222.5927270,N,00502.5584527,E,287.8,281.2,,V,D*62
$GPRMB,A,48.394,R,,,5222.5927270,N,00502.5584527,E,284.4,281.4,,V,D*69
$GPRMB,A,48.357,R,,,5222.5927270,N,00502.5584527,E,280.8,281.5,,V,D*6F
$GPRMB,A,48.570,R,,,5222.5927270,N,00502.5584527,E,277.4,281.7,,V,D*6A

NMEA RMC - Recommended Minimum Specific GNSS Data

Encoding Notes

  • The NMEA Talker, normally consisting of two characters, should be entered once under Settings in the driver's dialog.


Format
$--RMC,hhmmss.ss,A,llll.ll,a,yyyyy.yy,a,x.x,x.x,ddmmyy,x.x,a,a[*hh]<CR><LF>

Format Description

 Field

Format

Description


1

--

NMEA Talker identifier


2hhmmss.ssTime (UTC)

3

A

Status, 'A' = data valid, 'V' = Navigation warning

Always 'A'. (No output when position is not okay)
4
Latitude
5
N or S
6
Longitude
7
E or W
8
SOGAlways in knots
9
COGAlways true
10ddmmyyDate
11
Magnetic variationAlways empty
12aE or WAlways empty
13aPosition system mode indicator'D' when position is normal or 'E' when position is predicted

14

hh

Checksum, controlled by Drivers.io command line



<CRLF>

Carriage Return and Linefeed character


Format Example
$GPRMC,163354.17,A,5222.510883,N,00502.880538,E,4.5,271.1,130319,,,D*5F
$GPRMC,163355.67,A,5222.511045,N,00502.877294,E,4.5,272.3,130319,,,D*52
$GPRMC,163357.18,A,5222.511103,N,00502.874373,E,4.4,271.0,130319,,,D*51
$GPRMC,163357.18,A,5222.511103,N,00502.874373,E,4.4,271.0,130319,,,D*51
$GPRMC,163358.68,A,5222.510967,N,00502.871253,E,4.4,270.4,130319,,,D*51
$GPRMC,163400.19,A,5222.511086,N,00502.867984,E,4.4,272.6,130319,,,D*5C
$GPRMC,163400.19,A,5222.511086,N,00502.867984,E,4.4,272.6,130319,,,D*5C
$GPRMC,163401.70,A,5222.511166,N,00502.864900,E,4.4,272.1,130319,,,D*55
$GPRMC,163403.23,A,5222.511192,N,00502.861680,E,4.6,271.6,130319,,,D*5E
$GPRMC,163403.23,A,5222.511192,N,00502.861680,E,4.6,271.6,130319,,,D*5E
$GPRMC,163404.73,A,5222.511057,N,00502.858474,E,4.6,271.6,130319,,,D*57

NMEA XTE - Cross-Track Error, Measured

Encoding Notes

  • The NMEA Talker, normally consisting of two characters, should be entered once under Settings in the driver's dialog.
  • The outputted cross track error (4th field) can be multiplied with a scale factor: this XTE Scalefactor is by default 1, but may be changed in the Settings pane.
  • The unit for the outputted cross track error value (XTE) is default set to Meters ('M') but can be changed under Settings in the driver's dialog.


Format
$--XTE,A,A,x.x,a,N[*hh]<CR><LF>

Format Description

 Field

Format

Description

1

--

NMEA Talker identifier

2

A

Status, 'A' = data valid, 'V' = reliable fix not available

3

A

Status, always 'A'

4

x.x

Magnitude for cross track error (XTE). Always a positive value

5

a

Direction to steer 'L' = Left, 'R' = Right

6

N

XTE units, 'N' = Nautical miles, 'M' = Meters, 'f' = International Feet

7

a

Mode indicator ('D' when the position used for the XTE is valid, otherwise 'E')

8

hh

Checksum, controlled by Drivers.io command line


<CRLF>

Carriage Return and Linefeed character

Format Example
$GPXTE,A,A,2.43,R,M,D*1E
$GPXTE,A,A,2.04,R,M,D*1D
$GPXTE,A,A,1.58,R,M,D*17
$GPXTE,A,A,1.12,R,M,D*19
$GPXTE,A,A,0.73,R,M,D*1F
$GPXTE,A,A,0.16,R,M,D*1C
$GPXTE,A,A,0.16,L,M,D*02
$GPXTE,A,A,0.69,L,M,D*0A
$GPXTE,A,A,1.03,L,M,D*07
$GPXTE,A,A,1.45,L,M,D*05
$GPXTE,A,A,1.94,L,M,D*09
$GPXTE,A,A,2.40,L,M,D*03
$GPXTE,A,A,3.00,L,M,D*06

Euro500

Encoding Notes

  • The outputted offtrack will be the calculated offtrack of the selected node from the Controller's Mainline MINUS the user-defined Track Offset (default zero).
  • The outputted offtrack is rounded to the nearest 0.1m.
  • Maximum offset should be less than 499.95m (which equals 99990.00 mV).


Format
$1AO+xxxxx.xx<CR><LF>

Format Description

 Field

Format

Description

Values, Range, Units


$1AO

Is always the same. (Note that O is not the zero character)



+

Sign

+ means starboard,
- means port of the line.


xxxxx.xx

Means a multiple of 200mV, where 1m equals 200mV



<CRLF>

Means the Carriage Return and Line Feed character


Format Example
$1AO+00020.00<CR><LF>         means offset of  +0.1m
$1AO+01000.00<CR><LF>         means offset of  +5.0m
$1AO-02000.00<CR><LF>         means offset of -10.0m

RobNav AP9

Encoding Notes

  • No special encoding notes


Format
<STX><TrackReference><CrossTrackError><TrackSpeed><Checksum><ETX><CR><LF>

Format Description

 Field

Format

Description

Values, Range, Units


<STX>

Start of Text character

c         (ASCII 2)


Track Reference

Track Bearing

dddd   units of 0.1°


Cross Track Error

Distance across. +ve means vessel should steer to stbd, -ve means vessel should steer to port.

sdddd units of 0.1m


Track Speed

Code 30H means no speed information available

ddd     units of 0.01m/sec


Checksum

Sum of all characters between STX and ETX

c         1 byte

        

<ETX>

End of Text character

c         (ASCII 3)


<CR><LF>

means the Carriage Return and Linefeed character

cc       (ASCII 13 and 10)

Format Example
<STX>1800-1803091\<ETX><CR><LF>
<STX>1800-1840090\<ETX><CR><LF>
<STX>1800-1878097n<ETX><CR><LF>
<STX>1800-1902102U<ETX><CR><LF>

RobTrack STS500

Encoding Notes

  • The track offset (6th field) and the maximum allowed turn-rate (7th field) are user-defined values: these are not used for the cross track error calculation, but are copied as-is into the data-string.


Format
$DNRTR,r.r,x.x,v.v,a.a,o.o,t.t*hh<CR><LF>

Format Description

Field

Format

Description

Values, Range, Units

1

$DNRTR

header


2

r.r

Track ref. (direction of track) Line Heading

Unit: True heading in degrees

3

x.x

Cross track error (distance across)

Positive when heading must change to port to get closer to track  E.g. +12.2 -> Vessel must steer 12.2 to port. Unit: meters

4

v.v

Velocity along track

Positive when vessel SMG is in the track direction. Unit: meters / second

5

a.a

Velocity across

Positive when vessel moves to starboard. E.g. -0.33 -> vessel moves to port with 0.33 m/sec. Unit: meters / second

6

o.o

Track offset

Positive when vessel shall follow a parallel track to starboard side of track. E.g. +77 -> vessel moves to a parallel track 77m to starboard. Unit: meters

7

t.t

Nav computer control of maximum allowed turn-rate

E.g. 20.0 means that the vessel will use 20 seconds to change the heading with one degree. Unit: seconds / degree

8

hh

Checksum

XOR


<CRLF>

Carriage Return and Linefeed character


Format Example
$DNRTR,191.0,-1.1,1.0,-0.0,0.0,10.0*67<CR><LF>
$DNRTR,191.0,-1.1,1.0,-0.0,0.0,10.0*67<CR><LF>
$DNRTR,191.0,-1.2,1.0,-0.0,0.0,10.0*64<CR><LF>
$DNRTR,191.0,-1.2,1.0,-0.0,0.0,10.0*64<CR><LF>
$DNRTR,191.0,-1.3,1.0,-0.0,0.0,10.0*65<CR><LF>
$DNRTR,191.0,-1.4,1.0,-0.1,0.0,10.0*63<CR><LF>
$DNRTR,186.0,-1.5,0.9,0.0,0.0,10.0*40<CR><LF>
$DNRTR,186.0,-1.1,1.0,0.0,0.0,10.0*4C<CR><LF>
$DNRTR,186.0,-1.2,0.9,-0.0,0.0,10.0*6A<CR><LF>
$DNRTR,186.0,-1.2,0.9,-0.0,0.0,10.0*6A<CR><LF>

Kongsberg TNT

Format
$PRTNT,X,cccccc,x.x,x.x,x.x,c--c,x.x,x.x,x.x*hh<CR><LF>

Format Description

 Field

Format

Description

Values, Range, Units

1

$PRTNT

NMEA Talker 'PR' and Sentence 'TNT' identifier

Talker Id default 'PR' but can be changed in the dialogs settings.

Sentence Id always 'TNT'.

2

X

Message indicator.
An 'X' message contains cross-track error, specification of and distance to a reference point, track bearing and a set of flags

Always 'X'

3

cccccc

A field of six flags

Flag 1: Navigation receiver warning (A = OK; U = dead reckoning; V = position not valid)
Flag 2: Interpretation of cross-track error and tangent bearing (L = line between turns; C = turn arc from T sentence.)
Flag 3: Acknowledgement of forthcoming turn (A = cleared for turn; V = acknowledgement needed)
Flag 4: Control mode (C = course; T = track)
Flag 5: Command transfer to... (A = autopilot; E = ecdis; X = other external; D = direct (manual))
Flag 6: Reference point of distance (W = start of turn; C = end of turn)

Always 'ALATAW'

4
x.x
Accuracy of cross-track error, meter.
Entry is left open if no value or approximation exists.
Always empty
5
x.x
Approximate time lag of cross-track error, seconds.
Entry is left open if no value or approximation exists.
Always empty
6
x.x
Cross-track error, meter. Negative on port side of track, positive on starboard side of the track.The range of the Cross-track error is [-9999, 9999]. Extreme values will be interpreted by the autopilot as "more than..."
7c--cTurn ID, a variable number of characters.Always the current linename, or the current linename preceeded by the label 'Turning Track to'.
8
x.x

Distance (from the selected node) to reference point, in the selected unit (default meters).

Reference point will be SOL when the vessel is still before SOL.
Reference point will be EOL or EOS when the vessel is somewhere on the line.

Reference point will be EOL when the vessel is past EOL and the sign of the distance value will be negative.
9
x.x
Tangent bearing, degrees true

The true line bearing of the current line or current section if the mainline is a route.

(See also Advanced Setting 'Smooth Bearing Output')

10
x.x
Recommended heading (true)
11*hhChecksumNMEA XOR


<CR><LF>

means the Carriage Return and Linefeed character


Format Example
$PRTNT,X,ALATAW,,,-1.405,Turning Track to R2,2.0,85.0,131.0*6E
$PRTNT,X,ALATAW,,,-1.814,Turning Track to R2,16.6,95.0,101.3*50
$PRTNT,X,ALATAW,,,-2.488,Turning Track to R2,14.2,95.0,105.1*5A
$PRTNT,X,ALATAW,,,-3.153,Turning Track to R2,12.0,95.0,110.3*5A
$PRTNT,X,ALATAW,,,-3.818,Turning Track to R2,9.8,95.0,117.9*63
$PRTNT,X,ALATAW,,,-4.490,Turning Track to R2,7.9,95.0,129.5*66
$PRTNT,X,ALATAW,,,-5.145,Turning Track to R2,6.6,95.0,146.4*6C
$PRTNT,X,ALATAW,,,-5.809,Turning Track to R2,6.0,95.0,169.5*67

Interfacing Notes


Click here for interfacing notes...

The driver is a so-called active driver which means it will send data to the sensor (Auto Pilot Unit). The driver does not expect to receive data from the sensor.

The default output update-rate is every second, but this can be changed in your Database setup.

There are three versions of this driver: a serial one (RS232) and two network based drivers (UDP / TCP).

The user-interface for the three drivers is exactly the same, only the I/O protocol is different.

  • For the serial driver version only a one-way cable wiring is needed

    Auto Pilot unit
    Qinsy Computer

    DB-25

    Sensor

    or

    DB-9

    Sensor

     

    DB-25

    COM

    or

    DB-9

    COM

    Pin 2

    TXD


    Pin 3

    TXD

    X

    Pin 3

    RXD


    Pin 2

    RXD

    Pin 3

    RXD


    Pin 2

    RXD

    <-----

    Pin 2

    TXD


    Pin 3

    TXD

    Pin 7

    SG


    Pin 5

    SG

    -----

    Pin 7

    SG


    Pin 5

    SG

  • For the TCP network driver version a connection with a TCP Server (Auto Pilot unit) is required.
    The driver will act as a TCP Client.
  • The UDP network driver will just broadcast the data to the selected port number and IP address (mask).

    Before you go online it is recommended to check for a valid network connection.
    E.g use the ping command from the Windows Command Prompt:

    Just select Start from the Windows Task bar, Run..., Cmd <Enter>, and 'ping' the address of the autopilot unit.

Qinsy Setup


Click here to expand setup details...

Database

Add an output system to your template setup and select driver

  • "AutoPilot (with turning track)" for the serial, or
  • "Network - AutoPilot (with turning track) (TCP)" or
  • "Network - AutoPilot (with turning track) (UDP)" for the network version.

The output sentence format needs to be selected in the online Settings for these two driver entries.

However for the serial version (only) you could select here the driver entry with already the correct output format, e.g "AutoPilot (with turning track) - NMEA XTE"; this means that you can't change the output format while being online.

The maximum update rate tells the driver how often the formatted data sentence will be output to the autopilot unit.

Default update rate will be 1.000 s, which means every second.

In case you autopilot unit needs more often an update, e.g. 5 times per second then you should enter 0.200 s (in this case).

Qinsy Online


Click here to expand the online setup...

The Autopilot output driver has user-interface and therefore should be present in the Windows Taskbar.

When going on-line for the first time, locate the driver in order to view and change the settings to your requirements.

(In case the driver's dialog is not present in the Windows Taskbar, use the Controller's Driver Settings dialog to make it visible again: use pull-down menu Settings or keyboard shortcut Ctrl+H)

The driver's dialog has an upper pane and a lower pane; in the upper-pane you'll find user-definable settings and in the lower pane you'll see the results of the current situation.

Some settings are general and therefore always available and some settings depend on the selected output format.

General Settings - Upper pane

Setup:

Most settings (green rows) are only to be changed once; when going online for the very first time.

Once everything is set up correctly it may be wise to hide them to prevent changing a setting by mistake, so here you can select to show or hide these setup settings.

Note the third option Show+Advanced Settings: this will invoke on the next row an easy short-cut to access additional advanced settings, which normally only can be found using the dialog's upper-left corner icon menu.

Advanced Settings:

Use the [...] button (or double-click on the row) to invoke the Advanced Settings dialog.

Note that these settings are also accessible via the upper-left corner icon menu.

Go to the Advanced Settings paragraph (below) for a full description.

Format:

Main purpose of this driver is to continuously send track offset information to the Auto Pilot so the unit knows what course to steer to stay on the survey line.

Select here the required output format that your auto pilot unit accepts:

  • [ None ]

  • NMEA APA format - Autopilot Sentence "A"

  • NMEA APB format - Autopilot Sentence "B"

  • NMEA RMB - Recommended Minimum Nav Info

  • NMEA XTE format - Cross track Error, Measured

  • Euro500 format

  • RobNav-AP9 format

  • RobTrack / STS500 format

  • Kongsberg TNT ($PRTNT,X)

A change will be effective immediately and can be seen in the lower Results pane.

Please see the Format Specific Settings below for additional settings that come with the selected format.

This option to select the format is only visible when you didn't specify the required output format in your template database setup, so i.e. only when you've selected driver:
"AutoPilot (with turning track)",
"Network - AutoPilot (with turning track) (UDP)", or
"Network - AutoPilot (with turning track) (TCP)".

Additional Output:

This setting is only visible when one of the NMEA output formats is selected.

The selected NMEA output format can be combined with an additional NMEA RMB/RMC output format in order to support autopilot units requiring this additional information.

Use Virtual Node:

For the best result it may be needed to define a steering node some meters ahead of the vessel (e.g. half the vessel length), or close to a location of the vessel's rotation point.

This all depends on your vessel characteristics / behavior.

Here you may use a 'virtual' calculated node position to influence the performance of the autopilot steering unit.

  • No
    Select this option to use the exact position of the selected node. The cross-track error (XTE) will be calculated using this exact position.

  • Extend Node Baseline
    Use a position which is defined some distance in front of the vessel (e.g. half the vessel length), in order to calculate the XTE.

  • Predict Node Position
    Use a predicted node position in order to calculate the XTE. The prediction position is calculated using the vessel's current speed, COG, heading, rate-of-turn and the user-defined prediction time. When using this mode, it is strongly advisable to enable Kalman filtering in the Controller's Computation Setup.

Baseline Direction:

This setting is only available when using a virtual extended node baseline.

The virtual node will be 'moved' forward over a certain distance, and the direction used should come from the vessel's course over ground (COG) or its heading.

Baseline Length:

This setting is only available when using a virtual extended node position.

Enter a positive value, in survey units, to 'move' the selected node forwards, enter negative to 'move' backwards.

Prediction Time:

This setting is only available when using a virtual predicted node position.

The driver can calculate where the selected node will be, after this 'prediction time' value, in seconds. The calculation is very powerful, because next to the vessel's speed, COG and heading, also the rate-of-turn is used. Realistic results can be expected if you use a prediction time of not more than 60 [sec], and when Kalman filtering is enabled in the Controller's Computation Setup. The distance between the actual node and the predicted position can be monitored in the Results part of the dialog (lower pane).

Notice that there is an option in each Navigation Display, to show the predicted vessel shape. Open a Navigation Display, go to View Properties, Objects, select your vessel object, expand the Trail Settings option and enable 'show prediction'. Enter the same prediction time, and now you may graphically monitor how well the calculated prediction behaves.

Node:

The position of the selected node will be used to calculate the line offset with respect to the current survey line.

  • [Steered Node]
    Use the current Controller's steered node. The name of the current steered node can be monitored in the Results part of the dialog (lower pane).

  • [Computation Setup]
    Use the node currently selected in the Controller's Driver Output Settings. This name can then also be monitored in the Results part of the dialog (lower pane).
    The Drivers Output Settings can be found inside the Controller via pull-down menu Settings (or shortcut Ctrl+H).

  • Node name list
    Select your own node name and computation, totally independent from Controller settings.

Note that it depends on the 'Use Virtual Node' setting whether the exact node position is used, or a 'virtual' one.

Computation:

This setting is only available when you have selected your own node name from the Node list.

  • From Priority List
    The first valid computation will be used automatically.

  • Computation name list
    Select your own computation name.

Minimum Turn Radius:

Enter the minimum turn radius (in survey units) of the vessel.

In order to calculate a smooth turning track, two turns will be used, one when departing the start-point, one when approaching the stop-point.
The minimum turn radius depends of course on the length and characteristics of your vessel.

If you enter a minimum turn radius of zero, the turning track will always be a straight line from start to stop, so no curves.

Run-Out:

Enter a value in survey units if you want to extend the previous line, prior commencing the first turn of the turning track.

This might be useful to allow e.g. a towed fish to end the previous line.

A negative value is allowed, but not recommended. Note that this extra run-out value comes on top of the value you may have entered in the Controller's Session Setup, to extend the survey line.

Run-In:

Enter a value in survey units if you want to approach the SOL of the new line in a straight line, e.g. to settle the ships attitude.

A negative value is allowed, but not recommended. Note that this extra run-in value comes on top of the value you might have entered in the Controller's Session Setup, to start before the actual survey line.

Auto Turning Track:

  • Disabled (Manually)
    A turning track will never be calculated automatically, but you may use the [ Calculate... ] button at any time.

  • Always at Linechange
    Whenever the mainline is changed (including reversing the line bearing) in the Controller, a turning track will be calculated to start of the new line, using the current settings.

  • Only when Auto Start/Stop Recording
    Depends on the Auto Recording Options as defined in the Controller's Session Setup Storage Control.
    It means that a new turning track will be calculated automatically as soon as the Controller stops recording based on these Auto Recording Rules.
    A typical survey scenario for this setting is when you want a combination of Area based recording and the track-to-follow should be based on the swath coverage from your multibeam.

Start

Here you select the start-point of the turning track.

  • Line to Line
    This will calculate a turning track from EOL of the previous line to SOL of the new line.

  • Vessel to Line
    This will calculate a turning track from the current vessel position to SOL of the new line.

  • Vessel to Swath Coverage
    This option is only available when Auto Turning Track is set to 'Only when Auto Start/Stop Recording'.
    See for detailed information the Swath Coverage settings below.

Stop:

Here you select the end-point of the calculated track, which is the beginning of the new line.

Normally you select "Nearest point on Line", in a rare occasion you might go for the other side, e.g. when the vessel is far away from the new SOL.

Scenario:

A maximum of six scenario's are possible to go from the start to the stop-point.

So when commencing the turning track a vessel may turn to port (left turn) or to starboard (right turn) and approaching the stop-point can also be from port or from starboard.

Use a Navigation Display to view the outcome of the selected scenario.

  • Best-Fit (Shortest Track)
    From all scenario's the driver determines the best fit curve: meaning the shortest distance.
    However sometimes it is useful to go for another scenario, e.g. when the current one forces the vessel to go over a shallow area (land) or a jetty.

  • L S L
    Left turn, Straight line, Left turn

  • L S R
    Left turn, Straight line, Right turn

  • R S L
    Right turn, Straight line, Left turn

  • R S R
    Right turn, Straight line, Right turn

  • R L R
    Right turn, Left turn, Right turn

  • L R L
    Left turn, Right turn, Left turn

Note that some scenario's are not always possible (mathematically) with current settings and situation.


Format Specific Settings

NMEA format settings

These additional settings will be available when one of the NMEA specific format is selected:

NMEA Talker:

Two characters should be entered, and will be part of the first field of the outputted datastring.

For example 'GP' will result in an output string that starts with "$GP". The result can be immediately seen in the lower Results pane of the dialog.

When the Kongsberg TNT ($PRTNT,X) format is required it is recommended to enter 'PR' otherwise the Auto Pilot unit may not recognize the datastring

Unit:

Select the unit of the outputted cross-track error value (XTE).

It is by default set to Meters ('M'), but you may also select Nautical Miles ('N') or International Feet ('f').

XTE Resolution:

The number of decimals for the outputted cross-track error (XTE) value, and is default set to 3.

XTE Offset: *)

The outputted cross track error value (XTE) will be appended with this offset and is by default set to 0.0.

You may enter a negative offset value in order to decrease the outputted cross track error.

The entered value will be displayed with a red color if it isn't equal to 0, as an extra reminder to the user.

XTE Scalefactor: *)

The outputted cross track error value (XTE) will be multiplied with this scale factor, and is by default set to 1.0.

You may increase this value e.g. to 10 or 100 in order to address high-performance autopilot systems.

Note that if the scale factor is set to zero, the outputted XTE will also be zero.

The entered value will be displayed with a red color if it isn't equal to 1, as an extra reminder to the user.

*) The outputted cross track error value = (actual cross track + XTE Offset ) * XTE Scalefactor

When using a non-default XTE Offset and/or Scalefactor you will see both results in the Cross Track Error field of the Results pane: first the actual cross track error (plus unit) and between brackets the outputted cross track error value.

Euro500 format settings

This additional setting will be available when the Euro500 format is selected:

Track Offset:

Enter a value in survey units.

The outputted off track will be the calculated one MINUS this value.

RobNav-AP9 format settings

No extra settings are needed when the RobNav-AP9 format is selected.

A description for all the settings can be found in the General Settings paragraph.

RobTrack / STS500 format settings

These additional settings will be available when the RobTrack / STS500 format is selected:

Track Offset:

Enter a value in survey units.

It will be pasted in field number six of the output datastring.

Maximum Turn Rate:

Enter a value in sec/deg.

It will be pasted in field number seven of the output datastring.

Kongsberg TNT ($PRTNT,X) format settings

These additional settings will be available when the Kongsberg TNT ($PRTNT,X) format (NMEA look-a-like) is selected:

NMEA Talker:

Two characters should be entered, and will be part of the first field of the output datastring.

It is recommended to enter 'PR' otherwise the Auto Pilot unit may not recognize the datastring.

Other characters are allowed but will be colored red to remind the user.

The result can be immediately seen in the lower Results pane of the dialog.

Unit:

Select the unit of the outputted cross-track error value (XTE).

It is by default set to Meters ('M'), but you may also select Nautical Miles ('N') or International Feet ('f').

XTE Resolution:

The number of decimals for the output cross-track error (XTE) value, which is by default set to 3.

XTE Offset: *)

The outputted cross track error value (XTE) will be appended with this offset and is by default set to 0.0.

You may enter a negative offset value in order to decrease the outputted cross track error.

The entered value will be displayed with a red color if it isn't equal to 0, as an extra reminder to the user.

XTE Scalefactor: *)

The output cross track error value (XTE) will be multiplied with this scale factor and is by default set to 1.0.

You may increase this value e.g. to 10 or 100 in order to address high-performance autopilot systems.

Note that if the scale factor is set to zero, the output XTE will also be zero.

The entered value will be displayed with a red color if it isn't equal to 1, as an extra reminder to the user.

Swath Coverage Settings

These red-row-colored settings are only visible when in so-called Swath Coverage Mode.

This means that the Auto Turning Track option is set to 'Only when Auto Start/Stop Recording' and Start is 'Vessel to Swath coverage'.


Turn Always to:

Select to which side the vessel has to move after stop recording in order to start recording for the next session.

The first two are relative to the last heading direction, the other ones (compass rose directions) are independent from any line bearing or heading.

  • Starboard

  • Port

  • NORTH

  • NE

  • EAST

  • SE

  • SOUTH

  • SW

  • WEST

  • NW

Selecting one of the compass rose directions is useful when surveying an area:

In this example the survey commences at the south-west side (following the pink line) so in order to auto survey the entire area you should select 'NE'.

Changing this setting when your vessel is 'outside' the selected survey area will automatically re-calculate the (current) turning track .
When the vessel is 'inside' the selected survey area then nothing will happen yet.

Turning Line:

  • Straight Line (Using average outerbeam)
    The mean or average swath width is used to calculate the new turning track so this means that after the turn the track to follow is a straight line.
    This option is useful to have continuously a consistent turning track. It assumes that a) your survey area doesn't have much fluctuation in de water depth (shallow and deeper areas) and b) that (spiky) outer beams do not cause an erratic swath coverage.

  • Variable Line (Using every outerbeam)
    This option is useful when the depth of your survey area changes suddenly which affects the swath width for those areas.
    Of course the final shape of the new track depends on the Damping Factor setting. In the bottom example below a 'moderate' damping factor is used.

Below two examples of the turning track based on the same swath coverage:

Changing this setting when your vessel is 'outside' the selected survey area will automatically re-calculate the (current) turning track .
When the vessel is 'inside' the selected survey area then nothing will happen yet.

Damping Factor:

The damping factor is used when the turning track is based on 'Variable Line (Using every outerbeam)'.
The setting affects the final shape of the new track.

Use your Navigation Display to see the outcome when changing the damping factor.

  • None
    The exact path of the outer beams from the swath coverage will be used for the next turning track.
    Not recommended when your multibeam system has erratic or spiky outer beams because you'll see this 'behavior' back in the track.

  • Light
    The outer beam track from the swath coverage will be used for the next turning track but the worst erratic/ spiky outer beam data is filtered out

  • Moderate (default)
    This filter will smooth the new turning track.

  • High
    This filter will smooth the new turning track.
    Useful when your multibeam system has erratic / spiky outer beams or when the survey area has rapidly changing depths.

  • Heavy
    This filter will smooth the new turning track heavily.
    Useful when your multibeam system has erratic / spiky outer beams or when the survey area has rapidly changing depths.

Below three examples of the turning track based on the same swath coverage, the first using 'None', the second one 'Moderate' and the third one 'Heavy':

Changing the damping factor when your vessel is 'outside' the selected survey area will automatically re-calculate the (current) turning track .
When the vessel is 'inside' the selected survey area then nothing will happen yet.

Turning Line Offtrack:

  • None (Same Track back)
    The new turning track will follow the exact same vessel track from the previous recording.
    In a Navigation Display this path is represented with the blue colored 'center_track'.
    -- This setting is useful to survey the same line multiple times (forward and backward) or e.g. in case of multibeam roll/pitch alignment calibration for a patch test.
    -- Another option is to use 'the same track back' in combination with an additional offset so you can automatically survey an entire area with a fixed line spacing.

  • From Overlap Percentage
    The new turning track will follow the outer beam track (port or starboard) from the swath coverage of the previous recording with an additional offset of half the swath width.
    In a Navigation Display the two outer beam paths are represented with a red colored 'port_track' and a green colored 'stbd_track'.

Changing this setting when your vessel is 'outside' the selected survey area will automatically re-calculate the (current) turning track .
When the vessel is 'inside' the selected survey area then nothing will happen yet.

Overlap:

This setting is only visible when the Turning Line Offtrack setting is 'From Overlap Percentage'.

Enter a percentage value between 0 and 100 %

0% means the same line back as the past outer beam track plus half of the entire swath width:

100 % means the same line back as the past outer beam track:

Changing the overlap when your vessel is 'outside' the selected survey area will automatically re-calculate the (current) turning track .
When the vessel is 'inside' the selected survey area then nothing will happen yet.

Additional Offset:

This extra offset will always be added to the calculated turning track line.

You may enter a negative value in order to allow extra overlap for the next recording.

Changing the offset when your vessel is 'outside' the selected survey area will automatically re-calculate the (current) turning track .
When the vessel is 'inside' the selected survey area then nothing will happen yet.


Results - Lower pane

Use the lower pane to see the calculated results for current situation and settings.

Here you can also quickly disable the output to the autopilot unit if desired.


Swath Coverage:

This row is only visible in Swath Coverage Mode.

It shows the status whether the driver is collecting outer beam information for the swath coverage or not.

  • Idle (x.x sec)
    This status means the driver is not collecting outer beam information yet.
    With other words the Controller didn't start auto recording.

  • Collecting (x.x sec)
    The Controller is recording because of the auto recording rules and so the driver collects outer beam information for the swath coverage.
    To emphasize this status the row will be colored green.

The incrementing value between brackets indicates the duration (in seconds) for this status

Node Name:

The name of the selected node which current location is used to determine the cross-track error. When using a virtual node it will be mentioned here.

Node Result:

The current position of the selected node, in grid co-ordinates, which is used to determine the cross-track error. When using a virtual node position, it will be the position of the virtual node.

Predicted Distance:

This result is only visible when using a virtual predicted node position. It reflects the distance between the actual node position and the calculated predicted position, using the prediction time setting, the current heading and rate-of-turn of the vessel.

Vessel Heading / COG:

The current heading and course over ground (COG) of the vessel. The displayed rotation convention (true or grid) depends on the global project settings, which you can set in the Console. When using a virtual predicted node position, the heading will be the predicted heading, also, no COG will be displayed, because it is not calculated for the predicted node.

Line name:

The name of the current line, or the label "Turning Track to" the current line, in case the turning track is used.

Line Bearing / Track Bearing:

Line bearing of the current line and the bearing of the closest section of the turning track.

The displayed rotation convention (true or grid) depends on the global project settings as entered in the Console's Settings.

Cross Track Error:

The calculated distance across (XTE), in survey units, of the current node position and the turning track or mainline.
Value will be displayed on a green colored background when the vessel is starboard of the line and dark red when the vessel is on port side.

Note that when using an additional (non-default) XTE Offset and/or Scalefactor you will see both results: first the actual cross track error and between brackets the outputted cross track error value.

Velocity Across / Along:

The across and along speed of the vessel. The across speed will be positive when heading to starboard, negative when heading to port. The unit depends on the current global project speed unit setting, which can be set in the Console.

Format:

The name of the selected output format. The format can be changed in your template setup.

Note that this row won't be visible when you are able to select the Format in the upper Settings pane.

Output to I/O port

The ASCII data string that will be outputted to the selected serial COM or network TCP port.

If you disable the checkbox it will put the data output on hold. In that case values will be updated in the Results, but are displayed in gray.

Disabling the data output (temporarily) can be useful to experiment with some settings, without disrupting the Auto Pilot unit too much by sending extreme values to it.

Logging:

This row is only visible when Advanced Setting 'NMEA Logging' is enabled.

Notes
  • The number of decimals for all displayed values depend on the display resolution as defined by your Global Settings (Console).

  • All displayed values will be colored gray when the Output to the I/O (checkbox) has been disabled.

Examples
  • This is an example of the lower pane when no valid node results have been received yet at startup:



    Just be patience and wait for the initialization to finish...

  • This is an example when the current mainline is used to determine the cross track error


    The 'Line name' row displays the name of the current mainline
    The 'Cross Track Error' row is colored red when the node location is at port side and colored green when at starboard side.

  • This is an example when the calculated turning track is being used:


    The 'Line name' row is colored orange and the name of the current mainline is preceded with 'Turning Track to'.
    The 'Cross Track Error' row is colored red when the node location is at port side and colored green when at starboard side.

  • This is an example when no network connection could be made between the Qinsy computer and the Auto Pilot unit:


    When this happens please check the network connection before you continue.
    See the Interfacing Notes paragraph for more about the network connection.

Turning Track Action Buttons

To overrule any automated action you can always use these buttons for a manual intervention.

Remove...

This will invoke a dialog that allows the user to manually remove the current calculated turning track and from that moment on the driver will use the co-ordinates of the Controller's mainline again in order to determine the cross track error (XTE or distance across).

The exact remove action upon OK depends on the current situation and settings.

When an option is grayed out it means it can't be changed for current situation so that option will be the default.

For example in the above dialog the turning track will be removed (first checkbox) and the collected swath coverage will be cleared (second checkbox).
The driver will use the mainline again in order to determine the cross track error for the output to the auto pilot unit.

So after this action you can't manually calculate a new turning track to the past swath coverage; but the driver will start collecting new outer beam information as soon as the Controller started the auto recording.

The option to restore the original mainline is only applicable when Advanced Setting 'Update Controller Mainline' is enabled. In that case the mainline was (temporary) replaced by the 'autopilot_swath_track'.

Calculate...

This will invoke a dialog that allows the user to (re-)calculate the turning track using the current settings. You may use this at any time.

Use the Navigation Display to monitor the outcome.

In the Line Name field of the Results pane you will see the label "Turning Track to..." to indicate that the driver is using the calculated turning track in order to determine the cross-track error (XTE). Additionally the field is also colored orange.

When an option is grayed out it means it can't be selected for current situation.

  • Current location to swath coverage

  • Current location to mainline

  • Previous line to mainline
    This option is only visible when the general 'Start' setting is 'Line to Line'.

  • Reverse
    Select this to reverse the direction of the current turning track: so starboard becomes port and port becomes starboard. It has immediate effect on the cross track error that is outputted to your auto pilot unit.

  • Reset Line offsets
    Select this to reset the line offset calculation: useful in the rare occasion that the current line offset cross track error is not okay (which may occasionally happen with odd shaped turning tracks)


Advanced Settings

The advanced settings can be found using the dialogs upper-left icon menu or by double-clicking on the Advanced Settings row in the general setup


Update Controller Mainline:

This setting has only effect when in Swath Coverage mode.

This will activate immediately the new turning track as current mainline. So this new mainline is an exact copy of the turning track, based on the swath coverage, but without the turn to the start of it.

Line name will always be 'autopilot_swath_track'

Default setting is Yes.

Track can be found in layer 'ACTIVE' and stored in the project's LineData subfolder with filename 'autopilot.qgfline'.

Keep Mainline History:

This setting has only effect when in Swath Coverage mode.

This will keep a history of all previous calculated turning tracks where each track will be suffixed with an incrementing number.

  • Online (default)
    All calculated turning tracks will remain during your online session but will be removed when going offline

  • Always
    All calculated turning tracks will remain in the qgfline file and will not be removed when going offline

All tracks can be found in layer 'HISTORY' and stored in the project's LineData subfolder with filename 'autopilot.qgfline'.

Smooth Track Iterator:

This is a filter setting and has only effect when in Swath Coverage mode.

The calculated turning track may be affected by erratic outer beam behavior so in that case you should increase the iterator value to make the track smoother.

The default value will be 1, 0 means no filter strength applied at all.

It is safe to change this value when your vessel is still 'inside' the selected survey area: nothing will happen.
When the vessel is 'outside' the survey area then closing this dialog will automatically re-calculate the (current) turning track.

Smooth Heading Iterator:

This is a filter setting and has only effect when in Swath Coverage mode.

The calculated turning track may be affected by unstable heading behavior of the transducer so use this setting to filter the original heading values.

Note that in general such unstable heading behavior is expected on very small boats (unmanned or autonomous vehicles).

0: means no filter (original heading values)

1: is the default filter strength

4: is the strongest filter strength

5: means that a fixed value is used which is derived from the sailed start to end bearing

It is safe to change this value when your vessel is still 'inside' the selected survey area: nothing will happen. When the vessel is 'outside' the survey area then closing this dialog will automatically re-calculate the (current) turning track.

Section Reducer:

This is a filter setting and normally only useful when in Swath Coverage Mode.

The number of sections for the calculated turning track (based on the swath coverage) will be reduced by this number

Below two examples of the same calculated turning track, the first one with a maximum of 25 sections and the second one with a maximum of 100 allowed sections:

Less number of sections may result in a more stable autopilot behavior.
The auto pilot unit may receive at every section change a new 'heading-to-steer' value. This depends of course on the selected output format and on how erratic the turning track actually is.

Enable NMEA Logging:

All settings and all navigation data (NMEA) will be logged and therefore can be used afterwards for debugging purposes or reproducing the online behavior of your ASV.

Yes will be the default.

Two files are created and appended automatically every time you come online with the following filename convention:

  • DrvOutAutoPilotUI (<System Name>) dd-mm-yyyy.NMEA.log
    This file contains the GGA and HDT representation string for the selected node for each update and the exact formatted string that was being output to the autopilot unit in a sequential order.

  • DrvOutAutoPilotUI (<System Name>) dd-mm-yyyy.SETTINGS.log.
    This file contains the drivers dialog settings modifications in a sequential order.

Location will be the current project's LogFiles folder.

Beta Tester:

As a beta tester you'll get access to Abort / Resume Mission functionality.

Use [ Your System Name ]:

This setting has only effect when in Swath Coverage mode.

The swath width of this system will be used when enabled and therefore affects the turning track calculation.
So if you enable more than one system then all outer-beams will be used to determine the maximum width.

This row is repeated for every available singlebeam/multibeam/multi-transducer/laser system defined in your template database setup.

Example for a commonly used setup could be:
the multibeam system will be enabled and a possible defined laser and/or singlebeam system needs to be disabled.





Smooth Bearing Output:

Enabling the Smooth Bearing Output is only recommended to use in Swath Coverage mode.

  • Enabled
    This will filter the line bearing field in the NMEA APA, NMEA APB or Kongsberg TNT output format.
    (It has no effect when using other output formats)

  • Disabled (default)
    Leave disabled in order to use the exact line bearing of the current section

Which NMEA field is affected when this setting is enabled?

  • NMEA APA
    Field #9, 'Bearing origin to waypoint'

  • NMEA ABP
    Field #9, 'Bearing origin to waypoint'

  • Kongsberg TNT
    Field #9, 'Tangent bearing, degrees true'

Same Direction Threshold:

This setting affects the minimum turn radius in order to approach the next line.

It means that when the vessel (start point) is already approaching the line (i.e. both have same direction) then the track to follow will be just 'connecting the dots' instead of using mathematical turns.

  • No Threshold
    This will always use the exact minimum turn radius to approach

  • 30 deg (default threshold)
    When the vessel heading and the next line direction are more or less the same (within 30 degrees) then a straight line section will be used to approach the next line instead of a turn.

Below two examples of the same situation where the vessel is more or less approaching the next line:

The first one (with no threshold) would be the mathematical correct outcome but may result in an unwanted extra turn in order to approach the line.

The second example uses the default 30 degree threshold so in this case no unwanted/unnecessary turn was added.

Maximum Turn Angle:

Set the maximum turn angle for the turning circle sections. A turn angle from one section waypoint to the next will never exceed this value.

Enter a value between 1 and 30 deg

The default maximum turn angle is 5 deg

Below two examples of the same calculated turning track, the first one with a max turn angle of 1 and the second one of 30 degree:

Playing with his setting may affect the behavior of your auto pilot unit: ever section change along the turn will output a different 'cross track error' and 'heading-to-steer' - change.

Turning Track Name Specifier:

When a turning track is used for the cross track error calculation instead of the Controller's mainline then this format specifier is used to name it.
This name is visible in the Line Name row of the Results pane (orange background color) and it will be part of the output when an NMEA format is selected.

Here you may overrule the default naming with your own free text, plus the following format specifiers:


  • #L: Current line name

  • #P: Project name

  • #J: Job Number

The default name for the calculated turning track will be "Turning Track to <current line name>".

Note that this track name will be part of most NMEA output formats.

Useful option to overrule the default name in case your autopilot unit does not accept names which are too long.

Display


Click here how to visualize the track...

Navigation Display

The calculated turning track can be made visible automatically in your Navigation Display:

Open your Navigation Display, select 'View Properties', 'Layers', 'Line Planning' and make sure to check the 'AutoPilot turning track' option.

With the settings from the above example, the Navigation Display may look like this, after hitting the Calculate Turning Track button:


Tip

Every time when the turning track is calculated or changed, it will be refreshed by the Navigation Display within 5 seconds.

It is recommended to decrease this default 'refresh time' for a much faster response of your display. How?

Just select 'View Properties', 'View', 'User Interface' and set the 'File change check interval, in seconds' option to 1.


Note that the default (own) color of the turning track is orange and the individual straight sections in the turn are connected with orange circles.

Use the same View properties to change this turning track orange color in order to select your preferred one.

The circle icons can also be modified but for this you need to change the following registry key of the AutoPilot driver while being offline:

\HKEY_CURRENT_USER\Software\Qps\QINSy\8.0\Drivers\DrvOutAutoPilotUITCP\<Driver's Name>\Settings\Advanced - Icon Name

Possible values for this key are "icon_dot", "icon_solid_circle", "icon_open_circle", "icon_solid_square", "icon_open_square", "icon_plus", "icon_x", "icon_forward_arrow" or "icon_backward_arrow".

You may also enter the name of an existing graphics file located in the C:\Program Files (x86)\Common Files\QPS\CadIcons folder, but without file extension, e.g. "Star Yellow".





JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.