Word property node:selection - Ref.Number is 0!

Hello
I am trying to set a word property in LabView. The problem is that the selection property node is giving me always a ref.number of 0 back!
Therefore I can not set anything due to an error which is generated afterwards. I am using the word version 2010 with the LabView 2012 SP1.
Does anybody know how to solve that? Is a registry key missing maybe? Attached is a demo-vi.
thanks in advance
Solved!
Go to Solution.
Attachments:
Word example.vi ‏10 KB

Code works OK for me. I open MS Word, type in some text, select some text, run your VI and it returns with no errors.
Of course though if I run it without MS Word open or without any text selected it returns 0.
Edit:
Actually as long as MS Word is open the VI runs OK (even with no selection)

Similar Messages

When i change the value of a combo box using a property node it displays the value not the item label

I am using a combo box as a select list for text serial commands. I have items like "engineering", "GUI", and "Scan" for the commands "MDE", "MDN", and MDS respectively which i have input as the corresponding value in the combo box. so for example the label "engineering" has the value "MDE" in the combo box items list. when the Vi starts it needs to read the current value MDE, MDN, or MDS and then i want it to display on the front panel the item text corresponding to that command value.
To do this i have tried to read the serial command, ie MDS and then wire that to a "value" property of a property node of the combo-box, but instead of displaying the corresponding item label, "Scan", it displays the value "MDS" on the front panel instead. i want the front panel to use the label text when choosing and displaying but the block diagram to use the serial commands. Can this be done with a combo box? I'm trying to use a combo box so i can keep it all text and avoid having to build a case statement to convert enums or rings from a numerical value to the text command.
The correct text value is wired to the value property and it does exist in the combo-box. I have unchecked "values match items" and selected to not allow undefined values.

Don't use the value property node. Use the Text.Text property node. When creating the property node, select Text, then in the next pop-up box, select Text.
- tbob
Inventor of the WORM Global

Using Property Nodes to view a subVI's xy-graphs in the mainVI

