I realized that I did not fully answer your question..
Here goes:
"You will at one point have to connect to the instruments in order to "test" your LV code. What I tried to say in the previous 2 posts is that the LV4 code should still work.
Depending on the instruments that you work with, you may be able to find "virtual instruments" which may help you to complete the code without actually be connected to them. The other thing is that you can develop code and see that it is kind-of okay if the run arrow is not broken.
However, unless you have a virtual instrument or running the actual instrument, you'll get an error. But there is a trick around that. If you know you're going to get an error, capture that error into a Case Stru
cture and change it back to a non fail condition (or cheat by not wiring the error line to the instrument (bad coding practice but it will work). ((Maybe I shouldn't be giving bad advice - I'll get us both into trouble ;o)
I assume you have to share instruments with the designers and you basically never have access to it, right?
Anyway, not to be too verbose:
Here is another scheme. Create a virtual instrument by having a "box" which simulates the measurements for you and sends the values to the rest of your vi. You can leave in the instument by placing it into a Case Structure under FALSE. Force a TRUE value into the case and send the typical values the instrument would measure to the vi. After you get access to the instrument, change the case to FALSE to properly test it. Once you are happy with your code, remove the Case Structure."
Hope this long explanation helped..
Have fun..
JLV