Fetch vehicles position information to a channel from Scania Fleet Management Services using API.

To use the channel you need to have active Control package from Scania dealer and login/password to access Scania Fleet Management Services. Specify them to the channel configuration.

After creation please check the channel logs for errors using Toolbox. Known error codes:

  • 401 - wrong username and/or password;
  • 429 - too many requests, probably somebody using same credentials to access API or maybe you have created few channels, please leave only one channel with protocol scania-fms enabled and working;

Below is the list of parameters that can appear in the messages received by the channel via scania-fms protocol. In most parameters, the name consists of tags split by dots: tag1.tag2.tag3.tag4... Each tag defines a certain area of an application, e.g. any parameter that contains mileage data has the 'mileage' tag in the name and any parameter related to fuel control contains the 'fuel' tag. By default JSON fields of the message received by a channel via this protocol can only contain the below-specified parameters. Any additional parameter will be prefixed by the "custom" tag, e.g. "custom.unspecified-name".

Name Type Unit Description
channel_id number ID of channel that received message
driver.card.code string Driver identification card id
fuel.consumed.liters number liters Fuel volume totally consumed by vehicle
fuel.level number percentage Fuel level percentage
ident string Device unique identificator and optional password
message.type string Message type
position.direction number degrees Heading angle at position detection moment
position.latitude number degrees Latitude coordinate value
position.longitude number degrees Longitude coordinate value
position.speed number km/h Instant speed at position detection moment
position.timestamp number seconds Timestamp when coordinates where calculated
timestamp number seconds Message timestamp
vehicle.mileage number km Total calculated mileage string VIN of vehicle
No results found.