Open qcharmoillau opened 3 months ago
It looks like there may be an interaction between the launch args in the rosbridge_websocket_launch.xml and the foxglove_bridge_launch files.
The IncludeLaunchDescription
action will basically copy-paste the contents of the target file into your launch description. This is what is causing the "port" argument to be overwritten in this case.
Description
Steps To Reproduce 1°) On the one hand, by using the command line
ros2 launch foxglove_bridge foxglove_bridge_launch.xml
in the Ubuntu terminal, the address and the port are properly set judging by the terminal's feedback :Therefore I can visualize things as expected in Foxglove Studio in the PC.
2°) On the other hand, I created the following launch file, which include the equivalent launch and other ROS2 functions:
In this way, the default address and port are not met as can be seen in the terminal feedback :
[foxglove_bridge-3] [INFO] [1721824501.660898719] [foxglove_bridge]: [WS] WebSocket server listening at ws://[::1]:9090
It should bews://0.0.0.0:8765
instead ofws://[::1]:9090
), so of course Foxglove Studio cannot get the data :(3°) I can solve this by: a) Specifying the address and the port as launch arguments in my launch file:
b) Inverting the order of
rosbridge_launch
andfoxglove_bridge_launch
inreturn LaunchDescription([...])
. By doing so I obtainws://0.0.0.0:8765
as expected and Foxglove Studio works.Expected Behavior The result obtained at step 3°) should appear at the step 2°), since the port and the address are set by default to "8765" and "0.0.0.0" in
foxglove_bridge_launch.xml
, which is the file called by my launch code. What is the reason for this error?