Where is VISA run time engine in new LV 7.1 from August?

Hello All
Can somebody help me locating run time engine to VISA in the new LV7.1 from August 2004?
Thanks in advance
Pawel

Hello Pawel
The Run-time engine is not related to the LabVIEW version you are using on your executable but the NI-VISA driver version you are using in LabVIEW on your executable. So if you are using the newest version of NI-VISA in LabVIEW 7.1 which is version 3.2 you would have to install VISA Run-time engine 3.2 on the target machine.
You can find all the VISA run-time engine version on the following site...
http://digital.ni.com/softlib.nsf/webcategories/85​256410006C055586256BAC002C51FA?opendocument&node=1​32070_US
Regards
Mohadjer

Similar Messages

  • VISA run-time Engineがインストールできず困っています.

    VISA run-time Engine　5.4　のインストールをこころみましたが、
    ”VISA Shared Components 64-Bit”のインストールに失敗しました。というポップアップ
    が表示され、最終的にインストールに失敗します。
    VISA run-time Engine　5.3　と　VISA run-time Engine　4.6.2　のインストールも試しましたが、
    インストールに失敗します。
    ウィルス対策ソフトを停止しても同様に失敗します。
    どのバージョンもドライバーパッケージのインストール（中のデジタル著名？）がうまくいかないようです。
    解決方法をご存知の方、ご回答のほどよろしくお願いします。
    PCスペックは以下の通りです。
    　　OS:　　　　　　Windows 7　64bit
    　　実装メモリ：　8.00GB
    　　空き容量：　　260G
    添付:
    VISA_RunTimeEngine_インストールエラー.png ‏236 KB

    返信が遅くなりました。
    申し訳ありません、表現が悪かったようです。結局解決できずじまいです。
    幸いXPパソコンを用意できたので、XPパソコンにインストールし対応しました。
    VISA run-time EngineはNF社の任意波形発生器を制御するために必要でした。
    類似の事例等ご存知でしたら、アドバイスいただけませんでしょうか。

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

  • Is it possible to choose the serial port if only the run time engine is installed

    I have an application, which communicates over the serial port. When I use the full version of Labview I can change the serial port without any problem from Com1 to Com2 (similar to the example “Hardeware input output -> serial -> Labview serial vi"). When I build an application and try to run this program on a computer where only the run time engine 6.1 is installed, it is not possible to choose the serial port. Since there is no “Measurement and Automation Explorer” available on the run time engine and no directory C:\VXIpnp is created, when the run time engine is installed, I do not see a way, how I can satisfy the computer with the information it needs for configuring
    the different ports. Any suggestions?

    Hi Daniel,
    Before LV6.1 there was LV5.1 In LV5.1 the way to Spedify a resource was to use a string control with correct VIsa Resource Class identifier. For eg. "GPIB0::11" or "ASRL1::INSTR". With Introduction of VISA Resource Name Control and linking with MAX, These names are Available from Pull Down List and Can be Aliased, meaning ASRL1 which is Serial Port 1 can be called COM1 and so on. However the old method still works with all 6.1 Controls. Only thing is you have to make sure you Dont Conflict the Class Names ie Use "GPIB::.." instead of "ASRL..." when addressing Serial Port VI's.
    To solve your Problem I would Build a Menu ring with COM1 to COM4 in the Pull Down List.
    Next, If I use the Traditonal Serial Port VI wich accepts the Integer as Seria
    l Port #. I just Wire the Menu Ring to this VI.(Remember COM1 is 0, COM2 is 1 for this VI)
    If I use VISA Config Serial Post. I build an Array Constant with Corresponding VISA Class Names So in our case a String Array Constant of 4 elements "ASRL1::INST" to "ASRL4::INST". I Use Index Array Function With the Index Wired to my Menu Ring. The Array Input Terminal Wired to the Array Constant. The Output of this Array will be correct Visa Class Name Based on slection of my Menu Ring. I can Wire this as Input to my VISA Config Serial Port Vi.
    I have attached a Small VI to Illustrate this.
    Drawback: You must Predefine what Ports you will Want to Use. Basically you define all the cases.
    I hope this Answers your Q!
    Good Luck
    Mache
    Good Luck!
    Mache
    Attachments:
    Serial_Port_Select.vi ‏36 KB

  • Problems bundling visa run time with installer

    I am trying to build an installer for an application that makes VISA read/writes through a serial port.  I have tried to create an installer for this application but I keep getting a cryptic error that then terminates LV.  I am experiencing the same problem as described in this thread:
    http://forums.ni.com/ni/board/message?board.id=170&message.id=228510&query.id=494979#M228510
    I am developing with LV8.2 on XP SP2.  I would like to bundle the VISA Run Time so that I can communicate via VISA R/Ws.  After reading the above mentioned thread it didn't seem like there was ever a real resolution to the problem.  I am bundling the VISA Run Time engine just fine with other projects and I have deleted and started over several times with the installer inside this project, but I keep getting the same error, see attached document. 
    So are there any ideas short of me having to reinstall LV or VISA? 
    Thanks in advance!
    Dave
    Attachments:
    LV Error.doc ‏32 KB

    Thanks for the reply.
    I would agree that the project is corrupted.  I think I proved to myself that this was the case when I created a new project and magically everything worked just fine.  The project was created under the exact same release of LV by the same PC so I am just trying to understand why the project was corrupted while trying to build the installer. 
    I guess I have my solution now I'm into the deep dark hole of trying to understand why the error occured.  I know once I go down this path there is no returning.......
    Thanks!

  • Can't install LabVIEW Run-Time Engine 6.1 on Windows Terminal Server

    With my system admin, we tried to install the LabVIEW Run-Time Engine 6.1 on our Windows Terminal Server NT4. And we get an error all the time:
    -install using the plugin
    -install using LVRTE.exe
    -install after rebooting the server
    But I remember that we could install the Run-Time Engine 6.0 on another Windows Terminal Server NT4.
    Is there any compatibility issues with the new Run-Time Engine 6.1 ??
    Thanks for your help
    Cyrille

    Cyrille,
    What is the error that you get when trying to install the run-time engine?
    Are you installing it from the LabVIEW CD, or did you download it from the web site?
    To further troubleshoot this problem, it would be best if you send us an email to [email protected] and send the above information.
    Also, try running the installer from the command prompt window, and use the following syntax:
    setup.exe/l*v
    This will save the error log to the file you specify. Send us also this file to help us troubleshoot.
    Thanks
    Zvezdana S.
    National Instruments

  • How to include the visa run-time into the installer?

    Dear All,
              I made an USB device whose driver is developed by "NI visa driver development wizard".
              In my program, the COM is also be used. When it is builded and creats the installer, I have checked the Serial Port Suport in Advanced settings in Installer which I thought the visa run-time engine is concluded. In fact, when it is installed, the COM can work correctly, but the USB device's driver can't be installed. To fix it, the visa run-time engine must be setupped again.
              I see that I can add it to "run executable after installation" but during the installaion of run-time engine, some pages will be displayed which need user to choose some option.
             Would you please give some suggestion that the process of installation is automatic. Certainly the part of visa run-time engine which the USB driver is needed can be integrated to the installer of vi(like COM) is best.
              Thank you!
    Hugo
    PS: I am using LabVIEW 7.1

    First, you can install a VISA Runtime Engine in the target PC, to verify it is VISA Run Time Engine issue.
    If so, you can add a VISA Run Time Engine in LabVIEW when creating an Installer. It is much easy in LabVIEW 8 and still possible in LabVIEW 7.1. Follow the link.
    http://digital.ni.com/public.nsf/allkb/E09BA0E2F31​D304F86256A640070058E?OpenDocument

  • Installing VISA run-time with distribution

    Is there a way to seamlessly (transparent to the end-user) integrate the VISA run-time engine installation into an installation of a Labview app created with App Builder?
    I am trying to avoid the user having to run two different install programs (the app install and the VISA install).
    I am doing some serial port communications, using the VISA VI's in my app. Also, does VISA need to be configured beforehand, or can I just load a customized 'visaconf.ini' file with the serial ports aliases?
    Thanks.

    Hi,
    There isn't a way to automatically include the VISA installer on the LabVIEW app installer. You can use some batch files to make the LabVIEW app installer execute other installers.
    The following knowledge base gives some suggestions and points some of the problems you might encounter when using the LabVIEW 6.1 App Builder.
    How Do I Distribute National Instruments Drivers with Applications Built in LabVIEW 6.1?
    Hope this helps
    DiegoF
    National Instruments.

  • LabVIEW 8.0 Run Time Engine

    Hi,
    I've a question about LabVIEW 8.0 run time engine.
    I installed "LabVIEW_8.0_Runtime_Engine" from the NI website, but NI software in Add/Remove Programs does not list LabVIEW 8.0 Runtime Engine. However, LV 7.0 and 7.1.1 run time engines are listed in there. 
    Did anyone notice this?
    I also have installed TestStand 3.5 on the same computer.
    When I run an executable created in LabVIEW 8.0, I get the error message:
    "VI version is too early to convert to the current LabVIEW version" 
    Comments/suggestions are appreciated.
    Thanks.

    CarlaU wrote:
    The first thing that I would check is to go into Measurement and Automation Explorer (MAX) and click on the Software Tab. I would then check to see which version of the LabVIEW RTE shows up (if any). In theory, if the RTE shows up in MAX, then it should show up in Add or Remove Programs under National Instruments Software (highlight this and click Change....this should pull up a list of all NI products on your computer).
    It's in MAX, but not Add/Remove Programs>NI
    CarlaU wrote:
    If it doesn't show up there, then there are two other things that can be done. The first one involves modifying the Windows Registry. There are a great KnowledgeBase article that discusses how to do this in order to remove the driver.
    Nope - there's nothing to do with the RTE there either.
    CarlaU wrote:
    The second idea is to use a utility we have that I cannot post on the forum. If you create a service request via email or phone then we would be able to help you get the older versions fully uninstalled. You can create a service request at www.ni.com/ask. I hope this helps!
    Thanks Carla - I'll try that avenue.
    Copyright © 2004-2015 Christopher G. Relf. Some Rights Reserved. This posting is licensed under a Creative Commons Attribution 2.5 License.

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

  • VISA Write differs between TS Development System and LV Run-Time Engine

    Hi all
    I made an application on LabVIEW to test BERs (Bit Error Rates), and I used VISA Write between two COM ports to exchange data.
    Everything works fine using just LabVIEW.
    Afterwards, I used TestStand to call my application (VI). The LabVIEW adapters from TestStand were set to Development System by default, and everything works OK!!
    Finally, I needed to disable the development system, and set the LabVIEW adapters from TestStand to LabVIEW Run-Time Engine and I notice that the speed of the data exchange between the two COM ports decreased dramatically.
    The only difference was the speed...because all the data (changed slowly in this case) arrived correctly on the other COM port too.
    The symptom was the same as decreasing the baud rate...but the baud rate and all the other configurations remained the same. The only difference was the change between Develpment System to Run-Time Engine to notice this decreased speed between the exchanged data using VISA Write.
    Any solutions for this?
    Thanks in advance
    Joao
    Solved!
    Go to Solution.

    Joao,
    you state that using the LV Developement System as execution platform for your LV code modules result in faster datatransfer between the COM ports than using the LV Run-Time Engine.
    So i am pondering: Does this refer to TS at all?
    Please check the following:
    Run you communication using a sole LV application in LV Developement System. This should be fast. Now build an executable of this application and run that one. Do you see the same behavior?
    If there is no difference in a sole LV approach, there have to be some settings in the TS approach making this slow. So please let us know:
    Are there different modules involved in that data transfer (which in fact points to the reply Christophe made)?
    What about loading/unloading options of the modules?
    How big is the hierarchy of the modules, e.g. is it necessary for the RTE to load stuff the Dev Env has already in memory due to loading a lvproj.......?
    Could you provide a simple example sequence+modules showing this behavior?
    What versions of LV and TS are you using?
    hope this helps,
    Norbert
    CEO: What exactly is stopping us from doing this?
    Expert: Geometry
    Marketing Manager: Just ignore it.

  • 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

  • Are LabVIEW VISA functions supported by LabVIEW Run Time Engine?

    I have an executable file that I created using LabVIEWS Application Builder. When I run the application on another computer that does not have LabVIEW installed, it crashes with a Windows message stateing the my application has generated erros and will be shut down by Windows. I have isolated the problem as having something to to with VISA Reasource Names.
    Does anyone know if there has been any issues regarding the use of VISA function in LabVIEW Run Time Engine? The version of LabVIEW that I have is 6.0.2. The version of Run Time Engine is 6.0 .
    Dan

    Yes there are issues with the RTE 6.0 and VISA. Use the RTE 6.0.2
    LabVIEW, C'est LabVIEW

  • Path where to install the run time engine (on Linux)

    I have a cluster of Linux computers where I would like to run compiled LABview (8.20 at the moment) applications build
    with the application builder.
    Therefore I would like to install the LABview run time engine on a NFS mount file system seen from each computer.  But
    the installation procedure of the run time engine does not propose to
    choise the installation directory, but force the installation
    in  /usr/local/lib.
    I try to workaround this problem and have copied the /usr/local/lib/LABview.8.2 directory to my NFS filesystem and
    made the 'necessary' links.
    Unfortunatly it doesn't run and  fails because  the
    liblvrt.so.8.2 library  can not access patched versions of the
    libOSMesa.so.4
    and libGL.so.1 librairies but uses the standard ones in /usr/X11R6/lib.
    Even by setting my LD_LIBRARY_PATH correctly to access the patched librairies versions it does not run because the
    liblvrt8.2 library seems to be  linked with the following
    'rpath'   (given by the command 'strings liblvrt.so.8.2 |
    grep patchlib')
    $ORIGIN/LabVIEW-8.2/patchlib:$ORIGIN/patchlib:/usr/X11R6/lib:/usr/lib:$ORIGIN:$ORIGIN/LabVIEW-8.2/linux:$ORIGIN/linux:$ORIGIN/resource
    which prevents to access the patched librairies versions if the $ORIGIN is not set. Therefore I tried to set $ORIGIN as an
    environment variable but it doesn't change anything.
    Therefore my question is: Did somebody have already had this type of problem,  what is $ORIGIN and how I can set it ?
    Thanks in advance.

    Sir,
    Please could tell me the distribution you use ?
    Cordially,
    Pierre R...
    Certified LabVIEW Developer

  • Where can I download Run-time engine 6.1 for Mac OS

    When trying to run an executable I receive a message "Could not load LabView Runtime Shared Library: err = -2804, "Labview 6.1 Runtime". I did not see Run-time engine 6.1 for Mac OS 9 available for download. I only saw version 6.0.2. Does anyone know where I can download version 6.1??

    Hi majo008,
    If you click on the 'Drivers and Updates' under 'Option 3' on the Technical Support page (www.ni.com/support), you can select 'All Software Versions' and choose 'LabVIEW >> Run-Time Engine'. This page will then have a link to the LabVIEW 6.1 Runtime Engine for Mac OS.
    Have fun!
    - Philip Courtois, Thinkbot Solutions

Maybe you are looking for