03-30-2010 04:07 PM
This probably explains the problem. VI server access for an executable is enabled in the .ini file that must be in the same folder with the application (at least until LV 8.6, I guess this didn't change for LV 2009).
If you have MyApp.exe, you need MyApp.ini in the same folder. It will be created if it doesn't exist.
MyApp.ini controls VI server access to MyApp.exe.
MyApp.ini should contain the following lines (can contain a lot more) for VI server to work:
[MyApp]
server.tcp.enabled=True
server.tcp.port=3364
server.tcp.acl="290000000A000000010000001D00000003000000010000002A10000000030000000000010000000000"
The acl (access control list) value above enables access from any machine. Check also this KB article for more information about the acl.
The port can be adjusted to your needs.
03-30-2010 10:47 PM
Hi dan_u,
Thank you for your help. I will try it and will let you know.
Thanks again.
04-08-2010 11:01 PM
Just to add, NI stopped support to data communication with remote LV application from LV8.2 onwards. If you check the ini of the application built using LV7.1, you will see the VI server strings for TCP communication in that. Also, to pass data to specific VIs in exe, you could also use "All VIs in memory" from invoke node for the reference of remote app and then pass on the desired values.