PROGRESS REPORT 2 | ENGR 1182 SP19 Baker International Group

Team C – Nick Braun, Jeffrey Gaydos, Samira Wehmann	Progress Report 2
Instructor – Bill Cohen, GTA –Sheng Zhu	March 19, 2019

Progress Report

Situation Summary

Two different AEV components were tested: battery voltage and propeller configuration. The team believed this would aid in avoiding some of the problems that may be encountered in future tests with the AEV. The aim of the battery testing was to ensure that a slight drop in voltage did not affect the power output to the motors and the speed of the AEV. The purpose of the propeller configuration was to ensure that contra-rotating propellers performed better than more standard designs. The team first defined the problem that each operation needed to test, then brainstormed the procedure, including constraints. The procedure was based off the data determined from the Preliminary Research and Devolvement Tests performed in labs 1-3. When testing voltage effects, the time it took for the motors to carry the AEV across a certain distance was used to determine the effectiveness of the motors at decreasing voltages. Additionally, different motor speeds were tested to determine if voltage drops had a more significant effect with higher motor speeds. When testing propeller configurations, 7 designs were tested to see how far the AEV traveled (after coasting) with each configuration, and to determine which configuration would be best. Once the procedures were approved, the team tested the AEV and modified the experiments as needed to ensure that useful data was collected.

Results and Analysis

The results of the battery experiment showed that slight drops in voltage did not significantly affect motor power output. Though sometimes the time it took the AEV to travel the specified distance increased with decreasing voltage, these increases were negligible and at times the AEV’s travel time decreased (see Figure 1 on next page).

Figure 1

Trial*	Time (s)	Voltage (V)**	Power to Motors
1	3.78	9.748	40
2	3.871	9.741	40
3	3.84	9.727	40
10	3.782	9.683	40
11	3.6	9.521	40
4	2.521	9.727	50
5	2.522	9.712	50
6	2.46	9.712	50
12	2.52	9.668	50
13	2.521	9.521	50
7	1.981	9.697	60
8	1.98	9.697	60
9	1.982	9.683	60
14	1.981	9.668	60
15	1.98	9.507	60
*Trials disordered to organize table by motor speed groups
**Voltages averaged from the first 2 stationary seconds of each trial

This clearly shows that slight drops in voltage did not affect the power output to the motors regardless of how fast the motors are spinning, and should not be of concern when testing the AEV further. This is as expected, as arduino has built-in code to aid in keeping the motors at constant speeds regardless of battery voltage.

When testing propeller configurations, it was found that the direction of the propellers are important in maximizing thrust. During the fourth test, propellers were set up in the correct orientation resulting in an abnormal difference in total distance traveled than other configurations (see configuration 4 in Figure 2 below). Configurations 1-3 had one propeller facing the correct way and one facing the wrong way, meaning they can be compared to each other to draw conclusions.

Figure 2

Propeller Configuration*	Total Distance Traveled (sensor ticks)
1	39
2	43
3	48
4	109
5	26
6	70
7	78

*Propellor configurations are as follows:

(1) Contra-rotating propellers 1: Motors facing inwards from AEV and are close together

(2) Contra-rotating propellers 2: Motors facing inwards from AEV and are far apart from each other

(3) Contra-rotating propellers 3: Motors facing outwards from AEV and are far apart from each other

(4) Side-by-side propellers: Motors side by side and facing the same direction

(5) Propellers facing the same direction: Motors on Standoffs in a line facing the same direction

(6) Contra-rotating propellers 4: Motors facing inwards from AEV and are close together, propeller facing proper direction

(7) Contra-rotating propellers 5: Motors facing inwards from AEV and are far apart from each other, propeller facing proper direction

Based on configurations 1-3, it’s clear that configuration 3 is the most effective contra-rotating design when only one propellor is facing the correct direction (see configuration 3 in Figure 2 above). This means that outward facing, far apart contra-rotating propellers are more efficient than inward facing and close together propellers. Configuration 5 had both propellers facing the incorrect direction and accordingly resulted in the AEV traveling the least amount of distance. Finally, configurations 6 and 7 were tested using the correct propellor direction for both propellers, and the distance traveled after coasting increased as expected. Comparing these two configurations shows that the further apart the contra-rotating propellers, the more efficient the AEV will be.

The data collected from both experiments showed that battery usage should not be an issue when testing the AEV, and that contra-rotating propellers may not be as effective as propellers mounted side-by-side. However, contra-rotating propellers may be more efficient in reversing than side-by-side configurations, and as such will be used because of this possible advantage. It was also found that a design involving contra-rotating propellers far apart and facing outwards should help to maximize the efficiency of our final AEV design.

