2011:Autonomous Light Tracking Page - Revision history

Heydowns: Autonomous Light Tracking Page moved to 2011:Autonomous Light Tracking Page

2012-01-06T17:42:50Z

Autonomous Light Tracking Page moved to 2011:Autonomous Light Tracking Page

← Older revision	Revision as of 10:42, 6 January 2012
(No difference)

Programming: editing

2011-01-30T22:54:14Z

editing

← Older revision		Revision as of 15:54, 30 January 2011
Line 3:		Line 3:
	The biggest problem is there are only 12 inches to the peg from the end of the fork line. We can't go that far or else we won't be appropriatly lined up with the pegs. We also have to change this for the diffrent peg heights as well. (if the arm is more vertical, we have to drive foward further.)		The biggest problem is there are only 12 inches to the peg from the end of the fork line. We can't go that far or else we won't be appropriatly lined up with the pegs. We also have to change this for the diffrent peg heights as well. (if the arm is more vertical, we have to drive foward further.)

	A coding where the left / right sensor is dominante it might help (we can drive foward and let physics put the tube on, we do not need to be perpedicular to the peg wall to put the pegs on. Angled placement is possible.) by increasing the angle of the tube so the hole is more correctly lined up with the		A coding where the left / right sensor is dominante it might help (we can drive foward and let physics put the tube on, we do not need to be perpedicular to the peg wall to put the pegs on. Angled placement is possible.) by increasing the angle of the tube so the hole is more correctly lined up with the pegs. (so we can at least put it on.)<br>



	~~Also there have to be diffrent speeds~~ (pending on the position of the robot in relation to the line). The robot should be fast for 75% of the line before the fork, then go slowly while it trys to pick up the fork. then it should turn to the fork and go a moderate enough speed so it ~~can score the ubertube~~. ~~Of course we don't want to go slow the entire time. We only have 15 seconds.~~


			<br>

			Also there have to be diffrent speeds (pending on the position of the robot in relation to the line). The robot should be fast for 75% of the line before the fork, then go slowly while it trys to pick up the fork. then it should turn to the fork and go a moderate enough speed so it can score the ubertube. Of course we don't want to go slow the entire time. We only have 15 seconds.

			<br>

			<br>

			<br>

Programming: New page for autonomous light tracking content

2011-01-30T21:54:01Z

New page for autonomous light tracking content

New page

Currently Peter has the robot programmed to drive foward while following the line and stop once all three sensors can no longer see the tape. On the center line we need to figure out what to do after turning from the fork. 

The biggest problem is there are only 12 inches to the peg from the end of the fork line. We can't go that far or else we won't be appropriatly lined up with the pegs. We also have to change this for the diffrent peg heights as well. (if the arm is more vertical, we have to drive foward further.)

A coding where the left / right sensor is dominante it might help (we can drive foward and let physics put the tube on, we do not need to be perpedicular to the peg wall to put the pegs on. Angled placement is possible.) by increasing the angle of the tube so the hole is more correctly lined up with the 

Also there have to be diffrent speeds (pending on the position of the robot in relation to the line). The robot should be fast for 75% of the line before the fork, then go slowly while it trys to pick up the fork. then it should turn to the fork and go a moderate enough speed so it can score the ubertube. Of course we don't want to go slow the entire time. We only have 15 seconds.

 