How can I re-use the front panel of a sub-VI and have access to the terminals at the same time? I found out that I can re-use the front panel using the subpanel-control. In this case I don't have access to the terminals of the sub-VI. But I need them in my calling VI. As soon as I use the sub-VI in my block diagram and wire the terminals I get the Error 1000: The VI is not in a state compatible with this operation. I found out that this error occures if I call a VI multiple times. So as I said, if I remove the SubVI from the block diagram, the calling VI works, but I don't have access to the terminals any more.

@Exle wrote: I have updated the VI and started the other way round. I created the big Master-VI first. This one is working. Now the SubVI is being called four times. Now I see no way of including the dials (spannung, strom, kanal) into the SubVI without them being removed from the front panel. I Think you're confused. Apart from one improvement i'll come back to, this is how a program usually looks and should function. So no, you don't wan't that to be a sub-vi. What will happen is that you'll have a sub-vi with that White VI and those Controls as connectors, and you'll still need these Controls in the main VI to send the data, all in all you've just wrapped the White VI with a new Icon. The improvement you should do, however, is to Place those Controls in a Cluster and type-def it, then use an Array of that cluster instead of 4 copies. Then you can have a for loop with the White VI and an Unbundle fed by the Array of Control cluster. Also, remove those Reset Locals and just wire the Reset Control directly, else you'll get some strange effects later on, maybe tomorrow, maybe next week. /Y

LabVIEW

How to use the front panel and the terminals of a subVI simultaneously

Solved!

@altenbach wrote:

@Yamaeda wrote:

@altenbachThat's actually what i wrote in my first post, but if you forget to "Set values as default" or initialize that Array it can cause some issues that you won't have with 4 clusters, so i thought i'd let it slip. 🙂

Us graphical programmers are not good with words, so unless I see it on an image, i miss things (still cannot find it ;))

Yes, I mentioned to make the four-element array the default..

Yes, words can be hard sometimes. As is life. 😉
It's what i meant with my "Place those Controls in a Cluster and type-def it, then use an Array of that cluster instead of 4 copies."

Currently i'm on a non LV Project so can't really open and post code. 🙂

G# - Award winning reference based OOP for LV, for free! - Qestit VIPM GitHub

Qestit Systems