Agilent IO Libraries Suite 15.0 LXI Class B Update

Table of Contents

What Is Agilent IO Libraries Suite?

System Requirements

Installing the Software

What's Changed?

Known Issues

Uninstalling the Software

License Grant

Agilent Open System Developer Community


What Is Agilent IO Libraries Suite?


Agilent IO Libraries Suite is a collection of libraries that give you the ability to use your instruments from a test and measurement program, and utilities that help you quickly and easily connect your instruments to your PC.

To quickly and easily establish communication between your instruments and your PC, follow these three steps:

1.  Install the IO Libraries Suite: Get all the software you need to connect via GPIB, USB, LAN, and other standard interfaces.

2.  Connect Your Instrument:  Connect cables & apply power.

3.  Run Agilent Connection Expert to Configure Your Connection: See your system graphically and send commands to your instruments.

If you received two CD-ROMs with your Agilent product, install the IO Libraries Suite first. Then browse the second CD to find instrument drivers, documentation, and other application software, depending on the product you have purchased.


Note on Version Numbering: Agilent IO Libraries Suite is an enhanced, improved successor to the Agilent IO Libraries product. Agilent IO Libraries versions began with A.01.00 and ended with M.01.01. Agilent IO Libraries Suite versions began with 14.0, which is a higher version than M.01.01 for purposes of determining compatibility with other software and hardware products.

System Requirements for Agilent IO Libraries Suite 15.0


The system requirements for Agilent IO Libraries Suite 15.0 are as follows:

Windows XP Service Pack 2 (or later)
Windows 2000 Professional, SP 4 (or later)
Windows Vista
(Business, Ultimate, Enterprise)1
Processor450MHz Pentium II or higher required
800MHz recommended
1Ghz 32-bit (x86)
128MB minimum
(256 MB or greater recommended)
512 MB minimum
(1GB recommended)
Disk Space2
  • 280 MB minimum, 1GB recommended
    for Microsoft .NET Framework 2.0
  • 65 MB for Agilent IO Libraries Suite
  • 280 MB minimum, 1GB recommended
    for Microsoft .NET Framework 2.03
  • 65 MB for Agilent IO Libraries Suite
VideoSuper VGA (800x600) 256 colors or moreSupport for DirectX 9 graphics with
128MB graphics memory recommended
(Super VGA graphics is supported)
BrowserMicrosoft Internet Explorer 5.01 or greaterMicrosoft Internet Explorer 7 or greater
1 Windows Vista 64-bit and Home Basic and Home Premium editions are not supported.
2 Note: because of the installation procedure, less memory may required for operation than is required for installation.
3 .NET Framework 3.0 Runtime Components are installed by default with Windows Vista. Therefore, you may not need this amount of disk space.

You may want the Adobe Reader, which will allow you to read Agilent IO Libraries Suite manuals in PDF format. It can be obtained at

Who is licensed to install IO Libraries Suite 15.0?


See the License Grant at the end of this file to determine whether you are licensed to install this software.


What if I need support for an older operating system?

It is generally best to use the current version of the Agilent IO Libraries Suite. This version will support the newest interfaces and operating systems, and will have the most advanced features. However, you may need to install an earlier version of the IO Libraries Suite to support an older interface or operating system.

Installing the Software


To install Agilent IO Libraries Suite 15.0 LXI Class B Update:

First, disconnect any USB instruments, USB/GPIB converters, and FireWire® (IEEE 1394)-VXI interfaces that are connected to your PC.

Shut down all other applications that are running on the PC.

      If you have the Automation-Ready CD in your CD-ROM drive:

1.      Click this link, which opens a Windows File Explorer for the CD.

2.      Browse to the Autorun folder and double-click to execute auto.exe.

        If you are downloading Agilent IO Libraries Suite from the Web:

1.     Go to

2.      Download the IO Libraries Suite self-extracting zip file (*.exe) to any location on your hard disk.

3.      Double-click the .exe file to extract all files and start the installation process.

After the installation is complete, re-connect any devices that you disconnected prior to installing.

