ROS

Unable to echo ros2 topic from drone to a computer

Aniruddha — Mon, 27 Apr 2026 13:49:30 GMT

@ApoorvThapliyal Thank you for your help. also I was able to work with jazzy by only subscribing and printing with node. since error only occurred when I tried to echo the topic and not when another node is subscribing it. but using docker seems like most viable option to me since I m using ubuntu 24.04. Thank you for your help again

Ros2 Humble on Voxl2

jmltt — Tue, 18 Nov 2025 15:34:18 GMT

@Zachary-Lowell-0 Thank you for the feedback! This was very helpful

VEHICLE VISUAL ODOMETRY NOT PUBLISHING

teddy.zaremba — Mon, 04 Aug 2025 20:28:13 GMT

Hi @taiwohazeez, The " /fmu/in" prefix is used for sending data to the autopilot - you're never going to receive data from the autopilot listening to that topic. Look at the "/fmu/out" topics to see messages coming from the autopilot. Best, Ted

Issue sending custom odometry to PX4 via MAVROS

Judoor 0 — Wed, 30 Jul 2025 09:08:45 GMT

Hi @teddy-zaremba, The fusing part was a bit tricky, but it works now. Thank you!

Getting Range finder information in ROS and more.

teddy.zaremba — Thu, 17 Jul 2025 07:19:20 GMT

Hi @Judoor-0, Cool! Feel free to make a MR or post the link to your code if you want someone to review it.

voxl_mpa_to_ros2 only publishes left stereo camera

cguzikowski — Tue, 08 Jul 2025 23:16:26 GMT

@teddy-zaremba Nevermind, I was able to separate the images by modifying the voxl-camera-server.conf file to treat each camera as separate and it seems to be working now

ROS2 ON VOXL2

teddy.zaremba — Mon, 30 Jun 2025 16:16:13 GMT

@taiwohazeez Could you post the error and we can take a look? Also here's an easier way of installing it if you just want to run this script on the voxl. wget http://voxl-packages.modalai.com/dists/qrb5165/sdk-1.5/binary-arm64/voxl-ros2-foxy_0.0.1_arm64.deb wget http://voxl-packages.modalai.com/dists/qrb5165/sdk-1.5/binary-arm64/voxl-mpa-to-ros2_0.0.7_arm64.deb sudo dpkg -i voxl-ros2-foxy sudo dpkg -i voxl-mpa-to-ros2 voxl-configure-mpa-to-ros2

VOXL2 ROS2 Starling Code Inconsistencies

Zachary Lowell 0 — Fri, 04 Apr 2025 20:52:02 GMT

@claw said in VOXL2 ROS2 Starling Code Inconsistencies: @Zachary-Lowell-0 Thank you for your help and guidance. Is there a way to get the status information like battery voltage using Python? Reply @claw yes you can follow this post to get battery over the DDS: https://forum.modalai.com/topic/4353/voxl2-px4-ros2-mpa-to-ros2-for-battery-voltage-problems/12?_=1745355297145

Which development environment is suitable to build ROS2 packages and nodes for the RB5

tahawaru — Wed, 19 Mar 2025 12:51:48 GMT

@Zachary-Lowell-0 What kind of upgrade is necessary for this Rb5? Should we upgrade the sdk? we can run ros2 foxy with it. The dds is also working. How did you build this ros2 packages and nodes https://gitlab.com/voxl-public/voxl-sdk/utilities/voxl-mpa-to-ros2 Thank you

How to build-compile FOXY ROS2 packages and nodes for RB5

Zachary Lowell 0 — Mon, 10 Mar 2025 13:57:42 GMT

You need to push the install folder as thats where the executables live in ros2 once you run colcon build. src folder is just the code you wrote with zero executables after colcon build is run.

IMU stream rate fixed at 10Hz (PX4)

KLindgren — Wed, 05 Mar 2025 16:26:44 GMT

@Eric-Katzfey got it, thank you for the info.

Stuck installing ros-melodic-pcl-conversions

teddy.zaremba — Thu, 16 Jan 2025 19:10:01 GMT

