Alerts
Loading...
| Signal Name | Description | Condition | Impact |
|---|---|---|---|
|
Not Available
|
Unsuccessful communication with NVRAM.
|
These are the repercussions of the alert being set
|
|
|
Not Available
|
NVRAM detected as corrupted.
|
These are the repercussions of the alert being set
|
|
|
Not Available
|
Flash CRC is corrupted.
|
These are the repercussions of the alert being set
|
|
|
BCFDM_w036_InteriorSwitch
|
Switch is active for 30s continuously or is disconnected
|
Release cannot be used to trigger door motion until fault is cleared
|
|
|
Check alertLog for more information. If resultingState is CLOSED_BRAKE, the latch's OPEN switch may be disconnected. If previousState is OPENED_BRAKE, the latch's switches and release motor may be all disconnected.
|
PFD transitions from LATCH_OPENING to CLOSED_BRAKE or OPENED_BRAKE
|
PFD cannot open automatically
|
|
|
latch feedback switches are most likely harnessed incorrectly.
|
OPEN switch is active and AJAR switch is not active
|
Door latch status is incorrectly reported and PFD operation becomes erratic
|
|
|
The linkage may have become detached at the ball joint. This alert is only present in factory mode.
|
A possible issue with the PFD acutator linkage was detected
|
The door shuts off all powered operation until closed and latched
|
|
|
The door motor brake is not calibrated and using default values.
|
Door motor brake has no calibration data and is using default values.
|
The door motor brake might not function as expected. Use Service action 'Write Actuator Brake Calibration' to add it.
|
|
|
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
|
setcondition
|
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
|
A signal is received 10% out of timing 3 times in a row.
|
These are the repercussions of the alert being set
|
|
|
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.
|
|
|
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.
|
|
|
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
|
|
|
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 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
|
setcondition
|
These are the repercussions of the alert being set
|