CAN Bus “No ECU Found” Caused by One Controller
Table of Contents
In multi-node CAN networks, communication failures are often misdiagnosed as wiring issues or configuration errors. However, there is a more disruptive failure mode: an active disturbance, where a single faulty node prevents the CAN bus from reaching a valid idle state and renders the entire network invisible to diagnostic tools.
This article explores a real-world case study, detailing the diagnostic steps used to isolate a rogue node and highlighting the importance of standard-compliant error handling in industrial controllers.
1. The Field Symptom: When All ECUs Disappear
The scenario began on a standard test bench.
The Setup:
A functional CAN network with a diagnostic service tool and proper 120 Ω termination.
The Trigger:
As soon as one specific suspect controller was connected to the bus, the diagnostic tool immediately reported “No ECU Found.”
The Anomaly:
It wasn’t just the suspect controller that was missing — every other known-good node on the bus disappeared simultaneously.
This behavior immediately ruled out simple baud-rate mismatches. A misconfigured node usually just stays quiet; it does not mute its neighbors.
2. Technical Analysis: Active Interference vs. Passive Absence
When a network scan fails entirely, it indicates that the CAN bus cannot return to a valid recessive idle condition. Instead of a passive or silent failure, the suspect node was likely causing active interference.
Typical mechanisms include:
Error Frame Flooding
Factory: clean, stable 24V
Mobile: 8–32V range, load dumps, spikes, ripple → requires automotive-grade electronics
Vibration and Shock
Factory equipment is stationary
Vehicles experience constant vibration and impact → connectors and PCBs must be vibration-resistant
Environmental Exposure
Industrial PLCs live in enclosures
Mobile controllers face:
Water/dust (IP67)
Salt spray
Mud
Temperature extremes (-40°C to +85°C)
Communication
Factory: industrial Ethernet
Mobile: CAN, CANopen, J1939 (robust, low wiring cost)
Wiring Architecture
Factory: short, centralized wiring
Mobile: long chassis + distributed hydraulic blocks → ideal for distributed I/O modules
The Five-Step I/O Planning Process
Step 1 — Create a Complete I/O List
Document every signal:
| Module | Signal Name | Type | Notes |
|---|---|---|---|
| Drive | Forward / Reverse | DI | Safety-critical |
| Hydraulics | Main pressure sensor | AI | 0–5V |
| Lighting | Work lights | DO | High-side, 2A |
| Safety | E-stop | DI | Normally-closed, redundant |
| Proportional valve | Boom lift | PWM | Current-controlled 1.5A |
Group signals by function: drive, steering, hydraulics, safety, auxiliary systems.
Step 2 — Select the Communication Method
Joystick
CAN joystick → Less wiring, more diagnostics
Discrete joystick → Requires many DI channels
HMI
CAN or Ethernet depending on model capability
Sensors
Simple sensors → AI
Smart sensors → CAN (with diagnostics)
Actuators
On/off → DO
Proportional valves → PWM or current control
Choosing CAN joysticks can reduce DI count from ~20 to <10.
Step 3 — Estimate Required I/O Capacity
Typical mobile machinery example:
DI: 15–20
DO: 14
AI: 3
PWM: 2 (proportional valves)
CAN: 1–2 (ECU + joystick/HMI/I/O modules)
This varies depending on machine complexity, communication strategy, and safety requirements.
Step 4 — Choose Integrated or Distributed I/O
Integrated I/O controller (all in one)
Best for:
Small machines
Centralized wiring
Lower signal count
Controller + Distributed I/O modules
Best for:
Long chassis vehicles (cranes, fire trucks, sanitation trucks)
Multiple hydraulic zones
Minimizing cable runs
Advantages:
Shorter wiring → fewer failure points
Modules mounted near hydraulic blocks
Easy system expansion
Step 5 — Reserve Expansion Capacity
Recommended:
20–30% spare DI/DO
One extra CAN channel
Extra PWM channels for potential future valves
This prevents costly redesigns when new features are needed.
Common I/O Planning Mistakes to Avoid
Counting only total I/O, not grouping by function
Using industrial PLCs on mobile machines
Noisy analog signals due to poor filtering or cable routing
Incorrect CAN bus termination or star topology
No spare I/O or CAN channels for future expansion
Running sensor cables alongside high-current wires
Poor grounding leading to intermittent failures
No debouncing for DI, causing false triggers
Best Practices for Reliable Mobile I/O Systems
Use shielded cables for analog inputs
Separate sensor wiring from power wiring
Use a linear CAN topology with proper 120-ohm termination
Apply distributed I/O modules to shorten cable runs
Choose controllers with IP67, wide temperature range, EMC protection
Maintain clear signal documentation: wire numbers, channels, connectors
Add software debounce for DI
Test all I/O under real operating conditions: vibration, temperature, load
Conclusion
Effective I/O planning is essential for building reliable mobile machines. A clear signal list, proper communication choices, and attention to wiring, filtering, and CAN topology help ensure long-term stability and easier maintenance.
When a project requires rugged distributed I/O, SonnePower’s IP67 I/O modules — available in multiple channel configurations and designed for harsh mobile environments — can be a practical option. Their wide-voltage support and CAN-based architecture make them suitable for construction, sanitation, and agricultural equipment.