-
Notifications
You must be signed in to change notification settings - Fork 192
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
Adding Gazebo for rrbot #64
Conversation
<param name="example_param_hw_start_duration_sec">2.0</param> | ||
<param name="example_param_hw_stop_duration_sec">3.0</param> | ||
<param name="example_param_hw_slowdown">2.0</param> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is not parsed in the plugin
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe I misunderstood your comment, but this part is not included in the file generated by xacro because it is in the unless
statement.
Should it be included ?
@@ -0,0 +1,60 @@ | |||
# Copyright 2020 Open Source Robotics Foundation, Inc. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
# Copyright 2020 Open Source Robotics Foundation, Inc. | |
# Copyright 2021 Open Source Robotics Foundation, Inc. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Done through commit 68bdb89
…n_only_gazebo.launch.py
68bdb89
to
b18c780
Compare
@@ -14,6 +14,7 @@ | |||
<depend>hardware_interface</depend> | |||
<depend>pluginlib</depend> | |||
<depend>rclcpp</depend> | |||
<depend>gazebo_ros2_control</depend> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
you're missing an <exec_depend>xacro</exec_depend>
here.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks. Fixed in e6497f1
|
||
spawn_entity = Node(package='gazebo_ros', executable='spawn_entity.py', | ||
arguments=['-topic', 'robot_description', | ||
'-entity', 'cartpole'], |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
what's that cartpole doing here?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks. Fixed in e230567
@@ -5,7 +5,8 @@ Copied and modified from ROS1 example: | |||
https://github.com/ros-simulation/gazebo_ros_demos/blob/kinetic-devel/rrbot_description/urdf/rrbot.xacro | |||
--> | |||
<robot xmlns:xacro="http://www.ros.org/wiki/xacro" name="2dof_robot"> | |||
|
|||
<xacro:arg name="simu" default="false" /> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nitpick, but simu
sounds kinda weird. I'd propose either just sim
or something like use_sim
.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks. Fixed in 5e726d4
joints: | ||
- joint1 | ||
- joint2 | ||
interface_name: position |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@destogl can you explain what that interface name does here? I'd assume that the joints are sufficiently described in the ros2_control tag with their control and state interfaces names.
What if I use position
here and declare the joints as effort
?
I forget to mention one behavior that I found strange (or at least that I do not have with the original example from @ahcorde): gazebo takes a long time to start. Any feedback on this part is welcome. |
Nevermind, I actually tried it and the xacro substitution is really fast. Must be somewhere else. For what it's worth, I have the same delay on Linux as well as OSX. |
Superseded by #85 |
Objective
Following the nice work of @ahcorde on gazebo_ros2_control adding Gazebo for rrbot.
This pull requests modifies the rrbot_description to call the
gazebo_ros2_control
and theGazeboSystem
plugins.Given the interfaces of rrbot this is directly compatible.
The rrbot_system_description_position_only.urdf.xacro has been modified to take simu has parameter.
The default is false and switch quietly to the usual behavior.
If set to true it loads the gazebo system from
gazebo_ros2_control
.The
rrbot_gazebo.xacro
andrrbot_system_position_only.ros2_control.xacro
are modified accordingly.What is left ?
Major: Testing by sending commands to the system. Should we try to use the same forward_command_trajectory or use the same example than
gazebo_ros2_control
? The latter might lead to an unnecessary duplication of code between the two repositories.Minor: Modifying the README to launch the test:
ros2 launch ros2_control_demo_robot rrbot_system_position_only_gazebo.launch.py