A list of awesome mechatronics books, courses and software.
See the code
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
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
Mechatronics has been redefined roughly once per industrial revolution, and the current redefinition is the sharpest since the 1990s.
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:
| Term | Rough meaning | Who pushes it |
|---|---|---|
| Embodied AI | AI 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 AI | The broader commercial umbrella: models + simulation + compute sold as one stack for real-world machines | NVIDIA, BCG, investors |
| Mechatronics | The engineering discipline that actually builds the body the AI acts through | Everyone, 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.
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.
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
You want to build something that moves before you learn Laplace transforms. This is a legitimate order.
lerobot examples.The classics, kept because they are still the right first books:
| Course | Who | Cost | Why |
|---|---|---|---|
| Control Bootcamp | Steve Brunton, UW | 🆓 | Best state-space introduction on YouTube |
| Modern Robotics Specialization | Northwestern | 🆓 audit | Screw theory done properly, with CoppeliaSim labs |
| Underactuated Robotics | MIT | 🆓 | Trajectory optimisation, LQR trees, contact 🔬 |
| Robotic Manipulation | MIT | 🆓 | The manipulation course, with Drake notebooks 🔬 |
| SLAM lectures | Cyrill Stachniss, Bonn | 🆓 | The reference SLAM lecture series |
| Sim-to-Real with the SO-101 | NVIDIA | 🆓 | Full pipeline: Isaac Sim → Isaac Lab → GR00T → real arm 🧪 |
| LeRobot docs & tutorials | Hugging Face | 🆓 | Imitation learning and VLAs, hands-on, end to end ⭐ |
| Introduction to Robotics CS223A | Khatib, Stanford | 🆓 | Classic; operational space control from the source |
| Learn 5 PLCs in a Day | Udemy | 💵 | Practical multi-vendor PLC exposure |
| From Wire to PLC | Udemy | 💵 | Panel wiring → ladder → commissioning |
| Wearable Robotics — Exoskeletons | Udemy | 💵 | Niche but well-made |
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.
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:
Selection cheat-sheet:
| Need | Architecture | Typical ratio | Trade-off |
|---|---|---|---|
| Precise position, high stiffness | Harmonic / strain wave | 50:1–160:1 | Non-backdrivable, expensive, torque ripple |
| High dynamics, force control, impact | Quasi-direct drive (QDD) | 6:1–10:1 | Large motor, high current, heat |
| Safe human contact, energy storage | Series elastic (SEA) | any + spring | Bandwidth limited by spring, extra sensing |
| Cheap, high ratio, tolerant | Cycloidal | 20:1–100:1 | Vibration, harder to manufacture well |
| Lightweight distal mass | Cable / tendon drive | varies | Friction, stretch, routing complexity |
Learning-based manipulation made compliance fashionable again: policies that touch things need hardware that can survive touching things.
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.
| Tool | Type | Cost | Note |
|---|---|---|---|
| FreeCAD | Parametric CAD | 🆓 | v1.x finally fixed the topological naming problem; genuinely usable now |
| Onshape | Cloud CAD | 🆓 free tier | Free for public documents; excellent for open-source hardware |
| SolidWorks | CAD + CAE | 💵 | Industry default; motion + FEA add-ins |
| Fusion | CAD/CAM/CAE | 💵 (free personal) | Integrated generative design and CAM |
| nTop | Implicit modelling | 💵 | Lattices, topology optimisation, field-driven design |
| Ansys / COMSOL | Multiphysics FEA | 💵 | Thermal + structural + electromagnetic coupling |
| CalculiX / Code_Aster | FEA solver | 🆓 | Free FEA; usable via FreeCAD FEM workbench |
| ToOptix / ToPy | Topology optimisation | 🆓 | Learn the method before paying for a suite |
| OpenModelica | Acausal multi-domain sim | 🆓 | The right tool for mechanical+hydraulic+electrical system models |
| Simscape | Multi-domain sim | 💵 | The commercial equivalent, tightly coupled to Simulink |
| Blender | 3D modelling | 🆓 | Not CAD, but the standard for robot visual meshes and rendering |
| PrusaSlicer / OrcaSlicer | Slicers | 🆓 | Printed robot parts: print orientation determines layer-direction strength |
| Platform | Role | Note |
|---|---|---|
| Arduino 🆓 | Learning, prototyping | The Uno R4 / Nano ESP32 generation is far more capable than the AVR days |
| ESP32 family 🆓 | Wireless mechatronics | Wi-Fi/BLE + dual core + enough RAM for micro-ROS |
| Raspberry Pi Pico / RP2350 🆓 | Real-time IO | PIO state machines are excellent for encoder decoding and step generation |
| STM32 💵 | Production motor control | The industry default for motor drives; G4/H7 for FOC |
| Teensy 4.x 💵 | High-rate control loops | 600 MHz Cortex-M7; underrated for 10 kHz+ loops |
| Raspberry Pi 5 💵 | Linux + ROS 2 | Enough for perception at modest rates; add a Hailo or Coral for NN inference |
| NVIDIA Jetson Orin / Thor 💵 | On-robot policy inference | Thor / T4000 (Blackwell, 2026) is what current VLAs are deployed on |
embedded-hal 🆓 — async embedded Rust. Increasingly serious for safety-relevant firmware; memory safety without a GC.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.
This is the part of Industry 4.0 that actually matters and that most curricula skip.
| Distro | Released | Ubuntu | Support until | Use it? |
|---|---|---|---|---|
| Lyrical Luth | May 2026 | 26.04 | May 2031 | ✅ New production projects (LTS) |
| Kilted Kaiju | May 2025 | 24.04 | Nov 2026 | ⚠️ Migrate off |
| Jazzy Jalisco | May 2024 | 24.04 | May 2029 | ✅ Safe, widest package support today |
| Humble Hawksbill | May 2022 | 22.04 | May 2027 | ⚠️ Plan migration |
ROS 1 reached end of life in May 2025. New projects should not use it.
The physics-engine landscape has been rewritten by GPU acceleration.
| Simulator | Cost | Best 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 | 🆓 edu | Teaching 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.
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.
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:
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.
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.
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:
| Model | Params | Licence | Notes |
|---|---|---|---|
| SmolVLA | 450M | 🆓 Apache | Hugging Face, June 2025. Trained purely on community datasets; runs on consumer hardware. Best starting point. ⭐ 📄 |
| OpenVLA | 7B | 🆓 | Stanford/Berkeley, 2024. ~970k Open X-Embodiment episodes; DINOv2 + SigLIP + Llama 2. The reference open VLA. 📄 code |
| OpenVLA-OFT | 7B | 🆓 | Optimised fine-tuning recipe; large speed/success gains over base OpenVLA |
| π₀ / openpi | ~3B | 🆓 weights | Physical 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. 📄 |
| Octo | 27M–93M | 🆓 | Generalist transformer policy; small and easy to fine-tune |
| SpatialVLA | 4B | 🆓 | Explicit 3D spatial representations |
| MolmoAct | — | 🆓 | "Action reasoning model" — reasons in space before acting |
| BitVLA | 3B | 🆓 | 1-bit weights; VLA inference on constrained hardware 🔬 |
| Gemini Robotics On-Device | — | 💵 restricted | Google DeepMind; on-robot inference without cloud |
Surveys — read one of these before the papers:
Learned simulators that predict how the world evolves given actions — used for synthetic data generation, planning in imagination, and safe evaluation.
| Resource | What |
|---|---|
| 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) |
The single highest-value practical exercise in modern mechatronics. Under €500 of hardware and one afternoon.
pip install, no ROS required. Includes ACT, Diffusion Policy, VQ-BeT, π₀, SmolVLA, HIL-SERL, TD-MPC. ⭐ 📄 ICLR 2026lerobot code. Read this cover to cover. ⭐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.
"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.
Ordered by difficulty. Each one teaches something the previous one couldn't.
| # | Project | Level | Rough cost | What it actually teaches |
|---|---|---|---|---|
| 1 | Closed-loop DC motor position control with encoder | Beginner | €30 | Sampling, quantisation, integral windup, derivative noise |
| 2 | Line follower with PID on IR array | Beginner | €40 | Sensor calibration, loop rate vs. speed, saturation |
| 3 | Reaction wheel / inverted pendulum | Beginner+ | €60 | Unstable plants, state feedback, why LQR exists 🧪 |
| 4 | BLDC field-oriented control with SimpleFOC | Intermediate | €80 | Commutation, current control, why FOC beats trapezoidal |
| 5 | PLC-controlled sorting line in Factory I/O | Intermediate | €30 (licence) | Ladder/ST, sequence control, HMI, industrial thinking |
| 6 | ESP32 + micro-ROS sensor node into a ROS 2 graph | Intermediate | €20 | Distributed robotics, QoS, real-time boundaries |
| 7 | Differential-drive robot: SLAM + Nav2 | Intermediate+ | €200 | TF trees, odometry drift, costmaps, localisation |
| 8 | 3D-print an SO-101 arm, teleoperate it | Intermediate+ | €150–250 | Servo calibration, leader-follower, mechanical repeatability |
| 9 | Collect 50 demos, train ACT, run it on the SO-101 | Intermediate+ | +GPU access | Data quality, overfitting, the whole modern paradigm ⭐ |
| 10 | Fine-tune SmolVLA on your own task | Advanced | +GPU | Language conditioning, LoRA, evaluation protocol |
| 11 | RL locomotion in Isaac Lab → real quadruped | Advanced | €1500+ | Domain randomisation, sim-to-real, reward shaping |
| 12 | Digital twin: AAS + OPC UA of a real machine | Advanced | €0 | Information modelling — the Industry 4.0 skill that gets hired |
| 13 | Design + build a QDD actuator, characterise it | Advanced | €300 | Torque density, backdrivability, thermal, transparency 🔬 |
| 14 | UMI-style handheld data collection rig | Advanced | €200 | Robot-free data collection at scale 🔬 |
Project-based learning resources:
Open-source and low-cost platforms, roughly by price.
| Platform | ~Cost | Type | Notes |
|---|---|---|---|
| SO-101 / SO-ARM101 | €120–350 | 6-DoF arm pair | 🆓 open hardware. Leader/follower teleoperation; the LeRobot reference platform. Kits from Hiwonder, Seeed, WowRobo. ⭐ |
| LeKiwi | €400 | Mobile manipulator | SO-101 on a holonomic base; open source |
| Koch v1.1 | €250 | 5-DoF arm | The predecessor design; still a good build |
| ALOHA / ALOHA 2 | €5k–20k | Bimanual | The reference bimanual teleoperation setup |
| Open Duck Mini | €400 | Bipedal | Approachable legged-robot learning platform |
| Reachy 2 / Reachy Mini | €300–70k | Humanoid | Pollen Robotics (Hugging Face); open source |
| Unitree Go2 / G1 | €1.6k–16k | Quadruped / humanoid | The default research legged platforms; SDK is usable |
| Franka Research 3 | €25k+ | 7-DoF arm | The academic manipulation standard; excellent torque control |
| UR cobots | €20k+ | Cobot | The industrial collaborative standard; good ROS 2 driver |
| TurtleBot 4 | €1.5k | Mobile | The canonical ROS 2 teaching robot |
| Duckietown | €300+ | Mobile / education | Complete autonomy curriculum in a box 🎓 |
| Open Dynamic Robot Initiative | €3k+ | Legged actuators | 🆓 Open QDD actuator + leg designs from MPI/NYU |
Worked examples worth studying, because each one is a complete mechatronic argument:
Where things stand, honestly assessed.
| Trend | Maturity | Why a mechatronic engineer should care |
|---|---|---|
| VLAs / generalist robot policies | Early production | Changes what "programming a robot" means. Hardware must now be learnable, not just controllable |
| Diffusion & flow-matching policies | Production-ready | The strong default for contact-rich manipulation; robust to multimodal demonstrations |
| Real-time action chunking | Production-ready | Made large policies runnable at real robot rates — the practical unlock of 2025 |
| GPU physics (Newton, MuJoCo-Warp) | Rapidly maturing | Two orders of magnitude more simulation throughput; sim-first design becomes viable for small teams |
| World models (Cosmos, Genie) | Research → early product | Synthetic data instead of more robots; expect commercial integration around 2027 |
| Agentic AI in plant operations | Pilots, few deployments | Real value in exception handling and supervised execution; the safety architecture is the engineering problem |
| MCP as industrial glue | Early, fast-moving | Becoming the standard way models reach OPC UA / MES / historians |
| Humanoids | Overhyped, genuinely improving | Massive investment; the hard problems remain actuation, energy, hands and reliability — mechanical problems |
| Compliant & backdrivable actuation | Mature, resurging | Learned policies need hardware that survives contact; QDD, SEA and VSA are back in demand |
| Morphological computation / metamaterials | Research | Offload control effort into the structure; watch this over the next five years 🔬 |
| Digital twin standardisation (AAS) | Mature standard, slow adoption | The Industry 4.0 skill with the best employability-to-effort ratio |
| Edge AI / TinyML on MCUs | Mature | Condition monitoring and anomaly detection without cloud dependency |
| Digital Product Passport / ecomechatronics | Regulatory-driven | EU rules will make this mandatory work, not optional differentiation |
| Embedded Rust | Growing | Memory safety in firmware; adoption rising in safety-relevant contexts |
| Robot data scarcity | The bottleneck | The 2026 consensus: progress is limited by data infrastructure, not model architecture |
Journals
Conferences
Communities
Robotics & learning
Engineering & embedded
AI
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.
To the extent possible under law, the contributors have waived all copyright and related rights to this work.
A list of awesome mechatronics books, courses and software.
See the code
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
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
Mechatronics has been redefined roughly once per industrial revolution, and the current redefinition is the sharpest since the 1990s.
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:
| Term | Rough meaning | Who pushes it |
|---|---|---|
| Embodied AI | AI 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 AI | The broader commercial umbrella: models + simulation + compute sold as one stack for real-world machines | NVIDIA, BCG, investors |
| Mechatronics | The engineering discipline that actually builds the body the AI acts through | Everyone, 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.
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.
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
You want to build something that moves before you learn Laplace transforms. This is a legitimate order.
lerobot examples.The classics, kept because they are still the right first books:
| Course | Who | Cost | Why |
|---|---|---|---|
| Control Bootcamp | Steve Brunton, UW | 🆓 | Best state-space introduction on YouTube |
| Modern Robotics Specialization | Northwestern | 🆓 audit | Screw theory done properly, with CoppeliaSim labs |
| Underactuated Robotics | MIT | 🆓 | Trajectory optimisation, LQR trees, contact 🔬 |
| Robotic Manipulation | MIT | 🆓 | The manipulation course, with Drake notebooks 🔬 |
| SLAM lectures | Cyrill Stachniss, Bonn | 🆓 | The reference SLAM lecture series |
| Sim-to-Real with the SO-101 | NVIDIA | 🆓 | Full pipeline: Isaac Sim → Isaac Lab → GR00T → real arm 🧪 |
| LeRobot docs & tutorials | Hugging Face | 🆓 | Imitation learning and VLAs, hands-on, end to end ⭐ |
| Introduction to Robotics CS223A | Khatib, Stanford | 🆓 | Classic; operational space control from the source |
| Learn 5 PLCs in a Day | Udemy | 💵 | Practical multi-vendor PLC exposure |
| From Wire to PLC | Udemy | 💵 | Panel wiring → ladder → commissioning |
| Wearable Robotics — Exoskeletons | Udemy | 💵 | Niche but well-made |
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.
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:
Selection cheat-sheet:
| Need | Architecture | Typical ratio | Trade-off |
|---|---|---|---|
| Precise position, high stiffness | Harmonic / strain wave | 50:1–160:1 | Non-backdrivable, expensive, torque ripple |
| High dynamics, force control, impact | Quasi-direct drive (QDD) | 6:1–10:1 | Large motor, high current, heat |
| Safe human contact, energy storage | Series elastic (SEA) | any + spring | Bandwidth limited by spring, extra sensing |
| Cheap, high ratio, tolerant | Cycloidal | 20:1–100:1 | Vibration, harder to manufacture well |
| Lightweight distal mass | Cable / tendon drive | varies | Friction, stretch, routing complexity |
Learning-based manipulation made compliance fashionable again: policies that touch things need hardware that can survive touching things.
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.
| Tool | Type | Cost | Note |
|---|---|---|---|
| FreeCAD | Parametric CAD | 🆓 | v1.x finally fixed the topological naming problem; genuinely usable now |
| Onshape | Cloud CAD | 🆓 free tier | Free for public documents; excellent for open-source hardware |
| SolidWorks | CAD + CAE | 💵 | Industry default; motion + FEA add-ins |
| Fusion | CAD/CAM/CAE | 💵 (free personal) | Integrated generative design and CAM |
| nTop | Implicit modelling | 💵 | Lattices, topology optimisation, field-driven design |
| Ansys / COMSOL | Multiphysics FEA | 💵 | Thermal + structural + electromagnetic coupling |
| CalculiX / Code_Aster | FEA solver | 🆓 | Free FEA; usable via FreeCAD FEM workbench |
| ToOptix / ToPy | Topology optimisation | 🆓 | Learn the method before paying for a suite |
| OpenModelica | Acausal multi-domain sim | 🆓 | The right tool for mechanical+hydraulic+electrical system models |
| Simscape | Multi-domain sim | 💵 | The commercial equivalent, tightly coupled to Simulink |
| Blender | 3D modelling | 🆓 | Not CAD, but the standard for robot visual meshes and rendering |
| PrusaSlicer / OrcaSlicer | Slicers | 🆓 | Printed robot parts: print orientation determines layer-direction strength |
| Platform | Role | Note |
|---|---|---|
| Arduino 🆓 | Learning, prototyping | The Uno R4 / Nano ESP32 generation is far more capable than the AVR days |
| ESP32 family 🆓 | Wireless mechatronics | Wi-Fi/BLE + dual core + enough RAM for micro-ROS |
| Raspberry Pi Pico / RP2350 🆓 | Real-time IO | PIO state machines are excellent for encoder decoding and step generation |
| STM32 💵 | Production motor control | The industry default for motor drives; G4/H7 for FOC |
| Teensy 4.x 💵 | High-rate control loops | 600 MHz Cortex-M7; underrated for 10 kHz+ loops |
| Raspberry Pi 5 💵 | Linux + ROS 2 | Enough for perception at modest rates; add a Hailo or Coral for NN inference |
| NVIDIA Jetson Orin / Thor 💵 | On-robot policy inference | Thor / T4000 (Blackwell, 2026) is what current VLAs are deployed on |
embedded-hal 🆓 — async embedded Rust. Increasingly serious for safety-relevant firmware; memory safety without a GC.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.
This is the part of Industry 4.0 that actually matters and that most curricula skip.
| Distro | Released | Ubuntu | Support until | Use it? |
|---|---|---|---|---|
| Lyrical Luth | May 2026 | 26.04 | May 2031 | ✅ New production projects (LTS) |
| Kilted Kaiju | May 2025 | 24.04 | Nov 2026 | ⚠️ Migrate off |
| Jazzy Jalisco | May 2024 | 24.04 | May 2029 | ✅ Safe, widest package support today |
| Humble Hawksbill | May 2022 | 22.04 | May 2027 | ⚠️ Plan migration |
ROS 1 reached end of life in May 2025. New projects should not use it.
The physics-engine landscape has been rewritten by GPU acceleration.
| Simulator | Cost | Best 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 | 🆓 edu | Teaching 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.
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.
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:
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.
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.
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:
| Model | Params | Licence | Notes |
|---|---|---|---|
| SmolVLA | 450M | 🆓 Apache | Hugging Face, June 2025. Trained purely on community datasets; runs on consumer hardware. Best starting point. ⭐ 📄 |
| OpenVLA | 7B | 🆓 | Stanford/Berkeley, 2024. ~970k Open X-Embodiment episodes; DINOv2 + SigLIP + Llama 2. The reference open VLA. 📄 code |
| OpenVLA-OFT | 7B | 🆓 | Optimised fine-tuning recipe; large speed/success gains over base OpenVLA |
| π₀ / openpi | ~3B | 🆓 weights | Physical 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. 📄 |
| Octo | 27M–93M | 🆓 | Generalist transformer policy; small and easy to fine-tune |
| SpatialVLA | 4B | 🆓 | Explicit 3D spatial representations |
| MolmoAct | — | 🆓 | "Action reasoning model" — reasons in space before acting |
| BitVLA | 3B | 🆓 | 1-bit weights; VLA inference on constrained hardware 🔬 |
| Gemini Robotics On-Device | — | 💵 restricted | Google DeepMind; on-robot inference without cloud |
Surveys — read one of these before the papers:
Learned simulators that predict how the world evolves given actions — used for synthetic data generation, planning in imagination, and safe evaluation.
| Resource | What |
|---|---|
| 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) |
The single highest-value practical exercise in modern mechatronics. Under €500 of hardware and one afternoon.
pip install, no ROS required. Includes ACT, Diffusion Policy, VQ-BeT, π₀, SmolVLA, HIL-SERL, TD-MPC. ⭐ 📄 ICLR 2026lerobot code. Read this cover to cover. ⭐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.
"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.
Ordered by difficulty. Each one teaches something the previous one couldn't.
| # | Project | Level | Rough cost | What it actually teaches |
|---|---|---|---|---|
| 1 | Closed-loop DC motor position control with encoder | Beginner | €30 | Sampling, quantisation, integral windup, derivative noise |
| 2 | Line follower with PID on IR array | Beginner | €40 | Sensor calibration, loop rate vs. speed, saturation |
| 3 | Reaction wheel / inverted pendulum | Beginner+ | €60 | Unstable plants, state feedback, why LQR exists 🧪 |
| 4 | BLDC field-oriented control with SimpleFOC | Intermediate | €80 | Commutation, current control, why FOC beats trapezoidal |
| 5 | PLC-controlled sorting line in Factory I/O | Intermediate | €30 (licence) | Ladder/ST, sequence control, HMI, industrial thinking |
| 6 | ESP32 + micro-ROS sensor node into a ROS 2 graph | Intermediate | €20 | Distributed robotics, QoS, real-time boundaries |
| 7 | Differential-drive robot: SLAM + Nav2 | Intermediate+ | €200 | TF trees, odometry drift, costmaps, localisation |
| 8 | 3D-print an SO-101 arm, teleoperate it | Intermediate+ | €150–250 | Servo calibration, leader-follower, mechanical repeatability |
| 9 | Collect 50 demos, train ACT, run it on the SO-101 | Intermediate+ | +GPU access | Data quality, overfitting, the whole modern paradigm ⭐ |
| 10 | Fine-tune SmolVLA on your own task | Advanced | +GPU | Language conditioning, LoRA, evaluation protocol |
| 11 | RL locomotion in Isaac Lab → real quadruped | Advanced | €1500+ | Domain randomisation, sim-to-real, reward shaping |
| 12 | Digital twin: AAS + OPC UA of a real machine | Advanced | €0 | Information modelling — the Industry 4.0 skill that gets hired |
| 13 | Design + build a QDD actuator, characterise it | Advanced | €300 | Torque density, backdrivability, thermal, transparency 🔬 |
| 14 | UMI-style handheld data collection rig | Advanced | €200 | Robot-free data collection at scale 🔬 |
Project-based learning resources:
Open-source and low-cost platforms, roughly by price.
| Platform | ~Cost | Type | Notes |
|---|---|---|---|
| SO-101 / SO-ARM101 | €120–350 | 6-DoF arm pair | 🆓 open hardware. Leader/follower teleoperation; the LeRobot reference platform. Kits from Hiwonder, Seeed, WowRobo. ⭐ |
| LeKiwi | €400 | Mobile manipulator | SO-101 on a holonomic base; open source |
| Koch v1.1 | €250 | 5-DoF arm | The predecessor design; still a good build |
| ALOHA / ALOHA 2 | €5k–20k | Bimanual | The reference bimanual teleoperation setup |
| Open Duck Mini | €400 | Bipedal | Approachable legged-robot learning platform |
| Reachy 2 / Reachy Mini | €300–70k | Humanoid | Pollen Robotics (Hugging Face); open source |
| Unitree Go2 / G1 | €1.6k–16k | Quadruped / humanoid | The default research legged platforms; SDK is usable |
| Franka Research 3 | €25k+ | 7-DoF arm | The academic manipulation standard; excellent torque control |
| UR cobots | €20k+ | Cobot | The industrial collaborative standard; good ROS 2 driver |
| TurtleBot 4 | €1.5k | Mobile | The canonical ROS 2 teaching robot |
| Duckietown | €300+ | Mobile / education | Complete autonomy curriculum in a box 🎓 |
| Open Dynamic Robot Initiative | €3k+ | Legged actuators | 🆓 Open QDD actuator + leg designs from MPI/NYU |
Worked examples worth studying, because each one is a complete mechatronic argument:
Where things stand, honestly assessed.
| Trend | Maturity | Why a mechatronic engineer should care |
|---|---|---|
| VLAs / generalist robot policies | Early production | Changes what "programming a robot" means. Hardware must now be learnable, not just controllable |
| Diffusion & flow-matching policies | Production-ready | The strong default for contact-rich manipulation; robust to multimodal demonstrations |
| Real-time action chunking | Production-ready | Made large policies runnable at real robot rates — the practical unlock of 2025 |
| GPU physics (Newton, MuJoCo-Warp) | Rapidly maturing | Two orders of magnitude more simulation throughput; sim-first design becomes viable for small teams |
| World models (Cosmos, Genie) | Research → early product | Synthetic data instead of more robots; expect commercial integration around 2027 |
| Agentic AI in plant operations | Pilots, few deployments | Real value in exception handling and supervised execution; the safety architecture is the engineering problem |
| MCP as industrial glue | Early, fast-moving | Becoming the standard way models reach OPC UA / MES / historians |
| Humanoids | Overhyped, genuinely improving | Massive investment; the hard problems remain actuation, energy, hands and reliability — mechanical problems |
| Compliant & backdrivable actuation | Mature, resurging | Learned policies need hardware that survives contact; QDD, SEA and VSA are back in demand |
| Morphological computation / metamaterials | Research | Offload control effort into the structure; watch this over the next five years 🔬 |
| Digital twin standardisation (AAS) | Mature standard, slow adoption | The Industry 4.0 skill with the best employability-to-effort ratio |
| Edge AI / TinyML on MCUs | Mature | Condition monitoring and anomaly detection without cloud dependency |
| Digital Product Passport / ecomechatronics | Regulatory-driven | EU rules will make this mandatory work, not optional differentiation |
| Embedded Rust | Growing | Memory safety in firmware; adoption rising in safety-relevant contexts |
| Robot data scarcity | The bottleneck | The 2026 consensus: progress is limited by data infrastructure, not model architecture |
Journals
Conferences
Communities
Robotics & learning
Engineering & embedded
AI
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.
To the extent possible under law, the contributors have waived all copyright and related rights to this work.