H02 Protocol · Sinotrack / Cantrack ASCII format, port, SMS
96 devices 5 brands Port 5013 (Traxelio) · 8500 (Sinotrack ref) · 6789 (some Cantrack) TCP (UDP variant on some Sinotrack firmware)

H02 Protocol (Sinotrack / Cantrack family)

ASCII TCP protocol used across the Sinotrack, Cantrack, Secumore, and many no-name budget-tier GPS tracker families · the hash-delimited cousin of GPS103, with a different packet shape but the same simplicity goal.

3 min read · ~451 words

Quick answers

Is H02 the same as TK103?

No. Both are ASCII budget-tier protocols, both come out of Shenzhen, but they're different OEM lineages. H02 is the Sinotrack / Cantrack / Secumore wire format (hash-delimited *HQ,…#). TK103 is Coban's revision of GPS103 (semicolon-delimited imei:…,tracker,…;). Different decoders, different OEM ecosystems.

What does an H02 position packet look like?

Plain ASCII text, bracketed by *HQ, and #: *HQ,4109179276,V1,180000,A,2233.4567,N,11402.1234,E,0.00,0.00,310525,FFFFFBFF#. Fields are IMEI, message type, time, validity, lat, N/S, lon, E/W, speed, course, date, status bits. Human-readable in a raw TCP dump.

What port does H02 use?

