[Changelog] teltonika protocol

bird

FMC650/FMM650: DTC DM1 List (AVL 10494) and DTC DM2 List (AVL 10496) are now parsed into can.dtc objects (J1939 spn, fmi, cm, oc, source address sa and CAN bus bus; DM1 entries status active, DM2 entries historical). Fixed SPN decoding of DTC DM1/DM2 (AVL 10493/10495); DM2 codes now reported with status historical instead of pending. custom.param.10494 and custom.param.10496 are registered alongside for now and will be removed on 2026-10-23.
Fixed scaling of OEM HV battery parameters can.hybrid.battery.min.cell.voltage, can.hybrid.battery.max.cell.voltage, can.hybrid.battery.capacity and can.hybrid.battery.measured.capacity for FMB003, FMC003, FMM003 and FMM00A: values were reported 10 times too high.

bird

Bugfix in Manual CAN settings:

TFT100 manual_can_0...manual_can_9: can now be saved with Data, Send Period, Response Trigger or Send Count left empty; only the provided fields are written to the device.
FMX640 manual_can_request: can now be saved without Payload (e.g. for RTR requests).
FMX640 mcan_cmd: CAN ID and Data overrides must now be set together.

bird

New device configuration field sms_password for FTC/FTM and ATC/ATM devices, used to send SMS commands to devices protected with an SMS password.

Bugfix: SMS commands to FTC/FTM and ATC/ATM devices are now sent in the documented format, with the SMS password or a single leading space before the command.

EvgenyShatilo

tacho update: fixed parsing of tachograph driver names (AVL IDs 10518-10521) when the name is followed by 0xFF padding. With some code pages, for example Greek ISO-8859-7, such records were rejected: the device kept resending the same record and no new data was stored.
These records are now parsed correctly, and data buffered on the device uploads automatically without any action on the device.

bird

Fixed handling of GNSS status value 4 (AVL ID 69): FMB/FMC/FMM/FMT devices now report gnss.status true and position.valid false (GNSS ON with fix, invalid data); TAT/TST/TFT/GH/TMT devices report gnss.status and position.valid false (GNSS OFF in Static Navigation).

EvgenyShatilo

Tacho update: fixed automatic tachograph file download getting stuck.
When a driver card file request failed and the card was not in the slot, the scheduler stopped and never requested the other files (vehicle unit memory or the second driver slot).
Now the remaining files keep downloading on schedule, and the file for the missing card is requested as soon as the card is inserted. For Teltonika devices a failed tachograph check (tachocheck) now frees the queue immediately instead of waiting 10 minutes.

EvgenyShatilo

Parameters update:
AVL 10538 "Driver 1 Additional Information" (FMC650, FMB640 and other tacho-enabled models) no longer reports undefined bit field codes as valid values.
When the device sends "not available" or "error" codes, for example while the tachograph is not connected, the parameters: tacho.driver.remaining.ten.hour.driving.times.1, tacho.driver.remaining.reduced.daily.rest.periods.1, tacho.driver.unknown.periods.present.status.1, tacho.driver.card.data.available.status.1, tacho.driver.weekly.rest.calculation.status.1, tacho.driver.multi.manning.status.1 and tacho.driver.time.overlap.status.1 are now omitted from the message instead of being stored as counters like 7 or as true.
A true value in these parameters now always reflects a real condition reported by the tachograph.

baja

Data sending parameter IDs changes:

Previously these AVL IDs were stored as custom.param.<ID>. They are now parsed into named parameters.
During a transition period until 2026-10-30, custom.param.<ID> is still stored with the same value as before; after that date it will be removed.

FMB640, FMB641, FMC640, FMC650, FMM640, FMM650, FM6300 family
108 device.uptime.records.count
226 can.cng.status
227 can.cng.consumed
228 can.cng.level
507 can.battery.voltage
522 can.retarder.torque.load
523 can.total.cruise.control.time
524 can.engine.oil.level
526 can.vehicle.battery.range
10517 tacho.driver.daily.limit.exceed.number.2
10631 can.driver.seatbelt.status
10632 can.front.passenger.seatbelt.status
13261, 13262 tacho.driver.load.time.1, tacho.driver.load.time.2
13263 tacho.driver.private.data.consent

FMB family
185 can.spreader.working.hours
188 can.retarder.torque.load
189 can.total.cruise.control.time
190 geofence.status.24, overspeeding.status.24
1412 motorcycle.fall.event

bird

FMB930 now has two digital outputs: settings outputs1, setdigout_1 and the DOUT1 scenario settings are replaced with outputs2, setdigout_2 and the DOUT2 scenario settings (including seco_dout2). Fixed reading of digital output states from getio replies.
New setting added for FMB150, FMC150, FMM150, FMC250, FMM250: SECO - secure engine cut-off, Miscellaneous tab

« Previous Page