Variable Properties

Hi All,
Is there a place where we can go and see who created a certain variable and last changed as we can see the query properties?
Thanks
GMS

Go to the RSZGLOBV table.
Thanks,
Jeff

Similar Messages

In the shared variable properties box, when enabling aliasing, what is the difference between binding to a project variable vs. to a psp url

In the shared variable properties box, specifically with regard to a the target being an rt target, when enabling aliasing, what is the difference between binding to a project variable vs. to a psp url?

The difference is in the type of variable you are binding it to. A project variable is a variable that lives within the specific project in which it was created. A PSP URL is an address using the Publish-Subscribe Protocol (PSP). You can learn more about PSP URLs here: http://zone.ni.com/reference/en-XX/help/371361G-01/lvconcepts/using_datasocket_technology/#Specifyin...
PSP URLs will enable it to communicate between different machines and also between projects which may or may not be open. The project variable will exist within the project.
Julian R.
Applications Engineer
National Instruments

Where can I find the "Shared Variable Properties" VI to be used in my program for configuring SV remotely?

I was using the "configure Alarms" and "configure Logging" VIs to design two user interfaces to make use of these VIs when I came across a problem. In both VIs you can enable logging of alarms. So which one is valid? Which one has priority? Then I looked at the "Shared Variable Properties" built into the project explorer. Now I realize that I am spending all of this time redesigning this properties dialog (which also has two options of enabling logging of alarms (on the Alarms tab to the far right side as well as on the Logging tab). So now my question is, how do I access this "Shared Variable Properties" dialog through my program (Note: this would be on a different machine than where the shared variables are set up. The point is to configure shared variables remotely).
Thanks
Matt

Here is a VI I re-created and posted for all. I'm not sure why NI doesn't provide their VI to the developer. The only thing I can't figure out is that when reading in the "Ack Type" into a variable, it generates an error. It will work if you go into "project explorer" and right click on the library with the shared variable and "deploy" but eventually stops working. I have tried using the "undeploy library" and "deploy library" to see if this would be a work around but had no success.
Just pipe the path of the shared variable into the vi.
Mattk
Attachments:
Shared Variable Properties.vi ‏95 KB

Can't open/access Shared Variable Properties Dalog Box

I've just upgraded to LV 8.6 from 8.5. Now I can't open up the Shared Variable Properties Dialog Box. In the Project Explorer, I expand the shared variable library, select the shared variable, right-click on it to get the pop-up menu, select Properties, nothing happens. The same is true when I right-click on the shared variable library or My Computer and select New>>Variable.
On another computer that I upgraded to LV 8.6, I can do the same things and get the dialog box, albeit it looks different in 8.6 than it did in 8.5.
There were no errors reported in upgrading these computers. Any ideas as to what is wrong?

I've tried re-installing LV 8.6 from the DVDs sent to me. I get the following errors:
Error 1335. the cabinet file 'mib.cab' required for this installation is corrupt and cannot be used. This could indicate a network error , an error reading from the CD-ROM, or a problem with this package. - I responded with 'ignore'
The NI Assistant Framework LabVIEW Code Generator 8.5 installaion has failed with the following error.
Internal Error 2350.
Continue? - I responded with 'yes'
LabView installs but I still can't get access to the dialog box.

Shared Variable Properties and DSC

Is there a way to assign engineering units to a shared variable as a
configuration parameter? This should be on the "Scaling" page of
the shared variable properties. It seems this is a logical and
convenient place to track units. Assigning units programmatically
using the Scaling:Units property is awkward (to say the least).
On similar lines, why aren't shared variable properties automatically
saved to the DSC historical database? Every trace should have a
set of information that exposes ALL the shared variable properties that
created it. Take something like engineering units for
example: then you would know what kind of historical trace you
are looking at! This seems so basic I can't imagine why it was
missed.
Unless I missed something -- please enlighten me.
Regards,
David Moerman
TruView Technology Integration Ltd.

Hello David,
You are correct in that the units property is not exposed on the
Scaling page of hte Shared Variable properties dialog, and it sounds
like you are already well aware of the existing method to access this
property through the property node interface. As you have also
discovered, the Citadel database that we use with DSC does not have a
built-in provision for storing metadata about the shared variable from
which a trace originates. You can emulate this with, for example, an
array of strings which is also logged to the database, with each string
containing the metadata for a particular trace.
Since it seems like having these features would benefit you, I
encourage you to let our DSC development group know your needs by
filling out product feedback, accessible on our site at
http://www.ni.com/contact . This will send a feature request
directly to the appropriate R & D group, who reads and evaluates
every suggestion made. This is your most direct way to let us know
what features would best meet your needs.
Cheers,
Matt Pollock
National Instruments

Variable properties changes...?

Hi Experts,
Is there any option to change the variable properties declared at query designer ?

HI,
you can change it directly in table RSZGLOBV, but i will not recommend it when you don´t sure what you are doing.
If you have to do it for one variable only, it´s better to delete it and recreate it.
Regards
Marcus

Shared Variables - Properties

Hello,
I have a couple of questions about properties of Shared Variables (SV). They can be configured either by using the dialog box (right-click on SV -> Properties), or programmatically via the "SharedVariableIO" property node. Have a look at the NI-Examples to see how SV can be created programmatically by using the DSC module.
1) The dialog box offers a property "Variable Type" which can be "Network-published", "Single-Process" or "Time-Triggered". The "SharedVariableIO" property node gives no access to this property. Does anybody know why? The same question can be rephrased: How can I create a "Single-Process" SV programmatically?
2) The "SharedVariableIO" property node has two items, "Network.OnScan" and "Network.ConnectionType", which have no direct correspondance to any of the properties available in the dialog box. What is the exact meaning of those properties? The on-line help isn't of much use here...
3) Mutliple SV can be edited by using the Multiple Variable Editor (Tools->Shared Varaible->Multiple Variable Editor). A cool feature is the import/export of CSV-files. I am interested in programmatically creating SVs from the information stored in such a CSV-file. Reading the file is no problem, but connecting the file entries to the properties of the "SharedVariableIO" property node would be quite some job. In principle NI has already solved that within the Multiple Variable Editor. I guess there is a bunch of VIs somewhere below "....Program Files/NI/.../vi.lib that do exactly this thing. Does anybody know, if these (which ones?) are available for public use?
Regards,
Dietrich

