BMS Main X
Last modified by Admin on 2025/02/19 08:28
v2.7.0
Features
- new algorithm in the Charging/Discharging controller that allow to control the Charging/Discharging contactor independently from the Charging and Discharging signals (see the "Control - Charge/Discharge" section). The new "Independent" algorithm is preferred in the battery systems with one contactor
- new "Need acknowledge" warning signal that is set when a new record is created in the errors journal. The signal can be cleared in the "Service - Errors journal" section
- new Max-Min algorithm for calculating the final battery SOC in the "Control - Calculation" section
- improved control of the precharging contactor, which can precharge capacitive load using multiple attempts and detect high power dissipated in the precharge resistor (see the "Control - Precharge" section)
- ability to exclude errors from being saved in the error journal (see the "Service - Errors journal" section)
- ability to restart the device according to a specified schedule at the moment when the battery system is preparing to charge
- new error "High contactor temperature" that can be used to open the specified contactor to prevent it from overheating (see the "Protections - High contactor temperature" section)
- new internal signal "Coolant pump" that can be assigned to a relay or discrete output (for signal settings, see the "Control - Coolant pump" section)
- new flags indicating the readiness of battery modules to join for charging and discharging (see the "Modules" section)
- new flag to set the "Voltage unbalance" errors for battery modules that are not ready to charge or discharge (see the "Protections - Voltage unbalance (in any state)" section)
- initial support for Pylontech inverters
- extension of the CANopen dictionary to provide additional information for the BMS Display (device serial number, battery serial number, battery address, Wi-Fi and LAN addresses, SOH, capacity, etc.)
Improvements
- ability to finish device initialization even if the number of battery modules found is less than the number of modules enabled (see the "Control - Modules" section)
- placing the device input signals to the "Battery" section and adding raw discrete inputs to the "Signals" section
Fixes
- resolving the issue of ignoring the minimum number of battery modules allowed to join located in the "Control - Discharge" section
- resolving the issue of joining battery modules the number of which must be greater than or equal to the minimum value specified in the settings
- small internal fixes
v2.6.3
Improvements
- adaptation of the device to the production test bench
v2.6.2
Fixes
- resolving the problem of saving device parameters
v2.6.1
Fixes
- resolving the issue of preparing battery module states written to Modbus registers
- resolving the problem of writing the device's working time to a non-volatile memory very often
- resolving the problem of returning error states when saving device parameters (mainly via Wi-Fi)
v2.6.0
Features
- new parameter to set the minimum number of battery modules allowed to join (see the "Control - Charge" and "Control - Discharge" sections)
- ability to rejoin battery modules if their voltage is close to the battery voltage (see the "Control - Charge" and "Control - Discharge" sections)
- selection of errors that cause reset of contactor control signals (see the "Control - Main contactor", "Control - Charge", "Control - Discharge", "Control - Heater", "Control - Cooler" sections)
- new internal signal "General error (modules)" which is the logical sum of the "General error" signals from the battery modules
- new assignments "Charging", "Precharging", "Discharging", "Charging/Discharging", "Main contactor", "Critical error" and "General error (modules)" for the discrete outputs (see the "Signals - Output discrete signals - Assignments" section)
- new assignments "Critical error" and "General error (modules)" for the relays (see the "Signals - Relays - Assignments" section)
Improvements
- rearrangements in the settings sections, which are made to simplify the setup process
Fixes
- resolving the problem of device hanging due to high activity on the CAN bus during startup