This week we decided to do our weekly meeting at the local pub. Why? We needed some beer to calm our nerves and to get some expert advice from Martin, one of our collegues, that has presented at a lot of conferances. The reason for this is that in about two weeks we are presenting the Crazyflie project at the annual Øredev developer conference in Malmo, Sweden.

The presentation will be a mix of the project history, some tech details and of course a demo (hopefully a successful one without any injuries ;-) ).

So if you are attending Oredev drop by our presentation on the 7th of November at 15:40 in the Nyan Cat room and we will do our best to give you an interesting 50 minutes.

Last summer we were sitting in a meeting room after office hours discussing how we should react to the fact that a lot of people seemed to want to buy a Crazyflie. After having a bit of down time in the project we finally posted a video, that was already about 6 months old, on Youtube.  It was during the spring 2011 showing us flying the first prototype Crazyflie. After getting picked up by Hackaday it got a lot more attention that we originally thought and a lot of people wanted to buy one which was great! The only problem was that we only had three of them and at this time there where already obsolete components. Another problem was that the motors/propellers were scavenged from toy airplanes (they had a sale and we got them cheep) which was not a scalable sourcing solution.

So sitting in this meeting room we decided to give this project a shot by trying to release a kit that could be sold. Back then the development was funded by Epsilon, the consulting company that we are working for, which was not optimal if we wanted to commercialize the Crazyflie. So we decided (after a lot of discussions) to form a company which became Bitcraze AB (the name came after even more discussions). We needed a company to make manufactures and distributors take us seriously and for import and tax reasons. It is also pretty satisfactory to be on the board of director of our own company :-).

At this time the Crazyflie was already flying but it had to be redesigned, parts sourced and we needed to find someone to manufacture it for us. Since we didn’t (and still don’t) have that much capital this wasn’t something that we could leave our day-jobs for so the development continued on weeknights and weekends. As anyone working with product development (specially if it includes any type of hardware), going from a prototype that is working to a final product requires a lot of work.

A big obstacle for us was sourcing the mechanical parts: Motors, propellers, motor mounts and battery. Some of these can be found and some are harder. And even if you find something that looks good on paper there’s no guarantee that it’s very good or working at all. We got some motors that seemed like they were scavenged from the junkyard (and probably were), we got batteries that didn’t meet the specification and propellers that were unbalanced. All this takes a lot of time. Finally we had to design a motor mount ourselves since we couldn’t find anything that suited our purpose. After a lot of searching/testing we finally found good batteries and motors. The propellers are still a bit hard to find a reliable source for but we think that we have it sorted out.

Even though it’s been very frustrating at times, like when the Invensense gyros we were using went out of production, we have a lot of fun when we work (which you can hear in the videos). Also we have been challenged to learn new stuff and got to try things that we normally would’t do at work. One of the reasons we started the project at all back in the fall of 2009 was that we wanted to do something more challenging and we think that we achieved that :-)

So what’s the plan for the upcoming year? Well, the main plan is to release the kit soon of course! After that there’s a lot of ideas of what we want to do so we will have to see how things go. Also we would like to thank everyone that’s been following our progress and supporting the project!

[Show as slideshow]

No, the candle isn’t burning when we are flying…although we did try to…

We have noticed that there’s a lot more work to be done in this project than only designing hardware and developing software :-) It’s now about 14 months ago that we decided to make a Crazyflie kit that we would try to sell. At that point we had already had the first version of the Crazyflie flying for about 1 year. The list of things that we have done since then is pretty long…a lot longer that we first thought it would be. But let’s save that list for another post…

One of the things that we’ve had to spend some time on is setting up our IT environment and now we are trying to make the final push. Up until now we have been using Mercurial/Redmine hosted on our own VPS. Here’s a list of what we are thinking about using in the future:

• CM for code and schematics: Bitbucket
• Issue handling: Bitbucket
• Wiki: Dokuwiki
• Forum: phpBB
• Blog: WordPress :-D

Any thoughts or ideas about these? Any services that’s missing? Anyone that has good/bad experience with Bitbucket?

A couple of weeks ago we discovered that the sensors of our new prototype where not functioning. We have now received new MPU-6050 sensors from Seeedstudio that we are going to solder with hot-air during the week (photos of the soldering will be posted during later this week).

On the manufacturing side we received the motors we will use which brings us one step closer to making the Crazyflie available (as long as everything else is working :-))

On the software side we are working hard to clean up the copter firmware and PC client architecture. The goal is to make it as easy as possible to setup and fly but also to modify or tweak.

During this spring we have been involved in a Master thesis together with Epsilon. The goal for the thesis was to embed a camera module on the Crazyflie so it could be remotely controlled. Finding a lightweight camera module with access to documentation without buying a million units turned out to be trickier then we thought. The aptina MT9D131 was chosen as it can be bought from normal distributors, there is access to documentation and it has on-board JPG compression. The NRF24L01 radio was tested to see if it could handle low resolution video streaming, and it could, so no additional radio was needed. An addon board was built which could attach to the Crazyflie expansion port and it was called… Crazycam! (I wonder when we will become crazy for real :-)) . The Crazycam board uses the same STM32F103CB MCU that the Crazyflie uses to read out images from the camera chip.

Crazycam v0.1 (sensor side, mcu side, with mounted lens)

It turned out that the bandwidth to read out the images from the MT9D131 to the STM32 wasn’t enough and finding lightweight lenses was not that easy so the end result wasn’t as good as we hoped for. It wights about 5g and can stream images at about 6FPS. There are still things to try out and in theory it should handle 15-20FPS. It might be fixable so it ain’t over yet. If you would like to read the full report it is available at Linköpings university under the link “fulltext”. Even though we didn’t get all the way Thomas and Joakim, the authors, did a great job!