[Bug] Missing Parameters COM_FLTMODE1 to COM_FLTMODE6 Prevents RC Flight Mode Control on Navio2 with PX4

[Lqs66]

Describe the bug

When I followed the instructions on https://docs.px4.io/main/zh/flight_controller/raspberry_pi_navio2.html to start PX4 and connect it to QGroundControl (QGC), QGC notified me that parameters COM_FLTMODE1 through COM_FLTMODE6 were missing. As a result, I was unable to switch flight modes using the RC transmitter through these channels. However, the flight controller was able to detect the switching of the RC transmitter's switches. This suggests that while the hardware communication between the RC transmitter and the flight controller is functioning correctly, the necessary parameters for flight mode configuration are not properly set or are missing in the PX4 firmware.

This issue appears to be version-specific. In PX4 v1.12.3, the parameters COM_FLTMODE1 to COM_FLTMODE6 are correctly recognized and available for configuration, allowing proper mapping of RC channels to flight modes. However, in versions v1.13.3 and v1.15, these parameters are missing, which prevents QGroundControl (QGC) from configuring flight modes via the RC transmitter.

To Reproduce

First, execute the command sudo ./bin/px4 -s px4.config in the Raspberry Pi terminal, where px4.config refers to the configuration file located at posix-configs/rpi/px4.config. After starting PX4, open QGroundControl (QGC) and navigate to the Vehicle Setup. When attempting to access the Flight Modes settings, QGC will issue a warning, and you will be unable to configure the flight modes. This indicates that while PX4 is running on the Raspberry Pi, the necessary parameters or configurations for flight mode settings are either missing or improperly configured, preventing QGC from enabling this functionality.

Expected behavior

No response

Screenshot / Media

No response

Flight Log

No response

Software Version

PX4 version: v1.12.3 v1.13.3 v1.15

Flight controller

raspberrypi + navio2

Vehicle type

Multicopter

How are the different components wired up (including port information)

No response

Additional context

No response