Meeting Agenda:
Meeting Notes:
Everyone was present. The whole group worked on and observed Performance Test 4. Shyon, Meghan, and Dean worked on finishing the final report draft.
Future Actions:
Meeting Agenda:
Meeting Notes:
Everyone was present. Tom, Shyon and Dean worked on Performance 4 Test testing, and Dean did most of the testing log. Meghan worked on the final report draft and website, but observed a few tests.
Future Actions:
Purpose of Test: Complete Performance Test 3
Observers: Tom, Shyon, Dean, and Meghan
1st Run (3:23, Course B): Robot completed Performance Test 3 without failure.
2nd Run (3:24, Course B): Bump switch broke off and robot did not complete course.
Changed: Hot glued bump switch back on initial location.
3rd Run (3:30, Course G): Robot’s turns were inconsistent, axles kept getting caught on the course and turning robot at weird, incorrect angles.
Changed: Line up robot against wall more to try and be more consistent.
4th Run (3:35, Course H): Robot consistently inconsistent, drifting to the left when it approaches the garage.
Changed: Account for the leftward drifting and compensate for it.
5th Run (3:41, Course E): Still inconsistent when moving towards garage.
Changed: Tried to secure bump switches more.
6th Run (3:50, Course B): After a few inconsistent attempts, the robot failed some and succeeded during others. The team decided to do an Official Run™ and succeeded on the first attempt.
Meeting Agenda:
Meeting Notes:
Everyone was present for this meeting. The whole group worked towards successfully completing Performance Test 3. Shyon started the electrical documentation. Meghan worked on documentation and the website.
Future Actions:
Purpose of Test: Start completing performance test 3
Observers: Tom, Dean
1st Run (2:58, Course D): Programmed it to turn and pick up wrench, got stuck on the control panel when turning.
Changed: Ran proteus test code to get readings for optosensors
Purpose of Test: Complete performance test 2
Observers: Tom, Shyon, Dean, Meghan
1st Run (3:34, Course D): Ran the code multiple times, worked four times in a row but failed during the official run because didn’t show the color it read.
Changed: Made the robot display what color it read.
2nd Run (3:45, Course E): Succeeded three times in a row, but failed during the subsequent official run because it read the CdS value incorrectly due to driving past the light.
Changed: Got new CdS values by running the proteus test code
3rd Run (3:56, Course A): Failed once then succeeded twice, succeeded during the official run.
Meeting Agenda:
Meeting Notes:
Everyone was present. The team decided that they wanted to finish the performance test during the meeting, rather than spend the time on the exploration. Tom worked on completing Performance Test 2, then worked on the RPS exploration. Meghan worked on the website while and observed a few test runs, then helped Tom with the exploration. Dean soldered one of the shaft encoder wires back after it broke. He also compared the red and blue filters, deciding the the red filter was better and purchased it. Shyon observed test runs.
Future Actions:
Meeting Agenda:
Meeting Notes:
Tom, Dean, and Meghan were present. They all contributed to the coding and hardware issues that the robot faced and tried to get the robot ready for Performance Test 2 the following day.
Future Actions:
Meeting Agenda:
Meeting Notes:
Everyone was present. The team tested and coded the robot for Performance Test 2. The testing log can be found here.
Future Actions:
Purpose of Test: Have robot touch wrench and end on red button and complete performance test 2.
Observers: Meghan, Tom
1st Run (7:40, Course B): Lined up to the control panel, but robot didn’t hit the buttons it was supposed to.
2nd Run (7:41, Course B): Robot drove too far initially, running into the navigation panel.
Changed: The issue seemed to come from the hardware of the robot – Meghan and Tom hot glued the motors to the chassis.
3rd Run (7:47, Course F): Problem with driving too far was fixed and robot ran its course as it should have. Problem hitting blue button.
Changed: Back up robot more if the light is blue.
4th Run (7:54, Course B): Did not hit blue button, needs to more forward to hit buttons. Didn’t line up to wall with bump switches.
Changed: Nothing
5th Run (8:02, Course D): Did not hit the blue button, needs to move forward more to hit wrench.
Changed: Made it move more to hit the wrench, changed movement when hitting blue button.
6th Run (8:12, Course F): Inconsistency in lining up the CdS cell to read the light, causing it to incorrectly read the light some times, spent too long squaring up against the wall
Changed: try to hit button at the end, less time when squaring up against the wall.
7th Run (8:32, Course C): Got weird CdS readings, didn’t drive long enough to hit the button at the end (but came really close)
Changed: Ran proteus test code to get readings for CdS cell
8th Run (8:45, Course D): Everything worked except it kept missing the button color light
Changed: Correction factor on the turns
9th Run (8:58, Course F): Succeeded 3 out of the 5 times
Changed: Nothing