(Week Four)Week Four Updates

Moving through week four was a tough trek. Little forward momentum was accomplished during this week. The winter weather was to blame for a lack of good group progress, as it was difficult to meet in person. However, time was spent on pushing forward with some of the many logistical matters that are involved with the capstone project. Some of the logistical projects that were worked on were tee shirt and logo design, platform to project assignments, platform specific operational checklist and manual reviews.

The class shirt logo draft is complete and was sent in to the Purdue copyright office. At the time of this writing, I have not heard back from the office. But, I have a good feeling that it will be accepted and we will be able to move forward with the class logo. Soon we can start to promote the shirt for possible sponsorship or sales for other classes within the UAS degree.

The checklist that Ryan, Todd and I were working on has been uploaded into drone logbook. Some changes need to be made but it is a good step in the right direction. Ryan has put forth a great deal of work in accomplishing this task. There is still some collaboration that needs to be done to make this checklist as effective as possible. I personally am not a fan of the drone logbook application. Hopefully by the end of next week a complete and finished checklist for the M600 will accessible through the website. The flowchart below depicts the features of the drone logbook application. More dedicition is required to fully take advantage of the software properly. Hopefully during week five I will be able to get a firm grasp on how to modify and use this application.

Drone Logbook Flowchart

Manuals that were reviewed during week four included the M600 user manual, and the Altum from MicaSense sensor. Future reading includes the Bramor from C-Astral ( as soon as it is confirmed that it will be available for use this semester) , the RGB payload for the matrice, and the ground control point "Reach" system.