You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
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.
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
make px4_sitl_default gz_x500
MicroXRCEAgent udp4 -p 8888
ros2 run custom_mode custom_mode
System Information
Log Files and Screenshots
With the "StandardModes" for QGC Console log enabled, it didn't show anything. Only irrelevant errors:
The text was updated successfully, but these errors were encountered: