Cannot use GPS_INPUT as GPS source (PIXHAWK 6X)

Hardware Other Hardware
1

Hi,

I’m trying to send simulated mavlink gps messages (using a Companion Computer) through GPS2 Port using Mavlink Protocol.

I can see the messages on Mavlink inspector (when connected to pixhawk on MP) as shown in the image and it looks ok, but I can’t get the pixhawk to use as gps source.

The messages appear inside the vehicle but in a different COMP ID (see picture). Is there something I am missing?

image
image521×1021 24.6 KB

Set up is:

  • GPS1 OFF
  • GPS2 protocol - MAVLINK
  • SERIAL4 PROTOCOL - MAVLINK
  • SERIAL4 BAUD - 38400

image
image445×438 53.3 KB

Thanks in advance,
Pedro

2

Ignore the port labeling. You only have one GPS, so configure it as GPS1.

If you aren’t using SERIAL3 for anything else, disable its protocol as well (instead of the default GPS protocol).

1 Like
3

Hi Yuri,

Thanks for your reply.

In my case, GPS1 is connected to a default Holybro GPS module, while GPS2 is configured as the primary GPS. That’s why I’m trying to use GPS2 for the MAVLink GPS input.

I also tested your suggestion by disabling SERIAL3 (setting its protocol to None), but the issue still persists. The MAVLink GPS data continues to appear under a different component ID, and it’s not being recognized/used as a GPS source by the Pixhawk.

Is there something specific I should be doing to make the autopilot associate those MAVLink messages with the GPS driver? Or is there a requirement regarding the component ID or message routing that I might be missing?

I also attached some relevant parameters prints.

Thanks again for your help.

Best regards,
Pedro

image
image479×246 6.07 KB

image
image484×251 6.07 KB

image
image481×425 9.02 KB

image
image337×434 5.17 KB

image

4

All your pictures don’t refle> ct what you are writing.

“GPS1 is connected to a default Holybro GPS module”

As also @Yuri_Rage mentioned I think you mismatch the pyhysical labeled GPS connector with the logical GPS number.
As long only one GPS is defined I think this is always GPS1 also if it is connected to the connector Serial GPS 2.
If you want to use it as logical GPS2 as shown, you also have to connect and define your Holybro GPS correct on GPS1

But it is always bad not to have your complete latest params to double check