NF WF1973 User manual

MULTIFUNCTION GENERATOR
WF1973/WF1974
Instruction Manual
(Remote Control)
NF Corporation

MULTIFUNCTION GENERATOR
WF1973/WF1974
Instruction Manual
(Remote Control)
DA00016811-001

I
WF1973/WF1974
Introduction
This manual explains the WF1973/WF1974 GPIB and USB interfaces. For operations from the
panel, refer to the WF1973/WF1974 Instruction Manual.
The GPIB and USB interfaces of the WF1973/WF1974 feature a large array of functions, which
allow control of almost all front panel operations. Moreover, the setting values can be read from
outside the equipment.
●The chapter organization of the WF1973/WF1974 Instruction Manual (Remote Control) is
as follows.
1. PREPARATIONS BEFORE USE
Describes the interface settings and GPIB address settings.
2. COMMAND EXPLANATION
Outlines the commands, lists the commands, and describes the individual commands.
3. STATUS SYSTEM
Describes status reporting, including the status byte and standard event status register.
4. ERROR MESSAGES
Describes the error numbers and the error contents.
5. SPECIFICATIONS
Describes the specifications of the external control interfaces.
6. COMMAND TREE
Commands are shown in the tree structure.

II MULTIFUNCTION GENERATOR
Contents
Introduction .......................................................................................................I
Contents...........................................................................................................II
1. PREPARATIONS BEFORE USE..................................................................1
1.1 Outline of WF1973/WF1974 GPIB/USB Interface ............................................. 1
1.2 USB Preparations .............................................................................................. 1
1.3 GPIB Preparations............................................................................................. 1
1.4 Selecting the Interface ....................................................................................... 1
1.5 GPIB Address Setting........................................................................................ 3
1.6 USB ID............................................................................................................... 4
1.7 Releasing Remote Status .................................................................................. 4
1.8 Cautions............................................................................................................. 5
2. EXPLANATION OF COMMANDS.................................................................6
2.1 Outline of Commands ........................................................................................ 6
2.2 Command List.................................................................................................. 18
2.3 Description of Individual Commands ............................................................... 27
2.4 Sequence I/O Data Specifications ................................................................. 139
2.5 Trigger/Oscillation Status Control .................................................................. 142
2.6 System Unit ................................................................................................... 143
3. STATUS SYSTEM ....................................................................................144
3.1 Status Byte Register and Service Request Enable Register ......................... 144
3.2 Standard Event Status Register Group ......................................................... 145
3.3 Operation Status Register Group/Questionable Data Status
Register Group .............................................................................................. 146
3.4 Warning Event Register Group...................................................................... 154
3.5 Other.............................................................................................................. 156
4. ERROR MESSAGE ..................................................................................157
5. SPECIFICATIONS ....................................................................................160
5.1 Interface Functions ........................................................................................ 160
5.2 Response to Interface Messages .................................................................. 161
5.3 Multiline Interface Messages ......................................................................... 162
6. COMMAND TREE.....................................................................................163

1
WF1973/WF1974
1. PREPARATIONS BEFORE USE
1.1 Outline of WF1973/WF1974 GPIB/USB Interface
Almost all the functions of the WF1973/WF1974 can be remotely set via the GPIB or USB
interface. Moreover, by allowing measurement data and setting statuses to be transferred outside
the equipment, an automatic measuring system can be configured easily.
1.2 USB Preparations
The WF1973/WF1974 can be controlled by USB Test and Measurement Class (hereafter, USB-
TMC). Almost all panel operations can be controlled, and internal statuses, such as setting values
and errors, can be read out.
Install a USB-TMC class driver on the controlling computer, and connect it using a commercially
available USB cable. The installation file for this driver can be downloaded from the website of
National Instruments Corporation. The driver installation is described below.
1. Either search the VISA Run-time Engine page on the website of National Instruments
Corporation, or select “VISA driver downloads” from the following URL:http://www.ni.com/
support/visa/
2. Download VISA Run-time Engine from the VISA Run-time Engine page. User registration
is required at this time. Download Ver. 3.3 or a later version of VISA Run-time Engine.
3. The downloaded file is self-extracting. Extract and install the file.
4. Once the file has installed successfully, the USB-TMC class driver is installed.
For details, refer to the website of National Instruments Corporation.
1.3 GPIB Preparations
Install a GPIB controller board (card) in the controlling computer and connect it with a
commercially available GPIB cable. For details, refer to the user's manual of the GPIB controller
board (card) that is used.
1.4 Selecting the Interface
Either GPIB or USB can be used as the interface to be used. The WF1973/WF1974 cannot be
controlled from the interface that is not selected.
The selected interface is retained even after the power is switched off.
The USB interface is selected at shipping.

