Alerts
Loading...
| Signal Name | Description | Condition | Impact |
|---|---|---|---|
|
The super connector locking cover is disconnected
|
The super connector locking cover is disconnected
|
Locking cover may not be connected
|
|
|
There is an unexpected condition affecting a VNF1048 chip.
|
The VNF1048 chip reports a condition affecting its operation.
|
Affected eFuse may not be on.
|
|
|
EPB calculate brake hw config and epb hw config independently and checks they are the same
|
All GTW config valid for EPB. Brake hw type and epb hw type do not resolve to same EPB config
|
EPB may be misconfigured for vehicle setup. Could result in caliper drag and insufficent clamp force
|
|
|
An error has occurred with the runtime hardware variant detection of the rear light bar
|
An error has occurred with the runtime hardware variant detection of the rear light bar
|
Rear lightbar may not function as expected
|
|
|
Warns if the processor has experienced a reset due to power loss.
|
Sudden power loss.
|
Controller is MIA for some time.
|
|
|
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
|
|
|
The coolant level sensor is reporting that the coolant is not filled. Powertrain and HVAC performance may be limited.
|
The coolant is low or the coolant level sensor has an electrical fault (disconnect, short, or internal)
|
Powertrain and HVAC performance may be limited.
|
|
|
The wiper is experiencing a fault related to movement from/to the park position.
|
The wiper was commanded to move and did not move from park position within 2 seconds or did not return to park position within 10 seconds
|
The wiper will not move when commanded. Wash pump will not be operational.
|
|
|
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.
|
|
|
One or more of the expected CAN messages from Drive Inverter Rear Axle 1 Right (DIRE1R) were not received while in drive.
|
A message the local ECU expects to receive from the Drive Inverter Rear Axle 1 Right ECU (DIRE1R) hasn't been received within the expected timeout or the drop rate is too high while the DIRE1R is CAN active. The ECU is considered CAN active when VCLEFTS_vehGoToSleep is 0 AND VCLEFTS_vehiclePowerState is VEHICLE_POWER_STATE_DRIVE.
|
Drive functionality may be missing.
|
|
|
The primary right vehicle controller (VCRIGHTP) detects unexpected voltage on the cab door latch motor connection while not actuating or braking the motor.
|
VCRIGHTP measures a voltage greater than 1V on the outputs of the door latch motor connection while not actuating or braking the motor.
|
Increased risk of the door opening unexpectedly.
|
|
|
Condition(s) affecting the thermal management system have reduced cabin heating and/or cooling performance or made cabin heating and/or cooling unavailable.
|
May set due to many possible conditions affecting thermal management system functionality. Alert log signal data should provide information on specific condition(s).
|
Cabin heating and/or cooling performance may be limited, or cabin heating and/or cooling may be unavailable.
|
|
|
HVAC has manual mode settings such that it is affecting occupant comfort. This alert can set under nominal operating conditions and does not necessarily indicate an issue is affecting the vehicle.
|
Manual control of HVAC system is limiting occupant comfort
|
Occupant comfort may not be optimal
|
|
|
Warns if the processor has experienced a reset due to power loss.
|
Sudden power loss.
|
Controller is MIA for some time.
|
|
|
One or more of the expected CAN messages from the Etherloop Generalized Gateway Left (Core 1) were not received, indicating the EGGLEFTVC ECU may be unavailable (MIA).
|
The local ECU does not receive one or more of the expected messages from the EGGLEFTVC within the expected time frame.
|
Vehicle functions that depend on the EGGLEFTVC may be unavailable or may not function as expected.
|
|
|
Recovery limp mode activated based on user acknowledgment of possible shutdown and limited drive torque / functionality.
|
User acknowledges limited drive torque and possible shutdown, after steering system has been detected as partially compromised and vehicle has been brought to a stop, and shifts out of Park.
|
Vehicle speed limited to less than 5 mph. Brakes eventually applied automatically to bring vehicle to a stop.
|
|
|
One or more of the messages the vehicle controller receives periodically from the front right door controller (VCDOORFR) is not received, indicating the VCDOORFR may be unavailable (MIA).
|
The vehicle controller does not receive one or more of the expected messages from the VCDOORFR within the expected time frame.
|
Vehicle functions that depend on the VCDOORFR may be unavailable or may not function as expected.
|
|
|
The Electronic Parking Brake made an unexpected state transition.
|
Electronic Parking Brake moved between states that are not marked as having a valid transition.
|
Logical bug in the software
|
|
|
One or more of the messages the vehicle controller receives periodically from the rear left door controller (VCDOORRL) is not received, indicating the VCDOORRL may be unavailable (MIA).
|
The vehicle controller does not receive one or more of the expected messages from the VCDOORRL within the expected time frame.
|
Vehicle functions that depend on the VCDOORRL may be unavailable or may not function as expected.
|
|
|
One or more of the expected CAN messages from the Etherloop Generalized Gateway Rear (Core 1) were not received, indicating the EGGREAR1 ECU may be unavailable (MIA).
|
The local ECU does not receive one or more of the expected messages from the EGGREAR1 within the expected time frame.
|
Vehicle functions that depend on the EGGREAR1 may be unavailable or may not function as expected.
|