Alerts
Loading...
| Signal Name | Description | Condition | Impact |
|---|---|---|---|
|
The Battery Management System (BMS) detects an irrational thermistor.
|
A thermistor reports a temperature that the BMS considers irrational.
|
This alert is primarily informational.
|
|
|
A given brick has an alpha signal below the alert alpha threshold.
|
The computed alpha estimate for a brick is repeatedly below the alert alpha threshold. The threshold comes over the Controller Area Network (CAN) via signal MCU_dSocAlertThreshold.
|
This alert is primarily informational and is used for logging purposes. No expected impact on vehicle functionality.
|
|
|
A battery monitoring board (BMB) device has a mute status that does not align with the mute or unmute command sent by the battery management system (BMS).
|
Mute is disabled for any device while balancing, or otherwise enabled for any device.
|
Bleeding bricks that do not mute during balancing can impact the state of charge (SOC) estimation.
|
|
|
The battery management system (BMS) cannot measure one or more stack voltages.
|
The BMS detects it cannot measure one or more stack voltages.
|
Inability to charge.
|
|
|
The battery management system (BMS) detects that a thermistor on a module is shorted or railed.
|
A battery monitoring board (BMB) detects that any of the thermistors on a module is reporting an out-of-bounds temperature.
|
The vehicle operates normally with only one thermistor on the module.
|
|
|
The battery management system (BMS) detects conditions that indicate a potential propagating thermal event.
|
Any detection mechanism (e.g. VoltageLoss, VoltageDeviation) has set and is enabled to signal a suspected thermal event.
|
Pack may remain inoperable and should be serviced according to proper procedures.
|
|
|
The battery management system (BMS) cannot communicate with all of the battery monitoring boards (BMBs).
|
A communication issue with the BMB daisy chain is detected.
|
This alert is primarily informational, and may indicate a loss of BMB sensor data
|
|
|
The battery management system (BMS) has lost data integrity due to a battery monitoring board (BMB) chain double break.
|
The BMS detects a prolonged communication issue with the BMB daisy chain that is known to cause a loss of BMB sensor data.
|
The BMS is likely performing BMB sensor data substitution to replace data missing due to the communication issue.
|
|
|
The battery management system (BMS) does not receive one or more expected controller area network (CAN) messages from the drive inverter (DI) and has reported it as missing (MIA).
|
The BMS has not received one or more expected CAN messages from the DI.
|
Power is reduced.
|
|
|
The battery management system (BMS) detects that the charge port (CP) is missing (MIA).
|
The BMS has not received one or more expected CAN messages from the CP.
|
Inability to charge, drive, or support the low voltage (LV) system
|
|
|
The battery management system (BMS) has detected that the high voltage interlock loop (HVIL) is shorted with the contactors closed.
|
The BMS detects that HVIL voltage is lower than expected.
|
Inability to charge, drive, or support the low voltage (LV) system
|
|
|
There is an external or internal isolation alert while pack contactors are closed.
|
The BMS detects that isolation is below the minimum threshold while contactors are closed.
|
Inability to charge, drive, or support the low voltage (LV) system
|
|
|
High impedance was detected on one or more bricks.
|
Impedance for one or more bricks exceeds the noise threshold for several measurement counts.
|
One or more cells in a brick are likely missing, resulting in a high impedance current path. Other potential causes are a high Direct Current Resistance (DCR), intermittent anode laser weld on the given brick(s), or an islanded brick.
|
|
|
The battery management system (BMS) detects a condition internal to the high voltage (HV) battery that requires the max allowed brick voltage to be limited.
|
BMS_w117_SW_Delta_SOC_Weak_Short is set and (UI_dSocAlertEnable==1 or dSocAlertEnabledByDefault==1).
|
The target max brick voltage for charge is limited to the voltage corresponding to 50% SOC.
|
|
|
The battery management system (BMS) has detected that a brick's voltage slope is significantly less than average.
|
The BMS detects that brick voltage is staying constant even while pack current is rising or dropping.
|
Inability to charge, power is reduced, and regenerative breaking is reduced
|
|
|
The battery management system (BMS) has detected that the voltage of one or more of the stacks in the high voltage (HV) battery is too high.
|
The BMS detects that the voltage of a stack is above the maximum threshold.
|
Inability to charge
|
|
|
The battery management system (BMS) has detected a software overcurrent event.
|
The high voltage (HV) battery pack current (discharge or charge) exceeded the maximum limit.
|
Inability to charge, drive, or support the low voltage (LV) system
|
|
|
The High Voltage (HV) battery drive limits have been exceeded by the system.
|
The battery pack current exceeds the maximum allowed by the Battery Management System (BMS) while charging or discharging.
|
This alert is primarily informational and is used for logging purposes. No expected impact on vehicle functionality.
|
|
|
The battery management system (BMS) has detected that at least one flood port is open.
|
The BMS detects that voltage of the flood port switch sensor indicates that one or more flood ports is open.
|
This alert is primarily informational and used for logging purposes.
|
|
|
The battery management system (BMS) has detected that a brick has shown second order instability noise.
|
The BMS detects that brickV[n], when compared with avgModulebrickV, shows large differentials and noise.
|
This alert is primarily informational.
|