SERVER FOR SATELLITE TRACKERS TECHNICAL NOTE

Transcription

1 TN V6.1 SERVER FOR SATELLITE TRACKERS TECHNICAL NOTE April 2, 2008 Copyright 2008 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 trackers and A3LA trackers 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 TABLE OF CONTENTS INTRODUCTION GETTING STARTED System Requirements Installation USING THE PROGRAM Running the Server for Tracker File Menu New Session/Open Session/Save Session/Exit Communication Menu Configure Communications Links Options Menu GPS Options Menu Data Options Menu Message Format Options Menu 2Way Transmission Mode Options Menu Encryption (Model 9601-DGS Only) Options Menu Contact Remote Modems Options Menu Manage Chat Windows Options Menu Send / Track Remote Updates Options Menu Use 3.1 Open/Save Dialog Style Options Menu For SBD/SMS Use Unique ID Options Menu Emergency Report Acknowledge KNOWN PROBLEMS NOTES FOR MICROSOFT WINDOWS VISTA USERS APPENDIX A HANDSHAKING ALGORITHMS APPENDIX B DOCUMENT TYPE DEFINITIONS FOR XML FORMATTED REPORTS APPENDIX C DESCRIPTION OF MESSAGE FORMATS APPENDIX D BACKWARDS COMPATIBILITY NAL Research Corporation (TN V6.1) 2

3 1.0 INTRODUCTION The 9601-DGS, 9601-DGS-LP, 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, a laptop or a desktop with an attached tracker. NAL Research provides the Server for Trackers software with the intent of allowing users to quickly install on their NOCs for command/control of and receiving GPS reports from remote trackers. The DGS and 9601-DGS-LP satellite trackers can be loaded with firmware to support transmission of GPS reports in either standard format or 256-bit AES encrypted format. There are two versions of Server for Trackers to support each of the 9601-DGS and 9601-DGS-LP firmware standard Server for Trackers and Server for Trackers with encryption. Unless otherwise noted, comments in this manual are applicable to both software versions. With Server for Trackers software, a NOC can take full advantage of all features offered by the DGS, 9601-DGS-LP, A3LA-DGS and A3LA-TSS such as near real-time SBD tracking mode, real-time 2Way tracking mode and chatting mode. In addition, the program allows a NOC to communicate with modems attached to its serial ports, to communicate with POP3/SMTP servers, to communicate using the Iridium SBD DirectIP protocol, and to act as a RUDICS server/client to support incoming and outgoing communications with the trackers. Users can also develop their own application software more specific to their operating environments with information provided here. There are differences in the hardware design and communication capabilities for each of the four Iridium trackers. Below is a quick reference of their basic differences. Users are encouraged to thoroughly read the manuals provided with each model. Latest software releases and manuals can also be found 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 and communication statuses. d. MIL-STD-810F certified. e. Capable of two-way communications employing either standard compressed protocol or 256-bit AES encryption protocol. f. Small in form-factor, low in cost and low in power consumption. g. Compressed 30-byte GPS report to reduce SBD airtime cost. h. When not in tracking mode, can operate as a 9601-D or a 9601-DG. i. Does not support voice call. j. Sensitive GPS receiver (142dBm). NAL Research Corporation (TN V6.1) 3

4 DGS-LP Tracker: a. Capable of two-way communications ONLY under SBD. b. Has Alert/Emergency/Test switch. c. Has LEDs to display networks and communication statuses. d. MIL-STD-810F certified. e. Capable of two-way communications employing either standard compressed protocol or 256-bit AES encryption protocol. f. Small in form-factor, low in cost and low in power consumption. g. Compressed 30-byte GPS report to reduce SBD airtime cost. h. When not in tracking mode, can operate as a 9601-D or a 9601-DG. i. Does not support voice call. j. Extremely low-power consumption hardware during sleep mode. k. Has input and output pins to enable state changes of peripheral devices. l. Has internal motion sensor. m. High sensitive GPS receiver (158dBm). 3. 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 sleeping or sending out a report, audio calls can be placed. 4. 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. Each NAL Research s satellite tracker has a unique set of operating modes and their brief descriptions are given below DGS and 9601-DGS-LP Modes of Operation: 1. Command mode accepts AT commands from a DTE (running either SatTerm or any terminal emulator software) to set up its operating parameters, send and receive SBD messages, and request GPS information. 2. Tracking mode a. Sends GPS reports via SBD to a NOC at a pre-programmed interval. GPS reports can be either in standard or encrypted format. Continuous (approximately once every four seconds) Emergency GPS reports are sent to a NOC when the alert switch is activated. Continuous Test GPS reports are sent to a NOC when the Test switch is activated. NAL Research Corporation (TN V6.1) 4

5 b. Accepts commands/instructions from a NOC for operating profile reconfiguration such as reporting interval. Commands/instructions can either be in standard or encrypted format. Either Utility Software for Trackers or Server for Trackers installed on the NOC can be used for remote-configuration of the 9601-DGS and 9601-DGS-LP. A3LA-DGS Modes of Operation: 1. Command mode a. Accepts AT commands from a DTE (running either Terminal Software or any terminal emulator software) to set up its operating parameters. b. Converts itself into an A3LA-D modem (Regular mode) when received a specific AT command from a DTE. c. Converts itself into an A3LA-DG modem (GPS mode) when received a specific AT command from a DTE. 2. Tracking mode a. Sends GPS reports via one of two Iridium communication links: (i) SBD or (ii) 2Way. 2Way can either be dial-up or RUDICS for truly real-time GPS reporting and the Server for Trackers software must be used by the NOC server computer. b. Allows real-time chatting between the tracker and the NOC. The tracker s DTE must be running Terminal Software and the NOC must be running the Server for Trackers software. c. Accepts commands/instructions from a NOC for operating profile reconfiguration. d. Accepts an interruption from an audio handset and allows a voice call to be placed. Once the voice call is completed, the Tracking mode is resumed. A3LA-TSS Modes of Operation: 1. Command mode a. Accepts AT commands from a DTE (running either Terminal Software or any terminal emulator software) to set up its operating parameters. b. Accepts AT commands to retrieve GPS information. 2. Tracking mode a. Sends GPS reports via either SBD or SMS. b. Allows chatting between the tracker and the NOC. The tracker s DTE must be running Terminal Software and the NOC must be running the Server for Trackers software. c. Accepts commands/instructions from a NOC for operating profile reconfiguration d. Accepts a simultaneous audio call from handset during Tracking mode NOTE: The Server for Trackers no longer offers the TerminalModem COM object. If you are using a program that relies on the TerminalModem COM object, please contact NAL Research Corporation for help. NAL Research Corporation (TN V6.1) 5

6 2.0 GETTING STARTED 2.1 System Requirements Before installing the Server for Trackers software, make sure the NOC server computer meets the following requirements: Windows Vista/XP/2000/NT Pentium II 300MHz with 256MB of RAM 4MB video card with DirectX Version 9.0 or higher Minimum of 8MB available on hard drive 800 x 600 screen resolution (looks best with a screen resolution of at least 1024 x 768) NOTE: The Server for Trackers software may not displayed correctly on computers with older versions of DirectX. If this occurs, please go to and download the latest version of DirectX. 2.2 Installation The CD-ROM provided by NAL Research has two Server for Trackers Setup programs a standard version and a version with encryption. To install simply double click on the appropriate Setup program. Both programs can also be installed on the NOC computer. NAL Research Corporation (TN V6.1) 6

7 3.0 USING THE PROGRAM 3.1 Running the Server for Trackers Software Once installed, the Server for Trackers software can be accessed from the Windows start button/all Programs/NAL Research folder. The software may also be started by double clicking on any of the Session files; which are explained below. A startup screen, shown in Figure 1, will appear with four possible selections File, Communication, Options and Info. Figure 1. Startup screen of the Server for Trackers software. When the Server for Trackers software is opened, a default session file is loaded. The default session is stored as Default.gts in the Session subfolder of the installation directory. Session files are XML 1.0 compliance with.gts extension, which stands for GPS Server for Trackers Session. The information stored in a.gts session file includes: All of the information of the Configure Communication Links screen Status of the Log Reports to a Single File option Log File Name Status of the Log Reports to Individual Files option Logging Directory Logging ID Status of the Batch File option Batch File Name Message Format option 2Way Transmission Mode option Remote Change List File Name NAL Research Corporation (TN V6.1) 7

