Alerts
Loading...
| Signal Name | Description | Condition | Impact |
|---|---|---|---|
|
Prevents doors from operating when door motors exceeds temperature threshold.
|
Motor brush temperature exceeds 100 degrees Celsius
|
The power door no longer operates
|
|
|
An interior door release request is inhibited by Autopilot because of a passing pedestrian, vehicle or cyclist. Pressing the interior door release button a second time will allow the door to open.
|
The occupant requests an interior door open while Autopilot has inhibited open due to detecting an oncoming pedestrian, vehicle or cyclist.
|
The occupant's interior door open request is temporarily inhibited.
|
|
|
Mirror stalled unexpectedly while folding or unfolding.
|
If folding motor current exceeds 0.5A or decreases below 0.1A after 500ms from beginning of actuation. Or timeout from current state after 5 seconds.
|
Mirror might be halfway between folded and unfolded
|
|
|
A side-view mirror started a fold or unfold movement, but then stalled before finishing the movement. The mirror will attempt 1 retry to complete the movement.
|
Sets if the mirror folding motor current exceeds 0.5A at some point, but then decreases to below 0.1A between 200ms - 1750ms after the beginning of actuation. Also sets at the end of the retry actuation to capture/log additional data.
|
The mirror will stop for 400ms before attempting the retry. If the mirror unexpectedly stalls again during the retry, it may be left partially folded/unfolded.
|
|
|
Mirror heat undercurrent detected, indicating mirror heating may be limited or unavailable.
|
Mirror heat current was below the expected value
|
This alert is primarily informational and is used for logging purposes. No expected impact on vehicle functionality
|
|
|
The driver integrated circuit (IC) experiences a condition affecting the operation of the loads controlled by the device.
|
The driver IC reports a condition affecting its operation.
|
Mirror actuations, mirror heating, mirror dimming, or other vehicle operations relying on the driver IC may be inoperative.
|
|
|
This message contains separate signals for each watchdog reset source.
|
A watchdog (external or internal) was not serviced in time.
|
These are the repercussions of the alert being set
|
|
|
Undervoltage detection by the CPU can set this alert.
|
Sudden power loss.
|
These are the repercussions of the alert being set
|
|
|
The SBC CAN transceiver has faulted. Alert will be seen if the trasnceiver has recovered from the faulted condition.
|
The BDY CAN bus communication is not available.
|
Other ECUs may report this ECU as being MIA and behaviour will be impacted. This alert won't be seen until CAN communcation has returned.
|
|
|
Not Available
|
setcondition
|
These are the repercussions of the alert being set
|
|
|
Not Available
|
setcondition
|
These are the repercussions of the alert being set
|
|
|
Not Available
|
Response timeout of a LIN node
|
These are the repercussions of the alert being set
|
|
|
Not Available
|
setcondition
|
These are the repercussions of the alert being set
|
|
|
Not Available
|
setcondition
|
These are the repercussions of the alert being set
|
|
|
The electronic control unit (ECU) detects that the supply voltages from 1 or more components are out of range.
|
The ECU detects the supply voltage is < 7.31V. Specific reason(s) should be available in alert log signal data.
|
The ECU may be unavailable.
|
|
|
This message contains separate signals for Overvoltage and Undervoltage for each rail.
|
ECU 5V rail detected < 4.5V or > 5.5V, or 3.3V rail < 3.0V or > 3.6V for 100ms.
|
These are the repercussions of the alert being set
|
|
|
Not Available
|
Reset can be caused by: Clock Error, Flash Error, Software Reset, Checkstop Reset, Debug Reset
|
Potential issue with hardware or software caused the reset.
|
|
|
This alert is used to create the template for the raw alert log. Double check before this alert is used for something else.
|
Set condition
|
These are the repercussions of the alert being set
|
|
|
Bridge faults are most likely due to configuration error.
|
An fault was reported by the bridge driver while initializing or controlling the bridge driver or a bridge channel.
|
Some or all bridge outputs may not opperate due to a bridge fault.
|
|
|
After a record upgrade is successful, resetting the ECU should clear the alert.
|
Record not found, CRC mismatch, Version mismatch, Version upgrade.
|
Indicate the state of non-volatile data in the ECU.
|