LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Remote Panels and FPGA

Hello,

 

trying to add a remote panel to my VI I run into some trouble. I'm using LV2009 32bit (server side Win7 64bit, client side XP 32 bit).

 

First I set up the web server and established one simple connection using the LV example "power spectrum". That went quite nice.

 

After that I just tried to pass the user interface vi of my current project to the server and got an error. I guess that this was due to the fact that the vi is part of a project. But even if I use the notation <projectname.lvproj/MyComputer/vi-name.vi> I always get the error "LabVIEW:  Client does not have access to specified VI.". Also I made sure that the respective vi is part of the server's access list.

 

Now I have the possibility to run my server as part of the same project (I always get the error above) or to run it separately. In case of a normal vi that works fine. If my project uses FPGA then I get into even bigger trouble when I try to start the server from outside the project because:

 

all my FPGA-references inside all sub-vis were broken (!!!) and I could only recover my project by means of

 

(1) restart LV _and_

(2) change the execution system of the FPGA to "Development Computer" and back.

 

 

Is there anything that I may have ignored. Or just to ask the simple question: is it possible at all to access LV-FPGA-vis via remote panels?

 

 

Best regards,

\Ulli.

0 Kudos
Message 1 of 2
(2,452 Views)

Ok. since this topic seems to be a bit special, I would like to go one step back.

 

The issue that I described when starting this thread is the one that gets me into trouble. But the cause may be related to the fact that I'm not able to access VIs that are part of any project.

 

This is what I have done:

 

- Created a small project containing a VI that does some RS232-control and exposes a user interface.

 

- Enabled the webserver, allowed access to the client computer and made the RS232-control-VI visible.

 

- Added the NI example "RemotePanelMethods-Server.vi" to the project and inside changed the path to the vi to run in the server to my RS232-control.

 

- Run the modified server example.

 

- Run the NI example "RemotePanelMethods-Client.vi" on the client computer after specifying the correct ip of the server computer.

 

 

This is what happens:

 

- If I run the server VI as an instance of the project and the client only with the name of the RS232-control I get an error 1352 saying "LabVIEW:  Requested VI is not loaded into memory on the server computer." This is what I would expect to get, because that VI is part of a project.

 

- If I run the VI server as a project instance again and the client with the project name like <project name/My Computer/RS232-control name.vi> then I get error 1349 saying: "LabVIEW:  Client does not have access to specified VI.".

 

- The same happens when I run the VI server as main application instance and client with project name specified (error 1349 again).

 

- The only way to succeed in accessing my project bound VI is to start the VI server as main application instance and the client with just the name of the desired VI.

 

 

For me this seems not to be in accordance with the LV help wich says the following:

 

"... To specify a VI that is part of a LabVIEW project, you must include the project name, the project library name, and the target in the path of the VI, when applicable. For example, if MyVI.vi resides in a project called MyProject.lvproj under target My Computer, enter the VI name as MyProject.lvproj/My Computer/MyVI.vi. If the VI is owned by a project library called MyLibrary, also include the project library in the path, as in MyProject.lvproj/My Computer/MyLibrary.lvlib:MyVI.vi. If the VI is not in a project or project library, you can enter the VI name without any additional information. ..."

 

 Does anyone know about some pitfalls that I might be not aware of?

 

I'm really distressed with that issue and would appreciate your help very much.

 

 

Best regards,

\Ulli.

 

 

0 Kudos
Message 2 of 2
(2,433 Views)