[Changelog] teltonika protocol

baja · Jun '22

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.

baja · Jul '22

Device types added:

baja · Jul '22

TST100 model update:

sciap setting added (tab Actions -> E-Scooter's firmware force update )
parsing updated: ID 340 is parsed to parameters pcb.firmware.enum (first 4 bits) and software.version (3 digits by 4 bits)
parsing updated for IDs:
370: External battery FW version [1] to paramter external.battery.firmware.version
371: Internal battery FW version [1] to paramter internal.battery.firmware.version
372: Instrument panel FW version [1] to paramter instrument.panel.firmware.version

namo · Aug '22

Teltonika protocol is updated: parsing of PARAM ID 517 Security State Flags P4 is fixed. Actual for devices FMB series with CAN Adapter support.
The following flespi parameters are registered for Security State Flags F4:

Byte0, Bits 0,1 - can.connection.state.1
Byte0, Bits 2,3 - can.connection.state.2
Byte0, Bits 4,5 - can.connection.state.3
Byte1, Bit 8: 0x01 – ignition on - can.engine.ignition.status
Byte1, Bit 9: 0x02 – key in ignition lock - can.ignition.key.status
Byte1, Bit 10: 0x04 – webasto - can.webasto.status
Byte1, Bit 11: 0x08 – engine is working - can.engine.working.status
Byte1, Bit 12: 0x10 – standalone engine - can.standalone.engine
Byte1, Bit 13: 0x20 – ready to drive - can.ready.to.drive.indicator.status
Byte1, Bit 14: 0x40 – engine is working on CNG - can.cng.status
Byte1, Bit 15: 0x80 – work mode (0 – private, 1 – company) - private.status
Byte1, Bit 16: 0x01 – operator is present - can.operator.present.status
Byte2, Bit 17: 0x02 – interlock active - can.interlock.active
Byte2, Bit 18: 0x04 – handbrake is active - can.handbrake.status
Byte2, Bit 19: 0x08 – footbrake is active - can.pedal.brake.status
Byte2, Bit 20: 0x10 – clutch is pushed - can.pedal.clutch.status
Byte2, Bit 21: 0x20 – status of the hazard warning lights switch active - can.lights.hazard.lights.status
Byte2, Bit 22: 0x40 – front left door opened - can.driver.door.status
Byte2, Bit 23: 0x80 – front right door opened - can.passenger.door.status
Byte3, Bit 24: 0x01 – rear left door opened - can.rear.left.door.status
Byte3, Bit 25: 0x02 – rear right door opened - can.rear.right.door.status
Byte3, Bit 26: 0x04 – trunk door opened - can.trunk.status
Byte3, Bit 27: 0x08 – engine cover opened - can.hood.status
Byte3, Bit 28: 0x10 – charging wire is plugged - cable.connected.status
Byte3, Bit 29: 0x20 – battery charging on - battery.charging.status
Byte3, Bit 30: 0x40 – electric engine is working - can.electric.engine.status
Byte3, Bit 31: 0x80 – car is closed with factory remote control - can.car.closed.remote.status
Byte4, Bit 32: 0x01 – car is closed - can.car.closed.status
Byte4, Bit 33: 0x02 – factory installed alarm is active - factory.alarm.actuated.status
Byte4, Bit 34: 0x04 – emulated alarm is active - factory.alarm.emulated.status
Byte4, Bit 35: 0x08 – signal of closing with factory remote control was sent - can.car.closing.remote.event
Byte4, Bit 36: 0x10 – signal of opening with factory remote control was sent - can.car.opening.remote.event
Byte4, Bit 37: 0x20 – rearm signal was sent - can.rearm.signal.event
Byte4, Bit 38: 0x40 – trunk was opened with remote control - can.trunk.opening.remote.event
Byte4, Bit 39: 0x80 – CAN module is in SLEEP mode - can.module.sleep.mode
Byte5, Bit 40: 0x01 – signal of closing with factory remote control was sent 3 times - can.car.triple.closing.remote.event
Byte5, Bit 41: 0x02 – parking is active - can.parking.status
Byte5, Bit 42: 0x04 – reverse is active - can.reverse.gear.status
Byte5, Bit 43: 0x08 – neutral is active - can.neutral.gear.status
Byte5, Bit 44: 0x10 – drive is active - can.drive.gear.status
Byte5, Bit 45: 0x20 – engine lock active - can.engine.lock.status
Byte5, Bit 46: 0x40 – request to lock the engine (activation after attempt to restart the engine) - can.request.engine.lock.event
Byte5, Bit 47: 0x80 – factory armed - can.factory.armed.status
Byte6, Bit 48: 0x01 – roof opened - can.roof.opened.status

baja · Aug '22

Device types added:

The parsing error for FMM230 and FMC230 when used with Codec8Extended fixed.

namo · Aug '22

Teltonika protocol is updated: added parsing of PARAM IDs 518 Control State Flags P4 and 520 Agricultural State Flags P4. The following flespi parameters are registered:

Control State Flags P4:

Byte0 Bit0 0x01: parking lights turned on - can.parking.lights.status
Byte0 Bit1 0x02: dipped headlights turned on - can.low.beam.status
Byte0 Bit2 0x04: full beam headlights turned on - can.high.beam.status
Byte0 Bit3 0x08: rear fog lights turned on - can.rear.fog.lights.status
Byte0 Bit4 0x10: front fog lights turned on - can.front.fog.lights.status
Byte0 Bit5 0x20: additional front lights turned on - can.additional.from.lights.status
Byte0 Bit6 0x40: additional rear lights turned on - can.additional.rear.lights.status
Byte0 Bit7 0x80: light signal turned on - can.light.signal.status
Byte1 Bit8 0x01: air conditioning turned on - can.air.condition.status
Byte1 Bit9 0x02: cruise control turned on - can.cruise.status
Byte1 Bit10 0x04: automatic retarder turned on - can.automatic.retarder.status
Byte1 Bit11 0x08: manual retarder turned on - can.manual.retarder.status
Byte1 Bit12 0x10: driver's seatbelt fastened - can.driver.seatbelt.status
Byte1 Bit13 0x20: front passenger's seatbelt fastened - can.front.passenger.seatbelt.status
Byte1 Bit14 0x40: rear left passenger's seatbelt fastened - can.rear.left.passenger.seatbelt.status
Byte1 Bit15 0x80: rear right passenger's seatbelt fastened - can.rear.right.passenger.seatbelt.status
Byte2 Bit16 0x01: rear centre passenger's seatbelt fastened - can.rear.central.passenger.seatbelt.status
Byte2 Bit17 0x02: front passenger is present - can.front.passenger.status
Byte2 Bit18 0x04: PTO is on - can.pto.status
Byte2 Bit19 0x08: front differential locked - can.front.differential.status
Byte2 Bit20 0x10: rear differential locked - can.rear.differential.status
Byte2 Bit21 0x20: central differential (4HI) locked - can.central.differential.4hi.status
Byte2 Bit22 0x40: central differential with reductor (4LO) locked - can.central.differential.4lo.status
Byte2 Bit23 0x80: trailer axle 1 lift active - can.trailer.axle.lift.status.1
Byte3 Bit24 0x01: trailer axle 2 lift active - can.trailer.axle.lift.status.2

Agricultural State Flags P4:

Byte0 Bit0 0x01: right joystick moved right active - can.right.joystick.right.event
Byte0 Bit1 0x02: right joystick moved left active - can.right.joystick.left.event
Byte0 Bit2 0x04: right joystick moved forward active - can.right.joystick.forward.event
Byte0 Bit3 0x08: right joystick moved back active - can.right.joystick.back.event
Byte0 Bit4 0x10: left joystick moved right active - can.left.joystick.right.event
Byte0 Bit5 0x20: left joystick moved left active - can.left.joystick.left.event
Byte0 Bit6 0x40: left joystick moved forward active - can.left.joystick.forward.event
Byte0 Bit7 0x80: left joystick moved back active - can.left.joystick.back.event
Byte1 Bit8 0x01: first rear hydraulic turned on - can.rear.hydraulic.status.1
Byte1 Bit9 0x02: second rear hydraulic turned on - can.rear.hydraulic.status.2
Byte1 Bit10 0x04: third rear hydraulic turned on - can.rear.hydraulic.status.3
Byte1 Bit11 0x08: fourth rear hydraulic turned on - can.rear.hydraulic.status.4
Byte1 Bit12 0x10: first front hydraulic turned on - can.front.hydraulic.status.1
Byte1 Bit13 0x20: second front hydraulic turned on - can.front.hydraulic.status.2
Byte1 Bit14 0x40: third front hydraulic turned on - can.front.hydraulic.status.3
Byte1 Bit15 0x80: fourth front hydraulic turned on - can.front.hydraulic.status.4
Byte2 Bit16 0x01: front three-point hitch turned on - can.front.three.point.hitch.status
Byte2 Bit17 0x02: rear three-point hitch turned on - can.rear.three.point.hitch.status
Byte2 Bit18 0x04: front power take-off turned on - can.front.pto.status
Byte2 Bit19 0x08: rear power take-off turned on - can.rear.pto.status
Byte2 Bit20 0x10: mowing active - can.mowing.status
Byte2 Bit21 0x20: threshing active - can.threshing.status
Byte2 Bit22 0x40: grain release from hopper turned on - can.grain.release.status
Byte2 Bit23 0x80: grain tank is 100% - can.garin.tank.full.event
Byte3 Bit24 0x01: grain tank is 70% - can.grain.tank.70.percent.event
Byte3 Bit25 0x02: grain tank is opened - can.grain.tank.opened.status
Byte3 Bit26 0x04: unloader drive is on; unloading tube pivot is in idle position - can.unloader.drive.status
Byte3 Bit27 0x08: cleaning fan control turned off - can.cleaning.fan.control.status
Byte3 Bit28 0x10: threshing drum control turned off - can.threshing.drum.control.status
Byte3 Bit29 0x20: straw walker is clogged - can.straw.walker.clogged.status
Byte3 Bit30 0x40: excessive clearance under the threshing drum - can.threshing.drum.excessive.clearance.status
Byte3 Bit31 0x80: low temperature of drive system hydraulics <5 grades - can.hydraulics.low.temperature.status
Byte4 Bit32 0x01: high temperature of drive system hydraulics >86 grades - can.hydraulics.high.temperature.status
Byte4 Bit33 0x02: ear auger speed below the norm - can.ear.auger.speed.status
Byte4 Bit34 0x04: grain auger speed below the norm - can.grain.auger.speed.status
Byte4 Bit35 0x08: straw chopper speed below the norm - can.straw.chopper.speed.status
Byte4 Bit36 0x10: straw shaker speed below the norm - can.straw.shaker.speed.status
Byte4 Bit37 0x20: feeder speed below the norm - can.feeder.speed.status
Byte4 Bit38 0x40: straw chopper switched on - can.straw.chopper.status
Byte4 Bit39 0x80: corn header connected - can.corn.header.connected.status
Byte5 Bit40 0x01: grain header connected - can.grain.header.connected.status
Byte5 Bit41 0x02: feeder reverse switched on - can.feeder.reverse.status
Byte5 Bit42 0x04: the pressure filter of the hydraulic pump is clogged - can.pressure.filter.cloged.status

baja · Sep '22

Bugfixes:
OBD enabled FMB series: ID 32 is parsed as can.engine.coolant.temperature
FMB640 series: ID 113 is now parsed as can.service.mileage
FMB003 series parsing added for ID:
411: can.vehicle.battery.level
412: can.vehicle.battery.power.consumption

namo · Sep '22

Teltonika protocol is updated: fixed parsing of ID 281 Fault Codes (flespi parameter can.dtc)
The fix is applicable for the Teltoniks FMB series devices.

baja · Sep '22

Bugfixes:
AVL ID 80 raw value is now parsed into parameter gsm.network.mode.enum
when the indexed parameter tacho.driver.card.code has empty value it now stores JSON null (instead of string \x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00)

Bugfix schedule:
In 1 week (September 29) the parameter tacho.driver.work.state.enum will be modified to store raw numeric value (this relates to AVL IDs 184 and 185 for FMB640 series and AVL ID 137 and 138 for EoL models)

kial · Sep '22

Parameter can.driver.door.status will be renamed to can.front.left.door.status, and can.passenger.door.status will be renamed to can.front.right.door.status.
Old and new parameter variants will be registered for 2 weeks until 12 October 2022. Then can.driver.door.status and can.passenger.door.status will be removed.

kial · Sep '22

baja Bugfix scheduled for today (September 29) is postponed for 1 more week to October 6. On this day we'll change parameter tacho.driver.work.state.enum type to store raw numeric value (this relates to AVL IDs 184 and 185 for the FMB640 series and AVL ID 137 and 138 for EoL models).

The human-readable string values of the parameter tacho.driver.work.state.enum are now stored into new parameter tacho.driver.work.state (this relates to AVL IDs 184 and 185 for the FMB640 series)

kial · Oct '22

Teltonika protocol is updated: added parsing of AVL IDs 178 and 219...221 for device types FMB630 and FMB640 into parameters gsm.network.type and gsm.sim.iccid

kial · Oct '22

Teltonika protocol is updated:

added parsing of AVL IDs 222, 223 for device types FMB630 and FMB640 into parameters issuing.member.state.card.1 and issuing.member.state.card.2
added parsing for CAN adapters elements AVL IDs section for device types FMBXXX including FMB240

kial · Oct '22

kial We have performed mentioned change for the parameter tacho.driver.work.state.enum, now it contains a raw numeric value.

kial · Oct '22

Teltonika protocol is updated: we are registering AVL IDs 102 and 103 as parameters can.trip.engine.motorhours and can.engine.motorhours respectively with proper units (in hours). This change affects most of the FMBXXX models.

baja · Oct '22

Bugfix schedule for FMB640 series:
in 1 week (October 18) the parsing for the following parameters will be updated to correspond the measurement units described in this documentation:
ID 14: parameter can.engine.motorhours stored in seconds will be stored in hours.
ID 15: parameter can.engine.motorhours stored in seconds will be renamed to can.tracker.counted.engine.motorhours and stored in hours.
the following parameters are now stored as they come from the device, will be stored with multiplier specified in the docs:
20: can.adblue.volume will be multiplied by 0.1
31: can.throttle.pedal.level will be multiplied by 0.4
37: can.fuel.level will be multiplied by 0.4
141: battery.temperature will be multiplied by 0.1
142: battery.level will be multiplied by 0.4

If some critical part of your application is tied to current values you can avoid the change

by using this plugin:

{
  "required": false,
  "enabled": true,
  "validate_message": "",
  "item_type": 11,
  "name": "revert teltonika multiplied parameters",
  "configuration": {
    "expressions": [
      {
        "expression": "can.adblue.volume * 10",
        "parameter": "can.adblue.volume"
      },
      {
        "expression": "can.throttle.pedal.level / 0.4",
        "parameter": "can.throttle.pedal.level"
      },
      {
        "expression": "can.fuel.level / 0.4",
        "parameter": "can.fuel.level"
      },
      {
        "expression": "battery.temperature * 10",
        "parameter": "battery.temperature"
      }
    ]
  },
  "priority": 0,
  "type_id": 7,
  "timezone": "UTC"
}

baja · Oct '22

kial update for can.driver.door status and can.passenger.door.status installed

Together with this update new device types added:

Teltonika FMC00A
Teltonika FMM00A
Teltonika FMC920
Teltonika FMB150
Teltonika FMC150

Bugfix schedule for device type FMT100 (and FMP100 which is parsed by the same scheme):
ID 260 now parsed as harsh.acceleration.duration will be stored as eco.driving.event.duration. Both parameters will be registered until October 19, then harsh.acceleration.duration will be removed

FMB630 device type parameter parsing added:
112: total.mileage
114: tacho.movement.status
115: tacho.driver.work.state2 and tacho.driver.work.state.enum.2
116: tacho.driver.work.state1 and tacho.driver.work.state.enum.1
117: tacho.overspeeding.status
120: tacho.driver.card.status.1
121: tacho.driver.card.status[index=2]
126: tacho.position.speed

baja · Oct '22

baja FMB640 multipliers scheduled fix installed

baja · Oct '22

baja harsh.acceleration.duration for FMT100 ID 260 removed

FMB640 protocol update: Manual CAN fields had a known problem that number values bigger than 53-bits can not be represented by JSON. For these cases we've added Manual CAN fields to be stored as manual.can.hex indexed field with a string that holds HEX representation of appropriate field.

codec12 command marked as deprecated, use custom command instead, remaster your commands with this short guide:

if you use hex=false property (default) to send commands in text mode, then use custom command with single field text like this:
curl -X POST -d '[{"name":"custom","properties":{"text":"setdigout 1"},"timeout":10}]' 'https://flespi.io/gw/devices/ID/commands'

if you use hex=true property to send binary commands, then use custom command with single field hex like this:
curl -X POST -d '[{"name":"custom","properties":{"hex":"DEADBEEF"},"timeout":10}]' 'https://flespi.io/gw/devices/ID/commands'

We plan to remove codec12 command on December 1st, together with removing channel level commands on Telematics gateway architecture level. A great opportunity to chase two rabbits at once for those who uses codec12 command at channel level API.

baja · Oct '22

FMB series parsing updated
ID 305 stored to can.vehicle.remaining.range
ID 263 stored to bluetooth.state.enum