Alerts
Loading...
| Signal Name | Description | Condition | Impact |
|---|---|---|---|
|
The drive is likely corrupt and should be reformatted.
|
Dashcam experienced an error while freeing up space or creating a file
|
Dashcam cannot free up space or create new files
|
|
|
The USB drive for Dashcam and Sentry Mode does not have enough space to store video clips.
|
The Dashcam and Sentry Mode USB drive has under 32GB of free space for video clips.
|
Dashcam and Sentry Mode will continue to perform as designed, but the USB drive may fill up soon through normal use.
|
|
|
The Dashcam USB drive is running out of available space to store 60 minutes worth of Recent Clips, which may prevent the Dashcam from recording new video clips.
|
The Dashcam USB drive has under 9GB of available space.
|
The Dashcam USB drive may run out of available space, and the Dashcam may stop recording.
|
|
|
The drive is too large for FAT32 to support repairing.
|
The Dashcam USB drive is formatted FAT32 and over 256GB in size
|
Dashcam USB can become unrecoverable or corrupt
|
|
|
The Tesla Dashcam / Sentry Mode USB drive was installed but is missing or not available.
|
The Tesla Dashcam / Sentry Mode USB drive is missing or not available.
|
The Tesla Dashcam / Sentry Mode USB features may be unavailable.
|
|
|
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
|
|
|
The A2B primary node (in the car computer) was unable to discover any other nodes on the A2B bus, which may lead to a complete loss of audio.
|
The A2B primary node was unable to discover other nodes.
|
There may be a complete loss of audio.
|
|
|
A Wi-Fi stack condition is detected, which may lead to a loss of Wi-Fi connectivity.
|
One of the components on the Wi-Fi stack has a condition.
|
There may be a loss of Wi-Fi connectivity.
|
|
|
eMMC FTL Register has been set.
|
Periodic eMMC check or post-wake eMMC status has the FTL error set
|
Non-functional eMMC
|
|
|
eMMC Status Register has error bits set.
|
Periodic eMMC check or post-wake eMMC status has an error bit set
|
Non-functional eMMC
|
|
|
Post-wake disk check failure.
|
Post-wake disk check fails
|
Complete loss of UI
|
|
|
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.
|
|
|
A condition is detected with the video stream(s) coming from the camera(s).
|
The video stream(s) from the camera(s) is not performing as designed. Alert payload data contains which camera is affected and what the condition is.
|
TThe video stream(s) from the affected camera(s) may not be available for Camera Viewer, Dashcam, and/or Sentry Mode.
|
|
|
Low Disk Space.
|
Insufficient CID storage available to function
|
Misc. system errors could arise due to insufficient free storage
|
|
|
Modem failing to power ON.
|
Successive modem power ON failures
|
Loss of cellular connectivity
|
|
|
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.
|
|
|
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.
|
|
|
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.
|
|
|
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.
|
|
|
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.
|