Alerts
Loading...
| Signal Name | Description | Condition | Impact |
|---|---|---|---|
|
UMC_w003_GFCISelfTestFault
|
|
-
|
|
|
Alert indicating a UI process has exited with an error, payload contains the exited process name and exit signal.
|
UI process exits with error.
|
A process stopped unexpectedly. Depending on the specific process, some features may be unavailable.
|
|
|
The navigation service encountered an error when processing a navigation request.
|
Navigation service reports an error when attempting to navigate to a destination.
|
Navigation service falls back to offline routing. This can occur even if the vehicle has connectivity.
|
|
|
An error with a User Interface (UI) database was detected and the automatic recovery was not able to restore its functionality. Therefore some data from this database may be missing or incorrect and dependent features may not function as expected.
|
Database corruption recovery mechanism fails, triggers on each failed automatic recovery attempt.
|
Impacts specific UI features dependent on the affected database.
|
|
|
No hardware audio devices available in the system
|
Hardware audio devices intialization failed and will be re-tried
|
No audio
|
|
|
The Trailer Power Line Communication (PLC) Electronic Control Unit (ECU) is MIA while in drive or accessory power state.
|
The Trailer PLC ECU was detected MIA while in drive or accessory power state.
|
Trailer Anti-Lock Braking System may be unavailable.
|
|
|
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.
|
|
|
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.
|
|
|
Active Safety Automatic Emergency Braking System (AEBS) feature unavailable
|
AEBS feature enabled in the region and unavailable.
|
Potential lack of AEBS active safety feature
|
|
|
UMC_w010_inputOT
|
|
-
|
|
|
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.
|
|
|
UMC_w011_proxDisconnected
|
|
-
|
|
|
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.
|
|
|
UMC_w004_inputOverVoltage
|
|
-
|
|
|
UMC read smart adapter genealogy data and CRC check failed
|
UMC smart adapter genealogy was read but the data failed an integrity check
|
UMC will only report 8 A charge current capability until smart adapter genealogy can be read and passes an integrity check
|
|
|
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.
|
|
|
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.
|
|
|
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 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.
|
|
|
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.
|