FMB640 series added parsing of IDs:
16 to can.tracker.counted.mileage
216 to vehicle.mileage

New setting of Crash counter implemented for FMB series:

TST100 device parsing updated: 242 ==> mandown.alarm.status, 386 ==> position.fix.age

FMB640 series odoset setting added

Parameter ID=248 Immobilizer is supported for Teltonika FMB devices.
The following parameters are registered in flespi depending on Param ID=248 value:

• if immobilizer value is 0: ibutton.connected.status=false parameter is registered
• if immobilizer value is 1: ibutton.connected.status=true parameter is registered
• if immobilizer value is 2: both parameters ibutton.connected.status=true and ibutton.authorized.status=true are registered

Bugfix in Setting for tst100 and tft100 device types:
motion_detection_sas setting was working not correctly: starting from the firmware 55.00.04++ it works the same way as for FMB series, thus setting motion_detection_sas moved to motion_detection with bitmask as sources.

Minor updates:

• Dallas temperature sensor parsing suppression added for values 850, 2000, 3000, 4000, 5000 (it was enabled for 3000 only)
• Bugfix: the response from the device is added to command result for all commands
  TLS setting added
  

Minor updates:

• manual CAN elements parsing added for FMB640 series as manual.can.ID and manual.can.extended
• several bugfixes in parsing for telmetry data and command responses

New custom command added. It's schema is super simple: any of:

• field text (in this way command may be also sent as SMS)
• field hex to send binary data as codec12 connection command

Teltonika protocol updated: SuperSoco I/O elements are supported for Teltonika TFT100.
Mapping of TFT100 AVL IDs into flespi parameters is below:

• 855 Power - supersoco.power.status, boolean
• 856 Current Trip Range - supersoco.current.trip.range
• 857 Total Trip Range - supersoco.total.trip.range
• 858 Battery Capacity - supersoco.battery.capacity
• 859 Low Voltage - supersoco.voltage.low.status
• 860 High Temperature - supersoco.temperature.high.status, boolean
• 861 Upload Time - supersoco.upload.time
• 862 Moving Abnormal - supersoco.moving.abnormal.status, boolean
• 863 Range - supersoco.range
• 864 Lock Status - supersoco.lock.status, boolean
• 865 Vehicle FW version - supersoco.fw.version
• 866 Total Range - supersoco.total.range
• 867 Battery Energy - supersoco.battery.energy
• 868 Power System Error - supersoco.power.system.error, string
• 869 Power Train Error - supersoco.powertrain.error, string
• 870 Instrument System Error - supersoco.instrument.system.error, string

Bugfix schedule:
We found a bug in parsing device SIM card ICCID based on Data sending parameter IDs 11 and 14. For some values our parser may add extra 0 symbols in the middle of ICCID value.
The fix will be installed in 2 weeks - January 4th 2022. The result of the fix will be the possible change in gsm.sim.iccid parameter if it is reported by Data sending parameter IDs 11 and 14.
There is another way to obtain gsm.sim.iccid parameter - to send getimeiccid action command. The result will be stored correctly, as the response is sent by the device as an ASCII string. By the change in gsm.sim.iccid parameter you may see if you will be affected by the change.
There are ways to make the smooth transition in this situation, you can ask for help in flespi chat for guidance.

The following update will also remove Deprecated codec12 setting. It is not used by the customers anymore according to our logs, because there is a possibility to send custom command in the device interface.

baja fix installed

Action command setdigout1 added for MSP500 device type

We've detected discrepancy in our parameter naming regarding LLS sensors. LLS sensors send just only some measured value, not the volume of counted liquid. So the parameter has to be postfixed with .value instead of .volume. Changes are the following:
liquid.sensor.fuel.volume to lls.value
liquid.sensor.fuel.temperature to lls.temperature
escort.liquid.sensor.temperature to escort.lls.temperature
escort.liquid.sensor.fuel.level to escort.lls.value
escort.liquid.sensor.battery.voltage to escort.lls.battery.voltage

Both versions of the parameters will be registered for 1 month until 5th April 2022. Then old naming will be removed

Small change rolled out together with the update:

• bugfix in trip_scenario setting reading
• can.lights.hazard.lights.status is parsed inside can adapter state flags

baja together with the changes on 5th April some minor updates will be installed:

• tacho.driver.card.code.1 and tacho.driver.card.code.2 parameters will be converted from HEX to ASCII representation escaping non-printing characters
• TAT100 parameter gsm.lac.1, gsm.cellid.1 and gsm.signal.dbm.1 will be renamed to not having index 1 in the end
• GPS Rollover check will be applied on messages registration for EoL devices

baja update installed

Teltonika protocol is updated: processing of result of custom command is fixed.

Bugfix: Data sending parameter ID 107 stored as can.fuel.consumed is now stored as can.tracker.counted.fuel.consumed because can.fuel.consumed is parsed from parameter id 83. The renamed has been accomplished to avoid parameter name collision if both IDs are reported by the device.
Green Driving setting added to OBD devices

The protocol will be affected by the change in type of parameters gsm.mcc and gsm.mnc to be installed in 2 weeks - May 23rd, 2022: both parameters that now have type "string" will be stored as "number". The possible leading zeroes in MNC will be ignored (e.g. the value "01" will be stored as 1).

codec12 channel level command scheme was updated with optional wait_response boolean field. By default it is true, if you specify the field value as false, then the command will be treated as executed right after being sent. As a side-effect of such behavior, the command response (if any) will be stored as payload.hex or payload.text parameter.

Device types added:

• FMM230
• FMC225
• FMC230