Protocol Document For OT10 (OBDII) ITL FW Version V3.5 2017-03-23

WONDE PROUD TECHNOLOGY.
Protocol Document for Leasing Plan (OBDII)
Version: V3.5
Status: Preliminary
Date: 2017-03-23
Table Of Content
1. Protocol Revision History ....................................................2
2. Firmware Modification History ...........................................3

2.1 For OT10 ITL (2G) ............................................................................................. 3
2.2 For OT10 ITL (3G) ............................................................................................. 4
3. Parameter Format for Returning Message ..........................5

3. 1 Power up Message .......................................................................................... 5
3.2 Position Strings: ............................................................................................... 7
3.2.1 Regular String Format ........................................................................... 7
3.2.2 Report for “Engine On” and “Engine off” Events .................................. 9
3.2.3 Timer Report ....................................................................................... 10
4. Power Saving Function ..................................................... 11
5. Towing Detection ............................................................. 11
6. Command List: ................................................................. 12
7. Command Description ...................................................... 14
8. Report ID List ................................................................... 79
9. LED Indicator: ................................................................... 81
10. FTP OTA Instruction & Command Sets ............................. 82

10.1 Preparation .................................................................................................. 82
10.1.1 FTP Server ......................................................................................... 82
10.1.2 Device:............................................................................................... 82
10.2 Brief Instruction ........................................................................................... 82
P1
1. Protocol Revision History
Version Description
V3 Added 3G version
V3.1 Updated firmware modification history.
V3.2 1. Added the CSQ value in the end of the position string.
2. Added $HTRACK command.
V3.3 1. Changed the default settings for “Indigo GPS” project for all
command sets.
2. Added the $LAST+SPEED to show the speed for previous 29 seconds
In the $TRACK command based on 30 seconds tracking time
interval.
V3.4 Released the firmware version OT_1.042ITL_EHS5_Rev01
V3.5 1. Modify the returning position format (adding engine coolant
temperature)
2. Modify the $DTC3 and $DTC7 command response.
P2
2. Firmware Modification History

2.1 For OT10 ITL (2G)
Date Firmware Version Description

Initial ITL FW. This FW is based on NIA protocol, but
added on the following functions:
OT_1.027ITL_
1. OBDII and SACC mode auto-switch.
Rev01
2. IG on/off triggering condition for SACC mode is
referring to voltage changing only regardless the G-
sensor and GPS speed status.
1. Change the “Error code” parameter in the event ID
OT_1.029ITL_
100 to an “Error code indicator (0 or 1)”.
Rev01
2. Added $WP+DTC3 and $WP+DTC7 commands.
OT_1.030ITL 1. Support new G-Sensor
REV.02 2. Increase the $FC support range from 0.1~2.0
OT_1.031ITL_ Fixed the improper GPS working behavior when enter
Rev01 sleeping mode.
1. Added $WP+HTRACK command,
OT_1.032ITL_
2016.6.7 2. Added CSQ information in the end of the position
Rev01
string.
1. Add “Engine coolant temperature” in the position
OT_1.043ITL_EHS
2017.03.23 message.
5_Rev01
2. Modify the response of $DTC3 and $DTC7 command.
P3
2.2 For OT10 ITL (3G)
Date Firmware Version Description

