Siwi Protocol ($LETTER, id CSV)
Siwi on TCP 5135: $LETTER header, numeric id, reason letter, ignition 0/1, A/V decimal lat/lon, India Standard Time; no reply.
On Traxelio
What Siwi trackers do once they are on Traxelio
Point this protocol at Traxelio
Point Siwi at Traxelio
-
1
Capture a Siwi fingerprint
Confirm a line that opens $ then uppercase letters, a numeric key, a reason letter, and A or V.
-
2
Point Siwi at 5135
Configure only Siwi to TCP 5135. Siwi on 5135 is not Raveon on 5117 or Megastek on 5024.
-
3
Do not wait for a reply
Siwi has no reply byte. A parsed A-status line is enough.
-
4
Prove one Siwi fix
Send one $LETTER line whose status is A on 5135 and verify a map point.
Still offline after GPS lock
Siwi still not landing
- Siwi aimed at the wrong port
Siwi on 5135 is not Raveon on 5117 or Megastek on 5024.
- Session up, empty map
Status must be A. A V status binds the numeric key and will not plot.
- No reply, assumed dead
This dialect has no reply byte. Check the map, not the socket for an echo.
FAQ
Siwi leftover questions
Does Siwi send Concox 0x7878 frames?
No. Siwi opens with $ then uppercase letters, a numeric unit key, a reason letter, then A/V decimal lat/lon.
Which letter plots a Siwi fix?
A plots. V is void and will not plot.
Does Siwi send a reply?
No. There is no reply byte. A parsed A-status line is the whole handshake.
How is the Siwi clock stamped?
As India Standard Time, from the hhmmss time field and the ddmmyy date field.
Can a Siwi unit run SMS setup or a controlled-action flow?
This dialect is positions only. There is no SMS family on this row.