Create local variable in Vendor mode

Hi everybody,
I´m using B1if 1.11.2 in Vendor mode.
When trying to create a local variable I´m getting the following error message:
!http://scn.sap.com/servlet/JiveServlet/downloadImage/655879/pastedImage_1.png|height=56|style=width: 287px; height: 55.7344px;|alt=|width=287|class=jiveImage|src=http://scn.sap.com/servlet/JiveServlet/downloadImage/655879/pastedImage_1.png!
But the scenario is not activated. I have cleared the setup, but I´m still getting the same error.
BTW. I can edit the local variables in customer mode ...
Any suggestions?
Thanks in advance.
greetings

Hi Matthias,
I am not sure about the exact problem - at least I don't remember it (the version you are using is 3 years old)...
...at that time I am sure I didn't use local variables anyway.
...would it be an option to upgrade (only integration framework?) to a newer version?
Questions:
...is customer mode / vendor mode the only difference?
I.e. the namespace is the same?
Did you create the step in Vendor mode - or Customer mode?
Regards,
Frank

Similar Messages

Create local variable using labview scripting

I am trying to use labview scripting to create a control and a local variable for that control. I want both the local variable and the control contained inside a case structure. My problems are twofold:
1. the local variable is left blank/unnamed
2. the local variable is wired outside of the case structure, even though I set it's owner to be the same as the owner for the control (which is placed inside the case structure).
The flat panel is there because I thought that my problem might be a result of the local var being created before the actual control, so this just forces the control to be created first. The other thing I wonder about is the VI Object Class for the local variable. I have tried 'Node' and Control->Boolean, but neither worked.
I have attached a jpg of the code I'm talking about. The picture on thetop is of the code in question. The picture on the bottom is of the resulting code that's created....
Can anyone offer any help?
Thank you...
Attachments:
vi_scripting_lv.png ‏95 KB

The reason your locals aren't tied to a control, is because you didn't make a local variable from any control. Use the Boolean reference wire and wire it to an Invoke Node and select the Create >> Local Variable method.
Unofficial Forum Rules and Guidelines - Hooovahh - LabVIEW Overlord
If 10 out of 10 experts in any field say something is bad, you should probably take their opinion seriously.

Create Local Variable in Custom.pll

Hi,
I want to create and calling local variable in custom.pll. As i know, we can create local variable with personalization form. but i didn't find the way to create local variable in custom.pll.
Is there any way to create local variable in custom.pll and calling that variable ?
Thanks

I think what you want is to create a GLOBAL variable, a LOCAL variable would be available to the Procedure/Function being executed. But to create the local variable, you add it between the Function/Procedure declaration and the begin
PROCEDURE abc(p_input VARCHAR2);
v_count NUMBER := 0;
BEGIN
END;
A GLOBAL reaches out past the execution of the proc defined in CUSTOM.pll. You can simply type GLOBAL.<var_name> := <value>.
BEGIN
GLOBAL.xx_count := 0;
END;
Though I like the ability Personalizations give you of using Init Value vs. Value, Init Value will assign a value if the variable does not exist ... and creates it. Value just assigns a value.
Some say you have do a COPY(value, NAME_IN('variable name')) instad of GLOBAL.<variable_name>, I have never had to use this.

Programatically create local variable in TestStand

Can somebody please explain the process of creating a local variable programatically? I have searched the forums but haven't found what I am looking for yet.
I have an array of unknown size. I use a foreach loop to step through the array and grab the data that I need. I need to put that string in a Local String Variable that I can use later.
Any help is much appreciated.
Matt
Solved!
Go to Solution.

That did exactly what I wanted it to do thank you. Now I want to take it one step further...
I have a local variable array called RI_Equipment that is of an unknown size. The array contains a container data. I want to create a variable of name ri_nameField+"_ID" and then set the value of that variable to what is contained in RI_Equipment[x].ri_IDField. Hope that all makes sense. Below is the statement I have in TestStand however TS tells me that this will cause a run-time error. What am I doing wrong?
Locals.NewSubProperty(Locals.RI_Equipment[Locals.loopcounter].ri_nameField+"_ID",PropValType_String,False,"",0) = Locals.RI_Equipment[Locals.loopcounter].ri_IDField
Matt

Create local variable by an expression

Hi!
I searched the discussion forum, but I couldn't find any information about how to create a local variable using an expression.
The TestStand version I'm using is 4.0.
lets say, if I wanted to create a variable called "foo" as integer. What will the expression be?
The expression will be called from the step-type "Statement".
Thanks
Best regards
Selvakumar

Locals.SetValNumber("Foo", 1, 0) will create a variable named Locals.Foo, and initialize it with a value of 0.
The variable will only exist for the lifetime of the execution.
Allen P.
NI

What is the need to break a VI when a local variable in read mode is unconnected?

What's wrong with an unconnected "read" local variable?
A control terminal (or indicator terminal for that matter) can exist on the BD without issues!
Use case: When I create a new control, I may want to drop a few local variables in different cases of an event structure to be connected later.
If in addition, I am planning to create a few controls, to be used in several cases, this is quicker than dealing with each case one at a time.
I'll just grab the terminal, create a local variable for it, copy it and then paste it in all the cases I need it in.
Then repeat with another control and finally, deal with the bunch of local variables in each case later on.
I would like to be able to run the VI without having to treat all cases, which I can't right nowm because the VI is broken as long as there remains at least one unconnected "read" local variable.
Again, I cannot fathom why the compiler would be unhappy with a "read" local variable unconnected to anything. Generate a copy of the data if you wish, don't use it, that's all!
I can see the problem with a "write" local variable, although I would wish an unconnected "write" local variable would be simply ignored. And probably the same should be done with an unconnected local variable: no copy should be generated.
Of course, a warning would be useful.

Then put it on the IE (assuming it's not already there) and see how it fares. Personally, I think I prefer the current situation for safety (i.e don't forget to use the code you actually put in), but I wouldn't be terribly broken up if it behaved like you want.
Try to take over the world!

Is there an easier way to create a local variable?

I want to create a local variable, but I don't wont to have to find the terminal first and then use the option create-local variable. Is there a way to make a copy of an existing local variable? If I use the CTRL-C and CTRL-V option another terminal is created too.

> Great! That was exactly what I wanted. It even works if more than one
> variable is selected.
This may not apply in your situation, but I feel obliged to make this
warning anytime I see this sort of posting. If you find yourself making
too many local variables, it is worth checking to see if you are doing
things the best way.
If you are using the locals for communication between parallel loops or
for UI -- writing to controls, then keep trucking. That is why they
were added. If you are using them as storage locations, like variables
in BASIC or C, or to avoid wires, then you should definitely read the
devzone article about race conditions and the usage of globals/locals.
If not, you will probably find yourself with some monument
al debugging
sessions later on.
If you have questions, fire away.
Greg McKaskle

Create New Variable for COPA Drilldown Reports in KE3E

Hi,
How can we create a formula variable for COPA Drill down reports in KE3E? In standard global variables formula variable is not avaiable, I need to create a formula variables like ...from period, to period, last fiscal year and next fiscal year..
While creating report in KE31/KE35 trying create local variables, but it doesn't.
Can any body advise how can we create a new variables for "from period, to period, last fiscal year and next fiscal year.."
Thanks
VS Rao

Hi Rao
For Period (From &To)
1. KE3E
2. Type of Var = Char Value
    Enter variable name, say, ZPERIOD
    Field Name = PERDE
    Replacement type = Entry
    Enter Description
    Parameter/selectop = Selection Option
For Fiscal Year
    Type of Var = Char Value
    Enter variable name, say, ZGJAHR
    Field Name = GJAHR
    Replacement type = Entry
    Enter Description
    Parameter/selectop = Parameter
For Next and Last Fiscal Year
When you define your form in KE34/KE35
Use the variable ZGJAHR in your report
In the column for Next Year, Enter "ZGJAHR+1" as the local variable for GJAHR
In the Column for Last year, Enter "ZGJAHR-1" as the local variable for GJAHR
Regards
Ajay M

Local variable without frontpanel object

is there a possibility to create local variables without the need of a frontpanel object? I need zhem for program ccontrolontrol but don't want to show them to the user.
Thanks a lot,
greetings from Germany
Karin

