Date: 11 – Jan – 2019

Time: 9:35 AM (Face-to-Face) Hitchcock 224

Members Present: Zach DelVecchio, Allison Musgrove, Joanna Valentas, Claire Perez

Topics Discussed: Lab 1

---

Objective:

Today’s objective was to meet the team. The osu.edu website was created. 

To do/Action Items:

• Program microcontroller – (All)
• Group Selfie Assignment – (All)

Decisions:

• No major decisions made for this lab.

Reflections:

• All of us learned how to successfully program the Arduino microcontroller.
• Writing the program for the microcontroller took longer than expected.

 

Date:  1 – Feb – 2019

Time: 9:35 AM (Face-to-Face) Hitchcock 224

Members Present: Zach DelVecchio, Allison Musgrove, Joanna Valentas, Claire Perez

Topics Discussed: Lab 3

---

Objective:

Today the sampled AEV was assembled and tested in the AEV Extraction Program and Analysis Tool using MATLAB and Excel. After testing the Extraction program, the sensor test was ran again. After the sensor test, the AEV was tested on the track at 25% power.  The small propellers on the AEV were changed to the larger propellers. Then the AEV was tested on the track at 35% and at 50% power. There was a problem getting the AEV to travel on the tracks. To troubleshoot the problem, it was noticed the propellers may be rotating in opposite directions of each other. To check, the power was lowered and to see that the propellers were rotating in opposite directions.

To do/Action Items:

• Assemble AEV –(Zach and Allison)
• Test Data Extraction Tool (Zach)
• Data Analysis Tool (Zach)
• Sensor Test (Zach and Allison)
• Run AEV on track (All)

 

Decisions:

• Use the larger propellers instead of the small propellers. The small propellers did not produce enough power when we first tested it on the AEV track.
• Reverse the propeller that was going in the opposite direction. The propellers were rotating in opposite directions, so for the AEV to move on the track, we had to figure out which propeller was rotating backward instead of forward.
• Use above 25% power. We came to this decision because the AEV would not travel on the track at 25% power.

Reflections:

• Learned how to use the Data Extraction Program.
• Learned how to use the Analysis Tool.
• Learned how to resolve issues with the AEV traveling on the track.

 

Date:  8 – Feb – 2019

Time: 9:35 AM (Face-to-Face)

Members Present: Zach DelVecchio, Allison Musgrove, Joanna Valentas, Claire Perez

Topics Discussed: Lab 4 and Website  Update 2

---

Objective:

Our objective today was to run through the data collection process again and test the AEV on the track at a lower power than last lab. Since we changed the motors to spin in the forward direction, we lowered the power to 25% and tested the AEV on the track.  In today’s lab we must run through exercises 2-4, which includes the programming basics, reflectance sensor test, data extraction tool and creative design thinking. In this lab we began to work on the second website update and designing our team AEV.

To do/Action Items:

• Test AEV on track (Zach and Allison)
• Programming Basics (Zach)
• Reflectance Sensor Test (Zach)
• Website Update 2 (Joanna and Claire)
• Data Extraction (Zach)
• Brainstorming (All)
• Creative Design Thinking (All)
• Prepared deliverables such as plots and code (Zach)

Decisions:

• No major decisions were made during this lab.

Reflections:

• Learned how to organize projects and assignments.
• Learned how to design AEV as a team.
• Learned how to resolve issues with AEV on the track.

 

Date:  12 – Feb – 2019

Time: 8:00 AM (Face-to-Face)

Members Present: Zach DelVecchio, Allison Musgrove, Joanna Valentas, Claire Perez

Topics Discussed: Grant Proposal and Progress Report.

---

Objective:

The objective today was to model a part of the team AEV and finish the grant proposal.

To do/Action Items:

•  Model part for grant proposal (Zach)
• Discuss the modeling process (Allison and Joanna)
• Plan next meeting (All)
• Work on grant proposal slide (All)
• Divide Work for Progress Report (All)
• Team Meeting Minutes (Claire)

Decisions:

• Chose to model the wing part from the AEV team design. This decision was made since the wing introduced the most improvements to the AEV design.
• Divide up the work for the progress report. This decision was made since there were a lot of parts to the progress report, so it would be easier to meet another time when all the parts were finished. Work due by 2/14/18  1:45pm

Reflections:

• Learned how to divide up work properly based on specializations.
• Learned how to work together.

 

Date:  15 – Feb – 2019

Time: 9:35 AM (Face-to-Face)

Members Present: Zach DelVecchio, Allison Musgrove, Joanna Valentas, Claire Perez

