Section 4 Troubleshooting; Introduction; Controller Troubleshooting - Kohler 17RES Operation Manual

4.1 Introduction

Use the following charts to diagnose and correct
common problems. First check for simple causes such
as a dead engine starting battery, loose connections, or
an open circuit breaker. The charts include a list of
common problems, possible causes of the problem, and
recommended corrective actions.
If the procedures in this manual do not explain how to
correct the problem, contact an authorized distributor/
dealer. Maintain a record of repairs and adjustments
performed on the equipment. Use the record to help
describe the problem and repairs or adjustments made
to the equipment.
Problem Possible Cause
Controller LED No power to the controller:
di display is off l i ff
The generator set has not run for 48 hours or
longer and the controller has powered down.
Controller fuse (F3) is blown.
Low or no battery voltage.
Generator set master switch is in the OFF/RESET
position.
Generator set master switch in AUTO but no start
command has been received since last controller
reset.
Figure 4-1 ADC-RES Troubleshooting Chart
TP-6515 10/07

Section 4 Troubleshooting

4.2 Controller Troubleshooting

Figure 4-1 contains troubleshooting, diagnostic, and
repair information for the ADC-RES controller.
Corrective Action
Controller display will automatically activate when a remote start
command is received or the generator set master switch is
moved to the RUN position. See Section 2.4.
Replace the fuse. If the fuse blows again, contact the
distributor/dealer.
Check connections.
Check generator set battery and battery charger. See
Figure 4-2.
Move generator set master switch to the AUTO or RUN
position. In AUTO, the display will not turn on until the first start
command is received.
Controller display will activate when a remote start command is
received or the generator set master switch is moved to the
RUN position. Use the remote switch to start generator set and
activate the controller display, if desired. See Section 2.3.1.
Section 4 Troubleshooting 27