Global, local variables in SubVI's

Hi,
I'm having a problem with what is probably a 'feature' of labview
(using ver 6.1).
When running multiple SubVI's of the same type, any local variables
declared within the SubVI are globally scoped across all instances of
that SubVI within one VI. Is there any way to prevent this?
I am trying to store the Status of the SubVI in a local, but obviously
each instance of the SubVI ends up with the same status. Currently i
have solved this by having exact copies of the SubVI for each
instance, but obviuosly as far as labview is concerned they are now
different SubVI's, i consider this a bit of a hack and would rather
avoid it.
Any pointers?
Many Thanks,
Ed

If you make the sub-VI reentrant, you will get the type of local you're looking for. On the sub-VI's menus, goto File >> VI Properties >> Category >> Execution >> Reentrant Execution.

Similar Messages

Store Counter Number in BODS using Global/Local Variable

Hi All,
Anyone done before adding a counter integer field into a table based on key via BODS?
Example:
Table 1 (contains just 1 field) <-Input:
Key 1
Key 1
Key 2
Key 2
Key 2
Table 2(contains 2 fields with INT as the 2nd field) <-Output:
Key 1      1
Key 1      2
Key 2      1
Key 2      2
Key 2      3
I was wondering if populating the Local Variable or Global Variable might work but from my understanding, inside the Data Flow , it's not possible to increase the variable value ($count = $count + 1).

Hi Maurice,
Thats a good idea!!
I had currently implemented a solution where i use Variables and Customize Functions to solve the problem.
Will give a try and see if your solution produce the same result.
Tim

How to: Transform Activity: Read global/local variable, execute java code

Could anyone please show me how to do that???

could you please elaborate your usecase? yes you can read global variable using getVariableData( ) xpath function and pass them as an argument to the processXSLT ( ) xpath function.
You can read the global or local variables inside java exec using, please refer samples/references/javaexec sample.

How to find out where I have used a certain Global/Local Variable

Hi Friends
I want to track how and where the shared variable's value has been
changed/Read when I try to debug the program. Anyone
here had the expenrience on how to find a certain shared variable in
the Block Diagrams/VIs. I will very appreciate you help.
Cheers!

Hi All
I have tried the ctr+F to find a certain shared variabl, but the result came out is looks all the shared varibales. How can I focus on 1 certain shared variable. I am using labview8.2.1.
And I have tried the Find shared variables VI from the link Ben showed me. It can not work properly. It showed an error when I try to search, which says: Error 1057 as attached. Could anyone tell me why. Thanks.
Attachments:
Error 1057.JPG ‏66 KB

Shall I use global or local variables for my program?

Hello,
1) I am using 2 while loops in parallele. One 50 ms timed and the other one 1000 ms. The 50 ms one gets data from a sensor. I want to display that data every 1000ms in the 1000 ms loop. I have used global variables to do that. Should I better use local variables?
2) This question deals with the VI I have attached
a) Shall I initialise the " Quitter programme " global variable in the main VI aswell ? Or is what I have done enough?
b)
I want the sequence to continue ( finishes the last sequence and goes back to the first one without any delay if possible ) until the user presses Quit. I am concerned about the " wait until " icon of the exterior main while loop ( set to be 250 ms at the moment ). This time, 250 ms, is the time it takes between the end of the last sequence and the beginning of the first sequence? Is that right? Once u start the first sequence, the while loop doesn’t do anything until the end of the last sequence ( my 3 sequences can take several minutes ) ?
Hope I am clear… lol
Don’t hesitate to ask any questions if not clear enough
thanks a lot,
David
Attachments:
Example1.zip ‏28 KB

Bonjour Marc. You will definitely have a race condition because you are writing to the global in a parallel loop. You could click the stop button in the quitter program, then before it is read in the main loop, the lower loop writes a false to it, and your click is lost. Why do you want a separate quitter program? You may have a good reason but it isn't clear here. I would not use globals or locals for this, just put your stop button on the main vi. You already have one, so why do you want another one in another vi? If you must do it this way, eliminate both lower loops. They are not necessary. The global default is set to false, so when you run the vi, it is false. The button mechanical action is set to latch when released, so after clicking it will turn true until the main vi reads it, then it will automatically turn false. So you don't need the lower loops to keep writing false to it. If you just eliminate both lower loops, it will work fine. The only purpose I could see for the quitter vi is to have one button cause several vi's to stop. Instead of doing it this way, put one stop button in your main vi, create a reference (right click - create - reference), and wire this reference into all subvi's that the main calls. The subvi's must be changed to accept the reference and use it. This would be a much better method to close all vi's with one button.
You could also get rid of the sequence structure (it hides code and makes it more difficult to read). Just put all your code side by side. The error in/out wire will ensure that the execution order will be fixed, just like in your first sequence with the open file and write file functions. Just wire the error out of the write vi to the second write vi, and then the error out of the second write vi to the close vi. No sequence structure needed, and all your code is viewable on one screen.
- tbob
Inventor of the WORM Global

Convert local variable to global - labView

I have a sequence with a VI that contains a local variable array. Now I need that data saved for use by a VI in a later sequence. Can locals be converted to globals or must it be re-created and all references to it changed?
Thanks,
jvh

Hi,
If you are using the SequenceContext as the reference, then your lookup string to your variable would need to change.
eg "Locals.MyArray" would become "StationGlobals.MyArray"
Does this help
Regards
Ray Farmer
Regards
Ray Farmer

Is This a Global Versus Local Variable Problem?

I intend to use a variable (myselector) with a text value (e.g. roses, Big Sur, Pacific Grove, night, etc.) for the sort criteria of my photography list. Selection of a tab from a Tabbed Panel will appropriately define the variable and the selected thumbnails will display in the Content Panel.
The variable "myselector" is defined in the head section; a function for each tab of the Tabbed Panel will redefine the variable per the selected tab. Within the function, I am not using "var" to call the variable. Though the variable "myselector" should be global, the changes to its value are discarded when the function closes. This indicates that it is functioning like a local variable in the function. After a bit of reading, I've not found the cause of the global/local discrepancy or a fix for it.
Diagnosis History - I generated a simplified code. Variable "myselector" is defined as "abcd"; function "myfilter" is called by onclick of the text "button" and changes "myselector" to "efgh". At the end of the file, I used "document.write (myselector) to output the "myselector" value. The script follows.
The end value of "myselector" does not change. However, when I add "document.write (myselector)" to the function, then the changed value is displayed.
I ask someone to explain what I am doing incorrectly or, at least, guide me to a solution. I thank you for your assistance.
Scott
<script type="text/javascript">
var myselector="abcd";
function MM_callJS(jsStr) { //v2.0
return eval(jsStr)
</script>
</head>
<body>
<div id=text>
<p onclick="MM_callJS('myfilter();')">Button</p>
<script type="text/javascript">
function myfilter() {myselector="efgh"; }
</script>
<script type="text/javascript">
document.write (myselector);
</script>
</div>

Dear Ben:
I thank youfor your patience. This includes the script using Insert - Syntax Highlighting - Java.
The coding needs a lot of clean up but I want it to work, first.
Scott
<script src="SpryAssets/xpath.js" type="text/javascript"></script>
<script src="SpryAssets/SpryData.js" type="text/javascript"></script>
<script src="SpryAssets/SpryTabbedPanels.js" type="text/javascript"></script>
<script type="text/javascript">
var dsphotodata = new Spry.Data.XMLDataSet("EM_photo.xml", "/gallery");
</script>
<script type = "text/javascript">
function MM_callJS(jsStr) { //v2.0
return eval(jsStr)
</script>
<script type="text/javascript">
var dsphoto = new Spry.Data.XMLDataSet("EM_photo.xml", "/gallery/photos/photo");
dsphoto.filter(subjectfilter);
var myselector;
</script>
<link href="SpryAssets/SpryTabbedPanels.css" rel="stylesheet" type="text/css" />
</head>
<body>
This is a test of Scott's efforts to program his website.
<br />
<br />
<div id="TabbedPanels1" class="TabbedPanels">
<ul class="TabbedPanelsTabGroup">
    <li class="TabbedPanelsTab" tabindex="0" onclick="MM_callJS('{myselector=\'animal\'}; subjectfilter(); dsphoto.filter(subjectfilter); ')">Tab 1</li>
    <li class="TabbedPanelsTab" tabindex="0" onfocus="MM_callJS('myselector=\"pgbeach\" subjectfilter(); dsphoto.filter(subjectfilter); ')">Tab 2</li>
    <li class="TabbedPanelsTab" tabindex="0">Blank</li>
</ul>
<div class="TabbedPanelsContentGroup">
    <div class="TabbedPanelsContent" >Content 1
      <br />
<br />
<script> {document.write (myselector)} </script>
      <br />
      <div spry:region="dsphoto dsphotodata"> <img src="{dsphotodata::thumbnail/@base}{@thumbpath}" width = {@thumbwidth}px height = {@thumbheight}px spry:repeat="dsphoto" onclick="dsphoto.setCurrentRow('{ds_RowID}');" /></div>
    </div>
    <div class="TabbedPanelsContent">Content 2
      <script> {document.write (myselector)} </script>
      <br />
      <div spry:region="dsphoto dsphotodata"> <img src="{dsphotodata::thumbnail/@base}{@thumbpath}" width = {@thumbwidth}px height = {@thumbheight}px spry:repeat="dsphoto" onclick="dsphoto.setCurrentRow('{ds_RowID}');" /></div>
    </div>
    <div class="TabbedPanelsContent">Content 3 <script> {document.write (myselector)} </script><br />
<div spry:region="dsphoto dsphotodata"> <img src="{dsphotodata::thumbnail/@base}{@thumbpath}" width = {@thumbwidth}px height = {@thumbheight}px spry:repeat="dsphoto" onclick="dsphoto.setCurrentRow('{ds_RowID}');" /></div>
</div>
</div>
</div>
<div id="Selected_Photo" spry:detailregion = "dsphoto dsphotodata" >
<img src="Photo-Thumbnails/{@thumbpath}" width = {@thumbwidth}px height = {@thumbheight}px /><br />
<img src="Photo-Email/{@path}" width = {@width}px height = {@height}px />
</div>
<script type="text/javascript">
var subjectfilter = function(dataSet, row, rowNumber, criteria) { if (row["@subject"].search (myselector) != -1) return row; return null; };

</script>

Local Variables Versus Global Variables

DATA A TYPE I VALUE 100.
PERFORM PRINT_DATA.
FORM PRINT_DATA.
           DATA A(10) TYPE C 'HELLO'.
           WRITE / A. "Wanted to Print 100 (Global)
           WRITE / A. "Wanted to Print 'HELLO'(Local)
ENDFORM.
Note : Both the times, the Local Variable 'A' is Printed .
?Is there any way to   Differentiate the Local and Global Variables When the Names Are Same.*
*It Might be Possible in Object Oriented But I am Looking for the Same in FORMs.

Hello Gagan,
You want to print the Global as well as the local values of the variable named "A". Here are a couple of approaches:
1.The 'Subroutines' are part of the modularization techniques. There are certain keywords like "using" & "Changing" so that you can work by passing Values.
2. There is a keyword named "LOCAL". Declare data object with the keyword "LOCAL" and then try the 'write" statement. I suppose this should work for you.
Let me know if any one of the above works or if you need more help.
Best Regards,
Chaitanya

Global and Local Variable

Hi Gurus, I was unable to see where I can define local and global variables? I see that help.sap.com documentation but where do I create. All variables that I create, are global because, they are visible to all and they all can use it? Any help would be greatly appreciated.

As far as I know, Variables are re-usable objects that are not dependent upon InfoProvider. When I look at this link
http://help.sap.com/saphelp_nw04/helpdata/en/5c/8db07d555411d189660000e829fbbd/frameset.htm
it talks about Global and Local variable? Is this different than what we use in Query Designer?

How many ways to read and write a local variable in a called VI?

Ciao!
I'm producing my first TestStand sequence. It is called "FirstAttempt" and it is made by a single step which calls a VI. One of the first dilemmas i encountered realizing this sequence is how to read and write a local variable (created going in Variables -> Locals ('FirstAttempt') -> <right click to insert local>) in the called VI.
The first way (the only one i tried) is to create a control and an indicator on the VI front panel, connect them to their respective terminals in the connector pane and then specify (going in Step Settings -> Module) that these connectors (shown in the Parameter Name column) are linked to the local variable (selected in the Value column).
The second way (not tried) consists in using TestStand API: create a Sequence Context reference on the VI front panel, link it to a property node in the block diagram, select the property "Locals" and extract from this the local variable name and value which, i think, can be readable and writable.
So...
Are the shown ways correct?
Are there other ways?
Knowing that a "local" variable can be considered "global" within the whole sequence, is there the possibility to simply create a reference to the local variable and use the reference in the called VI block diagram in order to save space in the connector pane (if using method 1) or in the block diagram (if using method 2)?
Thanks!
Message Edited by aRCo on 09-17-2009 05:09 AM

Hi,
Before TestStand 3 you would use the second way you quoted as its the only way.
But now you would use the first way you quoted. You may still what to pass the SequenceContext if you were going to use the TestStand API. For TestStand 3.x and above you would use this way as the first chose. (Personnelly, I would not pass the SequenceContext into a VI if I know it was never going to be used in that VI.)
Not sure I understand your final comment, maybe you are liking it to passing the reference of a control to a subVI so that the control can be updated from within the subVI.
If this is the case and you had a situation where you had a step that was running in parallel with the rest of the steps in the sequence either as a separate thread or execution and were dependent on the contents of the local variable changing from that parallel running step, then you would have to use the API SetVal method to change the local.
Hope this is clear.
Regards
Ray Farmer
Regards
Ray Farmer

RE: local variable cross-talk?

Jeff
A global can be considered as a variable to the entire code, where lots of
different vi's can operate it. Locals only have any meaning within their
own vi, or instances of their own vi.
If anything writes to a particular global, whether in reenterent vi's or
not, it's available everywhere in the code.
What you were asking was about locals though. If a vi is non-renentrant
(i.e. as they come out of the box) then the values in the locals are vi
specific, no matter where the vi is, where it was last used, it retains the
data from it's last operation. If it is re-entrant, then the values in the
locals for each occurance of the vi are its own for EACH instance, i.e. just
like different locals in different vi's, it doesn't matter where else the vi
is used, the data held is that from the last operation of that specific
instance.
Simple way to demonstrate this. Make a vi that has one numeric control,
then code in +1 and get it to write to a local variable for that control.
Throw in an indicator to wire out the result of what is written to the local
for the control.
Then take this vi, put it in a for loop, then put another copy in the for
loop as well. Wire the indicators to the side of the for loop and create
indicator arrays for them. Get the loop to run 6 times say. Now try
running this with the vi in the for loop non-reentrant and then reenterrant.
One way the arrays will contain either all the odd no.s 1,3,5,7,9,11 and
then the other array 2,4,6,8,10,12 (don't know which array will be which,
depends which executes first in the for loop of this example). The other
way they will both be 1,2,3,4,5,6. In the first example, the same vi has
run 12 times, i.e. one copy of the vi which retains its info and is called
in many places and therefore only has one set of values, and the other with
two re-enterant copies where they have their information specific to that
instance of them i.e. effectively they are different vi's. Both ways are
useful, depends what you want.
If you're looking for a use for non-reenterant vi's then consider this:-
For instance. Supposing you get many things to try to write to a global
array of numbers, and you have two vi's one "A" writes to the first element
in the array and the other "B" writes to the second element. Because in LV
you have to read a global first and then write to it to perform a change,
these independant vi's "A" and "B" (be they re-enterant versions of the same
vi, or different vi's), can be performing the tasks simultaneously in the
code. I.e. "A" reads, "B" reads, "A" writes, and "B" writes over the top
with a modified version of what it read, and "A"'s changes are lost. This
is what's known as a "race condition" as "A" hadn't finished and "B" needed
to know what "A" was going to write before "B" performed "A" read. Try it,
hours of fun if you code this kind of thing in inadvertantly!
If the same vi is used, and is not re enterant, it can only run in one
instance at a time, hence two read / write operations cannot be performed
together, problem solved. Unless that gives you timing issues of course,
waiting for one to finish, to write the other......but that's another whole
can of worms.
cheers
Tim Price
This e-mail, its content and any files transmitted with it are intended
solely for the addressee(s) and are confidential and may be legally
privileged. Access by any other party is unauthorised without the express
prior written permission of the sender. If you have received this e-mail in
error you may not copy, disclose to any third party or use the contents,
attachments or information in any way.
-----Original Message-----
From: [email protected]
[mailto:[email protected]]On Behalf Of Jeffrey W Percival
Sent: 29 November 2001 21:12
To: [email protected]
Subject: Re: local variable cross-talk?
Another useful reply! What a great news group this is.
One last thing I wanted to ask about, though, is global vs. local. I see
you talk about globals, but in fact the variables in my subVI's were locals.
I can easily understand the behavior I observed accompanying the use of
global variables, But I guess the use of the word "local" stumped me.
Should I interpret "local" in LabVIEW's sense to mean "local to all
instances of this VI"? And global to mean "visible to all instances of this
VI as well as other VI's"?
-Jeff
Tim Price wrote:
This facility is actually very useful, for instances where you want to
encapsulate some code so that it can only run in one place at a time,
i.e.
global arrays that are written to in more than one place. This method
can
eradicate race conditions completely for example when used like this.
There
are multiple other uses as well.
However, using a vi as a module of code, to run in more than one
instance at
a time simultaneously, re-entrant is the way to go. Just make sure you
debug it first!!!
Remember though, just because a vi may be re-eneterant, doesn't mean
that
everything inside is; sub-vi's, Globals etc. The classic one I've seen
is
where people think that a re-enterant vi is talking to it's own copy of
any
Globals used within it, i.e. counters etc., where in actual fact of
course,
they are all using the same Globals.
Worth playing with a few examples to get familiar with it.
Tim Price
Jeffrey W Percival, Senior Scientist and Associate Director
Space Astronomy Laboratory, University of Wisconsin - Madison
1150 University Ave, Madison, WI 53706 USA
608-262-8686 (fax 608-263-0361) [email protected]
http://www.sal.wisc.edu/~jwp

Tim Price wrote:
Tim, thanks very much. I'll try the experiment you suggest.
Thanks for taking the time.
-Jeff
Jeffrey W Percival, Senior Scientist and Associate Director
Space Astronomy Laboratory, University of Wisconsin - Madison
1150 University Ave, Madison, WI 53706 USA
608-262-8686 (fax 608-263-0361) [email protected] http://www.sal.wisc.edu/~jwp

Equivalent of "C static local" variable?

Hi!
I am trying to write a sub-VI that has multiple call modes
(init, do1, do2) and needs to remember some variables set in the
'init' call. When I try the straightforward way of just placing
indicators as temporary variables on the front panel, these seem
to reset to the default values every time the VI is called.
Is there any equivalent of the static local variables used in C?
Or do I have to use GLOBAL variables?
Rudolf

There are several solutions:
1. Global variables.
You can create global variable for each of your temorary variables. This is easy to do but I think it's not very convivient way to pass data.
2. One Global variable.
If you have many temporary variables you can organize them into cluster and create only one global variable for this cluster. Then you have to read and write this cluster in your SubVI every time you change any of your temporary variables.
3. Pass data to/from your SubVI.
If you look at the most of LV VIs you will see that very often they have some practically identical input and output nodes. For example "AI Start.vi" has " task ID in' and "task ID out" nodes. You can make the same thing. Let your subVI reads and writes some cluster of your tempora
ry variables through its input and output nodes. So you will have the access to this variables in any place ofyour main VI. Also you can change and create your own clusters of temp variables in your main VI. And also you will get the ability to pass these data to your subVI using local variables or shift registers or sequence locals in your main VI
I think that the last way is the most useful.
Good luck.
Oleg Chutko.

LabVIEW 2010 local variable behavior

Hi -
I upgraded to LabVIEW 2010 from 2009SP1 and the attached sub VI no longer works correctly. This is a state machine case structure that gets called inside a loop. I'm setting a Boolean local variable true, then on the next call when the case changes the variable has been reset to false. It did not do this in LV2009.
Someone will immediately tell me I have a race condition, but these local variables are not being written anyplace else, just within these separate cases.
See the attached code, specifically, the local variable "Enable" is getting reset when going from case "Enable" to case "Turn on".
Anyone else seen this issue, or can shed any light?
I fixed the VI by writing the value in each case, but this different behavior makes me wonder what other issues are lurking in LV2010?
Thanks
Solved!
Go to Solution.
Attachments:
eq99_cycling.vi ‏42 KB

This code looks more like some sort of an Action Engine than a state machine, but not quite. It gets called repeatedly from a state machine, and it decides what the next state will be depending upon the inputs. Instead of using all those local variables, I would use uninitialized shift registers (nothing wired to the left side). They hold their value from one call to the next. One more case needs to be added in this case. An unnamed, default case that would set the initial values of all the shift registers. Make it the default case and don't even name it. It will be called first automatically because the shift register is uninitialized so the default will be called. Inside the default case, set all the shift registers to desired values. Next time this subvi is called, those values will still be there. That is as long as nothing is wired on the left side, Whatever is wired to the state shift register will be the next case called.
See attached vi. It is broken because I did not wire anything to the indicators.
- tbob
Inventor of the WORM Global
Attachments:
eq99_cycling-4[2].vi ‏33 KB

What is difference between local variable and property node ?

What is difference between local variable and property node ?
" 一天到晚游泳的鱼"
[email protected]
我的个人网站：LabVIEW——北方客栈 http://www.labview365.com
欢迎加入《LabVIEW编程思想》组——http://decibel.ni.com/content/groups/thinking-in-labview

To make things clear, here are two small examples that show how nasty locals and value properties can be to the naive programmer.
- Open the diagram of the race condition.vi before running it and try to predict what will be the values of the two counters after the third run.
- Use the Compare Locals Properties and Wires.vi to find out how slow locals and value properties can be (times 1000+).
This being demonstrated, I must add that I use globals and value properties quite often, because they are often very convenient
Chilly Charly (aka CC)
E-List Master - Kudos glutton - Press the yellow button on the left...
Attachments:
Race condition.vi ‏9 KB
Compare Locals Properties and Wires.vi ‏18 KB

Data Acquisition - using local variables to write data to a file

Hello,
I am running a Data Acquisition vi (currently in LabVIEW 7.1 but soon to be updated to 8.2) that collects ~100 parameters of data from several sources contained in a while loop. The current configuration (which I did not write) uses very few subVIs and writes to ~100 local variables to store each parameter. It then reads all the local variables and builds an array of all the strings, converts then to a spreadsheet string, then uses the write characters to file function to append to a datafile. I am trying to clean things up and have came up with subVIs to collect the data from the following sources:
8 serial port sources collecting btwn 8 and 20 parameters each
~15 thermocouple readings
~10 analog inputs
~20 parameters read off an ARINC 429 bus.
I have come up with a subVI to read each of the sources and have placed the subVIs in the while loop. Each subVI outputs the data that it collects in array or cluster form. I was wondering how best to write each parameter to a CSV file at between 1 and 10 Hz. Should I write each subVI output to a LV and then read them off as was done before (the difference being that I have reduced the # of LVs to ~10 vs >100?
I should add that precise timing is not that important, so if all the subVIs are not collecting simultaneously (which I understand that they won't be), it does not really matter.
Thanks.

Hi jilla,
jilla wrote:
What I think that you are saying is to turn the outputs of the 4 subVIs into inputs of a 5th subVI that writes to the data file. Correct?
Yes. It may sound like a fine-point, but I beileve it's better to create a VI specifically for formatting data - in your example, 4 arrays IN, a single string OUT. Then write the string to file as a seperate operation. GUI-displayed data can go through a similar transformation, the four arrays wired to a subVI which builds output-structures specifically for display. It's a beginner's mistake to put lots of individual controls and indicators on the screen when groups of them are naturally related (in an object-oriented sense.) Use clusters to group related controls - this will keep the diagram much cleaner.
One more question: at what point (either # of data points or frequency of data collection) does it become necessary to use queues? Thanks.
Well, there's not really a clearly definable "point". I'd say if your update-rate climbs above 100Hz, or you witness poor program or system performance, then it's time. The scenario you've described is a fairly simple acquire/display&log loop - and simple is good. Then-again people can't see/react-to updates faster than about 10Hz - so it doesn't make sense to sacrifice performance - if performance becomes an issue.
Re: queues: Queues are sometimes used to buffer data that's "produced" in one place and "consumed" in another.
Here, if/when logging data, you're logging with every DAQ. I wouldn't recommend using a queue to transport data from a "DAQ loop" to a "Logging-loop" - those functions can be in the same loop. Should/could a queue be used to get data from a "DAQ loop" to update the GUI at a lower frequency? Sure, but a Notifier might be a better choice. Further, in the (simple?) program you've described, you might use a case structure (True/False) to only update FP indicators every "X" iterations - a simple solution that doesn't require Queues or Notifiers.
Cheers!
"Inside every large program is a small program struggling to get out." (attributed to Tony Hoare)

Global, local variables in SubVI's

Similar Messages

Maybe you are looking for