LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Why does Labview create a .vi for each global variables?

Hi Risotto,

you're right and I wasn't exactly enough. If you're using the shared variable as a "single process variable" it is similar than the global variable but unfortunately it is created a new VI automatically. If you open this vi in the Windows Explorer you will discover that there isn't any block diagramm (as it wasn't with global variables). Maybe you already had a look to the tutorial I posted yesterday (second link). In the table of content you find the entry "single-process shared variable". There you find thoe following information:

"The underlying implementation of the single-process shared variable is similar to that of the LabVIEW global variable. The main advantage of single-process shared variables over traditional global variables is the ability to convert a single-process shared variable into a network-published shared variable that any node on a network can access."

If you use n
etwork-published shared variable then you wouldn't have the issue with the VIs as you described. Please have a look in the according section of the tutorial because it would be not so usefull to repeat it here I think.

I would suggest that you should use your variables always as network-published cause you wouldn't risk anything an get a lots of advantages.

If you have additional questions especially according to the tutorial do not hesitate to post them here.

Best regards,

Carsten Sprung
Application Engineer
National Instruments Germany
0 Kudos
Message 11 of 11
(510 Views)