Alerts
Loading...
| Signal Name | Description | Condition | Impact |
|---|---|---|---|
|
No hardware audio devices available in the system.
|
Hardware audio devices intialization failed and will be re-tried
|
No audio
|
|
|
One or more services in the User Interface (UI) process ID control group is using more memory than expected.
|
A UI service consumes more memory than expected.
|
The process consuming excessive memory may not perform as expected. Alert payload data will indicate which process is affected.
|
|
|
Node and type of circuit problem.
|
Circuit problem is detected.
|
Loss of audio communication over specific bus.
|
|
|
One or more services in the User Interface (UI) process ID control group is using more memory than expected.
|
A UI service consumes more memory than expected.
|
The process consuming excessive memory may not perform as expected. Alert payload data will indicate which process is affected.
|
|
|
Intelligent Speed Assist (ISA) feature is disabled during this time.
|
ISA feature is enabled in the vehicle's region and experienced an user action that disables the feature.
|
ISA active safety feature is disabled by user action.
|
|
|
Active Safety Automatic Emergency Braking System (AEBS) feature unavailable.
|
AEBS feature enabled in the region and unavailable.
|
Potential lack of AEBS active safety feature
|
|
|
Active Safety Automatic Emergency Braking System (AEBS) feature faulted.
|
AEBS feature enabled in the region and faulted.
|
Potential loss of AEBS active safety feature.
|
|
|
The modem has failed to transition to suspended state.
|
The modem fails to suspend.
|
The vehicle might stay awake, increasing High Voltage battery discharge rate.
|
|
|
The incorrect memory capacity is detected upon system boot up.
|
System boots with the incorrect memory capacity.
|
High system memory usage may lead to degraded Infotainment performance or frequent system reboots.
|
|
|
The Media Control Unit (MCU) does not detect a connection to the rear display.
|
The MCU's DisplayController does not detect a display present at the rear display connector.
|
The rear display may not be powered or may not function as expected.
|
|
|
The User Interface (UI) reported firmware version does not match the vehicle firmware version reported by the Gateway.
|
The User Interface (UI) reported firmware version does not match the firmware version reported by the Gateway.
|
A potential degradation of the User Interface (UI) experience or lack of communication between the UI and vehicle.
|
|
|
UMC_w009_vehConnOT
|
|
-
|
|
|
Accelerator pedal was deeply pressed at collision.
|
Collision is detected with high accelerator pedal position.
|
The collision may be related to the high accelerator pedal position.
|
|
|
The USB hub installed does not contain a Bluetooth module.
|
Did not detect USB Universal Asynchronous Receiver/Transmitter (UART) devices within 30 seconds after system wake or bootup, and Bluetooth daemon (btd)-rear had not yet initialized.
|
Bluetooth headset feature might not function.
|
|
|
Telematics Control Unit (TCU) reported Recovery Nand firmware version does not match the vehicle firmware version.
|
Telematics Control Unit (TCU) Recovery Nand reported signature does not match the stored deploy signature.
|
Telematics Control Unit (TCU) might not be recoverable if Primary Nand is not functioning as expected.
|
|
|
UMC_w018_vehConnOTFoldback
|
|
-
|
|
|
UMC_w017_wallPlugOTFoldback
|
|
-
|
|
|
UMC_w016_pcbaOTFoldback
|
|
-
|
|
|
UMC_w015_SA_Connection
|
|
-
|
|
|
UMC_w014_SA_Genealogy
|
|
-
|