Performance Test 2 is focused on perfecting the code used to operate the AEV in order to obtain the most efficient and consistent runs on the track. The lab’s focus on the code is due to the focus on physical design in Performance Test 1 in which Group M chose the final design to subject to further testing. Coding is the next step to the final AEV and is just as important as the physical design. To ascertain the best programming strategy two different codes with different strategies were written, tested, and had data recorded from each to be analyzed below. This analysis is designed to help the group make a decision on which strategy will provide the most efficient and consistent run for the AEV.
Since the team did not finish both codes, only the first code was tested on the track. While testing the AEV on the track using the first code, the team noticed an issue with the servo arm. Even when the servo was set to 180˚ the servo did not make enough contact with the track to stop the AEV’s movement. This was corrected by re-uploading the code. The team could not find a reason behind this discrepancy, but uploading the code again fixed the issue. The team also observed the distances travelled by the AEV varied between each run. This was attributed to the malfunctioning servo arm. Had the team run both codes, the second code—the code with short high powered pulses—would have been more efficient.
This lab taught the engineers the importance of considering different methods of accomplishing the same goal. This lab required students to create two separate codes to accomplish the same goal, and observe which code was most efficient and most consistent. There are multiple ways to accomplish a goal, but it is important to consider what is the best way to complete the goal. This lab also taught the engineers how to troubleshoot code, and find the errors within the code. This will be useful in future labs and in the industry as well.
Figure 1: Power vs. Time of Code Implementation
Team Meeting Notes:
Date: 3–April–2016
Time: 10:30am-12:30pm
Members Present: Kailee Gulbin (KG), Ben Reed (BR), Paul Conway (PC), Grant Miller (GM)
Topics Discussed: Performance Test 2 Memo
Objectives:
Today’s main focuses were meeting as a team to discuss how to prepare an Memo for Performance Test 2, compiling the data, and discussing which code works best, and how to approach finishing the second code.
To do:
-u.osu.edu (KG)
-Executive Summary (PC, KG, GM, BR)
Reflections:
-The u.osu page was not finished completely, need to uploading the memo when completed, and finish typing the description.
-The memo is not complete. Need to finish proof reading, inserting tables and figures, and also finish the second code to test in the next performance test.