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
So far it appears this library will almost drop in working on an ESP8266.
Unfortunately, (or fortunately?) this module (and the ESP32) has a software and hardware watchdog timers. This causes the module to reboot if the timer isn't fed.
The begin function for this library uses so many timeouts and delays that it's darn near impossible to trigger a full startup before the watchdog timer triggers.
I'm thinking that the begin should be drastically reduced, and a new startup function be created with an internal counter - in that it does each step within each run of the loop() method. Thus, the WDT could be fed between each step allowing for the maximum time for each command to run.
There might be better ways to solve this, I'm just starting trying to get this to work.
The text was updated successfully, but these errors were encountered:
So far it appears this library will almost drop in working on an ESP8266.
Unfortunately, (or fortunately?) this module (and the ESP32) has a software and hardware watchdog timers. This causes the module to reboot if the timer isn't fed.
The begin function for this library uses so many timeouts and delays that it's darn near impossible to trigger a full startup before the watchdog timer triggers.
I'm thinking that the begin should be drastically reduced, and a new startup function be created with an internal counter - in that it does each step within each run of the loop() method. Thus, the WDT could be fed between each step allowing for the maximum time for each command to run.
There might be better ways to solve this, I'm just starting trying to get this to work.
The text was updated successfully, but these errors were encountered: