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
With the default of esp_light_sleep_start() I see WiFi connection problems.
Using delay() can still noticeably reduce the SoC temperature. In my limited testing, the temperature reported by CpuTemperature.read() reduced from ~58 °C to ~52 °C after enabling -D_TASK_SLEEP_ON_IDLE_RUN=1 and hacking it to use delay() instead of esp_light_sleep_start().
The text was updated successfully, but these errors were encountered:
Hi,
Which version of TaskSxheduler are you running.
I believe I disabled light sleep in the latest version since yes, it causes WiFi issues.
Simple delay(1) (or vTaskDelay(1) ) works better.
One problem with a simple delay is that when using StatusRequest to wake from an interrupt, the delay is not interrupted.
So for ESP32 even better is to use xTaskNotifyWait() to sleep and xTaskNotify()/xTaskNotifyFromISR() to interrupt the sleep.
ranma
changed the title
Using esp_light_sleep_start() can break WiFi, should be configurable to use delay() instead.
Using esp_light_sleep_start() can break WiFi, should be configurable to use delay()/xTaskNotifyWait() instead.
Oct 6, 2024
With the default of
esp_light_sleep_start()
I see WiFi connection problems.Using delay() can still noticeably reduce the SoC temperature. In my limited testing, the temperature reported by
CpuTemperature.read()
reduced from ~58 °C to ~52 °C after enabling-D_TASK_SLEEP_ON_IDLE_RUN=1
and hacking it to usedelay()
instead ofesp_light_sleep_start()
.The text was updated successfully, but these errors were encountered: