And where the Yabro lost GPS in these pictures it basically has a line of sight to the datacenter.
At this point the Yarbo seem useless. The datacenter is on the side of the house about 30 feet in the air with 180 deg clear sky view. I can’t even get it cut the yard without babysitting it.
I am having the same issues with the GetAngleError. My understanding is that it is an IMU error and I know there are some IMU specific fixes being addressed in the next release. I am hoping this is one of them. What I have found is that if it doesn’t recover on it’s own after about 30 mins sitting idle, then reboot and drive it out further into the open (it seems a little close to the house there) and then it will usually recover “GPS” and you can resume. Sometimes driving it out a bit also works.
I have the same problem. I think it even got a little worse after the last hotfix, it actually happened during a video call with yarbo support,got no GPS signal for a few minutes. They told me to move it to a more open space, but it was already in an open space with clear view to the sky.
To move yarbo a few meters everytime it loses gps is not really a good solution for a autonomous yard robot.
Thanks for the share on the page. They need to go back and fix the stuff that’s getting cut off when viewing that page. Several lines are cutoff mid sentence, mid word, etc…lol
Scroll to the right. There are also a few references to the documentation “The specific status codes and details can be found in the right-side documentation or additional references” that doesn’t exist. @Yarbo-Forum
Thank you for pointing this out! We’ve forwarded the issue to the relevant team and will make the necessary revisions as soon as possible. We appreciate your attention to detail and your help in improving the documentation.
The last two updates have DC RTK sync and restart problems. If the satellite drops for a millisecond it throws an error that does not self resolve. So it will just sit there until you do it manually. Unless something else occurs to reset the sync.
Open the RTK details page, then the DC reconnect. Bring up the satellite map and allow it to refresh.
Close details and open the APP controller. Hit the clear errors button. Once the button has cycled move the unit a foot or two. Then close the controller.
This seems to resync everything and allows you to resume the job. At least it allows me to. About 80% of the time. Sometimes after the above I have to open details again, scroll to the bottom and hit the update status button to get it to wake up.
If moving it doesn’t clear the issue, rebooting the core usually does. It’s not possible to access the DC diagnostics page when you’re not home or close to the DC.
If you have need to remote access it, I’d suggest connecting it to a guest network on your wifi and setting up an external access point to that network (VPN or port forwarding). Then you will appear to be .local and be able to access all .local content on that network.
Could probably just ssh I to it as well. But I haven’t messed around with that yet.
I would not recommend attaching the core to your home WiFi. When HaLow is working it can cause communication conflicts and drop outs. HaLow should provide all the remote access and cellular as a backup if you enable it. Delete any WiFi networks to avoid problems.
Also for connection to the data center, that’s Bluetooth only.
