Our LG washing machine does this once every year and a half almost like clockwork. It will simply refuse to do anything until it is unplugged and then plugged back in.
It may be clockwork. If its power hasn’t been interrupted in the interim, i.e. you have very stable power at your house, that’s got to be some kind of overflow bug in its software. A timer somewhere is running out of room to count clock ticks and it barfs.
I’ve an oven which when turned off in hot state while in convection mode will turn on the fans for few minutes next time I turn it on, regardless of mode and temperature. To overcome this bug I need to put mains power off for couple of minutes and let the caps keeping the ram alive drain. Not only it has hot state reset bug but also a ram initialization issue as well it seems. Thankfully that state is not stored in nvram.
The manufacturer was as expected: ‘we’re not software guy, we can send an ‘expert’ engineer (who knows only to replace parts, no debugging) and it’ll cost $$’. I thought I’ll reverse it and fixing someday, till then I’ll live with it.
And yet I still have electronics to this day that require me to pull the plug to get going again 😂
That’s actually why. You have to drain the power from the circuits.
Our LG washing machine does this once every year and a half almost like clockwork. It will simply refuse to do anything until it is unplugged and then plugged back in.
It may be clockwork. If its power hasn’t been interrupted in the interim, i.e. you have very stable power at your house, that’s got to be some kind of overflow bug in its software. A timer somewhere is running out of room to count clock ticks and it barfs.
heh 🫧
I’ve an oven which when turned off in hot state while in convection mode will turn on the fans for few minutes next time I turn it on, regardless of mode and temperature. To overcome this bug I need to put mains power off for couple of minutes and let the caps keeping the ram alive drain. Not only it has hot state reset bug but also a ram initialization issue as well it seems. Thankfully that state is not stored in nvram.
The manufacturer was as expected: ‘we’re not software guy, we can send an ‘expert’ engineer (who knows only to replace parts, no debugging) and it’ll cost $$’. I thought I’ll reverse it and fixing someday, till then I’ll live with it.