LabVIEW
Array to cluster from one Sub VI to another Sub VI
Hi Msony,
use Bundle/Unbundle as shown by Koen.
I would strongly suggest to learn to use type-defined clusters to use (Un)BundleByName and to easy applying changes to that cluster across several VIs...
Msony wrote:I have a Sub VI which consists outputs of all six 1D arrays of booleans (single array has 9 to 10 booleans) and i have to use them in another Sub VI in the same program by which i can change the status of individual booleans.
It is not clear. The post title, you mentions "cluster", but the body of the post does not. What datatypes do you actually have?
What is your question? Do you have problems changing booleans in arrrays? Problems with using subVI connectors? How are you trying to "change" them, whatever that means.
Please attach a simplified set of VIs that demonstrates the problem. Thanks!
An edit to my reply,,
This is probably the way GerdW meant (better solution):
The big pro of this system is that you can give the different elements of the cluster a custom name.
When you unbundle you also have the option to only chose one element.
Only con to this concept is that it takes more space in general. But it makes things more clear especially when you use the cluster over different Subvi's!
Hi Msony,
and what's the problem here? You already have those boolean arrays as outputs of your VI, so you just need to wire them to your next subVI...
Btw. I would store those booleans as arrays (or even U8/U16 numbers) inside your cluster. Much less effort: DAQmx also takes unsigned numbers to output DO values and you don't need to convert from cluster to array (and vice-versa) constantly...
This one is the same as your VI, but without local variables and case structure:
Plus it automatically adapts to changes of your boolean clusters inside the big cluster...
Hello,
If this is Subvi who transmit it's data to a second subvi (correct me if I'm wrong) why would you already unbundle.
If my statement is correct you can better transmit the whole cluster itself
Btw you have to connect to error outs the error ins of the different property nodes.
Hi Koen,
why would you need to wire all the error cluster lines?
That's only needed to enforce DATAFLOW, but in this case it's already done by the case structure itself...
The OP may use this subVI similar to a "property VI" in an OOP-like style: you feed the cluster (the OOP object) and you get the data (OOP properties) for subsequent processing...
