- #IVI PRO RIPPER HOW TO#
- #IVI PRO RIPPER INSTALL#
- #IVI PRO RIPPER DRIVERS#
- #IVI PRO RIPPER DRIVER#
- #IVI PRO RIPPER SOFTWARE#
The block diagram should now appear similar to Figure 2. This is typically the first interface in the list.Ĭlick the OK button to return to the block diagram after you have selected the type library, object, and interface. For IVI-COM drivers, select the interface which defines the Initialize method. Select the interface with which you want to start.
#IVI PRO RIPPER DRIVERS#
IVI-COM drivers have one creatable object and multiple interfaces. Place a checkmark in the Show Creatable Objects Only check-box to display only objects that you can create.
#IVI PRO RIPPER DRIVER#
If you cannot find the driver in this list, use the Browse button to select the driver DLL in the IVI\Bin directory.Īfter you select the type library, the Objects list contains all the IVI-COM objects and interfaces associated with the driver. This list can be long, so you might need to browse for keywords that match the driver, such as the vendor name or "IVI". The Type Library list contains the type libraries for all the registered ActiveX servers on the system in alphabetical order. A dialog box appears, shown in Figure 1.įigure 1: Selecting a Type Library in ActiveX Class Browserįrom the Type Library pull-down menu, select the IVI-COM driver. Right-click the function and select Select ActiveX Class>Browse from the shortcut menu. Open the ActiveX palette and place the Automation Open function on the block diagram. Complete the following steps to create a simple LabVIEW IVI-COM application. Note: If you have already installed Agilent IO Libraries Suite version 14.1, you may have to uninstall/reinstall or repair all the Agilent components to use Agilent IO Libraries Suite version 14.0.īecause an IVI-COM driver is an ActiveX-enabled technology, use the LabVIEW ActiveX functions to access IVI-COM properties and methods in LabVIEW.
#IVI PRO RIPPER INSTALL#
NET Primary Interop Assembly, you need to install the Microsoft.
Install Agilent IVI-COM Driver for the 34401A DMM. Agilent IO Libraries Suite version 14.0 is not the most current version of the IO Libraries Suite, but later versions of the Agilent IO Libraries Suite are not compatible with NI GPIB interface cards. For compatibility with NI GPIB interface cards, install version 14.0 of the Agilent IO Libraries Suite. Install Agilent IO Libraries Suite, required by Agilent IVI-COM drivers. Install Agilent IVI-COM Components, required for older Agilent IVI-COM drivers. IVI Compliance Package, for the IVI Shared Components Install NI device drivers from either the NI Device Driver CD or Drivers and Updates on ni.com
#IVI PRO RIPPER SOFTWARE#
The installation steps described in this document are based on the software requirements for the Agilent 34401A IVI-COM driver.Ĭomplete the following steps to install the required software on your system: Refer to the instrument driver Readme file for detailed software requirements. Use these instructions as a guideline for using other IVI-COM drivers in LabVIEW.
#IVI PRO RIPPER HOW TO#
This document describes how to use Agilent's IVI-COM driver for the 34401A DMM in a simple LabVIEW application. In those cases, you can program the COM objects directly with LabVIEW’s ActiveX functions. In some cases, a driver with a simple LabVIEW interface is unavailable. You should consider all driver choices available, and choose the driver that best fits your needs. LabVIEW Plug and Play and IVI-C drivers with LabVIEW wrappers are available on the Instrument Driver Network. In general, a driver with a customized LabVIEW interface is easiest to use in LabVIEW.
For information on the differences between IVI-C and IVI-COM drivers, refer to the IVI Architecture document. The IVI Foundation defines two architectures for IVI drivers: IVI-C, which is based on ANSI C, and IVI-COM, which is based on Microsoft COM technology. IVI-COM is one of several instrument driver technologies that you can use with LabVIEW. Instrument drivers simplify instrument control and reduce test program development time by eliminating the need to learn the programming protocol for each instrument. Each routine corresponds to a programmatic operation such as configuring, reading from, writing to, and triggering the instrument. An instrument driver is a set of software routines that control a programmable instrument.
0 kommentar(er)
