Bryan's Drone Report

When we first started working with the AR drones, me and other classmates were checking the hardware and mechanic stability of each drone. I helped examine each drone, as well as test each of the drones in freeflight to determine which drones worked the best and which ones could not be used. Many of the drones had problems, and while working with autoflight, more drones became unusable.

When I first started working with autoflight, I had little to no issues with making my code until the last days of working. I spent the first 2 days trying to figure out how to make the drone flip through autoscript, but I had to abandon that idea since the flip command did not work. For the rest of the working week, I resolved to make a code for the drone to fly forward then back to make it stop, rotate 180 degrees, and move around in a small circle. One difficulty I had in doing this was that I tried using the abstracted rotate command in my code, and my drone would not rotate. Also, the drone would go out of control when I was using the rotate command in my code, which was also a big problem my peers had. I had to stop using the rotate command entirely and use the move_time command, setting numbers for phi and yaw and also the time I wanted the drone to keep flying in a circle, and setting all the other inputs to 0. I also had to stop using the up command because when I used it, it would keep going up. This may have been because I set it to keep going up until it reached a certain altitude, but I also set a time limit, and the drone would still lose control, so I had to take the up command out of my code.


This is the final code I made:

This is my drone flying with my final code: