Alerts
Loading...
| Signal Name | Description | Condition | Impact |
|---|---|---|---|
|
DI_d011_unused11
|
|
-
|
|
|
DI_d017_unused17
|
|
-
|
|
|
The reported proximity voltage indicates that there is a charge cable connected to the vehicle while the vehicle is in a drive state (Drive or Reverse).
|
The vehicle is in a drive state and proximity voltage indicates that a charge cable is connected to the vehicle.
|
This alert is for diagnostic logging purposes only.
|
|
|
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).
|
A shift request was made but the DI ECU does not detect a valid key.
|
The vehicle cannot enter Drive.
|
|
|
The drive interface (DI) electronic control unit (ECU) detects that the driver may no longer be in the driver's seat while the vehicle is not in Park.
|
The vehicle is not in Park and the front vehicle controller detects conditions indicating that the driver is leaving.
|
The vehicle shifts into Park
|
|
|
The drive interface (DI) electronic control unit (ECU) detects a condition that causes it to cancel cruise control.
|
The DI ECU detects a condition that causes it to cancel cruise control. Alert log signal data provides information on the specific condition(s) detected.
|
Cruise control is deactivated.
|
|
|
The drive interface (DI) electronic control unit (ECU) decreases torque because it detects that the brake and accelerator pedal were pressed at the same time.
|
The DI ECU detects that both the accelerator oedal and the brake were pressed at the same time.
|
Torque/acceleration is limited.
|
|
|
The drive interface (DI) electronic control unit (ECU) receives a shift request from Drive to Reverse or Reverse to Drive but denies it because the vehicle speed is too high.
|
There is a shift request from D to R (or vice versa) while the vehicle speed is above the alert threshold.
|
The shift request is denied.
|
|
|
The drive interface (DI) electronic control unit (ECU) receives a shift request but detects a condition that prevents the request from being honored.
|
The DI ECU detects a condition that causes it to deny a shift request. Set reasons defined by the DI_shiftDeniedReason value-table.
|
User unable to shift until clear condition is resolved.
|
|
|
The drive interface (DI) electronic control unit (ECU) detects that the electronic power assisted steering, gen 3 (EPAS3) controller area network (CAN) node is missing (MIA).
|
The DI ECU is not receiving the expected CAN communication from the EPAS3, and considers it irrational or MIA.
|
The DI ECU is unable to monitor the state of the EPAS3.
|
|
|
The drive inveter (DI) electronic control unit (ECU) detects that the fast learning initiated by resetting mileage since last tire service has finished.
|
This alert is set after the vehicle has driven long enough to learn new tire parameters after the user resets their tire service mileage in the Service UI, or the similar ODIN routine is run through Toolbox. It could indicate the vehicle recently had tire service, and the vehicle fast learned its new parameters.
|
This alert indicates the vehicle has very quickly learned the new tire sizes after a customer reset their tire service mileage or service updated tire parameters in order to improve the driving experience and reduce loss of regen or drive torque after tire service. Potential impact to learned tire parameters can be fixed by resetting again if any loss of torque still present after this alert.
|
|
|
The drive interface (DI) electronic control unit (ECU) detects that the iBooster (IBST, or brake assist) controller area network (CAN) node is missing (MIA).
|
The DI ECU is not receiving the expected CAN communication from the IBST, and considers it irrational or MIA.
|
The DI ECU is unable to monitor the state of the IBST.
|
|
|
The drive interface (DI) or drive inverter (DIx) electronic control unit (ECU) detects that the restraints control module (RCM) controller area network (CAN) node is missing (MIA).
|
The DI ECU is not receiving the expected CAN communication from the RCM, and considers it irrational or MIA.
|
The DI ECU is unable to monitor the state of the RCM.
|
|
|
The drive interface (DI) electronic control unit (ECU) detects that a differential locker (DFLKF or DFLKR) controller area network (CAN) node is missing (MIA).
|
The DI ECU is not receiving the expected CAN communication from the DFLKF or DFLKR, and considers it irrational or MIA.
|
The DI ECU is unable to monitor the state of the DFLKF or DFLKR.
|
|
|
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.
|
The DI ECU detects that the vehicle is in Drive before the HV system is up.
|
The vehicle cannot enter Drive.
|
|
|
DI_d016_unused16
|
|
-
|
|
|
DI_d015_unused15
|
|
-
|
|
|
The drive interface (DI) electronic control unit (ECU) detects that the Supermanifold Vehicle Controller (VCSUPER) controller area network (CAN) node is missing (MIA).
|
The DI ECU is not receiving the expected CAN communication from the VCSUPER, and considers it irrational or MIA.
|
The DI ECU is unable to monitor the state of the VCSUPER.
|
|
|
The Left Secondary Vehicle Controller (VCLEFTS) node is Missing in Action (MIA) on Controller Area Network (CAN) for one or more messages.
|
The VCLEFTS node is MIA on CAN for one or more messages. The VCLEFT node may have a condition affecting functionality.
|
The Drive Unit may not operate as expected.
|
|
|
The drive interface (DI) electronic control unit (ECU) detects that the front vehicle controller (VCFRONT) controller area network (CAN) node is missing (MIA).
|
The DI ECU is not receiving the expected CAN communication from the VCFRONT, and considers it irrational or MIA.
|
The DI ECU is unable to monitor the state of the VCFRONT.
|