issue with loading robot code

[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.

[lorem3k]

When you're still testing things, just run the code temporarily with the arrow button from Robot Main. We never actually build our code until we get to competiion.

[sparks-1784]

Ok. Thanks for the suggestion. I have actually tried running robotmain too.
I am still wondering why we would have to re-image (re-format) before loading.

[lorem3k]

I'm not sure what could be behind needing to reformat, but we had a aimilar problem earlier this year when another programmer here built the code really early into the season. I'd guess that the new code that's on the computer can't be run/deployed when the cRIO is already in use from the previously deployed code.

[RufflesRidge]

Install LabVIEW Update 5.1 or close the dashboard while loading code.

[Alan Anderson]

RufflesRidge's advice is good, if a bit terse.

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.

[sparks-1784]

Thank you. I'll make sure the team updates with 5.1.