BlackKite Protocol (Galileo-length tagged binary)
BlackKite on TCP 5091: Galileo-length tagged binary, IMEI 0x03, coords 0x30, ack 0x02 plus checksum.
On Traxelio
What Blackkite trackers do once they are on Traxelio
Hardware that speaks this protocol
Devices that speak Blackkite
Point this protocol at Traxelio
Point Blackkite at Traxelio
-
1
Capture a BlackKite fingerprint
Confirm tagged binary with 0x03 then 0x30, not Arnavi $AV or 0xFF versions.
-
2
Point BlackKite at 5091
Configure only BlackKite to TCP 5091. BlackKite on 5091 is not Galileo on 5034 or Arnavi on 5100.
-
3
Expect 0x02 plus checksum
Traxelio replies 0x02 then a little-endian checksum. A missing reply causes retries.
-
4
Prove one BlackKite fix
Send one batch with tags 0x20 and 0x30 and a 0x00 validity high nibble, then verify a map point.
Still offline after GPS lock
Blackkite still not landing
- BlackKite aimed at the wrong port
BlackKite on 5091 is not Galileo on 5034 or Arnavi on 5100.
- Session up, empty map
A fix needs tags 0x20 and 0x30 together. IMEI tag 0x03 alone will not plot.
- Unit retries after silence
This dialect expects 0x02 plus a little-endian checksum. Check the map after that three-byte reply.
FAQ
Blackkite leftover questions
Does BlackKite send Concox 0x7878 frames?
No. BlackKite is tagged binary: tag 0x03 then later 0x30 for a fix.
Which tags must land before a BlackKite map point?
Tag 0x20 (Unix time) and tag 0x30 (lat/lon). Either alone will not plot.
How does BlackKite acknowledge a batch?
Byte 0x02 then a little-endian checksum.
Where is the BlackKite unit id?
Tag 0x03 carries fifteen ASCII digits.
Can a BlackKite unit run SMS setup or a controlled-action flow?
This dialect is positions only. There is no SMS family on this row.