Performance Test 2

Performance Test 2

Performance Test 2  had the team compare different variations of the code. The team was to run two different codes and compare the data and observations of each code during AEV runs. Up to this point the team has been focusing on one primary code that they felt would perform the best. However, this test was the team’s time to ensure that their current code was the best code to achieve the team’s mission. The major differences in the two codes used by the teams was the stopping technique and the traveling method. For breaking, the team compared coasting to the gate and reversing the motors to break. For movement, the team wanted to compare using marks to the gate and using time to the gate. The team also wanted to see how the power used affected the speed and the energy output. The team not only wanted the most energy efficient code, but also a code that would be very consistent and effective. By the end of this lab the team knew what methods of coding they would use for their actual run.

The major take away from these past labs relating to the AEV relates to propeller size.  It seems the only way to move the new caboose with our current design is to change the size of the propellers.  Swapping just one is easier, as it does not involve any other design changes, but it has not been tested yet if this will move the caboose.  The other option is to change both propellers, but this will require relocating the supporting “L” arm, which will require a much larger redesign.  The real world take away from this week is that projects will change during the middle of the design process, and engineers need to be flexible and able to react and accommodate these changes.