01-05-2004 12:34 PM
01-05-2004 01:47 PM
01-06-2004
11:18 AM
- last edited on
02-08-2026
01:45 PM
by
Content Cleaner
Hi,
If you do chose to use the call chain function, please read the following KB that discusses one limitation to it.
Why is the Parent VI Not Being Returned When I Use the Call Chain Function?
Feroz
06-23-2006 03:58 AM
06-23-2006 10:10 AM
06-26-2006
12:04 PM
- last edited on
02-08-2026
01:46 PM
by
Content Cleaner
Hi Raman,
Generally speaking, using "call by reference" or VI Server with an invoke node accomplish the same goal -- loading a VI dynamically. Many programmers have used this functionality to achieve a "plug in" architecture with their subvi's, since they do not have to be part of the top-level VI's hierarchy. The two methods differ from each other in two main ways:
1. Call by Reference allows to you to wire just like a subvi's (with a connector pane), but the VI must execute in sequence according to the dataflow on the parent block diagram.
2. Using an invoke node allows you to truly launch the VI "in parallel" to the calling (parent) VI. However, you must use Get/Set control value methods to send data to it...which can make your block diagram a little messier 🙂
You may also find these links helpful:
Using Call by Reference with VI Server
http://sine.ni.com/apps/we/niepd_web_display.display_epd4?p_guid=B45EACE3DA8056A4E034080020E74861&p_node=DZ53013&p_source=External
Call By Reference Node
https://www.ni.com/docs/en-US/bundle/labview-api-ref/page/functions/call-by-reference.html
Good luck!