UPDATE 2: Spinning now. Turns out the shifter that I got from Amazon was bad. All good now
UPDATE: I put the old shifter back in and it appears to be doing something different. Will update if that fixes it for sure.
I know enough about this to follow along, but not necessarily understand. Sorry for the length of the post, but I'm trying to give as much detail as possible.
Error code:
F7E5Parts replaced so far:
Lid Lock, Shifter, Control BoardDescription of Problem: Original problem was the washer would stop full of water. Not sure if it was trying to agitate or spin. It happened about a year ago and I replaced the lid lock and it started working again. So I replaced the same part this time. That didn't work.
I got out the technicians manual and looked up that code, it said to check harness connections, observe shifter operation, and do test 3a. I went through all of those steps. In doing so, I've replaced the shifter and control board. It's still doing the same thing. Details of the the steps below, but the
thing that is still failing after all of that is step 9, voltmeter on J2-3 and J2-1. It's supposed to switch between +5 and 0. It stays on +5.Any idea on what I should try next? Thank you!
Details of Test 3a results:
1.check shifter with manual spin and agitate.
Spin and agitate both do nothing for about a minute, make a loud noise followed by a click.
2.unplug
3.Check basket turns
turns fine
4. Removed console
5. check j2 and j16 plugged in
They were plugged in fine
6. Remove J16 check resistance
Showed 2.718k, within range
7. Plug back in
8. Voltmeter AC J16-2 and J16-1 look for 120v
both were at 120 until it made the same noise as step one, then it would drop to zero and go right back to 120
9. Voltmeter DC J2-3 J2-1
Stayed at +5 for both spin and agitate
Failed step 9 so skip to 12
12. unplug
13. tilt
14. check electrical connections to shifter
These were fine
15. check harness for continuity
all fine
16. replace shifter assembly
did this, and calibrated. same result
17. replace main control
did this just now, same issue.
Edited by user Thursday, August 6, 2020 7:23:41 AM(UTC)
| Reason: Not specified