@VSK said in Stuck installing ros-melodic-pcl-conversions: configure python-twisted-core:all 17.9.0-2ubuntu0.3 status half-configured python-twisted-core:all 17.9.0-2ubuntu0.3 Maybe that package got corrupted on the install. Can you try running sudo apt-get clean? If that doesn't work, you could also try removing both of the packages and do the install again. $ sudo apt remove python-twisted-core:all $ sudo apt remove ros-melodic-pcl-ros ros-melodic-pcl-conversions

Offboard mode and ROS2 with Rb5

tahawaru — Wed, 15 Jan 2025 12:19:08 GMT

@Zachary-Lowell-0 offboard mode: [image: 1737382725235-d5d4a98e-4bf0-4aa7-baee-522cb331b4a7-image.png] The drone does NOT arm from the ROS2 command but it can be armed with the RC 3)rb5:~$ voxl-inspect-services Scanning services... [image: 1737382905455-bea8dc77-6e7c-4635-b0b0-c7b9a5ec7676-image.png] 4)/usr/bin/voxl-px4-start [image: 1737383495210-466822e7-ff3f-4c08-a6c4-780b619665d0-image.png] Best wishes,

/tof_depth image conversion problem

Judoor 0 — Thu, 09 Jan 2025 01:21:06 GMT

@Alex-Kushleyev thank you alex i'll try that

Bridging microdds agent and dds discovery server

Wed, 18 Dec 2024 16:33:17 GMT

ROS2 performance issues with multiple vehicles

Fri, 13 Dec 2024 21:56:55 GMT

MAVROS

Mon, 25 Nov 2024 22:46:17 GMT

Error when lunching voxl_mpa_to_ros.launch

teddy.zaremba — Fri, 22 Nov 2024 21:29:12 GMT

Hi @Mohammad-Goli, it seems like something on your VOXL is prematurely closing the file descriptor attached to the process that lists the pipes - I'm not sure what that is. I'm also not getting any errors with libyaml-cpp so that could be part of the problem. I'm running on SDK version 1.3.5, so I if were you I'd re-flash your VOXL and try the install again. Flashing the VOXL guide Sorry I couldn't recreate your issue. If you're still having a problem after re-flashing, let me know what SDK you tried and I'll give it a shot on my end.

Setting up Voxl2 MicroDDS Communication with PX4

James KDH — Tue, 19 Nov 2024 05:37:37 GMT

Okay I managed to solve the problem. The reason why my external pc is unable to see the /fmu topics is probably due to the voxl-microdds-agent service starting before the network is fully "set up". From this stack overflow topic, I edited my /etc/systemd/system/voxl-microdds-agent.service file to include the line ExecStartPre=/bin/sh -c 'until ping -c1 google.com; do sleep 1; done; (this is the only "hacky" method that somehow worked). My entire service file is: [Unit] Description=voxl-microdds-agent SourcePath=/usr/bin/MicroXRCEAgent After=network.target After=multi-user.target # After=network-online.target # Wants=network-online.target [Service] User=root Type=simple ExecStartPre=/bin/sh -c 'until ping -c1 google.com; do sleep 1; done;' ExecStart=/usr/bin/MicroXRCEAgent udp4 -p 8888 [Install] WantedBy=multi-user.target After modifying the service file and rebooting the voxl2, the external computer can now see and echo topics from the /fmu. This will obviously not work if the voxl2 is not connected to the internet.. However you can still manually fix this by ssh or adb shell into the voxl2 and restart the service using the commands: systemctl stop voxl-microdds-agent systemctl start voxl-microdds-agent and the external computer should be able to see /fmu topics. On a side note, to customize & add a prefix to the /fmu topic such that it is /drone1/fmu/ in ROS2, edit the px4 start up script /usr/bin/voxl-px4-start. There is a line that starts the microdds_client for px4 where: # Start microdds_client for ros2 offboard messages from agent over localhost microdds_client start -t udp -h 127.0.0.1 -p 8888 Simply add -n such that it becomes: # Start microdds_client for ros2 offboard messages from agent over localhost microdds_client start -t udp -h 127.0.0.1 -p 8888 -n drone2

problems installing voxl-mpa-to-ros2

LR — Thu, 07 Nov 2024 22:19:53 GMT

@LR I removed and reinstalled voxl-mpa-to-ros2 and that is working now, for voxl-mpa-to-ros I still have the same problem