Hi all. I’ve been struggling for quite a while now trying to get the sparkfun ZED-F9P board to work with a pixhawk 2.4.8 as a rover. I’m using an esp32 and the sparkfun github library to pull pointperfect corrections and feed them to the gps board which seems to be doing fine. After a long time troubleshooting in UCenter, i was finally able to get the pixhawk to even detect the gps, but now I see it consistently connects within the messages tab in mission planner. (see photo). This is problematic, as when viewing the graphical interface, it will read 3D dgps, no fix, no gps, and continues cycling - never holding a steady gps signal. I’ve tried outdoors with the same error as well as changing baud rates which surprisingly did not change the messages. they still read 38400 baud rate gps detected even after ensuring in ucenter that they were appropriately changed (and saved) as well as configured in mission planner itself. any help would be greatly appreciated, I’ve run out of ideas.
Can you confirm the pixhawk is actually altering the baud values another way? (with a different board, sensor, BT device, phone, etc?)
Just going off your photo I’d presume it is something errant setting with pixhawk, it is re-detecting after 13 seconds and and dropping (do the pre-ams occur without the f9p being detected, or is the f9p being detected triggering the pre-am?)
You could also confirm the f9p is working by hooking up with a laptop or what-have-you by itself and confirm it’s behaving to rule it out as a suspect