Property node visible

Hola que tal, tengo una duda.... en mi panel frontal tengo 10 controles boleanos, los cuales dependiendo de una señal de entrada se hacen visibles o in-visibles, ya tengo el property node con visible, ya funciona y toda la onda... lo que pasa es que cuando corro el programa se ve como aparecen los controles uno por uno, existe alguna manera de hacer que todos se vena al mismo tiempo y todos se oculten al mismo tiempo ?

>>Hola que tal, tengo una duda.... en mi panel frontal tengo 10 controles boleanos, los cuales dependiendo de una señal de entrada se hacen visibles o in-visibles, ya tengo el property node con visible, ya funciona y toda la >>onda... lo que pasa es que cuando corro el programa se ve como aparecen los controles uno por uno, existe alguna manera de hacer que todos se vena al mismo tiempo y todos se oculten al mismo tiempo ?
Ha probado el property node "Defer Front Panel Updates"? Cuando lo pone "verdad", normalmente, hace que nada cambia en el Front Panel hasta que se ponga "falso" de nuevo. (empieza "falso" al hacer correr el programa). Espero que me entiendas, no soy del habla espanola
Michael
Attachments:
deferFPupdates.JPG ‏31 KB

Similar Messages

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

Tab Page visible property node not working correctly

I am making a vi in which we have a tab control with 6 pages and to move from one page to another there is ring control with option for every page on page 1( page 1 is the default page), at a time only one page is visible so we can move only through that ring control present on page 1 and to come back to page 1 from all other pages there is button "go back" on all other 5 pages, everything is working fine for 5 pages but when after going on page 6 and then if i press go back button instead of going back to page 1 program hangs and one more thing that i noticed is after stopping the program the page 6 becomes the default page( which otherwise is page1) i dont know why this is happening.
I am attaching the snippet of the code which executes when i press go back button.
one more thing that i am not getting here is when i checked the program through step execution, the last property node( page6 ) that is executing first after that it goes to first property node and then it goes in sequence, this also i want to how is this happening.
Solved!
Go to Solution.
Attachments:
tab page property node.png ‏43 KB

I think you would be better off just to use your array and turn on/off the necessary tabs instead of explicity setting each property every iteration.
Attached is one example.
"There is a God shaped vacuum in the heart of every man which cannot be filled by any created thing, but only by God, the Creator, made known through Jesus." - Blaise Pascal
Attachments:
set visible tabs.png ‏56 KB

Any alternate solution to using Waveform Chart Property Nodes 'ActPlot', 'Plot.Visible' for mulit-plot color problem on PDA?

Hello,
    On a waveform chart, 4 signals need to be plotted based on the status of 4 boolean inputs. Eg. if the first boolean input is true, the first signal needs
to be visible on the waveform chart; if the first boolean input is false, the first signal should not be visible on the waveform chart and so on. This can be
done on LabVIEW desktop using the Waveform Chart Property Nodes 'ActPlot', 'Plot.Visible' - a sample VI "BundleSignals_Select_Desktop.vi" is attached for
reference.
    But on PDA, since the Waveform Chart Property Nodes 'ActPlot', 'Plot.Visible' are not supported, some other method has to be used. I have done the
selection/de-selection of these signals using 'Insert', 'Delete' array functions as shown in the attached VIs "BundleSignals_PDA.zip" which works, but the
problem is that the colour of these signals do not work as desired when the selection/de-selection of these signals is done - It is required that the first
signal should always appear in White color, the second signal should always appear in Red color, the third always in Green color & the fourth always in Blue
color.
    I hope i have made myself clear of the problem. Has anyone faced this problem before & is there a solution?
Note: Version of LabVIEW that we are using: LabVIEW 8.5 Professional Development System for Windows Vista/XP/2000 and LabVIEW 8.5 PDA Module for Windows
Mobile.
Thanks & Regards,
Subhashini
Attachments:
BundleSignals_Select_Desktop1.vi ‏25 KB
BundleSignals_PDA.zip ‏26 KB

