System Watchdog Errors disabling robot

[AndyB871]

Hey everyone, We just bagged and tagged a short while ago, but we had one weird problem that we couldn't seem to fix.

We kept getting Watchdog Expiration: System N User 0

Where N increments by 1 every 5 seconds or so.

We're using labview

At first I figured we must have done something dumb in our code accidentally. ( We discovered opening multiple PWMs or Relays twice causes things to go haywire. It would be nice if WPIlib was a little more forgiving of that, but whatever)

I had my guys disabling just about everything in our code with the Diagram Disable Structure. Didn't change a thing, so we rebooted our laptop, started Labview and created a new default robot project, compiled it and deployed it without touching any code at all. Same issue, we get incrementing system watchdog errors, that disables all our outputs for a fraction of a second, every 5 seconds.

That lead us to assume we borked our cRIO setup, so we re-ran the imaging tool and flashed the cRIO again. Same problem with the default code, We get System watchdog errors, and disabling of our output.

Next we figured maybe the hardware was dorked, maybe we had a bad cRIO or a bad sidecar or 9402 or something. To make our isolation easier we flashed last years robot with this years image, and deployed the default program. Same exact behavior. To make sure we didn't accidentally break last years robot, we re-flashed it with last years image, and deployed last years code. Errors went away.

We backed up there and re flashed last years robot with this years crio, and the error came back. At this point we decided to try switching to a different laptop, didn't change a darn thing, still watchdog errors and short output disables.

We also tried to direct connect the cRIO to the laptop to take the switch out of the loop, which also had no effect. Still watchdog errors.

Eventually we gave up and I had my guys work in some error tolerance, so our vision code didn't lose it's marbles when our LED ring clicks off once every 5 seconds.

Our code runs, but man is it annoying for every output to halt every 5 seconds for a half second or so. I've completely run out of ideas as to what we can try.

To sum up where we gave up:
1) Used last years cRIO flashed with this years image
-- Last years cRIO running last years code has no issues
2) Using a freshly generated default robot project from this years code
3) Direct cRIO to laptop connection via crossover

Anyone have any ideas? I'm really concerned that the FMS will end up disabling our robot for the entire match when the system watchdog expires...

Thanks in advance

-Andy & Team 871