Oh god did our robot just run into the driver station auto club

[IronicDeadBird]

And no the one that went flying out of the field doesn't count.

Our robot at least twice at Arizona North decided it would love tap the driver station opposite of the low bar. Turns out motion profiling is easier to spell then it is to implement.

[GreyingJay]

I'm fully expecting ours to accidentally do that at some point during our matches in North Bay this weekend. I'll be mortified, of course, given my vocal stance against this "strategy". But irony is what it is... If it happens, we'll fix it.

Our students agree that "run and gun" is NOT a viable auto strategy on our team. We have code that we think will do the job.

[yonip]

Well one time our robot just rammed the wall repeatedly for ~10 seconds. Next match (I think) it hit the driver station wall again... and then ran away :0 (both during CHS Greater DC, and that was all the castle crashing we've done)
We totally forgot that velocity PID is sticky so we never stopped the bot when it went far enough...

[GreyingJay]

As expected, we had a few unexpected crashes at North Bay. Our most egregious happened when an encoder was ripped clean off the gearbox in a previous match, and nobody noticed...

We fabbed up a skid plate after that!

[Nyxyxylyth]

Yeah, nobody noticed the encoder wire had fallen out.

We've since put in a timeout, just in case.

[EmileH]

1786 at Granite State, every single match

[messer5740]

Ours did that at the Buckeye Regional once... We increased the time and speed to get over some of the ground defenses and on our first run, we went over the rough terrain and went full force into the opposite driver station. Our drive team was mortified because this had happened to us multiple times in our previous regional and vowed to never intentionally do so. We changed the time slightly to avoid that happening again. We make up for a lack of aggressive auto by playing great tele opp!

[epylko]

Originally Posted by EmileH

1786 at Granite State, every single match

I saw a robot do something like that at the Pittsburgh regional this year. It hit so hard the driver station and joysticks flew off and hit the ground.

Everyone added velcro to their driver station and joysticks after that.

[SuperSVGA]

I can't remember what match number it was, but I think our robot hit the wall hard once and knocked the other teams driver station down. And I think the other team got a yellow card, but not us...

[rich2202]

Our team's robot hit the wall, and the wheels kept spinning. The Ref e-stopped our robot to keep it from digging up the carpet.

[IndieWaves]

Originally Posted by SuperSVGA

I can't remember what match number it was, but I think our robot hit the wall hard once and knocked the other teams driver station down. And I think the other team got a yellow card, but not us...

There's not necessarily a penalty for knocking an opponents driver station off, as they have tried to encourage teams to use the hook-and-loop tape to secure it down. The opposing alliance may have done something completely different during the match to earn a Yellow Card.

[SuperSVGA]

Originally Posted by IndieWaves

The opposing alliance may have done something completely different during the match to earn a Yellow Card.

I think the yellow card was probably for them trying to save it as it dangled by the cords.

[EricH]

Originally Posted by SuperSVGA

I think the yellow card was probably for them trying to save it as it dangled by the cords.

Operator console safety is NOT a yellow card. It's right there in the rule, as the exception.

Means that any yellows were for something else. What, I don't care to speculate.

[Road Rash]

Originally Posted by epylko

I saw a robot do something like that at the Pittsburgh regional this year. It hit so hard the driver station and joysticks flew off and hit the ground.

I saw the same thing at the 2016 Wisconsin Regional during qualifications. One robot hit the wall so hard the entire driver station flew right off the shelf.

[Tim Sharp]

Originally Posted by Nyxyxylyth

Yeah, nobody noticed the encoder wire had fallen out.

We've since put in a timeout, just in case.

Encoders seem to be the cause of a lot of that. We struggled with a similar issue at Rocket City. The encoders turned out to be counting down instead of up.