How can I find out which vi's are dynamic?

[Wiebe@CARYA]

But remember that dynamic VI's can call other VI's dynamically. So if you
found one, you need to open it, and search again, until you don't find new
ones.

I ofter create a sub VI that opens the references (with some path handling
or other Vi properties in it). You also need to find all instances of VI's
with the Open VI ref. in it (if the path/VI name is an input of the VI).

Another way to open a dynamic VI is through the system exec. function, but
that doesn't serve any real purpose. Don't worry about it, I used it one in
8 year, and that was for testing only.

Static VI references can also be used to use VI server (and to start VI's
dynamically). But LabVIEW recognises them, and includes them in the build.
They are underrated, and should be used in a lot of cases in stead of Open
VI Reference.

Regards,

Wiebe.

[MikeS81]

Hi Wiebe,

how can you open a vi with System Exec and work with it like opened with "open VI Refernce"? It sounds interesting, can you explain it please?

Thanks

Mike

[TCPlomp]

You can call LabVIEW with a path parameter and a port number.

Here's the tricky thing (I think).
If the calling app listens on that port, the called LabVIEW loads the VI from the path. And that will connect to the calling app, setting up a VI server reference.

Ton

[MikeS81]

Thanks TonP

Mike

[Wiebe@CARYA]

Starting a VI in an exe (LabVIEW.exe or a custom LV executable) works like
this:

Call the system exec. with parameter:

LVPATH\LabVIEW.exe "VIPATH\viname.vi"

Where LVPATH and VIPATH are the paths to the exe and the vi to start. This
loads the VI in the refered exe. I'm not sure if the VI is started
automatically, but I think so, it might depend on the VI settings (run when
opened).

This is great for debugging: Make an application with data buffers, user
events, you name it... Then you find out you forgot some debugging screen
(to monitor buffer values or something). Make the VI, and start it in the
exe. No need to recompile. No worries about security, since the debugging VI
is not even shipped with the distribution!

Regards,

Wiebe.

[MikeS81]

Thanks for the description.
Mike