Want Yarbo to keep a safe distance from sensitive edges and obstacles? 
Learn to adjust your Buffer settings.
Higher value = farther from the mapped boundary.
Lower value = closer to the mapped boundary.
Check out the tips and learn more in the Yarbo Wiki! 
@cobradunn This one has your name written all over it, lol. How do no go zones work? 
submit a support ticket with the times
Ticket submitted also my wife notified me it broke the track cover. Must have gotten caught on the smaller tree in the nogo zone :/.
Definitely let them know and send pictures of that as well.
Where’s the part where it sticks entire head or ass inside to take a look around?
I got the usual
Yarbo navigates using RTK GPS for centimeter-level accuracy. When the RTK signal is temporarily blocked or weakened (by trees, eaves, buildings, or large metal objects), the system switches to a dead-reckoning (DR) mode that estimates its position from the IMU and wheel encoders. The longer it travels without a solid RTK fix, the more the estimated position can drift — and if the drift accumulates, Yarbo can cross into a No-Go Zone even though it “thinks” it is still inside the allowed area. A strong, stable RTK signal is therefore the key to staying inside the boundary and out of No-Go Zones.
To help Yarbo keep a reliable RTK fix:
• Keep the Data Center and the mower in an open area with a clear view of the sky (avoid eaves, dense tree canopies, and large metal objects nearby — they reflect GPS signals).
• Make sure both RTK antennas are properly mounted and not damaged, bent, or blocked.
• On the Diagnose page, RTK status should be 4 (fixed) and L2 satellites > 10 while working; if not, the positioning is degraded and unexpected boundary/No-Go crossings are more likely.
As always my property is completely clear 22 acres from the house is the closest tree. Except for small fruit trees that the Yarbo backed up to too It has nothing to do with the Data center the plan is generated even before the Yarbor goes out to cut. But I will look in To all the recommendations they have requested. Here to support future advancements into this product. It’s a great tool.
Reply to your ticket and point out that the PLANNED path was through a NGZ and it has nothing to do with weak GPS or PPVS. Ask them to escalate it to R&D.
Thanks, Brian I will. It’s already 11 o’clock at night here in in Poland I am going to bed Lol I have to wait for my wife to take a picture of the damage to the track cover. Then I will get it sent out in The morning. I have been I the habit of checking the generated plans just to make sure no issue after hot fixes. But this one got past me. I did not have an issue three days ago when I ran the same plan with no issues.
If nothing else has changed (like firmware), take a look at the offset or rotation settings. They might be a factor. Maybe something you can temporarily disable if so.
Hi there, first of all, I’m really sorry for the inconvenience caused, and I also apologize for the initial response you received.
As Bryan mentioned, a weak GPS signal should not be the cause of this particular issue. I’ve helped escalate your case to our FSE team for further investigation.
