PT215 Protocol (XX binary 0x10 / 0x11)
PT215 on TCP 5197: XX binary, login 0x01, live GPS 0x10 or stored 0x11, lat/lon /60/30000, XX CRLF reply.
On Traxelio
What PT215 trackers do once they are on Traxelio
Point this protocol at Traxelio
Point PT215 at Traxelio
-
1
Capture a PT215 fingerprint
Confirm a binary frame that opens XX with type 0x01, 0x10, or 0x11, not a 0x7878 login and not %imei,$GPRMC.
-
2
Point PT215 at 5197
Configure only PT215 to TCP 5197. PT215 on 5197 is not GT02 on 5022 or PT3000 on 5045.
-
3
Complete login, then a GPS body
Type 0x01 binds the IMEI and is answered XX CR LF. Type 0x10 or 0x11 carries the fix.
-
4
Prove one PT215 fix
Send one 0x10 or 0x11 body whose flags bit 12 is set on 5197 and verify a map point.
Still offline after GPS lock
PT215 still not landing
- PT215 aimed at the wrong port
PT215 on 5197 is not GT02 on 5022 or PT3000 on 5045.
- Session up, empty map
Login 0x01 and heartbeat 0x08 bind the unit and will not plot. Send 0x10 or 0x11 with flags bit 12 set.
- Looked for 0x7878
This dialect opens ASCII XX. Concox 0x7878 belongs on 5023, not here.
FAQ
PT215 leftover questions
Does PT215 send Concox 0x7878 frames?
No. PT215 opens ASCII XX then a type byte. Login is 0x01. Live GPS is 0x10. Stored GPS is 0x11. Concox families use 0x7878 binary login.
Which type bytes plot a PT215 fix?
0x10 live GPS and 0x11 stored GPS plot when flags bit 12 is set. Login 0x01 binds the unit. Heartbeat 0x08 and status 0x13 do not plot.
What reply does a PT215 login get?
ASCII XX, a length byte, type 0x01, then CR LF. A GPS reply echoes the six datetime bytes after the type.
How is the PT215 IMEI packed?
Eight bytes after the type on a 0x01 login. Read as hex and drop the leading nibble so 15 digits remain.
Can a PT215 unit run SMS setup or a controlled-action flow?
This dialect is positions only. There is no SMS family on this row.