Skip to content
More
Share
Explore
AT 209 Autonomous Aircraft Technology and Maintenance I
Lab 01 & 02 - NIST OTL
This lab offered students the ability to test their in-flight proficiencies, to include steady control of the UAS and the gimbal tilt function. Depending on an individual’s role in the operation, verbal commands were either given or received throughout the exercise.
This lab tested the safety, capabilities, and proficiency of both drone functionality and teams of three individuals via standards determined by the National Institute of Standards and Technology (NIST). The drone used by the team was the Mavic 2 Pro. The objective of the exercise was to follow navigation commands and capture full images of the interiors of buckets, contained in a “stand”. The buckets contained green targets that were labeled alphanumerically. There were three stands in the exercise, and each stand was comprised of five buckets. Appropriate maneuvers were described in a scoresheet that stated the operational objectives.
One bucket would point vertically to the sky. This bucket would represent the stand number (i.e. 1, 2, 3). The other four buckets that comprised the stand would be labeled alphanumerically (i.e. 1A, 1B, 1C, 1D). These four buckets were placed equidistant from each other around the vertical bucket, creating 90 degrees of separation. The buckets had an approximate 45-degree angle between the sky and ground. In order to pass the exercise, PIC’s had to:
1.) Follow navigational commands.
2.) Attain quality pictures of the objectives.
3.) Complete the exercise within a 10-minute timeframe.
As referenced earlier, each team was composed of three individuals: a Pilot in Command (PIC), Proctor, and Visual Observer. The PIC’s job was to navigate the drone per verbal guidance from the Proctor. The PIC additionally had to capture images of the buckets that corresponded with the Proctor’s commands. The Proctor had the responsibility of commanding the PIC to take pictures of the appropriate buckets and to perform the necessary maneuvers. The Visual Observer kept track of the time during the exercise and ensured that the drones of other participants flew at a safe distance from the operation.
Initial setup prior to the start of the exercise
This exercise followed standards determined by NIST, however the instructions for the exercise were customizable. For this lab, we performed the Level 1, Open Lane, Basic Proficiency test. The distance between each bucket stand was 10 ft. The drone was launched 10 ft away from bucket stand #1. The PIC was instructed to stand 10 ft away from the location of launch. The buckets, launch point, and PIC were all setup in a vertical line, as demonstrated by the picture above.
The scoresheet used to facilitate the exercise. This is my scoresheet. Exercise was completed with a final time of 8 minutes and 12 seconds.
Additionally, this lab tested our BVLOS capabilities. This portion was completed with the Skydio 2+. Operators would perform the same Position and Traverse tests as before, but this time would complete the test turned away from the UAS. The PIC would be relegated to using only the Ground Control Station display. This is the only portion of the exercise that changed, as the Proctor still was responsible for issuing commands and the Visual Observer was still in charge of monitoring potential obstacles during flight.
Lucas Toppe, a team member, familiarizing himself with the Skydio 2+ prior to conducting the BVLOS portion of the test.
Lab 03 - Maintenance Tools
This lab is on its own Coda Document. We had the opportunity to use and answer questions about tools to include digital calipers, a Digital Multi Meter (DMM), wire strippers, crimping tool, and a torque wrench. See the link below for the lab.
Lab 04 - Soldering
For this lab, we reviewed the process and practical reasoning behind soldering wire. The instructions were to both create a lap joint between two wire strands and also to solder a resistor to a Printed Circuit Board (PCB).
Picture of completed overlap joint, to include equipment used in the process
The act of soldering is relatively simple, but it requires the proper tools, still hands, and practice. We used a 24AWG wire for the lap joint. First, wire strippers were used in order to expose both sides of the wire underneath the insulation. When using the wire strippers, it’s important to exercise caution and keep the individual copper wire strands intact. After using the wire strippers,
Lab 05 - MFE Believer Parts and Assembly
For this lab, we were split into groups with the objective of familiarizing ourselves with the entirety of the BFE Believer UAS nomenclature and assembly instructions. The below document dives into airframe/electrical components received as stock material for the MFE Believer kit. The document also shows additional electronic components that were purchased from multiple vendors. These components will be used to customize the Believer in a variety of ways. Check it out!
Lab 06 - Altitude Waiver
i still haven’t done this btw.
Lab 07 - DATX Setup and Modification
This lab was for the purpose of hardware and software modification of the DATX controller, which we will use to operate the Windracers ULTRA UAS. The lab was completed as a group, with the group split between those working on hardware modification, and others working on software modification. The stock DATX controller’s nomenclature is not ideal for operation, so the hardware group disassembled portions of the controller that were operationally unnecessary. The software group converted the controller’s firmware from its default OpenTX to EdgeTX 2.7.1.
Lucas Toppe performing hardware modifications
Lucas and I worked to disassemble the controller and modify the hardware. This included the removal of toggle switches and other knobs on the controller. The main purpose of this was that the stock controller was heavily crowded. It would be easy for an operator to make a mistake in accidentally flipping a switch or adjusting a knob. Removal of these extra switches will simplify flight for the operator. Extra parts were placed back in the DATX case.
The software group followed the guide to flash the EdgeTX 2.7.1 firmware onto the controller.
Lab 09 - Believer Avionics
I’m sure the above link won’t work for you, but pending my ability to competently use this website, I will have to address that problem later, as the deadline for Labs 10 and 11 is quickly approaching.
Lab 09 built upon concepts established in Lab 08. The lab was spent establishing communication between Ground Control and the Cubepilot. Communication was enabled by an RFD900x modem which utilized the MAVLink communications protocol. Parameters (which serve to establish constraints of a multitude of system operating components and aircraft physical limitations) were a heavy focus in this lab and adjusted via Ground Control. Appropriate ports we utilized to bring information to and from the Cubepilot board.
Lab 10 - Motors and Controls Pt. 1
Lab 10 - Motors and Controls.pdf
2.1 MB
Well to start, in this lab we created great things. We created the connection between the DATX controller and the Cube by using a TBS Tracer Micro Transmitter and Receiver set. We had to utilize a LUA script, a “lightweight and embeddable coding language”, to pair the transmitter and receiver together. This was the easy part.
The hard part came when we tried to upload the Parameters into Ground Control, as we unknowingly overlooked that we were not using the proper FCU version...this was a struggle that cost us approximately 45 minutes on the lab day. It was not discovered until Anestis was very graciously giving me a run through of Labs 08 and 09 that he realized what the problem was. This problem was fixed in the following lab.
Lab 11 - Motors and Controls Pt. 2
Lab 11 - Motors and Controls.pdf
2.1 MB
Want to print your doc?
This is not the way.
This is not the way.
Try clicking the ··· in the right corner or using a keyboard shortcut (
CtrlP
) instead.