YOKOGAWA SL1000 User manual

User’s
Manual
IM 720320-17E
3rd Edition
SL1000 High-Speed
Data Acquisition Unit
Communication Interface

i
IM 720320-17E
Thank you for purchasing the SL1000 API Control. This Communication Interface
User’s Manual describes the functions and commands of the following communication
interfaces.
•USB Interface
• Ethernet Interface (Optional)
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.
The following manuals are provided for the SL1000. Please read all of them.
Manual Title Manual No. Description
SL1000
High-Speed Data Acquisition Unit
User’s Manual
IM 720120-01E Explains how to install the SL1000 and its
input modules, and explains features related to
the hardware, such as the display, and how to
operate them.
SL1000 Acquisition Software
User’s Manual
IM 720120-61E Explains all functions and procedures of the
Acquisition Software used to configure and
control the SL1000.
SL1000 Input Module
User’s Manual
IM 720120-51E Explains the specifications of the input
modules that can be installed in the SL1000.
701992/701994
Xviewer User’s Manual
IM 701992-01E Explains all functions and procedures of the
Xviewer software used to display the measured
data as waveforms on a PC.
This manual is not included with the /XV0
option.
SL1000 Control API User’s
Manual
IM 720320-01E It explains the functions for controlling the
SL1000 (the SL1000 control API).
SL1000 High-Speed Data
Acquisition Unit
Communication Interface User’s
Manual
IM 720320-17E This manual. Explains the communication
interface functions of the SL1000
Notes
• This manual, IM 720320-17E, applies to SL1000 High-Speed Data Acquisition Unit
with firmware version 2.03 or later.
If the most recent firmware version is not running on your SL1000 not all of the
features described in this manual can be used.
You can check the firmware version of your SL1000 on the overview screen. For
instructions on how to open the overview screen, see section 9.5 in the User’s Manual
IM 720120-61E. For instructions on how to update the firmware and for information
about firmware versions, see the following Webpage.
http://www.yokogawa.com/tm/
• 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.
• Copying or reproducing all or any part of the contents of this manual without the
permission of Yokogawa Electric Corporation is strictly prohibited.
3rd Edition: September 2013 (YMI)
All Rights Reserved, Copyright © 2008 Yokogawa Electric Corporation
All Rights Reserved, Copyright © 2013 Yokogawa Meters & Instruments Corporation

ii IM 720320-17E
Trademarks
• Microsoft, MS-DOS, Visual C++, Windows, Windows XP, and Windows NT are
registered trademarks of Microsoft Corporation in the United States and/or other
countries.
• Adobe and Acrobat 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 holders.
Revisions
1st Edition: December 2008
2nd Edition: December 2009
3rd Edition: September 2013

iii
IM 720320-17E
How to Use This Manual
Structure of This Manual
This user’s manual consists of the following sections.
Chapter 1 Connecting to the PC
Describes the procedure for connecting to the PC using the USB and
Ethernet interfaces.
Chapter 2 Before Programming
Describes the syntax used to transmit commands.
Chapter 3 Command
Describes all the commands one by one.
Chapter 4 Status Reports
Describes the status byte, various registers, and queues.
Appendix
Describes reference material such as an ASCII character code table.

iv IM 720320-17E
Symbols and Notations Used in This Manual
Safety Markings
The following markings are used in this manual.
CAUTION Calls attentions to actions or conditions that could cause light injury
to the user or damage to the instrument or the user’s data, and
precautions that can be taken to prevent such occurrences.
Note Calls attention to information that is important for proper operation of
the instrument.
Notation Used in the Procedural Explanations
On pages that describe the operating procedures in chapters 1 through 3, the following
notations are used to distinguish the procedures from their explanations.
Procedure Carry out the procedure according to the step numbers. All
procedures are written with inexperienced users in mind; experienced
users may not need to carry out all the steps.
Explanation This section describes the setup items and the limitations regarding
the procedures.
Notation of User Controls
Operation/Soft Key Names and Menu Items Set in Boldface
Boldface type indicates the names of user-controlled operation keys on the instrument panel,
and soft key items and menu items displayed on screen.
SHIFT+Panel Key
The SHIFT+Panel key means you will press the SHIFT key to turn ON the indicator of SHIFT
keyand then press the panel key. The menu marked in purple above the pressed key appears
on the screen.
Unit
k: Denotes “1000.” Example: 100 kS/s (sample rate)
K: Denotes “1024.” Example: 720 KB (file data size)
How to Use This Manual

