-
Notifications
You must be signed in to change notification settings - Fork 10
Teltonika AVL Parameter Parser ‐ What, How, When, and Why
This page will introduce you to the Teltonika AVL parameter ID parser, why it is required, how it works, what it produces as output, and how it is used within OpenRemote. The Teltonika AVL parameter ID parser (parser for the rest of the document) is an integral part of the OpenRemote Teltonika parameter integration.
Teltonika Telematics has a long device list, both end of life and currently supported. Those devices are crammed with sensors and calculations to provide an enormous amount of data to the user. To maintain a standard across the entire product line, Teltonika has created their own communication protocols for devices to communicate with servers. Those protocols, called codecs, are specialized to transmit the data generated by the device to the server with the smallest possible overhead. A new codec that was introduced was Codec JSON, that sends the device data as a JSON file, with the format that loosely adheres to AWS IoT Core Shadow payloads. Each payload is transmitted via MQTT and is received by OpenRemote, where it is interpreted and converted into a new Asset state with upserted attributes. The JSON payload received, contains some parameters that are always included (timestamp, priority, coordinates, altitude, angle, visible satellite count, speed, event parameter), and the rest are key-value pairs, with an integer as a key and any primitive as a value.
Those key-value pairs are the parameter data that the device sends over. The key of the key-value pair is the parameter ID, and the value is the value of that parameter that the device found.
Parameter IDs are in essence the unique ID for identifying parameters in the list of key-value pairs. Those IDs are generated by Teltonika Telematics, and each model type has their own list of parameters, and each parameter has its own ID. Here's the parameter list for the FMC003, FMB920, and FMB640.