Quote:
Originally Posted by PlayfulPlatypus
Upon further experimentation, it appears that the SmartDashboard update on the cRIO side may be causing the watchdog timeouts. I added a couple of SD->PutDouble(...) calls in my drive subsystem whenever the drive motors were being set by either the joysticks or directly by a command. Sometimes this would work, and sometimes it would cause timeouts immediately, and sometimes it would timeout after a CommandGroup finished, but before the default command for the drive subsystem could start. If I remove the calls to SD->PutDouble(...) then the problem goes away, and everything functions normally.
|
If you can come up with a concise example that causes the failure with the 3111 release, please create a tracker at firstforge.wpi.edu in the WPILib project.
Thanks,
-Joe