Improve Reduce Boundary Option

Can we have configurable distance away from the edge of the map?

The Reduce Boundary currently only gives the options for 0,4,8,12. 0 is too close, 4 is too far. how about a slider for 1,2,3?

5 Likes

Moreover, not all boundary is the same. I would like to be able to segment the boundary and its behavior by classification.

Road or street segments
Decorative bed
Sidewalk
Fence

come to mind immediately

3 Likes

I like the idea but instead of having preset definitions I would prefer to be able to select or trace a boundry segment in the app and set the distance that way.

1 Like

I’d still like to be able to customize the behavior. With common segment types across multiple zones i was just trying to save some repeat work doing each individually.

1 Like

See: M1 Boundary Setback increments

2 Likes

Thank you for your suggestion! We’ve actually received this feature request before, and it’s already been added to our development list. We really appreciate your input and feedback!

2 Likes

Boundries and overlaps need more fine grained control.

2 Likes

I know I am doing something wrong but my Yarbo leaves about 18 inches uncut on the boundary. I even re-mapped the boundary as close to my fence as I could get. What adjustment am I missing?

1 Like

Area Settings, Reduce Boundary. Default is 4". Most of mine are 0.

Is it just this one spot, along that one fence?

If you put a No-go Zone outside on the edge of the boundary (as some people do), it could be reacting to that.

If Vision is on, the rover could be reacting to the fence, I suppose. What’s your Obstacle Avoidance set to?

Also look at your GPS Diagnostics when in that spot. If you’re looking at (among other things) Status 5 (well, not 4) or a HeadingDop > 2, when you map and mow there, everything could be off. Map drift could do this also, but you should get an error with that.

2 Likes

Thanks

Ken

1 Like