Andrew Reade
Jean-Pierre DeDeaux
Caden Pfendler
Aaron Foster
Backward Looking Summary
Situation
As a continuation on the previous A R&D labs, the group was tasked with testing the effects of motor and propellor configurations on the AEV’s distance, power use, and overall efficiency. The group tested four different configurations for both the motor and the propellers. The first configuration for the motors [Figure 1] involved spreading the motors as far out as possible. This was then tested running forwards and backwards along the monorail. Similarly, the second configuration was run forwards and backwards; however, the motors were placed closer together in the center of the AEV [Figure 2]. Regarding the propellers, the team alternated which propellor (short or long) was place in front of the other, the team also alternated the orientation of the propellers (parallel or perpendicular). These configurations were then tested pushing and pulling the AEV [Figure 3-6]. Testing the motors/propellers pushing and pulling the AEV, as well as placing them on different spots of the AEV combined together to create a total of 4 configurations which the group was then able to test, collect data from, analyze, and conclude which design would be most beneficial to use on the next iteration of their AEV.
Results & Analysis
Using the arduino to collect and compile data, the team was then able to upload this collected data to Matlab and create graphs comparing the Power vs. Time and Distance vs. Time of every configuration of the motors and propellers. As evident in Figure 7 all of the motor configurations used roughly the same power; however, the motors oriented in pull configuration used slightly less power than the motors pushing. Though the power usage was similar for all orientations, placing the motors further outward resulted in a much longer and more consistent distance traveled by the AEV [Figure 8]. Similar to the power usage of the motors, the four different propellor configurations used exactly the same amount of power as one another [Figure 9]. Even though the different propellor configurations used the same amount of power, the second configuration [Figure 4] went the furthest distance compared to the other orientations. Using the knowledge gained from these tests, the team came to the conclusion to use motor configuration 1, and propellor configuration 2 on their next AEV design.
Tables and Figures
Figure 1: Graph of Power vs. Time for propeller configurations.
Figure 2: Graph of Power vs. Distance for Propeller Configurations.
Figure 3: Propeller configurations 1, 2, 3, and 4, respectively from top left to bottom right.
Figure 4: Motor Configurations 1 and 2.
Figure 5: Graph of Power vs. Time for Motor Configuration
Figure 6: Graph of Power vs. Distance for Motor Configuration
Forward looking Summary
Situation
Moving forward, the group’s AEV is at a point in the design process in which the AEV can start being evaluated. The AEV run has to be precise and accurate in order to stop in the correct locations and deliver the passengers correctly. Testing the AEV on the tracks that will be used in the final runs will allow the group to tweak and change the AEV for the best possible run. In the allotted lab time, the group will start to test different percentage of power and for different time intervals to have the AEV stop at the first stop position halfway through the track. This will be tested multiple times during lab in order to validate consistent results in analysis.
Upcoming Goals
The goals, moving forward for the AEV is to fundamentally finish the design process and completely move forward in the goal of optimizing the run on the track by the AEV. Over the last few weeks the group has been testing different concepts on which the AEV could run more efficiently and with better response, our goal is to select which of these iterations is more effective in completing the task in which was given. The goal of the AEV project is to transport passengers efficiently and correctly, with more time in finalizing the AEV as a whole, the group will be able to achieve a higher level of success in these goals.
Upcoming schedule
Andrew Reade
-Lead programmer
-Create code that will allow the group to test within conditions of the final test runs
-Figure out if servo is necessary and better than coasting, if so integrate within code
Jean-Pierre DeDeaux
-Run through the past designs and consult group to meticulously pick best configuration of current design
Caden Pfendler
-Help develop code for the AEV runs
-Critically think ahead for overall AEV code that needs to be written for complete run
Aaron Foster
-Help and overall manage configuration of AEV as group sees fit
-On own time, develop a solidworks model of AEV that could be used and 3D printed to save money and weight
As a group, the AEV is close to being finalized in design, if the current design concept is thought to be the best and work as efficiently and to the best of our design ability. As a group, we need to finalize the design in order to move forward. Once this is accomplished, the next step, one in which the group may believe that is is at currently, is to test run and operate the AEV under the final test run conditions. This would allow the group to go back and analyze the code as well as the AEV design as a whole. Seeing what the AEV does in stopping where it needs to as well as traversing an incline is something that has yet to be tested, and seeing the AEV in action will allow more critical analysis of the AEV.
Appendix
Arduino Code
Propeller Configuration Test
File name: Propeller_Config_Test.ino
//Runs both motors and 25% power for 2.5 seconds, then brakes, then does the reverse.
motorSpeed(4,35);
goFor(5);
brake(4);
reverse(4);
motorSpeed(4,35);
goFor(5);
brake(4);
reverse(4);
Motor Configuration Test – Forward
File name: Motor_Config_Test_Forward.ino
//Runs both motors and 25% power for 2.5 seconds, then brakes.
motorSpeed(4,35);
goFor(5);
brake(4);
Motor Configuration Test – Backward
File name: Motor_Config_Test_Backward.ino
//Reverses then runs both motors and 25% power for 2.5 seconds, then brakes.
reverse(2);
motorSpeed(4,35);
goFor(5);
brake(4);
Meeting Notes
Meeting #5
Date: 2/7/2018
Time: 12:45 – 2:05 in lab
Members Present: All
Topics Discussed:
- Began work on Advanced R&D, with our topic being the propeller configuration.
- Determined a configuration that gave equal power when both pushing and pulling.
Meeting #6
Date: 2/13/2018
Time: 3:00 – 4:45 in 18th Avenue Library
Members Present: All
Topics Discussed:
- Designed part for the Grant Proposal.
- Discussed roles for each member in the Committee Meeting
Meeting #7
Date: 3/6/2018
Time: 7:30 – 8:30 in 18th Avenue Library
Members Present: Jean-Pierre DeDeaux, Aaron Foster, Andrew Reade
Topics Discussed:
- Worked on Progress Report 2.
- Discussed what we will work on In Lab 9a.