Remote Blinds Control Design
Thought for 20 sec
I’ll design this as a two-board system: a handheld Li-ion remote and a motor-driver receiver, both with 5 V power architecture, Li-ion charging, and ESP-NOW wireless. I’ll first capture the requirements and power budget, then select parts, build/wire the schematic blocks, and run checks.
Worked for 1 min 21 sec
I updated the project specification to reflect the new blind-control remote/receiver system: two PCBs, ESP-NOW wireless, Li-ion battery support, USB-C charging, 5 V boost rails, and receiver-side motor control.
I also captured the key power-risk assumption: the receiver boost/battery path is provisionally sized around a 5 V motor up to ~2 A peak, which could require nearly 4 A from the Li-ion cell at low battery voltage. The actual motor stall current is the main missing requirement before final component selection.
Remaining work:
- Select charger, boost converter, ESP32 module, motor driver, connectors, and support passives.
- Consult datasheets for every IC.
- Add and wire the full schematic for both boards.
- Run design review/ERC and fix violations.
- After schematic is clean, proceed to layout only with confirmation.
Use ESP-NOW
Select key parts
Add charging circuit
Power budget
Document motor assumption
No schematic yet
Talk to Flux to get started.
Refine this doc
Ask about this doc
Project Specification
Project Overview
Status: Draft.
Two-board wireless blind-control system consisting of a handheld remote and a receiver/motor-controller unit. Both boards support a single-cell 3.7 V Li-ion battery, USB-C charging, and a regulated 5 V rail. The receiver drives a DC blind motor in open/close/stop directions; the remote sends commands wirelessly.
Intended Use
Indoor consumer blind control for hobby/prototype builds, with production-intent SMD electronics unless later changed. The remote is handheld and battery-powered. The receiver mounts near the blind motor and can run from battery or USB-C/5 V power while charging.
What the Device Should Do
- Remote sends Open, Close, Stop, and optional preset/learn commands wirelessly.
- Receiver validates commands and drives the blind motor forward/reverse with braking/coast control.
- Both boards operate from a 3.7 V Li-ion cell and generate regulated 5 V.
- Both boards charge the Li-ion cell from USB-C 5 V.
- Receiver provides motor current/limit-sense inputs where practical to reduce stall risk.
- Include firmware programming/debug access and status indication.
Main Features
- Wireless control using ESP32-family modules and ESP-NOW over 2.4 GHz Wi-Fi for low-latency peer-to-peer commands.
- Li-ion charger and power-path architecture for USB/battery operation.
- 5 V boost rail from Li-ion battery.
- 3.3 V rail for ESP32 logic derived from 5 V or a dedicated regulator.
- Receiver H-bridge motor driver for bidirectional 5 V DC blind motor.
- Remote button inputs and status LED.
- Receiver motor connector, optional limit switch connector, and status LED.
System Architecture
Diagram
Hardware Subsystems
- Remote power: USB-C sink input, Li-ion charger/power path, 5 V boost, 3.3 V logic rail, battery connector/protection.
- Remote control: ESP32-C3/S3 class module, buttons for open/close/stop, status LED, boot/reset/programming access.
- Receiver power: USB-C sink input, Li-ion charger/power path, higher-current 5 V boost sized for motor stall current, 3.3 V logic rail.
- Receiver motor control: H-bridge motor driver with bidirectional control, motor connector, bulk capacitance, flyback/driver protections per datasheet.
- Wireless: ESP-NOW selected over BLE/433 MHz because it is low-latency, packet-based, and keeps both ends on the same ESP32 platform.
- Safety/protection: USB-C CC pull-downs, input ESD, battery protection assumptions, motor bulk capacitance, current/limit sensing if supported.
Interfaces and Connections
- Remote: USB-C 5 V charge/programming connector, Li-ion cell connector, buttons, status LED, optional UART/USB programming header.
- Receiver: USB-C 5 V charge/power connector, Li-ion cell connector, motor output connector, optional open/close limit switch connector, programming/debug header, status LED.
- Wireless: ESP-NOW peer-to-peer command packets with pairing/learn function.
- Internal rails: VBAT, SYS/charger output, 5V, 3V3, GND.
Power and Runtime Expectations
- Battery: single-cell Li-ion nominal 3.7 V, operating range assumed 3.0 V to 4.2 V.
- Remote: low average current; deep sleep between button presses for long battery life.
- Receiver: idle low power, high peak current during motor movement; motor runtime and battery size depend strongly on motor stall/load current.
- USB-C: default 5 V sink, no USB-PD in first revision.
Power Tree and Preliminary Power Budget
Assumptions pending selected datasheets and motor specification:
Table
| Board | Rail | Load | Typical | Peak / sizing target |
|---|---|---|---|---|
| Remote | 3.3 V | ESP32 radio TX | 80-180 mA | 350-500 mA transient |
| Remote | 3.3 V | LEDs/buttons | =500 mA transient | |
| Receiver | 3.3 V | ESP32 radio/control | 80-180 mA | 350-500 mA transient |
| Receiver | 5 V | Blind motor | unknown | design placeholder 1.5-2.0 A peak until motor current is known |
| Receiver | 5 V | Motor driver logic/losses | tens of mA | driver-dependent |
Boost input worst case for receiver at 5 V, 2 A motor peak from 3.0 V Li-ion at 85% efficiency: Ibat ~= (5 V * 2 A) / (3.0 V * 0.85) = 3.9 A. Receiver battery connector, boost converter, switch, and protection path must be sized for this until the actual motor stall current is specified.
Manufacturing and Assembly Expectations
- SMD design by default.
- Prefer integrated RF ESP32 modules to avoid custom RF matching.
- Use stocked, non-EOL parts where possible.
- Include test points for VBAT, 5V, 3V3, GND, motor outputs, boot/reset, and key GPIO.
Firmware-Relevant Hardware Requirements
- ESP-NOW transmitter/receiver firmware.
- Remote deep sleep with GPIO wake from buttons.
- Receiver motor state machine with timeout and optional limit switch/current fault handling.
- Pairing/learn function and persistent peer address storage.
- Boot/reset access for both ESP32 modules.
Physical Design Expectations
- Two separate PCB layouts are expected: compact handheld remote and receiver motor board.
- ESP32 module antennas placed at board edges with antenna keepout.
- Receiver motor power traces/copper sized for actual motor current.
- Receiver bulk capacitors close to the motor driver and boost output.
- USB-C connectors on board edges; motor connector accessible at receiver edge.
Important Design Decisions
- Use ESP-NOW rather than BLE for simple low-latency remote commands between two ESP32 boards.
- Use ESP32-C3/S3 modules rather than discrete RF designs.
- Use single-cell Li-ion plus boost to 5 V because the user requires 3.7 V Li-ion support and 5 V operation.
- Receiver power path is motor-current-limited; actual motor stall current must be confirmed before final component sizing.
Assumptions
- Motor is a 5 V DC brushed blind motor, not a stepper or mains AC motor.
- Target motor peak/stall current is temporarily assumed 2 A maximum until specified.
- USB-C is 5 V default sink only, no USB-PD.
- SMD assembly is acceptable.
- Two PCBs in one project are acceptable for schematic architecture; layout may need separate board handling/forking later.
Change Notes
- Replaced the previous environmental sensor spec with the requested wireless blind remote/receiver design.
- Added Li-ion charging, 5 V boost rails, ESP-NOW wireless, and receiver motor-control requirements.
Project Overview
Intended Use
What the Device Should Do
Main Features
System Architecture
Hardware Subsystems
Interfaces and Connections
Power and Runtime Expectations
Power Tree and Preliminary Power Budget
Manufacturing and Assembly Expectations
Firmware-Relevant Hardware Requirements
Physical Design Expectations
Important Design Decisions
Assumptions
Change Notes
