Can someone explain the use case for allowing dead-ends to be run in reverse? Is this a bug? Feature?
Multiple deadends have to be so strategically created to ensure Yarbo doesn’t back its way down the dead-end path.
Honestly, sometimes I want to pull my hair out, the software on this product is so frustrating.
I’m confident I spend 2x the time babysitting, remapping, etc, than just cutting the damn grass. Maddening.
I asked about this on May 4 on FB. I haven’t seen it since, and I admit I haven’t been trying to figure out why it happens, as I just want this thing to mow so I can knock off other projects.
Another FB user reached out to me today with the same issue. He was going to redo them. Curious if that fixes it for him. I suspect this is a bug.
This happened to me the other day.
I’d drawn the DE with one end starting in an area, and it worked normally.
I edited / trimmed the area such that the DE was no longer in it.
I added back to that area such that the DE was again, back within it.
From there on, Yarbo backs into the DE and drives out, forward.
Hi there,
Thank you for your feedback. We’re aware of the issue you’ve mentioned. At present, if the rover detects that its rear is already facing the direction of a deadend, it will proceed into the dead-end in reverse, without turning around. This behavior is designed to reduce unnecessary turning and help minimize wear on the grass.
That said, we’re actively evaluating whether the algorithm behind this behavior needs to be adjusted to better handle different scenarios.
We’re sorry for the inconvenience this has caused, and we truly appreciate your patience. Please know that we’re continuously working to improve the software and provide a smoother user experience.
Yes, @Yarbo-Forum, thank you for looking for ways to reduce wear on the grass!!!
My concern with the “I’ll back in because my butt is there already” algorithm is that the mowing won’t reach as far, so it’ll leave a rover’s length of grass at the end instead of the few inches the mower would leave.
This definitely seems like a design flaw because yes, the core is not the mower and can’t cut grass. And, if it knows this and extends down to the M1, then it’s exceeding the Dead End boundary that was mapped. This is a problem if it is.
THANKFULLY the rover’s butt stops where the mower’s front end would, else it’d be breaking out over a border and teabagging some hostas.
Not to mention, there is no bumper or vision on the back, so it is way riskier to back in first. This should definitely be considered a bug, or it should be a user setting that allows the user to choose (at their own risk).