Modern tractors, engines and construction machinery rely on CAN-bus networks so electronic controllers can communicate with each other. When the network is disturbed, the machine may show several fault codes at once even though only one wiring, power-supply or controller problem exists.
CAN-bus test points, resistance values, connector pin numbers and controller locations vary by make, model and serial range. Use the correct wiring diagram and diagnostic manual before probing connectors or replacing control units.
1. What Is a CAN Bus?
CAN means Controller Area Network.
It allows several electronic control units to share information over a small number of wires rather than every controller having a separate wire to every sensor or system.
Controllers May Include
- Engine ECU
- Transmission ECU
- Hydraulic controller
- Instrument cluster
- Aftertreatment controller
- Steering controller
- Implement controller
2. Why Communication Faults Can Create Many Codes
If one controller disappears from the network, other controllers may report:
- Lost communication
- Invalid data
- Abnormal update rate
- Missing engine speed
- Missing transmission status
- Sensor data unavailable
This can create a long list of secondary codes from one root cause.
3. Common Communication Code Descriptions
You may see wording such as:
- Lost communication with ECU
- CAN message missing
- Abnormal update rate
- Received data in error
- Controller offline
- Bus fault
- J1939 communication error
4. Check Battery Voltage First
Low voltage can make controllers reset or drop off the network.
Check
- Battery state
- Cranking voltage
- Charging voltage
- Main battery terminals
- Engine and chassis earths
If many controllers show communication codes immediately after starting, check battery and starter voltage drop before chasing the CAN wiring.
5. Check Controller Power Supplies
A controller cannot communicate if it has lost power.
Check:
- Main fuse
- Ignition-switched supply
- Permanent battery supply
- Main relay
- Controller earth
6. Check Grounds Carefully
Poor earths can cause intermittent network faults.
Look For
- Loose ground studs
- Paint under terminals
- Corrosion
- Broken braided straps
- Heat damage
7. CAN High and CAN Low
Most CAN networks use two communication wires:
- CAN High
- CAN Low
These wires are normally twisted together to reduce electrical interference.
8. Do Not Untwist or Re-Route CAN Wiring Casually
When repairing a CAN harness:
- Maintain the twisted pair
- Use suitable wire
- Keep repair length sensible
- Protect the joint from moisture
- Route away from severe interference sources
9. Common CAN Wiring Faults
- CAN High open circuit
- CAN Low open circuit
- CAN High shorted to ground
- CAN Low shorted to ground
- CAN High shorted to battery voltage
- CAN Low shorted to battery voltage
- CAN High shorted to CAN Low
10. Harness Chafing
CAN wiring often fails where the harness rubs against:
- Engine brackets
- Cab mounts
- Loader frames
- Hydraulic pipes
- Battery trays
- Sharp metal edges
Intermittent communication codes often justify a careful physical harness inspection.
11. Water in Connectors
Moisture can cause:
- Corrosion
- Short circuits
- High resistance
- Intermittent contact
Inspect For
- Green deposits
- Bent pins
- Pushed-back terminals
- Damaged seals
- Loose connector locks
12. Termination Resistors
CAN networks normally use termination resistors at defined points in the network.
A missing, open or incorrect termination can disturb communication.
Many systems use a familiar network-resistance arrangement, but machine architecture differs. Check the exact diagnostic procedure before deciding the network is faulty.
13. Resistance Testing
Where the manual specifies a resistance check:
- Switch machine off.
- Disconnect battery if instructed.
- Allow controllers to power down.
- Measure at the specified diagnostic point.
- Compare with the manual.
Do not resistance-test a powered circuit.
14. Voltage Testing on CAN Lines
Some diagnostic procedures use voltage checks on CAN High and CAN Low.
Use:
- High-impedance digital multimeter
- Correct reference earth
- Correct key/engine condition
Compare with manufacturer values.
15. Oscilloscope Testing
An oscilloscope can show network waveform quality.
It can help reveal:
- Noise
- Missing communication
- Distorted waveform
- Shorted network
- Intermittent connection
This is especially useful when basic resistance and voltage checks appear normal.
16. One Controller Pulling the Network Down
A failed controller or attached component can sometimes disturb the whole network.
The diagnostic manual may instruct you to disconnect modules one at a time to isolate the fault.
Do this only in the specified order.
17. Controller Power Loss vs Failed Controller
Before replacing an ECU, verify:
- Battery feed
- Ignition feed
- Earth
- CAN High
- CAN Low
- Relevant wake-up circuit
A perfectly good controller with no power will look dead to the rest of the machine.
18. Wake-Up Circuits
Some controllers do not become active until they receive a wake-up or ignition signal.
A missing wake-up input can create a communication code even when main battery supply is present.
19. Network Gateways
Some machines use a gateway controller between different CAN networks.
A gateway fault can cause:
- One group of controllers disappearing
- Cross-network data missing
- Multiple communication codes
20. Instrument Cluster as Part of the Network
The display or dash may be more than a simple gauge panel.
It may:
- Pass CAN messages
- Store fault codes
- Provide termination
- Act as a gateway
Do not assume the machine can operate normally with the cluster disconnected.
21. Engine ECU Communication Faults
If the engine ECU goes offline, other systems may lose:
- Engine speed
- Torque information
- Coolant temperature
- Throttle data
The machine may enter limp mode or fail to start.
22. Transmission ECU Communication Faults
Symptoms can include:
- No drive
- Fixed gear
- Shuttle disabled
- Gear display blank
- Multiple transmission codes
23. Aftertreatment Communication Faults
Later machines may use separate controllers for:
- DPF
- SCR
- DEF/AdBlue
- NOx monitoring
A communication fault can disable regeneration or trigger derate.
24. Intermittent Faults Caused by Vibration
If codes appear only while driving or operating hydraulics:
- Wiggle-test harness carefully
- Inspect connectors near moving joints
- Check cab-to-chassis harnesses
- Look for tight wiring stretched at full articulation
25. Heat-Related Network Faults
Faults appearing only when hot can be caused by:
- Controller internal failure
- Expanding connector terminals
- Heat-damaged harness
- Weak relay
- Voltage drop
26. Do Not Clear Codes Before Recording Them
Before clearing communication codes, record:
- Code number
- Controller reporting it
- Active/stored status
- Operating conditions
- Other codes present at the same time
27. Repairing CAN Wiring
Use proper repair methods.
Good Practice
- Correct wire size/type
- Maintain twist rate
- Proper crimp or approved joint
- Heat-shrink/sealing as required
- Restore original routing
28. After Repair
Once the fault is repaired:
- Reconnect all controllers.
- Clear codes if appropriate.
- Cycle ignition.
- Start machine.
- Confirm communication restored.
- Operate machine through the conditions that caused the fault.
29. Best Diagnostic Order
- Record all communication codes.
- Check battery and charging voltage.
- Check controller fuses and relays.
- Check controller powers and earths.
- Inspect harness and connectors.
- Check CAN resistance/voltage using the manual.
- Isolate controllers only if instructed.
- Repair and retest.
30. CAN Bus Diagnostic Checklist
| Area | Check |
|---|---|
| Battery voltage | Correct during key-on and cranking. |
| Charging system | Stable and within specification. |
| Controller power | Permanent and switched feeds present. |
| Controller earth | Low resistance / low voltage drop. |
| Harness | No chafing, water or damaged connectors. |
| CAN High / Low | Test only to exact wiring procedure. |
| Termination | Checked where specified. |
| Stored codes | Recorded before clearing. |
| Final test | Machine operated and communication confirmed. |
Related Agrimanual Manuals
CAN network diagrams, controller pinouts and diagnostic procedures are specific to each machine.
- Search Agrimanual CAN-bus diagnostic manuals
- Search Agrimanual electrical workshop manuals
- Search Agrimanual manuals containing fault codes
- Request a manual if your machine is not listed
Frequently Asked Questions
Can one CAN fault create lots of fault codes?
Yes. If one controller or network branch fails, several other controllers may report missing or invalid data.
Should I replace the ECU when it shows no communication?
Not before checking its battery feed, ignition feed, earth and CAN wiring.
Can low battery voltage cause CAN errors?
Yes. Controllers can reset or drop off the network during low-voltage cranking.
Why are CAN wires twisted together?
The twisted pair helps reject electrical interference and preserve reliable communication.
Can I join CAN wires with ordinary household connectors?
No. Use a proper automotive repair method and preserve the twisted-pair layout and sealing.
When several controllers complain at once, look for the common cause first — battery voltage, power, earth and CAN wiring — before replacing expensive electronic units.