Wondex / Wonde Proud SMS ($WP+COMMTYPE)
Connection supported
Read COMMTYPE
$WP+COMMTYPE={password},?
APN commands depend on the carrier SIM in your tracker, so they are not shown here.
Wondex on TCP 5032: 0xD0 echo bind, $OK:/$ERR:/$MSG: reuse last point, CSV with longitude then latitude.
On Traxelio
Hardware that speaks this protocol
Point this protocol at Traxelio
Confirm an 8-byte 0xD0 keepalive or a CR LF line that is $OK: or a CSV with longitude before latitude.
Configure only Wondex to TCP 5032. Wondex on 5032 is not Watch on 5093 or TK102 on 5036.
Traxelio echoes the eight 0xD0 bytes. That echo is not a map point.
Send one CSV whose satellite count is not 0 on 5032 and verify a map point.
Replace {password} with the tracker PIN or password.
Connection supported
Read COMMTYPE
$WP+COMMTYPE={password},?
APN commands depend on the carrier SIM in your tracker, so they are not shown here.
Still offline after GPS lock
Wondex on 5032 is not Watch [makerid] UD/AL on 5093 or TK102 binary brackets on 5036.
This CSV sends longitude first, then latitude. A Watch or Xexun sentence on 5032 will not decode.
These symptoms are answered outside this section:
FAQ
No. Wondex binds on an 8-byte 0xD0 echo, then sends ASCII closed by CR LF: either $OK: / $ERR: / $MSG: or a CSV with longitude before latitude. Concox families use 0x7878 binary login.
Any count other than 0 plots. A 0 count is void and will not plot.
No. Those lines reuse the last map point and only store the result text.
On the CSV line, the first run of digits after any non-digit prefix. On the 0xD0 echo, the reversed 32-bit word.
This dialect is positions only. There is no SMS family on this row.