Appendix AA: team schedule
Date: 1/11/19
Time: 9:35-10:55 (in class)
Members Present: All
Topics/Agenda: create u.osu.edu website, complete exercise 1-programing basics
Action Items with names assigned:
Jeff: complete exercise 1-programing basics
Nick: complete exercise 1-programing basics
Samira: complete exercise 1-programing basics
Tiana: complete exercise 1-programing basics
To be completed before next meeting:
Jeff: Reflection
Nick: Reflection
Samira: Meeting notes
Tiana: Website
Reflection:
Programming Arduino was explored and team members are prepared to begin the AEV project. Team members are beginning to brainstorm and think about a design that would be the most efficient for this project, as well as consider possible issues that could arise during this project.
Date 1/18/19
Time: 9:35-10:55 (in class)
Members Present: All
Topics/Agenda: complete exercise 2-external sensors
Action Items with names assigned:
Jeff: setup the AEV
Nick: program the code for adruino
Samira: setup the AEV
Tiana: setup the AEV
To be completed before next meeting:
Jeff: review AEV kit checklist/update website
Nick: review AEV kit checklist/update website
Samira: review AEV kit checklist/update website
Tiana: review AEV kit checklist/update website
Reflection:
Team members tested the reflectance sensors for the AEV, and familiarized themselves with senor hardware components and troubleshooting techniques
Date 1/25/19
Time: 9:35-10:55 (in class)
Members Present: All
Topics/Agenda: complete exercise 3-performance analysis tool
Action Items with names assigned:
Jeff: complete exercise 1-performance analysis tool
Nick: complete exercise 1-performance analysis tool
Samira: organize website
Tiana: organize website
To be completed before next meeting:
Jeff: Brainstorm AEV design
Nick: Brainstorm AEV design
Samira: Brainstorm AEV design
Tiana: Brainstorm AEV design
Reflection:
The AEV Data extraction program was explored and team members tested the motor of the vehicle. Team members also continued to develop and organize the website.
Date 2/8/19
Time: 9:35-10:55 (in class)
Members Present: All
Topics/Agenda: complete exercise 3, test motor, evaluate potential designs
Action Items with names assigned:
Jeff: complete exercise 3
Nick: complete exercise 3
Samira: update website
Tiana: update website
To be completed before next meeting:
Jeff: work on progress report
Nick: work on progress report
Samira: work on progress report
Tiana: work on progress report
Reflection:
Team members tested and fixed the program to run the vehicle. After the first two initial attempts to run the AEV failed due to poor connectivity and motor speed the team members fixed issues with the code and with the vehicle set up. Samira and Tiana worked on the criteria to test the potential designs.
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.
Date 3/19/19
Time: 9:10-10:05 (in class)
Members Present: All
Topics/Agenda: Complete the performance test, complete advance R&D presentation slides
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: be prepared to present the Advance R&D presentation (propellers), submit slides
Nick: be prepared to present the Advance R&D presentation (intro and test)
Samira: be prepared to present the Advance R&D presentation (battery), edit slides
Reflection:
The team concluded the performance test. The team had to edit the code to rely more on coasting. During the test, the propeller broke but this did not impact the results of the data. The team obtained a new propeller and decided the shell is too much weight, causing problems with stopping. The team decided to remove the shell. In addition, the AEV was titled, so the team decided to move the L-shaped arm more towards the center to balance out the vehicle.
Date 3/21/19
Time: 9:10-10:05 (in class)
Members Present: All
Topics/Agenda: Present Advance R&D, talk about next class
Action Items with names assigned:
Jeff: Present on propeller R&D test, Discuss ideas for performance test 2
Nick: Present approach and performance test, work on performance test 2 code
Samira: present battery R&D test, discuss ideas for performance test 2
To be completed before next meeting:
Jeff: N/A
Nick: N/A
Samira: N/A
Reflection:
The team presented on the results from the two advance R&D tests. In addition, the team shared how the team is approaching to the task assigned by the city of Columbus. The Team shared the results from the first performance test and discussed the changes in the design for the second performance test. After the presentation was done, the team answered questions and listened to three other Teams presentations. Finally, in the last 10 minutes of class, the team shared ideas and worked on the code for the second performance test.
Date 3/22/19
Time: 9:35-10:55 (in class)
Members Present: All
Topics/Agenda: Complete performance test 2
Action Items with names assigned:
Jeff: test AEV for performance test 2
Nick:test AEV for performance test 2
Samira: test AEV for performance test 2
To be completed before next meeting:
Jeff: N/A
Nick: N/A
Samira: N/A
Reflection:
The team began coding the AEV for the second performance test. The AEV must travel to the gate, wait 7 seconds, go pick up a load, wait 5 seconds and proceed from loading doc. The team was having trouble with the AEV traveling up to the proper position of the gate.
Date 3/24/19
Time: 5:15-6:00
Members Present: All
Topics/Agenda: Discuss the CDR and committee meetings
Action Items with names assigned:
Jeff: discuss CDR
Nick: discuss CDR
Samira: Discuss CDR
To be completed before next meeting:
Jeff: write results, executive summary and discuss of CDR, be prepared to present research and development and finances during committee meetings
Nick: write results, executive summary and discuss of CDR, be prepared to present public relations of committee meetings
Samira: write intro, conclusion and recommendations, and executive summary of CDR, be prepared to discuss human resources during committee meetings
Reflection:
The team split up roles for the CDR and discussed a due date to allow enough time for editing. The team also decided to stay in the same roles for the committee meetings. For the human resources, the team will contact Samira if the members have any concerns about another member to keep the issue confidential.
Date 3/26/19
Time: 9:10-10:05 (in class)
Members Present: All
Topics/Agenda: Complete performance test 2
Action Items with names assigned:
Jeff: complete performance test 2
Nick: complete performance test 2
Samira: complete performance test 2
To be completed before next meeting:
Jeff: write results, executive summary and discuss of CDR, be prepared to present research and development and finances during committee meetings
Nick: write results, executive summary and discuss of CDR, be prepared to present public relations of committee meetings
Samira: write intro, conclusion and recommendations, and executive summary of CDR, be prepared to discuss human resources during committee meetings
Reflection:
The team had multiple issues while completing the second performance test. The AEV would go too far past the sensor at the gate, then start reversing. Once that was fixed, the AEV was not going far enough to the load, but the propellers were still moving. Increasing the speed and other changes to the code solved this. Then the AEV would land near the load, and stop, but not go again. The team focused on getting the AEV to wait and start again before worrying about getting all the way to the load. Once this was fixed, the AEV began going too far pas the first sensor of the gate again. The team did not complete the 2nd performance test.
Date 3/29/19
Time: 9:10-10:05 (in class)
Members Present: All
Topics/Agenda: Complete performance test 2, have team meeting notes
Action Items with names assigned:
Jeff: complete performance test 2, present on research and development
Nick: complete performance test 2, present public relations of committee meetings
Samira: complete performance test 2, discuss human resources during committee meetings
To be completed before next meeting:
Jeff: N/A
Nick: N/A
Samira: N/A
Reflection:
The team, present the community meetings. The website changes include descriptions for the links. The team also needs to figure out why the AEV flew off the tracks. Finally, the team is doing well working as a group. The team also completed the progress report 2. The only issues was ensuring that the AEV went the proper distance for multiple trials. The team decided that the team will test the distance traveled by the AEV at different positions to see if the AEV actually goes the distance programmed.
Date 3/28/19
Time: 9:35-10:55 (in class)
Members Present: All
Topics/Agenda: Complete the Advance R&D 3 (placement of the reflector sensors), if time allows start testing for final performance test
Action Items with names assigned:
Jeff: complete A&D 3, start final test
Nick: complete A&D 3, start final test
Samira: complete A&D 3, start final test
To be completed before next meeting:
Jeff: work on progress report 3, results section
Nick: work on progress report 3, results section
Samira: work on progress report 3, intro and future section
Reflection:
The team, decided to test how the placement of the reflector sensor at the start of the trial impacted the distance and consistory traveled. The trials consisted of the sensor being on the right, left, top and bottom. It was noticed that after a certain amount of trials, there was a dip in the distance that would rise again. The conclusions showed that top configuration is most consistent. Then the team began coding for the final performance test.
Date 4/2/19
Time: 9:10-10;05 (in class)
Members Present: All
Topics/Agenda: test for final performance test
Action Items with names assigned:
Jeff: work on final test
Nick: work start final test
Samira: work final test
To be completed before next meeting:
Jeff: work on progress report 3, results section
Nick: work on progress report 3, results section
Samira: work on progress report 3, intro and future section
Reflection:
The team worked on coding for the final test. The team received a fully charged battery, as opposed to the semi charged battery last meeting. The team therefore had to adjust the code for the intense increase in power. The AEV was traveling too far and too fast. Once this issue was solved, the team worked on the code coming back after the load was picked up.
Date 4/4/19
Time: 9:10-10:05 (in class)
Members Present: Samira and Nick (**Jeff had an excused absence* *)
Topics/Agenda: test for final performance test
Action Items with names assigned:
Nick: work on code for final testing
Samira: work on code for final testing
To be completed before next meeting:
Jeff: work on progress report 3, results section
Nick: work on progress report 3, results section
Samira: work on progress report 3, intro and future section
Reflection:
The Team continued to work on the final code. During one of the tests, there was a metal piece on the load from another team, resulting in the damage of the Teams propeller. The team had to replace the propeller to continue with the code.
Date 4/4/19
Time: 9:35-10:55 (in class)
Members Present: Samira and Nick (**Jeff had an excused absence**)
Topics/Agenda: test for final performance test and edit CDR
Action Items with names assigned:
Nick: work on code for final testing, work on CDR
Samira: work on code for final testing,work on CDR
To be completed before next meeting:
Jeff: work on progress report 3, results section
Nick: work on progress report 3, results section
Samira: work on progress report 3, intro and future section
Reflection:
The team received a battery that was 1/3 of the way charged. When testing, the AEV barely made it up the first incline. The team decided it was best to work on the CDR as the battery charged. The team edited the CDR discussing what else to add and what to take away. at 10:20 the team began testing the AEV. The AEV was slower going to the gate, but still made it. However, the AEV had trouble coming back after picking up the load. The team used trial and error for different codes adding more power to the AEV.
Date 4/7/19
Time: 5:00-7:00
Members Present: All
Topics/Agenda: edit the third progress report, create the final oral presentation slide, talk about CDR
Action Items with names assigned:
Jeff: work on oral presentation, edit progress report, work on progress report, talk about CDR
Nick: work on oral presentation, work on progress report, talk about CDR
Samira: work on oral presentation, work on progress report, talk about CDR
To be completed before next meeting:
Jeff: submit progress report 3 and oral presentation
Nick: N/A
Samira: N/A
Reflection:
The team met to work on the third progress report. The team edited and added any necessary information. The team also created the draft slide for the final oral presentation, focusing on adding figures and pictures. The team created the Photoshop photo of the members on the AEV to add to the presentation.
Date 4/9/19
Time: 9:10-10:05 (In class)
Members Present: All
Topics/Agenda: work on the website, work on the CDR, complete Final Test
Action Items with names assigned:
Jeff: Complete final test, work on CDR
Nick: Complete final test (code)
Samira: Complete final test, work on website
To be completed before next meeting:
Jeff: work on CDR and website
Nick: work on CDR and website
Samira: work on CDR and website
Reflection:
The Team worked on the code and testing for the final performance test. The team had difficulties when it came to picking up the load, the AEV was too short. Then the team worked on editing the speed so the AEV will successfully come back with the load. During the first official final performance test, it completed the course, but did not stop at the very end. This did not allow the team to collect the data from the AEV leading to false data on the report. While waiting to test, the team worked on editing the website and the CDR.
Date 4/11/19
Time: 9:10-10:05 (In class)
Members Present: All
Topics/Agenda: complete Final Test
Action Items with names assigned:
Jeff: Complete final test
Nick: Complete final test (code)
Samira: Complete final test, work on website
To be completed before next meeting:
Jeff: work on CDR and website
Nick: work on CDR and website
Samira: work on CDR and website
Reflection:
The Team worked on the code and testing for the final performance test. The AEV was not going far enough to reach the gate or pick up the load. During the second final performance test, the AEV did not pick up the load and did not stop in the proper location. However, data was extracted. the time to complete the course was 76 seconds and the energy was 412 J. During the third and final performance test, the AEV did not pick up the load and again went too far for the final stopping point. However, this AEV completed the course faster then the previous two tests.
Date 4/12/19
Time: 9:35-10:55 (In class)
Members Present: All
Topics/Agenda: complete group activity, turn in AEV, work on final presentation
Action Items with names assigned:
Jeff: work on final presentation, take apart AEV, complete group activity
Nick: work on final presentation, take apart AEV, complete group activity
Samira: work on final presentation, take apart AEV, complete group activity
To be completed before next meeting:
Jeff: work on CDR and website
Nick: work on CDR and website
Samira: work on CDR and website
Reflection:
The team did a group activity that they did at the beginning of the year to see how their knowledge of engineering has grown. The team also took apart their AEV and turned it in. Finally, they worked on the final presentation and decided they will be presenting Tuesday.
Date 4/14/19
Time: 5:00-7:00
Members Present: All
Topics/Agenda: work on final presentation, CDR and website
Action Items with names assigned:
Jeff: work on final presentation, CDR and website
Nick: work on final presentation, CDR and website
Samira: work on final presentation, CDR and website
To be completed before next meeting:
Jeff: work on CDR, website, and presentation
Nick: work on CDR, website, and presentation
Samira: work on CDR, website and presentation
Reflection:
The team worked on the budget for the AEV to put onto the final presentation. The team also worked on the parts of the CDR and decided the team will meet Wednesday to finishing editing it. Finally, the team worked on the missing portions of the website, ensuring it was consistent throughout.
Date 4/16/19
Time: 9:35-10:05 (in class)
Members Present: All
Topics/Agenda: submit final presentation
Action Items with names assigned:
Jeff: submit final presentation
Nick: submit final presentation
Samira: submit final presentation
To be completed before next meeting:
Jeff: work on CDR, website
Nick: work on CDR, website
Samira: work on CDR, website
Reflection:
The team presented the final presentation over the progress of the entire project.
Date 4/17/19
Time: 7:30-12:30
Members Present: All
Topics/Agenda: work on final editing CDR and website
Action Items with names assigned:
Jeff: edit CDR and finish website
Nick: edit CDR and finish website
Samira: edit CDR and finish website
Reflection:
The team got together to edit the final CDR and website. The team also submitted the final everything.