Progress Report Lab 09

Backwards looking summary:

Lab 09A through 09C covered Performance Test 2, which focused on our two separate codes for the AEV test run. The codes mainly differed by their energy usage and ability to handle variations in the run. Our testing began with Code 1, which was less energy-intensive but fragile, in the sense that it could not handle small changes in battery power or distance. With Code 1, we were able to accomplish and film a complete run of the entire course. With this proof-of-concept, the team shifted focus to Code 2. Code 2 was Code 1’s reverse, a robust code that could weather the changes, but would carelessly burn through battery power. Code 2 is close to consistently finishing the entire track, and has been reliably reaching the second gate (with the caboose attached). The major takeaway for testing this Code is that the more powerful propellers raise the stakes for track testing. The new code moves the AEV much faster, so when the AEV overshoots a gate, it can jump the track or blow right past the gate. Appendix A is a table showing the breakdown of track distances and wait times.

Moving forward, we will continue to vary the code to determine the correct formula of efficiency in our AEV. To accomplish this, we need a desired baseline of code that we just spent the past performance test finalizing. From there we will make small adjustments to the code, and maybe even to the design. No dramatic changes to the design will be made, however things like balance as well as weight adjustments will be made in order to make the AEV more energy-efficient. Some ideas for making the AEV more efficient include, shorter reverse brakes, torque balancing, reduction of base weight, and push versus pull motor configuration. We have begun some of this process already, as we are ahead of schedule and deciding which code we wanted. Because we chose a more robust code we are able to limit misreads in sensors. More importantly, moving forward variations in code to reduce energy will have less of an effect on how the AEV operates the MCR.

This upcoming week we plan to make these changes on the fly with the design of the AEV as well as the code, but priority number one is to make sure that our AEV is running perfectly by the end of the week. Major step back at the stage will cause major destruction to the end goal. Goals for this week include, AEV runs at top efficiency with the robust code, AEV should be 100% ready to go by the end of performance test 3, lastly, ensure that all documents to be submitted are being worked on and project is moving towards finalization. The weekly schedule consists of finishing the last four on the gannt chart below. By the end, 3B well will have to analysis complete, 3C braking and acceleration will be finalized as well as time completely minimized. With the completion of those three things our AEV should be all tuned up. Finally, continue to work on designated parts of the PDR.