This happened to Yarbo twice this afternoon in different spots and both times it was not out of boundary, it was in by feet. I did not get pics of the second time, but the second time it was even more in bounds than the first. Good GPS, no trees nearby.
Fence is the boundary and can you notice it needs trimming, hint hint @Yarbo-Forum
It may have had a temporary GPS issue that caused it to think it was out of bounds. I assume you weren’t watching when it happened?
I was not watching it on the app, but was outside near it. The first one it may have been stopped for a few minutes, but the second time I caught it right when it happened, I opened the app, gps was good and I hit resume and it took off. Finished the rest of the area and recharged.
Very strange!
I have never had it happen before. The only issue I sometimes get is snowblowing right next to my garage door under the house eave, and that will just say waiting for GPS. I checked when it got on the dock, no map drift, and my DC is hard rigged mounted by welded pipe to my tv tower, so no way it can move.
Hi there, thanks for sharing the pictures and details. We may need to retrieve and review the system logs to help identify the root cause of the issue.
Please feel free to submit a support ticket with the pictures and any additional details you have available. Our support team can then further investigate the behavior and review the related logs for you.
It just did it again pics below.
@Yarbo-Forum ticket opened #199316
Do you have PPVS disabled?
Yes
Then that quality value makes sense. I wonder if that’s a factor here?
So now we have to use ppvs? I figured it was safer to not have it on, and not have it go off on it’s own, blind if you will? I have no issues with satellites and such except on the dock it takes time to find it, or I have to move forward 3 feet and then it locks in.
Not that we have to use it, but rather that it’s a corner case as most have it enabled and it’s enabled by default.
Thank you for reaching out and for sharing the detailed information regarding the issue.
We understand that the unit is stopping with an out-of-bounds error despite being within the mapped area, and we appreciate you providing the observations.
To help resolve this, we kindly suggest you to increase the perimeter buffer for the specific area where this issue is occurring. After adjusting the buffer, please monitor the behavior and check if the issue occurs again.
If the problem persists, please let us know, and we will be happy to investigate this further and assist you with a solution.
We appreciate your cooperation and look forward to your update.
Best regards,
Lionel
Team Yarbo
This is the bs response that I get from a detailed ticket I put in with pictures. Guess I need to add a 50 foot buffer in to the perimeter settings. What good is starting a ticket if this is the bs response they send back?
Definitely an incorrect response. It would not be the perimeter buffer you would need to modify and clearly PPVS is disabled, so you can’t adjust anything.
C’mon, who’s training the support staff. You definitely don’t want to increase the area buffer.
This feature is almost useless in it’s current state. If you could select what parts of an area perimeter could be extended, that would be useful.
I have had good results with the PPVS, but you’ll want to be careful not to let it roam too far without a quality GPS lock or it can drift off track. It usually regains signal and corrects it’s heading in my experience. I have one area where it occasionally stops and waits for signal.
Right, my thought is they could pull logs and see what happened. I gave them a time stamp of when it happened in the photos. I woke up at 3am to read their findings and this is what I get. I replied back that it was at least 30’ from the boarder, and this is at least the 3rd time this has happened in different area and not in the same zone either.
Is this the ticket number (#199316)? If so @Yarbo-Forum can hopefully get it escalated for log review.
Yes, I tagged @Yarbo-Forum in the post with ticket #.
Another case where support isn’t really looking at the pictures or thinking about the issue you described.