This section presents and discusses all hardware used in the MIRTE Master.
Hardware Specifications¶
Most of the hardware used in this implementation of the MIRTE Master comes from the standard components provided by the MIRTE team. The table below lists the hardware parts, excluding only trivial components such as nuts and bolts.
| Category | Components |
|---|---|
| Chassis | |
| Panels: | |
| - Left (with OLED-display) and right chassis side panels (3D-printed) | |
| - Rear battery bracket panel (3D-printed) | |
| - 2x rear Sonar-module panel (3D-printed) | |
| - Front RGB-D camera module (3D-printed) | |
| - 1.5 mm aluminium: top plate, bottom plate and manipulator-mounting plate (laser-cut) | |
| Electronics: | |
| - Main computer: Orange Pi 3B V1.1.1 | |
| - Microcontroller: Raspberry Pi Pico H | |
| - MIRTE custom PCB | |
| - microSD card | |
| - 12V RGB LED-strip | |
| Manipulation | |
| - Upper arm limb, lower arm limb (3D-printed) | |
| - Shoulder joint bracket, wrist joint bracket (3D-printed) | |
| - Double gears, bars for 4-bar linkage of gripper, triangle tips for gripper, TPE gripper ends (3D-printed) | |
| - Mounting bracket for RGB-camera module (3D-printed) | |
| - 5x Hiwonder bus servo-motors | |
| - Ball bearing for shoulder rotation joint | |
| Powertrain | |
| - Parkside 12V 5Ah Li-ion battery | |
| - Battery-to-circuit connector (3D-printed) | |
| - 12V to 5V step-down converter | |
| - Wiring, connectors, button and fuse | |
| Locomotion | |
| - 4x geared DC-motors | |
| - 4x mecanum wheels | |
| - 4x DC-motor brackets (3D-printed) | |
| Distance sensors | |
| - 2D-LiDAR: RPLiDAR C1 | |
| - 2x Ultrasonic sensor: HC-SR04 | |
| Cameras | |
| - RGBD (depth) camera: Orbbec3D Astra Mini S | |
| - RGB-camera: 720p USB camera module |
Given that MIRTE is not produced in large quantities and no standardized spare parts are available, 3D-printing was a practical way to produce the required structural parts from adjusted versions of the provided CAD models. These parts can be divided into two groups: chassis and manipulator.
Chassis¶
The chassis consists of a top, bottom, and manipulator-mounting plate, for which aluminium plates with a thickness of 1.5 mm were used, as well as several side panels. These side panels not only act as chassis support elements but also serve as mounting points for several electronic components. For these purposes, PETG was chosen because it is easy to print, impact-resistant, and sufficiently stiff for the intended application. The aluminium plates were chosen for their rigidity and durability. Although no formal material tests were performed in this study, these choices were made to match the practical requirements of the robot’s payload and expected handling.
The translucent PETG variant used for this project also enables the user to look at the status lights on the inside of the chassis. This would otherwise not have been possible due to the aluminium top and bottom plates. During printing, orange PETG accent lines were also added to make the robot more visible to people passing by.
Manipulator¶
The manipulator consists of several components, which are listed in the table at the top of this page. This system can be divided into four groups: brackets, limbs, servo-motors, and the gripping mechanism. Given that there are four servo-motors, the arm is defined to have four degrees of freedom to be able to reach all places around the robot. There is a fifth servo-motor mounted, but it only actuates the gripping mechanism and therefore does not add any degree of freedom to the system. All of this, including the chassis, can be seen in the interactive display near the bottom of the Mechanical overview page.
Software Specifications¶
The MIRTE Master robotic platform has free open-source software available for any user to install.
The latest stable release is used in this robotic system. This software comes packaged inside a ROS application Macenski et al. (2022), a standardized framework for developing distributed robotic systems. This allows for the use of a wide variety of cross-compatible plugins and additional software packages, making rapid prototyping and development more efficient.
The ROS distribution used by the MIRTE Master platform is ROS 2 Humble Hawksbill on Ubuntu 22.04.
SLAM¶
Before the robot is able to perform any complex task in an environment, the environment must first be mapped. For this, SLAM (Simultaneous Localization and Mapping) is used. This way, the robot can dynamically update its map of the environment based on measurements from its LiDAR scanner. The robot creates an occupancy grid map, represented as an image, while estimating its own pose. The two most widely adopted SLAM frameworks in the ROS ecosystem are Cartographer Kicman et al., 2011 and SLAM Toolbox Macenski & Jambrecic, 2021. For the MIRTE Master platform, SLAM Toolbox was selected due to its superior mapping accuracy and localization performance when reliable odometry is available İnce et al., 2025. Since the MIRTE Master is dedicated to running the core robotics software stack and is not burdened by other computationally intensive workloads, the higher computational requirements of SLAM Toolbox do not pose a significant limitation. Consequently, prioritizing mapping accuracy over computational efficiency makes SLAM Toolbox the most suitable choice for this application. SLAM Toolbox was also chosen for its native ROS 2 support and good integration with other ROS 2 packages. SLAM Toolbox allows for straightforward modification of mapping behavior using the set of parameters it provides. In the case of the MIRTE Master, there are several projects that have implemented SLAM Toolbox, so finding a ready-to-use set of SLAM parameters for this robot is relatively simple. The Mirte Navigation ROS package is used for configuration files and SLAM parameter settings. It was assumed that the robot would only navigate in unknown environments without predefined or recurring maps. Localization (using AMCL) was therefore disabled in the application.
Manipulation¶
While the arm on the MIRTE Master can be controlled in joint-space, the implementation relies on task-space (Cartesian-space) control over the end-effector position.
The manner in which motion planners are typically implemented requires the integration of several complex subsystems, such as inverse and forward kinematics solvers, trajectory planners, and path planners. To accomplish the goal of task-space control over the arm, MoveIt 2 (Coleman et al. (2014)) was used.
Navigation¶
Robot navigation poses a challenge analogous to that of robot manipulation: workspace control. The robot must be able to navigate to or through a set of waypoints given in the coordinate system of the map, while also implementing a real-time controller for obstacle avoidance. Similar to MoveIt 2, Nav2 is used as a solution to this problem (Macenski et al. (2020)). Aside from path planning and real-time control, Nav2 also provides a Costmap.
- Macenski, S., Foote, T., Gerkey, B., Lalancette, C., & William Woodall. (2022). Robot Operating System 2: Design, architecture, and uses in the wild. Science Robotics, 7(66), eabm6074. 10.1126/scirobotics.abm6074
- Kicman, P., Silson, P., Tsourdos, A., & Savvaris, A. (2011, March). Cartographer - A Terrain Mapping and Landmark-based Localization System for Small Robots. AIAA Infotech at Aerospace Conference and Exhibit 2011. 10.2514/6.2011-1513
- Macenski, S., & Jambrecic, I. (2021). SLAM Toolbox: SLAM for the dynamic world. Journal of Open Source Software, 6(61), 2783. 10.21105/joss.02783
- İnce, İ., Yiltas-Kaplan, D., & Keleş, F. (2025). From Simulation to Reality: Comparative Performance Analysis of SLAM Toolbox and Cartographer in ROS 2. Electronics, 14(24). 10.3390/electronics14244822
- Coleman, D., Sucan, I. A., Chitta, S., & Correll, N. (2014). Reducing the Barrier to Entry of Complex Robotic Software: a MoveIt! Case Study. Journal of Software Engineering for Robotics, 5(1), 3–16. 10.6092/JOSER_2014_05_01_p3
- Macenski, S., Martín, F., White, R., & Ginés Clavero, J. (2020). The Marathon 2: A Navigation System. 2020 IEEE/RSJ International Conference on Intelligent Robots and Systems (IROS). https://github.com/ros-planning/navigation2