Skip to main content

Devices and trackers

A vehicle or trailer is tracked by a device fitted to it: a GPS tracker, a CAN reader, a video recorder, an e-seal or e-lock, a reefer unit, a fluid monitor, or the driver's phone.

Tracker health​

Trackers lists every tracker's state from its own telemetry, worst first:

GroupStates
Needs actionoffline (silent for N min), unplugged (off the vehicle's power, on its backup battery), no GPS, weak signal
Checknever reported since it was registered
Healthyreporting, powered, with signal
  • Offline after sets how long a silent tracker waits before it is offline. 10 minutes is the least; for example 240.
  • Fleet managers change the threshold. Dispatchers read the list. Mechanics cannot change the threshold.
  • The manager app's Overview lists Trackers needing action.

Register a device​

Trackers → All devices → Register device:

  1. Kind first: tracker, CAN / J1939 reader, e-seal, reefer, fluid monitor, video recorder (MDVR).
  2. Protocol: only the protocols that kind speaks are offered. The form says when none does yet.
  3. The IMEI or serial, model, maker, and Fit to a vehicle → Register device.

Or from the vehicle: its page → Fit a tracker → IMEI, Tracker protocol → Fit tracker.

A device with an IMEI the platform does not know is refused when it connects. So is a retired device. Editing a device keeps its protocol.

Protocols​

ProtocolDevicesNotes
Teltonikatrackers, CAN readers, e-seals, reefers, fluid monitorspositions, ignition, fuel level, driver keys, named temperature observations; commands
Concox / Jimi GT06trackerslogs in on its own port; heartbeat and SOS answered
Queclink @Track (GV55 family)trackersno login, the IMEI is in every message; buffered reports marked as re-sent; power cut, SOS, overspeed and tow as alarms; commands
JT/T 808video recorders (Streamax, Howen, Jimi and other MDVRs) and trackersregisters and authenticates; buffered positions at their own times; ADAS and driver-monitoring alarms; live video and footage; commands
Meitrack (T1, T333, T366, MVT380/600 and the T series)trackersset the device to ASCII AAA reports; binary CCC / CCE reports are refused; harsh driving counts in trips and scores; commands
Wialon IPStrackers, and units retranslated from a Wialon serverlogin checked; black-box records at their own times; compressed messages; 2.0 over UDP too (data only); no commands
Ruptela (FM-Eco4, FM-Pro4, FM-Tco4, Trace5, HCV5)trackersno login, the IMEI is in every packet; CAN engine RPM; commands over GPRS (outputs, engine cut, position, any SMS command), the tracker's answer shown
Huabao e-locks (JT/T 808)e-sealsseal armed with its number, battery, opened from the console; see Trailers

For Teltonika cold-chain monitoring, a named temperature observation needs an explicit trailer source binding; connectivity alone does not establish the probe's cargo location. Before relying on cargo alerts, confirm that the fitted tracker reports the chosen sensor channel and that the installer has verified the probe's physical location. See Cold chain.

Setting up a device​

  • Point the device at the platform's address and the port for its protocol.
  • Queclink: the device needs no login; set its server with AT+GTSRI.
  • JT/T 808: the protocol sets the recorder's clock to GMT+8, and the platform reads it so. A recorder set to GCC local time needs its offset set in its codec configuration. Set the live camera channels to H.264; browsers do not play H.265 live.
  • Huabao e-lock: enter its Command password (PIN) when registering. It is kept sealed and never shown again.

Move a fleet over from Wialon​

  1. Register each unit with Protocol Wialon IPS, and as its IMEI or serial the unit's id as the Wialon server sends it (its IMEI, or a name such as RCH-UNIT-07).
  2. On the Wialon server, add a retranslator with protocol Wialon IPS and the platform's address.
  3. Nothing changes on the trackers: the fleet can run on both while it moves.

A tracker that speaks Wialon IPS itself is pointed at the same port.

Drivers' phones as a tracker​

A vehicle without a hardware tracker can be tracked by its driver's phone, only while the driver is on a job and only once they agree.

  1. The fleet manager: Vehicles → the vehicle → the tracker card → Track with drivers' phones on. A phone device appears on the vehicle and in Trackers.
  2. The driver: driver app → Today → Phone tracking → Read and decide → the notice → I agree.
  3. Share my location (allow location on the phone). Sharing status shows Last sent: … within about 30 seconds.
  4. The console shows the vehicle where the phone is.
  • Pause sharing stops sending.
  • Account → My privacy → the notice → Withdraw my consent: nothing more reaches the vehicle.
  • Switching Track with drivers' phones off retires the phone device.