LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

remote vi call

Hi
I use VI server to run a remote VI. The client machine is
Windows NT and the server is Solaris 2. According to LabVIEW
manual the path should be written using the client machines
format (who came up with that brilliant idea?).
The Unix path is /home/qrajkla/My_VI.vi therefor I write
\home\qrajkla\My_VI.vi but it doesn't work. Open VI reference
returns error 7, file not found.
How should the path be written?
Regards
Jan


Sent via Deja.com http://www.deja.com/
Before you buy.
0 Kudos
Message 1 of 4
(1,907 Views)
Jan
I believe that you need a double slash at the beginning
it should be
\\home\qrajkla\My_VI.vi

also I have noticed that the Solaris version tries to differentiate
between \homes and \homes even if these are the same thing
Kevin Kent
jan_klasson@my-deja.com wrote:

> Hi
> I use VI server to run a remote VI. The client machine is
> Windows NT and the server is Solaris 2. According to LabVIEW
> manual the path should be written using the client machines
> format (who came up with that brilliant idea?).
> The Unix path is /home/qrajkla/My_VI.vi therefor I write
> \home\qrajkla\My_VI.vi but it doesn't work. Open VI reference
> returns error 7, file not found.
> How should the path be written?
> Regards
> Jan
>
> Sent via Deja.com http://www.deja.com/
> Before yo
u buy.
0 Kudos
Message 2 of 4
(1,907 Views)
> I use VI server to run a remote VI. The client machine is
> Windows NT and the server is Solaris 2. According to LabVIEW
> manual the path should be written using the client machines
> format (who came up with that brilliant idea?).
> The Unix path is /home/qrajkla/My_VI.vi therefor I write
> \home\qrajkla\My_VI.vi but it doesn't work. Open VI reference
> returns error 7, file not found.
> How should the path be written?

The path control is merely a display of a binary encoding of a
machine path. When a VI moves between OSes, the display of the
path changes, and similarly, when displaying a path, there is
no information telling the control what platform it is for; so
the syntax in terms if separator characters will be the client,
or whereever the diagram is being v
iewed.

The other thing that may work is to use something like ~grajkla\
My_VI.vi. I'm not positive, but I believe the relative path
won't be interpreted until it reaches the server; so that would
allow the shorthand to work. Another thing to watch for is that
Solaris and other unixes are case sensitive where Win and Mac
aren't. I don't think that is causing your problem, but it would
also lead to the same error message.

Greg McKaskle
0 Kudos
Message 3 of 4
(1,907 Views)
In article <38EAAB46.1E003F51@austin.rr.com>,
gmckaskle@austin.rr.com wrote:
> > I use VI server to run a remote VI. The client machine is
> > Windows NT and the server is Solaris 2. According to LabVIEW
> > manual the path should be written using the client machines
> > format (who came up with that brilliant idea?).
> > The Unix path is /home/qrajkla/My_VI.vi therefor I write
> > \home\qrajkla\My_VI.vi but it doesn't work. Open VI reference
> > returns error 7, file not found.
> > How should the path be written?
>
> The path control is merely a display of a binary encoding of a
> machine path. When a VI moves between OSes, the display of the
> path changes, and similarly, when displaying a path, there is
> no information telling the control what platform it is for; so
> the syntax in terms if separator characters will be the client,
> or whereever the diagram is being viewed.
>
> The other thing that may work is to use something like ~grajkla\
> My_VI.vi. I'm not positive, but I believe the relative path
> won't be interpreted until it reaches the server; so that would
> allow the shorthand to work. Another thing to watch for is that
> Solaris and other unixes are case sensitive where Win and Mac
> aren't. I don't think that is causing your problem, but it would
> also lead to the same error message.
>
> Greg McKaskle
>

Hi

thanks for your suggestions Kevin and Greg.
However neither \\home... or ~qrajkla... works. I just got
it to work! This is the the way it should look like:
home:\qrajkla\My_VI.vi

This is not intuitive! How is anyone supposed to figure that out?
I used the array to path VI and then LabVIEW created the path above.

If the client machine is unix and the server is
Windows it will be equally weard. C:\qrajkla\My_VI.vi should be written
/c/qrajka/My_VI.vi.

It would be better to use a platform independent
way of describing the path (a URL). Or modify the VI's to take a path
in the target platforms format. Then I could just ask the remote
LabVIEW application which OS it's running on and build a correct path
with that information.

Thanks

Jan


Sent via Deja.com http://www.deja.com/
Before you buy.
0 Kudos
Message 4 of 4
(1,907 Views)