Вы находитесь на странице: 1из 48

COMPSB-TDG-SDT-002

EX-4132

Thorium VMS Satellite terminal


Up link/Down link Message Format
Specification

28th AUG 2008


KENWOOD

-0-

PREPARE PAR
VISA
Approuve PAR
APPLICATION
AUTORISEE PER

Name
Itakura
k.ono
Yatomi
M.GUIGUE

SIGLE
TOYO Technical
KENWOOD
Cubic-I
CLS

DIFFUSION
ORGANISME
TOYO Technical
KENWOOD

Cubic-I
CLS

DESTINATAIRES
Itakura
Tamura
A.SUZUKI
Shimada
Torii
Abe
Watanabe
Matuura
Himoto
YATOMI
M.GUIGUE

-1-

COPIES

DATE
14th MAY 2008
27th JUNE 2008
27th JUNE 2008

VERSIONS 1/3

VISA Gestion

Version
0.1

Date
27/04/2007
10/05/2007

1.0
1.1
1.2

18/06/2007
20/06/2007
22/06/2007

1.3

2/07/2007

Subject
Refer to CLS-DT-NT-06-369
Version:1rev2du20 mars 2007
Refer to CLS-DT-NT-06-369
Version:1rev3 du 24 avril 2007
1.5.3 Content of Request Technical message report
Added
status of DTE
Red
Red2
COMPSB-TDG-SDT-003
Thorium VMS satellite
terminal Up link/Down link Message Format Bit
arrangement detailed explanationis united to this
document.
1.1 Content of regular position format
Zone reference 5 bits Value range 0..20
Gps Status 3 bits 0..7
IridiumSignalQuality 3 bits 0..7
Min voltage on tx 6 bits 0..63
Current battery voltage 4 bits 0..15
Min external power supply 6 bits 0..63
Max external power supply 6 bits 0..63
number of times the power was off 4 bits 0..15
1.3 data logger
Number of positions in message range 1..18
1.4 Content of sensor data report
Status 1; "valid data"
1.5.1.2 Operation parameter
B1 field / Start day 9 bit: day 1..366
2.7.4 Configuration of zone data (polygon and circle)
Polygon Zone Id 5 bits range 1..20.
Circle Zone Id 5 bits range 1..20.
The page was added to the table of contents.
The item number was updated.
1.5.1=>2.3 TMT content added
1.5.3=>2.3.3 TMT content added
2.7 =>3.8 Zone management.
A notes addition of a the overlapped zones
- Maximum circle radius is changed
65000 Nautical Miles. => 8192 Nautical Miles.
- Description change which is the number definition
of the minimum points in the case of Poligon
2.7.4,=> 3.8.6 zone IDs changed 0..19.=>1...20
1.5.1.1 => 2.3.1.1Operation parameter [A]
A9 other anomaly 8 bits
1.5.1.2 => 2.3.1.2Operation parameter [B]
[B8] was added to B
2.6 => 3.6 Downlink Alert Message
"Message Count" of 8 bits at the beginning of the
message Content was added. Comment was added.
2.7=>3.8 add a command "Read one zone
report" with a command set to 0100
2.7.0.3=>2.3.5Read One Zone Report

-2-

VERSIONS 2/3
VISA Gestion

Version
1.3

Date
2/07/2007

Subject
APPENDIX:UP-date
[A1] Detailed Explanation of Bit Arrangement
[A1.1] Up-link Message Format
A1.1.1 Regular Position Report Format
A1.1.2 Sensor Data Report
A1.1.3 Operation Parameter [A] (Users Zone)A1.1.4 Operation Parameter [B] (CLS/Kenwood only
zone)
A1.1.5 Request Technical Message Report
[A2] Down-link Message Format
A2.1 Configuration of Zone Data (Polygon and
Circle)
A2.1.1 Polygon Zone Data
A2.1.2 Circle Zone Data
A2.2 Definition of Zones point
A-2-1: Polygon Zone
A-2-2:Circle zone
A-3:Explanation of overlapped processing

1.3.1

3/07/2007

1.4

11/07/2007

1.5
1.6

13/07/2007
18/07/2007

Page 12 2.1.1. State of unit change data


Page 21 2.3.3: The title changed " Technical Message
report"
Page 24 3.2.1 / second table: B field is 162 bits .Values of B
field are defined by B1 to B8
Page 26 3.7 Alert message: Message field length is 8*262
Page 27 3.8 Zone management: rename "Read Zone ID"
Page 29 3.8.2.1. In case of a detection of a zone
overlapping, status is
3.
Pages 18 2.3 (introduction) and 22 ( 2.3.5). rename "One
zone report"
Deletion after 45 pages
2.2 Sensor data report(Up-link format 3)
A1.1.2 Sensor Data report format changed.
2.2 Sensor data report(Up-link format 3)
A1.1.2 Sensor Data report format rechanged.

1.7

19/07/2007

1.8

21/07/2007

1. 9

24/07/2007

-3-

2.3.1.2 and A1.1.4 Operation Parameter[B]


B9 Battery operation time added.
2.2 Sensor data report interval added
2.1 Position report : origin of report
61
62added.
2.2 sensor data report field type Acquisition time of
sensor data deleted
2.3.1.2 and A1.1.4
B4
DSacq deleted.
3.3 Ping command message command
5added.
2.2 and A1.1.2 Sensor data field type Acquisition
time added.
2.3.1.2 and A1.1.4 Operation parameter [B] item
number rename.
2.3.3 Technical Message Report
TST information
IMEI number deleted
3.2. Setting Parameter Message table-1 DATA bits
length 312=>284
3.4 Thorium Ring Alert Message
Option
128bits=>8bits

VERSIONS 3/3
VISA Gestion

Version
2.0

Date
31/08/2007

2.1
2.2

21/09/2007
26/09/2007

2.3

01/10/2007

2.4

13/11/2007

2.5

07/04/2008

2.6

14/05/2008

Indication matter correction of the Factory


acceptance test at 16th April 2008.
2.3.1.1 Operation parameter [A] and
A1.1.3 operation parameter [B]
A1 DGPS report Main Power
Added [ All
0is invalid ]
2.3.1.2 Operation parameter [B] and
A1.1.5 operation parameter[B]
B4
GPS Duration
default value changed 30sec=>60sec
B7
Report default value changed
1=>0 only [A] format

2.7
2.8

27/06/2008
28/08/2008

FAINAL Ver
2.3.1.1 Operation parameter [A] A2 Remarks of DS
report changed.
A1.1.3 Operation parameter [A] A2 Remarks of DS
report changed.

-4-

Subject
1.1 Figure1.1 1.1-2 Item No modify

2.1.5.1 Definition of field


Data Log XX PART B
Spare Bits 2=>1 adjust bit length
2.3.1.1 Operation Parameter[A] A3 HDOP
0=>5 default 0=minimum Value
2.3.2 Free Form Text message [Header7]
=>[Header A]
2.3.3 technical Message Report
No3:55=>56
No6:4=>3
2.3.4 Thorium Message Downlink Management
2.5 =>2.3
3.2 setting Parameter Message No2:252=>284
Appendix
Part A Month July 01111=>0111
Latitude
110110111011110000000
=.>11011011101111000000
A1.1.5 Request Technical Message Report
No4:hh00101000(24h)=>00100011(23h)
[A2] latitude_y 110110111011110000000=>
11011011101110100000
2.3.4 TMDM Flag
3deletion
2.3.1.1 A2 Value invalidate
A6 comment added
A7
INmodify
A8 comment added
2.3.1.1 A2 Return Sensor Report Interval setting
A3 HDOP setting division.
2.3.4 Thorium Message Downlink management
No4 Adjustment
A1.1.3
A2 DS report Assistance Default
value Modify 5min=>60min.

