Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

GN*** sentences not recognized #4

Open
MaelysB opened this issue Jul 3, 2018 · 4 comments
Open

GN*** sentences not recognized #4

MaelysB opened this issue Jul 3, 2018 · 4 comments

Comments

@MaelysB
Copy link

MaelysB commented Jul 3, 2018

Hello,

Even though this is not really a big issue, I would like to point out that the code is not suitable for GN*** or GL*** sentences.

I tried to adapt it, and make it work for all prefixes of NMEA sentences but I did not succeed.

Has anyone made an attempt at this before ?

Thank you.

@MaelysB MaelysB changed the title This NMEA library recognize GNGGA sentences GN*** sentences not recognized Jul 3, 2018
@octavmatu
Copy link

octavmatu commented Apr 24, 2019

First of all, I really like the implementation using C++11 features! Thanks to the devs and kudos for sharing this!

Now, main point - I have also ran into this issue.

Basically, with a new uBlox GNSS, the library outputs constant (lat,lon)=(0,0), although sentences are marked as valid (as in, they pass the checksum test)

Any way to fix/bypass the issue ???

@octavmatu
Copy link

Looking through the implementation, my impression is that a quick fix to the issue consists in adding sentence handlers, as in the following manner
_parser.setSentenceHandler("GNGGA", [this](const NMEASentence &nmea) { this->read_GPGGA(nmea); });
..and similar for GNRMC, GNVTG, etc.

Can anyone please confirm?

@ckgt
Copy link
Owner

ckgt commented May 3, 2019

Thanks octavmatu. You are correct, you can add a sentence overload by using setSentenceHandler.

Just make sure you read the documentation for that sentence so you read the parameters correctly and update the fix object properly.

I remember someone adding GN* sentences in a fork. I'll have to find that and do a pull.

@jaxcorona
Copy link

I apologize for my ignorance but I had a question about how exactly this code works. I am new to Github and using the gps dongle so I am just trying to make sense of everything.

From my understanding is that this code does not read directly from a usb gps dongle rather from a string that the user has to input. Is this correct? If so, I am still confused about syntax. When I run demo_simple I receive a message that says "No satellite info in almanac." Assuming the user has to input a string in the form "GNGAA...." when and where would I input that string?

If this code does accept info straight from the gps dongle, how would I make that work? Where would I have to specify the port the dongle is connected to?

If this code does not accept into straight from a gps dongle, can anyone recommend a C script that reads from the gps dongle? or does anyone have any suggestions as to how I should modify the code to do this?

Thank you in advance.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants