MyTeslaMate App

Signal Name	Description	Condition	Impact
IDB_a141_DIbrakeTorqueCommandFullTooLow	The Integrated Dynamic Brake (IDB) has received a DI_brakeTorqueCommandFull brake torque request that is too low.	The value of DI_brakeTorqueCommandFull that the IDB received is too low for a given brake pedal position.	The IDB may internally generate and actuate brake torque requests as a function of brake pedal stroke, and actuate External Brake Requests (EBR) in response to DI_brakeTorqueCommand instead of DI_brakeTorqueCommandFull.
IDB_a140_PMbrakePedalCmdQFInvalid	Invalid Pedal Monitor (PM) full torque request signal is received.	The IDB receives the PM_brakePedalCmdQF CAN signal as BRAKE_COMMAND_INVALID, or the PM_state2 CAN message has a checksum, counter, or message length error.	The IDB may internally generate and actuate brake torque requests as a function of brake pedal stroke, and actuate External Brake Requests (EBR) in response to DI_brakeTorqueCommand instead of DI_brakeTorqueCommandFull.
IDB_a139_DIbrakeTorqueCommandFullSNA	The Integrated Dynamic Brake (IDB) receives an invalid DI_brakeTorqueCommandFull.	The IDB receives the DI_brakeTorqueCommandFull CAN signal as Signal Not Available (SNA).	The IDB may internally generate and actuate brake torque requests as a function of brake pedal stroke, and actuate External Brake Requests (EBR) in response to DI_brakeTorqueCommand instead of DI_brakeTorqueCommandFull.
IDB_a138_DIbrakeTorqueCommandAndFlagMismatch	A non-zero DI_brakeTorqueCommand was received while Drive Inverter (DI) DI_brakeTorqueRequestActive is 0.	The IDB receives a non-zero DI_brakeTorqueCommand while the DI_brakeTorqueRequestActive Controller Area Network (CAN) signal is INACTIVE.	The IDB may not respond to brake torque requested in DI_brakeTorqueCommand.
IDB_a137_VCLEFTcdpRequestInvalid	The Controlled Deceleration via Parking brake (CDP) request is invalid.	The IDB recieves the VCLEFT_cdpRequestState CAN signal as EPB_CDP_REQUEST_INVALID for longer than 1 second.	The IDB may not generate brake pressure in response to a request to shift to park while the vehicle is in motion.
IDB_a136_RCUptsCalMissing	The Redundant Control Unit (RCU) pedal travel sensor offset has not been calibrated.	The RCU external pedal travel sensor is not calibrated.	There may be an issue with the transmitting Electronic Control Unit (ECU).
IDB_a135_DIbrakeCommandChecksum	Drive Inverter (DI) brake command message DI_brakeCommand checksum is incorrect.	The IDB receives the DI_brakeCommand CAN message with incorrect CRC for longer than 100 milliseconds.	The IDB may internally generate and actuate brake torque requests as a function of brake pedal stroke, and actuate External Brake Requests (EBR) in response to DI_brakeTorqueCommand instead of DI_brakeTorqueCommandFull.
IDB_a134_DIbrakeCommandCounter	Drive Inverter (DI) brake command message DI_brakeCommand counter is incorrect.	The IDB receives the DI_brakeCommand CAN message with incorrectly incrementing counter for longer than 100 milliseconds.	The IDB may internally generate and actuate brake torque requests as a function of brake pedal stroke, and actuate External Brake Requests (EBR) in response to DI_brakeTorqueCommand instead of DI_brakeTorqueCommandFull.
IDB_a133_DIbrakeCommandDLC	Drive Inverter (DI) brake command message DI_brakeCommand was not received or message length is incorrect.	The IDB did not receive the DI_brakeCommand CAN message for longer than 100 milliseconds or DI_brakeCommand is received with incorrect data length for longer than 100 milliseconds.	The IDB may internally generate and actuate brake torque requests as a function of brake pedal stroke, and actuate External Brake Requests (EBR) in response to DI_brakeTorqueCommand instead of DI_brakeTorqueCommandFull.
MCU_w006_displayFirmwareMismatch	Cluster and center display firmware does not match		-
MCU_u019_ServiceShellActiveConnection	Active Service Connection.		-
MCU_u018_ApTrialExpired	Autopilot Trial Expired.		-
IDB_a132_RCUinputRodStrokeQFInvalid	Invalid Redundant Control Unit (RCU) input rod stroke qualifier (QF) is received.	The IDB recieves the RCU_inputRodPositionQF CAN signals as POSITION_FAULTED for longer than 100 milliseconds, or the RCU_status CAN message had a checksum, counter, or message length error.	There may be an issue with the transmitting Electronic Control Unit (ECU).
IDB_a130_DIfullTorqueRequestInvalid	Invalid Pedal Monitor (PM) PM_state2 message or Drive Inverter (DI) DI_brakeCommand message received.	The IDB did not receive the PM_state2 CAN message for more than 200 milliseconds or DI_brakeCommand message for more than 100 milliseconds, had a checksum, counter, or message length error, or had signals transmitted as invalid.	The IDB may internally generate and actuate brake torque requests as a function of brake pedal stroke, and actuate External Brake Requests (EBR) in response to DI_brakeTorqueCommand instead of DI_brakeTorqueCommandFull.
IDB_a129_RCUinputRodStrokeInvalid	Invalid Redundant Control Unit (RCU) input rod stroke signal is received.	The Integrated Dynamic Brake (IDB) receives the RCU_inputRodPosition signal as Signal Not Available (SNA) for longer than 100 milliseconds.	There may be an issue with the transmitting Electronic Control Unit (ECU).
IDB_a127_brakeFluidLevelInvalid	Brake fluid level signal measured by the Integrated Dynamic Brake (IDB) is invalid.	The brake fluid level sensor (IDB connector pins 20, 38) is detected to be disconnected for over 5 seconds.	Brake Traction Control (BTC), Vehicle Dynamics Control (VDC), Controlled Deceleration via Parking brake (CDP), Brake Disc Wipe (BDW), and External Brake Request (EBR) may be unavailable. The IDB may be unable to monitor brake fluid level. The vehicle should be driven with extreme caution.
IDB_a126_DItorqueRequestInvalid	Invalid Pedal Monitor (PM) PM_state2 message or Drive Inverter (DI) DI_chassisControl message received.	The PM_state2 or DI_chassiControl CAN messages were not received by the IDB for longer than 200 milliseconds, had a checksum, counter, or message length error, or had signals transmitted as invalid.	The IDB may not respond to brake torque requested in DI_brakeTorqueCommand.
IDB_a125_PMvdcCmdStateInvalid	Invalid Pedal Monitor (PM) Vehicle Dynamics Control (VDC) signal is received.	The IDB receives the PM_vdcCmdState CAN signal as COMMAND_INVALID, or the PM_state2 CAN message has a checksum, counter, or message length error.	The IDB may not respond to DI commands to build brake torque to control vehicle dynamics or wheel spin. The vehicle should be driven with extreme caution.
IDB_a124_VCFRONTtempInvalid	Invalid Vehicle Controller Front (VCFRONT) tempAmbient signal is received.	The Integrated Dynamic Brake (IDB) receives the VCFRONT_tempAmbient CAN signal as Signal Not Available (SNA) for longer than 5 seconds, or the VCFRONT_sensors CAN message has a checksum, counter, or message length error.	There may be an issue with the transmitting Electronic Control Unit (ECU).
IDB_a123_DIRtorqueCommandInvalid	Invalid Drive Inverter Rear (DIR) torque command signal is received.	The Integrated Dynamic Brake (IDB) receives the DIR_torqueCommand CAN signal as Signal Not Available (SNA) for longer than 100 milliseconds, or the DIR_torque CAN message has a checksum, counter, or message length error.	There may be an issue with the transmitting Electronic Control Unit (ECU).

IDB_a141_DIbrakeTorqueCommandFullTooLow

The Integrated Dynamic Brake (IDB) has received a DI_brakeTorqueCommandFull brake torque request that is too low.

The value of DI_brakeTorqueCommandFull that the IDB received is too low for a given brake pedal position.

The IDB may internally generate and actuate brake torque requests as a function of brake pedal stroke, and actuate External Brake Requests (EBR) in response to DI_brakeTorqueCommand instead of DI_brakeTorqueCommandFull.

IDB_a140_PMbrakePedalCmdQFInvalid

Invalid Pedal Monitor (PM) full torque request signal is received.

The IDB receives the PM_brakePedalCmdQF CAN signal as BRAKE_COMMAND_INVALID, or the PM_state2 CAN message has a checksum, counter, or message length error.

The IDB may internally generate and actuate brake torque requests as a function of brake pedal stroke, and actuate External Brake Requests (EBR) in response to DI_brakeTorqueCommand instead of DI_brakeTorqueCommandFull.

IDB_a139_DIbrakeTorqueCommandFullSNA

The Integrated Dynamic Brake (IDB) receives an invalid DI_brakeTorqueCommandFull.

The IDB receives the DI_brakeTorqueCommandFull CAN signal as Signal Not Available (SNA).

The IDB may internally generate and actuate brake torque requests as a function of brake pedal stroke, and actuate External Brake Requests (EBR) in response to DI_brakeTorqueCommand instead of DI_brakeTorqueCommandFull.

IDB_a138_DIbrakeTorqueCommandAndFlagMismatch

A non-zero DI_brakeTorqueCommand was received while Drive Inverter (DI) DI_brakeTorqueRequestActive is 0.

The IDB receives a non-zero DI_brakeTorqueCommand while the DI_brakeTorqueRequestActive Controller Area Network (CAN) signal is INACTIVE.

The IDB may not respond to brake torque requested in DI_brakeTorqueCommand.

IDB_a137_VCLEFTcdpRequestInvalid

The Controlled Deceleration via Parking brake (CDP) request is invalid.

The IDB recieves the VCLEFT_cdpRequestState CAN signal as EPB_CDP_REQUEST_INVALID for longer than 1 second.

The IDB may not generate brake pressure in response to a request to shift to park while the vehicle is in motion.

IDB_a136_RCUptsCalMissing

The Redundant Control Unit (RCU) pedal travel sensor offset has not been calibrated.

The RCU external pedal travel sensor is not calibrated.

There may be an issue with the transmitting Electronic Control Unit (ECU).

IDB_a135_DIbrakeCommandChecksum

Drive Inverter (DI) brake command message DI_brakeCommand checksum is incorrect.

The IDB receives the DI_brakeCommand CAN message with incorrect CRC for longer than 100 milliseconds.

The IDB may internally generate and actuate brake torque requests as a function of brake pedal stroke, and actuate External Brake Requests (EBR) in response to DI_brakeTorqueCommand instead of DI_brakeTorqueCommandFull.

IDB_a134_DIbrakeCommandCounter

Drive Inverter (DI) brake command message DI_brakeCommand counter is incorrect.

The IDB receives the DI_brakeCommand CAN message with incorrectly incrementing counter for longer than 100 milliseconds.

The IDB may internally generate and actuate brake torque requests as a function of brake pedal stroke, and actuate External Brake Requests (EBR) in response to DI_brakeTorqueCommand instead of DI_brakeTorqueCommandFull.

IDB_a133_DIbrakeCommandDLC

Drive Inverter (DI) brake command message DI_brakeCommand was not received or message length is incorrect.

The IDB did not receive the DI_brakeCommand CAN message for longer than 100 milliseconds or DI_brakeCommand is received with incorrect data length for longer than 100 milliseconds.

The IDB may internally generate and actuate brake torque requests as a function of brake pedal stroke, and actuate External Brake Requests (EBR) in response to DI_brakeTorqueCommand instead of DI_brakeTorqueCommandFull.

MCU_w006_displayFirmwareMismatch

Cluster and center display firmware does not match

-

MCU_u019_ServiceShellActiveConnection

Active Service Connection.

-

MCU_u018_ApTrialExpired

Autopilot Trial Expired.

-

IDB_a132_RCUinputRodStrokeQFInvalid

Invalid Redundant Control Unit (RCU) input rod stroke qualifier (QF) is received.

The IDB recieves the RCU_inputRodPositionQF CAN signals as POSITION_FAULTED for longer than 100 milliseconds, or the RCU_status CAN message had a checksum, counter, or message length error.

There may be an issue with the transmitting Electronic Control Unit (ECU).

IDB_a130_DIfullTorqueRequestInvalid

Invalid Pedal Monitor (PM) PM_state2 message or Drive Inverter (DI) DI_brakeCommand message received.

The IDB did not receive the PM_state2 CAN message for more than 200 milliseconds or DI_brakeCommand message for more than 100 milliseconds, had a checksum, counter, or message length error, or had signals transmitted as invalid.

The IDB may internally generate and actuate brake torque requests as a function of brake pedal stroke, and actuate External Brake Requests (EBR) in response to DI_brakeTorqueCommand instead of DI_brakeTorqueCommandFull.

IDB_a129_RCUinputRodStrokeInvalid

Invalid Redundant Control Unit (RCU) input rod stroke signal is received.

The Integrated Dynamic Brake (IDB) receives the RCU_inputRodPosition signal as Signal Not Available (SNA) for longer than 100 milliseconds.

There may be an issue with the transmitting Electronic Control Unit (ECU).

IDB_a127_brakeFluidLevelInvalid

Brake fluid level signal measured by the Integrated Dynamic Brake (IDB) is invalid.

The brake fluid level sensor (IDB connector pins 20, 38) is detected to be disconnected for over 5 seconds.

Brake Traction Control (BTC), Vehicle Dynamics Control (VDC), Controlled Deceleration via Parking brake (CDP), Brake Disc Wipe (BDW), and External Brake Request (EBR) may be unavailable. The IDB may be unable to monitor brake fluid level. The vehicle should be driven with extreme caution.

IDB_a126_DItorqueRequestInvalid

Invalid Pedal Monitor (PM) PM_state2 message or Drive Inverter (DI) DI_chassisControl message received.

The PM_state2 or DI_chassiControl CAN messages were not received by the IDB for longer than 200 milliseconds, had a checksum, counter, or message length error, or had signals transmitted as invalid.

The IDB may not respond to brake torque requested in DI_brakeTorqueCommand.

IDB_a125_PMvdcCmdStateInvalid

Invalid Pedal Monitor (PM) Vehicle Dynamics Control (VDC) signal is received.

The IDB receives the PM_vdcCmdState CAN signal as COMMAND_INVALID, or the PM_state2 CAN message has a checksum, counter, or message length error.

The IDB may not respond to DI commands to build brake torque to control vehicle dynamics or wheel spin. The vehicle should be driven with extreme caution.

IDB_a124_VCFRONTtempInvalid

Invalid Vehicle Controller Front (VCFRONT) tempAmbient signal is received.

The Integrated Dynamic Brake (IDB) receives the VCFRONT_tempAmbient CAN signal as Signal Not Available (SNA) for longer than 5 seconds, or the VCFRONT_sensors CAN message has a checksum, counter, or message length error.

There may be an issue with the transmitting Electronic Control Unit (ECU).

IDB_a123_DIRtorqueCommandInvalid

Invalid Drive Inverter Rear (DIR) torque command signal is received.

The Integrated Dynamic Brake (IDB) receives the DIR_torqueCommand CAN signal as Signal Not Available (SNA) for longer than 100 milliseconds, or the DIR_torque CAN message has a checksum, counter, or message length error.

There may be an issue with the transmitting Electronic Control Unit (ECU).

Alerts

Alerts