# NMEA not working in BlueOS 1.2 **URL:** \ **Category:** BlueOS\ **Created:** [January 31, 2024, 10:44pm UTC](https://discuss.bluerobotics.com/t/nmea-not-working-in-blueos-1-2/16002 "2024-01-31T22:44:38Z")\ **Posts on this page:** 10\ **Page:** 1
**Author:** ![gcelec](https://sea1.discourse-cdn.com/flex019/user_avatar/discuss.bluerobotics.com/gcelec/32/2038_2.png) [@gcelec](https://discuss.bluerobotics.com/u/gcelec)\ **Post date:** [January 31, 2024, 10:44pm UTC](https://discuss.bluerobotics.com/t/nmea-not-working-in-blueos-1-2/16002/1 "2024-01-31T22:44:38Z")
Hi @EliotBR. I’m trying use NMEA Injector to add a New NMEA Socket but when I CREATE it, nothing happens. I’m sure if I’m doing something wrong or if the version of BlueOS I’m using: BlueOS Version: [heads/ping-fix-attempt-0-gafacf496](https://github.com/bluerobotics/blueos-docker/tree/afacf496)Bootstrap Version: 1.1.1Build: 1/29/2024, 12:19:51 PMBy [Blue Robotics](https://bluerobotics.com/) ![image](https://us1.discourse-cdn.com/flex019/uploads/bluerobotics/original/2X/1/1a24e34f75e931151220117044b1f0515e4c772c.png) ---
**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:** [February 12, 2024, 12:37pm UTC](https://discuss.bluerobotics.com/t/nmea-not-working-in-blueos-1-2/16002/2 "2024-02-12T12:37:52Z")
Hi @gcelec, We’ve confirmed that [this is a consistent issue](https://github.com/bluerobotics/BlueOS/issues/2363) in the `master` branch of BlueOS (and I believe in some of the 1.2.0 beta versions as well), and since my `ping-fix-attempt` image was created from `master` that explains why that bug is also present there. Note that the fix I implemented has been merged into BlueOS master, so you should be able to switch back to the `bluerobotics` dockerhub base instead of using mine (`esalexander`), but the NMEA issue will still be present until we’ve managed to track it down and resolve it. ---
**Author:** ![gcelec](https://sea1.discourse-cdn.com/flex019/user_avatar/discuss.bluerobotics.com/gcelec/32/2038_2.png) [@gcelec](https://discuss.bluerobotics.com/u/gcelec)\ **Post date:** [March 9, 2024, 9:31pm UTC](https://discuss.bluerobotics.com/t/nmea-not-working-in-blueos-1-2/16002/3 "2024-03-09T21:31:40Z")
Hi Eliot, I’ve set up the NMEA injector using BlueOS 1.2.0-beta8. I can see the data string coming into 220 GPS\_INPUT but it’s not being display on the overlay. Is this still an ongoing issue, or is it something that can be fixed? ![image](https://us1.discourse-cdn.com/flex019/uploads/bluerobotics/original/2X/7/7a0b2e3eefa43734be779532125a41c8af18609b.png) ![image](https://us1.discourse-cdn.com/flex019/uploads/bluerobotics/original/2X/b/b80214586440a060e7651667c4720c6c2ed5d0f6.png) ---
**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:** [March 11, 2024, 6:27am UTC](https://discuss.bluerobotics.com/t/nmea-not-working-in-blueos-1-2/16002/4 "2024-03-11T06:27:56Z")
The GitHub issue is marked as solved, and [the relevant commit](https://github.com/bluerobotics/BlueOS/commit/32e06925c93cfce40058b0540542d5bd3104a901) is apparently present since `1.2.0-beta.6`. If creating NMEA sockets is working for you (which it must be if QGC is receiving the messages) then the original issue is fixed. I unfortunately have very little experience with the positioning aspects of QGC, but I’d assume if the numbers aren’t showing up then either 1. your latitude and longitude telemetry display variables are configured to the wrong source (e.g. `Gps2` instead of `Gps`), 2. there’s something else required to show the positions (e.g. configuring a global origin, although I believe that’s only relevant for local positioning), or 3. QGC’s telemetry widget may filter out messages that don’t come from the vehicle, but that seems unlikely given [220 is the official GPS component ID](http://mavlink.io/en/messages/common.html#MAV_COMP_ID_GPS) I expect @williangalvani or @tony-white may have some more relevant insight. ---
**Author:** ![williangalvani](https://avatars.discourse-cdn.com/v4/letter/w/6f9a4e/32.png) [@williangalvani](https://discuss.bluerobotics.com/u/williangalvani)\ **Post date:** [March 15, 2024, 6:14pm UTC](https://discuss.bluerobotics.com/t/nmea-not-working-in-blueos-1-2/16002/5 "2024-03-15T18:14:41Z")
Hi @gcelec , Have you tried setting the Parameter `GPS_TYPE` to 14 (MAVLink)? If that solves the issue, we need to add a warning in the NMEA Injector page if that parameter is not set properly. ---
**Author:** ![gcelec](https://sea1.discourse-cdn.com/flex019/user_avatar/discuss.bluerobotics.com/gcelec/32/2038_2.png) [@gcelec](https://discuss.bluerobotics.com/u/gcelec)\ **Post date:** [April 4, 2024, 12:41pm UTC](https://discuss.bluerobotics.com/t/nmea-not-working-in-blueos-1-2/16002/6 "2024-04-04T12:41:24Z")
Hi @williangalvani, Just getting back to this now. The Parameter `GPS\_TYPE was set to Auto so I changed it to 14 (MAVLink) and now I am getting Lat and Long on the QGC display. Thanks for your help ---
**Author:** ![iSENSYS](https://sea1.discourse-cdn.com/flex019/user_avatar/discuss.bluerobotics.com/isensys/32/3617_2.png) [@iSENSYS](https://discuss.bluerobotics.com/u/iSENSYS)\ **Post date:** [September 4, 2024, 6:06pm UTC](https://discuss.bluerobotics.com/t/nmea-not-working-in-blueos-1-2/16002/7 "2024-09-04T18:06:47Z")
Hi - is your GPS\_TYPE parameter staying on MAVLink after a reboot? We are using an NMEA device and after every reboot we must go in and reset the GPS\_TYPE parameter. Is Blue OS controlling this parameter somehow? ---
**Author:** ![tony-white](https://sea1.discourse-cdn.com/flex019/user_avatar/discuss.bluerobotics.com/tony-white/32/18385_2.png) [@tony-white](https://discuss.bluerobotics.com/u/tony-white)\ **Post date:** [September 4, 2024, 6:14pm UTC](https://discuss.bluerobotics.com/t/nmea-not-working-in-blueos-1-2/16002/8 "2024-09-04T18:14:54Z")
Hi @iSENSYS - Are you using BlueOS 1.3.1 ? ---
**Author:** ![iSENSYS](https://sea1.discourse-cdn.com/flex019/user_avatar/discuss.bluerobotics.com/isensys/32/3617_2.png) [@iSENSYS](https://discuss.bluerobotics.com/u/iSENSYS)\ **Post date:** [September 4, 2024, 6:16pm UTC](https://discuss.bluerobotics.com/t/nmea-not-working-in-blueos-1-2/16002/9 "2024-09-04T18:16:54Z")
Probably - ROV is charging but I’ll check… ---
**Author:** ![iSENSYS](https://sea1.discourse-cdn.com/flex019/user_avatar/discuss.bluerobotics.com/isensys/32/3617_2.png) [@iSENSYS](https://discuss.bluerobotics.com/u/iSENSYS)\ **Post date:** [September 4, 2024, 7:56pm UTC](https://discuss.bluerobotics.com/t/nmea-not-working-in-blueos-1-2/16002/10 "2024-09-04T19:56:19Z")
It was an extension creating the persistent parameter set. Thanks!