Supported Sensor IDs

SensorId	Sensor Value - Data Type	Notes	Events - Details
tbsAmberLight	Boolean		status.tbs v1
tbsRedLight	Boolean		status.tbs v1
tbsPowered	Boolean	true if the ebs/abs is powered. False otherwise	status.tbs v1
brakeLiningOk	Boolean	true when brake lining is ok for all wheels; false when at least one wheel has brake lining below the threshold	status.tbs v1
fuel	Integer	The Fuel Level that the truck has at the time of the message. It is expressed in percentage.	status.truck v1
tfu	Double	The Total Fuel Used of the truck, expressed in Liters	status.truck v1
supplyVoltage	Double	Allowed values: 0-32. Measured in Volts	status.truck v1
mileage	Double	Odometer reading, expressed in km	status.truck v1 status.trailer v1
gnssSpeed	Integer	Speed of the asset detected using gnss connection, expressed in km/h	position.registered v1
wheelSpeed	Integer	Speed of the asset detected using wheel information (for example from ebs), expressed in km/h	status.trailer v1
axleLoad	Integer	Aggregated load of all axles. Value is expressed in Kg with no decimal digits	status.trailer v1
tirePressure	DataType: LocationValueDouble { "location": , "value": }	See Wheel Location Logic for an explanation about the location value; Pressure is expressed in kPa with at most one decimal digit	status.tpms v1
tireTemperature	DataType: LocationValueInteger { "location": , "value": }	See Wheel Location Logic for an explanation about the location value; Temperature is expressed in Celsius degrees	status.tpms v1
tirePressureStatus	DataType: LocationValueString { "location": , "value": }	See Wheel Location Logic for an explanation about the location value See Pressure Threshold Status Enum Values, for the list of possible values for the tire_pressureStatus.value property	status.tpms v1
reeferLoggerTemperature	DataType: LocationValueDouble { "location": , "value": }	Temperature is expressed in Celsius degrees, with at most a decimal digit	status.reefer.logger v1
reeferLoggerHumidity	DataType: LocationValueInteger { "location": , "value": }	percentage of the logger humidity. Allowed values are from 0 to 100.	status.reefer.logger v1
reeferDigitalInput	DataType: LocationValueBoolean { "location": , "value": }		status.reefer.digitalinput v1
position	DataType: Position { longitude: , latitude: , validity: }		position.registered v1
heading	Integer		position.registered v1
satCount	Integer		position.registered v1
reeferTotalHours	Integer		status.reefer v1
reeferEngineHours	Integer		status.reefer v1
reeferElectricHours	Integer		status.reefer v1
reeferSupplyVoltage	Double	Value from 0 to 100, with at most one decimal digit	status.reefer v1
reeferFuel	Integer	allowed values are from 0 to 100.	status.reefer v1
reeferPowerMode	String	See Power Mode values values for list of allowed values	status.reefer v1
reeferOperatingMode	String	See Operating Mode Values For Each Zone for list of allowed values	status.reefer v1
reeferReeferOn	Boolean		status.reefer v1
reeferEvaporatorTemperature	Double
reeferAmbientTemperature	Double
reeferCompartmentSetPoint	DataType: LocationValueDouble { "location": , "value": }		status.reefer v1
reeferCompartmentReturnAir	DataType: LocationValueDouble { "location": , "value": }		status.reefer v1
reeferCompartmentSupplyAir	DataType: LocationValueDouble { "location": , "value": }		status.reefer v1
reeferCompartmentMode	DataType: LocationValueString { "location": , "value": }	See Reefer Operating Mode Values for allowed values that will return for the value property of this object	status.reefer v1
reeferCompartmentSpeedMode	DataType: LocationValueBoolean { "location": , "value": }		status.reefer v1
reeferCompartmentHumidity	DataType: LocationValueInteger { "location": , "value": }	Allowed values are from 0 to 100.	status.reefer v1
evRemainingCharge	Integer	Number from 0 (empty) to 100 (full)	status.ev.propulsion v1
evRemainingDistance	Double		status.ev.propulsion v1
evChargingStatus	String	See Propulsion Charging Status Values for allowed values that will return for the value property of this object	status.ev.propulsion v1
evChargingSpeed	Double		status.ev.propulsion v1
evTotalEnergyConsumption	Double		status.ev.propulsion v1
evBatteryTemperature	Double		status.ev.propulsion v1
evAmbientTemperature	Double		status.ev.propulsion v1
ignitionState	Boolean		status.truck v1
reeferCompartmentEvaporatorTemperature	DataType: LocationValueDouble { "location": , "value": }		status.reefer v1
reeferSpeedMode	Boolean		status.reefer v1
linTemperature	DataType: LocationValueDouble { "location": , "value": }		status.lin v1
linContact	DataType: LocationValueBoolean { "location": , "value": }		status.lin v1
externalPowerAvailable	Boolean		status.comunit.power v1
tbsAvailable	Boolean		status.comunit.power v1
tbsSuppliedVoltage	Integer		status.comunit.power v1
reeferAvailable	Boolean		status.comunit.power v1
reeferSuppliedVoltage	Integer		status.comunit.power v1
batteryPackAvailable	Boolean		status.comunit.power v1
batteryPackState	String	See Battery Pack Charging State Values for allowed values that will return for the value property of this object	status.comunit.power v1
batteryPackNotChargingReason	String	See Battery Pack Not Charging Reason Values for allowed values that will return for the value property of this object	status.comunit.power v1
batteryPackLevel	String	See Battery Pack Level Values for allowed values that will return for the value property of this object	status.comunit.power v1
batteryPackSuppliedVoltage	Integer		status.comunit.power v1

