The device type FMC650 was added.

Settings were added for TAT100 device.
As TAT100 is an asset tracker that works mostly on battery power for a long time, it might be critical that the current setting value should not be requested from the device. Thus "Settings polling" device configuration field was set to "never" for all devices of such type. If you need the settings to be synced - you may do it in SetBox, or via updating the "Settings polling" field in the device configuration.

"Secondary GPRS server mode" field was added to "Secondary GPRS Server Setup" (applicable for Professional trackers only)

2 months later

Changed EYE sensor parameters:
custom.param.10824...10827 to eye.sensor.battery.voltage.1...4
custom.param.10804...10807 to eye.sensor.humidity.1...4
custom.param.10820...10823 to eye.sensor.low.battery.status.1...4
custom.param.10808...10811 to eye.sensor.magnet.status.1...4
custom.param.10836...10839 to eye.sensor.movement.count.1...4
custom.param.10812...10815 to eye.sensor.movement.status.1...4
custom.param.10816...10819 to eye.sensor.pitch.angle.1...4
custom.param.10832...10835 to eye.sensor.roll.angle.1...4
custom.param.10800...10803 to eye.sensor.temperature.1...4

We added a new command "Set IO param". This will allow you to configure IO params as you wish.
For example, you want to setup Battery voltage input to generate an event when the voltage leaves the range from 2500mv to 3300mv. The event should have a low priority and should be added to every AVL record.
This is how it can be done using the new command:

This is how it can be configured using Teltonika Configurator tool:

13 days later

Changing the naming of parameters:

The change applies to models: FMB001, FMB002, FMB003, FMC001, FMC003, FMM003
389 - can.vehicle.mileage
390 - can.fuel.volume
402 - can.service.mileage
410 - can.vehicle.battery.charging.status
411 - can.vehicle.battery.level
412 - can.vehicle.battery.power.consumption
755 - can.vehicle.remaining.range
1151 - can.vehicle.battery.health
1152 - can.vehicle.battery.temperature

General parameter changes:
can.vehicle.battery.range and can.vehicle.remaining.range now displays values in kilometers.
also added:
543 - can.hybrid.onboard.power.voltage
544 - can.hybrid.onboard.current

Attention!

