# Navigator/BlueOS NMEA GPS not working **URL:** \ **Category:** Blue Robotics Software\ **Tags:** ardusub, positioning, navigator\ **Created:** [July 20, 2022, 2:00pm UTC](https://discuss.bluerobotics.com/t/navigator-blueos-nmea-gps-not-working/12566 "2022-07-20T14:00:51Z")\ **Posts on this page:** 11\ **Page:** 1
**Author:** ![mark](https://avatars.discourse-cdn.com/v4/letter/m/e9c0ed/32.png) [@mark](https://discuss.bluerobotics.com/u/mark)\ **Post date:** [July 20, 2022, 2:00pm UTC](https://discuss.bluerobotics.com/t/navigator-blueos-nmea-gps-not-working/12566/1 "2022-07-20T14:00:51Z")
Eliot, I just got my new navigator. I am upgrading from an mRo/PI 3B. Previously, I sent USBL GPGGA to the vehicle via UDP:::27000, This does not appear to work. So I tried creating an injector, with the default values UDP, 27000, 220 I am getting no GPS lock on the UI. Any thoughts? Mark Kozikowski ---
**Author:** ![EliotBR](https://sea1.discourse-cdn.com/flex019/user_avatar/discuss.bluerobotics.com/eliotbr/32/6937_2.png) [@EliotBR](https://discuss.bluerobotics.com/u/EliotBR)\ **Post date:** [July 20, 2022, 9:14pm UTC](https://discuss.bluerobotics.com/t/navigator-blueos-nmea-gps-not-working/12566/2 "2022-07-20T21:14:13Z")
Hi @mark, 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? Also, > [@williangalvani](#): > > make sure you have `GPS_TYPE` set to Mavlink which you can confirm/set from the [Parameters page](https://www.ardusub.com/reference/ardusub/parameters-page.html) in QGroundControl. ---
**Author:** ![mark](https://avatars.discourse-cdn.com/v4/letter/m/e9c0ed/32.png) [@mark](https://discuss.bluerobotics.com/u/mark)\ **Post date:** [July 21, 2022, 12:57pm UTC](https://discuss.bluerobotics.com/t/navigator-blueos-nmea-gps-not-working/12566/3 "2022-07-21T12:57:01Z")
Eliot, 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? Mark ---
**Author:** ![EliotBR](https://sea1.discourse-cdn.com/flex019/user_avatar/discuss.bluerobotics.com/eliotbr/32/6937_2.png) [@EliotBR](https://discuss.bluerobotics.com/u/EliotBR)\ **Post date:** [July 22, 2022, 2:08am UTC](https://discuss.bluerobotics.com/t/navigator-blueos-nmea-gps-not-working/12566/4 "2022-07-22T02:08:40Z")
> [@mark](#): > > This setup works with the mRo/Pi setup, but seems to be falling on deaf hardware with the navigator. > Any logging I can check? The logs for the NMEA injector can be found using the [File Browser](https://docs.bluerobotics.com/ardusub-zola/software/onboard/BlueOS-1.0/advanced-usage/#file-browser) (in [Pirate Mode](https://docs.bluerobotics.com/ardusub-zola/software/onboard/BlueOS-1.0/advanced-usage/#pirate-mode)), at `root/var/logs/blueos/services/nmea-injector` (here’s [a direct link](http://blueos.local:7777/file-browser/files/var/logs/blueos/services/nmea-injector/), if you’ve got your system on and connected) 🙂 ---
**Author:** ![CUIS](https://sea1.discourse-cdn.com/flex019/user_avatar/discuss.bluerobotics.com/cuis/32/6711_2.png) [@CUIS](https://discuss.bluerobotics.com/u/CUIS)\ **Post date:** [June 24, 2022, 2:26pm UTC](https://discuss.bluerobotics.com/t/navigator-blueos-nmea-gps-not-working/12566/5 "2022-06-24T14:26:47Z")
With the Pikhawk I used the nmea injector to send Cerulean GPS data to the ROV, but since upgrading to the Navigator the ROV doesn’t seem to be using the nmea data ---
**Author:** ![EliotBR](https://sea1.discourse-cdn.com/flex019/user_avatar/discuss.bluerobotics.com/eliotbr/32/6937_2.png) [@EliotBR](https://discuss.bluerobotics.com/u/EliotBR)\ **Post date:** [June 28, 2022, 4:40am UTC](https://discuss.bluerobotics.com/t/navigator-blueos-nmea-gps-not-working/12566/6 "2022-06-28T04:40:28Z")
How are you attempting to send the NMEA data? It seems that currently it’s necessary to [configure a relevant socket](https://docs.bluerobotics.com/ardusub-zola/software/onboard/BlueOS-1.0/advanced-usage/#nmea-injector) on every boot (that has apparently [been made persistent](https://github.com/bluerobotics/BlueOS-docker/issues/708) in the 1.1-beta releases) ---
**Author:** ![CUIS](https://sea1.discourse-cdn.com/flex019/user_avatar/discuss.bluerobotics.com/cuis/32/6711_2.png) [@CUIS](https://discuss.bluerobotics.com/u/CUIS)\ **Post date:** [August 2, 2022, 11:55pm UTC](https://discuss.bluerobotics.com/t/navigator-blueos-nmea-gps-not-working/12566/7 "2022-08-02T23:55:45Z")
> [@New Product: The Navigator Flight Controller and BlueOS!](https://discuss.bluerobotics.com/t/new-product-the-navigator-flight-controller-and-blueos/12231/19): > > Glad it’s mostly working well 🙂 > Which part of the NMEA injector is not working as expected? [The instructions I used from cerulean](https://forum.ceruleansonar.com/t/cerulean-sonar-blueos-docker/165/2) (quoted below) worked with the Pixhawk but when I upgraded to the Navigator they didn’t work. > [@NickNotham](#): > > If you enable pirate mode (in the gear icon in the left hamburger menu), you can go to the [NMEA Injector](http://blueos.local/tools/nmea-injector) and create a new socket on the default port of 27000. Then DVL or ROVL (via Cerulean Tracker) should be able to send $GPRMC strings to the ROV. > > These sockets are not persistent across a reboot. You can manually re-create the socket on each boot. Or you can automate it with the API. I did it with `crontab -e`. > > Go to the bottom of the file, and add this line: > `* * * * * curl -X 'POST' 'http://0.0.0.0:2748/v1.0/socks' -H 'accept: application/json' -H 'Content-Type: application/json' -d '{"kind": "UDP","port": 27000,"component_id": 220}'` > > This command will run once per minute. It’s okay that it runs repeatedly, the API will simply reject the request because the port is in use. ---
**Author:** ![EliotBR](https://sea1.discourse-cdn.com/flex019/user_avatar/discuss.bluerobotics.com/eliotbr/32/6937_2.png) [@EliotBR](https://discuss.bluerobotics.com/u/EliotBR)\ **Post date:** [August 5, 2022, 8:11am UTC](https://discuss.bluerobotics.com/t/navigator-blueos-nmea-gps-not-working/12566/8 "2022-08-05T08:11:11Z")
Hi @CUIS, 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. ---
**Author:** ![EliotBR](https://sea1.discourse-cdn.com/flex019/user_avatar/discuss.bluerobotics.com/eliotbr/32/6937_2.png) [@EliotBR](https://discuss.bluerobotics.com/u/EliotBR)\ **Post date:** [August 19, 2022, 6:33am UTC](https://discuss.bluerobotics.com/t/navigator-blueos-nmea-gps-not-working/12566/9 "2022-08-19T06:33:55Z")
@mark / @CUIS, 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 🙂 ---
**Author:** ![CUIS](https://sea1.discourse-cdn.com/flex019/user_avatar/discuss.bluerobotics.com/cuis/32/6711_2.png) [@CUIS](https://discuss.bluerobotics.com/u/CUIS)\ **Post date:** [August 20, 2022, 6:10pm UTC](https://discuss.bluerobotics.com/t/navigator-blueos-nmea-gps-not-working/12566/10 "2022-08-20T18:10:40Z")
> [@EliotBR](#): > > o 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 🙂 HI Eliot, I tried this on both the Stable and beta versions I still cant seem it to accept the NMEA Data ---
**Author:** ![CUIS](https://sea1.discourse-cdn.com/flex019/user_avatar/discuss.bluerobotics.com/cuis/32/6711_2.png) [@CUIS](https://discuss.bluerobotics.com/u/CUIS)\ **Post date:** [August 20, 2022, 6:17pm UTC](https://discuss.bluerobotics.com/t/navigator-blueos-nmea-gps-not-working/12566/11 "2022-08-20T18:17:33Z")
I figured it out I changed the GPS-type to MAV thanks