GPIB Instrument
A GPIB instrument is any instrument connected to a GPIB interface, as listed here.
Also See:Add Instruments, Update Instruments, Add Interfaces and Update Interfaces
GPIB Instrument Properties
Property | Description |
---|---|
Test Station |
The Select Test Station(s) dropdown shows the connected test station. Currently, it is not functional and a placeholder for future releases. |
GPIB Interface ID | The interface ID of the GPIB bus on which this instrument resides: for example, GPIB0. |
Primary Address | The primary GPIB address of the instrument ranges from 0 to 30. This address, or a secondary address if applicable, is used by the bus controller to uniquely identify the instrument. It must match the instrument's actual GPIB address and should not conflict with any other instrument or interface on the bus. Note that address 21 is typically reserved for the GPIB bus controller interface. Actual GPIB Address - Most newer instruments will display their GPIB address during the instrument's power-on sequence. Older instruments have the GPIB address set by a DIP switch, usually located on the back panel of the instrument. |
Secondary Address | Some GPIB instruments have a secondary GPIB address. Typically, the secondary address helps to identify a plug-in module in a mainframe. The secondary address and primary address are used by the bus controller to address a particular module. The secondary GPIB address is an integer from 0 to 30, or (None). |
Auto-Identify This Instrument |
When this check box is selected, an *IDN? query is sent to the instrument periodically. When this check box is cleared, this instrument will be excluded from periodic identifications. ![]() When auto-identification is enabled for an instrument, the Discovery Service sends an identification query (*IDN?) to determine the instrument's identity when it is added. You may want to disable auto-identification on certain instruments, including:
On Keysight PCI GPIB interfaces and Keysight USB/GPIB interfaces, auto-identification will not be attempted on a GPIB instrument that already has an open session, in order to minimize disruption of shared instruments. This is not true on remote GPIB interfaces and 488.2 GPIB interfacesthat cannot keep track of open sessions. If you are programming GPIB instruments, it is a good idea to lock an instrument (for example, using VISA's viLock function) when you want to prevent the instrument from being interrupted by a *IDN? query. |
Verify Connection | When you click the Test Connection button, the system will attempt to connect to the specified instrument and then display the state of the connection. The state of the connection is typically Verified or Failed. If the connection fails, the failure details may also be displayed. |
Saving the Configuration | The Add or Save buttons get enabled if you change information in this view. |