Lab 11: Final Testing

For the first day of the final testing lab, the team spent the lab period making adjustments to the code and analyzing the energy usage. For many runs, the AEV was performing inconsistently. After debugging the problem, it was determined that the battery that was being used didn’t have enough energy to produce the same results for each run. Instead, the distance that the AEV would travel decreased each time, even when the code was altered to anticipate it. After acquiring a new battery, the team reverted back to the original number of marks from the beginning of lab to correct the code and have normally functioning code again.

With the correct code adjustments in place, the team was ready for the final testing. To make sure that the code was running successfully, the team ran the AEV on the test track multiple times to ensure consistent performance. Once the team was ready, a TA was brought over to watch the run as the AEV traveled around the track. All of the requirements of the Mission Concept Review were completed correctly. The AEV traveled from the starting point to the gate, where it waited for the designated time while the gate opened. After the gate was open, it traveled to pick up the caboose and return it to the gate, where it waited for it to open once more. Finally the AEV and caboose returned to the starting point.

The time requirement for this test was 150 seconds, but the AEV performed in just over a minute. Once the test was complete both the energy usage and time from the final run were determined and taken into account for the final grading. The time requirement for the final test was under 150 seconds, but the AEV performed in just over 60.  With these results, the final grade was calculated as a 78/50.  The final analysis of the AEV and details on the overall project are found in the CDR, which was prepared following the final test.

CDR