GMT200 @track Air Interface Protocol V3.00 PDF

GMT200 @Track Air Interface Protocol
GSM/GPRS/GPS Tracker GMT200

@Track Air Interface Protocol
Application Notes: TRACGMT200AN003
Revision: 3.00
TRACGMT200AN003 http://www.queclink.com
–0–
sales@queclink.com
Document Title GMT200 @Track Air Interface Protocol
Version 3.00
Date 2014-12-10
Status Release
Document Control ID TRACGMT200AN003
k
General Notes
Queclink offers this information as a service to its customers, to support application and
i n
engineering efforts that use the products designed by Queclink. The information provided is
l l
based upon requirements specifically provided to Queclink by the customers. Queclink has
c a
not undertaken any independent search for additional relevant information, including any
i
information that may be in the customer’s possession. Furthermore, system validation of this
e t
product designed by Queclink within a larger electronic system remains the responsibility of
the customer or the customer’s system integrator. All specifications supplied herein are
u n
subject to change.
Q fide
Copyright
This document contains proprietary technical information which is the property of Queclink
Limited. The copying of this document, distribution to others, and communication of the
contents thereof, are forbidden without express authority. Offenders are liable to the payment
n
of damages. All rights are reserved in the event of a patent grant or registration of a utility
model or design. All specification supplied herein are subject to change without notice at any
o
time.
C
Copyright © Queclink Wireless Solutions Co., Ltd. 2012
TRACGMT200AN003 –1–
Contents
Contents ............................................................................................................................................ 2
0. Revision history ............................................................................................................................ 4
1. Overview ....................................................................................................................................... 5
1.1. Scope of This Document ..................................................................................................... 5
1.2. Terms and Abbreviation ...................................................................................................... 5
2. System Architecture ...................................................................................................................... 6
3. Message Description ..................................................................................................................... 7
k
3.1. Message Format .................................................................................................................. 7
3.2. Command And Acknowledgement ...................................................................................... 9
n
3.2.1. Server Connection ............................................................................................. 9
l i l
3.2.1.1. Bearer Setting Information........................................................................................... 9
3.2.1.2. Backend Server Register Information ........................................................................ 10
c ia
3.2.1.3. Quick Start Setting ..................................................................................................... 13
e t
3.2.2. Device Configuration ...................................................................................... 15
3.2.2.1. Global Configuration ................................................................................................. 15
u n
3.2.2.2. Auto-unlock PIN ........................................................................................................ 18
3.2.2.3. Time Adjustment ........................................................................................................ 20
Q fide
3.2.2.4. Protocol Watchdog ..................................................................................................... 21
3.2.2.5. Outside Working Hours.............................................................................................. 23
3.2.2.6. Jamming Detection .................................................................................................... 24
3.2.2.7. Non Movement Detection .......................................................................................... 26
n
3.2.3. Position Related Report................................................................................... 31
3.2.3.1. Fixed Report Information .......................................................................................... 31
o
3.2.3.2. Frequency Change of Fixed Report Information........................................................ 34
3.2.3.3. Preserve Special Device Logical State Setting ........................................................... 35
C
3.2.4. Alarm Settings ................................................................................................. 37
3.2.4.1. Geo-Fence Information .............................................................................................. 37
3.2.4.2. Tow Alarm Configuration .......................................................................................... 39
3.2.4.3. Speed Alarm............................................................................................................... 41
3.2.4.4. SOS Function ............................................................................................................. 43
3.2.4.5. Excessive Idling Detection......................................................................................... 44
3.2.4.6. Harsh Behavior Monitoring ....................................................................................... 46
3.2.4.7. Start Stop Report ........................................................................................................ 48
3.2.5. IO Application ................................................................................................. 50
3.2.5.1. Digital Output ............................................................................................................ 50
3.2.5.2. Digital Input Port Setting ........................................................................................... 51
3.2.5.3. Input/Output Port Binding ......................................................................................... 53
3.2.5.4. External Power Supply Monitoring ........................................................................... 54
3.2.6. Other Settings .................................................................................................. 56
3.2.6.1. Real Time Operation .................................................................................................. 56
3.2.6.2. Ignition Time Counter ................................................................................................ 58
3.3. Report ................................................................................................................................ 59
3.3.1. Position Related Report................................................................................... 60
3.3.2. Device Information Report.............................................................................. 69
3.3.3. Report of Real Time Querying ........................................................................ 72
3.3.3.1. +RESP:GTGPS .......................................................................................................... 72
3.3.3.2. +RESP:GTALL .......................................................................................................... 72
3.3.3.3. +RESP:GTCID .......................................................................................................... 88
3.3.3.4. +RESP:GTCSQ ......................................................................................................... 88
3.3.3.5. +RESP:GTVER ......................................................................................................... 89
3.3.3.6. +RESP:GTBAT.......................................................................................................... 90
3.3.3.7. +RESP:GTIOS ........................................................................................................... 90
k
3.3.3.8. +RESP:GTTMZ ......................................................................................................... 91
n
3.3.4. Event Report.................................................................................................... 92
i
3.3.5. Buffer Report................................................................................................. 106
l l
3.3.6. Report Google Maps hyperlink ..................................................................... 107
c a
3.4. Heartbeat ......................................................................................................................... 108
i
3.5. Server Acknowledgement................................................................................................ 109
e t
4. HEX Format Report Message ................................................................................................... 110
u n
4.1. Hex Report Mask ............................................................................................................ 111
4.2. Acknowledgement +ACK ............................................................................................... 116
Q fide
4.3. Location Report +RSP .................................................................................................... 119
4.4. Information Report +INF ................................................................................................ 127
4.5. Event Report +EVT......................................................................................................... 131
4.6. Heartbeat Data +HBD ..................................................................................................... 146
4.7. Buffer Report in HEX Format ......................................................................................... 148
n
Appendix: Message Index ............................................................................................................. 149
Co
0. Revision history
Revision Date Author Description of change

V1.00 2014-03-04 Bradom Dai Initial
V2.00 2014-10-21 Jerry Wang Modified default value of <+RSP Mask> and
<+EVT Mask> in AT+GTHRM
V3.00 2014-11-17 Jerry Wang 1. Add a new command AT+GTJBS to support
Jamming Behavior Setting function,which is based
on the “Jamming Detection”function.
k
2. Add a new command AT+GTWLT to support
white list for location by call and SMS functions.
i n
3. Add the sub command “F” into the command
l l
AT+GTRTO to reset jamming behavior.
c a
2014-12-10 Jerry Wang 1. Add Validity Time to Digital Input.
i
2. Modify the range of <Tow Interval>.
ue n t
Q fide
o n
C
1. Overview
1.1. Scope of This Document
The @Track Air Interface Protocol is a digital communication interface based on printable ASCII
characters over SMS or GPRS which is used for all communication between the backend server
and the terminal. The backend server sends a command to the terminal and then the terminal
k
confirms with an acknowledgement message. If necessary, the terminal also sends report messages
to the backend server.
i n
The purpose of this document is to describe how to build up the backend server based on the
l l
@Track Air Interface Protocol.
c ia
1.2. Terms and Abbreviation
ue n t
Abbreviation Description
Q fide
APN Access Point Network
ASCII American National Standard Code for Information Interchange
GPRS General Packet Radio Service
GSM Global System for Mobile Communications
HDOP Horizontal Dilution of Precision
n
ICCID Integrated Circuit Card Identity
o
IP Internet Protocol
SMS Short Message Service
C
TCP Transmission Control Protocol
UDP User Datagram Protocol
UTC Coordinated Universal Time
2. System Architecture
i n k l
cl ia
ue n t
The backend server can be accessed by many terminals and should have the following abilities:
 The backend server should be able to access the internet and listen to the connection
Q fide
originating from the terminal.
 The backend server should be able to support a TCP or UDP connection with the terminal. It
should be able to receive data from the terminal and send data to the terminal.
 The backend server should be able to receive and send SMS.
o n
C
3. Message Description
3.1. Message Format
All of the @Track Air Interface Protocol messages are composed of printable ASCII characters.
Each message has the following format:
Message format Message type
k
AT+GTXXX=<parameter1>,<parameter2>,…$ Command
+ACK:GTXXX,<parameter1>,<parameter2>,…$ Acknowledgement
i n
+RESP:GTXXX,<parameter1>,<parameter2>,…$ Report
cl a l
The entire message string ends with character ‘$’.
i
The characters ‘XXX’ identify the deferent message.
e t
The “<parameter1>,<parameter2>,…” carry the message’s parameters. The number of parameters
n
is different in different messages. The ASCII character ‘,’ is used to separate the neighbouring
u
parameter characters. The parameter string may contain the ASCII characters:
Q fide
‘0’–‘9’, ’a’–‘z’, ’A’–‘Z’.
Detailed descriptions of each message format are located in the specific message sections.
By sending Commands to the terminal, the backend server can either configure and query the
parameters of the terminal or control the terminal to perform specific actions. When the terminal
n
receives Commands over the air, it will reply with a corresponding Acknowledgement message.
o
According to the configuration of the parameters, the terminal can send Report messages to the
backend server. Please see the following figure:
C
Command
Acknowledgement
Terminal Backend
Server
Report
Report
k
Report
cl i n a l
i
Figure 1: @Tracker Protocol messages flow
ue n t
Q fide
o n
C
3.2. Command And Acknowledgement
3.2.1. Server Connection
3.2.1.1. Bearer Setting Information

The command AT+GTBSI is used to configure the GPRS parameters.
 AT+GTBSI=
Example:
k
AT+GTBSI=gmt200,cmnet,,,,,,,0000$
i n
SN Parameter Length(byte) Range/Format Default
l l
1 Password 4–6 '0' – '9' 'a' – 'z' 'A' – 'Z' gmt200
c ia
2 APN <=40
e t
3 APN User Name <=30
u n
4 APN Password <=30
Q fide
5 Reserved 0
6 Reserved 0
7 Reserved 0
8 Reserved 0
n
Serial Number 4 0000 – FFFF
o
Tail Character 1 $ $
C
 <Password>: The valid character of password is ‘0’–9’, ‘a’ –‘z’, ‘A’ –‘Z’. The default value
is “gmt200”.
 <APN>: Access point name (APN).
 <APN User Name>: the GPRS APN user name. If the parameter field is empty, the current
value of this parameter will be cleared.
 <APN Password>: the GPRS APN password. If the parameter field is empty, the current
value of this parameter will be cleared.
 <Reserved>: Not used at present. Please keep empty.
 <Serial Number>: the serial number for the command. It will be invoked in the ACK message
of the command.
 <Tail Character>: a character to indicate the end of the command. And it must be “$”.
The acknowledgment message of AT+GTBSI command:
 +ACK:GTBSI,
Example:
+ACK:GTBSI,240100,135790246811220,,0000,20090214093254,11F0$
Parameter Length(byte) Range/Format Default
XX0000 – XXFFFF,
Protocol Version 6
X∈{'A' – 'Z', '0' – '9'}
Unique ID 15 IMEI
Device Name <=20 '0' – '9' 'a' – 'z' 'A' – 'Z' '-' '_'
k
Send Time 14 YYYYMMDDHHMMSS
n
Count Number 4 0000 – FFFF
l i l
c a
 <Protocol Version>: The protocol version that the terminal conforms to. The first two
i
characters XX point out the device type. 24 means GMT200. The middle two characters
e t
point out the main version number of protocol and the last two characters point out the sub
u n
version number of protocol. And both of the main version and the minimum version are hex
digital. For example, 020A means version 2.10.
Q fide
 <Unique ID>: The IMEI of the terminal.
 <Device Name>: The specified name of the device.
 <Serial Number>: A serial number which is equal to the <Serial Number> in the
corresponding command to distinguish which command the ACK message is for.
 <Send Time>: The local time to send the ACK message.
n
 <Count Number>: A self-increasing count number in each acknowledgment message and
o
report message. It begins from 0000 and increases by 1 for each message. And it rolls back
after “FFFF”.
 <Tail Character>: a character to indicate the end of the command. Must be “$”.
Note:
C
Only after both the command AT+GTBSI and AT+GTSRI are properly set, the ACK messages
and other report messages can be sent to the backend server.
3.2.1.2. Backend Server Register Information

The command AT+GTSRI is used to configure where and how to report all the messages,
including the server information and the communication method between the backend server and
the terminal. When the terminal is configured correctly, it should be able to report data to the
backend server.
 AT+GTSRI=
TRACGMT200AN003 – 10 –
Example:
AT+GTSRI=gmt200,3,,1,116.226.44.17,7011,116.226.45.229,7012,+8613812341234,15,1,0,,,
,0001$
AT+GTSRI=gmt200,3,,1,some.host.name,7011,116.226.45.229,7012,+8613812341234,15,1,
0,,,,0001$
2 Report Mode 1 0–6 0
3 Reserved 0
k
4 Buffer Mode 1 0–2 1
n
5 Main Server IP /
<=60
i
Domain Name
l l
6 Main Server Port <=5 0 – 65535
c ia
7 Backup Server IP <=15
e t
8 Backup Server Port <=5 0 – 65535
u n
9 SMS Gateway <=20
Q fide
10 Heartbeat Interval <=3 0|5 – 360min 0
11 SACK Enable 1 0|1 0
12 Protocol Format 1 0|1 0
n
13 Connection On
1 0|1 0
Always
o
14 Reserved 0
C
15 Reserved 0
 <Report Mode>: This defines the communication method between the backend server and
the terminal. Supported report modes as following:
 0: Stop reporting.
 1: TCP short-connection preferred mode. The connection is based on TCP protocol.
The terminal connects to the backend server every time it needs to send data and will
shut down the connection when the terminal finishes sending data. And if it fails to
establish TCP connection to the backend server (both Main Server and Backup
Server), it will try to send data via SMS to the SMS gateway.
 2: TCP short-connection forced mode. The connection is based on TCP protocol. The
terminal connects to the backend server every time it needs to send data and will shut
down the connection when the terminal finishes sending data. And if it fails to
establish TCP connection to the backend server (both Main Server and Backup
Server), it will store the data in the memory buffer if buffer report function is enabled.
Otherwise the data is dropped.
 3: TCP long-connection mode. The connection is based on TCP protocol. The
terminal connects to the backend server and maintains the connection using the heart
beat data. The backend server should respond to the heart beat data from the
terminals.
 4. UDP mode. The terminal will send data to the backend server by UDP protocol.
Receiving protocol commands via UDP is supported if the GPRS network allows it. It
is recommended to enable heartbeat sending and +RESP:GTPDP report when UDP
receiving is the case.
k
 5: Force on SMS. Only use the SMS for transmitting.
 6: UDP with fixed local port. Like the UDP mode, the terminal will send data using
i n
UDP protocol. The difference is the terminal will use fixed local port rather than
l l
random port to communicate with the server in this mode. Thus the backend server
c a
could use identical port to communicate with all terminals if the backend server and
i
the terminals are all in the same VPN network. The port number the device uses is the
e t
same as the port number of the primary server.

u n
<Connection On Always>: This defines whether make device trying to keep TCP/UDP
connection always on when <Report Mode> is in “3: TCP long-connection mode” or “6:
Q fide
UDP with fixed local port mode”.
 0: Disable this feature.
 1: Enable this feature.
 <Buffer Mode>: The working mode the buffer report function. When buffer report function is
enabled, if the device goes into areas without GSM/GPRS network covering, it will stores all
n
report locally. When the device goes back to areas with GSM/GPRS network covering, it
o
will then send all the buffered reports through GPRS.
 0: Disable the buffer report function.
 1: Low priority. Enable the buffer report function. Under this working mode, the
C
device will send the buffered messages after sending the normal messages.
 2: High priority. Enable the buffer report function. Under this working mode, the
device will send all the buffered messages before sending any normal message except
for the SOS message (+RESP:GTSOS).
 <Main Server IP / Domain Name>: The IP address or the domain name of the primary server.
 <Main Server Port>: The port of the primary server.
 <Backup Server IP>: The IP address of the backup server.
 <Backup Server Port>: The port of the backup server.
 <SMS Gateway>: Maximum 20 characters including the optional national code starting with
“+” for SMS messages sending. Short code (for example: 10086) is also supported.
 <Heartbeat Interval>: the interval of sending heartbeat package message (+ACK:GTHBD)
when report mode is TCP long-connection mode or UDP mode. If set to 0, no heartbeat
package message sending.
 <SACK Enable>: This defines whether the backend server should respond to the terminal
with SACK message when receiving messages from the terminal.
 0: the backend server does not reply SACK message after receiving message from the
terminal.
 1: the backend server replies SACK message when receiving any message from the
terminal.
 <Protocol Format>: This defines the format of the report messages send from the device to
the backend server. 0 means using the ASCII format, 1 means the HEX format.
The acknowledgment message of AT+GTSRI command:

 +ACK:GTSRI,
Example:
k
+ACK:GTSRI,240100,135790246811220,,0001,20090214093254,11F0$
i n l
XX0000 – XXFFFF,
l
Protocol Version 6
X∈{'A' – 'Z','0' – '9'}
c ia
Unique ID 15 IMEI
e t
Device Name <=20 '0' – '9' 'a' – 'z' 'A' – 'Z' '-' '_'
u n
Q fide
o n
Note:
Only after both the command AT+GTBSI and AT+GTSRI are properly set, the ACK messages
and other report messages can be sent to the backend server.
C
3.2.1.3. Quick Start Setting
The command AT+GTQSS is used to configure the GPRS parameter and backend server
information in one command if all these settings are within 160 bytes, otherwise use AT+GTBSI
and AT+GTSRI in two steps.
 AT+GTQSS=
Example:
AT+GTQSS=gmt200,cmnet,,,3,,1,116.226.44.17,7011,116.226.45.229,7012,+861381234123
4,15,1,0,0,0002$
2 APN <=40
3 APN User Name <=30
4 APN Password <=30
5 Report Mode 1 0–6 0
6 Reserved 0
7 Buffer Mode 1 0–2 1
8 Main Server IP /
<=60
k
Domain Name
9 Main Server Port <=5 0 – 65535
l i n l
10 Backup Server IP <=15
c a
11 Backup Server Port <=5 0 – 65535
i
12 SMS Gateway <=20
e t
13 Heartbeat Interval <=3 0|5 – 360min 0
u n
14 SACK Enable 1 0|1 0
Q fide
15 Protocol Format 1 0|1 0
16 Connection On
1 0|1 0
Always
n
Co
The acknowledgment message of AT+GTQSS command:
 +ACK:GTQSS,
Example:
+ACK:GTQSS,240100,135790246811220,,0002,20090214093254,11F0$
XX0000 – XXFFFF,
Protocol Version 6
X∈{'A' – 'Z', '0' – '9'}
Unique ID 15 IMEI
Device Name <=20 '0' – '9' 'a' – 'z' 'A' – 'Z' '-' '_'
3.2.2. Device Configuration
3.2.2.1. Global Configuration
The AT+GTCFG command is used to configure the global parameters.
 AT+GTCFG=
Example:
k
AT+GTCFG=gmt200,123456,gmt200,,,,,,,,,,,,,,,,,,,0003$
n
AT+GTCFG=gmt200,,,1,123.4,0,0,0,1,,2FF,,1,1,300,0,,0,1,,,0003$
l i l
c a
e t i
2 New Password 4–6 '0' – '9' 'a' – 'z' 'A' – 'Z'
3 Device Name <=20 '0' – '9' 'a' – 'z' 'A' – 'Z' '-' '_' gmt200
u n
4 ODO Enable 1 0|1 0
Q fide
5 ODO Initial Mileage <=9 0.0 – 4294967.0Km 0
6 GPS On Need 1 0|1 0
7 GSM report 1 0–3 0
n
8 Report Composition Mask <=4 0000 – FFFF 003F
o
9 Power Saving Mode 1 0 –2 1
10 Reserved 0
C
11 Event Mask <=8 00000000 – FFFFFFFF 1FFFF
12 Reserved 0
13 LED On 1 0|1 0
14 Info Report Enable 1 0|1 0
15 Info Report Interval <=5 30 – 86400sec 300
16 Location By Call 1 0–2 0
17 Reserved 0
18 Power Mode 1 0–2 0
19 Agps Mode 1 0|1 0
20 Reserved 0
21 Reserved 0
 <New Password>: Set to change the current password.

 <Device Name>: An ASCII string to represent the name of the device.
 <ODO Enable>: Enable/disable the odograph function to calculate the total mileage. The
current mileage is included in every position report message.
 <ODO Initial Mileage>: The initial value for calculating the total mileage.
k
 <GPS On Need>: Whether to close GPS chip after retrieving GPS position information.
 0: Never close GPS chip
i n
 1: Close GPS chip after retrieving GPS information every time.
l l
 <GSM report>: If GPS fixing for the report message +RESP:GTSOS, +RESP:GTRTL,
c a
+RESP:GTLBC, +RESP:GTTOW and +RESP:GTFRI were failed and the parameter
i
<GSM report> was set to 1, the terminal reports the message +RESP:GTGSM, including the
e t
information of the service cell and the neighbour cells after those messages if cell’s
information available. If it was set to 2, the terminal will report the message
u n
+RESP:GTGSM after getting GPS position successfully every time if cell’s information
Q fide
available. If it was set to 3, the terminal will report +RESP:GTGSM no matter what result of
getting GPS position every time if cell’s information available.
 0: Not allow the cells’ information report.
 1: Allow the cells’ information report after failed to get GPS position if cell’s
information available.
n
 2: Report the message +RESP: GTGSM after getting GPS position successfully
every time if cell’s information available.
o
 3: Report the message +RESP:GTGSM no matter what result of getting GPS
position every time if cell’s information available.
C
 <Report Composition Mask>: Bitwise report mask to configure the composition of report
message, especially the GPS information composition.
 Bit 0 for <Speed>
 Bit 1 for < Azimuth >
 Bit 2 for <Altitude>
 Bit 3 for GSM tower data, including <MCC>, <MNC>, <LAC>, <Cell ID> and the
<reserved> parameter “00”
 Bit 4 for <Mileage>
 Bit 5 for <Send Time>
 Bit 6 for <Device Name>
For each bit, set it to 1 to enable corresponding component in the report, 0 to disable. This
mask is effective to all report messages.
 <Power Saving Mode>: Set mode of power saving function. If mode of power saving
function is set to 0, the fixed report will follow <IGF Report Interval> when the engine is off.
If mode of power saving function is set to 1, the fixed report, geo-fence and speed alarm
report functions are suspended when the device is at a standstill or the engine is off. If mode
of power saving function is set to 2, it is mostly like mode 1 and the difference is that the
fixed report will not be suspended and the fix and send interval of it will be set to <IGF
Report Interval> in AT+GTFRI when the engine is off.
 0: Disable power saving function
 1: Mode 1 of power saving function
 2: Mode 2 of power saving function
 <Event Mask>: Bitwise mask to configure which event report should be sent to the backend
server.
 Bit 0 for +RESP:GTPNA
 Bit 1 for +RESP:GTPFA
k
 Bit 2 for +RESP:GTMPN
 Bit 3 for +RESP:GTMPF
i n
 Bit 4 is reserved
l l
 Bit 5 for +RESP:GTBPN
c a
 Bit 6 for +RESP:GTBPF
i
 Bit 7 for +RESP:GTBPL
e t
 Bit 8 for +RESP:GTBTC
 Bit 9 for +RESP:GTSTC
u n
 Bit 10 for Reserved
Q fide
 Bit 11 for +RESP:GTSTT
 Bit 12 Reserved
 Bit 13 for +RESP:GTPDP
 Bit 14 for the power on +RESP:GTRTL
 Bit 15 for the ignition report +RESP:GTIGN and +RESP:GTIGF
n
 Bit 16 for the ignition on and ignition off location report +RESP:GTIGL
o
For each bit, set it to 1 to enable corresponding event report, 0 to disable.
 <LED On>: Configure the working mode of power LED and GPS LED.
 0: Each time the device powers on, both LED’s will work for 30 minutes and then are
C
turned off deadly.
 1: turn on Power LED and GPS LED if necessary.
 <Info Report Enable>: Enable/disable the device information report function
(+RESP:GTINF). The device information include state of the device, ICCID, GSM signal
strength, adapter connection status, backup battery enable setting, battery voltage, charging
status, Power and GPS LED working mode, GPS on need setting, external GPS antenna
status, the last known time of GPS fix, analog input voltage, all digit inputs and outputs status,
time zone information and daylight saving setting..
 0: Disable the device information report function.
 1: Enable the device information report function.
 <Info Report Interval>: The interval of reporting the device information.
 <Location By Call>: Configure how to handle the incoming call.
 0: Just hang up the call.
 1: Hang up the call and report the current position (+RESP:GTLBC) to the backend
server.
 2: Hang up the call and report the current position as a google maps hyperlink to
incoming call via SMS.
 <Power Mode>: Terminal power supply mode. There are three cases list below:
 0: The external power supply will charge the internal backup battery on need and
power for unit.
 1: The external power supply will only charge the internal backup battery when
ignition on is detected. The charge process is stopped when ignition off. During
charging, the external power supply will power the unit, otherwise the internal
backup battery will supply power for unit.
 2: The external power supply will charge the internal backup battery when ignition on
is detected or when the internal backup battery capacity is less than 30 percent if
k
ignition is off. During charging, the external power supply will power the unit,
n
otherwise the internal backup battery will supply power for unit.
i
 <Agps Mode>: A numeric to indicate whether to enable AGPS. AGPS is helpful to improve
l l
the ratio to get GPS position successfully and reduce the time to get GPS position.
c a
 0: Disable the AGPS function.
i
 1: Enable the AGPS function.
ue n t
The acknowledgment message of AT+GTCFG command:
Q fide
 +ACK:GTCFG,
Example:
+ACK:GTCFG,240100,135790246811220,,0003,20090214093254,11F0$
n
XX0000 – XXFFFF,
Protocol Version 6
o
X∈{'A' – 'Z','0' – '9'}
Unique ID 15 IMEI
C
Device Name <=20 '0' – '9' 'a' – 'z' 'A' – 'Z' '-' '_'
3.2.2.2. Auto-unlock PIN

The command AT+GTPIN is used to configure the auto-unlock PIN function of the device.
Some operators offer SIM card with PIN code protection by default. To make the device work
with the PIN-protected SIM card, use this command to let the device auto-unlock the SIM PIN
with the pre-set PIN code.
 AT+GTPIN=
Example:
AT+GTPIN=gmt200,1,0000,,,,,,0013$
2 Enable Auto-unlock PIN 1 0|1 1
3 PIN 4–8 '0' – '9'
4 Reserved 0
k
5 Reserved 0
n
6 Reserved 0
l i l
7 Reserved 0
c a
8 Reserved 0
e t i
u n
Q fide
 <Enable Auto-unlock PIN>: 1 to enable the auto-unlock PIN function, 0 to disable.
 <PIN>: Code used to unlock the SIM PIN.
n
The acknowledgment message of AT+GTPIN command:
 +ACK:GTPIN,
o
Example:
+ACK:GTPIN,240100,135790246811220,,0013,20090214093254,11F0$
C
XX0000 – XXFFFF,
Protocol Version 6
X∈{‘A’ – ‘Z’,’0’ – ‘9’}
Unique ID 15 IMEI
Device Name <=20 '0' – '9' 'a' – 'z' 'A' – 'Z' '-' '_'
3.2.2.3. Time Adjustment
The command AT+GTTMA is used to adjust the local time of the device remotely. Upon this
command, the device will set the time zone and daylight saving accordingly. Then it will use the
given UTC time to adjust the local time based on the time zone and daylight saving setting.
This command will also trigger the device to start GPS. After a successful GPS fix, the device
will update the local time with the GPS UTC time again.
 AT+GTTMA=
Example:
AT+GTTMA=gmt200,-,3,30,0,20090917203500,,,,,0010$
k
n
l i l
2 Sign 1 +|– +
c a
3 Hour Offset <=2 0 – 23 0
t i
4 Minute Offset <=2 0 – 59 0
e
5 Daylight Saving 1 0|1 0
u n
6 UTC Time 14 YYYYMMDDHHMMSS
Q fide
7 Reserved 0
8 Reserved 0
9 Reserved 0
n
10 Reserved 0
o
C
 <Sign>: Indicate the positive or negative of the local time offset to UTC
 <Hour Offset>: UTC offset in hours
 <Minute Offset>: UTC offset in minutes
 <Daylight Saving>: Enable/disable daylight saving time.
 0: Disable daylight saving
 1: Enable daylight saving
 <UTC time>: UTC time to adjust the local time..
The acknowledgment message of AT+GTTMA command:

 +ACK:GTTMA,
Example:
+ACK:GTTMA,240100,135790246811220,,00010,20090214093254,11F0$
XX0000 – XXFFFF,
Protocol Version 6
X∈{‘A’ – ‘Z’,’0’ – ‘9’}
Unique ID 15 IMEI
Device Name <=20 '0' – '9' 'a' – 'z' 'A' – 'Z' '-' '_'
k
l i n l
3.2.2.4. Protocol Watchdog
c
The AT+GTDOG command is used to reboot the device in a time based manner or upon ignition.
ia
This helps the device avoid working in an exceptional status for a long time. Besides these two
e t
automatically reboot method, the device also supports to use the digital input to trigger the reboot
manually.
u
Q fide n
 AT+GTDOG=
Example:
AT+GTDOG=gmt200,1,,1,0130,,1,1,,60,60,30,0012$
AT+GTDOG=gmt200,2,30,,,,1,1,,60,60,30,0012$
n
o
2 Mode 1 0–2 0
C
3 Ignition Frequency <=3 10 – 120 min 60
4 Interval <=2 1 – 30 day 30
5 Time 4 HHMM 0200
6 Reserved 0
7 Report Before Reboot 1 0|1 1
8 Input ID 1 0|1 0
9 Reserved 0
10 GSM Interval 4 0|5-1440 min 60
11 PDP Interval 4 0|5-1440 min 60
12 PDP reset interval 4 0|5-1440 min 30
 <Mode>: Working mode.

 0: Disable this function
 1: Reboot periodically according to the <Interval> and <Time> setting.
 2: Reboot when ignition on.
 <Ignition Frequency>: When the working mode is 2, if the time interval between two
adjacent ignitions is greater than the specified value, the device will automatically reboot
upon ignition on. When the initial use of device, the device will reboot automatically at the
second ignition on, no matter whether the time interval between two adjacent ignitions is
k
greater than the specified value.

n
<Interval>: The interval to reboot the device in day.
i
 <Time>: At what time to perform the reboot operation when <Interval> is met.
l l
 <Report Before Reboot>: Whether to report the +RESP:GTDOG message before reboot. 0
c a
means no report, 1 to report. If this is enabled, the device will make a real-time location
i
before sending the message in order to send it with the current location information.
e t
 <Input ID>: ID of the digital input port which is used to trigger the manually reboot. 0 means
n
do not use manual reboot. Only port 1 is supported.
u
 <GSM Interval>: The interval to reboot the device when in no GSM signal situation.0 means
Q fide
do not reboot the device.
 <PDP Interval>: The interval to reboot the device when GPRS unable to register successfully.
0 means do not reboot the device.
 <PDP reset Interval>: The time before reactivate PDP context after activating PDP context.0
means not reactivating PDP context.
o n
The acknowledgment message of AT+GTDOG command:
 +ACK:GTDOG,
C
Example:
+ACK:GTDOG,240100,135790246811220,,0012,20090214093254,11F0$
XX0000 – XXFFFF,
Protocol Version 6
X∈{‘A’ – ‘Z’,’0’ – ‘9’}
Unique ID 15 IMEI
Device Name <=20 '0' – '9' 'a' – 'z' 'A' – 'Z' '-' '_'
3.2.2.5. Outside Working Hours

To protect the privacy of the driver when they are off duty, the device could be configured to
report empty location information during the outside working hours. The command AT+GTOWH
is used to define the working hours and the working mode to protect the privacy. When this
function is enabled, the device will report empty latitude, empty longitude, empty MCC, empty
MNC, empty LAC and empty Cell ID in all the report messages except for +RESP:GTSOS.
k
AT+GTOWH=
Example:
n
AT+GTOWH=gmt200,1,1F,0900,1200,1300,1730,,,,1,1,,,,,,,0011$
l i l
c a
e t i
2 Mode 1 0–1 0
u n
3 Day of Work <=2 0 – 7F 1F
Q fide
4 Working Hours Start1 4 HHMM 0900
5 Working Hours End1 4 HHMM 1200
6 Working Hours Start2 4 HHMM 1300
7 Working Hours End2 4 HHMM 1800
n
8 Reserved 0
o
9 Reserved 0
C
10 Reserved 0
11 Output ID 1 0-1 0
12 Output Status 1 0|1 0
13 Reserved 0
14 Reserved 0
15 Reserved 0
16 Reserved 0
17 Reserved 0
18 Reserved 0
 0: Disable this function.
 1: Automatic mode. Under this mode, the device will ignore the status of the digital
input. It will automatically check the current time against the working hours arrange.
If outside the working hours, hide the location information. Otherwise report
normally.
 <Day of Work>: Specify the working days in a week in a bitwise manner.
 Bit 0 for Monday
 Bit 1 for Tuesday
 Bit 2 for Wednesday
k
 Bit 3 for Thursday
 Bit 4 for Friday
n
 Bit 5 for Saturday
l i l
 Bit 6 for Sunday
For each bit, 0 means off day, 1 means working day.
c a

i
<Working Hours Start1>, <Working Hours End1>: The first period of the working hours in a
e t
day.
 <Working Hours Start2>, <Working Hours End2>: The second period of the working hours in
u n
a day.
Q fide
The acknowledgment message of AT+GTOWH command:
 +ACK:GTOWH,
Example:
n
+ACK:GTOWH,240100,135790246811220,,0011,20090214093254,11F0$
o
XX0000 – XXFFFF,
C
Protocol Version 6
X∈{‘A’ – ‘Z’,’0’ – ‘9’}
Unique ID 15 IMEI
Device Name <=20 '0' – '9' 'a' – 'z' 'A' – 'Z' '-' '_'
3.2.2.6. Jamming Detection
The command AT+GTJDC is used to configure the parameter for jamming detection. When the
detection condition is matched, then according to <Mode> parameter, the device will report
+RESP:GTJDR or +RESP:GTJDS event message to the backend server.
 AT+GTJDC=
Example:
AT+GTJDC=gmt200,1,25,,5,10,10,,1,1,,,,0016$
2 Mode 1 0|1|2 0
3 Signal Threshold <=3 0 – 31 25
k
4 Reserved 0
i n
5 Jamming Cell Number Threshold <=2 0-99 5
l l
6 Enter Jamming Timer Threshold <=3 0-300 sec 10
c ia
7 Quit Jamming Timer Threshold <=4 0-3600sec 10
e t
8 Reserved 0
u n
9 Output ID 1 0-1 0
Q fide
10 Output Status 1 0|1
11 Reserved 0
12 Reserved 0
n
13 Reserved 0
o
C
 0: Disable Jamming detection function.
 1: Enable Jamming detection function, if the jamming is detected, the device will
report +RESP:GTJDR message. This message only is reported with entering into
“Jamming”.
 2: Enable Jamming detection function, if the jamming is detected, the device will
report +RESP:GTJDS message. This message is reported with entering into
“Jamming” or quiting the “Jamming”.
 <Signal Threshold>, < Jamming Cell Number Threshold >: The built-in jamming detection
algorithm uses these two parameters to judge whether the device is currently being jammed.
The smaller the parameter, the more sensitive.
 <Enter Jamming Timer Threshold>: when the device detects the jamming, the device based
on <Enter Jamming Timer Threshold> parameter to trigger the enter Jamming event.
 <Quit Jamming Timer Threshold>: when the device quits the jamming, the device based on
<Quit Jamming Timer Threshold> parameter to trigger the quit Jamming event.
The acknowledgment message of AT+GTJDC command:
 +ACK:GTJDC,
Example:
+ACK:GTJDC,240100,135790246811220,,0016,20090214093254,11F0$
XX0000 – XXFFFF,
Protocol Version 6
X∈{'A' – 'Z', '0' – '9'}
Unique ID 15 IMEI
Device Name <=20 '0' – '9' 'a' – 'z' 'A' – 'Z' '-' '_'
k
i n
l l
c ia
ue n t
3.2.2.7. Non Movement Detection
Q fide
The AT+GTNMD command is used to configure the motion sensor to detect the motion state of
the device. If the device is detected to be at non-movement status, the device could change the
send interval of FRI(including +RESP:GTGSM for FRI). If the device is detected to be at
movement status again, the device will resume send interval of FRI.
n
 AT+GTNMD=
o
Example:
AT+GTNMD=gmt200,1,4,1,300,,,,,000B$
C
SN Parameter Length(byte) Range/Format Default value
1 Password 4~8 ‘0’-‘9’,’a’-‘z’,’A’-‘Z’ gmt200
2 Mode 1 0|1 0
3 Non-movement Duration <=3 0 – 255 0
4 Movement Duration <=3 0 – 255 0
5 NMD Report Interval 5 0|5 – 86400sec 300
6 Reserved 0
7 Reserved 0
8 Reserved 0
9 Reserved 0
Serial Number 4 0000-FFFF
 <mode>: The working mode of this command.
0: Disable this function.
1: If the device is at rest, change the fixed timing report and send the +RESP:GTNMD
message to the backend server. If the device is at motion status again, resume the
fixed timing report and send the +RESP:GTNMD message to the backend server.
 <Non-movement duration>: If the device keeps still this time long, the device is then
considered to be at non-movement status. The default value is 0 i.e. 60 and the unit is second.
 Movement duration>: If the device keeps moving this time long, the device is then considered
to be at movement status The default value is 0 and the unit is second..
 <NMD report interval>: Period to fix and send the position information when <Power Saving
Mode> in AT+GTCFG is set to 0 or 2 and if <Mode> in AT+GTFRI is set to non zero value.
Its value range is 0|5 – 86400 and the unit is second.
k
The acknowledgment message of AT+GTNMD command:
 +ACK:GTNMD,
l i n l
Example:
+ACK:GTNMD, 240100,135790246811220,,0009,20090214093254,11F0$
c ia
e t
XX0000 – XXFFFF,
Protocol Version 6
u n
X∈{‘A’ – ‘Z’,’0’ – ‘9’}
Q fide
Unique ID 15 IMEI
Device Name <=20 '0' – '9' 'a' – 'z' 'A' – 'Z' '-' '_'
n
o
C
3.2.2.8. Jamming Behavior Setting
The command AT+GTJBS is used for the Jamming Behavior Setting function and The “Jamming
Behavior Setting” function is based on the “Jamming Detection” function. The output1 is used in
“cut fuel”.
NO
Jamming
Detected?
Configurable
Delay Duration(T1)
Jamming
k
NO
Still present?
i n
YES
cl l
Is ignition on?
e t ia
YES
u n
Sensor NO
Motion?
NO
Q fide
YES
GPS fix fail

YES
TimeOut(T3)
n
NO NO NO
o
GPS Fixed
C
YES
Current Speed <= Speed Limit
YES
Reset
Command
Trigger Output 1
(cut fuel)
Configurable
Timeout(T2)
YES
Jamming Reset output 1

NO
Still Present? (enable fuel)
 AT+GTJBS=
Example:
AT+GTJBS=gmt200,1,, 60,3600,1,30,,,,,001A$
Length
Parameter Range/Format Default
(byte)
Password 4–6 '0' – '9' 'a' – 'z' 'A' – 'Z' gmt200
Mode 1 0|1 0
Reserved 0
k
Delay duration(T1) 5 1 – 65535(sec) 60
n
Cut fuel Timer(T2) 5 1 – 65535(sec) 3600
l i l
Need Judge Motion Sensor 1 0|1 1
c a
Speed Limit 3 0 – 999km/h 30
t i
GPS Fix Fail Timer(T3) 5 30-65535(sec) 120
e
Reserved 0
u n
Reserved 0
Q fide
Reserved 0
n
o
 0: Disable JBS function.
 1: Enable JBS function.
C
 < Delay Duration (T1)>: it pointed to the Delay length of time.
 <Cut fuel Timer (T2)>: it pointed to cut fuel length of time.
 <Speed Limit>: the speed limit of cutting fuel.
 <Need Judge Motion Sensor>: The GPS fixed fail is timeout, whether need judge motion
sensor state to cut fuel. If the <Need Judge Motion Sensor> set as 0, the machine state will
always judge the GPS fixed state.
 0: Disable to need judge motion sensor.
 1: Enable to need judge motion sensor.
 <GPS Fix Fail Timer (T3)>: The valid time of GPS fix, if more than this time, we will be
consider it as fix fail.
The acknowledgment message of AT+GTJBS command:

 +ACK:GTJBS,
Example:
+ACK:GTJBS, 060100,135790246811220,,001A,20090214093254,11F0$
XX8000 – XX80FF, X∈{'A'

Protocol Version 6
– 'Z','0' – '9'}
Unique ID 15 IMEI
Device Name <=20 '0' – '9' 'a' – 'z' 'A' – 'Z' '-' '_' '?'
k
n
cl i
3.2.2.9. White List
ia l
e t
The command AT+GTWLT is used to configure a list of authorized phone numbers which are
u n
allowed to perform the location by call, voice monitoring and SMS functions
 AT+GTWLT=
Q fide
Example:
AT+GTWLT=gmt200,7,1,2,13813888888,13913999999,,,,,0018$
n
Call Filter 1 0–7 0
o
Start Index <=2 1 – 10
C
End Index <=2 1 – 10
Phone Number List <=20×10
Reserved 0
Reserved 0
Reserved 0
Reserved 0
 <Call Filter>: The working mode of this function.

 Bit 0: White list for location by call.
 Bit 1: Reserved.
 Bit 2: White list for SMS.
For each bit, set it to 1 to enable, 0 to disable. If the value of Bit0, Bit1 and Bit2 are all 0,
disable this function and allow any phone number to use the location by call and voice monitoring
functions.
 <Start Index>, <End Index>: The index range of the white list to which the phone numbers
are to be updated. For example, the <Start Index> is set to 1 and the the <End Index> is set to
2. Then the first two phone numbers in the white list will be updated by the numbers
provided in the parameter <Phone Number List>. The <Start Index> and <End Index> defines
the total amount of phone numbers that will be updated. If either one is empty, there should
be no <Phone Number List> parameter followed.
 <Phone Number List>: A list of phone numbers, which are separated by comma, to be
k
updated to the white list. The amount of the phone numbers are defined by <Start Index> and
n
<End Index>.
cl i a l
The acknowledgment message of AT+GTWLT command:
i
 +ACK:GTWLT,
e t
Example:
u n
+ACK:GTWLT,040100,135790246811220,,0018,20090214093254,11F0$
Q fide
XX0000 – XXFFFF, X∈{'A'

Protocol Version 6
– 'Z','0' – '9'}
Unique ID 15 IMEI
n
Device Name <=20 '0' – '9' 'a' – 'z' 'A' – 'Z' '-' '_' '?'
o
C
3.2.3. Position Related Report
3.2.3.1. Fixed Report Information
The command AT+GTFRI is used to configure the parameters of scheduled report

(+RESP:GTFRI).
 AT+GTFRI=
Example:
AT+GTFRI=gmt200,0,,,,,,,,,,,,,,,,,0009$
AT+GTFRI=gmt200,1,1,,1,1000,2300,180,30,,,,,600,,,,,0009$
AT+GTFRI=gmt200,2,1,,1,1000,2300,,,500,,,,,,,,,0009$
AT+GTFRI=gmt200,3,1,,1,1000,2300,,,,1000,,,,,,,,0009$
AT+GTFRI=gmt200,4,1,,1,1000,2300,,60,,300,,,,,,,,0009$
2 Mode 1 0–4 0
3 Discard No Fix 2 0|1 1
k
4 Reserved 0
n
5 Period Enable 1 0|1 1
l i l
6 Start Time 4 HHMM 0000
c a
7 End Time 4 HHMM 0000
t i
8 Check Interval <=5 30 – 86400sec 180
e
9 Send Interval <=5 5 – 86400sec 30
u n
10 Distance <=5 50 – 65535m 1000
Q fide
11 Mileage <=5 50 – 65535m 1000
12 Reserved 0
13 Corner Report <=3 0 – 180 0
n
14 IGF Report Interval <=5 0 | 5-86400sec 600
o
15 Reserved 0
16 Reserved 0
C
17 Reserved 0
18 Reserved 0
 <Mode>: The working mode of the fixed report.

 0: Disable this function.
 1: Fixed Timing Report. The positional report message is sent to the backend server
periodically according to the parameter <Send Interval>.
 2: Fixed Distance Report. The positional report message is sent to the backend server
when the straight-line distance between the current GPS position and the last sent
GPS position is greater than or equal to the distance specified by parameter
<Distance>.
 3: Fixed Mileage Report. The positional report message is sent to the backend server
when the path length between the current GPS position and the last sent GPS position
is greater than or equal to the mileage specified by parameter <Mileage>. This
function need connect the vehicle ignition signal to the specified digital input port of
the device.
 4: Optimum Report. Simultaneously observe both time interval and path length
between two adjacent reports. Report device position if the calculated time interval
per current time against the last report time is greater than the <Send Interval>, and
the length of path between the current position and the last position is greater than the
<Mileage> setting. This function need connect the vehicle ignition signal to the
specified digital input port of the device.
k
 <Discard No Fix>: Disable/enable reporting when there is no GPS fixing
 0: Enable reporting
i n
 1: Disable reporting
l l
 <Period Enable>: Disable/enable the time range specified by <Start time> and <End time>. If
c a
the time range is enabled, the position reporting is limited within the time range.
i
 <Start Time>: The start time of the scheduled fixed report. The valid format is “HHMM”. The
e t
value range of “HH” is “00”–“23”. The value range of “MM” is “00”–“59”.

u n
<End Time>: The end time of the scheduled fixed report. The valid format and range are
same as <Start Time>.
Q fide
 <Check Interval>: The interval time to fix GPS, its value range is 30 – 86400 and the unit is
second. The parameter is used only when the parameter <GPS On Need> in AT+GTCFG is
set to 1.
If <GPS On Need> was set as 1, the device has two modes to operate the GPS module
according to the value of <Check Interval>:
n
 “Normal mode”: If the <Check Interval> is no less than 60 seconds, the terminal will
o
close the GPS chip every time after GPS fixing finishes in order to save power.
 “Emergency mode”: If the <Check Interval> is less than 60 seconds, the terminal
will never close the GPS chip unless <Power Saving Enable> is 1 and the state in
C
+RESP:GTINF is 0x16(Tow) or 0x1A(Fake Tow) or 0x11(Ignition Off Rest) or
0x12(Ignition Off Motion) or 0x41(Sensor Rest). In this mode, the <Send Interval>
will be ignored, the terminal reports every <Check Interval> time, and the <Check
Interval> will be forced to 30 seconds if it is less than 30 seconds.
Due to the limitation of the maximum report message length, it must be assured that: <Send
Interval> / <Check Interval> <= 15.
 <Send Interval>: Period to send the position information. The value range is 5 – 86400 and
the unit is second. If <report mode> in AT+GTSRI is set to force on SMS, this should be
greater than 15 seconds.
 <Distance>: the specified distance to send the position information when <Mode> is 2. Unit:
meter.
 <Mileage>: the specified length to send the position information when <Mode> is 3 and 4.
