TT3026 Software Reference Manual

TT-3026L/M/S/D/LM easyTrack Transceiver,
TT-3000SSA Ship Security Alert System and

TT-3000E mini-C GMDSS System
Software Interface Reference Manual
Thrane & Thrane A/S

TT-3026 easyTrack Transceiver
Copyright Thrane & Thrane A/S

ALL RIGHTS RESERVED
2006, Thrane & Thrane A/S
Information in this document is subject to change without notice and does not represent
a commitment on the part of Thrane & Thrane A/S.
Document number: 98-116080 Revision: J

SAFETY SUMMARY
The following general safety precautions must be observed during all phases of
operation, service and repair of this equipment. Failure to comply with these
precautions or with specific warnings elsewhere in this manual violates safety standards
of design, manufacture and intended use of the equipment
Thrane & Thrane A/S assume no liability for the customers failure to comply with these
requirements.
MICROWAVE RADIATION HAZARDS
During transmission this unit radiates microwaves from the antenna. This radiation may
be hazardous to humans if they are exposed to it directly at short distances from the
antenna. During transmission, make sure that nobody is closer than the recommended
minimum safety distance of 0.3 meter.
KEEP AWAY FROM LIVE CIRCUITS
Operating personnel must not remove equipment covers. Qualified maintenance personnel must
make component replacement and internal adjustment. Under certain conditions, dangerous voltages
may exist even with the power cable removed. To avoid injuries, always disconnect power and
discharge circuits before touching them.

REVISION HISTORY
Rev.
I
Date
App.
2005-08-24
Section
Description / Remarks
8.26.3
Printer status
Figure 4.1
Figure updated to reflect software ver. 2.19
2.6
GPS section added
4.16.1
Auto grouping description updated
Table 7.1
Table updated with new data logging fields
8.9.6
Dn -f command extra precision for pos. upd.
8.9.14
Dn -p command extra precision for pos. upd.
8.9.17
Dn -tb command added give support for
8.14
GPS command added
8.20.4
Log -f command extended with new options
8.23.5 and
The option retxfail description has been upd.
binary user strings
8.11.3
8.23.7
Pg -fe command: An unused reserved field
New extended position precision field desc.
has replaced option remote.

D
New data logging fields described
8.28.33
Environment variable PRNFILTER added
5.3 , C.5
Added zone group/group list selection poll
8.25
Added Route command
8.9.8 / 8.9.9 Message data reporting

A.3
Table 9.15
J
2006-06-22
8.28.15
Configuration poll messages.

Default position for land mobile earth
generator updated.
8.28.9
SSA Covert Alert additional supplementary
8.28.5
SSA Covert Alert retransmission rate.
Table 8.12
Updated for new power statistic entry
8.9.6
New options for auto creation of interval
8.28.11
Configuration reset.
text.
(ecxeption).
programs - not auto started.
Thrane & Thrane A/S
This Document and any other appended documents and drawings are of copyright to
Thrane & Thrane A/S. It contains proprietary information which is disclosed for
information purposes only. The contents of this document shall not in whole or in part be
used for any other purpose; be disclosed to any member of the recipients organisation not
having a need to know such information or to any third party, individual, organisation or
Government; be stored in any retrieval system or be produced or transmitted in any form
by photocopying or any optical, mechanical or other means without prior permission of
Thrane & Thrane A/S.

TABLE OF CONTENTS
Table of Contents.................................................................... 4
List of Figures .......................................................................12
List of Tables ........................................................................13
1 Introduction .....................................................................14
1.1
Applicability...................................................................................................14
1.2
Related Documents and References................................................................14
1.3
Abbreviations.................................................................................................15
1.4
The Interface ..................................................................................................15
1.5
Changes From TT-302x C-Transceiver............................................................16
1.5.1
Environment Variables ............................................................................16
1.6
The CapLib Software Package ........................................................................16
2 General Transceiver Properties ..........................................17
2.1
Automatic Operations .....................................................................................17
2.1.1
Power On Operation ................................................................................17
2.1.2
Automatic Ocean Region Shift ..................................................................17
2.1.3
Automatic Login .......................................................................................18
2.2
Authority Levels..............................................................................................18
2.3
File System .....................................................................................................19
2.3.1
File Priorities ...........................................................................................20
2.3.2
File Commands........................................................................................20
2.4
Sleep Mode (Power Events)............................................................................20
2.4.1
Sleep Mode Disabled...............................................................................20
2.4.2
Sleep Mode Enabled................................................................................21
2.5
I/O Interface ...................................................................................................21
2.5.1
Input Pins .................................................................................................22
2.5.2
Tachograph Interface Pin .........................................................................22
2.5.3
Output Pins ..............................................................................................22
2.6
GPS unit ..........................................................................................................23
2.6.1
SBAS ........................................................................................................23
3 Messaging .......................................................................25
3.1
Overview........................................................................................................25
3.2
File Format .....................................................................................................25
3.2.1
Telex Address.........................................................................................25
3.2.2
Public Switched Telephone Network (PSTN) Address .............................25
3.2.3
Public Switched Data Network (PSDN ) x.25 address ...............................26
3.2.4
Closed Data Network ID (DNID) Address.................................................26
3.2.5
Special Access Code (SAC) Address.......................................................26
3.2.6
Address Prefix .........................................................................................26
3.3
Message Alphabets ........................................................................................26
3.4
Inmarsat Network Destination Codes..............................................................27
3.5
Examples........................................................................................................27
3.6
DNID Download Confirmation.........................................................................28

4 Data Reporting .................................................................29
4.1
Introduction ....................................................................................................29
4.2
Setting Up Data Networks ...............................................................................29
4.3
Manual Reports...............................................................................................30
4.4
Interval Reports ..............................................................................................31
4.4.1
Week schedule ........................................................................................33
4.4.2
Tachograph control..................................................................................33
4.5
Event Reports .................................................................................................34
4.6
Sleep Mode ....................................................................................................36
4.7
Antenna Blocked and GPS Blocked Events......................................................37
4.7.1
Antenna Blocked Events ..........................................................................37
4.7.2
Antenna blocked Filter feature ................................................................37
4.7.3
GPS Blocked Events .................................................................................40
4.8
Speed Limit Event...........................................................................................40
4.9
Mem Code translation ....................................................................................40
4.10 Attaching User-string......................................................................................41
4.11 Surveillance zones ..........................................................................................41
4.11.1 Basic Zones Feature .................................................................................42
4.11.2 Advanced Zones Feature .........................................................................43
4.12 Stored Positions ..............................................................................................46
4.13 Single Packet Position Reports........................................................................46
4.14 Number of Active Dnids in Transceiver ..........................................................46
4.15 Long to short report interval change...............................................................47
4.16 DNID Groups ..................................................................................................47
4.16.1 Auto grouping..........................................................................................49
4.17 Minimum Distance Between Position Reports..................................................50
4.18 Data Reporting Protocol..................................................................................50
5 Remote Configuration and Polling .......................................51
5.1
General Introduction ......................................................................................51
5.1.1
Sending Polls ...........................................................................................51
5.1.2
Initial Data Reporting and Polling Procedures..........................................51
5.1.3
Pollfile Contents.......................................................................................52
5.1.4
Poll Addressing .......................................................................................52
5.1.5
Polling Commands...................................................................................53
5.1.6
Response .................................................................................................54
5.1.7
Acknowledgement...................................................................................54
5.1.8
Randomising............................................................................................54
5.2
Sleep Mode Setup Poll ....................................................................................54
5.3
Remote configuration poll...............................................................................55
5.3.1
Zone Configuration Poll ...........................................................................55
5.3.2
Zone Group/Group list Selection Poll.......................................................56
5.4
I/O control poll ...............................................................................................56
5.4.1
Set output status .......................................................................................56
5.4.2
Read I/O status.........................................................................................56
5.5
Inmarsat PU Reporting ....................................................................................56
5.5.1
Programmed Unreserved (PU).................................................................57
5.5.2
Getting Data from Sub-addresses ............................................................57
5.6
Configuration information...............................................................................58
5.6.1
Poll packet format ....................................................................................58
5.6.2
Response packet format...........................................................................58
6 Alert functions..................................................................60
6.1
Land mobile alert............................................................................................60

5

6.2
6.3
6.4
Maritime Distress alert....................................................................................60

Covert/Security alerts ....................................................................................60
Alert reporting................................................................................................61
7 The data-logging feature ....................................................64

7.1
7.2
7.3
Data logging is not supported by all transceivers ...........................................65

Setting up the log............................................................................................65
Retrieving the data .........................................................................................67
8 Command Reference .........................................................68
8.1
Alarm..............................................................................................................68
8.1.1
ALARM Land Mobile Alert .......................................................................68
8.2
CA ..................................................................................................................69
8.2.1
CA Calibrate Frequency Correction ......................................................69
8.3
CFG ................................................................................................................69
8.3.1
CFG -c Configure Covert/Security Alert ................................................69
8.4
Clear ..............................................................................................................70
8.4.1
CLEAR Abort Current Operation ............................................................70
8.5
Confirm ..........................................................................................................70
8.5.1
CONFIRM Confirmation Request ............................................................70
8.6
Data ................................................................................................................71
8.6.1
DATA Manual Data Report......................................................................71
8.6.2
DATA -b Byte Count ...............................................................................72
8.6.3
DATA -o Insert Position at the Start of the Data Report ............................72
8.6.4
DATA -p Append Data to the Data Report Buffer.....................................72
8.7
Delete.............................................................................................................73
8.7.1
Delete Delete File(s) ..............................................................................73
8.8
DIAG ..............................................................................................................74
8.8.1
DIAG Diagnostics ...................................................................................74
8.8.2
DIAG DSP INFO Enable or disable DSP diagnsotics ................................74
8.8.3
DIAG DSP LD 7Request Lock detect status...............................................74
8.8.4
DIAG DSP ADC ADC sample data ...........................................................74
8.8.5
DIAG DSP RD Read DSP memory.............................................................74
8.8.6
DIAG TC Enable or Disable diagnostics trace .......................................74
8.8.7
DIAG TC CLR Disable diagnostics trace .................................................75
8.8.8
DIAG TC CLRALL Disable diagnostics trace ...........................................75
8.8.9
DIAG TC SET Enable diagnostics trace ..................................................75
8.8.10 DIAG TC SETMASK Enable diagnostics trace .........................................75
8.8.11 DIAG TC TEST Test Trace logging...........................................................75
8.8.12 DIAG TC LIST List processes with trace...................................................75
8.8.13 DIAG ACCESS Access layer diagnostics ................................................75
8.8.14 DIAG ACCESS -c Channel status .............................................................75
8.8.15 DIAG ACCESS -i List info.........................................................................76
8.8.16 DIAG ACCESS -p Show Packet log ..........................................................76
8.8.17 DIAG ACCESS -t Show the last frame received........................................76
8.9
DN ..................................................................................................................76
8.9.1
DN Data Network Setup..........................................................................76
8.9.2
DN -a DNID auto-grouping .....................................................................77
8.9.3
DN -c Clear DNIDs .................................................................................77
8.9.4
DN -d Display DNIDs...............................................................................77
8.9.5
DN -e DNID groups .................................................................................78
8.9.6
DN -f Set Default DNID Format.................................................................78
8.9.7
DN -fa Default auto-gruoping .................................................................79
8.9.8
DN -fg Default Reporting Protocol ..........................................................80
8.9.9
DN -g Reporting Protocol .......................................................................81
8.9.10 DN -l Set User Default Mem Codes ..........................................................81
6

8.9.11 DN -m Setup MEM codes to DNID-entry ..................................................82

8.9.12 DN -n Change Number Of Active DNIDs ................................................83
8.9.13 DN -o Create DNID..................................................................................83
8.9.14 DN -p Program DNID...............................................................................84
8.9.15 DN -s Change DNID Status......................................................................85
8.9.16 DN -t Attach User-string ..........................................................................85
8.9.17 DN -tb Attach Binary User-string .............................................................86
8.10 Directory ........................................................................................................86
8.10.1 DIRECTORY List Files .............................................................................86
8.11 EV...................................................................................................................87
8.11.1 EV -c Clear Event Program ....................................................................87
8.11.2 EV -d Display Event Programs ...............................................................87
8.11.3 EV -e Setup Extended Event Parameters ................................................87
8.11.4 EV -fe Default extended program parameters........................................88
8.11.5 EV -fp Default program parameters .......................................................88
8.11.6 EV -o Open/Create Event Program ........................................................88
8.11.7 EV -p Program/Specify Event Program ..................................................89
8.12 FI 89
8.12.1 FI Fishery configuration ..........................................................................89
8.12.2 FI 34 Autogrouping .................................................................................90
8.12.3 FI 72 Set Max number of DNID .................................................................90
8.13 FX ...................................................................................................................90
8.13.1 FX Set Fixed Positions .............................................................................90
8.14 GPS.................................................................................................................91
8.14.1 GPS GPS Configuration ..........................................................................91
8.14.2 GPS -d Display SBAS state .......................................................................91
8.14.3 GPS -g Display Status of the GPS Receiver ...............................................91
8.14.4 GPS -s Show or set SBAS configuration ....................................................92
8.15 Help................................................................................................................92
8.15.1 HELP Show Command Help....................................................................92
8.16 ID....................................................................................................................92
8.16.1 ID System Identification..........................................................................92
8.17 IO ...................................................................................................................92
8.17.1 IO -c Clear io-pin setup...........................................................................93
8.17.2 IO -i Input-pin Setup................................................................................93
8.17.3 IO -o Output-pin setup .............................................................................94
8.17.4 IO -s Show Io-pin setup ...........................................................................95
8.17.5 IO -t Tachograph pin setup ......................................................................95
8.18 LI 96
8.18.1 LI Login ..................................................................................................96
8.19 LO...................................................................................................................96
8.19.1 LO Logout...............................................................................................96
8.20 LOG ................................................................................................................96
8.20.1 LOG -c Clear the Data-Log ......................................................................97
8.20.2 LOG -d Display Data-Log Settings ...........................................................97
8.20.3 LOG -e Set Extended Data-Log Settings ...................................................97
8.20.4 LOG -f Select Data-Log Fields .................................................................97
8.20.5 LOG -i Start Logging ...............................................................................98
8.20.6 LOG -p Select Data-Log Events ................................................................98
8.20.7 LOG -s Stop Logging ...............................................................................98
8.20.8 LOG -x Transfer Data-Log .......................................................................98
8.21 NCS ................................................................................................................99
8.21.1 NCS -a Add an NCS .................................................................................99
8.21.2 NCS -g Go to Specific NCS .....................................................................99
8.21.3 NCS -l Show NCS list ............................................................................ 100
8.21.4 NCS -r Remove an NCS ........................................................................ 100
8.21.5 NCS -s Initiate Scanning for the Strongest NCS Signal .......................... 100
8.22 Password ...................................................................................................... 101
8.22.1 PASSWORD Change Password ............................................................. 101
8.23 PG ................................................................................................................ 102
7

8.23.1 PG -a Set alert activation ....................................................................... 102

8.23.2 PG -b Value of sparebit for dateformat 3 ............................................... 102
8.23.3 PG -c Close a Local Connection............................................................ 103
8.23.4 PG -d Overview of Connection Status................................................... 103
8.23.5 PG -e Extended program set-up........................................................... 104
8.23.6 PG -fa Set default alert activation........................................................... 105
8.23.7 PG -fe Default extended program set-up.............................................. 106
8.23.8 PG -fl Set default Long Interval and Minimum Distance ......................... 106
8.23.9 PG -fp Set default program parameters ................................................ 107
8.23.10
PG -fv View default extended program parameters .......................... 107
8.23.11
PG -i Initiate a Programmed Local Connection.................................. 107
8.23.12
PG -l Set Long Interval and Minimum Distance.................................. 107
8.23.13
PG -o Open a Local Connection ........................................................ 108
8.23.14
PG -p Program a Local Connection ................................................... 108
8.23.15
PG -s Stop a Programmed Local Connection ..................................... 108
8.23.16
PG -v View Extended Program Parameters....................................... 109
8.24 Recvfile......................................................................................................... 109
8.24.1 RECVFILE Receive File......................................................................... 109
8.25 RO ................................................................................................................ 109
8.26 RU................................................................................................................. 110
8.26.1 RU -g Display Status of the GPS Receiver.............................................. 110
8.26.2 RU -l List the Currently Connected Devices.......................................... 113
8.26.3 RU -p Set printer status ......................................................................... 113
8.27 SENDFILE ..................................................................................................... 114
8.27.1 SENDFILE Send File.............................................................................. 114
8.28 SET ............................................................................................................... 114
8.28.1
114
8.28.2 SET -a Enable or Disable Reception of Inmarsat System Call EGCs ..... 115
8.28.3 SET -am Set SSA message destinations.................................................. 115
8.28.4 SET -ame Set Extended SSA message destinations ................................ 116
8.28.5 SET -ap Set SSA message repeat rate ................................................... 117
8.28.6 SET -ar Reset high priority message or egc light indication .................. 117
8.28.7 SET -at Set SSA message text................................................................. 117
8.28.8 SET -atf Set SSA message text from file.................................................. 118
8.28.9 SET -atx Set SSA additional message text .............................................. 119
8.28.10
SET -au Set authority levels................................................................ 119
8.28.11
SET -b Reinitialize system parameters ............................................... 119
8.28.12
SET -c Show or Set Serial Port Parameters......................................... 120
8.28.13
SET -e Receive only EGC messages................................................... 120
8.28.14
SET -fd Filesystem cleanup ............................................................... 121
8.28.15
SET -g Set Up Alert Generator........................................................... 121
8.28.16
SET -I Enable or Disable Reception of FleetNet EGCs ...................... 122
8.28.17
SET -k Enable or Disable Land Mobile Alerting ................................ 122
8.28.18
SET -l Setup or Show NCS List ........................................................... 123
8.28.19
SET -m Set Up Alert........................................................................... 123
8.28.20
SET -n Enable or Disable Reception of Coastal Warning Call EGCs... 124
8.28.21
SET -ns Enable or Disable Login On the Nearest Allowed Satellite.... 124
8.28.22
SET -o Preferred Ocean Region .......................................................... 124
8.28.23
SET -p Show or Set Position and Heading Values ............................... 125
8.28.24
SET -q Distress test mode .................................................................. 125
8.28.25
SET -r Silent Mode ............................................................................. 126
8.28.26
SET -s Set Spare NavArea.................................................................. 126
8.28.27
SET -sn Set Spare NavAreas .............................................................. 126
8.28.28
SET -sp Speed Limits......................................................................... 127
8.28.29
SET -u Mobile Number ..................................................................... 127
8.28.30
SET -w Display SafetyNet EGC Reception Setting.............................. 128
8.28.31
SET -x Set Coastal Warning Areas..................................................... 128
8.28.32
SET -y Set Navtex Services................................................................ 128
8.28.33
SET -z Environment Variables........................................................... 128
8.29 Sleep ............................................................................................................ 129
8

8.29.1 SLEEP -c Disables Sleep Mode Operation ............................................ 129

8.29.2 SLEEP -d Show Sleep Mode Status ........................................................ 130
8.29.3 SLEEP -f Setup Sleep Mode Report Filter ............................................... 130
8.29.4 SLEEP -i Setup Sleep Mode Operation.................................................. 130
8.29.5 SLEEP -l setup auto-logout before sleep mode ...................................... 131
8.30 Status ............................................................................................................ 131
8.30.1 STATUS Display Transceiver Status ...................................................... 131
8.30.2 STATUS -a Status of Latest Alert ............................................................ 131
8.30.3 STATUS -c Channel Parameters............................................................ 132
8.30.4 STATUS -d DNID Information ................................................................ 133
8.30.5 STATUS -e Show EGC Log ...................................................................... 134
8.30.6 STATUS -g ENID Information ................................................................ 135
8.30.7 STATUS -i Show Transceiver Identification ........................................... 136
8.30.8 STATUS -l Show Status Report............................................................... 136
8.30.9 STATUS -m Show Last Test Result.......................................................... 136
8.30.10
STATUS -n Show LES Network Table ................................................. 136
8.30.11
STATUS -o Power On Statistics .......................................................... 137
8.30.12
STATUS -q Show Contents of Command Queue................................. 139
8.30.13
STATUS -r Receive Log ..................................................................... 139
8.30.14
STATUS -s Show Signal Strength........................................................ 140
8.30.15
STATUS -t Transmit Log..................................................................... 141
8.30.16
STATUS -v Show Software Version Number....................................... 143
8.30.17
STATUS -w Hardware Status Screen .................................................. 143
8.31 SU ................................................................................................................. 144
8.31.1 SU Substitute User ................................................................................ 144
8.32 Test............................................................................................................... 145
8.32.1 TEST Link Test ...................................................................................... 145
8.33 Time ............................................................................................................. 145
8.33.1 TI Show Present Time ........................................................................... 145
8.33.2 TI -l Show Local Time............................................................................ 146
8.33.3 TI -s Set Time....................................................................................... 146
8.33.4 TI -u Show UTC Time ............................................................................ 146
8.34 Transfer ........................................................................................................ 147
8.34.1 TRANSFER Transfer File From Console................................................. 147
8.34.2 TRANSFER -b Transfer in Binary Notation ............................................. 147
8.35 TX ................................................................................................................. 147
8.35.1 TX Transmit A Message ........................................................................ 147
8.35.2 TX -a Send with distress priority ............................................................ 148
8.35.3 TX -c Specify LES to Route the Message................................................ 148
8.35.4 TX -e Additional Receiver Address Information.................................... 148
8.35.5 TX -h Transmission time ....................................................................... 148
8.35.6 TX -k Keep Message After Transmission............................................... 149
8.35.7 TX -l Set Presentation at the Receiving End .......................................... 149
8.35.8 TX -s Specify Transmit Service ............................................................. 149
8.35.9 TX -t Specify Terrestrial Link ................................................................ 149
8.35.10
TX -v Request Confirmation .............................................................. 149
8.35.11
TX -y Transmission date..................................................................... 149
8.36 Type ............................................................................................................. 150
8.36.1 TYPE Display the Contents of a File ...................................................... 150
8.36.2 TYPE -b Type Binary ............................................................................ 150
8.36.3 TYPE -k Type and Keep........................................................................ 150
8.37 Weeksched .................................................................................................. 150
8.37.1 Weeksched Setting up a week schedule ............................................... 150
8.37.2 WEEKSCHED -c Clear week schedule .................................................. 151
8.37.3 WEEKSCHED -d Display week schedule ............................................... 151
8.37.4 WEEKSCHED -o Create week schedule entry ....................................... 151
8.38 Zone ............................................................................................................. 152
8.38.1 ZONE Set-up surveillance zones........................................................... 153
8.38.2 ZONE -a Display active zones ................................................................ 154
8.38.3 ZONE -ag Set active zone group............................................................ 154
9

8.38.4
8.38.5
8.38.6
8.38.7
8.38.8
8.38.9
8.38.10
8.38.11
8.38.12
8.38.13
8.38.14
8.38.15
8.38.16
8.38.17
8.38.18
8.38.19
8.38.20
8.38.21
8.38.22
ZONE -al Set active zone group list ....................................................... 154

ZONE -d Displays the zone configuration .............................................. 155
ZONE -dg Display Zone Group Configuration ........................................ 155
ZONE -dl Display Zone Group List Configuration ................................... 155
ZONE -g Add a Group to a Zone Group List............................................ 156
ZONE -i Change the reporting interval.................................................. 156
ZONE -ig Setup interval for zone in group.......................................... 156
ZONE -n Create a new zone ............................................................... 157
ZONE -ng Add Zone to Group............................................................. 157
ZONE -o Add radius or width ............................................................. 157
ZONE -og Setup radius of zone in group ............................................. 158
ZONE -p Add a position to a zone ...................................................... 158
ZONE -pg Setup positions in group..................................................... 159
ZONE -r Remove a zone ..................................................................... 159
ZONE -rg Remove zone in group ........................................................ 159
ZONE -rl Remove Zone Group List ...................................................... 159
ZONE -s Get the current zone number ............................................... 160
ZONE -t Test a position ...................................................................... 160
ZONE -u Check all zones now............................................................. 160
9 Info and Error Messages .................................................. 161
9.1
Introduction .................................................................................................. 161
9.2
Command Status Reports .............................................................................. 161
9.3
Message Delivery Reports............................................................................ 163
9.4
Command Errors .......................................................................................... 163
9.5
Receiving Messages ..................................................................................... 164
9.6
GPS Status..................................................................................................... 165
9.7
General Status .............................................................................................. 165
9.8
Link Status .................................................................................................... 165
9.8.1
List of Link Error Messages .................................................................... 166
9.9
Link Test Messages....................................................................................... 168
9.10 Distress Test Mode ....................................................................................... 168
9.11 Sleep Mode .................................................................................................. 168
APosition Report Packet Format .......................................... 169

A.1
A.2
A.3
Packet Formats defined for the satellite link ................................................. 169

T&T Data report format ................................................................................. 178
Message data report format.......................................................................... 179
BDifferences in VMS configuration between TT-3022D and TT3026M 180
Packet format of the configuration poll .......................... 183
Format of data from the data log ................................... 200
C.1
C.2
C.3
C.4
C.5
General format ............................................................................................. 183

Packet format of the zone configuration poll ................................................. 184
Examples of zone configuration polls............................................................ 190
Configuration poll Acknowledgement .......................................................... 198
Packet format of the zone group selection poll.............................................. 198
10

D.1
D.2
Header format .............................................................................................. 200

Entry format.................................................................................................. 202
E Remote TBus 2 interface .................................................. 205

F SSA messages format ....................................................... 206
F.1
F.2
F.3
F.4
F.5
F.6
F.7
Rules for future change of message format and explanation of content: ........ 207
Start of message body .................................................................................. 208
Message body .............................................................................................. 208
End of message body ................................................................................... 210
message supplementary text note ................................................................ 210
trailing message configuration information:.................................................. 210
End of message (message footer) ................................................................. 211
DNID Download Confirmation Format ........................... 212
Packet Format of LES file............................................. 213
I Acknowledgment Data report ........................................... 214

Index ................................................................................. 217
11

LIST OF FIGURES
Figure 4.1: Set-up Data Network...................................................................................30
Figure 4.2: Sending Manual Reports by use of command da.........................................31
Figure 4.3: Activating Interval Data Reporting..............................................................32
Figure 4.4:Illustration of tachograph control activated..................................................34
Figure 4.5: Activating Event Data Reporting .................................................................36
Figure 4.6: Rules for DNID in relation to filter feature. ..................................................37
Figure 4.7: Blocking reports with filtered blocking disabled. .......................................38
Figure 4.8: Antenna blocked reports with filtered blocking enabled............................39
Figure 4.9: Power reports with filtered power enabled. ...............................................39
Figure 4.10: Speed Limits .............................................................................................40
Figure 4.11: Zone example ...........................................................................................42
Figure 4.12: Automatic change of reporting interval.....................................................47
Figure 4.13: Precondition for group examples shown below. .......................................48
Figure 4.14: Case 1. Add DNIDs to group. ...................................................................48
Figure 4.15: Case 2. Add DNIDs to group (advanced). ................................................49
Figure 4.16: Case 3. Delete DNIDs. .............................................................................49
Figure 5.1: Group Poll Explanation...............................................................................53
Figure 9.1: Position Report Format ............................................................................. 169
Figure 9.2: T&Ts data report format........................................................................... 178
Figure 9.3: Message data reporting format................................................................. 179
Figure 9.4: Short packet descriptor ............................................................................ 183
Figure 9.5: Medium packet descriptor ....................................................................... 183
Figure 9.6: Ack reference........................................................................................... 184
Figure 9.7: Zone poll data........................................................................................... 185
Figure 9.8: Position format......................................................................................... 187
Figure 9.9: Radius format............................................................................................ 188
Figure 9.10: Width format........................................................................................... 188
Figure 9.11 Generation of checksum .......................................................................... 189
Figure 9.12: Fields used to calculate checksum .......................................................... 189
Figure 9.13: Calculation of the position field............................................................... 191
Figure 9.14: Data Field for the circle zone poll ........................................................... 192
Figure 9.16: Data Field for the polygon zone poll ....................................................... 195
Figure 9.18: Data Field for the polyline zone poll ....................................................... 198
Figure 9.19: Format when retrieving data from the data log. ...................................... 200
Figure 9.20: API header format................................................................................... 213
Figure 9.21: Acknowledgement data report Format ................................................... 214
Figure 9.22: Extended data for result code 6CH ......................................................... 215
12

LIST OF TABLES
Table 2.1 Automatic Operations ...................................................................................17
Table 4.1 Events generating Data Reports ....................................................................35
Table 5.1 Pollfile Header ..............................................................................................52
Table 5.2 DNID User Data .............................................................................................52
Table 5.3 Inmarsat Defined Polls ..................................................................................53
Table 5.4 T&T Defined Polls to Sub-address 1...............................................................53
Table 5.5 T&T Defined Polls to Sub-address 3...............................................................54
Table 5.6 Datareport sub-addresses.............................................................................54
Table 5.7 Sleep Mode Setup Poll ..................................................................................55
Table 5.8 Sleep Mode Acknowledge Report.................................................................55
Table 5.9 Sub-address 2 poll text field..........................................................................58
Table 5.10 Sub-address 2 poll function values ..............................................................58
Table 5.11 Sub-address 2 function 0 response..............................................................59
Table 5.12 Sub-address 2 function 1 response..............................................................59
Table 7.1 Possible data fields in a log entry..................................................................64
Table 7.2 Possible events creating log entries..............................................................65
Table 8.1 Nature of Land Mobile Alert ..........................................................................68
Table 8.2 GPS SBAS status values .................................................................................91
Table 8.3 Connection Status Summary........................................................................ 104
Table 8.4 GPS entries ................................................................................................. 112
Table 8.5 GPS Error Codes......................................................................................... 113
Table 8.6 GPS Status Interpretation ............................................................................ 113
Table 8.7 Nature of Alert. ........................................................................................... 121
Table 8.8 Channel Parameter Field Values................................................................. 132
Table 8.9 DNID Item List ............................................................................................. 133
Table 8.10 EGC Log Terms......................................................................................... 134
Table 8.11 ENID Item List ........................................................................................... 135
Table 8.12, Power on statistics reasons....................................................................... 139
Table 8.13 Receive Log Description ........................................................................... 140
Table 8.14 Transmission Log Description ................................................................... 142
Table 8.15 Hardware Status Screen Description ......................................................... 144
Table 8.16 Built in users and default passwords.......................................................... 144
Table 8.17 Overview of required user id / level of commands ................................... 145
Table 9.1 Command Status Reports ............................................................................ 163
Table 9.2 Message Delivery Reports .......................................................................... 163
Table 9.3 Command Errors ........................................................................................ 164
Table 9.4 Receiving Messages Info's........................................................................... 164
Table 9.5 GPS Info's .................................................................................................... 165
Table 9.6 General Status............................................................................................. 165
Table 9.7 General Status after Log file Changes ......................................................... 165
Table 9.8 LES Messages in case of a Pending/Rejected Call....................................... 166
Table 9.9 LES Messages in case of an Aborted Call .................................................... 166
Table 9.10 Transceiver Messages............................................................................... 168
Table 9.11 Link Test Messages ................................................................................... 168
Table 9.12 Test Mode Messages ................................................................................. 168
Table 9.13 Sleep Mode Messages............................................................................... 168
Table 9.14 Differences in VMS configuration between TT-3022D and TT-3026M......... 182
Table 9.15: Configuration poll command types .......................................................... 183
Table 9.16: Zone types ............................................................................................... 186
Table 9.17 Acknowledgement result codes ................................................................ 215
Table 9.18 Result codes for extended result field ....................................................... 215
13

INTRODUCTION
1.1 APPLICABILITY
This document describes the features of the Thrane & Thrane Inmarsat-C Satellite
Transceiver: the interface, the automatic operations, navigational equipment
connection, and the polling and position reporting service.
The document applies to the following Transceiver types:
TT-3026L easyTrack for Landmobile.
TT-3026M easyTrack for Maritime.
TT-3026S easyTrack for Maritime with Safety Net.
TT-3000SSA easyTrack for Maritime SSA installation.
TT-3026D easyTrack Non-SOLAS and Distress.
TT-3026C easyTrack SOLAS.
This document applies to software version 1.04 and up.

A TT-3026C, TT-3026D and TT-3026S may only be installed with a DTE connected to the
transceiver and the end user may only operate the transceiver through the DTE.
1.2 RELATED DOCUMENTS AND REFERENCES

[1] TT 99-110036, Internet Gateway User Manual
[2] TT 99-103879, PSDN User Interface Manual
[3] TT 98-116078, TT-3026L/M Installation Manual
[4] TT 98-116079, TT-3026L/M User/Operators Manual
[5] TT 99-104209, CAPLIB - Communication Library
[6] http://www.thrane.com/ contains information on how to contact the local Thrane
& Thrane distributor for further assistance.
[7] TT-6000 Inmarsat-C Land Earth Station API-Header Description
Introduction
14
Applicability

1.3 ABBREVIATIONS
A number of abbreviations are used in the text. The most important ones are:
<CR>
The ASCII carriage return character, 0DH.
<ETX>
The ASCII end-of-text character, 03H.
<LF>
The ASCII linefeed character, 0AH.
<SPACE>
The ASCII space character, 20H.
<STX>
The ASCII start-of-text character, 02H.
BGPS
Built in GPS
DNID
Data Network ID
LES
Land Earth Station.
LES ID
Land Earth Station identifier (number).
MEM
Macro Encoded Message
MRCC
Maritime Rescue Coordinating Centre
NCS
Network Co-ordinating Station.
PU
Programmed Unreserved Data reporting
SSAS
Ship Security Alert System
[x.xx]
Features are only supported FROM fx. [2.15] (software major- and minor version)
The STX and ETX characters are used by the TT-3606E, TT-3606C and TT-10202A
software to identify certain important information.
1.4 THE INTERFACE

The transceiver provides a text-based interface on its serial communications port. The
default settings for the serial port are:
4800 baud
No parity
8 databits
1 stopbit
See the command SET -c Show or Set Serial Port Parameters for an explanation on how
to change these settings.
The concept of the interface is to treat the transceiver as a message mailbox. There are
commands to transfer files to and from the transceiver and commands to control the
satellite link. When the transceiver issues the colon : prompt, just type in the desired
command.
A typical example of a command description is:
ncs -r <ncs_id>
where "ncs" is the command name, "-r" is the option switch and "<ncs_id>" is the
parameter value that should be supplied.
Short forms are available for most commands; usually they are the first two letters of the
full command name. To find the short form of a specific command, see the Command
Reference chapter. The commands are not case-sensitive.
The prompt sequence from the Transceiver is in this notation:
<Previous command > <CR><LF>
:<SPACE>a
Note that there is a space character after the colon character.
Introduction
15
Abbreviations

The results of the commands are returned in INFO or ERROR messages. By default,
these messages are not displayed but stored in a log, which can be accessed using the
STATUS -l Show Status Report command. This is called silent mode. Silent mode can be
turned off using the command SET -r Silent Mode. When silent mode is off, all INFO and
ERROR messages will be printed directly to the console. A list of messages can be
found in the chapter Info and Error Messages.
1.5 CHANGES FROM TT-302X C-TRANSCEIVER

1.5.1 ENVIRONMENT VARIABLES
Only two environment variable is fully implemented in the TT-3026L:
TZ, time zone
PRNFILTER, disable log or status printing

Use PRNFILTER=LOGS to disable printing of Rx, Tx and EGC logs,
PRNFILTER=STAT to disable printing of INFO and ERROR messages
or PRNFILTER=LOGS,STAT to disable both.
A number of variables are partly implemented for backward compatibility reasons. The
values of these variables are set to default at power-on. The following lists environment
variables that are preset at power ON:
1: POSFORMAT=PU
2: PRINTER=NO
3: PPAGING=NO
4: PLINES=61
5: FFEED=NO
6: OCEANSHIFT=SIGNAL
7: PCHARS=80
8: PCUTLN=NO
These variables cannot be changed. All other environment variables are lost on power
down.
1.6 THE CAPLIB SOFTWARE PACKAGE

The CapLib is a C source code package which can be used to create a communications
application that uses the Inmarsat-C system and a Thrane & Thrane Transceiver on a
DOS, Windows 95, Windows 98, NT or Windows CE platform.
Please refer to TT 99-104209, CAPLIB - Communication Library
Introduction
16
Changes From TT-302x C-Transceiver

GENERAL TRANSCEIVER PROPERTIES

2.1 AUTOMATIC OPERATIONS
The Transceiver has the following automatic operations built in:
Operation
Mobile Type
Read Navigational data from internal GPS
L/M/S/D/LM, TT-3000SSA and TT-3000E
Check Bulletin Board Error Rate (BBER) every 8.64 seconds. At a
BBER of 80 an info is generated and a scanning will begin.

Automatic spotbeam scanning every 24 hours.
Requesting data and/or sending position information at regular
intervals.
Clean-up of the logs when needed.
Network version check every 24 hours. If the Network version
stored in the Transceiver's LES table, is different from the NCS

TDM's, a login will commence.
Clean-up of the file system when needed.
If a tuning operation in a protocol fails, the Transceiver will
check the LES Network version number against the NCS TDM
Network version, and if they differ a login will be issued.
Automatic correction of Transceiver CMOS clock time when
deviation to the GPS UTC reaches 10 sec.
Table 2.1 Automatic Operations
2.1.1 POWER ON OPERATION

The Transceiver will perform the following operations when turned on.
LOGIN IF NECESSARY
By default the transceiver will login at the current ocean region if logged-out. This
default setting can be changed so that the transceiver login on the ocean region with
the nearest satellite (See the command SET -ns).
If using login on nearest satellite: The transceiver use the last known position to decide
which ocean region to use. Only allowed ocean regions are considered when deciding
which ocean region to use (See 2.1.2 ).
If the login for some reason fail the transceiver will try to find another ocean region.
STORE INFORMATION
The time and date of power-on, login and logout are stored.
2.1.2 AUTOMATIC OCEAN REGION SHIFT
This feature is very useful when the vessel/vehicle operates in different ocean regions.
The transceiver will perform automatic scanning and ocean region shift, if the signal
strength has been bad for a few minutes or at 24 hours interval. The ocean region shift
can be disabled or restricted to one or more allowed regions (See below and the se -o
command).
General Transceiver Properties
17
Automatic Operations

The environment variable OCEANSHIFT is for backward compatibility only.

AUTOMATIC OCEAN REGION SHIFT
Preferred ocean setting
Allowed ocean(s) setting
Automatic ocean-region shift

behavior
Preferred ocean set to "NONE"
Allowed ocean set to "NONE"
Scanning current ocean region,

and login on the strongest spot.
If synchronizing to current ocean
region fails the other regions are
scanned.
Allowed ocean set to one or more
oceans (W, E, P and I)

If synchronizing to current ocean
region fails the allowed regions are
scanned.
Preferred ocean set to an ocean
Allowed oceans setting has no
Scanning preferred ocean region,
(W, E, P or I)
effect.

If synchronizing to the preferred
ocean region fails info is sent to the
operator. The transceiver will be
tuned to preferred ocean
Automatic ocean shift does not apply for the TT-3000E mini-C GMDSS System - ocean
shift must be initiated by operator.
2.1.3 AUTOMATIC LOGIN
The Transceiver will start an automatic login under the following circumstances:
When a scan command finds a different NCS with a stronger signal than the current
NCS. The transceiver will login to the new NCS. If this fails, it will return to the
original NCS.
Every 24 hours the transceiver will check if the Network Version Number of the
stored LES Table and the NCS TDM channel are different. If they are different the
transceiver will login again on the current NCS TDM to get a new LES Network
Table.
If a tuning operation during a protocol failed the transceiver will check if the
Network Version Number of the stored LES Table and the NCS TDM channel are
different. If they are the transceiver will login again on the current NCS TDM to get
a new LES Network Table.
When the transceiver is turned on it will start a login to the current NCS TDM if it's
status shows that it is not logged in.
The transceiver will make an automatic login to a new NCS if the Inmarsat-C signal
has been bad for a few minutes (does not apply to the TT-3000E mini-C GMDSS
System).
2.2 AUTHORITY LEVELS

Many commands and features in the transceiver require that the user be at a certain
authority level. This system exists in order to allow system administrators of various
sorts to configure the transceiver with settings, which the normal users cannot change.
18
Authority Levels

Authority level protection also prevents users from inadvertently changing settings,
which may interfere with the correct operation of the transceiver.
A user can acquire a specific authority level using the SU command (see page 144). The
user supplies the desired level and the password for that level. Users can change the
password for each level, provided that they are at a sufficient authority level. The levels
are:
User Name
Default Password
Normal
(empty)
Description
Normal user level. This authority
level is the default after boot-up.
Super
Super
Super user level.
Sysadm
sysadm
System administrator level.

Intended for system
administrators
At a given authority level, the user has access to all the features at that level in addition
to those at the lower levels.
Every command can be assigned a required authority level if it is necessary to reduce
the set of commands that are available to users at lower authority levels. A user can set
the required authority level to his/her own level or lower.
Authority levels also affect Data Network IDs (DNIDs), interval programs and event
programs. Each DNID is given an authority level. Access at this level is required to
modify the properties of the DNID and the programs that are associated with it. See also
Data Reporting on page 29.
All users except "normal user" are required to change their password the first time they
use the SU command.
2.3 FILE SYSTEM

The file-system and all files are stored in non-volatile RAM.
The files system has the following specification/characteristic (as of [ver. 2.12]):
Total allocated memory for RAM-disk: 179.200 bytes
Max. file creation: 1400 files.
Maximum open files: 16
Internal use of file-priority.
Terminal command supporting transferring/creating, deleting, typing and listing

files.
19
File System

2.3.1 FILE PRIORITIES

The file-system operates with the following internal priorities, which cannot be altered
by normal users:
Priority
Description
File naming
System data-setup files
ZoneFile.Dat, DnidStr.Dat,
Highest
Datarep.dat
System log files
_EGCLOG, _TXLOG, _RXLOG
Poll files
POLL.xxx
and ERROR.LOG.
Lowest
Incoming messages/files
IN.xxx
EGC messages/files
EGC.xxx
User files
*.*
These priorities are mainly used in two situations:
When deleting files. (Note: a normal user cannot delete system files).
When creating or extending files. If no memory is left for creation or extension of a

file, an internal mechanism automatically tries to release memory from the oldest
files that have a priority lower than or the same as the new file.
2.3.2 FILE COMMANDS

The terminal interface provides the following commands for file operations. See the
Command Reference chapter for details about each command.
DIRirectory / LS. Displays a list of files.
TYpe. Displays the contents of file(s).
TRansfer. Transfers a file from the console to the RAM-disk.
DELete/RM. Deletes one or more files.
SENDFILE/SF. Sends a file using the X-modem protocol.
RECVFILE / RF. Receives a file using the X-modem protocol.
2.4 SLEEP MODE (POWER EVENTS)

The power controlling of the transceiver always follows one of three protocols.
Sleep Mode Disabled. (Default configuration)
Sleep Mode Enabled with or without Interval and fixed time wakeup.
2.4.1 SLEEP MODE DISABLED

If Sleep mode is disabled configured as SL -c then
If the transceiver is switched off, the transceiver will indicate this by sending
"Power Down Report" and "Power Up Report" when supply power has been reestablished. The "Power Down Report" includes the last known position before
the power was removed. The "Power Up Report" includes the current position.
20
Sleep Mode (Power Events)

Note, when sleep mode is disabled, either through the terminal of via. poll, a
leave sleep mode report is sent.
2.4.2 SLEEP MODE ENABLED
The sleep mode enabled can be configured with or without Interval and fixed time
wakeup.
Sleep mode is configured without wakeup using SL -i 0,0,0,0.
This configuration is used when it is necessary to separate "supply power removed
abruptly" from " supply power switched off nicely".
If the supply power is removed abruptly then the transceiver will indicate this
by sending "Power Down Report" and "Power Up Report" when supply power
has been re-established. The "Power Down Report" includes the last known
position before the power was removed. The "Power Up Report" includes the
current position.
If the supply power is removed using the remote switch then the transceiver
will indicate this by sending an "Enter Sleep Mode Report", before the power is
switched off and "Leave Sleep Mode Report" when transceiver is switched on
again. The "Enter Sleep Mode Report" includes position at the time of
transceiver is switched off. The " Leave Sleep Mode Report" includes position
at the time of transceiver is switched on again.
Sleep mode is configured with wakeup using SL -i x,x,x,x,x (x is any value, except
from all 0).
This allows the transceiver to save power/battery and periodically wakeup in
interval of 1-24 hours and transmit data-report etc. The transceiver always
automatically turns off the power, after transmission of the last data-report.
The configurations also setup the transceiver to wakeup every 24 hours at a fixed
time for a fixed period of time (from 15 to 60 minutes). During this fixed time
wakeup, the transceiver can be reconfigured, receive messages etc.
2.5 I/O INTERFACE

The transceiver contains an IO-interface of six In/Out open collector pins. If the
transceiver is part of a 3026D system pins 1,2,5 and 6 will be reserved for this purpose
(see paragraph 6.2 ). If the transceiver is part of a SSA system all six pins will be
reserved for this purpose (see paragraph 6.2 ). For the TT-3000E mini-C GMDSS
System pin 1,2,3 and 4 are reserved. Otherwise only the first pin is reserved for Land
Mobile Alert (see paragraph 6.1 ) and the remaining five are available for any userpurpose. (See Ref. [3] TT 98-116078, TT-3026L/M Installation Manual).
Before use, the io-pins must be configured using the IO command as described in
paragraph 8.17 IO
When using the Zone Group/Group list Selection Poll (see paragraph 5.3.2 ) for
changing output status, make sure to configure the io-pins as output. Poll for reading
I/O status is possible for all io-pins at any time.
21
I/O Interface

2.5.1 INPUT PINS

Any io-pin can be configured to generate any of the T&T predefined internal event,
using the "IO -i ..." command, as described in paragraph 8.17.2 .
Example: "IO -i 2,0,1,2" configures pin 2 to generate an internal event causing the
transceiver to change between long and short reporting interval.
Configuring short and long reporting interval is described in paragraph 8.23.5 PG -e
Extended program set-up and 8.23.12 PG -l Set Long Interval and Minimum Distance.
2.5.2 TACHOGRAPH INTERFACE PIN
One user selectable io-pin can be configured to function as a tachograph interface input
pin.
A tachograph is a unit that keeps track of the speed and motion of a vehicle. Connecting
a tachograph to the transceiver (normally through a suitable interface converter) will
make it possible to gather statistics of driven speeds and distances.
The main function of the tachograph interface is to count transitions (edges) on the
incoming signal; both positive edges (going from low to high input level) and
negative edges (going from high to low input level) are counted. The maximum
input frequency is 1.0 Hz (giving 2 edges per second).
Beside distance registration, the tachograph support function detects periods where the
vehicle is stopped or parked. This information can be included in reports (see sections
4.2 and 8.9.4 ), control the transmission of reports (see sections 4.4.2 and 8.23.5 ) and
control the data-logging function (see sections 7
and 8.20 )
This interface is configured through the IO -t command as described in paragraph
8.17.5 .
2.5.3 OUTPUT PINS
Output pin can be configured to change on any of the T&T predefined internal event
using the "IO -o ..." command as described in paragraph 8.17.3 IO -oOutput-pin setup.
Examples:
1. "IO -o 3,0,1,2" configures pin 3 to change level, when receiving Enter/Leave
Zone events.
General configuration of zones etc, see paragraph 4.11 Surveillance zones.
2. "IO -o 4,0,8,7" configures pin 4 to change level, when receiving Above/Below
Speed Limit events. General configuration of speed limit etc, see paragraph 4.8
Speed Limit Event.
3. "IO -o 4,0,5,6" configures pin 4 to change level, when receiving GPS Blocked
/Unblocked events, See paragraph 4.7.3 GPS Blocked Events.
4. IO -o 5,0,1,9 configures pin 5 to go low when a zone is entered and to go
high on a Change Output A event. The latter is a way of making an output pin
respond to an input pin by programming an input pin to generate this specific
event (e.g., the command IO -I 2,0,3,0: Generate Change Output A when pin
2 goes low).
22
I/O Interface

As can be seen in examples 2 and 3, several (up to 16) events can be assigned for a
single out-pin
2.6 GPS UNIT

The transceiver has a built-in GPS receiver that provides the current time and position.
The GPS receiver works by receiving timing signals from the GPS satellites. With later
versions (2.21 or later) it has become possible also to receive SBAS signals.
2.6.1 SBAS
SBAS is originally created for aviation control purposes and the advantage of having
this augmentation is two-fold:
Atmospherical correction that generally makes it possible to obtain greater

precision.
Integrity monitoring that increases the reliability of the GPS system by

disregarding faulty or imprecise signals.
Dispite the primary purpose being aviation, other GPS applications may also benefit
from the SBAS service.
There are a number of SBAS systems each covering different geographical areas.
WAAS in North America.
EGNOS in Europe and Africa
MSAS in Asia and Australia
At the time of writing only WAAS is fully functional; the other systems are under
development.
Unlike the normal GPS signals, the SBAS signals are broadcast through geostationary
satellites that are identified with PRN numbers in the range 100 to 132. The GPS
receiver in the TT-3026 is capable of choosing an SBAS PRN itself, but that is not
recommended for normal use. If, e.g., a WAAS signal is used in Europe, the advantage
is questionable at best since Europe is outside the coverage area of WAAS (though not
necessarily outside reach of the WAAS signal). The GPS receiver is not able to detect
this from the received signals and therefore it is generally required to choose the SBAS
PRN manually.
Please note that PRN allocation is subject to change, particularly for the systems not yet
in full operation.
Furthermore, systems may send the augmentation information as test messages (type 0
messages). Generally test messages should not be used since there is no guarantee of
the quality or availability. However for test or evaluation purposes the TT-3026 may be
configured to accept test messages.
Updated information on SBAS PRNs and test transmissions is provided by these
organisations:
The European Space Agency (for EGNOS)
The Federal Aviation Administration (for WAAS).
23
GPS unit

The Japanese Civil Aviation Bureau (for MSAS)
Please see the GPS s command (section 8.14.4 ) for details on SBAS configuration.
The SBAS reception status is recorded with the position and can be reported by adding
the Extra precisson 0.001 data. See section 8.9.14 and Appendix A.1 for more
information.
The service disabled by default [2.21]
24
GPS unit

MESSAGING
3.1 OVERVIEW
Sending a message with the transceiver involves two steps.
1. Transfer a file containing the message to the transceiver using the "tr" command
2. Transmitting the file using the "tx" command
When a message transmission is initiated, the transmit-log is updated. Since the log and
the transmitted file are preserved after a reboot, the transceiver can send the message
after a reboot.
3.2 FILE FORMAT

Depending on the destination the file may, apart from the message itself, contain the
destination addresses. In the following the address format for the supported
destination are described. Multiple address lines of the same type (e.g. PSTN) can be
specified. After the address information, an empty line must be inserted.
3.2.1 TELEX ADDRESS
The file shall contain the address information at the beginning of the file. Telex
addresses are defined in the ITU-T U.80 recommendation and have the general format.
<International telex number><+>[suffix]<CR><LF>
Currently only the following suffixes are recognized.
1. Detection of expected destination answer-back as specified with the '/' switch
2. Attention line information, which might be added to the message header, as
specified within parentheses
3. Request for message delivery acknowledgement as specified with the 'ACK' switch
4. Delayed delivery request as specified with the ',Dxx' switch
5. Time limited delivery as specified with the ',Lxx' switch
In connection with (1) it should be noted, that answer-back checks are not applicable
for MES to MES calls.
3.2.2 PUBLIC SWITCHED TELEPHONE NETWORK (PSTN) ADDRESS
The file shall contain the address information at the beginning of the file.
<International PSTN number><+><CR><LF>
Messaging
25
Overview

3.2.3 PUBLIC SWITCHED DATA NETWORK (PSDN ) X.25 ADDRESS

The file shall contain the address information at the beginning of the file.
<International PSDN number><+><CR><LF>
3.2.4 CLOSED DATA NETWORK ID (DNID) ADDRESS
The file contains no address information. DNID specified at the command line.
3.2.5 SPECIAL ACCESS CODE (SAC) ADDRESS
The file shall contain the address information. The address format depends on the
service and the LES configuration, contact the LES operator for details. The special
access code addressing is selceted with the -t 6 option and the SAC is specified at the
command line with the -e NN option.
Examples of sending email using the SAC below.
3.2.6 ADDRESS PREFIX
The Telex, PSTN and PSDN addresses may be prefixed with a two-digit prefix. The
prefixed store and forward service must be used.
3.3 MESSAGE ALPHABETS

Messages can be transmitted using a 5-bit or a 7-bit alphabet or 8-bit data. Alphabet or
data can be selected with the "-l" option of the "tx" command. When a message is
transmitted the transceiver assumes that the file is in ASCII format and will convert the
message to the selected 5 or 7-bit alphabet. If 8-bit data is selected no conversion are
performed.
The 5-bit alphabet (ITA2) defined in ITU-T S.1 with some Thrane & Thrane additions
consist of the following characters.
the 26 Latin alphabetic characters: a b c d e f g h i j k l m n o p q r s t u v w x y z
decimal figures: 0 1 2 3 4 5 6 7 8 9
Punctuation marks and miscellaneous signs: . , : ? + - / = ( )
Thrane & Thrane additions: $ # @ %
Other characters will be converted to: ?

The 7-bit alphabet (IA5) defined in ITU-T T.50. Removing the most significant bit does
conversion to this alphabet from ASCII.
Messaging
26
Message Alphabets

Destination network
Telex
PSTN
PSDN
DNID
SAC
ITA2
ITA2
ITA2
ITA2
ITA2
IA5
IA5
IA5
IA5
IA5
Data
Data
Data
Data
Applicability
3.4 INMARSAT NETWORK DESTINATION CODES

Destination
All regions
network type
code
AORE
POR
IOR
AORW
Telex (TNIC)
PSTN
580
581
582
583
584
870
871
872
873
874
1110
1111
1112
1113
1114
(PNIC)
PSDN
(DNIC)
3.5 EXAMPLES
Sending a message to another Inmarsat-C Mobile using 5-bit telex, via EIK
LES(AORE)
Content of file named "ex1.txt"
581492380021+<CR><LF>
<CR><LF>
this is a test telex message with a inmarsat-c mobile destination.
The message is transmitted with the command

tx -c 104 -l 6 -t 0 -s 0 ex1.txt
Sending a multi-addressed telex message using 7-bit to the following

An Inmarsat-C mobile requesting acknowledge and a 1 hour delayed transmission.
An Inmarsat-C mobile requesting acknowledge and a limited delivery of 1 hour.
A telex receiver with an attention line.
581492380046+,ack,D01<CR><LF>
581492380237+,ack,L01<CR><LF>
5519298+(ATTENTION BRP)<CR><LF>
<CR><LF>
This is multi-addressed telex.

tx -c 104 -l 0 -t 0 -s 0 ex2.txt
Sending a multi addressed message to PSTN destinations

An Inmarsat-C mobile
A FAX machine
Messaging
27
Inmarsat Network Destination Codes

871492380046+<CR><LF>
4539558888+<CR><LF>
<CR><LF>
This is multi-addressed message to an Inmarsat-C mobile and a FAX
machine at the PSTN network.
tx -c 104 -l 7 -t 1 -s 0 -e T30 ex3.txt
Sending a message to another Inmarsat-C mobile using PSDN destination and 8bit data.
1111492380046+<CR><LF>
<CR><LF>
This is a message to an Inmarsat-C mobile at the PSDN network.

tx -c 104 -l 7 -t 3 -s 0 ex4.txt
Sending an E-mail using EIK LES using the Special access code(-t 6), and the
email destination extension for EIK LES(28).
TO:AfterSalesService@tt.dk<CR><LF>
CC:492380046@inmc.eik.com<CR><LF>
SUBJECT:Email Test<CR><LF>
<CR><LF>
(your email text goes here)
The CC: and SUBJECT: fields can be omitted
The command to send the message file (called ex5.txt) is then

tx ex5.txt -c 104 -s 0 -t 6 -l 0 -e 28
3.6 DNID DOWNLOAD CONFIRMATION

[2.14]
This is a special message that may be delivered in a DNID mailbox indicating that the
issuing transceiver has had the DNID inserted and activated. The format of the message
is found in appendix G . After delivering the activation message the DNID can be
used just like a DNID downloaded with a poll (see Remote Configuration and Polling,
Chapter 5 ).
Note that only some transceivers can send this message; it only applies to transceivers
that have a special factory configuration and are put into use according to a special
agreement with a LES.
Contact the LES operator if a DNID download confirmation message is received in the
DNID mailbox from an unknown transceiver or from a transceiver that should not
contain that DNID.
Messaging
28
DNID Download Confirmation

DATA REPORTING
4.1 INTRODUCTION
A Data Report is a term used for a datagram carrying data from a mobile to a LES.
The Data Report contains routing information and user data. A Data Network
Identification number (DNID) and a LES number make the destination. A Data report is
routed to a mailbox in the LES. Each mailbox is identified by the DNID. A DNID is
unique in the domain of a specific LES.
The User Data field consists of a maximum of 32 bytes. The definition and layout of the
user data field are described in Position Report Packet Format, appendix A
For the transceiver to be able to send any Data Reports it must be associated with one
or more DNIDs (max. 64 DNIDs). The DNID is loaded into the transceiver via poll (see
Remote Configuration and Polling, Chapter 5 ). The LES operator controls the DNID
loading procedure.
A number of mobiles may be associated with the same DNID. Each mobile within the
group is then identified by a member number (1-255). The member number is included
in the Data Report as a part of the routing information.
The satellite protocol controlling the transmission of the Data Reports is not a reliable
protocol. As a consequence, the Data Reports may be lost due to collisions or may be
transmitted twice (missing acknowledge).
4.2 SETTING UP DATA NETWORKS

A DNID and a LES number identify the Data Networks. The DNID and LES are loaded
into the transceiver by means of a poll.
As the DNID is loaded into the transceiver it is set up by use of the DN command (see
chapter 8.9 )
A number of parameters are associated with each DNID. These parameters specify the
format of the Data Reports routed by using the DNID.
The parameters associated with a specific DNID is set-up by use of option -p (dn -p).
By default a DNID is associated with a set of default parameters. The default parameters
are stored by use of option -f (dn -f).
In the following example a Data Network is set up to transfer Data Reports including
Additional Speed and Course. Furthermore, the DNID is protected by setting the
authority level (level 2 corresponds to the system administrator).
: su
Current user: sysadm
: dn -d
Entry Provider Name
0
: Thrane
1
: Thrane
2
: Thrane
3
: Thrane
: dn -d 0
Data Reporting
S
01
01
01
01
29
LES
004
104
204
304
DNID
8048
8048
8048
8048
Mem
234
234
234
234
Sub
1
1
1
1
Introduction

LES
004
DNID
8048
Mem
234
auth
2
cat
0
date
1
io
0
speed
0
1pack
0
ustr
0
prec
0
tacho
0
: su normal
Enter password:
: dn -d
Entry
:
Provider Name
LES
DNID
Mem
Sub
: dn
Usage: dn <option>
-o <LES>,<DNID>,<mem>,<sub>,
<predef>,<provider>
-c <entry>[-<entry>]
-d [<entry>]
-e <entry>,<groupid>
-f <auth>,<cat>,<date>,<iopin>,
<speed>,<1pack>,<ustr>,
<reso>,<tacho>,<auint>,<auevt>
-l [<memindex>,<memcode>]
code
-m <entry>[,<memindex>,<memcode>]
-p <entry>,<auth>,<cat>,<date>,<io>,
<speed>,<1pack>,<ustr>,<reso>,<tacho>
-s <entry>,<'D'|'E'>
-t <entry>,[<tmemcode>,<string>]
-tb <entry>,[<tmemcode>,<size><CR><string>]
-a
-fa [<dautgrp>]
-g <entry>,[<obdr>]
-fg [<obdr>]
:
:
:
:
:
Create DNID
Delete DNID
Display DNID status
Change DNID Group
: Default data format

: Display/Change user default mem: Display/Change mem-code
:
:
:
:
:
:
:
:
Data format
Change DNID status
Setup UserString
Setup binary UserString
Disable auto-grouping
Default auto-grouping
Only basic reporting
Default only basic reporting
Figure 4.1: Set-up Data Network
4.3 MANUAL REPORTS

A Manual Report is a Data Report, which is initiated manually by the user. The Data
Report can be initiated by use of poll (remote access) and by use of the command Data
(local).
Data reports initiated by poll is described in the Remote Configuration and Polling
chapter (command Request response).
When initiating Data Reports using the Data command, it is possible to customize their
contents. Using the option -o the time and position will be included. Using the option -b
it is possible to include user data.
The following example shows how to send a data report to LES 102, DNID 10289,
including time and position and 2 bytes of user data. The status of the transmission is
stored in the log.
The short name of the command Data is da.
: da -?
Send data report immediately:
Usage: da [-o [-z <mem attr>] [-l]] [-b <byte cnt>] <LES>,<DNID>,<mem> [<data>]
Append user data to an active program:
da [-p] [-o] [-b <byte cnt>] <LES>,<DNID>,<mem> [<data>]
-b
: Number of bytes in <data> field
-o
: Insert position in data report
-p
: Append data to buffer
-z
: Set macro and attribute field
Data Reporting
30
Manual Reports

-l
: Force category to land mobile
:
: da -o -b 2 102,10289,3
12
: st -l
INFO 482: Position report issued
: st -l
INFO
:
481: Position report successful
Figure 4.2: Sending Manual Reports by use of command da
4.4 INTERVAL REPORTS

An Interval Report is a Data Report that is automatically sent by the transceiver. The
transmission of the Data Report is repeated with a fixed period of time (interval).
Interval Reports are set up by poll (remote access) or by the command PG (local).
Command PG creates and configures Interval Report Programs. Up to 15 Interval
Programs can be defined and each program runs independently and at its own interval
Interval Programs that are set-up via remote access cant be changed by the command
PG, similarly Programs set-up by command PG (local) cant be changed via remote
access (poll).
Interval Programs set-up by poll is described in Chapter 5
and Polling, (command PU Program/initiate/stop).
Remote Configuration
The following example shows how to set up a local Interval program. The Interval
program is sending Data Reports with a period of 100 frames (one frame = 8.64 sec.),
starting at frame 5920 the 26 November 2001. The destination is LES 002, 102, 202, 302
(all four oceans are covered) and DNID 10289 (same in all four oceans). The mobile has
been given member number 3.
: pg -d
Connection
0: closed
1: closed
2: closed
3: closed
: pg -?
Program
Ocean region
Usage: pg <option>
-o <LES>,<DNID>[,<mem>]
: Open Program
-c <conn>
: Close Program
-p <conn>,<interval>[,<start frame>] : Program setup
-i <conn>[,p]
: Initiate program
-s <conn>
: Stop Program
-d [<conn>]
: Display program status
-v [<conn>]
: Display extended program status
-e <conn>,<remote>,<rand>,<zoneint>,<retxfail>,<store>,
<longshortinterval>,<mindist>,<tacho>,<wksch>
: Extented Program setup
-l <conn>,<longinterval>,<distance> : Set long interval, minimum dist.
-a <conn>,<alert controlled>,<alert interval>
: Set alert control.
-b <conn>,<mask>
: Bitcontrol
-fp <interval>[,<start frame>]
: Default program setup
-fe <remote>,<rand>,<zoneint>,<retxfail>,<store>,
<longshortinterval>,<mindist>,<tacho>,<wksch>
: Extented default program setup
-fl <longinterval>,<distance>
: Set default long interval, minimum dist.
-fv
: Display default extended program status
-fa <alert controlled>,<alert interval>
: Set default alert control.
Data Reporting
31
Interval Reports

: pg -o 002,10289,3 102,10289,3 202,10289,3 302,10289,3

INFO 459: Connection no. 0 opened
: pg -d
Connection Program
0: local
none
1: closed
2: closed
3: closed
: pg -p 0,100
Ocean region
002,10289,3 102,10289,3 202,10289,3 302,10289,3
: pg -d 0
LES
002
102
202
302
DNID Mem
10289
3
10289
3
10289
3
10289
3
Start at
Next at
End at
Status
OK
0
0
0
0
Err Inter
0
100
0
100
0
100
0
100
: 687
(03-01-00
:
:
: 0 - OK
Sub
0
0
0
0
Rd
4
4
4
4
Auth
0
0
0
0
Sub
1
1
1
1
Rd
4
4
4
4
Auth
0
0
0
0
Sub
1
1
1
1
Rd
4
4
4
4
Auth
0
0
0
0
01:38:56)
: pg -i 0,p
: pg -d 0
LES
002
102
202
302
DNID Mem
10289
3
10289
3
10289
3
10289
3
Start at
Next at
End at
Status
OK
0
0
0
0
Err Inter
0
100
0
100
0
100
0
100
: 687
(03-01-00
: 687
(03-01-00
:
: 0 - OK
01:38:56)
01:38:56)
: pg -s 0
: pg -d 0
LES
002
102
202
302
DNID Mem
10289
3
10289
3
10289
3
10289
3
Start at
Next at
End at
Status
OK
0
0
0
0
Err Inter
0
100
0
100
0
100
0
100
: 687
(03-01-00
:
:
: 0 - OK
01:38:56)
Figure 4.3: Activating Interval Data Reporting
Data reports normally contain a MEM code that can be used to determine the origin or
nature of the report. Interval reports use the following two codes:
Reporting
MEM code
Description
Normal
11
Normal interval position reporting
Alert reporting
93
Alert reporting active. See section 6.4 Alert reporting for

more information on this topic.
Data Reporting
32
Interval Reports

4.4.1 WEEK SCHEDULE

A standard interval report program will keep on reporting periodically regardless of
the time of the day. However, in some situations it may be convenient (and more
economical) to skip data reports in some periods of the week. Typically this can be
used if, e.g., frequent interval reporting is required but only within ordinary working
hours. To achieve this, a week schedule can be set up to permit only some of the
interval reports to be sent.
The following steps set up the week schedule control:
The interval program must be set up to send reports as desired; this is

described earlier in this section.
Additionally the program must be set up to subject to the week schedule;

this is done with the pg -e command that described in section 8.20.3 PG -e
Extended program set-up (look for the < wksch> option).
Finally the week schedule is to be set up using the weeksched command

that is described in section 8.37 Weeksched.
Note that the week schedule only applies to interval reports; manual reports and event
reports are sent when requested regardless of the week schedule settings.
4.4.2 TACHOGRAPH CONTROL
As the week schedule function described above, the tachograph control may used to
suppress interval reports that are irrelevant in some situations.
The function is related to the tachograph control that is described in paragraph 2.5.2
and the main principle is that interval reports can be suppressed when the tachograph
is in stopped state.
However, the function of the tachograph control is more complex than a simple
started/stopped filter in order to give an interval reporting scheme that also
provides some information in the stopped state.
The rules that control the interval reporting in tachograph control mode are:
Ordinary interval reports are suppressed when the tachograph is in

stopped state - with the following exception
Interval report number two that occur in stopped state is not suppressed.
This report provides the information that the state changed to stop and
also give the GPS position.
If one or more interval reports have been suppressed while in stopped

state, an extra report will be sent when the tachograph changes to
running. This report will be sent as soon as the tachograph state changes
and it is not synchronized to the report interval settings.
Although these rules may seem complex, they will ensure that the transceiver reports
relevant state changes as soon as possible without exceeding the number of data
reports that are determined by the basic interval settings of the program.
Data Reporting
33
Interval Reports

Ordinary reports
block
Tachograph state
run
block
run
stop
Sent reports
ordinary
ordinary
extra
ordinary
Figure 4.4 shows an example that illustrates how the tachograph control works:
Figure 4.4:Illustration of tachograph control activated.
Enabling of the tachograph control on an interval program is done using the pg -e

command described in section 8.23.5 PG -e Extended program set-up (look for the
<wksch> option).
The tachograph control can be combined with the week schedule control (see section
4.4.1 for more details). Note that only interval reports can be controlled by the
tachograph; manual reports and event reports are sent when requested regardless of
the tachograph state.
4.5 EVENT REPORTS

An Event Report is a Data Report, which is initiated because an event occurred.
The Event Programs are set up by use of the command EV.
The event Data Report contains time and position and a MEM code indicating the type
of event.
Following events can be programmed to trigger a Data Report:
Data Reporting
34
Event Reports

Event
Thrane & Thrane
Description
Default MEM code

PowerCtrl
64 (power-up)
At power-up two Data Reports are sent, one Power-down
66 (power-down)
report, including the last known power down

time/position, and one report including the power-up
time/position.
Antenna
68
-- Not implemented --
Disconnected
Antenna Blockage
(antenna is built in)

69
Data report sent when Inmarsat-C sat. is blocked

(actually the report is sent when the Inmarsat-C is
unblocked afterwards, but with the original postition and
time).
Stored Position
70
IO-pin
71
Zone
72 (Enter Zone)
If Zone Events is set to 2, no event reports will be sent
73 (Leave Zone)
when moving from one zone to another - only when
Any changes of IO-pin status generates a data report

including current status of the IO-pins [1..5].
moving from outside zones to inside zones and vice

versa.
Sleep Mode
74 - 79
-- Unused --
80 (enter sleep mode)
Data Reports are sent when the sleep mode function is
81 (in sleep mode)
activated/deactivated and while the transceiver is waked
82 (leaving sleep mode)
up (in sleep mode).
83 (enter fix-time)
NOTE: the sleep mode function MUST be activated (see
section 8.29 Sleep and section 5.2 Sleep Mode Setup Poll)
if this event should generate any Data reports.
84-87
-- Unused --
Manual Position
88
-- Not implemented --
Speed Limit
89 (Above Speed Limits)
Data report are sent when speed event Is enabled and
GPS Blocked
90 (Below Speed Limits)
setup with command "set -sp x,y". See
91
Data report sent when GPS is blocked.
Table 4.1 Events generating Data Reports
The following example shows how to set up an event program. The event program
initiates a Data Report to LES 102, DNID 10289, when the status of the I/O-pins changes.
: ev -?
Usage: ev <option>
-o <LES>,<DNID>[,<mem>]
:
-c <entry>
:
-p <entry>,<powerctrl>,<sleepmode>,<io>,
<antennablockedtime>,<gpsblockedtime>,
<zoneevents>,<speedevents>
:
-e <entry>,<retxfail>,<store>,<normafterantblock>
[,<antblockedfn>]
:
-d
:
-fp <powerctrl>,<sleepmode>,<io>,
<antennablockedtime>,<gpsblockedtime>,
<zoneevents>,<speedevents>
:
-fe <retxfail>,<store>,<normafterantblock>,
<antblockedfn>
:
: ev -o 102,10289
Create event program

Delete event program
Enable or disable events
Program set-up
Display event status
Default enable or disable events
Default program set-up
: ev -d
Entry LES DNID Mem auth pwctrl sleep io retx store nantb antbt gpsbt zone speed
0
: 102 10289
3
0
0
0 0
0
0
0
0
0
0
0
Data Reporting
35
Event Reports

: ev -p 0,0,0,1,0,0,0,0
: ev -d
Entry LES DNID Mem auth pwctrl sleep io retx store nantb antbt gpsbt zone speed
0
: 102 10289
3
0
0
0 1
0
0
0
0
0
0
0
Figure 4.5: Activating Event Data Reporting
4.6 SLEEP MODE

The Transceiver can only be brought into sleep mode by means of the externally
accessible I/O pin, remote power switch, dedicated for this purpose. This pin can
always bring the Transceiver out of sleep mode. When switching the remote power
switch OFF the Transceiver goes to sleep and wakes up at specified intervals. When
switching the remote power switch ON then the Transceiver will power up and leave
sleep mode operation and stay awake until the remote power switch is switched OFF
again which will activate the sleep mode operation.
Sleep mode operation has the following features:
Wake up, send position reports and go to sleep again for a predefined duration.
The parameter T1 controls this mode. E.g. T1=4 means sleep 4 hours, wake up,
send a position report and go to sleep again for 4 hours.
Fix Time wake up. Wake up at a fixed time every day, send a position report and
stay awake for a 15 - 60 minutes. The parameters HH, MM and T2 control this mode.
E.g. HH=23, MM=0 and T2=30 mean wake up at 23:00 UTC and stay awake for 30
minutes. The purpose of the Fix Time wake up is to allow the Transceiver to receive
messages and polls during sleep mode operation; e.g. the Transceiver can receive
a poll that changes the sleep mode operation.
The following data reports with special MEM (Macro Encoded Message) codes are
defined for sleep mode operation, See Table 4.1 Events generating Data Reports:
Enter sleep mode report: Sent when entering sleep. A enter sleep mode report
contain the last known position when entering sleep mode. When the report has
been send the transceiver goes to sleep. If not able to sent the report the
transceiver will timeout after 13 minutes (software version 2.06) and go to sleep.
In sleep mode report: Sent when waking up just to send a report. An in sleep mode
report contains the current time/position. When the report has been sent the
transceiver goes to sleep. If the current position cannot be obtained the transceiver
will timeout after 5 minutes (software version 2.06) and try to send the last known
time/position instead. If not able to send the report the transceiver will timeout after
13 minutes (software version 2.06) and go to sleep.
Leave sleep mode report: Sent when leaving sleep mode. A leave sleep mode
report contains the current time/position. When the report has been sent the
transceiver has left sleep mode and stay on. If the current position cannot be
obtained the transceiver will timeout after 5 minutes (software version 2.06) and try
to send the last known time/position instead.
Fix Time begin report: Sent when waking up in fix time. A fix time report contains
the current time/position. When the report has been sent the transceiver stay on
until the fix time is gone then it goes to sleep. If the current position cannot be
obtained the transceiver will timeout after 5 minutes (software version 2.06) and try
to send the last known time/position instead. If not able to sent the report before the
fix time is gone the transceiver will go to sleep anyway.
The sleep command is described in paragraph 8.29 .
Data Reporting
36
Sleep Mode

4.7 ANTENNA BLOCKED AND GPS BLOCKED EVENTS

4.7.1 ANTENNA BLOCKED EVENTS
When Antenna Blocked Events are enabled, data reports will be sent whenever the
antenna has been blocked for more than a specified period. The minimum time that the
antenna must be blocked before the report is sent is configured by the user.
The antenna is considered blocked if the transceiver is unable to achieve
synchronization with the Inmarsat satellite signal for more than 80 frames (approx. 12
minutes). Note that, depending on the nature of the blockage, the GPS may still have fix
in this situation.
Antenna blocked reports are not sent until the antenna has been unblocked, but the
position in the report is the last known position before the blockage occurred.
The command for setting up Antenna Blocked Events (along with the other events) is EV
-p Program/Specify Event Program, which is described in section 8.11.7 .
4.7.2 ANTENNA BLOCKED FILTER FEATURE
[ver. 2.12]
The purpose of the feature is to reduce the number of data reports that come from
power and blocking events.
Note, that only event and interval programs based on the same DNID can be used to
operate with this feature.
Data Network IDentifier (dnid)
Eventprogram
Intervalprogram
DNID1
Eventprogram
DNID2
Intervalprogram
Figure 4.6: Rules for DNID in relation to filter feature.
These points summarizes the function:
Discards antenna block event reports if the corresponding interval program did
not lose any reports during blocking (referred to as filtered unblock events).
Discards power up/down event reports if the corresponding interval program

did not lose any reports during power off (referred to as filtered power events).
The basic purpose of this feature is to reduce traffic and avoid less important data
reports when interval reporting is enabled.
Note that this feature should not be used if it is important to detect all antenna block
reports and power event reports.
Consider a transceiver with an interval reporting set to one hour and a event program
which report power- and antenna blocked events.
Data Reporting
37
Antenna Blocked and GPS Blocked Events

Blocking:
A fishing vessel operating in severe weather at high northern latitudes might send
blocking data reports as often as every 15 minutes. A truck driving in urban high-rise
areas faces a similar situation because the view to the satellite can be obscured.
In this case the antenna blocked filtering can be used to suppress the antenna blocking
reports except when the interval program actually fails because of the blocking.
With filtered blocking feature disabled:
Antenna block report sent
Short blocking:
Frame interval
Prolonged blocking:
Blocked
Blocking started
Antenna block
report sent
Interval reports fail because of blocking
Frame interval Blocking started
Blocked
Note, the blockevent is sent after blocking ends even though reports are
lost or not.
Figure 4.7: Blocking reports with filtered blocking disabled.
With filtered blocking feature enabled:

Short blocking:
Antenna block report discarded
Retransmissions
Frame interval
Blocking Blocked
started
Short blocking:
Frame interval
Antenna block report discarded
Blocked
Blocking started
Antenna block report send
Prolonged blocking:
Interval reports fail because of blocking
Retransmissions
Retransmissions
fail
Frame interval
Data Reporting
Retransmissions
fail
Blocked
Blocking started
38

Figure 4.8: Antenna blocked reports with filtered blocking enabled.
The filtered blocking reports is enabled with the ev -e command (see section 8.11.3 ;
look for the <antblockedfn> command switch).
For this feature to operate correctly, it is required to set the interval report
retransmission attempt to at least 25. This requirement is crucial because the
transceiver does not enter blocking mode before the bulletin board error rate (BBER)
rises to 80 frames (each retransmission takes a couple of frames).
Use the command "diag prot retxrep <no. of retransmissions>" to set retransmissions only available as system administrator or above.
: diag prot retxrep 25
Reports are retransmitted 25 times
The recommended retransmissions in relation to the reporting interval is described in a

rule of thumb:
Report interval
4
Retransmissions =
If this requirement is not fulfilled, an undesired data report queue build-up will result in
disruption of the blocking filter function.
Power down/up:
In many types of installations it is not important to detect the loss of power. The filtered
power event feature suppresses power up/down reports if the interval program has not
lost any reports during the power off.
Filtered power events:

Short power off:
Frame interval
Power up/down reports send
Transceiver off
Prolonged power off:
Frame interval
Power up/down reports are discarded
Transceiver off
Figure 4.9: Power reports with filtered power enabled.
The filtered blocking reports is enabled with the ev -p command (see section 8.11.7 ;
look for the <powerctrl> command switch).
Data Reporting
39

4.7.3 GPS BLOCKED EVENTS

When GPS Blocked Events are enabled, data reports will be sent whenever the GPS has
been blocked (out of fix) for more than a specified period. The minimum time that the
GPS must be blocked before the report is sent is configured by the user.
Note that the Inmarsat signal does not necessarily have to be blocked because the GPS
signal is blocked, although this will often be the case.
The command for setting up GPS Blocked Events (along with the other events) is EV -p
Program/Specify Event Program, which is described in section 8.11.7 .
4.8 SPEED LIMIT EVENT

This feature enables the transceiver to send above/below speed-limit data-report.
No event sent
time for belowlimit was
to short
Speed
Send event for

Above speed-limit
Send event for
Belowe speed-limit
t
t
Limit
Figure 4.10: Speed Limits
The same event can never be sent twice. Ex. an above speed limit will always be
followed by a below speed limits and visa versa. The first event after power-on is
always the above speed-limit. As can be seen on the figure above an event/data-report
is only sent if the speed has been stable for a certain time. The data-report always
contains the position at the end of time 't'.
The speed limit event is configured as described in paragraph 8.28.28 SET -sp Speed
Limits
Enabling/disabling data reports for speed limit events is described in paragraph 8.11.7
EV -p Program/Specify Event Program.
For information on configuring one or more I/O-pin(s) to act on speed limit events, see
paragraph 8.17.3 IO -oOutput-pin setup.
4.9 MEM CODE TRANSLATION

When sending a Data Report initiated by an event, the report always contains a MEM
code identifying the event.
Data Reporting
40
Speed Limit Event

Thrane & Thrane has defined default values for these MEM codes, as described in
paragraph 4.5 Event Reports.
Any MEM-code can be changed by users, logged in as system administration level or
higher.
There is no restriction on what value that is assigned to a Macro Encoded Message but
please note that Inmarsat has predefined some MEM codes for Land Mobile Use in the
range 01H-3FH.
See also 8.9.11 DN -m Setup MEM codes to DNID-entry.
4.10 ATTACHING USER-STRING

The event Data Report always contains time and position and a MEM code indicating
the type of event. Besides the MEM code an user defined string can be attached to the
Data Report. These user-string are setup using the "DN -t
<DNIDentry>,<memcode>,<str>" command, See 8.9.16 DN -t Attach User-string.
It is possible to define up to 64 user strings containing a maximum of 32 characters
each.
See paragraph 8.9.6 DN -f Set Default DNID Format and 8.9.14 DN -p Program DNID for
programming default and specific DNID entry.
4.11 SURVEILLANCE ZONES

Surveillance zones are geographical areas that can be set up on the transceiver by the
system administrator. Some of the features of the transceiver can then be set to behave
differently depending on which zone it is in.
Interval programs can be set to report at special intervals when the transceiver is
inside specific zones. This may be used to increase the frequency of reports when
the transceiver is near important places, or to reduce the frequency when the
position of the transceiver is of less interest, e.g. a ship in port.
Event programs can be set up to send data reports whenever the transceiver enters
or leaves a zone.
The current zone status, i.e. the zone that the transceiver is currently inside, can be
read by external equipment through the terminal interface, thereby enabling this
equipment to take advantage of the advanced geographical positioning features.
In order to have the reporting interval change inside zones, this feature must be
enabled for the interval program (see 8.23.5 PG -e Extended program set-up) and an
interval must be set up for each of the zones (see the commands 8.38.9 ZONE -i Change
the reporting interval and 8.38.10 ZONE -ig Setup interval for zone in group.
In order to have event data reports sent when entering and leaving zones, an event
program must be set up for zone events (see 4.5 Event Reports).
The command 8.38.20 ZONE -s Get the current zone number can be used to get the
current zone status.
The transceiver automatically checks the current position against the active zones at
regular intervals. Zones are checked at a rate of one zone per 10 seconds.
Data Reporting
41
Attaching User-string

There are 8 types of zones with different shapes:

Zone type
Shape
Circle
Limits
Min radius 100 m
Max radius 6553500 m (6553.5 km)
Polygon with 3 positions
Max angle between sides = 180
Polyline with up to 40 positions
Min with 100 m

Max width 25500 m
Figure 4.11: Zone example
Examples of zones: Zone 1 is a valid type 3 zone. Zone 2 is invalid because of the angle
above 180.
If an invalid shape or invalid data is programmed the entire zone is ignored. When
zones overlap the zone with the highest priority (lowest number) will determine the
reporting interval. If there are many active zones, the transceiver takes a while to
search through all of them. One zone is searched every 10 seconds.
After the transceiver has entered or left a zone, and this has been detected, the next
zone check will not start until 2 minutes later. This delay prevents an excessive amount
of zone events that might otherwise occur if the transceiver is moving along or near a
zone border.
4.11.1 BASIC ZONES FEATURE
Zones may be set up in 2 different ways. The Basic feature is simpler and will suit a lot of
purposes, while the advanced feature provides more flexibility but is also more
complex to manage. It is possible to combine the basic and advanced features, but it is
advisable to stick to one method only to avoid confusion.
Data Reporting
42
Surveillance zones

In the basic feature, all zones are stored in a single file and all the existing zones are
always active at all times.
4.11.2 ADVANCED ZONES FEATURE
The advanced feature allows zones to be grouped in a number of separate files, Zone
Groups.
The zone groups can be activated separately. Only the active zone group will be
checked against the current position. If it is necessary to have more than one zone
group checked, a Zone Group List may be created. A zone group list does not contain
any zones itself, it just refers to existing zone groups. A zone group list may also refer
to a single zone within a zone group.
A number of zone group lists may be created. Because the lists only contain references,
it is possible for multiple lists to refer to the same group or the same zone.
A zone group list is

a list of zone
groups.
A zone group list
file contai ns no
zones, only
references to zone
groups.
A zone group is a collection of

zones. Each zone m ay be
either a polygon, a polyline,
or a circle.
All the zones in a zone group
is stored in one file on the
transceiver.
Zone 1 (polyline)
contains
Zone Group 1
contains
contains
Zone 2 (polyline)
Zone 3 (circle)
refers to
Zone Group 2
contains
contains
refers to
Zone 1 (polygon)
Zone 2 (polyline)
contains
Zone Group List 1
contains
refers to
Zone 3 (circle)
Zone 4 (polyline)
Zone Group 3
contains
refers to
contains
Zone Group List 2
refers to
Zone 1 (polyline)
Zone 2 (polyline)
Zone Group 4
contai ns
Zone 1 (polyline)
refers to
refers to
Zone Group List 3
refers to
Zone Group 5
contains
contai ns
contains
Any Zone Group List

m ay be selected as
the active one. Only
zones that are in the
active zone list will
cause events.
M ultipl e Zone
Group Li sts m ay
refer to the sam e
Zone Group
A list m ay al so
contain
references to
singl e zones
withi n groups.
Zone 1 (polyline)
Zone 2 (polyline)
Zone 3 (circle)
A Zone is part of one,

and onl y one Zone
Group.
The commands zo -ag and zo -al are used to active a zone group or a zone group list
(see 8.38.3 ZONE -ag Set active zone group and 8.38.4 ZONE -al Set active zone group
list).
The command zo -g is used to add a zone or zone group to a zone group list.
Data Reporting
43
Surveillance zones

CONFIGURING THE ADVANCED FEATURE

When it is desired to use the same zone configuration on many transceivers, this can be
done by setting up the zones on one transceiver and then copying the zone files to the
others.
The zone group files are named _ZONEnnn.DAT, where nnn is the number of the zone
group. Temporary files are sometimes created and they are named _ZONEnnn.tmp.
Zone group list files are named _ZLSTnnn.DAT, where nnn is the number of the zone
group list.
A quick way to delete zone groups and zone group lists is to delete the files. Sysadm
authority is required to access the files.
NOTE: Whenever files have been added, modified or deleted, the transcei ver should
be rebooted to update it with the changes.
THE DEFAULT ZONE GROUP
Default Zone Group is the zone group used by the basic features. It may be used like
other zone groups (it is identified by zone group number 0), but in order to avoid
confusion, it is recommended that the default zone group is not used when using the
advanced features.
The Default zone group file is named zonefile.dat and is has a corresponding temporary
file named zonef~_1.tmp.
ADVANTAGES OF THE ADVANCED FEATURE
There are several situations where it may be convenient (or even necessary) to use the
advanced zones feature.
Data Reporting
If a very long or complex zone is needed, this can be created by using several
zones grouped together in one zone group. For example, a polyline zone with more
than 40 points can be created using several polylines in one group.
If the zones needed are not always the same it may still be convenient to keep them
stored in the transceiver, but inactive.
44
Surveillance zones

EXAMPLE OF USE
The first table describes the configuration that needs to be done only once. This
configuration may be copied to other transceivers using normal file copying.
Description
Shell commands
A polyline following the road from So Paulo to
Create a new polyline zone:

zo -ng 1,1,8,40
Rio de Janeiro is created in Zone Group 1. The

polyline is split into polyline zones of max. 40
points each. For example, a route requiring 60
points would have to be split into one zone of 40
points and one with 20.
Enter positions 1-40 by repeating this for each

point:
zo -pg 1,1,<posno>,<position>
Create a new polyline zone for positions 41-60:
zo -ng 1,2,8,20
Enter positions 41-60 by repeating this for each
point:
zo -pg 1,2,<posno>,<position>
Set width of polyline to 300 meter:
zo -og 1,1,3
zo -og 1,2,3
A polyline zone following the road from So
See above
Paulo to Curitiba is created in Zone Group 2.

A polyline zone following the road from
See above
Curitiba to Porto Alegre is created in Zone

Group 3
A polygon zone around the area in Rio de
Janeiro (in which the truck is allowed to drive)
is added to Zone Group 1.
Sometimes the truck needs to go from Rio de

Janeiro to So Paolo and then to Curitiba.
Create a new polygon zone with 4 points:

zo -ng 1,3,3
zo -pg 1,2,1,<position1>
zo -g 1,1
zo -g 1,2
Therefore a Zone Group List referring to Zone

Group 1, and Zone Group 2 is created. The list
is called Zone Group List 1.
Sometimes the truck needs to go from Porto
Alegre to Curitiba and then to So Paolo.
zo -g 2,3
zo -g 2,2
Therefore a Zone Group List referring to Zone

Group 3, and Zone Group 2 is created. The list
is called Zone Group List 2.
Sometimes the truck needs to go all the cities in
Zone Group 1, 2, and 3. Therefore a Zone Group
List referring to Zone Group 1, Zone Group
zo -g 3,1
zo -g 3,2
zo -g 3,3
2,and Zone Group 3 is created. The list is called

Zone Group List 3.
Data Reporting
45
Surveillance zones

The second table describes the actions that will be taken during operation.
Description
Shell commands
Depending on where the truck is going, either one
Set zone list 1 active:

zo -al 1
of the Zone Groups and Zone Group Lists above

may be selected as the Active Zones. The inactive
zones are still stored in the transceiver, but they
don't cause events or interval changes.
To deactivate the zones, the default zone group
may be set to active. Note that if any zones exist in
the default zone group, those will then be active.
or set zone list 3 active:

zo -al 3
or set zone group 3 active:
zo -ag 3
Set the default zone group active (deactivate
others):
zo -ag 0
4.12 STORED POSITIONS

The transceiver can store the scheduled data reports when the transceiver is outside
Inmarsat-C coverage.
When the Inmarsat-C signal is blocked for approximately 12 minutes and the GPS
signal is still present the transceiver will begin store the scheduled data reports in nonvolatile memory.
When Inmarsat signal is restored and the transceiver has synchronized to a stable NCS
signal for approximately 3 minutes, the transceiver will begin transmitting the stored
data reports. The reports will be sent with a 25 frames interval. Scheduled report will
have a new MEM code specifying that it is a saved position and event reports will
remain unchanged.
The transceiver is capable of storing up to 250 reports independent of size and type.
When the storage area is full the transceiver will delete the oldest data-reports and
store the newest.
See section 8.11.3 to find out how to enable stored positions.
4.13 SINGLE PACKET POSITION REPORTS

If this entry is enabled the transceiver will only send 1 packet position reports i.e. no
speed, course or extended information is transmitted. Sending only one packet instead
to of two will reduce the number of position reports transmitted from the vessel/vehicle
by 50% and consequently reduce the cost of the position reporting in general.
Read more about the format of the position reports in Appendix A
enable single packet reporting in section 8.9.6 and 8.9.13 .
and see how to
4.14 NUMBER OF ACTIVE DNIDS IN TRANSCEIVER

Up to 64 DNIDs can be downloaded and stored in the transceiver as default. It is
possible to limit the number of DNIDs to a number between 0 and 64. However, it is not
recommended to change the default value, because it may reduce the functionality of
the system when used by an operator on a fishing vessel or truck.
This feature can be used to limit the access to local configured position reporting or as
an extra security against unauthorized tracking.
To find out how to change the number of active DNIDs see section 8.9.12
Data Reporting
46
Stored Positions

4.15 LONG TO SHORT REPORT INTERVAL CHANGE

This feature enables the transceiver to have two different position reporting intervals. A
long reporting interval for use when the vessel/vehicle has not moved more than the
configured number of meters (ex. 400 meter) since last report and a short interval at all
other times. The interval program uses the long interval when the user activates an
input pin programmed for long interval. The short interval is used automatically when
the vessel/vehicle has moved the programmed distance, or an input pin programmed
for short interval is activated.
The change in position is checked every 1 minutes.
Position
Interval changed
because vessel
has moved
400m from
harbor
Position of
harbor
time
Figure 4.12: Automatic change of reporting interval
The long interval and the long to short interval change distance are programmed using
the PG -l command (see 8.23.12 ). The short interval is the normal interval programmed
with the Pg -p command (see 8.23.14 ) or downloaded via poll. The long to short
interval change can be enabled/disabled for the individual programs using pg -e (see
8.23.5 ). The input pins are programmed with the IO -i command (see 8.17.2 ).
NOTE: The long to short interval change distance and the minimum distance between
position reports are the same.
4.16 DNID GROUPS

The purpose of this feature is to create a global or partly global DNID that can be
remotely configured and to which the transceiver can send data reports, regardless of
which ocean region the transceiver is logged in to.
Each DNID can be assigned to a group. Each group consists of up to 4 DNID, one in
each ocean region. When the configuration for one DNID is changed it affects all the
DNID's in the group. Similar, when one DNID is set-up for interval reporting or event
reporting, all the DNID's in the group will be in the reporting program.
Each group may be assigned a group id between 1 and 64. Group id 0 is reserved for
DNID's not in any group, and 65 to 255 are reserved for special applications.
The DNID's can only be assigned to a group with the terminal command 'dn -e' - see
section 8.9.5 . If a DNID is added to a group, and an interval- or event program already
is assigned to members of the group, this will be applied to the new DNID also. A DNID
Data Reporting
47
Long to short report interval change

entering a group always has its interval- and event programs removed. Only empty
ocean regions for a group can be assigned new DNIDs.
The DNID group members will inherit the attributes (general DNID properties as sub
address, provider name and authority level, memcodes, ect) of the DNID already in
group (if any).
To use the dn -e command, user authority level must be the same or higher as the DNID
authority level.
Deleting DNID can be done via. the terminal interface or via. poll - and has different
consequences according to the method. Using the terminal interface the DNID is
removed from group and does do appear in any programs afterwards. If the group is
not empty it remains populated with the remaining DNIDs. Deleting DNID via poll
using sub address 2 has the same effect. By using sub address 0 or 1 the group is
removed and all members deleted (a long with all associated programs).
Below are two examples of how the grouping works (summary of the rules explained
above):
Global (default) group:
Dnid 0
Ocean: AORE
Memcode setup: A
Authority:
A
Dnid setup:
A
Interval program
Event program
Dnid 4
Dnid 1
Ocean: POR
Memcode setup: B
Authority:
B
Dnid setup:
B
Ocean: AORW
Memcode setup: E
Authority:
E
Dnid setup:
E
Event
program
Interval
program
Dnid 3
Dnid 2
Ocean: IOR
Memcode setup: D
Authority:
D
Dnid setup:
D
Ocean: AORE
Memcode setup: C
Authority:
C
Dnid setup:
C
Figure 4.13: Precondition for group examples shown below.
Case 1:
y
Dnid 2 added to 34 (dn -e 2,34)
y
Create an event program based on group 34 member. (ev -o les/DNIDDNID 2)
y
Dnid 4 added to group 34 (dn -e 4,34)
Programs (i.e. event- and interval program) associated to DNID 2 are deleted before DNID enters group.
Creation of the event program includes all DNIDs in group (DNID 2 only).
Adding DNID 4 to group results initially in the deletion of the DNID 4 based programs. Afterwards DNID 4 gets
all properties from DNID 2 because it already belongs to the group.
Group 34 (result):
Event program for group 34
Dnid 4
Dnid 2
Ocean: AORW
Memcode setup: C
Authority:
C
Dnid setup:
C
Ocean: AORE
Memcode setup: C
Authority:
C
Dnid setup:
C
Figure 4.14: Case 1. Add DNIDs to group.
Data Reporting
48
DNID Groups

Case 2:
y
Add DNID 0 and DNID 1 to group 15 (dn -e 0,15 + dn -e 1,15).
y
Add DNID 2 and DNID 3 to group 10 (dn -e 2,10 + dn -e 3,10).
y
Create an interval program based on a group 15 member. (ev -o les/dnidDNID0/1)
y
Create an event program based on a group 10 member. (ev -o les/dnidDNID2/3)
y
Move DNID 2 from group 10 to group 15 (dn -e 2,15).
y
Move DNID 3 from group 10 to group 15 (dn -e 3,15).
Programs (i.e. event- and interval program) associated to DNID 0 and DNID 1 are deleted before DNID enters
group. All DNIDs entering thsi group will inherit the properties of DNID 0.Creation of the interval program
includes all DNIDs in group (DNID 0 and 1).
Likewise, programs (i.e. event- and interval program) associated to DNID 2 and DNID 3 are deleted before
DNID enters group. Creation of the event program includes all DNIDs in group (DNID 2 and 3).
Changing group for DNID 2 fails because the ocean regions is already occupied in group 15. Changing group
for DNID 3 succeeds because the ocean regions is not occupied in group 15.
Group 15 (result):
Interval program for group 15
Dnid 0
Dnid 1
Dnid 3
Ocean: AORE
Memcode setup: A
Authority:
A
Dnid setup:
A
Ocean: POR
Memcode setup: A
Authority:
A
Dnid setup:
A
Ocean: IOR
Memcode setup: A
Authority:
A
Dnid setup:
A
Group 10 (result):
Event program for group 10
Dnid 2
Ocean: AORE
Memcode setup: C
Authority:
C
Dnid setup:
C
Figure 4.15: Case 2. Add DNIDs to group (advanced).
Case 3:
Add DNID 0, DNID 1, DNID 3 and DNID 4 to group 40 (dn -e 0,40 + dn -e 1,40 + dn -e 3,40 + dn -e 4,40).
Delete DNID 0 via poll with sub address 2.
Delete DNID 1 via terminal interface.
Delete DNID 2 via poll with sub address 0.
Initially the group is created an populated.
The first delete DNID poll deletes and removes DNID 0 from group. Group remains with other members.
The second delete DNID poll deletes and removes DNID 1 from group. Group remains with other members.
The third delete DNID poll deletes the rest of group.
Group 40 (result):
Empty
Figure 4.16: Case 3. Delete DNIDs.
4.16.1 AUTO GROUPING

[ver. 2.15]
Data Reporting
49
DNID Groups

New DNIDs with the same DNID number and LES number in different ocean regions are
grouped together automatically when downloaded. Auto grouping can be
enabled/disabled using the command dn -f, see section 8.9.7 . DNIDs are only autogrouped if auto-grouping is enabled when both DNIDs are created. The group is
created when the second DNID is downloaded using the first available group number.
When a third or fourth DNID is downloaded it is added to the group.
4.17 MINIMUM DISTANCE BETWEEN POSITION REPORTS

This feature applies to programmed interval reporting only.
Minimum distance is a feature that makes sure the transceiver has moved a certain
minimum distance before sending the next position report.
After setting-up the program on a DNID, the first report is always sent. At the next
scheduled position report, if minimum distance is enabled, the transceiver will check
the current position and calculate the distance to the position it had when the previous
position report was sent. If this distance is below the minimum distance, the position
report will not be sent. This procedure is repeated at the times for the next scheduled
position reports.
This does not mean that the transceiver will send a data report when it has moved the
minimum distance. the position reports will be sent at scheduled times, but reports will
only be sent if the distance to the previous report is over the minimum distance.
The minimum distance value is also used to check if the transceiver is to go from
sending position reports with the long time interval to sending with the short interval.
Minimum distance is enabled/disabled with the pg -v command, and the minimum
distance value is set with the pg -l command. Setting the value to 0 will disable
minimum distance.
To use the pg -v and pg -l commands, user authority level must be the same or higher
as the DNID authority level.
4.18 DATA REPORTING PROTOCOL

Transceivers with software version 2.15 and newer contain two data reporting
protocols: Basic data reporting protocol and enhanced data reporting protocol. The
basic data reporting protocol is the origional data reporting protocol used before
software version 2.15. The enhanced data reporting protocol features provides full
acknowledgment of data report transmissions and an automatic retransmission scheme.
It is therefore strongly recommended to use the enhanced data reporting protocol. An
enhanced data report can contain 37 bytes data while a basic data report can contain 32
bytes.
By default the transceiver will use the enhanced data reporting protocol if the LES
support this protocol otherwise the transciver will use the basic data reporting protocol.
But it is possible to force the transciver to use basic reporting for a DNID, see 8.9.8 and
8.9.9 .
Data Reporting
50
Minimum Distance Between Position Reports

REMOTE CONFIGURATION AND POLLING

5.1 GENERAL INTRODUCTION
This section describes the polling features in the Transceiver.
Data reporting can be set up remotely via polls. This means that data reporting for a
fleet of Transceivers can be controlled remotely from a home base (e.g. using the T&T
Capsat Manager application). The remote control of the Transceiver is done via polling
commands. Some of the polling commands are defined by Inmarsat; other polling
commands are defined by T&T.
5.1.1 SENDING POLLS
Polls are sent via a LES. Contact a LES to get information about the interface for sending
Polls.
In the following sections poll files, poll addressing and polling commands are
described.
5.1.2 INITIAL DATA REPORTING AND POLLING PROCEDURES
Before the polling and data reporting facility can be used, contact a LES and obtain a
DNID. The service is ready for use when the LES informs that the DNID has been
entered in the LES database.
Then the DNID needs to be downloaded to the transceiver:
Login the transceiver to the proper ocean region by issuing the login command:
li <ncs_id>
The LES needs to be contacted in order to initiate a download DNID poll. Then wait for
the DNID to be downloaded from the LES via the NCS common channel (the one
specified above).
When the DNID has been downloaded the st -l INFO message will be received:
INFO 433: Poll Received
Added:
File POLLFILE.005 Size 26
131,2200,20,0; Load DNID; Datareport Response;
This means that the poll packet received by the link have added the DNID (LES ID 131,
DNID 2200, member number 20 and sub-address 0) to the transceiver DNID poll. The
poll contained 26 bytes of user data that was stored in the file POLLFILE.005. The
Transceiver will use the unique name POLLFILE.XXX to mark received polls. For a DNID
download the first part of the POLLFILE consists of a binary header containing the LES
ID, DNID, Member Number and Sub Address.
The transceiver will send an acknowledgment to the DNID if it is requested in the
download DNID poll (see paragraph 5.1.7 ). In software version 2.12 it was introduced
that the transceiver always response with a data report identifying the transceiver. This
makes it possible to identify DNID download into a wrong transceiver. The format of the
identification report is described in Table 5.11. Such a identification data report can
also be obtained using a sub-address 2 poll (see paragraph 5.6 ).
The DNID can now be used for data reporting and poll reception.
Remote Configuration and Polling
51
General Introduction

Use the dn -d command (please see section 8.30.4 on page 133) to obtain a list of the
DNIDs downloaded in the transceiver.
Data reports can only be sent on signaling channels having 'Closed User Group' access,
and if this is not the case for a particular LES (all channels will be searched by the
Transceiver), the error message 'No Closed User Group service available' will appear.
5.1.3 POLLFILE CONTENTS
The format of a pollfile is divided into a common header part and a specific userdata
defined part.
The header part has the following format:
Byte
Information
Remark
Header Length
Header size including this byte
LES ID
Compressed Inmarsat format: Two bits for

Ocean and 6 bits for ID, e.g. 5FH for LES ID
131
LSB of DNID
MSB of DNID
Member Number
Sub Address
Command
Command parameter from poll packet. This

includes the Acknowledgement bit (80h) if
this was included.
See section Polling Commands on page 53.
Sequence
A LES poll packet identifier. This value is
Number
returned in an acknowledgement.
Table 5.1 Pollfile Header
In Table 5.2 is given an example on a user data part for a DNID Download.
Byte
Information
Remark
Member Number
In binary
9-31
Provider name
In ASCII with Odd Parity. The name may be

shorter than 25 characters. If user data is
available, the name will be padded with
(space) characters.
32-307
User supplied data
Binary data
Table 5.2 DNID User Data
5.1.4 POLL ADDRESSING

The download DNID poll is addressed to a specific unit (individual address), but the
Inmarsat-C system also allows the LES to send out group polls or area polls (field P1 in
section 5.1.1 ).
Group polls uses the DNID (and LES ID) to address the units to be polled. All units
receiving the group poll will then have to store the information from this packet.
Area polls uses DNID, LES ID and a geographical area to designate which mobiles
should receive the poll. Area polls will therefore in principle address a smaller number
of units than a group poll.
52

Both area and group poll packets contain a Randomising Interval.

The randomising interval is used to prevent that all mobiles within the group/area try to
send their responses at the same time. The randomising interval is the number of
frames (8.64 second time units) that the Transceiver must wait in random before
sending a report.
The following example shows a group poll packet send from a terrestrial connection to
a Transceiver using the LES ID, DNID and sub-address.
The LES sends a Group Poll which
is received by member 12 and sent to
Subaddress 5
LES
Member Numbers
11
12
13
14
15
Group (DNID + LES ID)

Programming stored in the Transceiver
Subaddresses
5
Poll packet file
Figure 5.1: Group Poll Explanation
5.1.5 POLLING COMMANDS

The poll command contains a command field (field P6) that controls the actions of the
Transceiver.
The Transceiver supports the following commands:
Command
Command Name
Meaning
0AH (10)
Download DNID
Add the DNID to memory
0BH (11)
Delete DNID
Remove the DNID from memory
00H (0)
Request response
Used to convey a request to the User

Application (not the Transceiver)
04H (4)
PU Program
Store program information in the

Transceiver and mark this as the start
time. Contains a start frame number
and a frame interval.
05H (5)
PU Initiate
06H (6)
PU Stop
Initiate the stored program (especially

the device at <sub-address>.
Stop the stored program.
Table 5.3 Inmarsat Defined Polls
Command
Command Name
Meaning
6AH (106)
6CH (108)
Sleep mode
Remote
Setup Sleep mode.

Remotely configure transceiver. Used
configuration
to set-up surveillance zones.
Table 5.4 T&T Defined Polls to Sub-address 1
53

Command
Command name
Meaning
70H (112)
Set output
Set the output pins.
71H (113)
Read I/O
Read the I/O pins and return a datareport.
Table 5.5 T&T Defined Polls to Sub-address 3
5.1.6 RESPONSE
In a poll packet there may be a request for a data report response. This request is then
put into the INFO 433 status line. The response depends upon which sub-address is
being polled. If the sub-address is greater than 3 it is the responsibility of the DTE to
supply the appropriate response.
The three sub-addresses shown in the table below have a special meaning to the
Transceiver when they are polled with the response bit set.
Sub-address
Command
Function
Reserved for the DTE. No response facility is currently implemented in the
T&T DTEs (Message Handling software).
00H
The built-in GPS. Polling this sub-address with response request set to data
report using any DNID will result in a position report in the PU position
format.
00H
The Transceiver. Polling this sub-address with response request set to data
report using any DNID will result in a pre-defined data report that contains
the Transceivers general status information.
71H
I/O status. Polling this sub-address with response request set to data report
using any DNID will result in a data report containing the I/O status.
Table 5.6 Datareport sub-addresses.
5.1.7 ACKNOWLEDGEMENT
In a poll packet there may be a request for an acknowledgement. This is a special data
report that the transceiver formats and sends back to the LES without any user
intervention.
The acknowledgment datareport format can be found in Appendix I
5.1.8 RANDOMISING
In order to avoid collisions when a number of transceivers respond to a poll, the frame
number in which the response is sent is chosen randomly within a set interval. The
length of the interval is given in the poll packet. Only Group and Area Poll packets
contain a randomising interval. Responses to individual polls are sent immediately.
5.2 SLEEP MODE SETUP POLL

The command type is 6AH. The poll must be addressed to sub-address 1. The purpose
of this poll is to allow remote setting up of sleep mode.
54
Sleep Mode Setup Poll

T1 (8 bit)
HH (8 bit)
MM (8 bit)
T2 (8 bit)
Table 5.7 Sleep Mode Setup Poll
Where:
T1: 0 - 24,
Duration in hours the transceiver sleeps between wake ups. If T1=0, then there are no
periodic wake ups defined.
HH: 0 - 23
MM: 0 - 59
HH:MM specifies the time (UTC) for Fix Time wake up.
T2: 0 - 60
Duration in minutes of Fix Time wake up.
Setting T1=0 and T2=0 is equivalent to using the sl -c command.
Example of Sleep mode setup poll:
poll 1 i 12345 n 1 491234567 106 67 <P8> <P9> 1
0Ch (T1, Sleeps 12 hours between wake ups.)
0Fh (HH, Set to hour 15)
00h (MM, Set to minute 00)
30h (T2, Fix time wake up duration = 48 minutes)
The acknowledge report will be:

10000000
Command ( 8 bit)
Sequence Number (8 bit)
Spare (16 bit)
Result code
(16 bit)
Table 5.8 Sleep Mode Acknowledge Report
See also section 4.6 Sleep Mode.
5.3 REMOTE CONFIGURATION POLL

The command type for the remote configuration poll is 6CH.
A remote configuration poll is used to remotely configure the transceiver. It is executed
by sending an individual poll to sub address 1.
5.3.1 ZONE CONFIGURATION POLL
Using the zone configuration poll, it is possible to remotely configure surveillance
zones in the transceiver. Refer to 4.11 for more information on surveillance zones.
55
Remote configuration poll

Note: In order to be able to setup a zone using the zone poll, the DNID must have an
authority level of at least sysadm. This is set using the dn -p command. Refer to 8.9.13
for more information on this command.
The packet format of the zone configuration poll is described, and examples are shown,
in appendix C .
5.3.2 ZONE GROUP/GROUP LIST SELECTION POLL
[2.21] Using the Zone Group or Group list Selection Poll it is possible to remotely select
the active zone group or zone group list.
The packet format of the zone configuration poll is described in appendix C
5.4 I/O CONTROL POLL

The command type is 70H or 71H. The poll must be addressed to sub-address 3. The
purpose of this poll is to allow remote control of the output pin and to read the input
pins on the connector of the transceiver, See ref. [3] TT 98-116078, TT-3026L/M
Installation Manual.
The first pin (pin 1) is reserved for the land mobile alert button (option 112).
5.4.1 SET OUTPUT STATUS
Command type is 70H
Output status, LSB
Output status, MSB
Output status
Bit 0-1
pin 2 0 = low, 1 = high, 3 = unchanged
Bit 2-3
Bit 4-5
Bit 6-7
Bit 8-9
5.4.2 READ I/O STATUS

Command type is 113 (71H)
No data needed.
5.5 INMARSAT PU REPORTING

This section describes the Programmed Unreserved (PU) programming polls defined
by Inmarsat. The Transceiver can hold up to 64 independent PU programs.
The Inmarsat specified Position Data Report format can only operate in one Ocean
region at a time and there is no handshaking or protocol control.
If the Inmarsat Position Reporting is used then following has to be done:
Apply for a DNID number at the preferred LES.
56
I/O control poll

Make the LES download the DNID to the Transceivers (Remember to log the
Transceivers in to the correct Ocean Region).
Contact the LES and tell which destination the reports shuld be routed to (Fax,
Telex, PSTN Modem etc.).
Program the Transceiver locally or from remote connecting to the LES via PSTN,
PSDN, ISDN or Internet/mail.
5.5.1 PROGRAMMED UNRESERVED (PU)

The Transceiver supports the following three Inmarsat Poll commands:
Program Unreserved data reporting
Initiate Unreserved data-reporting
Stop Unreserved data-reporting
It can be specified that the Transceiver is to send data reports with regular intervals by
sending a program unreserved poll command (04H) to the Transceiver, where the
interval is defined in units of frames.
The program command (an individual or group poll) contains:
DNID
LES ID
Member number
Starting frame number
Reporting interval
If the DNID has already been programmed, it is re-programmed with the data
contained in the poll.
To initiate the program send the initiate unreserved poll (05H) to the desired sub
addresses. If position reports should be inserted in the start of the data report, send the
initiate unreserved poll to sub address 1. When the program is initiated the Transceiver
will start to send data to the specified DNID.
To stop reporting from a specific sub address, send a stop unreserved poll (06H) to that
sub address. If the poll is sent to sub address 0, the program will be removed from the
Transceiver.
5.5.2 GETTING DATA FROM SUB-ADDRESSES
Seen from the point of view of the Transceiver the data comes from an unknown device
(as the sub-address information is not part of the header information in the data report
packets). The Transceiver stores data from different sub-addresses using the same
DNID in the same buffer:
Group Buffer (Queue)
Data 1
Data 2
As the Transceiver knows when the PU transmission should occur, it will inform the DTE
5 frames before. Just before it sends the INFO 653 buffer request it will flush the buffer.
The DTE then has 8 seconds to transfer data from its devices to the Transceiver using
the da command. When this time has elapsed the Transceiver will send an INFO 663
57
Inmarsat PU Reporting

(Datareport buffer is now used). The PU protocol allows a maximum of 3 packets = 32

bytes.
5.6 CONFIGURATION INFORMATION

Poll to sub address 2 is used to retrieve configuration information from a transceiver in
the field.
Some of the most vital about the functionality of sub address 2 polling is the possibility
to read the Mobile Number by polling a DNID. This makes it possible to identify DNID
download into a wrong mobile.
5.6.1 POLL PACKET FORMAT
The packet is an individual poll directed to sub address 2. The text field of the poll
packet has a special format for the demand request data report response poll.
The format of the text field of the poll packet is shown here:
[Text field of poll]::= [Sequence No][Function]
Field
Size (bit)
Description
Sequence No
A sequence number that is used to
Function
A value deciding what information
match the response.

the MES should return. Refer to
Table 5.10
Table 5.9 Sub-address 2 poll text field

Function values
Description
Function 0 - Return Serial Number, Mobile Number,
Mobile Type and Version

Function 1 - Return DNID list
Function 4 - Reset transceiver (no response)
Table 5.10 Sub-address 2 poll function values

5.6.2 RESPONSE PACKET FORMAT
The format of the response depends on the information requested.
Function 0 response:
58
Configuration information

[Respons to function 0]::= [1011][Sequence No][TTRESMOBID]

[TTRESMOBID] ::= [serial_no][mobile_no][mobile_type] [version]
Field
Size (byte)
Description
Serial_no
Transceiver serial number
Mobile_no
Transceiver mobile number
Mobile_type
Land mobile / Maritime
Version
Version field
Table 5.11 Sub-address 2 function 0 response

Function 1 response:
[Respons to function 1]::= [1011][Seqno][TTRESPDLDNID]
[TTRESPDLDNID][TTRESPDLDNID][TTRESPDLDNID] [TTRESPDLDNID]
[TTRESPDLDNID]
[TTRESPDLDNID] ::= [status][DNID][les_id][member]
Field
Size (byte)
Status
Description
DNID status:
1 = active
0 = not activated
Dnid
DNID
les_id
LES Id
Member
Member number
Table 5.12 Sub-address 2 function 1 response
59
Configuration information

ALERT FUNCTIONS
The TT3026 transceiver supports a number of alert transmission schemes; the
availability of these functions depends on the configuration and the type of the mobile.
6.1 LAND MOBILE ALERT

Land mobile alerts may be issued be TT-3026 transceivers that are registered by
Inmarsat as Land Mobile. These alerts can only be handled by Land Earth Stations (LES)
where there is established a routing for the given transceiver.
The information sent in the event of an alert is similar to the GMDSS distress alert but
the transmission protocol is different giving the land mobile alert a lower priority and a
less extensive routing.
The TT-3026L has a variety of commands to support the Land Mobile alert function;
these include the following:
Enable or disable the function. See paragraph 8.28.17 SET -k Enable or

Disable Land Mobile Alerting.
Set up alert information. See paragraph 8.28.15 SET -g Set Up Alert

Generator.
Initiate alert. See paragraph 8.1.1 ALARM Land Mobile Alert.
In most installations the alert is initiated via an alarm button connected to a dedicated
I/O pin (see section 2.5 I/O Interface).
6.2 MARITIME DISTRESS ALERT

[2.15] Maritime Distress alerts may be issued by TT-3026C or TT-3026D transceivers.
These alerts are handled by Land Earth Stations (LES) wich forwards it to the nearest
MRCC. If the distress can not be delivered to the desired LES the transceiver will send
the distress to the NCS it is logged in to.
The TT-3026C/D has the following commands to support the Maritime Distress alert
function:
Set up alert information. See paragraph 8.28.15 SET -g Set Up Alert

Generator.
The TT-3026C/D tranceivers have no commands to send a distress alert. The alert is
initiated via an alarm button connected to dedicated I/O pin (see section 2.5 I/O
Interface).
6.3 COVERT/SECURITY ALERTS

The background for having covert/security alerts is found in two circulars issued by
IMO - MSC1072 and MSC1073 - that assumed that covert alerts from ships would be
handled by established maritime rescue co-ordinating centres (MRCCs). As a result
Inmarsat began specifying changes to Inmarsat C software and equipment that would
deliver the SSA alert automatically to the associated MRCC (or the national security
administration).
Alert functions
60
Land mobile alert

These changes were included in Inmarsat C Change Notice 137 (CN137).

Thrane & Thrane has released the TT-3000SSA (Ship Security Alert) system with a TT3026M/SSAS transceiver as the central unit.
The Thrane TT-3000SSA has been approved to meet the Inmarsat-C covert alert
(CN137) specification, which utilizes the distress alert protocol to provide priority and
pre-emption within the network. However it should be strongly noted that the InmarsatC network does not support this capability at this time and will not unless and until the
relevant regulatory authorities implement a procedure for routing alerts.
Inmarsat will issue a press statement if and when this capability becomes available but
no date for this can be given at this time (February, 2004).
Besides CN137, the TT-3000SSA also includes a Ship Security Message for flexible
routing (MRCC or Ship Owner). The Ship Security Message use the messaging
capability of Inmarsat-C to send a covert Message with routine priority to a competent
authority designated by the Administration (could be MRCC) or any other recipient
such as a ship owner.
See appendix F
SSA messages format for a specification of the message format used
for alert messages.
A TT-3026M/SSAS transceiver that is configured to be a part of a TT-3000SSA system has
a set of commands to configure the following:
Select whether covert/security alerting should be based on CN137 or SSA

message service (or both in combination). See paragraph 8.3.1 CFG -c .
Selection of up to three recipient addresses for SSA messages. See

paragraph 8.28.3 SET -am Set SSA message destinations. Each of these
message destinations has a set of extended properties which controls the
usage. See 8.28.4 SET -ame Set Extended SSA message destinations.
Selection of an additional text note to be attached to SSA messages. See

paragraphs 8.28.6 SET -ar Reset high priority message or egc light
indication and 8.28.8 SET -atf Set SSA message text from file.
Selection of preferred LES - this setting will apply to both CN137 and SSA
messaging. See paragraph 8.28.19 SET -m Set Up Alert.
Besides the TT-3026M/SSAS transceiver, the TT-3000SSA system consists of a set of

buttons that are connected to the I/O pins (see section 2.5 I/O Interface for more
information).
6.4 ALERT REPORTING

Each of the alert types described in the precious sections (Land Mobile and
Covert/Security) may be combined with Alert Reporting.
This reporting is an extension of the normal interval reporting that is described in
section 4.4 Interval Reports. The following points summarize how alert reporting works.
Alert functions
Alert reporting is created and configured just like an ordinary interval

reporting program; see section 4.4 Interval Reports for an overview.
Normally the program should be set up remotely as described in section
5.5 Inmarsat PU Reporting because this enables subsequent remote control
of the reporting in case an alert
61
Alert reporting

The content of an interval report is configurable as explained in section 4.2

Setting Up Data Networks. It is recommended to include the I/O
information in the data format as this provides information about the
current alerting status. See section 8.9.14 DN -p Program DNID for details
about configuration of the data format.
When an interval reporting program has been created it is made alert

controlled by using the pg -a command that enables or disables the
feature and also sets the interval to be used for alert reporting (see 8.23.1
PG -a Set alert activation).
An alert controlled interval program differs from a normal interval program

in the following ways:
When an alert is issued, the reporting is started (or reprogrammed if

already running) and the interval is set to the alert interval.
The MEM code of the data report is changed to indicate the alert
reporting mode. See section 4.4 Interval Reports for a table of MEM
codes being used.
The alert reporting bit in the I/O status byte is set. See appendix A.1
Packet Format for details.
The reporting mode can only be cancelled by re-programming or stopping

the interval program. This can be done via a PU poll as described in section
5.5.1 Programmed Unreserved (PU).
o
After cancellation of the alert reporting mode, the interval reporting

program behaviour is reset to normal and it will continue ordinary
reporting or stop depending on whether an init poll or a stop poll was
sent to the transceiver.
Note that releasing the alert buttons will not cancel alert reporting: An
interval program holds its own memory of the previous alert situation
and this will not be reset until the program is stopped or changed as
described above.
In dedicated alert installations that arent otherwise operated or used for other
purposes, the alert reporting can be configured with default values to make the
installation procedure easier. There are two sets of default settings that are relevant in
this situation:
1. Section 8.9.6 DN -f Set Default DNID Format describes how to set default
settings that apply to download of DNIDs. In particular it can be relevant
to set the <auint> selection to have a standard interval program created
at DNID download.
2. Furthermore, the commands described in sections 8.23.6 to 8.23.10 can
be used to specify the default behaviour for newly created programs.
By combining these two functions it is possible to set a predefined set of configuration
values so that a DNID download automatically creates an alert controlled interval
program as shown in this example:
: dn -f 3,1,0,1,0,0,0,0,0,1,0
: dn -f
Default Data Network format:
Alert functions
62
Alert reporting

Authority level
Time/pos type
Date format
I/O pin data
Add speed/course
Single packet report
Append userstring
Extra pos precision
Tachograph data
Autocreate intvpgr
Autocreate evpgr
: pg -fa 1,200
: 3
: Maritime
: 0
: Yes
: No
: No
: No
: No
: No
: 1
: 0
Connection no: Default, Alert controlled: 1, Alert interval: 200

:
The first command sets Autocreate interval program as a default property when
downloading DNIDs; the last command enables alert control for future created interval
programs.
After a DNID download, inspection shows that following program has been created:
: pg -d
Connection
0: remote
1: closed
2: closed
3: closed
: pg -a 0
Program
none
Ocean region
104,8048,10
Connection no: 0, Alert controlled: 1, Alert interval: 200

:
Note, that the program is not initiated (started); this will not happen until an alert is
issued or until the program is initiated remotely via a poll (see section 5.5 Inmarsat PU
Reporting).
Alert functions
63
Alert reporting

THE DATA-LOGGING FEATURE

[ver. 2.12]
Data can be logged in the transceiver over time. The stored data can be transferred to a
PC/laptop using the serial connection or send over the satellite, see section 7.3 . Not all
transceivers support the logging feature, see section 7.1 .
The log consists of a set of entries created over time. Every entry contains the same
data fields, which can be selected from
Table 7.1. Event number and Time of creation is always included as the two first fields
of an entry the other fields are optional. The size of an entry can be calculated by
adding the field size of the selected data fields. The format of the data fields is
described in more details in appendix D.2 .
Data fields
Precision
Limits
Field size
Description
Event number
256 types
1 byte
Cause of the entry creation.
Time of creation
1 second
Year 1970 to 2038
4 byte
The time where the log entry is created
1 second
18 hours
2 byte
(UTC time)
Time offset GPS
(time of event).
Time offset to the GPS data. GPS time
equal to Time of creation minus Time
offset GPS.
Position GPS
9 meters
6 byte
GPS position.
Speed GPS
1 km/h
254 km/h
1 byte
GPS speed in km/h.
Course GPS
2 degrees
0-360 degrees
1 byte
GPS course.
I/O status
1 byte
Status of the I/O-pins.
Distance
0.1 km
429,496,729.5 km
4 byte
The total traveled distance according
tachograph
to the tachograph interface (see

section 2.5.2 ).
Speed tachograph
1 km/h
255 km/h
1 byte
The speed according to the tachograph

interface (see section 2.5.2 ).
Extended position
2 meters
7 byte
GPS position. [2.19]
0,1 knots
6553,5 knots
2 byte
GPS speed in knots. [2.19]
GPS
Speed GPS in knots
Table 7.1 Possible data fields in a log entry

The transceiver has a logging storage of 512 kbyte flash memory. The logging storage
is divided into sectors of 64 kbyte. The sector containing the oldest data is erased when
the log is full and a new entry is to be created. This way the transceiver is able to
contain at least the newest 448 kbyte data.
Entries are created because of events or on an interval basic. Table 7.2 show the events
that can create entries.
The data-logging feature
64
Alert reporting

Event
Number
Description
Interval timeout
Entry created because of an interval timeout.
Tachograph started moving
13
An entry created because of a start event registered by the

tachograph interface. The tachograph interface is described in
section 2.5.2 .
Tachograph parked
14
An entry created because of a park event registered by the

tachograph interface. The entry contain data from the time were
the tachograph interface registered a stop. The tachograph
interface is described in section 2.5.2 .
Table 7.2 Possible events creating log entries.

Events that disable the interval timer and events that enable the timer can be specified.
For example the timer might be enabled while moving and disabled when parked if
used in connection with the tachograph function (see section 2.5.2 ). The timer creating
the interval entries is reset when booting and when a new entry is created.
7.1 DATA LOGGING IS NOT SUPPORTED BY ALL TRANSCEIVERS

Not all transceivers have the necessary flash memory to support the logging feature. To
find out whether the transceiver support the logging login as sysadm and use the
command log -d
Logging not supported:
: log -d
Logging is not supported
:
Logging supported:
: log -d
Log Status: Cleared

Field settings:
timeGPS PosGPS SpeGPS CouGPS I/O DistTG SpeTG
0
0
0
0
0
0
0
Event settings:
Timeout StartTG StopTG
0
0
0
Extended options:
StopWhenFull
0
:
7.2 SETTING UP THE LOG

The command Log is described in section 8.20 and is used to set up the data logging.
Sysadm authority is needed in order to use the command.
: log
Illegal argument (?).
-c (arg)
-i (arg)
-s (arg)
-d (arg)
-f (arg)
-p (arg)
-e (arg)
-x (arg)
:
Legal arguments are :

Clear data log
Enable data log
Disable data log
Display settings
Change field settings
Change event settings
Change extended options
Transfer log data using X-modem
65
Data logging is not supported by all transceivers

Use the command log -d to display the current log settings and status:
: log -d
Log Status: Cleared
Field settings:
0
0
0
0
0
0
0
Event settings:
0
0
0
Extended options:
StopWhenFull
0
:
In this case the log status is cleared (the log is not in use) setting can only be changed
when the log is cleared.
An example will be used to illustrate how to set up the log: The log entries are to
contain the following fields: Event number, time of creation, Time offset GPS, Position
GPS and Distance tachograph. Event number and time of creation is always included
the other fields are included using the Log -f command. Entries are to be created
when start and parked events are registered by the tachograph interface. When not
parked interval entries are to be created with a time interval of 90 seconds. Start events
start the interval timer park events stop the interval timer. This is set up using the Log p command:
: log -f
Usage: log -f <timeGPS>,<PosGPS>,<SpeGPS>,<CouGPS>,<I/O>,<DistTG>,<SpeTG>
: log -f 1,1,0,0,0,1,0
: log -p
Usage: log -p <timeout>,<startTG>,<stopTG>
: log -p 90,2,3
: log -d
Log Status: Cleared
Field settings:
1
1
0
0
0
1
0
Event settings:
90
2
3
Extended options:
StopWhenFull
0
:
The command Log -i enable the data log (the logging start):
: log -i
: log -d
Log Status: Enabled
Field settings:
1
1
0
0
0
1
0
Event settings:
66
Setting up the log


90
2
3
Extended options:
StopWhenFull
0
:
The command Log -s stop the logging without clearing the log:
: log -s
: log -d
Log Status: Disabled
Field settings:
1
1
0
0
0
1
0
Event settings:
90
2
3
Extended options:
StopWhenFull
0
:
To continue the logging use the command Log -i. To clear the log (delete all entries)
use the command Log -c.
7.3 RETRIEVING THE DATA

The data in the data log can be transferred out of the transceiver using a local or a
remote method. The format of the returned data is the same and is described in
appendix D .
Local transfer:
The command Log -x uses the X-modem protocol to transfer a specific part of the log
to the terminal. Example the following command makes the transceiver transfer a file
containing all log entries within the given time interval.
: log -x 2004-04-22,09:54,2004-05-04,09:57
Remote transfer:
A remote command message can be sent to the transceiver making the transceiver
send a data message containing a specific part of the log. . The remote command
message follows the TBus 2 format [7] a brief introduction can be found in appendix E
.
67
Retrieving the data

COMMAND REFERENCE
8.1 ALARM
8.1.1 ALARM ____________________________________________________ LAND MOBILE ALERT
Purpose: Issues a land mobile alert to a specified Land Earth Station.
Format:
Alarm
ALarm <land station>,<protocol>,<nature>
Prompts: Are you sure? Y/N

This command is used to send a Land Mobile alert to a Land Earth Station.
The parameters for the alert can be set with the set -m command or typed in at the
command line. The current status of the alert can be seen with the st -a command.
Please note that the use of Land Mobile Alerts requires a service agreement with the
particular Land Earth Station before the alerts can be processed. Before using the Land
Mobile Alert for the first time the LES operator should be contacted.
The Land Mobile Alert function is enabled using the set -k command.
The nature of the alert can be one of the following:
Identifier
Nature of Land Mobile Alert
Unspecified
Ambulance
Fire
Police
Hijack
Under attack/threat of attack
Dangerous cargo leak/spill
Accident
Vehicle breakdown
Severe weather
Table 8.1 Nature of Land Mobile Alert
The user must select a Land Earth Station for the alert to be sent to.
When a Land Mobile alert is issued the current operation is automatically cleared, and
the command queue is emptied. Transmission requests (have a lower priority than
other link commands) are not affected.
Example
If LES 131 should be used to send a Land Mobile Alert containing the information
Vehicle breakdown, type:
al 131,n,a<CR>
<CR><LF>
Are you sure Y/N > y<CR>
Command Reference
68
Alarm

Land mobile alerts may also be activated using a remote alarm button, which is an
optional accessory for the transceiver. Pressing this button corresponds to executing
the alarm command with no parameters.
8.2 CA
8.2.1 CA __________________________________________ CALIBRATE FREQUENCY CORRECTION
Purpose: Issues a calibration of the frequency correction.
Format:
CA <ocean_region>
ocean_region: W | E | P | I
In some rare circumstances, it might be necessary to issue a calibration command. If
the transceiver is unable to synchronize to the TDM channel because the transceiver
has been stored for 6 months or more, at extreme temperatures or other reasons. A
frequency calibration might solve the synchronizing problems.
When a calibration is issued the Transceiver searches for a NCS TDM starting with the
ocean region specified by the command argument. The calibration will not stop until a
NCS TDM has been found. A successful calibration could take several minutes (up to 45
minutes).
Note: When the Transceiver synchronized to a NCS TDM the frequency correction is
done automatically. Therefore, calibration of the frequency correction is not necessary
under normal circumstances.
8.3 CFG
8.3.1 CFG -C _____________________________________ CONFIGURE COVERT/SECURITY ALERT
Purpose: Configures the covert/security alert type. See paragraph 6.3 Covert/Security
alerts for more information.
Format:
CFG -c <alert type>
alert type: The alert type to be used.

0 = SSA messages
3 = SSA messages instant activation. [ver 2.15]
Please note that this command is only accessible for users with authority level sysadm.
See section 8.31 for more information about user level authority.
The cfg -c command is also used to enter SSA activation key for the TT-3026C model.
Command Reference
69
CA

8.4 CLEAR
8.4.1 CLEAR _____________________________________________ ABORT CURRENT OPERATION
Purpose: Forces the Transceiver to stop any protocol .
Format:
CLear <option>
This command terminates the current Transceiver link operation and deletes any
message file associated with it.
The command will result in a forced clear transmission to the LES in the following cases:
Transmission protocol
Aborting a pending call.
While waiting for an assignment from the LES.
During message packet transmission.
While waiting for a clear packet from the LES.
Receive protocol
After having sent assignment/announcement response.
While waiting for the message to arrive.
While waiting for the clear packet.
Link Test
The same cases as in the two message protocols.
After receiving the shore-to-ship call and it is being prepared for transmission.
During a pending ship-to-shore call.
While waiting for a distress test request.
Just before sending the distress test.
While waiting for the final Link Test clear packet.
The user will always be able to abort the current protocol when sending an alert, but
this will not result in a forced clear transmission from the Transceiver.
8.5 CONFIRM
8.5.1 CONFIRM _____________________________________________ CONFIRMATION REQUEST
Purpose: Requesting a delivery confirmation from a Land Earth Station.
Format:
COnfirm <message reference number> <LES_id>
The LES assigns a unique message reference number to each of the messages passing
through the system. The number can then be used by the Transceiver to request for the
status of that message.
Command Reference
70
Clear

The confirm command can be used to request for confirmation on a message that has
the status acknowledged in the transmit log. This status is given a message that has
been accepted by the Land Earth Station, but was not supposed to be confirmed.
With the st -t command the status of the message and the message reference number
can be seen, if the message has been acknowledged by the Land Earth Station.
The message reference number is also given in the INFO 81 message (see section 9.2 ).
When the confirmation (positive or negative) arrives from the LES via the NCS, the
transceiver will generate a a status report INFO, and the status in the transmit log will
be updated to deliver or failed.
Example
If transmit log contains a message with reference number 2345 sent to LES number 131,
and the message status is acknowledged, confirmation on that message can be
requested by typing:
co 2345 131
8.6 DATA
8.6.1 DATA ____________________________________________________ MANUAL DATA REPORT
Purpose: Sending a sequence of signalling channel bursts, transferring a small amount
of data to a Land Earth Station or append user data to an active interval
program (see cmd. pg)
Format:
Send data report immediately:

da [-o [-z <mem_attr>] [-l]] [-b <byte_cnt>]
<LES>,<DNID>,<mem>[<CR><data>]
Append user data to an active program:
da [-p] [-o] [-b <byte_cnt>] <LES>,<DNID>,<mem> [<data>]
-b
: Number of bytes in <data> field
-o
: Insert position in data rep.
-p
: Append data to buffer
-z
: Set macro and attribute field
-l
: Force category to land mobile
A data report command will at most send 32 bytes of user data.

If the -p option is used to store data in the data report buffer and if the operation is
successful, the following string will be displayed before the command line prompt:
<CR><LF><STX><count><ETX> bytes stored
where <count> is the number of bytes that is now stored in the buffer.
The first argument to the -z option will set the Macro Encoded Message (MEM) code.
The additional arguments will set the value of the 2-byte attribute field in the position
report. If the MEM code is in range 11-15 and 4 additional arguments (separated by
commas) is supplied then the 4 additional arguments are encoded as Time Of Position
in the 2-byte attribute field:
Command Reference
71
Data

Argument 2
month (1 bit)
0 is this month
1 is next month
Argument 3
day (5 bits)
Day of the month
Argument 4
hour (5 bits)
Hour of the day
Argument 5
minute (5 bits)
in units of 2 minutes
If the MEM code is 25 the additional arguments are emergency related parameters for
the attribute field:
Argument 2
TOP (3 bits)
Time Of Position
Argument 3
SP (2 bits)
Speed
Argument 4
DOT (3 bits)
Day Of Travel
Argument 5
Nature of
(See Note)
Emergency
Note: Consult the Inmarsat SDM, Volume 2, Part 2, Page AN2-27 for full description of
the decoding of the emergency fields.
Other MEM codes: The second argument will become the attribute.
Data reports can only be sent on signalling channels having 'Closed User Group'
access, and if this is not the case for a particular LES (all channels will be searched by
the Transceiver), the error message 'No Closed User Group service available' will
appear.
8.6.2 DATA -B ___________________________________________________________ BYTE COUNT
Purpose: Byte count
Format:
DA -b <number> <options> <LES>,<DNID>,<mem><CR><binary data>
number:
Value 0-32. Used if data is to be added to the report. The request is rejected
if the total number of bytes exceeds 32.
8.6.3 DATA -O _______________________ INSERT POSITION AT THE START OF THE DATA REPORT
Purpose: Insert the position at the start of the data report.
Format:
DA -o <options> <LES>,<DNID>,<mem>[<CR><binary data>]
If the -o option is specified alone a position data report will be sent to the specified
DNID. Additional data may be added after the position using the -b option. The position
format is as specified by Inmarsat for either Land Mobile or Maritime Transceivers.
8.6.4 DATA -P _______________________________ APPEND DATA TO THE DATA REPORT BUFFER
Purpose: Append data to the data report buffer.
Format:
DA -p <options> <LES>,<DNID>,<mem><CR><binary data>
The option only has effect with a DNID programmed for PU.
If the -p option is specified data will be appended to the data already in the data report
buffer. The data will be sent to the DNID when the next programmed report takes place.
Command Reference
72
Data

The data report buffer will be flushed before the Transceiver requests new data with
the INFO 653 message.
Data can only be added if the DNID parameters match those stored in the buffer. If the
data in the buffer was specified for another LES ID, DNID, Member number pair, the
buffer will be flushed before the new data is added.
If the -p option is not used data will be sent the default way: unreserved access as soon
as possible.
8.7 DELETE
8.7.1 DELETE __________________________________________________________ DELETE FILE(S)
Purpose: Deletes or removes a file from the file system.
Format:
DElete <filename>
RM <filename>
Filename: Maximally 12 characters

Remarks: The reserved files _EGCLOG, _RXLOG and _TXLOG cannot be deleted. The
wildcards "*" and "?" can be used to specify a group of files.
Command Reference
73
Delete

8.8 DIAG
8.8.1 DIAG _____________________________________________________________ DIAGNOSTICS
Purpose: Enable/disable diagnostics trace and displays diagnostics information.
Format:
DIAG DSP | DIAG TC | DIAG ACCESS
8.8.2 DIAG DSP INFO_____________________________ ENABLE OR DISABLE DSP DIAGNSOTICS

Purpose: Enable or disable DSP diagnsotics.
Format:
DIAG DSP INFO <ON>|<OFF>
8.8.3 DIAG DSP LD _____________________________________ 7REQUEST LOCK DETECT STATUS

Purpose: Request Lock detect status of 1 lo.
Format:
DIAG DSP LD
8.8.4 DIAG DSP ADC _______________________________________________ADC SAMPLE DATA

Purpose: Binary dump of data sampled during app. 100ms, while receiving the TDM
channel, transferred to DTE using the x-modem protocol.
Format:
DIAG DSP ADC
8.8.5 DIAG DSP RD ________________________________________________READ DSP MEMORY

Purpose: Read the DSP data or program memory.
Format:
DIAG DSP RD <src-addr> <cnt> <DM|PM> [-c]
src_adr:
Start address of memory to read from.
cnt:
Number of words to read.
DM:
Read datamemory.
PM:
Read program memory.
-c:
Continuos read of data. cnt must be less than 10.
8.8.6 DIAG TC _________________________________ ENABLE OR DISABLE
DIAGNOSTICS TRACE
Purpose: Enable or disable diagnostics trace from processes. Either the process name
or bit mask can be used. Bit masks can be combined by addition.
Process names and their bitmask
Name
Bitmask
Name
Bitmask
Name
Bitmask
Idle
00000001h
maintain
00000002h
powerctrl
00000004h
gps
00000008h
EgcHdl
00000010h
MsgHdl
00000020h
PollHdl
00000040h
DataRepHdl
00000080h
IOctrl
00000100h
Command Reference
74
DIAG

shell
00000200h
DspIn
00000400h
DspOut
00000800h
TPLayer
00001000h
RegMgr
00002000h
Dlink
00004000h
ChannelAccess
00008000h
PacketFilter
00010000h
SignalCtrl
00020000h
shellpost
00040000h
AlertHdl
00080000h
timer
00100000h
DataLogHdl
00200000h
PacketCmdHdl
00400000h
SLink
00800000h
SOutput
00000000h
main
40000000h
8.8.7 DIAG TC CLR_______________________________________ DISABLE
DIAGNOSTICS TRACE
Purpose: Disable diagnostics trace from one process.

Format:
DIAG TC CLR <name>
name:
Process name, as listed in 8.8.6
8.8.8 DIAG TC CLRALL___________________________________ DISABLE
DIAGNOSTICS TRACE
Purpose: Disable diagnostics trace from all processes.

Format:
DIAG TC CLRALL
8.8.9 DIAG TC SET ________________________________________ ENABLE
DIAGNOSTICS TRACE
Purpose: Enable diagnostics trace from one process.

Format:
DIAG TC SET <name>
name:
Process name, as listed in 8.8.6
8.8.10 DIAG TC SETMASK __________________________________ ENABLE
DIAGNOSTICS TRACE
Purpose: Enable diagnostics trace from one or more processes.

Format:
DIAG TC SETMASK <mask>
mask:
Process bit mask or combination, as listed in 8.8.6
8.8.11 DIAG TC TEST _____________________________________________ TEST TRACE LOGGING

Purpose: Testing Trace, Event and Error logging.
Format:
DIAG TC TEST
8.8.12 DIAG TC LIST ________________________________________LIST PROCESSES WITH TRACE

Purpose: Displays processes with trace enabled.
Format:
DIAG TC LIST
8.8.13 DIAG ACCESS ________________________________________ ACCESS LAYER DIAGNOSTICS

Purpose: Displays diagnostics information from the access layer processes.
Format:
DIAG ACCESS
8.8.14 DIAG ACCESS -C ________________________________________________CHANNEL STATUS
Command Reference
75
DIAG

Purpose: Displays channel status.

Format:
DIAG ACCESS -c
8.8.15 DIAG ACCESS -I_______________________________________________________ LIST INFO

Purpose: Displays access layer local variables values.
Format:
DIAG ACCESS -i <a|p|s>
a:
Display ChannelAccess variables.
p:
Display PacketFilter variables.
s:
Display SignalCtrl variables.
8.8.16 DIAG ACCESS -P ______________________________________________SHOW PACKET LOG

Purpose: Displays the log of the packets received with or without errors.
Format:
DIAG ACCESS -p
8.8.17 DIAG ACCESS -T __________________________________SHOW THE LAST FRAME RECEIVED

Purpose: Displays the last frame received in hexadecimal.
Format:
DIAG ACCESS -t
8.9 DN
8.9.1 DN _______________________________________________________ DATA NETWORK SETUP
Purpose: Configure the DNIDs.
Format:
dn -a
[ver 2.15]
dn -c <entry>[ - <entry>]
dn -d [<entry>]
dn -e <entry>,<groupid>
dn -f <auth>,<cat>,<date>,<iopin>,<speed>,<1pack>,<ustr>,<prec>,<tacho>,
<auint>,<auevt>
dn -fa [<dautgrp>]
[ver 2.15]
dn -fg [<obdr>]
[ver 2.15]
dn -g <entry>,[<obdr>]
[ver 2.15]
dn -l [<memindex>,<memcode>]
[ver 1.04]
dn -m <entry>[,<memindex>,<memcode>]
[ver 1.04]
Command Reference
76
DN

dn -o <LES>,<DNID>,<mem>,<sub>,<predef>,<provider>
[ver 2.14]
dn -p <entry>,<auth>,<cat>,<date>,<iopin>,<speed>,<1pack>,<ustr>,<prec>,
<tacho>
dn -s <entry>,<'D'|'E'>
dn -t <entry>,[<tmemcode>,<string>]
[ver 1.04]
dn -n <number of active DNIDs (0..64)>
[ver 1.04]
DNIDs are used for receiving poll and sending data reports. Up to 64 DNIDs can be
stored. The DN command manages the DNIDs and configures the format of the data
reports. See also section 4 Data Reporting and appendix A
8.9.2 DN -A ____________________________________________________ DNID AUTO-GROUPING
Purpose: Display auto-grouping settings for DNIDs. [ver 2.15]
Format:
DN a
Two DNIDs with the same DNID number and LES number in different oceans can be
auto-grouped. This command can be used to display whether auto-grouping is
enabled/disabled for the DNIDs in the transceiver. The section about the default autogrouping command 8.9.7 (dn -fa) describes the use of auto-grouping.
Example: Auto-grouping enabled for entry 0 and disabled for entry 1 and 2:
: dn -a
Entry dautgrp
0
:
0
1
:
1
2
:
1
:
8.9.3 DN -C ____________________________________________________________ CLEAR DNIDS

Purpose: Clear DNID.
Format:
DN -c <entry>[-<entry2>]
Clears all DNID entries between entry and entry2.

8.9.4 DN -D ___________________________________________________________ DISPLAY DNIDS
Purpose: Display DNIDs
Format:
DN -d
DN -d <entry>
Displays the list of DNIDs and associated format specification.
Command Reference
77
DN

8.9.5 DN -E ____________________________________________________________ DNID GROUPS

Purpose: Display and change DNID groups
Format:
DN -e
Displays the list of DNIDs in each group .

DN -e <entry>[,<group no>]
entry:
DNID entry no.
group no: DNID group number [0-64]. Default value is 0.

Assigns the DNID at entry to the DNID group with number group no. Group no 0 means
not in a group.
Example
DN -e 2, 4 Assigns the DNID at entry 2 to group 4.
DN -e 2 Moves the DNID at entry 2 out of its group.
8.9.6 DN -F _______________________________________________ SET DEFAULT DNID FORMAT
Purpose: Sets the default format specification for DNIDs. New DNIDs adapt this default
format when downloaded.
Format:
DN -f <auth>,<cat>,<date>,<iopin>,<speed>,
<1pack>,<ustr>,<prec>,<tacho>,<auint>,<auevt>
auth:
Authority level: 0-2, 0:normal user, 1:super user, 2: sysadm.
cat:
Format of data reports using this DNID.

0 = land mobile position report
1 = Maritime position report
2 = T&T data report format. Appendix A.2
date:
Add additional time and date information to data reports using this DNID.
0 =no time and date information included.
1 = time and date information, type 1, included.
iopin:
Include I/O-pin status in all data reports using this DNID.

0 = no I/O-pin status included.
1 = I/O-pin status included.
speed:
Add additional speed and course information to data reports using this DNID
0 = no speed and course info included.
1 = speed and course info included.
1pack:
Force transceiver to send only single packet reports. To enable this feature
make sure that no options that use the second packet are enabled. See
section 4.13 for more information about single packet reports [ver 1.04]
0 = one packet disabled.
1 = one packet enabled.
Command Reference
78
DN

ustr:
User defined string up to 32 characters in length. [ver 1.04]

0 = Attaching user string disabled.
1 = Attaching user string enabled.
prec:
Extra position precision. [ver 2.06]

0 = no extra precision included.
1 = extra precision included: 0,005 fraction of a minute.
2 = extra precision included: 0,001 fraction of a minute. [ver 2.19]
tacho:
Add tachograph data to data reports [ver 2.12]

0 = no tachograph data is included.
1 = tachograph data is included.
auint:
Automatic create interval programs for downloaded DNIDs. [ver 2.12]

0 = no intervalprogram is created automatically.
1 = intervalprogram is created automatically for new DNID.
2 = intervalprogram is created if 25th character in providername is A.
3 = intervalprogram is created as option 1, but is not auto started. [ver 2.22]
auevt:
Automatic create interval programs for downloaded DNIDs. [ver 2.12]

0 = no eventprogram is created automatically.
1 = eventprogram is created automatically for new DNID
2 = eventprogram is created if 25th character in providername is A..
8.9.7 DN -FA _________________________________________________ DEFAULT AUTO-GRUOPING

Purpose: Set whether DNIDs are auto-grouped on creation. [ver 2.15]
Format:
DN -fa [<dautgrp>]
dautgrp: Enable/disable auto-grouping.

0 = Enable auto-grouping.
1 = Disable auto-grouping.
Two DNIDs with the same DNID number and LES number in different oceans can be
auto-grouped. This command is used to set whether auto-grouping is enabled/disabled
for the DNIDs when they are created (downloaded or predefined, see the section about
the create DNID command 8.9.13 ). DNIDs are only auto-grouped if auto-grouping is
enabled when both DNIDs are created. The group is created when the second DNID is
created using the smallest available group number. When a third or fourth DNID is
created it is added to the group.
Example:
: dn -fa 0
: dn -fa
Auto group disabled : 0
: dn -o 4,8048,3,1,1,T&T
: dn -a
Entry dautgrp
0
:
0
: dn -fa 1
: dn -fa
: dn -o 104,8048,3,1,1,T&T
: dn -a
Entry
Command Reference
dautgrp
79
DN

0
:
1
:
: dn -e
0
1
Group AOR-W
AOR-E
POR
IOR
POR
IOR
: dn -fa 0
: dn -fa
: dn -o 204,8048,3,1,1,T&T
: dn -a
Entry dautgrp
0
:
0
1
:
1
2
:
0
: dn -e
Group AOR-W
AOR-E
1: 004,08048,003
: dn -o 304,8048,20,1,1,T&T
204,08048,003
: dn -e
Group AOR-W
1:
AOR-E
004,08048,003
POR
IOR
204,08048,003
304,08048,020
Description of examble step by step:

1. Auto grouping enabled
2. DNID 8048 LES 4 created.
3. Auto grouping disabled
4. DNID 8048 LES 104 created. No grouping (Auto grouping is disabled).
5. Auto grouping enabled
6. DNID 8048 LES 204 created. DNID 8048 LES 4 and 204 is auto grouped (DNID
8048 LES 104 is not grouped auto grouping was disabled when the DNID was
created).
7.
DNID 8048 LES 304 created. DNID 8048 LES 304 added to the group with the
same DNID on LES 4 and 204.
8.9.8 DN -FG ___________________________________________ DEFAULT REPORTING PROTOCOL

Purpose: Set the default data reporting protocol, see 4.18 . [ver 2.15]
Format:
DN -fg [<obdr >]
obdr:
Data reporting protocol

0 = Enhanced data reporting protocol, if protocol supported by LES else the
basic report protocol will be used.
1 = Force basic data reporting protocol.
2 = Force message data reporting. Data reports are sent as messages.
Message data reports contain 4 extra bytes of data, see A.3 Message data
report format. [ver 2.21]
Command Reference
80
DN

It is recommended to use the enhanced data reporting protocol.

Example:
: dn -fg
Reporting Protocol: 0
: dn -fg 1
: dn -fg
:
8.9.9 DN -G ____________________________________________________ REPORTING PROTOCOL

Purpose: Set the reporting protocol for a DNID, see 4.18 . [ver 2.15]
Format:
DN -g <entry>,[<obdr>]
obdr:
Data reporting protocol

0 = Enhanced data reporting protocol, if protocol supported by LES else the
basic report protocol will be used.
1 = Force basic data reporting protocol.
2 = Force message data reporting. Data reports are sent as messages.
Message data reports contain 4 extra bytes of data, see A.3 Message data
report format. [ver 2.21]
It is recommended to use the enhanced data reporting protocol.

Example:
: dn -g 0
: dn -g 0,0
: dn -g 0
:
8.9.10 DN -L _____________________________________________ SET USER DEFAULT MEM CODES

Purpose: Handles the user default MEM codes.
Format: DN -l
DN -l <index>,<mcode>
DN -l ttdefault
DN -l delete
List default MEM-codes with <mem-id>.

Change a single default MEM-code.
Load T&T defaults.
Deletes all user defaults MEM-codes.
<index> : Reference number to MEM codes listed in the list command

See DN -l
ttdefault:
Load Thrane & Thrane default MEM-codes.
delete:
Command to delete all user default codes.
<mcode> [0 .. 127 ] , See 4.4.2

The following examples, first loads user-default with T&T default, second change the
MEM code for "Fix Time Begin" to 83 and at last lists all user default MEM codes.
Command Reference
81
DN

Example:
: dn -l ttdefault<CR><LF>
<CR><LF>
: dn -l 11,83<CR><LF>
<CR><LF>
: dn -l<CR><LF>
<CR><LF>
User default MEM-codes:<CR><LF>
Index Name
0
Time of Position
1
Power Up
2
Power Down
3
Antenna Blocked
4
Stored Position
5
Io Report
6
Enter Zone
7
Leave Zone
8
Enter Sleepmode
9
In Sleepmode
10
Leave Sleepmode
11
Fix Time Begin
12
Enter Reduced
13
In Reduced
14
Leave Reduced
15
Manual Position
16
Above Speed Limit
17
Below Speed Limit
18
GPS Blocked
:
Mem-code<CR><LF>
11<CR><LF>
64<CR><LF>
66<CR><LF>
69<CR><LF>
70<CR><LF>
71<CR><LF>
72<CR><LF>
73<CR><LF>
80<CR><LF>
81<CR><LF>
82<CR><LF>
83<CR><LF>
85<CR><LF>
86<CR><LF>
87<CR><LF>
88<CR><LF>
89<CR><LF>
90<CR><LF>
91<CR><LF>
8.9.11 DN -M ________________________________________ SETUP MEM CODES TO DNID-ENTRY

Purpose: Assign MEM- codes to an existing DNID entry.
Format:
DN -m <entry>
List MEM-codes for <entry>.
DN -m <entry>,default
Load all user defaults.
DN -m <entry>,ttdefault
Load all T&T defaults.
DN -m <entry>,<index>
Load a single user default MEM-code.
DN -m <entry>,<index>,< mcode>
Change a single MEM-code.
mcode:
[0 .. 127 ], See 4.4.2
entry:
Reference number to DNID-entries listed with DN -d.
default:
Load user default MEM-codes. See section 8.9.10 for more in information.
ttdefault: Load Thrane & Thrane default MEM-codes.

index:
Example:
Command Reference
Reference number to MEM-codes seen in the liste-command

See DN -l and DN -m <entry>.
: dn -m 0,ttdefault<CR><LF>
<CR><LF>
: dn -m 0<CR><LF>
<CR><LF>
User defined MEM-codes for DNID-entry <0>:<CR><LF>
<CR><LF>
Index Name
Mem-code<CR><LF>
0
Time of Position
11<CR><LF>
1
Power Up
64<CR><LF>
2
Power Down
66<CR><LF>
3
Antenna Blocked
69<CR><LF>
4
Stored Position
70<CR><LF>
5
Io Report
71<CR><LF>
6
Enter Zone
72<CR><LF>
82
DN

7
Leave Zone
73<CR><LF>
8
Enter Sleepmode
80<CR><LF>
9
In Sleepmode
81<CR><LF>
10
Leave Sleepmode
82<CR><LF>
11
Fix Time Begin
83<CR><LF>
12
Enter Reduced
85<CR><LF>
13
In Reduced
86<CR><LF>
14
Leave Reduced
87<CR><LF>
15
Manual Position
88<CR><LF>
16
Above Speed Limit
89<CR><LF>
17
Below Speed Limit
90<CR><LF>
18
GPS Blocked
91<CR><LF>
: <CR><LF>
<CR><LF>
: dn -m 0,0,40<CR><LF>
<CR><LF>
: dn -m 0,1,41<CR><LF>
<CR><LF>
: dn -m 0,18,58<CR><LF>
<CR><LF>
: dn -m 0<CR><LF>
<CR><LF>
User defined MEM-codes for DNID-entry <0>:<CR><LF>
<CR><LF>
Index Name
Mem-code<CR><LF>
0
Time of Position
40<CR><LF>
1
Power Up
41<CR><LF>
2
Power Down
66<CR><LF>
3
Antenna Blocked
69<CR><LF>
4
Stored Position
70<CR><LF>
5
Io Report
71<CR><LF>
6
Enter Zone
72<CR><LF>
7
Leave Zone
73<CR><LF>
8
Enter Sleepmode
80<CR><LF>
9
In Sleepmode
81<CR><LF>
10
Leave Sleepmode
82<CR><LF>
11
Fix Time Begin
83<CR><LF>
12
Enter Reduced
85<CR><LF>
13
In Reduced
86<CR><LF>
14
Leave Reduced
87<CR><LF>
15
Manual Position
88<CR><LF>
16
Above Speed Limit
89<CR><LF>
17
Below Speed Limit
90<CR><LF>
18
GPS Blocked
58<CR><LF>
:
8.9.12 DN -N ________________________________________ CHANGE NUMBER OF ACTIVE DNIDS

Purpose: To change the number of active DNIDs. Requires a minimum of system
administrator userlevel.
Format:
DN -n <number>
number:
New number of active DNIDs [0-64].
8.9.13 DN -O ____________________________________________________________ CREATE DNID

Purpose: Create a pre-defined DNID entry. [2.14]
Format:
DN -o <LES>,<DNID>,<mem>,<sub>,<predef>,<provider>
LES:
LES id
DNID:
DNID number
Mem:
DNID member number
Sub:
DNID sub address
Predef:
Sets the DNID to be predefined. Only the value 1 is accepted
Command Reference
83
DN

Provider: A string of up to 25 characters in which the provider name can be entered

The stored DNID can be displayed using the command 8.9.4 DN -d Display DNIDs
8.9.14 DN -P __________________________________________________________ PROGRAM DNID
Purpose: Program a specific DNID entry.
Format:
DN -p
<entry>,<auth>,<cat>,<date>,<iopin>,<speed>,<1pack>,<ustr>,<prec>,<t
acho>
auth:
Authority level: 0-2, 0: normal user, 1: super user, 2: sysadm.
cat:
Format of data reports using this DNID.

0 = land mobile position report
1 = Maritime position report
2 = T&T data report format. Appendix A.2
iopin:
Include I/O-pin status in all data reports using this DNID. Note that the
content of the I/O-pin status depends on the transceiver type. See appendix
A.1 and A.2 for details.
0 = no I/O-pin status included.
1 = I/O-pin status included.
speed:
Add additional speed and course information to data reports using this DNID
0 = no speed and course info included.
1 = speed and course info included.
date:
Add additional time and date information to data reports using this DNID.
0 =no time and date information included.
1pack:
Force transceiver to send only single packet reports. To enable this feature
make sure that no options that use the second packet are enabled. See
section 4.13 for more information about single packet reports. [ver 1.04]
0 = one packet disabled.
1 = one packet enabled.
ustr:
Attach user defined string up to 32 characters in length. [ver 1.04]

0 = Attaching user string disabled.
1 = Attaching user string enabled.
prec:
Extra position precision. [ver 2.06]

0 = no extra precision included.
1 = extra precision included: 0.005 fraction of a minute.
2 = extra precision included: 0.001 fraction of a minute. [ver 2.19]
tacho:
Add tachograph data to data reports [ver 2.12]

0 = no tachograph data is included.
1 = tachograph data is included.
Command Reference
84
DN

8.9.15 DN -S _____________________________________________________ CHANGE DNID STATUS

Purpose: To enable or disable the DNID.
Format:
DN -s <entry>,<D | E | d | e | 0 | 1>
entry:
DNID entry.
To enable the DNID enter e, E or 1.

To disable the DNID enter d, D or 0.
8.9.16 DN -T ______________________________________________________ ATTACH USER-STRING
Purpose: To attach user-defined strings to a position report. Remember to enable this
feature with the command, described in paragraph 8.9.14 DN -p Program
DNID.
Format:
DN -t ?
List usage.
DN -t <entry>
List string(s) for <entry>
DN -t <entry>,<tmemcode>
List string for <entry>,<tmcode>
DN -t <entry>,DELETE
Delete all strings for <entry>
DN -t DELETEALL
Delete strings for all <entry>
DN -t <entry>,<tmemcode>,0
Delete string.
DN -t <entry>,<tmemcode>,[]<string>[]
Add/Change string.
entry:
Reference number to DNID-entries listed with DN -d.
tmemcode:Thrane & Thrane default MEM code in decimal values. [0127].

string:
User defined string up to 32 characters in length. Always used braces when

string contains spaces. Ex. "String With Spaces"
DELETEALL: Delete strings for all <entry>

DELETE: Delete all strings for a single <entry>
If for some reasons, no user-string is defined for a certain <entry> and <tmemcode>
pair, only the subaddress (43H) and length zero is added to the datareport. ( ..,43,00,..)
Example:
: dn -t 0,83,FixedTimeBegin<CR><LF>
<CR><LF>
: dn -t 0<CR><LF>
<CR><LF>
Entry MemCode UserString<CR><LF>
00
83
[FixedTimeBegin]<CR><LF>
1 of 64 entries found<CR><LF>
: dn -t 0,81,"In Sleep Mode"<CR><LF>
: dn -t 0<CR><LF>
<CR><LF>
00
83
00
81
[In Sleep Mode]<CR><LF>
: dn -t 0,71,"Intruder Alarm"<CR><LF>
<CR><LF>
: dn -t 0<CR><LF>
<CR><LF>
00
83
00
81
[In Sleep Mode]<CR><LF>
00
71
[Intruder Alarm]<CR><LF>
Command Reference
85
DN

:
8.9.17 DN -TB ______________________________________________ ATTACH BINARY USER-STRING

Purpose: To attach binary user-defined strings to a position report. [ver 2.19]
Format:
DN -tb ?
List usage.
DN -tb <entry>
DN -tb <entry>
DN -tb <entry>,<tmemcode>
List string for <entry>,<tmcode>
DN -tb <entry>,DELETE
Delete all strings for <entry>
DN -tb DELETEALL
Delete strings for all <entry>
DN -tb <entry>,<tmemcode>,0
Delete string.
DN -tb <entry>,<tmemcode>,<size><CR><string>
Add/Change string.
The only difference compared with DN -t is how a user string is Added or changed.
Example:
: dn -tb 0,72,20<CR><LF>
<00><01><02><03><04><05><06><07><08><09><0a><0b><0c><0d><0e><0f><10><11><12><13>
: dn -tb 0,73,20
<ff><fe><fd><fc><fb><fa><f9><f8><f7><f6><f5><f4><f3><f2><f1><f0><ef><ee><ed><ec>
: dn -t<CR><LF>
<CR><LF>
00
72
Binary[00 01 02 03 04 05 06 07 08 09 0a 0b 0c 0d 0e 0f 10 11 12 13
<CR><LF>
00
73
Binary[ff fe fd fc fb fa f9 f8 f7 f6 f5 f4 f3 f2 f1 f0 ef ee ed ec
<CR><LF>
: dn -tb<CR><LF>
<CR><LF>
00
72
Binary[00 01 02 03 04 05 06 07 08 09 0a 0b 0c 0d 0e 0f 10 11 12 13
<CR><LF>
00
73
Binary[ff fe fd fc fb fa f9 f8 f7 f6 f5 f4 f3 f2 f1 f0 ef ee ed ec
<CR><LF>
:
8.10 DIRECTORY
8.10.1 DIRECTORY _________________________________________________________ LIST FILES
Purpose: List all files.
Format:
DIRectory
LS
Remarks: The time stamp is UTC. The wildcards "*" and "?" can be used to specify a
group of files.
Example
List all files in the Transceiver. Type
: dir<CR><LF>
<CR><LF>
EVENT
LOG
EGC
001
REPORT
000
TEST
TXT #
4 File(s)
:
Command Reference
50 2001-05-17 16:21<CR><LF>
234 2001-05-17 13:00<CR><LF>
152 2001-05-17 11:47<CR><LF>
245 2001-08-23 11:47<CR><LF>
117760 bytes free<CR><LF>
86
Directory
]
]
]
]

The first two columns give the filename (name and extension), where the character #
indicates an open file. The next column gives the number of bytes in the file. The last
two columns give the UTC date and time for the file creation. The last line gives the
number of files listed, and the number of free bytes in the file system.
List all files beginning with "REP" followed a three-letter extension by typing:
dir rep*.*<CR>
REPORT
009
REPORT
011
REPORT
013
REPORT
015
4 File(s)
216
147
212
169
97-03-14 12:05<CR><LF>
97-03-14 12:11<CR><LF>
97-03-14 12:23<CR><LF>
97-03-14 12:32<CR><LF>
117760 bytes free<CR><LF>
8.11 EV
8.11.1 EV -C ___________________________________________________ CLEAR EVENT PROGRAM
Purpose: Clear event program
Format:
EV -c <entry>
entry:
reference to specific event program. (0-14)
8.11.2 EV -D _________________________________________________ DISPLAY EVENT PROGRAMS

Purpose: Display event programs.
Format:
EV -d
This command displays all event parameters for the active event programs. Please note
that settings are only visible for events the user has permission to see. See section 8.31
for more information about user level authority.
8.11.3 EV -E ________________________________________ SETUP EXTENDED EVENT PARAMETERS
Purpose: Setup extended parameters. [ver 1.04]
Format:
EV -e <entry>,<retxfailed>,<store>, <normafterantblock>,[antblockedfn]
entry:
retxfail:
Retransmit failed reports. Setting retxfail only has effect when using
enhanced data reporting (enhanced data reporting is used by default if the
used LES support the service [ver 2.15]). [0 - 4]
store:
Save Stored reports. When this mode is enabled, reports will be saved when
no satellites are visible. When the satellite becomes visible again, the stored
reports will be sent. Up to 250 reports can be stored.
0 = stored reports disabled
1 = stored reports enabled
normafterantblock: Normal position report after antenna blocked report.

0 = Normal position report after antenna blocked report disabled
1 = Normal position report after antenna blocked report enabled
antblockedfn: Only send unblock data report if an interval program based on the same
DNID has failed during blocking. See section 4.7.2 . [2.12]
Command Reference
87
EV

0 = Unblock data reports are always sent.

1 = Unblock data reports are only sent if interval program failed during
blocking.
8.11.4 EV -FE _________________________________ DEFAULT EXTENDED PROGRAM PARAMETERS

Purpose: Setup default extended parameters for eventprograms. [ver 2.12]
Format:
EV -fe <retxfail>,<store>,<normafterantblock>, <antblockedfn>
See details about "retxfail", "store", "normaafterblock" , "antblockedfn" in section 8.11.3

Example:
: ev -fe 1,1,1,1
: ev -fe
Retx
1
store
1
nantb
1
antbtfn
1
8.11.5 EV -FP ___________________________________________ DEFAULT PROGRAM PARAMETERS

Purpose: Setup default parameters for eventprograms for autocreation. [ver 2.12]
Format:
EV -fp <powerctrl>,<sleepmode>,<io>,<antennablockedtime>,
<gpsblockedtime>,<zoneevents>,<speedevents>
See details about "powerctrl", "sleepmode", "io", "antennablockedtime",

"gpsblockedtime", "zoneevents", "speedevents" in section 8.11.7 .
Example:
: ev -fp 1,2,1,0,0,1,0
: ev -fp
Pwctrl
1
sleep
2
io
1
antbt
0
gpsbt
0
zone
1
speed
0
8.11.6 EV -O ____________________________________________ OPEN/CREATE EVENT PROGRAM

Purpose: Open/create event program.
Format:
EV -o <LES>,<DNID>[,<mem>]
LES:
Land Earth station to be used for event reporting.
DNID:
Destination Network ID to be used.
mem:
Member number.
Command Reference
88
EV

8.11.7 EV -P ________________________________________ PROGRAM/SPECIFY EVENT PROGRAM

Purpose: Program/specify event program.
Format:EV -p <entry>,<powerctrl>, <sleepmode>,
<io>,<antennablockedtime>,<gpsblockedtime>,<zoneevents>,<speedevents>
entry:
powerctrl: Send datareport at power- up and down.

0 = no data reports at power- up/down.
1 = send data reports at power- up/down.
2 = only send data reports at power- up/down if an intervalprogram based
on the same DNID has lost reports during power off (See section 4.7.2 ).
sleepmode: send data report when sleepmode is active.
0 = no data reports at sleepmode events.
1 = send data report at sleepmode events.
2 = send data report at sleepmode events except at the enter fixtime
event.[ver 2.05]
io:
send data report at any changes of the I/O-pins.

0 = no data reports at changes of the I/O-pins.
1 = send data reports at changes of the I/O-pins.
antennablockedtime: this parameter is the number of minutes the antenna must be

blocked before an Antenna blocked report is issued. The count down is
initiated when the number of bulletin board errors reaches 80/100. [ver
1.04]
0 = antenna blocked reporting disabled
[1..255] number of minutes before report is sent.
gpsblockedtime:
Number of minutes with blocked GPS before a position report is sent. [ver
1.04]
0 = GPS blocked reporting disabled
[1..255] number of minutes before report is sent.
zoneevents: This parameter enables/disables the leave zone and enter zone reports.
[ver 1.04]
See 4.11 Surveillance zones.
0 = no data report at zone events
1 = sends data report at zone events
2 = [ver. 2.10] sends data report only when moving between inside zones
and outside.
speedevent: This event enables/disables speedevent reports. [ver 1.04]
See 8.28.28 SET -sp Speed Limits.
0 = sends data report at speed event
1 = no data report at speed event
8.12 FI
8.12.1 FI FISHERY CONFIGURATION
Purpose:Display and set fishery configuration. [ver 2.12]
Format:FI {<command>}
Command Reference
89
FI

Handles the fishery configuration. Only for backwards compatibility

8.12.2 FI 34 ___________________________________________________________ AUTOGROUPING
Purpose: Enable or Disable autogrouping. Autogrouping only affect those DNIDs with
an 'A' as the 25. character of provider name.
Format:
FI 34 <value>
Value:
0 (disable) / 1 (enable)
8.12.3 FI 72 __________________________________________________ SET MAX NUMBER OF DNID

Purpose: Set maximum number of DNIDs.
Format:
FI 72
Prompts: Set max number of DNID: {value}

Value:
[0 - 64]
Note. Identical to the dn -n command.
8.13 FX
8.13.1 FX __________________________________________________________SET FIXED POSITIONS
Purpose: Displays the main menu
Format:
FX {<lat>,<N|S>],<lon>,<E|W>}
FX -d
FX
A list of fixed positions can be entered into the transceiver. For example, a list of
positions where the vessel is expected to be in the nearest future can be entered. This
causes the transceiver to receive geographically addressed EGCs as if the transceiver
were located at the specified positions. An example of use could be to receive
meteorological warnings about areas that the vessel is approaching.
Using the command with a list of positions as parameter sets up those fixed positions in
the transceiver. Positions are given with a precision of 1 degree.
Using the command with no parameters clears the list of fixed positions.
Using the command with the "-d" parameter displays the current list of fixed positions.
Up to 7 fixed positions may be entered using this command.
Example
Set up three fixed positions
Command Reference
90
FX

: fx 30,N,12,E 27,N,5,E 24,N,3,W<CR><LF>

<CR><LF>
:
Show fixed positions
: fx -d<CR><LF>
<CR><LF>
3 fixed position(s)<CR><LF>
30 N 12 E<CR><LF>
27 N 5 E<CR><LF>
24 N 3 W<CR><LF>
:
Clear fixed positions
: fx<CR><LF>
<CR><LF>
:<CR><LF>
8.14 GPS
[ver 2.21]
8.14.1 GPS ______________________________________________________ GPS CONFIGURATION
Purpose: Configuration and inspection of the GPS receiver.
Format:
GPS <options>
8.14.2 GPS -D ______________________________________________________ DISPLAY SBAS STATE

Purpose: Display the current SBAS reception status.
Format:
Example:
GPS -d
: gps -d<CR><LF>
<CR><LF>
GPS mode
: 2<CR><LF>
SBAS satellite PRN : 120<CR><LF>
DGPS information age: 2.1<CR><LF>
The fields are described in Table 8.2 GPS SBAS status values.
GPS Mode
0: No fix
1: GPS fix
2: DGPS fix (using SBAS)
SBAS satellite PRN
Satellite PRN for SBAS; blank if no SBAS
DGPS information age
Age in seconds if DGPS information; blank if no

SBAS
Table 8.2 GPS SBAS status values
8.14.3 GPS -G ______________________________________ DISPLAY STATUS OF THE GPS RECEIVER

Purpose: Display status of the GPS receiver.
Format:
GPS g
Equivalent to the RU g command. See section 8.26.1 for more information.
Command Reference
91
GPS

8.14.4 GPS -S _________________________________________ SHOW OR SET SBAS CONFIGURATION

Purpose: Set or display the current SBAS reception set-up
Format:
GPS s <SBAS mode>,<PRN>

GPS -s
SBAS mode:Reception mode.

0: SBAS reception off
1: SBAS reception on
2: SBAS reception on, allow test mode messages (type 0)
PRN:
Specifies SBAS satellite PRN

0: Take any available satellite
100...132: Request a specific satellite
See section 2.6 for more information on GPS and SBAS.
8.15 HELP
8.15.1 HELP ____________________________________________________ SHOW COMMAND HELP
Purpose: Displays the main menu.
Format:
HElp
?
This command shows a list of the transceiver commands available at the current user
level. See section 8.31 for more information about user levels
8.16 ID
8.16.1 ID ______________________________________________________ SYSTEM IDENTIFICATION
Purpose: Show system identification data.
Format:
ID
Prints the system identification parameters.
8.17 IO
Purpose:Configuration of io-pins .
Format:
IO <options>
This command cannot be used on a transceiver that is part of an SSAS installation

(supporting Covert Security alert) since this will reserve all io-pins for the alert
functions.
Command Reference
92
Help

For other transceivers the io-pins from 2 to 6 can be programmed for various purposes.
Input-pin(s) can be programmed to initiate an internal event, causing a data report to
be sent or for example changing reporting interval etc.
Output-pin(s) can be programmed to change output-behavior (low- or high-level) on
various interval events.
Up to 16 io-events can be programmed.
8.17.1 IO -C ________________________________________________________ CLEAR IO-PIN SETUP
Purpose: Clear/removes and io-pin configuration.
Format:
IO -c <id>
Id:
[0..15], Id number used when showing io-pin configurations. See "io -s"
8.17.2 IO -I ___________________________________________________________ INPUT-PIN SETUP

Purpose: This command is used for assigning events to an input-pin.
Format:
IO -i ?
IO -i <PinNo>,<InitialLevel>,<LowLevelEvent>,<HighLevelEvent>
Displays help and Input Event Table.
PinNo:
[2..6] Pin reference number
InitialLevel:
Value currently not used.
LowLevelEvent:
Event on input-level low.
HighLevelEvent: Event on input-level high.

The table below shows current available input-events.
Input Event Table
Command Reference
Value
No event
Long Reporting Interval
Short Reporting Interval
Change output A
Change output B
Sleep reporting filter on
Sleep reporting filter off
93
IO

8.17.3 IO -O __________________________________________________________ OUTPUT-PIN SETUP

Purpose: This command is used for assigning events to an output-pin.
Format:
IO -o ?
IO -o <PinNo>,<InitialLevel>,<LowLevelEvent>,<HighLevelEvent>
Displays help and Input Event Table.
PinNo:
[2..6] Pin reference number
InitialLevel:
[ 0:Low | 1:High ], Initial output-level.
LowLevelEvent:
Event on output-level low.
HighLevelEvent: Event on output-level high.
A single output-pin can be programmed more then once. Ex. to respond on

enter/leave-zone and on antenna blocked etc. The last occurred event controls the
output.
Remember always to pair Low-/High-LevelEvent for output, unless an output is wanted
to toggle once (singleshoot).
The table below shows current available output-events.
Output Event Table
Value
No event
Enter Zone
Leave Zone
Antenna Blocked
Antenna Unblocked
GPS Blocked
GPS Unblocked
Below Speed Limit
Above Speed Limit
Change output A
Change output B
10
The Speed Limit, which is mentioned in items 7 and 8 above, is explained in section 4.8
Speed Limit Event.
Command Reference
94
IO

8.17.4 IO -S _________________________________________________________ SHOW IO-PIN SETUP

Purpose: Show all io-pin configurations.
Format:
IO -s
Example:
: io -s<CR><LF>
Id PinNo Type Init LowEvent HighEvent<CR><LF>
0
2
O
1
1
2<CR><LF>
1
3
O
1
2
1<CR><LF>
2
4
I
0
1
3<CR><LF>
3 entries used
:
8.17.5 IO -T _____________________________________________________ TACHOGRAPH PIN SETUP

[ver 2.12]
Purpose: Configure an io-pin as tachograph interface. See section 2.5.2 Tachograph
Interface Pin for an introduction to the tachograph function.
Format:
IO -t ?
IO -t <InitValue>,<PinNo>,<EdgesPr100km>,<StopDiscoverTime>,
<ParkDiscoverTime>, <StartEdgeCount>
InitValue:
[0..4000000000] Set the initial value of the tachograph counter

measured in [100 m] steps.
PinNo:
[2..6] Pin reference number.
EdgesPr100km:
[1..60000] Number of edges per [100 km].
StopDiscoverTime:[1..250] Seconds without edges before a stop event is recognized.

ParkDiscoverTime:[1..250] Minuts stopped before a park event is recognized.
StartEdgeCount: [1..250] Number of edges before a start event is recognized.
Examples:
Configure pin 2 as tachograph interface pin; start counter at 43,000 km:
: io -t 430000,2,5000,30,15,50<CR><LF>
The corresponding configuration list:

: io -s<CR><LF>
<CR><LF>
Id PinNo Type Init LowEvent HighEvent<CR><LF>
0
2
T<CR><LF>
1 entries used<CR><LF>
<CR><LF>
Tachograph count : 2150000 (43000 km) <CR><LF>
Edges per [100km]: 5000<CR><LF>
Stop latency [s] : 30<CR><LF>
Park latency [m] : 15<CR><LF>
Start latency
: 50<CR><LF>
State
: Parked<CR><LF>
Note that the Tachograph count is presented as an edge count of 43,000 km x 0.01 x
5000 edges per [100 km]. The IO-s command is described in paragraph 8.17.4 .
Command Reference
95
IO

8.18 LI
8.18.1 LI ______________________________________________________________________ LOGIN
Purpose: Issues a login request to an NCS.
Format:
LI <ncs_id | channel_no>
ncs_id is an integer in the range 1-63, 100-163, 200-263 or 300-363.

channel_no is an integer in the range 8000-14000.
It is strongly recommended to use the NCS ID specification method instead of the
channel number method, as the NCS ID also indicates to the transceiver which ocean
region to be used.
If no parameters are specified the Transceiver will use the main NCS in the preferred
ocean region.
The preferred ocean region is set by the command set -o command. If the preferred
ocean is set to none, the Transceiver will send the login request to current NCS.
The current NCS is the NCS channel that the transceiver is currently tuned to. The
current NCS can be set with the ncs -g command.
The date and time of the last login/logout can be seen with the st -c command.
Note: The Transceiver may start an automatic login. See 2.1.3 Automatic Login for
details about when this will occur.
8.19 LO
8.19.1 LO ___________________________________________________________________ LOGOUT
Purpose: Issues a logout request to the Network Co-ordinating Station.
Format:
LO
This command initiates a logout procedure from the current NCS.

A transceiver should always be logged out when turned off for more than a few hours.
The date and time of the last login/logout can be seen with the st -c command.
8.20 LOG
[ver 2.12]
Command Reference
96
LI

Purpose: Control the data-logging feature, see chapter 7

Format:
The data-logging feature.
LOG <options>
8.20.1 LOG -C ____________________________________________________ CLEAR THE DATA-LOG

Purpose: Clear the log: Delete all stored data and stop logging.
Format:
LOG -c
8.20.2 LOG -D ______________________________________________ DISPLAY DATA-LOG SETTINGS

Purpose: Display the current log settings and status.
Format:
LOG -d
8.20.3 LOG -E _________________________________________SET EXTENDED DATA-LOG SETTINGS

Purpose: Change the current settings for the extended log options. Can only be used
when the log is cleared.
Format:
LOG -e <StopWhenFull>
StopWhenFull: Stop when full or delete oldest data.

0 = When the log is full the oldest data is erased and the space is used for
new data.
1 = When the log is full the logging stops.
8.20.4 LOG -F _________________________________________________ SELECT DATA-LOG FIELDS
Purpose: Select the data fields to be included in the log. The command can only be
used when the log is cleared.
Format:
LOG -f <timeGPS>,<PosGPS>,<SpeGPS>,<CouGPS>,<I/O>,
<DistTG>,<SpeTG>
timeGPS: Time of GPS data.

0 = Time stamp for GPS data is not included in the log.
1 = Time stamp for GPS data is included in the log.
PosGPS:
The position GPS data.

0 = GPS position is not included in the log.
1 = GPS position in 0,005 fraction of a minute is included in the log.
2 = GPS position in 0,001 fraction of a minute is included in the log. [ver 2.19]
SpsGPS:
The speed GPS data.

0 = GPS speed is not included in the log.
1 = GPS speed in fractions of 1 km/h is included in the log.
2 = GPS speed in fractions of 0,1 knots is included in the log. [ver 2.19 ]
CouGPS: The course GPS data.

0 = GPS course is not included in the log.
1 = GPS course is included in the log.
I/O:
Command Reference
I/O pin data.

0 = I/O data is not included in the log.
1 = I/O data is included in the log.
97
LOG

DistTG:
The total travelled distance tachograph data.

0 = Tachograph distance is not included in the log.
1 = Tachograph distance is included in the log.
SpeTG:
The speed tachograph data.

0 = Tachograph speed is not included in the log.
1 = Tachograph speed is included in the log.
8.20.5 LOG -I _________________________________________________________ START LOGGING

Purpose: Start logging data.
Format:
LOG -i
8.20.6 LOG -P _________________________________________________ SELECT DATA-LOG EVENTS

Purpose: Select the events, which is to create entries in the log. The command can
only be used when the log is cleared.
Format:
LOG -p <timeout>,<startTG>,<parkTG>
Timeout: Interval timer. Every time an entry is created an interval timer is reset and
when a timeout occurs a new entry is created.
0 = The interval timer is not used.
5..43200 = The number of seconds used for the interval timer.
StartTG:
Tachograph start event.

0 = The event is not used.
1 = The event creates an entry.
2 = The event creates an entry and starts the interval timer.
3 = The event creates an entry and stops the interval timer.
ParkTG:
Tachograph parked event.

0 = The event is not used.
1 = The event creates an entry.
2 = The event creates an entry and starts the interval timer.
3 = The event creates an entry and stops the interval timer.
8.20.7 LOG -S __________________________________________________________ STOP LOGGING

Purpose: Stop logging data.
Format:
LOG -s
8.20.8 LOG -X _____________________________________________________ TRANSFER DATA-LOG

Purpose: Transferring all log data in a given time interval, using the X-modem
protocol.
Format:
Command Reference
LOG -x <StartDate>,<StartTime>,<EndDate>,<EndTime>
98
LOG

StartDate: The start date of the time interval.

Format: YYYY-MM-DD.
StartTime: The start time of the time interval.
Format: HH:MM
EndDate: The start date of the time interval.
Format: YYYY-MM-DD.
EndTime: The stop time of the time interval.
Format: HH:MM
8.21 NCS
Purpose: Management of NCS id's and channels.
Format:
NCs <options>
The NCS list is a user configured list of Network Co-ordinating Stations. There is one
main NCS in each of the four oceans. The four main NCS are specified by INMARSAT
and pre-programmed by Thrane & Thrane (the first line of the list) and they can not be
altered or removed.
The add and delete functions are a supplement to the set -l command. The nc -g
command is used to set the current NCS (see the set -o command and the li command).
The scan command can be used if the transceiver is in an overlap region.
8.21.1 NCS -A _____________________________________________________________ ADD AN NCS
Purpose: Add an NCS to the NCS list.
Format:
NC -a <ncs_id,ncs_channel><options>
The Inmarsat-C system is capable of operating with spot beams. Each spotbeam will
have an Id and common channel number, and shall be entered manually using this
command.
8.21.2 NCS -G _____________________________________________________ GO TO SPECIFIC NCS
Purpose: Go to a specific NCS.
Format:
NC -g <ncs_id><options>
NC -g <ncs_channel><options>
NC -g <ncs_id,ncs_channel><options>
ncs_id:
An integer in the range 1-63, 100-163, 200-263 or 300-363.
ncs_channel: An integer in the range 8000-14000

Go to a specific NCS, using NCS id, channel number, or both.
Command Reference
99
NCS

8.21.3 NCS -L __________________________________________________________ SHOW NCS LIST

Purpose: Show NCS list
Format:
NC -l <options>
Remarks: Similar to SE -l
Example
To change the current NCS to the Atlantic ocean main NCS, type:
or
ncs -g 144
ncs -g 11080
These specific values can be seen in the description of the set -l command.
To scan only the Indian ocean region, type:
set -o i
to select Indian as the preferred ocean region. Then type:

ncs -s
to initiate a scanning of this ocean region.

8.21.4 NCS -R _________________________________________________________ REMOVE AN NCS
Purpose: Remove a user defined NCS from the NCS list
Format:
NC -r <ncs_id> <options>
8.21.5 NCS -S _________________________ INITIATE SCANNING FOR THE STRONGEST NCS SIGNAL
Purpose: Initiate a scanning for the strongest NCS signal.
Format:
NC -s <options>
Initiate a scanning of the preferred ocean region part of the NCS list, for the strongest
NCS signal. Tune to and login at that NCS. If none is selected as the preferred ocean
region, then all the allowed regions will be scanned.
Command Reference
100
NCS

Scanning ocean regions:

Preferred ocean setting
Allowed ocean(s) setting
Automatic ocean-region shift

behavior
Preferred ocean set to "NONE"

and login on the strongest spot. If
synchronising to current ocean
region fails the other regions are
scanned.

If synchronising to current ocean
region fails the allowed regions are
scanned.
Preferred ocean set to an ocean
(W, E, P or I)

If synchronising to preferred ocean
region fail the other regions are
scanned.

If synchronising to preferred ocean
region fail the allowed regions are
scanned.
8.22 PASSWORD
8.22.1 PASSWORD _________________________________________________ CHANGE PASSWORD
Purpose: Changes user password.
Format:
PASSWORD < username >

PASSWD < username >
Prompts: Enter password:

Confirm password:
This command changes the password of <username>. The effective user id must be at
the same or higher level as <username>. The password protection of a user id/level
can be removed by entering a <CR> when prompted for a password.
Username can be one of the 3 built in user accounts.
See also the SU command.
Example
Command Reference
passwd super<CR>
Enter new password:*****<CR>
Confirm new password:*****<CR>
Password for user super changed.
101
Password

8.23 PG
Purpose: Setting up the Transceiver for Inmarsat-C PU reporting.
Format:
PG <options>
A connection opened with the pg command is marked as local and can not be changed
by any polls. In the same way connections opened by polls (Inmarsat PU program polls,
or T&T Proprietary Download DNID Poll) are marked as remote and can not be changed
by the pg command.
When a connection is opened all settings will be set to their default values; and these
default values are also through this pg command.
8.23.1 PG -A _____________________________________________________ SET ALERT ACTIVATION
Purpose: Selects whether an interval program should be started or altered when an
alert is issued.[ver 2.12]
Format:
PG -a <connection>,<alert controlled>,<alert interval>
connection: Points out the interval program to be configured

alert controlled: Enables the alert control
0 = alert control off
1 = alert control on
alert interval: Sets the reporting interval (measured in frames) for alert reporting.
Example
: pg -a 0,1,200
Connection no: 0, Alert controlled: 1, Alert interval: 200
:
Enables the alert control for an interval report program. See section 6.4 Alert reporting
for description of this feature.
8.23.2 PG -B _______________________________________ VALUE OF SPAREBIT FOR DATEFORMAT 3
Purpose: Set value of sparebit for dateformat 3 (sparebit located in packed 2, byte 6,
bit 8). [ver 2.12]
Format:
PG -b <connection>[,<status>]
connection: Program connection [0 - 14]

status:
00/cleared or 80/set
All connections relate to the same spare bit value - only for backwards compatibility.
Command Reference
102
PG

8.23.3 PG -C _______________________________________________ CLOSE A LOCAL CONNECTION

Purpose: Close a local connection.
Format:
PG -c <connection>
Close the local connection given by <connection>, where <connection> is the

connection number.
Open connections can be displayed by using the pg -d command.
8.23.4 PG -D __________________________________________ OVERVIEW OF CONNECTION STATUS
Purpose: Display an overview of the Transceivers connection status.
Format:
PG -d [<connection>]
Without the optional connection number the pg -d command will display an overview of
the Transceivers connection status.
Example
: pg -d<CR><LF>
<CR><LF>
Connection Program
0: remote
PU[ip]
1: local
PU[ip]
2: closed<CR><LF>
3: closed<CR><LF>
:
Ocean region<CR><LF>
131,2540,49<CR><LF>
131,2541,49 312,6202,49<CR><LF>
The connection can have the status remote, local or closed. A remote connection has
been opened and programmed by sending poll to the Transceiver. A local connection
is opened and programmed by the pg command.
Each connection can contain one program, which can be PU. The PU program is as
defined by Inmarsat and a connection can be programmed with PU using the Inmarsat
defined polls.
The letters inside the [ ] give information about the status of the connection:
p
i
s
data loaded from the GPS (sub-address 1)

Initiated
stopped
More information about the programming can be displayed by including the

connection number in the pg -d command.
Example
Command Reference
: pg -d 0<CR><LF>
<CR><LF>
LES DNID Mem
OK
Err Inter Sub Rd <CR><LF>
131 2540 49
5
0
200
1 10<CR><LF>
<CR><LF>
Start at : 2955 (01-04-11 07:05:31)<CR><LF>
Next at : 4155 (01-04-11 09:58:19)<CR><LF>
End at
: <CR><LF>
Status
: 0 - OK<CR><LF>
103
PG

Table 8.3 on page 68 summarises the status items:

LES
Land Earth Station ID.
DNID
Data Network ID.
Member
Member Number in the DNID group.
OK
The number of successful data reports
Err
The number of failed data reports.
since power-on.
Inter
Frame interval between each report
Sub
Sub-address
Sub-address currently being used by a

specific connection.
Rd
Start at
Random number
Frame number and the corresponding
date & time where the program was
started
Next at
Frame number and the corresponding

date & time where the next report is to
be sent.
Code
This reports the state of the

programming.
0 - OK
The program is running normally
1 - Overflow
Internal error such as erroneous

parameters given in the program poll
packet.
2 - Frame timing error
This appears if the Transceiver can not

get the NCS TDM frame number
information. This state will occur during
the normal tuning operations. If the state
exists for more than a minute check the
TDM channel number and the antenna
connection.
4 - Stopped
The program has been stopped with a
<other> - Unknown
Internal error.
stop poll packet.
Table 8.3 Connection Status Summary
8.23.5 PG -E ________________________________________________ EXTENDED PROGRAM SET-UP

Purpose: Set-up Extended program parameters.
Format:
PG -e <connection>,<remote>,<rand>,<zoneint>,
<retxfail>,<store>,<longshortinterval>,<mindist>,<tacho>,<wksch>
Change type of a connection (0=local, 1=remote) and random interval for a connection.
connection: Program connection number [0 - 14]
remote:
Change type of a connection

0 = local
1 = remote,
Command Reference
104
PG

rand:
Randomization interval [0 - 255]
zoneint:
Zone Interval[ver 1.04]

0 = don't use zone interval.
1 = use zone interval,
retxfail:
Retransmit failed reports. Setting retxfail only has effect when using
enhanced data reporting (enhanced data reporting is used by default if the
used LES support the service [ver 2.15]). [0 - 4]
store:
Save Stored reports. When this mode is enabled, reports will be saved when
no satellites are visible. When the satellite becomes visible again, the stored
reports will be sent. Up to 250 reports can be stored. [ver 1.04]
0 = stored reports disabled
1 = stored reports enabled
longshortinterval: This feature enables the transceiver to have two different position
reporting intervals. A long reporting interval for use when the vessel/vehicle
has not moved more than the configured number of meters (ex. 400 meter)
since last report and a short interval at all other times. [ver 1.04]
0 = long-short interval disabled
1 = long-short interval enabled
mindist:
Before a scheduled position report is sent, the transceiver checks if the

position in the last report and the current position are at least the minimum
distance apart. The minimum distance can be configured and if set to 0 m. all
scheduled position reports are sent. [ver 1.04]
0 = minimum distance disabled
1 = minimum distance enabled
tacho:
The tachograph input may be used to control the interval reporting so that
reports are postponed when the vehicle is stopped or parked. See
paragraph 2.5.2 for general information on the tachograph interface
function. [ver 2.12]
0 = tachograph event control disabled
1 = tachograph event control enabled
wksch:
Activate the week schedule control which makes it possible to limit the
generation of interval reports. See paragraph 8.37 Weeksched for further
information. [ver 2.12]
0 = disable week schedule control
1 = enable week schedule control
8.23.6 PG -FA ____________________________________________ SET DEFAULT ALERT ACTIVATION

Purpose: Selects whether a newly created interval report program should have alert
control enabled by default.[ver 2.12]
Format:
PG -fa <alert controlled>,<alert interval>
alert controlled: Sets the default alert control

0 = alert control off
1 = alert control on
Command Reference
105
PG

alert interval: Sets the default reporting interval (measured in frames) for alert
reporting.
The options for this command corresponds to the PG -a command except that no
<connection> number is given; this is because these settings does not apply to any
existing interval program but will be inserted into any future programs created. See
paragraphs 8.23.1 PG -a Set alert activation and 6.4 Alert reporting.
8.23.7 PG -FE _______________________________________ DEFAULT EXTENDED PROGRAM SET-UP
Purpose: Setup default program format for new programs being created. [ver 2.12]
PG -fe <resv>,<rand>,<zoneint>,
Format:
<retxfail>,<store>,<longshortinterval>,<mindist>,<tacho>,<wksch>
The options for this command corresponds to the PG -e command except that no
<connection> number is given and the <remote> option has been exchanged with an
unused field <resv>; The connection number is omitted because these settings does not
apply to any existing interval program but will be inserted into future programs
created. The remote option has been removed because whether future program is
remote or local depend on whether it is created locally or remote. See paragraph 8.23.5
PG -e Extended program set-up.
Example:
: pg -fe 0,4,0,0,0,0,0,0,1
: pg -fv
Resv
0
Rd Zone ReTx Store LSInt MDist Tacho WkSch

4
0
0
0
0
0
0
1
Selects this option combination (with <WkSch> set) as standard values for future
generated interval programs.
8.23.8 PG -FL ________________________ SET DEFAULT LONG INTERVAL AND MINIMUM DISTANCE
Purpose: Set default settings for long interval and minimum distance [ver 2.12]
Format:
PG -fl <longinterval>,<distance>[,<pwron reset>][,<GPS req.>]
This command sets long short interval, minimum distance automatic reset of report
interval and whether GPS fix is required.
longinterval: Long interval in frames between reports [20-10000]
distance: Units of 10 meters [0-65535]
The options for this command corresponds to the PG -l command except that no
paragraph 8.23.12 PG -l Set Long Interval and Minimum Distance.
pwron reset:Controls whether the report interval should reset to short on power up.
[2.14]
0 = Do not change the report interval on power up.
1 = Set the report interval to short on power up.
Command Reference
106
PG

GPS req.Controls whether a recent GPS fix is required to accept a change to long
interval mode. [2.14]
0 = Change of interval mode is done regardless of GPS fix.
1 = Change of interval mode requires GPS fix.
8.23.9 PG -FP ________________________________________ SET DEFAULT PROGRAM PARAMETERS
Purpose: Set the default connection values for future created programs. [ver 2.12]
Format:
PG -fp <interval>[,<start frame>]
The options for this command corresponds to the PG -p command except that no
paragraph 8.23.14 PG -p Program a Local Connection.
8.23.10 PG -FV _____________________________ VIEW DEFAULT EXTENDED PROGRAM PARAMETERS
Purpose: View default extended program parameters [ver 2.12]
Format:
PG -fv
This command displays the extended parameters assigned to interval programs that
are created.
See also 8.23.7 PG -fe Default extended program set-up and 8.23.16 PG -v View
Extended Program Parameters.
8.23.11 PG -I ________________________________ INITIATE A PROGRAMMED LOCAL CONNECTION
Purpose: Initiate the PU programmed local connection given by <connection>
Format:
PG -i <connection>[,p] <options>
Initiate the PU programmed local connection given by <connection> [0 - 14]. If the "p"
parameter is included, the datareports are sent as position reports containing the GPS
position. If the "p" is omitted, the DTE must supply the data for the report.
8.23.12 PG -L ________________________________ SET LONG INTERVAL AND MINIMUM DISTANCE
Purpose: Set long interval and minimum distance
Format:
PG -l <conn>,<longinterval>,<distance>[,<pwron reset>][,<GPS req.>]
This command sets long interval, minimum distance, automatic reset of report interval
and whether GPS fix is required.
conn:
Program connection [0 - 14]
longinterval: Long interval in frames between reports [20-10000]

distance: Units of 10 meters [0-65535]
pwron reset:Controls whether the report interval should reset to short on power up.
[2.14]
0 = Do not change the report interval on power up.
1 = Set the report interval to short on power up.
Command Reference
107
PG

GPS req. Controls whether a recent GPS fix is required to accept a change to long
interval mode. [2.14]
0 = Change of interval mode is done regardless of GPS fix.
1 = Change of interval mode requires GPS fix.
8.23.13 PG -O _______________________________________________ OPEN A LOCAL CONNECTION
Purpose: Open a local connection.
Format:
PG -o LES_id, DNID[,MemberNo]{ LES_id, DNID[,MemberNo]}
The LES ID, the DNID and the member number must be supplied as found in the DNID
table. The DNID table is displayed by the dn -d command.
Example
: pg -o 131,2540,49<CR><LF>
<CR><LF>
INFO 459: Connection no. 1 opened<CR><LF>
: pg -d<CR><LF>
<CR><LF>
Connection Program Ocean region<CR><LF>
0: remote
PU[ip]
131,2540,49<CR><LF>
1: local
PU[-]
131,2540,49<CR><LF>
2: closed<CR><LF>
3: closed<CR><LF>
:
Up to four LES_id, DNID can be linked pairs; one for each ocean region.
Example
pg -o 131,2540,49 31,2540,49
8.23.14 PG -P ___________________________________________ PROGRAM A LOCAL CONNECTION

Purpose: Program a local connection.
Format:
PG -p <connection>,<interval>[,<start frame>]
Program the local connection given by <connection> to send data reports every
<interval> frames [20-10000].
Optionally specify the frame no. <start frame> at which the data reporting should
begin. If <start frame> is not specified the data reporting will begin within 5 minutes [09999].
8.23.15 PG -S __________________________________ STOP A PROGRAMMED LOCAL CONNECTION
Purpose: Stop the PU programmed local connection given by <connection>.
Format:
PG -s <connection>
Stop the PU programmed local connection given by <connection>.
Command Reference
108
PG

8.23.16 PG -V _____________________________________ VIEW EXTENDED PROGRAM PARAMETERS

Purpose: View Extended program parameters
Format:
PG -v
PG -v <entry>
This command displays the extended parameters for a given program.
8.24 RECVFILE
8.24.1 RECVFILE ________________________________________________________ RECEIVE FILE
Purpose: Receive file from terminal using X-modem protocol.
Format:
RECVFILE <file name>

RF <file name>
This command initiates a file transmission of the file <file name> from the terminal using
the X-modem protocol.
8.25 RO
Purpose: Specifying incoming message storage media. [2.20]
Format:
RO <options>
Format:
ROute <filenum>,<dest>
filenum:
10 : RX Store & forward
30 : EGC System
31 : EGC FleetNET
32: EGC SafetyNET Routine+Safety
33: EGC SafetyNET Urgent+Distress
dest:
1: Memory
2: Local Printer
4: Remote Printer
Combinations can be obtained by adding the numbers.
Omitting parameters displays the current set up.
ro
Configuration of message file output<CR><LF>

File
Type
Destination<CR><LF>
0 : Quit<CR><LF>
10 : RX
Store & forward
: 3 : Memory + LocalPrn<CR><LF>
30 : EGC System
Command Reference
109
Recvfile

31 : EGC FleetNET
: 4 : RemotePrn<CR><LF>
32 : EGC SafetyNET Routine+Safety
33 : EGC SafetyNET Urgent+Distress
<CR><LF>
Enter filenumber > 0<CR>
<CR><LF>
:
Only the value 0 (for Quit) is accepted at the Enter filenumber prompt.
"remote printer" option is only for backwards compatibility.
"local printer" referes to the printer attatched to the TT-3606E Message Terminal.
"memory" referes to floppy disk.
This command can set routing parameters for received messages. The default routing
of the Transceiver depends on the transceiver type. For TT-3000E mini-C GMDSS
System all message types are routed to the connected printer. SafetyNET EGC's are
always routed to memory and local printer. For all other transceiver types all messages
and EGCs are saved in memory and not printed.
Received mail has -number 10, and EGC messages are in the range from 30 to 33.
ROUTE EXAMPLE
ro 31 4
8.26 RU
Purpose: Inspect the status and set the operation of remote units.
Format:
RU <options>
The command without any options gives the option list. An example is:
: ru<CR><LF>
<CR><LF>
-l (arg)
-g (arg)
Legal arguments are :<CR><LF>

List remote units<CR><LF>
GPS satellite info<CR><LF>
8.26.1 RU -G _______________________________________ DISPLAY STATUS OF THE GPS RECEIVER

Purpose: Display the status of the GPS Receiver.
Format:
Command Reference
RU -g <options>
110
RU

Example
: ru -g<CR><LF>
<CR><LF>
<STX>Test Summary: OK
10 visible satellites
SW Version 2.0.00<CR><LF>
Navigation Mode: 1
FOM: 1
UTC:
1<CR><LF>
Accept Altitude: 0
Hold: 0
VPerr: 0 m<CR><LF>
PDOP:
02
HDOP: 01
HPerr: 0 m<CR><LF>
Elevation mask: 00
HVerr: 0 cm/s<CR><LF>
<CR><LF>
Satellite Tracking Status<CR><LF>
Satellites: 05* 30* 14* 09* 04* 24* 29* 06* 25* <CR><LF>
Signal Level:46 46 49 46 47 45 42 43 41 <CR><LF>
Elevation:
075 061 035 034 029 028 028 022 008 <CR><LF>
Azimuth:
150 050 008 209 101 063 014 105 054 <CR><LF>
<CR><LF>
V. Speed :
0 ft/m Altitude:
256 ft<ETX><CR><LF>
Position : <STX>55 47 64 N 012 31 38 E<ETX> at 14:18:46 UTC <STX><ETX><CR><LF>
Course
: <STX>006<ETX> deg/true north<CR><LF>
Speed
: <STX>000<ETX> knots : 0000 kmph : 0000 mph<CR><LF>
<CR><LF>
:
The position part of the information will be the same as with the set -p command.
The satellites marked with a star are currently tracked by the GPS, and used in position
calculations.
The entries are explained in Table 8.4.
Command Reference
111
RU

Navigational
Status
Result of the self-test: Either 'OK' or 'ERROR XXXXH' which is a

hexadecimal error word (16 bits). The Transceiver will indicate FFFFH
from the test is started and until the results are received from the GPS.
Please refer to Table 8.5 GPS Error Codes
for an explanation of the Error Codes.
Visible
This is the number of satellites that the GPS is able to see on the current
Satellites
hemisphere.
SW Version
Software version of the GPS Module.
Navigation
Boolean: 1 for yes, 0 for no. Informs of valid position data.
Mode
FOM
UTC
Field not used. Retained only for backward compatibility.

Boolean: 1 for yes, 0 for no. Informs of valid time received from the GPS
satellites.
Accept Altitude
AltHold
Vperr
PDOP
Position Dilution of Precision: A number representing the geometric

properties of the satellites. A low number indicates a good satellite
geometry resulting in a small position error. PDOP is the RMS value of
HDOP and VDOP.
HDOP
Horizontal Dilution of Precision: A number representing the geometric

properties of the satellites. A low number indicates a good satellite
geometry resulting in a small position error.
Hperr
Hverr
Elevation Mask
Satellite
Data from the five GPS channels. Satellite Vessel ID, carrier to noise in
Tracking
dBHz, elevation angle and azimuth of the satellite.
Status
Position
Latitude and longitude of the last position (maybe from the non-volatile
storage).
V. Speed
Field not used. Retained only for compatibility.
Altitude
Not referring to mean sea level. For global applications, the geodetic
reference (datum) used for GPS is the World Geodetic System 1984
(WGS84). Altitude is described as the perpendicular distance above the
ellipsoid surface (which is not to be confused with the mean sea level
datum). The WGS84 ellipsoid approximates the geoid (The datum that
defines the mean sea level) on a worldwide basis with deviations between
the two datums never exceeding 100 meters. Altitude is measured in feet.
Speed
Horizontal speed in knots, km per hour and miles per hour.
Table 8.4 GPS entries
Command Reference
112
RU

4 digit hex
Description
Cause
Ex. 8000H
Not yet synchronised to no. of satellites necessary
GPS currently has no fix.
to get fix.
Value or OK
Bit 15
Not possible to get fix due to antennas view to the

sky is blocked.
Defect GPS module.
Note: If fix is lost for 30 minutes, the GPS module
will reset.
Bit 14 - bit 1
Not used. Retained only for
Bit 0
Ex. 0001H
compatibility.
Initialisation error. Try resetting the transceiver.
Failed to read from GPS

serial interface.
Table 8.5 GPS Error Codes
8.26.2 RU -L ___________________________________ LIST THE CURRENTLY CONNECTED DEVICES

Purpose: List the current connected devices and show their status.
Format:
RU -l <options>
An example is:
: ru -l<CR>
<CR><LF>
Device Nav SatCnt
BGPS
<STX>1<ETX>
PDOP
5
AltHold UTC Stat<CR><LF>

002
0
<STX>1<ETX>
The Built-in GPS columns have the following interpretation:

Device
List the name of the connected device: BGPS for the built-in GPS Module.
Nav
Navigation Mode: 1 for yes, 0 for no, signifies valid position data.
SatCnt
OK<CR><LF>
This is the number of satellites that the BGPS uses for it's position calculations.
This may be less than the number of tracked satellites
PDOP
Position Dilution of Precision: A number representing the geometric properties of

the satellites. A low number indicates a good satellite geometry resulting in a
small position error.
AltHold
Field not used. Retained only for compatibility.
UTC
Indicates if the GPS supplies a valid UTC (1) or not (0).
Stat
Result of the self-test: Either 'OK' or 'ERROR XXXXH' which is a hexadecimal error
word (16 bits). The Transceiver will indicate FFFFH from the test is started and
until the results are received from the GPS.
Table 8.6 GPS Status Interpretation
8.26.3 RU -P _______________________________________________________ SET PRINTER STATUS

Purpose: [2.20] Set printerstatus. This command is normally used by the TT-3606E to
indicate printerstatus for the TT-3000E mini-C GMDSS System. It is not
adviced to manually use this command!
Format:
Command Reference
RU -p <options>
113
RU

"Out of paper", "Paper low" or "Offline":

: ru -p 1<CR><LF>
Printer OK:
: ru -p 0<CR><LF>
Note, this command is only available for the TT-3026C.
8.27 SENDFILE
8.27.1 SENDFILE ___________________________________________________________ SEND FILE
Purpose: Send file from transceiver to terminal using X-modem protocol.
Format:
SENDFILE <file name>

SF <file name>
This command initiates a file transmission of the file <file name> from the transceiver to
the terminal using the X-modem protocol.
8.28 SET
8.28.1
Purpose: Adjust or display transceiver settings.
Format:
SEt <options>
The set command has several options. The default is to show the menu for the
command. This command makes it possible to set position parameters for the
navigation reports, if a navigator is not available. Other possibilities are setting of the
complete NCS list, or to configure the reception filter of the EGC (Enhanced Group
Call) receiver part of the Transceiver.
The EGC filter is mainly a set of switches that control whether or not a particular EGC
message type will be received. Other possibilities are to specify a reception area for a
service (NAVAREA). The spare NAVAREA is used to point out an additional reception
area (e.g. on an expected course), as the default area is calculated by the Transceiver,
from the position that is entered with the set -p command or via a connected
navigational device.
The preferred ocean command specifies which ocean (None, Atlantic, Indian, Pacific or
Spare) to use as the default for the next login or scanning operation.
The complete set command option listing is obtained:
: set
-p (arg)
-o (arg)
-l (arg)
-c (arg)
-u (arg)
-r (arg)
-z (arg)
-m (arg)
-g (arg)
Command Reference
Legal arguments are :

Position and heading
Preferred ocean region
NCS table
Console parameters
Mobile number
Silent (remote)
Environment variables
Distress message
Distress Generator
114
SENDFILE

-q (arg)
-k (arg)
-e (arg)
-a (num)
-i (num)
-w (num)
-s (num)
-t (num)
-n (num)
-x (str)
-y (str)
-sp(arg)
-au(arg)
-sn(arg)
-ns(arg)
-fd(arg)
-am(arg)
-ame(arg)
-at(arg)
-atf(arg)
value
value
value
value
value
value
value
value
is
is
is
is
is
is
is
is
Distress test mode

Enable Land Mobile Alert
Receive only EGC messages
EGC: System Calls
EGC: FleetNet Calls
EGC: SafetyNet Calls
EGC: Spare Navarea no.
EGC: Wmo area no.
EGC: Navtex switch
EGC: Navtex coverage areas
EGC: Navtex services
Speed limits
Set authority levels
EGC: Set all 4 spare Navareas
Startup: NCS choice
Clear filesystem after startup
Set covert alert message addresses
Set covert alert message address extended prop..
Set covert alert message free text (from console)
Set covert alert message free text (from file)
1
1
0
0
0
0
8.28.2 SET -A _____________ ENABLE OR DISABLE RECEPTION OF INMARSAT SYSTEM CALL EGCS
Purpose: Enable or Disable Reception of Inmarsat System Call EGCs.
Format:
SE -a <0|1>
SE -a
0:
Disables reception
1:
Enables reception
Using the command without parameters displays the current setting

8.28.3 SET -AM ___________________________________________ SET SSA MESSAGE DESTINATIONS
[ver 2.11]
Purpose: Set the destination address for Covert/Security alert when using SSA
messages (see paragraph 6.1 ). There can be entered three individual
addresses numbered 0, 1, and 2. A minimum of system administrator
userlevel is required to see/change message destination setup.
Format:
SE -am <entry>,<type>[,<address>[,<param>]]
entry:
Address list entry number [0..2].
type:
Destination type.
255 = Unused
0 = TELEX
1 = PSTN
3 = PSDN
6 = Special access code
254 = e-mail
address: Destination address. This can be telephone numbers, telex numbers, or email addresses depending on the type.
param:
Command Reference
Supplementary parameter for some address types. For PSTN, T30 selects fax
and V22B selects modem; for special access code it may specify various
information required for a given code.
115
SET

The parameters for the command correspond largely to the parameters that
may be specified for the TX command (see paragraph 8.35 TX)
Examples
Set address 0 to fax number 12345678 in Denmark (country code 45):
SE -am 0,1,4512345678,T30
Set address 1 to e-mail:

SE -am 1,254,someone@somewhere.com
Clear address 2:
SE -am 2,255
View configuration:
SE -am
<CR><LF>
Update time: 2004-02-10 14:24:11<CR><LF>
Entry Type Param Address<CR><LF>
0
1
T30 4512345678<CR><LF>
1
254
someone@somewhere.com<CR><LF>
2
Address not used<CR><LF>
<CR><LF>
To set/clear addresses: se -am <Entry>,<Type>[,<Addresses>[,<Param>]]<CR><LF>
8.28.4 SET -AME ________________________________ SET EXTENDED SSA MESSAGE DESTINATIONS

[ver. 2.12]
Purpose: Set the extended properties for a message destination for Covert/Security
alert when using SSA messages (see paragraph 6.1 ).
For each of the three available addresses (see 8.28.3 ) the extended
property can be configured. It is thus possible to control which addresses
that will receive Covert/Security alert and which addresses that will receive
test messages. It is not permitted to disable the Covert/Security alert for the
two first message destinations.
Note, configuration change message will always be send regardless of this
configuration.
A minimum of system administrator userlevel is required to see/change
extended message destination setup.
Format:
SE -ame <entry>,<usage>
entry:
Address list entry number [0..2].
usage:
Usage:
0 = Reserved
1 = Message only
2 = Test only
3 = Both test and message.
Examples
Set the first message destination to be used for both Covert/Security alert and test
messages:
SE -ame 0,3
Set the second message destination to be used for Covert/Security alert only:
Command Reference
116
SET

SE -ame 1,1
Set the third message destination to be used for test messages only:
SE -ame 2,2
View configuration:
SEt -ame
<CR><LF>
Extended address configuration.
Entry Usage
0
Msg+Test
1
Msg
2
Test
To set address-usage: se -ame <Entry>,<Cfg>
8.28.5 SET -AP ____________________________________________ SET SSA MESSAGE REPEAT RATE

[ver 2.22]
Purpose: Set number of minutes between two covert alert messages if repeated.
Format:
SE -ap <value>
SE -ap
<value>: From 20 min. to 60 min.

Using the command without parameters displays the current setting.
8.28.6 SET -AR ____________________ RESET HIGH PRIORITY MESSAGE OR EGC LIGHT INDICATION
[ver 2.19 - 3026C]
Purpose: Reception of a high priority message and/or EGC for the 3026C type results
in a aural and visual indication from the attached 3042C. The aural indication
can be reset by activating the Reset/Test button - reset of the visual
indication can only be accomplished using the set -ar command
Format:
SE -ar
8.28.7 SET -AT ___________________________________________________ SET SSA MESSAGE TEXT

[ver 2.11]
Purpose: Set the supplementary text note on SSA messages (see paragraph 6.1 ). This
may be used to provide information such as ship name, radio call sign,
country of registration, etc.
message text.
Format:
SE -at <text>
text:
Text note of max. 64 characters.
Examples
Set the text note:
SE -at Ship name: THRANE
Command Reference
117
SET

View configuration:
SE -at<CR><LF>
Current text: Ship name: THRANE<CR><LF>
<CR><LF>
To change text: se -at <Text><CR><LF>
8.28.8 SET -ATF ________________________________________ SET SSA MESSAGE TEXT FROM FILE
[ver 2.12]
Purpose: Set the supplementary text note on SSA messages (see paragraph 6.1 ). This
may be used to provide information such as ship name, radio call sign,
country of registration, etc. The supplementary text note is extracted from a
file to support texts up to 200 characters - in contrast to the se -at (8.28.6 )
which only supports up to 64 characters. If file contains more than 200
characters, the length of the content is truncted before used as
supplementary text note.
File with the supplementary text note can either be created directly via. the
terminal (section 8.34 ) or downloaded via the RECVFILE command (section
8.24 ).
supplementary text note.
Format:
SE -atf <filename>
<filename>: Name of file where the supplementary text is

Examples
Set and View configuration
: tr suppltx.txt<CR><LF>
Supplementary text note: <CR><LF>
The content of this file is used as supplementary text note for covert/security
alert.<CR><LF>
Can also be used to provide information such as ship name, radio call sign,
country of registration, ect.
<CTRL><C>
: dir<CR><LF>
IOPORT
_EGCLOG
_TXLOG
_RXLOG
EGC
suppltx
TXT
001
txt
6 File(s)
75
41
292
533
3070
221
04-06-10 09:16
04-06-10 09:16
04-06-10 09:16
04-06-10 09:16
04-06-10 09:34
04-06-10 13:14
168144 bytes free
: se -atf suppltx.txt<CR><LF>
Filecontent truncated due to oversize (to 200 characters)
: set -atf<CR><LF>
Current text:
Supplementary text note:
The content of this file is used as supplementary text note for covert/security
alert.
Can also be used to provide information such as ship name, radio call sign,
country o
To change text: se -atf <filename>
Command Reference
118
SET

8.28.9 SET -ATX _______________________________________ SET SSA ADDITIONAL MESSAGE TEXT

[ver 2.22]
Purpose: Set the additional supplementary text note on SSA messages (see paragraph
6.1 ). This may be used to provide additional information - can be accessed
at normal userlevel contrary command "set -at" (see section 8.28.7 ) which
requires system administrator userlevel.
Format:
SE -atx <text>
text:
Text note of max. 64 characters.
Examples
Set the text note:
SE -atx "2006-06-28 12:30:09 55.47N 012.31E"
View configuration:
SE -atx<CR><LF>
Current additional text: 2006-06-28 12:30:09 55.47N 012.31E<CR><LF>
<CR><LF>
To change text: se -atx <Text><CR><LF>
8.28.10 SET -AU ___________________________________________________ SET AUTHORITY LEVELS

Purpose: Set the authority levels for the commands. User can change authority level
for commands, which are accessible for user. User cannot set an authority
level higher than users own.
Format:
SE -au <command>,<authoritylevel>
<command>: Any transceiver command. The reserved word "all" can be used to set
authority level for all commands.
<authoritylevel>: Authority level: 0-2, 0:normal user, 1:super user, 2: sysadm. The
reserved word "reset" can be used to set the authority level to the default
settings.
Examples
Set the authority level for the tx command to sysadm:
Set -au tx,2
Set the authority level for all commands to default:

Set -au all,reset
8.28.11 SET -B __________________________________________ REINITIALIZE SYSTEM PARAMETERS

[ver 2.22]
Purpose: Complete reset of configuration - essentially "a reset to factory default".
Note, some system specific values are not reset (system id's, frequency
correction offset, distributor password).
Use this feature with outmost caution: lost data cannot in any way be restored
Format:
Command Reference
SE -b 1,<value>
119
SET

<value>: Value is returned by transceiver when issuing command "se -b" (without
parameters) - used as part of a "are you sure" mechanism.
Examples
Configuration reset:
: se -b
Usage: SEt -b 1,49325
: se -b 1,49325
Rebooting ...
8.28.12 SET -C ____________________________________ SHOW OR SET SERIAL PORT PARAMETERS

Purpose: Show or set the Transceiver serial console port parameters: baudrate, parity,
databits, stopbits. New settings takes effect at once [2.12].
Format:
SE -c <options>
SE -c <baud rate>,<parity>,<data bits>,<stop bits>[,<packet
mode>][,handshake]
Baud rate: 0 (autodetect), 4800, 9600, 14400, 19200, 38400, 57600, 115200
Parity:
N, E, O
Data bits: 7, 8
Stop bits: 1, 2
Packet mode: Optional. If ,PACKET is added to the parameters the serial port goes
into the TBUS2 packet interface mode (see appendix E ) and only TBUS2
packets can be sent and returned on the serial port, no shell commands can
be entered. This mode is for operation with DTE equipment that supports the
TBUS2 packet interface. To put the serial port back in shell mode the
Transceiver power must be swithced off and on.
handshake: 0 or 1. Set the handshake method, 0 = no handshake, 1 = hardware
handshake. Software handshaking is not available.
Example
Set -c<CR>
<CR><LF>
Console-status
: 4800,N,8,1<CR><LF>
Software handshake : no <CR><LF>
The default serial communications parameters are:

4800 baud
No parity
8 databits
1 stopbit
8.28.13 SET -E ______________________________________________ RECEIVE ONLY EGC MESSAGES

THIS COMMAND HAS BEEN REMOVED FROM VERSION 2.15 AND FUTURE VERSION
-only displaying the current setting is possible. Output will be "0" (disabled).
Purpose: Set up the transceiver for only receiving EGC messages.
Command Reference
120
SET

8.28.14 SET -FD ____________________________________________________ FILESYSTEM CLEANUP

Purpose: Enables or disables filesystem cleanup when transceiver boots. [2.12]
Format:
SE -fd <options>
SE -fd Show current setting
SE -fd { 0 / 1 } (disable or enable)
When filesystem cleanup is enabled, all files on disk are removed when transceiver
boots. Note, the three files _EGCLOG, _TXLOG and _RXLOG are regenerated by
transceiver regardless of how the set -fd option is set.
8.28.15 SET -G _________________________________________________ SET UP ALERT GENERATOR
Purpose: Set up or show alert parameters.
Format:
SE -g <options>
SE -g <LES_ID>[,<LES_ID>,<...>],<nature of alert>,
<N or S>,<lat_deg>,<lat_min>,<lat_hun>,
<E or W>,<lon_deg>,<lon_min>,<lon_hun>,
<hour>,<minute>,<course>,<speed> <options>
se -g without any parameters causes the transceiver to display the current alert
generator set-up.
se -g with 14-17 parameters sets every manually adjustable parameter of the alert
generator. A description of each parameter follows below.
LES_ID:
1 to 4 LES IDs can be entered, although no more than one for each ocean
region. Alerting will be disabled in ocean regions where no LES IDs have
been entered.
Nature of Alert: One letter representing the nature of alert. Table 8.7 lists the possible
natures of alert and their respective letters.
Identifier
Land Mobile
Maritime
Unspecified
Unspecified
Ambulance
Explosion
Fire
Flooding
Police
Collision
Hijack
Grounding
Under attack/threat of attack
Listing
Dangerous cargo leak/spill
Sinking
Accident
Disabled and adrift
Vehicle breakdown
Abandoning ship
Severe weather
Require assistance
Piracy/armed attack
Table 8.7 Nature of Alert.
Position:
Command Reference
Is given in latitude hemisphere, latitude degrees, minutes, and hundredths

of minutes, longitude hemisphere, longitude degrees, minutes, and
hundredths of minutes. Instead of entering an actual position the default
values can be entered instead, causing the transceiver to use the most recent
121
SET

GPS position if available when sending the alert. The default values are
S,127,63,124,W,255,63,124.
Time:
This time, given in hours and minutes, should correspond to the manually
entered position. If the position was set to defaults, the value of the time
parameter is ignored and the time of the GPS position is used instead. Time
is entered in 24 hour format.
Course:
Course in degrees. Also ignored when using GPS position.
Speed:
If transceiver is a 3026L speed is in km/h. Else the speed is in knots. Also

ignored when using GPS position.
Example
Set up LESs for two ocean regions (131 and 231), nature of alert (hijack), position, time
(12:15), course (180), and speed (150 km/h):
se -g 131,231,g,n,55,53,0,e,12,14,0,12,15,180,150<CR>
For SSAS systems, this command will also set and apply to the distress generator for
Covert Security alert. However, it should be noted that manual setting of position,
course, and speed is deprecated if the system is not approved for use with a DTE.
Systems without DTE approval should use only GPS information. To set up user defined
LESs for Covert Security alerts, the se -m command may be used.
8.28.16 SET -I __________________________ ENABLE OR DISABLE RECEPTION OF FLEETNET EGCS
Purpose: Enable or Disable Reception of FleetNet EGCs.
Format:
SE -i <0|1>
SE -i
0:
Disables reception
1:
Enables reception

8.28.17 SET -K ________________________________ ENABLE OR DISABLE LAND MOBILE ALERTING
Purpose: Set up or show land mobile alert parameters.
Format:
SE -k <options>
SE -k <0|1>
Remark: This command replaces the environment variable MOBALERT used in TT3020C transceiver.
se -k without parameters displays the current status (enabled or disabled.se -k 1
enables land mobile alerting.
se -k 0 disables land mobile alerting.
For SSAS and Non-SOLAS with Distress systems, this command has no effect; Covert
Security alert cannot be disabled.
Command Reference
122
SET

Example
Enable land mobile alerting:
se -k 1<CR>
8.28.18 SET -L _________________________________________________ SETUP OR SHOW NCS LIST

Purpose: Setup or show NCS list.
Format:
SE -l
This command is obsolete and only preserved for backwards compatibility. Use NCS -l
Show NCS list instead.
8.28.19 SET -M ____________________________________________________________ SET UP ALERT
Purpose: Set up or show alert parameters.
Format:
SE -m <options>
SE -m <LES_ID>,<protocol>,<nature> <options>
SE -m <LES_ocean_r1>,<LES_ocean_r2>,
<LES_ocean_r3>, <LES_ocean_r4> <options>
SE -m ALL_OCEANS
se -m without parameters causes the transceiver to display the current alert set-up.
se -m with 3 parameters (LES_ID, protocol, and nature of alert) sets up the parameters
for Land Mobile and maritime alerts. Note that the protocol parameter is obsolete
(insert any digit) and is only retained for backward compatibility. LES_ID should be a
valid LES number. Note that any LES IDs from other ocean regions that have been set
previously will be removed from the Land Mobile alert setup. The Nature of Alert
should be a letter according to Table 8.7, on page 121.
se -m with 4 parameters (4 valid LES numbers for 4 different ocean regions) sets up
which LESs to send Land Mobile, Covert Security and maritime alerts to. The
transceiver will automatically select the LES corresponding to the current ocean region.
In case the user does not wish to set up a LES for every ocean region, zeroes can be
entered instead of one or more of the LES IDs. This form is preferred to configure the
LES configuration for user defined LESs for Covert/Security alert (see paragraph 6.1 ).
se -m followed by the text ALL_OCEANS will cause the transceiver to display all 4 LESs
set up for alerting.
Example
Set up one LES ID, 131, and set Nature of Alert to hijack (G):
se -m 131,0,g<CR>
Set up LES IDs for three ocean regions, but leave one ocean region empty (no Land
Mobile Alerts can be sent in that ocean region):
se -m 31,131,0,331<CR>
Command Reference
123
SET

8.28.20 SET -N _____________ ENABLE OR DISABLE RECEPTION OF COASTAL WARNING CALL EGCS
Purpose: Enable or disable reception of Coastal Warning Call EGCs (Navtex calls).
Format:
SE -n <0|1>
SE -n
0:
Disables reception
1:
Enables reception

8.28.21 SET -NS _____________ ENABLE OR DISABLE LOGIN ON THE NEAREST ALLOWED SATELLITE
Purpose: Enable or disable the login on the ocean region with the nearest satellite
when booting.
Format:
SE -ns
SE -ns <0|1>
0:
Use last used satellite
1:
Use nearest allowed satellite

8.28.22 SET -O_________________________________________________ PREFERRED OCEAN REGION
Purpose: Setup or show preferred or allowed ocean region, the current NCS and the
synchronisation status.
Format:
SE -o <options>
-o : Show preferred ocean region, the current NCS and the synchronisation
status.
-o , : Show preferred ocean region and the allowed ocean regions.
-o : <preferred_ocean_region>[,<allowed_ocean_regions>]
Set preferred ocean region.
preferred_ocean_region : one letter <W,E,P,I,N>

allowed_ocean_regions : one or more letter <W,E,P,I,N>
Allowed_ocean_regions are only effective when the transceiver performs a scan.
The ocean region possibilities are:
West Atlantic
East Atlantic
Pacific
Indian
None
In allowed ocean regions None really means all ocean regions. In order to display or
change the allowed ocean region settings, system administrator authority level is
required.
Command Reference
124
SET

Example
: se -o<CR>
<CR><LF>
Preferred ocean : None<CR><LF>
Current NCS
: <STX>144<ETX> <STX>East Atlantic<ETX><CR><LF>
Sync
: Yes<CR><LF>
: se -o ,pie<CR>
: se -o ,<CR>
Allowed ocean(s): East Atlantic, Pacific, Indian<CR><LF>
8.28.23 SET -P ________________________________ SHOW OR SET POSITION AND HEADING VALUES

Purpose: Show position and heading values. , or set a manual position for reception of
geographically addressed EGCs.
Format:
SE -p
SE -p <lat_deg>,<lat_min>,<lat_hun>,<N|S>,<lon_deg>,<lon_min>,
<lon_hun>,<E|W>, <course>,<speed>
lat_deg:
Latitude degrees (0-90)
lat_min:
Latitude minutes (0-59)
lat_hun:
Latitude hundredths of minutes (0-99)
N or S:
Latitude hemisphere
lon_deg: Longitude degrees (0-180)

lon_min: Longitude minutes (0-59)
lon_hun:
Longitude hundredths of minutes (0-99)
E or W:
Longitude hemisphere
course:
integer from 0 to 360 degrees
speed:
positive integer in knots (0-255)
Note
The manually entered position is only used for area EGC reception. If a GPS position is
available, it will always override the manual position. See the command FX Set Fixed
Positions in section 8.13.1 to enter extra manual positions.
Example
: se -p<CR><LF>
<CR><LF>
Position : <STX>55 47 64 N 012 31 38 E<ETX> at 13:43:16 UTC
<STX>Valid<ETX><CR><LF>
Course
: <STX>134<ETX> deg/true north<CR><LF>
Speed
: <STX>000<ETX> knots : 0000 kmph : 0000 mph<CR><LF>
<CR><LF>
8.28.24 SET -Q ______________________________________________________ DISTRESS TEST MODE

Purpose: Show, enable, or disable distress test mode [2.15]
Format:
Command Reference
SE -q <0/1> <options>
-q
Show Distress Test Mode.
-q 0
Distress Test Mode OFF. Distress functionality enabled.
-q 1
Distress Test Mode ON. Distress functionality disabled.
125
SET

The Distress Test Mode is used to allow test of distress buttons, wiring and remote
alarm box without sending distress. The se -q command is intended for implementation
of a Test Mode menu in a message terminal.
Test of the Distress Button in Distress Test Mode:
Press the Distress Button for at least 5 seconds until the Distress LED is flashing at high
frequency. Observe that the Transceiver reacts by flashing the Alarm LED when the
Distress Button has been activated.
8.28.25 SET -R ____________________________________________________________ SILENT MODE
Purpose: Show, enable, or disable silent mode
Format:
SE -r <options>
SE -r <1|0>
When the transceiver is in silent mode, which is the default, INFO messages will not be
displayed automatically. Instead they are stored in a log, which can be read using the
STATUS -l Show Status Report command.
SET -r without parameters prints out the current mode (silent or not silent). The
parameter "1" enables silent mode, while the parameter "0" disables silent mode.
8.28.26 SET -S _______________________________________________________ SET SPARE NAVAREA
Purpose: Set extra Navarea for reception of Navarea-addressed EGCs.
Format:
SE -s <navarea>
SE -s
navarea: Navarea number or 0 for no area.

In addition to the EGCs that would normally be received, EGCs addressed to the
navarea set with this command will also be received.
Note
The command SET -sn allows up to 4 extra Navareas to be set and displayed.
8.28.27 SET -SN ____________________________________________________ SET SPARE NAVAREAS
Purpose: Set up to 4 extra Navareas for reception of Navarea-addressed EGCs.
Format:
SE -sn <navarea>,[<navarea>,[<navarea>,[<navarea>]]]
SE -sn
navarea: Navarea number or 0 for no area.

In addition to the EGCs that would normally be received, EGCs addressed to the
navareas set with this command will also be received.
Command Reference
126
SET

Note
The command SET -sn allows up to 4 extra Navareas to be set and displayed.
8.28.28 SET -SP ____________________________________________________________ SPEED LIMITS
Purpose: Setup or show speed limits .
Format:
SE -sp <option>
SE -sp
Show setup.
SE -sp <SpeedLimit>,<Time>
Setup limits and time.
<SpeedLimit> Speed in km/h, [0..255].

<Time>Time in seconds [0..65535].
The setup will only have meanings, if the transceiver has been setup to send datareport on speed events (see 4.8 Speed Limit Event) or if an I/O pin is configured to
respond to these events (see 8.17.3 IO -oOutput-pin setup).
Example
: se -sp 80,120
<CR><LF>
: se -sp
<CR><LF>
Speed limit: 80 km/h for 120 seconds<CR><LF>
:
8.28.29 SET -U ________________________________________________________ MOBILE NUMBER

Purpose: Setup or show the Mobile Number.
Format:
SE -u <number> <options>
-u
Display the Mobile Number.
-u <number>
Set the Mobile Number in the Transceiver. The number must be in the range
of 400000000-499999999. The Transceiver will respond with an error if the
number is out of range otherwise the number will be stored in non-volatile
memory:
Examples
: set -u<CR>
<CR><LF>
Mobile number
: 492380049<CR><LF>
: set -u 1<CR>
Illegal Number!<CR><LF>
:
: set -u 492380021<CR>
The number will now be stored permanently<CR><LF>
:
: set -u ?<CR>
<CR><LF>
Mobile number
Enter new number
Command Reference
: 492380049<CR><LF>
>
127
SET

8.28.30 SET -W ______________________________ DISPLAY SAFETYNET EGC RECEPTION SETTING

Purpose: Display whether SafetyNet call reception is enabled or disabled.
Format:
SE -w
0:
Disabled
1:
Enabled
This setting depends on the transceiver type and cannot be changed. This command
only displays the current setting.
8.28.31 SET -X _____________________________________________ SET COASTAL WARNING AREAS
Purpose: Set Coastal Warning Areas (Navtex areas) for EGC reception.
Format:
SE -x <areas>
SE -x
areas:
List of letters representing the areas.

Example
: se -x abcdefg
: se -x
-x (str)
value is abcdefg
8.28.32 SET -Y _____________________________________________________ SET NAVTEX SERVICES

Purpose: Set Navtex Services for EGC reception.
Format:
SE -y <services>
SE -y
services: List of letters representing the services.

Example
: se -y abcdefg
: se -y
-y (str)
value is abcdefg
8.28.33 SET -Z _________________________________________________ ENVIRONMENT VARIABLES

Purpose: Set up or show environment variables.
IMPORTANT: Environment variables are only implemented for backward compatibility
reasons. Only the TZ (Time Zone) and PRNFILTER (disable log or status printing) is
stored and restored at power-on. Any other changes to environment variables are lost
and reset to default settings at power-on.
Command Reference
128
SET

Format:
SE -z <options>
SE -z Show all environment variables
SE -z <variable>=<value>
Set environment <variable> equal to <value>.
SE -z <variable>=
Delete environment <variable>
See also 1.5.1 Environment Variables.

The intention with this command is that old implementations can still read environment
variables without receiving error messages. Therefore a number of environment
variables are implemented with fixed values, which cannot be changed.
Example
: se -z<CR><LF>
<CR><LF>
1: POSFORMAT=PU<CR><LF>
2: PRINTER=NO<CR><LF>
3: PPAGING=NO<CR><LF>
4: PLINES=61<CR><LF>
5: FFEED=NO<CR><LF>
6: OCEANSHIFT=SIGNAL<CR><LF>
7: PCHARS=80<CR><LF>
8: PCUTLN=NO<CR><LF>
:
8.29 SLEEP
Purpose: Controls sleep mode operation.
See paragraph 2.4 Sleep Mode (Power Events), for detailed description.
Format:
SLeep <options>
8.29.1 SLEEP -C _______________________________________ DISABLES SLEEP MODE OPERATION

Purpose: Disables sleep mode operation.
Format:
SL -c
Example
Disable sleep mode:
: sl -c<CR>
<CR><LF>
: sl -d<CR>
<CR><LF>
Sleep mode not enabled<CR><LF>
:
Command Reference
129
Sleep

8.29.2 SLEEP -D ______________________________________________ SHOW SLEEP MODE STATUS

Purpose: Show sleep mode status.
Format:
SL -d
8.29.3 SLEEP -F _______________________________________ SETUP SLEEP MODE REPORT FILTER

Purpose: Enables or Disables filtering of sleep mode reports. [2.14]
Format:
Enable:
SL -f <enable>,<distance>
0 = Sleep mode reports will not be filtered
1 = Sleep mode reports will be filtered.
Distance: Maximum distance from the enter sleep mode position before the filtering
is forced off thus permitting sleep mode reports to be sent. Values are
entered in 10 meter steps, eg. 100 means 1 km.
Filtering (i.e., removal) of sleep mode reports applies to In Sleep and Fix Time reports.
See section 4.6 for more information on sleep mode reports.
Note that the filter will be disabled when sufficient movement has been detected thus
allowing sleep mode reports to be sent; if the filter is required to be re-enabled at a
later time this can be done either be issuing this command again, or be using an I/O pin
programmed as input. See section 8.17.2 for more information on this topic.
8.29.4 SLEEP -I __________________________________________ SETUP SLEEP MODE OPERATION
Purpose: Setup sleep mode operation.
Format:
SL -i <T1>,<HH>,<MM>,<T2>,<FC>
T1:
Duration in hours the transceiver sleeps between wake ups. If T1=0, then
there are no periodic wake ups defined.
HH:
Hour of fixed time wake-up in UTC time (0-23)
MM:
Minute of fixed time wake-up in UTC time (0-59)
T2:
Duration of fixed time wake-up in minutes (0, 15-60)
FC:
Number of fixed time wake-ups in 24 hour (1,2,3,4,6,8,12). This parameter is

optional. If it is omitted, there will be one wake-up occurring the given time.
[ver. 2.13]
If T1, HH, MM, and T2 are all zero then there will be no wake-up (neither fixed time nor
sleep mode based) after the transceiver is powered down.
If more than one fixed time wake-up is requested (FC > 1) these wake-up times will be
distributed evenly over a 24-hour period.
Example
Enable sleep mode:
: sl -i 5,23,0,30,3<CR>
<CR><LF>
: sl -d<CR>
<CR><LF>
Next Wake Up:
04-07-08 14:27<CR><LF>
Wake Up Interval: 5 Hours<CR><LF>
Next Fix Time:
04-07-08 23:00 (3 fix times per 24 hours) <CR><LF>
Command Reference
130
Sleep

Duration:
<CR><LF>
: <CR><LF>
30 minutes<CR><LF>
This example sets three fixed time wake-ups at 23:00, 07:00, and 15:00 (11 PM, 7 AM,
and 3 PM).
8.29.5 SLEEP -L __________________________________ SETUP AUTO-LOGOUT BEFORE SLEEP MODE
Purpose: Enables or Disables automatic logout before power down for sleep mode
without wakeup. [ver. 2.12]
Format:
SL -l [0|1|?]
8.30 STATUS
8.30.1 STATUS ____________________________________________ DISPLAY TRANSCEIVER STATUS
Purpose: Display Inmarsat-C related information that the user can not directly change.
Format:
STatus <options>
The status command displays various Inmarsat-C system parameters. The only
parameters that can be changed with this command are the enable and disable status of
the ENID and DNID's.
The command without any parameters will display all the options:
: st <CR><LF>
<CR><LF>
-a (arg)
-c (arg)
-d (arg)
-e (arg)
-g (arg)
-i (arg)
-l (arg)
-m (arg)
-n (arg)
-q (arg)
-r (arg)
-s (arg)
-o (arg)
-t (arg)
-w (arg)
-v (arg)
Legal arguments are :<CR><LF>

Latest distress<CR><LF>
Channel<CR><LF>
DNID table<CR><LF>
EGC log<CR><LF>
EGC FleetNet ID's<CR><LF>
Identification<CR><LF>
Last command(s)<CR><LF>
Latest test result (P)<CR><LF>
LES Network table<CR><LF>
Queued command(s)<CR><LF>
RX log<CR><LF>
Signal strength<CR><LF>
Power-on statistics (P)<CR><LF>
TX log<CR><LF>
Hardware screen (P) (F)<CR><LF>
Program version<CR><CR><LF>
8.30.2 STATUS -A _______________________________________________ STATUS OF LATEST ALERT

Purpose: Show the latest distress status and clear any audible and visual alert
indications.
Format:
ST -a
The possibilities are:
None (No distress has been sent since power on)
Sending (Transceiver is sending a distress)
Accepted (Transceiver has sent a distress and it has been acknowledged by LES)
Command Reference
131
Status

Rejected (Transceiver has sent a distress and it has been rejected by LES
Example
st -a<CR>
<STX><CR><LF>
Latest Distress
: none<ETX><STX><CR><LF>
Latest Distress test : none<ETX><CR><LF>
8.30.3 STATUS -C _______________________________________________ CHANNEL PARAMETERS

Purpose: Show the current channel parameters: synchronisation, login status, TDM
type, TDM channel number, current channel, current protocol activity, TDM
origin, TDM frame number, Bulletin Board error rate and time of last login or
logout.
Format:
Example
ST -c
: st -c<CR>
<CR><LF>
<CR><LF>
SOFTWARE:
Version 1.0 Oct 16 2001 09:23:04, Inmarsat-C Transceiver <CR><LF>
Synchronization
: yes
Serial no
: 906407<CR><LF>
Logged in
: yes
Mobile no
: 492380049<CR><LF>
TDM type
: NCS
Preferred ocean: None <CR><LF>
TDM channel number : 12580<CR><LF>
Current channel
: NCS<CR><LF>
Current protocol
: Free<CR><LF>
TDM origin
: 144<CR><LF>
TDM frame number
: 5449<CR><LF>
BB error rate
:
2 of 100<CR><LF>
Last login at Fri Oct 12 11:50:43 2001<CR><LF>
<CR><LF>
:
Synchronization
Yes | No
Serial no
6 digit number
Logged in
Yes | No
Mobile no
9 digit number
TDM type
NCS | LES | Joint NCS | Standby NCS | -
Preferred ocean
West Atlantic | East Atlantic | Pacific | Indian |

None
TDM channel
6000-14000
number
Current channel
NCS | LES | Signalling | Message | Retuning | -
Current protocol
Free | Pending | Sending Distress | Sending

Distress test | Confirmation request | Login | Logout
| Changing NCS | Scanning | Link Test |
Transmission | Receiving message | Position report
| Data report | Programmed report
TDM origin
1-63 | 101-163 | 201-263 | 301-363
TDM frame number
0-9999
BB error rate
0-100
Last login/logout at
Date string
Table 8.8 Channel Parameter Field Values
Command Reference
132
Status

8.30.4 STATUS -D _________________________________________________ DNID INFORMATION

Purpose: Display the stored DNID information.
Format:
ST -d <add options>
The term DNID entry refers to the union of the four elements: LES ID, DNID, Member
Number and Sub-address. The command displays a line of information for each DNID
entry.
All four elements is downloaded to the Transceiver via the link and except for the Sub
Address the user is not able to alter any of them.
Via the da data report command set-up command the user is able to select an
alternative sub-address when responding to a poll.
The items in Table 8.9 will currently be displayed.
Provider Name
Describes the service provider. The Transceiver

stores this in a compressed format internally with
maximally 24 characters length.
Status
A bit field describing the current use of the DNID

entry. Several bits may be combined into one status
code number.
LES
Land Earth Station ID.
DNID
Data Network ID.
Member
Member Number in the DNID group.
Sub Address
Logical address of a unit attached to the Transceiver.
Channel
TDM channel number to use for reporting.
Randomising
A timing interval used by the Transceiver to spread

out a group response to a poll.
Table 8.9 DNID Item List
When using the position data reporting facility use the rs command to set the status of
the DNID entries of interest to position data report status (rs -f 2).
When the use of a particular DNID entry is not needed any more its status should be set
to disabled as this will indicate to the Transceiver that the particular DNID can be
overwritten if a new DNID is downloaded, in case the DNID storage is full.
A DNID entry is disabled by putting the letter D in front of the DNID entry when sending
the st -d command. This will also remove any position reporting indication for this DNID
entry.
The Transceiver currently has capacity for 64 DNID entries.
When a new DNID is downloaded it will automatically be set Active and in use for data
reporting as this will prevent the entry from being overwritten by a subsequent
download.
Example
st -d
Provider Name
S LES DNID
Thrane & Thrane USR Group: 5 131 17734
Mem Sub Chan Rd

37
0 11096 48
A colon always separates the provider name (always 25 characters) from the other
information.
Command Reference
133
Status

8.30.5 STATUS -E _______________________________________________________ SHOW EGC LOG

Purpose: Show the Enhanced Group Calls (EGC) log.
Format:
ST -e
Table of EGC Log Columns and Terms

LES
Land Earth Station number.
Sv
Service number. Hexadecimal:

00H General Call
02H Group Call
04H Urgency Message, Nav Warning to Rectangular Area
11H INMARSAT System Message
13H Coastal Warning
14H Distress Alert to Circular area
23H EGC System Message
24H Urgency Message, Nav Warning to Circular Area
31H MET Navarea Warning or MET Forecast
33H Download Group Identity (ENID)
34H SAR Coordination to Rectangular area
44H SAR Coordination to Circular area
72H Chart Correction Service
73H Chart Correction Service for fixed areas
Priority number:
0 Routine
1 Safety
2 Urgency
3 Distress
Language (presentation).
0 Int. Alphabet no. 5, odd parity
6 ITA 2, packed baudot
7 Data
Time
Local time of reception. (DD-MM-YY HH:MM).
Bytes
Number of characters in the message.
Mess.no
Message reference number. Given by the LES.
LES message repetition number.
Status
Message destination. As for receive log.
File
Received file. Name begins with the letters "EGC."

followed by a sequential three digit number.
Table 8.10 EGC Log Terms
Example
: st -e
EGC log at 02-12-12 12:48:45
LES Sv P L
Time
Bytes Mess.no Errors R Status File
---------------------------------------------------------------012 31 1 0 02-12-02 10:38
246
109
0 0 Mem
EGC.288
012 31 0 0 02-12-02 10:39
328
108
0 0 Mem
EGC.289
012 31 2 0 02-12-02 10:39
164
110
0 0 Mem
EGC.290
012 00 0 0 02-12-02 11:08
21
24
0 0 Mem
EGC.291
012 11 0 0 02-12-02 11:08
21
25
0 0 Mem
EGC.292
012 14 0 0 02-12-02 11:20
21
38
0 0 Mem
EGC.293
012 04 0 0 02-12-02 11:34
21
46
0 0 Mem
EGC.294
012 33 0 0 02-12-02 12:49
47
106
1 0 Mem
EGC.301
012 33 0 0 02-12-02 12:54
47
106
0 0 Mem
EGC.302
9 Entries listed
:
Command Reference
134
Status

8.30.6 STATUS -G _________________________________________________ ENID INFORMATION

Purpose: Display or configure ENID information.
Format:
ST -g <d/e><enid> <options>
-g
Show the list of stored ENIDs (EGC Network ID)'s.
-g e<enid> Enable reception for the ENID.

-g d<ENID>Disable reception for the ENID.
The ENID list contains the items shown in Table 8.11.
Provider
Describes the service provider. The Transceiver stores
Name
this in a compressed format internally with maximally 24

characters length.
ENID
EGC Network ID
Status
ENID status: Enabled or disabled. Only if disabled the

status is printed.
Table 8.11 ENID Item List
Example
st -g<CR>
<CR><LF>
<CR><LF>
EGC Network ID list<CR><LF>
<STX>131,t&t egc user gr
5 ENID(s) stored<CR><LF>
<ETX>
<ETX>
<ETX>
<ETX>
<ETX>
<STX>
<STX>
<STX>
<STX>
<STX>
100<ETX><CR><LF>
101<ETX><CR><LF>
102<ETX><CR><LF>
103<ETX> disabled<CR><LF>
104<ETX><CR><LF>
ENIDs are downloaded via the Inmarsat-C Network automatically, and are used for
various automatic messaging protocols.
When the EGC facility is used in the transceiver the status of the downloaded ENID's
can be displayed and changed.
The ENID's are downloaded to the transceiver by an individual addressed EGC
message (to mobile number of the transceiver). When a particular ENID is stored and
enabled any EGC message addressed to this ENID will be received. If the ENID is
disabled the transceiver will ignore these messages.
Example
Enabling and disabling an ENID
st -g e101
st -g d103
A disabled ENID can be overwritten by new ENID download if the ENID storage is full.
24 ENIDs can be stored in the transceiver.
Command Reference
135
Status

8.30.7 STATUS -I ____________________________________ SHOW TRANSCEIVER IDENTIFICATION

Purpose: Show transceiver identification: serial number, type and mobile number.
Format:
Example
ST -i
: st -i<CR><LF>
<CR><LF>
Serial number :
Terminal type :
Mobile number :
Mobile type
:
:
<STX>0890254<ETX><CR><LF>
<STX>Inmarsat-C Transceiver<ETX><CR><LF>
<STX>492380345<ETX><CR><LF>
<STX>Non-SOLAS Maritime<ETX><CR><LF>
8.30.8 STATUS -L __________________________________________________ SHOW STATUS REPORT

Purpose: Show status reports from the last commands. These are described in chapter
9
Info.
Format:
ST -l
Example
An example from a longer session:
st -l<CR>
<CR><LF>
INFO
82: Transmission issued OUT.646 and put in queue<CR><LF>
ERROR 253: No printer. Fetch file: REPORT.001 named OUT.646<CR><LF>
INFO
52: Changing NCS issued and put in queue<CR><LF>
INFO
41: Logout successful<CR><LF>
INFO
31: Login successful<CR><LF>
INFO
51: Changing NCS successful<CR><LF>
INFO
80: Transmission failed.<CR><LF>
<CR><LF>
Destination <STX>581482380010 File OUT.646<ETX><CR><LF>
Vital earth station information is missing<CR><LF>
ERROR 253: No printer. Fetch file: REPORT.004 named REPORT.<CR><LF>
8.30.9 STATUS -M ______________________________________________ SHOW LAST TEST RESULT

Purpose: Show the results of the last test preformed using the command TEST.
Format:
ST -m
8.30.10 STATUS -N ___________________________________________ SHOW LES NETWORK TABLE

Purpose: Show land station network table entry by entry from a shown list.
Format:
ST -n <options>
-n
Show all LESs supporting Mini-C MES traffic
-n A
Show all LESs
The LES network table is (apart from the NCS table) downloaded from the current NCS
when loging in for the first time.
The version number that the transceiver send with the login request, assures that the
transceiver will always have the latest table, as the NCS will download the newest
version number, if an older is stored in the Transceiver.
Command Reference
136
Status

The command lists the status of the LES and the services available at the LES. The
services are listed with one service on each line and the maximum number of services
are 16.
Example
: st -n<CR><LF>
<CR><LF>
Land Station Network version number: 39<CR><LF>
Total number of LES: 5<CR><LF>
Choose a LES id from this list<STX><CR><LF>
102 104 112 114 121<ETX><CR><LF>
> 102<CR><LF>
<CR><LF>
LES id <STX>102<ETX> at Frequency 11846<CR><LF>
Status :<STX><CR><LF>
600 bps return link<CR><LF>
Operational satellite<CR><LF>
In service<CR><LF>
Clear at the moment<CR><LF>
Open terrestrial links<ETX><CR><LF>
Service :<STX><CR><LF>
FleetNet traffic<CR><LF>
Closed network traffic<CR><LF>
Telex S&F traffic<CR><LF>
Inmarsat-C traffic<CR><LF>
SafetyNet traffic<CR><LF>
Maritime Distress traffic<CR><LF>
Mini-C MES traffic<CR><LF>
8 Bit (Data) traffic<CR><LF>
5 Bit (ITA-2) traffic<CR><LF>
Aero-C traffic<CR><LF>
Land mobile alerting traffic<ETX><CR><LF>
Choose a LES id from this list<STX><CR><LF>
102 104 112 114 121<ETX><CR><LF>
> <CR><LF>
:
Enter is used to quit.
Possible information, row by row:

300 | 600
Operational | Spare
In service | out of service except for alarms
Clear | Congested
Open | Closed
<variable number of service lines, max 16>
list of integer numbers (max. 80)
8.30.11 STATUS -O ________________________________________________ POWER ON STATISTICS
Purpose: Show the power-on statistics of the Transceiver.
Format:
ST -o [E]
The result of the command is a list of the last 5 power-ons indicating the time the
transceiver was turned on and the length of time it remained on. The duration is shown
with an accuracy of one hour.
Command Reference
137
Status

Example
: st -o<CR><LF>
<CR><LF>
Power-on statistics:<CR><LF>
--------------------<CR><LF>
At 01-12-06 18:32 for 0 hours<CR><LF>
At 01-12-07 08:49 for 72 hours<CR><LF>
At 01-12-10 08:59 for 0 hours<CR><LF>
At 01-12-10 09:05 for 0 hours<CR><LF>
At 01-12-10 14:22 for 64 hours<CR><LF>
Using power on statistics with option 'E' (st -o E), extends the statistics to 15 entries and
detailed information;
Power on time and reasons (Wakeup or Remote Power On)
Duration of Power on time
Power off reason (watchdog reset, Remote Power Off)
Example
: st -o E<CR><LF>
<CR><LF>
System power up time: <STX>Fri May 31 07:42:12 2002<ETX><CR><LF>
<CR><LF>
Power-on statistics:<CR><LF>
--------------------<CR><LF>
At 02-05-27 20:29:44 for 0:0:17 hours (02-05-27 20:30:01), Reason:0x21><CR><LF>
:
The table below, explains the reasons hex-codes.

Code
Command Reference
Reason text
01H
Remote Power Off
02H
Watchdog reset
03H
Exception
04H
Main Power Lost/Removed
08H
Forced reset
10H
Remote Power On
20H
Interval WakeUp
40H
Fixed Time WakeUp
138
Status

Table 8.12, Power on statistics reasons.
8.30.12 STATUS -Q _________________________________ SHOW CONTENTS OF COMMAND QUEUE

Purpose: Show contents of command queue.
Format:
Example
ST -q
: st -q<CR><LF>
<CR><LF>
Current activity : Scanning<CR><LF>
Activities in queue<CR><LF>
1 : Transmit message 2 : Transmit message
:
3 : Logout<CR><LF>
The information is the same as seen in the 5th row of the st -c information.
8.30.13 STATUS -R _________________________________________________________ RECEIVE LOG
Purpose: Show receive log.
Format:
Example
ST -r
st -r<CR><LF>
<CR><LF>
RX log at 01-10-25 10:33<CR><LF>
LES Sv P L
Time
Bytes Mess.no S Status
File<CR><LF>
-----------------------------------------------------------<CR><LF>
131 0 0 0 01-10-24 16:28
120 102425
0 Mem
IN.203<CR><LF>
131 0 0 0 01-10-24 19:15
120 102461
0 Mem
IN.204<CR><LF>
131 0 0 0 01-10-24 21:23
120 102485
0 Mem
IN.205<CR><LF>
131 0 0 0 01-10-24 21:55
120 102508
0 Mem
IN.206<CR><LF>
131 0 0 0 01-10-24 22:11
120 102515
0 Mem
IN.207<CR><LF>
131 0 0 0 01-10-25 00:23
120 102524
0 Mem
IN.208<CR><LF>
131 0 0 0 01-10-25 00:37
120 102546
0 Mem
IN.209<CR><LF>
7 Entries listed<CR><LF>
Explanation of the columns are given in Table 8.13.
Command Reference
139
Status

LES
Sv
Service number. Hexadecimal
value.
0
Store-and-forward.
Half duplex data.
Data. Bit transparent. No ARQ.
Data. With ARQ.
Pre-assigned data reporting.
5-D
Spare.
Performance verification message.
Reserved.
Routine.
Spare.
Priority number.
Spare.
Distress.
Int. Alphabet no. 5, odd parity
ITA-2. Packed baudot.
Data.
Mem
Memory (or disk).
Language (presentation).
Time
Local time of reception: DD-
Bytes
Number of characters in the
MM-YY HH:MM.
message.
Mess.
Message reference number.
no
Given by the LES.
Sub-address. Local routing at

the Transceiver.
Status
Message destination.
File
Name of received file. Begins

with the letters "IN." followed
by a sequential three digit
number.
Table 8.13 Receive Log Description
If a message reception fails, no information about it is stored in the receive log.

8.30.14 STATUS -S _______________________________________________ SHOW SIGNAL STRENGTH
Purpose: Show signal strength : number from 0 to 5.
Format:
Example
Command Reference
ST -s
st -s<CR>
<CR><LF>
Signal strength : <STX>5<ETX><CR><LF>
140
Status

8.30.15 STATUS -T _______________________________________________________ TRANSMIT LOG

Purpose: Show the transmit log.
Format:
Example
ST -t
st -t<CR>
<CR><LF>
TX log at 01-10-25 10:52<CR><LF>
LES Sv P L
Time
Bytes Destination
MTCA Status File/Ref<CR><LF>
----------------------------------------------------------------------<CR><LF>
131 0 1 0 01-10-25 09:02
67 581482380120
0000 Acknowl 107352<CR><LF>
131 0 1 0 01-10-25 09:13
67 581482380120
0000 Acknowl 107364<CR><LF>
131 0 1 0 01-10-25 09:14
463 581482380010
0010 Failed 107373<CR><LF>
131 0 1 0 01-10-25 09:14
463 581482380120
0010 Cleared OUT.267<CR><LF>
131 0 1 0 01-10-25 09:29
463 581482380120
0010 ConReq 107385<CR><LF>
131 0 1 0 01-10-25 09:20
463 581482380010
0010 Cleared OUT.268<CR><LF>
131 0 1 0 01-10-25 09:36
361 581482380010
0010 Sending OUT.269<CR><LF>
7 Entries listed<CR><LF>
Explanation of the columns is given in Table 8.14
Command Reference
141
Status

LES
Sv
Service number.
Hexadecimal. See above (st r command).

P
L
Priority number.
Immediate delivery
Deferred delivery
Telex
PSTN
Language (presentation). See

above (st -r command).
Time
Local time of reception. (DDMM-YY HH:MM).
Bytes
Number of characters in the

message.
Destin
Number of the called party.
.
M
Multi addressed message

number. 0 are single addr.
0 is the primary receiver, 1 is
the secondary etc.
C
A
Status
File /
Destination network type.
Confirmation request.
Alarm (SOS) message.
CSDN
PSDN
Closed network.
Special access code.
Other.
Not requested.
Requested.
Normal message type.
Alarm message type.
Current status of the
Waiting
is waiting to be sent.
message.
Sending
is being sent or are in queue.
Name of received file.
Acknowl
has been accepted by the LES.
ConReq
as above + confirmation is requested.
Deliver
has been successfully delivered
Pending
is held pending by the LES.
Reject
has been rejected by the LES.
Cleared
has been cancelled or transmission has failed.
Failed
delivery has failed.
NotDelv
message is not yet delivered.
NoInfo
LES has no info of this message.
File
Ref
Name of transmitted file. Begins with the letters

"OUT." followed by a sequential three digit
number.
Ref
message reference number (from the LES) in

case of a successful transmission.
Table 8.14 Transmission Log Description
Command Reference
142
Status

8.30.16 STATUS -V ______________________________________ SHOW SOFTWARE VERSION NUMBER

Purpose: Show software copyright notice and version number.
Format:
Example
ST -v
: st -v<CR><LF>
<LF>
<LF>
<LF>
<LF>
<LF>
Non-SOLAS Maritime Inmarsat-C Transceiver, Tr Version 3.00<CR><LF>
(C) Copyright 2001 Thrane & Thrane A/S<CR><LF>
Version 1.0 Oct 16 2001 09:23:04<CR><LF>
<CR><LF>
:
8.30.17 STATUS -W ____________________________________________ HARDWARE STATUS SCREEN

Purpose: Show hardware status screen
Format:
ST -w
Example
This is an example of the information:
: st -w<CR><LF>
<CR><LF>
<STX><CR><LF>
HARDWARE: System Clock 2004-11-18 09:36
PCB 0-00000000-0000<CR><LF>
LO Vtune
OSC offset/Acc/PllF
RX/TX/AGC
B/S/CNo<CR><LF>
0mV
-137Hz
0mA
1<CR><LF>
.
-139Hz
0mA
5<CR><LF>
.
-21Hz
99
43dBHz<CR><LF>
<CR><LF>
SOFTWARE:
Version 2.14 Nov 1 2004 18:20:53, Inmarsat-C Transceiver<CR><LF>
<CR><LF>
Synchronization
: yes
Serial no
: 906405<CR><LF>
Logged in
: yes
Mobile no
: 0<CR><LF>
TDM type
: NCS
Preferred ocean : None <CR><LF>
TDM channel number : 11080
<CR><LF>
Current channel
: NCS
<CR><LF>
Current protocol
: Free
<CR><LF>
TDM origin
: 44
<CR><LF>
TDM frame number
: 3999
<CR><LF>
BB error rate
:
0 of 100
<ETX><CR><LF>
:
Table 8.15 gives a description of the fields in the hardware status screen. For backward
compatibility reasons, some of the values are always displayed with value zero.
A description of the other fields can be found in Table 8.8.
Command Reference
143
Status

Field
Normal values
OSC
Description
<25 kHz
Offset to actual carrier. The value is likely to rise
Acc
<25 kHz
Offset to actual carrier do to aging.
PllF
<100 Hx
Measured offset to current channel carrier
AGC
20 - 255
offset
with temperature and as the transceiver ages.
Signal gain. The values listed are maximum and

minimum values respectively. In normal operating
conditions, the value will be around the middle of
this range.
CNo
>28 dbHz
Carrier to noise ratio. A lower value indicates no

signal or bad signal.
RX, LO Vtune, and TX are always displayed with value zero, for backward
comparability reasons.
Table 8.15 Hardware Status Screen Description
8.31 SU
8.31.1 SU _____________________________________________________________ SUBSTITUTE USER
Purpose: Substitute user identity.
Format:
SU <username>
Prompts: Enter password:

This command change the effective user id to that of <username>, if the correct
password is entered.
Username can be one of the 3 built in user accounts.
Level
Username
Default
password
sysadm
sysadm
super
super
normal
(no password)
Table 8.16 Built in users and default passwords.
Some of the TT3026L/M configuration commands require a specific user id level.

Commands not in the table below only require normal user id/level.
Command Reference
144
SU

Command
Required
and option
minimum user
Comment
id / level
sysadm
super
normal
EV
ID
CA
CFG
DE
System files requires sysadm
FI
Fishery Configuration
DIAG
IO
PG
Programs created remotely

requires sysadm
SE
-o
Allowed oceans requires

sysadm
-c
-f
ZOne
LOG
Control data-logging
Table 8.17 Overview of required user id / level of commands
8.32 TEST
8.32.1 TEST ________________________________________________________________ LINK TEST
Purpose: Issues a link test request.
Format:
TEst <options>
A link test is an automatic test procedure which tests message reception, message
transmission and alert transmission.
8.33 TIME
8.33.1 TI _________________________________________________________ SHOW PRESENT TIME
Purpose: Display or set the system clock.
Format:
TIme <options>
TI -u Show UTC time
TI -g Show GMT time (same as utc-time)
TI -l Show local time
TI -? Request Help
The command will show the present time: local time if the TZ configuration parameter is
set, UTC if not. This command gives the following possibilities:
Command Reference
145
Test

When a GPS position is available, the time shown by this command will be the current
time obtained from the GPS satellites.
The Transceiver will automatically adjust its RTC (Real Time Clock) hardware
continually, so that the transceiver's time will be accurate between power-ons. An INFO
463 message is received when this happens.
TZ configuration variable
TZ is the environment variable used for setting the time zone.
Use the following syntax to set the TZ environment variable:
set -z TZ=tzn[+ | -]hh[:mm]
The tzn is a three-letter time-zone name, such as UTC, followed by an optionally

signed number, +/- hh, giving the difference in hours between UCT and local time. To
specify the exact local time, the hours can be followed by minutes.
The time-zone name has no effect to the functionality of the TZ setting and i.e. can be
any three-letter name.
Example
se -z TZ=UTC-2:0
8.33.2 TI -L _________________________________________________________ SHOW LOCAL TIME

Purpose: Display local time.
Format:
Example
TI -l
ti -l<CR>
<CR><LF>
01-10-22 12:35:00<CR><LF>
:
8.33.3 TI -S _________________________________________________________________ SET TIME

Purpose: Set UTC time.
Please notice that the UTC time is adjusted frequently, whenever the GPS
delivers a valid time.
Format:
Example
TI <yyyy-mm-dd> <hh:mm>
ti 01-10-22
:
10:35:00<CR><LF>
8.33.4 TI -U ___________________________________________________________ SHOW UTC TIME

Purpose: Display UTC time.
Format:
Example
Command Reference
TI -u
ti -u<CR>
<CR><LF>
01-10-22 10:35:00<CR><LF>
146
Time

8.34 TRANSFER
8.34.1 TRANSFER _______________________________________ TRANSFER FILE FROM CONSOLE
Purpose: Make a new file with data from the console input.
Format:
TRansfer <filename>
The command will input a file from the console and stop after a 5-second time-out. The
transfer will then be in text mode, which means that a LF character on the console input
is converted to a CR+LF pair in the file.
The Transceiver should be allowed at least 20 ms to switch from text mode (command
line) to binary mode (the input data).
8.34.2 TRANSFER -B _____________________________________ TRANSFER IN BINARY NOTATION
Purpose: The file is transferred binary.
Format:
TR <filename> -b <byte_count>
All characters from 00H to FFH can be used. The number <byte_count> must match the
actual number of characters transferred. If <byte_count> is larger than the number of
characters sent, the command will time-out after 5 seconds.
8.35 TX
8.35.1 TX _______________________________________________________ TRANSMIT A MESSAGE
Purpose: Transmit a message file.
Format:
TX <filename> <options>
TX -c <LES ID> <filename> [-s <delivery service>] [-t <destination network>]

[-l <Language>] [-e <destination extension>] [-h <hour>:<minutes>] [-k]
[-y <YY-MM-DD>] [-v] [-a]
This command initiates a transmission. If no options are given, the default transmission
parameters are shown. In the telex service case the file must contain a destination as
the first line (using the CCITT U.80 recommendation). The same message can be sent to
several destinations by adding more address lines in the beginning of the file.
If only the filename and LES ID are specified in the command lime, the default
parameter values will be used as default.
If the LES is busy it can either reject the call attempt or give it Pending status. If
pending status is given to the Transceiver, it will show this in the 'Current protocol' field
of the st -c command. When pending the Transceiver will not service any other
transmission commands from the user. The LES will automatically call up the
Transceiver when it has spare capacity.
Command Reference
147
Transfer

8.35.2 TX -A ________________________________________________ SEND WITH DISTRESS PRIORITY

Purpose: Transmits a message with distress priority. [2.15]
Format:
TX <filename> -a <options>
This option is only available in TT-3026D and the TT-3000E mini-C GMDSS System.
8.35.3 TX -C ________________________________________ SPECIFY LES TO ROUTE THE MESSAGE
Purpose: Specifies which LES to route the message.
Format:
TX <filename> -c <LES ID>
<LES ID> is an integer from in the ranges 1-63, 100-163, 200-263 or 300-363.
8.35.4 TX -E _______________________________ ADDITIONAL RECEIVER ADDRESS INFORMATION
Purpose: Specifies additional receiver information
Format:
TX <filename> -e <destination extension>
The destination extension is a string describing additional information for the PSTN
destination type specifying the modem protocol, the code for the Special Access Code
destination or the DNID and Member Number for Transmissions to Closed Networks.
When the destination network type is PSTN (-t 1) the destination extensions holds:
"V22B" selects a telephone modem.
"T30" selects a FAX modem.
This is not used by the Transceiver, but at the LES to choose the correct modem
protocol type.
When the destination network type is closed network (-t 5) the destination extensions
holds the DNID. Specify the DNID and Member Number as: DNID,Member. Destination
address may be ommited in the file.
When the destination network type is Special access code (-t 6) the destination
extensions holds a string of up to 6 letters. Destination address may be omitted in the
file.
8.35.5 TX -H _______________________________________________________ TRANSMISSION TIME
Purpose: Transmission time.
Format:
TX <filename> -h <hour:minutes> <options>
Must be entered in 24 hour format. If specified without parameters current time is

displayed after execution. [ver 2.12]
Command Reference
148
TX

8.35.6 TX -K ________________________________________ KEEP MESSAGE AFTER TRANSMISSION

Purpose: Keep the message after transmission.
Format:
TX <filename> -k <options>
8.35.7 TX -L ___________________________________ SET PRESENTATION AT THE RECEIVING END

Purpose: An integer specifying the presentation at the receiving end.
Format:
TX <filename> -l <language>
0
Int. Alphabet no. 5, odd parity
ITA-2. Packed baudot.
Data.
8.35.8 TX -S _________________________________________________ SPECIFY TRANSMIT SERVICE

Purpose: Specifying the transmit service to use.
Format:
TX <filename> -s <delivery service>

An integer specifying the delivery service:
0
Store-and-forward.
Prefixed Store-and-forward.
8.35.9 TX -T _________________________________________________ SPECIFY TERRESTRIAL LINK

Purpose: Specifying the terrestrial link to use.
Format:
TX <filename> -t <destination network type>

An integer specifying the destination network type:
0
Telex
PSTN Use -e(fax or telephone modem)
PSDN(X.25 data network)
Closed networkUse -e(DNID's)
Special access codeUse -e
8.35.10 TX -V __________________________________________________ REQUEST CONFIRMATION

Purpose: Request confirmation from the Land Earth Station on the final delivery from
the LES to the destination.
Format:
TX <filename> -v <options>
8.35.11 TX -Y ________________________________________________________ TRANSMISSION DATE

Purpose: Set transmission date.
Format:
TX <filename> -y <year-month-day> <options>
If specified without parameters current date is displayed after execution. [ver 2.12]
Command Reference
149
TX

8.36 TYPE
8.36.1 TYPE ___________________________________________ DISPLAY THE CONTENTS OF A FILE
Purpose: Display the contents of a file.
Format:
TYpe <filename> <options>
This command will display the contents of a file on the console the way the DOS typecommand does if no options are specified.
After typing the file the Transceiver automatically removes the file from its memory
unless the -k option is added.
8.36.2 TYPE -B ___________________________________________________________ TYPE BINARY
Purpose: The file is typed binary.
Format:
TY <filename> -b <options>
The file is typed binary. In the first line the byte count is given. All characters from 00H
to FFH are used. After typing the file the transceiver automatically removes the file from
its memory unless the -k option is added.
8.36.3 TYPE -K _________________________________________________________ TYPE AND KEEP
Purpose: The file is typed and the file is kept in the Transceiver.
Format:
TY <filename> -k <options>
The file may be deleted using the delete command.
8.37 WEEKSCHED
[ver 2.12]
8.37.1 WEEKSCHED _________________________________________ SETTING UP A WEEK SCHEDULE
Purpose: Setting up a week schedule.
Format:
WeekSched <options>
A week schedule can be set up to control interval programs in order to suppress

reports that, e.g., fall outside office working hours (see section 4.4.1 for more details).
The week schedule contains up to 21 time intervals where programs are allowed to
send reports.
The week schedule only has effect on the interval programs where this function is
enabled. See paragraph 8.23.5 PG -e Extended program set-up for information on how
to activate the week schedule control.
Command Reference
150
Type

8.37.2 WEEKSCHED -C __________________________________________ CLEAR WEEK SCHEDULE

Purpose: Delete one (or all) of the week schedule entries.
Format:
WS -c all
WS -c <EntryNo>
EntryNo: The schedule entry to delete [0..20].

This command can delete either all or one specific week schedule entry.
Use the WEEKSCHED -d command to obtain a list of the current schedule entries (see
paragraph 8.37.3 ).
8.37.3 WEEKSCHED -D _________________________________________ DISPLAY WEEK SCHEDULE
Purpose: Display the current set of week schedule entries.
Format:
WS -d
Example:
This schedule is set up to enable interval reports Monday-Thursday 8.00 AM to 4:00 PM
and Friday 8:00 AM to 3:00 PM.
: weeksched -d<CR><LF>
<CR><LF>
No Start day/hour Stop day/hour<CR><LF>
0
1 (Mon) 8
1 (Mon) 16<CR><LF>
1
2 (Tue) 8
2 (Tue) 16<CR><LF>
2
3 (Wed) 8
3 (Wed) 16<CR><LF>
3
4 (Thu) 8
4 (Thu) 16<CR><LF>
4
5 (Fri) 8
5 (Fri) 15<CR><LF>
<CR><LF>
5 schedule entries used<CR><LF>
8.37.4 WEEKSCHED -O ___________________________________ CREATE WEEK SCHEDULE ENTRY

Purpose: Create a week schedule entry.
Format:
WS -o <StartDay>,<StartHour>,<StopDay>,<StopHour>
StartDay: Start day for entry [1..7].

1 = Monday
7 = Sunday
StartHour: Start hour for entry [0..24].
0 = midnight at the beginning of the day
24 = midnight at the end of the day.

StopDay: Stop day for entry [1..7].
1 = Monday
7 = Sunday
StopHour: Stop hour for entry [0..24].
Command Reference
151
Weeksched

0 = midnight at the beginning of the day
24 = midnight at the end of the day.

Creates a new entry in the week schedule. The schedule can contain up to 21 entries
(internally numbered from 0 to 20). Stop day/hour must be later than the start day/hour.
Example:
Create a schedule entry covering Friday 8:00 AM to 3:00 PM.
: weeksched -o 5,8,5,15<CR><LF>
<CR><LF>
:
8.38 ZONE
The zones can be used to reduce or increase the number of transmitted position reports
depending on, where the vessel/vehicle is see also 4.11 Surveillance zones.
Command Reference
152
Zone

8.38.1 ZONE _______________________________________________ SET-UP SURVEILLANCE ZONES

Purpose: Set-up surveillance zones.
Format:
ZOne <options>
BASIC ZONES FEATURE, SUMMARY OF COMMANDS

ZONE -d
Displays the zone configuration
ZONE -i
Change the reporting interval
ZONE -n
Create a new zone
ZONE -o
Add radius or width
ZONE -p
Add a position to a zone
ZONE -r
Remove a zone
ZONE -t
Test a position
ZONE -s
Get the current zone number [ver. 2.10]
ZONE -u
Check all zones now [ver. 2.10]
ADVANCED ZONES FEATURE, SUMMARY OF COMMANDS [VER. 2.10]

ZONE -dg Display Zone Group Configuration
ZONE -ig Setup interval for zone in group
ZONE -ng Add Zone to Group
ZONE -og Setup radius of zone in group
ZONE -pg Setup positions in group
ZONE -rg Remove zone in group
ZONE -dl Display Zone Group List Configuration
ZONE -rl Remove Zone Group List
ZONE -g
Add a Group to a Zone Group List
ZONE -a
Display active zones
ZONE -ag Set active zone group

ZONE -al Set active zone group list
GENERAL COMMENTS
The zone has to be created using zone -n or zone -ng before the interval and positions
can be entered.
<zone no.> = "0" - "249"
<zone group no.> = "1" - "255"
<zone group list no.> = "1" - "255"
Command Reference
153
Zone

8.38.2 ZONE -A ___________________________________________________ DISPLAY ACTIVE ZONES

Purpose: Displays the number of the zone group list or zone group which is currently
active. Only one zone group or one zone group list can be active at one time.
Format:
ZO -a
Example
If zone group 1 is active:
: zo -a<CR><LF>
<CR><LF>
Active Zone Group: 1<CR><LF>
<CR><LF>
If zone group list 12 is active:
: zo -a<CR><LF>
<CR><LF>
Active Zone Group List: 12<CR><LF>
<CR><LF>
8.38.3 ZONE -AG ________________________________________________ SET ACTIVE ZONE GROUP

Purpose: Sets the specified zone group to active. The previously active group or list
will be deactivated.
Format:
ZO -ag <zone group no.>
<zone group no.> The number of the zone group to be activated. It is possible to enter
the number of a zone group that doesn't exist. In this case, no zones will be
checked. If a zone group with that number is added later, checking will start.
Example
: zo -ag 2<CR><LF>
<CR><LF>
8.38.4 ZONE -AL ____________________________________________ SET ACTIVE ZONE GROUP LIST

Purpose: Sets the specified zone group list to active. The previously active group or
list will be deactivated.
Format:
ZO -al <zone group list no.>
<zone group list no.> The number of the zone group list to be activated. It is possible to
enter the number of a zone group list that doesn't exist. In this case, no zones
will be checked. If a zone group list with that number is added later,
checking will start.
Example
Command Reference
: zo -al 12<CR><LF>
<CR><LF>
154
Zone

8.38.5 ZONE -D ______________________________________ DISPLAYS THE ZONE CONFIGURATION

Purpose: Displays the zone configuration.
Format:
ZO -d <zonenumber >
Use <zonenumber> to select a specific zone.

Example
: zo -d 1<CR>
Zone 1: Valid
Type 8, reporting interval
Number of positions 5
Position 01: 55 44 37N 012
Position 02: 55 44 37N 010
Position 03: 55 44 37N 008
Position 04: 55 44 37N 006
Position 05: 00 00 00N 000
Width
: 400.0 km
600 frames
23
23
23
23
00
45E
46E
46E
46E
00W
8.38.6 ZONE -DG ___________________________________DISPLAY ZONE GROUP CONFIGURATION

Purpose: Displays a list of the zone groups stored in the transceiver. If a zone group
number is specified, a list of the zones in that zone is displayed.
Format:
Example
ZO -dg [<zone group no.>]

: zo -dg<CR><LF>
<CR><LF>
Zone Groups:<CR><LF>
Default Zone Group<CR><LF>
Zone Group 1<CR><LF>
18 Zone Group(s)<CR><LF>
<CR><LF>
8.38.7 ZONE -DL ______________________________ DISPLAY ZONE GROUP LIST CONFIGURATION

Purpose: Displays a list of all the zone groups in the specified zone group list. If the
zone group list number is omitted, a list of all the existing zone group lists is
displayed instead.
Format:
Example
Command Reference
ZO -dl [<zone group list no.>]

: zo -dl<CR><LF>
155
Zone

<CR><LF>
Zone Group Lists:<CR><LF>
Zone Group List 1<CR><LF>
14 Zone Group List(s)<CR><LF>
<CR><LF>
8.38.8 ZONE -G ______________________________________ADD A GROUP TO A ZONE GROUP LIST

Purpose: Adds a reference to the specified zone group to a zone group list.
Format:
ZO -g <zone group list no.>,<zone group no.>[,<zone no.>]
<zone group list no> The number of the list to which the zone group reference should
be added. If the list doesn't exist, it will be created.
<zone group no.> The number of the zone group to be added. It is possible to add
references to non-existing zone groups to a list. Entries containing
references to non-existing zone groups will be skipped when checking
zones. If the zone group is added later, it will then be included in the check.
<zone no.> The number of an individual zone in the zone group. This parameter is
optional. If it is omitted, the whole zone group will be referenced.
Example
Add zone group 2 to zone group list 173:
: zo -g 173,2<CR><LF>
<CR><LF>
8.38.9 ZONE -I _________________________________________ CHANGE THE REPORTING INTERVAL

Purpose: Add or change the reporting interval in a zone
Format:
ZO -i <zonenumber>,<reporting interval>
<reporting interval> = "20" - "65535"

Example
zo -i 1,600<CR>
8.38.10 ZONE -IG _____________________________________ SETUP INTERVAL FOR ZONE IN GROUP

Purpose: Sets the reporting interval to be used when the transceiver is inside the
specified zone.
Format:
ZO -ig <zone group no.>,<zone no.>,<reporting interval>
<reporting interval> = "20" - "4999" | "0"

Reporting interval in frames. If the interval is set to 0, the interval is not set to
a special zone interval when entering this zone.
Command Reference
156
Zone

Example
: zo -ig 2,9,2000<CR><LF>
<CR><LF>
8.38.11 ZONE -N ____________________________________________________ CREATE A NEW ZONE

Purpose: Create a new zone.
ZO -n <zonenumber>,<zonetype>[, <numberofpositions>]
Format:
<Zonetype>
Shape
1
2
3
4
5
6
7
8
Circle
When a zone type 8 polyline is created the <numberofpositions> must be entered.

Example
zo -n 1,8,5<CR>
8.38.12 ZONE -NG ___________________________________________________ADD ZONE TO GROUP

Purpose: Creates a new zone of the specified type in the specified zone group.
ZO -ng <zone group no.>,<zone no.>,<zonetype>[,<no of positions>]
Format:
<Zonetype>
Shape
1
Circle
2
3
4
5
6
7
8
When a zone type 8 polyline is created the <no. of positions> must be entered.
Example
: zo -ng 254,7,8,30<CR><LF>
<CR><LF>
: zo -ng 254,8,3<CR><LF>
<CR><LF>
8.38.13 ZONE -O ___________________________________________________ ADD RADIUS OR WIDTH

Purpose: Sets the circular zone radius or polyline width. Radius and width are entered
in units of 100 m
Format:
ZO -o <zonenumber>,<radius>|<width>
<radius> = "1" - "4999"

Command Reference
157
Zone

<width> = "1" - "255"

Example
zo -o 1,4000<CR>
8.38.14 ZONE -OG _________________________________________ SETUP RADIUS OF ZONE IN GROUP

Purpose: Sets the circular zone radius or polyline width. Radius and width are entered
in units of 100 m.
Format:
ZO -og <zone group no.>,<zone no.>,<radius>|<width>
<radius> = "1" - "65535"

<width> = "1" - "255"
Example
: zo -og 254,7,10<CR><LF>
<CR><LF>
8.38.15 ZONE -P _______________________________________________ ADD A POSITION TO A ZONE

Purpose: Add/Change a position in a zone.
Format:
ZO -p <zonenumber>,<positionnumber>,<lat deg>,<lat min>,<lat

dsec>,<hemNS>, <lon deg>,<lon min>,<lon dsec>,<hemEW>
<positionnumber> = "1" - "40"

<lat deg> = "0" - "90"
<lat min> = "0" - "59"
<lat dsec> = "0" - "99"
<hemNS> = "n"|"N"|"s"|"S"
<lon deg> = "0" - "180"
<lon min> = "0" - "59"
<lon dsec> = "0" - "99"
<hemEW> = "e"|"E"|"w"|"W"
Example
Command Reference
zo -p 1,1,55,44,37,n,12,23,45,e<CR>
158
Zone

8.38.16 ZONE -PG ______________________________________________ SETUP POSITIONS IN GROUP

Purpose: Sets the specified position of the specified zone in the specified zone group.
Format:
ZO -pg <zone group no.>,<zone no.>,<position no.>,<lat deg>,<lat

min>,<lat dsec>,<hemNS>,<lon deg>,<lon min>,<lon dsec>,<hemEW>
<positionnumber> = "1" - "40"

<lat deg> = "0" - "90"
<lat min> = "0" - "59"
<lat dsec> = "0" - "99"
<hemNS> = "n"|"N"|"s"|"S"
<lon deg> = "0" - "180"
<lon min> = "0" - "59"
<lon dsec> = "0" - "99"
<hemEW> = "e"|"E"|"w"|"W"
Example
Set position no. 2 in zone no. 1 in zone group 17:
: zo -pg 17,1,2,48,27,00,n,25,00,00,w<CR><LF>
<CR><LF>
8.38.17 ZONE -R ________________________________________________________ REMOVE A ZONE

Purpose: Remove a zone.
Format:
ZO -r <zonenumber>
<zonenumber> = "1" - "250"

8.38.18 ZONE -RG ________________________________________________ REMOVE ZONE IN GROUP
Purpose: Deletes the specified zone from the specified zone group. If the zone number
is omitted, the whole zone group is deleted.
Format:
ZO -rg <zone group no.>[,<zone number>]
Example
Delete zone group 17
: zo -rg 17<CR><LF>
<CR><LF>
8.38.19 ZONE -RL______________________________________________ REMOVE ZONE GROUP LIST

Purpose: Deletes the specified zone group list.
Format:
Example
Command Reference
ZO -rl <zone group list no.>

: zo -rl 173<CR><LF>
<CR><LF>
159
Zone

8.38.20 ZONE -S ___________________________________________GET THE CURRENT ZONE NUMBER

Purpose: Displays the current zone status, i.e. the zone group number and zone
number of the transceivers current position. Note that it may take a few
seconds or minutes from the time when the transceiver enters a zone until it
is detected by the transceiver. The time spent depends on the number of
active zones.
Format:
Example
ZO -s
: zo -s<CR><LF>
<CR><LF>
Current Zone:<CR><LF>
Zone Group: 1<CR><LF>
Zone:
5<CR><LF>
<CR><LF>
8.38.21 ZONE -T ________________________________________________________ TEST A POSITION

This command is used to test if a position is inside a zone. The command only checks
zones in the default zone group.
Purpose: Test if a position is inside a zone.
Format:
ZO -t <lat deg>,<lat min>,<lat dsec>,<hemNS>, <lon deg>,<lon min>,<lon

dsec>,<hemEW>
<lat deg> = "0" - "90"

<lat min> = "0" - "59"
<lat dsec> = "0" - "99"
<hemNS> = "n"|"N"|"s"|"S"
<lon deg> = "0" - "180"
<lon min> = "0" - "59"
<lon dsec> = "0" - "99"
<hemEW> = "e"|"E"|"w"|"W"
Example
zo -t 55,44,37,n,12,23,45,e<CR>
Position is in Zone 1, repinterval 600, Idx 1
8.38.22 ZONE -U ___________________________________________________ CHECK ALL ZONES NOW

Purpose: Checks all the active zones immediately. Normally the transceiver checks
only one zone per 10 seconds. This command updates the zone group
number and zone number shown by the zone -s command.
Format:
Command Reference
ZO -u
160
Zone

INFO AND ERROR MESSAGES

9.1 INTRODUCTION
The following section gives an overview of the status reports that the transceiver might
give, either as part of a message protocol, as part of a regular (daily) operation, or as
an operation initiated by a Land Earth Station.
A report line like:
30"Login failed"
will be stored in the status buffer as:

INFO
An error line like:
30 : Login failed
251Transceiver is no longer logged in
will be stored as:
ERROR 251 : Transceiver is no longer logged in
The actual text of the status and error reports will be subject to modification by
Thrane & Thrane, so an intelligent controller connected to the transceiver should only
rely on the INFO and ERROR numbers given in the reports.
9.2 COMMAND STATUS REPORTS

The following reports might be shown when using the built-in command set.
Info and Error Messages
161
Introduction

20
"Sending Distress failed"
21
"Sending Distress successful"
22
"Sending Distress issued"
30
"Login failed"
31
"Login successful"
32
"Login issued"
40
"Logout failed"
41
"Logout successful"
42
"Logout issued"
50
"Changing NCS failed"
51
"Changing NCS successful"
52
"Changing NCS issued"
60
"Scanning failed"
61
"Scanning successful"
62
"Scanning issued"
80
"Transmitting message failed"
81
"Transmitting message successful"
82
"Transmitting message issued (filename)"

In the two first cases the following texts will be appended:
Destination <STX>(number) File (filename)<ETX>
(error information, if any)
Or
Destination <STX>(number) File (filename)<ETX>
Reference number (number)
(number) Attempts
In the failed case, this text will be appended:
(filename) : Transmitting message failed"
Destination (number) File (filename)
(error information, if any)
111
"Update Position"
The position has not been updated by GPS or user for some time. Enter a new position using
se -p or se -g
116
"Land Earth Station in Distress Generator has become invalid."

"\n\rAutomatically reset by transceiver."
The transceiver has logged into an ocean region where no LES is selected for distress alert.
Use se -m to enter a LES for the current ocean region.
130
"Confirmation request failed"
131
"Confirmation request successful"
132
"Confirmation request issued"
193
"Time to enter new position"

The position has not been updated by GPS or user for some time. Enter a new position using
se -p or se -g
233
"Distress EGC message received"

An EGC with distress priority has been received.
313
"Urgent EGC message received"

An EGC with urgent priority has been received.
473
Received Distress call has been acknowledged

The user has cleared the indication indicating a message or EGC with distress priority has
been received.
480
"Position report failed"
481
"Position report successful"
482
"Position report issued"
490
"Data report failed"
491
"Data report successful"
162
Command Status Reports

492
"Data report issued"
510
"Programmed report failed"
511
"Programmed report successful"
552
"Distress Message has been initiated."

A message with distress priority is being transmitted.
553
"Distress Message has been received."

A message with distress priority has been received.
804
"No Distress facility available."

User has tried to send an alert or use the distress generator but no kind of distress is allowed
on this transceiver
1010
"Request blocked by LES lock"

The transmission request could not be fulfilled because the desired LES is not allowed by the
LES lock.
1011
"LES(s) configured for LM Alert blocked by LES lock"

This warning indicates that one or more of the LESs set up for Land Mobile Alert are not
allowed by the LES lock.
1023
"Distress generator position older than 24 hours\r\nCheck that the GPS position is correct."
The position has not been updated by GPS or user for 24 hours. Enter a new position using se
-p or se -g
1024
"Distress indications ackowledged"

The user has cleared the distress alert indication.
1025
Initiated Distress Alert for LES ID,
Table 9.1 Command Status Reports
9.3 MESSAGE DELIVERY REPORTS

After a transmission a confirmation is recived (from the LES, sent via the NCS) that can
be either positive or negative. Even though a confirmation has not been requested, a
negative confirmation is always received if the delivery failed.
140
"Message delivery failed"
141
"Message delivery successful"
Table 9.2 Message Delivery Reports
The following text is appended in the two cases:

LES (number) Destination <STX>(number) File (filename)<ETX>
(number) Attempt(s), Land station gives failure code: (3 letter code)
or
LES (number) Destination <STX>(number) File (filename)<ETX>
(number) Attempt(s)
The Transceiver may also receive confirmations for messages no longer in the TXLOG.
In this case the filename will appear as OUT.___ (using three underscore characters for
the number) as the filename only is known via the TXLOG entries.
9.4 COMMAND ERRORS

In Table 9.3 is a short explanation of each error.
163
Message Delivery Reports

110
"Memory available: (number) bytes"

Warning at the file system memory limit.
120
"Invalid command"
This command does not exist.
121
"Bad parameter(s)"
At transmission: Wrong option values or missing destination in the message file. Filename or
file is missing.
123
"Comport input error

Transceiver will be restarted"
A fatal serial communications input error has occurred. The Transceiver will restart it's
program as this is the only way to go to a well-known state.
126
"Land Mobile alert is not supported"

The MOBALERT environment variable has not been set correctly.
127
"Datareport cancelled. You are not logged in"

The Transceiver must be logged in when sending data reports.
251
Transceiver is no longer logged in
258
EGC reception in progress"

New commands will not be accepted while the Transceiver is receiving an EGC message
(except for distress alerts).
321
"Too many buffers used"

Internal memory error.
325
"Hardware problems. Distress button failure.\n\rDistress button may no longer work."

The distress button on the alarm panel is failing or not connected.
330
"File error"
Internal file system error. File copy error, file creation error or too many open files.
331
"File is missing"
A wrong filename has been given or a incorrect address line for transmit files has been
detected. Check the transmit command syntax and the file contents.
332
"File is too big for memory"

The file system memory is filled.
333
"File is empty"
The message could not be sent because the file was empty (no address line).
336
"Duplicate file exists"

The file system has got a file with this name already. This error appears at a file transfer.
337
"Invalid filename"
Filenames starting with the '_' underscore character can not be used.
338
"Log in use, please wait"
Table 9.3 Command Errors
9.5 RECEIVING MESSAGES

When a message has been received one these report is given:
90
91
"Receiving message failed"

"Receiving message successful"
For a telex, the following text will be added:
"Message no. <STX>(number)<ETX> Language
<STX>(number)<ETX>"
For an EGC message, the following text will be added:
"Message no. <STX>(number)<ETX> Priority
<STX>(number)<ETX> LES id <STX>(number)<ETX> EGC
service <STX>(hexadecimal number)<ETX>"
Table 9.4 Receiving Messages Info's
164
Receiving Messages

9.6 GPS STATUS

The built-in GPS may result in the following INFO message.
463
"UTC was updated by GPS"

The Transceiver's hardware CMOS clock has been corrected to the
received GPS UTC.
Table 9.5 GPS Info's
9.7 GENERAL STATUS

127
"Transceiver no longer logged in"
220
"Synchronization failed"
221
"Synchronization successful"
1013
"Transceiver disk space below 32 Kbytes, files might be

overwritten."
Table 9.6 General Status
The following status appears when an entry in one of the log files has been changed.
The TXLOG will change during the transmission protocol and when confirmation is
received. The RXLOG is updated after a successful receive protocol. The EGCLOG is
changed after an EGC message has been received or received once more.
393
"TXLOG updated"
403
"RXLOG updated
413
"EGCLOG updated
653
"Datareport buffer request : <LES_id>,<DNID>,<Member No>

<FrameNo>"
663
"Datareport buffer is now used"
Table 9.7 General Status after Log file Changes
These two status messages can be used to fill up the data-report buffer. The first one
(653) arrives 5 frame before the next programmed transmission should occur, and it
specifies how many bytes will be used for the next report and in which frame the report
will be sent. This message marks when to start filling up the buffer
The second status message (663) arrives 8 seconds after the first and marks when to no
longer fill data in the buffer, as it will not be used for the upcoming report (but for the
next report).
9.8 LINK STATUS

Whenever a link error occurs the originator of the message is stated:
Message from Transceiver:
or
Message from Land Station:
appear before the reason of the error.
Only in case of non-delivery message codes like:
Land Station gives error code: PRF
can still be found, where PRF would stand for "Protocol Failure".
165
GPS Status

These codes can not completely be eliminated as they can vary from Station to Station.
In case a full explanation is wanted contact the LES operator.
9.8.1 LIST OF LINK ERROR MESSAGES
A complete list of error messages is found in this section.
LES MESSAGES IN CASE OF A PENDING/REJECTED CALL
811
814
"Message from Land Station: Call rejected: "

"Message from Land Station: Call pending: "
followed by:
"Land Station message store full."
"Requested destination not served."
"Satellite circuit not available."
"Terrestrial circuit not available."
"Requested type of transmission not provided."
"Transmission request in queue."
"You are not allowed to use the system."
"Your Transceiver is not logged in."
"Your Transceiver is not commissioned."
"Will call you up later."
"Illegal request."
"Land Station out of service."
"Requested service is temporarily unavailable."
"Access to requested service is denied."
"Invalid service."
"Invalid address."
Table 9.8 LES Messages in case of a Pending/Rejected Call
LES MESSAGES IN CASE OF AN ABORTED CALL

813
"Message from Land Station: Call aborted: "

followed by:
"Did not receive your message."
"Transceiver did not follow call procedure."
"Fatal Land Station error."
"Call cleared by Land Station operator."
"Call cleared by Transceiver."
"Land Station did not follow call procedure."
"Land Station has detected Transceiver error."
"Transceiver did not receive message from Land Station."
"Land Station does not support this message format."
"Requested service is temporarily unavailable."
"Access to requested service is denied."
"Invalid service."
"Invalid address."
"Your destination is not commissioned."
"Your destination is not logged in."
"Your destination is not allowed to use the system."
"Requested service is not provided."
Table 9.9 LES Messages in case of an A borted Call
166
Link Status

TRANSCEIVER MESSAGES
"Message from Transceiver:"
followed by:
801
"Land Station out of service."

The TDM information indicates by a flag in the bulletin board that the particular LES is out of
service.
802
"Satellite link occupied."

The Transceiver has tried to find a free signalling channel slot for 5 times without success, or the
TDM bulletin board indicated "congestion".
806
"No usable signalling channels available at present."

The TDM information indicates by a flag in the signalling channel descriptor that there are no
slotted Aloha signalling channels available.
807
"Your reception is OK,

but erroneous information is transmitted from Land Station."
The TDM bulletin board information indicates 0 or more than 40 signalling channels available.
808

but vital information is not transmitted by Land Station."
Either the signalling channel descriptor or the transmission burst was not received two times
during reserved access transmission, or the signalling channel descriptor was not received 25
times in unreserved access.
809

but your transmission is not received by Land Station."
The Transceiver tried to send the burst 9 times without success.
812
"Land Station did not respond to transmission request"

The Transceiver did not receive an assignment to send a message.
815
"Land Station did receive request, but did not respond to it."
The Transceiver timed out waiting for a response packet from the LES.
816
"Transmission aborted by operator."

The user or the Transceiver aborted the operation.
817
"The Land Station does not exist in this Ocean Region."

The coast station selected for transmission was not found in the LES table.
819
"Cannot acquire synchronization at the satellite channel."

The synchronization was not found within 25 seconds after the tracking was finished, or the
tracking was not successful after 3 minutes.
822
"Did not receive any message from Land Station."

The Transceiver tried 4 times to request message packets from the LES.
823
"Land Station did not finish message."

The Transceiver tried 4 times to end a message reception with the LES.
824
"Reception aborted by operator."

The user or the Transceiver aborted message reception.
831
"Transmission hardware error."

Error detected in transmit queue hardware.
840
"Land Station did not follow call procedure."

The LES did not reserve a signalling channel slot for the Transceiver as expected.
841
"Inmarsat-C System is now in Restoration mode."

The system cannot be used for login, logout and link tests as the NCS is out of operation at the
moment.
842
"Land Station does not support Land Mobile Alerts"

The TDM channel information indicated that the LES did not support the alert service.
850
"No response from Land Station."

The Transceiver sent a login request 4 times without a response.
852
"Illegal service specified."

The store-and-forward service type was not specified for the transmission.
167
Link Status

853
"Expected Land Station was not found"

The Transceiver has checked the LES ID in the DNID table against the origin ID in the LES TDM and
found that they were different. Either the Transceiver tuned to the wrong channel, or the LES TDM
channel has been configured incorrectly.
854
"The 5 bit (ITA-2) service is not available at this LES."

The service bit indicator from the LES is OFF. Try another service or another LES.
855
"The 8 bit (Data) service is not available at this LES."

The service bit indicator from the LES is OFF. Try another service or another LES.
Table 9.10 Transceiver Messages
9.9 LINK TEST MESSAGES

343
Link Test started
353
Link Test finished
363
Link Test failed
500
Link Test Request failed
501
Link Test Request successful
502
Link Test Request issued
Table 9.11 Link Test Messages
9.10 DISTRESS TEST MODE

733
"Test Mode ON"

The maritime distress button is in test mode. No real distress are
sent.
803
"Test Mode OFF"

The maritime distress button is not in test mode. Real distress are
sent.
Table 9.12 Test Mode Messages
9.11 SLEEP MODE

963
Turn off remote power to enter sleep mode
973
Waked Up
Table 9.13 Sleep Mode Messages
168
Link Test Messages

Position Report Packet Format

A.1 Packet Formats defined for the satellite link
The position report format used for the Maritime or Land Mobile Transceivers is defined
by Inmarsat.
Each position report can contain additional information such as detailed date
information or status of the I/O pins. The position reports have this general format.
Each element except the first can be disabled. Each element will follow directly after
the previous, even if some elements are disabled. If only the <speed and course> are
enabled it will follow directly after <position and date>.
In the position reports with MEM-code IO-Report (71) the <I/O status> will always be
included. In position reports with MEM-code Enter Zone (72) the <ZoneNo> will always
be included. In position reports with MEM-code Above Speed Limits (89) the <Speed
and course> will always be included.
<Position report> ::= [<API Header>]<Position and Date>[<Detailed date
information>][< I/O status>] [<Speed and course>][<ZoneNo>][<User string>][<Extra
position precision>] [<tachograph data>]
The <API Header> is described in appendix H
<Position and Date> ::= <Maritime Position and date>|<Landmobile position and date>
Landmobile
1st Packet
Maritime
7 6 5 4 3 2 1 0
7 6 5 4 3 2 1 0
0 0 H Lat. Degrees
Lat. Minutes
0 1 H Lat. Degrees
Lat. Minutes
H = 1 for South, 0 for North
Lat. Min. Frac.

H Lon.
Degrees
Lon.
Minutes
L.Min. Frac.
Lat. Min. Frac.

H Lon.
Degrees
Lon.
Minutes
L.Min. Frac.
H = 1 for West, 0 for East
Macro Encoded Msg.

Attribute
Fraction is in units of 0.04 of a minute
Macro Encoded Msg.

Attribute
Attribute
Attribute
Reserved
Speed
Reserved
Course
Reserved
Reserved
2nd Packet
Figure 9.1: Position Report Format
The position reports use:

Maritime: 12 bytes (10 bytes if no data is appended)
Land Mobile: 10 bytes (8 bytes if no data is appended)
In position reports the Time of Position is decoded into the 2 attribute bytes:
The first bit indicates which month: 0 = This month, 1 = Next month.
The next 5 bits indicate the day of the month.
169

The next 5 bit indicate the hour of the day.

The last 5 bits indicate minutes divided by 2.
1st Packet of Positioning Report

Position (39 bits):
<Position> ::= <Latitude><Longitude>
Latitude (19 bits):
<Latitude> ::= <Hemisphere><Lat. Degrees><Lat. Minutes><Lat. Min. Fractional>
Hemisphere (H) (1 bit):
North/South indication. Set to 0 for North or 1 for South.
Lat. Degrees (7 bits):
The degrees of Latitude, North or South. 1 is 60 minutes.
Lat. Minutes (6 bits):
The integer part of the Minutes of latitude. 1 latitude minute is 1 nautical mile (~1852
meters)
Lat. Min. Fractional part (5 bits):
The fractional part of the Minutes of latitude in units of 0.04 of a Minute i.e. ~74 meters.
Longitude (20 bits)
<Longitude> ::= <Hemisphere><Lon. Degrees><Lon. Minutes><Lon. Min. Fractional>
Hemisphere (H) (1 bit):
East/West indication. Set to 0 for East or 1 for West.
Lon. Degrees (8 bits):
The degrees of Longitude, East or West.
Lon. Minutes (6 bits):
The integer part of the Minutes of longitude.
Lon. Min. Fractional (5 bits):
The fractional part of the Minutes of longitude in units of 0.04 of a Minute.
Macro Encoded Msg (MEM) (7 bits):
The Macro Encoded Message (MEM) number is a code that identifies the reason for
sending the report (such as regular position reporting or a report triggered by some
specific event). See sections 4.4 and 4.5 for a more details.
Attribute (date and time) (16 bits):
<Date, time>::=<Reserved><Day><Hour><Minute>
Reserved (1 bit):
Set to zero
Day (5 bits):
Value: 0 - 31 (Day of the month)
Hour (5 bits):
Value: 0 - 23 (Hour of the day)
Minute (5 bits):
Value: 0 - 29 (Minute within the hour given in units of 2 minutes)
170

2nd Packet of Positioning Report
For Landmobile: The Landmobile Position includes as default two reserved bytes in the
optional packet.
Reserved (16 bits):
Set to zero.
For Maritime: The Maritime Position includes by default speed, course and a reserved
field in the 2nd packet. The formats of the speed and course fields are like this:
Speed (8 bits):
Speed is coded as a one byte unsigned binary number with a resolution of 0.2 knots. If
no valid data is available at the MES, the field should be set to "FFH".
Course (9 bits):
The Course is coded as a 9 bit unsigned binary number with a resolution of 1 degree.
Reserved (15 bits):
Set to zero.
Detailed date information

<Detailed date information> ::= <Date Format 1>|<Date Format 2>|<Date Format 3>
<Date Format 1> ::=<Month><Year><Not used>
7
Month
Year
Year
Not used
Month (4 bits):
Value: 1 - 12
Year (6 bits):
Value: 0 - 63 (gives the year 1997 - 2060)
<Date Format 2> ::=<S><Year><Month><Day><Hour><Minutes><Not used>
7
Year
Spare
Month
Day
Day
Hour
Minutes
Minutes
Not used
Year (7 bit):
171

Month (4 bit):
Value: 1 - 12
Day (5 bit):
Value: 0 - 31
Hour (5 bit):
Value: 0 - 23
Minutes (6 bit):
Value: 0 - 59
<Date Format 3> ::=<S><Year><Month><Day><Hour><Minutes><Not used>
7
Spare
Year
Month
Day
Hour
Hour
Minutes
Not used
Year (12 bit):

Month (4 bit):
Value: 1 - 12
Day (5 bit):
Value: 0 - 31
Hour (5 bit):
Value: 0 - 23
Minutes (6 bit):
Value: 0 - 59
I/O status
< I/O status> ::= <Tag><Port value>
The I/O event reports use MEM-code (71) by default.
The actual format of the data report will vary depending on the type of the TT-3026 (see
section 1.1 Applicability for a list). TT-3026 types L, M, and S are identical but TT3000SSA differs because the I/O pins are dedicated to control the alert buttons and a
direct report of the pin status would not provide much useful information. In stead the
I/O status for this transceiver type is recoded to provide information about the alert
buttons.
Which of the I/O formats are actually used can be determined from the tag field, which
is either 3 or 70.
172

For TT-3026 L/M/S/D/LM and C(covert alert disabled):The following data will be added to the
data report in the free field:
7
Tag = 3
Port value bitmap
Port value bitmap (1 byte):

Bit 0
:
pin 2
Bit 1
:
pin 3
Bit 2
:
pin 4
Bit 3
:
pin 5
Bit 4
:
pin 6
Bit 5-6
:
reserved, set to 0
Bit 7
:
alert reporting active (*** see below)
For TT-3000 SSA and C(covert alert enabled):The following data will be added to the data report
in the free field:
7
Tag = 70
Port value bitmap

Bit 0-1
:
alert button 1 state (* see below)
Bit 2-3
:
alert button 2 state (* see below)
Bit 4-5
:
test lamp state (** see below)
Bit 6
:
reserved, set to 0
Bit 7
:
alert reporting active (*** see below)
(*) The alert buttons are coded into two bits like this:
00: Operational, released
01: Operation, pressed
10: Not operational: test mode
11: Not operational: Faulty
(**) The test lamp state is coded into two bits like this:
00: Light off
01: Light on
10: Slow blink (alert cancellation indication)
11: Quick blink (test indication)
(***) The alert reporting state is coded into one bit like this:
0:
No alert reporting
1:
Alert reporting active
Speed and course

<Speed and course> ::=<Tag><Speed><Course><Altitude>
The following data can be added to the packet. The set-up of the DNID or the position
report type determines if it is added.
173

7
Tag = 65
Speed in km/h
Course in degrees
Reserved
Zone number
<ZoneNo> ::= <Tag><Zone number >
The following data will be added to the position report in the free field:
7
Tag = 66
Zone number
User string
<User string> ::= <Tag><String-length><String>
7
Tag = 67
String-length
String
.....
String-length (8 bit) :
Value: 1 - 22
String (1 - 22 bytes) :
Value: User string
If the user string is longer than the available free bytes in the position report, the userstring will be truncated.
174

Extra position precision

The precision of the position in <Position and Date> is equal to 0,04 fractions of a
minute. This can be extended to 0,005 or 0,001 fractions of a minute when using <Extra
position precision>
<Extra position precision> ::= <Tag>(<Extra precision 0.005>|<Extra precision
0.001>)
Extra precisson 0.005:
7
Tag = 68
Sign
Lat.
Sign
Lon.
Offset Lat.
Offset Lon
The precise latitude position is calculated in the following way:

If <Sign Lat.> = 0 then
<Lat. Min. Frac. In 200 of a minute> = 8*<Lat. Min. Frac.> + <Offset Lat.>
<Lat. Min. Frac. In 200 of a minute> = 8*<Lat. Min. Frac.> - <Offset Lat.>
If <Lat. Min. Frac. In 200 of a minute> < 0 then
<Lat. Min. Frac. In 200 of a minute> = 200 + <Lat. Min. Frac. In 200 of a minute>
<Lat. Minutes> = <Lat. Minutes> -1
If <Lat. Min.> < 0 then
<Lat. Minutes> = 59
<Lat. Degrees> = <Lat. Degrees> -1
The precise longitude position is calculated using the same method.
Extra precisson 0.001:
7
Tag = 71
GPSQ
HDOP
Sign
Lat.
Sign
Lon.
Offset Latitude
Offset Longitude
The precise latitude position is calculated in the following way:

<Lat. Min. Frac. In 1000 of a minute> = 40*<Lat. Min. Frac.> + <Offset Latitude>
<Lat. Min. Frac. In 1000 of a minute> = 40*<Lat. Min. Frac.> - <Offset Latitude>
175

If <Lat. Min. Frac. In 1000 of a minute> < 0 then

<Lat. Min. Frac. In 1000 of a minute> = 1000 + <Lat. Min. Frac. In 1000 of a
minute>
<Lat. Minutes> = <Lat. Minutes> -1
If <Lat. Min.> < 0 then
<Lat. Minutes> = 59
<Lat. Degrees> = <Lat. Degrees> -1
The precise longitude position is calculated using the same method.
The GPSQ field indicates the GPS fix type at the time of the reported position:
0
1
2
: 2D fix
: 3D fix
: 3D fix + SBAS reception
The HDOP field indicates the assumed quality of the GPS position. It is coded into the
following values:
: HDOP 2
: 2 < HDOP 5
: 5 < HDOP 10
: 10 < HDOP
0
1
2
3
Tachograph data
<Tachograph data> ::= <Tag><Travelled distance><Last park time offset><Last start
time offset>
7
Sub-address = 69
Travelled distance
Last park time offset
Last start time offset
176

Travelled distance (26 bits): The travelled distance according to the tachograph
interface in units of 0,1 km.
Value: 0 - 67.108.863
Last park time offset (11 bit): Time of the last parking registered by the tachograph
interface. The time is in units of 2 minutes and is an offset from the position report time.
The first bit is a sign +/- indicating that the offset time in the last 10 bits has to be added
or subtracted from the position report time.
Value: +/- 2046 minutes (if the offset is at its limits +/- 2046 minutes it means that to
offset is at least 2046)
Last start time offset (11 bit): Time of the last start registered by the tachograph
interface. The time is in units of 2 minutes and is an offset from the position report time.
The first bit is a sign +/- indicating that the offset time in the last 10 bits has to be added
or subtracted from the position report time.
Value: +/- 2046 minutes (if the offset is at its limits +/- 2046 minutes it means that to
offset is at least 2046)
177

A.2 T&T Data report format

Instead of the Maritime or Land Mobile packet format a special T&T data report format
can be used. The T&T Data report format is shown in Figure 9.2. As with the Maritime
and Land Mobile packet format each position report can contain additional information
such as detailed date information or status of the I/O pins.
<Data report> ::= [<API Header>]<T&T data report format>[<Two reserved
bytes>][<Detailed date information>][< I/O status>][<Speed and course>][<User
string>]
The formats of the additional data are described in A.1 If additional data is included two
reserved bytes will be included as well.
In the data reports with MEM-code IO-Report (71) the <I/O status> will always be
included. In data reports with MEM-code Above Speed Limits (89) the <Speed and
course> will always be included. Beware that the MEM-code is not included in the T&T
data report format.
7
Latitude in units of 5 Seconds
Longitude in units of 5 Seconds

Time in unit of 10 minutes
P
Speed in unit of 5 km/h
P = Panic indicator
E/L
Z = Zone crossing indicator
Heading in units
of 45 degrees
E/L = Enter/Leave zone indicator
Figure 9.2: T&Ts data report format
Latitude in units of 5 Seconds (17 bit) :

Value: 0 - 129600
Where a latitude value of 0 is 90 degrees south and a latitude value of 129600 is 90
degrees north.
Longitude in units of 5 Seconds (18 bit) :
Value: 0-259200
Where a longitude value of 0 is 180 degrees west and a longitude value of 259200 is 180
degrees east.
Time in units of 10 minutes since midnight between Sunday and Monday (10 bit) :
Value: 0-1007 (this gives day-of-week)
Panic indicator (1 bit) :
Value: pin 2 status.
178

Zone crossing indicator (1 bit) :

Value: 0=if not enter/leave zone event, 1=enter/leave zone event
Enter/Leave zone indicator (1 bit) :
Value: 0=enter zone, 1=leave zone
Speed in units of 5 km/h (5 bit) :
Value: 0-31
Heading in units of 45 degrees (3 bit) :
Value: 0-7
A.3 Message data report format

Message data reports contain a 4 byte header before the actual data. A 10 byte data
report is send as a 14 byte message if message data reporting is used. Message data
reporting is used in case normal data reporting isnt supported by the used LES or in
case message data reporting is selected as the protocol for the used DNID, see 8.9.9 DN
-g Reporting Protocol. The format of a message data report can be seen in the figure
below:
7
DNID
Ocean
LES ID
Member Number
Data
...
Figure 9.3: Message data reporting format

DNID (16 bits).
Ocean (2 bits): 0: AOR-W, 1: AOR-E, 2: POR, 3: IOR.
LES ID (6 bits).
Member Number (8 bits).
Data: The actual data in the report.
179

Differences in VMS configuration

between TT-3022D and TT-3026M
This appendix is meant as a guide to users who are familiar with the fishery
configuration in TT-3022D.
VMS DNID is not specifically supported, but DNID groups has replaced this
functionality. There are some differences though;
TT-3026M can have several DNID groups.
Programs and events are configured individually on each DNID or group, and only
affects these.
Setting up the DNID groups:
Download the DNIDs separately with a Download DNID Poll, and then assign them
to a group using the DN -E command on each of the DNIDs.
A program or event is configured on a DNID group in the same way it is configured

on a single DNID. The program or event is automatically applied to all DNIDs in the
group.
For more information, refer to DNID Groups (section 4.16 ), Download DNID Poll
(section 5.1 ) and the DN -E command (section 8.9.5 ).
Differences in VMS configuration between TT-3022D and TT-3026M
180

TT-3022D
TT-3026M
Fishery transceiver
easyTrack
FI cmd
Description
number
Replaced by
Comment
command
Set all values to default
Not supported
10
Date and time format
DN -F
Date formats 1-3 is supported
20
Antenna blocked/Disconnected followed
EV -E
Antenna disconnected is not
by normal position report
supported.
21
Retransmit failed reports
not supported but planned in
22
Blocked GPS detection
future versions.
EV -P
If set-up correctly with EV -P

command, an event with MEM
code 91 will be sent in case of
blocked GPS.
23
Long to short report interval support
PG -E,
PG -L
24
Nice power down support
SL -i
Nice power down support is

enabled using:
SL -i 0,0,0,0
This feature is Sleep Mode
Enabled without interval wakeup.
26
Disable send LED on position report TX
27
Stop button initiates position report
Not configurable, has no send

LED
Not supported.
(Can be implemented externally
via an I/O port)
28
Disable position report infos
Controlled by authority level on

DNID. INFOs will not be shown if
the user authority level is lower
than the authority level of the
DNID.
29
Password on da command
Security is controlled by the

authority level on the DNID. User
authority level must be equal to
or higher than the authority level
of the DNID.
31
Only one packet per position report
DN -F
32
Mask out speed and course
Not supported
33
Disable GPS first fix beep
Not configurable. No beep

function implemented
34
A in provider name
Supported [2.12]
35
Use VMS DNID for special reports
EV -p
All DNID or DNID groups can be

configured individually to
receive special reports.
36
Hide remote connection
Controlled by authority level on

DNID. Connections will not be
shown if the user authority level
is lower than the authority level
of the DNID.
40
MEM code translation table
DN -L
50
Position report packet 2 bit mask
Not supported
51
Number of positions in storage queue
Space for 250 positions. Not
60
Reporting intervals
PG -P,PG -L
Each interval program has
configurable.
181

individual long and short

interval.
Use PG -P to set-up the
normal/short interval, and PG -L
to set-up the long interval.
61
Reporting interval change distance
PG -L
70
VMS DNID
Not directly supported, but

functionality is replaced by DNID
groups.
71
VMS LES
Not directly supported, but

functionality is replaced by DNID
groups.
72
Number of active DNIDs in transceiver
DN -N
Table 9.14 Differences in VMS configuration between TT-3022D and TT-3026M
182

Packet format of the configuration poll

The configuration poll is used for remote configuration. The poll command for the
configuration poll is 6CH.
C.1 General format

The general format of the data in a configuration poll:
<configuration poll> ::= <Zero field><Command1>[<Command2>][< Command27>]
<Zero field> (1 byte):
Value 00H.
<Command> ::= <Packet descriptor><Ack reference><Type dependent fields>
<Packet descriptor> ::= <Packet descriptor type><Command type><Length>
There are two variations of the packet descriptor; the short packet descriptor (1 byte):
7
0
Command type
Length
Figure 9.4: Short packet descriptor

The medium packet descriptor (2 bytes):
7
Command type
Length
Figure 9.5: Medium packet descriptor

<Command type> (3 or 6 bits):
The type of command to be performed, see Table 9.15.
Command type
Description
Zone configuration
Zone group selection [2.21]
Zone group list selection [2.21]
Table 9.15: Configuration poll command types

<Length> (4 or 8 bits):
Contains size in bytes of the rest of the sub command:
Length = Size of: <Ack reference> + Size of: <Type dependent fields>
<Ack reference> (1 byte):
183

The ack reference consists of a command no (5 bit) and a spare field (3 bit). The
command no is a unique identification of each specific zone in the poll. This value is
used in the extended data field in the acknowledgement data report. A maximum of 27
commands can be transmitted in one poll.
7
Command no
Figure 9.6: Ack reference

Sub Command no: Legal values are 1-31.
<Type dependent fields>
Depends on the command type.
C.2 Packet format of the zone configuration poll

It is possible to configure up to 27 zones in the same configuration poll, as long as the
poll packet does not exceed the maximum size of 213 bytes.
<Type dependent fields> ::= <zone header1> <zone data1> [<zone header2> <zone
data2>] [<zone header27> <zone data27>]
184

Data field of the

zone
configuration poll
Bit no.
8 7 6 5 4 3 2 1
Zero field only in
beginnning of the data
field
Zero field
Packet descriptor
(Variable size)
Ack reference
Zone no.
Zone type
Reporting interval LSB
Reporting interval MSB
1st zone in poll
Zone data
(Variable size)
Fields used
for checksum
calculation
Checksum
Packet descriptor
(Variable size)
Ack reference
Zone no.
Zone type
2nd zone in poll
Zone data
(Variable size)
Checksum
Maximum number of
zones is 27, but
delimited by the
maximum packet
size of 213 bytes
Figure 9.7: Zone poll data.

185
Fields used
for checksum
calculation

C.2.1 Zone header :

(4 bytes)
The zone header consists of the Zone poll no, Zone type and the reporting interval:
Zone no:
The zone no. is a number indicating where to store the zone in the transceiver.
Value: 0-249
Zone type:
Valid zone type values are from 1-8. Refer to table 7.16.
Value: 1-8
Reporting interval:
A 2-byte value, indicating the number of frames between each data report sent. The
byte order is little endian, the least significant byte (LSB) comes before the most
significant byte (MSB). 10000 frames = 24 hours, 1 frame=8.64 secs.
Value: 20-10000 (frames)
C.2.2 Zone data :

(Variable size)
The zone data contains the actual data that describes the area of a zone. This field varies
in size, depending on the zone type as can be seen in table 7.16.
Zone type
Description
Zone data
Circle
[Pos][Radius]
Polygon with 3
[Pos1] [Pos2] [Pos3]
Polygon with 4
positions
[Pos1] [Pos2] [Pos3] [Pos4]
positions
4
Polygon with 5
[Pos1] [Pos2] [Pos3] [Pos4] [Pos5]
positions
5
6
7
8
Polygon with 6
positions
[Pos6]
Polygon with 7
positions
[Pos6] [Pos7]
Polygon with 8
positions
[Pos6] [Pos7] [Pos8]
Polyline with up to
[Pos1][Pos40][Width]
40 positions
Table 9.16: Zone types
A circle zone (type 1) consists of a position and a radius, a polygon consists of a specific
number of positions and a polyline consists of 2-40 positions and a width.
The format of a position, radius and a width is described below:
[Pos]
(5 bytes)
186

Lat. Degrees
Lat. Minutes
Lat.
Lon.
Frac. H
Lon.
Degrees
S
Lon. Frac.
Min.
1
2
3
4
5
Byte
Bit no.
8 7 6 5 4 3 2 1
Figure 9.8: Position format
Latitude Hemisphere (1 bit) :
Value: 0=North, 1=South
Latitude Degrees (7 bit) :
Value: 0-90 degrees
Latitude Minutes (6 bit) :
The integer part of the minutes of latitude.

Value: 0-60 minutes
Latitude Fractional part (5 bit) :
The fractional part of the minutes of latitude in units of 0.04 minutes.

Value: 0-25
Longitude Hemisphere (1 bit) :
Value: 0=East, 1=West
Longitude Degrees (8 bit) :

Value: 0-180 degrees
Longitude Minutes (6 bit) :
The integer part of the minutes of longitude.

Value: 0-60 minutes
Longitude Fraction (5 bit) :
The fractional part of the minutes of longitude in units of 0.04 minutes.

Value: 0-25
Spare (1 bit):
Value: 0
[Radius]
(2 bytes)
187
Radius (LSB)
Radius (MSB)
1
2
Byte
1
2
Byte

Figure 9.9: Radius format
The radius is used for the circle (type 1) zone only.

Value: 1-65535 km
[Width]
(2 bytes)
Width (LSB)
Width (MSB)
Figure 9.10: Width format
The width is used for the polyline (type 8) zone only.

Value: 1-65535 [units of 100m]
C.2.3 Checksum
The checksum is generated for each zone, from the fields as seen in Figure 9.11.
188

Figure 9.11 Generation of checksum

Zero field
Packet descriptor
(Variable size)
Ack reference
Zone Header
Zone data
(Variable size)
Fields used
for checksum
calculation
Checksum
Figure 9.12: Fields used to calculate chec ksum
Before checksum generation, zeros must be placed in the checksum field.
C.2.4 Sending the zone configuration poll

The zone configuration poll can be sent via PSDN, (refer to PSDN User Interface Manual
for more information), or by e-mail via a T&T Internet Gateway (IGW). Refer to the T&T
Internet Gateway manual.
The poll data are sent as a file attachment.
189

C.3 Examples of zone configuration polls

C.3.1 Example of a Circle Zone Poll
This is an example of making a poll containing a circle zone (zone type 1).
We want to make a circle zone with the following values:
Latitude: 55 deg 47.25 min N
Longitude:12 deg 31.70 min E
Radius:235 km
Reporting interval:2 hours
We want to place the zone as number 1 in the transceiver (zone no.=1).
As this is the first (and only) zone in the poll, ack reference=1.
Packet Descriptor:
Short Packet Descriptor since this is a circle poll. The length is 14=EH, so the packet
descriptor has the value 1EH.
Ack Reference:
As described above, the Ack Reference = 1.
Reporting Interval:
The reporting interval must be converted to frames. 10000 frames are sent every 24
hours in the Inmarsat-C system.
Calculation of reporting interval: 2hours = 2
833 = 0341H LSB=41H, MSB=03H
10000
frames 833 frames
24
Zone data:
The zone data consists of a position and a radius
We need to convert the minute decimals [1/100 minutes] in the position to the fraction
[4/100 minutes] in the position field. This is done easily by dividing by 4:
Latitudefraction =
25
6
4
Longitudefraction =
70
18
4
The position field is calculated as shown in figure 7.13.
190

Radius = 235 = 00EBH LSB=EBH, MSB=00H
Degrees
55
47
06
12
Latitude
31
E4
11 10 01 00
Spare
Hemisphere
C7
11 00 01 11
Fraction
C0
11 00 00 00
Minutes
Position
BC
10 11 11 00
Degrees
37
00 11 01 11
Hemisphere
Hex
Binary
Longitude
Fraction
Latitude
Minutes
Packet
Field
18
Longitude
Figure 9.13: Calculation of the position field
Checksum:
If calculated like described in C.2.3 , the checksum bytes will be:

CB1=A7H
CB2=C9H
Summary:
Figure 9.14 shows the exact data for the circle zone. The attachment file must consist of
this data.
191

Bit no.
8 7 6 5 4 3 2 1
Zone data
(7 byte)
Checksum
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
0
0
0
0
0
0
0
0
1
1
1
1
1
0
1
1
Byte
Zero field
0 0 0 1
Length
Ack reference
Zone no.
Zone type
Bit no.
8 7 6 5 4 3 2 1
0
0
0
0
0
1
0
0
0
1
0
0
1
0
0
1
0
0
0
0
0
0
0
1
1
0
0
1
1
0
1
0
0
1
0
0
0
0
0
1
1
0
0
0
0
0
0
0
0
1
0
0
0
0
0
0
1
0
1
0
1
0
0
1
0
1
0
0
0
0
0
1
1
0
1
1
0
0
1
0
0
1
0
0
0
0
1
1
0
0
1
0
1
0
1
0
0
0
1
1
1
1
1
1
0
1
1
0
1
0
1
1
Hex
00
1E
01
01
01
41
03
37
BC
C0
C7
E4
EB
00
A7
C9
H
H
H
H
H
H
H
H
H
H
H
H
H
H
H
H
Figure 9.14: Data Field for the circle zone poll
C.3.2 Example of a Polygon (type 4) Zone Poll

This is an example of making a poll containing a polygon zone with 3 positions (zone
type 2).
We want to make a polygon zone with the following values:
Position 1: 25 deg 46.45 min N, 80 deg 12.50 min W
Reporting interval: 30 minutes
Packet Descriptor:
Medium Packet Descriptor since this is a Polygon zone. The length is 22=16H, so the
packet descriptor has the value 8116H.
Ack Reference:
192

Reporting Interval:
Calculation of reporting interval: 30 min = 30
208 = 00D0H LSB=D0H, MSB=00H
1 10000
frames 208 frames

60 24
Zone data:
The zone data consists of three positions.
Position 1:
Latitudefraction =
45
50
11 , Longitudefraction =
13
4
4
Position 2:
Latitudefraction = 0 , Longitudefraction = 0
Position 3:
Latitudefraction =
18
21
5
4
4
The position field is calculated as shown in Figure 9.15.
193

11
Latitude
80
12
1A
00 01 10 10
Spare
46
Degrees
25
03
00 00 00 11
Hemisphere
Fraction
75
01 11 01 01
Minutes
Position
B9
10 11 10 01
Degrees
19
00 01 10 01
Hemisphere
Hex
Binary
Longitude
Fraction
Latitude
Minutes
Packet
Field
13
Longitude
Similarly the position 2 and 3 fields are calculated:

Position 2: 17 20 15 25 C0 H
Position 3: 18 94 B5 33 CA H
Checksum:

CB1=FAH
CB2=3EH
Summary:
Figure 9.16 shows the exact data for the polygon poll. The attachment file must consist
of this data.
194

Bit no.
8 7 6 5 4 3 2 1
Bit no.
8 7 6 5 4 3 2 1
Zone data
Checksum
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
0
1
0
0
0
0
1
0
0
1
0
0
0
0
0
0
0
1
0
1
1
0
1
1
0
Byte
Zero field
1 0 0 0 0 0 0 1
Length
Ack reference
Zone poll no.
Zone type
Figure 9.16: Data Field for the polygon zone poll
195
0
0
0
0
0
0
1
0
0
0
1
0
0
0
0
0
0
1
0
0
0
0
1
1
0
0
0
0
0
0
0
0
0
0
1
1
0
0
0
1
0
1
0
0
0
1
1
0
1
1
0
0
1
0
0
0
1
0
1
1
1
0
1
1
0
1
0
0
1
1
1
1
0
1
1
0
0
0
0
0
0
0
0
1
1
0
0
1
0
0
0
0
0
1
0
0
0
1
1
1
0
0
1
0
0
0
0
0
0
0
1
0
0
1
0
1
1
0
0
1
1
0
0
0
1
0
0
1
0
1
1
0
0
0
0
0
1
1
1
0
0
0
0
0
0
0
1
1
1
1
0
1
0
1
0
0
0
0
1
1
1
1
0
1
0
1
1
0
0
0
1
1
0
0
0
00
81
16
01
02
02
D0
00
19
B9
75
03
1A
17
20
15
25
C0
18
94
B5
33
CA
FA
3E
H
H
H
H
H
H
H
H
H
H
H
H
H
H
H
H
H
H
H
H
H
H
H
H
H

C.3.3 Example of a Polyline Zone Poll

This is an example of making a poll containing a polyline zone with 3 positions (zone
type 8).
We want to make a polygon zone with the following values:
Position 1: 35 deg 43.39 min S, 24 deg 32.61 min W
Width: 114 km
Reporting interval: 12 hours
Packet Descriptor:
Medium Packet Descriptor since this is a Polyline zone. The length is 24=18H, so the
packet descriptor has the value 8118H.
Ack Reference:
Reporting Interval:
Calculation of reporting interval: 12hours = 12
5000 = 1388H LSB=88H, MSB=13H
10000
frames 5000 frames
24
Zone data:
The zone data consists of three positions.
Position 1:
Latitudefraction =
39
61
15
4
4
196

Position 2:
Latitudefraction =
67
48
= 12
4
4
Position 3:
Latitudefraction =
18
47
12
4
4
The position field is calculated as shown in Figure 9.17.
10
24
Latitude
32
1E
00 01 11 10
15
Longitude
Similarly the position 2 and 3 fields are calculated:

Position 2: A0 8A 31 45 D8 H
Position 3: 9C 94 B0 FD 18 H
The width field has a unit of 100m in contrast to the radius field in the circle zone poll,
which has a unit of 1 km.
Width = 114km = 1140 [100m] = 0474H LSB=74H, MSB=04H
Checksum:

CB1=99H
CB2=94H
197
Spare
43
Degrees
35
88
10 00 10 00
Hemisphere
Fraction
51
01 01 00 01
Minutes
Position
AD
10 10 11 01
Degrees
A3
10 10 00 11
Hemisphere
Hex
Binary
Longitude
Fraction
Latitude
Minutes
Packet
Field

Summary:
Figure 9.18 shows the exact data for the polyline poll. The attachment file must consist
of this data.
Bit no.
8 7 6 5 4 3 2 1
Bit no.
8 7 6 5 4 3 2 1
Zone data
Checksum
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
0
1
0
0
0
0
1
0
1
1
0
1
0
1
1
0
0
1
1
1
1
1
0
0
0
1
1
Byte
Zero field
1 0 0 0 0 0 0 1
Length
Ack reference
Zone poll no.
Zone type
0
0
0
0
0
0
0
0
0
0
1
0
0
0
0
0
1
1
0
0
0
1
0
1
0
0
0
0
0
0
0
0
0
0
0
1
1
0
0
0
1
0
1
0
0
0
0
1
1
0
1
0
0
0
0
0
1
0
0
0
0
1
0
0
1
0
1
0
0
1
0
1
1
1
1
1
1
1
0
1
1
0
0
1
0
0
1
1
1
0
1
0
1
1
0
1
0
0
1
1
0
0
1
1
0
0
1
0
0
0
0
0
0
0
0
1
0
1
0
0
1
0
0
0
1
0
1
1
0
1
0
1
1
0
1
0
0
0
0
1
0
0
0
1
0
0
0
1
0
1
0
0
0
0
0
0
0
0
0
0
0
0
0
1
0
1
1
0
0
1
1
1
1
0
0
0
0
1
1
0
0
0
0
1
0
0
0
1
0
00
81
18
01
03
08
88
13
A3
AD
51
88
1E
A0
8A
31
45
D8
9C
94
B0
FD
18
74
04
99
94
H
H
H
H
H
H
H
H
H
H
H
H
H
H
H
H
H
H
H
H
H
H
H
H
H
H
H
Figure 9.18: Data Field for the polyline zone poll
C.4 Configuration poll Acknowledgement

When the transceiver has received the T&T Remote Configuration poll and if
acknowledgement is requested the transceiver returns an acknowledgement datareport. The acknowledgment data report for a poll is described in appendix I .
C.5 Packet format of the zone group selection poll

[2.21] To select between the configured zone groups or zone group lists the following
poll can be sent.
198

<Type dependent fields> ::= <group/group list number>
Data field of the

zone/zone group
selection poll
Bit no.
8 7 6 5 4 3 2 1
Zero field only in
beginnning of the data
field
Select
group/group list
command
Zero field
Packet descriptor
(Variable size)
Ack reference
Group/group list number
Fields used
for checksum
calculation
Checksum
16 bit
For explanation of fields see C.1 . Since there is just one command set the Ack
reference to 0x01. For explanation of Checksum field see C.2.3
199

Format of data from the data log

[ver 2.12]
Figure 9.19 illustrates the format of the data returned from the data log.
ID string: "3026EventLog" (12 bytes)

Version number = 0 (1 byte)
Request number (2 byte)
Sequence number (2 byte)
Mask of fields (4 bytes)
Header
Entry size (1 byte)

Mobile number (4 bytes)
Entry 1
Number of entries in the desired time interval

(3 bytes)
...
Number of entries returned (3 bytes)
Entry n
Field 1 (Event number)
...
Field 2 (Time of creation)
Entry m
...
Field p
Figure 9.19: Format when retrieving data from the data log.
<Returned data> = <Header><Entry>*
* = zero or more
D.1 Header format

<Header> = <ID string><Version number><Request number><Sequence
number><Mask of fields><Entry size><Mobile number><Desired entry count><Entry
count>
<ID string> = 3026EventLog
(12 bytes)
Identification string.
<Version number> = 1
(1 byte)
Log version number for now only one version is defined (The one described here). All
other version numbers are reserved for other formats.
200

<Request number>
(2 bytes)
This number is equal to the request number given when using a remote command to
retrieve the log over the satellite. The request number is equal to zero when the log is
retrieved locally.
<Sequence number>
(2 bytes)
This number is counted up every time some part of the log is retrieved locally or
remote.
<Mask of fields>
7
(4 bytes)
3
Mask byte 3
Mask byte 2
Mask byte 1
Mask byte 0
This mask identifies the fields included in the entries. The possible fields has each one
bit, if this bit is set to one the field is included in the entries.
Data fields
Byte
Bit
Time offset GPS
Position GPS
Speed GPS
Course GPS
I/O status
Distance tachograph
Speed tachograph
Extended Position GPS
Speed GPS in knots
The not used bits are reserved for future use.

<Entry size>
(1 bytes)
This is the size of each entry.

<Mobile number>
(4 bytes)
This is the mobile number of the transceiver.

<Desired entry count>
(3 bytes)
201

This is the number of entries in the log meeting the requirements given when asking for
the log data. When using local transfer this is equal to the number of entries returned.
But when using remote transfer (message sent over the satellite) there might not be
space for all the desired entries in the message.
<Entry count>
(3 bytes)
This is the number of entries actually returned.
D.2 Entry format

<Entry> = <Event number><Time of creation>[<Time offset GPS>][<Position GPS>]
[<Speed GPS>][<Course GPS>][<I/O status>][<Distance tachograph>][<Speed
tachograph>][<Extended Position GPS>][<Speed GPS in knots>]
<Event number>
(1 byte)
This is the number of the event causing the entry creation see Table 7.2.
<Time of creation>
(4 bytes)
This is the time of creation in seconds since 01-01-1970.

<Time offset GPS>
(2 bytes)
This is the time of the last known GPS data in second. It is an offset from the time of
creation.
If Time offset GPS < 65535 then
Time of last known GPS data = Time of creation - Time offset GPS
Else
The last known GPS data is older than: Time of creation - Time offset GPS
<Position GPS>
(6 bytes)
This is the last known GPS position in the following format:

7
Not used
S/N
...
Latitude degrees
S/N: 1 for South, 0 for North
Latitude Minutes
Latitude Minute Fractions
Not
W/E
used
Longitude degrees
...
Longitude Minutes
In units of 1/200 minutes
W/E: 1 for West, 0 for East
Longitude Minute Fractions
In units of 1/200 minutes
Data is invalid if all bits are set to one.

<Speed GPS>
(1 byte)
202

This is the last known GPS speed in km/h.

Data is invalid if equal to 255.
<Course GPS>
(1 byte)
This is the last known GPS course in units of 2 degrees.

Data is invalid if equal to 255.
<I/O status>
(1 byte)
This gives the status of the I/O pins:

7
Port value bitmap

Bit 0 :pin 2
Bit 1 :pin 3
Bit 2 :pin 4
Bit 3 :pin 5
Bit 4 :pin 6
Bit 5-7:reserved, set to 0
<Distance tachograph>
(4 bytes)
This is the total distance registered by the tachograph interface in units of 100 meters.
<Speed tachograph>
(1 byte)
This is the speed registered by the tachograph interface in km/h.

<Extended Position GPS>
(7 bytes)
This is the last known GPS position in 0,001 fractions of a minute and the HDOP value of
this position in fractions of 0,2.
S/N
Latitude degrees
S/N = 1 for South, 0 for North
Latitude Minutes
Latitude Minute Fractions
HDOP
W/E
W/E = 1 for West, 0 for East
Longitude degrees
Longitude Minutes
Longitude Minute Fractions
203

<Speed GPS in knots>
(2 bytes)
Speed in knots
This is the last known GPS speed in fractions of 0,1 knots.

204

Remote TBus 2 interface

[ver 2.12]
A remote interface (using TBus 2 format) is introduced in software version 2.12. A TBus
2 message is a data message with a special format that contains a sequence of
commands for the transceiver. TBus 2 will not be described in this document - contact
T&T service support.
Remote TBus 2 interface
205

SSA messages format

[ver 2.12]
SSA alert message:
----------- Covert/Security Alert Received ----------Mobile Terminal No
: 421960216
To CES
: 104
Position
: 55 47.61'N 012 31.40'E
Position updated
: 15:15 2004-06-09 UTC
Nature of distress
: Piracy/armed attack
Course
: 128
Speed : 0
Activation
: Covert/Security Alert
Position activated
: Yes
Course/Speed updated : Yes
-----------------------------------------------------Free text
++++
TEST SSA message:

----------- TEST TEST TEST TEST TEST TEST ----------Mobile Terminal No
: 421960216
To CES
: 104
Position
: 55 47.61'N 012 31.40'E
Position updated
: 15:41 2004-06-09 UTC
Nature of distress
Course
: 154
Speed : 0
Activation
Position activated
: Yes
-This message is for test purposes, please disregard-Free text
Covert message setup
Destination type
Address
Parameter
Usage
Destination type
Address
Parameter
Usage
Destination type
Address
Parameter
Usage
(changed recently):
: E-mail
: john_doe_0@tt.dk
:
: Msg+Test
: E-mail
: john_doe_1@tt.dk
:
: Msg
: E-mail
: john_doe_2@tt.dk
:
: Test
Activation
Repeat rate
Last update
: 30 sec. delay
: 35 min.
: 2006-07-13 11:13:22
++++
SSA messages format
206

Configuration changed SSA message:

---------------- CONFIGURATION CHANGE ---------------Mobile Terminal No
: 492388069
To CES
: 101
Position
: 55 47.60'N 012 31.40'E
Position updated
: 12:44 2004-06-10 UTC
Nature of distress
Course
: 034
Speed : 0
Activation
Position activated
: Yes
-This message is for test purposes, please disregard--
Covert message setup

Destination type
Address
Parameter
Usage
Destination type
Address
Parameter
Usage
Destination type
Address
Parameter
Usage
(changed recently):
: E-mail
: john_doe_0@tt.dk
:
: Msg+Test
:
:
:
:
:
:
:
:
Activation
Repeat rate
Last update
: 30 sec. delay
: 35 min.
: 2006-07-13 11:13:22
++++
F.1 Rules for future change of message format and

explanation of content:
Applications for automatic message type/content recognition must implement a certain
set of rules to support future changes/additions of the covert/security message format.
Note, the message header may differ depending on the type of message (email, fax,
telex, ect.). In addition, the land earth stations have no common header specification
covering one particular message type. No unambiguous format definition can be
applied to this section of the message.
The message can be extended in the following ways:
SSA messages format
Lines can be extended to hold more information. If lines are extended the new
information will be located after one or more spaces at the end of line.
Lines can be added after sections.
207

These rules are explained in the following sections in BNF (Backus-Naur Form /
RFC2234):
Only keywords will not be changed and can be used henceforward for automatic
analyses. [2.12]
The custom keywords are defined like this:
IC: Including control characters. Any 7-bit US-ASCII character, excluding NULL.
<%d01> - <%d127>
<future useIC> ::= <CHAR>*
EC: Excluding control characters. Visible printing characters including space.

<%d20> - <%d126>
<future useEC> ::= (<VCHAR> / <SP>)*
F.2 Start of message body

Messages are always composed of a message body header:
Keyworda ::= <"-">11 <SP> <"Covert/Security Alert Received"> <SP> <"-">11
Keywordb ::= <"-">11 <SP> <"TEST TEST TEST TEST TEST TEST"> <SP> <SP> <"-">11
Keywordc ::= <"-">16 <SP> <"CONFIGURATION CHANGE"> <SP> <"-">16
::= (<Keyworda> / <Keywordb> / <Keywordc>) <CR><LF>
F.3 Message body

Mobile number of terminal where message has originated. The mobile number is
composed of digits only:
Keyword ::= <"Mobile Terminal No">
::= <Keyword> <SP>* <%d58> <SP> <DIGIT>* [<SP> <future useEC >] <CR><LF>
CES, Coast Earth Station - also commonly refereed as a Land Earth Station (LES) defines the identifier of the land earth station which received the message.
Keyword ::= <"To CES">
::= <Keyword> <SP>* <%d58> <SP> <DIGIT>* [<SP> <future useEC >] <CR><LF>
The position is the last valid know position of the TT-3026. Note, that the resolution is
based on hundredth minutes.
Keyword ::= <"Position">
SSA messages format
208

::= <Keyword> <SP>* <%d58> <SP> <DIGIT>2 <SP> <DIGIT>2 <%d46> <DIGIT>2 _
<%d39> (<%d78> / <%d83>) <SP> <DIGIT>3 <SP> <DIGIT>2 <%d46> <DIGIT>2 <%d39> _
(%d69 / %d87) [<SP> <future useEC >] <CR><LF>
Keyword ::= <"Position updated">
::= <Keyword> <SP>* <%d58> <SP> <DIGIT>2 <%d58> <DIGIT>2 <SP> <DIGIT>4 _
<%d45> <DIGIT>2 <%d45> <DIGIT>2 <SP> <CHAR>* [<SP> <future useEC>] <CR><LF>
Nature of distress will always be set to 'Piracy/armed attack':

Keyword ::= <"Nature of distress">
::= <Keyword> <SP>* <%d58> <SP> <%d80> <%d105> <%d114> <%d97> <%d99> _
<%d121> <%d47> <%d97> <%d114> <%d109> <%d101> <%d100> <SP> <%d97> <%d116> _
<%d116> <%d97> <%d99> <%d107> [<SP> <future useEC>] <CR><LF>
Course and speed relates to the last known valid position. Speed is given in knots :
Keyword ::= <"Course">
::= <Keyword> <SP>* <%d58> <SP> <DIGIT>3 <SP>9 <%d83> <%d112> <%d101> _
<%d101> <%d100> <SP> <%d58> <SP> <DIGIT>* [<SP> <future useEC>] <CR><LF>
Activation will always be set to 'Covert/Security Alert':

Keyword ::= <"Activation">
::= <Keyword> <SP>* <%d58> <SP> <%d67> <%d111> <%d118> <%d101> <%d114> _
<%d116> <%d47> <%d83> <%d101> <%d99> <%d117> <%d114> <%d105> <%d116> _
<%d121> <SP> <%d65> <%d108> <%d101> <%d114> <%d116> [<SP> <future useEC>] _
<CR><LF>
Position activated and course/speed updated. Note, after course/speed updated, new
lines can be inserted:
Keyword ::= <"Position activated">
::= <Keyword> <SP>* <%d58> <SP> ( (<%d89> <%d101> <%d115>) / (<%d78> <%d111>) )
[<SP> <future useEC>] <CR><LF>
Keyword ::= <"Course/Speed updated">
SSA messages format
209

::= <Keyword> <SP>* <%d58> <SP> ( (<%d89> <%d101> <%d115>) / (<%d78> <%d111>) ) _
[<SP> <future useEC>] <CR><LF> [<future useIC>]
F.4 End of message body

Messages are always composed of a message body footer:
Keyworda ::= <"-This message is for test purposes, please disregard--">
Keywordb ::= <"-">54
::= (<Keyworda> / <Keywordb>) <CR><LF>
F.5 message supplementary text note

The message supplementary text note is optional.
::= [<CHAR>*] <CR> <LF>
F.6 trailing message configuration information:

The trailing message configuration information is always started with:
Keyword ::= <"Covert message setup (changed recently):">
::= <Keyword> <CR><LF>
Type of destination:
Keyword ::= <"Destination type">
<DestKey> ::= <Keyword> <SP>* <%d58> <SP> [( (<%d84> <%d101> <%d108> <%d101> _
<%d120>) / (<%d80> <%d83> <%d84> <%d78>) / (<%d80> <%d83> <%d68> <%d78>) / _
(<%d68> <%d78> <%d73> <%d68>) / (<%d83> <%d66> <%d67>) / (<%d69> <%d45> _
<%d109> <%d97> <%d105> <%d108> ) )] [<SP> <future useEC>] <CR><LF>
The address holds the destination address:

Keyword ::= <"Address">
<AddrKey> ::= <Keyword> <SP>* <%d58> <SP> [<VCHAR>*] [<SP> <future useEC>] _
<CR><LF>
The parameter field holds additional information required to use some addresses:
Keyword ::= <"Parameter">
SSA messages format
210

<ParamKey> ::= <Keyword> <SP>* <%d58> <SP> [<VCHAR>*] [<SP> <future useEC>]
<CR><LF>
Usage holds information regarding the use of a particular message address:

Keyword ::= <"Usage">
<UsageKey> ::= <Keyword> <SP>* <%d58> <SP> [(<%d77> <%d115> <%d103>) / _
(<%d84> <%d101> <%d115> <%d116>) / (<%d77> <%d115> <%d103> <%d43> <%d84> _
<%d101> <%d115> <%d116>)] [<SP> <future useEC>] <CR><LF>
The destination type, address, parameter and usage are repeated for each of the
addresses.
::= (<DestKey> <AddrKey> <ParamKey> <UsageKey> [(<future useEC> <CR><LF>)*])* _
[<SP> <future useIC>] <CR><LF>
F.7 End of message (message footer)

Message footer will marks the end of message:
Keyword ::= "++++"
::= <Keyword> <CR> <LF>
SSA messages format
211

DNID Download Confirmation Format

[2.14]
DNID download confirmation message example:
Manufacturer Initiated
DNID download confirmation
Mobile Fwd ID = 749341
ISN + s/n = 4TT0870b6f1d + 906405
DNID = 8048
DNID member number = 200
LES ID = 304
Download date = 2004-10-26
Description of the DNID download confirmation message format:
<Manufacturer Initiated><CR><LF>
<DNID download confirmation><CR><LF>
<Mobile Fwd ID = ><Forward ID><CR><LF>
<ISN + s/n = ><ISN>< + ><Serial no><CR><LF>
<DNID = ><DNID no><CR><LF>
<DNID member number = ><Member no><CR><LF>
<LES ID = ><LES no><CR><LF>
<Download date = ><Year><-><Month><-><Day><CR><LF>
[<Extension>]
<Forward ID>
Transceiver ID: A sequence of 1-8 digits.
<ISN>
The ISN number: 4TT followed by a sequence of 9 characters (digits and letters).
<Serial no>
Transceiver serial number: A sequence of 1-8 digits.
<DNID no>
DNID number: A sequence of 1-5 digits.
<Member no>
DNID member number: A sequence of 1-3 digits.
<LES no>
LES ID: A sequence of 1-3 digits.
<Year>
DNID insertion date: 4 digits
<Month>
DNID insertion month: 2 digits
<Day>
DNID insertion day: 2 digits
<Extension>
Future extensions: Lines with additional data can be added in the future.
DNID Download Confirmation Format
212

Packet Format of LES file

When a report is received by the Land Earth Station (LES) a DNID file is created from
the packet and placed in a DNID mailbox. The DNID file can then be forwarded to the
transceiver owners surveillance center via a terrestrial network (Telnet, email, X.25,
PSTN etc.).
The format of the DNID files can be different on different LESes and it can also depend
on the configuration of LES DNID account - contact the LES for details on account
configuration issues.
Thrane & Thrane recommends using API headers, which is a format that is widely
available. Figure 9.20 shows an overview of the format; if more information is required
please refer to reference [7] that is available from Thrane & Thrane or from the LES. The
content of the data report itself will follow directly after this header.
Byte
Content
Size
Description
01
1 byte
Indication of header start (EOH)
3 bytes
ASCII values for string "T&T"
&
01
i.e. byte values 54H,26H,54H
1 byte
Type of API header (01 for DNID

header)
22
1 byte
The length of this header in bytes
Msg. Ref. LSB
4 bytes
Message reference number
Msg. Ref. MSB
10
Presentation
1 byte
Receive alphabet from satellite

side message reception
11
LES ID
1 byte
LES ID, can be used for

identification of ocean region for
multi ocean LES's
12
Data Length LSB
13
Data Length MSB
14
Stored time LSB
15
The bytes given will be the
16
number of seconds since
17
Stored time MSB
18
DNID LSB
19
DNID MSB
20
Member number
2 bytes
Number of data bytes following

the header
4 bytes
Giving the time of message store.
January 1. 1970 0:0:0

2 bytes
The DNID of the file.
1 byte
Member number sent by the MES

in the position report
21
22 ..
02
1 byte
Indication of header end (STX)
Data
.. bytes
Position/data report or message
Figure 9.20: API header format
Packet Format of LES file
213

Acknowledgment Data report

The transceiver will respond with an acknowledgment data report after processing an
incoming poll, if acknowledgment is requested in the poll.
The general format of an acknowledgement data report:
<Acknowledgment> ::= [<API Header>]<Acknowledgment data>[<Extended result>]
The <API Header> is described in appendix H
<Acknowledgment data> ::= <Acknowledgment ID><Fixed value><Poll command>
<Reserved><Spare><Result code>
7
Acknowledgment ID
Poll command
Reserved
Spare
Result code
Figure 9.21: Acknowledgement data report Format

<Acknowledgment ID> (8 bits):
Acknowledgment identifier, see Figure 9.21.
<Fixed value> (1 bit):
Value: 1
<Poll command> (7 bits):
The poll command from the acknowledged poll, see 5.1.5 .
<Reserved> (1 byte):
Any value.
<Spare> (2 bytes):
For future use.
<Result code> (2 bytes):
The result code can be found in Table 9.17.
214

Result code
Description
Extended data
0000H
No description of the outcome of the poll is included.
No
0001H
No errors were encountered while processing the poll.
No
0002H
Illegal connection id.
No
0003H
Access denied
No
0004H
Missing poll data
No
0041H
One or more of the DNID(s) are not downloaded.
No
006CH
Acknowledgement result is placed in the extended result field.
Yes
0200H
Illegal poll type (individual, group or area)
No
0201H
Illegal LES
No
0203H
DNID congestion, no space for more DNIDs
No
0204H
Illegal response type
No
0205H
Illegal sub-address
No
0206H
DNID not active
No
0207H
Interval Program congestion, no space for more interval programs.
No
0208H
No interval program exists for the specified DNID
No
0209H
Data report queue congestion, no space for more data reports.
No
Table 9.17 Acknowledgement result codes

<Extended result> ::= [<Extended data for result code 6CH>]
depends on the result code see Table 9.17.
<Extended result for result code 6CH> ::= <Result1><Command no1>
[<Result2><Command no2>]...[<Result25><Command No25>]
Contain the result of every single command in a configuration poll:
7
Result1
Command no1
...
Result25
Command no25
Figure 9.22: Extended data for result code 6CH

<Result> (3 bits):
This is the result code of the configuration command.
Sub result
Meaning
No error - configuration performed correctly
Unknown command
Invalid number of parameters
No access
Not enough memory
No free space
Unspecified error
Table 9.18 Result codes for extended result field
215

<Command no> (5 bits):

This is the command number identifying the command in a configuration poll, see
appendix C .
216

INDEX
A
Abbreviations....................................................15
al command.......................................................68
Alarm .......................................................... 60, 68
Alert reporting ............................61, 102, 105, 173
Automatic login ........................................... 18, 96
Automatic ocean region shift .............................17
Automatic operations ........................................17
B
Baudrate ...................................................119, 120
BGPS status...................................................... 165
Bulletin Board error rate.................................. 132
C
cl command.......................................................70
Clear .................................................................70
Clock............................................................... 145
Closed Networks ............................................. 148
co command......................................................70
Command errors ............................................. 163
Command queue ............................................. 139
Command status reports ................................. 161
Confirmation ............................................. 70, 149
Covert/Security Alert ........................................60
Current channel .............................................. 132
Current protocol activity ................................. 132
D
da command......................................................71
Data................................................................. 149
Databits ....................................................119, 120
Datareport
Buffer ............................................................72
Byte count .....................................................72
Insert position ...............................................72
Datareport buffer......................................... 57, 72
Datareport, Sending ..........................................71
de 73
Delete file..........................................................73
di command ......................................................86
Distress status.................................................. 131
DNID Download.................................................52
E
EGC Network ID.............................................. 135
EGNOS ..............................................................23
ENID................................................................ 135
Environment variables .................................... 128
ERROR messages............................................. 161
ETX....................................................................15
H
Hardware status screen ................................... 143
he command......................................................92
Help ............................................................ 90, 92
I
I/O-pin ..............................................................92
Identification ................................................... 136
Incoming message .......................................... 109
INFO messages ............................................... 161
io command.......................................................92
ITA-2 ............................................................... 149
L
Land Mobile Alert........................................ 60, 68
Land station network table .............................. 136
Last commands................................................ 136
li command........................................................96
Link status ....................................................... 165
List all files.........................................................86
lo command................................................. 96, 98
Login .................................................................96
status........................................................... 132
Logout ...............................................................96
ls 86
M
Member Number............................................. 133
Message delivery reports ............................... 163
Message file .................................................... 147
Mobile number................................................ 136
Mobile Number ............................................... 127
MSAS .................................................................23
N
Nature of Distress ..............................................68
nc command......................................................99
NCS
Current ....................................................... 124
NCS channel......................................................99
NCS id ...............................................................99
NCS list............................................................ 123
Network table.................................................. 136
O
Ocean
Automatic shift ..............................................17
F
File
delete............................................................73
list .................................................................86
transfer........................................................ 147
type............................................................. 150
fx command.......................................................90
INDEX
GPS ......................................................23, 40, 110
217
P
Packed baudot ................................................ 149
Parity........................................................119, 120
pg.................................................................... 108
pg command ................................................... 102

Poll
address .........................................................52
command ......................................................53
response .......................................................54
Pollfile ...............................................................52
Polling and data reporting facility .....................51
Position............................................................ 125
Position format ................................................ 169
Position reporting.....................................102, 108
Close local connection ................................ 103
Default settings ............................ 105, 106, 107
Extended Program Set-up ....................104, 106
Initiate local connection .............................. 107
Overview of status....................................... 103
Program local connection ....................107, 108
Stop local connection .................................. 108
Power On ..........................................................17
Power-on statistics........................................... 137
Preferred ocean region ................................... 124
Prompt...............................................................15
PSTN destination.............................................. 148
PU/PA reporting ................................................56
R
Receive log ..................................................... 139
Receiving messages ........................................ 164
Regular position reporting .......................102, 108
Remote power switch ........................................36
Remote units.................................................... 110
Connected devices ..................................... 113
Display status .............................................. 110
Reporting ..........................................................51
ro command .................................................... 109
Routing of incoming message.......................... 109
ru command .................................................... 110
S
SBAS .......................................................23, 91, 92
Scan...................................................................18
Scanning.................................................... 99, 100
Serial console port parameters.................119, 120
Serial number.................................................. 136
Setup
Environment variables ................................ 128
Mobile Number ........................................... 127
NCS list ....................................................... 123
Position and Heading ...........................125, 126
Preferred Ocean Region ............................. 124
Serial Port.............................................119, 120
Speed Limits................................................ 127
Signal strength ................................................ 140
sl command ..................................................... 129
Sleep mode ..................................................... 129
Disable........................................................ 129
Setup ....................................................130, 131
Show status.................................................. 130
Software version.............................................. 143
Special Access Code destination..................... 148
Speed Limits.........................................40, 94, 127
st command ..................................................... 131
Status............................................................... 131
Channel Parameters.................................... 132
INDEX
218
Command queue......................................... 139

ENID information......................................... 135
Hardware status screen............................... 143
Latest Distress status ................................... 131
LES network table ....................................... 136
Power-on-statistics ...................................... 137
Receive log ................................................. 139
Show status report....................................... 136
Signal strength ............................................ 140
Software version.......................................... 143
Transceiver identification............................ 136
Transmit log ................................................ 141
Status screen ................................................... 143
Stop any protocol ..............................................70
Stopbits ....................................................119, 120
STX ....................................................................15
Synchronisation ............................................... 132
T
T&T position reporting .............................102, 108
Tachograph ............................................22, 33, 95
TDM
Channel number ......................................... 132
Frame number ............................................ 132
Origin ......................................................... 132
Type............................................................ 132
Terrestrial link................................................. 149
Test Mode........................................................ 126
ti 145
Time ................................................................ 145
Local time.................................................... 146
Set time ....................................................... 146
Show UTC time............................................ 146
Time of last login ............................................. 132
Time of last logout ........................................... 132
tr 147
Transfer ........................................................... 147
Binary.......................................................... 147
Transmission date ........................................... 149
Transmission time ........................................... 148
Transmit .......................................................... 147
Additional receiver information .................. 148
Confirmation ............................................... 149
Date ............................................................ 149
LES .............................................................. 148
Presentation at receiver end ....................... 149
Service ........................................................ 149
Terrestrial link ............................................ 149
Transmission time ....................................... 148
Transmit log .................................................... 141
Transmit service .............................................. 149
tx command..................................................... 147
ty 150
type ................................................................. 150
Binary.......................................................... 150
Keep.............................. 150, 155, 157, 159, 160
TZ variable ...................................................... 146
W
WAAS ................................................................23
Week schedule.......................................... 33, 150

TT3026 Software Reference Manual

Hochgeladen von

Dokumentinformationen

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

TT3026 Software Reference Manual

Hochgeladen von

Copyright:

Verfügbare Formate

TT-3026L/M/S/D/LM easyTrack Transceiver,

TT-3000SSA Ship Security Alert System and

Software Interface Reference Manual

Thrane & Thrane A/S

Copyright Thrane & Thrane A/S

TT-3026L/M/S/D/LM easyTrack Transceiver,

Software Interface Reference Manual

TT-3026L/M/S/D/LM easyTrack Transceiver,

Software Interface Reference Manual

Figure updated to reflect software ver. 2.19

GPS section added

Auto grouping description updated

Table updated with new data logging fields

Dn -f command extra precision for pos. upd.

Dn -p command extra precision for pos. upd.

Dn -tb command added give support for

GPS command added

Log -f command extended with new options

The option retxfail description has been upd.

binary user strings

Pg -fe command: An unused reserved field

New extended position precision field desc.

has replaced option remote.

New data logging fields described

Environment variable PRNFILTER added

Added zone group/group list selection poll

Added Route command

8.9.8 / 8.9.9 Message data reporting

Configuration poll messages.

SSA Covert Alert additional supplementary

SSA Covert Alert retransmission rate.

Updated for new power statistic entry

New options for auto creation of interval

Thrane & Thrane A/S

TT-3026L/M/S/D/LM easyTrack Transceiver,

Software Interface Reference Manual

2 General Transceiver Properties ..........................................17

TT-3026L/M/S/D/LM easyTrack Transceiver,

Software Interface Reference Manual

4 Data Reporting .................................................................29

5 Remote Configuration and Polling .......................................51

Land mobile alert............................................................................................60

TT-3026L/M/S/D/LM easyTrack Transceiver,

Software Interface Reference Manual

Maritime Distress alert....................................................................................60

7 The data-logging feature ....................................................64

Data logging is not supported by all transceivers ...........................................65

8 Command Reference .........................................................68

TT-3026L/M/S/D/LM easyTrack Transceiver,

Software Interface Reference Manual

8.9.11 DN -m Setup MEM codes to DNID-entry ..................................................82

TT-3026L/M/S/D/LM easyTrack Transceiver,

Software Interface Reference Manual

8.23.1 PG -a Set alert activation ....................................................................... 102

TT-3026L/M/S/D/LM easyTrack Transceiver,

Software Interface Reference Manual

8.29.1 SLEEP -c Disables Sleep Mode Operation ............................................ 129

TT-3026L/M/S/D/LM easyTrack Transceiver,

Software Interface Reference Manual

ZONE -al Set active zone group list ....................................................... 154

9 Info and Error Messages .................................................. 161

APosition Report Packet Format .......................................... 169

Packet Formats defined for the satellite link ................................................. 169

BDifferences in VMS configuration between TT-3022D and TT3026M 180