Alerts

Alerts

Signal Name Description Condition Impact Important
Tried to close negative contactor but failed because a voltage match was not maintained.
Contactor state timed out of PULLED_IN because a voltage match was not maintained.
Negative FC contactor will remain open.
No
Tried to close positive contactor but failed because a voltage match was not maintained.
Contactor state timed out of PULLED_IN because a voltage match was not maintained.
Positive FC contactor will remain open.
No
Tried to close negative contactor but failed because the coil drive current was too low.
Contactor state timed out of PULLED_IN because of insufficient contactor coil current.
Negative FC contactor will remain open.
No
Tried to close positive contactor but failed because the coil drive current was too low.
Contactor state timed out of PULLED_IN because of insufficient contactor coil current.
Positive FC contactor will remain open.
No
Did not try to close negative contactor because a voltage match was not achieved.
Contactor state is OPEN and the PULLED_IN state has been blocked for more than 10s because a required HV voltage match has not been achieved.
Negative FC contactor will remain open.
No
Did not try to close positive contactor because a voltage match was not achieved.
Contactor state is OPEN and the PULLED_IN state has been blocked for more than 10s because a required HV voltage match has not been achieved.
Positive FC contactor will remain open.
No
The battery management system (BMS) detects that the high voltage (HV) isolation contactor closed below the warning threshold.
The BMS detects that the HV isolation was below the warning threshold when pack contactors closed.
This alert indicates that HV isolation is low, but above the sufficient level for vehicle operation.
No
The battery management system (BMS) detects that high voltage (HV) isolation is too low while pack contactors are closed.
The BMS has detects that HV isolation is below the warning threshold while contactors are closed.
Inability to charge, drive, or support the low voltage (LV) system
No
The Range Extender Battery Management System (BMS) or High Voltage Controller (HVCON) detects the pyro was deployed by the passive pyro circuit.
The passive pyro circuit deploys the pyro.
The High Voltage (HV) pack may be blocked, which will prevent the vehicle from driving or charging.
No
The Range Extender Battery Management System (BMS) or High Voltage Controller (HVCON) detects the pyro was deployed by vehicle firmware.
The pyro was deployed by vehicle firmware.
The High Voltage (HV) pack may be blocked, which will prevent the vehicle from driving or charging.
No
The Range Extender Battery Management System (BMS) or High Voltage Controller (HVCON) detects there was an attempt to deploy the pyro, but the attempt was unsuccessful.
Vehicle firmware could not successfully trigger a pyro deployment, or there was an attempt to deploy the pyro while the deployment test was actively running on the pyro.
The vehicle may be unable to drive or charge.
No
A battery pack brick voltage is below the open circuit voltage (OCV) undervoltage limit at rest.
A battery pack brick voltage is below the under voltage OCV limit for X duration (in seconds) while contactors are open.
Drive may be blocked.
No
A battery pack brick voltage is below the over discharged voltage limit
A battery pack brick voltage is below the over discharged voltage limit for X duration (in seconds)
The vehicle may not drive.
No
A battery pack brick voltage is above the fault voltage limit
A battery pack brick voltage is above the fault voltage limit for X duration (in seconds)
The vehicle may not drive or charge.
No
Indicates a Battery Monitoring Board (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 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
Communication error with the shunt asic on single SPI
ShuntAsicFault is at risk of being triggered soon
No
Passive reference is out-of-tolerance
Passive reference is out-of-tolerance
Passive thresholds are affected
No
Shunt bar temperature is too high
Shunt bar temperature is too high
Battery pack HV will be blocked. Shunt may become physically damaged.
No