AVT50

GPS Trackers

AVT50

Protocol

AVT50 Tracker Protocol

Revision 2.05 — May 7, 2026 — +DFI message, IGN BLE relay limits, PEO polygon fence

AVT50 Tracker Protocol R2.05 defines the data stream format, configuration commands, and message structures used between the AVT50 GNSS tracker and backend server. Use the sections below for a structured overview, or open the full PDF for complete command parameters and field definitions.

Revision history

RevisionDateDescription
1.012024-11-03Initial release
1.022025-03-10GNSS Satellites Number in AT@GCS; Charging Mode; Event Data Mask cleanup
1.032025-05-10AT@BSS BLE scan; AT@JAM/TAS; AT@ETS/EHS; external temp/humidity events; +TCF
1.042025-09-10GNSS Timeout parameter in AT@GCS
1.052025-09-24AT@SSI second server; TLS (TCR/TCL); MQTT (MQT); AT@UPC; AT@BWS; upgrade config event
2.012026-01-12AT@GGF geo-fence GNSS filter; GNSS spoofing alarm (type 39); JAM LTE signal params
2.022026-02-03ECL Trigger Mask in +RPT; ECL Trigger Report in AT@ECL
2.032026-02-25AT@PEO polygon fence; AT@BCS/BRY/BOS BLE connection and relay; PEO events 40/41
2.042026-03-23TOW/MOV/IGN/HBS/CRA parameter updates; JAM GSM params; ABK100 whitelist in AT@BSS
2.052026-05-07+DFI message; IGN output limits and BLE relay bits; ABR100 in AT@BCS; IGN debounce

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, PDP/TLS, Resend Time No SACK
SSIAT@SSI=Second server settings (same parameters as SIS)
NISAT@NIS=APN, credentials, network scan mode, Search No Signal Cover
MQTAT@MQT=MQTT client ID, topics, QoS, keep-alive (main or second server)
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: Data Mask, Event Data Mask (incl. PEO status bits 21/24), LED, GNSS/AGPS, odometer, hour meter, charging mode, GNSS timeout
RRSAT@RRS=Regular GNSS report: mode, IGN/IGF intervals, corner angle, long standby wake-up
RTOAT@RTO=Real-time operation: reboot, power off, factory reset, realtime positioning, +DFI, satellite info
PCLAT@PCL=Preset command list (up to 32 commands)
ECLAT@ECL=Event-driven command list with ECL Trigger Report
GGFAT@GGF=Geo-fence GNSS filter and spoofing detection settings

Alarm commands

CodeCommandDescription
MOVAT@MOV=Movement alarm with Motion Event Report
TOWAT@TOW=Towing (TOW) alarm detection
SPDAT@SPD=Speed alarm threshold and duration
GEOAT@GEO=Circular geo-fence settings (up to 32 zones)
PEOAT@PEO=Polygon fence settings (up to 50 zones)
HBSAT@HBS=Harsh behavior (driving style) with trigger interval
CRAAT@CRA=Crash detection with crash debounce
JAMAT@JAM=Jamming alarm (LTE and GSM signal thresholds)
TASAT@TAS=Tilt alarm detection

I/O, BLE, OTA, and debug

CategoryCodeDescription
IO & ADCIGNIgnition and virtual ignition; Ignition On limit outputs mask, GNSS speed limit, debounce
IO & ADCDAMDigital and analog input multiplexing (incl. delta AIS)
IO & ADCOUTDigital output settings
IO & ADCAOSAlarm output mapping and trigger masks
BLEBSSBLE scan settings, iBeacon UUID filter, accessory whitelist check
BLEBWSBLE beacon whitelist (MAC groups, up to 256 entries)
BLEBCSBLE connection settings (ABK100, ABR100 relay encryption)
BLEBRYBLE relay output control
BLEBOSBLE alarm output wave shape
BLEETSExternal temperature sensors (BLE)
BLEEHSExternal humidity sensors (BLE)
OTAUPFFirmware upgrade over the air (main MCU, network module, boot firmware)
OTAUPCConfiguration upgrade over the air
OTABMSDevice management system: BMS server, report mode (Stop/TCP/UDP/MQTT), +BMR Data Mask
DEBUGDBGOTA debug log server and log mask
Report mode (SIS/SSI/BMS): 0 = Stop, 1 = TCP, 2 = UDP, 3 = MQTT. 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@SSI?at,,# — query second 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
  • AT@PEO?at,,# — query polygon 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, +SCF, +TCF, +DFI — 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
7Upgrade informationFirmware upgrade status
8Event dataMain power, ignition, motion, mileage, GEO/PEO status, hour meter, crash, tilt, TLS, digital I/O
19BLE informationBLE scan results and sensor data
20BLE iBeaconiBeacon scan results
22Upgrade configConfiguration OTA status

Event types

TypeEvent
0Terminal power
1Regular report
2Moving
3Battery alarm
7Crash alarm
11Upgrade firmware
12External temperature alarm
13Ignition
14Main power alarm
15Tow alarm
16Over speed alarm
19Harsh behavior alarm
20G-sensor self-calibration
21Geo-fence alarm
22Digital input 1
27Output alarm
28Delta AIS alarm
29PDP alarm
30BLE common info
31External humidity alarm
32Jamming alarm
33Tilt alarm
34BLE iBeacon info
35TLS certificate download
38Upgrade configuration
39GNSS spoofing alarm
40PEO fence alarm
41PEO fence over-speed alarm
43ECL trigger alarm
The full PDF lists every event state, PEO status mask bit, data mask field, and byte length with value ranges.

Buffer messages (+BMR / -BMR)

+BMR frames are real-time BMS reports. -BMR frames are buffered BMS reports sent when connectivity is restored. Configure via AT@BMS.

ParameterDescription
Report Mode0 = Stop, 1 = TCP, 2 = UDP, 3 = MQTT
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, boot firmware

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

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
+SCFServer configuration fields
+TCFTerminal configuration fields (including tilt calibration)
+DFIDevice file information (requested via AT@RTO sub-command 16)

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
PEOPolygon fence (geo zone)
RPTReport message
SACKServer acknowledgement
TCP / UDPTransmission Control / User Datagram Protocol
TLSTransport Layer Security
TOWTowing detection
UTCCoordinated Universal Time
VGVirtual Ignition
VGN / VGFVirtual Ignition On / Off
In this document, "terminal", "device", and "equipment" refer to the AVT50 GNSS tracker unless otherwise specified.

AVT50 — Protocol

v2.05 · 2026-05-07 · Release

AVT50 — Protocol — Page 1 of 105

Page 1 of 105

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