12-17-2008 08:02 AM
NI had this to say about warm up reads:
"It seems that the way shared variables works has changed from version 8.5 to 8.6. In 8.5, the variable connection is not set up until the first node is executed. This is why a "warm up" read is necessary in 8.5. In 8.6 however, the connection is set up as soon as the VI is executed. However this connection can still take some time, so in 8.6 all that really matters is that there is a large enough delay between when the VI is run, and when the shared variables are used. Therefore either method of the warm-up read or initial delay should give the VI enough time to create a connection."
Undeploying before deploying libraries:
"For the ... issue of restarting the [OPC] service with the variables deployed, ... this was similar to losing an internet connection and not being able to reconnect until you get an IP address. Apparently it is just simply faster to undeploy and redeploy than it is to wait for the deployed library to reconnect."
12-17-2008 08:22 AM
Hi LabBEAN
Thanks for the posts, sorry the delayed response, been struggling to post on this thread for some reason, but has eventualy worked. It seems as though this warm up period is what might solve the problem for me. I am using labview 8.6, so hopefully the warm up period wont be too long. Will test this out on some small programmes to see how it goes. Won't be able to test it on the main program I was having problems with because that project has been delayed for a bit, but I'm keen to see if it will run smoother your advice. Will post my results when I can test this on it.
Thanks again for the advice
JChec
12-17-2008 08:46 AM
No problem JChec.
A 50 ms dumb wait at the beginning of your top level VI should be sufficient since you're using LabVIEW 8.6 (...LabVIEW 8.5 users should consult my previous posts). This does not appear to be necessary for subVIs making shared variable calls. (Let me know if you see otherwise.) I have not tested subsequent application instances in VI server.
Take care,
Jason