RotorS is a MAV gazebo simulator. It provides some multirotor models such as the AscTec Hummingbird, the AscTec Pelican, the AscTec Firefly, but the simulator is not limited for the use with these multicopters.
There are simulated sensors coming with the simulator such as an IMU, a generic odometry sensor, and the VI-Sensor, which can be mounted on the multirotor.
This packages also contains some example controllers, basic worlds, a joystick interface, and example launch files.
- Install and initialize ROS indigo desktop full, additional ROS packages, catkin-tools, and wstool:
$ sudo sh -c 'echo "deb http://packages.ros.org/ros/ubuntu `lsb_release -sc` main" > /etc/apt/sources.list.d/ros-latest.list'
$ wget http://packages.ros.org/ros.key -O - | sudo apt-key add -
$ sudo apt-get update
$ sudo apt-get install ros-indigo-desktop-full ros-indigo-joy ros-indigo-octomap-ros python-wstool python-catkin-tools
$ sudo rosdep init
$ rosdep update
$ source /opt/ros/indigo/setup.bash
- If you don't have ROS workspace yet you can do so by
$ mkdir -p ~/catkin_ws/src
$ cd ~/catkin_ws/src
$ catkin_init_workspace # initialize your catkin workspace
$ wstool init
Note for setups with multiple workspaces please refer to the official documentation at http://docs.ros.org/independent/api/rosinstall/html/ by replacing
rosws
bywstool
.
- Get the simulator and additional dependencies
$ cd ~/catkin_ws/src
$ git clone git@github.com:ethz-asl/rotors_simulator.git
$ git clone git@github.com:ethz-asl/mav_comm.git
Note if you want to use
wstool
you can replace the above commands withwstool set --git local_repo_name git@github.com:organization/repo_name.git
- Build your workspace with
python_catkin_tools
(therefore you needpython_catkin_tools
)
$ cd ~/catkin_ws/
$ catkin init # If you haven't done this before.
$ catkin build
- Add sourcing to your
.bashrc
file
$ echo "source ~/catkin_ws/devel/setup.bash" >> ~/.bashrc
$ source ~/.bashrc
Launch the simulator with a hex-rotor helicopter model, in our case, the AscTec Firefly.
$ roslaunch rotors_gazebo mav_empty_world.launch mav_name:=firefly
Note The first run of gazebo might take considerably long, as it will download some models from an online database.
The simulator starts by default in paused mode. To start it you can either
-
use the Gazebo GUI and press the play button
-
or you can send the following service call.
$ rosservice call gazebo/unpause_physics
There are some basic launch files where you can load the different multicopters with additional sensors. They can all be found in ~/catkin_ws/src/rotors_simulator/rotors_gazebo/launch
.
To let the multicopter fly you need to generate thrust with the rotors, this is achieved by sending commands to the multicopter, which make the rotors spin. There are currently a few ways to send commands to the multicopter, we will show one of them here. The rest is documented here in our Wiki. We will here also show how to write a stabilizing controller and how you can control the multicopter with a joystick.
We will for now just send some constant motor velocities to the multicopter.
$ rostopic pub /firefly/command/motors mav_msgs/CommandMotorSpeed '{motor_speed: [100, 100, 100, 100, 100, 100]}'
Note The size of the
motor_speed
array should be equal to the number of motors you have in your model of choice (e.g. 6 in the Firefly model).
You should see (if you unpaused the simulator and you have a multicopter in it), that the rotors start spinning. The thrust generated by these motor velocities is not enough though to let the multicopter take off.
You can play with the numbers and will realize that the Firefly will take off with motor speeds of about 545 on each rotor. The multicopter is unstable though, since there is no controller running, if you just set the motor speeds.
You can let the helicopter hover with ground truth odometry (perfect state estimation), by launching:
$ roslaunch rotors_gazebo mav_hovering_example.launch mav_name:=firefly
TODO(ff): Write something here.
TODO(ff): Write something here.