Hi all,
My app shows that I have map drift.
When I push the button to resolve it I get the message 'Yarbo is not charging or rtk status is not 4".
Yarbo in on the charging pad and charged to a 100%.
I have a good signal, it is positioned under the carport.
Not sure what to do.
Any suggestions?
Thank you
1 Like
Under a carport, your Yarbo may not receive good GPS signal, that may be why you can’t correct the map drift at this time.
2 Likes
As B-Mod mentioned, under a carport is not the optimal location and the reason you have poor signal and cannot correct for the map drift. I would reach out to support to see if they can assist and the steps they would recommend to potentially correct this. Most likely they are going to tell you to relocate your docking station and possibly have to remap.
1 Like
Thank you. I did restart my system and now the notification is gone. But I will take the advice into account.
Would like to avoid that I have to remap although 
3 Likes
@yarbo-forum Hope you got yours going. I got a new core as well. I was able to get the Map Transferred to the new core. I keep getting Map Drift error. So Power Down DC, Core and the error went away. Sent him out to start working. Well now 50% in the job. Lower end of the plan he’s doing his normal. Now that he’s 50% complete in open area of the yard nothing but clear sky. Top end he’s making a funnel to the far end, and nothing at the bottom end. 4” overlap slow speed, no hills, or slope. Any ideas? Letting him charge back up, then going to power DC and Core again resume at 50%
So I did this. Well he’s not see NGZ. He’s doing smart turn no the side about 50Yards on the good end. On the bad end is where the problem is still after. He does not a smart turn but like a tear drop turn, missing everything in the shape of a drop, stips about a foot wide on this end, and narrowing on the good end looking normal. The charging station, and DC haven’t moved. But just for giggles, I did a reinstall DC, and Charging pad. So looking at the map after the old charging pad was about 6 feet off on the map. Even though it had not been moved. Thinking OK well he sees the new location, maybe this will get him back on track. Nope same issues as before. I’m seeing a remap. On a large track of land, with all the probems I’ve had just getting to here. I really think the map transfer didn’t work. It said it did. They said it did. Something is way off.
Just posted in the other post, try a map drift correction. It should always be done after a map transfer.
2 Likes
@Yarbo-Forum @marco @bryan.wheeler Update. Well I wish it would have been an easy fix. He’s still about 6 feet off. So I deleted, and doing a remap now. Or should I say trying. But, I looked at the numbers again. I do see a smaller amount of what was happening before with the latency bouncing up more than the other core. Before they fixed it remote so it would stay stable. Now it stays at 1 some of the time. But is climbing to 21, then back to 1. After the fix they did, it was staying calm. Don’t know if the new core or what. Biggest issue is not being able to remap. So I got clear sky about 1/3 of an acre done. Many stops, and goes. But finally after 2 hours it’s done. But trying the other with anything in the area, tree, bush, building, car, flea, ant, dog, fly, it’s so unstable after 5 tries in the area, clockwise, and counter clockwise. No Go! This unstable GPS is not a happening thing. So I’ll reach out to them Once again, and see if they can see what happened with the transfer. Ticket numbers #91428,#113257,#109358
1 Like
I’m surprised you were able to map at all if your latency exceeds 15. Honestly the maps could be sketchy because of it and that could explain some things. Did you swap the DC out too or did your core not come with a new one?
1 Like
I didn’t swap it out. It’s mounted, on a long pole on the side of the house. Level, supports. Nice mount. It’s slow to start climbing. Nowhere as high, or as fast as before climbing. Just hoping they can take a look at it. But the transfer was way off. Explains why he was tearing things up, never paying attention to NGZ. It wasn’t only the Charging Pad. I did the spots in the yard maps like you said. Everyplace was off. So I did the DC and Charging Pad from new, just like when I did when I got it. The best signal strength on both. I’ve been watching him mow the one section I did get mapped. Seems to be do things normally. Flips to 4G sometimes. But has been mowing.
2 Likes
@Yarbo-Forum @marco @bryan.wheeler I just got a reply back from support. They don’t see any rise. So I guess I’m the only one seeing it. Go from 1 to 17 climbing. I told them when it rises, so does the HDop.
So I have seen if your connection to the core through WiFi, BT, or Cellular is poor that the app can show false readings like a latency increase and loss of GPS. Have you tried disabling BT and WiFi on your phone when you see this or are mapping? I typically always do this when I am out in the yard controlling it or mapping.
2 Likes
@Yarbo-Forum @marco @bryan.wheeler Connection isn’t connected to WiFi. Never has been. I forgot it from day one just like you said when I first got it, three cores ago. BT when I use him in the yard, and no more than 2 feet away when trying to map. Cellular 5 bars all the time. I can see my cell tower, it’s about 1 1/2 miles away. I have tried disable BT while watching him in open yard, no obstructions. Same when he’s on charging pad. Numbers show the same. Again No WiFi is connected. After giving them the same thing, and the numbers we spoke about. After I followed up with the email above. I got this a couple of hours later.
Their response doesn’t make sense to me.
To clarify, I was talking about disabling WiFi and Bluetooth directly on your phone and not WiFi on the rover.
Hopefully you see improvements after the firmware update. You going to try the map migration again?
1 Like
I can disable on both if you think it would help. Thoughts about trying migration again?
So right now with the suggestions you made. Sitting in open sky, no obstructions. L2 14, Status 4, Adjust 0, Heading 1, Sats 23, Data Latency 1, HDop below 1. But when Data Latency starts climbing HDop goes to 1.7, DC connection 3, HaLow -48
Does your DC stay at 3 or does it alternate between 2 and 3? Alternating is normal. Steady 3 is not.
regarding the migration, manually save your current maps that you made and they can try again if you’re up for it. Not sure if it will change anything but if you’ve done a lot of remapping and it’s operating properly with those maps, then remap is the best way honestly. Especially when the new firmware drops. It will truly help you there.
2 Likes
@yarbo-forum @marco @bryan @ken Well update to email. Their response doesn’t make sense to me either. We’re now back to the router has them blocked once again. So once AGAIN. This is the exact same thing that happened before, when they had to do a remote fix. Same issues. I’ve checked once again. No it’s not blocked. I checked again. I really see where it’s listed to try to connect as well as the all addresses are in my router, and has been trying to connect to Yarbo’s end. With no blocks, or blacklist. It has been allowed, I checked once again. I then Disabled the IP filter with no change to this helping anything. This didn’t change anything. Once again I asked them to please see if they have any notes to the closed ticket #91428. This is how they did the remote fix before. Same circle with the same addresses to check once again.
“Could you please add the following three MAC addresses to your router’s whitelist and check if this resolves the issue?
-
DC: 70:19:88:8e:1b:5a
-
hg0: 1e:9e:14:5f:a0:a8
-
wlan0: 78:22:88:b0:02:4a
If the issue persists after this, please don’t hesitate to contact us again.”
Hi there—sorry for the wait on a solution. Regarding Ticket #114007, your case has been escalated to our R&D team for a remote fix (as we did last time), and this process can take a bit of time. Please rest assured we understand your need for a quick resolution, and we truly appreciate your patience and understanding.
2 Likes
@Yarbo-Forum @marco We can’t do what we did to get this working. This has happened before. Do we have any notes left on what it took to fix like before?
1 Like
Hi there. Although the behavior looks similar, the root cause may vary. I’ll share the past handling records with the engineer on your current ticket so they can review and reference the previous remote fix.
3 Likes
Thanks @marco. I appreciate you helping pass along the previous notes. Thanks again to everyone helping correct the issues. Remapping everything again will be a choir. Just ready to get him off the charging pad and back to work. He’s been sitting almost two weeks now. Thanks again.
1 Like