Topics Discussed: Plan committee meeting

---

Objective:

The objective is to plan for Committee Meeting 1. The team assigned representatives to the three representatives.

 

To do/Action Items:

• Assign representatives. – (All)

Decisions:

• Claire is the representative for Human Resources. The team came to this decision since Claire is in charge of meeting minutes.
• Allison and Zach are the representatives of Research and Development. The team came to this decision since Allison and Zach were the leaders during the creative design thinking.
• Joanna is the representative for Public Relations. The team came to this decision since Joanna specialized in the website updates.

Reflections:

• No major reflections were made during this lab.

 

Date:  28 – Feb – 2019

Time: 9:10 AM (Face-to-Face)

Members Present: Zach DelVecchio, Allison Musgrove, Joanna Valentas, Claire Perez

Topics Discussed: APP 16 and R&D Methodologies

---

Objective:

The objective is to begin creating methodologies. The two methodologies will be based on Reflectance sensor testing and SolidWorks Simulations. For the SolidWorks simulations, prototypes will be created, then tested and this process will be repeated. The data for this will be shown using concept scoring. The effectiveness of the reflectance sensor will be tested using the SolidWorks and it’s positioning on the track.  The team also talked about how to begin APP 16 and what that work will look like.

 

To do/Action Items:

• Create methodology for Reflectance Sensor. (Zach)
• Create methodology for SolidWorks Simulation. (Allison)
• Fix website (Joanna)
• Team Meeting Minutes (Claire)
• APP 16 (All)

Decisions:

•  R&D1 will be Reflectance Sensor Testing. Reflectance Sensor methodology will be tested by the absolute position command and the error in the distance the reflectance sensors measurements. The team came to this decision because it will help optimize the AEV for the best results.
• R&D 2 will be SolidWorks simulations. SolidWorks simulation methodology will include tests of different prototypes. These prototypes will go through concept scoring. The team came to this decision because it will help optimize the AEV for the best results.

Reflections:

• Team learned how to create a methodology for different types of AEV testing.

 

Date:  01 – Mar – 2019

Time: 9:35 AM (Face-to-Face)

Members Present: Zach DelVecchio, Allison Musgrove, Joanna Valentas, Claire Perez

Topics Discussed: R&D 1 Methodology and Testing

---

Objective:

The object today is to begin data collection for R&D methodology, which is reflectance sensor testing. The accuracy of the reflectance sensor is to be tested. The team will be testing the accuracy of the reflectance sensor and the distance it says it travels by using the goToAbsolutePosition function vs. The assigned distance for the AEV will be measured using the tape ruler that is built into the track. The reflectance sensor will be observed for error in measurement by two tests. For the first test, the AEV (programmed at 0%)  will be pulled along the track by hand for a certain distance, in this case the distance is 96.00 inches. This will be repeated for 5  trials. The measurement on the track is taken from the from the front of the back wheel. The marks traveled by the AEV will be converted to inches using the conversion factor of 0.4875 inches=1 mark.  Then the difference between the measured and the true value will be calculated. Percent error will then be calculated as well. In the second test, the AEV will still be pulled by hand, but programmed to run 197 marks which is approximately 96 inches.  Then the distance that the AEV traveled in inches (measure directly using tape ruler on track,) will be converted to marks. Then the difference between the measured marks value and the programmed marks value.

To Do/Action Items:

• Testing AEV on track (Zach and Allison)
• Program for the AEV (Zach)
• Collecting data (All)
• Conversions (Allison)
• Fixing website (Joanna)
• Team Meeting Minutes (Claire)

Decisions:

• For Test 1, run the AEV at 0% power. This is so that the team can drag the AEV across the track while being able to track the marks by the AEV.

Reflections:

• Learned how the reflectance sensors worked better.

 

 

 

Date:  05 – Mar – 2019

Time: 9:10 AM (Face-to-Face)

Members Present: Zach DelVecchio, Allison Musgrove, Joanna Valentas, Claire Perez

Topics Discussed: R&D Methodology 2 , Progress Report 1 Fix, discuss the 2nd Progress Report

---

Objective:

Today the team will work the R&D Methodology 2, the SolidWorks Simulations.  The team also began to edit and fix the problems in the first progress report. The team also began to talk about the 2nd progress report and how to divide up the work over spring break.

 

To do/Action Items:

• SolidWorks Simulation (Zach)
• Website Update (Joanna)
• Discuss Project Report 2 (All)
• Team Meeting Minutes Claire

Decisions:

• Lower the height of the wings significantly. This is due to the flow and pressure. The pressure is low on wings and lowering the height will change how the AEV will push against the wind when traveling.

Reflections:

• No major reflections were made during this lab.

 

Date:  07 – Mar – 2019

Time: 9:10 AM (Face-to-Face)

Members Present: Zach DelVecchio, Allison Musgrove, Joanna Valentas, Claire Perez

Topics Discussed: R&D Methodology 2 , Progress Report 2, Website Update 3, Performance Test

---

Objective:

Today the team will work the R&D Methodology 2, the SolidWorks Simulations.  The work for the project report 2 was split up among the team. The website update 3 was checked over. The performance test for the AEV was started during this lab period as well. The team had to determined how to program the AEV so that it will travel up the incline and then wait at the gate, and then go through the gate once again. The team had to determine the power necessary through trial and error. The engine wire fell out which resulted in one of the propellers to not work.  The power necessary to get over the incline was somewhere around 35%

To do/Action Items:

• SolidWorks Simulation (Zach)
• Website Update (Joanna)
• Project Report Work (All)
• Progress Report 2 (Claire)
• Performance Test (Allison)

Decisions:

• Parts for the AEV should be 3D printed. The parts for the revised AEV should be printed so that the AEV can be programmed based on the design and not the sample.

Reflections:

• Learned how to determine to program the AEV properly for the performance testing.

 

 

Date:  08 – Mar – 2019

Time: 9:35 AM (Face-to-Face)

Members Present: Zach DelVecchio, Allison Musgrove, Joanna Valentas, Claire Perez

Topics Discussed: Performance Test 1 and Progress Report 2

---

Objective:

Today the team will continue to work on Performance Test 1. The AEV was not properly running on the track and not accurately measuring marks . The reflectance sensors wires were reversed. Once the reflectance sensors were reversed the first test on the track was close between the gate sensors. The team decided to add  more power at the end and then coast.

To do/Action Items:

• Program AEV (Zach)
• Run AEV on the Track (Allison)
• Progress Report 2 (Joanna and Claire)

Decisions:

• The reflectance sensors were reversed. This decision was made because the reflectance sensors were measuring the distance traveled in the opposite direction the wheels were going on the track. This made it difficult for the AEV to recognize how much distance it traveled.

Reflections:

• Learned how to program the AEV properly for the performance testing.

 

Date:  19 – Mar – 2019

Time: 9:10 AM (Face-to-Face)

Members Present: Zach DelVecchio, Joanna Valentas, Claire Perez

Topics Discussed: Performance Test 1 and PowerPoint slide for R&D Presentation

---

Objective:

Today the team will have to present their performance test to the instructional team. The first 15 minutes of class were used to test and tweak small things about the code and AEV design.  The team will have to program the AEV to make it to the gate, stop for 7 seconds and proceed through the gate. For the first practice trial, the AEV hit the sensor but then reversed too far and did not move. The team decided to increase the speed for the AEV to make it through the gate. For the second trial the AEV completed all the requirements for the performance test, but it was going too far after going through the gate, so the team decided to lower how long the AEV travels at a certain speed from 4 seconds to 2 seconds. On the third trial, the AEV ran fine, except it was slightly past the red line, so the team decided to slow down faster. On the fourth and fifth trials, the AEV completed all the requirements. The team felt confident to complete the performance test. Then the team began to talk about the Oral presentation for next lab.

 

To do/Action Items:

• Program AEV (Zach)
• Run tests on the track with the AEV (All)
• Performance Test 1 (All)
• PowerPoint (All)

Decisions:

• Increased the speed for the AEV to make it through the gate. The AEV was reversing too far and there wasn’t enough power to push the AEV through the gate, so the power was increased after triggering the sensor for 7 seconds.
• Decrease how long the AEV travels at a certain speed from 4 to 2. The AEV was traveling too far after proceeding through the gate, so this would make the AEV slow down and stop earlier.
• Slow the AEV faster before stopping at the gate. The AEV’s front wheel would stop on the red line, so slowing the AEV faster would trip the sensor and not pass the lines.

Reflections:

• Learned how to program the AEV to complete certain tasks by using trial and error with code.

 

Date:  21– Mar – 2019

Time: 9:10 AM (Face-to-Face)

Members Present: Zach DelVecchio, Joanna Valentas, Claire Perez, Allison Musgrove

Topics Discussed: R&D Presentation

---

Objective:

Today the team presented their Advanced Research and Development about the SolidWorks Simulation and the Reflectance Sensor.

 

To do/Action Items:

• Presentation (All)

Decisions:

• No major decisions were made during this meeting.

