Fix GPS baud rate: RYS352A defaults to 115200, not 9600

The AG3352 GNSS engine in the RYS352A ships at 115200 8N1 per
the datasheet spec table. 9600 was a generic assumption that
would cause the UART to read garbage and never acquire a fix.
This commit is contained in:
Ryan Malloy 2026-02-11 16:06:31 -07:00
parent f218cd468b
commit f2c1eb84d2
2 changed files with 3 additions and 3 deletions

View file

@ -223,7 +223,7 @@ ESP32 GND ──► RYS352A GND
|------------|-----------|----------|
| VCC | 3V3 | 3.3V power (onboard LDO on most breakouts) |
| GND | GND | Ground |
| TX | GPIO5 (UART2 RX) | NMEA sentence output at 9600 baud |
| TX | GPIO5 (UART2 RX) | NMEA sentence output at 115200 baud |
| RX | GPIO6 (UART2 TX) | UBX/NMEA config input (optional) |
| PPS | GPIO7 | 1Hz pulse synchronized to GPS time |
@ -233,7 +233,7 @@ this edge via interrupt (`micros()` timestamp) for correlating satellite events
with sub-microsecond precision relative to the GPS epoch. The module's RTC
battery backup enables warm starts (~5s) after initial cold start fix (~30-60s).
**UART notes:** The RYS352A defaults to 9600 baud NMEA output. The TX line
**UART notes:** The RYS352A defaults to 115200 baud NMEA output. The TX line
(GPIO6) is optional — only needed if you want to send UBX configuration
commands to change update rate, constellation selection, or enable additional
NMEA sentences. The firmware uses TinyGPS++ to parse standard GGA/RMC sentences.