Week 5

During Lab 05, the team was able to examine the AEV designs based on its performance on the track. Using the screen and score decision charts, the team was able to select key features of the final AEV design, and prioritize what aspects of the AEV need to be agreed upon (cost, materials, weight, etc.) before their deadlines. During testing, the team ran a preliminary code created to travel a predetermined length of the track to the gate, pick up the R2D2, and return to the original position. The AEV ran smoothly on the track with the scenario code. When the code was activated, the AEV ran down the track without leaning to a particular side, even when making turns. It came to a smooth stop at the green gate and reversed immediately, returning to the starting point without any issue. The AEV stopped at the green gate approximately half a foot farther on the first run when compared to the second. Based on the performance of the sample AEV during the test, the team was able to make further progress on the screening and scoring tables.

Analyzing the screening and scoring sheets, the team favored all designs in terms of durability and maintenance mostly due to them being made by the same materials. Lauren’s design stood out for it’s projected balance and center-of-gravity which are key aspects of the AEV structure and performance. These ratings can be seen on the chart based on their numerical score from 1-5, 1 being poor and 5 being satisfactory. The limitations of the designs lied in blockage and environmental effect. Because each design has essentially the same parts, their configurations were hard to improve in terms of how the figures block other parts of the AEV.

The team was able to learn the importance of screening and scoring sheets to outline the future progress of the project. The tables made helped determine several final decisions on the AEV design, and also allowed the team to decide which aspects of the project were more important to finalize than others. The team is becoming more comfortable troubleshooting the code when setting up the Arduino, and altering the code to fit the criteria of the final code. In terms of track testing, the team was able to run the AEV on an Arduino code similar to that of the final project code, and got the opportunity to test with the R2D2 and monitor any changes necessary to the speed of the AEV to facilitate the extra weight.