TT-3027 TT98-147405-A Software Interface Reference Manual Command Reference 151 Zone 4.46.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> 4.46.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> 4.46.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 : zo -al 12<CR><LF> <CR><LF>
TT-3027 TT98-147405-A Software Interface Reference Manual Command Reference 152 Zone 4.46.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 600 frames Number of positions 5 Position 01: 55 44 37N 012 23 45E Position 02: 55 44 37N 010 23 46E Position 03: 55 44 37N 008 23 46E Position 04: 55 44 37N 006 23 46E Position 05: 00 00 00N 000 00 00W Width : 400.0 km 4.46.6 ZONE -DG_______________________________ DISPLAY ZONE GROUP CONFIGURATION Purpose: Displays a list of the zone groups stored in the MES. If a zone group number is specified, a list of the zones in that zone is displayed. Format: ZO -dg [<zone group no.>] Example : zo -dg<CR><LF> <CR><LF> Zone Groups:<CR><LF> Default Zone Group<CR><LF> Zone Group 1<CR><LF> Zone Group 2<CR><LF> Zone Group 11<CR><LF> Zone Group 12<CR><LF> Zone Group 37<CR><LF> Zone Group 128<CR><LF> Zone Group 129<CR><LF> Zone Group 130<CR><LF> Zone Group 137<CR><LF> Zone Group 155<CR><LF> Zone Group 228<CR><LF> Zone Group 229<CR><LF> Zone Group 230<CR><LF> Zone Group 231<CR><LF> Zone Group 232<CR><LF> Zone Group 233<CR><LF> Zone Group 255<CR><LF> 18 Zone Group(s)<CR><LF> <CR><LF>
TT-3027 TT98-147405-A Software Interface Reference Manual Command Reference 153 Zone 4.46.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: ZO -dl [<zone group list no.>] Example : zo -dl<CR><LF> <CR><LF> Zone Group Lists:<CR><LF> Zone Group List 1<CR><LF> Zone Group List 2<CR><LF> Zone Group List 13<CR><LF> Zone Group List 17<CR><LF> Zone Group List 31<CR><LF> Zone Group List 34<CR><LF> Zone Group List 75<CR><LF> Zone Group List 81<CR><LF> Zone Group List 112<CR><LF> Zone Group List 113<CR><LF> Zone Group List 114<CR><LF> Zone Group List 115<CR><LF> Zone Group List 116<CR><LF> Zone Group List 173<CR><LF> 14 Zone Group List(s)<CR><LF> <CR><LF> 4.46.8 ZONE -E ________________________________________ SET ENTER/EXIT EVENT FLAG Purpose: Enable or disable events entering or exiting a zone Format: ZO -e <zone no>,<Y|N> <zoneNo> <Y|N> Y=enable events, N=disable events Example Enable enterzonenumber 0 to send enter- ang exit zone events: : zo -e 0,Y<CR><LF> <CR><LF> 4.46.9 ZONE -EG ______________________________ SET ENTER/EXIT EVENT FLAG IN GROUP Purpose: Enable or disable events entering or exiting a zonegroup Format: ZO -eg <zonegroup no>,<Y|N> <zoneNo> <Y|N> Y=enable events, N=disable events Example Enable enter zonegroupnumber 0 to send enter- and exit zone events: : zo -eg 0,Y<CR><LF> <CR><LF>
TT-3027 TT98-147405-A Software Interface Reference Manual Command Reference 154 Zone 4.46.10 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> 4.46.11 ZONE -I ____________________________________CHANGE THE REPORTING INTERVAL Purpose: Add or change the reporting interval in a zone. Format: ZO -i <zonenumber>,<reporting interval> <reporting interval> = 0 keep the current interval <reporting interval> = 1 adobt the interval of the interval program <reporting interval> = 20..10000 Example zo -i 1,600<CR> 4.46.12 ZONE -IG _________________________________ SETUP INTERVAL FOR ZONE IN GROUP Purpose: Sets the reporting interval to be used when the MES is inside the specified zone. Format: ZO -ig <zone group no.>,<zone no.>,<reporting interval> <reporting interval> = 0 keep the current interval <reporting interval> = 1 adobt the interval of the interval program <reporting interval> = 20..10000 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. Example : zo -ig 2,9,2000<CR><LF> <CR><LF>
TT-3027 TT98-147405-A Software Interface Reference Manual Command Reference 155 Zone 4.46.13 ZONE -N _____________________________________________ CREATE A NEW ZONE Purpose: Create a new zone. Format: ZO -n <zonenumber>,<zonetype>[, <numberofpositions>] <Zonetype> Shape 1 Circle 2 Polygon with 3 positions 3 Polygon with 4 positions 4 Polygon with 5 positions 5 Polygon with 6 positions 6 Polygon with 7 positions 7 Polygon with 8 positions 8 Polyline with up to 40 positions 9 Polygon with up to 40 positions When a zone type 8 polyline is created the <numberofpositions> must be entered. Example zo –n 1,8,5<CR> 4.46.14 ZONE –NG ____________________________________________ADD ZONE TO GROUP Purpose: Creates a new zone of the specified type in the specified zone group. Format: ZO –ng <zone group no.>,<zone no.>,<zonetype>[,<no of positions>] <Zonetype> Shape 1 Circle 2 Polygon with 3 positions 3 Polygon with 4 positions 4 Polygon with 5 positions 5 Polygon with 6 positions 6 Polygon with 7 positions 7 Polygon with 8 positions 8 Polyline with up to 40 positions 9 Polygon with up to 40 positions 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> 4.46.15 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" <width> = "1" - "255"
TT-3027 TT98-147405-A Software Interface Reference Manual Command Reference 156 Zone Example zo -o 1,4000<CR> 4.46.16 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> 4.46.17 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 zo -p 1,1,55,44,37,n,12,23,45,e<CR>
TT-3027 TT98-147405-A Software Interface Reference Manual Command Reference 157 Zone 4.46.18 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> 4.46.19 ZONE -R _________________________________________________REMOVE A ZONE Purpose: Remove a zone. Format: ZO -r <zonenumber> <zonenumber> = "1" - "250" 4.46.20 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> :
TT-3027 TT98-147405-A Software Interface Reference Manual Command Reference 158 Zone 4.46.21 ZONE -RL ________________________________________ REMOVE ZONE GROUP LIST Purpose: Deletes the specified zone group list. Format: ZO -rl <zone group list no.> Example : zo -rl 173<CR><LF> <CR><LF> : 4.46.22 ZONE -S ____________________________________ GET THE CURRENT ZONE NUMBER Purpose: Displays the current zone status, i.e. the zone group number and zone number of the MESs current position. Format: ZO -s Example : zo -s<CR><LF> <CR><LF> Current Zone:<CR><LF> Zone Group: 1<CR><LF> Zone: 5<CR><LF> <CR><LF> : 4.46.23 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
TT-3027 TT98-147405-A Software Interface Reference Manual Command Reference 159 Zone 4.46.24 ZONE -TG _________________________________ TEST IF POSITION IS IN A ZONE GROUP Purpose: This command is used to test if a position is inside a zonegroup. Format: ZO –tg <zone groupno>,<lat deg>,<lat min>,<lat dsec>,<hemNS>, <lon deg>,<lon min>,<lon dsec>,<hemEW> The syntax is the same as in ZO -t 4.46.25 ZONE -U ____________________________________________ CHECK ALL ZONES NOW Purpose: Checks all the active zones immediately. Normally the MES checks only one zone per 10 seconds. This command updates the zone group number and zone number shown by the zone -s command. Format: ZO –u 4.46.26 ZONE -W ___________________________WAIT SEARCHING WHEN NEAR ZONE BORDER Purpose: When the MES either leaves or enters a zone, the next zone check can be configured using this command. This delay prevents an excessive amount of zone events that might otherwise occur if the MES is moving along or near a zone border. By default the configuration is set to 2 minutes. Format: ZO –w <sec> sec: 10..65536
TT-3027 TT98-147405-A Software Interface Reference Manual Info and Error Messages 160 Introduction 5 INFO AND ERROR MESSAGES 5.1 INTRODUCTION The following section gives an overview of the status reports that the MES might give, either as part of a message protocol, as part of a regular (daily) operation, or as an operation initiated by a LES. A report line like: 30"Login failed" will be stored in the status buffer as: INFO 30 : Login failed An error line like: 251“MES is no longer logged in” will be stored as: ERROR 251 : MES is no longer logged in The actual text of the status and error reports will be subject to modification by T&T, so an intelligent controller connected to the MES should only rely on the INFO and ERROR numbers given in the reports. 5.2 COMMAND STATUS REPORTS The following reports might be shown when using the built-in command set.
TT-3027 TT98-147405-A Software Interface Reference Manual Info and Error Messages 161 Command Status Reports 20 “Sending Distress failed” 21 ”Distress Acknowledgement received” 22 “Sending Distress Alert” 24 “Land mobile alert failed” 25 “Land mobile alert acknowledgement received” 26 “Sending land mobile alert” 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 ”Transmission failed.” 81 “Transmission successful” 82 “Transmission 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 “WARNING Test software. Inmarsat-C education version.\n” “Distress alert and distress message functionalities\n” “are disabled. Distress alert is simulated i.e.\n” “nothing is transmitted. Distress priority message\n” “transmission is not possible.” 117 “System powered up” 118 “STOP button pressed” 119 “Land Earth Station in Distress Generator has become invalid.” “\nMES will select one automatically.” 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”
TT-3027 TT98-147405-A Software Interface Reference Manual Info and Error Messages 162 Message Delivery Reports 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” 492 “Data report issued” 510 “Programmed report failed” 511 “Programmed report successful” 550 "No distress facility available" 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 "The system detected a distress alert being initiated.\n" \ "If this is a real distress then please release button\n" \ "and press the button again to initiate the alert.\n" \ "If a distress button is not currently activated there\n" \ "is a malfunction of the distress alert panel and the\n" \ "system must be switched off immediately and the wiring checked." 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 cknowledged” The user has cleared the distress alert indication. 1025 Initiated Distress Alert for LES ID, Table 5.1 Command Status Reports 5.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” "\n\n" "Destination <STX>%s File %s<ETX>" "\n" "Reference number %s" "\n" "%s Attempts" ", Land station gives failure code: %3s" 141 “Message delivery successful” "\n\n" "Destination <STX>%s File %s<ETX>" "\n" "Reference number %s" "\n" "%s Attempts" Table 5.2 Message Delivery Reports The following text is appended in the two cases:
TT-3027 TT98-147405-A Software Interface Reference Manual Info and Error Messages 163 Command Errors LES (number) Destination <STX>(number) File (filename)<ETX> Reference number (number) (number) Attempt(s), Land station gives failure code: (3 letter code) or LES (number) Destination <STX>(number) File (filename)<ETX> Reference number (number) (number) Attempt(s) The MES 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. 5.4 COMMAND ERRORS In Table 5.3 is a short explanation of each error. 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. 125 "Your MES is landmobile so this function is not allowed" 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 MES must be logged in when sending data reports. 250 "Not allowed to transmit as EGC receiver." 251 “MES is no longer logged in” 258 EGC reception in progress" New commands will not be accepted while the MES is receiving an EGC message (except for distress alerts). 259 "High Bulletin Board error rate." 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 5.3 Command Errors
TT-3027 TT98-147405-A Software Interface Reference Manual Info and Error Messages 164 Receiving Messages 5.5 RECEIVING MESSAGES When a message has been received one these report is given: 90 "Receiving message failed" 91 "Receiving message successful" INFO 91: Receiving message successful : File EGC.887 Message no. 31681 Priority 1 LES id 102 EGC service 31 INFO 413: EGCLOG updated Table 5.4 Receiving Messages Info's 5.6 GPS STATUS The built-in GPS may result in the following INFO message. 443 "GPS Test summary available" 463 "UTC was updated by GPS" The MES's hardware CMOS clock has been corrected to the received GPS UTC. Table 5.5 GPS Info's 5.7 GENERAL STATUS 127 "MES no longer logged in" 220 "Synchronization failed" 221 "Synchronization successful" 1013 "MES disk space below 32 Kbytes, files might be overwritten." Table 5.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 5.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). 5.8 LINK STATUS Whenever a link error occurs the originator of the message is stated: Message from MES:
TT-3027 TT98-147405-A Software Interface Reference Manual Info and Error Messages 165 Link Status or Message from LES: appear before the reason of the error. Only in case of non-delivery message codes like: LES gives error code: PRF can still be found, where PRF would stand for "Protocol Failure". These codes can not completely be eliminated as they can vary from LES to LES. In case a full explanation is wanted contact the LES operator. 5.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 "Message from Land Station: Call rejected: " 814 "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 MES is not logged in." "Your MES 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 5.8 LES Messages in case of a Pending/Rejected Call
TT-3027 TT98-147405-A Software Interface Reference Manual Info and Error Messages 166 Link Status LES MESSAGES IN CASE OF AN ABORTED CALL 813 "Message from Land Station: Call aborted: " followed by: "Did not receive your message." "MES did not follow call procedure." "Fatal Land Station error." "Call cleared by Land Station operator." "Call cleared by MES." "Land Station did not follow call procedure." "Land Station has detected MES error." "MES 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 5.9 LES Messages in case of an Aborted Call
TT-3027 TT98-147405-A Software Interface Reference Manual Info and Error Messages 167 Link Status MES MESSAGES "Message from MES:" 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 MES 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 "Your reception is OK, 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 "Your reception is OK, but your transmission is not received by Land Station." The MES tried to send the burst 9 times without success. 812 "Land Station did not respond to transmission request" The MES did not receive an assignment to send a message. 815 "Land Station did receive request, but did not respond to it." The MES timed out waiting for a response packet from the LES. 816 "Transmission aborted by operator." The user or the MES 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 MES tried 4 times to request message packets from the LES. 823 "Land Station did not finish message." The MES tried 4 times to end a message reception with the LES. 824 "Reception aborted by operator." The user or the MES 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 MES 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 MES 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.
TT-3027 TT98-147405-A Software Interface Reference Manual Info and Error Messages 168 Link Test Messages 853 "Expected Land Station was not found" The MES 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 MES 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 5.10 MES Messages 5.9 LINK TEST MESSAGES 70 Link Test failed. 71 Link Test finished 72 Link Test started 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 5.11 Link Test Messages 5.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 5.12 Test Mode Messages 5.11 SLEEP MODE 963 Turn off remote power to enter sleep mode 973 Waked Up Table 5.13 Sleep Mode Messages
TT-3027 TT98-147405-A Software Interface Reference Manual Position Report Packet Format 169 A Position Report Packet Format A.1 Packet Formats defined for the satellite link The position report format used for the Maritime or Land Mobile MESs 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>. Position reports with the following MEM-codes: 71 IO-Report will include <I/O status>. 72 Enter Zone will include <ZoneNo>. 89 Above Speed Limits will include <Speed and course>. <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 G <Position and Date> ::= <Maritime Position and date>|<Landmobile position and date> 7 6 5 4 3 2 1 0 H Lat. Degrees Lat. Minutes Lat. Min. Frac. H Lon. Degrees Lon. Minutes L.Min. Frac. Macro Encoded Msg. Attribute Attribute 7 6 5 4 3 2 1 0 H Lat. Degrees Lat. Minutes Lat. Min. Frac. H Lon. Degrees Lon. Minutes L.Min. Frac. Macro Encoded Msg. Attribute Attribute Reserved Reserved Reserved Reserved Speed Course Landmobile Maritime H = 1 for South, 0 for North H = 1 for West, 0 for East 0 0 0 1 1st Packet 2nd Packet Fraction is in units of 0.04 of a minute Figure 5.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)
TT-3027 TT98-147405-A Software Interface Reference Manual Position Report Packet Format 170 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. The next 5 bit indicate the hour of the day. The last 5 bits indicate minutes divided by 2. 1 st 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): 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)
TT-3027 TT98-147405-A Software Interface Reference Manual Position Report Packet Format 171 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) 2 nd 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> Month 7 6 5 4 3 2 1 0 Year Year Not used Figure 5.2 Date format 1 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>
TT-3027 TT98-147405-A Software Interface Reference Manual Position Report Packet Format 172 7 6 5 4 3 2 1 0 Spare Year Month Day Day Hour Minutes Minutes Not used Figure 5.3 Date format 2 Year (7 bit): Value: 0 - 99 (gives the year 1998 - 2097) 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 6 5 4 3 2 1 0 Spare Month Day Hour Hour Minutes Not used Year Figure 5.4 Date format 3 Year (12 bit): Value: 0 - 4095 (gives the year 0 - 4095) Month (4 bit): Value: 1 - 12 Day (5 bit): Value: 0 - 31
TT-3027 TT98-147405-A Software Interface Reference Manual Position Report Packet Format 173 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 MES type. The data report from the TT-3027C (provided the covert alert is disabled) and TT-3027SSA differs from the rest 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. Instead the I/O status for this MES 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. For TT-3027 C(covert alert disabled)/D/M/LT: The following data will be added to the data report in the free field: 7 6 5 4 3 2 1 0 Port value bitmap Tag = 3 Figure 5.5 I/O format for TT-3027 C(covert alert disabled)/D/M/LT 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-3027 C(covert alert enabled)/SSA: The following data will be added to the data report in the free field: 7 6 5 4 3 2 1 0 Port value bitmap Tag = 70 Figure 5.6 I/O format for TT-3027 C(covert alert enabled)/SSA
TT-3027 TT98-147405-A Software Interface Reference Manual Position Report Packet Format 174 Port value bitmap (1 byte): 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. 7 6 5 4 3 2 1 0 Speed in km/h Tag = 65 Course in degrees Reserved Figure 5.7 Speed and course Zone number <ZoneNo> ::= <Tag><Zone number > The following data will be added to the position report in the free field:
TT-3027 TT98-147405-A Software Interface Reference Manual Position Report Packet Format 175 7 6 5 4 3 2 1 0 Zone number Tag = 66 Figure 5.8 I/O format for TT-3027 C(covert alert enabled)/SSA User string <User string> ::= <Tag><String-length><String> The following data will be added to the position report in the free field: 7 6 5 4 3 2 1 0 String-length Tag = 67 String ..... Figure 5.9 User stiring 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. 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: The following data will be added to the position report in the free field:
TT-3027 TT98-147405-A Software Interface Reference Manual Position Report Packet Format 176 Sign Lat. Tag = 68 7 6 5 4 3 2 1 0 Offset Lat. Sign Lon. Offset Lon Figure 5.10 Extra position precision0.005 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.> If <Sign Lat.> = 1 then <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: The following data will be added to the position report in the free field: 7 6 5 4 3 2 1 0 Tag = 71 Sign Lat. Sign Lon. Offset Latitude Offset Longitude GPSQ HDOP Figure 5.11 Extra position precision0.001 The precise latitude position is calculated in the following way: If <Sign Lat.> = 0 then <Lat. Min. Frac. In 1000 of a minute> = 40*<Lat. Min. Frac.> + <Offset Latitude> If <Sign Lat.> = 1 then <Lat. Min. Frac. In 1000 of a minute> = 40*<Lat. Min. Frac.> - <Offset Latitude> 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
TT-3027 TT98-147405-A Software Interface Reference Manual Position Report Packet Format 177 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 : 2D fix 1 : 3D fix 2 : 3D fix + SBAS reception The HDOP field indicates the assumed quality of the GPS position. It is coded into the following values: 0 : HDOP 2 1 : 2 < HDOP 5 2 : 5 < HDOP 10 3 : 10 < HDOP Tachograph data <Tachograph data> ::= <Tag><Travelled distance><Last park time offset><Last start time offset> The following data will be added to the position report in the free field: Figure 5.12 Tachograph data 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. Sub-address = 69 7 6 5 4 3 2 1 0 Travelled distance Last start time offset Last park time offset
TT-3027 TT98-147405-A Software Interface Reference Manual Position Report Packet Format 178 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)
TT-3027 TT98-147405-A Software Interface Reference Manual Position Report Packet Format 179 A.2 T&T Data report format Instead of the Inmarsat defined packet format a special T&T data report format can be used. The T&T Data report format is shown in Figure 5.13. 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. P Z E/L Latitude in units of 5 Seconds Speed in unit of 5 km/h Heading in units of 45 degrees Longitude in units of 5 Seconds Time in unit of 10 minutes P = Panic indicator Z = Zone crossing indicator E/L = Enter/Leave zone indicator 1 0 1 1 0 0 0 0 7 6 5 4 3 2 1 0 Figure 5.13 T&T´s 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.
TT-3027 TT98-147405-A Software Interface Reference Manual Position Report Packet Format 180 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 isn’t supported by the used LES or in case message data reporting is selected as the protocol for the used DNID, see DN -g. The format of a message data report can be seen in the figure below: Figure 5.14 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. 7 6 5 4 3 2 1 0 DNID Ocean LES ID Member Number Data ...
TT-3027 TT98-147405-A Software Interface Reference Manual Packet format of the configuration poll 181 B Packet format of the configuration poll The configuration poll is used for remote configuration. The poll command for the configuration poll is 6CH. B.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): Figure 5.15 Short packet descriptor The medium packet descriptor (2 bytes): Figure 5.16 Medium packet descriptor <Command type> (3 or 6 bits): The type of command to be performed, please see Table 5.14. Command type Description 1 Zone configuration 2 Zone group selection 3 Zone group list selection Table 5.14: 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): 7 6 5 4 3 2 1 0 0 Command type Length 7 6 5 4 3 2 1 0 Length 1 0 Command type
TT-3027 TT98-147405-A Software Interface Reference Manual Packet format of the configuration poll 182 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. Figure 5.17 Ack reference Sub Command no: Legal values are 1-31. <Type dependent fields> Depends on the command type. B.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>] 7 6 5 4 3 2 1 0 0 0 0 Command no
TT-3027 TT98-147405-A Software Interface Reference Manual Packet format of the configuration poll 183 8 7 6 5 4 3 2 1 Bit no. Data field of the zone configuration poll Zero field Ack reference Zone no. Zone type Reporting interval LSB Reporting interval MSB Checksum Zone data (Variable size) 1st zone in poll Packet descriptor (Variable size) Ack reference Zone no. Zone type Reporting interval LSB Reporting interval MSB Checksum Zone data (Variable size) Packet descriptor (Variable size) 2nd zone in poll Zero field only in beginnning of the data field Maximum number of zones is 27, but delimited by the maximum packet size of 213 bytes Fields used for checksum calculation Fields used for checksum calculation Figure 5.18 Zone poll data.
TT-3027 TT98-147405-A Software Interface Reference Manual Packet format of the configuration poll 184 B.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 MES. 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) B.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 1 Circle [Pos][Radius] 2 Polygon with 3 positions [Pos1] [Pos2] [Pos3] 3 Polygon with 4 positions [Pos1] [Pos2] [Pos3] [Pos4] 4 Polygon with 5 positions [Pos1] [Pos2] [Pos3] [Pos4] [Pos5] 5 Polygon with 6 positions [Pos1] [Pos2] [Pos3] [Pos4] [Pos5] [Pos6] 6 Polygon with 7 positions [Pos1] [Pos2] [Pos3] [Pos4] [Pos5] [Pos6] [Pos7] 7 Polygon with 8 positions [Pos1] [Pos2] [Pos3] [Pos4] [Pos5] [Pos6] [Pos7] [Pos8] 8 Polyline with up to 40 positions [Pos1]…[Pos40][Width] 9 Polygon with up to 40 positions [Pos1]…[Pos40] Table 5.15: 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:
TT-3027 TT98-147405-A Software Interface Reference Manual Packet format of the configuration poll 185 [Pos] (5 bytes) 1 2 3 4 5 Byte 8 7 6 5 4 3 2 1 Bit no. H Lat. Degrees Lat. Minutes H S Lon. Lon. Lon. Frac. Lat. Frac. Degrees Min. Figure 5.19 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
TT-3027 TT98-147405-A Software Interface Reference Manual Packet format of the configuration poll 186 [Radius] (2 bytes) Radius (LSB) Radius (MSB) 1 2 Byte Figure 5.20 Radius format The radius is used for the circle (type 1) zone only. Value: 1-65535 km [Width] (2 bytes) Width (LSB) Width (MSB) 1 2 Byte Figure 5.21 Width format The width is used for the polyline (type 8) zone only. Value: 1-65535 [units of 100m] B.2.3 Checksum The checksum is generated for each zone, from the fields as seen in Figure 5.22.
TT-3027 TT98-147405-A Software Interface Reference Manual Packet format of the configuration poll 187 Figure 5.22 Generation of checksum Zero field Ack reference Checksum Zone data (Variable size) Packet descriptor (Variable size) Fields used for checksum calculation Zone Header Figure 5.23 Fields used to calculate checksum Before checksum generation, zeros must be placed in the checksum field. B.2.4 Sending the zone configuration poll The zone configuration poll can be sent via: e-mail. Please see [1] TT 99-110036, Internet Gateway User Manual PSDN. please see [2] TT 99-103879, PSDN User Interface Manual The poll data are sent as a file attachment.
TT-3027 TT98-147405-A Software Interface Reference Manual Packet format of the configuration poll 188 B.3 Examples of zone configuration polls B.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 MES (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: hours frames 833 frames 24 10000 2 2 833 = 0341H LSB=41H, MSB=03H 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: 6 4 25 Latitudefraction 18 4 70 Longitudefraction The position field is calculated as shown in figure 7.13.
TT-3027 TT98-147405-A Software Interface Reference Manual Packet format of the configuration poll 189 Radius = 235 = 00EBH LSB=EBH, MSB=00H 00 11 01 11 10 11 11 00 11 00 00 00 11 00 01 11 11 10 01 00 Hemisphere Degrees Minutes Fraction Hemisphere Degrees Minutes Fraction Spare Latitude Longitude N 55 47 06 E 12 31 18 Hex Binary 37 BC C0 C7 E4 Latitude Longitude Position Packet Field Figure 5.24 Calculation of the position field Checksum: If calculated like described in B.2.3 , the checksum bytes will be: CB1=A7H CB2=C9H Summary: Figure 5.25 shows the exact data for the circle zone. The attachment file must consist of this data.
TT-3027 TT98-147405-A Software Interface Reference Manual Packet format of the configuration poll 190 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 Byte 8 7 6 5 4 3 2 1 Bit no. Zero field 0 0 0 1 Length Ack reference Zone no. Zone type Reporting interval LSB Reporting interval MSB Zone data (7 byte) Checksum 16 8 7 6 5 4 3 2 1 Bit no. 0 0 0 1 0 0 0 0 0 0 0 0 1 1 1 0 0 0 0 0 0 0 0 1 0 0 0 0 0 0 0 1 0 0 0 0 0 0 0 1 H H H H H H H 0 1 0 0 0 0 0 1 0 0 0 0 0 0 1 1 H H H H H H H 0 0 1 1 0 1 1 1 1 0 1 1 1 1 0 0 1 1 0 0 0 0 0 1 1 0 0 0 1 1 1 1 1 0 1 0 0 1 0 0 1 1 1 0 1 0 1 1 0 0 0 0 0 0 0 0 H H 1 0 1 0 0 1 1 1 1 1 0 0 1 0 0 1 00 1E BC 01 01 01 41 03 37 C0 C7 E4 EB 00 A7 C9 Hex Figure 5.25 Data Field for the circle zone poll B.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 Position 2: 23 deg 08.00 min N, 82 deg 23.00 min W Position 3: 24 deg 37.18 min N, 83 deg 15.21 min W Reporting interval: 30 minutes We want to place the zone as number 2 in the MES (zone no.=2). As this is the first (and only) zone in the poll, ack reference=1. 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: As described above, the Ack Reference = 1.
TT-3027 TT98-147405-A Software Interface Reference Manual Packet format of the configuration poll 191 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: frames 208 frames 24 10000 60 1 30min 30 208 = 00D0H LSB=D0H, MSB=00H Zone data: The zone data consists of three positions. 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: Position 1: 11 4 45 Latitudefraction , 13 4 50 Longitudefraction Position 2: Latitudefraction 0, Longitudefraction 0 Position 3: 5 4 18 Latitudefraction , 5 4 21 Longitudefraction The position field is calculated as shown in Figure 5.26.
TT-3027 TT98-147405-A Software Interface Reference Manual Packet format of the configuration poll 192 00 01 10 01 10 11 10 01 01 11 01 01 00 00 00 11 00 01 10 10 Hemisphere Degrees Minutes Fraction Hemisphere Degrees Minutes Fraction Spare Latitude Longitude N 25 46 11 W 80 12 13 Hex Binary 19 B9 75 03 1A Latitude Longitude Position Packet Field Figure 5.26 Calculation of the position field 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: If calculated like described in B.2.3 , the checksum bytes will be: CB1=FAH CB2=3EH Summary: Figure 5.27 shows the exact data for the polygon poll. The attachment file must consist of this data.
TT-3027 TT98-147405-A Software Interface Reference Manual Packet format of the configuration poll 193 8 7 6 5 4 3 2 1 Bit no. 0 0 0 0 0 0 0 0 0 0 0 0 1 0 1 1 0 0 0 0 0 0 0 1 0 0 0 0 0 0 1 0 H H H H H H H 0 0 0 0 0 0 1 0 1 1 0 1 0 0 0 0 H H H H H H H 0 0 0 1 1 0 0 1 1 0 1 1 1 0 0 1 0 1 1 1 0 1 0 1 0 0 0 0 0 0 1 1 0 0 0 1 1 0 1 0 0 0 0 1 0 1 1 1 H H 0 0 1 0 0 0 0 0 0 0 0 1 0 1 0 1 00 81 19 16 01 02 02 D0 00 B9 75 03 1A 17 20 15 1 2 3 4 5 6 7 8 9 Byte 8 7 6 5 4 3 2 1 Bit no. Zero field Ack reference Zone poll no. Zone type Reporting interval LSB Reporting interval MSB Checksum Zone data 1 0 0 0 0 0 0 1 Length 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 1 0 0 0 0 0 0 1 0 0 0 0 0 0 0 0 H H 25 C0 0 0 1 0 0 1 0 1 1 1 0 0 0 0 0 0 H H H H 18 94 B5 33 H H CA FA 3E H 0 0 0 1 1 0 0 0 1 0 0 1 0 1 0 0 1 0 1 1 0 1 0 1 0 0 1 1 0 0 1 1 1 1 0 0 1 0 1 0 1 1 1 1 1 0 1 0 0 0 1 1 1 1 1 0 Figure 5.27 Data Field for the polygon zone poll
TT-3027 TT98-147405-A Software Interface Reference Manual Packet format of the configuration poll 194 B.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 Position 2: 32 deg 34.67 min S, 20 deg 23.48 min W Position 3: 28 deg 37.18 min S, 15 deg 52.47 min W Width: 114 km Reporting interval: 12 hours We want to place the zone as number 3 in the MES (zone no.=3). As this is the first (and only) zone in the poll, ack reference=1. 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: 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: hours frames 5000 frames 24 10000 12 12 5000 = 1388H LSB=88H, MSB=13H Zone data: The zone data consists of three positions. 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: Position 1: 10 4 39 Latitudefraction , 15 4 61 Longitudefraction
TT-3027 TT98-147405-A Software Interface Reference Manual Packet format of the configuration poll 195 Position 2: 17 4 67 Latitudefraction , 12 4 48 Longitudefraction Position 3: 5 4 18 Latitudefraction , 12 4 47 Longitudefraction The position field is calculated as shown in Figure 5.28. 10 10 00 11 10 10 11 01 01 01 00 01 10 00 10 00 00 01 11 10 Hemisphere Degrees Minutes Fraction Hemisphere Degrees Minutes Fraction Spare Latitude Longitude S 35 43 10 W 24 32 15 Hex Binary A3 AD 51 88 1E Latitude Longitude Position Packet Field Figure 5.28 Calculation of the position field 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: If calculated like described in B.2.3 , the checksum bytes will be:
TT-3027 TT98-147405-A Software Interface Reference Manual Packet format of the configuration poll 196 CB1=99H CB2=94H Summary: Figure 5.29 shows the exact data for the polyline poll. The attachment file must consist of this data. 1 0 0 1 0 1 0 0 Zone data 8 7 6 5 4 3 2 1 Bit no. 0 0 0 0 0 0 0 0 0 0 0 0 1 1 0 0 0 0 0 0 0 0 0 1 0 0 0 0 0 0 1 1 H H H H H H H 0 0 0 0 1 0 0 0 1 0 0 0 1 0 0 0 H H H H H H H 1 0 1 0 0 0 1 1 1 0 1 0 1 1 0 1 0 1 0 1 0 0 0 1 1 0 0 0 1 0 0 0 0 0 0 1 1 1 1 0 H H 1 0 0 0 1 0 1 0 0 0 1 1 0 0 0 1 00 81 A3 18 01 03 08 88 13 AD 51 88 1E A0 8A 31 1 2 3 4 5 6 7 8 9 Byte 8 7 6 5 4 3 2 1 Bit no. Zero field Ack reference Zone poll no. Zone type Reporting interval LSB Reporting interval MSB Checksum 1 0 0 0 0 0 0 1 Length 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 1 0 0 0 0 0 0 1 0 0 0 1 1 1 0 1 H H 45 D8 0 1 0 0 0 1 0 1 1 1 0 1 1 0 0 0 H H H H 9C 94 B0 FD H H 18 74 04 H 1 0 0 1 1 1 0 0 1 0 0 1 0 1 0 0 1 0 1 1 0 0 0 0 1 1 1 1 1 1 0 1 0 0 0 1 1 0 0 0 26 27 99 H 94 H 0 1 1 1 0 1 0 0 0 0 0 0 0 1 0 0 1 0 0 1 1 0 0 1 1 0 1 0 0 0 0 0 Figure 5.29 Data Field for the polyline zone poll B.4 Configuration poll Acknowledgement When the MES has received the T&T Remote Configuration poll and if acknowledgement is requested the MES returns an acknowledgement data-report. The acknowledgment data report for a poll is described in appendix H .
TT-3027 TT98-147405-A Software Interface Reference Manual Packet format of the configuration poll 197 B.5 Packet format of the zone group selection poll To select between the configured zone groups or zone group lists the following poll can be sent. <Type dependent fields> ::= <group/group list number> Figure 5.30 B.5 Packet format of the zone group selection poll For explanation of fields see B.1 . Since there is just one command set the Ack reference to 0x01. For explanation of Checksum field see B.2.3
TT-3027 TT98-147405-A Software Interface Reference Manual Format of data from the data log 198 C Format of data from the data log Figure 5.31 illustrates the format of the data returned from the data log. Field 1 (Event number) Field 2 (Time of creation) Header Entry 1 ... Entry n ... Entry m Field p ... Version number = 0 (1 byte) Mask of fields (4 bytes) Mobile number (4 bytes) Number of entries in the desired time interval (3 bytes) ID string: "3027EventLog" (12 bytes) Number of entries returned (3 bytes) Request number (2 byte) Sequence number (2 byte) Entry size (1 byte) Figure 5.31 Format when retrieving data from the data log. <Returned data> = <Header><Entry>* * = zero or more C.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> = “3027EventLog” (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.
TT-3027 TT98-147405-A Software Interface Reference Manual Format of data from the data log 199 <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> (4 bytes) 7 6 5 4 3 2 1 0 Mask byte 3 Mask byte 2 Mask byte 1 Mask byte 0 Figure 5.32 Mask of fields 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 0 0 Position GPS 0 1 Speed GPS 0 2 Course GPS 0 3 I/O status 0 4 Distance tachograph 0 5 Speed tachograph 0 6 Extended Position GPS 0 7 Speed GPS in knots 1 0 Table 5.16 Data fields The not used bits are reserved for future use. <Entry size> (1 bytes) This is the size of each entry. <Mobile number> (4 bytes)
TT-3027 TT98-147405-A Software Interface Reference Manual Format of data from the data log 200 This is the mobile number of the MES. <Desired entry count> (3 bytes) 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. C.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 <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: