Meeting 7

Date: March 21, 2018

 

Location: Hitchcock Hall 308

 

Purpose: Fix our Arduino and its Code to prepare for Performance Test 1.

 

Team Members Present:

– Nina Moore

– Jacob Ryan

– Ravvin DeArmond

– Mason France

 

During the meeting:

-Discussed which version of the AEV design we preferred and made our first code to use for Performance Test 1.

  • Team decided among each other which AEV design was best.
  • When building the AEV to be used for the experiments during the meeting, Mason accidentally fried both of the motor chips on the Arduino. The TAs were notified and a new arduino was given. Mason has agreed to pay for all the damages done to the Arduino.
  • Jacob was tasked to begin the start of the Arduino.
  • Nina and Ravvin were recording all the changes and results of the codes we ran prior to our finalized code.
  • Mason and Nina both created the codes for the Arduino.
  • Mason was tasked to make sure that the AEV did not crash into the gate on the rail.
  • Ravvin mentioned the possibility of needing to record our voltages in the battery before we begin testing so we can adjust our codes whenever possible.
  • Nina brought up the idea of using a power break rather than coasting for more accurate stops.
  • Due to setbacks, the group must now Prepare for Performance Test 1 to be completed on Friday during the next lab day in preparation for Performance Test 2.

 

Tasks to complete before the next meeting:

– Nina:

  • Come up with ideas for two codes to prepare for Performance Test 2.
  • Update the team’s website.

– Jacob:

  • Prepare for meeting.
  • Research where the team should start there AEV on the track in order for a safer stop.
  • Update the team’s website.

– Ravvin:

  • Record changes for to the codes to be used or looked back on for future use.
  • Update the team’s website.

-Mason:

  • Come up with ideas to prepare for Performance Test 2.
  • Update the team’s website.

 

Plans for next meeting:

  • Run Performance Test 1
  • Figure out why the AEV has some variance in stopping either to far or too close to the gate’s sensors.
  • Begin preparation for Performance Test 2.