v
IM 720320-17E
Symbols Used in the Syntax
The following table indicates symbols that are used in the syntax mainly in chapters 2
and 3. These symbols are referred to as BNF (Backus-Naur Form) symbols.
Symbol Meaning Example Example of Input
< > Defined value CHANnel<x> <x> = 1 to 4 CHANNEL2
{} Select from values given in { } COUPling {AC|DC|DC50|GND} COUPLING AC
|Exclusive OR
[] Can be omitted TRIGger [:SIMPle]:SLOPe TRIGger:SLOPe
How to Use This Manual

vi IM 720320-17E
Contents
How to Use This Manual.................................................................................................................. iii
Chapter 1 Connecting to a PC
1.1 Connecting via USB................................................................................................................ 1-1
1.2 Connecting via Ethernet (Optional)......................................................................................... 1-2
Chapter 2 Before Programming
2.1 Messages ......................................................................................................................... 2-1
2.2 Commands ....................................................................................................................... 2-3
2.3 Response ......................................................................................................................... 2-5
2.4 Data.................................................................................................................................. 2-6
2.5 Synchronization with the Controller.................................................................................. 2-8
Chapter 3 Commands
3.1 Notes on Use of Communication Commands .................................................................. 3-1
3.2 A List of Commands ......................................................................................................... 3-2
3.3 ACQuire Group............................................................................................................... 3-12
3.4 ALARm Group ................................................................................................................ 3-14
3.5 ASETup Group ............................................................................................................... 3-17
3.6 CALibrate Group ............................................................................................................ 3-18
3.7 CHANnel Group ............................................................................................................. 3-19
3.8 COMMunicate Group ..................................................................................................... 3-33
3.9 CONTrol Group .............................................................................................................. 3-35
3.10 DATa Group .................................................................................................................... 3-36
3.11 ETHernet Group ............................................................................................................. 3-37
3.12 FILE Group..................................................................................................................... 3-38
3.13 GONogo Group .............................................................................................................. 3-40
3.14 HISTory Group................................................................................................................ 3-42
3.15 INITialize Group.............................................................................................................. 3-43
3.16 MEASure Group ............................................................................................................. 3-44
3.17 MONitor Group ............................................................................................................... 3-47
3.18 MRECord Group............................................................................................................. 3-49
3.19 MTRigger Group............................................................................................................. 3-51
3.20 SELFtest Group.............................................................................................................. 3-52
3.21 SSTart Group.................................................................................................................. 3-53
3.22 STARt Group .................................................................................................................. 3-54
3.23 STATus Group ................................................................................................................ 3-55
3.24 STOP Group................................................................................................................... 3-56
3.25 SYSTem Group .............................................................................................................. 3-57
3.26 TIMebase Group ............................................................................................................ 3-59
3.27 TRIGger Group............................................................................................................... 3-60
3.28 WAVeform Group............................................................................................................ 3-64
3.29 Common Command Group ............................................................................................ 3-67

vii
IM 720320-17E
Contents
1
2
3
4
App
Index
Chapter 4 Status Reports
4.1 Overview of the Status Report ......................................................................................... 4-1
4.2 Status Byte ....................................................................................................................... 4-3
4.3 Standard Event Register .................................................................................................. 4-4
4.4 Extended Event Register.................................................................................................. 4-5
4.5 Output Queue and Error Queue ....................................................................................... 4-6
Appendix
Appendix 1 ASCII Character Codes...................................................................................... App-1
Appendix 2 Error Messages..................................................................................................App-2

