Alerts

Alerts

Signal Name Description Condition Impact
One or more expected Controller Area Network (CAN) messages from the Body Controller - Front Driver Door (BCFDM) electronic control unit (ECU) was not received. The front driver side door may not function as expected.
An expected CAN message from the Body Controller - Front Driver Door (BCFDM) electronic control unit (ECU) has not been received within the expected timeout, or the message drop rate is too high while the BCFDM is CAN active. The BCFDM is considered CAN active when VCFRONT_vehGoToSleep is 0.
The front driver side door may not function as expected.
One or more of the messages the vehicle controller receives periodically from the electromechanical body controller for the driver side Falcon door (BCFALCD) is not received, indicating the BCFALCD may be unavailable (MIA).
One or more of the expected messages from the BCFALCD is not received.
The driver side falcon door may not function as expected.
One or more of the messages the vehicle controller receives periodically from the rear right door controller (VCDOORRR) is not received, indicating the VCDOORRR may be unavailable (MIA).
The vehicle controller does not receive one or more of the expected messages from the VCDOORRR within the expected time frame.
Vehicle functions that depend on the VCDOORRR may be unavailable or may not function as expected.
One or more expected Controller Area Network (CAN) messages from the Body Controller - Falcon EM Controller - Passenger Side (BCFALCP) electronic control unit (ECU) was not received. The passenger side Falcon door may not function as expected.
An expected CAN message from the Body Controller - Falcon EM Controller - Passenger Side (BCFALCP) electronic control unit (ECU) has not been received within the expected timeout, or the message drop rate is too high while the BCFALCP is CAN active. The BCFALCP is considered CAN active when VCFRONT_vehGoToSleep is 0.
The passenger side Falcon door may not function as expected.
One or more expected Controller Area Network (CAN) messages from the Body Controller - Front Passenger Door (BCFPM) electronic control unit (ECU) was not received. The front passenger side door may not function as expected.
An expected CAN message from the Body Controller - Front Passenger Door (BCFPM) electronic control unit (ECU) has not been received within the expected timeout, or the message drop rate is too high while the BCFPM is CAN active. The ECU is considered CAN active when VCFRONT_vehGoToSleep is 0.
The front passenger side door may not function as expected.
One or more of the expected CAN messages from the Etherloop Generalized Gateway Rear (Core 0) were not received, indicating the EGGREAR ECU may be unavailable (MIA).
The local ECU does not receive one or more of the expected messages from the EGGREAR within the expected time frame.
Vehicle functions that depend on the EGGREAR may be unavailable or may not function as expected.
One or more of the messages the vehicle controller receives periodically from the rear passenger door body controller (BCRPM) is not received, indicating the BCRPM may be unavailable (MIA).
One or more of the expected messages from the BCRPM is not received.
The rear passenger side falcon door may not function as expected.
One or more of the expected controller area network (CAN) messages from the Autopilot Primary (APP) were not received.
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.
An issue is indicated from the non-volatile memory manager.
Non-volatile memory misconfiguration or underlying flash/filesystem error.
Non-volatile memory records may be incorrect or missing.
A large voltage drop is detected in the input power to the vehicle controller, indicating the resistance on the input power feed to the vehicle controller is higher than 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 condition affecting switch functionality has been detected.
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.
Warns if the processor has experienced a reset due to power loss.
Sudden power loss.
Controller is MIA for some time.
One or more of the messages the vehicle controller receives periodically from the 2nd row center seat body controller (BCS2C) is not received, indicating the BCS2C may be unavailable (MIA).
One or more of the expected messages from the BCS2C is not received.
2nd row center seat features depending on BCS2C functionality, including seat buckle and heating pad, may be limited or unavailable.
The current measurement reported by the LV battery (LVBMS_packCurrent) does not match the current sensor on the vehicle controller LV battery feed (IBSCurrent).
The absolute value of current difference between LVBMS_packCurrent and IBSCurrent exceeds nominal expectations
Incorrect battery current data being used, resulting in sub-optimal LV battery management.
The front trunk (frunk) latch has been disabled. The frunk latch enable routine must be run to restore latch function.
The vehicle frunk latch has been set to disabled in the controller's non-volatile memory (NVM).
No frunk latch movement or function, even if frunk latch is connected.
One or more of the expected CAN messages from APP were not received.
A message the local ECU expects to receive from the APP ECU hasn't been received within the expected timeout or the drop rate is too high while the APP is CAN active. The ECU is considered CAN active when VCFRONT_chGoToSleep is 0.
Autopilot functionality may be missing.
Warns if the processor has experienced a reset due to watchdog reset.
A watchdog (external or internal) was not serviced in time.
Controller is MIA for some time.
The low voltage (LV) battery internal protection transistor (MOSFET) self test has not yet completed.
The LV battery internal protection transistor (MOSFET) self test has not yet completed, potentially because a condition or combination of conditions prevents it from running. Alert log signal data should provide more information.
Vehicle is unable to shift out of Park (P) until the LV battery internal protection transistor (MOSFET) self test completes or times out without completing. If the self test cannot complete and confirm LV battery MOSFET functionality, the LV battery may be unable to support vehicle electrical systems or to recharge via the power conversion system (PCS).
The vehicle controller detects the low voltage (LV) battery internal protection transistor (MOSFET) self test has failed, indicating one or more conditions affecting MOSFET functionality.
Any part of the LV battery internal protection transistor (MOSFET) self test reports a failure. Alert log signal data should provide more information.
LV battery internal protection transistor (MOSFET) functionality is not confirmed. The LV battery may be unable to support vehicle electrical systems or to recharge via the power conversion system (PCS).
The Thigh Support Motor encoder unexpectedly stalls.
Current draw exceeds 70% of the stall limit, and the encoder does not move for 100ms.
The seat motor encoder may increment incorrectly if an obstruction is encountered