engyasin/awesome-mechatronics

A list of awesome mechatronics books, courses and software.

214

12 commits

updated Aug 8, 2026

See the code

README

Awesome Mechatronics Awesome License: CC0-1.0

Books, courses, tools, papers and hardware for mechatronic engineering —
from the classical V-model to vision-language-action models.

Definitions · Learning paths · VLAs & diffusion policies · Agentic AI · Projects · Trends radar

The mechatronic stack in 2026: seven layers from mechanism and structure up to supervision and orchestration, with safety, simulation and data as cross-cutting concerns


Mechatronics is the synergistic integration of mechanical engineering, electronics, control theory and computing in the design of products and processes. The 1969 Yaskawa coinage described machines with electronics inside. The discipline has since absorbed cyber-physical systems, digital twins, and — since roughly 2023 — learned, language-conditioned policies that replace hand-written control laws. See §0 for how the definition has moved.

What's in here. This list keeps the classical mechatronics canon (it still matters — nothing about foundation models repeals the Nyquist criterion) and adds the parts of the field that appeared in the last five years: learned visuomotor control, VLAs, diffusion and flow-matching policies, GPU physics, agentic industrial software, and the mechanical-design ideas that came back into fashion because learning made compliant hardware tractable.

Legend — 📖 book · 📄 paper · 🎓 course · 🔧 tool · 📝 write-up · 🧪 hands-on · 🆓 free / open source · 💵 paid · ⭐ start here if you're new · 🔬 research-level

Table of contents

0. What Mechatronics Means Now

The definition has moved four times

Mechatronics has been redefined roughly once per industrial revolution, and the current redefinition is the sharpest since the 1990s.

Timeline of the mechatronics definition: 1969 Yaskawa coinage, 1980s-90s synergistic integration, 2011 cyber-physical systems, 2020 human cyber-physical systems, 2023-26 embodied intelligence

1. Mechanics + electronics → synergistic integration. The 1980s–90s reframing was that mechatronics is not a sum of parts bolted together but a co-design discipline: the mechanism, the sensor choice and the control law are decided together, from the first sketch. This is where the V-model and concurrent engineering come from, and it remains the core professional skill.

2. Mechatronics → Cyber-Physical Systems. With Industry 4.0 (2011), production systems became networked CPS built on digital twins and standardised information models. Mechatronics stopped being about one machine and started being about fleets of machines with an information layer. The Asset Administration Shell (IEC 63278-1:2023) is the concrete artefact of this shift.

3. CPS → Human-CPS (Industry 5.0). From around 2020, the framing added human-centricity, resilience and sustainability, giving rise to Human Cyber-Physical Systems and cobots. A useful consequence: three industrial paradigms now coexist on the same shop floor, and a mechatronics engineer is expected to work across all three.

4. Everything → Physical AI / Embodied AI. The 2024–2026 shift is the largest. Perception-to-action neural policies increasingly replace the hand-designed controller, not just augment it. Terminology is genuinely contested here:

TermRough meaningWho pushes it
Embodied AIAI that perceives, decides and acts through a body (physical or simulated). The older, academic term.Academia; ITU-T Rec. F.748.66 (Dec 2025) gives it a formal framework
Physical AIThe broader commercial umbrella: models + simulation + compute sold as one stack for real-world machinesNVIDIA, BCG, investors
MechatronicsThe engineering discipline that actually builds the body the AI acts throughEveryone, once the demo has to ship

The honest reading: Physical AI is a market category; mechatronics is the engineering discipline it depends on. Nothing in a VLA solves backlash, thermal derating, or the fact that a harmonic drive has a torque ripple signature. What has changed is where the difficulty sits — less in writing the controller, more in hardware that is learnable: backdrivable, well-instrumented, repeatable, and cheap enough to collect thousands of demonstrations on.

A working definition for 2026

Mechatronics is the design of systems whose behaviour emerges from the co-design of mechanism, actuation, sensing, computation and learned or programmed policy — where the policy may now be a neural network trained on data rather than a control law derived from a model.

Read the definition debate yourself 📄


1. Start Here: Learning Paths

Mechatronics is wide enough that "where do I start" is the most common question. Three paths, depending on where you want to end up.

flowchart TD
    A["Absolute beginner<br/>Arduino / ESP32 blink → sensors → PWM motor"] --> B["Circuits + C/C++ + Python"]
    B --> C["Classical control<br/>PID, Laplace, Bode, state space"]
    C --> D{"Pick a direction"}

    D --> E["<b>Industrial automation</b><br/>PLC · IEC 61131-3 · HMI/SCADA<br/>OPC UA · digital twin"]
    D --> F["<b>Robotics</b><br/>ROS 2 · kinematics · SLAM<br/>MoveIt · Nav2"]
    D --> G["<b>Machine / product design</b><br/>CAD · FEA · actuator sizing<br/>tolerances · DfM"]

    E --> H["Agentic industrial AI<br/>MCP · anomaly agents · predictive maintenance"]
    F --> I["Robot learning<br/>imitation → ACT → diffusion policy → VLA"]
    G --> J["Co-design<br/>compliant actuators · topology opt · morphological computation"]

    H --> K["<b>Physical AI engineer</b>"]
    I --> K
    J --> K

Path A — Beginner, hands-on first (0–6 months) ⭐

You want to build something that moves before you learn Laplace transforms. This is a legitimate order.

  1. Get a board and a motor. Arduino Uno/ESP32 + L298N or a TB6612 + a cheap DC gearmotor with an encoder. Total cost under €40.
  2. 🎓 Paul McWhorter — Arduino for Beginners 🆓 — the most patient beginner series that exists.
  3. 🎓 ControlSystemsAcademy / Brian Douglas — Control System Lectures 🆓 — intuition before mathematics. Watch "PID Control — A brief introduction" and the root locus series.
  4. 🧪 Build a closed-loop position controller for one motor. Tune a PID by hand. This single project teaches sampling, quantisation, saturation, integral windup and derivative noise — the four things that actually bite in practice.
  5. 🎓 MATLAB Tech Talks — Understanding PID Control 🆓 (free videos even without a MATLAB licence)
  6. Move to ESP32 + micro-ROS or Raspberry Pi + ROS 2 and you're in the robotics world proper.
  7. 🧪 Then: LeRobot + an SO-101 arm — collect 50 demonstrations, train a policy, watch it work. Two hours, and it will reframe everything you thought robot programming was.

Path B — Undergraduate / career-switcher (6–18 months)

  1. Control: 🎓 Steve Brunton — Control Bootcamp 🆓 + 📖 Feedback Systems (Åström & Murray) 🆓
  2. Robotics: 📖 Modern Robotics (Lynch & Park) 🆓 + the Coursera specialisation
  3. Embedded: build one project in bare-metal C on an STM32, then one on Zephyr RTOS. The contrast teaches you what an RTOS buys you.
  4. Industrial: one PLC project in Structured Text on OpenPLC 🆓 or a real S7-1200, plus one OPC UA client.
  5. Learning: 📖 Robot Learning: A Tutorial 🆓 — the single best on-ramp from classical control to learned policies, with runnable lerobot examples.

Path C — Graduate / research 🔬

  1. 📖 Underactuated Robotics and Robotic Manipulation — Russ Tedrake, MIT. 🆓 Free, interactive, with Drake notebooks. The best treatment anywhere of why contact-rich control is hard.
  2. 📄 Towards a Unified Understanding of Robot Manipulation: A Comprehensive Survey — 2025. The map of the whole manipulation literature.
  3. 📄 Vision-Language-Action Models for Robotics: A Review Towards Real-World Applications — Kawaharazuka et al., IEEE Access 2025. Has a searchable database of every VLA.
  4. Pick a benchmark (LIBERO, SimplerEnv, RoboCasa) and reproduce one result before you propose anything.

2. Foundations: Books & Courses

Core mechatronics textbooks 📖

The classics, kept because they are still the right first books:

Control & dynamics (free where possible) 📖

Robotics 📖

Machine learning for engineers 📖

Courses worth your time 🎓

CourseWhoCostWhy
Control BootcampSteve Brunton, UW🆓Best state-space introduction on YouTube
Modern Robotics SpecializationNorthwestern🆓 auditScrew theory done properly, with CoppeliaSim labs
Underactuated RoboticsMIT🆓Trajectory optimisation, LQR trees, contact 🔬
Robotic ManipulationMIT🆓The manipulation course, with Drake notebooks 🔬
SLAM lecturesCyrill Stachniss, Bonn🆓The reference SLAM lecture series
Sim-to-Real with the SO-101NVIDIA🆓Full pipeline: Isaac Sim → Isaac Lab → GR00T → real arm 🧪
LeRobot docs & tutorialsHugging Face🆓Imitation learning and VLAs, hands-on, end to end ⭐
Introduction to Robotics CS223AKhatib, Stanford🆓Classic; operational space control from the source
Learn 5 PLCs in a DayUdemy💵Practical multi-vendor PLC exposure
From Wire to PLCUdemy💵Panel wiring → ladder → commissioning
Wearable Robotics — ExoskeletonsUdemy💵Niche but well-made

3. The Mechanical Side, Seen From Mechatronics

The most common failure mode in modern mechatronics projects is a good policy on bad hardware. This section is the mechanical engineering that a mechatronic engineer specifically needs — not general machine design, but the subset where mechanics and control interact.

The central idea: your mechanism is part of your controller

flowchart LR
    subgraph Physical["Mechanical domain"]
        M["Mechanism<br/>kinematics, inertia"]
        T["Transmission<br/>ratio, backlash, friction"]
        C["Compliance<br/>stiffness, damping"]
    end
    subgraph Electrical["Electrical domain"]
        A["Actuator<br/>torque density, thermal"]
        S["Sensing<br/>resolution, bandwidth, latency"]
    end
    subgraph Compute["Computation"]
        P["Policy<br/>PID / MPC / learned"]
    end

    M --> T --> A --> P
    S --> P --> A
    C -.->|"sets achievable<br/>control bandwidth"| P
    P -.->|"required bandwidth<br/>constrains design"| C

    style Physical fill:#e8f0fe
    style Electrical fill:#fef3e8
    style Compute fill:#e8fae8

Three rules that follow, and that no amount of learning removes:

  1. Structural resonance caps your bandwidth. A closed loop cannot be much faster than the first flexible mode of the structure it drives. Stiffness is a control-design parameter.
  2. Backlash is not a disturbance, it is a discontinuity. It breaks gradient-based tuning, breaks learned policies trained in simulation, and shows up as limit cycles.
  3. Reflected inertia scales with gear ratio squared. This is why quasi-direct-drive exists, and why highly geared arms cannot do impedance control well.

