Model Number: MHWE200XW00
Brand: Maytag
Age: 1-5 years
My 3 years old washer started displaying the F6 E1 error after I replaced the fill hose (major leak dripping down the bottom plate, but the error didn't appear until after I replaced the hose). I could cancel and restart the wash but with the same result. Once it displayed the F1E2 error, but only once.
We live on an island off the coast of Maine and cannot rely easily on professional service repairs. I did call Maytag support though, who couldn't identify a service repair provider in the area of Portland, ME <rolleyes>.
This forum was very helpful in providing info and narrowing down to the cause of the problem. Did the diagnostic test, checked all connections from cord to harnesses and especially grounding connections. The MCU then became the usual suspect.
Identified the part and was ready to order, but at $160 (though with a nice return option and definitly better than getting a new machine shipped over here) I hesitated for a second and decided to take it out, following a very helpful youtube video (http://www.youtube.com/watch?annotat...&v=QEQUaCYUkZs), checked closely all I could, connections and signs of oxidation, wear or burn. Didn't notice anything, put it back in place, ran a delicate cycle, then a second wash on normal, a third one on heavy duty, and miracle it worked like the first day we got the machine! Complete cycles, perfectly washed and spun clothes, no error messages. Did a little dance while folding the laundry!
So now to my questions: did I correct a bad connection while disconnecting/reconnecting the wires? Or did I reset something in the MCU that erased some memory of the error message that was meant to be temporary? Have any of you experienced this? And if yes, did you fix the problem permanently or only temporarily? (I'll surely be holding my breath for a weeks... :-D). If the problem reoccur, how do you recommend I find out if it's connection related, MCU need to be replaced or maybe just the wire harness?
Thank you for any feedback, and hope this thread will be useful to anyone experiencing the same problem.