-
Notifications
You must be signed in to change notification settings - Fork 495
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
ATGM336H Not Encoding #137
Comments
Hi Wayne—
TinyGPSPlus looks at G*GGA and G*RMC sentences by default. Can you possible email some sample NMEA? (sundial @ sundial.com) I bet I can figure it out and make fix if needed.
Interested to hear about your balloon tracker! We are flying a balloon ourselves for the 8 April eclipse.
Mikal
|
The ATGM336H has many attractive qualities, but playing well with TinyGPSPlus is not one of them. With Mikal's help we determined it decoded the $GNGGA fine but always reported invalid. I added a custom TinyGPSCustom ATGMfix(gps, "GNGGA", 6); // $GNGGA sentence, 6th element to pluck out the fix quality and decided if it was valid. Works fine and we are ready to launch balloons again. Issue closed. |
I also use this GPS module, can you explain it in more detail? Mine cannot be parsed using the hardware serial port, but the software serial port can parse NMEA. |
I have never had much luck using TinyGPSplus with anything other than true
Arduino's.
I could never get it to output results with the 336 chip using TinyGPSplus but
could get it to parse using the new custom field commands feature.
Try asking ChatGPS to "code a NMEA parser for the ATGM336H GPS module". It
produced marvelous code that worked perfectly, but you do have to convert the
fields from text to useful numbers.
Good luck
…------ Original Message ------
Received: Thu, 04 Apr 2024 07:48:01 AM EDT
From: guming56 ***@***.***>
To: mikalhart/TinyGPSPlus ***@***.***>Cc: WaynePauly
***@***.***>, Author ***@***.***>
Subject: Re: [mikalhart/TinyGPSPlus] ATGM336H Not Encoding (Issue #137)
I also use this GPS module, can you explain it in more detail? Mine cannot be
parsed using the hardware serial port, but the software serial port can parse
NMEA.
--
Reply to this email directly or view it on GitHub:
#137 (comment)
You are receiving this because you authored the thread.
Message ID: ***@***.***>
|
We switched from the NEO-6M to the ATGM336H in our balloon trackers and the software won't encode a fix.
I tried the Device Example with no results either, but the raw NMEA sentences look normal to me and indicate a fix.
Any known issues using the 336H with TinyGPSPlus or suggestions? Which sentence does the library try to parse?
Wayne
The text was updated successfully, but these errors were encountered: