The purpose for the labs this week is to refine both vehicle and code to create the most consistent, energy efficient design that completes the task of retrieving R2D2. The team will then compare these two codes by determining which code is more consistent and energy efficient. The data analysis tool will help in determining the power usage of each code, while physical observation of the actual runs can determine the consistency of the code and the consistency of the vehicle’s balance.
These lab exercises focused on minimizing energy used to complete each run. The strategy used for testing consisted of running the AEV and using observations and data from the run to alter the code to be more efficient. No changes were made to the design, but after the three labs, the team concluded that installing a servo motor brake would be the most energy efficient choice remaining to the team. The brake will also increase consistency among runs. The code developed from these three labs is efficient, and consistent as is, but installing the brake will improve the AEV in every category. The purpose of these labs were to reduce the amount of energy used. The team’s conclusion of installing a servo brake fulfills the purpose of these lab exercises.
Below will a graph that compares the power to the time of one of the successful runs during this lab period. Under the link, there will be an Arudino code that corresponds to the graph. The total energy (J) used during this lab was approximately 250.
Links:
- Agenda
- Meeting Minutes
- Arduino Code
Previous Lab – Lab 9: Performance Test 2 (Code)
Next Lab – Lab 11: Performance Test 4 (Final Testing)