Documenti di Didattica
Documenti di Professioni
Documenti di Cultura
Operation Manual
CONFIDENTIAL DOCUMENT
This document belongs to intellectual property of Suntech
International Ltd. and shall neither be copied nor be given to any
3rd parties without prior written consent from the company.
DO NOT MAKE ANY COPIES
Table of Contents
1. Introduction ........................................................................................................................................ 7
2. Overview ............................................................................................................................................. 9
2-1. Operation modes ......................................................................................................................... 9
2-2. Reports sent by device................................................................................................................ 9
2-3. Parameter change...................................................................................................................... 10
2-4. Features ..................................................................................................................................... 10
3. Communication String Format ........................................................................................................ 12
3-1. Command format ....................................................................................................................... 12
3-2. Report Format ............................................................................................................................ 12
4. Configuration ................................................................................................................................... 13
4-1. Network parameters .................................................................................................................. 14
4-2. Reporting parameters ............................................................................................................... 16
4-3. Event Parameters ...................................................................................................................... 18
4-4. GSM Parameters for SMS messaging / phone calling............................................................. 25
4-5. Parameters for various features ............................................................................................... 26
4-6. Voltage control parameters ...................................................................................................... 28
4-7. Motion sensor parameters ........................................................................................................ 29
4-8. Circular geo-fencing parameters .............................................................................................. 30
4-9. Additional Parameters (TCP/UDP Parameters) ........................................................................ 30
4-10. New parameter setting ............................................................................................................ 33
4-11. Telemetry parameters.............................................................................................................. 36
4-12. Driver ID parameters ............................................................................................................... 38
4-12-1. How to add Driver ID ............................................................................................................................. 38
4-12-2. How to remove Driver ID ...................................................................................................................... 39
4-12-3. How to get Drive ID ............................................................................................................................... 39
4-13. How to set Driver Pattern Analysis parameters..................................................................... 40
4-14. Vehicle Engine Information ..................................................................................................... 41
4-14-1. How to Set Parameters for Engine Event ........................................................................................... 41
4-14-2. How to Get ECU Command Parameters ............................................................................................. 42
4-14-3. Requesting Information about ECU (or ECM) by J1939 .................................................................... 43
4-15. LATAM (Latin America) parameters ....................................................................................... 44
4-16. Polygon geo-fence parameters............................................................................................... 46
4-16-1. How to set polygon geo-fence for each group .................................................................................. 46
4-16-2. How to set Polygon Service ................................................................................................................. 49
4-16-3. How to get Information about Polygon Group .................................................................................. 50
4-16-4. How to get Information about Positions of the Polygon Group ........................................................ 50
4-16-5. How to erase Polygon Group ........................................................................................................... 51
4-16-6. How to get information about Polygon Service ................................................................................ 51
4-17. Temperature parameter ........................................................................................................... 51
4-18. Coin Machine Parameter ......................................................................................................... 52
5. Tracking and route deviation parameters ...................................................................................... 54
5-1. Start/Stop tracking ..................................................................................................................................... 54
5-2. How to set tracking positions ................................................................................................................... 54
5-3. Number of tracking positions ................................................................................................................... 55
6. Reporting to server .......................................................................................................................... 57
6-1. Status Report ............................................................................................................................. 58
Suntech International Ltd. Confidential Document
Doc. Title Author Page of Pages
Disclaimer
We, at Suntech, announce that this document and all other related products (i.e. device, firmware, and software)
have been developed by the company, Suntech International Ltd., which is hereinafter referred to as Suntech.
The information in this manual is believed to be accurate and reliable at the time of releasing. We, at Suntech, also
assume no responsibility for any damage or loss resulting from the use of this manual, and expressly disclaim any
liability or damages for loss of data, loss of use, and property damage of any kind, direct, incidental or
consequential, in regard to or arising out of the performance or form of the materials presented herein or in any
software program(s) that may accompany this document. When this document is released, it is most compatible
with a specified firmware version. Now that the functionalities of the devices are being developed and improved
continuously from time to time by Suntech, any alteration on the protocol, the firmware functions, the hardware
specifications of the product is subject to change without prior notice.
Copyright
We, at Suntech, notify that Suntech holds all parts of intellectual rights applicable in the copyright laws in all the
countries. The information contained in this document cannot be reproduced in any form without prior written
consent made by Suntech. Any software programs that might accompany this document can be used only in
accordance with any license agreement(s) between the purchaser and Suntech.
Warning
Our customers are required to be aware that connecting the wire inputs can be hazardous to both of the installer
and your vehicles electrical system(s) if not done by an experienced installer. This document assumes you are
aware of the inherent dangers of working in installing the device on the vehicle(s) and the machinery.
Document Amendments
When it comes to the firmware version column with specific firmware number, any amendment(s) on the comments
column should be made on this relevant firmware version (and the versions thereafter). Before applying any
changes made in this protocol, you are required to make sure that you have upgraded the firmware suitable for the
specified version.
1. Introduction
The ST300 (or ST340/ST340LC or their variation models such as ST300B, ST300V, ST300R, ST300A, ST300P,
ST300F, ST300H, ST300C, ST300K, ST340LC, etc.) is a vehicle tracking and controlling device. It is designed to
collect location data through GPS technology, various vehicle conditions through event lines, and interact remotely
with its server by using GSM/GPRS technology.
In order to make the vehicle tracking system work, device should be configured and installed properly on a vehicle
whose geographical position and/or state is desired to be remotely monitored and/or controlled.
Following this Introduction Chapter (i.e. Chapter 1.), the Operation Manual is organized as below.
Chapter 2. Overview
This chapter gives descriptions on the two (2) formats, Command (all the formats received by device) and
Report (sent from the device).
Chapter 4. Configuration
This chapter gives users explanation on how and what parameters are required to be set in configuring
device.
This manual describes setting commands which can be sent with following three options;
Option 1: Setting by PC.
Option 2: Setting by GPRS.
Option 3: Setting by SMS.
Practically special program (named as SyncTrak) is used for setting. It enables setting much easier and
multi-setting possible in PC environments.
This chapter gives users explanation on how these parameters need to be set if user wants to enable the
device to track moving of vehicle along the routes predefined by the user.
This chapter covers when and what reports are sent back to the server by device.
This chapter describes what commands the server sends to its device.
This chapter gives users explanation on what commands can be made in addition to the commands
described in the Chapter 7.
This chapter gives users detailed information on key features of the device and on how to operate the device
if the events occur after configuring the parameters related to such events.
Please note that this Operation Manual is for the standard model. In case specific requirements are incorporated into
this Manual, such a manual applies only for the case.
For overall operation including installation, in addition to the Operation Manual, users should refer to other
documents such as Installation Manual, Technical Data Sheet, Firmware OTA (over-the-air) Manual, Buyer Change
Guide, Trace Log, Assembly Guide and so on.
2. Overview
Main function of device installed on a vehicle is to report vehicle location and status to its monitoring server at
predefined interval and to deliver command coming from the server for activating any appliance connected to the
device.
The device works in one of the three (3) operation modes below.
Driving mode:
Parking mode:
This mode is operational when Ignition is OFF for duration longer than the pre-defined time (T1).
In the parking mode, the device can get into special modes for power saving like Sleep mode and Deep
sleep mode. These power saving modes are described in more details in the end of this document.
Emergency mode:
This mode works either when panic button is ON or when one of any predefined events occurs.
Emergency report,
Event report,
Keep-alive report,
Alert (**),
Note (**): In addition to the reports periodically sent to the server as described above, device also sends
some alerts. For instance, device sends the server such an alert if the vehicle moves under the parking
mode or if the connected Input Line is changed.
Suntech can also increase this capacity up to a certain level if a customer of the device wants to do so. As soon as
the reporting condition for the device is recovered, the device starts sending all those accumulated reports according
to the following rule:
- Emergency (the most important) Command Response Alert Status Report Alive (the lowest priority)
This means that the emergency report is the first one that should be sent right after the GPRS network condition is
recovered.
Parameters which have already been set on the device can be changed via GPRS or via SMS or via RS232
connected with PC/ST50if a user needs to do so. Some controlling functions can also be implemented in the same
way.
How to change values of the current parameters is described in detail in Chapter 4 of this document.
2-4. Features
- LED Indicators
The LEDs indicate GPRS and GPS status. It is helpful to check what error(s) and why such an error has
occurred.
- Event Lines
Device has 2 output lines, 3 input lines and one ignition line.
** The ST300F uses the <OUTPUT2> line to control power for the fuel sensor(s).
In case firmware of the device has an (some) error(s) or needs to be upgraded to provide the user with newly
implemented services, the device can upgrade its internal ROM file by over the air (Firmware OTA), remotely
via GPRS. The users do not need to visit the vehicle individually to download the new firmware on those
vehicles.
How to do OTA is described in detail in the SunTech_OTA_UA_Protocol document.
- Parking Lock
Device is able to check if the vehicle moves away from the pre-defined parking boundary or starts moving
without having a mode of the ignition on. In case the device recognizes such an unauthorized moving or driving,
it sends an emergency report immediately.
- Over-Speed
Device checks speed of the vehicle and sends to the server an alert if the vehicle runs faster than the
predefined over-speed threshold values.
Device alerts when GPS antenna is disconnected. It is applicable only to the device models which have the
external antenna.
Device recognizes its connectivity with the main power source (i.e. vehicles battery) and is able to inform the
server about status on whether or not the main power line is disconnected. The device is also able to inform
the server about the voltage level status of the main power source and informs the server in case the voltage
level of the main power source drops down below the pre-set value. This function is applicable to battery-
installed device models only.
Device sends an alert when a battery charging error occurs. This function is applicable only to the device
models available with back-up battery.
The following format is used when the server sends command message to the device(s) as shown in the below table.
The Value (or Indicating Mark) and its Meaning are described individually.
HDR stands for the header, DEV_ID for device identification number, VER for version, Field 1, Field 2, etc.
The Device ID(consisting of9digits)is a unique number that each device should have. It is equal to the last 9 digits
of IMEI numbers shown on the back label of the device. Whenever the server sends a command message, it
designates a specific device along with the unique identification number of the device as a command receiver. And
then, the device recognizes a fact that it has received the command message and responds to the server with a
relevant response or a relevant action to be taken. This is how a normal communication is made between the server
and its device.
On the other hand, sometimes, a very bad GPRS connection between a device and the server may consequently
bring about a bad result that the specified command message would be delivered NOT to the targeted device BUT
to other device. In such a situation, the wrong device does not accept the command message because the device
ID number of the message does not match the ID number of the wrong device.
However, we might consider a situation in which a command message is delivered to a device via RS232. In such a
situation the device accepts the command message even though the device ID number of that command message
is NOT its own one.
The contents of the following table show what messages and how they are delivered to the server in response to the
command that the server has sent to the device(s) by requesting the device(s) to respond with.
4. Configuration
Before a device starts being operated, its parameters should be set first. This chapter shows the string to be sent to
device.
In practice, configuration can be made more efficiently with SyncTrak, i.e. a setting tool provided by Suntech.
Once a device receives a command from the server, it gets back to the server with a relevant response. Device also
changes some parameters (if it is required to do so) or takes an action as instructed below as per the command sent
by the server.
The following table shows how and what parameters are required to be set so that the device can be connected with
network. As shown in the bottom part of this table, an <Example> of [command] and [response]are made in string
respectively when the configuration for the networking is completed.
0: PAP(NO in SyncTrak).
1: CHAP(YESinSyncTrak).
A: Automatic GPRS set.
In this case, parameters for APN, USER_ID and
USER_PWD field should remain empty.
APN String Access Point Name.
USER_ID String ID for GPRS Access.
USER_PWD String Password for GPRS Access.
SEVER_IP String Server IP Address.
SEVER_PORT String Server Port.
B_SEVER_IP String IP Address of Backup Server.
B_SEVER_PORT String Port of Backup Server.
SMS_NO String Phone number that will receive the SMS report sent by the
device.
[command] ST300NTW;100850000;02;0;internet;;;111.111.111.111;8600;;;;
[response] ST300NTW;Res;100850000;010;0;internet;;; 111.111.111.111;8600;;;;
ST300NTW;Res;100850000;010;A1;tim.br;tim;tim; 111.111.111.111;8600;;;;
<Note>:
** If network does not require User ID and Password, these fields should remain empty.
If you set the device to Automatic GPRS Set, the device will automatically set the parameters for GPRS with the
data available on the inserted SIM card.
For instance, if Airtel SIM is inserted, the device will set AUTH to 0, APN to airtelgprs.com, USER_ID and
USER_PASS to empty respectively.
And then, the device reports response string after adding real GPRS parameters, if Automatic GPRS Set is
selected.
DNS
SERVER_IP and B_SERVER_IP field can be filled with direct IP address (for example 111.111.111.111) or
domain name (for example, suntechint.com). If this field is written by domain, the device will find real IP address
by DNS and sends reports to IP address.
Device responds to the command(s) with the relevant report or response periodically at a time interval or at a travelled
distance interval of the vehicle that has already been predefined by user. Such are response sent back to the server
includes SMS message (if the device user has already configured SMS messaging functionality). The following table
shows how to set those parameters.
In bottom part of the table, the following table also shows how and what parameters should be set to utilize functions
like:
Angle Report, that is used for displaying the historic path more accurately or saving network cost while the
vehicle is driving on straight roads for long time.
FIFO or LIFO, should be selected to determine a sequential order if buffer of the device is completely full
of reports. For more information, take a look at the description made in the bottom part of the table below.
Range: 0 ~ 86400.
If 0, a report in parking will be sent only one time when vehicle
starts being parked.
T2 String Sec Interval to be set to send a Status Report in driving mode:
Range: 0 ~ 60000.
Range: 0 ~ 9999.
[command] ST300RPT;100850000;02;180;120;60;3;0;0;0;0;0
[response] ST300RPT;Res;100850000;010;180;120;60;3;0;0;0;0;0
<Note>:
** If a reporting interval is set with a big number, the network may disconnect GPRS connection because GPRS
communication does not make a progress for a long time. So, the device may not receive the command via GPRS.
T4 will be used to prevent such a disconnection by sending a short data for short time.
** The Keep Alive report is sent only when the device has no data to be sent for the time of the interval T4.
In order to set these parameters properly, read carefully the contents and <Example> along with <Note> described
in the bottom inside the table below.
15 = Anti-Theft Button 2.
Default = 3.
Only the device that includes voice option (audio circuit) can
be set to Call1 Button or Call2 Button.
IN2_TYPE 0 ~ 15 / 18 ST300P
14 = TPS (It works on ST300P, if the parameter is fixed to
the Input2)
ST300V
14 = TLS (It works on ST300V, if the parameter is fixed to
the Input2)
Default = 2.
Only the device that includes voice option (audio circuit) can
be set to Call1 Button or Call2 Button.
0 = Falling Edge.
1 = Rising Edge.
2 = Both Edge (Falling & Rising).
3 = Panic Button.
4 = Call1 Button.
5 = Call2 Button.
6 = ADC.
7 = Anti-Theft Button.
11 = Door Sensor.
15 = Anti-Theft Button 2.
Default = 2.
Only the device that includes voice option (audio circuit) can
be set to Call1 Button or Call2 Button.
ST300P
14 = TPS (It works on ST300P, if the parameter is fixed to
the Input2)
ST300V
14 = TLS (It works on ST300V, if the parameter is fixed to
the Input2)
Others :
Same as IN1_TYPE.
Default = 2.
IN1_CHAT String 100ms Input1 chattering time:
Range: 0 ~ 9999.
Default = 3 sec.
OUT1_TYPE 0 ~ 5 / 0 = GPIO.
8 ~ 9 1 = immobilizer.
2 = Immobilizer & Auto active.
Auto Active means that immobilizer is activated
automatically when the vehicle starts being parked.
3 = Pulse.
4 = LED Out for indicating Call Status. Refer to 9-2-3 of this
document for more detail.
5 = Buzzer.
8 = Immobilizer 2.
9 = Auto Immobilizer 2.
OUT2_TYPE 0 ~ 5 / Same as OUT1_TYPE.
8 ~ 9
In case of 300F
OUT2_TYPE shall be set as GPIO.
OUT1_ACTIVE 0 or 1 0 = Open when out1 is active.
1 = GND when out1 is active.
OUT2_ACTIVE 0 or 1 0 = Open when out2 is active.
1 = GND when out2 is active.
In case of 300F
OUT2_ACTIVEshall be set to 1.
PULSE1_NO String Pulse number when the out1 type is set to pulse:
Range: 0 ~ 9999.
If Pulse Number is 9999, pulsing runs permanently.
PULSE1_ON String 100ms Active time of Pulse1:
Range: 0 ~ 9999.
It should be set with an even number.
PULSE1_OFF String 100ms Inactive time of Pulse1:
Range: 0 ~ 9999.
It should be set with an even number.
PULSE2_NO String Pulse number when out2 type set to pulse:
Range: 0 ~ 9999.
If Pulse Number is 9999, pulsing runs permanently.
PULSE2_ON String 100ms Active time of pulse2:
Range: 0 ~ 9999.
It should be set with an even number.
PULSE2_OFF String 100ms Inactive time of Pulse2:
Range: 0 ~ 9999.
It should be set with an even number.
Same as IN1_TYPE.
Range: 0 ~ 9999.
If 0, Input 4 is not checked.
When the extra event IN4 is not available, it should be 0.
IN5_CHAT String Chattering time when extra event IN5 is available:
Range: 0 ~ 9999.
If 0, Input 5 is not checked.
When an extra event IN5 is not available, it should be 0.
BAUD 0 ~ 6 It is available when RS232 is supported for extra events.
0 = No use.
1 = 4800bps.
2 = 9600bps.
3 = 19200bps.
4 = 38400bps.
5 = 115200bps.
6 = 2400bps.
In case of ST300F
<Note>:
Suntech International Ltd. Confidential Document
Doc. Title Author Page of Pages
** If IGNITION is set to 0, the device doesnt check driving or parking state of the vehicle. It always reports status
string under parking mode, and cannot support Parking Lock and the Service which enters Sleep or Deep Sleep
automatically when the vehicle is parked.
** If IGNITION is set to 2, the device checks if it is in driving status or in parking status of the vehicle with voltage
range of vehicles battery. We named it as Virtual Ignition by power. Virtual ignition by power runs when the
device is installed on a real vehicle and it may need to adjust the voltage range for special vehicle. For setting
method, please refer to4-6 of this document.
** In case of pulse, pulse time may have tolerance about dozens of ms.
**Immobilizer, LED Blink line and Buzzer type cannot set both OUT1 and OUT2 simultaneously.
** In a case that an event is set to door sensor, the Active State means that the door is open.
The accumulated time of driving (named as HMETER) is written in the string of the report that the device sends
to its server. Normally, HMETER is counted while the vehicle is driven (when the ignition line is on).
If you want to utilize the functionality of HMETER under specific conditions, , you should set an input line to
HMETER for specifying those driving conditions.
Here is an example of how and in what situation you can utilize function of the HMETER input:
There might be a user of a GPS device who wants to know for how long time a companys vehicle (which is
equipped with a GPS device) has been driven for the purpose of the company. However, sometimes, this
vehicle might be used for other purpose. It means that driving time of this vehicle can be categorized by 2 cases
as follows:
.
Case A
Case B
the driver personally wanted to use the vehicle for his family not for the company.
The device models (i.e. only 3 models such as ST300A, ST300H and ST300K) of Suntech are able to measure
the driving time of Case A if device model was already configured properly by using a parameter, which is
HMETER.
The device can send its server a report to inform the user about how many hours the vehicle has been driven in
Case A if the device was already configured with the HMETER Parameter. To utilize the function of
HMETER properly, the vehicle should be equipped with a control switch for the HMETER function and the
driver:
Data of the <Driving time of Case A> is included in the string of the report that the device sends its server.
How does the device check the number of driving hours of Case A?
Step 1. User should configure the device by setting one of 3 Inputs (i.e. Input 1, Input2 and Input3) of
HMETER Parameter.
Step 2. If user of the device wants to use the function of HMETER in driving the vehicle, he should
turn on the switch to control the function.
Step 3. The device calculates the number of the driving hours of Case A not by utilizing Ignition
Line, but by sensing Ground Line of the Input which was already set to make HMETER function.
In order to set these parameters properly, read carefully the contents and <Example> along with <Note> described
in the bottom inside the table below.
CALL_MO1 CALL_MO2
<Note>
** When SMS or Call numbers are not set, that field should be empty.
In order to set these various parameters properly, read carefully the contents and <Example> along with <Note>
described in the bottom inside the table below. In setting a new device, the SyncTrak will show you detailed
explanation on how to set parameters relating to these Fields.
0 = KEEP_CON.
1 = KEEP_DISCON.
0: Disable.
1: Enable, One packet can include up to 5 normal reports
<Note>:
** Function of M_SENSOR can be used with the model that has motion sensor.
If shock or collision detection is enabled and if there is shock or collision on the vehicle, the device sends a report
to the server.
** If these parameters are customized for your device, please follow the instructions customized for you instead
of using this table.
CON_TYPE
1. KEEP_CON: Device always keeps TCP connection and can receive a command via GPRS.
2. KEEP_DISCON: Device maintains TCP connection while the device is sending the data to the server.
Within 3 minutes after sending all the data that the device has been keeping, the device disconnects
GPRS and TCP connection as there is no data to be sent any more inside the device. In this case, the
device cannot receive a command via GPRS.
Group Send
Device stores data if the vehicle is in no GPRS area. And, the vehicle moves to GPRS available area, device
starts sending the stored normal data.
If the Group Send option is enabled, the device sends the server 5 reports at one time as one bundle.
The Group Send is useful to speed up sending.
M_Sensor
Shock: Device sends an Alert report when ignition is OFF
LOG Data
When you run the SyncDown program, please set the port to USB and click Download in order to
store the data in your PC
FUEL_LV_ALT
This value is for ALT reports when the fuel level is changed fast.
If the fuel level is decreased upper FUEL_LV_ALT, ST300F sends ALT 73 report.
If the fuel level is increased upper FUEL_LV_ALT, ST300F sends ALT 80 report (Omnicomm sensor
only).
4-6. Voltage control parameters
In order to set these parameters properly, read carefully the contents and <Example> along with <Note> described
in the bottom inside the table below. In setting a new device, the SyncTrak will give you detailed explanation on how
to set parameters relating to these Fields.
Default = 0.
<Example>
[command] ST300MBV;100850000;02;0;22;19;8.00;18.00;0;0
[response]ST300MBV;Res;100850000;122;0;22;19;8.00;18.00;0;0
<Note>
1. IGNDET_H and IGNDET_L are 0, device check parking and driving automatically.
In order to set these parameters properly, read carefully the contents and <Example> along with <Note> described
in the bottom inside the table below. In setting a new device, the SyncTrak will give you detailed explanation on how
to set parameters relating to these Fields.
COLL_THRES
<Note>
* As for the shock level, it is recommended that the user should set to 0.04. If the motion threshold is higher than
0.04, the sensor will be too sensitive to make a proper detection on shock.
This table shows how a device user can set parameters for circular geo-fencing. In order to set these parameters
properly, read carefully the contents and <Example> along with <Note> described in the bottom inside the table
below. In setting a new device, the SyncTrak will show you detailed explanation on how to set parameters relating
to these Fields.
In order to set these parameters properly, read carefully the contents and <Example> along with <Note> described
in the bottom inside the table below. In setting a new device, the Additional Parameter section available in the
SyncTrak program will show you detailed explanation on how to set parameters relating to these Fields.
UDP_
HDR DEV_ID VER SVR_TYPE B_SVR_TYPE DEV_PORT
ACK
Reserved SAT_OUT SAT_DELAY SAT_RS232 BAT_VOLT_LIMIT Reserved
T: TCP.
U: UDP.
UDP_ACK 0 ~ 3 ACK from the server when UDP is used:
0: No Use.
0 = Disable.
In case of 300F
SAT_OUTshall be set to 0 (Disable).
SAT_DELAY String Sec Time length delayed inactivating the output after losing the
GSM/GPRS signal:
Range: 0 ~ 86400.
Please refer to the below <Note>, Control of Satellite Modem.
SAT_RS232 String 0 or 1 Send reports through RS232 when SAT_OUT is activated:
0: Disable.
1: Enable.
<Caution>: This function uses only for device which
supporting RS232.
In case of 300F
SAT_RS232shall be set to 0 (Disable).
SAT_T1 String Sec Interval to be set to send a Status Report in parking mode in
no GPRS and no GSM:
Range: 0 ~ 86400.
If 0, a report in parking will be sent only one time when vehicle
starts being parked.
SAT_T2 String Sec Interval to be set to send a Status Report in driving mode no
GPRS and no GSM:
Range: 0 ~ 60000.
<Example>
[command] ST300ADP;205989898;02;U;T;2;8700;0;4;1;0;180;180;2.56;0;1;1;1;1
[response] ST300ADP;Res;205989898;630;U;T;2;8700;0;4;1;0;180;180;2.56;0;1;1;1;1
<Notes>
ACK in case of UDP
UDP is protocol that does not check if the data has been transmitted successfully. So, the device checks
completion of sending with ACK depending on UDP_ACK type.
ACK is sent by server when the server receives the data.
If the ACK has not been received for more than 2 minutes after being sent, the device recognizes the data has
not been reached to the server and sends the data again.
Device users are recommended to set ACK_TYPE to 1 to confirm that all the data can be transmitted
successfully.
<Note>
O: Necessary
X: Not necessary
SAT_OUT, SAT_DELAY and SAT_RS232 are used for a connected satellite modem. In this case, the device can
communicate with its server instead of the device under the situation of no GSM/GPRS.
1. If no GSM/GPRS situation continues for more than SAT_DELAY, the device activates the related output
pursuant to SAT_OUT.
2. If SAT_OUT is activated, the satellite modem detects no GSM situation and automatically starts
communication by itself.
3. If SAT_RS232 is enabled, the device sends STT string which has 0 in MSG_TYPE field through RS232.
And then, it sends all the reports except for STT and Alive.
4. If the GSM signal is recovered, the device deactivates the output line related with SAT_OUT. If
SAT_RS232 is enabled, STT string which has 0 in MSG_TYPE field is sent prior to the deactivation.
5. The ST340R model can support only 0, 1, 2 of the SAT_OUT.
DPA2
CRR_EN, SPD_EN, SPD_TIME, HIST_EVT fields are appeared in ST300A, ST300D, ST300H. Other devices
are reserved.
Satellite Interval
SAT_T1, SAT_T2 fields are appeared in ST300R. Other devices are reserved.
This table shows how to set the parameters related with the reporting intervals. In order to set these parameters
properly, read carefully the contents and <Example> along with <Note> described in the bottom inside the table
below. In setting a new device, the New Parameter Setting section available in the SyncTrak program will show
you detailed explanation on how to set parameters relating to these Fields.
0: Disable.
Range: 1 to 180 degrees.
RPT_TYPE String 0 or 1 How to set a sequential rule of storing/erasing reports if buffer
of the device is full of reports un-sent to the server:
Range: 0~ 60000.
0 = Disable.
1 ~ 4 = enabled jamming detection and if detected first, check
assist functions and then triggered by JAM_DET mode as
follows.
JAM_DET Alert Active Immob. Active Buzzer
1 O X X
2 O O X
3 O X O
4 O O O
Default: 0.
JAM_CHK_DIST 0 ~60000 Meter This is complementary to the detection function of device
described above on the GPRS jamming by utilizing a distance
value as a parameter when jamming is done.
Range: 3~30.
Default: 5.
VI_ON_DELAY String Sec. Delay time for Motion Virtual Ignition On:
Range: 3~999.
Default: 10.
VI_ON_PERCENT String % Percent for Motion Virtual Ignition On:
Range: 30~100.
Default: 70.
VI_OFF_THRES String 1/255G Threshold value for Motion Virtual Ignition Off:
Range: 3~30.
Default: 5.
VI_OFF_DELAY String Sec. Delay time for Motion Virtual Ignition Off:
Range: 3~999.
Default: 10.
VI_OFF_PERCENT String % Percent for Motion virtual Ignition Off:
Range: 30 ~ 100.
Default: 70.
HBM 1 Should be 1
<Example>
[command] ST300NPT;100850000;02;0;0;10;0;0;500;300;5;10;70;5;10;70;0
[response] ST300NPT;Res;100850000;515;0.0;0;10;0;0;500;300;5;10;70;5;10;70;1
JAM_CHK_DIST and & JAM_CHK_TM are complementary to jamming detection to avoid false detection.
At least, we recommend that users of our device should utilize the JAM_CHK_DIST for safety purposes.
If you use the 2 (two) functions, it can detect the following two cases of jamming:
In a case that all of the complementary functions are disabled, device starts working according to the jamming
mode (JAM_DET mode) after detecting the jamming. In such a case, a false detection might be made in an area
having a weak GSM connectivity or in an area having a strong radio.
<NOTE>
The ST340R model can support only 0~ 3 of the JAM_DET
This table shows how to set the parameters related with telemetry. In order to set these parameters properly, read
carefully the contents and <Example> along with <Note> described in the bottom inside the table below. In setting
a new device, the New Parameter Setting section available in the SyncTrak program will show you detailed
explanation on how to set parameters relating to these Fields.
Range: 3~999.
Recommended value: 10.
CHK_GEAR_RPM String RPM RPM value to judge alert situation of CHK_GEAR
If not 0, the device alerts when the driver stops with ignition
on during more MAX_REST_TIME.
Suntech International Ltd. Confidential Document
Doc. Title Author Page of Pages
<Notes>
This setting works only on ST300H, ST300A and ST300K. ST300A and ST300K use only
DID_OUT_CTRL/MASTER_ADD/MASTER_REMOVE / MAX_STOP_TIME field, other fields should be 0.
A. Travel Event Report to prevent from driving vehicle down by positioning gear stick in neutral
In order to save fuel for vehicle, there are some drivers who drive vehicle by shifting the gearbox stick into the
neutral position, especially, while the vehicle is running from a high area down (i.e. a sliding-down slope)
toward a low altitude area.
It is very dangerous to drive a vehicle in such a way and such a bad driving behavior should be prohibited. The
variant models of the ST300 Series specified above have a useful detection function, named Dead Center
Checking, which prevents drivers from doing such a bad driving behavior.
This function can be operational after checking the values of the relevant parameters such as :
CHK_GEAR(checking enable/disable),
CHK_GEAR_RPM
CHK_GEAR_TIME
If a vehicle has been being driven under a driving condition of lower than a preset value of
CHK_GEAR_RPM for a longer time period than the present time period of CHK_GEAR_TIME, this feature
assumes that the vehicle is driven for this time period as a bad driving behavior (i.e. driving vehicle down with
the gear being positioned <neutral>) and makes a report, which is named as Travel Event Report. In that
case, such a bad driving time is reported to the server of the device.
User of device can save fuel in driving the vehicle by utilizing Travel Event Report if he/she pre-sets the 2
parameters (ECO_MAX_RPM and ECO_MIN_RPM) in order to make a range.
After value of the 2 parameters is pre-set and when driving is over, the device will report to its server about the
driving time by 3 categories:
Category A: How long the vehicle has been driven covering ECO_MAX_RPM and
ECO_MIN_RPM
Category B: How long the vehicle has been driven under the ECO_MIN_RPM
Category C : How long the vehicle has been driven over the ECO_MAX_RPM
This chapter shows how to add the driver ID to the registration table as shown on the bottom part of this chart. If
a vehicle is driven without processing to register driver ID in proper way, this feature assumes that the vehicle is
driven by non-registered driver. In this case, the device can activate immobilizer.
HDR DEV_ID VER DID_POS (1st) DID (1st) DID_POS (last) DID (last)
After receiving this command, the device will save the new driver ID as shown in the table below.
1st position 00001000000000 2nd position 00002000ABCDEF
rd
3 position 4th position
5th position 00003333AAAAAA
The table below shows how to remove the driver IDs that you want to eliminate.
HDR DEV_ID VER DID_POS
This table shows how a device user can set parameters for circular geo-fencing. In order to set these parameters
properly, read carefully the contents and <Example> along with <Note> described in the bottom inside the table
below. In setting a new device, the SyncTrak will show you detailed explanation on how to set parameters relating
to these Fields.
[command] ST300DPA;600850000;02;1;0.0;30.0;100.0;70.0;100.0;1;10
[response] ST300DPA;Res;600850000;010;1;0.0;30.0;100.0;70.0;100.0;1;10
CAN bus (CAN) is the name given to the communication network in a vehicle that is used for transferring
information between the various ECUs (i.e.: Electronic Control Units).Once users of CAN (i.e.: Controller Area
Network) model device configure the device based on the information about various factors as listed in the Fields
as shown in the following table (e.g. Engine Speed, Odometer, Total Fuel, Vehicle Speed, Engine Coolant
Temperature, etc.) and if the vehicle exceeds the pre-set limits, the device sends report(s)to the server.
The following table shows how to set the parameters based on the various information provided through ECU of
the vehicle:
HDR DEV_ID VER MODE EVS SPD ET OIL_P ERPM SHB ADD_CLAIM
0 = Disable.
1 = Enable
Default : 0
EVS String Km/h Exceed Vehicle Speed : 0-250
Default : 120
Default : 0
ERPM String rpm Limit value for Engine RPM : 0~8031
Default : 0
<Example>
[command] ST300ECU;100850000;02;1;120;100;200;100;8000;14.3;0
[response] ST300ECU;Res;100850000;02;1;120;100;200;100;8000;14.3;0
[response] ST300ECU;Res;100850000;02;CE
<Note>
If the device cannot initialize the MCU for J1939, it will be reporting error such as CE.
The following table shows how to get information about the parameters of commands relating to ECU.
HDR DEV_ID VER MODE EVS SPD ET OIL_P ERPM SHB ADD_CLAIM
<Example>
[command] ST300GES;100850000;02
[response] ST300GES;Res;100850000;02;1;120;100;200;100;8000;14.3;0
The following table shows how to get information about ECU (or ECM: Electronic Control Module)
compliant with J1939
HDR Res DEV_ID SW_VER DATE TIME CELL LAT LON SPD CRS SATT
In order to set these various parameters properly, read carefully the contents and <Example> along with <Note>
described in the bottom inside the table below. In setting a new device, the SyncTrak will show you detailed
explanation on how to set parameters relating to these Fields.
ST300A / ST300K
HDR DEV_ID VER PANIC_SND_DIR LIMIT_STOP_TIME CMD_RES_DIR TEMP_SENSOR
0: Send to server
1: Send to SMS
2: Send to server and SMS
LIMIT_STOP_TIME String Min Device sends this alert if the vehicle does not move for a
time interval (i.e. LIMIT_STOP_TIME) in a status of Ignition
On, which means that the engine is being operated. If this
status exceeds such a time interval, an alert is made by the
device automatically. This function is operational only if you
have already set the Event Parameter to Use Ignition Line.
Range : 0 ~ 1440
CMD_RES_DIR String How to set direction of Command response
0: No Use
1: Server
2: SMS
TEMP_SENSOR String Using the Temperature sensor (**)
0: No Use
1: Use
ENCRYPTION String Using the Encryption of Reporting data (**)
0 :No Use
1: Use
ENCRYPTION_KEY String Secret Code to encrypt the reporting message.(**)
<Example>
[command] ST300LTM;100850000;02;1;2;0
[response] ST300LTM;Res;100850000;010;1;2;0
ST300A / ST300K
[command] ST300LTM;;02;0;0;0;1
[response] ST300LTM;Res;600850779;557;0;0;0;1
<Note>:
** TEMP_SENSOR : Only 2 device models (i.e. ST300A, ST300K) support function of the temperature sensors.
The firmware version number of the ST300A / ST300K, which is higher than 557, supports function of the
temperature sensor.
** ENCRYPTION , ENCRYPTION_KEY : This function is optionally available only for the customers of the
ST340LC model who want to use the encryption functionality.
** ENCRYPTION_KEY: The input code length must consist of 32 digits and the input character that users can
use ranges from 0 to 9, a to f, A to F
** ENCRYPTION: If you want to use the encryption function on your device, first of all, please contact engineers
of Suntech via e-mail at info@suntechint.com
Each polygonal geo-fence group setting can make a sequential progress only with the sequential command packet.
The command flow is as below.
Case 1:
In the <Case 1> that the parameters have already been set
as above, the device sends the report at an interval of 30
seconds as soon as the vehicle gets into the pre-set geo-
fence territory (i.e. a vehicle in a driving mode). The device
will send a report every 120 seconds as soon as the vehicle
gets out of the geo-fence territory.
Case 2:
In the <Case 2> that the parameters have already been set
as above, the device sends the reports every 120 seconds
as long as the vehicle is in a mode of driving. It means that,
in Case 2, the device sends the report at an interval of 120
seconds wherever the vehicle may be.
RPT_INTERVAL_IN String Sec Interval for sending status report in parking
_PARKING
Range : 0 ~ 86400
Range : 0 ~ 300.00
Not Used 0 Should be 0
Not Used 0 Should be 0
Not Used 0 Should be 0
Not Used 0 Should be 0
GEO_LABEL String Geo-fence label
Range: 0 ~ 16 character.
<Note>
This command can be sent as an independent packet.
Please refer to the following example :
ST300PLG;100850000;02;1;1;1;1;3600;60;1;80.5;75;28.5;2;30.33;1;position 1
<Note> :
[command] ST300PLG;100850000;02;1;1;1;0
In a case that the Group1 has 8 positions, the followings show how such 4 sets of command/response, for
example, react:
[command] ST300PLG;100850000;02;1;4;1;1;3600;60;1;80.5;75;28.5;2;30.33;1;position 1
[response] ST300PLG;Res;100850000;104;1;4;1;1;3600;60;1;80.5;75;28.5;2;30.33;1;position 1
[command] ST300PLG;100850000;02;2;4;1;126.885545;37.480648;126.887466;37.478162;126.885095;
37.477506;126.884279;37.479005;126.883764;37.478885
[response] ST300PLG;Res;100850000;104;2;4;1;126.885545;37.480648;126.887466;37.478162;126.885095;
37.477506;126.884279;37.479005;126.883764;37.478885
[command]
ST300PLG;100850000;02;3;4;1;126.884773;37.476655;126.888517;37.477710;126.886328;37.480520;;;;
[response] ST300PLG;Res;100850000;104;3;4;1;126.884773;37.476655;126.888517;37.477710;
126.886328;37.480520;;;;
[command] ST300PLG;100850000;02;4;4;1;1
[response] ST300PLG;Res;100850000;104;4;4;1;1
The followings show how 2 sets of command/response, for example, react if the Group1 has no positions
(if all the positions are erased):
[command] ST300PLG;100850000;02;1;2;1;0;0;0;0;0;0;0;0;0;0;0
[response] ST300PLG;Res;100850000;104;1;2;1;0;0;0;0;0;0;0;0;0;0
[command] ST300PLG;100850000;02;2;2;1;0
[response] ST300PLG;Res;100850000;104;2;2;1;0
A response string which comes after GROUP_ID consists of the following fields as shown in the table below
ENABLE
ALLOW_ RPT_INTERVAL_ RPT_INTERVAL_ ALIVE_INTERVAL_
SPEED_LIMIT
PARAM IN_PARKING IN_DRIVING IN_PARKING
BUZZER_SPEED
ACCEL_SPEED ACCEL_TIME DECEL_SPEED DECEL_TIME
_LIMIT
POS_CNT GEO_LABEL
[command] ST300PLC;100850000;02;GetPolygonGroupPos;1
[response]
ST300PLC;Res;100850000;104;GetPolygonGroupPos;1;1;10;37.509683;126.882037;37.508841;126;880202;3
7.507981;126.80953;37.508926;126.882616;37.508887;126.901611
ST300PLC;Res;100850000;104;GetPolygonGroupPos;1;2;10;37.509683;126.882037;37.508841;126;880202;3
7.507981;126.80953;37.508926;126.882616;37.508887;126.901611
A response string which comes after GROUP_ID consists of the following Fields as shown in the table below.
TOTAL_
REPORT_NO LONGITUDE1 LATITUDE1 LONGITUDE2 LATITUDE2
REPORT_NO
LONGITUDE3 LATITUDE3 LONGITUDE4 LATITUDE4 LONGITUDE5 LATITUDE5
[command] ST300PLC;100850000;02;ErasePolygonGroup;1
[response] ST300PLC;Res;100850000;104; ErasePolygonGroup;1
A response string which comes after GROUP_ID consists of the following Fields as shown in the table below.
OUT_PROTECT ALIVE_RPT_INTERVAL_OUTSIDE
In order to set these various parameters properly, read carefully the contents and <Example> along with <Note>
described in the bottom inside the table below. In setting a new device, the SyncTrak will show you detailed
explanation on how to set parameters relating to these Fields.
[command]
ST300TAS;100850000;02;28E4D95F060000D5;+24.0;+20.0;28F5573B050000AA;+26.0;+22.0;28C4D95F0600
00C5;+12.0;-10.0
[response]
ST300TAS;Res;600850779;557;28E4D95F060000D5;+24.0;+20.0;28F5573B050000AA;+26.0;+22.0;28C4D95
F060000C5;+12.0;-10.0
<Note>:
** This function works only on ST300A and ST300K.
** An alert is sent to the server of the device when the temperature is greater than the pre-set value or is lower
than the pre-set value of the temperature.
If user of device wants to use a coin machine, the user should set this Parameter (Pulse Per Value).
The user should also set the coin machine as well.
[command]
ST300CMP;100850000;02;100
[response]
ST300CMP;Res;600850779;557;100
<Note>:
** This function works only on the ST300B model to support the functionality of Coin Machine.
** If you want to count various coins by coin value such as 10 Peso Coin, 50 Peso Coin, 100 Peso Coin, and
500 Peso Coin, please set this function as follows:
Step 2. You should set a pulse for the coin machine by coin value as follows :
a 10 Peso coin 1
a 50 Peso coin 5
a 100 Peso coin 10
a 500 Peso coin 50
The ST300B which has been set as above will count every pulse in Ignition ON mode, whenever you insert the
coins to Coin Machine.
For example, if you insert a 10 Peso coin and a 50 Peso coin, the Coin Machine makes 6 pulses. And then,
the device multiplies 6 pulses by 10, which is the value of PULSE PER VAL. In other words, you multiply 6 by
10, which is equal to 60.
6 x 10 = 60
By completing to set the coin machine and the device (ST300B) as above, the device is able to report 60 when
a STT Report is made.
These parameters need to be set if user wants to enable the device to track moving of vehicle along the routes
predefined by the user.
In order to set these parameters properly, read carefully the contents and <Example> along with <Note> described
in the bottom inside the table below.
Once these parameters are set properly, the device starts tracking vehicle and alerting in case the device gets out
of the predefined route(s).
[command] ST300CTR;100850000;02;1
[response] ST300CTR;Res;100850000;010;1
[command] ST300CTR;100850000;02;R;1
[response] ST300CTR;Res;100850000;010;R0 (When tracking is disabled.)
ST300CTR;Res;100850000;010;R1 (When the tracking is enabled.)
In order to set these parameters properly, read carefully the contents and <Example> along with <Note> described
in the bottom inside the table below.
HDR DEV_ID VER TR_NO_ID LAT1 LON1 GAP1 LAT2 LON2 GAP2
GAP1 0 meter Tolerance of the course ranging from the current position (POS
Or ID) to the next position (POS ID+1).
50 ~ 60000
If 0, do not check the course ranging from the current position
to the next position.
LAT2 String Latitude position of tracking POS ID+1.
LON2 String Longitude position of tracking POS ID+1.
GAP2 0, meter Tolerance of the course from the current position (POS ID+1) to
50 ~ 60000 the next position (POS ID+2).
<Note>
** This Command can cover maximum 10 (ten) geographical positions per command. If there is a very long course
requiring more than 10 positions to be set for the course, the 2 nd Command should be made to cover the 11th
position up to the 20th position. If the course needs more than 20 positions, the way how to set such positions with
the 3rd Command is same as how the 2nd command has set number of the positions.
** If TR_NO_ID is 1, all tracking positions that have already been set to the device will be erased and new
positions starts being set.
Read carefully the contents and <Example> along with <Note> described in the bottom inside the table below
HDR DEV_ID VER
<Note>
** Response can be divided into several strings; but not into more than 10 positions in each string. Also, a
response sting may be cut if next position starts new route. Response fields are as shown below.
Suntech International Ltd. Confidential Document
Doc. Title Author Page of Pages
HDR RES DEV_ID VER CONT TR_NO_ID LAT1 LON1 GAP1 LAT2 LON2 GAP2
CONT may be 0 or1, When next string is followed, CONT displays with 1. When the string is last, CONT
displays with 0.
6. Reporting to server
Once a device is configured properly and registered on its server for operation, it sends reports to the server (or
sends SMS messages to cellular phone whose number is predefined) either in response to the commands made by
the server or as per the way how the device has been configured to respond to its server.
This chapter shows the strings of each report, so that server could understand the contents. One report can be issued
in either of two types, normal string and zip string, both of which are described below.
Also, note that we take an <Example> and make a <Note> on the bottom part of each report in this chapter to help
the users understand better what contents are included in the report. So, it is highly recommended that users should
read the whole parts of the reports very carefully.
This report (Status Report) is sent to the server periodically as defined by user to configure status report if
conditions for issuing the report are met. The following two (2) tables show how one report can be made in 2
different types such as in string and in zip.
6-1-1. Normal
In case of ST300V
Maximum speed between before STT report and current STT report.
TPS_S1_IN The number of people riding on the bus to counting by sensor 1.
Initialized only command.
TPS_S1_OUT The number of people get off the bus to counting by sensor 1.
Initialized only command.
TPS_S2_IN The number of people riding on the bus to counting by sensor 2.
Initialized only command.
TPS_S2_OUT Number of people get out the bus to counting by sensor 2.
Initialized only command.
<Examples>
ST300
ST300STT;100850000;01;010;20081017;07:41:56;00100;+37.478519;+126.886819;000.012;000.00;9;1;0;15.3
0;001100;1;0072;0;4.5;1
ST300V
ST300STT;100850000;10;010;20081017;07:41:56;00100;+37.478519;+126.886819;000.012;000.00;9;1;0;15.3
0;00110000;1;0072;0;4.5;1;12.35;0;0
ST300A
The following string should be created if user of the ST300A does NOT use the optional
function of temperature sensing.
ST300STT;205989898;07;635;20150902;09:08:16;01454;+37.479300;+126.887852;000.011;000.00;8;1;0;12.2
5;000000;1;0000;000.083;0;000218;0.0;0;0.00;4.23;4.26;012497F1160000;1;000.047
The following string should be created if user of the ST300A selects the optional function
of temperature sensing and uses 3 units of the temperature sensor.
ST300STT;205989898;07;635;20150902;09:08:16;01454;+37.479300;+126.887852;000.011;000.00;8;1;0;12.2
5;000000;1;0000;000.083;0;000218;0.0;0;0.00;4.23;4.26;012497F1160000;1;28E4D95F060000D5:+23.5;28F5
573B050000AA:+23.8;28BBE721050000A0:+24.3;000.047
The following string should be created if user of the ST300A selects the optional function
of temperature sensing and uses 2 units of the temperature sensor.
ST300STT;205989898;07;635;20150902;09:08:16;01454;+37.479300;+126.887852;000.011;000.00;8;1;0;12.2
5;000000;1;0000;000.083;0;000218;0.0;0;0.00;4.23;4.26;012497F1160000;1;28E4D95F060000D5:+23.5;28F5
573B050000AA:+23.8;:;000.047
The following string should be created if user of the ST300A selects the optional function
of temperature sensing and uses only one (1) unit of the temperature sensor.
ST300STT;205989898;07;635;20150902;09:08:16;01454;+37.479300;+126.887852;000.011;000.00;8;1;0;12.2
5;000000;1;0000;000.083;000218;0.0;0;0.00;4.23;4.26;012497F1160000;1;28E4D95F060000D5:+23.5;:;:;0;00
0.047
ST300H
ST300STT;205787852;04;639;20150903;05:19:20;01454;+37.479322;+126.887835;000.000;000.00;10;1;1;12.
43;000000;1;0001;000266;0.0;1;0;012497F1160000;1;000.180;0;000.037
ST300C
ST300STT;600850802;11;999;20141212;09:47:21;04600;+37.479370;+126.888552;000.120;000.00;3;1;10660;
12.25;000000;2;0036;002068;0.0;1;3.10;302799;0.00;215.86
ST300K
The following string should be created if user of the ST300K does NOT use the optional function
of the temperature sensor.
ST300STT;600850779;12;560;20150501;02:28:22;01454;+37.479307;+126.887838;000.002;000.00;10;1;17;13
.54;100000;2;0026;001410;0.0;1;0.00;0;0.00;0.00;01488BF1160000;0
The following string should be created if user of the ST300K selects the optional function of
temperature sensing and uses the 3 temperature sensors
ST300STT;600850779;12;560;20150501;02:28:22;01454;+37.479307;+126.887838;000.002;000.00;10;1;17;13
.54;100000;2;0026;001410;0.0;1;0.00;0;0.00;0.00;01488BF1160000;0;28E4D95F060000D5:+23.5;28F5573B0
50000AA:+23.8;28BBE721050000A0:+24.3
The following string should be created if user of the ST300K selects the optional function
of temperature sensing and uses 2 temperature sensors.
ST300STT;600850779;12;560;20150501;02:28:22;01454;+37.479307;+126.887838;000.002;000.00;10;1;17;13
.54;100000;2;0026;001410;0.0;1;0.00;0;0.00;0.00;01488BF1160000;0;28E4D95F060000D5:+23.5;28F5573B0
50000AA:+23.8;:
The following string should be created if user of the ST300A selects the optional function
of temperature sensing and uses only one (1) temperature sensor.
ST300STT;600850779;12;560;20150501;02:28:22;01454;+37.479307;+126.887838;000.002;000.00;10;1;17;13
.54;100000;2;0026;001410;0.0;1;0.00;0;0.00;0.00;01488BF1160000;0;28E4D95F060000D5:+23.5;:;:
ST300P
ST300STT;205123456;13;430;20141222;01:58:24;01454;+37.479530;+126.887844;000.000;000.00;5;1;8;12.1
4;10110000;2;0002;000046;0.0;0;10;3
ST300F
ST300STT;600850805;14;453;20141222;03:01:49;01454;+37.479497;+126.887838;000.041;000.00;8;1;47;13.
33;000000;1;0003;000320;0.0;1;0.00;0338;0336
ST300D
ST300STT;205858552;16;637;20150902;11:06:52;01454;+37.479315;+126.887838;000.011;000.00;11;1;0;12.
00;000000;1;0001;000016;0.0;1;0.00;0155751F170000;1;000.120;0;000.027
ST340R
ST300STT;205124563;17;605;20150717;01:30:52;01454;+37.479324;+126.887843;000.037;000.00;9;1;0;12.2
5;000000;1;0002;000012;0.0;1
<Note>
Some fields written at the end of the report would be different. It depends on model of the GPS device (the
ST300 Series) of Suntech, for example,
The DID/DID_REG is included in STT only on ST300H, ST300A, ST300K and ST300D.
The TEMPERATURE is included in STT only on ST300A and ST300K. If a device (e.g. ST300A or
ST300K) has 2 temperature sensors which are not connected to it, the last 2 fields of the string should
be filled with 2 colons as shown below.
Suntech International Ltd. Confidential Document
Doc. Title Author Page of Pages
ST300STT;100850000;01;010;20081017;07:41:56;00100;+37.478519;+126.886819;000.012;000.00;9;1;0;15.3
0;001100;1;0072;0;4.5;1;012497F1160000;1;3.75;4.21;28E4D95F060000D5:+23.5;:;:
The TEMPERATURE is included in STT only on ST300A and ST300K. If a device (e.g. ST300A or
ST300K) has 1 temperature sensor which is not connected to it, the last field of the string should be
filled with 1 colon as shown below.
ST300STT;100850000;01;010;20081017;07:41:56;00100;+37.478519;+126.886819;000.012;000.00;9;1;0;15.3
0;001100;1;0072;0;4.5;1;012497F1160000;1;3.75;4.21;28E4D95F060000D5:+23.5;28BBE721050000A0:+24.3
;:
The OV_SP_RP, OV_SP_TIME and SPD_2 are included in STT only on ST300A, ST300D and
ST300H.
The MAX_SPD is included in STT only on ST300B can get a maximum speed between each STT
report
6-1-2. Zip
BCD format.
If the Device ID is 123456789, this field will be filled with 0x12, 0x34, 0x56
0x78 and 0x90.
MODEL 1byte Device Model (According to table model).
SW_VER 2 bytes Software Version.
DATE_TIME 6 bytes GPS date & Time (Year + Month + Day + Hour + Minute + Second).
CELL 3 bytes Location Code ID (2 bytes) + Serving Cell BSIC (1 byte).
LAT 4 bytes 1 byte (integer) + 3 bytes (BCD).
LON 4 bytes 1 byte (integer) + 3 bytes (BCD).
SPD 3 bytes 2 bytes (integer) + 1 byte (BCD).
CRS 3 bytes 2 bytes (integer) + 1 byte (BCD).
SATT_FIX 1 byte
Bit 7 Bit 6 Bit 5 Bit 4 ~ Bit 0
Fix Latitude Longitude Satellites count
+/- sign +/- sign
+ sign = 0, - sign = 1.
In case of ST300V
Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0
Out 3 Out2 Out1 In 4 In 3 In 2 In 1 Ignition
Ignition: 1 (ON), 0 (OFF).
Input1 ~ Input4: 1 (Ground, Shorted), 0 (Opened).
Out1 ~ Out3: 1 (Active), 0 (Inactive).
MODE 1 byte 1 = Parking mode.
2 = Driving Mode.
4 = Distance.
5 = Angle.
MSG_NUM 2 bytes Message number.
4 bytes(integer)
MAX_SPD 3 bytes 2 bytes (integer) + 1 byte (BCD).
TPS_S1_IN 2 bytes The number of people riding on the bus to counting by sensor 1.
Initialized only command.
TPS_S1_OUT 2 bytes The number of people get off the bus to counting by sensor 1.
Initialized only command.
TPS_S2_IN 2 bytes The number of people riding on the bus to counting by sensor 2.
Initialized only command.
TPS_S2_OUT 2 bytes Number of people get out the bus to counting by sensor 2.
Initialized only command.
Suntech International Ltd. Confidential Document
Doc. Title Author Page of Pages
Original String :
ST300STT;100850001;01;010;20081017;07:41:56;2F100;+37.478519;+126.886819;032.512;000.00;9;1;500;15
.30;001100;1;0072;2000;4.5;1;1750;012497F1160000;1
Zip Packet
<Note>
Some fields at the end of the report would be different. It depends on model name of ST300 Series, for
example,
The MAX_SPD is included in STT only on ST300B can get a maximum speed between each STT
report
When an emergency occurs, device sends to the server this emergency report as defined already in the course of
configuring device.
6-2-1. Normal
In case of ST300V
Ignition + Input1 + Input 2 + Input 3 + Input4 + Out1 + Out2 + Out3.
Ignition: 1 (ON), 0 (OFF).
Input1 ~ Input4: 1 (Ground, Shorted), 0 (Opened).
Out1 ~ Out3: 1 (Active), 0 (Inactive).
EMG_ID 1 char Emergency type
5 = emergency by anti-theft.
6 = emergency by anti-theft door.
7 = emergency by motion.
8 = emergency by anti-theft shock.
SPD_2 String Speed in km/h. Average speed in time report.
H_METER String Driving hour-meter.
BCK_VOLT String Voltage value of backup battery.
MSG_TYPE 1 char Report is real time (1); Report is storage (0).
ADC String Voltage value of ADC (0~30V)
ADC1 String Voltage value of ADC1 (0~5V)
ADC2 String Voltage value of ADC2 (0~5V)
RPM String Current RPM
TO String Odometer in Km/h
TF String Total fuel used by Lts
VS String Vehicle Speed by Km/h
DID 14 char. Driver ID (inserted I-button ID )
Suntech International Ltd. Confidential Document
Doc. Title Author Page of Pages
ST300
ST300EMG;100850000;01;010;20081017;07:41:56;00100;+37.478519;+126.886819;000.012;000.00;9;1;0;15.3
0;001100;1;0;4.5;1
ST300V
ST300EMG;100850000;10;010;20081017;07:41:56;00100;+37.478519;+126.886819;000.012;000.00;9;1;0;15.3
0;00110000;1;0;4.5;1;12.35;0;0
ST300A
ST300EMG;205989898;07;630;20150902;03:04:08;01454;+37.479320;+126.887834;000.011;000.00;12;1;1;12.
21;110000;1;000057;0.0;1;0.00;4.24;4.27;012497F1160000;1;000.035
ST300H
ST300EMG;205787852;04;639;20150903;05:20:13;01454;+37.479322;+126.887834;000.000;000.00;12;1;1;12.
43;010000;1;000266;0.0;1;0;012497F1160000;1;000.055
ST300C
ST300EMG;100850000;11;010;20081017;07:41:56;00100;+37.478519;+126.886819;000.012;000.00;9;1;0;15.3
0;001100;1;0;4.5;1;3.10;302799;0.00;215.86
ST300K
ST300EMG;100850000;12;010;20081017;07:41:56;00100;+37.478519;+126.886819;000.012;000.00;9;1;0;15.3
0;001100;1;0;4.5;1;1750;3.10;302799;0.00;215.86;012497F1160000;1
ST300P
ST300EMG;205123456;13;430;20141222;01:59:35;01454;+37.479801;+126.887904;000.357;000.00;5;1;108;1
2.14;11110000;1;000047;0.0;0;10;3
Suntech International Ltd. Confidential Document
Doc. Title Author Page of Pages
ST300F
ST300EMG;600850805;14;453;20141222;04:16:15;01454;+37.479612;+126.888632;000.041;000.00;6;1;0;13.3
3;001100;1;000320;0.0;0;0.00;0336;0238
ST300D
ST300EMG;205858552;16;637;20150902;11:10:11;01454;+37.479317;+126.887840;000.009;000.00;11;1;0;12.
00;010000;1;000016;0.0;1;0.00;0155751F170000;1;000.060
ST340R
ST300EMG;205124563;17;605;20150717;01:57:38;01454;+37.479310;+126.887854;000.011;000.00;8;1;1;13.8
2;110000;1;000016;0.0;0
<Note>
Emergency reports are sent A1 times until the device receives an Acknowledgement Response from its server.
Some fields at the end of the report would be different. It depends on device model. For example,
6-2-2. Zip
In case of ST300V
Zip Packet
MODEL 0x01 01
SW_VER 0x00 0x0A 010
DATE_TIME 0x08 0x0a 0x11 0x07 0x29 0x38 20081017;07:41:56
CELL 0x02 0xF1 0x00 2F100, BCD, MSB
LAT 0x25 0x47 0x85 0x19 +37.478519, Decimal part is BCD
LON 0x7e 0x88 0x68 0x19 +126.886819, Decimal part is BCD
SPD 0x00 0x20 0x51 032.512. Convert to 032.51
Decimal part is BCD, MSB
CRS 0x00 0x00 0x00 000.00, Decimal part is BCD, MSB
SATT_FIX 0x89 GPS fixed. Cell count = 9.
Lat. & Lon. sign = plus
DIST 0x00 0x00 0x01 0xF4 500. MSB
PWR_VOLT 0x0F 0x30 15.30. Decimal part is BCD, MSB
I/O 0x0c 001100
EMG_ID 0x01 1
H_METER 0x00 0x00 0x07 0xD0 2000, MSB
BCK_VOLT 0x04 0x50 4.5, Decimal part is BCD
MSG_TYPE 0x01 1
RPM 0x06, 0xD6 1750, MSB
DID 0x01 0x24 0x97 0xF1 0x16 0x00 0x00 012497F1160000
DID_REG 0x01 1
ETX 0x03
<Note>
Emergency reports are sent A1 times until the device receives an Acknowledgement response from its server.
Some fields located in the end part of the report would be different. It depends on model. For example,
The RPM is included in EMG in ST300H.
The DID/DID_REG is included in EMG only in ST300H, 300A, ST300K and ST300D.
TO, TF and VS are included in EMG only in ST300C or ST300K.
FUEL1 and FUEL2 are included in EMG only in ST300F.
The SPD_2 is included in EMG in ST300A, ST300D and ST300H.
The TPS_S1_IN, TPS_S1_OUT, TPS_S2_IN, TPS_S2_OUT are included in EMG only on
ST300P, which one is supported extra TPS fields.
When an emergency occurs, device sends to the server this event report as defined already in the course of
configuring the device. The following tables show a sample of the event report which is sent to the server if Input
Line is changed.
6-3-1. Normal
In case of ST300V
ST300
ST300EVT;100850001;01;010;20081017;07:41:56;00100;+37.478519;+126.886819;000.012;000.00;9;1;0;15.3
0;001100;1;0;4.5;1
ST300V
ST300EVT;100850001;10;010;20081017;07:41:56;00100;+37.478519;+126.886819;000.012;000.00;9;1;0;15.3
0;00110000;1;0;4.5;1;12.35;0;0
ST300A
ST300EVT;205989898;07;630;20150902;04:59:38;01454;+37.479311;+126.887833;000.004;000.00;12;1;1;12.
25;010000;6;000147;0.0;1;0.00;4.22;4.25;012497F1160000;1;000.039
ST300H
ST300EVT;205787852;04;639;20150903;05:21:07;01454;+37.479326;+126.887830;000.000;000.00;12;1;1;12.
46;010100;5;000266;0.0;1;0;012497F1160000;1;000.060
ST300C
ST300EVT;100850000;11;010;20081017;07:41:56;2F100;+37.478519;+126.886819;032.012;000.00;9;1;500;15
.30;001100;1;2000;4.5;1;1750;3.10;302799;0.00;215.86
ST300K
ST300EVT;100850000;12;010;20081017;07:41:56;2F100;+37.478519;+126.886819;032.012;000.00;9;1;500;15
.30;001100;1;2000;4.5;1;1750;3.10;302799;0.00;215.86;012497F1160000;1
ST300P
ST300EVT;205123456;13;430;20141222;02:10:23;01454;+37.479530;+126.887844;000.000;000.00;4;1;8;12.1
8;11110000;1;000050;0.0;1;10;3
ST300EVT;205123456;13;430;20141222;02:10:23;01454;+37.479530;+126.887844;000.000;000.00;4;1;8;12.1
8;11110000;1;000050;0.0;1;10;3;5;2;5;1
ST300F
ST300EVT;600850805;14;453;20141222;04:22:23;01454;+37.479497;+126.887838;000.041;000.00;6;1;8;13.3
8;001100;1;000320;0.0;1;0.00;0238;0336
ST300D
ST300EVT;205858552;16;637;20150902;11:12:53;01454;+37.479318;+126.887840;000.004;000.00;11;1;0;12.
00;010100;5;000016;0.0;1;0.00;0155751F170000;1;000.024
ST340R
ST300EVT;600850779;17;351;20150804;04:41:24;01454;+37.479321;+126.887835;000.002;000.00;12;1;3232
0;12.04;001000;3;000123;4.2;1
<Note>
Some fields at the end of the report would be different. It depends on device model of the ST300 Series. For
example,
The RPM is included in EVT in ST300H.
The DID/DID_REG is included in EVT only in ST300H, 300A, ST300K and ST300D.
TO, TF and VS are included in EVT only in ST300C or ST300K.
FUEL1 and FUEL2 are included in EVT only in ST300F.
The SPD_2 is included in EVT in ST300A, ST300D and ST300H.
The TPS_S1_IN, TPS_S1_OUT, TPS_S2_IN, TPS_S2_OUT are included in EVT only on
ST300P, which one is supported extra TPS fields.
6-3-2. Zip
In case of ST300V
Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0
Out 3 Out2 Out1 In 4 In 3 In 2 In 1 Ignition
Ignition: 1 (ON), 0 (OFF).
Input1 ~ Input4: 1 (Ground, Shorted), 0 (Opened).
Out1 ~ Out3: 1 (Active), 0 (Inactive).
EVT_ID 1 byte Event type:
Original String :
ST300EVT;100850000;01;010;20081017;07:41:56;2F100;+37.478519;+126.886819;032.512;000.00;9;1;500;15
.30;001100;1;2000;4.5;1;1750;012497F1160000;1
Zip Packet
MODEL 0x01 01
SW_VER 0x00 0x0a 010
DATE_TIME 0x08 0x0a 0x11 0x07 0x29 0x38 20081017;07:41:56
CELL 0x02 0xF1 0x00 2F100, BCD, MSB
LAT 0x25 0x47 0x85 0x19 +37.478519, Decimal part is BCD
LON 0x7e 0x88 0x68 0x19 +126.886819, Decimal part is BCD
SPD 0x00 0x20 0x51 032.512. Convert to 032.51
Decimal part is BCD, MSB
CRS 0x00 0x00 0x00 000.00, Decimal part is BCD, MSB
SATT_FIX 0x89 GPS fixed. Cell count = 9.
Lat. & Lon. sign = plus
DIST 0x00 0x00 0x01 0xF4 500. MSB
PWR_VOLT 0x0F 0x30 15.30. Decimal part is BCD, MSB
I/O 0x0c 001100
EVT_ID 0x01 1
H_METER 0x00 0x00 0x07 0xD0 2000, MSB
BCK_VOLT 0x04 0x50 4.5, Decimal part is BCD
MSG_TYPE 0x01 1
RPM 0x06, 0xD6 1750, MSB
DID 0x01 0x24 0x97 0xF1 0x16 0x00 0x00 012497F1160000
DID_REG 0x01 1
ETX 0x03
<Note>
Some fields at the end of the report would be different. It depends on device model of the ST300 Series. For
example,
The RPM is included in EVT in ST300H.
The DID/DID_REG is included in EVT only in ST300H, 300A, ST300K and ST300D.
TO, TF and VS are included in EVT only in ST300C or ST300K.
FUEL1 and FUEL2 are included in EVT only in ST300F.
The SPD_2 is included in EVT in ST300A, ST300D and ST300H.
The TPS_S1_IN, TPS_S1_OUT, TPS_S2_IN, TPS_S2_OUT are included in EVT only on
ST300P, which one is supported extra TPS fields.
Device sends Alert to the server as defined by user in the course of setting the relevant parameters. Most of cases
that requiring an alert to be issued means that the vehicle or asset or its driver is in danger or is almost in danger
that should be notified by the device to the server and/or the cellular phone (If communication via SMS has been
configured) for warning.
Have a close look at the fields from the following table for more information on when and what alerts are triggered.
An <Example> of alerting and <Note> are also described in the bottom part of the table below.
6-4-1. Normal
In case of ST300V
15 = Shocked.
16 = Collision has occurred to the vehicle.
18 = Deviated from the predefined route.
19 = Entered into the predefined route.
Suntech International Ltd. Confidential Document
Doc. Title Author Page of Pages
SPN1+ SPN2+SPN3&FMI+CM&OC
ST300
ST300ALT;100850000;01;010;20081017;07:41:56;00100;+37.478519;+126.886819;000.012;000.00;9;1;0;15.3
0;001100;3;0;4.5;1
ST300V
ST300ALT;100850000;10;010;20081017;07:41:56;00100;+37.478519;+126.886819;000.012;000.00;9;1;0;15.3
0;00110000;3;0;4.5;1;12.35;0;0
Suntech International Ltd. Confidential Document
Doc. Title Author Page of Pages
ST300A
Temperature no use
ST300ALT;205989898;07;630;20150902;04:33:28;01454;+37.479299;+126.887830;000.009;000.00;12;1;1;12.
25;010100;34;000147;0.0;1;0.00;4.23;4.27;012497F1160000;1;000.035
Temperature use
ST300ALT;205989898;07;630;20150902;04:33:28;01454;+37.479299;+126.887830;000.009;000.00;12;1;1;12.
25;010100;34;000147;0.0;1;0.00;4.23;4.27;012497F1160000;1;28E4D95F060000D5:+24.1;28F5573B050000A
A:+24.3;28BBE721050000A0:+24.8;000.035
ST300H
ST300ALT;205787852;04;639;20150903;05:22:12;01454;+37.479331;+126.887825;000.000;000.00;12;1;1;12.
46;110100;33;000266;0.0;1;0;012497F1160000;1;000.054
ST300C
ST300ALT;100850001;11;010;20081017;07:41:56;2F100;+37.478519;+126.886819;032.512;000.00;9;1;500;15
.30;001100;1;501;2000;4.5;1;1750;3.10;302799;0.00;215.86;0
If ALERT_ID is 28:
ST300ALT;100850001;11;010;20081017;07:41:56;2F100;+37.478519;+126.886819;032.512;000.00;9;1;500;15
.30;001100;28;501;2000;4.5;1;1750;3.10;302799;0.00;215.86;01020304;012497F1160000;1
ST300K
Temperature no use
ST300ALT;100850001;12;010;20081017;07:41:56;2F100;+37.478519;+126.886819;032.512;000.00;9;1;500;15
.30;001100;1;501;2000;4.5;1;1750;3.10;302799;0.00;215.86;012497F1160000;1
Temperature use
ST300ALT;100850001;12;010;20081017;07:41:56;2F100;+37.478519;+126.886819;032.512;000.00;9;1;500;15
.30;001100;75:28E4D95F060000D5;501;2000;4.5;1;1750;3.10;302799;0.00;215.86;012497F1160000;1;28E4D
95F060000D5:+24.1;28F5573B050000AA:+24.3;28BBE721050000A0:+24.8
ST300KDTC
ST300ALT;100850001;12;010;20081017;07:41:56;2F100;+37.478519;+126.886819;032.512;000.00;9;1;500;15
.30;001100;28;501;2000;4.5;1;1750;3.10;302799;0.00;215.86;01020304;012497F1160000;1
ST300P
ST300ALT;205123456;13;430;20141222;02:09:57;01454;+37.479530;+126.887844;000.000;000.00;4;1;8;12.1
4;10110000;45;000050;0.0;1;10;3
ST300F
ST300ALT;600850805;14;453;20141222;04:37:48;01454;+37.479722;+126.888591;000.046;000.00;7;1;47;13.
37;000000;73;000320;0.0;1;0.00;0238;0336
ST300D
ST300ALT;205858552;16;637;20150902;11:15:34;01454;+37.479320;+126.887834;000.002;000.00;11;1;0;12.
00;110100;33;000016;0.0;1;0.00;0155751F170000;1;000.036
ST340R
ST300ALT;205124563;17;605;20150717;02:25:41;01454;+37.479321;+126.887838;000.002;000.00;11;1;1;13.
82;110000;59;000044;0.0;1
Speed down from the over-speed state of the polygonal geo-fence group 1
ET200INALT;000000;105;20110419;05:38:03;00054;+37.504995;+126.877360;029.863;136.13;8;1;79;11.63;10
0000;2P01
[2015-11-11 11:51:04]
ST300ALT;205788787;07;682;20151111;02:51:08;01454;+37.479316;+126.887849;000.002;000.00;9;1;3;12.3
6;100001;46;000336;0.0;1;0.00;4.26;4.24;00000000000000;0;000.029;12;-51;-247;0.50
DPA Alert
ST300A
Temperature no use
ST300ALT;205989898;07;630;20150902;04:33:28;01454;+37.479299;+126.887830;000.009;000.00;12;1;1;12.
25;010100;34;000147;0.0;1;0.00;4.23;4.27;012497F1160000;1;000.029;12;-51;-247;0.50
Temperature use
ST300ALT;205989898;07;630;20150902;04:33:28;01454;+37.479299;+126.887830;000.009;000.00;12;1;1;12.
25;010100;34;000147;0.0;1;0.00;4.23;4.27;012497F1160000;1;28E4D95F060000D5:+24.1;28F5573B050000A
A:+24.3;28BBE721050000A0:+24.8;000.029;12;-51;-247;0.50
ST300D
ST300ALT;205858552;16;637;20150902;11:15:34;01454;+37.479320;+126.887834;000.002;000.00;11;1;0;12.
00;110100;33;000016;0.0;1;0.00;0155751F170000;1;000.029;12;-51;-247;0.50
ST300H
ST300ALT;205787852;04;639;20150903;05:22:12;01454;+37.479331;+126.887825;000.000;000.00;12;1;1;12.
46;110100;33;000266;0.0;1;0;012497F1160000;1;000.029;12;-51;-247;0.50
<Note>
ALERT_ID 3, 4, and 8 are applicable to the device that has an external GPS antenna.
ALERT_ID 13 may be reported if the Back-up Battery cannot be charged or cannot be supported for long time
enough in case the Main Power Source (vehicles battery) is disconnected.
ALERT_ID 46,47, 48 and 49 are optional functions to analyze the Driver Pattern.
ALERT_ID 59 and 60 are applicable to the device that has I-Button event line.
ALERT_ID 28 : It attaches a field for error code in front of the field of alert as below. Otherwise, its omitted.
DTC CODE : 0x01020304 ( SPN1(0x01)+ SPN2(0x02)+SPN3&FMI(0x03)+CM&OC(0x04)
Some fields at the end of the report would be different. It depends on device model of ST300 Series. For
example,
The RPM is included in ALT in ST300H.
The DID/DID_REG is included in ALT only in ST300H, 300A, ST300K and ST300D.
If the temperature sensor is not connected to the device, the field of TEMPERATUE is marked with
a colon, :.
The AC, HB, SHARP and FORCE are include in Alert number 46, 47, 48 and 49 only in
ST300A, ST300D and ST300H.
6-4-2. Zip
If the Device ID is 123456789, this field will be filled with 0x12, 0x34, 0x56
0x78 and 0x90.
MODEL 1byte Device Model (According to table model).
SW_VER 2 bytes Software Version.
DATE_TIME 6 bytes GPS date & Time (Year + Month + Day + Hour + Minute + Second).
CELL 3 bytes Location Code ID (2 Bytes) + Serving Cell BSIC (1 Byte).
LAT 4 bytes 1 byte (integer) + 3 bytes (BCD).
LON 4 bytes 1 byte (integer) + 3bytes (BCD).
SPD 3 bytes 2 bytes (integer) + 1 byte (BCD).
CRS 3 bytes 2 bytes (integer) + 1 byte (BCD).
SATT_FIX 1 byte
Bit 7 Bit 6 Bit 5 Bit 4 ~ Bit 0
Fix Latitude Longitude Satellites count
+/- sign +/- sign
+ sign = 0, - sign = 1.
In case of ST300V
Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0
Out 3 Out2 Out1 In 4 In 3 In 2 In 1 Ignition
Ignition: 1 (ON), 0 (OFF).
Input1 ~ Input4: 1 (Ground, Shorted), 0 (Opened).
Out1 ~ Out3: 1 (Active), 0 (Inactive).
ALERT_ID 1 byte Alert type:
0x01 ~ 0x4E
SPD_2 3 bytes 2 bytes (integer) + 1 byte (BCD)
AC 2 bytes Acceleration in X axel of accelerometer.
HB 2 bytes Harsh brake in X axel of accelerometer.
SHARP 2 bytes Sharp turn in X axel of accelerometer.
FORCE 4 bytes Value of force when DPA Alert
1 byte (integer) + 3 bytes (BCD)
H_METER 4 bytes Driving hour-meter.
BCK_VOLT 2 bytes Voltage value of backup battery:
MSG_TYPE 1 byte Report is made in real time (1); Report is in storage (0).
ADC 2 bytes Voltage value of ADC1. (0~30V)
Bottom byte : Previous active error code (Please refer to Note, hex.).
DID 7 byte Driver ID (inserted I-button ID )
DID_REG 1 byte State of DIDs registration
TPS_S2_OUT 2 bytes Number of people get out the bus to counting by sensor 2.
Initialized only command.
ETX 0x03 End of zip data.
<Example>
Original String :
ST300ALT;100850001;01;010;20081017;07:41:56;2F100;+37.478519;+126.886819;032.512;000.00;9;1;500;15
.30;001100;1;501;2000;4.5;1;1750;012497F1160000;1
Zip Packet
<Note>
ALERT_ID 3, 4, and 8 are applicable to the device that has an external GPS antenna.
ALERT_ID 13 may be reported if the Back-up Battery cannot be charged or cannot be supported for long time
enough in case the Main Power source (vehicles battery) is disconnected.
ALERT_ID 46,47, 48 and 49 are optional functions to analyze the Driver Pattern.
ALERT_ID 59 and 60 are applicable to the device that has I-Button event line.
ALERT_ID 28 : It attaches a field for error code in front of the field of alert as below. Otherwise, its omitted.
Suntech International Ltd. Confidential Document
Doc. Title Author Page of Pages
Some fields at the end of the report would be different. It depends on device model of ST300 Series. For
example,
Device sends Travel Event to the server as defined by user in the course of setting the telemetry parameters. This
event is sent when the vehicle is parked. This report is used only on ST300A, ST300H, ST300K and ST300D.
6-5-1. Normal
ST300HTE;100850000;07;248;20110101;00:13:52;167559;12.28;004005;0.0;1;0;3;3;0;-22.881018;-047.070831
;-22.881018;-047.070831;000.000;000.000;0;0;3;0;0;0;01E04D44160000
6-5-2. Zip
TIME_DC 2 bytes Accumulated time of the vehicle which has been driven putting the gear in
dead center in this travel (in minute).
DRIVER_ID 7 bytes Inserted driver ID: BCD format.
ETX 0x03 End of zip data.
<Example>
Original String :
ST300HTE;600850777;07;377;20140428;00:13:52;151227;12.11;000662;0.0;1;135010;351;21;330;
-22.881018;-047.130831;-22.882034;-047.087123;035.350;096.480;3;5;12;334;7;0;01E04D44160000
Zip Packet
A typical GSM/GPRS service provider in any countries has its own corporate policy restricting connection time of
device with the GSM/GPRS networks only at an interval if device does not communicate with its server for a long
time, which is 1 hour, for instance. The time length varies depending upon such service provider. Please check it by
asking your GSM/GPRS service provider this question in your country.
In a case that there has not been any communication between a device and its server for such a time period, the
GSM/GPRS service provider would not provide GSM/GPRS service for the device temporarily. To avoid such a case,
device sends the server this Keep-Alive Report at an interval, T4 (Keep-Alive interval named in SyncTrak and in
this document), which is shorter than the 60 minutes. User of the device may adjust the value of T4 as desired.
This report is intended to mean that the device is still alive and ready for any possible communications with the server
for that long time (T4) even though the device does not interact temporarily with the server.
6-6-1. Normal
All Models
HDR
DEV_ID
6-6-2. Zip
Zip Packet
If device is connected with an external appliance via RS232, it receives data from the appliance and sends the data
to the server. Data transfer is made with the string below.
6-7-1. Normal
In case of ST300V
Up to 500 bytes.
CHK_SUM String 8bit Checksum. Lower than 8 bit of the summation of DATA field.
H_METER String Driving hour-meter.
BCK_VOLT String Voltage value of backup battery.
6-7-2. Zip
BCD format
If the Device ID is 123456789, this field will be filled with 0x12, 0x34, 0x56
0x78 and 0x90.
MODEL 1 byte Device Model (According to table model).
SW_VER 2 bytes Software Version.
DATE_TIME 6 bytes GPS date & Time (Year + Month + Day + Hour + Minute + Second).
CELL 3 bytes Location Code ID (2 Bytes) + Serving Cell BSIC (1 Byte).
LAT 4 bytes 1 byte (integer) + 3 bytes (BCD).
LON 4 bytes 1 byte (integer) + 3bytes (BCD).
SPD 3 bytes 2 bytes (integer) + 1 byte (BCD).
CRS 3 bytes 2 bytes (integer) + 1 byte (BCD).
SATT_FIX 1 byte
Bit 7 Bit 6 Bit 5 Bit 4 ~ Bit 0
Fix Latitude Longitude Satellites count
+/- sign +/- sign
+ sign = 0, - sign = 1.
DIST 4 bytes Traveled distance in meter.
PWR_VOLT 2 bytes Voltage value of the Main Power:
<Example>
Original String :
ST300UEX;100850001;01;010;20081017;07:41:56;2F100;+37.478519;+126.886819; 032.512;000.00;9;1;500;15.
30;001100;25;Welcome to Suntech World!;12;2000;4.5;1;1750;012497F1160000;1
Zip Packet
If the device receives this command and is connected with external appliance via RS232, it transfers the data to the
appliance connected via RS232.
<Note>
CHK_SUM is string converted from lower 8 bit of the summation of DATA field.
In case of the above example, value of 0 character in DATA field is equal to 0x30 in hex system, and 1 is equal
to 0x31 in hex system.
In this case, summation of DATA will be 0x12F (0x30+0x31+0x32+0x33+0x34+0x35), and CHK_SUM string will
be 2F.
And, the whole string from server will be ST300DEX;100850000;02;6;012345;2F.
If the DATA field includes 0x00 or 0x01, the server should convert and send as below.
Original Data: 0x30 0x31 0x00 0x32 0x01.
Conversion: 0x30 0x31 0x01 0x10 0x32 0x01 0x11.
In case device is located in an area where it has good connectivity with GSM and without having good connectivity
with GPRS, it sends a string type report to its server. However, as soon as the bad connectivity between GPRS and
device gets back to normal, the device will try to send the reports to the server.
(Note: STT String sent via SMS does not include the message number field.)
Suntech International Ltd. Confidential Document
Doc. Title Author Page of Pages
Device sends to its server status string via SMS when it can be connected with the server only via SMS without
being connected with GPRS.
If you are a smart phone user, you can use it to easily find the current location on the Google map, just send one of
the following messages by your smart phone:
And, then the Google Map will be responding to you by sending the address on your smart phone. You can see the
current location of ST300/ST340 just by opening the message containing that address on the web browser.
In order to enable ST300/ST340 to accept your SMS message, you have to add your smart phone number to one of
the 4 optional numbers such as SMS_MT1 to SMS_MT4 or disable SMS_LOCK. Refer to Chapter 4-4 of this Manual,
GSM Parameter Setting for more details. Before you start using this function, you should get to know the URL
(server address) of the Google map first.
You can have more information about how to get the server address of the Google map in section Command to Get
Google Map Address of this document.
When Ignition OFF is made, device sends to the server this coin machine report as defined already in the course
of configuring device.
ST300B
HDR
DEV_ID
MODEL
SW_VER
DATE
TIME
CELL
LAT
LON
SPD
CRS
SATT
FIX
DIST
PWR_VOLT
I/O
MODE
TOTAL_COIN
MSG_NUM
6-11-1. Normal
ST300B
ST300COI;205121212;09;576;20150526;00:57:11;00000;+37.479318;+126.887826;000.006;000.00;12;1;42;12.
25;000000;0;0000000000;0151
<Note>
Coin Machine reports are sent when Ignition OFF only.
6-11-2. Zip
BCD format.
If the Device ID is 123456789, this field will be filled with 0x12, 0x34, 0x56
0x78 and 0x90.
MODEL 1byte Device Model (According to table model).
SW_VER 2 bytes Software Version.
DATE_TIME 6 bytes GPS date & Time (Year + Month + Day + Hour + Minute + Second).
CELL 3 bytes Location Code ID (2 bytes) + Serving Cell BSIC (1 byte).
LAT 4 bytes 1 byte (integer) + 3 bytes (BCD).
LON 4 bytes 1 byte (integer) + 3 bytes (BCD).
SPD 3 bytes 2 bytes (integer) + 1 byte (BCD).
CRS 3 bytes 2 bytes (integer) + 1 byte (BCD).
SATT_FIX 1 byte
Bit 7 Bit 6 Bit 5 Bit 4 ~ Bit 0
Fix Latitude Longitude Satellites count
+/- sign +/- sign
+ sign = 0, - sign = 1.
In case of ST300V
Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0
Out 3 Out2 Out1 In 4 In 3 In 2 In 1 Ignition
Ignition: 1 (ON), 0 (OFF).
Input1 ~ Input4: 1 (Ground, Shorted), 0 (Opened).
Out1 ~ Out3: 1 (Active), 0 (Inactive).
MODE 1 byte 1 = Parking mode.
2 = Driving Mode.
4 = Distance.
5 = Angle.
TOTAL_COIN 4 bytes Total coin value
Original String :
ST300COI;100850001;01;010;20081017;07:41:56;00000;+37.478519;+126.886819;032.512;000.00;9;1;500;15.
30;001100;1;0000000000;0072
Zip Packet
When Ignition OFF is made, device sends to the server this Journey Summary Report as defined already in the
course of configuring device.
ST300C
HDR
DEV_ID
MODEL
SW_VER
BRAKE
ODOMETER
AVE_FUEL_ECO
AVE_RPM
AVE_SPEED
CLUTCH
TOTAL_IDLE
ENGINE_HOURS
TOTAL_FUEL
TOTAL_FUEL_IDLE
AVE_TEMP
6-12-1. Normal
<Example>
ST300C
ST300JSR;205326326;11;596;10;12345.678;12.345;1234.567;12.345;20;123;12.345;12.345;1.234;12.345
<Note>
Journey Summary Report is sent when Ignition OFF only.
6-12-2. Zip
BCD format.
If the Device ID is 123456789, this field will be filled with 0x12, 0x34, 0x56
0x78 and 0x90.
MODEL 1byte Device Model (According to table model).
SW_VER 2 bytes Software Version.
BRAKE 4 bytes How many times pushing brake pedal.
This value will be increasing when brake pedal push more than 1second.
4 bytes (integer)
ODOMETER 3 bytes Odometer value for Ignition ON to Ignition OFF.
3 bytes Total using fuel in idle value for Ignition ON to Ignition OFF.
TOTAL_FUEL_IDLE
2 bytes (integer) + 1 byte (BCD).
3 bytes Average engine temperature value for Ignition ON to Ignition OFF.
AVE_TEMP
2 bytes (integer) + 1 byte (BCD).
<Example>
Original String :
ST300JSR;205326326;11;596;10;12345.678;12.345;1234.567;12.345;20;123;12.345;12.345;1.234;12.345
Zip Packet
6-13-1. Normal
Definition : String to report information of current travel when ignition is OFF (starts parking).
6-13-2. Zip
If the Device ID is 123456789, this field will befilled with 0x12, 0x34, 0x56
0x78 and 0x90.
MODEL 1byte Device Model (According to table model)
SW_VER 2 byte Software Version
DATE_TIME 6 bytes GPS date & Time (Year + Month + Day + Hour + Minute + Second)
Suntech International Ltd. Confidential Document
Doc. Title Author Page of Pages
Original String :
ST300HIS;205956956;05;503;20150615;08:23:35;12.36;0.0;1;000.007;000.007;0;10;0;0;0;0;0;0;0;0;0;0;0;0;0;0;
0;0;0;0;0;0;180
Zip Packet
0x02
0x00 0x48
0x1e
0x20 0x59 0x56 0x95 0x60
0x05
0x01 0xf7
0x0f 0x06 0x0f 0x08 0x17 0x23
0x0c 0x36
0x00 0x00
0x01
0x00 0x00 0x00
0x00 0x00 0x00
0x00 0x00 0x00 0x00
0x00 0x0a
0x00 0x00
0x00 0x00
0x00 0x00
Suntech International Ltd. Confidential Document
Doc. Title Author Page of Pages
0x00 0x00
0x00 0x00
0x00 0x00
0x00 0x00
0x00 0x00
0x00 0x00
0x00 0x00
0x00 0x00
0x00 0x00
0x00 0x00
0x00 0x00
0x00 0x00
0x00 0x00
0x00 0x00
0x00 0x00
0x00 0x00
0x00 0x00
0x00 0x00 0x00 0xb4
0x03
Definition:
Response
1. In case that ST300 has the log data
ST300CMD;Res;000000000;390;LOGREQ;OK
ST300CMD;Res;000000000;390;LOGREQ;EMPTY
Response :
ST300CMD;Res;000000000;390;LOGCANCEL;OK
<note>
If the SPD_TIME = 0 the device store the data. The maximum time you can request is 2 hours and the
device can store the data during 10 hours.
If the SPD_TIME is 1 ~ 4 the device cant store the data.
Definition :
<note>
Data packet
Time : 6bytes
Year 1byte : Integer
Month 1byte : Integer
Day 1byte : Integer
Hour 1byte : Integer
Minute 1byte : Integer
Second 1byte : Integer
Crash Reconstruction Data : 26bytes * 30sec = 780 bytes
Latitude 4bytes : double float : 8bytes
Longitude 4bytes : double float : 8bytes
Speed 4bytes : float : 4bytes
Accelerometer X-Axis : integer : 2bytes
Accelerometer Y-Axis : integer : 2bytes
Accelerometer Z-Axis : integer : 2bytes
After device is configured, user may need to check/query values of the parameters if he/she wants to change those
values. This chapter shows user how to change the parameters values that have been set already.
**Caution: If Device ID is not correct, this command will be ignored by the device.
Once this command is made, some interactions will be made between the server and the device as described in the
Meaning section of the table below.
Once this command is made, some interactions will be made between the server and the device as described in the
Meaning section of the table below.
7-4. Pre-setting
Once this command is made, some interactions will be made between the server and the device as described in the
Meaning section of the table below.
[response] ST300CMD;Res;100850000;010;Preset;
NTW;0;internet;;;111.111.111.111;8600;;;;1234;
RPT;60;180;120;60;3;0;0;;;;
EVT;1;60;0;3;2;2;30;20;20;1;1;1;0;0;0;0;0;0;0;0;0;0;0;0;
GSM;0;;;;;0;;;;;;;;
SVC;1;120;0;0;0;0;1;1;1;0;0;0;0
DEV;0;0;0;0
<Note>
** After power is on, the device sends to the server response string of the Preset once.
** The DEV field informs the server about the current status of the device as below.
OUT1 OUT2 PWR_DN BAT_CON
0 = Disable 0 = Disable 0 = Normal 0 = Backup battery is disconnected.
1 = Enable 1 = Enable 1 = Sleep 1 = Backup battery is connected.
2 = Deep sleep
[command] ST300CMD;100850000;02;PresetA
[response] ST300CMD;Res;100850000;010;PresetA;
NTW;0;internet;;;111.111.111.111;8600;;;;1234;
RPT;60;180;120;60;3;0;0;;;;
EVT;1;60;0;3;2;2;30;20;20;1;1;1;0;0;0;0;0;0;0;0;0;0;0;0;
LTM;0;3;1;
GSM;0;;;;;0;;;;;;;;
SVC;1;120;0;0;0;0;1;1;1;0;0;0;0;
ADP;U;T;2;9000;0;0;0;0;0;0;
MSR;10;0.10;0.10;0.70;
MBV;9.43;21.07;17.07;8.00;18.00;0.00;0.00;
Suntech International Ltd. Confidential Document
Doc. Title Author Page of Pages
NPT;02;0;0;0;0;0;500;300;5;10;5;10;
DEV;0;0;0;0;0;0;0;0
<Note>
Once this command is made by the server, the device will stop reporting about the occurrence of emergency. More
details are described in the Meaning section of the table below.
[EXTRA_INFO]
HDR DEV_ID SW_VER DATE TIME CELL LAT LON SPD CRS
<Note>
** Output1 line goes to active status.
** If OUT1 is set with immobilizer, output1 line goes to the Active Status gradually with pulse in driving mode.
** If OUT1 is set with pulse type, output1 line generates pulse and automatically returns to the Inactive State after
pulsing out.
<Note>
** Output1 line goes to the Inactive Status.
<Note>
<Note>
** Output2 line goes to the Inactive Status.
<Note>
<Note>
** Output3 line goes to the Inactive Status.
** This command does not work on the ST340R model.
Once this command is made, some interactions will be made between the server and the device as described in the
Meaning section of the table as below.
Once this command is made, some interactions will be made between the server and the device as described in the
Meaning section of the table as below.
Suntech International Ltd. Confidential Document
Doc. Title Author Page of Pages
[command] ST300CMD;100850000;02;ReqICCID
[response] ST300CMD;Res;100850000;010;ReqICCID;89550230000084256668
Once this command is made, some interactions will be made between the server and the device as described in the
Meaning section of the table as below.
[command] ST300CMD;100850000;02;ReqVer
[response] ST300CMD;Res;100850000;010;ReqVer;ST300E_SAMPLE_STBASE_001
7-15.Status Request made by External Device Connected with RS232 of Event Lines
This command is made towards a device by the external device connected with RS232 of the event line. Once the
device receives this command, some interactions will be made between the external device and the device as
described in the Meaning section of the table as below.
[command] SttReq
[response]
ST300STT;100850000;01;010;20090724;07:12:16;00129;+37.479995;+126.885815;000.029;000.00;
7;1;0;15.33;100000;2;0002
This command is made towards a device by the external device connected with RS232 of the event line. Once the
device receives this command, some interactions will be made between the external device and the device as
described in the Meaning section of the table as below.
[response]
+CGREG:0, 1
OK
<Note>
The device of Suntech can support the most of AT Commands except SMS commands.
<Note>
This command is used only on the model that has Odometer line (ST300H).
[response] ST300CMD;Res;100850000;267;StopCountOdo;3300
Device calculates ODO_UNIT with count of odometer pulses and value of entered traveled distance
And responds with ODO_UNIT value (odometers pulse count per 1km distance).
3300 in the above example was calculated by 4950/1.5 (pulse count during the travel / travel
distance).
<Note>
Refer 9-10 for calibration by using this command.
This command is used only on the model that has Odometer line (ST300H).
<Note>
This command is used only on the model that has RPM line (ST300H).
<Note>
In case of big truck, the vehicle may have dual gear system and may be changed odometer unit (pulse per 1km
distance). When ODO_UNIT is set to auto, the device can recognize these dual situations automatically and
can apply different value depending on dual situations as calculating speed and moving distance.
This command is used only on the model that has RPM line (ST300H).
<note>
This command is used only on the model that has RPM line (ST300H).
<Note>
When the device activates related output because registered I-button is not inserted and the device receives this
command, the device deactivates related output temporarily until next parking.
This command is used only on the model that can support I-button (ST300A, ST300H, ST300K and ST300D).
<Note>
This command works only on ST300H, ST300A and ST300K.
Description on each factor necessary to make types of these commands is shown in this Chapter.
8-1. Command on how to erase all the saved reports Erase All
This command is used if you want to erase all the saved reports and disable the outputs.
This command is used if you want to initialize sequence number of the message.
This command is used if you want to set the travelled time period.
This command is used for erasing all circular geo-fence setting data.
This command is used if the device is required to report to the server with all of the geo-fence parameters that are
pre-set.
<Notes>
** Continuous field of the above response string represents bold.
Once this command is made, some interactions will be made between the server and the device as described in the
Meaning section of the table as below.
<Notes>
** When the device has no SIM or is under power-on process, the own phone number cannot be read.
The device reports with NotReady.
** If the own number field in SIM is empty, the device reports with NoData.
Once this command is made, some interactions will be made between the server and the device as described in the
Meaning section of the table as below.
<Notes>
** When the device has no SIM or is under power-on process, the own phone number cannot be set.
The device reports with NotReady.
8-9. Command on how to request information about Current Volume Level in Call
This command is used if the current volume level needs to be reported to the server.
<Notes>
** Its available only for the model that can support voice call.
This command is made to the device when the volume level for the phone call receiver needs to be set.
<Notes>
** It is available only for the model that can support voice call.
If the device supports Voice, volume number range must be 0 to 6.
If the device does not support Voice, volume number range must be 0 to 255.
This command is made by the server to the device which needs to be rebooted.
This command is made by the server to the device when the server wants to enable server locking.
<Note>
1. How to EnableSvrLock command is available only when this command is sent by GPRS.
2. Once Server Lock is Enabled and the first report is made to the server, the server starts being locked.
3. If Server is LOCKED, you can change IP and port (including backup server) only by GPRS.
The other parameters are configurable by SyncTrak or GPRS or SMS.
4. In order to Disable the Server Locking, you have to use PC program (ServerLock) with USB Dongle.
This command is made by the server to the device when the server wants to disable a function of server locking.
<Note>
1. DisableSvrLock command can be effective only when the command is sent by GPRS.
2. This command is used to disable the state of the server locking.
This command is made by the server to the device when the server wants to restart a function, Anti-theft 2.
<Note>
This command is only for Anti-theft 2 mode.
This table shows us how to set the SMS number to be used when the panic button is pressed.
This table shows us how to get the SMS number when the panic button is pressed.
In a case that you use a smart phone operating a function of Where Are You, you can use the server of the Google
as set below in italic bold letters, Google map address. The users of the Google map should check what the right
map address of the Google is and that the right address should be set. The Google map address needs to be checked.
If the Google map address is not right, this function (Where Are You) cant be used.
[command] ST300CMD;100850000;02;SetGoogleMap=http://maps.google.com/[Lon],[Lat]/maps?q
[response] ST300CMD;Res;100850000;010; SetGoogleMap=http://maps.google.com/[Lon],[Lat]/maps?q
<Note>
The max of input string is 96 characters.
In case this command is made, the pre-set existing Google Map address will be known.
8-19. Command on how to do Simultaneous Testing for Output 1 & 2 for 30 seconds
The following tables show how to test the two outputs (i.e. Output1 and Output2) at the same time for 30 or 60
seconds.
Output 1 and Output 2 will be activated for 30 seconds for the testing. In 30 seconds, the two outputs will be
deactivated.
Output 1 and Output 2 will be activated for 60 seconds for the testing. In 60 seconds, the two outputs will be
deactivated.
For the purpose of reducing power consumption of the battery while the main power line is disconnected (only
backup battery sources power), the server can make this command.
Once this command is made, some interactions will be made between the server and the device as described in
the Meaning section of the table as below.
This command is made to the device when the volume level for the phone call receiver needs to be set.
<Notes>
** It is available only for the model that can support voice call.
This command will be setting Horn Pulses count or reset the output type to GPIO.
<Notes>
Value Activating Time Deactivating Time Pulse count Output2 type
1 2 seconds 2 seconds 1 Horn Pulses
2 2 seconds 2 seconds 2 Horn Pulses
3 2 seconds 2 seconds 3 Horn Pulses
4 2 seconds 2 seconds 4 Horn Pulses
5 n/a n/a n/a GPIO
This command will be setting Horn Pulses count or reset the output type to GPIO.
Device has 14-pin event lines consisting of a port with 4-pin lines (to be described later) and another port with10-pin
cables as shown in the below picture to be used for events, communication, power and ground line.
The Input lines were designed to endure up to 50V. The output lines can endure up to 40V.
Option1 and Option2 lines can be selected out of the types (which are shown in the Figure above) by changing the
circuit of the connection made in the factory.
ST340R
Main Power
GND
Ignition
Input 1
Input2
RS232_RX
Output1
RS_232_TX
9-1-1. Immobilizer
If output type is set to Immobilizer or Immobilizer & Auto Active and you connect this line to immobilize the vehicle,
the Output line can use the immobilizer.
When the device receives command to activate the immobilizer output, one of the 2 options (ActiveorInactive) will
be selected. Which activation you choose will depend on what mode the vehicle is in a parking mode or in a driving
mode.
In case of driving, the immobilizer activation is made in a way of progressive blocking as shown the following blinking
diagram:
However, in case of parking, as soon as the vehicle is parked, the immobilizer is activated normally.
In a case that the Output type is set to Immobilizer & Auto active, the output is activated automatically as long as
the vehicle is parked. In such a case the Output is also activated as long as the vehicle starts being in a driving mode.
If the device receives a command to activate the immobilizer output, the output is always activated regardless to a
mode type (either parking mode or driving mode).
9-1-2. Immobilizer2
If output type is set to Immobilizer2(or Immobilizer2 & Auto Active), the way how Immobilizer2(or Immobilizer2 &
Auto Active) functions is same as the way how 9-1-1. Immobilizer functions.
The active time of the Immobilizer2(or Immobilizer2 & Auto Active) is increased by 90ms every 2.5 seconds.
One(1) minute later, the immobilizer starts being activated and will be activated continuously.
In a case that the Output type is set to Buzzer, the buzzer alerts. The following table shows such cases:
RED LED indicates GPS status and blue LED indicates GPRS status while the device is not processing call.
No Fix 2
<Probable Situations>
1. If power is on, GPS chipset tries to find position for some minutes.
Blue LED
Red LED
Blue LED
Red LED
The device can save power consumption of the battery by using one of two modes such as Sleep Mode or Deep
Sleep Mode. If PWR_DN is set with 1 or 2 and report interval in parking mode is made every 10 minutes or longer
than 10 minutes to enable the devices to process power down while the vehicle is in parking situation.
- If an emergency situation occurs, device cannot process power down for 30 minutes due to safety issue.
- When GPS signal is not fixed, the device can start to process power down after trying to fix for 5 minutes.
- If communication with the server fails continuously, the device processes Deep Sleep after trying to make
communications for 8 minutes.
- While the device is in deep sleep, it cannot process charging the backup battery.
Device turns off LED and sends a status report and a related alert before entering the power-down functionality.
The device terminates power down either when ignition is ON or when an event or an emergency occurs. In such
cases, the device sends related alert and status string, instead.
- Sleep
Device turns off only GPS part and GPRS part enters Sleep. Even for time of Sleep, all communication with the
server works normally and the device can receive SMS or call always. Average of Sleep current is lower than 10mA
and this current may be increased under weak GPRS condition.
- Deep Sleep
Device turns off GPS and GPRS part. For the time of Sleep, all communication with the server is impossible and it
cannot receive any SMS messages or any calls, either. Device turns on GPRS session every max. 30 minutes.
However, the device cannot receive SMS or call while it is in Deep Sleep. Average current during Deep Sleep mode
is around 5mA (non-battery version).
9-4.Backup Battery
The device has a backup battery in order to be prepared for any emergency cases when the main power source is
removed or sabotaged. When the vehicle is stolen and power of device is removed, the backup battery starts working
as a replacement power source for the main power source (the vehicles battery).
Backup battery at full charge on good GPRS network condition at a reporting interval value of every 3 minutes, the
device can work for 6 hours or more at least.
The device was designed to keep backup battery staying as effective as possible all the time. Charging the backup
battery starts if voltage of the backup battery goes below 4,2V.In a parking mode, charging the backup battery is hold
when the main power source gets consumed down to 90% of the normal voltage level.
The charging algorithm for the backup battery has a protection against over-voltage, abnormal charging current and
high temperature.
In addition, the device alerts about battery error if the backup battery cannot be charged.
- Ignition ON (Driving)
The sensor mode goes to collision detection mode. So, if the vehicle has a car accident, the accident may bring about
a big impact of which value is higher than that of the specified collision threshold (COLL_THRES). In this case the
device will be reporting a collision message to the server.
After a collision is made against the vehicle, the sensor will be disabled for a while (30 seconds) so as to avoid
sending to the server the same message as the first one repeatedly.
Ignition Off situation means that the vehicle is in state of parking and that the sensor goes to parking mode(shock
or movement detection mode).
In this situation, if there is a shock made on the vehicle by somebody, the device will report a shock message to the
server. The device will also exit from the power down mode if the device has been in power down mode.
In case of movement, the device will exit from the mode of power down to check functionality of Parking Lock without
reporting to the server.
After triggering an event such as a shock or a movement, the sensor will be disabled for a while (for 30 seconds) so
as to avoid sending to the server the same message as the first one repeatedly.
<About Threshold>
- Collision Threshold
Our recommendation is 0.7 but it is only for reference value obtained from our field testing made on real vehicles
(nearby gear).The value may vary in a real situation depending upon driving manner or condition of road. So, you
need to check this value.
- Shock Threshold
Our recommendation is 0.04 but it is only for reference value obtained from our field testing made on real vehicles
(nearby gear).Motion sensor is installed on an inside part of the vehicles body to measure sensitivity value(s) created
by vibration and shock impact given to the vehicle. Value of this sensitivity varies because it depends on what body
part of the vehicle the motion sensor is installed.
Shock Threshold is also used for checking movement of vehicle. So, the device may not be able to recognize if a
shock threshold value is too high. You need to consider these kinds of factors measurable under realistic environment
when you also adjust the values.
<Notes>
ON: Activation.
OFF: Deactivation.
Enable: Enable or Disable by setting.
X:Please, do not care.
[Caution]:Basically, the device checks any motions in parking mode(Ignition Off). It does not care about the enable
flags such as COLL_EN or SHOCK_EN. This means that, if the device senses any motion (movement) created in
the power down mode, it will exit from the power down mode as if a creature would wake up from sleeping suddenly.
So, if you want to check the power down mode to save power consumption of the backup battery, DO NOT give any
impacts to the vehicle.
For a period of duration that the vehicle has been in a parking mode for a long time by consuming vehicles battery
down to a very low level, the device starts entering the Deep Sleep Mode automatically. This situation happens
because the device intends to prevent vehicles battery from wasting power. In this case, the device alerts with
ALERT_ID 14 before entering the deep sleep mode, and exits from the deep sleep mode either when ignition line
goes to ON or until the voltage level is increased sufficiently.
The vehicles battery level for protection can be changed by making a Command. Refer to Voltage control parameters
section.
Route deviation is a function to track travelling route of the vehicle with the predefined route. It is useful for the
company to instruct the driver to drive the vehicle along a safe road or without getting out of the safe road(s). The
following picture shows you an example of the predefined route.
[Sample Route]
Setting Route
If number of positions exceeds 10 points, the command should be divided with 10 points as follows:
The last field of Gap should be 0. Our device provides many positions up to 500.
ST300CTR;xxxxxxxxx;02;1
If Route deviation is enabled, the device checks whether or not the vehicle is moving along the predefined route.
A sample shown hereunder shows you that the device is able to check if the vehicle is moving along the predefine
route as long as the vehicle in on motion is inside the gray-colored boundary.
When the vehicle gets out of the route or re-enters the route, the device alerts with Alert ID 18 and Alert ID 19 to the
server.
9-8. Anti-Theft
Anti-theft function available at the device is used to protect the vehicle from a risk of potential thefts by utilizing buzzer,
immobilizer and alerting to the server.
In order to use the function related with the anti-theft, the following basic conditions should be satisfied:
[Basic Conditions]
If one output event is set to immobilizer or buzzer, immobilizer or buzzer can be activated automatically when
emergency related with anti-theft occurs.
Activation/Deactivation
When the input is set to Anti-theft by command, anti-theft is enabled by default at first.
Activation/deactivation state of anti-theft can be checked by PresetA command.
Case of Anti-Theft
In a case that anti-theft button type is Anti-theft and that the device has a buzzer, the anti-theft function can be
activated or deactivated by pressing anti-theft button for more than 10seconds.If anti-theft button is pressed for 10
seconds in activation mode of anti-theft, anti-theft gets disabled by making the buzzer beep two times.
On the other hand, if anti-theft button is pressed as being disabled, anti-theft gets enabled by making the buzzer
beep just one time.
Case of Anti-Theft 2
In case that anti-theft button is set to Anti-theft2, anti-theft activation/deactivation cannot be changed by pressing
the anti-theft button. In that case, the anti-theft is always activated.
The anti-theft system in a vehicle without door sensor can be operated. The followings show you how it works:
1. About when the anti-theft system starts working? There are 2 different types of the start timing of the anti-theft
function as described below:
1.1 If your device (ST300) has been configured with the Anti-theft button, twenty (20) seconds later after the
vehicle is parked (ignition goes to off), the protection function starts working by making a beep just one
time.
1.2 If your device (ST300) has been configured with the Anti-theft2 button, twenty (20) seconds later after
the vehicle is parked (ignition goes to off), the protection function starts working silently.
2. After driving is started (ignition goes to on) in state of vehicle protection, the driver should press the anti-theft
button within the predefined time period of Delay of Anti-theft Release described in the New Parameter.
3. If the button is pressed for 1 second within this time period, the protection function is released. If the driver has
not pressed the button within this time period, anti-theft emergency of the device starts working immediately.
4. In emergency, the buzzer and the immobilizer are activated if they are connected properly. After the preset time
of Delay of Anti-Theft Alert, the device sends emergency report about anti-theft occurring.
5. However, you can stop such an emergency functioning of the device if you were not expecting such an
emergency. The followings are two (2) alternatives on how to stop functioning the Emergency:
Alt. 1. By pressing Anti-theft button for 1 second, the emergency situation can be stopped immediately.
Alt. 2. As soon as all the immobilizer and the buzzer start getting deactivated by commands of the Disable
Output, the emergency situation will be over.
The anti-theft system in a vehicle having door sensor can be operated. The followings show you how it works:
1. About when the anti-theft system starts working? There are 2 different types of the start timing of the anti-theft
function as described below:
1.1 Under an assumption that your device (ST300) has been configured with the Anti-theft button, twenty
(20) seconds later after the driver parks the vehicle (ignition goes to off), opens and closes the door, the
protection function starts working by making a beep just one time.
1.2 Under an assumption that your device (ST300) has been configured with the Anti-theft2button, twenty
(20) seconds later after the driver parks the vehicle (ignition goes to off), opens and closes the door, the
protection function starts working silently.
2. After the door is opened and closed in state of vehicle protection, the driver should press the Anti-theft button
within the predefined time period of Delay of Anti-theft Release described in the New Parameter.
3. If the button is pressed for 1 second within this time period, the protection function is released. If the driver has
not pressed the button within this time period, anti-theft emergency of the device starts working immediately.
4. In emergency, the buzzer and the immobilizer are activated if they are connected properly. After the preset time
of Delay of Anti-Theft Alert, the device sends emergency report about anti-theft occurring.
5. However, you can stop such an emergency functioning of the device if you were not expecting such an
emergency. The followings are two (2) alternatives on how to stop functioning the Emergency:
Alt. 1. By pressing Anti-theft button for 1 second, the emergency situation can be stopped immediately.
Alt. 2. As soon as all the immobilizer and the buzzer start getting deactivated by commands of the Disable
Output, the emergency situation will be over.
Door Protection
Door protection is operated if one (1) input is set to Door Sensor. This function is necessary to protect the vehicle
from unsafe occurrence events such as door-opening while driving the vehicle.
If the ignition goes to on in a situation of having a door opened, the device beeps two times just for notice. Once this
situation occurs, the driver should close the door and press the anti-theft button for 1 second within the predefined
time period, Delay of Anti-Theft Release of the New Parameter.
Otherwise, door sensor emergency of the device will start working and the buzzer and the immobilizer will be
activated.
If there is no pressing the Anti-theft button for the time period of Delay of Anti-theft Report, the device starts
sending to the server the report about the door sensor emergency.
By pressing Anti-theft button shortly (for 1 second), the emergency can be stopped and the immobilizer and the
buzzer can be deactivated.
Shock checking can be supported when the following conditions are satisfied:
In case that protection against anti-theft starts (with/without door sensor) and that the period of shock delay time
has passed, the shock protection starts working as well.
In a situation of the shock protection, if a shock is checked, the device activates the immobilizer and the buzzer if
they are connected properly. In such a situation, the device will also send the related emergency report to the server.
By pressing the anti-theft button shortly (for 1 second), the emergency situation can be stopped and the immobilizer
and the buzzer can be deactivated.
If the panic button is pressed, the anti-theft is deactivated temporarily to protect the driver from robbery in a dangerous
situation. Once the anti-theft is deactivated, the anti-theft can be activated only by making a command named
RestartAntiTheft2.
Device has maximum storage capacity of the un-sent reports in such cases as follows:
50 emergency reports,
1500 bytes for the response that the command has required the device to respond with as command
response
Note (**):
Due to bad report-routing environment, device could not make a real-time based reporting. For example,
the reporting router does neither run properly, is nor connected properly. In such a situation there might be
a report which has consequently failed to arrive in the server successfully after making several attempts to
send the report to the server. In that case, the device stores such a report for a while until such environment
(e.g. GPRS network) gets back to normal to enable the device to try to send the report to the server again.
When status reports start being accumulated, max 2000 reports can be hold in the buffer storage of the
device. If those status reports are triggered out to the server, the oldest report is erased first and a new
report is buffered if the buffer is completely full of those reports. And then, a new status report enters (FIFO:
First In First Out as a sequential system).
RPM Calibration
1. Turn ON and turn OFF ignition line (blue line)9 times continuously.
On(1st) Off(2nd) ON(3rd) Off(4th) ON(5th) Off(6th) On(7th) Off(8th) On(9th)
2. Wait during 5 seconds.
3. And GPRS LED (blue) blinks 0.5s continuously and GPS LED (red) is turned off.
4. Press accelerator keeping 2000RPM for 10seconds. It should be progressed within 3minutes.
5. As calibration is completed successfully, the GPRS LED illuminates. The LEDs return to normal mode after
turn off and on again. In case of fail, the device blinks the LED with normal method and Installer should
repeat calibration process from 1ststep.
Odometer Calibration
There are two ways to calibrate odometer automatically, by ignition line and by commands. Each calibration follows
below steps.
Calibration by ignition:
1. Wait until GPS is fixed (GPS LED (red) blinks one time).
1. Turn ON and turn OFF the blue line (ignition line)5 times continuously.
On(1st) Off(2nd) On(3rd) Off(4th) On(5th).
2. Wait during 5 seconds.
3. And, GPS LED (red) blinks 0.5s continuously and GPRS LED (blue) is turned off. If GPS has no enough
good condition, LEDs blinks with normal method.
4. Drive more than 1 km.
5. When the calibration is completed successfully, the GPS LED illuminates continuously. The LEDs return
normal way after turn off and on again. In case of fail after driving, the device blinks the LEDs normally and
installer should repeat calibration process from 1st step.
Calibration by commands:
9-11. I-button
The ST300H, the ST300A and the ST300K support reading I-button and supply related functions.
I-button looks like a coin and has a unique ID, 14 hex digits.
Once the device recognizes the I-button, this ID of the button is valid until the vehicle changes from driving to parking
although the I-button is removed. So, until the next parking, the device keeps reporting with this ID information and
approval of this ID from registration table forbids activation by driver ID.
.
Case 1)
1. When a registered I-button is inserted in parking mode, the buzzer beeps once (if buzzer is connected) and the
device sends alert (ID=59).
2. I-button is removed and the device sends alert (ID=60).
3. Device reports with the previous I-buttons ID, which is still valid.
4. Even if the vehicle turns into a driving mode, the output relating to the driver ID is not activated. Even though
the registered I-button is not inserted, the previous I-buttons ID is still valid.
5. As soon as the vehicle goes to a parking mode, the ID is removed.
Case 2)
1. When unregistered I-button is inserted in parking mode, the buzzer beeps once (if buzzer is connected) and the
device sends alert (ID=59).
2. The vehicle turns to driving, and the device activates the related output because the previous driver ID is not
available in the registration table.
3. The vehicle turns to parking, and the device releases the related output.
4. When the I-button is removed, the device sends alert (ID=60) and the ID field in the report is removed.
Driver ID can be registered up to 100 in the device. There are 2 methods for registration. One is done by command
and the other is done by the master I-button.
By utilizing I-button, the procedure on how to register Driver ID is taken by step-by-step instruction as follows:
Step 1. Please insert and remove the Master I-button (by adding the master / by removing the master).
Step 2. Please insert a new I-button within 10 seconds after removing it.
Step 3. Upon completing the procedure for the Step 1 and Step 2, the ID of I-button is registered or
deregistered automatically.
When a device with registered I-button is set to control immobilizer of a vehicle, only the drivers whose IDs have
been registered are allowed to drive the vehicle. If other drivers drive the vehicle, the device will activate the
immobilizer and the vehicle cannot be driven by those people. .
After the power of fuel sensor has been turned on, the sensor outputs the first RS232 data elapsed after 50
seconds. After the first data is output, the sensor outputs RS232 data every 10 seconds. (The sensor sample is
fixed to this condition by sensor firmware. It is a special feature of ESMUS01.)
[Alert Level]
If the ST300F detects rapid fuel level reduction from any of the fuel sensors, the ST300F makes an alert report.
The alert ID is 73.
If the ST300F detects rapid fuel level increased from any of the fuel sensors, the ST300F makes an alert report.
This alert ID is 80, and this application can use when you use Omnicomm fuel sensors.
This 1-Wire Temperature Sensor use Maxim DS18B20 digital thermometer solution, which is designed to
monitor the temperature of Refrigerator or Refrigerator car.
10.Appendices
10-1. How to convert the TEMPERATURE DATA(ZIP DATA) to the Celsius value.
If you use the ZIP option, you will be received data which is zipped like below.
<CODE>
float _celsius_temperature(unsigned short temperature)
{
unsigned short measure;
unsigned char negative;
unsigned char digit;
unsigned short decimal;
float fResult;
measure = temperature;
digit = (measure>>4);
//Store decimal digits
decimal=measure&0xf;
decimal*= 625;
//range -55 ~ +125
if(negative==0)
{
fResult = digit + ((float)decimal/(float)10000.0);
}
else
{
fResult = digit + ((float)decimal/(float)10000.0);
fResult *= -1;
}
return fResult;
}
CELSIUS = _celsius_temperature(0x01B4);
CELSIUS = 27.25
REVISIONS
Rev. No. Date Modifications were made on: Writer
Rev. 1.00 2012-12-05 Construct Protocol. Ronaldo
Rev. 1.01 2012-12-13 Changed Motion Setting, Main Voltage Setting Command. KJH
Rev. 1.02 2012-12-17 General review and changed some details. Ronaldo
Rev. 1.00 2013-01-18 Create ST215 Standard spec. HG.Park
Rev. 1.01 2013-02-13 Add comment: alert 40,41,44,45 are optional. HG.Park
Rev. 1.02 2013-04-02 SW Version allocation byte changed from 1byte to 2bytes in case of Zip packet. SE.Park
Rev. 1.03 2013-04-17 Add missed tracking function description from old spec. HG.Park
Rev. 1.04 2013-05-23 Remove profile ID in tracking function. Its customized option. HG.Park
Rev. 1.05 2013-06-10 Add Hands-free kit options. SE.Park
Rev. 1.06 2013-06-25 Review whole the document. DY Jeong
Rev. 1.20 2014-01-25 ST300 : Replace whole document Which was proofread by Mr.Lee HG.Park
Ref. OperationDescription_ST215_ST240_STADV_SUNTECHBR_V112.odf
Rev. 1.22 2014-01-27 Change Event pin configure / add MODEL field in SMS report format. HG.Park
Modify anti-theft description / Proofreading. Sam.Lee
Rev. 1.23 2014-02-03 Clear Errata. HG.Park
Rev. 1.24 2014-02-04 Remove HBM_STT field in New Parameter Setting. Requested by SB. HG.Park
Rev. 1.25 2014-02-20 Include ignition in IN1_TYPE. Ronaldo
Rev. 1.26 2014-02-21 Include Protocol Setting. Ronaldo
Rev. 1.27 2014-02-26 Rearrange about protocol setting & satellite parameter setting. SA Kim
Rev. 1.28 2014-03-19 Include AT Commands from RS232. Ronaldo
Rev. 1.29 2014-04-23 Include ST300H setting. Ronaldo
Rev. 1.30 2014-04-28 Add travel events zip report. SA Kim
Rev1.31 2014-05-19 Change copyright. HG. Park
Rev1.32 2014-10-20 Modified for Gabriel comments. HGPARK
Rev1.33 2014-11-04 Arranged document with Sam SA Kim
Rev 1.34 2014-11-13 Added related on driver pattern SA Kim
Rev 1.35 2014-11-28 Cleared table error SA Kim
Rev 1.35A 2014-12-05 Added 300V model SA Kim
Rev 1.35B 2014-12-17 Changed Event in3 type SA Kim
Rev 1.35C 2014-12-22 SA Kim
Zip Table
Rev 1.35D 2014-12-26 Changed ordering manner of the report fields for ST300A SA Kim
Deleted the commands relating to Shutdown
Rev 1.36 2014-12-30 Added STGPS Req. SE Park
Added Polygon geo-fence SA Kim
Added some Single commands..
Rev 1.37 2015-01-10 Clear errata HGpark.
Rev 1.38 2015-04-02 Change Idle to Parking and Active to Driving JK Kim
Rev 1.39 2015-05-01 Added Temperature Sensor function and description SE Park
Rev 1.40. 2015-05-06 Add Dont use software flow control, if use RS232. script in Chapter 4-3, 6-7, 6-8. JK Kim
Fix Chapter 6-5 ST300K explain.
Add script for Immobilizer2 in Chapter 9-1-2.
Rev 1.41 2015-05-26 Added input1 type Use Coin Machine in Chapter 4-3. JK Kim
Added input1 chattering time description in Chapter 4-3.
Added Coin Machine Parameter in Chapter 4-18.
Added STT Report field TOTAL_COIN in Chapter 6-1-1.
Added COI Report in Chapter 6-11.