Progress Report Lab 4

Progress Report Lab 4

Lab 4 was meant to familiarize team K with the process of data analysis regarding the AEV. The lab took our team through all the steps of collecting, uploading, and evaluating the data collected by the AEV during its run. After the AEV finished its run, the team used the new Matlab function aevDataRecorder, which extracts data the arduino recorded during its run, to download and record the time, current, voltage, position, and cumulative wheel counts. Team K then developed a Matlab script file that would convert the raw data from aevDataRecorder into data with useful units using the equations found in the Appendix.

Results & Analysis

The data collected during the run can be found in the Appendix. This data tells Team K a couple of things, a large amount of power is needed to get the AEV going from rest, and a constant percentage of power will require a constant amount of watts from the battery. More testing will need to be done in labs to come in order to determine the best way to program the AEV. One possibility would be to program an air brake that would stop the AEV consistently at its position. While this would use significantly more energy than a coasting method, which was at zero watts when tested, it may be worth it if Team K needs consistency. The coasting method may be too unreliable over a greater number of runs.

AEV Takeaways

• When stuck on a particular part of the lab do not hesitate to ask one of the TA’s for help
• n the track would be a good way to conserve power
• Make sure all wires are properly connected before attempting to run the AEV

Forwards Looking To Lab 5

During Lab 5, Team K will actually build and test their team AEV designs. They will determine the success criteria of their AEV design and then screen and score their design concepts in comparison to the sample AEV.  

Weekly Goals

1.     Update portfolio with cover page and past reports
2.     Start EC video
3.     Built AEV design

Upcoming Week Schedule