2MULTIFUNCTION GENERATOR
1. PREPARATIONS BEFORE USE
<1> From [MENU], select “4:Utility” and then press the [ENTER] key.
<2> Select “Remote” and then press the [ENTER] key.

3
WF1973/WF1974
1.5 GPIB Address Setting
<3> Select “Interface” and then press the [ENTER] key to display the screen for selecting the
interface.
CAUTION
When the computer recognizes the WF1973/WF1974, the computer may
operate erratically when the interface is switched from USB to GPIB or the USB
cable is disconnected.
1.5 GPIB Address Setting
The GPIB address can be set.
Set the GPIB address to a different value than the addresses of other devices connected with a
GPIB cable. The set value is backed up when the power is switched off.
“2” is set at shipping.
<1> Set “Interface” to [GPIB] by performing steps <1> to <3> in “1.4 Selecting the Interface”.

4MULTIFUNCTION GENERATOR
1. PREPARATIONS BEFORE USE
<2> Select “GPIB Address” and then press the [ENTER] key to display the screen for setting the
GPIB address.
1.6 USB ID
If multiple WF1973/WF1974 units are connected within a system with USB, the following
numbers are used to allow unit recognition by the application.
• Vendor number: 3402(0x0D4A)
• Product number: 13(0x0D)/WF1973, 14(0x0E)/WF1974
• Serial number: Product’s manufacturing number (serial number)
1.7 Releasing Remote Status
In the remote control remote status, the “USB” or “GPIB” icon is lit on the LCD, and “LOCAL” is
displayed on the [F5] software key. When the [F5] key is pressed in this status, the remote status
is released, and panel operation becomes possible. However, when “LOCAL” is not displayed (local
lockout status), panel operation is disabled. To enable panel operation, specify local control from
the remote control controller.

5
WF1973/WF1974
1.8 Cautions
1.8 Cautions
• USB and GPIB connectors are located on the rear panel.
• USB and GPIB are interfaces designed based on the assumption of use in a relatively favorable
environment. Use of these interfaces in unfavorable locations such as locations with power
supply fluctuations and noisy locations should be avoided whenever possible.
• Connect/disconnect the GPIB connector only after powering off all the units connected on the
bus.
• During GPIB use, power on all the units connected on the bus.
• The total cable length should be 2 m x (number of units) or 20 m, whichever is shortest.
• The length of each cable must be 4 m max.
• Set GPIB addresses after careful checking. If the same address is set within the same sequence,
the equipment may be damaged.

6MULTIFUNCTION GENERATOR
2. EXPLANATION OF COMMANDS
2.1 Outline of Commands
The commands of the WF1973/WF1974 comply with IEEE488.2 and SCPI (version 1999.0). SCPI
defines a communication method using between controllers and measuring devices. For general
information regarding SCPI, refer to the following document:
Standard Commands for Programmable Instruments (SCPI) Version 1999.0, available at http://
www.scpiconsortium.org/.
2.1.1 Notation
For convenience, the following notation system is used in this document.
< >: < > indicates something other than the item itself. In the case of
parameters and response data, the abbreviation of the type is
enclosed in < >.
[ ]: Options, which can be omitted, are indicated between [ ].
{abc|xyz}: Means that either “abc” or “xyz” can be used.
[abc|xyz]: Indicates that either “abc” or “xyz” can be used, but that both are
options, which may be omitted.
Uppercase, lowercase: Keywords in both uppercase and lowercase are the long form,
while keywords in uppercase only are the short form.
2.1.2 Commands
The program messages of the WF1973/WF1974 are configured of common commands and
subsystem commands.
The format of each type of command, the subsystem command tree, etc., are described
below.
2.1.2.1 Common commands
Common commands are commands that are used to control comprehensive functions of the
equipment.
Figure 2.1 shows the common command syntax.
Figure 2.1. Common Command Syntax
The keyword in Figure 2.1 consists of 3 alphabetic characters. Here, SP is a space character
(ASCII code 32).
ParameterKeyword SP
?