Goals

The next focus for the team is the Advanced Research and Development Presentation. The presentation includes the team’s approach to the data from the battery efficiency and propeller configuration tests. The aim of the presentation is to communicate to other companies and the directors what data has been gathered from the Advanced Research and Development tests as well as what conclusions can be drawn from the data. The team will focus on supporting their findings with data from the experiments and on the limitations and issues that arose during testing. This will be completed by meeting to create a PowerPoint presentation together and practicing the presentation.

In addition, the team will focus on preparing for the Performance Test. The plan for the performance test will be outlined in the Advance Research and Development presentation. During the performance test, the team’s AEV must travel to the gate along the track, stop for seven seconds, and proceed from the gate. The goal of this test is to ensure that teams have a firm grasp on moving the AEV with high precision. The team will complete this by making sure that AEV travels slowly to minimize coasting as well as using an if statement to correct for undershooting the gate. This cautious approach eliminates the need to brake the AEV, using less energy.

One of the team’s goals is to use 75% or less of the budget given. This will be accomplished by avoiding breaking or losing parts. In addition, the team will be careful to program the AEV, so it does not fly off the track. The team will also have multiple members acting as stoppers along the track to ensure it is caught to avoid damages costing the team. The team will also stay within the budget goal through the aid of the grant paying for 50% of the cost to 3D print items.

Another goal for the team is to effectively secure the wires and motors. To accomplish this, the team plans to use the shell to ensure the wires that are in place. The team also plans on using Zip Ties and tape to secure the wires in the shell. To secure the propeller motors, the team plans on adding additional pieces given in the AEV kit to place on top of the Standoff, acting as a lid, so the motors of the propeller are secured.

Appendices

Appendix A: Future Schedule

*NOTE: in progress*

Task	Start Date	Finish Date	Due Date	Primary Person	Secondary Person	Est. Hours	% Completed
Grant Proposal	2/9/19	2/14/19	2/14/19	Jeff, Nick	Tiana, Samira	2	100
Progress Report 1	2/9/19	2/14/19	2/15/19	All		4	100
Committee Meeting	2/20/19	2/22/19	2/22/19	All		0.5	100
Advance R&D 1	2/22/19	3/1/19	3/1/19	Nick, Jeff	Samira	3.5	100
Advance R&D 2	3/3/10	3/7/19	3/8/19	Nick, Jeff	Samira	4	100
Performance Test 1	3/8/19	3/19/19	3/19/19	Nick	Jeff	2	100
GOAL: Secure wires and propellor motors	3/18/19	3/19/19	3/19/19	Jeff	Nick, Samira	0.5	0
Advance R&D Presentation	3/18/19	3/19/19	Lab 13	Samira	Jeff	2	50
Performance Test 2	3/20/19	3/22/19	Lab 15	Nick	Samira	2	0
Advanced R&D 3	3/26/19	3/29/19	Lab 18	Jeff	Samira, Nick	4	0
Final Deliverables	3/29/19	4/3/19	Lab 19	Nick	Jeff, Samira	5	0
Final Performance Test	4/2/19	4/5/19	Lab 21	Nick	Jeff	3	0
Oral Presentation	4/1/19	4/14/19	Lab 24	Samira	Nick,Jeff	2	0
Progress Report 2	3/3/19	3/18/19	3/19/19	Samira	Nick, Jeff	5	100
Website 3 Update	3/3/19	3/7/19	3/8/19	Samira	Nick, Jeff	2	100
CDR (draft)	3/20/19	3/21/19	Lab 14	Jeff	Nick, Samira	3	0
Team Eval 2	3/25/19	3/27/19	Lab 16	All		0.5	0
Committee Meetings 2	3/25/19	3/27/19	Lab 16	All		1	0
Progress Report 3	3/29/19	4/3/19	Lab 19	Jeff	Nick, Samira	5	0
Final Oral Presentation Draft	3/29/19	4/4/19	Lab 21	Samira	Nick, Jeff	3	0
Final Team Eval	4/15/19	4/17/19	Lab 25	All		0.5	0
CDR	3/22/19	4/17/19	Lab 25	Jeff	Samira, Nick	5	0
Final Website	4/11/19	4/17/19	Lab 25	Samira	Jeff, Nick	3	0
GOAL: use less than or equal to 75% of the budget	2/19/19	4/18/19	Lab 25	ALL			50

Appendix B: R&D 1: Battery Testing Trials, Arduino Code

B.1 Trials 1-3:

reverse(2);

goFor(2);

