ASCII TCP uplink used by Sinotrack, Cantrack, and Secumore on gps.traxelio.com port 5013. Position rows are *HQ,...# hash-delimited sentences, the cousin of GPS103. Point the tracker here, confirm the IMEI, then Traxelio decodes the stream.
On Traxelio
Get alerted when vehicles cross boundaries
Driver scoring software to reduce accidents and insurance costs
Automated maintenance scheduling that prevents breakdowns
Every trip recorded, every dispute settled
Immobilizer requests for compatible installations
Hardware that speaks this protocol
Who ships hardware on this wire
Point this protocol at Traxelio
H02 devices have no UI to surface APN failures · test the SIM in a phone first.
Send apn,your_carrier_apn# to the device's SIM. APN must be set before any TCP attempt.
Send server,0,your-server.com,5013,0# (Sinotrack syntax). Vendor variants: Cantrack uses similar; Secumore uses setserver. Check the model's command sheet.
Send mode,1# (Sinotrack) to prevent UDP keep-alive garbage on the TCP listener. Some H02 firmware mixes them by default.
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.
Replace {password} with the tracker PIN or password.
What Traxelio surfaces from these packets
Still offline after GPS lock
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.
These symptoms are answered outside this section:
FAQ
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.