7
WF1973/WF1974
2.1 Outline of Commands
2.1.2.2 Subsystem commands
Subsystem commands are commands that are used to execute specific functions of the
equipment. Each such command consists of a root keyword, one or more lower-level
keywords, a parameter, and a suffix.
A sample command and query are shown below.
:OUTPut:STATe ON
:OUTPut:STATe?
OUTPut is the root-level keyword, linking a second level keyword, and ON is a parameter.
2.1.2.2.1 Command tree of subsystem command
(A) Command tree structure
In SCPI, a hierarchical structure resembling a file system is used for subsystem
commands.
This command structure is called a command tree.
Figure 2.2 shows an example of a command tree for subsystem commands.
Figure 2.2. Example of Command Tree for Subsystem Commands
In the command tree in Figure 2.2, the keywords nearest the top ([:SOURce], [:OUTPut],
and [:SYSTem]) are root level keywords, and to reach the keywords on the lower levels, a
specific path must be traveled. For example, the access path to [:OFFSet] is [:SOURce]-
[VOLTage]-[LEVel]-[IMMediate]-[OFFSet].
(B) Current path transition
The current path is the first level that is searched by the parser among the various levels
of the command tree when the user sends the next command. The parser determines the
current path according to the following rules.
(1) At power-on and reset
The current path is set to root.
(2) Message terminator
Upon reception of a message terminator, the current path is set to root.
(3) Colon (command separator)
When a colon is placed between two keywords, the colon moves the current path one
level down in the command tree.
root
[:SOURce]
[:OUTPut]
[:SYSTem]
:VOLTage
:FREQuency
:PHASe
[:STAte]
:ERRor
[:LEVel]
[:FIXed]
[:IMMediate] [:AMPLitude]
OFFSET

8MULTIFUNCTION GENERATOR
2. EXPLANATION OF COMMANDS
(4) Colon (root specifier)
When a colon is placed at the beginning of a command, the current path is set to root.
(5) Semicolon
Semicolons have no influence on the current path.
(6) Space
Spaces have no influence on the current path.
(7) Comma
Commas have no influence on the current path.
(8) IEEE488.2 common commands
Common commands have no influence on the current path.
Through appropriate use of semicolons, multiple commands can be sent efficiently.
For example, the following string
:SOURce:VOLTage:LEVel:IMMediate:AMPLitude 1.0; OFFSet 1.0
achieves the transmission of the following two commands:
:SOURce:VOLTage:LEVel:IMMediate:AMPLitude 1.0
:SOURce:VOLTage:LEVel:IMMediate:OFFSet 1.0
When an optional keyword is omitted, caution about the current path movement is
required.
For example, in the case of
:VOLTage 1.0
the current path is [:SOURce]. Therefore, if
:SOURce:VOLTage:LEVel:IMMediate:AMPLitude 1.0
:SOURce:FREQuency:FIXed 1000.0
are transmitted as one program message, as follows,
:SOURce:VOLTage:LEVel:IMMediate:AMPLitude 1.0; FREQuency:FIXed 1000.0,
this results in an error.
However,
:SOURce:VOLTage 1.0; FREQuency:FIXed 1000.0
does not result in an error.

