Alerts
Loading...
| Signal Name | Description | Condition | Impact |
|---|---|---|---|
|
UMC proximity line disconnected or vehicle is not providing proximity voltage
|
Proximity line in charge cable has no voltage present but a vehicle is connected
|
UMC will not allow charging while the proximity line is broken because it cannot determine if the cable is latched
|
|
|
UMC pilot signal is being pulled to an invalid level or pilot generation circuit failure
|
Pilot signal transitioned to an invalid voltage level
|
UMC will not allow charging while the pilot signal is invalid
|
|
|
UMC ADC self test: reading did not pass sanity check
|
UMC microcontroller analog readings fail sanity checks
|
UMC will not operate until ADC readings pass sanity checks
|
|
|
UMC AC input side ground impedance exceeded threshold
|
UMC AC input side ground impedance is above 1 Mohm
|
UMC will not allow charging until the protective earth connection is corrected
|
|
|
UMC ground leakage current exceeded threshold
|
A ground fault current exceeding detection threshold was detected
|
UMC will not charge until the ground fault is corrected. UMC will retest after 15 minutes (except when an EU smart adapters) or charge cable cycle
|
|
|
Infotainment GPU operation timed out
|
GPU driver reports a fence timeout
|
Touchscreen or UI may not be responsive
|
|
|
UMC GFCI self test failed
|
GFCI self test failed
|
UMC will not charge until the self test passes. UMC will retest automatically after 15 minutes (except EU smart adapters) or charge cable cycle
|
|
|
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.
|
|
|
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.
|
|
|
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
|
|
|
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.
|
|
|
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
|
|
|
UMC detected contactor stuck open or closed
|
UMC contactor is open when it should be closed (non-EU smart adapter) or closed when it should be open for several seconds
|
UMC will not allow charging if the contactor is stuck in an unexpected state. Charge handle pins may be live and hazardous. Stuck open (non-hazardous) contactors will not trigger this fault with EU smart adapters.
|
|
|
Active Safety Emergency Lane Keep System (ELKS) feature unavailable
|
ELKS feature enabled in the region and unavailable.
|
Potential lack of ELKS active safety feature
|
|
|
Tuner has failed to perform an OTA Update of the latest radio tuner firmware.
|
The radio tuner set a status flag indicating a firmware OTA update of the tuner has failed early.
|
The radio tuner may be unable to update to the latest firmware provided.
|
|
|
The audio watchdog detects a critical audio error during vehicle wake, which may cause the Media Control Unit (MCU) to restart and/or audio to be temporarily unavailable.
|
The audio watchdog detects a critical audio error within 60 seconds of vehicle wake.
|
If blocked alert log signal values are reported, audio may be unavailable until the next vehicle wake. If rebooted alert log signal values are reported, the MCU will reboot.
|
|
|
The radio tuner firmware expected a newer version of tuner firmware to be installed.
|
The radio tuner reported an older version of installed tuner firmware.
|
The radio tuner may not be on the latest or most reliable version of firmware.
|