Hallo,
I'm using a Raspberry Pi 5 with the SX1262 XXXM LoRaWAN/GNSS HAT from Waveshare.
The GNSS receiver is using /dev/ttyAMA0 serial with 9600 baud
configuration is set to enable GPS, serial and the port
The GPS on the map is then reporting "NMEA checksum mismatch"
I checked that services like chrony are able to use GNSS to sync, so the GNSS hat is working. Chrony is disabled, so there should be no conflicting access to the serial device. "cat /dev/ttyAMA0" also shows that data is flowing
Hallo,
I'm using a Raspberry Pi 5 with the SX1262 XXXM LoRaWAN/GNSS HAT from Waveshare.
The GNSS receiver is using /dev/ttyAMA0 serial with 9600 baud
configuration is set to enable GPS, serial and the port
The GPS on the map is then reporting "NMEA checksum mismatch"
I checked that services like chrony are able to use GNSS to sync, so the GNSS hat is working. Chrony is disabled, so there should be no conflicting access to the serial device. "cat /dev/ttyAMA0" also shows that data is flowing
<!-- github-sync-id:5027456121 -->
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Hallo,
I'm using a Raspberry Pi 5 with the SX1262 XXXM LoRaWAN/GNSS HAT from Waveshare.
The GNSS receiver is using /dev/ttyAMA0 serial with 9600 baud
configuration is set to enable GPS, serial and the port
The GPS on the map is then reporting "NMEA checksum mismatch"
I checked that services like chrony are able to use GNSS to sync, so the GNSS hat is working. Chrony is disabled, so there should be no conflicting access to the serial device. "cat /dev/ttyAMA0" also shows that data is flowing
Works now after update - Thanx !
Great!