The last week of the DTSF program when pretty well, I ended up using the QR codes and the mission pads to navigate the drone and update its navigation in route.
I decided to create two different navigation paths, one in which the drone simply takes off reads the QR code, adjusts itself if it’s not in frame and follows the given navigation, then uses a search grid at the end to complete the route and drop off the package. The second navigation route was longer to the point where it actually would navigate the drone down the hall and around the corner. This one was a little tough in that there was a lot of trouble shooting. The difficulties that I encountered are as follows:
- Weight distribution
- Height measurement
- QR code reading
I mention weight distribution because of the hook that I attached to the drone. The hook was taped to the drone via double sided sticky tape. It did not weigh too much but if I taped the hook slightly more to the right versus the left then the drone’s navigation would be impacted by this—shifting it more to the left or the right depending on how I taped the hook on.
Secondly, the drone’s measurement of height. This greatly impacted the reading of the QR code because the drone height measurement was not accurate in that it would return a different height measurement after each launching of the program. Why this is, I’m not sure but it turns out that the mission pads height detection was way more efficient, meaning that if I told the drone to go to a height of 50 it would do so, there would be no inaccurate height measurements.
Thirdly, the QR code reading. This was probably the most difficult thing I had to do throughout the whole project. The QR code reading method itself was not hard to code but the adjusting of the drone to get the drone to capture a good frame of the QR code, was. But looking back, the main reason why I was having so much trouble was because of the inaccurate height measurements. I’m just glad that we were able to sort out that problem in the end. Additionally, the end goal was to glue a QR code that contained the navigation on a delivery box. However, I previously printed out a picture that was relatively large, so the excess paper created issues for the drone in flight. So, I then tested out different QR code sizes and was able to find the right size that wasn’t too big or too small, and one that did not interfere with the drone’s navigation.
In conclusion, I was able to solve all three of these issues, except for some occasional errors, and I learned that drone programming is far from precise data and straightforward code. A lot of the time you will run into unexpected errors that might drive you crazy only for you to realize that it was the slight covering of one of the sensors, or you taped the hook a little too far to the right. I learned how to 3D print and how you really need to carefully think out and measure whatever mechanism you’re trying to print out or else you’ll be rudely surprised after a 3 hour wait when you discover that whatever you printed out is too big or too small. Essentially, my takeaway is that the tedious work is often necessary in order to execute whatever you’ve set out to do. In the future I think I would have tried to finish earlier so I could’ve looked into to voice navigation, in addition to creating more complicated navigation routes. But ultimately, I’m happy with how my project turned out.














