-
Notifications
You must be signed in to change notification settings - Fork 59
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Still having trouble #28
Comments
I have the ESP32 running for months (with 1 ping each ~10 mins). The only restarts I had (just a few) were when there were issues with WiFi and it was trying too many times to reconnect ... but there I suspect something with WiFi stack, not with the ping. |
Well... i´m pinging every 15 secs, maybe you need more time. I´m runing the code from a task in core 1, maybe there is a bug while running in the other core than core 0. I´m gonna try to move it to the core 0 (in the main loop) and tell you the results. |
Moved to the first core... and testing. By the way... the reason cause i´ve moved the function is the long time it takes, so, i moved the function to the second idle core. I´ve seen the default timeout is 1sec. Is there any way to decrease it for example 200ms? tnxs |
I´ve experimented the memmory leak issue a few months ago. I few days ago, i´ve noticed the problem was solved, and was fun for me. Cheking memmory, i ´ve seen no more running out memmory But, a new issue has arrived. After aproximately 8 hours of running program, the ESP32 restarts (whatchdog i guess). I know there is a library trouble, cause, increasing the time between pings the restart time increases too. Free memmory seems to be stable arround 170KB. And, of course, dissabling the ping call, the ESP32 never restarts. Any suggestions?
The text was updated successfully, but these errors were encountered: