I’m having consistent issues with Yarbo mowing too far from the perimeter. I map counterclockwise with right edge of mower of metal edging of my landscaping beds (right up against edge). When I mow, I set perimeter to 4” (default) and am trying 0”. I routinely get a gap of 6-8”. What are ways to fix this? I have entirely clear skies where I’m at with minimal to no GPS blockage.
Hi there, you can try setting the reduce boundary to 0. Please note that even with this setting, Yarbo will still leave about a 10 cm (approx. 4”) uncut buffer by default. This safety buffer is currently in place to ensure stable and safe operation.
We understand this can be inconvenient, and we’ve already shared your feedback with our product team. Once positioning accuracy is further improved, we will work on optimizing this behavior. We truly appreciate your patience and understanding!
2 Likes
IMHO I think the current 4” safety buffer is unnecessary and easily fixed.
The quickest fix would be to add a warning to the reduce boundary setting that when you go below 4” you are warned that Yarbo may make contact with items at the border.
Much like the warning you get when you mow below 2.7”
This transfers the “risk” to the owner.
It would be great if that simple fix was in the next software release. That would help eliminate part of my weed whacking time. And that would be a very welcome thing.
5 Likes
I don’t want to pollute all the threads about this but it seems that Yarbo makes several decisions based on “safety” that are not really safety of humans, but safety of the robot… They should, as you said Ken, enable the customers to make their own informed decision… Like for zero-turn maybe? They mention safety for some zero-turn situations…
4 Likes
That’s probably the tricky part. Getting enough information to make an informed decision.
It’s easy to say “no zero turns” it’s a lot harder to say what Yarbo will do at a given corner at any given mow angle.
But if a user checks the “no zero turns” button and then Yarbo eats up your flowers…. that’s on the user in my book.
1 Like
If you send an autonomous 300 pounds robot with sketchy RTK capabilities 800 meters from your home, out of direct sight while travelling abroad, everything is on the user… in my book…
2 Likes
I get that it would make zero turns in limited instances of confined corners, at borders and similar, but it makes them all over the place where they’re not required. The ones that bother me the most are the pathway and DE ones where it’s inside an Area with nothing around. They apply the same logic regardless of the situation. My bet is that was just easier to code than analyzing multiple conditions to determine if zero turn is actually required.
4 Likes
Pathways are to me by far the most problematic as they are required several times per day at the same spot… I try to put them on hard areas but not always possible…
DE also problematic, but since I mow less often in DE, it creates less damages… But I concur…
2 Likes
Like the totally unnecessary zero turns in front of the dock. I can’t understand why they are ok with that lawn destroying behavior.
In my case, I count TWO zero turns to get into the dock. When in reality, none are needed.
4 Likes
If we can still control an object that’s 15.5 billion miles away from earth with 1970’s technology we should be able to control a robot in our backyard in 2025. 
4 Likes
Oh yes! That one for sure! I’m so accustomed to the round bare spot, it slipped my mind 
I’m lucky to have my dock in location hidden from view so no one else gets to see the stupid.
3 Likes
Yea, even with 0” boundary setback, I’m still left with minimum 4” perimeter long clippings. More realistically it’s 6”-8” perimeter of long clippings.
1 Like
4” is correct and unfortunately the current state of things.
1 Like
100% agree with this, warn but let me do it.
More frustrating is that they changed this and it used to be able to go to 0… I had everything set up to work that way and then they changed it.
I think I did see somewhere that it was temporary so maybe the next firmware version we will get it back.
4 Likes
I’m hoping so.
I agree if i map it to where i want it.. it should go to where i mapped.. fine create a buffer but allow us to control the inward of the overall area. so if we want to go into the negative to compensate for this let us. we use it all the time and find things you never thought of before. mapping is my biggest hurdle and issue.. mapping needs work to allow the user to make changes like straight lines if while mapping a 500 foot run make 1 wrong bump and now i have to remap the entire thing. I know you can modify but that is horrible to use. no accuracy and guidelines to go by meaning when i go to the area i want to change I have to somehow get yarbo exactly on that little line then drive it to connect at the other end .. very hard to do. the icon is so big and no guides are given to align it up. same goes for no-go zones. where do you place the robot at to start them where does the line start the mower front center?, the yarbo center or left or right side? i dont know..
4 Likes
pathways also.. if i put in like 3 connecting one area should it now choose the closest one ? maybe it is doing a job in the front then the side which i have three paths to choose from. but it always uses the same one everytime.. it should be smart enough to choose the closest one and use that. this way we are not creating ruts on one are. Also the turn around at the base.. what.. it destroys the lawn.. just drive in backward and park. dont go forward turn backward turn forward turn then spin around then go in.. just get close do a random turn to back in.. done..
5 Likes
The other reason to be able to widen a perimeter is that there are many kinds of perimeters. The perimeter could be along side a ditch, alongside a flat property line, or alongside a wooden fence. In some cases a buffer is needed and in other cases a buffer is ridiculous. I also sort of think that the NGZ should dictate the boundary, so having a NGZ and a buffer is redundant. But letting us choose would be best, and I’m guessing fairly easy to implement.
2 Likes
Thank you for sharing your thoughts on the mapping experience. We do have plans to optimize the entire mapping process, and I’ll make sure to pass your feedback along to our product team. For clarification, Yarbo uses the central point of the Yarbo core as its reference when mapping.
2 Likes