Yesterday, in the middle of a work plan, the map positioning shifted by about two meters. I had something similar happen when an antenna mount on the Core broke, so I was thinking “oh no, not again…”
Antennae all looked fine, sonI thought I’d recalibrate everything by reinstalling/reinitializing the Data Center. That’s when things got weird.
Every time I get to the stage where it assesses GNSS signal strength/CNR, the Data Center reboots: big rainbow light show on the status light. I try again, it does it again. I’ve even attempted short and long POE power cycling to no avail.
I’ve switched to NetRTK positioning for now, and between that and some map drift correct I appear to have everything on the map aligned.
Ticket submitted this morning. Still waiting for the autoresponse to give me a ticket number. I’m a little concerned about the apparent support backlog I keep hearing about (which is probably worse after the security issues).
They have a ton of people trying to work the back log down as quickly as possible. You should be good on NetRTK for now. If the HaLow still works on your DC or if you have WiFi throughout your property. If not, keep an eye on the cellular usage as it will hit its cap and shut off.
I’m running a test mow now. So far so good. I’ve kept the cellular option off as the HaLow should have enough coverage.
Still, I’ll want to restore full DC function. DC mediated RTK is still supposed to be the most accurate/reliable positioning system, correct?
There will be slightly less delay/latency and in theory would be more accurate because of this. It will also survive an internet outage. NetRTK needs internet for it to work. However, I have been using it for a really long time and noticed no issues with the accuracy even with slightly higher latency. The only thing to consider is that for non kickstarter backers it is a subscription after 90 days. No pricing information released yet on that.
Subscription? Oof. Now I really want my DC up and running again… 
Hi there, please rest assured that our support team will do their best to help resolve the issue as soon as possible.
If you need any assistance along the way, feel free to share your ticket number here, and I’ll be happy to help follow up on your case.
Ticket #195801 opened.
“At this point, I am escalating your concern to our Senior Technical Team for further investigation and assistance. They will review the issue in detail and assist you further directly within the same email thread.”
Interestingly, the Yarbo mowed well over the weekend. This was all with NetRTK instead of DC positioning, since I still think the DC is malfunctioning.
However, when I launched it from the dock just now it initiated normally, but then the mapshifted by a couple of meters as it was heading to the start point of the plan. Yarbo is now reporting its position north and slightly west of where it actually is.
This is with NetRTK and not DC positioning, which makes me wonder if the Core is misbehaving – I’ve now seen map shifts like this with both positioning paradigms.
I’ll see if map drift correction helps once I’m able to get the Yarbo back to the dock. That’ll require some on-site, in-person, fiddling.
I looked at the map 20 minutes later and everything had returned more or less to normal. The Core was even able to guide itself to the dock.
So, why is my map moving in the first place?
Is the map moving or the cores relationship and location on the map? If GPS is poor (not green) then it could definitely show a different location on the map that doesn’t jive with reality.
They have confirmed that the DC is likely damaged. A new one should be on its way shortly. Fingers crossed that does the trick.