Agilent 6000 Series Instrument Driver Readme

Agilent 6000 Series Instrument Driver Readme
To rate this driver, go to the driver download page on the Instrument Driver Network.

1. Overview
Instrument Driver Technology: Plug and Play (project-style)
Manufacturer: Agilent Technologies
Supported Language(s): LabVIEW
Supported Model(s):
DSO5012A, DSO5014A, DSO5032A, DSO5034A, DSO5052A, DSO5054A,
DSO6012A, MSO6012A, DSO6014A, MSO6014A, DSO6032A, MSO6032A, DSO6034A, MSO6034A,
DSO6052A, MSO6052A, DSO6054A, MSO6054A, DSO6102A, MSO6102A, DSO6104A, MSO6104A,
DSO6014L, DSO6054L, DSO6104L,
DSO7032A, MSO7032A, DSO7034A, MSO7034A, DSO7052A, MSO7052A, DSO7054A, MSO7054A,
DSO7104A, MSO7104A, DSO7012A, MSO7012A, DSO7014A, MSO7014A, DSO7032B, MSO7032B,
DSO7034B, MSO7034B, DSO7052B, MSO7052B, DSO7054B, MSO7054B, DSO7104B, MSO7104B,
DSO7012B, MSO7012B, DSO7014B, MSO7014B

Model(s) Tested: MSO6034A, DSO6014L, DSO5052A, MSO7104A, MSO7014A, MSO7034B
Interface(s): GPIB, Ethernet, USB
Firmware Revision Tested: 4.02.0078 (6000 Series), 4.01 (5000 Series), 05.29.0383 (7000 Series)

Certified: Yes
NI Supported: Yes
Source Code Available: Yes

Driver Revision: 3.3.1
Original Release Date: 09/2006
Current Revision Date: 04/2012

2. Required Software
Some software components need to be installed before using this instrument driver. The minimum versions of
these components are listed below, and can be downloaded from the Download Site.

VISA 3.0

Note: VISA has additional software requirements. For example, unless you are using a serial interface,
NI-VISA requires that NI-488.2 and/or NI-VXI be installed on your system. Check with VISA help for additional
support software and hardware requirements.

3. Installation Instructions
LabVIEW:
Instrument drivers should be installed as a subdirectory of the labview\instr.lib. For example, the HP34401A
instrument driver, which is included with LabVIEW, is installed in the following directory:

labview\instr.lib\hp34401a

Within this directory you can find the menu files and VI libraries that make up an instrument driver. The
menu files allow you to view the instrument driver VIs from the Functions palette. The VI libraries contain
the instrument driver VIs.

4. Using the Instrument Driver
LabVIEW:
To verify communication with your instrument and test a typical programmatic instrument operation, you should
first open the Getting Started or Example VIs the instrument driver. Look over each of the controls and set
them appropriately. Generally, with the exception of the address field, the defaults for most controls will
be sufficient for your first run. You will need to set the instrument resource name appropriately. After
running the VI, check to see that reasonable data was returned and an error was not reported in the error
cluster.

After you have verified basic communication with your instrument, you might want to customize instrument
control for your needs. If your application needs are similar to the Getting Started or Example VI, the
simplest means of creating a customized VI is to save a copy of the Getting Started or Example VI by
selecting Save As from the File menu. You can then modify this example to meet your specific needs.

For more details, reference the LabVIEW Help under Help » VI, Function, & How-To Help.

5. Known Issues
To report issues or provide feedback about this instrument driver, please send an email to instrument.drivers@ni.com.

1. When the GPIB interface was used to read waveforms, the oscilloscope would return invalid data points on occasion,
which appeared as spikes on the waveform graph. During testing, this problem only occured on one particular PC, but it
was a persistent issue. If you encounter this problem, a valid workaround would be to acquire your waveform using the
USB or Ethernet interfaces.

6. Revision History
The latest version of this and other LabVIEW and LabWindows/CVI instrument drivers can be downloaded at the
Instrument Driver Network.

REV 1.0, 17/02/06, LV 7.0
Created by: Pavel Petranek
Modified by: Martin Hruby
Release Revision
- ag6000a Abort.vi and ag6000a Acquisition Status.vi moved from Action/Status class to LowLevel class in Data class.
- Created Polymorphic VI Read.vi with ag6000a Read Single Waveform.vi, ag6000a Read Multiple Waveforms.vi, ag6000a Read Digital Waveforms.vi and ag6000a Read Waveform Measurement.vi.
- ag6000a Acquisition Status.vi - Percent Complete indicator changed to Boolean LED with name "Acquisition Complete?"
- In ag6000a Disable Front Panel.vi renamed control to Lock and have values of True and False.
- Moved ag6000a Configure Math Channel.vi, ag6000a Configure Math FFT.vi and ag6000a Configure Math Setting.vi from _ag6000.llb. to the ag6000.llb.
- Moved ag6000a Configure Measurement Delay.vi , ag6000a Configure Measurement Source.vi and ag6000a Configure Measurement Threshold.vi VIs from _ag6000.llb to the ag6000.llb.
- Created Polymorphic VI ag6000a Configure Measurement.vi with ag6000a Configure Measurement Delay.vi , ag6000a Configure Measurement Source.vi and ag6000a Configure Measurement Threshold.VI.
- Moved ag6000a Read Waveform Measurement.vi and ag6000a Fetch Waveform Measurement.vi from _ag6000.llb to the ag6000.llb.
- ag6000a Configure Trigger Source.vi - renamed values in Polymorphic VI selector
- ag6000a Configure Trigger.vi renamed to ag6000a Configure Trigger Holdoff.vi.
- In examples used Polymorphic VIs.
- ag6000a Read Digital Waveforms.vi - control "Digital Waveform Graph" connected to the connector pane.
- ag6000a Read Waveform Measurement.vi - control "Measurement Function (7: Frequency)" connected to the connector pane.
- ag6000a Read Waveform Measurement.vi - control "Measured Value" connected to the connector pane.

REV 1.1, 09/14/06, LV 7.0
Modified by: Jason Hobbs & Martin Hruby
-Changed default values and/or labels for Channel control in the following VIs:
Configure Channel
Configure TV Trigger Source
Configure Measurement Source
Read Digital Waveforms
Read Waveform Measurement
Fetch Digital Waveform.vi
-Removed Error Query from the following VIs:
Acquisition Status
Abort
-Updated Error Query to check instrument Status Byte before proceeding so that incoming timeout errors are preserved if there are no instrument errors.
-Removed the following VIs that were not used by or exposed in the driver:
Lock Device.vi
Lock Front Panel.vi
Configure Trigger.vi
Fetch Waveform.vi
-Added Read Single Digital Waveform.vi to Read.vi polymorphic VI
-Renamed Read Digital Waveforms.vi to Read Multiple Digital Waveform.vi and fixed for multiple waveforms. Existing applications with Read Digital Waveforms.vi
should be updated to call Read Single Digital Waveform.vi.

Revision 2.0, 09/2006
Original release for LabVIEW 8.0 created from ag6000 driver (v.1.1) in LV 7.0

Revision 2.1, 02/2007
Changed channel enum idexing in configure channel characteristics.vi
deleted unwanted \r character from pick-line inputs in the fetch waveform measurement.vi

Revision 3.0, 5/1/2007
Modified by: Vinny LaPenna
-Initialize: Changed the ID query string to work with 5000 models
-Created Fetch Min Max Waveform and Read Min Max Waveform, created Fetch Waveform Poly VI, updated Read VIs to use Fetch Waveform Poly VI
-Fetch Waveform Measurement, Read Waveform Measurement: Added Source 2 control to both VIs
-Configure Trigger VIs: Added :TRIG:MODE command to appropriate VIs, which switches the trigger mode without having to call Configure Trigger Holdoff
-Configure Timebase VIs: Removed unnecessary REF command from Configure Timebase, added window controls to Configure Timebase Mode
-Made Configure Measurement Source VI obsolete, made Configure Window Timebase VI obsolete
-Fetch Analog Waveform: Rewired scaling equation to comply with programming manual
-Configure Acquisition Type: Added HRES option; added case structure to block diagram to avoid “settings conflict” error when type is AVER
-Acquire Multiple Waveforms Example, Edge Triggered Acquisition Example: Rewired block diagram to reflect the correct use of Configure Trigger
and to comply with templates
-Acquire Waveform Example, Acquire Continuous Waveform Example: Changed default value of Probe Attenuation control to 1
-Acquisition Status: Changed Timeout default value to 10000

Revision 3.0.1, 12/20/2007
Modified by: Berk Ozdogan
-Configure CAN Trigger Source: Removed the "\r" (Carriage Return) character within the string constant which was causing the Trigger Source control to behave incorrectly
-Edge Triggered Acquisition Example: Removed "Ground" option from the "Vertical Coupling" control

Revision 3.1, 02/26/2008
Modified by Berk Ozdogan
- Added support for 7000 series scopes
- Removed the erronous "Ground" option from the Vertical Coupling control in Agilent 6000 Series Edge Triggered Acquisition VI.
- Corrected various spelling errors

Revision 3.1.1, 05/28/2008
Modified by Nathan Tacha
- Added ":WAV:UNS 1;" command to the defualt setup string to have the instrument return the data as unsigned.

Revision 3.2, 08/25/2009
Modified by Brandon Sun
- Added support for new models: DSO7012A, MSO7012A, DSO7014A, MSO7014A.
- The VI: Configure Math Channel is obsoleted due to the command change from Agilent's manual. The new VI is Configure Math Function.

Revision 3.3, 03/2010
Modified by Brandon Sun
- Added support for 7000 series B modules.

Revision 3.3.1, 04/2012
Modified by JP
-Addressed bug in Configure Edge Trigger Source. Trigger Level does not support Line as a Trigger Source, so compared Trigger Source control to Line Trigger Source constant,
if Line is selected Trigger Level command will not be executed.