Problem in writing to a property node of a cluster

Hello together!
I have a problem in writing to a property node of a cluster which contains several control elements, such as combo boxes or string controls.
I would like to set the options to choose for an array of such clusters.
I tried to do this by writing to property node --> value, but the the control element in the cluster does not remain a control, but instead an indicator. The can't choose one of
the options that I set. So I further set the property node --> indicator (of the cluster) to "False", with the purpose to keep the control as a control. This results in a comment from Labview,
that this is not possible as long as the Vi is not in edit mode. I don't understand this comment. If I look to Labviews toolbar "Operate", I see that I am obviously in edit mode.
If anybody could help me, or suggest a better solution to solve my problem I would be very glad.
Thanks a lot!
Woodi
An example of what I tried to do:
Attachments:
How to write to a cluster.vi ‏42 KB

I took the liberty to modify your VI for an alternative approach (LabVIEW 7.1). You should keep your array of 32 clusters in a shift register and show only a single cluster as a front panel control.
Selecting a different transducer from the listbox on the left will load its settings into that control via a local variable.
Any changes to the settings will modify the currently selected array element
At any give time, a boolean array shows which transducers have changed settings
At any given time, a listbox summarizes all settings.
Let me know it this makes sense to you. These are just some ideas, modify as needed. Good luck!
LabVIEW Champion . Do more with less code and in less time .
Attachments:
How_to_write_to_a_clusterMOD.vi ‏87 KB

