UTILITY SOFTWARE FOR SATELLITE TRACKERS

Transcription

1 TN V5.1.0 UTILITY SOFTWARE FOR SATELLITE TRACKERS February 12, 2007 Copyright 2007 by NAL Research Corporation The specifications in this document are subject to change at NAL Research s discretion. NAL Research assumes no responsibility for any claims or damages arising out of the use of this document or from the use of the 9601-DGS, A3LA-DGS or A3LA-TSS based on this document, including but not limited to claims or damages based on infringement of patents, copyrights or other intellectual property rights. NAL Research makes no warranties, either expressed or implied with respect to the information and specifications contained in this document. Performance characteristics listed in this document are estimates only and do not constitute a warranty or guarantee of product performance.

2 TABLE OF CONTENTS 1.0 INTRODUCTION GETTING STARTED USING THE MESSAGE TRANSLATOR GUI Version of Message Translators Command Line Version of Message Translator SENDING A GENERAL SBD MESSAGE TO AN IRIDIUM MODEM Required Format to Send an SBD Message How to Send an SBD Message SENDING A GENERAL SMS MESSAGE TO AN IRIDIUM MODEM Required Format to Send an SMS Message How to Send an SMS Message USING THE REMOTE CONFIGURE GUI Version of Remote Configure Command Line Version of Remote Configure APPENDIX A DOCUMENT TYPE DEFINITIONS FOR XML FORMATTED GPS APPENDIX B DESCRIPTION OF MESSAGE FORMATS APPENDIX C BACKWARD COMPATIBILITY NAL Research Corporation (TN V5.1.0) 2

3 1.0 INTRODUCTION The 9601-DGS, A3LA-DGS and A3LA-TSS are Iridium satellite trackers developed by NAL Research. They are stand-alone units each relying on a built-in controller and a GPS receiver for operation instead of an external Data Terminal Equipment (DTE). As satellite trackers, their primary function is to send GPS reports to a network operating center (NOC) at a pre-programmed interval. While in the field, they can also accept real-time instructions/commands from a NOC to change their operating parameters as well as to relay on-demand GPS reports. A NOC could be a sophisticated command/control facility equipped with servers connected to high-speed networks. A NOC could also be as simple as a PDA/laptop/desktop with an attached tracker. There are differences in the hardware design and communication capabilities for each of the three Iridium trackers. Below is a quick reference on their basic differences; however, users are encouraged to thoroughly read the manuals provided with each model. Manuals are also available on NAL Research s website under RESOURCE CENTER/Anonymous ftp site DGS Tracker: a. Capable of two-way communications ONLY under SBD. b. Has Alert/Emergency/Test switches. c. Has LEDs to display networks statuses. d. Capable of two-way communications employing either standard compressed protocol or 256-bit AES encryption protocol. e. Small in form-factor, low in cost and low in power consumption. f. Compressed 30-byte GPS report to reduce SBD airtime cost. g. Does not support voice call. 2. A3LA-DGS Tracker: a. Capable of two-way communications using dial-up, RUDICS and SBD. b. Has Alert/Emergency switch. c. Encryption is not available. d. Larger in form-factor, higher in cost and higher in power consumption than the 9601-DGS. e. Compressed 30-byte GPS report to reduce SBD airtime cost. f. When not in tracking mode, audio calls can be placed. 3. A3LA-TSS Tracker: a. Capable of two-way communications using SBD and SMS. b. Has Alert/Emergency switch. c. Encryption is not available. d. Same form-factor, cost and power-consumption as the A3LA-DGS. e. Compressed 30-byte GPS report to reduce SBD airtime cost. f. While in tracking mode, a simultaneous audio call can be placed. NAL Research provides the Utility Software package with the intent of allowing users to quickly test the functionalities of any of the three trackers mentioned above. Before using the Utility Software, users must first set the trackers operating parameters with either SatTerm or the Terminal Software. The mode of operation of the trackers must either be SBD or SMS. The Utility Software package comprises of two parts NAL Research Corporation (TN V5.1.0) 3

