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

New device type added: Teltonika FTC305

baja

New parameters parsing added according to this Wiki specs about Hybrid vehicles for OBD-type trackers:

baja

Bugfix for TFT100: ID 817 charger.plug.status boolean value parsing inverted. Now it is false when charger is unplugged, and true when plugged.
Trip Odometer IO setting added for FMB series:

YuryAheichyk

Added optional field Command ID for serial_port command. Default value 0x0E(14)

baja

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

EvgenyShatilo

parameter media.type has been renamed to media.type.enum.description
The values of the parameters have not been changed ("Video rear", "Video front", "Photo rear" ,"Photo front")

baja

4 new generation device types added

Teltonika ATC700
Teltonika ATC704
Teltonika ATM700
Teltonika ATM704

baja

Parsing updated:
For FMB series IDs 306 to 309 parsed to indexed parameter ble.sensor.frequency
For FMC921 Id 841 to dout.overcurrent.status.1, ID 70 to pcb.temperature

EvgenyShatilo

Photo and Video protocol changes.

Change in the concept of the take_photo and request_video commands. The standard for this command in flespi is to use the channel number for which the data request is made. Previously, when only DashCam & DualCam were supported, it was necessary to select from which camera the video would be loaded, now this same field determines the channel number that corresponds to the device type.
According to the protocol, each camera (DualCam, ADAS, DSM) has only its own file_source that is used in the command. Therefore, in fact, nothing has changed in the operation of DualCam.
The take_photo command requests a photo only with the current timestamp. As parameters, it is necessary to select only the channel number that corresponds to the camera type. The photo resolution will correspond to what is set in the tracker configuration.
.
The request_video command. Has no changes except that now the camera type is also determined by the channel number. You can still select the video download time and its duration. The maximum video duration is still limited by the interface to 10 seconds, so that this happens as smoothly and quickly as possible.

Added ADAS support.

Devices that support photo & video upload: FMB640, FMC640, FMС650.
Devices that only support event registration: FMB125, FMU125, FMC125, FMB225, FMC225
Photo upload is available via the take_photo command, where you can select the channel number that corresponds to the device type. The photo resolution is taken from the tracker configuration.
Video upload is available via the request_video command, where you also need to select the channel number, timestamp and video duration.
Event photo & video upload also works correctly.
When registering a media file, a message with an event code will be registered, which is a trigger. For example:
```
camera.report.reason: Server request
camera.report.reason.enum: 0
```

YuryAheichyk

The parameters custom.param.605(606, 610, 612, 613, 614, 619) have been renamed to the parameters corresponding to ADAS events with the adas prefix. The parameters custom.param.11700(11701 - 11706, 11713) have also been renamed to the parameters corresponding to DSM events with the dsm prefix. List of new parameters:
adas.lane.departure.event
adas.distance.event
adas.collision.warning.event
adas.pedestrian.event
adas.traffic.sign.violation.event
dsm.fatigue.event
dsm.distraction.event
dsm.yawning.event
dsm.driver.phone.event
dsm.smoking.event
dsm.driver.missing.event
dsm.driver.mask.event
dsm.seatbelt.event

These events are only registered when the event is triggered.

baja

Parsing updated.
For OBD trackers new parameters from ELD_J1939_Parameters_definitions table

ID 1120 → can.brake.pressure (kPa)
ID 1176 → can.vehicle.mileage (km)
ID 1177 → can.engine.motorhours (h)
ID 1178 → can.engine.ignition.status
ID 1179 → can.parking.brake.status
ID 1180 → can.fuel.consumed (L)
ID 1181 → can.total.engine.idle.time (h)
ID 1182 → can.dtc.number
ID 1183 → can.fuel.level[index=2] (%)
ID 1184 → can.battery.voltage (V)
ID 1185 → can.fuel.idle.consumed (L)
ID 1186 → can.trip.vehicle.mileage (km)
ID 1187 → can.fuel.economy (km/L)
ID 1188 → can.ambient.air.temperature (°C)
ID 1189 → can.engine.load (%)
ID 1191 → can.engine.oil.temperature (°C)
ID 1192 → can.trip.fuel.consumed (L)
ID 1193 → can.engine.oil.pressure (kPa)
ID 1194 → can.driver.seatbelt.status
ID 1195 → can.cruise.control.state
ID 1196 → can.throttle.pedal.level (%)
ID 1197 → can.engine.coolant.level (%)
ID 1198 → can.engine.coolant.pressure (kPa)
ID 1199 → can.transmission.oil.temperature (°C)
ID 1201 → can.brake.pedal.level (%)

For FMX650 series:

ID 449 → engine.ignition.on.duration
ID 1161 → device.imei
ID 13200 → sim.card.error.count
ID 1148 → Multiple parameters:
- network.signal.rssi (dBm)
- network.signal.rsrp (dBm)
- network.signal.sinr (dB)
- gsm.signal.quality (dB)

Note: All parameters will be temporarily available in both formats (e.g., both as can.vehicle.mileage and custom.param.1176) until February 4, 2025, after which only the standard parameter names will remain.

baja