OT_1.033ITL_3G_ Base on OT_1.034ITL_SLITE_3G, this version only for
Rev03 2G network
OT_1.034ITL_3G_Rev01 Modified the $GBLAC command to support 3G
network.
2016.6.7 OT_1.035ITL_3G_Rev01 1. Added $WP+HTRACK command,
2. Added CSQ information in the end of the position
string.
2016.12.3 OT_1.037ITL_3G_REV.01 1. Changed the default settings for “Indigo GPS”
project.
2. Added $LAST_SPEED function (display previous
speed
for each second in the $TRACK message.
2017.01.16 OT_1.038ITL_3G_Rev01 1. Added the $INFO=CSQ message in the binary mode
returning message.
2. Changed binary returning message prefix from ‘#’ to
“$#”
Added the previous speed for each second presenting
in $LAST_SPEED=1st speed, 2nd speed, 3rd
OT_1.042ITL_EHS5_
2016.01.19 speed, ……29th speed when a tracking message is
Rev01
generated every 30 seconds (the 30th speed will be
referred to the speed in the tracking message).
P4
3. Parameter Format for Returning Message

There are two different formats for returning messages. One is generated
automatically when unit powers up every time, another is for regular position
reporting.
3. 1 Power up Message
 Vehicle VIN# is available:
Unit_ID, IMEI, SIM_Serial_Number, New_VIN No., Vehicle Signature,
Battery Level, Backup Battery Voltage, Telco, CSQ
Vehicle VIN# is not available:
Unit_ID, IMEI, SIM_Serial_Number, 00000000000000000 (VIN NO.),
0000000000 ( Vehicle Signature), Battery Level, Backup Battery Voltage,
Telco, CSQ
Parameter definition of each parameter (for Power up Message):

 Unit ID: The identification code of the GPS Device (consist of 10 digits,
numerical characters only).
 IMEI number: International Mobile Equipment Identity of the GSM Modem
 SIM_Serial_Number: International Mobile Subscriber Identity
 New VIN No. :
VIN number of the current vehicle which device is installed. If VIN No. is
not available, this parameter will leave as blank.
 Vehicle Signature:
The Signature string consists of OBDII protocol identifier and “signature of
the vehicle will be displayed:
The string formation is the following:
%########
%: OBDII protocol identifier:
1 SAE J1850 PWM (41.6 Kbaud)
2 SAE J1850 VPW (10.4 Kbaud)
3 ISO 9141-2 (5 Baud Init)
4 ISO 14230-4 KWP (5 Baud Init)
5 ISO 14230-4 KWP (Fast Init)
6 ISO 15765-4 CAN (11 bit ID, 500 Kbaud)
P5

########: Vehicle Signature
 Battery Volts: current voltage level of the vehicle battery.

 Backup battery Voltage: current voltage level of internal backup battery.
 Telco: Telecommunication identity of current device register
 CSQ: signal strength quality of the telecommunication provider.
P6
3.2 Position Strings:
3.2.1 Regular String Format
Unit ID, Date/Time, Longitude, Latitude, Speed, Heading, No. Satellite, Event_ID,
Odometer, IG status, Data Type (Real time report or log), HDOP value, No. of
HA1, No of HA2, No. of HA3, No. of HA4, No. HA5, No. of HB1, No. of HB2, No.
of HB3,No. of HB4, No. of HB5, Max_Speed, RPM(0), Fuel Used since last
position, Engine coolant temperature $Info=CSQ,$LAST_SPEED=Speed of the 1st
second since last tracking message, speed of the 2nd second since last tracking
message, speed of the 3rd second since last tracking message,……….., speed of
the 29th second since last tracking message.
Note:
The $LAST_SPEED information will only be carried by $TRACK message (ID 2)
Parameter definition of each parameter (for Power up Message):

 Unit ID: The identification code of the GPS device (consist of 10 digits,
numerical character only)
 Date/Time: Date and Time of the captured Data generated by GPS
device.
 Longitude: longitude of the GPS coordinates
 Latitude: GPS latitude of the GPS coordinates
 Speed: vehicle speed from GPS speed.
 Heading: directions in degrees (0~359) of GPS.

 No. Satellite: the number of satellites used for this position data.
 Event ID: Event identifier.
 Odometer: vehicle trip meter, the calculation is based on the G
 IG status: Vehicle ignition status
0: Ignition off.
1: Ignition on.
 Date type:
0: Real time reporting.
1: Data is from the device internal logging memory.
P7
 HDOP value: Horizontal Dilution of Precision of GPS information.

 No. of HA1: number of Level 1 Harsh Acceleration Event generating
since last position
since last position
since last position
since last position
since last position
 No. of HB1: number of Level 1 Harsh Braking Event generating since
last position
last position
last position
last position
last position
 Max Speed: the highest speed since last position.
 RPM: the current RPM when the position report is generated.
 Fuel Used: fuel consumption since last position (in milliliter)
 $Info=CSQ value: the CSQ value when the position string generated.
 $LAST_SPEED= Speed of the 1st second since last tracking message,
speed of the 2nd second since last tracking message, speed of the 3rd
second since last tracking message,……….., speed of the 29th second
since last tracking message.
P8
Note:
1. The following counter will be reset each time when unit generates a tracking
report (ID 2), they will not be cleared if the position message with ID
other than 2.
 Odometer
 No. HA1
 No. HA2
 No. HA3
 No. HA4
 No. HA5
 No. HB1
 No. HB2
 No. HB3
 No. HB4
 No. HB5
 Max_Speed
 Fuel Used
2. Total number of times of harsh braking or harsh acceleration for each trip
will be accumulating at the server software.
3.2.2 Report for “Engine On” Events
There is a extra parameter in the end of the position string that is the
“Error code” read from the OBDII
The format is the following:

Unit ID, Date/Time, Longitude, Latitude, Speed, Heading, No. Satellite,
Event_ID, Odometer, IG status, Data Type (Real time report or log), HDOP
value, No. of HA1, No of HA2, No. of HA3, No. of HA4, No. HA5, No. of HB1,
No. of HB2, No. of HB3,No. of HB4, No. of HB5, Max_Speed, RPM(0), Fuel
Used since last position(0.000), engine coolant temperature,OBDII error
code identifier (0: No Error Code available; 1: Error code is available)
P9
3.2.3 Timer Report
There is an extra parameter in the end of the position string that is the
“ Firmware version of this device loaded”.
The format is the following:

Unit ID, Date/Time, Longitude, Latitude, Speed, Heading, No. Satellite,
Event_ID, Odometer, IG status, Data Type (Real time report or log), HDOP
value, No. of HA1, No of HA2, No. of HA3, No. of HA4, No. HA5, No. of HB1,
No. of HB2, No. of HB3,No. of HB4, No. of HB5, Max_Speed, RPM(0), Fuel
Used since last position(0.000), Engine coolant temperature,FW version
P 10
4. Power Saving Function

Device will enter sleeping state after 10 minutes of engine switching off
and wake up as soon as detects engine switching ON.. .
Unit status when it is in sleeping state:
Components Status
GSM Comm. Off
GPRS Comm. Off
GPS reception Off
G-Sensor On
OBDII Data Checking On
5. Towing Detection
Towing alert will be generated if device detects movement/vibration for 30
seconds continuously after “Engine Off” report is generated without report ID 44
event (device unplugged event) generated.
P 11
6. Command List:
Command Description
$WP+UNCFG Set/Read device ID, Password, PIN Code of the SIM card.
$WP+COMMTYPE Set/Read device communication type and its parameters
$WP+GETLOCATION Get current position of the device
$WP+TRACK Enable/disable/read tracking function to the device
$WP+REC Enable/disable/read logging function to the device
$WP+CLREC Erase all logging data from the memory of the device
$WP+DLREC Download entire/selective logging data from the memory of the device
$WP+SPDLREC Stop downloading logging data from the device.
$WP+REBOOT Restart up the device
$WP+RESET Reset all parameters to the manufactory default settings
Set default event for input, main power low/lost, and voltage level of
$WP+SETDR
internal battery
$WP+AVL Alignment the voltage reading of the device
$WP+QBCLR Clear the queue buffer of the device.
$WP+IMEI Query the IMEI number of the internal GSM module
$WP+SIMID Query the identification of the SIM card
$WP+VER Query the current firmware version.
$WP+SPD Enable/disable/read over-speed event
$WP+TMRR Enable the function of daily report
$WP+HALV Enable/disable “Harsh Acceleration” detection
$WP+HBLV Enable/disable “Harsh Braking” detection
$WP+ESB Enable/disable “Impact” detection
$WP+ESBC Enable/Disable the report for “Impact Event” confirmation
$WP+RPM Enable/disable “excessive RPM detection
$WP+ODM Set/query total mileage travelled (odometer)
$WP+FC Set/query the total fuel used for a trip.
$WP+VIN Query VIN information of the vehicle
$WP+GSMINFO Query the information about the GSM communication information
$WP+DLESBC Download the logs from the “Security Memory” for “IMACT” logs
$WP+CLESBC Clear the data for “Security Memory”
P 12
Command Description
$WP+OBDII Configure the OBDII reading behavior
$WP+PUM Query the Power Up Message
$WP+IFUC Memorizing OBDII communication protocol
$WP+DTC3 Query “Stored Diagnostic Trouble Codes”
$WP+DTC7 Query “Pending Diagnostic Trouble Codes”
$WP+OBDPLUG Enable/Disable device plug/unplug event.
$WP+GBLAC Query CELLID information that the device registered currently.
$WP+HTRACK Tracking message generating by GPS “heading” condition.
$WP+SETTOW Enable/Disable the “Towing Alert”
$WP+FTPSET Set up the FTP server information
P 13
7. Command Description
$WP+UNCFG
Description Execute this command to configure the device ID, device password, PIN code of
the SIM card, and the delay time for input ports (input 1~4).
Format $WP+UNCFG+[Tag]=[Password],[Device ID],[New Password],
Write
[PIN code]
Read $WP+UNCFG+[Tag]=[Password],?
Response $OK:UNCFG+[Tag]= [Device ID],[New Password], [PIN code]
Error $ERR:UNCFG+[Tag]=[Error Code]
Response Please refer to appendix 8.2 for detailed error code descriptions.
Parameter The tag could consist of number or character string which can be
defined by user. The returning message will include the same tag
Tag and it is helpful to recognize the acknowledgements with
corresponding issued commands. This tag could be left as empty if
it is not used. (Max. 5 characters)
Password of the device. Only correct password can access the
device and change the configuration. The minimum length of
Password
character is 4 digits; maximum length of character is 10 digits. It
supports numerical characters only. Default password is “8888”
Device identification number. The maximum length is 10 digits.
Device ID
Only integer can be used. Default device ID is 1680000001
New
New password of the device. Default is “8888”
Password
The PIN Code of the SIM card. The maximum length is 8 digits.
PIN Code Note:
Please use “” to clear parameter.
Example Ex:
Issue command:
$WP+UNCFG=8888,1685000001,0000
Response:
$OK:UNCFG=1685000001,0000
P 14
Note 1) The SIM card will be locked by the TELCO if enter incorrect PIN code for 3
times then the PUK code is required. Please contact the local TELCO to unlock
the SIM card. Please use the Culler phone to unlock the PUK once the card is
locked.
P 15
$WP+COMMTYPE
Description Execute this command to set the primary communication type and its related
parameters.
Format $WP+COMMTYPE+[Tag]=[Password],[Comm_Select],
[SMS Base Phone No.],[CSD Base Phone No.],[GPRS_APN],
Write [GPRS_Username],[GPRS_Password],[GPRS_Server_IP_Address],[G
PRS_Server_Port],[GPRS_Keep_Alive Packet_Interval],
[GPRS_DNS IP address],[Data Format]
Read $WP+COMMTYPE+[Tag]=[Password],?
Response $OK:COMMTYPE=[Comm_Select],[SMS Base Phone No.],[CSD Base Phone No.],
[GPRS_APN],[GPRS_Username],[GPRS_Password],[GPRS_Server_IP_Address],
[GPRS_Server_Port],[GPRS_Keep_Alive Packet_Interval],[GPRS_DNS IP address]
Error $ERR:COMMTYPE+[Tag]=[Error Code]
Password
Set primary communication type:
1. GSM SMS communication
2. CSD: Circuit Switched Data communication
(Reserved, currently not support)
Comm_
3. GPRS UDP communication
Select
4. GPRS TCP/IP communication
5. USB port communication
Note:
Support COM numbers: COM 1~ COM 199 auto detection.
P 16
Base phone number for the GSM SMS base station. Maximum
SMS Base
length is 16 digits (could be ignored if uses GPRS communication).
Phone No.
Note: Please use “” to clear the parameter.
Base phone number for the GSM Circuit Switched Data
CSD Base
communication. Maximum length is 16 digits (could be ignored if
Phone No.
uses GPRS communication).
(Reserved)
Access Point Name for GPRS service (required for GPRS
communication)
GPRS_APN
The maximum length is 40 characters.
User name for GPRS service if applicable.
GPRS_User-
The maximum length is 31 characters.
name
GPRS_Pass- Password for GPRS service if applicable.
word The maximum length is 20 characters
Default setting: 0.0.0.0
1. Static IP address:
GPRS_Serve
format xxx.xxx.xxx.xxx (Please do not use virtual IP address)
r_
2. Host/Domain Name (GPRS_DNS server must be defined) for the
IP_Address
base station. The maximum length is 40 characters.
GPRS_Serve The port IP of the computer which the control center software is
r_ operating. The available range is from 1000~65535.
Port Default setting: 1000
GPRS Keep_Alive Packet is used to establish the GPRS connection
and maintain the GPRS connectivity between the device and the
base station. The range is between 0~65535 seconds.
GPRS_Keep
Default setting: 30 seconds
_Alive
Note:
Packet
Set to ‘0’ to disable sending GPRS Keep_Alive Packet. This
Interval
parameter will not send any Keep_Alive Packet to the control
center.
P 17
Domain Name System IP address. Please contact local ISP for the IP
GPRS_DNS address of DNS server. Please use the xxx.xxx.xxx.xxx as the format
Server for this parameter.
Default setting: 168.95.1.1
0: ASCII
Data Format
1: Binary (for position message only)
Example Ex1: GPRS TCP/IP with static IP address
Issue command:
$WP+COMMTYPE=8888,4,,,internet,,,60.210.45.68,1050,30,168.95.1.1
Response:
$OK:COMMTYPE=4,,,internet,,,60.210.45.68,1050,30,168.95.1.1
Ex2: If the control center use DNS name(Domain Name System) server
Issue command:
$WP+COMMTYPE=8888,4,,,internet,,,serverDNSNAME,6080,30,168.95.1.1
Response:
$OK:COMMTYPE=4,,,internet,,,serverDNSNAME,6080,30,168.95.1.1
Notes 1) If primary communication is GPRS then both parameters “SMSPhone No.”
and “CSD Phone No.” are not required.
2) The port number of GPRS_Server_Port parameter must be opened for the
control center software and not conflict with others port which is occupied
by OS or other software.
3) Please enable the GPRS service for the SIM card before start GPRS
configuration. Also, please obtain related information such as “Access Point
Name” (APN), user name (if applicable), and password (if applicable) for
GPRS configuration ($WP+COMMTYPE command).
4) The Static IP address is required for the GPRS communication. Sometimes
the failure of GPRS connection is caused by the firewall setting enabled.
5) The software developer must implement the function in the control center
software in which must echo back exact GPRS Keep_Alive packet back to the
device once the base station receives the GPRS Keep_Alive packet which was
sent from the device to confirm the GPRS connection.
P 18
6) The performance of the GPRS connectivity might be affected by the

