Local variable is never used

I have some code like this:
String s = null;
if (<some test>)
s = "whatever";
}Eclipse tells warns that the local variable s is never used, which is somewhat understandable since the assignment of s is nested. Still, it's annoying. I don't want to turn off the warnings because I like to be notified of them in order to keep the code clean. Is there a reasonable way around this?

It has nothing to do with it being "nested". Even without the if, the variable is not used. It's only assigned to. But you never use it. You never pass it to a method, or assign it to any other variable.
You can
* Get rid of the variable, since you're not using it for anything.
* Use it.
* Ignore the warning.
* Turn off that warning in eclipse's settings. (Not recommended, IMHO.)

Similar Messages

Local variable fail when using SIT

Dear all,
I am using SIT (Simulink Interface Toolkit) to obtain data generated by the model of Simulink. I need to use the local variable of the indicator to get the data out.
The interface with the mappings seems to work fine. The problemn is that the local variable of the waveform （this waveform is an indicater which mapped to the output signal of simulink and it can displays the signal from simulink）didn't work. I cann't obtain any data from the local variable, but the waveform which the local variable belonges to seems to work fine.
I also found an interesting thing that, when I hightlighting the execution process, the local variable seems like didn't work at all, because there is no data flows from it.
The software version is Matlab simulink R2011b, Labview 2011.
Below is a simple test model in simulink. It is a sine signal.
Below is the local variable from the waveform which mapped to the signal of simulink. To check there is any data in the local variable, I put a waveform to check.

Dataflow.
The local variable of the waveform is going to be empty to start. The writing of the local variable called Waveform to the indicator called Local Variable is going to happen right away. Only later does the waveform get any data. But by then the first part has already exectued never to be run again.
I would recommend looking at the online LabVIEW tutorials
LabVIEW Introduction Course - Three Hours
LabVIEW Introduction Course - Six Hours

How to assign bean value to a local variable in JSP using struts.

Hi everybody!
I've a problem that puzzled me on how to assign a bean value to a local variable like String in JSP using struts.
we can have someting like this to display the value
<bean:write name="detailService" property="status" />or
<bean:define id="theStatus" name="detailService" property="status"/>
This is country: <%=theStatus%>but an error occured when I tried like this:
String currentStatus = "<bean:define id="theStatus" name="detailService" property="status"/>";
or
String currentStatus = "<bean:write name="detailService" property="status" />";Is there a way to do this?.....
Any help pretty much appreciated

Java != JSP.
The <bean:define> and <bean:write> tags are custom tags meant to appear in the HTML section of a JSP file, as opposed to the scriptlet section. They actually get turned into java code as part of the translation process.
The <bean:write> tag naturally just writes out what you tell it to.
The <bean:define> tag defines a local variable, and gives it a value.
this should do it.
<bean:define id="theStatus" name="detailService" property="status" type="java.lang.String"/>
<%
String currentStatus = theStatus;
%>With the advent of JSTL, you shouldn't really need to use scriptlet code anymore. Personally I am for 0% scriptlet code in any jsp I write.

Can you sort the "local variable" pick list?

My program has a lot of local variables. If I right click on a variable and click on "select item", a loooong list of all my local variables appears. They appear to be in the order in which they were created in my program.
Is there any way to modify the display to where the local variables appear in alphabetical order?
Amateur programmer for over 10 years!

The best solution is to not use a lot of local variables . Here is a neat trick to use local variables without having to use local variables . If you are using a state machine (case structure inside a while loop), create a cluster constant on the block diagram inside a state or case called "Local Defs". Inside the cluster, put constants for every local variable you will use. Label the constants like you would a local variable. Put a shift register on the loop border. Wire the cluster to the shift register on the right side. Do not initialize the shift register on the left side. In any case frame, you can wire from the left shift register into an unbundle or bundle to read or write to the Local. You never have to call the Local Defs state, the cluster will be defined because of the wiring. If using controls at many places, make a local constant for each control and have a state where the control is written to the local. Then you can read the local to use the value at any time. See attached vi for an example.
- tbob
Inventor of the WORM Global
Attachments:
StateMachineWithLocals.vi ‏45 KB

Having Trouble Copy and Pasteing Local Variable in LabVIEW 2010

I am Having Trouble Copy and Pasteing Local Variable in LabVIEW 2010 in s subVI.
I have a VI that has a Local Variable called "Node Addr". I can select it OK, and it appears to Copy OK, But when I go to paste it, nothing appears. It doesn't matter if I use Cntrl-C Cntrl-V or the Copy and Paste from the Edit menu, I get the same results. I tried many times and got the same results. I made sure that I had click a paste location. I can insert the Local Variable if I use the Data Communication panel.
On one of the Paste, I got an error in the error list that said that a Local Variable was not connected to anything. When I clicked on the error, it took me to an insible item in the lower right corner of the block diagram that had nothing but a select box around it. I couldn't select the invisible item, but I could delete it.
Why does the copy and paste of this local variable not work?
Why does the paste cause the insertion of an invisible item?

dbaechtel wrote:
My VI is fairly complicated. In several places in the VI, I am either reading or writing to this variable which is an numeric Indicator on the Front Panel. Using local variables seems to be the best way to handle this situation rather that using wiring all over the VI. Since the VI is mainly a State Machine and there are only 2 Writes to the local variable, I am not afraid of race conditions in this case. NO!! While you may think that using Locals is your solution to wiring, it is not! The fact that you are writing and reading, most likely from several places, will most definitely contribute to a race condition. Depending on your implemetation, you should ALWAYS use wires. The wires are the variable. If you are using a loop (While, For), then using shift registers are appropriate means for routing values so that they are used by other sections of the code, later. One thing you must respect with LabVIEW is the dataflow. That's where Locals often fail.
I am not copying the Local Variable from one VI to another.
I am not copying the Local Variable from one VI to another.
The Data Communication panel is one of the panels that shows up in the Functions pop up list when editing the Block Diagram. It is the panel that includes the Local Variable function.
I don't know if the invisible item that was inserted in my block diagram was hidden or not. All I know is that the Errors List said that it was a Local Variable and that it was not connected to anything. I couldn't select it to get more information. All I could do was delete it.
You did not address my questions about why the Copy and Paste does not work properly for my Local Variable. Maybe it's a sign from the Software Gods not to use them LOL!..
So if I understand correctly, you are trying to copy & paste the Local Variable from within the same VI. How large is your block diagram? Did you try right-click on the variable and select "Find > Local Variables"? If it's a block diagram larger than 1 single screen (which it shouldn't), then it is possible that the Local is hiding beyond the screen. You should find it as I described earlier.
See my comments in red above.

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

Clause local variable question

Hi,
I still don't have a glue how clause local variables work. Using the simple D :
#pragma D option quiet
int this x;
BEGIN
check1 = 0;
check2 = 0;
syscall::read:entry
/ execname == "in.mpathd" /
this->x = check1 != 0 ? this->x : 1;
check1 = 1;
printf("1st clause: %d \n", this->x);
syscall::read:entry
/ execname == "in.mpathd" /
printf("2nd clause: %d \n", this->x++);
syscall::write:entry
/ execname == "in.mpathd" /
this->x = check2 != 0 ? this->x : 1000;
check2 = 1;
printf("3nd clause: %d \n", this->x);
}I am getting the following result:
3nd clause: 1000
1st clause: 1
2nd clause: 1
3nd clause: 2
1st clause: 2
2nd clause: 2
3nd clause: 3
1st clause: 3
2nd clause: 3
3nd clause: 4
1st clause: 4
2nd clause: 4
3nd clause: 5
1st clause: 5
2nd clause: 5
3nd clause: 6
1st clause: 6
2nd clause: 6
3nd clause: 7
1st clause: 7
2nd clause: 7
3nd clause: 8
1st clause: 8
2nd clause: 8
3nd clause: 9
1st clause: 9
2nd clause: 9
3nd clause: 10
1st clause: 10
2nd clause: 10
3nd clause: 0
1st clause: 0
2nd clause: 0
3nd clause: 1
1st clause: 1
2nd clause: 1
3nd clause: 2
1st clause: 2
2nd clause: 2
3nd clause: 0
1st clause: 0
2nd clause: 0
3nd clause: 3
1st clause: 3
2nd clause: 3
3nd clause: 1
1st clause: 1
2nd clause: 1
3nd clause: 2
1st clause: 2
2nd clause: 2
3nd clause: 3
1st clause: 3
2nd clause: 3
3nd clause: 4
1st clause: 4
2nd clause: 4
3nd clause: 5
1st clause: 5
2nd clause: 5
3nd clause: 6
1st clause: 6
2nd clause: 6
3nd clause: 7
1st clause: 7
2nd clause: 7
3nd clause: 8
1st clause: 8
2nd clause: 8
3nd clause: 9
1st clause: 9
2nd clause: 9
3nd clause: 10
1st clause: 10
2nd clause: 10
3nd clause: 11
1st clause: 11
2nd clause: 11
3nd clause: 12
1st clause: 12
2nd clause: 12
3nd clause: 0
1st clause: 0
2nd clause: 0
3nd clause: 11
1st clause: 11
2nd clause: 11I was expecting that the value of this->x within syscall::read:entry should be incremented by 1 as the probe fires and this->x within syscall::write:entry should remain 1000. Hmm...

