Building a Follow-Me Robot
Thought for 11 sec
That’s a good instinct: build the recommended beginner prototype first, but choose parts that leave a clear upgrade path for your camera AI and arms.
Recommended v1 plan:
- Start with a rolling follow-me base: 2 driven wheels + caster, 3 speed modes: slow / normal / fast.
- Use an ESP32-S3 module for the first controller because it supports camera projects, has native USB, and is beginner-friendly compared with a bare chip .
- Use USB-C rechargeable battery power, but the exact battery size depends on motor current; we must do a full power budget before choosing regulators, fuses, charger, and connectors .
- Make AI-upgrade room now: add expansion headers for a Raspberry Pi / Jetson / future AI board, with UART/I2C/SPI, power, camera/control signals, and mounting holes.
- Arms are possible, but I would make them a v2 add-on: start with simple gripper/servo mounting points and an expansion connector instead of designing full lifting arms immediately.
- Firmware can be prepared for upgrades: once the schematic pin map is defined, I can create real starter firmware with named GPIOs, motor speed modes, sensor polling, and placeholders for your later AI control path .
Best first build: mobile base + camera mount + obstacle sensors + 3 speeds + USB-C rechargeable battery + AI/arm expansion ports. Then after it drives reliably, add the camera-following AI and arm module. Want me to draft the full v1 robot architecture/spec next?
Please.
Thought for 11 sec
I’ll turn this into a beginner-friendly v1 robot spec and save it as a project file so we have a clear starting point. I’ll keep the current 555 blinker design untouched and frame this as a new robot project plan with an upgrade path for AI and arms.
Worked for 1 min 3 sec
I created the detailed v1 architecture/spec here: Follow-Me Robot V1 Specification.
It keeps the 555 blinker untouched and defines the robot as a separate beginner-friendly project: rolling base first, three speed modes, USB-C rechargeable battery planning, ESP32-S3 control path, AI expansion, and arms as a later add-on. This follows the staged PCB workflow and records the design decisions in a project file instead of burying them in chat .
Next best step: create a new robot project and start with motor + battery selection, because those determine the power budget and every power-path part rating .
Motor battery table
Find motor drivers
Estimate power budget
Document PCB requirements
Refine this doc
Ask about this doc
Design Notes — 9V 555 LED Blinker
Requirements
- Blink a red LED approximately once per second.
- Power from a 9 V block battery.
- Include an on/off switch.
- Use components that are easy to hand-solder.
Architecture
The design uses a Texas Instruments NE555P in an astable oscillator configuration. The 9 V battery positive terminal feeds the switched 9 V rail through SW1. The NE555 output drives a 5 mm red LED through a 1 kOhm current-limiting resistor.
Selected Components
Table
| Designator | Function | Value / Part | Notes |
|---|---|---|---|
| J1 | Battery connector | Keystone 967 | Through-hole 9 V snap connector |
| SW1 | On/off switch | AS11CH | Through-hole SPST slide switch |
| U1 | Timer IC | NE555P | Through-hole DIP-8 timer |
| LED1 | Indicator | LTL-307EE | 5 mm through-hole red LED |
| R1 | Timing RA | 4.7 kOhm | Axial 1/4 W through-hole |
| R2 | Timing RB | 4.7 kOhm | Axial 1/4 W through-hole |
| R3 | LED limit | 1 kOhm | Axial 1/4 W through-hole |
| C1 | Timing capacitor | 100 uF, 16 V | Radial aluminum electrolytic |
| C2 | Supply bypass | 100 nF, 50 V | NE555 VCC bypass |
| C3 | Control bypass | 10 nF, 50 V | NE555 CONT bypass |
Datasheet-Grounded Wiring
NE555P pins are wired as follows:
- Pin 1 GND -> GND
- Pin 2 TRIG -> 555_TIMING
- Pin 3 OUT -> R3 -> LED1 anode; LED1 cathode -> GND
- Pin 4 RESET -> 9V_SW
- Pin 5 CONT -> C3 -> GND
- Pin 6 THRES -> 555_TIMING
- Pin 7 DISCH -> R1/R2 junction
- Pin 8 VCC -> 9V_SW
The NE555 datasheet recommends a 0.1 uF bypass capacitor from VCC to GND and notes that bypassing CONT to ground can improve operation. Both are included.
Timing Calculation
Astable equations:
- High time: tH = 0.693 * (RA + RB) * C
- Low time: tL = 0.693 * RB * C
- Period: T = 0.693 * (RA + 2RB) * C
- Frequency: f = 1 / T
With RA = 4.7 kOhm, RB = 4.7 kOhm, C = 100 uF:
- tH = 0.651 s
- tL = 0.326 s
- T = 0.977 s
- f = 1.02 Hz
- Duty cycle is approximately 66.7% LED-on time.
Power Budget
Approximate peak loads:
- LED current while on: about 5-7 mA using R3 = 1 kOhm from a 9 V supply.
- NE555 supply current: typically a few mA, depending on operating conditions.
- Total expected peak load: under 15 mA.
The 9 V battery connector and switch are rated far above this load. Resistor dissipation is low: R3 dissipates roughly 45 mW at 6.7 mA, below the 0.25 W resistor rating.
Simulation / Verification
Behavioral NE555 astable simulation results:
- High time: 0.6516 s
- Low time: 0.3280 s
- Period: 0.9796 s
- Frequency: 1.0208 Hz
- LED current while on: 6.74 mA
- LED average current: 4.45 mA
Conclusion: the circuit blinks the red LED essentially once per second.
Review Notes
Schematic-level connectivity is complete: all NE555 power, ground, reset, timing, output, and control pins are connected; decoupling is included. Current remaining review errors are PCB-layout airwires, which are expected because the board has not yet been placed or routed. These will be resolved in the layout/routing phase.
Requirements
Architecture
Selected Components
Datasheet-Grounded Wiring
Timing Calculation
Power Budget
Simulation / Verification
Review Notes