Keep_Alive packet interval due to the TELCO policy for the dynamic IP
address source control. The optimized Keep_Alive Packet interval needs to be
tested in the local area in order to obtain the optimized interval (cost
effective).
7) Keep_Alive message format (Data transmission by Hex format) typedef struct
{
unsigned short Keep_Alive_Header;
unsigned short Keep_Alive_ID;
unsigned long Keep_Alive_Device_ID;
} Keep_Alivestruct;
Keep_Alive_Header is always 0xD7D0
Keep_Alive_ID is the sequence number for the Keep_Alive message
Keep_Alive_Device ID is the device identification number. The base station
could use this information to recognize the current holding dynamic IP for
each device.
Ex:, received Synchronization message following:

0xD0 0xD7 0x1A 0x01 0xC7 0x54 0x44 0x3C
Keep_Alive_Header = 0xD7 0xD0
Keep_Alive_ID = 0x01 0x1A (Decimal = 282)
Keep_Alive_Device_ID = 0x3C 0x44 0x54 0xC7 (Decimal = 1011111111)
8) If the control center software is installed in a computer which is located in
the “Intranet” then the parameter “GPRS_Server_IP” address should be the
external one which connects to the router and the parameter
“GPRS_Server_Port” should be the port number of the computer which is
assigned by the router. If the parameter “GPRS_Server_IP” address is using
“Virtual IP address” in the intranet then it will lead to the GPRS connection
failure.
P 19
9) If the device is configured under GPRS mode (GPRS UDP/TCP), the device will
send the acknowledgement for the receiving command or returning message
back to the GMS SMS base phone number once the device receives the
command from a GSM SMS phone number other than GSM SMS base phone
number. If the GSM SMS base phone number is not set then the device will
take the parameters but will not returning any message back to GSM SMS
base phone number or GPRS server.
10) Please be aware that if the GSM base phone number is not set, the device
has following behaviors:
- If the device receives any valid incoming command via GSM SMS, the device
will execute the command, but all acknowledgements or returning message
will NOT be sent and will be ignored.
- If the device is configured under GPRS mode (GSM base phone number is
set), if the device receives any valid incoming GSM command from a phone
number other than GSM base phone number then the device will execute
this command and return all acknowledgements and returning messages
back to the GSM base phone number.
11) If this command is issued over GSM SMS, please be aware the text length
limitation of the GSM message.
Default Settings:
Settings $WP+COMMTYPE=8888,?
$OK:COMMTYPE=4,,,telstra.m2m,,,210.50.2.215,8008,180,168.95.1.1,1
P 20
$WP+GETLOCATION
Description Execute this command to get current position of the device
Format Write $WP+GETLOCATION+[Tag]=[Password],
Response Unit ID, Date/Time, Longitude, Latitude, Speed, Heading, No. Satellite, Event_ID,
Odometer, IG status, Data Type (Real time report or log), HDOP value, No. of HA1,
No of HA2, No. of HA3, No. of HA4, No. HA5, No. of HB1, No. of HB2, No.of HB3,
No. of HB4, No. of HB5, Max_Speed, RPM, Fuel Used since last position.
Error $ERR:GETLOCATION+[Tag]=[Error Code]
Parameters The tag could consist of number or character string which can be
Password
Example Ex:
Issue command:
$WP+GETLOCATION=8888
Response:
1685000001,20170321082337,121.648426,25.060544,0,0,9,101,0.166,0,0,1.
01,0,0,0,0,0,0,0,0,0,0,23,0,0.000,46,$INFO=21
P 21
$WP+TRACK
Description Execute this command to enable automatically reporting current position to the
base station according to the parameter “mode” and related conditions.
Format $WP+TRACK+[Tag]=[Password],[Mode],[Time],[Distance],[Number
Write
of Tracking Times],[Track basis],[Comm_Select],[Heading]
Read $WP+TRACK+[Tag]=[Password],?
Response $OK:TRACK+[Tag]= [Mode],[Time],[Distance],[Number of Tracking Times],
[Track basis],[Comm_Select],[Heading]
Error $ERR:TRACK+[Tag]=[Error Code]
Password
0. Disable (Stop tracking)
1. Time mode:
The position information is sent to the base station according to
Mode
the required time interval, only whole number can be used.
Effective range for different communication types:
Effective range: 5~120 seconds.
Specify elapsed time interval to report current position. Default
Time
value is ‘0’. The effective range, please refer to the “mode”
Interval
parameters option ‘1’ => “Time mode”.
Distance
Reserved
Interval
Number of
Tracking Reserved
Times
P 22
0. Tracking report is sent ONLY IF GPS is fixed.

1. Tracking report is sent regardless the GPS signal reception
Track Basis 2. Track report is sent when ACC is on and GPS is fixed
3. Track report is sent when ACC is on regardless whether the GPS
signal is fixed or not.
Set the output communication channel:
1. GSM SMS communication
2. CSD: Circuit Switched Data communication (Reserved, currently
not support)
Comm_
3. GPRS UDP communication
Select
4. GPRS TCP/IP communication
5. USB port
Note:
Support COM numbers: COM 1~ COM 199 auto detectable.
Heading The effective value is from 10~90 degrees.
Example Ex:
issue command:
$WP+TRACK=8888,1,5,0,5,0,4,15
Response:
$OK:TRACK=1,5,0,5,0,4,15
Note 1) The mode 2, 3, 5, 7, and 8 require the GPS reception. If the GPS reception is
not stable then the accuracy will be decreased.
2) “Track basis” can be set to 1 or 3 when mode is set to 1, 4, 6, or 9.
Default Default settings is the following:
Setting Settings :
$WP+TRACK=8888,1,30,100,0,3,4,15
Behavior:
Tracking message will be generated every 30 seconds as soon as IG status
changing from 0 (off) to 1 (on) and stop sending tracking message as soon as IG
status changing from 1 (on) to 0 (off)
P 23
$WP+REC
Description Execute this command to enable automatically logging current position into the
memory of the device according to the parameter “Mode” and corresponding
conditions.
Format $WP+REC+[Tag]=[Password],[Mode],[Time],[Distance],[Number of
Write
Times],[Record Basis],[Heading]
Read $WP+REC+[Tag]=[Password],?
Response $OK:REC+[Tag]= [Mode],[Time],[Distance],[Number of Times],[Record basis],
[Heading]
Error $ERR:REC+[Tag]=[Error Code]
Response: Please refer to appendix 8.2 for detailed error code descriptions.
Password
0. Disable (Stop storing position data into flash memory)
1. Time mode:
The position information is logged into the memory of the
Mode device according to the required time interval, only integer can
be used.
Effective parameters:
Range: 1~120 seconds.
Specify elapsed time interval to report current position. Default
Time
Interval
parameters option 1 “Time mode”.
Specify elapsed distance interval to report current position. Default
Distance
Interval
parameters option 2 “Distance mode”.
P 24
Frequency (number of times the report needs to be sent). Effective

range is from 0~65535.
Set ‘0’ indicating “Continuously logging”.
Number of
Note:
Times
The counter of “Times” will be displayed how many times left while
the command is executing when we query the command
parameters.
0. Logging function is executed ONLY IF GPS is fixed.
1. Logging function is executed regardless the GPS signal reception.
Record
2. Logging function is executed when ACC is on and GPS is fixed.
Basis
3. Logging function is executed when ACC is on regardless whether
the GPS signal is fixed or not.
Heading The effective value is from 10~90 degrees.
Example Ex:
Issue command:
$WP+REC=8888,1,5,0,0,0,15
Response:
$OK:REC=1,5,0,0,0,15
Note 1) This function follows the FIFO (first in first out algorithm) algorithm.
Default Default settings is the following:
Settings Settings
$WP+REC=8888,1,1,0,0,3,0
Behavior
Device will record a position message as soon as IG stats changing from 0 (Off)
to 1 (On) and stop recording as soon as IG status changing from 1 (On) to 0 (Off)
P 25
$WP+CLREC
Description Execute this command to erase all logging data from the memory of the device.
Format $WP+CLREC+[Tag]=[Password]
Response $OK:CLREC+[Tag]=OK
Error $ERR:CLRREC+[Tag]=[Error Code]
Password
Example Ex:
Issue command:
$WP+CLREC=8888
Response:
$OK:CLREC
P 26
$WP+DLREC
Description Execute this command to download request logging data from the memory of the
device
Format Write $WP+DLREC+[Tag]=[Password],[Start Date/Time],[End Date/Time]
Read $WP+DLREC+[Tag]=8888,?
Response For Write command:
Command acknowledgement:
$OK:DLREC+[Tag]=[Start Date/Time],[End Date/Time]
Download task completes:

$MSG:$Download Completed
For Read command:
$OK:DLREC=number of logs (Start Date ~ End Date)
Ex:
$OK:DLREC=388(20070522074235~20070522074907)
Error $ERR:DLREC+[Tag]=[Error Code]

