Stories
Slash Boxes
Comments

SoylentNews is people

posted by martyb on Monday December 17 2018, @08:01PM   Printer-friendly
from the plug-it-in dept.

Hackaday:

The Internet of Things is eating everything alive, and the world wants to know: how do you make a small, battery-powered, WiFi-enabled microcontroller device? This is a surprisingly difficult problem. WiFi is not optimized for low-power operations. It’s power-hungry, and there’s a lot of overhead. That said, there are microcontrollers out there with WiFi capability, but how do they hold up to running off of a battery for days, or weeks? That’s what [TvE] is exploring in a fantastic multi-part series of posts delving into low-power WiFi microcontrollers.

The idea for these experiments is set up in the first post in the series. Basically, the goal is to measure how long the ESP8266 and ESP32 will run on a battery, using various sleep modes. Both the ESP8266 and ESP32 have deep-sleep modes, a ‘sleep’ mode where the state is preserved, a ‘CPU only’ mode that turns the RF off, and various measures for sending and receiving a packet.

The takeaway from these experiments is that a battery-powered ESP8266 can’t be used for more than a week without a seriously beefy battery or a solar panel.

Power consumption and battery life remain limitations for IoT applications. How can they be overcome?


Original Submission

 
This discussion has been archived. No new comments can be posted.
Display Options Threshold/Breakthrough Mark All as Read Mark All as Unread
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
  • (Score: 5, Interesting) by coolgopher on Tuesday December 18 2018, @12:24AM

    by coolgopher (1157) on Tuesday December 18 2018, @12:24AM (#775651)

    Haven't read the article(s), but if they're only getting a week out of it, they're doing it wrong. At $work we're using the ESP8266 for one of our products, and on a standard (good quality) 18650 battery we get a year, sampling every 30sec, uploading once an hour or so. If we upload less frequently, we can easily extend it a year and a half, at which point the self-discharge of the battery is becoming quite significant in its own right. This is on a combination of pure C and NodeMCU [github.com] for the higher-level logic (which only gets booted when we need WiFi).

    If you're on battery, you have to approach the solution with that constraint as the first and foremost. The what-appears-to-be-typical attitude of glue-high-level-components-together-until-it-kinda-works doesn't fly in this space. Not if you want things to not run out of juice in a hurry.

    Starting Score:    1  point
    Moderation   +3  
       Interesting=2, Informative=1, Total=3
    Extra 'Interesting' Modifier   0  
    Karma-Bonus Modifier   +1  

    Total Score:   5