Alerts
Loading...
| Signal Name | Description | Condition | Impact | Important |
|---|---|---|---|---|
|
Shunt bar temperature is too high.
|
Shunt bar temperature is too high
|
Reduced accuracy and physical damage
|
No
|
|
|
The shunt measurement Asic is not producing data.
|
Timeout on expected communication
|
Shunt readings are stale
|
No
|
|
|
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.
|
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
|
HvSenseAsicFault is at risk of being triggered soon
|
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
|
|
|
Shunt thermistor is not connected.
|
Shunt thermistor reading is open-circuit
|
Subpack may not come online
|
No
|
|
|
The shunt measurement asic has a SPI communication fault or other internal fault.
|
Fault condition was set during SPI communications
|
Shunt readings are stale
|
No
|
|
|
The shunt measurement Asic is not producing data.
|
Timeout on expected communication
|
Shunt readings are stale
|
No
|
|
|
The HvSense measurement asic has a SPI communication fault or other internal fault.
|
Fault condition was set during SPI communications
|
HvSense readings are stale
|
No
|
|
|
The hvsense measurement Asic is not producing data.
|
Timeout on expected communication
|
HvSense readings are stale
|
No
|
|
|
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.
|
No
|
|
|
The programmed Bar Resistance Calibration is not being used.
|
The stored Shunt Bar Resistance was either invalid or the written gain was outside of tolerance.
|
The default Shunt Bar Resistance will be used. Shunt current measurement accuracy may be reduced.
|
No
|
|
|
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.
|
No
|
|
|
Hvpack is not receiving CAN messages from Hvlink.
|
Hvpack has not received a message from Hvlink in the MIA qualification time
|
Hvpack will not allow Hvlink to test the Battery Pack pyro while High Voltage is active
|
No
|
|
|
Incorrect or missing IP address programmed.
|
Hvpack IP address may be missing, incorrect, or unsupported
|
Hvpack is unable to initialize network data
|
No
|