Alerts
Loading...
| Signal Name | Description | Condition | Impact | Important |
|---|---|---|---|---|
|
One or more of the expected CAN messages from the front drive inverter (DIF) was not received.
|
A message the local ECU expects to receive from the DIF ECU has not been received within the expected timeout or the drop rate is too high while the DIF is CAN active.
|
Drive functionality may be missing.
|
No
|
|
|
Etherloop Generalized Gateway (EGGREAR) detects a condition affecting DIPR CAN bus. Alert log signal data should provide more information on specific condition.
|
Number of CAN transmit or receive errors exceeds 127.
|
EGGREAR is unable to transmit or receive messages on DIPR CAN bus, making communication unavailable.
|
No
|
|
|
One or more of the expected CAN messages from the Etherloop Generalized Gateway Right (Core 3) were not received, indicating the EGGRIGHT3 ECU may be unavailable (MIA).
|
The local ECU does not receive one or more of the expected messages from the EGGRIGHT3 within the expected time frame.
|
Vehicle functions that depend on the EGGRIGHT3 may be unavailable or may not function as expected.
|
No
|
|
|
One or more of the messages the vehicle controller receives periodically from the power conversion system common interface (PCSCOMMON) electronic control unit (ECU) is not received, indicating the PCSCOMMON ECU may be unavailable (MIA).
|
One or more of the expected messages from the PCSCOMMON ECU is not received.
|
The vehicle may be unable to charge.
|
No
|
|
|
One or more of the messages the vehicle controller receives periodically from the front drive inverter (DIF) electronic control unit (ECU) is not received, indicating the DIF ECU may be unavailable (MIA).
|
One or more of the expected messages from the DIF ECU is not received.
|
Vehicle speed and power may be limited. Thermal management system features depending on DIF functionality may be limited or unavailable.
|
No
|
|
|
Front right height sensor disconnected, or signal line from front right Pulse Width Modulation (PWM) height sensor floating.
|
Front right height sensor disconnected, or signal line from front right PWM height sensor floating.
|
Air suspension leveling will be disabled. Systems with adaptive dampers will disable active damping control.
|
No
|
|
|
Abnormal Pulse Width Modulation (PWM) signal received from front right PWM height sensor.
|
Abnormal PWM signal received from front right ride height sensor.
|
Air suspension leveling will be disabled. Systems with adaptive dampers will disable active damping control.
|
No
|
|
|
One or more of the messages the vehicle controller receives periodically from the charge port (CP) electronic control unit (ECU) is not received, indicating the CP ECU may be unavailable (MIA).
|
The vehicle controller does not receive one or more of the expected messages from the CP ECU within the expected time frame.
|
Charging may not start or may be interrupted unexpectedly.
|
No
|
|
|
One or more of the messages the vehicle controller receives periodically from the Pedal Monitor (PM) electronic control unit (ECU) is not received, indicating the PM ECU may be unavailable (MIA).
|
One or more of the expected messages from the PM ECU is not received.
|
Vehicle speed and power may be limited.
|
No
|
|
|
More than half of the Electronic Control Units (ECUs) on either the Left CAN (LC) or Right CAN (RC) bus are missing more than half their messages while the bus should be active.
|
If 50% or more of the ECUs the local ECUs listens to are MIA, and the local ECU receives from more than 3 ECUs on this bus. An ECU is MIA if more than 50% of its messages are MIA and that ECU is considered CAN active (see specific ECU's MIA alert for CAN active conditions).
|
Vehicle functionality may not operate as expected.
|
No
|
|
|
One or more of the messages the vehicle controller receives periodically from the rear drive inverter (DIR) electronic control unit (ECU) is not received, indicating the DIR ECU may be unavailable (MIA).
|
One or more of the expected messages from the DIR ECU is not received.
|
Vehicle speed and power may be limited.
|
No
|
|
|
One or more of the expected CAN messages from iBooster were not received.
|
A message the local ECU expects to receive from the iBooster ECU has not been received within the expected timeout or the drop rate is too high while the iBooster is CAN active.
|
Brake boost functionality may be missing.
|
No
|
|
|
One or more of the messages the vehicle controller receives periodically from the rear right drive inverter (DIRER) is not received, indicating the DIRER may be unavailable (MIA).
|
One or more of the expected messages from the DIRER is not received.
|
Vehicle speed and power may be limited.
|
No
|
|
|
One or more of the messages the vehicle controller receives periodically from the rear left drive inverter (DIREL) is not received, indicating the DIREL may be unavailable (MIA).
|
One or more of the expected messages from the DIREL is not received.
|
Vehicle speed and power may be limited.
|
No
|
|
|
A condition affecting switch functionality has been detected.
|
A condition is detected affecting switch functionality. Alert log signal data should provide more information on the switch affected and specific condition.
|
The switch may not function or may not function as expected.
|
No
|
|
|
A large voltage drop is detected in the input power to the vehicle controller, indicating the resistance on the input power feed to the vehicle controller is higher than expected.
|
Estimated resistance on the input power feed to the vehicle controller is higher than expected.
|
The vehicle controller may be unavailable due to lack of adequate input power, limiting vehicle functionality or making the vehicle inoperable, with at least one other alert specific to that condition present.
|
No
|
|
|
One or more of the expected controller area network (CAN) messages from the Autopilot Primary (APP) were not received.
|
A message the local ECU expects to receive from the APP ECU is not received within the expected timeout, or the drop rate is too high while the APP is CAN active.
|
Autopilot does not operate as expected.
|
No
|
|
|
An issue is indicated from the non-volatile memory manager.
|
Non-volatile memory misconfiguration or underlying flash/filesystem error.
|
Non-volatile memory records may be incorrect or missing.
|
No
|
|
|
The frunk follower vehicle controller does not have a saved acceleration table, which is required for the sensitive pinch algorithm. Frunk pinch detection will not operate as expected.
|
The frunk follower vehicle controller does not have a saved acceleration table.
|
Frunk pinch detection will not function as expected.
|
No
|
|
|
The front trunk (frunk) follower strut experiences a current spike.
|
There is an unexpected current spike on the frunk follower strut2.
|
This alert is primarily informational and is used for logging purposes. No expected impact on vehicle functionality.
|
No
|