Engine Brake Inoperative Below Set Speed With Jake Brake Switch On
A 2015 conventional school bus with a Cummins ISL 9 and an integrated compression-release engine brake is used on a hilly route. The driver reports the engine brake works above about 35 mph but does nothing below that, even with the switch on and the transmission in a low gear on a long downgrade. The brake selector is set to high. The ECM shows no active faults, but a history code for the engine brake output circuit is present. The clutch switch and throttle position sensor read correctly on the scan tool. Vehicle speed is accurate. Oil pressure is within spec. The engine brake harness connector at the valve cover is secure, and the solenoid resistance measured at the connector is within spec. The driver also notes the cruise control cancels normally.
1. Explain why the engine brake cuts out below 35 mph and whether this is a fault or a design condition.
Read the worked answer
Many OEM engine brake calibrations inhibit brake operation below a minimum vehicle speed (often around 20–35 mph) to prevent stalling or harsh operation at low speed, and they also require the throttle closed, clutch engaged, and engine above a minimum rpm. The driver's observation that the brake works above 35 mph but not below is consistent with a speed-inhibit calibration, not necessarily a failure.
However, the history code for the engine brake output circuit means the inhibit threshold alone may not explain the complaint. The correct approach is to verify the actual programmed minimum-speed threshold in the ECM calibration and compare it to the driver's expectation, then confirm the brake actually engages on a downgrade above the threshold. If it engages above threshold and the threshold is as programmed, the system is operating as designed and the driver needs education on the calibration.
2. The brake also fails to engage above 35 mph on a subsequent road test. How do you proceed, given the history code and good solenoid resistance?
Read the worked answer
A history output-circuit code with a good static solenoid resistance means the fault is likely intermittent or in the wiring/connector under load, or the ECM driver is being commanded off by an input the scan tool snapshot did not capture.
Steps:
- Road test with the scan tool recording engine brake command, vehicle speed, throttle %, clutch status, and brake switch status to see which input drops out when the brake fails.
- Wiggle-test the harness from ECM to valve cover while monitoring solenoid command; check for chafed wiring at the valve cover pass-through.
- Measure solenoid current (not just resistance) during command; a solenoid can read correct resistance cold but draw wrong current hot.
- If command is present at the ECM but not at the solenoid, repair the circuit; if command is absent with all inputs correct, suspect the ECM driver and follow OEM diagnostics before replacement.
Do not replace the ECM or the brake solenoid on the strength of a history code alone.