Out of boundary errors

@jso Hi there, could you please submit a support ticket regarding this and include the estimated timestamp of when the issue occurred? This will help our support team investigate the problem further. Thank you!

2 Likes

Ok, thanks. I will try to reproduce the error with Record Issue enabled and will open ticket later.

2 Likes

I believe I know the root cause of this issue.
Yarbo works on Snow Blower area (Area with Snow Blower label). After completing the Plan Snow Blower tries to use Blower area (Area labeled as Blower only) to return to the dock. Blower area is underlying Snow Blower area and is smaller and therefore Yarbo thinks its outside of the area but its within. Yes, Snow Blower is outside Blower area but its within Snow Blower Area. Question remains why Snow Blower module tries to use Blower only area instead of Snow Blower only areas.
This is definitely design issue and should be fixed.

1 Like

All areas can be used by all modules, the labels are simply for filtering in edit mode

2 Likes

That turns out not to be the only issue, I was getting it much more often now that I had to make overlapping summer/winter areas…it would often get that area when it was in 1 area and crossed the “boundary” into the next area. Had a very short support call this morning and they said it should be fixed in the next software release. They offered to see if I could get the firmware for testing and I’m definitely interested in testing it. It might take a few days for approval, though​:crossed_fingers:. Although, with my luck the public release might be out shortly after, lol.

And I was usually screenshotting when it happened, at least 16x’s since december
Google Photos album:

Google Photos

Guess I get “priority installation” for the upcoming release. Hope it’s soon!

1 Like

Nice. Hope it solves the issue for you.

Well I’m not getting the error when it’s purposely transitioning sections…but Yarbo is actually driving out of the boundary occasionally when running escape maneuvers…maybe I need to reduce the safety boundary from 0? Ideally it still doesn’t give the error…

Yes, suggested safety buffer is 8 inches. That’s what it was forced to last year. I can run 4 inches, but it is very dependent on your situation with GPS and track slippages. PPVS Dead Reckoning doesn’t do well with slopes and track slippages. Either will cause it to lose accuracy faster.

It’s been fine running 0 up until this release.

Do you notice any track slippage when it happens or low GPS?

I think the tracks are slipping and it’s backing up as the “escape maneuver” and then freaking out that it went too far.

1 Like

I think we all do that when we slip :joy:

So no GPS issues that would put it into DR mode?

That pesky perimeter.

I don’t think so, it’s in the front yard and driveway where GPS is strongest

1 Like

We recommend keeping the safety buffer set to 8 inches, which has been our default setting since last year.

One of my areas with lots of turns does that so I’ve had to keep it at a full 12” buffer. Another good reason to have smaller areas that can be customized when needed.

1 Like

Confirmed software issue, hopefully next update :crossed_fingers:, wish we had a bug fix priority list…not sure this one is on the top of the list, but it could become one in summer​:sweat_smile:

1 Like

I’ve been suffering from this as well. Haven’t had the time to take a video for Yarbo support yet though.

1 Like