Ivi driver

Important Resources:IVI Foundation's IVI Getting Started GuideMagna-Power Electronics MagnaDC IVI Programming Example Projects (C# and Visual Basic)Magna-Power Electronics MagnaLOAD IVI Programming Example Projects (C# and C)Prerequisites:Development environment such as Visual Studio Express 2008IVI Foundation Shared ComponentsVISA-COM Global Resource Manager (choose only one)National Instruments NI-VISA: Accept all defaults during installation, orAgilent IO Libraries Suite: Install as the primary VISA and accept all defaultsMagna-Power Electronics (MPE) IVI Driver. See Support Downloads. Note: The MPE-IVI Driver will fail to install if the IVI Foundation Shared Components are not installed first. The MPE-IVI Driver will give a warning, Figure 1, if a VISA-COM Global Resource Manager is not installed. The VISA-COM can be installed before or after the MPE-IVI driver. Figure 1. MPE-IVI Driver error if IVI Foundation Components are not installed. Using the IVI DriverReference the IVI Drivers Before you can utilize the IVI Driver, you must add a reference to it. In Solution Explorer, right click on your Visual Studio project and click Add Reference… Select the COM tab (Figure 2) and then select the IVI MPEIVI 1.5 Type Library and click OK. Note: This will automatically add a reference to IviDCPwrLib and IviDriverLib (Figure 3). Figure 2. Solution Explorer's Add Reference window. Figure 3. Solution Explorer's reference list window. Ensure the target platform is 32-bit (x86)Since the IVI driver is a 32-bit COM driver, it can only be accessed from a 32-bit executable. By default, .NET programs will run in the native architecture of the operating system. However, a 64-bit program cannot access a 32-bit COM driver, so the target platform must be changed to force the program to run in 32-bit (x86) mode if your application will be used on a 64-bit version of Windows. Special Instructions for Visual Studio Express UsersBy default, Visual Studio Express hides the configuration options

All oscilloscopes have very similar fundamental capabilities for vertical and horizontal settings, there is a wide variety of trigger modes across oscilloscopes. The IVI Foundation specification for oscilloscopes includes extensions for different scope trigger modes, such as video triggers, runt trigger, width trigger, and so on. Through extensions, the IVI Foundation has created standard programming interfaces for features and capabilities that are not standard in every scope. Therefore, every scope that accepts video signals will then comply with the video signal extension functions and attributes of the IVI specification.Configuring Your SystemIn order to use IVI class drivers in your test programs, you must first configure your system so that class drivers can communicate with specific instrument drivers. This is done by using the Measurement & Automation Explorer (MAX). MAX is the NI standard configuration tool for all hardware and related driver software. The first thing you will configure is the logical name, which refers to the virtual instrument you want to use in your application. A virtual instrument is the combination of the physical instrument, the instrument driver, and option settings.By changing the virtual instrument that the logical name refers to, you can swap instruments without changing your program. This mechanism is triggered through the initialize functions in the class drivers. For example, when you initialize an instrument using a class driver, you do not pass the driver a standard VISA resource string, such as “GPIB::2::INSTR”. Instead, you pass it a logical name, such as “DMM1.” MAX contains information that associates “DMM1” with a particular digital multimeter, as well as information about the location of the instrument driver and the initial configuration of the driver. The screenshot above shows the IVI configuration section of MAX. The Logical Names folder contains any logical names that you define to identify the instrument you communicate to in your program. The Virtual Instruments folder contains information on every IVI-specific instrument driver currently installed in your system. This information includes the initial settings of the IVI attributes on the drivers, such as state-caching1 (do you want the driver to track all instrument settings in software for better performance), simulation2 (for developing test code when the instrument is not available), and so on. The Instrument Drivers folder contains information on where to find the specific driver for each instrument in the Virtual Instruments folder. The Devices folder contains information on the physical hardware address of the

