syrus installation and configuration manual v1

7/25/2019 Syrus Installation and Configuration Manual v1

1/53

www.digitalcomtech.com

D i g i t a l C o m m u n i c a t i o n T e c h n o l o g i e s

SyrusInstallation and Configuration ManualV1 - December 2013


2/53

rev1Dec 2013 www.digitalcomtech.com 2

Contents

INTRODUCTION ............................................................................................................................................... 4

COMPATIBILITY .............................................................................................................................................. 4

SPECIFICATIONS ............................................................................................................................................. 5LEDS ................................................................................................................................................................... 7

SYS.................................................................................................................................................................................................. 7

GPS................................................................................................................................................................................................. 7

NET................................................................................................................................................................................................. 7

INPUTS AND OUTPUTS .................................................................................................................................. 8

CARE AND CAUTION ....................................................................................................................................... 9

OPERATING TEMPERATURE...........................................................................................................................................................9

HOW TO REMOVE SIMCARD..........................................................................................................................................................9

HOW TO REMOVE THE INTERNAL BATTERY...............................................................................................................................9

SET UP THE CORRECT PINFOR THE SIMCARD. ........................................................................................................................9

DO NOT LEAVE THESE WIRES UNPROTECTED.........................................................................................................................9

INSTALLATION .............................................................................................................................................. 10

GETTING STARTED ....................................................................................................................................... 12

Support Site Getting Started Section ........................................................................................................................... 12

Setting the unit's ID ............................................................................................................................................................. 12

Setting the APN and PIN.................................................................................................................................................... 12

Creating a Destination Point (DP) ................................................................................................................................ 13

Creating a Destination Address (DA) .......................................................................................................................... 14

Creating a time-period criterion ................................................................................................................................... 14

Tying a signal to an event ................................................................................................................................................. 15

EVENT MACHINE ........................................................................................................................................... 19TRIGGERS.......................................................................................................................................................................................... 19ACTIONS ............................................................................................................................................................................................ 20

EVENTS............................................................................................................................................................................................. 20

SIGNALS............................................................................................................................................................................................. 21Examples ................................................................................................................................................................................... 21

DETAILED COMMAND EXPLANATION ..................................................................................................... 22

UNIT'S ID ......................................................................................................................................................... 22

IMEI AS ID ....................................................................................................................................................... 22

ENABLING THE UNIT ON GSM AND GPRS ............................................................................................... 23

DESTINATIONS (DPS AND DAS) ................................................................................................................ 25

SYRUS COMMANDS ....................................................................................................................................... 27

DA-DESTINATION ADDRESS..................................................................................................................................................... 27

Qualifiers: Q, S, R. .................................................................................................................................................................. 27

Examples:.................................................................................................................................................................................. 27

ED-EVENT DEFINITION .............................................................................................................................................................. 28

Qualifiers: Q, S, R. .................................................................................................................................................................. 28

EV-EVENT MESSAGE................................................................................................................................................................... 29


3/53


Qualifiers: R. ............................................................................................................................................................................ 29

Example: ................................................................................................................................................................................... 29Extended EV Tags formats: .............................................................................................................................................. 30

Example: ................................................................................................................................................................................... 30

GC-COUNTERS,TIMERS,DISTANCERS.................................................................................................................................... 31

Qualifiers: Q, S, R. .................................................................................................................................................................. 31

Examples:.................................................................................................................................................................................. 32GS-SPEED LIMIT ........................................................................................................................................................................... 33

Qualifiers: Q, S, R. .................................................................................................................................................................. 33

Examples:.................................................................................................................................................................................. 33ID-IDENTIFICATION ..................................................................................................................................................................... 34

PV-POSITION-VELOCITY............................................................................................................................................................. 35

Qualifiers: Q, R. ....................................................................................................................................................................... 35

RF-RADIO FREQUENCY MODULE CONFIGURATION............................................................................................................ 36

Qualifiers: Q, S, R. .................................................................................................................................................................. 36

Examples:.................................................................................................................................................................................. 36

RT-RESET MESSAGE .................................................................................................................................................................... 37

Qualifiers: S, R......................................................................................................................................................................... 37

SI-SIMCARD ID ........................................................................................................................................................................... 38

Qualifiers: Q, R. ....................................................................................................................................................................... 38

Examples:.................................................................................................................................................................................. 38

SS-SIGNAL STATUS...................................................................................................................................................................... 39

Qualifiers: Q, S, R. .................................................................................................................................................................. 39

Examples:.................................................................................................................................................................................. 39

ST-STATUS..................................................................................................................................................................................... 40Qualifiers: Q, R. ....................................................................................................................................................................... 40

TD-TIME AND DISTANCE........................................................................................................................................................... 41

Qualifiers: Q, S, R. .................................................................................................................................................................. 41

Examples:.................................................................................................................................................................................. 41

VR-V

ERSIONN

UMBER................................................................................................................................................................ 42Qualifiers: Q, R. ....................................................................................................................................................................... 42

XADP-DESTINATION POINTS................................................................................................................................................... 43Qualifiers: Q, S, R. .................................................................................................................................................................. 43

Examples:.................................................................................................................................................................................. 44

XAEF-EXTENDED-EVMESSAGE FORMATS........................................................................................................................... 45

Qualifiers: Q, S, R. .................................................................................................................................................................. 45

Example: ................................................................................................................................................................................... 45

XAID-IMEIAS ID ........................................................................................................................................................................ 46

Qualifiers: Q, S, R. .................................................................................................................................................................. 46

XAIM-IMEICONSULT ................................................................................................................................................................ 46Qualifiers: Q, R. ....................................................................................................................................................................... 46

XANS-NETWORK STATUS......................................................................................................................................................... 47Qualifiers: Q, R. ....................................................................................................................................................................... 47

ERROR LIST .................................................................................................................................................... 50

SIGNAL LIST .................................................................................................................................................... 51

SCRIPT EXAMPLE .......................................................................................................................................... 52


4/53


Introduction

This manual is intended for Syrus firmware 2 only

The following is an introduction manual for the DCT Syrus GPS tracking device, its mainpurpose is to provide a quick reference for the installation and configuration of the device.

Compatibility

The Syrus firmware 2 is only compatible with the most recent Syrus hardware. Likewise,

the most recent hardware is not backwards compatible with the firmware 1 family.

The benefits of the most recent hardware and the new firmware 2, are the many

accessories and functionalities only available to the firmware 2, such as:

ECU Monitor accessory.

I/Os Expander accessory. Time Windows. Sim Card ID.

GPS Back and Forward Logs. Register status. UDP Network.

Virtual Hour Meter. Commands associated to the ECU Monitor.

New signals:o GPS antenna connection status.o Output short-circuits.

o Idle signal.o And others...
http://sw.dctserver.com/syrdocs/syr_doc_2_1_5_rev36/files/IOsExpander.htmlhttp://sw.dctserver.com/syrdocs/syr_doc_2_1_5_rev36/files/GTTimeWindow.htmlhttp://sw.dctserver.com/syrdocs/syr_doc_2_1_5_rev36/files/SISIMCardID.htmlhttp://sw.dctserver.com/syrdocs/syr_doc_2_1_5_rev36/files/XAKLGPSBackLog.htmlhttp://sw.dctserver.com/syrdocs/syr_doc_2_1_5_rev36/files/XARSRegisterStatus.htmlhttp://sw.dctserver.com/syrdocs/syr_doc_2_1_5_rev36/files/XAUNUDPNetwork.htmlhttp://sw.dctserver.com/syrdocs/syr_doc_2_1_5_rev36/files/XAVOVirtualOdometer.htmlhttp://sw.dctserver.com/syrdocs/syr_doc_2_1_5_rev36/files/XAVOVirtualOdometer.htmlhttp://sw.dctserver.com/syrdocs/syr_doc_2_1_5_rev36/files/XAUNUDPNetwork.htmlhttp://sw.dctserver.com/syrdocs/syr_doc_2_1_5_rev36/files/XARSRegisterStatus.htmlhttp://sw.dctserver.com/syrdocs/syr_doc_2_1_5_rev36/files/XAKLGPSBackLog.htmlhttp://sw.dctserver.com/syrdocs/syr_doc_2_1_5_rev36/files/SISIMCardID.htmlhttp://sw.dctserver.com/syrdocs/syr_doc_2_1_5_rev36/files/GTTimeWindow.htmlhttp://sw.dctserver.com/syrdocs/syr_doc_2_1_5_rev36/files/IOsExpander.html


5/53


Specifications

Power

DC Voltage: 8V - 32 V

Current consumption:

o With Internal battery at null charge (IDLE)

o Long term average: 50 mA @ 12V.

o Long term average while on power saving mode: 6mA @ 12V.

Reverse voltage polarity protection.

High transient voltage (as seen on automotive applications) protection.

Thermal shutdown and current limit protection.

Inputs/Ignition

3 Auxiliary Inputs + 1 Ignition Input. Max 30V.

Impedance: 50 K-ohms (Pull-Up)

1 Analog to Digital Input. 0V - 10V. This input has a protection against voltages greaterthan 10V.

Outputs

2 Open Drain Outputs. Continuous current capacity: 1.8A

Maximum instantaneous current (< 1 sec): 10A

Maximum switching voltage: 30V

Over temperature shutdown at 165 C.

Over current shutdown. The output restarts automatically after the over current state

finishes, this can take up to 5 seconds. TheG07 signal transitions to True when the over

current state is detected.

ESD protection.

Environment

Charging temperature: 0 C to +45 C

Operating temperature: -20 C to +70 C

Storage temperature: -30 C to +85 C

Humidity: up to 95% non-condensing


6/53


GPS Module

GPS Solution MTK MT3329

Frequency L1, 1575.42MHz

Sensitivity Acquisition -148dBm, cold start

Reacquisition -160dBm

Tracking -165dBm

Channels 66

TTFF Hot start: 1 second typical

Warm start: 33 seconds typical

Cold start: 35 seconds typical

Altitude Maximum 18,000m (60,000 feet)

Velocity Maximum 515m/s (1000 knots)

Acceleration Maximum 4G

Update Rate 1Hz (default), maximum 10Hz

DGPS RTCM protocol / SBAS (default) [WAAS, EGNOS, MSAS, GAGAN]

AGPS Support

GPRS Module

Data transmission GPRS Class 12 & Class 10 Max. 86 kbps (DL and UL) Coding schemes.

Dimensions

CS 1-4

LxWxH = 135 mm x79 mm x 31 mm


7/53


LEDs

SYS

RED LED is not a power indicator; it is a system fault or system abnormal status indicator. Under

normal operation this LED is OFF, it will also flash once when the unit has successfully restartedand initialized the Syrus application. To verify if the unit is ON, check the state of the GPS and NET

LEDs, which will always show some kind of activity.

- 2 seconds ON 1 second OFF (SYS Error) general system error, lack of SIM or otherhardware related issue.

- Flashes twice rapidly (Airplane Mode) indicates RF Module is Off, and no communicationvia Syrus commands is available.

- Short 0.5 sec flash every 5 seconds (Power Saving Mode) indicates the unit is sleeping or inPower Saving Mode.

- On/Off repeatedly every 0.5 seconds (Jamming Detected) communication jamming wasdetected (this could be from an external jammer)

GPS

When both the Red and YellowLEDs flash in unison, it indicates a GPS Error .External GPS Antenna in short circuit or internal hardware fault.

YELLOW LED is a GPS Signal indicator.

3 states that indicate GPS Signal Quality (We refer to the adquisicion of GPS Coordinates, latitude andlongitude, as the GPS Fix fixing its position).

- No GPS Fix the LED does not flash at all and is always off.- Low GPS Quality Show flash every 1 second indicates low GPS quality- High GPS Quality Shows 2 rapid flashes every 1 second

NET

Network Error: indicates a GSM Registration Error. Possible causes:- No SIM Card inserted, PIN error, or network rejects the SIM card registration

4 States:

On 0.5 seconds / Off 0.5 seconds Not registered to either GSM or GPRSOn 0.5 seconds / Off 3 seconds Registered to GSM network, but not GPRS networkRapid flash twice attached to the GPRS Network

Solid On Voice call in progress


8/53


Inputs and Outputs


9/53


Care and Caution

Operating Temperature

Due to the limitations on the operation of the Lithium polymer battery, the temperature while charging the battery

must be 0C to 45C, and the regular operating temperature must be -20C to 70C. For more information about theLithium polymer batteries, visit:

http://en.wikipedia.org/wiki/Lithium-ion_polymer_batteryorhttp://www.batteryuniversity.com/parttwo-34.htm

How to remove SIM Card

Always send an >SRT< command before removing the SIM card, due to the risk of possible damage to the SIMcard. Follow these steps in order to prevent these issues:

- Send a Reset (>SRT< command) via Serial port.- Remove SIM card after sending the >SRT< command. That means you have around 10 seconds to

remove the SIM card.

How to remove the internal battery

Always send a >SRT< command before removing the battery if the external power supply is not connected, due to

the risk of possible data loss or data corruption in the device memory. Follow these steps in order to prevent these

issues:- Send a Reset (>SRT< command) via Serial port.- Remove the battery after sending the >SRT< command. That means you have around 10 seconds to

remove the battery.

If the external power supply is connected, the battery can be replaced without sending the >SRT< command.

Set up the correct PIN for the SIM card.

The SIM card may be blocked if the PIN parameter is configured using the>SRFI


10/53


Installation

The SyrusTMcan be installed in any location of any type of vehicle as long as some

environmental conditions are met:

o No exposure to water.

o No direct exposure to sun light.

o Away from excessive heat sources like the motor or the exhaust's path.

o Away from excessive cold sources like a truck's refrigerator or AC system.

o Not attached to a highly vibrating structure.

o The Syrus has an internal GSM antenna that will assure GPRS communicationunder normal vehicular conditions. The unit must not be installed inside a metal

structure that could act as a Faraday cage, which could lower the signal strength.

o The Syrus has an internal GPS antenna, and a connector for an optional external

GPS antenna. When using the internal antenna, the units must be located so that

it has minimal metal obstructions to the sky view and with the upper part facingup. It is recommended to use the external GPS antenna in most cases.

The unit's location/position can be such that it remains hidden. The LEDs indicators do

not have to be visible but it is recommended some access to them for

failure/diagnostics situations. The same recommendation holds for physical access to

the unit's serial port.

Power Supply

The unit's power cables should be directly connected to the vehicle's battery (12V or24V). The unit supports an operating voltage range from 8V to 32V.When the unit is not being used in a vehicle (e.g. lab testing) it must be powered by a

12V DC adapter that supplies a minimum current of 800mA.

Warning:The internal lithium polymerbattery has an integrated automatic cut offcircuit to protect against over-charge, over-current and over-discharge. After long

disconnection periods, the battery may activate its over discharge protection circuit.The unit is shipped with an unplugged battery connector to help prevent this state.

Plug this connector in before connecting the main power and wait for activityindication on the green LED. It is not recommended to unplug the battery, except for

seldom-long storage periods. Refer toCare & Caution Sectionto see how to removethe Battery or the SIM card.

Even though it is possible for the unit to work with no internal battery, it is

recommended to always use the battery; this is to prevent any data loss or memory

corruption that can be caused due to momentary external power loss.


11/53


Vehicles with a main power switch

When the vehicle has a main power switch to cut/restore the battery voltage, somerecommendations have to be followed:

o If the switch disconnects the positive voltage of the vehicle's battery,the Syrus can be connected before or after the switch. When connected before it

will keep on receiving the vehicle's power whenever the switch is off. If it is

connected after the switch, the unit will run with its optional back up battery

whenever the switch is turned off.

See the following figures for a better understanding of connecting the unit when thevehicle uses a main power switch:


12/53


Getting Started

Support Site Getting Started Section

On the DCT support site (support.digitalcomtech.com) uponregisteringyou have the

option to visit thegetting started page. We recommend you go here first and refer to the

following for examples on how to further configure the device and get startedprogramming. Also we recommend usingSyrus Desk softwareand test all these commands

so you can see first-hand how the device responds.

Setting the unit's ID

The default Syrus behavior is to use the unit's IMEI as ID. It is recommended to use this

setting as the IMEI is unique for each unit. However it is possible to use a user defined ID in

order for the unit to be identified on the AVL server. The default value for the unit's ID is

0000. This field may be any string of 10 characters maximum.

For this example lets call our unit EXAMPLE:>SIDEXAMPLESXAID0SXAID1RXANS1,internet.carrier-name.com,1234,,;1,1,null,1,22,1,1,18.18.9.8,1;socket://avl.server.com:2145,3, -1,,-1,,,,0,0,0,,,,0,,,,25\;0,0,0,0,,,17;28,3,101,0,0,,5,42,socket://avl.server.com:2145;SED35SV0;F00+;ACT=SGC05TC;ACT=SSSU041;ACT=SGC07U<

Checking the host software/server

At this point and as long as the unit remains GPRS attached, anEVmessage should be

arriving to the AVL server every 5 minutes. The software must be able to interprettheEVmessages generated by the unit. If you run into troubles checking your AVL

application you can always shut it down an use some popular free TCP listener applications

that will show you the RAW data received, and confirm that the reports from Syrus arebeing received properly by the server. Another useful tool is a network sniffer that allows

you to analyze the traffic on a given TCP/UDP connection while the the AVL server isrunning.

Some examples of such tools can be found at:

TCP client and listener: TCP Test ToolTMfromwww.simplecomtools.comUDP client and listener: UDP Test ToolTMfromwww.simplecomtools.comNetwork sniffer: WiresharkTMfromhttp://www.wireshark.org/
http://www.simplecomtools.com/ProductCart/pc/viewPrd.asp?idproduct=7&idcategory=5http://www.simplecomtools.com/ProductCart/pc/viewPrd.asp?idproduct=7&idcategory=5http://www.simplecomtools.com/ProductCart/pc/viewPrd.asp?idproduct=7&idcategory=5http://www.simplecomtools.com/ProductCart/pc/viewPrd.asp?idproduct=6&idcategory=5http://www.simplecomtools.com/ProductCart/pc/viewPrd.asp?idproduct=6&idcategory=5http://www.simplecomtools.com/ProductCart/pc/viewPrd.asp?idproduct=6&idcategory=5http://www.wireshark.org/download.htmlhttp://www.wireshark.org/download.htmlhttp://www.wireshark.org/download.htmlhttp://www.wireshark.org/download.htmlhttp://www.simplecomtools.com/ProductCart/pc/viewPrd.asp?idproduct=6&idcategory=5http://www.simplecomtools.com/ProductCart/pc/viewPrd.asp?idproduct=7&idcategory=5


18/53


Script

The example so far can be summarized with the following script:#Syrus SB script#Getting Started example

#Delete any previous configuration>SRT;CONFIGSXADP**USRFI1234SRFAinternet.carrier-name.com<

#The remote AVL server address and port>SXADP0000avl.server.com;2145<

#A Destination Address holding the server destination>SDA4;P00STD80300SED37NV4;TD8+SED05NV4;IP3+


19/53


Event Machine

The unit's reporting is controlled by an Event Machine which constantly evaluates userdefined events. These events allow the user to create a reporting schema andfunctionality controlled by triggers and actions. Events can be consulted or configured atany time with the ED message throughout the Command Console, enabling the user toalter the Event Machine parameters at any time locally or over the air.

Up to 100 events may be defined on the unit. These events are evaluated on asequential order based on the event's ID. This means that lower IDs are evaluated first.Having this in mind an event's ID may be relevant if its trigger depends on other events'signals and/or on other events' user-defined actions.

This section examines the events components: triggers and actions. Then it gives anoverview of the events definition. Finally explains one of the most important componentsof the events triggers: Signals.

Triggers

A trigger is determined by the logical combination of several situations (also calledsignals). A logical combination is basically an equation (specifically: a boolean equation)that combines signals (situations) with the logical operators AND, OR and NOT. InSyrusTM, these boolean equations use the post fixed notation, meaning that theoperator is at the end of the signals to be evaluated. When more than three signals arebeing evaluated, a logical operator must be inserted every two signals in the equation.These are some examples of the post fixed notation syntax:

A or BAB|A and BAB&

A and B and CAB&C&

To determine how the signals will trigger the report a plus (+) or minus (-) sign is addedat the end of the equation. A plus sign (+) indicates that the report is generated when asignal or an equation becomes "true". Consequently, a minus (-) sign indicates that thereport 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 becomesfalse one of the signals must be negated using the boolean operator not. Either the plusor minus sign can be used, but for it is easier to understand the equation when the plussign is used.

When A becomes "true" and B becomes "false" A!B&+


20/53


Actions

Once you have defined a trigger (and/or a set of triggers) the next step for configuringthe Syrus TM event machine, is to tell the unit what to do when a trigger goes off. Thereare two types of actions the unit may take when a trigger goes off. These are the report

action and the user-defined action.

When the event machine detects that a trigger goes off it uses the configuration of thereport action to generate a report. A report action configuration includes routing optionsand a type of report.

The routing options tell the unit where to report the occurrence of the specific event. Thereport destinations may be IP addresses (or host names), cellular phone numbers or theunit's serial port. It could also be a silent report which is not reported to any destination.It is possible to send the same report to several destination at the same time by defininga group of destinations using the DA command.

The type of report used by the unit is called "EV Event report". The informationcontained in this type of report is described in the EV command. The EV report caninclude extra information tags, called "Extended EV Tags". This tags are included in thereport by defining an event using the A, B or C Message IDs. The information that eachtag contains can be defined using the XAEF command.

A user-defined action is defined by a user-specified command (or set of commands)that are appended at the end of a regular event definition using the "ACT=" or "XCT="string. This enables the user to predefine commands that the unit will only processwhenever the trigger of a defined event goes off.

Events

Triggers and actions are bound together on a single configuration message calledevent. An event is defined or consulted with the ED command. A single event holds atrigger, a report action and optionally a user action. The following figure gives a globaldescription of the ED command.

The SyrusTM has 100 events available for the user to configure. They may be definedall at once in a configuration script or they me be individually defined at any moment asthe user adds/removes functionality. Please refer to the ED command for moreinformation on each of the message's fields.


21/53


Signals

As described in the previous section, the event machine takes actions like reporting orswitching outputs whenever a user defined trigger goes off. This trigger is configured bythe user with the logical combination of situations.

Situations make reference to a vehicle state which is in fact represented by signals andtheir state. SyrusTM signals are of boolean nature, meaning that they can only take oneof two possible values: true or false.

Signals and the logical operators AND, OR, NOT are used to create logical equations toform event triggers.

By using the SS command a signal's state can be consulted, and depending on thesignal's type, this command can be used also to change the signal's state. Signals'names always have three characters. Please refer to the Signal List section, for a list of

valid signals and their meanings.

Examples

Some examples about the use of the event machine are presented next.

Configuring two events on the Event Machine to generate an ignition report:

The ignition ON event may be defined as:

>SED18NV4;F00+SED19NV4;F00-SED05NV0;S00J00&+


22/53


Detailed ommand Explanation

Unit's ID

Syrus Commands:ID,XAID

This parameter is only meaningful to the AVL software which is going to receive reportmessages from the unit. It is not necessary for the unit to work but it may necessary for

making a test with an AVL software.

The unit's default behaviour is to use its IMEI number as ID, but it is possible to use a

custom ID, which is set using theID command, and then enable using the custom ID withtheXAID command.

The unit's ID is a 10 characters maximum string that may contain any character except: ';',''. The initial value is 0000. The ID is used every time the unit sends a report

message (EV) by adding the postfix ";ID=0000" to the message. This postfix gives theAVL software information on who is sending the report.

