YOKOGAWA TA720 User manual

Time Interval Analyzer
Communication Interface
IM 704510-17E
1st Edition

i
IM 704510-17E
Foreword
Thank you for purchasing the YOKOGAWA TA720 Time Interval Analyzer.
This Communication Interface User’s Manual describes the functions of the
communication interface and command communications. To ensure correct use, please
read this manual thoroughly before beginning operation.
After reading the manual, keep it in a convenient location for quick reference whenever a
question arises during operation of the software.
The following manual is also provided in addition to this manual. Read them along with
this manual.
Manual Title Manual No. Description
TA720 User’s Manual IM 704510-01E Explains all functions and procedures of the
TA720 excluding the command communication
functions.
Notes
•The contents of this manual are subject to change without prior notice as a result of
continuing improvements to the instrument’s performance and functions.
•Every effort has been made in the preparation of this manual to ensure the accuracy
of its contents. However, should you have any questions or find any errors, please
contact your nearest YOKOGAWA dealer as listed on the back cover of this manual.
•Copying or reproducing all or any part of the contents of this manual without the
permission of Yokogawa Electric Corporation is strictly prohibited.
•The TCP/IP software of this product and the document concerning the TCP/IP
software have been developed/created by YOKOGAWA based on the BSD
Networking Software, Release 1 that has been licensed from California University.
Trademarks
•Microsoft, MS-DOS, and Windows are either registered trademarks or trademarks of
Microsoft Corporation in the United States and/or other countries.
•Adobe, Acrobat, and PostScript are trademarks of Adobe Systems Incorporated.
•For purposes of this manual, the TM and ® symbols do not accompany their
respective trademark names or registered trademark names.
•Other company and product names are trademarks or registered trademarks of their
respective companies.
Revisions
1st Edition: September 2002
Disk No. HF16
1st Edition : September 2002 (YK)
All Rights Reserved, Copyright © 2002 Yokogawa Electric Corporation

ii IM 704510-17E
How to Use This Manual
Structure of the Manual
This User’s Manual consists of the following sections:
Chapter 1 GP-IB Communication Interface
Describes the setup procedures for using the GP-IB communication
interface.
Chapter 2 Ethernet Communication Interface (Option)
Describes the setup procedures for using the Ethernet communication
interface.
Chapter 3 Program Syntax and Programming
Describes the program syntax and points to note when creating the
programs.
Chapter 4 Commands
Describes all the commands one by one.
Chapter 5 Status Reports
Describes the status byte, various registers, queues, and other
information.
Chapter 6 Sample Programs
Introduces program examples made using Visual Basic.
Appendix
Describes reference material such as an ASCII character code table.
Index
Gives an index.
Conventions Used in This Manual
•Conventions
Type Symbol Meaning
Unit k 1000 Example: 100 kHz
K1024 Example: 128 KB (memory size)
Symbols Note Describes useful information.
•Symbols Used in the Syntax
The following table indicates symbols that are used in the syntax mainly in chapter 3.
These symbols are referred to as BNF (Backus-Naur Form) symbols. For a
description of the symbols used with the data (conditions and values that are written
following a space after the program header), see pages 3-5 and 3-6.
Symbol Meaning Example Entry Example
<> Defined value WINDow<x> <x>=1 to 16 WINDOW2
{} Select from values given in {} MODE {AUTO|MANual} MODE AUTO
|Exclusive OR MODE {AUTO|MANual} MODE AUTO
[] Can be omitted :MEASure[:MODE]
... Can be repeated

