Sie sind auf Seite 1von 90

GSM/GPRS/GPS Tracker GL300

@Track Air Interface Protocol


Application Notes: TRACGL300AN001
Revision: 1.02

sales@eddywireless.com
GL300 @Tracker Air Interface Protocol

Document Title GL300 @Tracker Air Interface Protocol

Version 1.02

Date 2013-11-26

Status Release

Document Control ID TRACGL300AN001

k
General Notes

n
Queclink offers this information as a service to its customers, to support application and

l i
engineering efforts that use the products designed by Queclink. The information provided is

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

u
the customer or the customer’s system integrator. All specifications supplied herein are

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 the 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. 2011

TRACGL300AN001 -1-
GL300 @Tracker Air Interface Protocol

Contents

Contents ............................................................................................................................................2
Table Index........................................................................................................................................4
Figure Index ......................................................................................................................................5
0. Revision history ............................................................................................................................6
1. Overview.......................................................................................................................................8
1.1. Scope ...................................................................................................................................8
1.2. Terms and Abbreviations.....................................................................................................8
2. System Architecture ......................................................................................................................9

k
3. Message Description ...................................................................................................................10

n
3.1. Message Format ................................................................................................................10

i
3.2. Command and Acknowledgement.....................................................................................12

l l
3.2.1. Quick Start Setting...............................................................................................12

c
3.2.2. Bearer Setting Information ..................................................................................15

i a
3.2.3. Backend Server Register Information..................................................................16

e t
3.2.4. Global Configuration ...........................................................................................18
3.2.5. Non movement detection .....................................................................................21

u n
3.2.6. Time Adjustment..................................................................................................23
3.2.7. Fixed Report Information ....................................................................................24

Q fide
3.2.8. Geo-Fence Information........................................................................................27
3.2.9. Speed Alarm.........................................................................................................29
3.2.10. Function Key Setting ...........................................................................................30
3.2.11. Real Time Operation............................................................................................32

n
3.2.12. White Call List Configuration .............................................................................33
3.2.13. Google link SMS configuration ...........................................................................35

o
3.2.14. Auto unlock SIM-PIN..........................................................................................36
3.2.15. Digital Input Port Settings ...................................................................................37

C
3.2.16. Protocol watchdog ...............................................................................................38
3.2.17. Data transfer between UART and backend server ...............................................40
3.2.18. Network Select.....................................................................................................41
3.2.19. Outside Working Hours .......................................................................................42
3.2.20. Temperature Alarm ..............................................................................................43
3.2.21. Store Command String.........................................................................................45
3.2.22. User Defined Function.........................................................................................46
3.2.23. Update configuration over the air ........................................................................48
3.2.24. Jamming Detection ..............................................................................................49
3.3. Report................................................................................................................................52
3.3.1. Position Related Report .......................................................................................52
3.3.2. Device Information Report ..................................................................................56
3.3.3. Report for Querying.............................................................................................58
3.3.4. Event Report ........................................................................................................70
3.3.5. Buffer Report .......................................................................................................83
TRACGL300AN001 -2-
GL300 @Tracker Air Interface Protocol

3.3.6. Report Google Maps hyperlink............................................................................84


3.4. Heartbeat ...........................................................................................................................85
3.5. Sever Acknowledgement...................................................................................................85
Appendix: Message Index...............................................................................................................87

i n k
c l i al
u e n t
Q fide
o n
C
TRACGL300AN001 -3-
GL300 @Tracker Air Interface Protocol

Table Index

TABLE 1: TERMS AND ABBREVIATIONS .........................................................................................8

i n k
c l i al
u e n t
Q fide
o n
C
TRACGL300AN001 -4-
GL300 @Tracker Air Interface Protocol

Figure Index

FIGURE 1: SYSTEM ARCHITECTURE................................................................................................9


FIGURE 2: @TRACKER PROTOCOL MESSAGES FLOW...............................................................10

i n k
c l i al
u e n t
Q fide
o n
C
TRACGL300AN001 -5-
GL300 @Tracker Air Interface Protocol

0. Revision history

Revision Date Author Description of change


0.02 2012-10-12 Evan.tu Initial
1.00 2012-10-26 Evan.Tu 1. Add a new parameter to control whether to drive
the motor in the command “AT+GTFKS”
2. Add a new command “AT+GTMON”
2012-11-12 Evan.Tu 3.Delete the command “AT+GTFFC” protocol
2012-11-14 Evan.Tu 4.Modified the command “AT+GTRTO” protocol
5.Modified the command “AT+GTOWH” protocol

k
2012-11-16 Evan.Tu 6.Delete the report massage “+RESP:GTANT”

n
2012-11-19 Evan.Tu 7.Add the report massage “+RESP:GTALS”

i
2012-11-20 Evan.Tu 8.Add 4 reserved parameter in the command

l l
“AT+GTOWH”

c
2012-11-26 Evan.Tu 9.Modified the parameter <log enable> is reserved

i a
2012-11-28 in the commands “AT+GTQSS 、AT+GTBSI”

e t
Evan.Tu 10.Modified the report massage “+RESP:GTDOG”

u
Evan.Tu 11.Modified the description of NOTE in the

n
command “AT+GTFRI”

Q fide
Evan.Tu 12.Add the report massage “+RESP:GTDAT”
2012-11-29 Evan.Tu 13.Add a parameter <GSM Interval> in the
command “AT+GTNTS”
2012-12-04 Evan.Tu 14.Modified the report massage “+RESP:GTALL”
15.Modified the report massage “+RESP:GTDOG”

n
2012-12-15 Evan.Tu 16.Modified the decription of the parameter<Power
key ind> in command “AT+GTFKS”

o
17.Add the report massage “+RESP:GTMON”
2013-1-5 Evan.Tu 18.Add the temperature alarm report function

C
AT+GTTEM and the alarm report massage
+RESP:GTTEM
2013-1-9 Evan.Tu 19.Add a parameter <temperature> in the report
massage +RESP:GTINF
2013-1-15 Evan.Tu 20.Modified the report massage “+RESP:GTMON”
1.01 2013-07-24 Evan.Tu 1.Add two new commands “AT + GTCMD” and
“AT + GTUDF”
2.Add two new parameters <SMS ACK Enable>
and <quick link enable> in the command
“AT+GTSRI”
2013-08-28 Evan.Tu 1.Add a new protocol command AT + GTUPC
2013-08-30 Evan.Tu 1.Delete a protocol command AT + GTMON
1.02 2013-10-17 Evan.Tu 1.Add the report mode 6 in the command
AT+GTQSS

TRACGL300AN001 -6-
GL300 @Tracker Air Interface Protocol

2.Add the mode 6 in the command AT+GTFRI


2013-11-14 Evan.Tu 1.Add a new protocol command AT+GTJDC

i n k
c l i al
u e n t
Q fide
o n
C
TRACGL300AN001 -7-
GL300 @Tracker Air Interface Protocol

1. Overview

1.1. Scope

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
confirms with an acknowledgement message. If necessary, the terminal also sends report messages
to the backend server.

k
The purpose of this document is to describe how to build up the backend server based on the
@Track Air Interface Protocol.

l i n l
1.2. Terms and Abbreviations

c i a
Table 1: Terms and abbreviations

e t
Abbreviation Description

u n
APN Access Point Network
ASCII American National Standard Code for Information Interchange

Q fide
GPRS General Packet Radio Service
GSM Global System for Mobile Communications
HDOP Horizontal Dilution of Precision
ICCID Integrated Circuit Card Identity

n
IP Internet Protocol
SMS Short Message Service

o
TCP Transmission Control Protocol
UDP User Datagram Protocol

C
UTC Coordinated Universal Time

TRACGL300AN001 -8-
GL300 @Tracker Air Interface Protocol

2. System Architecture

i n k
c l i al
e t
Figure 1: System architecture

u n
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
TRACGL300AN001 -9-
GL300 @Tracker Air Interface Protocol

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
AT+GTXXX=<parameter1>,<parameter2>,…$ Command
+ACK:GTXXX,<parameter1>,<parameter2>,…$ Acknowledgement

k
+RESP:GTXXX,<parameter1>,<parameter2>,…$ Report

n
The entire message string ends with character ‘$’.

i
The characters ‘XXX’ identify the deferent message.

l l
The “<parameter1>,<parameter2>,…” carry the message’s parameters. The number of parameters

c
is different in different messages. The ASCII character ‘,’ is used to separate the neighbouring

i a
parameter characters. The parameter string may contain the ASCII characters:

e t
‘0’-‘9’, ’a’-‘z’, ’A’-‘Z’.
Detailed descriptions of each message format are located in the specific message sections.

u n
By sending Commands to the terminal, the backend server can either configure and query the

Q fide
parameters of the terminal or control the terminal to perform specific actions. When the terminal
receives Commands over the air, it will reply with a corresponding Acknowledgement message.
According to the configuration of the parameters, the terminal can send Report messages to the
backend server. Please see the following figure:

o n Command

C
Acknowledgement

Terminal Backend
Server
Report

Report

Report

Figure 2: @Tracker protocol messages flow

TRACGL300AN001 - 10 -
GL300 @Tracker Air Interface Protocol

When the device receives commands over the air, it supports several commands in one SMS or
GPRS packet without separate symbol between two close commands. But it is necessary to make
sure the total size of the several commands is not longer than 160 if the commands are sent via
SMS. Here is an example to send three commands in one SMS.

AT+GTFRI=gl300,1,1,,,0000,2359,60,60,,,1F,0,,,,,,,,0007$AT+GTGEO=gl300,0,3,101.412248,
21.187891,1000,600,,,,,,,,,0008$AT+GTSPD=gl300,1,5,40,30,60,,,,,,,,,,,,,,,,0009$

It includes three commands (AT+GTFRI, AT+GTGEO and AT+GTSPD) in the above message.
And the terminal will handle the three commands one by one after it received the message via

k
SMS and it will report the following three acknowledgement message to the backend server one
by one.

l i n
+ACK:GTFRI,1A0102,135790246811220,,0007,20100310172830,11F0$

c al
+ACK:GTGEO,1A0102,135790246811220,,0,0008,20100310172900,11F1$

e t i
+ACK:GTSPD,1A0102,135790246811220,,0009,20100310172930,11F2$

u
Q fide n
o n
C
TRACGL300AN001 - 11 -
GL300 @Tracker Air Interface Protocol

3.2. Command and Acknowledgement

3.2.1. Quick Start Setting

The command AT+GTQSS is used to set 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=gl300,cmnet,,,4,,,116.226.44.17,9001,116.226.44.16,9002,+8613812341234,0,1,

k
,,0001$

n
Parameter Length (byte) Range/Format Default

i
Password 4–6 ‘0’ – ‘9’, ‘a’ – ‘z’, ‘A’ – ‘Z’ gl300

l l
APN <=40

c a
APN user name <=30

i
APN password <=30

e t
Report mode 1 0–6 0

u n
Reserved 0
Buffer enable 1 0|1|2 1

Q fide
Main server IP/domain <=60
name
Main server port <=5 0 – 65535 0
Backup server IP <=15 0.0.0.0
Backup server port <=5 0 – 65535 0

n
SMS gateway <=20

o
Heartbeat interval <=3 0|5 – 360min 0
SACK enable 1 0|1 0

C
Reserved 0
Reserved 0
Serial number 4 0000 – FFFF
Tail character 1 $ $

 <Password>: The valid character of password is ‘0’-9’, ‘a’-‘z’, ‘A’-‘Z’. The default value is
“gl300”.
 <APN>: Access point name (APN).
 <APN user name>: the GPRS APN user name. If the parameter field is empty, the parameter
will be cleared.
 <APN password>: the GPRS APN password. If the parameter field is empty, the parameter
will be cleared.
 <Report mode>: Supports report modes as following:
 0: Stop reporting.
 1: TCP short-connect preferred mode. The connection is based on TCP protocol. The
TRACGL300AN001 - 12 -
GL300 @Tracker Air Interface Protocol

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 is failed to
establish a TCP connection with the backend server (including Main Server and
Backup Server), it will try to send data via SMS.
 2: TCP short-connect 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 is failed to
establish a TCP connection with the backend server (including Main Server and
Backup Server), it will be stored in the BUFFER (if BUFFER function is enabled,
please refer to <Buffer enable>) or discarded (if the BUFFER function is disabled).
 3: TCP long-connect mode. The connection is based on TCP protocol. The terminal

k
connects to the backend server and maintains the connection using the heart beat data.
Please note that in this mode the backend server should respond to the heart beat data

n
from the terminals.

l i
 4: UDP mode. The terminal will send data to the backend server by UDP protocol. It

l
supports to receive protocol command via UDP. But it is recommended to make sure

c a
the IP address and UDP port of the device can be visited in the internet, and this is

e i
generally realized by heart beat package and the message +RESP:GTPDP.

t
 5: Force on SMS. Only use the SMS for transmitting.

u
 6: UDP with fixed local port. Like the UDP mode, the terminal will send data using

n
UDP protocol. The difference is the terminal will use fixed local port rather than

Q fide
random port to communicate with the server in this mode. Thus the backend server
could use identical port to communicate with all terminals if the backend server and
the terminals are all in the same VPN network. The port number the device uses is the
same as the port number of the primary server.
 <Reserved>: .Not used at present.Please keep empty

n
 <Buffer enable>: Enable or disable BUFFER function. Please refer to 3.3.5 for the details

o
about BUFFER function.
 0: Disable the BUFFER function.
 1: Enable the BUFFER function.

C
 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 main server.
 <Main server port>: The port of the main server.
 <Backup server IP>: The IP address of the backup backend 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. Short code (for example: 10086) is also supported.
 <Heartbeat interval>: the interval for the terminal to send heartbeat package message to the
backend server. If set to 0, no heartbeat package is sent.
 <SACK enable>: A numeric to indicate whether the backend server should reply SACK
message to the device.
 0: the backend server does not reply SACK message after receiving a message from

TRACGL300AN001 - 13 -
GL300 @Tracker Air Interface Protocol

the device.
 1: the backend server should reply SACK message after receiving a message from the
device.
 <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 should be “$”.
Note:
If <Report mode> is set as 4 (UDP mode), it is strongly recommended to enable SACK or heart
beat mechanism (<Heartbeat interval> doesn’t equal to 0).

The acknowledgement message of AT+GTQSS command:

k
 +ACK:GTQSS,
Example:

i n
+ACK:GTQSS,1A0102,135790246811220,,0001,20100310172830,11F0$

l l
Parameter Length (byte) Range/Format Default
Protocol version 6 XX0000 – XXFFFF,

c a
X∈{'A'-'Z','0'-'9'}

e t i
Unique ID 15 IMEI
Device name 20

u n
Serial number 4 0000 – FFFF
Send time 14 YYYYMMDDHHMMSS

Q fide
Count number 4 0000 – FFFF
Tail character 1 $ $

 <Protocol version>: The combination of the device type and the version number of the

n
applied protocol. The first two characters ‘XX’ indicate the device type. ‘1A’ represents
GL300. The middle two characters are the main version number and the last two characters

o
are the minimum version number. Both the main version and the minimum version are hex
digital. For example, ‘020A’ means version 2.10.

C
 <Unique ID>: ID of the device, use the IMEI of the current SIM card inside the terminal.
 <Device name>: Please refer to the parameter <Device name> in the command
AT+GTCFG.
 <Serial number>: The same serial number which is sent to the device with the corresponding
command. The backend server could use it to distinguish which command the ACK message
is for.
 <Send time>: The local time to send the ACK message.
 <Count number>: The self-increasing count number will be put into every acknowledgment
message and report message. The count is beginning from 0000 and increases by 1 every
time. It will roll back after “FFFF”.

TRACGL300AN001 - 14 -
GL300 @Tracker Air Interface Protocol

3.2.2. Bearer Setting Information

The command AT+GTBSI is used to set the GPRS parameter.


 AT+GTBSI=
Example:
AT+GTBSI=gl300,cmnet,,,,,,,0002$
Parameter Length (byte) Range/Format Default
Password 4–6 ‘0’ – ‘9’, ‘a’ – ‘z’, ‘A’ – ‘Z’ gl300
APN <=40
APN user name <=30

k
APN password <=30
Reserved 0

n
Reserved 0

l i
Reserved 0

l
Reserved 0

c a
Serial number 4 0000 – FFFF

e i
Tail character 1 $ $

u n t
The acknowledgement message of AT+GTBSI command:
 +ACK:GTBSI,

Q fide
Example:
+ACK:GTBSI,1A0102,135790246811220,,0002,20100310172830,11F0$
Parameter Length (byte) Range/Format Default
Protocol version 6 XX0000 – XXFFFF,

n
X∈{'A'-'Z','0'-'9'}
Unique ID 15 IMEI

o
Device name 20
Serial number 4 0000 – FFFF

C
Send time 14 YYYYMMDDHHMMSS
Count number 4 0000 – FFFF
Tail character 1 $ $

TRACGL300AN001 - 15 -
GL300 @Tracker Air Interface Protocol

3.2.3. Backend Server Register Information

The command AT+GTSRI is used to configure the backend server information that the terminal
reports to and the report mode that defines the communication method between the backend server
and the terminal.
 AT+GTSRI=
Example:
AT+GTSRI=gl300,4,,,116.226.44.17,9001,116.226.44.16,9002,+8613812341234,0,1,,,,,0003$
Parameter Length (byte) Range/Format Default
Password 4–6 ‘0’ – ‘9’, ‘a’ – ‘z’, ‘A’ – ‘Z’ gl300
Report mode 1 0–5 0

k
Reserved 0

n
Buffer enable 1 0|1|2 1

l i
Main server IP/domain <=60

l
name

c a
Main server port <=5 0 – 65535 0

e i
Backup server IP <=15 0.0.0.0

t
Backup server port <=5 0 – 65535 0

u n
SMS gateway <=20
Heartbeat interval <=3 0|5 – 360min 0

Q fide
SACK enable 1 0|1 0
SMS ACK Enable 1 0|1 0
Quick Link Enable 1 0|1 0
Reserved 0

n
Reserved 0
Serial number 4 0000 – FFFF

o
Tail character 1 $ $

C
 <SMS ACK Enable>: This defines whether the ACK confirmation should respond by SMS
when the command was sent by SMS.
 0: the device will send the ACK confirmation with the mode configured by the
<Report Mode>.
 1: the device will send the ACK confirmation by SMS to the phone which sent the
command by SMS.
 <Quick link Enable>: This defines whether the device should establish TCP connection under
certain condition.
 0: disable.
 1: The device should establish TCP connection immediately when a call is coming.
This feature will be valid only when the report mode is set as TCP long connection.

The acknowledgement message of AT+GTSRI command:


 +ACK:GTSRI,
TRACGL300AN001 - 16 -
GL300 @Tracker Air Interface Protocol

Example:
+ACK:GTSRI,1A0102,135790246811220,,0003,20100310172830,11F0$
Parameter Length (byte) Range/Format Default
Protocol version 6 XX0000 – XXFFFF,
X∈{'A'-'Z','0'-'9'}
Unique ID 15 IMEI
Device name 20
Serial number 4 0000 – FFFF
Send time 14 YYYYMMDDHHMMSS
Count number 4 0000 – FFFF
Tail character 1 $ $

i n k
c l i al
u e n t
Q fide
o n
C
TRACGL300AN001 - 17 -
GL300 @Tracker Air Interface Protocol

3.2.4. Global Configuration

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

 AT+GTCFG=
Example:
AT+GTCFG=quectl,123456,,,,,,,,,,,,,,,,,,,,0004$
AT+GTCFG=gl300,,GL300,0,0.0,0,7,0,0,,,,1,1,300,1,0,20491231235959,1,0,,0004$
Parameter Length (byte) Range/Format Default
Password 4–6 ‘0’ – ‘9’, ‘a’ – ‘z’, ‘A’ – ‘Z’ gl300
New password 4–6 ‘0’ – ‘9’, ‘a’ – ‘z’, ‘A’ – ‘Z’

k
Device name 20 ‘0’ – ‘9’, ‘a’ – ‘z’, ‘A’ – ‘Z’, ‘-’, GL300

n
‘_’

l i
ODO enable 1 0|1 0

l
ODO mileage <=9 0.0 – 4294967.0Km 0.0

c a
GPS on need 1 0|1|2|3 1

e i
GPS fix delay 2 5 – 60sec 5

t
Report items mask <=4 0000 – 007F 001F

u n
Gsm report 1 0|1|2|3 0
Reserved 0

Q fide
Event mask 4 0000-3FFF 0FFF
EPB mode 1 0|1 0
LED on 1 0|1|2 1
Info report enable 1 0|1 1

n
Info report interval <=5 30 – 86400sec 300
Location by call 1 0|1 1

o
Expiry enable 1 0|1 0
Expiry time 14 YYYYMMDDHHMMSS 204912312

C
35959
Agps mode 1 0|1 0
Sleep enable 1 0|1 0
Reserved 0
Serial number 4 0000 – FFFF
Tail character 1 $ $

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


 <Device name>: the name of the device, which appears in each uplink message.
 <ODO enable>: Enable or disable the odograph function to calculate the total mileage. The
current mileage is included in the message GTINF.
 0: Disable the ODO mileage function.
 1: Enable the ODO mileage function.
 <ODO mileage>: The value of the current total mileage.

TRACGL300AN001 - 18 -
GL300 @Tracker Air Interface Protocol

 <GPS on need>: Whether to close GPS chip after retrieving GPS position information.
 0: Never close GPS chip
 1: Close GPS chip after retrieving GPS information every time.
 2: Never close GPS chip only in ignition on state or movement state.
 3: Never open GPS chip.
 <GPS fix delay>: This is the time to wait after GPS fixing succeed. After GPS fixing succeed,
the device will wait for a period of time (defined by <GPS fix delay>) and then get the result
of GPS fixing because maybe it is not accurate to get the position immediately after GPS
fixing succeed. (e.g. if <GPS fix delay> is set as 7, we will wait for 7 seconds after GPS
fixing succeed and then get the position as the result). The range of the parameter is 5 – 60,
and the default value is 5. Unit: second.

k
 <Report items mask>: Bitwise report mask to configure the composition of all the uplink
message. Each bit represents a field in the uplink message. If some bit is set as 1, the

n
corresponding field will be filled if it is included in the uplink message. Otherwise, the field

l i
will be empty.

l
Bit0(0001): <speed>

c a
Bit1(0002): <azimuth>

e i
Bit2(0004): <altitude>

t
Bit3(0008): GSM LAI and CI, including <mcc>, <mnc>, <lac>, <cellid>

u n
Bit4(0010): <send time>
Bit5(0020): <Device name>

Q fide
 <Event mask>: A Hex value to configure which event reports can be sent to the backend
server: Each bit corresponds to a report message. And if the bit is set as 1, the corresponding
report message can be sent to the backend server. Otherwise, it can not be sent to the backend
server. Here is the mapping between each bit and each report message.
bit0(0001): +RESP:GTPNA

n
bit1(0002): +RESP:GTPFA

o
bit2(0004): +RESP:GTEPN
bti3(0008): +RESP:GTEPF
bit4(0010): Reserved

C
bit5(0020): +RESP:GTBPL
Bit6(0040): +RESP:GTBTC
Bit7(0080): +RESP:GTSTC
bit8(0100): +RESP:GTSTT
bit9(0200): Reserved
bit10(0400): +RESP:GTPDP
bit11(0800): +RESP:GTPNL
bit12(1000): +RESP:GTIGN and +RESP:GTIGF
bit13(2000): +RESP:GTIGL
 <Gsm report>: If GPS fixing for the report message +RESP:GTSOS, +RESP:GTRTL,
+RESP:GTLBC and +RESP:GTFRI were failed and the parameter <Gsm report> was set as
1, the terminal reports the message +RESP:GTGSM, including the information of the service
cell and the neighbour cells after those messages.
 0: Not allow the cells’ information report after failed to get GPS position.

TRACGL300AN001 - 19 -
GL300 @Tracker Air Interface Protocol

 1: Allow the cells’ information report after failed to get GPS position.
 2: Do not report the message +RESP:GTGSM if no cell’s information is found.
 3: Allow the cells’ information report whatever it gets GPS position or not
 <EPB mode>: The mode of External Power Control Unit With Built-in Motion Sensor.
 0: disable External Power Control Unit With Built-in Motion Sensor.
 1: enable External Power Control Unit With Built-in Motion Sensor.
 <LED on>: Configure the working mode of LEDs.
 0: Each time after the device powers on or the parameter is updated to 0 from other
values, GPS LED will work for 150 seconds and then turn off deadly. GSM LED and
Power LED work normally.
 1: All LEDs work normally.

k
 2: All LEDs are off always except the following cases. The first exception is all LEDs
will work for a period time after power on. The second exception is Power LED will

n
flash fast during power off procedure. The third exception is Power LED will work

l i
normally for charging status when a charger is inserted in power off state.

l
 <Info report enable>: Enable/disable the device information report (+RESP:GTINF)

c a
function. The device information include state of the device, ICCID, GSM signal strength,

e i
adapter connection status, battery voltage, charging status, Power and GPS LED working

t
mode, GPS on need setting, GPS antenna type, GPS antenna status, the last known time of

u n
GPS fix.
 0: Disable the device information report function.

Q fide
 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.

n
 <Expiry enable >: Enable or disable the expiry function to stop all the GPS fixing and any

o
reports.
 0: Disable the Expiry function.
 1: Enable the Expiry function.

C
 <Expiry time>: The time when to stop all the GPS fixing and any reports. The valid format is
“YYYYMMDDHHMMSS”. The value range of “YYYY” is “2000”-“3000”. The value
range of “MM” is “01”-“12”. The value range of “DD” is “00”-“31”. The value range of
“HH” is “00”-“23”. The value range of “MM” is “00”-“59”. The value range of “SS” is
“00”-“59”It is noticed to use RTC time here.
 <Agps mode>: A numeric to indicate whether to enable AGPS. AGPS is helpful to improve
the ratio to get GPS position successfully and reduce the time to get GPS position.
 0: Disable the AGPS function.
 1: Enable the AGPS function.
 <Sleep enable >: Enable or disable the sleep mode when charging.
 0: Disable the sleep mode when charging.
 1: Do not disable the sleep mode when charging.
Note:
For AGPS function, it is necessary to download AGPS file from the specified URL, so it is

TRACGL300AN001 - 20 -
GL300 @Tracker Air Interface Protocol

unavoidable to cost some data traffic for the AGPS function. At present, it takes about 10 KB data
traffic for the AGPS function each day.

The acknowledgement message of AT+GTCFG command:


 +ACK:GTCFG,
Example:
+ACK:GTCFG,1A0102,135790246811220,,0004,20100310172830,11F0$
Parameter Length (byte) Range/Format Default
Protocol version 6 XX0000 – XXFFFF,
X∈{'A'-'Z','0'-'9'}
Unique ID 15 IMEI

k
Device name 20
Serial number 4 0000 – FFFF

i n
Send time 14 YYYYMMDDHHMMSS

l l
Count number 4 0000 – FFFF

c
Tail character 1 $ $

3.2.5.

e t i
Non movement detection

u a
n
The AT+GTNMD command is used to configure the parameters for non movement detection.

Q fide
 AT+GTNMD=
Example:
AT+GTNMD=gl300,,3,2,3,,,,,,,,,,0005$

n
Parameter Length (byte) Range/Format Default
Password 4–6 ‘0’ – ‘9’, ‘a’ – ‘z’, ‘A’ – ‘Z’ gl300

o
mode 1 0-F 0
Non-movement <=3 1 – 255(×15sec) 2

C
duration
Movement duration <=2 1 – 50(×128ms) 3
Movement threshold 1 2–9 2
rest fix interval 5 5 – 86400sec 300
rest send interval 5 5 – 86400sec 300
pm rest threshold 1 2–9 2
pm motion threshold 1 2–9 3
Urc report 1 0|1 0
Reserved 0
Reserved 0
Reserved 0
Reserved 0
Serial number 4 0000 – FFFF
Tail character 1 $ $

TRACGL300AN001 - 21 -
GL300 @Tracker Air Interface Protocol

 <mode>: A hex numeric to determine how the function works. Each bit of the hex numeric
indicate different behavior that device could do. If the corresponding bit is 1, the device will
behave as the description. Otherwise, it won’t behave as the description.
Bit0(1): Suspend the report of FRI(including +RESP:GTGSM for FRI) and
Geo-Fence when it detects non-movement.
Bit1(2): Report the message +RESP:GTNMR to the backend server when it detects
non-movement.
Bit2(4): Report the message +RESP:GTNMR to the backend server when it detects
movement.
Bit3(8): Change the fix interval and send interval of FRI(including +RESP:GTGSM

k
for FRI) to <rest fix interval> and <rest send interval> when it detects non-movement. In the
case, it just modify the fix interval and send interval of FRI(including +RESP:GTGSM for

n
FRI) but not suspend the report of FRI(including +RESP:GTGSM for FRI) even if Bit0 is 1.

l i
 <Non-movement duration>: A time parameter to determine whether the device enters

l
non-movement status, i.e. if the motion sensor detects that the device keeps in non-movement

c a
for a period of time defined by <Non-movement duration>, the device will be considered as

e i
in non-movement status.

t
 <Movement duration>: A time parameter to determine whether the device enters movement

u n
status. If the motion sensor detects that the device keeps in movement for a period of time
defined by <Movement duration>, the device will be considered as in movement status.

Q fide
 <Movement threshold>: The threshold for the motion sensor to determine whether the device
is in movement. The less, the more likely to be treated as movement.
 <rest fix interval>: the fix interval for the report of FRI when the device is in rest state if Bit3
of <mode> is 1.
 <rest send interval>: the send interval for the report of FRI when the device is in rest state if

n
Bit3 of <mode> is 1.

o
<pm rest threshold>: The threshold for the EBK motion sensor to determine whether the
EBK enters non-movement status.
 <pm motion threshold>: The threshold for the EBK motion sensor to determine whether the

C
EBK enters movement status.
 <Urc report>: Enable or disable output sensor state through urc.
 0: Do not output the sensor’s state to UART.
 1: Output a URC to UART to indicate state changing. “SENSOR:REST” means state
changing from MOTION to REST. “SENSOR:MOTION” means state changing from
REST to MOTION.

The acknowledgement message of AT+GTNMD command:


 +ACK:GTNMD,
Example:
+ACK:GTNMD,1A0102,135790246811220,,0005,20100310172830,11F0$
Parameter Length (byte) Range/Format Default
Protocol version 6 XX0000 – XXFFFF,
X∈{'A'-'Z','0'-'9'}

TRACGL300AN001 - 22 -
GL300 @Tracker Air Interface Protocol

Unique ID 15 IMEI
Device name 20
Serial number 4 0000 – FFFF
Send time 14 YYYYMMDDHHMMSS
Count number 4 0000 – FFFF
Tail character 1 $ $

3.2.6. Time Adjustment

The command AT+GTTMA is used to adjust local time. If the GPS fixing is successful, the local

k
time will be automatically adjusted according to the GPS UTC time.

n
 AT+GTTMA=

l i l
Example:
AT+GTTMA=gl300,-,3,30,0,20090917203500,,,,,0006$

c a
Parameter Length (byte) Range/Format Default

e t i
Password 4–6 ‘0’ – ‘9’, ‘a’ – ‘z’, ‘A’ – ‘Z’ gl300
Sign 1 +|- +

u n
Hour Offset <=2 0 - 23 00
Minute Offset <=2 0 - 59 00

Q fide
Daylight Saving 1 0|1 0
UTC Time 14 YYYYMMDDHHMMSS
Reserved 0
Reserved 0

n
Reserved 0
Reserved 0

o
Serial number 4 0000 – FFFF
Tail character 1 $ $

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>: The configuration UTC time.

The acknowledgement message of AT+GTTMA command:


 +ACK:GTTMA,
Example:
+ACK:GTTMA,1A0102,135790246811220,,0007,20100310172830,11F0$
Parameter Length (byte) Range/Format Default

TRACGL300AN001 - 23 -
GL300 @Tracker Air Interface Protocol

Protocol version 6 XX0000 – XXFFFF,


X∈{'A'-'Z','0'-'9'}
Unique ID 15 IMEI
Device name 20
Serial number 4 0000 – FFFF
Send time 14 YYYYMMDDHHMMSS
Count number 4 0000 – FFFF
Tail character 1 $ $

3.2.7. Fixed Report Information

k
The command AT+GTFRI is used to configure the parameters of scheduled report.

i n
 AT+GTFRI=

l l
Example:

c a
AT+GTFRI=gl300,0,,,,,,,,,,,,,,,,,,,0007$

i
AT+GTFRI=gl300,1,1,,,0000,2359,60,60,,,1F,,,,,,,,,0007$

e t
Parameter Length Range/Format Default

u n
(byte)
Password 4–6 ‘0’ – ‘9’, ‘a’ – ‘z’, ‘A’ – ‘Z’ gl300

Q fide
Mode 1 0|1|2|3|4|5|6 0
Discard no fix 1 0|1 1
Reserved 0
Reserved 0
Begin time 4 HHMM 0000

n
End time 4 HHMM 0000

o
Check interval <=5 5 – 86400sec 180
Send interval <=5 5 – 86400sec 180

C
Ignition check interval <=5 5 – 86400sec 180
Ignition send interval <=5 5 – 86400sec 180
Report mask <=4 0000 – 007F 001F
Distance <=5 50 – 65535m 1000
Mileage <=5 50 – 65535m 1000
movement detect mode 1 0|1 0
movement speed <=3 1-999(km/h) 5
movement distance <=4 1-9999(m) 50
Movement send number 1 1-5 5
corner 3 0 - 180 0
Reserved 0
Serial number 4 0000 – FFFF
Tail character 1 $ $

TRACGL300AN001 - 24 -
GL300 @Tracker Air Interface Protocol

 <Mode>: The working mode of the fixed report.


 0: Disable fixed report function.
 1: Enable the scheduled timing report.
 2: Enable the scheduled distance report. Report each time the straight length that the
device moved has exceeded the specified distance. It ignores the detail path the
device has passed along. This function is invalid unless the GPS chip opens always.
Unit: Meter.
 3: Enable the scheduled mileage report. Report each time the path length that the
device moved has exceeded the specified length. It calculates the length of the detail
path the device has passed along. This function is invalid unless the GPS chip opens
always. Unit: Meter.

k
 4: Optimum Report. Simultaneously observe time interval and path length between
two adjacent reports. Report device position if the calculated time interval per

n
current time against the last report time is greater than the <Send Interval>, and the

l i
length of path between the current position and the last position is greater than the

l
<Mileage> setting. There is a precondition for the function. It is that <GPS on need>

c a
must be 0 (Never close GPS chip) or 2 (Never close GPS chip in ignition on state or

e i
movement state).

t
 5: Enable the scheduled timing report for GSM.

u
 6: Fixed Time or Mileage Report. Simultaneously observe both time interval and path

n
length between two adjacent reports. Report device position if the calculated time

Q fide
interval per current time against the last report time is greater than the <Send
Interval>, or the length of path between the current position and the last position is
greater than the <Mileage> setting.
 <Discard no fix>: 0 to report last known GPS position if there is no GPS fix, 1 to send
nothing if there is no GPS fix.

n
 <Begin time>: The start time of scheduled fixed report. The valid format is “HHMM”. The

o
value range of “HH” is “00”-“23”. The value range of “MM” is “00”-“59”. It is noticed to
use system time here.
 <End time>: The end time of scheduled fixed report. The valid format and range are same as

C
<Begin time>.
 <Check interval>: The interval time to fix GPS when the device attached vehicle is ignition
off, its value range is 5-86400 and the unit is second.
 <Send interval>: The period to send the position information when the device attached
vehicle is ignition off. The value range is 5-86400 and the unit is second.
 <Ignition check interval>: The interval time to fix GPS when the device attached vehicle is
ignition on, its value range is 5-86400 and the unit is second.
 <Ignition send interval>: The period to send the position information when the device
attached vehicle is ignition on. The value range is 5-86400 and the unit is second.
 <Report mask>: Bitwise report mask to configure the composition of GPS position
information for fixed report. If some bit is set as 1, the corresponding field will be filled in
the position related message. Otherwise, the field will be empty.
Bit0(0001): <speed>
Bit1(0002): <azimuth>

TRACGL300AN001 - 25 -
GL300 @Tracker Air Interface Protocol

Bit2(0004): <altitude>
Bit3(0008): GSM LAI and CI, including <mcc>, <mnc>, <lac>, <cellid>
Bit4(0010): <send time>
 <Distance>: the specified distance to send the position information when <Mode> is 2 and
this is valid only in the case that GPS chip keep opened always. Unit: meter.
 <Mileage>: the specified path length to send the position information when <Mode> is 3 and
this is valid only in the case that GPS chip keep opened always.. Unit: meter.
 <movement detect mode>: Enable or disable the movement detect function.
 0: Disable the movement detect function.
 1: Enable the movement detect function. If the movement detect function is enabled,
it will consider the device is non-movement if the speed according to the GPS fixing

k
result is slower than <movement speed> and the distance between the current GPS
point and the last moving GPS point is less than <movement distance>. After it

n
considers the device is non-movement, it will stop reporting FRI message after report

l i
FRI messages (speed field is shown as -1 in these messages.) for <movement send

l
number> times.

c a
 <movement speed>: The speed threshold of movement detect. The unit is km/h.

i
 <movement distance>: The distance threshold of movement detect. The unit is meter.

e t
 <movement send number>: According to the speed threshold and distance threshold, if the

u n
terminal is considered staying at one position, the terminal will send out at most this number
of reports before it moves again.

Q fide
 <corner>: A numeric to indicate whether to report +RESP:GTFRI message according to the
heading changing, i.e. the movement direction of the device changing.
0: disable the function, i.e. do not detect whether the device has changed its direction.
1 – 180: The angle used for deciding whether the device turn around. If the heading changing
is greater than the specified value, the device will be considered turning around. Unit: degree.

n
Note:
 Check interval

o
If <GPS On Need> was set as 1 or <GPS On Need> was set as 2 without ignition on,
The terminal has two modes to operate the GPS module according to the value of <Check

C
interval>:
 Mode 1: If the <Check interval> is more than 60 seconds, the terminal will close the
GPS part every time after GPS fixing finishes in order to save power.
 Mode 2: If the <Check interval> is less than 60 seconds, the terminal will never close
the GPS part in this mode.

Due to the maximum length limitation of the report message, it must be assured that: <Send
interval> / <Check Interval> <= 15. If exceed that limitation, the command is discarded and the
previous settings keep untouched.

If the terminal is in “Force on SMS Mode” (<Report mode> = 5) while the <Send interval> /
<Check Interval> > 1, the terminal will report only the last position in the fixed timing report,
because only one position could be filled in one single SMS message (160 bytes at most).

TRACGL300AN001 - 26 -
GL300 @Tracker Air Interface Protocol

 Action time range


 <Begin time> < <End time>: reports in the time period (begin time, end time) every day.
 <Begin time> > <End time>: reports starting from <Begin time> and stopping at <End
time> on the following day.
 <Begin time> = <End time>: reports on the whole day.

 Scheduled Report Mode


For the mode schedule distance report and scheduled mileage report and optimum report, <GPS on
need> must be 0 (Never close GPS chip) or 2 (Never close GPS chip in ignition on state or
movement state) for the function. For the mode scheduled timing report, it doesn’t care whether
GPS works always.

k
 Corner report
It is necessary to set <GPS on need> as 0 or 2 for detecting turning point. Because the detection

n
for turning point is based on heading in GPS position which is not so accurate, it could make

l i
mistake to detect turning point sometimes.

c al
The acknowledgement message of AT+GTFRI command:

i
 +ACK:GTFRI,

e t
Example:

u n
+ACK:GTFRI,1A0102,135790246811220,,0007,20100310172830,11F0$
Parameter Length (byte) Range/Format Default

Q fide
Protocol version 6 XX0000 – XXFFFF,
X∈{'A'-'Z','0'-'9'}
Unique ID 15 IMEI
Device name 20

n
Serial number 4 0000 – FFFF
Send time 14 YYYYMMDDHHMMSS

o
Count number 4 0000 – FFFF
Tail character 1 $ $

C
3.2.8. Geo-Fence Information

The command AT+GTGEO is used to configure the parameters of Geo-Fence. Geo-Fence is a


virtual perimeter on a geographic area using a location-based service, so that when the geofencing
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.

 AT+GTGEO=
Example:
AT+GTGEO=gl300,0,3,101.412248,21.187891,1000,600,,,,,,,,,0008$
Parameter Length (byte) Range/Format Default
Password 4–6 ‘0’ – ‘9’, ‘a’ – ‘z’, ‘A’ – ‘Z’ gl300
GEO ID 1 0–4
TRACGL300AN001 - 27 -
GL300 @Tracker Air Interface Protocol

Mode 1 0–3 0
Longitude <=11 (-)xxx.xxxxxx
Latitude <=10 (-)xx.xxxxxx
Radius <=7 50 – 6000000m 50
Check interval <=5 0|30 – 86400sec 0
State mode 1 0|1 0
Reserved 0
Reserved 0
Reserved 0
Reserved 0
Reserved 0

k
Reserved 0

n
Reserved 0

i
Serial number 4 0000 – FFFF

l l
Tail character 1 $ $

c i a

e
<GEO ID>: A numeric to identify the Geo-Fence.

t
 <Mode>: A numeric which indicates when to report the notification to the backend server

u n
based on the following:
 0: Disable the Geo-Fence on the specified GEO ID.

Q fide
 1: Reports when enters the Geo-Fence.
 2: Reports when leaves the Geo-Fence.
 3: Reports when enters or leaves the Geo-Fence.
 <Longitude>: The longitude of a point which is defined as the center of the Geo-Fence
circular region. The format is “(-)xxx.xxxxxx” and the value range is from “-180.000000” to

n
“180.000000”. The unit is degree. West longitude is defined as negative starting with minus

o
“-” and east longitude is defined as positive without “+”.
 <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

C
“90.000000”. The unit is degree. South Latitude is defined as negative starting with minus
“-” and north Latitude is defined as positive without “+”.
 <Radius>: The radius of the Geo-Fence circular region. The value range is (50-6000000) and
the unit is meter.
 <Check interval>: The interval of GPS checking for the Geo-Fence alarm.
 <state mode>:
 0: It should report when get the state first time.
 1: It doesn’t report until the state changes.
Note:
If the parameter <Check interval> is set as 0, <Mode> will be set as 0 automatically (To
Geo-Fence 0, <Mode> will be restored at first and it could be used later when switch on
Geo-Fence 0 via Function Key), because the terminal doesn’t know when to check Geo-Fence if
the parameter <Check interval> is 0.

The acknowledgement message of AT+GTGEO command:


TRACGL300AN001 - 28 -
GL300 @Tracker Air Interface Protocol

 +ACK:GTGEO,
Example:
+ACK:GTGEO,1A0102,135790246811220,,0,0008,20100310172830,11F0$
Parameter Length (byte) Range/Format Default
Protocol version 6 XX0000 – XXFFFF,
X∈{'A'-'Z','0'-'9'}
Unique ID 15 IMEI
Device name 20
GEO ID 1 0–4
Serial number 4 0000 – FFFF
Send time 14 YYYYMMDDHHMMSS

k
Count number 4 0000 – FFFF

n
Tail character 1 $ $

c l i l
3.2.9. Speed Alarm

e i a
The AT+GTSPD command is used to configure speed alarm of the device. Based on the working

t
mode set, the device will report speed alarm when its speed is outside or inside of a predefined

u n
range.

Q fide
 AT+GTSPD=
Example:
AT+GTSPD=gl300,1,5,40,30,60,,,,,,,,,,,,,,,,0009$
AT+GTSPD=gl300,2,0,80,30,60,,,,,,,,,,,,,,,,0009$

n
Parameter Length (byte) Range/Format Default
Password 4–6 ‘0’ – ‘9’, ‘a’ – ‘z’, ‘A’ – ‘Z’ gl300

o
Mode 1 0|1|2 0
Min speed <=3 0 – 400km/h 0

C
Max speed <=3 0 – 400km/h 0
Duration <=4 15 – 3600sec 60
Send interval <=4 0|5 – 3600sec 300
Reserved 0
Reserved 0
Reserved 0
Reserved 0
Reserved 0
Reserved 0
Reserved 0
Reserved 0
Reserved 0
Reserved 0
Reserved 0

TRACGL300AN001 - 29 -
GL300 @Tracker Air Interface Protocol

Reserved 0
Reserved 0
Reserved 0
Reserved 0
Serial number 4 0000 – FFFF
Tail character 1 $ $

 <Mode>: A numeric to indicate the working mode of speed alarm.


 0: Disable speed alarm.
 1: Enable speed alarm. If the current speed is within the speed range defined by min
speed and max speed, a speed alarm is sent.

k
 2: Enable speed alarm. If the current speed is outside the speed range defined by min

n
speed and max speed, a speed alarm is sent.

i
 <Min speed>: The lower limit of the speed range.

l l
 <Max speed>: The upper limit of the speed range.

c
 <Duration>: According to the working mode, if the speed satisfies the specified speed range

i a
and maintains a period of time defined by <Duration>, the speed alarm will be triggered.

e t
 <Send interval>: After the speed alarm is triggered, the speed alarm message is sent every
interval time, but when the send interval is set to 0, the speed alarm message will be sent only

u n
once.

Q fide
Note:
The parameter <Duration> and <Send interval> are invalid when GPS doesn’t open always. When
GPS doesn’t open always, it will report speed alarm immediately if it detects the speed of the
terminal is out of the allowed speed range.

n
The acknowledgement message of AT+GTSPD command:
 +ACK:GTSPD,

o
Example:
+ACK:GTSPD,1A0102,135790246811220,,0009,20100310172830,11F0$

C
Parameter Length (byte) Range/Format Default
Protocol version 6 XX0000 – XXFFFF,
X∈{'A'-'Z','0'-'9'}
Unique ID 15 IMEI
Device name 20
Serial number 4 0000 – FFFF
Send time 14 YYYYMMDDHHMMSS
Count number 4 0000 – FFFF
Tail character 1 $ $

3.2.10. Function Key Setting

The AT+GTFKS command is used to configure the function of the power key and the function
key.
TRACGL300AN001 - 30 -
GL300 @Tracker Air Interface Protocol

 AT+GTFKS=
Example:
AT+GTFKS=gl300,1,,1,1,1,,,ffff$
Parameter Length (byte) Range/Format Default
Password 4–6 ‘0’ – ‘9’, ‘a’ – ‘z’, ‘A’ – ‘Z’ gl300
Power key mode 1 0|1|2 1
Full power up 1 0|1 1
Function key mode 1 0|1|2|3 3
Power key ind 0 0|1 0
Function key ind 0 0|1 0
Reserved 0

k
Reserved 0

n
Serial number 4 0000 – FFFF

i
Tail character 1 $ $

c l l

a
<Power key mode>: A numeric to indicate the working mode of the power key.

i
 0: Press power key will not power down the device.

e t
 1: Press power key will power down the device.

u
 2: Press power key after long press for 1.5 seconds, it will work as SOS mode.

n
 <Full power up>: A numeric to indicate whether the terminal powers on completely after the

Q fide
terminal was power on because of charger inserted.
 0: Do not power on the terminal completely. And the terminal will only work on
charging.
 1: Power on the terminal completely. The terminal will work normally as power on
by power key long pressed.

n
 <Function key mode>: The working mode for the function key operation..
 0: Ignore the function key operation.

o
 1: Geo-Fence mode. Switch on/off the Geo-Fence ID 0 when the function key is long
pressed. And after long press the function key, the terminal will report the message

C
+RESP:GTSWG to inform to switch on or off Geo-Fence ID 0 via this operation.
 2: Geo-Fence in current position. Switch on/off the Geo-Fence 0 when the function
key is long pressed and use the current position as the centre of Geo-Fence 0 when
switch on the Geo Fence 0 via the function key. After long press the function key, the
terminal will report the message +RESP:GTSWG immediately. And if this operation
is expected to switch on Geo-Fence ID 0, the terminal will start GPS fixing to get the
current position as the centre of Geo-Fence ID 0. After GPS fixing finishes, it will
report the message +RESP:GTGCR to inform the result of GPS fixing and whether
Geo-Fence ID 0 was switched on successfully.
 3: SOS mode. After long press for 3 seconds, the device will report the current
position according to the result of the latest GPS fixing and then start GPS fixing.
After the GPS fixing finishes or timeout, the device will report the SOS message
according the result of the GPS fixing.
 <Power key ind>: A numeric to indicate the working mode of the motor for power key.
 0: Disable drive the motor when the power key is long pressed
TRACGL300AN001 - 31 -
GL300 @Tracker Air Interface Protocol

 1: Drive the motor vibration when the power key is long pressed to power off
 <Function key ind>: A numeric to indicate the working mode of the motor for function key.
 0: Disable drive the motor when the function key is long pressed
 1: Drive the motor vibration when the function key is long pressed

The acknowledgement message of AT+GTFKS command:


 +ACK:GTFKS,
Example:
+ACK:GTFKS,1A0102,135790246811220,,000A,20100310172830,11F0$
Parameter Length (byte) Range/Format Default
Protocol version 6 XX0000 – XXFFFF,

k
X∈{'A'-'Z','0'-'9'}
Unique ID 15 IMEI

i n
Device name 20

l l
Serial number 4 0000 – FFFF

c
Send time 14 YYYYMMDDHHMMSS

i a
Count number 4 0000 – FFFF

e t
Tail character 1 $ $

u n
3.2.11. Real Time Operation

Q fide
The AT+GTRTO command is used to retrieve information from the terminal or control the
terminal.
 AT+GTRTO=

n
Example:
AT+GTRTO=gl300,0,,,,,,000B$

o
Parameter Length (byte) Range/Format Default
Password 4–6 ‘0’ – ‘9’, ‘a’ – ‘z’, ‘A’ – ‘Z’ gl300

C
Sub command 1 0–F
Single Configuration 3
Command
Reserved 0
Reserved 0
Reserved 0
Reserved 0
Serial number 4 0000 – FFFF
Tail character 1 $ $

 <Sub command>: A numeric to indicate the sub command to execute.


0: (GPS): Request GPS related information, including setting of <GPS on need>,
<Report items mask>, <Report mask> of fixed report, GPS antenna type, GPS
antenna status and the last known time of successful GPS fixing.

TRACGL300AN001 - 32 -
GL300 @Tracker Air Interface Protocol

1: (RTL): Request the device to report its current position.


2: (READ): Request the device to report its entire configuration.
3: (REBOOT): Reboot the device remotely.
4: (RESET): Reset all parameters to factory default except parameter of AT+GTBSI,
AT+GTSRI, AT+GTTMA.
5: (PWROFF): Power off the device remotely.
6: (CID): Request the device to report the ICCID of the installed SIM card.
7: (CSQ): Request the device to report the current GSM signal level.
8: (VER): Request the device to report version information including the device type,
the firmware version and the hardware version.
9: (BAT): Request the device to report power supply related information including the

k
external power supply status, current voltage of the battery, the battery charging
status and the working mode of LED.

n
A: (TMZ): Request the device to report the time zone setting.

l i
B: (INF): Read the device information report function. The corresponding information

l
will be reported via the message +RESP:GTINF.

c a
C: (RESERVED)

e i
D: (RESERVED)

t
E: (GSV): Request the device to report the GPS fix level.

u n
F: (GSM): Request the device to report the cells’ information.
 <Single Configuration Command>: Get the specified command configuration of the terminal

Q fide
via the message +RESP:GTALS. For example, it is OK to get the configuration of
AT+GTCFG by the command “AT+GTRTO=gl300,2,CFG,,,,,000F$”. NOTE: This
parameter is available only when <Sub Command> is set to 2. If the parameter is default, the
terminal will report all configuration via the message +RESP:GTALL.

n
The acknowledgement message of AT+GTRTO command:
 +ACK:GTRTO,

o
Example:

C
+ACK:GTRTO,1A0102,135790246811220,,GPS,000B,20100310172830,11F0$
Parameter Length (byte) Range/Format Default
Protocol version 6 XX0000 – XXFFFF,
X∈{'A'-'Z','0'-'9'}
Unique ID 15 IMEI
Device name 20
Sub command <=6 Sub command string
Serial number 4 0000 – FFFF
Send time 14 YYYYMMDDHHMMSS
Count number 4 0000 – FFFF
Tail character 1 $ $

3.2.12. White Call List Configuration

The AT+GTWLT command is used to set white call list table.


TRACGL300AN001 - 33 -
GL300 @Tracker Air Interface Protocol

 AT+GTWLT=
Example:
AT+GTWLT=gl300,1,1,2,13813888888,13913999999,,,,,000C$
Parameter Length(byte) Range/format Default
password 4~6 ‘0’-‘9’,’a’-‘z’,’A’-‘Z’ gl300
call filter 1 0|1|2 1
mobile start 1 1-10
mobile end 1 1-10
white number list <=20*10
reserved 0
reserved 0
reserved 0

k
reserved 0

n
Serial number 4 0000 – FFFF

i
Tail character 1 $

c l l
 <call filter>: A numeric to indicate whether to filter the incoming call according to <white

i a
number list> and <direct number list> before it tries to send google link SMS to the incoming

e t
number.
 0: Do not return a google link SMS to incoming number no matter what the parameter

u n
<location by call> was set and no matter whether the incoming number is in the
<white number list> or <direct number list>.

Q fide
 1: Do not filter the incoming call. It will return a google link SMS to the incoming
number as long as the parameter <location by call> was set as 1.
 2: Filter the incoming call. If the incoming number isn’t in <white number list> or
<direct number list>, it won’t return a google link SMS to the incoming number even

n
if the parameter <location by call> was set as 1.
 <mobile start>: A numeric to indicate the first index of the white call number to input. For

o
example, if it is 1, it will update the white call list from the 1st one. If it is empty, it should
not include <white number list> later.

C
 <mobile end>: A numeric to indicate the last index of the white call number to input. For
example, if it is 2, it will update the white call list until the 2nd one. If it is empty, it should
not include <white number list> later.
 <white number list>: A phone number list. It could include several phone numbers. And two
close phone numbers are separated with ",". The number of the phone number in the list is up
to the parameter <mobile start> and <mobile end>. For example, if <mobile start> is 1 and
<mobile end> is 2, the <white number list> should include 2 phone numbers and the two
numbers are separated with ",".

The acknowledgment message of the AT+GTWLT command:


 +ACK:GTWLT,
Example:
+ACK:GTWLT,1A0102, 135790246811220,,000C,20101029085505,0025$
Parameter Length (byte) Range/Format Default

