Hundreds of "Watchdog Expiration: System X" Errors

[lollypop2020]

Just a few days ago, our cRIO started giving tons of "Watchdog Expiration: System X, User 0" whenever we enable the robot (it doesn't happen when disabled.) It averages out of about 4 or 5 additional system watchdog expirations per second. If left on long enough, the counter gets up to the thousands. I have tried everything I can think of to fix it, I've re imaged and re-updated everything (I'm 100% positive all the updates have worked), and tried using unchanged new project code. It isn't the wireless(I've tried it with an Ethernet cable directly from the DS to the cRIO) Does anyone know what this is caused by or how to fix it? The robot still works, we can use the camera and motors, but it is slightly noticeable that the jaguars stop communicating very quickly and then start again.

[Tom Line]

Please use the search function. You will find that NI is already working on resolving this - it is not your fault. It is a bug in the current software.

[Greg McKaskle]

Can you describe the situations that provoke this? What processes are running? What tab is frontmost on the DS? Is the dashboard also visible? Is Vision displaying in the dashboard? What account was logged in?

Greg McKaskle

[lollypop2020]

Originally Posted by Tom Line

Please use the search function. You will find that NI is already working on resolving this - it is not your fault. It is a bug in the current software.

I did search first, but most of the threads I found were for people getting a few expirations here and there, not the hundreds I am seeing.

Originally Posted by Greg McKaskle

Can you describe the situations that provoke this? What processes are running? What tab is frontmost on the DS? Is the dashboard also visible? Is Vision displaying in the dashboard? What account was logged in?

Greg McKaskle

It happens whenever the robot is enabled. I even tried taking all code out of the teleop enabled state, but the expirations still happen. I don't have the DS with me at the moment, but I can find out more about what processes are running tomorrow afternoon. The DS and Dashboard work fine, as does vision. I honestly wouldn't have known anything was going on were it not for the hundreds of system watchdog expiration errors in the diagnostic tab and the periodic flickering of the RSL and Jaguar LEDs. I was logged into the driver account only.

[BLProgram2010]

We're having the exact same problem, and every time we enable the robot, there is a 'watchdog not feed' message and the robot won't respond to the joysticks. Please help!!!!!

[Greg McKaskle]

Watchdog not fed messages will normally indicate that the code is not feeding the watchdog. This could be because there is a loop or slow operation in the Teleop or Autonomous Iterative method.

Does this happen with teleop, auto, both?

Greg McKaskle

[lollypop2020]

Originally Posted by Greg McKaskle

Watchdog not fed messages will normally indicate that the code is not feeding the watchdog. This could be because there is a loop or slow operation in the Teleop or Autonomous Iterative method.

Does this happen with teleop, auto, both?

Greg McKaskle

I used the totally unchanged new project code that was working perfectly a few days ago. I also tried taking all the code out of the teleop method, but the system watchdog still expired rapidly. This happened in both auto and teleop, but only when enabled.

I called NI today, and spoke to someone for quite a bit who was unable to figure out what was wrong. We went through all the troubleshooting steps, but she said that it was beyond her knowledge and that unless I talked to R&D, there was nothing I could do unless the upcoming update fixes it.

[Tom Line]

FYI - we are also seeing this on a heavily modified project. Literally hundreds.

[BLProgram2010]

I'm having the exact same problem, Do you know if there is anyway to fix it?

[Tom Line]

NI is looking into it. It's a bug, but so far it hasn't impacted how our robot actually functions. It's just annoying seeing error messages when we don't think we have errors

[lollypop2020]

I tried installing the DS and Dashboard software on a desktop computer to see if that would improve anything, amazingly enough our system watchdog expirations completely stopped happening. It's good that we have something to work with until the next update, but still rather frustrating that the classmate doesn't work.

With the classmate, I decided to completely start over from scratch. I got out the recovery flash drive, and completely reinstalled windows. I installed the labview update and installed/uninstalled the DS update until it worked. Even after doing all that, re-imaging the cRIO and still using a completely 100% unchanged project, we are still getting the hundreds of errors. It makes me inclined to think that something is actually wrong with our classmate, but I'm not sure.