1 device 1 brand

GT30 Protocol ($$ length / A/V sentence)

GT30 on TCP 5131: $$ plus hex length, 14-char device id, hex type, optional alarm, then hhmmss.sss A/V lat/lon.

Positions go to this server

gps.traxelio.com:5131 TCP
I already have a tracker

Connect your tracker

Enter your tracker IMEI to see whether Traxelio recognizes the model before you start setup.

Hardware that speaks this protocol

Devices that speak GT30

Point this protocol at Traxelio

Point GT30 at Traxelio

  1. 1

    Capture a GT30 fingerprint

    Confirm a newline ASCII line that opens $$ with a 14-character device id and an A/V sentence. Not 0x6868 and not $GM.

  2. 2

    Point GT30 at 5131

    Configure only GT30 to TCP 5131. GT30 on 5131 is not GT02 on 5022 or GPS Marker on 5057.

  3. 3

    Do not wait for a reply

    GT30 has no reply byte. A parsed A-status sentence is enough.

  4. 4

    Prove one GT30 fix

    Send one $$ sentence whose status is A on 5131 and verify a map point. V will not plot.

Still offline after GPS lock

GT30 still not landing

GT30 aimed at the wrong port

GT30 on 5131 is not GT02 on 5022 or GPS Marker on 5057.

Session up, empty map

Status must be A. A V status binds the device id and will not plot.

No reply, assumed dead

This dialect has no reply byte. Check the map, not the socket for an ACK.

FAQ

GT30 leftover questions

Does GT30 send GT02 0x6868 frames?

No. GT30 is $$ then hex length, a 14-character device id, a hex type, optional alarm character, then an A/V sentence.

Which letter plots a GT30 fix?

A plots. V is void and will not plot.

Does GT30 send a reply byte?

No. There is no reply. A parsed A-status sentence is the whole handshake.

Which GT30 alarm values map to SOS or low battery?

0x01, 0x02, and 0x03 are SOS. 0x10 is low battery. 0x11 is overspeed. 0x12 is geofence. The alarm character is optional.

Can a GT30 unit run SMS setup or a controlled-action flow?

This dialect is positions only. There is no SMS family on this row.

T
Trax
Online
Say hello to Trax!