Retrieve the code from the monitor or with a diagnostic tool, record the exact code and the conditions it appeared under, then test the circuit the code points to. A code identifies a circuit or a condition, not necessarily the failed component within it.
How to confirm it
- Find out how to retrieve codes on this platform
On many machines the monitor has a service mode, entered by a sequence of button presses, that displays stored codes. Others need a diagnostic tool. Establish which before you start, and note that some codes are only visible while the fault is active.
- Record every code, not just the one you expected
Write down all stored codes in order, with the machine hours if shown. A sequence of codes from one session is often more informative than any single code, and clearing codes before writing them down throws away the most useful evidence you had.
- Note the conditions the fault appears under
Cold or hot, idle or full load, traveling, swinging, in wet weather. Fault codes tell you what the controller saw; the conditions tell you why. Together they narrow the search considerably.
- Interpret the code against the machine documentation
Look the code up in the service documentation for that model and serial number range. The same numeric code can mean different things on different platforms and revisions, so the code alone is not enough.
- Test the circuit the code identifies
Measure power and ground at the component, check the connector, and check the sensor signal against specification. Most codes that result in a component replacement should have been preceded by this step.
- Clear the code and re-test to confirm
Clear the code, operate the machine in the conditions that produced it, and see whether it returns. A code that does not return after the fault is corrected confirms the repair. A code that returns immediately after clearing points to an unresolved fault, not a persistent memory.
What to do about it
Code present, circuit and component within specification: the fault may be intermittent. Check the harness run for chafing, the connectors for water and the grounds for corrosion before replacing the component.
Code points to a sensor: confirm the sensor signal against specification with a meter before replacing it. Sensor drift is common, and it is detectable without removing the sensor.
Code points to a solenoid: test the coil directly. A failed coil is common and inexpensive, and the valve body behind it usually does not need replacing at the same time.
Multiple unrelated codes together: check system voltage and grounds first. Several controllers logging faults simultaneously usually share one supply problem rather than having several component failures at once.
No codes but a clear fault: work from the symptom. Older machines without electronic monitoring give you no codes at all, and the troubleshooting sections on this site are arranged to work that way.
Need the parts this covers?
Send the machine model, serial number and the part numbers you need. We confirm fitment before payment and state the grade of every line — genuine, OEM-quality or aftermarket.
Request a quoteFrequently asked
I cleared the codes and they came back. What does that mean?
That the underlying fault is still present. Clearing a code erases the record, not the condition. If a code returns immediately after clearing with the machine running, the fault is active or current rather than historic.
The machine shows no codes but something is clearly wrong. Why?
Because not every fault is monitored. Mechanical wear, hydraulic leakage and many undercarriage faults are outside what the controllers can see. Absence of codes is not evidence of a healthy machine.
Can I diagnose from codes alone?
Not reliably. A code identifies a circuit and a condition. Whether the component, its wiring, its connector or its supply is at fault requires measurement. Codes save time by narrowing the search; they rarely complete it.