Explore

Course Overview

Expectations vs. Reality

I expected to obviously build on my knowledge of UAS in a more direct way. In previous semesters, we seemed to go over the overall basics of what drones are, how they fly, and what they are composed of. I also believed that we would fly drones a bit more, or even the same amount as we did last semester.

However, I have now learned that this course was about learning the ins and outs of a UAS. Being able to direct it, understand it, and put it back together. We did not fly drones as much as I had thought, but that helped me learn there is much more to the field than just some joysticks and a screen. I once talked to an alumni about my major, and the one thing he told me to learn, was how to build them, because anyone can fly a drone. With this class, and I believe future classes, I will be able to achieve and understand how to do that.

Overview of Semester

Began by tapping back into the sticks and flying the drones around. One lab we completed the NIST OTL Flight, testing and honing in the skills/accuracy of our piloting. This was to ensure we still understood how to pilot an aircraft not only safely, but not accurately na din a timely manner.

Then we began the identification and understanding stage. We had some labs where we had to learn about Maintenance tools and protocols, familiarize ourselves with the Believer parts and pieces, and know what a Wiring harness should look like. I did not know it at the time, but all these labs eventually contributed to the final building of the believer.

Next began the hands on stage, getting down to the integral parts that make up the believer. For example, the DATX Controller, the original Taranis controller contained too many switches so we opened up the back of the controller and proceeded to unscrew, remove, and hot glue the free pieces to the inside of the controller shell, out of the way. This allows us to keep the switches still connected to the controller, but out of sight and out of mind. This mitigates risk and allows the user to be more efficient.

We continued this stage by setting up the believers avionics so the uas could communicate with ground control. In this secition we learned the specifications of the RFD900x and learned how to engage it. We learned how to properly sync the information into the computer, and how to get the ground module and air module talking. We eventually got the Air and Ground module communicating, and further testing this by sending a “Hello world!” prompt to the neighboring RFD900x through PuTTY. We were successful in communicating, but had some troubles originally because we entered in our values (the BAUD and the NetID() wrong initially. We further focused on dialing in the Believer Avionics specifically through the alteration of parameters in the system. We added in the airspeed sensor and the GPS sensor to the system. We also made sure that we could communicate with the GCS wirelessly. We paired the telemetry modules once again, but this time connected the cube to the Air Telem. It then was able to communicate with the GCS. We then modified the SERIALX Parameters to the proper values.

Next, we began to sync up the controller with the mechanisms it would be controlling. This included the servos, ESCs, motors, and any other controls it would managing. In this lab we simulated the avionics, controls, and motors used in the Believer aircraft, focusing on powering and ensuring proper connection and calibration of the system components. The lab involved setting up and calibrating the DATX, verifying its inputs and outputs, and ensuring proper parameter settings in the hardware and LUA script. We finalized setting up all the Believers avionics, ensuring and mapping the correct controls for each. We also calibrated the ESCs and ensured proper motor startup and function. I was a big fan of this lab because we got to see all our work over the past several weeks in action and see it all working together.

Last, but not least, we were able to begin building the integral part of the system, the physical UAS body itself. This was neat because we were able to see the entire thing start to come together, were able to visualize where different pieces, avionics, and controls would go. We did not fully complete the building of the Believer, however, we got a great start to set ourselves up for success next semester.

Value of Building from Scratch

A lot of what I have learned from this class is how to troubleshoot. That's really what this major centered around, is troubleshoot, troubleshoot, troubleshoot. That ability comes from building from scratch. I honestly like this. When given something prebuilt, the feeling of fulfillment upon completion isn't all there. However, when starting from scratch, the feeling upon completion is much more fulfilling.

Building from scratch also helps you understand the system more, as you are the person who completed everything. If something were to go wrong, you would be able to identify it, and on top of that, possibly even fix it considering you understand how it works.

I used to think that a UAS was something that was pulled out of a box, turned on, and flow. But now, I understand the complexity of the system, and admire it. Not only the art and effort that goes into it, but also the customization and creativity that can play a part into each UAS.

Skill Growth and Technical Learning

I mentioned before how I talked to an alumni about my major and how he told me t learn how to build drones. I wondered if that would really happen in this major, and this class exceeded my expectations with that. I thrive by learning in a hands on method, especially when building things. Taking this class, on top of AT 265, my understanding and skill involving wires grew exponentially, which will allow me to thrive heavily in this field. On top of this, just understanding the different components of a UAS was huge for me to learn as well. Being able to fly a drone is one thing, but learning how the motors work, how the props allow the drone to generate lift, and many more specifics, was incredibly beneficial. I think this has been the best class so far in this major just because it introduced us to so many specific parts and capabilities of UAS.

I never was looking forward to the day where I would have to do software work in this major, but it honestly was not all too bad. I was able to understand how a UAS communicates, and how to alter the way it acts, reacts, and moves on a software basis.

I have always been able to work in a team, but I would normally take the reigns. With this class, I was able to not only do that, but take a backseat when needed. This allowed everyone to get their fair share of involvement and understanding of the systems throughout the semester, and allowed me to survey the way other people work.

What Surprised Me

I mentioned before that the minimal amount we flew drones in this class surprised me. But, looking back on it, I believe it was necessary and a good choice. There is a lot to the UAS field, and ultimately what sets one apart from others is understand the ins and outs of them.

Moving more into that, what surprised me was how in depth and hands on we got in this class. Again, I expected some hand-on because it is UAS, however, essentially building a drone from scratch is something I did not have on my checklist.

I think things started to fully click for me when we began syncing everything up. Throughout the semester, we went from setting one system up, to setting avionics up, to parameters, etc. But finally, near the end, when everything began to communicate and work together, I understood why.

I think for me, dealing with software was the most educational. I had never really been a fan of it, but it is necessary in this field. I believe it was incorporated in a good manner, and was overly beneficial to me.

What I Am Most Proud Of

In the beginning of the semester, I was most proud of my abilities when operating a drone. I spent a lot of time over the summer flying my own, and really honing in my skills, camera capturing, and overall understanding of how one flys.

Approaching the end, I was pleased with my ability to take information away, and apply well into the task at hand. I have always been someone who tries to execute to the best of their ability, but I felt that this semester especially, I thrived in the realm of execution.

I also took the helm of the Airspace Waiver project, which allowed me to fully learn the steps of submitting one, which will benefit me in the future.

Overall Takeaways

This course severely increased my confidence when working with UAS Hardware. Before, I would look at a custom built drone, and have no idea how anything worked, or was put together. Now, I am Abel to identify different parts, what was done to them in the process, and how they work.

When I take my talents into. future internship, it won't just be me bringing in experience flying a drone, but also the ability to dissect and understand one, and to put it back together. The ability to understand and build the hardware of a drone is essential to success.

As for the bigger picture, this class not only allowed me to learn, but allowed me to enjoy what I was doing. In a lot of other “engineering” esque classes, people still have not put their hands on anything. As for this major, we have almost already fully built a drone. This allows me to stay bought into the major, all while enjoying it and not feeling burnt out.

Want to print your doc?
This is not the way.

Try clicking the ··· in the right corner or using a keyboard shortcut (

CtrlP

) instead.