Pacific Track Protocol (bit-ext segment binary)
Pacific Track on UDP 5198: start byte, bit-extended segments, 0x100 IMEI, 0x10 fix with lat-90 lon-180, no ACK.
On Traxelio
What Pacifictrack trackers do once they are on Traxelio
Point this protocol at Traxelio
Point Pacifictrack at Traxelio
-
1
Capture a Pacific Track fingerprint
Confirm a UDP datagram with a start byte and a 0x100 IMEI segment.
-
2
Point Pacific Track at 5198
Configure only Pacific Track to UDP 5198. Pacific Track on 5198 is not Path Away on 5099 or Plugin on 5192.
-
3
Do not wait for an ACK
Pacific Track has no reply byte. A parsed 0x10 segment is enough.
-
4
Prove one Pacific Track fix
Send one 0x10 segment whose bit 4 is set on 5198 and verify a map point.
Still offline after GPS lock
Pacifictrack still not landing
- Pacific Track aimed at the wrong port
Pacific Track on 5198 is not Path Away on 5099 or Plugin on 5192.
- Session up, empty map
Segment 0x10 must be present and bit 4 set. IMEI-only datagrams reuse the last point and will not invent a new fix.
- No ACK, assumed dead
This dialect has no reply byte. Check the map, not the socket for an ACK.
FAQ
Pacifictrack leftover questions
Does Pacific Track send Concox 0x7878 frames?
No. Pacific Track sends a start byte then bit-extended segments, including 0x100 for the IMEI and 0x10 for the fix.
Which segment plots a Pacific Track fix?
Segment 0x10. Valid is bit 4 of that segment's first byte. Latitude is unsigned / 1e6 minus 90.
Does Pacific Track send an ACK?
No. There is no reply byte. A parsed 0x10 segment is the whole handshake.
Where is the Pacific Track unit id?
In segment 0x100: eight raw bytes, first 15 hex digits.
Can a Pacific Track unit run SMS setup or a controlled-action flow?
This dialect is positions only. There is no SMS family on this row.