In this lab the group debated together what the two different codes should consist of and initially concurred that one should use goFor (Time Based) and the other should use goToRelativePosition (Distance Based). The group decided this because a major portion of the grade for the project is based off of how efficient the AEV is during its run, and using a time based code would allow for the AEV to very efficiently glide to its destinations.
This led the team to use a distance based code that would go exactly how far it needed to go, and then reverse the motors to brake the AEV. The only problem with this run is that it was highly inconsistent and the team couldn’t figure out why. The reason for the inconsistency was only discovered when the team reached out to a TA and the TA determined that the source of error was in the sensors themselves, since they were not zip tied onto the AEV properly.
Takeaways:
Code – A new code will be necessary based on the fail trials from the lab.
Code – The new AEV code will be based on the Position function instead of time.
General – The battery could be a factor for the inconsistency on the labs, less energy in the battery will affect the efficiency of the AEV.
General – The testing labs are helping us improve the understanding AEV in general terms. As a team we have been able to troubleshoot by ourselves.
Design – The testing in the AEV have not been consistent, one of the causes could be the sensors or even the Arduino. To solve this we will change the parts too see the results.