IS APPLICATION BUILDER 6 COMBATIBILE WITH LABVIEW 7 ?

IS APPLICATION BUILDER 6 COMBATIBILE WITH LABVIEW 7 ?

No it's not but it is a free upgrade last time I checked. Go here and click on the Upgrade Advisor link. You will need the serial number of your current app builder.
p.s. LabVIEW 7.1 was released today so you might want to skip 7 and go straight to the latest.

Similar Messages

  • Application Builder error in LabVIEW 7.0

    I am maintaining some legacy code in LabVIEW 7.0.  I have recently (perhaps within the last month or so) been getting Error 1003 in Dist Copy Non-VI Files.vi (part of App Builder) when building my code.  I've done some testing, including trying to build much simpler VIs, and get the same error.  Curiously, this occurs on multiple (Windows XP SP3) machines, both "real" and "virtual", including on two of three installations on a single PC (so it is not hardware-dependent).
    I have a strong suspicion that the problem is neither my code nor LabVIEW itself, based on the following logic:  1) This problem arose on multiple PCs at about the same time (i.e. I don't recall seeing this a few months ago, now I see it on almost all of my PCs).  2) There are two PCs where I do not see this error -- when I check the LabVIEW installation files between a PC that "works" and one that doesn't, the differences seem (to me) to be small, more related to "what did I do most recently" or "how much of MAX did I install, which drivers".  (3) Using or not using OpenG in my code mades no difference, nor does turning off Anti-Virus scans.
    I tried two other things.  First, I have a VM that I recently build (which I think is significant) that has both LabVIEW 7.0 and LabVIEW 7.1.  The build fails with LabVIEW 7.0, but succeeds with LabVIEW 7.1.  In addition, I found a VM, built a year ago and "sitting idle", with LabVIEW 7.0 on it.  I fired it up, did not allow Microsoft Update to update anything, and tried the build with LabVIEW 7.0 -- it worked!
    My current working hypothesis is that some "patch" installed by Microsoft (.NET? ActiveX?) has clobbered something in the LabVIEW 7.0 Build Application.  Unfortunately, the VIs that make up this application are password-protected, so I can't see "inside" to discover what file or other condition is responsible for the error message.
    Does anyone have any ideas or suggestions?  [Don't suggest "Upgrade to 7.1" -- I'm the only "maintainer" of multiple PCs and multiple applications, some of which run on systems "belonging" to other people.  I am in the process of rewriting the code in "modern LabVIEW" (2011) and will port it widely, but until then, it's not practical (or "politically correct") to make the 7.0 -> 7.1 shift ...  Besides, my curiousity is piqued!]
    Bob Schor
    Solved!
    Go to Solution.

    Good point.  The reason for my "laser beams" is several fold.  First, I follow a written protocol (I wrote it!) whenever I install or re-install LabVIEW 7.0, so I'm pretty sure that all of the installations "should be consistent" (if not identical).  Second, I compared two NI folders in Program Files between a version that worked and one that didn't, and while there were differences, it seemed "not likely" to be an explanation.  Third, I'm 99% sure that at least one of the systems that now cannot build (of the eight installs, all by me, that I've checked, only three worked, and one was on a PC that hadn't been turned on in over a year, hence was certainly not updated) was able to build previously (i.e. I don't recall seeing this problem until about a week ago, when I started re-building an update to my legacy application).  It is possible that this problem was always present on these systems, but doesn't seem likely.
    Nevertheless, before the beginning of next week, I plan to take one of my "failing" systems, uninstall LabVIEW (but not change the OS in any way), reinstall it, and see if I can build.  If this still fails, I'll take the "old" system I mentioned above and start bringing it "up to speed" until I "break" the App Builder.  Note that it is possible that MicroSoft is not to blame -- I have other software (such as editors, utilities like WinZip, etc.) that have also been updated, and one of them might have clobbered the Builder.
    Will let you all know what I find.
    Bob Schor

  • Building classes with labview (version 8+).

    Just wondering if it is possible to build classes with labview and how this applies, starting a new project and want to design the software to be easily maintained.  I would like to be able to Inherit vi modules and possibly override portions of the inherited vi.  Also if anyone has any experience trying to impliment OOD features and can provide any feedback.  In addition are there any suggested standards to adhere to for labview development that might increase readability.  thanks Paul.

    svt4cobra6 wrote:
    Just wondering if it is possible to build classes with labview and how this applies, starting a new project and want to design the software to be easily maintained.  I would like to be able to Inherit vi modules and possibly override portions of the inherited vi.  Also if anyone has any experience trying to impliment OOD features and can provide any feedback.  In addition are there any suggested standards to adhere to for labview development that might increase readability.  thanks Paul.
    Come on now! Do you you really think you can get a good answer with such a broad question?
    If you are uisng LabVIEW 8.2 or better then LVOOP is what you want to look into.
    LAVA has a forum devoted to OOP in LV and can be found here. If you are not uisng LVOOP then that site is your best resource for help.
    At this link you will find a document that talks about what went into LVOOP.
    If you are an old time OOP type you will probably be disapointed that the is no "call by refence" (yet) and you will have to "roll-your-own" if you want a design that uses Active Objects.
    I believe there is a style guide built into the LV help.
    Did I cover the main points?
    Ben
    BTW "LVOOP" = LabVIEW Object Oriented Programming and is often pronounced like it is a french word "la-voop".
    Ben Rayner
    I am currently active on.. MainStream Preppers
    Rayner's Ridge is under construction

  • Folder of application builder(*.exe) with run-time DLL

    My application consists of main.vi, subvi folder, and example folder.
    In addition, I have to add the run-time libraries for add-on tool kit (advanced signal processing, lvwa.dll) which should be located in the root folder.
    (For exe application, can I set the location of DLLs to not the root folder but "DLL folder"?)
    In my several trials, I can't maintain the hierachy of "example folder".
    Instead of my intension, the NI application builder copied the files in the folder to the support directory.
    Can I locate the "example folder" to the root folder by using NI application builder?
    In summary, I want to get the folder structure by application builder.
    main.exe, DLL folder, Example Folder.
    메시지가 08-08-2008 01:30 AM에 labmaster에 의해 편집되었음

    Hey Labmaster,
    What version of LabVIEW are you using?
    I am not too clear as to what you are trying to do. You can create folders and add anything from your project when creating an installer under the Source Files section in its properties.
    It might be easier if you'd attach a screen shot of what you are doing or trying to do.
    Aashish M
    Applications Engineer
    National Instruments
    http://www.ni.com/support/

  • Where do I find the VISA installation drivers to add to my application builder for my LabVIEW app?

    I need to add the VISA installation drivers to my LabVIEW application builder, but I don't know where to locate them. (I found the instructions on adding the drivers, but it didn't tell how to find them: http://digital.ni.com/public.nsf/3efedde4322fef19862567740067f3cc/e09ba0e2f31d304f86256a640070058e?OpenDoc ument)

    The following webpage contains the NI VISA drivers that you can download:
    http://digital.ni.com/softlib.nsf/display?ReadForm&lookup=NI-VISA&view=current&node=132060_US
    Chris_Mitchell
    Product Development Engineer
    Certified LabVIEW Architect

  • Application-Builder-Exe with Web-Server crashes

    Windows XP Service Pack 2
    EXE file created with Application Builder
    Web-server active - as picture 1 time per second
    Access from browser in local network:
    3 times has occured application crash:
    Yesterday:
    10:26:34
    Application fault VI-app.exe, Version 1.0.0.0,  module fault: lvrt.dll, Version 8.6.0.4001, Address 0x007424c3.
    10:30:21
    Memory fault 1129110434.
    13:50:59
     Application fault VI-app.exe, Version 1.0.0.0,  module fault: lvrt.dll, Version 8.6.0.4001, Address 0x007424c3.
    Now:
    First access with browser at 08:03, second acess at 08:24
    08:26:07
    Application fault VI-app.exe, Version 1.0.0.0,  module fault: lvrt.dll, Version 8.6.0.4001, Address 0x007424c3.
    08:30:49
    Memory fault 1129110434

    Hey Hellboy,
    Please have a look at this thread -> http://forums.ni.com/ni/board/message?board.id=170&requireLogin=False&thread.id=194442
    You might find some hints due to the facts its discussing the same error.
    Christian 

  • Application build problems with polymorphics

    In LV8, when I try to build an executable application I get an error about polymorpics.
    It says to us an "instance" of it instead of the polymorphic.
    Anyone know an easy way to search out all of the polymorphics and then how to convert them over to something that will "build"?
    Thanks
    Jim

    Jim,
    Is there any sort of error number or additional text that is associated with that error?  Checking the "Disconnect...unused polymorphic instances" should remove any unused instances and automatically remove them from the build and is mostly for saving some space.  Is this older code that you have opened in LabVIEW 8 or was it all developed in 8?  If it is older you may try to Mass Compile it to make sure that all of the VIs are linked correctly.  One last thing to try is addressed by this KB:
    http://digital.ni.com/public.nsf/websearch/86256A47004E16D186256B1A006C76EC?OpenDocument
    This is in LabVIEW 6.1 and should be taken care of in previous releases, but its something to try before you have to go through you code to try to find all of the polymorphic VIs. 
    Hope this helps!
    Andy F.
    National Instruments

  • C++ build error with LabVIEW DLL

    Hi, I'm a student at UC Irvine learning to use LabVIEW.  I am working on a practice project for which I have to use a PID system to control the temperature of an object.  Things are starting to get a little messy with nested control statements, loops, etc., so I figured I'd export a LabVIEW DLL with all the hard to code stuff, such as interfacing with my instruments, and plotting data or whatever, and do the number crunching and keeping track of stuff in C++.
    The DLL file I made in LabVIEW went off without a hitch as far as I can tell, but when linking it to my C++ test program (which at this point is just including the LabVIEW's .h file for the DLL and an empty main() function), I get a lot of build errors.  I am using Dev-C++ which uses g++ to compile the code.
    Here is a pic of my build errors:
    Solved!
    Go to Solution.
    Attachments:
    LabVIEW_compile_error.JPG ‏184 KB

    Normal windows apps are not as forgiving about where you can put your DLL as LabVIEW. You have to have a DLL either in the direcotry where the executable file itself resides (that would be your build directory, not the source directory), the windows or system directory, or any directory that is set in the PATH environment variable. Anythin else will most likely not work, or at least not reliably.
    No need to add the cintools directory into your include file paths nor the library file paths. you would only need that if you decided to let the DLL export native LabVIEW data types in which case you would need the LabVIEW manager functions to prepare the correct data buffers.
    Rolf Kalbermatter
    Message Edited by rolfk on 07-30-2009 07:49 AM
    Rolf Kalbermatter
    CIT Engineering Netherlands
    a division of Test & Measurement Solutions

  • Interfacing a C++ Console Application Genetic Algorithm with LabVIEW

    Hi,
    I am have recently modified the GENESIS genetic algorithm using C++ so that it runs on a Windows machine (before it only ran under UNIX). In my experimental work the aim is to control everything using LabVIEW, including this Genetic algorithm.
    My problem comes from the fact that the Genetic Algorithm is set-up as a console application, a library file is created  containing the input parameters of the VI, then this is joined with an evaluation function that is dependant on the library file an an executable is created.
    I need to take some information collected from LabVIEW and give it to the genetic algorithm, but I don't know how to do this.
    Any Ideas?
    Thanks
    Alan Homer

    You can run most applications from a command line using the location/application.exe (where the location is where the executable is stored), all c++ applications run using:   int main (int argc, char **argv); where the argc is the number of arguments and argv is essentially a string table with the parameters passed to the program (will be used as code) the output if a command line application is the std out which can be piped to file or wired out from the standard out terminal.  To pass parameters from your LV code to the command line you should know the parameter list (sometimes empty). 
    Paul
    Paul Falkenstein
    Coleman Technologies Inc.
    CLA, CPI, AIA-Vision
    Labview 4.0- 2013, RT, Vision, FPGA

  • Application builder and dynamic class VIs name collision

    I'm, using LabView 8.6 and I'm trying to make executable file. 
    The application builder returns warning:  
    "LabVIEW prevented a file name collision during the build. Duplicate file names cannot be copied to the same destination. You can rename files as part of the build process to avoid name conflicts."
    ...and no executable is created.
    I'm pretty sure the warning comes from the fact that I use dynamic class member VIs, that are by definition have to have same names in both parent and children.    
    The following link (http://zone.ni.com/reference/en-XX/help/371361E-01/lvhowto/caveats_apps_dlls/) says " If you don't rename the files, Application Builder moves the files to different folders for you to avoid a filename collision.", but no folders are created.
    Any help here? 

    Hi,
    If you have a parent class and one or more child classes, during the build LV will create a folder for each class with a conflicting VI.  The offending VIs will be dumped in their respective folders, resolving the conflict.  For what it's worth, I've used dynamic dispatch VIs several times in executables in LV 8.6 without seeing the issue you're reporting.
    My only advice would be to:
    1) make sure that you haven't somehow put two VIs of the same name in the same class (not even sure that's possible).
    2) make sure you aren't renaming a VI during the build and creating a conflict
    JasonP - CLD

  • I have a application build in labview 8.5 for Windows XP using NI Visa functions to interact with hardware , how to make is work in Windows 7 32 bit and Win 7 64 bit

    I have a application build in Labview 8.5 which wroks fine with Windows XP , this program uses basic read /write functions of NI Visa to communicate with Hardware . This application doesnt work with Windows 7 32 bit/64 and Vista . What changes i need to do to make it work for the said operating system

    srinivas wrote:
    Sorry for confusion ,
    My question is what changes i need to do in code or while making the installer to make the existing program work with other Windows operating system
    You need to make sure the machine have the corresponding NI-VISA installed. Check in the NI software pages for the right version.
    Also make sure that the com port's can be selected when you first start the application. Eg. if you refer to VISA "COM1" on the XP machine It might be "COM2" on the Win7 machine.
    Br,
    /Roger

  • Can i build an application with Labview 2009 for Windows 7?

    Hello
    i use Labview 2009 SP1 and the application builder 2009 SP1. If i install the application on win7 this message is display:
    Labview Run Time Engine depends on pruduct with upgrade code (...) version 9.0.301, language {} which is not in distribution.
    Solved!
    Go to Solution.

    Is this an issue with Windows 7 having both installation folders for 32 bit (C:\Program Files (x86)) and 64 bit (C:\Program Files)?
    I had an application built on an XP machine and installed on a Windows 7 machine which was looking for files in C:\Program Files when they were actually installed in C:\Program Files (x86) - because it was 32-bit application.  After installation I had to move the files from 1 location to the other to make it work.

  • Problems with Application Builder and NI-DAQmx drivers in Labview 8.2 Professional

    Hello everyone,
    I am trying to use the application builder to create an executable so that someone without labview is capable of a remote panel connection to connect to our test laboratory.  our test laboratory uses the USB Compact DAQ  9172.  I did find some other forums that ran into a similar problem where a computer that didnt have labview installed on it looked for a particular driver (nilvaiu.dll).  The common solution appeared to be when building the installer, include the current NI-DAQmx (8.3 in our case) option and then the clients worked fine.   My question is when i use the application builder to create an installation file for this application, i get a prompt to:
    Locate the "National Instruments Device Drivers - February 2006 Disk 1" distribution. LabVIEW needs to copy a component installed or updated by the distribution to continue building the installer.
    What is confusing is that the installation cd's in our laboratory are from August 2006 (501165N-03).  It didnt make sense to me that i would need to downgrade the drivers from a few months ago, but i've been wrong before.  We just upgraded from the full development to the professional version about 2 weeks ago to utilize the application builder function.  Has anyone else ran into this problem and could this be a limitation because we purchased the software with the academic discount?
    thanks in advance
    Chris

    Chris,
    My "fix" is brute force.  Backup everything.  Removing all the NI software takes a while.  Be sure to remove leftover directories and files. 
    Altering the windows registry takes seconds and is not hard if you know what you are looking for.  I've attached a screen shot with the NI entry selected.  This is what I  deleted on by machine.  The thing to remember is that the registry controls all the software on your pc.  Delete/alter the wrong entry and you have problems.  Worst case scenario is that you could end up formating the hard drive and starting over from scratch.  I'm not trying to scare you, but I want to make sure you understand the potential for harm. 
    One thing you might try first.  NI-DAQmx 8.5 is now available for download from NI.  You might try unloading 8.3 and installing 8.5. 
    Attachments:
    regedit pic.JPG ‏102 KB

  • Cannot build application with labview 7.0

    I had built application previously using labview 6.X while some of the V.I. are without block diagrams, but I couldn't do that any more with labview 7.0 as a error will be prompted, why is this happening & are there difference in application builder between labview 7.0 and previous version? Must I load those V.I. without block diagrams dynamically now ?

    Unfortunately it is impossible to build application with newer version with VIs without block diagrams, which saved in oldest version.
    from ni web site:
    "National Instruments does not recommend saving VIs without block diagrams because LabVIEW needs the block diagram to recompile the VI after an upgrade. When you upgrade LabVIEW, you must find a version of the VI that includes its block diagram to recompile it. Such a version did exist before the block diagram was removed because it is impossible to create a new VI without a block diagram."
    "Based on that information, it should be clear that once a VI is saved without diagrams:
    You cannot open or run the VI on any other version of LabVIEW, older or newer."
    More information:
    http://digit
    al.ni.com/public.nsf/3efedde4322fef19862567740067f3cc/00a6bacda1c01a0786256b60006163e7?OpenDocument
    http://digital.ni.com/public.nsf/3efedde4322fef19862567740067f3cc/28c4cb0cf83e1a1d862566e2007a2a9c?OpenDocument
    http://digital.ni.com/public.nsf/3efedde4322fef19862567740067f3cc/fee732f4b1541b9586256bf0006a78ca?OpenDocument
    http://digital.ni.com/public.nsf/3efedde4322fef19862567740067f3cc/0649a3350de20aa186256d91007b3d61?OpenDocument

  • I would like to display the pause button in an executable built with the LabVIEW 6.0.2 application builder.

    When we upgraded to LabVIEW 6.0.2 (Windows) the executables no longer had the pause button in them. This was a useful feature but I can't find an option to display this button in the Application Builder. Please let me know if this option has been removed and whether I need to allow for pauses to be built into the programming. Thanks.

    A well designed application shouldn't need to be aborted the hard way but if you want this feature, you can enable it in the application builder settings.
    Under the "VI Settings" tab, select your Top Level VI and press "Edit build settings...".
    Change the item "User can abort VI" to "Yes".
    LabVIEW, C'est LabVIEW

