M5Stack Cardputer Zero · Volume 5
M5Stack Cardputer Zero Volume 5 — Power Profile
Hypothesized smaller battery, charge subsystem, per-mode current draw, runtime estimates, budget-tier power discipline
Contents
| Section | Topic |
|---|---|
| 1 | About this volume |
| 2 | Battery — hypothesized capacity |
| 3 | Charge subsystem |
| 4 | Per-mode current draw (estimated) |
| 5 | Runtime estimates |
| 6 | Field-deployment power discipline |
| 7 | LiPo small-cell safety |
| 8 | Resources |
1. About this volume
Vol 5 covers Cardputer Zero’s hypothesized power profile. Smaller battery is the load-bearing assumption — budget variants typically cut battery capacity meaningfully, and the Zero is hypothesized to land in the 500-1000 mAh range (vs ADV’s 1750 mAh). This drives runtime estimates ~50% below the ADV’s.
Cross-reference: ../../../M5Stack Cardputer ADV/03-outputs/Cardputer_ADV_Complete.html Vol 6 (the Cardputer ADV’s power profile). This volume re-derives the numbers for Zero’s presumed smaller capacity.
2. Battery — hypothesized capacity
| Aspect | Hypothesis | Confidence | Notes |
|---|---|---|---|
| Chemistry | LiPo (single cell) | High | Industry standard |
| Capacity | 500-1000 mAh | Medium | Budget-tier sizing; ADV is 1750 mAh |
| Voltage | 3.7V nominal | High | Single-cell |
| Charge endpoint | 4.20V | High | Standard LiPo |
| Discharge cutoff | ~3.0V (protection IC) | High | Standard |
| Energy (700 mAh midpoint) | ~2.6 Wh | High (derived) | Reference value for planning |
| Energy (1000 mAh top) | ~3.7 Wh | High | Best-case |
| Energy (500 mAh bottom) | ~1.9 Wh | High | Worst-case |
2.1 Why the capacity range
The 500-1000 mAh range reflects M5Stack’s typical budget design choices:
- 500 mAh: aggressive cost cut; weight reduction; “Zero” tier
- 700 mAh: middle ground; M5StickS3 has 250 mAh as reference for very-small
- 1000 mAh: ~57% of ADV; meaningful capacity for several-hour use
The actual value depends on Zero’s intended use case. Education / classroom: smaller (1-2 hour sessions). Fleet ops: medium (3-4 hour shifts). General use: larger end of range.
2.2 Comparison to siblings
| Device | Battery | Energy | Typical runtime |
|---|---|---|---|
| M5StickS3 | 250 mAh | 0.9 Wh | ~2-3 hours mixed |
| Cardputer Zero (mid) | 700 mAh | 2.6 Wh | ~3-5 hours mixed (estimated) |
| Cardputer K132 | 1500 mAh | 5.6 Wh | ~5-7 hours mixed |
| Cardputer ADV | 1750 mAh | 6.5 Wh | ~6-8 hours mixed |
Zero sits between StickS3 and the larger Cardputers — about half a Cardputer’s typical runtime.
3. Charge subsystem
3.1 Likely topology
Standard single-cell LiPo handheld pattern (Vol 2 § 7):
USB-C 5V ──→ TP4056-class charger ──→ Battery
│
└→ Protection IC + MOSFET pair
(DW01+ / FS8205A typical)
│
▼
Battery (700 mAh nominal) ──→ Buck reg (SY8089) ──→ 3.3V bus3.2 Charge time
For a 700 mAh cell at 1 A charge:
- CC phase (3.0V → 4.20V): ~50 minutes (covers ~80% capacity)
- CV phase (4.20V hold to termination): ~15-20 minutes (last 20%)
- Total full charge: ~1-1.5 hours
Shorter than the ADV (which is ~2.5 hours for 1750 mAh). One of the few wins of a smaller battery.
3.3 Charge-while-operating
Standard charge-while-operating topology (Vol 2 § 7) — USB-C power feeds both the system and charge controller. With USB-C connected, internal battery stays at near-100% while the device runs. Useful for extended sessions.
4. Per-mode current draw (estimated)
Engineered estimates based on ESP32-S3 + standard handheld subsystem composition. Verify on hardware.
| Mode | Current (mA) | Notes |
|---|---|---|
| Deep sleep | 1-5 | Protection IC + leakage; very low |
| Light sleep (display off, Wi-Fi off) | 20-30 | LPC32-S3 light sleep mode |
| Menu navigation (display on, no Wi-Fi) | 60-80 | Display + backlight + CPU active |
| Wi-Fi scan | 120-180 | ESP32-S3 active + display |
| Wi-Fi connected, idle | 80-120 | Active connection without traffic |
| Wi-Fi active TX/RX | 200-300 | Variable based on traffic |
| BLE scan | 90-130 | Lower than Wi-Fi |
| microSD write | +30-50 | On top of base load |
| Speaker tone | +5-15 | PWM-driven low-current |
| All on (Wi-Fi scan + display + SD write) | 250-350 | Heaviest typical load |
4.1 Notes on the estimates
The Zero shouldn’t differ meaningfully from other ESP32-S3 + small-display handhelds at the same brightness setting. The values above are reasonable estimates from the family.
4.2 What’s lower vs the ADV
Some Zero-specific savings:
- No audio codec idle current (~5-10 mA saved vs ADV)
- No mic + amp idle (~3-5 mA saved)
- No IMU continuous sampling (~5-10 mA saved)
- Smaller backlight area if display is smaller (insignificant)
Total Zero savings vs ADV: ~15-25 mA in typical operation. Modest but additive.
5. Runtime estimates
Assuming 700 mAh nominal cell (mid-range estimate) and ~600 mAh usable capacity (after voltage cutoff margin):
| Mode | Current (mA) | Runtime |
|---|---|---|
| Deep sleep | 3 | ~200 hours (8+ days) |
| Light sleep | 25 | ~24 hours |
| Menu navigation | 70 | ~8.5 hours |
| Wi-Fi scan continuous | 150 | ~4 hours |
| Wi-Fi connected idle | 100 | ~6 hours |
| Wi-Fi active TX/RX | 250 | ~2.4 hours |
| BLE scan continuous | 110 | ~5.5 hours |
| All on (heaviest load) | 300 | ~2 hours |
For other capacities:
- 500 mAh: multiply by 0.71
- 1000 mAh: multiply by 1.43
5.1 Realistic mixed-use
A typical “Cardputer in your pocket” scenario:
| Activity mix | Avg current | Runtime |
|---|---|---|
| 80% idle / standby, 15% navigation, 5% scan | 50 mA | ~12 hours |
| 50% navigation, 30% scan, 20% idle | 100 mA | ~6 hours |
| 30% Wi-Fi active, 40% navigation, 30% idle | 130 mA | ~4.5 hours |
| Continuous Wi-Fi pentest workflow | 220 mA | ~2.7 hours |
Operational bottom line: Zero is a half-day device, not a full-day device. Plan engagements accordingly.
6. Field-deployment power discipline
For Zero used in field engagements:
6.1 Pre-deployment
- Charge to 100% before deployment
- Carry USB-C battery pack for any engagement >3 hours
- Pack USB-C cable
- Verify charging works before leaving
6.2 During engagement
- Dim display to 30-50% — saves ~30 mA continuous
- Use sleep mode when not actively using — Zero supports this if firmware is well-implemented
- Disable Wi-Fi when not needed — biggest single power saver
- Monitor battery indicator every 30-60 minutes
- Switch to USB-C pack when internal drops below 30%
6.3 Engagement length guidelines
| Duration | Internal battery only? | USB-C pack required? |
|---|---|---|
| <2 hours | Yes (with margin) | No |
| 2-3 hours | Yes (tight) | Recommended |
| 3-5 hours | No | Yes (5000 mAh minimum) |
| 5-8 hours | No | Yes (10000 mAh recommended) |
| 8+ hours | No | Yes (20000 mAh + opportunistic top-up) |
For comparison: ADV doubles all of these durations on internal alone.
7. LiPo small-cell safety
Smaller cells share the same safety concerns as larger ones, with one specific addition: higher discharge rate per nominal capacity under heavy load.
7.1 Standard discipline
- Don’t charge a swollen cell
- Don’t operate when wet
- Store at ~50% charge for long shelf life
- Operating temperature 0-40 °C
- Charging current ~1C (700 mA for a 700 mAh cell)
- Discharge cutoff at protection IC’s ~3.0V
7.2 Small-cell-specific concerns
- Faster discharge ratio: Wi-Fi peak currents (~300 mA) are ~0.5C on a 700 mAh cell — within spec but stresses the cell more than a 1750 mAh cell at the same load
- Less voltage headroom: smaller cells sag more under high current; brownouts more likely under aggressive load
- Less thermal mass: a small cell warms faster under heavy discharge; thermal management more delicate
- Replacement cost: smaller cells are sometimes cheaper, sometimes more proprietary (model-specific)
7.3 Longevity expectations
300-500 charge cycles before capacity drops to 80%. For a Zero charged daily: ~1-2 years before noticeable degradation. For weekly charging: ~5+ years.
7.4 Storage discipline for Zero
If Zero will sit unused for >2 weeks:
- Charge to ~50% (not 100% or empty)
- Store at room temperature (15-25 °C)
- Disconnect from USB if connected (no float-charge stress)
- Top up to ~50% every few months
8. Resources
- Cardputer ADV Vol 6 (power canonical):
../../../M5Stack Cardputer ADV/03-outputs/Cardputer_ADV_Complete.html - M5StickS3 Vol 11 (small-cell discipline reference):
../../../M5Stick S3/03-outputs/M5StickS3_Complete.html - Battery University: https://batteryuniversity.com/ (LiPo behavior canonical)
- TP4056 datasheet: NanJing TopPower
End of Vol 5. Next: Vol 6 covers the firmware ecosystem — what Zero inherits from the Cardputer family, what’s restricted vs ADV, and what budget-tier firmware authoring looks like.