Updating a property node from a sub-vi

I want to have a string indicator box that updates as my program moves along, i have been using the property node this works fine in the main vi but now i want to update it from a sub iv. any ideas?

Tip: The easiest way to accomplish this is to do the following:
In your top-level VI that has the control right-click on it and select Create-->Reference. This will allow you to place a reference in top-level VI's block diagram.
Create a new VI that will be your subVI.
Drag and drop the reference object from the block diagram of your top level VI to the front panel of your new subVI. This will create a reference control on your subVI that is of the same type as the control on your top-level VI.
Connect the reference control on your subVI to a connection terminal, and then wire the reference object in your top-level VI's block diagram to the subVI's input terminal.
Then, in your subVI you can just use the standard "Property" and "Invoke" nodes to fiddle with the control.

Similar Messages

To update the Associate node from se38 program

Hi Expert,
I am trying to update the bobf root node and associate node under it.
This is BOBF EHFND_DATA_AMOUNT custom enhanced z_***** , i can able to update the root node but for associate node created after enhancement its not updating.
Code i used is
           APPEND INITIAL LINE TO lt_mod ASSIGNING <ls_mod>.
          <ls_mod>-node        = if_ehs_ih_ehfnd_data_am_c=>SC_NODE-/SDR/EHS_IH_AMNPPE_ITEM.
*          /sdr/if_ehs_ih_ehfnd_data_am_c=>sc_association-root-ehs_ih_amnppe_item.
          <ls_mod>-change_mode = /bobf/if_frw_c=>SC_MODIFY_CREATE.
          <ls_mod>-key         = lr_s_amnppe_item->key.
          <ls_mod>-data        = lr_s_amnppe_item.
          <ls_mod>-association = /IF_EHS_IH_EHFND_DATA_AM_C=>SC_ASSOCIATION-/SDR/EHS_IH_AMNPPE_ITEM-/SDR/EHS_IH_AMNPPE_ITEM.
          <ls_mod>-source_node = if_ehfnd_amn_c=>SC_NODE-ROOT.
          <ls_mod>-source_key = lv_key.
          <ls_mod>-root_key    = lv_key.
*      Create the Amount record:
      CALL METHOD lo_driver->mo_svc_mngr->modify
        EXPORTING
          it_modification = lt_mod
        IMPORTING
          eo_change       = lo_change
          eo_message      = lo_message.
            "Check for errors:
      IF lo_message IS BOUND.
        IF lo_message->check( ) EQ abap_true.
          lo_driver->display_messages( lo_message ).
          RETURN.
        ENDIF.
      ENDIF.
      "Apply the transactional changes:
      CALL METHOD lo_driver->mo_txn_mngr->save
        IMPORTING
          eo_message = lo_message
          ev_rejected = lv_rejected.
      IF lv_rejected EQ abap_true.
        lo_driver->display_messages( lo_message ).
        RETURN.
      ENDIF.
but the above code is not helping to update the associate node from se38 program.
Regards
Sasikumar S
Can anybody help me on that thanks in advance.

Hi Sasi,
According to what you have written above, You want to update a Z node under a root node.
But in the coding for association you have written a standard node.
Give the name of the Z interface which is created and in that you will have the 'Z' custom created node.
Try this.
ls_mod>-association = "Z Interface"=>SC_ASSOCIATION-"root_node"-znode.
Hope this helps you.
Regards,
Sanket Vaity.

Changing the property node from an control in an cluster raises an error in LV2011

Hi, all
when I run the code in LV2010 SP1 no problems.
But in LV2011 it gives an error.
Is this an BUG
Attachments:
test.vi ‏18 KB

Franzo,
It certainly is strange. The error comes from the Width property node, but it occurs when ReadoutMode is clicked. It does not need to be changed.
Wrapping it in an event structure (ReadoutMode: Value Change) seems to eliminate the error.
Questions for someone at NI who knows how these things work internally: It is also interesting that the data type of the Maximum property is always DBL, regardless of the datatype of the control. Should not a U16 control have a U16 Maximum? And what about the Extended datatype? How can a value larger than the maximum for a DBL be set via a property node of type DBL?
Lynn

