Thread: CAN being wierd
View Single Post
  #2   Spotlight this post!  
Unread 16-02-2013, 11:44
Levansic's Avatar
Levansic Levansic is offline
Registered User
AKA: Len Evansic
FRC #0585 (Cyber Penguins)
Team Role: Mentor
 
Join Date: Jan 2012
Rookie Year: 2008
Location: Tehachapi, CA
Posts: 185
Levansic has much to be proud ofLevansic has much to be proud ofLevansic has much to be proud ofLevansic has much to be proud ofLevansic has much to be proud ofLevansic has much to be proud ofLevansic has much to be proud ofLevansic has much to be proud ofLevansic has much to be proud ofLevansic has much to be proud of
Re: CAN being wierd

I certainly could be wrong on this, but I'm assuming that you are using the jaguars to control single CIM motors on a tank drive setup. What is your gear ratio, wheel size, and wheel configuration?

I ask, because it sounds like you are inducing over current situations. The one that cuts out more often likely has a chain that is a bit too tight, but both sides are likely dealing with gear ratios that are too low for the torque that they are asked to provide. Another possibility is that the one that cuts out more is not the one directly connected to the cRIO, and you have a CAN bus connectivity or termination problem.

An attempted quick fix for the overcurrent condition, is to use a bigger number for the voltage ramp rate parameter. By default, the parameter is set to ~500, which corresponds to a 1/8 second ramp from 0-100% output. This is too quick for heavily loaded CIM motors, causing an over-current cutout. If you aren't already using voltage ramping on the jaguar, it sounds like you should be. This will throttle the response to "drastic" changes of input.
Reply With Quote