How build applicatio​n without labview

i build application in my PC. My Pc include professional LV but if  try my programe work  another PC without LV the programe not work
so i need my programe worke in pc without LV
can help me how my programe worke without LV
Note: my programe main Vi and contain sub VI

Create application to run in another PC with no labview installed:
1 - create application
2 - create installer that include the application
If you run the installer in the other PC, It install the application and the labview runtime (necessary to run your application).
If you want another solution, just download labviewruntime from NI and install in the PC with no labview.
Software developer
www.mcm-electronics.com
PS: Don't forget to rate a good anwser ; )
Currently using Labview 2011
PORTUGAL

Similar Messages

  • Build applicatio​n with LabView 8.2 Prof

    Hello,
    in the past (V 6.1) it was possible to build LabView application with a complete setup routine, not only *.exe. In Version 8.2 I dont find these option. Anybody knows where to find it?
    Best regards
    Robert

    I think that what you want it's to create an installer. See the steps on the attach picture.
    Software developer
    www.mcm-electronics.com
    PS: Don't forget to rate a good anwser ; )
    Currently using Labview 2011
    PORTUGAL
    Attachments:
    teste.png ‏333 KB

  • Standalone application without labview ?

    Hi
    I am trying to build an .exe file using application builder in LabVIEW 7.0. Is it possible to build an application without labview dependency ? In short, I want something like an .exe file which will run on systems without labview. I know visual basic has this facility. Please let me know.
    Thanks
    Sridhar.
    Kudos always welcome for helpful posts

    "Maximus00" <[email protected]> wrote in message news:[email protected]..
    > . . . I wanted an option where he can view my application without having
    to install anything on his PC. Looks like that is not possible ? Am i right
    ?<br><br>Sridhar.
    You are not right. It is possible. With LV 7.0 and previous versions (I
    don't know if this still works for 7.1), the executable will run correctly
    if lvrt.dll and the other support files are in the same directory. So you
    could, for example, put your executable on a thumb drive. Copy all files
    and folders in the C:\Program Files\National Instruments\shared\LabVIEW
    Run-Time\7.0 directory to the thumb drive as well. Then your supervisor
    could just run the program from the thumb drive without copying anything to
    his computer. Or, if you want the drive back, he could copy the entire
    contents to his drive without using an installer.
    But this begs the question, if your supervisor is evaluating executables you
    are creating in LabVIEW, what's the problem with installing LV Run-Time on
    his computer?

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

  • How to build demo versions with Labview ?

    Hello,
    is it possible to design Labview applications in a kind,
    that it is possible to generate "demo versions" of it ? Demo version in the means of feature-limited crippled versions of a full instrumentation software, where SOME hardware access is denied, but you can load and view and analyse data.
    Of course it might be useful to compile this demo version with the Labview Application Builder,
    What might be the business modell for demo versions:
    A hardware manufacturer creates a Labview application which controls the manufacturer's components, and allows instrumentation and data recording. The application is not free but sold for extra money.
    As pre-sales benifit, the manufacturer would like to send the (compiled) Labview application to future customers.
    Now the problem is, that the customer has not (all) the external devices or PCI/USB devices,
    on the other hand the hardware manufacturer does not want to give the "full application" as gilft to the customers.
    Now with traditional software development with C++, Java, C#,
    either a demo version is gained from the full version by replacing some module with hardware access by modules wth "empty" function body or with function body which return constant values instead of accessing the hardware.
    In the world of process industry, usual process control systems may supply "alternative" values if the original device is not available.
    What kind of software structure must I build with Labview, to do the same ?
    Now the problem with Labview applications is
    Labview applications depend on drivers. Drivers depend on hardware.
    So if the FULL commercial version of the Labview program accesses a DAQmx driver, GPIB driver or any other hardware driver by a VI,
    and often this means that a special manufacturer VI is used in the Labview program which does the actual hardware access,
    how to modify the software to make a demo version
    a) so that IF the customer buys the hardware and gets the hardware driver, he still does not have the full version
    b) so if the customer neither has the hardware nor the driver, he still can run the Labview software and load an view data, push buttons, can execute menu items even can manipulate data ect, can use the manufacturer's VI
    Unfortunately, it is no solution just to delete "some" of the VIs with hardware access from the distribution of the demo version, as this just causes error messages during the loading of the (compiled) Labview demo application.
    Message Edited by hemmerling on 01-11-2007 12:35 AM
    Message Edited by hemmerling on 01-11-2007 12:37 AM

    Thanks alot.
    Conditional Disable and Diagram Disable Structures
    http://zone.ni.com/reference/en-XX/help/371361B-01/lvconcepts/cond_diagram_disable/
    are indeed at least a part of what I wanted.
    Anyhow, as such "suspended" VIs are often the *source* of signals,
    so there must be an addtional method how to provide "alternative" signals for the demo version,
    which does not make the administration / further development the full version  too complicated...
    For example: The VI for an external signal generator device is disabled, but alternatively it would be nice if the users of the demo version can get a fixed sinus signal instead...
    How to do that with Labview and the "Conditional Disable and Diagram Disable Struktures",
    and can I test this all even without Labview Application Builder, in the full development system ( so that I don´t need the compiler for frequent checking ) ?
    Btw, with what version was this "Conditional Disable and Diagramm Disable" feature introduced ? Is ist already available with Labview 7.0, /.1 ?
    Sincerely
    Rolf

  • Build application and installer to work without LabView installed.

    Hi!
    Can someone please tell me how to build an installer
    in LabView, that can be installed on a different computer
    and run my program without having to install LabView
    on that computer?
    Regards,
    Børild

    You just go through the nomral process of creating the installer:
    http://zone.ni.com/reference/en-XX/help/371361B-01/lvhowto/build_installer/
    Just make sure you select the run-time engine (default I think) and VISA if needed...
    Use the rating system, otherwise its useless; and please don't forget to tip your waiters!
    using LV 2010 SP 1, Windows 7

  • How to remove the "int len" of my return string on the DLLS header when building a DLL on LabVIEW 8.5

    Hi all.
    I'm building a DLL on LabVIEW and I choose a string as an output on the terminals connectors.
    But LabVIEW creates another output, the lenght of the return string.
    This is a problem because I have other DLLs and I need them to be compatible.
    How do I remove this length from the header? What is the difference between Pascal String and C string and String Handle Pointer?
    String Handle Pointer removes the length from the header but I don't know the difference between this data types.
    Thanks in advance for the help.
    Daniel Coelho
    Portugal
    Daniel Coelho
    VISToolkit - http://www.vistoolkit.com - Your Real Virtual Instrument Solution
    Controlar - Electronica Industrial e Sistemas, Lda

    Daniel Coelho wrote:
    Hi all.
    I'm building a DLL on LabVIEW and I choose a string as an output on the terminals connectors.
    But LabVIEW creates another output, the lenght of the return string.
    This is a problem because I have other DLLs and I need them to be compatible.
    How do I remove this length from the header? What is the difference between Pascal String and C string and String Handle Pointer?
    String Handle Pointer removes the length from the header but I don't know the difference between this data types.
    Thanks in advance for the help.
    Daniel Coelho
    Portugal
    C string pointer is a pointer to a memory location whose string information is terminated by a 0 byte. Pascal String Pointer is a pointer to a memory location where the first byte specifies the number of bytes to follow. This obviously allows only for strings up to 255 character length.
    LabVIEW String Handle is a pointer to a pointer to a memory location where the first 4 bytes are an int32 value indicating the number of characters to follow. You can read such a String handle in a function without many problems, but you can only create, resize and delete such a handle by using LabVIEW memory manager functions. So this makes only sense if the caller of such a DLL is LabVIEW too as another caller would have to go through several hoops and tricks in order to gain access to the correct LabVIEW kernel that could provide the memory manager functions to deal with such handles.
    Last but not least output strings whose allocated length is not passed to the funciton as additional parameter are a huge secerity risk (talk about buffer overrun errors). LabVIEW DLL Builder does not support the creation of DLLs with output string (or array parameters)  without the explicit passing of an additional parameter telling the DLL function how large the allocated size is (so that the DLL function can make sure to never write over the end of the buffer).
    The additional length parameter only disappears for String Handles because LabVIEW will simply resize them to whatever length is necessary and that is also the reason why those handles need to be allocated by the same memory manager instance that is also going to execute the DLL function.
    Resizing of memory pointers is non-standardized and in normal circumstances not suited for passed function parameters at all.
    Rolf Kalbermatter
    Message Edited by rolfk on 06-13-2008 12:28 PM
    Rolf Kalbermatter
    CIT Engineering Netherlands
    a division of Test & Measurement Solutions

  • How does the Labview based program apply to computer which without Labview

    How does the Labview based program apply to computer which without Labview
    student number：1110340001

    SInce you list your "student number", you are probably using the student edition.
    You cannot build standalone executables with the student edition.
    You need LabVIEW professional. If you only have LabVIEW full, you need to purchase the application builder seperately.
    LabVIEW Champion . Do more with less code and in less time .

  • How can i make the .exe run on the computer without Labview?

    .exe can't run on computer without Labview.  Is there any way?  Thank you.

    You need to install the LabVIEW Runtime engine for your specific LabvIEW version.
    In the project window you can create an installer that includes the Runtime Engine (RTE).
    Ton
    Free Code Capture Tool! Version 2.1.3 with comments, web-upload, back-save and snippets!
    Nederlandse LabVIEW user groep www.lvug.nl
    My LabVIEW Ideas
    LabVIEW, programming like it should be!

  • How to use g++ to build shared libraries for labview in linux?

    does anyone knows if it's possible to compile a shared library in linux with g++ that could be recognized by labview?
    thks
    JP

    Hi JP,
    Yes you can use g++ to build shared libraries that labview can use. You'll want to give your C++ library a C interface. This is really common practice. You can do this by simply declaring functions as 'extern "C"'. Here is a link with more information:
    http://www.parashift.com/c++-faq-lite/mixing-c-and-cpp.html#faq-30.8
    I've personally worked on projects that do exactly what you want to do.

  • Error 1073 (on Clear Errors.vi) When Building Applicatio​n in LV 8.2

    I have seen numerous posts about this problem when building an application without a block diagram in LV 7.x, however, I am recieving this error on LV 8.2.  Whats most disturbing about it, is that it always hangs when processing Clear Errors.vi.  I have tried my source on two different machines, to no avail.  Also I tried to do a mass recompile of the entire vi.lib again no help.  It is very important that this program compiles, however I cannot get past this error.  Any suggestions?
    My specific error message is here:
    Visit the Request Support page at ni.com/ask to learn more about resolving this problem. Use the following information as a reference:
    Error 1073 occurred at ABAPI Dist disconnect td-poly.vi -> ABAPI Dist Chg and Save VIs.vi -> ABAPI Dist Build LLB Image.vi -> ABAPI Copy Files and Apply Settings.vi -> EBEP_Invoke_Build_Engine.vi -> EBUIP_Build_Invoke.vi -> EBUIP_Build_Invoke.vi.ProxyCaller
    Possible reason(s):
    LabVIEW:  This property is writable only when the VI is in edit mode, or this method is available only when the VI is in edit mode.
    -Paul

    Hello Paul,
    I am sorry for not elaborating previously.  This issue has been documented previously for further investigation to our R&D group (# 3ZK9LGP2).  In the report I found that this error, though vague in the description, is fixed by enabling MathScript Support. 
    To enable MathScript support, check the checkbox in the application properties for the 'Enable MathScript support' option.
    -Bob
    -Bob

  • Create installer without labview

    Hi,
    Is it possible to create an installer without LabVIEW? I am supporting Windows 2000 through 7 and the versions of NI software varies with each OS, specifically when dealing with oscilloscopes running Windows due to VISA conflicts.
    The two main problems I have with creating installers with LabVIEW (Application Builder):
    1) Windows 2000 requires the Product Framework before 2.8.0. This makes it impossible for installers to run on Windows 2000 that require product installation newer than 2.8.0 which is basically every installation for Windows 7.
    2) As far as I am aware, the required software has to be installed on a local machine first before creating an installer. Then you navigate to the Additional Installers section when creating an installer to add to the installation. The location path will point to the orignal CD drive or location it was installed from on the local drive. I don't see why this required. Why can the installer be created directly from the extracted files without it being installed on machine?
    Thanks
    Solved!
    Go to Solution.

    Wow guys, thanks for two blatent insults. If you don't have anything nice to say don't say it at all.
    A little further explaination:
    Supporting and maintaining Windows 2000 in 2014, I agree, is cumbersome. However, you have to realize these oscilloscopes that run Windows 2000 in 2014 still cost upwards of $8,000 to replace and the operating system cannot be upgraded. Why do they still cost so much? Because they are very useful tools. And new ones cost $20,000 to $30,000. I don't think that this effort is "los[ing] [the company's] ability to make a profit".
    For those of you that are interested in the orignal question posted here is my solution.
    I used SFX Builder (http://sourceforge.net/projects/s-zipsfxbuilder/) to bundle NI's software into a single executeable file. Heres the steps:
    1) Download all necessary NI software
    2) Download SFX Builder
    3) Download 7-zip (http://www.7-zip.org/)
    1) Extract all NI software into a single folder and use 7-zip to compress into a .7z archive
    2) Open SFX Builder and add the .7z archive to the File tab
    3) You can easily set the path of extraction to anywhere on the computer, the temp (%temp%) is the most useful
    4) On the Tasks tab click the add/plus button and select Run Program, then enter the path where the extraction happened, here is an example
    5) Easy peasy!

  • Making DLL with C++ builder to use in Labview

      Anybody knows how to make DLL in C++ builder to use in Labview?? 
      Regards,

    smercurio_fc wrote:
    MCFSE wrote:
    This is a good question that does not appear to be addressed in that other thread.
    But is addressed via several NI KnowledgeBase articles and NI Community examples. For example: https://decibel.ni.com/content/docs/DOC-14564
    Well not verbatim, as that document refers to Visual Studio, not C Builder. But creating DLLs in C Builder for use in LabVIEW is no different than creating DLLs in C Builder for any other programming environment that can call unmanaged DLLs. How to configure C Builder to create a DLL, is really beyond the tasks anyone from NI should be required to explain. This requires someone who is familiar with C Builder and requesting a supplier to have specific experience with tool X goes a bit far. NI and most others are using Visual Studio so that is what gets explained. If some C Builder crack would come up with a tutorial targeted at integration with LabVIEW and post that here or someplace else, that would be of course great, but alas, nobody so far has felt the desire to step up to the challenge. There is no inherent difficulty with C Builder created DLLs to be used by LabVIEW, but apparently some difficulty of people to understand how to use C Builder to create working DLLs at all. Similar problems can appear for beginners with Visual Studio and since this is the tool mostly used here around, there are several tutorial style documents available that try to handhold the beginner to get a DLL at all.
    Personally I'm not sure that is ideal either, since those people usually know very little about C programming, or more precise if they know about C programming, they will be able to learn to use the tool in question, with some simple, non LabVIEW oriented examples from elsewhere and then easily apply that knowledge to LabVIEW with the help of the Visual Studio examples posted in quite big numbers, even if they use a different tool than Visual Studio.
    Other even more challenging topics would be to use CygWin, MingW, Bloodshed Dev C++ and similar compilers and write tutorials about them. However the challenges with all of these is to get them even installed well on your development system and to figure out various configuration hassles, also when trying to distribute the result later on.
    Rolf Kalbermatter
    CIT Engineering Netherlands
    a division of Test & Measurement Solutions

  • Running a LabVIEW app on a MAC yosemite without LabVIEW

    Hello all !
    When you compile LabVIEW codes on a Mac, you create a ".app" instead of a ".exe". I would like to run my ".app" on another Mac running with Yosemite (OSX 10.10) and without LabVIEW on it.
    I downloaded the latest RunTime Engine for LabVIEW on that Mac in order to make the application run but it does not seem to work ...
    Has anyone already done such a thing and would have a method to follow ? :-)
    Thank you in advance !
    Solved!
    Go to Solution.

    gvanhoeke wrote:
    When you compile LabVIEW codes on a Mac....
    LabVIEW VIs are always compiled. You are probably talking about building a standalone executable.
    gvanhoeke wrote:
    I downloaded the latest RunTime Engine for LabVIEW on that Mac in order to make the application run but it does not seem to work 
    Instead of the "latest", you need the runtime engine that matches the LabVIEW version used to develop the program.
    (Sorry, I have no direct experience with Macs)
    LabVIEW Champion . Do more with less code and in less time .

  • How do i run a Labview file through a windows phone?

    Hello there
    How do i run a Labview file through a windows phone or a tablet? is it possible
    is there any phone specifications required? or steps?
    Thanks alot  

    Blokk wrote:
    na1992 wrote:
    hahaha my baad
    i mean if i have done my labview file on laptop and i want it to connect my file to a microcontroler using usb or any serial connection, i want a way that my labview file will run if i store it on a phone. 
     i searhced about exe  format but i didnt find enough info
    Sorry, but you should define more precisely what is your goal:
    " i searhced about exe  format but i didnt find enough info"
    If you build an exe using Labview, that exe will not run on iOS, or Android, if this is what you ask...
    Nor Windows Phone or Windows RT. A LabVIEW exe is compiled and linked for x86 or AMD64 architecture with Win32 API architecture and will only run on Windows for x86 or x64 systems.
    Windows Phone and Windows RT are despite the similarity in the name technically completely different platforms to the normal Desktop Windows system, just as different as MacOS X or iOS.
    Rolf Kalbermatter
    CIT Engineering Netherlands
    a division of Test & Measurement Solutions

Maybe you are looking for