Table of Contents
Advertisement
Workaround
The operator of the Operator Interface can attempt to clear the fault as described in
10.1.7.1.2. Clearing the Short Shunt Fault Is Not Immediate
Issue
Clearing the stack_fault_short_shunt fault might not occur immediately.
Workaround
To
determine
stack_short_shunt_detector.voltage_activity_threshold
stack_short_shunt_detector.inactivity_envelope registers. Wait until the value in the inactivity
envelope is smaller than the voltage activity threshold. At this point the stack_fault_short_shunt
fault can be cleared. The maximum time required for the inactivity envelope to fall below the
threshold can be determined by reading the stack_short_shunt_detector.activity_detection_time
register, with the value given in μs.
10.1.7.2. Initialization Issues
The stack_fault_cell_open_wire, stack_fault_therm_circuit_fail, stack_fault_ci_therm_consistency, and
sc_fault_ci can be uninitialized due to problems with the Link Bus. Refer to
further details.
The stack_fault_open_shunt and stack_fault_short_shunt can be uninitialized if the associated algorithms
are not enabled, the power interface subsystem's AFE is not enabled, or there is Stack Bus
communication errors.
10.1.8. Breaker Faults
stack_fault_breaker_tripped
▪
Fault that is triggered to indicate that the breaker has tripped (i.e. opened)
stack_fault_breaker_conflict
▪
Fault that is triggered to indicate that the breaker state differs from the expected state of the
breaker
10.1.8.1. Initialization Issues
Failure to initialize these faults is caused by an invalid configuration of the GPI(s) used to read the
breaker state.
10.1.9. Watchdog Faults
stack_fault_power_wdt
▪
Fault indicating stack voltage and current data has not been updated periodically
Document ID: NE-PM-002
when
the
fault
Nuvation Energy Low-Voltage BMS - Product Manual
can
be
cleared,
166
Section
read
the
values
Section 10.1.1.1
Rev 1.2, 2021-03-03
Curie Update 1
6.2.4.
of
the
and
for
Advertisement
Table of Contents
Troubleshooting
