In other news, a few months ago my microwave oven keypad broke; the first two rows of numbers quit working, 012 and 345. That made things tricky. Had to cook things for 6:66 minutes and seconds. Setting time was hard. I assumed that some trace had broken in the membrane thing.
So last night we had a brief power failure, and now it all works! I don't understand how that's possible.
Are you joking? A friend had an older console TV with a digital readout of the channel. Did I mention it had a picture tube? So the digital channel indicator was separate from the screen. One time it stopped working right . I think it was not displaying numbers at all or something similarly goof y. He thought it was time to tear it apart. I told him to unplug it for a few seconds and then it worked. The tiny MCU needed a good reset. The MC U probably is never turned off since it is likely involved in the remote co ntrol circuit too.
It may have been a short power glitch that knocked it silly in the first pl ace. His and yours.
Software written by EEs
Most microwaves manufactured in the past 20 years that cost over $150 have a +30 sec button
Should I ask if you power cycled (unplugged) the microwave after the problem appeared?
John ;-#)#
One of the rear passenger doors on my car stopped locking about a year ago and the key fob remote stopped working. No biggie, only an old car anyway in which I might do 1500 miles per year tops.
Last week the door lock started working again, still no key fob remote, but now all the warning messages on the dashboard display are in German. It's a French car too - must be something to do with Brexit but I haven't figured out what.
Cheers
Mine doesn't have a computer, it has multiple computers. Sometimes I yearn for... I dunno a Lada maybe.
NT
the disease is quickly fixed by driving one ...
They drive pretty well
NT
How can one bit of code break, and be fixed by a reset?
I guess I just don't have the chops to be a programmer.
No, that would be rude.
Why would anyone think to do that?
Mine has EASY COOK, which is +30 seconds, which works depending on what state it is in. It's complex.
glitch, radiation, esd etc. gets is stuck somewhere it can't get out of and the 5 cent micro doesn't have a watchdog
It's not the code that "broke". The MCU got lost by a hardware glitch. The power supplies they use are not the best in the world and let various noise past.
for (size_t i = 0; i < keypad_arr_.size(); ++i) { for (size_t j = 0; j < keypad_arr_[j].size(); ++j) { ^ ...
FUUUUUUUUUUUK!
that hopefully wouldn't make it out of production but it can ruin your day
Also ask Toyota they prolly know
Or a millennial. I'm sorry... make that "sketch" by a millennial, not software.
No millennial would stoop to writing code for such lowly apparatus as _appliances_.
Hey boomers! While you're ranting about what the lousy kids are up to these days, there was a generation or two between the lousy boomers and the lousy kids these days.
Hey remember us? Anyone? Bueller? Buller....
Reports say their code was littered with thousands of static/global variables, creating almost an infinitely complex (but certainly un-analysable) state space.
The first thing I do before starting to look for bugs in a client's embedded device is make a comprehensive review of all global data. It's amazing how many potential bugs you can find just by looking at the linker map of global data.
Clifford Heath.
Have something to add? Share your thoughts — no account required.
Ask the community — no account required