TRACGL300AN001 - 34 -
GL300 @Tracker Air Interface Protocol

Protocol version 6 XX0000 – XXFFFF,


X∈{'A'-'Z','0'-'9'}
Unique ID 15 IMEI
Device name 20
Serial number 4 0000 – FFFF
Send time 14 YYYYMMDDHHMMSS
Count number 4 0000 – FFFF
Tail character 1 $ $

Note:
It is necessary to make sure the total size of the command is not greater than 160 if it is sent via

k
SMS.

l i n
3.2.13. Google link SMS configuration

c l
The AT+GTGLM command is used to configure whether to send SMS with google link for SOS

i a
and GEO event.

e t

u
AT+GTGLM=

n
Example:

Q fide
AT+GTGLM=gl300,1,1,2,13813888888,13913999999,,,,,000D$
Parameter Length(byte) Range/format Default
password 4~8 ‘0’-‘9’,’a’-‘z’,’A’-‘Z’ gl300
google mode 1 0|1|2 0
mobile start 1 1-3
mobile end 1 1-3

n
direct number list <=20*3

o
reserved 0
reserved 0

C
reserved 0
reserved 0
Serial number 4 0000 – FFFF
Tail character 1 $

 <google mode>: A numeric to indicate whether to send a SMS with google link to the number
in <direct number list> for SOS and GEO event.
 0: Do not send a SMS with google link to the number is in the <direct number list>
for SOS and GEO event.
 1: Send a SMS with google link to the number is in the <direct number list> for SOS
and GEO event and include the terminal name in the google hyperlink.
 2: Send a SMS with google link to the number is in the <direct number list> for SOS
and GEO event and do not include the terminal name in the google hyperlink.
 <mobile start>: A numeric to indicate the first index of the direct number to input. For
example, if it is 1, it will update the direct number list from the 1st one. If it is empty, it

TRACGL300AN001 - 35 -
GL300 @Tracker Air Interface Protocol

should not include <direct number list> later.


 <mobile end>: A numeric to indicate the last index of the direct number to input. For example,
if it is 2, it will update the direct number list until the 2nd one. If it is empty, it should not
include <direct number list> later.
 <direct number list>: A phone number list. It could include several phone numbers. And two
close phone numbers are separated with ",". The number of the phone number in the list is up
to the parameter <mobile start> and <mobile end>. For example, if <mobile start> is 1 and is
<mobile end> 2, the <direct number list> should include 2 phone numbers and the two
numbers are separated by with ",".

The acknowledgment message of the AT+GTGLM command:

k
 +ACK:GTGLM,
Example:

i n
+ACK:GTGLM,1A0102, 135790246811220,,000D,20101029085505,0025$

l l
Parameter Length (byte) Range/Format Default
Protocol version 6 XX0000 – XXFFFF,

c a
X∈{'A'-'Z','0'-'9'}

e t i
Unique ID 15 IMEI
Device name 20

u n
Serial number 4 0000 – FFFF
Send time 14 YYYYMMDDHHMMSS

Q fide
Count number 4 0000 – FFFF
Tail character 1 $ $

3.2.14. Auto unlock SIM-PIN

n
The AT+GTPIN command is used to configure whether to automatically unlock the PIN of the

o
SIM card in the device.

C
 AT+GTPIN=
Example:
AT+GTPIN=gl300,1,1234,1,,,,,000E$
Parameter Length(byte) Range/format Default
password 4~6 ‘0’-‘9’,’a’-‘z’,’A’-‘Z’ gl300
auto unlock PIN 1 0|1 1
PIN 4-8 ‘0’-‘9’
PIN checking 1 0|1 0
reserved 0
reserved 0
reserved 0
reserved 0
Serial number 4 0000 – FFFF
Tail character 1 $
 <auto unlock PIN>: A numeric to indicate whether to unlock the SIM-PIN for the device.

TRACGL300AN001 - 36 -
GL300 @Tracker Air Interface Protocol

 0: Do not unlock SIM-PIN automatically.


 1: Each time the device powers on, it will detect whether the SIM card is locked with
a PIN. If it is locked, the device will unlock the PIN automatically for one time.
 <PIN>: The PIN code which is used when unlocks PIN automatically. If it is empty, the PIN
code saved in the device will be cleared.
 <PIN checking>: A numeric to indicate whether to lock the device with SIM-PIN.
 0: Do not lock the SIM-PIN.
 1: Lock the SIM-PIN.

The acknowledgment message of the AT+GTPIN command:


 +ACK:GTPIN,

k
Example:
+ACK:GTPIN,1A0102, 135790246811220,,000E,20101029085505,0027$

i n
Parameter Length (byte) Range/Format Default

l l
Protocol version 6 XX0000 – XXFFFF,
X∈{'A'-'Z','0'-'9'}

c a
Unique ID 15 IMEI

e t i
Device name 20
Serial number 4 0000 – FFFF

u n
Send time 14 YYYYMMDDHHMMSS
Count number 4 0000 – FFFF

Q fide
Tail character 1 $ $

3.2.15. Digital Input Port Settings

n
 AT+GTDIS

o
Example:
AT+GTDIS=gl300,1,1,5,,,,,,0010$
Parameter Length(byte) Range/format Default

C
password 4~6 ‘0’-‘9’,’a’-‘z’,’A’-‘Z’ gl300
Input ID 1 1 1
Mode 1 0|1|2|3 0
Debounce time <=2 0-20 (×10ms) 5
reserved 0
reserved 0
reserved 0
reserved 0
reserved 0
Serial number 4 0000 – FFFF
Tail character 1 $

 <Input ID>: The ID of the digital input. It is always 1. If the filed is empty, the device will
ignore the following settings about the digital input 1, i.e. change nothing about the digital
input 1.
TRACGL300AN001 - 37 -
GL300 @Tracker Air Interface Protocol

 <Mode>: A numeric to check whether to enable the digital input.


 0: Disable the digital input, i.e. ignore the status changing of the digital input.
 1: Enable the digital input. If the status of the input change, the device will report the
message +RESP:GTDIS to the backend server to inform the latest status.
 2: If the status of the input is changed to 0, the device will disable the sleep mode. If
the status of the input is changed to 1, the device will enable the sleep mode.
 3: If the status of the input is changed to 0, it will trigger the SOS event.
 <Debounce time>: The time for debouncing.

The acknowledgment message of the AT+GTDIS command:


 +ACK:GTDIS,

k
Example:
+ACK:GTDIS,1A0102,135790246811220,,0010,20101029085505,0028$

i n
Parameter Length (byte) Range/Format Default

l l
Protocol version 6 XX0000 – XXFFFF,
X∈{'A'-'Z','0'-'9'}

c a
Unique ID 15 IMEI

e t i
Device name 20
Serial number 4 0000 – FFFF

u n
Send time 14 YYYYMMDDHHMMSS
Count number 4 0000 – FFFF

Q fide
Tail character 1 $ $

3.2.16. Protocol watchdog

n
The AT+GTDOG command is used to reboot the device in a time based manner or upon ignition.

o
This helps the device avoid working in an exceptional status for a long time. Besides these two
automatically reboot method, the device also supports to use the digital input to trigger the reboot

C
manually.

 AT+GTDOG=
Example:
AT+GTDOG=gl300,1,,1,0130,,1,1,,,,,0011$
AT+GTDOG=gl300,2,30,,,,1,1,,,,,0011$
Parameter Length (byte) Range/Format Default
Password 4–6 ‘0’ – ‘9’, ‘a’ – ‘z’, ‘A’ – ‘Z’ gl300
Mode 1 0|1|2 0
Ignition Frequency <=3 10-120 60
Interval <=2 1-30 30
Time 4 HHMM 0200
Reserved 0
Report Before Reboot 1 0|1 1

TRACGL300AN001 - 38 -
GL300 @Tracker Air Interface Protocol

Input ID 1 0|1 0
Unit 1 0|1 0
Gsm interval 4 0|5-1440min 60min
Pdp interval 4 0|5-1440min 60min
Reserved 0
Serial number 4 0000 – FFFF
Tail character 1 $ $
 <Mode>: Working mode.
 0: Disable this function
 1: Reboot periodically according to the <Interval> and <Time> setting.
 2: Reboot when ignition on.

k
 <Ignition Frequency>: When the working mode is 2, if the time interval between two

n
adjacent ignitions is greater than the specified value, the device will automatically reboot

i
upon ignition on.

l l
 <Interval>: The interval to reboot the device.

c
 <Time>: At what time to perform the reboot operation when <Interval> is met.

i a
 <Report Before Reboot>: Whether to report the +RESP:GTDOG message before reboot. 0

e t
means no report, 1 to report. If this is enabled, the device will make a real-time location

u
before sending the message in order to send it with the current location information.

n
 <Input ID>: ID of the digital input port which is used to trigger the manually reboot. 0 means do not use

Q fide
manual reboot. Only port 1 is supported.
 <Unit>: Unit.
 0: Unit is day.
 1: Unit is hour.
 <Gsm interval>: The time in minute before rebooting the terminal when the GSM is not

n
registered.
 <Pdp interval>: The time in minute before rebooting the terminal if it is failed to activate

o
PDP context.

C
The acknowledgment message of the AT+GTDOG command:
 +ACK:GTDOG,
Example:
+ACK:GTDOG,1A0102,135790246811220,,0011,20101029085505,0028$
Parameter Length (byte) Range/Format Default
Protocol version 6 XX0000 – XXFFFF,
X∈{'A'-'Z','0'-'9'}
Unique ID 15 IMEI
Device name 20
Serial number 4 0000 – FFFF
Send time 14 YYYYMMDDHHMMSS
Count number 4 0000 – FFFF
Tail character 1 $ $

TRACGL300AN001 - 39 -
GL300 @Tracker Air Interface Protocol

3.2.17. Data transfer between UART and backend server

The AT+GTDAT command is used to transfer the data between UART and the backend server.

 AT+GTDAT=
Example:
AT+GTDAT=gl300,0,,data needs to be sent,0,,,,0016$
AT+GTDAT=gl300,1,,config command to the CAN bus device,1,,,,0016$
Parameter Length (byte) Range/Format Default
Password 4–6 ‘0’ – ‘9’, ‘a’ – ‘z’, ‘A’ – ‘Z’ gl300
Command Type 1 0|1 0

k
Reserved 0

n
Data <=100 ASCII code

i
Need ack 1 0|1 0

l l
Reserved 0

c
Reserved 0

i a
Reserved 0

e t
Serial number 4 0000 – FFFF

u
Tail character 1 $ $

Q fide n
 <Command Type>: A numeric to indicate the direction of the transferred data.
 0: The data should be transferred from UART to the backend server.
 1: The data should be transferred from the backend server to UART.
 <Data>: The data to be transferred. It should be printable ASCII string.
 <Need ack>: A numeric to indicate whether the device should reply +ACK message to the

n
backend server.
 0: Do not send +ACK:GTDAT to the backend server.

o
 1: Send +ACK:GTDAT to the backend server.

C
The acknowledgment message of the AT+GTDAT command:
 +ACK:GTDAT
Example:
+ACK:GTDAT,1A0102,135790246811220,,0011,20101029085505,0028$
Parameter Length (byte) Range/Format Default
Protocol version 6 XX0000 – XXFFFF,
X∈{'A'-'Z','0'-'9'}
Unique ID 15 IMEI
Device name 20
Serial number 4 0000 – FFFF
Send time 14 YYYYMMDDHHMMSS
Count number 4 0000 – FFFF
Tail character 1 $ $

TRACGL300AN001 - 40 -
GL300 @Tracker Air Interface Protocol

3.2.18. Network Select

The AT+GTNTS command is used to set network when in low signal.

 AT+ GTNTS =
Example:
AT+GTNTS=gl300,1,20,2,46001,,,,,FFFF$
Parameter Length (byte) Range/Format Default
Password 4–6 ‘0’ – ‘9’, ‘a’ – ‘z’, ‘A’ – ‘Z’ gl300
enable 1 0|1 0
Rssi threshold 3 0 – 35 30

k
Interval 3 0 – 300min 10

n
Oper1 10

i
Oper2 10

l l
Oper3 10

c
GSM interval 3 0 – 300min 10

i a
Reserved 0

e t
Serial number 4 0000 – FFFF

u
Tail character 1 $ $

n
 <Enable>: Enable or disable “NTS” based functionality.

Q fide
 0: Disable
 1: Enable
 <Rssi threshold>: The threshold of the CSQ value.
 <Interval>: The interval time to change to another opetor.
 <Oper1>: The first network it will select when under threshold over interval time.

n
 <Oper2>: The second network it will select when under threshold over interval time.

o
<Oper3>: The third network it will select when under threshold over interval time.
 <GSM Interval>: The time in minute before changing the operator without GSM network.

C
The acknowledgment message of the AT+ GTNTS command.
 +ACK:GTNTS
Example:
+ACK:GTNTS,1A0102,135790246811220,,0011,20101029085505,0028$
Parameter Length (byte) Range/Format Default
Protocol version 6 XX0000 – XXFFFF,
X∈{'A'-'Z','0'-'9'}
Unique ID 15 IMEI
Device name 20
Serial number 4 0000 – FFFF
Send time 14 YYYYMMDDHHMMSS
Count number 4 0000 – FFFF
Tail character 1 $ $

TRACGL300AN001 - 41 -
GL300 @Tracker Air Interface Protocol

3.2.19. 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 LAC, empty
Cell ID, empty MCC and empty MNC in all the report messages except for +RESP:GTSOS.

 AT+GTOWH=
Example:

k
AT+GTOWH=gl300,1,1F,0900,1200,1300,1730,,,1,,,,,,,,,0012$
Parameter Length(byte) Range/Format Default

i n
Password 4–6 '0' – '9' 'a' – 'z' 'A' – 'Z' gl300

l l
Mode 1 0|1|2|3 0
Day of Work <=2 0 – 7F 1F

c a
Working Hours Start1 4 HHMM 0900

e t i
Working Hours End1 4 HHMM 1200
Working Hours Start2 4 HHMM 1300

u n
Working Hours End2 4 HHMM 1800
Reserved 0

Q fide
Reserved 0
Digital Input ID 1 0|1 0
Reserved 0
Reserved 0

n
Reserved 0
Reserved 0

o
Reserved 0
Reserved 0

C
Reserved 0
Reserved 0
Serial Number 4 0000 – FFFF
Tail Character 1 $ $

 <Mode>: Working mode.


 0: Disable this function.
 1: Manual mode.Use the specified digital input (refer to the parameter <Digital Input
ID>) to control whether to check working hours. After the digital input is enabled, if
the device finds it is outside of the working hours, it will hide the location
information. Otherwise report normally.
 2: Full manual mode. Use the specified digital input (refer to the parameter <Digital
Input ID>) to control whether to hide the location information. It hides the location
information when the input is enabled and reports normally when the input is

TRACGL300AN001 - 42 -
GL300 @Tracker Air Interface Protocol

disabled.
 3: 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 it is outside of the working hours, the device will 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
 Bit 3 for Thursday
 Bit 4 for Friday

k
 Bit 5 for Saturday
 Bit 6 for Sunday

n
For each bit, 0 means off day, 1 means working day.

l i
 <Working Hours Start1>, <Working Hours End1>: The first period of the working hours in a

l
day.

c a
 <Working Hours Start2>, <Working Hours End2>: The second period of the working hours in

e i
a day.

t
 <Digital Input ID>: The input ID used to trigger this function when mode is 1 or 2. Only

u n
digital input port 1 is supported.

Q fide
The acknowledgment message of AT+GTOWH command:
 +ACK:GTOWH,
Example:
+ACK:GTOWH,1A0102,135790246811220,,0012,20090214093254,11F0$
Parameter Length(byte) Range/Format Default

n
Protocol Version 6 XX0000 – XXFFFF,

o
X∈{‘A’ – ‘Z’,’0’ – ‘9’}
Unique ID 15 IMEI

C
Device Name <=20 '0' – '9' 'a' – 'z' 'A' – 'Z' '-' '_'
Serial Number 4 0000 – FFFF
Send Time 14 YYYYMMDDHHMMSS
Count Number 4 0000 – FFFF
Tail Character 1 $ $

3.2.20. Temperature Alarm

The AT+GTTEM command is used to configure temperature alarm of the device. Based on the
working mode set, the device will report temperature alarm when its temperature is outside or
inside of a predefined range.

 AT+GTTEM=
Example:

TRACGL300AN001 - 43 -
GL300 @Tracker Air Interface Protocol