4 Message Translator and Remote Configure. They include both GUI and Command Line programs with standard and encryption features. The Message Translator, as the name implies, translates all incoming attachments of SBD and SMS GPS reports into readable formats. The Remote Configure gives a NOC the ability to send commands to field trackers for operating parameters reconfiguration. 2.0 GETTING STARTED Before running the Setup program, make sure the NOC computer meets the following requirements: Windows XP/2000/NT Pentium II 266MHz (Pentium II 300MHz or faster for XP) with 256MB of RAM 4MB video card with DirectX 9.0 compatible drivers 8MB available on hard disk 800 x 600 screen resolution (looks best with a screen resolution of at least 1024 x 768) NOTE: On some computers with older versions of DirectX, the software may not appear correctly. If this happens, please go to and download the latest version of DirectX. We recommend at least version USING THE MESSAGE TRANSLATOR When the 9601-DGS, A3LA-DGS or A3LA-TSS tracker sends a GPS report using SBD, the report can arrive to a NOC as an message with an attachment. The SBD attachment is compressed to 30 bytes employing NAL Research s defined algorithm. For an SMS GPS report (applicable only to model A3LA- TSS), the SMS attachment is also compressed to 58 bytes in length. The message length for both SBD and SMS attachments can be longer depending on the static identifier (platform ID) entered by the users. In addition, SBD attachments may include previously missed GPS reports, which makes the message length potentially a lot longer than 30 bytes. If encryption is used the file size will be increased by two bytes to 32 bytes long. The Message Translator converts SBD and SMS GPS report attachments into readable formats. There are two versions of the Message Translator GUI and command line programs. 3.1 GUI Version of Message Translator The Message Translator can be accessed from the Windows Start menu by choosing NAL Research Tracker Utilities Message Translator. To use the program follow the steps below. If the encrypted version is used, click the Properties button to setup the properties. On some Windows XP version, the Message Translator software may prematurely close when opening a file. If this occurs, it is recommended that the Open/Save Dialog Style of 3.1 be selected. If Decrypt is selected, then a user name and password must be entered in the Encryption Login window. This use name and password will be used to retrieve the decryption key for the translation. The Crypto Officer Settings can also be selected to change or view accounts. Users are referred to the Encryption Module Manual for more information. NAL Research Corporation (TN V5.1.0) 4

5 Use the pull down menu to select a format for the translation. Click the Translate GPS Report button. Change the Type of File button to narrow the files displayed to show only SBD Reports (.sbd) or SMS Reports (.eml). Select the file to translate and click Open. Once a file is selected using the Translate GPS Report button, it remains in memory and can be translated in to any of the formats by selecting from the pull down menu without the need to click the Translate GPS Report button again. The translation is written to the screen. However, it is not saved. To save the report to a file, follow the remaining steps. Click the Save button. Enter a file name to write the translation to and click Save. The program is also setup upon installation to automatically translate the.sbd extension when data files of are double clicked. NAL Research Corporation (TN V5.1.0) 5

6 3.2 Command Line Version of Message Translator This program is located in the Program Files\NAL\Tracker Utilities directory. An example batch file called SMT_example.bat is also included in this directory. The program writes its output to a standard display device (computer screen), which can be redirected to a file with the greater than sign (>) and then a file name. The program requires two arguments as listed below. 1. The name of the file to be translated that should have a.sbd for SBD GPS reports and an.eml for SMS reports. The program needs the appropriate extension to translate correctly. 2. The number corresponding to the format of the translated report. Format before version GPSI XML String 2 - Easy to Read Text 3 - Compact Delimited Text 4 - Original Text format from 2Way Mode 5 - NMEA GGA and VTG format Format after version 3.2 with no DOPs 6 - GPSI XML String 7 - Easy to Read Text 8 - Compact Delimited Text 9 - Original Text format from 2Way Mode 10 - NMEA GGA and VTG format Format using version 4 GPS reports 11 - GPSI XML String 12 - Easy to Read Text 13 - Compact Delimited Text 14 - NMEA GGA and VTG format 3. \eu: User Name Optional if Encryption feature is included the user name to use for the encryption lookup. 4. \ep:"password" Optional if Encryption feature is included the password to use for the encryption lookup. 5. \ekey:"key" Optional if Encryption feature is included the location of the Keys directory, NOT including the Keys folder. Default location is c:\program Files\NAL\Common. 6. \YMillenniumCentury Optional The millennium and century values are not included with the GPS reports. An example is Y20. If none is specified then the millennium is assumed to be 2 and the century 0. NAL Research Corporation (TN V5.1.0) 6

7 Two examples are given above (1) Input SMT_command_Line c:\test\ _ sbd 1 and (2) Input SMT_command_Line c:\test\ _ sbd 1 \eu: user1 \ep: user1passwd \ekey: c:\program files\nal ). 4.0 SENDING A GENERAL SBD MESSAGE TO AN IRIDIUM MODEM 4.1 Required Format to Send an SBD Message In order to send a general SBD message to an Iridium modem (not necessarily to an NAL Research s tracking unit), the program must be in the standard Multipurpose Internet Mail Extensions (MIME) Base64 encoding as defined in RFC The following instructions describe how to set this up for Microsoft Outlook Express: 1. Select Tools/Options 2. Click the Send Tab 3. Under Mail Sending Format, click HTML Settings 4. Click MIME 5. Select Base 64 for Encode text using NAL Research Corporation (TN V5.1.0) 7

