Posts made by Inverse AJ

@Eric-Katzfey I had not since this discussion was the closest I could find to my issue. But I have created one now: Cannot see obstacle_distance_fused on QGC

@Eric-Katzfey Small update. I also tried it with the custom firmware with that additional publication added (from previous reply), and the result has not changed. obstacle_distance_fused still shows up as "never published" when using the listener. However, with the custom firmware I get warnings from QGC about missing parameters: BAT1_V_LOAD_DROP, BAT2_V_LOAD_DROP, and COM_OBS_AVOID. I pulled the most recent main branch for the PX4 Repository to build it, so maybe there's not support by QGC yet?

@Eric-Katzfey I was previously in "Hold" mode, but I tried in "manual" and still am not seeing the obstacle_distance_fused message. I noticed one other difference in my parameters which is that COM_OBS_AVOID doesn't exist for me.

Another question, I had previously re-flashed the Pixhawk firmware after changing the file: "PX4Autopilot/src/modules/uxrce_dds_client/dds_topics.yaml". I had added the following to the publications section:

• topic: /fmu/out/obstacle_distance_fused
  type: px4_msgs::msg::ObstacleDistance

However, it had no effect so I reverted back to the default px4 firmware shown on QGC. Is that change necessary to see the message or should I leave the default?

@Eric-Katzfey I am having a similar problem, where I can see obstacle_distance, but not obstacle_distance_fused using the listener command. When I checked CP_DIST it was set to -1 so I set it to 1 and then I could briefly see both with the listener command, and was able to see obstacle_distance using the mavlink inspector. After unplugging then replugging in my pixhawk, this was gone and I was back to only being able to see obstacle_distance with the listener command. Was there something that could've changed during my restart? I checked CP_DIST and it was still set to 1 even afterwards.

The only notable differences between my system and the original users is that my connection is across ethernet.