baja custom params from 21 January update removed.

For FMB650 series parsing for Ids 10493 to 10496 remastered. Current parameters:

can.dm1.dtc.number
can.dm1.dtc.time
can.dm2.dtc.number
can.dm2.dtc.time
will be removed on February 18th 2025. The array can.dtc with objects with parsed DTC codes will be stored instead.

EvgenyShatilo

Photo and Video protocol update:

Fixed an issue where an incorrect server address could be substituted into the command for uploading media data.
Improved handling of invalid media data from the device. For example, if the tracker sends a broken packet or data that does not match the protocol.

EvgenyShatilo

Photo and Video protocol update:

DSM implementation is added. Commands & events. Note: the protocol does not support video, only photos.
DashCam,DualCam,ADAS: Added registration of coordinates for an uploaded media file.

baja

flespi adapted to Teltonika's change in SMS events handling. More details here
On flespi you may find these settings at SMS tab:

SMS Number and SMS Text was removed from each I/O element configuration card.

EvgenyShatilo

Added new parameter with index 1433 for FT series:

#dead.reckoning.calibration.state.enum // numerical value (0-3)
#dead.reckoning.calibration.state:
    0 ==> "uncalibrated" 
    1 ==> "ready for calibration" 
    2 ==> "calibrating" 
    3 ==> "calibrated"

EvgenyShatilo

Tacho functionality is available now.
At the moment, only for the model is available: FMC650.

The ability to upload files from the tachograph access using the new command request_tachograph_file, you need to select the file type:

Driver slot 1 (Download file from the first driver card slot)
Driver slot 2 (Download file from the second driver card slot)
Tachograph memory (Download file from tachograph memory for 90 days)

Important! The command must be sent by a button TO QUEUE otherwise, the command will be sent once without the mechanism of re-sending.

According to the official documentation of the manufacturer, the tachograph will not allow you to download the file without the turned ignition ON. If the command was sent, then Warning event will be registered in the log
, that the ignition is turned OFF and the file download cannot be continued, after which the server will repeat the command through 5 minutes.

The text of the event corresponds to the description from the documentation:
Tachograph ignition as configured in global parameters (according to DIN1/2/3/4) is OFF. Vehicle ignition must be on for digital tachograph to work and to allow remote download.
In total, 3 attempts will be fulfilled send the command, after which the command will be removed from the queue due to the send limit of attempts.

Preliminary setting.

It is necessary to enable the Secondary URI option in the channel configuration. This is necessary so that the tracker can connect to the server in a separate connection and upload the file. The server address does not need to be entered anywhere, all the logic of data processing and a separate connection are hidden under the hood for the maximum convenience of the user.
For authorization, a configured and connected application is required Tacho Bridge App. Do not forget to check fresh versions. To help with setting fell free to ask Codi.
It is also necessary set the company's card number in the configuration of the device.

The entire downloading process is accompanied by logging of every significant stage from sending a command to saving a file.

P.S: additional tacho functionality will be added soon.

namo

Teltonika protocol updated: added new Actions settings for Teltonika FTC921 and Teltonika FTC961 devices:

getgps
cpureset
getrecord
web_connect
getimeiccid

EvgenyShatilo

Change in the naming of parameters for media (DualCam, DashCam, ADAS).
Now the coordinates that are transmitted along with a media file, such as a photo or video, are registered as position.media.latitude, position.media.longitude.
Previously, the coordinates were registered as normal parameters: position.latitude, position.longitude, which could cause coordinate outliers on the map, and also complicated the analysis of data using the camera.

If you need to return the coordinates to their previous form, please use the msg-expression plugin, for more complex cases the PVM plugin.

EvgenyShatilo

Tacho functionality update.

Added models for working with tacho: FMC640, FMM640.
Changed file naming according to EU regulations:
- The driver card file now fully complies with the regulations: C_20250303_0803_N_Surname_1220000000000000.DDD
- The file from the tachograph memory has the correct format, but does not include the VIN and state number of the vehicle: M_20250302_2246__.DDD.
- The file extension is currently always *.DDD. In the future, it will be determined automatically depending on the country of registration of the driver or tachograph.
Improved loading of tachograph memory file, type "memory". Now the file contains the full structure according to the regulations, and not only driver activity data.
Improved loading validation. Added checks for ignition on with registration of accompanying messages in the device log.
Added the ability to configure Tacho settings. Tachograph DDD dowload source where you can configure the number of the CAN bus used (1 or 2). And also Tachograph ignition source with ignition source setting (ignition or DIN1-4).
Tacho WEB. Function for automatic file upload to flespi server.
- To configure this option, you must use the Tacho WEB settings setting. The tracker connection timeout to the server can be set from 0 to 255 minutes.
- When the tracker is automatically connected, the flespi server will request 3 files from the tachograph to be downloaded: driver 1, driver 2, data from the tachograph memory (for 90 days).
- The server address for downloading files can be specified as custom, not only flespi.
- IMPORTANT! To configure the flespi server address, you must leave the host fields empty, and the port must be 0 and the server will send the correct configuration to the device. Preliminary TBA configuration is required.