8 Number List from the Contact Remote Modems screen Whether to use Encryption (Used if Server for Trackers has Encryption option) Kind of Dialog Box Displayed when Opening or Saving Files 3.2 File Menu New Session/Open Session/Save Session/Exit The following options are available under the File Menu: New Session: Choose this option to create a new.gts session file. Open Session: Choose this option to load an existing.gts session file at run time. Save Session: Choose this option to save a.gts session file. Exit: Terminate and close the Server for Trackers software. 3.3 Communication Menu Configure Communications Links Depending on the models of the trackers, a NOC has four choices to communicate with remote satellite trackers as displayed in Table 1 via modems (either landline and/or Iridium modems) connected to its computer s serial ports, via accounts, via SBD DirectIP, or via RUDICS. The Communication menu allows the setup of these communication types. When Communication menu is selected, the Configure Communication Links submenu appears as shown in Figure 2. Figure 2. Configure Communication Links Submenu. NAL Research Corporation (TN V6.1) 8

9 LINKS TYPE Server Modems Accounts SBD DirectIP RUDICS Account DESCRIPTIONS OF USAGE 1. Receive GPS reports from A3LA-DGS trackers via dial-up connections. 2. Send configuration updates to A3LA-DGS trackers via dial-up connections. 3. Initiate dial-up connections for chatting with A3LA-DGS trackers. 4. Receive GPS reports or Emergency reports from A3LA-TSS trackers via SMS. 5. Send configuration updates to A3LA-TSS trackers via SMS. 6. Initiate on-demand GPS reports from A3LA-TSS trackers via SMS. 7. Chat with A3LA-TSS trackers via SMS. 1. Receive GPS reports, Emergency reports or Test reports from 9601-DGS, DGS-LP, A3LA-DGS or A3LA-TSS trackers via SBD. 2. Send configuration updates to 9601-DGS, 9601-DGS-LP or A3LA-DGS trackers via SBD. 3. Receive GPS reports or Emergency reports from A3LA-TSS trackers via SMS. 4. Send configuration updates to A3LA-TSS trackers via SMS. 5. Initiate on-demand GPS reports from A3LA-TSS trackers via SMS. 6. Chat with A3LA-TSS trackers via SMS. 1. Receive GPS reports, Emergency reports or Test reports from 9601-DGS, DGS-LP, A3LA-DGS or A3LA-TSS. 2. Send configuration updates to 9601-DGS or 9601-DGS-LP trackers via SBD. 1. Receive GPS reports from A3LA-DGS trackers via RUDICS connections. 2. Initiate RUDICS connections with A3LA-DGS trackers. 3. Chat with A3LA-DGS trackers via RUDICS connections. 4. Send configuration updates to A3LA-DGS trackers via RUDICS connections. Table 1. Description of the types of communication links between a NOC and remote trackers. NAL Research Corporation (TN V6.1) 9

10 Figure 2. Configure Communication Links Submenu. Data entered with the Configure Communication Links submenu are automatically used by other parts of the Server for Trackers program. This approach requires information to be entered only once at a central place. Therefore, if an error is encountered while running any part of the Server for Trackers program, the Configure Communication Links screen should be re-checked to make sure that the correct information is entered. Any of the Configure Communication Links options not used should be left blank or left with the default values. However, before the Server for Trackers program can retrieve GPS reports, one or more of the Configure Communication Links boxes must be setup, which will be discussed in the following sections. Communication Menu Configure Communication Links /Server Modems The upper half of the Configure Communication Links screen is used to setup modems and accounts. This section will focus on setting up server modems connected to the NOC s server computer allowing the NOC to communicate with the remote satellite trackers. The Server for Trackers software supports all Iridium A3LA modem series and most but not all Hayes-compatible landline modems. The program permits multiple server modems operating simultaneously. To add a server modem to the Server for Trackers software, click the Add Server Modem button. The program will determine the available serial ports on the NOC s server computer and then pops up the Add Server Modem window as shown in Figure 3. Select a serial port from the pull-down menu and enter its properties in the boxes below. Once all the serial port information is entered, click the Add button to finish. The modem along with its corresponding serial port assignment will appear under the Server Modems screen indicating a successful installation. The process can be repeated for each modem. Table 2 has the descriptions of the required server modem properties. NAL Research Corporation (TN V6.1) 10

11 PROPERTIES COM port Baud Rate Parity Data bits Stop bits Receive SMS Messages Manage Connection for Satellite Modems Automatically Answer Calls with ATS0=1 DESCRIPTIONS Serial port of the NOC s server computer that the modem is connected to. Baud rate between the modem and NOC s server computer. MUST BE FOR IRIDIUM SATELLITE MODEMS. Parity setting of the modem. MUST BE None FOR SATELLITE MODEMS. Data bits setting of the modem. MUST BE 8 FOR SATELLITE MODEMS. Stop bits setting of the modem. MUST BE 1 FOR SATELLITE MODEMS. This option instructs the Server for Trackers software to set up the modem to receive SMS messages immediately without storing them in the SMS memory by executing the AT+CMNI=2,2 command. This option is required for server modems to communicate with A3LA-TSS trackers by SMS. This option instructs the Server for Trackers software to check for the satellite signal strength occasionally with the AT+CSQ command. If the satellite connection has been lost, the program will renegotiate the connection with the AT+COPS=1 command. This option should only be used with satellite modems. If this option is selected, the program will use the ATS0=1 command to cause the server modem to automatically answer calls after one ring. This option should be selected if the server modem is to be used to receive reports in 2Way connections. Table 2. Description of the Server Modem properties. NAL Research Corporation (TN V6.1) 11

12 After a server modem is added, the COM port is automatically opened and remains open with the entered settings until the server modem is removed. At this point, only the Receive SMS Messages, the Automatically Answer Calls with ATS0=1 and the Manage Connection for Satellite Modems options can be modified by highlighting the appropriate modem under the modem/ account list and click the Edit button. If other properties of the server modem need to be changed, then the server modem has to be removed first from the Server Modems screen and then added again with a different set of properties. NOTE: After a server modem has been added, it does not necessarily mean that it is ready to be used. It only means that the Server for Trackers software has successfully established communications with the COM port. Users must ensure correct connections between each COM port and its corresponding server modem. The most common mistake made is to NOT turn power to the external modems ON. AT+CMNI=2,2 Causes the modem to receive SMS messages immediately without storing them in the SMS memory. If this command returns an error, it may be because the SMS memory is full. Any serial communications program, such as SatTerm (from NAL Research) or HyperTerminal can be used to view/delete messages in the SMS memory. Use the AT+CMGL=4 command to list all of the messages in the SMS memory. This command will show the message number followed by the message. Then use the AT+CMGD=# command, where # is the number of the message to delete. +CMT Displayed when an SMS message is received. AT+CMGS Sends an SMS message. +CMS ERROR:331 No network service. This usually means that the modem is not getting strong enough signal strength. +CMS ERROR:300 Phone failure. This does not necessarily mean that the command did not work. However, the program will assume that the command did not work. If this error continues to occur, restarting the modem will most likely get rid of it. If restarting the modem does not fix the problem, try deleting some messages from the SMS memory as described in the description of the AT+CMNI=2,2 command. +CMS ERROR:302 Operation not allowed. This does not necessarily mean that the command did not work. However, the program will assume that the command did not work. If this error continues to occur, restarting the modem will most likely get rid of it. If restarting the modem does not fix the problem, try deleting some messages from the SMS memory as described in the description of the AT+CMNI=2,2 command. Table 3. Understanding and troubleshooting SMS commands and errors. NAL Research Corporation (TN V6.1) 12

13 Communication Menu Configure Communication Links / Accounts The Server for Trackers software can use multiple accounts to communicate with the remote trackers. To add an account to the Server for Trackers software, click the Add Account button. The program will pop up the Add Account window as shown in Figure 4. Enter information in the empty boxes under either Information for Retrieving or Information for Sending or both. Once all the information is entered, click the Add button to finish. The newly created account will appear under the Accounts screen indicating a successful installation. The process can be repeated for additional accounts. Table 4 has the descriptions of the required properties. Figure 4. Add Account Menu NAL Research Corporation (TN V6.1) 13

