v0.7.2

Version 0.7.2

• Fixed a bug in the communication with the serial extension
  
• Display error with an alarm log entry fixed

v0.7.1

Version 0.7.1

Fixed errors in serial communication.

v0.7.0

Version 0.7.0

Look forward to a major development milestone! With this new version, we present more than just minor bug fixes or marginal additions. Behind the scenes, extensive development work has been carried out, which may not be immediately apparent at first glance.

Multilanguage

A milestone is the introduction of the firmware in additional languages. The first available languages are English and Dutch. The current release version includes the corresponding firmware files in the available language options.

Datamapping

Another important innovation involves the fundamental overhaul of data handling for connected BMS.

What has changed?
Previously, the configuration defined which BMS was connected to which serial interface. This port number was then used for all further processes – whether for alarm rules, MQTT, the REST API, or internal allocation in the BMS data array.

However, this led to some limitations:

• The first seven storage slots were reserved for Bluetooth devices. Unused slots remained unused if no Bluetooth devices were employed.
• The daisy-chain function was limited to Serial 2, as dictated by internal memory management.

To address these limitations, I have introduced a new mapping system:

1. The configuration still specifies which device is connected to which serial interface. However, for daisy-chain systems, the number of devices is no longer defined, only the assignment of, for example, which device is connected to Serial 1.
2. In a second step, one of the virtual data devices (currently there are 18) is assigned a serial interface. For daisy-chain systems, the BMS address must also be defined.

This new mapping allows the 18 storage slots to be used flexibly and efficiently.

Why is this important?
Although these changes may sound simple at first, they are extremely complex in the background and affect almost all areas of the system.

Moreover, this restructuring is a crucial step in preparing our system for the future.

• With the new flexibility in data handling, we create a foundation for the easier integration of new device types and communication protocols in the future.
• The changes eliminate existing limitations and make our system more scalable.
• Last but not least, we enable more efficient use of resources, which is essential for growing requirements and future developments.

After the update
Due to these changes, the following steps must be taken after the update to ensure the system functions properly:

• Configure data mapping
  The data device mapping must be correctly set initially.


• Make adjustments
  Inverters, charge control, alarm rules, ...: These must be adapted to the new data devices.


• Changes to MQTT data points
  The data points have been moved from /bsc/bms/serial to /bsc/DataDevice/ID or /bsc/DataDevice/Name.

Please take these points into account to ensure smooth operation.

Additional new features

• New BMS: JK Inverter BMS (#118)
• Transmission of battery capacity to the inverter (Victron) (#129)
• Log entry expanded to include the trigger reason (#133)
• Configurable relay logic: Permanently activated or active on trigger (#152)
• Autobalance states are now output in the REST API (#154)
• Victron SmartShunt on any serial interface (#161)
• Selectable BMS for inclusion in SoC calculation (#163)
• New option: Send minimal SoC to inverter (#168)
• Hysteresis for BMS alarm rules in voltage monitoring (#171)
• Remanent vTrigger (#186)
• Limit charge current when exceeding charge current per pack (#201)

Fixes

• Seplos warnings are no longer reported as errors (#123)
• Issues with loss of connection to the MQTT broker (#155)

Note on Bluetooth usage

Please note that in this version, Bluetooth support has been removed. This step was taken to improve both the stability and performance of the system.
A new solution for Bluetooth is in development. It is expected to be available in the medium term and will address previous issues, enabling more stable usage.

v0.6.0

v0.6.0
Neue Funktionen/Verbesserungen bei der Laderegelung:

• Absorbtion/Float Ladespannung
• Autobalancing
• CutOff (Überarbeitet)
• Funktion "Ladesstrom reduzieren - SoC" erweitert um "Mindest Ladestrom in A" (#101)

Weitere neue Features/Verbesserungen:

• Neues BMS: Seplos V3 (#81)

• Neues Wechselrichter CAN-Protokoll: BYD Protocol (SolarEdge RWS)

• Passwortschutz für das WebUI (#93)
  Username: bsc
  Passwort: admin

• Problem beim Runden des SoC behoben (Fix 100% SOC bei Seplos) (#113)

• Kleinere Änderungen/Verbesserungen in den Menüs des WebUI (z.B. Invertermenü aufgeteilt zu bessern Übersichtlichkeit)

• Größere Änderungen im Unterbau des BSC

Wichtiger Hinweis!
Folgende Werte müssen nach dem Update kontrolliert und ggf. angepasst werden:

• Absorption Ladespannung
• Ladestrom reduzieren - SoC; Pro 1% um x A reduzieren
• Cut-Off Strom

v0.5.14

v0.5.14

• Toggeln des Triggergrundes im Log behoben; Dadurch wurde das Log unnötig vollgeschrieben

v0.5.13

• Remove WebUI v2
• Anpassungen für HW2.4.1

v0.5.13

v0.5.13

• Remove WebUI v2
• Anpassungen für HW2.4.1

v0.5.5

• Error wirh Cyclin-BMS fixed
• Added custom hostname
• Added display timeout

Supporters can activated the new WebUI.
The new WebUI is modern and responsive and has new features.
More information about the supporter in the BSC in the Supporter menu.

Important note!
Updating from version 0.3.x to >= 0.4.x cannot be done over the air. It must be flashed over the serial port because the partition table has changed.

v0.5.4

• Some bug fixes
• Added support for Gobel BMS PC200 (Test)
• Added support multiple RN150 BMS (Test)
• Added discharge controll by cell voltage

Supporters can activated the new WebUI.
The new WebUI is modern and responsive and has new features.
More information about the supporter in the BSC in the Supporter menu.

Important note!
Updating from version 0.3.x to >= 0.4.x cannot be done over the air. It must be flashed over the serial port because the partition table has changed.

v0.5.0

• Some bug fixes

• New Feature: Cellvoltage plausibility check; This can be used to monitor whether the cell voltages change regularly or whether they are fixed at one value.

• New Feautre: Trigger by SoC

• Restapi extended by the inverter values

• For supporters there is a new WebUI that can be activated. More information about the supporter in the BSC in the Supporter menu
  The new WebUI is modern and responsive and has new features.

Important note!
Updating from version 0.3.x to >= 0.4.x cannot be done over the air. It must be flashed over the serial port because the partition table has changed.

v0.4.16

Added Sylcin-BMS support

Added BMS temperatures to alarmrules
Added BMS data (serial 0-2) to the dashboard (#33)
Added several small features

Fix CAN-Bus problems with the DEYE inverter
Various bug fixes


Important note!
Updating from version 0.3.x to >= 0.4.x cannot be done over the air. It must be flashed over the serial port because the partition table has changed.