AT+GTTEM=gl300,1,-05,10,15,30,,,,,,,000E$
Parameter Length(byte Range/Format Default
Password 4–6 '0' – '9' 'a' – 'z' 'A' – 'Z' gl300
mode 1 0|1|2|3 0
Min temperature <=3 -20℃-60℃ 0
Max temperature <=3 -20℃-60℃ 0
Duration <=4 0 – 3600sec 60
Send interval <=4 0|5 – 3600sec 300
Reserved 0
Reserved 0
Reserved 0

k
Reserved 0

n
Reserved 0

i
Reserved 0

l l
Serial Number 4 0000 – FFFF

c a
Tail Character 1 $ $

e t i
 <mode>: A numeric to indicate the working mode of temperature alarm.

u
 0: Disable this function.

n
 1: Report the alarm message +RESP:GTTEM when the current temperature is

Q fide
lower than the lowest temperature defined by <Min temperature>.
 2: Report the alarm message +RESP:GTTEM when the current temperature is
inside of the temperature range.
 3: Report the alarm message +RESP:GTTEM when the current temperature is
higher than the highest temperature defined by <Max temperature>.

n
 <Min temperature>: The lower limit of the temperature range

o
<Max temperature>: The upper limit of the temperature range
 <Duration>: According to the working mode, if the temperature is in the specified
temperature range and maintains a period of time defined by <Duration>, the temperature

C
alarm will be triggered.
 <Send interval>: After the temperature alarm is triggered, the temperature alarm message
will be sent each time of <Send interval>, but when the send interval is set to 0, the
temperature alarm message will be sent only once.

The acknowledgment message of AT+GTTEM command:


 +ACK:GTTEM,
Example:
+ACK:GTTEM, 1A0102,135790246811220,,000E,20090214093254, 000E$
Parameter Length(byte) Range/Format Default
Protocol Version 6 XX0000 – XXFFFF,
X∈{‘A’ – ‘Z’,’0’ – ‘9’}
Unique ID 15 IMEI
Device Name <=20 '0' – '9' 'a' – 'z' 'A' – 'Z' '-' '_'
TRACGL300AN001 - 44 -
GL300 @Tracker Air Interface Protocol

Serial Number 4 0000 – FFFF


Send Time 14 YYYYMMDDHHMMSS
Count Number 4 0000 – FFFF
Tail Character 1 $ $

3.2.21. Store Command String

The AT+GTCMD command is used to store the commands which will be used by the command
AT+GTUDF.
 AT+GTCMD=
Example:

k
AT+GTCMD=gl300,1,1,AT+GTRTO=gl300,0,,,,,,000B$,,,,,0005$

n
Parameter Length (byte) Range/Format Default

i
Password 4–6 ‘0’ – ‘9’, ‘a’ – ‘z’, ‘A’ – ‘Z’ gl300

l l
mode 1 0-1 0

c
Store cmd id 3 0 – 31

i a
Command string 200 AT command

e t
Reserved 0

u
Reserved 0

n
Reserved 0

Q fide
Reserved 0
Serial number 4 0000 – FFFF
Tail character 1 $ $
 <Mode>:The working mode of the store command string.
 0: Delete the stored command.

n
 1: Add the stored command.

o
 <Store cmd id>: A numeric to identify the stored command.
 <Command string>: the whole content of the stored command.

C
The acknowledgement message of AT+GTCMD command:
 +ACK:GTCMD
Example:
+ACK:GTCMD,1A0102,135790246811220,,0005,20100310172830,11F0$
Parameter Length (byte) Range/Format Default
Protocol version 6 XX0000 – XXFFFF,
X∈{'A'-'Z','0'-'9'}
Unique ID 15 IMEI
Device name 20
Serial number 4 0000 – FFFF
Send time 14 YYYYMMDDHHMMSS
Count number 4 0000 – FFFF
Tail character 1 $ $

TRACGL300AN001 - 45 -
GL300 @Tracker Air Interface Protocol

3.2.22. User Defined Function

The AT+GTUDF command is used to bind input event and the stored commands. The input
events will trigger the corresponding stored commands..
 AT+GTUDF=
Example:
AT+GTUDF=gl300,1,1,FFFFFFFF,30,,,FFFFFFFF,1,,,,,0005$
Parameter Length (byte) Range/Format Default
Password 4–6 ‘0’ – ‘9’, ‘a’ – ‘z’, ‘A’ – ‘Z’ gl300
mode 1 0-2 0
Group id 2 0 – 31

k
Input id mask 16 0-FFFFFFFFFFFFFFFF

n
Debounce time 5 0-86400(s) 0

i
Reserved

l l
Reserved

c
Stocmd id mask 16 0-FFFFFFFF

i a
Stocmd ack 1 0|1 0

e t
Reserved

u
Reserved

n
Reserved

Q fide
Reserved
Serial number 4 0000 – FFFF
Tail character 1 $ $

 <Mode>: The working mode of the user defined fuction.

n
 0: Disable the group.

o
 1: Enable the group.
 2: Delete the group.

C
<Group id>: A numeric to identify the group of input events and stored commands to
execute.
 <Input id mask>: The bitwise mask to indicate the input events that the group cares about...
Bit0(00000001): select id1
Bit1(00000002): select id2
Bit2(00000004): select id3
Bit3(00000008): select id4
For example:
Bit(00000003): select id1,id2
Bit(00000017): select id1,id2,id3,id5
ID Bit Item to Mask
1 Bit 0 Power on finished
2 Bit 1 Ignition on
3 Bit 2 Ignition off
4 Bit 3 The GPRS network is attached
TRACGL300AN001 - 46 -
GL300 @Tracker Air Interface Protocol

5 Bit 4 The GPRS network is not attached


6 Bit 5 The GSM network registered
7 Bit 6 The GSM network not registered
8 Bit 7 Network roaming
9 Bit 8 Network non roaming
10 Bit 9 SIM card is locked
11 Bit 10 GPS is opened
12 Bit 11 GPS is closed
13 Bit 12 The device is stationary
14 Bit 13 The device is moving
15 Bit 14 External charge inserted

k
16 Bit 15 No external charge.

n
17 Bit 16 The device is charging

i
The device is not charging

l
18 Bit 17

l
19 Bit 18 External battery inserted

c a
20 Bit 19 No external battery

e i
21 Bit 20 Digital input 1 is low

t
22 Bit 21 Digital input 1 is high

u n
23 Bit 22 SIM card is inserted.
24 Bit 23 SIM card is not inserted

Q fide
25 Bit 24 Reserved
26 Bit 25 Reserved
27 Bit 26 Inside the Geo 0
28 Bit 27 Outside the Geo 0
Inside the Geo 1

n
29 Bit 28
30 Bit 29 Outside the Geo 1

o
31 Bit 30 Inside the Geo 2
32 Bit 31 Outside the Geo 2

C
33 Bit 32 Inside the Geo 3
34 Bit 33 Outside the Geo 3
35 Bit 34 Inside the Geo 4
36 Bit 35 Outside the Geo 4
37 Bit 36 Inside the speed range
38 Bit 37 Outside the speed range
39 Bit 38 Messages need to be sent
40 Bit 39 No messages need to be sent
41 Bit 40 SOS event

 <Debounce time>: The debounce time for input events before executing the specified stored
commands.
 <Stocmd id mask>: The bitwise of the stored commands which will be executed after the
state of the group becomes TRUE (i.e. all cared input events happen.).

TRACGL300AN001 - 47 -
GL300 @Tracker Air Interface Protocol

 <Stocmd ack>: A numeric to indicate whether to return acknowledgement message after the
stored commands are executed.
 0: Do not send acknowledgement message when execute the stored command.
 1: Send acknowledgement message when execute the stored command.
Note:
The maximum number of the stored commands to execute in a group is five

The acknowledgement message of AT+GTUDF command:


 +ACK:GTUDF
Example:
+ACK:GTUDF,1A0102,135790246811220,,0005,20100310172830,11F0$

k
Parameter Length (byte) Range/Format Default
Protocol version 6 XX0000 – XXFFFF,

i n
X∈{'A'-'Z','0'-'9'}

l l
Unique ID 15 IMEI

c
Device name 20

a
Serial number 4 0000 – FFFF

e t i
Send time 14 YYYYMMDDHHMMSS
Count number 4 0000 – FFFF

u n
Tail character 1 $ $

Q fide
3.2.23. Update configuration over the air

The AT+GTUPC command is used to send control command.


 AT+GTUPC=

n
Example:
AT+GTUPC=gl300, 0,10,0,0,168,http://www.queclink.com/configure.ini,,,,,0001$

o
Parameter Length(byte) Range/Format Default value
password 4~6 ‘0’-‘9’,’a’-‘z’,’A’-‘Z’ gl300

C
max download retry 1 0–3 0
download timeout <=2 5 – 30 min 10
download protocol 1 0 0
report enable 1 0|1 0
update interval 1 0 – 8760 0
download URL <=100 URL
reserved 0
reserved 0
reserved 0
reserved 0
serial number 4 0000-FFFF
tail character 1 $ $

 <password>: the valid character of password is ‘0’-9’, ‘a’-‘z’, ‘A’-‘Z’. The default value is
TRACGL300AN001 - 48 -
GL300 @Tracker Air Interface Protocol

“gl300”.
 <max download retry>: specifies the maximum time of retrying to download the configuration
file upon downloading failure.
 <download timeout>: specifies the expiration timeout of one single downloading. If the
downloading expires, it is considered to be failure.
 <download protocol>: the protocol used to download the file. Only HTTP is supported now.
Set to 0.
 <report enable>: A numeric to indicate whether to report the message +RESP:GTUPC to
indicate the configuration was updated over the air.
 0: Do not report the message +RESP:GTUPC
 1: Report the message +RESP:GTUPC

k
 <update interval>: The time interval in hour for updating the configuration over the air.
 <download URL>: specifies the URL to download the configuration file. If the URL is end

n
with “/” which means this is just a path without any file, the unit will add <imei>.ini as the

l i
default configuration file name at the end of URL.

c al
The acknowledgement message of AT+GTUPC command:

i
 +ACK:GTUPC

e t
Example:

u n
+ACK:GTUPC, 1A0102,135790246811220,,0005,20100310172830,11F0$
Parameter Length (byte) Range/Format Default

Q fide
Protocol version 6 XX0000 – XXFFFF,
X∈{'A'-'Z','0'-'9'}
Unique ID 15 IMEI
Device name 20

n
Serial number 4 0000 – FFFF
Send time 14 YYYYMMDDHHMMSS

o
Count number 4 0000 – FFFF
Tail character 1 $ $

Notice:

C
1> If the <download URL> is end with “/” which means the URL is just a path
without file name, the unit will add <imie>.ini as the file name to complete the
URL.If it is larger than 100 will be returned error.

3.2.24. 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.

TRACGL300AN001 - 49 -
GL300 @Tracker Air Interface Protocol

 AT+GTJDC=
Example:
AT+GTJDC= gl300,1,25,,5,10,10,,,,,,,0016$

Parameter Length(byte) Range/Format Default

Password 4–6 '0' – '9' 'a' – 'z' 'A' – 'Z' gl300

Mode 1 0|1|2 0

Signal Threshold <=3 0 – 31 25

Reserved 0

k
Jamming Cell Number
<=2 0-99 5
Threshold

i n
Enter Jamming Timer

l
<=3 0-300 sec 10

l
Threshold

c a
Quit Jamming Timer
<=4 0-3600sec 10

i
Threshold

e t
Reserved 0

u n
Reserved 0

Q fide
Reserved 0

Reserved 0

Reserved 0

n
Reserved 0

o
Serial Number 4 0000 – FFFF

Tail Character 1 $ $

C
 <Mode>: Working mode.
 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
TRACGL300AN001 - 50 -
GL300 @Tracker Air Interface Protocol

<Quit Jamming Timer Threshold> parameter to trigger the quit Jamming event.

The acknowledgment message of AT+GTJDC command:


 +ACK:GTJDC
Example:
+ACK:GTJDC,0A0102,135790246811220,,0016,20090214093254,11F0$

Parameter Length(byte) Range/Format Default

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
Serial Number 4 0000 – FFFF

c a
Send Time 14 YYYYMMDDHHMMSS

e t i
Count Number 4 0000 – FFFF

u
Tail Character 1 $ $

Q fide n
o n
C
TRACGL300AN001 - 51 -
GL300 @Tracker Air Interface Protocol

3.3. Report

3.3.1. Position Related Report

3.3.1.1. General Position Report

 +RESP:GTFRI: report of AT+GTFRI


 +RESP:GTGEO: report of AT+GTGEO
 +RESP:GTSPD: report of AT+GTSPD
 +RESP:GTSOS: report after long press the function if the function key is enabled and the

k
mode is SOS mode.

n
+RESP:GTRTL: report of AT+GTRTO-RTL

i
 +RESP:GTPNL: The first location after the device powers on.

l l
 +RESP:GTNMR: non movement is detected by motion sensor, according to the setting of

c
AT+GTNMD

i a
 +RESP:GTDIS: the status of digital input is detected being changed if the parameter

e t
<Enable> is set as 1 in the command AT+GTDIS,
 +RESP:GTDOG: the protocol watchdog reboot message.

u n
 +RESP:GTIGL:The location message for ignition on and ignition off.

Q fide
Example:
+RESP:GTFRI,1A0102,135790246811220,,0,0,1,1,4.3,92,70.0,121.354335,31.222073,20090
214013254,0460,0000,18d8,6141,00,,20090214093254,11F0$

n
+RESP:GTFRI,1A0102,135790246811220,,0,0,2,1,4.3,92,70.0,121.354335,31.222073,20090
214013254,0460,0000,18d8,6141,00,0,4.3,92,70.0,121.354335,31.222073,20090101000000,04

o
60,0000,18d8,6141,00,,20090214093254,11F0$

C
+RESP:GTGEO,1A0102,135790246811220,,0,0,1,1,4.3,92,70.0,121.354335,31.222073,2009
0214013254,0460,0000,18d8,6141,00,,20090214093254,11F0$

+RESP:GTSPD,1A0102,135790246811220,,0,0,1,1,4.3,92,70.0,121.354335,31.222073,20090
214013254,0460,0000,18d8,6141,00,,20090214093254,11F0$

+RESP:GTSOS,1A0102,135790246811220,,0,0,1,1,4.3,92,70.0,121.354335,31.222073,20090
214013254,0460,0000,18d8,6141,00,,20090214093254,11F0$

+RESP:GTRTL,1A0102,135790246811220,,0,0,1,1,4.3,92,70.0,121.354335,31.222073,20090
214013254,0460,0000,18d8,6141,00,,20090214093254,11F0$

+RESP:GTPNL,1A0102,135790246811220,,0,0,1,1,4.3,92,70.0,121.354335,31.222073,20090
214013254,0460,0000,18d8,6141,00,,20090214093254,11F0$

TRACGL300AN001 - 52 -
GL300 @Tracker Air Interface Protocol

+RESP:GTNMR,1A0102,135790246811220,,0,0,1,1,4.3,92,70.0,121.354335,31.222073,2009
0214013254,0460,0000,18d8,6141,00,,20090214093254,11F0$

+RESP:GTDIS,1A0102,135790246811220,,0,0,1,1,4.3,92,70.0,121.354335,31.222073,20090
214013254,0460,0000,18d8,6141,00,,20090214093254,11F0$

+RESP:GTDOG,1A0102,135790246811220,,0,0,1,1,4.3,92,70.0,121.354335,31.222073,2009
0214013254,0460,0000,18d8,6141,00,2000.0,20090214093254,11F0$

+RESP:GTIGL,1A0102,867844000125073,,,00,1,5,,,,117.201362,31.832724,2012082103203

k
7,,,,,,,,000C$
Parameter Length (byte) Range/Format Default

i n
Protocol version 6 XX0000 – XXFFFF,

l l
X∈{'A'-'Z','0'-'9' '-' '_'}

c
Unique ID 15 IMEI

a
Device name 20

e t i
Report ID 1 0–4
Report type 1 0|1

u n
Number <=2 0 – 15

Q fide
GPS accuracy <=2 0|1 – 50
Speed <=5 0.0 – 999.9km/h
Azimuth <=3 0 – 359
Altitude <=8 (-)xxxxx.x m
Longitude <=11 (-)xxx.xxxxxx

n
Latitude <=10 (-)xx.xxxxxx
GPS UTC time 14 YYYYMMDDHHMMSS

o
MCC 4 0XXX
MNC 4 0XXX

C
LAC 4 XXXX
Cell ID 4 XXXX
Odo mileage 9 0.0 – 4294967.0Km
battery percentage 3 0-100
Send time 14 YYYYMMDDHHMMSS
Count number 4 0000 – FFFF
Tail character 1 $ $

 <Report ID>: ID of Geo-Fence in +RESP:GTGEO, ID of input id in +RESP:GTDIS,0 for


other reports.
 <Report type>: type of the report for +RESP:GTGEO and +RESP:GTSPD and
+RESP:GTNMR, 0 for other reports.
 For +RESP:GTFRI
0: This is a common scheduled position report.
TRACGL300AN001 - 53 -
GL300 @Tracker Air Interface Protocol

1: This is a turning point.


 For +RESP:GTGEO
0: exit the corresponding Geo-Fence.
1: enter the corresponding Geo-Fence.
 For +RESP:GTSPD
0: Outside the speed range.
1: Inside the speed range.
 For +RESP:GTNMR
0: The state of the device changed from motion to rest.
1: The state of the device changed from rest to motion.
 In the +RESP:GTDIS report message generated by the digital input

k
0: The current logical status of the input port is low level
1: The current logical status of the input port is high level

n
 In the message of ignition on and ignition off message +RESP:GTIGL

l i
0: the engine is ignition on.

l
1: the engine is ignition off.

c a
 For +RESP:GTDOG

e i
0: Reboot periodically according to the <Interval> and <Time> setting or ignition on or

t
<Input ID> cases to reboot.

u n
1: GPRS network registered unsuccessful cases to reboot
2: Without GSM signal cases to reboot

Q fide
 <Number>: Number of points in one report message. According to the setting of fixed
report, there could be up to 15 points in one +RESP:GTFRI report. For other reports, this is
always 1. If there are more than 1 point in the report, information from <GPS accuracy> to
<Odo mileage> is repeated for each point.
 <GPS accuracy>: The HDOP defined in NMEA0183. The range of value is 1 – 50. The

n
smaller the value, the higher the precision. Different from NMEA0183, 0 here means no fix,

o
while GPS accuracy between 0 and 1 is set to 1.
 <Speed>: The speed from GPS.
 <Azimuth> The azimuth from GPS.

C
 <Altitude>: The height above sea level from GPS.
 <Longitude>: The longitude of the current position. The format is “(-)xxx.xxxxxx” and the
value range is from “-180.000000” to “180.000000”. The unit is degree. West longitude is
defined as negative starting with minus “-” and east longitude is defined as positive without
“+”.
 <Latitude>: The latitude of the current position. 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 “+”.
 <GPS UTC time>: UTC time from GPS.
 <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.
 <Odo mileage>: The total mileage in the position defined by <Latitude> and <Longitude>. If

TRACGL300AN001 - 54 -
GL300 @Tracker Air Interface Protocol

<ODO enable> was set as 0 in the command AT+GTCFG, the field will be empty.
 <battery percentage>: The current volume of the battery in percentage.

3.3.1.2. Location by Call Report

 +RESP:GTLBC:
Example:
+RESP:GTLBC,1A0102,135790246811220,,+8613800000000,1,4.3,92,70.0,121.354335,31.2
22073,20090214013254,0460,0000,18d8,6141,00,,20090214093254,11F0$
Parameter Length (byte) Range/Format Default
Protocol version 6 XX0000 – XXFFFF,

k
X∈{'A'-'Z','0'-'9'}
Unique ID 15 IMEI

n
Device name 20

l i l
Call number <=20 phone number
GPS accuracy <=2 0|1 – 50

c a
Speed <=5 0.0 – 999.9km/h

e t i
Azimuth <=3 0 – 359
Altitude <=8 ±XXXXX.X m

u n
Longitude <=11 ±XXX.XXXXXX
Latitude <=10 ±XX.XXXXXX

Q fide
GPS UTC time 14 YYYYMMDDHHMMSS
MCC 4 0XXX
MNC 4 0XXX
LAC 4 XXXX

n
Cell ID 4 XXXX
Odo mileage 9 0.0 – 4294967.0Km

o
Reserved2 0
Send time 14 YYYYMMDDHHMMSS

C
Count number 4 0000 – FFFF
Tail character 1 $ $

 <Call number>: the phone number of the incoming call which initiates this report.

3.3.1.3. Location as centre of Geo-Fence

If function key mode was set as 2 and long press function key to switch on Geo-Fence 0, the
terminal will start GPS fixing to get the current position as the centre of Geo-Fence 0. And after
GPS fixing finishes, the terminal will report the message +RESP:GTGCR.

 +RESP:GTGCR:
Example:
+RESP:GTGCR,1A0102,135790246811220,,3,50,180,2,0.4,296,-5.4,121.391055,31.164473,2

TRACGL300AN001 - 55 -
GL300 @Tracker Air Interface Protocol

0100714104934,0460,0000,1878,0873,00,,20100714104934,000C$
Parameter Length (byte) Range/Format Default
Protocol version 6 XX0000 – XXFFFF,
X∈{'A'-'Z','0'-'9'}
Unique ID 15 IMEI
Device name 20
Geo mode 1 0|1|2|3
Geo radius <=7 50 – 6000000m
Geo check interval <=5 0|30 – 86400sec
GPS accuracy <=2 0|1 – 50
Speed <=5 0.0 – 999.9km/h

k
Azimuth <=3 0 – 359

n
Altitude <=8 ±XXXXX.X m

i
Longitude <=11 ±XXX.XXXXXX

l l
Latitude <=10 ±XX.XXXXXX

c a
GPS UTC time 14 YYYYMMDDHHMMSS

i
MCC 4 0XXX

e t
MNC 4 0XXX

u n
LAC 4 XXXX
Cell ID 4 XXXX

Q fide
Odo mileage 9 0.0 – 4294967.0Km
Reserved2 0
Send time 14 YYYYMMDDHHMMSS
Count number 4 0000 – FFFF
Tail character 1 $ $

o n
 <Geo mode>: the new mode of Geo-Fence 0. Please refer to the parameter <Mode> in the
command AT+GTGEO.

C
 <Geo radius>: the radius of Geo-Fence 0. Please refer to the parameter <Radius> in the
command AT+GTGEO.
 <Geo check interval>: the check interval of Geo-Fence 0. Please refer to the parameter
<Check interval> in the command AT+GTGEO.
 <Longitude>: The longitude of the current position. If it is successful to fix position this time,
this longitude will replace the longitude of the centre of Geo-Fence 0.
 <Latitude>: The latitude of the current position. If it is successful to fix position this time,
this latitude will replace the latitude of the centre of Geo-Fence 0.

3.3.2. Device Information Report

 +RESP:GTINF:
Example:
+RESP:GTINF,1A0102,135790246811220,,41,898600810906F8048812,16,0,0,0,,4.10,0,0,0,0

TRACGL300AN001 - 56 -
GL300 @Tracker Air Interface Protocol

,20100214013254,,,,+0800,0,20100214093254,11F0$
Parameter Length (byte) Range/Format Default
Protocol version 6 XX0000 – XXFFFF,
X∈{'A'-'Z','0'-'9'}
Unique ID 15 IMEI
Device name 20
State 2 21|22|41|42
ICCID 20
CSQ RSSI <=2 0 – 31|99
CSQ BER <=2 0 – 7|99
External power supply 1 0|1

k
Mileage <=9 0.0 – 4294967.0Km

n
Reserved 0

i
Battery voltage <=4 0.0 – 4.50V

l l
Charging 1 0|1

c a
LED on 1 0|1|2

i
GPS on need 1 0|1|2|3

e t
GPS antenna type 1 0

u n
GPS antenna state 1 0
Last GPS fix UTC 14 YYYYMMDDHHMMSS

Q fide
time
battery percentage 3 0-100
Flash type 1 0|1
Temperature <=3 XX℃
Reserved 0

n
Reserved 0

o
Send time 14 YYYYMMDDHHMMSS
Count number 4 0000 – FFFF

C
Tail character 1 $ $

 <State>: The current motion state of the device.


 21: The device attached vehicle is ignition on and motionless.
 22: The device attached vehicle is ignition on and moving.
 41: The device is motionless without ignition on.
 42: The device is moving without ignition on.
 <ICCID>: The ICCID of the installed SIM card.
 <CSQ RSSI>: The GSM signal strength level.
 <CSQ BER>: The quality of the GSM signal.
 <External power supply>: Whether the external power supply is connected.
 0: Not connected
 1: Connected
 <Mileage>: The total mileage is base on <ODO Initial mileage> which is a parameter in
AT+GTCFG.
TRACGL300AN001 - 57 -
GL300 @Tracker Air Interface Protocol

 <Battery voltage>: The voltage of the battery.


 <Charging>: Whether the battery is charging when the external power supply is connected.
 0: Not charging
 1: Charging
 <LED on>: The setting of <LED on> in AT+GTCFG.
 <GPS on need>: The setting of <GPS on need> in AT+GTCFG.
 <GPS antenna type>: A numeric to indicate which GPS antenna is working now.
 0: inside GPS antenna
 <GPS antenna state>: the status of the working GPS antenna.
 0: The antenna is working
 <Last GPS fix UTC time>: The UTC time of the latest successful GPS fixing.

k
 <Temperature>: The temperature of the device.
 <Flash type>: A numeric to indicate what the type of flash is.

n
 0: SST flash

l i
 1: NMX flash

3.3.3.

c
Report for Querying

e i al
t
These are the report of real time querying by command AT+GTRTO.

u n
 +RESP:GTGPS: The report for real time operation GPS

Q fide
Example:
+RESP:GTGPS,1A0102,135790246811220,,0,1F,1F,0,0,20100214013254,20100214093254,
11F0$
Parameter Length (byte) Range/Format Default

n
Protocol version 6 XX0000 – XXFFFF,
X∈{'A'-'Z','0'-'9'}

o
Unique ID 15 IMEI
Device name 20

C
GPS on need 1 0|1|2|3
GPS fix delay 3 5 – 60sec
GPS antenna type 1 0
Report items mask <=4 0000 – FFFF
FRI report mask <=4 0000 – FFFF
GPS antenna state 1 0
Last GPS fix UTC 14 YYYYMMDDHHMMSS
time
Send time 14 YYYYMMDDHHMMSS
Count number 4 0000 – FFFF
Tail character 1 $ $
 <FRI report mask>: The setting of <Report mask> in AT+GTFRI.

 +RESP:GTALL: The report for real time operation READ


TRACGL300AN001 - 58 -
GL300 @Tracker Air Interface Protocol

Example:
+RESP:GTALL,1A0102,860599000000448,GL300,BSI,cmnet,,,,,,,SRI,2,,1,116.228.146.250
,8161,192.0.0.0,0,+8618600126107,5,0,,,,,CFG,gl300,GL300,1,0.8,0,5,003F,0,,0FFF,0,1,1,30
0,1,0,20491231235959,1,0,,NMD,0,2,3,2,300,300,2,3,0,,,,,TMZ,+0000,0,FRI,3,0,,,0000,0000,
30,30,180,180,001F,1000,100,0,5,50,5,0,,GEO,0,0,0,0,50,0,0,,,,,,,,1,0,0,0,50,0,0,,,,,,,,2,0,0,0,50
,0,0,,,,,,,,3,0,0,0,50,0,0,,,,,,,,4,0,0,0,50,0,0,,,,,,,,SPD,0,0,0,60,300,,,,,,,,,,,,,,,,FKS,1,1,3,0,0,,,WLT
,1,,,,,,,,,,,,,,,,,,,GLM,0,,,,,,,,,,,,PIN,1,,0,,,,,DIS,1,0,5,,,,,,DOG,0,60,30,0200,,1,0,0,60,60,,NTS,0,
30,10,,,,10,,OWH,0,1f,0900,1200,1300,1800,,,0,,,,,,,,,TEM,0,0,0,60,300,,,,,,,UPC,0,10,0,0,168,
http://www.queclink.com/configure.ini,,,,,JDC, 1,25,,5,10,10,,,,,,,20130123034509,02AE$
Parameter Length (byte) Range/Format Default
Protocol version 6 XX0000 – XXFFFF,

k
X∈{'A'-'Z','0'-'9'}
Unique ID 15 IMEI

i n
Device name 20

l l
BSI 3 BSI BSI

c
APN <=40

i a
APN user name <=30

e t
APN password <=30

u
Reserved 0

n
Reserved 0

Q fide
Reserved 0
Reserved 0
SRI 3 SRI SRI
Report mode 1 0–6 0
Reserved 0

n
Buffer enable 1 0|1 1

o
Main server IP/domain <=60
name
Main server port <=5 0 – 65535 0

C
Backup server IP <=15 192.0.0.0
Backup server port <=5 0 – 65535 0
SMS gateway <=20
Heartbeat interval <=3 0|10 – 360min 0
SACK enable 1 0|1 0
SMS ACK Enable 1 0|1 0
Quick Link Enable 1 0|1 0
Reserved 0
Reserved 0
CFG 3 CFG CFG
New password 4–6 ‘0’ – ‘9’, ‘a’ – ‘z’, ‘A’ – ‘Z’ gl300
Device name 20 GL300
ODO enable 1 0|1 0

TRACGL300AN001 - 59 -
GL300 @Tracker Air Interface Protocol

ODO mileage <=9 0.0 – 4294967.0Km 0


GPS on need 1 0|1|2|3 1
GPS fix delay 3 5 – 60sec 5
Report items mask <=4 0000 – FFFF 1F
Gsm report 1 0|1|2|3 0
Reserved 0
Event mask 4 0000-FFFF FFF
EPB mode 1 0|1 0
LED on 1 0|1|2 1
Info report enable 1 0|1 1
Info report interval <=5 30 – 86400sec 300

k
Location by call 1 0|1 1

n
Expiry enable 1 0|1 0

i
Expiry time 14 YYYYMMDDHHMMSS

l
204912312

l
35959

c a
Agps mode 1 0|1 0

i
Sleep enable 1 0|1 0

e t
Reserved 0

u n
NMD 3 NMD NMD
mode 1 0-F

Q fide
Non-movement <=3 1 – 255(×15sec) 2
duration
Movement duration <=2 1 – 50(×100ms) 3
Movement threshold 1 2–9 2
rest fix interval 5 5 – 86400sec 300

n
rest send interval 5 5 – 86400sec 300

o
pm rest threshold 1 2–9 2
pm motion threshold 1 2–9 3

C
Urc report 1 0|1 0
Reserved 0
Reserved 0
Reserved 0
Reserved 0
TMZ 3 TMZ TMZ
Time Zone 5 -|+HHMM
Daylight Saving 1 0|1
FRI 3 FRI FRI
Mode 1 0|1|2|3|4|5|6 0
Discard no fix 1 0|1 1
Reserved 0
Reserved 0
Begin time 4 HHMM 0000

TRACGL300AN001 - 60 -
GL300 @Tracker Air Interface Protocol

End time 4 HHMM 0000


Check interval <=5 5 – 86400sec 180
Send interval <=5 5 – 86400sec 180
Ignition Check interval <=5 5 – 86400sec 180
Ignition Send interval <=5 5 – 86400sec 180
Report mask <=4 0000 – FFFF 1F
Distance <=5 50 – 65535m 1000
Mileage <=5 50 – 65535m 1000
movement detect mode 1 0|1 0
movement speed <=3 1-999(km/h) 5
movement distance <=4 1-9999(m) 50

k
movement send 1 1-5 5

n
number

i
corner 3 0 - 180 0

l l
Reserved 0

c a
GEO 3 GEO GEO

i
GEO ID0 1 0 0

e t
Mode 1 0–3 0

u n
Longitude <=11 ±xxx.xxxxxx 0.00000
Latitude <=10 ±xx.xxxxxx 0.00000

Q fide
Radius <=7 50 – 6000000m 50
Check interval <=5 0|30 – 86400sec 0
State mode 1 0|1 0
Reserved 0
Reserved 0

n
Reserved 0

o
Reserved 0
Reserved 0

C
Reserved 0
Reserved 0
GEO ID1 1 1 1
Mode 1 0–3 0
Longitude <=11 ±xxx.xxxxxx 0.00000
Latitude <=10 ±xx.xxxxxx 0.00000
Radius <=7 50 – 6000000m 50
Check interval <=5 0|30 – 86400sec 0
State mode 1 0|1 0
Reserved 0
Reserved 0
Reserved 0
Reserved 0
Reserved 0

TRACGL300AN001 - 61 -
GL300 @Tracker Air Interface Protocol

Reserved 0
Reserved 0
GEO ID2 1 2 2
Mode 1 0–3 0
Longitude <=11 ±xxx.xxxxxx 0.00000
Latitude <=10 ±xx.xxxxxx 0.00000
Radius <=7 50 – 6000000m 50
Check interval <=5 0|30 – 86400sec 0
State mode 1 0|1 0
Reserved 0
Reserved 0

k
Reserved 0

n
Reserved 0

i
Reserved 0

l l
Reserved 0

c a
Reserved 0

e i
GEO ID3 1 3 3

t
Mode 1 0–3 0

u n
Longitude <=11 ±xxx.xxxxxx 0.00000
Latitude <=10 ±xx.xxxxxx 0.00000

Q fide
Radius <=7 50 – 6000000m 50
Check interval <=5 0|30 – 86400sec 0
State mode 1 0|1 0
Reserved 0
Reserved 0

n
Reserved 0

o
Reserved 0
Reserved 0

C
Reserved 0
Reserved 0
GEO ID4 1 4 4
Mode 1 0–3 0
Longitude <=11 ±xxx.xxxxxx 0.00000
Latitude <=10 ±xx.xxxxxx 0.00000
Radius <=7 50 – 6000000m 50
Check interval <=5 0|30 – 86400sec 0
State mode 1 0|1 0
Reserved 0
Reserved 0
Reserved 0
Reserved 0
Reserved 0

TRACGL300AN001 - 62 -
GL300 @Tracker Air Interface Protocol

Reserved 0
Reserved 0
SPD 3 SPD SPD
Mode 1 0|1|2 0
Min speed <=3 0 – 400km/h 0
Max speed <=3 0 – 400km/h 0
Duration <=4 15 – 3600sec 60
Send interval <=4 30 – 3600sec 300
Reserved 0
Reserved 0
Reserved 0

k
Reserved 0

n
Reserved 0

i
Reserved 0

l l
Reserved 0

c a
Reserved 0

e i
Reserved 0

t
Reserved 0

u n
Reserved 0
Reserved 0

Q fide
Reserved 0
Reserved 0
Reserved 0
FKS 3 FKS FKS
Power key mode 1 0|1|2 1

n
Full power up 1 0|1 1

o
Function key mode 1 0|1|2|3 3
Power key ind 0 0|1 0

C
Function key ind 0 0|1 0
Reserved 0
Reserved 0
WLT 3 WLT WLT
call filter 1 0|1|2 1
white number 20
white number 20
white number 20
white number 20
white number 20
white number 20
white number 20
white number 20
white number 20

TRACGL300AN001 - 63 -
GL300 @Tracker Air Interface Protocol

white number 20
Reserved 0
Reserved 0
Reserved 0
Reserved 0
Reserved 0
Reserved 0
Reserved 0
Reserved 0
GLM 3 GLM GLM
google mode 1 0|1|2 0

k
direct number 20

n
direct number 20

i
direct number 20

l l
Reserved 0

c a
Reserved 0

e i
Reserved 0

t
Reserved 0

u n
Reserved 0
Reserved 0

Q fide
Reserved 0
Reserved 0
PIN 3 PIN PIN
auto unlock PIN 1 0|1 1
PIN 4-8 ‘0’-‘9’

n
PIN checking 1 0|1 0

o
Reserved 0
Reserved 0

C
Reserved 0
Reserved 0
DIS 3 DIS DIS
Input ID 1 1 1
Enable 1 0|1 0
Debounce time <=2 1-20 (×10ms) 5
Reserved 0
Reserved 0
Reserved 0
Reserved 0
Reserved 0
DOG 3 DOG DOG
Mode 1 0|1|2 0
Ignition Frequency <=3 10-120 60

TRACGL300AN001 - 64 -
GL300 @Tracker Air Interface Protocol

Interval <=2 1-30 days 30


Time 4 HHMM 0200
Reserved 0
Report Before Reboot 1 0|1 1
Input ID 1 0|1 0
Unit 1 0|1 0
Gsm interval 4 0|5-1440 60
Pdp interval 4 0|5-1440 60
Reserved 0
NTS 3 NTS NTS
enable 1 0|1 0

k
Rssi threhold 3 0 – 35 30

n
Interval 3 0 – 300min 10

i
Oper1 10

l l
Oper2 10

c a
Oper3 10

e i
Gsm interval 3 0 – 300min 10

t
Reserved 0

u n
OWH 3 OWH OWH
Mode 1 0|1|2|3 0

Q fide
Day of Work <=2 0 – 7F 1F
Working Hours Start1 4 HHMM 0900
Working Hours End1 4 HHMM 1200
Working Hours Start2 4 HHMM 1300
Working Hours End2 4 HHMM 1800

n
Reserved 0

o
Reserved 0
Digital Input ID 1 0|1 0

C
Reserved 0
Reserved 0
Reserved 0
Reserved 0
Reserved 0
Reserved 0
Reserved 0
Reserved 0
TEM 3 TEM TEM
mode 1 0|1|2|3 0
Min temperature <=3 -20℃-60℃ 0
Max temperature <=3 -20℃-60℃ 0
Duration <=4 0 – 3600sec 60
Send interval <=4 0|5 – 3600sec 300

TRACGL300AN001 - 65 -
GL300 @Tracker Air Interface Protocol

Reserved 0
Reserved 0
Reserved 0
Reserved 0
Reserved 0
Reserved 0
UPC 3 UPC UPC
max download retry 1 0–3 0
download timeout <=2 5 – 30 min 10
download protocol 1 0 0
report enable 1 0|1 0

k
update interval 1 0 – 8760 0

n
download URL <=100 URL

i
reserved 0

l l
reserved 0

c a
reserved 0

e i
reserved 0

t
JDC 3 JDC JDC

u n
Mode 1 0|1|2 0
Signal Threshold <=3 0 – 31 25

Q fide
Reserved 0
Jamming Cell Number
<=2 0-99 5
Threshold
Enter Jamming Timer
<=3 0-300 sec 10
Threshold

n
Quit Jamming Timer
<=4 0-3600sec 10

o
Threshold
Reserved 0

C
Reserved 0
Reserved 0
Reserved 0
Reserved 0
Reserved 0
Send time 14 YYYYMMDDHHMMSS
Count number 4 0000 – FFFF
Tail character 1 $ $

 No matter what report mode is set, +RESP:GTALL is only reported through GPRS. If the
current report mode is forcing on SMS, +RESP:GTALL will be reported via TCP short
connection.

 +RESP:GTCID: The report for real time operation CID

TRACGL300AN001 - 66 -
GL300 @Tracker Air Interface Protocol

Example:
+RESP:GTCID,1A0102,135790246811220,,898600810906F8048812,20100214093254,11F0
$
Parameter Length (byte) Range/Format Default
Protocol version 6 XX0000 – XXFFFF,
X∈{'A'-'Z','0'-'9'}
Unique ID 15 IMEI
Device name 20
ICCID 20
Send time 14 YYYYMMDDHHMMSS
Count number 4 0000 – FFFF

k
Tail character 1 $ $

l i n l
 +RESP:GTCSQ: The report for real time operation CSQ

c a
Example:

i
+RESP:GTCSQ,1A0102,135790246811220,,16,0,20100214093254,11F0$

e t
Parameter Length (byte) Range/Format Default

u n
Protocol version 6 XX0000 – XXFFFF,
X∈{'A'-'Z','0'-'9'}

Q fide
Unique ID 15 IMEI
Device name 20
CSQ RSSI <=2 0 – 31 | 99
CSQ BER <=2 0 – 7 | 99
Send time 14 YYYYMMDDHHMMSS

n
Count number 4 0000 – FFFF

o
Tail character 1 $ $

C
 +RESP:GTVER: The report for real time operation VER
Example:
+RESP:GTVER,1A0102,135790246811220,,GL300,0100,0101,20100214093254,11F0$
Parameter Length (byte) Range/Format Default
Protocol version 6 XX0000 – XXFFFF,
X∈{'A'-'Z','0'-'9'}
Unique ID 15 IMEI
Device name 20
Device type 10 ‘0’ – ‘9’, ‘a’ – ‘z’, ‘A’ – ‘Z’ GL300
Firmware version 4 0000 – FFFF
Hardware version 4 0000 – FFFF
Send time 14 YYYYMMDDHHMMSS
Count number 4 0000 – FFFF

TRACGL300AN001 - 67 -
GL300 @Tracker Air Interface Protocol

Tail character 1 $ $

 <Device type>: A string represents the type of the device.


 <Firmware version>: The firmware version. The first two characters point out the main
version and the last two characters point out the subsidiary version. For example: 010A
means the version 1.10
 <Hardware version>: The hardware version. The first two characters point out the main
version and the last two characters point out the subsidiary version. For example: 010A
means the version 1.10

 +RESP:GTBAT: The report for real time operation BAT

k
Example:
+RESP:GTBAT,1A0102,135790246811220,,0,,,4.10,0,1,20100214093254,11F0$

i n
Parameter Length (byte) Range/Format Default

l l
Protocol version 6 XX0000 – XXFFFF,

c
X∈{'A'-'Z','0'-'9'}

i a
Unique ID 15 IMEI

e t
Device name 20

u
External power supply 1 0|1

n
Reserved 0

Q fide
battery percentage 3 0-100
Battery voltage <=4 0.0 – 4.50V
Charging 1 0|1
LED on 1 0|1|2
Send time 14 YYYYMMDDHHMMSS

n
Count number 4 0000 – FFFF

o
Tail character 1 $ $

C
 +RESP:GTTMZ: The report for real time operation TMZ
Example:
+RESP:GTTMZ,1A0102,135790246811220,-0330,0,20100214093254,11F0$
Parameter Length Range/Format Default
(byte)
Protocol version 6 XX0000 – XXFFFF,
X∈{'A'-'Z','0'-'9'}
Unique ID 15 IMEI
Device name 20
Time zone offset 5 ±HHMM
Daylight saving 1 0|1
Send time 14 YYYYMMDDHHMMSS
Count number 4 0000 – FFFF

TRACGL300AN001 - 68 -
GL300 @Tracker Air Interface Protocol

Tail character 1 $ $

 +RESP:GTALS: The report for real time operation READ,for example DIS
Example:
+RESP:GTALS,1A0102,135790246811220,GL300,DIS,1,1,5,,,,,,20121119083156,10FB$
Parameter Length (byte) Range/Format Default
Protocol version 6 XX0000 – XXFFFF,
X∈{'A'-'Z','0'-'9'}
Unique ID 15 IMEI
Device name 20

k
DIS 3 DIS DIS

n
Input ID 1 1 1

i
Mode 1 0|1|2|3 0

l l
Debounce time <=2 0-20 (×10ms) 5

c
reserved 0

i a
reserved 0

e t
reserved 0

u
reserved 0

n
reserved 0

Q fide
Send time 14 YYYYMMDDHHMMSS
Count number 4 0000 – FFFF
Tail character 1 $ $

n
 +RESP:GTGSV: The report for GPS level
Example:

o
+RESP:GTGSV,1A0102,359464036001111,,3,17,11,30,24,31,30,32,28,32,29,12,0,14,17,16,1
8,20,0,22,24,24,0,25,0,20120305101643,000F$

C
Parameter Length (byte) Range/Format Default
Protocol version 6 XX0000 – XXFFFF,
X∈{'A'-'Z','0'-'9'}
Unique ID 15 IMEI
Device name 20
GPS level 1 0|1|2|3
Jamming indicator 1 0-255
SV count 2 0-12
Sv_id 2 0-50
Sv_power 2 0-55
Sv_id 2 0-50
Sv_power 2 0-55
……………
Sv_id 2 0-50
TRACGL300AN001 - 69 -
GL300 @Tracker Air Interface Protocol

Sv_power 2 0-55
Send time 14 YYYYMMDDHHMMSS
Count number 4 0000 – FFFF
Tail character 1 $ $

 <GPS level>:Four levels:


 0: Can not fix
 1: Hard to fix
 2: A little hard fix
 3: Easy to fix
 <Jamming indicator>: Scaled (0 = no CW jamming, 255=strong CW jamming)

k
 <SV count>: Count of satellites the GPS found.
 <Sv id>: Satellite id

i n
 <SV power>: Satellite power

c l l
3.3.4. Event Report

e t i a
The following event reports are triggered when certain event occurs.
+RESP:GTPNA: Power on report

u n
+RESP:GTPFA: Power off report
+RESP:GTEPN: The report for connecting external power supply

Q fide
+RESP:GTEPF: The report for disconnecting external power supply
+RESP:GTBPL: Battery low report
+RESP:GTBTC: Start charging report
+RESP:GTSTC: Stop charging report.

n
+RESP:GTSTT: Device motion state indication
+RESP:GTPDP: GPRS PDP connection report

o
+RESP:GTSWG: Switch on or off Geo-Fence 0 via function key
+RESP:GTIGN: Ignition on report

C
+RESP:GTIGF: Ignition off report
+RESP:GTGSM:The report for the information of the service cell and the neighbor cells.
+RESP:GTTEM: Temperature alarm report
+RESP: GTUPC: Tell the backend server that the configuration in the unit is updated over the air
+RESP: GTJDR:If the <Mode> set as 1 in the AT+GTJDC command, when jamming is detected,
the device will report +RESP:GTJDS message.
+RESP: GTJDS:If the <Mode> set as 2 in the AT+GTJDC command, when jamming is detected,
the device will report +RESP:GTJDS message.

In +RESP:GTEPN, +RESP:GTEPF, +RESP:GTBTC, +RESP:GTSTC, +RESP:GTBPL,


+RESP:GTSTT,+RESP:GTSWG event reports, the last known GPS information and the current
GSM network information are involved.

 +RESP:GTPNA:
TRACGL300AN001 - 70 -
GL300 @Tracker Air Interface Protocol

Example:
+RESP:GTPNA,1A0102,135790246811220,,20100214093254,11F0$
Parameter Length (byte) Range/Format Default
Protocol version 6 XX0000 – XXFFFF,
X∈{'A'-'Z','0'-'9'}
Unique ID 15 IMEI
Device name 20
Send time 14 YYYYMMDDHHMMSS
Count number 4 0000 – FFFF
Tail character 1 $ $

n k
 +RESP:GTPFA:

l i
Example:

l
+RESP:GTPFA,1A0102,135790246811220,,20100214093254,11F0$

c a
Parameter Length (byte) Range/Format Default

i
Protocol version 6 XX0000 – XXFFFF,

e t
X∈{'A'-'Z','0'-'9'}

u n
Unique ID 15 IMEI
Device name 20

Q fide
Send time 14 YYYYMMDDHHMMSS
Count number 4 0000 – FFFF
Tail character 1 $ $

n
 +RESP:GTEPN:

o
Example:
+RESP:GTEPN,1A0102,135790246811220,,0,4.3,92,70.0,121.354335,31.222073,200902140

C
13254,0460,0000,18d8,6141,00,20100214093254,11F0$
Parameter Length (byte) Range/Format Default
Protocol version 6 XX0000 – XXFFFF,
X∈{'A'-'Z','0'-'9'}
Unique ID 15 IMEI
Device name 20
GPS accuracy 1 0
Speed <=5 0.0 – 999.9km/h
Azimuth <=3 0 – 359
Altitude <=8 ±XXXXX.X m
Last longitude <=11 ±XXX.XXXXXX
Last latitude <=10 ±XX.XXXXXX
GPS UTC time 14 YYYYMMDDHHMMSS
MCC 4 0XXX

TRACGL300AN001 - 71 -
GL300 @Tracker Air Interface Protocol

MNC 4 0XXX
LAC 4 XXXX
Cell ID 4 XXXX
Odo mileage 9 0.0 – 4294967.0Km
Send time 14 YYYYMMDDHHMMSS
Count number 4 0000 – FFFF
Tail character 1 $ $

 <Last longitude>: The longitude of the last position. The format is “(-)xxx.xxxxxx” and the
value range is from “-180.000000” to “180.000000”. The unit is degree. West longitude is
defined as negative starting with minus “-” and east longitude is defined as positive without

k
“+”.

n
<Last latitude>: The latitude of the last position. The format is “(-)xx.xxxxxx” and the value

i
range is from “-90.000000” to “90.000000”. The unit is degree. South Latitude is defined as

l l
negative starting with minus “-” and north Latitude is defined as positive without “+”.

c i a
 +RESP:GTEPF:

e t
Example:

u
+RESP:GTEPF,1A0102,135790246811220,0,,4.3,92,70.0,121.354335,31.222073,200902140

n
13254,0460,0000,18d8,6141,00,20100214093254,11F0$

Q fide
Parameter Length (byte) Range/Format Default
Protocol version 6 XX0000 – XXFFFF,
X∈{'A'-'Z','0'-'9'}
Unique ID 15 IMEI
Device name 20

n
GPS accuracy 1 0

o
Speed <=5 0.0 – 999.9km/h
Azimuth <=3 0 – 359
±XXXXX.X m

C
Altitude <=8
Last longitude <=11 ±XXX.XXXXXX
Last latitude <=10 ±XX.XXXXXX
GPS UTC time 14 YYYYMMDDHHMMSS
MCC 4 0XXX
MNC 4 0XXX
LAC 4 XXXX
Cell ID 4 XXXX
Odo mileage 9 0.0 – 4294967.0Km
Send time 14 YYYYMMDDHHMMSS
Count number 4 0000 – FFFF
Tail character 1 $ $

 +RESP:GTBPL:
TRACGL300AN001 - 72 -
GL300 @Tracker Air Interface Protocol

Example:
+RESP:GTBPL,1A0102,135790246811220,,3.53,0,4.3,92,70.0,121.354335,31.222073,20090
214013254,0460,0000,18d8,6141,00,20100214093254,11F0$
Parameter Length (byte) Range/Format Default
Protocol version 6 XX0000 – XXFFFF,
X∈{'A'-'Z','0'-'9'}
Unique ID 15 IMEI
Device name 20
Battery voltage <=4 0.0 – 4.50V
GPS accuracy 1 0
Speed <=5 0.0 – 999.9km/h

k
Azimuth <=3 0 – 359

n
Altitude <=8 ±XXXXX.X m

i
Last longitude <=11 ±XXX.XXXXXX

l l
Last latitude <=10 ±XX.XXXXXX

c
GPS UTC time 14 YYYYMMDDHHMMSS

i a
MCC 4 0XXX

e t
MNC 4 0XXX

u
LAC 4 XXXX

n
Cell ID 4 XXXX

Q fide
Odo mileage 9 0.0 – 4294967.0Km
Send time 14 YYYYMMDDHHMMSS
Count number 4 0000 – FFFF
Tail character 1 $ $

o n
 +RESP:GTBTC:
Example:

C
+RESP:GTBTC,1A0102,135790246811220,,0,4.3,92,70.0,121.354335,31.222073,200902140
13254,0460,0000,18d8,6141,00,20100214093254,11F0$
Parameter Length (byte) Range/Format Default
Protocol version 6 XX0000 – XXFFFF,
X∈{'A'-'Z','0'-'9'}
Unique ID 15 IMEI
Device name 20
GPS accuracy 1 0
Speed <=5 0.0 – 999.9km/h
Azimuth <=3 0 – 359
Altitude <=8 ±XXXXX.X m
Last longitude <=11 ±XXX.XXXXXX
Last latitude <=10 ±XX.XXXXXX
GPS UTC time 14 YYYYMMDDHHMMSS

TRACGL300AN001 - 73 -
GL300 @Tracker Air Interface Protocol

MCC 4 0XXX
MNC 4 0XXX
LAC 4 XXXX
Cell ID 4 XXXX
Odo mileage 9 0.0 – 4294967.0Km
Send time 14 YYYYMMDDHHMMSS
Count number 4 0000 – FFFF
Tail character 1 $ $

 +RESP:GTSTC:

k
Example:

n
+RESP:GTSTC,1A0102,135790246811220,,0,4.3,92,70.0,121.354335,31.222073,200902140

l i
13254,0460,0000,18d8,6141,00,20100214093254,11F0$

l
Parameter Length (byte) Range/Format Default

c a
Protocol version 6 XX0000 – XXFFFF,

i
X∈{'A'-'Z','0'-'9'}

e t
Unique ID 15 IMEI

u n
Device name 20
Reserved 0

Q fide
GPS accuracy 1 0
Speed <=5 0.0 – 999.9km/h
Azimuth <=3 0 – 359
Altitude <=8 ±XXXXX.X m
Last longitude <=11 ±XXX.XXXXXX

n
Last latitude <=10 ±XX.XXXXXX

o
GPS UTC time 14 YYYYMMDDHHMMSS
MCC 4 0XXX

C
MNC 4 0XXX
LAC 4 XXXX
Cell ID 4 XXXX
Odo mileage 9 0.0 – 4294967.0Km
Send time 14 YYYYMMDDHHMMSS
Count number 4 0000 – FFFF
Tail character 1 $ $

 +RESP:GTSTT:
Example:
+RESP:GTSTT,1A0102,135790246811220,,41,0,4.3,92,70.0,121.354335,31.222073,2009021
4013254,0460,0000,18d8,6141,00,20100214093254,11F0$
Parameter Length (byte) Range/Format Default

TRACGL300AN001 - 74 -
GL300 @Tracker Air Interface Protocol

Protocol version 6 XX0000 – XXFFFF,


X∈{'A'-'Z','0'-'9'}
Unique ID 15 IMEI
Device name 20
State 2 21|22|41|42
GPS accuracy 1 0
Speed <=5 0.0 – 999.9km/h
Azimuth <=3 0 – 359
Altitude <=8 ±XXXXX.X m
Last longitude <=11 ±XXX.XXXXXX
Last latitude <=10 ±XX.XXXXXX

k
GPS UTC time 14 YYYYMMDDHHMMSS

n
MCC 4 0XXX

i
MNC 4 0XXX

l l
LAC 4 XXXX

c a
Cell ID 4 XXXX

i
Odo mileage 9 0.0 – 4294967.0Km

e t
Send time 14 YYYYMMDDHHMMSS

u n
Count number 4 0000 – FFFF
Tail character 1 $ $

Q fide
 +RESP:GTPDP:
Example:

n
+RESP:GTPDP,1A0102,135790246811220,,20100214093254,11F0$
Parameter Length (byte) Range/Format Default

o
Protocol version 6 XX0000 – XXFFFF,
X∈{'A'-'Z','0'-'9'}

C
Unique ID 15 IMEI
Device name 20
Send time 14 YYYYMMDDHHMMSS
Count number 4 0000 – FFFF
Tail character 1 $ $

 +RESP:GTSWG:
Example:
+RESP:GTSWG,1A0102,135790246811220,,1,0,2.1,0,27.1,121.390717,31.164424,20100901
073917,0460,0000,1878,0873,00,20100901154653,0015$
Parameter Length (byte) Range/Format Default
Protocol version 6 XX0000 – XXFFFF,
X∈{'A'-'Z','0'-'9'}

TRACGL300AN001 - 75 -
GL300 @Tracker Air Interface Protocol

Unique ID 15 IMEI
Device name 20
Geo active 1 0|1
GPS accuracy 1 0
Speed <=5 0.0 – 999.9km/h
Azimuth <=3 0 – 359
Altitude <=8 ±XXXXX.X m
Last longitude <=11 ±XXX.XXXXXX
Last latitude <=10 ±XX.XXXXXX
GPS UTC time 14 YYYYMMDDHHMMSS
MCC 4 0XXX

k
MNC 4 0XXX

n
LAC 4 XXXX

i
Cell ID 4 XXXX

l l
Odo mileage 9 0.0 – 4294967.0Km

c a
Send time 14 YYYYMMDDHHMMSS

e i
Count number 4 0000 – FFFF

t
Tail character 1 $ $

u n
 <Geo active>: A numeric to indicate to activate or deactivate Geo-Fence 0 by the long press
of the function key.

Q fide
 0: deactivate Geo-Fence 0
 1: activate Geo-Fence 0

 +RESP:GTIGN:
Example:

n
+RESP:GTIGN,1A0102,135790246811220,,1200,0,4.3,92,70.0,121.354335,31.222073,20090

o
214013254,0460,0000,18d8,6141,00,20090214093254,11F0$
Parameter Length (byte) Range/Format Default

C
Protocol version 6 XX0000 – XXFFFF,
X∈{'A'-'Z','0'-'9'}
Unique ID 15 IMEI
Device name 20
Duration of Ignition <=6 0 – 999999 sec
Off
GPS accuracy 1 0
Speed <=5 0.0 – 999.9km/h
Azimuth <=3 0 – 359
Altitude <=8 ±XXXXX.X m
Last longitude <=11 ±XXX.XXXXXX
Last latitude <=10 ±XX.XXXXXX
GPS UTC time 14 YYYYMMDDHHMMSS
MCC 4 0XXX

TRACGL300AN001 - 76 -
GL300 @Tracker Air Interface Protocol

MNC 4 0XXX
LAC 4 XXXX
Cell ID 4 XXXX
Odo mileage 9 0.0 – 4294967.0Km
Send time 14 YYYYMMDDHHMMSS
Count number 4 0000 – FFFF
Tail character 1 $ $

 <Duration of Ignition Off>: Duration since last time the ignition is off. If greater than 999999
seconds, report as 999999 seconds.

k

n
+RESP:GTIGF:

i
Example:

l l
+RESP:GTIGF,1A0102,135790246811220,,1200,0,4.3,92,70.0,121.354335,31.222073,20090

c
214013254,0460,0000,18d8,6141,00,20090214093254,11F0$

i a
Parameter Length (byte) Range/Format Default

e t
Protocol version 6 XX0000 – XXFFFF,

u
X∈{'A'-'Z','0'-'9'}

n
Unique ID 15 IMEI

Q fide
Device name 20
Duration of Ignition <=6 0 – 999999 sec
On
GPS accuracy 1 0
Speed <=5 0.0 – 999.9km/h

n
Azimuth <=3 0 – 359

o
Altitude <=8 ±XXXXX.X m
Last longitude <=11 ±XXX.XXXXXX

C
Last latitude <=10 ±XX.XXXXXX
GPS UTC time 14 YYYYMMDDHHMMSS
MCC 4 0XXX
MNC 4 0XXX
LAC 4 XXXX
Cell ID 4 XXXX
Odo mileage 9 0.0 – 4294967.0Km
Send time 14 YYYYMMDDHHMMSS
Count number 4 0000 – FFFF
Tail character 1 $ $

 <Duration of Ignition On>: Duration since last time the ignition is on. If greater than 999999
seconds, report as 999999 seconds.

TRACGL300AN001 - 77 -
GL300 @Tracker Air Interface Protocol

 +RESP:GTGSM
Example:
+RESP:GTGSM,1A0102,011874000103767,FRI,0460,0000,1878,0871,20,,0460,0000,1878,0
152,16,,,,,,,,,,,,,,,,,,,,,,,,,,0460,0000,1878,0873,57,00,20100712071540,0008$
Parameter Length(byte) Range Default
protocol version 6 XX0000 – XXFFFF,
X∈{'A'-'Z','0'-'9'}
unique id 15 IMEI
fix type 3 SOS|RTL|LBC|FRI|GSM
mcc1 4 0XXX
mnc1 4 0XXX
lac1 4

k
cellid1 4

n
rxlevel1 2 0-63

l i
reserved1 0

l
mcc2 4 0XXX

c a
mnc2 4 0XXX

e i
lac2 4

t
cellid2 4

u n
rxlevel2 2 0-63
reserved2 0

Q fide
mcc3 4 0XXX
mnc3 4 0XXX
lac3 4
cellid3 4

n
rxlevel3 2 0-63
reserved3 0

o
mcc4 4 0XXX
mnc4 4 0XXX

C
lac4 4
cellid4 4
rxlevel4 2 0-63
reserved4 0
mcc5 4 0XXX
mnc5 4 0XXX
lac5 4
cellid5 4
rxlevel5 2 0-63
reserved5 0
mcc6 4 0XXX
mnc6 4 0XXX
lac6 4
cellid6 4

TRACGL300AN001 - 78 -
GL300 @Tracker Air Interface Protocol

rxlevel6 2 0-63
reserved6 0
mcc 4 0XXX
mnc 4 0XXX
lac 4
cellid 4
rxlevel 2 0-63
ta 2
send time 14 YYYYMMDDHHMMSS
count num 4
Tail character 1 $ $

k
 <fix type> : A string to indicate what kind of GPS fixing this cell information is for.
 "SOS" This cell information is for SOS requirement.

i n
 "RTL" This cell information is for RTL requirement.

l l
 "LBC" This cell information is for LBC requirement.

c
 "FRI" This cell information is for FRI requirement.

i a
 <mcci> : MCC of the neighbor cell i (i is the index of the neighbor cell).

e t
 <mnci> : MNC of the neighbor cell i.
 <laci> : LAC in hex format of the neighbor cell i.

u n
 <cellidi> : Cell ID in hex format of the neighbor cell i.

Q fide
<rxleveli> : 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

n
 <reservedi> : The reserved filed for the neighbor cell i.
 <mcc> : MCC of the service cell.

o
 <mnc> : MNC of the service cell.
 <lac> : LAC in hex format of the service cell.

C
 <cellid> : Cell ID in hex format of the service cell.
 <rxlevel> : 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)>, <cellid(i)> means the terminal doesn’t know the value.
