Alerts
Loading...
| Signal Name | Description | Condition | Impact |
|---|---|---|---|
|
Autopilot Processor Secondary (APS) has not received one or more Controller Area Network (CAN) messages from the front vehicle controller (VCFRONT) on Party Bus.
|
APS does not receive one or more CAN messages from VCFRONT on Party Bus.
|
Some Autopilot features like Autowiper will be impacted.
|
|
|
An Autopilot Processor Secondary (APS) device has not received one or more universal asynchronous receiver-transmitter (UART) messages from system-on-chip (SoC) A or B.
|
APS (SMS / SMS UART) does not receive one more more UART messages from SoC A or B.
|
AP features will be unavailable.
|
|
|
The Autopilot (AP) electronic control unit (ECU) detects a watchdog event on the Turbo B main processor, which causes the AP ECU to reboot.
|
The AP ECU detects a watchdog event on the Turbo B main processor, causing the AP ECU to reboot.
|
All AP features will be unavailable.
|
|
|
The Autopilot (AP) electronic control unit (ECU) detects the Turbo B main processor encounters a lockup error in the security controller subsystem (SCS), which causes the AP ECU to reboot.
|
The AP ECU detects a lockup error on the Turbo B main processor in SCS, causing the AP ECU to reboot.
|
All AP features will be unavailable.
|
|
|
The Autopilot (AP) electronic control unit (ECU) detects the Turbo B main processor encounters a lockstep error in the safety management subsystem (SMS).
|
The AP ECU detects a lockstep error on the Turbo B main processor in the SMS.
|
All AP features will be unavailable.
|
|
|
One or more of the messages the Autopilot Processor Secondary (APS) receives periodically from the Rear Steering Actuator (RSA) Electronic Control Unit (ECU) is not received, indicating the RSA ECU may be unavailable (MIA).
|
APS does not receive RSA messages for more than 10 messages.
|
Autopilot features will be unavailable.
|
|
|
Undervoltage detection by the CPU can set this alert.
|
Sudden power loss.
|
These are the repercussions of the alert being set
|
|
|
This message contains separate signals for each watchdog reset source.
|
A watchdog (external or internal) was not serviced in time.
|
These are the repercussions of the alert being set
|
|
|
Indicates the reason for the Tesla Inference Processor (TRIP) issue reported by the memory built-in self-test (MBIST). Autopilot features are unavailable.
|
The Autopilot electronic control unit (ECU) reports an unexpected TRIP issue reported by the MBIST.
|
Autopilot features are unavailable.
|
|
|
APS electronic control unit (ECU) encountered an unusual error during boot process.
|
Error occurred during APS boot process.
|
Autopilot may be unavailable.
|
|
|
The Autopilot electronic control unit (ECU) encountered an unusual timeout in sleep state transition.
|
Timed out in sleep state control.
|
Autopilot may unexpectedly stay on or off.
|
|
|
The Autopilot electronic control unit (ECU) encountered an unusual timeout in power state transition.
|
Timed out in power state control.
|
Autopilot may unexpectedly stay on or off.
|
|
|
The Autopilot electronic control unit (ECU) detects that the Media Control Unit (MCU) port connected to the ethernet switch has a link down, indicating a condition affecting the cabling or the ECU connected to that port.
|
The alert is set if link goes down.
|
Communication between the autopilot ECU and MCU will be disrupted.
|
|
|
The Autopilot Electronic Control Unit (ECU) detects an unexpected condition affecting the Universal Flash Storage (UFS).
|
The Autopilot UFS device experienced an unexpected condition affecting its operation. Alert log signal data will provide further information on the specific condition(s).
|
Autopilot functionality is limited or unavailable. The rear-view (backup) camera feed is unavailable on the Media Control Unit (MCU).
|
|
|
The Autopilot Secondary (APS) detects poor signal quality on one or more ports of the etherloop switch.
|
A poor signal quality on any etherloop switch port sets the alert.
|
Communication between the various electronic control units (ECUs) may fail.
|
|
|
The APS detects that a port of the etherloop switch has a link down, indicating a condition affecting the cabling or the electronic control unit (ECU) connected to that port. On turbo A, Port 2 is connected to RIGHT controller. On turbo B, Port 2 is connected to GTW.
|
The alert is set if link goes down.
|
Communication between the various electronic control units (ECUs) on the etherloop bus may be disrupted.
|
|
|
Autopilot Processor Secondary (APS) received a frame from an unexpected Media Access Control (MAC) source. The payload has a 6 byte MAC address of an unknown source and the address is in the decimal number system. While this condition is present, APS may receive ethernet frames from an unknown sender.
|
APS received a frame from an unexpected MAC source.
|
APS may receive ethernet frames from an unknown sender.
|
|
|
The Autopilot electronic control unit (ECU) reports a graphic processing unit (GPU) hardware condition. Autopilot features are unavailable.
|
The Autopilot ECU experiences an unexpected GPU hardware condition caused due to an exception trigged by GPU.
|
Autopilot features are unavailable.
|
|
|
The Tesla Inference Processor (TRIP) reports a hardware condition. Autopilot features are unavailable.
|
The Autopilot electronic control unit (ECU) experiences an unexpected TRIP hardware condition.
|
Autopilot features are unavailable.
|
|
|
Autopilot Processor Secondary (APS) has not received one or more Controller Area Network (CAN) messages from Brake Booster (BB) on Party Bus.
|
APS does not receive one or more CAN messages from Brake Booster (BB) on Party Bus.
|
Some Autopilot features like Traffic Aware Cruise Control will be impacted.
|