“Cooktop timer off has d0 and beeps sound that will not turn off. How do I rectify this problem?”
1-4 of 4 Answers
This is super anoything but its a safty feature. If the controls get wet and stay wet for a certain amount of time it can get locked in the d0 mode, if it gets locked in the d0 mode you have to switch the circuit breaker for your kitching off for 30 sec then back on to reset. If you clean the counter top make sure you put it (child lock) mode so this wont happen.
Sorry, there was a problem. Please try again later.I just had the same problem. 1 I wiped down the stove surface NOPE 2 I pressed and held every button for 3 seconds NOPE 3 I SHUT OFF THE MAIN CURCUIT BREAKER !and that worked!!!! It started back up Solution: I'd in d0 mode for too long it gets stuck in d0 Simple design in future??? Install sensitivity know for "wet detection" can make counter have extreme wetness sensitivity to completely disengaged. My wife has threatened divorce over this stove because if anything spills on it it shuts off BUT u can still leave a dry 100 dollar pan on it and destroy it by leaving on the stove on low power all day
Sorry, there was a problem. Please try again later.I'm happy to help with this! The "d0" on the display is a "stuck button" error code. This means that the panel detects a button is being continuously touched. This can happen if the panel is wet or if something actually is continuously touching the panel. Make sure the panel is clear of any debris or water droplets, and then restart the cooktop using the Power button. If that does not resolve the issue, please reference ticket number 1143187484, and contact us directly through Facebook Messenger: http://m.me/samsungsupport; or Twitter: https://twitter.com/messages/compose?recipient_id=18768513. ^Jecca
Sorry, there was a problem. Please try again later.Buy a different cooktop. This error will keep occurring, and the even child lock doesn't prevent it entirely. This cooktop is so sensitive to any liquid on it that I strongly regret buying it.
Sorry, there was a problem. Please try again later.
