This section will help you diagnose and resolve GPIB and LAN interface problems. Before using this section, be sure you have carefully followed all the steps in the installation section. If you still experience problems communicating with or controlling instruments over the LAN or GPIB, follow the steps in the section that supports your interface type below. If the problem still persists, refer to the Connection Expert utility, installed with Keysight IO Libraries Suite. For information on using the Connection Expert utility and for further troubleshooting information, see the IO libraries online help and the PDF documentation accessed through the Start menu.
"Connecting Hardware..." continues to be displayed and does not change to "Ready" within a few minutes. There may be a problem with the VISA connections. Verify that the instruments are properly configured in the IO Libraries.
Ensure that the GPIB cable and all connectors are not damaged.
Verify that the GPIB cables are securely attached to the PC and the signal generator.
Verify that the instrument you are trying to communicate with is turned on.
Select
in the tree view of the software to view the system details. Verify that the GPIB address is the same as the GPIB address used by your instrument. Press the button to test the hardware connections.If you have multiple GPIB boards installed, verify which board is selected.
Verify that the instrument you are trying to communicate with is using the SCPI language. For example, the signal generator supports 8656B, 8657A/B languages as well as SCPI. Refer to the instrument's user guide for information on available languages and how to select the SCPI language.
Uninstall any Keysight IO Libraries.
Install NI Visa and verify the NI GPIB card is working.
Install Keysight IO Libraries version 15.1 or later.
The National Instruments GPIB card should now work. To verify the Keysight GPIB card is working, perform the following steps:
Open National Instrument's Measurement and Automation Explorer (MAX).
Navigate to
and make sure the NiVisaTulip.dll box is checked.Check all LAN cable connections and make sure you are connected to the LAN. The LAN connector you are using may not be active. Check the rear panel of the signal generator and spectrum analyzer for flashing green or yellow lights which indicate LAN activity. Do not use a cross-over LAN cable.
Select
in the tree view of the software to view the system details. Verify that the TCP/IP address is the same as the TCP/IP address used by your signal generator. Press the button to test the hardware connections.Select
in the tree view of the software to view the system details. Verify that the TCP/IP address is the same as the TCP/IP address used by your hardware. Press the button to test the hardware connections.From the computer, go to command then click .
, typeAt the C:\> prompt, type ping <IP address>, where <IP address> is the hardware's IP address or hostname.
If the hardware does not respond, contact your IP department.
Type exit in the command prompt window then press
The VI_ERROR_ALLOC error indicates that an attempt was made to connect to a TCP/IP address that is currently in use by another application.