[an error occurred while processing this directive] PNA Series > PNA Support > IO Libraries

Agilent PNA Series: Updating the Agilent IO Libraries Suite



Never attempt to upgrade the IO Library Suite on any PNA unless specifically instructed to do so! This will break connectivity. The instructions below are only for upgrading 14.1 to 14.2. Do not attempt to upgrade to 15.x!




Agilent has updated the IO Libraries suite to version 14.2. This document describes how how properly perform this upgrade. This document is meant only for PNAs with a 1.1GHz CPU or faster! If you are not sure which you have, check this page.

Do NOT upgrade older PNAs! Attempting to perform this upgrade on a PNA with a 266 or 500MHz CPU will render the GPIB inoperable! This procedure is only for PNAs that currently have IO Libraries Suite 14.0 or 14.1. If you have the "M" version of IO Libraries (or earlier), do not attempt this procedure!



1. Question: What has changed and why would I want to update this?
Answer: The new version has several changes and bug-fixes as shown below. The new version also allows use of the new 82357B USB-to-GPIB adaptor as well as the new USB power sensors.

2. Question: Where can I obtain a copy of version 14.2?
Answer: You can download the latest version for free from this web site. Registration may be required.




Instructions for Upgrading to Version 14.2

  1. Close the PNA application
  2. Download and save the Agilent IO libraries Suite 14.2 to some convenient location on the PNA. Do not select "Run"; instead, just save it.
  3. Once saved, click on it to begin the installation. Part way through it should halt with a message that you must uninstall the current version first; this is expected. Make sure the box is checked that indicates it will save your configuration data. Exit the installation and ignore any warning about it being incomplete.
  4. Click on Start, Settings, Control Panel; then select Add/Remove Programs.
  5. Click on Agilent IO Libraries Suite. Click on Change/Remove. Completely remove the IO libraries.
  6. Re-launch the 14.2 installation program. This time it should continue until the end. When it gets to the final prompt where it has a checkbox for "Launch the Agilent Connection Expert when finished", uncheck that checkbox, then exit.
  7. Navigate to, and execute C:\Program Files\Agilent\IO Libraries Suite\bin\iocfg32.exe. Under the list of "Configured Interfaces", you will see that VISA interface GPIB2 has "n/a" as its SICL Name. This is the PNA's SICL-LAN interface, which is improperly set up. Click on that item and then click the 'Remove' button to remove it. Then, in the "Available Interface Types" listbox, click on the item that says "Internal Instrument" as its Interface Description. Click the 'Configure' button. In the "Internal Instrument Configuration" dialog that pops up, just click 'OK' (the default values are acceptable.) Then close the IO Config dialog box by clicking OK.
  8. You are done!

 

What's Changed in Agilent IO Libraries Suite 14.2

 

Agilent IO Libraries Suite 14.2 includes defect fixes and makes two changes to improve the compatibility of Agilent 488 with recent releases of third-party software:

  • 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.)
  • The default board number for Agilent GPIB interfaces is now zero, to conform to hardcoded board numbers in many NI-488.2 programs.

Issues Resolved in Revision 14.2

 

The following software issues existing in Agilent IO Libraries Suite 14.1 have been resolved in Agilent IO Libraries Suite 14.2. This version includes all fixes that were included in IO Libraries Suite 14.1 Patch 1 and Patch 2.

  1. A communication failure message was sometimes displayed when a USBTMC device was connected, if both Agilent and National Instruments I/O software were installed.
  2. In some cases when both Agilent and National Instruments I/O software were installed, a call to viReadSTB on a USBTMC device could fail.
  3. In some cases when both Agilent and National Instruments I/O software were installed, USBTMC device communication was disrupted after a viReadSTB call on a USBTMC device.
  4. In some cases, an attempt to send a standard USB control request could cause a call to viUsbControlIn to fail.
  5. In some cases when both Agilent and National Instruments I/O software were installed, interrupts relating to USBTMC devices are not delivered. This could cause failure of various operations on USBTMC devices.
  6. In some cases when both Agilent and National Instruments I/O software were installed, a Device Clear operation on a USBTMC device could cause a device communication failure.
  7. In some cases, a Device Clear operation on a non-Agilent USBTMC device could time out, leaving the device in an unknown state.
  8. Connection Expert was unable to find certain non-Agilent GPIB instruments on the LAN. These instruments were therefore not displayed in Connection Expert's Search for Instruments on the LAN dialog box.
  9. Fatal exception errors were displayed by Agilent Interactive IO in some cases.
  10. The viFindRsrc function did not support specification of global attributes. That support has been added.
  11. Agilent VEE programs are unable to access Agilent GPIB cards that are assigned a logical unit of 14, 15, 17, or 18. Connection Expert has been modified so that it no longer assigns those logical unit values.
  12. After the operating system resumed from the “Hibernate” state, 82350A/B PCI-GPIB cards were sometimes unable to communicate with attached instruments. 
  13. The END status bit was not set correctly on return from the Agilent 488 Receive and RcvRespMsg functions.
  14. Devices which do not support termination characters were shown in "failed" state in Agilent Connection Expert, although no failure existed.
  15. An unhandled exception error ("Cannot control AgilentGpib32RenamerService") was displayed every six seconds for users running IO Libraries Suite without Administrator privileges and with certain Option settings.
  16. Task guide information in Connection Expert was blank for some optionally-installed interfaces.
  17. In some cases involving remote GPIB interfaces, the SICL function igeterrno returned an error although no error had occurred.
  18. Some VXI-11.2 devices returned errors when accessed by Agilent Connection Expert or by VISA or SICL programs.
  19. The SICL function igetlulist returned logical units for interfaces that were in the ignored state (set in Connection Expert). With this fix, igetlulist will not return those interface's LUs.
  20. Performance was suboptimal when a program called the Agilent 488 ibwait function with a mask parameter of zero.

 

 


Last Modified: 10 Jan 2008 [an error occurred while processing this directive]