AVT130 / AVT131

GPS Trackers

AVT130 / AVT131

RS485 Protocol

AVT130/AVT131 RS485 Tracker Protocol

Revision 1.03 — Jun 23, 2026 — JAM duration range, boot firmware OTA, RS485 AT@RCS/AT@RAS

AVT130/AVT131 RS485 Tracker Protocol R1.03 defines the data stream format, configuration commands, and message structures for the optional RS-485 interface for trailer trackers. Based on the RS232 protocol (V1.08) with RS485-specific accessory commands (AT@RCS, AT@RAS). 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-09-15Initial release (based on RS232 V1.08 protocol)
1.022025-10-26Boot firmware OTA in AT@UPF Update Type 3; Bit 9 BOOT Firmware Mask in AT@BMS; BOOT Firmware Version in +BMR
1.032026-06-23Enter Jamming Duration range 60–360 seconds in AT@JAM

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, Message Filter Mode/Mask, 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)
FTPAT@FTP=FTP server address, port, credentials
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 (incl. RS485 info mask), Event Data Mask, LED, GNSS/AGPS, odometer, hour meter, power saving
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, +DFI, satellite info, satellite info
PCLAT@PCL=Preset command list (up to 32 commands)
ECLAT@ECL=Event-driven command list binding events to preset commands

Alarm commands

CodeCommandDescription
MOVAT@MOV=Movement alarm detection
TOWAT@TOW=Towing (TOW) alarm detection
SPDAT@SPD=Speed alarm threshold and duration
GEOAT@GEO=Circular geo-fence settings (up to 32 zones)
HBSAT@HBS=Harsh behavior (driving style) with trigger interval
CRAAT@CRA=Crash detection with crash debounce
JAMAT@JAM=Jamming alarm detection

I/O and ADC

CodeCommandDescription
IGNAT@IGN=Ignition and virtual ignition settings
DAMAT@DAM=Digital and analog input multiplexing (incl. delta AIS)
OUTAT@OUT=Digital output settings
AOSAT@AOS=Alarm output mapping and trigger masks (GEO, SPD, HBS, DRV, JAM)

1-Wire and RS485 (replaces RS232 URT/TRS)

CodeCommandDescription
WASAT@WAS=1-Wire application: iButton timer, temperature timer, 1-wire Data Mask
ETSAT@ETS=External temperature alarm (1-Wire or BLE sensors)
EHSAT@EHS=External humidity alarm (1-Wire or BLE sensors)
DRVAT@DRV=Driver ID authorization whitelist and report mode
RCSAT@RCS=RS485 communication: baud rate index (1200–115200), data bits (7/8), stop bits, parity
RASAT@RAS=RS485 accessory: accessory type/model (e.g. DYP-U02 ultrasonic oil level sensor), address IDs (up to 5 per type)

BLE, OTA, and debug

CategoryCodeDescription
BLEBSSBLE scan settings: working mode, frequency, duration, filter groups, I/O match/save rules, report intervals
OTAUPFFirmware upgrade over the air (APP MCU, auxiliary MCU, network module, boot firmware type 3)
OTABMSDevice management system: BMS server, report mode (Stop/TCP), +BMR Data Mask (incl. BOOT firmware bit 9)
DEBUGDBGOTA debug log server and log mask (incl. UART, 1-Wire, CAN logs)
Report mode (SIS/SSI): 0 = Stop, 1 = TCP, 2 = UDP, 3 = MQTT. BMS report mode: 0 = Stop, 1 = TCP. Buffer mode: 0 = disabled, 1 = low priority, 2 = high priority. RS485 variant uses AT@RCS/AT@RAS instead of RS232 AT@URT/AT@TRS.

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@RCS?at,,# — query RS485 communication settings
  • AT@RAS?at,,# — query RS485 accessory 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, heartbeat, and large-data 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, +LDP / -LDP, +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, +CVS, +CMI, +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 status, hour meter, crash, digital I/O, 1-Wire sensors
9–10Motor CAN infoMotor CAN Information Mask 1 and 2
11Electric CAN infoElectric CAN Information Mask
15Tacho common eventTachograph Common Event Information Mask
16Tachograph infoTachograph card and status data
19BLE informationBLE scan results and sensor data
21RS485 informationRS485 accessory data (volume, temperature) from AT@RAS accessories

Event types

TypeEvent
0Terminal power
1Regular report
2Moving
3Battery alarm
11Upgrade firmware (incl. CAN, BOOT MCU)
12External temperature alarm
13Ignition
14Main power alarm
15Tow alarm
16Over speed alarm
17Engine idle alarm
18Start/stop alarm
19Harsh behavior alarm
21Geo-fence alarm
22Digital input 1
23ID authorized event
24CANBUS info event
27Output alarm
28Delta AIS alarm
29PDP alarm
30BLE common info
31External humidity alarm
32Jamming alarm
35TLS certificate download
The full PDF lists every event state, CAN info mask field, RS485 accessory field, tachograph data field, and byte length with value ranges.

Buffer messages (+BMR / -BMR)

+BMR frames are real-time BMS reports sent to the device management server. -BMR frames are buffered BMS reports sent when connectivity is restored. Configure 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 Life5–300 seconds TCP keep-alive
Report Interval1–2880 minutes
BMR Data MaskMain power, battery level, auxiliary MCU, config version, CAN info, IGN state, GNSS info, SIM info, module version, BOOT firmware (bit 9)
Revision 1.03 added Update Type 3 (boot firmware) in AT@UPF and Bit 9 BOOT Firmware of Main MCU Mask in AT@BMS, with <BOOT Firmware Version> reported in +BMR.

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 (incl. CAN, TAC, TCO sub-commands)
+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
+CVSCAN module version and serial number (via AT@RTO sub-command 13)
+CMICAN module car model ID (via AT@RTO sub-command 14)
+DFIDevice file information (via AT@RTO sub-command 16)
+LDP/-LDP carries large data packets such as BLE transparent data or file transfers. Message Filter Mask in AT@SIS/SSI can filter +LDP, +DFI, and related +ACK responses.

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
RS485RS-485 serial bus for external accessories (replaces RS232 URT/TRS)
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 AVT130/AVT131 GNSS tracker with RS485 interface unless otherwise specified.

AVT130 / AVT131 — RS485 Protocol

v1.03 · 2026-06-23 · Release

AVT130 / AVT131 — RS485 Protocol — Page 1 of 90

Page 1 of 90

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