@ApoorvThapliyal
Thank you again for the reply!
We are setting up a multi-robot system, so we are using ROS_LOCALHOST_ONLY=0.
For example, we want to set the ROS_DOMAIN_ID of drone 1 to 1 and the ROS_DOMAIN_ID of drone 2 to 2.
However, for both drones, PX4-related messages still appear under domain ID 0.
Have you tried this with two or more drones?

@ApoorvThapliyal
Thank you for the reply.
Did you happen to add export ROS_DOMAIN_ID=1 to your ~/.bashrc?
When I do that, ROS 2 topics disappear in the VOXL shell.
However, on my laptop where ROS_DOMAIN_ID=0, I can see the ROS topics.
That’s why I posted this.

Hello,
I am currently using Starling 2 and Starling 2 Max for our experiments, and we need to document their specifications. Could you please provide the following information?

Starling 2
Maximum flight range
Maximum speed

Starling 2 Max
Maximum flight range

Thank you in advance for your help.

We are currently using Starling 2 and Starling 2 Max for our experiments, and we need to document their specifications.
Could you please provide the following information?
Starling 2

• Maximum flight range
• Maximum speed
• Model of the remote controller
  Starling 2 Max
• Maximum flight range
• Model of the remote controller
  Sensors
• IMX412: Manufacturer (country of origin) and location of manufacturing
• AR0144: Manufacturer (country of origin) and location of manufacturing
• ToF sensor: Manufacturer (country of origin) and location of manufacturing

Thank you in advance for your help.

Dear Researchers and Developers,

I can see PX4-related ROS 2 messages even without explicitly running any ROS 2 nodes myself.
It looks like these messages are visible under ROS_DOMAIN_ID=0.
Could you please share guidance on how to change the ROS 2 domain ID for these PX4-related messages?