ATrack Protocol · AX5 / AX7 / AX9 / AX11 binary + ASCII reference
27 devices 1 brands Port 5026 (Traccar binary) · 5040 (Traccar ASCII) TCP (primary) · UDP supported

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.

Talk to integration team Browse 27 supported devices

3 min read · ~590 words

Quick answers

Does ATrack use binary or ASCII?

Both, negotiable per session. The device's config flags binary or ASCII mode; the server's first reply confirms. Production deployments lean binary (compact, ~50% less bandwidth), debugging deployments lean ASCII (grep-friendly, replay-friendly). Same hardware, same firmware, same protocol document · just two encodings.

What port does ATrack use?

Configurable. Traccar's reference is 5026 for binary mode and 5040 for ASCII mode · two listeners on the same server, each binding to its respective decoder. Inside your platform you can run both ports if you have a fleet that's mixed binary + ASCII (e.g. half on production firmware, half on debug units).

What's the ATrack AVL bitmap?

A 4-byte field in every config that tells the device which I/O elements to include in every position record. Position-only deployments set most bits to zero · CAN-rich heavy-truck deployments enable digital inputs, analog inputs, J1939 PGNs, driver-ID readers. Same packet shape, very different payload size, controlled at the bitmap level.

Can ATrack run scripts on the device?

On the AX9 and AX11 premium tier · yes, via a script language similar to CalAmp's PEG. You define triggers (hard brake, geofence cross, ignition on, custom thresholds) and actions (send extended record, change reporting interval, engage relay). The AX5 and AX7 mid-tier don't support scripting · they stick to the AVL bitmap for all trigger logic.

Does ATrack support OTA firmware updates?

Yes, robustly · ATrack Studio (their cloud platform) manages OTA rollouts with versioning, batching, rollback, and per-device targeting. You can also self-host the firmware delivery via the protocol's firmware-push command codes if you have a fleet integrator's setup, but Studio is the path of least resistance.

The ATrack protocol is the wire format used by ATrack Technology (Taiwan) across the AX5, AX7, AX9, AX11, AT5B, AK7V, and AL7 fleet-tracker families. ATrack sits in the Western fleet OEM tier · less visible than Teltonika or Queclink in retail, but heavily deployed in US fleet integrator stacks (Verizon Connect, Geotab partner ecosystem, several large telematics resellers white-label ATrack hardware).

Distinctive among Asian-OEM protocols, ATrack supports two negotiable wire formats on the same hardware · binary (compact, byte-aligned) for production deployments, and ASCII (semicolon-delimited, easy to grep) for debugging and integration testing. The device chooses based on its config and the server's first reply.

Protocol-at-a-glance

  • Transport · TCP (primary) or UDP
  • Default ports · 5026 (Traccar binary), 5040 (Traccar ASCII)
  • Encoding · binary (big-endian) OR ASCII (@P-prefixed, ;-separated, terminated)
  • Auth · Login packet (binary @T... or ASCII @P,<imei>,<info>;) negotiates mode + session
  • Heartbeat · keep-alive every 30 s by default (configurable)
  • Spec · ATrack publishes the protocol PDF on their integrator portal (current rev: v9.5 covering AX5 / AX7 / AX9 / AX11)

Packet structure (binary mode)

@T [LEN] [SEQ] [CHK] [BODY...]
  • @T (0x40 0x54) is the session start marker for the most-common position-report subtype
  • LEN = 2 bytes total length
  • SEQ = 2-byte sequence number (for ack tracking)
  • CHK = 2-byte XOR checksum
  • BODY = compact position record (lat, lon, speed, course, altitude, satellites, I/O bitfield, AVL bitmap)

ATrack uses an AVL bitmap in every record · the server tells the device which I/O elements to report on which trigger, and the device packs only those fields into each position. The same packet shape carries everything from a basic position to a CAN-rich heavy-truck record · the bitmap is the dimension.

Packet structure (ASCII mode)

@P,<imei>,<msg_type>,<date>,<time>,<lat>,<lon>,<speed>,<course>,<sats>,<HDOP>,<altitude>,<inputs>,<outputs>,<analog>,<event_code>;<
>

