Alerts
Loading...
| Signal Name | Description | Condition | Impact |
|---|---|---|---|
|
Not Available
|
The glove box latch did not open or close as intended.
|
These are the repercussions of the alert being set
|
|
|
reseting the controller should fix the issue.
|
Driver side config stored in NVRAM does not match the config sent by GTW
|
controller may have behaviors that correspond with the wrong side of the car
|
|
|
The electrical hardware for the glovebox will disable itself if it encounters an 'overtemperature' or 'overcurrent' condition. If this is a recurring problem, a module replacement may eliminate the issue.
|
The glovebox electrical hardware (High-Side Driver) reports an overtemperature fault
|
The glovebox will not respond for 15 seconds. May eventually lead to a totally inoperative glovebox if triggered consistently over a long period of time.
|
|
|
Motor calibration is usually performed as part of routine 0x170 for BCCEN. The calibration data is stored in the module's non-volatile memory.
|
Rake or reach motor is not uncalibrated
|
Automatic position recall disabled for affected axes, manual adjustment may stop working
|
|
|
Not Available
|
Error in communication.
|
These are the repercussions of the alert being set
|
|
|
Not Available
|
Recall command for a profile that had never been set with a Store command.
|
These are the repercussions of the alert being set
|
|
|
Not Available
|
Error reported from device motor.
|
These are the repercussions of the alert being set
|
|
|
Log contains stack usage for each task.
|
Stack usage exceeds 80% for any task.
|
Stack overflow can occur if there is not enough stack space.
|
|
|
Not Available
|
Rail value does not match GTW request value after 500ms. Rail state is unknown.
|
These are the repercussions of the alert being set
|
|
|
Not Available
|
Rail value does not match GTW request value after 500ms. Rail state is unknown.
|
These are the repercussions of the alert being set
|
|
|
Not Available
|
Flash CRC is corrupted.
|
These are the repercussions of the alert being set
|
|
|
Not Available
|
Any of the signals in message RCM are set.
|
These are the repercussions of the alert being set
|
|
|
None
|
The transponder was used to open car/start car.
|
None. Purely informational. After this alert is set the car will be unlocked or will allow drive rail on (details in alert log)
|
|
|
Version 0.0 or 2.1 will cause the SE on the central controller to lock up in certain scenarios.
|
If the SE version on Central Controller is not the latest one
|
-
|
|
|
Not Available
|
UHF firmware update failure. LF firmware update failure.
|
These are the repercussions of the alert being set
|
|
|
Replace battery on keyfob(s). This alert always clears upon drive rail turn off.
|
Keyfob battery too low, as seen a few seconds after drive rail turns on.
|
Keyfob may be unusable soon.
|
|
|
Not Available
|
NVRAM detected as uninitialized.
|
These are the repercussions of the alert being set
|
|
|
Not Available
|
Switch brake pressed != DI CAN message for 1000ms.
|
could indicate loss of communication with the drive inverter
|
|
|
Not Available
|
The desired state of the rear footwell illumination could not be set, the current state is not the expected one or the brightness adjustment did fail.
|
These are the repercussions of the alert being set
|
|
|
Not Available
|
setcondition
|
These are the repercussions of the alert being set
|