Things you only do ONCE!

[fb39ca4]

Originally Posted by 3175student17

202. Use a skidplate as the only thing holding you up on the back of the robot (2010, our team's rookie year.)

Why exactly was it a bad idea? Too much friction? Did it get caught on something?

[orangemoore]

Originally Posted by Owen Makin

208. after tethering in the pits, not reconnecting the radio to crio and wondering why your robot isnt moving during the match

210. forgot to charge your driver station laptop at competition, and realize its out charge at the alliance wall right before autonomous and dies...

208.
At our regional this happened but the FTA saved us the match

210.
If you use a classmate they have chargers at the alliance stations

[Owen Makin]

Originally Posted by orangemoore

208.
At our regional this happened but the FTA saved us the match

210.
If you use a classmate they have chargers at the alliance stations

208.we werent saved and they ended up just sitting there.

210. our classmate wasnt updated, our computer was compatitable with the charger, and even though it shut off at the wall, it booted up fast enought that we ended up playing that match

[Gregor]

Originally Posted by Owen Makin

208. after tethering in the pits, not reconnecting the radio to crio and wondering why your robot isnt moving during the match

You never need to disconnect the radio from the cRIO. Plug the tether from the laptop into any of the other radio ports, while still maintaining connection with the cRIO.

[Thad House]

Originally Posted by Gregor

You never need to disconnect the radio from the cRIO. Plug the tether from the laptop into any of the other radio ports, while still maintaining connection with the cRIO.

I'm assuming that he was talking about 2010 or 2009, when the radio only had one port.

[Owen Makin]

Originally Posted by sst.thad

I'm assuming that he was talking about 2010 or 2009, when the radio only had one port.

no it was this year. i have never heard of that though, im the only one on my team who knows how to do any of the wiring or programming stuff. And the mentor i used to have never showed me that.

[kghaemi96]

211. Forget to turn the robot on before a match starts

212. Break 2 drill bits in 1 day

213. Get attacked by killer treading

214. Try to defend against 2485's Sun Tzu. <3 (over 50 penalties called, I didnt realize they were touching us)

[David8696]

Originally Posted by kghaemi96

211. Forget to turn the robot on before a match starts

212. Break 2 drill bits in 1 day

213. Get attacked by killer treading

214. Try to defend against 2485's Sun Tzu. <3 (over 50 penalties called, I didnt realize they were touching us)

This last one made my day.
Also because your blocker may end up breaking... Just sayin'. 45 mph, 3300 rpm.

I'm aloud to brag about that because I was in no way involved in the bild team

[Anthony Galea]

Originally Posted by fb39ca4

Why exactly was it a bad idea? Too much friction? Did it get caught on something?

Yes. It broke off almost every match.
NOTE: We were a team with (i think) no mentors at the time.

[2348humanplayer]

Originally Posted by Al Skierkiewicz

I was just thinking about this while writing in another thread. This may prove to be just a thread to make people chuckle but it also may serve to remind teams about safety and best practices. So here goes a start for the list...

1. Touch a soldering iron to see if it turned on.
2. Carry a battery with one hand, and dropping it. (on your foot or on the ground)
3. Put the red wire on the black battery terminal.
4. Wire the radio to a normal 12 volt output on the PD.
5. Use a crescent wrench as a hammer. (power on or off, you choose.)
6. Hold a robot part in your hand while drilling. ( a variety of errors jump to mind)
7. Put a practice battery on the robot. (actually happens more than you know)
8. Build to last year's dimensions because "they never change".
9. Use a dremmel tool to grind right next to your custom 3D printed part.
10. Mount your bumpers upside down. (except teams 11, 111, 1111)

This is funny, one of our students did number 6, but not for FRC, but for his senior project. Ended up getting a pretty good puncture wound, nothing life-threatening, but had his hand bandaged up for weeks.

[V. Gray]

Originally Posted by bgg

90. Blame the programmers before you double check that the PWMs are all connected.

Unfortunately, the programming team is the wiring team, so either way. We blame ourselves either way.

[Al Skierkiewicz]

There was a day when we got bored at work many years ago. While looking at a Murphy's Law poster we decided to come up with ridiculous units for measurement. From the poster, 'furlongs per fortnight' jump to mind. We then decided to make another for measurement for length and came up with the femto (10^-15) parsec, then the kilo microwatt. We also received a piece of equipment that had a warning label on it that stated "Do not connect to a power supply in excess of 115,000 millivolts." Just when we thought we had seen it all, we received a specification in our rental agreement that we had to provide a TV signal from our transmitter to the building RF distribution that "must be no less that 1,000,000 microvolts." While that sounds harmless enough, our transmitter at the time was capable of producing 866,000,000 microvolts.

[pfreivald]

Originally Posted by Al Skierkiewicz

the femto (10^-15) parsec

I've been known to give distances in attoparsecs... (How tall are you? Oh, about 58 attoparsecs...)

[Storcky]

215: use one Victor 888 and one 884 on the drive system then spend a week trying to figure out why the wheels are rotating at different speeds.
216: not test 215 until after competition season is over. Yay for offseason events!
217: give the robot to the programmers for essentially the first time around 6 PM on practice day. (Ok maybe this one is wishful thinking...)

[martin417]

Originally Posted by pfreivald

I've been known to give distances in attoparsecs... (How tall are you? Oh, about 58 attoparsecs...)

If you are a Mork & Mindy fan, that would be nano-nano parsecs....