LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

remote panel / app bulder / external vi

I'm trying to use the application builder in order to make standalone applications of the "remotepanel" example that NI delivers with Labview. It constists of the VIs RemotePanelMethods-Client.vi, the RemotePanelMethods-Server.vi and the PowerSpectrumMeasurement.vi.

 

Everything is fine when I run this example within Labview. I'm also capable to build an executable for the client that works with the server run within Labview.

But when I try to build RemotePanelMethods-Server.vi  and run it standalone as an exe I have problems with the PowerSpectrumMeasurement.vi.

I get the message, that PowerSpectrumMeasurement.vi is not loaded into the memory of the server side.

The path to PowerSpectrumMeasurement.vi  is correct within the executable - otherwise I will get another failure at startup of the executable - so everything seems to me set up - but it doens't work.

 

I would be very grateful, if someone could provide a useful approach how to build an executable for the server side / RemotePanelMethods-Server.vi .

 

 

0 Kudos
Message 1 of 5
(2,360 Views)

Hi,

Do you use a Path Constant or a Relative paht? You can also try "dialog" as a path, so you will get pormpted and can manually choose the path. Just to be sure you get the right path.

 

Regards 

0 Kudos
Message 2 of 5
(2,328 Views)
0 Kudos
Message 3 of 5
(2,327 Views)

Well, I tried bot relative and avbsolute path - in the original example it's a relative path - but I saved Power Sepectrum Maesurement.vi to C:\Temp\PSM.vi and reassigned the path in the Remote Panel Server vi. When I run it under Labview everything is working fine. But when I generate an application out of the Remote Panel Server vi I get no repsonse on the client side and instead the error messge

 

Angefordertes VI ist nicht lauffähig und kann daher nicht angezeigt oder gesteuert werden.

 

which means in english :

 

Requested VI cannot be executed and bcause of that can't be shown or controled.

 

I'm puzzled because the only difference is that I run it here as an application - and not under Labview 2010, where everything works fine.

 

Do I have to do something during the build process in order to "include" the Power Sepectrum Maesurement.vi  / C:\Temp\PSM.vi  ???

0 Kudos
Message 4 of 5
(2,315 Views)

I think you should check the path. As you see in the Link below:

 

http://digital.ni.com/public.nsf/allkb/506F10CAD6E21EA786256E3100653CDD?OpenDocument

 

If the VI is part of a LabVIEW project, you must include the project name and the target in the VI name field.
For example: If MyVI.vi resides in a project called MyProject.lvproj under the target My Computer, enter the VI name as MyProject.lvproj/My Computer/MyVI.vi
Unlike the VI Name, the target name ( My Computer in the above example) is case sensitive.

0 Kudos
Message 5 of 5
(2,296 Views)