Table of Contents
1. Introduction.............................................................................................................................................................................................- 8 1.1 Categorization of Up-link Message............................................................................................................................................... - 8 1.2 Down-link Message Format..........................................................................................................................................................- 10 1.3 Header Information ........................................................................................................................................................................ - 11 1.3.1 Up-link Message Header .......................................................................................................................................................... - 11 1.3.2 Down-link Message Header ..................................................................................................................................................... - 11 1.4 Up-link Message Categorization..................................................................................................................................................- 12 1.4.1 Up-link Format 1 ........................................................................................................................................................................- 12 1.4.2 Up-link Format 2 ........................................................................................................................................................................- 12 1.4.3 Up-link Format 3 ........................................................................................................................................................................- 12 1.4.4 Up-link Format 4 ........................................................................................................................................................................- 12 2. Up-link Message Format.....................................................................................................................................................................- 13 2.1 Position Report (Up-link Format 1) .............................................................................................................................................- 13 2.1.1 Content of Position Report........................................................................................................................................................- 14 2.1.2 Ping Answer with Regular Position Report [Header 7]............................................................................................................- 15 2.1.3 Ping Answer with Extended Position Report [Header 7].........................................................................................................- 15 2.1.4 Ping Answer with Tracking Replay Memory [Header 8].......................................................................................................- 16 2.1.4.1 Definition of field
GPS Position XX35
..................................................................................................................................- 16 2.1.5 Data Logger (Satellite Network Recovery) [Header 9]............................................................................................................- 17 2.1.5.1 Definition of field
Data Log XX35
.........................................................................................................................................- 18 2.2 Sensor Data Report (Up-link format 3) .......................................................................................................................................- 19 2.3 Other Up-link Message (Up-link Format 2, 4) ............................................................................................................................- 20 2.3.1 Parameter Setting Report [Header 0].......................................................................................................................................- 20 2.3.1.1 Operation Parameter [A] (Users Zone) .............................................................................................................................- 21 2.3.1.2 Operation Parameter [B] (CLS/Kenwood only zone).......................................................................................................- 22 2.3.2 Free Form Text Message [Header A], Email [Header 2], and E-form [Header 3]..................................................................- 22 2.3.3 Technical Message Report [Header 5].....................................................................................................................................- 23 2.3.4 Thorium Message Downlink Management (TMDM) [Header 6]............................................................................................- 24 2.3.5 Read one zone report [Header B] ............................................................................................................................................- 24 3. Down-link Message Format................................................................................................................................................................- 25 3.1 Basic Format of Down-link Message..........................................................................................................................................- 25 3.2 Setting Parameter Message [Header AA] ..................................................................................................................................- 26 3.2.1 Details of Operation Parameter ................................................................................................................................................- 26 3.3 Ping Command Message [Header BB] ......................................................................................................................................- 27 3.4 Thorium Ring Alert Message [Header AB].................................................................................................................................- 27 3.5 Free Form Text Downlink Message [Header AE], Email, and E-Form [Header CC, DD]....................................................- 27 3.6 Request Technical Expertise [Header AC].................................................................................................................................- 28 3.7 Downlink Alert Message [Header EE].........................................................................................................................................- 28 -5-

3.8 Zone Management Message [Header AD].................................................................................................................................- 29 3.8.1 Read Zone ID.............................................................................................................................................................................- 29 3.8.1.1 Acknowledgement to Command [Read Zone ID] ............................................................................................................- 29 3.8.2 Read One Zone Data................................................................................................................................................................- 30 3.8.3 Add Zone Data...........................................................................................................................................................................- 31 3.8.3.1 Acknowledgment of Command [ADD Zone Data] ...........................................................................................................- 31 3.8.4 Modify Zone Data ......................................................................................................................................................................- 32 3.8.4.1 Acknowledgment of Command [Modify Zone Data] ........................................................................................................- 32 3.8.5 Remove Zone Data ...................................................................................................................................................................- 33 3.8.5.1 Acknowledgment of Command [Remove Zone Data] .....................................................................................................- 33 3.8.6 Configuration of Zone Data (Polygon and Circle)....................................................................................................................- 34 APPENDIX .................................................................................................................................................................................................- 35 [A1] Detailed Explanation of Bit Arrangement ....................................................................................................................................- 36 [A1.1] Up-link Message Format..........................................................................................................................................................- 36 A1.1.1 Regular Position Report Format ............................................................................................................................................- 36 A1.1.2 Sensor Data Report ................................................................................................................................................................- 40 A1.1.3 Operation Parameter [A] (Users Zone)..................................................................................................................................- 41 A1.1.4 Operation Parameter [B] (CLS/Kenwood only zone) ...........................................................................................................- 43 A1.1.5 Request Technical Message Report......................................................................................................................................- 44 [A2] Down-link Message Format ...........................................................................................................................................................- 46 A2.1 Configuration of Zone Data (Polygon and Circle)..................................................................................................................- 46 A2.1.1 Polygon Zone Data .................................................................................................................................................................- 46 A2.1.2 Circle Zone Data .....................................................................................................................................................................- 47 -

-6-

This document describes details about "Message Content" specified by the following specification.
IRIDIUM
CLS-DT-NT-06-369
Version:1rev2 du 20 mars 2007
Nomenclature: IRID-SP-211-0004-CLS-courant

-7-

1. Introduction
The description of the message format is divided into several sub-sections for Up-link Message and
Down-link Message, respectively. The detailed explanation of bit field is given in the Appendix.

1.1 Categorization of Up-link Message


The Up-link message format is categorized into several groups shown in the figures below.
The detailed format of each message is described in 2.

2.1
Position Report
Format
1.4.1 Up-link Format 1
Header
1
,
7
,
8
,
9

2.1.1 Header
135
Regular Position Report

2.1.2/3 Header 34
7
Ping Answer
*Regular Position Report
*Extended Position Report

2.1.4 Header
835
Position Tracking Replay

2.1.5 Header
935
Data Logger

Figure 1.1-1 Up-link Format 1 Category

1.4.3 Up-link Format 2-1


Header
4

2.2 Header
435
Sensor Data Report
format

Figure 1.1-2 Uplink Format 2-1 Category

-8-

2.3 Other
Up-link
Message

2.3.3 Header
535
Request Technical
Message

2.3.1
Header
035

2.3..1..1
Operation Parameter
(1/2)

Parameter

1.4.4 Up-link
Format 3
Header
0
,
5
,
6

Setting
Report

1.4.2 Up-link
Format 2
Header
2
,
3
,
A
,
B

2.3.1.2
Operation Parameter
(2/2)

3.8.1.1
Acknowledgement
Add Zone Data

of

3.8.3.1
Acknowledgement
Modify Zone Data

of

3.8.5.1
Acknowledgement
Remove Zone Data

of

3.8.1.1
Acknowledgement of
Read Zone ID

2.3.4 Header
635
Thorium
Message
Downlink Management

2.3.2 Header
2,
3,
A35
Free Form Text Message

2.3.5 Header 34
B

Read One Zone Report

Figure 1.1-2 Uplink Format 2 & Format 3 Category

-9-

1.2 Down-link Message Format


The Down-link message format is organized shown in the below figure. The detailed format of each
message is described in 3.

Down-link

2.3.1.1 & 2.3.1.2


Operation
Parameter

3.2 Header
AA35
Setting Parameter

Message
Format

3.3 Header
BB35
Ping Command
3.4 Header
AB35
Thorium Ring Alert
3.5 Header
AE,
CC,
DD35
Free Form Text
3.6 Header
AC35
Request Technical Expertise

3.7 Header
EE35
Downlink Alert

3.8 Header
AD35
Zone Management

3.8.3
Add Zone Data

3.8.4
Modify Zone Data

3.8.6
Configuration of Zone Data

3.8.1
Read Zone ID

3.8.5
Remove Zone Data

Figure 1.2-1 Down-link Message Organization

- 10 -

1.3 Header Information


1.3.1 Up-link Message Header
Header(Hex)
0
1
2
3
4
5
6
7
8
9
A
B

Name
Parameter Setting Report
Position Data Report
E-Mail
E-Form
Sensor Data Report
Technical Message
Thorium Message Downlink Management
Ping Answer
Ping Tracking Replay
Data Logger
Free Form
Read One Zone Report

Abbreviation
PSR
PDR
EM
EF
SDR
TMR
TMDM
PAP
PTRP
DPDR
FFUM
ROZR

Note: Up-link message has 4 bits header field.

1.3.2 Down-link Message Header


Header(Hex)
AA
BB
AB
CC
DD
AC
EE
AD
AE

Name
Parameter Setting
Ping Command
Thorium Ring Alert
E-Mail
E-Form
Request for Technical Expertise
Downlink Alert
Zone Management
Free Form Downlink Text Message

Note: Down-link message has 8 bits header field.

- 11 -

Abbreviation
PSC
PIN
TRA
EM
EFM
EXP
ALT
ZM
FFDM

1.4 Up-link Message Categorization


There are following four kinds of Up-link formats.
Up-link format 1: The format of Position Data Report from TST
This Up-link format is most commonly used with TST
Up-link format 2: The format to send text message
Up-link format 3: The format exclusively for Sensor Data Report
Up-link format 4: The format which TST transmits with regards to Down-Link message reception

1.4.1 Up-link Format 1


Field Name
Header
Origin of Report

No
1
2

Content of Position Report

Bit Length
4
8

Variable

Value
1, 7, 8, 9
xx

Combination

Remarks

PART A
PART B
PART C
PART A + PART B + PART C
PART A + PART C

1.4.2 Up-link Format 2


No
1
2
3
4
5

Field Name
Header
Thorium Uplink Message Number (TMO)
Message Index
Total No. of Messages
Message Content

Bit Length
4
20
4
4
2668.

Value
2, 3, A, B
1 - 1048575
1 - 15
1 - 15
.

Remarks

1.4.3 Up-link Format 3


