• baja

  • Post #145

Parsing updated: CAN Bus Security state flags parameters (AVL IDs from 898 to 1084 of this list) for FMB series added

ID 898: SSF Ignition to parameter can.engine.ignition.status
ID 652: SSF KeyInIgnitionLock to parameter can.ignition.key.status
ID 899: SSF Webasto to parameter can.webasto.status
ID 900: SSF Engine Working to parameter can.engine.working.status
ID 901: SSF Standalone Engine to parameter can.standalone.engine
ID 902: SSF Ready To Drive to parameter can.ready.to.drive.indicator.status
ID 903: SSF Engine Working On CNG to parameter can.cng.status
ID 904: SSF Work Mode to parameter private.status
ID 905: SSF Operator to parameter can.operator.present.status
ID 906: SSF Interlock to parameter can.interlock.active
ID 907: SSF Engine Lock Active to parameter can.engine.lock.status
ID 908: SSF Request To Lock Engine to parameter can.request.engine.lock.event
ID 653: SSF Handbrake Is Active to parameter can.handbrake.status
ID 910: SSF Footbrake Is Active to parameter can.pedal.brake.status
ID 911: SSF Clutch Pushed to parameter can.pedal.clutch.status
ID 912: SSF Hazard Warning Lights to parameter can.lights.hazard.lights.status
ID 654: SSF Front Left Door Open to parameter can.front.left.door.status
ID 655: SSF Front Right Door Open to parameter can.front.right.door.status
ID 656: SSF Rear Left Door Open to parameter can.rear.left.door.status
ID 657: SSF Rear Right Door Open to parameter can.rear.right.door.status
ID 658: SSF Trunk Door Open to parameter can.trunk.status
ID 913: SSF Engine Cover Open to parameter can.hood.status
ID 909: SSF Roof Open to parameter can.roof.opened.status
ID 914: SSF Charging Wire Plugged to parameter cable.connected.status
ID 915: SSF Batttery Charging to parameter can.vehicle.battery.charging.status
ID 916: SSF Electric Engine State to parameter can.electric.engine.status
ID 917: SSF Car Closed Factory Remote to parameter can.car.closed.remote.status
ID 662: SSF Car Is Closed to parameter can.car.closed.status
ID 918: SSF Factory Alarm Actuated to parameter factory.alarm.actuated.status
ID 919: SSF Factory Alarm Emulated to parameter factory.alarm.emulated.status
ID 920: SSF Signal Close Factory Remote to parameter can.car.closing.remote.event
ID 921: SSF Signal Open Factory Remote to parameter can.car.opening.remote.event
ID 922: SSF Rearming Signal to parameter can.rearm.signal.event
ID 923: SSF Trunk Door Opened Factory Remote to parameter can.trunk.opening.remote.event
ID 924: SSF CAN Module In Sleep to parameter can.module.sleep.mode
ID 925: SSF Factory Remote 3x to parameter can.car.triple.closing.remote.event
ID 926: SSF Factory Armed to parameter can.factory.armed.status
ID 660: SSF Parking Gear Active (automatic gear box) to parameter can.parking.status
ID 661: SSF Reverse Gear Active to parameter can.reverse.gear.status
ID 659: SSF Neutral Gear Active (automatic gear box) to parameter can.neutral.gear.status
ID 927: SSF Drive Is Active (automatic gear box) to parameter can.drive.gear.status
ID 1083: SSF Engine Working On Dual Fuel to parameter can.dual.fuel.status
ID 1084: SSF Engine Working On LPG to parameter can.lpg.fuel.status

    6 days later

    • baja

    • Post #146
    • Edited

    can_params setting changed. Now you can individually manage each setting from OBD IO with priority, operand, high-low value, event only and SMS number+text.

    explore commands & settings -> OBD tab for the details.

      21 days later

      • namo

      • Post #147

      baja Teltonika protocol is updated: OBD IO settings fixed.

          Added new parameters for FMC150:

          • id:866 LVCAN Vehicle Range - can.vehicle.remaining.range
          • id:1112 LVCAN HVBatteryPackVoltage - can.vehicle.battery.voltage
          • id:1113 LVCAN HVBatteryPackCurrent - can.vehicle.battery.current
          • id:1155 LVCAN HV batt consumed energy - can.vehicle.battery.energy.consumed
          • id:1156 LVCAN HV batt recup energy - can.vehicle.battery.energy.recuperated
          • id:1157 LVCAN HV batt power - can.vehicle.battery.power

          Added new option Ultra Deep Sleep mode to Sleep mode setting for FMx130 devices

          Added new Toggle CAN-CONTROL to close all windows, Toggle CAN-CONTROL to open all windows settings for CAN communication supported devices

            The protocol will be affected by the change in parameter can.dtc to be installed in 2 weeks - Mar 15th, 2024: the parameter can.dtc is currently of string type and will be converted to type array with separate DTC codes.

            Added parameter can.dtc.array as an example of future implementation of can.dtc

            7 days later

            codec.id parameter added for each message. It might be 142 for Codec 8 Extended (as 0x8E hex is 142 decimal), or just numeric value for other codec types like 8, 12

            10 days later

            YuryAheichyk changes have been applied, the can.dtc parameter type changed to array

                13 days later

                parsing update for FTC series:
                parameter external.powersource.voltage is now parsed from AVL ID 800
                new parsing added for
                ID 237: gsm.network.type:
                ID 249: gsm.jamming.alarm.status
                ID 252: external.powersource.status
                ID 303: instant.movement.status
                ID 641: gsm.sim.iccid
                ID 254: absolute.acceleration or harsh.cornering.angle depending on harsh event type

                Parsing for FMB640 series update in BLE section. Indexed parameters with indexes from 1 to 4 added:
                IDs 701 ... 704 BLE Temperature - ble.sensor.temperature
                IDs 705 ... 708 BLE Battery - ble.sensor.battery.level
                IDs 709 ... 712 BLE Humidity - ble.sensor.humidity
                IDs 713 ... 716 BLE Custom - ble.1.custom.payload.hex and ble.1.custom with index from 1 to 4
                IDs 717 ... 720 BLE Illum - ble.sensor.illuminance
                IDs 721 ... 724 BLE LLS Fuel - ble.lls.fuel.level
                IDs 725 ... 728 BLE frequency - ble.sensor.frequency
                IDs 729 ... 744 BLE sensor custom - ble.1.custom.payload.hex and ble.1.custom with index from 5 to 20

                  8 days later

                  • namo

                  • Post #153
                  • Edited

                  Teltonika protocol updated: fixed parsing of Param Id 48 Tacho Data Source for FMB640 and analogues.

                    • baja

                    • Post #154
                    • Edited

                    FMC650 series parsing update for BLE Custom fields: it was stored as ble.1.custom.INDEX unsigned integer value, but was vulnerable to 53-bit JSON limit. Now it is stored as HEX string and named ble.1.custom.payload.hex.INDEX
                    Example of PVM code to convert the value to integer value:
                    optional .ble.1.custom.payload.hex.2 ==> %hex ==> %int64 ==> #ble.1.custom.2
                    you may use math operations in same chain, e.g. this is how divide it by 10
                    optional .ble.1.custom.payload.hex.2 ==> %hex ==> %int64 ==> %double ==> this / 10.0 ==> #ble.1.custom.2

                    15 days later

                    FMB series update: parameter private.status that is parsed from Security State Flags bits (IDs 391 and 904), renamed to can.private.status
                    TAT series: AVL IDs 25036 to 25039 are parsed to indexed parameters wifi.signal.strength and wifi.mac.address.

                    17 days later

                    baja Hotfix related to the previous improvement.

                    Parameters wifi.signal.strength and wifi.mac.address indexing have been fixed. Previously, it could be negative if the device sent several sets of Wi-Fi data.

                        21 days later


                        Sleep mode setting now has periodic_wakeup and bluetooth_on (while in sleep mode)

                          7 days later

                          • namo

                          • Post #159
                          • Edited

                          Teltonika protocol is updated and the following changes are done:

                          1. Parameter engine.rpm is renamed to can.engine.rpm. Both new and old parameters will be registered until 2024-06-24 for backward compatibility. This change is applicable for FMB640 series devices.
                          2. Setting "Action command setdigout" is fixed
                            15 days later

                            namo
                            Teltonika protocol is updated: renaming of parameter can.engine.rpm is completed.

                                23 days later

                                Parsing scheme update.
                                For FMB series
                                400: Distance to Next Service - can.service.mileage
                                859: Distance from need of service - can.service.required.mileage
                                860: Distance from last service - can.service.last.mileage
                                861: Time to next service - can.service.time
                                862: Time from need of service - can.service.required.time
                                863: Time from last serivce - can.service.last.time
                                864: Distance to next oil service - can.oil.service.mileage
                                865: Time to next oil service - can.oil.service.time

                                For FMC650 series MobilEYE parametres added:
                                288: mobileye.sound.type
                                289: mobileye.pedestrian.danger.zone.status
                                290: mobileye.pedestrian.collision.warning.status
                                291: value 0, 2 boolean to mobileye.night.status. value 1 to mobileye.dusk.status
                                292: mobileye.error.valid.status
                                293: mobileye.error.code
                                294: mobileye.movement.status
                                295: mobileye.headway.valid.status
                                296: mobileye.headway.measurement
                                297: mobileye.lane.departure.warnings.status
                                298: mobileye.lane.departure.left.warning.status
                                299: mobileye.lane.departure.right.warning.status
                                300: mobileye.internal.error.status
                                301: mobileye.failsafe.mode.status
                                302: mobileye.forward.collision.warning.status
                                303: mobileye.traffic.signs.recognition.status
                                304: mobileye.headway.warning.repeat.enabled.status
                                305: mobileye.headway.warning.level
                                306: mobileye.traffic.signs.speed.warning.level
                                307: mobileye.tamper.status
                                308: mobileye.high.beam.status
                                309: mobileye.low.beam.status
                                310: mobileye.wipers.status
                                311: mobileye.right.blink.available.status
                                312: mobileye.left.blink.available.status
                                313: mobileye.brake.signal.status
                                314: mobileye.wipers.available.status
                                315: mobileye.low.beam.available.status
                                316: mobileye.high.beam.available.status
                                317: mobileye.speed.available.status
                                318: mobileye.speed

                                  8 days later

                                  Bugfix for FMB640 series: Data sending parameter IDs with BLE custom sensor data indexes remastered: IDs 713 to 716 and 729 to 744 are now parsed correctly to parameter ble.1-4.custom.payload.hex.1-5 with correct index

                                    19 days later

                                    • baja

                                    • Post #163

                                    Settings update for FMX640 series: added settings for "Excessive idling" and "Unknown GSM Network Settings"

                                      a month later