omnicomm-rpc

Fetch vehicles position information to a flespi channel from Omnicomm Online server using SOAP web service.

To create a channel specify the web service URL, login, and password in the channel configuration.

Please refer to the Omnicomm Online Integration Manual on how to obtain the connection address and credentials for the web service.

Below is the list of parameters that can appear in the messages received by the channel via omnicomm-rpc 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
engine.ignition.status boolean Engine ignition status
fuel.level number percentage Fuel level percentage
ident string Device unique identificator and optional password
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
No results found.