I do have a ticket open for this but hoping someone has a quick fix so I can take advantage of a rare dry spring day. My mower will not calculate getting into a mapped area, nor will it start if I drive it into any mapped area. throws an error to the effect of pathways are cut off by no go zones. I have not added or removed pathways since last season. Has even mowed a half a dozen times this season. I have removed a couple of no go zones in hopes of reducing string trimming time, due to the fact the times when it did mow this season it seemed to encounter less ‘gps loss’ induced stops.
My logic in debugging says it is a firmware issue because it mowed an area the day before an update.
If you have a No-go Zone that cuts off part of an Area, NOTHING will calculate. So if you have a situation like that big, tall rectangle going straight through the middle of a couple of Areas, no route will be calculated – no route at all anywhere on the map. So turn those No-go Zones off or delete them. Don’t let a No-go Zone create multiple separate sections in one Area.
You can try the steps the others have mentioned. If you can’t get it, post your map and screenshots of the errors and we will try and help figure it out.
Hot Dog, we have a wiener! did have a NGZ splitting an area after the deletion of a second NGZ (over lapping to prevent a small area from being isolated.) Thanks Ken, much appreciated.
