LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

How to execute a reentrant vi?

There are some good shipping examples that help explain the Asynchronous call by reference functions too.


"Should be" isn't "Is" -Jay
Message 11 of 14
(845 Views)

Thank you.

Another question abaout reentrant-vi.

My dummy-construction with dummy-vis is now working.

Later i want to replace the dummy-vi with instrument-control-vis.

So i will have one vi setup as reentrant that contains three other vis (config, measure, read)

-->Do i have to setup ALL subvis also as reentrant or are they automatically reentrant if the are called by a reentrant vi?

And do i have to close the references created by the "Opne Vi Reference?

 

Thx

0 Kudos
Message 12 of 14
(832 Views)

You can mix reentrancy without problems, just be wary of the effects of your choice ... Reentrancy isn't inherited. A config-vi can be reentrant if the settings are permanent or handled in other manners, as configuring a com-port. Once it's set it's "permanent" and you can happily set other ports simultaneously, thus a decent candidate for reentrancy.

Some information is unique to the instance, so it might "disappear" if spawning new ones, the simple solution to this is to send all data needed as inputs.

 

Stuff like that.

/Y

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

Qestit Systems
Certified-LabVIEW-Developer
0 Kudos
Message 13 of 14
(824 Views)
Check the help file for namespaces. And my tag cloud might offer something if you can decrypt it. This will be a learning experience. I'll try to post links when I'm near a PC.

"Should be" isn't "Is" -Jay
0 Kudos
Message 14 of 14
(817 Views)