v1.2.0 brings per-area configuration overrides, a batch of v2 hardware improvements, and a handful of reliability fixes. Area Overrides for Various Settings The move from map.bag to map.json in v1.1.0 opened the door to flexible, backwards-compatible map extensions. The first major use of that flexibility lands here: individual mowing areas can now carry their own values for outline_count ,…
The docs at openmower.de just got a complete visual overhaul — and alongside it, we’re publishing the first official OpenMower brand system . What Changed on the Site The site now runs a fully custom theme built directly on OpenMower design tokens: self-hosted DM Sans and DM Mono fonts, a cohesive green-on-dark colour palette, and a homepage that leads with what the project actually is — a…
Community member @rovo89 has been quietly building something great: the OpenMower App , a completely new application for your OpenMower mower. You can find it here: github.com/xtech/openmower-app What’s in it right now At this stage, the app ships with a map editor and some debug information. The map editor is the part we wanted to get into people’s hands first — it’s the most…
v1.1.1 is a focused patch on top of v1.1.0. What’s New Skip inactive mowing areas — The mower now correctly skips areas that have been marked as inactive, so you don’t need to delete and re-record areas you only want to temporarily disable. Thanks @rovo89 . Publish parameters to MQTT — Mower configuration parameters are now published to MQTT, making it easier to observe and integrate…
Firmware v0.0.3 is out. This release is a big step forward for SABO / John Deere users and brings a handful of robustness improvements that benefit all platforms. SABO / John Deere Support Most of the work in this release went into maturing SABO support, driven almost entirely by @Apehaenger — huge thanks! The SABO carrier board can now be considered properly supported: BMS integration — The…
v1.1.0 is a substantial release with a breaking map format change, a long-standing planner bug fix, and a wide range of new features. Map Format Changed to JSON The map is now stored as map.json instead of map.bag . On first boot after upgrading, your existing map.bag will be automatically converted — no manual action required. From that point on only map.json is read and updated. The MQTT map…
v1.1.1-beta is a hardware revision fixing a critical EEPROM power issue and switching the inter-module connectors. Changes EEPROM 3.3V fix — The 3.3V supply for the EEPROM was not connected in the previous revision. This is now routed correctly, fixing #6 . Without this fix the core board cannot read the carrier board’s EEPROM and therefore cannot auto-detect the attached mower model. XH…
v1.1.0-beta brings a handful of hardware improvements to the YardForce v2 carrier board. Changes Fan voltage selector — A voltage selector has been added for the fan connectors, allowing the fan supply voltage to be configured. Fan connector silkscreen labels have been added to match. The third FAN connector has been removed and the silkscreen documentation updated accordingly, resolving #3 .…
v1.0.2 is a large feature release with contributions from across the community. Highlights GPS via TCP — The GPS driver can now connect to a GPS source over TCP, making it easier to use network-attached GPS receivers and relay setups. Thanks @rovo89 . Rain detection — The mower now implements rain logic: when rain is detected it stops mowing and waits for the configurable OM_RAIN_DELAY_MINUTES…
It’s been a while since the last proper OpenMower update — three years, in fact. Back then, the project was barely more than a prototype. No kits, no polished user experience — just some soldered PCBs and command-line interactions. Fast-forward to today, and OpenMower has matured in a big way. How Far We’ve Come When the project started, users had to build their mowers from scratch,…
Three beta releases shipped in quick succession in October 2024, establishing the initial hardware design for the Universal carrier board. v1.0.0-beta — 2024-10-19 The first public release of the Universal carrier board design. The Universal board is designed to work with a wide range of robot mower platforms and can be broken apart into separate modules if the full board doesn’t fit a given…
The YardForce v2 carrier board is the reference design for the OpenMower v2 hardware platform. It connects the universal xCore board to the YardForce mower’s motors, charging circuit, and sensors, and shares the same SODIMM form factor as the original board with the same connectors. v1.0.0-beta — 2024-10-07 First public release of the YardForce v2 carrier board design. v1.0.1-beta —…
Three edge pre-releases shipped between v1.0.0 and v1.0.2. Here’s a summary of what landed in each. v1.0.1-edge.2 — 2024-07-24 Docking retry on roll-off — The mower now retries docking if it rolls off the charger instead of giving up. Thanks @jeremysalwen . NTRIP IP ban fix — Fixed an issue where the NTRIP client could get your IP banned from public casters. Thanks @EtheriVR . Configurable…