agentleFS
wedsamuel1230wedsamuel1230/embedded-engineering-skills/skills/power-budget-calculator/SKILL.md

power-budget-calculator

Skill28 starsChanged 31 days agoMITView on GitHub

Calculates total power consumption and battery life for Arduino/ESP32/RP2040 projects. Use when user asks about battery life, power requirements, current draw, or needs to estimate runtime. Includes sleep mode analysis, power optimization tips, and battery sizing recommendations. Run scripts/calculate_power.py for accurate calculations.

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

4 rules. About 0 are common, 3 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Run the calculator interactively:

    line 19
  2. Distinctive:

    All sensors and modules

    line 52
  3. Very specific:

    Run scripts/calculate_power.py --interactive for guided calculation, or use this template:

    line 60
  4. Distinctive:

    Use the shared Arduino skill contract: state assumptions, required tools and versions, implementation steps, tests/evidence by proof stage, …

    line 369

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Power Budget Calculator

Estimates power consumption and battery life for embedded projects.

Resources

  • scripts/calculate_power.py - Python calculator with component database, duty cycle support, battery life estimation
  • references/component-database.md - Comprehensive current draw reference from datasheets
  • assets/example-project.json - Sample project configuration

Quick Start

Run the calculator interactively:

uv run --no-project scripts/calculate_power.py --interactive

Or calculate for a single component:

uv run --no-project scripts/calculate_power.py --component ESP32 --mode deep_sleep --duty 95

Load a project configuration:

uv run --no-project scripts/calculate_power.py --json assets/example-project.json --output report.md

List all components in database:

uv run --no-project scripts/calculate_power.py --list

When to Use

  • "How long will my battery last?"
  • "What size battery do I need?"
  • "How much current does my project draw?"
  • Planning battery-powered projects
  • Optimizing for low power

Workflow

Step 1: Gather Component List

Ask user for:

  1. Microcontroller (model and operating mode)
  2. All sensors and modules
  3. Displays
  4. Actuators (motors, LEDs, relays)
  5. Communication (WiFi, Bluetooth, LoRa)
  6. Operating profile (always on vs. duty cycle)

Step 2: Calculate Power Budget

Run scripts/calculate_power.py --interactive for guided calculation, or use this template:

# Power Budget: [Project Name]

## Operating Conditions
- Supply Voltage: [V]
- Operating Modes: [Active/Sleep cycles]
- Duty Cycle: [X% active, Y% sleep]

## Component Current Draw

### Always-On Components
| Component | Voltage | Current | Power | Notes |
|-----------|---------|---------|-------|-------|
| [name] | [V] | [mA] | [mW] | [conditions] |
| ... | ... | ... | ... | ... |
| **Subtotal** | - | **[mA]** | **[mW]** | - |

### Active Mode Only
| Component | Voltage | Current | Power | Duty % |
|-----------|---------|---------|-------|--------|
| [name] | [V] | [mA] | [mW] | [%] |
| ... | ... | ... | ... | ... |
| **Subtotal** | - | **[mA]** | **[mW]** | - |

### Peak Current Events
| Event | Current | Duration | Frequency |
|-------|---------|----------|-----------|
| [WiFi TX] | [mA] | [ms] | [per hour] |
| ... | ... | ... | ... |

## Power Calculations

### Average Current

I_avg = (I_active × t_active + I_sleep × t_sleep) / t_total I_avg = ([X]mA × [Y]s + [Z]mA × [W]s) / [T]s I_avg = [result] mA


### Battery Life Estimate

Capacity: [X] mAh Efficiency factor: 0.8 (80% usable) Effective capacity: [X × 0.8] mAh

Runtime = Effective capacity / I_avg Runtime = [X] mAh / [Y] mA Runtime = [Z] hours ([days] days)


## Recommendations
- [Power optimization suggestions]
- [Battery type recommendation]
- [Sleep mode configuration]

Current Draw Database

Microcontrollers

Arduino (ATmega328P @ 5V)

ModeCurrentNotes
Active (16MHz)15-20mANo peripherals
Idle6mACPU stopped, peripherals on
Power-down0.1µAOnly WDT/external interrupt
With USB-Serial+50mACH340/FTDI chip always on

ESP32 (WROOM-32)

ModeCurrentNotes
Active (WiFi TX)160-260mAPeak during transmission
Active (WiFi RX)95-100mAListening
Active (no WiFi)20-68mACPU only
Modem-sleep20mAWiFi off, CPU on
Light-sleep0.8mACPU paused
Deep-sleep10µARTC only
Hibernation5µARTC off

ESP32-C3

ModeCurrentNotes
Active (WiFi TX)320mA peakBrief spikes
Active (BLE)50-100mADuring advertising
Active (no radio)25-35mACPU at 160MHz
Light-sleep130µAAuto wake
Deep-sleep5µARTC on

RP2040 (Pico)

ModeCurrentNotes
Active (both cores)25-50mADepends on clock
Single core15-25mAOne core dormant
Dormant0.18mAWake on GPIO/RTC
Sleep1.3mA

RP2040 (Pico W)

ModeCurrentNotes
WiFi active50-150mADuring TX
WiFi idle30-40mAConnected, listening
WiFi off25-50mARadio disabled

Sensors

SensorActiveSleepNotes
DHT221.5mA50µADuring read
BME2800.35mA0.1µAForced mode
BMP2800.27mA0.1µA
MPU60503.8mA5µAAll axes
DS18B201.5mA1µADuring conversion
HC-SR0415mA2mANo true sleep
VL53L0X19mA5µADuring ranging
MAX30102600µA0.7µALow power mode
BH1750120µA1µAPower down mode
GPS (NEO-6M)45mA11mABackup mode

Displays

DisplayActiveOff/SleepNotes
16x2 LCD (backlight)80-120mA1mABacklight dominates
16x2 LCD (no backlight)1-2mA1mA
SSD1306 OLED 128x648-20mA10µADepends on content
SSD1306 OLED 128x325-15mA10µA
ST7735 TFT20-40mA20mABacklight always on
ILI9341 TFT50-80mA50mA
E-Paper 2.9"8mA0µAOnly during refresh

Communication Modules

ModuleTX PeakRX/IdleSleepNotes
ESP8266 (module)170mA70mA20µADeep sleep
NRF24L0111.3mA13.5mA0.9µA
HC-05 Bluetooth40mA8mA2mA
RFM95 LoRa120mA10mA0.2µA
SIM800L GSM2A peak15mA1mANeeds big cap!

Actuators

ComponentCurrentNotes
LED (typical)10-20mAThrough resistor
RGB LED (each color)20mAPer channel
WS2812B NeoPixel60mA maxFull white
SG90 Servo (idle)10mANo load
SG90 Servo (moving)200-500mAUnder load
MG996R Servo500-900mAUnder load
Small DC motor100-500mAVaries with load
5V Relay module70-100mACoil energized
Buzzer (passive)30mA

Sleep Mode Configurations

ESP32 Deep Sleep Template

#include <esp_sleep.h>

#define uS_TO_S_FACTOR 1000000ULL
#define TIME_TO_SLEEP 60  // seconds

void setup() {
    // Do measurements here
    
    // Configure wake-up source
    esp_sleep_enable_timer_wakeup(TIME_TO_SLEEP * uS_TO_S_FACTOR);
    
    // Enter deep sleep
    esp_deep_sleep_start();
}

void loop() {
    // Never reached
}

Arduino Power-Down Template

#include <avr/sleep.h>
#include <avr/wdt.h>

void enterSleep() {
    set_sleep_mode(SLEEP_MODE_PWR_DOWN);
    sleep_enable();
    sleep_mode();  // Sleep here
    sleep_disable();
}

// Wake on watchdog or external interrupt
ISR(WDT_vect) {
    // Wake up
}

Power Optimization Checklist

Hardware

  • Remove power LED (saves 5-10mA)
  • Remove USB-Serial chip for battery operation
  • Use LDO with low quiescent current (<10µA)
  • Add MOSFET to power-gate high-current peripherals
  • Use pull-downs on unused pins
  • Disable ADC when not reading

Software

  • Use sleep modes between readings
  • Reduce clock speed if possible
  • Batch data and transmit less frequently
  • Turn off WiFi/BLE when not needed
  • Disable brown-out detector in deep sleep
  • Use interrupts instead of polling

Design Patterns

Power Gating:

       VCC
        │
    [P-MOSFET] ← GPIO (LOW = ON)
        │
    [Sensor/Module]
        │
       GND

Duty Cycling Formula:

I_average = (I_active × T_active + I_sleep × T_sleep) / T_total

Example: Sensor reads every 5 minutes
- Active: 50mA for 2 seconds
- Sleep: 10µA for 298 seconds

I_avg = (50mA × 2s + 0.01mA × 298s) / 300s
I_avg = (100 + 2.98) / 300
I_avg = 0.34mA

With 2000mAh battery:
Runtime = 2000mAh × 0.8 / 0.34mA = 4706 hours = 196 days

Battery Reference

Common Battery Types

TypeVoltageTypical CapacityNotes
CR20323V220mAhVery low current only
2x AA Alkaline3V2500mAhGood for low power
3x AA Alkaline4.5V2500mAhDirect to 5V systems
4x AA Alkaline6V2500mAhWith LDO to 5V
18650 Li-ion3.7V2000-3500mAhRechargeable, popular
LiPo 1S3.7VVariousFlat, light
9V Alkaline9V500mAhPoor energy density

Voltage Over Discharge

18650/LiPo Discharge Curve:

Capacity%   Voltage
─────────────────────
100%        4.2V
80%         3.9V
50%         3.7V
20%         3.5V
0%          3.0V (cut-off!)

Never discharge below 3.0V - damages cell!

Alkaline AA Discharge:

Capacity%   Voltage (per cell)
─────────────────────────────
100%        1.5V
50%         1.2V
0%          0.9V

Many devices stop working below 1.1V/cell

Quick Calculator

Enter your values:

Always-on current: ______ mA
Active current: ______ mA
Active time: ______ seconds
Sleep current: ______ mA  
Sleep time: ______ seconds
Battery capacity: ______ mAh

Average current = (Active_mA × Active_s + Sleep_mA × Sleep_s) / Total_s
                = (_____ × _____ + _____ × _____) / _____
                = _____ mA

Runtime = Capacity × 0.8 / Average_current
        = _____ × 0.8 / _____
        = _____ hours
        = _____ days

Shared Output Contract

Use the shared Arduino skill contract: state assumptions, required tools and versions, implementation steps, tests/evidence by proof stage, known limitations, and recovery/security notes.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.