LAB 01- Believer Punch List

For this weeks lab, me and my group were transisitoned into new groups and checked off all of our and the next teams components for the Believer drones. We also updated our blogs so that the other team can see where we left off and where they left off. By making a punch list, we were able to see what were the remaining tasks that the previous group was not able to complete. We took note of the work still left out for us like installing the motor mounts and soldering the ECS and other important hardware.

First we documented a few things on our blog that the other team did right with their believer drone like seeing if there were any mistakes in the building process, what they should they improve, and what does my team have to do to fill in for the other teams work. After reading through our blog, we were confident that the next team who will take this drone will see our comments and suggestions clearly.

The next step was to delevop our punch list. A punch list is basically shows the final repairs or final tasks that is passed to a person or a group and they must work on those tasks till completion. The punch list is made to be a final assurance check and is used before rotating it to a new group, highlighting the other groups work.

This was our punch card for our lab:

Glue fuselage halves together

Glue on rubber pads to fuselage

Glue on wing root connectors

Glue on clear battery plate to inside of fuselage

Glue black bracing strips to inside of fuselage

Needs ruddervator latches installed (P/N 14)

Needs all electronics installed besides wing and tail servos

Install engines and engine covers

Needs tail servo attachments installed (P/N 13)

Needs control surface linkages installed

Needs panel latches installed (P/N 18)

After writing our punch card, we made sure that the harward in the believer drone was up to date and made sure the DATX controller the other team had free motion sticks and proper configuration. We also made sure that the software and parameters on both DATX and Cubepilot were on par with regualtions. After reviewing all the data and making sure that all of the punch list tasks were commented and tasked, we then moved onto the parameters for the Cube pilot that the previous group worked on. Since our previous Cubepilot was already configured, we had to check the CubePilot from the other group was up and working with the correct set parameters

Here is the link of their parameter that we checked:

Parameters (3).json

39.8 KB

⁠

Overall, this lab helped me understand how important using a punch list is and how you can utilize this in any work enviorment and learn about who other members are doing and what they have done. Each group is different and switching groups helped me learn about other peoples thought processes and what pace they are at with their drone. In summary, using this punch list and going through the entire lab manual to make sure the status of our new drone was crucial to my understanding of this lab and how Other groups can perform better and get on the right track.

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

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

CtrlP

) instead.