Maybe you are looking for

  • Time Machine won't let me back up an external hard drive

    Hello, I am running time machine to backup onto a 500GB USB drive and keep my iTunes library on a firewire 250gb drive. When I looked in time machine options in system preferences I found that my firewire disk is already listed as 'do not back up'. I

  • HELP: How to configure ichat

    I want to use google talk on ichat. what i've done so far. - registered with google talk - downloaded spark - failed to create a new spark/ jabber account using my google talk id. which server i need to fill in here?? talk.google.com??? i'm really st

  • The user admin is not authorized to make the Create Order request

    Hi, I have deployed the PiP and trying to create the order. But i am getting the below error The user admin is not authorized to make the Create Order request> Please note :-- I have assigned roles in administrator I have assigned permissions in Webl

  • Help with Bridge CS5 reading RAWs from a  Nikon d7100

    So just bought a Nikon D7100, and not Bridge and PS CS5 cannot open my RAW photos. Is there something else I can do, besides upgrading to cs6?? My current version of bridge is 4.1.0.54 and photoshop 12.1

  • JVM crashes when converting jstring to native string

    Hi , I am trying to convert a jstring to a char * . My main program is in C. I tried calling the two methods : const char str = (env)->GetStringUTFChars(env, myJstring, 0); and const char *result = JNU_GetStringNativeChars(env, myJstring); Both the t