Hey all.
Yet again I sit here facing a problem. I currently working on subtracting a background spectra from another measured spectra. This part work good enough, and is what you can see in the RemoveBackground.vi.
My problem is that I want to display the xy-graphs from the subVI in my mainVI named Sample.VI. For some reason it worked for the one called Derevative, but though I am doing the very same thing to get the reference control (right-click the xy-graph in the mainVI and created a reference -> right click to create a control to the reference -> copy-paste the control into the subVI -> make a property node and connected the control and the property node -> selected the property value -> changed the property of the node to write -> linked the cluster going to the subVI's xy-graph to the property node as well).
Why won't it work for my signal as well?
Christian Maden
Attachments:
Sample1.vi ‏16 KB
RemoveBackground.vi ‏38 KB

The problem is that your Delta Signal XY Graph is expecting an array of clusters and you're feeding in a cluster to the "Value" property. If you insert a Build Array function prior to writing to the "Value" property it will work. Did not intend to have an array of clusters for that graph?
You should not you have a nasty bug in your code. If you run the top level VI as is, you get into a continuous loop that displays a dialog message about not having any data, and the only way to get out is to force quit LabVIEW, unless you have a handy-dandy LabVIEW app that aborts all running VIs.

How to read the configuration of a FXP number via property nodes or other methods.

Hello all,
I am attempting to store in plain-text the value and configuration specifics of the LV FXP datatype. (please do not suggest I cast it to integer).
The ini config format does not support FXP. So we'd like to; using property nodes, interrogate the specifics of a FXP numeric control on the FP.
It appears this is not exposed by control ref's and property nodes.
Oddly enough, you cannot even interrogate the detailed type of an INT if it is a U8, I8 or I16 etc?! via property nodes, the deepest you can go is 'digital'.
Specifically, you need to know the following to 'reconstruct' a FXP:
1. Value
2. Signed\unsigned
3. Word length
4. Integer word length
Without this, there is a risk of corrupting the value during conversion.i.e we want to load initial FXP from disk at application startup. This is a critical application and we cannot tolerate rounding\conversion errors accumilating with numerous reads\writes of FXP settings.
It is odd that you cannot interrogate via property nodes the details of a numeric type. ie. you cannot 'discover' via the property node of an INT if it is a U8, I8 or any other type.
Regards
Jack Hamilton
PS: Don't suggest XML either....

Aristos Queue wrote:
Alias name here wrote:
..second post telling me the 'propertys' of a control have nothing to do with the value is bizzare - via 'properties' for a LV control is the ONLY way to configure the specific type of a numeric...so via the numeric 'property nodes' should\would be able to query it's configuration.
I do not see any way to set these things through the properties...
I think he means by right clicking the control on the front panel and configuring with the properties dialog. The properties are exposed there, but not within the property nodes.
Edit: You beat me.
CLA, LabVIEW Versions 2010-2013

How to increment array that contains two clusters whose visibility is controlled by a visible property node and selected by a radio button.

I am trying to use a property node: visible in order to enable or disable one of two clusters. These clusters are in a larger cluster and this larger cluster is in an array. The two clusters are controlled by a radio button (one labeled transistor and the other diode). When diode is selected, the corresponding diode parameters cluster should be visible and when transistor is selected, the corresponding transistor parameters cluster should be visible. In the mean time, the cluster of the device that is not selected should not be visible. There are at least 45 elements in the array (but not more than 45). Data is entered into each cluster (diode or transistor data) for each element in the array via the increment/decrement. The problem is when you select the first radio button (transistor) and enter data, when you increment the array for a new device selection, since a visible property node was used on the cluster, a loop is created where a new cluster is trying to be shown, but the old cluster is also trying to be shown (because it is the one referenced by the property node. How do I get rid of this loop and still be able to increment the array and keep my data intact for future use? Attached is the vi
Attachments:
ChooseScan.vi ‏17 KB

You could try something like this. However, if you know how to use an xcontrol, that would be a better way to implement the above functionality so that these UI characteristics are not a part of your main VI. The problem with the above VI is that you're looping every 100 ms just to update your UI.
Also, try using the "disabled" property node, instead of the "visible" one. That way, the user will still see the options he has but they will be grayed out.
Message Edited by Sudhir Gopinath on 06-25-2007 04:45 PM
S G
Certified LabVIEW Architect, Certified TestStand Developer, Certified Professional Instructor
Attachments:
ChooseScan_1.vi ‏19 KB

Xy Graph property node:apply to all plots

I have an xy graph with multiple plots and am using property nodes to give each plot a different color. My problem is that i would like to set the "point style" for every plot to be the same, in other words: create a default point style that differs from the XY graph default.
Cheers
CLA, CLED, CTD,CPI, LabVIEW Champion
Platinum Alliance Partner
Senior Engineer
Using LV 2013, 2012
Don't forget Kudos for Good Answers, and Mark a solution if your problem is solved.

You can do this statically on the "Plots" tab of the graph properties dialog box. You can also get a property node to alter this dynamically by right-clicking on the graph and selecting Create >> Property Node >> Plot >> Point Style.
Brian R.
District Sales Manager
Washington DC
National Instruments

Can the cursors in a property node be changed to the LabView 7.X format instead of 8.X?

I plotted data and used the property node thing to create cursors so that I can select individual data points. The LabView 7.0 or 7.1 format for the cursors was useful because I could punch in a number and the cursor would then jump to that number. But with LabView 8.0, this option is apparently no longer available, and I must manually move the cursor to where I want it to go. This is very time-consuming, and I would like to know if there's a way to revert to the LabView 7.0 format, or change the existing format so that I can tell the cursor where to go by punching in a number. Any ideas?
Attachments:
question 090504.jpg ‏233 KB

Sorry but no. You are stuck with the 8.0 style cursor option. I find the labview 8.x cursor display ugly and useless. Even my customers are very quick to specify that they do not want Labview 8.x styled cursors. I really miss the 7.1 type cursor display
Besides which, my opinion is that Express VIs Carthage must be destroyed deleted
(Sorry no Labview "brag list" so far)

VI Reference Property Node inside sub-vi

Hey Folks,
I was always curious about why this is:
If I open a vi-reference in one vi, and pass the reference to a sub-vi, I can put a property node in the sub-vi and get all properties just fine - as long as I am in debug mode. When I compile to an executable this problem has its own error message and everything. So why does debug mode not throw an error too? I'm just trying to deduce what the heck is the difference.
Check my painstakingly time-consuming example.
-Devin
I got 99 problems but 8.6 ain't one.
Attachments:
OpenMyReference.zip ‏42 KB

When I discovered this issue I was coding an "About" modal screen that a user could select from a run-time menu. This was supposed to work just like Labview's "Help->About Labview" screen, giving program description and version information. So I tried to simply link in the revision from my vi's proerties because that would automatically keep a revision count and I didn't care what the format was as long as I could get a number. I just wanted an easy way to check the revision, and its easy to give someone simple instructions to check the "about" screen. Is there an easy way for a user to check the revision if all I do is put it in the application builder? User-friendliness is key, because for me to support the application I will need to have them tell me the revision they are using over the phone or in an email.
Will it be possible to create this screen in 8? If I just do it in the application builder, is there any way to link to it and build an "About" screen? I don't really care what format. It could be revision 728 as long as a user can get to it in a simple way. Otherwise I will have to just build a screen with plain text on it and edit the text by hand every time I build an application. Isn't there a more elegant way to do it?
Message Edited by billings11 on 10-20-2005 11:28 AM
-Devin
I got 99 problems but 8.6 ain't one.

Property Node

Hi Devchander:
I have a question I would like to ask. I have a property node question. For some reason. I could not send the vi file. I make a word document.
The one that is on the left is the property node I created from waveform graph. You can see there is no Plot Interp after ActPlot. The orginal one inside the For Loop contains those parameter. Why? How can I make the one like inside the For Loop.
What I am trying to do is to select another nice waveform graph on the front panel to see if it work, but the propery node can not be created the one inside the For Loop.
The attached file vi is actually a niScope EX Multi Record.vi
Regards,
John
Attachments:
Property Node.doc ‏99 KB

Here is the link to the same question in your other thread. http://forums.ni.com/ni/board/message?board.id=150&message.id=1058&jump=true

Coercion dots, Typedef. and Property Nodes

Hi,
following problem:
1. I place a simple Control (Button 1) and connect it to an Indicator (Indicator 1) -> OK
2. I place a Button as Typedef. (Button 2) and connect it to an Indicator (Indicator 2) -> Coercion dot on Indicator 2 (I don't see the point of a boolean coercion, but OK)
3. I create a property node for Indicator 1 (Value) and try to connect a constant (right-click>Create>Constant -> the constant is grayed out and the error message is 'type definition not found or contains error'
Details: The master copy for this type definition could not be found or the master copy has errors. You must find and fix the master copy, or right-click this type definition and select Disconnect.
4. I remove Button 2 and repeat step 3 -> the same thing happens
If I connect an existing boolean constant to the property node there is a coercion dot. As a matter of fact for using one Typedef. Control in a VI all other control property nodes suddenly have coercion dots even if I remove the Typedef. control. Does it mean either all controls and indicators better are typedef. or none at all?
Thanks in advance.
P.S.: the problem occurred originally in a VI with much more than two buttons...

benMyer wrote:
Something else: did you realize that the spell-checker for this forum does not know the word 'LabView'?
Because you are spelling it wrong. try LabVIEW instead.
LabVIEW Champion . Do more with less code and in less time .

How to find Property Nodes in other VI's

I am working on an application that I have inherited from others. It has huge, and in my opinion, very complicated and difficult to follow block diagrams. Here is the essence of the problem I am facing. On the main front panel there are various controls and indicators, but on the block diagram, none of them are wired to anything. So that means that (whomever it was before me) used property nodes on these controls and indicators. However, it looks like none of the references exist anywhere within the same .vi.
I have used the "Find reference" selection, but that only seems to work within the current .vi that I am already in. So I guess I have two questions...
1 Is there a way to search aross multiple VI's for a reference to a conrol or indicator?
2. To set up a program in such a way seems completely "bonkers" to me, as there is now no easy way to find where any of the controls or indicators are actually being set from. Considering there are something like 100 .VI's in this project, finding something is a bit challenging. Of course, there is not documentation of any sort. I am certainly NOT a labview expert. Perhaps there really IS a reason to set things up this way, that I am just not thinking of. Can anyone think of reasons why it might be a good idea to set things up that way? I would think that whenever possible you would want to wire directly to a control or indicator. And if you cannot do that, at least have the reference in the same .vi, and pass it into something else if needed.
Thanks....
Dan

Finding the where used cases for named queues and where obtained cases for vi server references to controls can get frustrating. The "find" feature in LabVIEW does allow text searches with several options.
Finding the String "<QueueName>" within the application instance on BD only and ignoring hidden stuff gets you to string constants that are exact matches to the queuename:
Searching for property node to a specific FP Object throughout a hierarchy can get devistating. Especially if the developer used the call chain to obtain a ref to the top level vi panel and pulled a rerence to a control that way
(DO NOT DO THIS) but I've seen it done:
Its "Legal" but almost garunteed to cause the guy who inherits your code to denigrate your parentage and intelligence. HOWEVER: that same text search for the control label text will find those string constants too.
Then document that code when you find out who is messing with what and how.
Chart it out over the app and e-mail that scribbling to the original developer too! Feel free to add a thank you note.
Jeff

Labview property node used in a subvi

I have a group of front panel Boolean control I would like to minipulate the visiblity and color(4) in a subvi. I created a cluster of boolean refnum and passed them to the VI. In the VI I created a cluster of CTLRefnum which I used as the input cluster. In the subVI I am able to control the visibility via the visibiliy property node, however the Color(4) property node does not appear as a selection in the subvi. Any ideas on how I could control the colors in a subvi.
Solved!
Go to Solution.

Hello HEJ@WR,
It sounds like you may have cast your Boolean refnums to more generic Control refnums- as the Color property is specific to Booleans you'll need to ensure that you're maintaining the reference type. Visibility is a more generic property that applies to all types of controls. Refer to this article for more information on casting refnums:
LabVIEW Help: To More Specific Class Function
http://zone.ni.com/reference/en-XX/help/371361H-01/glang/to_more_specific_class/
LabVIEWWiki also has a pretty good discussion of refnum types and class-specific properties here:
LabVIEWWiki: Control References
http://labviewwiki.org/Control_References
Also- if you attach example code demonstrating what you're attempting to do it's much easier for other forum users to assist!
Regards,
Tom L.

Property node example

can someone show me a strait forward example of using a property node and a reference node... thanks

Strait forward ?
A reference node contain a reference to a labVIEW object (control or indicator). You can modify a number of properties of the object, using a property node. The property node can be ascribed to an object either at creation time (rightclick on the control/indicator, then "create...") or later (rightclick on the property node, then "Link to)". Alternativelly, it can be wired to a reference node...
Why use ref nodes, since a property node can be linked directly to an object? You can pass the reference to a sub-vi where all the work on the properties will be done, leaving a clean diagram in the calling vi...
See the example below.
More ?
Chilly Charly (aka CC)
E-List Master - Kudos glutton - Press the yellow button on the left...
Attachments:
Example.llb.zip ‏14 KB

Is there a way to reference the property node value of a control in another VI?

Let's say that I have a situation like the one shown in the attached image.
I have an interlock system which is basically a bunch of booleans
If for example the "RF Enable" button in the "interlock VI" is true, then I should be able to flick the ON switch in my other VI (in the back), but if the value is FALSE, then it shouldn't allow it.
In other words, how do I check the value of a control across 2 separate VIs (running simultaneously)?
Thanks!!
Attachments:
sample.jpg ‏295 KB

Is one VI launched by the other, or are they launched independently? If it's the former then you just need to pass the control reference to the subVI via terminal node. If it's the latter there are a variety of ways to handle this:
Use a global variable - somewhat "sloppy" as it requires a global variable, and can lead to race conditions. In the "Interlock" VI you just set the value of the global variable when you change the value of the Boolean. In the other you're just reading it.
Action Engine - Ben wrote a Community Nugget a while back. Similar concept to a global variable.
Queue - The "Interlock" VI simply pops an element onto the queue with the value. The other VI just monitors the queue for a new element. It just needs to have something like a shift register to keep track of the last state.
Use the VI Server to access the controls of the "Interlock" VI. You can do this by accessing the "Interlock" VI's pane and get the control references. With the control reference you just need to get the value with a property node.
... (I'll let others chime in)

How can I make a "property node" for a VI?

Hello!
If I add a boolean button on the FP then I am able to make a property node for that button in the Block Diagram. But how can I make a property node for a VI? I have several VI:s an that together is one program. What I need to do is to verify what kind of VI some of my VI:s is. I need to verify if it is .exe or .vi-file, and if it is .exe then I want to disable run, abort, run continuously bottons otherwise not. I have hard that this is possible to do programmaticaly but I can´t figure out how. I am aware that I could do that manually in the File->vi properties->customize->windows appearance but theese choises makes it last forever.
I want to be able to stop and run and everything if it is a .vi file, but if it is .exe-file then all those buttons should be disabled.
Anyone have an example on this?
In an other message at this Forum I read "You can use the `Front Panel Window. Allow Runtime PopUp`" property to disable run-time shortcuts menues programmaticaly, but still I dont know how to create this property node.
/Amir

You really shouldn't open a new thread. If you don't understand something, ask and we will explain it.
Like I said in the other thread, you can check if you are running in LV or an EXE by using the Application>>Kind property. To get it, place a property node (from the Application Control palette) on the diagram, click it and find the property.
To set the properties for the VI, place another property node, right click it and select Select Class>>VI Server>>VI. You should have the properties you want under Front Panel Window.
To learn more about LabVIEW, I suggest you try searching this site and google for LabVIEW tutorials. Here and here are a couple you can start with. You can also contact your local NI office and join one of their courses.
In addition, I suggest you read the LabVIEW style guide and the LabVIEW user manual (Help>>Search the LabVIEW Bookshelf). I believe chapter 17 of the user manual explains about programmatic control of VIs.
Try to take over the world!

Word property node:selection - Ref.Number is 0!

Similar Messages

Maybe you are looking for