Skip to content
RobothecaBeta
Log in

linorobot2

  • Software
  • Navigation and mapping
  • Framework
  • Runs on hardware you can build

A ROS 2 package that takes a robot from bare hardware to autonomous navigation, with Nav2, SLAM Toolbox and robot_localization pre-wired, and a Gazebo simulation using the same configs.

Made by Linorobot, Singapore (checked on github.com/linorobot (opens in a new tab)).

Source on GitHub: github.com/linorobot/linorobot2 (opens in a new tab). Facts read at commit f6b0bd0 (opens in a new tab).

Licenses

Code
Apache-2.0 (opens in a new tab)

Read by Robotheca from LICENSE (opens in a new tab) (Apache-2.0) at commit f6b0bd0 (opens in a new tab), on 16 Oct 2026.

Commercial use
Yes

What it does

  • Provides working configurations for Nav2, SLAM Toolbox and the robot_localization EKF, shared by physical and simulated robots.
  • Ships a templated robot URDF with a 2D lidar, an RGBD depth camera and an IMU, adjustable through one properties file.
  • Lets you convert a floor plan image into a Gazebo world using the image_to_gazebo GUI tool.
  • Batch-converts saved SLAM maps into Gazebo worlds with the create_worlds_from_maps tool.
  • Supports a range of 2D lidars and RGBD depth cameras, with drivers and topic remappings set up by the install script.
  • Supports 2WD, 4WD and Mecanum drive bases, with micro-ROS firmware for Teensy-class microcontrollers that publishes odometry and IMU data.

Written by Robotheca from the project's README (opens in a new tab) at commit f6b0bd0.

Getting started

Difficulty
Intermediate
Hardware it needs, as the project states it
A robot computer running the ROS 2 stack, plus a microcontroller such as a Teensy running micro-ROS firmware for physical robots; a workstation runs the Gazebo simulation.

Maintenance

Status
Active: a commit in the last 90 days
Newest commit
29 Sept 2026 on jazzy
Latest release
None published on GitHub

Checked on GitHub on 16 Oct 2026.

Links

Robots on Robotheca that use it

No robot on Robotheca is linked to it yet. Links come from a robot's robot.yaml, from its dependency files read as text, or from Robotheca's editors.

Robotheca lists software as a reference: nothing is hosted or run here, and every fact links to where it was read.