Thread: Stall detection
View Single Post
  #5   Spotlight this post!  
Unread 07-03-2013, 15:22
Jefferson Jefferson is offline
Registered User
AKA: Jeff Clements
FRC #0016 (Bomb Squad)
Team Role: Mentor
 
Join Date: Jan 2011
Rookie Year: 2010
Location: Mountain Home, AR
Posts: 258
Jefferson has a reputation beyond reputeJefferson has a reputation beyond reputeJefferson has a reputation beyond reputeJefferson has a reputation beyond reputeJefferson has a reputation beyond reputeJefferson has a reputation beyond reputeJefferson has a reputation beyond reputeJefferson has a reputation beyond reputeJefferson has a reputation beyond reputeJefferson has a reputation beyond reputeJefferson has a reputation beyond repute
Re: Stall detection

I don't know a thing about Labview, but I am familiar with CAN. The non-hardware solution is to monitor the output current to your shooter motors. In c++, the function is GetOutputCurrent. Our method: if the current exceeds a defined limit (say 20A) for a defined time (1.5 s) then you know the motor is stalled. Then you can take action to either shut it down to save the motor, or run it backwards if you think you can clear the jam.

To determine the current limit and time above, you'll need to know what a baseline current is for your shooter and how it reacts under normal conditions. Easiest way to do that is to chart the current on the dashboard while you are doing normal tasks like startup and shooting. These will create spikes in current. You don't want these normal activities to get confused with a stall condition.