Alerts
Loading...
| Signal Name | Description | Condition | Impact | Important |
|---|---|---|---|---|
|
The main audio process (Audiod) Input / Output (IO) thread is being prevented from executing, or blocked. Audiod has restarted due to Advanced Linux Sound Architecture (ALSA) IO function taking longer than 10 seconds.
|
The main audio process (Audiod) IO thread is blocked. Audiod has restarted due to the ALSA IO function taking longer than 10 seconds. The IO thread may have a condition affecting functionality.
|
Audiod and vehicle audio may not function as expected.
|
No
|
|
|
Low Disk Space
|
Insufficient CID storage available to function
|
Misc. system errors could arise due to insufficient free storage
|
No
|
|
|
The USB hub is not enumerating
|
The USB hub is not enumerating, it may be broken or disconnected.
|
USB hub may be broken or disconnected
|
No
|
|
|
A software update has ended.
|
A software update has ended. One of the conditions will be present on the vehicle: success, early_failure, late_failure, or hammered.
|
The vehicle software may have been updated. If the update did not complete, the vehicle may not function as expected.
|
No
|
|
|
A software update has started.
|
A software update has started.
|
The vehicle software is being updated. The vehicle will be unable to start a drive cycle.
|
No
|
|
|
The QtCarVehicle link is stalled, preventing communication between the Center Instrument Display (CID) or User Interface (UI) and the vehicle Gateway (GTW).
|
The QtCarVehicle link is stalled between the CID / UI and GTW.
|
The touchscreen UI may not reflect the current state of the vehicle. Vehicle information, such as turn indicators, drive modes, and vehicle speed, may be not be accurate.
|
No
|
|
|
The vehicle gateway (GTW) cannot ping the radio tuner after at least 3 attempts to connect.
|
The GTW cannot ping the radio tuner after at least 3 attempts to connect. The radio tuner may have a condition affecting functionality.
|
The radio tuner may not function as expected.
|
No
|
|
|
The vehicle gateway (GTW) cannot ping the radio tuner.
|
The GTW cannot ping the radio tuner.
|
The radio tuner may not function as expected. The radio tuner may take longer to operate.
|
No
|
|
|
The SIM card type is set to Removable, is missing, or is not fully seated, which may lead to a loss of cellular connectivity.
|
The SIM card type is set to Removable, is missing, or is not fully seated.
|
There may be a loss of cellular connectivity.
|
No
|
|
|
Display status check failed due to touch device missing.
|
The /dev/input/touch directory is not accessible.
|
Touchscreen is unresponsive or has limited functionality.
|
No
|
|
|
The Dashcam and Sentry Mode USB drive does not write fast enough for Dashcam operation, which may prevent Dashcam and Sentry Mode from saving videos.
|
Dashcam detects a USB drive below the minimum sequential write speed of 4MB/s.
|
Dashcam and Sentry Mode may not be able to save videos.
|
No
|
|
|
The A2B microphone channels are in a swapped state
|
The device is in the swapped channel state if any of the first three channels are zero and any of the other channels are non zero
|
Microphone may be inoperative. Its audio stream will be restarted
|
No
|
|
|
The Ecall audio configurator 'Ecall Digital microphone' test failed
|
Ecall digital microphone RMS amplitude is lower then EcallDigitalMicRMSThreshold (0.02)
|
Ecall voice issues or Ecall unavailable
|
No
|
|
|
The car computer is unable to recieve the deserialization chip ID over the I2C bus, which may lead to the touchscreen being blank, unresponsive, or have limited functionality.
|
The car computer is unable to recieve the deserialization chip ID over the I2C bus.
|
The touchscreen may be blank, unresponsive, or have limited functionality.
|
No
|
|
|
Display status check failed due to datastream serialization error.
|
The serialiser check failed because the I2C bus 2 failed to open or the serializer chip state check failed.
|
Touchscreen is blank, unresponsive or has limited functionality.
|
No
|
|
|
The cellular modem has been rebooted due to an active eCall lasting longer than 1,800 seconds, the backstop timer value.
|
The cellular modem has been rebooted due to an active eCall lasting longer than 1,800 seconds, the backstop timer value. eCall may have a condition affecting functionality.
|
The cellular modem may not function as expected. The eCall feature may not function as expected.
|
No
|
|
|
The modem cellular connection search timer has expired, which may lead to a loss of cellular connectivity.
|
The modem cellular connection search timer has expired.
|
There is a loss of cellular connectivity.
|
No
|
|
|
The USB drive used for dashcam does not have enough free space.
|
The drive has less than 100MB of free space.
|
Dashcam (and Sentry recording) will not work.
|
No
|
|
|
The USB drive used for dashcam has failed to mount.
|
FSCK failed to fix the drive while trying to mount it.
|
Dashcam (and Sentry recording) will not work.
|
No
|
|
|
An eCall has been cancelled manually with no passengers present and all doors closed.
|
An eCall has been cancelled manually with no passengers present and all doors closed. eCall or the Restraints Control Module (RCM) may have a condition affecting functionality.
|
The eCall feature may not be functioning as expected.
|
No
|