Kenji Protocol (>C id A/V CSV)
Kenji on TCP 5102: >C six-digit id CSV with A or V status, T speed, H course, and reverse date.
On Traxelio
What Kenji trackers do once they are on Traxelio
Point this protocol at Traxelio
Point Kenji at Traxelio
-
1
Capture a Kenji fingerprint
Confirm a line that opens with >C and a six-digit id, then M, O, I, and Dhhmmss.
-
2
Point Kenji at 5102
Configure only Kenji to TCP 5102. Kenji on 5102 is not Hunter PRO on 5116 or KHD on 5058.
-
3
Do not wait for an ACK
Kenji has no reply byte. A parsed A-status line is enough.
-
4
Prove one Kenji fix
Send one >C line whose status is A on 5102 and verify a map point.
Still offline after GPS lock
Kenji still not landing
- Kenji aimed at the wrong port
Kenji on 5102 is not Hunter PRO on 5116 or KHD on 5058.
- Session up, empty map
Status must be A. A V status binds the six-digit 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
Kenji leftover questions
Does Kenji send Concox 0x7878 frames?
No. Kenji is an ASCII >C CSV with typed M/O/I/D fields. Concox families use 0x7878 binary login.
Which letter plots a Kenji fix?
A plots. V is void and will not plot.
Does Kenji send an ACK?
No. There is no reply byte. A parsed >C line is the whole handshake.
Where is the Kenji unit id?
After >C, six digits, immediately before the M alarm word.
Can a Kenji unit run SMS setup or a controlled-action flow?
This dialect is positions only. There is no SMS family on this row.