Respawning this topic.
I also have faced this issue. Yarbo is mowing deadend un throws an error or out of boundaries..however it’s still on the deadend.
Ticket already created.
I’m betting it’s related to the overlaps. Hopefully they can confirm and do something about it. Assume this worked fine for a while before or did you recently add or change something?
That’s what I was thinking a well. Maybe make a new DE that starts in that upper area to see what happens.
Well. I also have other deadends overlapping in other places and no issues there.
Here i suspect that there might be several factors:
- Some tree coverage + shed with metal roof blocking some sattlites
- Slope. Even when drawing the deadends had to stop to wait for gps to recover and yarbo was rolling backwards.
And one more wtf moment there - one of those deadends in slope yarbo always drives backwards - it goes where deadend starts, turns around and drives backwards imto.deadend and then drives out of deadend forward. Have not observed anything like that with any other deadend in my map.
Yep. Randomly backing into DEs has been there since last year. I haven’t figured out exactly what causes it, but I’ve had to remap a couple to correct it.
Whenever the rear of the core is closer to the entrance of the dead end it will just back down. They are going to fix this.
Overlapping DE’s might be a factor but I was referring to the overlapping areas. Those tend to cause confusion like this as it thinks it’s on a different layer than what it should be paying attention to.
Refresh my memory because I still haven’t mowed yet, because I haven’t hit my first mow season. So I’m speaking a little outta pocket here, but these Deadend issues seem very similar if not the same to Sidewalks on the S1. On the S1 my opinion is that Sidewalks are unusable. Seems Deadends are running the same programming chassis.
Yep, dead ends are essentially reversing sidewalks and they share the same root issue.
It would be beneficial to define pathways and include them in work plan.
That would be the way how to address special places where it’s enough for yarbo to drive one (or maybe in any) direction.
Drawing a pathway here would do the trick.
As there is quite steep slope, i can’t allow yarbo to figure out himself the routes and try to navigate there and probably even roll over there.
Agreed. Pathways should be able to be enabled/disabled and also able to be added to work plans.
Yep, yep, yep! Lots of places I could use this.. with the mower.
If I had to guess, something with the overlaps and maybe if GPS signal dropped out.
Maybe, but there has to be a function where Yarbo checks that the unit is no longer out of the boundary, even though it hasn’t traveled, and then automatically continue the plan.
Agreed! I think they are relying too much on GPS and not factoring in the fact that it can’t move quickly out of bounds from where it originally knew it was. In other words, it was in the area and suddenly wasn’t because poor GPS. It should be impossible to move that fast out of bounds (rely on IMU and wheel odometry to back this up). Pause and wait for GPS quality to recover and then assess what to do based on the actual good data at that time.
There should be a way to tell if the unit drifted into other areas or a radius of likelihood. If it’s in another labelled work zone keep going you’re fine, if it really is possible it’s out of all work areas, then it’s valid to throw up that error and stop. Could also have settings in the NGZ for danger/severity levels and if it’s close to them(say a pond or cliff) PPVS settings/responses change dynamically. There should also be an easier to paint/map that to “out of bounds” areas. Maybe an update to the drawing rules where we can draw connected poly-lines instead of only rectangle or circle templates.
This needs to be added.