3.1 Actuation & transmission

Selection cheat-sheet:

NeedArchitectureTypical ratioTrade-off
Precise position, high stiffnessHarmonic / strain wave50:1–160:1Non-backdrivable, expensive, torque ripple
High dynamics, force control, impactQuasi-direct drive (QDD)6:1–10:1Large motor, high current, heat
Safe human contact, energy storageSeries elastic (SEA)any + springBandwidth limited by spring, extra sensing
Cheap, high ratio, tolerantCycloidal20:1–100:1Vibration, harder to manufacture well
Lightweight distal massCable / tendon drivevariesFriction, stretch, routing complexity

3.2 Compliance, contact and impedance

Learning-based manipulation made compliance fashionable again: policies that touch things need hardware that can survive touching things.

3.3 Mechanical intelligence & morphological computation 🔬

The idea that the body itself performs computation — that a well-designed gripper needs less control than a badly-designed one. This has moved from curiosity to an active research programme.

3.4 Design, simulation and manufacturing tools

ToolTypeCostNote
FreeCADParametric CAD🆓v1.x finally fixed the topological naming problem; genuinely usable now
OnshapeCloud CAD🆓 free tierFree for public documents; excellent for open-source hardware
SolidWorksCAD + CAE💵Industry default; motion + FEA add-ins
FusionCAD/CAM/CAE💵 (free personal)Integrated generative design and CAM
nTopImplicit modelling💵Lattices, topology optimisation, field-driven design
Ansys / COMSOLMultiphysics FEA💵Thermal + structural + electromagnetic coupling
CalculiX / Code_AsterFEA solver🆓Free FEA; usable via FreeCAD FEM workbench
ToOptix / ToPyTopology optimisation🆓Learn the method before paying for a suite
OpenModelicaAcausal multi-domain sim🆓The right tool for mechanical+hydraulic+electrical system models
SimscapeMulti-domain sim💵The commercial equivalent, tightly coupled to Simulink
Blender3D modelling🆓Not CAD, but the standard for robot visual meshes and rendering
PrusaSlicer / OrcaSlicerSlicers🆓Printed robot parts: print orientation determines layer-direction strength

3.5 Practical mechanical checklist for mechatronic builds 🧪

Expand — the things that actually go wrong
  • Actuator sizing: size on RMS torque over the duty cycle, not peak. Check thermal, then check peak, then check backdrive torque.
  • Reflected inertia ratio: aim for load-to-motor inertia below ~10:1 for good servo response; below 3:1 for high dynamics.
  • First resonance: measure it (tap test + accelerometer, or a swept-sine on the actuator). Target closed-loop bandwidth ≤ 1/3 of it.
  • Backlash budget: total it across every joint in the chain. Preload, use anti-backlash gears, or move the encoder to the output.
  • Encoder placement: motor-side encoders lie about the load. Output-side encoders (dual encoding) cost more and solve most repeatability complaints.
  • Cable management: the leading cause of field failures in articulated robots. Design the cable path before the last link.
  • Thermal path: motors derate. Where does the heat go? Aluminium bracket, not printed PLA.
  • Tolerance stack-up: run it for the gripper-to-camera chain specifically — that's what a learned policy actually sees.
  • Learnability: if you plan to collect demonstrations, the robot must be backdrivable enough to hand-guide, repeatable enough that yesterday's data still applies, and mechanically identical to any other unit you deploy on.

4. Electronics, Embedded & Edge

Microcontrollers & compute

PlatformRoleNote
Arduino 🆓Learning, prototypingThe Uno R4 / Nano ESP32 generation is far more capable than the AVR days
ESP32 family 🆓Wireless mechatronicsWi-Fi/BLE + dual core + enough RAM for micro-ROS
Raspberry Pi Pico / RP2350 🆓Real-time IOPIO state machines are excellent for encoder decoding and step generation
STM32 💵Production motor controlThe industry default for motor drives; G4/H7 for FOC
Teensy 4.x 💵High-rate control loops600 MHz Cortex-M7; underrated for 10 kHz+ loops
Raspberry Pi 5 💵Linux + ROS 2Enough for perception at modest rates; add a Hailo or Coral for NN inference
NVIDIA Jetson Orin / Thor 💵On-robot policy inferenceThor / T4000 (Blackwell, 2026) is what current VLAs are deployed on

Firmware & RTOS

  • 🔧 Zephyr RTOS 🆓 — the RTOS to learn now: vendor-neutral, device-tree based, Linux-Foundation governed, huge board support.
  • 🔧 FreeRTOS 🆓 — still ubiquitous, simpler mental model.
  • 🔧 micro-ROS 🆓 — ROS 2 on microcontrollers. Runs on Zephyr, FreeRTOS, Mbed, Arduino. The correct way to bridge MCU sensors/actuators into a ROS 2 system. ⭐
  • 🔧 PlatformIO 🆓 — sane multi-board build system; escape from the Arduino IDE.
  • 🔧 Embassy / embedded-hal 🆓 — async embedded Rust. Increasingly serious for safety-relevant firmware; memory safety without a GC.
  • 🔧 Renode 🆓 — emulate the whole board in CI. Test firmware without hardware.

Edge AI / TinyML

Running inference on the machine rather than in the cloud is now a normal part of a mechatronic design, especially for condition monitoring and anomaly detection.

Electronics design

  • 🔧 KiCad 🆓 — v8/v9 is fully production-capable. No reason to pay for hobby or small-team PCB work.
  • 🔧 Fritzing 💵 (small fee) — still the best for teaching wiring diagrams.
  • 🔧 Proteus 💵 — schematic capture with MCU co-simulation.
  • 🔧 Falstad Circuit Simulator 🆓 — instant intuition for analog circuits, in the browser.
  • 🔧 LTspice 🆓 — free, accurate SPICE; use it before you build the motor driver.
  • 🔧 LabVIEW 💵 — still dominant in test & measurement rigs.
  • 📖 The Art of Electronics — Horowitz & Hill, 3rd ed. 💵 The reference.
  • 📖 Practical Electronics for Inventors — Scherz & Monk. 💵 More approachable starting point.

5. Industrial Automation, Industry 4.0 / 5.0

Controllers & languages

  • IEC 61131-3 — the PLC languages standard (LD, FBD, ST, IL, SFC). Learn Structured Text first; ladder second.
  • IEC 61499 — distributed, event-driven automation. The intended successor for distributed control; slow adoption but conceptually important. 🔧 Eclipse 4diac 🆓 is the open reference implementation.
  • 🔧 OpenPLC 🆓 — open-source IEC 61131-3 runtime + editor. The cheapest possible way to learn real PLC programming. ⭐ 🧪
  • 🔧 Beremiz 🆓 — open IDE for IEC 61131-3.
  • 🔧 CODESYS 💵 — the vendor-neutral runtime behind many PLC brands.
  • 🔧 TwinCAT 💵 — Beckhoff's PC-based control platform; increasingly the platform where AI-in-automation experiments happen first.
  • 🔧 Siemens TIA Portal / STEP 7 💵
  • 📖 Programmable Logic Controllers — Petruzella. 💵 The standard PLC textbook.

Simulation & commissioning

Connectivity, information models and digital twins

This is the part of Industry 4.0 that actually matters and that most curricula skip.

Industry 5.0 concepts

  • Human Cyber-Physical Systems (HCPS) — the human is inside the control loop by design, not by exception.
  • Cobots — ISO/TS 15066 defines the power-and-force-limiting regime; read it before designing any human-adjacent machine.
  • Ecomechatronics — energy- and material-efficiency as first-class design objectives, driven by EU sustainability regulation.
  • 📄 The Evolution of Mechatronics Engineering and Its Relationship with Industry 3.0, 4.0, and 5.0 — 2026. 🆓

6. The Robotics Software Stack

ROS 2 — current state (as of mid-2026)

DistroReleasedUbuntuSupport untilUse it?
Lyrical LuthMay 202626.04May 2031✅ New production projects (LTS)
Kilted KaijuMay 202524.04Nov 2026⚠️ Migrate off
Jazzy JaliscoMay 202424.04May 2029✅ Safe, widest package support today
Humble HawksbillMay 202222.04May 2027⚠️ Plan migration

ROS 1 reached end of life in May 2025. New projects should not use it.

  • 🎓 ROS 2 official tutorials 🆓 ⭐
  • 🎓 ROS 2 for Beginners — Edouard Renard 💵 / lots of free material
  • 🔧 MoveIt 2 🆓 — motion planning for manipulators
  • 🔧 Nav2 🆓 — the navigation stack for mobile robots
  • 🔧 ros2_control 🆓 — hardware abstraction + controller lifecycle. Learn this before writing a custom driver.
  • 🔧 Zenoh 🆓 — increasingly used as an alternative RMW / bridge, especially over lossy links.

Kinematics, dynamics & optimisation libraries

  • 🔧 Pinocchio 🆓 — fast rigid-body dynamics with analytical derivatives. The backbone of most modern whole-body controllers.
  • 🔧 Drake 🆓 — MIT's toolbox: modelling, contact, trajectory optimisation, convex programs. 🔬
  • 🔧 CasADi 🆓 — symbolic framework for nonlinear optimisation and optimal control.
  • 🔧 acados 🆓 — embedded NMPC that actually runs at kHz rates on real hardware.
  • 🔧 Crocoddyl 🆓 — DDP-family optimal control for legged/multi-contact robots. 🔬
  • 🔧 OMPL 🆓 — sampling-based motion planning.
  • 🔧 Python Robotics 🆓 — readable implementations of dozens of algorithms. Excellent for learning. ⭐

Simulation — this changed completely in 2025–2026

The physics-engine landscape has been rewritten by GPU acceleration.

SimulatorCostBest for
Newton🆓The new centre of gravity. Open-source, GPU-accelerated, differentiable; built on NVIDIA Warp + OpenUSD; developed by NVIDIA + Google DeepMind + Disney Research under the Linux Foundation. v1.0 GA at GTC 2026. Bundles MuJoCo-Warp and Disney's Kamino (closed-loop mechanisms) solvers, SDF collision, hydroelastic contact, and deformables.
MuJoCo🆓Contact-rich control research; CPU version remains the easiest to debug
MuJoCo Playground🆓Ready-made GPU RL environments
Isaac Lab🆓Large-scale robot learning; v3.0 builds on Newton + PhysX
Isaac Sim🆓Photorealistic digital twins, synthetic data, sensor simulation
Genesis🆓Fast multi-platform GPU physics; strong on generative scene creation
Gazebo🆓ROS-native system-level simulation; still the right tool for full-robot integration testing
Webots🆓Education; batteries included, low setup cost ⭐
CoppeliaSim🆓 eduTeaching kinematics; used by the Modern Robotics course
SAPIEN🆓Articulated-object manipulation research

