After this last update my guy stops and waits for GPS way more frequently.
My rtk status is 4 and the app UI shows gps signal in green with a 0.02M but when you scroll to the “Status” section of the debug info it shows “Running: 6 WaitForRTK”
Is this happening to anyone else? It seems maybe there is GPS status change that is not getting recognized so the yarbo just sits there. Also, these stops are happening in areas where I never had any GPS issues, pretty open areas. Usually my GPS waits are in my wooded areas.
I forgot to add, the fix so far for me has been to take control and back it up a little bit. Then I resume the plan and it will work. Now the interesting part is I could back it up and the UI will show 0.04M but when I resume, that changes to 0.00M and in the debug status it changes to RunningNormal. So that is why I feel like some broadcast message of the GPS status changing is not propagating properly so it doesn’t know to “recover” from the GPS problem it thinks it has.
Hi there, could you please submit a support ticket for this issue? Our technical team will review the logs and investigate why Yarbo is remaining in the WaitForRTK status even when the app shows a stable RTK connection.
Please include the approximate time and location where the issue occurred, if possible. This will help our team investigate more accurately.
I just noticed yesterday it stopping and giving a “waiting for GPS” several times in the same position (right by my house). I took remote control and moved it into a solid GPS area, only to have it return to the same spot and have the same problem. I finally just stopped the job and re-started it on a different part of the yard. It has mowed that area several times before yesterday without issue.
This is the ticket number #230526.
It is a little bit annoying that there is just some automated response I guess keyed on the WaitForRTK. So I had to upload a screenshot of the debug screen even though it does not demonstrate the problem at all. It is just the screen shot of it now sitting on its dock.
What I was commenting on was when I submitted the ticket and I had WaitForRTK in there I got an immediate response that seemed to me to be an automated response that asked for a screen shot. So the only way to proceed with the ticket was to upload a screenshot.
Hi there, sorry for the inconvenience caused by the AI step.
Regarding your case, it has already been escalated to our FSE team for further investigation. We will work on resolving this issue as soon as possible and keep you updated on the progress.
I’m not sure when I got the latest firmware (3.14.1), but I’m seeing GPS oddities too. It was mowing one of my areas yesterday, and twice it told me it was out of bounds, while right in the middle of the mowing area, and it showed the correct location in the app. I drove it a foot or two, and it was able to resume fine. Then, when it was on the way back to the charger, it just stopped and said it couldn’t navigate a path. It was maybe 10 feet from the charger when it did this. I’m running a mow now, I’ll see if it does it all again.
Never happened to me before until 3.14… Now it does that randomly. Sometimes it is really out of bounds however so be careful and don’t assume it is still in-bound.
I didn’t notice it in 3.14.0, just now in 3.14.1. Both times it happened, it was definitely not out of bounds. The first time was maybe 2 or three feet into the mowing area (which butts up right to another mowing area, so there is no unmapped space even close). The second time was right in the middle, right over the planned mowing lines.
Yeah, something definitely wrong. Right while doing a mowing plan, it just stopped with “failed to calculate route”, and cancelled the plan (I don’t get a “resume” option). Solid GPS, right in a mowing area that I’ve done dozens of times. It was in process of mowing, it had finished the perimeter laps.
The behavior you described, such as showing “out of bounds” while the Yarbo was still within the mapped area and failing to navigate back to the charger, does not appear to be normal.
Could you please keep monitoring it during the current mowing task and let us know if the issue happens again? If it occurs again, please submit a support ticket and share the ticket number with us. Our team can then review the logs and further investigate the cause.
Thank you for sharing your experience and helping us improve.
Thanks for the reply. I do have a minor update, but I’m still monitoring. I remembered that I recently was trying to figure out why my Yarbo was missing spots/parts of rows (like 1 to 2 inches of uncut grass in a line). One of the suggestions was to turn on PVSS. I believe it was the first mow after disabling that that these new issues came up. I turned it back on, and haven’t had the out-of-bounds or “failed to calculate route” issue since. When they occurred, GPS never dropped and it in a wide-open area (well away from trees/buildings). I guess now I’m back to figuring out the missed lines/spots. I will say my property is pretty much not flat anywhere, and the missed spots always seem to be on inclines.