Alerts
Loading...
| Signal Name | Description | Condition | Impact |
|---|---|---|---|
|
Infotainment process stopped unexpectedly
|
Operating System reports a segmentation fault
|
Application or UI element closes or restarts
|
|
|
Infotainment process hung for extended period of time
|
Operating System reports a task was hung for 2 minutes
|
Touchscreen or UI may not be responsive
|
|
|
Infotainment GPU operation timed out
|
GPU driver reports a fence timeout
|
Touchscreen or UI may not be responsive
|
|
|
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.
|
|
|
A phone contact sync with more than 5000 contacts completed. Alert payload contains the number of contacts loaded.
|
This alert is set when a phone is connected to Bluetooth and a phone contact is synced with over five thousand contacts.
|
Bluetooth connection and call quality may be impacted during a large phone contact sync. Normal operation is expected after the sync is completed.
|
|
|
UMC AC input voltage exceeded upper limit
|
UMC input voltage has risen above 300 V RMS
|
UMC will not allow charging until AC input voltage is within 90-300 V RMS
|
|
|
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.
|
|
|
Indicates that the User Interface (UI) main application, also known as QtCar, is intentionally rebooting due to a user-initiated action.
|
QtCar receives a valid request to reboot, such as a user-initiated software update or a settings change that requires a restart.
|
QtCar will temporarily be unavailable during reboot, which may cause a brief interruption to the user's interaction with the vehicle's systems.
|
|
|
The Media Control Unit (MCU) does not detect a connection to the center display.
|
The MCU's DisplayController does not detect a display present at the center display connector.
|
The center display may not be powered or may not function as expected.
|
|
|
UMC AC input voltage is below lower limit
|
UMC AC input voltage has fallen below 90 V RMS
|
UMC will not allow charging until AC input voltage is within 90-300 V RMS
|
|
|
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 modem has failed to transition to suspended state.
|
The modem fails to suspend.
|
The vehicle might stay awake, increasing High Voltage battery discharge rate.
|
|
|
One or more of the expected messages the electronic control unit (ECU) receives periodically from the high voltage processor (HVP) ECU is not received, indicating the HVP may be unavailable (MIA).
|
One or more of the expected messages from the HVP ECU is not received.
|
Vehicle may be unable to drive. Charging may be limited or unavailable.
|
|
|
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.
|
|
|
Warns if the processor has experienced a reset due to power loss.
|
Sudden power loss.
|
Controller is MIA for some time.
|
|
|
UMC_w038_chcVitalsFault
|
|
-
|
|
|
UMC_w037_GFCICalibration
|
|
-
|
|
|
UMC_w039_inputOverCurrent
|
|
-
|
|
|
Universal Mobile Connector (UMC) AC input side ground impedance exceeded warning threshold. Charging is not affected.
|
UMC AC input side ground impedance is above 1 Mohm
|
UMC will display a warning LED pattern, but will allow charging at the nominal current
|
|
|
UMC_w036_SA_gpio
|
|
-
|