Rinho
Guided setup available
Switch to TCP
>SCXIPTT<
APN commands depend on the carrier SIM in your tracker, so they are not shown here.
TAIP on 5031: > then RGP/REV/RPV/RUV, lat/lon, mph speed (km/h on RUV), ;ID= unit key, >ACK or >SAK reply.
On Traxelio
Hardware that speaks this protocol
Who ships hardware on this wire
Point this protocol at Traxelio
Confirm a > line with RGP, REV, RPV, or RUV and a ;ID= attribute before <.
Configure only TAIP to 5031. TAIP on 5031 is not Hunter PRO on 5116 or Cradlepoint on 5118.
Traxelio answers >ACK;*HH< or >SAK on #IP. Check the map, not only the socket.
Send one RGP or RUV sentence with lat/lon and a plotting fix mode, then verify a map point.
Guided setup available
Switch to TCP
>SCXIPTT<
APN commands depend on the carrier SIM in your tracker, so they are not shown here.
Still offline after GPS lock
TAIP on 5031 is not Hunter PRO on 5116 or Cradlepoint on 5118.
A line without ;ID= will not bind. A void fix mode will not plot. Check the map after one RGP with lat/lon.
Non-RUV speed is mph. RUV (Akroz) speed is km/h. Mix those and the trail looks wrong.
FAQ
No. TAIP is ASCII after > with RGP, REV, RPV, or RUV and a ;ID= attribute. Concox families use 0x7878 binary login.
RUV (Akroz) uses km/h. RGP, REV, and the other letter prefixes store speed in mph.
Yes. Traxelio replies >ACK with the # index and ID= plus XOR *HH<. An index that starts #IP is answered >SAK. No index echoes the ID= value.
In the ;ID= attribute before the closing <. IO=, SV=, BL=, and VO= are optional extras.
This dialect is positions only. There is no SMS family on this row.