Meeting Notes

January 

Meeting #1

Team meeting notes 1/25/17, 12pm-1:30pm, Thompson Library, all members

Purpose of meeting: Complete this progress report and create a weekly schedule to determine what needs to be completed in the upcoming week.

  • Tasks Completed from the last meeting
    • Students familiarized themselves with the programming of the Arduino/AEV. (all members)
    • All members of the group created a program to upload into Arduino. (all members)
    • Group set up motors stand and connected motors and battery to Arduino. (Axay, Cole)
    • One code was selected and uploaded into the Arduino. (Sky, Nick)
    • Gained experience with troubleshooting various problems within the programming of code and uploading of the Arduino. (all members)
  • Tasks to be completed for upcoming week
    • Complete construction of prototype AEV (Tuesday all members)
    • Complete lab 3 and understand the concepts it presents (Wednesday all members)
    • Complete a progress report for lab 3 (all members)
  • Decisions made by group
    • Weekly meetings will be on Saturday at 12p.m unless otherwise specified(consensus)
    • Additional meeting will be held this Tuesday 1/24/16 to complete prototype AEV
  • Reflections from previous assignment
    • Only roadblock in last lab was with uploading the program into the Arduino. Upload did not work at first due to group error but even when upload was successful the blue light on Arduino did not flash
    • No deadlines were missed in previous week
    • No work was substandard, or differing expectations, or other conflicts
    • In future it would be beneficial for the group to look into what is to be complete each lab and then plan who will do what so that the most work can be completed in the lab.

Meeting #2

Team meeting notes 1/29/17, 12pm-1:30pm, Thompson Library, all members

Purpose of meeting: Complete this progress report and create a weekly schedule to determine what needs to be completed in the upcoming week

  • Tasks completed from last meeting
    • Construction of sample AEV was completed (all members)
    • Progress report 1/25/17 was completed and submitted (all members)
    • Team became familiar with installation and calibration of reflectance sensors (Sky, Nick, Cole)
    • Team became familiar with new commands to utilize the reflectance sensors (Sky, Nick, Cole)
    • Gained experience by troubleshooting various problems within building of AEV, installation of reflectance sensors, and programming AEV (All members
    • Data was recorded for the different propulsion set ups (Axay)
  • Tasks to be completed for next week
    • Complete Lab 4 (Wednesday, all members)
    • Complete progress report for lab 4 (Sunday, all members)
    • Update portfolio website (Sunday, sky)
  • Decisions made by the group
    • Team meeting this week only  will be held on a different day (consensus).
    • Sky will handle the majority of uploading documents onto the team’s portfolio website(consensus).
    • Cole will be in charge of taking photos for the team’s website (consensus).
  • Reflections from previous assignment
    • Only roadblock from last week was building the AEV design so that the AEV would go around the track in the right direction.
    • No deadlines were missed in previous week.
    • No work was substandard, or differing expectations, or other conflicts.
    • This week in lab the data taken from the wind tunnel was very poor upon review. The collection of this data only took up a small portion of lab time. In the future it would be much more useful to spend more time on taking data to obtain better data that is more useful.

February

Meeting #3

Team Meeting Notes 2/4/17, 12pm-1:30pm, Thompson Library, all members

Purpose of This meeting: Complete this progress report and create a weekly schedule to determine what needs to be completed in the upcoming week

  • Tasks Completed From last meeting
    • Project report for 1/29/17 was completed and turned in ( all members)
    • Team members brainstormed designs and decided upon a design (all members)
    • Team tested the AEV on the test track (all members)
    • Team analyzed and utilized data collected in lab 3c(all members)
  • Tasks to be completed for next week
    • Complete lab 5 and understand the concepts it presents (Wednesday all members)
    • Update portfolio website( Sky Zhang Saturday 12 pm)
    • Complete a progress report for lab 5 (Saturday 12pm all members)
  • Decisions made by the group
    • The team will use the 3030 motor configuration in its final design
    • Additional meeting will be held on Tuesday after class to finish this progress report and add details to designs.
  • Reflections from previous Assignment
    • Only roadblocks from this lab was the uncertainty of what traits of a design would yield the best results
    • No deadlines were missed in previous week
    • No work was substandard, or differing expectations, or other conflicts
    • In the future it would be beneficial for students to only need to dimension and calculate a weight for the final design. It would also be useful for the team to be given a greater understanding of how to calculate the weight of the AEV.

Meeting #4

Team meeting notes 2/12/17, 8pm-9pm, Thompson Library, all members

  • Tasks completed from last meeting
    • Lab 4a/b were completed
    • The AEV was tested on the track
    • Data from the AEV test run was recorded and analyzed
    • The Team became familiar with AEV data analysis tool and the AEV recorder
  • Tasks to be completed for next week
    • Complete lab 5 and understand concepts presented in lab 5
    • Finish this progress report and analyzing the data from lab 4a
    • Complete progress report for lab 5
    • Make 3d plans for body of AEV design
    • Begin working on extra credit video
  • Decisions made by the group
    • There will be an additional meeting held this Tuesday to complete some of the tasks for this week.
  • Reflections from previous assignment
    • The team experience no roadblocks this week all went smoothly in lab and even though both sections of the lab were not completed 4b was easily completed as a team outside of lab
    • No deadlines were missed in previous week
    • No work was substandard, or differing expectations, or other conflicts
    • In the future it would be beneficial to suggest that teams create codes that will show different power consumptions. Our team just created a simple code with only a few commands which made analysis of the phases less interesting.

Meeting #5

Team meeting notes 2/18/17, 12pm to 1:30pm, Thompson Library, All members

Purpose of meeting: Complete this progress report, complete the PDR presentations worksheet, watch the sample presentation videos for the bonus video and finally plan out and create a schedule for what needs

  • Tasks completed from last meeting
    • Students completed lab 5 and understood the concepts it presented
    • Narrowed the choice of AEV designs down to either Cole’s Design or the groups design using concept scoring and screening.
    • More data was recorded and analyzed during the team’s AEV testing using the data recording and analysis tools.
    • Team created and tested an AEV based off our designs.
  • Tasks to be completed for next meeting
    • Watch and critique the sample videos for the bonus video(Tuesday, everyone)
    • Finish the PDR presentation worksheet (everyone)
    • Progress 5 (everyone)
    • Complete lab 6 and understand the concepts it presents(Wednesday, everyone)
  • Decisions made by the group
    • There will be an additional meeting Tuesday after lab to begin discussing work on the bonus video
    • The AEV design that we use will either be the group AEV design or Cole’s AEV design
  • Reflections from last assignment
    • Last week there were no roadblocks during the lab everything went smooth and the team was able to test the AEV and record data
    • No deadlines were missed in previous week
    • No work was substandard, or differing expectations, or other conflict
    • In future, it might be beneficial to build one of the team’s concept AEVs before doing the data recording and analysis lab, this way the data that is recorded will be more relevant to the final AEV

March 

Meeting #6

Team meeting notes 3/5/17, 4pm-5:30pm Sunday, Thompson Library, all members

  • Tasks completed from last meeting
    • Oral Presentation was given
    • Cole’s design was further developed/finalized
    • team began creating the model for our final design in Solidworks
  • Tasks to be completed for next week
    • Finish design in Solidworks
    • design Solidwork part to be printed/decide if this is necessary
    • create water bottle fuselage
    • create code to stop AEV at the gate
    • Start the PDR
  • Decisions made by the group
    • There will be an additional meeting held this tuesday to complete some of the tasks for this week.
    • We will try to use a water bottle as a cheap fuselage
  • Reflections from previous assignment
    • The team enjoyed the oral presentations and were lucky enough to go before Schrock broke the computers and therefore had no problems in the lab.
    • No deadlines were missed in previous week
    • No work was substandard, or differing expectations, or other conflicts
    • No suggestions this week the team felt that our presentation went well and enjoyed watching the presentation of the other teams.

Meeting #7

Team meeting notes 3/22/17, 5:30pm-6:30pm Tuesday, Thompson Library, all members

Purpose of meeting: Complete this progress report, begin working on the PDR, work on thinking of changes that can be made to the design to make it easier to access components

  • Tasks completed from last meeting
    • team built the bottle design for the AEV
    • Team decided the final design for the AEV will be the bottle design
    • Team submitted a design to be laser-cut
    • Team became familiar with servo and integrated it into bottle design
    • More data was recorded and analyzed during the team’s AEV testing using the data recording and analysis tools.
  • Tasks to be completed for next meeting
    • Finish the PDR
    • Create an initial code to use with the AEV for testing
  • Decisions made by the group
    • We will use the bottle design AEV
  • Reflections from last assignment
    • Last week there were no roadblocks during the lab everything went smooth and the team was able to test the AEV and record data
    • No deadlines were missed in previous week
    • No work was substandard, or differing expectations, or other conflict
    • The next lab we are doing requires that the team have two codes it seems like it would be more beneficial for the team to just work on a single code and tweak it in different ways to see how it might be made more efficient

Meeting #8

Team meeting notes 3/30/17, 12pm-1:30pm, Thompson Library, all members

Purpose of meeting: Complete this progress report and create a weekly schedule to determine what needs to be completed in the upcoming week.

  • Tasks Completed from the last meeting
    • team created and tested a code that will complete the mission outlined in the MCR
    • Team analyzed data recorded in the testing of the AEV code(all members)
    • Laser cut arm was created and attached to the AEV. (Nick)
    • Connection to the cargo was created on the AEV (Cole, Nick)
    • Gained experience with troubleshooting various problems within the programming of code and uploading of the Arduino. (all members)
  • Tasks to be completed for upcoming week
    • Test a second code for the AEV
    • Consider what motor percent powers will be the most efficient at various points in the code
    • Improve the efficiency and reliability of the AEV code
  • Decisions made by group
    • Weekly meetings will be on Saturday at 12p.m unless otherwise specified(consensus)
    • The final test will be done on the 224 track
  • Reflections from previous assignment
    • Only roadblock in the process was obtaining the laser cut arm and the difference between the tracks in the 308 and 224 rooms
    • No deadlines were missed in previous week
    • No work was substandard, or differing expectations, or other conflicts
    • In future it would have been beneficial for the team to have turned in their request for laser parts earlier so that they could begin full testing earlier

April

Meeting #9

Team meeting notes 4/7/2017, 5:30pm-6:30pm Thursday, Thompson Library, all members

Purpose of meeting: Complete this progress report, begin working on the PDR, work on thinking of changes that can be made to the design to make it easier to access components

  • Tasks completed from last meeting
    • The team made a much more reliable code
    • The team began work on the CDR presentation
  • Tasks to be completed for next meeting
    • Create code for the AEV to run the last leg of the track
    • Do final test of AEV
    • Begin work on CDR
  • Decisions made by the group
    • We will use a more reliable code even if it uses more energy
  • Reflections from last assignment
    • Last week there were no roadblocks during the lab everything went smooth and the team was able to test the AEV and record data
    • No deadlines were missed in previous week
    • No work was substandard, or differing expectations, or other conflict
    • This week we feel like we have gotten more done just by brainstorming and fixing the problems we see in the AEV. It seems the project would be more effective if there was more time like this. Especially since the team already knew what AEV they wanted to create before performance test 1.