Lab Description:
This lab consisted of several tasks that all lead to an ultimate goal of completing a half-track run. The first task was to create a code that would cause the AEV, once put on the track, to travel 15 feet forward and 10 feet backward using only the “motorSpeed” command. Next the EEPROM data collected form the AEV during the run was extract and uploaded to a Excel spread sheet, using the “aevDataRecorder” MATLAB function, to allow for numerical calculations to be made. Once the data was analyzed, a code was made that would, once again, go 15 feet forward and 10 feet back but only using the “celerate” command. Both the “motorSpeed” and “celerate” command runs took several attempts and several code changes in order to go the proper distance both times.
Next, a MATLAB code had to be written that would reduce all of the EEPROM data from this lab and all future labs into physical values, and useful tables and figures so that the best adjustments to the code and the AEV could be made. This was done by programming several equations into code to make sure that the proper values were outputted. These equations can be seen here.
Once the MATLAB code was completed the half-track run code was developed. This half-track run consisted of traveling from the Maintenance Station, to the Grand Canyon, to Waves, and then to Alaska. Just like the flat track runs, this run took several attempts, and lots of code tinkering in order to get a desirable and successful run.
Once a successful run was complete the EEPROM data was uploaded to the Excel spreadsheet and the MATLAB code was used to reduce it to physical values just like the flat track runs.
Lab Take Aways:
A plethora of new ideas and concepts were developed through out this lab. An overall idea of how the AEV behaves on a longer run was gotten, as well as the amount of power needed to get up the hills safely, and when braking needs to occur in order to ensure a smooth stop. Moreover, a further understanding of what features will need to be included in the final AEV design. The MATLAB data was also written which will be used in all future runs. Also, and idea of the Arduino code complexity and what the final code should include to ensure a successful full track run.
Lab Schedule:
- February 19, 2020: Complete both flat track runs and extract their respective data, as well as star on coding and completing the half-track run.
- February 26, 2020: Complete MATLAB code and the half-track run.
- February 27, 2020: Start on the lab documentation
- March 3, 2020: Have all graphs and tables completed
- March 5, 2020: Have the memo done and ready to turn in
Meeting Notes:
- The staring position of the AEV on the track makes a difference on where it ends up.
- The reflective tape on the wheels should always start facing up.
- A quick reverse before the destination is required to proved a smooth and accurate stop.
- The momentum lost and gained from traversing the hills needs to be accounted for.
- Nate Johnson will write the introduction, discussion question 2d and 1 c.
- Heath Myers will write the conclusion; discussion questions 3, 2c and all figures and tables for question 1.
- Jason Kibler II will write question 2a and 2b as well as comment the Arduino code.
You can view the whole lab here: AEV Lab 6