Progress Report 3

Caden Pfendler

Andrew Reade

J.P. Dedeaux

Aaron Foster

 

Progress Report 3

 

Backward Looking Summary

Situation

Recently the group has used the lab times to test the two main codes that are used on the AEV. The group found that the creation and implementation of two codes was necessary due to the tracks on floors two and three having slight differences. Having two codes available allows the group to fine tune the AEV to each track without having to constantly edit and erase parts of a single program. The group has found however, that even with the use of two codes to adapt to the differences in the two tracks, the AEV is still inconsistent. These inconsistencies could be a product of the use of different batteries for each test run, along with slight imperfections in the weight distribution of the AEV and propellers. Over all, the group has been trying to make the AEV as consistent as possible, with assistance from the TA’s.

The group has faced a large set back in the past few labs, which has caused some tensions in the group, as well as problems with the AEV. On one of the test runs the AEV fell of the track and broke a propellor. Thankfully another group was able to lend the team a propellor. This fall may have caused some of the inconsistencies with distance and stopping. To overcome this obstacle the group has slightly redesigned the AEV and has changed the code slightly over multiple test runs to hopefully rid the AEV of its problems and pass the Progress Checks. The team has also had some problems being able to find meeting times and collaborating to finish some work. Hopefully with hard work and dedication the team will be able to overcome these problems in the future.

 

Results & Analysis

During the first performance test, the main problem that arose was getting the correct stopping position for the AEV. While getting to and passing the first sensor was easily achieved, stopping at before the second sensor proved to be difficult, as the AEV would coast after the stop and thus go past the second sensor, failing the test. To fix this, the code was changed and experimented with to ensure a complete stop of the AEV and eliminate coasting. After this change, the AEV was much more consistent, and was able to complete the first performance test with full marks.

The second performance test introduced the caboose, which when combined with the requirement of staying within the loading bay for five seconds, introduced some new problems. If struck too hard, the caboose would not attach to the AEV, and would instead bounce off. Also, the added weight of the caboose affected the power needed to move the AEV, forcing the team to experiment with different power levels in order to move the AEV out of the loading dock. However, the smaller incline of the track compared to the first incline allowed the team to utilize coasting, which saved power when compared to using the motors to go. Also, by slowing down the AEV to a slow coasting speed, the AEV would consistently be slow enough to attach to the caboose. After these adjustments, performance test two was successfully completed.

 

Forward Looking Summary

Upcoming Goals

The group has multiple upcoming  goals for the last stretch of the project. One of the goals is changing the AEV code to run more consistently. As of now the AEV will run the track perfectly the first run and then mess up on the following run. Another goal is to discuss roles for the oral presentation and get together to practice the presentation to make sure it will go smoothly on presentation day. One final goal for the group is to start working on the final CDR to make sure we have all the requirements in the document and so that we are not pressured for time and make little mistakes.

 

Upcoming schedule

Andrew Reade

-Lead programmer

-Create code that will allow the group to test within conditions of the final test runs

-Start creating a second code

Jean-Pierre DeDeaux

-Run through the past designs and consult group to meticulously pick best configuration    of current design

Caden Pfendler

-Help develop original code for the AEV runs

-Critically think ahead for overall AEV code that needs to be written for complete run

Aaron Foster

-Help and overall manage configuration of AEV as group sees fit

 

Although the AEV code is finished and we have ran through the entire track multiple times, it is now becoming inconsistent. It had the tendency of not stopping before reaching the gate on the way to the loading zone. To fix this the group just added more braking power and reduced the amount of time that the propellers would run on the way to the gate. While this fixed that particular problem, the AEV would then not reach the gate after connecting with the caboose. The group has yet to fix this problem so the group will work together on figuring out the best way to resolve this situation. Whether that be changing the design of the AEV, the code, or simply changing where the caboose comes in contact with the AEV.

Appendix

Arduino Code

Propeller Configuration Test
File name: Propeller_Config_Test.ino
//Runs both motors and 25% power for 2.5 seconds, then brakes, then does the reverse.
motorSpeed(4,35);
goFor(5);
brake(4);
reverse(4);
motorSpeed(4,35);
goFor(5);

brake(4);
reverse(4);

Motor Configuration Test – Forward
File name: Motor_Config_Test_Forward.ino
//Runs both motors and 25% power for 2.5 seconds, then brakes.
motorSpeed(4,35);
goFor(5);
brake(4);

 

Motor Configuration Test – Backward

File name: Motor_Config_Test_Backward.ino
//Reverses then runs both motors and 25% power for 2.5 seconds, then brakes.
reverse(2);
motorSpeed(4,35);
goFor(5);
brake(4);

 

Meeting Notes

 

Meeting #8

Date: 3/20/2018

Time: 12:45 – 2:05 in lab

Members Present: All

Topics Discussed:

  • Worked on AEV code and completed performance test 1.
  • Discuss plan performance test 2.

 

Meeting #9

Date: 3/24/2018

Time: 7:00 – 8:15 in 18th Avenue Library

Members Present: All

Topics Discussed:

  • Worked on CDR Draft assignment
  • Discuss the progress of performance test 2