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 . Supported devices list Teltonika FM1100 Teltonika FM1110 Teltonika FM1120 Teltonika FM1122 Teltonika FM1125 Teltonika FM1200 Teltonika FM1202 Teltonika FM2200 Teltonika FM3001 Teltonika FM3300 Teltonika FM3612 Teltonika FM3622 Teltonika FM36M1 Teltonika FM4100 Teltonika FM4200 Teltonika FM5300 Teltonika FM6300 Teltonika FM6320 Teltonika FMA110 Teltonika FMA120 Teltonika FMA202 Teltonika FMA204 Teltonika FMB001 Teltonika FMB002 Teltonika FMB003 Teltonika FMB010 Teltonika FMC001 Teltonika FMM001 Teltonika FMB110 Teltonika FMB120 Teltonika FMB122 Teltonika FMB125 Teltonika FMB130 Teltonika FMB202 Teltonika FMB204 Teltonika FMB630 Teltonika FMB640 Teltonika FMB641 Teltonika FMC650 Teltonika FMB900 Teltonika FMB910 Teltonika FMB920 Teltonika FMB962 Teltonika FMB964 Teltonika FMT100 Teltonika FMU125 Teltonika FMU130 Teltonika GH5200 Teltonika MTB100 Teltonika TMT250 Teltonika TST100 Teltonika FMM125 Teltonika FMC125 Teltonika FMM130 Teltonika FMC130 Teltonika FMB204 Teltonika FMB140 Teltonika TFT100 Teltonika FMM800 Teltonika FMC800 Teltonika FMM920 Teltonika FMM150 Teltonika FMM13A Teltonika FMC13A Teltonika FMM80A Teltonika FMM650 Teltonika FMB930 Teltonika FMM880 Teltonika FMC880 Teltonika FMC234

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

baja

Bugfix in FMB parsing scheme:
IO ID 332 stored as ble.2.custom.payload.hex.2 must be stored as ble.2.custom.payload.hex.1
IO ID 333 stored as ble.3.custom.payload.hex.3 must be stored as ble.3.custom.payload.hex.1
IO ID 334 stored as ble.4.custom.payload.hex.4 must be stored as ble.4.custom.payload.hex.1
IO ID 248 raw numeric value is now also stored in immobilizer.state.enum parameter
FMB640 series update in IO ID 251: together with immobilizer.state string parameter now the parameter immobilizer.state.enum is stored. Depending on value, extra boolean parameters are registered:
value 0: false to ibutton.connected.status
value 1: true to ibutton.connected.status
value 2: true to ibutton.connected.status, true to ibutton.authorized.status

baja

Immobilizer scenario parameters setting added for the models with 3 digital outputs

Immobilizer scenario parameters setting for the models with 1 and 2 digital outputs updated with field "auth_list_check" - List check for authorization. Equivalent to Teltonika configuring tool:

baja

baja several protocol updates:
the quoted messages refers to update where indexed parameters ble.sensor.temperature.error.code and ble.sensor.humidity.error.code have been stored according to the values:
4000 - abnormal sensor state
3000 - sensor not found
2000 - failed sensor data parsing
This was a problem since there was no way to tell temperature 20 from error code 2000. Teltonika made this codes outdated, so now the values 20, 30 and 40 will be correctly parsed.

ID 540 - Throttle position group stored as can.throttle.pedal.level
ID 541 - Fuel-Air Commanded Equivalence Ratio stored as can.equivalence.ratio
ID 542 - Intake Manifold Absolute Pressure stored as can.intake.map

baja

command response field in the log of successful command execution is now stored as HEX string
(It was stored as escaped string before)

baja

Teltonika TAT240 device type added

baja

Minor update: devices that work over TLS will now have 2 second delay before delivering any commands. This made to give devices a timeout to finish encrypting operation. Because if device would receive a command during encrypting the packet to be sent in few moments - it just breaks the connection. So let's treat it as a server fix of a device-side behavior.

also, SECO setting added under Miscellaneous tab

