Autonomy: How Did You Guys Do It?

[davidthefat]

From the looks of it, a lot of teams did the whole "drive forward for x seconds/feet and score" method. Others used line trackers, some might have used cameras.

How did you guys do it?

[mwtidd]

Originally Posted by davidthefat

From the looks of it, a lot of teams did the whole "drive forward for x seconds/feet and score" method. Others used line trackers, some might have used cameras.

How did you guys do it?

I've got a range finder on the front of the robot. I drive until I'm about 3ft away from the wall. Then switch over to the camera, and adjust to center on the peg.

Arm is only on timers... Hoping to add encoders soon.

[MagiChau]

Used the E4P quadrature encoders provided in the KoP. We had the robot driven the correct distance for different modes, and I plugged them in for drive distance. Had some other encoder counts noted to do some calculations without trial and error. Arm height at our starting position angle needed to go through the peg was noted. Program ended up drive robot until encoder count got close to target. When robot stops moving and the code that moves the robot mechanisms to position returns a boolean of complete another stage is triggered that lowers the arm and shoots the tube out with the rollers.

Had to do some trial and error with drive speeds at competition so lift gets out before the robot goes up to the peg.

[davidthefat]

Originally Posted by lineskier

I've got a range finder on the front of the robot. I drive until I'm about 3ft away from the wall. Then switch over to the camera, and adjust to center on the peg.

Arm is only on timers... Hoping to add encoders soon.

Now, I was going to use the rangefinder to find weather we are on the fork or the stop. I had the worry that due to the metal backing, it would give a wrong reading.

[mwtidd]

Originally Posted by davidthefat

Now, I was going to use the rangefinder to find weather we are on the fork or the stop. I had the worry that due to the metal backing, it would give a wrong reading.

Actually they are awesome. Good to almost an inch. For me the drive was geared too high so we coasted a lot, but I came up with a fix to that (drop the strafe wheel and do an endo )

you need to do a bit of filtering, but not a big deal.

[CoachPoore]

Our autonomous uses the encoders on the SuperShifter transmissions. The software uses the encoder values to actively make the robot drive dead straight. We also know reliably how far the robot has driven from the encoders. Encoders on the arm allow reliable positioning of the arm. The claw motors let us adjust the attitude of the tube when we reach the peg and then eject it onto the target peg. We have six different programs, one for each peg height. At GSR, we only ever ran the two for the top pegs, but have the others just in case. We can also select a delay before we start, which proved very useful in eliminations at GSR when we were on an alliance with 175 and 176 which scored 3 ubertubes in many of our elimination matches. See http://www.youtube.com/user/FRCteam1.../3/drbPrGJlroI for a match (semi-final 2) where all 3 of our alliance and 2 of our opponents scored in autonomous. Our robot is the middle blue robot which does not move until after the 4s delay we selected.

Noel

[nighterfighter]

Encoders on our drive train, encoders on our elevator, camera tracking, gyro angle correction, and sonar sensor. Consistently scores the ubertop on the top peg every time.

[BigJ]

We decided that dead reckoning would be enough for this year given that the autonomous period is not very dynamic. Although our encoder code is done, we have had hardware problems and they are not on yet. Thankfully, our robot it pretty balanced and drives very straight. We didn't get an auto-mode in until yesterday in WI and it only scored once (in a somewhat humorous fashion), but will have one that should score pretty consistently week 4 in Midwest.

Given the hardware issues are fixed, the timing to approach will be changed to distance and a gyro would be added for turning around and getting ready. I don't think our robot functions act quickly enough to attempt a double-tube in 15 seconds.

[Jetweb]

We used the camera 100%. I have a feeling previous years vision targets have given the camera a bad name. The retro-reflective tape used this year is simply awesome to track and is the only target in my history that is not affected by the stage lighting used at the competitions. I hope that stuff is around for a long time to come.

[nighterfighter]

Originally Posted by Jetweb

The retro-reflective tape used this year is simply awesome to track and is the only target in my history that is not affected by the stage lighting used at the competitions. I hope that stuff is around for a long time to come.

Yup. Our autonomous works in normal lighting, pitch black, or intense lights. We love that stuff.

[torihoelscher]

Originally Posted by davidthefat

From the looks of it, a lot of teams did the whole "drive forward for x seconds/feet and score" method. Others used line trackers, some might have used cameras.

How did you guys do it?

We used Line Sensors, a sonar, a Gyro, and a backup way to make the auto move. Of course the Line Sensors gave us a hassle that we had to disable them and trust the sonar. it was great!!!

[Sean1038]

Our Auton code drives straight for x seconds using gyro angle correction; rotates our arm using x distance using an encoder value; rotates the tube pitch; rolls out the tube onto the peg; and backs up.

we're working on putting up two ubertubes.

[davidalln]

We're using nothing but line sensors, and its working excellently for us (backing up when it hits the horizontal piece of tape)!

[Jogo]

We're using a line track and ultrasonic range finder combo, with a gyro to keep us straight. In hindsight, the line track isn't really that useful.

[Owen Meaker]

Our team was going to have encoders on our drive wheels, but we decided they wouldn't be that helpful for the most part. As a result, our automous is drive forward x seconds, move arm down for Y seconds, and retreat. we are using a makeshift encoder for the lift, so we will be able to make it go to the right height. Whether or not this code works will be determined on Thursday.