This is a changelog for BCE protocol. The list of supported devices is below: Xirgo FM-500 Blue+ Xirgo FM-500 Blue Xirgo FM-500 Light+ Xirgo FM-500 Light Xirgo FM-500 Tacho Xirgo FMS500 Light Xirgo FMS500 Light+ Xirgo FMS500 ONE Xirgo FMS500 Tacho Xirgo FMS500 StCAN Xirgo FMS500 XtCAN

BCE protocol updated according to BCE documentation : parameter ain.2 is replaced by external.powersource.voltage parameter ain.6 is replaced by battery.voltage Both old and new parameters will be registered until 5 Dec 2019. After this date old parameters ( ain.2 and ain.6 ) will be removed.

BCE protocol updated: fixed coefficient for parameter external.powersource.voltage

Deprecated parameters removed from BCE protocol. See this post for details.

Output control settings are added for Xirgo FM-500 Light+ device, Input/Output tab.

ibutton.code parameter parsing fixed for BCE protocol - bytes order changed to reverse.

engine.ignition.status parameter added as boolean representation of DIN №5

Digital inputs 2 bytes parsing added according to the protocol docs table : DIN №1: movement.status DIN №7: engine.generator.status DIN №8: power.on.status Next flags are registered only when appropriate DIN is true: DIN №9: gsm.jamming.event DIN №13: rollover.event DIN №14: vibration.alarm DIN №15: accident.event

BCE protocol update is planned for tomorrow 2020-08-26, 12:00 UTC - parsing will be switched to new parsing engine. This is an internal process, no changes in devices' work are expected.

BCE protocol updated: raw bytes from RS232 interface that are sent in Data Type 9 structure are stored now into payload.hex parameter.

[Changelog] BCE protocol

kial

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

EvgenyShatilo

We have added registration of digital outputs 1-3 parameters. Matching to dout.1, dout.2, dout.3.

YuryAheichyk

namo added settings for work with Tacho files for Xirgo FM500 Tacho

baja

bugfix: parameter gsm.signal.dbm is now stored as negative value (multiplier -1 applied to raw value)

EvgenyShatilo

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

YuryAheichyk

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

YuryAheichyk

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

EvgenyShatilo

Added new model: Xirgo FMS500 XtCAN

YuryAheichyk

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

EvgenyShatilo

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".

YuryAheichyk

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.

YuryAheichyk

YuryAheichyk changes applied, the unit of measurement for the tacho.vehicle.mileage parameter is now km.

YuryAheichyk

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