ATL200

GPS Trackers

ATL200

Protocol

ATL200 Tracker Protocol

Revision 1.01 — Jul 4, 2025 — Initial release

ATL200 Tracker Protocol R1.01 defines the data stream format, configuration commands, and message structures used between the ATL200 data logger and backend server over LTE Cat-1 / EGPRS. Use the sections below for a structured overview, or open the full PDF for complete command parameters and field definitions.

Revision history

RevisionDateDescription
1.012025-07-04Initial release

Data stream format

Communication includes upstream (device → server) and downstream (server → device) data streams over the cellular network. Upstream carries responses to downlink commands, heartbeat packets, and unsolicited reports. Downstream carries configuration, query commands, and responses to uplink messages.

Frame types

DirectionEncodingFrameUsage
DownstreamPrintable ASCIIConfiguration CommandConfigure terminal parameters (AT@…=)
DownstreamPrintable ASCIIQuery CommandQuery current parameters (AT@…?)
DownstreamPrintable ASCII+SACKServer acknowledgement for +RPT messages
DownstreamPrintable ASCII+SHBDServer response to +HBD heartbeat
UpstreamPrintable ASCII+QRYTerminal response to a query command
UpstreamPrintable ASCII+HBDPeriodic heartbeat to maintain TCP/UDP connectivity
UpstreamPrintable ASCII+ACK / +NACKAcknowledgement or rejection of configuration commands
UpstreamHexadecimal+RPT / -RPTReal-time and buffered report messages
All upstream and downstream frames end with the character "#" (0x23). In printable ASCII frames, "," separates adjacent parameters. Hexadecimal frames have no parameter separator.

Configuration commands

Configuration commands use the format AT@<KEY>=<password>,<parameters>,…,<serial># . Each command is protected by a password (default at) and ends with a 4-digit hexadecimal serial number and "#".

Example — main server settings:

AT@SIS=at,0,1,255.255.255.255,12345,,,0,0001#

Network commands

CodeCommandDescription
SISAT@SIS=Main server IP, port, report mode (0 Stop / 1 TCP / 2 UDP / 3 MQTT), buffer, SACK enable, heartbeat interval, PDP/TLS settings
NISAT@NIS=APN, credentials, network scan mode (0 auto Cat1→GSM, 1 Cat1, 2 GSM), Search No Signal Cover
MQTAT@MQT=MQTT client ID, topics, QoS, keep-alive
TCRAT@TCR=TLS certificate remote download (HTTP)
TCLAT@TCL=TLS certificate local download

General commands

CodeCommandDescription
GMTAT@GMT=Greenwich Mean Time / time zone setting
GCSAT@GCS=Global configuration: +RPT Data Mask, Event Data Mask, Cold Chain Info Mask, LED mode, GNSS/AGPS, odometer, hour meter, power saving, button mode
RRSAT@RRS=Regular GNSS report: mode (0 off / 1 continuous / 2 long standby), IGN/IGF intervals, corner angle, wake-up schedule
RTOAT@RTO=Real-time operation: reboot, power off, factory reset, query network/version, flight mode, delete buffer, satellite info
PCLAT@PCL=Preset command list (up to 32 commands)
ECLAT@ECL=Event-driven command list binding events to preset commands
DOGAT@DOG=Software watchdog: scheduled reboot interval

Alarm commands

CodeCommandDescription
MOVAT@MOV=Movement alarm detection
FMSAT@FMS=Flight mode alarm settings
SPDAT@SPD=Speed alarm threshold and duration
GEOAT@GEO=Circular geo-fence settings (up to 32 zones)
LASAT@LAS=Light detection and alarm
BTAAT@BTA=Built-in temperature alarm
BHAAT@BHA=Built-in humidity alarm

I/O, BLE, OTA, and debug

CategoryCodeDescription
IOIGNIgnition and virtual ignition (G-sensor) settings
BLEBSSBLE scan settings and filter groups
BLEETSExternal temperature sensors (1-Wire, BLE)
BLEEHSExternal humidity sensors (1-Wire, BLE)
OTAUPFFirmware upgrade over the air
OTABMSDevice management system: BMS server, report interval, +BMR Data Mask
DEBUGDBGOTA debug log server and log mask
Report mode (SIS/BMS): 0 = Stop, 1 = TCP, 2 = UDP, 3 = MQTT (SIS only). Buffer mode: 0 = disabled, 1 = low priority, 2 = high priority.

Query commands

Query commands retrieve the current working parameters of the terminal. They use printable ASCII with comma-separated fields:

AT@<KEY>?<password>,,<serial>#

  • AT@SIS?at,,# — query main server settings
  • AT@NIS?at,,# — query network (APN) settings
  • AT@GMT?at,,# — query time settings
  • AT@GCS?at,,# — query global configuration
  • AT@RRS?at,,# — query regular report settings
  • AT@GEO?at,,# — query geo-fence settings