Set chart value (property node) from a waveform ARRAY?!?

Hi!
In Labview 8.0 I want to send data to a front panel chart via its value property node. This works just fine if I wire a single waveform to the value property (attachment1). However, if I wire it with a waveform array (attachment2) it fails. Is there any workaround?
Thanks in advance,
Rudolf
Attachments:
attachment1.PNG ‏3 KB
attachment2.PNG ‏3 KB

The reason I was showing this with only one graph was that
the
two-graph version failed for me. I had tried having separate data
sources, of course. Just to be sure I have rebuilt the VI from scratch
as per your diagram (see attached image and VI) and run it again with
the same results:
The failure was not in my inability to see the
plot but rather in an error message (attachment) which would only
occur if I tried to wire more than a single plot into the value node.
I subsequently also tried doing this using 1D and 2D DBL arrays and
observed a similar problem: the 1D case works fine, the 2D case throws
"insane object" errors and crashes labview entirely.
Message Edited by frumpel on 04-05-2007 10:53 AM
Attachments:
test1.vi ‏16 KB
block-diagram.PNG ‏33 KB
error-message.PNG ‏15 KB

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 activated even though it's been removed from Block Diagram

Hi,
I messed around with the property node of one of my controls and when I was finished and removed the property node from the block diagram it still makes my control blink.
How do I make it stop??
Is the option of Enable state not possible to set in property node mode. I'd like to go from disabled and grayed to enabled.
Thanks.
Solved!
Go to Solution.

Hi
Your blinking property might still be set. Add the property again to set it to False.
To set the enabled/disabled/grayed state use the "Disabled" property.
Hope this helps.

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!

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

Property Node in VI throws Error 7 in LV 7.1 but runs OK in LV80 and LV86

Hi everybody
I build a custom IVI instrument driver and using the LV tool <Generate VI Interface from Instrumnet CVI Driver> I was able to get a LV wrapper for each driver method. From LV86 I saved first in LV80 and from LV80 I saved as LV71. I have all these LV versions on installed on my PC.
I have no trouble in using these LV wrappers in any of these LV versions as they work OK.
Now my IVI driver has also Properties that the Import Driver Tool does not convert as a wrapper and for that reason I had to create a Property Node Warpper myself and saved in the same LLB under LV/instr.lib folder.
Once I have all these method wrappers and the property node wrappers I made a small VI
1. Initialize IVI With Options on a TCPIP instrument
2. Set-Get an IVI Timeout property
3 Close IVI driver on TCPIP instrument.
Good part is that in LV 86 and in LV 80 the VI is running fine when I use these LV version wrappers from their coresponding instr.lib folder.
As soon as I am going to use the LV 71 wrappers in LV 71 I could create the same small VI to Set/Get Timeout and the VI look OK nothing is broken but when I run it the Initialization is OK but as soon as is reaching the Timeout Set Property Node gets out an Error Code 7.
To run this VI the user need to install the jdCMR IVI driver then add the LV71 jdCMR wrappers inside LV71/instr.lib and then he may build any VI using these LV warppers.
The only problem is that the Property Node get out an Error Code 7 and the same error code get out from Property Node if I am picking the Property Node from VISA Advanced Pallette, connect this node to jdCMR driver, set Timeout property inside the node and after connecting the input and output references plus the input and output error to Initialize and Close LV wrappers I still get this error at running time.
The same LV 71 VI if I open in LV80 or in LV 86 runs without any problem?
Does anybody knows why LV 71 is not working the same way as LV80 and LV86 with respect to Property Node?
Btw When I save my VI from LV 80 to LV 71 I get this warning...
IVI Error Message Builder.vi
    Cannot save VI from VI.LIB to previous version.
Merge Errors.vi
    Cannot save VI from VI.LIB to previous version.
Thanks
Sorin

Hi
For further testing of the IVI driver Property Node bug with LabVIEW 7.1 IVI drivers I download and installed two different IVI drivers from two very known instrument companies, Rodhe-Schwarz and Agilent Technologies.
I have to mention that both these companies releasead their IVI NI LabVIEW 7.1 drivers under NI Instrument Driver Network and ready to be installed and used by any customer of these two instruments.
The bug is present only in LabVIEW 7.1 version as if I take the same VI that breaks in LabVIEW 7.1 I could run it without any problem in LabVIEW 8.0 or LabVIEW 8.6 versions.
Anybody could test this bug for these two NI released IVI drivers in simulation in LabVIEW 7.1 by following these links below.
Agilent ag81150ni IVI Driver for LabVIEW 7.1 install from here. Run in simulation only by setting Simulate=1
http://sine.ni.com/apps/utf8/niid_web_display.download_page?p_id_guid=55798957B1A633BDE0440003BA7CCD...
   Rodhe Schwarz rsngpt IVI Driver for LabVIEW 7.1 install from here. Run in simulation only by setting Simulate=1
http://sine.ni.com/apps/utf8/niid_web_display.download_page?p_id_guid=E3B19B3E91D6659CE034080020E748...
After installation complete close LabVIEW 7.1 if was open, then restart LabVIEW 7.1 and now you may see under the LabVIEW Instrument Driver Palette two new IVI drivers ready to be used as LabVIEW 7.1 wrappers.
Open a new blank VI and from Instrument Driver Palette use two well known Vis that are Initialize With Options.vi and Close.vi add them on your blank VI block diagram and connect thm together. Accept all default parameters except Simulate that must be Simulate=1.
Both Vis run OK in simulation mode without errors. Now pick a Property Node from VISA Advanced Panel and squeeze this between the Initialize With Options VI and Close VI and make the instrument reference in-out and error in-out connections.
Now run these two simple Vis in simulation
I run Rodhe Schwarz IVI driver and Property Node passes OK until the end
I run Agilent IVI driver but Property Node is getting out Error Code 7 that is the same as my own driver error.
Both these IVI drivers are under NI Instrument Driver Networks and have been built and integrated as native NI IVI instrument drivers.
Question is why they behave so different with respect to Property Node from the VISA Advanced Panel?
I attached the screen shots as PNG files that show clearly the difference of VISA Property Node behaviour when used under the same circumstances.
Thanks  Sorin
Attachments:
ScreenTestShots.zip ‏152 KB

Labview 2014 Excel Active X Property Nodes disabled - Why?

Hello,
I am using Labview 2014 and want to open, write to and close Excel by the use of Active X.
I am confronted with the problem, that, if connecting (Active X-) property nodes to the references (e.g. "Excel_Application"), right-clicking on the context menue doesn´t let me choose any properties, the item is disabled (one can read in German "Keine Eigenschaften" (no properties)).
How can I resolve this? What am I doing wrong?
Thank you!

I am having the same problem. When I left click to choose/change the property I do not get a list - instead I get the greyed No Properties popup - see screenshot.
If I drag and drop an existing property node from within an example subVI it connects to the reference and keeps showing the current property but I cannot change to a different one.
I am using LV 2012, Win7, Office 2013.
When I try with LV 2012, Win7, Office 2010, it works properly. So my guess is that is has to do with the version of office. But I would like to know the reason why as well.
Attachments:
NoProperties.png ‏67 KB

Tentative bug report: property node (and other objects) resizes structure in which they are dropped even when this is not needed

This one has bugged me for a while, so, since I am in a mood to report annoying features, here it is:
On the diagram, when you drop an object that could have its size increased by user action (for instance a property node in which you chose "Value", which is a short property, but you could later change this to a "longer" one, which admittedly might require more space on the diagram), a case structure in which you drop it, will automatically increase its size.
Let me illustrate this with ONE example (can be reproduced with other objects such as enums, clusters, etc...).
Here is a simple diagram:
Note that I am going to create a property node from the front panel. This, for a reason that makes the beauty of this "feature", is very important. Apparently, if you create the property node from the diagram, nothing weird happens. The exact location where I will drop the node is not very important but needs to be close enough from the border.
Here is the result (LV 2011 but as I said, this has bugged me for a few versions already):
Basically, the case structure (and the whole diagram as a matter of fact) has expanded.
This is particularly annoying, say, when you are creating a diagram with 10 cases in a case structure and you start dropping things such as property nodes in each case: the structure keeps growing, and growing, and growing...
That also works with Event structure, and I am ready to bet, with other as well.
As I said, it is also not limited to Property nodes. I have noticed that this happens if you drop a cluster constant that contains an enum (presumably because some of the enumerated strings are longer than others).
I could speculate why this is the case, but that is not my job.

