@Kyuhyong-You Take a look at the file /usr/bin/voxl-px4-start. That is the file that starts all of the PX4 drivers, modules, etc. Look for the microdds_client start -t udp -h 127.0.0.1 -p 8888 line and comment that out.
@Kyuhyong-You
After reboot this error is magically gone.
now I can see topics
after $ ros2 run voxl_mpa_to_ros2 voxl_mpa_to_ros2_node
then in another terminal on voxl, I see below topics
$ ros2 topic list
/fmu/in/obstacle_distance
/fmu/in/offboard_control_mode
/fmu/in/onboard_computer_status
/fmu/in/sensor_optical_flow
/fmu/in/telemetry_status
/fmu/in/trajectory_setpoint
/fmu/in/vehicle_attitude_setpoint
/fmu/in/vehicle_command
/fmu/in/vehicle_mocap_odometry
/fmu/in/vehicle_rates_setpoint
/fmu/in/vehicle_trajectory_bezier
/fmu/in/vehicle_trajectory_waypoint
/fmu/in/vehicle_visual_odometry
/fmu/out/failsafe_flags
/fmu/out/position_setpoint_triplet
/fmu/out/sensor_combined
/fmu/out/timesync_status
/fmu/out/vehicle_attitude
/fmu/out/vehicle_control_mode
/fmu/out/vehicle_local_position
/fmu/out/vehicle_odometry
/fmu/out/vehicle_status
/parameter_events
/rosout
@tom
Wow I didn't know there is dedicated apt package to install ros-foxy and why the guide leads to install ros via script.
Anyway thanks for the comment and I will try to install as you mentioned.
Sure thing @Kyuhyong-You . That is correct - currently the voxl2 runs the microdds client instead of the uxrce dds client on 1.14.0 stable. The microdds client starts automatically on the voxl2 when px4 is instantiated - if not, feel free to build PX4 yourself and flash it on the board via the instructions here:
https://docs.modalai.com/voxl-px4-dev-build-guide/
There is also another service available on SDK 1.1 (https://docs.modalai.com/sdk-1.1-release-notes/) called microdds-agent which spins up the agent to listen to localhost port 8888 and allow for comms similar to mavsdk.
https://docs.modalai.com/ros2-installation-voxl2/
K
