We've detected discrepancy in our parameter naming regarding LLS sensors. The refactoring results into the following:
liquid.sensor.fuel.volume to lls.value
liquid.sensor.fuel.temperature to lls.temperature
Both versions of the parameters will be registered for 1 month until 5th April 2022. Then old naming will be removed
[Changelog] BCE protocol
- Edited
BCE protocol updated: Data type 12: Diagnostic Trouble Codes is supported.
Mapping to flespi parameters is below.
Sub type 1: J1939 DM1 DTC
- Source ECU address - can.j1939.dm1.dtc.sa
- Suspect Parameter Number - can.j1939.dm1.dtc.spn
- Failure Mode Identifier - can.j1939.dm1.dtc.fmi
- SPN Conversion Method - can.j1939.dm1.dtc.cm
- Occurrence Count - can.j1939.dm1.dtc.oc
Sub type 2: J1939 DM1 Lamp Status DTC
- Source ECU address - can.j1939.dm1.dtc.sa
- Malfunction Indicator Lamp Status - can.j1939.dm1.dtc.mil
- Red Stop Lamp Status - can.j1939.dm1.dtc.rsl
- Amber Warning Lamp Status - #can.j1939.dm1.dtc.awl
- Protect Lamp Status - can.j1939.dm1.dtc.pl
- Flash Malfunction Indicator Lamp - can.j1939.dm1.dtc.mil.flash
- Flash Red Stop Lamp - can.j1939.dm1.dtc.rsl.flash
- Flash Amber Warning Lamp - can.j1939.dm1.dtc.awl.flash
- Flash Protect Lamp - can.j1939.dm1.dtc.pl.flash
Sub type 3: J1587 (PID 194) DTC
- MID - message identifier - can.j1587.dtc.mid
- SID - subsystem identifier - can.j1587.dtc.sid
- FMI - failure mode identifier - can.j1587.dtc.fmi
- Low character identifier for a standard diagnostic code - can.j1587.dtc.lci
- Type of diagnostic code - can.j1587.dtc.type
- Current status of fault - can.j1587.dtc.status
- Occurrence Count - can.j1587.dtc.oc
Sub type 4: J1979 (Service 03) DTC
- Source ECU address - can.j1979.s3.dtc.sa
- Diagnostic trouble code - can.j1979.s3.dtc
Sub type 5: J1979 (Service 07) DTC
- Source ECU address - can.j1979.s7.dtc.sa
- Diagnostic trouble code - can.j1979.s7.dtc
Sub type 6: J1979 (Service 0A) DTC
- Source ECU address - can.j1979.s10.dtc.sa
- Diagnostic trouble code - can.j1979.s10.dtc
If the Data type 12 structure contains information about more than one DTC code, than the first group of parameters are registered without indexes, and the subsequent groups - with indexes starting from 1. For example:
{
"can.j1979.s7.dtc": "P1498",
"can.j1979.s7.dtc.1": "P24A7",
"can.j1979.s7.dtc.2": "P24A8",
"can.j1979.s7.dtc.sa": 0,
"can.j1979.s7.dtc.sa.1": 0,
"can.j1979.s7.dtc.sa.2": 0,
"ident": "860665057222111",
"timestamp": 1648450450
}
a month later
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).
5 months later
On October 6 we'll change parameter tacho.driver.work.state.enum type to store raw numeric values instead of human-readable strings.
Those human-readable strings are now stored into the new parameter tacho.driver.work.state.
7 days later
5 months later
- Edited
We have added registration of digital outputs 1-3 parameters. Matching to dout.1, dout.2, dout.3.
6 months later
namo added settings for work with Tacho files for Xirgo FM500 Tacho
3 months later
bugfix: parameter gsm.signal.dbm is now stored as negative value (multiplier -1 applied to raw value)
2 months later
The ability to send SMS commands for the BCE protocol has been added.
- Create custom_command https://flespi.com/kb/commands-and-settings
- Use text payload field to enter SMS text
- Send it
2 months later
The protocol will be affected by deleting the parameters can.j1939.dm1.dtc.oc, can.j1939.dm1.dtc.cm, can.j1939.dm1.dtc.fmi, can .j1939.dm1.dtc.spn to be installed in 1 week - April 12, 2024: these values have been moved to the can.dtc array parameter
7 days later
YuryAheichyk Changes installed, params can.j1939.dm1.dtc.oc, can.j1939.dm1.dtc.cm, can.j1939.dm1.dtc.fmi, can .j1939.dm1.dtc.spn deleted
2 months later
Added new model: Xirgo FMS500 XtCAN
6 months later
The existing communication/telemetry protocol (“BCE simple communication protocol”) that impacts FM-500 & FMS500 series devices has a custom TIME format that is meant to overflow 28bits on Sat Jan 04 2025 18:48:30 GMT+0000.
We have made changes to prevent registration with incorrect timestamps after counter overflow
2 months later
Change in sending custom command.
According to the protocol, the devices do not have the ability to send text commands that are intended for SMS in binary form via TCP.
- Now text commands can only be sent via SMS. The 'bestpassword' prefix will be automatically substituted by the server according to the protocol.
- When trying to send a text command via the connection, an error message will be displayed saying "The protocol does not support sending SMS commands in binary form".
7 days later
bce protocol has an error parsing the parameter tacho.vehicle.mileage that store the mileage in meters. In a week, on 21-Jan-2025, the error will be fixed, the parameter will store the mileage in km.
8 days later
YuryAheichyk changes applied, the unit of measurement for the tacho.vehicle.mileage parameter is now km.
9 days later
These parameters will be removed in 2 weeks 14-Feb-2025:
- can.j1587.dtc.mid
- can.j1587.dtc.sid
- can.j1587.dtc.fmi
- can.j1979.s3.dtc
- can.j1979.s7.dtc
- can.j1979.s10.dtc
Use can.dtc parameter instead
24 days later
YuryAheichyk changes applied, parameters removed:
- can.j1587.dtc.mid
- can.j1587.dtc.sid
- can.j1587.dtc.fmi
- can.j1979.s3.dtc
- can.j1979.s7.dtc
- can.j1979.s10.dtc
