Meeting 1
Team Meeting Notes
Date: 12– Jan – 2018
Time: 9:30 AM
Location: MSE 225
Members Present: Paul Lyda, Marquis Willis, Thomas Yoder, Issac Zachmann
Topic Discussed: Meeting Minutes and inventory
Objective:
The objective was to create our team and start laying out the groundwork for our project.
To-Do/Action Items:
- Create first Team meeting minutes before next Lab
- Did inventory of the AEV kit
- Exchange contact information between group members
Decisions:
- The team decided Paul would create the outline and the first team meeting minutes by LAB 02
- The team agreed Issac would be responsible for the AEV kit
Reflection:
- We need to make sure the group understands what we need to do before each lab.
Meeting 2
Team Meeting Notes
Date: 18– Jan – 2018
Time: 9:00 AM
Location: MSE 225
Members Present: Paul Lyda, Marquis Willis, Thomas Yoder, Issac Zachmann
Topic Discussed: Creation of the AEV and learning programming basics with the sensors
Objective:
The objective was to build our AEV and to learn the basics of programming the arduino board along with the sensors.
To-Do/Action Items:
- Build the basic AEV kit
- Program the sample code for the arduino board
- Program the sensors to make sure they are working properly
Decisions:
- The team decided Marquis would meet with the grey company in order to build the website for our company.
- The team agreed Issac would be responsible for making sure the sensors are functioning each lab.
- The team agreed we would meet within the next week to complete website update 1
Reflection:
- We have to make sure we manage our time wisely during the lab period to make sure we can complete everything within the time period.
Meeting 3
Team Meeting Notes
Date: 24– Jan – 2018
Time: 9:00 AM
Location: MSE 225
Members Present: Paul Lyda, Marquis Willis, Thomas Yoder, Issac Zachmann
Topic Discussed: Creation of team E website and discussion of team priorities and MCR
Objective:
To lay the foundation of an informative and resourceful website
To-Do/Action Items:
- Create team homepage
- Ensure website links are fully functioning
- Gather team member contact information and graphics and display on website
Decisions:
- The team decided to hire Thomas as a quality engineer to ensure that products meet requirments
- The team agreed on a purpose statement and developed an approach to MCR
Reflection:
- We plan to come back when we have more materials to add to our website and ensure that they are added in a way that maintains the organization.
Meeting 4
Team Meeting Notes
Date: 25– Jan – 2018
Time: 9:30 AM
Location: MSE 225
Members Present: Paul Lyda, Marquis Willis, Thomas Yoder, Issac Zachmann
Topic Discussed: New designs for the AEV, and learning the data analysis tools.
Objective:
Build and test our own design for the AEV and test it’s efficiency
To-Do/Action Items:
- 4 Individual designs for the AEV
- Evaluate those designs and choose which one to build.
- Learned how to use the data analysis software.
Decisions:
- The team decided to make a hybrid of the designs due to the fact the one we started to build didn’t end up being practical thus we didn’t have time to start over.
Reflection:
- We hated the hybrid design we created because the Arduino board was blocked by our new design thus making it very frustrating to upload data to the controller.
Meeting 5
Team Meeting Notes
Date: 1– Feb – 2018
Time: 9:30 AM
Location: MSE 225
Members Present: Paul Lyda, Marquis Willis, Thomas Yoder, Issac Zachmann
Topic Discussed: Created the decision matrices and discussed the pro’s and con’s of each individual design. Website update 2
Objective:
To pick two different designs to use for further development of our AEV and to start on website update 2.
To-Do/Action Items:
- Created a concept screen matrix
- Created the concept score matrix
- Started work on website update two
Decisions:
- The team decided to use AEV designs C and D to use for further development
Reflection:
- The team decided to work further on website update 2 outside of class if needed. We believe we found two potentially good designs to meet the requirements of the MCR
Meeting 6
Team Meeting Notes
Date: 7– Feb – 2018
Time: 9:30 AM
Location: MSE 225
Members Present: Paul Lyda, Marquis Willis, Thomas Yoder, Issac Zachmann
Topic Discussed: We discussed the requirements for the upcoming advanced R&D Lab experiments and worked on website update 2
Objective:
To review and prepare experiments to ensure that data can be efficiently collected and analyzed.
To-Do/Action Items:
- Decide on which experiments the team will be doing
- Finish on website update two
Decisions:
- The team decided to do the Servo, coasting vs power breaking, and Solidworks simulation experiments
Reflection:
- The team will prepare for committee meeting 1, progress report 1, and grant proposal. The team is also much more familiar with its task in the upcoming lab
Meeting 7
Team Meeting Notes
Date: 8– Feb – 2018
Time: 9:30 AM
Location: MSE 225
Members Present: Paul Lyda, Marquis Willis, Thomas Yoder, Issac Zachmann
Topic Discussed: How to determine whether coasting or power braking would be more ideal for our AEV and how we would come to this determination using experimental methods
Objective:
To determine whether coasting or power braking was more efficient
To-Do/Action Items:
- Design an experiment to test coasting and power braking
- Collect relevant data from the experiments and synthesize it to form a conclusion
Decisions:
- The team decided that coasting was more energy efficient, but power braking provided more consistent and reliable stopping
Reflection:
- The team has furthered its understanding of the best ways to implement the AEV, taking into consideration real world problems and obstacles
Meeting 8
Team Meeting Notes
Date: 15– Feb – 2018
Time: 9:30 AM
Location: MSE 225
Members Present: Paul Lyda, Marquis Willis, Thomas Yoder, Issac Zachmann
Topic Discussed: How to implement a servo motor as a reliable and power efficient power braking method, using a custom 3D printed part
Objective:
To design the most efficient implementation of a servo brake
To-Do/Action Items:
- Design an Servo brake as well as a custom 3D printed part
- Design an experimental methodology to test the servo brake
- Collect data and compare it to data collected from coasting vs. power braking
Decisions:
- The team decided that servo braking strikes a good balance between coasting and power braking, providing a consistent and power efficient braking method
Reflection:
- The team will continue to refine the servo implementation and collect information on its impact on the efficiency of the AEV
Meeting 9
Team Meeting Notes
Date: 22– Feb – 2018
Time: 9:30 AM
Location: MSE 225
Members Present: Paul Lyda, Marquis Willis, Thomas Yoder, Issac Zachmann
Topic Discussed: How to represent our AEV design within a functional SolidWorks Simulation
Objective:
A working SolidWorks Simulation accurately representing the movement of our AEV
To-Do/Action Items:
- Create a SolidWorks assembly of our AEV
- Create a SolidWorks simulation using the AEV assembly
- Record the simulation for use as evidence of the functional capacity of our AEV
Reflection:
- The team will use the visuals in the simulation to determine how to better the AEV design
Meeting 10
Team Meeting Notes
Date: 19– March – 2018
Time: 9:30 AM
Location: MSE 225
Members Present: Paul Lyda, Marquis Willis, Thomas Yoder, Issac Zachmann
Topic Discussed: What will be expected in the first performance test and what we need to do to exceed expectations. We need to implement and test one of our alternative AEV designs for the purpose of comparing it to our current.
Objective:
To compare two AEV designs and determine the more efficient model
To-Do/Action Items:
- Develop code to test the AEVs on the main track, taking into account the gate
- Implement alternative AEV design into a working prototype
- Test both AEVs on the main track, collect, record, and compare data
Decisions:
- The team decided to use Concept C from preliminary R&D to test and compare to our current prototype
- The team created a code to in order to meet the goals of performance test 1
Reflection:
- The team created an efficient code using the motorspeed command to complete the goals of the performance test 1
Meeting 11
Team Meeting Notes
Date: 21– March – 2018
Time: 9:30 AM
Location: MSE 225
Members Present: Paul Lyda, Marquis Willis, Thomas Yoder, Issac Zachmann
Topic Discussed: What will be expected in the first performance test and what we need to do to exceed expectations. We need to implement and test one of our alternative AEV designs for the purpose of comparing it to our current.
Objective:
To compare two AEV designs and determine the more efficient model
To-Do/Action Items:
- Develop code to test the AEVs on the main track, taking into account the gate
- Implement alternative AEV design into a working prototype
- Test both AEVs on the main track, collect, record, and compare data
Decisions:
- The team compared the two prototypes within the scenario for performance test 1
Reflection:
- The team found our current pototype to be more efficient, reaffirming our confidence in our AEV and its performance
Meeting 12
Team Meeting Notes
Date: 26- March – 2018
Time: 9:30 AM
Location: MSE 225
Members Present: Paul Lyda, Marquis Willis, Thomas Yoder, Issac Zachmann
Topic Discussed: What will be expected in the second performance test and what we need to do to exceed expectations. We need to create two different codes one using motorspeed and the other one using the command cellerate and compare the efficiency of the two.
Objective:
To compare two different codes determine the more efficient code.
To-Do/Action Items:
- Develop the two codes to test the AEV on the main track, taking into account the gate
- Implement alternative AEV design into a working prototype
- create both codes
Decisions:
- The team declared that we would change the part of the code following the gate to determine which command would be more efficient.
Reflection:
- The team was able to finish writing both codes but wasn’t able to test them. However the team believes that motorspeed will be a more efficient command.
Meeting 13
Team Meeting Notes
Date: 28– March – 2018
Time: 8:30 AM
Location: MSE 225
Members Present: Paul Lyda, Marquis Willis, Thomas Yoder, Issac Zachmann
Topic Discussed: What will be expected in the second performance test and what we need to do to exceed expectations. The comparison of the two commands motorspeed and celerate.
Objective:
To compare the two different codes designed to complete performance test 2
To-Do/Action Items:
- Develop code to test the AEVs on the main track, taking into the account the contact with the caboose.
- Test both AEV codes on the main track, collect, record, and compare data
Decisions:
- The team concluded that the motorspeed is the most efficient way to power the AEV.
Reflection:
- The team found the motorspeed command to be more efficient than the celerate command.
Meeting 14
Team Meeting Notes
Date: 30– March – 2018
Time: 8:30 AM
Location: MSE 225
Members Present: Paul Lyda, Marquis Willis, Thomas Yoder, Issac Zachmann
Topic Discussed: What will be expected in the thrid performance test and what we need to do to exceed expectations.
Objective:
To make a code that is consistent and efficient and meets all requirements in the MCR
To-Do/Action Items:
- Develop code to test the AEVs on the main track, taking into the account the trip back through the gate and stopping at the loading dock.
- Test the AEV code and refine until satisfied with the results.
Decisions:
- Started dividing the work on who should do what on progress report two.
Reflection:
- The teams AEV performed to our expectation and is expected to be under budget.