iii
IM 704510-17E
1
2
3
4
5
6
App
Index
Contents
Foreword ......................................................................................................................................... i
How to Use This Manual .................................................................................................................ii
Chapter 1 GP-IB Communication Interface
1.1 Names and Functions of the Parts Related to GP-IB Communications ........................ 1-1
1.2 Connecting the GP-IB Cable ......................................................................................... 1-2
1.3 GP-IB Communication Capabilities and Specifications ................................................. 1-3
1.4 Settings on the TA720 ................................................................................................... 1-5
1.5 Responses to Interface Messages ................................................................................ 1-6
Chapter 2 Ethernet Communication Interface (Option)
2.1 Names and Functions of the Parts Related to Ethernet Communications..................... 2-1
2.2 Ethernet Communications Functions and Specifications............................................... 2-2
2.3 Connection Using the Ethernet Communication Interface ............................................. 2-3
2.4 Setting the TA720 .......................................................................................................... 2-4
Chapter 3 Program Syntax and Programming
3.1 Messages ...................................................................................................................... 3-1
3.2 Commands .................................................................................................................... 3-3
3.3 Responses ..................................................................................................................... 3-4
3.4 Data ............................................................................................................................... 3-5
3.5 Synchronization with the Controller ............................................................................... 3-7
Chapter 4 Commands
4.1 List of Commands .......................................................................................................... 4-1
4.2 ASCale Group................................................................................................................ 4-8
4.3 CALCulation Group........................................................................................................ 4-9
4.4 COMMunicate Group ................................................................................................... 4-25
4.5 DISPlay Group ............................................................................................................. 4-27
4.6 FILE Group .................................................................................................................. 4-31
4.7 HCOPy Group.............................................................................................................. 4-34
4.8 HHIStogram<x> and THIStogram<x> Group............................................................... 4-36
4.9 IHIStogram Group........................................................................................................ 4-45
4.10 INPut Group .................................................................................................................4-52
4.11 MEASure Group .......................................................................................................... 4-55
4.12 MEMory Group ............................................................................................................ 4-57
4.13 RECall Group ............................................................................................................... 4-59
4.14 SAMPle Group ............................................................................................................. 4-60
4.15 SSTart Group ............................................................................................................... 4-64
4.16 STARt Group ............................................................................................................... 4-64
4.17 STATus Group ............................................................................................................. 4-65
4.18 STOP Group ................................................................................................................ 4-66
4.19 STORe Group .............................................................................................................. 4-66
4.20 SYSTem Group ............................................................................................................ 4-67
4.21 TVARiation<x> Group .................................................................................................. 4-69
4.22 UNIT Group ................................................................................................................. 4-71
4.23 Common Command Group .......................................................................................... 4-72

iv IM 704510-17E
Contents
Chapter 5 Status Report
5.1 Overview of the Status Report ....................................................................................... 5-1
5.2 Status Byte .................................................................................................................... 5-2
5.3 Standard Event Register................................................................................................ 5-3
5.4 Extended Event Register ............................................................................................... 5-4
5.5 Output Queue and Error Queue .................................................................................... 5-5
Chapter 6 Sample Programs
6.1 Before Programming...................................................................................................... 6-1
6.2 Sample Program Image ................................................................................................. 6-1
6.3 Initialization, Error, and Functions for Execution............................................................ 6-2
6.4 Setting Measurement Parameters or Querying the Settings (for GP-IB) ....................... 6-6
6.5 Querying the Measured Statistical Values of Period Measurement (for GP-IB) ............ 6-8
6.6 Querying the Measured Statistical Values of Period A & Period B Measurement
(for GP-IB) ................................................................................................................... 6-11
6.7 Querying the Measured Data of A-to-B Time Interval Measurement (for GP-IB)......... 6-14
6.8 Setting Measurement Parameters or Querying the Settings (for Ethernet) ................. 6-17
6.9 Querying the Measured Statistical Values of Pulse Width Measurement
(for Ethernet)................................................................................................................ 6-19
Appendix
Appendix 1 ASCII Character Codes ....................................................................................App-1
Appendix 2 Error Messages ................................................................................................App-2
Appendix 3 Overview of IEEE.488.2-1992 ..........................................................................App-4
Index

