Robot Lab · 12 archetypes · vendor-neutral

Build any robot. Boot it. Watch it move.

Every robot on Earth is the same five layers — structure, actuation, sensing, compute, power — wired through a control loop. Pick an archetype, snap the real parts together, and the animation shows the machine come alive. No brand secrets, no copyrighted CAD — just how robots actually work.

Archetypes
Parts Bay

Bipedal Humanoid

~28 DOF. Whole-body MPC at 500 Hz keeps ZMP inside the support polygon.

0/21
Missing: Chassis / Frame, BLDC + FOC Driver, Harmonic Reducer, Leg Assembly, Manipulator Arm, End Effector, Real-time MCU, Single-Board Computer, AI Accelerator, Li-ion Pack, BMS, DC-DC + Bus, IMU, Joint Encoders, Force/Torque Sensor, Depth Camera, RGB Camera, Microphone Array, VLM / Policy Net, Safety Controller, E-Stop
CELL · Bipedal Humanoid · STANDBY
Assembly
MCU
SBC
BMS
E-STOP
Ready: 21 missing

How any robot actually works

Layer 1 · Structure

The chassis carries every other subsystem

Aluminium extrusion, CF composite, or 3D-printed nylon. First rule of robot design: pick the stiffest structure you can afford, because every millimetre of flex becomes a control error the software has to fight forever.

CF stiffness
70 GPa
Al 6061
69 GPa
PA-CF print
6 GPa
Deflection budget
<0.5 mm
Layer 2 · Actuation

Everything moves because of one of five actuators

Brushed / brushless motors, smart servos, harmonic-geared servos, hydraulic cylinders, or pneumatics. Modern robots default to BLDC + FOC (field-oriented control) because it's backdrivable, silent, and force-controllable.

BLDC efficiency
~90%
Servo bandwidth
1 kHz
Harmonic backlash
~0 arcmin
Hydraulic pressure
200 bar
Layer 3 · Sensing

Proprioception + exteroception, always

Proprioception (encoders, IMU, F/T) tells the robot where its body is. Exteroception (cameras, LiDAR, depth, mics) tells it what the world is. You cannot skip either — a robot with no encoders is a rag doll, one with no cameras is blind.

IMU rate
500–1000 Hz
Encoder res
14-bit abs
LiDAR points/s
0.1–1.3 M
Depth range
0.1–10 m
Layer 4 · Compute

Two brains: real-time + high-level

An MCU (STM32 / Teensy) runs the deterministic control loop at 1 kHz — safety-critical, cannot miss a deadline. An SBC (Jetson / Pi / NUC) runs ROS 2, perception, planning and any AI model. They talk over UART, CAN or Ethernet.

Control loop
1000 Hz
Perception
30–60 Hz
Planning
5–20 Hz
VLM inference
1–5 Hz
Layer 5 · Power

Wh in vs W out — the runtime equation

Battery Wh divided by average draw = runtime. Motors dominate mobile robots (~70%), compute dominates AI robots (~30-50%). A BMS is mandatory: cell imbalance in Li-ion causes fires, and no CV of a demo is worth that.

Li-ion 21700
~250 Wh/kg
Quadruped draw
150–400 W
Humanoid draw
500–2500 W
Jetson Orin
15–60 W
Control

The universal robot loop

sense → estimate → plan → control → act. Every robot runs this loop, differing only in what fills each stage. A cobot's plan is inverse kinematics; a humanoid's plan is a whole-body MPC; a swarm robot's plan is 'match my neighbours'.

IK solve
<1 ms
MPC horizon
0.3–1.5 s
PID rate
1–8 kHz
Nav2 rate
20 Hz
Kinematics

DOF, workspace, singularities

A 6-DOF arm can reach any pose in its workspace. A 7-DOF arm avoids singularities (positions where a joint velocity blows up). Bipeds need 6+ DOF per leg; hands need 20+ DOF to grasp the way we do — most cheat with underactuation.

Arm DOF
6–7
Hand DOF
1–24
Leg DOF
3–6
Humanoid total
24–40
Perception

SLAM: build a map while you walk it

Simultaneous Localization And Mapping fuses LiDAR/camera + IMU + odometry to answer two questions at once: where am I, and what does the world look like? Modern stacks (ORB-SLAM3, LIO-SAM, Cartographer) run in real time on an SBC.

Map cells
1–100 M
Loop closure
seconds
Drift
<1% distance
CPU load
1–2 cores
Autonomy

From scripts to policies

Classical robots run scripts (move here, grip, place). Autonomous robots run policies — functions that map sensors to actions. Modern ones use learned policies: RL, imitation learning, or Vision-Language-Action models like OpenVLA and RT-2.

Demos to learn
50–5000
Sim2real gap
domain rand.
Latency budget
<200 ms
Success rate
task-dep.
Safety

Safety is a hardware property, not a wish

ISO 10218 (industrial) and ISO/TS 15066 (collaborative) define allowed contact forces. Cat-3 PLe safety controllers cut motor power in <10 ms. E-stops are dual-channel and mechanically latching. If the software can override the safety, it isn't safety.

Contact limit
65–160 N
Stop time
<80 ms
PLe MTTFd
≥100 yr
Redundant chan.
2
Communication

CAN, EtherCAT, DDS: how the parts talk

Between joints: CAN or EtherCAT — deterministic, hard real-time. Between processes on the SBC: ROS 2 DDS pub/sub. To the operator: Wi-Fi 6 / 5G / mesh. Never mix real-time and non-real-time traffic on the same bus.

CAN bitrate
1 Mb/s
EtherCAT cycle
125 µs
DDS latency
<1 ms
Wi-Fi 6 UL
1 Gbps
Build path

How you actually start today

Pick an archetype (arm, wheeled, quadruped). Buy an open kit: LeRobot SO-100 arm, Unitree Go2 edu, TurtleBot 4. Install ROS 2 Jazzy. Wire ODrive/moteus. Run the demos. Only then write your own node. 90% of robotics is plumbing, not brains.

First prototype
2–6 weeks
First policy
1–3 months
First product
1–3 years
Cost floor
€300+

Open sources only. Content is synthesised from open standards (ROS 2, ISO 10218 / TS 15066, IEC 61508), open-source robotics stacks (Nav2, MoveIt2, ODrive, moteus, Betaflight, LeRobot) under Apache-2.0 / BSD / MIT, public research papers (Cassie, Kilobot, OpenVLA, RT-2) and Wikipedia (CC BY-SA). No proprietary CAD, firmware, or internal documents are used or redistributed.

Trademarks. Unitree, Boston Dynamics, Tesla, TurtleBot and all other product / company names are trademarks of their respective owners, mentioned only as editorial and educational references (nominative fair use). This site is not affiliated with, endorsed by, or sponsored by any of them.