Mike Dolt Enterprises Logo Mike Dolt Enterprises

Topic: kohler 17RES OS overspeed fault

User: electrofelon, Location: Cherry Valley NY, Seattle, WA

Asked on: Monday, October 28, 2024 at 9:30 pm EDT
Answered on: Thursday, March 6, 2025 at 4:32 am EST

Question: Probably a long shot, but anyone have experience with this fault on this or similar unit? Its a circa 2007 unit. It cranks for about 4 seconds, just starts to fire then stops with a overspeed fault. I am nearly certain that it is not actually overspeeding. I tested the speed sensor and both tests pass with the 1.3-1.9 k ohms and 1.75 VAC minimum while cranking. I am leaning toward it being the controller, because when I disconnect the gas so the unit does fire at all, it cranks for about the same 4 seconds then stops with an OC (overcrank) fault and does not try again. According to the service manual it is suppose to crank for 15 seconds, stop for 15 seconds and do that 3 times. Apparently that is built into the controller and is not adjustable.

You've done a good job with the initial troubleshooting steps! Given your observations, it definitely points towards a controller issue or a problem closely tied to its interpretation of the speed sensor signal. Here's a breakdown of things to consider and potentially test, keeping in mind that diagnosing electronic controls remotely is always challenging

1. Deep Dive into the Speed Sensor Circuit & Signal:
Oscilloscope is your friend

Your voltage test is good, but an oscilloscope will reveal the

quality and shape
of the AC signal from the speed sensor. Look for:
Clean Sine Wave

Is it a distorted or irregular waveform? Noise in the signal can be misinterpreted by the controller.

Consistent Frequency

Does the frequency
increase smoothly as the engine cranks, or are there sudden jumps or dips? These fluctuations can trick the controller.

Wiring Inspection

Trace the entire wiring harness from the speed sensor to the controller. Look for:

Loose Connections

Especially at connectors. Corrosion can create intermittent signals.


Damaged Insulation

Chafing or cracking can cause short circuits or interference.

Proximity to High-Voltage Wires

Routing speed sensor wires near spark plug wires or other high-voltage components can introduce noise. Shielded cable helps in these scenarios.


Speed Sensor Gap

Verify the gap between the speed sensor and the tone wheel (or flywheel teeth) is correct. Too large a gap weakens the signal. Consult the service manual for the proper specification.

Tone Wheel Condition

Check the teeth (or the tone wheel itself) for damage, rust, or debris. Irregularities can disrupt the speed sensor signal.

2. Controller Considerations



Controller Power Supply

A stable, clean power supply is crucial for the controller to function correctly. Check the voltage at the controller's power input terminals while cranking. It should remain within the specified range (usually 12V or 24V DC, depending on the generator). Look for voltage drops. If the voltage sags significantly during cranking, it could be causing the controller to malfunction.

Grounding

Poor grounding is a common cause of erratic behavior in electronic systems. Ensure the controller is properly grounded to a clean, unpainted surface on the generator frame. Clean all grounding connections.


Controller Connectors

Carefully inspect all connectors going into the controller. Disconnect and reconnect them to ensure good contact. Use electrical contact cleaner.

Controller Programming/Parameters

(If applicable, and
only if you have the necessary software and knowledge): Some controllers have adjustable parameters related to speed sensing and fault thresholds. Do not change anything unless you are absolutely sure what you are doing. Incorrect settings can cause major problems. Look for anything related to speed thresholds for faults. Document the original settings before making any changes. If you can revert to factory default settings (if available) as a test, that might be helpful.

Controller Internal Faults

Unfortunately, sometimes controllers just fail. If all else checks out, the controller itself is the most likely culprit. Consider having it tested by a specialist if possible.

3. Simulating a Running Engine (Advanced, Use Caution)



Signal Generator

Only do this if you are very comfortable with electronics. You might be able to simulate the speed sensor signal with a signal generator. This would let you isolate the controller and test its response to a known, clean, and properly increasing frequency. However, incorrect signal levels could damage the controller, so proceed with extreme caution. You'd need to determine the correct voltage and frequency range that corresponds to the engine cranking and running speeds.

4. Fuel System Consideration (Less Likely, But Worth Checking)

While you've disconnected the gas, ensure the fuel solenoid or valve (if present) is opening and closing correctly during the start sequence. A sticking valve could cause a brief burst of fuel followed by a cutoff, mimicking an overspeed condition. Verify voltage at the fuel solenoid.

Troubleshooting Order Suggestion


Detailed Wiring and Connector Inspection

Start with the basics. Carefully inspect all wiring and connectors in the speed sensor circuit and the controller power/ground circuits. Clean and reconnect.2.

Oscilloscope Analysis of Speed Sensor Signal

Get a visual picture of the signal.3.

Controller Power Supply Voltage Check

Verify stable voltage while cranking.4.

Simulating Speed Sensor Signal (Advanced, Use Caution)

If the above doesn't point to a problem, consider the signal generator test.5.

Controller Replacement

If all other tests fail, the controller is the most likely cause.

Important Safety Notes

Always disconnect the generator's battery before working on electrical components. Be careful when working around moving parts while the engine is cranking.* If you are not comfortable working with electrical systems, consult a qualified generator technician.

Why the Overcrank Fault is Important:


Your observation about the overcrank (OC) fault is very important. The fact that it's not performing the expected 3-crank sequence strongly suggests a controller issue. The controller's programmed timing and logic are not functioning as designed.Good luck, and keep us updated on your progress! Hopefully, one of these suggestions will lead you to the solution. Flag for review

Previous Question Next Question