Lab Summary
This past week the group started to test code for the newly designed AEV. The group considered the new size and mass while coding. Through trial and error, the group tested codes that would create smoother more accurate stop. The group decided to use time instead of the sensor marks due to a previous lack of reliability. The group will prove that coding with time will be more reliable than sensor marks by testing the AEV this next week. .
Takeaways
After performing this lab, many different things were learned. The first half of the lab was spent putting together the AEV into the new design. It is shaped similarly to a biplane in order to fit all the materials in the smallest surface area possible. The next thing that happened was the timing of our AEVs trip. The reason that the group is using time instead of the markers is because we had problems with the sensors. We couldn’t get the sensors to work correctly so we decided to use timing instead. We know this has a higher probability for error, but it was decided that it was safer do to the fact the sensors weren’t working well for our group. This will be a focus going forward. The group will try to be as consistent as possible by coding the AEV using power and time rather than distance.
Team Schedule
Team Meeting Notes
Date: 3-March-2017
Time: 2:45 (Post-Class)
Members Present: All
Objective: To decide what two concepts the lab group would test this week.
To Do:
– Decide and review what should be tested this upcoming week
Decisions:
– Justin wants to work on the physical design more
– Emily wants to figure out a code to get to the first gate
– Megan and Michael think that an analysis should be done to verify using time will work out alright.
– The group decided to test time first before beginning the code therefor they will not waste time if they decide to switch after starting the code.
– Justin will be able to tweak physical design through the rest of the week
Reflections:
– The group needs to verify that time will be consists and work for the whole lab.
Task | Team Member | Start Date | Due Date | Time |
Upload progress report | Emily | 3-9-17 | 3-10-17 | 30 min |
Lab 9 progress report compile and check, appendix | Megan | 3-9-17 | 3-22-17 | 2 hour |
Lab 9 progress report: Situation | Justin | 3-9-17 | 3-19-17 | 1 hour |
Lab 9 progress report: Results and Analysis | Emily | 3-9-17 | 3-19-17 | 1 hour |
Lab 9 progress report: Takeaways | Michael | 3-9-17 | 3-19-17 | 1 hour |