Satsol Protocol (LE binary 0x4CBF ACK)
Satsol on TCP 5184: little-endian binary, unit id after preamble, valid byte plots, ACK preamble 0x4CBF.
On Traxelio
What Satsol trackers do once they are on Traxelio
Point this protocol at Traxelio
Point Satsol at Traxelio
-
1
Capture a Satsol fingerprint
Confirm a little-endian envelope whose fourth field is the 32-bit unit id.
-
2
Point Satsol at 5184
Configure only Satsol to TCP 5184. Satsol on 5184 is not Sabertek on 5166 or Siwi on 5135.
-
3
Wait for the 0x4CBF ACK
A known unit is answered with preamble 0x4CBF, the same unit id, and CRC-16.
-
4
Prove one Satsol fix
Send one record whose valid byte is greater than 0 on 5184 and verify a map point.
Still offline after GPS lock
Satsol still not landing
- Satsol aimed at the wrong port
Satsol on 5184 is not Sabertek on 5166 or Siwi on 5135.
- Session up, empty map
The valid byte must be greater than 0. A bind-only envelope will not plot.
- No 0x4CBF, assumed dead
This dialect answers 0x4CBF plus CRC-16. If the map is empty, check the valid byte, not only the ACK.
FAQ
Satsol leftover questions
Does Satsol send Concox 0x7878 frames?
No. Satsol sends a little-endian binary envelope and Traxelio replies with preamble 0x4CBF.
Which byte plots a Satsol fix?
A valid byte greater than 0. Latitude and longitude are unsigned / 1e6.
Does Satsol send an ACK?
Yes. The reply carries preamble 0x4CBF, the same unit id, a zero length, and a CRC-16.
Where is the Satsol unit id?
After the checksum and preamble, a little-endian 32-bit value.
Can a Satsol unit run SMS setup or a controlled-action flow?
This dialect is positions only. There is no SMS family on this row.