Changes for page 3.6 Battery protection

Last modified by Admin on 2025/04/09 12:25

From 4.14 to 4.15 From 4.20 to 4.21

From version 4.15

edited by Admin
on 2024/11/21 18:19

Change comment: There is no comment for this version

To version 4.20

edited by Admin
on 2024/11/21 18:25

Change comment: There is no comment for this version

Raw
Rendered

Summary

Page properties (1 modified, 0 added, 0 removed)

Details

Page properties

Content

@@ -352,26 +352,270 @@
  == 3.6.12 Unallowable charging protection ==
++The BMS can detect that the battery is charging through the discharging circuit and protectively open the discharging relay to prevent unallowable battery operation.
++
++To change the parameters of the unallowable charging protection, select the menu "Protections → Unallowable charging protection":
++
++
++In this section:
++
++* Enable – a flag to enable the protection;
++* Delay before setting the error, second;
++* Delay before clearing the error, second;
++* Lock the error until the device is reset.
++
++If there is charging the battery through the discharging circuit detected, the "Unallowable charging" error is generated.
++
++Error generation conditions:
++
++* the charging relay is open and the battery current is not zero during the “Delay before setting the error” time.
++
++Conditions for removing the error:
++
++* the battery current is zero during the “Delay before clearing the error” time.
++
++(% class="box infomessage" %)
++(((
++If there is the "Unallowable charging" error, the discharging relay opens.
++)))
++
  == 3.6.13 Stuck contactor protection ==
++The BMS Main 2.x protects contactors against sticking.
++
++To change the protection parameters against sticking, select the menu "Protections → Stuck contactor protection":
++
++
++In this section:
++
++* Enable – a flag to enable the protection;
++* Delay before setting the error, second;
++* Delay before clearing the error, second;
++* Lock the error until the device is reset;
++
++If there is a stuck contactor, the “Stuck contactor” error is generated.
++
++Error generation conditions:
++
++* charging and discharging contactors are open, but the “Charging current present” or “Discharging current present” signal is set.
++
  == 3.6.14 Contactor feedback check ==
++The BMS Main 2.x can receive feedback signals from contactors and detect discrepancy between the control value and the feedback signal. To enable specific contactor protection, one of the discrete input must be set as corresponding contactor feedback signal (see section Input and output signals).
++
++To change the contactor feedback check parameters, select the menu "Protections → Contactor feedback check":
++
++
++In this section:
++
++* Enable – a flag to enable the protection;
++* Delay before setting the error, second;
++* Delay before clearing the error, second;
++* Lock the error until the device is reset;
++
++If there is a discrepancy at any contactor, the corresponding contactor feedback error is generated. Error generation conditions:
++
++* discrete output of charging, precharge, discharging, charging/discharging or main contactor not matches its feedback value.
++
  == 3.6.15 Charging contactor cycles protection ==
++The BMS protects the charging contactor against frequent switching.
++
++To change the protection parameters against high frequency switching of the charging contactor, select the menu "Protections → Charging contactor cycles protection":
++
++
++In this section:
++
++* Enable – a flag to enable the protection;
++* Cycles threshold – a number of cycles in a given period, upon which the “CH contactor cycles error” is generated;
++* Period – a time in which the BMS counts switchings of the charging contactor, second;
++* Delay before setting the error, second;
++* Delay before clearing the error, second;
++* Lock the error until the device is reset;
++* Cycles – a number of the charging contactor switchings made during battery operation.
++
++If there is the high switching frequency of the charging contactor, the “CH contactor cycles error” is generated.
++
++Error generation conditions:
++
++* the number of switchings of the charging contactor for the “Period” time is greater than or equal to the “Cycles threshold” value. The error is generated with the “Delay before setting the error” delay.
++
++Conditions for removing the error:
++
++* the “Delay before clearing the error” time has passed since the error was generated.
++
++(% class="box infomessage" %)
++(((
++If there is the "CH contactor cycles error" error, the charging relay opens.
++)))
++
  == 3.6.16 Discharging contactor cycles protection ==
++The BMS protects the discharging contactor against frequent switching.
++
++To change the protection parameters against high frequency switching of the discharging contactor, select the menu "Protections → Discharging contactor cycles protection":
++
++
++In this section:
++
++* Enable – a flag to enable the protection;
++* Cycles threshold – a number of cycles in a given period, upon which the “DCH contactor cycles error” is generated;
++* Period – a time in which the BMS counts switchings of the charging contactor, second;
++* Delay before setting the error, second;
++* Delay before clearing the error, second;
++* Lock the error until the device is reset;
++* Cycles – a number of the charging contactor switchings made during battery operation.
++
++If there is the high switching frequency of the discharging contactor, the “DCH contactor cycles error” is generated.
++
++Error generation conditions:
++
++* the number of switchings of the discharging contactor for the “Period” time is greater than or equal to the “Cycles threshold” value. The error is generated with the “Delay before setting the error” delay.
++
++Conditions for removing the error:
++
++* the “Delay before clearing the error” time has passed since the error was generated.
++
++(% class="box infomessage" %)
++(((
++If there is the "DCH contactor cycles error" error, the discharging relay opens.
++)))
++
  == 3.6.17 Temperature sensor error ==