dietrich wrote:
1) The dialog box offers a property "Variable Type" which can be "Network-published", "Single-Process" or "Time-Triggered". The "SharedVariableIO" property node gives no access to this property. Does anybody know why? The same question can be rephrased: How can I create a "Single-Process" SV programmatically?
You can't. The single-process shared variable is an old style LabVIEW global placed under the shared variable abstraction. There is currently no way to create those on the fly. Time-triggered also cannot be created programmatically. I confess I don't know enough about them to know the reason why.
dietrich wrote:
2) The "SharedVariableIO" property node has two items, "Network.OnScan" and "Network.ConnectionType", which have no direct correspondance to any of the properties available in the dialog box. What is the exact meaning of those properties? The on-line help isn't of much use here...
Network.On Scan = read/write hardware? - this allows you to programmatically control when you are reading from or writing to configured hardware.
Network.ConnectionType = connect to hardware even when no one is viewing me? - this has 2 choices, UpFront & OnDemand, UpFront means that the variable will be connected to hardware even when no one is connected to the variable. This is useful when you want to reserve hardware or when logging is enabled. OnDemand means that you disconnect from hardware whenever no one is reading the variable.
dietrich wrote:
3) Mutliple SV can be edited by using the Multiple Variable Editor (Tools->Shared Varaible->Multiple Variable Editor). A cool feature is the import/export of CSV-files. I am interested in programmatically creating SVs from the information stored in such a CSV-file. Reading the file is no problem, but connecting the file entries to the properties of the "SharedVariableIO" property node would be quite some job. In principle NI has already solved that within the Multiple Variable Editor. I guess there is a bunch of VIs somewhere below "....Program Files/NI/.../vi.lib that do exactly this thing. Does anybody know, if these (which ones?) are available for public use?
I would advise against using any of these. National Instruments can change, or remove, those underlying files at any time as a result of modifications to the MVE. That could cause issues for any code using those sub-VIs.
Regards,
Robert

Viewing variable properties with JSP 2.0

Hi,
I just started using JSP 2.0. How can I get NitroX for JSP to help me see properties for variables.
For example:
<td><input type="text" name="company_name" value="${model.company_name}" size="25"></td>
[/code:1:a2d2041db4]
I want to be able to see all properties for model. I've seen this work with JSTL - can this work with JSP 2.0 too?
WILL

