Performance Test 2

Team R was tasked with completing another Performance Test in order to verify that the team’s work was on track with the mission of the AEV. The AEV had to travel to the gate, wait 7 seconds, and then travel through the gate. It then needed to pick up a load on the other side. This Performance Test 2 focuses on perfecting the code used once the design was optimized. The team used the design utilizing a one-push-one-pull propeller configuration.

It was noted during performance test two that the AEV stopped 5 inches earlier than last test, using the same control program. The team was unsure why this was happening but assumed it needed to be re-calibrated due to variables such as the battery changing since last test. Brian rewrote the code for the AEV and the test was re-run. Zip ties were also added to the sensors to help with consistency.

During the second day of AEV testing, the AEV was still being inconsistent. The AEV was testing multiple times to try and fix this. The AEV would work fine for 5 runs or so, and then stop to early or too short. The AEV had virtually no way of being able to be fixed, because it would work and then not work depending on the run. The team decided to complete the performance test and chance it.

 

The operational objective page shows the code comparison used in Performance Test 2.

Operational Objectives