It can fly up to 7 minutes and depending on how you fly it, the time will decrease.
It is charged using a standard micro-USB connector commonly used by smartphones. You probably have one of these cables at home. You can charge it from any USB unit that can supply 500mA, most computers and adapters do. It takes up to 40min to charge and the blue LED (M3) will tell you roughly how charged it is by how long it is lit. When it is fully lit it is fully charged.
Yes, you can hot swap batteries.
Yes, as long as it is not too heavy, it is a single cell (3.7V), it fits and the polarity is correct you can do so. A higher capacity battery will give you longer flight times but will also decrease agility. We recommend batteries with at least 15C continuous discharge rate.
The Crazyflie 2.X can be controlled with the Crazyradio or Crazyradio PA from a PC or with a mobile device using Bluetooth Low Energy.
Here is a list of requirements for the mobile device:
- Bluetooth Low Energy (BLE) or sometimes called Bluetooth Smart support.
- Runs Android 4.4 or newer
- Runs iOS 7.1 or newer
Since Android is available on many different devices, it is not certain it works even though it fulfills the requirements above. We have therefore created a list of devices it has been tested on.
As with all radio communication it depends. It depends on the environment, radio interference, chip production variations, etc. It also depends on if you use the Crazyradio, Crazyradio PA or a mobile device. We have done a couple of line-of-sight tests with little interference outdoor with the different configurations:
- Crazyradio: Up to about 100 meters range in the 250 Kbit mode (The uplink, Crazyradio, is the limiting the range).
- Crazyradio PA: Up to about 1000 meters range in the 250 Kbit mode (The downlink, Crazyflie 2.X, is the limiting the range).
- Mobile device: Up to about 20 meters range (The uplink, mobile device is limiting the range).
This can be done with the BigQuad expansion deck. It’s working, but not yet a turn-key solution.
The Crazyflie 2.X is using the PCB itself as the frame. The PCB is made of FR4 which is a strong and lightweight material. Attached to that is the motor mount which is a bit flexible. The motor mount is designed in such a way that it will break in case of a violent crash and not the PCB or electronics. The motor mount is very easy to change and cheap. We have not yet been able to break anything except the motor mount or a motor during violent crashes and some have been from 30m height right on to concrete. It is not unbreakable though so handle it with care!
Yes, the firmware and the communication protocol is backward compatible. All libraries that have been made in Python, Ruby, C, C++, Java, etc. will be able to control the Crazyflie 2.X the same way.
Yes, The firmware and python client are working with the Crazyflie 1.0.
Yes, it can. With the BigQuad expansion deck.
There is ongoing development in this area:
The Crazyflie 2.X does not have enough sensors to locate itself in the environment as is, it requires more information to do that. The easiest way to acheive that is to add the Flow deck V2. It tells the Crazyflie how it moves relative to the floor and thus enables it to fly autonomously. See the product page for more information.
With an external positioning system the Crazyflie will even understand its absolute position which gives it even more possibilities when it comes to autonomous flight. Outdoors the Crazyflie could use a GPS receiver to achieve autonomous flight but indoors some other positioning system is required.
Researchers often use motion capture systems, like Qualisys or Vicon, to fly the Crazyflie autonomously, usually controlling it from an outside computer. For example this research from MIT is using such a system together with a powerful control algorithm: https://www.youtube.com/watch?v=v-s564NoAu0
We have been using camera systems like the Microsoft Kinect to achieve autonomous flight above the camera: https://www.bitcraze.io/2015/05/autonomous-flight-using-kinect2-for-position-control/
Want to add a FAQ? Improve this page