Unfortunately the only alternative to using property nodes is to set the properties manually on the development environement. The limited size of memory does limit us in terms of features for the module.
Mehak D.

How to show/hide sliders on a slider control using property nodes?

If I have a slider with multiple sliders on it how do I change which sliders are visible using property nodes? The only property I have found is making the entire control to be visible or not. This is a possible solution to have two different controls, one slider with only one slider and another slider with two sliders overlapped, but not desirable.
I found on a thread in the forum that it is possible but the user did not provide any specifics about which property it was. (http://forums.ni.com/ni/board/message?board.id=170&message.id=181279&query.id=34404#M181279)
I would appreciate an example VI if possible (Preferred version is 8.5 but versios 8.2, 8.0, and 8.6 are available to me).
Thank you in advance for the help,
Aaron

Just make them transparent! Here's a quick draft.
LabVIEW Champion . Do more with less code and in less time .
Attachments:
HideSliders.vi ‏20 KB

Property nodes are severely affecting performance

LabVIEW Gurus,
I am continually running into some serious performance hits using property nodes to update attributes of FP objects. Attached is a classic example.
I have 8 XY plots that are being fed 600 SGL points every 200 msec - a very modest data rate. Each plot is a dynamically instanciated .vit placed into one of 8 subpanels in a container VI. The container VI also acts as the data server for the charts, sending each one their data in their own single element queue. The entire architecture runs great (~4% CPU load, see attached picture) until I being updating a property node to display the value of the cursor y-value. When I enable the "Caption.Text" property node of the XY Graph to display the cursor value, the CPU usage soars to over 30%.
As an aside, I am developing on a dual core 2.1GHz platform with 4G memory with LV8.5.1, and the target machine is not nearly as beefy. That's why 30% CPU on my powerhouse is an issue - it basically brings the embedded target to its knees.
I have included an example VI for you to run on your machine. Consider it "representative" of my bigger issues. The VI runs about 10% CPU without the caption update, and 20% with the caption updates.
Finally, I have tried putting the VIs into the UI execution system. I have also tried Defer Panel Updates, but this actually slows down performance.
Best regards,
Jack Dunaway
With Captions
Without Captions:
Message Edited by mechelecengr on 10-10-2008 11:23 AM
Message Edited by mechelecengr on 10-10-2008 11:27 AM
a.lia-user-name-link[href="/t5/user/viewprofilepage/user-id/88938"] {color: black;} a.lia-user-name-link[href="/t5/user/viewprofilepage/user-id/88938"]:after {content: '';} .jrd-sig {height: 80px; overflow: visible;} .jrd-sig-deploy {float:left; opacity:0.2;} .jrd-sig-img {float:right; opacity:0.2;} .jrd-sig-img:hover {opacity:0.8;} .jrd-sig-deploy:hover {opacity:0.8;}
Solved!
Go to Solution.
Attachments:
WithCaptions.png ‏102 KB
WithoutCaptions.png ‏96 KB
GraphPerformanceProblems.vi ‏23 KB

Yes, property nodes force synchronous execution and if you do that too often, other things suffer.
The above solution is good. You can simplify things even more by removing all that unneeded extra code that just complicates things.
Here's a quick draft. Let me know if you have questions.
Message Edited by altenbach on 10-10-2008 09:58 AM
LabVIEW Champion . Do more with less code and in less time .
Attachments:
samewithlesscode.png ‏9 KB
GraphPerformanceProblemsMOD.vi ‏19 KB

Problem with the Value property node (MacOS)

As far as I have tested it, Value Property nodes (and Value (signaling)) don't work in MacOS : The value property appears as a boolean, the value(signaling) as a cluster (width, height).
Even with boolean controls, the node is not working.
No such problem in LV 8.6.
Am-I missing something ? Is that some "intended use" ? Or simply a bug ?
Chilly Charly (aka CC)
E-List Master - Kudos glutton - Press the yellow button on the left...
Solved!
Go to Solution.

That sounds like some sort of indexing problem with the property nodes like somesort of corrupted installation. What if you just delete the property node and recreate it?
I dropped a numeric control and looked at the shortcut menu for the list of property nodes. Right below Value and Value (signalling) are Visible (which would be a boolean) and Xcontrol, which when you step down through the submenus, the first choice is Container bounds, a cluster of Width and Height. So these 2 datatypes that are 2 lower on the list match the ones you are getting.
What happens if you pick another property node a few elements up or down on the shortcut menu? Does is happen for some other properties, and if so, are thereany properties that are okay?
Here is what my property nodes look like for a numeric and I draggged the box up and down to show the natural order of the property nodes. Note that I have scripting installed, so there are a few more property nodes (and the blue box at the top) that you might not have.
PS. Check you signature. The Kudos button is now moved to the left since the forum upgrade.
Attachments:
Example_VI_BD.png ‏4 KB

Property nodes to items in cluster are FRAGILE

This issue has bugged me for a long time . I just got bit again and I wonder if anyone else has a workaround.
I just checked and LV 2009 has it too.
Create a custom control of a cluster with three elements named A, B, C (numeric controls, booleans, whatever, it doesn't matter).
Make it a TYPE DEF (non-strict) and save it.
Put an instance of it on a new VI panel.
Create a PROPERTY NODE for item B and set it to DISABLED property.
Wire a constant to that property node.
Now, if you run the VI, it sets the DISABLED property of item B to the value of the constant. Fine.
Now go to the TYPEDEF, and add another item, called A2 to the cluster.
Re-arrange the cluster order so that it's A, A2, B, C, and save the type def.
Look at your diagram. The property node is no longer linked to B, it's now linked to A2.
Apparently, LV uses the cluster order internally to keep track of the links. So now I'm linked to A2, not B.
If A2 was a different type of object from B, then you MIGHT get lucky and the diagram breaks. At least then, you can see the fact that it changed.
But almost everything has a DISABLED and a VISIBLE property, if that's the one you're using, then you won't notice that it was changed behind your back.
I have taken to adding a free label with the name of the expected control (in parentheses) next to the property node, along with the true label. So if I see a discrepancy between the true label and the free label, I can recognize such a case.
But that's only if I remember that this crap happens.
Anybody got any better ideas? How can I prevent, or at least recognize, such an unwanted change?
Bonus question: the same thing happens with events, for the same reason (I suppose). If I tied an event to item B, that event switches to item A2 behind my back.
Steve Bird
Culverson Software - Elegant software that is a pleasure to use.
Culverson.com
Blog for (mostly LabVIEW) programmers: Tips And Tricks

CoastalMaineBird wrote:
This issue has bugged me for a long time . I just got bit again and I wonder if anyone else has a workaround.
I just checked and LV 2009 has it too.
Create a custom control of a cluster with three elements named A, B, C (numeric controls, booleans, whatever, it doesn't matter).
Make it a TYPE DEF (non-strict) and save it.
Put an instance of it on a new VI panel.
Create a PROPERTY NODE for item B and set it to DISABLED property.
Wire a constant to that property node.
Now, if you run the VI, it sets the DISABLED property of item B to the value of the constant. Fine.
Now go to the TYPEDEF, and add another item, called A2 to the cluster.
Re-arrange the cluster order so that it's A, A2, B, C, and save the type def.
Look at your diagram. The property node is no longer linked to B, it's now linked to A2.
Apparently, LV uses the cluster order internally to keep track of the links. So now I'm linked to A2, not B.
If A2 was a different type of object from B, then you MIGHT get lucky and the diagram breaks. At least then, you can see the fact that it changed.
But almost everything has a DISABLED and a VISIBLE property, if that's the one you're using, then you won't notice that it was changed behind your back.
I have taken to adding a free label with the name of the expected control (in parentheses) next to the property node, along with the true label. So if I see a discrepancy between the true label and the free label, I can recognize such a case.
But that's only if I remember that this crap happens.
Anybody got any better ideas? How can I prevent, or at least recognize, such an unwanted change?
Bonus question: the same thing happens with events, for the same reason (I suppose). If I tied an event to item B, that event switches to item A2 behind my back.
For the disabled property inside of cluster whos definition hcanges... we are screuued.
For the events your idea to include the text name, is the same technique that Jim Kring shared with us when he discovered the same thing can happen with dynamic event references. I belive that was CAR'd.
No solutions so no bonus points.
Ben
Ben Rayner
I am currently active on.. MainStream Preppers
Rayner's Ridge is under construction

Y scale flip in waveform graph when using property node.

I'm having problem with property node. I'm trying to build a stackable scope with Waveform Graph And dynamically change the number of plots. It is working. But The Y scale is flipping. The minimum goes on the upper part and the minimum scale goes down. when I change it appearance it's not very fast. It take about 1 or 2 second on my computer.
The way it is build actually is:
Cluster_1 is containing 8 clusters. And each of the 8 clusters are containing a Waveform Graph. By reference I change the property of each Waveform to make visible or not each of the Waveforms.
First I would like to solve the scale problem and second accelerate the redrawing of my scope.
Maybe there is an other way t
o do what I need.
Thanks.
Nitrof
Attachments:
MultiScopeExample.llb ‏192 KB

Wow, you have a neat program! The problem with your y axis flipping is because the last four charts in the cluster were programmed with a flipped axis. I relabeled the charts and it worked correctly.
From what I could tell with your code, you do not need the sequence structures. The one inside of the even actually runs the same code twice. Remove this duplication and you should see improvement. Also clusters are slow, so you should not expect it to blink back with additional coding. Use defer panel updates to get that behavior. I incorporated these changes and attached the program.
Jeremy Braden
National Instruments
Attachments:
MultiScopeExample.vi ‏163 KB

How can I copy property nodes without them unlinking?

I'm in the process of designing a VI that allows the user to choose between two methods of data analysis, each with a unique display structure. So I set up the two display methods, and overlapped them, and wrote a quick sequence to make the appropriate set appear/disappear using the visible property node. I wanted to be able to copy the frame where I made all the elements of one type invisible. However, when I copied the property nodes, they all unlike from their front panel items. I found a more elegant way around the issue, but the problem remains: is there any way to copy property nodes without having to relink them manually afterwards?
Drew

If you copy by selecting the items and then while holding down the Ctrl key (on a PC) drag a copy instead of copying and pasting the property nodes won't unlink.
Brian

Error 1055 occurred at Property Node : Object reference is invalid. This Error occurs only in built application

I am using a WaveformChart to display multiple traces of data, the number of traces is variable, I use property nodes to set the number of traces and whether the digital display is visible or not, as more data is available the number of traces is increased and the digital displays are made visible. Within the Labview design environment everything works well. However when running the built application if two or more traces are to be charted I see error 1055. I suspect it is related to making the digital display visible on two or more waveform traces. See VI attached.
Why is this error happening ?
Thanks.
Single trace
Two traces
Solved!
Go to Solution.
Attachments:
Setup Plot Style.vi ‏29 KB

WF Charts only create their plots at development time.
If you attempt to access a plot that was never there you get that error.
To work-around this detail, simply size the legend for more plots than you ever expect to use at development time so that the plots are created and availabe when you do the build.
Ben
Ben Rayner
I am currently active on.. MainStream Preppers
Rayner's Ridge is under construction

Property node or what else ?

Hi,
I want to built a VI that function similar to the Terminal in the Telnet Line Client.vi (in Telnet Toolkit). I try to learn from the example, but could not figure out what the "Terminal" showed below is. The 1st picture in the attachment is the property node, but I don't know how it is related to the 2nd picture. Could not find any help on it, and don't even know what it called Any idea is appreciate!
thanks,
Anh
Attachments:
terminal question.JPG ‏4 KB

Hi Anh,
The second "thing" in your picture is a local variable.
With a property node, you can access not only the value of the pointed variable ("terminal" in that case) but all its attributes, such as size, position, color, visible or not and many interesting things ; some attributes are read only and some at reable and writtable.
With a local variable, you can only access (in read or write mode) the value of the pointed variable.
To create a local variable, right click on your variable, go to "create" >> "local variable"
Am I clear ?
When my feet touch the ground each morning the devil thinks "bloody hell... He's up again!"

Tab Control Property Node unknown error on TPC

I am using Lab View 8.6. I am programming an HMI onto a TPC 2106. I am using a Tab Control and it workls fine. The problem is when I add a property node for the tab control to the block diagram. I get an unknown error no matter which property I choose or if it is read or write. I tried it on a vi destined for the computer and it works fine. It seems to be an issue with the TPC 2106 as the destination.

Hi vrundquist,
When compiling a VI for a TPC, there are many properties of controls and indicators that will not be supported. Which properties specifically have you tried? I want to be sure you are choosing a property that should be OK. For example, try the Visible property. Also, is there anything else going on in your code, or can you reproduce this with a VI that has nothing but a tab control?
Regards,
Brian A.
National Instruments
Applications Engineer

Help with property node

I have a graph chart with 3 plots. I can make any of the plots visible or not using property node as shown in the attached file.
Is there a any way I can scale the block diagram and use less case structure . for instance is it possible to use just one case structure to set the plot visible property of the three plots.
Thank you.
Attachments:
PropertyNodeChartAssign.vi ‏29 KB

(You are using way too much code for these cases! Your true and false cases only differ by the boolean, which you already have from the control. In a first cleanup, you can delete the case structure and wire the button directly to the "visible" property. Same functionality! Right?)
Still, that's not the way to go!
Property nodes are expensive! You only need to write these properties if one of the selector changes, and not with every iteration of the loop! You should handle these thing in a seperate loop using an event structure. Attached is a simple example. See if it makes sense.
Notice that the bottom loop waits until needed and rarely spins.
Also: Instead of a column of similar controls, use an array of controls. Instead of using thee sets of "dices" use one in a FOR loop.
Message Edited by altenbach on 05-18-2007 08:32 PM
LabVIEW Champion . Do more with less code and in less time .
Attachments:
ChartVisible.png ‏16 KB
PropertyNodeChartAssignMOD.vi ‏28 KB

I don't know how to use the property node to get information out of my sub vi while it is working.

I had a question answered earlier about passing information out of a sub vi, and was helped out. The problem is that I don't understand what is happening as I can not reproduce the results. I am now trying to take results of a comparison (true-false) and pass that back out of my sub vi. I tried a property node and to connect a refnum control to it in the sub vi. Then I tried to connect an indicator to its terminal in the main vi, but was unsuccessful can someone tell me how and why, step by step, to pass this information out. Starting with the point of information in the sub vi to the indicator in the vi. I would appreciate any help that you could give m
e.
Attachments:
Pass_a_Reference.vi ‏15 KB
GL_Flicker_mod.vi ‏77 KB

Step by step:
1. On your main vi Front Panel, create your boolean indicator.
2. On the block diagram, right click the new boolean indicator and select Create - Reference.
3. On sub-vi front panel, create boolean indicator (or use one that is already created).
4. On sub-vi front panel, create a reference (Controls Palette - Refnum - Control Refnum).
5. Right click on the newly created Refnum and select Select Vi Server Class - Generic - GObject - Control - Boolean. The refnum label changes to BoolRefnum.
6. On sub-vi block diagram, create Property Node (Functions - Application Control - Property Node). Find the BoolRefnum and move it close to the new Property Node.
7. Wire the BoolRefnum to the reference input of the property node.
8.
Right click on the property node and select Change to All Write.
9. Move mouse to point to Visible inside property node box, left click and select Value.
10. Wire the boolean indicator from step 3 to the Value input of the property node.
11. On sub-vi front panel, right click on icon and select Show Connector.
12. Click on empty connector spot then click on the new BoolRefnum. Save your sub-vi.
13. On main vi block diagram, connect refernece created in step 2 to the new connector terminal of sub-vi.
14. Save and run.
Here are the modified vi's.
- tbob
Inventor of the WORM Global
Attachments:
Pass_a_Reference.vi ‏20 KB
GL_Flicker_mod.vi ‏83 KB

Property node visible

Similar Messages

Maybe you are looking for