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

Parameter can.vehicle.vin removed

baja

Parameter can.fuel.rate will be renamed to can.fuel.consumption
Both parameters will be registered for 2 weeks until 30 March, 2020. Then can.fuel.rate will be removed

namo

New Teltonika TFT100 device is supported in flespi telematics hub.

baja

We've performed some architecture changes: now for all up-to-date Teltonika models (that reply with its HW type in getver command response) it is not necessary to register device with appropriate device type. If device is not registered, server will send "getver" command right after login packet received. If device responds with correct answer in HW specified field then the following parsing goes according to this device type.

baja

New Teltonika FMB140 device is supported in flespi telematics hub.

baja

New Teltonika FMB910 device is supported in flespi telematics hub.

baja

gsm.sim.iccid parameter parsing fixed: when LSB (ICCID 2, AVL ID 14) which Teltonika sends as number, started from zeros - these zeros were skipped in flespi. Now we force this tag to be 10 characters long string appended with leading zeros, so full ICCID combination results in valid 19 or 20 digits string.

baja

AVL ID 375 from E-Scooter elements for TST100 will be ranamed in flespi parameters from external.battery.level to external.battery.capacity. Both parameters will be registered until July 15.

baja

The bug fixed in position registering for Codec8 and Codec16. If device is initialized and can't spot the satellites (e.g. inside the building) it send zero coordinates. flespi registered it as parameters position.latitude = 0 and position.longitude = 0. Which lead to inconsistent data for device messages. From now zero coordinates will not be stored.
A bug with unregistered zero parameter also fixed for position.direction and position.altitude parameters

namo

Teltonika protocol updated:

added Unlock Bluetooth Lock setting, Actions tab
added new AVL_IDs:
871 - BLE Lock status - flespi parameter ble.lock.status
872 - BLE Lock Battery - flespi parameter ble.lock.battery.level
AVL_ID 352 now stored in flespi parameter scooter.battery.level
Applicable for TST100 device.

namo

Teltonika protocol updated: Freezer AVL_IDs added for FMB640, FMC640 and FMM640 devices.

Mapping of AVL_IDs to flespi parameters is below:

10040 - Fuel Level - is registered as freezer.fuel.level
10041 - Battery Voltage - is registered as freezer.battery.voltage
10042 - Total Electric Minutes - is registered as freezer.electric.total
10043 - Total Vehicle Minutes - is registered as freezer.vehicle.total
10044 - Total Engine Minutes - is registered as freezer.engine.total
10045 - Zone 1 Alarm Type - is registered as freezer.zone1.alarm.type
10046 - Zone 1 Alarm Code - is registered as freezer.zone1.alarm.code
10047 - Zone 1 Return Air Temperature 1 - is registered as freezer.zone1.return.air.temperature.1
10048 - Zone 1 Supply Air Temperature 1 - is registered as freezer.zone1.supply.air.temperature.1
10049 - Zone 1 Temperature Setpoint - is registered as freezer.zone1.temperature.setpoint
10050 - Zone 1 Evaporator Coil Temperature - is registered as freezer.zone1.evaporator.coil.temperature
10051 - Zone 1 Return Air Temperature 2 - is registered as freezer.zone1.return.air.temperature.2
10052 - Zone 1 Supply Air Temperature 2 - is registered as freezer.zone1.supply.air.temperature.2
10053 - Zone 1 Operating Mode - is registered as freezer.zone1.operating.mode
10054 - Zone 2 Alarm Type - is registered as freezer.zone2.alarm.type
10055 - Zone 2 Alarm Code - is registered as freezer.zone2.alarm.code
10056 - Zone 2 Return Air Temperature 1 - is registered as freezer.zone2.return.air.temperature.1
10057 - Zone 2 Supply Air Temperature 1 - is registered as freezer.zone2.supply.air.temperature.1
10058 - Zone 2 Temperature Setpoint - is registered as freezer.zone2.temperature.setpoint
10059 - Zone 2 Evaporator Coil Temperature - is registered as freezer.zone2.evaporator.coil.temperature
10060 - Zone 2 Return Air Temperature 2 - is registered as freezer.zone2.return.air.temperature.2
10061 - Zone 2 Supply Air Temperature 2 - is registered as freezer.zone2.supply.air.temperature.2
10062 - Zone 2 Operating Mode - is registered as freezer.zone2.operating.mode
10063 - Zone 3 Alarm Type - is registered as freezer.zone3.alarm.type
10064 - Zone 3 Alarm Code - is registered as freezer.zone3.alarm.code
10065 - Zone 3 Return Air Temperature 1 - is registered as freezer.zone3.return.air.temperature.1
10066 - Zone 3 Supply Air Temperature 1 - is registered as freezer.zone3.supply.air.temperature.1
10067 - Zone 3 Temperature Setpoint - is registered as freezer.zone3.temperature.setpoint
10068 - Zone 3 Evaporator Coil Temperature - is registered as freezer.zone3.evaporator.coil.temperature
10069 - Zone 3 Return Air Temperature 2 - is registered as freezer.zone3.return.air.temperature.2
10070 - Zone 3 Supply Air Temperature 2 - is registered as freezer.zone3.supply.air.temperature.2
10071 - Zone 3 Operating Mode - is registered as freezer.zone3.operating.mode
10350 - Ambient Air Temperature - is registered as freezer.air.temperature
10351 - Coolant Temperature - is registered as freezer.coolant.temperature
10352 - Error Count - is registered as freezer.error.count
10353 - RPM - is registered as freezer.compressor.rpm
10354 - RPM - is registered as freezer.compressor.state
10355 - Door status - is registered as freezer.door.status
10356 - Installation Serial - is registered as freezer.installation.serial
10357 - Trailer Serial - is registered as freezer.trailer.serial

namo

namo
Mapping for Freezer IO parameters is updated.

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.