The Royal Institution approached Bristol Robotics Lab in November 2014 to ask if we could contribute a drone to their robot orchestra project, inspired by this YouTube video and others. The brief was quite broad: get a drone to play something somehow. We agreed to investigate and see what we could do. In particular, we made this a "crash project" for the new FARSCOPE students, perhaps a poor choice of term under the circumstance, but highlighting the emphasis on simplicity and timeliness of whatever we came up with.
Drones are tough to control with great accuracy, so we quickly narrowed our ideas down to percussion. My personal, and slightly ironic, wish was to have a drone play the triangle This urge was quickly subdued, both by the drowning of the triangle sound by the motor noise, and the alarming response of the drone when affixed with a beater and flown into a triangle. It was clear that some sort of transmission would be required to strike the instrument. Electrical transmission was ruled out, as we wanted it to be obvious that it was really the drone making the noise. Therefore, we had a requirement for a mechanism that would convert some motion of the drone into motion of the beater striking the instrument.
|CDT Student Dave wheels the drone kit into the Faraday Lecture Theatre|
Meanwhile, other details had been falling into place. Students had been building QAV250 quadrotor drones and equipping them with Naze32 flight stabilizers. These turned out to be excellent machines, mechanically robust, well-stabilized, and easy to fly for beginners, so very suited to our needs. Some Arduinos were programmed to take commands from our ROS environment and convert them to PWM streams for the trainer port of our radio transmitters, with an added emergency stop functionality. With our Vicon motion capture system tracking the drone, we were able to close the loop. One day we may share the radio control bridge and PID tuning packages with the ROS community, but it's the nature of crash projects that things aren't done as tidily as they could be.
|Students put finishing touches to the drone landing pad in the RI library|
One surprise was yet to come: the producers liked the drone so much they wanted to make more of it, so we quickly contrived a demo for it to follow an external target. For comedy reasons and as a nod to the computer vision world, it had to be a teapot. It's a great credit to the students involved that an extra function was written into the software at about an hour's notice, but that went on to work beautifully.
|FARSCOPE students at the control station, backstage at the RI.|
So what do we learn from all this? Drones will clearly not be great musicians in the near future. Still, the students learnt a wide range of practical skills through this exercise, from ROS use to drone construction. Time management, teamwork and the importance of testing were also reinforced, although this was far from a good model of systems engineering. Finally, it was great for those of us running FARSCOPE in its first year to explore the flexibility and responsiveness that the Centre for Doctoral Training gives us.