Neos Protocol (>id CSV *xx!)
Neos on UDP 5183: >8-digit id, status, valid 0/1, yymmdd, hhmmss, hem-first lat/lon, reply $OK!.
On Traxelio
What Neos trackers do once they are on Traxelio
Hardware that speaks this protocol
Devices that speak Neos
Point this protocol at Traxelio
Point Neos at Traxelio
-
1
Capture a Neos fingerprint
Confirm a line that opens with > and an 8-digit id and ends *xx!, not a $GPRMC wrap.
-
2
Point Neos at 5183
Configure only Neos to UDP 5183. Neos on 5183 is not Hunter PRO on 5116 or NET on 5215.
-
3
Wait for $OK!
Traxelio answers $OK!. That reply is not proof of a map point.
-
4
Prove one Neos fix
Send one line whose valid digit is 1 on 5183 and verify a map point.
Still offline after GPS lock
Neos still not landing
- Neos aimed at the wrong port
Neos on 5183 is not Hunter PRO on 5116 or NET on 5215.
- Session up, empty map
Valid digit must be 1. Digit 0 is void and will not plot. $OK! alone is not a plot.
- Sent $GPRMC to 5183
id<$GPRMC belongs on Hunter PRO 5116. This listen wants >8-digit CSV ending *xx!.
FAQ
Neos leftover questions
Does Neos send a $GPRMC sentence?
No. Neos sends a >8-digit CSV that ends *xx!. Hunter PRO wraps a unit id in > < and then sends $GPRMC.
Which digit marks a valid Neos fix?
1 plots. 0 is void and will not plot.
What reply does a Neos datagram get?
$OK!. That reply is not proof of a map point.
Where is the Neos unit id?
Eight digits immediately after the opening >, before the first comma.
Can a Neos unit run SMS setup or a controlled-action flow?
This dialect is positions only. There is no SMS family on this row.