@Kyuhyong-You
It actually turned out that the host-pc has ufw enabled.
Disabling ufw solved the issue.
Thanks
@Kyuhyong-You
It actually turned out that the host-pc has ufw enabled.
Disabling ufw solved the issue.
Thanks
@Zachary-Lowell-0
Is there a way to publish ros2 message to certain ethernet port?
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_status
I 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,
Hello,
I am trying to use 4 in 1 esc from https://holybro.com/collections/autopilot-peripherals/products/tekko32-f4-metal-4in1-65a-esc-65a
This esc works with DSHOT however
https://nearth.atlassian.net/l/cp/HSr9ZCoU says DSHOT is "Not yet supported"
If DSHOT not available, can I use PWM instead?
Which port should I use on voxl 2 board to connect PWM input to esc?
Thanks,
@Zachary-Lowell-0
I was finally able to install ros2 on voxl2 with latest sdk 1.1.0 and run voxl_mpa_to_ros2_node.
and I can see the topics on voxl2 as below.
VOXL:~$ 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
Now I am trying to send command via ros2 message from my host pc however those topics are not visible on my host pc.
HOST_PC:~$ ros2 topic list
/parameter_events
/rosout
They both have same ROS_DOMAIN_ID=0
They are in the same network router and share same ip layer 10.10.150.XXX
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
@Kyuhyong-You
I found solution.
This error was resolved by apt installing libtinyxml2 by
sudo apt install libtinyxml2-dev
With sdk 1.1.0 up and running.
apt installed ros-foxy and voxl_mpa_to_ros2 as well.
as described in this document https://docs.modalai.com/ros2-installation-voxl2/
When trying to start voxl_mpa_to_ros2_node I get following error.
$ ros2 run voxl_mpa_to_ros2 voxl_mpa_to_ros2_node
/opt/ros/foxy/mpa_to_ros2/install/voxl_mpa_to_ros2/lib/voxl_mpa_to_ros2/voxl_mpa_to_ros2_node: error while loading shared libraries: libtinyxml2.so.6: cannot open shared object file: No such file or directory
How to fix this error?
Hello,
I just upgraded my voxl2 with the latest sdk 1.1.0 and apt installed ros2 relate packages as follows
sudo apt install voxl-ros2-foxy
$ sudo apt install voxl-microdds-agent
$ sudo apt install voxl-mpa-to-ros2
$ pip3 install netifaces
$ pip3 install pyyaml
After source /opt/ros/foxy/setup.bash
and tried to run ros2 topic and it returns following error.
$ ros2 topic list
Unable to get rmw_implementation_identifier, try specifying the implementation to use via the 'RMW_IMPLEMENTATION' environment variable
It seems like RMW_IMPLEMENTATION
not set in the bash.
How to set this variable to run on voxl?
Also tried to run configuration as below
$ sudo voxl-configure-microdds
Starting Wizard
do you want to enable or disable voxl-microdds-agent
factory-enable will also reset the config file back to default
1) disable
2) enable
#? 2
enabling voxl-microdds-agent systemd service
Created symlink /etc/systemd/system/multi-user.target.wants/voxl-microdds-agent.service → /etc/systemd/system/voxl-microdds-agent.service.
Done configuring voxl-microdds-agent
And inspect service returns
$ voxl-inspect-services
Scanning services...
Service Name | Enabled | Running | CPU Usage
-------------------------------------------------------------------
docker-autorun | Disabled | Not Running |
modallink-relink | Disabled | Not Running |
voxl-camera-server | Enabled | Not Running |
voxl-cpu-monitor | Enabled | Running | 0.7%
voxl-dfs-server | Disabled | Not Running |
voxl-feature-tracker | Disabled | Not Running |
voxl-flow-server | Disabled | Not Running |
voxl-imu-server | Enabled | Running | 6.2%
voxl-lepton-server | Disabled | Not Running |
voxl-mavcam-manager | Enabled | Running | 0.0%
voxl-mavlink-server | Enabled | Running | 3.4%
voxl-microdds-agent | Enabled | Running | 13.5%
voxl-modem | Disabled | Not Running |
voxl-portal | Enabled | Running | 0.1%
voxl-px4-imu-server | Disabled | Not Running |
voxl-px4 | Enabled | Running | 40.2%
voxl-qvio-server | Enabled | Running | 4.2%
voxl-rangefinder-server | Disabled | Not Running |
voxl-remote-id | Disabled | Not Running |
voxl-softap | Disabled | Not Running |
voxl-static-ip | Disabled | Not Running |
voxl-streamer | Enabled | Running | 0.1%
voxl-tag-detector | Disabled | Not Running |
voxl-tflite-server | Disabled | Not Running |
voxl-time-sync | Disabled | Not Running |
voxl-uvc-server | Disabled | Not Running |
voxl-vision-hub | Enabled | Running | 1.8%
voxl-wait-for-fs | Enabled | Completed |``
@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.