You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Very rare times board stops to response. I made small investigation on my own branch version of SW - it stucks somewhere inside SDK client function calls and no WDT fires occurs. I thought about external watchdog IC, but after found proper google request I found that solution: esp8266/Arduino#1532
It not tested by years, but looks fine and extra WDT should not be a problem. I just want to advice it to implement.
Thanks for your project!
PS: Also ESP8622 not supports WDT period customization, Im not sure about ESP32. But you trying to define it in the code, it can confuse someone)
The text was updated successfully, but these errors were encountered:
A WDT is never a real solution. It is always a workaround which might help in special cases, but hide more severe problems which don't get detected for a long time.
Can you please provide more information?
Did you compile the firmware yourself?
If yes, did you use the Arduino IDE or VisualStudio Code?
Which firmware version do you use?
How is your configuration?
Which sensors, APIs and LCDs do you have enabled (the easiest way is to save the config and copy the resulting web-page as text)?
Very rare times board stops to response. I made small investigation on my own branch version of SW - it stucks somewhere inside SDK client function calls and no WDT fires occurs. I thought about external watchdog IC, but after found proper google request I found that solution:
esp8266/Arduino#1532
It not tested by years, but looks fine and extra WDT should not be a problem. I just want to advice it to implement.
Thanks for your project!
PS: Also ESP8622 not supports WDT period customization, Im not sure about ESP32. But you trying to define it in the code, it can confuse someone)
The text was updated successfully, but these errors were encountered: