The site is read-only. Please transition to use Robotics Stack Exchange
| ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange |
 | 1 | initial version |
The comman <rosparam command="load" file="$(find husky_highlevel_controller)/config/laser_enable_param.yaml"/> puts the parameters on the parameter server. The launchfile spawn_husky.launch expects the data as a launch file argument, though. This is a differenct concept Think of it as a parameter of a function (launch file argument) versus global variables (rosparam server).
| | 2 | No.2 Revision |
The comman command <rosparam command="load" file="$(find husky_highlevel_controller)/config/laser_enable_param.yaml"/> puts the parameters on the parameter server. The launchfile spawn_husky.launch expects the data as a launch file argument, though.
This is a differenct different concept Think of it as a parameter of a function (launch file argument) versus global variables (rosparam server).
| | 3 | No.3 Revision |
The command <rosparam command="load" file="$(find husky_highlevel_controller)/config/laser_enable_param.yaml"/> puts the parameters on the parameter server. The launchfile spawn_husky.launch expects the data as a launch file argument, though.
This is a different concept concept. Think of it as a parameter an argument of a function (launch file argument) versus global variables (rosparam server).
| | 4 | No.4 Revision |
The command <rosparam command="load" file="$(find husky_highlevel_controller)/config/laser_enable_param.yaml"/> puts the parameters on the parameter server. The launchfile spawn_husky.launch expects the data as a launch file argument, though.
This is a different concept. Think of it as an argument of a function (launch file argument) versus global variables (rosparam server).
You can just put it in your launchfile, tough:
<include file="$(find husky_gazebo)/launch/spawn_husky.launch">
<arg name="laser_enabled" value="true"/>
</include>
ROS Answers is licensed under Creative Commons Attribution 3.0 Content on this site is licensed under a Creative Commons Attribution Share Alike 3.0 license.