Unit: meter.
 <Corner Report>: The threshold to determine whether the device is turning around a corner.
0 to disable the corner report. For other values, the device will compare the current heading
with the last known corner, if the difference is greater than or equal to this value, send the
corner report with +RESP:GTFRI.
 <IGF Report Interval>: Period to fix and send the position information when <Power
Saving Mode> in AT+GTCFG is set to 2 and the engine is off and if <Mode> is set to non
zero value. 0 means disable this report.
The acknowledgment message of AT+GTFRI command:

 +ACK:GTFRI,
Example:
k
+ACK:GTFRI,240100,135790246811220,,0009,20090214093254,11F0$
i n l
XX0000 – XXFFFF,
l
Protocol Version 6
X∈{‘A’ – ‘Z’,’0’ – ‘9’}
c ia
Unique ID 15 IMEI
e t
Device Name <=20 '0' – '9' 'a' – 'z' 'A' – 'Z' '-' '_'
u n
Q fide
o n
3.2.3.2. Frequency Change of Fixed Report Information
The command AT+GTFFC is used to change the parameters of fixed report when certain event
C
occurs to match the request of different report interval according to the need. When the event
disappears, the device will resume its previous settings.
The device supports up to 5 sets of parameter for different events. Priority is assigned among these
events. Only the parameters for the highest priority event are applied if more than one event
occurs at the same time.
 AT+GTFFC=
Example:
AT+GTFFC=gmt200,0,1,,,,,0000$
2 Priority 1 0-4 0
3 Mode 1 0|1|2 0
4 Reserved
5 Reserved
6 Reserved
7 Reserved
 <Priority>: Priority to the event which triggers the parameter change for fixed report. 0 is the
k
highest priority.
n
 <Mode>: Specify the trigger event to change the fixed report parameters.
i

l l
0: Disable the parameters in the specified priority.
 1: Change the send interval for the report of FRI according to the value of <IGF
c a
report interval> in AT+GTFRI when ignition is off.
i
 2: Change the send interval for the report of FRI according to the value of <NMD
e t
report interval> in AT+GTNMD when the device is in non-movement status.
u n
The acknowledgment message of AT+GTFFC command:
Q fide
 +ACK:GTFFC,
Example:
+ACK:GTFFC, 240100,135790246811220,,0009,20090214093254,11F0$
n
XX0000 – XXFFFF,
Protocol Version 6
o
X∈{‘A’ – ‘Z’,’0’ – ‘9’}
Unique ID 15 IMEI
C
Device Name <=20 '0' – '9' 'a' – 'z' 'A' – 'Z' '-' '_'
3.2.3.3. Preserve Special Device Logical State Setting
The command AT+GTPDS is used to preserve special device logical state for the terminal.
According to the working mode, the function is enabled or disabled. According to the value of the
MASK, specified logical state(s) will be saved.
 AT+GTPDS=
Example:
AT+GTPDS=gmt200,1,1F,,,,,,,001A$
2 Mode 1 0|1|2 0
3 Mask 4 0000-FFFF 0
4 Reserved
k
5 Reserved
n
6 Reserved
l i l
7 Reserved
c a
8 Reserved
e t i
9 Reserved
u n
Q fide
 < Mode >:

 1: Preserve special device logical state according to the value of the MASK
n
 2: Reset all the special device logical states listed in the <Mask> after receiving the
command, and then preserve special device logical state according to the value of
o
the <Mask>
 < Mask >: Bitwise mask to configure which device states will be preserved. Each bit
C
represents a state.
 Bit 0: States of GEO
 Bit 1: Reserved bit
 Bit 2: Reserved bit
 Bit 3: Information of last known position
 Bit 4: State of ignition
 Bit 5: State of cut relay output
The acknowledgment message of AT+GTPDS command:

 +ACK:GTPDS,
Example:
+ACK:GTPDS, 240100, 135790246811220,, 0011, 20090214093254,FFFF$
XX0000 – XXFFFF,
Protocol Version 6
X∈{‘A ’– ‘Z’,’0’ – ‘9’}
Unique ID 14 IMEI
Device Name <=20 '0' – '9' 'a' – 'z' 'A' – 'Z' '-' '_'
i n k
3.2.4. Alarm Settings
cl l
3.2.4.1. Geo-Fence Information
ia
The command AT+GTGEO is used to configure the parameters of Geo-Fence. (Geo-Fence is a
e t
virtual perimeter on a geographic area using a location-based service, so that when the geofencing
u n
terminal enters or exits the area a notification is generated. The notification can contain
information about the location of the terminal and may be sent to the backend server.)
Q fide
 AT+GTGEO=
Example:
AT+GTGEO=gmt200,0,3,121.412248,31.187891,1000,600,1,1,,,,,,,000A$
n
o
2 GEO ID 1 0–4
C
3 Mode 1 0–3 0
4 Longitude <=11 (–)xxx.xxxxxx
5 Latitude <=10 (–)xx.xxxxxx
6 Radius <=7 50 – 6000000m 50
7 Check Interval <=5 0|5 – 86400sec 0
8 Output ID 1 0-1 0
10 Reserved 0
11 Reserved 0
12 Reserved 0
13 Reserved 0
14 Reserved 0
15 Reserved 0
 <GEO ID>: ID of the Geo-Fence. Total five zones, 0 to 4, are supported.

 <Mode>: The working mode of the Geo-Fence to report the message +RESP:GTGEO to the
backend server.
 0: disable the zone’s Geo-Fence function.
k
 1: Entering the zone. The report will be generated only when the terminal enters the
n
Geo-Fence.
i l
 2: Exiting the zone. The report will be generated only when the terminal exits from
l
the Geo-Fence.
c a
 3: Both entering and exiting.
i

t
<Longitude>: The longitude of a point which is defined as the center of the Geo-Fence
e
circular region. The format is “(–)xxx.xxxxxx” and the value range is from “–180.000000” to
u n
“180.000000”. The unit is degree. West longitude is defined as negative starting with minus
“–” and east longitude is defined as positive without “+”.
Q fide
 <Latitude>: The latitude of a point which is defined as the centre of the Geo-Fence circular
region. The format is “(–)xx.xxxxxx” and the value range is from “–90.000000” to
“90.000000”. The unit is degree. South Latitude is defined as negative starting with minus
“–” and north Latitude is defined as positive without “+”.

n
<Radius>: The radius of the Geo-Fence circular region. The value range is (50 – 6000000)
and the unit is meter.
o
 <Check Interval>: The interval of GPS checking for the Geo-Fence alarm.
C
The acknowledgment message of AT+GTGEO command:
 +ACK:GTGEO,
Example:
+ACK:GTGEO,240100,135790246811220,,0,000A,20090214093254,11F0$
XX0000 – XXFFFF,
Protocol Version 6
X∈{‘A’ – ‘Z’,’0’ – ‘9’}
Unique ID 15 IMEI
Device Name <=20 '0' – '9' 'a' – 'z' 'A' – 'Z' '-' '_'
GEO ID 1 0–4
3.2.4.2. Tow Alarm Configuration
The AT+GTTOW command is used to configure the motion sensor and the parameters for tow
alarm.
 AT+GTTOW=
k
Example:
n
AT+GTTOW=gmt200,1,5,0,120,1,0, , ,4,10,4,,,,,,,,,000B$
l i l
c a
e t i
2 Tow Enable 1 0|1 0
u n
3 Engine Off to Tow <=3 0 – 900 sec 60
Q fide
4 Fake Tow Delay <=3 0 – 600 sec 60
5 Tow Interval <=5 0|5 – 86400 sec 300
6 Tow Output ID 1 0-1 0
7 Tow Output Status 1 0|1 0
n
8
0
o
Reserved
C
0
Reserved
10 Rest Duration <=3 1 – 255 (×15sec) 2
11 Motion Duration <=2 1 – 99 (×100ms) 3
12 Motion Threshold 1 2–9 2
13 Reserved 0
14 Reserved 0
15 Reserved 0
16 Reserved 0
17 Reserved 0
18 Reserved 0
19 Reserved 0
20 Reserved 0
 <Tow Enable>: Enable or disable tow alarm (+RESP:GTTOW).

 0: Disable the tow alarm
 1: Enable the tow alarm
 <Engine Off to Tow>: A time parameter to judge whether the device is considered being
towed after the engine off. If the motion sensor doesn’t detect stillness within the specified
k
time after engine off, the device is being towed.
 <Fake Tow Delay>: After engine off and stillness detected, if the motion sensor detects
i n
moving again, the device turns into a state called fake tow. If the device keeps in fake tow
l l
after a period of time defined by the parameter <Fake Tow Delay>, it is considered being
c a
towed.
i
 <Tow Interval>: The period to send tow alarm message.
e t
 <Tow Output ID>: The ID of the output port to output the specified wave shape when tow
event is detected.
u n
 <Tow Output Status>: Please refer to the parameter <Output1 Status> in the chapter 3.2.5
Q fide
when <Tow Output ID> is set to 1 and refer to the parameter <CUT Relay Status> in the
chapter 3.2.5 when <Tow Output ID> is set to 2.
 <Rest Duration>: A time parameter to make sure that the device enters stillness status, i.e. the
status of the device will be changed to stillness if the motion sensor detects stillness and
maintains for a period of time defined by the parameter <Rest Duration>.
n
 <Motion Duration>: A time parameter to make sure that the device enters motion status, i.e.
the status of the device will be changed to motion if the motion sensor detects motion and
o
maintains for a period of time defined by the parameter <Motion Duration>.
 <Motion Threshold>: The threshold for the motion sensor to measure whether the device is
C
moving.
The acknowledgment message of AT+GTTOW command:

 +ACK:GTTOW,
Example:
+ACK:GTTOW,240100,135790246811220,,000B,20090214093254,11F0$
XX0000 – XXFFFF,
Protocol Version 6
X∈{'A' – 'Z','0' – '9'}
Unique ID 15 IMEI
Device Name <=20 '0' – '9' 'a' – 'z' 'A' – 'Z' '-' '_'
3.2.4.3. Speed Alarm

This command is used to set a speed-alarm range for the terminal. According to the working mode,
the terminal will report message +RESP:GTSPD to the backend server when its moving speed is
k
outside or inside of the range.
n

i
AT+GTSPD=
l l
Example:
c a
AT+GTSPD=gmt200,1,80,120,60,300,0,0,,,,,,,,,,,,,,000C$
i
AT+GTSPD=gmt200,2,80,120,60,300,1,1,,,,,,,,,,,,,,000C$
e t
u n
Q fide
2 Mode 1 0–3 0
3 Min Speed <=3 0 – 400km/h 0
4 Max Speed <=3 0 – 400km/h 0
n
5 Duration <=4 0 – 3600sec 60
o
6 Send Interval <=4 30 – 3600sec 300
7 Output ID 1 0-1 0
C
9 Reserved 0
10 Reserved 0
11 Reserved 0
12 Reserved 0
13 Reserved 0
14 Reserved 0
15 Reserved 0
16 Reserved 0
17 Reserved 0
18 Reserved 0
19 Reserved 0
20 Reserved 0
21 Reserved 0
 <Mode>: The working mode of the speed alarm.

 0: Disable speed alarm.
k
 1: Report speed alarm if the current speed is within the speed range defined by <Min
Speed> and <Max Speed>.
i n
 2: Report speed alarm if the current speed is outside the speed range defined by <Min
l l
Speed> and <Max Speed>.
 3: Report speed alarm only one time if the current speed is within or outside the speed
c ia
range defined by <Min Speed> and <Max Speed>. In this mode, <Send Interval>
e t
will be ignored.
 <Min Speed>: The lower limit speed.
u n
 <Max Speed>: The upper limit speed.
Q fide
 <Duration>: If the speed meets the alarm condition and maintains a period of time defined by
<Duration>, the speed alarm will be triggered.
 <Send Interval>: The interval time of sending speed alarm message.
n
The acknowledgment message of AT+GTSPD command:
 +ACK:GTSPD,
o
Example:
+ACK:GTSPD,240100,135790246811220,,000C,20090214093254,11F0$
C
XX0000 – XXFFFF,
Protocol Version 6
X∈{‘A’ – ‘Z’,’0’ – ‘9’}
Unique ID 15 IMEI
Device Name <=20 '0' – '9' 'a' – 'z' 'A' – 'Z' '-' '_'
3.2.4.4. SOS Function

This command is used to configure the specified input port for emergency. When an emergency
occurs, the end user can use this input port to trigger reporting current position as a google maps
hyperlink to <SOS Number> via SMS and report position message +RESP:GTSOS to the
backend server. A specified wave shape can be configured to output on specified output port.
 AT+GTSOS=
Example:
AT+GTSOS=gmt200,1,1,+8613812341234,1,1,,,,,,,000D$
k
n
l i l
2 Mode 1 0–2 0
c a
3 Digital Input ID 1 0|1 0
t i
4 SOS Number <=20
e
5 Output ID 1 0-1 0
u n
Q fide
7 Reserved 0
8 Reserved 0
9 Reserved 0
n
10 Reserved 0
o
11 Reserved 0
12 Reserved 0
C
 <Mode>: The working mode of SOS function.

 0: Disable SOS function.
 1: Send the current position to the backend server only.
 2: Send the current position as a google maps hyperlink to the <SOS Number> via
SMS.
 <Digital Input ID>: ID of the digital input port which triggers the SOS function. 0 means the
SOS function is disabled. The corresponding digital input port should be configured by the
command AT+GTDIS first. If configured to trigger the SOS function, there is no
+RESP:GTDIS report message for the specified digital input port.
 <SOS number>: the emergency phone number.
The acknowledgment message of AT+GTSOS command:

 +ACK:GTSOS,
Example:
+ACK:GTSOS,240100,135790246811220,,000D,20090214093254,11F0$
XX0000 – XXFFFF,
Protocol Version 6
X∈{‘A’ – ‘Z’,’0’ – ‘9’}
Unique ID 15 IMEI
k
Device Name <=20 '0' – '9' 'a' – 'z' 'A' – 'Z' '-' '_'
n
l i l
c ia
e t
u
Q fide n
3.2.4.5. Excessive Idling Detection
The command AT+GTIDL is used to detect the engine excessive idling (stationary while ignition
on). To use this command, the ignition signal must be connected to the device. When the device
detects that the vehicle is entering into the idle status, it will report event message
n
+RESP:GTIDN to the backend server. When the vehicle leaves the idle status, the device will
report event message +RESP:GTIDF to the backend server.
o
 AT+GTIDL=
C
Example:
AT+GTIDL=gmt200,1,2,1,,,,,0,0,,,,,,,000E$
2 Mode 1 0|1 0
3 Time to Stationary 2 1 – 30 min 2
4 Time to Movement 1 1 – 5 min 1
5 Reserved 0
6 Reserved 0
7 Reserved 0
8 Reserved 0
9 Output ID 1 0-1 0
11 Reserved 0
12 Reserved 0
13 Reserved 0
14 Reserved 0
15 Reserved 0
k
16 Reserved 0
n
l i l
c ia
e t
 1: Enable this function.
u n
 <Time to Stationary>: If the vehicle is detected to be stationary with ignition on for this time
Q fide
long, it is considered to be in idling status.
 <Time to Movement>: After the vehicle enters into idling status, if it moves again or turns
ignition off and keeps in that status for this time long, the vehicle is considered to leave idling
status.
o n
The acknowledgment message of AT+GTIDL command:
 +ACK:GTIDL,
C
Example:
+ACK:GTIDL,240100,135790246811220,,000E,20090214093254,11F0$
XX0000 – XXFFFF,
Protocol Version 6
X∈{'A' – 'Z','0' – '9'}
Unique ID 15 IMEI
Device Name <=20 '0' – '9' 'a' – 'z' 'A' – 'Z' '-' '_'
3.2.4.6. Harsh Behavior Monitoring
The command AT+GTHBM is used to monitor the harsh behavior of drive with GPS. Two harsh
behaviors are monitored, the harsh braking and the harsh acceleration. According the speed read
from GPS, 3 levels of speed are defined including high speed, medium speed and low speed. For
each speed level, 2 thresholds of speed change are defined to determine the harsh braking and
harsh acceleration. If the change of speed within 5 seconds are greater than the corresponding
threshold, the device will report +RESP:GTHBM message to the backend server to indicate the
harsh behavior. The same harsh behavior within 30 seconds only reports once. For this function to
work, the <GPS on Need> in AT+GTCFG must set to 0.
k
 AT+GTHBM=
i n
Example:
l l
AT+GTHBM=gmt200,1,,,100,21,6,,60,21,6,,,21,15,,1,1,,,,,,,000F$
c ia
e t
u n
2 Enable 1 0|1 0
Q fide
3 Reserved 0
4 Reserved 0
5 High Speed <=3 100 – 400km/h 100
6 ∆Vhb <=3 0 – 100km/h 0
n
7 ∆Vha <=3 0 – 100km/h 0
o
8 Reserved 0
C
9 Medium Speed <=3 60 – 100km/h 60
10 ∆Vmb <=3 0 – 100km/h 0
11 ∆Vma <=3 0 – 100/km/h 0
12 Reserved 0
13 Reserved 0
14 ∆Vlb <=3 0 – 100/km/h 0
15 ∆Vla <=3 0 – 100/km/h 0
16 Reserved 0
17 Output ID 1 0-1 0
19 Reserved 0
20 Reserved 0
21 Reserved 0
22 Reserved 0
23 Reserved 0
24 Reserved 0
k
 <Enable>: Enable or disable this function.
n
l i l
 1: Enable this function
 <High Speed>, <Medium Speed>: If the last known speed of the device read from GPS is
c ia
greater or equal to <High Speed>, the vehicle that the device is attached to is considered to be
e t
high speed. If the last known speed is less than <High Speed> while greater or equal to
<Medium Speed>, the vehicle is considered to be medium speed. If the last known speed is
u n
less than <Medium Speed>, the vehicle is considered to be low speed.

Q fide
<∆Vhb>: The threshold for harsh braking in high speed level. If within 5 seconds, the current
speed is less than the last known speed and the change of the speed is greater than or equal to
this value, a harsh braking is detected in high speed level. If set to 0, do not monitor harsh
braking behavior in high speed level.
 <∆Vha>: The threshold for harsh acceleration in high speed level. If within 5 seconds, the
n
current speed is greater than the last known speed and the change of the speed is greater than
or equal to this value, a harsh acceleration is detected in high speed level. If set to 0, do not
o
monitor harsh acceleration behavior in high speed level.
 <∆Vmb>: The threshold for harsh braking in medium speed level. If within 5 seconds, the
C
current speed is less than the last known speed and the change of the speed is greater than or
equal to this value, a harsh braking is detected in medium speed level. If set to 0, do not
monitor harsh braking behavior in medium speed level.
 <∆Vma>: The threshold for harsh acceleration in medium speed level. If within 5 seconds,
the current speed is greater than the last known speed and the change of the speed is greater
than or equal to this value, a harsh acceleration is detected in medium speed level. If set to 0,
do not monitor harsh acceleration behavior in medium speed level.
 <∆Vlb>: The threshold for harsh braking in low speed level. If within 5 seconds, the current
speed is less than the last known speed and the change of the speed is greater than or equal to
this value, a harsh braking is detected in low speed level. If set to 0, do not monitor harsh
braking behavior in low speed level.
 <∆Vla>: The threshold for harsh acceleration in low speed level. If within 5 seconds, the
current speed is greater than the last known speed and the change of the speed is greater than
or equal to this value, a harsh acceleration is detected in low speed level. If set to 0, do not
monitor harsh acceleration behavior in low speed level.
The acknowledgment message of AT+GTHBM command:

 +ACK:GTHBM,
Example:
+ACK:GTHBM,240100,135790246811220,,000F,20090214093254,11F0$
XX0000 – XXFFFF,
Protocol Version 6
X∈{'A' – 'Z','0' – '9'}
Unique ID 15 IMEI
k
Device Name <=20 '0' – '9' 'a' – 'z' 'A' – 'Z' '-' '_'
n
l i l
c ia
e t
u
Q fide n
3.2.4.7. Start Stop Report
The command AT+GTSSR is used to detect the status of vehicle (Start or Stop status). When the
device detects that the vehicle is entering into start status, it will report event message
+RESP:GTSTR to the backend server. When the vehicle leaves the start status, and then enters
n
into stop status, it will report event message +RESP:GTSTP to the backend server.
 AT+GTSSR=
o
Example:
AT+GTSSR=gmt200,1,2,1,5,,,,,000F$
C
2 Mode 1 0|1 0
3 Time to Stop 2 1 – 30 min 2
4 Time to Start 1 1 – 5 min 1
5 Start Speed 2 1 – 10 Km/h 5
6 Reserved 0
7 Reserved 0
8 Reserved 0
9 Reserved 0

 1: Enable this function
 <Time to Stop>: After the vehicle enters into start status, if it rest again and keeps in that
status for this time long, the vehicle is considered to leave start status.
 <Time to Start>: If the vehicle is detected to be moving with ignition on for this time long, it
k
is considered to be in start status.
 <Start Speed>: The start speed threshold to determine whether the vehicle is start or not.
n
When the device is detected to be moving with ignition on by the built-in motion sensor, it
l i l
will start to check the speed from GPS. If the device speed stays greater than this <Start
Speed> longer than <Time to Start>, the vehicle is regarded to be start status. The event report
c ia
+RESP:GTSTR will be reported. Otherwise, if the device speed stays less than or equal with
e t
this <Start Speed> longer than <Time to Stop>, the vehicle is regarded to quit start status. The
event report +RESP:GTSTP will be reported. If GPS fix abnormal more than 1 minutes,
u n
only use the built-in motion sensor to detect the start / stop status and do not check the speed.
Q fide
The acknowledgment message of AT+GTSSR command:
 +ACK:GTSSR,
Example:
+ACK:GTSSR, 240100,135790246811220,,000F,20090214093254,11F0$
n
o
XX0000 – XXFFFF,
Protocol Version 6
X∈{'A' – 'Z','0' – '9'}
C
Unique ID 15 IMEI
Device Name <=20 '0' – '9' 'a' – 'z' 'A' – 'Z' '-' '_'
3.2.5. IO Application
3.2.5.1. Digital Output
The AT+GTOUT command is used to set cut relay status as following figure.
Figure 2: Wave Shape
n k
 AT+GTOUT=
l i l
Example:
AT+GTOUT=gmt200,1,,,,,,,,,,,,,0004$
c ia
e t
u n
2 Output1 Status 1 0|1 0
Q fide
3 Reserved 0
4 Reserved 0
5 Reserved 0
n
6 Reserved 0
o
7 Reserved 0
8 Reserved 0
C
9 Reserved 0
10 Reserved 0
11 Reserved 0
12 Reserved 0
13 Reserved 0
14 Reserved 0
 <Output1 Status>: Used only for the wave shape as shown in Figure 2 to set the final status
of the output port.
 0: Disable status.
 1: Enable status.
The acknowledgment message of AT+GTOUT command:

 +ACK:GTOUT,
Example:
+ACK:GTOUT,240100,135790246811220,,0004,20090214093254,11F0$
XX0000 – XXFFFF,
Protocol Version 6
X∈{'A' – 'Z','0' – '9'}
k
Unique ID 15 IMEI
i n
Device Name <=20 '0' – '9' 'a' – 'z' 'A' – 'Z' '-' '_'
l l
c ia
e t
u n
Q fide
3.2.5.2. Digital Input Port Setting
The command AT+GTDIS is used to configure the parameters of 2 digital input ports. Input
n
<Ignition Detection> is dedicated for ignition detection. The digital input port 1 is customizable. If
the logical status is changed on the digital input port 1, the device will report message
o
+RESP:GTDIS to the backend server.
C
 AT+GTDIS=
Example:
AT+GTDIS=gmt200,0,2,,,1,1,4,,,,,,,0005$
2 Ignition Detection 1 0 0
3 Sample Period <=2 0|1 – 12(×2s) 1
4 Reserved 0
5 No ignition 1 0|1 0
6 Input ID 1 1 1 1
7 Enable 1 0|1 0
8 Debounce Time <=2 0 – 20(×10ms) 0
9 Validity Time <=2 0|1 – 12(×2s) 0
10 Reserved 0
11 Reserved 0
12 Reserved 0
13 Reserved 0
14 Reserved 0
k
n
 <Ignition Detection>: ID of the ignition detection port.
i

l
<No ignition >: No Ignition wire connection.
l
 0: Ignition signal is connected.
c a
 1: Ignition signal is not connected.
i
 <Input ID 1>: the digital input port ID.
e t
 <Sample Period>: the sampling period of the non-interruptible input port.
n

u
<Enable>: Enable or disable the interrupt input.
 0: Disable
Q fide
 1: Enable
 <Debounce Time>: The time for debouncing.
 <Validity Time>: The validity time of the input port, 0 means not to check the validity time.
n
The acknowledgment message of AT+GTDIS command:
o
 +ACK:GTDIS,
Example:
C
+ACK:GTDIS,240100,135790246811220,,0005,20090214093254,11F0$
XX0000 – XXFFFF,
Protocol Version 6
X∈{'A' – 'Z','0' – '9'}
Unique ID 15 IMEI
Device Name <=20 '0' – '9' 'a' – 'z' 'A' – 'Z' '-' '_'
3.2.5.3. Input/Output Port Binding

This command is used to configure the user defined output-port action triggered by input ports. If
the IO combination is set and the corresponding condition appears, the device will output specified
wave shape on the specified output port. Otherwise, the device will restore the initial status of the
specified output port. And the device will report message +RESP:GTIOB to the backend server
when the logical status of bound input ports changes.
 AT+GTIOB=
Example:
AT+GTIOB=gmt200,1,3,3,3,0,0,,,,,,,0006$
k
AT+GTIOB=gmt200,1,3,3,3,1,1,,,,,,,0006$
n
l i l
c a
2 IOB ID 1 0–2
e t i
3 Input Mask 1 0–3 0
u n
4 Trigger Mask 1 0–3 0
Q fide
5 Input Sample Period <=2 0|1 – 12(×2s) 0
6 Output ID 1 0-1 0
8 Reserved 0
n
9 Reserved 0
o
10 Reserved 0
C
11 Reserved 0
12 Reserved 0
13 Reserved 0
 <IOB ID>: ID of the user defined IO binding.

 <Input Mask>: Bitwise mask for input ports composition. Each bit, from bit 0 to bit 1,
represents one digital input port. Set to 1 to enable and 0 to disable corresponding input port.
 bit0: ignition detection
 bit1: digital input 1
 <Trigger Mask>: bitwise mask for trigger condition composition of the corresponding input
ports. Each bit, from bit 0 to bit 1, represents the logical status of the corresponding input
port to trigger the IOB event. Set to 1 to use enable status as the trigger condition and 0 to use
disable status. Only when the logical status of all the input ports in one IO binding meets the
trigger condition is the IOB event triggered.
 bit0: ignition detection
 bit1: digital input 1
 <Input Sample Period>: The period to check the status of all the digital input ports in one IO
binding. AT+GTIOB and AT+GTDIS use independent sample period to check the input port
status even for the same input port.
 <Output ID>: ID of the output port to output specified wave when the trigger condition meets.
0 means no wave will be output.
k
The acknowledgment message of AT+GTIOB command:
 +ACK:GTIOB,
l i n l
Example:
+ACK:GTIOB, 240100,135790246811220,,1,0006,20090214093254,11F0$
c ia
e t
XX0000 – XXFFFF,
Protocol Version 6
u n
X∈{‘A’ – ‘Z’,’0’ – ‘9’}
Q fide
Unique ID 15 IMEI
Device Name <=20 '0' – '9' 'a' – 'z' 'A' – 'Z' '-' '_'
IOB ID 1 0–2
n
o
C
3.2.5.4. External Power Supply Monitoring

The command AT+GTEPS is used to configure the parameters of external power supply
monitoring. The device will measure and monitor the voltage of the external power supply. If the
voltage of the external power supply matches the predefined alarm condition, the device will
report an alarm message +RESP:GTEPS to the backend server to notify the status of the external
power supply.
 AT+GTEPS=
Example:
AT+GTEPS=gmt200,2,250,12000,3,2,1,1,,,1,1,,,0007$
2 Mode 1 0–3 2
3 Min Threshold <=5 250 – 32000 mV 9500
4 Max Threshold <=5 250 – 32000 mV 15000
5 Sample Period <=2 0|1 – 12(×2s) 1
6 Debounce Time 1 0 – 5 (×1s) 1
7 Output ID 1 0-1 0
k
n
9 Reserved 0
l i l
10 Reserved 0
c a
11 Sync with FRI 1 0|1 0
e t i
12 Validity 1 0-5（×5s） 1
u n
13 Reserved 0
Q fide
14 Reserved 0
n
 <Mode>: Working mode of the external power supply monitoring.
 0: Disable the external power supply monitoring.
o
 1: Enable the external power supply monitoring. If the current voltage is within the
range of (<Min Threshold>, <Max Threshold>), the +RESP:GTEPS alarm will be
C
triggered.
 2: Enable the external power supply monitoring. If the current voltage is outside the
range of (<Min Threshold>, <Max Threshold>), the +RESP:GTEPS alarm will be
triggered.
 3: Enable the external power supply monitoring. If the current voltage is within or
outside the range of (<Min Threshold>, <Max Threshold>), the +RESP:GTEPS
alarm will be triggered.
 <Min Threshold>: The lower limit to the voltage of the external power supply to trigger the
alarm.
 <Max Threshold>: The upper limit to the voltage of the external power supply to trigger the
alarm.
 <Sample Period>: The sampling period to measure the external power supply.
 <Debounce Time>: The time for debouncing to avoid exceptional voltage drop of the external
power supply.In general, <debounce time> shall not be larger than <sample period>.
 <Output ID>: ID of the output port to output specified wave shape when the +RESP:GTEPS
alarm is triggered. If set to 0, no output wave.
 <Sync with FRI>: Besides the +RESP:GTEPS alarm report, the device can also send the
voltage of external power supply periodically along with the fixed report message.
 0: Do not report external power supply voltage with fixed report message.
 1: Report external power supply voltage with fixed report message.
 <Validity>: If the current voltage meets the alarm condition and maintains a period of time
defined by < Validity >, the +RESP:GTEPS alarm will be triggered. The parameter is used
only when the parameter < Mode > in AT +GTEPS is set to 3.
The acknowledgment message of AT+GTEPS command:

 +ACK:GTEPS,
k
Example:
n
+ACK:GTEPS,240100,135790246811220,,0007,20090214093254,11F0$
l i l
c a
XX0000 – XXFFFF,
i
Protocol Version 6
X∈{'A' – 'Z','0' – '9'}
e t
Unique ID 15 IMEI
u n
Device Name <=20 '0' – '9' 'a' – 'z' 'A' – 'Z' '-' '_'
Q fide
n
Co
3.2.6. Other Settings
3.2.6.1. Real Time Operation
The command AT+GTRTO is used to retrieve information from the terminal or control the
terminal to execute certain actions.
 AT+GTRTO=
Example:
AT+GTRTO=gmt200,A,,,,,,0014$
2 Sub Command 1 0–D
3 Reserved 0
4 Reserved 0
5 Reserved 0
6 Reserved 0
7 Reserved 0
k
<Sub Command>: Valid value is 0–9, A, B, C, D.
 0: GPS. Get the GPS related information via message +RESP:GTGPS.
n
 1: RTL. Request the terminal to report its current position immediately via message
l i l
+RESP:GTRTL.
 2: READ. Get the current configuration of the terminal via message
c a
+RESP:GTALL.
i
 3: REBOOT. Reboot the terminal.
e t
 4: RESET. Reset all parameters to factory setting. Parameters configured by
u n
AT+GTBSI, AT+GTSRI, AT+GTCFG ,AT+GTPIN and AT+GTTMA will not be
reset.
Q fide
 5: PWROFF. Power off the device.
 6: CID. Get the ICCID of the SIM card which is being used by the terminal via
message +RESP:GTCID.
 7: CSQ. Get the current GSM signal level of the terminal via message
+RESP:GTCSQ.
n
 8: VER. Get the version information of the device via message +RESP:GTVER.
o
 9: BAT. Get the battery level and adapter status of the terminal via message
+RESP:GTBAT.
 A: IOS. Get status of all the IO ports via message +RESP:GTIOS.
C
 B: TMZ. Get the time zone settings via message +RESP:GTTMZ.
 C: GIR. Get cell information via message +RESP:GTGSM.
 D: DELBUF. Delete all the buffered reports.
 E: Reserved.
 F; RJB. Reset jamming behavior. This command is used in the AT+GTJBS.
The acknowledgment message of AT+GTRTO command:

 +ACK:GTRTO,
Example:
+ACK:GTRTO,240100,135790246811220,,IOS,0014,20090214093254,11F1$
Protocol Version 6 XX0000 – XXFFFF,
X∈{'A' – 'Z','0' – '9'}
Unique ID 15 IMEI
Device Name <=20 '0' – '9' 'a' – 'z' 'A' – 'Z' '-' '_'
Sub Command <=6 Sub command string
k
 <Sub Command>: A string to indicate the sub command of AT+GTRTO.
l i n l
3.2.6.2. Ignition Time Counter
c a
The command AT+GTHMC is used to measure time of use with each actuation of the ignition on.
e t i
To use this command, the ignition signal must be connected to the device. When the device sends
+RESP:GTFRI and +RESP:GTIGN and +RESP:GTIGF, <Ignition Time Count> will be sent
u n
in these reports.
Q fide
 AT+GTHMC=
Example:
AT+GTHMC=gmt200,1,12345:12:34,,,,,,,,,0015$
n
o
2 Ignition Time Counter
1 0|1 0
Enable
C
3 Initial Ignition Time 00000:00:00-99999:00:0
11 00000:00:00
Count 0
4 Reserved 0
5 Reserved 0
6 Reserved 0
7 Reserved 0
8 Reserved 0
9 Reserved 0
10 Reserved 0
11 Reserved 0
 <Ignition Time Counter Enable>: Enable or disable ignition time counter function. If ignition
time counter function is enabled, ignition time count will be increased when the device is in
ignition.
 0: Disable ignition time counter function
 1: Enable ignition time counter function
 <Initial Ignition Time Count>: Initial ignition time count. It is formatted with 5 hour digits
and 2 minute digits and 2 second digits and ranges from 00000:00:00– 99999:00:00. When
engine is on at the first time, <Ignition Time Count> which report in +RESP:GTFRI
k
/+RESP:GTIGN/+RESP:GTIGF will be increased based on this value.
l i n l
The acknowledgment message of AT+GTHMC command:
c a
 +ACK:GTHMC,
t i
Example:
e
+ACK:GTHMC,240100,135790246811220,,0015,20090214093254,11F0$
u n
Q fide
XX0000 – XXFFFF,
Protocol Version 6
X∈{'A' – 'Z','0' – '9'}
Unique ID 15 IMEI
Device Name <=20 '0' – '9' 'a' – 'z' 'A' – 'Z' '-' '_'
n
o
C
3.3. Report
This section defines the formats of the report messages. Due to the max length of SMS message
(160 bytes), it is recommended to carefully set the <Report Composition Mask> in AT+GTCFG
to limit the length of the report which contains GPS position information if you choose SMS as
the transmit method. Otherwise the report will be truncated to fit the length of SMS message.
3.3.1. Position Related Report
 +RESP:GTTOW,
If the tow alarm is enabled by the command AT+GTTOW, the device will send the message
+RESP:GTTOW to the backend server when the motion sensor detects tow.
 +RESP:GTDIS,
If the status of digital inputs are detected being changed, the device will send the message
+RESP:GTDIS to the backend server.
 +RESP:GTIOB,
If the IO combination is set and the corresponding condition appears, the device will report the
k
message +RESP:GTIOB to the backend server.
i n
 +RESP:GTGEO,
l l
If Geo-Fence is configured and enabled, the device will send the message +RESP:GTGEO to
c a
the backend server according to settings when the device enters or exits the Geo-Fence.
e t i
 +RESP:GTSPD,
u n
If the speed alarm is enabled, the device will send the message +RESP:GTSPD to the backend
server when the speed of the device is detected into the alarm range,.
Q fide
 +RESP:GTSOS,
If the SOS mode is set to 1, the device will send the message +RESP:GTSOS to the backend
server when the corresponding digital input port triggers SOS.
n
 +RESP:GTRTL,
o
After the device receives the command AT+GTRTO, it will start GPS to get the current position
and then send the message +RESP:GTRTL to the backend server.
C
 +RESP:GTDOG,
The protocol watchdog reboot message.
 +RESP:GTIGL,
The protocol ignition on and ignition off location message.
 +RESP:GTHBM,
If harsh behavior is detected, this message will be sent to the backend server.
All of the above report messages have the same format as shown below.
Example:
+RESP:GTTOW,240100,135790246811220,,,10,1,1,4.3,92,70.0,121.354335,31.222073,200902
14013254,0460,0000,18d8,6141,00,2000.0,20090214093254,11F0$
+RESP:GTDIS,240100,135790246811220,,,10,1,1,4.3,92,70.0,121.354335,31.222073,2009021
4013254,0460,0000,18d8,6141,00,2000.0,20090214093254,11F0$
+RESP:GTIOB,240100,135790246811220,,,10,1,1,4.3,92,70.0,121.354335,31.222073,2009021
4013254,0460,0000,18d8,6141,00,2000.0,20090214093254,11F0$
+RESP:GTGEO,240100,135790246811220,,,00,1,1,4.3,92,70.0,121.354335,31.222073,200902
14013254,0460,0000,18d8,6141,00,2000.0,20090214093254,11F0$
+RESP:GTSPD,240100,135790246811220,,,00,1,1,4.3,92,70.0,121.354335,31.222073,2009021
4013254,0460,0000,18d8,6141,00,2000.0,20090214093254,11F0$
k
+RESP:GTSOS,240100,135790246811220,,,10,1,1,4.3,92,70.0,121.354335,31.222073,2009021
n
4013254,0460,0000,18d8,6141,00,2000.0,20090214093254,11F0$
l i l
+RESP:GTRTL,240100,135790246811220,,,00,1,1,4.3,92,70.0,121.354335,31.222073,200902
c a
14013254,0460,0000,18d8,6141,00,2000.0,20090214093254,11F0$
e t i
+RESP:GTDOG,240100,135790246811220,,,01,1,1,4.3,92,70.0,121.354335,31.222073,200902
u n
14013254,0460,0000,18d8,6141,00,2000.0,20090214093254,11F0$
Q fide
+RESP:GTDOG,240100,135790246811220,,,13,1,1,4.3,92,70.0,121.354335,31.222073,200902
14013254,0460,0000,18d8,6141,00,2000.0,20090214093254,11F0$
+RESP:GTIGL,240100,135790246811220,,,00,1,1,4.3,92,70.0,121.354335,31.222073,2009021
4013254,0460,0000,18d8,6141,00,2000.0,20090214093254,11F0$
o n
+RESP:GTHBM,240100,135790246811220,,,10,1,1,4.3,92,70.0,121.354335,31.222073,200902
14013254,0460,0000,18d8,6141,00,2000.0,20090214093254,11F0$
C
+RESP:GTHBM,240100,135790246811220,,,11,1,1,24.3,92,70.0,121.354335,31.222073,20090
214013254,0460,0000,18d8,6141,00,2000.0,20090214093254,11F0$
XX0000 – XXFFFF,
Protocol Version 6
X∈{'A' – 'Z','0' – '9'}
Unique ID 15 IMEI
Device Name <=20 '0' – '9' 'a' – 'z' 'A' – 'Z' '-' '_'
Reserved
Report ID/Report Type 2 X(0-4)X(0-3)
Number 1 0–1
GPS Accuracy <=2 0|1 – 50
Speed <=5 0.0 – 999.9 km /h
Azimuth <=3 0 – 359
Altitude <=8 (–)xxxxx.x m
Longitude <=11 (–)xxx.xxxxxx
Latitude <=10 (–)xx.xxxxxx
GPS UTC Time 14 YYYYMMDDHHMMSS
MCC 4 0XXX
k
MNC 4 0XXX
n
LAC 4 XXXX
l i l
Cell ID 4 XXXX
c a
Reserved 2 00
e t i
Mileage <=9 0.0 – 4294967.0 km
u n
Q fide
 <Report ID/Report Type>: The report ID and the type of the report type in hex format. 4 high
bits mean report ID and 4 low bits means report type.
n
Report ID has different meanings in different messages as below.
o
 The ID of digital input port which triggers the report message +RESP:GTDIS and
+RESP:GTSOS. The value is 1.
 The ID of the bound IO which triggers the report message +RESP:GTIOB. The range
C
is 0 – 2.
 The ID of Geo-Fence in the report message +RESP:GTGEO. The range is 0 – 4.
 The ID of the digital input port which triggers the reboot message +RESP:GTDOG.
The valid value is 1 .
 The speed level of which the harsh behavior is detected in message +RESP:GTHBM. 3
is high speed, 2 is medium speed and 1 is low speed.
For the rest of the messages, it will always be 0.
Report type has different meanings in different messages as below.

 In the +RESP:GTDIS report message generated by the digital input
0: The current logical status of the input port is disable status.
1: The current logical status of the input is enable status.
 In the +RESP:GTIOB report message generated by bound IO
0: The current logical status of the bound IO does not meet the alarm condition.
1: The current logical status of the bound IO meets the alarm condition.
 In Geo-Fence report message +RESP:GTGEO
0: Exit from the Geo-Fence.
1: Enter the Geo-Fence.
 In the message of speed alarm +RESP:GTSPD
0: Outside of the predefined speed range.
1: Inside of the predefined speed range.
 In the message of protocol watch dog reboot message +RESP:GTDOG
1: Reboot message for time based working mode
2: Reboot message for ignition on working mode
3: Reboot message for input triggered reboot
4: Reboot message for GSM watchdog reboot
k
5: Reboot message for GPRS watchdog reboot
 In the message of ignition on and ignition off message +RESP:GTIGL
i n
0 :the engine is ignition on
l l
1: the engine is ignition off
c a
 In the message of harsh behavior monitoring message +RESP:GTHBM
i
0: Harsh braking behavior
e t
1: Harsh acceleration behavior
u n
For the rest of the messages, it will always be 0.
 <Number>: The number of the GPS position included in the report message. Generally, it
Q fide
equals to 1.
 <GPS Accuracy>: The HDOP defined in NMEA0183 (The National Marine Electronics
Association (NMEA) is a non-profit association of manufacturers, distributors, dealers,
educational institutions, and others interested in peripheral marine electronics occupations.
The NMEA 0183 standard defines an electrical interface and data protocol for
n
communications between marine instrumentation.). The range of value is 0 – 50. Here 0
o
means no GPS fix.
 <Speed>: The current speed. Unit: km/h
 <Azimuth>: The azimuth of the GPS fixing.
C
 <Altitude>: The height above the sea level.
 <Longitude>: The longitude of the current position.
 <Latitude>: The latitude of the current position.
 <GPS UTC Time>: The UTC time from the GPS chip.
 <MCC>: Mobile country code. It is 3 digits in length and ranges from 000–999.
 <MNC>: Mobile network code. It is 3 digits in length and ranges from 000–999.
 <LAC>: Location area code in hex format.
 <Cell ID>: Cell ID in hex format.
 <Mileage>: The current total mileage.
 +RESP:GTFRI,
If fixed report is enabled, the device will send the message +RESP:GTFRI to the backend server
according to the working mode.
Example:
+RESP:GTFRI,240100,135790246811220,,,10,1,1,4.3,92,70.0,121.354335,31.222073,2009021
4013254,0460,0000,18d8,6141,00,2000.0,12345:12:34,,80,,,,,,20090214093254,11F0$
+RESP:GTFRI,240100,135790246811220,,,10,2,1,4.3,92,70.0,121.354335,31.222073,2009021
4013254,0460,0000,18d8,6141,00,0,4.3,92,70.0,121.354335,31.222073,20090101000000,0460,0
000,18d8,6141,00,2000.0,12345:12:34,,,80,,,,,,20090214093254,11F0$
XX0000 – XXFFFF,
Protocol Version 6
X∈{'A' – 'Z','0' – '9'}
k
Unique ID 15 IMEI
n
Device Name <=20 '0' – '9' 'a' – 'z' 'A' – 'Z' '-' '_'
l i l
External Power Supply <=5 0 – 32000 mV
c a
Report ID/Report Type 2 X(1-4)X(0-1)
e t i
Number <=2 0 – 15
u n
Speed <=5 0.0 – 999.9 km /h
Q fide
Azimuth <=3 0 – 359
n
o
MCC 4 0XXX
C
MNC 4 0XXX
LAC 4 XXXX
Cell ID 4 XXXX
Reserved 2 00
Mileage <=9 0.0 – 4294967.0 km
Ignition Time Count 11 HHHHH:MM:SS
Reserved 0
Reserved
Backup Battery
<=3 0 – 100
Percentage
Digital Input 2 00-03
Digital Output 2 00/01
Reserved
Reserved
 <External Power Supply>: The voltage of the external power supply. If using command
AT+GTEPS to set the device report the external power supply voltage periodically with
k
fixed report, the device will send the current voltage along with +RESP:GTFRI message to
n
the backend server. If not set, this field will be empty.
i
 <Report ID/Report Type>: Indicate the working mode of the fixed report and the type of the
l l
message.
c a
Report ID has four meanings as below.
i
 1: fixed timing report.
e t
 2: fixed distance report.
u n
 3: fixed mileage report.
 4: fixed timing and mileage report.
Q fide
Report type has two meanings as below.
 0: the normal fixed report.
 1: corner report which indicates that the device just turns around a corner.
 <Number>: The number of the GPS position included in the report message. In the message
+RESP:GTFRI, it probably includes one or several GPS position according to the setting of
n
<Send Interval> and <Check Interval>. If multi-position in one +RESP:GTFRI message, the
o
green part repeats.
 <Ignition Time Count>: If ignition time counter function is enabled by the command
C
AT+GTHMC, total ignition time counted when engine is on will be reported in this field. It
is formatted with 5 hour digits and 2 minute digits and 2 second digits and ranges from
00000:00:00– 99999:00:00. If the function is disabled, this field will be reserved.
 <Backup Battery Percentage>: The current volume of the backup battery in percentage.
 <Digital Input>: A bitwise hex integer to represent the logical status of the digital input. From
the lowest bit to the highest bit, each bit represents ignition detection and the digital input 1
respectively. For each bit, 0 means disable status, 1 means enable status.
 <Digital Output>: A bitwise hex integer to represent the logical status of the digital output.
From the lowest bit to the highest bit, each bit represents the digital output 1 and otheroutput
 +RESP:GTEPS,
If the external power supply monitoring is enabled by the command AT+GTEPS, the device will
send the message +RESP:GTEPS to the backend server when the voltage of the external power
supply enters the alarm range.
Example:
+RESP:GTEPS,240100,135790246811220,,13500,00,1,1,4.3,92,70.0,121.354335,31.222073,20
090214013254,0460,0000,18d8,6141,00,2000.0,20090214093254,11F0$
240100
XX0000 – XXFFFF,
Protocol Version 6
X∈{'A' – 'Z','0' – '9'}
k
Unique ID 15 IMEI
n
Device Name <=20 '0' – '9' 'a' – 'z' 'A' – 'Z' '-' '_'
l i l
External Power Supply <=5 0 – 32000 mV
c a
Report ID/Report Type 2 X(0)X(0-1)
e t i
Number <=2 0–1
u n
Speed <=5 0.0 – 999.9 km /h
Q fide
Azimuth <=3 0 – 359
n
o
MCC 4 0XXX
C
MNC 4 0XXX
LAC 4 XXXX
Cell ID 4 XXXX
Reserved 2 00
Mileage <=9 0.0 – 4294967.0 km
 < Analog Input VCC>: The value of the analog input voltage. When the voltage of the analog
input meets the alarm condition as set by command AT+GTEPS, the device will send the
current analog input voltage with +RESP:GTEPS message to the backend server.
 <Report ID/Report Type>: The report ID and the type of the report type in hex format. 4 high
bits mean report ID and 4 low bits means report type.
Report ID has different meanings in these two messages.
 The ID of analog input port which triggers report message +RESP:GTEPS. The value
is 0.
Report type has two meanings as below.
 0: Outside of the predefined range.
 1: Inside of the predefined range.
 <Number>: The number of the GPS position included in the report message. Generally, it
equals to 1.
k
 +RESP:GTLBC,
i n
If the parameter <Location By Call> is set to 1 by the command AT+GTCFG, the device will get
l l
and send the current position to the backend server by the message +RESP:GTLBC when there
c a
is an incoming call.
e t i
Example:
u n
+RESP:GTLBC,240100,135790246811220,,+8613800000000,1,4.3,92,70.0,121.354335,31.222
073,20090214013254,0460,0000,18d8,6141,00,20090214093254,11F0$
Q fide
XX0000 – XXFFFF,
Protocol Version 6
X∈{'A' – 'Z','0' – '9'}
n
Unique ID 15 IMEI
o
Device Name <=20 '0' – '9' 'a' – 'z' 'A' – 'Z' '-' '_'
Call Number <=20 phone number
C
Speed <=5 0.0 – 999.9 km /h
Azimuth <=3 0 – 359
MCC 4 0XXX
MNC 4 0XXX
LAC 4 XXXX
Cell ID 4 XXXX
Reserved 2 00 00
 <Call Number>: The phone number of the incoming call which triggers the report message.
i n k l
cl ia
ue n t
Q fide
o n
C
3.3.2. Device Information Report
If the device information report function is enabled by the command AT+GTCFG, the device
will send the device information by the message +RESP:GTINF to the backend server
periodically.
 +RESP:GTINF,
Example:
+RESP:GTINF,240100,135790246811220,,16,898600810906F8048812,16,0,1,11870,,4.1,0,0,0,
,20090214013254,, ,,00,00,+0800,0,20090214093254,11F0$
k
XX0000 – XXFFFF,
Protocol Version 6
X∈{'A' – 'Z','0' – '9'}
i n l
Unique ID 15 IMEI
l
Device Name <=20 '0' – '9' 'a' – 'z' 'A' – 'Z' '-' '_'
c ia
State 2 11|12|21|22|41|42|1A|16
e t
ICCID 20
u n
CSQ RSSI <=2 0 – 31|99
Q fide
CSQ BER <=2 0 – 7|99
External Power Supply 1 0|1
External Power VCC <=5 0 – 32000mV
n
Reserved 0
o
Backup Battery VCC <=4 0.0 – 4.5 V
Charging 1 0|1
C
LED On 1 0|1
GPS On Need 1 0|1
Reserved 0
Last Fix UTC Time 14 YYYYMMDDHHMMSS
Reserved 0
0
Reserved
Reserved 0
Digital Input 2 00 – 03
Digital Output 2 00/01
Time Zone Offset 5 ±HHMM
Daylight Saving 1 0|1
 <State>: The current motion state of the device.

 16 (Tow): The device attached vehicle is ignition off and it is towed.
 1A (Fake Tow): The device attached vehicle is ignition off and it might be towed.
 11 (Ignition Off Rest): The device attached vehicle is ignition off and it is motionless.
k
 12 (Ignition Off Motion): The device attached vehicle is ignition off and it is moving
n
before it is treated as being towed.
i l
 21 (Ignition On Rest): The device attached vehicle is ignition on and it is motion less
l
 22 (Ignition On Motion): The device attached vehicle is ignition on and it is moving
c a
 41 (Sensor Rest): The device attached vehicle is motionless without ignition signal
t i
detected
e
 42 (Sensor Motion): The device attached vehicle is moving without ignition signal
u n
detected
 <ICCID>: The ICCID of the SIM card.
Q fide
 <CSQ RSSI>: The signal strength level.
CSQ RSSI Signal Strength (dBm)
0 <-133
1 -111
n
2 – 30 -109 – -53
31 >-51
o
99 Unknown
 <CSQ BER>: The quality of the GSM signal. The range is 0-7, 99 for unknown.
C
 <External Power Supply>: Whether the external power supply is connected.
 0: Not connected
 1: Connected
 <External Power Supply VCC>: The voltage of the external power supply.
 <Backup Battery VCC>: The voltage of the backup battery. The value of this field is only
valid when the external power is not connected.
 <Charging>: Whether the backup battery is charging when the main power supply is
connected.
 0: Not charging
 1: Charging
 <Last Fix UTC Time>: The UTC time of the latest successful GPS fixing.
 <Digital Input>: A bitwise hex integer to represents the logical status of the digital input.
From the lowest bit to the highest bit, each bit represents ignition detection and the digital
input 1 respectively. For each bit, 0 means disable status, 1 means enable status.
 <Digital Output>: A bitwise hex integer to represents the logical status of the digital output.
From the lowest bit to the highest bit, each bit represents the digital output 1 and other output
 <Time Zone Offset>: The time offset of the local time zone to the UTC time.
 <Daylight Saving>: The current setting of the daylight saving.
 0: Daylight saving is disabled
 1: Daylight saving is enabled
i n k l
cl ia
ue n t
Q fide
o n
C
3.3.3. Report of Real Time Querying
3.3.3.1. +RESP:GTGPS
After the device receives the command AT+GTRTO to read the GPS information, it will send
the GPS information to the backend server by the message +RESP:GTGPS.
 +RESP:GTGPS,
Example:
+RESP:GTGPS,240100,135790246811220,,0,,,0000,,,20090214013254,20090214093254,11F0
$
k
XX0000 – XXFFFF,
Protocol Version 6
n
X∈{'A' – 'Z','0' – '9'}
l i l
Unique ID 15 IMEI
c a
Device Name <=20 '0' – '9' 'a' – 'z' 'A' – 'Z' '-' '_'
e t i
GPS On Need 1 0|1
u n
Reserved 0
Q fide
Reserved 0
Report Composition
4 0000 – FFFF
Mask
Reserved 0
n
Reserved 0
o
Last Fix UTC Time 14 YYYYMMDDHHMMSS
C
 <Report Composition Mask>: Refer to <Report Composition Mask> of AT+GTCFG

command
3.3.3.2. +RESP:GTALL
After the device receives the command AT+GTRTO to read all the configurations, it will send
all configurations to the backend server by the message +RESP:GTALL. This message only
sends via GPRS even if the report mode is force on SMS.
 +RESP:GTALL,
Example:
+RESP:GTALL,240103,862170014703969,gmt2000505,BSI,cmnet,,,,,,,SRI,4,,1,116.228.146.
250,7006,0.0.0.0,0,,60,1,0,,,,CFG,gmt200,gmt2000505,0,0.0,1,1,007F,2,,1FFFF,,1,1,600,0,,0,0,,
,TOW,1,60,60,180,0,0,,,2,3,2,,,,,,,,,EPS,2,9500,15000,1,1,0,0,,,1,,,,DIS,,,,0,1,1,1,,,,,,,IOB,0,00,0
0,0,0,0,,,,,,,1,00,00,0,0,0,0,0,,,,,2,00,00,0,0,0,0,0,,,,,TMZ,+0800,0,,,,,FRI,1,0,,1,0000,0000,60,30
0,1000,1000,,0,600,,,,,GEO,0,0,121.390678,31.164373,50,120,0,0,,,,,,,1,0,121.390678,31.16437
3,50,120,0,0,,,,,,,2,0,121.390678,31.164373,50,120,0,0,,,,,,,3,0,121.390678,31.164373,50,120,0,0
,,,,,,,4,0,121.390678,31.164373,50,120,0,0,,,,,,,SPD,1,30,90,60,180,0,0,,,,,,,,,,,,,,SOS,0,0,,0,0,,,,,,,
PIN,1,1234,,,,,,OWH,0,1f,0900,1200,1300,1800,,,,0,0,,,,,,,DOG,0,60,1,1700,,1,0,,60,60,,
IDL,0,2,1,,,,,0,0,,,,,,,HMC,1,00000:00:00,,,,,,,,,HBM,1,,,100,1,1,,60,5,5,,,10,10,,0,0,0,0,,,,,HRM
,,,7f,fe5fff,fe5fff,ff7f,ff,,,,,SSR,1,2,1,5,,,,,JDC,1,10,40,,,,,0,0,,,,PDS,0,0,,,,,,,20130110102100,01
k
64 JBS,1,,60,3600,1,30,,,,, WLT,3,13813888888,13913999999,,,,,,,,,,,,,$
i n l
XX0000 – XXFFFF,
l
Protocol Version 6
X∈{'A' – 'Z','0' – '9'}
c ia
Unique ID 15 IMEI
e t
Device Name <=20 '0' – '9' 'a' – 'z' 'A' – 'Z' '-' '_'
u n
BSI 3 BSI BSI
Q fide
APN <=40
APN User Name <=30
APN Password <=30
Reserved 0
n
Reserved 0
o
Reserved 0
C
Reserved 0
SRI 3 SRI SRI
Report Mode 1 0–6
Reserved 1 0|1
Buffer Report 1 0–2
Main Server IP / <=60

Domain Name
Main Server Port <=5 0 – 65535
Backup Server IP <=15
Backup Server Port <=5 0 – 65535
SMS Gateway <=20
Heartbeat Interval <=3 0|5 – 360min
SACK Enable 1 0|1 0
Protocol Format 1 0|1 0
Reserved 0
Reserved 0
Reserved 0
CFG 3 CFG CFG
k
Password 4 – 6 '0' – '9' 'a' – 'z' 'A' – 'Z'
n
Device Name <=20 '0' – '9' 'a' – 'z' 'A' – 'Z' '-' '_'
l i l
ODO Enable 1 0|1
c a
ODO Initial Mileage <=9 0.0 – 4294967.0Km
e t i
GPS On Need 1 0|1
u n
GSM report 1 0–3
Q fide
Report Composition
<=4 0000 – FFFF
Mask
Power Saving Mode 1 0 –2
Reserved 0
n
Event Mask <=4 00000000 – FFFFFFFF
o
Reserved 0
LED On 1 0|1
C
Info Report Enable 1 0|1
Info Report Interval <=5 30 – 86400sec
Location By Call 1 0–2
Reserved 0
Power Mode 1 0–2
Agps Mode 1 0|1
Reserved 0
Reserved 0
TOW 3 TOW TOW
Tow Enable 1 0|1
Engine Off to Tow <=2 0 – 900 sec
Fake Tow Delay <=2 0 – 600 sec
Tow Interval <=5 0 – 86400 sec
Tow Output ID 1 0-1
Tow Output Status 1 0|1
Reserved 0
Reserved 0
Rest Duration <=3 1 – 255(×15sec)
k
Motion Duration <=2 1 – 99(×100ms)
n
Motion Threshold 1 2–9
l i l
Reserved 0
c a
Reserved 0
e t i
Reserved 0
u n
Reserved 0
Q fide
Reserved 0
Reserved 0
Reserved 0
Reserved 0
n
EPS 3 EPS EPS
o
Mode 1 0–3
C
Min Threshold <=5 250 – 32000 mV
Max Threshold <=5 250 – 32000 mV
Sample Period <=2 0|1 – 12(×2s)
Debounce Time 1 0 – 5(×1s)
Output ID 1 0-1
Output Status 1 0|1
Reserved 0
Reserved 0
Sync with FRI 1 0|1
Validity 10 0-5(×5s)
Reserved 0
Reserved 0
DIS 3 DIS DIS
Ignition Detection 1 0 0
Sample Period <=2 0|1 – 12(×2s)
Reserved 0
No ignition 1 0|1 0
Input ID 1 1 1 1
k
Enable 1 0|1
n
Debounce Time <=2 0 – 20(×10ms)
l i l
Reserved 0
c a
Reserved 0
e t i
Reserved 0
u n
Reserved 0
Q fide
Reserved 0
Reserved 0
IOB 3 IOB IOB
IOB ID 1 0–2
n
Input Mask 1 0–3 0
o
Trigger Mask 1 0–3 0
C
Input Sample Period <=2 0|1 – 12(×2s) 0
Output ID 1 0-1 0
Output Status 1 0|1 0
Reserved 0
Reserved 0
Reserved 0
Reserved 0
Reserved 0
Reserved 0
TMZ 3 TMZ TMZ
Time Zone 5 –|+HHMM
Reserved 0
Reserved 0
Reserved 0
Reserved 0
FRI 3 FRI FRI
Mode 1 0–4
k
Discard No Fix 2 0|1
n
Reserved 0
l i l
Period Enable 1 0|1
c a
Begin Time 4 HHMM
e t i
End Time 4 HHMM
u n
Check Interval <=5 0|30 – 86400sec
Q fide
Send Interval <=5 0|5 – 86400sec
Distance <=5 300 – 65535m
Mileage <=5 300 – 65535m
Reserved 0
n
Corner Report <=3 0 | 40 – 100
o
IGF Report Interval <=5 0|5-86400sec
C
Reserved 0
Reserved 0
GEO 3 GEO GEO
GEO ID0 1 0 0
Mode 1 0–3
Radius <=7 50 – 6000000m
Check Interval <=5 0 | 5 – 86400sec
Output ID 1 0-1
Output Status 1 0|1
Reserved 0
Reserved 0
Reserved 0
Reserved 0
Reserved 0
Reserved 0
GEO ID1 1 1 1
k
Mode 1 0–3
n
l i l
c a
Radius <=7 50 – 6000000m
e t i
u n
Output ID 1 0-1
Q fide
Output Status 1 0|1
Reserved 0
Reserved 0
Reserved 0
n
Reserved 0
o
Reserved 0
C
Reserved 0
GEO ID2 1 2 2
Mode 1 0–3
Radius <=7 50 – 6000000m
Output ID 1 0-1
Output Status 1 0|1
Reserved 0
Reserved 0
Reserved 0
Reserved 0
Reserved 0
Reserved 0
GEO ID3 1 3 3
Mode 1 0–3
k
n
Radius <=7 50 – 6000000m
l i l
c a
Output ID 1 0-1
e t i
Output Status 1 0|1
u n
Reserved 0
Q fide
Reserved 0
Reserved 0
Reserved 0
Reserved 0
n
Reserved 0
o
GEO ID4 1 4 4
C
Mode 1 0–3
Radius <=7 50 – 6000000m
Output ID 1 0-1
Output Status 1 0|1
Reserved 0
Reserved 0
Reserved 0
Reserved 0
Reserved 0
Reserved 0
SPD 3 SPD SPD
Mode 1 0–2
Min Speed <=3 0 – 400km/h
Max Speed <=3 0 – 400km/h
Validity <=4 15 – 3600sec
k
Send Interval <=4 30 – 3600sec
n
Output ID 1 0-1
l i l
Output Status 1 0|1
c a
Reserved 0
e t i
Reserved 0
u n
Reserved 0
Q fide
Reserved 0
Reserved 0
Reserved 0
Reserved 0
n
Reserved 0
o
Reserved 0
C
Reserved 0
Reserved 0
Reserved 0
Reserved 0
SOS 3 SOS SOS
Mode 1 0–2
Digital Input ID 1 0|1
SOS Number <=20
Output ID 1 0-1
Output Status 1 0|1
Reserved 0
Reserved 0
Reserved 0
Reserved 0
Reserved 0
Reserved 0
PIN 3 PIN PIN
Enable Auto-unlock PIN 1 0|1
k
PIN 1 '0' – '9'
n
SIM PIN Lock 1 0|1
l i l
Reserved 0
c a
Reserved 0
e t i
Reserved 0
u n
Reserved 0
Q fide
OWH 3 OWH OWH
Mode 1 0–1
Day of Work <=2 0 – 7F
Working Hours Start1 4 HHMM
n
Working Hours End1 4 HHMM
o
Working Hours Start2 4 HHMM
C
Working Hours End2 4 HHMM
Reserved 0
Reserved 0
Reserved 0
Digital Output ID 1 0-1
Output Status 1 0|1
Reserved 0
Reserved 0
Reserved 0
Reserved 0
Reserved 0
Reserved 0
DOG 3 DOG DOG
Mode 1 0–2
Ignition Frequency <=3 10 – 120min
Interval <=2 1 – 30
Time 4 HHMM
Reserved 0
k
Report Before Reboot 1 0|1
n
Input ID 1 0|1
l i l
Reserved 0
c a
GSM Interval 4 0|5-1440 min 60
e t i
PDP Interval 4 0|5-1440 min 60
u n
Reserved 0
Q fide
IDL 3 IDL IDL
Mode 1 0|1
Time to Stationary 1 1 – 5 min
Time to Movement 1 1 – 5 min
n
Reserved 0
o
Reserved 0
C
Reserved 0
Reserved 0
Output ID 1 0-1
Output Status 1 0|1
Reserved 0
Reserved 0
Reserved 0
Reserved 0
Reserved 0
Reserved 0
HMC 3 HMC HMC
Ignition Time Counter

1 0|1
Enable
Initial Ignition Time

11 00000:00:00-99999:00:00
Count
Reserved 0
Reserved 0
Reserved 0
Reserved 0
k
Reserved 0
i n
Reserved 0
l l
Reserved 0
c ia
Reserved 0
e t
HBM 3 HBM HBM
u n
HBM Enable 1 0|1
Q fide
Reserved 0
Reserved 0
High Speed <=3 100 – 400km/h
∆Vhb
n
<=3 0 – 100km/h
∆Vha <=3 0 – 100km/h
o
Reserved 0
C
Medium Speed <=3 100 – 400km/h
∆Vmb <=3 0 – 100km/h
∆Vma <=3 0 – 100km/h
Reserved 0
Reserved 0
∆Vlb <=3 0 – 100km/h
∆Vla <=3 0 – 100km/h
Reserved 0
Output ID 1 0-1
Output Status 1 0|1
Reserved 0
Reserved 0
Reserved 0
Reserved 0
Reserved 0
Reserved 0
HRM 3 HRM HRM
Reserved 0
k
Reserved 0
n
ACK Mask 1 '0' – '9' 'a' – 'f' 'A' – 'F' 7F
l i l
Response Mask 4 '0' – '9' 'a' – 'f' 'A' – 'F' FE5FFF
c a
Event Mask 4 '0' – '9' 'a' – 'f' 'A' – 'F' FE5FFF
e t i
Information Mask 2 '0' – '9' 'a' – 'f' 'A' – 'F' FF7F
u n
HBD Mask 1 '0' – '9' 'a' – 'f' 'A' – 'F' FF
Q fide
Reserved 0
Reserved 0
Reserved 0
Reserved 0
n
SSR 3 SSR SSR
o
Mode 1 0|1 0
C
Time to Stop 2 1 – 30 min 2
Time to Start 1 1 – 5 min 1
Start Speed 2 1 – 10 Km/h 5
Reserved 0
Reserved 0
Reserved 0
Reserved 0
JDC 3 JDC JDC
Mode 1 0|1 0
Signal Threshold <=3 0 – 255 10
Reserved 0
Jamming Cell Number

<=2 0-99 5
Threshold
Enter Jamming Timer

<=3 0-300 sec 10
Threshold
Quit Jamming Timer

<=4 0-3600sec 10
Threshold
Reserved 0
Output ID 1 0-1
k
Output Status 1 0|1
n
Reserved 0
l i l
Reserved 0
c a
Reserved 0
e t i
NMD 3 NMD NMD
u n
Mode 1 1 0
Q fide
Non-movement Duration <=3 1 – 255 (×15s) 4
Movement Duration <=3 1 – 255 (×100ms) 1
NMD Report Interval 5 0|5 – 86400sec 300
Reserved 0
n
Reserved 0
o
Reserved 0
C
Reserved 0
FFC 3 FFC FFC
Priority 1 0 0
Mode 1 0|1|2 0
Reserved 0
Reserved 0
Reserved 0
Reserved 0
Priority 1 1 1
Mode 1 0|1|2 0
Reserved 0
Reserved 0
Reserved 0
Reserved 0
Priority 1 2 2
Mode 1 0|1|2 0
Reserved 0
Reserved 0
k
Reserved 0
n
Reserved 0
l i l
Priority 1 3 3
c a
Mode 1 0|1|2 0
e t i
Reserved 0
u n
Reserved 0
Q fide
Reserved 0
Reserved 0
Priority 1 4 4
Mode 1 0|1|2 0
n
Reserved 0
o
Reserved 0
C
Reserved 0
Reserved 0
PDS 3 PDS PDS
Mode 1 0|1|2 0
Mask 4 0000-FFFF 0
Reserved 0
Reserved 0
Reserved 0
Reserved 0
Reserved 0
Reserved 0
JBS 3 JBS JBS
Mode 1 0|1 0
Reserved 0
Delay duration(T1) 5 1 – 65535(sec) 60
k
Cut fuel Timer(T2) 5 1 – 65535(sec) 3600
n
Need Judge Motion
i
1 0|1 1
l l
Sensor
c a
Speed Limit 3 0 – 999km/h 30
i
GPS Fix Fail Timer(T3) 5 30-65535(sec) 120
e t
Reserved 0
u n
Reserved 0
Q fide
Reserved 0
Reserved 0
WLT 3 WLT WLT
n
Call Filter 1 0|1|2|3
o
Phone number 1 <=20
Phone number 2 <=20
C
Phone number 3 <=20
Phone number 4 <=20
Phone number 5 <=20
Phone number 6 <=20
Phone number 7 <=20
Phone number 8 <=20
Phone number 9 <=20
Phone number 10 <=20
Reserved 0
Reserved 0
Reserved 0
Reserved 0
3.3.3.3. +RESP:GTCID
After the device receives the command AT+GTRTO to read the ICCID of the SIM card, it will
send the ICCID to the backend server by the message +RESP:GTCID.
 +RESP:GTCID,
Example:
+RESP:GTCID,240100,135790246811220,,898600810906F8048812,20090214093254,11F0$
k
i n
XX0000 – XXFFFF,
l l
Protocol Version 6
X∈{'A' – 'Z','0' – '9'}
c a
Unique ID 15 IMEI
e t i
Device Name <=20 '0' – '9' 'a' – 'z' 'A' – 'Z' '-' '_'
u n
ICCID 20
Q fide
o n
3.3.3.4. +RESP:GTCSQ
After the device receives the command AT+GTRTO to read the GSM signal level, it will send
C
the GSM signal level to the backend server by the message +RESP:GTCSQ.
 +RESP:GTCSQ,
Example:
+RESP:GTCSQ,240100,135790246811220,,16,0,20090214093254,11F0$
XX0000 – XXFFFF,
Protocol Version 6
X∈{'A' – 'Z','0' – '9'}
Unique ID 15 IMEI
Device Name <=20 '0' – '9' 'a' – 'z' 'A' – 'Z' '-' '_'
CSQ RSSI <=2 0 – 31|99
CSQ BER <=2 0 – 7|99
 <CSQ RSSI>: The signal strength level.

CSQ RSSI Signal Strength (dBm)
0 <-133
1 -111
2 – 30 -109 – -53
31 >-51
k
99 Unknown
 <CSQ BER>: The quality of the GSM signal. The range is 0-7, 99 for unknown.
cl i n
3.3.3.5. +RESP:GTVER
a l
e t i
After the device receives the command AT+GTRTO to get the versions (including software
version and hardware version), it will send the version information to the backend server by the
u n
message +RESP:GTVER.
 +RESP:GTVER,
