Watch Protocol ([maker*id*] UD/AL)
Watch on TCP 5093: [maker*id*len*TYPE] ASCII, UD/AL/WT with A or V, INIT and LK answered.
On Traxelio
What Watch trackers do once they are on Traxelio
Hardware that speaks this protocol
Devices that speak Watch
Point this protocol at Traxelio
Point Watch at Traxelio
-
1
Capture a Watch fingerprint
Confirm a bracket line with two maker letters, asterisks, a unit id, and a type such as UD, AL, or LK.
-
2
Point Watch at 5093
Configure only Watch to TCP 5093. Watch on 5093 is not Wondex on 5032 or TK102 on 5036.
-
3
Complete INIT and LK
INIT is answered INIT,1. LK is answered LK. Neither reply is a map point.
-
4
Prove one Watch fix
Send one UD, AL, or WT sentence whose status is A on 5093 and verify a map point.
Still offline after GPS lock
Watch still not landing
- Watch aimed at the wrong port
Watch on 5093 is not Wondex $OK: on 5032 or TK102 binary brackets on 5036.
- LK up, empty map
LK only keeps the socket and may attach steps and battery. A map point needs UD, AL, or WT with status A.
- Status V, assumed broken listener
A plots. V binds the id and will not plot.
FAQ
Watch leftover questions
Does Watch send Concox 0x7878 frames?
No. Watch wraps ASCII in square brackets with asterisk fields and types such as UD, AL, and LK. Concox families use 0x7878 binary login.
Which letter plots a Watch fix?
A plots. V is void and will not plot.
What reply follows INIT and LK?
INIT is answered INIT,1. LK is answered LK. Those replies are not a map point.
Where is the Watch unit id?
Between the first two asterisks after the two maker letters, immediately after the opening bracket.
Can a Watch unit run SMS setup or a controlled-action flow?
SMS setup on this row follows the Xexun adminip family. The 5093 dialect is positions only. A remote cut-relay is not offered here.