Is anyone able to provide any assistance with this persistent error?
Note that no new map areas or NGZs have been added since Yarbo’s last successful winter work plan; only changes to Yarbo have been M1 replacing S1 & OTA updates.
I’ve attempted to initiate a work plan with all NGZs toggled OFF
I’ve remapped the path from the charging station to map area 1, and attempted to initiate a work plan for map area 1 ONLY.
Unable to begin work plan. Initial error messages indicating clearing path ending in NGZ (no changes to map have occurred since last fall). Turned off all NGZs, shortened work plan to only include area adjacent to docking station. Unsuccessful. Deleted and recreated initial pathway from dock to Area 1, unsuccessful.
5/28/26: The issue continues with attempting to mow area 1 ONLY adjacent to charging station:
Unable to begin work plan. Initial error messages indicating clearing path ending in NGZ (no changes to map have occurred since last fall). Turned off all NGZs, shortened work plan to only include area adjacent to docking station. Unsuccessful. Deleted and recreated initial pathway from dock to Area 1, unsuccessful.
5/27/26: Unable to begin work plan. Initial error messages indicating clearing path ending in NGZ (no changes to map have occurred since last fall). Turned off all NGZs, shortened work plan to only include area adjacent to docking station. Unsuccessful. Deleted and recreated initial pathway from dock to Area 1, unsuccessful.
The new pathway offset feature might cause this issue.
As afr as I understand, if pathway is close to area border or ngz and pathway offest setting allows it to breach the ngz or area border, then the error is not automatically handled, but the failed to calculate error is thrown …
Note: Map Area 1 does not have path offset enabled
Note that Map Area 1, the area immediately adjacent to the charging dock, does not have any NGZs associated with it.
By process of elimination, I was attempting to initiate a work plan with Area 1, Area 1+2, Area 1+2+3, etc. to isolate the problematic location on the map. Unfortuinetly, map Area 1 (the closest & most simplistic) would not initiate a work plan.
Note: Map Area 1 does not have path offset enabled
Note that Map Area 1, the area immediately adjacent to the charging dock, does not have any NGZs associated with it.
By process of elimination, I was attempting to initiate a work plan with Area 1, Area 1+2, Area 1+2+3, etc. to isolate the problematic location on the map. Unfortuinetly, map Area 1 (the closest & most simplistic) would not initiate a work plan.
Really hard to see the whole map. Pretty impressive looking map BTW. I’m going to agree with @andris.leja that it very well may be path or pathway offset causing you some grief. Try disabling those (since you already disabled all the NGZ’s). See if that resolves it for you. If not, lets get some closer views on your NGZ’s and see if we see anything that might be causing you the issue.
I just opened every map area to confirm that Path offset is toggled OFF for each. Here are some close-ups of the NGZs: https://photos.app.goo.gl/ytW7xi8AQie1ybZU7. Is there a better way to provide an image of the entire map instead of screenshots? I’m using web browser BlueStacks App Player but given the size of the map, it’s still a relatively small screenshot to share.
When I created the NGZs, I previewed each and map-corrected if one interfered with a path or area of travel. Again, no map/pathway/NGZ changes have been made since Yarbo’s successful winter work plans.
Thanks for the kudos on the map. As I’m sure you can appreciate, it’s been hours of “perfecting” it, the pathways of travel, the slopes, etc. Out of desperation, I’ve begun deleting NGZs to try to flush out the presumed problematic location w/o success:
Nothing is jumping out at me except maybe one pathway looking a little short near an overlap. But that could just be the view. I am definitely curious about the random pathways that loop around seemingly nothing? Yarbo support may have to see if they can isolate what on your map is causing the issue. Just to confirm, you have the mower module attached? Not blower or anything else that needs a yellow line drawn on the boundary?
So I assume there was a NGZ there. Did you find the pathway helped the situation? I can’t imagine it actually used it at all? You have piqued my curiosity here.
I saw references to Ares Path Offsets in the conversation. There are also Pathway Offsets that can be enabled for each Pathway. @andris.leja mentioned this but I didn’t see a confirmation these were disabled?