Q fide
Example:
+RESP:GTVER,240100,135790246811220,,GMT200,0100,0101,20090214093254,11F0$
n
XX0000 – XXFFFF,
Protocol Version 6
X∈{'A' – 'Z','0' – '9'}
o
Unique ID 15 IMEI
C
Device Name <=20 '0' – '9' 'a' – 'z' 'A' – 'Z' '-' '_'
Device Type 10 '0' – '9' 'a' – 'z' 'A' – 'Z'
Software Version 4 0000 – FFFF
Hardware Version 4 0000 – FFFF
MCU Version 4 0000-FFFF
 <Device Type>: The type of the device.

 <Software Version>: The software version. The first two characters represent the major
version and the last two characters represent the minor version. For example: 010A means the
version 1.10.
 <Hardware Version>: The hardware version. The first two characters represent the major
version and the last two characters represent the minor version. For example: 010A means the
version 1.10.
 <MCU Version>: The MCU (micro control unit which handles sensor data) version. The first
two characters represent the major version and the last two characters represent the minor
version. For example: 010A means the version 1.10.
3.3.3.6. +RESP:GTBAT
k
After the device receives the command AT+GTRTO to read the power supply information, it
will send the power supply information to the backend server by the message +RESP:GTBAT.
i n
 +RESP:GTBAT,
l l
Example:
c a
+RESP:GTBAT,240100,135790246811220,,1,12000,,4.40,0,0,20090214093254,11F0$
e t i
n
XX0000 – XXFFFF,
u
Protocol Version 6
X∈{'A' – 'Z','0' – '9'}
Q fide
Unique ID 15 IMEI
Device Name <=20 '0' – '9' 'a' – 'z' 'A' – 'Z' '-' '_'
External Power Supply 1 0|1
n
External Power VCC <=5 0 – 32000mV
o
Reserved 0
C
Charging 1 0|1
LED On 1 0|1
3.3.3.7. +RESP:GTIOS
After the device receives the command AT+GTRTO to get all the IO ports status, it will send the
status to the backend server by the message +RESP:GTIOS.
 +RESP:GTIOS,
Example:
+RESP:GTIOS,240100,135790246811220,,, ,,00,00,20090214093254,11F0$
XX0000 – XXFFFF,
Protocol Version 6
X∈{'A' – 'Z','0' – '9'}
Unique ID 15 IMEI
Device Name <=20 '0' – '9' 'a' – 'z' 'A' – 'Z' '-' '_'
Reserved 0
0
Reserved
k
Reserved 0
i n
Digital Input 2 00 – 03
l l
Digital Output 2 00-01
c ia
e t
u n
Q fide
3.3.3.8. +RESP:GTTMZ
After the device receives the command AT+GTRTO to get the time zone settings, it will send
n
the time zone settings by the message +RESP:GTTMZ to the backend server.
 +RESP:GTTMZ,
o
Example:
+RESP:GTTMZ,240100,135790246811220,,+0800,0,20090214093254,11F0$
C
XX0000 – XXFFFF,
Protocol Version 6
X∈{'A' – 'Z','0' – '9'}
Unique ID 15 IMEI
Device Name <=20 '0' – '9' 'a' – 'z' 'A' – 'Z' '-' '_'
Time Zone Offset 5 ±HHMM
3.3.4. Event Report
The following event reports are triggered when certain events occur.
+RESP:GTPNA: Power on report
+RESP:GTPFA: Power off report
+RESP:GTMPN: The report for connecting main power supply
+RESP:GTMPF: The report for disconnecting main power supply
+RESP:GTBTC: Backup battery starts charging report
+RESP:GTSTC: Backup battery stop charging report.
+RESP:GTBPL: Backup battery low
+RESP:GTBPN: Backup battery is connected.
k
+RESP:GTBPF: Backup battery is removed.
+RESP:GTSTT: Device motion state indication when the motion state is changed
n
+RESP:GTPDP: GPRS connection establishment report
l i l
+RESP:GTIGN: ignition on report
+RESP:GTIGF: ignition off report
c ia
+RESP:GTIDN: Enter into idling status
e t
+RESP:GTIDF: Leave idling status
+RESP:GTJDR: Jamming indication
u n
+RESP:GTGSM:The report for the information of the service cell and the neighbor cells
+RESP:GTSTR: Vehicle enters into start status
Q fide
+RESP:GTSTP: Vehicle enters into stop status
+RESP:GTNMD: Device change movement status.
In +RESP:GTMPN, +RESP:GTMPF, +RESP:GTBTC, +RESP:GTSTC, +RESP:GTBPL,
+RESP:GTBPN, +RESP:GTBPF, +RESP:GTSTT, +RESP:GTIGN, +RESP:GTIGF,
n
+RESP:GTIDN, +RESP:GTIDF ， +RESP:GTJDR +RESP:GTSTR and
+RESP:GTSTP,event reports, the last known GPS information and the current GSM network
o
information are involved.
C
 +RESP:GTPNA,
 +RESP:GTPFA,
 +RESP:GTPDP,
Example:
+RESP:GTPNA,240100,135790246811220,,20090214093254,11F0$
+RESP:GTPFA,240100,135790246811220,,20090214093254,11F0$
+RESP:GTPDP,240100,135790246811220,,20090214093254,11F0$
XX0000 – XXFFFF,
Protocol Version 6
X∈{'A' – 'Z','0' – '9'}
Unique ID 15 IMEI
Device Name <=20 '0' – '9' 'a' – 'z' 'A' – 'Z' '-' '_'
 +RESP:GTMPN,
 +RESP:GTMPF,
 +RESP:GTBTC,
 +RESP:GTBPN,
 +RESP:GTBPF,
k
 +RESP:GTJDR,
Example:
i n
+RESP:GTMPN,240100,135790246811220,,0,4.3,92,70.0,121.354335,31.222073,2009021401
l l
3254,0460,0000,18d8,6141,00,20090214093254,11F0$
c
+RESP:GTMPF,240100,135790246811220,,0,4.3,92,70.0,121.354335,31.222073,20090214013
ia
254,0460,0000,18d8,6141,00,20090214093254,11F0$
e t
+RESP:GTBTC,240100,135790246811220,,0,4.3,92,70.0,121.354335,31.222073,20090214013
254,0460,0000,18d8,6141,00,20090214093254,11F0$
u n
+RESP:GTBPN,240100,135790246811220,,0,4.3,92,70.0,121.354335,31.222073,20090214013
Q fide
254,0460,0000,18d8,6141,00,20090214093254,11F0$
+RESP:GTBPF,240100,135790246811220,,0,4.3,92,70.0,121.354335,31.222073,20090214013
254,0460,0000,18d8,6141,00,20090214093254,11F0$
240100
+RESP:GTJDR,240100,135790246811220,,0,4.3,92,70.0,121.354335,31.222073,20090214013
n
254,0460,0000,18d8,6141,00,20090214093254,11F0$
o
XX0000 – XXFFFF,
Protocol Version 6
C
X∈{'A' – 'Z','0' – '9'}
Unique ID 15 IMEI
Device Name <=20 '0' – '9' 'a' – 'z' 'A' – 'Z' '-' '_'
GPS Accuracy <=2 0 0, Last known
Speed <=5 0.0 – 999.9 km /h
Azimuth <=3 0 – 359
MCC 4 0XXX
MNC 4 0XXX
LAC 4 XXXX
Cell ID 4 XXXX
Reserved 2 00 00
i n k
If the <Mode> set as 2 in the AT+GTJDC command, when jamming is detected, the device will
l l
report +RESP:GTJDS message.
 +RESP:GTJDS,
c ia
Example:
e t
+RESP:GTJDS,040408,135790246811220,,2,0,4.3,92,70.0,121.354335,31.222073,2009021401
n
3254,0460,0000,18d8,6141,00,20090214093254,11F0$
u
Q fide
XX0000 – XXFFFF,
Protocol Version 6
X∈{'A' – 'Z','0' – '9'}
Unique ID 15 IMEI
n
Device Name <=20 '0' – '9' 'a' – 'z' 'A' – 'Z' '-' '_' '?'
o
Jamming Status 1 1|2
C
Speed <=5 0.0 – 999.9 km /h
Azimuth <=3 0 – 359
MCC 4 0XXX
MNC 4 0XXX
LAC 4 XXXX
Cell ID 4 XXXX
Reserved 2 00 00
 <Jamming Status>: The current Jamming status of the device.
 1: Quit the jamming.
 2: Enter the jamming.
 +RESP:GTSTC,
k
Example:
n
+RESP:GTSTC,240100,135790246811220,,,0,4.3,92,70.0,121.354335,31.222073,20090214013
i l
254,0460,0000,18d8,6141,00,20090214093254,11F0$
l
c ia
XX0000 – XXFFFF,
e t
Protocol Version 6
X∈{'A' – 'Z','0' – '9'}
u n
Unique ID 15 IMEI
Q fide
Device Name <=20 '0' – '9' 'a' – 'z' 'A' – 'Z' '-' '_'
Reserved 0
Speed <=5 0.0 – 999.9 km /h
n
Azimuth <=3 0 – 359
o
C
MCC 4 0XXX
MNC 4 0XXX
LAC 4 XXXX
Cell ID 4 XXXX
Reserved 2 00 00
 +RESP:GTBPL,
Example:
+RESP:GTBPL,240100,135790246811220,,3.53,0,4.3,92,70.0,121.354335,31.222073,2009021
4013254,0460,0000,18d8,6141,00,20090214093254,11F0$
XX0000 – XXFFFF,
Protocol Version 6
X∈{'A' – 'Z','0' – '9'}
k
Unique ID 15 IMEI
i n
Device Name <=20 '0' – '9' 'a' – 'z' 'A' – 'Z' '-' '_'
l l
c ia
e t
Speed <=5 0.0 – 999.9 km /h
u n
Azimuth <=3 0 – 359
Q fide
n
MCC 4 0XXX
o
MNC 4 0XXX
C
LAC 4 XXXX
Cell ID 4 XXXX
Reserved 2 00 00
 +RESP:GTSTT,
Example:
+RESP:GTSTT,240100,135790246811220,,16,0,4.3,92,70.0,121.354335,31.222073,200902140
13254,0460,0000,18d8,6141,00,20090214093254,11F0$
XX0000 – XXFFFF,
Protocol Version 6
X∈{'A' – 'Z','0' – '9'}
Unique ID 15 IMEI
Device Name <=20 '0' – '9' 'a' – 'z' 'A' – 'Z' '-' '_'
State 2 11|12|21|22|41|42|16
Speed <=5 0.0 – 999.9 km /h
k
Azimuth <=3 0 – 359
l i n l
c a
i
e t
MCC 4 0XXX
u n
MNC 4 0XXX
Q fide
LAC 4 XXXX
Cell ID 4 XXXX
Reserved 2 00 00
n
o
C
 <State>: The current movement state of the device.
 16 (Tow): The device attached vehicle is ignition off and it is towed.
 11 (Ignition Off Rest): The device attached vehicle is ignition off and it is motionless.
 12 (Ignition Off Motion): The device attached vehicle is ignition off and it is moving
before it is treated as being towed.
 21 (Ignition On Rest): The device attached vehicle is ignition on and it is motion less
 22 (Ignition On Motion): The device attached vehicle is ignition on and it is moving
 41 (Sensor Rest): The device attached vehicle is motionless without ignition signal
detected
 42 (Sensor Motion): The device attached vehicle is moving without ignition signal
detected
 +RESP:GTIGN,
Example:
+RESP:GTIGN,240100,135790246811220,,1200,0,4.3,92,70.0,121.354335,31.222073,2009021
4013254,0460,0000,18d8,6141,00,2000.0,12345:12:34,20090214093254,11F0$
XX0000 – XXFFFF,
Protocol Version 6
X∈{'A' – 'Z','0' – '9'}
Unique ID 15 IMEI
Device Name <=20 '0' – '9' 'a' – 'z' 'A' – 'Z' '-' '_'
k
Duration of Ignition Off <=6 0 – 999999 sec
i n
l l
Speed <=5 0.0 – 999.9 km /h
c ia
Azimuth <=3 0 – 359
e t
u n
Q fide
MCC 4 0XXX
n
MNC 4 0XXX
o
LAC 4 XXXX
Cell ID 4 XXXX
C
Reserved 2 00
Mileage <=9 0.0 – 4294967.0 km
Ignition Time Count 11 HHHHH:MM:SS
 <Duration of Ignition Off>: Duration since last time the ignition is off. If greater than 999999
seconds, report as 999999 seconds.
 <Ignition time Count>: If ignition time counter function is enabled by the command
AT+GTHMC, total ignition time counted when engine is on will be reported in this field. If
the function is disabled, this field will be reserved. It is formatted with 5 hour digits and 2
minute digits and 2 second digits and ranges from 00000:00:00– 99999:00:00.
 +RESP:GTIGF,
Example:
+RESP:GTIGF,240100,135790246811220,,1200,0,4.3,92,70.0,121.354335,31.222073,2009021
4013254,0460,0000,18d8,6141,00,2000.0,12345:12:34,20090214093254,11F0$
XX0000 – XXFFFF,
Protocol Version 6
X∈{'A' – 'Z','0' – '9'}
Unique ID 15 IMEI
k
Device Name <=20 '0' – '9' 'a' – 'z' 'A' – 'Z' '-' '_'
n
Duration of Ignition On <=6 0 – 999999 sec
l i l
c ia
Speed <=5 0.0 – 999.9 km /h
e t
Azimuth <=3 0 – 359
u n
Q fide
MCC 4 0XXX
n
MNC 4 0XXX
o
LAC 4 XXXX
C
Cell ID 4 XXXX
Reserved 2 00
Mileage <=9 0.0 – 4294967.0 km
Ignition Time Count 2|11 00|HHHHH:MM:SS
 <Duration of Ignition On>: Duration since last time the ignition is on. If greater than 999999
seconds, report as 999999 seconds.
 +RESP:GTIDN,
Example:
+RESP:GTIDN,240100,135790246811220,,,,0,4.3,92,70.0,121.354335,31.222073,2009021401
3254,0460,0000,18d8,6141,00,2000.0,20090214093254,11F0$
XX0000 – XXFFFF,
Protocol Version 6
X∈{'A' – 'Z','0' – '9'}
Unique ID 15 IMEI
Device Name <=20 '0' – '9' 'a' – 'z' 'A' – 'Z' '-' '_'
Reserved 0
k
Reserved 0
n
l i l
Speed <=5 0.0 – 999.9 km /h
c a
Azimuth <=3 0 – 359
e t i
u n
Q fide
MCC 4 0XXX
MNC 4 0XXX
n
LAC 4 XXXX
o
Cell ID 4 XXXX
C
Reserved 2 00 00
Mileage <=9 0.0 – 4294967.0 km
 +RESP:GTIDF,
Example:
+RESP:GTIDF,240100,135790246811220,,22,300,0,4.3,92,70.0,121.354335,31.222073,200902
14013254,0460,0000,18d8,6141,00,2000.0,20090214093254,11F0$
TRACGMT200AN003 – 100 –
XX0000 – XXFFFF,
Protocol Version 6
X∈{'A' – 'Z','0' – '9'}
Unique ID 15 IMEI
Device Name <=20 '0' – '9' 'a' – 'z' 'A' – 'Z' '-' '_'
Motion State 2 11|12|16|22
Duration of Idling Status <=6 0 – 999999 sec
Speed <=5 0.0 – 999.9 km /h
k
Azimuth <=3 0 – 359
l i n l
c a
i
e t
MCC 4 0XXX
u n
MNC 4 0XXX
Q fide
LAC 4 XXXX
Cell ID 4 XXXX
Reserved 2 00 00
n
Mileage <=9 0.0 – 4294967.0 km
o
C
 <Motion State>: The current motion state when the vehicle leaves idling status.
 <Duration of Idling Status>: The time that the vehicle has been in idling status. If greater
than 999999 seconds, report as 999999 seconds.
+RESP:GTGSM
Example:
+RESP:GTGSM,240100,135790246811220,FRI,0460,0000,1878,0871,20,,0460,0000,1878,015
2,16,,,,,,,,,,,,,,,,,,,,,,,,,,0460,0000,1878,0873,57,00,20090214093254,11F0$

Protocol Version 6 XX0000 – XXFFFF,
X∈{'A'-'Z','0'-'9'}
TRACGMT200AN003 – 101 –
Unique ID 15 IMEI
Fix Type 3 SOS|RTL|LBC|TOW|FRI|GI

R
MCC1 4 0XXX
MNC1 4 0XXX
LAC1 4
Cell ID1 4
RX Level1 2 0-63
Reserved 0
k
MCC2 4 0XXX
i n
MNC2 4 0XXX
l l
LAC2 4
c ia
Cell ID2 4
e t
RX Level2 2 0-63
u n
Reserved 0
Q fide
MCC3 4 0XXX
MNC3 4 0XXX
LAC3 4
Cell ID3 4
n
RX Level3 2 0-63
o
Reserved 0
C
MCC4 4 0XXX
MNC4 4 0XXX
LAC4 4
Cell ID4 4
RX Level4 2 0-63
Reserved 0
MCC5 4 0XXX
MNC5 4 0XXX
LAC5 4
Cell ID5 4
TRACGMT200AN003 – 102 –
RX Level5 2 0-63
Reserved 0
MCC6 4 0XXX
MNC6 4 0XXX
LAC6 4
Cell ID6 4
RX Level6 2 0-63
Reserved 0
k
MCC 4 0XXX
n
MNC 4 0XXX
l i l
LAC 4
c a
Cell ID 4
e t i
RX Level 2 0-63
n
Reserved 2 00
u
Q fide
n
 <Fix Type> : A string to indicate what kind of GPS fixing this cell information is for.
"SOS" This cell information is for SOS requirement.
o
"RTL" This cell information is for RTL requirement.
"LBC" This cell information is for LBC requirement.
C
"TOW" This cell information is for TOW requirement.
"FRI" This cell information is for FRI requirement.
"GIR" This cell information is for sub command “C” in AT+GTRTO command.
 <MCC(i)> : MCC of the neighbor cell i (i is the index of the neighbor cell).
 <MNC(i)> : MNC of the neighbor cell i.
 <LAC(i)> : LAC in hex format of the neighbor cell i.
 <Cell ID(i)> : Cell ID in hex format of the neighbor cell i.
 <RX Level(i)> : The signal strength of the neighbor cell i. This parameter is a 6-bit coded in 1
dB steps:
0: -110 dBm
1 to 62: -109 to -48 dBm
63: -47 dBm
 <MCC>: MCC of the service cell.
 <MNC>: MNC of the service cell.
 <LAC>: LAC in hex format of the service cell.
TRACGMT200AN003 – 103 –
 <Cell ID>: Cell ID in hex format of the service cell.
 <RX Level>: The signal strength of the service cell.
Note:
1. It probably includes only several neighbor cells’ (even no neighbor cell) information. If some
neighbor cell wasn’t find, all the fields of the neighbor cell will be empty.
2. "ffff" in the field of <LAC(i)>, <Cell ID(i)> means the terminal doesn’t know the value.
3. This message cannot be sent via SMS.
 +RESP:GTSTP,
 +RESP:GTSTR,
k
Example:
+RESP:GTSTR,060100,135790246811220,,,,0,4.3,92,70.0,121.354335,31.222073,2009021401
i n
3254,0460,0000,18d8,6141,00,2000.0,20090214093254,11F0$
l l
+RESP:GTSTP,060100,135790246811220,,,,0,4.3,92,70.0,121.354335,31.222073,2009021401
c a
3254,0460,0000,18d8,6141,00,2000.0,20090214093254,11F0$
t i
e
XX0000 – XXFFFF,
u n
Protocol Version 6
X∈{'A' – 'Z','0' – '9'}
Q fide
Unique ID 15 IMEI
Device Name <=20 '0' – '9' 'a' – 'z' 'A' – 'Z' '-' '_'
Reserved 0
n
Reserved 0
o
Speed <=5 0.0 – 999.9 km /h
C
Heading <=3 0 – 359
MCC 4 0XXX
MNC 4 0XXX
LAC 4 XXXX
Cell ID 4 XXXX
Reserved 2 00 00
TRACGMT200AN003 – 104 –
Mileage <=9 0.0 – 4294967.0 km
 +RESP:GTNMD,
Example:
+RESP:GTNMD,240100,135790246811220,,16,0,4.3,92,70.0,121.354335,31.222073,20090214
013254,0460,0000,18d8,6141,00,20090214093254,11F0$
k
n
XX0000 – XXFFFF,
Protocol Version 6
i
X∈{'A' – 'Z','0' – '9'}
l l
Unique ID 15 IMEI
c ia
Device Name <=20 '0' – '9' 'a' – 'z' 'A' – 'Z' '-' '_'
e t
NMD status 2 0|1
u n
Q fide
Speed <=5 0.0 – 999.9 km /h
Azimuth <=3 0 – 359
n
o
C
MCC 4 0XXX
MNC 4 0XXX
LAC 4 XXXX
Cell ID 4 XXXX
Reserved 2 00 00
 < NMD status >: The current movement state of the device.
 0: The device is detected to be at movement status or exit the NMD status.
 1: The device is detected to enter the NMD status and be at non-movement status.
TRACGMT200AN003 – 105 –
3.3.5. Buffer Report
If the buffer report function is enabled by command AT+GTSRI, the terminal will save the report
messages in a local buffer when the following occurs.
 GSM network is not available
 Failed to activate GPRS context for the TCP or UDP connection.
 Failed to establish the TCP connection with the backend server.
These messages will be sent to the backend server when connection to the server recovers again.
The buffer reports are saved to the built-in non-volatile memory in case the device is reset. The
terminal can buffer up to 3000 messages (160 bytes per message).
k
Detailed information about buffer report is listed below.
 Only +RESP messages are buffered except that +RESP:GTALL is not buffered
n
 In the buffer report, the original header string “+RESP” is replaced by “+BUFF” while keeps
l i l
the other content untouched including the original sending time and count number.
 Buffered messages will be sent only via GPRS by TCP or UDP protocol. They cannot be sent
c ia
via SMS. If the current report mode is forcing on SMS, the buffered messages will not be
e t
sent until the report mode is changed to TCP or UDP.
 The buffered messages will be sent after the other normal messages sending if <Buffer
u n
Mode> in AT+GTSRI is set to 1.
 The buffered messages will be sent before the other normal messages sending if <Buffer
Q fide
Mode> in AT+GTSRI is set to 2. The SOS message has the highest priority and is sent
before the buffered messages.
Example:
n
The following is an example of the buffered message:
+BUFF:GTFRI,020100,135790246811220,,0,0,1,1,4.3,92,70.0,121.354335,31.222073,200902140
o
13254,0460,0000,18d8,6141,00,,20090214093254,11F0$
C
TRACGMT200AN003 – 106 –
3.3.6. Report Google Maps hyperlink
According to the setting of the command AT+GTSOS and the configuration of location by call,
the device can send a SMS with Google Maps hyperlink to a mobile phone.
If the <Mode> was set to 2 in the command AT+GTSOS, the terminal will send a SMS with
Google Maps hyperlink to the direct phone numbers.
If <Location By Call> is set to 2, the terminal will send its current position to the incoming call via
SMS with Google Maps hyperlink.
k
 Google Maps hyperlink