14 PROPERTIES Display Name POP3 Server User Name Password Delete Mail on Server Auto Retrieve Frequency Auto Retrieve Enabled / Disabled SMTP Server From Address DESCRIPTIONS Any unique name assigned to this account. Address or domain name of the POP3 server. User name required for signing into the POP3 server. Password required for signing into the POP3 server. If set to Yes, messages from the POP3 server will be deleted after retrieved by the Server for Trackers. If set to No, messages from the POP3 server will be left alone after retrieved by the Server for Trackers. The Server for Trackers program will also mark already retrieved messages so that they will not be downloaded again. The retrieval process may be slowed down if too many messages build up on the POP3 server. Frequency in minutes between each POP3 server check (0 minutes means continuously checking messages on the POP3 server). If Enabled, the program will automatically login to the POP3 server to retrieve e- mails at the frequency given by the Frequency field. If Disabled, can be manually retrieved by selecting the account on the main window in the Current Activity list and clicking the Retrieve button. Address or domain name of the SMTP server. address used to send messages to remote trackers. The Iridium gateway requires a valid From Address for error acknowledgment. The From Address is also needed for the NOC to chat with a remote A3LA-TSS tracker. Table 4. Description of the properties. After an account is added, it can be edited by highlighting the appropriate account under the modem/ accounts list and clicking on the Edit button. Any of the properties can be changed. However, the display name must be unique among all of the other accounts. The status of the POP3 and SMTP clients as well as accounts on the POP3 server can be viewed from the main window in the Current Activity screen. If there was an error in the operation of the POP3 or SMTP client, they will be displayed. The counts in the Last column are the counts for the last connection to the POP3 server. The Filtered Out s are those s which are not needed by the program and therefore were not retrieved. The Already Retrieved s are those s which have been retrieved by the program and will not be retrieved again. Communication Menu Configure Communications Links /SBD DirectIP A NOC server can communicate with remote satellite trackers using the SBD DirectIP protocol. SBD DirectIP allows SBD messages to be sent and received via IP address instead of account. To setup Server for Trackers for receiving SBD DirectIP traffic, the local IP address of the machine running the Server NAL Research Corporation (TN V6.1) 14

