Hello,
I am new to VEE and I have some functionalities in Labview as .vi files and I want to call them in VEE program. I converted the .vi files to executable (.exe) as suggested in the user manual and tried to run the program. It works but I have to control over the input to the .vi function. In simple terms, I want to pass parameters from VEE program to the called .vi object.
Please suggest.
I am new to VEE and I have some functionalities in Labview as .vi files and I want to call them in VEE program. I converted the .vi files to executable (.exe) as suggested in the user manual and tried to run the program. It works but I have to control over the input to the .vi function. In simple terms, I want to pass parameters from VEE program to the called .vi object.
Please suggest.
This should be doable in that you'll create a command line on-the-fly.
Start with the execute program object ( I/O -> Execute Program )
You can probably write in the working directory to the executable directly and, optionally, set the Run Style to minimised.
Add an input pin ( object menu -> Add Terminal -> Data Input... ) and select Command.
Now you need a Formula object ( Device -> Formula ) to build your command-plus-parameters string. Say you have 2 inputs on the formula box labelled V & I and your excutable is called SetupPSU.exe, then your formula would look like this ( quotes & spaces included ):
"SetupPSU.exe " + V + " " + I
which would be the same as typing on the command line
SetupPSU.exe 3.2 1.0
Let us know how you get on.
I have a feeling, depending on the application, that you might want to call it from the DOS command processor, in which case it would need to start with cmd / c SetupPSU.exe
but that might be only if you don't want the window to show up, sorry I can't quite remember the details of that.
If the above doesn't work straight off:
1. check the command syntax entered in a Windows command window ( that is, you type it in manually to check it works )
2. check the text coming out of the 'create command line' formula box matches point 1.
3. try calling the executable by typing in the command-plus-arguments in the Execute Program object
Mike