01.05.2023 the battery.charging.status parameter will be renamed to can.vehicle.battery.charging.status.
The changes have already been added to the server and the parameter are registered with a new name. When the time is reached, the old one will be deleted.

  • baja replied to this.
    9 days later

    • baja

    • Post #119

    baja remastering of previously added parameters
    ID 10828: array parameter visible.beacons renamed to ble.beacons
    ID 10829: array parameter found.beacons renamed to ble.beacons with field state: found at each beacon object
    ID 10831: array parameter lost.beacons renamed to ble.beacons with field state: lost at each beacon object

    ID 11317 now stored to array parameter eye.beacons will be renamed to ble.beacons in 10 days, May 5th

    ID 1151 (OEM Battery State Of Health) stored as can.vehicle.battery.health multiplier 0.1 removed
    ID 1152 (OEM Battery Temperature) stored as can.vehicle.battery.temperature multiplier 0.01 removed

      6 days later

      Parsing update for FMB640 series:
      ID 10507: (Driver 1 current daily driving time) to parameter tacho.driver.daily.driving.duration.1
      ID 10508: (Driver 1 current weekly driving time) to parameter tacho.driver.weekly.driving.duration.1
      ID 10509: (Driver 1 time left until new daily rest period) to parameter tacho.driver.daily.before.rest.duration.1
      ID 10514: (Driver 2 current daily driving time) to parameter tacho.driver.daily.driving.duration.2
      ID 10515: (Driver 2 current weekly driving time) to parameter tacho.driver.weekly.driving.duration.2
      ID 10516: (Driver 2 time left until new daily rest period) to parameter tacho.driver.daily.before.rest.duration.2
      IDs 10518 + 10519 to parameter driver.name.1
      IDs 10520 + 10521 to parameter driver.name.2
      ID 10522: (Driver 1 Time Left Until New Weekly Rest Period) to parameter tacho.driver.weekly.before.rest.duration.1
      ID 10523: (Driver 2 Time Left Until New Weekly Rest Period) to parameter tacho.driver.weekly.before.rest.duration.2
      ID 10528: (Driver 1 Duration Of Next Break Rest) to parameter tacho.driver.next.rest.duration.1
      ID 10529: (Driver 2 Duration Of Next Break Rest) to parameter tacho.driver.next.rest.duration.2
      ID 10530: (Driver 1 Remaining Time Until Next Break Or Rest) to parameter tacho.driver.remaining.before.rest.duration.1
      ID 10531: (Driver 2 Remaining Time Until Next Break Or Rest) to parameter tacho.driver.remaining.before.rest.duration.2

      Parsing update for FMB series as notfied here EvgenyShatilo :
      battery.charging.status in security state flags renamed to can.vehicle.battery.charging.status. (Old parameter removed)

      Together with this baja update, the parameters prefixed with eye.sensor. will be renamed to ble.sensor.

          Device types added:
          FMM80A
          FMM650
          FMB930

          baja
          eye.beacons duplicated parameter removed
          eye.sensor.temperature renamed to ble.sensor.temperature
          eye.sensor.humidity renamed to ble.sensor.humidity
          eye.sensor.magnet.status renamed to ble.sensor.magnet.status
          eye.sensor.movement.status renamed to ble.sensor.movement.status
          eye.sensor.pitch.angle renamed to ble.sensor.pitch.angle
          eye.sensor.low.battery.status renamed to ble.sensor.low.battery.status
          eye.sensor.battery.voltage renamed to ble.sensor.battery.voltage
          eye.sensor.roll.angle renamed to ble.sensor.roll.angle
          eye.sensor.movement.count renamed to ble.sensor.movement.count

            24 days later

            For Teltonika FMC640 series of devices new set of parameters integrated with readings from connected TK Transcan:

            • freezer.transcan.temperature: Sensor temperature reported by TK Transcan
            • freezer.transcan.state.enum: Status value as reported by TK Transcan
            • freezer.transcan.alarm.enum: Alarm value as reported by TK Transcan
              14 days later

              Parameters renaming schedule on June 19th:
              AVL ID 331 to 334, ble.sensor.payload.hex.1 to ble.sensor.payload.hex.4 renamed to ble.1.custom.payload.hex.1 to ble.4.custom.payload.hex.1. Both parameters are stored now, old names will be removed in a week
              New parameters parsing added for IDs 463 to 474. In Teltonika documentation they are described as
              BLE X Custom #Y and may be unsigned 4 bytes integer or data chunk in HEX mode
              so they are stored as
              ble.X.custom.Y for integer mode
              ble.X.custom.payload.hex.Y for HEX mode

                • baja

                • Post #124
                • Edited

                Parsing update for temperature and humidity sensors: when sensors report the code that shows that the value is incorrect, the parameter with the value will not be stored, but string error code will be stored instead
                IDs 72 to 75: parameter sensor.temperature.1 to sensor.temperature.4 extra parameter sensor.temperature.error.code.1 to sensor.temperature.error.code.4
                IDs 25 to 28: parameter ble.sensor.temperature.1 to ble.sensor.temperature.4 extra parameter ble.sensor.temperature.error.code.1 to ble.sensor.temperature.error.code.4
                IDs 86, 104, 106, 108: parameter ble.sensor.humidity.1 to ble.sensor.humidity.4 extra parameter ble.sensor.humidity.error.code.1 to ble.sensor.humidity.error.code.4

                  a month later

                  AVL ID 11317 parsing updated, added mac.address and magnet.count parameters to ble.beacons array

                  17 days later

                  Major update in ibutton.code parameter: Teltonika tech team reported to us that all the values for ibutton.code parameter parsed from ID 78 for all the device types are sent in reversed bytes order. So now flespi stores it in reversed order, and we need to reverse it back to be in touch with reality. So now, together with ibutton.code parameter we have parameters ibutton.code.old and ibutton.code.new. Now ibutton.code.old is the same as ibutton.code, ibutton.code.new is made of reversed bytes of ibutton.code. In 2 weeks, August 17th, ibutton.code will become reversed, the same as ibutton.new. In 1 month, September 3rd, ibutton.code.new and ibutton.code.old will be removed. You may now prepare your infrastructure and create a plugin that renames ibutton.code.new to ibutton.code. Contact our team in flespi chat if you need assist with that.

                  FMB640 series parsing update:
                  Bugfix in IO ID 109 that is parsed into fms.sfotware.version
                  FMS Eco driving parameters supported.

                  fms.event.enum
                  fms.vehicle.vin
                  fms.active.driver.id
                  fms.event.number
                  fms.coasting.mileage
                  fms.coasting.fuel.used
                  fms.coasting.time
                  fms.ecoroll.mileage
                  fms.ecoroll.fuel.used
                  fms.ecoroll.time
                  fms.braking.mileage
                  fms.braking.fuel.used
                  fms.braking.time
                  fms.braking.number
                  fms.retarder.mileage
                  fms.retarder.fuel.used
                  fms.retarder.time
                  fms.cruise.mileage
                  fms.cruise.fuel.used
                  fms.cruise.time
                  fms.torque.mileage
                  fms.torque.fuel.used
                  fms.torque.time
                  fms.pto.mileage
                  fms.pto.fuel.used
                  fms.pto.time
                  fms.driving.fuel.used
                  fms.idle.fuel.used
                  fms.engine.load.fuel.used
                  fms.total.mileage
                  fms.total.fuel.used
                  fms.total.time
                  fms.short.stops.number
                  fms.long.stops.number
                  fms.parking.brake.number
                  fms.harsh.acceleration.number
                  fms.harsh.braking.number
                  fms.harsh.cornering.number
                  fms.mileage.speed.range
                  fms.fuel.used.speed.range
                  fms.time.speed.range
                  fms.mileage.rpm.range
                  fms.fuel.used.rpm.range
                  fms.time.rpm.range
                  fms.mileage.torque.range
                  fms.fuel.used.torque.range
                  fms.time.torque.range
                  fms.mileage.braking.range
                  fms.fuel.used.braking.range
                  fms.time.braking.range

                  11 days later

                  DashCam Data Sending Parameters ID parsing parameters update:

                  Camera ping transmission and TF status checking parameters ID (id 498) recorded as 2 parameters:
                  camera.report.reason.enum - represented as numeric value.
                  camera.report.reason - and textual human-readable value with values:

                  0="Server request"