ASCII mode is what most integrators reach for first · it's grep-friendly, replay-friendly, and the protocol document reads like English. Production deployments typically switch to binary once the integration is stable, to cut bandwidth ~50%.

Why ATrack matters

  • Configurable wire format · binary for prod, ASCII for debug, same hardware · rare among Asian OEMs
  • OTA firmware updates · ATrack supports robust OTA firmware push via their Studio cloud · enterprise-grade rollout management
  • PEG-style scripting · the AX9 / AX11 high-tier units accept on-device scripts for triggered behaviors (engine cut on geofence, log dump on hard brake, etc.), similar to CalAmp PEG
  • Western fleet certifications · FCC, IC, CE, E-Mark for in-vehicle use · easier sale into regulated North American and EU fleet contracts than uncertified Chinese OEMs
  • Stable protocol · the same parser written in 2015 still decodes 2026-firmware packets · long upgrade paths

Configuring an ATrack device for any server

Two paths · the ATrack Configurator (Windows + USB-to-serial) or ATrack Studio (cloud, web-based):

Configurator path (preferred for first config):

  1. Open ATrack Configurator
  2. Connect device via USB-to-serial cable
  3. Set Main Server to your-server.com:5026 (binary) or 5040 (ASCII)
  4. Set APN to your carrier's value
  5. Pick wire format (binary recommended for production)
  6. Apply, power-cycle

Studio path (preferred for fleet rollouts):

  1. Pair the device's IMEI to your Studio organization
  2. Push the server config from the cloud
  3. Device picks up the config on next sync · no SMS, no USB

After GPS lock and carrier attach, confirm the first decoded position in Traxelio. The configurable AVL bitmap means you decide which fields ride in every packet.

Supported devices in our catalog

ATrack AX5 (basic fleet), AX7 (mid-fleet + CAN), AX9 (premium + PEG scripting), AX11 (heavy-truck + multi-CAN), AT5B (asset tracker), AK7V (battery-powered fleet), AL7 (lone-worker) are catalogued under protocol: "atrack". The AX9 is the headline model · sold heavily into North American fleet integrators as the white-label core of branded telematics products.

