How unitreerobotics/qmini works
Project type and purpose
• Project Type: Open-source bipedal robotics platform
• Purpose: Provide a fully 3D-printable, modular biped robot (Qmini) with supporting hardware files (STEP, STL), URDF model, and a reference control software stack (RoboTamer4Qmini).
High-level architecture overview
• Hardware Layer
• Mechanical structure: 3D-printed links (hip, knee, ankle, base) from STEP and STL files
• Actuation: 11 Unitree 8010 brushless motors (10 for legs, 1 for neck/expansion)
• Electronics: Motor driver boards, sensors (IMU, encoders), battery pack, Raspberry Pi 4 (or alternative controller)
• Software Layer
• Robot description: URDF/XML file + meshes for simulation & collision models
• Control stack: RoboTamer4Qmini (ROS-based controllers, motion planners, gait generators)
• Simulation: Gazebo or other physics engine (leverages URDF and plugins)
• External Interfaces
• User interface / CLI on Raspberry Pi or remote workstation
• Optional networked telemetry or ROS topics for monitoring, logging, GUI
• 3D-printed chassis & joints
• Motor drivers & wiring harness
• Raspberry Pi 4 (or equivalent SBC)
• Battery / power distribution
• Sensors (IMU, encoders)
• URDF parser & robot_state_publisher
• Motion control nodes (gait generation, PID controller)
• Communication middleware (ROS topics/services over TCP/UDP)
• Simulation interface (Gazebo plugin)
• User tools (CLI scripts, ROS launch files)
c. Data flows and interactions
• Commands from user interface → motion control nodes
• Control nodes → motor driver over serial/SPI/I2C
• Sensors → feedback to control nodes
• URDF & meshes → simulation engine
• Simulation → virtual sensor feedback → control nodes
d. Architectural patterns / principles
• Layered separation: Hardware Abstraction → Control → Application
• Modular design: each joint’s motor, driver, and control node treated as a unit
• Standard ROS pub/sub for decoupling components
• Reuse of URDF across real hardware and simulation