Alerts
Loading...
| Signal Name | Description | Condition | Impact | Important |
|---|---|---|---|---|
|
Not Available
|
The Freescale HSD has been returned bad data on the MISO line from the microprocessor more than 10 times in a row.
|
HSD outputs could toggle endlessly.
|
No
|
|
|
Not Available
|
BDY_RCM_collision did not match BDY_BCCEN_collision
|
If any crash signal is active, crash behavior is active
|
No
|
|
|
Pitch will default to uncalibrated in new ECUs and can be set uncalibrated by UDS routine. AlertLog contains uncalibrated reason.
|
Pitch position calibration is checked and found to be uncalibrated at ECU power cycle, wake from sleep, etc
|
Pitch motor will stop moving
|
No
|
|
|
none
|
Set when the user attempts to move pitch in both directions and the seat does not move in response
|
Seat movement is stopped
|
No
|
|
|
Seat occupant was detected outside the comfort zone causing Easy Entry Latch to be unable achieve full forward engagement.
|
Seat occupant was detected outside the comfort zone causing Easy Entry Latch to be unable achieve full forward engagement while in Drive or Reverse mode.
|
The safety of individuals utilizing the seats may be compromised due to incorrect configurations.
|
No
|
|
|
None
|
The car is not in Park AND backrest is in the comfort zone AND the track is unlatched
|
Occupant safety is impacted
|
No
|
|
|
None
|
The drive rail is on AND backrest is in the comfort zone AND the track is unlatched
|
Occupant safety is impacted
|
No
|
|
|
BCS2L_w055_2RCSeatHeatOverCurr
|
|
-
|
No
|
|
|
None
|
The car is in a moving gear, and the track is unlatched
|
Occupant safety is impacted
|
No
|
|
|
Not Available
|
Vehicle did not unlock after crash.
|
These are the repercussions of the alert being set
|
No
|
|
|
Production vehicle should not have Debug Jumper in place. Remove jumper from ECU.
|
ECU Debug Jumper is set.
|
ECU Debug Jumper will disable SBC watchdog, preventing external watchdog reset protection.
|
No
|
|
|
Log contains CPU load for each task.
|
CPU load exceeds 80%.
|
High CPU load can indicate ineffecient code.
|
No
|
|
|
Not Available
|
FILL_THIS_OUT
|
FILL_THIS_OUT
|
No
|
|
|
Not Available
|
FILL_THIS_OUT
|
FILL_THIS_OUT
|
No
|
|
|
Not Available
|
FILL_THIS_OUT
|
FILL_THIS_OUT
|
No
|
|
|
Not Available
|
FILL_THIS_OUT
|
FILL_THIS_OUT
|
No
|
|
|
Not Available
|
FILL_THIS_OUT
|
FILL_THIS_OUT
|
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
|
|
|
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
|