I want a simplest possible schematic that allows m...

I’ll check suitable AA battery-holder options, then update the schematic so the battery pack is the 9V input source and verify the power ERC afterward.
Yes — for the existing 9V motor rail, the right AA approach is six AA cells in series. I didn’t find a single 6×AA holder in the library, so I’m using a 4×AA holder plus a 2×AA holder wired in series for 9V nominal alkaline output.
Implemented the AA battery power update: added BT1 4×AA + BT2 2×AA in series as a 6×AA pack, wired to V9_MOTOR/GND through restored battery input terminal J2, and kept the holders as external/off-board parts. Updated the project files and verified ERC plus key placement/DRC checks are clean.
Open items:
  • 6× alkaline AA = ~9V nominal; 6× NiMH AA = ~7.2V nominal, so 9V motors may run slower on rechargeables.
  • Confirm motor stall current and AA cell discharge capability before relying on four motors at once.
Suggested next steps:
  1. Add an input fuse/polyfuse for battery short-circuit protection.
  2. Add reverse-polarity protection for the battery input.
  3. Re-check layout/routing with the restored J2 battery connector.
Add protections and verify
Add input fuse
Add reverse protection
Check battery current
Re-check layout

Refine this doc
Ask about this doc
Project Specification — Remote Pico Controller
Project Overview
Status: Draft schematic complete / ready for ERC review and layout planning.
Remote Pico Controller is a Raspberry Pi Pico HAT-style board that seats a Pico module, adds UART WiFi through an ESP-01S module, and switches up to four external 9V DC motors from Pico GPIOs.
Intended Use
  • Prototype / hobby robotics or remote-actuator controller.
  • An external 6xAA battery pack connects through the battery-input screw terminal. With alkaline cells this is 9V nominal; with NiMH rechargeable cells it is about 7.2V nominal.
  • Up to four 9V brushed DC motors connect through individual screw terminals.
  • The Pico firmware sends AT commands to the ESP-01S over UART for WiFi communication.
What the Device Should Do
  • Power the Raspberry Pi Pico from the 9V input through a 5V buck regulator into Pico VSYS.
  • Power the ESP-01S from a dedicated 3.3V regulator.
  • Allow the Pico to communicate with the WiFi module using GP0/GP1 UART.
  • Independently switch four 9V motor outputs using:
    • Motor 1: GP18
    • Motor 2: GP19
    • Motor 3: GP20
    • Motor 4: GP21
Main Features
  • Pico socket / footprint representation: J1.
  • ESP-01S UART WiFi module: U1.
  • 9V input screw terminal: J2.
  • Motor screw terminals: J3J6.
  • Four low-side MOSFET motor switches: Q1Q4.
  • Four flyback diodes: D1D4.
  • 9V-to-5V buck regulator: U2.
  • 5V-to-3.3V WiFi regulator: U3.
System Architecture

Table


BlockComponentsPurpose
Pico socketJ1Seats/represents the Raspberry Pi Pico and exposes required GPIO/power pins.
WiFiU1, R1R4, C9, C10ESP-01S UART WiFi interface and boot pull-ups.
Power inputBT1, BT2, J2, C5External 6xAA battery pack represented as 4xAA + 2xAA holders in series, connected through the battery-input terminal, plus bulk input capacitance.
5V logic powerU2, L1, C1C4, C6Buck conversion from 9V to 5V for Pico VSYS and WiFi LDO input.
3.3V WiFi powerU3, C7, C8Local 3.3V regulator for ESP-01S.
Motor outputsQ1Q4, D1D4, R5R12, J3J6Four independent low-side motor switches.
Interfaces and Connections

Table


InterfaceSchematic Net / PinsNotes
AA battery inputBT1 + BT2 in series, connected through J2; J2:1 = V9_MOTOR, J2:2 = GND6xAA pack: 9V nominal alkaline or about 7.2V nominal NiMH.
Pico powerV5 to J1:VSYSDo not drive Pico VBUS; avoids USB backfeed.
WiFi UARTJ1:GP0 -> U1:RXD, U1:TXD -> J1:GP13.3V UART logic.
Motor 1J3, Q1, D1, GP18Low-side switch; motor positive tied to V9_MOTOR.
Motor 2J4, Q2, D2, GP19Low-side switch.
Motor 3J5, Q3, D3, GP20Low-side switch.
Motor 4J6, Q4, D4, GP21Low-side switch.
Power Tree and Power Budget

