OKO Protocol ({ IMEI A/V CSV)
OKO on TCP 5152: { optional 15-digit IMEI, hhmmss, A or V, packed lat/lon, reverse date, sats, ADC, event, power.
On Traxelio
What Oko trackers do once they are on Traxelio
Hardware that speaks this protocol
Devices that speak Oko
Point this protocol at Traxelio
Point Oko at Traxelio
-
1
Capture an OKO fingerprint
Confirm a brace line that opens with { and carries A or V after the time field.
-
2
Point OKO at 5152
Configure only OKO to TCP 5152. OKO on 5152 is not Hunter PRO on 5116 or Omnicomm on 5203.
-
3
Do not wait for an ACK
OKO has no reply byte. A parsed A-status line is enough.
-
4
Prove one OKO fix
Send one brace sentence whose status is A on 5152 and verify a map point.
Still offline after GPS lock
Oko still not landing
- OKO aimed at the wrong port
OKO on 5152 is not Hunter PRO on 5116 or Omnicomm on 5203.
- Session up, empty map
Status must be A. A V status can bind the IMEI and will not plot.
- No ACK, assumed dead
This dialect has no reply byte. Check the map, not the socket for an ACK.
FAQ
Oko leftover questions
Does OKO send Concox 0x7878 frames?
No. OKO is a brace ASCII CSV that opens with { and optional IMEI. Concox families use 0x7878 binary login.
Which letter plots an OKO fix?
A plots. V is void and will not plot.
Does OKO send an ACK?
No. There is no reply byte. A parsed brace line is the whole handshake.
Must an OKO line carry an IMEI?
No. The 15-digit IMEI after the opening brace is optional. Time, A or V, and packed lat/lon still have to be present.
Can an OKO unit run SMS setup or a controlled-action flow?
This dialect is positions only. There is no SMS family on this row.