15 for Trackers software must be entered in the Server Account IP Address text box. Then an open port must be entered in the Port text box. Make sure that a firewall or router is not blocking traffic through this port or the server will not receive SBD messages. When the server is ready to accept DirectIP traffic, check the Listen selection box. An error will appear if an incorrect IP address has been entered. To configure Server for Trackers to use SBD DirectIP as an outgoing communications link, enter the IP address of the remote network. This can be either the IP address of the Iridium gateway or NAL Research s proxy server. In the Client Account: Port text box enter the port on the remote machine to connect to in the Client Account: Port text box. Communication Menu Configure Communications Links /RUDICS Account A NOC server can communicate with remote satellite trackers using RUDICS. RUDICS is a modem emulator maintained by the Iridium gateway allowing socket connection over the Internet. Whereas a COM port connects the NOC server to an actual modem, a socket connection connects the NOC server to the RUDICS system as shown in Figure 5. Iridium Network RUDICS Telnet A3LA-DGS DNIS (Group #) Local IP Address Local Port MSISDN-C Server IP Address Server Ports RUDICS Enabled SIM Card NOC Server Figure 5. RUDICS operational diagram. Prior to setting up a RUDICS account by an Iridium Service Provider, the following information must be given by the account holder: SIM cards to be enabled for that particular RUDICS account, the NOC IP address (Server Account: IP Address) and the NOC port (Server Account: Port). Once a RUDICS account has been setup, the following information is given to the account holder: DNIS (Group #), RUDICS IP address (Client Account: IP Address) and RUDICS ports (Client Account: Ports). As shown in the diagram below, when an A3LA-DGS tracker places a RUDICS call to the NOC server, it must have a RUDICS enabled SIM card installed. The RUDICS system at the Iridium gateway then uses the Server Account: IP Address and the Server Account: Port to initiate a socket connection with the NOC server. When the NOC server places a RUDICS call to an A3LA-DGS tracker, the NOC server must first establish a socket connection with the RUDICS system using the RUDICS Client Account: IP Address and the RUDICS Client Account: Ports. After connecting to the RUDICS server, the NOC server can dial the MSISDN-C number of A3LA-DGS to connect. NAL Research Corporation (TN V6.1) 15

16 To setup the Server for Trackers to use a RUDICS account, enter the NOC Server Account: IP Address, the NOC Server Account: Port, the RUDICS Client Account: IP Address, and the RUDICS Client Account: Ports in the Configure Communication Links/RUDICS Account screen. To accept connections from remote A3LA-DGS trackers, check the Listen selection box. Uncheck the Listen selection box to stop listening for RUDICS connection attempts. NOTE: If there is a firewall on the NOC server, it may prevent RUDICS connections. If a RUDICS account is being used, the firewall should be configured to allow RUDICS connections. 3.4 Options Menu GPS Options Menu/GPS/Batch File A Batch File contains a batch program or a user-defined program that gets executed as soon as a GPS report arrives at the NOC server computer from remote trackers. The Batch File may be either a command line batch file (.BAT) or a Windows executable file (.EXE). As the tracker receives GPS reports, each report executes a single instance of the batch file. When the batch file executes, the report is passed as a parameter to the batch program or user-defined program. For example, the Batch File could be an ftp program sending the current GPS report to multiple servers via ftp each time a GPS report is received by the NOC server computer. Or perhaps it could be a mapping program reading, manipulating and displaying realtime incoming GPS reports. The Batch File can be specified by choosing Options Menu/GPS/Batch File/Select Batch File. The name of the current Batch File will be displayed near the bottom of the main window. The Batch File can be toggled ON/OFF by selecting Options Menu/GPS/Batch File/Batch File Toggle. If the Batch File is toggled off, the Batch File label at the bottom of the main window will be grayed out. If the encryption version of the Server for Trackers software is used then the encrypted GPS reports arriving at the NOC server computer will be decrypted before sending to the batch file. NOTE: The.BAT batch files need to be named such that they have the same name with the command line as with Windows or the batch file will not be executed. If a batch file is not executing properly, try applying the following naming conventions to the batch file and folder where it is located: The file name should be no more than 8 characters with no spaces and a 3 character extension. (i.e. BATCH001.BAT) The folder name and all parent folders should be no more than 8 characters with no spaces. Also, note that a Windows executable is the method of choice for most using the Batch File functionality. The format of the GPS report that is sent to the batch file can be selected by checking the options Send Reports to Batch File in Message Format and Send Reports to Batch File in Hex Format. If both options are selected both will be sent as parameters. If no format option is selected, the batch file will still execute, but there will be no parameters sent. The Send Reports to Batch File in Message Format option sends GPS reports in the message format selected in the Message Format menu. (See section 3.6 for details) The Send Reports to Batch File in Hex Format option sends the GPS report as a hexadecimal representation of the GPS report binary data. NAL Research Corporation (TN V6.1) 16

17 3.4.2 Options Menu/GPS/Logging Options Menu/GPS/ Logging/Log Reports to a Single File The Log Reports to a Single File option will force all GPS reports and chatting messages to be saved to a log file. This option requires that a log file be specified by choosing Options Menu/GPS/Logging/Logging Setup.... The name of the current log file will be displayed near the bottom of the main window and will be grayed out if not being used. Since GPS reports can arrive simultaneously through different communication links, logging is done with XML elements in order to group the related GPS reports while keeping the log files as sequential as possible. However, the log files are not guaranteed to be XML compliant. The main element used is the Session element. All other elements are contained inside of a Session element. A Session element is appended to the log file every time an SBD or an SMS transaction occurs, every time a 2Way connection ends, and every five minutes in a 2Way continuous GPS reporting or chatting mode. The Session element has several attributes that keep the log file organized and sequential. These attributes are described below in Table 5. ATTRIBUTE VALUES DESCRIPTIONS Protocol 2Way, SBD, SMS Identifies the connection type of a remote tracker. CommLink RemoteModem Server Modem (n) Account (n) RUDICS Session (n) Identifier (n) IMEI Number (n) Phone Number (n) Identifies the communication link of the NOC server. For server modems, n is the COM port the NOC server modem connected to. For accounts, n is the unique display name given to identify the account. For RUDICS session, n is the port being used on the RUDICS system. Identifies remote tracker. In the values, n represents the identifier, IMEI number, or phone number of the remote tracker. Duration Integer >= 0 Continued 1 The duration of the connection in seconds. This attribute is only used when Protocol is 2Way and Continued is not displayed. This is displayed only if the Protocol is 2Way and the remote tracker is still in a connection with the NOC server at the time that the session element was logged. Table 5. Attributes of the Session Element. Another element used is the MsgFormat element. This element indicates the current message format and is included at the beginning of every Session element as well as being added every time the format changes. The possible values of the MsgFormat element are the names of the nineteen Message Formats. Chatting information is logged with Chat elements. The Chat element has several attributes which identify the type of chatting information. These attributes are shown in Table 6 below. NAL Research Corporation (TN V6.1) 17

18 ATTRIBUTE VALUES DESCRIPTIONS Sent 0, 1 Normally 0 means that the element contains a chat message that was received and 1 means that the element contains a chat message that was sent. However, if Sent is 0 and the RefNum, Checksum, and Length attributes are present, the element represents a response to a sent SMS chat message with the same RefNum, Checksum, and Length. If this is the case, then the element is empty. RefNum Checksum Length Two character hexadecimal number. Four character hexadecimal number. Two character hexadecimal number. This is used for keeping track of the order of SMS chat messages. Only used for SMS chatting. These two attributes are used for matching sent SMS chat messages with responses, from the remote tracker, that indicate that the message was received. Therefore, they only appear when an SMS chat message is sent or a response to a sent SMS chat message is received. They are not present if an SMS chat message is received. Only used for SMS chatting. Table 6. Attributes of the Chat Element All data inside of a Session element that is not part of another element belongs to GPS reports formatted in the current message format. If the Server for Trackers has the encryption feature then reports arriving as encrypted reports will be sent to the log file in a decrypted format. Options Menu/GPS/ Logging/Log Reports to Individual Files The Log Reports to Individual Files option will force each GPS report to be logged to its own individual file. A sequential record is kept by including the local time in the name of each file when it is created. This option requires that a logging directory and a logging id be specified by choosing Options Menu/GPS/Logging/Logging Setup.... The logging directory is the directory that will contain all of the individual log files. The logging id will be included in the name of each file, so that, in the case of two Server for Trackers running at the same time and using the same logging directory, the individual log files can be easily distinguished by the logging id. Each time a GPS report is received, a new log file is created with a unique name determined by the logging id, date, and time as follows... NALServer{Logging Id}_{YYYY}{MM}{DD}{HH}{MM}{SS}_{Counter}.txt where {YYYY} is the current year {MM} is the current month {DD} is the current day {HH} is the current hour using a 24 hour clock {MM} is the current minute NAL Research Corporation (TN V6.1) 18

19 {SS} is the current second {Counter} is a counter starting at 1 The GPS report is logged to the newly created file inside of a Session element (see the previous section about logging to a single log file for information). The Duration and Continued attributes will never be present in an individual log file. If the Server for Trackers has the encryption feature then reports arriving as encrypted reports will be sent to the log files in a decrypted format. 3.5 Options Menu Data The Options/Data menu provides the user the ability to log and pass to a batch file data other than tracking messages. Tracking messages are modem communications, the most common of which being GPS reports, sent from a tracker to the Server for Trackers containing information such as the location or operational settings of the tracker. Whereas the settings under Options/GPS provide for logging and batch file execution using GPS reports only, the options which appear under the Options/Data menu provide for logging and batch file execution using other incoming communications as well as GPS reports. Some forms of incoming communications other than tracking messages include SMS and SBD messages. The options under this menu do not provide the capability of recording chat sessions Options Menu/Data/Record All Record All instructs the Server for Trackers to log all incoming data applicable to this menu option, including tracking messages. Furthermore, if Options/Data/Batch File/Batch File Toggle is enabled, all incoming communications will be sent as parameters to the batch file specified in Options Menu/Data/Batch File/Batch Setup Options Menu/Data/Batch File Batch files are thoroughly explained in section The parameters sent to the batch file specified in Options/Data/Batch File/Batch Setup will be formatted in hexadecimal characters. Every byte of the received communication will be represented by two uppercase hexadecimal characters which will be passed as an argument to the batch file. Unlike the Options/GPS/Batch File, the status of the Data batch file will not be visible at the bottom of the Server for Trackers main window. Options Menu/Data/Batch File /Batch File Toggle This option provides the capability of toggling the batch file ON/OFF. If the encryption version of the Server for Trackers software is used then the encrypted data arriving at the NOC server computer will be decrypted before sending to the batch file. Options Menu/Data/Batch File /Batch Setup This menu item simply allows the user to select a batch file to which the received data will be sent as parameters Options Menu/Data/Logging Each received communication will be saved to a separate file ending in the extension.dat. Each time a communication is received, a new log file is created with a unique name determined by the IMEI, time stamp, and counter as follows... d_{iiiiiiiiiiiiiii}_{yyyy}{mm}{dd}{hh}{mm}{ssss}_{counter}.dat NAL Research Corporation (TN V6.1) 19

20 where {IIIIIIIIIIIIIII} is the IMEI of the tracker from which the communication originated {YYYY}{MM}{DD}{HH}{MM}{SSSS} is the time stamp in GMT Time where {YYYY} is the year {MM} is the month {DD} is the day {HH} is the hour {MM} are the minutes {SSSS} are the fractions of a second {COUNTER} is the number of communications received since the Server for Trackers program began Example: d_ _ _23.dat The leading character of the file name, d, is reserved; it has not been used to head information previously and will not be used subsequently. Therefore files beginning with this letter can be discarded by applications that do not wish to process this data. Unlike GPS logging, there is no formatting applied to the.dat files; each file is simply the stream of bytes from the received communication. Options Menu/Data/Logging/ Log Data Toggle This option toggles the logging of received communications ON/OFF. If the encryption version of the Server for Trackers software is used then the encrypted data arriving at the NOC server computer will be decrypted before sending to the log file. Options Menu/Data/Logging/Logging Setup This option allows the user to set the directory where the.dat files will be stored. 3.6 Options Menu Message Format There are nineteen available formats each incoming GPS reports can be displayed or translated to. The Message Format option specifies the type of format incoming GPS reports is to be translated to by the Server for Tracker program. The GPS reports are translated before being displayed on the screen, logged, or sent to a batch file. See APPENDIX C DESCRIPTION OF MESSAGE FORMATS for more information about these message formats. 3.7 Options Menu 2Way Transmission Mode Options Menu 2Way Transmission Mode/Use Remote Change List/Continuous/Standard The 2Way Transmission Mode defines the protocol (see Appendix B more for more details) used to communicate with a remote A3LA-DGS tracker while connecting to the Server for Trackers program. The 2Way Transmission Mode only affects new connections; changing the transmission mode will not change how existing connections are handled. Three modes can be selected through the Options/2Way Transmission Mode menu. Standard: This mode instructs the Server for Trackers program to play a passive role by simply waiting to receive incoming GPS reports at a preprogrammed schedule from the remote A3LA-DGS trackers without sending back any special instructions or commands to the A3LA-DGS trackers. NAL Research Corporation (TN V6.1) 20

21 Continuous: In this mode, when a remote A3LA-DGS tracker connects to the NOC server computer at a preprogrammed schedule and starts to send over the first GPS report, the Server for Trackers program immediately sends back a command to instruct the A3LA-DGS tracker to maintain the connection and continuously send GPS reports faster than once a second. To terminate this mode, select the appropriate communication link in the Current Activity list box in and click the Hangup button on the main window. The remote A3LA-DGS tracker reverts back to its original preprogrammed GPS report schedule. Use Remote Change List: This mode allows the Server for Trackers program to modify the start-up parameters of the remote A3LA-DGS trackers or causes the trackers to start transmitting GPS reports continuously based on the tracker identifiers. Each time an A3LA-DGS gets connected and delivers a GPS report, the Server for Trackers searches the loaded Remote Change List for the identifier of the call-in A3LA-DGS. If the Server for Tracker finds a pending action for that particular remote A3LA-DGS tracker in the Remote Change List, the Server for Trackers will either send an update of the start-up parameters or a command to request for continuous transmission of GPS reports. If an update is successfully sent, the remote A3LA-DGS tracker will modify and store in its own non-volatile memory the new values and starts using the updated parameters. The next section has a detailed description on how to configure the Remote Change List. Options Menu 2Way Transmission Mode/Configure Remote Change Lists A Remote Change List can be created, deleted, edited, loaded or unloaded using the Option Menu/2Way Transmission Mode/Configure Remote Change Lists. When the Configure Remote Change Lists is chosen, a window as shown in Figure 6 will appear. Each Remote Change List (or file) is stored in a plain text XML file with an.rcl extension. The.rcl file is password protected. Although.rcl files are plain text, they must be modified with Server for Trackers program; otherwise, they will be rendered unusable by the Server for Trackers. The Remote Change List also has information regarding the status of changes of each A3LA-DGS. This allows the user to see what changes were made and which are still in pending. On the Configure Remote Changes window, there are several buttons for managing the currently loaded Remote Change List (or file) and stored Remote Change Lists (or files) which explained below. New and Delete buttons: The New button creates a new Remote Change List, while the Delete button removes an existing Remote Change List. A password must be provided when creating a new Remote Change List. The password must be entered twice for confirmation. Edit button: This button allows the user to edit a Remote Change List by opening the Edit Remote Changes window, which is explained in the next section. The correct password for the Remote Change List must be provided in order to edit the list. Load and Unload buttons: The Load button loads a Remote Change List into memory, while the Unload button clears the Remote Change List from memory. The Load button is available for all Remote Change Lists except the one that is currently loaded, while the Unload button is only available for the Remote Change List that is loaded. Only one Remote Change List can be loaded into memory at a time. Therefore, loading a Remote Change List will automatically unload NAL Research Corporation (TN V6.1) 21

22 the currently loaded Remote Change List. The Remote Change List that is loaded into memory will be used to make changes to remote A3LA-DGS tracker whenever the transmission mode is set to Use Remote Change List... Locate button: The Locate button identifies the location where the Remote Change List is stored (drive and directory). NOTE: The currently loaded Remote Change List cannot be deleted, edited, loaded, or unloaded while the transmission mode is Use Remote Change List.... NOTE: Since remote updates have precedence over chatting, a remote update can occur while attempting to initiate a Chat Session and will prevent the NOC server from requesting chat mode. Options Menu 2Way Transmission Mode/Configure Remote Change Lists /Edit Remote Change Lists A Remote Change List can be edited by choosing the Edit button from the Options Menu/2Way Transmission Mode/Configure Remote Change Lists screen. The password used to create the Remote Change List is required. A window similar to the one shown in Figure 7 will appear. In the Edit Remote Changes window, all of the A3LA-DGS Identifiers in the Remote Change List will be displayed. The Add button allows users to add a new Identifier. The name of an existing Identifier can be modified by double clicking on the Identifier and entering a new one. When an A3LA-DGS Identifier is selected, the changes that apply to it are shown below in their respective fields. If multiple A3LA-DGS NAL Research Corporation (TN V6.1) 22

23 Identifiers are selected, a red asterisk will appear next to the fields for which not all Identifiers have the save value. Making a change to any field will cause the change to be made for all A3LA-DGS Identifiers that are selected. Add, Delete, and Select All buttons: The Add button adds an A3LA-DGS Identifier to the list, the Delete button deletes an A3LA-DGS Identifier from the list, and the Select All button selects all of the A3LA-DGS Identifiers in the list. OK, Cancel, and Apply buttons: These buttons are used to accept or cancel changes made to the Remote Change List. No changes are made to the actual file until the Apply or OK button is clicked. Once the Apply or OK button is clicked, changes are made to the actual file and cannot be undone except manually. The only difference between the Apply and OK buttons is that the OK button closes the window, while the Apply button keeps it open. The Cancel button cancels all changes made to the Remote Change List since the last Apply button was clicked and closes the window. NAL Research Corporation (TN V6.1) 23

24 The following is a list of fields used to change an A3LA-DGS settings, along with the default values given to them when a new A3LA-DGS Identifier is added to a Remote Change List. Type of Change field (Default: No Change): This field is used to determine what will happen when the Server for Trackers finds the remote A3LA-DGS Identifier in the Remote Change List. If the Type of Change is Continuous, the software will cause the remote A3LA-DGS to transmit reports continuously. If the Type of Change is Remote Update, the software will attempt to update the remote A3LA-DGS settings. If the Type of Change is No Change, the software will not affect the remote A3LA-DGS. Status field (Default: N/A) and Reset button: The Status field shows whether or not a change has been made to a remote A3LA-DGS. This field is only applicable to the A3LA-DGS Identifiers with the Remote Update type of change. If the changes have been made, the field will display Change Completed. Otherwise, it will display Change Pending. The status will change back to Change Pending whenever any field for the A3LA-DGS Identifier is modified. Alternatively, the status can be changed back to Change Pending, without changing any fields, by clicking the Reset button. Remote Modem Password field (Default: ): This field holds the password for the A3LA- DGS Identifier. The password is given to the A3LA-DGS during setup using the Terminal Software for PC or A3LA-DGS Terminal Software for PDA. The password is only needed and enabled for the A3LA-DGS Identifiers with the Remote Update type of change. When the Server for Trackers attempts to make a change to the remote A3LA-DGS start-up parameters, the remote A3LA-DGS first verifies if the password is correct before making any changes. Update Number to Dial field (Default: No): This field determines whether or not the number to dial is updated when the Type of Change is Remote Update. Number to Dial field (Default: ): This field holds the number to be used when updating the number to dial. Remote Modem Calls Satellite or Landline (Default: Satellite): This field indicates the type of modem for the Number to Dial. If the remote modem s version is 2.0 or 2.1 this field is ignored. Update Frequency field (Default: No): This field determines whether or not the time between calls and number of tries is updated when the Type of Change is Remote Update. Time between Calls field (Default: 1): These fields hold the frequency to be used when updating the time between calls. Number of Tries field (Default: 1): This field determines the number of times that the remote A3LA-DGS will try to make a GPS report when it fails to complete a report or when it gets an Invalid Position Fix. If the remote modem s version is 2.0 or 2.1 this field is ignored. This section presents an example, step by step, of how to create, edit, and use a Remote Change List to change the report frequency of a remote A3LA-DGS. A3LA-DGS #1: Identifier = Modem A Number to Dial = Number of the server modem NAL Research Corporation (TN V6.1) 24

25 GPS Report Frequency = 1 minute Password = abcdefgh A3LA-DGS #2: Identifier = Modem B Number to Dial = Number of the server modem GPS Report Frequency = 5 minutes Password = abcdefgh A3LA-DGS #3: Identifier = Modem C Number to Dial = Number of the server modem GPS Report Frequency = 8 minutes Password = abcdefgh Step 1: Create a new Remote Change List Choose the Options/2Way Transmission Mode/Configure Remote Change Lists. In the Configure Remote Changes window, click the New button. In the Choose a File window, enter Test for the file name and click the Open button. In the Enter Password window, enter in both password boxes and click OK. The Remote Change List has now been created and should appear in the Remote Change Files on the Configure Remote Changes window. However, it needs to have a list of A3LA-DGS Identifiers to be useful. Step 2: Adding Identifiers to the Remote Change List Select Test.rcl in the Remote Change Files list box and click the Edit button. In the Enter Password window, enter for the password and click OK button. In the Edit Remote Changes window, click the Add button. Type Modem A and hit the ENTER/RETURN key. Click the Add button again. Type Modem B and hit the ENTER/RETURN key. There should now be a list of two identifiers. However, no updates will be made unless they are specified. Step 3: Specify an update in the Remote Change List Select the Modem A Identifier in the Modem Identifiers list box by clicking on it. Change the Type of Change to Remote Update. Change the time between calls to 5 minutes by clicking the up arrow on the Minutes box. Save the changes and close the Edit Remote Changes window by clicking OK button. Now, the Remote Change List is ready to be loaded. Step 4: Load the Remote Change List Select Test.rcl in the Remote Change Files list box. Click the Load button. In the Enter Password window, enter for the password and click the OK button. NAL Research Corporation (TN V6.1) 25

26 Even though the Remote Change List is loaded, it will not be effective until the transmission mode is changed to Use Remote Change List.... Step 5: Change the transmission mode Click the Close button to close the Configure Remote Changes window. Choose the Options Menu/2Way Transmission Mode/Use Remote Change List. Now that the Remote Change List is loaded and in use, the change will be made to the A3LA- DGS when it reports in. The following timeline shows what should happen as the A3LA-DGS call in. about 1 minute later A3LA-DGS with Identifier Modem A calls in. A3LA-DGS with Identifier Modem A delivers report. Server for Trackers finds Modem A in the Remote Change List. Server for Trackers updates the frequency of the A3LA-DGS with Identifier Modem A from 1 minute to 5 minutes. In the Remote Change List, the Status of Modem A is changed from Change Pending to Change Completed. A3LA-DGS with Identifier Modem A hangs up....about 4 minutes later A3LA-DGS with Identifier Modem B calls in. A3LA-DGS with Identifier Modem B delivers report. Server for Trackers finds Modem B in the Remote Change List. Sever for Terminals software does not update the A3LA-DGS with Identifier Modem B since the Type of Change is No Change. Nothing changes in the Remote Change List for the Modem B entry. A3LA-DGS with Identifier Modem B hangs up....about 1 minute later A3LA-DGS with Identifier Modem A calls in. A3LA-DGS with Identifier Modem A delivers report. Server for Trackers finds Modem A in the Remote Change List. Server for Trackers does not update the A3LA-DGS with Identifier Modem A since the Status is Change Completed. Nothing changes in the Remote Change List for the Modem A entry. A3LA-DGS with Identifier Modem A hangs up....about 2 minutes later A3LA-DGS with Identifier Modem C calls in. A3LA-DGS with Identifier Modem C delivers report. Server for Trackers does not find Modem C in the Remote Change List. Server for Trackers does not update the A3LA-DGS with Identifier Modem C since it is not in the Remote Change List. NAL Research Corporation (TN V6.1) 26

27 Nothing changes in the Remote Change List. A3LA-DGS with Identifier Modem C hangs up. Step 6: Verify that the changes were made Choose the Options Menu/2Way Transmission Mode/Standard. Choose the Options Menu/2Way Transmission Mode/Configure Remote Change Lists. Select Test.rcl in the Remote Change Files list box and click the Edit button. In the Enter Password window, enter for the password and click OK button. Select the Modem A Identifier in the Modem Identifiers list box by clicking on it. Check that the status for is Change Completed. 3.8 Options Menu Encryption (Models 9601-DGS and 9601-DGS-LP Only) This option is available only on the Server for Trackers with Encryption version and on the 9601-DGS or 9601-DGS-LP configured to send/receive encrypted information. After receiving the 9601-DGS or DGS-LP tracker from NAL Research, the Crypto Officer is required to setup <usernames>, <passwords>, <encryption key> and <decryption key> before use. After the initial setup, access to the encryption feature is possible only when the correct <username> and <password> are entered. When GPS reports are sent to the NOC computer, the Server for Trackers software will use the entered <username> and <password> with the IMEI number from the GPS reports to look up the decryption key, which is then used to automatically decrypt GPS messages. The <username> and <password> can also be specified when Server for Trackers program is executed from the command line or from a service. For example, NALServerforTrackers <session file> <user name> <password>. The Option/Encryption/Use Encryption allows encryption feature to be turned on and off. When selecting this option, <username> and <password> will be requested. File/Save Session is used to overwrite the default session file after encryption features are set. If the loaded session file is set to use encryption then <username> and <password> will be requested at login. The Option/Encryption/User Properties allows entry of the <username> and <password> that will be used to retrieve the encryption or decryption keys from the Encryption User Files. The Option/Encryption/Crypto Officer Properties will begin the Encryption Module. If Option/Encryption/Discard Non-Encrypted and Option/Encryption/Use Encryption are selected then non-encrypted incoming GPS reports will be discarded. If Option/Encryption/Discard Non-Encrypted is not selected then the Server for Trackers may receive information from encrypted and non-encrypted trackers. Details regarding encryption are intentionally left out in this section. Users can read the Encryption Module Manual TN V2.1.0 for more information. 3.9 Options Menu Contact Remote Modems If a remote 9601-DGS, 9601-DGS-LP, A3LA-DGS or A3LA-TSS has Callable property set to true, then it can be contacted by the Server for Trackers using Options/Contact Remote Modems window to request for on-demand GPS reports. Chatting can also be established with A3LA-DGS or A3LA-TSS under this window. When the Options/Contact Remote Modems window appears as shown below, a tracker type must first be chosen by clicking the Tracker Type box. After a tracker type is selected, a list of available communication links for the NOC computer will appear inside the Communication Link Used to Contact box NAL Research Corporation (TN V6.1) 27

28 in which the selected link will be used to call a remote tracker. The available communication links inside this box depends on what was entered under Communication/Configure Communication Links. The phone numbers of the remote A3LA-DGS and A3LA-TSS or IMEI numbers of the remote 9601-DGS and 9601-DGS- LP trackers can be entered under either the Number List or One Time Number field. Clicking the Insert button will allow an entry to be added to the Number List, while clicking the Delete button will delete the currently selected entry in the Number List. The Number List provides a convenient and easy recognition list of phone numbers and IMEI numbers for fast dialing. Every session file has a Number List associated with it. If the tracker type is A3LA-IGS/A3LA-DGS, the RUDICS Account will be available in the Communication Link Used to Contact list. NOTE: A SIM card inside the remote A3LA-DGS tracker has two numbers: MSISDN and MSISDN-C if the card supports both voice and data. The MSISDN number must be dialed if calling the remote tracker with an Iridium modem. The MSISDN-C number, along with the appropriate prefix, must be dialed if calling the remote tracker with a landline modem. To avoid high international airtime costs, an Iridium satellite modem should be used by the NOC server computer when calling remote trackers instead of a landline modem. If the RUDICS account is used to connect to the remote A3LA-DGS, then the MSISDN-C number should be used. If the card is only provisioned for data then the MSISDN-C number is used for both Iridium to Iridium calls and for calling the Iridium from a landline. Request a GPS Report from a Remote 9601-DGS or 9601-DG-LP Tracker To initiate an on-demand GPS report from 9601-DGS and 9601-DGS-LP trackers, follow the steps below: 1. Choose 9601-DGS from the Tracker Type box. 2. Choose a communication link from the Communication Link Used to Contact list. 3. Choose an IMEI number from the Number List or type an IMEI number in the One Time Number field. 4. Enter the correct 8-character Remote Update Password inside the Password box (default password is ). 5. Click the appropriate Ping button. The NOC server computer will send an SBD ping request to the 9601-DGS tracker using the selected communication link. If the 9601-DGS is not in sleep mode, it will immediately send a GPS report back to the NOC server computer. If it is in sleep mode, request is sent on the next report cycle. The 9601-DGS tracker will ignore a ping request(s) from the NOC server computer if Remote Update Password is incorrectly entered. Request a GPS Report from a Remote A3LA-DGS Tracker To initiate an on-demand GPS report from an A3LA-DGS tracker, follow the steps below: 1. Choose A3LA-IGS / A3LA-DGS from the Tracker Type box. 2. Choose a communication link from the Communication Link Used to Contact list. 3. Choose a number from the Number List or enter a number in the One Time Number field. 4. Click the appropriate Call button. NAL Research Corporation (TN V6.1) 28

29 The NOC server computer will place a call to the remote A3LA-DGS tracker using the selected communication link. Once a connection is established between the remote A3LA-DGS and NOC server computer, the tracker will immediately send a GPS report back to the NOC server computer. Initiating an on-demand GPS report from the remote A3LA-DGS tracker will restart the Time between Calls timer on the remote A3LA-DGS. Request a GPS Report from a Remote A3LA-TSS Tracker To initiate an on-demand GPS report from an A3LA-TSS tracker, follow the steps below: 1. Choose A3LA-TSS from the Tracker Type box. 2. Choose a communication link from the Communication Link Used to Contact list. 3. Choose a number from the Number List or type a number in the One Time Number field. 4. Click the appropriate Ping button. The NOC server computer will send an SMS ping request to the A3LA-TSS tracker using the selected communication link. Initiate Chatting with a Remote A3LA-DGS Tracker To establish a chat session between a remote A3LA-DGS tracker and the NOC server computer, follow the steps in Request a GPS Report from a Remote A3LA-DGS Tracker. However, Chat button should be clicked instead of the Call button. If the remote A3LA-DGS is capable of chatting (has firmware version 3.0 or higher and connected to NAL Terminal software) then chatting will begin. Once chatting has begun, the Chat window will appear on the NOC server computer. There is a separate Chat window for each chat session between a remote tracker and NOC server computer. Messages will be sent and received using the Chat window of Figure 8 below. While chatting, the remote A3LA-DGS will send over GPS reports approximately every ten seconds. Conversation Window: This window will display messages received from the A3LA-DGS tracker in red and messages sent from the NOC server computer s modem in blue. This window is only cleared when the Clear Conversation button is clicked. User may want to clear the conversation field with the Clear Conversation button for privacy. If a more permanent record of the conversation is desired, user may refer to the log file (see the section on the Log Reports to a Single File option for details). Content of chat message inside the Conversation window may also be copied with Ctrl+c. Message Window: Messages can be typed in the Message window even when not in chat mode. The length of messages is limited to 127 characters. The Message window is only cleared when the Clear Message button is clicked or the message was successfully sent, in which case, the message is moved to the Conversation window. Therefore, if the connection is lost unexpectedly while a message was being sent, the message will be left in the Message window so that the user may resend the message at a later time. Send Button: When the Send button is clicked the communication link will attempt to send the text in the Message window to the tracker until it receives a response from the tracker that the message was successfully delivered. While the NOC server computer is sending the message, the Send button will NAL Research Corporation (TN V6.1) 29

30 change to a Cancel button. Clicking the Cancel button will cause the program to stop sending the message. Even if sending is cancelled, the message may have still been delivered to the tracker. Hangup Button: This button will end chat mode and hang up the connection. If a message was in the middle of sending, it will be cancelled. NOTE: Chatting has higher precedence than continuous mode, but does not have higher precedence than remote updates, which have the highest precedence. Therefore, even if the transmission mode is set to Continuous, the Server for Trackers program will cause the remote A3LA-DGS to go into chat mode. However, if the transmission mode is set to Use Remote Change List and there is a remote change for the remote tracker in the change list, then the Server for Trackers software will attempt to make the update and will not start chatting. Initiate Chatting with a Remote A3LA-TSS Tracker To initiate chatting with an A3LA-TSS tracker, follow the steps in Request a GPS Report from a Remote A3LA-TSS Tracker. However, Chat button should be clicked instead of the Call button. Once chatting has begun, the Chat window will appear on the NOC server computer. There is a separate Chat window for each chat session between a remote tracker and NOC server computer. Chatting with an A3LA-TSS tracker is done via SMS. For this reason, if the communication link used to chat with the A3LA- TSS is a NOC server modem, then the A3LA-TSS and the NOC server modem has the option to establish a simultaneous voice call while chatting. NOTE: While in the chat mode, the A3LA-TSS tracker will send GPS reports, SMS messages and responses to the phone number or address via SMS message even if the tracker is currently set up to send reports using SBD. Messages will be sent and received using the Chat window. While chatting, the remote A3LA- TSS will send over GPS reports approximately every ten seconds. Conversation Window: This window will display messages received in red and messages sent in blue. This box is only cleared when the Clear Conversation button is clicked. User may want to clear the Conversation box with the Clear Conversation button for privacy. Content of chat message inside the Conversation window may also be copied with Ctrl+c. NAL Research Corporation (TN V6.1) 30

31 Message Window: Messages to be sent are entered in this window. The length of messages is limited to 157 characters. Some characters may be counted twice, due to the way SMS messages are formatted, or may not be allowed depending on whether the communication link is a server modem or an account. A count of the actual SMS characters is shown below the message window. If the communication link is an account, the count includes the length of the From address plus one for a separating space. The From address is included when sending from an account so that the remote tracker will know where the message came from (the remote tracker only accepts chat messages from SMS messages). The message box can be cleared by clicking Clear Message. Send Button: The process of sending a message using the Chat window is as follows. User types a message in the Message box and clicks the Send button. If the message was sent successfully, the Send button becomes the Cancel button and the message is left in the Message box until a response from the tracker is received or the Cancel button is clicked. If the Cancel button is clicked the message is moved to the Conversation box, but is displayed in Italics, meaning that the software has not received a response from the tracker. Whenever the Server for Trackers program receives a response for a chat message, it will try to match it to a sent chat message. If the response matches a chat message that was canceled, it will find it in the Conversation box and display it in Regular font. If the response matches a chat message that has not been canceled, the software will move the chat message from the Message box to the Conversation box and display it in Regular font. The Server for Trackers software keeps a record of the chatting with the remote tracker in two places the Conversation box and the log file (if the Log Reports to a Single Log File option is being used). The contents of the Conversation box are not saved between program executions, whereas the log file is Options Menu Manage Chat Windows The Server for Trackers creates a separate Chat window for each chat session. The Option/Manage Chat Windows window keeps track of and provides easy access to all of the Chat windows. From this window, all of the information except the actual conversation can be seen for all of the Chat windows at once. There is also a field showing the number of unread messages for each Chat window. A message is considered unread if it is received while the Chat window does not have focus (the currently active window). Once the Chat window gains focus, all of the messages for that window are considered read. NAL Research Corporation (TN V6.1) 31

32 Double clicking on a record for a Chat window in the Manage Chat Windows window will cause the associated Chat window to pop up for that session. The Show button displays the selected Chat windows, the Hide button hides the selected chat windows, and the Remove button terminates the selected Chat windows. If the Remove button is clicked, the conversations in the destroyed Chat windows will be lost. When the Server for Trackers is closed all of the Chat windows are destroyed Options Menu Send / Track Remote Updates Updates can be sent to remote trackers via SBD for the 9601-DGS, 9601-DGS-LP, and A3LA-DGS (A3LA-DGS trackers must be in SBD mode to receive updates) and via SMS for the A3LA-TSS. A remote update can also be made for A3LA-DGS trackers with the remote configure list. When a remote tracker receives an update, it sends a response back to the NOC server computer (unlike the 9601-DGS, 9601-DGS- LP, and A3LA-DGS, the A3LA-TSS does not send a response if the update fails). By receiving responses from trackers, the NOC server computer is able to track the status of all updates. However, this tracking scheme is not totally reliable, since the remote tracker may have made an update but may not have been able to send back a response. The Option/Send/Track Remote Updates window is provided by the Server for Trackers to carry out the features mentioned above. This window combines a screen for sending remote updates and a screen for tracking remote updates into one window. Switching back and forth between these two screens is accomplished by selecting Send a Remote Update or Track Remote Updates (see Figure 10). Figure 10. Send/Track Remote Updates. Send a Remote Update The process of sending a remote update is broken into three steps with each step depending on the previous step(s) Specify Sending Information, Enter Remote Update and Review and Send. To go NAL Research Corporation (TN V6.1) 32

33 through the steps, click either the Previous or the Next button at the bottom of the screen. To start over from the first step and clear all of the entered information, click the Start Over button. Some users may find it more convenient to use the Previous button instead of the Start Over button since the Previous button does not clear the previously entered information. In this way, the same remote update can be sent to several remote trackers by simply changing the information in the Specify Sending Information step. In the first step or Specify Sending Information, seen above in Figure 10, the information needed for sending the remote update is entered. This information includes the destination of the remote update and the communication link that will be used to send the remote update. It is important to first choose the remote tracker type, since subsequent information depends on this selection. In the second step or Enter Remote Update, seen in the figures below, the updated operating parameters of the selected tracker are entered. The information available to update depends on the remote tracker type specified in the Specify Sending Information step discussed above. For the A3LA-IGS / A3LA-DGS remote modem type, the parameters that can be updated include the Number to Dial, Type of Calls, Time Between Calls and Number of Tries. The Enter Remote Update step for the A3LA-IGS / A3LA-DGS remote modem type option is shown below in Figure 11. Figure 11. Send/Track Remote Updates for A3LA-IGS / A3LA-DGS. The Enter Remote Update step for the A3LA-TSS Remote Modem Type option of step one is shown below. The remote update settings that can be modified include the destination and the report interval. Under Update Destination Use SBD Address, Use SMS Phone Number and Use SMS Address are the available options. Time between Reports and Number of Tries are the parameters which can be updated under Update Time between Reports / Number of Tries. NAL Research Corporation (TN V6.1) 33

34 Figure 12. Send/Track Remote Updates for A3LA-TSS. When a 9601-DGS is the chosen Remote Modem Type of step one, the settings that can be updated include Time between Reports and Time to Keep Trying, both listed under Update Interval, along with Sleeps Between Reports and Callable Between Reports, both listed under Update Callable. The Enter Remote Update step for the 9601-DGS is shown below. NAL Research Corporation (TN V6.1) 34

35 The Enter Remote Update step for the 9601-DGS-LP is shown below in Figure 13. Settings that can be updated include the Interval Between Reports, Callable Status, Block Invalid GPS Reports, Emergency Report Flood, Motion Sensor Alert, and the Output pins. The Interval Between Reports and the Callable settings can be updated for Normal, Test, and Emergency mode. The 9601-DGS-LP V2 option from the Specify Sending Information step has a similar interface as shown in Figure 13, but adds the following settings: Interval Between Reports for moving Normal, moving Test and moving Emergency, Motion Sensor Wait for Normal, Test and Emergency, Motion Sensor Begin, Motion Sensor End, Pin Signaling, Signaling Times, and Same Place Skip Reports for Normal, Test and Emergency. Figure 13. Send/Track Remote Updates for 9601-DGS-LP. A password is required for all remote updates. If the Remote Update Password on the remote unit does not match then no update will be made. If a section is checked then the values will be updated on the remote tracking unit. If the section is not checked then no update will be made. For more information on the 9601-DGS operating parameters, please see manuals AT Commands for Model 9601-DGS (TN V2.1.0) and SatTerm Software Manual (TN V4.1.0). For more information on the A3LA-DGS and A3LA-TSS operating parameters, please see the Terminal Software Manual (TN V4.0.2). For more information on the 9601-DGS-LP operating parameters, please see manual AT Commands for Model DGS-LP (TN V1.0). In the last step, the user is given a chance to review the entered update information and can choose to either send the update or to go back to previous screen(s) and make corrections. When the Send button is clicked, the Server for Trackers program will use the specified communication link to send the entered update operating parameters to the selected remote tracker. If the update is successful, an entry will be NAL Research Corporation (TN V6.1) 35

36 made on the Track Remote Updates screen by the Server for Trackers program, which can then be used to track the status of the remote update. Figure 14. Send Remote Update Track Remote Updates The Track Remote Updates screen has two lists Sent Remote Updates list and Received Responses list. After a remote update has been sent from the Send a Remote Update screen, it will be entered into the Track Remote Updates screen and into the Sent Remote Updates list along with the time that it was sent and the information of the remote tracker it was sent to (either IMEI number or phone number). In the same way, when a response is received from a remote tracker, it will be entered into the Track Remote Updates screen and into the Received Responses list along with the time that it was received and the information of the remote tracker that it was sent from. The R or Result column indicates the status of the updates. A blank denotes no response from the remote tracker, an S denotes a successful update, or an F denotes a failed update. The Sent Remote Updates and the Received Responses lists are separated yet they are related to each other. If a remote update is selected in the Sent Remote Updates list and there is a response for that remote update in the Received Responses list, then the response is automatically selected and moved into view. Likewise, the same is true for when a response is selected. The Delete button will delete all of the remote updates and responses that are selected. The way responses are matched to remote updates is based on the type of remote tracker that sent the response. For A3LA-IGS trackers and older versions of the A3LA-DGS trackers, the response is matched to the remote update by IMEI number. When matching by IMEI number, the Server for Trackers program looks NAL Research Corporation (TN V6.1) 36

37 for the first remote update that does not already have a response associated with it. For new versions of the A3LA-DGS, the response is matched to the remote update by the actual remote update string as well as the IMEI number. This provides a more accurate match than just using the IMEI number. If the response came from an A3LA-TSS tracker, it is matched to a remote update by the time stamp and checksum of the remote update. This should always provide an accurate match, since the time stamp records the date and time to the hundredth of a second that the remote update was sent. The 9601-DGS matches by the date time stamp and by the values that were being updated as well as by the IMEI number. The information in the Track Remote Updates screen is automatically saved to a file in the installation directory to enable tracking across program executions. Figure 15. Track Remote Update. The 9601-DGS-LP sends the values of the Input pins in remote update responses. These values are recorded in the Track Remote Updates screen and are labeled In Pins. Below is a figure showing where the pin values are recorded NAL Research Corporation (TN V6.1) 37

38 3.12 Options Menu Use 3.1 Open/Save Dialog Style The Option/Use 3.1 Open/Save Dialog Style option determines the type of dialog boxes used to open and save files. Selecting this option means that Windows 3.1 style dialogs are used and if not selected then Windows XP style dialogs are used. On some computers the Windows XP Save and Close dialogs will prematurely close. If this happens we recommend using the Windows 3.1 dialog boxes instead. Please see the Known Problems section for more details Options Menu For SBD/SMS Use Unique ID When this option is enabled Server for Trackers is forced to use IMEI numbers as the identifiers for trackers. The For SBD/SMS Use Unique ID option has been made available due to operational complications that arise when static IDs are used to identify modems. Enabling this option also ensures compatibility with NAL Research's Mapping Software Options Menu Emergency Report Acknowledge The Emergency Report Acknowledge form, shown below, creates a configuration message to set the behavior of an active Emergency mode. When Server for Trackers receives an Emergency report from a tracker, it indicates an Emergency status. The Emergency Report Acknowledgement responds to the Emergency report by configuring the remote tracker to stop sending an Emergency state indicator, to stop an Emergency report flood (if ^ERF is enabled on the unit), and to report using different timings. The first setting, Override Emergency Interval, controls how the trackers in Emergency mode will operate after being acknowledged. Continue Using Emergency Interval sets the tracker to use the Emergency mode reporting parameters ^TBRE, ^TTKTE, and^cale. Use Normal Interval sets the tracker to use the Normal mode reporting parameters ^TBR, ^TTKT, and ^CAL. The Auto-Send setting provides the option to allow the Server for Trackers to automatically acknowledge Emergency reports via DirectIP SBD or SBD. When Auto-Send is enabled, there are two options for specifying which trackers to responds to. When Use Same Password is checked, the specified remote update password will be used for all acknowledgements and any Emergency report received by Server for Trackers will trigger an acknowledgement to be sent to the sending tracker. When Use Same Password is unchecked, the IMEI numbers listed are the only trackers to which acknowledgements will be sent. The messages will not be accepted by the trackers if the Remote Update Password field for an IMEI is incorrect. The SMTP Settings determine the account to be used when sending acknowledgements via . The SMTP Settings must be entered for Emergency report acknowledgements to be sent; the SMTP settings of Communication/Configure Communication Links... are not applicable to the Emergency Report Acknowledge form. The DirectIP settings must be entered under Communication/Configure Communication Links... described earlier in this document. The Send Now portion of the form allows Emergency report acknowledgements to be sent without the Server for Trackers having received an Emergency report from a tracker. Emergency report acknowledgements sent for each unique IMEI number are limited to one every 20 seconds. This is to prevent a flood of Emergency reports from generating a large number of acknowledgements for a single unit. NAL Research Corporation (TN V6.1) 38

39 Figure 16. Emergency Report Acknowledge. NAL Research Corporation (TN V6.1) 39