Freematics Protocol (PID hex key=value)
Freematics on UDP 5117: unit-id# hex PID pairs (0xA lat, 0xB lon) or EV= events, closed by *sum.
On Traxelio
What Freematics trackers do once they are on Traxelio
Hardware that speaks this protocol
Devices that speak Freematics
Point this protocol at Traxelio
Point Freematics at Traxelio
-
1
Capture a Freematics fingerprint
Confirm unit-id# then hex keys such as 0xA= and 0xB=, or an EV= sentence, then *checksum.
-
2
Point Freematics at 5117
Configure only Freematics to UDP 5117. Freematics on 5117 is not Freedom on 5066 or Flex API on 5235.
-
3
Treat EV replies as events only
An EV= sentence may get 1#EV=...,RX=1,TS=...*. That reply is not a map point.
-
4
Prove one Freematics fix
Send one 0x0 block whose 0xA and 0xB parse and verify a map point.
Still offline after GPS lock
Freematics still not landing
- Freematics aimed at the wrong port
Freematics on 5117 is not Freedom on 5066 or Flex API on 5235.
- Only EV, empty map
EV= can get RX=1. A plot needs 0xA and 0xB. VIN without those keys reuses the last point.
- Lat: labels sent here
Freedom Lat: Lon: Spd: labels will not parse as hex PID keys. Move Freedom units to 5066.
FAQ
Freematics leftover questions
Which hex keys plot a Freematics fix?
0xA is latitude. 0xB is longitude. A 0x0 key starts a new block.
Does an EV-only Freematics sentence plot?
No. EV= can get RX=1. VIN without 0xA and 0xB reuses the last point.
Does Freematics send an ACK?
Only EV= sentences: 1#EV=...,RX=1,TS=...* plus a checksum. Position blocks have no reply.
How does a Freematics sentence wrap?
Unit id, then #, then pairs, then * and a checksum. A line that misses # or * is dropped.
Can a Freematics unit run SMS setup or a controlled-action flow?
This dialect is positions only. There is no SMS family on this row.