GT02 on TCP 5022: 0x6868 length-field binary, type 0x10 fix, heartbeat 0x1A with Th 0x1A CRLF reply.
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
Point this protocol at Traxelio
Confirm a binary frame that opens 0x68 0x68 with type 0x10 or 0x1A, not a 0x7878 login.
Configure only GT02 to TCP 5022. GT02 on 5022 is not GT06 on 5023 or TK102 on 5036.
A 0x1A heartbeat is answered 0x54 0x68 0x1A 0x0D 0x0A. Type 0x10 has no reply byte.
Send one 0x10 body with flags bit 0 set on 5022 and verify a map point.
What Traxelio surfaces from these packets
Still offline after GPS lock
GT02 on 5022 is not GT06 on 5023 or TK102 on 5036.
Type 0x1A only keeps the session. A map point needs type 0x10 with flags bit 0 set.
0x7878 login belongs on GT06 5023. This listen wants 0x6868 with type 0x10 or 0x1A.
FAQ
No. GT02 opens 0x68 0x68 with type 0x10, 0x1A, or 0x1C. GT06 families use 0x7878 binary login.
0x10 plots when flags bit 0 is set. 0x1A is a heartbeat. 0x1C stores ASCII result text and will not move the map.
Bytes 0x54 0x68 0x1A 0x0D 0x0A. That exchange is not a map point.
Eight bytes after the power and GSM bytes. Read as hex and drop the leading nibble so 15 digits remain.
This dialect is positions only. There is no SMS family on this row.