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

Meeting 16

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

2/21 Test

by at

Purpose of Test: Wanted the robot to complete Performance Test 1.

Observers: Tom, Dean, Shyon, Meghan

1st Run (3:30, Course A): The robot successfully completed Performance Test 1 but run was unofficial.

Changed: Changed nothing.

2nd Run (3:33, Course A): Bump switches failed to engage when the robot hit buttons.

Changed: Made a conditional statement that if the robot failed to engage the bump switches after three seconds, then the robot would just continue with the next task.

3rd Run (3:45, Course F): Official run, bump switches failed to engage when robot fit buttons.

Changed: Realized an “or” in conditional statement should have been an “and”, and we changed this.

4th Run (3:56, Course B): Unofficial run, the robot successfully completed Performance Test 1.

Changed: No changes

5th Run (4:02, Course B): Official Run, robot successfully completed Performance Test I.

https://github.com/ballas13/Robot-Team/edit/master/main.cpp

2/20 Test

by at

Purpose of Test: Want to observe robot doing completing performance test 1.

Observers: Tom, Dean

1st Run (2:20, Course A): Observed the robot navigating up the ramp but failing to hit the buttons.

Changed: Added two 45 degree turns to help shift the robot towards the buttons and added moves for the robot to back up, turn back left, and run into the wall.

2nd Run (2:25, Course E): Observed the robot successfully doing all tasks shown above.

Changed: Added a forward movement across the course, a back right turn, and a forward movement toward the switch.

3rd Run (2:31, Course G): Observed the robot successfully doing all tasks shown above.

Changed: Added a turn for the robot to face the wall, added a forward until it hit the wall, and then go forward to hit the switch.

4th Run (2:38, Course D): The robot was successful until it failed to make a large enough turn towards the switch.

Changed: Increased the turn before the robot goes towards the switch.

5th Run (2:45, Course A): The robot was successful in completing all tasks for Performance Test 1.

Changed: No changes

6th Run (2:48, Course A): The robot was again successful.

Changed: No changes

7th Run (2:52, Course A): the robot was again successful.

2/19 Test

by at

Purpose of Test: Want to observe robot go straight, make a left turn, go forward again, make another left turn, go forward up the ramp, go backward down the ramp.

Observers: Tom, Dean, Shyon

1st Run (3:54, Course A): Observed the robot was not turning a full 90 degrees on its turns.

Changed: Changed this code to increase the amount of time the robot turned.

2nd Run (4:02, Course B): Observed the robot successfully completed its mission.

Changed: Did not change anything and stopped working.

https://github.com/ballas13/Robot-Team/blob/master/main.cpp

Meeting 14

by at
February 21, 2018
3:00 pm
Hitchcock Hall Room 214

Meeting Agenda:

  1. Performance Test 1
  2. Pseudocode
  3. Order more parts

Meeting Notes:

Everyone was present. Tom helped team accomplish Performance Test 1, reworked the SolidWorks model to include shaft encoders, ordered screws, shaft encoders, and axles, and started to work on pseudocode assignment as well. Shyon sanded the skid along with Dean and updated the website meeting notes. Dean sanded the skid and also found the right screws with Tom for the skid. Meghan helped with Performance Test 1 as well. She worked on the website, made templates, began testing logs, updated meeting notes and picked up items from the store. The robot was successful on the performance test on its second attempt.

Future Actions:

  1. Implement shaft encoding on robot
  2. Fix chassis issues

Meeting 13

by at
February 20, 2018
3:45 pm
Hitchcock Hall Room 214

Meeting Agenda:

  1. Finalize robot for Performance Test 1
  2. Attach CdS cell
  3. Finish code

Meeting Notes:

Tom, Dean, and Meghan were present. Tom helped finish code for Performance Test 1, and attached bump switches to the robot as well. Dean mounted the CdS cell while Meghan helped finish coding for the performance test. The testing log can be found here.

Future Actions: 

  1. Perform Performance Test 1 early
  2. Start on pseudocode