When sent by the backend server, parameters are returned to the server. When sent by SMS, parameters are returned via SMS.

Message format

Report, buffer, and heartbeat messages share a common frame structure with header, data, and tail zones:

ZoneFieldsEncoding
HeaderHead (5 B) + Length (2 B) + IMEI (8 B) + Device ID (1 B)ASCII / HEX / HEX / HEX
DataVariable payload + G-time (7 B)HEX or ASCII
TailSerial number (2 B) + Tail "#" (1 B)HEX / ASCII
  • +RPT / -RPT, +BMR / -BMR, +HBD — data zone encoded in hexadecimal (big-endian for multi-byte values)
  • +SACK / +SHBD — fully ASCII encoded
  • +ACK, +QRY, +ALL, +QNI, +VER, +GSV, +LSV, +BSV, +GAV — data zone in ASCII with comma separators

Report messages (+RPT / -RPT)

+RPT frames are real-time reports generated and sent within 3 minutes. -RPT frames are historical reports stored in the device buffer and sent when connectivity is restored.

All GNSS-related messages and events share the same +RPT/-RPT hex-encoded format. The Data Mask and Event Data Mask in AT@GCS control which information zones are included.

Key +RPT Data Mask bits (AT@GCS)

BitFieldContent
0Multi-packetAuto-enabled when message exceeds 256 bytes
1Network typeCellular network type
2BatteryVoltage (mV) and level (%)
3GNSS informationFix type, HDOP, speed, azimuth, altitude, lat/lon, UTC time, satellite counts
4Cell informationMCC, MNC, LAC, Cell ID, CSQ
5Neighboring cellAdjacent cell information
6Cold chain informationBuilt-in temp/humidity, light, 3-axis, 1-Wire sensors
7Upgrade informationFirmware upgrade status
8Event dataIgnition, motion, mileage, GEO status, hour meter, TLS download
19BLE informationBLE scan results and sensor data

Event types

TypeEvent
0Terminal power
1Regular report
2Moving
3Battery alarm
6Flight mode
8Light alarm
9Built-in temperature alarm
10Built-in humidity alarm
11Upgrade firmware
12External temperature alarm
13Ignition
16Over speed alarm
21Geo-fence alarm
29PDP alarm
30BLE common info
31External humidity alarm
The full PDF lists every event state, Cold Chain Info Mask bit, sensor data field, and byte length with value ranges.

Buffer messages (+BMR / -BMR)

+BMR frames are real-time BMS reports generated and sent within 3 minutes. -BMR frames are buffered BMS reports sent when connectivity is restored. Configure BMS reporting via AT@BMS.

ParameterDescription
Report Mode0 = Stop, 1 = TCP
Buffer Mode0 = disabled, 1 = low priority, 2 = high priority
BMS Server IP / PortDevice management server address
Connection Life0 or 5–300 seconds TCP keep-alive
Report Interval1–2880 minutes
BMR Data MaskBattery level, config version, IGN state, GNSS info, SIM info, module version
+BMR/-BMR use the same header/tail frame structure as +RPT/-RPT with a hexadecimal data zone.

Heartbeat and acknowledgement

FrameDirectionDescription
+HBDDevice → serverPeriodic heartbeat when report mode is TCP or UDP (interval set in AT@SIS)
+SHBDServer → deviceServer response to +HBD
+ACKDevice → serverConfirms a valid configuration command was received
+NACKDevice → serverRejects an illegal configuration command
+SACKServer → deviceServer acknowledgement when SACK Enable is set in AT@SIS

Command query responses

FrameDescription
+QRYResponse to a single query command
+ALLBulk response with all configured parameters
+QNINetwork information (APN, IMSI, ICCID, CSQ, cell ID)
+VERFirmware and hardware version information
+GSVGPS satellite visibility
+LSVGLONASS satellite values
+BSVBEIDOU satellite values
+GAVGALILEO satellite values

Terms and abbreviations

TermMeaning
ACKAcknowledgement
AGPSAssisted Global Positioning System
APNAccess Point Name
BLEBluetooth Low Energy
GNSSGlobal Navigation Satellite System
IMEIInternational Mobile Equipment Identity
IoTInternet of Things
MQTTMessage Queuing Telemetry Transport
RPTReport message
SACKServer acknowledgement
TCP / UDPTransmission Control / User Datagram Protocol
TLSTransport Layer Security
UTCCoordinated Universal Time
VGVirtual Ignition
VGN / VGFVirtual Ignition On / Off
In this document, "terminal", "device", and "equipment" refer to the ATL200 data logger unless otherwise specified.

ATL200 — Protocol

v1.01 · 2025-07-04 · Release

ATL200 — Protocol — Page 1 of 69

Page 1 of 69

If the preview does not load, use Download or Open in new tab.