Lab 04 was split up into two parts: collecting performance data from the AEV, and inputting the raw data into a MATLAB generated graph. For the first part of the lab, the team took on the task of getting the AEV to not only run on the track, but perform at different speeds and distances. While running, the Arduino collects data on the time, velocity, position, marks, and current of the trip around the track. The team then used a MATLAB data recording program to upload the information found and categorize it into a coherent data chart. The values found are based on units of measurement identifiable by the Arduino system, however, the team must use equations given in the lab manual to convert these values to ones easily applicable to the lab analysis and discussion.
The second part of this lab consisted of developing these values into graphs through MATLAB to determine a visible trend in the data. The plot of the graphs communicated that the team’s coding strategy has proven effective and will be further implemented in future labs. These graphs and their analyses can be found in Appendix C (Figures 1-4). The team will need to complete a plethora of activities prior to the completion of the AEV, but is currently focused on the effectiveness of the code at hand.
The team was able to take away more understanding of code in terms of distance traveled and power used. Based on recorded data and visual observations, the team will also be able to further develop a final draft of the AEV design. In terms of data evaluation, the team is better equipped to find conclusions on how to alter the project based on numerical data and charts which provide a better idea of why and how we should change the code/structure. Additionally, it was realized that the data collection program may not be entirely accurate, being that the code was designed to run the AEV on 40% power for the first two seconds but was reported that it dropped after approximately .25 second.