Hello Michael,
thank you for the explanation. The output of your D brings some new questions:
BEGINClause 2: 0
Clause 3: 0
Clause 3: 1
Clause 5: 0      -> should be 99 ?
Clause 3: 2
Clause 5: 0
Clause 2: 0      -> should not be reentered again?
Clause 3: 0
Clause 3: 1
Clause 3: 2
Clause 3: 3
Clause 5: 99
Clause 5: 100
Clause 5: 101
Clause 5: 102
Clause 5: 103
Clause 5: 104
Clause 5: 105
Clause 5: 106
Clause 5: 107
Clause 5: 108
Clause 5: 109
Clause 2: 0
Clause 3: 0
Clause 3: 1
Clause 5: 0
Clause 3: 2
Clause 5: 1
Clause 3: 3
Clause 3: 4
Clause 3: 5
Clause 3: 6
Clause 3: 7
Clause 5: 1
Clause 3: 8
Clause 3: 9
Clause 5: 2
Clause 3: 10
Clause 3: 11
Clause 5: 3
Clause 3: 12
Clause 3: 13
Clause 5: 4
Clause 3: 14
Clause 3: 15
Clause 5: 5
Clause 5: 110
Clause 5: 111
Clause 5: 112
Clause 5: 113
Clause 5: 114
Clause 5: 115
Clause 5: 116
Clause 5: 117
Clause 5: 118
Clause 5: 119
Clause 5: 120
Clause 5: 121
Clause 5: 122
Clause 5: 123
Clause 5: 124
Clause 5: 125
Clause 5: 126
Clause 2: 0
Clause 3: 0
Clause 5: 127
Clause 3: 1
Clause 5: 128
Clause 3: 2
Clause 5: 129
Clause 3: 3
Clause 5: 2   -> should be 130?
Clause 3: 4
Clause 5: 3
Clause 3: 5
Clause 5: 4
Clause 5: 5
Clause 5: 6
Clause 3: 6
Clause 3: 7
Clause 3: 8
Clause 5: 7
Clause 3: 9
Clause 3: 10
Clause 3: 11
Clause 5: 8
Clause 3: 12
Clause 3: 13
Clause 3: 14
Clause 5: 9
Clause 3: 15
Clause 3: 16
Clause 3: 17
Clause 5: 10
Clause 3: 18
Clause 3: 19
Clause 4: 20     -> should exit here?
Clause 5: 1       -> 1 again?
Clause 3: 4
Clause 3: 5
Clause 3: 6
Clause 5: 2
Clause 3: 7
Clause 3: 8
Clause 3: 9
Clause 5: 3
Clause 3: 10
Clause 3: 11
Clause 3: 12I'm wondering that the initial value of probe 5 is 0, not 99.
Should not have the action of Clause 2 executed just once, because of the predicate / !this->x / ? But it appears several times.
After Clause 4: 20 the D should exit. Why are there still probes firing and why the value of this->x has become 4 ?
Should not clause 5 increment this->y by 1 if it's fired? Why does this->y get values < 99 ?
Edited by: go_insane on Aug 11, 2010 3:18 AM

Wire or local variable?

The best method to pass data inside the same VI is wire or local variable? or the same? Which one is more effient? Thanks.

