LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

labeling clusters

Take your front panel cluster, right click the first label and go to Visible/Label.  Type in the name you want.  Do the same for the second.  I'm not sure what you mean by you can only do it for the first one.
 
Second.  Take the local variable of that cluster and put it into the middle terminal of the bundle cluster function.    Better yet is to use a bundle by name function.  When you wire a cluster into a bundle by name, it will populate all the fields with the names of the cluster, and make it easier to know you are wiring to the correct part of the cluster.
Message 11 of 15
(713 Views)
Hi exo,

you shouldn't hate subvis, they make your diagram a much less messy Smiley Very Happy

And to use locals to have less wiring (programming like you would use a textual programming language) results in:
- most often race conditions
- always using more memory due to data copies
- slower execution due to disabling optimizations of the LabView compiler
Best regards,
GerdW


using LV2016/2019/2021 on Win10/11+cRIO, TestStand2016/2019
0 Kudos
Message 12 of 15
(712 Views)
Gerd
Thanks.
I don't think memory will be a problem; Speed shouldn't be either although I will keep this in mind. I'm not sure what you mean by a race condition.
0 Kudos
Message 13 of 15
(708 Views)
Hi exo,

just use the search function.
Race condition means there is no execution order given for several read and write accesses to a local. So it may happen you read from a local even before the first value is written to...

Best regards,
GerdW


using LV2016/2019/2021 on Win10/11+cRIO, TestStand2016/2019
0 Kudos
Message 14 of 15
(700 Views)
How many times should I rate someone per topic? 🙂
0 Kudos
Message 15 of 15
(695 Views)