8 6. Click OK 7. Under Mail Sending Format, click Plain Text Settings 8. Repeat steps How to Send an SBD Message Follow the instructions below to send a general SBD message to an Iridium modem (not necessarily to an NAL Research s tracking unit) through the commercial Iridium Gateway: 1. Send all messages to Data@SBD.Iridium.com. 2. Place the Iridium modem s IMEI number in the subject line. 3. The message is carried in an attachment, which must have a.sbd extension. NOTE: Similar steps are given for the DoD gateway upon request. 5.0 SENDING A GENERAL SMS MESSAGE TO AN IRIDIUM MODEM 5.1 Required Format to Send an SMS Message In order to send a general SMS message to an Iridium modem (not necessarily to an NAL Research s the tracker), the program should not use any encoding. The following instructions describe how to set this up for Outlook Express: 1. Select Tools/Options 2. Click the Send Tab 3. Under Mail Sending Format, click HTML Settings 4. Select None for Encode text using 5. Click OK 6. Under Mail Sending Format, click Plain Text Settings 7. Repeat steps How to Send an SMS Message Follow the instructions below to send a general SMS message to an Iridium modem (not necessarily to an NAL Research s the tracker) through the commercial Iridium Gateway: 1. Send all messages to [MSISDN]@msg.Iridium.com where [MSISDN] is the MSISDN number of the SIM card. 2. Place NO the subject line. This will keep the return address from being included. 3. Cut and paste the text for the SMS message into the body of the message. NOTE: Similar steps are given for the DoD gateway upon request. 6.0 USING THE REMOTE CONFIGURE The approaches in making remote changes to the operating parameters of the 9601-DGS, A3LA-DGS and A3LA-TSS are similar to what is being described in Sections 4.0 and 5.0. The content of the SBD attachments and the SMS body of the message contain the updated operating parameters. The Remote Configure software provides the user an easy way to generate these attachments. The 9601-DGS and the A3LA-DGS are updated by SBD and the A3LA-TSS is updated by SMS. There is both a GUI version and a Command Line Version of Remote Configure. NAL Research Corporation (TN V5.1.0) 8

9 6.1 GUI Version of Remote Configure The GUI version of the Remote Configure program can be opened by choosing NAL Research Tracker Utilities Remote Configure from the Windows start menu. On some Windows XP versions the Remote Configure software may prematurely close when opening a file. If this happens, it is recommended that the Open/Save Dialog Style of 3.1 be selected. Instructions below are for remote updating the 9601-DGS operating parameters: Select the Tracker Type of 9601-DGS. Select the Update Interval check box to change the followings: o Select Time between Reports option and enter minutes or hours/minutes if applicable o Select Time to Keep Trying option and enter the minutes/seconds if applicable Select Update Callable, then select Sleeps Between Reports or Callable Between Reports. Enter the password given to the 9601-DGS during setup (must be 8 characters in length). Click Generate SBD Message to Configure button and save. This newly generated file can be sent via SBD to update the 9601-DGS operating parameters by following instructions in Section 4.2. The IMEI number must be entered if encryption is used so that the Remote Configure software can look up the Encryption Key. NAL Research Corporation (TN V5.1.0) 9

10 Instructions below are for remote updating the A3LA-DGS dial-up operating parameters. Select the Tracker Type of A3LA-DGS. Select the Update Number to Dial check box to change calling settings. This only applies to sending reports in 2way mode. o Enter the new number to dial o Re-enter the number to dial on the next line and press Enter. If the two numbers match, the second line for the number to dial will disappear o Select whether the unit will be calling another Iridium modem or a landline modem Select the Update Interval check box to change the interval settings. o Enter the new Time between Calls in either minutes or hours/minutes o Enter the Number of Tries Enter the password given to the A3LA-DGS during setup (must be 8 characters in length) Click Generate SBD Message to Configure button and save. This newly generated file can be sent via SBD to update the A3LA-DGS operating parameters by following instructions in Section 4.2. NAL Research Corporation (TN V5.1.0) 10

11 Instructions below are for remote updating the A3LA-TSS operating parameters: Select the Tracker Type of A3LA-TSS. Select the Update Destination check box to change destination settings. o Select the method to send the updates by SBD, SMS Phone Number, or SMS Address o If updating SMS Phone Number or SMS Address then re-enter the field on the next line. Select the Update Interval check box to change the interval settings. o Enter the new Time between Calls in either minutes or hours/minutes o Enter the Number of Tries Enter the password given to the A3LA-TSS during setup (must be 8 characters in length). Click the Display SMS Configure Text button to generate the update message. This can be cut and pasted into the body of the that will make the remote update. NAL Research Corporation (TN V5.1.0) 11

12 6.2 Command Line Version of Remote Configure This program locates in the Program Files\NAL\Tracker Utilities directory. This program creates an SBD attachment for an message to configure the 9601-DGS or the A3LA-DGS remotely or the text to put into the body of an message to configure an A3LA-TSS remotely. The input arguments of the program must have the following identical formats. /c:stat Callable status between reports, where stat is s for sleeps or c for callable (all modems) /d:"#" If /tss Number to send SMS to. If not /tss and not /tgs, number to dial, where # is a 1 to 32 byte string, within recommended quotes /dsc:# /e: address /f:"file name" /kt:min,sec /ktv:# /m:# /p:" " /r:# /t:t /tss /tgs Delivery short code, where # is from 0 to 255(9601-DGS) The address to send the SMS message to within recommended quotes The name of the file to save the message. Recommend ending it with a.sbd extension, within recommended quotes, if not using the /tss option Time to retry call, where min is from 0 to 21. If min is less than 21 then sec is from 0 to 59. If min is 21, then sec must be 0 to 10. Both sec and min cannot be 0. Sec must be divisible by 5.(9601-DGS) Time to retry call straight value, where # is from 0 to will cause the modem to try to send reports once, 255 will keep the modem trying until the next report.(9601-dgs) Minutes between calls, where # is from 0 to will cause the modem to send out reports as fast as it can on the 9601-DGS will cause the unit to not send out reports, but wait for ping and remote update requests. (all modems) 8 byte password within recommended quotes Number of tries, where # is from 1 to (A3LA-IGS, A3LA-DGS, and A3LA- TSS) Type of call where T is L for landline or S for satellite (A3LA-IGS and A3LA- DGS). If present then sending to an A3LA-TSS. If not present and not /tgs, then sending to an A3LA-IGS or A3LA-DGS. If present then sending to a 9601-DGS. If not present and not /tss, then sending to an A3LA-IGS or A3LA-DGS. If sending to an A3LA-IGS or A3LA-DGS unit, a valid argument list must contain /p and (/d /t) or (/m /r). If sending to a 9601-DGS unit, the valid parameter list will have /p and at least one of these groups: (/dsc), (/m /kt), (/m /ktv), or (/c). NAL Research Corporation (TN V5.1.0) 12

