R12W Protocol ($HX type 0001 ACK)
R12W on TCP 5226: $HX CSV type 0001 binds the id and replies $HX,1001 with OK and XOR; that ACK does not plot.
On Traxelio
What R12W trackers do once they are on Traxelio
Point this protocol at Traxelio
Point R12W at Traxelio
-
1
Capture an R12W fingerprint
Confirm a comma line that opens $HX with type 0001 and a unit id in field 3.
-
2
Point R12W at 5226
Configure only R12W to TCP 5226. R12W on 5226 is not R16H on 5266.
-
3
Expect 1001 OK
Type 0001 is answered $HX,1001 with OK and a two-hex XOR. That reply is not a map point.
-
4
Do not wait for a map from 0001
The 0001 handshake binds the id and does not plot. @GPSD belongs on R16H 5266.
Still offline after GPS lock
R12W still not landing
- R12W aimed at the wrong port
R12W on 5226 is not R16H on 5266.
- Got 1001 OK, empty map
Expected. Type 0001 binds the id and does not plot a map.
- Sent @GPSD to 5226
@GPSD/@LBSD/@LINK belong on R16H 5266. R12W is $HX type 0001.
FAQ
R12W leftover questions
Does R12W send Concox 0x7878 frames?
No. R12W is $HX comma CSV. Concox families use 0x7878 binary login.
Which R12W type gets a 1001 OK reply?
Type 0001. Traxelio answers $HX,1001 with OK and a two-hex XOR.
Does the R12W 1001 OK reply plot a map?
No. Type 0001 binds the unit id and is dropped. That handshake has no lat/lon.
Where is the R12W unit id?
Third comma field, after $HX and the type word.
Can an R12W unit run SMS setup or a controlled-action flow?
This dialect is positions only. There is no SMS family on this row.