Open Source RoboticsRobots, software & learning

Linorobot

Robot / hardware build

Configurable ROS 2 mobile-robot stack; this profile selects a two-wheel differential-drive, ESP32 control route with separately versioned firmware and measured chassis parameters. [1]

Build & first use →Official website

For
Builders able to select motors, wire electronics and configure ROS 2 [1]
Cost
No current cost or bill of materials established yet.
Source rights
Named licenses are documented by part. Review licenses
Unknowns
tools not fully established. Review gaps

Source researched · Not tested by us
Sources checked · Research details

Licenses & related hardware

Requirements · Research details and dates

On this page

Overview

Linorobot2 combines ROS 2 navigation, mapping and state estimation with a configurable mobile base. This profile selects the documented two-wheel differential-drive route with an ESP32 running micro-ROS. It is a configuration choice within a platform that also supports four-wheel skid-steer and mecanum robots, not a claim that a particular complete kit has been built or tested. [1] [5] [9]

Is this for you?

Known limitations
  • No single complete chassis BOM or delivered cost established for the selected route
  • Humble firmware branch is unsupported; Teensy removed from Jazzy and Lyrical
  • Simulation configuration does not replace physical odometry and sensor calibration

Configuration and documentation comparison, not a hardware test.

[1] [9] · Editorial assessment

3D preview

Linorobot default 2WD simulation model. The default two-wheel-drive description uses simple source boxes, cylinders and spheres. This illustrates its configured chassis and sensor positions, not a detailed fabrication assembly or every Linorobot build.

The 3D preview loads after the page.

Drag to orbit · Scroll or pinch to zoom · Right-drag to pan. Use the view buttons for front, side and top views. The tree shows names supplied by the source; unnamed bodies remain labeled as such.

Download original URDF source bundle (ZIP) · File checksums and provenance

Separate bodies can be inspected in the model tree. Explode is a viewing aid, not an assembly sequence.

Source, license and scale

Source: Linorobot contributors, revision f6b0bd0350c4a9d6b815ef4bb5c701a1e5129711. Original and preview: Apache-2.0. Preview conversion by Open Source Robotics; source files unchanged inside the downloadable bundle. Preview coordinates are centered and rounded to six decimal places. URDF visual origins, mesh scales and joint transforms applied at zero joint positions, then metres converted to millimetres. No physical part tested.

Viewer: three-cad-viewer 5.0.7 (MIT license). Confirm scale and manufacturing settings before printing.

What you need

Operating system
  • Firmware guide: Jazzy on Ubuntu24.04 or Lyrical on Ubuntu26.04; match both repository branches

[9]

Host computer

ROS 2 workstation for setup and firmware build; onboard robot computer if selecting the onboard-compute architecture.

[5]

Dependencies
  • Separate linorobot2_hardware firmware
  • PlatformIO and micro-ROS
  • Nav2, SLAM Toolbox and robot_localization

[1] [5] [9]

Hardware & parts

Hardware configuration

Selected route: two-wheel differential drive; the platform also supports four-wheel skid-steer and mecanum configurations.

[1] [9]

Actuators
  • Two driven motors with encoders; exact motor model remains a build choice

[9]

Controller

ESP32 micro-ROS firmware and separate ROS 2 computer for the selected route.

[5] [9]

Assembly & first use

Project documentation [1]

Assembly

Builder-selected chassis, motor drivers, encoders and power components wired to the chosen ESP32 configuration.

[9]

Calibration

Verify motor and encoder signs; measure encoder counts, wheel diameter and wheel separation; tune limits and IMU orientation.

[9]

Cost

No current, complete configuration-specific build cost has been established for this profile.

Project notes

Preserve software and firmware as separate revisions

The ROS packages and microcontroller firmware live in different repositories. The main overview still mentions Teensy, but the separately preserved firmware guide says Teensy was removed from Jazzy and Lyrical, with its remaining Humble branch unsupported. The firmware guide lists Jazzy with Ubuntu 24.04 and Lyrical with Ubuntu 26.04. Match the ROS branch, firmware branch and board target rather than following an old Teensy recipe against a newer firmware checkout. [1] [9] [11]

For the selected ESP32 route, the firmware handles motor control and publishes encoder odometry and IMU data through micro-ROS. The ROS computer fuses those measurements and runs the higher-level stack. The installation guide requires robot software on the workstation used to build the firmware; the onboard-computer configuration also needs it on the robot. [5] [9]

A supported drive type is not a complete parts list

A two-wheel build still needs a chosen chassis, encoder-equipped motors, compatible drivers, power components and sensors. The reviewed documentation supplies reference wiring and configurable robot descriptions, but this review has not reconciled a complete procurement list or current delivered price for one manufactured chassis. Choose and record those parts before assigning a budget or copying geometry values. [4] [9]

The firmware distinguishes two-wheel differential drive, four-wheel skid-steer and mecanum kinematics. Its example motor, encoder and wheel constants are configuration inputs. They are not measurements of the robot on your bench. [9]

Establish reliable odometry before mapping

Upstream calibration instructions require the robot to be elevated with its wheels clear of the ground. Check motor direction and encoder sign, then establish counts per revolution, wheel diameter and wheel separation for the actual assembly. The guide also explains limiting commanded speed below the motor maximum so the speed controller retains room to correct errors. [9]

An IMU requires its own orientation and configuration checks; the firmware guide explicitly allows initial testing without one and warns that a misconfigured IMU can break navigation. Verify the base measurements and transforms before interpreting a distorted map as a planner problem. This sequence is an editorial synthesis of the calibration and ROS setup documentation, not a reproduction result. [7] [8] [9]

The main repository and separately preserved firmware carry Apache-2.0 licenses. Their robot-description templates and reference diagrams do not establish complete manufacturing source for every purchased motor, driver or sensor. No firmware compilation, installation, hardware calibration or navigation run was performed in this review. [3] [10]

What we checked

Source research only; no installation, physical build or performance test performed. No affiliate links added.

Not yet established

  • Requirements: tools
  • A step-by-step setup summary

Updates

Upstream last updated
Sep 29, 2026 [2]
Latest release
Not established
Profile updated
Oct 1, 2026
Sources last checked
Oct 1, 2026
Next review
Oct 31, 2026
Reviewed revision
f6b0bd0350c4a9d6b815ef4bb5c701a1e5129711 (commit snapshot; no published stable release found) · combined hardware and software repository

Source files and licenses

Available project sources support research coverage; complete build and commercial qualification remain separate.

LayerAvailability / license
mechanical designavailable · Apache-2.0
Software, documentation and robot-description templates; mechanical description is not a complete manufacturing design for the selected chassis. [3] [4]
electronicsavailable · Apache-2.0
Reference wiring and configuration documentation, not manufacturer source for every purchased board. [9] [10]
firmwareavailable · Apache-2.0
Separate preserved firmware; no build or compatibility test performed. [9] [10] [11]
softwareavailable · Apache-2.0
Software, documentation and robot-description templates; mechanical description is not a complete manufacturing design for the selected chassis. [3] [4]
documentationavailable · Apache-2.0
Software, documentation and robot-description templates; mechanical description is not a complete manufacturing design for the selected chassis. [3] [4]

Selected mapping/navigation platform uses no selected learned policy or training dataset.

References

Each source links to the exact revision we read. “Used for” shows where this page relies on it.

Correction guidance · Discussion is not enabled · Profile format 0.6.0-draft.1

Change history