Yarbo having issues returning to charger after completing mowing task

So I just remapped this area on Saturday because I added a greenhouse and remove a temporary parking shed I had in this zone. I also remapped the path to this zone.

Sent yarbo to mow Saturday night (insert problem with rover going dead at 4am). Today it is dry so sent yarbo to finish area. It did complete it. But then I got the error in the pics below and it did not return to charge. I tried manually it would not go, same error. I tried to send it to another zone to mow, same error.

I then drove it manually about 100 feetish, and then sent it to recharge and it did it with no error.

Can anyone explain this? I don’t see anything wrong with path or zone mapping.

Pictures in post below. Top right picture at 12:45pm, is after I manually drove it closer to pathway to charger.

@Yarbo-Forum ticket opened #199302

I am going to bet it is something with the path/pathway/transit offsets.

When it happened to me, it was because not all the perimeter sides of an area were joined correctly together, or the path I created to join two areas was not detected as correct because it was not long enough within the two areas. If you don’t have one of these problems, I don’t know what to suggest.

I have offsets off on the pathway. Path goes like 20 feet into this zone so that should not be an issue. Zone is complete closed loop so that should not be an issue.

Not sure what is going on. I will probably redo pathway after tech support looks into it, just to be sure nothing is wrong, but I mapped it from dock to area, pretty simple path.

You could disable the offsets and see if the error clears. Then you’d know if it’s that or not.

They are disabled on the pathway for sure as it takes a concrete sidewalk back to dock. Offset is probably on in that zone, I don’t see why that would affect it not returning to charge.

I guess it is my time for odd issues. I have two memory paths for trimmer set up in this area, and had issues getting it to start a memory path and trim, even if I was in this zone. I kept getting the error about wp005 failed to calculate route.

Does the memory path exit the area at all?

I don’t know for certain, not at a large extent, but maybe it hugged a fence line closer than the areas boundry, but if so we are talking an inch max. But after I remapped the whole zone (area) I mapped everything as close as the trimmer would put the core to that fence area.

Hi there, I’m sorry to hear you’re experiencing this issue. This may require further investigation from our support team.

Thank you as well for submitting a support ticket regarding this. Our team will look into it further and follow up with you as soon as possible.

I would definitely start with disabling Transit Path for all Areas on the route home.

Done, it is not enabled,

Nothing else is jumping out to me. If you’ve double checked that all the Pathway and Area Offsets are disabled. Support may have to jump in. I would probably delete the Pathways and create fresh ones.

I don’t get how I manually drove it 100 feet closer to path, but still in same area, and then it worked. This makes no sense.

Of course ticket was ignored last night. And the other ticket I opened got a BS response.

The only thing that look a little unusual is the stacked Pathways. No idea if it’s related, just an observation.

It is a physical concrete sidewalk. No other way to do it. I had just one path to the concrete pad in front of the garage, and then short pathway to mowing area, but the trimmer did not like that for memory trimming.

Also this would not be an issue if Yarbo did mapping by module installed instead of just jamming everything in one map. One of the pathways is for snowblowing.

Forgot Pathways can’t be tagged. Makes sense now. I got nothing else. Sorry.

I agree…for the dead ends, making them overlapping had created problems for me

There’s an overlap there and pathways cannot start or end in an overlap and need to extended 3.3ft past the overlap. This might be a factor and could have some weird results working sometimes depending on where the unit is when it’s calculating the routes.