Visa Control grayed out when executable used with Run-time Engine

When I run an executable on a machine with only the Run-time Engine the Visa Control for Com Ports is grayed out. I'm guessing that I am missing a library, but do not know which one.

You need to install the VISA run-time. If you are just using VISA for serial communication, then there is an option on the app builder (Installer Settings>Advanced) for Serial Port Support. This will add a much smaller version of the VISA run-time engine to the installer you create. If you are using GPIB, etc., you have to install the hardware driver (i.e. NI-GPIB) and the full VISA run-time engine.

Similar Messages

  • How to load dynamically String into a VI using LabVIEW Run-time Engine Version 7.0?

    I would like to be able to traduce string into my application using import string method. I create an program with my VI to translate. When I use the import method, I get this error: the VI is locked. WHY ? because it works well in the edit mode but not using LabVIEW Run-time Engine Version 7.0 .

    Hello loup,
    If you call dynamically a VI in your LabVIEW application you must add this VI when you build the .exe file.
    To add this VI, go to the Tab "Source Files" when you build application and click on "Add Dynamic VI..." then chose the VI you call.
    It should solve your problem.
    In the attached file you can found an example of LV program that translate front panel.
    Try to build exe file and add "Languages.vi" as dynamic VI and .txt files as "Support files".
    I test it, it works.
    I hope that this will help you.
    Best Regards,
    Sanaa T
    National Instruments
    Attachments:
    Translation.zip ‏69 KB

  • Can I use LabView Run-Time Engine on Windows XP?

    An Application uses LV Run-Time Engine 5.1, i want to use this application on windows XP, can i use the same version of the RTE, if not, what is the solution??

    To eleminate the possibility of errors, you need to convert the application to a version fully compatible with windows XP, like 6.1 or 7.0 (6.02 should do it)
    Would version 5.1 work with XP, NI do not gaurantee that. However, I had installed apllications written in version 5.1.1 and worked fine under XP. In your case, just give a try, if it did not work as expected, you may have functuionality that may not be fully comptaible with XP.

  • My executable compiled with Real Time Engine 5.1.1 in App Builder gives error when trying to run in App Builder with RTE 6.1

    Hello.  I built an executable using App Builder in LV 5.1.1 and now, years later, I am trying to run it in LV 6.1 but I get an error stating a requirement for Run Time Engine version 5.1.1.  To be able to run this, must I install the older version of Run Time Engine?  If so, where can I find the older version?  Do I have to install the older version of LabVIEW to get the RTE?  Will having both versions on my pc be a problem?
    I assume that once I am able to run the exe, that I will be able to recompile with the newer version of the RTE using App Builder.  Is this correct?
    I have been away from LabVIEW for several years and am a bit rusty on these details that I once knew.  Any help is appreciated.
    Alex

    The version of the run-time engine must match the version of LabVIEW that was used to create the executable. You can get any version of the run-time engine you want here. The only way to create a version 6.1 exe is to re-build it from the source code with diagrams. An exe has no block diagram so it cannot be converted to a newer version.

  • Error -18004 with LabVIEW Adapter using LabVIEW Run Time Engine 7.1.1

    Hi to all,
    I am trying to use the LabVIEW Run Time Engine 7.1.1 instead of the Development System for executing VIs in TestStand with the LabVIEW adapter.
    The Problem is that I get the following error, saying that my VIs cannot be executed:
    -18004; An error occurred accessing the LabVIEW Run-Time Engine DLL.
    All my VIs were masscompiled with LabVIEW 7.1.1
    How do I manage this problem, in other words how do I get my VIs in TestStand to run with the LV Run Time Engine?
    Thanks for you help,
    - Caribe -
    PS: I configured the adapter to use the  LabVIEW Run Time Engine 7.1.1. When I check back in the dialog "LabVIEW Adapter Configuration" the selector went back to LV Runtime 7.1??? Thats weird dude!

    Hi Caribe,
    Did you find any solution to this weird behaviour? Even I am facing the same problem! If we set the adapter as LV 7.1.1 runtime engine, it changes back to LV 7.1 runtime engine.
    I am also facing -18002 error after mass compiling LV 7.1 folder and my source code folder.
    If you can share your solution, that would be of great help to me. If i couldnt find any solution, I have planned to revert back to LV 7.1 version.
     Thank you,
    Sasi

  • Why is VI not executable using Labview 7.1 Run-Time Engine?

    Hi,
    In our Teststand sequence, we have a Labview Action step which is returning an error: "The VI is not executable", along with the error code: -18002.
    This error occurs on a Production PC using the L.V. 7.1 Run-Time Engine.
    I'm aware of Mass Compiling to ensure all the VI's are the correct version, but this has not resolved the problem.
    The software was installed on the production PC using a Teststand created installer, with the Labview Adapter set
    correctly to the Run-Time Engine, i.e. not trying to open the Labview Developer Server to execute the step at run time.
    Because it's the 1st Labview module to be executed, I added another similar step to run beforehand, i.e. the new simple
    Labview code ran first. This executed correctly, but then the next step caused the error above.
    The small number of associated sub-vi's are on the target PC, and have been mass compiled.
    I've had -18002 errors before, but this is one I cannot cure.
    All suggestions gratefully received.
    Gary.

    Hi Guys,
    Regarding this -18002 error when using the Run Time Engine instead of the Development Environment, what is the VI within the step that is failing (in any of the cases you've mentioned) trying to do? Are they built around any toolkits?
    In my experiments with a simple VI (with just a user dialogue) using the LabVIEW 7.1 RTE in both TestStand 3.1 and 3.5 this morning, I haven't found any issues
    There is a possibility if any of the sub-VIs or toolkits you use contain a Merge Errors.vi, that the Run Time Engine picks up a copy of the VI built for previous versions of the RunTime Engine (due to the order in which the sub-VI directories are scanned), and it cannot convert it.
    There are a few solutions for this, the easiest one looks to be to copy the error.llb\Merge Errors.vi for LabVIEW 7.1 into the same directory as the VI you're calling (so TestStand can pick it up easily).
    Can you let me know if this solution helps at all? If not, would it be possible to post up any of the code or sequence you're having problems with?
    Best wishes,
    Mark
    Applications Engineer
    National Instruments

  • Can LabVIEW Run-Time Engine 7.0 control LabVIEW 6.1 VIs?

    I'm attempting to remotely control a LabVIEW 6.1 example VI through the browser plugin on another system. On that other system, can I use LabVIEW Run-Time Engine 7.0? Or do I need 6.1?

    Never mind, I should have read the RTE 7.0 information first. I need LabVIEW Run-Time Engine 6.1 to run LabVIEW 6.1 VIs.

  • Call VI in EXE but have it execute in Developmen​t Environmen​t not Run Time Engine

    I am working on building a palette editor for distribution of a reusable code library for my company (I know the VIPM does this very well already).  I have the code complete and am trying to create an executable that I can distribute that will call the code I wrote to update/create the palette .mnu files for the reuse library, which lives on the company network.  I am using the Palette Editing VI's and it seems as though they cannot be built into an executable.  So I wrote some code to dynamically call my palette modification code (I call it the Reuse Library Manager).  When my executable calls the Reuse Library Manager dynamically I get a broken run arrow on the Reuse Library Manager front panel and the following reasons for the broken arrow:
    It seems to me that the reason the Reuse Library Manager works when called in the development environment and not when called dynamically is because the dynamic call uses the run time engine for execution.  This made me think of how in the VIPM it opens LabVIEW while it installs packages.  If anyone knows, does the VIPM open LabVIEW in order to run the Palette Editing VI's or is it for another reason?  If it is this reason how can I force the dynamically called VI's to run in the development environment by opening LabVIEW programmatically from an executable that is running in the run time engine?
    Let me know where clarification is needed.
    Message Edited by jmcbee on 04-28-2009 10:00 AM
    CLA, CLED, CTD,CPI, LabVIEW Champion
    Platinum Alliance Partner
    Senior Engineer
    Using LV 2013, 2012
    Don't forget Kudos for Good Answers, and Mark a solution if your problem is solved.
    Attachments:
    Reuse.PNG ‏14 KB

    Hi jmcbee,
          In spite of years of using LV and building a resuable library of code, I've done very little with customizing the standard paletts, however,
    Many times when deploying a new distributable I've seen a dialog like what you posted.  In most cases the problem was solved by rebuilding distributable to include the missing VIs.  In one case I added the VI-lib to the target-platform and made-sure VI-lib was in distributable's VI search-path.
    There are two ways I know of to build distributables which include the VI-lib code,
    1) Include all VI-lib VIs when building the distributable
     - In LV 8x, uncheck "Exclude Files from VI lib" project-property.
     - In LV 7.1 it's possible but I don't remember how! (probably a post on it around here.)
     - This can add an enormous number of un-needed VIs (see this post.) 
    2) Re-write the VIs so that they are no-longer identified with VI-lib and get included "naturally".
     - Open each VI diagram, select-all, paste in new/untitled diagram.  In your case naming will be tricky, but it's doable.
     - This is a great advantage in 8x as it allows LLBs to be built with File\Save As\Create Hierarchy.
    In addition, here's a tool to call following "Open VI Reference" (if it returns an error.)  This VI open all broken children making it much easier to identify specific missing parts (typically VI-lib.)
    Luck/
    Cheers!
    "Inside every large program is a small program struggling to get out." (attributed to Tony Hoare)
    Attachments:
    Util.VI.OpenBroken.vi ‏57 KB

  • Labview 6.0 run-time engine will not control BKPrecision power supply.

    I created a test program in Labview 6.0 to control a BKPrecision power supply and Measurement computing DAQ in our test system. I am able to control both intsruments from my PC which has Labview loaded on it. I created an executable from the application builder tool for distribution. When i install the run-time engine and executable on a new PC (Labview not installed), i am unable to control the BKPrecision power supply. The BK power supply is connected to the serial COM port of the PC.
    Do i need to install drivers that are not included in the executable build?
    Do i need to install VXIpnp (VISA interactive control)?
    thanks,
    Tim
    Solved!
    Go to Solution.

    tmann-
                The API Drivers are often times for more specific Operating Systems than the others (Linux, Pharlap, etc.) and they are more easily accessible for programmers that want to (and have enough time to put up with the headaches ) of building speciality drivers off of ours. 99% of the time you just want the drivers that come up first when you type in your driver name (NI-VISA). As to versions, issues can crop up later from not using the exact same driver version but all the drivers are built off of each other (they hardly ever scrap an entire driver and start over) so the problems should be minor. Its up to you about switching. Unfortunately to downgrade version you have to completely uninstall the driver from Add/Remove Programs>>National Instruments Software>>Your driver and then reinstall the correct one. If you have time, I think it is well worth it to do it right the first time. Hope this is helpful!!
    Grant H.
    National Instruments
    LabVIEW Product Marketing Manager

  • "Access Control - Do Not Inherit" Grayed out when setting up a backup on Server 2008 R2 when trying to use remote NAS

    I see one response here:
    http://social.technet.microsoft.com/Forums/en-US/c99eead0-e2fc-4c83-8cb2-959d03512667/server-2008-r2-dc-backup-greys-out-do-not-inherit-option-for-file-share-backup
    But it makes no sense to me. Running that command doesn't do anything.
    How do I make the box stop graying out when setting up a backup with the GUI interface? This should be really simple I would think and for some reason the backup utility is graying out the "Do Not Inherit" option so I can backup to the NAS
    device that has access control enabled in order to backup to the NAS.
    Thanks in advance!

    Hi,
    From this article, it mentioned that it is by design that we cannot choose "do not inherit" in backup schedule when backup target is a remote shared folder.
    Checklist: Schedule Automatic Backups
    http://technet.microsoft.com/en-us/library/cc732540.aspx
    If you use a remote shared folder, make sure that the folder is available, that you have write access to the folder, and that you are a member of the Administrators group or Backup Operators group on the computer hosting the folder. Each time you create
    a backup, it will overwrite the older backups so that you will only have one backup at a time.
    The backup will inherit the access control list (ACL) permissions of the folder.
    For the account it required, as mentioned above, it should be "a member of Admin group or Backup Operators group, and it should have write permission on target folder".
    Also map a network folder as a drive will not help show the mapped drive letter in backup destination. It is still a remote shared folder.
    TechNet Subscriber Support in forum |If you have any feedback on our support, please contact [email protected]

  • Am working with trial version of photoshop elements 12. Layer functions remain grayed out when trying to use.

    I'm working with trial version of Photoshop Elements 12. Layer functions remain grayed out when trying to use them.

    You need to have an image open in the main window.

  • Import button remains grayed out when adding existing folder to LR 4

    Greetings.  I'm following the steps in the following link from Adobe:
    http://help.adobe.com/en_US/Lightroom/3.0/Using/WSE828B644-9097-46ab-98A7-E2719BBB6647.htm l
    The final step, after selecting the folder I want to add, is to select Import.  Except, the Import button remains grayed out.  I'm not sure what to do in order to select Import and add the folder I already have.
    Thanks,
    Mike H.

    Thank you for the information.  Yes, that seems to make sense based on what I've discovered using LR 4.  Still trying to come up to speed.  Appreciate everyone's help with their tips and insight.
    Date: Tue, 24 Apr 2012 01:44:25 -0600
    From: [email protected]
    To: [email protected]
    Subject: Import button remains grayed out when adding existing folder to LR 4
        Re: Import button remains grayed out when adding existing folder to LR 4
        created by LRuser42 in Photoshop Lightroom - View the full discussion
    Folders per se cannot be imported - only pictures (or movies) in a folder can. So, you have to select a folder containing at least one picture or movie (all pictures and movies found are automatically selected when the import dialog opens). This is probably not the case for the folder you want to add, so "no photos found" is displayed in the dialog center and the "Import" button is greyed out.
         Replies to this message go to everyone subscribed to this thread, not directly to the person who posted the message. To post a reply, either reply to this email or visit the message page: http://forums.adobe.com/message/4356518#4356518
         To unsubscribe from this thread, please visit the message page at http://forums.adobe.com/message/4356518#4356518. In the Actions box on the right, click the Stop Email Notifications link.
         Start a new discussion in Photoshop Lightroom by email or at Adobe Forums
      For more information about maintaining your forum email notifications please go to http://forums.adobe.com/message/2936746#2936746.

  • When creating an application installer in LV, what run-time engine or driver must be installed to install the VISA interactive control?

    I've created an application installer using LabVIEW's application builder and use it to install NI MAX.  However, after running the installer, the VISA interactive control is disabled in NI MAX.
    The installer installs the following NI components:  NI LabVIEW Run-Time 2014 SP-1(64-bit), NI LabWindows/CVI Shared Run-Time Engine 2013 SP2, NI Measurement & Automation Explorer 14.5, NI-488.2 Application Development Support (includes run-time), NI-VISA Configuration Support 14.0.1, NI-VISA Runtime 14.0.1, NI-VISA Server 14.0, NI Systems Configuration Runtime 14.5.0, vision run-time, dc-power run-time.
    If I download and run the 488.2 installer, the VISA interactive control is enabled in NI MAX.  But, the installer created with the application builder does not seem to install the necessary components.
    What needs to be added to the installer to enable  the VISA interactive control (VISAIC)?
    Thanks.
    Solved!
    Go to Solution.

    From Pedro Munoz, Applications Engineer, National Instruments
    Sorry for the confusion with the forum post that Jon sent you. I did some research on our internal database and I found out the component will not be installed by any of the components added from the additional installers section on the configuration of the installer. As you have already found out you need to install the full installer in order to enable this feature.
    I know that this might be an inconvenient for you because you wanted to have one installer to run. On this case may I suggest using the NI Batch Installer Builder.
    The NI Batch Installer Builder allows building installers that contain National Instruments software from several products. That way you can create an installer for you application in LabVIEW (and not include the drivers in the additional installer section), then use NI Batch Installer Builder to include the installer for your application and the full version of the drivers that you mentioned.
    Here is the download link:
    http://www.ni.com/download/ni-batch-installer-builder-14.5/5193/en/
    And in here you can find instructions on how to get started with it:
    http://zone.ni.com/reference/en-XX/help/374206A-01/
    Let me know if you have any question.
    Regards
    Pedro Munoz
    Applications Engineer
    National Instruments
    http://www.ni.com/support

  • Items grayed out when they should not be

    I have some apps where files that should be available for opening are instead grayed out when they shouldn't be. They never used to be grayed out until recently, and they are a correct file type. (Open is set to "All files" not just the file extension, so it's not an oversight).
    Which part of the OS is responsible for choosing what items will be available in a file list (i.e. not grayed out)? I'd like to rebuild it since it seems to be corrupted. Also my LaunchServices seems to be messed up as well because some apps are not available for certain file types "Open With" when they ought to be. Terminal command? Disk Warrior? TinkerTool? Thanks.

    Hi,
    If you aren't confident in using Terminal check out this site for help with Launch Services.
    http://www.thexlab.com/faqs/resetlaunchservices.html
    Carolyn

  • Labview Executable with VISA functions in Run Time Engine

    Hi Everybody
    I designed a gui to communicate using VISA GPIB. I created an executable for the gui. I also installed LabView Run Time Engine on the desired machine. I recieved couple of errors, for which I copied the files visa32.dll, NIVISV32.dll and serpdrv to the folder with the executable.
    I recieved the following error, ' Initialization of NIVISV32.dll failed. The process interminating abnormally.'
    Are there any drivers I should install in addition to the Run Time Engine? If so, where can I find these drivers?
    Thank you
    Jackie

    I installed NI-VISA with similar version as my development installation, and LV runtime engine. Labview still crashed.
    I noticed certain library functions in full labview that is not present in the NI-VISA + LV run time directory, such as _visa.llb etc.
    Do I need to copy these additional library functions too? Will Run Time Engine read these library functions?

Maybe you are looking for