Meeting 14

Team I Meeting 14

Meeting 14

Date: 3/28/2018
Time: 12:45
Location: Hitchcock 224
Attendance: All members present

Topics Discussed:

  • Committee Meeting 2
  • Effectivity of Code for Performance Test 2

Objectives:

  • Clean Code for Performance Test 2
  • Complete Performance Test 2
  • Continue work on Progress Report 3

To Do:

  • Performance Test 2
  • Progress Report 3
  • Committee Meeting 2

Meeting 13

Team I Meeting 13

Meeting 13

Date: 3/27/2018
Time: 12:45
Location: Hitchcock 224
Attendance: All members present

Topics Discussed:

  • Our efficiency on working on the CDR Draft
  • Upcoming Deliverables

Objectives:

  • Clean and test a code to complete performance test 2
  • Begin Progress Report 3

To Do:

  • Progress Report 3
  • Performance test 2

Meeting 12

Team I Meeting 12

Meeting 12

Date: 3/23/2018
Time: 12:45
Location: Hitchcock 224
Attendance: All members present

Topics Discussed:

  • Using Propellers to break into the caboose
  • Progress toward CDR Draft Completion

Objectives:

  • Begin Working To create a code to complete performance test 2
  • Continue work on CDR Draft

To Do:

  • CDR Draft
  • Performance test 2

Meeting 10

Team I Meeting 10

Meeting 10

Date: 3/20/2018
Time: 12:45
Location: Hitchcock 224
Attendance: All members present

Topics Discussed:

  • Possible Changes in Code of Performance Tests
  • Progress on CDR Draft

Objectives:

  • Repeatedly Test Code to Work out flaws and build consistency
  • Continue to Work on CDR Draft

To Do:

  • Performance Test 1
  • CDR Draft

Meeting 9

Team I Meeting 9

Meeting 9

Date: 3/7/2018
Time: 12:45
Location: Hitchcock 224
Attendance: All members present

Topics Discussed:

  • Code of Performance Tests
  • Usage of distance or time-based code for the AEV

Objectives:

  • Begin Working To create a code to complete performance test 1
  • Begin to Work on CDR Draft

To Do:

  • Performance Test 1

Meeting 8

Team I Meeting 8

Meeting 8

Date: 2/28/2018
Time: 12:45
Location: Hitchcock 224
Attendance: All members present

Topics Discussed:

  • Progress Report 3
  • Advanced R&D Oral Presentations
  • Possible design changes

Objectives:

  • Make the Oral Presentation
  • Start website update 3

To Do:

  • Finish Progress Report 3
  • Begin Thinking of Strategies for Performance Tests

Final Performance Test

The final test was done with the same design as the previous tests.

The first final test that Group I ran didn’t go as planned.  The AEV made it through the first gate smoothly, picked up the cargo, waited, and then left the loading zone with ease.  Once the AEV obtained the cargo, the issues arose.  The AEV would’ve overshot the next gate, but it was stopped short to assure that the run could be completed.  The AEV proceeded through the gate, but again for unknown reasons had to be touched again at the starting zone so that it didn’t recoil out of the zone.  The reasons for these errors are unknown, but it was assumed to be something due to the battery or motors.  The final brake didn’t stop the AEV completely, but prior to that it had never failed to stop the AEV. This test was done in room 224, which was the room that Group I had the most trouble with consistency in.  The AEV used a total of 227 joules of energy and took approximately 53 seconds.  This data was a little worse than expected as it pushed the group over the budget.

When Group I finished for that day, they intended to fix these issues for the last day of testing.  To the surprise of the group, the AEV had issues on the final run in room 308.  The errors that presented themselves in room 308 had never happened before and came to the surprise of the group.  The AEV made it smoothly through the first gate and proceeded perfectly to the cargo and stopped.  The AEV left the loading zone and proceeded up the ramp, but the brake never kicked in, which was another unknown error, so the AEV had to be stopped using one of the groups’ touches.  After it was moved into the gate sensor, the group assumed the run would proceed smoothly as it has never failed to stop in the starting zone with that code in room 308.  Again, to the surprise of the group the AEV fell short of the starting zone.  The fact that the AEV ran smoothly prior to that final test and then failed to finish the performance test was again due to random chance.  This test used 228 joules of energy and took approximately 51 seconds.  This small change in energy and time between runs doesn’t have much effect on the overall budget, which means both runs had similar results.  The timings that are present in the below graph, figure 9, are inaccurate, the correct times were taken using a stopwatch during the runs.

Performance Test 2

The same design used in performance test 1 was used in performance test 2.

 

Performance test went much smoother than performance test 1.  The AEV succeeded perfectly on the first try for the second performance test.  It stopped at the gate proceeded through, picked up the caboose and then proceeded out of the loading zone.

Performance Test 1

This was the design used for the first performance test.

 

This first performance test did not go as planned because the AEV failed to reach the gate on the first try and then for some random error it failed to reach it again on the second try.  Upon analysis of the issue it was discovered that one of the motors was disconnected and therefore was the reason for the AEV falling short.  The AEV then proceeded through the cat after the error was established and corrected.