[Greg McKaskle]

It is great to post the solutions to your problem, but I'm not sure all of the things you are combining together are really related.

If you have watchdog problems, the problem is almost certainly with the code feeding the watchdog and you shouldn't need to reimage the cRIO. If all else fails and you aren't in need of the extra safety provided by the watchdog, you can delete it from the code.

As for the deployment, something that we saw twice in DC were deployments where all sorts of source files were listed in the source page. That wasn't the default build, and it can cause name collisions which will result in the wrong file being in memory at runtime. It took a long time to look at the Build Spec because we didn't think it would have changed. Anyway, I know better now, and if you are having lots of deploy problems, it is probably worthwhile looking at, and perhaps deleting and building another. As you mention, it should have only the Robot Main VI included, let the LV linker do the rest. That and the additional exclusions page with the checkbox for libraries are the only things you should have to concern yourself with if you are using one of the frameworks. Also, another way to cleanup a controller is to ftp to it and delete stuff. You really shouldn't need to reimage unless there is a patch or if things have been mangled by renegade file I/O or something really serious.

On the other hand, a reimage will not hurt, but is probably not necessary and will only make everything take longer.

Greg McKaskle