GT30 on TCP 5131: $$ plus hex length, 14-char device id, hex type, optional alarm, then hhmmss.sss A/V lat/lon.
On Traxelio
Point this protocol at Traxelio
Confirm a newline ASCII line that opens $$ with a 14-character device id and an A/V sentence. Not 0x6868 and not $GM.
Configure only GT30 to TCP 5131. GT30 on 5131 is not GT02 on 5022 or GPS Marker on 5057.
GT30 has no reply byte. A parsed A-status sentence is enough.
Send one $$ sentence whose status is A on 5131 and verify a map point. V will not plot.
Still offline after GPS lock
GT30 on 5131 is not GT02 on 5022 or GPS Marker on 5057.
Status must be A. A V status binds the device id and will not plot.
This dialect has no reply byte. Check the map, not the socket for an ACK.
FAQ
No. GT30 is $$ then hex length, a 14-character device id, a hex type, optional alarm character, then an A/V sentence.
A plots. V is void and will not plot.
No. There is no reply. A parsed A-status sentence is the whole handshake.
0x01, 0x02, and 0x03 are SOS. 0x10 is low battery. 0x11 is overspeed. 0x12 is geofence. The alarm character is optional.
This dialect is positions only. There is no SMS family on this row.