Lab 4 – System Analysis 2 & Design Analysis Tool

Summary

Lab 04 consisted of two parts, lab 04a and lab 04b. The purpose of lab 04a was to download data from the automatic control system, convert EEPROM Arduino data to physical parameters, and to calculate performance characteristics using the converted physical parameters. The equipment required to complete Lab 04a included a functional AEV with the battery attached, a USB connection cable, and an AEV test rail. The first task completed during the lab was writing a simple program that would move the AEV from the starting point to the first stop, just before the gate, when it was placed on the track. During its time on the track, the Arduino collected a significant amount of data. To ensure the data collection was finished, the team waited until the yellow light on the Arduino controller stopped flashing before switching the power off. Next, the Arduino was connected to the computer using the USB cable and the EEPROM data was uploaded to an excel spreadsheet using the provided AEV Data Recorder script file in MATLAB. The final task that was completed required that a MATLAB script be written to convert EEPROM data to usable metric data. Once the data was converted, the AEV’s performance was analyzed through calculations and figures.

The purpose of Lab 04b was to become familiar with the design analysis tool and how to use it to upload, analyze, plot and export data in the form of figures. Lab 04b required no physical equipment other than the computer on which the analysis was performed. Lab 04b consisted of installing and using the AEV Analysis tool to visualize and relate the data collected during the AEV’s run on the track. Using the analysis tool, the data saved from Lab 04a was used to create plots of Power vs Time and Power vs Distance so that the team could see how the AEV performed throughout the whole run. Using this data, the team will be able to make changes to both the Arduino code and the AEV itself to decrease the amount of power necessary to perform all required tasks. The AEV Analysis tool will be used for the remainder of the project in order to study the performance of each modification made to the AEV and to make future programming and design decisions.

Takeaways

Lab 04 provided the team with a significant amount of data regarding the AEV’s usage of energy during its run. Upon analyzing the data, several key takeaways developed. First, the team will need to find a way to reduce the energy used during phase 1 while keeping the speed of the run consistent. Second, the team will need to discuss ways to slow down the AEV in phase 2, perhaps by using the servo motor to physically brake the vehicle rather than reversing the motors. The most important takeaway from the lab was that the team will need to spend time optimizing both the arduino code as well as the physical body of the AEV to reduce weight and improve efficiency.

Schedule

The lab will be completed on Tuesday, February 14th from 11:10AM – 12:30PM. Following the lab, the team will meet on Thursday, February 16th from 6:00PM-8:30PM to begin the progress report and complete as much of it as possible. If the progress report is not completed on Thursday, the team will meet again on Sunday, February 18th at 5:30PM and will work on the lab until it has been completed. The team will also update the project portfolio. The group has also been split off into two different tasks. Ryan Born and Trevor McDowell will be focusing on making the AEV code as efficient as possible while Khalid Musa and Gonzalo Diago will be working to make the physical AEV as efficient and light as possible. Khalid and Gonzalo will be meeting Wednesday at 7:00 PM to discuss the current situation of the AEV, while Trevor and Ryan meet at the same time on Wednesday to continue to develop the most efficient velocities for the code while making it as concise and efficient as possible.

 

Meeting Notes

Date: 9 February 2017

Time: 7:00 P.M. (Remote – Skype)

Members Present: Gonzalo Diago, Trevor McDowell, Ryan Born, Khalid Musa

Topics Discussed:Lab 05 Progress Report

Objective:

Today, the group met in order to discuss the Lab 05 Progress Report as well as their final AEV design (based off of the tests in the lab on last Tuesday).

To Do:

  • Finalize the tables and charts for the AEV test (KM, GD)
  • Look further into the efficiency of the AEV (power vs velocity) (TM, RB)
  • Lab 05 Progress Report (KM, GD, TM, RB)

Timeline/Schedule

– The group will meet on Sunday to discuss Lab 07 as well as to complete the Lab 06 Progress Report.

-Throughout the week, the portfolio will be updated when team members have free time.

Decisions Made

  • The group will meet on Sunday to complete the Lab 06 Progress Report and prepare for Lab 07.
  • The group has also divided parts for the Lab 05 Progress Report.
  • The group will work to perfect the AEV design, as well as finding the optimal power input.

Reflection

Last week for the group went fairly well, despite a few scheduling conflicts, the group was still able to meet remote, and finish the progress report. Although the group did not finish what was required in the lab, the group was able to meet outside of class time and make the necessary calculations, tables, and charts. The group was also very productive in that they were able to also discuss their final design further, and how they would be ready to complete the final objective in the most efficient manner.