Alerts

A message the local ECU expects to receive from the DIF ECU has not been received within the expected timeout or the drop rate is too high while the DIF is CAN active.

Drive functionality may be missing.

An expected CAN message from the ICR ECU has not been received within the expected timeout, or the CAN message drop rate is too high while the ICR is CAN active.

Intrusion alarm functionality may be missing.

One or more of the expected messages from the PCS ECU is not received.

The vehicle may be unable to charge.

One or more of the expected messages from the TAS ECU is not received.

The air suspension may not function as expected.

The vehicle controller does not receive one or more of the expected messages from the CP ECU within the expected time frame.

Charging may not start or may be interrupted unexpectedly.

One or more of the expected messages from the PM ECU is not received.

Vehicle speed and power may be limited.

If 50% or more of the ECUs the local ECUs listens to are MIA, and the local ECU receives from more than 3 ECUs on this bus. An ECU is MIA if more than 50% of its messages are MIA and that ECU is considered CAN active (see specific ECU's MIA alert for CAN active conditions).

Vehicle functionality may not operate as expected.

One or more of the expected messages from the DIR ECU is not received.

Vehicle speed and power may be limited.

A message the local ECU expects to receive from the iBooster ECU has not been received within the expected timeout or the drop rate is too high while the iBooster is CAN active.

Brake boost functionality may be missing.

One or more of the expected messages from the DIRER is not received.

Vehicle speed and power may be limited.

One or more of the expected messages from the DIREL is not received.

Vehicle speed and power may be limited.

A condition is detected affecting switch functionality. Alert log signal data should provide more information on the switch affected and specific condition.

The switch may not function or may not function as expected.

Estimated resistance on the input power feed to the vehicle controller is higher than expected.

The vehicle controller may be unavailable due to lack of adequate input power, limiting vehicle functionality or making the vehicle inoperable, with at least one other alert specific to that condition present.

A message the local ECU expects to receive from the APP ECU is not received within the expected timeout, or the drop rate is too high while the APP is CAN active.

Autopilot does not operate as expected.

Non-volatile memory misconfiguration or underlying flash/filesystem error.

Non-volatile memory records may be incorrect or missing.

Amplifier 2 reports one or more of its channels is overcurrent.

One or more of the amplifier channels is not operating as expected. Audio will not operate as expected, and the amplifier may be shorted.

The amplifier reports one or more of its channels is overcurrent.

One or more of the amplifier channels is not operating as expected. Audio will not operate as expected, and the amplifier may be shorted.

An amplifier condition is reported on second amp. Alert log signal data should provide more information on the specific condition(s) detected.

Audio quality may decrease.

Etherloop Generalized Gateway (EGG) has detected a condition affecting Etherloop communication.

Loss of communication redundancy or total loss of communication between some electronic control units (ECUs).

The SQI of the EGG clockwise Ethernet link to EGGLEFT is less than 4.

The Ethernet packet loss affects the vehicle's functionality and performance.