Teltonika is one of the most popular protocols in flespi platform and in the world of Telematics. This topic will be used to post changes in protocol implementation. Here is a guide how to obtain telematics data from Teltonika devices over API .

BLE temperature and humidity sensor values parsing added to device types FMB

Dear flespi users. We have added a new device type Teltonika TST100 to the list of supported Teltonika devices. With this update we also announce major refactoring of the whole Teltonika protocol implementation for all device types. The newly integrated TST100 already works on the new base, and has all possible settings integrated. In the nearest future we will move all other devices messages parsing and settings operations to the new base. We will report here the log of the migration. The main goal is to make parameters parsing more faster and more precise. Update will touch only "secondary" parameters without influencing time and position parameters.

Teltonika FM3001 moved to new parsing scheme. FM3001 settings have been remastered to correspond Teltonika Parameter list With this update we also moved "Generic Teltonika" device type to new parsing scheme. So if you do not register a device in Telematics Hub and use it only in channel level - the parsing will work with correspondence to Teltonika FMB table as it is the most popular device family. Again, this relates only to "secondary" parameters without influencing time and position parameters.

As described in previous post we do major refactoring here. The list of updates installed today: (and the main): All device types moved to new parsing scheme. Device types added: FMC125 , FMM125 , FMC130 , FMM130 , FMB206 Wide range of settings added for devices: MTB100 , TMT250 . Digital inputs settings remastered to fit clearly to all FMB devices family list.

Device types added: FMC001 , FMM001 And for the OBD device family device settings are almost full. (We skip Geofence settings and Bluetooth OBD settings as they require settings Arrays work which is under construction on Telematics Hub back-end side)

tags 253 and 254 remastered as specified in Teltonika wiki . As for now it is parsed as following: if parameter 253 is: 1 – harsh.acceleration.event = true (parameter 254 is parsed to absolute.acceleration in G) 2 – harsh.braking.event = true (parameter 254 is parsed to absolute.acceleration in G) 3 – harsh.cornering.event = true (parameter 254 is parsed to harsh.cornering.angle in degrees) For FMB640, FMB630, FM3612 and FM36m1 254 tag have been parsed to eco.driving.events.number which is not valid parsing. This parameter will be removed from 254 tag parsing in a week - 20 November, 2019

Teltonika protocol updated: Parameter can.liquid.sensor.fuel.volume is renamed to can.fuel.volume For backward compatibility both parameters are registered for now. Old parameter will be removed 25 Nov 2019. Multiplier 0.1 is applied to can.fuel.volume parameter to get resulting value in liters.

namo Teltonika protocol updated: can.liquid.sensor.fuel.volume parameter is removed

Dear flespi users, there are minor changes in Teltonika protocol: overspeeding.event parameter will be renamed to overspeeding.status parameter. movement.event parameter will be renamed to movement.status . For now both parameters are registered. movement.event and overspeeding.event will be removed on December 4th There are also some bugfixes: Several parameters has wrong signed/unsigned parsing. E.g. external.powersource.voltage generated bad values as it was parsed as signed integer, now it switched to unsigned and has correct values. The same with gsm.lac or gsm.cellid (it was parsed as signed, and now as unsigned, so on big values it was possible incorrect). FMB630 device series parameter can.engine.coolant.temperature parsing fixed towing.event parameter parsing was incorrect. We've fixed it and now correct parameter value is stored in towing.alarm.status gsm.jamming.event parameter parsing was incorrect. We've fixed it to gsm.jamming.alarm.status If you will find something suspicious in Teltonika parameter parsing - please, contact us.

