Simple Explanation (ELI5)

Imagine building a LEGO tower on a wobbling base without instructions—just trial and error. This study is the ultimate manual telling you exactly which bricks you need, in what order, and how to connect them so the tower balances itself, no matter what shape you want.

Key Advantages & Current Limits

🟢 Pros: Turns a chaotic "trial-and-error" process into a standardized, reusable procedure for any two-wheeled vehicle. 🟢 Pros: Integrates mechanics, electronics, and software from the start (MBSE approach), avoiding costly late-stage redesigns. 🔴 Cons: Requires advanced systems engineering skills and modeling tools (SysML, co-simulation) that are non-trivial for small makers. 🔴 Cons: Validation relies on a single case study (two-seater); time is needed to confirm universality on edge cases (e.g., variable loads, rough terrain).

Future Outlook & Takeaways

In the next 3-5 years, this "universal manual" will become the standard for startups and universities, accelerating the development of delivery robots, agile wheelchairs, and two-wheeled urban taxis. Thanks to integrated simulation, physical prototypes will be fewer and safer, slashing costs and time to bring these vehicles to our streets.

How Do You Design a Self-Balancing Vehicle? The Universal Method

Article

100%

Scooters, two-wheeled robots, futuristic wheelchairs: self-balancing vehicles are everywhere. Yet, for decades, builders navigated by sight. Thousands of studies existed on how to *control* them — they are inherently unstable, like a broom balanced on a palm — but a complete guide on how to *design* them from scratch, from requirements to finished vehicle, was missing.

Now a research team has filled the gap. Published in *Machines*, the paper proposes a mechatronic procedure based on the MBSE (Model-Based Systems Engineering) approach. The key idea is to treat the vehicle not as a set of separate parts, but as a complex system where mechanical, electrical, and software components exchange energy and information through well-defined interfaces.

By analyzing these exchanges, the authors identified the minimal set of parameters essential for design. The result is a logical sequence of steps, each with clear inputs and outputs, represented with standardized diagrams. The procedure covers everything: chassis, motors, sensors, batteries, control algorithms. It works for any variant, from warehouse robots to passenger vehicles.

The method was validated by designing a full-scale real vehicle in detail. Finally, engineers and makers have a reliable map to turn an unstable idea into a solid project.

Bonus

100%

The paper formalizes a mechatronic design procedure for self-balancing vehicles (non-holonomic, underactuated systems) using the MBSE framework and languages like SysML. The core contribution is a functional architecture based on power flows (bond-graph approach) and logical flows, decoupling physical domains (mechanical, electrical, hydraulic, thermal) from control logic.

The procedure unfolds in sequential phases: 1) Requirements analysis (Stakeholder needs -> System Requirements); 2) Logical architecture and interface definition (Logical Architecture, ICD); 3) Kinematic and dynamic synthesis (inverted pendulum on cart model, inertial parameter calculation, center of mass); 4) Actuator and drivetrain sizing (motors, gearboxes, wheels) via performance analysis (torque/speed, bandwidth); 5) Sensor selection (IMU, encoders) for full state observability; 6) Electronic architecture design (BMS, drivers, MCU, CAN/EtherCAT bus); 7) Control synthesis (LQR, MPC, SMC) with robustness analysis (gain/phase margins, μ-analysis); 8) Verification and Validation (V&V) via co-simulation (Simulink/Modelica + 3D multibody) and Hardware-in-the-Loop (HIL).

The case study applies the workflow to a two-passenger, parallel two-wheeled vehicle, demonstrating how the procedure manages trade-offs between mass, battery volume, payload capacity, and dynamic stability, producing technical specs ready for rapid prototyping.