how to stop microdds-agent from running?
-
As soon as I install voxl-ros2-foxy, I see topics being published
$ ros2 topic list /fmu/collision_constraints/out /fmu/debug_array/in /fmu/debug_key_value/in /fmu/debug_value/in /fmu/debug_vect/in /fmu/manual_control_setpoint/in /fmu/offboard_control_mode/in /fmu/onboard_computer_status/in /fmu/optical_flow/in /fmu/position_setpoint/in /fmu/position_setpoint_triplet/in /fmu/sensor_combined/out /fmu/telemetry_status/in /fmu/timesync/in /fmu/timesync/out /fmu/trajectory_bezier/in /fmu/trajectory_setpoint/in /fmu/trajectory_waypoint/out /fmu/vehicle_attitude/out /fmu/vehicle_command/in /fmu/vehicle_command_ack/out /fmu/vehicle_global_position/out /fmu/vehicle_local_position/out /fmu/vehicle_local_position_setpoint/in /fmu/vehicle_mocap_odometry/in /fmu/vehicle_odometry/out /fmu/vehicle_offboard_setpoints/in /fmu/vehicle_setpoints/in /fmu/vehicle_status/out /fmu/vehicle_trajectory_bezier/in /fmu/vehicle_trajectory_waypoint/in /fmu/vehicle_trajectory_waypoint_desired/out /fmu/vehicle_visual_odometry/in /gimbal_attitude /mission_command /mission_command_ack /mission_status /parameter_events /physical_state /rosout /set_vehicle_id /stick_command /timesync_status /vehicle_command /vehicle_command_ack /vehicle_statusI didn't even installed voxl-microdds-agent, voxl-mpa-to-ros2
How can I let voxl stop sending these message?
I just want to run the agent myself.
Thanks, -
As soon as I install voxl-ros2-foxy, I see topics being published
$ ros2 topic list /fmu/collision_constraints/out /fmu/debug_array/in /fmu/debug_key_value/in /fmu/debug_value/in /fmu/debug_vect/in /fmu/manual_control_setpoint/in /fmu/offboard_control_mode/in /fmu/onboard_computer_status/in /fmu/optical_flow/in /fmu/position_setpoint/in /fmu/position_setpoint_triplet/in /fmu/sensor_combined/out /fmu/telemetry_status/in /fmu/timesync/in /fmu/timesync/out /fmu/trajectory_bezier/in /fmu/trajectory_setpoint/in /fmu/trajectory_waypoint/out /fmu/vehicle_attitude/out /fmu/vehicle_command/in /fmu/vehicle_command_ack/out /fmu/vehicle_global_position/out /fmu/vehicle_local_position/out /fmu/vehicle_local_position_setpoint/in /fmu/vehicle_mocap_odometry/in /fmu/vehicle_odometry/out /fmu/vehicle_offboard_setpoints/in /fmu/vehicle_setpoints/in /fmu/vehicle_status/out /fmu/vehicle_trajectory_bezier/in /fmu/vehicle_trajectory_waypoint/in /fmu/vehicle_trajectory_waypoint_desired/out /fmu/vehicle_visual_odometry/in /gimbal_attitude /mission_command /mission_command_ack /mission_status /parameter_events /physical_state /rosout /set_vehicle_id /stick_command /timesync_status /vehicle_command /vehicle_command_ack /vehicle_statusI didn't even installed voxl-microdds-agent, voxl-mpa-to-ros2
How can I let voxl stop sending these message?
I just want to run the agent myself.
Thanks,@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 8888line and comment that out.
Reading along? Create a free ModalAI Forum account to join in.
With an account you can reply, ask your own question, get an email when a ModalAI engineer answers, and mark the reply that solved it. Your place in each thread is saved between visits.
Questions about VOXL, Flight Core, ESCs and ModalAI drones are answered here by the engineers who build them.
Register Login