13 If sending to an A3LA-IGS, A3LA-DGS, or 9601-DGS unit, since to send the file with sbd the file must have an sbd extension it is recommended the file name will end by.sbd. The SBD message attachment must use Mail Extensions (MIME) Base64 encoding as defined in RFC If sending to an A3LA-TSS unit, the parameter list must contain /p and either both /m and /r or neither. The output from the program must be put into the body of the that will be used to update the remote unit. The /f is optional. If not specified the string will be sent to standard output. The /eu, /ep, /eimei, and /ek are optional. However they may only be used if the /tgs tag is specified and if one is used then all 4 must be used. Examples: /p:" " /d:" " /t:l /m:12 /r:2 /f:"out.sbd" /p:" " /tss /d:" " /p:" " /tgs /d:" " /kt:10,20 NAL Research Corporation (TN V5.1.0) 13

14 APPENDIX A DOCUMENT TYPE DEFINITIONS FOR XML FORMATTED REPORTS GPS reports received by SBD from A3LA-DGS with firmware versions arrive in XML format and do not need to be translated. All other GPS reports, whether received by 2Way, SBD, or SMS, can be translated into any of the ten supported message formats including GPSI and GPSI < 3.2 using either the Server for Trackers program or the Message Translator utility. The definitions shown below were written in XML version 1 for the ASCII character set. In the current version, the report numbers can only be from 0 to 3. However, this may change in future releases, which may be able to store more GPS Reports. The HDOP and VDOP do not appear if the GPSI no DOPs is selected. GPSI Format DTD <!ELEMENT GPSI (ID, Emergency, Report+)> <!ELEMENT ID (#PCDATA)> <!ELEMENT Emergency (#PCDATA)> <!ELEMENT Report (Time, Date, Lat, Lng, Alt, Speed, Dir, VerVel, Fix, Sat)> <!ATTLIST Report N ID #REQUIRED> <!ELEMENT Time (#PCDATA)> <!ELEMENT Date (#PCDATA)> <!ELEMENT Lat (#PCDATA)> <!ELEMENT Lng (#PCDATA)> <!ELEMENT Alt (#PCDATA)> <!ELEMENT Speed (#PCDATA)> <!ELEMENT Dir (#PCDATA)> <!ELEMENT VerVel (#PCDATA)> <!ELEMENT Fix (#PCDATA)> <!ELEMENT Sat (#PCDATA)> <!ELEMENT HDOP (#PCDATA)> <!ELEMENT VDOP (#PCDATA)> GPSI < 3.2 Format DTD <!ELEMENT GPSI (ID, Report+)> <!ELEMENT ID (#PCDATA)> <!ELEMENT Report (Time, Date, Lat, Lng, Alt, Speed, Dir, Fix, Sat)> <!ATTLIST Report N ID #REQUIRED> <!ELEMENT Time (#PCDATA)> <!ELEMENT Date (#PCDATA)> <!ELEMENT Lat (#PCDATA)> <!ELEMENT Lng (#PCDATA)> <!ELEMENT Alt (#PCDATA)> <!ELEMENT Speed (#PCDATA)> <!ELEMENT Dir (#PCDATA)> <!ELEMENT Fix (#PCDATA)> <!ELEMENT Sat (#PCDATA)> NAL Research Corporation (TN V5.1.0) 14

15 DTD for SBD s for Firmware Versions 2.0 and 2.1 <!ELEMENT GPSI (ID, Report+)> <!ELEMENT ID (#PCDATA)> <!ELEMENT Report (Time, Date, Lat, Lng, Alt, Fix, Sat)> <!ATTLIST Report N ID #REQUIRED> <!ELEMENT Time (#PCDATA)> <!ELEMENT Date (#PCDATA)> <!ELEMENT Lat (#PCDATA)> <!ELEMENT Lng (#PCDATA)> <!ELEMENT Alt (#PCDATA)> <!ELEMENT Fix (#PCDATA)> <!ELEMENT Sat (#PCDATA)> NAL Research Corporation (TN V5.1.0) 15

16 APPENDIX B DESCRIPTION OF MESSAGE FORMATS The different message formats are listed below. In the next few sections, the {} symbol denotes a variable and the [] symbol denotes that what is enclosed is optional. If the text is not enclosed by {}, then it is literal. The table below describes the parts of a GPS report. The 9601-DGS always has 1 position since it does not buffer missed positions. VARIABLES ID DESCRIPTION The identifier or IMEI number of the remote modem that delivered the GPS report. Indicates if the report was an emergency report or not. The representation of the emergency indicator varies for the message formats as shown below. Emergency Indication Easy to Read, NMEA GGA and VTG GPSI, Compact Original Emergency Emergency 1 Emergency Not Emergency Normal 0 (Nothing) ReportNum BufferedA BufferedB BufferedC Time Date Lat Lng Alt Speed Dir VerVel For GPSI formats: For Easy to Read Formats and Original formats: 1 means first buffered GPS report 1 means latest buffered GPS report 2 means second buffered GPS report 2 means second buffered GPS report 3 means latest buffered GPS report 3 means first buffered GPS report First buffered report. Second buffered report. Latest buffered report. The UTC time when the GPS information was gathered, given as hours, followed by minutes, followed by seconds, followed by fractions of a second. The UTC date when the GPS information was gathered, given as month, followed by day, followed by year. The latitude of the remote modem, given as degrees, followed by minutes, followed by fractions of a minute, followed by cardinal direction. The longitude of the remote modem, given as degrees, followed by minutes, followed by fractions of a minute, followed by cardinal direction. The height above mean sea level of the remote modem in meters. The speed of the remote modem in kilometers per hour. The direction of the remote modem, given by degrees from True North. The vertical component of the velocity of the remote modem in meters per second. Ascending is negative and descending is positive NAL Research Corporation (TN V5.1.0) 16

17 VARIABLES DESCRIPTION The type of position fix that the remote modem acquired. The representation of the types of position fixes varies for the message formats as shown below. Type of Fix Easy to Read GPSI, Compact NMEA GGA and VTG Invalid Invalid Positing Fix 0 0 Valid Valid Position Fix 1 1 Fix 2D 2D Fix 2 N/A Dead Reckoning Dead Reckoning 3 6 Type of Fix Invalid Valid Easy to Read < 3.2, Original < 3.2, Original Invalid Positing Fix (Nothing) GPSI < 3.2, Compact < 3.2, NMEA GGA and VTG < Sat HDOP VDOP NMEA GGA NMEA VTG ZDA The number of GPS satellites used in determining the position. Horizontal delusion of precision Vertical delusion of precision See TN V3.3.1 (Extended AT GPS Commands) for the details of each NMEA message. NOTE: The GPS report information also includes a report type, which is used to help translate the reports as well as determine if the sending remote modem supports certain features NAL Research Corporation (TN V5.1.0) 17

18 Easy to Read Format This format displays GPS information in an easy to read plain text string. FORMAT ModemID={ID} {Emergency} [Missed {ReportNum} {BufferedC} [Missed {ReportNum} {BufferedB} [Missed {ReportNum} {BufferedA} ]]] UTC Time={Time} UTC Date={Date} Latitude={Lat} Longitude={Lng} Altitude={Alt} meters Ground Velocity={Speed} km/h at {Dir} degrees from True North Vertical Velocity={VerVel} m/s {Fix} Satellites Used={Sat} HDOP={HDOP} VDIO={VDOP} EXAMPLE ModemID= Normal Missed 1 UTC Time=14:28:09.56 UTC Date= Latitude=38: North Longitude=077: West Altitude=54.3 meters Ground Velocity=0.1 km/h at degrees from True North Vertical Velocity=0.0 m/s Satellites Used=07 HDOP=1.19 VDOP=1.66 UTC Time=14:31:50.04 UTC Date= Latitude=38: North Longitude=077: West Altitude=0.0 meters Ground Velocity=0.0 km/h at 0.00 degrees from True North Vertical Velocity=0.0 m/s Invalid Position Fix Satellites Used=03 HDOP=1.04 VDOP=1.84 NAL Research Corporation (TN V5.1.0) 18

19 GPSI Format This format displays GPS information in an XML string (see Appendix C for the DTD). FORMAT <GPSI> <ID>{ID}</ID> <Emergency>{Emergency}</Emergency> [{BufferedC} [{BufferedB} [{BufferedA}]]] <Report N= {ReportNum} > <Time>{Time}</Time> <Date>{Date}</Date> <Lat>{Lat}</Lat> <Lng>{Lng}</Lng> <Alt>{Alt}meters</Alt> <Speed>{Speed}km/h</Speed> <Dir>{Dir} degrees from True North</Dir> <VerVel>{VerVel}m/s</VerVel> <Fix>{Fix}</Fix> <Sat>{Sat}</Sat> <HDOP>{HDOP}</HDOP> <VDOP>{VDOP}</VDOP> </Report> </GPSI> EXAMPLE <GPSI> <ID> </ID> <Emergency>0</Emergency> <Report N= 1 > <Time>14:28:09.56</Time> <Date> </Date> <Lat>38: N</Lat> <Lng>77: W</Lng> <Alt>54.3meters</Alt> <Speed>0.1km/h</Speed> <Dir>40.81 degrees from True North</Dir> <VerVel>0.0m/s</VerVel> <Fix>1</Fix> <Sat>7</Sat> <HDOP>1.07</HDOP> <VDOP>1.11</VDOP> </Report> <Report N= 0 > <Time>14:31:50.04</Time> <Date> </Date> <Lat>38: N</Lat> <Lng>77: W</Lng> <Alt>0.0meters</Alt> <Speed>0.0km/h</Speed> <Dir>0.00 degrees from True North</Dir> <VerVel>0.0m/s</VerVel> <Fix>0</Fix> <Sat>3</Sat> <HDOP>1.05</HDOP> <VDOP>1.01</VDOP> </Report> </GPSI> NAL Research Corporation (TN V5.1.0) 19

20 Compact Format This format displays GPS information as a compact comma delimited string. FORMAT {ID} {Emergency} [{BufferedC} [{BufferedB} [{BufferedA}]]] {Time},{Date},{Lat},{Lng},{Alt},{Speed}:{Dir},{VerVel},{Fix},{Sat},{HDOP},{VDOP} EXAMPLE :28:09.56,12-1-3,38: N,77: W,54.3,0.1:40.81,0.0,1,7,1.05, :31:50.04,12-1-3,38: N,77: W,0.0,0.0:0.00,0.0,0,3,1.07,1.06 NAL Research Corporation (TN V5.1.0) 20

21 Original Format This format displays GPS information in a format compatible with version 2.1. FORMAT ModemID={ID} [Missed {ReportNum} {BufferedC} [Missed {ReportNum} {BufferedB} [Missed {ReportNum} {BufferedA} ]]] UTC Time={Time} UTC Date={Date} Latitude={Lat} Longitude={Lng} Altitude={Alt} [{Fix}] Satellites Used={Sat} EXAMPLE ModemID= Missed 1 UTC Time=14:28:09.56 UTC Date= Latitude=38: North Longitude=077: West Altitude=54.3 meters Satellites Used=07 UTC Time=14:31:50.04 UTC Date= Latitude=38: North Longitude=077: West Altitude=0.0 meters Invalid Position Fix Satellites Used=03 NAL Research Corporation (TN V5.1.0) 21

22 NMEA GGA, VTG, and ZDA Formats This format displays GPS information using the GGA, VTG, and ZDA formats. FORMAT {ID} {Emergency} [{BufferedC} [{BufferedB} [{BufferedA}]]] {NMEA GGA} {NMEA VTG} {ZDA} EXAMPLE Normal $GPGGA, , ,N, ,W,1,07,1.55,54.3,M,,M,,*74 $GPVTG,40.81,T,,M,0.05,N,0.1,K*59 $GPZDA, ,01,12,2003,00,00*60 $GPGGA, , ,N, ,W,0,03,1.03,0.0,M,,M,,*48 $GPVTG,0.00,T,,M,0.0,N,0.0,K*50 $GPZDA, ,01,12,2003,00,00*64 NAL Research Corporation (TN V5.1.0) 22

23 Easy to Read < V3.2 Format This format displays GPS information in an easy to read plain text string. FORMAT ModemID={ID} [Missed {ReportNum} {BufferedC} [Missed {ReportNum} {BufferedB} [Missed {ReportNum} {BufferedA} ]]] UTC Time={Time} UTC Date={Date} Latitude={Lat} Longitude={Lng} Altitude={Alt} meters Ground Velocity={Speed} km/h at {Dir} degrees from True North [{Fix}] Satellites Used={Sat} EXAMPLE ModemID= Missed 1 UTC Time=14:28: UTC Date= Latitude=38: North Longitude=077: West Altitude=54.3 meters Ground Velocity=0.1 km/h at degrees from True North Satellites Used=07 UTC Time=14:31: UTC Date= Latitude=38: North Longitude=077: West Altitude=0.0 meters Ground Velocity=0.0 km/h at 0.00 degrees from True North Invalid Position Fix Satellites Used=03 NAL Research Corporation (TN V5.1.0) 23

24 GPSI < V3.2 Format This format displays GPS information in an XML string (see Appendix C for the DTD). FORMAT <GPSI> <ID>{ID}</ID> [{BufferedC} [{BufferedB} [{BufferedA}]]] <Report N={ReportNum}> <Time>{Time}</Time> <Date>{Date}</Date> <Lat>{Lat}</Lat> <Lng>{Lng}</Lng> <Alt>{Alt}meters</Alt> <Speed>{Speed}km/h</Speed> <Dir>{Dir} degrees from True North</Dir> <Fix>{Fix}</Fix> <Sat>{Sat}</Sat> </Report> </GPSI> EXAMPLE <GPSI> <ID> </ID> <Report N=1> <Time>14:28:09.562</Time> <Date> </Date> <Lat>38: N</Lat> <Lng>77: W</Lng> <Alt>54.3meters</Alt> <Speed>0.1km/h</Speed> <Dir>40.81 degrees from True North</Dir> <Fix>1</Fix> <Sat>7</Sat> </Report> <Report N=0> <Time>14:31:50.038</Time> <Date> </Date> <Lat>38: N</Lat> <Lng>77: W</Lng> <Alt>0.0meters</Alt> <Speed>0.0km/h</Speed> <Dir>0.00 degrees from True North</Dir> <Fix>0</Fix> <Sat>3</Sat> </Report> </GPSI> NAL Research Corporation (TN V5.1.0) 24

25 Compact < V3.2 Format This format displays GPS information as a compact comma delimited string. FORMAT {ID} [{BufferedC} [{BufferedB} [{BufferedA}]]] {Time},{Date},{Lat},{Lng},{Alt},{Speed}:{Dir},{Fix},{Sat} EXAMPLE :28:09.562,12-1-3,38: N,77: W,54.3,0.1:40.81,1,7 14:31:50.038,12-1-3,38: N,77: W,0.0,0.0:0.00,0,3 NAL Research Corporation (TN V5.1.0) 25

26 Original < V3.2 Format This format displays GPS information in a format compatible with version 2.1. FORMAT ModemID={ID} [Missed {ReportNum} {BufferedC} [Missed {ReportNum} {BufferedB} [Missed {ReportNum} {BufferedA} ]]] UTC Time={Time} UTC Date={Date} Latitude={Lat} Longitude={Lng} Altitude={Alt} [{Fix}] Satellites Used={Sat} EXAMPLE ModemID= Missed 1 UTC Time=14:28: UTC Date= Latitude=38: North Longitude=077: West Altitude=54.3 meters Satellites Used=07 UTC Time=14:31: UTC Date= Latitude=38: North Longitude=077: West Altitude=0.0 meters Invalid Position Fix Satellites Used=03 NAL Research Corporation (TN V5.1.0) 26

27 NMEA GGA, VTG, and ZDA < V3.2 Formats This format displays GPS information using the GGA, VTG, and ZDA formats. FORMAT {ID} [{BufferedC} [{BufferedB} [{BufferedA}]]] {NMEA GGA} {NMEA VTG} {ZDA} EXAMPLE $GPGGA, , ,N, ,W,1,07,,54.3,M,,M,,*74 $GPVTG,40.81,T,,M,0.05,N,0.1,K*59 $GPZDA, ,01,12,2003,00,00*60 $GPGGA, , ,N, ,W,0,03,,0.0,M,,M,,*48 $GPVTG,0.00,T,,M,0.0,N,0.0,K*50 $GPZDA, ,01,12,2003,00,00*64 NAL Research Corporation (TN V5.1.0) 27

28 GPSI < V5 Format This format displays GPS information in an XML string (see Appendix C for the DTD). FORMAT <GPSI> <ID>{ID}</ID> <Emergency>{Emergency}</Emergency> [{BufferedC} [{BufferedB} [{BufferedA}]]] <Report N={ReportNum}> <Time>{Time}</Time> <Date>{Date}</Date> <Lat>{Lat}</Lat> <Lng>{Lng}</Lng> <Alt>{Alt}meters</Alt> <Speed>{Speed}km/h</Speed> <Dir>{Dir} degrees from True North</Dir> <VerVel>{VerVel}m/s</VerVel> <Fix>{Fix}</Fix> <Sat>{Sat}</Sat> </Report> </GPSI> EXAMPLE <GPSI> <ID> </ID> <Emergency>0</Emergency> <Report N=1> <Time>14:28:09.56</Time> <Date> </Date> <Lat>38: N</Lat> <Lng>77: W</Lng> <Alt>54.3meters</Alt> <Speed>0.1km/h</Speed> <Dir>40.81 degrees from True North</Dir> <VerVel>0.0m/s</VerVel> <Fix>1</Fix> <Sat>7</Sat> </Report> <Report N=0> <Time>14:31:50.04</Time> <Date> </Date> <Lat>38: N</Lat> <Lng>77: W</Lng> <Alt>0.0meters</Alt> <Speed>0.0km/h</Speed> <Dir>0.00 degrees from True North</Dir> <VerVel>0.0m/s</VerVel> <Fix>0</Fix> <Sat>3</Sat> </Report> </GPSI> NAL Research Corporation (TN V5.1.0) 28

29 Easy to Read Format no DOPs This format displays GPS information in an easy to read plain text string. FORMAT ModemID={ID} {Emergency} [Missed {ReportNum} {BufferedC} [Missed {ReportNum} {BufferedB} [Missed {ReportNum} {BufferedA} ]]] UTC Time={Time} UTC Date={Date} Latitude={Lat} Longitude={Lng} Altitude={Alt} meters Ground Velocity={Speed} km/h at {Dir} degrees from True North Vertical Velocity={VerVel} m/s {Fix} Satellites Used={Sat} EXAMPLE ModemID= Normal Missed 1 UTC Time=14:28:09.56 UTC Date= Latitude=38: North Longitude=077: West Altitude=54.3 meters Ground Velocity=0.1 km/h at degrees from True North Vertical Velocity=0.0 m/s Satellites Used=07 UTC Time=14:31:50.04 UTC Date= Latitude=38: North Longitude=077: West Altitude=0.0 meters Ground Velocity=0.0 km/h at 0.00 degrees from True North Vertical Velocity=0.0 m/s Invalid Position Fix Satellites Used=03 NAL Research Corporation (TN V5.1.0) 29

30 GPSI no DOPs Format This format displays GPS information in an XML string (see Appendix C for the DTD). FORMAT <GPSI> <ID>{ID}</ID> <Emergency>{Emergency}</Emergency> [{BufferedC} [{BufferedB} [{BufferedA}]]] <Report N= {ReportNum} > <Time>{Time}</Time> <Date>{Date}</Date> <Lat>{Lat}</Lat> <Lng>{Lng}</Lng> <Alt>{Alt}meters</Alt> <Speed>{Speed}km/h</Speed> <Dir>{Dir} degrees from True North</Dir> <VerVel>{VerVel}m/s</VerVel> <Fix>{Fix}</Fix> <Sat>{Sat}</Sat> </Report> </GPSI> EXAMPLE <GPSI> <ID> </ID> <Emergency>0</Emergency> <Report N= 1 > <Time>14:28:09.56</Time> <Date> </Date> <Lat>38: N</Lat> <Lng>77: W</Lng> <Alt>54.3meters</Alt> <Speed>0.1km/h</Speed> <Dir>40.81 degrees from True North</Dir> <VerVel>0.0m/s</VerVel> <Fix>1</Fix> <Sat>7</Sat> </Report> <Report N= 0 > <Time>14:31:50.04</Time> <Date> </Date> <Lat>38: N</Lat> <Lng>77: W</Lng> <Alt>0.0meters</Alt> <Speed>0.0km/h</Speed> <Dir>0.00 degrees from True North</Dir> <VerVel>0.0m/s</VerVel> <Fix>0</Fix> <Sat>3</Sat> </Report> </GPSI> NAL Research Corporation (TN V5.1.0) 30

31 Compact no DOPs Format This format displays GPS information as a compact comma delimited string. FORMAT {ID} {Emergency} [{BufferedC} [{BufferedB} [{BufferedA}]]] {Time},{Date},{Lat},{Lng},{Alt},{Speed}:{Dir},{VerVel},{Fix},{Sat} EXAMPLE :28:09.56,12-1-3,38: N,77: W,54.3,0.1:40.81,0.0,1,7 14:31:50.04,12-1-3,38: N,77: W,0.0,0.0:0.00,0.0,0,3 NAL Research Corporation (TN V5.1.0) 31

32 NMEA GGA, VTG, and ZDA no DOPs Formats This format displays GPS information using the GGA, VTG, and ZDA formats. FORMAT {ID} {Emergency} [{BufferedC} [{BufferedB} [{BufferedA}]]] {NMEA GGA} {NMEA VTG} {ZDA} EXAMPLE Normal $GPGGA, , ,N, ,W,1,07,,54.3,M,,M,,*74 $GPVTG,40.81,T,,M,0.05,N,0.1,K*59 $GPZDA, ,01,12,2003,00,00*60 $GPGGA, , ,N, ,W,0,03,,0.0,M,,M,,*48 $GPVTG,0.00,T,,M,0.0,N,0.0,K*50 $GPZDA, ,01,12,2003,00,00*64 NAL Research Corporation (TN V5.1.0) 32

33 APPENDIX C BACKWARDS COMPATIBILITY NAL Research Corporation continues to support old A3LA-IGS and A3LA-DGS firmware versions as well as all versions and features of the A3LA-TSS and 9601-DGS modems. Please note that the version of the software that runs on the PCs does not necessarily correspond to the versions on the modems themselves. In version the RF board changed from the Sebring to the Daytona. The table below summarizes which firmware versions support the listed features. SUPPORTED A3LA-IGS/ -DGS FIRMWARE VERSIONS FEATURES , , 3.2.1, Terminal Software 3.2 Can Configure Server for Terminal Modems 3.2 Accepts GPS Reports in 2Way Mode Server for Terminal Modems 3.2 Accepts GPS Reports from SBD Mode 1 Can be Called During one of the Tracking Modes (2way and SBD) Can Make Remote Updates To Can Chat With Can Include Text Identifier with SBD GPS Reports Has TIM-LP GPS Receiver Responses to Remote Updates Includes Items that were Changed Before using the 2.2 software to configure 2.1 A3LA-DGS or before calling the version 2.2 and higher of Server for Terminal Modems Software, all quotes, spaces, and underscores need to be removed from the password and all quotes need to be removed from the identifier field. Versions 2.2 and higher of the Server for Terminal Modems Software translate all underscores to spaces in the identifier field. Thus, if a unit is deployed to contain underscore characters, they will appear as spaces in the version 2.2 and higher of the Server for Terminal Modems software. 1 A3LA-IGS with firmware versions send GPS reports in XML format for SBD mode instead of a compressed format (see appendix C for the DTD). However, the Server for Terminal Modems software as well as the SBD Message Translator utility expects the GPS reports to be in a compressed format. Therefore, these programs are unable to translate GPS reports from SBD mode for these firmware versions. In fact, if the Server for Terminal Modems program is used to retrieve SBD GPS reports from an A3LA-IGS with a firmware version of , the program may delete the containing the GPS report without logging it, depending on the program s properties. NAL Research Corporation (TN V5.1.0) 33