[Changelog] webfleet-connect protocol

omol

We've implemented integration with Webfleet platform via WEBFLEET.connect API as a channel protocol.

omol

We've updated webfleet-connect protocol:

added fetching vehicles information and using it for proper identification of objects from the events (vehicle identnumber is used as device ident)
message type 80000810 now is interpreted as a crash event.

omol

Webfleet connect protocol has been updated.

Default ident has been changed to the following template: objectno:{WEBFLEET OBJECTNO VALUE}. Default ident is set in the messages for which corresponding vehicle is not found or vehicle's ident (identnumber in Webfleet terms) contains characters banned for flespi ident.

omol

omol
Fix: objectuid is used instead of objectno for default ident.

namo

Webfleet-connect protocol is updated.
The following tachograph-related data parameters (msg_class=8) are supported for the protocol:

dt_cardid - flespi parameter tacho.driver.card.code
dt_cardaction - flespi parameters tacho.driver.card.action.enum (numeric value) and tacho.driver.card.action (corresponding string description)
dt_cardtype - flespi parameters tacho.driver.card.type.enum (numeric value) and tacho.driver.card.type (corresponding string description)
dt_slot - flespi parameter tacho.driver.card.slot
dt_state - flespi parameter tacho.driver.card.status (true - driver card is connected, false - disconnected)
event_time - flespi parameter event.timestamp
workstate - flespi parameters tacho.driver.work.state.enum (numeric value) and tacho.driver.work.state (corresponding string description)

YuryAheichyk

Webfleet-connect protocol is updated, added parameters:

rpm - flespi parameter can.engine.rpm
gear - flespi parameter can.gear
fuel_level - flespi parameter can.fuel.volume

YuryAheichyk

Webfleet-connect protocol has been updated: the msg_time parameter is now registered as the send.timestamp flespi parameter. If the message contains the event_time parameter, it will be used as the timestamp flespi parameter. Otherwise, the pos_time parameter will be registered as timestamp.

baja

can_signals structure parsing added:
field FMS_ENGINE_COOLANT_TEMPERATURE is parsed to parameter can.engine.coolant.temperature
field FMS_GROSS_COMBINATION_VEHICLE_WEIGHT is parsed to parameter can.gross.combination.vehicle.weight
field FMS_ENGINE_MIL_INDICATOR is parsed to parameter can.mil.status
field FUEL_CONSUMPTION is parsed to parameter can.fuel.consumption
field CHARGER_CONNECTED is parsed to parameter charger.plug.status
field CHARGING is parsed to parameter can.vehicle.battery.charging.status
field STATE_OF_CHARGE is parsed to parameter can.vehicle.battery.level
field FUEL_RANGE is parsed to parameter remaining.range
field ELECTRIC_RANGE is parsed to parameter can.recharge.mileage
field BATTERY_VOLTAGE is parsed to parameter can.vehicle.battery.voltage
field FMS_FUEL_LEVEL_PERCENTAGE is parsed to parameter can.fuel.level

namo

Webfleet-connect protocol is updated.

Added processing of the parameters sent by third party peripheral devices connected to the trackers.

The following message parameters parameters (msg_class=8) are registered:

aux_device_data_in > device_id - flespi parameter payload.source.id
aux_device_data_in > aux_data - flespi parameter payload.text