Sending telematics data to Track Fleet


The platform can receive data not only directly from devices, but also with the help of supported retranslating protocols from other services. Currently, there are 3 such protocols – Wialon Retranslator, Wialon Combine, and Wialon IPS (We don’t have it as a generic protocol, but you can register one of the IPS compatible models.)

Let’s check how these protocols should be configured to send data to our server and what information we can get.

Wialon Retranslator

Wialon Retranslator protocol is intended for retranslating data via TCP in binary format. With the help of the protocol, you can transmit information about a device’s location and the values of sensors. The protocol can be easily extended and specific fields can be supported by processing them depending on the model.

Supported inputs

  • AVL IO: #1-100000
  • Battery voltage
  • CAN: Axle load: #1-8
  • CAN: Level of AdBlue fluid
  • CAN: RPM
  • CAN: Total fuel used
  • LLS: Level: #1-8
  • Temperature
  • Analog sensor: #1-16
  • Board voltage
  • CAN: Engine temperature
  • CAN: Mileage
  • CAN: Raw data: #1-16
  • External temperature: #1-10

Supported events

  • Deviation from the route
  • Distance between objects
  • Engine excessive idling
  • Entrance or exit from geofence
  • Excessive driving
  • Excessive parking
  • Fuel level change
  • GPS antenna cut
  • GPS signal lost/recover
  • GSM jamming
  • Inputs triggering
  • Outputs triggering
  • Parameter in range
  • Parking state detection
  • Pressing SOS button
  • Shake sensor
  • Speeding (platform related)
  • Task status change
  • Tracker switched OFF or lost connection

How to connect

To add a device to Navixy, register a new device with the ID. On the sender’s side specify the following tracking server IP address and port.

AU platform: https://gps.trackfleet.com.au/

Server port:

Wialon Combine

Wialon Combine protocol is intended for retranslating data via TCP or UDP in binary format. You can transmit telematics data and telemetry using it. The platform supports all custom fields from the protocol, so you can get any information from devices.

Supported inputs

  • Analog sensor: #1-32767
  • Counter: #1-32767
  • External temperature: #1-32767
  • CAN Parameter: #1-32767
  • Custom parameter: #1-32767
  • LLS: Level: #1-32767

Supported events

  • Deviation from the route
  • Distance between objects
  • Engine excessive idling
  • Entrance or exit from geofence
  • Excessive driving
  • Excessive parking
  • Fuel level change
  • Inputs triggering
  • Outputs triggering
  • Parameter in range
  • Parking state detection
  • Pressing SOS button
  • Speeding (platform related)
  • Task status change
  • Tracker switched OFF or lost connection

How to connect

To add a device to Navixy, register a new device with the ID. On the sender’s side specify the following tracking server IP address and port.

AU platform: https://gps.trackfleet.com.au/

Server port:

Wialon IPS

A text protocol over TCP that is easily extended by passing additional parameters in the #D message.

Message format

#D#date;time;lat1;lat2;lon1;lon2;speed;course;height;sats;hdop;inputs;outputs;adc;ibutton;params\r\n

params is a comma-separated set of additional parameters. Each parameter has a NAME:TYPE: VALUE construction.

NAME – any string, up to 15 bytes long, case insensitive,

TYPE – parameter type, 1 – integer, 2 – real number, 3 – string,

VALUE – value depending on the type. Some of the parameters are common and some are vendor-specific, the processing of these fields depends on the model.

General parameters

Field – description
  • SOS – SOS button alarm,
  • INTERVAL_MODE – the sign of a single-point route,
  • BatteryLevel – battery charge in percent,
  • b – battery charge in Volts,
  • a or LOC_RADIUS – location accuracy (radius) in meters,
  • LOC_SRC – navigation data source: 0 – GPS, 1 – GSM LBS,
  • pwr_ext – board voltage,
  • pwr_int – built-in battery voltage,
  • fuel level – fuel level in liters,
  • temperature – temperature from the built-in sensor.

BITREK specific parameters

Field – description
  • ADC0, ADC1 – values of analog sensors 1 and 2 in millivolts,
  • AIN1, AIN2 – values of analog sensors 1 and 2 in volts,
  • DIN1, DIN2, DIN3, DIN4 – discrete inputs values,
  • VBAT – built-in battery voltage,
  • par1, par2, … – BITREK protocol parameters, where the parameter number corresponds to the IO element code. The main part of the data is described by these parameters.

How to connect

To connect, add the device to the platform as one of the BITREK devices. Reading data from Glonassoft UMKa and NaviTrek devices are also supported. When registering, specify the ID.

On the sender’s side, specify the following tracking server IP address and port.

AU platform: https://gps.trackfleet.com.au/

Server port:

If you don’t need specific fields, you can use one of the BITREK models.