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

  • Post #177

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.

    8 days later

    • baja

    • Post #178

    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.
        17 days later

        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"

          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.

          1. 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.
          2. 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.
          3. 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.

          7 days later

          • namo

          • Post #181

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

          • getgps
          • cpureset
          • getrecord
          • web_connect
          • getimeiccid

          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.

            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.

              7 days later

              2 models added:

              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

                    | New Unified Parameter Name | Old Teltonika Parameter Name | Old Volvo-trucks Parameter Name |
                    |----------------------------|------------------------------|--------------------------------|
                    | can.airbag.indicator.state | fms.tell.tale.airbag.state | can.ab.indicator.state |
                    | can.adblue.level.indicator.state | fms.tell.tale.adblue.level.state | can.abl.indicator.state |
                    | can.abs.failure.indicator.state | fms.tell.tale.abs.failure.state | can.abs.fail.indicator.state |
                    | can.abs.trailer.indicator.state | fms.tell.tale.abs.trailer.state | can.abs.trailer.indicator.state |
                    | can.adaptive.cruise.control.indicator.state | fms.tell.tale.acc.state | can.acc.indicator.state |
                    | can.emergency.braking.system.indicator.state | fms.tell.tale.emergency.braking.system.state | can.aeb.indicator.state |
                    | can.air.filter.clogged.indicator.state | fms.tell.tale.air.filter.clogged.state | can.afc.indicator.state |
                    | can.battery.charging.indicator.state | fms.tell.tale.battery.charging.state | can.bcc.indicator.state |
                    | can.brake.lights.indicator.state | fms.tell.tale.brake.lights.state | can.bl.indicator.state |
                    | can.brake.failure.indicator.state | fms.tell.tale.brake.failure.state | can.bm.indicator.state |
                    | can.ebs.indicator.state | fms.tell.tale.ebs.state | can.ebs.indicator.state |
                    | can.engine.coolant.level.indicator.state | fms.tell.tale.engine.coolant.level.state | can.ecl.indicator.state |
                    | can.engine.coolant.temperature.indicator.state | fms.tell.tale.engine.coolant.temperature.state | can.ect.indicator.state |
                    | can.engine.emission.failure.indicator.state | fms.tell.tale.engine.emission.failure.state | can.eef.indicator.state |
                    | can.engine.oil.indicator.state | fms.tell.tale.engine.oil.state | can.eo.indicator.state |
                    | can.engine.oil.level.indicator.state | fms.tell.tale.engine.oil.level.state | can.eol.indicator.state |
                    | can.engine.oil.temperature.indicator.state | fms.tell.tale.engine.oil.temperature.state | can.eot.indicator.state |
                    | can.esc.indicator.state | fms.tell.tale.esc.indication.state | can.esc.indicator.state |
                    | can.fuel.filter.pressure.indicator.state | fms.tell.tale.fuel.filter.pressure.state | can.ffdp.indicator.state |
                    | can.front.fog.light.indicator.state | fms.tell.tale.front.fog.light.state | can.ffl.indicator.state |
                    | can.fuel.level.indicator.state | fms.tell.tale.fuel.level.state | can.fl.indicator.state |
                    | can.malfunction.general.failure.indicator.state | fms.tell.tale.malfunction.general.failure.state | can.gf.indicator.state |
                    | can.high.beam.indicator.state | fms.tell.tale.high.beam.state | can.hb.indicator.state |
                    | can.height.control.indicator.state | fms.tell.tale.height.control.state | can.hc.indicator.state |
                    | can.hazard.warning.indicator.state | fms.tell.tale.hazard.warning.state | can.hw.indicator.state |
                    | can.low.beam.indicator.state | fms.tell.tale.low.beam.state | can.lb.indicator.state |
                    | can.lane.departure.indication.indicator.state | fms.tell.tale.lane.departure.indication.state | can.ldw.indicator.state |
                    | can.engine.mil.indicator.indicator.state | fms.tell.tale.engine.mil.indicator.state | can.mil.indicator.state |
                    | can.parking.brake.indicator.state | fms.tell.tale.parking.brake.state | can.pb.indicator.state |
                    | can.position.lights.indicator.state | fms.tell.tale.position.lights.state | can.pl.indicator.state |
                    | can.retarder.indicator.state | fms.tell.tale.retarder.state | can.ret.indicator.state |
                    | can.rear.fog.light.indicator.state | fms.tell.tale.rear.fog.light.state | can.rfl.indicator.state |
                    | can.service.maintenance.indicator.state | fms.tell.tale.service.maintenance.state | can.scm.indicator.state |
                    | can.steering.failure.indicator.state | fms.tell.tale.steering.failure.state | can.stf.indicator.state |
                    | can.trailer.connected.indicator.state | fms.tell.tale.trailer.connected.state | can.tc.indicator.state |
                    | can.transmission.fluid.temperature.indicator.state | fms.tell.tale.transmission.fluid.temperature.state | can.tft.indicator.state |
                    | can.tachograph.indication.indicator.state | fms.tell.tale.tachograph.indication.state | can.ti.indicator.state |
                    | can.transmission.failure.indicator.state | fms.tell.tale.transmission.failure.state | can.tmf.indicator.state |
                    | can.tire.failure.indicator.state | fms.tell.tale.tire.failure.state | can.tpms.indicator.state |
                    | can.ebs.trailer.indicator.state | fms.tell.tale.ebs.trailer.state | can.trailer.ebs.indicator.state |
                    | can.turn.signals.indicator.state | fms.tell.tale.turn.signals.state | can.ts.indicator.state |
                    | can.worn.brake.linings.indicator.state | fms.tell.tale.worn.brake.linings.state | can.wbl.indicator.state |
                    | can.windscreen.washer.fluid.indicator.state | fms.tell.tale.windscreen.washer.fluid.state | can.wwf.indicator.state |
                    | can.cooling.air.conditioning.indicator.state | fms.tell.tale.cooling.air.conditioning.state | N/A |
                    | can.disabled.persons.indicator.state | fms.tell.tale.disabled.persons.state | N/A |
                    | can.hatch.open.indicator.state | fms.tell.tale.hatch.open.state | N/A |
                    | can.park.heating.indicator.state | fms.tell.tale.park.heating.state | N/A |
                    | can.steering.fluid.level.indicator.state | fms.tell.tale.steering.fluid.level.state | N/A |
                    | can.articulation.indicator.state | fms.tell.tale.articulation.state | N/A |
                    | can.stop.request.indicator.state | fms.tell.tale.stop.request.state | N/A |
                    | can.pram.request.indicator.state | fms.tell.tale.pram.request.state | N/A |
                    | can.bus.stop.brake.indicator.state | fms.tell.tale.bus.stop.brake.state | N/A |
                    | can.raising.indicator.state | fms.tell.tale.raising.state | N/A |
                    | can.lowering.indicator.state | fms.tell.tale.lowering.state | N/A |
                    | can.kneeling.indicator.state | fms.tell.tale.kneeling.state | N/A |
                    | can.engine.compartment.temperature.indicator.state | fms.tell.tale.engine.compartment.temperature.state | N/A |
                    | can.auxiliary.air.pressure.indicator.state | fms.tell.tale.auxiliary.air.pressure.state | N/A |
                    | can.seat.belt.indicator.state | fms.tell.tale.seat.belt.state | N/A |
                    | can.esc.switched.off.indicator.state | fms.tell.tale.esc.switched.off.state | N/A |
                    | can.lane.departure.warning.off.indicator.state | fms.tell.tale.lane.departure.warning.off.state | N/A |
                    | can.engine.emission.filter.indicator.state | fms.tell.tale.engine.emission.filter.state | N/A |
                    | can.electric.motor.failures.indicator.state | fms.tell.tale.electric.motor.failures.state | N/A |
                    | can.adblue.tempering.indicator.state | fms.tell.tale.adblue.tempering.state | N/A |
                    | can.multiplex.system.indicator.state | fms.tell.tale.multiplex.system.state | N/A |
                    | can.battery.pack.indicator.state | fms.tell.tale.battery.pack.state | N/A |
                    | can.high.voltage.system.caution.indicator.state | fms.tell.tale.high.voltage.system.caution.state | N/A |
                    | can.battery.pack.temperature.indicator.state | fms.tell.tale.battery.pack.temperature.state | N/A |
                    | can.limited.performance.electric.motor.indicator.state | fms.tell.tale.limited.performance.electric.motor.state | N/A |
                    | can.battery.pack.cooling.indicator.state | fms.tell.tale.battery.pack.cooling.state | N/A |

                        10 days later

                        Tacho functionality update.

                        The configuration scheme has been changed. Now the configuration that relates to the tachograph is packed into an object that have to be activated before use. The company card number input field is mandatory.
                        Important:

                        • The tachograph configuration has been migrated to the new scheme on the server side.
                        • The Automatic file request option is not yet available for use and is undergoing active testing. Will be updated later.

                        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.

                          Write a Reply...