11-15-2006 07:51 PM
11-16-2006 09:22 AM
turbot,
If you are not changing your shared variables often you can turn off auto-deploy by right clicking your library and unchecking "auto-deploy". This way it will not re-deploy the variables every time you start your VI. If you change your variables you can then re-deploy by right clicking on your library and selecting "deploy". If you do things this way, you will only have to spend the 3-5minutes deploying once and every subsequent time you will not have to wait.
-Justin D
11-16-2006 07:41 PM
11-16-2006 09:19 PM
11-17-2006 10:52 AM
turbot,
If the variables are hosted on the server side, the client will not cause the server to re-deploy when the client connects. The only other thing that I can think of that might be slowing down your shared variables would be network congestion. Do you see the same behavior if you connect the server and the client with a crossover cable?
-Justin D
11-20-2006 08:37 PM
11-21-2006 05:48 PM
11-21-2006 07:21 PM
11-22-2006 11:34 AM
turbot,
Unfortunately, the shared variable engine does not support multiple network cards. R&D is looking into possibly supporting this in the future but as of right now this is not supported. If you look at the LabVIEW 8.2 readme it actually states:
"Network-published shared variables do not function properly if multiple network adapters are enabled on the same computer."
I'm sorry if this causes an inconvenience but this is most likely what's causing your issues.
-Justin D