The Syrus 3G comes in two flavors, one of the flavors is compatible with 850/1900 MHz frequency bands & the other flavor is compatible with 900/1800 MHz.
Make sure you get the right flavor when ordering your units.
Please visit the following to make sure your country’s frequency band is supported:
You can download the wiring diagram for all devices on the following page:
Syrus Wiring Diagrams
If you intend on extending the 1-wire cable (Red/white on harness) the length of this cable should not exceed 20 meters length in total (65 feet).
DCT University is an online e-learning course that is open to anyone that wants to learn more about GPS tracking technologies. The course is used to train technicians in the advanced use of tracking technologies using the Syrus GPS and the various peripherals DCT has to offer.
The actual Syrus manual is found under the Syrus menu option – > “Syrus Manual” or by following this link.
Please note that access to this manual requires a different login than the access to the support site. In order to have access to the actual Syrus manual please consult with your commercial representative.
For Syrus 1 FW Updrade please look at the following video:
A complete comparison of these two transport protocols can be read here.
If data consumption is not a problem we recommend using TCP protocol.
How does this relate to the Syrus GPS?
Syrus GPS can support up to 4 TCP and 2 UDP servers reporting simultaneously.
Something to keep in mind when using TCP:
It is important to note that although TCP guarantees the delivery of the data to the AVL platform, the data successfully reaching the AVL server depends on GPRS network conditions, in the event of little to no cell coverage the Syrus can lose data even if it’s using TCP protocol.
For example, if your AVL platform’s listener is still accepting the Syrus event messages, but the database is temporarily unavailable, the data is confirmed on a TCP level but not on the AVL platform (database) level, thus you can lose packets. To fix these issues we can use an ACK (Acknowledge) mechanism to ensure the data reaches the server.
For more information download our Syrus Listener Recommendation guide.
Something to keep in mind when using UDP:
Communication between the server and the Syrus is not as ‘immediate’ as with TCP because UDP is connectionless, in other words you have to wait for the device to report to the server before the server can send a command to the Syrus, to keep this time low consider using a short Keep Alive
Only when you use UDP + ACK make sure the definition of the Destination Point uses the IP address and not the URL.
The ID of the device as it’s reported on the listener server:
In the event above the ACK sent back to the Syrus is : 356612021234567
In the event above the ACK sent back to the Syrus is : test
Often people receive several repeated messages when they are using Acknowledgements in TCP or UDP. In order to tune up the time of the re-tray, there is an acknowledge mechanism which uses a incremental delay that starts at 10 seconds before retrying to send a report for which there was no acknowledge from the server. The retry mechanism waits 10 seconds, 60 seconds, 120 seconds and 240 seconds if no acknowledge is received. The retry time will not reset if 240 seconds is reached.
Use the XAAO command to add more time to the delay between retries. The offset time will be added to the current retry time, meaning that the unit sends the first retry after 10 seconds + offset time, the second retry after 60 seconds + offset time, and so on.
To set an offset time of 15 seconds, use:
If you have to update the APN of your Syrus device you can do this via SMS remotely (as long as the device is registered on the GSM network).
In case you don’t have communication via SMS, then you would have to update the APN locally via Syrus Desk.
This can only be done by DCT staff remotely. Please note we need GPRS APN access to the device, if it’s inside a VPN we cannot extract the script. To download the script locally on your desktop please follow the instructions found on this page: Scripting.
The Syrus Device has a built in buffer that can hold up to 7,200 events in case of signal loss, once the signal is recovery the Syrus will push all these events into the listener server. Note that if you reach an event over 7,200 the Syrus Buffer will replace the oldest info to get space for the newest one therefore , it wont report that data since it wont be in Syrus buffer anymore.
It is not possible to calculate exactly how many bytes your Syrus will consume, what we can do is approximate based on the load of the event reports and the approximate distance the vehicle will travel.
Without including the header information, the typical size of a regular event – 61 bytes
If you include regular extended tags this could increase from 80 – 120 bytes
If you include ECU Monitor accessory it could be up to 250 bytes
- An IP packet is composed of two parts: the packet header and the payload. Payload in our case is the event reports above.
- The size of an IPv4 header is at least 20 bytes.
- The payload of the IP packet is called a TCP segment or a UDP datagram.
- A UDP datagram consists of a UDP header and the transported data.
- The size of a UDP header is 8 bytes.
- A TCP segment consists of a TCP header and the transported data.
- The size of a TCP header is roughly 20 bytes.
- This means an IP packet with an empty UDP datagram or TCP segment as payload takes at least 28 (IPv4) bytes in UDP, and 40 (IPv4) bytes in TCP.
The factors that influence the most are:
- Size of Reports – low/med/high event reports (payload) – add 60, 120, 250 bytes
- TCP or UDP – add 28 or 40 bytes to the event reports if using ACK add 15 bytes or the size of the ID of the event report
- RPD – reports per day – calculate how many hours a day the device is on and multiply this by the frequency of reporting
Medium Event Reports, TCP + ACK, reports every 2 min with Ignition ON and every 12 hours with Ignition OFF.
( 120 bytes + (40 bytes + 15 bytes) )* ((9 hours ON * 60 min)/2 min) * 25 days a month) = 1181250 bytes or 1181 KB / month. About 1.2 MB/month.
We recommend the following links for installation purposes:
Database of wiring diagrams for different vehicle’s – Free
Vehicle wiring, Relay Diagrams, and Technical Information – Free
There is no command needed to save the changes you make to a Syrus. Everything you send to the device as a command will automatically be stored in memory.
Please contact our sales department for more information about the prices of our products.
– Batteries swell only if they are charged or discharged at temperatures higher than 40°C
The Syrus charger is designed to keep the internal battery 100% charged and to use it only for backup in an emergency case (when the external power source has been cut). This means that when a Syrus is receiving external power 100% of the time, internal battery is never used. Thus the battery under these conditions will have no reason to swell up, and as long as there’s full time power, the Syrus can work at extreme temperatures reaching almost 80°C
We can find a complete information about Syrus’ battery under this link:
The higher the AMP – longer will be the battery life.
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 this 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.
Our Lithium-ion polymer batteries have a high power density that gives you a long battery life in a light package. And you can recharge a lithium-ion polymer battery whenever convenient, without requiring a full charge or discharge cycle.
The length of time your battery will power your device depends on how you use it. This battery it’s supposed to work perfectly during the first year, then begins to wear and can last up to two more years.
In Syrus 1 all depends of the battery. This means that the battery life is less than the Syrus 2 that does not depend of it.
For more information visit this link: http://www.batteryuniversity.com/parttwo-34.htm
In Syrus 1 we have to change the battery every one or two years in order to maintain the operation of it. Following all the steps of installation of the equipment and looking after it , we can prolong the life for more than five years.
Same thing in Syrus 2, but it does not depend of the battery and it is even stronger than syrus1 which means it has more life.
Qualifiers: Q, R.
This message allows to consult the SIM Card ID of the SIM card currently installed on the Syrus.
To consult the SIM card ID, send:
The Syrus will reply like this:
If no SIM card is installed, the response will be error 13:
Always send a >SRT< command before removing the SIM card, due to the risk of possible damage to the SIM card. Follow this 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.
It is often suggested that removing the SIM card and battery, cleaning the SIM and putting it all back together will cure a number of faults. Most of this advice is wrong because the problems are often caused by other things, sometimes even the network itself. Quite often the act of restarting the Syrus, as in this case, will co-coincidently ‘cure’ the fault.
However, some faults are caused by the SIM contacts becoming dirty and going dull. Messages such as ‘Insert SIM’ or ‘SIM Not Valid’ can be caused by dirty contacts.
One of the best ways to clean your SIM contacts is to use a pencil eraser or rubber. Simply lay the SIM flat on a desk and gently rub the gold colored SIM contacts with the rubber. You will be amazed how the dull surface becomes brighter. Then blow off the bits of rubber and finally wipe with a dry piece of kitchen towel. Job done!
After cleaned the SIM, please take the Syrus unit and try to lift carefully the contact pins located in the SIM card slot with a knife blade very thin.
fig: SIM card slot pins.
Warning: Don’t use an ink eraser as they tend to be too abrasive. This method, which doesn’t require any fluid, reduces the chance of damaging the SIM with contaminants.
The Syrus unit weighs 6 oz. or 0.35 lb.
We recommend a Corrosion Protection Tape.
Corrosion Protection Tape 1200 is a 20 mil general purpose corrosion resistant tape. The tape is applied over primed pipe to protect the pipe and pipe joints from corrosion.
For more information and how to get this tape please visit the link below.
In order to delete all messages store in the unit’s buffer, just send this command:
Please note that in order to change the APN remotely, you need communication via the original APN.
If there’s no connectivity with the original APN then you have to change the APN locally via the Serial port.
This process can be done a number of ways, in this example we’ll use an empty event and a user signal.
First, find an empty Event Definition – to do this: ask the device for an event index like this:
If the response is:
then you have an empty event, in this case our event #40 is empty so we’ll use it.
Next, find a User Signal that is not in use.
for this we recommend using signals 15-19 (normally these are rarely used).
Finally, we’ll use the following information to change the APN:
Empty Event: 40
User Signal: 15
This is the result:
Now that we have defined the event, the last step is to activate it: to do this simply activate User Signal 15 like this:
The new APN: data.m2mcloudconnect.com should be configured on the device, and we can now communicate via this APN no problem.
Earlier users of ECUmonitor could noticed that the new ECU Monitor Devices comes with an Orange wire to read OBDII protocols and older devices not.
It is possible to read OBDII protocol with old ECUmonitors too. Follow these simple steps to upgrade the older hardware and achieve it:
– Weld an Orange wire in “K” through-hole:
– Follow the Firmware Upgrade procedure detailed here
– Ready to work with OBDII!
Sometimes, and often in Syrus 1 than successors, a Syrus could be found with all its LEDs off. There are several causes to that, such as:
– Battery out of charge
– Hardware damage
– Memory corruption
We are going to evaluate each case:
Note: Syrus 2 works whether with or without battery since it is connected to an external power source, but Syrus 1 only works if it has its battery connected.
Hardware Damage: There are 4 points marked in red in the picture below: A, B, C and D
With a Volt-meter and having sure the Battery and external power are connected, test against Ground the voltage in the four test points. It must be as follows:
A: Battery Voltage.
B: 3.3 Volts Main power source output. This is the voltage output of the Voltage regulator IC501
C: 2.9 Volts. It just means “Modem ON”. If the voltage here is lower it means
If any of the voltages expressed here shows different in your unit, it has a hardware problem. Please contact support team for further information. Also please take a look to the TVS protection Diode. More information about this diode here
Memory Corruption: After an abrupt interruption of energy provided by internal battery an “Unexpected Reset” could happens, resulting in a memory corruption; same as when a USB memory is retired abruptly from a PC’s USB slot: It could not happens nothing at all, or all the files stored in such memory could result damaged. In Syrus’ memory case, the damage could be from a simple Script erasure (Both Syrus 1 and Syrus 2 stores and protects its APN and destination Points in another memory), to a total corruption of the Firmware. Always check the connector and wires of Internal Battery to avoid Unexpected resets.
For this case:
1. From a Terminal Try to send >QVR< command at 9600 and 57600 bps.
If there are response >RVR…< at any of those baud rates simply reestablish 115200 baud rate with >SXABR115200< and you are going to be able again to work with Syrus desk.
– Try to send the command ATI followed by hitting the “Enter” Key at 9600, 57600 and 115200 bps. If there are some response at any of those baud rates please sent these both commands to try to restore the unit:
At this point you should be able to send TAIP commands again. Send >SXAEC::rt 2<to reactivate Autostart.
If there are response to those AT commands but you still can not send TAIP commands the memory could be corrupted, but you can try to restore it with Syrus Upgrader Software. NOTE: A natural serial port is needed. Contact support for further information.
If there are not response at all, contact support either.
There are 2 ways to know the phone number in a Syrus:
1. By QXARS Command
In some countries (Not all of them) Operator could add the line number associated with its simcards in a slot of a simcard. >QXARS< command could help in this case The response to that command could include the following information (Note: Information may vary between operators and/or countries):
>RXARS;IMSI;Name of the server provider;Simcard ID;Name associated with phone line;Mobile phone number;Type of mobile phone number<
Example: To get the phone line number of a Syrus in Chile using Entel PCS:
There are two ways to know this:
1. If you are using ECUmonitor, some On-board computers shows such voltage by sending this command:
Also you could set Vehicle’s battery voltage as an extended tag OB
2. Else, Syrus counts with an Analog-To- digital Converter input. It only works between 0 and 10 volts, so you could make a Voltage divisor with two resistances. The following examples shows voltage divisors proposed for 12 and 24 Volts batteries respectively:
With the circuit above voltage read between Vout and Ground will be between 0 and 10 Volts. Vout is connected to White wire of Syrus, and you will be able to ask: >QXAAC<
The unit may reply like this:
Note that the answer could be also a percentage
To alert a voltage of external battery below 22 V:
If 24V == 10V then 22V = X , So The voltage to be alerted in ADC will be 9.16
Creating a threshold:
To have this value as an extended tag:
>QSI< Gives Simcard’s ID
>QXARS< ives all the parameters available of a simcard inserted in a unit
Syrus 1 (Only last version 1.3.61)
>QXARS< ives all the parameters available of a simcard inserted in a unit
See the below diagram as an example of how to add a fuse by pass to protect the wiring of the vehicle:
Position Accuracy Without aid: 3.0m (50% CEP) DGPS(SBAS(WAAS,EGNOS,MSAS)):2.5m (50% CEP)
ST – Status
This message provides information about the unit’s GPS receiver. The message has the following format: >QST<
Syrus GPS comes with a filter that does not update GPS coordinates (lat,lon) until certain conditions have been met, for more information please visit: Syrus GPS Anti-drift Filter.
After understanding the GPS filter, the first step would be to disable the GPS filter and see if the coordinates update:
>SXAEC::gps 9 0<
If the coordinates fail to update after some time (5 minutes), a series of resets can be applied to the internal GPS module:
After completing the resets please turn the GPS Filter back on with the following command
>SXAEC::gps 9 1<
If the GPS information has not been resolved with the resets explained above, then it could be a physical problem with the location of the device inside the vehicle.
It is recommended that the device be installed parallel to the Earth, facing with the Syrus logo towards the sky. Also, no metal should be covering the device or it’s views of the sky as this blocks GPS signals.
If the above steps have been followed and the unit is still experiencing problems the use of an external antenna is recommended.
Otherwise, please contact support for more information.
The first step is to check if there’s LED activity when you connect the Syrus to the power supply, if there is no LED activity we recommend the Syrus 2 Troubleshooting Guide.
Remove the SIM Card, power supply, and internal battery. Connect only the the external power supply and see if the RED LED turns on after a couple of minutes, this LED indicates when the Syrus application is running (it flashes because there is no SIM card inserted). If this is the case then refer to the Syrus Desk FAQ for more troubleshooting options.
- The power consumption of a Syrus device in operational mode with its internal battery fully charged is 1 Watt.
- The power consumption of a Syrus device in operational mode and assuming that the internal battery is being charged, could be up to 4.8Watts
No, the Syrus 2 hardware is different than the the Syrus 1 hardware and some of the accessories used for Syrus 2 cannot be used on the Syrus 1.
The supported Syrus 1 accessories include:
The best and fastest way to distinguish between Syrus 2 and Syrus 1 is to look at the antenna connector, if the connector extends past the case it’s a Syrus 2, or else it’s a Syrus 1.
You can lock the unit’s serial port using the command
where you must change pppp for a 4-digit alphanumeric code, preventing other programmers from modifying the configuration via the serial port.
This blocks the unit via the serial port only, over the air the communication is the same.
If you want to unlock the unit, you must use
where pppp is the alphanumeric code you used in the lock.
Please make sure to update the firmware of the device to the latest stable version.
This issue is most likely the cause of a faulty wiring harness, the first step you should take when you encounter this issue on the field is to shake the wiring harness and see if the LEDs come back on, if this is the case then replace the wiring harness for a new one.
Please visit the Syrus 2 Troubleshooting Guide for help on this issue.
Please visit the Syrus 2 Troubleshooting Guide for help on this issue.
Please note that this Error Code might be temporary as it could appear when the device has recovered from a reset, that is normal.
If after some time the Error Persists, then please visit the Syrus 2 Troubleshooting Guide for help on this issue.
Please refer to the following tutorial to help you get started with SMS interaction.
Yes, there is a way to assign two UDP socket as destination points on the Syrus, where the first occupies Destination Point P04:
Where xxx.xxx.xxx.xxx is the IP address, and pppp is the port number.
The second UDP socket occupies the Destination Point P05: (note – P04 has to first be assigned before you can occupy P05)
Some AVL platforms support sending commands remotely to Syrus devices.
As long as your device is not behind a VPN, DCT can remotely upload a script using Syruswatch, please contact support and provide the script & IMEIs of the Syrus devices you wish to send the script to.
If you have your own Pegasus Gateway entire scripts can be changed with the click of a button, please contact a commercial representative for more information.
Yes you can connect all 1-wire accessories DCT provides to that one red/white cable. We have successfully connected all 4 accessories that go connected to the 1-wire port simultaneously without a problem (iButton, ECU, Temperature, I/O Exp). Please see the following page regarding communication between multiple 1-wire accessories.
We are capable of detecting these jammers, but we are not capable of transmitting any data. Syrus Intelligent event machine does, however, allow us to execute actions and commands when Jamming is detected. Actions that include turning the vehicle off for example.
Syrus is not capable of detecting GPS Jamming.
Please visit our Jamming Tutorial for more information
The following could be the reasons why you are experimenting such situations:
1. If you are using TCP or UDP without acknowledgement is a risk of data loss because anything confirms to the unit the message arrived. The use of an ACK from the server to the unit for each event report sent is strongly recommended. This process is made as follows:
a. The unit must be configured to wait an ACK from the server for each event report it sends (Note: just event reports REV or RET type must be acknowledged; Responses to commands sent do not need acknowledgement).
Example of Destination Point using TCP with ACK (Acknowledgement): >SXADP0001yourdomain.com;5555<
Example of Destination Point using UDP with ACK (Acknowledgement): >SXADP0403yourdomain.com;5555<
b. Every Event report sent by the unit must be replied by the server with the ID assigned to the unit. Then, if unit’s ID is Lab0123, the server must answer Lab0123 to the unit.
2. If you discard the above sugestion, then make sure the unit is not reporting in the same place; in this case you must to make a fine tunning to the Anti-drift filter, or remove it as shown above.
The maximum length is 20 meters by adding the same cable gauge or using a thicker gauge.
Yes, the operation of the regular inputs and outputs on the Syrus devices still function the same way.
After installing the I/O Expander you will have a total of 7 inputs and 6 outputs to work with.
The speaker works best with a 5V DC power supply.
Adjusting Voice Parameters
The command is XAVP – Voice Parameters –
The structure of this command is as follow:
For A we have 4 different options
- M: Microphone gain.
- S: Speaker volume.
- T: Dialing and ringing tones.
- R: Ring before pick up time. Time waited before picking up the call.
For B (depending on the value of A) we have the following parameters available.
- For microphone gain: 0-7
- For speaker volume: 0-4
- The characters “+” and “-” are also allowed and will increase/decrease the value by 1.
- For Dialing and ringing tones:
- 0: Disables the dialing and ringing tones. This is the default value.
- 1: Enables the dialing and ringing tones.
- For ring before pick up time: Range 0-9. Time in seconds. Default time is 0, pick up immediately.
To adjust the microphone gain:
>SXAVPM0< lowest >SXAVPM7< highest
To adjust the speaker volume:
>SXAVPS0< lowest >SXAVPS4< highest
To enable dialing and ringing tones:
To wait 5 seconds before picking up the phone:
Polar pattern: Omni-directional
Frequency Response: 50Hz-16KHz
Output impedance: 1000Ω±30%
If you are using the 1-wire temperature sensor make sure somewhere in your script you have the command:
This command enables the 1-wire temperature sensor.
If you are using the temperature sensor that connects to the Serial Port for Syrus 2 devices please place the following command somewhere in your script:
The sensor works at a 9600 baud rate – somewhere in the script add this to change the baud rate:
make sure you have the green wire which extends from the sensor connected to the Syrus green wire.
There are three ways to obtain temperature readings from Analog Interface:
1. Consulting: Send the command >QXAADC< to the unit. The response culd be as follows:
Indicating that input A has a value of 749 mV, input C has a value of 2085 mV and input B does not have a sensor connected.
2. Defining thresholds: Defining thresholds with the XAEA Configuration Command. These thresholds configure how the events are triggered by the M signals.
For example, set a threshold that will use the average of the value measured by the three sensors for a voltage of 1700mV
Then an event that uses this threshold is defined, for this example the falling edge of the signal will be used, meaning that the event will be triggered when the voltage falls below the threshold:
3. Extended Tags: You can set the unit to report an aditional information tag attached to the normal events reporting temperature.
Example: A report showing temperature is needed every ten minutes.
– Create an Extended Format containing EA tag:
– Create a periodic counter each 10 minutes:
– Create an event definition which report will include Temperature information:
The gray and blue cables are used to measure differential voltages that can sometimes be found in large fuel tanks.
Normally there’s two wires that are used to measure the level of the fuel tank. These are found behind a plastic cover directly on the fuel tank. If you are going to connect to these wires you may use the Blue and Gray cables to do so.
This method of measuring the fuel level has only worked in cases where:
- Fuel tank is large (>80 gallons)
- Fuel tank is cylindrical
- Voltage measured in these two cables is less than 5V
Thus it will not work in light/conventional cars and vehicles, nor SUVs or Pick up Trucks, only large trucks and heavy duty vehicles.
Please see the following page for a list of supported vehicles.
DCT intends to update the information found on that page regularly with updates from manufacturers.
If you have successfully tested the Syrus ECU Monitor on a vehicle not listed in the page please tell us: firstname.lastname@example.org
Please allow up to 20 minutes for the ECU to upgrade once you send the >SXAEM1ecu_##< command. In case that the ECU does not upgrade after 20 minutes, try sending the upgrade command once again. Remember to have the ECU permanently powered during the upgrade, you can ask the device: >QXAEM0< to see the status of the Upgrade.
If the problem persist, it may be because there is too much noise or signal interference to the one-wire cable that connects the Syrus to the ECU Monitor (white with red cable). We recommend the upgrade when the vehicle is parked with the ignition off.
Light Vehicles (OBDII Signal Protocols)
ISO 14230-4: Also known as KWP2000 or K-Line. Uses the orange cable only. There are two variations of this protocol:
- ISO 14230-4 (5 baud init,10.4 Kbaud)
- ISO 14230-4 (fast init,10.4 Kbaud)
ISO15765: Also known as CAN OBDII. Uses the green and yellow twisted cables. There are 4 variations of this protocol:
- ISO 15765 CAN (11 bit ID,500 Kbaud)
- ISO 15765 CAN (29 bit ID,500 Kbaud)
- ISO 15765 CAN (11 bit ID,250 Kbaud)
- ISO 15765 CAN (29 bit ID,250 Kbaud)
ISO 9141-2: Uses the orange cable.
Trucks/Heavy Vehicles (CAN Bus Signal Protocols)
- J1939: 29 bit ID, 250Kbaud. Uses the green and yellow twisted cables.
- FMS: 29 bit ID, 250Kbaud. Uses the green and yellow twisted cables.
- J1708/J1587: Uses the brown and purple twisted cables.
The SAE J1939 protocol defines this impedance as standard. However, we have seen cases where the resistance is above these values and the ECU Monitor could still work. We recommend doing the following:
- Verify that everything in the vehicle is working correctly before connecting the ECU Monitor
- Connect the ECU CAN_H & CAN_L and make sure everything is still operational
- If it works, then you can leave the installation. However, if the installation fails then the fault is not on the ECU Monitor, it’s the fact that the wires don’t have an internal terminating resistor. Do not proceed with the installation.
If these 3 steps are followed and you proceed, query the ECU Monitor parameters with the command:
and paste the response here.
There are only two ways to do this:
1. Connect it to a vehicle with compatible CAN Bus / OBDII interface.
2. Buy a CAN Bus / OBDII Simulator:
For J1939 we use (click here)
There are many models, and the cost depend of how many parameters you want to know. We have the Engine Basic Edition version 1.0 and it is pretty good. The cost of it is about 660 dollars.
For OBDII we use one called EcuSim2000 (click here).
The ECU Monitor has a lot of extended tags that add functionality on the platform side of reporting.
First we need to figure out which parameters we would like periodically and those we don’t need periodically. Second, depending on the parameters read with the command >QXAEM0< you can adjust the extended tag definition.
Syrus extended tags are defined with the XAEF command, you can have up to 3 extended tags [ A B & C ]. For this FAQ we are going to occupy B & C.
Where B is used for periodic tags, and C is used for one time or non-periodic tags.
More details about the parameters can be found in the EV – Event Message Command of the Syrus manual.
The parameters available with extended tag information are the following:
OT - Trip distance (m) OD - Total traveled distance. Odometer (km) OA - Throttle pedal position (%) OE - Engine revolutions per minute (rpm) OY - Instant fuel consumption (liters/hour) OC - DM1 diagnostic messages. OL - Vehicle's current fuel level (analog - mV) OX - Fuel Level (%) OH - Total engine usage (hours) OI - Total fuel used while in idle (liters)* OU - Total time while engine in idle (h) OF - Total fuel used (liters) YD - OBDII distance traveled with Malfunction Indicator Light On [MIL] (km) YE - OBDII instant fuel efficiency (km/liter) YO - OBDII Oxygen Sensor YT - OBDII MIL Status
Set up Extended Tag B with information that we would like to receive periodically:
Set up Extended Tag C with information that is not needed periodically, only when they occur or when the thresholds are exceeded:
Not recommended unless you find an application – OY;YE
Setting up the events with the extended tag information
Let’s say that our periodic report is in Event Definition #00 – we would add the Extended Tag B information like this:
For extended tag C we could set various events with this Tag:
Example: when speeding is detected we would like to know the throttle position:
#Event 04 – Speeding
For Diagnostic Message Reporting we can use signals G08 & G12:
#Event 44 – ECU or OBDII Error Message Detected
First, make sure you upgraded your ECU to the latest Firmware version. This occurs when the ECU Monitor’s white cable is not correctly connected to the Syrus 1-wire cable. Also, if the cable that supplies power to the ECU Monitor fails when the vehicle is ON.
There are a couple ways to obtain these codes:
1. Manually by querying the device
2. Via Pegasus
For method 1 we will have to send the XAOC command to the Syrus once the ECU Monitor is connected:
The response from the Syrus should be something similar to this if there are no trouble codes reported:
If a trouble code is reported the response will look like this:
Where 91,3,0,5 refers to SPN, FMI, CM, OC
SPN 91: Suspect parameter is accelerator pedal position.
FMI 3: Failure mode is identified as voltage above normal.
CM 0: (1 bit)
OC 5: Occurrence count indicates trouble has occurred 5 times.
For more information about the interpretation of these Trouble Codes – refer to the following SPN FMI Manuals:
Oshkosh Diagnostic Codes Manual
Controls Incorporated Common SPN FMI Codes
Murphy’s PowerView Error Messages
2. The second method is to configure the Syrus using Pegasus Gateway and refer to the Raw data generated from the ECU Monitor.
All you need to do is select the parameter from the Raw Data Browser, like so:
Once you generate the table you will see something like this:
Which indicates the following (according to the manuals above)
SPN 639: SAE J1939 MULTIPLEXING PGN TIMEOUT ERROR
FMI 9: Failure is identified as a Timeout Error
CM 0: (1 bit)
OC 16: Occurrence count indicates trouble has occurred 16 times.
For more information, please look at the following Page: Data Trouble Codes
Once the ECU Monitor is connected, turn on the vehicle and check that the 4 status LEDs flash once indicating that the ECU Monitor is properly connected to the power source, and wait approximately up to 1 minute while the ECU Monitor recognizes the available protocols used by the vehicle. If both protocols are available J1939 and J1708, the J1939 will be used, since this protocol is newer, faster and has a better information resolution. The J1939 is being used exclusively on most newer vehicles.
Once the auto-configuration is finished, the status LEDs will show one of the following behaviors:
- Either LED1 or LED2 will flash twice every 5 seconds, indicating which protocol is being used. If FMS protocol is detected LED1 will flash 3 times every 5 seconds.
- LED3 indicates communication between Syrus and the ECU Monitor. It should always be flashing. Please verify the connection between Syrus and ECU Monitor of this LED is no flashing constantly. If ECU Monitor version is lower than 1.9 LED3 is not used.
- LED4 indicates OBDII protocol. it flashes once when ISO14230 is detected, twice when ISO9141 is detected and 3 times when ISO15765 is detected. If ECU Monitor version is lower than 1.9 LED4 indicates communication between Syrus and the ECU Monitor.
Please see the Installation Guide for a complete description of the cables. ECU Monitor Installation
This orange cable goes inside the OBDII connector, so if you are using any other protocol that is not the OBDII, you do not need to connect it and you can cut it.
Send this command to the device:
and paste the response at the bottom of the page here.
Once you have connected a ECU monitor in one fuel tank, and we have more than one fuel tank in the vehicle, we need to multiply the value we obtain in a tank per the numbers of tanks we actually have in our vehicle.
Example: In a vehicle with 3 fuel tanks.
ECU monitor reports us that we consumed 10 liters of diesel, but in fact, we consumed 30 liters of diesel because we need to multiply 10 liters per 3 fuel tanks in order to obtain our total value of diesel consumed today.
CANGOclick© is an accessory which reads vehicle’s CANbus signals without making a wire to wire connection.
This technology guarantees that no intrusive signals are send to the vehicle CANbus or J-bus. This eliminates liability matters, warranty issues or wrong connections
- No direct CANbus and J-bus connection;
- One cable fits all vehicles/equipments;
- 100% accurate recovering of CANbus and J-bus data;
- 100% non-intrusive technology;
- Safe and reliable reading of CANbus and J-bus data;
- No soldering, wire cutting or crimping;
- No physical wire to wire connections.
Through your web host you should have a Domain Manager inside your CPanel.,
Once the subdomain is created you have to create an ‘A’ record inside your DNS Zone editor that points to one of the dedicated Pegasus Gateway IP addresses – the exact IP address is given to you by your commercial representative.
Please visit our Tutorials & How To page for more information.
Please visit our Tutorials & How To page for more information.
Only Syrus GPS devices (both Syrus 1, 2, and soon 3) can be used on Pegasus Gateway.
Pegasus Gateway will also integrate all the accessories DCT has to offer on Pegasus.
Please visit our Tutorials & How To page for more information.
When you are creating Geo-fences in Pegasus in order to create rules of alert, you can whether configure Pegasus to show addresses or to show the name of the Geo-fence instead.
To select if Pegasus must show addresses or Geo-fence name instead, check or UN-check the following Check-box:
Path: Menu Notifications -> Rules -> Zone Tab -> Pick a Zone -> Edit
Please use the following link for a list of different implementations:
We have a tutorial guide that includes all the information needed to get started on your very own JSON RPC listener.
Please follow the link for more information: Pegasus Gateway.
Please contact us at support with the URL where the listener is located. We will send a sample packet which expects an ‘ok’ as a response, if this is successful we can enable the full redirecction.
Event example: 2014-09-10 13:22:55: HighGenRate 356612022000000 >>> 0.74 /0.20 [events ps]
This notification means; That on Sept, 10 2014 the device 356612022000000, measured events at a rate of 0.74 events per seconds.
The limit is setup at 0.20 events per seconds which is equal to 1 event every 5 seconds during a 2 minutes window. The report will be triggered when a device is generating a high volume rate of events, which means there’s an issue that needs to be resolved:
- Connectors issues
- Output shorts
- Hight resolution configurations
- Any other electric or configuration problem, causing the device to generate a high volumen rate of events.
This is translated as:
- High consumption of SIM card’s data
- Unit storage buffer’s capacity reduced
- Limits the capability of the gateway to get managable reports.
We have an advanced API available for every Pegasus Gateway.
The Remote Procedure Call Application Program Interface (RPC API) is used by remote machine-clients to:
- Consult Gateway tracking, organization, analytics and general information data.
- Interact in real time with devices/vehicles to drive outputs, do MDT/Garmin Chats, change configurations among many other interactions.
- Manage the Gateway Notification Rules.
Inside your Gateway you can find more information as well as examples of the interaction.
Make sure your Syrus 1 is firmware 1.3.61, for upgrading instructions please look at the Syrus 1 FAQ below.
- Rate_avg = Amount of messages sent by your devices to the listener per second.
- Active = Total amount of units ever connected to your Pegasus for the life of the listener or after it was restarted.
- Online = Units currently connected with a valid session network session.
DC voltage: 8v – 32v .
But we recommend to feed the camara power from the green cable (pin 7) of the Syrus harness.
The size of the photos can depend on the lighting, colors, shading, etc.
Depending on the resolution chosen the sizes vary from :
The first approach is to double check the type of camera, the cable installation and and setup of the carrier detect.
Also, make sure you have upgraded your device to the latest stable version (found on the footer of the site).
No, you can’t. Both accessories requires the use of the RS-232 (DB9) Serial connector of your Syrus GPS device.
You can use the following credentials for a demo FTP server,
- IP: 18.104.22.168
- Port: 10239
- username: test
- password: mauro0228
This command deletes the serial camera files stored on the Syrus and restarts the photo id if serial camera mode 2 is being used.
This happens if you buy your devices from an authorized DCT distributor. If this is the case, please send DCT Support a complete list of the IMEIs that you bought from the distributor, we will proceed to update the database and assign the devices to your account.
Scripts can only be sent by authorized DCT members, please send a request to our support engineers with the following information:
Please see the tutorial found in the following page for the meaning of these Undervoltage parameters: Syrus Watch.
Please visit our VPN resources for the necessary socket connections that need to be enabled in order to have your Syrus device report to Syrus Watch portal.
List of Reason’s why Syrus Desk will not connect
You must upgrade the Firmware of the Syrus 1 device to at least 1.3.42. Please insert the SIM and load the script for that SIM (the device will accept commands via SyrusDesk) once the green LED flashes twice rapidly you can send the commands >SXAFU0A< to upgrade to firmware 1.3.42 then send >SXAFU0B< to upgrade to 1.3.61.
When the upgrade command is sent to the device >SXAFU0A<, >SXAFU0B<, or >SXAFU0C< the device will enter an upgrading mode where it shows lots of A’s in the Syrus Desk console window. This should take 3-5 minutes to finish.
If the process is taking longer than 10 minutes to upgrade, consider sending the command
Afterwards you should wait a couple of minutes for the unit to respond:
Then send this command:
If the A’s on the screen show up randomly after that procedure, consider formatting the device and loading the Firmware manually.
Make sure the internal battery is fully charged and properly connected.
Consider formatting the Syrus and reloading the Firmware of the device. Click here for a step-by-step guide on how to do this.
If this happens to you please contact DCT Support for further assistance, please include a log the codes seen and the IMEI of the device.
This is due to two reasons,
1. The device is in communication with an accessory via the serial port (Garmin or Serial camera – make sure to disable these modes).
2. A bad serial cable / usb cable, make sure you have downloaded the latest drivers for the cable before you connect the Syrus device.
Please visit our Syrus Desk support page for the step by step tutorial.
This is completely normal, in some cases these red lines would stop the script from completely loading. Just restart the device or load the script configuration again, as long as the Syrus Desk console shows script finished once it’s done loading the lines, then you are all set and the Syrus is 100% configured.
We have video tutorials dedicated to showing you how to program devices using Syrus Desk.
For Firmware versions prior to 1.3.42, please send the command:
This will upgrade your device to FW 1.3.42, to upgrade to 1.3.61(std) send:
The latest Syrus 1 Firmware will always be 1.3.61, there are 3 different versions of the 1.3.61 however.
Due to the memory limitations Syrus 1.3.61 firmware were divided into 3 functionalities:
- Standard – supports MDT PAD
- Garmin – supports Garmin Mode
- iButton – supports up to 10 iButtons
Make sure the internal lithium-ion battery is fully charged, see the Diagnostic Manual for step by step instructions on recovering the devices.
Possibly, as long as the modem is still responding regular ASCII text and you don’t see ^EXIT or ^SHUTDOWN responses when it’s connected to the serial port. DCT recommend you first change the NTC resistor and check for short-circuits. Please see the Diagnostic Manual for step by step instructions.
This happens when too much current enters the battery, the only way this could occur is if there’s an excess of temperature while the battery is charging. Please look at the temperature specifications in care & caution section of the Syrus Manual.
Please see the Diagnostic Manual for step by step instructions on recovering the device.
Visit our diagnostic guide for complete instructions on how to recover devices.
DCT recommends the use of inline fuse holders when making installations [3-5 A ratings]. Also, we recommend using a bi-directional diode connected to the positive and negative pins on the Syrus 1, this protects the device and will not cause the internal voltage regulator (also called – IC3) to burn. Reference Part for the bi-directional diode: P6KE36CA
As a general note, all lithium-ion batteries lose a significant amount of charge after 2 years (depending on the environment this period could be shorter). It is recommended to rotate the batteries between 1.5 – 2 years.
To test batteries with your Syrus 1 device first measure the voltage of the battery directly – connect the positive probe of your multimeter to the red wire of the battery, black probe to the black wire – it should be between 2.7 V min to 4.2 V max. If your battery is marking 0 V DC then we recommend slow charging it with a Lithium-ion charger – look for (1~2A) until it reaches 2.7V then charge it normally by connecting it back to the Syrus 1 device.
No, this time cannot be changed, the output 1 (red/blue cable) on Syrus 1 GPS will always take 20 seconds to activate. Syrus 2 devices change outputs immediately.
- Charging temperature: 0 C to +40 C
- Operating temperature: 0 C to +60 C
- Storage temperature: – 30 C to +85 C