-
Notifications
You must be signed in to change notification settings - Fork 171
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Inconsistency in launch examples and ROS2 launch xml specifications #156
Comments
As far as I can tell, all of the examples work fine on Foxy. Can you please give the error you are seeing when running it? |
Here is my intention if it helps. I'm trying to port UUV models into uuv simulator ROS2 port Plankton. If I run the example it works like a charm. ~ ros2 launch robot_state_publisher rsp-launch-urdf-file.xml
[INFO] [launch]: All log files can be found below /home/cem/.ros/log/2021-02-09-11-18-06-411110-cem-x1e-196727
[INFO] [launch]: Default logging verbosity is set to INFO
[INFO] [robot_state_publisher-1]: process started with pid [196827]
[robot_state_publisher-1] Parsing robot urdf xml string.
[robot_state_publisher-1] [INFO] [1612887486.486491405] [robot_state_publisher]: got segment base_link If I give robot_description as an argument, it works. <!-- Working. Gives a deprecation warning as expected -->
<launch>
<arg name="namespace" default="eca_a9"/>
<node
name="robot_state_publisher"
pkg="robot_state_publisher"
exec="robot_state_publisher"
output="screen"
args="$(find-pkg-share eca_a9_description)/robots/generated/$(var namespace)/robot_description"
>
</node>
</launch> However, If I try to use the method that used in the example in another launch file like as shown it fails poorly. <!-- Not working -->
<launch>
<arg name="namespace" default="eca_a9"/>
<node
name="robot_state_publisher"
pkg="robot_state_publisher"
exec="robot_state_publisher"
output="screen"
>
<param name="robot_description" value="$(command 'cat $(find-pkg-share eca_a9_description)/robots/generated/$(var namespace)/robot_description')"/>
</node>
</launch> And this is how it fails
At this moment, I'm not quite sure if it's the gazebo complaining or the launch file failed to parse the argument. |
Oh, I see. OK, this is a problem with the launch infrastructure and more complicated pieces of XML. I'm not entirely sure of the fix here. I'm going to close this as a duplicate of ros2/launch_ros#214 , which is the same issue. |
Hi @clalancette Not sure if you still have this issue persists or not. But here's how i get it work on
Above launch.xml also show how to use Hope it helps. Best, |
<param/>
key no longer substitute$(command ...)
. But it's still in use in the examples.Branch is Foxy
robot_state_publisher/launch/rsp-launch-urdf-file.xml
Line 37 in d8b471b
Am I missing something? If a change needed I can make it.
The text was updated successfully, but these errors were encountered: