ATGM336H Not Encoding

[WaynePauly]

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]

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

[WaynePauly]

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]

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]

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: ***@***.***>

[zuckerme]

My ATGM336H has no problems communicating with TinyGPSPlus on a Raspberry Pi Pico (RP2040). I encountered erratic speed (race?) issues with encode(), but reducing default output to RMC and GGA sentences alone helps (factory default spits out 8 standard NMEA sentences, with redundant content, plus at least one proprietary sentence). Increasing serial output to 115200 baud from default 9600 also helps. Here are some useful ATGM336H command strings:

$PCAS10,3*1F<cr><lf>    factory reset, cold restart (loses fix memory)
$PCAS01,5*19<cr><lf> 	 115200 baud
$PCAS03,1,0,0,0,1,0,0,0,0,0,,,0,0*02<cr><lf>  GNGGA and GNRMC sentences only