Password
Start Format of this parameter: YYYYMMDDHHMMSS or ‘0’ (please refer
Date/Time to the “Note” section for detail)
End Format of this parameter: YYYYMMDDHHMMSS or ‘0’
Date/time (please refer to the “Note” section for detail)
P 27
Example Ex:
Issue command:
$WP+DLREC=8888,0,0
Response:
$OK:DLREC=0,0
1680000001,20130124072456,25.057696,121.634545,0,244,8,2,0.003,1,0,
1.48,0,0,0,0,0,0,0,0,0,0,0,675,0.010
1680000001,20130124072526,25.057686,121.634541,0,244,9,2,0.000,1,0,
0.95,0,0,0,0,0,0,0,0,0,0,0,562,0.008
1680000001,20130124072556,25.057668,121.634495,0,242,8,2,0.003,1,0,
1.53,0,0,0,0,0,0,0,0,0,0,0,600,0.009
1680000001,20130124072626,25.057408,121.633921,2,240,8,2,0.056,1,0,
1.00,1,1,0,0,0,1,0,0,0,0,2,612,0.015
1680000001,20130124072656,25.057391,121.633878,0,243,8,2,0.001,1,0,
1.00,0,0,0,0,0,0,0,0,0,0,0,612,0.009
1680000001,20130124072726,25.057390,121.633880,0,243,8,2,0.000,1,0,
0.94,0,0,0,0,0,0,0,0,0,0,0,600,0.009
1680000001,20130124072756,25.057348,121.633813,0,242,7,2,0.007,1,0,
1.16,1,0,0,0,0,0,0,0,0,0,0,612,0.010
1680000001,20130124072826,25.057346,121.633813,0,242,7,2,0.000,1,0,
1.15,0,0,0,0,0,0,0,0,0,0,0,987,0.009
1680000001,20130124072856,25.056253,121.635164,56,112,9,2,0.268,1,
0,0.96,1,0,0,0,0,0,0,0,0,0,56,2112,0.046
1680000001,20130124072911,25.055764,121.637365,20,93,10,57,0.213,1,
0,0.84,0,0,0,0,0,2,0,0,0,0,0,1037,0.018
1680000001,20130124072926,25.055761,121.637553,0,91,8,2,0.008,1,0,
1.49,0,0,0,0,0,0,0,0,0,0,0,625,0.004
$Download Completed
Note 1) The downloading logs function is not available when the device is configured
the GSM SMS communication.
2) This command does not support resume function.
P 28
3) The value ‘0’ can be used for both parameters “Start Date/Time” and “End
Date/ Time”. The corresponding actions are following:
Start End Corresponding data will be

Date/Time Date/Time downloaded
Get entire logging data from the flash
0 0
memory
Download selective logging data from
Start
0 the “Start Date/Time” to the last
Date/Time
logging data in the flash memory
End
0 the first logging position data to the
Date/Time
“End Date/Time” logging data
Start End
the “Start Date/Time” to the “End
Date/Time Date/Time
Date/Time”
P 29
$WP+SPDLREC
Description Execute this command to stop downloading process
Format $WP+SPDLREC+[Tag]=[Password]
Response $OK:SPDLREC+[Tag]
Error $ERR:SPDLREC+[Tag]=[Error Code]
Password
Example Ex:
Issue command:
$WP+SPDLREC=8888
Response:
$OK:SPDLREC
P 30
$WP+REBOOT
Description Execute this command to reboot the device. All setting will be remained.
Format $WP+REBOOT+[Tag]=[Password]
Response $OK:REBOOT+[Tag]
Error $ERR:REBOOT+[Tag]=[Error Code]
Password
Example Ex:
Issue command:
$WP+REBOOT=8888
Response:
$OK:REBOOT
Note 1) Please re-establish the direct connection after issuing the $WP+REBOOT
command. The physically unplug and re-plug in the micro USB cable might be
necessary.
P 31
$WP+RESET
Description Execute this command to reset the device to factory default settings or pre-set
settings
Format Write $WP+RESET+[Tag]=[Password]
Response
$OK:RESET+[Tag]
Error $ERR:RESET+[Tag]=[Error Code]

Password
Example Ex:
Issue command:
$WP+RESET=8888
Response:
$OK:RESET
Note 1) The “Device ID” and “PIN code” parameters will remain the same after
executing this command. Other settings will be set back to factory default.
P 32
$WP+SETDR
Description Execute this command to enable/disable the power system monitoring
Format $WP+SETDR+[Tag]=[Password], [Low Voltage],[Polling],[Logging]
Response $OK:SETDR+[Tag]= [Low Voltage],[Polling],[Logging]
Error $ERR:SETDR+[Tag]=[Error Code]
Password
Set the voltage for the main power low report.
Low Voltage
Effective range: 0.00~30.00 V; Default voltage level: 11.50V
If any of specific report triggered then the report will be sent back
to the control center. This setting is based on the bitwise operation.
This parameter can specify what report would be available. The
bitwise definition is following (default setting:127) :
0. Disable
Polling 16. Main power low
32. Main power lost
64. Internal battery voltage low
256.Main power voltage recover
512.Main power recover
1024. Internal battery voltage recover
P 33
If any of specific report triggered then report will be stored into the
device memory and can be downloaded later. This setting is based
on the bitwise operation. This parameter can specify what report
would be available. The bitwise definition is following:
0. Disable
Logging 16. Main power low
32. Main power lost
64. Internal battery voltage low
256.Main power voltage recover
512.Main power recover
1024. Internal battery voltage recover
Example Ex:
Issue command:
$WP+SETDR=8888,12.00,1919, 1919
Response:
$OK:SETDR=12.00, 1919, 1919
Note 1) Each event has different report indication, below is the list of event name with
the corresponding Event ID:
Main power low: Event ID 40
Main power lost: Event ID 41
Main power low recover: Event ID 42
Main power lost recover: Event ID 43
Internal backup battery low: Event ID 46
Internal backup battery low recover: Event ID 47
2) For event detecting time, please refer to the following definitions:
a) Main Power low event: voltage level of the main power is lower than the
pre-defined voltage level (“Low Voltage” parameter in this command) for
30 seconds
b) Main power lost event: 5 seconds
c) Main power low recover event:
- IG on : 1 hour
- IG off : 30 minutes
P 34
d) Main power lost recover event: the voltage level is greater than 7.5V
e) Internal backup battery low event: voltage level is lower than 3.7V for 1
minutes
f) Internal backup battery low recover event: voltage level of internal back
battery is greater than 4V or greater than 3.7V for 30 minutes
continuously.
Default Settings
Setting $WP+SETDR=8888,11.00,1904,1904
Behavior
All listed detections in this command is enabled including the following:
 Main power low
 Main power lost
 Internal battery voltage low
 Main power voltage recover
 Main power recover
 Internal battery voltage recover
P 35
$WP+AVL
Description Execute this command to calibrate the difference between the voltage reading of
the device and the exact voltage level ice installation for the main power
detection. This action is suggested to be done after reset the device, uploading
the firmware, or installing a new device in order to increase the accuracy of
voltage reading.
Format Write $WP+AVL+[Tag]=[Password],[Measurement of Main Power Voltage]
Read $WP+AVL+[Tag]=[Password],?
Response $OK:AVL+[Tag]= [Current Voltage],[Voltage Level of Backup Battery],
Error $ERR:AVL+[Tag]=[Error Code]
Password
Measureme
nt of Effective range: 0.00~30.00V
Main Power
Voltage
Example Ex:
Issue command:
$WP+AVL=8888,12.70
Response:
$OK:AVL=12.70,4.02
Note The calibrated voltage level for the main power will be remained and it will not be
affected by device RESET or loading another FW version.
P 36
$WP+QBCLR
Description Execute this command to clear queue buffer
Format Write $WP+QBCLR+[Tag]=[Password]
Response
$OK:QBCLR+[Tag]
Error $ERR:QBCLR+[Tag]=[Error Code]

Password
Example Ex:
Issue command:
$WP+QBCLR=8888
Response:
$OK:QBCLR
P 37
$WP+IMEI
Description Execute this command to query the IMEI No. for the internal GSM module
Format $WP+IMEI+[Tag]=[Password]
Response $MSG:IMEI+[Tag]=IMEI No.
Error $ERR:IMEI+[Tag]=[Error Code]
Password
Example Ex:
Issue command:
$WP+IMEI=8888
Response:
$MSG:IMEI=357258004284081
P 38
$WP+SIMID
Description Execute this command to query the identification number of the SIM card
Format $WP+SIMID+[Tag]=[Password]
Response $MSG:SIMID+[Tag]=SIM card Identification No.
Error $ERR:SIMID+[Tag]=[Error Code]
Password
Example Ex:
Issue command:
$WP+SIMID=8888
Response:
$MSG:SIMID=87109834789209748618
P 39
$WP+VER
Description Execute this command to query the current firmware and hardware version of the
device.
Format $WP+VER+[Tag]
Response $MSG:VER+[Tag]=firmware version
Error $ERR:VER+[Tag]=[Error Code]
Example Ex:
Issue command:
$WP+VER
Response:
$MSG:VER=OT_1.035ITL_3G REV.01
P 40
$WP+SPD
Description Execute this command to enable the speeding event. If the vehicle speed is in/out
the speeding range (between minimum and maximum speed) for the certain time
period (Duration) then it will trigger the speeding event.
Format $WP+SPD+[Tag]= [Password],[Mode],[Minimum Speed],[Maximum
Write Speed],[Speeding Duration],[Speeding Mode],[Off-Speeding
Duration]
Read $WP+SPD+[Tag]=[Password],?
Response $OK:SPD+[Tag]= [Mode],[Minimum Speed],[Maximum Speed],[Speeding
Duration],[Output Port],[Output Control],[Speeding Mode],[Off-Speeding
Duration]
Error $ERR:SPD+[Tag]=[Error Code]
Password
This parameter is to define the actions when the conditions
become true. The following actions are available:
0. Disable
1. Logging:
When the conditions of the defined event are true then the
Mode device will store the current GPS position information for the
specify event into the memory.
2. Polling:
device will send the current GPS position information for the
specify event back to the base station.
P 41
3. Logging and Polling:

device will store the current GPS position information for specific
event into memory and send the event back to the base station as
well.
Minimum Set Minimum Speed.
Speed Valid range: 0~255 km/hr.
Maximum Set Maximum Speed.
Speed Valid range: 0~255 km/hr
The parameter defined the time duration to activate the speeding
Speeding event(Event ID 3).
Duration In Speeding Mode ‘0’, the range: 15~65535 seconds
In Speeding Mode ‘1’, the range: 0~ 65535 seconds
0: As the GPS speed is in the defined range, the device will send
Event ID 3 according to the defined duration continually.
1: Enter and End speeding reports:

Speeding
- As the GPS speed is in the defined range for the defined
Mode
duration,
Event ID 3 will be sent once.
- As the GPS speed is out the defined range for the defined
duration, Event ID 9 will be sent once.
The parameter defined the time duration to activate the off-
Off-
speeding event (Event ID 9).
speeding
In Speeding Mode ‘0’, this parameter is disabled.
Duration
In Speeding Mode ‘1’, the range: 0~ 65535 seconds
Example Ex:
Issue command:
$WP+SPD=8888,3,100,200,15,1,30
Response:
$OK:SPD=3,100,200,15,1,30
P 42
Note 1) If the Speeding mode ‘1’ is selected, when the conditions of speeding report
are satisfied (speeding) or not satisfied (no speeding), the report only
sending once.
For example, issue $WP+SPD=8888,1,60,120,15,0,0,1,30
If the vehicle speed is 70 KPH for 40 seconds, the Event (ID 3) would be sent
once in the first 15 seconds. Then if the speed is down to 40 KPH for 20
minutes, then the Event (ID 9) would be sent once in the first 30 seconds.
2) If we need only using one specific speed as the condition (send Event ID 3
above the speed for defined interval and send Event ID 9 below the speed for
defined interval) then we can set the specific speed condition in “Minimum
Speed” parameter and set the speed which is not possible to reach in the
“Maximum Speed” parameters.
For example, issue $WP+SPD=8888,3,120,255,15,0,0,1,30
The device will generate a Speeding Event (ID 3) as the vehicle speed is over
120 for 15 seconds and a Speeding Event (ID 9) as the vehicle speed is below
120 for 30 seconds.
3) If the “Speeding Mode” sets to ‘0’, like $WP+SPD=8888,3,120,255,15,0,0,0,0
then the speeding report (ID 3) will be sent every 15 seconds when the
vehicle speed is between 120 and 255 KPH continuously.
4) In the Speeding Mode ‘1’, the Event ID 9 will be sent if the ACC is off.
For example, issue $WP+SPD=8888,3,120,255,15,0,0,1,30. As the speed is
lower than 120 KPH for only 20 seconds but the ACC is off, the device will
generate an Event ID 9.
Default Setting:
Setting $WP+SPD=8888,3,135,250,5,1,10
Behavior:
- A speeding alert (Event ID 3) will be generated if speed is in the range
between 140 to 255 Km/h for 5 seconds
- A off speeding alert (Event ID 9) will be generated if speed below 140 Km/h or
above 255 Km/h for 10 second.
P 43
$WP+TMRR
Description Execute this command to set the time for reporting position in specific time. It can
be set up to 3 times per day.
Format $WP+TMRR+[Tag]=[Password],[Enable/Disable],[Timer 1],[Timer 2],
Write
[Timer 3]
Read $WP+TMRR+[Tag]=[Password],?
Response $OK:TMRR+[Tag]= [Enable/Disable], [Timer 1],[Timer 2],[Timer 3]
Error $ERR:TMRR +[Tag]=[Error Code]
Password
Enable/Disa 0.Disable
ble 1.Enable (at least one time should be set)
Format: HHMMSS (Time format: 24 hours)
Timer 1
Timer 2
Timer 3
Example Ex:
Issue command:
$WP+TMRR=8888,1,083000,””,163233
Response:
$OK:TMRR=1, 083000,,163233
Note TMRR position report will append the firmware version to the end of the TMRR
string.
P 44
Default Setting
Setting $WP+TMRR=0000,1,020000,””,””
Behavior:
Device will generate a “TIMER” report sending to server at 2 am every day.
P 45
$WP+HALV
Description Execute this command to set up to 5 different thresholds for different harsh
acceleration levels and also define the action when event triggering.
Format $WP+HALV+[TAG]=[PWD],[HA Level Index],[Mode],
Write
[Speed Increasing Threshold],[Duration]
Read $WP+HALV+[Tag]=[Password],?
Response $OK:HALV+[Tag]= [HA Level Index],[Mode],[Speed Increasing Threshold],
[Duration]
Error $ERR:HALV +[Tag]=[Error Code]
Password
This parameter is to configure different threshold for 5 levels.
1: HA Level 1
HA Level 2: HA Level 2
Index 3: HA Level 3
4: HA Level 4
5: HA Level 5
This parameter is to define the mode for action when the event is
triggering.
0: Disable
Mode
1: Logging
2: Polling
4: Counting mode.
Speed
Increasing Effective range 5~250 Km/h
Threshold
P 46
Duration Effective range: 0~10 seconds.

Example Ex:
Issue command:
$WP+HALV=8888,2,3,1
Response:
$OK:HALV=2,3,1
Note 1) Report ID list :
The report ID for harsh acceleration level 1 is 66
2) The counter value will be reset after power is disconnected.
Default Settings/Behavior
Setting - $WP+HALV=8888,1,4,5,1
(HA 1 counter will increment by 1 if speed increases 5 Km/h in 1 second).
- $WP+HALV=8888,2,4,7,1
- $WP+HALV=8888,3,4,9,1
- $WP+HALV=8888,4,4,11,1
- $WP+HALV=8888,5,7,14,1
P 47
$WP+HBLV
Description Execute this command to set up to 5 different thresholds for different harsh
braking levels and also define the action when event triggering.
Format $WP+HBLV+[TAG]=[PWD],[HA Level Index],[Mode],
Write
[Speed Decreasing Threshold],[Duration]
Read $WP+HBLV+[Tag]=[Password],?
Response $OK:HBLV+[Tag]= [HA Level Index],[Mode],[Speed Increasing Threshold],
[Duration]
Error $ERR:HALV +[Tag]=[Error Code]
Password
This parameter is to configure different threshold for 5 levels.
1: HB Level 1
HB Level 2: HB Level 2
Index 3: HB Level 3
4: HB Level 4
5: HB Level 5
This parameter is to define the mode for action when the event is
triggering.
0: Disable
Mode
1: Logging
2: Polling
4: Counting mode.
Speed
Decreasing Effective range 5~250 Km/h
Threshold
P 48
Duration Effective range: 0~10 seconds.

