Alerts
Loading...
| Signal Name | Description | Condition | Impact |
|---|---|---|---|
|
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
|
|
|
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.
|
|
|
Not Available
|
A signal is received 10% out of timing 3 times in a row.
|
These are the repercussions of the alert being set
|
|
|
Not Available
|
Reasons to keep the controller awake have been the same for greater than one hour
|
The bus could not sleep causing significant range loss for the battery pack
|
|
|
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
|
setcondition
|
These are the repercussions of the alert being set
|
|
|
The log data contains failure count and up to five init failure codes.
|
A task init function returns with an error.
|
If an init routine fails, software may not opperate correctly.
|
|
|
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
|
Any of the signals in message RCM are set.
|
These are the repercussions of the alert being set
|
|
|
The door zero position is cleared.
|
The door zero position was cleared due to latch closing while door angle is above threshold value, the angle reaching threshold negative value, or the door controller resetting while latch is not closed. Alert payload data should provide more information on specific condition(s) involved.
|
The door power operation is disabled.
|
|
|
The door latch transitions to opened state while the vehicle is in motion.
|
Latch status changes from closed to opened while the vehicle is in motion.
|
Door latch may be opened while vehicle is in motion, or the door latch is incorrectly detected open.
|
|
|
The door stopped unexpectedly while opening or closing.
|
The door controller detected a stopping condition while opening or closing. Alert payload data should provide more information on specific condition(s) involved.
|
Door opening or closing actuation did not complete.
|
|
|
The Falcon Door Body Controller has detected the electrical current limit for the upper actuator has been exceeded.
|
The actuator's electrical current has been exceeded.
|
An obstruction may be impacting functionality or a strut may be damaged.
|
|
|
The door ice breaker extended but the door latch is not opened.
|
Door ice breaker started retracting while the door latch is not opened.
|
Door might not open due to the latch release actuator not working or an external factor blocking the door.
|