I’m trying to get a MT3339 based GPS working with Ardupilot, specifically a Adafruit Ultimate GPS Breakout V3 on a Matek F405 Wing V2 board.
I verified, that the GPS is connected correctly on Serial3 by using the passthrough feature and I can see the NMEA messages in Terminal.
The issue is that even if the GPS has a 3D Fix indicated by LED, Ardupilot’s Pre-Arm check fails
with “AHRS - Waiting for Home”, “EKS3 not started”. Indicator on HUD is “GPS: No GPS”.
Serial Port is configured as GPS with correct baudrate of 9600. I tried GPS_TYPE as “Auto”, “NMEA”, “HemisphereNMEA” and I was not able to get it to the point that I would see some “GPS: No Fix” or whatever on HUD.
Summing up my endeavors of the past week.
If NMEA is built-in, I get a 3D FIX with the Adafruit Ultimate GPS, but it does not last long because AHRS / EKF3 regards the GPS as broken due to the 1Hz STANDARD update rate of NMEA.
09.03.2024 07:43:14 : PreArm: GPS 1: Bad fix
09.03.2024 07:43:13 : PreArm: AHRS: Not healthy
09.03.2024 07:43:01 : GPS 1: detected as NMEA at 9600 baud
09.03.2024 07:42:48 : GPS 1: detected as NMEA at 9600 baud
09.03.2024 07:42:42 : PreArm: GPS 1: Bad fix
09.03.2024 07:42:42 : PreArm: AHRS: Not healthy
09.03.2024 07:42:35 : GPS 1: detected as NMEA at 9600 baud
09.03.2024 07:42:22 : GPS 1: detected as NMEA at 9600 baud
09.03.2024 07:42:12 : PreArm: GPS 1: not healthy
MT3339 itself can do much more, but there is no config support in Ardupilot for writing configuraiton to NMEA-type GPS.
The easy way around was to order a holybro micro M10 which is roughly the same size.
We’ll see if that one does any better.
Again summing it up, NMEA-type GPS don’t work with Ardupilot, U-Blox is the de facto standard.