3. This message can not be sent via SMS.

 +RESP:GTTEM
Example:
+RESP:GTTEM,1A0102,860599000000448,,3,33,0,5.8,0,33.4,117.201191,31.832502,201301
09061410,0460,0000,5678,2079,,20130109061517,0091$
Parameter Length (byte) Range/Format Default

TRACGL300AN001 - 79 -
GL300 @Tracker Air Interface Protocol

Protocol version 6 XX0000 – XXFFFF,


X∈{'A'-'Z','0'-'9'}
Unique ID 15 IMEI
Device name 20
Alarm type 1 1|2|3
Temperature 4 XX.X
GPS accuracy 1 0
Speed <=5 0.0 – 999.9km/h
Azimuth <=3 0 – 359
Altitude <=8 ±XXXXX.X m
Last longitude <=11 ±XXX.XXXXXX

k
Last latitude <=10 ±XX.XXXXXX

n
GPS UTC time 14 YYYYMMDDHHMMSS

i
MCC 4 0XXX

l l
MNC 4 0XXX

c a
LAC 4 XXXX

i
Cell ID 4 XXXX

e t
Odo mileage 9 0.0 – 4294967.0Km

u n
Send time 14 YYYYMMDDHHMMSS
Count number 4 0000 – FFFF

Q fide
Tail character 1 $ $
 <Last longitude>: The longitude of the last position. The format is “(-)xxx.xxxxxx” and the
value range is from “-180.000000” to “180.000000”. The unit is degree. West longitude is
defined as negative starting with minus “-” and east longitude is defined as positive without
“+”.

n
 <Last latitude>: The latitude of the last position. The format is “(-)xx.xxxxxx” and the value

o
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 “+”.

C
<Alarm type>: The type of temperature alarm.
 1: The current temperature lower than the low temperature threshold defined by
<Min temperature>.
 2: The current temperature in setting temperature threshold range
 3: The current temperature higher than the high temperature threshold defined by
<Max temperature>.
 <Temperature>: The current temperature of the device.

 +RESP:GTUPC:
Example:
+RESP:GTUPC,1A0102,135790246811220,,1,http://www.queclink.com/configure.ini,,20090
201000000,11F0$
Parameter Length(byte) Range/Format Default
protocol version 6 XX0000 – XXFFFF,
X∈{'A' – 'Z', '0' – '9'}

TRACGL300AN001 - 80 -
GL300 @Tracker Air Interface Protocol

unique ID 15 IMEI
device name <=10 ‘0’-‘9’,’a’-‘z’,’A’-‘Z’
Command id 1
result 2 100|101|102|103|200|201|202|300|301|302
download URL <=60 Complete URL
reserved 0
send time 14 YYYYMMDDHHMMSS
count number 4 0000-FFFF
tail character 1 $ $
 <Command id>: The command id in the update configure file.It is always 0 before the device
