Quote:
Originally Posted by Radical Pi
Hi all,
I just updated our 2010 cRIO to the 2011 image and rebuilt the code against the 2011 libraries. After switching the jaguar code to the new WPILib version though, we are having some major issues. Jaguars have been updated to v92, and we are using a serial bridge.
When the code is enabled, at random intervals 1 or more motors stop for a few seconds, then continue moving again. On the jaguar when the motor stops the status LED is flashing yellow, when it is working it is the expected state. I've reduced the code down to just joystick input and output to the 4 jaguars with no change. I haven't seen it die though when using only two jaguars. Even when idle the status LEDs on the jaguars show the same symptoms. NetConsole gives no errors, MotorSafety has been disabled on all of the jaguars, and it works fine in BDC-COMM.
Any help would be appreciated
|
We had this problem, but it disappeared after a good reboot and code redeploy. That seemed suspiciously easy, so we'll keep an eye out for these symptoms. I suspect since you've made several alterations to your code I'm sure your cRio has been through a couple reboots, so clearly that isn't a solution.
Perhaps you have some CAN wiring in a bad place coupling in some interference from motors? That thought just occurred to me, and while I was doing my reboot, the wires had been rearranged (temporary test bed), so I may have incorrectly attributed the solution to the reboot.
Check and see where your wires are routed, if they're picking up EMI from the motors, it could be causing a communications fault.
Matt