Author: ogle.81

Meeting 21

by at
March 4, 2018
2:00 pm
Hitchcock Hall Room 214

Meeting Agenda: 

  1. Get data logging from exploration 3 done
  2. Start working on Performance Test 3

Meeting Notes:

Only Tom and Dean were present. Tom started testing for Performance Test 3 using only the bump switch, as the line following kit was being re-soldered. With Dean, he cut the motor wires to get a stronger connection with the motor ports. Dean re-soldered the line following kit, added the appropriate resistors to it. He mounted a bump switch to the robot for testing while re-doing the line following kit.

Future Actions: 

  1. Prepare for board meeting
  2. Prepare for Performance Test 3
  3. Finish exploration
  4. Mid-semester feedback

2/28 Test

by at

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

by at
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 17

by at
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

by at

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