Agilent Technologies

Agilent 34970A Data Acquisition/Switch Unit VXIplug&play Instrument Driver Read Me

Agilent 34970A Data Acquisition/Switch Unit
Universal Instrument Driver (UID)
Driver Revision A.00.03
May 2002

Revision History
- ---------------------------------------------------------------------------
A.00.00 August 1997 Initial Release.
A.00.01 May 1999 Second Release.
+Channel error verification by slot 101 to 150, 201 to 250, 301 to 350.
+Function hp34970a_readArray fixed to read more than 1500 points with 
time and channel stamp.
+Parameters of hp34970a_readArray in Example 5 and 6 on help file were
+Description of how to create a command button was corrected.
A.00.02 April 2002 Third Release.
+Corrected several errors in constant values in .bas, .h, and .fp files
+Several functions used wrong-named but identical constants (no user effect)
+Removed invalid bypass in hp34970a_channelDelay
+Fixed numerous errors in help file parameter descriptions
+Agilent rebranding
A.00.03 May 2002 Fourth Release.
+hp34970a.h file referenced non-existent _cmdxxxArr_Q calls
- ---------------------------------------------------------------------------


1 Introduction

2 VTL/VISA Specific Information
2.1 Instrument Addresses
2.2 Language Specific Features

3 Using the 34970A UID in Application Development Environments
3.1 Microsoft Visual C/C++
3.2 Microsoft Visual Basic
3.3 LabWindows/CVI

4.0 Known Defects

5.0 Online Information

- ---------------------------------------------------------------------------

1. Introduction

The help file included with the Agilent 34970A Universal Instrument Driver
contains instrument and programming information. This readme file contains
additional information concerning the driver.

The 34970A Windows 95 and Windows NT drivers are actually a single 32-bit
driver. All of directory paths which follow assume Windows 95. For Windows
NT, change references from win95 to winnt. 

This 34970A driver conforms to all portions of the VXIplug&play driver
standard which are applicable to conventional GPIB and RS-232. Two
elements of the standard do not apply to the 34970A since it is not a
VXI instrument. First, there is no soft front panel, as the 34970A
can be controlled from it's hardware front panel. Second, there is no
knowledge base file, which is primarily a description of a VXI board.

This driver features:

1. Conformance with the VXIplug&play standard. The only exceptions are that
it does not have a soft front panel or a knowledge base file.

2. It is built on top of, and uses the services provided by VISA. VISA
supports GPIB and VXI protocols. The driver can be used with any
GPIB card for which the manufacturer has provided a VISA DLL.

3. It includes a "Function Panel" (.fp) file which allows it to be used
with visual programming environments such as Agilent VEE, LabWindows,
and LabVIEW.

4. It includes a comprehensive on-line help file which complements the
instrument manual. The help file presents application programming
examples, a cross-reference between instrument commands and driver
functions, and detailed documentation of each function, with examples.

5. Source is included so that the driver can be modified if desired. The
source conforms to VXI Plug & Play standards. Modifications should only
be done by people who are familiar with the VXIplug&play standard.

6. It includes a Visual Basic include file (.bas) which contains the function
calls in Visual Basic syntax, so that driver functions can be called from
Visual Basic. If you use Visual Basic with this driver, you should be
familiar with C/C++ function declarations. In particular, care must be
taken when working with C/C++ pointers.

- ---------------------------------------------------------------------------

2. VISA Specific Information

The following topics refer to instances when the driver is used with
different versions of VISA.

2.1 Instrument Addresses

When using VXIplug&play instrument drivers, instrument addresses must
be all uppercase letters. Implementation of the addressing scheme is
vendor specific and some vendors support mixed cases. However, for
maximum portability, the instrument address should use uppercase
characters only.

For example: use "GPIB0::20" instead of "gpib0::20"

2.2 Language Specific Features

Language Specific features are not supported with this driver.

- --------------------------------------------------------------------------

3. Application Development Environments

For general instructions on using the driver with Agilent VEE,
Microsoft Visual C++, Borland C++, Microsoft Visual Basic,
LabVIEW, and LabWindows/CVI, see the online help file.

Additional notes:

3.1 Microsoft Visual C++ 4.0 (& higher) and Borland C++ 4.5 (& higher)

A.) The driver uses Pascal calling conventions.
B.) Do not build the driver in the directory in which it was installed.

3.2 Microsoft Visual Basic 4.0 (& higher)

Refer to the Microsoft Visual BASIC manual for additional
information on calling DLLs.

3.3 LabWindows CVI/(R) 4.0 (& higher)

The 34970A driver is supplied as both a source code file and as a
dynamic link library file (dll). There are several advantages to
using the dll form of the driver. These include: 

1. Transportability across different computer platforms
2. A higher level of support from Agilent for the compiled
3. Faster load time for your project

LabWindows/CVI (R) by default will attempt to load the source version
of the instrument driver. To load the dll you must include the file
hp34970a.fp in your project. This file can be found in vxipnpwin95hp34970a
Do not include hp34970a.c in your project. You must also provide an
include path for hp34970a.h. This is done by adding vxipnpwin95include
to the include paths (CVI Project Option menu).

- ---------------------------------------------------------------------------

4.0 Known Defects

There are no known defects in the 34970A driver.

- ---------------------------------------------------------------------------

5.0 Online Information

The latest version of this driver and other Agilent drivers are available
on the Internet.


- ---------------------------------------------------------------------------

LabVIEW and LabWindows/CVI are registered trademarks of National Instruments.

© Agilent 2000-2006