1="DIN1"
2="DIN2"
3="Crash"
4="Towing"
5="Idling"
6="Geofence"
7="Unplug"
8="Green Driving"

                  Image sending trigger parameters ID (id 499) recorded as 2 parameters:
                  camera.state.enum - represented as numeric value.
                  camera.state - and textual human-readable value with values:

                      0="Camera not detected"
    1="No card"
    2="Card mount failed"
    3="Card mounted"
    4="Card faulty"

                    • baja

                    • Post #128

                    baja ibutton.code first update postponed to August 24

                        7 days later

                        • baja

                        • Post #129

                        baja Update installed, ibutton.code parameter has now the same value as ibutton.code.new. If this affects your operations contact flespi team immediately, we'll help you to deal with the problem. It can be done by simple using of ibutton.code.old, which is still available in message parameters

                        FMX640 series parsing change in AVL ID 548. It is now parsed the same way as other device series according to this specification

                            8 days later

                            • baja

                            • Post #130

                            The removal of ibutton.code.old and ibutton.code.new parameters postponed to 14th September

                            • baja replied to this.
                              4 days later

                              Teltonika DualCam with IMAGE uploading function is now implemented on flespi: https://wiki.teltonika-gps.com/view/Teltonika_DualCam
                              The process of uploading photos is integrated and works automatically, provided that the camera is correctly configured. You can also request a photo using the take_photo command.

                              The photo is loaded in an additional connection. Along with the photo, the media.url parameter is registered, which contains a link for public viewing of the image.

                              10 days later

                              • baja

                              • Post #132

                              baja ibutton.code.old and ibutton.code.new parameters removed

                                  Corrections have been made to the take_photo photo upload command.
                                  Reasons: there may have been an error with the media file type request.

                                    4 days later

                                    Added VIDEO download support for DualCam and DashCam.
                                    The photo is available for all models that can operate the camera: FMB125, FMB225, FMC125, FMC225. Video is currently limited to models only: FMC125, FMC225.
                                    You can request videos and photos on the MEDIA tab, which becomes available when you enable the experimental functionality in your account settings.

                                    When you click on the video download button, an additional window will appear in which you have to select:

                                    1. Channel for downloading the video file
                                    2. Indicate the time that will serve as the beginning of the video
                                    3. Duration of the video. (at the moment, the duration of the video clip is limited to 10 seconds. Minimum value 1 second.)

                                      All necessary information for the video file is recorded in logs and messages: metadata, title, public link to the file.
                                    6 days later