Alerts

-

-

-

-

-

-

-

-

-

-

One of HOLD stopping mode's unavailable reasons is active.

The DI may not be able to bring the vehicle to a stop and hold on grades when stopping mode HOLD is selected on UI.

Vehicle hold is unavailable when HOLD stopping mode is activated, or the external brake request feature becomes unavailable from the electronic stability program module.

The DI holds the vehicle using motor torque, which may lead to reduced hold performance while near standstill.

The Drive Inverter (DI) is not receiving signals from the Redundant (Brake) Control Unit (RCU) properly. Controller Area Network (CAN) issues should be diagnosed and can be caused by RCU not transmitting messages or general bus error frames or shorts.

The Redundant (Brake) Control Unit (RCU) is unavailable to perform backup braking requests and may impact traction and vehicle dynamics control performance. The vehicle should be driven with extreme caution if the traction or vehicle dynamics control systems are faulted.

The DI receives a shift request from the PM when the vehicle's speed is above 1 mph (1.6 km/h).

The DI automatically shifts to Neutral without user request.

The ESP reports secondary collision mitigation is active.

The ESP ECU may engage the brakes and the DI will remove accelerating torque.

The DI ECU does not receive the expected CAN messages from TAS.

TAS may be unavailable.

The vehicle has entered Track Mode.

In Track mode, the vehicle's stability control, traction control, regenerative braking, and cooling system behavior will be modified.

The DI ECU detects that some or all velocity estimate inputs are unavailable. Check for corresponding ECU missing (MIA) alerts from DI and other ECUs to help identify the cause of the controller area network (CAN) issue.

Traction control and stability control are unavailable, requiring greater manual input from the driver.

This alert sets any time traction control is not available. This is almost always due to the system being faulted. To diagnose the cause of the fault, check this alert's payload to identify which inputs are in a degraded state. <br>Steps to find cause:<br>1) If velocityEstimatorState is degraded, check other DI alert for velocityEstimatorState to find the root cause. If velocityEstimatorState is normal: <br>2) If btcTargetState or ptcTargetState are degraded, check for CAN bus issues (these signals come from ESP) or sensor issues with ESP (check associated ESP alerts). If target states are normal: <br>3) If addState is degraded, check for other DI alerts about ADD. If slaveADDState is degraded, check for DIS alerts about ADD and check for other DI alerts indicating CAN communication issues with DIS.

Traction control is not available. The vehicle should be driven with extreme caution.

The actuators required for stability control are in degraded states, so stability control is also degraded. Check tractionControlState and espActuatorState to find the specific controller that is degrading stability control. For tractionControlState, check previous DI alerts that point to specific cause of their degredation. For espActuatorState, check for ESP alerts that point to the specific cause of its degredation.

Traction control and stability control may fault due to this error, requiring greater manual input from the driver.