compiling speed-a few ?

[Lucario231]

I see where you are going with this "shadow" VI.
My question is when the Robot Main is edited the shadow is not edited so that it
is a older code. Does this matter at all if the shadow is older code?

I have the basic style of code right now. Will this still work in this style? Because, if the main is built first, then if it changes, all of the other VIs need to be recompiled will have to move and thus recompiled too.

thanks for the advice.

[Greg McKaskle]

This shouldn't do any harm. The shadow will be in memory on the cRIO, and your Main VI too. The big benefit is that if you Main VI is removed from memory, the 500 or so other VIs that it references won't need to be redownloaded because the shadow will keep them there. I have never seen an issue with using this trick. If you think you see something funny, just close the shadow occasionally.

Greg McKaksle

[Chaos in a Can]

You should be able to use the calibration file idea without running into the aforementioned problem.
You could load your main project that uses the calibration file as the startup application, then use a button on the front panel of a vi to save the current settings to the calibration file. Running the debug version should allow you to change the calibration file without rebuilding the startup application.