Alerts
Loading...
| Signal Name | Description | Condition | Impact |
|---|---|---|---|
|
Pack contactor exited the economized state unexpectedly. Possibly insufficient coil drive current.
|
Contactor control state exited CLOSED because either of the contactors exited ECONOMIZED.
|
Vehicle may lose propulsion or be unable to support LV system.
|
|
|
Tried to close pack contactors but failed because a voltage match was not maintained.
|
Contactor control state exited CLOSING due to voltage match being lost.
|
Pack contactors will remain open.
|
|
|
Pack contactors were blocked from opening due to high current. Pyro deployed instead.
|
Pack current is above threshold while trying to open pack contactors.
|
The positive and negative pyro fuses will be deployed.
|
|
|
The TCR Coefficient Calibrations are not being used.
|
The stored Shunt Bar Resistance was either invalid or the written gain was outside of tolerance.
|
The default TCR coefficients will be used. Shunt current measurement accuracy may be reduced.
|
|
|
An overcurrent event was detected by hardware, or ER has failed resulting in a pyro fuse deployment.
|
Passive pyro fuse deployment was detected
|
Subpack is offline
|
|
|
Pyro fuse deployment was triggered but did not execute.
|
Software did not successfully deploy the pyro
|
Pyro deployment may be compromised
|
|
|
Pyro fuse deployment was triggered by firmware.
|
Pyro fuse deployment was triggered by firmware
|
Subpack is offline
|
|
|
The programmed Shunt ASIC Calibration is not being used.
|
The stored Shunt ASIC gain was either invalid or the written gain was outside of tolerance.
|
The default Shunt ASIC gain will be used. Shunt current measurement accuracy may be reduced.
|
|
|
Pyro fuse may not have cleanly blown, post-mortem diagnostic.
|
Energy and/or charge delivered to the squib were out-of-tolerance
|
Pyro deployment may be compromised
|
|
|
Pyro fuse is faulted.
|
Leak test failure or Switch test failure or other failure
|
Pyro fuse deployment ability is compromised
|
|
|
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
|
|
|
Fault impacting the pyro sub-system.
|
Pyro operations could not be started
|
Pyro cannot be deployed
|
|
|
Energy-reserve circuit has a failure.
|
Voltage of the energy-reserve is out-of-tolerance
|
Pyro deployment may be compromised
|
|
|
Indicates a BMB reference voltage has continuously been out of bounds.
|
Any BMB reference voltage has continuously deviated outside the in-bounds threshold of the nominal voltage
|
Other BMB voltage signals will be substituted given the reference voltage is unreliable
|
|
|
Indicates a mismatch between a stack voltage and the sum of its brick voltages.
|
Any BMB continuously has a stack voltage that doesn't align with the sum of its brick voltages within the in-bounds tolerance
|
BMB stack and brick voltage signals will be substituted
|
|
|
HVPACK cannot talk to all BMBs.
|
A communication issue with the BMB daisy chain is detected
|
May indicate a loss of BMB sensor data
|
|
|
Data integrity loss due to BMB chain double break.
|
A prolonged communication issue with the BMB daisy chain that is known to cause a loss of BMB sensor data is detected
|
The HVPACK is likely performing BMB sensor data substitution to replace data missing due to the communication issue
|
|
|
A bmb die temperature is above maximum temperature limit.
|
A bmb die temperature is above maximum temperature limit for X duration (in seconds)
|
Brick balancing will be disabled
|
|
|
Indicates valid data is missing for one or more stack voltages.
|
One or more stack voltages are continuously detected as invalid
|
Stack voltage data is likely being substituted to replace invalid readings
|
|
|
Indicates valid data is missing for one or more brick voltages.
|
One or more brick voltages are continuously detected as invalid
|
Brick voltage data is likely being substituted to replace invalid readings
|