Page 2 Antares SB GSM User’s Manual (FW 5.30) Digital Communications Technologies September 9, 2009...
Page 3 Copyright This manual is copyrighted. All type of reproduction of its content must be authorized by Digital Communications Technologies Document information Version: 1.00 Type: Release. Date of release: 08-09-09 History:...
Page 4 Special Note This manual applies to the GSM version of the Antares SB Firmware version This manual applies to ﬁrmware version 5.30 of the GSM version of the Antares SB . You can consult the unit’s ﬁrmware version with the...
Page 5: Regulatory Compliance
Regulatory Compliance This product operates with Wavecoms Q24PL transmitter. FCC Parts 22H and 24E are granted to the Wavecom Q24PL under FCC identiﬁer O9EQ24PL001. The antenna gain, including cable loss, must not exceed 3 dBi at 1900 MHz / 1.4 dBi at 850 MHz for mobile operating conﬁgurations and 7 dBi at 1900 MHz / 1.4 dBi at 850 MHz for ﬁxed mounted operations, as deﬁned in 2.1091 and 1.1307 of the rules for satisfying RF exposure com- pliance.
Page 6 GARMIN AUTHORIZED PARTNER Digital Communications Technologies LLC is a Garmin authorized partner. Founded in 1989, Garmin is a pioneer in Global Positioning System (GPS) devices and the worldwide leader in the design, manufacture and sale of GPS equipment. The company has built and sold millions of GPS products that serve the automotive, aviation, marine, consumer, wireless, OEM, and general recre- ation markets.
Page 7 LIMITED WARRANTY Digital Communications Technologies warrants the original purchaser that for a period of twelve (12) months from the date of purchase, the product shall be free of defects in materials and work- manship under normal use. During the warranty period, Digital Communications Technologies shall, at its option, repair or replace any defective product upon return of the product to its facil- ities, at no charge for labor and materials.
Page 8 Technologies be liable for any special, incidental, or consequential damages based upon breach of warranty, breach of contract, negligence, strict liability, or any other legal theory. Such damages include, but are not limited to, loss of proﬁts, loss of the product or any associated equipment, cost of capital, cost of substitute or replacement equipment, facilities or services, down time, purchasers time, the claims of third parties, including customers, and injury to property.
Page 9: Table Of Contents
0.3 Technical Assistance ....1 About the Antares SB 1.1 Features ......
Page 10 Contents 1.2 Contents of package ....1.3 Front side description ....1.3.1 RS-232 port .
Page 11 Contents 3 Operation 3.1 Serial Port ......3.2 LEDs ......3.2.1 Power (Red) .
Page 12 3.22 TAIP Downloader Tool (Write/Read scripts) ..3.22.1 Communicating locally with the Antares SB 3.22.2 STEP 1. Selecting a COM port ..3.22.3 STEP 2. Test Communication ..
Page 13 Contents 4.4 Reporting ......4.5 *Event Machine ..... . 4.5.1 Triggers .
Page 14 Contents 4.28.2 Reading Scripts ....127 4.28.3 Writing Scripts ....128 4.28.4 Scripts Over The Air .
Page 15 Contents 5.6.1 Setting the speed limit ....142 5.6.2 Start a counter ....142 5.6.3 Creating the violation report .
Page 16 Contents 6 Unit’s TAIP reference 6.1 (AL) Altitude ..... . . 164 6.2 (CP) Compact Position ....165 6.3 (DA) Destination Address .
Page 17 Contents 6.23 (ST) Status ......202 6.24 (TM) Time and Date ....203 6.25 (TD) Time and Distance signals conﬁguration .
Page 18 Contents 6.42.6 (XAGMR) Garmin Mode Add or Delete Canned Replies ..... . 234 6.42.7 (XAGMRS) Garmin Mode Canned Reply Text Message .
Page 19 Contents 6.62 (XAOS) OBD Status Consult ....261 6.63 (XAOT) Throttle Position thresholds..263 6.64 (XAPM) Power Management ....264 6.64.1 Examples .
Page 20 Contents 10 Appendix D - Quick TAIP reference 10.1 Setting the Antares SB ID ....299 10.2 Setting the APN ..... 299 10.3 Conﬁguring the SIM card PIN .
Page 21: Scope
Preface This document is the Antares SB User’s Guide. On this document you will ﬁnd information on what is the Antares SB , its features, speciﬁcations, installation instructions and explanation on the unit’s conﬁguration and operation. This document is available at: http://www.digitalcomtech.com...
Page 22: Technical Assistance
0.3. TECHNICAL ASSISTANCE The TAIP reference chapter is a compendium of all the conﬁgu- ration and query commands, therefore it is the big complement of the Operation and Conﬁguration chapters. The Quick Start Guide is a very condensed summary to get you started with the unit.
Page 23: About The Antares Sb
About the Antares SB The Antares SB is a vehicle tracking and controlling device designed to interact remotely with Automated Vehicle Location (AVL) systems or end-users by using the GSM/GPRS cellular network as commu- nication media. The Antares unit is installed on a vehicle whose geographical position and/or state is desired to be remotely moni- tored/controlled.
Page 24: Optional Back-Up Battery
1.1. FEATURES 1.1.3 Optional Back-up Battery The Antares SB may include a built-in back-up battery to be used when the vehicle’s battery is unavailable. Refer to the Operation chapter for more information. 1.1.4 Voice support An audio jack for non-balanced hands-free audio systems allows the unit to initiate and receive phone calls (Hands-free audio system is not included).
Page 25: Versatile Rs-232 Communication
Destinations. One application for this is attaching an MDT device. Other example includes attaching a satellital modem to be used when no GSM/GPRS signal is detected by the Antares SB 1.1.10 Communication buﬀer Antares SB will start saving event’s reports and incoming serial...
Page 26: Gps Back Log And Acceleration
Cellular Network Cell ID information on every reported message. This enables a Tracking System to locate the unit when GPS is not available. Antares SB will report the Cell ID, LAC, MCC, MNC and RSSI of the cell it is registered with.
Page 27 1.1. FEATURES 30 Polygon-deﬁned geographical regions (50 points each). 100 circular geographical regions. 10 Speed limits. 5 Positive/negative acceleration limits. 10 Time windows (dates’ intervals). 4 Discrete inputs 4 Discrete outputs 20 Counters for traveled distance, time and event counting. 5 Heading change deltas (turn by turn report).
Page 28: Contents Of Package
1.2. CONTENTS OF PACKAGE Contents of package Inside the Antares SB box you will ﬁnd the following content: An Antares SB A GSM Quad-Band antenna ready to work with any GSM car- rier regardless of its operation frequency. An active GPS antenna with magnetic support and reverse- polarity connector.
Page 29: Front Side Description
Use this port to conﬁgure or query the unit and to connect accessories like PDA-like devices or MDTs. The Antares SB ’s works as an RS-232 DCE device. See the Serial Port section in the Operation chapter for more in-...
Page 30: Sim Card Slot
1.3. FRONT SIDE DESCRIPTION 1.3.2 SIM card slot Use this slot to insert the GSM SIM card. Insert the SIM card as described on the next ﬁgure. Use a thin object like a coin to get the SIM card fully inserted until it clicks. The SIM gets locked when it clicks.
Page 31: Audio Jack
1.3. FRONT SIDE DESCRIPTION 1.3.4 AUDIO jack The audio connector is designed to connect a non-balanced hands-free audio system. See the Speciﬁcations section for information on the type of speaker and microphone that can be used. The connector is designed to use a 2.5mm stereo plug with the fol- lowing conﬁguration: A non-balanced speaker-microphone connection must be as follows: Most popular cellular phones’...
Page 32: Back Side Description
1.4. BACK SIDE DESCRIPTION Back side description 1.4.1 GSM Antenna connector This is a SMA (Sub Miniature A) connector with a female center contact. Use this connector for the GSM Antenna provided with the unit. 1.4.2 GPS Antenna connector This is a SMA (Sub Miniature A) connector with a male center con- tact .
Page 33: Power/Ignition Molex-Type Connector
1.4. BACK SIDE DESCRIPTION XP makes reference to Outputs, IP to Inputs. For information on inputs, outputs and ADC see the Operation chapter. The I/O Harness (female molex-type receptacle) supplied with the unit is conﬁgured as follows: Signal Color White and brown White and red White and orange White and yellow...
Page 34 1.4. BACK SIDE DESCRIPTION The Power Harness (female molex-type receptacle) supplied with the unit is conﬁgured as follows: Signal Color Black Ignition (F00) Yellow...
Page 35: Speciﬁcations
1.5. SPECIFICATIONS Speciﬁcations 1.5.1 Dimensions Values shown in millimeters. The depth of the unit is 127mm. 1.5.2 Environment Operating: 20 C to +55 C Storage: 30 C to +85 C Humidity: Up to 95% non-condensing. 1.5.3 Power DC Voltage : 8V - 32 V Current consumption: –...
Page 36: Inputs/Ignition
1.5. SPECIFICATIONS 1.5.4 Inputs/Ignition Input impedance: 50 Kohms. Internal Pull-up: 50 Kohms. Sampling rate: 3 s/sec. Inputs’ detection: Logical State Electrical State Active 0V to 1V Inactive 2.9V to 32V or Open Ignition detection: State Voltage range Ignition ON 5.8V to 32V Ignition OFF 0V to 4.8V or Open 1.5.5...
Page 37: Gsm/Gprs Module
1.5. SPECIFICATIONS 2.5mm Stereo audio jack. Speaker impedance: 32ohms. Microphone: Electret type. 1.5.8 GSM/GPRS module Frequencies: 850/1900 or 900/1800 Mhz. Full duplex communication. Automatic start up. Antenna Impedance: 50 Ohms. SIM Card: 3 Volts. SIM Card PIN: Programmed by user one time, automatically in- troduced onward.
Page 38: Gps Module
1.5. SPECIFICATIONS 1.5.9 GPS module Units with ﬁrmware version 1.05: Sensitivity: -152 dBm Tracking, -142 dBm Acquisition. Protocol: TAIP(ASCII). Frequency: L1 type (1575.42 MHz). C/A code. Channels: 12 channel simultaneous operation. Update rate: 1Hz. Accuracy: Horizontal: <3 meters (50%), <8 meters (90%) Altitude: <10 meters (50%), <16 meters (90%) Velocity: 0.06 m/sec.
Page 39: Gsm Antenna Connector
Warm Start: 35 sec. Cold Start (TTFF): 38 sec. Out of the box: 41 sec. To consult or update the ﬁrmware version of your Antares SB module, please contact Digital Communications Technologies . Up- dates are provided at no cost.
Page 40: Gps Antenna Connector
1.5. SPECIFICATIONS 50 ohms impedance. 1.5.11 GPS antenna connector SMA (Sub Miniature A) connector with a male center contact 50 ohms impedance. Also called reverse polarity connector...
Page 41: Installation
When the vehicle has a main power switch to cut/restore the battery voltage, some recommendations have to be followed: If the switch disconnects the positive voltage of the vehicle’s battery, the Antares SB can be connected before or after the switch. When connected before it will keep on receiving the vehicle’s power whenever the switch is oﬀ.
Page 42 2.1. POWER SUPPLY If the switch disconnects the negative voltage of the vehicle’s battery, the Antares SB power CAN NOT BE TAKEN BE- FORE THE SWITCH. Doing so will make all of the unit’s con- nections to ground like panic buttons and its chassis serve as current path canceling the vehicle’s main power switch thus...
Page 43 2.1. POWER SUPPLY...
Page 44 2.1. POWER SUPPLY...
Page 45: Inputs Detection
(inactive). Any voltage below 1V on the input will be indicated as ON (active). It is normal to see a 3.4V(approx.) voltage on the Antares SB Inputs when nothing is conencted to it. This voltage is set on purpose through a pull-up circuit (50kOhm resistors) in order to ﬁx a inactive state when there is nothing connected to the Inputs.
Page 46: Outputs
The unit’s ignition sense can be directly connected to the electrical end of this position. See the Connection Diagrams section for an illustration. It is normal to see a 3.4V(approx.) voltage on the Antares SB ignition input when nothing is conencted to them. This voltage is set on pur- pose through a pull-up circuit (50kOhm resistors) in order to ﬁx a...
Page 47 2.4. OUTPUTS If the output is used for cutting/restoring a positive voltage on a high current device, like for example the vehicle’s ignition wire, an external device like a relay o high current transistor has to be used. See the Connection diagrams for an illustration.
Page 48: Connection Diagrams
2.5. CONNECTION DIAGRAMS Connection diagrams The following illustrations show: Panic Button detection. Ignition sense. Engine turn oﬀ Shutting and engine oﬀ without knowing a vehicle’s state is not advised. See the Operation chapter for more information.
Page 49 2.5. CONNECTION DIAGRAMS...
Page 50: Operation
Operation The Antares SB operates on an automatic basis according to an user-deﬁned conﬁguration which can be modiﬁed at any time locally or remotely using the GSM/GPRS network. The unit’s operation in- cludes actions/reports based on interaction with its surroundings like remotely-given commands, input sensing, accessories’...
Page 51: Serial Port
(9600,8N1). It does not use any ﬂow control method and all of the RS-232 communication lines on the DB9 connector are used. The Antares SB works as a DCE device, meaning that it is connected to a PC with a one-one cable.
Page 52: Power (Red)
3.2. LEDS 3.2.1 Power (Red) This LED is solid ON whenever the unit is functional, OFF when it has no main or back-up power . Any time the LED is blinking the unit is in a temporal state where some features are not available. These temporal states may be reached when: Initializing: This state lasts 15 seconds and is reached any time the unit is recovering from a non-power situation or recovering...
Page 53: Fix (Yellow)
3.2. LEDS Blinks RSSI [(-)dBm] 0 to 7 113 - 99 Very poor (oﬀ) 8 to 13 97 - 87 Poor 14 to 17 85 - 79 Fair 18 to 20 77 - 73 Fair 21 to 24 71 - 65 Good 25 to 31 63 - 51...
Page 54: Inputs/Ignition
3.3. INPUTS/IGNITION Inputs/Ignition The unit has 4 general purpose discrete-inputs located on the main molex connector and a vehicle ignition detector located on the main power molex connector. For the general purpose inputs the electrical conditions are as fol- lows: Logical State Electrical State Active...
Page 55: Outputs
3.4. OUTPUTS and when the input is not active (i.e. input 3 at any voltage disconnected): >RSSIP30< Outputs The unit has 4 discrete outputs located on the main molex connector. Given their 2A current capacity they can drive a wide range of loads. The outputs are of Open Drain type with no pull-up resistor.
Page 56: Analog To Digital Converter
3.5. ANALOG TO DIGITAL CONVERTER >SSSXP30< Example Making the Antares SB automatically drive an output: Use the SS message as an user-action on an event deﬁnition, see the Event Machine section on the Conﬁguration chapter and the ED mes- sage on the TAIP reference: >SED20NV0;R05-;ACT=SSSXP21<...
Page 57: Back-Up Battery
These events will send the report to the serial port. See the Event Machine section on the Conﬁguration chapter for more information. Back-up Battery The Antares SB oﬀers the possibility of a built-in back-up Lithium- Polimer battery to be used whenever the main power source (the ve- hicle’s battery) is lost or sabotaged.
Page 58 3.6. BACK-UP BATTERY 10 days when in sleep mode: Only inputs’ detection is available and an optional wake-up interval is available. This last wake-up option was not used on the battery test. The battery level measurement is done in a similar way as the unit’s Analog to Digital Converter please refer to that section for some notes.
Page 59: Sleep Mode
TCP/UDP port has to be created on any of the unit’s Destinations’ space. When using TCP the unit functions as a TCP client which always initiates the connection to the remote IP Antares SB supports IP numbers as well as domain names.
Page 60 TAIP commands on a ﬁxed, always-available port. No- tice that the UDP server port solution only works when both the server sending the TAIP query and the Antares SB located on the same network (Virtual or Real). This is not the case on the majority of situations where the unit has Internet access.
Page 61 3.8. OVER THE AIR Server address validation When working with TCP, a server sending TAIP queries to Antares is validated through the TCP connection which is always initi- ated by the unit. For incoming UDP datagrams there are two mechanism the unit uses to validate the remote peer (AVL server).
Page 62: Via Sms (Gsm)
3.8. OVER THE AIR 1. From a SMS Destination (mobile number) that has TAIP con- sole access, send a SMS with a command that instructs the unit to send a “hello-type” report to the IP host which is going to interact with the unit.
Page 63: Voice (Gsm)
Refer to the XAVC, XAVE commands and voice signals for more infor- mation. Refer also to the Operation chapter and Examples chapter. TAIP console The Antares SB TAIP console allows commands and queries to be sent to the the unit by a user or software. The TAIP console is avail- able on all of the communication channels.
Page 64 ID Flag (ID) The unit can be conﬁgured to output every message with the vehicle’s ID. The default ID is set to 0000. The Antares SB will check all incoming messages for ID, if no ID is speciﬁed, the unit will accept the message.
Page 65 ( S qualiﬁer) with the corresponding “Response” message ( R qualiﬁer). For example, when setting the unit’s ID with the TAIP message: >SIDTest< If the EC Flag is active, Antares SB will reply with: >RIDTest;ID=Test< If the EC Flag is inactive, Antares SB will not return a reply to the message.
Page 66: Reporting Messages
;SI=xxxx characters, the response to this message will include those same characters. The maximum length of a Session ID message is 10 alphanumeric characters For example, to query the Antares SB version using the Session ID, use: >QVR;SI=123ABC<...
Page 67: Working With Tcp
These are the general requirements for an AVL server working with units on TCP: 1. The AVL server has to be able to work as a TCP server, as the Antares SB is always going to initiate the TCP connection acting as TCP client. Technically speaking, for this to happen the AVL server has to be able to open a TCP socket on listening mode on an available port.
Page 68: Working With Udp
3.10. REMOTE HOST SOFTWARE possibility for the server to have open TCP connections with unknown IDs every time an unit opens a connection but it has nothing to report. There is a workaround for this: Having the unit send a re-connection event so every time the connection is opened the server knows who did open it.
Page 69: Working With Sms
Then no more sends for about 6 more minutes. After that the mech- anism restarts. 3.10.3 Working with SMS Antares SB may use Telephone Number Destinations to send its report or to give TAIP console access via SMS messages. The Destina- tion may be conﬁgured to send user-deﬁned event messages intended to be read by a person with a cellular phone or similar.
Page 70: Reports' Messages
TAIP command that the user locates on the user- action section of an event deﬁnition. So, the AVL server shall expect two types of reports from the Antares SB : The Events’ Reporting Messages and the Responses to TAIP commands messages.
Page 71: Responses To Taip Commands Messages
3.11. REPORTS’ MESSAGES The Extended Reporting Messages (Extended EV) When using an Extended Reporting EV Message, extra tags are added at the end of the standard EV message presented above. These tags allow the addition of information on: Inputs and Outputs state. Counters’...
Page 72: Reports' Buﬀer
For more information and examples see the Event Machine section on the Conﬁguration chapter. 3.12 Reports’ buﬀer The Antares SB reserves a memory space to save reports whenever the remote Destination is not available. The buﬀering process for a Destination takes place on any of the following situations: For IP-type destinations: 1.
Page 73: Gps Back Log
ﬁgured in the server. The XAPW TAIP message is used to conﬁgure the password in Antares SB The XAAU TAIP message is used to send the challege text to the server.
Page 74: Sms Alias
The AVL server will be able to send and consult the state of Stop Messages. The Stop Messages give the Garmin device coordinates of a destination which it can use to trace a route that the driver can follow. Antares SB will also send unsolicited status messages when an action is performed on the Stop Message, or when the destination is reached.
Page 75 Fleet Managment Protocol data deletion. If a functionality has more that one X mark it means that a Garmin de- vice must have at least one of these protocols so Antares SB can use the functionality. If the Garmin device has more than one of these protocols, Antares SB will use the most recent one.
Page 76: Data Flow Example
3.18. GARMIN DEVICES SUPPPORT nuvi nuvi 205W nuvi 255W nuvi 465T nuvi 265T nuvi Data Cable Pin Out: 3.18.2 Data Flow Example This is an example of the ﬂow of the data between Garmin, Antares and the server listening for incoming messages from the Garmin device. To send a text message to the Garmin device from the server, use the fol- lowing TAIP message:...
Page 77 3.18. GARMIN DEVICES SUPPPORT >SXAGMTS0000001244751579Hello World< If the message was received by the Garmin device, Antares will respond to the server: >RXAGMTS0000001244751579Hello World< If there is a communications problem and the Garmin device does not receive the message, Antares will respond with Error 46 (Internal communications problem).
Page 78 3.18. GARMIN DEVICES SUPPPORT At the same time Antares will send a status message to the server indicating that the message was read: >RTXGMTS000001< If the user decides to delete the message, Antares will send a message indi- cating this action: >RTXGMTS000002<...
Page 79 3.18. GARMIN DEVICES SUPPPORT The user just needs to select the desired message and select Yes when prompted: Antares will send the message to the server like this: >RTXGMTR00000001180936526626May be< To use the Stop Messages functionality, the server must ﬁrst send the Stop Message using the XAGMS TAIP message: >SXAGMS0001244753308+0307600189-0957793861127<...
Page 80 >RTXGMSS000100000< Or if the user deletes the message, Antares will send the unsolicited message to conﬁrm this action: >RTXGMSS000104---< Please refer to the XAGM TAIP message for more information on the conﬁg- uration of the Garmin device with Antares SB...
Page 81: Setting Up The Server
Because of this it is important that the modem is correctly conﬁgured and has been tested to be working correctly by prior to connecting it to Antares SB The event deﬁnition must be done using the Message ID qualiﬁer “O” from...
Page 82: Operation
Serial Interface Speciﬁcation can be requested directly to Orbcomm at Service.customer@orbcomm.com. However this information is not re- quired to set up Antares SB to work with the satellite modem. If the Event Handling ﬁeld is set as “X” the encapsulated message will only be sent to the serial port.
Page 83 3.19. ORBCOMM SATELLITE MODEMS SUPPORT this conditions to change the report criteria intelligently. In this example the report event will be sent to the serial port only when the GPRS-IP destination is unreachable. First we must create the IP destination point. >SXADP0000avl.server.com;1234<...
Page 84: Obd Support
>SMTR< 3.20 OBD Support Through the OBDII Interface model BG accessory, Antares SB can use the vehicle’s On-Board Diagnostic (OBD) system parameters to generate reports based on the vehicle’s Engine RPM, Throttle Position, Speed, Ac- celeration, Odometer, Fuel Level, Fuel Rate, Ignition State and Malfunction Indicator Light.
Page 85: Firmware Upgrade
This process is stared with the XAFU message. See the TAIP reference for detailed information. The message takes a ﬁrmware version number for ex- ample 5.22, a ﬂag that tells which server to use: DCT’s or any deﬁned by the user, and a Destination Address or Destination Point to send the up- grade progress state.
Page 86 (pending events) will be lost. The unit’s conﬁguration is preserved throughout ﬁrmware upgrades Example Initiate an over-the-air ﬁrmware update with DCT’s servers in order to up- grade the unit’s ﬁrmware to version 5.22 having the diagnostic messages sent over the serial port: >SXAFU00522SV15<...
Page 87: Upgrading Locally
3.22. TAIP DOWNLOADER TOOL (WRITE/READ SCRIPTS) >RTXNew firmware installed!. Running version: Antares GPS 5.22 < Meaning that the upgrade process ended ok. For detailed information see the XAFU message. 3.21.2 Upgrading locally This upgrade is done trough the unit’s serial port, with a terminal software like Windows ’...
Page 88: Communicating Locally With The Antares Sb
3.22. TAIP DOWNLOADER TOOL (WRITE/READ SCRIPTS) 3.22.1 Communicating locally with the Antares SB Power on the unit. Connect a direct serial cable between the unit’s and the PC’s serial ports. You can also use an USB serial port converter . Open TAIP Downloader and follow the next steps.
Page 89: Write A Conﬁguration Script
You can create a conﬁguration script from scratch or copy one of several scripts shown on this manual or you can ask for an script ﬁle from DCT. For more information on script refer to the Using Scripts section on the Conﬁguration chapter.
Page 90: Read A Conﬁguration Script
TOOL (WRITE/READ SCRIPTS) 3.22.5 Read a Conﬁguration Script When reading an Antares SB , an script ﬁle (tmf ﬁle) containing an unit’s conﬁguration is created. This script can be edited and passed to other units to replicate a conﬁguration. To generate an script ﬁle based on an unit’s conﬁguration, on TAIP Downloader...
Page 91: Conﬁguration
Conﬁguration The Antares SB conﬁguration is done through the unit’s TAIP console via TAIP commands. The TAIP console can be used with several commu- nication methods: The unit’s serial port. TCP or UDP (GPRS level) communication. 2-way SMS (GSM level).
Page 92: Unit's Id
4.1. *UNIT’S ID are also deﬁned in order to gain remote access to the unit. The sections on this chapter marked with an * are essential to Note: every conﬁguration. This chapter is a complement of the TAIP reference chapter and vice versa.
Page 93: Sim Card's Pin For Gsm Registration
PIN was not given. So it is recommended in those cases to reset the unit after the PIN-set command with the >SRT< reset message. Or better, have the PIN correctly conﬁgured before the SIM card is inserted. The Antares SB does not block a SIM card when the given PIN Note: is wrong.
Page 94: Access Point Name (Apn) For Gprs Set Up
For example: this.is.an.apn.com internet.carrier-name.com Setting the APN on the Antares SB is also done with the RF message. An “empty” APN may be conﬁgured too. An empty value is used when a GPRS session is not desired.
Page 95: Destinations (Dps And Das)
*Destinations (DPs and DAs) (*)Essential conﬁguration A destination makes reference to the device or user that is receiving and/or sending messages from/to the Antares SB . The possible destination for the unit are: 10 IP hosts. Via TCP and/or UDP.
Page 96: Destination Addresses (Das)
4.3. *DESTINATIONS (DPS AND DAS) an IP address or a server name and a TCP or UDP port number. The Antares SB is a TCP and/or UDP client which always starts the communication. This means that the IP host has to be a TCP or UDP server listening for incoming connections on the same port speciﬁed here.
Page 97: Reporting
DP instead of TAIP reporting messages. See the XADP message for more information on this. The Antares SB reporting messages that have to be interpreted by the AVL software server are the EV and ET messages. See the...
Page 98: Event Machine
4.5. *EVENT MACHINE *Event Machine (*)Essential conﬁguration The unit’s reporting is controlled by an Event Machine which constantly evaluates user deﬁned events. These events allow the user to create a re- porting schema and functionality controlled by triggers and actions. Events can be consulted or conﬁgured at any time with the ED message throughout the TAIP console, enabling the user to alter the Event Machine parameters at any time locally or over the air.
Page 99 4.5. *EVENT MACHINE sequently, a minus (-) sign indicates that the report is generated when the signal or the equation becomes “false”. When A or B becomes true AB + When A and B and C becomes false AB&C& If the report must be generated when one signal becomes true and another becomes false one of the signals must be negated using the boolean opera- tor not.
Page 100: Actions
Actions Once you have deﬁned a trigger (and/or a set of triggers) the next step for conﬁguring the Antares SB event machine, is to tell the unit what to do when a trigger goes oﬀ. There are two types of actions the unit may take when a trigger goes oﬀ.
Page 101 4.5. *EVENT MACHINE Report action When the event machine detects that a trigger goes oﬀ it uses the conﬁgura- tion of the report action to generate a report. A report action conﬁguration includes routing options and a type of report. The routing options tell the unit where to report the occurrence of the spe- ciﬁc event.
Page 102 Activate a led connected to any output whenever a vehicle is out of a polygonal geo-fence. Have the Antares SB safely turn the vehicle’s engine oﬀ whenever this travels too far from the normal working region.
Page 103: Events
The next ﬁgure gives a global description of the TAIP ED mes- sage. For detailed information refer to the unit’s TAIP speciﬁcation chapter. The Antares SB has 50 events available for the user to conﬁgure. They may be deﬁned all at once in a conﬁguration script or they me be individually deﬁned at any moment as the user adds/removes functionality.
Page 104: Signals
4.5. *EVENT MACHINE >RED09U< >RED10NV0;A00U01&+;ACT=SSSU010< >RED11NV1;A00!F03&U01&+;ACT=SSSU010< >RED12U< >RED13U< >RED14U< >RED15U< >RED16U< >RED17U< >RED18U< >RED19U< >RED20NV0;A00C02&+< >RED21NV1;A00!C02&+< >RED22XM0;F03!C02&+< >RED23U< >RED24U< >RED25U< >RED26U< >RED27U< >RED28U< >RED29U< >RED30U< >RED31U< >RED32U< >RED33U< >RED34U< >RED35U< >RED36sV0;S00-;ACT=SGC02U< >RED37sV0;S00+;ACT=SGC02TC00010< >RED38U< >RED39U< >RED40sV0;F00+;ACT=SSSU001< >RED41sV0;F00-;ACT=SSSU011< >RED42U< >RED43U< >RED44U< >RED45U< >RED46U<...
Page 105 4.5. *EVENT MACHINE A situations makes reference to a vehicle state which is in fact represented by signals and their state. Antares SB signals are of boolean nature, meaning that they can only take one of two possible values: true or false.
Page 106 4.5. *EVENT MACHINE Signal Description A00 - A09 Destination Points’ state True when the IP address/port deﬁned on the corresponding Destination Point’s index is accepting a TCP connection or when using UDP (i.e. the TCP/UDP socket is open). See the XADP message. B00 - B04 Battery Levels(+) True when the unit’s back-up battery level is above the value...
Page 107 4.5. *EVENT MACHINE Signal Description OE0 - OE4 Engine’s RPM thresholds True when the egine’s RPM detected by the OBD is higher than the corresponding RPM thresholds. See the XAOE mes- sage. OT0 - OT4 Throttle Position thresholds True when the throttle position percentage is higher than the corresponding throttle thresholds.
Page 108 (*) Antares SB does not have GPIOs. These signals are maintained for backwards compatibility with scripts from other versions. Instead, Antares SB has 4 inputs and 4 outputs. Signals G00-G03 are the same as IP1-IP4 signals and G04-G07 signals are the same as XP1-XP4 signals. The user is encouraged to use IP and XP signals instead of G signals.
Page 109: Examples
>SGR26011-8024444+025840550099< >SGR2602U-8017861+025849440001< Using Polygonal Regions The Antares SB supports detecting when a vehicle is inside or outside of up to 30 user-deﬁned polygons (50 points maximum each). These polygon- deﬁned regions are deﬁned with the GR message and the associated regions’...
Page 110: Using Circular Regions (Geo-Fences)
4.7. USING CIRCULAR REGIONS (GEO-FENCES) Note: For circular regions see the next section and the XAGR message For instructions on creating a region refer to the GR TAIP message. Polygonal regions are useful for creating large regions, like cities’ bound- aries.
Page 111: Using Region Id Reports
4.8. USING REGION ID REPORTS >SXAIR44000500< Note that any region previously deﬁned on the index 44 will be overwritten. Now, to generate event 30 when the vehicle leaves this region, send to the unit: >SED30XV0;K44-< To undeﬁne the region, use: >SXAGR44U<...
Page 112: The Time And Distance Criteria
4.10. THE TIME AND DISTANCE CRITERIA >SED33NV0;S00+< A conﬁguration may be created so a warning to the driver is given via a LED indicator before actually generating the event. See the Scenarios and Examples section for this. 4.10 The Time And Distance criteria Up to 10 Time And Distance (T&D) criterion can be deﬁned.
Page 113: Using Time Windows
4.11. USING TIME WINDOWS 1. Distance Threshold. 2. Minimum time between reports. 3. Maximum time between reports. A T&D signal (TD) gets high according to its deﬁned T&D parameters and it is immediately reset after all events have been evaluated in order to get ready for the activation of the signal again, when the T&D criteria is met on the future.
Page 114 4.12. USING COUNTERS For counting time (TIMERS). For counting distance (DISTANCERS). For counting situations (COUNTERS). For each counter a counter signal Cxx exists. A counter signal gets true whenever the counter’s value exceeds a user-deﬁned threshold and gets low on the contrary. For example, a time counter (TIMER) set to count sec- onds with a threshold value of 300 will make a corresponding Cxx signal to become true 300 seconds after deﬁning the counter.
Page 115 4.12. USING COUNTERS A counter may be suspended and resumed with the GC command.Use the S and R commands on a previously deﬁned counter. The next graph illustrates this.
Page 116 4.12. USING COUNTERS A counter value can also be ”‘manually”’ altered with the GC command. Use the V command on a previously deﬁned counter. The next graph illustrates this. Note that altering a counter’s value does not aﬀect its counting con- ﬁguration: After altering its value, the counter keeps on counting from the given value.
Page 117 4.12. USING COUNTERS The X next to the V on the setting-value command indicates the counter to preserve its recycling ﬂag: If the letters R or C were used instead of X, the counter will not only change its value but its recycling conﬁguration too. A counter value may be consulted at any time.Use the V command in query form (>QGC00V<).
Page 118: Manipulating Signals
4.13. MANIPULATING SIGNALS Unit’s TAIP reference chapter and the Scenarios and Examples sections. 4.13 Manipulating signals Signals marked with a (-) sign on the signals’ list on the Event Machine section can be directly manipulated by the user. These signals are: Outputs (4).
Page 119: Driving Metrics (Acceleration, Max. Speed, Etc)
>SED40NV0;J02+< 4.16 Driving Metrics (Acceleration, Max. Speed, etc) Antares SB has the ability of calculating the vehicle’s positive and nega- tive accelerations based on GPS information. The instant acceleration value gives an idea of how a vehicle is being drove. Large positive values indicates...
Page 120 4.16. DRIVING METRICS (ACCELERATION, MAX. SPEED, ETC) situations. A vehicle having large acceleration values indicates unsafe an expensive driving. On the contrary, low values indicate an smooth, eﬃcient driving. The actual acceleration of the vehicle can be known with the XAIT command.
Page 121: Using Acceleration Signals
4.17. USING ACCELERATION SIGNALS command is sent: >SXAITC< For detailed information consult the XAIT message in the TAIP chapter. Acceleration limits can be set to trigger events whenever the acceleration exceeds given positive or negative thresholds. See the next section. 4.17 Using Acceleration signals See the previous section for an introduction on how acceleration is calcu-...
Page 122: Voice Calls
4.18. VOICE CALLS This will make the unit send the last 60 GPS messages Antares SB received from its GPS module. . The last 15 seconds can be retrieved instead of 60, just change QXAKL to QXAKL0015. See the XAKL message and the GPS Back Log section for more information.
Page 123: Serial Port Devices
2. The external device has no idea of TAIP so it talks any byte-based protocol. For the ﬁrst option there are no special conﬁgurations on the Antares SB . It is only necessary to conﬁgure the Event Machine to send reports to the serial port so the attached device has GPS/events information to analyze.
Page 124 Supposing the external device sends the following data: Note: Non-printable data is shown between [ ] symbols in hex value [02]Test message...[03] The Antares SB after receiving the 03 byte will send to Destination 04 the following TX message: >RTX 02Test message... 03<...
Page 125: Analog To Digital Converter Monitoring
If the host would like to send the sequence: [02][07][08][FC][AA]xyz[F1] to the device attached on the serial port, then it has to send the follow- ing TX message to the Antares SB >STX 02 a b FC AAxyz F1< This will make the Antares SB send the original sequence to the attached device.
Page 126: Cell Id Reporting
Cellular Network Cell ID information on every reported message. This enables a Tracking System to locate the unit when GPS is not available. Antares SB will report the Cell ID, LAC, MCC, MNC and RSSI of the cell it is registered with. This information can be used by systems that know the location of Cells to approximate a location of an unit with no GPS.
Page 127: Sleep Mode
4.25. SLEEP MODE Event 30 will be reported as: >REV301447147509+2578250-0802813901519512;CE=233428;ID=EXAMPLE< The reported message is explained in detail on the EV message description. See the TAIP messages’ reference. user-action method The second method for obtaining Cell ID reporting from the unit is to add a Cell ID query to an user-action ﬁeld on an Event Deﬁnition.
Page 128: Using Scripts
Comments are not passed to the unit, they are only saved on the .tmf ﬁle and can not be retrieved when reading an script from an unit. Here it is an example of an script ﬁle: #Antares SB script #Getting Started example #Unit’s ID >SIDEXAMPLE<...
Page 129: Creating An Script From Scratch
If you prefer, you can edit an existing script instead of creating a new one from scratch. Another option for not having to create an script from scratch is making TAIP Downloader generate an script ﬁle by reading an Antares SB . See the next section. 4.28.2...
Page 130: Writing Scripts
ﬁguration. 4.28.3 Writing Scripts Make sure of following the instructions on the TAIP Downloader Tool section of the Operation chapter and have TAIP Downloader already con- nected and communicating with Antares SB before proceeding. Make sure using version superior 1.0.2...
Page 131 4.28. USING SCRIPTS For more information on these software tools contact Digital Communi- cations Technologies...
Page 132: Scenarios And Examples
Scenarios and examples For this chapter It is assumed that the reader already has access to the unit’s TAIP console trough the unit’s serial port using a terminal software like Windows ’ Hyperterminal . Refer to the Operation chapter for more information.
Page 133: Creating A Destination Point (Dp)
5.1. GETTING STARTED The GSM registration status is indicated by the status LED. This LED is solid whenever the unit is not registered on GSM. Although the unit is not registered, it could be searching for the operator which is a normal con- dition.
Page 134: Creating A Destination Address (Da)
TCP listener. 4. The server is accepting the connection but it is immediately (or a few seconds later) closing it. 5. The Antares SB is behind a cellular carrier’s NAT which has the selected port blocked.
Page 135: Tiding A Signal To An Event
AVL application you can always shut it down an use some popular free TCP listener applications that will show you the RAW data where you can check the TAIP messages generated by the Antares SB Other useful tool is a network sniﬀer that allows you to analyze the traﬃc...
Page 136: Adding An Input Report
Now our unit is generating a 5 minutes periodic report and also a special report whenever the Input 3 goes high 5.1.9 Script This example can be resumed with the following script: #Antares SB script #Getting Started example #Delete any previous configuration >SRT;CONFIG< >SXADP**U<...
Page 137: Adding Sms Reporting
5.2. ADDING SMS REPORTING # server destination >SDA4;P00< #Time-only Time And Distance #signal definition >STD80300< #Event triggered by T&D signal >SED37NV4;TD8+< #Input report event >SED05NV4;IP3+< #end You can copy and paste this script to a new empty text ﬁle and have it save with a .tmf extension so TAIP Downloader software can pass it to a unit.
Page 138: Change The Input Report Event Deﬁnition
5.2. ADDING SMS REPORTING Now Destination Address 5 holds Destination Points 00 and 10. We can point any event to DA 5 making any report generated by the event to be routed to our AVL server an to the Telephone Number 912345678 at the same time.
Page 139: Script
Signal LED does not have to be solid ON. The cellular carrier has to provide SMS sending capabilities to the cellular line being used by the Antares SB The phone number 912345678 may not be exactly the phone number that should be used for sending SMS messages. A plus sign with country/area code or similar may be required.
Page 140: Adding Sms Interaction
5.3. ADDING SMS INTERACTION #signal definition >STD80300< #Event triggered by T&D signal >SED37NV4;TD8+< #Input report event >SED05NV5;IP3+< #User text message for event 05 >SXATM05Input 3 has been activated!< #end Adding SMS interaction Once a Phone-Number-type destination has been created it is possible to interact with the unit via SMS messages generated from that phone number, as long as the Destination conﬁguration allows TAIP console access to the conﬁgured DP.
Page 141: Adding Voice Interaction
5.4. ADDING VOICE INTERACTION phone number 912345678 the text message: >SSSXP21< The unit responds the following via SMS: >RSSXP21< Conﬁrming that it accepted the command and the output has been set high. Adding voice interaction The unit may receive or make calls from/to any of the Phone Number-type deﬁned Destinations.
Page 142: Ignition Detection
Ignition ON and OFF events are only going to be sent to the AVL server. 5.5.1 Script The resulting script: #Antares SB script #Getting Started example # + SMS reporting (+SMS interaction + Voice interaction) # + Ignition sense #Delete any previous configuration >SRT;CONFIG<...
Page 143: Speed Violation (With Warning) Report
5.6. SPEED VIOLATION (WITH WARNING) REPORT #The remote AVL server address and port >SXADP0000avl.server.com;2145< #The Phone-Number-type destination #with support for user-messages ON >SXADP1010912345678< #A Destination Address holding the # server destination >SDA4;P00< #A Destination Address holding the # server destination and phone number >SDA5;P00,P10<...
Page 144: Setting The Speed Limit
5.6. SPEED VIOLATION (WITH WARNING) REPORT 5.6.1 Setting the speed limit Up to 10 speed limits can be deﬁned on the unit, for no particular reason we choose the limit 07. Using the GS message we set the limit: >SGS0710650< Now any time the vehicle speed is above 65mph the S07 signal is going to be true.
Page 145: Script
LED oﬀ when the speed limits falls below: >SED43SV0;S07-;ACT=SSSXP10< 5.6.6 Script The resulting script: #Antares SB script #Getting Started example # + SMS reporting (+SMS interaction + Voice interaction) # + Ignition sense # + Speed viol. and warning #Delete any previous configuration >SRT;CONFIG<...
Page 146: Start/Stop Monitoring
5.7. START/STOP MONITORING >SED37NV4;TD8+< #Input report event >SED05NV5;IP3+< #User text message for event 05 >SXATM05Input 3 has been activated!< #Ignition ON event >SED19NV4;F00+< #Ignition OFF event >SED20NV4;F00-< #Set an speed limit of 65mph >SGS0710650< #Start a 15 secs. timer when #speed limit is violated #(silent event) >SED40SV0;S07+;ACT=SGC00TC00015<...
Page 147: Setting A Low Speed Limit
5.7. START/STOP MONITORING + Ignition sense + Speed violation and warning. Now we have to tell the unit what is a STOP and what is a START. There are several ways of doing this, for this example we are going to deﬁne a STOP situation to be when the vehicle’s speed remains below a small speed limit for a given period of time.
Page 148: Create The Start Report
5.7.6 Script The corresponding script of this conﬁguration plus all the examples worked so far is: #Antares SB script #Getting Started example # + SMS reporting (+SMS interaction + Voice interaction) # + Ignition sense # + Speed viol. and warning...
Page 149 5.7. START/STOP MONITORING #The Phone-Number-type destination #with support for user-messages ON >SXADP1010912345678< #A Destination Address holding the # server destination >SDA4;P00< #A Destination Address holding the # server destination and phone number >SDA5;P00,P10< #Time-only Time And Distance #signal definition >STD80300< #Event triggered by T&D signal >SED37NV4;TD8+<...
Page 150: Safe Engine Turn Oﬀ
5.8. SAFE ENGINE TURN OFF #Create the violation report >SED10NV4;C00+< #Drive a LED on output 1 ON #when the speed goes beyond the limit #(silent event) >SED42SV0;S07+;ACT=SSSXP11< #Drive a LED on output 1 OFF #when the speed falls off the limit #(silent event) >SED43SV0;S07-;ACT=SSSXP10<...
Page 151: Create The Speed Limit
5.8. SAFE ENGINE TURN OFF 4. We can also add an event to report when the output is actually set (i.e. the ignition is cut), let’s use event code 13 for this. We continue working on the same example worked so far. 5.8.1 Create the speed limit We set 15mph on the S01 limit:...
Page 152: Script
5.8. SAFE ENGINE TURN OFF 5.8.6 Script Adding a safe-engine-turn-oﬀ option leads to the following script: #Antares SB script #Getting Started example # + SMS reporting (+SMS interaction + Voice interaction) # + Ignition sense # + Speed viol. and warning...
Page 153 5.8. SAFE ENGINE TURN OFF #Event triggered by T&D signal >SED37NV4;TD8+< #------------------------------------------- #--Input sense------------------------------ #Input report event >SED05NV5;IP3+< #User text message for event 05 >SXATM05Input 3 has been activated!< #------------------------------------------- #--Ignition sense--------------------------- #Ignition ON event >SED19NV4;F00+< #Ignition OFF event >SED20NV4;F00-< #------------------------------------------- #--Speed viol.
Page 154: Operation
5.8. SAFE ENGINE TURN OFF #Speed limit for START/STOP detection >SGS0310080< #Start 2 minutes timer >SED38SV0;S03-;ACT=SGC01TC00120< #Stop the time >SED39SV0;S03+ACT=SGC01U< #Create the STOP report >SED30NV4;C01+< #Create the START report >SED31NV4;S03C01&+< #------------------------------------------- #--Safe engine turn off--------------------- #Set the speed limit for the time/speed #condition >SGS0110150<...
Page 155: Improving The Periodic Report
5.9. IMPROVING THE PERIODIC REPORT 2. If you receive a conﬁrmation of this message the turn oﬀ process has initiated. Wait for event 13 to report. When event 13 report is received it means that the given time/speed condition met and the vehicle’s engine has been turned oﬀ.
Page 156: Script
And leave the rest of the script unchanged. 5.9.1 Script Changing only the TD8 deﬁnition, our script ends up: #Antares SB script #Getting Started example # + SMS reporting (+SMS interaction + Voice interaction) # + Ignition sense # + Speed viol. and warning...
Page 157 5.9. IMPROVING THE PERIODIC REPORT #The Phone-Number-type destination #with support for user-messages ON >SXADP1010912345678< #A Destination Address holding the # server destination >SDA4;P00< #A Destination Address holding the # server destination and phone number >SDA5;P00,P10< #A complete Time And Distance criterion #min = 120 secs.
Page 158 5.9. IMPROVING THE PERIODIC REPORT >SED41SV0;S07-;ACT=SGC00U< #Create the violation report >SED10NV4;C00+< #Drive a LED on output 1 ON #when the speed goes beyond the limit #(silent event) >SED42SV0;S07+;ACT=SSSXP11< #Drive a LED on output 1 OFF #when the speed falls off the limit #(silent event) >SED43SV0;S07-;ACT=SSSXP10<...
Page 159: Reconnection Event For Tcp
A00 signal has to be used as the AVL server is deﬁned on the Destination Point 00: >SED49NV4;A00+< We chose event 49 for no particular reason. This will have the AVL server receiving event 49 any time a new connection from an Antares SB established. 5.10.1 Script...
Page 160 5.10. RECONNECTION EVENT FOR TCP >SXADP**U< #------------------------------------------- #--Essential configurations----------------- #Units ID >SIDEXAMPLE< #configuring the SIMs PIN >SRFI1234< #configuring the APN >SRFAinternet.carrier-name.com< #The remote AVL server address and port >SXADP0000avl.server.com;2145< #The Phone-Number-type destination #with support for user-messages ON >SXADP1010912345678< #A Destination Address holding the # server destination >SDA4;P00<...
Page 161 5.10. RECONNECTION EVENT FOR TCP >SED20NV4;F00-< #------------------------------------------- #--Speed viol. + warning-------------------- #Set an speed limit of 65mph >SGS0710650< #Start a 15 secs. timer when #speed limit is violated #(silent event) >SED40SV0;S07+;ACT=SGC00TC00015< #Stop the timer when the speed falls #below the limit #(silent event) >SED41SV0;S07-;ACT=SGC00U<...
Page 162: Main-Power-Loss Alarm
5.11. MAIN-POWER-LOSS ALARM #condition >SGS0110150< #Start 16 seconds timer when the speed #falls off the previously set value and #as long as the user signal is set >SED14SV0;S01!U00&+;ACT=SGC02TC00016< #Stop the timer when the speed condition #is violated >SED15SV0;S01+;ACT=SGC02U< #Ignition cut event #Sets output 4 high and #sends a report to DA 5 >SED13NV5;C02U00&+;ACT=SSSXP41<...
Page 163: Conﬁguring/Reading A Distance Counter
5.13. CONFIGURING/READING A DISTANCE COUNTER 5.13 Conﬁguring/reading a distance counter Refer to the XACR message. 5.14 Generating an extended-EV report Related commands: ED, EV, XAEF As mentioned on the Reports’ messages section of the Operation chapter, an EV report can be extended to include extra information tags .
Page 164 ;ID=EXAMPLE >REV311447147649+2578440-0802854301000512;AL=00001;AC=+08 ;ID=EXAMPLE And event 32 as >REV321447147747+2578440-0802854301000512;AC=-12;CV07=01203;SV=09 ;ID=EXAMPLE< Notice that the order of information tags deﬁned with the XAEF is not preserved, Antares SB reports the tags alphabetically. For detailed in- formation see the ED, EV and XAEF messages.
Page 165: Unit's Taip Reference
Unit’s TAIP reference...
Page 166: Al) Altitude
6.1. (AL) ALTITUDE (AL) Altitude Qualiﬁers: Q, R This message gives the vehicle’s altitude and vertical speed. The message has the following format: AAAAABBBBBBCCCCDE Chars Item Format Value Meaning GPS Time AAAAA seconds GPS time of day. Altitude BBBBBB meters Above Mean Sea Level Altitude.
Page 167: Cp) Compact Position
6.2. (CP) COMPACT POSITION (CP) Compact Position Qualiﬁers: Q, R This message gives the position solution. The message has the following format: AAAAABBBCCCCDDDDEEEEFG Chars Item Format Value Meaning GPS Time AAAAA seconds GPS time of day. Latitude BBB.CCCC degrees Latitude in the WGS-84 datum. Positive values indicate a northern latitude.
Page 168: Da) Destination Address
6.3. (DA) DESTINATION ADDRESS (DA) Destination Address Qualiﬁers: Q, S, R A Destination Address is an association of Destination Points. These allows an event deﬁned with the ED message to be routed to multiple receivers at the same time by selecting the Destination Address (or group) that holds all of the desired destinations (IP-types, Telephones, Serial Port).
Page 169: Examples
6.3. (DA) DESTINATION ADDRESS 6.3.1 Examples Creating DAs To create Destination Address 5 as an association of Destination Points 2, 3, 10 and 15 (15 is the unit’s serial port): >SDA5;P02,P03,P10,P15< To create Destination Address 0 with only one Destination Point, for example the unit’s serial port: >SDA0;P15<...
Page 170: Dp) Destination Point
6.4. (DP) DESTINATION POINT (DP) Destination Point Qualiﬁers: Q, S, R This command is deprecated and should not be used, use the XADP message instead. A Destination Point deﬁnes the IP address and/or cellular telephone of a destination. An association of Destination Points is used to deﬁne a Des- tination Address which is used in an Event Deﬁnition to route Event Mes- sages.
Page 171 6.4. (DP) DESTINATION POINT AABC[DDD...] Chars Item Format Value Meaning Destination 10-14 Decimal number holding the point’s index. In- Point ID dexes 00 to 09 refer to IP addresses where an AVL software is listening for TAIP messages. Indexes 10 to 14 refer to SMS receptors’ tele- phones.
Page 172: Ed) Event Deﬁnition
Qualiﬁers: Q, S, R This message is used to deﬁne events. These events deﬁne the Event Ma- chine conﬁguration for the Antares SB . An event is created by deﬁning a boolean combination of signals as a trigger, a routing indication for a gener- ated event message (EV or ET) and a possible TAIP message to be executed when the event occurs.
Page 173 6.5. (ED) EVENT DEFINITION AABCD;EEE [EEE][F] G[[;ACT=HH...][;ACT=HH...]...] Chars Item Format Value Meaning Event ID 00-49 Decimal number ranging between 00 to 49 (or ’**’). Event ﬂag Message routing: Handling Normal. Route the Event Message to the speciﬁed Destination Address (DA). Serial Port.
Page 174: Examples
6.5. (ED) EVENT DEFINITION 6.5.1 Examples Single signal triggers Example: Periodic report To deﬁne event 05 to send an EV Event Message every 3 minutes: 1. Use the TD message to conﬁgure a Time & Distance signal to trigger every 3 minutes: >STD70180<...
Page 175 Application notes AN0020EN and AN0021EN explains the binary form and a method to decode the binary messages sent by Antares SB that can be implemented in any server. Both application notes can be found at: http://www.digitalcomtech.com/support.html...
Page 176: Er) Error Report
6.6. (ER) ERROR REPORT (ER) Error Report Qualiﬁers: R This message is generated by the unit whenever the previous command en- tered on the TAIP console generates an error. The message has the following format: AA:[BBB...] Chars Item Format Value Meaning Error Error code: See the table of error...
Page 177: Et) Event Report, Time Only Message
6.7. (ET) EVENT REPORT, TIME ONLY MESSAGE (ET) Event Report, time only message Qualiﬁers: R This message is generated when an event is triggered. This message only contains date and time of the generated event. The message has the follow- ing format: AABBBBCDDDDD Chars...
Page 178: Ev) Event Message
6.8. (EV) EVENT MESSAGE (EV) Event Message Qualiﬁers: R This message is generated when an event is triggered and reported. The message has the following format: AABBBBCDDDDDEEEFFFFFGGGGHHHHHIIIJJJKL[EXTENDED-EV TAGS] Chars Item Format Value Meaning Event 00-49 Event code. code BBBB week Number of weeks since 00:00AM January 6, 1980.
Page 179 6.8. (EV) EVENT MESSAGE Meaning ;AL=AAAAA Altitude is A meters Above Mean Sea Level (AMSL). ;AC=AAA Acceleration is A [Miles] per [Hour per second] ;AD=AAAAA Voltage on the Analog port is A mV. ;BL=AAAAA Voltage of the back-up battery is A mV. ;CE=AAAABB Simple Cell ID information.
Page 180 Binary where each bit represents a ﬂag. The ﬂags from the Least Signiﬁcat Bit to the Most Signiﬁcant Bit are: SignalState True if the OBD is communicating with Antares SB . ChecksumError True if a checksum error was detected. Ignition True if the vehicle’s engine is on.
Page 181: Gc) Counters, Timers, Distancers
6.9. (GC) COUNTERS, TIMERS, DISTANCERS (GC) Counters, Timers, Distancers Qualiﬁers: Q, S, R This message is used to conﬁgure and manipulate internal counters. Each counter can be conﬁgured as a user-controlled counter, a timer, or a dis- tancer (counter updated by the traveled distance). For more information refer to the Conﬁguration chapter, Using Counters section.
Page 182: Counters' Commands
6.9. (GC) COUNTERS, TIMERS, DISTANCERS 6.9.1 Counters’ commands Value Meaning Sets the counter type to Counter with a threshold value de- ﬁned as DDDDD. The value for this type of counter can only be changed with the increment (I or value (V) command. Set and start a Timer counter with a threshold value deﬁned as DDDDD, time increment 1 or EEEEE seconds.
Page 183 6.9. (GC) COUNTERS, TIMERS, DISTANCERS are not interested on monitoring the C05 signal. We can query the distance counter value at any time: >QGC05V< Ant the unit shall respond: >RGC05V00997< Indicating that the traveled distance since the counter set is 99.7km (997 x 100m).
Page 184: Gf) Gpios' Function (I/O)
An output is deﬁned by setting the bit that corresponds to the GPIO’s index. An input is deﬁned by re- setting this bit. Only the following command works on Antares SB >SGFF0< Any other value will make the unit return error 86: >SGF00<...
Page 185: Gs) Speed Limit
6.11. (GS) SPEED LIMIT 6.11 (GS) Speed Limit Qualiﬁers: Q, S, R This message is used to conﬁgure the speed limits that can be used to trigger events. The message has the following format: AABCCCC Chars Item Format Value Meaning Speed 00-09 Identiﬁcation code assigned to...
Page 186: Gt) Time Window
6.12. (GT) TIME WINDOW 6.12 (GT) Time Window Qualiﬁers: Q, S, R This message is used to conﬁgure the Time Windows that can be used to trigger events. The signal associated with a Time Window becomes active when the actual date and time is between the values set by the TMin and TMax parameters.
Page 187: Gr) Regions
Use 99 to leave this ﬁeld bor 2 empty.Check the explanation after this table. The Antares SB has the ability to detect whether a vehicle is inside or outside of a user deﬁned polygon. In order to achieve this the point’s nu-...
Page 188: Special Cases
6.13. (GR) REGIONS A point is formed by the region’s index, the point’s index, the point’s latitude and longitude and by other two parameters called the left neighbors. The left neighbors of a point are the indexes of the points connected (if any) with a line to the actual point and have a longitude value equal to or less than the actual point’s longitude.
Page 189 6.13. (GR) REGIONS This region is drawn with the north pointing upwards so you can see how the leftmost point has the index 00 and the rightmost has the higher index 06 following the longitude ordering discussed above. Left neighbors Lets examine each point’s left neighbors according to the deﬁnition given.
Page 190 6.13. (GR) REGIONS As you can see points 02 and 03 share the same longitude. As discussed early it is not relevant which point comes ﬁrst, the points could be assigned having the 03 below the 02 instead of the arrangement presented in the ﬁgure.
Page 191 6.13. (GR) REGIONS Another approach would have been counting 02 as left neighbor Note: of point 03 but then we must be careful of not including 03 as left neighbor of point 02. Point 04. Left Neighbor 1 : Left Neighbor 2 : Point 05.
Page 192 6.13. (GR) REGIONS Point 03. Left Neighbor 1 : Left Neighbor 2 : Point 04. Left Neighbor 1 : Left Neighbor 2 : Point 05. Left Neighbor 1 : Left Neighbor 2 : Point 06. Left Neighbor 1 : Left Neighbor 2 : Point 07 has two left neighbors that share the same longitude.
Page 193: Id) Identiﬁcation
6.14. (ID) IDENTIFICATION 6.14 (ID) Identiﬁcation Qualiﬁers: Q, S, R This message is used to set/query unit’s ID. The message has the following format: A[AAA...] Chars Item Format Value Meaning 1 to 10 Vehicle ID A[AAA. . . ] string Identiﬁcation code assigned to the vehicle.
Page 194: Ms) Memory Session
6.15. (MS) MEMORY SESSION 6.15 (MS) Memory Session Qualiﬁers: S, R This message is deprecated and has no eﬀect on the unit.
Page 195: Mt) Mdt Mode
6.16. (MT) MDT MODE 6.16 (MT) MDT Mode Qualiﬁers: Q, S, R This message controls and starts the serial port’s MDT communication mode. The message has the following format: A[BBB[CCCD EE FF GG HH]][;ROUTE=I] Chars Item Format Value Meaning Mode ﬂag MDT mode: N: Normal(default)
Page 196: Pv) Position-Velocity
6.17. (PV) POSITION-VELOCITY 6.17 (PV) Position-velocity Qualiﬁers: Q, R This message gives the unit’s current position, velocity, heading, source of information and age of the data. The message has the following format: AAAAABBBCCCCCDDDDEEEEEFFFGGGHI Item Format Units Meaning GPS Time AAAAA seconds Time of the generated report.
Page 197: Rf) Radio Frequency Module Conﬁguration
6.18. (RF) RADIO FREQUENCY MODULE CONFIGURATION 6.18 (RF) Radio Frequency module conﬁguration Qualiﬁers: Q, S, R This message is used to conﬁgure Cellular Network parameters. Any RF parameter can be left empty by issuing the command Note: without the B string The message has the following format: A[BBB...] Item...
Page 198: Rm) Reporting Mode
6.19. (RM) REPORTING MODE 6.19 (RM) Reporting Mode Qualiﬁers: Q, S, R This message controls ﬂags used to change the format of the responses and reports, i.e. messages with the R qualiﬁer. The message has the following format: [;ID FLAG=A][;EC FLAG=B][;CR FLAG=C][;ER FLAG=D][;CS FLAG=E] Chars Item Format...
Page 199: Rp) Registration Parameters (Cellular Network)
6.20. (RP) REGISTRATION PARAMETERS (CELLULAR NETWORK) 6.20 (RP) Registration Parameters (Cellular Network) Qualiﬁers: Q, R This message reports the unit’s cellular registration state. The message has the following format: ABBCCCC Item Format Units Meaning Registration Values: state registered searching operator. Registered in home network.
Page 200 6.20. (RP) REGISTRATION PARAMETERS (CELLULAR NETWORK) RSSI [-dBm] 0 to 7 113 - 99 Very poor 8 to 13 97 - 87 Poor 14 to 17 85 - 79 Fair 18 to 20 77 - 73 Fair 21 to 24 71 - 65 Good 25 to 31...
Page 201: Rt) Reset Message
6.21. (RT) RESET MESSAGE 6.21 (RT) Reset message Qualiﬁers: S, R When this message is issued alone the unit performs a system reset. When used with qualiﬁers it serves multiple internal initializations purposes. The message has the following format: [;CONFIG][;SIGNALS] Qualiﬁer Meaning Deletes the contents of the S&F buﬀer.
Page 202: Ss) Signal Status
6.22. (SS) SIGNAL STATUS 6.22 (SS) Signal Status Qualiﬁers: Q, S, R This message allows for the inspection of signals’ state and the setting of outputs and other manipulatable signals. See the Signals’ list on the Event Machine section of the Conﬁguration chapter. The message has the following format: AAA[B] Chars Item...
Page 203 6.22. (SS) SIGNAL STATUS >SSSXP31< To deactivate it: >SSSXP30< See the Conﬁguration and Operation chapters for more examples.
Page 204: St) Status
6.23. (ST) STATUS 6.23 (ST) Status Qualiﬁers: Q, R This message provides information about the unit’s GPS receiver. The message has the following format: AABCDDEFGG Chars Item Format Value Meaning Tracking Hex characters: 00- GPS satellite signal acquisition and tracking Status status.
Page 205: Tm) Time And Date
6.24. (TM) TIME AND DATE 6.24 (TM) Time and Date Qualiﬁers: Q, R This message provides information about the unit’s Time and Date as provided by the GPS service. The message has the following format: AABBCCDDDEEFFGGGGHHIJJKLLLL Chars Item Format Value Meaning Hour decimal...
Page 206: Td) Time And Distance Signals Conﬁguration
6.25. (TD) TIME AND DISTANCE SIGNALS CONFIGURATION 6.25 (TD) Time and Distance signals conﬁguration Qualiﬁers: Q, S, R The Time and Distance signals are set by its corresponding Time and Distance counter which is a counter that follows a Time and Distance criteria. This criteria allows to create a counter that does not follow a time or distance criteria inde- pendantely from each other, instead, combines these two variables to generate an intelligent trigger to be used for a more eﬃcient vehicle tracking.
Page 207 6.25. (TD) TIME AND DISTANCE SIGNALS CONFIGURATION The TD message allows to conﬁgure the parameters that control the Time & Dis- tance signals’ trigger. Ten TD counters may de deﬁned independantely. The message has the following format: ABBBB[CCCCDDDDEEEE] Chars Item Format Value Meaning...
Page 208: Tx) Text Message
Text Messages to the server using the following modiﬁcations of the TX TAIP message: (TXGMKI) Garmin Mode Driver ID - Unsolicited This message will be sent by Antares SB each time the user changes the Driver ID on the Garmin device. This message has the following format:...
Page 209 Antares SB if the Garmin device support Application Protocol A603. If the complete Stop Message list is deleted, Antares SB will only report that the last message on the list was deleted. This message has the following...
Page 210 But if the user deletes the Stop Message, Antares will send this message instead: RTXGMSS000104--- (TXGMTC) Garmin Mode Canned Reply - Unsolicited This message will be sent by Antares SB each time the user selects a Canned Reply that was generated by a Canned Reply Text Message. This message has...
Page 211 Canned Reply was choosen: RTXGMTC062023468800000001;ID=Test (TXGMTR) Garmin Mode Received Text Message - Unsolicited This message will be sent by Antares SB each time the user sends a text message using the Garmin device. This is an unsolicited message and the server should be conﬁgured to receive this message.
Page 212 6.26. (TX) TEXT MESSAGE (TXGMTS) Garmin Mode Sent Message Status - Unsolicited This message will be sent by Antares SB each time the user performs an action on a Text Message found in the Garmin’s Inbox. This message will only be sent by Antares SB if the Garmin device support Application Protocol A604.
Page 213: Vr) Version Number
6.27. (VR) VERSION NUMBER 6.27 (VR) Version number Qualiﬁers: Q, R This message returns the unit’s ﬁrmware version The message has the following format: Antares GPS [A]A.AA[B][C] Chars Item Format Value Meaning Version A.AA Firmware version number. number Reserved Reserved...
Page 214: Xaac) Analog To Digital Converter
6.28. (XAAC) ANALOG TO DIGITAL CONVERTER 6.28 (XAAC) Analog to Digital converter Qualiﬁers: Q, R Use this message to consult the actual computed value of the ADC. The message has the following format: AAAAAPBBB Chars Item Format Value Meaning ADC Com- AAAAA millivolts ADC computed value: Average value...
Page 215: Xaau) Challenge Text
6.29. (XAAU) CHALLENGE TEXT 6.29 (XAAU) Challenge Text Qualiﬁers: Q, R Use this message to send the Challenge Text to Antares SB in order to authen- ticate the connection. The message has the following format: ABBB... Chars Item Format Value...
Page 216: Xabs) Battery Status
6.30. (XABS) BATTERY STATUS 6.30 (XABS) Battery Status Qualiﬁers: Q, R Use this message to consult the actual state of the built-in back up battery . The message has the following format: ABBBBPCCC Chars Item Format Value Meaning Main ﬂag Indicates that the main power source Power (vehicle’s battery) is ON (1) or OFF...
Page 217: Xace) Cell Environment
6.31. (XACE) CELL ENVIRONMENT 6.31 (XACE) Cell Environment Qualiﬁers: Q, R Use this message to query Cellular Network Cell Environment information. The message has the following format: A[;BBB...] Chars Item Format Value Meaning Query type Type of query: 1: Cell ID information as described out- side the table.
Page 218: Xacr) Counter Report
6.32. (XACR) COUNTER REPORT 6.32 (XACR) Counter Report Qualiﬁers: S, R Use this message to have the unit generate a TX message to a Destination Point (DP) or Destination Address (DA) containing an speciﬁc counter’s (see GC mes- sage) value. The message takes a counter’s index, and a DP or DA index. The message has the following format: AABB Chars...
Page 219: Xact) Communication Test
6.33. (XACT) COMMUNICATION TEST 6.33 (XACT) Communication Test Qualiﬁers: S, R Use this message to generate an event code to a Destination Address (DA). This message is used to test the communication with a given destination(s) without requiring for an speciﬁc event to occur. It is also a method for testing a DA deﬁnition and testing the remote host identiﬁcation process of an EV message.
Page 220: Xadm) Diagnostic Message
6.34. (XADM) DIAGNOSTIC MESSAGE 6.34 (XADM) Diagnostic Message Qualiﬁers: Q, R Use this message to query unit’s status. The message has the following formats: For diagnostic level 0: ABBCCDEFFGHIIJKLMMNN Chars Item Format Value Meaning level Diagnostic level. 0: First level FW family Firmware family.
Page 221 6.34. (XADM) DIAGNOSTIC MESSAGE ABBCCDDEFGGHIJJKLMNNOOPPQQRRR Chars Item Format Value Meaning level Diagnostic level. 1: Second level FW family Firmware family. Always return 05 FW version – Firmware version. version – Type SV: Stable Version. Ax: Alfa version. x indicates the revision number Bx: Beta version.
Page 222 6.34. (XADM) DIAGNOSTIC MESSAGE For example, to query, send: QXADM0 The unit responds: RXADM0053090310007320F000 Wwhen using 1 as Diagnostic level: QXADM1 The unit responds: RXADM10530B690310008320F0001515000...
Page 223: Xadp) Destination Points
6.35. (XADP) DESTINATION POINTS 6.35 (XADP) Destination Points Qualiﬁers: Q, S, R This message conﬁgures both IP-type and Telephone destinations. 6.35.1 IP-type destinations For IP-type destination, i.e. Destination Points 00 to 09 use the following format and table: AABCD[DDD...];E[EEE...] Chars Item Format Value...
Page 224 6.35. (XADP) DESTINATION POINTS AABCD[DDD...] Chars Item Format Value Meaning Destination 10-14 Telephone destination point. Point index Type of host or DP type/Action: Delete action Delete the Destination Point. Report messages are sent as TAIP messages to this destination. User-deﬁned messages are sent in- stead of TAIP.
Page 225: Xaef) Extended-Ev Message Formats
6.36. (XAEF) EXTENDED-EV MESSAGE FORMATS 6.36 (XAEF) Extended-EV message Formats Qualiﬁers: Q, S, R This message allows the creation and conﬁguration of up to three sets of infor- mation tags to be used by an event having the Message ID qualiﬁer set to A, B or C.
Page 226 6.36. (XAEF) EXTENDED-EV MESSAGE FORMATS See the Reports’ messages section on the Operation chapter, the Event Machine section on the Conﬁguration chapter and the ED and EV TAIP messages for more information. See also the Scenarios and examples chapter.
Page 227: Xafu) Firmware Upgrade (Over The Air)
ABBBBCCDD Chars Item Format Value Meaning Server Firmware server: Use 0 for DCT’s servers, 1 for user- deﬁned server Firmware Ver- BBBB Firmware Version to download. The ﬁrst two char- sion acters must always be 05 which indicate ﬁrmware family.
Page 228: Xaga) Adc Levels
6.38. (XAGA) ADC LEVELS 6.38 (XAGA) ADC levels Qualiﬁers: Q, S, R This message is used to conﬁgure analog-to-digital converter levels associated to ”D” signals. The message has the following format: AABCCCCC Chars Item Format Value Meaning ADC level 00-04 Identiﬁcation code assigned to the ADC level.
Page 229: Xagb) Back-Up Battery Levels
6.39. (XAGB) BACK-UP BATTERY LEVELS 6.39 (XAGB) Back-up Battery levels Qualiﬁers: Q, S, R This message is used to conﬁgure back-up battery levels associated to ”B” signals. The message has the following format: AABCCCCC Chars Item Format Value Meaning Battery 00-04 Identiﬁcation code assigned to the level ID...
Page 230: Xagf) Store & Forward Thresholds
6.40. (XAGF) STORE & FORWARD THRESHOLDS 6.40 (XAGF) Store & Forward Thresholds Qualiﬁers: Q, S, R The Store & Forward Thresholds allow to create reports based on the number of stored events in the Store & Forward Buﬀer of a particular Destination Point. The message has the following format: AABCCDDDD Chars...
Page 231: Xagh) Heading Deltas
6.41. (XAGH) HEADING DELTAS 6.41 (XAGH) Heading deltas Qualiﬁers: Q, S, R This message is used to conﬁgure heading changes to be monitored with J signals. The message has the following format: AABCCC Chars Item Format Value Meaning Index 00-04 Heading delta index.
Page 232: Xagm) Garmin Mode
It also allows to receive Stop Messages from the server, that can help create routes for the vehicle to follow. Antares SB can work with any Garmin device that have the Fleet Management Protocol implemented.
Page 233: (Xagmi) Consult Garmin Device General Information
6.42. (XAGM) GARMIN MODE When Garmin sends a message to the server which uses the time ﬁeld, the value will reﬂect the same time set on the Garmin device. However, when sending messages from the server, the Garmin Note: device will handle any time value received as GMT 0. Because of this the time value used in the messages sent to Garmin must be calculated using the local GMT oﬀset.
Page 234: Xagmksa) Garmin Mode Add Driver Status
For example, to set a new Driver ID, use the following message: SXAGMKI00000000010620229003AuthorizedDriver Antares SB will respond like this to conﬁrm that the Driver ID was set: RXAGMKI00000000010620229003AuthorizedDriver;ID=Test To query the current Driver ID set on the Garmin device, use this message:...
Page 235: Xagmksd) Garmin Mode Delete Driver Status
For example, to delete a Driver Status from the Garmin device’s list, use this message: SXAGMKSD0000000001 Antares SB will reponse like this to conﬁrm that the Driver Status was deleted: RXAGMKSD0000000001;ID=Test It is possible to delete all the Driver Status with a single message, please refer to the TAIP message XAGMX for more information on this.
Page 236: Xagmr) Garmin Mode Add Or Delete Canned Replies
To add or delete a Canned Reply to the Garmin device use the R modiﬁer. This list can not be consulted on the Garmin device. The server must know the IDs that have been set in order to use them. Antares SB will repond with Error 94 if an Id that has not been set is used.
Page 237: Xagms) Garmin Mode Stop Message
If the result of this operation is a number with less than 10 digits, it must be preceded with as many “0” as needed to complete the 10 digits. For example: Latitude: 25.7827 * 11930464.7 = 307599592 This number should be typed in for Antares SB like this: +0307599592...
Page 238 6.42. (XAGM) GARMIN MODE Longitude: -0.1197 * 11930464.7 = -1428076 This number should be typed in for Antares SB like this: -0001428076 When using the S qualiﬁer to send a Stop Message, use the following format: AAABBBBBBBBBBCCCCCCCCCCCDDDDDDDDDDDE[EEE...] Chars Item Format...
Page 239: Xagmcs) Garmin Mode Change Stop Message Status
6.42. (XAGM) GARMIN MODE AAABBBCCC Chars Item Format Value Meaning Stop ID 000-255 ID used to identify the Stop Message to be con- sulted. Status 100-104 100: Active status. The Stop is active. The value of Index will correspond to the cur- rent position of the Stop in the list.
Page 240: Xagmts) Garmin Mode Text Send
6.42. (XAGM) GARMIN MODE AAAB Chars Item Format Value Meaning Stop ID 0-255 ID used to identify the Stop Message to be modiﬁed. Status The status in which the Stop Mes- sage will be set. 1: Mark Stop as Done. 2: Mark Stop as Active.
Page 241: Xagmt) Garmin Mode Message Status
ﬁes each message sent to the Garmin device. Each message must have a diﬀerent ID. If a message is sent us- ing an ID that is already in use by Garmin, Antares SB will return Er- ror 67. Message Type ﬂag Indicates how Garmin should handle the message.
Page 242: Xagmta) Garmin Mode Set Canned Message
6.42. (XAGM) GARMIN MODE AAAAAB Chars Item Format Value Meaning Message ID AAAAA 00000- The ID of the message to be con- 99999 sulted. Message Sta- Indicates the status of a message in the Garmin device. 0: Message is unread. 1: Message is read.
Page 243: Xagmx) Delete Fleet Management Protocol Related Data
RXAGMX7;ID=Test The Garmin device will then restart and the Fleet Management icon will no be shown. To enable the Fleet Management features on the Garmin device again, send the Garmin Mode enable message to Antares SB . For example: SXAGME0...
Page 244: Xagn) Acceleration Limits
6.43. (XAGN) ACCELERATION LIMITS 6.43 (XAGN) Acceleration Limits Qualiﬁers: Q, S, R This message is used to conﬁgure positive and negative acceleration limits (thresh- olds). Acceleration thresholds are monitored with the N signals. Note that for positive acceleration thresholds, Acceleration Sig- nals are TRUE when the vehicle’s acceleration is larger than the Warning: threshold.
Page 245: Xagp) Gprs Pause
6.44. (XAGP) GPRS PAUSE 6.44 (XAGP) GPRS Pause Qualiﬁers: Q, S, R Use this message to make the unit close any open TCP sockets, and end the current GPRS session. After 20 seconds the unit will start the GPRS session again. The message has the following format: Chars Item...
Page 246: Xagr) Circular Regions
6.45. (XAGR) CIRCULAR REGIONS 6.45 (XAGR) Circular Regions Qualiﬁers: Q, S, R Use this message to create up to 100 circular regions based on a center’s coordi- nates and a radius. Use the XAIR to create a circular region centered on the actual unit’s GPS position.
Page 247: Xaid) Imei As Id
6.46. (XAID) IMEI AS ID 6.46 (XAID) IMEI as ID Qualiﬁers: Q, S, R This message tells the unit whether to use or not (defaults to not) its IMEI as ID. Chars Item Format Value Meaning action Use 1 to set the unit’s ID with the IMEI. Use 0 to set the unit’s ID to the value set by the user with the ID message.
Page 248: Xaim) Imei Consult
6.47. (XAIM) IMEI CONSULT 6.47 (XAIM) IMEI consult Qualiﬁers: Q, R This message is used to consult the unit’s IMEI (International Mobile Equipment Identity). AAAAAAAAAAAAAAB Chars Item Format Value Meaning IMEI IMEI. IMEI’s CS IMEI’s Check Sum.
Page 249: Xaio) Input, Outputs Consult
6.48. (XAIO) INPUT, OUTPUTS CONSULT 6.48 (XAIO) Input, Outputs consult Qualiﬁers: Q, R This message is used to consult the actual state of inputs and outputs. ;XABCD;IEFHJ;GKLM Chars Item Format Value Meaning Out 4 ﬂag State of Output 4 (1=active, 0=inactive). Out 3 ﬂag State of Output 3.
Page 250: Xaip) Ip Address
6.49. (XAIP) IP ADDRESS 6.49 (XAIP) IP address Qualiﬁers: Q, R This message is used to consult the actual IP address assigned to the unit by the carrier. IP address 0.0.0.0 is returned when the GPRS session is not up. The message has the following format: AAABBBCCCDDD Chars...
Page 251: Xair) Create Circular Region "Here
6.50. (XAIR) CREATE CIRCULAR REGION “HERE” 6.50 (XAIR) Create Circular Region “here” Qualiﬁers: S, R When this command is given to the unit, a circular region centered at the actual position is created with the radius given. See also the XAGR to create Circular Regions manually.
Page 252: Xait) Driving Metrics
6.51. (XAIT) DRIVING METRICS 6.51 (XAIT) Driving Metrics Qualiﬁers: S, Q, R Use this message to consult the actual vehicle’s acceleration, maximum registered positive acceleration, maximum registered negative (breaking) acceleration and maximum registered speed. This command allows to consult also the GPS situa- tion of the vehicle when each maximum occurred.
Page 253: Xaka) Keep Alive
6.52. (XAKA) KEEP ALIVE 6.52 (XAKA) Keep Alive Qualiﬁers: S, Q, R This message is used to activate/deactivate a keep-alive to a given IP-type Des- tination Point (see the XADP message). A keep-alive option should be avoided as increases the transmission cost. Use this option if you need to be able of interro- gating the unit at any time and the unit is working behind a NAT.
Page 254: Xakl) Gps Back Log
6.53. (XAKL) GPS BACK LOG 6.53 (XAKL) GPS Back Log Qualiﬁers: Q, R This message is used to retrieve up to the last 60 messages received from the unit’s built-in GPS module. The message has the following format: [AAAA] Chars Item Format Value...
Page 255: Xall) Local Lock
6.54. (XALL) LOCAL LOCK 6.54 (XALL) Local Lock Qualiﬁers: S, Q, R This message is used to lock/unlock most conﬁguration messages ( S messages) and query messages ( Q messages) on the TAIP console for the serial port. A locking operation consists of using this message and a user-deﬁned 4-character code.
Page 256: Xamd) Md5 Check
Use this message to check the MD5 checksum value of any string. This message is used mostly as a diagnostics message that helps conﬁrm the MD5 checksum values calculated by Antares SB and/or the server performing the authentication. This message has the following format: AAA...
Page 257: Xanb) Network Band Mode
6.56 (XANB) Network Band mode Qualiﬁers: S, Q, R Antares SB is capable of working on 4 diﬀerent cellular bands in the following way: With this command the user selects a mode which may be of mono band or dual-band type. On dual-band modes, bands are automatically switched by the module according to network discovery information.
Page 258: Xans) Network Status (Gprs)
6.57. (XANS) NETWORK STATUS (GPRS) 6.57 (XANS) Network Status (GPRS) Qualiﬁers: Q, R Use this message to consult the state of the GPRS session and the state of the TCP sockets of every IP-type Destination Point. The message has the following format: ABB[ ;CDEEE x 10] Chars...
Page 259: Xaoe) Engine's Rpm Thresholds
6.58. (XAOE) ENGINE’S RPM THRESHOLDS. 6.58 (XAOE) Engine’s RPM thresholds. Qualiﬁers: Q, S, R This message is used to conﬁgure the RPM threshold levels associated to the “OE” signals. The message has the following format: ABCCCCC Chars Item Format Value Meaning Index Threshold index.
Page 260: Xaof) Fuel Level Percentage Values
6.59. (XAOF) FUEL LEVEL PERCENTAGE VALUES. 6.59 (XAOF) Fuel Level percentage values. Qualiﬁers: Q, S, R This message is used to conﬁgure the fuel level thresholds associated to the “OF” signals. This fuel level thresholds are presented in a percentage value. The message has the following format: ABCCC Chars...
Page 261: Xaog) Remaining Fuel Gallons Thresholds
6.60. (XAOG) REMAINING FUEL GALLONS THRESHOLDS. 6.60 (XAOG) Remaining Fuel Gallons thresholds. Qualiﬁers: Q, S, R This message is used to conﬁgure the fuel level thresholds associated to the “OG” signals. This fuel level thresholds are presented in Gallons remaining. The message has the following format: ABCCC Chars...
Page 262: Xaor) Fuel Rate Thresholds
6.61. (XAOR) FUEL RATE THRESHOLDS 6.61 (XAOR) Fuel Rate thresholds Qualiﬁers: Q, S, R This message is used to conﬁgure the fuel rate thresholds associated to the “OR” signals. This fuel rate thresholds are presented in Gallons per hour. The message has the following format: ABCCC Chars...
Page 263: Xaos) Obd Status Consult
6.62. (XAOS) OBD STATUS CONSULT 6.62 (XAOS) OBD Status Consult Qualiﬁers: Q, R Use this message to consult the Vehicle-Interface-Antares communication state, the vehicle’s supported OBD variables and the OBD variables’ values. The mes- sage has the following format: A[B[;CC[:DDD...];EE[:FFF...]...]] Chars Item Format...
Page 264 Indicating that communication is OK and the parameters that can be updated from the vehicle are Speed, Engine Speed, Throttle position, Ignition, MIL, Trip Odometer and Secondary Tool status. All other parameters are not supported by the Interface model connected to Antares SB when reading a particular vehicle. Furthermore, using: >QXAOS1<...
Page 265: Xaot) Throttle Position Thresholds
6.63. (XAOT) THROTTLE POSITION THRESHOLDS. 6.63 (XAOT) Throttle Position thresholds. Qualiﬁers: Q, S, R This message is used to conﬁgure the Throttle Position thresholds associated to the “OT” signals. The message has the following format: ABCCC Chars Item Format Value Meaning Index Threshold index.
Page 266: Xapm) Power Management
6.64. (XAPM) POWER MANAGEMENT 6.64 (XAPM) Power Management Qualiﬁers: S, Q, R This command activates/deactivates the unit’s power saving mode (sleep mode). When power saving mode is activated, the unit will go to sleep after 2 minutes as long as no communication activity is detected over the GPRS network, SMS channels or local TAIP console.
Page 267 6.64. (XAPM) POWER MANAGEMENT A[[[[BBBBBCDEFGHI]JJJJ]KKKK]LLLL] Chars Item Format Value Meaning Action Action: Activate the power saving mode. End any active power saving mode. Go to power saving mode immedi- ately(*). Flags BBBBB Reserved ﬂags. Should be set to 11111 Power ﬂag Set to 1 to monitor the power detector input when in sleep mode.
Page 268: Examples
6.64. (XAPM) POWER MANAGEMENT (*) When going to sleep immediately using the ’I’ qualiﬁer the saving mode is not preserved. i.e. after the unit wakes up the unit ends the power saving mode. 6.64.1 Examples Activate the power saving mode. Only the vehicle’s ignition may awake the unit, and when awaken, the unit must remain up for 20 minutes: SXAPMA000000010000020m Activate the power saving mode.
Page 269: Xapw) Set Password
For example, to set a password, use the following conﬁguration: SXAPWpassword To consult if a password is set, use the following message: QXAPW Antares SB will respond like this: RXAPW1 Indicating that a password is set, but it will never show the actual password.
Page 270: Xard) Reset Diagnostics
6.66. (XARD) RESET DIAGNOSTICS 6.66 (XARD) Reset diagnostics Qualiﬁers: S, Q, R This messages activates/deactivates the system’s resets’ information displayed with TX messages to a selected DA or DP. The message has the following for- mat: Chars Item Format Value Meaning DA or DP / Ac- Command:...
Page 271: Xare) Regions Report
6.67. (XARE) REGIONS REPORT 6.67 (XARE) Regions Report Qualiﬁers: Q, R Use the Region ID report to deﬁne a single event for several circular and polygonal regions. A report will be sent using only one event code when the associated regions’...
Page 272: Xasd) Destinations' Set
6.68. (XASD) DESTINATIONS’ SET 6.68 (XASD) Destinations’ Set Qualiﬁers: Q, R Use this message to query which Destination Points and Destination Addresses are set on the unit. This is useful for knowing which DPs and DAs are deﬁned, preventing a one-by-one query with the XADP and DA messages. The message has the following format: It returns a string which contains a P plus a two-digit number for each DP set and an A plus a two-digit number for each DA found.
Page 273: Xasf) Store & Forward Buﬀer
6.69. (XASF) STORE & FORWARD BUFFER 6.69 (XASF) Store & Forward Buﬀer Qualiﬁers: Q, R Use this message to consult the reports’ buﬀer state of a given Destination The message has the following format: AA[BBBBB;CCCCC;DDDDD] Chars Item Format Value Meaning Destination 00-14 Destination Point.
Page 274: Xasg) Sms Messages Gateway
6.70. (XASG) SMS MESSAGES GATEWAY 6.70 (XASG) SMS Messages Gateway Qualiﬁers: Q, S, R The SMS Messages Gateway allows Antares SB to send any text message through a TAIP message. Antares SB will retry to send the message up to three times, if it fails to send it the message will be canceled.
Page 275: Xasi) Imsi Consult
6.71. (XASI) IMSI CONSULT 6.71 (XASI) IMSI Consult Qualiﬁers: Q, R Use this message to consult the unit’s International Mobile Subscriber Identity (IMSI). The message has the following format: [AAA...] Chars Item Format Value Meaning IMSI varies International Mobile Subscriber Identity...
Page 276: Xata) Sms Alias
Text message associated with the TAIP message to be executed. For example, to create a SMS Alias that will set the Output 1 of Antares SB true use this message: >SXATA001;SSSXP11;VehicleOFF< For this example, Output 1 is connected to a Engine Turn OFF Circuit that will turn the vehicle oﬀ...
Page 277: Xatd) Current Destination Point
6.73. (XATD) CURRENT DESTINATION POINT 6.73 (XATD) Current Destination Point Qualiﬁers: Q, R Use this message to know the DP index used on the actual communication channel. The command will return the DP index used to generate the QXATD query. The message has the following format: Chars Item...
Page 278: Xatm) User-Deﬁned Text Messages
6.74. (XATM) USER-DEFINED TEXT MESSAGES 6.74 (XATM) User-deﬁned Text Messages Qualiﬁers: S, Q, R Use this message to set the user-custom messages to be used when an SMS report is to be generated to a Telephone-type Destination conﬁgured to receive non-TAIP messages.
Page 279: Xats) Taip Console Sniﬀer
6.75. (XATS) TAIP CONSOLE SNIFFER 6.75 (XATS) TAIP Console Sniﬀer Qualiﬁers: S, R Use this message to activate/deactivate the debugging tool that throws to the serial port all of the TAIP console messages exchanged over any communication media. This is useful to check the communication between an IP-host software or Telephone and the unit.
Page 280: Xaun) Udp Network
6.76. (XAUN) UDP NETWORK 6.76 (XAUN) UDP Network Qualiﬁers: S, Q, R An UDP-Network can be set as a validation mechanism for UDP queries orig- inated to the unit’s UDP-Server Port conﬁgured with the XAUP message. The UDP-Network validation for the UDP-Server port is optional as the validation is also done by looking for a match on the IP-type, UDP Destinations deﬁned as IP-numbers When an UDP-Network is set, the validation for UDP queries received on the...
Page 281: Xauo) Udp Origin Port
6.77. (XAUO) UDP ORIGIN PORT 6.77 (XAUO) UDP Origin Port By default Antares SB chooses the value of the UDP-origin-port when sending UDP datagrams. Usually after a GPRS session has been established, the cho- sen port is 1024. This value is incremented and reused according to the unit’s TCP/IP stack.
Page 282: Xaup) Udp Server Port
6.78. (XAUP) UDP SERVER PORT 6.78 (XAUP) UDP Server Port Qualiﬁers: S, Q, R This command is used to conﬁgure a listening UDP port on the unit. If the spe- cial value 00000 is used the unit won’t listen for UDP messages on a ﬁxed port, instead it will only use the dynamic port created when it sends reports to a UDP destination.
Page 283: Xavc) Voice Call Start
6.79. (XAVC) VOICE CALL START 6.79 (XAVC) Voice Call Start Qualiﬁers: S, R This command is used to initiate a voice call with a Telephone-type Destination Point (DPs 10 to 14). Two optional ﬁelds are provided to specify a retry number and a time between retries for failing calls.
Page 284: Xave) Voice Call End
6.80. (XAVE) VOICE CALL END 6.80 (XAVE) Voice Call End Qualiﬁers: S, R Use this message to hang-up any current voice call. If no voice call is being held, the command returns error 65 ( RER65:SXAVE ). The message has the following format: ...No parameters ...
Page 285: Xavi) Voice Call Identiﬁcation Switch
6.81. (XAVI) VOICE CALL IDENTIFICATION SWITCH 6.81 (XAVI) Voice Call Identiﬁcation switch Qualiﬁers: S, R, Q This command is used to turn ON/OFF the voice call number validation per- formed by the unit on incoming voice calls. It defaults to ’ON’, meaning that the calling-party’s number has to be deﬁned on any of the Telephone-type destinations in order for the unit to accept the call .
Page 286: Xavm) Microphone Gain
6.82. (XAVM) MICROPHONE GAIN 6.82 (XAVM) Microphone gain Qualiﬁers: S, R, Q This command is used to change the microphone gain for voice calls. Chars Item Format Value Meaning Action/value 0-9, +, - Gain value (0-9) or gain action: + to increase, - to decrease.
Page 287: Xavo) Virtual Odometer
6.83. (XAVO) VIRTUAL ODOMETER 6.83 (XAVO) Virtual Odometer Qualiﬁers: S, Q, R Use this message to consult the current value of the Virtual Odometer or to set a new value for it. This mesasage can also be used to conﬁgure up to ﬁve distance thresholds associated with the L signals.
Page 288: Xavs) Speaker Volume
6.84. (XAVS) SPEAKER VOLUME 6.84 (XAVS) Speaker volume Qualiﬁers: S, R, Q This command is used to change the speaker volume for voice calls. Chars Item Format Value Meaning Action/value 0-9, +, - Volume value (0-9) or volume action: + to increase, - to decrease.
Page 289: Errors List
6.85. ERRORS LIST 6.85 Errors list The following table contains a list of the errors returned by the unit with the ER message. See the ER message for more information.
Page 290 6.85. ERRORS LIST Description Unrecognized command The message is not delimited by > and/or < ID miss match on incoming postﬁx “;ID= ” KY miss match on incoming postﬁx “;KY= ” Not a valid set message. Missing parameter. TAIP console is restricted for this DP. See the locking parameters on the XADP message. Queries resulting on multiple answers are not supported over the air.
Page 291 6.85. ERRORS LIST Continued from the previous page. Description Invalid XAGA or XAGB query. Wrong XAGA or XAGB parameter. Internal communication problem. Length exceeded for TX message. See the TX message. Invalid event index when using the XATM message. See the XATM message. Invalid XATM message format.
Page 292 6.85. ERRORS LIST Continued from the previous page. Description Problem with the Canned Reply ID. Try a new ID. Wrong point index. See the GR message. Checksum error. Missmatch or checksum was not present in the response message. Unavailable feature. Operation not allowed.
Page 293: Appendix A - Quick Start Guide
Appendix A - Quick Start Guide The next two pages are a quick guide for installing and conﬁguring the unit. You can print these two pages and have them at hand.
Page 296 Appendix B - Getting Started Script Select the following script and paste it on any plain-text editor to create the GettingStarted.tmf script ﬁle. #Antares SB script #Getting Started example #Delete any previous configuration >SRT;CONFIG< >SXADP**U< #Unit’s ID >SIDEXAMPLE< #configuring the SIM’s PIN >SRFI1234<...
Page 297 Appendix C - Signals’ Table For more information on signals refer to the Conﬁguration chapter, Event Machine section. The available signals for the Antares SB are presented in the next table on the next page.
Page 298 Signal Description A00 - A09 Destination Points’ state True when the IP address/port deﬁned on the corresponding Destination Point’s index is accepting a TCP connection or when using UDP (i.e. the TCP/UDP socket is open). See the XADP message. B00 - B04 Battery Levels(+) True when the unit’s back-up battery level is above the value deﬁned with the XAGB message.
Page 299 Signal Description OE0 - OE4 Engine’s RPM thresholds True when the egine’s RPM detected by the OBD is higher than the corresponding RPM thresholds. See the XAOE mes- sage. OT0 - OT4 Throttle Position thresholds True when the throttle position percentage is higher than the corresponding throttle thresholds.
Page 300 (*) Antares SB does not have GPIOs. These signals are maintained for backwards compatibility with scripts from other versions. Instead, Antares SB has 4 inputs and 4 outputs. Signals G00-G03 are the same as IP1-IP4 signals and G04-G07 signals are the same as XP1-XP4 signals. The user is encouraged to use IP and XP signals instead of G signals.
Page 301: Appendix D - Quick Taip Reference
This chapter presents quick examples of the most commonly used TAIP com- mands. Refer to the Unit’s TAIP reference chapter for detailed information on a command. 10.1 Setting the Antares SB To set the unit’s ID to AbcD-1234, send: SIDAbcD-1234 10.2 Setting the APN To set the APN to internet.carrier.com, send:...
Page 302: Reseting The Gprs Connection
10.6. RESETING THE GPRS CONNECTION 10.6 Reseting the GPRS connection To reset the GPRS connection, send: SXAGP1 The until will close the GPRS session and will automatically start it again af- ter approximately 1 minute . 10.7 Conﬁguring a host address/type To set IP address 192.168.0.1 working on TCP port 8000 on Destination Point 00, send: SXADP0001192.168.0.1;8000...
Page 303: Grouping Avl Servers On Das
10.10. GROUPING AVL SERVERS ON DAS 10.10 Grouping AVL servers on DAs To make Destination Address (DA) 4 represent only host address (Destination Point) 00, send: SDA4;P00 To make Destination Address (DA) 4 represent Destination Point 00 and unit’s Serial Port, send: SDA4;P00,P15 To delete DA 4 grouping, send: SDA4U...
Page 304: Creating A Kilometer Counter
10.14. CREATING A KILOMETER COUNTER vehicle’s heading delta changes by more than 45 degrees, send: SED44XV0;J00+ 10.14 Creating a kilometer counter To make a distance counter count kilometers (01000 meters), send: SGC12DC0000101000 To query the kilometer count of this counter, send: QGC12V To make the unit report the kilometer count automatically: Deﬁne an event and add the XACR command to the event’s user-action ﬁeld:...
Page 305: Querying The Internal Back-Up Battery Level
10.19. QUERYING THE INTERNAL BACK-UP BATTERY LEVEL 10.19 Querying the Internal back-up battery level To query the voltage value and charge level of the internal back-up battery, send: QXABS 10.20 Driving the unit to sleep power mode To activate the power saving mode, send: SXAPMA To make the unit go to sleep mode immediately without activating the power saving mode (once the unit wakes up, it won’t go to sleep again automatically):...

DCT Antares SB Manual

1 About the Antares SB

2 Installation

3 Operation

4 Conﬁguration

5 Scenarios and Examples

6 Unit's TAIP Reference

Quick Links

Need help?

Questions and answers

Related Manuals for DCT Antares SB

Summary of Contents for DCT Antares SB