To set the unit's Id as UNIT-0015, use:

>SIDUNIT-0015SRTSXAID1SXAID0SRT


23/53


Enabling the unit on GSM and GPRS

Syrus Commands:RF,XANS

The GSM registration as well as the GPRS attachment (getting a valid IP address from thecellular operator) is automatically done by the unit all the time. This means that wheneverthere is GSM and GPRS network availability and the unit is correctly configured it is

going to be GPRS attached (The green NET LED will be blinking quickly twice). TheSIM card's PIN and the cellular operator APN (Access Point Name) are required by the

unit to be GPRS attached.

SIM Card's PIN for GSM registration

This parameter is optional because it depends on how the SIM card is configured. Most

cellular operators distribute no-pin SIM cards so you don't have to worry about this

parameter or you can explicitly set it to "empty" if you are unsure of a previousconfiguration. But if your SIM card requires a PIN this parameters has to be set or else theunit will fail to register on GSM. The configuration message for the SIM card's PIN is

theRF message. This message is used as follows:

To set the PIN number 1234 send to the unit:

>SRFI1234SRFISRTSRFAinternet.carrier-name.com<

To leave the APN parameter empty:

>SRFA


25/53


Once the GPRS session is up the unit is ready to communicate with IP networks (i.e. withIP addresses). For this, the cellular carrier assigns the unit an IP address that is usually but

not necessarily dynamic, meaning that for every session the unit starts its value changes.The actual IP address assigned by the operator through the chosen APN can be consulted

with theXANS command.

Destinations (DPs and DAs)

Syrus Commands:XADP,DA

A destination makes reference to the device or user that is receiving and/or sending

messages from/to the Syrus. The possible destination for the unit are:

o

6 IP hosts. 4 of these hosts are TCP only (00-03) and 2 hosts are UDP only (04-05).o 5 telephone numbers via SMS.o The unit's serial port

Each destination is called aDestination Point(or simply a DP). Destination Points maybe grouped to form aDestination Address(or simply a DA). As you can deduce from the

list, there are 11 DPs. The unit offers 10 possible combinations of DPs, leading to 10DAs. In the majority of cases DAs are used to tell the unit where to send its report but in

some cases a command may require a DP on its configuration.

Destination Points (DPs)

As mentioned there are 11 DPs, these are divided in the following way:

o The first 6 DPs (00 to 05) are IP hosts. These are defined with an IP address or aserver name and a TCP or UDP port number. The Syrusis 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

specified here. Keep in mind that DPs 00 to 03 are TCP only and the DP 04 and

05 are UDP only.

o The next 5 (DPs 10 to 14) make reference to phone numbers. These numbers are

used to send SMSs or make voice calls. They are also used as authorizationnumbers for replying to receive SMSs commands and/or answering incoming

voice calls. Defining if a report should be sent as a Syrus command or using a

custom user message is also done here.

o The last DP (15) makes reference to the serial port.

For more information please refer to theXADP command.


26/53


Destination Addresses (DAs)

A Destination Address is a user-defined group ofDestination Points. This enables some

reporting commands to route their report to several destinations at the same time with asingle definition. Up to 10 (0 to 9) DAs may be defined. Refer to the DA message for

more information. This command enables the user to group a list of DPs.

The main use for DAs is on the routing options of an event definition. TheEvent

Machinesection gives more information about this. What should be clear on this, is that areport generated by an event is always sent to a DA, not to a single DP. For this reason

DAs make part of the minimum configuration required by the unit. Some examples ofDAs' definitions are:

Defining DA 5 as the group containing DPs 02, 04, 10 and 15:

>SDA5;P02,P04,P10,P15


27/53


Syrus commands

DA - Destination Address

Qualifiers: Q, S, R.

A Destination Address is an association of Destination Points. These allows an event

defined 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). A Destination Address is not the

actual IP address or SMS telephone of the receivers. The message has the following

format:

A;PBB[,PBB,...,PBB:PBB,...]

o Ais the Destination Address' index. Its range goes from 0 to 9. Remember that a

Destination Address is a group or an association of Destination Points. ADestination Point (seeXADP message) is the actual IP address or telephone of a

destination.

o Bholds a Destination Point's index. You can select multiple Destination Points by

separating them with a ','.

Examples:

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


28/53


ED - Event Definition


This message is used to define events. These events define the Event Machine

configuration for the SyrusTM. An event is created by defining a boolean combination

of signals as a trigger, a routing indication for a generated event message and a

possible Configuration Commandto be executed when the event occurs. The message

has the following format:

AABCD;EEE{[EEE][F]}G[[;ACT=HH...][;ACT=HH...]...]

o AA: Index. Specifies one of the event definitions associated with an event

definition signal EAA. Ranging from 00 to 99 (or '**').

o B: Event Handling. Message Routing. The valid values for this field are:

N: Normal. Route the Event Message to the specified Destination Address

(DA). X: Serial Port. Route the Event Message to the unit's serial port only.

S: Signal only. Do not generate an Event Message. The event's signal still

follows the event's state.

U: Undefine. Delete the event's definition.

o C: Message ID. Generate event message as:

V:EV message.

A: extended-EV message A.

B: extended-EV message B.

C: extended-EV message C.

o D: Destination address of the Event Message. The value of this field is the index

of the desired Destination Address (DA) defined with the DA message.

o EEE: Signal(s) used to trigger the event. Consult the Signals List for a list of valid

signals.

o F: Logical operation used to combine signals:

&: AND

|: OR

!: NOT

o G: Event sense. Edge of signals' combination used to trigger the event:

+: Rising edge.

-: Falling edge.

o H: Event Action. A valid Configuration Commandwithout the opening (>) and

