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

minor update in parsing 875 flag for GH5200 device: if AVL ID 875 length is 14 symbols then it means that 875 contains not MAC address but IMEI of violating device, thus it would be stored in proximity.violation.ident parameter.

namo

New settings added for Teltonika TST100, Configuration tab: Scooter speed limits for Normal, Eco and Sport modes.

namo

Reset device setting added to Teltonika TST100, TMT100, TFT100 and GH5200 devices, Actions tab.
Setting sends cpureset command to the device.

namo

New setting added for Teltonitka FMC130: Network Ping, Connectivity tab.

namo

namo
Network Ping Timeout setting, Connectivity tab, is added for Teltonika FMB120 and FMB920 devices.

namo

Teltonika devices FMB130, FMC130, FMU130 and FMM130 now have a possibility to configure 3 digital outputs (at Input/Output settings tab):

namo

Manual CAN I/O (AVL IDs 900 - 930) are added for Teltonika TFT100.
They are registered as 8-byte hex string into flespi parameters can.data.frame.1 - can.data.frame.30 respectively.

namo

AVL ID 381 Ground Sense is supported for Teltonika protocol.
It's registered as a boolean parameter negative.input.status: true - negative input is connected to the ground, false - not connected.

baja

Several action settings added for FMB device series.
setdigout action to manage device outputs with specifying timeout and speed limit
lvcan commands:

lvcanopenalldoors - Toggle CAN-CONTROL to open [unlock] all doors
lvcanclosealldoors - Toggle CAN-CONTROL to close [lock] all doors
lvcanopentrunk - Toggle CAN-CONTROL to open [unlock] trunk
lvcanturninglights - Toggle CAN-CONTROL to flash lights

namo

New devices added: Teltonika FMB002 and Teltonika FMB003

baja

In one week, 11 January 2021, 11:00 UTC, Teltonika protocol will be upgraded to new parsing engine.
At the moment flespi team performs extensive testing to avoid any bugs and mismatches after the upgrade.

baja

baja Teltonika protocol implementation upgraded to new parsing engine.

namo

New settings added for Teltonika TST100, TFT100, GH5200 and TMT250 devices:
Permanent Link and Network Ping Timeout, Connectivity tab:

baja

MSP500 device type added
Motion Detection Source (param ID 100) setting marked as deprecated is removed.

baja

door.open.status parameter is parsed as bitmask to detect:
can.driver.door.status - front left door is opened
can.passenger.door.status - front right door is opened
can.rear.left.door.status - rear left door is opened
can.rear.right.door.status - rear right door is opened
can.hood.status - hood is opened
can.trunk.status - trunk is opened

baja

bugfix: can.control.module.voltage conversion from millivolts to volts added

baja

Some of Teltonika Routers can send position data using Codec 8. The devices added:
Teltonika RUT850
Teltonika RUT955

baja

There is an error in parameter acceleration.array parsing: device sends accelerometer values in mG units, while flespi converts it to G with division by 100 and not by 1000.
Fix will be installed today (Feb 17) at 17-00 UTC

baja

New scheme is applied to setdigout action setting for all device types for 1, 2, 3 and 4 outputs. Old format is marked as deprecated and will be removed in 2 weeks.

kial

We have added a TLS support for the teltonika protocol.
Now you can generate your own PKI, then build a server certificate plus private key and use them in the channel configuration as shown on the screenshot below:
tls