Performance Test 1- Design
Lab 08- Test Readiness Review
Before Lab 08, the group had to decide which member will complete certain tasks. The group plans out the next lab by giving each member a task to do during the lab. Micheal would focus on building and maintaining the AEV, Mark and Charles would do testing and collect data, and Zehan would create the solidwork designs. They also decide what they will be testing for and what they will need to do for each test. This helped the group get prepared before the lab starts.
Lab 08-Preliminary Design Review
During Lab 08, the team tested 2 designs. Design A was the original design chosen during Lab 01 and Lab 03, which was the team concept design. Design B was built to try things that Design A wasn’t doing, like have a vertical base and have propellers facing different sides. Testing for the effectiveness in Power of each design in a Power v Time graph, allowed the group to decide which design would be more efficient for Final Testing.
Design A
Design B
Performance Test 2
Lab 09- Test Readiness Review
Beofre Lab 09, the group decided who would complete each task. Micheal would design and fix the codes, Charles would collect and interpret the data, and Mark and Zehan would test the AEV and give suggestions for fixing the code. This helped the team get prepared for the lab.
Lab 09- Lab Memo
During Lab 09, the team tested the efficiency of two separate codes. Code A was used during Performance Test 1 and Code B was developed specifically for this lab. Code A was simple and used only motorSpeed, goToRealitvePosition, and Brake commands. Code B used the same commands but used a celerate function to speed up the AEV and a motorSpeed to help brake the AEV. After testing each to the same point on the track, the team compiled the data using Matlab and compared the data. A Power v Time graph showed that Code 1 was more energy efficient but the Team still choose Code 2 for final testing. This was due to a consistency that Code 1 lacked. For Final testing, the team decided a consistent code would be better than an efficient code that was never consistent.
Phase Breakdown
Code 1:
| Phase | Arduino Code | Time(seconds) | Energy (J) |
| 1 | motorSpeed(4,25); goToAbsolutePosition(310); | 7.62 | 46.21 |
| 2 | brake(4); goFor(13); | 13.08 | 0 |
| 3 | motorSpeed(4,30); goToRelativePosition(320); | 6.12 | 48.24 |
| 4 | brake(4); goFor(15); | 15.06 | 0 |
| 5 | motorSpeed(4,30); goToRelativePosition(-315); | 7.62 | 56.69 |
| 6 | brake(4); goFor(13); | 13.02 | 0 |
| Total Energy | 151.14 |
Code 2:
| Phase | Arduino Code | Time(seconds) | Energy (J) |
| 1 | celerate(0,30,5,2); motorSpeed(4,30); goToAbsolutePosition(347); reverse(4); motorSpeed(4,20); goFor(2); |
11.16 | 69.8 |
| 2 | brake(4);goFor(9); | 9 | 0 |
| 3 | celerate(0,30,5,2); motorSpeed(4,25); goToRelativePosition(418); reverse(4); motorSpeed(4,20);goFor(2); |
14.16 | 74.7 |
| 4 | brake(4);goFor(5); | 4.98 | 0 |
| 5 | celerate(0,40,5,2); motorSpeed(4,35); goToRelativePosition(-330); reverse(4); motorSpeed(4,20); goFor(2); |
12.06 | 85.43 |
| 6 | brake(4);goFor(9); | 9 | 0 |
| Total Energy | 229.93 |
Performance Test 3
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 |