1-1
IM 720320-17E
Connecting to a PC
1
2
3
4
App
Index
Chapter 1 Connecting to a PC
1.1 Connecting via USB
Procedure
Use the following procedure to connect the SL1000 High-Speed Data Acquisition Unit
(hereinafter, the SL1000 unit) to the PC.
Installing the Acquisition Software
Install the acquisition software that came with the SL1000 unit on the PC. For
instructions, see section 2.2, “Installing or Uninstalling the Acquisition Software” in the
SL1000 Acquisition Software User’s Manual (IM720120-61E).
Connecting via USB Cable
Connect the SL1000 unit to the PC by following the procedure in section 4.1, “Connecting
to a PC” in the SL1000 High-Speed Data Acquisition Unit User’s Manual (IM720120-01E).
Installing the USB Driver
Install the USB driver on the PC by following the procedure in section 2.3, “Installing the
USB Driver” in the SL1000 Acquisition Software Unit User’s Manual (IM720120-61E).
This is only necessary the first time the SL1000 unit is connected to the PC.
Note
The USB and Ethernet interfaces cannot be used at the same.

1-2 IM 720320-17E
1.2 Connecting via Ethernet (Optional)
Procedure
Use the following procedure to connect the SL1000 unit to the PC.
Note
Because communications settings are also entered on the SL1000 unit when connecting via
Ethernet, at first it is necessary to connect via USB.
Installing the Acquisition Software (First Time Only)
Install the acquisition software that came with the SL1000 unit on the PC. For
instructions, see section 2.2, “Installing or Uninstalling the Acquisition Software” in the
SL1000 Acquisition Software User’s Manual (IM720120-61E).
Connecting via USB Cable
Connect the SL1000 unit to the PC by following the procedure in section 4.1, “Connecting
to a PC” in the SL1000 High-Speed Data Acquisition Unit User’s Manual (IM720120-01E).
Installing the USB Driver (First Time Only)
Install the USB driver on the PC by following the procedure in section 2.3, “Installing the
USB Driver” in the SL1000 Acquisition Software Unit User’s Manual (IM720120-61E).
This is only necessary the first time the SL1000 unit is connected to the PC.
Entering Communication Settings (TCP/IP Settings)
Start the acquisition software, then enter communication settings for the SL1000 unit.
For instructions, see section 3.2, “Specifying Communication Settings (When Using
the Optional Ethernet Interface)” in the SL1000 Acquisition Software User’s Manual
(IM720120-61E).
Connecting via Ethernet Cable
Close the acquisition software, then turn OFF the power to the SL1000 unit. Connect the
SL1000 unit to the PC via Ethernet by following the procedure in section 4.1, “Connecting
to a PC” in the SL1000 High-Speed Data Acquisition Unit User’s Manual (IM720120-01E).

2-1
IM 720320-17E
Before Programming
1
2
3
4
App
Index
2.1 Messages
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 4-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 4-5.
Exampl
"$2VJSF.0%&/03.BM1.5
Header Data
Response Messages
The response message format is shown belo.
<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 the next section.
Exampe
Unit Unit
"$2VJSF.0%&/03.BM.&"4VSF.0%&0/1.5
<RMT>
A response message terminator. It is NL^EOM.
Messages
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 Messages
The program message format is shown below
<PMT>
;
<Program message unit>
<Program Message Unit>
A program message consists of zero 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
"$2VJSF.0%&/03.BM.&"4VSF.0%&0/1.5
<PMT>
PMT is a program message terminator. The following
three types are available.
NL (New Line): Same as LF (Line Feed). ASCII
code “0AH”
^EOM:The END message as defined by USBTMC
(The data byte that is sent simultaneously
with the END message is the last data of the
program message.)
NL^EOM:NL with an END message added
(NL is not included in the program
message.)
Chapter 2 Before Programming

2-2 IM 720320-17E
Response Message Unit Format
The response message unit format is shown belw.
,
<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 4-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 4-5.
Exaple
&3.5"$26*3&.0%&/03."-3.5
HeaderData Data
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 attempts 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.
2.1 Messages

2-3
IM 720320-17E
Before Programming
1
2
3
4
App
Index
2.2 Commands
• 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 ACQuire:MODE NORMal;
TIME 0,0,0,0,500,0<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 (cannot be omitted).
Example :ACQuire:MODE NORMal;:CHANNEL1:
ACCL:COUPLING GND<PMT>
•When Concatenating Simple Headers
If a simple header follows another command, a
colon (:) is placed in front of the simple header
(cannot be omitted).
Example :ACQuire:MODE NORMal;:
STARt<PMT>
•When Concatenating Common Commands
Common commands that are defined in the
USBTMC-USB488 are independent of hierarchy.
Colons (:) are not needed before a common
command.
Example :ACQuire:MODE NORMal;*CLS;
TIME 0,0,0,0,500,0<PMT>
• 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 :ACQuire:MODE NORMal<PMT>:
ACQuire:TIME 0,0,0,0,500,0<PMT>
Commands
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 USBTMC-USB488
are called common commands. The header format of
a common command is shown below. An asterisk (*) is
always placed in the beginning of a cmmand.
*<Mnemonic>
Common command example: *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 hiearchy.

