Why would it do a, dance and then a bunch of tank turns and then go backwards through this pathway to get from one area to the next? Is it because of the overlap of areas?
Why can’t it just transition between overlapped areas even without a pathway? Or be able to mark overlapped areas as allowed to consider them a contiguous crossing zones?
There are a few places I prefer it go to a specific area to cross to get better GPS quality first but I definitely don’t want missed swipes.
Would making that pathway longer help? I also need to re-optimize my dock pathways…
Pathways should extend into areas (non overlapping ones) by at least 3.3ft as a good rule. Ending or starting in an overlap can cause issues. There is also a weird bug with the leaf blower that I’ve seen reported and basically is what you described. Assume this was the leaf blower?
I agree that pathways between overlapping areas seems unnecessary.
At least for the M1, you CAN have pathways across overlaps even span multiple areas, but ensure that the head and tail of such pathways extend well into single, distinct areas.
Yes, the areas in the middle will use the pathways without issue.
Currently, Yarbo does not support traveling directly through overlapped zones when moving between areas. As some others mentioned, extending both ends of the pathway at least 3.3 feet (about 1 meter) into each area can help reduce the unusual turning or “dancing” behaviors.
Once you make those adjustments, please let us know how it goes — we’re interested in your results. And feel free to reach out if you have any other questions!
