Building SubVIs w/o Controls & Indicators

[super-neuron]

Must all subVI inputs & outputs be passed through controls(input) and indicators(output) on the front panel?

Can a subVI be block diagram only and be called/wired without using front end components?

I have several portions of labview functionality that I would like to wrap into small individual subVIs, and it seems odd that my only option for input/output is through controls/indicators.

[TCPlomp]

Don't look at the controls as GUI controls but as API interface nodes.
You can write a VI without any FP but it has no interface to the outside world.

Ton

[altenbach]

I agree with TonP.

Also remember that subVIs that don't have ther FP open, actually don't load or update their front panel (with a few exceptions where needed, e.g. if it prints its FP programmatically). There is little overhead calling a subVI that does not show its panel. You can also hide connected controls or indicators if they are not to be used by the operator.

Of course you could write a subVI that gets invoked exclusively via VI server and communicates with the rest of the wold via global or shared variables... but why??? That would be much more involved. 🙂

[super-neuron]

Ok guys, I hear what you're saying.   So how do I pass my "error in" and "error out" handling?

Please see attached...

[altenbach]

Right-click on the error input and "create control", right-click on the final error output and "create indicator". Now connect them to terminals on the connector pane. Move them offscreen or hide them if you don't want to see them.

What's wrong with that??

[TCPlomp]

Just create FP-controls for the Error in and out, and connect them to your conenctor pane.

Ton

[super-neuron]

Sweet!

That works like a champ!

Thank-you altenbach & TonP!