Lynn, Marc, and "tbob",
Thanks for your replies. I detect the common theme of keeping my variables in bundles, but I'm not experienced enough to see how to apply this to my problem of communicating between parallel event handlers. If you have the time and patience, I have attached a very simple example of what goes on in my program.
I have three independent systems: a motion system that carries around a microscope and digital camera. Each system has its own event handler. The motion system responds to user commands to move the microscope around, the microscope handler responds to changes in focus, zoom, etc, and the camera event handler continuously snaps pictures to provide a "live" image.
But sometimes the loops need to talk to each other. For example, autofocusing is handled by the camera event handler, because it is based on image contrast, and that is the event handler that is acquiring the images. So that means the camera event handler should take over the microscope during auto focus. So the microscope event handler needs to be prevented from trying to get in on the act.
So here is what the example illustrates: some motion has just ended "normally". The timeout event in the motion system signals the camera system to perform an auto focus (and waits for the focus to complete before allowing any movement). The camera system signals the microscope system to perform a "stop" event, does the auto focus, releases the microscope from the stop event, and signals back to the motion loop that auto focus is done.
I, of course, thought this kind of thing was very clever! More experienced Labviewistas may have other opinions....
-Geoff
Attachments:
too many indicators.vi ‏24 KB

How to solve error using local variables?

I've created a sequence with a local variable.
But when I execute it, an error occurs since the first step (before the step where I manipulate the local variable).
The error code is something like:
Error in Evaluation. Syntax expression. Column [0-0]
It's interesting because it seems that once I've executed my sequence for the first time I can't create any other sequence where this error doesn't appear.

Pparo,
The problem does not occur under TS 1.0.3 on my system. However, I think we can get to the bottom of this.
When at a breakpoint in your sequence, if I type the expression "Locals.nls == 15-" in the TestStand watch window, I will get the message
Evaluation Failed: Syntax error in expression (Column 18-18)
I believe that this is the same type of error that you have encountered. Correct me if I am wrong.
The numbers after the word "Column" indicate where the error has occurred in the expression. In your case the error occurs at the beginning of an expression. The question still remains as to in which expression is error occurring.
Are you seeing this error reported in the watch window? If so, then you have typed the expression in the watch window.
If I copy the bad expression above into a the expression of a Statement step I get a run-time error of
An error occurred in the 'Statement' step of the 'MainSequence' sequence in 'Sequence File1'.
The post-expression for the step 'Statement' could not be evaluated.
Syntax error in expression.
Error Code: -17322
From what you report, the error appears to be located in your watch expression. When I executed your sequence with a breakpoint on the first step, I added the watch expression by selected the Context tab, expanding the Sequence Context tree view until I could see the nls variable, and then I dragged nls from the tree view to the watch window. This created the watch expression of Locals.nls. I also created the same watch expression by right clicking in the watch window, selecting Add Watch from the context menu, and selecting (or typing) Locals.nls. The expressions all evaluated to 24 without error.
This process has NOTHING to do with creating local variables. You asked if you are creating variables properly. There are only 2 ways to create variables in TestStand 1.0.3, neither of which you have described. The most common method is to select the Locals tab after opening your sequence (not during execution), right click in the right pane and add the variable of your choice. It seems like you did this correctly based on the sequence file you sent. The other method of creating variables is to do so programmatically. However, this is beyond the scope of this answer.
You ask a question about "the best way to create three constants in LabVIEW and pass them to a LabVIEW VI that is a step?" This implies to me that you want to create the strings within a VI called by one sequence step, and then use them in another VI called by a different sequence step. I would recommend taking a look at the example AccessingPropertiesAndVariables.seq that ships with TestStand. The first 3 VIs write values back to step properties, but could just as easily write them back to local variables. The 4th VI writes a file reference back to a TS local variable. The 5th and 6th step get the file reference from the TS local variable. You want to do something similar to the 4th and 5th VI, however, you want to send 3 strings to local TS variables, and then get them in the following VI. This will require using "TestStand - Set Property Value (String).vi" and "TestStand - Get Property Value (String).vi" which can be found in the TestStand function palette in LabVIEW. After reviewing this example you can then ask additional question. I recommend posting the question on a different thread since it is unrelated to your original question about the syntax error.

Using local variables

trying to use a simple local buffer to get an interger value and use it some where else. any help?

If you are using a state machine, here is another way to create local variables. Create a cluster with all local variables that you need. Wire into a shift register. Use Unbundle to get the value and Bundle to change the value. See code below:
Message Edited by tbob on 05-09-2007 11:58 AM
- tbob
Inventor of the WORM Global
Attachments:
Local.png ‏4 KB

Question about Local Variables (Multiple answers welcomed!)

A couple of questions about Local Variables
1. Programmers always say: “Do not abuse of Local Variables”. I’d like to know, when and where Local variable are most efficiently used?
2. If I have to create a couple of local variables, is there anyway to “clone” them without going through the repetitive “create/local variables” mouse click each time? (When I try to copy and paste, it creates a new variables instead of the one that I am trying to reproduce)
3. Which is faster in execution: Updating a variable through a) writing to property node/value or b) through local variable
Everyone’s input is welcomed, so if this question is already answered, please
feel free to add additional comments/answers!

1. Use Local Variables in user interface code and no where else. The only exception is using a local variable of a cluster output to define the datatype for a bundle by name node.
2. You can drag copy them then right click to get to a menu of all the currently defined controls and indicators on the VI.
3. B. The problem with A is that it forces a thread switch to the user interface thread--which can take time if you aren't already in it, and it's a very convoluted process under the hood. NI's advice never update indicator values through a property node unless you absolutely, positively can't figure out some other way of doing it.
Mike...
Certified Professional Instructor
Certified LabVIEW Architect
LabVIEW Champion
"... after all, He's not a tame lion..."
Be thinking ahead and mark your dance card for NI Week 2015 now: TS 6139 - Object Oriented First Steps

Labview local variables not always renamed

Hello,
I might be missing something, but it seems that sometimes the local variables in my VIs are not always updated when I rename the Front Panel control associated with it.
I have an example where I right click on the terminal of a control named "RxConfigTest", create local variable. The local variable that gets created is named with the old name "RxConfig1".
Have you ever seen that behavior? I'm using LV 7.1.1.
Thank you,
Mathieu

Hi,
Thanks for the response, but I was actually displaying the label. I know that this sounds like a newbie question, but I'm not.
I noticed that by closing and re-openning my VI after the rename, the variables were updated. It looks like a refresh that was not done. Even the local variable in the block diagram was not resized to the new text of the variable name.
I'll try to grab a screen shot if it happens again.

How can you create a local variable from a boolean control?

I want to create a local variable from a boolean control, but it says that boolean latch actions are incompatible with local variables, but I need a way to check this boolean control in two differents loops, how can I do it?

"Graci" schrieb im Newsbeitrag
news:[email protected]..
> I want to create a local variable from a boolean control, but it says
> that boolean latch actions are incompatible with local variables, but
> I need a way to check this boolean control in two differents loops,
> how can I do it?
Use global variables.
Compare them with a constant Boolean like F or T.
The result is true or false and then you can use it in a Cae-Loop.
Martin

How to create a local variable in bpel?

Hi,
In my bpel flow I need to call service based upon a pl/sql procedure multiple times. The procedure returns the results of a query in chunks and contains a boolean as an output parameter that tells me whether there are any more records that need to be fetched based upon which I will be calling the service again. I want to achieve this using a while loop. So for the while loop condition I am thinking of creating a local variable in the bpel process and assign it an initial value of false(). Then once the service is called I will set the value of this variable to the output boolean parameter returned by the procedure. So while the boolean is true the service will be called again.
My question is how can I create a local variable in bpel and assign it an initial value of false. Or is there any other way that this can be achieved?
Thanks!!

Hello! thanks for yr response.
I tried creating a new variable by defining a scope. But in the create variable window I cannot define a standalone variable of boolean type I need to pick up the type from an lov that brings up a list of all existing variable! so basically u are just mapping to an existing variable which in my case will not work because I will need to map to one of the elements of the output of the pl/sql procedure based service -- also this element itself is not exposed in the lov only the name "inputParameters" is displayed as the element --all the contents are not exposed.
Any suggestions?
Thanks!

Create local variable in Vendor mode

Similar Messages

Maybe you are looking for