Intresting Autonomous

[TVan]

Originally Posted by GODUX123

We started it. They saw ours and copied it. They even told me. It was part of the reason that we won the regional, it worked amazing! No-one scored on us the entire district when we were in autonomous mode!

we did not make this autonomous up and were scored on in autonomus,
and we were on the winning alliance. Selected by 2645 (a Great Team, thank you ) and played with 247 (The Bears rock )

The most intresting or gut wrenching was our robot taking off at a slow speed than insted of one side forward and one backward both forward full speed into the driver station on the other side of the field. who ever thought up the bumpers on the driver station wall thank you. ( did you flash it )

Tim

[Lowfategg]

We don't like spinning automode since our human plays say its easier to score on than some other modes. It does look awesome.

[GGCO]

My team, 904, went with the track the trailer and score in it method. It works pretty well. It's still a little buggy, but we can fix that easily.

I did notice at Traverse City team 2645 also was tracking and shooting. I was wondering if one of their programmers could fill the rest of us in on what their secret was?!? From what I could tell the robot drove towards the target, found it, backed up when the image percent was too large, and then lobbed a cell into the trailer. Pretty impressive.

Anyone use an ultrasonic sensor for their auto mode?

[BigWhiteYeti]

They really need to give bonus points for robot scoring in auton. That is really impressive.

[GGCO]

Originally Posted by BigWhiteYeti

They really need to give bonus points for robot scoring in auton. That is really impressive.

Yeah, I totally agree. If your robot can score in autonomous every match (which I haven't seen) then it gives you an advantage, but only if you don't get a lot of balls in your trailer.

[thefro526]

I think 612 has a strong auto. They don't score in Autonomous because they chose not to but they can line themselves up almost perfectly with a trailer about 90% of the time.

[bduddy]

Originally Posted by thefro526

I think 612 has a strong auto. They don't score in Autonomous because they chose not to but they can line themselves up almost perfectly with a trailer about 90% of the time.

What do you mean "chose not to"? Why?

[robodude03]

Originally Posted by bduddy

What do you mean "chose not to"? Why?

Probably because you have a greater chance of scoring during human control. The fact that there are no bonus points in autonomous mode really makes scoring in autonomous less desirable. Instead I would imagine the team sets themselves up to dump as soon as the mode switches. Our robot has some stringent requirements to dump into the trailer for autonomous mode. Therefore I doubt we will be scoring during auto mode unless those conditions are met.

[lynca]

Please post a link to a video you if you find an Interesting Autonomous

My favorite autonomous as of now is the 121/175 alliance pinning of their opponent.

http://www.thebluealliance.net/tbatv...?matchid=11858

Does anyone see any strategy problems with the 121/175 autonomous ?

I think most of 121's autonomous modes were excellent

[eschanz]

Does anyone have a picture of 1254 if u do please post it. thanx

[nahstobor]

Originally Posted by bduddy

What do you mean "chose not to"? Why?

At the New Jersey regional we chose not to score during Autonomous for many reasons. First off we felt that because our Autonomous mode was not fully ready for scoring it was not worth the risk. We attempted scoring earlier but was only able to score 4 balls. Those first 7 moon rocks are very important so we choose only to line up with a trailer so when we started teleoperted we were ready to go. This gave us a greater chance of scoring those first 7. Now at the NASA/VCU Regional we will go back to trying to score in Autonomous because I think in Atlanta this will be a very important ability.

Here are some good videos of our robot tracking during the playoffs (all this video was provided from our "bot cam" that was mounted next to the actual camera)

(Quarterfinal Match 1, locked on team 136)

(Semifinal Match 1, locked on team 708)

(Semifinal Match 2, locked on team 708)

(Semifinal Match 3, locked on team 1218) (My favorite)

[Enigma's puzzle]

that bot cam is awesome, i didnt know we were allowed to do that

[nahstobor]

Originally Posted by Enigma's puzzle

that bot cam is awesome, i didnt know we were allowed to do that

From my understanding in order to do so you must have permission from the Lead Inspector at the event, which at the New Jersey regional we did.

[FRC4ME]

Our autonomous runs to our alliance's refueling station and hides. It is very difficult for human player to score on a robot that is over there.

We decided not to go forward and spin since that's what everyone else does, giving us a 50% chance of being pinned to the wall rather than getting to center.

[Hazmatt]

Originally Posted by GGCO

My team, 904, went with the track the trailer and score in it method. It works pretty well. It's still a little buggy, but we can fix that easily.

I did notice at Traverse City team 2645 also was tracking and shooting. I was wondering if one of their programmers could fill the rest of us in on what their secret was?!? From what I could tell the robot drove towards the target, found it, backed up when the image percent was too large, and then lobbed a cell into the trailer. Pretty impressive.

Anyone use an ultrasonic sensor for their auto mode?

We built our code from the "2 color servo tracking demo". Basically we looked at the part in the code that spit out the servo angles for the x-axis servo on the gimbal. These were an angle value and so consequently ranged from 0-170. We called angles 0-85 (85 = 170 / 2) "left turn". We made a function that linearly increased power to the drive wheels as the angle got closer to 0. angles 85-170 were considered "right turn" and were scaled the same way. additionally, we told the robot not to move if the camera wasn't currently tracking a target. After all of this, our robot would turn but not drive towards a target. Next we found the part in the code that spit out the "area %" of the target on the screen. We created a function that would add an amount to the drive speed of both motors (so that the motors would drive forward) that increased linearly based on the distance (area %) that the camera saw. Additionally, we added a switch on our robot to switch between the colors that the camera is currently tracking (green/pink or pink/green).

If you do this type of programming in Labview, I suggest that every time you make a multiplier in a function you first make a knob on the front panel so that you can "tweak" the outcome of the function. Then when you are done go to the block diagram, right click on the knob or dial and select "change to constant". Doing this will ensure that the numbers you have chosen in your functions always stay the same. If you leave them as a dial they will reset themselves.

We are currently working on getting the robot to move out on to the field 3 seconds initially, and then start tracking. Ideally we would have had a "field position switch" which would allow us 3 different autonomous modes, but unfortunately a firmware update disabled this ability for us. Also unfortunate was that we already had the control panel made with the switch mounted.

I wrote a ton, but I hope that lets you in on the "secret"