baja

baja minor update rollback. 2 second delay for devices that work over TLS was removed, as Teltonika released a fix for that.

baja

new device type added:
Teltonika FMC234

baja

Settings idling, green_driving and overspeeding had been remastered for different device types to have appropriate amount of DOUT in control option (or no DOUT management for OBD devices.)

baja

"On demand tracking activated by" setting added on Tracking tab

baja

Parsing updated: CAN Bus Security state flags parameters (AVL IDs from 898 to 1084 of this list) for FMB series added

details

ID 898: SSF Ignition to parameter can.engine.ignition.status
ID 652: SSF KeyInIgnitionLock to parameter can.ignition.key.status
ID 899: SSF Webasto to parameter can.webasto.status
ID 900: SSF Engine Working to parameter can.engine.working.status
ID 901: SSF Standalone Engine to parameter can.standalone.engine
ID 902: SSF Ready To Drive to parameter can.ready.to.drive.indicator.status
ID 903: SSF Engine Working On CNG to parameter can.cng.status
ID 904: SSF Work Mode to parameter private.status
ID 905: SSF Operator to parameter can.operator.present.status
ID 906: SSF Interlock to parameter can.interlock.active
ID 907: SSF Engine Lock Active to parameter can.engine.lock.status
ID 908: SSF Request To Lock Engine to parameter can.request.engine.lock.event
ID 653: SSF Handbrake Is Active to parameter can.handbrake.status
ID 910: SSF Footbrake Is Active to parameter can.pedal.brake.status
ID 911: SSF Clutch Pushed to parameter can.pedal.clutch.status
ID 912: SSF Hazard Warning Lights to parameter can.lights.hazard.lights.status
ID 654: SSF Front Left Door Open to parameter can.front.left.door.status
ID 655: SSF Front Right Door Open to parameter can.front.right.door.status
ID 656: SSF Rear Left Door Open to parameter can.rear.left.door.status
ID 657: SSF Rear Right Door Open to parameter can.rear.right.door.status
ID 658: SSF Trunk Door Open to parameter can.trunk.status
ID 913: SSF Engine Cover Open to parameter can.hood.status
ID 909: SSF Roof Open to parameter can.roof.opened.status
ID 914: SSF Charging Wire Plugged to parameter cable.connected.status
ID 915: SSF Batttery Charging to parameter can.vehicle.battery.charging.status
ID 916: SSF Electric Engine State to parameter can.electric.engine.status
ID 917: SSF Car Closed Factory Remote to parameter can.car.closed.remote.status
ID 662: SSF Car Is Closed to parameter can.car.closed.status
ID 918: SSF Factory Alarm Actuated to parameter factory.alarm.actuated.status
ID 919: SSF Factory Alarm Emulated to parameter factory.alarm.emulated.status
ID 920: SSF Signal Close Factory Remote to parameter can.car.closing.remote.event
ID 921: SSF Signal Open Factory Remote to parameter can.car.opening.remote.event
ID 922: SSF Rearming Signal to parameter can.rearm.signal.event
ID 923: SSF Trunk Door Opened Factory Remote to parameter can.trunk.opening.remote.event
ID 924: SSF CAN Module In Sleep to parameter can.module.sleep.mode
ID 925: SSF Factory Remote 3x to parameter can.car.triple.closing.remote.event
ID 926: SSF Factory Armed to parameter can.factory.armed.status
ID 660: SSF Parking Gear Active (automatic gear box) to parameter can.parking.status
ID 661: SSF Reverse Gear Active to parameter can.reverse.gear.status
ID 659: SSF Neutral Gear Active (automatic gear box) to parameter can.neutral.gear.status
ID 927: SSF Drive Is Active (automatic gear box) to parameter can.drive.gear.status
ID 1083: SSF Engine Working On Dual Fuel to parameter can.dual.fuel.status
ID 1084: SSF Engine Working On LPG to parameter can.lpg.fuel.status

baja