Example:
n
GMT200 SOS:
l i l
<http://maps.google.com/maps?q=31.222073,121.354335 F1 D2009/01/01T00:00:00>
GMT200 LBC:
e c t ia
<http://maps.google.com/maps?q=31.222073,121.354335 F1 D2009/01/01T00:00:00>
u n
'0' – '9' 'a' – 'z' 'A' – 'Z'
Device Name <=20
'-' '_'
Q fide
Report Type 3 SOS|LBC
Google Maps Hyperlink http://maps.google.com http://maps.google.co
30
Header /maps?q= m/maps?q=
n
GPS Fix <=3 F0|F1 – F50
o
DYYYY/MM/DDTHH
GPS UTC Time 20
:MM:SS
C
 <Report Type>: A string that includes GPS fix type ("SOS", "LBC").
 <Google Maps hyperlink>: A string of a google map hyperlink.
 <GPS Fix>: The accuracy of the location information. F0 means no GPS fix. When outside of
working hours, the default value of GPS Fix is F0.
TRACGMT200AN003 – 107 –
3.4. Heartbeat
Heartbeat is used to maintain the contact between the device and the backend server if
communicating via GPRS. The heartbeat package is sent to the backend server at the interval
defined by <Heartbeat interval> in AT+GTSRI command.
 +ACK:GTHBD
Example:
+ACK:GTHBD,240100,135790246811220,,20100214093254,11F0$
k
Protocol version XX0000 – XXFFFF,
6
n
X∈{'A' – 'Z','0' – '9'}
l i l
Unique ID 15 IMEI
c a
'0' – '9' 'a' – 'z' 'A' – 'Z' '-'
i
Device Name <=20
'_'
e t
u n
Q fide
Whenever the backend server receives a heartbeat package, it should reply an acknowledgement to
the device.
n
 +SACK:GTHBD
Example:
o
+SACK:GTHBD,240100,11F0$
+SACK:GTHBD,,11F0$
C
Protocol version XX0000 – XXFFFF,

6
X∈{'A' – 'Z','0' – '9'}
 <Protocol Version>: The device type and the protocol version that the backend server
supported. This field is optional. The backend server could just send an empty field to
decrease the length of the heartbeat data acknowledgement.
 <Count Number>: The backend server uses the <Count Number> extracted from the
heartbeat package from the device as the <Count Number> in the server acknowledgement of
the heartbeat.
TRACGMT200AN003 – 108 –
3.5. Server Acknowledgement
If server acknowledgement is enabled by AT+GTSRI command, the backend server should reply
to the device whenever it receives a message from the device.
 +SACK:
Example:
+SACK:11F0$
k
i n
 <Count Number>: The backend server uses the <Count Number> extracted from the received
l l
message as the <Count Number> in the server acknowledgement.
e c t ia
u
Q fide n
o n
C
TRACGMT200AN003 – 109 –
4. HEX Format Report Message
From this version, the @Tracker protocol starts to support report messages in HEX format. For all
the commands, they are still using the ASCII format as described above. By default the device
using ASCII format report messages. The backend server could use AT+GTQSS or AT+GTSRI
command to enable the HEX format report messages by setting the <Protocol Format> to 1.
All the report messages are sorted into 5 categories and messages in the same category use the
same header string, including acknowledgement to command (+ACK), location report (+RSP),
event report (+EVT), information report (+INF) and the heartbeat data (+HBD).
k
The composition of the HEX report message could be customized by AT+GTHRM command.
n
The actual length of each HEX report message varies depending on set some mask in
l i l
AT+GTHRM .
c ia
The device uses CRC16 method to calculate the checksum of the report data and appends the
e t
checksum to the end of the data. The backend server could use this checksum to verify the
integrity of the received data.
u n
At the end of each HEX report message, the device uses 0x0D and 0x0A to mark the end.
Q fide
The HEX report messages are transmitted in network byte order (big-endian).
o n
C
TRACGMT200AN003 – 110 –
4.1. Hex Report Mask
AT+GTHRM command consists of <+ACK Mask>, <+RSP Mask>, <+EVT Mask>, <+INF
Mask> and <+HBD Mask> to control the composition of the corresponding HEX report message.
In each HEX report message, the corresponding mask for the report is involved to indicate which
part is reported.
 AT+GTHRM=
Example:
k
AT+GTHRM=gmt200,,,FF,FFFFFFFF,FFFFFFFF,FFFF,FF,,,,,0018$
n
l i l
c a
Reserved 0
e t i
Reserved 0
n
+ACK Mask 1 00 – FF 7F
u
+RSP Mask 4 00000000 – FFFFFFFF FE1FFF
Q fide
+EVT Mask 4 00000000 – FFFFFFFF FE1FFF
+INF Mask 2 0000 – FFFF FF7F
+HBD Mask 1 00 – FF FF
n
Reserved 0
o
Reserved 0
Reserved 0
C
Reserved 0
 <+ACK Mask>: Component mask of the acknowledgement received.
Bit Item to Mask
Bit 7 Reserved
Bit 6 <Count Number>
Bit 5 <Send Time>
TRACGMT200AN003 – 111 –
Bit 4 <Device Name>
Bit 3 <Firmware Version>
Bit 2 <Protocol Version>
Bit 1 <Device Type>
Bit 0 <Length>
 <+RSP Mask>: Component mask of the location report message.
Bit Item to Mask
k
Bit 31 Reserved
n
Bit 30 Reserved
l i l
Bit 29 Reserved
c a
Bit 28 Reserved
e t i
Bit 27 Reserved
u n
Bit 26 Reserved
Q fide
Bit 25 Reserved
Bit 24 Reserved
Bit 23 <Total Hour Meter Count>
Bit 22 <Current Hour Meter Count>
n
Bit 21 <Total Mileage>
o
Bit 20 <Current Mileage>
C
Bit 19 <GPS Antenna And Satellites Information>
Bit 18 <Motion Status>
Bit 17 <Digital IO Status>
Bit 16 Reserved
Bit 15 Reserved
Bit 14 Reserved
Bit 13 Reserved
Bit 12 <External Power Supply Voltage>
Bit 11 <Battery Level>
TRACGMT200AN003 – 112 –
Bit 8 <Device Type>
Bit 7 <Length>
Bit 6 <Device Name>
Bit 4 <Send Time>
Bit 3 <MCC/MNC/LAC/Cell ID/Reserved>
Bit 2 <Altitude>
k
Bit 1 <Azimuth>
n
Bit 0 <Speed>
l i l
 <+EVT Mask>: Component mask of the event report message.
e c t ia
Bit Item to Mask
u n
Bit 31 Reserved
Q fide
Bit 30 Reserved
Bit 29 Reserved
Bit 28 Reserved
Bit 27 Reserved
n
Bit 26 Reserved
o
Bit 25 Reserved
C
Bit 24 Reserved
Bit 23 <Total Hour Meter Count>
Bit 22 <Current Hour Meter Count>
Bit 21 <Total Mileage>
Bit 20 <Current Mileage>
Bit 19 <GPS Antenna And Satellites Information>
Bit 18 <Motion Status>
Bit 17 <Digital IO Status>
Bit 16 Reserved
Bit 15 Reserved
TRACGMT200AN003 – 113 –
Bit 14 Reserved
Bit 13 Reserved
Bit 12 <External Power Supply Voltage>
Bit 11 <Battery Level>
Bit 8 <Device Type>
Bit 7 <Length>
k
Bit 6 <Device Name>
n
l i l
Bit 4 <Send Time>
c a
Bit 3 <MCC/MNC/LAC/Cell ID/Reserved>
e t i
Bit 2 <Altitude>
u n
Bit 1 <Azimuth>
Q fide
Bit 0 <Speed>
 <+INF Mask>: Component mask of the information report message. Bit 8 to Bit 15 indicate
which group of items is included when reporting message other than +RESP:GTINF.
n
Bit Item to Mask
o
Bit 15 +RESP:GTGIR
Bit 14 +RESP:GTTMZ
C
Bit 13 +RESP:GTCSQ
Bit 12 +RESP:GTCID
Bit 11 +RESP:GTBAT
Bit 10 +RESP:GTGPS
Bit 9 +RESP:GTIOS
Bit 8 +RESP:GTVER
Bit 7 Reserved
Bit 5 <Send Time>
TRACGMT200AN003 – 114 –
Bit 2 <Device Type>
Bit 1 <Device Name>
Bit 0 <Length>
 <+HBD Mask>: Component mask of the heartbeat data..
Bit Item to Mask
Bit 7 <UID>
k
n
Bit 5 <Send Time>
l i l
Bit 4 <Device Name>
c a
e t i
u n
Bit 1 <Device Type>
Q fide
Bit 0 <Length>
The acknowledgment message of AT+GTHRM command:

 +ACK:GTHRM,
Example:
n
+ACK:GTHRM, 240100,135790246811220,,0019,20090214093254,11F0$
o
C
XX0000 – XXFFFF,
Protocol Version 6
X∈{'A' – 'Z','0' – '9'}
Unique ID 15 IMEI
Device Name <=20 '0' – '9' 'a' – 'z' 'A' – 'Z' '-' '_'
TRACGMT200AN003 – 115 –
4.2. Acknowledgement +ACK
 +ACK,
Example:
2B 41 43 4B 01 7F 24 24 01 03 05 01 67 6D 74 31 30 30 00 00 00 00 09 07 DC 0C 06 07 28 15
00 16 F0 15 0D 0A
Message Header 4 +ACK +ACK
Message Type 1
k
Report Mask 1 00 – FF
n
Length 1
l i l
Device Type 1 24 24
c a
Protocol Version 2 0000 – FFFF
e t i
Firmware Version 2 0000 – FFFF
Unique ID 8 IMEI/Device Name
u n
ID 1
Q fide
n
Checksum 2 0000 – FFFF
o
Tail Characters 2 0x0D 0x0A 0x0D 0x0A
 <Message Type>: The ID of the command that the device received.
C
Command ID
AT+GTBSI 0
AT+GTSRI 1
AT+GTQSS 2
Reserved 3
AT+GTCFG 4
AT+GTTOW 5
AT+GTEPS 6
AT+GTDIS 7
AT+GTOUT 8
TRACGMT200AN003 – 116 –
AT+GTIOB 9
AT+GTTMA 10
AT+GTFRI 11
AT+GTGEO 12
AT+GTSPD 13
AT+GTSOS 14
Reserved 15
AT+GTRTO 16
k
Reserved 17
n
Reserved 18
l i l
Reserved 19
c a
Reserved 20
e t i
AT+GTUPD 21
u n
AT+GTPIN 22
Q fide
Reserved 23
AT+GTOWH 24
AT+GTDOG 25
n
26
Reserved
o
AT+GTJDC 27
AT+GTIDL 28
C
AT+GTHBM 29
AT+GTHMC 30
AT+GTHRM 31
AT+GTSSR 33
AT+GTNMD 34
AT+GTFFC 35
AT+GTPDS 36
AT+GTJBS 37
AT+GTWLT 38
TRACGMT200AN003 – 117 –
 <Report Mask>: It refer to the <+ACK Mask> in AT+GTHRM.
 <Length>: The whole length of the acknowledgement message header to the tail characters.
 <Unique ID>: If the Bit 4 of <+ACK Mask> is 0, IMEI of the device as the unique ID of the
device. IMEI is a 15-digit string. In the HEX format message, each 2 digits are encoded into
one byte as an integer.
IMEI 13 57 90 24 68 11 22 0
HEX 0D 39 5A 18 44 0B 16 00
If the Bit 4 of <+ACK Mask> is 1, use the device name as the unique ID of the device. The
device name refer to the <Device Name> in AT+GTCFG. Device name is 8-bytes string, if
the length of the <Device Name> is more than 8 bytes, it will only acquire the first 8 bytes. In
k
the Hex format message, each byte is encoded into one byte as an integer. If the device name
is less than 8 bytes, the rest of bytes set as 0.
n
Device Name g
i
m t 2 0 0
l l
HEX 67 6D 74 32 30 30 00 00
c ia
 <ID>: Sub-command ID of AT+GTRTO or the ID of AT+GTIOB and AT+GTGEO, for
e t
others, set to 0.
 <Send Time>: The local time to send the acknowledgement message. Total 7 bytes. The first 2
u n
bytes are for year, the rest 5 bytes for month, day, hour, minute and second respectively.
Q fide
Send Time 2012 01 31 06 29 11
HEX 07 DC 01 1F 06 1D 0B
 <Checksum>: The CRC16 checksum for data from <Message Type> to <Count Number>.
o n
C
TRACGMT200AN003 – 118 –
4.3. Location Report +RSP
Location report messages including +RESP:GTTOW, +RESP:GTDIS, +RESP:GTIOB,

+RESP:GTFRI, +RESP:GTGEO, +RESP:GTSPD, +RESP:GTRTL, +RESP:GTDOG ,
+RESP:GTIGL, +RESP:GTHBM and +RESP:GTEPS use this format.
 +RSP,
Example:
2B 52 53 50 0B 00 FE 5F FF 00 61 24 01 03 05 01 67 6D 74 31 30 30 31 36 61 2E BB 00 00 00
00 42 07 00 01 04 00 01 01 00 00 FF FC 07 3C 48 19 01 DB 88 D1 07 DC 0C 06 09 1B 23 04 60
00 01 10 59 6C 8A 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 07 DC 0C 06 11 1B 24
k
00 43 95 1C 0D 0A
n
Length(byt
i
l
e)
l
Message Header 4 +RSP +RSP
c ia
Message Type 1
e t
Report Mask 4 00000000 – FFFFFFFF
u n
Length 2
Q fide
Device Type 1 24 24
n
o
Battery Level 1 0~100
External Power Supply

2
C
Voltage
2 0000 0000
Reserved
Digital Input Status 1 00 – 1F
Digital Output Status 1 00 – 1F
0x11 | 0x12
0x21 | 0x22
Motion Status 1
0x41 | 0x42
0x16
Satellites in View 1
Report ID / Report Type 1
TRACGMT200AN003 – 119 –
Number 1 1 – 15
GPS Accuracy 1 0|1 – 50
Speed 3 0.0 – 999.9km/h
Azimuth 2 0 – 359
Altitude 2
Longitude 4
Latitude 4
k
MCC 2 0000 – FFFF
n
MNC 2 0000 – FFFF
l i l
LAC 2 0000 – FFFF
c a
Cell ID 2 0000 – FFFF
e t i
Reserved 1 00 00
u n
Current Mileage 3 0.0 – 65535.0 km
Q fide
Total Mileage 5 0.0 – 4294967.0 km
Current Hour Meter Count 3 HHMMSS
Total Hour Meter Count 6 HHHHHHHHMMSS
n
o
C
 <Message Type>: The ID of location report message.
Command ID
Reserved 0
+RESP:GTTOW 1
Reserved 2
+RESP:GTLBC 3
+RESP:GTEPS 4
+RESP:GTDIS 5
+RESP:GTIOB 6
+RESP:GTFRI 7
TRACGMT200AN003 – 120 –
+RESP:GTGEO 8
+RESP:GTSPD 9
+RESP:GTSOS 10
+RESP:GTRTL 11
+RESP:GTDOG 12
Reserved 13
14
Reserved
k
+RESP:GTHBM 15
+RESP:GTIGL 16
l i n l
 <Report Mask>: It refer to the <+RSP Mask> in AT+GTHRM.
c a
 <Unique ID>: If the Bit 6 of <+RSP Mask> is 0, IMEI of the device as the unique ID of the
i
e t
u n
IMEI 13 57 90 24 68 11 22 0
HEX 0D 39 5A 18 44 0B 16 00
Q fide
If the Bit 6 of <+RSP Mask> is 1, use the device name as the unique ID of the device. The
n
o
Device Name g m t 2 0 0
C
HEX 67 6D 74 32 30 30 00 00
 <Digital Input Status>: The mask of digital input1 and digital input2 status consist of the
byte.
Input status mask ID
Ignition Detection 0x01
Digital Input1 0x02
 <Digital Output Status>: The mask of digital output1 and relay output status consist of the
byte.
Output status mask ID
Digital Output1 0x01
TRACGMT200AN003 – 121 –
0x02
Reserved
 < Satellites>: The byte is for <Satellites>.

 <Report ID / Report Type>: The high nibble is for <Report ID> and the low nibble is for
<Report Type>
 <Speed>: Total 3 bytes. The first 2 two bytes are for the integer part of the speed and the last
byte is for the fraction part. The fraction part only has 1 digit.
 <Longitude>: The longitude of the current position. Total 4 bytes. Convert the longitude to an
integer with 6 implicit decimals and report this integer in HEX format. If the value of the
longitude is negative, it is represented in 2’s complement format.
k
Longitude 121390847
121.390847
i n
HEX 07 3C 46 FF
cl a l
 <Latitude>: The latitude of the current position. Total 4 bytes. Convert the latitude to an
i
integer with 6 implicit decimals and report this integer in HEX format. If the value of the
e t
latitude is negative, it is represented in 2’s complement format.
u n
Latitude 31164503
31.164503
Q fide
HEX 01 DB 88 57
 <GPS UTC Time>: The UTC time from the GPS chip. Total 7 bytes. The first 2 bytes are for
year, the rest 5 bytes for month, day, hour, minute and second respectively.
n
GPS UTC Time 2012 07 14 08 24 13
HEX 07 DC 07 0E 08 18 0D
o
 <Current Mileage>: Total 3 bytes. The first 2 bytes are for the integer part of the current
C
mileage and the last byte is for the fraction part. The fraction part only has 1 digit.
Current Mileage 0 0
HEX 00 00 00
 <Total Mileage>: Total 5 bytes. The first 4 bytes are for the integer part of the total mileage
and the last byte is for the fraction part. The fraction part only has 1 digit.
Total Mileage 0 0
HEX 00 00 00 00 00
 <Total Hour Meter Count>: Total 6 bytes. The first 4 bytes are the hour part, The fifth byte is
the minute part. The sixth byte is the second part.
Total Hour Meter Count 0 0 0
HEX 00 00 00 00 00 00
TRACGMT200AN003 – 122 –
Location report message for +RESP:GTLBC use below format

Example:
2B 52 53 50 03 00 FE 5F FF 00 68 24 01 03 05 01 67 6D 74 31 30 30 31 36 5E 2F 55 00 00 00 00
41 0C 00 70 13 91 69 70 97 9F 01 01 00 00 01 00 00 00 18 07 3C 47 28 01 DB 88 E5 07 DC 0C
08 06 1B 12 04 60 00 01 10 59 81 6B 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 07
DC 0C 08 0E 1B 12 00 24 02 BD 0D 0A
Length(byt
e)
k
Message Type 1
n
l i l
Length 2
c a
Device Type 1 24 24
e t i
u n
Q fide

2
Voltage
n
2 0000 0000
Reserved
o
C
0x11 | 0x12
0x21 | 0x22
Motion Status 1
0x41 | 0x42
0x16
Number Length /
1
Number Type
Phone Number <=10
Number 1 1 – 15
TRACGMT200AN003 – 123 –
Speed 3 0.0 – 999.9km/h
Azimuth 2 0 – 359
Altitude 2
Longitude 4
Latitude 4
MCC 2 0000 – FFFF
k
MNC 2 0000 – FFFF
n
LAC 2 0000 – FFFF
l i l
c a
Reserved 1 00 00
e t i
Current Mileage 3 0.0 –65535.0 km
u n
Q fide
n
o
 <Number Length / Number Type>: The high nibble is for <Number Length> and the low
C
nibble is for <Number Type>. <Number Length> is the number of byte used to represent the
phone number including this byte. <Number Type> indicates if there is a ‘+’ sign before the
phone number. 1 means has the sign, 0 means no sign.
Number Length Number Type
HEX 7 0
 <Phone Number>: Not more than 10 bytes. In each byte, use the high nibble and low nibble
to represent one digit of the phone number respectively. If the last low nibble has no digit to
represent, fill in 0xF.
Phone Number
02 15 44 50 29 3
02154450293
HEX 02 15 44 50 29 3F
Location report message for +RESP:GTSOS use below format
TRACGMT200AN003 – 124 –
Example:
2B 52 53 50 0A 00 FE 5F FF 00 62 24 01 03 05 01 67 6D 74 31 30 30 31 36 5E 2F 6B 00 00 02
00 11 0C 10 00 01 01 00 00 03 00 66 00 1D 07 3C 46 E7 01 DB 88 DC 07 DC 0C 08 05 3A 02 04
60 00 01 14 4B 3E 65 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 07 DC 0C 08 0D
3A 02 00 16 99 D5 0D 0A
Length(byt
e)
Message Type 1
k
Length 2
i n
Device Type 1 24 24
l l
c ia
e t
u n
Q fide
2
Voltage
2 0000 0000
Reserved
n
o
0x11 | 0x12
C
0x21 | 0x22
Motion Status 1
0x41 | 0x42
0x16
Number 1 1 – 15
Speed 3 0.0 – 999.9km/h
Azimuth 2 0 – 359
Altitude 2
TRACGMT200AN003 – 125 –
Longitude 4
Latitude 4
MCC 2 0000 – FFFF
MNC 2 0000 – FFFF
LAC 2 0000 – FFFF
Reserved 1 00 00
k
n
l i l
c a
Total Hour Meter Count 6 HHHHHHHHHHMMSS
e t i
u n
Q fide
o n
C
TRACGMT200AN003 – 126 –
4.4. Information Report +INF
Information report messages include +RESP:GTINF, +RESP:GTGPS, +RESP:GTCID,

+RESP:GTCSQ, +RESP:GTVER, +RESP:GTBAT, +RESP:GTIOS and +RESP:GTTMZ.
These messages use the same format as below, however only +RESP:GTINF includes all the
items while others only include related information to themselves.
 +INF,
Example:
2B 49 4E 46 01 FF 7F 00 AC 67 6D 74 31 30 30 31 36 24 01 03 05 01 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 41 00 0B 00 07 DC 0C 08 03 38 3B 00 01 00 7F 00 3C 02
k
58 00 00 00 00 00 F0 2E FD 0F CD 56 89 86 01 11 31 31 00 11 12 63 12 00 00 08 00 06 07 04
60 00 01 14 4B CC 13 00 1D 04 60 00 01 10 59 24 06 00 1C 04 60 00 01 10 59 6C 8A 00 1C 04
i n
60 00 01 10 59 C6 AD 00 1B 04 60 00 01 10 59 19 85 00 1A 04 60 00 01 10 59 81 3A 00 17 04
l l
60 00 01 14 4B 3E 65 00 21 07 DC 0C 08 0B 39 00 00 08 D0 12 0D 0A
c a
e t i
Message Header 4 +INF +INF
u n
Message Type 1
Report Mask 2 0000 – FFFF
Q fide
Length 2
Device Type 1 24
n
o
Firmware Version 2 0000 – FFFF +RESP:
GTVER
C
Hardware Version 2 0000 – FFFF
MCU Version 2 0000 – FFFF
Reserved for GPS FW Version 2 0000
Reserved 1 00
Reserved 2 0000
+RESP:
Reserved 9 00
GTIOS
0x11 | 0x12
+RESP:
Motion Status 1 0x21 | 0x22
GTGPS
0x41 | 0x42
TRACGMT200AN003 – 127 –
0x16
Reserved 1 00
GPS on Need / Power Saving Enable /

OWH Mode / Outside Working Hour / 1
AGPS
YYYYMMDDHHMMS
Last Fix UTC Time 7
S
Reserved 1 00
k
FRI Discard No Fix 1 0|1
n
ResponseReport Items Mask 2
l i l
IGN Interval 2
c a
IGF Interval 2
e t i
Reserved 5 0000000000
u n
Main Supply / Backup Battery On /
Charging / LED On / Backup Battery 1
Q fide
Charge Mode
+RESP:
External Power Supply VCC 2 0 GTBAT
Backup Battery VCC 2 0 – 4500mV
n
Backup Battery Level 1 00
o
+RESP:
ICCID 10 ICCID
GTCID
C
CSQ RSSI 1 0 – 31 | 99 +RESP:
CSQ BER 1 0 – 7 | 99 GTCSQ
Time Zone Offset Sign /

