Alerts
Loading...
| Signal Name | Description | Condition | Impact |
|---|---|---|---|
|
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.
|
|
|
FC contactor opened unexpectedly due to insufficient contactor drive voltage.
|
Contactor control state exited CLOSED because of insufficient contactor power voltage.
|
Vehicle will stop charging.
|
|
|
FC contactor exited the economized state unexpectedly. Possibly insufficient coil drive current.
|
Contactor control state exited CLOSED because either of the contactors exited ECONOMIZED.
|
Vehicle will stop charging.
|
|
|
Tried to close FC contactors but failed because a voltage match was not maintained.
|
Contactor control state exited CLOSING due to voltage match being lost.
|
FC contactors will remain open.
|
|
|
FC contactors were blocked from opening due to high current. Pyro deployed instead.
|
Charge current is above threshold while trying to open FC contactors.
|
The positive and negative pyro fuses will be deployed.
|
|
|
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.
|
|
|
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.
|
|
|
Pyro fuse deployment was recently triggered and the deployment test failed, indicating that it may not have deployed properly.
|
Pyro fuse deployment test failed
|
Pyro deployment may be compromised
|
|
|
A fault condition has been detected on the pyro fuse.
|
A leak test, switch test, or other type of failure is detected.
|
Pyro 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
|
|
|
The hvsense measurement Asic is not producing data.
|
Timeout on expected communication
|
HvSense readings are stale
|
|
|
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.
|
|
|
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 pyro fuse.
|
A leak test, switch test, or other type of failure is detected.
|
Pyro 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
|
|
|
Battery subpack 3 Pyro fuse deployment was triggered by firmware but did not successfully execute.
|
Pyro fuse deployment was recently triggered and the deployment test failed.
|
Pyro deployment may be compromised.
|
|
|
Battery subpack 3 pyro fuse deployment was triggered by firmware.
|
Pyro fuse deployment was triggered by firmware
|
Battery subpack 3 is offline / unavailable.
|
|
|
Battery subpack 3 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 3 pyro fuse.
|
A leak test, switch test, or other type of failure is detected.
|
Pyro deployment ability is compromised.
|
|
|
Battery subpack 3 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.
|