PERFORMANCE TESTS

Performance Test 1

For Performance Test One, the AEV had to travel to the gate, without passing the second sensor, then wait for 7 seconds and proceed from the gate. The team’s approach for the performance test was to create a code based on distance and coasting rather than the time and power needed to coast to the gate. This allows the code to be transferred from one testing room to the other. The Propeller of the AEV broke mid performance test 1, however, this did not prevent the AEV from completing the test. Based on the results from the first performance test, the shell will be removed from the AEV to decrease the weight and allow the AEV to stop faster. In addition, the AEV was tilted, so the team decided to move the L-shaped arm more towards the center of the base.

Performance Test 2

For Performance Test Two, the AEV had to travel to the gate, wait 7 seconds, proceed from the gate to pick up the load, wait 5 seconds when the load is attached, and proceed from the loading zone. Designing the connector for the load’s magnet involved trial and error. At first, the connector was too close to the AEV, causing the propellers of the AEV to intersect with the load. To fix this, the connector was extended outwards from the AEV using spacers and spare nuts. The code was edited to fully stop the AEV well before the second sensor of the gate or the load. After coming to a complete stop, the AEV then traveled forwards at the minimum speed needed to move the AEV. Once the AEV reached the first sensor or the load, the code stopped the motors. Because the AEV was previously traveling the minimum speed, coasting was minimized, helping to reduce the observed inconsistency.

Final Performance Test

For the Final Performance Test, the AEV had to complete the second performance test along with traveling back up to the gate, waiting for 7 seconds, then traveling to the original starting point. The team struggled to create a code for this test. The AEV would move too fast after the gate and was not able to stop. In addition, the AEV would not proceed far enough to reach the load and had to be pushed by a team member.  With more time, these issues of the code could be fixed.