VI Server - Open VI Reference is using local path, not remote

[mschmit]

First time posting to NI Developer Zone, so bear with me.

I have a PXI-1050 chassis with a PXI-8187 controller that runs LabView RT.  I have set up this PXI system to utilize a VI server on port 3363 and opened access to my host PC which runs LabView 8.2 with the RT module.

I am having trouble openning a remote VI using the VI Server and the "Open VI Reference" function.  I am fairly certain that the VI server is connecting using the "Open Application Reference" function, but it seems that the vi I wish to run cannot be found.

Here is the error that is thrown back to me
"Error 7

Possible reason(s):

LabVIEW:  File not found. The file might have been moved or deleted, or the file path might be incorrectly formatted for the operating system. For example, use \ as path separators on Windows, : on Mac OS, and / on Linux. Verify that the path is correct using the command prompt or file explorer.
=========================
NI-488:  Non-existent board.

VI Path: D:\LabView_Projects\VI_Server_Test_Project\/ni-rt/startup/temp_1.vi"

You will notice that the "Open VI Reference" is prepending the local path 'D:\LabView_Projects\VI_Server_Test_Project\' to my remote path.  If I specify the path using Windows style path, e.g. 'c:\ni-rt\startup\temp_1.vi', again the remote VI cannot be found.  I think I am missing something trivial, but I don't know what it is.

Thoughts?

[mschmit]

OK, I think I figured it out, but I'm having some other problem with this.  I'm uploading the VI, the Project, and the Library that I'm using.

Message Edited by mschmit on 03-05-2007 08:28 AM

[mschmit]

The problem that I'm having is that it simply isn't working and I'm not sure why.  I know there's some problem with the file references because it throws an error at the end about closing the references, but other than that I'm not sure why my shared variables aren't transmitting properly.

[JaimeC]

What are you trying to do?????????'

You just open vi server in your RT for your RT. And just open the vi reference and close it. You do not run the vi, neither specify the exact path.

Are you trying to call a vi that is on the Host?

Are you trying to run an exe on your target with VI server from the host?

Sorry but with that project I cannot see anything...

Error 7 means that the file is not found, so the target or host specified or the file path is wrong,

Pls upload your code again an explain clearly what you want to do.

[mschmit]

I'm sorry I was not very clear in my previous postings.  Let me see if I can clear this up.

Goal: I would like to have a 'Host  VI' run on my host machine (LV 8.2), which opens up a 'Target VI' on an RT machine (located on the network) to perform a data adquisition task.  The RT machine will also perform some data logging and analysis.  I have sucessfully programmed the data adquistion, the logging, and the host VI. What I cannot figure out is how to call the Target VI automatically from the Host VI.  Right now I have to manually start the Target VI and I'd like to avoid this if possible.

Procedure: Using the VI server I open up an Application Reference, and then a VI Reference, and then using a VI Sever Property Node I tell that Target VI to run on open.  When I'm done, I tell close the reference.  This seems straight forward to me.  Am I missing something?

One of the other problems that I'm having is I don't know where the target.vi and variable libraries are downloaded to on the RT target.  I cannot find them when I FTP into the system.  How can I specify the path if I don't know where they go?  Do I have to FTP the Target VI and libraries to the RT machine manually?  Shouldn't this be automatic?

I am uploading a simplified code to see if it makes it clear what I'm trying to do.  Thanks for the response.

Message Edited by mschmit on 03-06-2007 04:13 AM

[JaimeC]

Several things:

1. When u open the vi reference u must use and invoke node to make the Run vi, if you dont make it the vi is loaded but not running.

2. Insert correctly the path on your RT and the IP of your RT target

3. is better to have the variables on your HOST than on your RT becoz of two things:

            - Not to use resources of your RT system as memory etc... is better to use the host ones that are more available

            - The library needs to be deployed when running the vi on the host. If you put it on the RT it would need to be redeployed, so it is better to leave it on the host becoz of that.

4. Then as the library is on the host it needs to be deployed with the proper invoke node inside a stacked sequence to ensure is the first thing you do.

5. The enable RT fifo on the variables is used only to pass data between different vi's or processes inside the RT, it has no sense to enable it when sharing data RT - Host coz it is not possible, Shared variable work with TCP/IP not as RT FIFO.

See the attached vi for extra info.

I give u these extra links for your info:

http://digital.ni.com/public.nsf/websearch/F4010DD5C8D1B13D862565BC007384E9?OpenDocument

http://digital.ni.com/public.nsf/websearch/04D9A85B6967EE87862571140065EEC6?OpenDocument

http://digital.ni.com/public.nsf/websearch/48D244EC86971D3986256BD4005CCC28?OpenDocument