-
-
Notifications
You must be signed in to change notification settings - Fork 160
Example Universal Robots
This package provides an interface between ROS2 and the UR3e, UR5e, and UR10e simulation models of the Universal Robots running in Webots. It includes several simulations of these robots.
This simulation can be started with the following launch file:
ros2 launch webots_ros2_universal_robot universal_robot.launch.py
This simulation contains one UR5e robot in a very simple environment.
This example shows how you can control the robotic arm by moving it in RViz with the help of MoveIt2
.
Run the the following launch file to test it:
ros2 launch webots_ros2_universal_robot moveit_demo_launch.py
Then you will be able to move the robotic arm in RViz and press Plan & Execute
to see the same movement in the Webots simulation.
This example shows how you can make control multiple robots to collaborate in a single simulation.
Run the UR5e and IRB 4600 simulation in Webots using:
ros2 launch webots_ros2_universal_robot multirobot_launch.py
before webots_ros2 1.1.2
This simulation uses a new Webots feature to export URDF. Therefore, you will be able to change the robot model in Webots and to see the changes in RViz.
ros2 launch webots_ros2_universal_robot universal_robot_rviz_dynamic.launch.py
Note that the visual elements are still not supported, only the transforms will be shown.
This simulation can be started with the following launch file:
ros2 launch webots_ros2_universal_robot universal_robot_multiple.launch.py
This simulation contains a UR3e and a UR5e robot in a simple factory environment. This is a very good example showcasing how to use the multi-robots support with the Webots-ROS2 interface.
This world contains UR5e robot with 3D LiDAR.
ros2 launch webots_ros2_core robot_launch.py \
executable:=webots_robotic_arm_node \
world:=$(ros2 pkg prefix webots_ros2_universal_robot --share)/worlds/universal_robot_lidar.wbt
The /ur_joint_trajectory_controller/follow_joint_trajectory
action server can be tested directly using the ROS2 action CLI interface to move the robot (if more than one robot is present in the simulation, the action name should be changed, e.g. /UR3e/ur_joint_trajectory_controller/follow_joint_trajectory
):
ros2 action send_goal /follow_joint_trajectory control_msgs/action/FollowJointTrajectory "{
trajectory: {
joint_names: [shoulder_pan_joint, shoulder_lift_joint, elbow_joint, wrist_1_joint, wrist_2_joint, wrist_3_joint],
points: [
{ positions: [3.02, -1.63, -1.88, 1.01, 1.51, 1.13], velocities: [0.1, 0.1, 0.1, 0.1, 0.1, 0.1], accelerations: [0.1, 0.1, 0.1, 0.1, 0.1, 0.1], time_from_start: { sec: 5, nanosec: 500 } },
{ positions: [-1.01, 0.38, -0.63, -0.88, 0.25, -1.63], velocities: [0.1, 0.1, 0.1, 0.1, 0.1, 0.1], accelerations: [0.1, 0.1, 0.1, 0.1, 0.1, 0.1], time_from_start: { sec: 6, nanosec: 500 } },
{ positions: [-1.01, 0.38, -0.63, -0.88, 0.25, 6.2], velocities: [0.1, 0.1, 0.1, 0.1, 0.1, 0.1], accelerations: [0.1, 0.1, 0.1, 0.1, 0.1, 0.1], time_from_start: { sec: 50, nanosec: 500 } }
]
},
goal_tolerance: [
{ name: shoulder_pan_joint, position: 0.01 },
{ name: shoulder_lift_joint, position: 0.01 },
{ name: elbow_joint, position: 0.01 },
{ name: wrist_1_joint, position: 0.01 },
{ name: wrist_2_joint, position: 0.01 },
{ name: wrist_3_joint, position: 0.01 }
]
}"
before webots_ros2 1.1.2
Use /follow_joint_trajectory
instead of /ur_joint_trajectory_controller/follow_joint_trajectory
and /UR3e/follow_joint_trajectory
instead /UR3e/ur_joint_trajectory_controller/follow_joint_trajectory
in case more than one robot is present in the simulation.
The joint state (/joint_states
topic) can be displayed directly using the ROS2 topic CLI interface (if more than one robot is present in the simulation, the action name should be changed, e.g. /UR3e/joint_states
):
ros2 topic echo /joint_states
- The Ros2Supervisor Node
- Using URDF or Xacro
- Import your URDF Robot in Webots
- Refresh or Add URDF a Robot in a Running Simulation
- Wheeled robots
- Robotic arms
- Automobiles
- Drones