Hello,
Help Needed. I am starting to design a circuit that is a door lock system. However, It will be battery Powered and I am expecting it to last 1 Year at least using a 3.7V 2500mAH battery. My problem is, if it is continuously connected to the wifi 24x7, it will not last long due to the Power consumption of ESP32. I could not make it sleep as someone will send door unlock or lock command it needs to be received by it.
I am expecting 10-15 lock-unlock events entire day. How can I reduce the current consumption of ESP32? This is the most power hungry system in my application. For all other devices, such as motor, sensors, all will be disconnected from power source until or unless I receive the command from wifi.
Achieving Low Power while using the WiFi
Re: Achieving Low Power while using the WiFi
Most of the locks on the market use plug in wifi bridges. The eufy lock that uses wifi has a 10Ah battery to last 12 months.
Re: Achieving Low Power while using the WiFi
This thread may be of interest
https://www.esp32.com/viewtopic.php?t=12067
https://www.esp32.com/viewtopic.php?t=12067
Re: Achieving Low Power while using the WiFi
I had another look at this today out of interest, as there have been significant improvements to light sleep since my comment in the linked thread - average ESP32 light sleep current now settles <400uA with the right config.
With a very high listen interval of 30 (ie. max ~3 seconds between receiving queued up packets from the router), I'm seeing about 850-1100uA average current now with WiFi connected. That's pretty good, but you're still going to chew through your battery in less than half the target time, and that's without the motor, sensors, interface, etc.
There's a TCP task waking the ESP32 every 500ms though, which isn't helping. Might be a bug? Giving this task a much higher timeout, and setting the listen interval to 50, average current can go as low as 600uA while maintaining a WiFi connection.
ESP32-WROOM-32D, ebf7e811b12e3c1e347340e5b9ec014e9c6319ba
With a very high listen interval of 30 (ie. max ~3 seconds between receiving queued up packets from the router), I'm seeing about 850-1100uA average current now with WiFi connected. That's pretty good, but you're still going to chew through your battery in less than half the target time, and that's without the motor, sensors, interface, etc.
There's a TCP task waking the ESP32 every 500ms though, which isn't helping. Might be a bug? Giving this task a much higher timeout, and setting the listen interval to 50, average current can go as low as 600uA while maintaining a WiFi connection.
ESP32-WROOM-32D, ebf7e811b12e3c1e347340e5b9ec014e9c6319ba
Who is online
Users browsing this forum: Baidu [Spider] and 37 guests