Lab 10- Test Readiness Review
Before Lab 10, the team decided who would complete each task. Micheal, Zehan, and Mark would focus on testing by running each test and collecting the data needed for the lab memo. After the run, Charles would compile the data into graphs, tables, and other forms of information that can be used to evaluate the energy efficiency of the entire run.
Lab 10- Lab Memo
The team was only able to complete one code for this section due to complications with the track and with how the team had been changing the code. Since the team had been using a Guess and Check System for coding, the code took much longer to perfect for final testing. Instead of making chnages and evaluating how they effect the energy effieceny, the team just evaluated the minor changes made to the code and the pros and cons of how the AEV runs using this code. The final code made at the end of this lab will be used for the Final Test.
Phase Breakdown
Part 1
Phase | Arduino Code | Time(seconds) | Energy (J) |
1 | reverse(2);
celerate(0,30,5,2); motorSpeed(4,30); goToAbsolutePosition(352); |
8.94 | 58.85 |
2 | reverse(4);
motorSpeed(4,20); goFor(2); |
3 | 15.22 |
3 | brake(4);
goFor(9); |
9 | 0 |
4 | reverse(4);
celerate(0,30,5,2); motorSpeed(4,25); goToRelativePosition(440); |
10.44 | 54.89 |
5 | reverse(4);
motorSpeed(4,20); goFor(2); |
3.72 | 17.04 |
6 | brake(4);
goFor(5); |
5 | 0 |
Total Energy | 146 |
Part 2
Phase | Arduino Code | Time(seconds) | Energy (J) |
7 | celerate(0,40,5,2);
motorSpeed(4,35); goToRelativePosition(-357); |
10.42 | 83.24 |
8 | reverse(4);
motorSpeed(4,30); goFor(2); |
2.04 | 16.15 |
9 | brake(4);
goFor(9); |
9 | 0 |
10 | reverse(4);
motorSpeed(4,35); goToRelativePosition(-340); |
7.74 | 71.32 |
11 | reverse(4);
motorSpeed(4,20); |
2.04 | 8.08 |
12 | goFor(2);
brake(4); |
2 | 0 |
Total Energy | 178.79 |