Gazebo:Tutorials:pioneer2dx moving

From The Player Project

(Difference between revisions)
Jump to: navigation, search
m (Reverted edits by Kirkpatricky (talk) to last revision by Rmattes)
 
(4 intermediate revisions not shown)
Line 95: Line 95:
  </code>
  </code>
The '''provides''' tag tells this driver what type of interface this driver uses, and the gz_id tells the driver where to find the matching Gazebo interface. This name must match a name in the Gazebo shared memory interfaces.
The '''provides''' tag tells this driver what type of interface this driver uses, and the gz_id tells the driver where to find the matching Gazebo interface. This name must match a name in the Gazebo shared memory interfaces.
 +
 +
[[Category:Gazebo]]
 +
[[Category:Documentation]]]
 +
[[Category:Tutorials]]

Latest revision as of 15:58, 23 August 2011

Contents

Overview

We assume that you have installed both Gazebo and Player locally (in your home directory).

This tutorial demonstrates how to move a robot around in Gazebo using a graphical tool in Player called playerv. By the end of this tutorial, you will know how to launch Gazebo, edit a player config file to correspond to a robot in Gazebo, and use the playerv tool to move the robot around.

Launching Gazebo

The first step is to launch Gazebo and place a robot in the world. Gazebo takes at a minimum one command line argument, which is a word file. This file tells Gazebo how to setup the world, and what to place in it. We won't delve into the guts of the world file in this tutorial.

First go to the location of all the default world files.


$ cd ~/local/share/gazebo/worlds

Now run gazebo with the pioneer2dx.world file


$ gazebo pioneer2dx.world

At this point, a new window should appear that contains a Pioneer2dx sitting on a flat surface.

Launching Player

Once Gazebo is up and running, you can also run Player to control robots inside Gazebo.

In a new terminal:


$ cd ~/local/share/gazebo/player_cfgs

Run player:


$ player gazebo.cfg

Not too much will happen here. Player should output something along the lines of:


Gazebo Plugin driver creating 1 device
 6665.31.0 is  a simulation interface.
Gazebo Plugin driver creating 1 device
 6665.4.0 is  a position2d interface.
Gazebo Plugin driver creating 1 device
 6665.6.0 is  a laser interface.
listening on 6665
Listening on ports: 6665 

Controlling the Robot

Now that the simulated robot is running in Gazebo and the Player is running, we can control the robot using a graphical interface called playerv.

In a new terminal:


$ playerv -h localhost

A window will pop-up that should a few menu items and a grid.

  1. Select the Devices menu item, then Position2d:0, then Subscribe.
  2. Select the Devices menu item, then Position2d:0, then Enable.
  3. Select the Devices menu item, then Position2d:0, then Command.

At this point a red box and cross-hair should be visible in playerv. Left-click on the cross hair and drag it around. Once you do this, the robot in Gazebo should move.

If you want to see the output from the laser:

  1. Select the Devices menu item, then Laser:0, then Subscribe.

Behind the Scenes

Here is a little insight into what's going on.

Gazebo uses a shared memory interface to communicate with the other programs. The shared memory files are created once Gazebo is started, and are found in:


/tmp/gazebo-<user_name>-0/

List the contents of that directory, and you'll see all the interfaces to entities in Gazebo. Note the Position2d and Laser interfaces.


$ ls /tmp/gazebo-<user_name>-0/
...
position.pioneer2dx_model1::position_iface_0
laser.pioneer2dx_model1::laser_iface_0
...

Here is how the filenames break down: <interface_type>.<gazebo_model>.<interface_name>. For the position2d interface, the type is position, the model which contains the interface (or your can think of this as the model that is controlled by the interface) is the pioneer2dx_model1, and the name of the interface itself is position_iface_0.

This information is used in the Player configuration file. Take a look at the gazebo.cfg file used previously in this tutorial. Look at this section:


driver
(
 name "gazebo"
 provides ["position2d:0"]
 gz_id "pioneer2dx_model1::position_iface_0"
)

The provides tag tells this driver what type of interface this driver uses, and the gz_id tells the driver where to find the matching Gazebo interface. This name must match a name in the Gazebo shared memory interfaces.]

Personal tools