04-05-2007 06:52 AM
04-05-2007 08:48 AM
Zorro, does this delay occur when you start/deploy the program? What you might be seeing is the delay as the variable library is deployed. Communication delays between different modules on a network can slow this deployment down (I personally saw it very slow on a PC to Fieldpoint connection with a bad network). If it is critical to your application to have access to the Shared variables immediately on startup, you can have an initialize case where you can deploy the variabled explicitly using an invoke node, rather than waiting on the auto-deploy from the project, and then start the main case of your VI.
-Mello
04-09-2007 08:49 AM
04-10-2007 11:51 PM
04-11-2007 07:03 AM
04-11-2007 08:01 AM
08-08-2008 02:55 PM
08-11-2008 10:13 AM
08-13-2008 10:29 AM
Hi Jeremy_B,
I tried binding the shared variables to the right network card as explained in your link, but the delay's still there. It's about 1-1½min for 50 shared variables on the first computer, with their 50 bound counterpart on the other computer. I may have just too many shared variables for the startup to be fast, it's a pretty big project. I have disabled the "autodeploy shared variables" too, I'll do it manually from now on, but it didn't do much for the initialization delay.
Usually, I can't disable the building network for security purposes. I'll check if it would be possible to make an exception for the test. It would clear the question about the data passing through the building network.
Any ideas?
Tak321
08-14-2008 03:18 PM
Hi Tak321,
Can you post your VI? That might make it easier to reproduce the problem. Also do you have another computer on or off your building network that you could run this VI on to check this behavior against?
What version of the Shared Variable Engine do you have? You can check this by going to Tools>>Shared Variable>>Variable Manager. Then Help>>About Variable Manager... to view the version.
Regards,
Stephen S.