we've implemented special logic for parsing BLE connected devices. Teltonika protocol send it under tag 385 and now it is parsed to parameter ble.beacons which is JSON object, where keys are BLE beacons UUID, and values - JSON objects with beacon parameters, e.g. {... "ble.beacons": { "E2C56DB5-DEAD-BEEF-B060-D0F5A71096E0:1234:9876": { "rssi": -79 }, "E2C56DB5-DEAD-BEEF-B060-D0F5A71096E0:4321:6789": { "rssi": -86 } }, "channel.id": 12345, "event.enum": 385, "event.priority.enum": 0, "ident": "123451234512345", "position.altitude": 126, "position.direction": 60, "position.latitude": 12.3456, "position.longitude": 65.4321 ...} if("undefined"!==typeof hljs)hljs._ha();else if("undefined"===typeof hljsLoading){hljsLoading=1;var a=document.getElementsByTagName("head")[0],e=document.createElement("link");e.type="text/css";e.rel="stylesheet";e.href="//cdnjs.cloudflare.com/ajax/libs/highlight.js/9.7.0/styles/default.min.css";a.appendChild(e);e=document.createElement("script");e.type="text/javascript";e.onload=function(){var d={},f=0;hljs._hb=function(b){b.removeAttribute("data-hljs");var c=b.innerHTML;c in d?b.innerHTML=d[c]:(7

[Changelog] teltonika protocol

EvgenyShatilo

Tacho functionality udpate: Another fix to stabilize authorization with the latest version of Stoneridge firmware. This fixes the authorization issue even after the tracker completes authorization, although the tracker continues to communicate with the card.

bird

New device type added: Teltonika FTC887

New Dead Reckoning parameters for FTC devices:

dead.reckoning.turning.alignment — DR turning alignment progress (%)
dead.reckoning.straight.alignment — DR straight alignment progress (%)
dead.reckoning.movement.state.enum, dead.reckoning.movement.state — VMDS movement status
dead.reckoning.harsh.acceleration.event, dead.reckoning.harsh.braking.event, dead.reckoning.harsh.turn.event, dead.reckoning.harsh.lane.change.event, dead.reckoning.collision.event, dead.reckoning.rollover.event, dead.reckoning.stability.warning, dead.reckoning.euler.anomaly, dead.reckoning.harsh.turn.left.event, dead.reckoning.harsh.turn.right.event — VMDS alarm events (boolean, set to true when detected)

EvgenyShatilo

Tacho functionality added for model FMB641

EvgenyShatilo

FMC650/FMB630/FMM640/FMM650: Fixed parsing crash when tachograph driver name fields (AVL IDs 10518-10521) contain all-0xFF bytes indicating no driver card is inserted. The parser now correctly treats all-0xFF input as empty data instead of attempting text conversion, which previously caused repeated connection failures.

bird

Removed Dead Reckoning VMDS parameters per manufacturer request (internal code parameters unintentionally published to wiki):

dead.reckoning.movement.state.enum, dead.reckoning.movement.state — removed
dead.reckoning.harsh.acceleration.event, dead.reckoning.harsh.braking.event, dead.reckoning.harsh.turn.event, dead.reckoning.harsh.lane.change.event, dead.reckoning.collision.event, dead.reckoning.rollover.event, dead.reckoning.stability.warning, dead.reckoning.euler.anomaly, dead.reckoning.harsh.turn.left.event, dead.reckoning.harsh.turn.right.event — removed

Parameters dead.reckoning.turning.alignment, dead.reckoning.straight.alignment, dead.reckoning.calibration.state.enum, dead.reckoning.calibration.state remain available.

bird

67 individual CAN adapter boolean AVL IDs (CSF 928-952, ISF 953-992, CSF 1085-1086) are now mapped to named can.* parameters for FMB-family devices. Previously these fell through to custom.param.* storage.

bird

FTC device family (FTC887, FTC921, FTC305, FTC134, FTC880, FTC927, FTC881, FTC961, FTM305, ATC700 and others) — BLE/Bluetooth sensor parameters are now parsed into normalized names instead of custom.param.*:

ble.sensor.temperature.1 through ble.sensor.temperature.4 (BLE Temperature sensors 1-4)
ble.sensor.temperature.error.code.1 through ble.sensor.temperature.error.code.4
ble.sensor.battery.level.1 through ble.sensor.battery.level.4 (BLE Battery sensors 1-4)
ble.sensor.humidity.1 through ble.sensor.humidity.4 (BLE Humidity sensors 1-4)
ble.sensor.humidity.error.code.1 through ble.sensor.humidity.error.code.4
ble.sensor.movement.count.1 through ble.sensor.movement.count.4 (EYE Movement Count sensors 1-4)
ble.sensor.magnet.status.1 through ble.sensor.magnet.status.4 (EYE Magnet sensors 1-4)
ble.sensor.magnet.status.error.code.1 through ble.sensor.magnet.status.error.code.4
ble.sensor.pitch.angle.1 through ble.sensor.pitch.angle.4 (EYE Pitch sensors 1-4)
ble.sensor.pitch.angle.error.code.1 through ble.sensor.pitch.angle.error.code.4
ble.sensor.low.battery.status.1 through ble.sensor.low.battery.status.4 (EYE Low Battery sensors 1-4)
ble.sensor.low.battery.error.code.1 through ble.sensor.low.battery.error.code.4
ble.sensor.roll.angle.1 through ble.sensor.roll.angle.4 (EYE Roll sensors 1-4)
ble.sensor.roll.angle.error.code.1 through ble.sensor.roll.angle.error.code.4

BLE beacon parameters (ble.beacons, ble.beacons.advanced, ble.beacons.visible, ble.beacons.found, ble.beacons.lost, ble.eye.sensor.data) were already supported.

bird

Fixed tachograph driver card file parsing for non-Latin character encodings (Greek, Cyrillic, Turkish, Baltic, etc.) in holderSurname, holderFirstNames, cardIssuingAuthorityName, and drivingLicenceIssuingAuthority fields. Previously, driver cards with non-Latin names would fail to parse, preventing DDD file creation. All 14 ISO 8859 character sets and KOI8-R/KOI8-U are now correctly handled.

bird

Fixed vehicle.registration.number not being produced when the registration number fits in a single part (≤8 characters) for FMC650, FMB641, FMC640, FMM640, FMM650, FMB640, FM6300 devices.

bird

New action setting deleterecords ("Delete all stored records") added for all modern Teltonika devices — clears all AVL records from internal FLASH memory.

sdformat ("Format SD card") now available for FMB641, FMC650, FMM650, and FMB630.

bird

deleterecords action setting now properly parses device response — command result reports "All Records Deleted" instead of generic success.

bird

Fixed neighbouring cell parameters mapping for FTC-series devices (AVL IDs 13370-13389): corrected field order and cell grouping from 5×4 to 4×5 (LAC, CellID, RSSI, MNC, MCC per cell)
New parameter gsm.signal.dbm with indexing for neighbouring cell RSSI

bird

Fixed BLE Temperature (AVL IDs 701-704) parsing for FMB641, FMC640, FMM640, FMM650, FMC650, FMB640, FM6300, MCX301, MCX3M1 devices:

Temperature multiplier is now conditional on sensor byte size: 2-byte sensors use ×0.01 (was ×0.1, values were 10× too high), 1-byte sensors use ×0.1
New parameter ble.sensor.temperature.error.code.N for error conditions (abnormal sensor state, sensor not found, failed sensor data parsing)

bird

Fixed a crash in tachograph auto-upload that could cause a connect-disconnect loop for devices with auto file request configured.

bird

New parameters for FMC650 devices: fms.ferry.train.enum, tacho.border.crossing.info, tacho.kline.privacy.mode.enum, tacho.vehicle.load.type, can.engine.oil.temperature, scenario.status (indexed 1-4)

New ISOBUS PTO parameters for FMC650 devices: isobus.rear.pto.output.shaft.speed, isobus.rear.pto.shaft.speed.point, isobus.rear.pto.engagement.status, isobus.rear.pto.mode.enum, isobus.rear.pto.economy.mode.status

New BLE sensor parameters for FTC devices: ble.sensor.rssi (indexed 1-10), ble.mac.address (indexed 1-10), ble.sensor.device.name (indexed 1-10), plus sensors 5-10 support for existing BLE parameters (temperature, battery level, humidity, magnet, movement count, pitch, roll, low battery)

bird

New setting fields added to Manual CAN Command settings for TFT100, TST100, GH5200, TMT250 devices: send_period, response_trigger, send_count. These fields control periodic sending interval, response trigger source, and transmission count for each Manual CAN Command slot.