2 models added:

• Teltonika FMC250
• Teltonika FMM250

Parsing scheme updated for FMC650 series Tacho related parameters:

Starting today, next parameters will be available through both custom parameters and standardized parameter names. After March 24, 2025, only the standardized parameter names will remain.

custom.param.10501 renamed to tacho.driver.time.before.warning
custom.param.10503 renamed to tacho.next.calibration.timestamp
custom.param.10504 renamed to tacho.driver.daily.rest.end.timestamp.1
custom.param.10505 renamed to tacho.driver.weekly.rest.end.timestamp.1
custom.param.10506 renamed to tacho.driver.weekly.second.rest.end.timestamp.1
custom.param.10510 renamed to tacho.driver.daily.limit.exceed.number.1
custom.param.10511 renamed to tacho.driver.daily.rest.end.timestamp.2
custom.param.10512 renamed to tacho.driver.weekly.rest.end.timestamp.2
custom.param.10513 renamed to tacho.driver.weekly.second.rest.end.timestamp.2
custom.param.10524 renamed to tacho.driver.daily.minimum.rest.duration.1
custom.param.10525 renamed to tacho.driver.daily.minimum.rest.duration.2
custom.param.10526 renamed to tacho.driver.weekly.minimum.rest.duration.1
custom.param.10527 renamed to tacho.driver.weekly.minimum.rest.duration.2
custom.param.10532 renamed to tacho.driver.remaining.current.driving.duration.1
custom.param.10533 renamed to tacho.driver.remaining.shift.driving.duration.1
custom.param.10534 renamed to tacho.driver.remaining.weekly.driving.duration.1
custom.param.10535 renamed to tacho.driver.compensation.last.week.1
custom.param.10536 renamed to tacho.driver.compensation.before.last.week.1
custom.param.10537 renamed to tacho.driver.compensation.second.before.last.week.1
custom.param.10539 renamed to tacho.driver.remaining.current.rest.duration.1
custom.param.10540 renamed to tacho.driver.time.until.next.driving.1
custom.param.10541 renamed to tacho.driver.next.driving.duration.1

Special Case: Data Sending Parameter ID 10538: Parameter custom.param.10538 will be split into multiple parameters through bit extraction:

Bits 0-2 parsed to tacho.driver.remaining.ten.hour.driving.times.1
Bits 3-5 parsed to tacho.driver.remaining.reduced.daily.rest.periods.1
Bits 6-7 parsed to tacho.driver.unknown.periods.present.status.1
Bits 8-9 parsed to tacho.driver.card.data.available.status.1
Bits 10-11 parsed to tacho.driver.weekly.rest.calculation.status.1
Bits 12-13 parsed to tacho.driver.multi.manning.status.1
Bits 14-15 parsed to tacho.driver.time.overlap.status.1

Tacho functionality update.

• Improved processing of driver info data in the response from the tachograph.
• Improved processing of incorrect tracker behavior.
• Fixed the problem of ending the session when a file is successfully loaded or when an error is received.

For FMB640 series:

1. remastered parsing of Tell Tale statuses based on this documentation
   

2. several settings renamed:
   battery_voltage_io_640 => battery_voltage_io
   battery_level_io_640 => battery_level_io
   inputs1_fmb640 => inputs1
   analog_input1_io_640 => analog_input1_io
   analog_input2_io_640 => analog_input2_io
   axis_x_640 => axis_x
   axis_y_640 => axis_y
   axis_z_640 => axis_z
   inputs2_fmb640 => inputs2
   inputs3_fmb640 => inputs3
   inputs4_fmb640 => inputs4

3. bugfix in parsing of ID 255: now the value is stored to parameter overspeeding.speed. If the value is higher than overspeeding limit set in overspeeding_dout3 setting, then the parameter overspeeding.status = true stored, otherwise overspeeding.status = false stored

New device type FTM305 added

