Hey @yunwool
Just to be clear, consider only your first drone, if you run export ROS_DOMAIN_ID=1, then run ros2 topic list, you aren't seeing any topics right?

After you set the ROS_DOMAIN_ID of a drone to 1, to get the PX4 topics to show up, on QGC > Analyze Tools > MAVLink Console, run the following commands:

param set XRCE_DDS_DOM_ID 1
param save

Then power cycle the drone, give it like 15s after boot up, then the topics should come up directly when running ros2 topic list on that drone.

Hey @greg_s
I was able to reproduce the issue where the drone does not fly correctly toward the setpoint. I think reviewing the extrinsics.conf file is a good next step, as there may be an incorrect transform defined there.

Hey @yunwool
Did you try setting the ROS_LOCALHOST_ONLY variable to limit the topics to your local device?

Hey @greg_s
I just wanted to confirm, are you dragging the planned point to the height desired? By default, simply clicking on the map will generate a point at height 0.
Let me know, thanks

Hey @greg_s,
Can you post your voxl-logs and flight logs?

Thanks

Hey @yunwool
I would recommend writing export ROS_DOMAIN_ID=1 in your ~/.bashrc and then restarting all terminals so the change takes effect. This should prevent other ROS 2 messages from appearing in your environment, since you’ll effectively be using your own domain.

Optionally, you may want to look into the ROS_LOCALHOST_ONLY variable as well, since I do believe if someone else sets their domain ID to 1, you would see their messages.

@kgn-mdlai Thank you for bringing this up, a fix to this is currently being worked on.
Thanks

Hey @dvz, thanks for your query

We’re currently in the process of updating the voxl-tag-detector to support additional AprilTag families beyond just the 36h11.

If you’d like to try this yourself in the meantime, the following line in main.cpp creates the detector for the 36h11 family: here

To add support for the tagCustom48h12 family, you can:

Add the include:

#include <tagCustom48h12.h>

Replace the detector creation line with:

tf = tagCustom48h12_create();

Please note that this change may affect the current functionality, you’ll likely need to make additional modifications in main.cpp to ensure it builds and runs correctly.
As mentioned, we’re actively working on making this a much smoother process in the future. But if you’d like to get started now, the above steps should point you in the right direction.

@Rupesh Apologies for the late reply
It looks like there’s an issue with how the AprilTag system is relocalizing the drone. In my tests, the z-value appears to be misinterpreted, which could explain why your drone was climbing in altitude to correct its height estimate. We’re actively working on a fix.

@Rupesh What rotation matrix are you currently using in your tag_locations.conf?
You can try setting it to:

[[0, 1, 0],
[0, 0, 1],
[1, 0, 0]]
Keep in mind that relocalization will only work reliably at certain viewing angles relative to the AprilTag. A good way to test is to rotate the tag and observe at which orientations voxl-vision-hub --debug_fixed_frame gives a value and not WARNING, apriltag roll/pitch out of bounds. Improvements are in progress to make this more robust across a wider range of angles.