Whirlpool Duet Washer Model GHW9160PW1: F11 after C:01

[BrianE]

The washer has a F11 code. I ran diagnositics and it stopped at C:01 and never displayed C:02. Does that mean that C:02 failed or C:01 failed?

If C:01, what should I check next? I saw water flow into the washer during C:01 testing and then it went to F11.

If C:02, what should I check next? I'm not sure where the dispenser contact is to inspect it. Is there a way to test the dispenser motor or should I replace it?

I really appreciate the help!

Brian

[Vance R]

On 4/3/2021 at 4:44 AM, BrianE said:

The washer has a F11 code. I ran diagnositics and it stopped at C:01 and never displayed C:02. Does that mean that C:02 failed or C:01 failed?

The "C" numbers are the steps in the test sequence. Since there is a error in step 1 the board stops at that step. F11 is a serial communication error between the MCU and the CCU. The tech sheet should be inside the machine, follow the steps to troubleshoot F11.

[BrianE]

Thank you, Vance. I think I get it now. The tech sheet says that, for F11, one of the steps is to run the diagnostic test, so I had done that. I thought that the diagnostic test ran and stopped when it encountered a problem, which was indicated by the C codes. That's why I asked the way I asked in the first question. Now, I see that I advance the test to a C code to test that part of the washer. I can't get the C:04 cycle to run before F11 shows. So, I think that means that the MCU is not working, rather than the CCU. I will try to tighten the connection between the MCU and CCU first and then replace the MCU to see if that works. Does that sound like the right path?

Brian

[Vance R]

1 hour ago, BrianE said:

Does that sound like the right path?

 

Yes, ohm out the windings of the motor. All 3 windings should be the same, the tach winding should be around 100 with all windings infinity to ground. Verify 120 vac and believe it is 12 vdc to MCU when motor is supposed to running. 

[BrianE]

Since I don't know how to ohm out windings, I ordered a new MCU. It came in today and solved the problem.  Thanks for all the help!

Brian