Use ROS extension's launch debugger while setting ROS_IP #1289
rsarrazin2
started this conversation in
ROS1
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
We have a setup where we communicate between different machines (actually different docker containers) and a ROS1 launch file starts all nodes. When setting
ROS_IPon the "launch" container andROS_MASTER_URIon the other container, the communication works well and as expected.Nevertheless, when starting the extension's launch debugger, the communication doesn't happen - as if
ROS_IPhadn't been set. I setROS_IPin thelaunch.json, here is how my configuration looks like:{ "name": "ROS: Debug", "type": "ros", "request": "launch", "target": "${workspaceFolder}/src/package/package.launch", "arguments": [ "param1:=value1", "param2:=value2" ], "env": { "ROS_IP": "172.17.177.140" } }What am I missing? I guess the roscore is found by the other machine as there's no error message, but the messages sent from the "launch" machine don't reach the other machine as if
ROS_IPwasn't set. What am I missing?By the way, https://github.com/ms-iot/vscode-ros/blob/master/doc/debug-support.md#prerequisite seems to tell a roscore needs to be started manually, but it looks like one is started when debugging a launch file (and this is backed by
vscode-ros/src/debugger/configuration/resolvers/ros1/launch.ts
Line 49 in 43dc595
Beta Was this translation helpful? Give feedback.
All reactions