Practical guidance: for learning a policy, use Newton/MuJoCo-Warp or Isaac Lab. For validating a system, use Gazebo or Isaac Sim. For understanding what your controller does, use MuJoCo on CPU with the viewer open.

Perception

  • 🔧 OpenCV 🆓 — v5 launched at CVPR 2026.
  • 🔧 Open3D 🆓 — point clouds and 3D processing.
  • 🔧 SAM 2 🆓 — promptable segmentation for images and video; now a standard preprocessing block in robot perception.
  • 🔧 FoundationPose 🆓 — 6-DoF pose estimation for novel objects.
  • 🔧 ORB-SLAM3 🆓 / RTAB-Map 🆓 — visual and RGB-D SLAM.
  • 🔧 Nerfstudio 🆓 / gsplat 🆓 — NeRF and 3D Gaussian splatting; now used for real-to-sim asset capture.

Tooling & visualisation

  • 🔧 Foxglove 🆓 free tier — the modern replacement for RViz+rqt for log inspection.
  • 🔧 Rerun 🆓 — multimodal time-series visualisation. Excellent for debugging learned policies (log observations, actions and predictions together).
  • 🔧 PlotJuggler 🆓 — the fastest way to look at time-series from a robot or PLC.
  • 🔧 MCAP 🆓 — the modern robotics log format.

7. Learning-Based Control: The New Core

This is the section that did not exist when this list was first written. In five years, robot manipulation moved from "write an inverse-kinematics solver and a state machine" to "collect demonstrations and train a policy." Both approaches are alive; a mechatronic engineer in 2026 needs to know when to reach for which.

7.0 The mental model

Side-by-side comparison of the classical model-based control pipeline and the learned visuomotor pipeline, with guidance on when to use each

flowchart LR
    subgraph Classical["Classical mechatronic pipeline"]
        direction TB
        C1["Sensors"] --> C2["State estimation"] --> C3["Planner"] --> C4["Controller<br/>PID / MPC"] --> C5["Actuators"]
    end

    subgraph Learned["Learned visuomotor pipeline"]
        direction TB
        L1["Cameras +<br/>proprioception"] --> L2["Neural policy<br/>ACT · Diffusion · VLA"] --> L3["Action chunk<br/>(next N actions)"] --> L4["Low-level<br/>joint controller"] --> L5["Actuators"]
    end

    Choose{"Which one?"}
    Classical -.->|"models known,<br/>state observable,<br/>safety certifiable"| Choose
    Learned -.->|"contact-rich,<br/>deformable, cluttered,<br/>hard to model"| Choose

    style Classical fill:#e8f0fe
    style Learned fill:#e8fae8

Three ideas do most of the work in modern policies:

  1. Action chunking — predict a sequence of future actions instead of one. Cuts compounding error and makes the policy robust to slow inference.
  2. Generative action heads — model the distribution over action sequences (diffusion, flow matching) rather than regressing a mean. Critical when demonstrations are multimodal (two valid ways to grasp a mug, and averaging them drops the mug).
  3. Pretrained vision-language backbones — inherit semantic and spatial priors from internet-scale data so the robot generalises to objects and instructions it never saw.

7.1 Imitation learning & action chunking

7.2 Diffusion policies

A diffusion policy generates robot actions by iteratively denoising, exactly as image diffusion models generate pixels. It handles multimodal demonstrations naturally and has become the default strong baseline.

7.3 Flow matching & real-time chunking

Flow matching learns a deterministic transport from noise to data instead of an iterative denoising chain. In practice: faster inference, smoother trajectories, better stability — which is why the newest VLAs use it.

7.4 Vision-Language-Action models (VLAs)

A VLA takes camera images plus a natural-language instruction and outputs robot actions, end to end. This is the fastest-moving area in robotics.

flowchart LR
    IMG["Camera(s)"] --> VE["Vision encoder<br/>SigLIP / DINOv2"]
    TXT["Instruction:<br/>'put the mug in the sink'"] --> LM
    VE --> LM["Language model backbone<br/>Llama / PaliGemma / Cosmos"]
    STATE["Proprioception"] --> AH
    LM --> AH["Action head"]
    AH --> A1["Discrete action tokens<br/>(autoregressive)"]
    AH --> A2["Diffusion / flow<br/>action expert"]
    A1 --> CH["Action chunk<br/>H × DoF"]
    A2 --> CH
    CH --> RTC["Real-time chunking<br/>+ low-level controller"]
    RTC --> ROBOT["Robot"]
    ROBOT -->|"new observation"| IMG

    style LM fill:#fef3e8
    style AH fill:#e8fae8

Open models you can actually run:

ModelParamsLicenceNotes
SmolVLA450M🆓 ApacheHugging Face, June 2025. Trained purely on community datasets; runs on consumer hardware. Best starting point. ⭐ 📄
OpenVLA7B🆓Stanford/Berkeley, 2024. ~970k Open X-Embodiment episodes; DINOv2 + SigLIP + Llama 2. The reference open VLA. 📄 code
OpenVLA-OFT7B🆓Optimised fine-tuning recipe; large speed/success gains over base OpenVLA
π₀ / openpi~3B🆓 weightsPhysical Intelligence. Flow-matching action expert on a VLM backbone; pretrained on 10,000+ hours. Smoothest trajectories in contact-rich tasks. 📄
Isaac GR00T N~2–3B🆓NVIDIA. Dual-system: slow VLM planner (System 2) + fast diffusion transformer controller (System 1). N1 (Mar 2025) → N1.5 → N1.6 (Dec 2025, Cosmos-2B backbone). Built for humanoids. 📄
Octo27M–93M🆓Generalist transformer policy; small and easy to fine-tune
SpatialVLA4B🆓Explicit 3D spatial representations
MolmoAct—🆓"Action reasoning model" — reasons in space before acting
BitVLA3B🆓1-bit weights; VLA inference on constrained hardware 🔬
Gemini Robotics On-Device—💵 restrictedGoogle DeepMind; on-robot inference without cloud

Surveys — read one of these before the papers:

7.5 World models 🔬

Learned simulators that predict how the world evolves given actions — used for synthetic data generation, planning in imagination, and safe evaluation.

  • 🔧 NVIDIA Cosmos 🆓 open weights — world foundation models for physical AI; Cosmos 3 (GTC 2026) unifies world generation, vision reasoning and action simulation.
  • 📄 Genie 3 — Google DeepMind. Real-time interactive world generation.
  • 📄 DayDreamer / Dreamer V3 — model-based RL that learns a world model and plans inside it.
  • 📄 Real2Render2Real / GigaBrain-0 — scaling robot data without scaling robot hardware.
  • Why it matters for mechatronics: synthetic data augmentation lets a team turn ~200 real demonstrations into thousands of variants, which is often cheaper than buying more robots.

7.6 Reinforcement learning on real hardware

7.7 Datasets & benchmarks

ResourceWhat
Open X-Embodiment 🆓1M+ trajectories, 22 embodiments, 30+ labs. The ImageNet moment for robot data.
DROID 🆓76k in-the-wild manipulation trajectories, 564 scenes
BridgeData V2 🆓60k trajectories, widely used for VLA pretraining
LeRobot datasets on the HF Hub 🆓Thousands of community datasets in a standard format
LIBERO 🆓The standard lifelong-manipulation benchmark
SimplerEnv 🆓Reproducible simulated evaluation of real-robot VLAs
RoboCasa 🆓Large-scale simulated kitchen environments
RoboTwin 2.0 🆓Bimanual manipulation data generator + benchmark
Isaac Lab-Arena 🆓NVIDIA's robot evaluation framework (2026)

7.8 Hands-on: train your own policy 🧪

The single highest-value practical exercise in modern mechatronics. Under €500 of hardware and one afternoon.

  • 🔧 LeRobot 🆓 — Hugging Face's end-to-end robot learning library. pip install, no ROS required. Includes ACT, Diffusion Policy, VQ-BeT, π₀, SmolVLA, HIL-SERL, TD-MPC. ⭐ 📄 ICLR 2026
  • 📖 Robot Learning: A Tutorial — Capuano, Pascal, Zouitine, Aractingi, Wolf. 🆓 RL → behavioural cloning → generalist policies, with runnable lerobot code. Read this cover to cover. ⭐
  • 🎓 SO-101 assembly guide 🆓 — 3D-printable leader/follower arm pair, ~€120–250 depending on servos.
  • 🎓 NVIDIA SO-101 sim-to-real course 🆓 — the same arm, through Isaac Sim → Isaac Lab → GR00T → hardware.
  • 📝 How I trained ACT on SO-101: journey, gotchas and lessons 🆓 — honest write-up of the failure modes (no eval split, accidentally cheating by watching the arm instead of the camera feed). Read it before you start.

Realistic expectations: ~50 demonstrations and ~30 minutes on an RTX 3060 gets a working single-task ACT policy. Language conditioning and generalisation need far more. For a single fixed task, ACT or Diffusion Policy usually beats a general VLA — reach for a VLA when you need language conditioning or cross-task transfer.


8. Agentic AI in Automation and Robotics

"Agentic" is the most abused word in industrial marketing right now, so start with the distinction that actually matters:

A copilot answers when asked. An agent acts on a trigger, plans a sequence, calls tools, and escalates only when confidence is low or a threshold is crossed.

flowchart TD
    G["Goal<br/>'keep OEE above 85% this shift'"] --> P["Planner<br/>LLM reasoning"]
    P --> T{"Tool selection"}
    T --> T1["MES / ERP API"]
    T --> T2["Historian / time-series DB"]
    T --> T3["OPC UA client<br/>read tags"]
    T --> T4["CMMS<br/>create work order"]
    T1 & T2 & T3 & T4 --> O["Observation"]
    O --> P
    P --> G2{"Confidence and<br/>authority check"}
    G2 -->|"within limits"| ACT["Bounded actuation<br/>small setpoint change"]
    G2 -->|"outside limits"| HUM["Human-in-the-loop<br/>approval"]
    ACT --> SAFETY["Deterministic safety layer<br/>PLC interlocks · ISO 13849 · SIL"]
    HUM --> SAFETY
    SAFETY --> MACHINE["Machine"]

    style SAFETY fill:#fde8e8
    style HUM fill:#fef3e8

