Alerts
Loading...
| Signal Name | Description | Condition | Impact | Important |
|---|---|---|---|---|
|
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
|
No
|
|
|
Not Available
|
Failure of a software assertion.
|
These are the repercussions of the alert being set
|
No
|
|
|
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.
|
No
|
|
|
Not Available
|
setcondition
|
These are the repercussions of the alert being set
|
No
|
|
|
Not Available
|
setcondition
|
These are the repercussions of the alert being set
|
No
|
|
|
Not Available
|
Response timeout of a LIN node
|
These are the repercussions of the alert being set
|
No
|
|
|
Not Available
|
setcondition
|
These are the repercussions of the alert being set
|
No
|
|
|
Not Available
|
setcondition
|
These are the repercussions of the alert being set
|
No
|
|
|
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.
|
No
|
|
|
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.
|
No
|
|
|
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
|
No
|
|
|
Undervoltage detection by the CPU can set this alert.
|
Sudden power loss.
|
These are the repercussions of the alert being set
|
No
|
|
|
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
|
No
|
|
|
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.
|
No
|
|
|
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.
|
No
|
|
|
The ultrasonic controller used by the Falcon doors is reported as OFF, or as FAULTED, while it is expected to be ON
|
The ultrasonic controller used by the Falcon door is reported as OFF, or as FAULTED, for more than 500 milliseconds
|
The Falcon door ultrasonic sensors might not be powered on, which could limit the door obstacle detection capabilities
|
No
|
|
|
The Falcon Door Body Controller has detected a deviation from the desired speed of the door section during opening at a rate of 9 degrees per second or upon closure at a speed of 7 degrees per second.
|
Deviation from the desired speed of the door section during opening at a rate of 9 degrees per second or upon closure of 7 degrees per second is detected.
|
Multiple occurrences suggest possible hardware conditions in the door or interference from foreign objects and debris affecting door functionality.
|
No
|
|
|
This alert is our best guess at which actuator is problematic, but this could be incorrect.
|
Positions differ by 5 degrees and the lower front actuator has a lower absolute velocity than the rear.
|
Position differences could indicate damaged, miswired, or unplugged actuators
|
No
|
|
|
This alert is our best guess at which actuator is problematic, but this could be incorrect.
|
Positions differ by 5 degrees and the lower rear actuator has a lower absolute velocity than the front.
|
Position differences could indicate damaged, miswired, or unplugged actuators
|
No
|
|
|
The Falcon Door Ultra-Sonic Sensor (USS) Electronic Control Unit (ECU) has experienced an internal error.
|
An internal error was detected in the USS ECU.
|
An internal error could result in intermittent or total loss of functionality of the USS.
|
No
|