"watchdog not fed" error

[Lumit]

Ok, so we're having an issue with the code here.
For some reason we are getting a "watchdog not fed error" whenever the code is run, however I don't understand what is causing this.

We don't have any infinite loops, waits, or anything else that is particularly different from the default code.
The only modifications we've made so far is switching to tank drive and two solonoids w/ a compresor

Is there something obvious that needs to be added to the default code to make this work?

[Doug Norman]

I'm guessing your code is still running, even though you are seeing watchdog errors. At this point (update 2.0) it is common to see system watchdog errors. We will soon have an update to address this issue.

Doug Norman
National Instruments

[Lumit]

I have noticed some documents from NI...

Known Issues:
FRC Driver Station returns a system watchdog error often
Workaround—The system watchdog error is normal and should not affect how your program runs.

This seems to say that it doesn't really matter. Unfortunately for us this has disabled our robot completely, we are not able to execute any code. Surely our issues are not normal...

[Joe Ross]

Originally Posted by Lumit

Is there something obvious that needs to be added to the default code to make this work?

The default code should not have persistent, lengthy watchdog issues, only the intermittent ones that Doug mentioned.

Have you run the default code? That would be an important troubleshooting step to see if your minor changes are causing the issue or if the problem is something deeper.

The most common cause of persistent watchdog issues (other then broken code) is not having all the updates installed. Make sure you've installed LabVIEW update 2.0, and reimaged the cRIO with the v19 image. Also make sure you've installed the driver station update. If the dashboard doesn't have a compass in the lower right hand corner, then you've run into a know DS installer bug. Uninstall the DS software and reinstall it, and you should get the updated dashboard.

[Shivang1923]

We had the same error in the begining of build season.

What I noticed was that the camera has a watchdog.feed vi. Without communications to the camera, even the default code was getting all confused. Have you set up your camera properly and is it on and connected to the cRIO properly?

It fixed our watchdog problem

[Lumit]

Turns out that our issue was that we tried to run the code by deploying it directly from labview without setting it to run as startup.

It's working perfectly now.

thanks for the replies

[BLProgram2010]

We're having the same problem with the Watchdog, but we ran the code as a startup and the watchdog still pervent the robot from responding to the joysticks. we as install all the updates and do have that compass on our dashboard. But every time we enable the robot we recieve a watchdog not feed message. Please help us

[Mark McLeod]

Does this happen if you try using a new default Robot Project?

Do you have "Teleoperated" clicked on the Driver Station before you Enable?

[hamosad1657]

This error can appear because only 1 reason: You trying to download a code that wrote with previous LabVIEW version, to a cRIO with Image of newer version. BUT! When you met that error while the cRIO Image is compatible to the code version, the single solution is to reset the cRIO through the Diagnostic panel in the Driver Station.