Alerts
Loading...
| Signal Name | Description | Condition | Impact | Important |
|---|---|---|---|---|
|
The Falcon Door Body Controller has detected a falcon door is open and the vehicle speed exceeds 0.5KPH.
|
Falcon doors are detected in an open state while vehicle speeds exceed 0.5KPH.
|
Falcon doors may become damaged.
|
No
|
|
|
BCFALCD_w042_actuator12VFault
|
Door movement with a irregular 12V battery voltage.
|
These are the repercussions of the alert being set
|
No
|
|
|
Not Available
|
NVRAM detected as uninitialized.
|
These are the repercussions of the alert being set
|
No
|
|
|
Not Available
|
Unsuccessful communication with NVRAM.
|
These are the repercussions of the alert being set
|
No
|
|
|
Not Available
|
NVRAM detected as corrupted.
|
These are the repercussions of the alert being set
|
No
|
|
|
Not Available
|
Flash CRC is corrupted.
|
These are the repercussions of the alert being set
|
No
|
|
|
Not Available
|
Any of the signals in message RCM are set.
|
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
|
|
|
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
|
|
|
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
|
|
|
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 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.
|
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
|
|
|
Not Available
|
A signal is received 10% out of timing 3 times in a row.
|
These are the repercussions of the alert being set
|
No
|
|
|
Not Available
|
setcondition
|
These are the repercussions of the alert being set
|
No
|
|
|
The inward-facing Ultrasonic Sensor (USS) located on the left Falcon Door has encountered a hardware failure.
|
Alert log signal data should provide further information on specific condition(s) involved.
|
Malfunctioning hardware in the left Falcon Door's internal ultrasonic sensor can result in intermittent or total loss of functionality of the USS.
|
No
|