Similar Messages

  • Convert Refnum / Property Node to a cluster or an array of strings

    Hi I'm wiring a new app, and I really need to make it flexible (the needs of my customers are changing a lot). Basically I'm using XNET and and I'm putting information into different trees. The thing is that if I want to add another column related to a new property I need to rewrite a lot VIs. Is there any solution to have more generic solution?
    See the attachment, cause I'm not really that it makes sense for a lot of people here.
    Attachments:
    NotThatFlexible.vi ‏19 KB

    Here is another sample...
    I think that in this situation it's pretty obvious that if I want to change the property that I want to display it requires to hardcode a lot of things for example I cannot make a list of booleans and select which column to display. Or I need to provide to save first all the columns and use conditions tricks but that means it requires to check alllllll the properties in a very first place =/
    Attachments:
    Untitled 2.vi ‏24 KB

  • Help comparing the value of a button using the Property Node (I get a variant)

    Dear Sirs:
    (I'm using LabView 6. I guess the solution is different for 6.1)
    Currently I have created an array of Boolean RefNums (which point to many, many buttons). When I need to know when any (and which) of the buttons was pressed I just compare every element on the array with the constant TRUE. It fact, as the array is built from RefNums, I should compare the VALUE from the Property Node.
    The problem here is that the Property Node for this type of Boolean is a LV Variant, and I need to compare this with a TRUE/FALSE value.
    I tried to convert the TRUE constant to a LV variant and visc. But nothing works... I always get that none of the buttons was pressed.
    Here it co
    mes the question: "How can I compare the value of a Property Node for a Boolean (Button) with a TRUE (or False) constant?"
    BTW, maybe I should explain why I'm using RefNums instead of the direct values: As my project requires tons of buttons, I would preffer using RefNums to refer to them. (I.E. I could use a single VI that takes the RefNum and formats the button to hide it for certain users).
    I have enclosed a VI that contains what I've achieved until now, which is nothing
    I appreciate your time and help.
    Best regards,
    JAVIER VIDAL
    Attachments:
    Other_Main_Menu.vi ‏103 KB

    Javier,
    There is another problem in your code: the booleans are not polled by the main loop so they will remain false until the user presses them again. This renders the boolean latch action useless.
    What you can do is to change the mechanical action of the booleans to non-latch. When you detect a "true" in the polling loop, set the boolean to false again. One added benefit is that once all boolean are non-latch, the value property won't be a variant but a boolean so conversion is no longer needed.
    LabVIEW, C'est LabVIEW

  • Plotimages property node of XY-Graph

    hi guys,,, Could u guys plz figure out my problem?  I use Plotimages property node of XY-graph to make the maker as picture attached. At first, I selected Plotimages.front ,so my
    graph is behind of the maker no1. but my point is I want the graph is on the maker therefore, I changed from Plotimages.front to Plotimages.back to get the maker no2 and the
    graph is in front of maker but I really don't understand why the maker no1 is still there. Why is it not gone? 
    Mannie
    Thanks a lot
    Attachments:
    Untitled.png ‏83 KB

    Hey Mannie,
    I would suggest to have a look at the Plot Images.vi located at the ...labview\examples\general\graphs directory which shows how to work with this properties.
    BR, Christian

  • 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)

  • Tab property nodes LV 6.02 and 7.0 what changed?

    I'm converting from lV 6.02 to 7.0 and I have a problem with tabs and their property nodes. The code that converted generates error 1058 in LV 6.1 and 7.0 but not on 6.0.2. Where can I look to learn what changed?

    Under Help there is an entry called "Search the LabVIEW Bookshelf...". There is a link to the upgrade notes.
    But in both (6.1 and 7.0) upgrade notes nothing is mentioned about deleted properties. There are new properties for the tab control.
    Which properties are creating the error?
    Waldemar
    Waldemar
    Using 7.1.1, 8.5.1, 8.6.1, 2009 on XP and RT
    Don't forget to give Kudos to good answers and/or questions

  • Broblem with property node and DAQ-card

    Hi!
    I am using NI DAQ-card to control mini relays and I have a following broblem. I use a "binary" button to control the DAQ-assistant and so on the relays. I have made property node of the "binary" button and set it to value mode(write). When I change the value of property node, the "binary" button in user interface works properly, but the the relay doesn't change the state.

    The boolean array constant that you are writing to the property node is empty. That is it has been defined as a boolean array, but it has no elements.
    The array constant on the left is an empty boolean array. Notice that all teh boolean constants are grayed out. This indicates that none of the constants are 'active'. The array on the right contains 8 active elements. Note that the 8 elemants are more solid in color adn the the 9th element is grayed out.
    What you need to do is define your boolean array with the proper constants to turn on or off the proper digital lines.
    EdMessage Edited by Ed Dickens on 05-25-2005 09:15 AM
    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.
    Attachments:
    emptyarrays.png ‏2 KB

  • Property node to cluster element

    Hello All
    When clicking at the control cluster element you can create a property node.
    But if right click on property node you can NOT Link to the cluster element.
    How it is possible, that you can do it only in "one direction"?
    Pawel

    Have you looked at creating a property node for the cluster and using the Controls[] property? Controls[] is an array of control references for the elements in the cluster. The array is ordered in the cluster order. If you're doing the same operations on each cluster element, you can put the operations in a loop autoindexed by Controls[]. If you're doing different things for each cluster element, you could create a state machine controlled by the Controls[] index. The property nodes for the indiviual elements will be disconnected from the controls, then the control reference indexed (or autoindexed) from Controls[] will be wired to the reference input of the property node.
    You can get a disconnected property node from the Commun
    ication >> ActiveX function palette, or your can create a property node for any control, then right-click on the property node and select Disconnect From Control. Don't worry about the label on the disconnected property node until you wire the control reference to it. It will automatically adjust based on what it's wired to.

  • 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

  • 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.

  • Problem scrolling using property nodes

    What Im trying to do is a "fake scroll bar" using numeric controls and the VI Property FP Origin for the same vi where the numeric controls are. The problem is that when the vi is running and I use the scroll bar the controls also move and is a mess. I need to have it in a fixed (like floating) position within the window, how can I do that?

    How about using a property node to move the control as you scroll so it
    appears to remain fixed on a moving front panel?
    "pacp" wrote in message
    news:50650000000500000082D90100-1079395200000@exch​ange.ni.com...
    > Hi,
    >
    > What I want to move is the entire front panel but one control (the
    > fake scroll bar which is a numeric control) that is on it. What I
    > really need is to have ONLY a vertical scroll bar... the way to do it
    > doesn't really matter,
    >
    > Thanks

  • I'am having problem with a graph property node by using format & precision

    I would like to display an amount of data in a waveform graph and to choose the X scale to display absolute time (whitout date information) or scaled decimal value.
    Absolute time is a must because the scaling should reflect the acquisition time and not only a value in hour, minute and second.
    Using the property node I can choose between 10 differents formats (0-Decimal, 1-Scientific, 2-Engineering, 3-Binary, 4-Octal, 5-Hexadecimal, 6-Relative Time, 7-Time and Date, 8-SI, and 9-Custom).
    Format 7 - Time and Date should be a good choice but LabVIEW set automatically system time AND system date without any possibilities to change anything.
    Trying format 9 - Custom ends everytime with error 1077 (invalid property value).
    Any help to explain me how to use the format Custom or to give me a solution to switch between time (no date) and decimal scaling is appreciate.
    Thank 

    In addition to the Xscale.Format property node, you also need to set the XScale.FormatString (see a little below the Format entry).
    Use %<%.0X>T as format string.
    Chilly Charly    (aka CC)
             E-List Master - Kudos glutton - Press the yellow button on the left...        

  • A problem about property node

    Hi,
        Why this VI use property node before visa read?
    Attachments:
    Basic Serial Write and Read1.vi ‏36 KB

    Hi hengfo,
          It's not necessary to use "bytes at port", in fact, I don't trust it, it seems there can be some strange latency! (see threads below)
    Just go ahead and wire the number of bytes you want to read to the Read  - but be ready for a timeout error if the bytes you request don't arrive within the VISA timeout period.
    See these threads:
    http://forums.ni.com/ni/board/message?board.id=140​&message.id=7839&requireLogin=False
    http://forums.ni.com/ni/board/message?board.id=170​&message.id=111079&requireLogin=False
    "Inside every large program is a small program struggling to get out." (attributed to Tony Hoare)

  • Property Node whitepaper

    Is there any white paper on property node similar to this one on control references http://www.ni.com/white-paper/3159/en/. I am running into some problems with image property node and I have not been able to find useful information.

    Frankly, that sounds like a problem with the image control itself. Is this control from a LV toolkit? Where did you get it?
    Another thought I just had. Is this image control implemented as an XControl? Something I noticed once is that when you write to the terminal of an XControl, LV doesn't actually update the control unless the value has actually changed from the last time it was written to, but writing to the value property node would always update the XControl.
    Mike...
    Certified Professional Instructor
    Certified LabVIEW Architect
    LabVIEW Champion
    "... after all, He's not a tame lion..."
    Be thinking ahead and mark your dance card for NI Week 2015 now: TS 6139 - Object Oriented First Steps

  • 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.

Maybe you are looking for