Setup walkthrough

  1. 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. 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 Parameters to see the device's current state.

  3. 3

    Point the device at your server

    In Configurator, set Main Server IP/Host to your-server.com and the port to 5026 (binary) or 5040 (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. 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. 5

    Confirm first position arrives

    Power-cycle, watch your server log. The login packet lands first (@T...login binary 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.

  6. 6

    Don't have an ATrack-compatible server yet?

    Traxelio decodes ATrack natively on both binary (5026) and ASCII (5040) ports. Point the device at traxelio.com:5026 for binary and the first decoded position can be verified in Traxelio · including AVL bitmap support and OTA-firmware ack handling. Or self-host Traccar · same decoder, same ports. ATrack Studio also remains usable for OTA rollouts alongside whatever server you decode positions on.

Reference

Configuration reference

Parameter Value
Transport TCP (primary) · UDP supported
Default port 5026 (Traccar binary) · 5040 (Traccar ASCII)
Encoding Binary (big-endian) OR ASCII (`@P,...;` `\r\n`)
Packet header `@T` binary · `@P,` ASCII
Packet footer Binary: 2-byte XOR checksum · ASCII: `;` + `\r\n`
Authentication Login packet (binary `@T...login` or ASCII `@P,<imei>,...;`) negotiates mode + session
Heartbeat 30 s default · configurable down to 5 s, up to 3600 s
Checksum Binary: XOR checksum (2 bytes) · ASCII: none (TCP integrity)
Message types Position · keep-alive · event (ignition, geofence, hard brake, panic) · CAN frame · driver-ID · firmware ack
Codec versions AVL bitmap (4-byte) controls which I/O elements ride in every record
Configurator ATrack Configurator (Windows + USB-to-serial)
On-device scripting AX9 / AX11 only · PEG-style on-device script engine for triggered behaviors
Vendor platform ATrack Studio (cloud, web · OTA firmware, config push, fleet rollout)
Spec name ATrack Protocol Specification
Spec versions v9.5 (current, AX5 / AX7 / AX9 / AX11)
Open-source decoder Traccar `AtrackProtocolDecoder` covers both binary and ASCII modes
Vendor ATrack Technology · Taipei, Taiwan
Vendor portal www.atrack.com.tw · integrator portal for spec + Studio

Or skip the integration

Traxelio decodes Atrack natively

Point your device at our endpoint, then verify the first decoded position in Traxelio. We handle the protocol, ack the packets, and serve the dashboards.

Plan a protocol cutover Talk to integrators

Protocol Capabilities

Data Points from Atrack Devices

Traxelio processes all telemetry data sent by Atrack trackers for comprehensive fleet insights.

Core Tracking

  • GPS Location
  • Speed
  • Altitude
  • Heading / Direction
  • Street Address
  • GPS Accuracy

Engine & Driving

  • Ignition Status
  • Odometer / Mileage

Sensors

  • Battery Level

Event Coverage

Alerts you'll get from devices on this protocol

Device online

The device is back online and transmitting data.

Device offline

The device has stopped reporting. It may have lost connection or power.

Device Moving

The vehicle is currently in motion.

Device Stopped

The vehicle is stationary.

Device overspeed

The vehicle is exceeding the set speed limit.

Geofence enter

The vehicle has entered a defined zone.

Geofence exit

The vehicle has exited a defined zone.

Alarm

Tow

Possible towing activity detected, check vehicle status.

Ignition On

The ignition is ON. The engine has started.

Ignition Off

The ignition is OFF. The engine has been stopped.

Long Idle

The vehicle has been idling for a long period.

All Models

Representative Atrack Devices (27)

Start with the strongest matches, then use pagination or brand pages for the full compatibility list.

ATrack AK1

ATrack

ATrack AK11

ATrack

ATrack AK7S

ATrack

ATrack AK7V

ATrack

ATrack AL1

ATrack

ATrack AL11

ATrack

ATrack AL7

ATrack

ATrack AP1

ATrack

ATrack AS1

ATrack

ATrack AS11

ATrack

ATrack AS3

ATrack

ATrack AT1

ATrack

Compatible Brands

Brands Using Atrack Protocol

ATrack

27 devices

Common troubleshooting

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 Script step distinct from Apply 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.

Explore More

Other Protocols

GT06

99 devices

H02

96 devices

Teltonika

84 devices

Meiligao

59 devices

GL200

36 devices

Huabao

32 devices
View All Trackers

FAQ

Frequently Asked 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.

Is ATrack still being manufactured?

Actively, yes · ATrack is a publicly-traded Taiwanese company (4416.TW), and the AX9 / AX11 lineup ships at scale into North American fleet integrators. Newer revisions add LTE Cat-M / NB-IoT modems, Bluetooth-LE beacons for asset chaining, and improved on-device scripting · the protocol document accumulates new message types but stays backward-compatible.

What's the difference between AX5, AX7, AX9, AX11?

AX5 is the entry fleet tracker (position, basic I/O, no CAN). AX7 adds CAN bus + driver-ID + RS-232. AX9 adds PEG-style scripting, multi-CAN, FOTA over LTE. AX11 is the heavy-truck variant (multi-CAN with J1939 + J1708 + custom protocols, configurable inputs, ruggedized for off-highway). Same protocol across all four · the I/O capabilities and scripting tier differ. Pick by application; the integration code stays the same.

Does ATrack work over 4G LTE / 5G?

All current AX-series ship with LTE Cat-1 or Cat-4 modems; some revisions support Cat-M / NB-IoT for low-power asset tracking. The protocol is transport-agnostic at the IP layer · LTE, NB-IoT, even 5G NSA all carry the same packets. 2G fallback exists on units with quad-band modems, useful in markets where LTE coverage is patchy.

Can I run ATrack and Teltonika devices on the same fleet platform?

Yes, on different decoder ports. Teltonika uses Codec 8 / 8 Extended on its own ports (usually 5027); ATrack uses 5026 (binary) or 5040 (ASCII) on its own decoders. Your platform handles the protocol multiplexing at the listener level, and both feed into the same downstream position store. Many fleet integrators run mixed Teltonika + ATrack + Queclink deployments this way.

Talk to integration team
T
Trax
Online
Say hello to Trax!