I suggest adding the ability to place a templated no-go zone on the fly during a plan. Here is an example use case scenario: During a plan, yarbo stops due to track slippage on a tree root for example. In order to place a no-go zone currently I have to end the plan and revise the map then start the plan over at whatever percent I ended it at. Upon restart the plan also shifts by 10% unless i have turned that off, so it really doesnt pick up where it left off. I would rather drop the no-go zone without interrupting the plan, get yarbo unstuck manually (with smart vision) and resume the plan.
5 Likes
That slippage thing is weird. I had some slippage, helped Yarbo out of the situation and hit resume. He proceeded to swing around and get stuck in the same spot again. Not the brightest move.
2 Likes
This is a good idea but hard because it changes the entire route that it planned. It does currently point cloud map it, it would be possible for them to enable a setting to avoid track slippages. It doesn’t do so currently.
I also wish those were marked in yellow and not red. It would be nice to be able to tap those and permanently save them for future though
3 Likes
Yarbo knows where it’s been already. Seems reasonable to assume it could re-calculate the remainder of the job, taking into account any new NGZs.
2 Likes
And if I turn on the blades to move it out of the slippage area, mark that as mowed.
2 Likes
The best way to trick it is get it lined back up on the path line right before the slippage area and hit resume. If you get it close enough it will just continue like nothing happened.
2 Likes
In my case the slippage happened again. 
Well not that close. Lol
1 Like
I support this. When it highlights an area on the map with obstacles, we lose them when the job is done and we can’t add some no go zone around it or fix the map. Would be nice that all those errors be saved so we can act on it or « clear it »… But you know what? Those nice to have features are probably for later no? They probably should focus more on fixing the vision first…
2 Likes
Yep.
1 Like
100% they are for later and they said they are focusing on the user nice to have’s after fixing the other bigger issues. But simple things like making track slippages yellow instead of red would be a nice EASY thing to help users understand what is going on in the interim.
2 Likes
Indeed. Sounds like a thing I could do with ChatGPT 
2 Likes
Thank you for sharing your insight, and I’ve also reviewed the ongoing discussion on optimizing the no-go zone feature. Adding on-the-fly no-go zones during an active work plan is not something we’re planning to implement in the short term. However, the idea of saving obstacles identified by the rover during a work plan is something we’ve considered before, and I’ll be sure to pass along your renewed interest to our product team.
Regarding the suggestion about color differentiation for marking track slippage, we’ve already shared that with our product team, and they’ve acknowledged and accepted the idea.
We truly appreciate everyone’s input and efforts in helping us improve the Yarbo experience.
1 Like
It would be helpful to be able to mark a no go zone during a plan but not implement it or store it in the map until after the active plan is complete and after proposed changes were reviewed? Similar to obstacles marked by Yarbo during a plan. We should be able to review them and add them to the map after the plan is complete (or ended by the user)
2 Likes
Thanks for your input! We will pass this along to our product team, especially if more people express interest in this feature.
+1 to this. Happens very frequently.
The Problem: During a plan, Yarbo runs into an obstacle that causes track slippage and manual intervention. It is very difficult to estimate and plot where minor obstacles, such as tree roots, are located.
The Solution: Anything the Yarbo engineers can come up with to resolve this issue, whether that’s adding a no-go zone, remembering obstacles, or other.
3 Likes