[sparks-1784]

Hi. We have been dealing with an issue when loading code into the cRIO.
After making changes to our labview code, we 'build' and then load the code through 'run as startup'. The message window states that it is trying to connect to target - and just seems to hang there never actually loading the software. Not sure if we are waiting long enough - there does not seem to be any timeout.
What we end up doing is to re-image the cRIO. After re-imaging, then we are able to connect to the target and load the code. It doesn't make sense that re-imaging must be done each time a new load is sent to the cRIO.

I assume that our programming 'process' is being done out of sequence or incorrectly, but I am not sure. I have not been loading the software myself - it is being done by another mentor - so I am not sure of the environment of the computer while attempting to reprogram the cRIO. 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?

I'd appreciate any suggestions on how to rectify this issue.