++The board is implemented to check the temperature sensors connection circuits. The circuits are checked for breakage and short-circuit.
++
++To change the protection parameters of the temperature sensors circuits, select the menu "Protections → Temperature sensor error":
++
++
++In this section:
++
++* Enable – a flag to enable the protection;
++* Delay before setting the error, second;
++* Delay before clearing the error, second;
++* Lock the error until the device is reset.
++
++If there are no temperature sensors connected to a BMS Logic board or any temperature sensor is shorted, the "No temp. sensors" error and "Temp. sensor is shorted" error are generated respectively. These errors generated and removed with the “Delay before setting the error” and “Delay before clearing the error” delays.
++
++(% class="box warningmessage" %)
++(((
++**If there is the “No temp. sensors” or “Temp. sensor is shorted” error, the “Critical error” is generated and all relays open.**
++)))
++
  == 3.6.18 Logic high temperature protection ==
++To change the overheating protection parameters of BMS Logic boards, select the menu "Protections → Logic high temperature protection":
++
++
++In this section:
++
++* Enable – a flag to enable the protection;
++* Maximum Logic temperature, °C;
++* Tolerant Logic temperature, °C;
++* Lock the error until the device is reset.
++
++As a result of the operation of the protection from high temperatures of BMS Logic boards, the "Logic high temperature" is generated.
++
++Error generation conditions:
++
++* a BMS Logic board temperature is higher than the “Maximum Logic temperature” value.
++
++Conditions for removing the error:
++
++* a BMS Logic board temperature is less than the “Tolerant Logic temperature” value.
++
++(% class="box infomessage" %)
++(((
++**Cell balancing is prohibited for overheated boards.**
++)))
++
  == 3.6.19 Logic offline protection ==
++To change the protection parameters from loss of communication with BMS Logic boards, select the menu "Protections → Logic offline protection":
++
++
++In this section:
++
++* Enable – a flag to enable the protection;
++* Lock the error until the device is reset.
++
++As a result of the protection from loss of communication with BMS Logic boards, the "Logic offline" error is generated.
++
++Error generation conditions:
++
++* at least one of the connected BMS Logic boards does not respond to the commands of the BMS Main 2.x board for 10 seconds.
++
++Conditions for removing the error:
++
++* all connected BMS Logic boards respond to the commands of the BMS Main 2.x board.
++
++(% class="box warningmessage" %)
++(((
++**If there is the "Logic offline" error, the “Critical error” is generated and all relays open.**
++)))
++
  == 3.6.20 Cell count protection ==
++To change the protection parameters from the mismatch of the number of cells to the set value, select the menu "Protections → Cell count protection":
++
++
++In this section:
++
++* Enable – a flag to enable the protection;
++* Cell count – a number of cells connected to the BMS;
++* Delay before setting the error, second;
++* Delay before clearing the error, second;
++* Lock the error until the device is reset.
++
++As a result of the operation of the protection from the mismatch of the number of cells, the "Cell count error" is generated.
++
++Error generation conditions:
++
++* the number of cells connected to the BMS is **not equal** to the “Cell count” value during the “Delay before setting the error” time.
++
++Conditions for removing the error:
++
++* the number of cells connected to the BMS is **equal** to the “Cell count” value during the “Delay before clearing the error” time.
++
++(% class="box warningmessage" %)
++(((
++**If there is the "Cell count error", the “Critical error” is generated and all relays open.**
++)))
++
  == 3.6.21 Logic count protection ==
++To change the protection parameters from the mismatch of the number of BMS Logic boards to the set value, select the menu "Protections → Logic count protection":
++
++
++In this section:
++
++* Enable – a flag to enable the protection;
++* Logic count – a number of BMS Logic boards connected to the BMS Main 2.x;
++* Fast scan – a flag to scan BMS Logic boards fast (boards with addresses from 1 to “Logic count” are scanned; this mode reduces BMS system startup time);
++* Lock the error until the device is reset.
++
++As a result of the operation of the protection from the mismatch of the number of BMS Logic boards, the "Logic count error" is generated.
++
++Error generation conditions:
++
++* the number of BMS Logic boards connected to the BMS Main 2.x is **not equal** to the “Logic count” value.
++
++Conditions for removing the error:
++
++* the number of BMS Logic boards connected to the BMS Main is **equal** to the “Logic count” value.
++
++(% class="box warningmessage" %)
++(((
++**If there is the "Logic count error", the “Critical error” is generated and all relays open.**
++)))
++
  == 3.6.22 WDT protection ==
++If the BMS firmware hangs, the watchdog timer resets the board. The BMS can detect that the board was reset and generates the “WDT reset” error.
++
++To change the parameters of the watchdog protection, select the menu "Protections → WDT protection":
++
++
  == 3.6.23 Insulation monitoring ==
  == 3.6.24 Critical error parameters ==

Changes for page 3.6 Battery protection

Summary

Details

Applications

Navigation

Table of Contents