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

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

namo

Teltonika protocol updated - new CAN Adapter parameters are supported for FMB140 and other devices. The following parameters are registered:

232 CNG status - can.cng.status
233 CNG used - can.cng.consumed
234 CNG level - can.cng.level
388 Module ID 17B - can.module.id.hex
517 SecurityStateFlags_P4 - can.security.state.flags.bitmask

namo

Teltonika protocol updated, added parsing of one more parameter for FMB devices:

636 UMTS/LTE Cell ID - gsm.cellid

baja

FMB devices parameter bug fixes:
AVL ID 152 is stored as can.vehicle.battery.level. Was in conflict with AVL ID 113 battey.level
AVL ID 105 is stored as can.tracker.counted.mileage. Was in conflict with AVL ID 87

FMB640 devices update: AVL ID 143 Door status parsing updated with precise parsing scheme for each door: can.driver.door.status, can.passenger.door.status, can.rear.left.door, can.rear.right.door, can.hood.status, can.trunk.status, door.open.status

baja

Some more of Teltonika Routers can send position data using Codec 8. The devices added:
Teltonika RUTX09
Teltonika RUTX10
Teltonika RUTX11
Teltonika RUTX12

namo

Bitwise parsing of security state flags is supported in flespi. This is a replacement for the parameter lvc.security.state.bitmask that will be removed in a week, 05-Apr-2021.
The mapping into flespi parameters is the following:

Byte 0
CAN1-CAN3 connected states - can.connection.state.1 - can.connection.state.3
Byte 2
0x04 – Battery charging - battery.charging.status
0x08 – Charging cable connected - cable.connected.status
0x10 – Vehicle working mode, 1-business mode, 0-private mode - private.status
0x20 – Bit appears when any operate button in car was put. This bit is reset if the button is released - button.pressed.status
0x40 – Bit appears when immobilizer is in service mode - immobilizer.service.status
0x80 – Immobiliser, bit appears during introduction of a programmed sequence of keys in the car - immobilizer.keys.status
Byte 3
0x01 – The key is in ignition lock - can.ignition.key.status
0x02 – Ignition on - can.engine.ignition.status
0x04 – Dynamic ignition on - can.dynamic.ignition.status
0x08 – Webasto - can.webasto.status
0x10 – Car closed - can.car.closed.status
0x20 – Car closed by factory's remote control - can.car.closed.remote.status
0x40 – Factory-installed alarm system is actuated (is in panic mode) - factory.alarm.actuated.status
0x80 – Factory-installed alarm system is emulated by module - factory.alarm.emulated.status
Byte 4
0x01 – Parking activated (automatic gearbox) - can.parking.status
0x10 – Handbrake is actuated (information available only with ignition on) - can.handbrake.status
0x20 – Footbrake is actuated (information available only with ignition on) - can.pedal.brake.status
0x40 – Engine is working (information available only when the ignition on) - can.engine.working.status
0x80 – Reverse is on - can.reverse.gear.status
Byte 5
0x01 – Front left door opened - can.driver.door.status
0x02 – Front right door opened - can.passenger.door.status
0x04 – Rear left door opened - can.rear.left.door.status
0x08 – Rear right door opened - can.rear.right.door.status
0x10 – Engine cover opened - can.hood.status
0x20 – Trunk door opened - can.trunk.status
Byte 6
0x01-0x05 – Different remote control states - car.remove.control.state
0x80 – CAN module goes to sleep mode - can.module.sleep.mode

namo

To resolve parameter names collision, parameter ID 303 Instant Movement now is stored into flespi parameter instant.movement.status.
Before the update Param ID 303 was registered as movement.status parameter, which was already taken by Param ID 240 Movement.
List of Teltonika Param IDs with affected device types can be found here.

baja

Teltonika devices now can be configured over UDP connection
This update had been installed with some minor bug fixes in Teltonika device settings.

baja

baja This update had a bug in the format of ACK sent via UDP . This lead to inproper work of Teltonika devices connected over UDP. The bug had been fixed.
Fixed bug with processing of 0xFF ping byte for UDP protocol.

baja

geofence AVL IDs parsing bug fixed.
previous logic was that number of geofence had been stored into geofence.id parameter, while its state was parsed as
0=false, 1=true ==> geofence.status
2=false, 3=true ==> overspeeding.status
The problem was when 1 message contained several geofence AVL IDs, so the parsing of the last AVL ID erased previously parsed geofence parameters.
The solution is - migrate geofence id to parameter index. So the new logic is

geofence.id parameter will be removed
value is parsed to
0=false, 1=true ==> geofence.status.INDEX_OF_GEOFENCE
2=false, 3=true ==> overspeeding.status.INDEX_OF_GEOFENCE

old logic and new logic are now working in parallel. Old logic will be removed July 21st

baja

FMB640 series added parsing of IDs:
16 to can.tracker.counted.mileage
216 to vehicle.mileage

New setting of Crash counter implemented for FMB series:

baja

TST100 device parsing updated: 242 ==> mandown.alarm.status, 386 ==> position.fix.age

FMB640 series odoset setting added

namo

Parameter ID=248 Immobilizer is supported for Teltonika FMB devices.
The following parameters are registered in flespi depending on Param ID=248 value:

if immobilizer value is 0: ibutton.connected.status=false parameter is registered
if immobilizer value is 1: ibutton.connected.status=true parameter is registered
if immobilizer value is 2: both parameters ibutton.connected.status=true and ibutton.authorized.status=true are registered

baja

Bugfix in Setting for tst100 and tft100 device types:
motion_detection_sas setting was working not correctly: starting from the firmware 55.00.04++ it works the same way as for FMB series, thus setting motion_detection_sas moved to motion_detection with bitmask as sources.

baja

Minor updates:

Dallas temperature sensor parsing suppression added for values 850, 2000, 3000, 4000, 5000 (it was enabled for 3000 only)
Bugfix: the response from the device is added to command result for all commands
TLS setting added

baja

Minor updates:

manual CAN elements parsing added for FMB640 series as manual.can.ID and manual.can.extended
several bugfixes in parsing for telmetry data and command responses

baja

New custom command added. It's schema is super simple: any of:

field text (in this way command may be also sent as SMS)
field hex to send binary data as codec12 connection command

namo

Teltonika protocol updated: SuperSoco I/O elements are supported for Teltonika TFT100.
Mapping of TFT100 AVL IDs into flespi parameters is below:

855 Power - supersoco.power.status, boolean
856 Current Trip Range - supersoco.current.trip.range
857 Total Trip Range - supersoco.total.trip.range
858 Battery Capacity - supersoco.battery.capacity
859 Low Voltage - supersoco.voltage.low.status
860 High Temperature - supersoco.temperature.high.status, boolean
861 Upload Time - supersoco.upload.time
862 Moving Abnormal - supersoco.moving.abnormal.status, boolean
863 Range - supersoco.range
864 Lock Status - supersoco.lock.status, boolean
865 Vehicle FW version - supersoco.fw.version
866 Total Range - supersoco.total.range
867 Battery Energy - supersoco.battery.energy
868 Power System Error - supersoco.power.system.error, string
869 Power Train Error - supersoco.powertrain.error, string
870 Instrument System Error - supersoco.instrument.system.error, string