Suddenly disabled?!?

[Mark McLeod]

Lots and lots of ways to mess up that Watchdog.

Which development environment (Wind River or LabVIEW)?
What did you start from as a base (Advanced/Basic Framework, Simple Robot Template).

If you want to post a zip of your project, a second set of eyes will help.

Regardless of Bomber7's self-denial-of-service attacks against himself , the DS No Comms still bothers me as a failed Watchdog would produce a DS No Code error.
No Comms essentially means the DS Linux operating system cannot communicate with the cRIO VxWorks operating system. It should be outside our code unless we discover creative ways to crash the cRIO operating system.

[Mr. E]

Well, I fixed the problem by setting everything back to "factory specs." Reimaged the cRio, reinstalled update 3.0 for labview, even reupdated the firmware for the DS. I think its the reimaged cRio that actually fixed the solution. We'll have to build our code a little bit more carefully this time (smaller incremental steps) to trouble shoot what kind of changes tick my watchdog off.