Open Source RoboticsRobots, software & learning

Ardumower

Robot / hardware build

DIY robotic mower reference platform; this review selects the 1.0a10-Azurit release and records its PCB configuration, stored-setting behavior and conflicting license notices. [1] [2] [5] [6] [7]

Build & first use →Official website

For
Experienced robotics developers able to reconcile historical boards, firmware and physical protective functions [1]
Cost
No current cost or bill of materials established yet.
Source rights
Some licenses are unresolved. 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
License
not fully assessed for mechanical design, electronics, firmware, software, documentation · Details by part

Requirements · Research details and dates

On this page

Overview

Ardumower provides Arduino mower code, perimeter-sender code and hardware reference files. This review selects release 1.0a10-Azurit, preserved at commit dd41c1f1ce1e2745c8373a4f112a99ee54322e0f. The README warns against treating the development master branch as a stable download. The selected release is a source reference, not a tested mower assembled by this catalog. [1] [2]

Is this for you?

Known limitations
  • GPLv3-or-later notices coexist with private-use-only restrictions
  • Selected chassis archive is labeled 0.99 while source prerequisites name chassis kit 1.0
  • Factory defaults disable several optional sensor functions
  • No compilation, stored-setting readback or mowing test performed

[1] [5] [6] [7] [8] [9]

What you need

Dependencies
  • Matched Arduino board and PCB revision
  • Configured motor drivers and actual sensors
  • Perimeter sender for a perimeter-based installation
  • Separate chassis, power and charging configuration

[1] [6] [7]

Hardware & parts

Hardware configuration

DIY wheeled lawn-mower reference platform, selected Azurit firmware release.

[1] [2]

Actuators
  • Left and right wheel motors
  • Separate mowing motor
  • Selected compile-time motor driver is MC33926

[6] [7]

Controller

Arduino Mega or Due; selected header enables PCB 1.3 and recommends Due with that board.

[5] [6]

Sensors
  • Selected IMU definition is GY801
  • Configurable odometry, sonar, bumpers, tilt, rain and perimeter inputs; availability is not validation

[6] [7]

Assembly & first use

Project documentation [1]

Calibration

Robot/PCB selection is in mower.h; edited factory defaults require reset through the serial console or ArduRemote/pfodApp according to source comments.

[6] [7]

Cost

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

3D preview

No hosted 3D preview: the upstream license restricts the Ardumower files to private use and requires permission for commercial use, so Open Source Robotics does not host a model or derived preview of them. Ardumower README, License section states: “Private-use only! (you need to ask for a commercial-use)” The README separately offers the code, schematics and PCB files under the GNU General Public License version 3 or later; it gives no other license for the chassis CAD. License: README.md License section in Ardumower/ardumower.

Project notes

The Arduino and PCB selections are linked

The sketch accepts Arduino Mega or Due and rejects other board targets. Its mower.h prerequisites say Due requires PCB 1.3; the preserved header enables PCB 1.3, the full Ardumower robot, MC33926 motor drivers and GY801 IMU. Those are compile-time selections, not proof that a particular physical mower has those components installed. [5] [6]

The hardware archive contains a chassis directory labeled 0.99 with STEP and DXF files, while the source prerequisites refer to chassis kit 1.0 or the Mini. The board archive spans multiple designs and revisions. These version labels must be reconciled before treating the archive as a complete matching fabrication package. No CAD or PCB manufacturing validation was performed. [6] [9]

Source defaults are not the same as active robot settings

The mower constructor warns that changing its factory values requires resetting the robot through the serial console or ArduRemote/pfodApp. Editing a source value alone therefore does not establish the active saved configuration after flashing. This review did not compile, flash or read back a controller. [7]

The inspected defaults disable bumpers, tilt, drop, rain, sonar and perimeter use, while defining other related parameters. Those settings are a concrete reason to audit the actual installation rather than assuming that the existence of sensor code means every protective or boundary function is enabled and tested. No motion, blade operation or protective-function test was conducted here. [7]

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
Mar 19, 2021 [2]
Latest release
Mar 19, 2021 [2]
Profile updated
Oct 1, 2026
Sources last checked
Oct 1, 2026
Next review
Oct 31, 2026
Reviewed revision
dd41c1f1ce1e2745c8373a4f112a99ee54322e0f (release 1.0a10-Azurit) · 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
Source artifacts available, but private-use-only language conflicts with GPLv3-or-later statements. No unqualified layer license assigned; exact file rights and configuration completeness require resolution. [1] [5] [8] [9]
electronicsavailable · License not fully assessed
Source artifacts available, but private-use-only language conflicts with GPLv3-or-later statements. No unqualified layer license assigned; exact file rights and configuration completeness require resolution. [1] [5] [8] [9]
firmwareavailable · License not fully assessed
Source artifacts available, but private-use-only language conflicts with GPLv3-or-later statements. No unqualified layer license assigned; exact file rights and configuration completeness require resolution. [1] [5] [8] [9]
softwareavailable · License not fully assessed
Source artifacts available, but private-use-only language conflicts with GPLv3-or-later statements. No unqualified layer license assigned; exact file rights and configuration completeness require resolution. [1] [5] [8] [9]
documentationavailable · License not fully assessed
Source artifacts available, but private-use-only language conflicts with GPLv3-or-later statements. No unqualified layer license assigned; exact file rights and configuration completeness require resolution. [1] [5] [8] [9]

Selected conventional mower controller profile does not require a learned policy or training dataset.

Licensing needs resolution before an unrestricted reuse claim

The README and main sketch state GPL version 3 or later, but also repeat a private-use-only restriction requiring permission for commercial use. The separate PCB notice contains the same combination. This profile records that conflict and leaves the normalized license unresolved; it does not describe the entire package as unconditionally GPL-licensed hardware and software. [1] [5] [8]

The preserved files remain useful for source research and configuration comparison. A complete build still needs matched chassis and board revisions, a delivered parts budget, current sourcing and validated firmware/settings. None of those gaps is resolved merely by downloading the release. No physical build, installation or mowing trial was performed. [6] [7] [9]

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