Bendix EC-60 UDS 54 / SPN 639 FMI 2 — Invalid Data from Transmission

Code Details

Plain-English Meaning

The EC-60 is not receiving valid J1939 data from the transmission controller (ETC). The EC-60 uses transmission gear and output shaft speed data to calculate effective vehicle speed ratio and to coordinate ABS deceleration requests with the transmission control. Loss of transmission data can cause the EC-60 to use less accurate vehicle speed estimates. Without the expected data, affected coordination functions are suspended while basic ABS wheel-speed-based control continues.

The Bendix EC-60 table maps UDS code 54, blink code 11-10, J1587 231-02, and J1939 SPN 639 FMI 2 to this ABS/ATC/ESP diagnostic entry. The Bendix source indicates an ABS and/or ATC/ESP warning lamp can be on for this entry. The EC-60 continuously monitors wheel speed sensor circuits, pressure modulation valve output drivers, supply voltage quality, J1939 network data from the engine and transmission controllers, and internal self-diagnostic routines. When any monitored value falls outside its acceptable range — or a circuit does not respond as the module expects — the EC-60 logs a diagnostic trouble code and may disable the affected ABS, ATC, or ESP function. Bendix ACOM Pro or a compatible diagnostic interface is the required tool for reading live sensor data, running actuator tests, performing calibrations, clearing latched codes, and adjusting EC-60 configuration parameters. Generic J1939 scan tools can read the SPN/FMI but cannot access EC-60-specific live data screens or configuration settings.

Common Symptoms

• ATC/ESP lamp on; affected coordination functions degraded or disabled
• The source module (transmission controller (ETC)) may also be logging communication faults
• May correlate with recent wiring work, module replacement, or CAN connector service
• Condition may be intermittent if the source module resets or the CAN connection is marginal
• Other modules sharing the J1939 backbone may show related communication codes

Possible Causes

Possible causes may include the items below. The list is not a parts diagnosis.

• transmission controller (ETC) offline, not transmitting, or sending out-of-range data on J1939
• Damaged or high-resistance CAN segment between EC-60 and the J1939 backbone junction
• Fault in the transmission controller (ETC) itself — power failure, software crash, or hardware fault
• Incorrect J1939 source address or configuration after a module replacement
• Corroded CAN connector at the EC-60, at the transmission controller (ETC), or at a backbone T-junction

First Checks

• Connect Bendix ACOM or a J1939-capable tool and verify whether the transmission controller (ETC) is visible and active on the bus.
• Read fault codes from the transmission controller (ETC) directly — a fault there often explains why it stopped transmitting.
• Check CAN bus wiring between the EC-60 and the backbone: inspect connectors for corrosion, measure wire resistance for shorts or opens.
• Verify the transmission controller (ETC) has correct power, ground, and has not been recently replaced with an unconfigured unit.
• After resolving the source module issue, clear EC-60 codes and confirm J1939 communication is restored via Bendix ACOM.

Can I Keep Driving?

J1939 communication faults typically disable ATC and ESP coordination functions while ABS wheel-speed monitoring continues. Normal base braking is unaffected. Multiple simultaneous ABS and engine/transmission warning lamps may appear together when a network-level fault is present — in that case, investigate the network before addressing individual module codes.

Related Lookup Pages

• SPN 639 topic page
• FMI 2 explanation
• Bendix manufacturer hub
• ABS / ATC / ESP fault codes
• ABS Light symptom page
• Brake Warning Light symptom page
• Search this code