I should’ve never worked as the no go zones are blocking the pathways and it should never enter a NGZ. This is definitely a pathing issue, but the NGZ is the catalyst. Why do you need these there in the first place?
@bryan.wheeler - This one’s odd. You can clearly see the rover mapped out a return to the Docking Station by going around the No-go Zones into an unmapped Area. We’ve been asking Yarbo to respect Area boundaries and No-go Zones for “get around the Area” (what I think of as “utility paths”) type navigation, so that bug’s in. This is an example of that, coupled with a map that is drawn in a way as to be unworkable for the rover. In this case the rover should have stopped and thrown an error.
This is crossposted on FB which may be getting more attention, not sure.
This corner case was absolutely not accounted for in their programming and testing. I’m not surprised at all to see some issue here. Surprised the pathways work at all because that bug was fixed previously if I recall correctly.
Super wet area… the smaller no-go zone is often too wet to mow until July or so, but I had to expand it due to a week of a lot of rain.
I’m hoping the giant squares can be turned off by next week. (It’s even too wet for my regular mower with the giant tires. Not sure how, but this little robot on tracks is way harder on the lawn than my 54” mower that weighs 10x
Instead of a NGZ, why not map that as a separate area and exclude from the plan during wet season. Then create a path that Yarbo can navigate around from one area to the next bypassing this wet zone.