Mowing route going into NGZ

Im working on getting my mowing maps dialed in. I have a creek and pond feature in my yard that yarbo keeps getting dangerously close to either jumping in for a swim, or at least running the mower over the rocks. No good.
Looking at the map, the route extends into the NGZ,.exactly where the Rover has issues. There is a tree near that spot as well but ive cleard the low branches and grass around it. There should be lots of room for yarbs.

Any recommendations on how to get it to not plan a route into the creek?

Pictures of the area in question attached. I scribbled approximately where the route is going.
Thanks community, y’all rock

Im honestly quite surprised to see Yarbo planning to turn around inside of the no go zone like that.

Can’t say I’ve ever seen that happen before, but I guess maybe mine does it too but I just never noticed.

Will you ever want Yarbo to mow in those no go zone areas? If not, maybe as an alternative, you could re do that area, and have the outer parameter follow the creek/pond instead of using a no go zone. (Does that make sense?)

I get what you’re saying but the NGZ is kinda in the middle of the front yard, not on and edge. Its the weird shaped one here…

@Yarbo-Forum Would you like me to submit a ticket for this one?

I see what you’re saying. You could probably split that one large zone into two, with the pond in the middle being the border, but it wouldn’t be ideal.

I’d really love to know why Yarbo decided to ignore the no go zone and turn around like that. Let’s see what support has to say about it.

That looks like a path planning issue and I’d definitely submit a ticket but you could also try disabling any offsets, angle rotations, and or adjusting perimeter laps and see if that makes a a difference. Also see if it generates the plan that way or if that happens after mowing that area.

In the preview it isnt extending into the ngz but it does have this weird little triangle loop right in the same spot. I tried a few route angles and they are all the same.

Maybe I just need to extend the ngz there a little bit?

couldn’t hurt to drop a templated NGZ in that spot and see what happens.

Yarbo struggles with very narrow areas between NGZs , both in mapping and execution. In general, I try to avoid these and run Spiral pattern where I can’t. It helps avoid the dumb 2 foot zigzags.

Those zig zags drive me crazy.

Last year I worked to minimize / eliminate them. This season it seems the algorithm is updated so I need to make further mapping adjustments.

I’m not surprised, my yarbo went into a no go zone and mowed my blueberry bushes I had just planted, wiping out $550 dollars of blueberry bushes, it also decided to try and climb my front steps backwards and wouldn’t stop and caused damage to the trex-decking on the steps and the risers. Another $350 repair, It also damaged my vehicle this winter while snow blowing and decided after a firmware update that it now was in love with my car. That was an expensive fix. :flushed_face: also using the face looking module for follow me mode it randomly out of nowhere hooked a hard left and drove itself into a family members car who was visiting, right into their rear bumper and wouldn’t stop, it literally lifted the back of their Accord up into the air as the yarbo wrenched itself deeper into their rear bumper while riding upward towards the sky lifting their car, that was a VERY expensive mistake the yarbo made that I had to pay for. Honestly when it works right the thing’s awesome, but when it does weird quirky things that it shouldn’t be doing it is terrible and can be expensive. Beta bots on the loose.. sometimes it reminds me of those videos of the Chinese delivery vehicles that drive around and run over everything and crash into everything.. just tonight when it was trying to go home and dock it started trying to drive straight into some planting pots I had in front of my garage and it kept backing up about a foot and then driving forward and yelling obstruction over and over and would not correct itself so after about 5 minutes I decided to start recording it and then after a couple minutes of recording it I turned it left by dragging the rear and it then fix itself and went to the dock to charge. You kind of would expect this thing can correct itself and figure out that it’s doing things it shouldn’t be doing, but it doesn’t appear to learn and takes its perimeters and no go zones as suggestions only… :laughing::unamused_face::thinking:

Yarbo should not extend its route into a No-Go Zone under normal conditions. As Bryan mentioned above, we would recommend submitting a support ticket so our team can further investigate the path planning behavior in that area.

In the meantime, you can also try adjusting some related settings, such as offsets and route angles to see whether that helps temporarily reduce or avoid the issue.

Thank you for sharing the detailed information and screenshots — they are very helpful for understanding the situation.