Opening a Remote Panel of the Top Level vi for an executable

[John_Neutron]

Hello Everyone

I was wondering how you would open up a remote panel for the top-level vi in an executable?

I have created a LabVIEW application and have tested opening the remote panel when it is running in the full labview development suite - this all works fine. I simply go operate>connect to remote panel and enter the server address, the port (8000) and the vi name using the path "My Project.lvproh/My Computer/main.vi" format.

However, if I then build this application into an executable I do not seem to be able to open a remote panel - it might be that I am just entering the VI name incorrectly.

with VI name = "main.vi"  or with VI name = "C:\builds\main.exe\main.vi" and the exe. running I get the error:

Connecting to remote panel server...
Requested VI is not loaded into memory on the server computer

However I am not sure how else I would enter it.

The main.ini has the following configuration:

server.app.propertiesEnabled=True
server.ole.enabled=True
server.tcp.acl="0800000008000000"
server.tcp.enabled=True
server.tcp.paranoid=True
server.tcp.port=6363
server.tcp.serviceName=""
server.vi.access=""
server.vi.callsEnabled=True
server.vi.propertiesEnabled=True
WebServer.Enabled=True
WebServer.TcpAccess="c+*"
WebServer.ViAccess="+*"
DebugServerEnabled=True
DebugServerWaitOnLaunch=False

Both machines have LabVIEW 2011 Profesional Development System SP1 on so I do not think it is a limited remote access licence issue.

Any suggestions as to where I am going wrong would be much appreciated.

Cheers

John

[John_Neutron]

Am I to take it from this document that the only way of using remote panels with an executable is through a web browser?

http://digital.ni.com/public.nsf/allkb/6F58D8300ACB743C862579F8006E2800

Cheers

John

[John_Neutron · Accepted solution]

It appears that you can infact use remote panels within an executable.

The problem I had was that I had left the web server port for the remote panels the same as the LabVIEW development environment. That meant that the main LabVIEW web server was getting in the way of the web server that was associated with my built application.

With the application's web server on a different port and the VI in memory (and the file in a library/directory external to the exe if it is not the top level VI), you just need to specify the VI name such as main.vi .

Solved!