Code Details
| Display code | Bendix EC-60 UDS 98 / SPN 1808 FMI 9 |
|---|---|
| SPN | 1808 |
| FMI | 9 |
| OEM code | Bendix UDS 98, Bendix Blink 22-05, J1587 103-09 |
| Manufacturer | Bendix |
| System | ABS / ATC / ESP |
| Component | J1939 / CAN communication |
| 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 is not receiving CAN messages from the yaw rate sensor within the expected time window. The YRS transmits its measurements over a dedicated sensor CAN bus to the EC-60; a timeout means that communication link is broken or the sensor has stopped transmitting. All ESP yaw-correction functions that depend on real-time yaw rate data are suspended until communication resumes.
The Bendix EC-60 table maps UDS code 98, blink code 22-05, J1587 103-09, and J1939 SPN 1808 FMI 9 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
- ESP/stability lamp on
- ESP yaw-correction suspended — no real-time yaw data reaching the EC-60
- ABS and ATC continue to function normally through their own signal paths
- Other sensor codes (SAS, LAS) may appear simultaneously if they share a supply or CAN segment with the YRS
- Code is typically persistent until communication is physically restored
Possible Causes
Possible causes may include the items below. The list is not a parts diagnosis.
- CAN wire between YRS and EC-60 damaged, cut, or corroded — the sensor has no way to transmit without this link
- YRS supply voltage or ground fault — a sensor without power cannot transmit on any bus
- Corroded or partially disconnected YRS connector that is breaking the CAN path
- Failed YRS CAN transceiver — the sensor may be powered but its communication circuit is no longer functioning
- Another fault on the sensor CAN segment loading the bus and blocking the YRS messages from reaching the EC-60
First Checks
- Inspect the YRS connector and CAN wiring for damage, corrosion, or disconnected pins — a broken CAN wire is the most common cause of a timeout.
- Measure supply voltage and ground at the YRS connector with ignition on; no power means no CAN output regardless of sensor condition.
- If accessible, check resistance between CAN High and CAN Low at the YRS connector; values far from 60 Ω indicate a missing termination or bus fault.
- If multiple sensor codes appeared at the same time, check for a shared supply or backbone wiring fault before diagnosing each sensor individually.
- After restoring the physical connection, clear codes and confirm the EC-60 shows the YRS as active in Bendix ACOM live data.
Can I Keep Driving?
A stability sensor fault (yaw rate, steering angle, or lateral acceleration) disables ESP stability intervention while leaving ABS and ATC intact. The vehicle handles as it would without electronic stability control. Drive with that in mind — cornering, evasive maneuvers, and braking on slippery surfaces carry a higher risk. Stability sensor faults should be addressed before returning the vehicle to regular line-haul or severe-weather service.
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 the YRS on the same CAN network as the engine and transmission?
Typically no. The YRS uses a dedicated sensor CAN bus separate from the main J1939 vehicle network. A fault on the sensor CAN bus does not directly cause J1939 communication codes on other vehicle modules.
Can a failed CAN termination resistor cause a timeout?
A missing or open termination resistor raises bus impedance and can cause communication errors or complete loss of a CAN segment, including sensor timeouts. If resistance between CAN Hi and CAN Lo measures well above 60 Ω with both terminations in place, check the terminator condition.
If the timeout clears itself briefly and comes back, is that useful information?
Yes. An intermittent timeout that self-clears usually points to a marginal connector or harness that briefly drops the CAN connection under vibration or temperature. Locate and permanently correct the intermittent connection before it fails completely.