Alerts
Loading...
| Signal Name | Description | Condition | Impact |
|---|---|---|---|
|
Etherloop Generalized Gateway (EGGLEFT) detects a condition affecting EGGLEFTPRIV CAN bus. Alert log signal data should provide more information on specific condition.
|
Number of CAN transmit or receive errors exceeds 127.
|
EGGLEFT is unable to transmit or receive messages on EGGLEFTPRIV CAN bus, making communication unavailable.
|
|
|
The Electronic Parking Brake (EPB) configuration differs from the EPB configuration reported by Gateway (GTW). The Electronic Parking Brake Monitor (EPBM) expects the configuration from EPB to be valid based on GTW vehicle configuration.
|
5 seconds after boot, the vehicle reports the EPB configuration and GTW vehicle EPB configuration is mismatched.
|
When an inconsistency between GTW and EPB configurations is present, the EPB configuration is used.
|
|
|
The vehicle controller detects one or more loads did not turn off after the self-test commanded them off, or they did not turn on when the self-test commanded them on.
|
One or more loads did not turn off after the self-test commanded them off, or they did not turn on when the self-test commanded them on
|
The vehicle is unable to drive.
|
|
|
Frunk interior emergency release button press has been detected, but the frunk was not opened because vehicle was in motion.
|
Frunk emergency interior release button press detected while the vehicle is in motion.
|
Possible occupant or object inside the frunk pressing the interior release button.
|
|
|
A condition affecting frunk exterior button functionality has been detected.
|
Frunk exterior button voltage is outside its expected range for at least 500 milliseconds, and the frunk exterior button is pressed four times within a 10-second window.
|
The frunk exterior button will not be able to control the frunk.
|
|
|
Fused rail driver or downstream load driver test result stale.
|
Any required fused rail driver or downstream load driver test has not been completed within the last 24h.
|
May not be able to detect fused rail driver or downstream load driver stuck-on condition.
|
|
|
Fused rail driver or downstream load driver cannot be turned off independently.
|
Stuck-on condition (unexpected load or output) is detected on rail driver or any downstream load.
|
Front left seat heater and left frunk strut may be disabled.
|
|
|
The vehicle controller detects an undercurrent condition on the front trunk (or frunk) strut actuator, indicating the 48V rail may be down.
|
Firmware is commanding the frunk strut to actuate but the strut actuator draws less than 50mA for 300ms, and the velocity of the actuator is less than 1 deg/s.
|
The front trunk strut may be unable to actuate, preventing the front trunk from opening or closing.
|
|
|
Steering column up / down motor end stop is not within the expected range.
|
The full range of up / down movement is less than 53mm or greater than 64mm.
|
Calibration may have been unsuccessful. Steering column profile recall may not operate as expected.
|
|
|
Steering column in / out motor end stop is not within the expected range.
|
The full range of in / out movement is less than 117mm or greater than 128mm.
|
Calibration may have been unsuccessful. Steering column profile recall may not operate as expected.
|
|
|
The bridge gate driver experienced a condition affecting its operation.
|
The bridge gate driver reports a condition affecting its operation.
|
Actuators controlled by the bridge gate driver may be inoperative.
|
|
|
One or more loads failed to turn on during the Left Domain Undervoltage Self-Test. Those loads will be inhibited from use in drive.
|
One or more loads failed to turn on during the Left Domain Undervoltage Self-Test.
|
Impacted load(s) will not be usable in drive.
|
|
|
The Left Domain Undervoltage self-test did not pass, as a condition affecting a load on the Left Domain was detected during the self-test.
|
The Left Domain Undervoltage self-test does not succeed.
|
The undervoltage protection circuit may not be functional.
|
|
|
No position change on frunk latch exit, so the encoder has likely stalled
|
No encoder movement was seen after a latch exit
|
The frunk will not be able to actuate open
|
|
|
The frunk stopped moving for an unexpected reason
|
An unexpected frunk stop reason is set
|
Frunk opening/closing actuation will not complete
|
|
|
The frunk has become uncalibrated
|
The frunk latch became closed while opened at an unexpected angle
|
The frunk will not be able to actuate open
|
|
|
The seat track abuse has been detected, maximum number of events per time exceeded
|
The maximum number of operating events per time has been exceeded
|
The seat track motor will be disabled
|
|
|
Seat track motor abuse has been detected, with number of events within 5 minutes required to generate a warning exceeded
|
The number of operating events per time period required to generate a warning for seat track motor abuse has been exceeded
|
The seat track motor will be disabled if operation continues and maximum number of events within 5 minutes is exceeded
|
|
|
The seat has detected that the track motor has exceeded normal operating times
|
The operating time has exceeded 120 seconds within 5 minutes
|
The seat track motor will be disabled
|
|
|
The frunk leader vehicle controller does not have a saved acceleration table, which is required for the sensitive pinch algorithm. Frunk pinch detection will not operate as expected.
|
The frunk leader vehicle controller does not have a saved acceleration table.
|
Frunk pinch detection will not function as expected.
|