Yes, this should work for any tag in a JSP 2.0 app.
NitroX recognizes that the JSP version by looking into the web.xml servlet version.
For JSP 2.0, web.xml should start with:
<web-app xmlns="http://java.sun.com/xml/ns/j2ee"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee/webapp_2_4.xsd"
version="2.4">
Is it not working for you?
M7 Support

Environment Variable Properties file

Using log4j and creating a log4j properties file. "log4j.properties".. How do I specify the home directory in the properties file ? On command line I might use $HOME but I don't think that works in a properties file. I'd like any log file generated to be placed in a directory under the home directory. So the log4j.properties file needs to contain the line..
log4j.appender.A2.File=$HOME/foo/log.txt
But I'm seeing FNFE set file failed...

Or, do what I should have done in the first place:
read the API documentation for PropertyConfigurator
where it says
"All option values admit variable substitution. The
syntax of variable substitution is similar to that of
Unix shells. The string between an opening "${" and
closing "}" is interpreted as a key. The value of the
substituted variable can be defined as a system
property or in the configuration file itself. The
value of the key is first searched in the system
properties, and if not found there, it is then
searched in the configuration file being parsed. The
corresponding value replaces the ${variableName}
sequence. For example, if java.home system property
is set to /home/xyz, then every occurrence of the
sequence ${java.home} will be interpreted as
/home/xyz."
So your guess was close.Good to know I can do that with all variable names. I should have know to look at the API too. Thanks again :o)

Setting dynamic variable properties

I asked this down in the Actionscript 3.0 forum, but maybe it
was the wrong place... I really need some help on this to finish
off an application we are creating.
Thanks!
If I create the textareas dynamically how do I loop through
them later on to set their properties?
so basically I have some textareas with ids of
myText_0
myText_1
myText_2
myText_3
(etc)
and I have a loop of
for (var x:int=0; x<4; x++)
// insert AS3 code here
inside the loop I need to be able to say something like:
myText_x.height = 50;
myText_x.text = "Hello " + x.toString();

Thanks ntsiii the bracket notation didn't work the way you
put it, but if it is written as:
this["myText_" + x].height = 50;
this["myText_" + x].text = "Hello " + x.toString();
And to think three days ago I put had it with parens instead
of brackets (argh).

Table Variable properties/ uses?

Dear Readers,
I wanted to know how table variable works. Is it like a temp table where we cannot retrieve it after the connection is dropped or is it retrievable?
DECLARE @MyTable TABLE
id INT NOT NULL,
fname VARCHAR(20)
I read somewhere that we can use it in a stored procedure, that means it must be saved somewhere in order to be retrieved?
Thanks for clarifying the concept/issue.
Regards
SQL 75

Nope its like a local variable but of table type
ie its scope is only within the batch where you created it
see this example
declare @t table
v varchar(100)
insert @t
values('uyty1231314'),('qweq2142423uyiy')
--here you will get result
select *
from @t
--end of batch table variable becomes out of scope and destroyed
GO
--this will throw error as table variable doesnt exist any more
select *
from @t
Please Mark This As Answer if it solved your issue
Please Mark This As Helpful if it helps to solve your issue
Visakh
My MSDN Page
My Personal Blog
My Facebook Page

Peculiar behavior of Shared Variable RT FIFO

I'm trying to "leverage" the enhanced TCP/IP and Shared Variable properties of LabView 8.5. My application involves (among other things) doing continuous sampling (16 channels, 1KHz/channel) using 6-year-old PXIs (Pentium III) and streaming data to the host. I developed a small test routine that was more than capable of handling this data rate, even when I had the host put a 20msec wait between attending to the PXI (to simulate other processing on the host). To do this, I enabled the "RT FIFO" property of the Shared Variable (which was an array of 16 I16 integers) and specified a buffer size of 50 (that's 50 arrays). Key to making this work was figuring out the "error codes" associated with the SV RT FIFO, particularly the one that says the FIFO is empty (so don't save the "non-data" that is present).
Flush with success, I started developing a more realistic routine that involves rather more traffic between Host and Remote, including the passing back and forth of "event" data. These include, among other things, "state variables" to enable both host and remote to run state machines that stay "in sync"; in addition, the PXI also acquires digital data (button pushes, etc.) which are other "events" to be sent to the Host and streamed to disk. I developed the dual state-machine model without including the "analog data" machine, just to get the design of the Host/Remote system down and deal with exchanging digital data through other Shared Variables. Along the way, I decided to make these also use an RT FIFO, as I didn't want to "miss" any data. One problem I had noticed when using Shared Variables is the difficulty of telling "is this new?", i.e. is the variable present one that has been already read (and processed) or something that needs processing. I ended up adopting something of a kludge for the events by including an incrementing "event ID" that could be tested to see if it was "new".
Today, I put the two routines together by adding the "generate 16-channels of integer data at 1 KHz and send it to the Host via the Shared Variable" code to my existing Host/Remote state machine. I used exactly the same logic I'd previously employed to monitor the RT FIFO associated with this Shared Variable (basically, the Host reads the SV, then looks at the error code -- a value of -2220 means "Shared Variable FIFO Read Buffer Empty", so the value you just read is an "old" value, so throw it away). Very sad -- my code threw EVERYTHING away! No matter how slowly the Host ran, the indicator always said that the Shared Variable FIFO Read Buffer was empty! This wasn't true -- if I ignored the flag, and saved anyway, I saw reasonable-looking data (I was generating a sinusoid, and I saw numbers going up and down). The trouble was that I read many more points than were actually generated, since I read the same values multiple times!
Looking at the code, the error line coming into the Shared Variable (before it was read) was -2220, and it remained so after it was read. How could this be? One possibility is that my other Shared Variables were mucking up the error line, but I would have thought that the SV Engine handling reading my "analog data" SV would have set the error line appropriately for my variable. On a hunch, I turned of the RT FIFO on the two Event shared variables, and wouldn't you know, this more-or-less fixed it!
But why? What is the point of having a shared variable "attached" to an error line and having it return "Shared Variable FIFO Read Buffer Empty" if it doesn't apply to its own Read Buffer? This seems to me to be a very serious bug that renders this extremely useful feature almost worthless (certainly mega-frustrating). The beauty of the new Shared Variable structure and the new code in Version 8.5 is that it does seem to allow better and faster communication in real-time using TCP/IP, so we can devote the PXI to "real-time" chores (data acquisition, perhaps stimulus generation) and let the PC handle data streaming, displays, controls, etc.
Has anyone been successful in developing a data-streaming application using shared variables between a PXI and and PC, particularly one with multiple real-time streams (such as mine, where I have an analog stream from the PXI at 16 * 1KHz, a digital stream from the PXI at irregular intervalus, but possibly up to 300 Hz, and "control" information going between PC and PXI to keep them in step)? Note that I'm attempting to "modernize" some Version 7 code that (in the absence of a good communication mechanism) is something of a nightmare, with data being kept in PXI memory, written on occasion to the PXI hard drive (!), and then eventually being written up to the PC; in addition, because the data "stayed" on the PXI, we split the signal and ran a second A/D board in the PC just so we could "see" the signal and create a display. How much better to get the PXI to send the data to the PC, which can sock it away and take samples from the data stream to display as they fly by on their way to the hard drive!
But I need to get Shared Variables (or something similar) working more "understandably" first ...
Bob Schor

Bob,
The error lines passed into and out of functions are just just clusters with a status boolean, an error code, and an error string, and are not "attached" to a particular function as you describe in your post. Most functions have an error in input and an error out output, and most functions will simply do nothing except pass through the error cluster if the error in status is True (to verify this for yourself, double click on a function such as a DAQmx Read or Write and look at the block diagram. If there is an error passed in, no read/write occurs). This helps prevent unwanted code from executing when an error does arise in your program. By wiring the error cluster from your other shared variables to your analog data variable, you're essentially telling LabVIEW that these functions are related and that your analog data variable depends requires that the other shared variables are functioning properly. The error wire is a great way to enforce the flow of your program, but you must always consider how it will affect other functions if an error does arise.
Anyways, it's great that you have things more or less working at the moment. Keep us all updated!

DSC Saving Shared Variables to Library

I'm guessing this is a bug (LV/DSC 2009 SP1), but I wanted to see if anyone else had experienced this or had a workaround.
I'd like to make changes to the logging state of some shared variables programmatically and be able to save the changes. When I use the SharedVariablestoLib.vi function on a simple test library it works. However when I use it on my actual library I get the following (testing vi I'm using is Untitled 2):
Error Code 1
Invoke Node in PRC_SVsToLib.vi->PRC_DumpSharedVariables.vi->NI_DSC.lvlibharedVariablesToLib.vi->Untitled 2
Possible reason(s):
LabVIEW: An input parameter is invalid. For example if the input is a path, the path might contain a character not allowed by the OS such as ? or @.
=========================
NI-488: Command requires GPIB Controller to be Controller-In-Charge.
I think the culprit is that my library has variables organized into virtual folders. Any thoughts?
Thanks,
Kyle
CLD using LV, DSC 8.5-2009, RT 8.5
Ghoti!

