We are having a “gathering” here on the farm for anyone interested in learning/building autonomous Mowers/Rovers/Boats/Drones, etc. The main goals being to meet, compared ideas/best practices and share experiences with putting these things together.
We should have at least 5 working mower examples on hand and everyone is encouraged to bring their own. We have ~100 acres of short hay fields to play with so room to roam is not an issue. Will also have our on-site RTK (via NTRIP) active and available for use.
Church Point is a small town about 20 miles NW of Lafayette, LA with no motels. However, Lafayette is a large metropolitan area about 30 minutes away with many motels and a large, full service airport served by American, Delta and United. RV’s are welcome but please call for details.
If attending, please contact so we can plan accordingly!
Location Address – 1529 Beaugh St, Church Point, LA 70525
Contact: Steve Webre – 337-349-8365 or “email@example.com”
I’m looking forward to playing with Scurves. I have my Version 2 mower ready to roll out of the shop, likely tomorrow. I have the latest beta on it, but if I don’t get relatively straight lines pretty quickly, I’ll shift back to NAV L1 to get some work done and save the playing for Mowstock.
I’ll be bringing my Hogbot (built by Yuri), my mower (built by Steve, Bill, Yuri, and me), my drone, maybe a new RC plane still in the box, and maybe a surprise.
I just wanted the express my appreciation to Steve Webre @Swebre for hosting this great event and I wanted to thank @ktrussell and all the others that helped me to learn more about the mowers and the details of using the Ardupilot software. It was also a great opportunity to meet the real people behind the names and faces we see on the internet.
Here is some information on a few parts that a few people ask about on my mower.
Here is the little sealed more industrial DC-DC converter that was ask about.
MowStock was great event!
Thanks again to Steve Webre and Mel
Want to “Thank” all involved in MowStock gathering!
Several folks drove a long way and in the end, we had 6 functioning autonomous mowers show up. So for the moment we claimed we had the “Worlds Largest Gathering of DIY Autonomous Mowers”! (Lots of laughs ensued.)
I think we all learned a new thing or two and generally had a great time. The most interesting part for me, besides meeting folks face-to-face, was seeing and discussing the different logical and mechanical approaches we took to the same problems.
Looking forward to the next time we can gather up. Onward!
@ktrussell@Yuri_Rage and others: Recent video with 2 mowers working (for some reason it seems the default viewing resolution is low, and that one must manually select high resolution replay when viewing these videos from google photos):
I do occasionally lose RTK, and it seems that it happens more under heavier tree cover… and I also have a hypothesis that it happens more when the trees are wet. When the GPS fix level is 4 or less, I pause, and wait, and resume when GPS level is 5 or 6 again. (This logic is implemented in my companion computer, not on the autopilot). I estimate this happens every 10-20 minutes in the most heavily wooded parts of my lawn. Usually the GPS drops to 4 for <5 secs so not a major factor. About once every 10 hours I have a pause that’s more than 5 seconds. I’m sure I will learn more about this as I mow at more properties this season.
Do you know if there’s a difference between GPS fix level 5 and level 6? Right now I’m mowing with either 5 or 6 because I think they both indicate an acceptable level of precision. But I actually don’t know this for certain.
Then of course, before beginning a mission, we visually scan the yard to ensure there are no new obstacles. Which works pretty well but not perfectly. Yesterday a mower met up with this yard waste bin.
GPS level 5 is RTK Float. Level 6 is RTK Fix. I have found that float is pretty bad. I stop if RTK drops below 6. @Yuri_Rage wrote a Lua script that does that. It can easily be tweaked to do what you are doing with your companion computer. A couple of years ago, a companion computer would have been required to do it, but the Lua scripting has enabled a lot of functionality right in the FC.
Thanks for the white paper reference. I am using the built-in Bendy Ruler OA with exclusion fences around trees. Unfortunately, the way it is implemented leaves a triangle after the obstacle. I have to manually insert some waypoints to fix that. It has worked well for me with that modification, however.
@ktrussell@Yuri_Rage I have been experimenting with the horizontal accuracy reported by the GPS (h_acc in the mavlink message). It seems it may be a finer-grained accuracy indicator than the GPS fix type. The lowest value for h_acc (i.e. most accurate) I see is 14mm. When mowing in the open, it generally varies between 14 and 18mm. Then under heavy trees it can increase up to 50 or 60 mm. What do you think about using the horizontal accuracy (rather than the gps fix type) as the basis for stopping mowing when GPS accuracy falls?