DI_a171 — Drive Rail Not Requested

Full alert identifier: DI_a171_driveRailNotRequested

Alert description

The drive interface (DI) electronic control unit (ECU) cannot confirm that a vehicle controller ECU requested a drive state, and as a result blocks shifting into Drive or Reverse.

Potential impact

The vehicle cannot enter Drive.

Set condition

The DI ECU does not receive a controller area network (CAN) message requesting a drive state.

Clear condition

The DI ECU detects that a drive state was requested.

Check other alerts

With Service Mode Plus enabled, open Service Alerts → All. Review the other alerts for clues to the cause of DI_a171.

DI_a174 — Not Ok To Start Drive DI_a174_notOkToStartDrive The drive interface (DI) electronic control unit (ECU) detects that the low voltage (LV) supply is too low to shift into Drive.
DI_a023 — Car Not Parked DI_a023_carNotParked The drive interface (DI) electronic control unit (ECU) detects that the electronic park brake (EPC) ECU is missing (MIA) and as a result cannot honor the park request.
DI_a129 — Epb Not Applied DI_a129_epbNotApplied The drive interface (DI) electronic control unit (ECU) detects a condition that prevents the electronic parking brake (EPB) from being set while the vehicle is not moving.
DI_a167 — Key Not Authenticated DI_a167_keyNotAuthenticated The drive interface (DI) electronic control unit (ECU) does not detect a valid key (key card, key fob, phone as key, or Tesla mobile app).
DI_a227 — Contactors Not Closed DI_a227_contactorsNotClosed The drive interface (DI) electronic control unit (ECU) has not started the drive rail yet because the high voltage (HV) system is not yet energized for drive.

Browse all DI alert codes