I brought this up internally and was told if you’re getting “no GPS lock” then ArduPilot is saying there’s a connected GPS with no lock, so perhaps the issue is with where/how you’re testing the USBL or something?
Thank you for the prompt response.
After it was mentioned to check the parameters for GPS_TYPE, I sent it to MAV. This made no change.
As far as having a gps device connected, hardware includes only the R-PI and Navigator, and I am feeding NMEA GGA messages via UDP:27000, from a simulator.
This setup works with the mRo/Pi setup, but seems to be falling on deaf hardware with the navigator.
Any logging I can check?
I’ve moved your NMEA-related messages here, because they’re seemingly on the same topic.
I’m not sure what’s going on here, but I’ve spoken to the software team and they will hopefully be testing the Navigator + BlueOS NMEA Injector functionality next week, to see if they can replicate the issues you and @mark have been running into.
Was this the case with BlueOS 1.0.1 stable, or one of the beta images? We added a few different fixes and tests in BlueOS 1.1.0-beta.1 to beta.3. Assuming you were testing with an earlier version, can you confirm whether this issue is still present for you in a recent beta release?
You’ll need to turn on Pirate Mode to access the beta releases, but once you’ve installed one you can easily roll back to stable if you’d prefer to stay on a stable release for your normal operation