The non-negotiable design rule: the LLM never sits inside the safety function. Interlocks, e-stops and safety-rated logic remain deterministic, certified and independent. An agent may adjust a setpoint inside a human-defined envelope; it may not define the envelope.

8.1 Where this actually is, in production

  • Beckhoff TwinCAT CoAgent (Hannover Messe 2026) — LLMs connected over the Model Context Protocol driving real machine motion sequences inside the TwinCAT platform. Engineers describe a motion in natural language; the platform generates and runs it.
  • Dell / XMPro / NVIDIA Omniverse — live PLC data from a brewery centrifuge digital twin feeding an LLM that detects boundary violations and makes small supervised SCADA-level adjustments. Deployed, not a proof of concept.
  • Siemens Industrial Copilot — code generation and diagnostics inside TIA Portal.
  • Adoption reality check: surveys through 2026 put most manufacturers at pilot stage, a minority at line-level deployment, and only a few percent letting agents make consequential decisions unsupervised. Multi-agent orchestration is still rare. Human-in-the-loop remains a hard requirement in regulated and high-precision environments, because non-deterministic behaviour is a validation problem, not just a quality problem.

8.2 Protocols and building blocks

  • 🔧 Model Context Protocol (MCP) 🆓 — the open standard for connecting models to tools and data sources. Rapidly becoming the way agents reach OPC UA servers, historians and MES.
  • 🔧 Agent2Agent (A2A) 🆓 — inter-agent interoperability across vendors.
  • 🔧 LangGraph 🆓 / CrewAI 🆓 / AutoGen 🆓 — agent orchestration frameworks.
  • 🔧 Node-RED 🆓 — unglamorous, but still the most practical glue between OT protocols and everything else.

8.3 Agents in robotics (as opposed to plant floors)

  • 📄 Code as Policies — LLMs writing robot control code. The paper that opened this line.
  • 📄 SayCan — grounding language plans in what a robot can actually do.
  • 📄 Embodied Chain-of-Thought Reasoning — CoRL 2024. Reasoning traces improve VLA action quality.
  • 📄 OpenHelix — open dual-system (planner + controller) VLA; a good template for the architecture. 🆓
  • The dual-system pattern (slow LLM planner + fast reactive controller) is now the dominant architecture — GR00T N1's System 1 / System 2 split is the clearest published example.

8.4 Safety, assurance and governance

  • 📄 Agentic AI in Engineering and Manufacturing — MIT DeCoDE Lab, 2026. 🆓 Sober analysis of bounded autonomy: agents inside tightly scoped workflows, subject to human validation, not assuming engineering accountability. ⭐
  • EU AI Act — machinery and safety components fall under high-risk obligations. If your agent touches a machine sold in the EU, this applies to you.
  • EU Machinery Regulation 2023/1230 — replaces the Machinery Directive from January 2027 and explicitly addresses self-evolving behaviour and AI-enabled safety components. This is the regulation mechatronic engineers should be reading now.
  • NIST AI Risk Management Framework 🆓
  • OWASP Top 10 for LLM Applications 🆓 — prompt injection into an agent with OPC UA write access is not a theoretical risk.
  • ISO 10218-1/-2:2025 (industrial robot safety, revised) and ISO/TS 15066 (collaborative operation).

9. Hands-On Projects

Ordered by difficulty. Each one teaches something the previous one couldn't.

#ProjectLevelRough costWhat it actually teaches
1Closed-loop DC motor position control with encoderBeginner€30Sampling, quantisation, integral windup, derivative noise
2Line follower with PID on IR arrayBeginner€40Sensor calibration, loop rate vs. speed, saturation
3Reaction wheel / inverted pendulumBeginner+€60Unstable plants, state feedback, why LQR exists 🧪
4BLDC field-oriented control with SimpleFOCIntermediate€80Commutation, current control, why FOC beats trapezoidal
5PLC-controlled sorting line in Factory I/OIntermediate€30 (licence)Ladder/ST, sequence control, HMI, industrial thinking
6ESP32 + micro-ROS sensor node into a ROS 2 graphIntermediate€20Distributed robotics, QoS, real-time boundaries
7Differential-drive robot: SLAM + Nav2Intermediate+€200TF trees, odometry drift, costmaps, localisation
83D-print an SO-101 arm, teleoperate itIntermediate+€150–250Servo calibration, leader-follower, mechanical repeatability
9Collect 50 demos, train ACT, run it on the SO-101Intermediate++GPU accessData quality, overfitting, the whole modern paradigm ⭐
10Fine-tune SmolVLA on your own taskAdvanced+GPULanguage conditioning, LoRA, evaluation protocol
11RL locomotion in Isaac Lab → real quadrupedAdvanced€1500+Domain randomisation, sim-to-real, reward shaping
12Digital twin: AAS + OPC UA of a real machineAdvanced€0Information modelling — the Industry 4.0 skill that gets hired
13Design + build a QDD actuator, characterise itAdvanced€300Torque density, backdrivability, thermal, transparency 🔬
14UMI-style handheld data collection rigAdvanced€200Robot-free data collection at scale 🔬

Project-based learning resources:


10. Hardware You Can Actually Buy or Build

Open-source and low-cost platforms, roughly by price.

Platform~CostTypeNotes
SO-101 / SO-ARM101€120–3506-DoF arm pair🆓 open hardware. Leader/follower teleoperation; the LeRobot reference platform. Kits from Hiwonder, Seeed, WowRobo. ⭐
LeKiwi€400Mobile manipulatorSO-101 on a holonomic base; open source
Koch v1.1€2505-DoF armThe predecessor design; still a good build
ALOHA / ALOHA 2€5k–20kBimanualThe reference bimanual teleoperation setup
Open Duck Mini€400BipedalApproachable legged-robot learning platform
Reachy 2 / Reachy Mini€300–70kHumanoidPollen Robotics (Hugging Face); open source
Unitree Go2 / G1€1.6k–16kQuadruped / humanoidThe default research legged platforms; SDK is usable
Franka Research 3€25k+7-DoF armThe academic manipulation standard; excellent torque control
UR cobots€20k+CobotThe industrial collaborative standard; good ROS 2 driver
TurtleBot 4€1.5kMobileThe canonical ROS 2 teaching robot
Duckietown€300+Mobile / educationComplete autonomy curriculum in a box 🎓
Open Dynamic Robot Initiative€3k+Legged actuators🆓 Open QDD actuator + leg designs from MPI/NYU

11. Classic Mechatronic Systems

Worked examples worth studying, because each one is a complete mechatronic argument:

  • ABS — wheel-slip estimation from noisy sensors under hard real-time constraints. The canonical automotive mechatronic system.
  • 3D printers — motion control, thermal control, and (in Klipper) input shaping and pressure advance. An accessible, complete control-systems case study. 🧪
  • GNSS/INS — sensor fusion; the practical home of the Kalman filter.
  • PLCs — deterministic scan-cycle computation; a genuinely different computational model worth understanding.
  • Hybrid & electric drivetrains — power-split control, energy management, thermal.
  • Hard disk drives — the highest-precision mass-produced servo system ever built; nanometre positioning at kHz bandwidth.
  • Washing machines — unbalance detection, drum resonance avoidance, cost-driven sensor minimisation. Deceptively deep.
  • Surgical robots — teleoperation, force reflection, safety architecture.
  • Wafer steppers — the extreme end: sub-nanometre stages, feed-forward everything, the field's hardest control problems.

Where things stand, honestly assessed.

TrendMaturityWhy a mechatronic engineer should care
VLAs / generalist robot policiesEarly productionChanges what "programming a robot" means. Hardware must now be learnable, not just controllable
Diffusion & flow-matching policiesProduction-readyThe strong default for contact-rich manipulation; robust to multimodal demonstrations
Real-time action chunkingProduction-readyMade large policies runnable at real robot rates — the practical unlock of 2025
GPU physics (Newton, MuJoCo-Warp)Rapidly maturingTwo orders of magnitude more simulation throughput; sim-first design becomes viable for small teams
World models (Cosmos, Genie)Research → early productSynthetic data instead of more robots; expect commercial integration around 2027
Agentic AI in plant operationsPilots, few deploymentsReal value in exception handling and supervised execution; the safety architecture is the engineering problem
MCP as industrial glueEarly, fast-movingBecoming the standard way models reach OPC UA / MES / historians
HumanoidsOverhyped, genuinely improvingMassive investment; the hard problems remain actuation, energy, hands and reliability — mechanical problems
Compliant & backdrivable actuationMature, resurgingLearned policies need hardware that survives contact; QDD, SEA and VSA are back in demand
Morphological computation / metamaterialsResearchOffload control effort into the structure; watch this over the next five years 🔬
Digital twin standardisation (AAS)Mature standard, slow adoptionThe Industry 4.0 skill with the best employability-to-effort ratio
Edge AI / TinyML on MCUsMatureCondition monitoring and anomaly detection without cloud dependency
Digital Product Passport / ecomechatronicsRegulatory-drivenEU rules will make this mandatory work, not optional differentiation
Embedded RustGrowingMemory safety in firmware; adoption rising in safety-relevant contexts
Robot data scarcityThe bottleneckThe 2026 consensus: progress is limited by data infrastructure, not model architecture

13. Journals, Conferences, Communities

Journals

Conferences

  • ICRA · IROS — the two big robotics conferences
  • RSS — smaller, higher signal-to-noise; where Diffusion Policy and ACT appeared
  • CoRL — the robot learning conference
  • AIM — IEEE/ASME Advanced Intelligent Mechatronics
  • Hannover Messe · SPS Nuremberg · automatica — where industrial reality shows up
  • NVIDIA GTC — increasingly where robotics platform announcements land

Communities


Robotics & learning

Engineering & embedded

AI


Contributing

Contributions are welcome — additions, corrections and dead-link reports alike.

The rules in short: prefer free and primary sources, mark paid ones with 💵, include the year for anything in the fast-moving sections, and give one line on why a resource is worth someone's time. Keep the mechatronic point of view — this is not a general AI, ME or EE list.

Read CONTRIBUTING.md for the full guidelines, entry format and marker conventions.

Licence

CC0

To the extent possible under law, the contributors have waived all copyright and related rights to this work.

awesome
awesome-list
electrical-engineering
industrial-automation
iot
mechanical-engineering
mechatronics
mechatronics-engineering
mechatronic-systems
python
robotics
ros2

Contributors

engyasin

10 commits

smasher2010

1 commits