Table


RailSourceLoadsDesign Limit / Assumption
V9_MOTOR6xAA pack (BT1 + BT2) via J2Motor positives, U2 VIN9V nominal with alkaline AA cells; about 7.2V nominal with NiMH. Net metadata remains up to 12A total / 3A per motor channel assumption, but real AA pack current and motor stall current must be verified.
V5U2 LMR50410Y5 buckPico VSYS, U3 VINU2 is a 1A fixed 5V buck.
V3V3_WIFIU3 AP2112K-3.3ESP-01S and boot pull-upsU3 is 600mA max; ESP-01S peak current is ~300mA per datasheet.
Manufacturing and Assembly Expectations
  • Schematic is suitable for a simple two-layer prototype after layout rules are set for motor current.
  • Motor traces and ground returns must be sized for the real motor stall current.
  • ESP-01S antenna keepout must be respected during layout.
  • Through-hole screw terminals and TO-220 MOSFETs are used for easy wiring and current handling.
Firmware-Relevant Hardware Requirements

Table


FunctionGPIOFirmware Use
ESP UART TX from PicoGP0Pico UART TX to ESP RXD.
ESP UART RX to PicoGP1Pico UART RX from ESP TXD.
Motor 1GP18Digital or PWM output.
Motor 2GP19Digital or PWM output.
Motor 3GP20Digital or PWM output.
Motor 4GP21Digital or PWM output.
Important Design Decisions
  • Use ESP-01S instead of a full WiFi MCU because the Pico remains the controller and communicates over simple UART.
  • Use low-side MOSFET switches for simplest motor control; this supports on/off and PWM speed control but not direction reversal.
  • Use a buck regulator, not a linear regulator, from 9V to 5V to avoid unnecessary heat.
  • Use a separate 3.3V regulator for ESP-01S instead of relying on the Pico 3.3V output.
Assumptions
  • Motors are unidirectional brushed DC motors.
  • Motor current is not yet specified; current metadata assumes up to 3A/channel, but actual stall current must be confirmed before layout/manufacturing.
  • The ESP-01S will run AT firmware at 115200 baud unless changed by firmware.
  • The 9V input is externally protected or current-limited unless input protection is added in a later revision.
Open Items
  • Confirm motor running and stall current, and confirm the selected AA cells can supply the required startup/stall current without excessive voltage sag.
  • Decide whether to add input fuse, reverse-polarity protection, and TVS clamp before layout.
  • Decide whether to add current sensing or diagnostic test points.
  • Validate thermal margin for U3 if ESP WiFi transmit duty cycle is high.
Change Notes
  • Project renamed to Remote Pico Controller.
  • Initial schematic built with Pico socket, ESP-01S WiFi, 9V input, 5V/3.3V rails, and four GP18–GP21 motor channels.
  • Project Overview

  • Intended Use

  • What the Device Should Do

  • Main Features

  • System Architecture

  • Interfaces and Connections

  • Power Tree and Power Budget

  • Manufacturing and Assembly Expectations

  • Firmware-Relevant Hardware Requirements

  • Important Design Decisions

  • Assumptions

  • Open Items

  • Change Notes

Documents

  • Project Specification — Remote Pico Controller

  • Design Notes and Power Budget — Remote Pico Controller

  • Firmware Starter — Raspberry Pi Pico / ESP-01S Motor Controller

  • Board Bring-Up Plan — Remote Pico Controller

  • Regulatory and Safety Notes — Remote Pico Controller

  • Preliminary FMEA — Remote Pico Controller

Assets

Assets are files uploaded to this project which can be used in various ways.

Remote Pico Controller thumbnail
Raspberry Pi Pico HAT for WiFi communication and independent control of up to four 9V motors from GPIO GP18-GP21.

Properties

Properties describe core aspects of the project.

Pricing & Availability

Distributor

Qty 1

Arrow

$8.88–$16.52

Digi-Key

$15.48

HQonline

$4.63

LCSC

$23.80–$23.85

Mouser

$18.27

TME

$13.82

Verical

$3.68–$11.37

Controls