View Single Post
  #6   Spotlight this post!  
Unread 15-02-2011, 22:29
Greg McKaskle Greg McKaskle is offline
Registered User
FRC #2468 (Team NI & Appreciate)
 
Join Date: Apr 2008
Rookie Year: 2008
Location: Austin, TX
Posts: 4,751
Greg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond repute
Re: E-Stop Lag... now part of our arm is broken

I know that the arm damage has probably put you behind schedule, but please try to check things out to see what does and doesn't work and to verify you can trust the safety systems.

1. E-Stop the robot. The buttons aren't the most robust things, and if yours is broken, toss it. As mentioned, hitting spacebar disables the robot and is good to teach in addition or instead.

2. Break communications with the robot by pulling the enet cable on the cRIO. The outputs should stop due to the system watchdog.

3. Review code looking for logic issues that could lead to a wild value being computed.

4. Examine the digital breakout. In the very rare cases I've heard of where a robot moved even when disabled, it was due to a fused digital breakout board that didn't disable digital lines properly. I don't remember the exact issue, but it was a damaged board. That doesn't make sense with a PWM signal, but verify the board looks good anyway.

Please let us know if you see anything else that looks flaky, anything else that needs a close inspection or additional testing.

Greg McKaskle
Reply With Quote