engyasin/awesome-mechatronics

A list of awesome mechatronics books, courses and software.

214

12 commits

updated Aug 8, 2026

See the code

README

Awesome Mechatronics Awesome License: CC0-1.0

Books, courses, tools, papers and hardware for mechatronic engineering —
from the classical V-model to vision-language-action models.

Definitions · Learning paths · VLAs & diffusion policies · Agentic AI · Projects · Trends radar

The mechatronic stack in 2026: seven layers from mechanism and structure up to supervision and orchestration, with safety, simulation and data as cross-cutting concerns


Mechatronics is the synergistic integration of mechanical engineering, electronics, control theory and computing in the design of products and processes. The 1969 Yaskawa coinage described machines with electronics inside. The discipline has since absorbed cyber-physical systems, digital twins, and — since roughly 2023 — learned, language-conditioned policies that replace hand-written control laws. See §0 for how the definition has moved.

What's in here. This list keeps the classical mechatronics canon (it still matters — nothing about foundation models repeals the Nyquist criterion) and adds the parts of the field that appeared in the last five years: learned visuomotor control, VLAs, diffusion and flow-matching policies, GPU physics, agentic industrial software, and the mechanical-design ideas that came back into fashion because learning made compliant hardware tractable.

Legend — 📖 book · 📄 paper · 🎓 course · 🔧 tool · 📝 write-up · 🧪 hands-on · 🆓 free / open source · 💵 paid · ⭐ start here if you're new · 🔬 research-level

Table of contents

0. What Mechatronics Means Now

The definition has moved four times

Mechatronics has been redefined roughly once per industrial revolution, and the current redefinition is the sharpest since the 1990s.

Timeline of the mechatronics definition: 1969 Yaskawa coinage, 1980s-90s synergistic integration, 2011 cyber-physical systems, 2020 human cyber-physical systems, 2023-26 embodied intelligence

1. Mechanics + electronics → synergistic integration. The 1980s–90s reframing was that mechatronics is not a sum of parts bolted together but a co-design discipline: the mechanism, the sensor choice and the control law are decided together, from the first sketch. This is where the V-model and concurrent engineering come from, and it remains the core professional skill.

2. Mechatronics → Cyber-Physical Systems. With Industry 4.0 (2011), production systems became networked CPS built on digital twins and standardised information models. Mechatronics stopped being about one machine and started being about fleets of machines with an information layer. The Asset Administration Shell (IEC 63278-1:2023) is the concrete artefact of this shift.

3. CPS → Human-CPS (Industry 5.0). From around 2020, the framing added human-centricity, resilience and sustainability, giving rise to Human Cyber-Physical Systems and cobots. A useful consequence: three industrial paradigms now coexist on the same shop floor, and a mechatronics engineer is expected to work across all three.

4. Everything → Physical AI / Embodied AI. The 2024–2026 shift is the largest. Perception-to-action neural policies increasingly replace the hand-designed controller, not just augment it. Terminology is genuinely contested here:

TermRough meaningWho pushes it
Embodied AIAI that perceives, decides and acts through a body (physical or simulated). The older, academic term.Academia; ITU-T Rec. F.748.66 (Dec 2025) gives it a formal framework
Physical AIThe broader commercial umbrella: models + simulation + compute sold as one stack for real-world machinesNVIDIA, BCG, investors
MechatronicsThe engineering discipline that actually builds the body the AI acts throughEveryone, once the demo has to ship

The honest reading: Physical AI is a market category; mechatronics is the engineering discipline it depends on. Nothing in a VLA solves backlash, thermal derating, or the fact that a harmonic drive has a torque ripple signature. What has changed is where the difficulty sits — less in writing the controller, more in hardware that is learnable: backdrivable, well-instrumented, repeatable, and cheap enough to collect thousands of demonstrations on.

A working definition for 2026

Mechatronics is the design of systems whose behaviour emerges from the co-design of mechanism, actuation, sensing, computation and learned or programmed policy — where the policy may now be a neural network trained on data rather than a control law derived from a model.

Read the definition debate yourself 📄


1. Start Here: Learning Paths

Mechatronics is wide enough that "where do I start" is the most common question. Three paths, depending on where you want to end up.

flowchart TD
    A["Absolute beginner<br/>Arduino / ESP32 blink → sensors → PWM motor"] --> B["Circuits + C/C++ + Python"]
    B --> C["Classical control<br/>PID, Laplace, Bode, state space"]
    C --> D{"Pick a direction"}

    D --> E["<b>Industrial automation</b><br/>PLC · IEC 61131-3 · HMI/SCADA<br/>OPC UA · digital twin"]
    D --> F["<b>Robotics</b><br/>ROS 2 · kinematics · SLAM<br/>MoveIt · Nav2"]
    D --> G["<b>Machine / product design</b><br/>CAD · FEA · actuator sizing<br/>tolerances · DfM"]

    E --> H["Agentic industrial AI<br/>MCP · anomaly agents · predictive maintenance"]
    F --> I["Robot learning<br/>imitation → ACT → diffusion policy → VLA"]
    G --> J["Co-design<br/>compliant actuators · topology opt · morphological computation"]

    H --> K["<b>Physical AI engineer</b>"]
    I --> K
    J --> K

Path A — Beginner, hands-on first (0–6 months) ⭐

You want to build something that moves before you learn Laplace transforms. This is a legitimate order.

  1. Get a board and a motor. Arduino Uno/ESP32 + L298N or a TB6612 + a cheap DC gearmotor with an encoder. Total cost under €40.
  2. 🎓 Paul McWhorter — Arduino for Beginners 🆓 — the most patient beginner series that exists.
  3. 🎓 ControlSystemsAcademy / Brian Douglas — Control System Lectures 🆓 — intuition before mathematics. Watch "PID Control — A brief introduction" and the root locus series.
  4. 🧪 Build a closed-loop position controller for one motor. Tune a PID by hand. This single project teaches sampling, quantisation, saturation, integral windup and derivative noise — the four things that actually bite in practice.
  5. 🎓 MATLAB Tech Talks — Understanding PID Control 🆓 (free videos even without a MATLAB licence)
  6. Move to ESP32 + micro-ROS or Raspberry Pi + ROS 2 and you're in the robotics world proper.
  7. 🧪 Then: LeRobot + an SO-101 arm — collect 50 demonstrations, train a policy, watch it work. Two hours, and it will reframe everything you thought robot programming was.

Path B — Undergraduate / career-switcher (6–18 months)

  1. Control: 🎓 Steve Brunton — Control Bootcamp 🆓 + 📖 Feedback Systems (Åström & Murray) 🆓
  2. Robotics: 📖 Modern Robotics (Lynch & Park) 🆓 + the Coursera specialisation
  3. Embedded: build one project in bare-metal C on an STM32, then one on Zephyr RTOS. The contrast teaches you what an RTOS buys you.
  4. Industrial: one PLC project in Structured Text on OpenPLC 🆓 or a real S7-1200, plus one OPC UA client.
  5. Learning: 📖 Robot Learning: A Tutorial 🆓 — the single best on-ramp from classical control to learned policies, with runnable lerobot examples.

Path C — Graduate / research 🔬

  1. 📖 Underactuated Robotics and Robotic Manipulation — Russ Tedrake, MIT. 🆓 Free, interactive, with Drake notebooks. The best treatment anywhere of why contact-rich control is hard.
  2. 📄 Towards a Unified Understanding of Robot Manipulation: A Comprehensive Survey — 2025. The map of the whole manipulation literature.
  3. 📄 Vision-Language-Action Models for Robotics: A Review Towards Real-World Applications — Kawaharazuka et al., IEEE Access 2025. Has a searchable database of every VLA.
  4. Pick a benchmark (LIBERO, SimplerEnv, RoboCasa) and reproduce one result before you propose anything.

2. Foundations: Books & Courses

Core mechatronics textbooks 📖

The classics, kept because they are still the right first books:

Control & dynamics (free where possible) 📖

Robotics 📖

Machine learning for engineers 📖

Courses worth your time 🎓

CourseWhoCostWhy
Control BootcampSteve Brunton, UW🆓Best state-space introduction on YouTube
Modern Robotics SpecializationNorthwestern🆓 auditScrew theory done properly, with CoppeliaSim labs
Underactuated RoboticsMIT🆓Trajectory optimisation, LQR trees, contact 🔬
Robotic ManipulationMIT🆓The manipulation course, with Drake notebooks 🔬
SLAM lecturesCyrill Stachniss, Bonn🆓The reference SLAM lecture series
Sim-to-Real with the SO-101NVIDIA🆓Full pipeline: Isaac Sim → Isaac Lab → GR00T → real arm 🧪
LeRobot docs & tutorialsHugging Face🆓Imitation learning and VLAs, hands-on, end to end ⭐
Introduction to Robotics CS223AKhatib, Stanford🆓Classic; operational space control from the source
Learn 5 PLCs in a DayUdemy💵Practical multi-vendor PLC exposure
From Wire to PLCUdemy💵Panel wiring → ladder → commissioning
Wearable Robotics — ExoskeletonsUdemy💵Niche but well-made

3. The Mechanical Side, Seen From Mechatronics

The most common failure mode in modern mechatronics projects is a good policy on bad hardware. This section is the mechanical engineering that a mechatronic engineer specifically needs — not general machine design, but the subset where mechanics and control interact.

The central idea: your mechanism is part of your controller

flowchart LR
    subgraph Physical["Mechanical domain"]
        M["Mechanism<br/>kinematics, inertia"]
        T["Transmission<br/>ratio, backlash, friction"]
        C["Compliance<br/>stiffness, damping"]
    end
    subgraph Electrical["Electrical domain"]
        A["Actuator<br/>torque density, thermal"]
        S["Sensing<br/>resolution, bandwidth, latency"]
    end
    subgraph Compute["Computation"]
        P["Policy<br/>PID / MPC / learned"]
    end

    M --> T --> A --> P
    S --> P --> A
    C -.->|"sets achievable<br/>control bandwidth"| P
    P -.->|"required bandwidth<br/>constrains design"| C

    style Physical fill:#e8f0fe
    style Electrical fill:#fef3e8
    style Compute fill:#e8fae8

Three rules that follow, and that no amount of learning removes:

  1. Structural resonance caps your bandwidth. A closed loop cannot be much faster than the first flexible mode of the structure it drives. Stiffness is a control-design parameter.
  2. Backlash is not a disturbance, it is a discontinuity. It breaks gradient-based tuning, breaks learned policies trained in simulation, and shows up as limit cycles.
  3. Reflected inertia scales with gear ratio squared. This is why quasi-direct-drive exists, and why highly geared arms cannot do impedance control well.

