Good Afternoon!
Unless I am missing something, most of the areas I’m trying to mow do not need, nor do I want, any perimeter laps. It would be very useful to have an option for “none” in each area config.
Likewise with no-go zones; not all want to have laps taken around them.
Please add “None” as an option for how many perimeter laps are taken to any area that presently performs perimeter laps.
Likewise, the core’s travel speed when making perimeter laps is unnecessarily slow. Running these perimeters that I do not need almost takes as long as mowing the areas within them.
These two behaviors significantly reduce the amount of acreage that can be mowed in a day. The below map is about a third of the acreage I intend to mow with this unit. I have no use for most perimeters laps around areas, and the navigation around objects is immature enough that I don’t want perimeters around them at this time. Maybe some day, but the object navigation is not useful at this time.
Thank you for your valuable feedback! We fully understand your desire to avoid unnecessary perimeter laps in order to improve mowing efficiency. Based on your input, we’re excited to let you know that we will be adding an option to disable perimeter laps around no-go zones in an upcoming update, so please stay tuned for that!
Additionally, we’ve added your suggestion for a “none” option for perimeter laps around each individual area to our request list, and we will consider this feature for future releases.
Regarding the core’s travel speed during perimeter laps, the default speed is set to 0.3m/s for safety reasons. While we understand that this may feel slow, this setting helps ensure the system operates safely, particularly when navigating around the edges of the mowing area.
We also recognize the importance of improving object navigation efficiency, which has been a common request from many of our users. We are actively working on enhancing this feature and will keep you updated as our tests progress smoothly.
Once again, thank you for your suggestions! We truly value user input and remain committed to improving our products.
This is a good idea. I’d expand on it and say add the option to manually select 0 to X number of laps thereby letting the user determine if they want none, 1, 2, 5, etc…
Followup clarification on “0 perimeter laps” for M1 mowing areas -
Yarbo presently requires the two laps as a way to stay away from the perimeter during the ZigZag portion of a job. I should clarify that the two lap distance does not need to be changed.
When “0 perimeter laps” is selected, Yarbo can maintain that buffer with the perimeter. No change to the zig-zag’s perimeter handling is wanted for this feature; literally do what Yarbo currently does when “2 Laps” is selected, but skip doing the perimeter laps.
It is intended that a section of perimeter, when desired, would be cleaned up with Dead-Ends and such.
I’d thought about that and decided against it as part of this specific request.
I’m not convinced that the navigation is up to that accuracy. One little track-slip and you’re over the line, and that already occurs on occasion with the 2-lane buffer. Since Yarbo’s current policy appears to treat a resulting ripped off antenna as a warranty issue, that’s a risk I’d probably have them avoid, for now.
One day when they are confident that out-of-bounds behavior is fully mitigated, then, sure. I’m totally being selfish, but I personally don’t want this feature held up because of that risk. Their warranty risk with the existing buffer has already been accepted, so build upon that.
For me, running two perimeter laps takes almost as long as mowing its area. The laps reduce the amount I can cut in a day by a significant amount, along edges that are either overlapped, bounded, or will need to be dead-ended or weed-whacked, anyway.
I understand a slower perimeter for safety reasons, but maybe only the outermost perimeter lap needs to be slowed down. It would save a lot of time if even just the inner perimeter lap(s) were at full speed.
