LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Labview Executable - Missing .ini file for VI Server

Solved!
Go to solution

I have a LabVIEW executable (.exe) file that runs perfectly when I execute it.  The problem I have is that I did not build this executable.  I need a way to access its .ini file so that I can add the following lines:

 

server.tcp.enabled=True
server.tcp.port=3390

 

My ultimate goal is for this .exe to run and to set up a Server VI such that I can control the .exe front panel from my own custom VI.  (Simulate button clicks, query for data from indicators, etc.)

 

According to my searching this is the best approach and will likely work for my needs; however, I just can't find how to edit the .ini for the executable since it did not come with one and doesn't create one upon execution (as it supposedly should).

 

Anyone have any tips or ways to go about doing this?  Thanks!

 

**Note: I'm using Windows XP if that matters.  Perhaps the .ini gets stored in a seperate directory?

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
If someone helped you out, please select their post as the solution and/or give them Kudos!
0 Kudos
Message 1 of 3
(2,962 Views)
Solution
Accepted by topic author MrHappyAsthma

Hi,

 

Let’s try the second method from the link below.

http://digital.ni.com/public.nsf/websearch/65F76F247012DF68862562C70073BE06?OpenDocument

 

Let me know if that work for you.

 

Regards,

 

 

Richard.

Message 2 of 3
(2,925 Views)

When you build an executable in LabVIEW (LabVIEW 7.0 through LabVIEW 2012, at least), at least two files are created in the same directory -- My Application.exe and My Application.ini (note "My Application" is a default name -- your application, I hope, has a more appropriate name).  The .ini file has a [My Application] section in which you put the Keys (such as the ones you listed).

 

Note that if you move your executable file, you just need to move the .ini file to the same folder.  If you've "lost" the .ini file, you can use NotePad to easily recreate it.

Message 3 of 3
(2,912 Views)