When Yarbo navigates from point A to B (starting a mowing job, moving between areas, etc.), Yarbo’s navigation puts it on a path that is too close to boundaries of areas and no go zones. As Yarbo reaches these points in the path, it has to stop, adjust, maneuver, sometimes seemingly getting confused as it tries to work around a boundary corner.
When Yarbo maps a path for navigation, if it just gave the unit a bit more buffer on either side, Yarbo would be able to seamlessly move between points.
In the image, the green circle is where Yarbo is, the green arrow is where Yarbo needs to go. The two red arrows are boundary corners where Yarbo has to stop and dance around because it gets too close. Note, this is not an obstacle avoidance scenario. Yarbo is just getting too close to the boundary and it halts, then tries to work through the problem. This particular use case was mid-job.
I have a support ticket in progress, but wanted to see if anyone else has this issue or if Yarbo has any insight on the issue. Thanks!
it happens in the current firmware from time to time. Overall hugging the perimeter is just a recipe for problems. I think it should stick to the 2nd perimeter line instead of hugging the boundary line. I mean it already cuts across an area for no good reason, why not just let it do that in general if it’s not going to follow already cut path lines in order to avoid disturbing the nice cut line look.
Thank you for bringing this to our attention, and we apologize for any misunderstanding in your support ticket. We understand that you’re requesting an improvement in route planning, particularly in situations where Yarbo gets too close to boundaries or no-go zones.
We’ve shared your case and feedback with our product team, and they’ve already taken such scenarios into consideration. An optimization is planned for the next version, which will include maintaining at least a 30 cm buffer when planning routes to help avoid these types of issues.
We hope this upcoming update will help resolve the problem and improve your overall experience.
Thank you for reporting this, @jeremyj114. I was collecting evidence, but you beat me to it – good.
In this example the lines Yarbo draws to get from point to point within an Area to start mowing another section can be drawn across border corners. It did hit the fence that’s there, even though it’s outside the border.
I have seen mowing lines drawn within the boundary of a No-go Zone. When Yarbo traverses an Area to a starting point, I have had a line drawn right though a No-go Zone, and I think it did a Gentle Touch of what’s there (not sure on that – the rover did seem startled anyway).
Wow, glad I posted this in the forums. Based on the responses I was getting in my support ticket, I was beginning to think I was doing something wrong.
No you are right, I have the same problem as you. I even had a support “teams call” about that issue and they took note of the problem. Yarbo crosses the boundaries in the green marked areas, problem, there is a metal fence it runs into, sometimes it stops and waits for manual resume.
It goes up, across the whole hill, to the blue marked area, does 2 turns and then goes back down to mow the remaining 3%. It needs to get more efficient in planning, like a little leeway in overlap, or do do some stripes twice to avoid going up and down the hill to do 3m².
I think the problem got worse when they started to include the cameras.
I have a lot of problems with growing plants alongside my boundries that throw yarbo off it’s way.
