I have reduced the boundary area by the max 16 inches. The Yarbo gets stuck when turning around in the flowerbed with mulch. I have tired different turning styles to prevent this as well as put no go zones for the flower beds.
What can I do to prevent the Yarbo from going outside the working area?
Is this on a downhill or in a poor GPS area?
Have you tried adjusting the route angle in that area? This adjustment might help reduce such cases. If it doesn’t solve the issue, please share more detailed information about that area so I can better assist you.
Open area no trees, flat area as well. It went well out of bounds this morning. It is set to change the angle 40 degrees after every mowing.
I see a bunch of no go zones there. Is it possible there is things there that could be blocking gps signals or causing multipath errors? That would be one of the few reasons that it would go out of bounds. Basically a false good signal telling it wrong information due to reflection and or noise. The good news is, they are releasing DR and confidence levels for GPS soon that will identify noise and multipath issues and be able to continue to work for extended periods of times in these conditions.
Do you notice the out of bounds more running certain directions vs others? Perhaps adjust the angle and turn off rotation so that one that doesn’t cause these issues is always used until the new firmware is released.
I assumed the NGZs were added to keep Yarbo in bounds. But that is an assumption on my part.
As Bryan mentioned, are there any factors that might block the GPS signal and cause a multipath effect? If not, please submit a support ticket so our team can check the logs and investigate the root cause.
Noting that should block gps, wide open area with no trees or other obstructions.
I added the no go zones to try and keep Yarbo from going out of bounds, but that hasn’t worked.
Then it’s possible it could be your data center install. Do you have pictures and can you provide a screenshot of the DC diagnostic screen. If you go into diagnostics, there is a yellow details under the RTK section. Two that and connect to your DC. It should show a sky map and CNR values.
We may need to investigate further to determine the root cause. As I suggested earlier, please consider submitting a support ticket so our team can review the logs and identify the issue.
Data center is mounted on side of my single story home. It has good signal. I think I’ll have to open a support ticket.
Your GLONAS is poor and Galileo is borderline. It might be a factor. Support could certainly help here in determining if it is.
What would be ideal values I would be looking for?
If I need to reposition my datacenter I will.
You want to see anything above 40, the higher the better. If you move the DC, keep in mind you will have to remap. Check the DC diagnostics periodically and as long as you have 40 or better most of the time you are good. If not, at least 37 is needed. Anything less is not usable. Not all constellations there are going to give you ideal numbers, Galileo doesn’t show up for me most of the time. But, the others are 37+ 99% of the time. So keep that in mind, it’s location and environmental factors dependent, etc.
