January
Date: 1 – Jan – 2019
Time: 9:35 am (In Lab 224)
Members Present: Ryan Burrows, Alec Glenwright, Vincent Bello, & Mitchell Mullholand
Topics Discussed: AEV coding set-up and website set-up
Objective: Today’s main focus was on getting the website and the Arduino set up and running. We also looked at the problem, criteria, and constraints of the project to figure out what we actually had to do
To do/Action Items:
- Run the Arduino with code blocks in order to get the motors to start and stop individually and in unison – (VB, MM)
- Set up the u.osu.edu website in partnership with Group I – (RB, AG)
Decisions: The group started to divide up roles with Ryan and Alec working with the website, while Vincent and Mitchell wrote the Arduino code to figure out how to program and work it.
Reflections: Next time each group member should be more involved in each aspect of the project. That way if the two members who worked on the Arduino or website got sick and couldn’t make it to lab, the other two members could still progress and work effectively on the project.
Date: 18 – Jan – 2019
Time: 9:35 am (In Lab 224)
Members Present: Ryan Burrows, Alec Glenwright, Vincent Bello, & Mitchell Mullholand
Topics Discussed: Reflectance sensor set-up and AEV kit dissection
Objective: Today’s main focus was on testing the reflectance sensors and making sure they are working in combination with the Arduino. We also looked at our AEV kit and made sure we had all the supplies we should have had.
To do/Action Items:
- Check the AEV kit and make sure all materials are present – (RB)
- Set up the Arduino code for testing the reflectance sensors – (VB)
- Make a draft of the AEV for testing the reflectance sensors – (RB & MM)
Decisions: The group decided that Vincent would be in charge of writing most of the Arduino code as he has had the most experience with it (day 1 and 2 of preliminary R&D he has worked with the Arduino code). Also it was decided that Vincent and Mitchell would be in charge of the AEV kit, bringing it to and from class, as Mitchell wanted to have the kit and try some things with it.
Reflections: Vincent and Mitchell need to remember to bring the AEV kit to class every lab day and check their GroupMe in case another group member needs the kit for whatever reason.
Future Tasks: All group members should be prepared for the next lab session and start to think of possible ideas for the structure of the AEV. Also by next lab, group members need to create the team working agreement and load it onto the website.
February
Date: 2 – February – 2019
Time: 9:35 am (In Lab 224)
Members Present: Ryan Burrows, Alec Glenwright, Vincent Bello, & Mitchell Mullholand
Topics Discussed: Data collection set-up and AEV test run
Objective: Today’s main focus was on testing the data collection system via test runs of the given AEV design
To do/Action Items:
- Make sure AEV doesn’t fall of the track during test runs – (Everyone)
- Set up Arduino code and collect the data from the test runs – (VB)
- Start updating website – (RB)
- Compile data to make graphs from data collected – (AG)
- Research Design Possibilities – (MM)
Decisions: The group decided that Mitchell would be in charge of the designing of the AEV in solid works, as well as printing any parts needed at low cost from his personal 3D printer.
Reflections: For some reason the data collector didn’t convert any of the units, so without the conversions, we are stuck with data that can’t be graphed. We will have to email the GTA. Also, it seemed like the fan powered AEVs were very variable, they didn’t always work the best and sometimes they just didn’t move at all. To get the AEV moving, a nudge was needed to overcome the static friction, so if we go the fan route, we need to adjust the code to compensate for the extra push in the beginning.
Future Tasks: Alec will get the data issue sorted out and create the graphs by next class. Vincent will upload the code to the website. Ryan will update the website for the second update. All team members will have an orthographic drawing of a proposed AEV design by next Friday meeting.
Date: 8 – February – 2019
Time: 9:35 am (In Lab 224)
Members Present: Ryan Burrows, Alec Glenwright, Vincent Bello, & Mitchell Mullholand
Topics Discussed: Data re-collection and AEV final design
Objective: Today’s main focus was on collecting the data again in order to graph it and deciding on an AEV final design.
To do/Action Items:
- Make sure AEV doesn’t fall of the track during test runs – (Everyone)
- Set up Arduino code and collect the data from the test runs – (VB)
- Start updating website – (RB)
- Compile data to make graphs from data collected – (AG)
- Discuss – (MM)
Decisions: The group decided that we are going to try and make a direct drive AEV.
Reflections: For some reason the data collector didn’t convert any of the units, so at this meeting we did the same tests and procedure as last meeting to get the correct data.
Future Tasks: Alec will use the new data to create graphs and get the screw from Lowe’s. Vincent will update the code on the website. Mitchell will update his solidworks model and create drawings of the extra parts needed for the grant proposal. Ryan will update the website for the second update. All team members will have their tasks completed by next Thursday and will assist each other in writing the progress report by next Friday.
Date: 15 – February – 2019
Time: 9:35 am (In Lab 224)
Members Present: Ryan Burrows, Alec Glenwright, Vincent Bello, & Mitchell Mullholand
Topics Discussed: Grant Proposal, its usage, and Committee Meeting
Objective: Today’s main focus was on expertly presenting our grant proposal and discussing how we will use the money depending on the magnitude of the grant, if any, we received.
To do/Action Items:
- Make sure AEV doesn’t fall of the track during test runs – (Everyone)
- Set up Arduino code and collect the data from the test runs – (VB)
- Start updating website – (RB)
- Compile data to make graphs from data collected – (AG)
- Discuss – (MM)
Decisions: The group decided that we would use the grant for all of our 3D printing needs. Also, Alec and Vincent will be the humanitarian positions, Ryan will be the public outreach, and Mitchell will be the R&D position for the committee meeting.
Reflections: We could have been a little more clear about which parts we needed to 3D print in our design. It would have helped if we had a laser pointer or control of the mouse on the main computer.
Future Tasks: We will all prepare for the committee meeting by uploading all documents needed, thinking about topics to discuss, and dressing up business casual.
Date: 29 – February – 2019
Time: 9:10 am (In Lab 308)
Members Present: Ryan Burrows, Alec Glenwright, Vincent Bello, & Mitchell Mullholand
Topics Discussed: aR&D Methodology
Objective: Today’s main focus was on discussing and figuring out what exactly we are testing and doing for our aR&D 1.
To do/Action Items:
- Discuss methodology design ideas- (Everyone)
- Start writing code to test our methodology ideas- (VB)
- Start updating website – (RB)
- Set up graphs and tables for methodology – (AG)
- Think of new design iterations to fix any problems- (MM)
Decisions: The group decided that for aR&D 1 , we will be testing how different speeds of the motor affect energy consumption of our prototype AEV. Essentially we are trying to find the speed to run the AEV at (when it doesn’t have a load) so it completes the test under the specified time, but uses the least amount of energy in doing so, thus saving money.
Reflections: We could have been more prepared and decided on a methodology quicker, as it was, we barely got started testing the AEV and so we will have to play catch-up for the next few classes.
Future Tasks: We will come to the next lab with ideas for aR&D 2 so we can get started on that right away after aR&D 1. Alec will have graphs made to input the collected data onto, and Vincent will have the aR&D 1 code fully completed.
March
Date: 1- March- 2019
Time: 9:35 am (In Lab 224)
Members Present: Ryan Burrows, Alec Glenwright, Vincent Bello, & Mitchell Mullholand
Topics Discussed: aR&D 1 Tests and aR&D 2 methodology
Objective: Today’s main focus was on getting our AEV running and starting to collect data for aR&D 1.
To do/Action Items:
- Make sure AEV doesn’t fall of the track during test runs – (RB, AG, MM)
- Set up and fix Arduino code and collect the data from the test runs – (VB)
- Update website – (RB)
- Compile data to make graphs from data collected – (AG)
- Disassemble and reassemble AEV between trials to allow for data download and upload via Arduino – (MM)
Decisions: The group decided that we definitely need a new design printed for the AEV to give access to the Arduino when the capsule is closed. We also decided that for aR&D 2 we will be testing how different speeds of the motor affect energy consumption of our prototype AEV, with the passenger car attached. Essentially it is similar to the first methodology, but now instead of trying to find the optimal speed of the AEV going down the track, we are trying to find the optimal speed coming back with the passenger car attached. The two speeds should be different as the passenger car is pretty heavy and so should reduce the speed and use more power than the un-encumbered AEV.
Reflections: We could have been more prepared and had an optimized Arduino code, as halfway through we found out we could do three trials in one run of the AEV, which could’ve saved time.
Future Tasks: Vincent and Alec will write and submit the methodology for aR&D1 and aR&D2 by before lab on the next Tuesday. Mitchell will send SolidWorks files to the OSU department so we can get our next iteration of the AEV printed to make testing easier and faster.
Date: 4- March- 2019
Time: 9:10 am (In Lab 308)
Members Present: Ryan Burrows, Alec Glenwright, Vincent Bello, & Mitchell Mullholand
Topics Discussed: aR&D 2 Tests and Progress Report
Objective: Today’s main focus was on finishing aR&D 1 data collection, and then start aR&D 2 data collection.
To do/Action Items:
- Make sure AEV doesn’t fall of the track during test runs – (RB, AG, MM)
- Set up and fix Arduino code and collect the data from the test runs – (VB)
- Write aR&D 2 Arduino code – (VB)
- Update website – (RB)
- Compile data to make graphs from data collected – (AG)
- Disassemble and reassemble AEV between trials to allow for data download and upload via Arduino – (MM)
Decisions: The group decided that Ryan would talk with Harry about the Progress Report to see where points where lost before redoing the report.
Reflections: We are still behind and need to finish aR&D 2 on Thursday at the latest
Future Tasks: Vincent will optimize the aR&D 2 code as best as possible to save time and allow aR&D 2 to be finished in lab this coming Thursday. Alec will start decoding the data and converting it to graphs via excel, and finish by Thursday after lab. Mitchell will devise away for the pssenger car to attach to the current AEV model so aR&D 2 can be completed on the coming Thursday in lab.
Date: 7- March- 2019
Time: 9:10 am (In Lab 308)
Members Present: Ryan Burrows, Alec Glenwright, Vincent Bello, & Mitchell Mullholand
Topics Discussed: aR&D 2 Tests, Progress Report, Performance Test
Objective: Today’s main focus was on finishing aR&D 2 data collection, and discussing the Performance Test.
To do/Action Items:
- Make sure AEV doesn’t fall of the track during test runs – (RB, AG, MM)
- Set up and fix Arduino code and collect the data from the test runs – (VB)
- Start writing Performance Test code – (VB)
- Update website – (RB)
- Compile data to make graphs from data collected – (AG)
- Disassemble and reassemble AEV between trials to allow for data download and upload via Arduino – (MM)
Decisions: The group decided that Ryan would talk with Mr. Cohen about the Progress Report after lab today in order to see where points where lost, and then tell the group if the report still needs to be redone. We also decided that we wouldn’t worry about the Performance Test in lab tomorrow, but finish aR&D 2. If we finish aR&D 2 early, then we will work towards the Performance Test, but we plan on testing after break.
Reflections: We completely finished aR&D 2 data collection so if we perfect the code and running of the AEV in lab tomorrow (Friday), then we should try and do the Performance Test to get it out of the way.
Future Tasks: Vincent will write the Performance Test code and complete it before lab on Friday. Since Ryan knows what Mr. Cohen said about the Progress Report he will fix the report and make changes, and after all other members will proof read and make sure he fixed all the mistakes present in the first iteration of the Progress Report (before lab on Friday).
Date: 8- March- 2019
Time: 9:35 am (In Lab 224)
Members Present: Ryan Burrows, Alec Glenwright, Vincent Bello, & Mitchell Mullholand
Topics Discussed: Performance Test 1, Progress Report 2, Website Update 3, aR&D Oral Presentations, and Spring Break work
Objective: Today’s main focus was on getting the Performance Test code completed and then actually do the performance test.
To do/Action Items:
- Make sure AEV doesn’t fall of the track during test runs – (Everyone)
- Set up and fix Arduino code and collect the data from the final Performance Test – (VB)
- Start writing Performance Test code – (VB)
- Update website – (RB)
- Compile data to make graphs from data collected – (AG)
- Disassemble and reassemble AEV between trials to allow for data download and upload via Arduino – (MM)
- Transition all AEV components to the new shell – (MM)
Decisions: We decided to do our performance test 1 today and to try to make our code more robust to account for any battery current variations we might come across.
Reflections: We aced the performance test and the AEV seemed to stop on the other end right were it needs to to pick up the passenger car.
Future Tasks: Mitchell will tinker with the new shell to figure out kinks and make sure everything fits and looks like it is supposed to. Vincent will update the Arduino code to make more robust. Ryan will finish website update 3 and Alec will create graphs and tables for the data collected. Everyone will help finish progress report 2.
Date: 19- March- 2019
Time: 9:10 am (In Lab 308)
Members Present: Ryan Burrows, Alec Glenwright, Vincent Bello, & Mitchell Mullholand
Topics Discussed: aR&D Oral Presentation
Objective: Today’s main focus was on getting the aR&D oral presentation completed.
To do/Action Items:
- Complete Problem and Overview Slides – (AG)
- Complete aR&D 1 Slides – (RB)
- Complete Conclusion and Recommendation slides and format power point- (VB)
- Complete aR&D 2 Slides – (MM)
Decisions: The group decided to focus all time on getting ready for the aR&D oral presentation as we had already completed the first performance test.
Reflections: We need to make sure to speak slowly and clearly in order to get within the specified time limit.
Future Tasks: Everyone will dress in business casual attire and prepare for the oral presentation next class.
Date: 21- March- 2019
Time: 9:10 am (In Lab 308)
Members Present: Ryan Burrows, Alec Glenwright, Vincent Bello, & Mitchell Mullholand
Topics Discussed: aR&D Oral Presentation
Objective: Today’s main focus was on expertly presenting our aR&D oral presentation
To do/Action Items: Present aR&D oral presentation (Everyone)
Decisions: N/A
Reflections: We went over our allotted time limit and so for future presentations we need to not read directly off of the slides and speak in our own words
Future Tasks: Everyone get prepared for performance test two next class by looking at the requirements for the test.
Date: 22- March- 2019
Time: 9:35 am (In Lab 224)
Members Present: Ryan Burrows, Alec Glenwright, Vincent Bello, & Mitchell Mullholand
Topics Discussed: Performance Test 2 and Critical Design Review
Objective: Perfect code for the second performance test and discuss the CDR
To do/Action Items:
- Make sure AEV doesn’t crash (Everyone)
- Set up AEV for test runs (MM)
- Change and Fix Arduino Code (VB)
- Work on Website (RB)
Decisions: We decided to create two sections of our code, one for lab 224 and one for 308 in order to deal with the difference in the two tracks.
Reflections: We need a way to get reliable results from the AEV each time, we need to have the ability in our code to be able to keep moving if it didn’t pass a certain point so we can complete the performance tests quicker with more accurate results.
Future Tasks: Alec will finish the appendices, Ryan will complete the results and discussion, Mitchell will complete the conclusion and recommendations and format, and Vincent will complete the executive summary and intro and methodology sections of the CDR. This will be completed by 3/27/17 at the very latest in order to be submitted by 3/28/19. Also, everyone will dress up and prepare for committee meeting 2 next class.
Date: 26- March- 2019
Time: 9:10 am (In Lab 308)
Members Present: Ryan Burrows, Alec Glenwright, Vincent Bello, & Mitchell Mullholand
Topics Discussed: Performance Test 2 and CDR
Objective: Complete Performance Test 2
To do/Action Items:
- Make sure AEV doesn’t crash (Everyone)
- Work on assigned CDR parts (Everyone)
- Update Website (RB)
Decisions: We completed performance test 2 today and got a score of 100%. We also talked more about the CDR and everyone’s parts.
Reflections: We all should have started our CDR parts sooner as we now only have a couple or days to finish it.
Future Tasks: All CDR parts should be finished by tomorrow in order for it to be able to submitted before class on Thursday.
Date: 28- March- 2019
Time: 9:10 am (In Lab 308)
Members Present: Ryan Burrows, Alec Glenwright, Vincent Bello, & Mitchell Mullholand
Topics Discussed: Committee Meeting 2
Objective: Attend and complete committee meeting 2
To do/Action Items: Complete committee meeting 2 and discuss aR&D 3 (Everyone)
Decisions: For aR&D 3 we decided to increase the control of the AEV. We are going to try to change how the caboose attaches, how it speeds up after it attaches to the caboose, and possibly braking in order to decrease the ‘bounce’ / slipping of the wheel.
Reflections: In order to not get behind, we need to stay on task and finish aR&D 3 on time.
Future Tasks: No immediate pressing matters need to be completed by next class.
Date: 29- March- 2019
Time: 9:35 am (In Lab 224)
Members Present: Ryan Burrows, Alec Glenwright, Vincent Bello, & Mitchell Mullholand
Topics Discussed: aR&D3
Objective: Start aR&D 3
To do/Action Items:
- Code in the jolt testing (VB)
- Update the website (RB)
- Make sure the AEV doesn’t cause any safety infractions (Everyone)
Decisions: Because the code for the jolt needed to be written, we decided to test the alternate caboose attachment system and see if that fixed the initial slipping.
Reflections: We did this test with a rough contraption, so we need to test the actual 3D attachment once it is printed.
Future Tasks: We still have most of our aR&D 3 to finish so we need to stay on task for the next couple of classes.
April
Date: 2- April- 2019
Time: 9:10 am (In Lab 308)
Members Present: Ryan Burrows, Alec Glenwright, Vincent Bello, & Mitchell Mullholand
Topics Discussed: aR&D3
Objective: Complete aR&D 3
To do/Action Items:
- Code in the rest of the tests and correct code after runs (VB)
- Set up and film tests (MM)
- Run the AEV and update the website (RB)
- Make sure the AEV isn’t a safety concern (Everyone)
Decisions: The jolt and the slide distance with the resistance band coating and new 3D printed attachment were tested
Reflections: Half the class we didn’t physically have the AEV, so we got very far behind in aR&D 3 and need to make up this time lost.
Future Tasks: We still have most of our aR&D 3 to finish so we need to stay on task for the next couple of classes.
Date: 4- April- 2019
Time: 9:10 am (In Lab 308)
Members Present: Ryan Burrows, Alec Glenwright, Vincent Bello, & Mitchell Mullholand
Topics Discussed: Final Performance Tests
Objective: Start the Final Performance Test
To do/Action Items:
- Attach new attahment method and rubber wheel (MM)
- Write and fix code (VB)
- Update Website (RB)
- Make sure the AEV doesn’t fall off the track (Everyone)
Decisions: We are going to finish up the rest of the aR&D 3 on Friday as the final performance tests will take place in lab 308, so today we are working towards the final performance tests.
Reflections: The final test days are getting very close so we need to buckle down and get our tests done.
Future Tasks: Everyone needs to work on their progress report three sections and have them essentially finished by next class so they can be turned in on April 7.
Date: 5- April- 2019
Time: 9:35 am (In Lab 224)
Members Present: Ryan Burrows, Alec Glenwright, Vincent Bello, & Mitchell Mullholand
Topics Discussed: Final Performance Test, aR&D 3, and poster draft
Objective: Finish the remaining part of advanced R&D 3 that we need to complete and then work on the final performance test code
To do/Action Items:
- Set up and prepare AEV for each run (MM)
- Write and fix code (VB)
- Update Website (RB)
- Make sure the AEV doesn’t fall off the track (Everyone)
Decisions: Despite the final tests taking place in room 308, we will continue to prepare and test the AEV in this room, 224. Hopefully the difference in tracks isn’t too great, and the marks can be changed a little in order to still have a perfect run in room 308.
Reflections: We were able to achieve a perfect run by the end of lab time, meaning we know it is possible, and that should mean the same thing can be replicated in room 308 next class. Upon finishing the last half of advanced R&D 3, it was found that the latex wheel as well as the different passenger car attachment were beneficial to the AEV and so will be included on it.
Future Tasks: Progress Report 3 sections should be mostly finished and poster sections were assigned and should be completed by April 7.
Date: 9- April- 2019
Time: 9:10 am (In Lab 308)
Members Present: Ryan Burrows, Alec Glenwright, Vincent Bello, & Mitchell Mullholand
Topics Discussed: Final Performance Tests
Objective: Complete the three final performance tests
To do/Action Items:
- Set up and prepare AEV for each run (MM)
- Write and fix code (VB)
- Update Website (RB)
- Make sure the AEV doesn’t fall off the track (Everyone)
- Stand at gate to open or close it if need be (AG)
- Stand at passenger car end to manually attach if necessary (RB)
- Stand at starting line to set up and manually stop AEV if need be (MM)
Decisions: We will try to get a perfect our first time and if we do we will try to immediately do the other two tests in order to reduce the affect of battery variance.
Reflections: Most of class was spent trying to get the AEV to run perfectly. For some reason it wasn’t attaching to the passenger car nor making it through the gate anymore. That led to us only being able to test the AEV once, despite getting a perfect on that run.
Future Tasks: Nothing in the immediate future needs to be finished before next class. If any members have extra time, they can start working on the final poster or final CDR.
Date: 11- April- 2019
Time: 9:10 am (In Lab 308)
Members Present: Ryan Burrows, Alec Glenwright, Vincent Bello, & Mitchell Mullholand
Topics Discussed: Final Performance Tests
Objective: Complete the last two final performance tests
To do/Action Items:
- Set up and prepare AEV for each run (MM)
- Write and fix code (VB)
- Update Website (RB)
- Make sure the AEV doesn’t fall off the track (Everyone)
- Stand at gate to open or close it if need be (AG)
- Stand at passenger car end to manually attach if necessary (RB)
- Stand at starting line to set up and manually stop AEV if need be (MM)
- Film one of the tests (RB, AG)
Decisions: We will run the AEV immediately to see if the perfect code from last time still achieves a perfect score. If not, more tests will need to be conducted to fix any issues.
Reflections: Since we already had a code that ran a perfect test, it didn’t take long to get the code perfect with the new battery. After two perfect runs, the AEV was tested and didn’t score perfectly. It tripped the second sensor at the gate and didn’t attach to the passenger car, despite no change in code since the two perfect trial runs. The third test wasn’t perfect either. For some unknown reason, the AEV got stuck after the gate opened and wouldn’t move (we suspect due to a drained battery), but other than that it ran perfectly; however, that skewed our time and energy data, increasing the cost dramatically for that run.
Future Tasks: We were nominated to the website showcase, so everyone needs to bring ideas on what to add to the website to really make it stand out next class.
Date: 12- April- 2019
Time: 9:35 am (In Lab 224)
Members Present: Ryan Burrows, Alec Glenwright, Vincent Bello, & Mitchell Mullholand
Topics Discussed: Engineering Showcase and CDR
Objective: Decide which showcase we want to attend and start working on the final CDR
To do/Action Items:
- Update Website (RB)
- Work on CDR sections (Everyone)
Decisions: Since we were also recently nominated to go to the showcase, we didn’t have to take apart our AEV and turn in the kit. We were only allowed to go to one showcase so the team selected the website showcase.
Reflections: For the CDR, we didn’t follow the rubric as closely as we should have; therefore, we need to fix all of our errors and then update it with the new information by April 18.
Future Tasks: Mitchell needs to bring the AEV kit to class on April 16 so it can be turned in. Everyone needs to finish their poster sections and Ryan needs to finish updating the website by April 14 so it can get turned in on April 15 in time for the showcase and our final oral presentation on April 16.