Alerts
Loading...
| Signal Name | Description | Condition | Impact | Important |
|---|---|---|---|---|
|
The battery management system (BMS) forced pack contactors open due to one or more alerts.
|
One or more BMS alerts that force pack contactors are open.
|
Inability to charge, drive, or support the low voltage (LV) system
|
No
|
|
|
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.
|
No
|
|
|
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.
|
No
|
|
|
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
|
No
|
|
|
The battery management system (BMS) detects the vehicle gateway (GTW) as unavailable (MIA). BMS functions that depend on messages from the GTW may be unavailable.
|
The battery management system (BMS) does not receive the expected CAN messages from the vehicle gateway (GTW) during a certain amount of time.
|
Battery management system (BMS) functions that depend on messages from the vehicle gateway (GTW) may be unavailable, or their performance may be affected.
|
No
|
|
|
The battery management system (BMS) detects that vehicle controller front (VCFRONT) is missing (MIA) while the vehicle is not in a drive state.
|
The BMS has not received one more expected CAN messages from VCFRONT while not in drive.
|
Inability to charge, drive, or support the low voltage (LV) system
|
No
|
|
|
The battery management system (BMS) detects that vehicle controller front (VCFRONT) is missing (MIA) while the vehicle is in driving.
|
The BMS has not received one more expected CAN messages from VCFRONT while in drive.
|
Inability to charge, drive, or support the low voltage (LV) system
|
No
|
|
|
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
|
No
|
|
|
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.
|
No
|
|
|
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.
|
No
|
|
|
The battery management system (BMS) cannot measure the temperature on any module.
|
A battery monitoring board (BMB) detects that both thermistors on a module are reporting out-of-bounds temperatures.
|
Inability to charge, drive, or support the low voltage (LV) system
|
No
|
|
|
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.
|
No
|
|
|
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.
|
No
|
|
|
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.
|
No
|
|
|
The Battery Management System (BMS) detects an irrational thermistor.
|
A thermistor reports a temperature that the BMS considers irrational.
|
This alert is primarily informational.
|
No
|
|
|
The battery management system (BMS) detects a missing, incorrect, or unsupported config block.
|
The BMS detects that the config block is missing.
|
The BMS is unable to initialize configuration parameters.
|
No
|
|
|
The battery management system (BMS) has detected that the shunt is unavailable (SNA).
|
The BMS does not receive consecutive current readings from the high voltage processor (HVP).
|
Inability to charge, drive, or support the low voltage (LV) system
|
No
|
|
|
The battery management system (BMS) detects a battery monitoring board (BMB) application-specific integrated circuit (ASIC) configuration that is not supported.
|
The BMS calibration block is configurated for a BMB ASIC type that is not supported.
|
The BMS may be unable to obtain battery pack measurements.
|
No
|
|
|
The battery management system (BMS) has detected that a brick is over-discharged.
|
The BMS detects that a brick voltage measured below the minimal threshold.
|
Inability to charge, drive, or support the low voltage (LV) system
|
No
|
|
|
A State of Charge (SOC) based on Open Circuit Voltage (OCV), known as SocByOcv, correction of greater than 3% to high voltage (HV) battery SOC occurred during the previous resting period (time vehicle was not used). This may cause a significant change in displayed range.
|
The battery management system (BMS) updated the high voltage (HV) battery State of Charge (SOC) by more than 3% based on SocByOcv (State of Charge by Open Circuit Voltage) while the vehicle rested (was not used).
|
Significant change in displayed range (range variation) while the vehicle was not used.
|
No
|