Snapper Protocol (P ping / K JSON GPS)
Snapper on TCP 5256: P ping answers PO, K-framed JSON GPS with la/lo, flag bit 3 required, type 0x01 replies hello.
On Traxelio
What Snapper trackers do once they are on Traxelio
Point this protocol at Traxelio
Point Snapper at Traxelio
-
1
Capture a Snapper fingerprint
Confirm a 2-byte P ping or a length-prefixed record whose GPS body is JSON with la and lo.
-
2
Point Snapper at 5256
Configure only Snapper to TCP 5256. Snapper on 5256 is not Smokey on 5125 or Solar Powered on 5201.
-
3
Treat PO and K replies as handshake, not a fix
A P ping gets PO. Type 0x01 gets hello. Other types get OK. None of those replies plot.
-
4
Prove one Snapper fix
Send one type 0x32 JSON record with flag bit 3 and la/lo on 5256 and verify a map point.
Still offline after GPS lock
Snapper still not landing
- Snapper aimed at the wrong port
Snapper on 5256 is not Smokey on 5125 or Solar Powered on 5201.
- Got PO or hello, empty map
PO and hello are handshake replies. Wait for type 0x32 JSON whose flag bit 3 is set.
- JSON arrived, empty map
Flag bit 3 must be set or the GPS JSON is ignored. Flag bit 1 is validity. Type 0x21 and 0x23 reuse last known coordinates.
FAQ
Snapper leftover questions
Does Snapper send Concox 0x7878 frames?
No. Snapper is a P ping or a K-wrapped JSON GPS body with la and lo. Concox families use 0x7878 binary login.
What answers a Snapper P ping?
PO (0x50 0x4F). That two-byte reply is not a map point.
Which JSON keys carry a Snapper fix?
la is latitude (two degree digits plus minutes). lo is longitude (three degree digits plus minutes). f is hex flags. d and t make ddMMyyHHmmss.
Which Snapper flag bit must be set?
Bit 3 must be set or the GPS JSON is ignored. Bit 1 is validity. Type 0x21 events and 0x23 tech slots reuse last known coordinates.
Can a Snapper unit run SMS setup or a controlled-action flow?
This dialect is positions only. The Snapper GN8 is the listed device. There is no SMS family on this row.