Alerts
Loading...
| Signal Name | Description | Condition | Impact | Important |
|---|---|---|---|---|
|
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.
|
No
|
|
|
An error occurred during whitelisting of Bluetooth Low Energy (BLE) media access control (MAC) addresses
|
If any error occured while whitelisting devices
|
Endpoint may continually trigger FALSE RF Mia alerts (centerEndpointRFMia), causing the alerts to appear repeatedly in logs. This alert does NOT indicate any larger impact to Bluetooth Low Energy (BLE) functionality.
|
No
|
|
|
An error occured during whitelisting of BLE Mac Adresses
|
If any error occured while whitelisting devices
|
Endpoint may continually trigger FALSE RF Mia alerts (rearEndpointRFMia), causing the alerts to appear repeatedly in logs. This alert does NOT indicate any larger impact to Bluetooth Low Energy (BLE) functionality.
|
No
|
|
|
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.
|
No
|
|
|
Key whitelist operation failed
|
when a whitelist operation resulted in failure
|
key was not added or updated
|
No
|
|
|
Door handle pulled without an authenticated device
|
Door handle pulled without auth
|
May indicate passive entry failure
|
No
|
|
|
The Vehicle Security Controller (VCSEC) detects a condition affecting the functionality of the front left Bluetooth Low Energy (BLE) endpoint and requests a soft reset.
|
The VCSEC requests a soft reset for the front left BLE endpoint. Alert log signal data should provide more information on the specific condition(s) detected that caused the soft reset.
|
The front left BLE endpoint is being reset and may be temporarily unavailable.
|
No
|
|
|
One or more sensors, or the security controller may be missing or damaged
|
Vehicle has spent more than 10 minutes while driving with less than 4 sensors connected
|
TPMS system is not functional
|
No
|
|
|
Reached maximum number of attempts to identify a BLE device was reached
|
BLE device is connected. Reached maximum number of attempts to identify this device
|
None
|
No
|
|
|
This VCSEC has no customer-usable keys paired to it
|
VCSEC has no customer-usable keys paired to it
|
Car will not be secure; customer will not be able to drive
|
No
|
|
|
One or more sensors have indicated a low battery
|
One or more battery voltages are below 2.5v
|
None
|
No
|
|
|
Connected Key is expiring. will be removed in 10mins. For informational purposes only
|
When a key is detected to be expiring in 10mins and it is currently connected to the vehicle
|
Connected key may not be able to lock/unlock/authenticate drive
|
No
|
|
|
Front right tire may be slightly underinflated or leaking
|
Front right sensor reports pressure under region specific percentage of recommended cold pressure (RCP)
|
TPMS telltale and poor vehicle performance
|
No
|
|
|
Security Vehicle Controller (VCSEC) is using the factory key (unfused) rather than a production key (fused).
|
This alert is set on first boot when the VCSEC is unfused.
|
ODIN key pairing or remote commands may not work until the VCSEC is fused.
|
No
|
|
|
The security controller did not receive event for more than 10 seconds from the front 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.
|
No
|
|
|
The Security Controller (VCSEC) has not detected signal from the wireless charger Near Field Communication (NFC) reader for over ten seconds.
|
VCSEC has not detected signal from the wireless charger NFC reader for over ten seconds. The wireless charger NFC reader may have a condition affecting functionality.
|
VCSEC may not function as expected. VCSEC may retain a last known valid value that is no longer accurate. Vehicle security and communication with consumer's authentication device may not function as expected.
|
No
|
|
|
The Security Controller (VCSEC) has not detected signal from one of two Bluetooth Low Energy (BLE) endpoints within VCSEC A-Header for over ten seconds.
|
VCSEC has not detected signal from one of two BLE endpoints within VCSEC A-Header for over ten seconds. The BLE endpoint may have a condition affecting functionality.
|
VCSEC may not function as expected. VCSEC may retain a last known valid value that is no longer accurate. Vehicle security and communication with consumer's authentication device may not function as expected.
|
No
|
|
|
The security controller did not receive event for more than 10 seconds from the front 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.
|
No
|
|
|
Child seat battery is low. Need to replace battery for child seat
|
Child seat battery is low
|
Child seat communication with the vehicle will be disconnected
|
No
|
|
|
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.
|
No
|