LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

How to create a cluster, whose elements are all scattered across the front panel?

You're right in saying that the cluster wouldn't get updated, however the wire will always carry the most current values.

If you run the wire through a loop in a shift register, you will always have the most recent values available to you.
0 Kudos
Message 11 of 19
(1,406 Views)
Sounds feasible, thanks! But what still bugs me is: where could I right-click on to create a "value" property node for further reference?
0 Kudos
Message 12 of 19
(1,405 Views)
It looks like if you create a customized control (Type Def) that is a large cluster that contains all of the override buttons in their desired positions, you can place the other controls on top of the cluster it without them becoming part of it.  The only problem is the shadows that are part of the controls that are on top.
Randall Pursley
0 Kudos
Message 13 of 19
(1,402 Views)
Hi Severin, yes, the resulting cluster will always reflect the values of the input controls (I just didn't put a loop around it). You can create an indicator for it, then right-click and hide it from the block diagram. Finally, access it with a local variable if you must use it somewhere that cannot be reached by a simple wire. I've attached the VI again.
 
 
0 Kudos
Message 14 of 19
(1,399 Views)
Great, this looks like it. How on earth did you get the "output cluster"? (The one in the left loop - the right one I assume is a "value" reference node, isn't it?)
0 Kudos
Message 15 of 19
(1,392 Views)
If you were to right click on the output of the bundle node, you can Create->Indicator.
0 Kudos
Message 16 of 19
(1,388 Views)
Wow, that was easy ;-).

Next I'd like to react if some of the buttons gets clicked. I've set up an event structure watching for changes in the cluster, but it doesn't react. See the attachment for a simplified example: monitoring the booleans directly (button 4) works, but monitoring the entire cluster (button 3) fails. It's just that I'd rather not define my event case as waiting for a change in one of 13 booleans.

Message Edited by severin on 06-22-2006 06:16 PM

0 Kudos
Message 17 of 19
(1,383 Views)
The one in the right loop is a local variable. You can right-click on either the front panel or block diagram object and do create --> local variable.
0 Kudos
Message 18 of 19
(1,370 Views)

The event structure generally monitors user events - which happen when a user clicks a *control*, but "output cluster" is an indicator. If you'd like to know whether the whole cluster changes, use a shift register...

N.B. To compare the cluster as a whole, right-click on the "not equal" function and "comparison mode" --> "compare aggregates". That'll give you a boolean output.

 

0 Kudos
Message 19 of 19
(1,367 Views)