1-1
IM 704510-17E
GP-IB Communication Interface
1
1.1 Names and Functions of the Parts Related to GP-IB Communications
Chapter 1 GP-IB Communication Interface
1.1 Names and Functions of the Parts Related to GP-IB Communications
Front Panel
Remote
UTILITY key
Press this key to configure
communications.
LOCAL key (SHIFT+AUTO SCALE) key
Press this key to clear the remote mode
(controlled via communications) and enter the
local mode in which key operations are enabled.
Remote indication appears at the upper right corner of the screen
when in remote mode using communications.
POWER
ESC
CH A CH
sec/V/
MHz
LOCAL
INITIALIZE FILE
COPY MENU
SHIFT
EXT ARM/EXT GATE INHIBIT
50 1M 40Vpk 1M 40Vpk5V rms
B
MODE
ENTER
0
123
m
456
789n
SINGLE START/STOP
COPY
AUTO
SCALE
FUNCTION INPUT
MARKER UTILITY
SAMPLE
DISPLAY SCALE
R
E
S
E
T
S
E
L
S
C
T
Rear Panel
GP-IB connector
Connector used to connect the TA720 to
the controller (PC) using a GP-IB cable.
REFERENCE
GATE OUT
MONITOR
OUT
PROBE
POWER
ADJUST
ETHERNET
100-240V AC
250VA MAX
50/60Hz
FUSE 250V T 3.15A
GP-IB(IEEE488)
10BASE - T
TX
LINK
(TTL)
( 12V)(50 )
10MHz OUT
(1Vp-p)
10MHz REF IN
(1Vp-p)
1Vp-p
CH
B
CH
A
WARNING
Do not operate without reading
safety precautions in user s manual

1-2 IM 704510-17E
1.2 Connecting the GP-IB Cable
1.2 Connecting the GP-IB Cable
GP-IB Cable
The GP-IB connector used on this instrument is a 24-pin connector that conforms to the
IEEE St’d 488-1978. Use a GP-IB cable that conforms to this standard.
Connection Procedure
Connect the cable as shown below.
GP-IB connector
GP-IB cable
Precautions to Be Taken When Connecting Cables
•Firmly tighten the screws on the GP-IB cable connector.
•Multiple devices can be connected to a single GP-IB system. However, no more than
15 devices (including the controller) can be connected to a single system.
•When connecting multiple devices, each device must have its own unique address.
•Use a cable of length 2 m or less for connecting the devices.
•Make sure the total cable length does not exceed 20 m.
• When communicating, have at least two-thirds of the devices turned ON.
•When connecting multiple devices, connect them in a star or linear configuration (see
the figure below). Loop and parallel configurations are not allowed.

1-3
IM 704510-17E
GP-IB Communication Interface
1
1.3 GP-IB Communication Capabilities and Specifications
GP-IB Communication Capabilities
•Listener capability
• All of the information that you can set with the panel keys can be set through the
GP-IB interface except for turning ON/OFF the power and setting the
communication parameters.
• Receives commands from a controller requesting the output of setup information,
measured data, and other information.
•Also receives status report commands.
•Talker capability
Outputs setup information, measured data, and other information.
Note
Listen-only, talk-only, and controller capabilities are not available on this instrument.
Switching between Remote and Local Modes
•When switching from local to remote mode
Receiving a REN (Remote Enable) message from the controller when the instrument
is in the local mode causes the instrument to switch to the remote mode.
•REMOTE indication appears at the upper right corner of the screen (see page 1-1).
•All keys other than the LOCAL (SHIFT+AUTO SCALE) key are locked.
•The settings that existed in the local mode are maintained even when the
instrument switches to the remote mode.
•When switching from remote to local mode
Pressing the LOCAL (SHIFT+AUTO SCALE) key when the instrument is in the
remote mode causes the instrument to switch to the local mode. However, this act is
invalid if the instrument has been set to Local Lockout mode (see page 1-6) by the
controller.
• REMOTE indication at the upper right corner of the screen disappears.
•Key operations are enabled.
•The settings that existed in the remote mode are maintained even when the
instrument switches to the local mode.
1.3 GP-IB Communication Capabilities and Specifications

1-4 IM 704510-17E
GP-IB Interface Specifications
Electrical and mechanical specifications: Conforms to IEEE St’d 488-1978 (JIS C1901-
1987)
Functional specifications: See table below.
Protocol: Conforms to IEEE St’d 488.2-1992
Code: ISO (ASCII) code
Mode: Addressable mode
Address setting: The address can be set in the range from 0 to
30 on the GP-IB setup menu that is played
using the UTILITY key.
Clear remote mode: Clear remote mode by pressing the LOCAL
(SHIFT+AUTO SCALE) key. However, key
operations are void when Local Lockout is
enabled by the controller.
Function Subset Name Description
Source handshaking SH1 Full source handshaking capability
Acceptor handshaking AH1 Full acceptor handshaking capability
Talker T6 Basic talker capability, serial polling, untalk on
MLA (My Listen Address), and no talk-only
capability
Listener L4 Basic listener capability, unlisten on MTA (My
Talk Address), and no listen-only capability.
Service request SR1 Full service request capability
Remote local RL1 Full remote/local capability
Parallel polling PP0 No parallel polling capability
Device clear DC1 Full device clear capability
Device trigger DT1 Full device trigger capability
Controller C0 No controller capability
Electrical characteristics E1 Open collector
1.3 GP-IB Communication Capabilities and Specifications

1-5
IM 704510-17E
GP-IB Communication Interface
1
1.4 Settings on the TA720
Procedure
1. Press the UTILITY key to display the Utility menu.
2. Press the Device soft key to display the Device selection menu.
3. Select GP-IB using the soft key.
4. Set the address using the rotary knob or numeric keys.
Set the address using the rotary knob or numeric keys.
Explanation
Setting the Address
Each device that can be connected via GP-IB has a unique address within the GP-IB
system. This address is used to distinguish the device from others. Therefore, when
you connect the TA720 to a PC, for example, make sure to assign a unique address to
the TA720.
Select the address from the following: The initial value is 1.
Selectable range: 0 to 30
1.4 Settings on the TA720

1-6 IM 704510-17E
1.5 Responses to Interface Messages
What Is an Interface Message
Interface messages are also referred to as interface commands or bus commands. They
are commands that are issued by the controller. They are classified as follows:
•Uni-line messages
A single control line is used to transmit uni-line messages. The following three types
are available.
IFC (Interface Clear), REN (Remote Enable), and IDY (Identify)
•Multi-line messages
Eight data lines are used to transmit multi-line messages. The messages are
classified as follows:
•Address commands
These commands are valid when the instrument is designated as a listener or as a
talker. The following five types are available.
•Commands that are valid on an instrument that is designated as a listener
GTL (Go To Local), SDC (Selected Device Clear), PPC (Parallel Poll Configure),
and GET (Group Execute Trigger)
•Commands that are valid on an instrument that is designated as a talker
TCT (Take Control)
•Universal commands
These commands are valid on all instruments regardless of the listener and talker
designations. The following five types are available.
LLO (Local Lockout), DCL (Device Clear), PPU (Parallel Poll Unconfigure), SPE
(Serial Poll Enable), and SPD (Serial Poll Disable)
•In addition, listener address, talker address, and secondary commands are also
considered interface messages.
•The differences between SDC and DCL
In multi-line messages, SDC messages are those that require talker or listener
designation and DCL messages are those that do not require the designation.
Therefore, SDC messages are directed at a particular instrument while DCL
messages are directed at all instruments on the bus.
Responses to Interface Messages
•Responses to a uni-line message
•IFC: Clears the talker and listener functions. Stops output if data are being
output.
•REN: Switches between the remote and local modes.
•IDY: Not supported.
•Responses to a multi-line message (address command)
•GTL: Switches to the local mode.
•SDC: Clears the program message (command) being received and the
output queue (see page 5-5).
•GET: Same operation as the *TRG command.
• The COMMunicate:WAIT command is immediately terminated.
•PPC or TCT: Not supported.
•Responses to a multi-line message (universal command)
•LLO: Disables the LOCAL key on the front panel to prohibit switching to the
local mode.
•DCL: Same operation as the SDC message.
•SPE: Sets the talker function on all devices on the bus to serial polling mode.
The controller polls the devices in order.
•SPD: Clears the serial polling mode of the talker function on all devices on the bus.
•PPU: Not supported.
1.5 Responses to Interface Messages

