[FTC]: 121 Autonomous

[BradMello]

Originally Posted by Overyourhead

I saw this Auto in the finals at the RI regional. It was pretty sick. It was awesome teaming up with you guys again!

Yeah, we had to try and run it at least once hahah

nice winning with you guys, great finals round

[Nitro-Guy]

Nice job... looking forward to seeing you folks in Atlanta.

-Jonathan

[basicxman]

Crazy good, I'd recommend hooking up some ultrasonics for avoidance techniques, while avoiding a robot, keep track of the encoders, and then do the reverse movements

[ttldomination]

Hey..Andy..No giving people my ideas. .

[chopperdudes]

Originally Posted by ttldomination

Hey..Andy..No giving people my ideas. .

rofl yeah!! but yeh rly props to whoever can do what andy suggested

[ttldomination]

Well, it's not that hard to implement. Let's say you're following a code, and something's not right. For example, if you're using a compass sensor, your sensor indicates you're not facing in the right direction or something, at that moment, your robot start counting encoder counts and angle measurements from the initial "alarm". After you no longer have movement or your encoders stop moving, then you simply perform the actions you did in reverse.

[chopperdudes]

Originally Posted by ttldomination

Well, it's not that hard to implement. Let's say you're following a code, and something's not right. For example, if you're using a compass sensor, your sensor indicates you're not facing in the right direction or something, at that moment, your robot start counting encoder counts and angle measurements from the initial "alarm". After you no longer have movement or your encoders stop moving, then you simply perform the actions you did in reverse.

yes THAT would not be hard. but actually avoiding robots... can be quite hard... especially in this small space

[dooey100]

Originally Posted by chopperdudes

yes THAT would not be hard. but actually avoiding robots... can be quite hard... especially in this small space

I was planning to do this if I got the time, and my plan was to have specific likely interference points. Then it would just go to something like:

if (interferenceDetected) {
//do something
} else {
//do something else
}

[PhilBot]

Originally Posted by dooey100

I
if (interferenceDetected) {
//do something
} else {
//do something else
}

Now "all" you need to do is figure out what code to include for:

"//do something else"

Were you thinking "Different Goal" or "Different approach to the Same Goal"?

[dooey100]

Originally Posted by PhilBot

Now "all" you need to do is figure out what code to include for:

"//do something else"

Were you thinking "Different Goal" or "Different approach to the Same Goal"?

If we were interfered with as we attempted to put pucks in the goal, we would have tried to go around them. If we were interfered with as we attempted to collect the pucks, we would have dumped another of our opponents racks.

[craig_yates]

From our experiences, the ultrasonic sensors aren't reliable enough for accurate use in robot-avoidance procedures.

[595294001]

The other problem is that form the videos the code seems to take 29-ish seconds, leaving no time to retrace your footsteps even if you could.