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

ATGM336H Not Encoding #137

Open
WaynePauly opened this issue Mar 19, 2024 · 4 comments
Open

ATGM336H Not Encoding #137

WaynePauly opened this issue Mar 19, 2024 · 4 comments

Comments

@WaynePauly
Copy link

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

@mikalhart
Copy link
Owner

mikalhart commented Mar 19, 2024 via email

@WaynePauly
Copy link
Author

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.

@guming56
Copy link

guming56 commented Apr 4, 2024

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.

@WaynePauly
Copy link
Author

WaynePauly commented Apr 4, 2024 via email

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

3 participants