2-1
IM 704510-17E
Ethernet Communication Interface (Option)
2
2.1 Names and Functions of the Parts Related to Ethernet Communications
Chapter 2 Ethernet Communication Interface
(Option)
2.1 Names and Functions of the Parts Related to Ethernet Communications
Front Panel
Remote
UTILITY key
Press this key to set the user name
and password for user verification
and TCP/IP parameters.
LOCAL key (SHIFT+AUTO SCALE) key
Press this key to clear the remote mode
(controlled via communications) and enter the
local mode in which key operations are enabled.
Remote indication appears at the upper right corner of the
screen when in remote mode using communications.
POWER
ESC
CH A CH
sec/V/
MHz
LOCAL
INITIALIZE FILE
COPY MENU
SHIFT
EXT ARM/EXT GATE INHIBIT
50 1M 40Vpk 1M 40Vpk5V rms
B
MODE
ENTER
0
123
m
456
789n
SINGLE START/STOP
COPY
AUTO
SCALE
FUNCTION INPUT
MARKERUTILITY
SAMPLE
DISPLAY SCALE
R
E
S
E
T
S
E
L
S
C
T
Rear Panel
Ethernet interface connector
Connector used to connect the TA720 to the
controller (PC) using an Ethernet cable.
For details on how to connect the cable, see page 2-3.
REFERENCE
GATE OUT
MONITOR
OUT
PROBE
POWER
ADJUST
ETHERNET
100-240V AC
250VA MAX
50/60Hz
FUSE 250V T 3.15A
GP-IB(IEEE488)
10BASE - T
TX
LINK
(TTL)
( 12V)(50 )
10MHz OUT
(1Vp-p)
10MHz REF IN
(1Vp-p)
1Vp-p
CH
B
CH
A
WARNING
Do not operate without reading
safety precautions in user s manual

2-2 IM 704510-17E
2.2 Ethernet Communications Functions and Specifications
2.2 Ethernet Communications Functions and Specifications
Reception Function
You can specify the same settings as those specified by front panel key operations.
Receives output requests for measured and computed data, setting parameters of the
panel, and error codes.
Transmission Function
Outputs measured and computed data.
Outputs setting parameters of the panel and the status byte.
Outputs error codes that are generated.
Ethernet Communication Interface Specifications
Number of communication ports: 1
Electrical and mechanical specifications: Conforms to IEEE802.3
Transmission system: 10BASE-T
Maximum transmission rate: 10 Mbps
Connector type: RJ-45
Switching between Remote and Local Modes
•When switching from local to remote mode
If the TA720 receives a “:COMMunicate:REMote ON” command from the PC when it
is in the local mode, it switches to the remote mode.
•REMOTE is displayed at the upper left corner of the screen.
•All keys except the LOCAL (SHIFT+AUTO SCALE) key are disabled.
•The settings that existed in the local mode are maintained even when the
instrument switches to the remote mode.
•When switching from remote to local mode
Pressing the LOCAL (SHIFT+AUTO SCALE) key when the instrument is in the
remote mode causes the instrument to switch to the local mode. However, this is void
when the TA720 has received a “:COMMunicate:LOCKout ON” command from the PC
(local lockout condition).
When the TA720 receives a “:COMMunicate:REMote OFF” command from the PC,
the TA720 switches to the local mode regardless of the local lock condition.
•REMOTE indication at the upper right corner disappears.
•Key operations are enabled.
•The settings that existed in the remote mode are maintained even when the
instrument switches to the local mode.
Note
The Ethernet communication interface cannot be used concurrently with the GP-IB interface.
User Verification Function
When using the Ethernet communication interface, a user name and password are
required when connecting to the network. The user name and password are set on the
User Account pop-up window under the Utility menu of the TA720. For details, see
section 2.4, “Setting the TA720.”

2-3
IM 704510-17E
Ethernet Communication Interface (Option)
2
2.3 Connection Using the Ethernet Communication Interface
2.3 Connection Using the Ethernet Communication Interface
Connection Procedure
Connect a UTP (Unshielded Twisted-Pair) cable or an STP (Shielded Twisted-Pair)
cable that is connected to a hub, for example, to the 10BASE-T port on the rear panel of
the TA720.
Hub or router that supports 10BASE-T
PC or workstation
UTP cable or STP cable
(Straight cable)
Ethernet NIC
POWER
ESC
CH A CH
sec/V/
LOCAL
INITIALIZE FILE
COPYMENU
SHIFT
EXT ARM/EXT GATE INHIBIT
50 1M 40Vpk 1M 40Vpk5V rms
B
MODE
ENTER
0
123
m
456
789n
SINGLE START/STOP
COPY
AUTO
SCALE
FUNCTION INPUT
MARKER UTI LITY
SAMPLE
DISPLAY SCALE
R
E
S
E
T
S
E
L
S
C
T
Ethernet port (10BASE-T)
RJ-45 modular jack
Precautions to Be Taken When Connecting Cables
To connect the TA720 and a PC, be sure to use a straight cable via a hub. Operation is
not guaranteed when the TA720 and the PC are connected one-to-one using a cross
cable.

2-4 IM 704510-17E
2.4 Setting the TA720
2.4 Setting the TA720
Procedure
•Selecting the Communication Interface
1. Press the UTILITY key to display the Utility menu.
2. Press the Device soft key to display the Device selection menu.
3. Press the Ethernet soft key.
Note
Only the communication interface selected by Device is enabled. The TA720 does not accept
commands that are transmitted using an unselected GP-IB communication interface.
• Setting the User Name, Password, and Timeout
4. Press the Account soft key.
The user verification dialog box opens.
5. Turn the rotary knob to move the cursor onto the User Name.
6. Press the SELECT key to display the keyboard.
7. Enter the user name. Specify anonymous if you wish to allow access to all
users. To restrict access, enter the user name using up to 15 characters.
8. Turn the rotary knob to move the cursor to Password.
9. Press the SELECT key to display the keyboard.
10. Enter the password using up to 15 characters.
11. Turn the rotary knob to move the cursor onto the Time Out.
12. Press the SELECT key.
13. Set the timeout time using the rotary knob or numeric keys.
14. Press the SELECT key to confirm the new settings.

2-5
IM 704510-17E
Ethernet Communication Interface (Option)
2
2.4 Setting the TA720
Note
•For details on the keyboard operation, see section 4.4, “Entering Values and Character
Strings” in the
TA720 User’s Manual IM704510-01E .
•User name and password are case-sensitive.
•Setting the TCP/IP
To use the network interface function, the following TCP/IP settings must be entered.
•IP address
•Subnet mask
•Default gateway
For details on how to enter these parameters, see section 12.2, “Setting the TCP/IP”
in the
TA720 User’s Manual IM704510-01E .
Explanation
Enter the following settings when using a controller to set information that can be
specified through key operation on the TA720 or when outputting setting parameters or
output waveform data to the controller.
•Setting the User Name and Password
The network interface has a user verification function. A user name and password for
the TA720 are set in advance.
•Setting the User Name
Enter the password using up to 15 characters. The default setting is “anonymous.”
•Setting the password
Enter the password using up to 15 characters.
•Setting the Timeout Time
The connection to the TA720 is automatically dropped if there is no access to the
TA720 for the specified time. The default setting is Infinite (no timeout).
•Setting the TCP/IP
For details, see section 12.2, “Setting the TCP/IP” in the
TA720 User’s Manual
IM704510-01E .
Note
•If the user verification fails, connection to the TA720 is dropped.
•Password is not required if the user name is “anonymous.”
•If you change the user name, password, timeout time, or TCP/IP settings, power-cycle the
TA720 to activate the new settings.

3-1IM 704510-17E
Program Syntax and Programming
3
3.1 Messages
Chapter 3 Program Syntax and Programming
<PMT>
PMT is a program message terminator. The following
three types are available.
NL (New Line): Same as LF (Line Feed). ASCII
code “0AH”
^END:END message that is defined in
IEEE488.1 (EOI signal)
(The data byte that is sent
simultaneously with the END
message is the last data of the
program message.)
NL^END:NL with an END message added
(NL is not included in the program
message.)
•Program Message Unit Format
The program message unit format is shown below.
,
<Program header> <Program data>Space
<Program header>
The program header indicates the command type. For
details, see page 3-3.
<Program Data>
If certain conditions are required in executing a
command, program data is added. A space (ASCII
code “20H”) separates the program data from the
header. If there are multiple sets of program data, they
are separated by commas (,).
For details, see page 3-5.
Example
Header Data
:SAMPLE:GATE:MODE EVENT<PMT>
3.1 Messages
Message
Messages are used to exchange information between
the controller and the instrument. Messages that are
sent from the controller to the instrument are called
program messages and messages that are sent back
from the instrument to the controller are called
response messages.
If a program message contains a message unit that
requests a response (a query), the instrument returns
a response message upon receiving the program
message. A single response message is always
returned in response to a single program message.
Program Message
Data that is sent from the controller to the instrument
are called program messages. The program message
format is shown below.
<PMT>
;
<Program message unit>
<Program Message Unit>
A program message consists of one or more program
message units; each unit corresponds to one
command. The instrument executes the received
commands in order.
Each program message unit is separated by a
semicolon (;).
For details regarding the format of the program
message unit, see the next section.
Example
Unit Unit
:MEASURE:MODE HHISTOGRAM;FUNCTION PERIOD,A<PMT>

