Hey @Aniruddha
I was able to recreate your issue with ROS2 jazzy, seems like there is a mismatch between topic size between the versions.
I use humble on my laptop and havent faced any issues, try using it and let me know your results

I'll investigate this issue further

@Aniruddha
Even after matching the versions, I am not able to recreate your error
I will try relfashing my voxl2, to start from a clean slate similar to your setup right now.
Since you reflashed the voxl2, is there something you changed on the voxl2 for your goals? I assume that after a reflash, I should have the same setup as you

@Aniruddha
What version SDK are you using? What are the versions of voxl-mpa-to-ros2, voxl-microdds-agent , voxl-ros2-foxy and voxl-px4. You can find it with the command: voxl-version
My suspicion is that the ros2 message being published is of a different size than what ros2 subscriber is expecting, and that's causing the break
Here are the versions I used that worked for me:
voxl-mpa-to-ros2 0.0.7-202511100959
voxl-microdds-agent 3.0.0-0-202511141239
voxl-ros2-foxy 0.0.1-202511141235
voxl-px4 1.14.0-2.0.134

Hey @Aniruddha
I tried recreating the issue on my setup using a Starling V2 Max connected to my computer over Wi-Fi. On my end, I’m able to echo ROS 2 topics both on the drone and from the computer without any issues. I even added the same static IP configuration you used, and I was still able to echo my topics without any errors.

You also mentioned seeing an error on the drone side for the voxl_mpa_to_ros2_node, could you clarify what the exact error is? Are you unable to run ros2 topic echo directly on the drone as well, or is the problem only when echoing from your computer? Additionally, which drone model are you using?

Hey @Aniruddha
As I understand it, you are able to see the topics on your computer but cant echo them. Which topic are you trying to echo so I can try to recreate it on my end?

Hey @Aniruddha,
Thanks for reaching out, could you provide more information about your setup and how things are communicating?

Hey, I wanted to know if the VOXL 2 supports Bluetooth, ideally with an SDK that makes integration easy. If not, is there a module you’d recommend for adding Bluetooth support?

Hey @voxltester
It seems there is an issue with how MicroXRCE and the microhard modem interfaces are starting up, I had to edit the service files to get the topics on the VOXL2.
Edit /etc/systemd/system/voxl-microdds-agent.service:

[Unit]
Description=voxl-microdds-agent
SourcePath=/usr/bin/MicroXRCEAgent
After=network.target
After=multi-user.target

[Service]
User=root
Type=simple
ExecStart=/usr/bin/MicroXRCEAgent udp4 -p 8888

[Install]
WantedBy=multi-user.target

Edit /etc/systemd/system/voxl-modem.service:

[Unit]
Description=Modem Initialization
After=sdsprpcd.service

[Service]
User=root
Type=oneshot
ExecStartPre=/bin/sleep 2
ExecStart=/usr/bin/voxl-modem-start
RemainAfterExit=yes

[Install]
WantedBy=multi-user.target

Add export ROS_DOMAIN_ID=0 to your .bashrc
Reboot the VOXL2, and the topics should come up
Thanks

Hey @svempati
I trained a model in the docker command as provided by you. I am able to run an inference on potholes following exactly the steps provided by @Zachary-Lowell-0 earlier.
Could I ask you what your voxl-tflite-version is? And if you havent yet, could you try to run this version: http://voxl-packages.modalai.com/dists/qrb5165/sdk-1.6/binary-arm64/voxl-tflite-server_0.5.1_arm64.deb
Make sure to change the .tflite model and labels as shown in the loom video after the install, then run voxl-configure-tflite

Thanks

@voxltester,
When you say voxl-microdds-agent doesnt work, do you mean it doesnt run? Or it doesnt create the topics? Whats the terminal output when you run it directly from the terminal?
Is your setup like earlier where you have the hat on and the wifi dongle is connected on the hat?

If the topics are only showing up after disabling the wifi interface, then I suspect its a ip routing issue, and that voxl microdds agent is binding to the first interface that comes up, which is the wifi.