Actually, this might not be true. I found a variant of this behavior. With "Place Structure with Auto Grow enabled" unchecked, here is what I observed while dropping a property node on my diagram:
Before:
After:
This is the expected behavior. The Property Node is partly hidden inside the Case Structure I dropped it in. Now that's not what I wanted to do. I wanted to drop it in in the innermost Case Structure:
The problem is that now this Structure has grown (as has the whole diagram) to leave space for the whole Property Node:
It is a subtle bug in the sense that I tried to reproduce it on a new VI with a series of nested Case Structures, but it did not result in this behavior.
Anybody caring to comment?

Error cluster in XControls Property node

Hello!
Property Nodes of XControls do have Error Clusters, but how can I change those out of the Facade? I'm setting an object through a property node for tree data. It is possible that some of the object methods generate an error while executing in the facade and I would like to catch this error in the VI containing my XControl.

You can't change the error output from a property node from within the facade since the facade only gets called after the property VI has run and modified the contents of the display state information. If possible try to catch invalid values in the property VI itsefl. If there are errors that the xcontrol will need to report you will need to provide a separate mechanism.
Something that I have used in the past to good effect is the idea of an error stack. The error stack itself is an array of error clusters that resides in the display state data and is maintained as a circular buffer by the xcontrol code. To access this value from the calling program create a read-only property that reads the contents of the buffer and then clears it.
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

Double Click Property Node not functioning with Queued State Machine

I am writing an application which relies on input from the operator to start different steps in a process of steps. I am using a queued state machine, however I cannot get the Double-Click property of my listbox to function with in this Queued state machine. I have tried Creating a refrence to the Listbox and creating a property node from that refrence. I have tried a property node of the control. The double click functon works only if the queueing is not occuring. It has something to do with the queue but I am at a loss as to what is causing it. Any help would be GREATLY appreciated. I have attached a simplified version of the state machine with the double click function. Thanks for any help on this. It is written in LV7.1
Attachments:
Test Q.llb ‏55 KB

Hi
Its Simple....
Your Properrty node is not getting read..... dont understand how..
see the attachment...
now laugh at your small mistake... (even i have the habbit of making such small mistakes ;-) )
Message Edited by Tushar Jambhekar on 01-11-2006 11:38 AM
Tushar Jambhekar
[email protected]
Jambhekar Automation Solutions
LabVIEW Consultancy, LabVIEW Training
Rent a LabVIEW Developer, My Blog
Attachments:
Test Q.llb ‏55 KB
Picture.JPG ‏44 KB

Using LV Class Property Nodes in In-place Element structure causes the code to halt

I have some code written in LV RT 2010 that uses property nodes from a LVOOP class that I created. I am using access the property node from inside an in-place element structure. When the code reaches the property node, LabVIEW stops running. (as if the abort button was pressed). I verified this behaviour using highlight execution. When I remove the in-place structure code runs fine.
Is this is know bug in LabVIEW? Is there a CAR to resolve this created for a future release?

Bob,
I tried to reproduce the behavior you're seeing by recreating the Trigger and Trigger List classes, but I have not been able to reproduce it. Please take a look at my version of the project in the attached zip file. Take a look at Test.vi, and feel free to modify and repost it to show me how to make the problem occur. I would like to file a CAR to make sure we get the problem fixed, but I will need to be able to reliably reproduce it first.
On a similar note, you can get much better performance out of the Process Triggers VI by preallocating the list array, instead of using build array in a loop. Take a look at Process Triggers2.vi in my project. You can run Benchmark.vi to see the performance difference between the two different approaches.
Chris M
Attachments:
triggerlist test.zip ‏165 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.

Updating a property node from a sub-vi

Similar Messages

Maybe you are looking for