Skip to content
Buzz as a ROS package
Branch: master
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Type Name Latest commit message Commit time
Failed to load latest commit information.
include/rosbuzz move rosbuzz headers and reneabled pursuit and graph formation from w… Apr 10, 2019
misc Add spiri case to Sep 26, 2018
msg Neighbours pos publisher addition Jan 9, 2017
src beautified Apr 10, 2019
.gitignore logger addition Aug 31, 2017
CMakeLists.txt implemented Voronoi Centroid tessellation - still need works Nov 7, 2018
package.xml minor fix from sitl Sep 7, 2018



ROSBuzz is a ROS node encompassing Buzz Virtual Machine (BVM) and interfacing with ROS ecosystem for mobile robots. The only node of the package is rosbuzz_node. It can be used in simulation-in-the-loop using Gazebo and was tested over many platforms (Clearpath Husky, DJI M100, Intel Aero, 3DR Solos, Pleidis Spiris, etc.). More information about ROSBuzz peripheral nodes is available in [1].

What is Buzz?

Buzz is a novel programming language for heterogeneous robots swarms. Buzz advocates a compositional approach, by offering primitives to define swarm behaviors both in a bottom-up and in a top-down fashion. Its official documentation and code are available Buzz.


  • Buzz:

Follow the required steps in Buzz.

  • ROS base binary distribution (Indigo or higher):

Follow the required steps in ROS Kinetic. Note that the guidance and camera node of DJI for the M100 require to use the Indigo distribution.

  • ROS additionnal dependencies:
$ sudo apt-get install ros-<distro>-mavros ros-<distro>-mavros-extras


mkdir -p ROS_WS/src
cd ROS_WS/src
git clone rosbuzz
cd ..
catkin_make -DSIM=0 -DKIN=1

Compilation Flags

Flags to be passed during compilation.

Flag Rationale
-DSIM Indicates Compilation for robot or Simulation.
-DKIN Indicates compilation for ROS Distro Kinetic

Source ROS environment

source /opt/ros/kinetic/setup.bash
source ~/ROS_WS/devel/setup.bash


To run the ROSBuzz package using the launch file, execute the following:

$ roslaunch rosbuzz rosbuzz.launch

Have a look at the launch file to understand what parameters are available to suit your usage. All topics and services names are listed in launch_config/topics.yaml. Note : Before launching the ROSBuzz node, verify all the parameters in the launch file. A launch file using gdb is available too (rosbuzzd.launch).

A launch file for a groundstation is also available launch/groundstation.launch. It uses the robot ID = 0, which is detected as a groundstation by our Buzz scripts. It also has hardcoded GPS coordinates to avoid the need of a GPS sensor on the groundstation. While a groundstation is never required to deploy a swarm with ROSBuzz, it opens a websocket on ROS, useful to monitor the swarm and it creates a rosbag of the flight.

  • Buzz scripts: Several behavioral scripts are included in the "buzz_Scripts" folder, such as "graphformGPS.bzz" uses in [1] and the "testaloneWP.bzz" to control a single drone with a ".csv" list of waypoints. The script "empty.bzz" is a template script.


  • Messages from Buzz (BVM): The node publishes mavros_msgs/Mavlink message "outMavlink".

  • Command to the flight controller: The node publishes geometry_msgs/PoseStamped message "setpoint_position/local".

  • Other information from the swarw: The node publishes:

    • "bvmstate" (std_msgs/String)
    • "neighbours_pos" (rosbuzz_msgs/neigh_pos)
    • "fleet_status" (mavros_msgs/Mavlink)


  • Information from the Robot controller (mavros compliant): The node subscribes to:

    • "global_position/global" (sensor_msgs/NavSatFix message)
    • "global_position/rel_alt" (std_msgs/Float64)
    • "local_position/pose" (geometry_msgs/PoseStamped)
    • "battery" (sensor_msgs/BatteryState)
    • either "extended_state" (mavros_msgs/ExtendedState) or "state" (mavros_msgs/State)
  • Messages to Buzz (BVM): The node subscribes to mavros_msgs/Mavlink incoming message with name "inMavlink".


  • Remote Controller: The package offers a service "buzzcmd" (mavros_msgs/CommandLong) to control it. In the "misc" folder, a bash script shows how to control the swarm state from the command line.


  • [1] ROS and Buzz : consensus-based behaviors for heterogeneous teams. St-Onge, D., Shankar Varadharajan, V., Li, G., Svogor, I. and Beltrame, G. arXiv :

  • [2] Over-The-Air Updates for Robotic Swarms. Submitted to IEEE Software (August 2017). 8pgs. Shankar Varadharajan, V., St-Onge, D., Guß, C. and Beltrame, G.

Visual Studio Code

To activate highlights of the code in Visual Studio Code or Roboware add the following to settings.json:

    "files.associations": {
You can’t perform that action at this time.