This lab consisted of three days where the team worked to adjust the Arduino code so that it would perform effectively and adapt to the two different tracks that it was required to run on. The first track was in the downstairs lab with the second track upstairs. Code was written for each lab as the AEV traveled differently between the two. With this in mind, the team wrote a test readiness review describing the objectives for the next week of testing with the different tasks divide between team members.
Throughout the lab, the team used trial and error methods to adjust the code as the only area that needed adjusting was the distance that the power should be supplied to the motors. Due to the fact that the two sensors are a very small distance apart, the slightest adjustment in the data caused a pretty significant difference in successfully reaching the gate and opening it. The team struggled to obtain consistent runs even when no changes were made to the code. This was partly due to the fact that the AEV would start at inconsistent positions, and the fact that there are notches on the track that the vehicle could become trapped in.
By the end of the lab, the team was able to create a code that allowed for a successfully functioning AEV that although inefficient, would perform the necessary functions correctly. With this imformation, the team created a memo documenting the results from the lab and the future steps that were going to be taken.