TCP/UDP wire protocol published by Gurtam · the format most GPS trackers use to push positions, sensors, and events to a Wialon-compatible server (Wialon Hosting, Wialon Local, or Traxelio).
On Traxelio
Hardware that speaks this protocol
Point this protocol at Traxelio
Open your tracker's existing configurator (or check the SMS-command sheet for the model). Note the current server IP + port so you can roll back if anything goes wrong.
Set the destination to your platform's IP and port. Gurtam's reference port is 20332 but Wialon IPS is port-flexible · use whatever your server listens on. Transport: TCP. The IMEI and SIM stay the same.
Most Wialon-IPS-compatible firmware applies the new server on the next boot. Some devices accept a remote #REBOOT# command if you can't physically access the unit.
After GPS lock, confirm the first decoded position in Traxelio. If nothing arrives in 5 min, check the device's raw log for outbound TCP attempts on the port · no attempts means the SIM's data session isn't open (APN, airtime, roaming block).
Still offline after GPS lock
Verify the server IP and port were actually written back to the device (some configurators silently keep a draft). Power-cycle the tracker, then check its raw log for an outbound TCP attempt on the new IP. If the attempt never leaves the device, the SIM probably has no data session · check airtime + APN before assuming a protocol issue.
Sensor channels ride in the #D# (full data) packets, not #SD# (shortened). Some devices default to #SD# to save GPRS bytes. Re-enable full data in the configurator (Teltonika: Codec settings; Concox: extended mode; Queclink: AT+GTCFG sensor opcodes).
Expected. Retranslator is a server-to-server feed · it ships after the source platform has decoded, persisted, and queued the record. For live, point the device directly at Traxelio over Wialon IPS (cuts out the source platform's queue).