<Mnemonic> 
Compound header example: :ACQuire:MODE
Simple Header
These commands are functionally independent and do
not have a hierarchy. The format of a simple header is
shownbelow.
<Mnemonic> 
Simple header example: :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 acquisition
:ACQuire:ECLock?
:ACQuire:ECLock:PCOunt
:ACQuire:ECLock:COUNt
:ACQuire:MMODe
:ACQuire:MODE
:ACQuire:TIME

2-4 IM 720320-17E
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.
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 do 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 “CONTrol” can also be written as
“control” or “Control.”
•The lower-case section of the header can be
omitted.
Example “CONTrol” can also be written as “CONTR”
or “CONT.”
•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 CONTrol? is
CONT?.
•If the <x> (value) at the end of a mnemonic is
omitted, it is interpreted as a 1.
Example If “CHANnel<x>” is written as “CHAN,” it
means “CHANnel1.”
•The section enclosed by braces ([]) can be
omitted.
Example CHANnel1[:VOLTage]:COUPling can
also be written as CHAN1:COUP.
However, the last section enclosed by braces ([])
cannot be omitted in an upper-level query.
Example “CHANnel1?” and “CHANnel1:
COUPling?” are different queries.
2.2 Commands

2-5
IM 720320-17E
Before Programming
1
2
3
4
App
Index
2.3 Response
Response
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 :ACQUire:MODE?<PMT>
-> :ACQUire:MODE NORMAL<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.
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. The sections enclosed by braces
([]) are also omitted in the abbreviated form.