closing (


29/53


EV - Event Message

Qualifiers: R.

This message is generated when an event is triggered and reported. The message has the

following format:

AABBBBCDDDDDEEEFFFFFGGGGHHHHHIIIJJJKL[EXTENDED-

EV TAGS]

o AA: Event index. Range 0-99.o BBBB: Number of weeks since 00:00 AM January 6, 1980.o C: Day of week. From 0 to 6 where 0 is Sunday.

o DDDDD: Time of the generated report. Seconds since 00:00 of the current date.o EEEFFFFF: WGS-84 Latitude. It does include the sign: Positive for

north. EEErepresents a value in degrees and FFFFFparts of a degree in

decimals.o GGGGHHHHH: WGS-84 Longitude. It does include the sign: Positive for

east. GGGGrepresents a value in degrees and HHHHHparts of a degree in

decimals.o III: Vehicle velocity in mph.o JJJ: Vehicle heading, in degrees from North increasing eastwardly.o K: Position fix mode:

0: 2D GPS 1: 3D GPS 2: 2D DGPS

3: 3D DGPS

9: Unknowno L: Age of data used for the report:

0: Not available 1: Older than 10 seconds 2: Fresh, less than 10 seconds 9: GPS Failure

o [EXTENDED-EV TAGS]: Extended information tags. See theXAEF message for

information on how to set the EV tags, and consult the list below for more

information on the format used by each tag to present the information.

Example:

An Event Message could be like this:

>REV481599462982+2578391-0802945201228512< Which indicates that the report was generated by theEvent Definition48, on September

2nd, 2010 (1599 4), at 17:29:42 GMT (62982), with thecoordinates +25.78391 latitude and-080.29452 longitude, with a speedof 012 mph, and a heading of285 degrees, with a 3D GPS fix mode and the age datawas recent.


30/53


Extended EV Tags formats:

o ;AC=AAA... AAA...: Instant acceleration measured in Miles per hour per seconds

o ;AL=AAA... AAA...: Altitude is A meters Above Mean Sea Level (AMSL). This value will

be -9999 when no valid GPS data is available.o ;BL=AAA...

AAA...: Voltage level of the battery in milivolts.o ;CF=AAA...,BBB...,CCC...

AAA...: Local Area Code (LAC). BBB...: Cell ID (CID) CCC...: RSSI level.

o ;CVAA=BBB... AA: Index of the counter. BBB...: Value of the counter.

o ;DOP=AAA...,BBB...,CCC...

AAA...:PDOPvalue. Must be divided by 100 to obtain the real value*. BBB...:HDOPvalue. Must be divided by 100 to obtain the real value*. CCC...:VDOPvalue. Must be divided by 100 to obtain the real value*.

o ;IO=ABC

A:Bitwise representation ofA: bit0: Ignition (1=ACTIVE, 0=INACTIVE) bit1: Main Power Source (1=EXT-PWR, 0=BACKUP-BATTERY)

B:Bitwise representation of B(outputs): bit0: Output 1 (1=ACTIVE, 0=INACTIVE) bit1: Output 2

C:Bitwise representation of C(inputs):

bit0: Input 1 (1=ACTIVE, 0=INACTIVE) bit1: Input 2 bit2: Input 3

o ;IP=AAABBBCCCDDD AAA: First number of the IP number. BBB: Second number of the IP number. CCC: Third number of the IP number. DDD: Fourth number of the IP number.

o ;SV=A... A...:Number of satellites on view.

o ;VO=AAA... AAA...: Current value of the virtual odometer.

Example:

>REV401770475916+1672118-0930303000000032;VO=18787159;SV=9;ID=356612022871133SGC03TC00300SGC07TR0002700060SGS0010550SED33NV0;S00+


34/53


ID - Identification


This message is used to set/query unit's ID. When changing the ID it is necessary

to reset the unit using theRT command in order to reestablish the currentconnections to any Destination Pointusing the new ID. The message has the

following format:

A[AAA...]

o A[AAA...]: Identification code assigned to the vehicle. This parameter is alpha-

numeric and up to 10 characters long. The only forbidden characters are ">", "


35/53


PV - Position-velocity

Qualifiers: 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

o AAAAA: Time of day. Time of the generated report. This number represent the

seconds elapsed since 00:00 of the current day.

o BBBCCCCC: WGS-84 Latitude. It does include the sign: Positive for

north. BBBrepresents a value in degrees and CCCCCparts of a degree in

decimals.

o DDDDEEEEE:WGS-84 Longitude. It does include the sign: Positive foreast. DDDDrepresents a value in degrees and EEEEEparts of a degree in

decimals.o FFF: Vehicle velocity.

o GGG: Vehicle heading, in degrees from North increasing eastwardly.

o H: Position fix mode:

0: 2D GPS

1: 3D GPS

2: 2D DGPS

3: 3D DGPS

9: Unknown

o I: Age of data used for the report:

0: Not available

1: Old, 10 seconds

2: Fresh, RPV69311+2578378-0802936300125532<

Indicating that the report was generated at 19:15:11 GMT with

coordinates +2578378 latitude and-08029363longitude, with a speed

of 001mph and a heading of255degress, with 3D DGPS fix mode and the age of thedata was recent.


36/53


RF - Radio Frequency Module Configuration


This message is used to configure Cellular Network parameters. Any RF parameter can beleft empty by issuing the command without the B string. The message has the following

format

A[BBB...]

A: RF parameter to be configured. The valid values for this field are:

A: GPRS APN (Access Point Name) (40 chars. max.).

I: SIM Card PIN.

L: GPRS Login (40 chars. max.).

P: GPRS Password (40 chars. max.)

[BBB...]: String with the parameter described by A. It cannot contain the "


37/53


RT - Reset message

Qualifiers: S, R.

When used with qualifiers it serves multiple initializations purposes. The valid

options are:

o Without a Qualifier (i.e: >SRT


38/53


SI - SIM Card ID

Qualifiers: Q, R.

This message allows to consult the SIM Card ID of the SIM card currently installed on

the Syrus.

Examples:

To consult the SIM card ID, send:

>QSIRSI8957123310512805597RER13;QSI


39/53


SS - Signal Status


This message allows for the inspection of signals' state and the setting of outputs and

other user controllable signals. Please refer to theSignal Listsection, for a list of

valid signals. The message has the following format:

AAA[B]

o AAA: Index. 3 character identifier if the signal. See theSignal Listsection for a

list of valid signals.

o B: Status of the specified signal. The only valid values for this field are 0 or 1.

Examples:

To activate output 2:>SSSXP21SSSXP20QSSIP2RSSIP20RSSIP21SSSU080SSSU081QSSF00RSSF000RSSF001


40/53


ST - Status

Qualifiers: Q, R.

This message provides information about the unit's GPS receiver. The message has the

following format when using no modifier (>QST


41/53


TD - Time and Distance


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 criterion

allows creating a counter that does not follow a time or distance criteria

independently from each other, instead, combines these two variables to generate an

intelligent trigger to be used for a more efficient vehicle tracking. The message has

the following format:

ABBBB[CCCCDDDDEEEE]

o A: Index. Range 0-9. Specifies one of the Time and Distance configurations

associated with a Time and Distance signal TDA.

o BBBB: Minimum amount of time elapsing between reports. To enable just time

reporting, this is the only parameter to set, and the others should be set to 0.Setting this value to 0 disables the report.

o CCCC: This parameter is ignored and can have any value.

o DDDD: Distance the unit must travel between reports. Each unit represents 100

meters.

o EEEE: Maximum amount of time elapsing between signals' activation. This

parameter is only relevant when distance reporting is desired. If set to 0, there is

no limit to the amount of time between reports.

Examples:

In this example we will create a tracking event that sends event code 49 based on a

T&D criterion. A 8km (5miles) report is desired. The criterion must be so that no

more than one hour passes between successive reports, and the minimum time

between successive reports must be 2 minutes.

In this example the T&D index 6 is used for no particular reason. The requirements

call for the following T&D configuration:

o Minimum time between reports: 120 seconds (2mins).

o Distance Threshold: 80 x 100m (8km).

o Maximum time between reports: 3600 seconds (1hr).

This configuration is achieved by sending:

>STD60120000000803600SED49NV0;TD6+


42/53


The T&D could also be configured on a time-only basis by defining the Minimum

Time parameter and setting the others to zero. To define a time only criteria of 15minutes (900 seconds):

>STD60900000000000000STD60900


43/53


XADP - Destination Points


This message configures both IP-type (Internet Protocol) and Telephone

destinations. The IP-type destinations support both TCP and UDP.

The Destination Points index from 00 to 03 are reserved for TCP destinations only.

The TCP destinations support both IP number and URL addresses.

The Destination Pointwith index 04 and 05 are reserved for UDP destinations only.Please note that the UDP destinations also support both IP number and URL

addresses for reporting, but to send Configuration Commands over the air from aUDP connection, it must use an IP number address on the destination configuration

of the unit. This restriction is temporary and will be changed in a future firmware

version.

Important:

The UDP DP 05 can only be set if UDP DP 04 is already defined. The port defined forDP 05 must always be different to the port defined for DP 04. DP 04 can only be

deleted once DP 05 has been deleted first. After configured the DP 05 it is necessary

to restart the Syrus using the>SRT


44/53


For Telephone destination, i.e. Destination Points10 to 14 use the following format:

AABCD[DDD...]

o AA: Index for Telephone destinations. Range 10-14.

o B: DP type/Action:

U: Delete the Destination Point

0: Report messages are sent as Configuration Commandsresponses to this

destination.

1: User-defined text messages are sent instead of the

regular Configuration Commandresponse.

o C: Access permission for this Telephone:

0: Full Access

o D[DDD...]: Telephone number. Maximum 50 characters.

Examples:

To set a TCP Destination Point:

>SAXDP0000avl.server.com;57816<

or

>SXADP0100192.168.0.1;57816<

To set a UDP Destination Point:

>SXADP0403avl.udp.server.com;5454<

To set a telephone type Destination Point:

>SXADP10105551234567


45/53


XAEF - Extended-EV message Formats


This message allows the creation and configuration of up to three sets of information

tags to be used by an event having the Message ID qualifier set to A, B or C. The

message has the following format:

A[BBB...]

o A: Identifier of the extended-EV format being set or consulted. The valid

identifiers are: A, B or C.

o [BBB...]: Information tag. Enter each tag separated by a ";" character. The valid

tags are:

AC: Instant acceleration measured in Miles per hour per seconds.

AL: Altitude in meters above mean sea level (AMSL).

BL: Battery voltage level. Milivolts. CF: Cell information.

CVxx: Counter xx value.

DOP: GPS dilution of precision.

IO: Inputs and Outputs state.

IP: IP Address.

SV: Satellites in view.

VO: Virtual Odometer value. Meters.

For more information on each tag, refer to the Extended-EV Tags formats list on

theEvent Message(EV)section.

Example:

To set event 49 to send an extended-EV message that includes the cell information,

the number of GPS satellites in view and the state of counter 05 whenever the

vehicle's speed goes above 55 mph:

Define the event. Set it to use extended-EV formatA

>SED49NA0;S00+SXAEFA;CF;SV;CV05SXAEFAU


46/53


XAID - IMEI as ID


This message tells the unit whether to use or not its IMEI as ID. When changing this

parameter, it is necessary to reset the unit using theRT command in order to

reestablish the current connections to any Destination Pointusing the ID

setting.The default is to use the IMEI. The message has the following format:

A

o A: Flag:

1: Set the unit's ID with the IMEI. This is the default value.

0: Set the unit's ID to the value set by the user with the ID message.

Please refer to theID andXAIM messages, which are closely related to this message.

XAIM - IMEI Consult

Qualifiers: Q, R.

This message is used to consult the unit's IMEI (International Mobile Equipment

Identity) The message has the following format:

AAAAAAAAAAAAAAB

o AAAAAAAAAAAAAA: Unit's IMEI.o B: IMEI's Checksum.

Please refer to theID and XAIDmessages, which are closely related to this message.


47/53


XANS - Network Status

Qualifiers: 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 response message information is

presented in groups separated by a ";" character and each group separates its data

with a "," character.

A XANS messages interpreter is available, which will show the XANS information in

a easy to read format.

Some information may not be available all the time, in this case the field

corresponding to that data will be empty. It is possible to see more fields than those

explained here on the right side of each group of the message, however that

information can be ignored. The relevant information provided by this message is:

First group:o Air Interface status.

0= Air Interface is down. 1= Air Interface is up.

o APNo SIM PINo GPRS Logino GPRS Password

Second Group:o SIM insert state

0= SIM not inserted 1= SIM inserted 2= SIM hardware off

o SIM state 1= SIM ready 2= SIM hardware off 3= SIM inserted 4= SIM removed 5= PIN error 6= waiting PIN 7= SIM lock 8= SIM error

o SIM lock reason. This field's value only matters if the SIM state is 7 SIM PIN = waiting for SIM PIN.

SIM PUK = waiting for SIM PUK if PIN was disabled after three failed attempts to enterPIN.

o GSM register state 0= Not registered 1= Registered 2= Not registered, searching. 3= Rejected 4= Error 5= Registered, Roaming.


48/53


o GSM RSSI 0 = -113 dBm or less 1= -111 dBm 2 to 30 = -109 to -53 dBm 31 = -51 dBm or greater 99 = not known or not detectable

o GPRS attached state 0= Not attached* 1= Attached

o GPRS register state 0= Not registered* 1= Registered 2= Not registered, searching. 3= Rejected 4= Error 5= Registered, Roaming.

o Local IP addresso GPRS bearer state

0 = Bearer is down

1 = Bearer is upo Jamming state:

-2 = Normal state 0-60 = Jamming detection in progress -3, -1 = Jamming Detected

* This state can be reported when no TCP Destination Point is set. Consult the XADP message for moreinformation.

Third Group:

This group holds the information about each Destination Point set. Each destination

point is separated by a "\" character. If no destination point is set this group will be

empty. The Destination Points are listed in the chronological order they were

created. They are not listed by the index used by the XADP message.

The address of the IP destination point.o Socket connection state

0= Not connected 1= Connecting 2= Closing 3= Connected 4= Connected, limited. 5= Closing, hold.

o Local porto

Remote IP addresso Remote porto Socket up timeo Socket down timeo Socket down log timer


49/53


An example of the response for this message could be:

>RXANS1,intnet.cxn,,,;1,1,null,5,31,1,5,10.1.17.207,1;socket://visionairegps.com:8040,3,1024,66.228.127.212,804

0,3,,\;,,,;3,1,1,0,4; and/or


51/53


Signal List

A00 - A03: Destination Points' state. True when the IP address/port defined on the

corresponding Destination Point's index is accepting a TCP connection (i.e. the TCP

socket is open).

B00 - B04: Battery levels. True when the unit's back-up battery level is above the valuedefined.

C00 - C19: Counters, Timers, Distancers. True when the corresponding counter reachesits defined threshold value. See theGC message.

E00 - E99: Event triggers. True when the corresponding event trigger is True. See

theEDmessage.

F00: Ignition. True when the ignition input of the unit is on.

F01: GPS Fix. True when doing GPS fixes.

F02: GSM/GPRS Roaming. True when the unit is Roaming on GSM/GPRS.

F03: GSM-Registered. True when the unit is registered in the GSM network.

F04: GPS Antenna Feed-line fault. Indicates a short on the GPS antenna cable. F05: GPRS Bearer. True when the GPRS bearer is up.

F08: SIM State. True when SIM is inserted. This signal has a persistence time check of

10 seconds.

F12: Motion. True when the movement is detected.

F13: Power. True when the unit's main power supply is on.

F15: Low battery. True when the internal battery charge is below 20%.

F16: Aggressive driving. True when aggressive driving is detected.

F17: Collision. when a collision is detected.

G05: Idle signal. True when Syrus determines that the vehicle is in idle state. This

happens when the vehicle's engine is turned on but the vehicle is not moving.

G06: GPS antenna connection status signal. True when the GPS antenna is connected. IP1 - IP3: Inputs. True when the corresponding input is activated.

J00 - J04: Heading Deltas. True when the vehicle's heading change is greater than thecorresponding heading change threshold. The signal is immediately reset after

evaluation to achieve a turn-by-turn report.

S00 - S09: Speed thresholds. True when the vehicle's speed is faster than the

corresponding speed threshold. See theGSmessage.

TD0 - TD9: True when the associated Time and Distance counter has a Time and

Distance condition true. The signal is immediately reset after being evaluated to enable

the counter for further triggers. See the TDmessage.

U00 - U15: User flags. These signals may be changed by the user at any time with

theSS message. XP1 - XP2: Outputs. True when the corresponding output is on. See theSSmessage.


52/53


Script example

#- Syrus 2 Script - Standard Configuration

#- v1 - last edit DEC 2013

#- Extended formats

>SXAEFA;VOSXAGH001045SED00NA0;J00C02|C03|F00&+;XCT=SGC03DR00800;XCT=SGC02TR00120SGS0110060SED69SV0;S01!F00&+;XCT=SGC05TC0006000010SED68SV0;S01F00!|+;XCT=SGC05USED01NV0;C05+;XCT=SGC05USED02NV0;F00+;XCT=SGC02TR00120;XCT=SGC03DR00800;XCT=SGC07DR00500;XCT=S

GC08TC00300;XCT=SGC11USED03NV0;F00-

;XCT=SGC02U;XCT=SGC03U;XCT=SGC07U;XCT=SGC08U;XCT=SGC01TR0006000120SGS0010700SED67SV0;S00+;XCT=SGC04TC00010SED66SV0;S00-;XCT=SGC04USED04NA0;C04+;XCT=SGC04USED65SV0;C07+;XCT=SGC08TC00300


53/53

#Event 05 - Slow Traffic

>SED05NA0;C08+SED06NV0;F13-SED07NV0;F13+SED08NV0;C01+SED09NV0;IP1+SED10NV0;IP2+SED11NV0;IP2-SED12NV0;IP3+SED13NV0;IP3-SED14NV0;XP2+SED15NV0;XP2-SED16NV0;F15+SED17NV0;F04+

syrus installation and configuration manual v1

Documents