Lab 9 – Performance Test 2
During this lab the team was instructed to come up with two separate codes that would take the AEV around the track. The reason behind two code was that if the team could construct two codes to go around the track, they could combine parts of each separate code into one code. This would lead to the best code from an efficiency standpoint. Ultimately that will be the goal of all the performance tests during these few weeks, to develop the most efficient code and vehicle possible.
The team discovered it is more efficient to have the vehicle have a hard brake at the gate as opposed to coasting to a stop. The use of while loop which terminates when the AEV is going backwards is the best possible way to brake the AEV. It is vital to ensure the ground sensors are in the correct areas, as the vehicle will not run correctly! The AEV center of mass may have been solved in the last week, but it hurt the ability to handle and assemble the AEV.
Team Meeting Notes
Date: April 2nd, 2017
Time: 4:00 pm
Members Present: All
Topics/Agenda: Progress Report Week 10/11, Lab 9ABC
Action Items:
- Portfolio Update: Kaitlyn
Due: 4/3/17
This is an important part of the outreach process. - Oral Presentation Draft: All
Due: 4/7/17
This will be an important part of the final presentation.
- Lab 9 Progress Report: All
Due: 4/3/17
We began outlining and started writing the progress report for Lab 9. - CDR: All
Due: 4/21/17
This is the final report, outlining the entire project. It is vital to start now so we have enough time to adequately write the report.
Weekly Schedule
Task | Team Members | Start Date | Due Date | Time Needed |
Portfolio Update | Kaitlyn | 4/2/17 | 4/21/17 | 1 hour |
Oral Presentation Draft | All | 4/2/17 | 4/7/17 | 1 hour |
Lab 10 Progress Report | All | 4/3/17 | 4/10/17 | 3 hours |
CDR | All | 4/2/17 | 4/21/17 | 7 hours |