Open Source RoboticsRobots, software & learning

Just1

Robot / hardware build

Raspberry Pi mecanum robot with ROS 2 navigation using lidar and an IMU; its published wheel commands are not measured wheel speeds. [1] [8] [9]

Build & first use →Official websiteBill of materials

For
Builders comfortable with printed parts, Raspberry Pi wiring and ROS 2 setup [1]
Cost
No current cost yet. Upstream bill of materials [6]
Source rights
Some licenses are unresolved. Review licenses
Unknowns
tools not fully established. Review gaps

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

Upstream comparison image of a physical Just1 robot and its design visualization.
Upstream comparison image of a physical Just1 robot and its design visualization. Nicolas Rodriguez and Just1 contributors · MIT. Original image unchanged; displayed responsively. Preview re-encoded for faster display; the link opens the original file.
Licenses & related hardware
License
MIT · license not fully assessed for mechanical design, electronics · Details by part

Requirements · Research details and dates

On this page

Overview

Just1 combines a Raspberry Pi 4, four mecanum wheels and ROS 2 Jazzy for manual driving and indoor autonomous navigation. The preserved design uses an LD19 lidar and MPU6050 IMU with RTAB-Map and Nav2. Camera Module 3 is optional for this lidar-based navigation route. [1] [5] [7]

Is this for you?

Known limitations
  • Upstream reports obstacles below 20 cm are not detected by the mounted lidar
  • Wheel encoders are a future improvement
  • Camera starts in both manual and autonomous launch modes despite being optional hardware
  • No complete current delivered cost or reproduced navigation performance verified

[1] [6] [10]

3D preview

Just1 source assembly. The source STEP assembly, including supplied purchased-component representations. This is a visual reference; exact component revisions, physical fit and a working build have not been verified.

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 STEP (gzip) · 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: Nicolas Rodriguez / Just1 contributors, revision a00abd6e85358cd43f39f26393cbea04c65af20d. Original and preview: MIT. Preview conversion by Open Source Robotics; original file unchanged. Preview coordinates are centered and rounded to six decimal places. STEP preview triangulated in 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
  • Ubuntu Server 24.04

[7]

Host computer

Raspberry Pi 4 and a separate computer running Foxglove for visualization and navigation goals.

[5] [7]

Dependencies
  • ROS 2 Jazzy
  • RTAB-Map, Nav2 and Madgwick IMU filter
  • Foxglove bridge
  • Source-built camera libraries in the documented installation route

[1] [7]

Hardware & parts

Upstream bill of materials [6]

Hardware configuration

Four-wheel mecanum platform with a two-level printed chassis.

[1] [5]

Actuators
  • Four TT motors driving 60 mm mecanum wheels

[6]

Controller

Raspberry Pi 4 with 8 GB RAM; two L298N motor drivers.

[5]

Sensors
  • LD19 lidar
  • MPU6050 IMU
  • Optional Camera Module 3

[5] [6]

Assembly & first use

Project documentation [1]

Assembly

Print the supplied STL parts, use the STEP assembly as a reference and wire the separate Pi and motor power supplies.

[5]

Calibration

Use the supplied diagnostics mode to check wheel direction and movements; verify sensor mounting transforms against the built chassis.

Editorial commissioning sequence; not performed.

[8] [10] · Editorial assessment

Cost

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

Project notes

Build around the documented power and parts choices

The hardware guide selects an 8 GB Pi 4, four TT motors, two L298N drivers and 60 mm mecanum wheels. It separates the Pi's 5 V, 3 A power bank from the six-AA motor battery holder. A rechargeable motor supply is mentioned as a future alternative, not a fully specified replacement configuration. The repository includes a STEP assembly, printable STL components and wiring diagrams, but their presence is not a fit or electrical test. [4] [5] [6]

The $250 headline comes from a March 2025 US parts table. That table assumes access to free chassis printing and lists screws, wires, spacers and a switch separately. A builder should price the chosen camera, printing, accessories, batteries and delivery before treating it as a complete budget. No current delivered build total was verified here. [6]

Follow the selected software route

The setup guide targets Ubuntu Server 24.04 and ROS 2 Jazzy, with RTAB-Map, Nav2, the Madgwick filter and Foxglove bridge. Its camera setup builds libcamera and libcamera-apps from source. Those clone instructions do not pin dependency revisions, so preserving this project commit alone does not preserve the complete installation. No installation commands were run in this review. [2] [7]

The launch file provides manual, diagnostics and autonomous modes. In autonomous mode, Foxglove is used to inspect the map and publish navigation goals. There is an important optional-camera detail: the hardware guide calls the camera optional, but the launch file starts the camera node in both manual and autonomous modes. Omitting the camera therefore calls for checking and adapting that launch configuration; this review does not claim a tested camera-free setup. [5] [7] [10]

Read wheel commands and odometry differently

The autonomous motor controller converts velocity commands into wheel RPM using fixed wheel radius and chassis dimensions, then converts those RPM values to bounded motor percentages. Its wheel_speeds message contains calculated RPM commands, not encoder feedback. Adding wheel encoders is still listed as a future improvement in the overview. [1] [9]

The node documentation describes lidar scan matching and IMU data as the input to ICP odometry. Consequently, a wheel command does not demonstrate that the robot actually moved at that speed. The provided diagnostics mode can help a builder check individual wheels and movements, while sensor transforms must match the physical installation. This commissioning sequence is an editorial recommendation, not a test performed here. [8] [9] [10]

Upstream reports that the lidar placement misses obstacles below 20 cm. It also reports high CPU utilization during navigation, with RTAB-Map, Nav2 and the camera contributing load. Those observations are useful constraints for an indoor experiment, but this review does not establish collision avoidance reliability, achieved speed or available computing margin. [1] [7]

What the source release covers

The root license is MIT for software and associated documentation. Third-party driver code and dependencies retain their own terms. The archive includes STEP, STL and wiring artifacts, but this review did not establish a separate hardware-design grant or complete source for the purchased electronics. No printed assembly, power system, calibration or navigation test was performed. [3] [4] [5]

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
Nov 9, 2025 [2]
Latest release
Not established
Profile updated
Oct 25, 2026
Sources last checked
Oct 1, 2026
Next review
Oct 31, 2026
Reviewed revision
a00abd6e85358cd43f39f26393cbea04c65af20d (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 · License not fully assessed
STEP assembly and printable STL files present; no separate explicit hardware-design license established. [4] [5]
electronicsavailable · License not fully assessed
Wiring diagrams and editable Excalidraw file present; purchased electronics source not established. [4] [5]
firmwarenot found · License not fully assessed
No complete firmware source for the purchased lidar, Pi or other electronics established in this archive. [4]
softwareavailable · MIT
Root software license; vendored lidar driver and external dependencies retain their own notices and terms. [3] [4]
documentationavailable · MIT
Root license covers associated documentation; linked external materials separate. [3] [4]

Selected lidar/IMU navigation route does not use a downloaded learned policy or training dataset.

References

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

Project sources

Videos

  • S011 Just1 (YouTube video)
    Video uploaded by Nico, linked from the project’s own documentation. Not reviewed by us for accuracy.
    Revision, date & where cited

    YouTube video Nico · youtube.com · Accessed Oct 4, 2026

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

Change history

2026-10-04 — Added 1 YouTube reference(s) (S011): official channel or videos linked from the pinned upstream sources. Existing claims, source-check dates and evidence are unchanged.

2026-10-25 — Added an attributed upstream image with linked reuse terms; technical evidence dates unchanged.