I’ve heard this from a few people. I’d file a ticket with the times if you can recall. They are probably in the notification history.
I got this again today. Drove rover 10 feet, then hit recharge and it recharged no problem. Adding to my open ticket tonight
No help at all from Yarbo on this one. Please draw a path from dock to area and see if that fixes it. No sh*t, I only wrote that to them at least three times in the ticket. They are claiming pathways on top of each other can cause issues. No fixing that, but I never had this issue till just the past week.
I had the same problem, but noticed that I had the pathway to the docking station turned on. Once I turn this option off for all my pathways to the docking station it started to work again. However, I did not have to turn pathway offsets off between the different mowing zones.
Hi there, could you please check the pathway offset settings for the pathway connected to your docking station? If the feature is enabled, try turning it off temporarily to see if that helps.
Also, please try the suggestions from our support team and let us know how it goes.
There are a couple things that can cause these routing errors, especially in combination.
-
Pathway Offsets enabled when the Pathway is close to NGZs or Area boundaries. It needs to be able to shift it’s path without running out of space. This one is very dependent on map density and layout. Disable one at time until you find the offender(s)
-
NGZ Buffer feature defaulted to 12" when implemented. This reduces area it has to plan routes. Dial it back to something reasonable like 2".
-
Pathway Offset enabled for Pathway to Dock. This one will cause an instant error. Disable it.
Pathway offsets are turned off, was never turned on as yarbo needs to travel down a cement sidewalk, so no use for offset.
Yep. It sounded like you yours is something different. Keep us posted if you find a solution.
I got rid of the dedicated path to charger. Now I just have a path from charger to my concrete slab in front of the garage, and then a short path from slab to mowing area. I will see if that fixes the issue.
I am now getting this error on almost all my areas when they finish. If I move the rover a few feet and hit recharge it will then go recharge without the error. Why do they keep breaking the software?
You turn off the offsets?
Pathways are off, but in area they are on.
I’d toggle transit path offset off and see. If not, try in area. Should not matter on a recharge, but stranger things.
Sorry for the issue. I’ve asked the field service engineer responsible for your case to check your ticket #199302 as soon as possible.
I added to the ticket again as it just did it again. I hit record just before the error popped up so they have great data if they look for it. I put all this in the ticket with even more pics. Drive the rover manually a few feet and it goes back to charge just fine.
Finally happened to me in rarely cut area. It couldn’t find its way home after finishing. I turned both offsets off and still had the error. Did another edit then Exit without saving any changes and was able to route home. There’s some obscure bug here.
You can see on the pic how offsets could cause an issue, but just disabling them didn’t initially fix it.
You disabled transit path too?
Sorry for you, but glad I am not the only one. It happens on 3 of my biggest areas now. One of them is every single time it does that area.
I tell ya every “feature” they bring out they break stuff we need for the rover to do it’s job.
Yep. Didn’t grab screen of that though, but thought sure that was it. Only the third time of going in and checking everything again worked. I know, can’t explain it either.