I can pretty well cause the problem with virtual folders. I have attached the vi I'm using to change the logging state and save the changes as well as the two libraries I used for testing purposes.
What I did to test:
-Disabled logging on both variables in both libraries.
-Saved, undeployed, and redeployed both libraries.
-Ran my log enabling vi on each library. It ran on Test 2 (no folders) fine. On Test 3 (includes a folder) it threw the same error as above.
-At this point I tested and both libraries were logging both variables.
-Looking at the variable properties in the project, both Test 2 variables showed Enable Logging checked. Neither Test 3 variable did.
-Exited the project. Test 3 had unsaved changes so I saved it.
-Re-opened the project and examined the variables, both Test 2 variables showed Enable Logging as before. In Test3 the root variable showed Enable Logging but the variable in the folder did not.
-Undeployed and redeployed both libraries.
-Confirmed that both Test 2 variables and only the root Test 3 variable were logging.
CLD using LV, DSC 8.5-2009, RT 8.5
Ghoti!
Attachments:
Programmatic Log Change.vi ‏17 KB
Test 2 Library.lvlib ‏5 KB
Test 3 Library.lvlib ‏4 KB

Weird delay reading shared variables

Hello,
I'm working on a project were I'm monitoring some prodution lines. I'm using DSC module's OPC server to connect to PLCs on the production line and I've created bound variables on my labview project of the PLC's tags.
On my project I have one main VI were I show information about the production lines and were I can access several subVIs were I show other information about those lines. Then I have a VI that is running in background were I'm reading about 50 shared variables from the PLC and where I'm registering some data in a MySQL database, datalogging data on the Citadel database and registering alarms.
The problem I'm having is that on the VI that runs in background I noticed a delay reading the variables that are reading containers weights from the production line. It seems that all the other shared variables don't suffer any delay, only the weight variables start having some delay when the values are increasing. It also seems like that, when I'm only running that VI alone, without running the main VI, there isn't any kind of delay. I'm reading the shared variables as shared variable nodes.
Can anybody help me understand what's happening and how can I fix this delay? The VI that runs in background is time critical and a weird delay like that messes up my data.
Solved!
Go to Solution.

Hi Mateus23,
The shared variable has various buffering capabilites, including integration with the Real-Time FIFO feature in LabVIEW Real-Time.
I guess that the buffering settings are causing the unexpected behavior.
Check these resources:
Buffered Network-Published Shared Variables (whitepaper)
Shared Variables Properties Dialog
- Network Page
- Real-Time FIFO Page
~~

Averages in a query using a variable with Replacement Path: Replacement wit

I have two queries. Query1 has a handful of characteristics, one of which is used in a formula where I used replacement path in order to be able to use it in some calculated key figures. I also have a couple of key figures that are not calculated and they are averages.
The second query has a characteristic value variable that is replaced with the first query. This replacement value variable is placed into the filter section and the characteristic itself is placed in the rows section. I am bringing in the same calculated key figures that were in my first query as well as the normal key figures that are averages.
The issue I am having is the regular key figures that I am bringing in are coming in summed up instead of as averages. Is it possible to bring the normal key figures in Query1 as averages into Query2?
There is more information in the thread below if you need more background.
[Replacement Path and Aggregation;
PS - I am using 7.0.

Hi Satyakam,
In the text variable properties make sure that in the replacment path you have chosen "Text" to appear date as per user setting . Other wise as in your case it must be set to "Key" which always shows in the format YYYYMMDD.
Hope that helps.
Regards
Mr Kapadia

Variable Properties

Similar Messages

Maybe you are looking for