3-2 IM 704510-17E
3.1 Messages
Response Message
Data that is sent from the instrument to the controller
are called response messages. The response
message format is shown below.
<RMT>
;
<Response message unit>
<Response Message Unit>
A response message consists of one or more
response message units; each response message unit
corresponds to one response.
Response message units are separated by a
semicolon (;).
For details regarding the format of the response
message unit, see page 3-4.
Example
Unit Unit
:SAMPLE:GATE:MODE EXTERNAL;POLARITY POSITIVE<RMT>
<RMT>
A response message terminator. It is NL^END.
•Response Message Unit Format
The response message unit format is shown below.
,
<Response header> <Response data>Space
<Response Header>
A response header sometimes precedes the response
data. A space separates the data from the header.
For details, see page 3-4.
<Response Data>
Response data contains the content of the response.
If there are multiple sets of response data, they are
separated by commas (,). For details, see page 3-5.
Example
Data Header Data
500.0E-03<RMT> :SAMPLE:INTERVAL MINIMUM<RMT>
If there are multiple queries in a program message,
responses are made in the same order as the queries.
In most cases, a single query returns a single
response message unit, but there are a few queries
that return multiple units. The first response message
unit always corresponds to the first query, but the nth
response unit may not necessarily correspond to the
nth query. Therefore, if you want to make sure that
every response is retrieved, divide the program
messages into individual messages.
Precautions to Be Taken when Transferring
Messages
•If a program message that does not contain a query
is sent, the next program message can be sent at
any time.
•If a program message that contains a query is sent,
a response message must be received before the
next program message can be sent. If the next
program message is sent before the response
message is received in its entirety, an error occurs.
The response message that was not received is
discarded.
•If the controller tries to receive a response message
when there is none, an error occurs. If the
controller tries to receive a response message
before the transmission of the program message is
complete, an error occurs.
•If a program message containing multiple message
units is sent, and the message contains incomplete
units, the instrument will attempt to execute the
ones that are believed to be complete. However,
these attempts may not always be successful. In
addition, if the message contains queries, the
responses may not be returned.
Deadlock
The instrument can store in its buffer program and
response messages of length 1024 bytes or more (The
number of available bytes varies depending on the
operating conditions). When both the transmit and
receive buffers become full at the same time, the
instrument can no longer continue to operate. This
state is called a deadlock. In this case, operation can
be resumed by discarding the program message.
Deadlock will not occur if the program message
(including the <PMT>) is kept below 1024 bytes.
Furthermore, deadlock never occurs if a program
message does not contain a query.

3-3IM 704510-17E
Program Syntax and Programming
3
3.2 Commands
3.2 Commands
Command
There are three types of commands (program headers)
that are sent from the controller to the instrument.
They differ in their program header formats.
Common Command Header
Commands that are defined in the IEEE 488.2-1992
are called common commands. The header format of
a common command is shown below. An asterisk (*)
is always placed in the beginning of a command.
*<Mnemonic> ?
An example of a common command: *CLS
Compound Header
Dedicated commands used by the instrument are
classified and arranged in a hierarchy according to
their functions. The format of a compound header is
shown below. A colon (:) must be used to specify a
lower hierarchy.
:
<Mnemonic> ? :
An example of a compound header:
MEASURE:FUNCTION
Simple Header
These commands are functionally independent and do
not have a hierarchy. The format of a simple header is
shown below.
<Mnemonic> ? :
An example of a simple header: START
Note
A <mnemonic> is a character string made up of alphanumeric
characters.
When Concatenating Commands
•Command Group
A command group is a group of commands that
have common compound headers arranged in a
hierarchy. A command group may contain sub-
groups.
Example Group of commands related to sampling
:SAMPLE?
:SAMPLE:GATE?
:SAMPLE:GATE:MODE
:SAMPLE:GATE:EVENTSIZE
:SAMPLE:GATE:POLARITY
:SAMPLE:GATE:TIME
:SAMPLE:INTERVAL
:SAMPLE:ARMING:SOURCE
:SAMPLE:ARMING:DELAY:MODE
:SAMPLE:ARMING:DELAY:TIME
•When Concatenating Commands of the Same
Group
The instrument stores the hierarchical level of the
command that is currently being executed, and
performs analysis on the assumption that the next
command sent will also belong to the same level.
Therefore, common header sections can be omitted
for commands belonging to the same group.
Example :INPUT:ACHANNEL:COUPLING AC;
IMPEDANCE I50<PMT>
•When Concatenating Commands of Different
Groups
If the following command does not belong to the
same group, a colon (:) is placed in front of the
header.
Example :MEASURE:MODE TSTAMP;:DISPLAY:
ITEM LIST<PMT>
•When Concatenating Simple Headers
If a simple header follows another command, a
colon (:) is placed in front of the simple header.
Example :MEASURE:MODE TSTAMP;:
START<PMT>
•When Concatenating Common Commands
Common commands that are defined in the IEEE
488.2-1992 are independent of hierarchy. Colons
(:) are not needed before a common command.
Example :MEASURE:MODE TSTAMP;*CLS;
FUNCTION PERIOD,A<PMT>

