How to set up crazyflie_ros with a VICON motion capture system?

Use the hover_vicon.launch file from the demo package, specifying the Crazyflie URI and tf-frame, but you'll need to install and configure vicon_bridge separately. The README provides example commands with parameters like frame and coordinates.

crazyflie_ros vs Crazyswarm: which should I use for my project?

Crazyswarm is the recommended successor, offering better features and active maintenance. Use crazyflie_ros only if you have legacy code or need specific functionalities not yet ported to Crazyswarm, as per the deprecation warning.

Can I use crazyflie_ros for autonomous navigation without motion capture?

No, the included PID controller for waypoint navigation requires external pose estimation from systems like VICON. For basic teleoperation or sensor logging, motion capture isn't needed.

How to add and control multiple Crazyflies in crazyflie_ros?

Use the multi_teleop_xbox360.launch file with unique URIs for each Crazyflie, ensuring they have different addresses and share the same channel/datarate. The scan tool helps find connected drones.

Is crazyflie_ros compatible with Crazyflie 2.0 and stock firmware?

Yes, it supports both Crazyflie 1.0 and 2.0 using the stock firmware, as highlighted in the README's features, without requiring custom modifications.

How to teleoperate a Crazyflie with a joystick using crazyflie_ros?

Run the teleop_xbox360.launch with the correct URI parameter, which maps joystick inputs to the cmd_vel topic for control. The README includes an example command with URI specification.

Open-Awesome

crazyflie_ros

MITC++

A deprecated ROS driver for Bitcraze Crazyflie quadcopters, enabling sensor data publishing, parameter control, and multi-drone operation.

GitHub

199 stars208 forks0 contributors

What is crazyflie_ros?

crazyflie_ros is a ROS driver stack for Bitcraze Crazyflie nano quadcopters, enabling integration of drone hardware into ROS-based robotic systems. It provides sensor data publishing, parameter control, and multi-drone operation capabilities without requiring the Bitcraze SDK. The project simplifies developing autonomous drone applications by leveraging ROS's messaging and tooling ecosystem.

Target Audience

Robotics researchers, academic labs, and developers working with Crazyflie drones in ROS environments, particularly those needing multi-drone control or motion capture integration.

Value Proposition

It offers a fully open-source, SDK-independent C++ implementation with multi-drone support and ROS-standard interfaces, making it more flexible and integrable than vendor-specific solutions for research and prototyping.

Overview

ROS Driver for Bitcraze Crazyflie

Use Cases

Best For

Integrating Crazyflie drones into existing ROS-based robotic systems
Academic research requiring multi-drone coordination experiments
Prototyping drone applications with motion capture systems like VICON
Teleoperating Crazyflies via joystick in ROS environments
Accessing Crazyflie sensor data through standard ROS messages
Developing waypoint navigation controllers for Crazyflie quadcopters

Not Ideal For

New projects requiring active maintenance and updates (deprecated, successor available)
Applications needing to control large fleets (>3 drones per dongle due to bandwidth limits)
Teams without motion capture systems for advanced navigation features
Developers seeking a fully documented, plug-and-play ROS package

Pros & Cons

Pros

Multi-Drone Support

Allows operation of multiple Crazyflie 1.0/2.0 drones with a single Crazyradio, facilitating swarm experiments as demonstrated in the multi_teleop launch files.

SDK-Independent Implementation

Written in C++ without Bitcraze SDK dependencies, offering flexibility and direct hardware control for research, as stated in the README's philosophy.

ROS Standard Integration

Publishes sensor data like IMU, temperature, and battery in standard ROS message formats, ensuring compatibility with ROS tools like rviz.

Extensive Demo Suite

Includes launch files for teleoperation, hover, and waypoint navigation, providing quick-start examples for developers, as shown in the crazyflie_demo package.

Cons

Deprecated Project Status

Marked as deprecated with the author recommending Crazyswarm instead, meaning no future updates, bug fixes, or official support.

Bandwidth Limitations

Performance degrades with more than 3 drones per Crazyradio dongle due to bandwidth constraints, limiting scalability for large swarms.

Motion Capture Dependency

Advanced features like waypoint navigation require external systems like VICON, adding cost and setup complexity, as noted in the controller package.

Complex Initial Setup

Requires ROS, catkin workspace, and git submodule initialization, which can be challenging for those unfamiliar with ROS ecosystems.

Frequently Asked Questions

Related Projects

Tesla-API

🚘 A Ruby gem and unofficial documentation of Tesla's JSON API for the Model S, 3, X, and Y.

Stars2,056

Forks535

Last commit2 months ago

ROS driver

ROS support for Velodyne 3D LIDARs

Stars715

Forks684

Last commit9 months ago

ublox

A driver for ublox gps

Stars530

Forks441

Last commit8 months ago

livox_ros_driver

Livox device driver under ros, support Lidar Mid-40, Mid-70, Tele-15, Horizon, Avia.

Stars492

Forks251

Last commit2 years ago

Community-curated · Updated weekly · 100% open source

Found a gem we're missing?

Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.

Submit a project Star on GitHub