For detailed discussion of installation options, refer to the Agilent IO Libraries Suite Connectivity Guide. You will need Adobe Reader (available at You can also find the Connectivity Guide at

What's Changed in Agilent IO Libraries Suite 15.0 LXI Class B Update


Agilent IO Libraries Suite 15.0 LXI Class B Update includes defect fixes and makes several significant improvements and additions:

  • Support for LXI 1.2 (changes from LXI 1.1) including: a new "stateless" flag, the "Retransmission" flag has been depricated,LXI Class A and B instruments are now required to handle "future time" LXI events (events that happen in the future)., instrument web pages now have an XML Identification Document, etc.

  • Support for IEEE 1588-2008 (changes from IEEE 1588-2002) including: a new Product Description field in the clock description; manufacturer identity is now a 3 hex digit OUI, Management messages to all clocks and ports change, clock ID’s now use the EUI-64 format, positions of Boolean flags in messages have changed, positions of fields in some Ptp messages have changed, etc.

The following IO Libraries Suite 15.0 defects are corrected in this LXI Class B Update release:

  • Setting Query Timeout to non-multiple of 10 can hang Interactive LXI.
  • Interactive LXI fails to find slow-responding clocks mixed with fast-responding clocks.
  • Interactive LXI does not resize properly on a Japanese PC.
  • Interactive LXI does not show clocks if any information is missing for any clock.
  • Interactive LXI does not display errors in clock replies.
  • LxiTcpEventServer running on one login blocks use on another login.
  • Sending an LXI event from Interactive LXI with ‘after send time’ checked can cause an error dialog.
  • Connection Expert fails to open on Vista Japanese PCs with Office 2007 installed.
  • Connection Expert fails after NkoServer exits after running continuously for just under 25 days.
  • Some programs can't see Agilent IO Libraries Suite 15.0 as later version.
  • Corrected the AgilentIOLibrariesService so that it doesn't log PowerStatusChange power events. Laptops generate this event very frequently and logging them floods the event log.
  • Corrected problem in NkoServer, IocAgentVxiFirewire and IORemoteServer where Process.WaitForExit() does not wait indefinitely. It returns after int.MaxValue milliseconds even if the referenced process has not exited.
  • Added the Agilent-specific attribute ‘VI_AGATTR_INTFC_SERIALNUMBER’ to VISA INTFC. viGetAttribute returns the serial number of a VISA interface. If the interface doesn’t have a serial number, an empty string is returned.

The following list of changes were made with IO Libraries Suite 15.0, and are carried through in this update.

  • LAN instrument discovery and configuration is now significantly easier and faster.
  • Support for LXI Class B instruments. This includes support for LXI events and IEEE 1588 Precision Time Protocol (PTP). Also included is a new Interactive LXI gui interface to test and experiment with both LAN/LXI events (to send and receive events) and the IEEE 1588 PTP.
  • IO Monitor has been added to the suite of utilities.
  • VISA Open Reports has been added to help diagnose IO problems.
  • VISA 4.0 Compliance
  • Microsoft Windows VISTA support
  • The option to Enable Agilent GPIB cards for 488 programs is disabled by default if another vendor’s NI-488.2–compatible library is also installed. This reduces the likelihood of error messages from the third-party software. (You can always enable this option and your 488 programs will work correctly, regardless of the presence of third-party software.)
  • Location of Agilent Connection Expert log changed: As part of the migration to Vista, we moved the location of the Ace.log file out of:
        C:\Program Files\Agilent\IO Libraries Suite
    to the standard Windows location for program data. In Windows XP it is:
        C:\Documents and Settings\All Users\Application Data\Agilent\Agilent IO Libraries
    and in Windows Vista it is:
        C:\ProgramData\Agilent\Agilent IO Libraries
  • Agilent IO Libraries Suite 15 uses the new IVI VISA COM Standard Components. They install both the IVI VISA COM files, and create the VXIplug&play directory structure if it doesn't already exist. The default base directory for the VXIpnp components in this installer is:
        C:\Program Files\IVI Foundation\VISA
    Note that if you already have a set of VXIpnp directories on your PC, the new installer will continue to use your current set of directories (probably either
        C:\Program Files\VISA
    and not create a new set in
        C:\Program Files\IVI Foundation\VISA.
  • The default board number for Agilent PCI-GPIB interfaces is now zero, to conform to hardcoded board numbers in many NI-488.2 programs.
  • The default board number for National Instruments PCI-GPIB cards in Agilent Connection Expert is now 0 (it was 21). This makes Connection Expert more compatible with the NI-MAX default value. However, one or more of the following situations may occur:
    1) An additional device appears in the VISA Open report at the board GPIB address specified in Agilent Connection Expert. The device is shown as configured in NI-MAX.
    2) Agilent Connection Expert shows a real device on the interface as 'OK' but Interactive IO returns a VI_ERROR_IO when doing a *IDN?
    3) NI-MAX reports an error on the real device when scanning for instruments.
    4) Agilent Connection Expert shows the real device in the error state.

