Anyone else get random out of boundary errors even though you have good GPS and you’re pretty far from the boundaries of any of your areas?
2 Likes
Haven’t see that one yet. Just to confirm that it’s actually at that physical location in real life and not just displaying that in the app?
1 Like
Yup, it’s done it multiple times running that specific sidewalk along the long edge of that no-go zone. It’s running fine inside the driveway area though no problem and all those other sidewalks
1 Like
Very strange. Doesn’t even look like it got close to the NGZ or boundary.
2 Likes
I’ve gotten that many times. It used to mean there was some issue with the map, like a strange outcrop that made the map difficult to generate. They applied a hot-fix and it went away for a long while. But then I got it again, much more rarely. There doesn’t seem to be any real reason, however, one thing’s for certain…it has nothing to do with being “out of boundary”. It’s some sort of other error that generates this message.
2 Likes
Yeah those incidents were with the mower. It was usually where there was a pinched area and the path planning line went out of bounds when calculating the route. Also similarly when there were jagged edges on the boundary line of the area forcing a clearing line to go out of bounds. I don’t see anything here like that unless it’s seeing that sidewalk as a boundary. Could be an error in that code possibly.
1 Like
Hi there! Could you please submit a support ticket for this issue? We’ll take a closer look and work on finding a solution for you.
3 Likes
I also just replied to the support ticket but I’ll also put it here for others to reference.
I think I figured it out. The one Sidewalk furthest north near the driveway I created a while ago, but recently I “trimmed” off a bit of the driveway as it was detecting the garage door as an obstacle and moving further away. Once I trimmed the northern edge off a few inches that sidewalk was no longer starting inside the Driveway work area. I just deleted that one and now it’s working fairly well 
3 Likes
Thanks for sharing.
1 Like
That error is like a default error message. It could mean many things, but the one thing it doesn’t mean is that Yarbo is out of boundary.
1 Like
Oh, trust me, it means that too.
2 Likes
oh 
Literally 
2 Likes
Always a bright side with @steve
3 Likes
I installed SnowBlower today to map the area and set params for snow blower and plow mode and perform preliminary run.
I got out of the boundary error in Plow Mode after clicking recharge button to return back to the dock. Yarbo was moved to the next area by app control and the same error appeared. After disabling PPVS Yarbo returned as expected. In both cases Yarbo was at least 0.5m within the area. Looks like PPVS is not adding up but also reducing by having its own bugs.
1 Like
Here you see overlap of 3 areas. 1 on the left side is overlaping 2 areas from the right side.
2 areas on the right side represent road with parking (area1) and road without parking (area2) with the different blowing direction (area 2 without parking in case if car is parked with opposite blowing direction, not against the car).
I believe this is ok real life scenario.
In the map SnowBlower filter is enabled, so all areas displayed are snow blower areas and outside border should be used not internal or overlapping borders.
In picture Yarbo is within the Area by any meaning. It should go to the left and use pathway.
As I mentioned I turned PPVS off without moving Yarbo and its started to work as expected and returned back to the dock without any out of the boundary errors.
Segmentation of area with small overlapping should be also ok scenario, not something special at least until direct map editing is allowed in the App to create perfect border intersection.
Looks like currently algorithm for overlapping areas is not complete for any of the modules. Blower module was also dancing by crossing such areas until fixed in last firmware and now it crosses areas as expected.
1 Like