Example Ex:
Issue command:
$WP+HBLV=8888,3,10,1
Response:
$OK:HBLV=3,10,1
Note 1) Report ID list :
The report ID for harsh braking level 1 is 61
2) The counter value will be reset after power is disconnected.
Default Settings/Behavior
Setting $WP+HBLV=8888,1,4,7,1
(HB 1 counter will increment by 1 if speed decreases 7 Km/h in 1 second).
$WP+HBLV=8888,2,4,11,1
$WP+HBLV=8888,3,4,14,1
$WP+HBLV=8888,4,4,18,1
$WP+HBLV=8888,5,7,22,1
P 49
$WP+ESB
Description Execute this command to detect “Impact” event
Format $WP+ESB+[TAG]=[Password],[Mode],[Speed Drop Threshold],
Write
[Duration]
Read $WP+ESB+[TAG]=[Password],?
Response $OK:ESB+[TAG]= [Mode],[Speed Drop Threshold],[Duration]
Error $ERR:ESB+[Tag]=[Error Code]
0: Disable
1: Logging
Mode
2: Polling
3: Logging + Polling
Speed Drop Effective range: 5~250 Km/h
Threshold
Duration Effective range: 0~10 seconds
Example Ex:
Issue command:
$WP+ESB=8888,3
Response:
$OK:ESB=3
Note Event ID for $WP+ESB command is “57”.
Default Setting
Setting $WP+ESB=8888,3,28,1
Behavior
“Impact” report will be sent to the server and store in memory if speed
decreases 35Km/h in 1 second.
P 50
$WP+ESBC
Description Execute this command to confirm the “Impact” event (Event ID 57).
Format $WP+ESBC=[PWD],[Report Action],[IG Off Detection Time
Write
Interval],[IG On Detection Time Interval]
Response $OK:ESBC+[TAG]= [Report Action],[IG Off Detection Time Interval],
[IG On Detection Time Interval]
Error $ERR:ESBC+[Tag]=[Error Code]
Password
This parameter is to define the actions need to be taken when all
the define condition becoming true:
Report 0: Disable
Action 1: Logging
2: Polling
IG Off
This parameter is the 1st condition which detects the IG status must
Detection
be changed from ON to OFF after generating event ID 57
Time
Effective range: 0~255 seconds.
Interval
IG On
This parameter is the 2nd condition which detects the IG status
Detection
must be remained OFF during this time interval.
Time
Effective range: 0~255 seconds
Interval
P 51
Example Ex :
Issue command:
$WP+ESBC=8888,3,60,60
Response:
$OK:ESBC=3,60,60
Note 1) The event ID for this “Impact Event” confirmation is “157”
2) The event ID 157 will be generated only if the both [IG On Detection Time
Interval] and [IG Off Detection Time Interval] are satisfied.
3) The event ID 157 will not be generated if ID 57 is not generated at first.
4) As soon as the event ID 157 is generated, the logging data between 60
seconds before and the time interval of IG off event after the event ID 57 will
be copied into a security memory sectors. They can be downloaded by the
$WP+DLESBC command and clear the memory by $WP+CLESBC command
Default Setting
Setting $WP+ESBC=8888,3,60,300
Behavior
The event ID 157 will be generated if IG status changes from ON to OFF within
the time interval of [IG Off Detection Time Interval] after event ID 57 and no IG
ON event occurred within the time interval of [ IG On Detection Time Interval].
P 52
$WP+RPM
Description Execute this command to enable the RPM abnormal alert
Format Write $WP+RPM+[TAG]=[Password],[Mode],[RPM Threshold],[Duration]
Read $WP+RPM+[TAG]=[Password],?
Response $OK:RPM+[TAG]= [Mode],[Speed Drop Threshold],[Duration]
Error $ERR:ESB+[Tag]=[Error Code]
0: Disable
1: Logging
Mode
2: Polling
RPM Effective range: 0~16000
Threshold,
Duration Effective range: 0~240 seconds
Example Ex:
Issue command:
$WP+RPM=8888,3,5000,10
Response:
$OK:RPM=3,5000,10
Note 1) Event ID for “Excessive RPM Alert” alert is 71.
Default Setting:
Setting $WP+RPM=8888,3,3000,10
Behavior:
An alert (ID 71) will be generated and store in memory If RPM exceeds
6000 for 10 seconds.
P 53
$WP+ODM
Description Execute this command to initial/query the odometer of the vehicle.
Format Write $WP+ODM=[PWD], [Odometer (KM)]
Query $WP+ODM=[PWD],?
Response $OK:ODM+[TAG]= [Odometer]
Error $ERR:ODM+[Tag]=[Error Code]
Password
This parameter has to functions:
1. Initial odometer value, the value will be started
Odometer accumulating afterwards.
(KM) 2. Given the current accumulated odometer when
receive querying request.
Effective range: 0.0~999999.9
Example Ex:
Issue command:
$WP+ODM=-0000,0.0
Response:
$OK:ODM=0.0
Note The odometer reading function only supports vehicle can output OBDII data. .
P 54
$WP+FC
Description Execute this command to initial/query the total fuel used information
Format Write $WP+FC=[PWD], [Fuel Used in Liter],[Coefficient]
Query $WP+FC=[PWD],?
Response $OK:FC+[TAG]= [Fuel Used in Liter],[Coefficient]
Error $ERR:FC+[Tag]=[Error Code]
Password
This parameter has two functions:
1. Initial total fuel used value, the value will be started
Fuel Used accumulating afterwards.
(Liter) 2. Given the current accumulated fuel used
information when receive querying request.
Effective range: 0.0~999999.9 (KM)
This parameter is to complement the accuracy of internal algorithm
comparing with the real fuel used.
Coefficient
Effective range: 0.1~2.0
Default value: 1
Example Ex:
Issue command:
$WP+FC=5.000,1.05
Response:
$OK:FC=5.000,1.05
P 55
Note 1) The command $WP+FC command is developed based on the vehicle using
gasoline. If the device is plugged on a vehicle using Diesel, please adjust the
coefficient in order to increase the accuracy.
P 56
$WP+VIN
Description Execute this command to query VIN number of the vehicle
Format Write $WP+VIN=[PWD]
Response $MSG:VIN+[TAG]=[VIN in text format],[VIN in Hex format]
Error $ERR:VIN+[Tag]=[Error Code]
Password
Example Ex 1 (VIN is available):
Issue command:
$WP+VIN=8888
Response:
$MSG:VIN=LFAAS0XXX52R01583,4C46414153305858583523031353833
Ex 2 (VIN is not readable)
Issue command:
$WP+VIN=8888
Response:
$MSG:VIN=7F2091012
Note 1) The VIN query function can only be functioning if OBDII function is supported
and engine is on.
2) Not all vehicles can read VIN information out even unit can identify the OBDII
protocol of the vehicle.
P 57
3) Alternative string for displaying vehicle identification when VIN is not available
is the following:
VIN%########XXXXX
%: OBDII protocol identifier:
1 SAE J1850 PWM (41.6 Kbaud)
########: available OBDII PIDs
This information consists of total 8 characters in Hex Decimal data
format.
XXXXX: Reserved (If the string appears in the VIN parameter, that
means the unit fails to read the VIN number from vehicle OBDII.
P 58
$WP+GSMINFO
Description Execute this command to query the Name of the operator, GSM signal strength,
GPRS connection status, and Roaming status.
Format $WP+GSMINFO+[Tag]=[Password]
Response $MSG:GSMINFO+[Tag]=[GSM Operator], [GSM signal strength], [GPRS
status],[Roaming Status]
GSM
Name of the Telecommunication corp.
Operator
This parameter indicates the signal strength
for GSM network. The closer the value
approaches to 31, the stronger the signal is.
CSQ dBm
GSM signal
0 -113dBm or less
strength
Parameter 1 -111dBm
2..30 -109…-53dBm
31 -51dBm or greater
99 not known or not detectable
0:GPRS is not connected
GPRS Status
1: GPRS is connected
Roaming 0: Currently is in home GSM/GPRS network.
Status 1: Currently is in roaming GSM/GPRS network
Error $ERR:GSMINFO+[Tag]=[Error Code]
Password
P 59
Example Ex:
Issue command:
$WP+GSMINFO=0000
Response:
$MSG:GSMINFO=”Chunghwa”, 18,1,0
Note The command is available after the device registered to the GSM/GPRS network.
P 60
$WP+DLESBC
Description Execute this command to download request logging data from the “Security”
memory of the device.
Format Write $WP+DLESBC+[Tag]=[Password],[Start Date/Time],[End Date/Time]
Read $WP+DLESBC+[Tag]=8888,?
Response For Write command:
$OK:DLESBC+[Tag]=[Start Date/Time],[End Date/Time]
Download task completes:

$MSG:$Download Completed
For Read command:
$OK:DLESBC=number of logs (Start Date ~ End Date)
Ex:
$OK:DLESBC=388(20070522074235~20070522074907)
Error $ERR:DLESBC+[Tag]=[Error Code]

Password
Start Format of this parameter: YYYYMMDDHHMMSS or ‘0’ (please refer
Date/Time to the “Note” section for detail)
End Format of this parameter: YYYYMMDDHHMMSS or ‘0’
Date/time (please refer to the “Note” section for detail)
P 61
Example Ex:
Issue command:
$WP+DLESBC=8888,0,0
Response:
$OK:DLESBC=0,0
1680000001,20130124072456,25.057696,121.634545,0,244,8,2,0.003,1,0,
1.48,0,0,0,0,0,0,0,0,0,0,0,675,0.010
1680000001,20130124072526,25.057686,121.634541,0,244,9,2,0.000,1,0,
0.95,0,0,0,0,0,0,0,0,0,0,0,562,0.008
1680000001,20130124072556,25.057668,121.634495,0,242,8,2,0.003,1,0,
1.53,0,0,0,0,0,0,0,0,0,0,0,600,0.009
1680000001,20130124072626,25.057408,121.633921,2,240,8,2,0.056,1,0,
1.00,1,1,0,0,0,1,0,0,0,0,2,612,0.015
1680000001,20130124072656,25.057391,121.633878,0,243,8,2,0.001,1,0,
1.00,0,0,0,0,0,0,0,0,0,0,0,612,0.009
1680000001,20130124072726,25.057390,121.633880,0,243,8,2,0.000,1,0,
0.94,0,0,0,0,0,0,0,0,0,0,0,600,0.009
1680000001,20130124072756,25.057348,121.633813,0,242,7,2,0.007,1,0,
1.16,1,0,0,0,0,0,0,0,0,0,0,612,0.010
1680000001,20130124072826,25.057346,121.633813,0,242,7,2,0.000,1,0,
1.15,0,0,0,0,0,0,0,0,0,0,0,987,0.009
1680000001,20130124072856,25.056253,121.635164,56,112,9,2,0.268,1,0,
0.96,1,0,0,0,0,0,0,0,0,0,56,2112,0.046
1680000001,20130124072911,25.055764,121.637365,20,93,10,57,0.213,1,
0,0.84,0,0,0,0,0,2,0,0,0,0,0,1037,0.018
1680000001,20130124072926,25.055761,121.637553,0,91,8,2,0.008,1,0,
1.49,0,0,0,0,0,0,0,0,0,0,0,625,0.004
$Download Completed
Note 1) The downloading logs function is not available when the device is configured
the GSM SMS communication.
2) This command does not support resume function.
P 62
$WP+CLESBC
Description Execute this command to erase all logging data from the security memory of the
device.
Format $WP+CLESBC+[Tag]=[Password]
Response $OK:CLESBC+[Tag]=OK
Error $ERR:CLESBC+[Tag]=[Error Code]
Password
Example Ex:
Issue command:
$WP+CLESBC=8888
Response:
$OK:CLESBC
P 63
$WP+OBDII
Description Execute this command to identify whether a vehicle OBDII is compatible with
OBDII data base also check the available PIDs can be used for OBDII function.
Format $WP+OBDII+[TAG]=[Mode],[InterfaceSet],[Get_Data_Timer],
Write
[ECU_Selection],[Enable/Disable the “Auto Scan” Function]
Read $WP+OBDII+[Tag]=[Password],?
Response $OK:OBDII+[Tag]=[Enable/Disable],[InterfaceSet],[Get_Data_Timer],
[ECU_Selection],[Enable/Disable the “Auto Scan” Function]
Error $ERR:OBDII+[Tag]=[Error Code]
Note
If FW can not identify the matched OBDII protocol interface, it will display the
following string (via USB only)
$OBD-II:Can`t find OBDII interface
Password
This command is to select different mode to either enable/disable
the OBDII data collection or check the supported PIDs
Mode 0: Disable
1: Enable the data collection
2: Check the PIDs availability
P 64
Interface 0 Auto Scan

Set 1 SAE J1850 PWM (41.6 Kbaud)
Get_Data_ This timer is indicating the waiting time interval before reading next
Timer OBDII string once receiving a complete OBDII string.
Effective Range: 0~65535 seconds
ECU This command is to define OBDII data is collected from which ECU
Selection inside vehicle.
Effective ECU number: 1~10
Default value: 1
Note:
ECU can only be referred one ECU at a time.
Enable/ This parameter is to enable/disable the OBDII “Auto Scan”
Disable the function.
“Auto Scan” 0: Set OBDII reading to Auto Scan.
Function 1: Set the OBDII reading protocol according to the parameter
“Interface Set” (Auto SCAN function will be disabled, this
parameter is used when user can identify the vehicle OBDII
protocol and communicating successfully).
Example Ex1:
Issue command:
$WP+OBDII=0000,1,0,5,1,1
Response:
$OK:OBDII=0000,1,0,5,1,1
Note 1) This function can be performed via direct communication (USB or serial port).
2) If [Interface Set] sets to 1~9 and [Enable/Disable the “Auto Scan” Function]
set to 0, the device will switch to “Auto Scan” if assigning protocol can not
read the OBDII data from the vehicle successfully.
P 65
3) If FW can identify any supported OBDII interface by using

$WP+OBDII mode 1, then the identified OBDII interface
will be displayed following by the command response. Please
refer to the following example (identified OBDII interface is
marked in blue):
Example:
Issue command:
$WP+OBDII=0000,1,0,5,
Response:
$OK:OBDII=1,0,5,1
$DBUG:WRITE_OBDII_INTERFACE
$OBD-II:READY=ISO 15765-4 (CAN 11/500)
$OBD-II:ECU_STD=EOBD (Europe)
$OBD-II:ECU_ID=0x7E8
4) Mode 2 can be performed only if OPBDII interface can be

identified by using $WP+OBDII mode 1.
After issuing $WP+OBDII=[PWD],2 then the following

table will be displayed:
------------------------------------------------------------------------------------
ECU 1 0x7E8 OBDII PID SUPPOR
-------------------------------------------------------------------------------------
PID | 1 2 3 4 5 6 7 8 9 A B C D E F NextPage
------------------------------------------------------------------------------------
0x00 | 1 0 0 1 1 0 0 0 0 0 1 1 1 0 1 1
0x10 | 1 1 0 0 0 0 0 0 0 0 0 1 0 0 1 1
0x20 | 1 0 1 0 0 0 0 0 0 0 0 0 0 0 0 0
0x30 | 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1
0x40 | 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 0
0x50 | 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 -------------------------------
-----------------------------------
P 66
To verify whether the required PIDs are supported or

not by the FW , it must check the PID indicator
(marked in red) is 0 (not supporting) or 1 (supporting).
How to identify the required PID availability, please follow the below steps:
Step 1:
Identify the HexDecimal value of PID one is looking
for.
Step 2:
To separate digit in tens (present in rows i.e.
0x00, 0x10, 0x20,..0x50) and digits in ones (present in
columns i.e. 1,2,3,4,5,……E,F). One may find the
request PID indicator (either 0 or 1) by locating the
intersection of the specific row and column.
If request PID is supported by the FW, then one needs to convert the Hex
Decimal value into Decimal value in order to define it in the $WP+SETPID
command.
Ex:
If “Engine RPM” is the parameter ID one is looking for, we
need to identify the Hex Decimal value for it, which is
“0C”, then separate the digit in tens and digits in
ones which is 0x00 and 0x0C, then we can locate the PID
indicator by locating the intersection of row “0x00” and
column ‘C’ (0x0C) which is ‘1’ as the result. Please refer to
the following illustration:
P 67
$WP+PUM
Description Execute this command to query the “Power Up Message”
Format $WP+PUM+[Tag]=[Password]
Response $OK:PUM+[Tag]=OK
Error $ERR:PUM+[Tag]=[Error Code]
Password
Example Ex:
Issue command:
$WP+PUM=8888
Response:
2000000125,356496042687566,89886920033011174764,,606DEA810,12.81,
4.08,"Chunghwa Telecom",11
P 68
$WP+IFUC
Description Execute this command to enable/disable the function of fixing the communicating
OBDII protocol.
Format $WP+IFUC+[Tag]=[Password]
Response $OK:IFUC+[Tag]=OK
Error $ERR:IFUC+[Tag]=[Error Code]
Password
Example Ex:
Issue command:
$WP+IFUC=8888
Response:
$OK:IFUC=0
Note 1) As soon as this command is enabled, the “working OBDII protocol” will
be stored in the FW and will be stick by the “working OBDII protocol” all
the time and the “OBDII auto-scan mechanism” will not be activated until
this command is disabled.
2) If the device is unplugged then plug it in to a non-OBDII supportive vehicle,
device will be switched to the SACC mode.
P 69
$WP+DTC3
Description Execute this command to query “Stored Diagnostic Trouble Codes”.
Format $WP+DTC3+[Tag]=[PWD]
Response Command
$OK:DTC3
ACK
- If there is no error code available, the following response will
be following by the command ACK:
Error code $MSG:NO DATA
Response - If there is error code available, the DTC codes will be presented
in the $MSG string
$MSG: DTC codes (separated by a space char)
Error $ERR:DTC3+[Tag]=[Error Code]
Response Please refer to appendix 9.2in the standard protocol for detailed error code
descriptions.
Password
Example Ex
Issue command:
$WP+DTC3=0000
Response:
$OK:DTC3=20170321082620,P0601,P0002,P0003,P0043,P0082,P00C1
Note If the OBDII communication can not be established, this command would have no
error message appear (no command ACK). Please ensure the OBDII reading
function is operating correctly before using this command. The RPM information
in other position message can be used for determining whether the ODBII reading
function is working or not.
P 70
$WP+DTC7
Description Execute this command to query “Pending Diagnostic Trouble Codes (detected
during current or last driving cycle)”.
Format $WP+DTC7+[Tag]=[PWD]
Response Command
$OK:DTC7
ACK
- If there is no error code available, the following response will
be following by the command ACK:
Error code $MSG:NO DATA
Response - If there is error code available, the DTC codes will be presented
in the $MSG string
$MSG: DTC codes (separated by a space char)
Error $ERR:DTC7+[Tag]=[Error Code]
Response Please refer to appendix 9.2in the standard protocol for detailed error code
descriptions.
Password
Example Ex
Issue command:
$WP+DTC7=0000
Response:
$OK:DTC7=20170321082616,P0401,P0702,P0703,P0743,P0700
Note If the OBDII communication can not be established, this command would have no
error message appear (no command ack, etc). Please ensure the OBDII reading
function is operating correctly before using this command. The RPM information
in other position message can be used for determining whether the ODBII reading
function is working or not.
P 71
$WP+OBDPLUG
Description Execute this command to enable/disable device unplug/plug-in events
Format Write $WP+OBDPLUG+[TAG]=[Password],[Enable/Disable]
Read $WP+OBDPLUG+[TAG]=[Password],?
Response $OK:OBDPLG+[TAG]= [Mode],[Enable/Disable]
Error $ERR:OBDPLG+[Tag]=[Error Code]
0: Disable
1: Logging
Enable/
2: Polling
Disable
Example Ex:
Issue command:
$WP+OBDPLUG=8888,2
Response:
$OK:OBDPLUG=2
Note 1) Event ID for “Device Plug in” event is 45
2) Event ID for “Device unplug” event is 44
P 72
$WP+GBLAC
Description Execute this command to query or set “auto-reporting” function of the close GSM
BTS location information
Format Write $WP+GBLAC+[Tag]=[Password],[Auto Mode]
Read $WP+GBLAC+[Tag]=[Password],?
Response Command $MSG:GBLAC+[Tag]= [Auto Mode]
Device ID, Date/Time, LAC (Location Area Code), CI (Cell ID)
Device ID Identification of the device
Date and Time
Report Date Time
Parameter (Base on the Time Zone setting)
LAC Location area code
CI Cell ID
Error $ERR:GBLAC+[Tag]=[Error Code]
Query This format only query the information once, no continuously event will be sent.
Format Query $WP+GBLAC+[TAG]=[PWD]
Response $MSG:GBLAC= Device ID, Date/Time, LAC, CI
Password
0: Disable
1: The event will be sent whenever the information (LAC and CI) is
Auto Mode changed regardless GPS reception
2: The event will be sent whenever the information (LAC and CI) is
changed if there is no GPS reception.
P 73
Example Ex 1:
Issue command:
$WP+GBLAC=0000,1
Response:
$OK:GBLAC=1
Ex2:
Issue command:
$WP+GBLAC=0000,?
Response:
$OK:GBLAC=1
Ex 3:
Issue Command:
$WP+GBLAC=0000
Response:
$MSG:GBLAC=2000011111,20150420102501,2829,01199CD0
P 74
$WP+HTRACK
Description Execute this command to enable/disable the tracking condition by using GPS
“heading”
Format $WP+HTRACK+[TAG]=[PWD],[Enable/Disable],[Heading
Write
Threshold],[Event ID assignment]
Query $WP+HTRACK=[PWD],?
Response $OK:HTRACK+[TAG]=[Enable/Disable],[Heading Threshold],[Event ID assignment]
Error $ERR:HTRACK+[Tag]=[Error Code]
Password
This parameter is the enable/disable this function
Enable/
0: Disable
Disable
1: Enable
Heading This parameter is to define the “heading” threshold:
Threshold Effective range: 1~359 degree
This parameter is to assign a specific event ID for the heading
Event ID
tracking event:
Assignment
Effective range: 1~255 (except ID 2)
Example Ex:
Issue command:
$WP+HTRACK=0000,1,30,155
Response:
$OK:HTRACK=1,30,155
P 75
Note 1. This function can be executed only if GPS is fixed.

2. The purpose of this position message is retrieved GPS related information,
please ignore the value displaying in the following parameters:
“ No. of HA1, No of HA2, No. of HA3, No. of HA4, No. HA5, No. of HB1, No. of
HB2, No. of HB3,No. of HB4, No. of HB5”. The correct values will be showing in
the next Tracking messages event ID 2
P 76
$WP+SETTOW
Description Execute this command to enable/disable Tow alert.
Format $WP+SETTOW+[Tag]=[Password], [Mode],[Satellite Fixed],
Write
[Speed threshold],[Tow Duration],[Auto Reset Duration]
Read $WP+SETTOW+[Tag]=[Password],?
Response $OK:SETTOW+[Tag]= [Mode],[Satellite Fixed],[Speed threshold],
[Tow Duration],[Auto Reset Duration]
Error $ERR:SETTOW+[Tag]=[Error Code]
Password
0.Disable
1.Logging
Mode
2.Polling
3.Logging + Polling
Satellite Effective range: 3~12
Fixed
Speed 10~255 km/hr
Threshold
Tow 30~65535 seconds
Duration
The Tow function will be re-enabled when reaching the end of
Auto Reset
“Auto Reset Duration” after the first tow event is triggered.
Duration
0~65535 seconds
Example Ex:
Issue command:
$WP+SETTOW=0000,3,3,10,30,10
P 77
Example Ex:
Issue command:
$WP+SETTOW=0000,3,3,10,30,10
Response:
$OK:SETTOW=3,3,10,30,10
Default Setting:
setting $WP+SETTOW=8888,?
$OK:SETTOW=3,5,15,30,0
P 78
8. Report ID List
Corresponding Remark
Event ID Description
command
0 Position data $WP+GETLOCATION
1 Logging position data $WP+REC
2 Track position data $WP+TRACK
3 Speeding Start Report $WP+SPD
4 Timer event $WP+TMRR
5 Tow event $WP+SETTOW
9 Speeding Stop Report $WP+OSC
40 Main Power Low Event $WP+SETDR
41 Main Power Lost Event $WP+SETDR
Main Power Voltage Recover
42 $WP+SETDR
Event
43 Main Power Recover Event $WP+SETDR
44 Device unplug event $WP+OBDPLUG
45 Device plug in $WP+OBDPLUG
Internal Backup Battery Voltage
46 $WP+SETDR
Low Event
Internal Backup Battery Voltage
47 $WP+SETDR
Recover Event
56 Harsh Braking (Level 5) $WP+HBLV
57 Impact event $WP+ESB
58 Harsh Acceleration (Level 5) $WP+HALV
71 Excessive RPM Alert $WP+RPM
P 79
Corresponding Remark
Event ID Description
command
100 Ignition On N/A Not configurable
101 Ignition Off N/A Not configurable
Impact Event Confirmation
157 $WP+ESBC
Report
P 80
9. LED Indicator:
Indicators Blinking Behavior Status

Not Ready or Searching GSM
0.6 second on/ 0.6 second off
signal
Registered to GSM network
GSM 100ms on / 3 seconds off
successfully
(Red)
GPRS is ready
Solid On (Server connection is
established)
1 second on / 1 seconds off GPS not fixed
Solid on GPS fixed
GPS
Enter Sleeping State
(Green)
100ms on/ 5 seconds off (Except mode 3 of $WP+PSM
command)
P 81
10. FTP OTA Instruction & Command Sets

10.1 Preparation
10.1.1 FTP Server
The FW file to be upgraded must be saved onto the FTP server before starting
FW upgrading over the FTP process.
1. The firmware file in “.fw” format.
10.1.2 Device:
Unit’s SIM card must support GPRS communication. Thus, the related
information must be set correct such as APN (Access Point Name), Use_Name
and Password for the GPRS.
10.2 Brief Instruction
1. Please use $WP+FTPSET command to set all necessary information and the FTP
OTA process will be started immediately.
2. The firmware process will be started automatically without disconnecting the

primary GPRS server after receiving $WP+FTPSET command,
Once the firmware upgrading process is completed, there are two messages
will be displayed to indicate the process is completed. These messages are the
following:
- $MSG: DOWNLOAD FIRMWARE OK
- $MSG: REBOOT & REFRESH
3. Please check if the firmware has been uploaded successfully by issuing

$WP+VER command after new GPRS session is established.
4. If the firmware upgrading process is interrupted due to any reason, the

process needs to be re-started again, this function does not
P 82
$WP+FTPSET
Description Execute this command to store user name, password, IP address, and File name
for FTP server.
Format $WP+FTPSET+[TAG]=[Password],[FTP_User_Name],[FTP_Password]
Write ,[FTP_IP address],[Name of firmware file],[Check_Sum of the FW
File]
Read $WP+FTPSET+[Tag]=[Password],?
Response $OK:FTPSET+[Tag]= [FTP_User_Name],[FTP_Password],[FTP IP address],[Name of
firmware file],[Check_Sum of the FW File]
Error $ERR:FTPSET+[Tag]=[Error Code]
Password
FTP_User User Name of FTP server
name Maximum length is 10 chars.
FTP_Passwo Password of FTP server
rd Maximum length is 10 chars.
FTP_IP IP address for the FTP server
address Format xxx.xxx.xxx.xxx (Please do not use virtual IP address)
Name of
The firmware file is going to load into the unit. The file must be in
firmware
“.fw” format.
file
Check_Sum
of the FW Check_Sum of the FW file which is going to be loaded into the unit.
File
P 83
Example Ex:
Issue command:
$WP+FTPSET=8888,wpftp,12345,203.74.1.200,OT_1.020NIA_Rev31.fw,DA75
Response:
$OK:FTPSET= wpftp,12345,203.74.1.200,OT_1.020NIA_Rev31.fw,DA75
Note 1) The “Check_Sum” information will be provided by Wonde Proud Corp.
2) If the OTA process gets interrupted and could not be success. The error
message “$ERR:FTPSET=error code” will be appeared.
P 84

Protocol Document For OT10 (OBDII) ITL FW Version V3.5 2017-03-23

Caricato da

Informazioni sul documento

Titolo originale

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

Protocol Document For OT10 (OBDII) ITL FW Version V3.5 2017-03-23

Caricato da

Copyright:

Formati disponibili

WONDE PROUD TECHNOLOGY.

Protocol Document for Leasing Plan (OBDII)

1. Protocol Revision History ....................................................2

2. Firmware Modification History ...........................................3

3. Parameter Format for Returning Message ..........................5

4. Power Saving Function ..................................................... 11

5. Towing Detection ............................................................. 11

6. Command List: ................................................................. 12

7. Command Description ...................................................... 14

8. Report ID List ................................................................... 79

9. LED Indicator: ................................................................... 81

10. FTP OTA Instruction & Command Sets ............................. 82

1. Protocol Revision History

2. Firmware Modification History

Date Firmware Version Description

2.2 For OT10 ITL (3G)

Date Firmware Version Description

3. Parameter Format for Returning Message

Parameter definition of each parameter (for Power up Message):

8 ISO 15765-4 CAN (11 bit ID, 250 Kbaud)

 Battery Volts: current voltage level of the vehicle battery.

3.2 Position Strings:

3.2.1 Regular String Format

Parameter definition of each parameter (for Power up Message):

 Heading: directions in degrees (0~359) of GPS.

 HDOP value: Horizontal Dilution of Precision of GPS information.

3.2.2 Report for “Engine On” Events

The format is the following:

3.2.3 Timer Report

The format is the following:

4. Power Saving Function

Unit status when it is in sleeping state:

6) The performance of the GPRS connectivity might be affected by the

Ex:, received Synchronization message following:

0. Tracking report is sent ONLY IF GPS is fixed.

Frequency (number of times the report needs to be sent). Effective

Download task completes:

Error $ERR:DLREC+[Tag]=[Error Code]

Start End Corresponding data will be

Error $ERR:RESET+[Tag]=[Error Code]

Error $ERR:QBCLR+[Tag]=[Error Code]

3. Logging and Polling:

1: Enter and End speeding reports:

Duration Effective range: 0~10 seconds.

Duration Effective range: 0~10 seconds.

Download task completes:

Error $ERR:DLESBC+[Tag]=[Error Code]

Interface 0 Auto Scan

3) If FW can identify any supported OBDII interface by using

4) Mode 2 can be performed only if OPBDII interface can be

After issuing $WP+OBDII=[PWD],2 then the following

ECU 1 0x7E8 OBDII PID SUPPOR

To verify whether the required PIDs are supported or

Note 1. This function can be executed only if GPS is fixed.

Indicators Blinking Behavior Status

10. FTP OTA Instruction & Command Sets

10.1.1 FTP Server

10.2 Brief Instruction

2. The firmware process will be started automatically without disconnecting the

3. Please check if the firmware has been uploaded successfully by issuing

4. If the firmware upgrading process is interrupted due to any reason, the

Potrebbero piacerti anche