Code Details
| Display code | Bendix EC-60 UDS 141 / SPN 629 FMI 12 |
|---|---|
| SPN | 629 |
| FMI | 12 |
| OEM code | Bendix UDS 141, Bendix Blink 13-25, J1587 254-12 |
| Manufacturer | Bendix |
| System | ABS / ATC / ESP |
| Component | ABS electronic control unit |
| Source address | Unknown or not applicable |
| Severity | medium |
| Review status | ai source checked |
| Source confidence | high |
| Last reviewed | 2026-03-04 |
Plain-English Meaning
The EC-60 detected a VIN mismatch — the vehicle identification number stored in the module does not match what it received from another J1939 controller. This points to a module replacement or network data discrepancy, not a hardware failure.
The Bendix EC-60 table maps UDS code 141, blink code 13-25, J1587 254-12, and J1939 SPN 629 FMI 12 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/or ATC/ESP lamp on after module replacement
- Code present without any brake complaint
- All other ABS functions may operate normally
- May appear alongside other post-replacement configuration codes
Possible Causes
Possible causes may include the items below. The list is not a parts diagnosis.
- Replacement EC-60 installed with a different VIN (sourced from another vehicle)
- VIN not programmed or transferred during the module swap
- J1939 network source (cluster, body controller) broadcasting an unexpected VIN
- Module reprogrammed with incorrect VIN data
First Checks
- Connect Bendix ACOM and read the VIN stored in the EC-60; compare to the vehicle VIN on the door jamb.
- If they differ, program the correct VIN into the EC-60 using ACOM.
- Confirm the J1939 source broadcasting the VIN (typically instrument cluster) also has the correct VIN.
- After correcting, clear all codes and confirm no other post-replacement faults remain.
- Document the module serial number and VIN change per fleet maintenance requirements.
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
Sources
- Bendix EC-60 ABS/ATC/ESP Controllers Service Data SD-13-4869 Bendix Commercial Vehicle Systems, hosted in NHTSA Manufacturer Communications · oem · accessed 2026-05-05 · confidence high
Source: Bendix Commercial Vehicle Systems, hosted in NHTSA Manufacturer Communications, Bendix EC-60 ABS/ATC/ESP Controllers Service Data SD-13-4869. This page paraphrases factual fields only and is not a substitute for the original document.
Open source - Bendix EC-60 Advanced Controllers Service Data SD-13-4869 Bendix Commercial Vehicle Systems, hosted in NHTSA Manufacturer Communications · oem · accessed 2026-05-05 · confidence high
Source: Bendix Commercial Vehicle Systems, hosted in NHTSA Manufacturer Communications, Bendix EC-60 Advanced Controllers Service Data SD-13-4869. This page paraphrases factual fields only and is not a substitute for the original document.
Open source
FAQ
Is Bendix EC-60 UDS 141 / SPN 629 FMI 12 a safety-critical fault?
It is flagged by the system but does not indicate a hardware failure. VIN mismatch is an administrative/configuration issue following a module swap. Address it to keep diagnostic records accurate.
Can VIN be programmed without special tools?
Bendix ACOM or compatible OEM software is required to write VIN data to the EC-60. A standard scan tool can read DTCs but cannot write configuration parameters.
Why does the EC-60 store the VIN?
The VIN is used to confirm the module is in the correct vehicle — relevant for warranty tracking, recall compliance, and ensuring configuration parameters match the specific build.