PDA

View Full Version : GW395 keypad doesn't work


Jiggypig
October 25th, 2006, 05:39 PM
This is a difficult one. Purchased the stove in April 05. Oven quit working Thanksgiving day the same year (start button wouldn't work). Cooked at a neighbors and called for a warranty repair. It started working again the following week, but the serviceman went ahead and replaced the control board and keypad to prevent future problems. Early September, none of the oven control buttons work for the bake cycle. Broil and Clean worked though. No longer under warranty, and Whirlpool is no help. Replaced the control board, now no buttons work. Replaced the keypad, same thing. Had 2 repairmen out that disassembled the entire stove, metered all the relays, sensors, and anything else they could check, and both said it was a bad control board. Returned the board under warranty (it was 3 weeks old), installed the new replacement, with the new keypad and still no response to the keypresses. If the keypad is disconnected it will generate an error code, but otherwise it just reports the power failure. I haven't been able to find any reference for the control board to even begin to test it, and all the repairmen don't seem to have a clue. Any input would be greatly appreciated.

Jake
October 26th, 2006, 12:26 AM
I remember I had a few of these models that I found doing the same thing, I pulled out the range and opened the back access panel, and I found a wire that was arcing to a metal connector causing a short.

Check all your wiring very well behind that back access panel after you pull your range out.

Jake

Jiggypig
October 26th, 2006, 05:29 PM
Nothing happening in the back of the oven. It's been dissasembled several times by now, and most of the testing is without the sheetmetal installed. the only thing that works is the clock display, but I can't set it. I tipped it over and looked underneath also, but everything looks ok. Any other suggestions?

Jake
October 27th, 2006, 01:03 AM
This is a tough one. I can't think of anything else.

Hopefully another tech. or member that has seen this happen can post the fix here.

Jake