motorSpeed(4,40);

goToRelativePosition(74);

brake(4);

B.2 Trials 4-6:

reverse(2);

goFor(2);

motorSpeed(4,50);

goToRelativePosition(74);

brake(4);

B.3 Trials 7-9:

reverse(2);

goFor(2);

motorSpeed(4,60);

goToRelativePosition(74);

brake(4);

B.4 Trials 10, 15:

reverse(2);

goFor(2);

motorSpeed(4,40);

goToRelativePosition(74);

brake(4);

B.5 Trials 11, 14:

reverse(2);

goFor(2);

motorSpeed(4,50);

goToRelativePosition(74);

brake(4);

B.6 Trials 0, 12, 13:

reverse(2);

goFor(2);

motorSpeed(4,60);

goToRelativePosition(74);

brake(4);

Appendix C: R&D 2 Trials, arduino code

C.1 Trial 0:

motorSpeed(4,50);

goFor(1);

brake(4);

C.2 Trial 1:

motorSpeed(4,50);

goFor(1);

brake(4);

C.3 Trial 2:

reverse(2);

motorSpeed(4,50);

goFor(1);

brake(4);

goFor(2);

C.4 Trial 3:

reverse(2);

motorSpeed(4,50);

goFor(1);

brake(4);

goFor(2);

C.5 Trial 4:

reverse(2);

motorSpeed(4,50);

goFor(1);

brake(4);

goFor(2);

C.6 Trial 5:

reverse(4);

motorSpeed(4,50);

goFor(1);

brake(4);

goFor(2);

C.7 Trial 6:

reverse(2);

motorSpeed(4,50);

goFor(1);

brake(4);

goFor(2);

C.8 Trial 7:

reverse(1);

motorSpeed(4,50);

goFor(1);

brake(4);

goFor(2);

Appendix D: Team Meeting Minutes

Date 2/9/19

Time: 3:00-5:30

Members Present: All

Topics/Agenda: complete exercise 4, assign parts for the lab report, create grant proposal

Action Items with names assigned:

Jeff: complete exercise 4, start model on solidworks, grant proposal

Nick:complete exercise 4, grant proposal

Samira:complete exercise 4, grant proposal

Tiana: complete exercise 4, grant proposal

To be completed before next meeting:

Jeff: work on progress report, complete solidworks part, edit grant proposal, gather documents for community meeting

Nick: work on progress report, edit grant proposal, gather documents for community meeting

Samira: work on progress report, gather documents for community meeting

Tiana: work on progress report

Reflection:

Team members presented their individual designs then worked together to create a group design including the most efficient parts from each design. The team members worked on the grant proposal power point and determined which information is needed and which can be left out because of the 60-90 second time limit. Members also started working on their parts of the progress report. Finally, the team decided who would be representing each part of the community meetings.

Date 2/22/19

Time: 9:35-10:55 (in class)

Members Present: All

Topics/Agenda: complete community meeting, discus changes with project, talk with company about what each division is researching for Advanced R&D 1 and 2.

Action Items with names assigned:

Jeff: go to budget and R&D meetings

Nick: to the he PR meeting

Samira: go the the HR meeting

To be completed before next meeting:

Jeff: update website, submit part to be 3D printed

Nick: update website

Samira: update website

Reflection:

Team members attended their assigned meetings prepared to answer the questions asked. Once the meetings were concluded, the team came back together to discuss how the meetings went and the changes that needed to be made. Most changes revolved around minor details on the website. Problems with the computer occurred during class, so the team members decided to work on the changes another time. It was decided that team C is researching battery and propellers during advanced R&D 1 and 2.

Date 2/28/19

Time: 9:10-10:05 (in class)

Members Present: All

Topics/Agenda: create procedure for testing the battery during Advanced R&D 1.

Action Items with names assigned:

Jeff: create procedure for Advanced R&D 1, testing battery

Nick:create procedure for Advanced R&D 1, testing battery

Samira: create procedure for Advanced R&D 1, testing battery

To be completed before next meeting:

Jeff: submit application 16, Create SolidWorks model assembly for the Prototype Vehicle

Nick: Create SolidWorks Working Drawings for the Prototype Vehicle

Samira: Create SolidWorks Working Drawings for the Prototype Vehicle

Reflection:

Team members created a procedure testing the power to voltage, power of motors, and time over a distance of 3 feet. The Teams model was based off of the example models in class, but mortified to fit the exact criteria the team wanted to test. There was not a set number of trials for the experiment. The team had their procedure approved before the end of class so the team could have maximum amount of time.

Date 3/1/19

