Trackbox Protocol (a=connect + hhmmss CSV)
Trackbox on TCP 5068: a=connect i=id then hhmmss.sss CSV; fix digit greater than 0 plots; reply =OK=.
On Traxelio
What Trackbox trackers do once they are on Traxelio
Point this protocol at Traxelio
Point Trackbox at Traxelio
-
1
Capture a Trackbox fingerprint
Confirm an a=connect line with i= then the unit id, then a hhmmss.sss CSV. This is not a ^TM line.
-
2
Point Trackbox at 5068
Configure only Trackbox to TCP 5068. Trackbox on 5068 is not TrakMate on 5127 or TranSync on 5247.
-
3
Wait for =OK=
Traxelio answers =OK= after a=connect and after each parsed CSV row.
-
4
Prove one Trackbox fix
Send one hhmmss.sss CSV whose fix digit is greater than 0 on 5068 and verify a map point.
Still offline after GPS lock
Trackbox still not landing
- Trackbox aimed at the wrong port
Trackbox on 5068 is not TrakMate ^TM on 5127 or TranSync binary on 5247.
- Session up, empty map
Fix digit must be greater than 0. Digit 0 will not plot. CSV before a=connect will not bind.
- CSV without a=connect
Send a=connect with i= then the unit id first. A CSV row alone will not bind.
FAQ
Trackbox leftover questions
Does Trackbox send Concox 0x7878 frames?
No. Trackbox opens with a=connect then a time-first CSV. Concox families use 0x7878 binary login.
Which fix digit plots a Trackbox point?
Any digit greater than 0 plots. Digit 0 will not plot.
How does Trackbox answer?
=OK= after a successful a=connect and after each parsed CSV row.
Where is the Trackbox unit id?
After i= on the a=connect line.
What is the first CSV field on Trackbox?
hhmmss.sss time, then latitude, then longitude, then HDOP and altitude. Knots land as speed.