3.1 Actuation & transmission

Selection cheat-sheet:

NeedArchitectureTypical ratioTrade-off
Precise position, high stiffnessHarmonic / strain wave50:1–160:1Non-backdrivable, expensive, torque ripple
High dynamics, force control, impactQuasi-direct drive (QDD)6:1–10:1Large motor, high current, heat
Safe human contact, energy storageSeries elastic (SEA)any + springBandwidth limited by spring, extra sensing
Cheap, high ratio, tolerantCycloidal20:1–100:1Vibration, harder to manufacture well
Lightweight distal massCable / tendon drivevariesFriction, stretch, routing complexity

3.2 Compliance, contact and impedance

Learning-based manipulation made compliance fashionable again: policies that touch things need hardware that can survive touching things.

3.3 Mechanical intelligence & morphological computation 🔬

The idea that the body itself performs computation — that a well-designed gripper needs less control than a badly-designed one. This has moved from curiosity to an active research programme.

3.4 Design, simulation and manufacturing tools

ToolTypeCostNote
FreeCADParametric CAD🆓v1.x finally fixed the topological naming problem; genuinely usable now
OnshapeCloud CAD🆓 free tierFree for public documents; excellent for open-source hardware
SolidWorksCAD + CAE💵Industry default; motion + FEA add-ins
FusionCAD/CAM/CAE💵 (free personal)Integrated generative design and CAM
nTopImplicit modelling💵Lattices, topology optimisation, field-driven design
Ansys / COMSOLMultiphysics FEA💵Thermal + structural + electromagnetic coupling
CalculiX / Code_AsterFEA solver🆓Free FEA; usable via FreeCAD FEM workbench
ToOptix / ToPyTopology optimisation🆓Learn the method before paying for a suite
OpenModelicaAcausal multi-domain sim🆓The right tool for mechanical+hydraulic+electrical system models
SimscapeMulti-domain sim💵The commercial equivalent, tightly coupled to Simulink
Blender3D modelling🆓Not CAD, but the standard for robot visual meshes and rendering
PrusaSlicer / OrcaSlicerSlicers🆓Printed robot parts: print orientation determines layer-direction strength

3.5 Practical mechanical checklist for mechatronic builds 🧪

Expand — the things that actually go wrong
  • Actuator sizing: size on RMS torque over the duty cycle, not peak. Check thermal, then check peak, then check backdrive torque.
  • Reflected inertia ratio: aim for load-to-motor inertia below ~10:1 for good servo response; below 3:1 for high dynamics.
  • First resonance: measure it (tap test + accelerometer, or a swept-sine on the actuator). Target closed-loop bandwidth ≤ 1/3 of it.
  • Backlash budget: total it across every joint in the chain. Preload, use anti-backlash gears, or move the encoder to the output.
  • Encoder placement: motor-side encoders lie about the load. Output-side encoders (dual encoding) cost more and solve most repeatability complaints.
  • Cable management: the leading cause of field failures in articulated robots. Design the cable path before the last link.
  • Thermal path: motors derate. Where does the heat go? Aluminium bracket, not printed PLA.
  • Tolerance stack-up: run it for the gripper-to-camera chain specifically — that's what a learned policy actually sees.
  • Learnability: if you plan to collect demonstrations, the robot must be backdrivable enough to hand-guide, repeatable enough that yesterday's data still applies, and mechanically identical to any other unit you deploy on.

4. Electronics, Embedded & Edge

Microcontrollers & compute

PlatformRoleNote
Arduino 🆓Learning, prototypingThe Uno R4 / Nano ESP32 generation is far more capable than the AVR days
ESP32 family 🆓Wireless mechatronicsWi-Fi/BLE + dual core + enough RAM for micro-ROS
Raspberry Pi Pico / RP2350 🆓Real-time IOPIO state machines are excellent for encoder decoding and step generation
STM32 💵Production motor controlThe industry default for motor drives; G4/H7 for FOC
Teensy 4.x 💵High-rate control loops600 MHz Cortex-M7; underrated for 10 kHz+ loops
Raspberry Pi 5 💵Linux + ROS 2Enough for perception at modest rates; add a Hailo or Coral for NN inference
NVIDIA Jetson Orin / Thor 💵On-robot policy inferenceThor / T4000 (Blackwell, 2026) is what current VLAs are deployed on

Firmware & RTOS

  • 🔧 Zephyr RTOS 🆓 — the RTOS to learn now: vendor-neutral, device-tree based, Linux-Foundation governed, huge board support.
  • 🔧 FreeRTOS 🆓 — still ubiquitous, simpler mental model.
  • 🔧 micro-ROS 🆓 — ROS 2 on microcontrollers. Runs on Zephyr, FreeRTOS, Mbed, Arduino. The correct way to bridge MCU sensors/actuators into a ROS 2 system. ⭐
  • 🔧 PlatformIO 🆓 — sane multi-board build system; escape from the Arduino IDE.
  • 🔧 Embassy / embedded-hal 🆓 — async embedded Rust. Increasingly serious for safety-relevant firmware; memory safety without a GC.
  • 🔧 Renode 🆓 — emulate the whole board in CI. Test firmware without hardware.

Edge AI / TinyML

Running inference on the machine rather than in the cloud is now a normal part of a mechatronic design, especially for condition monitoring and anomaly detection.

Electronics design

  • 🔧 KiCad 🆓 — v8/v9 is fully production-capable. No reason to pay for hobby or small-team PCB work.
  • 🔧 Fritzing 💵 (small fee) — still the best for teaching wiring diagrams.
  • 🔧 Proteus 💵 — schematic capture with MCU co-simulation.
  • 🔧 Falstad Circuit Simulator 🆓 — instant intuition for analog circuits, in the browser.
  • 🔧 LTspice 🆓 — free, accurate SPICE; use it before you build the motor driver.
  • 🔧 LabVIEW 💵 — still dominant in test & measurement rigs.
  • 📖 The Art of Electronics — Horowitz & Hill, 3rd ed. 💵 The reference.
  • 📖 Practical Electronics for Inventors — Scherz & Monk. 💵 More approachable starting point.

5. Industrial Automation, Industry 4.0 / 5.0

Controllers & languages

  • IEC 61131-3 — the PLC languages standard (LD, FBD, ST, IL, SFC). Learn Structured Text first; ladder second.
  • IEC 61499 — distributed, event-driven automation. The intended successor for distributed control; slow adoption but conceptually important. 🔧 Eclipse 4diac 🆓 is the open reference implementation.
  • 🔧 OpenPLC 🆓 — open-source IEC 61131-3 runtime + editor. The cheapest possible way to learn real PLC programming. ⭐ 🧪
  • 🔧 Beremiz 🆓 — open IDE for IEC 61131-3.
  • 🔧 CODESYS 💵 — the vendor-neutral runtime behind many PLC brands.
  • 🔧 TwinCAT 💵 — Beckhoff's PC-based control platform; increasingly the platform where AI-in-automation experiments happen first.
  • 🔧 Siemens TIA Portal / STEP 7 💵
  • 📖 Programmable Logic Controllers — Petruzella. 💵 The standard PLC textbook.

Simulation & commissioning

Connectivity, information models and digital twins

This is the part of Industry 4.0 that actually matters and that most curricula skip.

Industry 5.0 concepts

  • Human Cyber-Physical Systems (HCPS) — the human is inside the control loop by design, not by exception.
  • Cobots — ISO/TS 15066 defines the power-and-force-limiting regime; read it before designing any human-adjacent machine.
  • Ecomechatronics — energy- and material-efficiency as first-class design objectives, driven by EU sustainability regulation.
  • 📄 The Evolution of Mechatronics Engineering and Its Relationship with Industry 3.0, 4.0, and 5.0 — 2026. 🆓

6. The Robotics Software Stack

ROS 2 — current state (as of mid-2026)

DistroReleasedUbuntuSupport untilUse it?
Lyrical LuthMay 202626.04May 2031✅ New production projects (LTS)
Kilted KaijuMay 202524.04Nov 2026⚠️ Migrate off
Jazzy JaliscoMay 202424.04May 2029✅ Safe, widest package support today
Humble HawksbillMay 202222.04May 2027⚠️ Plan migration

ROS 1 reached end of life in May 2025. New projects should not use it.

  • 🎓 ROS 2 official tutorials 🆓 ⭐
  • 🎓 ROS 2 for Beginners — Edouard Renard 💵 / lots of free material
  • 🔧 MoveIt 2 🆓 — motion planning for manipulators
  • 🔧 Nav2 🆓 — the navigation stack for mobile robots
  • 🔧 ros2_control 🆓 — hardware abstraction + controller lifecycle. Learn this before writing a custom driver.
  • 🔧 Zenoh 🆓 — increasingly used as an alternative RMW / bridge, especially over lossy links.

Kinematics, dynamics & optimisation libraries

  • 🔧 Pinocchio 🆓 — fast rigid-body dynamics with analytical derivatives. The backbone of most modern whole-body controllers.
  • 🔧 Drake 🆓 — MIT's toolbox: modelling, contact, trajectory optimisation, convex programs. 🔬
  • 🔧 CasADi 🆓 — symbolic framework for nonlinear optimisation and optimal control.
  • 🔧 acados 🆓 — embedded NMPC that actually runs at kHz rates on real hardware.
  • 🔧 Crocoddyl 🆓 — DDP-family optimal control for legged/multi-contact robots. 🔬
  • 🔧 OMPL 🆓 — sampling-based motion planning.
  • 🔧 Python Robotics 🆓 — readable implementations of dozens of algorithms. Excellent for learning. ⭐

Simulation — this changed completely in 2025–2026

The physics-engine landscape has been rewritten by GPU acceleration.

SimulatorCostBest for
Newton🆓The new centre of gravity. Open-source, GPU-accelerated, differentiable; built on NVIDIA Warp + OpenUSD; developed by NVIDIA + Google DeepMind + Disney Research under the Linux Foundation. v1.0 GA at GTC 2026. Bundles MuJoCo-Warp and Disney's Kamino (closed-loop mechanisms) solvers, SDF collision, hydroelastic contact, and deformables.
MuJoCo🆓Contact-rich control research; CPU version remains the easiest to debug
MuJoCo Playground🆓Ready-made GPU RL environments
Isaac Lab🆓Large-scale robot learning; v3.0 builds on Newton + PhysX
Isaac Sim🆓Photorealistic digital twins, synthetic data, sensor simulation
Genesis🆓Fast multi-platform GPU physics; strong on generative scene creation
Gazebo🆓ROS-native system-level simulation; still the right tool for full-robot integration testing
Webots🆓Education; batteries included, low setup cost ⭐
CoppeliaSim🆓 eduTeaching kinematics; used by the Modern Robotics course
SAPIEN🆓Articulated-object manipulation research

