Controlling the Agilent 34980A internal DMM using the IVI-C DMM Class Driver in cooperation with the Agilent 34980A IVI driver

Size: px

Start display at page:

Download "Controlling the Agilent 34980A internal DMM using the IVI-C DMM Class Driver in cooperation with the Agilent 34980A IVI driver"

Roxanne Booth
5 years ago
Views:

1 Controlling the Agilent 34980A internal DMM using the IVI-C DMM Class Driver in cooperation with the Agilent 34980A IVI driver Agilent Technologies, Inc. Alan Copeland Last revised June 23, 2009 Goal We want to use the 34980A s internal DMM to make measurements and control that DMM with an IVI-C driver. Problem The Agilent 34980A IVI driver implements the IVI-C Switch class, but does not implement the IVI-C DMM class. Solution Using NI s IVI-C to IVI-COM adapter we can bridge between the NI IVI-C DMM Class Driver and the Agilent 34980A IVI-COM driver that supports the IVI-COM DMM class (IIviDmm interface). Agilent Technologies, Inc. pg. 1

2 Contents How NI s IVI-C Class Drivers work... 3 Software to install... 4 Important installation considerations... 4 Configuring the Driver Session using the NI IVI Configuration Store tool... 5 Example code... 8 NI LabWindows/CVI 9.0 code... 9 Visual C win32 console code Agilent Technologies, Inc. pg. 2

How NI s IVI-C Class Drivers work The users program will link directly to the NI IVI-C Class Driver. In the Initialize call, the user will supply a Driver Session for the address.

3 How NI s IVI-C Class Drivers work The users program will link directly to the NI IVI-C Class Driver. In the Initialize call, the user will supply a Driver Session for the address. The IVI-C Class Driver will query the IVI Configuration Store to see what driver is associated with the Driver Session. If the IVI Configuration Store reports that the Driver Session is associated with an IVI-C driver that supports the IVI Class, the IVI-C Class Driver will broker calls to the specific driver. The specific driver will then broker the interaction with the instrument (see Figure 1). Figure 1 Figure 1 - IVI-C Class Driver talking to IVI-C Specific Driver User Program IVI-C DMM Class Driver IVI-C to IVI-COM adapter for IVI DMM Agilent 34980A IVI-COM Driver (supports IVI-COM IIviSwtch) Instrument Q: Which driver is assigned to Driver Session = dmm_session? IVI Configuration Store A: Agilent34980A IVI-COM Driver Key User Program NI IVI Compliance Package IVI Shared Components Agilent IVI Driver Instrument If the IVI Configuration Store reports that the Driver Session is associated with an IVI-COM driver that supports the IVI Class, the IVI-C Class Driver will use an IVI-C to IVI-COM adapter to broker calls to the specific driver. The specific driver will then broker the interaction with the instrument (see Figure 2). Figure 2 IVI-C Class Driver talking to IVI-COM specific driver through an IVI-C to IVI-COM adaptor Agilent Technologies, Inc. pg. 3

Software to install NI LabWindows/CVI 9.0 1, or Microsoft Visual C++ 2005 or later NI VISA 4.5 2 o Installs NI Measurement and Automation Explorer (NI-MAX). NI IVI Compliance Package 3.

4 Software to install NI LabWindows/CVI 9.0 1, or Microsoft Visual C or later NI VISA o Installs NI Measurement and Automation Explorer (NI-MAX). NI IVI Compliance Package Agilent 34980A IVI instrument driver version Important installation considerations 1. Install the NI IVI Compliance Package after NI-MAX has been installed on the system (the NI IVI Configuration Store Tool won t be installed by the IVI Compliance package if NI-MAX isn t already on the system) 2. When installing the NI IVI Compliance Package choose the option to install the IVI-COM Adapters, which are not selected by default. 1 Download from 2 Download from 3 Download from &id= Agilent Technologies, Inc. pg. 4

Configuring the Driver Session using the NI IVI Configuration Store tool 1) Create a new Driver Session by right-clicking the Driver Session node in NI-MAX (under My System IVI Drivers) 2) Select the

