Robot Parts: What Are the Parts of a Robot?
A robot is made of six functional parts: a frame, actuators, a power system, sensors, a controller, and an end effector or drivetrain. Every machine people call a robot has all six, even when two of them share one circuit board.
The parts are easier to learn as jobs than as objects. The frame holds shape, actuators create motion, power supplies energy, sensors gather state, the controller decides, and the end effector or drivetrain does the actual work.
That job-first view survives across scale. A $40 desktop rover and a 500 kg welding arm split into the same six blocks, and only the size of each block changes.
On this page: the three main parts answer, then each of the six blocks in turn, then where builders over-buy and under-spec.
- What are the 3 main parts of a robot?
- The frame and mechanical structure
- Actuators: motors, servos, and gearboxes
- Power: batteries, regulation, and distribution
- Sensors: how a robot knows anything
- The controller: microcontroller or single-board computer
- End effectors and drivetrains
- Where builders over-buy and under-spec
| Part | Job it does | Typical hardware | Most common failure mode |
|---|---|---|---|
| Frame / chassis | Holds every other part in fixed relation | Aluminium extrusion, 3D-printed plate, sheet metal | Flex under load, which shows up as inaccuracy the software gets blamed for |
| Actuators | Turn electrical energy into motion | DC motors, servos, steppers, gearboxes | Under-specified torque, so the robot stalls on carpet or under payload |
| Power system | Stores and regulates energy | LiPo or Li-ion pack, BMS, regulators | Voltage sag under motor load, which resets the controller mid-run |
| Sensors | Report the robot's own state and the world | Encoders, IMU, ultrasonic, lidar, cameras, limit switches | No feedback at all, so the robot runs open-loop and drifts |
| Controller | Reads sensors, runs logic, commands actuators | Microcontroller or single-board computer | Wrong tier for the task, usually a general-purpose computer doing real-time work |
| End effector / drivetrain | Applies the work to the world | Gripper, tool, wheels, tracks, legs | Chosen last, after the arm or chassis can no longer carry it |
What Are the 3 Main Parts of a Robot?
The three main parts of a robot are sensors, a control system, and actuators. That is the standard teaching answer, and it is the one most classroom and exam sources use.
Some courses give a different trio: body, brain, and power. That version promotes the power system and folds sensing into the brain. Both are simplifications of the six-block breakdown above.
The three-part model names the loop that makes a machine a robot: sense, decide, act. A device that acts without sensing is automation, not robotics. Our autonomous mobile robots guide draws that distinction.
Use the three-part model to explain a robot and the six-part model to build one. Once you start ordering hardware, "actuators" splits into motors, gearboxes, and drivers. Each of those needs its own decision.
- Sensors — measure the robot's own joints and the environment around it
- Control system — the processor and code that turn measurements into commands
- Actuators — the motors and drives that convert those commands into movement
- Power (added by the four-part version) — the battery, regulation, and distribution that keep the other three alive
- Structure (added by the five-part version) — the frame that holds tolerances so the sensors stay meaningful
Robot Parts: The Frame and Mechanical Structure
The frame sets the accuracy ceiling for everything mounted on it. If the chassis twists 2 mm under load, no encoder or control loop recovers that error, because the sensor is measuring the motor and not the flex.
Hobby frames are usually laser-cut acrylic, 3D-printed PLA, or aluminium extrusion. Extrusion costs more and stays square, which matters as soon as a robot carries anything heavier than its own electronics.
Mechanical parts inside the frame do the quiet work: bearings, shafts, couplers, standoffs, and fasteners. These are the parts builders forget to budget for and then improvise badly.
A shaft coupler is the classic example. A misaligned coupler between motor and wheel adds vibration that a beginner reads as a code problem for a week.
Actuators: Motors, Servos, and Gearboxes
Actuators convert electrical energy into motion, and they are the part that most often decides whether a robot works. A robot with weak actuators fails visibly; a robot with weak code fails quietly.
Three families cover almost all robots. Brushed and brushless DC motors spin continuously and need a gearbox for torque, servos hold a commanded angle, and stepper motors move in fixed increments without feedback.
Gearboxes trade speed for torque at a fixed ratio. A 100:1 gearbox multiplies torque roughly 100 times and divides speed by the same, minus real losses in the gear train.
Choosing between these families is a page of its own — see the robot motors guide for the torque, RPM, encoder, and driver decisions. Here it is enough to know that the actuator sets the robot's physical limits before any other part gets a vote.
Power: Batteries, Regulation, and Distribution
The power system stores energy and delivers it at the voltages each part expects. It is the most under-designed block in amateur robotics and the cause of the most confusing failures.
A typical robot runs two voltage domains. Motors take raw pack voltage through a driver, and logic takes a regulated 5 V or 3.3 V rail, because motors create electrical noise that resets processors.
Voltage sag is the failure to design for. When motors stall, current spikes and pack voltage drops, and if the logic rail rides on the same unregulated supply the controller reboots mid-move.
The fix is boring and effective: separate the logic supply, size the pack for stall current rather than average current, and add bulk capacitance near the motor driver. Total build cost is easier to sanity-check with the DIY robot cost calculator before ordering.
Sensors: How a Robot Knows Anything
Sensors split into two groups: proprioceptive sensors that measure the robot itself, and exteroceptive sensors that measure the world. Most beginner robots buy the second group and skip the first, which is backwards.
Proprioceptive sensors are encoders on motor shafts, an inertial measurement unit for orientation, current sensors on drivers, and limit switches at joint extremes. These close the control loop and turn commanded motion into verified motion.
Exteroceptive sensors are ultrasonic range finders, infrared reflectance sensors, lidar, and cameras. They answer questions about the environment: how far is that wall, where is the line, what object is this.
Sensor choice follows the question, not the price. An ultrasonic sensor that costs a few dollars answers "is something within two metres" more reliably than a camera answering the same question with far more code.
| Sensor | Group | What it measures | Good for |
|---|---|---|---|
| Rotary encoder | Proprioceptive | Shaft angle and rotation count | Closed-loop speed, odometry, repeatable positioning |
| IMU (accelerometer + gyro) | Proprioceptive | Orientation and angular rate | Balancing, heading hold, tilt detection |
| Limit switch | Proprioceptive | A joint reaching a known endpoint | Homing an axis, hard safety stops |
| Ultrasonic range finder | Exteroceptive | Distance by sound time-of-flight | Cheap obstacle stopping on hard, flat surfaces |
| IR reflectance array | Exteroceptive | Surface contrast under the robot | Line following, edge and cliff detection |
| 2D lidar | Exteroceptive | Distance across a scanned plane | Mapping and navigation in indoor spaces |
| Camera | Exteroceptive | Images for software to interpret | Object recognition, tag following, inspection |
The Controller: Microcontroller or Single-Board Computer
The controller runs the code that reads sensors and commands actuators, and it comes in two tiers that solve different problems. Picking the wrong tier is the most common architecture mistake in hobby robotics.
A microcontroller such as an Arduino board or an ESP32 runs one program directly on the metal. It reacts in microseconds and never pauses to schedule another process, which is what motor control needs.
A single-board computer such as a Raspberry Pi runs a full operating system. It handles cameras, networking, and mapping well, and it is a poor choice for timing-critical pulses because the OS can preempt your loop.
Serious robots use both. The single-board computer plans and perceives, the microcontroller drives the motors, and a serial link joins them. Our Arduino robot kits guide and Raspberry Pi robot kits guide cover the kits built around each tier.
End Effectors and Drivetrains: The Parts That Touch the World
The end effector is whatever the robot uses to act on its environment, and on mobile robots the drivetrain plays that role. This is the part most builds specify last and should specify first.
Grippers are the common case on arms: two-finger parallel jaws, vacuum cups for flat surfaces, and magnetic tools for ferrous parts. Each carries a payload rating that must be subtracted from the arm's rating, not added to it.
Robot wheels are the mobile equivalent, and the choice changes the robot's whole geometry. Two driven wheels with a caster turn in place, four driven wheels climb better and scrub in turns, and omni or mecanum wheels move sideways at the cost of traction and carpet performance.
Tracks and legs solve terrain that wheels cannot. Both add mechanical complexity that only pays back when the ground is genuinely rough. For arm tooling specifically, see end effectors and grippers.
- Two-wheel differential drive with a caster — simplest to build and to control, turns in place, struggles on thresholds
- Four-wheel drive — more traction and payload, wheels scrub during turns, needs more motor budget
- Omni or mecanum wheels — full sideways motion, poor on carpet and debris, high cost per wheel
- Tracks — excellent on loose ground, high friction losses, hard on indoor flooring
- Legs — clears obstacles no wheel can, and multiplies actuator count, cost, and control difficulty
Where Builders Over-Buy and Under-Spec
The parts most builders over-buy are sensors, and the part they under-spec is almost always the drivetrain. This inversion is visible in first-build parts lists across the hobby: three range finders and a camera bolted to motors that cannot climb a doorway threshold.
The same asymmetry shows up at commercial scale. Continuous torque, duty cycle, and payload at full extension are the numbers that decide whether a machine finishes a shift, and they are the ones hardest to find on a product page.
The inversion case is real, though. On a fixed indoor test rig with a known load, spending on sensing over drivetrain is correct, because the mechanics never change and the perception problem is the whole project.
Practical rule for a first mobile build: buy motors with roughly twice the torque you calculate, one proprioceptive sensor per driven wheel, and exactly one exteroceptive sensor. Add the second exteroceptive sensor only after the first one is doing real work.
When you are ready to buy, the where to buy robot parts guide maps each category to the suppliers that stock it, and robotics for beginners sequences the first four projects.
Bottom Line
The robot parts you actually need are best learned as six jobs rather than a shopping list: structure, actuation, power, sensing, control, and the end effector or drivetrain that does the work. The classroom "three main parts" answer — sensors, control system, actuators — names the sense-decide-act loop correctly and hides the power and structure decisions that sink most real builds. Specify the drivetrain and the power system first, add sensing to close the loop before adding sensing to perceive the world, and match the controller tier to the timing the task actually demands.
Working out which parts your first build actually needs? Start with the robotics for beginners path, price the bill of materials in the DIY robot cost calculator, then use the sourcing directory to order each category from a supplier that stocks it.
FAQs
What are the 3 main parts of a robot?
The three main parts of a robot are sensors, a control system, and actuators. Sensors measure the robot and its environment, the control system decides what to do, and actuators produce the motion. Some courses instead teach body, brain, and power, which describes the same machine with the power supply promoted into the top three.
What are the basic parts of a robot?
The basic parts of a robot are a frame, actuators, a power system, sensors, a controller, and an end effector or drivetrain. Small robots often combine parts on one board — a controller with an integrated motor driver, for example — but every one of the six jobs is still being done by something.
What are robot parts and their functions?
The frame holds every part in fixed relation, actuators convert electricity into motion, the power system stores and regulates energy, sensors report state, the controller runs the decision logic, and the end effector or drivetrain applies work to the world. Each part has a matching failure mode, such as frame flex creating errors the software cannot correct.
What is the difference between a robot part and a robotic component?
The terms are used interchangeably in practice. Suppliers tend to say robot parts for physical items you buy, such as wheels, servos, and brackets, and robotic components for subsystems described by function, such as the drive system or the sensing stack.
Do all robots need sensors?
Yes, in the usual definition. A machine that acts on a fixed schedule without measuring anything is automation rather than robotics. The sense-decide-act loop is what separates the two, so even a simple line-following robot carries at least one sensor closing that loop.
Which robot part should you choose first?
Choose the end effector or drivetrain first, then the actuators that must carry it, then the power system that must feed those actuators. Working in this order stops the common mistake of designing a chassis and discovering afterwards that no motor in the budget can move it under load.
Primary Sources
- Arduino — official site and hardware documentation
- Raspberry Pi — official site and product documentation
- Espressif ESP32 product page
- Pololu — motors, gearmotors, and encoder documentation
- SparkFun — sensor tutorials and hookup guides
- Adafruit Learning System — power and regulation guides
- ROS documentation — robot description and components