Practical guidance: for learning a policy, use Newton/MuJoCo-Warp or Isaac Lab. For validating a system, use Gazebo or Isaac Sim. For understanding what your controller does, use MuJoCo on CPU with the viewer open.

Perception

  • 🔧 OpenCV 🆓 — v5 launched at CVPR 2026.
  • 🔧 Open3D 🆓 — point clouds and 3D processing.
  • 🔧 SAM 2 🆓 — promptable segmentation for images and video; now a standard preprocessing block in robot perception.
  • 🔧 FoundationPose 🆓 — 6-DoF pose estimation for novel objects.
  • 🔧 ORB-SLAM3 🆓 / RTAB-Map 🆓 — visual and RGB-D SLAM.
  • 🔧 Nerfstudio 🆓 / gsplat 🆓 — NeRF and 3D Gaussian splatting; now used for real-to-sim asset capture.

Tooling & visualisation

  • 🔧 Foxglove 🆓 free tier — the modern replacement for RViz+rqt for log inspection.
  • 🔧 Rerun 🆓 — multimodal time-series visualisation. Excellent for debugging learned policies (log observations, actions and predictions together).
  • 🔧 PlotJuggler 🆓 — the fastest way to look at time-series from a robot or PLC.
  • 🔧 MCAP 🆓 — the modern robotics log format.

7. Learning-Based Control: The New Core

This is the section that did not exist when this list was first written. In five years, robot manipulation moved from "write an inverse-kinematics solver and a state machine" to "collect demonstrations and train a policy." Both approaches are alive; a mechatronic engineer in 2026 needs to know when to reach for which.

7.0 The mental model

Side-by-side comparison of the classical model-based control pipeline and the learned visuomotor pipeline, with guidance on when to use each

flowchart LR
    subgraph Classical["Classical mechatronic pipeline"]
        direction TB
        C1["Sensors"] --> C2["State estimation"] --> C3["Planner"] --> C4["Controller<br/>PID / MPC"] --> C5["Actuators"]
    end

    subgraph Learned["Learned visuomotor pipeline"]
        direction TB
        L1["Cameras +<br/>proprioception"] --> L2["Neural policy<br/>ACT · Diffusion · VLA"] --> L3["Action chunk<br/>(next N actions)"] --> L4["Low-level<br/>joint controller"] --> L5["Actuators"]
    end

    Choose{"Which one?"}
    Classical -.->|"models known,<br/>state observable,<br/>safety certifiable"| Choose
    Learned -.->|"contact-rich,<br/>deformable, cluttered,<br/>hard to model"| Choose

    style Classical fill:#e8f0fe
    style Learned fill:#e8fae8

Three ideas do most of the work in modern policies:

  1. Action chunking — predict a sequence of future actions instead of one. Cuts compounding error and makes the policy robust to slow inference.
  2. Generative action heads — model the distribution over action sequences (diffusion, flow matching) rather than regressing a mean. Critical when demonstrations are multimodal (two valid ways to grasp a mug, and averaging them drops the mug).
  3. Pretrained vision-language backbones — inherit semantic and spatial priors from internet-scale data so the robot generalises to objects and instructions it never saw.

7.1 Imitation learning & action chunking

7.2 Diffusion policies

A diffusion policy generates robot actions by iteratively denoising, exactly as image diffusion models generate pixels. It handles multimodal demonstrations naturally and has become the default strong baseline.

7.3 Flow matching & real-time chunking

Flow matching learns a deterministic transport from noise to data instead of an iterative denoising chain. In practice: faster inference, smoother trajectories, better stability — which is why the newest VLAs use it.

7.4 Vision-Language-Action models (VLAs)

A VLA takes camera images plus a natural-language instruction and outputs robot actions, end to end. This is the fastest-moving area in robotics.

flowchart LR
    IMG["Camera(s)"] --> VE["Vision encoder<br/>SigLIP / DINOv2"]
    TXT["Instruction:<br/>'put the mug in the sink'"] --> LM
    VE --> LM["Language model backbone<br/>Llama / PaliGemma / Cosmos"]
    STATE["Proprioception"] --> AH
    LM --> AH["Action head"]
    AH --> A1["Discrete action tokens<br/>(autoregressive)"]
    AH --> A2["Diffusion / flow<br/>action expert"]
    A1 --> CH["Action chunk<br/>H × DoF"]
    A2 --> CH
    CH --> RTC["Real-time chunking<br/>+ low-level controller"]
    RTC --> ROBOT["Robot"]
    ROBOT -->|"new observation"| IMG

    style LM fill:#fef3e8
    style AH fill:#e8fae8

Open models you can actually run:

ModelParamsLicenceNotes
SmolVLA450M🆓 ApacheHugging Face, June 2025. Trained purely on community datasets; runs on consumer hardware. Best starting point. ⭐ 📄
OpenVLA7B🆓Stanford/Berkeley, 2024. ~970k Open X-Embodiment episodes; DINOv2 + SigLIP + Llama 2. The reference open VLA. 📄 code
OpenVLA-OFT7B🆓Optimised fine-tuning recipe; large speed/success gains over base OpenVLA
π₀ / openpi~3B🆓 weightsPhysical Intelligence. Flow-matching action expert on a VLM backbone; pretrained on 10,000+ hours. Smoothest trajectories in contact-rich tasks. 📄
Isaac GR00T N~2–3B🆓NVIDIA. Dual-system: slow VLM planner (System 2) + fast diffusion transformer controller (System 1). N1 (Mar 2025) → N1.5 → N1.6 (Dec 2025, Cosmos-2B backbone). Built for humanoids. 📄
Octo27M–93M🆓Generalist transformer policy; small and easy to fine-tune
SpatialVLA4B🆓Explicit 3D spatial representations
MolmoAct—🆓"Action reasoning model" — reasons in space before acting
BitVLA3B🆓1-bit weights; VLA inference on constrained hardware 🔬
Gemini Robotics On-Device—💵 restrictedGoogle DeepMind; on-robot inference without cloud

Surveys — read one of these before the papers:

7.5 World models 🔬

Learned simulators that predict how the world evolves given actions — used for synthetic data generation, planning in imagination, and safe evaluation.

  • 🔧 NVIDIA Cosmos 🆓 open weights — world foundation models for physical AI; Cosmos 3 (GTC 2026) unifies world generation, vision reasoning and action simulation.
  • 📄 Genie 3 — Google DeepMind. Real-time interactive world generation.
  • 📄 DayDreamer / Dreamer V3 — model-based RL that learns a world model and plans inside it.
  • 📄 Real2Render2Real / GigaBrain-0 — scaling robot data without scaling robot hardware.
  • Why it matters for mechatronics: synthetic data augmentation lets a team turn ~200 real demonstrations into thousands of variants, which is often cheaper than buying more robots.

7.6 Reinforcement learning on real hardware

7.7 Datasets & benchmarks

ResourceWhat
Open X-Embodiment 🆓1M+ trajectories, 22 embodiments, 30+ labs. The ImageNet moment for robot data.
DROID 🆓76k in-the-wild manipulation trajectories, 564 scenes
BridgeData V2 🆓60k trajectories, widely used for VLA pretraining
LeRobot datasets on the HF Hub 🆓Thousands of community datasets in a standard format
LIBERO 🆓The standard lifelong-manipulation benchmark
SimplerEnv 🆓Reproducible simulated evaluation of real-robot VLAs
RoboCasa 🆓Large-scale simulated kitchen environments
RoboTwin 2.0 🆓Bimanual manipulation data generator + benchmark
Isaac Lab-Arena 🆓NVIDIA's robot evaluation framework (2026)

7.8 Hands-on: train your own policy 🧪

The single highest-value practical exercise in modern mechatronics. Under €500 of hardware and one afternoon.

  • 🔧 LeRobot 🆓 — Hugging Face's end-to-end robot learning library. pip install, no ROS required. Includes ACT, Diffusion Policy, VQ-BeT, π₀, SmolVLA, HIL-SERL, TD-MPC. ⭐ 📄 ICLR 2026
  • 📖 Robot Learning: A Tutorial — Capuano, Pascal, Zouitine, Aractingi, Wolf. 🆓 RL → behavioural cloning → generalist policies, with runnable lerobot code. Read this cover to cover. ⭐
  • 🎓 SO-101 assembly guide 🆓 — 3D-printable leader/follower arm pair, ~€120–250 depending on servos.
  • 🎓 NVIDIA SO-101 sim-to-real course 🆓 — the same arm, through Isaac Sim → Isaac Lab → GR00T → hardware.
  • 📝 How I trained ACT on SO-101: journey, gotchas and lessons 🆓 — honest write-up of the failure modes (no eval split, accidentally cheating by watching the arm instead of the camera feed). Read it before you start.

Realistic expectations: ~50 demonstrations and ~30 minutes on an RTX 3060 gets a working single-task ACT policy. Language conditioning and generalisation need far more. For a single fixed task, ACT or Diffusion Policy usually beats a general VLA — reach for a VLA when you need language conditioning or cross-task transfer.


8. Agentic AI in Automation and Robotics

"Agentic" is the most abused word in industrial marketing right now, so start with the distinction that actually matters:

A copilot answers when asked. An agent acts on a trigger, plans a sequence, calls tools, and escalates only when confidence is low or a threshold is crossed.

flowchart TD
    G["Goal<br/>'keep OEE above 85% this shift'"] --> P["Planner<br/>LLM reasoning"]
    P --> T{"Tool selection"}
    T --> T1["MES / ERP API"]
    T --> T2["Historian / time-series DB"]
    T --> T3["OPC UA client<br/>read tags"]
    T --> T4["CMMS<br/>create work order"]
    T1 & T2 & T3 & T4 --> O["Observation"]
    O --> P
    P --> G2{"Confidence and<br/>authority check"}
    G2 -->|"within limits"| ACT["Bounded actuation<br/>small setpoint change"]
    G2 -->|"outside limits"| HUM["Human-in-the-loop<br/>approval"]
    ACT --> SAFETY["Deterministic safety layer<br/>PLC interlocks · ISO 13849 · SIL"]
    HUM --> SAFETY
    SAFETY --> MACHINE["Machine"]

    style SAFETY fill:#fde8e8
    style HUM fill:#fef3e8