1 +RESP:
Daylight Saving Enable
GTTMZ
Time Zone Offset 2 HHMM
GIR Trigger Type 1
Cell Number 1
MCC 2 +RESP:
MNC 2 GTGIR
LAC 2
Cell ID 2
TRACGMT200AN003 – 128 –
Reserved 1
RX Level 1
YYYYMMDDHHMMS
Send Time 7
S
0x0D
Tail Characters 2 0x0D 0x0A
0x0A
 <Message Type>: The ID of information report message.
k
Command ID
n
+RESP:GTINF 1
l i l
+RESP:GTGPS 2
c a
Reserved 3
e t i
+RESP:GTCID 4
u n
+RESP:GTCSQ 5
Q fide
+RESP:GTVER 6
+RESP:GTBAT 7
+RESP:GTIOS 8
+RESP:GTTMZ 9
n
+RESP:GTGIR 10
o
 <Report Mask>: It refer to the <+INF Mask> in AT+GTHRM.
C
 <Unique ID>: If the Bit 1 of <+INF Mask> is 0, IMEI of the device as the unique ID of the
IMEI 13 57 90 24 68 11 22 0
HEX 0D 39 5A 18 44 0B 16 00
If the Bit 1 of <+INF Mask> is 1, use the device name as the unique ID of the device. The
HEX 67 6D 74 32 30 30 00 00
TRACGMT200AN003 – 129 –
 <GPS on Need / Power Saving Enable / OWH Mode / Outside Working Hour / GPS Antenna
Status>: The highest bit, bit 7 is for <GPS on Need>, bit 5 and bit 6 is for<Power Saving
Enable>, bit 4 and bit 3 are for <OWH Mode>, bit 2 is for <Outside Working Hour>. Bit 0 is
for <AGPS>. <Outside Working Hour> is used to indicate whether the device is currently
outside the working hour. 1 means outside.
 <Main Supply / Backup Battery On / Charging / LED On / Backup Battery Charge Mode>:
The highest bit, bit 7 is for <Main Supply> to indicate whether the external power supply is
connected to the device. Bit 6 is for <Backup Battery On> to indicate whether the backup
battery is working. Bit 5 is for <Charging> to indicate whether the backup battery is
currently charging. Bit 4 is for <LED On> to indicate whether the LED’s are turned on. Bit 0
is for <Backup Battery Charge Mode>.
k
 <ICCID>: ICCID is a 20-digit string. In the HEX format message, every 4 bits are used to
n
represent one digit of the 20 digits of the ICCID.
i l
ICCID 89 86 00 00 09 09 17 21 49 53
l
HEX 89 86 00 00 09 09 17 21 49 53
c a

i
<Time Zone Offset Sign / Daylight Saving Enable>: Bit 1 is for <Daylight Saving Enable> to
e t
indicate whether the daylight saving function is currently enabled. Bit 0 is for <Time Zone
Offset Sign> to indicate the positive or negative of the local time offset to UTC. 1 means
u n
negative.
 <GIR Trigger Type>: It refer to the <Fix Type> of +RESP:GTGSM.
Q fide
 <Cell Number>: <Cell Number> express number of the IMSI. The IMSI consist of MCC,
MNC, LAC, Cell ID.
o n
C
TRACGMT200AN003 – 130 –
4.5. Event Report +EVT
Event report messages including +RESP:GTPNA, +RESP:GTPFA, +RESP:GTMPN,

+RESP:GTMPF, +RESP:GTBTC, +RESP:GTSTC, +RESP:GTSTT, +RESP:GTPDP,
+RESP:GTIDN, +RESP:GTIDF, +RESP:GTBPN and +RESP:GTBPF, +RESP:GTSTR,
+RESP:GTSTP, +RESP:GTJDR use this format.
 +EVT,
Example:
2B 45 56 54 09 00 FE 5F FF 00 60 24 01 03 05 01 67 6D 74 31 30 30 31 36 5D 00 00 00 00 00 00
41 0C 01 00 00 00 01 01 2F 00 16 07 3C 47 1B 01 DB 88 BA 07 DC 0C 07 08 2B 29 04 60 00 01
k
10 59 81 6B 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 07 DC 0C 07 10 2B 2C 00
AD AA DB 0D 0A
i n l
Length(byt
l
e)
c ia
Message Header 4 +EVT +EVT
e t
Message Type 1
u n
Q fide
Length 2
Device Type 1 24 24
n
o
C
2
Voltage
Analog Input1 Voltage 2
0x11 | 0x12
0x21 | 0x22
Motion Status 1
0x41 | 0x42
0x16
Number 1 1
TRACGMT200AN003 – 131 –
GPS Accuracy 1 0 0
Speed 3 0.0 – 999.9km/h
Azimuth 2 0 – 359
Altitude 2
Longitude 4
Latitude 4
MCC 2 0000 – FFFF
k
MNC 2 0000 – FFFF
n
LAC 2 0000 – FFFF
l i l
c a
Reserved 1 00 00
e t i
u n
Q fide
n
o
 <Message Type>: The ID of event report message.
C
Command ID
+RESP:GTPNA 1
+RESP:GTPFA 2
+RESP:GTMPN 3
+RESP:GTMPF 4
Reserved 5
+RESP:GTBPL 6
+RESP:GTBTC 7
+RESP:GTSTC 8
+RESP:GTSTT 9
TRACGMT200AN003 – 132 –
10
Reserved
Reserved 11
+RESP:GTPDP 12
+RESP:GTIGN 13
+RESP:GTIGF 14
+RESP:GTUPD 15
+RESP:GTIDN 16
k
+RESP:GTIDF 17
Reserved 18
l i n l
+RESP:GTGSM 19
c a
+RESP:GTJDR 20
e t i
21
Reserved
u n
+RESP:GTBPN 22
Q fide
+RESP:GTBPF 23
+RESP:GTSTR 24
+RESP:GTSTP 25
n
+RESP:GTNMD 26
+RESP:GTJDS 27
o

C
<Report Mask>: It refer to the <+EVT Mask> in AT+GTHRM.
 <Unique ID>: If the Bit 6 of <+EVT Mask> is 0, IMEI of the device as the unique ID of the
IMEI 13 57 90 24 68 11 22 0
HEX 0D 39 5A 18 44 0B 16 00
If the Bit 6 of <+EVT Mask> is 1, use the device name as the unique ID of the device. The
TRACGMT200AN003 – 133 –
HEX 67 6D 74 32 30 30 00 00
Event report message +RESP:GTBPL uses this format.

 +EVT,
Example:
2B 45 56 54 06 00 FE 5F FF 00 62 24 01 03 05 01 67 6D 74 31 30 30 31 36 0F 00 00 00 00 00 00
41 0B 0D D9 01 00 00 00 01 00 C2 00 19 07 3C 47 9C 01 DB 88 28 07 DC 0C 07 17 2E 14 04
60 00 01 10 59 81 6B 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 07 DC 0C 08 07 2E
16 03 D0 05 3B 0D 0A
k
Message Type 1
l i n l
c
Length 2
ia
Device Type 1 24 24
e t
u n
Q fide

2
n
Voltage
o
2 0000 0000
Reserved
C
0x11 | 0x12
0x21 | 0x22
Motion Status 1
0x41 | 0x42
0x16
Backup Battery VCC 2 0 – 4500 mV
Number 1 1
GPS Accuracy 1 0 0
Speed 3 0.0 – 999.9km/h
TRACGMT200AN003 – 134 –
Azimuth 2 0 – 359
Altitude 2
Longitude 4
Latitude 4
MCC 2 0000 – FFFF
MNC 2 0000 – FFFF
LAC 2 0000 – FFFF
k
n
Reserved 1 00 00
l i l
c a
e t i
Current Hour Meter
3 HHMMSS
Count
u n
Q fide
n
Co
Event report message +RESP:GTIGN and +RESP:GTIGF use this format. For these two
messages, the <mileage> field will always be present in spite of the <Report Items Mask> setting.
 +EVT,
Example:
2B 45 56 54 0E 00 FE 5F FF 00 64 24 01 03 05 01 67 6D 74 31 30 30 31 36 60 2E DC 00 00 00
00 11 09 00 00 01 B2 01 00 00 00 06 00 1A 00 0C 07 3C 47 3A 01 DB 88 97 07 DC 0C 06 09 28
14 04 60 00 01 10 59 6C 8A 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 07 DC 0C
06 11 28 17 00 54 86 F2 0D 0A
Message Type 1
TRACGMT200AN003 – 135 –
Length 2
Device Type 1 24 24
External Power Supply Voltage 2
2 0000 0000
k
Reserved
l i n l
c a
0x11 | 0x12
i
0x21 | 0x22
t
Motion Status 1
e
0x41 | 0x42
0x16
u n
Q fide
Duration of Ignition On or
4 0 – 999999 sec
Ignition Off
Number 1 1
n
GPS Accuracy 1 0 0
o
Speed 3 0.0 – 999.9km/h
Azimuth 2 0 – 359
C
Altitude 2
Longitude 4
Latitude 4
MCC 2 0000 – FFFF
MNC 2 0000 – FFFF
LAC 2 0000 – FFFF
Reserved 1 00 00
TRACGMT200AN003 – 136 –
0x0D
Tail Characters 2 0x0D 0x0A
0x0A
n k
Event report message +RESP:GTUPD uses this format. For this message, the <Protocol Version>
l i l
and <Firmware Version> will always be present in spite of the <Report Items Mask> setting
 +EVT,
c ia
Example:
e t
2B 45 56 54 0F 00 FE 5F FF 00 63 24 01 03 05 01 67 6D 74 31 30 30 31 36 4B 2F 1E 00 00 00
00 41 00 01 2D 00 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 04
u n
60 00 01 10 59 81 6B 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 07 DC 0C 08 0B 17
25 00 03 A8 DF 0D 0A
Q fide
Length(b
yte)
n
Message Type 1
o
Length 2
C
Device Type 1 24 24

2
Voltage
2 0000 0000
Reserved
TRACGMT200AN003 – 137 –
0x11 | 0x12
0x21 | 0x22
Motion Status 1
0x41 | 0x42
0x16
Code 2
Retry 1
Number 1 1
k
GPS Accuracy 1 0 0
n
Speed 3 0.0 – 999.9km/h
l i l
Azimuth 2 0 – 359
c a
Altitude 2
e t i
Longitude 4
u n
Latitude 4
Q fide
MCC 2 0000 – FFFF
MNC 2 0000 – FFFF
LAC 2 0000 – FFFF
n
o
Reserved 1 00 00
C
Event report message +RESP:GTIDF uses this format.

 +EVT,
TRACGMT200AN003 – 138 –
Example:
2B 45 56 54 11 00 FE 5F FF 00 64 24 01 03 05 01 67 6D 74 31 30 30 31 36 60 2E FD 00 00 00
00 11 09 00 00 01 A9 01 00 00 00 00 00 1A 00 16 07 3C 47 1E 01 DB 88 BE 07 DC 0C 06 09 29
14 04 60 00 01 10 59 6C 8A 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 07 DC 0C 06
11 29 17 00 58 26 CA 0D 0A
Length(b
yte)
Message Type 1
k
Length 2
i n
Device Type 1 24 24
l l
c ia
e t
u n
Q fide
2
Voltage
2 0000 0000
Reserved
n
o
0x11 | 0x12
C
0x21 | 0x22
Motion Status 1
0x41 | 0x42
0x16
Duration of Idling 4
Number 1 1
GPS Accuracy 1 0 0
Speed 3 0.0 – 999.9km/h
Azimuth 2 0 – 359
Altitude 2
TRACGMT200AN003 – 139 –
Longitude 4
Latitude 4
MCC 2 0000 – FFFF
MNC 2 0000 – FFFF
LAC 2 0000 – FFFF
Reserved 1 00 00
k
n
l i l
c a
e t i
u n
Q fide
Event report message +RESP:GTGSM uses this format.
n
 +EVT,
o
Example:
2B 45 56 54 13 00 FE 5F FF 00 6D 24 01 03 05 01 67 6D 74 31 30 30 31 36 05 07 04 60 00 01 14
C
4B C0 97 00 1E 04 60 00 01 10 59 81 3A 00 19 04 60 00 01 14 4B CC 13 00 18 04 60 00 01 10
59 C6 AD 00 17 04 60 00 01 10 59 24 06 00 17 04 60 00 01 10 59 81 6C 00 15 04 60 00 01 10 59
81 6B 00 23 07 DC 0C 07 10 22 2D 00 A6 1E 85 0D 0A
Length(b
yte)
Message Type 1
Length 2
Device Type 1 24 24
TRACGMT200AN003 – 140 –
Fix Type 1
Cell Number 1
MCC 2 0000 – FFFF
MNC 2 0000 – FFFF
LAC 2 0000 – FFFF 0
k
TA 1 00 00
n
RX Level 1 00 – FF
l i l
c a
e t i
u n
Q fide
 <Fix Type> : A string to indicate what kind of GPS fixing this cell information is for.
"SOS" This cell information is for SOS requirement.
"RTL" This cell information is for RTL requirement.
"LBC" This cell information is for LBC requirement.
n
"TOW" This cell information is for TOW requirement.
"FRI" This cell information is for FRI requirement.
o
"GIR" This cell information is for sub command “C” in AT+GTRTO command.
C
Fix Type ID
SOS 1
RTL 2
LBC 3
TOW 4
FRI 5
GIR 6
Event report message +RESP:GTNMD uses this format.

 +EVT,
TRACGMT200AN003 – 141 –
Example:
2B 45 56 54 1A 00 FE 5F FF 00 64 24 01 03 05 01 67 6D 74 31 30 30 31 36 60 2E FD 00 00 00
00 11 09 00 00 01 A9 01 00 00 00 00 00 1A 00 16 07 3C 47 1E 01 DB 88 BE 07 DC 0C 06 09 29
14 04 60 00 01 10 59 6C 8A 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 07 DC 0C 06
11 29 17 00 58 26 CA 0D 0A
Length(b
yte)
Message Type 1
k
Length 2
i n
Device Type 1 24 24
l l
c ia
e t
u n
Q fide
2
Voltage
2 0000 0000
Reserved
n
o
0x11 | 0x12
C
0x21 | 0x22
Motion Status 1
0x41 | 0x42
0x16
NMD status 1 0|1
Number 1 1
GPS Accuracy 1 0 0
Speed 3 0.0 – 999.9km/h
Azimuth 2 0 – 359
Altitude 2
TRACGMT200AN003 – 142 –
Longitude 4
Latitude 4
MCC 2 0000 – FFFF
MNC 2 0000 – FFFF
LAC 2 0000 – FFFF
Reserved 1 00 00
k
n
l i l
c a
e t i
u n
Q fide
Event report message +RESP:GTJDS uses this format.
n
 +EVT,
o
Example:
2B 45 56 54 1B 00 FE 5F FF 00 64 24 01 03 05 01 67 6D 74 31 30 30 31 36 60 2E FD 00 00 00
C
00 11 09 00 00 01 A9 01 00 00 00 00 00 1A 00 16 07 3C 47 1E 01 DB 88 BE 07 DC 0C 06 09 29
14 04 60 00 01 10 59 6C 8A 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 07 DC 0C 06
11 29 17 00 58 26 CA 0D 0A
Length(b
yte)
Message Type 1
Length 2
Device Type 1 24 24
TRACGMT200AN003 – 143 –

2
Voltage
2 0000 0000
Reserved
k
0x11 | 0x12
n
0x21 | 0x22
i
Motion Status 1
l l
0x41 | 0x42
0x16
c ia
e t
Jamming Status 1 1|2
u n
Number 1 1
Q fide
GPS Accuracy 1 0 0
Speed 3 0.0 – 999.9km/h
Azimuth 2 0 – 359
n
Altitude 2
o
Longitude 4
Latitude 4
C
MCC 2 0000 – FFFF
MNC 2 0000 – FFFF
LAC 2 0000 – FFFF
Reserved 1 00 00
TRACGMT200AN003 – 144 –

 <Jamming Status>: The current Jamming status of the device.
 1: Quit the jamming.
 2: Enter the jamming.
i n k l
cl ia
ue n t
Q fide
o n
C
TRACGMT200AN003 – 145 –
4.6. Heartbeat Data +HBD
 +HBD,
Example:
2B 48 42 44 FF 20 24 01 03 05 01 67 6D 74 31 30 30 31 36 07 DC 0C 07 12 0D 2C 00 B9 4E E1
0D 0A
Message Header 4 +HBD +HBD
k
Report Mask 1 00 – FF
n
Length 1
l i l
Device Type 1 24 24
c a
e t i
u n
Q fide
o n
 <Report Mask>: It refer to the <+HBD Mask> in AT+GTHRM.
 <Unique ID>: If the Bit 4 of <+HBD Mask> is 0, IMEI of the device as the unique ID of the
C
IMEI 13 57 90 24 68 11 22 0
HEX 0D 39 5A 18 44 0B 16 00
If the Bit 4 of <+HBD Mask> is 1, use the device name as the unique ID of the device. The
HEX 67 6D 74 32 30 30 00 00
TRACGMT200AN003 – 146 –
If the mask of <UID> set as 0 in the <+HBD Mask> of AT+GTHRM, the heart beat message will
not report device name or IMEI information. If the mask of <UID> is set as 1, then according to
the mask of <device name>, the heart beat message will report device name or IMEI information
i n k l
cl ia
ue n t
Q fide
o n
C
TRACGMT200AN003 – 147 –
4.7. Buffer Report in HEX Format
When HEX format messages go into the local buffer, the device will replace the 2nd byte of the
report messages with ‘B’. Thus, +BSP is buffered report for +RSP, +BNF is buffered report for
+INF and +BVT is buffered report for +EVT. The rest part of the report messages keep
untouched.
i n k l
cl ia
ue n t
Q fide
o n
C
TRACGMT200AN003 – 148 –
Appendix: Message Index
 Command and ACK

AT+GTBSI
+ACK:GTBSI
AT+GTSRI
+ACK:GTSRI
AT+GTQSS
+ACK:GTQSS
AT+GTCFG
k
+ACK:GTCFG
AT+GTOUT
n
+ACK:GTOUT
l i l
AT+GTDIS
+ACK:GTDIS
c ia
AT+GTIOB
e t
+ACK:GTIOB
AT+GTEPS
u n
+ACK:GTEPS
AT+GTFRI
Q fide
+ACK:GTFRI
AT+GTGEO
+ACK:GTGEO
AT+GTTOW
n
+ACK:GTTOW
AT+GTSPD
o
+ACK:GTSPD
AT+GTSOS
C
+ACK:GTSOS
AT+GTIDL
+ACK:GTIDL
AT+GTHBM
+ACK:GTHBM
AT+GTTMA
+ACK:GTTMA
AT+GTOWH
+ACK:GTOWH
AT+GTDOG
+ACK:GTDOG
AT+GTPIN
+ACK:GTPIN
AT+GTRTO
+ACK:GTRTO
TRACGMT200AN003 – 149 –
AT+GTHMC
+ACK:GTHMC
AT+GTJDC
+ACK:GTJDC
AT+GTHRM
+ACK:GTHRM
AT+GTJBS
+ACK:GTJBS
AT+GTWLT
+ACK:GTWLT
AT+GTSSR
+ACK:GTSSR
k
AT+GTNMD
n
+ACK:GTNMD
i
AT+GTFFC
l l
+ACK:GTFFC
c a
AT+GTPDS
i
+ACK:GTPDS
ue n t
Position Related Report
Q fide
+RESP:GTTOW
+RESP:GTEPS
+RESP:GTDIS
+RESP:GTIOB
+RESP:GTFRI
n
+RESP:GTGEO
o
+RESP:GTSPD
+RESP:GTSOS
+RESP:GTRTL
C
+RESP:GTLBC
+RESP:GTDOG
+RESP:GTIGL
+RESP:GTHBM
 Device Information Report

+RESP:GTINF
 Report for Querying

+RESP:GTGPS
+RESP:GTALL
+RESP:GTCID
+RESP:GTCSQ
TRACGMT200AN003 – 150 –
+RESP:GTVER
+RESP:GTBAT
+RESP:GTIOS
+RESP:GTTMZ
 Event Report
+RESP:GTPNA
+RESP:GTPFA
+RESP:GTMPN
+RESP:GTMPF
+RESP:GTBTC
+RESP:GTSTC
k
+RESP:GTBPL
n
+RESP:GTBPN
i
+RESP:GTBPF
l l
+RESP:GTSTT
c a
+RESP:GTPDP
i
+RESP:GTIGN
e t
+RESP:GTIGF
u n
+RESP:GTIDN
+RESP:GTIDF
Q fide
+RESP:GTJDR
+RESP:GTGSM
+RESP:GTSTR
+RESP:GTSTP
+RESP:GTNMD
n
+RESP:GTJDS
o
 Heartbeat
+ACK:GTHBD
C
+SACK:GTHBD
 Server Acknowledgement
+SACK
 Hex format report message

+ACK
+RSP
+EVT
+INF
+HBD
TRACGMT200AN003 – 151 –

GMT200 @track Air Interface Protocol V3.00 PDF

Uploaded by

Document Informationclick to expand document information

Document Informationclick to expand document information

Copyright:

Available Formats

GMT200 @track Air Interface Protocol V3.00 PDF

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

GMT200 @track Air Interface Protocol V3.00 PDF

Uploaded by

Copyright:

Available Formats

GMT200 @Track Air Interface Protocol

GSM/GPRS/GPS Tracker GMT200

Document Title GMT200 @Track Air Interface Protocol

Document Control ID TRACGMT200AN003

Revision Date Author Description of change

1.1. Scope of This Document

3.1. Message Format

3.2. Command And Acknowledgement

3.2.1. Server Connection

3.2.1.1. Bearer Setting Information

The acknowledgment message of AT+GTBSI command:

Parameter Length(byte) Range/Format Default

Serial Number 4 0000 – FFFF

3.2.1.2. Backend Server Register Information

SN Parameter Length(byte) Range/Format Default

1 Password 4–6 '0' – '9' 'a' – 'z' 'A' – 'Z' gmt200

2 Report Mode 1 0–6 0

11 SACK Enable 1 0|1 0

12 Protocol Format 1 0|1 0

Serial Number 4 0000 – FFFF

The acknowledgment message of AT+GTSRI command:

Parameter Length(byte) Range/Format Default

Count Number 4 0000 – FFFF

SN Parameter Length(byte) Range/Format Default

1 Password 4–6 '0' – '9' 'a' – 'z' 'A' – 'Z' gmt200

3 APN User Name <=30

4 APN Password <=30

5 Report Mode 1 0–6 0

7 Buffer Mode 1 0–2 1

9 Main Server Port <=5 0 – 65535

Parameter Length(byte) Range/Format Default

Serial Number 4 0000 – FFFF

Send Time 14 YYYYMMDDHHMMSS

Count Number 4 0000 – FFFF

3.2.2. Device Configuration

3.2.2.1. Global Configuration

The AT+GTCFG command is used to configure the global parameters.

6 GPS On Need 1 0|1 0

7 GSM report 1 0–3 0

14 Info Report Enable 1 0|1 0

15 Info Report Interval <=5 30 – 86400sec 300

16 Location By Call 1 0–2 0

18 Power Mode 1 0–2 0

19 Agps Mode 1 0|1 0

Serial Number 4 0000 – FFFF

 <New Password>: Set to change the current password.

Parameter Length(byte) Range/Format Default

Serial Number 4 0000 – FFFF

Send Time 14 YYYYMMDDHHMMSS

Count Number 4 0000 – FFFF

3.2.2.2. Auto-unlock PIN

SN Parameter Length(byte) Range/Format Default

1 Password 4–6 '0' – '9' 'a' – 'z' 'A' – 'Z' gmt200

2 Enable Auto-unlock PIN 1 0|1 1

3 PIN 4–8 '0' – '9'

Serial Number 4 0000 – FFFF

Send Time 14 YYYYMMDDHHMMSS