5 Configuring the Driver Session using the NI IVI Configuration Store tool 1) Create a new Driver Session by right-clicking the Driver Session node in NI-MAX (under My System IVI Drivers) 2) Select the General tab for the Driver Session. In this tab you can set any initialization options that you need for the driver. 5 5 Note, adding the entry Trace=true in the Driver Setup field is completely optional. This option enables the Agilent 34980A IVI driver s internal tracing option, which outputs driver trace information to an XML file in the directory where the main program executable is located. This can be useful for debugging purposes. Agilent Technologies, Inc. pg. 5

6 3) Next, select the Hardware tab for the Driver Session. In this example, give the Resource Descriptor a value of dmm, which is a VISA alias. This enables us to reassign the VISA alias (in NI- MAX or Agilent Connection Expert) to a different instrument without having to change any program code, or the IVI Configuration Store information. 6 6 Don t forget to setup the VISA alias (in NI-MAX or Agilent Connection Expert) for your 34980A after you have finished configuring the Driver Session. Agilent Technologies, Inc. pg. 6

7 4) Finally, select the Software tab for the Driver Session. Choose Ag34980a from the Software Module dropdown box. 5) Click Save IVI Configuration. Agilent Technologies, Inc. pg. 7

8 Example code On the next couple of pages, you will find some simple example code that shows how to use the NI IVI DMM Class driver in LabWindows/CVI and in Microsoft Visual C++. To use the code, you will first need to setup an example project. For an example on how to setup the C++ compiler and linker options, see the IVI Getting Started Guide for the environment that you are interested in using (you can download all IVI Getting Started Guide s at the IVI Foundation website, Once the project is setup, simply copy the code into a.c file, compile the program, then run it. Agilent Technologies, Inc. pg. 8

9 NI LabWindows/CVI 9.0 code #include <ansi_c.h> #include "ividmm.h" void main() { ViChar errmsg[1000]; ViInt32 err; ViReal64 reading = 0; ViSession dmm = 0; ViStatus dmm_init_err = 0; IviDmm_init ("driver_session_dmm", VI_TRUE, VI_FALSE, &dmm); IviDmm_ConfigureMeasurement (dmm, IVIDMM_VAL_2_WIRE_RES, 10000, 0.003); IviDmm_error_query (dmm, &err, errmsg); printf("%d %s", err, errmsg); IviDmm_Read (dmm, 5000, &reading); IviDmm_error_query (dmm, &err, errmsg); printf("%d %s", err, errmsg); IviDmm_close (dmm); printf("%f", reading); return; } Agilent Technologies, Inc. pg. 9

10 Visual C win32 console code #include "stdafx.h" #include "ividmm.h" int _tmain(int argc, _TCHAR* argv[]) { ViChar errmsg[1000]; ViInt32 err; ViReal64 reading = 0; ViSession dmm = 0; ViStatus dmm_init_err = 0; IviDmm_init ("driver_session_dmm", VI_TRUE, VI_FALSE, &dmm); IviDmm_ConfigureMeasurement (dmm, IVIDMM_VAL_2_WIRE_RES, 10000, 0.003); IviDmm_error_query (dmm, &err, errmsg); printf("%d %s", err, errmsg); IviDmm_Read (dmm, 5000, &reading); IviDmm_error_query (dmm, &err, errmsg); printf("%d %s", err, errmsg); IviDmm_close (dmm); printf("%f", reading); return 0; } Agilent Technologies, Inc. pg. 10

Table of Contents. Pickering Instruments IVI Driver Help... 1 Contents... 1 Getting Started... 3 Introduction... 3 Essential Functions... 4 LXI...

Table of Contents. Pickering Instruments IVI Driver Help... 1 Contents... 1 Getting Started... 3 Introduction... 3 Essential Functions... 4 LXI... Table of Contents Pickering Instruments IVI Driver Help... 1 Contents... 1 Getting Started... 3 Introduction... 3 Essential Functions... 4 LXI... 5 LXISpecific... 5 PXI and PCI... 5 PXISpecific... 5 GPIB...