Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug] QGC not showing external mode from PX4 #11996

Open
junwoo091400 opened this issue Oct 11, 2024 · 4 comments
Open

[Bug] QGC not showing external mode from PX4 #11996

junwoo091400 opened this issue Oct 11, 2024 · 4 comments

Comments

@junwoo091400
Copy link
Contributor

junwoo091400 commented Oct 11, 2024

Expected Behavior

QGC should show the name of the external mode "CustomMode" (in this example) supported by PX4 via it's ROS2 Control interface. This feature was added in #10788.

Current Behavior

The mode name doesn't show up in flight modes supported.

Steps to Reproduce:

Please provide an unambiguous set of steps to reproduce the current behavior

  1. Install QGC v4.4.2
  2. Start PX4 SITL make px4_sitl_default gz_x500
  3. Start MicroXRCE-DDS Agent MicroXRCEAgent udp4 -p 8888
  4. Start ROS2 script ros2 run custom_mode custom_mode
  5. Check QGC's listed supported modes

System Information

Log Files and Screenshots

image

image

With the "StandardModes" for QGC Console log enabled, it didn't show anything. Only irrelevant errors:
image

@patrikpordi
Copy link

I face the same issue!

@DonLakeFlyer
Copy link
Contributor

Can you try a daily build as well?

@patrikpordi
Copy link

It works on the daily build but based on the #10788 I assume it should work on the main as well? Do we misunderstand it?

@hamishwillee
Copy link
Contributor

hamishwillee commented Oct 29, 2024

This should work by requesting AVAILABLE_MODES and then populating the UI appropriately. That message is in development.xml - does QGC import this for both main and daily builds?

I.e. first thing to check is that this message is being requested and recieved. Then check that the properties field does not have MAV_MODE_PROPERTY_NOT_USER_SELECTABLE set

@patrikpordi It only works on daily build, which imports development.xml, because that is the file that includes the required message definitions.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants