Agilent Technologies

Agilent 8613x VXIplug&play Instrument Driver Read Me

README.TXT
AG 8613X BitAlyzer Error Performance Analyzer
Universal Instrument Driver (UID)
Driver Revision A.00.00
April/2001

Revision History
- ---------------------------------------------------------------------------
A.00.00 April/2001 Initial Release.
- ---------------------------------------------------------------------------

Contents:

1 Introduction

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

3 Using the AG 8613X 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

6.0 Packing List

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

1. Introduction

The help file included with the AG 8613X Universal Instrument Driver contains
instrument and programming information. This readme file contains additional
information concerning the driver.

The AG 8613X 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 AG 8613X driver conforms to all portions of the VXIplug&play driver
standard which are applicable to conventional HP-IB and RS-232. Two elements 
of the standard do not apply to the AG 8613X since it is not a VXI 
instrument. First, there is no soft front panel, as the AG 8613X 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 GP-IB and VXI protocols. The driver can be used with any
GP-IB 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 Agilent 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::17" instead of "gpib0::17"

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 AG 8613X 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 Technologies for the compiled
driver
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 ag8613x.fp in 
your project. This file can be found in vxipnpwin95ag8613x
Do not include ag8613x.c in your project. You must also provide an include 
path for ag8613x.h. This is done by adding vxipnpwin95include to the 
include paths (CVI Project Option menu).

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

4.0 Known Defects

The ag8613x_ED_accum_Q and ag8613x_ED_accumPeriod_Q functions have known 
issues and they don't work correctly.

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

5.0 Online Information

The latest version of this driver and other AG drivers are available
on the Internet at

http://www.agilent.com/find/inst_drivers

The AG 8613X driver is located in a self-extracting archive file called
ag8613x.exe.

If you do not have internet access, the drivers can be obtained by contacting 
your country support organization. In the U.S., the phone number is 
800-452-4844. A list of contact information for other countries is available 
on the Agilent Technologies website at

http://www.agilent.com/find/assist

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

6.0 Packing List

The following files are included with the VXI Driver:

<LIST FILES HERE, and their install locations>

VxiPnPWinXXBin
ag8613x_32.dll

VxiPnPWinXXinclude
ag8613x.bas
ag8613x.h

VxiPnPWinXXlibmsc
ag8613x.lib
ag8613x_32.lib

VxiPnPWinXXlibc
ag8613x.lib
ag8613x_32.lib

VxiPnPWinXXAg8613X
ag8613x.c
ag8613x.h
ag8613x.bas
ag8613x.fp
ag8613x.hlp
ag8613x.rc
ag8613x.prj
ag8613x.dsw
AgVisaCommon.h
ag8613x.cfg
readme.txt
agLib.dll
agDriver.dll
agPass.dll

VxiPnPWinXXAg8613XagDriver
agDriver.c
agDriver.h
agDriver.def
agDriver.dsp

VxiPnPWinXXAg8613XagLib
agLib.c
agLib.h
agLib.def
agLib.dsp

VxiPnPWinXXAg8613XagMain
agMain.c
agMain.h
agMain.def
agMain.dsp
agLoadDriver.c
agLoadDriver.h
agLoadPass.c
agLoadPass.h
agLoadLib.c
agLoadLib.h

VxiPnPWinXXAg8613XagPass
agPass.c
agPass.h
agPass.def
agPass.dsp

VxiPnPWinXXAg8613XagUtil
agUtil.c
agUtil.h
agUtil.dsp

VxiPnPWinXXAg8613Xexamplesagvee
example8.vee
example10.vee
example12.vee

VxiPnPWinXXAg8613Xexamplesc
example1.c
example3.c
example5.c

VxiPnPWinXXAg8613Xexampleslabview
example7.vi
example9.vi
example11.vi

VxiPnPWinXXAg8613Xexamplesvbexample2
example2.frm
example2.frx
example2.vbp
example2.vbw

VxiPnPWinXXAg8613Xexamplesvbexample4
example4.frm
example4.frx
example4.vbp
example4.vbw

VxiPnPWinXXAg8613Xexamplesvbexample6
example6.frm
example6.frx
example6.vbp
example6.vbw

VxiPnPWinXXAg8613Xlabview
ag8613x.llb
ag8613x_00.mnu
ag8613x_01.mnu
ag8613x_02.mnu
ag8613x_03.mnu
ag8613x_04.mnu
ag8613x_05.mnu
ag8613x_06.mnu
ag8613x_07.mnu
ag8613x_08.mnu
ag8613x_09.mnu
ag8613x_10.mnu
ag8613x_11.mnu
ag8613x_12.mnu
ag8613x_13.mnu
ag8613x_14.mnu
ag8613x_15.mnu
ag8613x_16.mnu
ag8613x_17.mnu
ag8613x_18.mnu
ag8613x_19.mnu
ag8613x_20.mnu
ag8613x_21.mnu
ag8613x_22.mnu
ag8613x_23.mnu
ag8613x_24.mnu
ag8613x_25.mnu
ag8613x_26.mnu
ag8613x_27.mnu
ag8613x_28.mnu
ag8613x_29.mnu
dir.mnu

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

Caution: When using the VXIplug&play functions always consider how the
8613X configuration may change. It is possible that a subtle change in the
configuration can cause instrument errors in your program that are retained
in the 8613X status register. When developing programs be sure that for
each function used, each parameter's value is appropriate for all the
instrument's possible configurations.


LabWindows/CVI is a registered trademark of National Instruments.


© Agilent 2000-2006