Invoking remote VI's

[jan_klasson@my-deja.com]

I want to call a VI in a remote LabVIEW application. I use the Open VI
Reference to open a reference to the remote VI. However it seems like
this VI requires me to give a full path or ensure that the VI is already
loaded in memory if I provide only VI name.

How can I call a VI in a remote LabVIEW application if I only now the VI
name?

Regards
Jan Klasson


Sent via Deja.com http://www.deja.com/
Before you buy.

[Greg_McKaskle2]

> I want to call a VI in a remote LabVIEW application. I use the Open VI
> Reference to open a reference to the remote VI. However it seems like
> this VI requires me to give a full path or ensure that the VI is already
> loaded in memory if I provide only VI name.
>
> How can I call a VI in a remote LabVIEW application if I only now the VI
> name?
>

A hard disk can be a big lonely place. The best workaround is to orgnize
the VIs so that they are in a known place or in one of several known places.
If the VI isn't in one location, then the Open will fail with a specific
error, and you can check another location. This is not something that you
will want to do to every file on the disk. That would take much longer
than you probably want.

Another way to do this is t
o have in a known location an agent that can
do the search looking for the Vi file and return the file.

Greg McKaskle

[jan_klasson@my-deja.com]

In article <387D3EEC.F850FAD9@austin.rr.com>,
gmckaskle@austin.rr.com wrote:
> > I want to call a VI in a remote LabVIEW application. I use the Open
VI
> > Reference to open a reference to the remote VI. However it seems
like
> > this VI requires me to give a full path or ensure that the VI is
already
> > loaded in memory if I provide only VI name.
> >
> > How can I call a VI in a remote LabVIEW application if I only now
the VI
> > name?
> >
>
> A hard disk can be a big lonely place. The best workaround is to
orgnize
> the VIs so that they are in a known place or in one of several known
places.
> If the VI isn't in one location, then the Open will fail with a
specific
> error, and you can check another location. This is not something that
you
>
will want to do to every file on the disk. That would take much
longer
> than you probably want.
>
> Another way to do this is to have in a known location an agent that
can
> do the search looking for the Vi file and return the file.
>
> Greg McKaskle
>

OK, thanks Greg.

However, I belive LabVIEW ought to supply a function for finding and
loading a VI by using VI search path. This would be much easier, and it
would be a natural solution.
In my app I can probably assure that the VI is allways loaded.

Regards
Jan


Sent via Deja.com http://www.deja.com/
Before you buy.