WLI Protocol (wli: bind + field 52)
WLI on TCP 5209: 0xDB stuffed binary closed by 0x03, wli: class-2 bind, class-1 field 52 plots.
On Traxelio
What Wli trackers do once they are on Traxelio
Hardware that speaks this protocol
Devices that speak Wli
Point this protocol at Traxelio
Point Wli at Traxelio
-
1
Capture a WLI fingerprint
Confirm a 0xDB stuffed record that closes on 0x03, with a class-2 wli: bind line.
-
2
Point WLI at 5209
Configure only WLI to TCP 5209. WLI on 5209 is not Watch on 5093 or Wondex on 5032.
-
3
Do not wait for a reply
WLI has no reply byte. A parsed field 52 is enough.
-
4
Prove one WLI fix
Send one class-1 record whose field 52 is present on 5209 and verify a map point.
Still offline after GPS lock
Wli still not landing
- WLI aimed at the wrong port
WLI on 5209 is not Watch [makerid] on 5093 or Wondex $OK: on 5032.
- wli: up, empty map
A class-2 wli: line only binds the session. A map point needs class 1 field 52.
- No reply, assumed dead
This dialect has no reply byte. Check the map, not the socket for an ACK.
FAQ
Wli leftover questions
Does WLI send Concox 0x7878 frames?
No. WLI destuffs 0xDB pairs, closes on 0x03, binds with wli: on class 2, and plots on class 1 field 52. Concox families use 0x7878 binary login.
Which WLI field plots a new map point?
Field 52 on a class 1 record. A class 2 wli: line only binds. Type 0xE4 reuses the last point.
Does WLI send a reply byte?
No. There is no reply byte. A parsed field 52 is the whole handshake.
Where is the WLI unit id?
After the wli: prefix on a class 2 line.
Can a WLI unit run SMS setup or a controlled-action flow?
This dialect is positions only. There is no SMS family on this row.