2/28 Test

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 19

February 28, 2018
3:00 pm
Hitchcock Hall Room 214

Meeting Agenda: 

  1. Complete Performance Test 2, start working on Performance Test 3
  2. Complete RPS exploration

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:

  1. Prepare for Performance Test 3
  2. Finish exploration
  3. Read and provide feedback for other teams’ reports

Meeting 18

February 27, 2018
1:30 pm
Hitchcock Hall Room 214

Meeting Agenda:

  1. Finish coding/testing Performance Test 2

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:

  1. Complete Performance Test 2
  2. Learn about RPS

Meeting 17

February 26, 2018
7:30 pm
Hitchcock Hall Room 214

Meeting Agenda: 

  1. Finish coding robot to finish Performance Test 2

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:

  1. Finish robot for performance test

2/26 Test 2

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

2/26 Test

Purpose of Test: Wanted to start completing performance test 2

Observers: Dean, Shyon, Tom

1st Run (4:29, Course F): The robot had problems with turning and going the right length

Changed: Changed the lengths (after measurement) and turning amount

2nd Run (4:32, Course D): Robot didn’t go far enough forward, or far enough after it turned

Changed: Made the robot go farther both when it went forward and after it turned

3rd Run (4:35, Course A): Robot didn’t go far enough forward, went too far after it turned

Changed: Made the robot go farther during the first leg and shorter during the second leg

4th Run (4:40, Course C): Got pretty close to the light, but kept pushing the red button

Changed: Ran proteus test code to get light readings.

5th Run (4:50, Course F): Ran proteus test code

Changed: Got readings for the light, and updated our code accordingly

6th Run (4:56, Course F): Once again, always acted as if the light was red

Changed: Debugged code and found that the action for red was pasted into the else statement that was entered if the light was read as blue, changed the code accordingly.

7th Run (4:59, Course G):  Worked properly, except it had trouble hitting the blue button, and was misaligned when it started driving to the wrench

Changed: Made it go backwards less before turning to go to the wrench, adjusted motion when blue light is on.

8th Run (5:08, Course H): Worked well for red light, for blue light, it wouldn’t back up enough

Meeting 16

February 26, 2018
3:00 pm
Hitchcock Hall Room 214

Meeting Agenda: 

  1. Build and code robot to complete Performance Test 2
  2. Board Meeting

Meeting Notes:

Everyone was present for this meeting. Tom worked on the code for Performance Test 2. Shyon collaborated with Tom and observed testing. Tom and Dean mounted the shaft encoder properly, so the robot could drive straight. He then mounted the CdS cell and bump switches on. Meghan prepared for and went to the coding board meeting and brought back feedback to the team. She then helped with preparation for Performance Test 2. The testing log can be found here.

Future Actions:

  1. Meet up later to finish coding the robot for Performance Test 2