Reflections:

• No major reflections were made during this meeting.

 

Date:  22– Mar – 2019

Time: 9:35 AM (Face-to-Face)

Members Present: Zach DelVecchio, Joanna Valentas, Allison Musgrove

Topics Discussed: Performance Test 2

---

Objective:

Today the team began performance test 2. The team was trying to figure out how to make the design work, but realized it would only push them back in time. The team began testing the same code from Performance Test 1 to know where to begin on performance test 1. The team tested the speed the AEV goes down the track and the AEV does not make it all the way down the track. So the AEV should go for longer at the same speed. Then the AEV recoiled too much when attaching to the caboose, so the speed had to be lowered.

 

To do/Action Items:

• Program AEV (Zach)
• Figuring out how to design the AEV. (Allison and Joanna)
• Testing AEV on track (All)

Decisions:

• The team decided to not use their design for the performance test 2. The team came to this decision by realizing that the AEV must reverse backwards and the design at this moment would only push the team back.

Reflections:

• Learned how to program the AEV to complete certain tasks by using trial and error and experimentation with code.

 

Date:  26– Mar – 2019

Time: 9:10 AM (Face-to-Face)

Members Present: Zach DelVecchio, Joanna Valentas, Alison Musgrove

Topics Discussed: Performance Test 2

---

Objective:

Today the team completed performance test 2. The AEV recoiled too much when attaching to the caboose, so either the speed or the time had to be lowered. First, the team decided to raise the time and lower the speed. However the final code used the original speed and time, but reversed the motors at the end. This made sure the AEV connected to the caboose in control. The team also created a new design for the AEV.

 

To do/Action Items:

• Program AEV (Zach)
• New AEV Design (Alison)
• Testing AEV on track (All)

Decisions:

• The team decided to use the original AEV design to complete performance test 2 in order to save time. The team also decided to use the new design in the future.

Reflections:

• Learned how to approach the caboose in control by reversing the motors to brake.

 

Date:  28 – Mar – 2019

Time: 9:10 AM (Face-to-Face)

Members Present: Zach DelVecchio, Joanna Valentas, Claire Perez

Topics Discussed: Committee Meeting 2 and Fixing Website Updates

---

Objective:

Today the team attended the  2nd Committee Meeting. The team also started fixing the website updates.

 

To do/Action Items:

• Committee Meeting (All)
• Website Update (All)

Decisions:

• No major decisions were made during this meeting.

Reflections:

• No major reflections were made during this meeting.

 

Date:  29 – Mar – 2019

Time: 9:35 AM (Face-to-Face)

Members Present: Zach DelVecchio, Joanna Valentas, Claire Perez

Topics Discussed: aR&D 3 and Progress Report 3.

---

Objective:

Today the team will begin aR&D 3, which will be brake speed test. The team also began to start the Progress Report 3.

To do/Action Items:

• aR&D 3 (Zach)
• Progress Report 3 (All)

Decisions:

• No major decisions were made during this meeting.

Reflections:

• No major reflections were made during this meeting.

 

Date:  02 – Apr. – 2019

Time: 9:10 AM (Face-to-Face)

Members Present: Zach DelVecchio, Joanna Valentas,  Allison Musgrove

Topics Discussed: aR&D3

---

Objective:

Today the team continued to work on advanced research and development 3, which is brake testing. The team also decided to redesign the AEV design.

 

To do/Action Items:

• aR&D3 (Zach)
• Redesign AEV (Allison and Joanna)

Decisions:

• The team decided to redesign the AEV. The old AEV design would not be beneficial when running in the opposite direction on the track.

Reflections:

• The team learned how the AEV brake testing will affect how the AEV stops.

 

Date:  04 – Apr. – 2019

Time: 9:10 AM (Face-to-Face)

Members Present: Zach DelVecchio, Joanna Valentas, Claire Perez, Allison Musgrove

Topics Discussed: Practice  for Final Performance Testing

---

Objective:

The team began to practice testing for the Final Performance test. The team tested their revised AEV design on the track. On the first run the team realized that the top propeller was too long and would hit the track. The team decided to change the top propeller to a smaller propeller. The team noticed with more runs, that the smaller propeller made the AEV go much slower. The team also realized that the revised AEV design is heavier, so the code must be adjusted.  The team put the large propeller back onto the AEV, but adjusted the design slightly so it would not hit the track or the other propeller.

 

To do/Action Items:

• Program AEV (Zach)
• Test AEV on track (All)

Decisions:

• Team decided to make the top propeller a smaller propeller. This is because the large propeller was hitting the track when it ran. It was slightly too long. The bottom propeller will stay as a large propeller.
• Code must be adjusted for the new weight of the AEV. The AEV is heavier than the last AEV design, so the code must be adjusted for the extra weight.
• The team decided to make adjustments so that the top propeller could be a large propeller as well. Having the small propeller on the top was not creating enough power to run the AEV to complete the tasks.

Reflections:

• No major reflections were made during this lab period.

 

Date:  05 – Apr. – 2019

Time: 9:35 AM (Face-to-Face)

Members Present: Zach DelVecchio, Joanna Valentas, Claire Perez, Allison Musgrove

Topics Discussed: Practice  for Final Performance Testing

---

Objective:

Today the team is going to continue to practice for the final performance test.  For the first test the team realized that the revised AEV design is much more efficient on the track. The reverse speed was bumped up to 75% since the AEV was traveling very fast up the first incline. The team realized that we could use a higher speed to increase the efficiency and lower the costs. The 75% was then way too much, so this was reduced to 65%. The team is trying to figure out how to get the AEV to break before the gate sensors. The team got the AEV to brake, but too early.  The team had to experiment with various codes to figure out how to get the AEV to travel on the track properly. Then the AEV was not breaking fast enough. The team then tested the AEV and it worked. The team began coding for the rest of the performance test. The AEV must go slower when approaching the caboose. Then AEV speed must also increase with the caboose when approaching the gate once again. The team had to add a code that was “the end of the track minus where the AEV needs to go.” This code will help the AEV break when approaching the gate again from the opposite direction.

 

To do/Action Items:

• Program AEV (Zach)
• Test AEV on track (All)

Decisions:

• The reverse power was reduced from 75% to 65%. This is because the 75% speed made the AEV fly way too far back, therefore the team bumped the reverse power to 65%
• The speed was increased with the caboose when approaching the gate. This is because the AEV did not have enough power going up the incline.
• The team had to add a code that was “the end of the track minus where the AEV needs to go” in marks.  This decision came to be to help the AEV stop properly when approaching the gate with the caboose.

Reflections:

• Learned how to smooth out errors in code.
• Learned how to work together to create new code for the AEV.

 

 

Date:  09 – Apr. – 2019

Time: 9:10 AM (Face-to-Face)

Members Present: Zach DelVecchio, Joanna Valentas, Claire Perez, Allison Musgrove

Topics Discussed: Final Performance Testing Day 1

---

Objective:

Today the team will continue practicing for their final performance test and complete one of their trials for the performance test. For the first run of the day, the AEV tripped the second sensor, so the AEV’s stopping point was moved back three marks. The AEV is breaking too early at the end. The team decides to let the AEV stall longer at the gate. Then the AEV needed to break for longer so that it will properly stop at the gate when reversing back to the starting point. Tje team began their first trial for final testing.

To do/Action Items:

• Program AEV (Zach)
• Run AEV on track (All)

Decisions:

• AEV’s stopping point was moved back three marks. This is due to the AEV trippng the second sensor. This will help stop the AEV earlier.
• Let the AEV stall and break faster at the gate. This is because the AEV was running too fast when traveling in the reverse direction towards the gate.

Reflections:

• No major reflections were made today.

 

Date:  11 – Apr. – 2019

Time: 9:10 AM (Face-to-Face)

Members Present: Zach DelVecchio, Joanna Valentas, Claire Perez, Allison Musgrove

Topics Discussed: Final Performance Testing  Day 2

---

Objective:

Today the team will be working on their second and third trials for the final performance testing. For the first 20-30 minutes of class the team was practicing their code. The team had problems with the battery. The team replaced the battery and then began to sort out any problems in the code. In the second final performance test, the AEV ran perfectly except at the end, the AEV did not stay within the two tape marks with the caboose. In the third run, the AEV tripped the first sensor on the gate and then ran into the track at the end of the performance test.

To do/Action Items:

• Program AEV (Zach)
• Run AEV on track (All)

Decisions:

• No major decisions were made during this lab period.

Reflections:

• Learned how to work out problems in code efficiently.

 

Date:  11 – Apr. – 2019

Time: 9:10 AM (Face-to-Face)

Members Present: Zach DelVecchio, Joanna Valentas, Claire Perez

Topics Discussed: AEV Turn In

---

Objective:

Today the team will Turn-In the AEV Kit and go through the AEV check list.

To do/Action Items:

• Turn in the AEV (All)

Decisions:

• No major decisions were made during this lab period.

Reflections:

• Learned how to work out problems in code efficiently.