-
Notifications
You must be signed in to change notification settings - Fork 10
simulator development
Follow this step-by-step guide to start developing with simulated robots. Make sure to complete the initial setup before proceeding further.
Content:
Note 1: If no Nvidia drivers are present, the Docker runtime is set to
runc
, instead ofnvidia
, to bypassnvidia-docker2
when entering the container. However, 3D accelerated tools, including Gazebo and Rviz, will most likely not work. You can modify the default runtime in~/.bashrc
.
-
Run the Docker container:
cd ~/ur-o2as && sh RUN-CONTAINER.sh
```
-
If you only want to run the robots, execute this:
roslaunch o2as_moveit_config demo.launch
-
Alternatively, if you need to simulate cameras and parts, you should launch Gazebo via
roslaunch
, and then MoveIt from a separate terminal window:roslaunch o2as_gazebo o2as_gazebo.launch roslaunch o2as_moveit_config o2as_moveit_planning_execution.launch sim:=true
See the ReadMe in the o2as_moveit_config package for more details on how to move the robots with the MoveIt GUI. For sending motion commands from another node, read the below.
-
Enter the Docker container from a new terminal window:
cd ~/u2-o2as/ && ./RUN-DOCKER-CONTAINER.sh
-
Use MoveIt from inside a ROS node. Example:
roslaunch o2as_examples example_tf_moveit.launch
The example above requires MoveIt to be launched. See Step 1 or the readme of o2as_moveit_planner for more information.
-
If Gazebo is running, it is publishing the different camera streams as rostopics. To display an image stream:
rosrun rqt_image_view rqt_image_view
You can use
rostopic list
to see other available data streams.
-
Start up the skill server:
roslaunch o2as_skill_server o2as_skill_server.launch
-
Check the example in the o2as_routines package, which shows how to make a Python script using the high-level actions offered by the skill server.