Yep, was considering that but hopeful that now it’s repaired, map drift fix would properly shift it back to square one. I’ll try cloud restore.
Hi there, as Bryan mentioned, the Correct Map Drift function is designed to realign the map with Yarbo’s current real-world position by using the docking station as the reference point. It primarily corrects positional offset by shifting the map to match the actual location.
Now that the antenna issue has been resolved, please try the Correct Map Drift function again and let us know the result.
Thanks for your suggestion. I’ve shared your feedback with our product team for further review.
Sorry to hear about the out-of-boundary issue. I’ve checked our system and see that you already have a ticket for a Core replacement. We hope the replacement Core will provide a better experience once you receive and set it up. Please feel free to keep us updated on the results.
It’s difficult to tell which local basemap is accurate from a registration perspective.
Cloud maps - appears these are not versioned and there’s only one?
The cloud would be the most recent saved local map. Any time you hit save, it writes one to the cloud as well as locally. There should be a date and timestamp on all of them. If you tap on it, it will show you what the map looks like and tell you the date/time at the bottom.
Cloud or local map restore is not a valid solution to my current issue. The current issue is that the map has somehow drifted too far to the North out of bounds. That may have been caused by me doing map drift correction with bad antennas or something totally unrelated. There was no indication or warning that the antennas were bad upon doing map drift correction, which would have been nice. I only initially did map correction to attempt to fix that issue after repairing Yarbo.
But more importantly, the map charging pad/docking location appears to be bang on when Yarbo is parked on it. This was the case for known good antennas and questionable antennas both pre and post map drift. The map always appeared to be accurately georeferenced at the docking station and still does. This is what led me to my question about what the algorithm is a simple shift or more than that…
At this point I think I’ll just wait until the replacement core arrived and go from there. I do fear that I’ll have to remap everything though.
TBH, remapping is probably the safest bet. As much as that sucks.