DMM. The proper approach to this situation is to call Configure first, before Read, to configure the instrument exactly as it needs to be set up before any measurements are taken. Interchangeability checking asserts a warning whenever you make measurements that rely on the default settings of the instrument. Other Tools Included with IVI Class Drivers Simulation DriversIn addition to the interchangeable instrument drivers (class drivers and specific drivers), and configuration tools, the IVI Compliance Package includes some other utilities that will help you build your test system. Simulation drivers are “virtual instruments” that plug into a class and generate simulated data. For example, there are five simulation drivers that are included with the IVI Driver Library – the oscilloscope, DMM, arbitrary waveform/function generator, switch, and power supply simulation drivers. Each of these simulation drivers plugs into the generic class drivers and performs flexible data generation when the drivers are used in simulation mode. Simulation drivers pop up user interface panels so developers can interactively configure the data generated. For example, when you are using a DMM driver in simulation mode with a simulation driver enabled, a data panel will be displayed whenever the Measure function is called. From the panel, you can select a base measurement value and an offset for the value generated. For example, generate a value of 3.0 V within a range of ±0.05 V. You can also configure the driver to pop up the panel each time the function is called, or automatically generate the data within the specified range every time.DMM Simulation Driver – When you call the DMM_Measure function with the DMM Simulation Driver enabled, the driver displays the measurement panel above, from which you can enter values to be “acquired” either manually or automatically, based on a specified range. Simulation drivers are included with the IVI class drivers with source code. Therefore, you can develop very robust simulated data generation algorithms for your test systems and plug them into the simulation drivers. Because simulation drivers work with the class drivers, the code you develop can be reused without change when you swap specific instruments. ConclusionInterchangeability has long been a goal for test engineers. The IVI class drivers delivered in the IVI Compliance Package provide a standard architecture for delivering hardware-independent test systems. The architecture is built around standard programming interfaces defined by a consortium of experienced test developers, the IVI Foundation, and

Release Date Version Version Description 2020-10-09 2.2.2.0 Added model support for B2901B,B2901BL,B2902B,B2910BL,B2911B,B2912B,B2961B,B2962B. Release Date Version 2020-10-09 2.2.2.0 Version Description Added model support for B2901B,B2901BL,B2902B,B2910BL,B2911B,B2912B,B2961B,B2962B. Driver type: IVI-C (32-bit/64-bit), IVI-COM (32-bit/64-bit), MATLAB (32-bit only) IVI class support: IviDriver 1.0, IviDCPwr 3.0 How to Download Click the Download button. Select the appropriate executable file. Choose Run. How to Install Run the downloaded installer. Licensing Does Not Require a License Supporting Documentation Download IVI, MATLAB Version 2.2.2.0 for B29xx Precision Source Measure Unit for 32-bit Windows IVI, MATLAB Version 2.2.2.0 for B29xx Precision Source Measure Unit for 64-bit Windows Operating System Windows 8Windows 7Windows 10 Prerequisites Supported Instruments B2901A, B2902A, B2911A, B2912A, B2961A, B2962A, B2901B, B2901BL, B2902B, B2910BL, B2911B, B2912B, B2961B, B2962B. Related Links Driver type: IVI-C (32-bit/64-bit), IVI-COM (32-bit/64-bit), MATLAB (32-bit only) IVI class support: IviDriver 1.0, IviDCPwr 3.0 How to Download Click the Download button. Select the appropriate executable file. Choose Run. How to Install Run the downloaded installer. Licensing Does Not Require a License Supporting Documentation Driver type: IVI-C (32-bit/64-bit), IVI-COM (32-bit/64-bit), MATLAB (32-bit only) IVI class support: IviDriver 1.0, IviDCPwr 3.0 How to Download Click the Download button. Select the appropriate executable file. Choose Run. How to Install Run the downloaded installer. Licensing Does Not Require a License Supporting Documentation How to Download Click the Download button. Select the appropriate executable file. Choose Run. How to Install Run the downloaded installer. Licensing Does Not Require a License Supporting Documentation How to Download Click the Download button. Select the appropriate executable file. Choose Run. How to Install See Readme File Licensing Does Not Require a License Supporting Documentation Downloads Operating System Windows 7Windows VistaWindows XP Prerequisites Supported Instruments B2901A, B2902A, B2911A, B2912A Related Links How to Download Click the Download button. Select the appropriate executable file. Choose Run. How to Install See Readme File Licensing Does Not Require a License Supporting Documentation Downloads Operating System Windows 7Windows VistaWindows XP Prerequisites Supported Instruments B2901A, B2902A, B2911A, B2912A Related Links SHOW MORE

How to find your installed IVI-C drivers in MATLABWhether you received your IVI-C drivers from the manufacturer or through one of the search methods mentioned on the "IVI Instrument Drivers and MATLAB" page, you can find installed drivers and instrument resources on your computer by calling the "instrsupport" command at the MATLAB Command Window.In the "VISA" section, you should see your connected devices in the following format:Connecting using the constructor: visa('ni', 'USB0::0x1AB1::0x04CE::::INSTR'); VISA-USB Object Using NI Adaptor : VISA-USB-0-0x1AB1-0x04CE--0 Communication Address ManufacturerID: 0x1AB1 ModelCode: 0x04CE SerialNumber: Take note of the resource name from the second argument in the listed "visa" function. In this case, it is:USB0::0x1AB1::0x04CE::::INSTRIn the "MODULES" section, you should see a cell array of all the installed drivers. The driver for this would be named:Note: Make sure that you have the most up-to-date NI-VISA software installed on your computer. This can be done by uninstalling any current NI-VISA software and downloading the "Instrument Control Toolbox Support Package for National Instruments VISA and ICP Interfaces" using the MATLAB Add-On Explorer. Restarting your computer may be necessary.Connecting to your deviceThe simplest interface to use would be the “Quick-Control Oscilloscope” object which would use the vendor-provided “rgdg1kz” IVI-C driver:Note that in order to use the installed “rgdg1kz” IVI-C driver, you need to set the "Resource" and “Driver” properties of the object accordingly before calling the “connect” function:myScope = oscilloscope;myScope.Resource = 'USB0::0x1AB1::0x04CE::::INSTR';myScope.Driver = 'rgdg1kz';Please refer to the following documentation page for a usage example that uses the "Oscilloscope" object:Below is an example application that uses the "Oscilloscope" object that you may be interested in:Another approach would be to use the “ividev” function using the “IVIScope” object class, which would provide more functionality and also uses the “rgdg1kz” IVI-C driver. Please refer to the following documentation page for more information:

The Benefits of Instrument InterchangeabilityThe benefits of instrument interchangeability extend into a wide variety of application areas and industries. Test system developers in the military and aerospace industries, who must maintain test systems and code for many years, can easily reuse their test code on new equipment as instruments are improved or become obsolete. Manufacturers in competitive, high-volume industries, such as telecommunications and consumer electronics, can keep their production lines running when instruments malfunction or must be recalibrated. And large manufacturing companies of all kinds can more easily reuse and share test code between departments and facilities without being forced to use the same instrumentation hardware. IVI Driver Architecture OverviewInterchangeability using IVI drivers is achieved through generic instrument class drivers. A class driver is a set of functions and attributes for controlling an instrument within a specified class, such as an oscilloscope, digital multimeter (DMM), or function generator. The IVI Compliance Package has eight classes – oscilloscope, DMM, arbitrary waveform/function generator, switch, power supply, power meter, RF signal generator, and spectrum analyzer. Each one of these generic class drivers makes calls to specific instrument drivers to control the actual instruments. The specific instrument drivers contain the information for controlling a particular instrument model, including the command strings, parsing code, and valid ranges of each setting for that particular instrument. From your test program, you make calls to the class drivers, which in turn communicate through the specific drivers for your instruments. You can change the specific instrument drivers (and corresponding instruments) in your system underneath the class driver without affecting your test code.IVI Driver Architecture – the class driver contains generic functions for controlling a DMM. The specific drivers contain information for controlling a specific instrument, such as command strings, parsing code, and valid ranges for instrument settings. A Word on InterchangeabilityInstrument interchangeability has long been a goal of many engineers building test systems, particularly in the military and avionics industries. When discussing these possibilities, it is important to realize that software interchangeability of instruments through instrument drivers is still limited by the interchangeability of the hardware in question. For example, with IVI drivers you can develop test code that works with any DMM. However, the requirements of your test system are still the driving force behind which particular instruments you use. If your test system requirements are DMM measurements with 8½ digits of precision, that means you must always