March’s Meetings


Meeting #9

Date: March 7

Time: 12:45PM – 2:05PM

Members Present: All

Objective:

  • Prepare to test the prototype AEV build

To-do:

  • All members will contribute to the preparation of the AEV and begin testing the reflectance sensors, motors, types of propellers, etc.

Decisions:

  • Over spring break, the AEV will be 3D printed for the base and shell, the team will reuse the arm from the secondary AEV prototype.
  • The division decided that reflectance sensors are not really a necessity in the experiments, so it was removed.

Future tasks:

  •  Prepare the AEV over spring break.
  • Run tests for propeller and motor configurations to get the timings down for moving the AEV from the start point to the gate, wait for 7s, then continue. This is the performance test 1.

Meeting #10

Date: March 21

Time: 12:45PM – 2:05PM

Members Present: All

Objective:

  • Complete Performance Test 1

To-do:

  • All members will contribute to the testing and data collection for the newly built AEV and complete the performance test for the day.

Decisions:

  • Each member has a specific task to get the work done. Zachary uploads code, Avi-Blake-Esar conduct the experiments on the track, Blake & Esar are support in case if the AEV malfunctions, Avi builds & alters AEV and code with Zachary, Blake collects data from the AEV.
  • After removing the reflectance sensor wiring, the team depended on power and timings for the AEV to function accurately. The team successfully completed the first performance test with ease.

Future Work:

  •  The team will prepare for performance test 2, with the same roles but also contribute to the code used in test1.

Meeting #11

Date: March 28

Time: 12:45PM – 2:05PM

Members Present: All

Objective:

  • Complete Performance test 2 for the day

To-do:

  • Contribute to the code last used in test1 for the AEV to conduct further actions on the track.
  • Collect all the data useful as well as completing the performance test2 for the day.

Decisions:

  • The team decided that they will still use power changes and time accuracy to continue towards the Cargo load station, gracefully connecting with the cargo, then pulling it out of the loading zone with enough power till it reaches the gate. This is the performance 2 test objectives.
  • The team successfully completed performance test 2, but also conducted experiments on batteries, as they were a significant problem for the day. The team overlooked the relationship between the usage of battery by trials in relation to the power outputted from the battery, throwing most of the power levels of the motor off than expected.

Future tasks:

  •  Prepare for the Committee Meeting 2 and discuss potential fixes for the battery issue.

Meeting #12

Date: March 30

Time: 12:45PM – 2:05PM

Members Present: All

Objective:

  • Committee Meeting 2

To-do:

  • Discuss reports as well as potential fixes for the battery variances found in fully charged batteries to used batteries, and variances between experiments

Decisions:

  • Each member discussed with the head department about the division’s progress.

Reflections and future work:

  •  The division should start written tasks earlier, however, the physical experimentations are right on schedule, good work.