9
WF1973/WF1974
2.1 Outline of Commands
2.1.2.2.2 Subsystem command syntax
Figure 2.3 shows the syntax of subsystem commands.
Figure 2.3. Subsystem Command Syntax
(A) Keyword
The keyword in Figure 2.3 is a string of up to 12 characters, starts with an alphabetic
character, and is comprised of uppercase and lowercase alphabetic characters, underscore
(_), and numeric characters.
The majority of the keywords listed in “2.2 Command List” consist of a mix of uppercase
and lowercase characters. Here, uppercase characters are used for the short form, and a
mix of uppercase and lowercase characters is used for the long form of keywords. For
convenience, keywords use uppercase and lowercase characters, but in the case of actual
commands, no distinction is made between uppercase and lowercase. Examples for the
“OUTPut” keyword are listed in Table 2.1.
Table 2.1. Keywords Accepted and Not Accepted by Equipment (for “OUTPut")
(B) Keyword separator
The colons (:) in Figure 2.3 are interpreted as keyword separators. These keyword
separators serve to separate an upper-level keyword from a lower-level keyword in the
command tree, as shown in Figure 2.2.
The colon (:) at the beginning of the subsystem command is interpreted as a root specifier.
This root specifier sets the current path to root.
(C) Keyword omission
The keywords enclosed in square brackets ([ ]) in the commands listed in “2.2 Command
List” can be omitted.
If omitted, the equipment analyzes that command as if that option keyword had been
received.
For example, in the case of
:OUTPut[:STATe]
Keyword Description
OUTPUT Can be use as long form.
OUTP Can be used as short form.
OuTpUt Not case sensitive. Can be used as long form.
oUtP Not case sensitive. Can be used as short form.
OUTPU Cannot be used because it corresponds to neither long form nor short form.
OUT Cannot be used because it corresponds to neither long form nor short form.
ParameterKeyword:
Suffix
SP
?
: ,

10 MULTIFUNCTION GENERATOR
2. EXPLANATION OF COMMANDS
either of the following two commands can be used.
:OUTPut:STATe
:OUTPut
(D) Channel specification
In the case of a two-channel unit, the channel can be specified for the majority of the
commands by using an omissible numeric keyword suffix.
For example, in the case of
:OUTPut[1|2]:STATe
Channel 1 and Channel 2 commands are as follows:
:OUTPut[1]:STATe
:OUTPut2:STATe
If no channel number is specified, [1] is considered to have been omitted, and the
command is interpreted as a command for Channel 1. For example, when the output of
Channel 1 is controlled to “On", either of the following commands can be used:
:OUTPut1:STATe ON
:OUTPut:STATe ON
(E) Parameters
The parameter types are as follows.
(1) Numeric parameter (<REAL>, <INT>)
The numeric parameter syntax is shown in Figure 2.4.
Figure 2.4. Numeric Parameter (<REAL>, <INT>) Syntax
IndexMantissa SP

11
WF1973/WF1974
2.1 Outline of Commands
The syntaxes of the mantissa and index of Figure 2.4 are shown in Figures 2.5 and 2.6.
Figure 2.5. Mantissa Syntax
Figure 2.6. Index Syntax
(2) Discrete parameter (<DISC>)
The discrete parameter syntax is shown in Figure 2.7.
Figure 2.7. Discrete Parameter (<DISC>) Syntax
Number
Number
Number
Number
.
.
NumberE/e
SP
Choice 2
Choice 1
Choice 3
Choice N

12 MULTIFUNCTION GENERATOR
2. EXPLANATION OF COMMANDS
(3) Truth value parameter (<BOL>)
The truth value parameter syntax is shown in Figure 2.8.
Figure 2.8. Truth Value Parameter (<BOL>) Syntax
The truth value parameter is interpreted as true for values other than 0, and as false for
“0”.
If a value that includes a fractional part is specified, this value is interpreted as the whole
number obtained by rounding off the fractional part. Therefore, for example, “0.4” is false,
and “0.5” is true.
(4) Character string parameter (<STR>)
The character string parameter syntax is shown in Figure 2.9.
Figure 2.9. Character String Parameter (<STR>) Syntax
ON
OFF
NUM
(character)
(character)
Character
other than
Character
other than

13
WF1973/WF1974
2.1 Outline of Commands
(5) Block parameter (<BLK>)
The block parameter syntax is shown in Figure 2.10.
Figure 2.10. Block Parameter (<BLK>) Syntax
NL is a line feed (ASCII code 10), and ^END is an EOI asserted at the last byte.
(F) Parameter separator
The parameter separator is used for commands that have two or more parameters, and
serves as a separator between parameters.
(G) Query parameter
The query parameter is specified after “?” of the query, and can be used for most queries
for commands with numeric parameters. For example, when “MINimum” or
“MAXimum” is specified, the settable minimum value or settable maximum value,
respectively, can be queried.
(H) Suffix
The suffix syntax is shown in Figure 2.11.
Figure 2.11. Suffix Syntax
In the WF1973/WF1974, the prefix of the unit and the unit attached to a parameter are
valid only for that command, and have no influence on other commands.
:SOURce1:VOLTage:AMPLitude:UNIT VRMS
Sets amplitude unit to Vrms
:SOURce1:VOLTage:LEVel:IMMediate:AMPLitude 2.0 Sets amplitude to 2.0 Vrms
:SOURce1:VOLTage:LEVel:IMMediate:AMPLitude 2.0VPP Sets amplitude to 2.0 Vp-p
2.1.2.2.3 Program message syntax
Two or more common commands and subsystem commands can be combined and
transmitted from the controller to the equipment as one program message.
The program message syntax is shown in Figure 2.12.
Number
other than 0
Byte
data
Byte
data
0 NL ^END
Number
Prefix
of unit
SP Unit

14 MULTIFUNCTION GENERATOR
2. EXPLANATION OF COMMANDS
Figure 2.12. Program Message Syntax
Commands are separated by a semicolon (;).
2.1.2.2.4 Response message syntax
A response message is send data from the equipment in response to a query.
(A) Response message syntax
The response message syntax is shown in Figure 2.13.
Figure 2.13. Response Message Syntax
Commas (,) and semicolons (;) are used as separators in response messages. When
multiple values are returned with one command, the data are separated with commas (,).
On the other hand, when there are several queries for one program message, the data for
each query are separated with semicolons (;).
(B) Response message data
The response message data types are as follows.
(1) Real number response data (<REAL>)
The real number response data syntax is shown in Figure 2.14.
Figure 2.14. Real Number Response Data (<REAL>) Syntax
Common
command
Subsystem
command
NL
;
NL
^END
^END
,
;
Response
data NL ^END
<NR2>
<NR3>

15
WF1973/WF1974
2.1 Outline of Commands
The NR2 real number response data syntax is shown in Figure 2.15.
Figure 2.15. NR2 Real Number Response Data (<NR2>) Syntax
The NR3 real number response data syntax is shown in Figure 2.16.
Figure 2.16. NR3 Real Number Response Data (<NR3>) Syntax
(2) Integer response data (<INT>)
The integer response data syntax is shown in Figure 2.17.
Figure 2.17. Integer Response Data (<INT>) Syntax
NumberNumber .
NumberNumber
E
.
Number
Number

16 MULTIFUNCTION GENERATOR
2. EXPLANATION OF COMMANDS
(3) Discrete response data (<DISC>)
The discrete response data syntax is shown in Figure 2.18.
Figure 2.18. Discrete Response Data (<DISC>) Syntax
(4) Numeric truth value response data (<NBOL>)
The numeric truth value response data syntax is shown in Figure 2.19.
Figure 2.19. Numeric Truth Value Response Data (<NBOL>) Syntax
(5) Character string response data (<STR>)
The character string response data syntax is shown in Figure 2.20.
Figure 2.20. Character String Response Data (<STR>) Syntax
(6) Determined length block response data (<DBLK>
The determined length block response data syntax is shown in Figure 2.21.
Figure 2.21. Determined Length Block Response Data (<DBLK>) Syntax
Choice 2
Choice 1
Choice 3
Choice N
1
0
(character)
Character
other than
Number
other than 0
Byte
data
Number