Alerts
Loading...
| Signal Name | Description | Condition | Impact |
|---|---|---|---|
|
One or more of the messages the vehicle controller receives periodically from the Tesla Air Suspension (TAS) electronic control unit (ECU) is not received, indicating the TAS ECU may be unavailable (MIA).
|
One or more of the expected messages from the TAS ECU is not received.
|
The air suspension may not function as expected.
|
|
|
One or more of the messages the vehicle controller receives periodically from the power conversion system (PCS) electronic control unit (ECU) is not received, indicating the PCS ECU may be unavailable (MIA).
|
One or more of the expected messages from the PCS ECU is not received.
|
The vehicle may be unable to charge.
|
|
|
Front right tire may be slightly underinflated or leaking.
|
Front right sensor reports pressure under allowed percentage of recommended cold pressure (RCP)
|
TPMS telltale and poor vehicle performance
|
|
|
An issue is indicated from the non-volatile memory manager.
|
Non-volatile memory misconfiguration or underlying flash/filesystem error.
|
Non-volatile memory records may be incorrect or missing.
|
|
|
One or more of the messages the vehicle controller receives periodically from the left Electronic Park Brake (EPBL) electronic control unit (ECU) is not received, indicating the EPBL ECU may be unavailable (MIA).
|
The vehicle controller does not receive one or more of the expected messages from the EPBL ECU within the expected time frame.
|
The parking brake may be unavailable or may not function as expected.
|
|
|
One or more expected Controller Area Network (CAN) messages from the Electronic Stability Program (ESP) electronic control unit (ECU) was not received. Stability and traction control functions may be unavailable, or their performance may be affected.
|
An expected CAN message from the Electronic Stability Program (ESP) electronic control unit (ECU) has not been received within the expected timeout, or the message drop rate is too high while the ESP is CAN active.
|
Stability and traction control functions may be unavailable, or their performance may be affected.
|
|
|
One or more of the messages the vehicle controller receives periodically from the right vehicle controller (VCRIGHT) is not received, indicating the VCRIGHT may be unavailable (MIA).
|
The vehicle controller does not receive one or more of the expected messages from the VCRIGHT within the expected time frame.
|
Vehicle functions that depend on the VCRIGHT may be unavailable or may not function as expected.
|
|
|
Connection sniffer endpoints are not reporting connection signal strength.
|
Center endpoint has valid RSSI values but sniffer does not
|
Reduced passive entry performance
|
|
|
Door handle pulled without an authenticated device.
|
Door handle pulled without auth
|
May indicate passive entry failure
|
|
|
A previously paired sensor identification was removed either automatically or part of diagnostic routine.
|
A sensor status changes to the unpaired state
|
Some pressure reading will not be available
|
|
|
The security controller did not receive event for more than 10 seconds from the rear endpoint.
|
The security does not hear any response when requesting an event from an endpoint for more than 10 seconds.
|
Phone key will not work.
|
|
|
The security controller did not receive event for more than 10 seconds from the right endpoint.
|
The security does not hear any response when requesting an event from an endpoint for more than 10 seconds.
|
Phone key will not work.
|
|
|
Low battery detected on key device.
|
If reported key voltage is below a temperature dependent threshold
|
Key will stop functioning soon
|
|
|
The Tire Pressure Monitoring System (TPMS) pairing process was started but not completed. TPMS will not be fully configured.
|
Fewer than 4 sensors have paired.
|
Tire Pressure Monitoring System (TPMS) will not be fully configured.
|
|
|
An error occured when sending indication to the phone.
|
An error occured when sending indication to the phone.
|
This alert is used primarily for logging purposes.
|
|
|
There were no keys detected by the vehicle while it was in Drive. Vehicle may not restart after current drive if no key is detected.
|
No phone key or key fob has been connected after driving for 250 meters, and near-field communication (NFC) card was not used for authentication.
|
If the user puts the vehicle in Park after this alert sets, they may not be able to shift into Drive again because no key is detected.
|
|
|
B Pillar Bluetooth Low Energy (BLE) chip was not able to talk to Near Field Communication (NFC) chip.
|
B Pillar BLE chip was not able to talk to NFC chip.
|
Key cards will not work.
|
|
|
An error occured during whitelisting of BLE Mac Adresses.
|
If any error occured while whitelisting devices
|
Endpoint may continually trigger FALSE RF Mia alerts (passengerEndpointRFMia), causing the alerts to appear repeatedly in logs. This alert does NOT indicate any larger impact to Bluetooth Low Energy (BLE) functionality.
|
|
|
The security controller did not receive event for more than 10 seconds from the left endpoint.
|
The security does not hear any response when requesting an event from an endpoint for more than 10 seconds.
|
Phone key will not work.
|
|
|
An error occured during whitelisting of BLE Mac Adresses.
|
If any error occured while whitelisting devices
|
Endpoint may continually trigger FALSE RF Mia alerts (driverEndpointRFMia), causing the alerts to appear repeatedly in logs. This alert does NOT indicate any larger impact to Bluetooth Low Energy (BLE) functionality.
|