I’m using the Navigator Flight Controller with a Blue Robotics GPS module and I’m consistently seeing 0 satellites in QGroundControl—even when the system is outdoors with a clear view of the sky. The GPS module powers on and the LED blinks (yellow), indicating it’s receiving power but not acquiring a fix.
Here’s what I’ve tried so far:
Verified wiring: TX and RX are crossed properly, and 5V and GND are connected.
Power: GPS LED is blinking, so it’s powered.
Location: Tested in open sky for over 10 minutes with no change.
Flight stack: ArduPilot Rover and BlueOS latest firmware. Also tried previous firmware versions.
Despite this, QGroundControl continues to show “AHRS: Waiting for home” and “0 satellites.” EKF3 doesn’t initialize, and GPS appears in the MAVLink inspector, but shows “GPS_FIX_TYPE_NO_GPS”.
Any suggestions on additional troubleshooting steps or things I may have missed would be greatly appreciated. I am lost at this point
Hi @kenbyrrrd -
Welcome to the forums!
Blue Robotics does not make a GPS - are you referring to one used in a BlueBoat? Is that the system you’re working with?
We’ve had some (rare) issues with GPS like this - often when they are returned they mysteriously work just fine! If you’re using this with a BlueBoat, please reach out via the contact form to discuss a replacement, including your order #.
Thanks for the reply. I was just about to update my post.
Yes I am referring to the one in the BlueBoat.
I was able to resolve the issue, although I wouldnt call it a true fix. I have two other unused BlueBoats. I simply went through each of their settings in BlueOS and made those changes to the BlueBoat with issues. Now the system can pick up satellites.
I updated Qgroundcontrol and to the new BlueOS, which is when these issues occurred. I had never mnaually edited vehicle settings in BlueOS until today.
Hi @kenbyrrrd -
That’s very interesting! For future reference, you could have downloaded the parameters from another boat, and loaded them on that boat, and seen what changes you were making (from within BlueOS, Autopilot Parameters.) Then we would understand what may have been changed…