Meeting #1
Date: 27-Jan-2018
Time: 5:00 pm (Face-to-Face)
Members Present: Chris Wagner, Hadi Saputra, Will Nguyen, and Sean Mclaughlin
Topic: Post Lab 1
Objectives:
The main focus of the meeting, was to get a good understanding of what was required for the AEV project. We also want to just touch base with each other in person and get a better idea of who are team members were. We also need to discuss how the website will be set up and who will be completing each task.
To do/Action Items:
-Work on website design
-Find who will complete each section
Decisions:
-We decided Will would create the skeleton of the website, Chris and Hadi will work on the Executive Summary, and Sean will work on the MCR summary.
Reflections:
-We will all need to get more familiar with how the website functions and is set up. We will continue with construction in between labs.
Meeting #2
Date: 03-Feb-2018
Time: 12:00 pm (Face-to-Face)
Members Present: Chris Wagner, Hadi Saputra, Will Nguyen, and Sean Mclaughlin
Topic: Post Lab 2
Objectives:
To get an understanding of the Adrino Code, assemble the AEV prototype, and figure out what needs to be updated for the website.
To do/Action Items:
-Run through functions for Adrino Code
-Assemble prototype AEV
-Update Website
Decisions:
-Chris and Hadi will assemble AEV
-Sean will work with William on Adrino Code
-Whole team with collaborate on the website
Reflections:
-At first it was a little difficult to get the Adrino running since we first tried to download the software with a mac. After switching computers it went a lot smoother. The AEV is assembled as much as it can be outside out class. Now we have to start brainstorming on what our teams unique AEV design will be.
Meeting #3
Date: 06-Feb-2018
Time: 3:30 pm (Face-to-Face)
Members Present: Chris Wagner, Hadi Saputra, Will Nguyen, and Sean Mclaughlin
Topic: Post Lab 3&5
Objectives:
The main focus of today is to get all the concept drawings finalized and formatted properly. Also to finish lab 5, which was the concept screening. To get a better understanding of what exactly needs to go into the progress report and to assign tasks to each one of our team members. While also adding any additional information to the website.
To do/Action Items:
-Finish Sketches
-Perform Concept Screening
-Update website
-Assign tasks to finish Progress report
Decisions:
-Hadi will work on section 5 for the progress report, and create the template in Excel
-Chris will work on submitting all the documentation of our sketches and progress photos
-William will work on the Adrino Code part of the report
-Sean will complete section 2 for the progress report and cover note taking.
Reflections:
Everyone had the concept drawings done and finalized. While a little confusing at first on what exactly needed to be done for the progress report, that was finally worked out. As a group we will keep better records of each step of the AEV construction process, which will cause it to be much easier in creating future reports.
Meeting #4
Date: 14-Feb-2018
Time: 8:00 pm (Face-to-Face)
Members Present: Chris Wagner, Hadi Saputra, Will Nguyen, and Sean Mclaughlin
Topic: Committee meeting
Objectives:
The main focus of this meeting was to get everything we have worked on together and ready to discuss and present. The team also covered some concept ideas and discussed possible future work for the project.
To do/Action Items:
-Gain compete understanding of what we will discuss at the Committee Meeting
Decisions:
-Chris and Will: these team members will be representing R&D
-Sean: he is representing HR
-Hadi: he is representing PR
Reflections:
The team has a great handle on the project and everyone knows and is executing their assigned tasks. Some that was more of a side note to the meeting, but still important to the overall project, was Chris’s design of the Servo moto mounding piece, the whole team agrees it will be a great addition to the final design.
Meeting #5
Date: 25-Feb-2018
Time: 8:00 pm (Face-to-Face)
Members Present: Chris Wagner, Hadi Saputra, Will Nguyen, and Sean Mclaughlin
Topic: Presentation, motor configuration, and material choice
Objectives:
The main focus of this meeting was to get an idea of how the team wanted to address the presentation for the next lab. This also included deciding which base material and which motor configuration the group would continue with.
To do/Action Items:
-Gain compete understanding of what we will discuss at the Presentation
-Who will cover which topics
-Make final decision on what the materials and motor set up will be
Decisions:
-Chris and Will: Covering the motor configuration tests ran in the Advanced R&D
-Sean and Hadi: Covering the material testing ran in the Advanced R&D
-The team has reviewed the data collected from the analysis tool in MATLAB, and the combination of the MDF body and two motors will produce the most efficient AEV, and is the design the group will be moving forward with
Reflections:
The team meeting was very productive. An almost complete design has been decided on and each member is satisfied with the results. The main problem, which has been a running issue, is finding more time to be able to perform test runs. The next step is discovering how to get the AEV to travel accurate distances and stop when needed. This will be address at the next lab.
Meeting #6
Date: 05-March-2018
Time: 6:30 pm (Face-to-Face)
Members Present: Chris Wagner, Hadi Saputra, Will Nguyen, and Sean Mclaughlin
Topic: Covering second progress report. Discuss next step in development. Make final decision on motor configuration.
Objectives:
Today the team will determine what still needs to be completed for the progress report and dividing tasks. A final decision on the motor configuration needs to be reached, one motor or two. Figure out what will be attempted in next lab, so the team can arrive prepared.
To do/Action items:
-Finish project report two
-Start to address getting the AEV to stop in an effective manner
-Deciding on a final motor configuration (addressing the data collected)
-Decide code that will be run during lab, so testing can begin upon arrival
Decisions:
The team will move forward with the two-motor design discussed in previous reports, because while the two-motor does use more energy per meter, it will better suit the added weight of the passengers, plus one motor will be turned around to give the AEV adequate power on the travel back from destination. William is going to write the code for the AEV before next lab period. The team will submit the drawing for the servo mount tomorrow, so it can be 3D printed. Minor adjustments need to be made for progress report (e.g. tables and figures), Chris will add these in before Thursday of this week.
Reflections:
Team A has made good progress on the AEV, moving one step closer to a finished product. The extra lab time in the upcoming weeks will be a big benefit, because the design ideas can be tested, and therefore finalized, much quicker. Once the servo mount is printed and the vehicle can be stopped reliably, the last step will be creating a fully functioning code.
Meeting #7
Date: 09-March-2018
Time: 6:30 pm (Face-to-Face)
Members Present: Chris Wagner, Hadi Saputra, Will Nguyen, and Sean Mclaughlin
Topic: Preparation for the performance test 1 and braking system
Objectives:
The team will determine how to approach the task of stopping at an exact location. Decide whether to continue using the propellers to stop the vehicle, or spend the extra time and money figuring out how to use the servo motor to create a brake. Decisions should be made on these topic before the next lab time in order to maximize testing time.
To do/Action items:
-Finalize breaking method.
-Address spending limits and time management.
-Have an at least an outline of a performance code.
Decisions:
Team A will proceed with using the propellers to stop the AEV. This was discussed in depth, however, after looking at the time required to get the need braking arm constructed and the cost to the company, the added benefit didn’t outweigh the draw backs. The first performance test is coming up soon and the company cannot afford to wait that long for something that might not work. Also, the current process of braking the AEV has been working well and energy usage is low, so the new brake isn’t priority. A rough calculation of the distance to the first gate was determined, and a code has been outlined to get there. Fine tuning the code, to maximize energy used, will have to be performed in lab.
Reflection:
Progress has been good, the team is working at a proper pace, and is slightly ahead of schedule. As each lab period passes, the team is getting more comfortable with the code, allowing for more tests to be run. This is great considering there is a limited amount of time allowed under the current budget. Everyone is happy with the base design and moving forward the focus can be on trying to get the energy consumption as low as possible.
Meeting #8
Date: 15-March-2018
Time: 8:00 pm (Face-to-Face)
Members Present: Chris Wagner, Hadi Saputra, Will Nguyen, and Sean Mclaughlin
Topic: Performance Test One, CDR Draft
Objectives:
Touch base on what will be accomplished in the next lab. Discuss possible sources of error in the performance of the AEV. Work out any flaws in the code, and make sure the code for the upstairs lab is separate from the code run on the downstairs track. Look over the data collected from previous runs, to discuss improvement. Discuss CDR draft and work out a time line to start and complete.
To do/Action items:
–Assign tasks for each team member to complete for the CDR draft
-Refine code to complete performance test 1
-Figure out all up coming due dates and deadlines
Decisions:
The team has decided to run a code that provides a high energy boost to the AEV initially and allow the AEV to coast as long as possible. From the analysis tool, it seems on average this method consumes the least amount of power. It was also decided to go with the code that is consistent and will complete the first test, and worry about streamlining the code until after the AEV had pass its test. Two separate files have been created to hold different codes for the two lab rooms. Using the same code on both tracks doesn’t work, the results are not consistent, and therefore it was necessary to do. Finally, the group will divide the CDR into two sections, having two team members assigned to each half.
Reflection:
While the team has been getting better at forming code to execute different objectives, materials themselves seem to varying performances. The team doesn’t know if it is the motor, battery, or Arduino that is causing inconsistent results. Some labs the same code will work perfectly for half time period, then will suddenly start missing its marks and not travel at the right speeds. This will be something to look into when time allows.
Meeting #9
Date: 25-March-2018
Time: 7:00 pm (Face-to-Face)
Members Present: Chris Wagner, Hadi Saputra, Will Nguyen, and Sean Mclaughlin
Topic: Performance Test 2
Objectives:
The team has successfully created a code that will get the AEV to and through the first gate. The next step is to get the AEV to travel down the first loading port and connect with the caboose that will be holding the passengers. The team needs to figure out how to get to this location and connect with the caboose smoothly, entering the loading dock too fast will cause damage to both objects and possibly not form a connection. Once the AEV and caboose are secured, there is a minimum loading time that has to be met. The step after that is handled in another performance test.
To do/Action items:
-Determine time after leaving gate one that the motor should be shut off.
-Decide whether to power brake before reaching the caboose or try and allow the AEV to just coast till the connection.
-Figure out if the speed leaving the loading station should be gradual or if it is better to run the motors similar to the initial start.
Decisions:
The distance to shut of the motors after passing through the gate, was determined to be somewhere around 300 marks. This will allow the AEV to reach the slope and use momentum to travel the rest of the distance to the loading dock. Using a power brake consumes a lot of energy, the team will attempt allowing the AEV to coast all the way to the point where it connects with the caboose. This method has worked well so far and is saving the company a lot of money. Finally, the consensus is to supply a short high energy burst to the motors when leaving the loading station, and power it long enough to reach the gate. In past trails, slowly increasing power has proven to consume more energy.
Reflection:
The team is well prepared for the performance test 2. Sometime will be taken at the beginning of lab to implement the adjustments made, but after that the AEV will be ready for testing. Moving forward the team will need to develop the code to complete the whole track, however this shouldn’t be too difficult since most of the distances and code has been developed already. Hopefully there will be time before the final performance test to make further adjustments to the code. While the code currently being used is working well, Team A is striving to produce the most efficient AEV in the company. Any extra time allowed will be used to focus on that, however the main priority is developing a code that successfully runs the whole track, and any further changes will be extra.