PST Protocol (0x05 status / tag 0x10 GPS)
PST on 5207: paren-wrapped id+version+index, type 0x05 status, tag 0x10 GPS, 0x00 CRC16 XMODEM reply.
On Traxelio
What PST trackers do once they are on Traxelio
Point this protocol at Traxelio
Point PST at Traxelio
-
1
Capture a PST fingerprint
Confirm a paren-wrapped binary record: unit id, version, index, type 0x05. Reject Progress LE type/length and PUI JSON.
-
2
Point PST at 5207
Configure only PST to 5207 as TCP or UDP. PST on 5207 is not Progress on 5012 or PUI on 5249.
-
3
Expect the 0x00 CRC16 reply
Traxelio echoes id, version, index, then 0x00, the original type, and CRC16 XMODEM. That reply is not a map point.
-
4
Prove one PST fix
Send one type 0x05 whose tags include 0x10 lat/lon on 5207 and verify a map point.
Still offline after GPS lock
PST still not landing
- PST aimed at the wrong port
PST on 5207 is not Progress on 5012 or PUI on 5249.
- Session up, empty map
Type 0x05 without tag 0x10 binds the unit and will not plot. Tag 0x09 and 0x0D do not invent coordinates.
- Saw 0x00 reply, assumed a fix
Every record is answered 0x00 plus CRC16 XMODEM. Check the map for a tag 0x10 body, not the socket.
FAQ
PST leftover questions
Does PST send Concox 0x7878 frames?
No. PST is binary id, version, index, then a type byte. Status is 0x05. GPS is tag 0x10. Concox families use 0x7878 binary login.
Which PST tag plots a fix?
Tag 0x10 carries packed lat/lon and plots. Tag 0x0D stores battery percent. Tag 0x09 stores sensor bytes and will not plot.
What reply does a PST unit get?
The same id, version, and index, then 0x00, the original type, and a CRC16 XMODEM. That reply is not a map point.
How is the PST unit id packed?
The first four bytes are an unsigned 32-bit integer used as the unit id, before the version byte and the index.
Can a PST unit run a controlled-action flow?
This dialect is positions only. A remote cut-relay is not offered on this row.