Komatsu Engines 285 Fault Code: SAE J1939 Multiplexing PGN Timeout Error - Abnormal Update Rate
SAE J1939 Multiplexing PGN Timeout Error - Abnormal Update Rate · ai-assisted, editor-reviewed · Last updated 2026-07-13
TL;DR
Komatsu fault code 285 (SPN 639, FMI 9) means the engine ECM did not get a valid J1939 message from a multiplexed device in time, or at all. The amber CHECK ENGINE lamp comes on, the ECM substitutes a default value for that input, and one or more multiplexed components will not work right until the communication is restored.
Medium severity. The engine keeps running because the ECM substitutes a default state for the missing input, but any multiplexed switch, sensor, or accelerator input tied to that message will not behave normally. Depending on which component is affected, this can range from a minor inconvenience to a real operating problem, so it should be diagnosed the same shift it appears rather than ignored.
What does Komatsu Engines error code 285 mean?
Fault code 285 is Komatsu's version of SPN 639 FMI 9, an SAE J1939 Multiplexing PGN Timeout Error with an abnormal update rate. Instead of most switches, sensors, and accelerator components wiring directly into the engine ECM, multiplexing lets an OEM vehicle electronic control unit (VECU) or transmission ECU in the cab collect those signals and forward them to the engine ECM over the J1939 data link.
This code sets when the ECM expected a scheduled message from a multiplexed device on that data link and either did not receive it in time or never received it at all. It can also be triggered by an open or short circuit detected in the J1939 data link harness itself.
When active, the ECM lights the amber CHECK ENGINE lamp immediately and substitutes a default value for the missing multiplexed input so the engine keeps running, but the real-world component that was supposed to be reporting over the data link will not function as intended.
What triggers a Komatsu Engines 285 code?
The ECM sets this fault when it does not receive a valid J1939 message from a multiplexed device for more than 1 second, or when it detects an open or short circuit condition in the J1939 data link harness. The diagnostic runs continuously whenever the keyswitch is in the ON position (on some versions, also whenever the engine is running).
Common causes of 285
- The ECM is configured correctly (component enabled, OEM VECU source address correct) but the OEM VECU is actually transmitting a message stating that component is not available for multiplexing.
- A multiplexed component is enabled in the ECM, but the OEM VECU source address programmed into the ECM does not match the VECU that is actually sending that component's message.
- The OEM VECU itself is not set up or configured to transmit the multiplexed component message in the first place.
- A damaged J1939 data link connection between the OEM VECU and the engine ECM.
- A damaged connection between the component itself and the OEM VECU.
- A damaged OEM VECU or a damaged engine ECM.
- Loose, missing, or intermittent connections at OEM Power Distribution Center fuses and relays, especially when intermittent power or datalink issues affect aftertreatment components.
How to troubleshoot Komatsu Engines 285: first checks
- Connect a diagnostic electronic service tool and identify exactly which multiplexed component or PGN is timing out, and use the tool to monitor multiplexed components live.
- Check the OEM VECU source address configured in the engine ECM against the address the OEM VECU is actually transmitting from; a mismatch here is a listed cause.
- Confirm the OEM VECU is actually enabled and set up to transmit the message for that specific component; it may simply not be configured to send it.
- Inspect the J1939 data link harness end to end for damage, opens, or shorts between the OEM VECU and the engine ECM, using the OEM wiring diagram since this wiring is OEM-supplied.
- Inspect the wiring and connections between the affected component and the OEM VECU for damage.
- Check OEM Power Distribution Center fuses and relays for loose, missing, or intermittent connections, particularly if the symptoms are intermittent or involve aftertreatment components.
- If configuration and wiring both check out, consider that the OEM VECU or the engine ECM itself may be damaged, and contact the OEM for proper multiplexing configuration support.
How the code clears
To validate a repair, cycle the key, start the engine, and let it idle for 1 minute. Once the diagnostic runs and passes during that idle period, the fault code status on the electronic service tool changes to INACTIVE immediately and the ECM turns off the amber CHECK ENGINE lamp. The Reset All Faults command in the electronic service tool can also be used to clear both active and inactive faults (and will extinguish the MIL on OBD applications).
Frequently asked questions
What does Komatsu fault code 285 mean?
It means the engine ECM did not receive a timely or valid J1939 message from a multiplexed device, SPN 639 FMI 9, an abnormal update rate timeout on the data link. This is a communication problem between the OEM's cab electronics and the engine ECM, not a mechanical engine fault.
Is it safe to keep operating with code 285 active?
The engine will keep running because the ECM substitutes a default value for the missing input, but whatever switch, sensor, or accelerator signal was supposed to come through multiplexing will not operate correctly. Whether that is safe to ignore depends entirely on which component is affected, so it should be diagnosed promptly rather than run indefinitely.
Will code 285 clear itself?
It clears automatically once the diagnostic runs and passes, which Komatsu says can be confirmed by cycling the key, starting the engine, and letting it idle for 1 minute. You can also use the Reset All Faults command on the electronic service tool to clear active and inactive faults directly.
What usually causes this fault?
The most common causes are configuration mismatches: the OEM VECU source address programmed in the ECM does not match the actual transmitting VECU, or the OEM VECU is not set up to send the component's message at all. Physical causes include damaged J1939 data link wiring, a damaged component-to-VECU connection, or a damaged VECU or ECM.
Does this fault mean the J1939 wiring is bad?
Not necessarily. Komatsu lists both configuration issues (wrong source address, VECU not enabled to transmit) and physical wiring or hardware damage as possible causes, so wiring should be checked but configuration should be verified first since it is just as common a cause.
Why would this happen with aftertreatment components specifically?
For intermittent power or datalink issues tied to aftertreatment components, Komatsu specifically recommends thoroughly checking the OEM Power Distribution Center fuses and relays for loose, missing, or intermittent connections before assuming a deeper wiring or module failure.
Do I need the OEM's help to fix this?
Possibly. Since the VECU, its configuration, and the J1939 wiring downstream of the engine ECM are all OEM-supplied and OEM-configured, Komatsu notes it can become necessary to contact the OEM for proper multiplexing configuration, especially if the address and wiring checks do not resolve it.