RufflesRidge's advice is good, if a bit terse.
Quote:
Originally Posted by sparks-1784
One thing I noticed is that the imaging tool, dashboard and the labview development environment are all running at the time of the reprogramming attempts. Is this ok? Will there be any contention from programs competing for communications with the cRIO?
|
If you're still using the 5.0 LabVIEW update, then there is indeed a problem with having a Dashboard program running. A bug in the Network Tables library keeps a deployed program from shutting down when requested, so you can't load new code on top of it. Reimaging the cRIO removes any running code, so that's why it works. So would turning on the NO APP switch (easy on an 8-slot cRIO, less so on a 4-slot) and rebooting.
Shutting down the Dashboard before trying to load new code masks the bug and lets the new program overwrite the old one. That's the simple workaround.
The proper fix is to install the newest (5.1) LabVIEW update.