Labview to .exe

I have a Labview file that transmits and receives using CAN and also sends and receives using the RS-232 port. I need to convert the .vi file to an .exe file so it can be run on a computer that does not have Labview. I heard it can be done, but how?

Hi Ivanka,
I'll be as fast as possible...
You are most likely experiencing the issue solved in the following KnowledgeBase:
Why Does My Executable Hang When It Is Opened When I Use A MATLAB Script Node?
Please follow the steps in the KB and let me know if it solves your issue, thanks.
- Philip Courtois, Thinkbot Solutions

Similar Messages

  • Can a Labview application EXE run on a PC with 128MB RAM

    Hi,
      What is the minimum requirement of the LabVIEW application exe  to run on  a PC. Is it necessary to have 256 MB RAM PC.
    Regards,
    Sowmya

    See Release notes. They can be found in the support section of the website or on the install CD/DVD.
    Message Edited by andre.buurman@carya on 10-30-2007 10:42 AM
    Regards,
    André
    Using whatever version of LV the customer requires. (LV5.1-LV2012) (www.carya.nl)

  • Labview 2009 .exe not working with windows 2000

    I created a simple vi with Labview 2009 to reset a counter in registry key. I changed it to an exe. The program runs fine on any machine with XP but it does not work on the machine I need it on which is running Windows 2000 SP4. I installed the 2009 runtime but I continue to get an error when it starts up saying the vi is not executable and that I need the full development to fix the errors. But like I said it works every where else. I've tried other exe wrote in LV2009 on this machine and they work. Is there something in my vi that is not compatible with Windows 2000?
    Thanks
    Solved!
    Go to Solution.
    Attachments:
    Serial Number Reset Cell 2.vi ‏15 KB

    There was an issue with building DLLs on Windows 2000 - http://digital.ni.com/public.nsf/allkb/431C9BD8F3482033862576A90073441F. Since you say you are trying an EXE, this may not be applicable.
    George M
    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

  • What options can be in a labview created .exe's .ini file?

    Every executable created by labview has a .ini file associated with it. What options can I enter into this file?. I was told that entering a section with the name of the executable and HideMainWindow=True would stop 2 entries being made in the system tray. I either didn't understand or it doesn't work. I am wondering where can I find a documented list of entries that can be made in the .ini file?
    Thanks in advance. Any help would be appreciated.
    Bob

    For the keys to work they need to be in a section that has the same name as the executable. For instance, the program MyApp.exe might have a MyApp.ini file containing something like:
    [MyApp]
    hideRootWindow=true
    Mike...
    PS: it also helps of you have the name of the key right...
    Certified Professional Instructor
    Certified LabVIEW Architect
    LabVIEW Champion
    "... after all, He's not a tame lion..."
    Be thinking ahead and mark your dance card for NI Week 2015 now: TS 6139 - Object Oriented First Steps

  • Can Labview Executables(.exe) be recompiled to source code(.vi)?

    We have lost some valuable virtual instruments(.vi's) in a hard drive
    crash. We do have copies of the executables(.exe's). Is there  any
    procedure or software available to return them to their original state
    (.vi's)? Please Help.

    Actually the answer is maybe.
    If you only need to call the VIs and not edit them, the following from
    some old info-LabVIEW posts may help you out.  I have never done
    this and I don't know if it works with newer versions of LabVIEW, but
    it may help you out of a bind.  find the whole thread by looking
    in SearchVIEW for "How do I distribute copy-protected Labview applications?"
    I hope that this helps,
    Bob Young
    <quote>
    There are some requirements...
    To load and run an executable in LabVIEW development, it must have been
    built by the same version and platform. Since the VIs have no diagrams, they
    can't be recompiled.
    Only 6.0 (don't know for 6.1... tell us someone) can open EXE's as LLB's.
    However, you can take a 5.1 executable, rename as an LLB, use the 6.0 VI
    Library Manager to copy VIs from this LLB to a new dir or LLB. Then LabVIEW
    5.1 will be able to open and run.
    <snip>
    Jean-Pierre
    <end quote>
    Bob Young - Test Engineer - Lapsed Certified LabVIEW Developer
    DISTek Integration, Inc. - NI Alliance Member
    mailto:[email protected]

  • How to run labview in exe

    We have a scoreboard and we don't know how to run it in an exe.file.
    We need it to project on a big tv screen.
    please answer
    thx

    You need the Application Builder installed (before 8.0 - Tools>>Build Application..., in 8.x building should be part of the project).
    If you don't have it, you can purchase it seperately from NI.
    To learn more about LabVIEW, I suggest you try searching this site and google for LabVIEW tutorials. Here, here, here, here and here are a few you can start with and here are some tutorial videos. You can also contact your local NI office and join one of their courses.
    In addition, I suggest you read the LabVIEW style guide and the LabVIEW user manual (Help>>Search the LabVIEW Bookshelf).
    Try to take over the world!

  • Interfacing Labview with .EXE file

    I need to create a GUI in labview that can interface and run dos commands (codes) from .EXE file.how can I achieve this.
    Please advice.

    ...and in general it will not help posting the same question in various forums..., as here

  • Stand alone labview application (.exe file) does not run properly

    Hi all,
    I am trying to make a stand alone labview application to run on another computer ( I have never done this before).
    I went through the tools->build application prompts and was able to build an exe file.
    the program is supposed to control a power meter and make power measurements then save them to a text file.
    When I run the exe file, on the same computer I compiled the exe file on, the program generates a text file to save data to but it can not communicate with the power meter.
    There are some sub-VIs and a dll file that are used to communicate with the power meter. Could it be that I am not telling labview to correctly
    include these files when I create an executable?
    What are some common problems that occur when generating stand alone applications that could be causing my issues?
    And does anyone know of any good tutorials on generating stand alone applications in labview other than the NI help files?
    Thanks for your help,
    Solved!
    Go to Solution.

    edCubed wrote:
    Hi Bill, thanks for your suggestions.
    I haven't tried to run this app on another computer yet. I'm just trying to run it on the computer it was developed on.
    The computer I developed it on has all the drivers/resources I need to control the power meter.
    Also, I don't know how to include the VISA runtime with my installer. could you explain how this is done?
    This is the first time IV tried to turn any labview programs into stand alone exe files so I don't anything about how to do it other than what I've seen in youtube videos and help files.
    If you know of any good tutorials that will help me figure this out I would appreciate it.
    Thanks,
    My fault - I didn't read that this was the same computer.  I know the very end of Core 3 studies shows how to build an executable and installer, but even that is very general.  I'm not sure if there exists a tutorial on how to do it.
    As for including the runtimes, when you build an installer, you have to include the runtimes that your executable will need.  It's fairly straightforward.
    Since it won't run on the machine that built it, I'll have to think about it a little bit...
    Bill
    (Mid-Level minion.)
    My support system ensures that I don't look totally incompetent.
    Proud to say that I've progressed beyond knowing just enough to be dangerous. I now know enough to know that I have no clue about anything at all.

  • Debe tener instalado para ejecutar Labview. Exe?

    Hola a todos .. Estoy empezando a trabajar con Labview así que tengo varias preguntas, cuanto más lo hago uno a la vez.
    Después de crear un archivo ejecutable. Labview Exe es necesario tener instalado para ejecutar la aplicación?
    Cuando creo una solicitud de un cliente .. qué software instalar en su máquina sólo para ejecutar la aplicación?
    Agradecido
    Rafael Nunes

    Translation 
    Hello everyone .. I'm starting to work with Labview so I have several questions, the more I do it one at a time.
    After creating an executable file. Exe Labview must be installed to run the application?
    When I create an application for a client .. which software to install on your machine just to run the application?

  • Bring LabVIEW built exe to front on subsequent launch attempts

    I'm using LV 2012 on Windows 7.  I have a LV built executable whose window is commonly minimized by users.  Since there can only be one instance of the exe, if a user attempts to click the shortcut while the exe is already running, nothing happens.  I'd prefer that my app window instead open and move to the front.   I'd swear that LV executables used to do this all on their own, though I don't know if that is due to a change in LV or to Windows.  I'm willing to do it programmatically, but no event seems to get triggerend when you "re-launch" the exe.  Anybody know a trick for doing this?  

    There may be an easier way, but...
    You could modify your INI file to allow multiple instances of the program. Then in the program you can set it so it does NOT show the front panel at startup and add a check at startup using "Find Window" from the windows API to determine if the window already exists. If it does (i.e. you get a valid handle) you can use that handle to move the already running window to the front (also using the windows API as was suggested above) and quit the program, because another instance is already running. If it does not exist, then use a property node to show the front panel.
    The only possible issue here is, you will always get a valid handle to the window since yoru program will be running because you just opened it, whether it is the first or second instance. I am not a windows API wiz by any means, but you may be able to determine if you get multiple handles vs. if you just get one valid handle for a window name, and use that logic to your advantage. This is just a stab in the dark.
    CLA, LabVIEW Versions 2010-2013

  • Using Sync Manager for LabVIEW OI exe & TestStand

    We would like to have our LabVIEW Operator Interface executable send data via a TestStand queue to a logging sequence.  The SyncManager API sounds like a slick way to do this because it provides access to TS syncronization objects from other processes outside of TestStand.  I created an experimental sequence to try out the concept.  The sequence creates a queue with a TestStand Queue step, enqueues an item with another TS queue step, then uses ActiveX calls into the SyncManager API to add another item to the queue.  That all works.  
    When I added a LabVIEW VI to enqueue another item via similar ActiveX calls into the SyncManager API, the VI does not get a valid reference to the queue and so it can't enqueue the item.  
    I read on the forum that the TS queue name needs to start with * in order to be accessed by separate processes on the same machine.  When I prepend a * on my queue name, the TS queue steps continue to work, but the step that uses an ActiveX call into the SyncManager API to get a reference to the queue returns a null ref so the following ActiveX enqueue step returns an error.  Plus the LabVIEW VI still doesn't get a valid reference to the queue either.
    Ideas and suggestions welcome!  The sequence and LabVIEW VI are attached. Using LV and TS 2012, got similar results in 2013SP1 .
    Thanks!
    Hans
    Solved!
    Go to Solution.
    Attachments:
    Sync Manager Experiment.zip ‏193 KB

    Thank you very much dug9000.  I unchecked the Create Object box in the sequence step adapter settings and disabled the Automation Open node in the VI.  Now the sequence ActiveX steps can get a valid queue ref for a queue named "*TestQueue" and can enqueue an item.  Yay!  The VI gets now gets a valid reference to the queue and can get the numbers of items on the queue.  Yay!  But, I have not been able to get the VI to successfully enqueue an item.  I tried both passing the sequence context and a null sequence context to the IQueue Enqueue method, but no luck either way.  The updated zip file is attached.  More help would be greatly appreciated!
    Hans
    Attachments:
    Sync Manager Experiment II.zip ‏49 KB

  • Can I Run a labview application in a hidden window (i.e. I don't want the front panel to pop up in this Labview created EXE)?

    I have a executable labview 6.1 program with a front panel. The front panel pops up every time I run it. Can I force the program to run without popping up its front panel.
    Thanks in Advance

    If you're using MS Window, you can use lvwutil32.zip to hide the front panel. lvwutil32.zip can be downloaded from NI site.
    Or you can move your front offscreen, so that user can't see it. And save your vi. When you run your vi again, it'll popup at the offscreen position. NI uses this trick to hide windows from LabVIEW users. You can also set front panel size to 0.
    George Zou
    http://gtoolbox.yeah.net

  • Call Labview generated EXE with Parameters

    Hi
    I have generated an exe  in a Lab project(bcos of the no of VIs = 300) 
    I want  to call this EXE in   Teststand  with  Parameters
    how to achive this
    mytry1)   as  executable  but  the cluster outs cant be exported to teststand 
    mytry2)  as a dll   called in Teststand  ->  I cant see  the outs (it just provides one return value)
    Attachments:
    sapouterror.PNG ‏190 KB

    Dear aparab,
    does the following article help with the DLL call?
    http://digital.ni.com/public.nsf/allkb/22BF02003B4​588808625717F003ECD67
    Kind regards

  • The root cause for the case that "cannot close labview-generated exe file"

    Hi All, I have a big program including a lot of things. When I converted it to an exe file, it cannot be closed properly. I used to load the dynamic vi in this program and cannot close it by clicking "X" of the window. Now I have removed that dynamic load but still cannot close the exe. Could anyone give me some advice? Thank you!

    Hi Freelance_LV, thank you for your advise, here is a program for a USB dongle. Here are the answers:
    for now, questions:
    1. how are you closing the EXE? Panel close (X) on the top right corner/stop or exit button on the GUI?
    [A] I use (X) on the top right corner but it did not work. But when I use exit button on the GUI it worked.
    2. Or are you using a FP Close invoke node?
    [A] No
    3.how are you handling the event for Panel close or for Stop/exit button?
    [A] events are inside a sequence frame
    how many loops are running in parallel inside the EXE?
    [A] It is hard to tell. I am not the original creator of this code, but the main structure is this: a big "for" loop, inside there are some sequence frame, and some events in one of the frame.
    how are you stopping those loops when the panel is closed or a Stop/Exit button is pressed.
    [A] the main loop inlcudes some events, sequence frame, and something like this. And there is a subvi from some previous people's work to close USB. 
    have you checked if all the loops are closing when you stop the EXE?
    [A] Sorry I don't know how to check all the loops are closed.
    does this work well when you run the source code?
    [A] yes source code can be always be closed well.
    have you checked for any errors when yuo stop your EXE?
    [A] sorry I don't know how to check for errors?
    when you say it cannot be closed properly, there could be two things:
    1. the front panel/GUI does not close and it stays there. you cannot perform any GUI actions, or it seems to have hung.
    [A] Yes GUI still there. But cannot perform any GUI actions.
    2. the GUI closes but you can still it in the task bar below, you will have to use the Task manager to force close the executable.
    [A] Not this case.
    Thank you very much!

Maybe you are looking for