Lab 02

The team has worked on the Preliminary R&D Document.

Exercise 1 – Programming Basics – Arduino Glossary Displayed in Background

Exercise 2 – Reflectance Sensors – Displayed in Lab 07

Exercise 3 – Creative Design Thinking – Displayed in Plans/Codes

Exercise 4 – Design Analysis Tool – Displayed in Lab 06 & Lab 07

Exercise 5 – Concept Screening and Scoring – Displayed in Lab 02

Screening matrix for our hand-drawn designs for the AEV.

 

 

 Lab 06- Feb 9

Durning this Lab, we began testing the model AEV for its power consumption and efficiency. The code we used was:

The run yielded or data for energy used by the AEV over time:

After the results of our run were collected. We realized that the Reflectance sensors were not correctly counting the number of wheel rotations.  Our relative Error was wildly outside of normal boundaries.  As a consequence, the team will have to use the next lab period to determine the cause of this error.

Lab 07 – Feb 26

The team continued to work with Advanced Energy Analysis.

 

The team has used the following code to test the AEV’s power consumption over a given period of time.  We then used the AEV Data analysis tool to determine a power/distance ratio, which remains inaccurate.

Advanced Energy Analysis Code:

reverse(4);
motorSpeed(4,25);
goFor(4);
motorSpeed(4,0);
goFor(10);

 

Over the last several lab periods, the team has run into consistent troubles coming from the reflectance sensors.  Below is a graph from the AEV analysis tool of 4 different runs using the Advanced Energy Analysis Code.  For the first 3 runs, the AEV measured around half of the actual distance traveled.  While this was consistent, it was consistently inaccurate. After fixing the orientation of the reflectance sensor wires, we began to record accurate data, as shown in the 4th run (purple).

 

A simple flip in the direction of the wires going into the reflectance sensor threw off our data by a factor of 1/2 until corrected.

(after orientation correction)

 

 

 

 

 

Post Lab session – Feb 26

Durning the post-lab session, we were able to replace the reflectance sensors on our AEV. Our results were recorded while using the same code from Lab 07. With our sensors being able to take accurate measurements of distance traveled, these were the results of the modified given AEV. Our modified AEV had a mass of 250.0 grams, while the original AEV had a mass of 267.2 grams.

Results:

Graph of the velocity of the AEV during the run:

 

 

 

 

 

The average speed during the run was 1.1768 m/s.

The maximum speed achieved was 2.3536 m/s

 

Graph of the distance traveled by the AEV during the run:

Now that the reflectance sensors are performing properly, we will be able to run our AEV with additional models of varying weight to compare their performances.

 

Lab – March 2

The beginning part of the lab was used to redo the Energy Analysis Exercise.  Because the reflectance sensors are now working with an acceptable margin of error, we were able to complete this with consistent results.  As reflected in our 2nd Progress Report, the team learned that a lower mass AEV consumes less power than a higher mass AEV.

 

Lab – March 5

This lab was used to catch up on A-R&D2.  For our second exercise, we completed Track Variance.  Because of time constraints, the team was able to complete just 2 tests per track.

 

Lab – March 7

This lab was used to work on and complete Performance Test 1.  The AEV was required to travel from the beginning mark, to the gate, and stop without triggering the second sensor.  Hard work from the team allowed us to complete the test with full points.  Because of

 

Lab – March 9

This lab was used to work on the Performance Test 2.

 

Lab – April 2

This lab was used to work on the Final Performance test, in an attempt to complete the project.

The team is actively using the following code in preparation for the Final Performance Test

  reverse(4);
  motorSpeed(4,50);
  goToRelativePosition(205); //218 in room 308 190 224
  motorSpeed(4,0);
  goFor(2.0);

  while(getVehiclePostion() < 296) //296 in room 308 293 in 224 {
    motorSpeed(4,60);
    goFor(.5);
    motorSpeed(4,0);
    goFor(0.9);
  }

    motorSpeed(4,0);
    goFor(7.0);
    motorSpeed(4,55);
    goToRelativePosition(145);
    motorSpeed(4,0);
    goFor(6.0);
    
  reverse(4);
  motorSpeed(4,100);
  goToRelativePosition(-95);
  motorSpeed(4,0);
  goFor(5.0);

  while (getVehiclePostion() > 355) {
    motorSpeed(4,100);
    goFor(.425);
    motorSpeed(4,0);
    goFor(.9);
  }

  motorSpeed(4,0);
  goFor(7.0);
  motorSpeed(4,100);
  goToRelativePosition(-33);
  goFor(10.0);

  while (getVehiclePostion() > 0) {
    motorSpeed(4,100);
    goFor(.425);
    motorSpeed(4,0);
    goFor(.9);
  }

 

Lab – April 4

The team worked during today’s lab to perfect the return run for the final performance test.  The AEV is consistently getting to the caboose and back to the gate each time.  As of now, we are just perfecting the final leg of the trip.  The AEV seems to be encountering some kind of friction along the track/on the wheels, as the distance of each coast is noticeably less than it was in previous tests.  Additionally, it was determined that the time between pulses on the return trip must be greater.  So as not to be redundant, the team will not post the code again until signifigant changes have been made.

 

Lab – April 9

On the first run today, the AEV overshot every mark that it was supposed to stop.  Additionally, the front wheel came off of the track on the return trip.  After some discussion, the team decided it was a result of the positioning of the battery.  We collaborated with other divisions within the company, and determined that it is important to verify the positioning of the battery is consistent to ensure a proper center of mass.  After fixing this issue, the team continued working on getting the AEV to return with the caboose accurately.