ATrack AT command set
Connection supported
Set reporting interval
AT$TRAC=1,60,,,,,2APN commands depend on the carrier SIM in your tracker, so they are not shown here.
29 devices
1 brand
ATrack Protocol (AX5 / AX7 / AX9 / AT5B / AK7V family)
Hybrid TCP protocol designed by ATrack Technology (Taiwan) for the AX-series fleet trackers · supports binary mode (default, compact) or ASCII mode (legacy, debuggable), auto-negotiated at session start. Western-fleet OEM tier.
On Traxelio
What Atrack trackers do once they are on Traxelio
Hardware that speaks this protocol
Devices that speak Atrack
Point this protocol at Traxelio
Point Atrack at Traxelio
-
1
Insert SIM with data plan + airtime
ATrack hardware is fleet-grade · LEDs are diagnostic (GPS, GSM, server-connected each get their own LED on the AX-series). Confirm SIM works in a phone first so you can isolate SIM issues from config issues.
-
2
Pick wire format + open Configurator
Decide binary (production, ~50% less bandwidth) or ASCII (debugging, grep-friendly). Plug in the USB-to-serial cable, open ATrack Configurator, click
Read Parametersto see the device's current state. -
3
Point the device at your server
In Configurator, set
Main Server IP/Hosttoyour-server.comand the port to5026(binary) or5040(ASCII). Set the wire format to match. Apply, then power-cycle.; Configurator parameters (binary mode example) Main Server Host: your-server.com Main Server Port: 5026 Wire Format: Binary APN: internet Report Interval (moving): 30s Report Interval (stopped): 300s -
4
Tune the AVL bitmap
Decide which I/O elements ride in every position. Basic fleet: position + speed + ignition + battery (small packet). CAN-rich heavy-truck: add J1939 PGNs, RPM, fuel level, odometer (~3x packet size). The bitmap is the most important per-deployment tuning lever · don't accept the defaults blindly.
-
5
Confirm first position arrives
Power-cycle, watch your server log. The login packet lands first (
@T...loginbinary or@P,<imei>,login;ASCII), then confirm the first decoded position in Traxelio. No traffic after the reboot · re-check APN and confirm the wire format matches what your server's listener expects.
gps.traxelio.com:5044
TCP
Still offline after GPS lock
Atrack still not landing
- Login packet arrives, server attempts ASCII decode, gets garbage · or vice versa
Wire-format mismatch between device and server. The device sends in whichever mode its config selects; the server's listener has to bind to the matching decoder. Either change the device config to match the port (Configurator > Wire Format > Binary / ASCII), or change the server-side listener (e.g. point the device at 5040 instead of 5026 if you want ASCII). The protocol does not auto-detect from the first byte alone · the port is the routing signal.
- AX9 PEG-style script runs in test but never fires on a real trigger
Common failure: the script is compiled but not committed to the device's active config. The Configurator has a separate
Apply Scriptstep distinct fromApply Parameters. Also confirm the trigger condition is satisfiable on the AVL bitmap you've configured · if the script depends on an I/O element that isn't enabled in the bitmap, the trigger never gets the data and never fires.- CAN bus reports arrive but values look wrong (RPM reads as fuel-level units, etc.)
PGN-to-AVL-id mapping issue. ATrack lets you map any J1939 PGN to any AVL ID for transport efficiency, which means your server's decoder must know the same mapping or it interprets the bytes wrong. Either use ATrack's default mapping (documented in the protocol PDF) and document it server-side, or pin a custom mapping in your fleet's standard config and ship it to every device.
FAQ
Atrack leftover questions
Is the ATrack protocol open / publicly documented?
ATrack distributes the protocol PDF (current rev v9.5) to integrators via their portal · sign-up is required but approval is routine for any commercial-use case. The open-source Traccar project ships AtrackProtocolDecoder covering both binary and ASCII modes, which is the most accessible reference for a working implementation. ATrack also publishes a Protocol Tester Windows app that lets you replay PCAPs against a sandbox decoder for debugging.