LV 8.0 App Builder - Installer including NI-VISA

Hallo,
how can I include Ni VISA into the installer files with the LV 8.0 App
Builder for using Visa functions?
Kind regards
Niko

Hi Niko,
Matt's right on the money here. You can check out these links if you need more detail:
http://zone.ni.com/devzone/conceptd.nsf/webmain/5ADBC06AC32E508A8625706E0062EBD1
http://zone.ni.com/reference/en-XX/help/371361B-01/lvdialog/addl_install_info_db/
Let us know if you have questions!
Charlie S.
Visit ni.com/gettingstarted for step-by-step help in setting up your system

Similar Messages

  • USB/Serial Drivers and App Builder Installer Questions...are drivers included in the Installer with the LV runtime engine?

    Hello all,
    I'm wondering if someone can help me out with how drivers and all are treated with applications distributed with App Builder, used to create a stand alone, full install of app and labview engine with Installer.
    What has happened  is, my application was created using the NI branded USB to RS232...and USB to RS485, and they work great.
    On the application when running..you fire it up, it finds the USB to serial device, and I have a dropdown that finds the available COM ports to use (along with setting parity, etc).
    I've installed on different computers (without previous labview installs) with the installer. They all worked.
    The customer has received the installer....and despite us telling them to use the NI branded USB/Serial interfaces..they are trying to work with a different USB/serial cable.
    They say the COM ports aren't even showing up when they run the installed application.
    So, I'm not sure where to start. Is this a driver issue?  Does the App Builder Installer...install the drivers for the interfaces I was using with it? Is there a way for the person to find and install a driver on their own...or would I have to somehow find out a driver for what they use....then, basically redo the App Builder Installer build...to include that driver with the executable I send back out?
    I guess I basically need a better understanding of how drivers for external access/communications are handled when you use App Builder to create a stand alone application complete with the labview runtime engine...and nothing else.
    Thank you in advance,
    cayenne

    The main thing is that LV uses VISA to talk to serial port whether native on the machine or from USB dongles that you plug into the computer. It sounds to me like their dongles aren't working.
    Can the customer see the ports in the Windows Device Manager? Can they access them through something like hyperterminal? How does your program find the USB/Serial devices?
    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

  • Runtime Error building Installer with NI-VISA Runtime

    Greetings,  I'm getting this error whenever I check the "NI-VISA Runtime" option in the installer app builder.
    Everything builds fine when I check only the Runtime Engine.  Shown below is what causes the RUNTIME ERROR and closes Labview Unexpectedly.
    Any help you could provide would be very much appreciated.
    Regards,
    JD

    Hi JD,
    This is a relatively common error with the Application Builder that can happen for several different reasons, namely registry keys pointing to installations that no longer exist. The easiest way to identify the problem is to get detailed information about the installer build. Here are directions:
    LabVIEW has the
    ability to create a very detailed log of the events that occur when
    building an application or installer. To enable this feature, open up
    the LabVIEW.ini file and copy "CDK.EnableLog=true" to the bottom
    of the file. Save the changes and close the ini file. The LabVIEW.ini
    file is usually located in C:\Program Files\National
    Instruments\LabVIEW X.X
    Enabling this feature will create a log file in the %temp% directory of your computer (%...% means a computer variable) .
    To
    find out where this temp directory is located, go to Start>>Run.
    Type in "cmd". Then type "set". This will return all of your computer's
    variable names.
    Look for TEMP in the list of variable names. You should see something like "TEMP=C:\DOCUME~1\user\LOCALS~1\Temp".
    Navigate to this directory using Windows Explorer.
    You
    should see a file named "Name.log" where "name" is the name of your
    build specification. For example, you might see "My Installer.log" if
    the name of your build specification is "My Installer".
    This will give you a more detailed log of the attempted build and, if I'm correct about why this particular build failed, show you which installer is expected at that registry. If the registry points to a directory without the necessary installer (i.e. VISA), simply delete the registry and allow the App Builder to prompt you to to point to the correct location.
    Michael K.
    | Michael K | Project Manager | LabVIEW R&D | National Instruments |

  • LabVIEW 2010 App Builder/Installer- Target OS Options

    I will shortly be migrating from LV8.6.1 Devloper Suite in Win XP 32 bit to 2010 running in Win7 64 bit.
    Does the applicationbuilder and installer have the option to deploy Win XP 32 bit applications along with the corresponding run time engine?
    Thanks
    -AK2DM
    ~~~~~~~~~~~~~~~~~~~~~~~~~~
    "It’s the questions that drive us.”
    ~~~~~~~~~~~~~~~~~~~~~~~~~~
    Solved!
    Go to Solution.

    Hmmm, do you have a time machine?
    LabVIEW 2011 is not released yet. You'll have to wait until August for that.
    There is no specific Windows XP selection in the setup section of the Application Builder. It will simply create an installer for whatever Windows platform you are running at that moment. So if you run LabVIEW 32 Bit it will create a LabVIEW 32 Bit application and installer and if you run LabVIEW 64 Bit it will create an according application and installer. Needless to say that 64 Bit application and installer can only run on a 64 Bit system, while you can install the 32 bit application on either system.
    Rolf Kalbermatter
    CIT Engineering Netherlands
    a division of Test & Measurement Solutions

  • App Builder Installer Build Registry Keys no longer created in Vista.

    This board has been a great resource for answers...thank you all for your help.
    Last week (7/31/09), an automatic MS Windows Vista Home Premium
    upgrade was performed on my development PC.  After the upgrade, I
    used AppBuilder to build the final version of my application, which writes
    3 string keys to the Window's registry.  The Installer build completed successfully,
    however, when I run setup.exe, I received an OS error stating that I don't
    have permission to update the registry.  I have full admin rights AND
    User Account Control (UCS) is OFF.  This error notification occurred 3
    times, once for each registry addition attempt.
    The installation was working correctly prior to this Vista update and still works in XP.
    Any help would be greatly appreciated!
    Please note that this is VI independent- the registry keys were created through
    the AppBuilder 'Installer' tool.
    I worry that this problem will manifest itself with all new LV application installations
    that have the Vista upgrade.

    Does the installation fail only when you try to install on computers that have the Vista update?  Or since you have updated your development computer, when you build the installer again the installation will fail on any computer?  Have you tried installing it on more than one computer with the Vista update?
    Please attach the installer log for when the installation fails.
    http://digital.ni.com/public.nsf/allkb/AB597E885DB7D16B86256E92006DB232?OpenDocument 
    Cheers,
    David Goldberg
    National Instruments
    Software R&D

  • Impossible de télécharger la dernière version du DPS Apps Builder- fichier d'installation endommagé

    Bonjour,
    J'essaye sans succès depuis hier de télécharger la dernière version du DPS
    Apps Builder depuis votre site ou via le support en ligne et à chaque fois
    que j'essaye de l'ouvrir il me met le message :
    Désolé, une erreur s'est produite.
    L'application n'a pas pu être installée, car le fichier d'installation est
    endommagé. Essayez d'obtenir un nouveau fichier d'installation auprès de
    l'éditeur de l'application.
    J'ai réessayé 20 fois.
    Je suis sous Max OS X (version 10.6.8)
    JE CRAQUE !!!
    Help me
    -- Sophie JOSSE

    DPS App Builder installer file is damaged

  • How do I create a single file installer for LV 6.1 App Builder Output?

    I have created an application using the 6.1 App builder and it installs fine. To be able to send this app to others, I would really like to put it in something like a self extracting executable file. How can I do this with app builder or can you suggest another software to buy that will let me create this.
    Thanks for any help that you can provide

    You raise a number of important points. I'll answer to the best of my knowledge.
    1. Usually true. Win98/2K/XP have the Windows Installer Service built in, but 95/98/ME require InstMsiA.exe, and WinNT4 requires InstMsiW.exe. The difference is in the character set (ASCII vs. Unicode), and I don't know how that difference applies to the non-Roman alphabet installations. It's safest to include both if you're going to include one.
    On the same subject, I noticed that the first thing the LV7 evaluation installer does on a Win2K box (and therefore probably on a Win98 box as well) is update the Windows Installer service, so LV7-built executables may very well require InstMsiA.exe/InstMsiW.exe on Win98/2K.
    2. I think so. I usually don't distribu
    te LabVIEW EXEs as self-extracting installers, but it probably is safest to wait until the setup is complete before returning control to the self-extractor software.
    3. True. (And note that one of the circumstances under which you might repair/update msiexec is with LV7 on Win98/2K).
    4. True. Setup.exe appears to install/update msiexec if needed and then launch the MSI file.

  • Build an installer including folders that aren't in project?

    My VIs work in my project.  I am programmatically deploying two libraries.  When I build an application and run that the libraries don't deploy even though they are "Always Included" in the application build.  I think this is because they reside on my computer in folders and the application builder doesn't know what to do with them.  All that doesn't really matter to me because if I manually move the folders to the location where the built application resides, it works as expected and deploys the libraries.  The problem is when I want to build an installer for someone else to run on a remote computer.  I can't choose the folders with the libraries in them and where they should install to when I build the installer.  What am I expected to do?

    I've had similar experiences with getting non-referenced files included in the application builder. The solution I found was to create a new folder in the destinations tab of the app builder and select all the non-referenced files to be placed there in the source file settings tab. I've only used this solution with an application builder, and have never created an installer program, but hopefully it will work for this too.
    Hope this helps,
    Andy

  • How to include Instrument drivers in Lab-view apps builder

    Hi,
    I am using Labvier 7,1, I have managed to use the Application builder for a simple program, but have problems with a larger program that includes P & P instrument drivers (for GPIB)
    I can create an installer, but when I try & install it, I get a great number of errors, all relating to being unable to find all the vi for the Instrument driver functions.
    I tried several variations,  including support files, & including the instrument driver dll's from C:\vxipnp\winnt\bin\
    this time I got app f.ailed to start , needs VISA32. dll was not found.
    I had expected there to be a standard way of using applications Builder to include GPIB p & P Instrument drivers, guess I'm nieve, being a newbe. Any help will be greatly appreciated
    Mikesub

    The app builder prior to 8.x was only designed to install the application you created. The actual instrument driver VIs should be included in the app but the IVI driver itself (the low level dll) is not. You should really include the installer for the IVI driver and not just the dlls. This is the .msi file that is on the instrument driver download page. If you are getting an error about VISA32, then it sounds like VISA was not installed either. I usually install VISA and NI-GPIB from the CD that comes with the GPIB board and I do this when I install the board into the computer. However, you can also include these installers with your app as well. On the Installer Settings tab, click the Advanced button. You have the option there of 'Run executable after installation'. The simplest thing to do is to create a .bat file that will call the other installers you include with the distribution. Don't forget that you also need the IVI Compliance Package so include that installer as well.

  • Provisioning Profile - problems with installation our app build on devices

    We have problems with installation our app build on few devices. There are all in Provisioning Profile, but we don't know why we can't install the build on some devices. Any ideas?

    Apple products needing Apple love/support (athough using Adobe to compile to Apple-code may be an obvious concern since nothing beats native-code)
    The app still however requires code-signing in the correct manner - personally, the more the merrier.

  • App Builder generates Error 1 when I create installer

    When I compile my project without creating the installer, it runs fine. However, when I check the box "create installer" (with or without the Advanced /LV Runtime Engine box checked), the build fails, and I get an Error 1 - ..Input Parameter is invalid. See attached scrren snapshots.
    Attachments:
    CompilerBug_TTower.xls ‏39 KB

    Bill, NI Tech support suggested I save my project in LV60 format, recompile, and see if the error still occurs. I did this. However, I could not export the .bld file from LV61 to 60, so I had to re-create it. No error occurred when I compiled this (with installer) in LV60. I then loaded this project back into LV61 and compiled it - also, no error! So I have no idea what caused this. However, I did ask NI for a wish list item - to add more error info in App Builder, so that one knows what input parameter or VI caused the problem. (With 300 Vis is a project, it is a daunting task to find the probelm otherwise).

  • How to build an installer including the vision Acquisition Software

    hi all, my question is "how to build an installer including the Vision Acquisition Software".
    is it enough to select "2010 Run-Time Engine" "Vision Run-Time Engine" and "NI-IMAQdx"? Its ok with the "2010 Run-Time Engine" but there is some problem with the other two.
    can some one help thanks a lot!

    hi again, i have some problem with install Vision Run-Time Engine
    must i install RTE with the Serial Number, or i can chose the "install this product for evaluation" to continue the installing, maybe active it later. But after i chosed "install this product for evaluation" and finish the installing, i still cant find RTE from my disk.
    i cant even chose my path to install the RTE. Can u plz tell me what is wrong with that?

  • Build installer LV2009, requires OLD distribution installation disks?

    When building an Installer using LabVIEW 2009, and including additional distributions, why does the installer builder require the original distribution disks from the install DVD/CDs?  Why are the version required not promoted to the LATEST update installed?  This is a real PITA when I have to go find the disks from 1Q2009, no wait, it did not ask for that, it asked for Feb 2009 device drivers disk 2. 
    This is as bad as Microsoft for installing from original distributions.  
    It is not a good thing to expect that I have to maintain a library of DVDs/CDs for every distribution/update I have ever used.  Especially when I am taking work home, and do not have access to this ENTIRE library, rather a copy of the lasest update ONLY.
    to National Instruments, Thoughts on this?
    Paul <--Always Learning!!!
    sense and simplicity.
    Browse my sample VIs?

    Thanks Craig... BUT, I only have LabVIEW 2009 Intalled.  although I have upgraded components through the quartely updates.  So while what you say is true... it does NOT necessarly mean that you have 'multiple' versions of the LabVIEW development environment installed
    That said... I have been at this for a little while (more than a day, but less than the time since dinosaurs walked)... and app building is something that has become much more complicated over time... I want to know WHY NI does not promote the installers/distributions to the most current version on the update DVD/CD where applicable... but you bring up a good point... If it cannot promote the distribution, it should give you a warning and ASK you if you wish to 'cache' the obsolete distribution as it does when building the current distribution.  This gives you an option to cache it WHILE the distribution is handy.
    Failing that, in the project, there should be an option to have it display the currently required distributions as opposed to having to build the installer object, start the installer build, then wait for it to ask you.... by then it maybe too late.
    I realize that you are trying to help/offer workarounds... I appreciate what you are trying to do... BUT, in this case, I want NI's people to justify what they are doing and why.  This goes beyond wish list, this requires justification, as even Microsoft has addressed this issue.
    Paul <--Always Learning!!!
    sense and simplicity.
    Browse my sample VIs?

  • DPS APP Builder Error Code 1

    Hello,
    I'm getting an Error Code 1 message when trying to download the test APP from the DPS APP Builder. I've tried re-building the document (a process that takes almost 8 hours in my case as our APP features 110 articles including almost 1000 images), updating it, generating new certificates and any other workaround mentioned in a previous discussion about this same subject. Nothing worked for me.
    The only workaround I haven't tried is deleting the folio from ~/Library/Preferences/StageManager.BD092818F67280F4B42B04877600987F01 11B594.1/Local Store/dmp.
    Apparently, there's nothing called "StageManager" in my MacBook Pro. Not in this route neither in any other route.
    Any idea about how to solve this? (if possible without re-building once again the whole document) We can't wait until the error code 1 bug is fixed in future Adobe updates as we need to submit the APP to Apple next week.
    Thanks for your time.

    Anyone can help??
    Update my latest experimental results.
    I found that issue was folio package related.
    Because when I use another folio package to the same app item in App Builder, this error message does not appear.
    But the original package in exchange, this error information occurs.
    Are there helpful to solve this problem?

  • File name collision during build that includes Report Generation toolkit. How to correct?

    When I switched to LV 8.6 (it's also in 8.6.1) I started getting a file name collision warning when building an installer that included the Report Generation toolkit. The executable works, but I don't like to leave warnings uninvestigated. I don't understand 1) why it's happening now and 2) what it's recommending for the fix. Here's part of the actual warning it gives.
    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.
    The following files were moved to a unique
    location:
    C:\Program Files\National Instruments\LabVIEW
    8.6\vi.lib\Utility\NIReport.llb\Append Control Image to Report.vi
    C:\Program
    Files\National Instruments\LabVIEW 8.6\vi.lib\Utility\NIReport.llb\HTML\Append
    Control Image to Report.vi
    C:\Program Files\National Instruments\LabVIEW
    8.6\vi.lib\Utility\NIReport.llb\Append File to Report.vi
    C:\Program
    Files\National Instruments\LabVIEW 8.6\vi.lib\Utility\NIReport.llb\HTML\Append
    File to Report.vi
    C:\Program Files\National Instruments\LabVIEW
    8.6\vi.lib\Utility\NIReport.llb\Append Horizontal Line to Report.vi...........

    Hi GS,
    The architecture of the Report Generation Toolkit was changed in LabVIEW 8.6 to utilize LabVIEW Classes.  As such, there are some warnings during an EXE build because the class VIs have identical names.  Classes were not used in the toolkit in LabVIEW 8.5 and previous...that's why you didn't see any warnings during the build until now.
    Your EXE should still function properly, and you shouldn't have to change anything about your build.  The purpose of the warnings is to let you know that the duplicate-named VIs needed to be handled differently during the build.
    -D
    Darren Nattinger, CLA
    LabVIEW Artisan and Nugget Penman

Maybe you are looking for