Commercial disclosure: EAR may receive compensation from qualifying purchases made through approved SparkFun affiliate links. Commercial relationships do not determine our recommendations. Purchases are completed with SparkFun. Read EAR’s disclosure.
Research note: This is documented editorial research, not a hands-on EAR test.
A small mobile robot needs a way to observe its surroundings, decide what to do and apply power to motion hardware. Understanding those roles makes choosing parts—and diagnosing faults—much easier.
The controller runs the program. Sensors provide measurements. Motor drivers switch power to suitable motors. A power system supplies the required energy. One board may combine several of these functions.
The controller runs the decision process
A microcontroller follows the program you give it. It can read a button, receive a sensor value, calculate a response and produce control signals.
For example, an obstacle exercise might follow this logic: read the distance, compare it with a chosen threshold, then command movement or stop. The threshold and behavior are choices in your program; they are not automatically supplied by installing a distance sensor.
SparkFun’s RedBoard Plus is an Arduino-compatible example. It includes GPIO and a Qwiic connector for compatible peripherals. The exact pins, voltage settings and available memory matter when choosing examples and accessories. [1]
The motor driver handles the motor’s power path
A controller pin is not a substitute for a motor power circuit. A driver takes control inputs and switches a suitable motor supply. For a brushed DC motor, an H-bridge can provide opposite drive directions; many drivers also accept speed-control signals. [2]
SparkFun’s Qwiic Motor Driver controls two small DC motors and accepts an I2C interface. The board specifies 1.2A steady-state drive per channel and a 3–11V operating motor supply. It is a 3.3V-default logic device. Those limits must fit the project. [3]
Choose a driver using the motor’s voltage and stall-current requirements, not only its ordinary running current. Check the manufacturer’s thermal and power guidance. A brief peak rating is not a promise of sustained output.
A board that controls DC motors is not automatically appropriate for a stepper motor or servo. Choose the driver and interface for the actual actuator.
Sensors report particular kinds of measurements
A sensor gives the program information; it does not decide the entire behavior of the robot.
| Sensor type | What you might learn from it | What it does not establish on its own |
|---|---|---|
| Distance sensor | A range measurement in its sensing direction | A complete map of the room |
| Line sensor | Reflectance differences near the floor | Global robot position |
| Encoder | Rotation of the monitored mechanism | Exact position after wheel slip |
| IMU | Motion or orientation-related measurements | Guaranteed drift-free navigation |
| Camera | Images for suitable processing software | Automatic object understanding |
For example, SparkFun’s VL53L1X board is a single-zone optical distance sensor. A Mini VL53L5CX ToF Imager measures multiple depth zones. Neither is equivalent to an ordinary color camera. [4,5]
Choose the measurement that solves your problem. A robot following a floor line and a robot interpreting an image do not need the same sensing approach.
Power and communication are separate questions
A connector may carry power and signals, but that does not mean its power rail can operate every attached load. A motor driver can need its own motor supply even when it communicates with the controller through Qwiic.
Before connecting components, check four things: supply voltage, signal voltage, current demand and communication/software support. Matching connector shapes only answers part of the question.
For I2C devices, also check addresses and bus requirements. Two devices that cannot share an address may require a supported alternative configuration or a multiplexer. A plug-in connector reduces wiring work; it does not eliminate integration decisions. [6]
Complete robot kits can combine the roles
The current XRP controller includes motor-drive circuitry and dedicated sensor connections. That is why a learner assembling the standard kit does not need to purchase a separate motor-driver board just to complete the basic robot. [7]
A separate RedBoard-and-driver project is different: you are choosing and connecting more of the system yourself. It can teach more about wiring and component selection, but it also leaves more integration work to you.
Troubleshoot one role at a time
If a robot fails to move, ask:
- Is the controller running the intended program?
- Does the driver receive the intended command?
- Is the required motor supply present?
- Are the motor connections correct?
- Is a sensor condition deliberately preventing movement?
When the sensor example works independently and the motor example works independently, combining them becomes a software-and-integration task rather than a mystery involving every component at once.
Build that habit early: test the observation, test the action, then connect them through a small program.
Sources
- RedBoard Plus
- TB6612FNG motor driver and documentation
- Qwiic Motor Driver
- VL53L1X distance board
- Mini VL53L5CX ToF Imager
- Qwiic Mux
- XRP controller hardware overview
Continue learning
Compare your starting path in XRP vs SparkFun Inventor’s Kits. For a broader introduction, read EAR’s robot sensors guide.
