EDITED
Scheduled protocol change rejected
Changelog relates to those who uses generic device type.
Protocol change schedule: generic device type which parses AVL IDs by the same scheme as FMB110 will be changed at November 14th. All AVL IDs for generic device type will be stored upon custom.param.ID names and raw values. The parsing of timestamp and positioning data will remain the same.
Bugfix schedule: Together with removing codec12 command on December 1st, there will be change in parsing for BLE temperature sensor values for categories of: Easy, Advanced, Special trackers from here
AVL IDs 25 to 28 responsible for indexed parameters ble.sensor.temperature.1 to ble.sensor.temperature.4 parsing multiplier will be changed from 0.1 to 0.01. The change is caused by update in Teltonika documentation . It might be so that older FW version of trackers or sensors will still report value multiplied by 0.1 . If this is the case for you, you may revert back old values by multiplying new values by 10 via this plugin:
{
"required": true,
"enabled": true,
"validate_message": "",
"item_type": 11,
"name": "pvm-plugin",
"configuration": {
"code": "optional .ble.sensor.temperature.1[number] ==> this * 10 ==> #ble.sensor.temperature.1\noptional .ble.sensor.temperature.2[number] ==> this * 10 ==> #ble.sensor.temperature.2\noptional .ble.sensor.temperature.3[number] ==> this * 10 ==> #ble.sensor.temperature.3\noptional .ble.sensor.temperature.4[number] ==> this * 10 ==> #ble.sensor.temperature.4"
},
"priority": 0,
"type_id": 1,
"timezone": "UTC"
}
Another note: there are several error codes specified for the sensor values:
4000 - abnormal sensor state
3000 - sensor not found
2000 - failed sensor data parsing
But according to Teltonika support, there is no way to tell temperature 20 from error code 2000 with multiplier 0.01. So flespi will not process error codes, this will be user's responsibility. Usually, sensor can be treated in error state when its value is not changed for long period of time in one of the error codes state.
baja codec12 command removed
AVL IDs 25 to 28 responsible for indexed parameters ble.sensor.temperature.1 to ble.sensor.temperature.4 parsing multiplier is changed from 0.1 to 0.01
bugfix in trip_scenario for OBD and FMB trackers
FMB series: ID 282 is stored to can.dtc string
FMB640 series ID 144 stored to sd.status parameter
baja
actually, the command for external device has to be a bit more sophisticated (details here), because it can be also a Garmin device or a Paired Bluetooth device connected, so:
external_device_packet renamed to serial_port
bluetooth command added to forward commands to paired bluetooth device
garmin command added to forward commands to Garmin System
FMB640 series parsing scheme update:
new parameters added:
224 - ultrasonic.fuel.level.1
225 - ultrasonic.fuel.level.2
208 - ultrasonic.software.state.enum.1
209 - ultrasonic.software.state.enum.2
10009 - eco.driving.events.number
10487 to 10492 - sensor.humidity.1 to sensor.humidity.6
109 - fms.software.version
110 - fms.diagnostics.supported
111 - fms.requests.supported
122 - fms.movement.direction
123 - fms.tacho.performance
124 - fms.handling.info
125 - fms.system.event
137 - pto.drive.engagement.enum
229 - fms.adblue.state.enum
357 - can.brake.pedal.level
10428 to 10431 - fms.tell.tale.1 to fms.tell.tale.4
10445 - can.adblue.level
176 - can.dtc.number
550 to 599 - geofence.status.51 and overspeeding.status.51 to geofence.status.100 and overspeeding.status.100
257 - acceleration.array json array of json objects with x, y,z keys showing acceleration on each axis
258 - max.x.acceleration, max.y.acceleration, max.z.acceleration
259 - average.x.acceleration, average.y.acceleration, average.z.acceleration
260 - eco.driving.event.duration
251 - immobilizer.state
183 - tacho.drive.recognize.status
189 to 190 - tacho.driver.time.state.enum.1 and tacho.driver.time.state.1 to tacho.driver.time.state.enum.2 and tacho.driver.time.state.2
56 to 57 - tacho.driver.continuous_driving.duration.1 to tacho.driver.continuous_driving.duration.2
58 to 59 - tacho.driver.cumulative_break.duration.1 to tacho.driver.cumulative_break.duration.2
60 to 61 - tacho.driver.selected.activity.duration.1 to tacho.driver.selected.activity.duration.2
69 - tacho.driver.cumulative_driving.duration.1
77 - tacho.driver.cumulative_driving.duration.2
48 - tacho.data.source
indexed parameter device.com.connection.status parsed from IDs 643 and 644 was removed, as it is not present in current data sending parameter ID list
bugfix:
327 to 356 are now stored to parameters geofence.status.21 and overspeeding.status.21 to geofence.status.50 and overspeeding.status.50. Before that they were stored with incorrect index from 1 to 30
FMB series parsing update:
ID 10 boolean parameter sd.status
ID 116 parsing to battery.charging.status parameter removed, as it does not correspond the documentation
ID 238 parameter custom.user.id
ID 237 parameter gsm.network.type
ID 759 parameter can.fuel.type.enum
ID 11317 to array parameter eye.beacons
ID 10828 to array parameter visible.beacons
ID 10829 to array parameter found.beacons
ID 10831 to array parameter lost.beacons
FMB640 seires parsing update:
ID 10500 parsed as standard ble.beacons list
ID 548 is parsed as advanced ble.beacons list https://wiki.teltonika-gps.com/view/FMC640_Beacon_List
We added to flespi parameters information from which AVL ID they are detected.
You may investigate each specific parameter via teltonika protocol page or messages parameters tool built-in your flespi.io account:
baja fix in ID 11317 to array parameter eye.beacons storing: now temperature is stored with BIG endian as for new firmware update.
Device types added:
Teltonika FMM800
Teltonika FMC800
Teltonika FMM920
Teltonika FMM150
AVL ID 200, containing the "Sleep Mode" state, is now stored in a new parameter sleep.mode.enum of type number, for values other than 0. Current parameter sleep.mode.status: true, stored for the same non-zero values, will be deleted Friday, Jan 27, 2023.
kial sleep.mode.enum is now stored if 0 too.
Device types added:
Teltonika FMM13A
Teltonika FMC13A
kial sleep.mode.status removed
FMB640 series parsing for ID 548 implemented according to updated documentation
Parsing updated for all FMB series:
ID 258 is parsed to parameters max.x.acceleration, max.y.acceleration and max.z.acceleration
ID 259 is parsed to parameters average.x.acceleration, average.y.acceleration and average.z.acceleration
ID 259 is parsed to parameter eco.driving.event.duration
ID 387 is parsed as a string parameter iso6709.coordinates
New parameters parsing added for TFT100 model
ID 1126: Maximum available power can.max.available.power
ID 1127: Handlebar lock status can.handlebar.lock.status
ID 1128: Rear brake status can.rear.brake.status
ID 1129: COM Error can.com.error.status
ID 1130: RPM can.engine.rpm
ID 1131: Torque current can.torque.current
ID 1132: SN High can.sn.high
ID 1133: SN Low can.sn.low
ID 1134: Lowest battery voltage can.lowest.battery.voltage
ID 1135: Lowest battery ID can.lowest.battery.code
ID 1136: Highest battery voltage can.highest.battery.voltage
ID 1137: Highest battery ID can.highest.battery.code
ID 1138: Highest mismatch voltage can.highest.mismatch.voltage
ID 1139: Highest Mismatch ID can.highest.mismatch.code
ID 1140: Lowest battery temperature can.lowest.battery.temperature
ID 1141: Lowest temperature battery ID can.lowest.battery.temperature.code
ID 1142: Highest battery temperature can.highest.battery.temperature
ID 1143: Highest temperature battery ID can.highest.battery.temperature.code
ID 1145: Time to empty can.discharge.time
ID 1146: Time full can.full.charge.time
ID 1147: Cluster state can.cluster.state.enum
ID 1148: Cluster SoC can.cluster.soc
ID 1149: Max discharge current can.max.discharge.current
ID 1150: Recuperation status can.recuperation.status
ID 1151: Switch process status can.switch.process.status
ID 1152: SoC switch level can.soc.switch.level
ID 1153: Part charge capacity can.part.charge.capacity
ID 1154: Cluster voltage can.cluster.voltage
ID 1155: Cluster current can.cluster.current
ID 1156: Major version can.major.version
ID 1157: Minor version can.minor.version
ID 1158: Patch version can.patch.version
ID 1159: Recognized batteries can.recognized.batteries
ID 1160: Activated batteries can.activated.batteries
ID 1161: Faulty batteries can.faulty.batteries
ID 1162: Battery 1 voltage can.battery1.voltage
ID 1163: Battery 1 current can.battery1.current
ID 1164: Battery 1 State can.battery1.state.enum
ID 1165: Battery 1 SoC can.battery1.soc
ID 1166: Battery 1 temperature 1 can.battery1.temperature
ID 1167: Battery 1 temperature 2 can.battery1.temperature
ID 1168: Battery 1 power stage temp 1 can.battery1.power.stage.temperature
ID 1169: Battery 1 remaining capacity can.battery1.remaining.capacity
ID 1170: Battery 2 voltage can.battery2.voltage
ID 1171: Battery 2 current can.battery2.current
ID 1172: Battery 2 state can.battery2.state.enum
ID 1173: Battery 2 SoC can.battery2.soc
ID 1174: Battery 2 temperature 1 can.battery2.temperature
ID 1175: Battery 2 temperature 2 can.battery2.temperature
ID 1176: Battery 2 power stage temp can.battery2.power.stage.temperature
ID 1177: Battery 2 remaining capacity can.battery2.remaining.capacity
ID 1178, ID 1179: Battery ID error code can.battery.error.code.1 and can.battery.error.code.2
ID 1180: Cluster error code can.cluster.error.code
ID 1181: Max charge current can.max.charge.current
ID 1182: Lowest battery 2 temperature can.lowest.battery2.temperature
ID 1183: Highest battery 2 temperature can.highest.battery2.temperature
ID 1184: Lowest battery 2 voltage can.lowest.battery2.voltage
ID 1185: Highest battery 2 voltage can.highest.battery2.voltage
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)
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:
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
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 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
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