Location/Zones

In some sensors, the location property inside the sensorValue object defines the location or zone of the sensor for the specific measurement.
For Example, in the tpms_temperature sensor, it indicates the location of the tire.
For further details, see Wheel Location Logic
It is possible to query the temperature of all the tires by using “tmps_temperature” in the sensor ID query parameter. It is also possible to request the temperature of a specific wheel. For example, to get the temperature of the first wheel on the left of axis 1, you can use "tire_temperature_17". For a mapping of the wheels with the number, see the paragraph Wheel Location Logic. This logic is applied for the following sensors:

tire_pressure
tire_temperature
tire_pressureStatus

The zone location is more straightforward and it refers to the actual zone with the same number. For example, if in the reeferlogger_temperature object the location is 2, it means that it refers to the reefer temperature collected from zone 2 of the reefer.
Also, in this case is possible to query a specific zone by using reefer_logger_temperature, where is the zone we are interested. This logic applies for:

reefer_logger_temperature
reefer_digital_input

Wheel Location Logic

The wheels are calculated from the mid-point 8, that means there is no wheel number 8. All the wheels will go from 0-7 or 9-F (15 in hexadecimal).
Also, the number of the wheel location also start from the mid-point, decreasing when on the left of mid-point and increasing when on the right.
That means, when we have one wheel on the left it will have the number 7, if we add a second wheel in the same axle on the left side it will have the number 6 and so on.
When we have one wheel on the right it will have the number 9, if we add a second wheel in the same axle on the right side it will have the number A (10) and so on.
The following diagrams should help in understanding the Scalar format for wheel location.

Examples

from integer to wheel position

Decimal = 39; hex = 27 ==> axle 2, first wheel to the left
Decimal = 41; hex = 29 ==> axle 2, first wheel to the right
Decimal = 54; hex = 36 ==> axle 3, second wheel to the left
Decimal = 58; hex = 3A ==> axle 3, second wheel to the right

from wheel position to integer

axle 1, third wheel to the left = 21. In hexadecimal it is 15 (1 stands for axle 1 and 5 stands for third wheel, considering the first one has number 7, the second one has number 6 and so on). Converting 15 from hex to dec, we obtain 21
axle 5, fifth wheel to the left = 83. Converting the position in hexadecimal we have 5 as first digit due to the axle 5; then we have 3 as second digit by considering the part in bold: 7 = wheel 1; 6 = wheel 2; 5 = wheel 3; 4 = wheel 4; 3 = wheel 5; 2 = wheel 6; 1 = wheel 7; = wheel 8. Then, by converting 53 from hex to dec, we obtain 83
axle 1, fourth wheel to the right. The value is 28. We take 1 as first digit for the axle; then we take C because is the fourth wheel (9= wheel 1; A = wheel 2; B = wheel 3; C = wheel 4; D = wheel 5; E = wheel 6; F = wheel 7). Then, converting 1C from hex to dec, we obtain 28
axle 4, first wheel to the right. 49 is the hexadecimal representation (4 for axle 4 and 9 for wheel 1 to the right). Converting it to decimal we obtain 73

Value Mapping

Some properties contains a value as string which is mapped to an enumerator. In this section we document all the enumeration used by the sensor module

Pressure Threshold Status Enum Values

extremeOverPressure
overPressure
normal
underPressure
extremeUnderPressure

Power Mode Values

invalid
diesel
electric

Operating Mode Values For Each Zone

invalid
powerOff
cooling
heating
defrost
pretrip
irregularShutdown
compulsoryShutdown
thermostatOff
sleep

Reefer Operating Mode Values

invalid
cycleSentry
continuous

Propulsion Charging Status Values

notCharging
charging
unknown

Battery Pack Charging State Values

notCharging
charging
fullyCharged

Battery Pack Not Charging Reason Values

noPower
temperatureIssue
error

Battery Pack Level Values

critical
low
medium
high
full