Known Issues


  • IO Monitor: Agilent IO Monitor installed as part of Agilent T&M ToolKit will cease to function after IO Libraries Suite 15 is installed. IO Libraries installs a newer, revised version of IO Monitor.

  • Vista Power Management: Microsoft changed the Power Management behavior in Windows Vista. Vista does not send a QuerySuspend message to the service. Apparently there have been problems with people closing their laptop computers expecting them to sleep but with XP, if a program (such as IOLibraries) refused the query suspend, the machine would display a message and not sleep. Since the laptop had been closed, the user never saw the message - he just put his laptop back in the case where it either overheated or drained the battery. In Vista this won't happen because programs never get the option to refuse a QuerySuspend. When running the LAN server on a Vista machine, the machine must be configured to not enter sleep mode. If it does, the LAN server will cease to respond and any remote IO that is in progress will fail. On Windows XP and Windows 2000, the AgilentIOLibrariesService prevents transition to 'standby' mode.

  • Location of Agilent Connection Expert log changed: As part of the migration to Vista, we moved the location of the Ace.log file out of:
        C:\Program Files\Agilent\IO Libraries Suite
    to the standard Windows location for program data. In Windows XP it is:
        C:\Documents and Settings\All Users\Application Data\Agilent\Agilent IO Libraries
    and in Windows Vista it is:
        C:\ProgramData\Agilent\Agilent IO Libraries

  • Instruments disappear in Connection Expert: When you install IO Libraries Suite 15 and one or more of your LAN instruments no longer appear in the Connection Expert, it may be because those instruments have incorrect subnet masks. Refer to the instrument's documentation.

  • VISA Assistant help file does not work in Vista OS: WinHlp32.exe is required to display 32-bit Help files that have the ".hlp" file name extension. To view .hlp files on Windows Vista, you need to install the WinHlp32.exe. If you click on Help > Help Topics, an error message pops up stating the problem and providing the following link to install WinHlp32.exe:

  • Vista USBTMC Driver incompatibility: On Windows Vista (and only on Vista) there is an incompatibility between USBTMC drivers supplied by National Instruments and Agilent Technologies. If you have NI-VISA installed as the primary VISA and Agilent VISA installed as the secondary VISA, you may experience one of two problems depending on which driver is associated with the USBTMC instrument.

    1. If the National Instruments driver is associated with the USB device, the USB driver vendor field in Agilent Connection Expert Properties Pane will be blank.

      In this case, the Connection Expert shows the USBTMC device in the failed state and the device cannot be used by the Connection Expert or by a VISA program that was built to explicitly use Agilent VISA (linked with agvisa32.dll). It can be used by a normal VISA program (one linked with visa32.dll) and the device will appear in NI-MAX. The VISA Open Report will indicate that the device is managed by NI-MAX and is usable in a VISA program.

    2. If the Agilent USB driver is associated with the device, the USB driver vendor will be identified as Agilent Technologies.

      In this case, Connection Expert shows the USBTMC device in the connected state and the Connection Expert and Agilent’s Interactive IO program can communicate with it. It will not, however, be usable by a standard VISA program and it will not be visible in NI-MAX. The VISA Open Report will show that this device is managed by Agilent Connection Expert as unavailable to a VISA program.

    If you need to change the USBTMC driver associated with a device, you must do it for each device you wish to change. From the Windows device manager, right click on the device you wish to change and select ‘Update Driver Software…’. Choose ‘Browse my computer for driver software’ then choose ‘Let me pick from a list of device drivers on my computer’. From that list select the driver you desire and then click ‘Next’ to install the driver. You may be asked to reboot when you make this change.

    • If you choose the NI driver, your device will be visible in NI-MAX and will work with normal VISA programs. The device will appear as failed in Agilent Connection Expert.
    • If you choose the Agilent driver, your device will not be visible in NI-MAX and it will not work with a normal VISA program. The device will be visible and connected in Agilent Connection Expert.

    Note: on Windows XP, this is not an issue because the NI USBTMC driver is (for the most part) compatible with the Agilent driver.

  • LAN Discovery without DNS: The ‘Auto Find’ capability for LAN instruments may, under some conditions fail to find instruments that are present on the local subnet if there is no DNS server available. The problem can manifest as long search times or a search that returns few or no instrument. This problem can occur when you reconfigure you LAN topology without rebooting the PC or the router. If a DNS server was configured but is no longer available, Windows will still attempt to reach the configured DNS server and may take 30 seconds or more before giving up and deciding that it can’t resolve a hostname. The severity of this problem varies with different routers. Some routers cause long DNS delays and others do not. If you experience LAN discovery delays or problems due to DNS issues, here are some suggestions to work around the problem.
    1. Uncheck the ‘Lookup hostnames’ box so the Connection Expert will not attempt to do a DNS lookup.
    2. Reboot both the router and the PC after changing LAN topology to make sure the current DNS situation is reflected in the LAN setup of both the PC and the router.
    3. Manually configure your LAN instruments using IP addresses, not host names.
    Note: it is not necessary to configure a LAN instrument in the Connection Expert for a program to be able to communicate with it. If the IP address of the device is known, a program can talk to it even if it is not configured in the Connection Expert.

  • Vista Installation with UAC Disabled: If you experience problems installing Agilent IO Libraries on a system with Windows Vista OS, you may have User Account control (UAC) Enabled. Typically, you may get an error message stating that a directory name is invalid. UAC must be disabled prior to installing IO Libraries.

    To disable UAC:
    1. Log into your system with Administrator privileges.
    2. Left mouse click the Start button (lower right-hand corner).
    3. Click Control Panel > Administrative Tools > Local Security Policies
    4. Click Local Policies > Security Options
    5. Scroll down to the bottom of the Policy list. You may also need to increase the width of the Policy pane.
    6. Locate the policy, “User Account Control: Run all administrators in Admin Approval Mode”.
    7. If it is “Enabled”, you must change it to “Disabled”.
    8. Right mouse click on the UAC and select Properties. Select the “Disabled” radio button and click OK.
    9. Close out of all the windows.
    10. You must reboot your computer before the setting will take place.
    For additional information, refer to:

  • Windows Vista, PTP and LXI C samples may not run the first time from Visual Studio 2005. If you attempt to open the C sample projects for LXI and PTP by double clicking on the solution file in the Windows Explorer after starting the IO Libraries install from that same explorer, the projects will compile, but the resulting sample programs will not run from Visual Studio. The symptom is a dialog box saying that the PtpManagerC.dll (PTP sample) or LxiEventManagerC.dll (LXI sample) cannot be found. The error is caused by a Vista defect that fails to refresh the environment variables passed to programs started based on file associations.
    Workaround: Close all instances of Windows Explorer after completing installation of IO Libraries. Thereafter, the environment variables seen by Visual Studio reflect the additions made by the IO Libraries install and the C samples will find PtpManagerC.dll or LxiEventManagerC.dll and run successfully.

  • Configuring a remote USB1. If you configure a remote USB1 device, NI-VISA will find it and report it correctly if NI Passport for VISA is enabled. But but when you try to open the USB1 device, NI appears to ignore the board number on the USB interface and attempts to open it on their USB0 interface. This process fails. Agilent's VISA Open Report correctly shows the USB1 device and indicates that it is managed by Agilent Connection Expert and that the device is available to a VISA program. This device can only be accessed by VISA programs that use an Agilent Connection Expert configured alias to the USB1 device.

