Schufti, I think that's a typographical error in the current API Reference, section 3.3.9 for system_deep_sleep. I'll see if it wakes 67 minutes from now. 'Toto, I've a feeling we're not in Kansas any more.'Īfter hitting it with 10-12 RESETs, it finally went to sleep. It didn't hit the next line in my other program, a Serial.println(), and it didn't reboot so it's off in some strange place in the code, likely stuck in a blind end in the SDK.

I'd have to fire up a debugger to see where the CPU went to after that Deep Sleep command. It stopped responding and yet the WiFi connected (stored connection) and it responds to pings if I use the same Deep Sleep command in another program that enables WiFi. It usually doesn't go into Deep Sleep, but I don't know exactly what it DOES do. deepSleep(deepSleepMax, WAKE_RF_DISABLED) So the ~12000s returned by deepSleepMax() should be safe ? Indicates a 32bit timer, then the max sleep time would be 0xFFFFFFFF * periode giving something between 21474.8 to 30064.8 s. The theoretical maximum value of time_in_us can be calculated by formula: For more details about the cali, please see the API: system_rtc_clock_cali_proc (c.f 3.3.50)Ĭali translates to values in the range 5lastest SDK document is - regarding max deep sleep and cali_proc - even more questionable than the ones before.

Esp32 from time import deepsleep