# Yarbo is out of boundary by 4.9ft (1.5m) **URL:** \ **Category:** GPS Issues\ **Tags:** lawn-mower\ **Created:** [August 11, 2026, 2:15pm UTC](https://forum.yarbo.com/t/yarbo-is-out-of-boundary-by-4-9ft-1-5m/7235 "2026-08-11T14:15:02Z")\ **Posts on this page:** 11\ **Page:** 2
**Author:** ![B-Mod](https://yyz1.discourse-cdn.com/flex007/user_avatar/forum.yarbo.com/b-mod/32/292_2.png) [@B-Mod](https://forum.yarbo.com/u/B-Mod)\ **Post date:** [August 13, 2026, 4:45pm UTC](https://forum.yarbo.com/t/yarbo-is-out-of-boundary-by-4-9ft-1-5m/7235/21 "2026-08-13T16:45:27Z")
Just an FYI I received this same message around the middle of May, so it is not fixed yet. ---
**Author:** ![Yarbo-Forum](https://yyz1.discourse-cdn.com/flex007/user_avatar/forum.yarbo.com/yarbo-forum/32/126_2.png) [@Yarbo-Forum](https://forum.yarbo.com/u/Yarbo-Forum)\ **Post date:** [August 14, 2026, 9:39am UTC](https://forum.yarbo.com/t/yarbo-is-out-of-boundary-by-4-9ft-1-5m/7235/22 "2026-08-14T09:39:13Z")
Then it may not be related to the DC version. If you continue to experience this issue, please submit a support ticket so our team can further investigate and assist you. ---
**Author:** ![cobradunn](https://yyz1.discourse-cdn.com/flex007/user_avatar/forum.yarbo.com/cobradunn/32/298_2.png) [@cobradunn](https://forum.yarbo.com/u/cobradunn)\ **Post date:** [August 14, 2026, 1:14pm UTC](https://forum.yarbo.com/t/yarbo-is-out-of-boundary-by-4-9ft-1-5m/7235/23 "2026-08-14T13:14:33Z")
Saw it one time and it hasn’t reoccurred. Odd one. ---
**Author:** ![jddockery2](https://yyz1.discourse-cdn.com/flex007/user_avatar/forum.yarbo.com/jddockery2/32/3260_2.png) [@jddockery2](https://forum.yarbo.com/u/jddockery2)\ **Post date:** [August 14, 2026, 6:39pm UTC](https://forum.yarbo.com/t/yarbo-is-out-of-boundary-by-4-9ft-1-5m/7235/24 "2026-08-14T18:39:38Z")
I have noticed a periodic drift. It makes me think one of the satellites is not where their table thinks it is. if I catch it I shut the mower down and wait for the position to look normal again. The biggest pain is when it is sitting on the charger and will not charge because it thinks it is 10 feet away ---
**Author:** ![andris.leja](https://yyz1.discourse-cdn.com/flex007/user_avatar/forum.yarbo.com/andris.leja/32/503_2.png) [@andris.leja](https://forum.yarbo.com/u/andris.leja)\ **Post date:** [August 14, 2026, 7:15pm UTC](https://forum.yarbo.com/t/yarbo-is-out-of-boundary-by-4-9ft-1-5m/7235/25 "2026-08-14T19:15:30Z")
Hey, If this is a known issue, then why would you put extra load on support (and to the customer to collect logs and endlessly discuss with AI) to look at more and more similar tickets where the issue is identified and promised to be fixed with next update? ---
**Author:** ![GROWF](https://yyz1.discourse-cdn.com/flex007/user_avatar/forum.yarbo.com/growf/32/2579_2.png) [@GROWF](https://forum.yarbo.com/u/GROWF)\ **Post date:** [August 14, 2026, 7:24pm UTC](https://forum.yarbo.com/t/yarbo-is-out-of-boundary-by-4-9ft-1-5m/7235/26 "2026-08-14T19:24:01Z")
I agree Yarbo Support struggles with quickly identifying known issues. From my professional experience in Services, it is usually a tool/system/time issue (or lack thereof) than a “bad employee” issue. Most employees try to do a good job, but when they lack good tools, training, and/or reasonable work time, they struggle. That struggle often appears in the form of elongated ping-pong communications with customers. ---
**Author:** ![andris.leja](https://yyz1.discourse-cdn.com/flex007/user_avatar/forum.yarbo.com/andris.leja/32/503_2.png) [@andris.leja](https://forum.yarbo.com/u/andris.leja)\ **Post date:** [August 14, 2026, 8:21pm UTC](https://forum.yarbo.com/t/yarbo-is-out-of-boundary-by-4-9ft-1-5m/7235/27 "2026-08-14T20:21:32Z")
Agree. So basically if there is a ticket for yarbo crossing NGZs, yarbo missing to mow stripes, yarbo getting out of boundaries by 1.5m .. support should have enough info to pass to developers to fix the issue and all further tickets should be dismissed, unless they are really struggling to find what causes the issue. But in those rare cases me, as a customer, would appreciate that I can reproduce the issue and logs are collected without silly AI advices to change the setting and try this and that before the work plan. ---
**Author:** ![Yarbo-Forum](https://yyz1.discourse-cdn.com/flex007/user_avatar/forum.yarbo.com/yarbo-forum/32/126_2.png) [@Yarbo-Forum](https://forum.yarbo.com/u/Yarbo-Forum)\ **Post date:** [August 17, 2026, 10:01am UTC](https://forum.yarbo.com/t/yarbo-is-out-of-boundary-by-4-9ft-1-5m/7235/28 "2026-08-17T10:01:43Z")
@andris.leja @GROWF Hi there, I’ve gone through the relevant ticket once more, and it appears that this case may not be the same as the known issue we previously identified. We apologize for the earlier miscommunication in the ticket. I’ve asked the FSE responsible for this case to escalate it to our R&D team for further investigation so we can better determine the root cause. Thank you for raising this concern. We also understand the importance of distinguishing known issues from cases that still require further investigation, so users are not asked to repeat unnecessary troubleshooting. ---
**Author:** ![GROWF](https://yyz1.discourse-cdn.com/flex007/user_avatar/forum.yarbo.com/growf/32/2579_2.png) [@GROWF](https://forum.yarbo.com/u/GROWF)\ **Post date:** [August 17, 2026, 4:48pm UTC](https://forum.yarbo.com/t/yarbo-is-out-of-boundary-by-4-9ft-1-5m/7235/29 "2026-08-17T16:48:34Z")
Thank you for the update. FYI I have mowed once since opening the ticket. I mowed on Friday, Aug 14 without experiencing the issue. I turned on PPVS which might have helped mitigate the issue. My next scheduled mowing is tomorrow (Tuesday, Aug 18) and I’ll be monitoring for another occurrence. If it again mows without this problem I might try the following mowing (likely Thursday, Aug 20) with PPVS turned off. Trying to get data points the engineers can use. ---
**Author:** ![B-Mod](https://yyz1.discourse-cdn.com/flex007/user_avatar/forum.yarbo.com/b-mod/32/292_2.png) [@B-Mod](https://forum.yarbo.com/u/B-Mod)\ **Post date:** [August 17, 2026, 6:58pm UTC](https://forum.yarbo.com/t/yarbo-is-out-of-boundary-by-4-9ft-1-5m/7235/30 "2026-08-17T18:58:39Z")
That is how I got rid of this same error, I had to turn on PPVS but I turned the settings down just a little above minimum. Odd you have to turn on a feature you don’t want, but it worked so I left it this way. ---
**Author:** ![OhCanada](https://yyz1.discourse-cdn.com/flex007/user_avatar/forum.yarbo.com/ohcanada/32/472_2.png) [@OhCanada](https://forum.yarbo.com/u/OhCanada)\ **Post date:** [August 17, 2026, 11:53pm UTC](https://forum.yarbo.com/t/yarbo-is-out-of-boundary-by-4-9ft-1-5m/7235/31 "2026-08-17T23:53:53Z")
I get this error multiple times every workplan. Here are a couple from today. I have ppvs turned off, ill try turning it on at minimum settings and see if it helps. Agreed we shouldn’t have to turn on ‘features’ (especially beta features!) to make things work. But also, if it works it works. ![Screenshot_20260817_175011](https://canada1.discourse-cdn.com/flex007/uploads/yarbo/original/2X/6/6c8f6539fa5851915a59c879d77e7cb253737af5.jpeg) ![Screenshot_20260817_160139](https://canada1.discourse-cdn.com/flex007/uploads/yarbo/original/2X/e/ed86cf35f63d3e5347bada8e38139c9fc26d7f85.jpeg) [Previous page](https://forum.yarbo.com/t/yarbo-is-out-of-boundary-by-4-9ft-1-5m/7235.md?page=1)