Testing Log #1: The testing done on the robot was done a day before performance checkpoint #1 and it made sure the code worked for the robot as well as making sure the robot completed all the necessary tasks of the checkpoint.
Link to PDF for Testing Log #1: Testing Log 1 – Sheet1
Testing Log #2: The testing done on the robot was done on the day of performance checkpoint #1 to make sure the robot was fully set for completing the first checkpoint successfully. Fewer runs were done than the first test.
Link to PDF for Testing Log #2: Testing Log 2 – Sheet1
Testing Log #3: This test was done a couple of days before performance checkpoint #2 to make sure the robot successfully went up the ramp consistently and was orientated in the same way to ensure the correct distances the robot needed to travel to get to the light. From the testing, the team came to the conclusion that the robot needed to align itself with the wall to make sure the correct distance is found.
Link to PDF for Testing Log #3: Testing Log 3 – Sheet1
Testing Log #4: This test was done before the performance checkpoint #2 to make sure the robot successfully read the light and displayed the color of the light on the proteus. From the testing, the team determined to find a more efficient way to read the light values as the initial method wasn’t consistent.
Link to PDF for Testing Log #4: Testing Log 4 – Sheet1
Testing Log #5: This test was done on the day of performance checkpoint #2 and was done to make sure the robot traveled the correct distance to hit the correct colored button on the kiosk. Doing last-minute testing allowed the team to find the right angle to rotate and the right distance to travel in order to perfectly hit the correct button on the kiosk.
Link to PDF for Testing Log #5: Testing Log 5 – Sheet1
Testing Log #6: This test was done on the day of the performance checkpoint #3 and was done to make sure the robot successfully drove to the fuel station, moved the proper fuel lever down for 5 seconds and back up. This test was also done to see how incorporating the RPS would help the robot move in the correct orientation. From the testing, the team learned that it had to be precise with the alignment of the robot to get the right RPS values for it to move the correct fuel lever.
Link to PDF for Testing Log #6: Testing Log 6 – Sheet1
Testing Log #7: This test was done four days before the performance checkpoint #4 and was done to make sure the robot could successfully drive up the ramp and align itself to the passport station as well as flipping the passport stamp. The robot could consistently go up the ramp, but sometimes misalign itself to the passport station causing inconsistencies in flipping the passport stamp.
Link to PDF for Testing Log #7: Testing Log 7 – Sheet1
Testing Log #8: This test was done two days before the performance checkpoint #4 and was done to make sure the robot could successfully complete the passport flip and return the lever to its initial position. The robot would successfully complete the passport stamp, but sometimes the lever wouldn’t be returned to its initial position due to how fast the mechanism would lift up the passport stamp. This causes consistency issues which led the team to think about how the robot would account for that speed issue if the passport lever doesn’t get returned to its initial position.
Link to PDF for Testing Log #8: Testing Log 8 – Sheet1
Testing Log #9: This test was done one day before performance checkpoint #4 and was done to make sure the robot could consistently complete the passport stamp flip and return the passport lever to its initial position. The robot would successfully flip the passport stamp, and after would drive back, move the mechanism to the left of the lever, drive forward, and finally move the lever back down. This proved to be very efficient as it worked every time.
Link to PDF for Testing Log #9: Testing Log 9 – Sheet1
Testing Log #10: This test was done two days before performance checkpoint #5 and was done to make sure the robot could successfully drop off the luggage in the upper baggage claim. Overall, the robot would do this task efficiently, though sometimes the luggage would fall off the mechanism when the robot went up the ramp depending on how securely it was placed on the mechanism at the start of the run.
Link to PDF for Testing Log #10: Testing Log 10 – Sheet1
Testing Log #11: This test was done four days before the performance test #1 and was done to make sure the robot could do all the tasks on the course. Overall, the robot did okay experiencing some alignment issues. Sometimes the robot would drop off the luggage in the bottom baggage claim. Additionally, due to RPS issues on courses B and D, the robot would miss the fuel lever or stop randomly because it wasn’t receiving accurate signals from the RPS. This had to be fixed by utilizing shaft encoding for the robot for the fuel lever task when the robot didn’t get good signals from the RPS.
Link to PDF for Testing Log #11: Testing Log 11 – Sheet1
Testing Log #12: This test was done two days before the performance test #1 and was done to make sure the robot could do all the tasks on the course. Overall, the robot did good but, there was one run where the robot missed the light which caused problems for the rest of the run. After the robot missed the light, alignment was off and all the other tasks remained incomplete. This causes the team to work more with the optimization of shaft encoding and the robot as it would drive to the light. After trial and error, the team found the right distance and time to go for the robot to read the light.
Link to PDF for Testing Log #12: Testing Log 12 – Sheet1
Testing Log #13: This test was done one day before the performance test #1 and was done to make sure the robot could do all the tasks on the course. On all runs, the robot did everything well, and team decided the robot was ready for the performance test the next day.
Link to PDF for Testing Log #13: Testing Log 13 – Sheet1