Open Source RoboticsRobots, software & learning

OpenMower

Robot / hardware build

RTK-guided mower conversion ecosystem; this review selects the v2 YardForce route and preserves its separate carrier-board and xCore firmware revisions. [1] [5] [6] [9] [12]

Build & first use →Official website

For
Experienced electronics and robotics developers matching mower, carrier board and firmware variants [1]
Cost
No current cost or bill of materials established yet.
Source rights
Named licenses are documented by part. Includes noncommercial terms. Review licenses
Unknowns
host computer, tools, operating system 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

OpenMower converts a compatible commercial mower into an RTK-guided platform with mapped mowing areas. Its main repository is now an entrypoint to separate electronics, firmware, operating-system, ROS and app repositories. This profile selects the v2 YardForce route; it does not treat one entrypoint archive as the complete robot source. [1] [5] [12]

Is this for you?

Known limitations
  • Entrypoint archive does not contain the recursive ecosystem payload
  • Pinned firmware documents runtime platform selection while architecture page describes compile-time configuration
  • Debug preset enables simulated inputs
  • Quoted shopping estimate excludes mower and RTK base station

[1] [5] [9] [11]

What you need

Dependencies
  • Compatible mower and YardForce carrier board
  • CM4, xCore and matching motor-control hardware
  • RTK correction source and configured GNSS installation
  • Separate ROS, OS, app and nested firmware dependencies

[1] [5] [6] [9] [11]

Hardware & parts

Hardware configuration

Conversion of a compatible wheeled commercial mower; selected v2 YardForce route.

[1] [6] [12]

Controller

xCore STM32H723 with ChibiOS; separate Raspberry Pi Compute Module 4 handles ROS navigation.

[9]

Sensors
  • RTK GNSS positioning
  • IMU and mower-specific inputs; exact installed configuration must be matched

[9] [11]

Assembly & first use

Project documentation [1]

Cost

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

Separate the licenses and the incomplete cost estimate

The entrypoint documentation uses CC BY-NC-SA 4.0. The selected YardForce board declares CC BY 4.0, and the xCore firmware declares GPL version 2. Those declarations apply to different artifacts; they do not establish a single unrestricted license for the complete conversion or every bundled dependency. The ROS, OS and app licenses remain outside this scoped review. [1] [3] [7] [10]

The overview's approximate €700 shopping estimate explicitly excludes the mower and RTK base station. It is not a verified delivered build budget. RTK correction delivery and the physical GNSS installation are additional system dependencies. The catalog has not tested positioning, boundary behavior, protective functions or mowing performance. [1] [11]

3D preview

Preview not available yet. Design-source links are available, but the reviewed record does not establish unambiguous reuse rights for a hosted CAD preview.

Project notes

Preserve the component revisions together

The entrypoint commit is 0e11044fb316e179de029f9cdbf551bdfa171387. Its gitlinks identify the YardForce carrier-board revision 17e06696e046fd63da448bbfbb7e3ee1c5d85f46 and xCore firmware revision d87c8277807c7d239d20d2397642a8337b274c6a; both were separately archived for this review. Other ecosystem repositories and nested dependencies remain separate collection work. [2] [5] [6] [9]

The board repository names Classic 500(B) and SA-series mower compatibility and contains KiCad board and schematic sources. That is a carrier-board package, not complete fabrication CAD for the commercial mower chassis. Physical compatibility, board revision and wiring still require installation-specific verification. The official hardware guide distinguishes v1 and v2 and recommends v2 for new builds; mixing those generations would obscure the applicable architecture. [6] [8] [12]

The firmware documentation has moved beyond the architecture page

The selected firmware runs on an STM32H723 xCore using ChibiOS, with a Raspberry Pi Compute Module 4 running higher-level ROS navigation over Ethernet. Its README describes a unified firmware binary with two-stage runtime identification: EEPROM detection for applicable platforms and a ROS-provided robot variant. It distinguishes YardForce and YardForce-V4, including a different mower ESC for the latter. [9]

The architecture web page instead describes compile-time robot configuration. This discrepancy is recorded rather than silently combining the two procedures. For the pinned firmware, its own README is the relevant documented workflow, but no compilation or device validation was performed here. The exact carrier, firmware, motor controller and runtime selection must be reconciled for an actual build. [9] [11]

Build presets also matter: the README states that Debug enables a simulated input driver, while Release uses optimized output and bootloader reset configuration. A successful debug build would therefore not establish normal physical sensor behavior. The documented build needs an Arm toolchain, CMake, Make and recursive dependencies; network upload requires the xCore bootloader. None of these procedures was executed. [9]

What we checked

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

Not yet established

  • Requirements: operating system, host computer, tools
  • A step-by-step setup summary

Updates

Upstream last updated
Sep 3, 2026 [2]
Latest release
Sep 3, 2026 [2]
Profile updated
Oct 4, 2026
Sources last checked
Oct 1, 2026
Next review
Oct 31, 2026
Reviewed revision
0e11044fb316e179de029f9cdbf551bdfa171387 (release v1.4.0) · 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 designnot found · License not fully assessed
Commercial mower chassis retained; board component models do not establish complete mower fabrication CAD. [1] [8]
electronicsavailable · CC-BY-4.0
Selected YardForce carrier-board design only. Third-party component libraries and other modules require their own rights and compatibility checks. [6] [7] [8]
firmwareavailable · GPL-2.0-only
Selected xCore firmware repository declares GPL version 2; bundled and nested dependencies require separate license review. Not a complete recursively preserved toolchain. [9] [10]
softwarenot found · License not fully assessed
ROS, OS and app repositories are linked by the entrypoint; their complete contents and individual licenses are not established by the selected archives. [1] [5]
documentationavailable · CC-BY-NC-SA-4.0
Entrypoint repository documentation only. This noncommercial license is not applied to separate board, firmware or website content. [1] [3]

Selected conventional RTK mower conversion does not establish a required 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

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

Change history

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