No
1
5

Field Name
Header
Message Content

Bit Length
4
2668.

Value
4
.

Remarks

1.4.4 Up-link Format 4


No
1
2
3
4
5
6

Field Name
Header
Thorium Uplink Message Number (TMO)
Message Index
Total No. of Messages
Thorium Downlink Message Number (TMT)
Message Content

- 12 -

Bit Length
4
20
4
4
20
2668.

Value
0, 5, 6
1 - 1048575
1
1
1 - 1048575
.

Remarks

2. Up-link Message Format


2.1 Position Report (Up-link Format 1)

No

Field Name

Bit Length

Header

Origin of Report

Value

Remarks

1, 7, 8, 9

1 = Regular Position Data Report


7 = Ping Answer
8 = Ping Tracking Replay
9 = Satellite Network Recovery

XX

00 : Regular Position Report


AF : Activation of Assistance
FA : Release of Assistance
FF : Assistance Mode
20 : GPS Antenna Disconnection
21 : GPS Loss
22 : Poor HDOP
23 : GPS Recovery
30 : Iridium Antenna Disconnection
31 : Low RSSI
*32:Satellite Network RecoveryLogger Data
40 : Terminal Power Up
41 : Terminal Power Down
42 : Last Message on Battery
10 : Terminal Entering a zone
11 : Terminal in a Zone
12 : Terminal Leaving a Zone
13 : Terminal Entering at a Port
14 : Terminal in a Port
15 : Terminal Leaving a Port
B0 : Ping Answer
B2 : Tracking Reply
50 : Intrusion Sensor
51 : Dome Dismounting
60 : Other Anomaly
61: PING A+B for NMFS
62:MO PDR for NMFS
PART A: Date, Location, GPS Report, Power Supply
PART B: House Keeping Data
PART C: Thorium Downlink Message Number (TMT)

Content
Report

of

Position
Variable

Combination of
Part A,B,C,A
,A
B.

*Regular Position Report : PART A + PART B


*Automatic Download of Data Logger
: PART A
+ PART B
*Answer to a Ping command using:
Regular Position Report : PART A + PART C
Extended Position Report:
PART A + PART B + PART C
Download of Tracking Replay Memory
PART A
+ PART C

*Origin of Report
62
: This report is performed when there is a Request to Send of DTE to Position.
This format is transmitted as up link as a response of "DPDR" DTE
command .

- 13 -

2.1.1 Content of Position Report


No

Field
Type

Field Name

Bit
Length

Year

015

Relative year starting from 2007


(2023 with 0 value)

Month

112

Month

Day

1.31

Day

Hour

0.23

Hour

Minute

0.59

Minute

Second

011

Second by 5 sec step

Latitude

21

018000000

Latitude by 0.0001 deg step

Longitude

22

03599999

Longitude by 0.0001deg step

Speed

063

Speed by o.5 knots step

Heading

0359

Heading by 1 deg step

GPS Position Report Interval

028

Report Interval: 5
,10
,15
,30
,45
min or
1 to 24 hours

Power Supply

0 or 1

Main : 0 Battery : 1

Working Duration on Battery

0127

In hours

Zone Reference

0.20

Zone ID, 0 (Out of Zone)

GPS Status

0.7

=1: No com. =2:No loc. =3: High HDOP


= 0 : Normal

No of Navistar in View

015

Number of Visible Navistar Satellite

Iridium Status (Network Status)

0 or 1

0 : Network Not Available 1 : Network


Available

Iridium Signal Quality (RSSI)

0.5

0, 1, 2, 3, 4, 5

Minimum Voltage on TX

063

Minimum Power on previous TX for


SBDIX command to answer from network.

Current Battery Voltage

015

Volt

063

063

Number of time the power was


off

0 or 1

Intrusion Sensor Flag

0 or 1

0 : Unit is Not Open 1: Unit is Open

Dome Dismounting Flag

0 or 1

0 : Mounted 1: Dismounted

State of unit

04

Reserve 0000

Spare Bits

Value

Remarks

PART A

PART B
Minimum
Supply

External

Power

Maximum
Supply

External

Power

PART C

Thorium Downlink Message


Number (TMT)

20

Adjustmen
t

Adjust Bit

Variable

1 - 1048575
all bit = 0

*Note: Refer to appendix A1.1.1 for the details of bits arrangement.

- 14 -

Minimum
External
Power
Supply
measured during the previous hour (app. 5
minutes sampling time)
Maximum External Power Supply
measured during the previous hour (app. 5
minutes sampling time)
number of time the power was OFF during
the past hour.(only 0 or1)

Adjust total bit length to multiples of 4


Total bit length does not exceed 2668 bits

2.1.2 Ping Answer with Regular Position Report [Header 7]


This format is used as an answer to a Ping command in conjunction with Regular Position Report.

No

Field Type

Field Name

Bit Length

Value

Header

Origin of Report

B0

PART A

PART C

Remarks

Date/Location/Speed/Heading
GPS Report Interval/Power Supply

92

2.1.1
Refer to
2.1.1 Refer to

Thorium Downlink Message Number


(TMT)

20

1-1048575

Origin of Failure

2.1.3 Ping Answer with Extended Position Report [Header 7]


This format is used as an answer to a PING command in conjunction with Extended Position Report
And It uses by response of PINGAB command added for NMFS. (19th JULY 2007)

No

Field Type

Field Name

Bit Length

Value

Header

Origin of Report

B0

Remarks

PART A

Date/Location/Speed/Heading
GPS report period/Power Supply

92

2.1.1
Refer to
2.1.1 Refer to

PART B

House Keeping Data

56

Refer to
2.1.1 Refer to
2.1.1

Thorium Downlink Message Number


(TMT)

20

1 - 1048572

PART C

Origin of Failure

- 15 -

2.1.4 Ping Answer with Tracking Replay Memory [Header 8]


This format is used as an answer to a PING command in conjunction with the tracking replay memory

Field
Type

No

Bit
Length

Field Name

Value

Remarks

Header

Origin of Report

B2

Message Index

115

Total Number of Message

115

1...29

Number of
Message

PART C

Positions

in

Position Report
B2 : Tracking Reply

GPS Position
XX(TYPE-A
)

92*n

Refer to
2.1.4.1

Thorium Downlink Message Number


(TMT)

20

1 - 1048575

0001= 1

0010= 2
:
:

1111= 15

0001= 1 message

0010= 2 messages
:
:

1111= 15 messages

00001= 1 position message

00010= 2 positions message


:

11101= 29 positions message

Origin of Failure

2.1.4.1 Definition of field


GPS Position XX
No

Field Type

PART A

Field Name

Bit
Length

Year

015

Relative year starting from 2007 (2023 with a 0


value)

Month

112

Month

Day

1.31

Day

Hour

0.23

Hour

Minute

0.59

Minute

Second

011

Second by 5 sec step

Latitude

21

018000000

Latitude by 0.0001 deg step

Longitude

22

03599999

Longitude by 0.0001deg step

Speed

063

Speed by o.5 knots step

Heading

0359

Heading in degree

GPS Report Interval

028

Report Interval: 5
,10
,15
,30
,45
, 1 to 24 hours

Power Supply

0 or 1

Main : 0 Battery : 1

Value

- 16 -

Remarks

2.1.5 Data Logger (Satellite Network Recovery) [Header 9]


No

Field Name

Bit Length

Header

Origin of Report

32(HEX)

Message Index

1...15

Total Number of Message

115

Position in Message

1...18

Data Log XX TYPE-A,TYPE-B

Spare Bits

148*n
1

- 17 -

Value
9

.
0

Remarks
1001 = Position Report
00110010=32H:
Satellite Network Recovery
0001 = 1
0010 = 2
:
1111 = 15
0001 = 1
0010 = 2
:
1111 = 15
00001 = 1
:
10010 = 18
N = Max 18

2.1.5.1 Definition of field


Data Log XX
No

Field
Type

Field Name

Bit
Length

Year

015

Relative year starting from 2007


(2023 will be refer with a 0 value)

Month

112

Month

Day

1.31

Day

Hour

0.23

Hour

Minute

0.59

Minute

Second

011

Second by 5 sec steps

Latitude

21

018000000

Latitude by 0.0001 deg step

Longitude

22

03599999

Longitude by 0.0001deg step

Speed

063

Speed by o.5 knots step

Heading

0359

Heading in degree

GPS Report Interval

028

Report Interval: 5
,10
,15
,30
,45
min
1 to 24 hours

Power Supply

0 or 1

Main : 0 Battery : 1

Working Duration of Battery

0127

in hours

Zone Reference

020

Zone ID if inside of the Zone. =0 : not refer

GPS Status

07

=1: no com. =2: No loc. =3: High HDOP


= 0 : Normal

No of Navistar Satellite in View

015

Number of Visible Satellite

Iridium Status
Availability)