can_params setting changed. Now you can individually manage each setting from OBD IO with priority, operand, high-low value, event only and SMS number+text.

explore commands & settings -> OBD tab for the details.

namo

baja Teltonika protocol is updated: OBD IO settings fixed.

YuryAheichyk

Added new parameters for FMC150:

id:866 LVCAN Vehicle Range - can.vehicle.remaining.range
id:1112 LVCAN HVBatteryPackVoltage - can.vehicle.battery.voltage
id:1113 LVCAN HVBatteryPackCurrent - can.vehicle.battery.current
id:1155 LVCAN HV batt consumed energy - can.vehicle.battery.energy.consumed
id:1156 LVCAN HV batt recup energy - can.vehicle.battery.energy.recuperated
id:1157 LVCAN HV batt power - can.vehicle.battery.power

Added new option Ultra Deep Sleep mode to Sleep mode setting for FMx130 devices

Added new Toggle CAN-CONTROL to close all windows, Toggle CAN-CONTROL to open all windows settings for CAN communication supported devices

YuryAheichyk

The protocol will be affected by the change in parameter can.dtc to be installed in 2 weeks - Mar 15th, 2024: the parameter can.dtc is currently of string type and will be converted to type array with separate DTC codes.

Added parameter can.dtc.array as an example of future implementation of can.dtc

YuryAheichyk

YuryAheichyk changes have been applied, the can.dtc parameter type changed to array

baja

codec.id parameter added for each message. It might be 142 for Codec 8 Extended (as 0x8E hex is 142 decimal), or just numeric value for other codec types like 8, 12

baja

parsing update for FTC series:
parameter external.powersource.voltage is now parsed from AVL ID 800
new parsing added for
ID 237: gsm.network.type:
ID 249: gsm.jamming.alarm.status
ID 252: external.powersource.status
ID 303: instant.movement.status
ID 641: gsm.sim.iccid
ID 254: absolute.acceleration or harsh.cornering.angle depending on harsh event type

Parsing for FMB640 series update in BLE section. Indexed parameters with indexes from 1 to 4 added:
IDs 701 ... 704 BLE Temperature - ble.sensor.temperature
IDs 705 ... 708 BLE Battery - ble.sensor.battery.level
IDs 709 ... 712 BLE Humidity - ble.sensor.humidity
IDs 713 ... 716 BLE Custom - ble.1.custom.payload.hex and ble.1.custom with index from 1 to 4
IDs 717 ... 720 BLE Illum - ble.sensor.illuminance
IDs 721 ... 724 BLE LLS Fuel - ble.lls.fuel.level
IDs 725 ... 728 BLE frequency - ble.sensor.frequency
IDs 729 ... 744 BLE sensor custom - ble.1.custom.payload.hex and ble.1.custom with index from 5 to 20

namo

Teltonika protocol updated: fixed parsing of Param Id 48 Tacho Data Source for FMB640 and analogues.

baja

FMC650 series parsing update for BLE Custom fields: it was stored as ble.1.custom.INDEX unsigned integer value, but was vulnerable to 53-bit JSON limit. Now it is stored as HEX string and named ble.1.custom.payload.hex.INDEX
Example of PVM code to convert the value to integer value:
optional .ble.1.custom.payload.hex.2 ==> %hex ==> %int64 ==> #ble.1.custom.2
you may use math operations in same chain, e.g. this is how divide it by 10
optional .ble.1.custom.payload.hex.2 ==> %hex ==> %int64 ==> %double ==> this / 10.0 ==> #ble.1.custom.2

baja

FMB series update: parameter private.status that is parsed from Security State Flags bits (IDs 391 and 904), renamed to can.private.status
TAT series: AVL IDs 25036 to 25039 are parsed to indexed parameters wifi.signal.strength and wifi.mac.address.

EvgenyShatilo

baja Hotfix related to the previous improvement.

Parameters wifi.signal.strength and wifi.mac.address indexing have been fixed. Previously, it could be negative if the device sent several sets of Wi-Fi data.