Quote:
Originally Posted by nick1023
Make sure you have installed the latest driver station and labview updates from www.ni.com/first.
These updates have resolved some of the watchdog issues.
Here is my very broad understanding of watchdog issues at the moment. Each time the watchdog encounters an error it pauses your code running on the crio (watchdogs want to stop the machine from hurting itself if there is an error). If you call something in teleop.vi that is not opened in Begin.vi the whole control system will "pulse" in between pauses for example.
The update addressed this by making the watchdog ignore smaller errors. Ignore more small errors and you will have less watchdog errors. If you do something to cause a more "major" error you will still see watchdog timeouts.
Again, people who really know what the watchdog does are likely to wince at my explaination but it boils down to
-make sure the update is installed.
-make sure you have error free vis.
I think there was a "watchdog for beginners" explaination thread somewhere on the boards today ... |
We had the update installed on the laptop being used, but for good measure we installed them on the driver station pc as well. Then we imaged the cRIO from the driver station and deployed the unmodified default FRC project.
Everything was as fresh as possible. And we STILL couldn't get it working.
We think it may be hardware, because with some testing, it seems we don't get watchdog errors when we unplug the digital sidecar.
I got to the school at 10 am and I left at 7 with this issue still unresolved.