robodatech.Time budget
For a 100 Hz loop you have 10 ms per cycle. Measure worst-case sensor reads, computation, and output updates. Avoid blocking network requests inside this loop.
Controllers
Choose the brain of your robot.
Compare current microcontrollers and hybrid boards by timing, interfaces, connectivity, and the work your robot needs to do.
Try it yourselfChange an input.
Change an input.
See what follows.
A simplified learning model. Values describe the model, not a connected robot.
Start with the job, then choose the board.
A controller repeatedly samples inputs, updates its state, and commands outputs. A microcontroller is well suited to predictable timing, encoder capture, PWM, and fast fault handling. A Linux computer adds cameras, planning, networking, and a larger software environment. A useful robot often uses both: the computer requests motion, while the microcontroller enforces local limits and stops on stale commands.
Current platforms to understand
| Platform | What it brings | Robotics application | Integration decision |
|---|---|---|---|
| Arduino UNO Q | QRB2210 Linux processor + STM32U585 MCU | Vision-assisted inspection with a separate MCU control loop | Use the documented bridge; verify shield pin voltage and software compatibility. |
| Raspberry Pi Pico 2 / 2 W | RP2350, programmable I/O; 2 W adds wireless | Encoder acquisition, pulse generation, compact sensor controllers | 3.3 V GPIO. Pick 2 W when wireless is required. |
| ESP32-C6 | RISC-V with Wi-Fi 6, Bluetooth LE and 802.15.4 | Connected sensor nodes and telemetry gateways | BLE is not Classic Bluetooth SPP; old HC-05 phone workflows do not transfer unchanged. |
| ESP32-P4 | Compute and multimedia interfaces | Robot display, camera frontend, local visual processing | No integrated radio; wireless needs a companion device. |
| ESP32-S31 | Newer connected RISC-V platform | Multi-protocol sensor gateways and connected robot interfaces | Check board availability and the ESP-IDF support matrix before committing. |
| Classic Arduino Nano | ATmega328P learning platform | Existing 5 V rover lessons and simple experiments | Keep the existing Nano pin plan; newer boards are not wiring-compatible by default. |
Make a controller budget
Interface budget
Count ADC channels, encoder inputs, UARTs, I²C addresses, SPI chip selects, PWM timers, and a debug port. Pin count alone does not guarantee simultaneous peripheral support.
Power budget
Check supply input, logic voltage, current peaks, and brownout behavior. Use a regulated logic supply and a rated motor driver; a GPIO pin cannot power a motor.
A useful first project
- Read one encoder at a fixed interval and report counts per second.
- Add a PWM output through a motor driver, with the wheels lifted.
- Introduce a command timeout that disables the driver.
- Only then add Wi-Fi, a display, or a Linux companion.
The timing experiment above shows sample frequency as the reciprocal of loop period. It does not estimate processor instruction throughput.
Go to the source
Manufacturer and project documentation. Reviewed 20 September 2026; check your exact board revision and software release.