Test Readiness Review 3
The purpose of the Performance Test Design Lab 3 is to test two different versions of the Arduino code used to run the course for energy efficiency. These versions will consist of altercations to which commands are used and when the commands are used. This will be completed by creating one code using the goToAbsolutePosition() command, and one code using the goToRelativePosition() command in order for the AEV to travel to each of the respective distances. Along with these differences, the first code that uses the goToAbsolutePosition() will use short, high powered bursts of energy, allowing for it to coast longer distances without the motors running. The second code that uses the goToRelativePosition() command will use a constant, lower powered burst of energy to bring the AEV to the next stopping point with less coasting. After creating and running each of the codes, the energy data will be analyzed using the AEV Analysis tool in Matlab. The team will move forward with the most efficient AEV code. Next, the task of finalizing the chosen Arduino code will be completed by implementing minor changes in order to improve consistency. These minor changes will include the amount of marks needed in the goToRelativePosition() or goToAbsolutePosition() commands. After the code has gone through these tests, it will be optimized for maximum energy efficiency of the AEV.
On Tuesday, March 29th, the two codes will be created then tested by running the the AEV along the monorail course two separate times, once for each separate version of the code. The data will then be extracted from the Arduino, and the two graphs will be compared side by side for the lowest total energy usage. The code that has the least energy used will be chosen for the final code. On Friday, April 1st, the minor changes to the number of marks will be completed, giving the team their final code. Throughout this lab, the writing of the two codes will be assigned to the Programmer (Nick), the team’s progress will be documented by the Media Designer (Niki), and extraction of the data and analysis of the energy usage graphs will be done by the Data Analysis/AEV Constructors (Noah and Stefan).
Comparing the efficiency data of the separate AEV codes and deciding among the one that yields the most efficient results will decrease the amount of supplied power needed in the end. This week will enable the team to possess not only the most efficient AEV design, but the most efficient Arduino code to run it as well.