Well its a personal choice you have to decide. Is that just for one machine or both? That is a lot cheaper than Maytag ever offered me for extended warranty on my Neptunes direct from them. I could get cheaper extended warranties buying from the Maytag dealers in the area. You might see if a local dealer can sell you one for less. For the 1000-1500 dollar cost of a new machine it may be safe insurance. Most every item I had that I didnt have extended warranty on broke. Nearly everything I had extended warranty on never had breakdowns or had lower cost breakdowns than the price of the warranty. If you can fix it yourself and can aquire parts reasonable that would figure into my decision if it were me. Ive worked on autos for a living for over 30 years so I have tools and ability. I just need a manual and the internet.. :-)

I hope I'm not hijacking this thread. I have a Duet 9300 HT made in Germany. It's a tad over 4 yrs old. After just over a year of owning it, I started to get the fdl code, followed by the f11 code. After several visits they ended up changing one of the boards, not sure if it was the MCU or CCU. It has worked fine ever since, no errors for a solid three years. Yesterday, I washed an electric blanket. As soon as I chose normal I pushed start, the machine did the usual spray water, then lock. I had realized that I forgot to set the spin to low speed since it was an electric blanket, so during the spray, then lock I pushed pause to try to re-set the spin speed, so it paused, I set it to low, then started it back, then I got an f11 code. I said NO! NO! NO! I paused and started, it did it one more time, so I paused, started again, and it finished the cycle. I'm hoping that this was caused by the confusion of me "pausing" it during its initial spray, lock? Maybe it got confused..I don't know. I hope so. I've ran three loads since and nothing has went wrong. But I distinctly remember with my first go round with this crap, I could do many loads thinking everything was fine and then the ugly f11 would rear it's ugly head. Thankfully, I have the extended warranty which runs out in october of this year. So I have time to make sure.

When you aimed the exhaust out your window, did you have it blowing through a window screen? If so, that's wrong. It's very difficult for air to blow *through* a screen. Try it again with the screen off the window or the exhaust duct aimed out a door, or simply laying on the floor, whatever, so the air stream has no restriction. Just wondering also ... I've seen cases in which the dryer was shoved too far back against the wall, crushing the flexible vent hose or bending it sharply. By the way, the thermostat is *supposed* to turn off (and then back on) to maintain whatever is the target temperature for the selected cycle. For your reference, below are the temperatures at which the heat shuts off. It cycles back on when the temp drops by 10°F to 15°F. High = 155°F +/- 10°F Medium = 145°F +/- 10°F Low = 125°F +/- 10°F Ex Low = 105°F +/- 5°F Your washer's spin speed does have some effect on drying time, but the new dryer still should be able to dry a load in close to the same time as the old one. Maybe your old dryer ran hotter than the new one? Did you normally use the High temperature setting on it? The starting cycle time is only an estimate. The electronic control recalculates and adjusts the remaining time based on how quickly it senses the clothes are drying, size of the load, what is the target dryness level, etc. If the two damp items were of substantially heavier fabric weight than the rest of the items in the load, it's normal for them to be damp at the end. Your dryer's electronic sensing split the difference between the lighter and heavier items. If your old dryer didn't have an electronic sensor, you may not be accustomed to how it works. Some newer dryers also tend to err toward the side of less-dry for energy saving purposes, so you may need to raise the target dryness setting by one level depending on the mix of fabrics that comprises your normal loads.

Well the new motor fixed it, so I guess I'll let this drop.