From Friday, April 19th (11:00 PM CDT) through Saturday, April 20th (2:00 PM CDT), 2024, ni.com will undergo system upgrades that may result in temporary service interruption.

We appreciate your patience as we improve our online experience.

LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Trying to connect to an Executable with the Decktop Execution Toolkit.

Hi,

 

I am running LabVIEW 2012 f5 and trying to connect to a built executable using the 2013 Descktop Execution toolkit.

 

Ideally I would like to do this on a remote machine with only the RunTime Installed, but I am having so many problem I thought I would start of on a local machine, with the full 2012

development installed.

 

*  Firewalls are disabled.

* I can connect the DETT to the top level project in dev mode.

* Created a debug build executable. using this executable I can connect and run the executable in Trace mode from the dev environment using "Dubug Application"

 

But if I only run the executable then start the DETT I gat <LabVIEW>VI Server not found and a popup LabVIEW server access not enabled.

 

My labview ini file is below.

 

[SUB10-ATS-DEBUG]
server.app.propertiesEnabled=True
server.ole.enabled=True
server.tcp.acl="440000000900000001000000380000000001000000000000000000000000000000000000000000"
server.tcp.enabled=True
server.tcp.port=3368
server.tcp.paranoid=True
server.tcp.serviceName="+*"
server.vi.access=""
server.vi.callsEnabled=True
server.vi.propertiesEnabled=True
WebServer.TcpAccess="c+*"
WebServer.ViAccess="+*"
DebugServerEnabled=True
DebugServerWaitOnLaunch=False

 

I would be grateful for any help

Danny Thomson AshVire Ltd
0 Kudos
Message 1 of 2
(2,516 Views)

OK,

 

I have jst played around some more and managed to get it working ....yippeeee

 

my new ini file looks like ---

 

[SUB10-ATS-DEBUG]
server.app.propertiesEnabled=True
server.tcp.acl="310000000A000000010003110000000030000000000010000000000"
server.tcp.enabled=True
server.tcp.port=3368
server.tcp.paranoid=True
server.tcp.serviceName=""
server.vi.access="+*"
server.vi.callsEnabled=True
server.vi.propertiesEnabled=True
WebServer.TcpAccess="c+*"
WebServer.ViAccess="+*"
DebugServerEnabled=True
DebugServerWaitOnLaunch=False

 

The key difference is the serve.vi.acess="+*"   and adding in local host 127.0.0.1 into my VI server configuration.

Danny Thomson AshVire Ltd
Message 2 of 2
(2,506 Views)