Uninstalling the Software


Use the Windows Control Panel ("Add or Remove Programs" in windows XP or "Programs and Features" in Windows Vista) to remove the Agilent IO Libraries Suite. Do not delete files directly.

Removing the IO Libraries Suite does not delete the standard VISA directory, standard VISA COM files, standard IVI (Interchangeable Virtual Instrument Foundation) files, and IVI Shared Components. There is no reliable way for the IO Libraries Suite uninstaller to be sure that no other installed product (whether from Agilent or another vendor) is using these files and directories.

License Grant


For every individual Agilent instrument, Agilent hardware I/O product (including Agilent GPIB cards and Agilent I/O converters), and development copy of Agilent T&M Toolkit or Agilent VEE Pro that you legally own or have a valid, legal license from Agilent to use, Agilent grants you one non-exclusive license of the Software at no charge pursuant to the terms of the License Agreement. The License Agreement is displayed when you install the software and is available in the IO Libraries Suite Online Help.  You may download one copy of the Software, and store or run that copy of the Software for internal use and purposes in accordance with this Agreement and the documentation provided with the Software.  Such documentation may include license terms provided by Agilent's third party suppliers, which will apply to the use of the Software and take precedence over these license terms.  In the absence of documentation specifying the applicable license, you may store or run one copy of the Software on one machine or instrument.  If the Software is otherwise licensed for concurrent or network use, you may not allow more than the maximum number of authorized users to access and use the Software concurrently.

Agilent Open System Developer Community

Thank you for your interest in Agilent IO Libraries Suite 15.0.  As you use IO Libraries Suite, we also invite you to join the Agilent System Developer community at for additional test & measurement connectivity resources and information free of charge.

Microsoft and Windows are U.S. registered trademarks of Microsoft Corporation.

FireWire is a registered trademark of Apple Computer, Inc.

Copyright © Agilent Technologies, Inc. 2004-2008