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

EvgenyShatilo

Tacho functionality udpate. Fixed encoding parsing error, more details here.

baja

New device type added: Teltonika FTC880

EvgenyShatilo

Tacho functionality udpate: fixed a bug with loading data from the second driver slot.
Corrections were made in accordance with the manufacturer's recommendations.

EvgenyShatilo

Tacho functionality udpate: fix error text & minor bug fixes.

baja

Manual CAN commands for TFT100 can now be configured from flespi settings

baja

New parameters parsing added:
FMB120 series: ID 622 - counter.impulses.frequency.1, ID 623 - counter.impulses.frequency.2
FMC650 series: ID 10502 - tacho.out.of.scope.condition.status

EvgenyShatilo

Tacho functionality udpate: mechanism has been added to check for the presence of a driver card in the tachograph slot. For example, if a file is requested from slot 2 but there is no card in it, a log message will be logged stating: The requested driver slot is not available. File loading will be skipped. and the file download process will be stopped.
If the file download process was initiated by the automatic download mechanism, then the file for the driver whose card is not in the tachograph slot will be skipped until the next interval.

baja

Teltonika FTC Series parameter update:

counter.impulses.1 (IO 4) - Counter for impulse counting
x.acceleration, y.acceleration, z.acceleration (IO 17, 18, 19) - Three-axis accelerometer data
accelerometer.calibration.state (IO 383) - Accelerometer calibration status
position.fix.age (IO 386) - Age of GPS position fix
engine.ignition.on.duration (IO 449) - Duration of engine ignition on state
Indexed gsm.mcc, gsm.mnc, gsm.lac, gsm.cellid (IO 13370-13389) - Neighboring cell tower info
crash.event (IO 247) - Crash detection event flag
crash.event.enum (IO 247) - Crash event type enumeration
geofence.status (IO 175) - Geofence enter/exit status
towing.alarm.status (IO 246) - Towing detection alarm

baja

Bugfix schedule: we identified incorrect parsing for CAN related parameters IDs 102 and 103 in FMB series devices.
How it was before (incorrect behavior):
ID 102 → can.trip.engine.motorhours (incorrect name)
ID 103 → can.engine.motorhours (incorrect name)

How It Is Now (Stage 1 - Transition Period)

ID 102 → can.trip.engine.motorhours (old, will be renamed in stage 2)
ID 103 → can.engine.motorhours (old, will be removed after transition)
can.counted.engine.motorhours (new, correct name)

Duration: 1 week transition period (till October 22)

What's Next (Stage 2)

After the transition period:
ID 102 → can.engine.motorhours (final correct name)
ID 103 → can.counted.engine.motorhours (final correct name)

Action Required

Users relying on can.engine.motorhours from ID 103 should migrate to can.counted.engine.motorhours
Both parameters will be available during the 1-week transition period

Also, after current update the value in ID 103 can be checked and configured via a separate CAN setting:

baja

Second stage of transition to new parsing scheme for FMB series IDs 102 and 103:
ID 102 → can.engine.motorhours
ID 103 → can.counted.engine.motorhours

EvgenyShatilo

Tacho functionality update:

Internal fixes, performance optimization.
The Tacho WEB setting now checks the server address to ensure it matches the flespi channel address. If successful, the setting will be stopped with a message similar to the following: Using the flespi channel as a Tacho WEB server is prohibited. The execution of the setting will be stopped.

EvgenyShatilo

Tacho functionality update: аdded ignition check for automatic uploading mechanism.
The check is performed using the telemetry parameter #engine.ignition.status for all device models that use a tacho: FMC640, FMC650, FMM640, FMM650, FMB630, FMB640, FM6300, and FM6320.
This parameter corresponds to AVL_ID=239, which is typically included in the tracker's basic configuration.

Conditions:

If the telemetry parameter is present, the download check will only be performed if True.
If the telemetry parameter is absent, the check is performed as usual for each incoming message.
If the parameter is present but has not been changed recently, the 2-day rule applies. If the value exceeds this limit, the check will be performed as usual for each message.

EvgenyShatilo

Tacho functionality udpate: request_tachograph_file command changes & and optimization of card processing.

The command now has the ability to request a detailed memory file.
- Select specific files within the tachograph's memory (overview, activity, speed details, technical data, events, and faults).
- Activity data can be specified for a specific time interval from and to. Or, the last N days from the current time can be specified.
The command structure has changed, but this does not affect previously generated API requests.
- Parameters for requesting driver data have not changed: {"type":"driver1"}
- Parameters of the form: {"type":"memory"} will work, since the new parameters are optional and have default values.
- What it looks like now: {"activity":{"days":90},"detailed_speed":true,"events_faults":true,"overview":true,"technical_data":true,"type":"memory"}
- This is what the from/to time interval looks like: {"activity":{"from":1761589095,"to":1761761895},"detailed_speed":true,"events_faults":true,"overview":true,"technical_data":true,"type":"memory"}
By default, all parameters are enabled and the data interval is requested for the last 90 days.