FOX Protocol (id= data= A/V CSV)
FOX on TCP 5105: id= and data= wrap, then status-id, A or V, ddmmyy, hhmmss, NMEA lat/lon, plus input and power.
On Traxelio
What Fox trackers do once they are on Traxelio
Hardware that speaks this protocol
Devices that speak Fox
Point this protocol at Traxelio
Point Fox at Traxelio
-
1
Capture a FOX fingerprint
Confirm a line that carries id= and data= with a status id and an A or V letter. Reject UNITSTAT as Flextrack.
-
2
Point FOX at 5105
Configure only FOX to TCP 5105. FOX on 5105 is not Flextrack on 5090 or GNX on 5106.
-
3
Do not wait for an ACK
FOX has no reply byte. A parsed A-status data CSV is enough.
-
4
Prove one FOX fix
Send one data CSV whose status is A on 5105 and verify a map point.
Still offline after GPS lock
Fox still not landing
- FOX aimed at the wrong port
FOX on 5105 is not Flextrack UNITSTAT on 5090 or GNX $GNX_ on 5106.
- Session up, empty map
Status must be A. A V status binds the id and will not plot.
- No ACK, assumed dead
This dialect has no reply byte. Check the map, not the socket for an ACK.
FAQ
Fox leftover questions
Does FOX send Concox 0x7878 frames?
No. FOX wraps a unit id in id= and a data= A/V CSV. Concox families use 0x7878 binary login.
Which letter plots a FOX fix?
A plots. V is void and will not plot.
Does FOX send an ACK?
No. There is no reply byte. A parsed A-status data CSV is the whole handshake.
Where is the FOX unit id?
In the id= attribute, immediately before the data= CSV.
Can a FOX unit run SMS setup or a controlled-action flow?
This dialect is positions only. There is no SMS family on this row.