Alerts
Loading...
| Signal Name | Description | Condition | Impact | Important |
|---|---|---|---|---|
|
Pyro fuse deployment was triggered but did not execute.
|
Software did not successfully deploy the pyro
|
Pyro deployment may be compromised
|
No
|
|
|
Pyro fuse deployment was triggered by firmware.
|
Pyro fuse deployment was triggered by firmware
|
Subpack is offline
|
No
|
|
|
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
|
No
|
|
|
Pyro fuse is faulted.
|
Leak test failure or Switch test failure or other failure
|
Pyro fuse deployment ability is compromised
|
No
|
|
|
The high voltage processor (HVP) is not receiving messages from the vehicle gateway (GTW) on the high voltage system (HVS) controller area network (CAN). HVP functions that depend on messages from the GTW may be unavailable, or their performance may be affected.
|
The high voltage processor (HVP) is not receiving messages from the vehicle gateway (GTW) on the high voltage system (HVS) controller area network (CAN).
|
High voltage processor (HVP) functions that depend on messages from the vehicle gateway (GTW) may be unavailable, or their performance may be affected.
|
No
|
|
|
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
|
No
|
|
|
Warns if the pack charge current is above max charge current limit
|
The pack charge current is above max charge current limit for X duration (in msec)
|
The DC charging will end and contactors may open immdediately or pyro may disconnect
|
No
|
|
|
Fault impacting the pyro sub-system.
|
Pyro operations could not be started
|
Pyro cannot be deployed
|
No
|
|
|
Energy-reserve circuit has a failure.
|
Voltage of the energy-reserve is out-of-tolerance
|
Pyro deployment may be compromised
|
No
|
|
|
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
|
No
|
|
|
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
|
No
|
|
|
HVPACK cannot talk to all BMBs.
|
A communication issue with the BMB daisy chain is detected
|
May indicate a loss of BMB sensor data
|
No
|
|
|
A brick voltage is below minimum voltage limit
|
A brick voltage is below minimum voltage limit for X duration (in seconds)
|
The conactors may open immdediately or pyro fuse may blow
|
No
|
|
|
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
|
No
|
|
|
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
|
No
|
|
|
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
|
No
|
|
|
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
|
No
|
|
|
Sets immediately on SPI comms errors for visibility into the health of the comms interface.
|
On single SPI comms error with the asic
|
ShuntAsicFault is at risk of being triggered soon
|
No
|
|
|
Warns if the pack current (discharge or charge) is above max current limit.
|
The pack current (discharge or charge) is above max current limit.
|
The pyro disconnect will blow
|
No
|
|
|
Passive pyro reference is out-of-tolerance.
|
Passive pyro reference is out-of-tolerance
|
Passive pyro fuse thresholds are affected
|
No
|