0 or 1

0: Network Not Available


1: Network Available

Iridium Signal Quality (RSSI)

07

0,1,2,3,4,5

Minimum Voltage on TX

063

Minimum Power Supply Voltage on


previous TX from SBDIX command to
answer from network.

Current Battery Voltage

015

Volts

063

Maximum external power supply

063

Number of Power-off time

0 or 1

Intrusion Sensor Flag

0 or 1

0 : Unit is Not Open 1: Unit is Open

Dome Dismounting flag

0 or 1

0: Mounted 1: Dismounted

Unit Status

04

Reserve 0000

Spare Bits

Value

Remarks

PART A

PART B

Minimum
Supply

(Network

External

Power

- 18 -

Minimum
External
Power
Supply
measured during the previous hour (app. 5
minutes sampling time)
Maximum
External
Power
Supply
measured during the previous hour( app. 5
minutes sampling interval)
Number of power off time during the past
hour.(only 0 or 1)

(56bits)

2.2 Sensor Data Report (Up-link format 3)


Ref: TST-FCT-GEN-1702/T

No

Field Type

Field Name

Header

Header

Acquisition Time
of Sensor Data
1

Sensor
data
report Interval

Bit
Length

Value

Year

015

Month

112

Day

131

Hour

0...23

Minute

0...59

Time

Sensor Data 1

Sensor Data Report


Relative year starting from 2007
0: 2007

1bit+6bit

1bit+6bit 1bit: =0: min =1:hour


5,15,30,45 min and 1,2,3,24hours

Status

0 or 1

0: Data Invalid (Collection Error)


1: Data Valid

Value

12

03FF

10 bit A/D Value

Value

0 or 1

1or 0

Reserved

Analogue
4

Remarks

Digital I/O
Total Bit Length

4+31+15=50

Note: Refer to Appendix A1.4 for the details of bits arrangement.

- 19 -

2.3 Other Up-link Message (Up-link Format 2, 4)


No

Field Name

Header

Thorium Uplink Message Number


(TMO)

Bit Length

Value

20

Message Index

1..15

Total Number of Message

1..15

Content of Message

Remarks
x:
0000 = 0 : Parameter Setting Report
0010 = 2 : E-mail
0011 = 3 : E-Form
0101 = 5 : Technical Message Report
0110 = 6 : TMDM Message
1010 = A : Free Form Text Message
1011 = B :One Zone Report
1.1048575
0001 = 1
0010 = 2
0011 = 3
:
1111 = 15
0001 = 1
0010 = 2
0011 = 3
:
1111 = 15
0 : Parameter Setting Report
Refer to
2.3.1
2 : E-mail
Refer to 2.3.2

3 : E-Form
Refer to 2.3.2

5 : Technical Message Report


Refer to 2.3.3

6 : TMDM Message
Refer to 2.3.4

A : Free Form Text Message


Refer to 2.3.2

B : One Zone Report


Refer to 2.3.5

2.3.1 Parameter Setting Report [Header 0]


The below table corresponds to 34
Content of Messageof the table shown in
2.3 Other Up-link Message
,
when the message header filed is 0(HEX).
No

Field Type

Field Name

TMT

Thorium
Downlink
Message Number

Type

Origination

Data

Operation Parameter

Data

Zone
Management
Response

Adjustment

Adjust Bit

Bit Length
20

Value
1 - 1048575

0..3

v
(variable)

all bit = 0

- 20 -

Remarks
TST puts 34
0when transmitting independently

00
: Power on

01
: Response to Setting Message

10
: Response to Zone Management Message
Refer to
2.3.1.1 and 2.3.1.2 Operation
Parameter
if Origination = 2 v>0 else v=0

Refer to
3.8.1.1
or
3.8.3.1
or
3.8.4.1
or3.8.5.1
Adjust total bit length to multiples of 4
Total bit length does not exceed 2688 bits

2.3.1.1 Operation Parameter [A] (Users Zone)


No

Field Type

Field Name

Bit
Length

Defaul
t

Remarks

DGPS
Report

Main PWR

1+ 6 = 7

60min
(1hour)

1bit+6bit 1bit: =0: min =1:hour


5,15,30,45 min and 1,2,3,24hours
*All
0is invalid

Battery

1+ 6 = 7

60min

same with above

Assistant

1+ 6 = 7

5min

same with above

Port

1+ 6 = 7

60min

same with above

Zone

1+ 6 = 7

60min

same with above

Main PWR

1+ 6 = 7

60min
(1hour)

1bit+6bit 1bit: =0: min =1:hour 5,15,30,45 min


and 1,2,3,24hours

Battery

1+ 6 = 7

60min

invalidate

Assistant

1+ 6 = 7

60min

same with aboveMain PWR

Port

1+ 6 = 7

60min

same with above

Zone

1+ 6 = 7

60min

same with above

A1

A2

A3

A4

A5

A6

A7

A8

A9

DS Report
*Sensor
data report
interval

GPS-Failur
es Monitor

Iridium
Failure
Monitor
Power
Supply
Monitor

Zone
Manageme
nt

Port
Manageme
nt

Tamper
Proof
Detection
Other
Anomaly

ANT. disconnection

=0 : non monitor =1:monitor

Los of GPS fix

=0 : non monitor =1:monitor

HDOP monitor

=0 : non limitation =1:monitor

HDOP Limitation

1 to 64

GPS Recovery

=0 : non monitor =1:monitor

ANT. disconnection

=0 : non monitor =1:monitor

RSSI

=0 : non monitor 0< : minimum value (19)

Power-Up

Main Power -up

Power-Down

Main Power -down =0 : non monitor =1 : monitor


(= battery mode ON )

Last Message on
Battery (Shutdown)

=0 : non monitor =1 : monitor

Entering Zone

=0 : non mange =1 : manage

In a Zone

Mandatory (Only
1can be set up.).

Leaving a Zone

=0 : non mange =1 : manage

Stopping

=0 : non manage =1 : manage

IN

=0 : non mange =1 : manage

Leaving

=0 : non mange =1 : manage

300m

Intrusion Sensor

Mandatory (Only
1can be set up.).

Dome Dismounting

=0 : non monitor =1 : monitor

All
05 July 2007

------

12point

- 21 -

defult:5

=0 : non monitor =1 : monitor

management
s parameter : average of move
management
s parameter : number of GPS Point

th

2.3.1.2 Operation Parameter [B] (CLS/Kenwood only zone)


No

Field Type

ISU
Transmission

B1

B2

DGP Sacq

Sensor Data
report

B3

GPS
Data
Collection

B4

SBD Modem
Setting

B5

Field Name

Bit Length

Default

Remarks
7bits + 9bits
0: Any Day
7bits: Year 00..99
9bits: Day 1365
1.366
0: No Duration

Start Day

16

Duration

Stop

=1: Stop ON =0: OFF

Main PWR

1+ 6 = 7

5min

1bit+6bit
1bit 0: min 1:hour
6bits 5,15,30,45 min. or 1,2,3,24hours

Battery

1+ 6 = 7

30min

same with above

Assistant

1+ 6 = 7

5min

same with above

Port

1+ 6 = 7

5min

same with above

Zone

1+ 6 = 7

5min

same with above

Enable

Sensor Data repot


enable(Y)

Deport

Deport function : =0: sensor =1:option input

60sec

Max Interval of GPS Collection

=0: disable (=N) =1:

Interval

S112

Read only Modem S-register contents

S113

Read only Modem S-register contents

S121

Read only Modem S-register contents

S122

Read only Modem S-register contents

32

..

B6

ID

TID

B7

Report

Report
Selection

B8

Battery
operation time

Bo time

from
7

Read only Thorium ID

0= Position data format Type A

1= Position data format Type A + Type B

72hour

0000001=1hour

Note: Refer to appendix A1.5.1.1 and 1.5.1.2 for the details of bits arrangement.
*19th July 2007
B4sensor acquisition time setting deletion.

2.3.2 Free Form Text Message [Header A], Email [Header 2], and E-form [Header 3]
Ref: TST-FCT-GEN-2003/T
The below table corresponds to 34
Content of Messageof the table shown in
2.3 Other Up-link Message
,
when the message header filed is 7 (Free Form Text Message), 2 (E-mail), or 3 (E-Form).

No

Field Type

Field Name

Message

Text Message

Bit Length
8*336(max)

- 22 -

Value
ASCII text

Remarks
text area
variable length by byte

2.3.3 Technical Message Report [Header 5]


Ref: TST-FCT-GEN-1801/T
The below table corresponds to 34
Content of Messageof the table shown in
2.3 Other Up-link Message
,
when the message header filed is 5 (Request Technical Message Report).

No
1

Field Type
TMT

TST Information

Field Name

Bit Length

Value

Remarks

Thorium Downlink Message


Number

20

1 - 1048575

TST puts
0 when transmitting
independently.

Serial Number

64

Software
Version

3*8 = 24
3*8 = 24
3*8 = 24

00
...
99

01
...
12

01
...
31

ASCII character
ASCII character
ASCII character

XX_ZZ

5*8 = 40

00_01

ASCII character (Version Number)

Data of Regular Position Report PART B

RTC
4

YY/
MM/
DD/

Device Status

56

YY

4*2 = 8

MM

4*2 = 8

DD
hh
mm
ss

4*2 = 8
4*2 = 8
4*2 = 8
4*2 = 8

4bit*4bit BCD form

Status of Junction Box

1 or 0

1: Detected 0: Not Found

Status of DTE

1 or 0

1: On-line

Reserved

Reserved

Status

0 or 1

0: Data Invalid (Collection Error)


1: Normal

Value

12

01023

10 bit A/D value

Value

0 or 1

0 or 1

Reserved

Analog Data
5

Current
Data

Sensor

0: Off-line

Digital Data

Adjustment

Adjust Bit Length

all bit = 0

20+64+24*3+40+56+6*8+1+1+8+153=328 bit

Note: Refer to appendix A1.5.3 for the details of bits arrangement.

- 23 -

Adjust total bit length to multiples of


8
Total bit length does not exceed
2668 bits

2.3.4 Thorium Message Downlink Management (TMDM) [Header 6]


Ref: TST-FCT-GEN-1900/T
The below table corresponds to 34
Content of Messageof the table shown in
2.3 Other Up-link Message
,
when the message header filed is 6 (Thorium Message downlink Management (TMDM)).

No

Field Type

Field Name

Bit Length

Message Number

TMT

20

Flag

Reserved

Response to TRA
or
one of receiving text
message.

Value
1-..

015

Remarks
Downlink Message Number
0: ACK from DTE
1: NAK from TST
2: Request for downloading text message
upon TRA reception.
3: Invalid message received. 21/09/2007
4 14 : Reserved
15: ACK for Downlink Alert Message
Reserved

2.3.5 Read one zone report [Header B]


The below table corresponds to 34
Content of Messageof the table shown in
2.3 Other Up-link Message
,
when the message header filed is B (One Zone Report).

No

Field Type

Field Name

Bit Length

Message Number

TMT

20

Value
1-..

Zone Data

Zone Data

-----

Adjustment

Adjust Bit

all bit = 0

Remarks
Downlink Message Number
x polygon or circle
polygon: (11+43 * p) bits p: number of point
circle: 65 bits
refer to
configuration of each type
Adjust total bit length to make multiples of 8
total bit length do not exceed 2108 bits

Note: Refer to appendixA2.7.4.for the details of Zone data bits arrangement.

- 24 -

3. Down-link Message Format


3.1 Basic Format of Down-link Message
No

Bit
Length

Field Name

Header

Security Key

Thorium
Downlink
Number (TMT)

Message Index

1..15

Total Number of Message

1..15

Value

xx

Remarks
AA : Parameter Setting
BB : Ping Command
AB : Thorium Ring Alert Message
CC : E-mail
DD : E-Form
AC : Request for Technical Expertise
EE : Downlink Alert Message
AD : Zone Management Message
AE : Free Form Downlink Text Message

16
Message

20

1.1048575

AA : Parameter Setting
Refer to
3.2
BB : Ping Command
Refer to

AB : Thorium Ring Alert Message


Refer to

CC : E-mail
Refer to

DD : E-Form
Refer to

AC : Request for Technical Expertise


Refer to

EE : Downlink Alert Message


Refer to

AD : Zone Management Message


Refer to

AE : Free Form Downlink Text Message


Refer to

Content of Message

- 25 -

3.2 Setting Parameter Message [Header AA]


Ref: TST-FCT-GEN-2203/T
The below table corresponds to Content
34
of Messageof the table shown in
3.1 Basic Format of
Down-link Message, when the message header filed is 34
AA(Setting Parameter Message).

No

Field Type

Field Name

Command

Read or Write

Data

Operation Parameter

Adjustment

Adjust Bit

Bit Length
1
118 or 284
1

Value
0,1

all bit = 0

Remarks
0: Set Parameter
1: Read Parameter
Refer to
2.3.1.1 or 2.3.1.2
Details of
Operation Portion
Adjust total bit length to make multiples
of 4

*In "1" of read parameter command, two-itemdataportion is omitted.

3.2.1 Details of Operation Parameter


The following data applies to Users Zone.
No

Field Type

Field Name

[A]data

Operation Parameter

Bit Length
118

Value
A1-A9

Remarks
Refer to
2.3.1.1 Users Zone

The following data applies to CLS/Kenwood only Zone.


No

Field Type

Field Name

[B] data

Operation Parameter[A]

KEY

Key

[B] data

Operation Parameter[B]

Bit Length
118
32
134

- 26 -

Value
A1-A9

B1-B8

Remarks
Refer to
2.3.1.1 Users zone
Refer to
3.2.1 Details of operation
portion(??)
Refer to
2.3.1.2 CLS/Kenwood only
zone

3.3 Ping Command Message [Header BB]


Ref: TST-FCT-GEN-2303/T
The below table corresponds to 34
Content of Messageof the table shown in
3.1 Basic Format of Down-link
Message
, when the message header filed is 34
BB(Ping Command Message).
No

Field Type

Command

Option

Field Name

Bit Length

Value

Remarks

Ping Command

0...15

0000 = 0: Not Defined


0001 = 1: Request for Current Position
0010 = 2: Not Defined
0011 = 3: Request for Tracking Replay
0100 = 4: Not Defined
0101= 5 :Request for NMFS position
data A+B(PINGAB)
:
1111 = 15: Not Defined

Command Extension

Not Defined

3.4 Thorium Ring Alert Message [Header AB]


Ref.: TST-FCT-GEN-2401/T
The below table corresponds to Content
34
of Messageof the table shown in
3.1 Basic Format of
Down-link Message
, when the message header filed is
AB(Thorium Ring Alert Message).

No

Field Type

Field Name

Bit Length

Value

Remaining User
Message
to
Download

Count of Message

0...255

Option

Ring Alert Extension

Adjustment

Adjust Bit

0: No Pending Message
Not Defined

all bit =
0

Remarks

Adjust total bit length to multiples of 4


Total bit length do not exceed 2108 bits

3.5 Free Form Text Downlink Message [Header AE], Email, and E-Form
[Header CC, DD]
Ref: TST-FCT-GEN-2407/T
The below table corresponds to Content
34
of Messageof the table shown in
3.1 Basic Format of
Down-link Message
, when the message header filed is AE
3 4 (Free Form Text Downlink Message),
CC
(E-Mail), or
DD(E-Form).
No

Field Type

Field Name

Bit Length

Message
Count

Remaining User Message


to Download

0255

Reserved

Fill-in

Message

Text Message

8*262 (max)

- 27 -

Value

ASCII

Remarks

Adjust Byte Boundary


Text Area
Variable Length by byte

3.6 Request Technical Expertise [Header AC]


Ref: TST-FCT-GEN-2501/T
The below table corresponds to Content
34
of Messageof the table shown in
3.1 Basic Format of
Down-link Message
, when the message header filed is 34
AC(Request Technical Expertise).

No

Field Type

Reserved

Field Name

Option

Bit Length

Value

Remarks

0255

01: Reset Intrusion Sensor Flag


02: Reset Dome Dismounting Flag
03: Reset both of above two
Latest flag status is returned on the technical
message report.
00, 04255: Reserved

3.7 Downlink Alert Message [Header EE]


Ref : TST-FCT-GEN-2602/T
The below table corresponds to Content
34
of Messageof the table shown in
3.1 Basic Format of
Down-link Message
, when the message header filed is 34
EE(Downlink Alert Message).

No

Field Type

Field Name

Bit Length

MC

Message Counter

Reserved

Filler

Message

Text Message

8*262 (max)

Value

Remarks

0-255
0
ASCII

Adjust Byte Boundary


Text Area
Variable Length by byte

Note: If this message is received, TST will set 34


Fin the flag field of the format shown in 2.3.4, and will
transmit ACK response.

- 28 -

3.8 Zone Management Message [Header AD]


Ref: TST-FCT-DIR-2700/T
TST receives the following commands as a Zone Management Message.
Command
Read Zone ID
Read One Zone Data
Add Zone Data
Modify Zone Data
Remove Zone Data

ID
: 0000
: 0100
: 0001
: 0010
: 0011

3.8.1 Read Zone ID


The following is a down-link format of
Read Zone IDfrom a ground station to TST.
No

Field Type

Field Name

Bit Length

Command

Read Zone Data

Adjustment

Adjust Bit

Value

Remarks

0
all bit = 0

3.8.1.1 Acknowledgement to Command [Read Zone ID]


The following is an up-link format which TST answers in response to the command of 34
Read Zone ID
.
This data corresponds to the item No. 4 of the table shown in 2.3.1
Parameter Setting Report
.
No

Field Type

Field Name

Data Type

Response to Zone Data


Management

Command

Read Zone ID

Zone Data

Number of Zones

120

Number of Defined Zones

Zone ID

0....20

Programmed Zone ID

Status

03

Any values

all bit =
0

Data 1

Bit Length

Value

Remarks
Acknowledgment to Zone
Management Message.

Data

Data 2

.
Data n

Adjustment

Adjust Bit

- 29 -

Adjust total bit length to make


multiples of 4
Total bit length does not exceed 2108
bits

3.8.2 Read One Zone Data


The following is a down-link format from ground Station to TST for Reading One Zone Data.

No

Field Type

Field Name

Bit Length

Value

Command

Read One Zone

Zone Data

Zone Id

1..20

Adjustment

Adjust Bit

all bit = 0

Remarks

*TST does not send a usual ACK response with regards to this command. An Up-link message with
header
B(refer to 2.3.5) will be transmitted in stead. The zone data filed of the up-link message will be filled out
by the zone data specified by Read One Zone Command.

- 30 -

3.8.3 Add Zone Data


The following is a down-link format from ground Station to TST to add Zone Data.

No

Field Type

Field Name

Command

Add Zone Data

1: TST adds Zone Data

Zone Data

Number of data

120

Number of Zone Data to add.

Zone Data 1

Bit Length

Value

Remarks

-----

X: Polygon or Circle
Polygon: (11+43 * p) bits p: number of point
Circle: 65 bits
refer to
configuration of each type

all bit = 0

Adjust total bit length to make multiples of 4


Total bit length does not exceed 2108 bits

Zone Data 2
.
Zone Data n

Adjustment

Adjust Bit

Note: Refer to Appendix A2.7.4.for the details of Zone Data bits arrangement.

3.8.3.1 Acknowledgment of Command [ADD Zone Data]


The following is an up-link format which TST answers in response to the command of 34
Add Zone Data
.
This data corresponds to the item No. 4 of the table shown in 2.3.1
Parameter Setting Report
.
No

Field Type

Field Name

Bit Length

Data Type

Response to
Zone Data Management

Command

Add Zone

Zone Data

Number of Data

120

Number of Zone Data to Add.

020

Zone ID of Adding Zone.

03

0: OK
1: No Space to Add
2: Format Error
3 : Unused (overlapped)

Zone ID

Value

Data 1
Status
3

Data 2

The same as the above.

Data n
Adjustment

Adjust Bit

Acknowledgment to Zone Data Management

The same as the above.

Remarks

The same as the above.


k

- 31 -

all bit = 0

Adjust total bit length to multiples of 8.


Total bit length does not exceed 2668 bits.

3.8.4 Modify Zone Data


The following is a down-link format from ground Station to TST to modify Zone Data.
No

Field Type

Field Name

Bit Length

Command

Modify Zone Data

Zone Data

Number of Data

120

Zone Data 1

Value

Remarks

-----

X: Polygon or Circle
Polygon: (11+43 * p) bits p: Number of Point
Circle: 65 bits
Refer to
configuration of each type

all bit= 0

Adjusts total bit length to multiples of 4


Total bit length does not exceed 2108 bits

Zone Data 2
.
Zone Data n

Adjustment

Adjust Bit

Note: Refer to Appendix A2.7.4.for the details of Zone Data bits arrangement.

3.8.4.1 Acknowledgment of Command [Modify Zone Data]


The following is an up-link format which TST answers in response to the command of Modify
3 4 Zone
Data
. This data corresponds to the item No. 4 of the table shown in 2.3.1
Parameter Setting Report
.
No

Field Type

Field Name

Bit Length

Value

Data Type

Response to
Zone Data Management

Command

Zone Data Modify

Zone Data

Number of Data

120

Zone ID

1...20

Zone ID of Modifying Zone Data

Status

0..3

0: OK
1: No Zone ID
2: Format Error
3: Unused(overlapped)

Data 1

Remarks

Acknowledgment to Zone Data


Management Message.

Data 2
.
Data n

Adjustment

Adjust Bit

- 32 -

all bit= 0

Adjust total bit length to multiples of


8.
Total bit length do not exceed 2668
bits

3.8.5 Remove Zone Data


The following is a down-link format from ground Station to TST to remove Zone Data.
Bit
Length

No

Field Type

Field Name

Command

Remove Zone Data

Zone Data

Number of Data

120

Zone ID 1

120

Zone ID 2

120

120

Zone ID n

120

Adjust Bit

all bit = 0

Value

Remarks

Remove Zone Data of ID 1

Adjustment

Adjust total bit length to multiples of 4.


Total bit length does not exceed 2108 bits

3.8.5.1 Acknowledgment of Command [Remove Zone Data]


The following is an up-link format which TST answers in response to the command of 34
Remove Zone
Data
. This data corresponds to the item No. 4 of the table shown in 2.3.1
Parameter Setting Report
.
No

Field Type

Field Name

Bit Length

Data Type

Response to
Zone Data Management

Acknowledgment to Zone
Management Message.

Command

Zone Data Remove

Remove Zone Data

Zone data

Number of Data

120

1...20

Zone ID of Removing Zone Data

0..3

0: OK
1: No ID
2: Format Error
3 :Unused

Zone ID

Value

Data 1
Status
3

Remarks

Data

Data 2
.
Data n

Adjustment

Adjust Bit

- 33 -

all bit = 0

Adjust total bit length to multiples of 8.


Total bit length does not exceed 2668
bits

3.8.6 Configuration of Zone Data (Polygon and Circle)


When a zone is presented by a polygon,
43bits x number of pointsis necessary in one zone. In addition,
another 11bits are required to indicate ID, type, and the number of points.
Therefore, when the number of zone is one, it requires 11bits + 43bits x N, where N = 3 to 20;
3means that
the zone is triangle.
When the number of zone is 20 (the maximum number of zones), and each zone is presented by 20 points
polygon (the largest number), it requires 11 + (43 x 20) x 20 = 11 + 860 x 20 = 17,211 bits.
The one circle data requires 61 bits in total; 55 bits are used for presenting a circle, 6 bits are used for Zone ID
and Zone type.
When the number of zone is 20 (the maximum number of zone), and all of them are presented by a circle, it
requires 61 x 20 = 1220 bits.

No

Field
Type

Polygon

1.20

Zone Type
Number of Point

1
5

0
320

Point_1
Point_2

.
Point_n

Circle

Value

Zone ID

Point_0

Bit
Length

Field Name

Remarks

0: Polygon
Max 20

Longitude_x

22

03599999

01799999: East, 18000003599999: West

Latitude_y

21

01800000

Longitude_x

22

0899999: South, 9000001800000: North


Point0->Point1->Point2->->Point n
(Counter Clock-wise)

Latitude_y
Longitude_x
Latitude_y

21
22
21

Longitude_x

22

Latitude_y

21

Longitude_x
Latitude_y

22
21

Zone ID

1.20

Zone Type

1: Circle

Longitude_x

22

03599999

01799999: East, 18000003599999: West

Latitude_y

21

01800000

0899999: South, 9000001800000: North

Center
Radius

12

Total bits Polygon: 11 + (43 * n) * m


Circle : 61 * m

Nautical Mile: 12bit: 1.4095


(1Nautical mile=1852m)
max bit count -> 11+ (43 * 20) * 20 = 17,211 bits
max bit count -> 61 * 20 = 1,220 bits
1.4095

Note: Refer to Appendix A2.7.4.for the details of Zone data bits arrangement.

- 34 -

APPENDIX

- 35 -

[A1] Detailed Explanation of Bit Arrangement


[A1.1] Up-link Message Format
A1.1.1 Regular Position Report Format

No

Field Type

Field Name

Bit Length

Value

Year

015

Month

112

Day

1.31

Hour

0.23

Minute

0.59

Second

011

PART A

- 36 -

Remarks
Relative year starting from 2007
(2023 will be referred with 0)

0000
=2007 or 2023,,,,2007+16xN :N=1,2,3

0001
=2008 or 2024,,,,2007+16xN :N=1,2,3

0010
=2009 or 2025 ,,,2007+16xN :N=1,2,3

0011
=2010 or 2026,,,,2007+16xN :N=1,2,3

0100
=2011 or 2027,,,,2007+16xN :N=1,2,3

0101
=2012 or 2028,,,,2007+16xN :N=1,2,3

0110
-2013 or 2029,,,,2007+16xN :N=1,2,3

0111
=2014 or 2030,,,,2007+16xN :N=1,2,3

1000
=2015 or 2031,,,,2007+16xN :N=1,2,3

1001
=2016 or 2032,,,,2007+16xN :N=1,2,3

1010
=2017 or 2033,,,,2007+16xN :N=1,2,3

1011
=2018 or 2034,,,,2007+16xN :N=1,2,3

1100
=2019 or 2035,,,,2007+16xN :N=1,2,3

1101
=2020 or 2036,,,,2007+16xN :N=1,2,3

1110
=2021 or 2037,,,,2007+16xN :N=1,2,3

1111
=2022 or 2038,,,,2007+16xN :N=1,2,3
Month

0001
=January

0010
=February

0011
=March

0100
=April

0101
=May

0110
=June

0111
=July

1000
=August

1001
=September

1010
=October

1011
=November

1100
=December
Day

00001
=1

00010
=2

00011
=3
:
:

11110
=30

11111
=31
Hour

00000
=0

00001
=1

00010
=2
:
:

10111
=23
Minute

000000
=0min

000001
=1min

000010
=2min
:
:

111011
=59min
second by 5 sec steps

0000
=0sec

0001
=5sec

0010
=10sec

0011
=15sec

0100
=20sec

0101
=25sec

0110
=30sec

0111
=35sec

1000
=40sec

1001
=45sec

1010
=50sec

1011
=55sec

No

Field Type

Field Name

Bit Length

Value

Latitude

21

01800000

Longitude

22

03599999

Speed

063

Heading

0359

GPS Report
Interval

028

Power
Supply

0 or 1

PART A

- 37 -

Remarks
Latitude in 0.0001 deg step

000000000000000000000= S90.0000deg

000000000000000000001= S89.9999deg

000000000000000000010= S89.9998deg
:
:

011011011101110011111= S0.0001deg

011011011101110100000= 0.0000deg
(Equator)

011011011101110100001= N0.0001deg

011011011101110100010= N0.0002deg
:
:
110110111011101000000 = N90.0000deg
Longitude in 0.0001deg step
0000000000000000000000 = E0.0000deg
0000000000000000000001 = E0.0001deg
0000000000000000000010 = E0.0002deg
:
:
0110110111011110000000 = E180.0000deg
0110110111011110000001 = E180.00001deg
(W179.9999deg)
0110110111011110000010 = E180.0002deg
(W179.9998deg)
:
:
1101101110111001111111 = E359.9999deg
(W0.0001deg)
Speed in o.5 knots step

000000= 0.0knots

000001= 0.5knots

000010= 1.0knots
:
:

111110= 31.0knots

111111= 31.5knots
Heading in degree (Clockwise)

000000000= 0 degree

000000001= 1 degree

000000010= 2 degree
:
:

101100111= 359 degree


Report Interval 5
,10
,15
,30
,45
, 1 to 24 hours

00000= 5min

00001= 10min

00010= 15min

00011= 30min

00100= 45min

00101= 1 hours

00110= 2hours

00111= 3hours

01000= 4hours

01001= 5hours

01010= 6hours

01011= 7hours

01100= 8hours

01101= 9hours

01110= 10hours

01111= 11hours

10000= 12hours

10001= 13hours

10010= 14hours

10011= 15hours

10100= 16hours

10101= 17hours

10110= 18hours

10111= 19hours

11000= 20hours

11001= 21hours

11010= 22hours

11011= 23hours

11100= 24hours
Main : 0 Battery : 1

No

Field Type

Field Name

Bit Length

Value

Working duration
on battery

0127

Zone Reference

020

GPS Status

07

No of Navistar
Satellite in View

015

Iridium Status
(Network
Availability)

0 or 1

Iridium
Signal
Quality (RSSI)

05

Minimum Voltage
on TX

063

Current
Voltage

015

PART B

Battery

- 38 -

Remarks
in hours

0000000= no working
0000001= 1hour

0000010= 2 hours
:
:

1001000= 72 hours
:
:

1111111= 127hours
*Although a setup is possible till 127 hours, a
battery operation for 127 hours is not guaranteed.
Zone ID, 0: Out of Zone

00000= Out of Zone.

00001= Zone No1

00010= Zone No2

00011= Zone No

00100= Zone No
:
:

10100= Zone No20

000 = Location OK
001= no com

010= no location

011= Poor HDOP

100= Reserved
:
:
Number of Visible Satellite

0000= 0

0001= 1

0010= 2

0011= 3
:
:

1111= 15
0: Network Not Available
1: Network Available

000
=0

001
=1

010
=2

011
=3

100
=4

101
=5
Minimum Power Supply Voltage on previous TX
from SBDIX command to answer from network.

000000= 0V to 0.4V

000001= 0.5V to 1.4V

000010= 1.5V to 2.4V

000011= 2.5V to 3.4V


:
:

110111= 54.5V to 55.4V

111110= 61.5V to 62.4V

111111= No connection
*No Voltage beyond 55V in fact.

0000= 5.2V under

0001= 5.3V - 5.7V

0010= 5.8V - 6.2V

0011= 6.3V - 6.7V

0100= 6.8V - 7.2V


:
:

1101= 11.3V - 11.7V

1110= 11.8V - 12.2V

1111= 12.3V over

No

Field Type

Bit
Lengt
h

Field Name

Minimum
External
Power Supply

Value

063

Remarks
Minimum External Power Supply measured during
the previous hour (about 5 minutes sampling time)

000000= 0V - 0.4V

000001= 0.5V - 1.4V

000010= 1.5V - 2.4V

000011= 2.5V - 3.4V

110111= 54.5V - 55.4V

111110= 61.5V - 62.5V

111111= No connection
*No Voltage beyond 55V in fact.

PART B

Maximum External Power Supply measured during


the previous hour (about 5 minutes sampling time)
same as the above
Power OFF time during the past hour.

0000= No Power Off

0001= 1 time

0010= 2 times
:

1111= 15 times

Maximum External
Power Supply

063

Number of time the


power was off

0 or 1

Intrusion Sensor Flag

0 or 1

0: Unit is not open

1: Unit is open

Dome
Flag

0 or 1

0: Installed

1: Dismounted

04

Dismounting

State of Unit
Spare Bits
3

PART C

Thorium
Message
(TMT)

Adjustment

Adjust Bit

Downlink
Number

20
K

Reserve=0000

1 - 1048575
all bit = 0

- 39 -

Adjust total bit length to multiples of 4


Total bit length does not exceed 2668 bits

A1.1.2 Sensor Data Report


Ref: TST-FCT-GEN-1702/T
No

Field Type

Field Name

Header

Header

The acquisition
of the sensor

Bit Length
4

Year

015

Month

112

Day

131

Hour

0...23

Minute

059

Sensor
Data
report Interval

Status
Analog
Data
4

Value

0000000 to
1011000

Sensor data report


It is the same as that Year of A1.1.1
3 4 Content
Position ReportPART A
It is the same as that Month of 34
A1.1.1 Content
Position ReportPART A
It is the same as that Day of A1.1.1
3 4 Content
Position ReportPART A
It is the same as that Hour of A1.1.1
3 4 Content
Position ReportPART A
It is the same as that Minute of 34
A1.1.1 Content
Position ReportPART A
1bit + 6bit
MSB = 0: min MSB = 1: hour
5, 15, 30, 45 min and 1, 2, 3,24hours

000000035
= 0min

000000135
= 5min

0000010= 15min

0000011= 30min

0000100= 45min

1000001= 1hour

1000010= 2hour

1000011= 3hour
:
:

1011000= 24hour

0 or 1

0: Data Invalid (Collection Error)

Value

12

01023

10 bit A/D value

00000000000= 0
:

001111111111= 1023

Value

0 or 1

0 or 1

Reserved

Sensor Data 1
Digital
Data

Remarks

Total bit length

4+31+15=50

- 40 -

1: Normal

000000000001= 1
:

of
of
of
of
of

A1.1.3 Operation Parameter [A] (Users Zone)


No

Field Type

DGP Sreport

Bit
Length

Field Name

Default

Remarks

Main PWR

1+ 6 = 7

60min(1hour)

1bit+6bit *all
0is invalid
MSB = 0: min MSB =1:hour
5,15, 30, 45 min and 1, 2, 3,24hours

000000035
= 0min

000000135
= 5min

0000010= 15min

0000011= 30min

0000100= 45min

1000001= 1hour

1000010= 2hour

1000011= 3hour
:

1011000= 24hour

Battery

1+ 6 = 7

60min

same with above

Assistant

1+ 6 = 7

5min

same with above

Port

1+ 6 = 7

60min

same with above

Zone

1+ 6 = 7

60min

same with above

Main PWR

1+ 6 = 7

60min(1hour)

same with above

Battery

1+ 6 = 7

60min

invalidate

Assistant

1+ 6 = 7

60min

same with above (Main PWR)

Port

1+ 6 = 7

60min

same with above

Zone

1+ 6 = 7

60min

same with above

A1

A2

A3

DS report

GPS-failures
monitor

ANT. disconnection

0 (FIX)

= 0 : non monitor = 1 : monitor

Los of GPS fix

= 0 : non monitor = 1 : monitor

HDOP

= 0 : non monitor = 1 : monitor

000001=1
000101=5
011111=32
111111=64( It is select-able but invalidate)

monitor

HDOP Limitation value

A4

A5

Iridium failures
monitor

Power Supply
monitor

GPS recovery

= 0 : non monitor

= 1 : monitor

ANT. disconnection

0 (FIX)

= 0 : non monitor

= 1 : monitor

Zone
Management

0000 = 0 : non monitor 0< : minimum value


(15)
0001 = 1
0010 = 2
0011 = 3
0100 = 4
0101 = 5
Main Power -up
= 0 : non monitor = 1 :
monitor
Main Power -down = 0 : non monitor = 1 :
monitor
(= Battery mode ON )

RSSI value

Power-Up

Power-Down

= 0 : non monitor

Entering Zone

Mandatory = 0 : non monitor

In a Zone

Mandatory (Only
1can be set up.).

leaving a Zone

Mandatory = 0 : non monitor

Last
message
Battery(shutdown

A6

on

- 41 -

= 1 : monitor
= 1 : monitor

= 1 : monitor

No

A7

A8

A9

Field Type

Port
Management

Tamperproof
detection
Other
anomaly

Field Name

Bit Length

Default

Remarks

Stopping

= 0 : non manage

IN

Mandatory , (stop state)


(Only
1can be set up.).

Leaving

= 0 : non mange

= 1 : manage

00000000 = 0m
00000001 = 1m
:
:
011111111 = 255m
:
100100110 = 300m
111111111 = 511m
Management
s parameter : average of movement
00001 = 1 point
00010 = 2point
:
:
01100 = 12point
:
11111 = 31point
Management
s parameter : number of GPS Point

Intrusion Sensor

Mandatory (Only
1can be set up.).

Dome dismounting

= 0 : non monitor

00000000 : Non monitor


00000001 : Monitor not specified

------

300m

= 1 : manage

12point

- 42 -

= 1 : monitor

A1.1.4 Operation Parameter [B] (CLS/Kenwood only zone)


No

B1

B2

B3

B4

B5

Field Type

ISU
Transmission

DGPS acq

SenserData
report

GPS dur

SBD modem
setting

Field Name

Bit Length

Default

Remarks

Start Day

16

7bit+9bit : =0: any day


7bit: Year: 00..99
9bit : Day 1366

Duration

1.365

Stop

=1: Stop ON =0: OFF

Main PWR

1+6=7

5min

1bit+6bit 1bit: =0: min =1:hour


5,15,30,45 min and 1,2,3,24hours

Battery

1+6=7

30min

same with above

Assistant

1+6=7

5min

same with above

Port

1+6=7

5min

same with above

Zone

1+6=7

5min

same with above

enable

Sensor Data repot =0: disable (=N) =1: enable(Y)

DI port

Deport function : =0: sensor =1:option input

60sec

max duration of GPS collection


000000=0sec
000001=1sec
000010=2sec
:
:
011101=30sec
:
111111=63sec

duration

=0 : no duration

S112

Read only Mosem S-register contents

S113

Read only Mosem S-register contents

S121

Read only Mosem S-register contents

S122

Read only Mosem S-register contents

32

..

B6

ID

TID

B7

report

Report
selection

B8

Battery
Operation time

Bo time

from

72hour

- 43 -

Read only Thorium ID number

0
=position data format Type A

1
=position data format TypeA+TypeB
0000001=1hour
0000010=2hour

1001000=72hour

A1.1.5 Request Technical Message Report


No
1

Field Type
TMT

TST
Information

Field Name

Bit Length

Value

Remarks

Thorium Downlink Message


Number

20

1-1048575

TST inputs
0in the case transmitted
independently.

Serial Number

64

TBD

TBD

YY/

3*8=24

00
..to
99

MM/

3*8=24

01
..to
12

DD/

3*8=24

01
..to
31

XX_ZZ

5*8=40

00_01

55

Refer to
A1.1.1

Software
Version

Data of [regular position report PART B] is


here

YY

MM

RTC read out


4

ASCII character (create data)


30302F=00/
30312F=01/
:
39392F=99/
ASCII character
30312F=01/
:
31322F=12/
ASCII character
30312F=01/
30322F=02/
:
33312F=31/
ASCII character(version)
30305F3031=00_01
30305F3032=00_02
:
39395F3939=99_99

4*2=8

4bit*4bit BCD form


00000000=00 year
00000001=01
00000010=02
:
:
10011001=99

4*2=8

4bit*4bit BCD form


00000001=01(January)
00000010=02(February)
:
00010010=12(December)

DD

4*2=8

hh

4*2=8

mm

4*2=8

ss

4*2=8

4bit*4bit BCD form


st
00000001=01 1
nd
00000010=02 2
:
:
st
00110001=31
4bit*4bit BCD form
00000000=0h
:
00100011=23h
4bit*4bit BCD form
00000000=0min
:
01011001=59min
4bit*4bit BCD form
00000000=0sec
:
01011001=59sec

Device
Status

status of junction box

1or 0

1: attached 0: not found

status of DTE

1 or 0

1: on-line 0: off-line

reserved

Reserved

- 44 -

No

Field Type

Field Name

Bit Length

Value

Value

0 or 1

0: Data Invalid (Collection Error)


Normal
10 bit A/D value

00000000000
=

000000000001= 1
:

001111111111= 1023
0 or 1

Reserved

all bit = 0

Adjusts total bit length to multiples of 8.

Status

0 or 1

Value

12

01023

Analog Data
5

The current
Sensor Data

Digital Data
6

Adjustment

Remarks

Adjust Bit

- 45 -

1:

0
:

[A2] Down-link Message Format


A2.1 Configuration of Zone Data (Polygon and Circle)
A2.1.1 Polygon Zone Data
Field
Type

Field Name

Bit
Length

Value

Remarks

Zone ID

1.20

00001 to 10100

Zone Type

Number of Point

3 ..20

= 0: polygon
00011=3
:
:
10100=20 (max 20)
01799999 : East, 18000003599999 : West
longitude in 0.0001deg
0000000000000000000000 = E0.0000deg
0000000000000000000001 = E0.0001deg
0000000000000000000010 = E0.0002deg
:
:
0110110111011110000000 = E180.0000deg
0110110111011110000001 = E180.00001deg
(W179.9999deg)
0110110111011110000010 = E180.0002deg
(W179.9998deg)
:
:
1101101110111001111111 = E359.9999deg
(W0.0001deg)
0899999 : South, 9000001800000 : North
latitude in 0.0001 deg

000000000000000000000= S90.0000deg

000000000000000000001= S89.9999deg

000000000000000000010= S89.9998deg
:
:

011011011101110011111= S0.0001deg

011011011101110100000= 0.0000deg
(Equator)

011011011101110100001= N0.0001deg

011011011101110100010= N0.0002deg
:
:
(DBBA0h)

11011011101110100000= N90.0000deg
Same as point_0

Longitude_x

22

03599999

Latitude_y

21

01800000

Longitude_x
Latitude_y
Longitude_x
Latitude_y

22
21
22
21

Longitude_x

22

Latitude_y

21

Longitude_x
Latitude_y

22
21

Point_0
Polygon

Point_1
Point_2

.
Point_n
(Max20)

Same as point_0

Same as point_0
Same as point_0

- 46 -

A2.1.2 Circle Zone Data


Field Type

Field Name

Bit Length

Value

Zone ID

1.20

Zone Type

Longitude_x

22

03599999

Center Point
Circle

Latitude_y

Radius

21

01800000

12

1.4095

- 47 -

Remarks
00001 to 10100
=1: circle
01799999 : East,18000003599999 : West
longitude in 0.0001deg
0000000000000000000000 = E0.0000deg
0000000000000000000001 = E0.0001deg
0000000000000000000010 = E0.0002deg
:
:
0110110111011110000000 = E180.0000deg
0110110111011110000001 = E180.00001deg
(W179.9999deg)
0110110111011110000010 = E180.0002deg
(W179.9998deg)
:
:
1101101110111001111111 = E359.9999deg
(W0.0001deg)
0899999 : South, 9000001800000 : North
latitude in 0.0001 deg

000000000000000000000= S90.0000deg

000000000000000000001= S89.9999deg

000000000000000000010= S89.9998deg
:
:

011011011101110011111= S0.0001deg

011011011101110100000= 0.0000deg
(Equator)

011011011101110100001= N0.0001deg

011011011101110100010= N0.0002deg
:
:

11011011101110100000 = N90.0000deg
Nautical mile: 12bits: 14095 (1Nautical
mile=1852m)
000000000001 = 1mile
000000000010 = 2mile
:
:
111111111111 = 4095mile

Похожие интересы