3-4 IM 704510-17E
3.2 Commands/3.3 Responses
•When Separating Commands with <PMT>
If a terminator is used to separate two commands,
each command is a separate message. Therefore,
the common header must be specified for each
command even when commands belonging to the
same command group are being concatenated.
Example :MEASURE:MODE TSTAMP<PMT>:
MEASURE:FUNCTION PERIOD,A<PMT>
Upper-level Query
An upper-level query is a query in which a question
mark (?) is appended to the highest level command of
a group. Execution of an upper-level query allows all
settings that can be specified in the group to be
received at once. Some query groups which are
comprised of more than three hierarchical levels can
output all the lower level settings.
Example :MEASURE?<PMT> -> :MEASURE:
MODE HHISTOGRAM;
FUNCTION PERIOD,A;SLOPE RISE
The response to an upper-level query can be
transmitted as a program message back to the
instrument. In this way, the settings that existed when
the upper-level query was made can be restored.
However, some upper-level queries will not return setup
information that is not currently in use. It is important to
remember that not all the group’s information is
necessarily returned as part of a response.
Header Interpretation Rules
The instrument interprets the header that is received
according to the rules below.
•Mnemonics are not case sensitive.
Example MEASure can be also written as
measure or Measure.
•The lower-case section of the header can be omitted.
Example MEASure can also be written as MEASU
or MEAS
• The question mark (?) at the end of a header
indicates that it is a query. The question mark (?)
cannot be omitted.
Example The shortest abbreviation for
“MEASure?” is “MEAS?.”
• If the <x> (value) at the end of a mnemonic is
omitted, it is interpreted as a 1.
Example If WINDow<x> is written as WIND, this
represents WINDow1.
•The section enclosed by braces ([]) can be omitted.
Example :CALCulation[:WINDow1]:
AVERage? can be written as
:CALCulation:AVERage?.
However, the last section enclosed by braces ([])
cannot be omitted in an upper-level query.
3.3 Responses
When the controller sends a message unit that has a
question mark (?) in its program header (query), the
instrument returns a response message to the query.
A response message is returned in one of the following
two forms.
•Response consisting of a header and data
If the response can be used as a program message
without any change, it is returned with a command
header attached.
Example :SAMPLE:GATE:MODE?<PMT> ->
:SAMPLE:GATE:MODE EVENT<RMT>
•Response consisting of data only
If the response cannot be used as a program
message unless changes are made to it (query-only
command), only the data section is returned.
However, there are query-only commands that
return responses with the header attached.
Example :STATUS:ERROR?<PMT> ->
0,”NO ERROR”<RMT>
•When You Wish to Return a Response without a
Header
Responses that return both header and data can be
set so that only the data section is returned. The
“:COMMunicate:HEADer” command is used to do
this.
•Abbreviated Form
Normally, the lower-case section is removed from a
response header before the response is returned to
the controller. Naturally, the full form of the header
can also be used. For this, the
“:COMMunicate:VERBose” command is used.