Got Yarbo, 3 DC issues

Maybe a stupid question at this point, have you tried hard rebooting the rover? i.e. hold the button until it shuts off, pull the battery, wait 5 minutes, reassemble, and power back on?

I did hard reboot yesterday.

Stats with PPVS off

Try the reboot (5 min battery pull). Leave PPVS enabled first. If that doesn’t work, get a ticket started. There’s something tweaked wrong on the core. You can also fire up the DC so you’re not burning through cellular.

I’ve got a ticket open since Saturday. Do appreciate everyone’s ideas and inputs.

Another stupid question… Is there a chance you have your HaLo and BLE antennas on the DC backwards? I noticed that your HaLo reception was at -92. I’ve never seen mine that low, even several hundred feet away through trees.

For reference the shorter one is the BLE antenna and the longer one is HaLo

Looking at the side with the light, BLE is on the right, and HaLo is on the left. i.e. short antenna should be on the right, and long should be on the left.

Should look like this.

Nope, theyre on there right, looks just like yours.

Latest results after a hard reset, same result.

Looks like you switch positioning back to DC?

Yes i did.

And can you complete a DATA CENTER Reinstall? That positioning screen looks like docking station install.

Mmk reinit the DC and then went on to charge station. Same result.

New antennas will arrive tomorrow to rule out one variable.

There is either something wrong with your RTK module in the core or the DC. HaLow is still false, so I’m leaning towards DC, but NetRTK should solve this if it was. So possibly a multifaceted issue. Do you have a ticket opened? You can drop this thread in there so they have more context.

I Do have an open ticket # but no responses yet. I updated the ticket with my SN # and relevant information. It looks like they generated the ticket to my email to Support as it has this thread link already in it (and that’s what I threw into my initial email).

@bryan.wheeler - When you say you’re leaning towards the DC, do you mean the entire unit or just one or more of the antennas?

I am leaning towards the unit itself. Your scatterplot looks beautiful from a GPS perspective. Your HaLow seems like it’s broken. Either on the core or on the DC itself. Your GPS and other stats on the core also look beautiful. But the quality metric is zero. That should be closer to 1 for maximum quality. But it says zero. It should only be zero if PPVS is disabled. It remained zero no matter what you did. So, something is either not right in the RTK/HaLow modules on the core or something with the DC itself. I suspect a few issues potentially. Either way, this needs escalation. Please drop your ticket number here so @Yarbo-Forum can help to try and articulate the details and speed this along.

It’s also weird to be seeing it say false when the signal is -10… It’s 50/50 whether its the core or the DC. The transmitter is working or else there’d be no signal to see, and the receiver in the core needs to be working or there’d be no way to see that there is a signal… So it’s like the computer at one end or the other isn’t working…

Switching to NetRTK removed the DC variable and nothing changed = Core

Exactly. The DC was removed from the equasion by using NetRTK and cellular. Still, the issue persisted.

It’s gotta be a problem with the Core.

Seems reasonable. Just not sure there isn’t some other issue going on. Someone else had a similar issue with a new unit and it was the DC. Can’t remember if that was on here or on FB. May have been on FB. So that’s why I’m leaning towards both.

@slw2206 I would switch back to NetRTK for positioning. Connect your rover to WiFi and make sure cellular is toggled on. If HaLow is still false and you don’t have GPS still, there is definitely something wrong with the core side. Hopefully it’s just a software glitch.

Ya even with those settings its not getting GPS.

I guess the question now is, how do I get customer service to actually respond.

Unfortunately they are really backed up, but @Yarbo-Forum can possibly help speed it along providing some context to the FSE’s. If you share your ticket number here, that could be helpful.

What can help speed the process up. Give pre consent for remote troubleshooting. Document all troubleshooting you’ve done in the ticket. Again, this thread link is a good start, assuming they actually will read it. But a quick summary of what you did already may help them vs this thread in that regard.