Just got my new Core + Mower Pro and the unit refuses to lock onto GPS.
Been litigating this issue with @bryan.wheeler and others in the thread below, but nothing works and no GPS lock has resulted.
I have a case number of 204874 open with support. Can someone please take a look at this as currently have a brand new $6,000 paper weight.
Hi there,
I completely understand your frustration, especially when you’re eager to use a brand-new machine and it won’t even acquire a GPS lock.
I’ve checked your support ticket (#204874). We are currently working through a backlog of support tickets, which has unfortunately resulted in slower response times than usual.
That said, I’ve already asked our team to review your case as soon as possible. We understand that your Yarbo is currently unusable, and we want to get to the root cause of the issue as quickly as we can.
We sincerely apologize for the inconvenience and appreciate your patience while our team investigates this further.
Here is the email response I got. Hopefully at some point today the mower will just start mowing on its own 
I have personally checked with our engineers, and they confirmed that the issue you are experiencing (the Core not connecting to GPS) is caused by a firmware problem. They have already taken action, and a firmware update will be pushed to your Yarbo within 24 hours. Once the update is applied, your GPS should start working normally.
@Yarbo-Forum What bug is this? The group spent spent a lot of time trying to diagnose this. It would help us all to have a better understanding.
That was an errant “Solution” press on my part, it has not been fixed yet.
That being said Yarbo came back and said there’s a firmware update I need that they’ll push out in the next 24 hours. Apparently there’s firmware that we can’t update by the app.
Will post back when/if I can lock onto GPS.
Curious. Maybe firmware loaded in the GPS module?
Not sure, but I would be interested if you guys know of a way I can tell that Yarbo has pushed the update?
Checking every 5 minutes might be a little counter-productive.
If it’s something other than the main firmware version number. I’m not aware of any way you’d know. Hopefully they would confirm when it’s complete.
There is no way to know except from a ticket update or catching it say ready to work (if it reboots after).
The revision number should be listed regardless. They shouldn’t push a patch without some indication to the end user.
Same issue here. Looking at the diagnostics page everything looks good except connection quality is consistently 0.00. Tried reinstalling/reinitializing positioning service and using both Data Center and NetRTK.
Under RTK section:
Mode: True L2:23 Status:4 Quality: 0.00
Clicking into details all 4 CNR values are 36-40.
HaLow connection is true and signal is -37
Get a ticket opened and post this thread in there for reference. I will say that your DC levels are a little low. Ideally you want over 40. Is your DC out in the wide open with 120 degree clear and unobstructed view of the sky? Perfect time to move it if not.
There could some internal module firmware separate and unrelated to the main firmware. Only a guess.
Exactly. From what was said earlier in the thread, it sounded like they were updating something internal, not the base firmware itself.
I had something similar happen, but in my case they needed to update firmware in the snowblower module.
I hadn’t considered that. In that case there should be a page that displays all the various firmware and revision levels. If they told me that they need to update firmware for X component I would want to be able check that it was actually updated. Not critical but would be nice.
Yep. I was going there next. I believe the cams report their version but there could well be a couple other modules we can’t see.
Having the same issue, my core is consistently seeing 0 satellites even after several reboots. Has been working perfectly before this, suspect a firmware issue
Zero satellites I think is a different issue. Still possibly firmware related but a few have been RTK antennas that have gone bad. What does your DC scatterplot look like? Tap the yellow details under RTK in diagnostics.
DC scatterplot looks great, but rover shows 0 satellites
What are your CNR values out of curiosity? Do you see any satellites on L2 or total satellites? Or both are blank? Mind posting your diagnostics and scatterplot?