You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Me and my friend are using the PX4 autopilot with ROS2 for a project, and initially we were getting each others topics when running ros2 topic list, so we then added ROS_LOCALHOST_ONLY=1 in our zshrc files. But recently, our MicroXRCE agent is giving small issues:
Running make px4_sitl gazebo-classic, the MicroXRCE agent connects, but running ros2 topic list does not give any topics
Running ./Tools/simulation/gazebo-classic/sitl_multiple_run.sh -m iris -n 1, the MicroXRCE agent simply does not connect, and so we dont get topics
May I know any possible reason for this problem? Thanks
To Reproduce
No response
Expected behavior
No response
Screenshot / Media
No response
Flight Log
No response
Software Version
No response
Flight controller
No response
Vehicle type
Multicopter
How are the different components wired up (including port information)
No response
Additional context
No response
The text was updated successfully, but these errors were encountered:
Describe the bug
Me and my friend are using the PX4 autopilot with ROS2 for a project, and initially we were getting each others topics when running
ros2 topic list
, so we then addedROS_LOCALHOST_ONLY=1
in our zshrc files. But recently, our MicroXRCE agent is giving small issues:Running make
px4_sitl gazebo-classic
, the MicroXRCE agent connects, but runningros2 topic list
does not give any topicsRunning
./Tools/simulation/gazebo-classic/sitl_multiple_run.sh -m iris -n 1
, the MicroXRCE agent simply does not connect, and so we dont get topicsMay I know any possible reason for this problem? Thanks
To Reproduce
No response
Expected behavior
No response
Screenshot / Media
No response
Flight Log
No response
Software Version
No response
Flight controller
No response
Vehicle type
Multicopter
How are the different components wired up (including port information)
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: