Control exe from labview

I was wondering is there a way that I can run and pass parameters to exe file from the labview program. If yes then please enlighten me..
In anticipation of reply
cheers
Priiyank

On the Communication palette, select System Exec. The on-line should explain how to use it.

Similar Messages

Pda execute other exe from Labview

I'm looking for ways to execute an exe from Labview PDA that is stored on the PDA (another PDA application)... I'm running WM5.0 ... .any ideas ...
Greycat

Hey Greycat.
That is a great question! So as you noticed there is no equivalent to System Exec in LabVIEW PDA, so you cannot launch an application that way. I would think that there would be a DLL that could be called on the PDA that will allow you to launch applications. However, after several Google searches I was not able to come up with any specific code or DLLs. Once you found that DLL hoewever, you shouldn't have problems launch an EXE. I am assuming that these are not other LabVIEW PDA built EXEs, which is a shame since you might be able to open a VI reference to that VI.
Andy F.
Message Edited by Andy F. on 04-25-2006 06:52 PM
National Instruments

Control a LabVIEW GUI exe from LabVIEW

I have a vendor supplied LabVIEW.exe application, it's used to control a device that's part of an automated manufacturing process. At present we need to manually run the exe from the control PC , read data, make a decision, then input a few values, button clicks etc. I'd like to automate this step. Without having the source code for the application, what options do I have for controlling this application from LabVIEW?
I tried using System Exec.vi, but I got beat when I needed to right-click on a graph indicator to retrieve data. LabVIEW applications don't accept SHIFT+f10 for right-click.
What other methods can I use to communicate with this application?

Dennis_Knutson wrote:
On the other hand, if the specifications that you provided to the software vendor did not include these requirements, then the vendor would be quite reasonable in asking for additional money to make the changes. You should also have required that the source code be provided.
Of course, this is true. I was making an assumption, that since the OP has experience in LabVIEW, these sort of things had already been taken into consideration by the buyer.
Would source code normally be provided when someone purchases an EXE? If there are proprietary pieces in there (algorithms, etc.), I thought it would be more common for the vendor to just provide hooks to the control and data functions.
Cameron
To err is human, but to really foul it up requires a computer.
The optimist believes we are in the best of all possible worlds - the pessimist fears this is true.
Profanity is the one language all programmers know best.
An expert is someone who has made all the possible mistakes.
To learn something about LabVIEW at no extra cost, work the online LabVIEW tutorial(s):
LabVIEW Unit 1 - Getting Started
Learn to Use LabVIEW with MyDAQ

How to call Exe from labview?

Hello NI,
I want to call the exe from the labview. presently i am using command.vi to open the exe. but it works only with source code. after creating the exe it doesnt work.
I checked the path of exe.
do you have any solution for this?
Regards,
Balaji DP

Working directory should be c:\windows\system32
copy your winword.exe into that system32 folder and just try this
Message Edited by mathan on 01-06-2009 03:24 AM
Attachments:
untitled.PNG ‏3 KB

Control OpenOffice from LabVIEW

Does anyone know how to automate OpenOffice applications from LabVIEW?

Are you wanting to have labview automate open excel or word or access. If this is what you are asking then here is an example for word.
Joe
Joe.
"NOTHING IS EVER EASY"
Attachments:
View_word_document_file.vi ‏29 KB

Control keypad from labview

Hi,
I would like to connect a keypad 4x4 and monitor it from Labview.
In the past I implemented a simple algorithm which scans the rows and coloumns of the matrix, but is there an easier way to do this in Labview?
I don't mean a virtual keypad, but an actual one. I would like to use Crio with RT as my controller
Thanks,
Eyal.

Hi Braxat. WHy don't you use the parallel port of your computer? it's a mini-DIO port. Just to give you an idea.
To just read a keypad, it's a really expensive solution to use c-Rio
Kind regards,
BJorn Conjaerts
Kind regards,
- Bjorn -
Have fun using LabVIEW... and if you like my answer, please pay me back in Kudo's
LabVIEW 5.1 - LabVIEW 2012

Control solenoid from labview

Hi all,
I am having a solenoid valve to be controlled from my labview program from a computer.
I already have an interface that is built to switch the solenoid valve on/off.
But I dont have any information on the interface. The interface is provided with a PCI DIO 96 card to communicate with the computer.
The interface has a "ni sc 2054" (24 VDC) accessory and its connected to a "Grayhill 16 channel rack". I couldn't really understand the interface.
I need to switch the solenoid on/off using the PCI DIO 96 card. Can I do that without the knowledge of what's in the interface? The interface is working with a Windows 98 system but there is no way to view its code or make it work on the system with Windows XP. Does labview provide with this abstraction so that I can use DAQ and operate the solenoid without knowing what it actually does?
Or its ok even if I have to purchase a new hardware to control the solenoid. Any solution which doesn include the interface or with a new setup in the middle is also appreciated.
I have attached a snapshot of the circuit inside the interface, but I dont think if it will be really useful.
Thanks for your help.
VJ
Attachments:
Picture 048.jpg ‏1101 KB

Hi Vijay,
Looks like you've got an opto isolation board populated with "output" opto relays. (Those are the red blocks on the Grayhill board)
Your Opto board is connected to a "Breakout" board, and that is connected to your DIO 96 card.
This is a setup we use all the time. You shouldn't need new hardware to operate your solenoid valve.
I'm not sure from your question if you want to add a new solenoid to your existing hardware, or if you just want to control an existing one.
If you've already got your solenoid wired up, you need to know what channel (line) it's on. The numbers beside the red blocks on the Grayhill board indicate which line each block is on.
An easy way to test your wiring connection without writing any code is to start Measurement and Automation Explorer. There should be a link to it from your National Instruments Start menu.
Start that program, and look for something called "Devices and Interfaces" on the left hand side. Under that menu, you should see some reference to your DIO 96 card. If you select that, on the top of the right hand pane you should see something called "Test Panels". When you click on Test Panels you should see something similar to the image below. (Your's may look different if you're running an older version)
Click the "All Output" button, and then click "Start". Then move the switch sliders to select On or Off. Make sure you aren't going to damage anything by turning on the wrong output if you don't know exactly which one your solenoid is connected to.
As you turn outputs on and off, you should see the little red LEDs on your Grayhill board lighting up. Once you know which Port and which Line your solenoid is on, you can then write LabVIEW code to turn it on and off.
Good luck.
Message Edited by pallen on 03-05-2009 09:34 AM
Patrick Allen
Attachments:
testpanel.jpg ‏36 KB

Running an EXE from LABVIEW without the 'cmd' window showing

Hi,
I am currently using the 'system exec.vi' in a LabVIEW application to open files in external executables (mainly Windows Explorer, Acrobat Reader and Word). This actually works fine and while my application is fairly sleek (even if I do say so myself) I am annoyed by the cmd window that momentarily appears each time I use the 'system exec.vi'.
Is there any way to disable this window? Or maybe there is another way of opening the files altogether?
I am using LabVIEW 8.0 on Windows XP Pro.
Any help would be appreciated.
Bazza

Bazza wrote:
Thankyou for your comments...
I do buy LV as part of a developer suite so could use the toolkit you mentioned. While PDF's and Word docs are the main files I open they are not the only. I guess I could open different file types different ways. I just hoped there was a better all round way to do it.
As far as Windows Explorer goes... My application is a file manager targetted directly at the file structures we use for developing functional test applications. The application handles all the file management requirements (i.e. WIP Backups, deploying, zipping/archiving etc) and its an added feature that you can 'explore' a given folder directly from the application. The general idea is that all our developers create systems using the same structure and approach.
Cheers,
Bazza
Have you looked at the VI in vi.lib\Platform\browser.llb\Open a Document on Disk.vi. It opens the document passed in according to its file ending and attempts to communicate with the target application through DDE if possible before using the command line. Even then I have not seen a cmd window popup so far.
Rolf Kalbermatter
Rolf Kalbermatter
CIT Engineering Netherlands
a division of Test & Measurement Solutions

How to launch an exe from LabVIEW VI

Hi,
I have made a few programs using LabVIEW and generated executables for each of these programs. I wish to generated a single launch program for these executables -- launch this wrapper program, select the (program) executable which you want to run and then finally run the executable.
If this possible to do that using LabVIEW? How should this be done?
Best Regards,
Harpreet

I would much rather call a subvi than call an exe. But there might be a reason for using exe's instead of subvi's. Anyway, create a loop with an event structure with an event case for each button. In each event case, run the proper exe with SystemExec.
- tbob
Inventor of the WORM Global

How to call a Linux exe from LabVIEW for Windows

Hello,
I need to call a non-LabVIEW Linux executable using LabVIEW for Windows. Any suggestions, aside from buying LabVIEW for Linux?
Thank you,
Chris White

Okay, I'll throw out a few ideas and I'll let you pick which one you may think is easiest.
1. Use the internet toolkit ($$$) or build a simple telnet client yourself in LabVIEW (use the TCP VIs in labview). This would allow you to connect to the telnet port of your linux box, login, password, and execute a command. (You'll probably want to use nohup, do a man on nohup to find out more).
2. Install SSH daemon on your linux box, and an ssh client on your windows machine. You can't get SSH for windows from cygwin. This would be more secure, and you wouldn't need to use the TCP VIs, you could simply use the "system exec" vi to call SSH.
3. On your linux box, install your app in inetd. Then, whenever someone connected to a certai
n port # on the linux box, it would execute your command. A little dangerous because someone might try to connect 50 million times (or a port scan) and kill your box. You also wouldn't be able to send a dynamic command line argument.
4. Write a small TCP application on your linux box to wait for connections (listen for command line options) and execute your command.
You'll probably find one of these options ideal depending on your administration and programming background.

How can I get handle(s) to and poll non-LabVIEW window(s)/application(s) from LabVIEW?

Want to launch EXE from LabVIEW, wait for user to finish with EXE's UI, and once they closed it, return execution flow in LabVIEW. Cool, no problem.
Used the System Exec VI and with the "wait until completion" = TRUE the EXE never launches. Not sure why.
With the "wait until completion" = FALSE, the application runs with no problems, but now LabVIEW no longer waits. Can't tell when user is done.
Work around idea... Once the Sys Exec VI launches the EXE, wait and poll some Windows API call to see when the window for the specific EXE closes. Cool.
I know G and no C. What I would ideally like is a DLL, that I can wrap with the DLL Import Wizard. Of course best would be a VI and the wrapped API call.
Any ideas?
Scott Rogers
Sr. DSM
Western NY

You could try it with a pipe. With a pipe you can open an exe, and interact
with it through a read and write reference. Although in your case the exe
might not start, since the normal sysexec doesn't start it...
http://forums.ni.com/ni/board/message?board.id=170&message.id=270461&requireLogin=False
Regards,
Wiebe.

Calling NIST from Labview

Does anyone have any experience using NIST software with Labview. I am wanting to call NIST to get properties of two different gases, and not exactly sure how to accomplish this.
Can anyone point me in the right direction?

aputman wrote:
I use a TCP connection to get NIST time. Not sure if something like this is available for what you are looking for. Hope it helps.
NISTime-32.exe is shareware and available here
Their is a command line hook so you can just call it with the system exe from LabVIEW
Jeff

How to send a command from a vc++.exe to LABVIEW.exe in order to control the button on the LABVIEW.exe

Hello, everyone. Using VC++, I have gotten the handle of a *.exe(built by Labview), but I cannot get the button handle. I want to get the button handle and post the message to control the button. How can I do that? When I use the SPY++, the *.exe(built by Labview) have not any child windows which is very different from the *.exe(built by VC++). In SPY++, what is the LVDChild class? How can I send the message to control the button on *.exe(built by Labview)???
That is to send a command from a vc++.exe to LABVIEW.exe in order to control the button on the LABVIEW.exe. How can I get it ?
Thank you!

hummingbird wrote:
Thank you! But I dont kown how to use vi server to raise a value signalling event. Can we put vi server into the vc program? Can you give me some more information or some examples, hehe!
hummingbird
Checkout the LabVIEW ActiveX server interface in the User Manual in Chapter 20, Windows Connectivity and the VI Server Reference in Chapter 17, Programmatically Controlling VIs.
There is a sample for Visual Basic under examples/comm/VBtoLV.frm, which should be quite simple to translate to Visual C as long as you can figure out the basics of ActiveX programming in VC (I have never done anything with ActiveX in VC). For those basics I would recommend some text book or MSDN.
Rolf Kalbermatter
Rolf Kalbermatter
CIT Engineering Netherlands
a division of Test & Measurement Solutions

Controlling Tera Term from labview

Hi guys
In my new project I would like to send commands to Tera Term Pro. Tera Term then responds to the commands from Labview the same way as I would type the commands directly into Tera Term.
I'm able to use cmd.exe with the SystemExecute Vi, but for my program I would like to do the same with Tera Term.
I would like to send commands with a stringcontrol and get the respond in a string indicator, all in labview. Tera Term should run invisible in the background.
So for this I thought using ActiveX would be the best. I have downloaded tera term pro.
In Labview I create this from the ActiveX Palette and select browse on the ActiveX Class.
In the Tera Term folder I find many .dll's:
I have tried to open them all, but I only get this message:
Does this mean it's impossible to use Tera Term with Labview like I described?
I'm not so familiar with ActiveX, only with Excel (which is in the ActiveX Class list), so I might have missed something.
My goal was to create a sub-vi which does the communication with Tera Term, the same way SystemExecute VI is built.
Regards,
Even
Regards,
Even
Certified LabVIEW Associate Developer
Automated Test Developer
Topro AS
Norway
Solved!
Go to Solution.

Sorry for this late reply. I have been using Teraterm Macro (not Teraterm Pro serial terminal) to interface with my previous provisioning app written in LabVIEW.
Teraterm Macro is such a lifesaver in that it can easily interface with your development boards that need: (1) RS-232C, (2) FTP, (3) TFTP or (4) SSH connections. The plain-vanilla 'serial' VI's are just that - serial port only and those need additional code to work reliably. If you need a good serial port VI try Prabhakant Patil's Hyper Terminal for LV 2009 and newer. You will find an ZIP or VIPM package from LAVA (lava.org). I have used his versions countless of times and is 10x more reliable than provided in LV examples.
You will indeed use the System-Exec.VI to call Teraterm Macro since *sigh* no one has written a wrapper for the DLLs (as you mentioned they are built for .Net framework. I have talked with the current developers and they are willing to give anyone the pass to extend Teraterm for LabVIEW so C++ devs out there with good LabVIEW knowledge should re-build the DLLs as static libraries that can be called from within LabVIEW. For now, this is the only way and it is a kludge - but it works - just not in a way you expect.
Here you can see that I am building the command line arguments before I call the system-exec node. Refer to the excellent how-to instructions at:
http://ttssh2.sourceforge.jp/manual/en/macro/commandline.html
Teraterm Macro will be spawned (opened) like it would when called from the command line. Its std input & output are not tied to your VI. You can merely pass arguments to the system-exec node. This is the reasons why we need someone to recompile the Teraterm Macro DLL as a static library (anyone?) so we can build a wrapper VI around the functions. Then its std inputs and outputs can be tied to LabVIEW's controls and indicators - hence, it becomes LV native.
-Relativity

I am using Activex controls from Labview to log the data into Excel spreadsheet. My applica

tion is running fine without giving any error messages. But even after the vi stops, excel process does not shutdown. "Excel.exe" process keeps running until I end it from Windows NT Task Manager. Is there any way to end the excel.exe process from Labview?

tion is running fine without giving any error messages. But even after the vi stops, excel process does not shutdown. "Excel.exe" process keeps running until I end it from Windows NT Task Manager. Is there any way to end the excel.exe process from Labview?I use Excel Active X control frequently to save and then analysis test data. In order to properly destroy the "Excel.exe" process it is important to close all the automation refnums opened when using the Excel active x controls. After completing your desired Excel task wire all the refnums in reverse order they were created into the Automation Close function in Functions->Communication->Active X pallette. This includes all Application, Workbook, Worksheet, or Range refnum. Missing even one of these refnums will mean that Excel.exe will still persist in the task manager and cause problems when excel is opened from outside LabVIEW. I hope this helps.
Stephan

Control exe from labview

Similar Messages

Maybe you are looking for