Multiple property nodes

Hi,
I have about 10 or so numeric indicators that I modify their properties so I can change the background colors etc.  The problem is, these indicators are not bundled or anything, so I bascally have 10 different property nodes that I have to wire and it looks bad in the block diagram.  I was wondering if there is a way to bundle only the property nodes in the block diagram and apply the changes directly to the bundle so my code would be cleaner.  Hope my question is clear enough. BTW, the changes made to every indicator property nodes are the same.
Thanks
Yohan

Attached is a vi and an image of the block diagram.
Edit: The VI will not run as is, you need to wire something to the property node in order for it to run.
Message Edited by Novatron on 06-23-2006 09:21 AM
Message Edited by Novatron on 06-23-2006 09:22 AM
Attachments:
Properties.vi ‏11 KB
Properties.jpg ‏55 KB

Similar Messages

  • Use of multiple property nodes for GUI manipulation

    I have a LabVIEW 6.0.2 application where I'm using 14 different property nodes in the main loop. All of these have to do with GUI - hiding buttons when "X" isn't pressed, disabling and greying out controls if <0, popping one button on top of another depending on the mode of operation, etc, etc. While this works fine, the program is getting slow. I've noticed that using the old 2-D buttons works faster - things update faster and redraw quicker. However, more to the point, I once read that if you have to use a lot of Property Nodes like this, that you should bundle them into a sub-vi, thus replacing what would be Property Nodes with references. How does that make it faster?
    Richard

    Not sure if bundling them into a sub-vi by itself would make it faster. The nodes in the sub-vi would still have to access the user interface thread, and that's where the slow down comes from.
    When I use any property node, I put it in a case structure and only write to it when needed. You just need to be able to detect when the value being written is changed from last loop iteration. It's useless to constantly rewrite the same value (doesn't have to be the "value" property) to the node.
    Bundle them into a sub-vi and put the change detector, case structure and nodes in the sub-vi, this should help speed things up a bit. Assuming of course that the nodes are the slowdown. It may also help clean up the diagram a bit.
    Ed
    Ed Dickens - Certified LabVIEW Architect - DISTek Integration, Inc. - NI Certified Alliance Partner
    Using the Abort button to stop your VI is like using a tree to stop your car. It works, but there may be consequences.

  • X-y graph property node

    I am looking for a means by which to programmatically turn on and off some of the plots in an x-y graph.
    I have the code that plots a series of thermocouple inputs to an x-y multigraph where the x-value is time. Using a property node I can wire in a Boolean to turn the "plot visible" input TRUE or FALSE. This works for the first plot on the graph, but I can't make it work for the rest of the plots. Creating multiple property nodes and assigning different plot ID numbers to the Plot Y. Scale Index input doesn't work, they're just ignored. I can't even get multiple plots to turn off if I wire multiple plot ID numbers into the same property node (using multple Plot Y Scale Index inputs).
    Is there a trick to turning plots on and off in a multiple plot x-y graph?
    thank you. 
    Laura SImpson
    Electrical Engineer
    BEI Precision Systems and Space Company
    Solved!
    Go to Solution.

    That and a for loop were exactly what I needed. Thank you.
    Laura SImpson
    Electrical Engineer
    BEI Precision Systems and Space Company

  • How to set property nodes for each of the multiple y-axes?

    In Labview 6i, I have set up multiple y-axes on an xy graph. I want to change certain properties of each of the 2 y-axes independently. I believe I can do this using "property node".
    However, after I have created a property node for the xy graph, I realised that there is only 1 y-axis selectable from the list of properties. How can I set the property of the other y-axis then?
    Thanks for the help!

    I believe there is a property called "active graph"... this allows you to
    select the active graph to apply the property changes to...
    Later...
    meng118230 wrote in message
    news:[email protected]..
    > In Labview 6i, I have set up multiple y-axes on an xy graph. I want to
    > change certain properties of each of the 2 y-axes independently. I
    > believe I can do this using "property node".
    >
    > However, after I have created a property node for the xy graph, I
    > realised that there is only 1 y-axis selectable from the list of
    > properties. How can I set the property of the other y-axis then?
    >
    > Thanks for the help!

  • Using One Property Node For Multiple Controls/I​ndicators

    Question for all you LabVIEW gurus.  Is there a way to create 1 property node that is used for multiple indicators?  For example, if I wanted to display the same value on 10 different indicators using the property node - value function do I need to create 10 separate property node-value instances for each indicator?  Or is there a way to tie all of those indicators to only one property node?
    Thanks!
    Solved!
    Go to Solution.

    Hi hobby1
    You could create a cluster, and inside in it put all the indicators, see the image attached
    Attachments:
    capture1.JPG ‏14 KB

  • Add multiple TermChar properties in property node

    Hello all
    I am communicating to a device via RS232 and most of the responses are terminated with  a <CRLF>.  but some of the commands are not terminated.  Can i use multiple termination char properties in the property node ?
    - James
    Using LV 2012 on Windows 7 64 bit

    Usually, I set the termination settings before reading each command. If
    the command is terminated with <CRLF> then set the termchar to
    <LF> before reading the reply. Make a Read VI that will set or
    not  the termchar according to a boolean input.
    Message Edité par Jean-Pierre Drolet le 07-19-2005 08:44 PM
    LabVIEW, C'est LabVIEW
    Attachments:
    termchar.gif ‏6 KB

  • Property node for a chart with multiple axes

    I have created a chart with two y axes, one for each of two data sets
    that I am plotting. From the front panel, I can view the properties of
    the chart and adjust the scales of the two axes separately under the
    Scales tab. I need to, though, adjust the maximum and minimum of these
    axes programmatically. How can I create a property node that refers to
    one of the two y axes, and how can I specify which axis the node is
    referring to? If create a generic YScale:Minimum property node, I get
    an error.
    Thanks for the help,
    TJR

    "...YScale:Minimum property node, I get an error."
    That is curious.
    You can specify the active scale for which the property will be applied.
    The attached demo (in LV 7.1) illustrates how to do this by fist setting the index of the active scale and then updating its property (property nodes execute from top to bottom).
    What error do you get?
    Ben
    Message Edited by Ben on 11-30-2005 08:07 PM
    Ben Rayner
    I am currently active on.. MainStream Preppers
    Rayner's Ridge is under construction
    Attachments:
    Set Active Scale.vi ‏27 KB
    Set Active Scale.JPG ‏18 KB

  • 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

  • What are the alternatives to updating indicators using property nodes?

    Hello,
    I'm building a VI which needs to update several controls/indicators at multiple points throughout its execution. It also needs to be able to accept new values from the controls at any given time.
    The problem with this is that all of these controls and indicators are on the front panel of another VI which is calling my VI. The current version of my program updates all of these controls and indicators using references and property nodes (each indicator/control that needs to be used has its own reference control on my VI, and these references are then sent into property nodes), which naturally makes it slow.
    At the moment I'm considering rebuilding my VI in such a way that the main one is able to retrieve the data without using references, but this will be not only very time-consuming but also difficult and possibly even impossible without my code turning into a massive disorganized pile (especially since the lab computer is slow enough, and the main VI large enough, that pressing the 'clean/reorganize block diagram' button causes a crash).
    Any alternatives to this? Queues?
    Solved!
    Go to Solution.

    This (my Event nugget) is the best general solution I came up so far.
    Felix
    www.aescusoft.de
    My latest community nugget on producer/consumer design
    My current blog: A journey through uml

  • 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

  • Waveform Names to Menu Ring String Property Node

    Hi,
    I am extracting waveform data (names) to go into a menu ring as string data.
    It seems to work, apart from when you actually click on the menu there is no text (though you can successfully change it).  I am wondering if it is to do with the odd symbol in front of the name but not sure how to get rid of it.
    Hoping it is something simple but it is just knowing where to look with all the options available to you.
    Please see attached.
    Best Regards,
    James
    Solved!
    Go to Solution.
    Attachments:
    MenuRing.jpg ‏23 KB

    Hi James,
    You were 99% of the way there all you needed to do was to pull that weird character from the string, I used the “match pattern” function to allow me to isolate that character and pass the resultant string into the text ring property node. A good bit of advice if you find a character in LabVIEW that you do not recognise or if you are unsure about spacing, right click the output string and select “ ‘\’ codes display “ this will show what the code representation of the string is and you can just feed that directly into the “match  pattern” function. I have attached my code (LabVIEW 2010 if you need in previous version please just ask) for you to have a look at. I have used a producer consumer template and selected multiple input channels from a simulated PCI 6220.
    P.S. I’m not sure where that character comes from??
    Regards
    Andrew George @ NI UK
    Attachments:
    Forum James AC.vi ‏26 KB

  • 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

  • Grouping property nodes

    Hi there, I'm creating a DAQ application wich reads in 64 channels. Now I want to enable and disable certain items in the front panel using property nodes. You may understand that this would take a lot of time considering it's a 64-channel DAQ application. Does someone has any idea how to group certain front panel objects so I can use only one property node for multiple objects? Or is there another way?
    Another question:
    How can I automaticaly read in a front panel datalog file so it remember names I entered last time I used the application?
    thanks, Bert.

    > What I'm trying to do is:
    > Grey out all 64 channels (1 channel = a string control, numeric
    > indicator and two check boxes) when the acquisition begins (pushing a
    > button). So this would take me 64*4 = 256 property nodes and I thought
    > that there must be an easier way.
    >
    Consider putting the string, numeric, and check boxes in a cluster.
    Place the cluster in an array, and grow it vertically to show 64
    elements. If your layout has several columns, make a copy of the array
    and make say four of them with 16 rows each.
    On the diagram you will be able to set the array properties easily, but
    you will not be able to set properties for individual cells within the
    array.
    This will also affect how you access the controls. Instead of 64x4
    terminals all over the diagram, you will just have the arrays, and you
    can index and unbundle when you want a data element. If you normally
    deal with the 64 displays, this will be very convenient. If you often
    need access to individual elements, I'd recommend making a subVI icon
    where you pass in the array and the index and it returns the four
    subelements as outputs. This will probably clean up your diagram as
    well as simplifying the graying of the display.
    Greg McKaskle

  • Why knob need to use property node to change its value

    Refer boiler vi in CLD exam sample question. 
    In the vi the knob vlaue is changed with a property node, it is not wired directly to a constant. The comment in the vi is something like "writing using property node because of the latch action of the booleans in the cluster"...
    Huh? How do the booleans influence the knob even though they are in a same cluster? What principle is this called? I need to google this up,  I didn't read it in.
    my Labview books. 
    Attachments:
    Boiler Main LV86.zip ‏61 KB

    That comment doesn't make any sense.
    There are two main reasons I can think of why you want to use a Value property node.
    1.  You want to control the order of execution by using the error wire.
    2.  You want to use a property node on multiple controls by feeding it references to different controls.
    Neither of these appear to apply in the screenshot you show.
    However, looking deeper, it looks like you can set the value of a specific item in the cluster by way of the property node.  Check out the Link to section of its shortcut menu.  I don't think you can use a local variable to set a given element of the cluster.  Now you could change the value of the entire cluster.  Read the cluster, bundle the new value for that one element, write to a local variable of the cluster.  But you won't be allowed to do that because of the latched booleans that are a part of the cluster.  Hover over the context help of that property node and read the description there as well.

  • Unable to use correctly the value property node in a re-entrant VI

    Hi everybody,
    I am using labview 6.1 and developing an application which call a reentrant SubVI. However when I use the Value Property Node (which I need : the use of local terminal isn't possible in my final application) in the re-entrant SubVI, i get the initial value of the control, not the current value !?
    Is there anybody to explain me why and how to solve this problem ?
    I have attached 3 VIs for a better explanation.
    Thanks.
    Attachments:
    Master.vi ‏9 KB
    Slave.vi ‏23 KB
    globales.vi ‏7 KB

    You just need to create a local variable instead of a property node to read the value of the control that was passed in. Popup on the control and select Create >> Local Variable. Or just wire the control to where you need it. Data flow is still working; Feroz just explained an idosyncracy of how property nodes work in reentrant VIs.
    BTW - I don't mean to turn this into a sales opportunity, but you might want to check out the VI Analyzer Toolkit. It reports the following for a reentrant VI that uses property nodes:
    "You are using an implicit property node in this reentrant VI. This can result in unexpected block diagram behavior, as a reentrant VI will occupy multiple data spaces but will maintain only a single front panel. You should consid
    er either making this VI non-reentrant, or eliminating the use of implicit property nodes."
    I'm not sure how many people would know what the message means, but they would be forewarned and hopefully check into it further (e.g. test with this specifically in mind).
    I filed a bug report to have this investigated further and at least documented better.
    Roy

Maybe you are looking for