Time: 9:35-10:05 (in class)

Members Present: All

Topics/Agenda: test the batter advance R&D, update website from community meeting

Action Items with names assigned:

Jeff: test battery advance R&D

Nick:Test battery advance R&D

Samira: update website

To be completed before next meeting:

Jeff: N/A

Nick: N/A

Samira: N/A

Reflection:

Two team members worked on coding the program for the advance R&D test, then tested the program collecting and recording the data. The third team member worked on the updates for the website given during the community meeting.

Date 3/3/19

Time: 5:30-7:15

Members Present: All

Topics/Agenda: complete updates on website, discuss the idea for progress report one, discus progress report two, write procedure for Advance R&D 2: Propellers

Action Items with names assigned:

Jeff: update website (glossary of programming functions), create procedure

Nick: update website (citations), create procedure

Samira: update website (meeting notes), create procedure

To be completed before next meeting:

Jeff: work on progress report 2 ( results section)

Nick: work on progress report 2 (results section)

Samira: work on progress report 2 (introduction and future section)

Reflection:

It was determined that the team will not edit and resubmit Progress Report 1 since the grade can only be improved by 3% and the team rather focus on testing, the website, and the second progress report. In addition, the team worked on updating the website. The team updated missing documents/citations, edited the written paragraphs, and updated links. the team also made the procedure for Advance R&D 2, propellers. The team plans to get the procedure approved during the next class. Finally, the team divided the parts for the progress report 2.

Date 3/5/19

Time:9:10-10:05 (in class)

Members Present: All

Topics/Agenda: Get the procedure for R&D 2 approved, start performing tests

Action Items with names assigned:

Jeff: Work on adjusting propellers, test propellers

Nick: update code for propellers, test propellers

Samira: assist on adjusting propellers, test propellers

To be completed before next meeting:

Jeff: work on progress report 2 ( results section)

Nick: work on progress report 2 (results section)

Samira: work on progress report 2 (introduction and future section)

Reflection:

The team worked on comparing different positions of the propellers to determine which position would be more efficient for the AEV traveling up to the gate and proceeding from the gate. It took more time than expected to change the position of the propellers. In addition, it took multiple tries to obtain accurate results because the code would stop recording as the AEV costed. The team added a wait feature onto the code so the data could be completed. The team completed the testing of one trial.

Date 3/7/19

Time: 9:10-10:05 (in class)

Members Present: All

Topics/Agenda: complete advance R&D test 2

Action Items with names assigned:

Jeff: Work on adjusting propellers, test propellers

Nick: update code for propellers, test propellers

Samira: assist on adjusting propellers, test propellers

To be completed before next meeting:

Jeff: work on progress report 2 ( results section)

Nick: work on progress report 2 (results section)

Samira: work on progress report 2 (introduction and future section)

Reflection:

The team continued to test the different locations of the propellers. The distance traveled was sufficiently lower than trial one. It was determined that the propellers were attached backwards onto the motor so air was not being caught in the propeller properly. The team decided that during the lab the team would perform another test to compare how many marks the design was changed.

Date 3/8/19

Time: 9:35-10:55 (in class)

Members Present: All

Topics/Agenda: create the code for the Performance Test 1

Action Items with names assigned:

Jeff:Work on Performance Test

Nick: Work on Performance Test

Samira: Work on Performance Test

To be completed before next meeting:

Jeff: work on progress report 2 ( results section)

Nick: work on progress report 2 (results section)

Samira: work on progress report 2 (introduction and future section)

Reflection:

The team wrote the code and tested the code for the performance test. The AEV has to travel a certain distance to the gate, stop for seven seconds then proceed from the gate. The team decided to base the coding on the distance traveled so the code can be the same from the lab room to the classroom.

Date 3/18/19

Time: 4:20-6:00

Members Present: All

Topics/Agenda: Complete the progress report, assign roles and create PowerPoint for the Advance R&D Test Presentation

Action Items with names assigned:

Jeff: work on presentation and progress report, update website

Nick: work on presentation and progress report, update website

Samira: work on presentation and progress report, update website

To be completed before next meeting:

Jeff: be prepared to present the Advance R&D presentation, submit progress report

Nick: be prepared to present the Advance R&D presentation

Samira: be prepared to present the Advance R&D presentation

Reflection:

The team created the PowerPoint for the Advance R&D oral report. The report should be 6-8 minutes long containing the results from the test, the upcoming performance test, and the approach for the team’s design. The topics to divide are; Propeller results, battery results, and approach/performance test. At the following meeting, the team will edit and submit the final PowerPoint and determine who is presenting which part.