Bendix EC-60 UDS 30 / SPN 630 FMI 13 — ECU (1E)

Code Details

Plain-English Meaning

The EC-60 detected a calibration data or EEPROM integrity fault (ECU (1E)). The EEPROM stores the module's configuration — axle layout, sensor types, tire parameters, and feature calibrations. The module's own self-test found that stored configuration data may be corrupt or unreadable. Unlike a runtime processor fault, an EEPROM fault directly threatens the EC-60's stored identity: if configuration data cannot be read reliably, the module may revert to default parameters that do not match the vehicle.

The Bendix EC-60 table maps UDS code 30, blink code 13-22, J1587 253-13, and J1939 SPN 630 FMI 13 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

• ABS and ATC/ESP warning lamps on — full system disablement
• Code is typically persistent, not intermittent
• All external circuits (sensors, valves) test normally
• Configuration parameters may revert to defaults if EEPROM data is unreadable
• Code may appear after a module power interruption or voltage spike during programming

Possible Causes

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

• Power interruption or voltage spike during an EC-60 calibration or configuration write
• EEPROM worn past write-cycle limits on a high-mileage or frequently reprogrammed module
• EC-60 exposed to temperature extremes beyond specification during or after a write cycle
• EMI event that corrupted the EEPROM contents
• Internal EC-60 hardware degradation of the non-volatile memory circuitry

First Checks

• Connect Bendix ACOM and attempt to read the EC-60 configuration — if ACOM cannot read the stored parameters, EEPROM corruption is confirmed.
• Review the service history for power events, voltage spikes, or programming sessions that were interrupted before completion.
• Clear the code and check whether the configuration data remains intact across the next two power cycles.
• Check for Bendix TSBs for the specific UDS code — some EEPROM fault codes have software recovery procedures.
• If configuration cannot be restored via ACOM, EC-60 replacement is indicated; document the full configuration before removal.

Can I Keep Driving?

An ECU internal fault typically disables all ABS, ATC, and ESP functions until the root cause is corrected and the code is cleared. Normal base braking continues. ECU codes do not resolve by themselves — clearing without diagnosis will result in the code returning. Stable power supply quality is the first thing to verify before more extensive diagnosis.

Related Lookup Pages

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