Build stand alone (exe),help?

hi i want to make build stand alone (exe) but i cant do that, can you tell me where i can found some example
to make it (explain with images)?
tanx

smercurio_fc wrote:
Reading the manual might be worth trying as well. You keep asking VERY basic questions which can be answered by just looking in the Help, which NI spent a great deal of time making, or doing a simple search. Your question has been asked many times before, all with the same answer.
Come on Smercurio, that is too much work!  It would really be easier for him if you would just fly to wherever Marp lives, sit next to him, and handhold him through programming for the rest of his LabVIEW career.
Marp,
Take the tutorials. How to Learn LV
Pay for taking some LabVIEW courses that NI offers.
and RTFM!

Similar Messages

  • Stray Blob with Dual Monitors and a Stand Alone exe

    Hi,
    When I run any stand alone exe that I make on a dual monitor system (XP Media Center) I get a blob (see attachment) that is stuck in the middle of the primary monitor.  I tried a very simple app and a complicated one.  Clicking on this blob will make my app run in the foreground and if my app is in the foreground then the blob will show up in front of everything else except for my app.
    I'm using LabVIEW 8.01.
    Thanks,
    Albert
    Attachments:
    Blob1.GIF ‏8 KB

    Have you tried a CO2 fire extinguisher on it? (reference to the movie "The Blob")
    Message Edited by AnalogKid2DigitalMan on 09-19-2006 01:35 PM
    ~~~~~~~~~~~~~~~~~~~~~~~~~~
    "It’s the questions that drive us.”
    ~~~~~~~~~~~~~~~~~~~~~~~~~~
    Attachments:
    200px-The_Blob_poster.jpg ‏16 KB

  • How build stand alone application without labview

    I have main vi and contain the sub vi i need build stand alone application without labview
    how build stand alone application without labview?
    thank and regard

    I assume that the poster means to run this on a computer without the development environment installed.  That is what the app builder is for. Review Altenbach's post.  This being said, there will need to be a runtime engine installed on the target PC. You can 'bundle' that with your build application and install it together, although I usually prefer Not to do that, and make that a seperate step because it is rather large, and if the target already has it, then it is wasted space.  Speaking of run time engine, I have seen negative reactions to it by my customers, but after sitting down and explaining that, with few exceptions, every application requires a run time engine. It is just that some are bundled with windows, or installed through windows update.  Once explained, it usually quiets the opposition. [Paul steps off soap box now]
    Paul <--Always Learning!!!
    sense and simplicity.
    Browse my sample VIs?

  • I have trouble in building stand-alone application, "you must intall Labview run-time engine on any computer on which you want to run this application"

    I have installed the LabVIEW 7.0 run time engine and checked all in the advanced setup on the installer setup slide. but I still get such a message saying that the target computer needs to have LabVIEW 7.0 run-time engine. What I want is a real stand-alone application even without having labview ... I used to think that's due to my program contains MATLAB nodes. But this is not true, since even without Matlab, it's still wrong. Please help, thanks!!!

    As was stated elsewhere, you have the option of building the runtime engine into your application when you build it. However, you can also create a "runtime engine application" by simply opening the application builder and doing a build without adding any source code files. The result is a small program (named lvrt.exe) that can run any LabVIEW code--whether or not its built into an executable.
    Such an application can be helpful if you are wanting to install several LV-based applications on the same computer in that it reduces the amount of redundant code on disk. All you have to do is make sure that Windows on the target computer associates the llb and vi file extensions with the runtime engine program.
    It can also be helpful during testing to run test code that isn't built into an executable.
    Mike...
    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

  • Error building stand alone applicatio​n, with LV.7.01

    Hi to all....
    I always get this pop up error (see picture attached) when trying to build a Stand alone application. I got the full version of Labview 7.01 and the Application builder also. the runtime engine is also 7.01.
    Regards
    HFZ.
    HFZ
    Solved!
    Go to Solution.
    Attachments:
    Error Building App.JPG ‏51 KB

    Hi GardW
    All comm. problem are handeled.
    The problem was based on the destinations for the .VI's.
    Labview 7.1 isn't so got to manage these. It's something the user got to be carefully about.
    Allmost solved. But now can't get the default 'labview Icon' to my finnished Application.  You know... when you make a stand alone application..
    then somewhere under the building process... you can choose if you want your own Icon added as the application starter icon! If you don't  choose any.. Labview makes the Labview Icon as your application starter Icon.
    And that is my problem now. Any ideas???
    Thanks for trying to help , i appriceate it !!
    Regards HFZ
    HFZ

  • Stand-Alone exe not seeing my VISA instruments

    Hello, I am attempting to build a standalone installer application from my VI using LV 7.1 on a Win 2k machine. I have gone through the build application wizard making sure to enable hardware configuration checkbox and select the desired VISA TCP/IP instruments from the list. I am able to build the application without errors and install the stand-alone app on a new PC without LV installed. When I try and run the app, I do not see my TCP resources.
    I have tried to install the NI-VISA runtime ver 4 with no success.
    Now, when I was installing the app on the new PC, I did recieve an error saying that MAX wasnt avalible. So is there a way to get MAX without installing Labview? Is there someplace on NI's website that allows you to download just the MAX. I would think that the whole purpose of building a standalone application is to NOT have to install labview and therefore MAX.
    So what am I missing here? Any help would be great.

    I have done some additional digging and here are my results. On my front panel I have a VISA Resource Combo box that selects which instrument I want to use over ethernet (they are both Agilent RF sources). In the visaconf.ini file on my development PC, I see that the aliases for my instruments TCPIP0::xxx.xxx.xxx.xxx::instr0::INSTR are present. There is also a TCPIP-RSRCS section in the config file with more info relating to the TCPIP0 instrument.
    On my target PC with only my stand-alone application installed (and no LV), my visaconf.ini file doesnt say a thing about TCPIP0. There is no TCPIP-RSRCS section in the file either. This probably explains why I am not seeing my Agilent instruments in the standalone application.
    I do have the MAX configuration file (.nce) but I see no obviously way to load this file into my stand-alone application. I think I bundled it with the installer, but I am really stuck.
    Any thoughts???
    Attachments:
    Labview MAX error.jpg ‏21 KB

  • Stand alone exe errors using report generation vi's

    I have a stand alone application that uses some report generation vi's. I have added the _wordsub.llb as a support file. In the main program I have told the report generations vi's where to find the _wordsub.llb so it can load the dynamic vi's as needed. The problem is when I run the stand-alone executable I get an open refernce error for one of the dynamic vi's that says that vi is not executable. But when I reconfigure the executable and include that vi as a dymaically loaded vi in addition to the _wordsub.llb, the stand alone works error free. Any suggestions?

    It really depends on what version of office you are using. Some methods have different set of parameters or even different names, labview does not adjust them accordingly, even though the code might execute but it will fail during build process. You must reselect the methods manually in order to build the executable. Most time you need to build different executables for each office version.
    -Joe

  • Does a stand-alone EXE built with Labview 8.2 return a return code?

    My application is an executable that was built from a VI in Labview 8.2. I'm expecting a return code of this stand-alone executable after the execution, however couldn't find a way to control the return code of the application.
    Does a stand-alone executable built with Labview 8.2 return a return code? If yes, how is this code controllable?

    Hi Tdot!
    Thank you for contacting National Instruments.  It looks like your question is something that many others have run into.  This topic is discussed here, and looks to be answered along with a couple of suggestions.  I hope this helps!  Let me know if there is anything else I can clarify.  Have a great day!
    Jason W.
    National Instruments
    Applications Engineer

  • Build stand-alon​e applicatio​n with Global variable

    Question:
       how to build a VI access a global variable into a standalone EXE file?
    there are multiple VIs access to one Global variable, one of the VIs need to run in background to update the Global variable, whick i built into EXE file.
    the rest VI will be called in from Teststand to retrieve the Global variable.
    the global variable is updated if i run the background VI in labview, but after i build it into EXE file, it seems the global is not updated even the EXE running OK.

    Hi,
    Do you actually need to have an executable.
    If you can call your global variable updater VI as a VI form, then your other VI's will still beable to see the Global variable.
    You can launch you global variable updater VI in a new thread or execution so that it runs in the background and returns back to TestStand sequence so you can continue on with the rest of your tests.
    Remember to close your global updater VI before you complete your test sequence run.
    Regards
    Ray Farmer

  • Stand-Alone exe for Windows

    Hi -
    I would like to use Java to create executables that will run by themselves with their own icon in Windows 2000 prof. - preferably without any other software installed. I am learning Java but at this point I am confused by all the choices for compilers, interpreters, GUIs, IDEs, etc.
    Which of these elements and which versions will I need?
    Thanks,
    dppatt

    I don't think it's worth doing this. If all you want is a standalone installation that has an icon shortcut, you can do all of that with the JVM.
    1. Distribute the JRE in your application. Installs are for suckers. You don't need them. Create a subfolder in your application direcory and put the JRE you want to use in it.
    2. Write the java command to run your app using the jre from 1, don't just use java because you have no idea what the user has installed.
    3. Create a shortcut in windows. Right click, open properties. Select your icon. In the target, enter your java command but use javaw instead of Java.

  • 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.

  • Skin menu won't work in stand alone published project

    Morning
    I created skin with a menu, but when I published it
    as a stand alone (.exe) the menu doesn't link to anything... I've
    double ck'd my links and all are OK. The links I put in to other
    project via a 'button' work fine. It's just the skin menu that
    doesn't work. Help! Thank you
    Bev

    Hi Jef,
    thanks for your answer. There were noch errors while installation, and, as I have said, the bridge ist working within Photoshop as "Minibridge" Trying to start bridge itself still fails.
    I was also using the above mentioned loganalyzer, he returned a message, that everything is ok with the install.
    any further ideas? I am concerned, that maybe the download from the Adobe-Site could be corrupt and/or incomplete???
    Best regards,
    jens

  • How to include .xml file while building a stand alone applicatio​n .exe file from a Labview program

    HI,
    I have a labview program which loads default values of all the variables from a .xml file when executed.  I am trying to build a standalone '.exe application'  using
    (Tools Menu --> Build Application from VI) , however I am not sure where to include this .xml file in the process?  I really appreciate if some one could let me know.
    Thanks
    Vish

    As GerdW said, it is preferable (and better practice) to use the project explorer. My guess, you didn't configure the build correctly (and probably used the default settings).
    First, you have to specify your xml file as Always included is the source file tab
    Now look at how the build folders are built:
    The .ini file (xml in your case) is in the data folder. So in the build the relative position of the xml file is not the same as in the development environment. You have to be aware of this difference and use a diiferent relative path for the exe. You can do this using a conditional disable symbol in the project and then use the conditional disable structure in your VI.
    Here in the deploy case the exe will look for the file in the data folder and in the development environment it will look in a folder name Files.
    Ben64

  • Stand-alone application generates error with function 'Ramp Pattern' (bug in application builder?)

    Hello,
    in my program a main.vi links to a sub-VI via 'open VI reference' and 'invoke node'. In this sub-VI the function 'Ramp Pattern' is used. The program itself runs normally, but if I build a stand-alone application using application builder I get an error message 'error 1003 occurred ..'. I believe this error is directly related to the build specifications which are as follows: the main.vi is referenced in a main build specification, the sub-VI in its own specification where the target is a LLB.
    I appended an example-program that exhibits the error (when executing 'Application.exe' and pressing 'calculate ramp'). The error does not occur when disabling the 'ramp pattern' function and rebuilding the application.
    I would rate this to be a bug in the application builder and would appreciate any help on how to solve this problem. However, due to the structure of the whole program the sub-VI has to remain in its own LLB.
    Attachments:
    RampPattern.zip ‏198 KB

    There can be reasons why a VI might appear broken when loaded from an executable. For example, if you have different versions of the same VI or enum that differ in such a way as to break the calling VI, that can cause a broken arrow when loaded from the executable. If you have DLLs being called and the runtime engine can't find the DLL, that can cause a broken arrow that you might not see otherwise. Finally, there is a bug related to a VI appearing broken when its not.
    Mike...
    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

  • How to build Vis in NI_AALbase​.lvlib to my Stand-alon​e applicatio​n?

    Hi, everybody.
    I met some problems while building the subVis of NI_AALbase.lvlib and NI_AALPro.lvlib into my stand-alone application.
    I use Labview 8.2 professional version and Windows xp OS.
    While I build the system contained example "Peak detection and display.vi" into stand-alone application, it succeeded in the local computer,and the exe program run correctly.
    Then I move the generated application files to another computer, where only the run-time engine 8.2  was installed.  However, some errors
    appeared during the running. The error message is "unable to load the front panel, error in loading 'NI_AALPro.lvlibeak detector.vi'  "
    It seems the "Peak detector" subvi in NI_AALPro.lvlib can not be found. Similar problems happened with the subvis in NI_AALbase.lvlib.
    I use the default configuration for Application Builder.  I donot know how to configure the Application Builder.
    Could you help me  to solve the problems?
    Thank you.
    Stephen

    An example of a non-vi support file might be an image that you are importing into your application. LabVIEW can obtain data from external files and perform LabVIEW functions on it.
    Thus, if you created an application that imported a file that is not a vi, you would include this in your support files.
    You can find out more about File I/O in the LabVIEW Help>>Fundamentals section.
    I hope this helps clarify things. Let me know if you have any more questions regarding this issue.
    Cheers,
    Emilie K. | Applications Engineer | National Instruments

Maybe you are looking for