how are you
Welcome to Flux
Treat Flux like your intern. Tell it what you'd like to build and it'll get to work. You can also ask it questions, brainstorm ideas, and teach it your preferences. Learn More
Explain project
Write a project description
Find schematic issues
Create a test plan
Simulate a circuit
Prepare for Manufacturing
Component Selection Workflow
New Subsystem Wizard
Write I2C initialization code
Generate firmware skeleton
Refine this doc
Ask about this doc
Power Architecture
Objective
Define the initial power architecture for the retro IoT radio concept with both plugged-in and rechargeable battery operation.
Product Context
- Wood-look tabletop radio
- Approximate width: 220 mm
- WiFi-enabled
- Bluetooth-enabled
- Streaming-ready
- Small center display
- Two front knobs
- Good quality audio target
- Rechargeable battery operation for a few hours when unplugged
Power Modes
External-Power Mode
- Device operates from an external power source when connected
- External power should be capable of supporting:
- system processing
- wireless connectivity
- display
- audio playback
- battery charging
Battery Mode
- Device operates from the onboard rechargeable battery when unplugged
- Battery mode shall support several hours of typical listening use
- Battery mode should preserve core playback and UI functions
Charge-and-Play Mode
- Device should be usable while the battery is charging
- Power-path behavior should avoid disruptive resets or audio interruptions during source transitions
Functional Power Blocks
External Power Input Block
Responsibilities:
- Accept external input power
- Provide input protection and system entry point
- Feed the battery charging / power-path stage
Battery Charging Block
Responsibilities:
- Charge the onboard rechargeable battery safely
- Manage battery charging while the system is powered
- Support rechargeable consumer-product usage
Battery / Protection Block
Responsibilities:
- Store energy for unplugged operation
- Provide battery protection appropriate to the chosen cell strategy
- Support safe integration inside the enclosure
System Rail Generation Block
Responsibilities:
- Generate the required regulated rails for:
- application processor / wireless subsystem
- display and UI logic
- audio subsystem as needed
- any always-on / low-power support rails
Audio Power Block
Responsibilities:
- Supply the audio amplifier subsystem
- Prevent audio artifacts due to poor rail management
- Coordinate with battery and external-power operating conditions
Preliminary Architectural Direction
- Use a rechargeable battery architecture suitable for consumer portable audio products
- Use integrated charging and power-path management rather than a simple charger-only approach
- Separate noisy audio-power and sensitive digital / RF power planning at the PCB level
- Plan for regulator choices that balance efficiency, thermal behavior, and audio noise performance
Key Requirements
- Support plugged-in operation
- Support battery-backed operation
- Support seamless or near-seamless source transition behavior
- Support charging during normal product use
- Support runtime of a few hours minimum, pending final battery sizing
- Support WiFi, Bluetooth, display, and audio subsystem peak loads
PCB / Layout Considerations
- Power entry should be physically organized for safe routing and thermal management
- Battery charging and protection circuitry should be isolated from sensitive audio paths where practical
- High-current paths should be short and appropriately sized
- Ground strategy should consider both RF/digital integrity and audio performance
- Battery connector and serviceability constraints must align with enclosure packaging
System-Level Risks to Resolve Later
- Final average and peak current budget
- Thermal rise during charging plus audio playback
- Battery capacity required for target runtime
- Whether a single-cell or multi-cell strategy is justified
- Required amplifier rail strategy versus available battery/input rails
- Low-battery behavior and shutdown thresholds
Open Decisions
- External power connector type
- Exact battery technology and pack format
- Charge current target
- Runtime target in hours
- Power budget by subsystem
- Number and voltage levels of regulated rails
- Need for fuel gauging or battery state reporting on the display
Relationship to Other Docs
This document should be refined alongside:
system-requirementsproduct-architectureui-controlsmechanical-front-panel-constraints
Next Engineering Step
Use this document to drive component selection for charger, battery path, regulators, and amplifier supply strategy during schematic development.
Objective
Product Context
Power Modes
External-Power Mode
Battery Mode
Charge-and-Play Mode
Functional Power Blocks
External Power Input Block
Battery Charging Block
Battery / Protection Block
System Rail Generation Block
Audio Power Block
Preliminary Architectural Direction
Key Requirements
PCB / Layout Considerations
System-Level Risks to Resolve Later
Open Decisions
Relationship to Other Docs
Next Engineering Step