ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange |
1 | initial version |
You can perform a workaround by putting the delayed node into an extra launch file and run it via timed_roslaunch
.
Explanation goes here.
In your case:
<launch>
<node name="talker" pkg="roscpp_tutorials" type="talker" />
<node pkg="timed_roslaunch" type="timed_roslaunch.sh" args="1 roscpp_tutorials my_listener.launch"
name="timed_roslaunch" output="screen" />
</launch>
Content of my_listener.launch
<launch>
<node name="listener" pkg="roscpp_tutorials" type="listener" />
</launch>
2 | No.2 Revision |
You can perform a workaround by putting the delayed node into an extra launch file and run it via timed_roslaunch
.
Explanation goes here.
In your case:
<launch>
<node name="talker" pkg="roscpp_tutorials" type="talker" />
<node pkg="timed_roslaunch" type="timed_roslaunch.sh" args="1 roscpp_tutorials my_listener.launch"
my_listener.launch" name="timed_roslaunch" output="screen" />
</launch>
Content of my_listener.launch
<launch>
<node name="listener" pkg="roscpp_tutorials" type="listener" />
</launch>
3 | No.3 Revision |
You can perform a workaround by putting the delayed node into an extra launch file and run it via timed_roslaunch
.
Explanation goes here.
Script is available here.
In your case:
<launch>
<node name="talker" pkg="roscpp_tutorials" type="talker" />
<node pkg="timed_roslaunch" type="timed_roslaunch.sh" args="1 roscpp_tutorials my_listener.launch" name="timed_roslaunch" output="screen" />
</launch>
Content of my_listener.launch
<launch>
<node name="listener" pkg="roscpp_tutorials" type="listener" />
</launch>