Everything Dennis said above is true.
Let's look at a seasoned text programmer suddenly forced to use LabVIEW: The first mental hurdle the new LabVIEW programmer might face is the fact that there are no visible "variables", something that is central to text based programming languages. Looking for "variables", he might stumble on local variables and suddenly he thinks he found the solution to keep programming the old-fashioned way.
What you might see as a result, is a LabVIEW program that has all controls and indicators completely disconnected, all lined up on the top or left side of the diagram (Similar to the variable definitions section in classic text code ). Then, on the right side everything is done writing and reading from local variables. Each disconnected code segment duplicating a programming statement, e.g. [Length] x [Height] = [Area] (where [x] are now a local variables).
This is NOT in the spirit of LabVIEW! In LabVIEW, the wire itself is the variable. Controls and indicators are just user interface access ports to the data, they contain their own data copies and are read or updated whenever dataflow might service them. Local variables are just secondary access points to the same controls or indicators.
Lets look at a (slightly flawed) analogy: I need to give you a CD with my LabVIEW program. I can (1) hand it to you directly (=wire) or I can (2) drop it off at the front desk (=front panel ) and you can pick it up later (local variable). As you can see, case (1) is more efficient and easier to debug. We both immediately know if the transaction succeeded. Case (2) could have a race condition, e.g. what happens if you try to pick it up before I had a chance to drop it off?
Local variables should be used sparingly. There are two main uses:
(1) Sometimes, it is required to either read from indicators or write to controls programmatically. This could be to initialize controls with a set of default values or similar.
(2) Exchanging data between two independent parallel processes in the same VI. For example to stop all while loops with a single control.
Anything that can be done with a wire should be done with a wire. If a wire is not sufficient, a shift register might do the trick. Local variables should only be used as a last resort.
Remember: Always go with the dataflow!

Problem using local variable in event loop

I have a state machine from which I want to monitor various controls, including "Start" and "Stop" buttons. Not every state needs to monitor the controls. At present, most states run timed loops. In the first state that reads the front panel, I have an Event structure (inside a While loop) that monitors the various controls' Change Value events. For numeric controls, I update variables (in shift registers) as needed. The "Start" button is used to end the While loop controlling the Event structure, allowing the State to exit to the next state.
My problem comes in subsequent states that employ this same idea. Here, I put a Local Variable bound to the Start button and use the same code, but it frequently happens that when I enter this particular state, I cannot "turn on" the control -- I push the button, but it stays off. Curiously, if it was On when I enter, I can turn it off, but then I'm stuck not being able to turn it on.
I mocked up a very simply routine that illustrates this. There are two sequences (corresponding to the two states). Both use an Event loop with a local variable bound to my Stop button (really this is an LED control with custom colors). I've deliberately moved the "initialization" (the declaration of the control in the block diagram) out of the Event loops -- putting it inside the first loop modifies the behavior in another strange way.
Here's my thinking on how I would expect this to work: The code outside Event Loop 1 should have little effect. Assume the Stop button is initially Off. You will "sit" in Event Loop 1 until you push the Stop button, changing its value to True; this value will be passed out of the Event case and cause the first While loop to exit. You now enter the second sequence. As I understand the Exit tunnel, it defaults to "False", so I'd expect to stay in the second Event loop until I turn the Stop button from On to Off, which will pass out a False, and keep me in the While for one more button push. However, this doesn't happen -- I immediately exit, as though the "True" value of the Stop local variable is being seen and recognized by the Event loop (even though it hasn't changed, at least not in the context of this second loop).
An even more curious thing occurs if I start this routine with the Stop button turned on. Now I start in my Event loop waiting for a change, but this time the change will be from On to Off, which won't cause an exit from the frame. This will be reflected by having the While loop count increment. We should now be in the state of the example above, i.e. in an Event loop waiting for the control to be pushed again, and turned On. However, clicking the control has no effect -- I cannot get it to "turn on".
Where am I going astray in my thinking? What is it about this method of doing things that violates the Labview paradigm? As far as I can tell, what I'm doing is "legal", and I don't see the flaw in my reasoning, above (of course not -- otherwise I'd have fixed it myself!). Note that because I'm using local variables inside Event loops (and I'm doing this because there are two places in my code where I want to do such testing), the Stop control is not latching (as required). Is there something that gets triggered/set when one reads a latched control? Do I need to do this "manually" using my local variable?
I'll try to attach the simple VI that illustrates this behavior.
Bob Schor
Attachments:
Simple Stop Conundrum.vi ‏14 KB

altenbach wrote:
Ravens Fan wrote:
NEVER have multiple event structures that share the same events.
Actually, that's OK. NOT OK is having multiple event structures in the same sequence structure.
See also: http://forums.ni.com/ni/board/message?board.id=170&message.id=278981#M278981
That's interesting. I had always thought I read more messages discouraging such a thing rather than saying it was okay. Your link lead me to another thread with this message. http://forums.ni.com/ni/board/message?board.id=170&message.id=245793#M245793. Now that thread was mainly concentrating on registered user events which would be a different, but related animal.
So if you have 2 event structures they each have their own event queue? So if you have a common event, one structure pulls it off its event queue and it does not affect the other structure's event queue? I guess the inherent problem with this particular VI was that the second event structure locked the front panel. Since the code never got to that 2nd event structure because the first loop never stopped because the change was from true to false. After reading your post and the others, I did some experimentation and turned off the Lock front panel on the 2nd structure, and that prevented the lockup of the program.
Overall, the example VI still shows problems with the architecture and I think your answer should put the original poster on the right track. I think as a rule I would probably never put the same event in multiple structures, I feel there are better ways to communicate the same event between different parts of a program, but I learned something by reading your reply and about how the event structures work in the background. Thanks.

How to avoid "The local variable ___ is never read" warnings

If you create an instance of a class using something like:
MyClass myClassInstance = new MyClass(param1, param2, ...);
And everything you require this class to do is done from within it's constructor then you always get a warning saying "The local variable myClassInstance is never read" with the class you're making this initialization from.
Is there a good practice technique to avoid these warnings?
On a large project this type of warning can become numerous and it would be cleaner to avoid them.
Thanks

TimThe.., I disagree about the result of a bad design
comment. In simple cases it can be beneficial to
only require an object's constructor, then that
object's actions are self contained and its methods
can then be called from its own constructor. In the
right situations this can help to loosen coupling
between classes and increase encapsulation.I disagree with that. If your code depends on behaviour that is carried out by a constructor, you have a dependency on a concrete class, which is a nice quick way to tightly couple classes. You'd achieve looser coupling if the desired behaviour was inside a method, which was in turn declared on an interface

Local variable files is never read

How do i fix an error that reads "The local variable files is never read"?

It's a warning, not an error. Your code will still compile.
You fix it by either getting rid of that variable, or using it. What's the point of having a variable if you never read its value?

How to use local variable in member formula?

Hi Expert,
We would like to use a {local variable} in a member formula, so that it can pick up the prompt from webform upon save. Would like to know if it is possible to do? If so, what is the correct syntax?
We attempted to use brace {scenario}, blacket [scenario], blacket with quote ["scenario"]. None of these work.
We are using 11.1.2.1 version, EPMA, Hyperion Planning.
Thanks in advance for your help!

One other pointer. Where did you define your variable? Hopefully you went into Calc Manager and selected <Tools>, <Variables>. From there, navigate to your application or database. Right-click on your application or database and select "New". In the bottom panel, you'll need to select your Variable Type. Make sure you select "Member", and not "Members". You cannot pass "Members" (plural) to a web input form. Also, if you want to define a variable for a custom dimension, you'll need to do it at the database level. Standard dimension member variables can be defined at the app level. (Not sure why this is the case, especially when my custom dimension exists in all plan types . . . . )
Anyway, hope this helps,
- Jake

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)

MacAir - error message "This version of itunes has not been correctly localized for this language. Please run the english version" Saw other answers for windows users, I have a MacAir. never used any other language but English

Trying to open iTunes - get an error message saying "This version of itunes has not been correctly localized for this language. Please run the english version" Saw other answers for windows users, I have a MacAir. never used any other language but English so I have no clue what the problem is. I just want to update my phone and back it up.

Let's try a repair install of iTunes.
Restart the PC first.
If you're using Vista or 7, now head into your Uninstall a program control panel, select "iTunes" and then click "Repair".
If you're using XP, head into your Add or Remove Programs control panel, select "iTunes", and click "Change". Select "Repair" and click "Next" as per the following screenshot:
Can you launch your iTunes now?

How can I use local variable in LabVIEW-Action?

Hi All!
There is local variable (for example "MyVariable") in local scope of project. There is Action-step, created by LabVIEW. One of input terminals step is "Sequence Context".
How can I access to MyVariable by Sequence Context? Unbundle? It does't work.
Thank you.

On the TestStand palette there is a VI called TestStand - Get Property Value.vi. Use that. Attached is an image showing how to use it. The trick is making it produce the correct data type. Do that by right clicking on the VI and selecting Select Type. Then you can choose the type. I think in LV 2010 and TS 2010 it is a polymorphic VI and you can just change it. I wrote an example here for Chaz: http://forums.ni.com/t5/NI-TestStand/How-to-execute-two-steps-in-parallel/td-p/1449874
It's the second example that's attached.
Hope this helps,
jigg
CTA, CLA
teststandhelp.com
~Will work for kudos and/or BBQ~
Attachments:
AccessLocalVar.JPG ‏67 KB

Local variable is never used

Similar Messages

Maybe you are looking for