Alerts
Loading...
| Signal Name | Description | Condition | Impact |
|---|---|---|---|
|
check occupancy sensor and harness, seat belt sensor and harness, damaged ECU.
|
3rd row detects occupancy sensor is in the faulted or disconnected voltage range
|
Occupant safety is impacted
|
|
|
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
|
|
|
3930 Fault - Under voltage, Overtemperature, Incorrect Logic Levels.
|
Vreg < 8V, Overtemperature > 170 deg C on the A3930,Logic levels below lockout voltage level of 4V
|
If overtemperature, A3930 will continue to drive. If undervoltage or logic fault, motor control will be disabled.
|
|
|
Check for obstacle detected, high current readings, or running into track ends.
|
The track motor reads an unreasonably high or stall current of FILL_THIS_OUT amps
|
FILL_THIS_OUT
|
|
|
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.
|
|
|
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
|
|
|
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
|
|
|
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
|