2-6 IM 720320-17E
2.4 Data
<Voltage>, <Time>, <Frequency>, and <Current>
<Voltage>, <Time>, <Frequency>, and <Current>
indicate decimal values that have physical significance.
<Multiplier> or <Unit> can be attached to the <NRf>
form that was described earlier. It is expressed in one
of the following forms.
Form Example
<NRf><Multiplier><Unit> 5MV
<NRf><Unit> 5E-3V
<NRf><Multiplier> 5M
<NRf> 5E-3
<Multiplier>
<Multipliers> which can be used are indicated
below.
Symbol Word Multiplier
EX Exa 1018
PE Peta 1015
T Tera 1012
G Giga 109
MA Mega 106
K Kilo 103
M Milli 10–3
U Micro 10–6
N Nano 10–9
P Pico 10–12
F Femto 10–15
A Ato 10–18
<Unit>
<Units> that can be used are indicated below.
Symbol Word Meaning
V Volt Voltage
S Second Time
HZ Hertz Frequency
MHZ Megahertz Frequency
A Ampere Current
• <Multiplier> and <Unit> are not case sensitive.
• “U” is used to indicate micro “µ”.
• “MA” is used for Mega to distinguish it from Milli.
The only exception is Megahertz which is expressed
as “MHZ.” Therefore, the “M (Milli)” multiplier cannot
be used for frequencies.
•If both <Multiplier> and <Unit> are omitted, the
default unit is used.
• Response messages are always expressed in the
<NR3> form. Response messages are returned
using the default unit without the <Multiplier> or
<Unit>.
Data
A data section comes after the header. A space must be
included between the header and the data. The data
contains conditions and values. Data is classified as below.
Data Meaning
<Decimal> A value expressed as a decimal number
(Example: Probe attenuation of CH1
-> CHANnel1:PROBe 100)
<Voltage><Time> A physical value
<Frequency> (Example: Time axis range
<Current> -> TIMebase:TDIV 1US)
<Register> Register value expressed as binary, octal,
decimal or hexadecimal.
(Example: Extended event register value
-> STATUS:EESE #HFE)
<Character Data> Predefined character string (mnemonic).
Can be selected from { }.
(Example: Select the input coupling of CH1
-> CHANnel1:COUPling
{AC|DC|DC50|GND})
<Boolean> Indicates ON and OFF. Set using ON,
OFF or a value
(Example: Turn ON the CH1 display
-> CHANnel1:DISPlay ON)
<String data> An arbitrary character string
(Example: Comment to a screen data output
-> MATH1:UNIT:USERdefine "VOLT")
<Filename> Indicates a file name.
(Example: Save file name
−> FILE:SAVE:WAVeform:NAME "CASE1")
<Block data> Arbitrary 8-bit data
(Example: Response to acquired waveform data
-> #800000010ABCDEFGHIJ)
<Decimal>
<Decimal> indicates a value expressed as a decimal
number, as shown in the table below. Decimal values
are given in the NR form as specified in the ANSI
X3.42-1975.
Symbol Meaning Example
<NR1> Integer 125-1 +1000
<NR2> Fixed-point number 125.0 -.90 +001.
<NR3> Floating-point number 125.0E+0 -9E-1 +.1E4
<NRf> Any of the forms <NR1> to <NR3> is allowed.
• The instrument can receive decimal values that are
sent from the controller in any of the forms, <NR1>
to <NR3>. This is represented by <NRf>.
•For response messages that the instrument returns
to the controller, the form (<NR1> to <NR3> to be
used) is determined by the query. The same form is
used regardless of the size of the value.
•For the <NR3> format, the “+” sign after the “E” can
be omitted. However, the “-” sign cannot be omitted.
• If a value outside the setting range is entered, the
value is normalized so that it is just inside the range.
• If a value has more significant digits than the
available resolution, the value is rounded.

2-7
IM 720320-17E
Before Programming
1
2
3
4
App
Index
<Register>
<Register> indicates an integer, and can be expressed
in hexadecimal, octal, or binary as well as a decimal
number. It is used when each bit of the value has
a particular meaning. It is expressed in one of the
following forms.
Form Example
<NRf> 1
#H<Hexadecimal value made up of the digits #H0F
0 to 9 and A to F>
#Q<Octal value made up of the digits 0 to 7> #Q777
#B<Binary value made up of the digits 0 and 1> #B001100
• <Register> is not case sensitive.
• Response messages are always expressed as
<NR1>.
<Character Data>
<Character Data> is a specified string of character data
(a mnemonic). It is mainly used to indicate options
and is chosen from the character strings given in { }.
For interpretation rules, refer to “Header Interpretation
Rules” on page 4-4.
Form Example
{AC|DC|DC50|GND} AC
• As with the header, the “COMMunicate:VERBose”
command can be used to select whether to return
the response in the full form or in the abbreviated
form.
•The “COMMunicate:HEADer” setting does not
affect the character data.
<Boolean>
<Boolean> is data that indicates ON or OFF. It is
expressed in one of the following forms.
Form Example
{ON|OFF|<NRf>} ON OFF 1 0
• When <Boolean> is expressed in the <NRf> form,
“OFF” is selected if the rounded integer value is 0,
and ON for all other cases.
•A response message is always returned with a 1 if
the value is ON and 0 if the value is OFF.
<String data>
<String data> is not a specified character string like
<Character data>. It is an arbitrary character string.
The character string must be enclosed in single
quotation marks (') or double quotation marks (").
Form Example
<String data> 'ABC' "IEEE488.2-1987"
• If a character string contains a double quotation mark
('), the double quotation mark is replaced by two
double quotation marks (""). This rule also applies
to a single quotation mark within a character string.
•A response message is always enclosed in double
quotation marks (").
• <String data> is an arbitrary character string.
Therefore the instrument assumes that the
remaining program message units are part of the
character string if no single (') or double quotation
mark (") is encountered. As a result, no error is
detected if a quotation mark is omitted.
<Filename>
<Filename> is data that indicates a file name. It is
expressed in one of the following forms.
Form Example
{<NRf>|<Character data>|<String data>} 1 CASE "CASE"
• <NRf> is rounded to an 8-digit integer and converted
to ASCII code. The result is the file name (example:
1becomes "00000001"). Negative values are not
allowed.
•Response messages are always returned in the
<String data> form.
• For <Character data>, the first 12 characters
become the file name.
• For <String data>, the first 259 characters become
the file name.
• For a description of the number of characters of the
<String data> file name, see the DL9500/DL9700
User’s Manual.
<Block data>
<Block data> is arbitrary 8-bit data. It is only used in
response messages on the DL9500/DL9700. Below is
the syntax.
Form Example
#N<N-digit decimal number> #800000010ABCDEFGHIJ
<Data byte sequence>
• #N
Indicates that the data is <Block data>. “N”
indicates the number of succeeding data bytes
(digits) in ASCII code characters.
• <N-digit decimal number>
Indicates the number of bytes of data (example:
00000010 = 10 bytes).
• <data byte sequence>
Expresses the actual data (example: ABCDEFGHIJ).
• Data is comprised of 8-bit values (0 to 255). This
means that the ASCII code “0AH,” which stands for
“NL,” can also be a code used for data. Hence, care
must be taken when programming the controller.
2.4 Data

2-8 IM 720320-17E
2.5 Synchronization with the Controller
• Using the COMMunicate:OVERlap command
The COMMunicate:OVERlap command enables (or
disables) overlap operation.
Example :COMMunicate:OVERlap #HFFBF;:
FILE:LOAD:SETup:
EXECute "CASE1";:CHANnel1:
VDIV?<PMT>
“COMMunicate:OVERlap #HFFBF” enables
overlap operation on commands other than media
access. Because the overlap operation of file
loading is disabled, “FILE:LOAD:SETup:EXECute
"CASE1"” operates in the same way as a sequential
command. Therefore, CHANnel1:
VDIV? is not executed until the file loading is
complete.
•Using the *OPC Command
The *OPC command sets the OPC bit, bit 0 of the
standard event register (see page 6-4), to 1 when
the overlap operation is completed.
Example :COMMunicate:OPSE #H0040;
*ESE 1;
*ESR?;*SRE 32;:FILE:LOAD:SETup:
EXECute "CASE1";*OPC<PMT>
(Read the response to *ESR?)
(Wait for a service request)
:CHANnel1:VDIV?<PMT>
“COMMunicate:OPSE” is a command used to select
the “*OPC” target. Here, media access is specified.
“*ESE 1” and “*SRE 32” indicate that a service
request is generated only when the OPC bit is 1.
“*ESR?” clears the standard event register.
In the example above, “CHANnel1:VDIV?” is not
executed until a service request is generated.
Overlap Commands and Sequential Commands
There are two types of commands, overlap commands
and sequential commands. In the case of overlap
commands, the execution of the next command may
start before the execution of the previous command is
completed.
For example, if the next program message is
transmitted when specifying the V/div value and
querying the result, the response always returns the
most recent setting (5 V in this case).
:CHANnel1:VDIV 5V;VDIV?<PMT>
This is because the next command is forced to wait
until the processing of “CHANnel1:VDIV” itself
is completed. This type of command is called a
sequential command.
On the contrary, let us assume that you send the next
program message when you wish to load a file and
query the V/div value of the result.
:FILE:LOAD:SETup:EXECute "CASE1";:
CHANnel1:VDIV?
In this case, “CHANnel1:VDIV?” is executed before
the loading of the file is completed, and the V/div value
that is returned is the value before the file is loaded.
The act of executing the next command before the
processing of itself is completed such as with “FILE:
LOAD:SETup:EXECute "CASE1"” is called an
overlap operation. A command that operates in this
way is called an overlap command.
In such case, the overlap operation can be prevented
by using the methods below.
Synchronizing with Overlap Commands
• Using the *WAI Command
The *WAI command holds the subsequent
commands until the overlap command is completed.
Example :COMMunicate:OPSE #H0040;:
FILE:LOAD:SETup:
EXECute "CASE1";*WAI;:
CHANnel1:VDIV?<PMT>
“COMMunicate:OPSE” is a command used to select
the “*WAI” target. Here, media access is specified.
Because “*WAI” is executed immediately before
“CHANnel1:VDIV?,” “CHANnel1:VDIV?” is not
executed until the file loading is complete.

2-9
IM 720320-17E
Before Programming
1
2
3
4
App
Index
• Using the *OPC? Query
The *OPC? query generates a response when an
overlap operation is completed.
Example :COMMunicate:OPSE #H0040;:FILE:
LOAD:SETup:EXECute "CASE1";
*OPC?<PMT>
(Read the response to *OPC?)
:CHANnel1:VDIV?<PMT>
“COMMunicate:OPSE” is a command used to
select the “*OPC?” target. Here, media access is
specified.
Because “*OPC?” does not generate a response
until the overlap operation is completed, the loading
of the file will have been completed by the time the
response to “*OPC?” is read.
Note
Most commands are sequential commands. Overlap
commands are indicated as overlap commands
in chapter 5. All other commands are sequential
commands.
Achieving Synchronization without Using
Overlap Commands
Even for sequential commands, synchronization is
sometimes required for non communication-related
reasons such as a trigger occurrence.
For example, if the next program message is
transmitted to make an inquiry about the waveform
data which has been acquired with the trigger mode
set to single, the WAVeform:SEND? command may
be executed regardless of whether the acquisition has
been completed or not and may result in command
execution error.
TRIGger:MODE SINGle;:STARt;:WAVeform:
SEND?<PMT>
In this case, the following method must be used to
synchronize with the end of the acquisition.
•Using the STATus:CONDition? Query
The “STATus:CONDition?” query is used to query
the contents of the condition register (page 6-5).
Whether waveforms are being retrieved can be
determined by reading bit 0 of the condition register.
If bit 0 of the condition register is “1,” waveforms are
being retrieved. Otherwise, it is stopped.
Example TRIGger:MODE SINGle;:STARt<PMT>
:STATus:CONDition?<PMT>
(Read the response. If bit 0 is 1, repeat
this command until it becomes 1.)
:WAVeform:SEND?<PMT>
The WAVeform:SEND? command will not be
executed until bit 0 of the condition register is set to
“0.”
•Using the Extended Event Register
The changes in the condition register can be
reflected in the extended event register (page 6-5).
Example :STATus:FILTer1 FALL;:
STATus:EESE 1;EESR?;*SRE 8;:
TRIGger:MODE SINGle;:STARt<PMT>
(Read the response to STATus:EESR?)
(Wait for a service request)
:WAVeform:SEND?<PMT>
The “STATus:FILTer1 FALL” command sets
the transition filter so that bit 0 (FILTer1) of the
extended event register is set to 1when bit 0 of the
condition register changes from 1to 0.
The “:STATus:EESE 1” command is used to
reflect only bit 0 of the extended event register to
the status byte.
The “STATus:EESR?” command is used to clear the
extended event register.
The “*SRE 8” command is used to generate a
service request solely on the cause of the extended
event register.
The “WAVeform:SEND?” command is not executed
until a service request is generated.
•Using the COMMunicate:WAIT Command
The “COMMunicate:WAIT” command halts
communications until a specific event is generated.
Example :STATus:FILTer1 FALL;:
STATus:EESR?;:TRIGger:
MODE SINGle<PMT>
(Read the response to STATus:EESR?)
:COMMunicate:WAIT 1;:WAVeform:
SEND?<PMT>
For a description of “STATus:FILTer1 FALL”
and “STATus:EESR?” see the previous section
regarding the extended event register.
The “COMMunicate:WAIT 1” command indicates
that the program will wait for bit 0 of the extended
event register to be set to “1.”
The WAVeform:SEND? command will not be
executed until bit 0 of the extended event register is
set to “1.”
2.5 Synchronization with the Controller

3-1
IM 720320-17E
Commands
1
2
3
4
App
Index
Chapter 3 Commands
3.1 Notes on Use of Communication Commands
When using communication commands, please note the following.
• The following functions of the SL1000 High-Speed Data Acquisition Unit are not
available when using communication commands.
• Synchronized operation of multiple units (the API can be used for synchronized
operation)
• Automatic recording to PC
• Reading of data per WAVeform group (only possible while measurement is stopped).
• At least one module must be set to measurement group 1 (using the: TIMebase:
MODUle<x>:GROUp command).
• The initial value of the: CHANnel<x>:DISPlay command that turns measurement ON/
OFF on individual channels is OFF. Turn this setting ON when using the command for
the first time.
• When using the MRECord group commands for auto recording, the initial value for the
recording destination is “PC.” When auto-recording, you must change the recording
destination to HDD.