About the Project
IF YOU ARE NOT 100% SURE WHAT YOU ARE DOING, PLEASE DON'T TRY THIS AT HOME! ASK IN DISCORD, IF YOU HAVE ANY QUESTIONS!
Project Intro Video
If you want to see a quick overview, you can check out this video:
Let's be honest: The current generation of robotic lawn mowers sucks. Basically all of these bots drive in a random direction until they hit the border of the lawn, rotate for a randomized duration and repeat. I think we can do better!
Therefore, we have disassembled the cheapest off-the-shelf robotic mower we could find (YardForce Classic 500) and were surprised that the hardware itself is actually quite decent:
- Geared sensored brushless motors for the wheels
- A sensored brushless motor for the mower motor itself
- The whole construction seems robust, waterproof and all in all thought through
- All components are connected using standard connectors, therefore upgrading the hardware is easily possible.
The bottom line is: The bot itself is surprisingly high quality and doesn't need to be changed at all. We just need some better software in there.
Here is a quick overview of this project's goals:
The basic mowing function finally works! As you can see in the video, map teaching and mowing work as expected. It even returns to the docking station automatically as soon as the battery gets low and continues once it's recharged.
At this point I can recommend that brave tech savvy users can build one for themselves! Since it's quite an expensive and complex project, please don't be shy and ask if you have any questions. I'm glad to help
The first mainboard PCB is almost done. It currently looks like this:
- Low Level Firmware Implementation
- Voltage / Current Sense
- Emergency Stop Button tracking
- IMU Communication
- Rain Sensor
- Charging State
- Sound Module
- UI Board Communication
- Low Power Mode
- ROS Hardware Interface
- Hardware Redesign (bugs / enhancements):
- Digial Emergency Stop Signal from Pico to xESC
- Sound Module Pinout needs to be adapted to DFPlayer
- XT60 Power Connector needs to be connected to main power instead of charging input
The basic software is basically done; Our prototype works as intended (but is not able to avoid obstacles yet).
The software for the robot can be found in a separate repository: https://github.com/ClemensElflein/open_mower_ros
- Mowing State Machine (Docking / Mowing, ...)
- Path Planning
- Obstacle Avoidance
- App / Visualization
How You Can Help
You can help by starting an OpenMower build of your own. This helps to validate the concept and helps to create useful documentation for new users.
Additionally, you can help by starring
Compatible Robotic Mowers
While disassembling the bot, I wondered about its mainboard: Instead of "YardForce" it read "GForce". After checking the internet for "GForce" robots, I found that that very similar looking robotic mowers are sold under the Herkules brand. Naturally I tried to dig deeper and actually found evidence that the mainboard is manufactured by some chinese company (SUMTEC Hardware).
It is therefore quite safe to assume that many robot mowers are basically the same device in a different case. This would be a huge win for the community, since this would mean that by making one of those robots smarter, we could upgrade A LOT OF ROBOTS!
Therefore it might be a good idea to start a list of compatible devices. So if you have a cheap robotic lawn mower, it would be nice of you to check, if it contains the same mainboard as ours and send me some pictures / model numbers.
This page only contains the basic overview of the project. To follow my current development state, check out my Blog.
Patents, Local Laws, Liability
Before building a robot based on the designs published here, please make sure that you are allowed to do so in your specific regions. There may be patents and / or laws prohibiting you of doing so.
The code/schematics/PCB files are distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
This basically means: I'm just documenting a project of mine here for free and I don't have the time and resources to check that devices built using this information will be safe to use, legal to use or even work as intended. You will need technical know-how to use this project and I'm not liable for any damages your devices do to anyone or anything.
This work is licensed under a Creative Commons Attribution-NonCommercial-ShareAlike 4.0 International License.
Feel free to use the design in your private/educational projects, but don't try to sell the design or products based on it without getting my consent first. The idea here is to share knowledge, not to enable others to simply sell my work. Thank you for understanding.