View Single Post
  #6   Spotlight this post!  
Unread 05-02-2012, 23:45
PAR_WIG1350's Avatar
PAR_WIG1350 PAR_WIG1350 is offline
Registered User
AKA: Alan Wells
FRC #1350 (Rambots)
Team Role: Alumni
 
Join Date: Dec 2009
Rookie Year: 2009
Location: Rhode Island
Posts: 1,187
PAR_WIG1350 has a reputation beyond reputePAR_WIG1350 has a reputation beyond reputePAR_WIG1350 has a reputation beyond reputePAR_WIG1350 has a reputation beyond reputePAR_WIG1350 has a reputation beyond reputePAR_WIG1350 has a reputation beyond reputePAR_WIG1350 has a reputation beyond reputePAR_WIG1350 has a reputation beyond reputePAR_WIG1350 has a reputation beyond reputePAR_WIG1350 has a reputation beyond reputePAR_WIG1350 has a reputation beyond repute
Re: Near-death experiences or injuries during build season?

Once our primary mentor was using a belt sander to deburr a decently sized aluminum bracket. It got loose and flew >10 feet and missed his son's head by inches. If I remember correctly, the only reason it didn't hit him is because he had just bent down to look at something in/on the robot.

Quote:
Originally Posted by dellagd View Post
My friends laptop is a piece of *$#%, despite the fact that is has an i7 even though it is 1.5 years old. It is electrically unsound, so if we touch him while he uses the trackpad, he will be shocked.

I'm sure it hurts, as the sound was quite audible, but wow was that a hilarious day.
Sounds like he spilled something (probably hot) on it or otherwise damaged it. I would look into touchscreen screen protectors. either that or something has come loose internally.


Quote:
Originally Posted by JamesCH95 View Post
One of my friends also had a lathe chuck come loose, again on one of the high-powered lathes at the same shop. The part guard kept the 50lb chuck from running him over. A post-mortem by the shop's lead tech found that the chuck was faulty.
How fast was that going at the time? I can imagine it made quite a noise when it crashed.
__________________

Last edited by PAR_WIG1350 : 05-02-2012 at 23:57.
Reply With Quote