The No-Go Zone refers to enclosed areas within Yarbo’s working area where you do not want it to enter. While Yarbo’s stereo depth perception allows it to recognize and avoid many obstacles automatically, certain areas still require manual no-go zones to ensure optimal performance and safe operation.
Key Areas to Draw No-Go Zones
Swimming Pools and Water Features
Yarbo cannot operate in or near water, and entering these areas could result in damage.
Recommendation: Set a no-go zone around pools, fountains, and ponds to prevent accidents.
Flowerbeds and Gardens
While Yarbo can navigate under trees and detect common obstacles, delicate plants or garden beds may need extra protection.
Recommendation: Draw no-go zones around flowerbeds, vegetable patches, and newly planted areas.
Restricted Areas
Prevent Yarbo from entering spaces you want to keep off-limits, such as pet zones, tool storage areas, or seasonal setups.
Recommendation: Use no-go zones to block off restricted spaces, especially if the objects are temporary.
Large Fixed Obstacles
Yarbo can avoid trees and shrubs automatically, but large or complex obstacles, such as parked vehicles, furniture, or heavy equipment, may require manual restriction.
Recommendation: Set no-go zones around parked cars, playground equipment, or seasonal decorations to avoid interference.
Areas Where No-Go Zones Are Not Necessary
Trees and Bushes: Yarbo automatically detects these obstacles and marks them on the map.
Navigating under trees: With visual fusion navigation and odometry (ODOM), Yarbo stays on track without manual no-go zones.
Is there a maximum number of No-Go Zones @Yarbo-Forum? Also you mention that we do not need to mark trees as No-Go zones, but if we identify them as No-Go, will it be faster for Yarbo to mow? Especially if we have several dozens (110 in my case) threes? Or will it make things worse?
If you select mow around NGZ’s then it can make the mow time a little slower possibly. But probably not as slow as letting obstacle avoidance figure out how to navigate around 100+ objects.
And no there is no limit that I’m aware of. Seen many maps with just as many or more. But it could impact the calculation time. @Ken will tell you about this with his complex maps
Ok. I am at 41 NGZ mapped. I’ll try an hybrid solution for now and let it figure out the rest. I’ll also try to mow with the NGZ around the trees active or not and report back what is the most efficient (unless someone has a definitive answer about how the algo works to plan the paths!).
Be curious to hear your results. In theory it should be faster. But it’s going to ping pong on the perimeter and NGZ cuts quite a bit. Might eat into your battery life. That may be the only negative (well and all the extra path lines). If you care about the look, maybe do the zig zag last.
I don’t think complexity comes from many No-go Zones. I think it comes from the Area sandwiches, many paths, tons of Deadends, the Sidewalks that are still there for the snowblower but hidden for now, …
You bring up a good point of what will take longer – mowing with many mapped No-go Zones or letting Gentle Contact handle it. I like the hybrid solution, @Micke, so you can do a little testing on that and can let us know.
Will take a few days before I have results to report on. I made a rookie “mistake” and I have one main big area. So as long as we cannot split it without having to choose one of the areas after the split, I’ll have to wait for the whole job to finish. I will report back for sure!
I’m looking at the thing right now and it seems to handle the trees better (just a feeling for now). But it takes 3-4 minutes before the job starts (much longer than without NGZ).
By the way, I feel like I am getting addicted at watching the thing do its job. Am I alone? haha
You can create a big No-go Zone over half your Big Area using a Template, and that will allow you to have just one half mowed. You can then do the same for the other half. That way you don’t have to modify or delete the Big Area.
It sounds like you are driving the rover around your trees to create the No-go Zones. Yes? No? I typically park the rover next to the tree and create a Circle Template No-go Zone relative in location and size to the rover, leaving a bit of a size buffer. After a mow I can see what grass wasn’t cut, and I can create another Template No-go Zone and size and locate it relative to the No-go Zone that’s there, then delete the first No-go Zone. It may take a time or two to dial it in, though, but you don’t need the rover to do it after the first time.
Also you can look into using Deadends to get close to something to mow it – Deadends follow the same path every time (mostly) and ignore No-go Zones.
Oh! Clever! Also just found a post on Facebook about it. Not perfect but will do the job for now. Now we need to be able to add this to the scheduler! But I wont add it in the feature request, they need to fix some more urgent stuff first… Although I am enthusiastic about the machine after a few days, there are a few more things that need to be fixed ASAP… I’ve had a Husqvarna 450X and Landroid Worx that have some functions for years that Yarbo doesnt…
I’m working on a 10 step process to break the addition. Rolling the Yarbo over and crushing the RTK antennas pretty much stops the watching it work for awhile. Ask me how I know.
Thanks for your question. In your case, there’s no problem with mapping all the No-Go Zones. Mapping all the No-Go Zones can help Yarbo navigate around these trees more accurately and reduce the chances of it running into them.
And yes, as Bryan has suggested, mapping all the No-Go Zones in advance should make the work plan process faster.
Ok so now I am ready to report about my tests. Yarbo is doing much much better when using smart vision with no NGZ around each tree. The issue is that with that many trees in a zone it 1) takes a long time to compute; 2) it creates redundant/repetitive patterns when the NGZ are very close that can damage the lawn; 3) you can not mow along NGZ when you have say 100 NGZ some of which are very close (the map becomes a big mess).
So for areas with a lot of trees (orchard in my case), smartvision is the best. It will miss some areas but if you rotate on next mow it will catch it. If you mow regularly you won’t notice. Best keep NGZ for things not seen by smart vision, or ditches, water area, flowers, etc…
Off note, look at the picture. A lot of trees. No GPS issues (I do see HDOP increase sometimes but it is able to recover on time).
On the picture of the map you’ll see a few NGZ around trees because I removed NGZ step by step and this is the only screenshot I have. Now the lawn looks even better and I removed all NGZ around trees.
Advice, when mowing at night, expect a few ghosts (Yarbo sees things that don’t exist). Way better during the day. Since I mow often I don’t care and I don’t see it on the lawn but if you mow less often, Insuggest mowing with good lighting if using smart vision.
But it may be because the leaves are going quite low… this is my only tree below 2 inches.
I find the navigation around the trees quite good in fact. It is not as tight as I could do with a mower, but mowing regularly around that many trees is nearly impossible. Now it looks clean and I can do some edge cuts around the trees when it becomes too obvious. Had to do it anyway with a mower so no difference.
Now, I need to find a way to solve the track issues along the paths Yarbo takes to navigate between zones… Anyone found a workaround while waiting for an update that adds some variations? With my husqvarna I had the capacity to de use the with of the corridor (between 1 and 10 feet)….
Thanks for the follow up! Yeah vision and trees seem to work very well. I agree, sometimes it does see some ghosts at night, but sometimes I wonder if that’s bugs landing on the cameras because of the lights.
