jr98 / ESP32 ROBOT CONTROLLER

Loaded

210

Files

Schematic

PCB

Log InSign Up

Modelo de Creación de Pasos

flux

1:42

Running design review.

Analyzing the schematic.

Analyzing the schematic.

Linking components effectively.

ESP32 Robot Controller — beginner explanation
This board is a robot control board: U1 is the “brain,” U2 drives two motors, and the connectors let you attach sensors, buttons, an RC receiver, and a small display.
I’m keeping this at the high-level, beginner-friendly level: first power, then the main blocks, then what you actually need to use first. That’s the right way to explain an existing board to a beginner
1) What each main part does

Main parts


PartJob
U1The ESP32 controller. This runs your code and reads inputs.
U2Motor driver. It takes low-power control signals from U1 and switches more current to the motors.
U37805 voltage regulator. It makes a 5 V supply for the board from the battery/input side.
D1Input protection diode on the power path.
C1, C2, C3, C4Capacitors that help keep the power stable.
2) How power flows
Think of power like this:
battery/input -> protection -> regulator -> board electronics
In this design:
  • Power comes in through the input side using J3 and the power switch SW8
  • D1 is in the input path
  • U3 creates the 5 V rail
  • That 5 V goes to U1 through its VIN pin and also out to several connectors
  • U1 then provides 3.3 V
  • That 3.3 V powers logic-side parts like U2, the display connector J13, and the button circuits around SW1, SW2, and SW3
Important beginner takeaway
You do not need to understand every capacitor right now. Just understand:
  • input power enters
  • U3 makes 5 V
  • U1 is the processor
  • U2 is the motor driver
That is enough to get oriented
3) What the board can connect to Motors
  • J1 and J2 are the two motor outputs
  • U2 connects directly to them
  • U1 sends control signals to U2:
    • D27 -> AIN1
    • D14 -> AIN2
    • D4 -> BIN1
    • D13 -> BIN2
Display
  • J13 is an OLED display connector
  • It uses I2C:
    • U1 D21 -> SDA
    • U1 D22 -> SCK/SCL
Buttons
  • SW1, SW2, and SW3 are the three user buttons
  • They go into U1 through resistor networks like R1 and R3
RC / serial / external inputs
  • J14 carries a serial connection tied to U1 RX2/TX2
  • R18 is part of that IBUS/serial input conditioning
  • J4 and J5 are 4-pin headers going to GPIOs on U1
Sensor connectors
There are multiple 3-pin connectors:
  • J6
  • J7
  • J8
  • J9
  • J10
  • J11
  • J12
Most of these follow the pattern:
  • pin 1 = GND
  • pin 3 = 5 V
  • pin 2 = signal to U1
So these are basically easy plug-in ports for sensors or signal devices.
4) What happens when the robot runs
Very simply:
  1. Power is applied through J3 and SW8
  2. U3 creates 5 V
  3. U1 boots up
  4. U1 reads:
    • buttons from SW1, SW2, SW3
    • external signals from the connectors
    • optional display communication through J13
  5. U1 sends motor commands to U2
  6. U2 powers the motors through J1 and J2
5) What you should care about first as a beginner

Only learn these 4 things first


Learn this firstWhy
Where power goes inSo you do not damage the board
Which connector is for motorsSo you know what moves the robot
Which connector is for programming / serialSo you can upload/test code
Which pins go to buttons/displaySo you can make simple tests first
6) What you do not need to understand yet
You do not need to fully understand:
  • every resistor
  • every capacitor
  • every ESP32 GPIO
  • every review warning
That can come later. The explanation workflow for beginners should focus on what the board does, how power works, and how the subsystems connect, not every tiny detail
7) One practical warning
The current review shows several floating-pin warnings on U1, SW1, SW2, SW3, and SW8. That does not automatically mean the board is unusable, but it does mean the schematic may still need cleanup before trusting it completely.
Best next step
If you want the easiest path forward, ask me one of these:
  • “Show me where to connect power safely.”
  • “Show me which connectors are for motors and sensors.”
  • “Show me how to program U1.”
  • “Make me a beginner checklist to test this board.”
If you want, I can do the next step now: a super simple connector-by-connector guide for this board.
Review schematic basics
Explain PCB layout
Check for common issues
2 days

​
Sign up to send

To get started, talk to Flux or create a New Document.

Reviews

Documents

    Documents are markdown text files which describe project goals, capture details, or even simulation outputs.

    Assets

    No assets added.

    ESP32 ROBOT CONTROLLER

    ESP32 ROBOT CONTROLLER thumbnail
    Control board for autonomous or radio-controlled robots. It has inputs to connect distance sensors and encoders for autonomous mode. It can be radio controlled by the ESP32 bluetooth or by connecting a Flysky RC controller receiver to the IBUS port. It also has 3 push buttons and you can connect some kind of display by I2C to visualize and select configuration modes.

    Properties

    Properties describe core aspects of the project.

    Pricing & Availability

    Distributor

    Qty 1

    Arrow

    $10.64–$11.21

    Digi-Key

    $4.62–$5,830.17

    LCSC

    $3.46–$4.05

    Mouser

    $4.35–$4.58

    Verical

    $28.04–$28.68

    Controls

    Welcome 👋

    Flux helps you build PCBs faster with an AI teammate!

    Create your account to collaborate, stay updated, fork your own version, and get instant answers from our AI agent.

        Introducing AI Placement!
        AI Placement Demo

        AI-Powered Component Placement

        Let AI place your components intelligently. AI Placement analyzes your schematic and positions components for optimal routing, signal integrity, and board density.

        From Schematic to Layout in Seconds

        Skip the tedious manual placement. AI Placement generates a starting layout you can refine, saving hours of repetitive work on every new design.

        Works With Auto-Layout

        Pair AI Placement with Auto-Layout for a complete AI-driven PCB design flow — from component placement through trace routing, all with one click.

        Try it