A machine that has dropped to 5 mph, limited engine speed, or reduced torque does not need guesswork. It needs fault data. Can scan tools clear derates? Yes, in specific conditions. A capable diagnostic platform can clear stored and inactive faults, run a reset routine, and sometimes release a temporary protection strategy after the underlying repair is complete. It cannot make an active failure disappear, and it should not be treated as a substitute for repairing the system that initiated the derate.
For heavy equipment, agricultural machines, commercial trucks, and industrial engines, the exact answer depends on the OEM, engine family, emissions configuration, fault state, and diagnostic access level. The difference between clearing a code and clearing a derate matters because it determines whether the unit returns to work or returns to the shop ten minutes later.
What a derate actually means
A derate is an ECM-controlled reduction in available engine performance. Depending on the platform, that can mean reduced torque, limited RPM, restricted road speed, disabled PTO operation, reduced hydraulic response, or a programmed shutdown countdown. The ECM applies the restriction to protect the engine, aftertreatment system, drivetrain, or another monitored system from a condition outside its allowable operating range.
Common derate triggers include low oil pressure, high coolant temperature, fuel rail pressure faults, turbocharger or boost-control problems, EGR faults, DPF soot loading, SCR efficiency faults, low DEF quality, NOx sensor faults, and repeated regeneration failures. On some machines, the fault may originate in a body controller, transmission controller, or hydraulic controller rather than the engine ECM.
A derate is therefore not a single diagnostic trouble code. It is a response to one or more faults and operating conditions. The scan tool must communicate with the correct controller and support the correct service function if it is going to do more than display and erase a generic code.
Can scan tools clear derates permanently?
A scan tool can clear a derate permanently only when the cause is corrected and the controller’s release conditions have been met. If a failed sensor, plugged DPF, wiring fault, DEF issue, or mechanical problem remains active, the ECM will usually detect it on the next key cycle, self-test, or loaded operating event. The fault returns, and so does the derate.
This is why a generic OBD code reader often produces disappointing results on commercial and off-highway equipment. It may erase an emissions-related code from memory, but it may not access OEM-specific faults, live data, regeneration controls, reset counters, or protected service routines. It may also fail to communicate with the controller that is currently commanding the limitation.
Factory-level or brand-specific diagnostic software has a different role. It can identify whether a fault is active, pending, previously active, or stored as history. It can show the conditions that triggered the event, display sensor values in real time, and, where supported, perform functions such as forced regeneration, aftertreatment reset, SCR inducement reset, learned-value reset, or fault clearing after repair.
The practical rule is simple: a tool can clear the command only when the machine is ready to release it.
The difference between code clearing and reset functions
Technicians often use the phrase “clear derate” to describe several different operations. They are not interchangeable.
Clearing fault memory removes eligible inactive diagnostic trouble codes from the controller. It does not necessarily cancel an active warning or restore power. An ECM reset restarts the module and can force the controller to re-evaluate certain conditions, but it does not repair failed components. A service reset may clear a counter, adaptation, inducement stage, or maintenance value after the required repair has been verified.
Forced regeneration is another separate function. It is used when soot loading and operating conditions allow a stationary or service regeneration. It can resolve a soot-related restriction when the DPF and supporting systems are otherwise serviceable. It will not correct an exhaust temperature sensor circuit fault, a failed dosing component, excessive ash loading, damaged substrate, or an SCR efficiency problem.
Some platforms also use inducement logic. An inducement can reduce speed, torque, or restart capability after emissions-related faults have remained unresolved for a defined period. Depending on the OEM, clearing an inducement may require a completed repair, valid sensor readings, a successful drive cycle, security access, or a supported OEM routine. Simply disconnecting batteries or clearing generic codes is rarely a reliable solution.
A diagnostic workflow that prevents repeat derates
Start by connecting a tool that supports the machine’s OEM and controller network. Pull all modules, not just the engine ECM. A CAN communication issue, supply-voltage problem, or fault in an aftertreatment controller can create symptoms that look like an engine-only issue.
Record active and inactive codes before clearing anything. Freeze-frame information, occurrence counts, engine hours, and associated codes can identify whether the fault happened once during a low-voltage event or is repeating every time the engine sees load. Clearing codes before saving this information can erase evidence needed for a fast repair.
Next, use live data to test the fault path. Compare commanded and actual values for rail pressure, boost, EGR position, DPF differential pressure, exhaust temperatures, DEF tank quality, DEF pressure, NOx readings, and coolant temperature where applicable. Do not condemn a sensor based on a code alone. Verify reference voltage, ground integrity, connector condition, harness routing, and mechanical causes that can generate a plausible but incorrect sensor reading.
Once the repair is complete, run the proper service routine. That may mean clearing faults, performing a parked regeneration, resetting an aftertreatment maintenance value, completing an SCR test, or following a specified key-cycle and drive-cycle procedure. Then verify that the fault remains inactive under the operating conditions that previously triggered the derate. A machine that passes at idle but derates under load has not been repaired.
Why a clear command may fail
When diagnostic software refuses to clear a code or a derate returns immediately, the issue is usually one of four categories: the fault is still electrically active, the mechanical cause has not been corrected, a required monitor has not completed, or the tool lacks the required OEM function or security authorization.
For example, a differential-pressure code may remain active because the pressure sensor circuit is open. A forced regeneration will not start until that circuit is valid. An SCR derate may remain in place because the controller needs to see normal DEF pressure, valid upstream and downstream NOx signals, and a successful efficiency test. A low-power condition may be caused by a restricted fuel supply or charge-air leak that produces no simple “reset” outcome at all.
Software version and communication hardware also matter. Older software may identify codes but lack newer service functions. A low-cost interface may not support J1939, CAN FD, DoIP, proprietary adapters, or the communication stability required for programming and reset operations. Before buying or using a tool, confirm the OEM coverage, model year range, engine family, required interface, operating system, and whether the needed function is available in that software version.
Derate clearing requires the right level of access
Independent shops need more than a code reader when servicing late-model diesel platforms. The productive setup is one that can read full OEM fault detail, view live parameters, perform guided tests, access service routines, and support the security functions required by the application. That level of coverage reduces unnecessary parts replacement and avoids dealer dependence for routine diagnostic work.
SYSTEMRTX-focused diagnostic resources are intended for technicians who need brand-specific software, service utilities, password tools, and technical data matched to real repair workflows. The correct package is not the one that claims to “clear all codes.” It is the one that supports the exact controller, model range, and function required for the job.
Emissions systems and legal limits
A proper repair restores the emissions system to its designed operating condition. Removing, bypassing, or altering emissions controls to prevent a derate can violate federal and state requirements and may create larger reliability, resale, and compliance problems. Use diagnostic functions to identify faults, complete approved repairs, and verify that the machine meets its intended operating strategy.
The fastest way out of a derate is usually not an erase button. It is accurate OEM-level data, a verified repair, and a scan tool capable of proving the ECM has accepted the result.