Being able to adjust the width of pathways so yarbo doesn’t run over and travel the exact sme spot every time.
6 Likes
Thank you for your feedback! We’re aware of the issue caused by Yarbo following the exact same pathway every time and are actively working on ways to improve this behavior.
One option we’re currently exploring is allowing users to create multiple pathways between areas, with Yarbo randomly selecting one for each trip. Would this solution meet your needs, or is adjustable pathway width still something you’d prefer? Your input will help us shape the best approach.
2 Likes
That would probably solve the problem
A suggestion I’ve been thinking about that would fix multiple issues I have is to create a “yard” which encompasses anywhere that yarbo could go and sets boundaries like the geo fence. Then create or better to split the yard into areas or zones to mow that utilized a single boundary line instead of drawing areas with yarbo which creates tiny micro areas with overlaps and undercuts. Then yarbo would not be constrained to the pathways, it would have free range of the entire yard.
Short of mapping the whole yard boundary with the Yarbo I don’t see how this could work technically as it builds the area maps with GPS coordinates and most likely other factors from the other sensors. If the Yard was the geo fence then a lot of people who map their neighbors yards and driveways would have geofence alerts.
It was mentioned on yesterday’s live stream that they want to be able to tightly couple and allow mapping from google maps. This might be more like what you are asking for. I’m sure this is a long way out though as it sounds extremely complicated and will require a lot of testing. It might be more practical to use VSLAM which could build the map and satellite overview automagically. This is what terramow does and it’s pretty neat.