The team spent Lab 09 completing the code and design of the AEV. The final design using the 3D printed part was constructed and tested with throughout this lab. The group also had to add a small metal piece that could be used to magnetically attach to the R2D2 carrier. The code was continuously adjusted to meet the requirements of the mission. There was a lot of trial and error throughout the labs to find what values needed to be inputted into the code. There were a lot of tests because the group had to find how changing the number of marks the vehicle ran would affect its run. It was found that the vehicle has to be propeller for much more marks after it has picked up the cargo to go the same distance it travelled before picking it up. This was due to the dramatic increase in weight that the AEV had to carry.
Schedule:
| Task | Teammate(s) | Start Date | Due Date | Time Needed |
| Lab 10 Progress Report | All | 3/23/17 | 3/30/17 | 3 Hours |
| Lab 10A | All | 3/30/17 | 3/30/17 | 55 Mins |
| Lab 10B | All | 4/4/17 | 4/4/17 | 55 Mins |
| Lab 10C | All | 4/5/17 | 4/5/17 | 1 Hour 20 Mins |
| Update Portfolio | Adam | 3/23/17 | 3/30/17 | 30 Mins |
Team Meeting Notes
Date: 27-Mar-17
Time: 5:00pm
Members Present: Aaron Mckinley, Adam Boes, Christian Considine and Spencer Lohmeier
Topics Discussed: Tasks to be completed for the week
____________________________________________________________________________
Objective:
– Establish a plan for tasks that need to be completed this week
– Make sure all members understand what needs to be completed
– Form a general understanding about where the project needs to be at the end of the
week
____________________________________________________________________________
To do/Action Items:
– Progress Report (SL, AB, AM, CC)
– Backwards Looking Situation (AB)
– Forwards Looking Situation (CC)
– Results & Analysis (AM)
– Weekly Meeting Notes (SL)
____________________________________________________________________________
Status Summary:
The results from the prototype test runs came back with an unexpected outcome for the group.
The prototype that was expected to have a better efficiency, was not the design that ended up being the most efficient. For this reason the group is discussing its options for what changes need to be made to the current design. The goal is to update the design in a way that keeps the same concept, but improves the efficiency. Some changes that may be made are repositioning the arduino and/ battery, or changing the position of the motors. All these are just some of the ideas that are being discussed at this point.
____________________________________________________________________________
Reflection:
– Better use of class time needs and will be a main goal
– Continue to think of ways to make the current design more efficient
– Remain a group that gets along well and produce results