The non-negotiable design rule: the LLM never sits inside the safety function. Interlocks, e-stops and safety-rated logic remain deterministic, certified and independent. An agent may adjust a setpoint inside a human-defined envelope; it may not define the envelope.

8.1 Where this actually is, in production

  • Beckhoff TwinCAT CoAgent (Hannover Messe 2026) — LLMs connected over the Model Context Protocol driving real machine motion sequences inside the TwinCAT platform. Engineers describe a motion in natural language; the platform generates and runs it.
  • Dell / XMPro / NVIDIA Omniverse — live PLC data from a brewery centrifuge digital twin feeding an LLM that detects boundary violations and makes small supervised SCADA-level adjustments. Deployed, not a proof of concept.
  • Siemens Industrial Copilot — code generation and diagnostics inside TIA Portal.
  • Adoption reality check: surveys through 2026 put most manufacturers at pilot stage, a minority at line-level deployment, and only a few percent letting agents make consequential decisions unsupervised. Multi-agent orchestration is still rare. Human-in-the-loop remains a hard requirement in regulated and high-precision environments, because non-deterministic behaviour is a validation problem, not just a quality problem.

8.2 Protocols and building blocks

  • 🔧 Model Context Protocol (MCP) 🆓 — the open standard for connecting models to tools and data sources. Rapidly becoming the way agents reach OPC UA servers, historians and MES.
  • 🔧 Agent2Agent (A2A) 🆓 — inter-agent interoperability across vendors.
  • 🔧 LangGraph 🆓 / CrewAI 🆓 / AutoGen 🆓 — agent orchestration frameworks.
  • 🔧 Node-RED 🆓 — unglamorous, but still the most practical glue between OT protocols and everything else.

8.3 Agents in robotics (as opposed to plant floors)

  • 📄 Code as Policies — LLMs writing robot control code. The paper that opened this line.
  • 📄 SayCan — grounding language plans in what a robot can actually do.
  • 📄 Embodied Chain-of-Thought Reasoning — CoRL 2024. Reasoning traces improve VLA action quality.
  • 📄 OpenHelix — open dual-system (planner + controller) VLA; a good template for the architecture. 🆓
  • The dual-system pattern (slow LLM planner + fast reactive controller) is now the dominant architecture — GR00T N1's System 1 / System 2 split is the clearest published example.

8.4 Safety, assurance and governance

  • 📄 Agentic AI in Engineering and Manufacturing — MIT DeCoDE Lab, 2026. 🆓 Sober analysis of bounded autonomy: agents inside tightly scoped workflows, subject to human validation, not assuming engineering accountability. ⭐
  • EU AI Act — machinery and safety components fall under high-risk obligations. If your agent touches a machine sold in the EU, this applies to you.
  • EU Machinery Regulation 2023/1230 — replaces the Machinery Directive from January 2027 and explicitly addresses self-evolving behaviour and AI-enabled safety components. This is the regulation mechatronic engineers should be reading now.
  • NIST AI Risk Management Framework 🆓
  • OWASP Top 10 for LLM Applications 🆓 — prompt injection into an agent with OPC UA write access is not a theoretical risk.
  • ISO 10218-1/-2:2025 (industrial robot safety, revised) and ISO/TS 15066 (collaborative operation).

9. Hands-On Projects

Ordered by difficulty. Each one teaches something the previous one couldn't.

#ProjectLevelRough costWhat it actually teaches
1Closed-loop DC motor position control with encoderBeginner€30Sampling, quantisation, integral windup, derivative noise
2Line follower with PID on IR arrayBeginner€40Sensor calibration, loop rate vs. speed, saturation
3Reaction wheel / inverted pendulumBeginner+€60Unstable plants, state feedback, why LQR exists 🧪
4BLDC field-oriented control with SimpleFOCIntermediate€80Commutation, current control, why FOC beats trapezoidal
5PLC-controlled sorting line in Factory I/OIntermediate€30 (licence)Ladder/ST, sequence control, HMI, industrial thinking
6ESP32 + micro-ROS sensor node into a ROS 2 graphIntermediate€20Distributed robotics, QoS, real-time boundaries
7Differential-drive robot: SLAM + Nav2Intermediate+€200TF trees, odometry drift, costmaps, localisation
83D-print an SO-101 arm, teleoperate itIntermediate+€150–250Servo calibration, leader-follower, mechanical repeatability
9Collect 50 demos, train ACT, run it on the SO-101Intermediate++GPU accessData quality, overfitting, the whole modern paradigm ⭐
10Fine-tune SmolVLA on your own taskAdvanced+GPULanguage conditioning, LoRA, evaluation protocol
11RL locomotion in Isaac Lab → real quadrupedAdvanced€1500+Domain randomisation, sim-to-real, reward shaping
12Digital twin: AAS + OPC UA of a real machineAdvanced€0Information modelling — the Industry 4.0 skill that gets hired
13Design + build a QDD actuator, characterise itAdvanced€300Torque density, backdrivability, thermal, transparency 🔬
14UMI-style handheld data collection rigAdvanced€200Robot-free data collection at scale 🔬

Project-based learning resources:


10. Hardware You Can Actually Buy or Build

Open-source and low-cost platforms, roughly by price.

Platform~CostTypeNotes
SO-101 / SO-ARM101€120–3506-DoF arm pair🆓 open hardware. Leader/follower teleoperation; the LeRobot reference platform. Kits from Hiwonder, Seeed, WowRobo. ⭐
LeKiwi€400Mobile manipulatorSO-101 on a holonomic base; open source
Koch v1.1€2505-DoF armThe predecessor design; still a good build
ALOHA / ALOHA 2€5k–20kBimanualThe reference bimanual teleoperation setup
Open Duck Mini€400BipedalApproachable legged-robot learning platform
Reachy 2 / Reachy Mini€300–70kHumanoidPollen Robotics (Hugging Face); open source
Unitree Go2 / G1€1.6k–16kQuadruped / humanoidThe default research legged platforms; SDK is usable
Franka Research 3€25k+7-DoF armThe academic manipulation standard; excellent torque control
UR cobots€20k+CobotThe industrial collaborative standard; good ROS 2 driver
TurtleBot 4€1.5kMobileThe canonical ROS 2 teaching robot
Duckietown€300+Mobile / educationComplete autonomy curriculum in a box 🎓
Open Dynamic Robot Initiative€3k+Legged actuators🆓 Open QDD actuator + leg designs from MPI/NYU

11. Classic Mechatronic Systems

Worked examples worth studying, because each one is a complete mechatronic argument:

  • ABS — wheel-slip estimation from noisy sensors under hard real-time constraints. The canonical automotive mechatronic system.
  • 3D printers — motion control, thermal control, and (in Klipper) input shaping and pressure advance. An accessible, complete control-systems case study. 🧪
  • GNSS/INS — sensor fusion; the practical home of the Kalman filter.
  • PLCs — deterministic scan-cycle computation; a genuinely different computational model worth understanding.
  • Hybrid & electric drivetrains — power-split control, energy management, thermal.
  • Hard disk drives — the highest-precision mass-produced servo system ever built; nanometre positioning at kHz bandwidth.
  • Washing machines — unbalance detection, drum resonance avoidance, cost-driven sensor minimisation. Deceptively deep.
  • Surgical robots — teleoperation, force reflection, safety architecture.
  • Wafer steppers — the extreme end: sub-nanometre stages, feed-forward everything, the field's hardest control problems.

Where things stand, honestly assessed.

TrendMaturityWhy a mechatronic engineer should care
VLAs / generalist robot policiesEarly productionChanges what "programming a robot" means. Hardware must now be learnable, not just controllable
Diffusion & flow-matching policiesProduction-readyThe strong default for contact-rich manipulation; robust to multimodal demonstrations
Real-time action chunkingProduction-readyMade large policies runnable at real robot rates — the practical unlock of 2025
GPU physics (Newton, MuJoCo-Warp)Rapidly maturingTwo orders of magnitude more simulation throughput; sim-first design becomes viable for small teams
World models (Cosmos, Genie)Research → early productSynthetic data instead of more robots; expect commercial integration around 2027
Agentic AI in plant operationsPilots, few deploymentsReal value in exception handling and supervised execution; the safety architecture is the engineering problem
MCP as industrial glueEarly, fast-movingBecoming the standard way models reach OPC UA / MES / historians
HumanoidsOverhyped, genuinely improvingMassive investment; the hard problems remain actuation, energy, hands and reliability — mechanical problems
Compliant & backdrivable actuationMature, resurgingLearned policies need hardware that survives contact; QDD, SEA and VSA are back in demand
Morphological computation / metamaterialsResearchOffload control effort into the structure; watch this over the next five years 🔬
Digital twin standardisation (AAS)Mature standard, slow adoptionThe Industry 4.0 skill with the best employability-to-effort ratio
Edge AI / TinyML on MCUsMatureCondition monitoring and anomaly detection without cloud dependency
Digital Product Passport / ecomechatronicsRegulatory-drivenEU rules will make this mandatory work, not optional differentiation
Embedded RustGrowingMemory safety in firmware; adoption rising in safety-relevant contexts
Robot data scarcityThe bottleneckThe 2026 consensus: progress is limited by data infrastructure, not model architecture

13. Journals, Conferences, Communities

Journals

Conferences

  • ICRA · IROS — the two big robotics conferences
  • RSS — smaller, higher signal-to-noise; where Diffusion Policy and ACT appeared
  • CoRL — the robot learning conference
  • AIM — IEEE/ASME Advanced Intelligent Mechatronics
  • Hannover Messe · SPS Nuremberg · automatica — where industrial reality shows up
  • NVIDIA GTC — increasingly where robotics platform announcements land

Communities


Robotics & learning

Engineering & embedded

AI


Contributing

Contributions are welcome — additions, corrections and dead-link reports alike.

The rules in short: prefer free and primary sources, mark paid ones with 💵, include the year for anything in the fast-moving sections, and give one line on why a resource is worth someone's time. Keep the mechatronic point of view — this is not a general AI, ME or EE list.

Read CONTRIBUTING.md for the full guidelines, entry format and marker conventions.

Licence

CC0

To the extent possible under law, the contributors have waived all copyright and related rights to this work.

awesome
awesome-list
electrical-engineering
industrial-automation
iot
mechanical-engineering
mechatronics
mechatronics-engineering
mechatronic-systems
python
robotics
ros2

Contributors

engyasin

10 commits

smasher2010

1 commits