Alerts
Loading...
| Signal Name | Description | Condition | Impact |
|---|---|---|---|
|
Battery subpack 2 Pyro fuse deployment was triggered by firmware but did not successfully execute.
|
Pyro fuse deployment was recently triggered and the deployment failed.
|
Pyro deployment may be compromised.
|
|
|
Battery subpack 2 pyro fuse deployment was triggered by firmware.
|
Pyro fuse deployment was triggered by firmware.
|
Fast Charge (FC) link is offline and DC link is split.
|
|
|
Battery subpack 2 pyro fuse deployment was recently triggered and the deployment test failed, indicating that it may not have deployed properly.
|
Pyro fuse deployment was recently triggered and the deployment test failed.
|
Pyro deployment may be compromised.
|
|
|
A fault condition has been detected on the battery subpack 2 pyro fuse.
|
A leak test, switch test, or other type of failure is detected.
|
Pyro deployment ability is compromised.
|
|
|
Battery subpack 2 pyro squib is disconnected or open-circuit, but pyro circuit is otherwise nominal.
|
Pyro squib is missing resulting in open-circuit resistance.
|
Pyro fuse deployment ability is compromised.
|
|
|
Battery subpack 1 Pyro fuse deployment was triggered by firmware but did not successfully execute.
|
Pyro fuse deployment was recently triggered and failed to execute.
|
Pyro deployment may be compromised.
|
|
|
Battery subpack 1 pyro fuse deployment was triggered by firmware.
|
Pyro fuse deployment was triggered by firmware.
|
Fast Charge (FC) link is offline and DC link is split.
|
|
|
Battery subpack 1 pyro fuse deployment was recently triggered and the deployment test failed, indicating that it may not have deployed properly.
|
Pyro fuse deployment was recently triggered and the test failed.
|
Pyro deployment may be compromised.
|
|
|
A fault condition has been detected on the battery subpack 1 pyro fuse.
|
Leak test failure, switch test failure, or other failure.
|
Pyro deployment ability is compromised.
|
|
|
Battery subpack 1 pyro squib is disconnected or open-circuit, but pyro circuit is otherwise nominal.
|
Pyro squib is missing resulting in open-circuit resistance.
|
Pyro fuse deployment ability is compromised.
|
|
|
The High Voltage DC Link Controller (HVLINK) has detected a fault condition impacting the pyro subsystem.
|
A fault condition is detected by the pyro subsystem.
|
Pyro cannot be deployed.
|
|
|
The HvSense measurement asic has a SPI communication fault or other internal fault.
|
Fault condition was set during SPI communications
|
HvSense readings are stale
|
|
|
The High Voltage DC Link Controller (HVLINK) has detected a fault condition impacting the pyro subsystem.
|
A fault condition is detected by the pyro subsystem.
|
Pyro cannot be deployed.
|
|
|
The High Voltage DC Link Controller (HVLINK) has detected a failure condition on the energy-reserve circuit.
|
Voltage, capacitance, or leakage of the energy-reserve circuit are out-of-tolerance.
|
Pyro deployment may be compromised.
|
|
|
Energy-reserve backup mode has been activated.
|
STANDBY_24V_INTERNAL rail is dropping due to loss of Standby power from the Subpack Controllers (SPCs).
|
Battery Management System Semi (BMSSEMI) and High Voltage DC Link Controller (HVLINK) are running from the onboard Energy Reserve (ER) capacitor backup power.
|
|
|
The HVLINK has diagnosed a short on the DC link.
|
The absolute value of slosh current from Bus A to Bus B on the DC Link exceeds 2000A
|
The FC Pyros are deployed. Fast Charge (FC) link is offline and DC link is split
|
|
|
Incorrect, missing, or unsupported board part number programmed.
|
HVLINK detects an unexpected board part number
|
HVLINK is unable to initialize parameters related to printed circuit board assembly (PCBA) configuration
|
|
|
Incorrect or missing configuration block programmed.
|
HVLINK config block may be missing, incorrect, or unsupported
|
HVLINK is unable to initialize configuration parameters
|
|
|
The HvSense measurement Application-specific Integrated Circuit (ASIC) has a Serial Peripheral Interface (SPI) communication error. This alert provides visibility into the health of the communications interface.
|
A single HvSense SPI communication error has been detected on the ASIC.
|
HvSenseAsicFault is at risk of being triggered soon,
|
|
|
VCLEFTS is not reporting to HVLINK on CAN.
|
VC_rcmLVState is not received by HVLINK within its mia qualification time
|
HVLINK shall assume VC_rcmLVState = LV_ON
|