What was your teams worst expierence during competition?

[mechanical_robot]

What was your teams worst incident/experience at competition.

Ours was when during the Ultimate Ascent game someone threw a Frisbee and it hit out of all places the power switch on our robot when it was trying to make the 10 point climb, so we did not get the 10 point climb at that. But we fixed it immediately. though

[Brandon_L]

To go with the game-pieces-shutting-down-robots theme, in 2010 at the Duel on the Delaware offseason, we forgot our electronics covers back home. A soccer ball rolled down the return, bounced on the ground twice and into our robot hitting the power switch.

[CENTURION]

There's probably a worse one that I can't recall at the moment, but a recent one:

At our 2013 regional, a newer student was tweaking our autonomous code in the pit. We had our final practice match for the day coming up, and the new code was put on the robot, without being checked or tested.

During auto, the climber ran backwards. This was a half-inch ACME lead screw, running off a CIM (Don't remember what gearbox was on it). So instead of moving the climber up a bit to release another mechanism that was tied into it, it ran downwards, and kept running until it bottomed out, and then kept running some more. This also raised the robot off the ground at the front, and so it couldn't drive.

The screw warped itself pretty bad, and bent a couple 0.25" aluminum brackets by 40 or so degrees. The climber was pretty trashed. The CIM continued to run (while stalled) for the rest of the match, came back to the pit too hot to touch.

The pit crew stayed late that night, and had it running by the next morning, which was quite a feat.

[Qbot2640]

Originally Posted by antimatter_john

...someone threw a Frisbee and it hit out of all places the power switch on our robot...

In one match this year we had just finished autonomous, was about 2 feet from the loading station where our human player was standing with four discs in hand, and a Frisbee hit our power switch, turning us into a statue for a good minute and a half. What a helpless feeling.

[Jefferson]

2013 Razorback Regional:

First practice match. Our regular diver coach was very ill, so I was pinch hitting for the first time ever. I'm usually just the controls/programming guy. Somebody (may have been me) plugged the gyro into analog port 8 instead of 1 (the other 6 were all filled, so honest mistake). After firing the first three shots, the robot was supposed to drive back to the center line using the now non-existent gyro. Instead, it spun about its axis at full speed for the remainder of autonomous. The pickup was pretty badly damaged by the pyramid, but it woke up a pretty bored crowd.

Final elimination match. Loading discs, one disc was caught between the robot and the wall. Driver tries to shake it loose, but instead the disc is shoved into the control system, pulling the header off the analog module. This causes some wheel modules to spin briefly, and the shooter cam follower to roll all the way around and snap. Those screws are in the headers for a reason people! Somehow ours was out.

I was glad it was a short drive home from our first "home" regional. Very frustrating weekend.

[Koko Ed]

This (happens at 7:52 in the video) fortunately it was followed by one of our best experiences ever not long after as we eventually won the event from the sidelines.

[DampRobot]

30 pt climber having too little travel by about 3/4" to climb for 30. That seriously blew.

[brandon.cottrell]

Last year prior to revisions we had the worst hopper for our frisbees. Not only was it difficult to get frisbees in their because of the odd angle and shape of the hopper, their was a constant loom of fear that a frisbee would go in upside down (We couldn't get it out if that happened).

At our 2nd regional, we got put on an alliance with 2 mainly defence robots, meaning we had to be the dedicated scorers. Then this happened.

Believe it or not an alliance actually selected us as a defense robot because of our fast drivetrain, made it to semis. We fixed our robot quite a bit in the last few months and now it's actually pretty good.

[JamesCH95]

In 2004, while vying for a regional win at Palmetto, a missed decimal place in a revised autonymous code caused our robot to impact the other player station at full speed (in the next year or two FIRST started putting velcro on the player station IIRC). This caused one of our transmissions, the universally disappointing 3/8 Bosh drill transmission, to fall apart. We thought we fixed it, but not quite. In the next few minutes our alliance captain smoked a motor or two on their robot's arm, making them basically unable to score. A few seconds into the 3rd match of the finals our transmission failed entirely, turning the final match into a snooze-fest that the other alliance won handily, as the chassis driver I was heart-broken, as was much of our team.

To take a step back, we were the 8th seeded alliance (after much in-picking in the top 8) and managed to knock out the 1st and 5th seeded alliances convincingly. Sometimes luck just doesn't go your way...

Though this was my most frustrating experience with FRC, I wouldn't call it bad (just less good I guess?) Our team had gone from 2nd-to-last in the standings to one of the top-scoring robots during eliminations, and while I/we felt that we could have (and should have) won, it was a strong lesson in graciously accepting a loss and always trial-running antonymous code before putting the robot out on the field.

[Peter Matteson]

I have a lot of stories that would shock many of you or just have you rolling on the floor, but I'll stick with the simple one that used to happen all the time with the old control systems.

The match starts and you realize your robot isn't turned on. This was a common occurence up until around 2004 or 2005.

Also for a bonus there's the the time we almost took out the scoring table at the UTC New England Regional in 2004:
http://www.chiefdelphi.com/media/photos/17725

[cmrnpizzo14]

Originally Posted by Peter Matteson

I have a lot of stories that would shock many of you or just have you rolling on the floor, but I'll stick with the simple one that used to happen all the time with the old control systems.

The match starts and you realize your robot isn't turned on. This was a common occurence up until around 2004 or 2005.

Also for a bonus there's the the time we almost took out the scoring table at the UTC New England Regional in 2004:
http://www.chiefdelphi.com/media/photos/17725

I see that your team started doing better once you learned to turn the robot on

[Caleb Sykes]

Not a terrible moment, but funny and nerve-wracking.
In autonomous in our first practice match, the robot shot 3 discs into the wall, then drove backward 2 feet, then proceeded to spin in circles in place for the rest of autonomous. Nothing broke, but it scared all of us.

Aren't untested auto modes so much fun

[Jay O'Donnell]

This isn't the worst story in our teams history but it's the one I was on the team for. At Battlecry this year I was driving and we were in the middle of our best match yet that weekend, when all of a sudden we stopped moving. The FTA ran over, took out his phone, and took a picture of our laptop and left without saying a word. Our laptop had blue-screened in the middle of the match.

[Answer42]

Having our teams mentor scream at us for an hour after another teams mentor helped us improve our shooter at a regional.

[AdamHeard]

Originally Posted by Answer42

Having our teams mentor scream at us for an hour after another teams mentor helped us improve our shooter at a regional.

That mentor sounds like a real winner.