start to update device configure.It is total number of the commands when the respond result

k
code is 301.It is wrong format of command id when the respond result code is 302.

n
 <result>: A numeric to indicate whether the configuration was updated successfully.

i
 100: the update command is starting.

l l
 101: the update command is confirmed by the device.

c
 102: the update command is refused by the device.

i a
 103: the update process is refused because the battery is low.

e t
 200: the device starts to download the package.
 201: the device finishes downloading the package successfully.

u n
 202: the device fails to download the package.

Q fide
 300: the device starts to update the device configure.
 301: the device finishes updating the device configure successfully.
 302: the device fails to update the device configure.
 <download URL>: The complete URL to download the configuration. It includes the file
name.

n
 +RESP:GTJDR:

o
Example:
+RESP:GTJDR,0A0102,135790246811220,,0,4.3,92,70.0,121.354335,31.222073,20090214013

C
254,0460,0000,18d8,6141,00,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' '-' '_'

GPS Accuracy <=2 0 0, Last known

Speed <=5 0.0 – 999.9 km /h

Azimuth <=3 0 – 359

Altitude <=8 (–)xxxxx.x m

TRACGL300AN001 - 81 -
GL300 @Tracker Air Interface Protocol

Longitude <=11 (–)xxx.xxxxxx

Latitude <=10 (–)xx.xxxxxx

GPS UTC Time 14 YYYYMMDDHHMMSS

MCC 4 0XXX

MNC 4 0XXX

LAC 4 XXXX

Cell ID 4 XXXX

Reserved 2 00 00

k
Send Time 14 YYYYMMDDHHMMSS

i n
Count Number 4 0000 – FFFF

l l
Tail Character 1 $ $

c i a

e
+RESP:GTJDS:

t
Example:

u n
+RESP:GTJDS,0A0102,135790246811220,,2,0,4.3,92,70.0,121.354335,31.222073,200902140
13254,0460,0000,18d8,6141,00,20090214093254,11F0$

Q fide
Parameter Length(byte) Range/Format Default

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' '-' '_' '?'

Jamming Status 1 1|2

C
GPS Accuracy <=2 0 0, Last known

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

MNC 4 0XXX

LAC 4 XXXX

TRACGL300AN001 - 82 -
GL300 @Tracker Air Interface Protocol

Cell ID 4 XXXX

Reserved 2 00 00

Send Time 14 YYYYMMDDHHMMSS

Count Number 4 0000 – FFFF

Tail Character 1 $ $
 <Jamming Status>: The current Jamming status of the device.
 1: Quit the jamming.
 2: Enter the jamming.

i n k
 +RESP:GTDAT

l l
Example:
+RESP:GTDAT,1A0102,135790246811220,GL300,config command to the CAN bus

c a
device,20121117112247,032D$

e i
Parameter Length(byte) Range Default

t
protocol version 6 XX0000 – XXFFFF,

u n
X∈{'A'-'Z','0'-'9'}
unique id 15 IMEI

Q fide
Device name 20
data 4 0XXX
send time 14 YYYYMMDDHHMMSS
count num 4
Tail character 1 $ $

o n
 <data>: The data to be transferred when you execute the command “AT+GTDAT”,It should
be printable ASCII string.

C
3.3.5. Buffer Report

If BUFFER function is enabled, the terminal will save the message into the BUFFER in the
following circumstances.
 No GSM signal.
 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 after the message can be sent to the backend
server. The buffer reports are saved to the built-in non-volatile memory in case the device is reset.
The device can save 3000 messages at most.
 Only +RESP messages can be buffered except +RESP:GTALL
 In the buffer report, the original header string “+RESP” is replaced by “+BUFF” while
keeps 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

TRACGL300AN001 - 83 -
GL300 @Tracker Air Interface Protocol

via SMS.
 The buffered messages will be sent after the other normal messages sending if <Buffer
Mode> in AT+GTSRI is set to 1.
 The buffered messages will be sent before the other normal messages sending if <Buffer
Mode> in AT+GTSRI is set to 2. The SOS message has the highest priority and is sent
before the buffered messages.

Example:
The following is an example of the buffered message:
+BUFF:GTFRI,1A0102,135790246811220,,0,0,1,1,4.3,92,70.0,121.354335,31.222073,20090214
013254,0460,0000,18d8,6141,00,,20090214093254,11F0$

k
3.3.6. Report Google Maps hyperlink

l i n l
According to the setting of the command AT+GTGLM and the configuration of location by call,
the device can send a SMS with Google Maps hyperlink to a mobile phone.

e c i a
If location by call is set to 1, GL300 will sent its current position to the incoming call via SMS

t
with Google Maps hyperlink if the incoming call is a direct number (Please refer to <direct

u n
number list> in the chapter 3.2.13) or a white call (Please refer to <white number list> in the
chapter 3.2.12).

Q fide
If the <google link mode> was set as 1 in the command AT+GTGLM, GL300 will send a SMS
with Google Maps hyperlink to the direct phone numbers after the message +RESP:GTSOS and
+RESP:GTGEO.

n
 Google Maps hyperlink

o
Example:
GL300 SOS:
http://maps.google.com/maps?q=31.222073,121.354335+%28GL100%29

C
F1 D2009/01/01T00:00:00 B74%
Parameter Length(byte) Range/Format Default
Sms header <=30
Google Maps hyperlink <=77
GPS fix 2 F1|F0
GPS UTC time 20 DYYYY/MM/DDTHH
:MM:SS
battery level <=5 B1-100%

 <Sms header>: A string that includes the terminal name and GPS fix type ("SOS", "IN
GEO-i", "OUT GEO-i", "LBC").
 <Google Maps hyperlink>: A string of a google map hyperlink.

TRACGL300AN001 - 84 -
GL300 @Tracker Air Interface Protocol

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+GTQSS or AT+GTSRI command.
 +ACK:GTHBD:
Example:
+ACK:GTHBD,1A0102,135790246811220,,20100214093254,11F0$
Parameter Length (byte) Range/Format Default
Protocol version 6 XX0000 – XXFFFF,

k
X∈{'A'-'Z','0'-'9'}
Unique ID 15 IMEI

n
Device name 20

l i
Send time 14 YYYYMMDDHHMMSS

l
Count number 4 0000 – FFFF

c a
Tail character 1 $ $

u e n t i
Whenever the backend server receives a heartbeat package, it should reply an acknowledgement to
the device.

Q fide
 +SACK:GTHBD:
Example:
+SACK:GTHBD,1A0102,11F0$
Parameter Length (byte) Range/Format Default

n
Protocol version 6 XX0000 – XXFFFF,
X∈{'A'-'Z','0'-'9'}

o
Count number 4 0000 – FFFF
Tail character 1 $ $

C
 <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.

3.5. Sever Acknowledgement

If server acknowledgement is enabled by AT+GTQSS or AT+GTSRI command, the backend


server should reply to the device whenever it receives a message from the device.
 +SACK:
Example:
+SACK:11F0$
Parameter Length (byte) Range/Format Default

TRACGL300AN001 - 85 -
GL300 @Tracker Air Interface Protocol

Count number 4 0000 – FFFF


Tail character 1 $ $

 <Count number>: The backend server uses the <Count number> extracted from the received
message as the <Count number> in the server acknowledgement.

i n k
c l i al
u e n t
Q fide
o n
C
TRACGL300AN001 - 86 -
GL300 @Tracker Air Interface Protocol

Appendix: Message Index

 Command and ACK


AT+GTQSS
+ACK:GTQSS
AT+GTBSI
+ACK:GTBSI
AT+GTSRI
+ACK:GTSRI
AT+GTCFG

k
+ACK:GTCFG

n
AT+GTNMD

i
+ACK:GTNMD

l l
AT+GTTMA

c
+ACK:GTTMA

i a
AT+GTFRI

e t
+ACK:GTFRI
AT+GTGEO

u n
+ACK:GTGEO
AT+GTSPD

Q fide
+ACK:GTSPD
AT+GTFKS
+ACK:GTFKS
AT+GTRTO

n
+ACK:GTRTO
AT+GTWLT

o
+ACK:GTWLT
AT+GTGLM

C
+ACK:GTGLM
AT+GTPIN
+ACK:GTPIN
AT+GTDIS
+ACK:GTDIS
AT+GTDOG
+ACK:GTDOG
AT+GTDAT
+ACK:GTDAT
AT+GTNTS
+ACK:GTNTS
AT+GTOWH
+ACK:GTOWH
AT+GTTEM
+ACK:GTTEM
TRACGL300AN001 - 87 -
GL300 @Tracker Air Interface Protocol

AT+GTCMD
+ACK:GTCMD
AT+GTUPC
+ACK:GTUPC
AT+GTJDC
+ACK:GTJDC

 Position Related Report


+RESP:GTFRI
+RESP:GTGEO
+RESP:GTSPD

k
+RESP:GTSOS
+RESP:GTRTL

n
+RESP:GTLBC

l i
+RESP:GTPNL

l
+RESP:GTNMR

c a
+RESP:GTGCR

e i
+RESP:GTDOG

t
+RESP:GTIGL

u n
 Device Information Report

Q fide
+RESP:GTINF

 Report for Querying


+RESP:GTGPS
+RESP:GTALL

n
+RESP:GTCID

o
+RESP:GTCSQ
+RESP:GTVER
+RESP:GTBAT

C
+RESP:GTTMZ
+RESP:GTALS

 Event Report
+RESP:GTPNA
+RESP:GTPFA
+RESP:GTEPN
+RESP:GTEPF
+RESP:GTBTC
+RESP:GTSTC
+RESP:GTBPL
+RESP:GTSTT
+RESP:GTPDP
+RESP:GTSWG

TRACGL300AN001 - 88 -
GL300 @Tracker Air Interface Protocol

+RESP:GTIGN
+RESP:GTIGF
+RESP:GTGSM
+RESP:GTTEM
+RESP:GTUPC
+RESP:GTJDR
+RESP:GTJDS

 Executive command Report


+RESP:GTDAT
Heartbeat

k
+ACK:GTHBD
+SACK:GTHBD

l i n
 Server Acknowledgement

l
+SACK

e c t i a
u
Q fide n
o n
C
TRACGL300AN001 - 89 -