I need to essentially do the same thing in 2 places: disabling here and enabling here. Take off highlight execution, enable them, run them, they’re all enabled. Now if I pull up my front panel, and put this on highlight execution, I can watch as one by one, I will disable each object. Now choose the disabled property, change to write, move this over, create a constant. How can I have this same property node access these references? Simple, create an array and auto-index it into a For Loop. If I want to use one generic property node on these other two objects I’ll need to create references for those. We have a perfect need for an explicitly linked property node in our current Test.vi as these 3 implicitly linked property nodes here and here are accessing the disabled property on 3 different front panel objects, these three. A common reason is to have a single property node access the same property of multiple objects.
![labview property node labview property node](https://www.thorlabs.com/images/tabimages/Kinesis_LabVIEW_D5e-350.png)
So why would we want to be so explicit? Let’s examine. This property node is explicit because I used this reference to explicitly point it to a particular object, and has the added benefit of not needing a parental advisory. The object is the Acquisition Rate Control. Now I’ve exposed all the same properties of the object with this explictly linked property node as I had with this implicitly linked property node. Now, I’ll pull up that same generic property node and wire the reference into the Reference input.
![labview property node labview property node](https://slidetodoc.com/presentation_image_h/8c92e575b0f1c0f09cab81c0c8be7b12/image-16.jpg)
I’ll right-click on Acquisition Rate and choose create>reference. We do that by creating a reference to an object. Well what’s that? I can create an explicitly linked property node by simply pulling up a generic property node, this property node can display the properties of any object, it just needs to be pointed to that object. Why are they called that? To differentiate them from explicitly linked property nodes. That’s what we really want and that’s what we’ll do now.įirst we’ll look at how we previously accessed the disable property: through these implicitly linked property nodes. At the end I asked if there exists an easy way to modularize what I’ve done and access the same disable property on all these objects without creating separate property nodes for each object each time I enable and disable. As we see here, these front panel objects being enabled or disabled with these property nodes. “In our last episode we learned about intuitivity and disabling and enabling front panel objects with property nodes.
LABVIEW PROPERTY NODE FULL
The full course also has a more excited narrator. This is a small part of the full content in the Sixclear Lucid LabVIEW Fundamentals Training (formerly Sixclear LabVIEW Fundamentals) course. As before, this is the first of two parts. We use references and refnums to create a Disable VI specifically made to enable and disable objects on the front panel of calling VIs. In this episode of VI High, we continue our discussion of intuitivity and conditionally enabling and disabling LabVIEW front panel objects.
LABVIEW PROPERTY NODE HOW TO
VI High 3 - How to Use Property Nodes in SubVIs through Use of LabVIEW Control References and Refnums