Lab02- External Sensors and System
The group worked on three task last week, these tasks include: Constructing a sample AEV design to be used during the lab, using basic function calls to write a program using the Arduino Ide software, using, and familiarizing themselves with reflectance sensors and the usage of them, and testing the propulsion efficiency of different propeller types and configurations to determine the optimum design for the AEV.
Familiarizing oneself to reflectance sensors was important because it provided the team with an understanding about how distance would work while running the AEV. This is done by knowing how much one mark would equal out to in inches. With this measurement being known the team would be able to know how many marks would be needed for them to traverse the entirety of the AEV track. Completing this last week was important so that the team could begin working with the AEV track.
Two propeller types were tested and each with one set of data for the “puller” configuration and one for the “pusher” configuration. The propellers were cased inside of a wind tunnel with a speed controller and indicator as well as a power supply control. This method of testing is useful when simulating various propeller configurations to save time and money in real-life settings, such as the AEV project. Changing the arduino power setting altered the measurements taken by the wind tunnel. Measuring the power input as well as the power output allowed for the calculation of the propulsion efficiency which is a mixture of motor and propeller efficiency. The propulsion efficiency is graphed against the advance ratio-which is a unitless measurement found using input and output data- in graph 6 of Appendix A. The graph shows that the 2510 puller had the greatest propulsion efficiency over advance ratio of all of the configurations. The propeller of the puller is facing the same direction as the thrust line while the pusher is facing the opposite direction. Graph 7 of Appendix A shows the arduino power setting for the calibrated thrust for the five configurations. The 3030 puller created the largest thrust output, yet on graph 6, it had the smallest efficiency. The 2510 puller had the largest efficiency, yet it had the smallest thrust output. This data supports that larger thrusts will create smaller efficiencies.
Thrust versus Arduino Power for 3030 and 2510
Weekly Schedule
Team Meeting Notes Week 3
Date: 1/28/2017
Time: 6:00 pm
Members Present: Cat, Emily, Lovell
Topics Discussed: Progress Report Week 3, Portfolio Update
Objective:
The objective of this meeting is to discuss the requirements for Progress Report 3 and to split the parts up evenly. Also, the members will discuss the parts of the lab that they worked on and decided on a type of blade preference. Lastly, the team will need to discuss the portfolio update and assemble more of the AEV and discuss possible additions to make to it.
To do/Action Items:
-Split parts for Progress Report 3
-Determine who is doing the portfolio update
-Decide on blade preference
-Assemble more of the AEV
Decisions:
-Progress Report 3 will be split evenly
-The portfolio update will be completed
-The AEV was assembled as a group
Reflections:
-Talk through the labs as they are performed will be more productive in understanding the meaning of labs and make the writing process easier as well.
-Collection of data is meaningless unless the reasoning is understood before the the lab is performed, so more time needs to be taken to understand the reasonings.
-Overall a more productive and interactive meeting.