StarLink Protocol ($SLU type 6)
StarLink on TCP 5136: $SLU then a 6-hex or 15-digit id, type 6 event report, tagged CSV, and a * checksum.
On Traxelio
What Starlink trackers do once they are on Traxelio
Hardware that speaks this protocol
Devices that speak Starlink
Point this protocol at Traxelio
Point Starlink at Traxelio
-
1
Capture a StarLink fingerprint
Confirm a line that contains SLU, a 6-hex or 15-digit id, type 6, and a trailing *xx.
-
2
Point StarLink at 5136
Configure only StarLink to TCP 5136. StarLink on 5136 is not Starcom on 5190 or Startek on 5222.
-
3
Do not wait for an ACK
StarLink has no reply byte. A parsed type 6 event report is enough.
-
4
Prove one StarLink fix
Send one type 6 line whose + or - latitude and longitude parse on 5136 and verify a map point.
Still offline after GPS lock
Starlink still not landing
- StarLink aimed at the wrong host path
StarLink on 5136 is not Starcom on 5190 or Startek on 5222.
- Session up, empty map
Only type 6 plots. Other types bind the 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
Starlink leftover questions
Does StarLink send Starcom |unit=| lines?
No. StarLink opens with SLU and ends with a star checksum. Starcom wraps |unit=| CSV.
Which type plots a StarLink fix?
Type 6, the event report. Any other type binds the unit and will not plot.
Where is the StarLink unit id?
Immediately after SLU: either 6 hex digits or 15 decimal digits, then a comma and the type.
Does StarLink send an ACK?
No. There is no reply byte. A parsed type 6 line is the whole handshake.
Can a StarLink unit run SMS setup or a controlled-action flow?
This dialect is positions only. There is no SMS family on this row.