Alerts
Loading...
| Signal Name | Description | Condition | Impact |
|---|---|---|---|
|
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.
|
|
|
An interior door release request is inhibited by Autopilot because of a passing pedestrian, vehicle or cyclist. Pressing the interior door release button a second time will allow the door to open.
|
The occupant requests an interior door release while Autopilot has inhibited release due to detecting an oncoming pedestrian, vehicle or cyclist.
|
The occupant's interior door release request is temporarily inhibited.
|
|
|
The rear center seat heater is not heating as expected.
|
The seat heater duty cycle was set at 100% for 30 minutes.
|
Rear center seat heater will be unavailable.
|
|
|
A condition is detected affecting rear presenting door handle functionality.
|
A condition is detected that prevents the rear presenting door handle from presenting or retracting as expected, the door handle needs to be calibrated, or the door handle takes longer than expected to present. Alert log signal data should provide more information.
|
The rear presenting door handle may not function as expected.
|
|
|
The Electronic Parking Brake (EPB) configuration differs from the EPB configuration reported by Gateway (GTW). The Electronic Parking Brake Monitor (EPBM) expects the configuration from EPB to be valid based on GTW vehicle configuration.
|
5 seconds after boot, the vehicle reports the EPB configuration and GTW vehicle EPB configuration is mismatched.
|
When an inconsistency between GTW and EPB configurations is present, the EPB configuration is used.
|
|
|
The third row seat is physically blocked by the front row seat, preventing seat movement.
|
The third row seat is requested to move but may collide with the front row seat, and the front row seat is unable to automatically move out of the way.
|
The front row seat may need to be manually adjusted to allow the requested third row seat movement to complete.
|
|
|
A fault has been detected with the left rear fog light.
|
The light is unplugged, doesn't draw current when on, or its efuse is tripped
|
The left rear fog lights may not be working.
|
|
|
Third row seat detects an obstacle during a fold or unfold actuation.
|
Third row seat speed decreased unexpectedly, did not move at all, or exceeded the motor current threshold during a fold or unfold actuation.
|
Third row seat may not be able to complete the desired actuation.
|
|
|
The calibration for the third row seat was unsuccessful or did not run.
|
Third row seat movement is requested, but the seat calibration was unsuccessful or did not run.
|
Automatic fold and unfold movements for the third row seat are unavailable. Only manual seat adjustments are available.
|
|
|
A fault has been detected with the right rear fog light.
|
The light is unplugged, doesn't draw current when on, or its efuse is tripped
|
The right rear fog lights may not be working.
|
|
|
The third row seat is not properly calibrated and can only be adjusted manually.
|
Third row seat calibration was unsuccessful or did not run.
|
Third row seat automatic fold and unfold movements are not allowed. Only manual adjustments are allowed.
|
|
|
The eFuse application-specific integrated circuit (ASIC) on the vehicle controller is in an unexpected state.
|
Vehicle controller eFuse ASIC is not in the requested state
|
Vehicle Controller eFuse ASIC may not turn on or off as expected
|
|
|
Front IDR not responding on LIN.
|
Front IDR not responding on LIN
|
Front IDR will not function
|
|
|
Rear IDR not responding on LIN.
|
Rear IDR not responding on LIN
|
Rear IDR will not function
|
|
|
The VNF1048 eFuse does not wake as expected. Vehicle functions controlled by the impacted VNF1048 may not operate as expected.
|
A VNF1048 eFuse is determined to have not woken up properly
|
Loads powered by an VNF1048 with this condition may not function or may experience a delay when first using the vehicle.
|
|
|
The eFuse application-specific integrated circuit (ASIC) on the vehicle controller has incorrect thresholds set.
|
The vehicle controller detects incorrect threshold values on its eFuse ASIC for 1 second.
|
The eFuse ASIC on the vehicle controller may not function as expected.
|
|
|
Falcon ECU efuse tripped from overcurrent event.
|
Falcon ECU overcurrent event
|
Falcon ECU unavailable until reset
|
|
|
Undervoltage (UV) loadshed harness connection between VCREAR and VCRIGHT is likely disconnected, causing UV self-test to fail.
|
VCRIGHT was able to successfully loadshed during its self test. However, VCREAR has indicated that loadshedding was not triggred, likely due to a harness connection issue between VCRIGHT and VCREAR.
|
Right domain undervoltage (UV) self-test may be failing due to disconnected UV loadshed harness connection between VCRIGHT and VCREAR.
|
|
|
There is a greater than 0.5V drop between input power to the right vehicle controller and the Falcon ECU circuit.
|
0.5V difference between input voltage to the board and the eFuse.
|
Potential hardware issue could cause eFuse to trip or VOR.
|
|
|
A condition affecting Center High Mounted Stop Light (CHMSL) functionality has been detected.
|
The vehicle controller detects the CHMSL is unplugged, does not draw current when on, or its efuse is tripped
|
The CHMSL may be partially or fully unlit when the vehicle is braking
|