baja the recent update of parameters with fms.tell.tale. prefix was changed: now the parameters just have can. prefix, and are ended with .indicator.state to be unified with volvo-trucks Tell Tale parameters. Full list under

Tacho functionality update.

Added automatic file request function for Tacho WEB functionality.
The required file types for uploading can be specified in the device configuration:

The function works when using the Tacho WEB functionality, which is designed for periodic connection to the server to download tachograph data, with the ability to specify the connection interval, for example: once every few hours the tracker will connect to the server and if the interval specified in the device configuration is reached, the server will give permission to download the specified files. If the interval has not yet been reached and the device has connected to the server, an event of the type will be registered in the device logs: tacho communication (Tachograph specific status) with a description of the event:
tacho_code_description : "The tacho auto download interval has not yet been reached. Time remaining: 602948 sec"

Teltonika protocol updated.
The following parameters are renamed:

• can.rear.left.passenger.seatbelt.status ==> can.rear.left.seatbelt.status
• can.rear.right.passenger.seatbelt.status ==> can.rear.right.seatbelt.status
• can.rear.central.passenger.seatbelt.status ==> can.rear.central.seatbelt.status

To ensure backward compatibility both new and old parameters will be registered for 2 more week, until 2025-Apr-18. On the mentioned date old parameters *.passenger.seatbelt.status will be removed.

Tacho fix: fixed the problem of parsing the driver's name. Case when the tracker does not read correctly or the tachograph incorrectly returns the driver's name. Now such behavior does not happen parsing error and the loading process can be continued.

Teltonika protocol is updated: old parameters are removed after renaming (see namo)

Tacho functionality update: added functionality for the models: fm6300, fm6320, fmb630, fmb640

setparam command bugfix: \r\n ending bytes removed
newly added AVL ID 1149 is now stored as network.lte.band

YuryAheichyk changes applied, can.dtc array contain objects now.

For reference, two additional parameters added:

• can.dtc.strings - contains errors in the old format (will be removed on May 24, 2025)
• can.dtc.objects - contains errors in the new format (will be removed on May 24, 2025)

can.dtc.strings example:
["P0020","U0001"]
can.dtc.objects example:
[{"standard":"OBDII","code":"P0020"},{"standard":"OBDII","code":"U001"}]

Teltonika protocol is updated: fixed parsing of gms.sim.iccid parameter for FMB devices.

Tacho functionality update: the authorization process with different generations of tachographs has been improved. In particular, the improvement concerns work with Stoneridge equipment. Current and potential problems have been fixed.
Important: the change works in tandem with version TBA 0.6.1.

Tacho functionality update:

• fixed the behavior of the yellow warning notification in the log when polling the driver information tracker. Now such a message will appear only if it was not possible to get the name or id of the driver for the file type that is currently being loaded. Previously, it could erroneously trigger for the second driver.
• Increased the TTL of the tacho command when sending via media-box to 600 seconds. Previously 300, it could cause the command to expire prematurely before completion.

can.electric.engine.status will be renamed to can.motor.status
can.limited.performance.electric.motor.indicator.state will be renamed to can.motor.limited.performance.indicator.state
can.electric.motor.failures.indicator.state will be renamed to can.motor.failures.indicator.state
Both parameters are registered for 2 weeks till June 5th.

Teltonika protocol is updated.

• AVL_ID 1388 OEM HV Battery Lifetime Power Use has been fixed and now is registered as signed integer value
• flespi parameters renamed:
  for AVL_ID 1388 OEM HV Battery Lifetime Power Use: parameter is renamed from can.hybrid.battery.consumed.capacity to can.vehicle.battery.energy.consumed
  for AVL_ID 1389 OEM HV Battery Lifetime Charge Power: parameter is renamed from can.hybrid.battery.charged.capacity to can.vehicle.battery.total.charge.energy
  Old parameters will be registered along with the new ones for 2 week, until 2025-Jun-12.

The update is related to Teltonika FMB003 device.