Configurable. Traxelio uses 5013 (TCP, matches Traccar's default). Sinotrack's reference docs often say 8500 or operator-assigned. The SMS server,... command sets whichever port the server expects.

Does H02 support engine cut / immobilizer?

Yes on models with the relay wired (Sinotrack ST-906, ST-907, GTR-100 vehicle variants). SMS commands vary by OEM · Sinotrack uses relay,1# to engage, relay,0# to release. Some Cantrack firmware uses EngineOff and EngineOn. Check the model's command sheet.

Do H02 devices support sensors or just basic GPS?

Mostly basic GPS + speed + ignition. The protocol has a status bitmask that can carry simple flags (door open, button press, geofence in/out) but no analog sensor channels in the base spec. For fuel sensors, temperature probes, or CAN bus, look at Teltonika Codec 8 or Ruptela tiers.

The H02 protocol is the ASCII wire format used by Sinotrack, Cantrack, Secumore, and a long tail of OEM-clone GPS tracker brands. It evolved alongside Coban's GPS103/TK103 but went a different direction in packet structure: hash-delimited fields starting with *HQ, instead of semicolon-delimited. Same goal · cheap silicon, simple decode, fixed packet shape. Different OEM ecosystem.

Protocol-at-a-glance

  • Transport · TCP (UDP variant exists for some Sinotrack firmware)
  • Default port · 5013 (Traxelio's ingest port; matches the Traccar default)
  • Encoding · ASCII text, comma-separated, message bracketed by *HQ,#
  • Auth · login implied by the first packet carrying IMEI; no explicit ACK exchange
  • Heartbeat · device-driven, every ~2-5 min (configurable via SMS)

Packet examples

A typical H02 position record:

*HQ,4109179276,V1,180000,A,2233.4567,N,11402.1234,E,0.00,0.00,310525,FFFFFBFF#

Fields (in order): start-marker (*HQ,) · IMEI · message type (V1=position, V0=keep-alive, BR00=blind-spot binary, etc.) · UTC time · validity flag (A=valid GPS lock, V=invalid) · latitude · N/S · longitude · E/W · speed · course · UTC date · status bits (hex bitmask, varies per model).

The trailing # is the end-of-message marker · everything between *HQ, and # is one record.

Why the Sinotrack/Cantrack ecosystem is its own thing

  • Different OEM lineage · Sinotrack and Cantrack come out of separate Shenzhen design houses than Coban (GPS103) and Concox (GT06)
  • Wider hardware family · Sinotrack alone has dozens of model numbers (ST-901, ST-902, ST-905, ST-906, ST-907, ST-909, GTR-100, LK206A, more) all speaking H02
  • Pet / asset / motorcycle skew · much of the H02 catalog targets smaller form factors (pet trackers, motorcycle trackers, asset tags) not vehicle-class
  • Self-install heavy · most H02 devices ship as plug-and-go, no professional install needed

Configuring an H02 device for Traxelio

H02 devices use SMS commands closely modeled on the GPS103 set but with slight syntax differences per OEM. The most common Sinotrack syntax:

server,0,traxelio.com,5013,0#
apn,internet#                          (replace with your carrier's APN)
center,A,YOUR_PHONE_NUMBER#            (so SOS calls reach you)
timer,30#                              (position every 30 seconds)

The Cantrack and Secumore variants use the same SMS shape with vendor-specific opcodes · check the model's command sheet.

Supported devices in our catalog

91+ devices declare protocol: "h02" · the headline models: Sinotrack ST-901 / ST-905 / ST-907, Sinotrack GTR-100, Sinotrack LK206A, plus the Cantrack and Secumore lineups and many AliExpress / Alibaba no-name H02 rebrands.

H02 vs GPS103 vs GT06

Quick disambiguation · these three dominate the budget tier worldwide:

Protocol Packet style Header Vendor lineage Port (Traxelio)
H02 ASCII *HQ,# Sinotrack / Cantrack / Secumore 5013
GPS103 / TK103 ASCII imei:…,tracker,…; Coban / TK family 5001 / 5002
GT06 Binary 0x78 0x78 [LEN] [PROTO] … Concox / Jimi / OEM clones 5023

Traxelio decodes all three. Mixed-vendor fleets are common · the dashboard treats them as the same kind of GPS event, the per-device protocol just changes how the wire is parsed.

Setup walkthrough

  1. 1

    Insert SIM with data plan + airtime

    H02 devices have no UI to surface APN failures · test the SIM in a phone first.

  2. 2

    Set the APN

    Send apn,your_carrier_apn# to the device's SIM. APN must be set before any TCP attempt.

  3. 3

    Point the device at your server

    Send server,0,your-server.com,5013,0# (Sinotrack syntax). Vendor variants: Cantrack uses similar; Secumore uses setserver. Check the model's command sheet.

  4. 4

    Force TCP-only mode

    Send mode,1# (Sinotrack) to prevent UDP keep-alive garbage on the TCP listener. Some H02 firmware mixes them by default.

  5. 5

    Confirm first position arrives

    After GPS lock, confirm the first decoded position in Traxelio. The V flag in the position packet means GPS data invalid (weak antenna) · A means valid.

  6. 6

    Don't have an H02-compatible server yet?

    Traxelio decodes H02 natively on port 5013. Send server,0,traxelio.com,5013,0# and the first decoded position can be verified in Traxelio. Or self-host Traccar · same h02 decoder, same port.

Reference

Configuration reference

Parameter Value
Transport TCP (UDP variant on some Sinotrack firmware)
Default port 5013 (Traxelio) · 8500 (Sinotrack ref) · 6789 (some Cantrack)
Encoding ASCII, comma-separated fields
Packet envelope *HQ, ... #
Authentication Implicit · first packet carries IMEI, no ACK exchange
Heartbeat Configurable, default ~2-5 min
Message types V1 = position, V0 = keep-alive, BR00 = binary extended, NBR = nearby cell
Spec PDF www.traccar.org/protocol/5013-h02/h02_cantrack_secumore.pdf

SMS commands

server,0,your-server.com,5013,0#

Set destination server (Sinotrack syntax · vendor-specific variants exist). Mode 0 = TCP.

apn,internet#

Set the SIM's APN to your carrier's value (replace `internet`).

center,A,YOUR_PHONE#

Set the SOS / authorized number that receives alerts and can issue commands.

timer,30#

Position interval in seconds. `timer,60#` for 1-min reporting.

mode,1#

Force TCP-only (some firmware mixes UDP keep-alives into the TCP connection · this forces clean TCP).

relay,1#

Engage engine-cut relay (only on ST-906/ST-907/GTR-100 with relay wired · `relay,0#` releases).

Or skip the integration

Traxelio decodes H02 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.

Protocol Capabilities

Data Points from H02 Devices

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

Core Tracking

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

Engine & Driving

  • Ignition Status
  • Odometer / Mileage
  • Engine Hours

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.

Hard Braking

Hard braking detected, driver safety alert.

Hard Acceleration

Rapid acceleration detected, driving behavior alert.

Hard Turning

Sharp turning detected, driving behavior alert.

Impact Detected

Potential impact detected based on sudden deceleration and course change pattern.

All Models

Representative H02 Devices (96)

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

Compatible Brands

Brands Using H02 Protocol

Common troubleshooting

Device sends positions over TCP, then occasionally garbled bytes appear

Some H02 firmware variants mix UDP and TCP modes on the same connection (legacy firmware bug). Check the device's mode setting · force TCP-only with mode,1# (Sinotrack) or vendor-equivalent. The UDP keep-alives can appear as garbage on a TCP-only listener.

Device acquires GPS lock but the V/A validity flag stays at V

V means GPS data invalid · the device has a fix on satellites but isn't confident enough to publish coordinates. Common causes: weak antenna placement (under metal dashboard, near amplifier), partial sky view, indoor installation. Move the device or its external antenna to a clearer position.

SMS configuration commands appear to send successfully but device behavior doesn't change

Two possibilities: (1) command syntax varies by OEM · a Sinotrack command sent to a Cantrack device may be silently rejected; check the actual model's command sheet. (2) password protection · some H02 firmware variants require a leading password (123456 default) before the command keyword.

Explore More

Other Protocols

FAQ

Frequently Asked Questions

Is H02 an open protocol?

Cantrack/Secumore published a spec PDF that has circulated freely across the integrator community. Traccar's H02 decoder is the most authoritative reference implementation. There is no licensing barrier to decoding it.

Why are there so many H02 device models?

Sinotrack alone sells under multiple branded names (Sinotrack, Sinotrack Direct, plus dozens of European/American resellers re-labeling the same hardware). Add Cantrack and Secumore and the long tail of AliExpress no-name clones · easily 100+ distinct model numbers ship the same H02 wire protocol.

Does H02 work over 4G LTE?

Yes on the newer Sinotrack 4G hardware. Same ASCII protocol, just over LTE Cat-1 or Cat-M1 modems instead of 2G GPRS. The protocol is transport-agnostic at the application layer.

Can I use an H02 device with both Traxelio and another tracking server in parallel?

Most H02 firmware allows only one server endpoint at a time · pick one. Some Sinotrack firmware variants support a second backup server for failover, but that's not the same as dual-streaming. For genuine parallel tracking (Traxelio + another platform), Wialon Retranslator (server-to-server) is the cleaner pattern.

What's the BR00 message type?

BR00 is an extended binary record some H02 devices use for higher-frequency position bursts (1-second intervals during alarm events, for example). It piggybacks on the same connection as V1 ASCII records. Traxelio decodes both transparently · the dashboard doesn't surface the difference.

T
Trax
Online
Say hello to Trax!