Remote Control Manual Curve Tracer CS-3000 Series1].pdf · Remote Control Manual Curve Tracer CS-3000 Series . i Introduction Thank you for purchasing this Iwatsu’s instrument

Remote Control Manual

Curve Tracer

CS-3000 Series

i

Introduction ◇ Thank you for purchasing this Iwatsu’s instrument. Please read this manual before using the

instrument, then keep the manual handy for future reference. ◇ Please read this manual and understand the contents before use.

Safety Precautions

To ensure safe operation of the instrument and to prevent injury to the user or damage to property, items to be observed are written in the warnings and cautions in the Instruction manual attached. Be sure to read them for safe operation.

Precautions

◇ Parts of the contents of this manual may be modified without notice for improvements in performance and functions.

◇ Reproduction or reprinting of the contents of this manual without prior permission from Iwatsu is prohibited.

◇ All product names and brand names in this manual are described only for the purpose of identification: i.e., they are registered trademarks belonging to individuals and corporate bodies.

◇ Microsoft, Microsoft Windows, Visual Basic, and Microsoft Excel are registered trademarks of Microsoft Corporation. NI, National Instruments, and NI-VISA are registered trademarks of National Instruments Corporation.

◇ For inquiry about this instrument, contact Iwatsu office or our sales distributors. Revision History

◇ February 2010 : 1st edition

KML069611

ii

Memo

― 1 ―

Contents

1. Remote Control .......................................................................................................................3 1.1 General ..............................................................................................................................3 1.2 Restrictions of Remote Control ..........................................................................................3 1.3 Remote/Local Control ........................................................................................................3 1.4 Remote Connection Setting ...............................................................................................4 1.5 MAC Address .....................................................................................................................4 1.6 Communication Mode ........................................................................................................5 1.7 Connection with the Instrument..........................................................................................7

1.7.1 Cable Connection .....................................................................................................7 1.7.2 Confirming IP Connection.........................................................................................7 1.7.3 Confirming Connection (Example) using VISA Library .............................................9 1.7.4 Describing User Program .......................................................................................12

2. Remote Control Commands ..................................................................................................16 2.1 Message Protocol ............................................................................................................16

2.1.1 General ...................................................................................................................16 2.1.2 Delimiter..................................................................................................................17 2.1.3 Input and Output Buffers.........................................................................................17 2.1.4 Message Format.....................................................................................................18 2.1.5 Multi-Commands.....................................................................................................19 2.1.6 Query ......................................................................................................................21 2.1.7 Mnemonic ...............................................................................................................21 2.1.8 Data Format............................................................................................................22

2.2 Status Report Structure....................................................................................................26 2.2.1 Service Requests (SRQ) ........................................................................................26 2.2.2 Status Byte Register ...............................................................................................27 2.2.3 Service Request Enable Register...........................................................................28 2.2.4 Standard Event Status Register .............................................................................29 2.2.5 Standard Event Status Enable Register .................................................................30 2.2.6 Output Queue .........................................................................................................31 2.2.7 Device-Specific Error Condition Status Register ....................................................32 2.2.8 Device-Specific Error Event Status Register ..........................................................33 2.2.9 Device-Specific Error Event Status Enable Register ..............................................34 2.2.10 Measurement Condition Status Register ................................................................35 2.2.11 Measurement Event Status Register ......................................................................36

― 2 ―

2.2.12 Measurement Event Status Enable Register..........................................................37 2.3 Command List ..................................................................................................................38 2.4 Common Commands .......................................................................................................45

2.4.1 *IDN? (Device Information Reading Out)................................................................45 2.4.2 *RST (Reset) ..........................................................................................................46 2.4.3 *OPC/*OPC? (Completed Action)...........................................................................47 2.4.4 *WAI (Wait) .............................................................................................................48 2.4.5 *CLS (Status Register Clear) ..................................................................................49 2.4.6 *ESE/*ESE? (Event Status Register Enable Setting) .............................................50 2.4.7 *ESR? (Event Status Register Reading Out Setting) .............................................52 2.4.8 *PSC/*PSC? (Powering On Enable Register Clear Setting)...................................53 2.4.9 *SRE/*SRE? (Status Register Enable Setting) .......................................................54 2.4.10 *STB? (Status Byte Reading Out) ..........................................................................56 2.4.11 *TRG (Manual Trigger) ...........................................................................................58 2.4.12 *RCL (Panel Setting Recall) ...................................................................................59 2.4.13 *SAV (Panel Setting Saving) ..................................................................................60 2.4.14 *TST? (Test) ...........................................................................................................61

2.5 Hardware-Specific Commands ........................................................................................62 2.5.1 Device-Specific Status Byte Control-Related .........................................................63 2.5.2 Step Generator Control Related .............................................................................71 2.5.3 Collector Supply Control-Related ...........................................................................86 2.5.4 Screen Display Control-Related ...........................................................................105 2.5.5 Cursor Control-Related.........................................................................................129 2.5.6 System Control-Related........................................................................................143 2.5.7 Display Illumination Control-Related.....................................................................149 2.5.8 Configuration Control ............................................................................................154 2.5.9 Measurement Control ...........................................................................................155 2.5.10 Data Saving-Related.............................................................................................157 2.5.11 Data Recall-Related..............................................................................................163 2.5.12 Data Deletion-Related ..........................................................................................167 2.5.13 Data Transfer-Related ..........................................................................................172

― 3 ―

1. Remote Control 1.1 General

The remote control means to control the instrument through an external controller (usually a personal computer) in almost the same way as when you operate it manually using buttons on it. Since almost all the settings and controls on the instrument excluding those related to power ON/OFF and communication itself can be carried out remotely (full remote), it can be used for configuring the automatic measurement system using a PC. In addition, the remote control for the instrument uses the usual LAN interface through 10Base-T/100Base-TX and adopts VXI-11 as the communication protocol. Therefore, VISA library supporting VXI-11 is needed. For details on VISA library, see "1.6 Communication mode".

1.2 Restrictions of Remote Control

Almost all the functions on the instrument can be controlled remotely excluding the power switch ON/OFF and settings in UTILITY menu related to the remote interface (e.g., IP address). For functions to be controlled remotely, see the control command list in "2.3 Command list".

1.3 Remote/Local Control

The instrument does not have the status change which is widely used in the remote control for measurement instruments: e.g., remote from/to local for GPIB interface. It can always accept key operation on the panel and remote control. However, when it accepts the remote control, the menu which has been displayed on it will disappear.

― 4 ―

1.4 Remote Connection Setting

Since the instrument uses TCP/IP protocol for communication, it is required to make network settings; e.g., IP address. Since the factory default setting sets DHCP (Dynamic Host Configuration Protocol) function to ON, the network settings can be made automatically. In the environment without the DHCP server, after setting DHCP function to OFF, it is required to manually set parameters below. For settings, contact the administrator of the network to which the instrument is connected. In addition, for setting method, see the explanation on "REMOTE CONTROL submenu" in Instruction Manual.

- IP address - Subnet mask - Default gateway

In addition, since the instrument does not support the name service. It is necessary to directly set the IP address instead of a host name when setting the instrument for network connection. If DHCP sets the IP address automatically, your assigned IP address can be checked in [UTILITY]-[REMOTE CONTROL] menu.

1.5 MAC Address

To confirm your MAC address, follow: 1. Press [UTILITY] key. 2. Press the function key corresponding to [REMOTE CONTROL] button.

The menu to set parameters for REMOTE connection appears. 3. MAC address of the instrument is the hexadecimal character string displayed on

[MAC ADDRESS] button of the menu. Note that MAC address is unique to a device; i.e., cannot be changed.

― 5 ―

1.6 Communication Mode

The instrument uses VXI-11 protocol as the communication protocol. GPIB interface has been widely used as the remote control interface for measurement instruments up to now and the VXI-11 protocol can realize the same functions as GPIB on the TCP/IP protocol. VXI-11 protocol supports not only the basic input/output functions such as writing of command/query messages in the device and reading of response messages from the device but also GPIB-specific functions such as device trigger, serial poll device clear, and service request (SRQ). To make actual communication with the instrument, VISA library corresponding to VXI-11 is required. Since VISA library corresponds not only to VXI-11 but also to various interfaces such as GPIB, serial, and USB, it can supply the control application for measurement instruments with the common API (Application Programming Interface) which absorbs difference among various interfaces. For example, VISA library has APIs shown in the correspondence table below to recall functions used for measurement instrument control. These APIs can be used without any modification in the instrument adopting VXI-11 as well as GPIB measurement instruments.

Correspondence table between main measurement instrument control functions and VISA library APIs

Control function for measurement instrument corresponding to GPIB VISA library API Writing in device viWrite(), viVPrintf(), etc.Reading from device viRead(), viVScanf(), etc.Device trigger viAssertTrigger() Serial poll viReadSTB() Device clear viClear() Activation of service request (or other event) handler viEnableEvent() Registration of service request (or other event) handler viInstallHandler()

As shown above, when configuring and designing the system where measurement instruments having different interfaces are combined, use of APIs supplied by VISA library allows the user not to be aware of difference between them.

― 6 ―

Image of measurement instrument control using VISA library If communication with the instrument is made without use of VISA library, it is necessary to implement VXI-11 client function by yourself. However, complex processing of VXI-11 protocol may make the implementation very difficult. Therefore, unless acquisition of VISA library is difficult; e.g., use in UNIX environment, such implementation is not recommended. Note that Iwatsu does not supply VISA library. Please prepare it by yourself. Follow the license requirement of VISA library of the VISA library vendor. Iwatsu recommends NI-VISA from National Instruments Corporation as VISA library.

VXI-11 measurement

instrument (the instrument

etc.)

GPIB

measurement instrument

VISA library

Control application for measurement

instrument

GPIB driver

GPIB I/F

・・・

TCP/IP

Ethernet I/F

VISA API

Controller (PC)

VXI-11

Other I/F

Measurement

instrument with other I/F

― 7 ―

1.7 Connection with the Instrument

1.7.1 Cable Connection Follow steps below to confirm the physical connection between the instrument and the host computer. 1. When no cable is connected, make correct settings for network connection and

power off the instrument once. 2. When the power is off, connect the cable.

If connecting the instrument directly to the host computer, use the cross cable to connect the instrument to a PC. For connection through the network, use the straight cable to connect the instrument to the network terminal; e.g., hub.

3. Power on the instrument against. In addition, incorrect settings of network connection may cause an unexpected action to occur on the instrument and/or a device on the network. When connecting to the existing network, be sure to connect the instrument to the network after inquiring of the network administration how to set correctly.

1.7.2 Confirming IP Connection Connection on the IP network can be confirmed by using "ping" command on a PC. The command confirms the normality of the IP network by sending an IP packet to the network device and receiving its response. "ping" command can be used in Windows and UNIX environments. In Windows environment, make entry at command prompt as shown below.

C:¥>ping 192.168.102.102 (※)

(※) The argument following "ping" is used to specify the network device for which connection is confirmed. The IP address assigned to the instrument is entered in it: e.g., entry example of "192.168.102.102" above. It is necessary to replace the value with the actual value for your network environment. In addition, if the automatic assignment of an IP address is activated on DHCP, use [UTILITY]-[REMOTE CONTROL] menu to confirm the IP address actually assigned.

The following is the example of "ping" command execution result when connection is made normally.

― 8 ―

C:¥>ping 192.168.102.102 Pinging 192.168.102.102 with 32 bytes of data: Reply from 192.168.102.102: bytes=32 time

In addition, the following is the example of "ping" command execution result when no response is received and timeout occurs because of a failure on the network.

C:¥ >ping 192.168.102.102 Pinging 192.168.102.102 with 32 bytes of data: Request timed out. Request timed out. Request timed out. Request timed out. Ping statistics for 192.168.102.102: Packets: Sent = 4, Received = 0, Lost = 4 (100% loss), C:¥ >

When timeout occurs, there may be a problem in IP address setting for the instrument or the controller PC, or network connection.

― 9 ―

1.7.3 Confirming Connection (Example) using VISA Library For almost all VISA libraries, the tool to test the basic communication with the measurement instrument is supplied from the vendor. Use of such a tool allows connection with the instrument to be confirmed without creating your own application program. The following shows one example of it: how to confirm the connection using "VISA Interactive Control" attached to VISA library (NI-VISA) from National Instruments Corporation. Note that the version of NI-VISA used for the explanation in this section is Version 4.6. 1. Starting VISA Interactive Control

On Windows start menu, click on [All programs (P)] ⇒ [National Instruments] ⇒ [VISA] ⇒ [VISA Interactive Control].

2. Connection with the instrument

a. Enter VISA resource name in "Resource to Open:" edit box on the lower part of VISA Interactive Control. VISA resource name is the character string indicating the connection route to the measurement instrument and the connection method; i.e., consisting of the interface type (GPIB, Ethernet, etc.), address (GPIB address, IP address, etc), instrument name, and connection type (INSTR, INTFC, etc). For the instrument, the name is "inst0", the connection type is "INSTR", and the resource character string is as follows:

TCPIP0::192.168.102.102::inst0::INSTR The part above indicated by is the IP address assigned to the instrument.

The example shows "192.168.102.102": i.e., the part should be actually changed depending on your usage environment.

― 10 ―

b. On the menu, click on [File] ⇒ [Open Selection].

If connection is established successfully, the dialog box appears. If not, there may be problems in VISA resource name, IP address setting, or network connection.

a

b

― 11 ―

3. Sending "*IDN?" query a. Select [viWrite] tab. b. Enter "*IDN?¥n" in [Buffer] field. (Where "¥n" is the delimiter (LF).) c. Click on [Execute] button.

4. Receiving response character string

a. Select [viRead] tab. b. Click on [Execute] button. c. The response character string appears in Buffer field.

(For *IDN? query, see "2.4.1 *IDN? (device information reading out)".)

c

a

b

b

a

c

― 12 ―

1.7.4 Describing User Program The following is the step-by-step explanation of how to create the user program using VISA library which operates on Microsoft Excel 2007. Note that the explanation assumes environment below: OS : Microsoft Windows XP or Microsoft Windows Vista Reference module : VISA32.bas (Modules supplied from VISA library vendors) Used language : Microsoft Excel 2007 Visual Basic Application 1. Start Visual Basic.

To start Visual Basic, click on [Visual Basic] icon on Excel [Development] toolbar.

2. Import VISA32.bas.

On Visual Basic menu, select [File (F)] ⇒ [File import (I)] and set VISA32.bas in [File import] dialog. (VISA32.bas is Visual Basic source code supplied by VISA library vendor.)

3. Add the standard module.

On Visual Basic menu, select [Insert (I)] ⇒ [Standard module (M)] and create a new standard module.

4. Describe the user program.

Describe Visual Basic program in the new standard module created in step 3. Here, the sample program below is used.

- Outline of sample program

The sample program is very simple: i.e.; it sends/receives "*IDN?" query and displays the result on the popup dialog. It can be utilized to grasp the procedure of the measurement instrument control using VISA library.

- About VISA resource name The IP address included in VISA resource name which is indicated by in the sample program needs to be changed depending on the usage environment.

- Caution when using the sample program To simplify the explanation, the sample program does not make error check for the return value (status) of each VISA function. When actually creating the user application program, it is necessary to check the return value of each VISA

― 13 ―

function and add the error processing as required. Public Sub IDN_Query() Dim DRM As Long 'Session of resource manager Dim vi As Long 'Session of instrument Dim status As Long 'Status Dim Resp As String * 256 'Receive buffer (fixed length (256) character string) Dim ResourceString As String 'VISA resource name 'Initialize VISA resource name of the instrument '(Change IP address depending on environment) ResourceString = "TCPIP0::192.168.102.102::inst0::INSTR" 'Starting session of resource manager status = viOpenDefaultRM(DRM) 'Starting session of instrument status = viOpen(DRM, ResourceString, 0, 0, vi) 'Sending *IDN? query status = viVPrintf(vi, "*IDN?" & vbLf, 0) 'Receiving *IDN? query status = viVScanf(vi, "%s", Resp) 'Popup displaying *IDN? query response Call MsgBox(Resp, vbOKOnly, "Response to *IDN? query") 'Finishing session of instrument Call viClose(vi) 'Finishing session of resource manager Call viClose(DRM) End Sub

― 14 ―

Example of Visual Basic description 5. Execute macro.

a. Click on [Macro] icon on Excel [Development] toolbar to display the Macro dialog. b. Select "IDN_Query" in the Macro list. c. Click on [Execute (R)] button.

c b

a

Response to *IDN? Query

'Session of resource manager 'Session of instrument 'Status 'Receive buffer (fixed length (256) character string)'VISA resource name

'Initialize VISA resource name of the instrument '(Change IP address depending on environment)

'Starting session of resource manager

'Starting session of instrument

'Sending *IDN? query

'Receiving *IDN? query

'Popup displaying *IDN? query response

'Finishing session of instrument

'Finishing session of resource manager

― 15 ―

6. Execution result If the macro is executed successfully, the response character string to *IDN? query is displayed on the popup dialog. (Note that some security settings on Excel may not execute the macro.)

― 16 ―

2. Remote Control Commands 2.1 Message Protocol

This section describes the configuration of the program message that the instrument communicates with the controller, as well as the send and receive operations of the instrument. For details about data format of each command, see the description of relevant command. Remarks The elements defined in IEEE Std.488.2 are given as follows. ＜PROGRAM MESSAGE＞ → ＜CHARACTER PROGRAM DATA＞ → ＜DECIMAL NUMERIC PROGRAM DATA＞ → ＜SUFFIX PROGRAM DATA＞ → ＜STRING PROGRAM DATA＞ → ＜RESPONSE MESSAGE＞ → ＜CHARACTER RESPONSE DATA＞ → ＜NR1 NUMERIC RESPONSE DATA＞ → ＜NR2 NUMERIC RESPONSE DATA＞ → ＜NR3 NUMERIC RESPONSE DATA＞ → ＜STRING RESPONSE DATA＞ → ＜ARBITRARY ASCII RESPONSE DATA＞ →

2.1.1 General

The structure of the message to be received/sent when controlling the instrument is in accordance with IEEE Std.488.2 standard. IEEE Std.488.2 standard is widely used for measurement instrument control as the message rule on GPIB (IEEE Std.488.1) interface. However, the instrument uses VXI-11 protocol instead of GPIB interface which realizes the same functions as GPIB on TCP/IP.

Configuration of communication protocol

VXI-11

TCP/IP

Ethernet (10Base-T / 100Base-TX)

GPIB (IEEE488.1)

IEEE Std.488.2 IEEE Std.488.2

The instrument General GPIB

measurement instruments

― 17 ―

2.1.2 Delimiter When the instrument receives a program message, it recognizes LF, CR+LF, and END flag of VXI-11 message as the delimiter. If any of these delimiters is received, up to the delimiter is judged as of a command or query and the command or query is interpreted or executed. On the other hand, the delimiter when the instrument sends () is LF. In addition, END flag of a VXI-11 message is always set.

2.1.3 Input and Output Buffers - Usual message

The size of input buffer of the instrument when receiving the usual program message is 1024 bytes. If up to the delimiter is received even if the input buffer is not full, the command in the buffer is interpreted. The instrument does not receive next messages when interpreting or executing received commands. Immediately after the command has been executed and interpreted: i.e., immediately after the delimiter, the next delimiter begins to be searched. If the input buffer becomes full, the command is interpreted and executed even if no delimiter is found. Therefore, the part exceeding the buffer size is discarded. The instrument also has the output buffer of 1024 bytes (output queue). If the output buffer is full, the part of a response message exceeding the buffer size is discarded; i.e., not sent. In addition, the query error is generated at that time. Care should be taken so that the total number of bytes of the response message for multiple queries does not exceed the buffer size.

- Data transfer

For data transfer (input), the input buffer size is 1M bytes. If the size being set in the preamble of the data part in the message unit exceeds 1M bytes, data of the size being set is discarded and the command is not executed. Care should be taken so that the size of transfer data does not exceed 1M bytes. If the size being set in the preamble is 1M bytes or less, the command is executed when the data of the size being set is received. In addition, if END flag of VXI-11 message is received, data up to END flag allows the command to execute even if the size of received data does not reach the preamble-specified size. For data transfer (output), the size of the output buffer is 1024 bytes which is the same as that of usual messages. Data exceeding 1024 bytes is divided into 1024-byte data when being sent.

― 18 ―

2.1.4 Message Format One message unit consists of a header, the data, and a header separator that divides these two major parts. (Example) :STP:VOL 100E-3

Data Header separator Header a. Header

The header consists of ASCII characters. The header is composed of one to three mnemonic parts separated by a colon (:) and expresses the function or operation of the instrument. The string in the example above is a command used when setting up the instrument. When the string is a query that looks for a setting (in which cases, the instrument creates response data), the header ends with a question mark "?".

b. Header separator

This code separates the header and the data. The header separator is a space code (ASCII characters) of at least one character. The character defined in IEEE Std.488.2 may be used. The command without the data part does not need the header separator. Additionally, it is not allowed to omit the data part except for commands without the data part in the instrument.

c. Data

The data is a parameter describing the concrete setting of the function specified in the header. This part may consist of mnemonics (strings) or numerical values. When multiple parameters are needed, a comma "," is used to separate respective parameters. The number of parameters and the configuration depend on the command. For details on the data format, see the description of relevant command.

― 19 ―

2.1.5 Multi-Commands Multiple message units can be assembled to configure one message. Respective message units are separated and connected with a semicolon ";". (Example) :CSP:VAR 30.0;:CSP:LOPS 10 Message unit Message unit separator Message unit The device-specific commands for the instrument are a hierarchical command called "compound command program header". For example, the parent command CSP can be combined with subcommands such as UNI, VER, LOPS, LOPH, HV, and HC to build a header (e.g., :CSP:VER or :CSP:HC:POL). When the message units, each of which has a header composed of a common parent command, are combined to build one message, the parent command may be omitted on the second and following message units. (Example) :CSP:VAR 10.0;:CSP:HC:SWST 1000 The above message can be written in the following format. :CSP:VAR 10.0;HC:SWST 1000 (If the parent command is omitted, care should be taken so that the colon (:) is not put in the header part.) This function specifies the parent command CSP as the header path. The header path designation is valid only within the message (until the delimiter). In the next message, the parent command of the start message unit is specified as a header path. Therefore, if the colon (:) for the first character of the header part is omitted at the top of the message, the message is determined as parent command. (Example) "CSP:VAR 10.0" is interrupted as it equals ":CSP:VAR 10.0". If ":CSP:VAR 10.0;HC:SWST 1000" is sent as one message, it is

interrupted correctly. However, ":CSP:VAR 10.0; HC:SWST 1000" is sent with it separated

into ":CSP:VAR 10.0" and "HC:SWST 1000", it is determined as an error.

(The instrument does not have the HC parent command.) Head path setting can be made at the sub-command level. (Example) :CSP:HC:SWST 1000;:CSP:HC:POL NEG The above message can be written in the following format. :CSP:HC:SWST 1000;POL NEG In the case above, up to :CSP:HC has been set as the header path.

― 20 ―

If the message is started with a colon (:), this command is determined as a parent command. The header path is also updated and this command becomes a new header path. (Example) :STP:OFF 10E-3;:CSP:VAR 10.0 ↑ ↑ The header path is STP. The header path is CSP. The instrument does not search for the command along with the command tree. Therefore, if the command at the layer above the header path is made to be one message, be sure to add the colon (:) at the beginning of the message unit to change the header path. (Example) Command 1 CSP:HV:POL NEG Command 2 CSP:HC:SWST 1000 ○ :CSP:HV:POL NEG;:CSP:HC:SWST 1000 × :CSP:HV:POL NEG;HC:SWST 1000 ↑ The header path cannot be interpreted because of CSP:HV. The above header path rules do not apply to the common commands (*WAI, *OPC, etc.) defined in IEEE Std.488.2. The common commands are executed with the header path omitted. However, the header path destination is not broken and the previous header path is valid when interpreting the next message unit after the common command. (Example) :CSP:VAR 10.0;*WAI;HV:POL NEG The header path is :CSP The common command *WAI is executed correctly If the message has the message unit which includes the command not to be interpreted (command which generates a command error, e.g., character string which is not a command, parameter in the format not specified), up to the message units before that causing the command error are executed normally and the remaining units are not interpreted and are discarded. The command error is returned.

― 21 ―

2.1.6 Query A message whose header ends with a question mark "?" is called a query. The query is a command used to inquire settings and measurement results. Upon reception of a query, the instrument creates a response message and stores it in the output queue. When (a part of) the response message remains in the output queue and a new message is received, the current contents of the output queue are cleared, causing a query error (service request event). Depending on the type of query, the created response message, in which multiple message units are connected by a comma (,). For details of response message format, see the description of relevant query.

2.1.7 Mnemonic The header mnemonic is formed from ASCII codes for A to Z, 0 to 9, and an underscore (_). ASCII's A to Z characters are not case-sensitive. In other words, there is no distinction between uppercase and lowercase letters, as they are interpreted in the same way. The instrument has the long format and short format for the mnemonic in the header part. Functions of both formats are the completely same. Both formats can be mixed in one message unit. Commands below have the same meanings. COLLECTORSUPPLY CSP CollectorSupply csp In addition, the message unit can include uppercase and lowercase characters as shown below: :csp:UNIT HV;:CollectorSupply:hv:MOD AC In the instrument, the response message unit created corresponding to the query is composed of only data part without header. The mnemonic of the data part of the response message that the instrument sends is always upper-case.

― 22 ―

2.1.8 Data Format a. /

As with header mnemonics, and are data are formed from a combination of ASCII codes for A to Z, 0 to 9, and an underscore (_).

:CSP:UNI HV;:CSP:HV:MOD LEAK In this example, HV and LEAK, which are the parameters for the :CSP:UNI

command and the :CSP:HV:MOD command respectively, serve as the . Similar to mnemonic in the header part, it can include uppercase and lowercase characters. The instrument always creates uppercase for the .

b. /

Numerical data can be formatted as an integer (NR1), real number (NR2), or exponent (NR3). If the message is described in the form of ":STP:OFF 100E-3", "100E-3" corresponds to the numeric program data. The following numerical values are all interpreted as identical values.

0.1 ＝ 100E-3 ＝ 1e-1 ＝ 10E-2 ＝ 100e-3 In addition, the instrument does not support the suffix showing the physical unit itself;

e.g., "V (volts)" and "Hz (hertz)" and the suffix showing the multiplier for the unit; e.g., m (milli) and k (kilo). The received by the instrument can have any of the formats listed below.

The format of the mantissa part is shown below.

Exponential partSpace Mantissa part

＋

－

Number Number.

NumberNumber .

― 23 ―

The format of the exponential part is shown below. Remarks: Space or blank in the above format includes defined in

IEEE Std.488.2. sent by the instrument can have any of the formats listed

below. NR1 (Integer) type NR2 (Real number) type NR3 (Exponent) type c.

This data is response data created by the instrument composed of text characters including ASCII characters not allowed in and . If a new query message unit exits between the query returning and delimiter, the response is not created for such query and this state is determined as a query error.

d.

the instrument receives is as follows:

Blank

E

e

＋

－

Number

＋

－ Number Number

＋

－ Number Number. Number

＋

－ Number Number. Number E

＋

－ Number

― 24 ―

Data delimited by single or double quotation marks (') or (") is processed as

. If two delimiters ((') or (")) are written continuously in , they are recognized as one delimiter. All 7-bit JIS code characters can be used in . However, if a character not permitted for each command is included, the command error occurs.

Important: The range of the instrument can interpret is as follows: a. Integer format (NR1)

Numeric values from -2,147,483,647 to +2,147,483,647 can be used. Any value out of the range causes the command error to be returned.

b. Real number format (NR2)

Numeric values with part above the decimal point (integer part) from -2,147,483,647 to +2,147,483,647 can be used. Any value out of the range causes the command error to be returned.

c. Exponent format (NR3)

Mantissa part : Numeric values from -2,147,483,647 to +2,147,483,647 can be used. Any value out of the range causes the command error to be returned.

Exponent part : Values from -24 to +24 are available. Any value out of the range causes the command error to be returned.

Numeric value range : If the received value satisfies the conditions above and the value is out of range from -2,147,483,647 to +2,147,483,647 when being converted into the real number, the value is rounded to the upper limit value or the lower limit value.

Insert'

'Character other than

' ' '

Insert"

"Character other than

" " "

― 25 ―

For the query which returns of the instrument, if a value corresponding to the response data cannot be returned, NAN (None Numeric Value) is returned. NAN is 9.91E+37.

― 26 ―

2.2 Status Report Structure

2.2.1 Service Requests (SRQ) The instrument issues the service request by such factors as completed action and occurrence of various errors. To identify the cause of the service request, the controller must execute a serial poll or read the internal status register of the instrument.

― 27 ―

2.2.2 Status Byte Register Reading by serial poll or *STB? query is possible. This register is the last stage of the hierarchical status information on the instrument. This register consists of 8 bits; these bits have the following contents. (Bit 7) The instrument does not use bit 7 of the status byte register.

Bit 7 is always set to 0. RQS (Bit 6) When serial polling is executed, a message is returned as bit 6 of the

status byte of serial poll response. A message is generated when other bits in the status byte register (ESB, MAV, CPSB, DESB) are masked by the service request enable register, and consequently, the logical sum of all bits is changed from 0 to 1. RQS is cleared when the logical sum described above is changed from 1 to 0, the power is turned on, or serial polling is executed.

MSS (Bit 6) A message is returned as bit 6 of the *STB? query response.

MSS connects the logical sum of all bits when other bits in the status byte register (ESB, MAV, CPSB, DESB) are masked by the service request enable register.

ESB (Bit 5) A message is returned as bit 5 of the serial poll or *STB? query response.

This is a summary message connected to the standard event status register.

MAV (Bit 4) A message is returned as bit 4 of the serial poll or *STB? query response.

This is a summary message connected to the output queue. (Bit 3) The instrument does not use bit 3 of the status byte register.

Bit 3 is always set to 0. (Bit 2) The instrument does not use bit 2 of the status byte register.

Bit 2 is always set to 0. (Bit 1) The instrument does not use bit 1 of the status byte register.

Bit 1 is always set to 0. MEV (Bit 0) A message is returned as bit 0 of the serial poll *STB? query response.

This is a summary message connected to the measurement event status xbyte.

― 28 ―

2.2.3 Service Request Enable Register The service request enable register masks the status byte register. A message is returned to the RQS or MSS bit, depending on the result of masking. Therefore, conditions for service request issue can be controlled. If the corresponding bit in the enable register is set to 1, the corresponding event is enabled (factor to generate the service request), and if set to 0, the event is disabled (not the factor). The mask pattern is can be set using the *SRE command and read using the *SRE? query. Whether or not the contents of this register are cleared (to 0) as the power is turned on is set using the *PSC command. This does not directly affect the device clear and the *CLS command. Status byte resister structure

0 MAV MEVESB 0 00

RQS

MSS

Not used

Standard event status

This reflects the output queue

Measurement event status

This is read by the serial pole

Status byte register

This is read by *STB? query

Service request enable register

This is set by *SRE command and

read by *SRE? query

ANDAND AND

OR

ＸＸＸＸＸ

Not usedNot used

Not used

― 29 ―

2.2.4 Standard Event Status Register This register can be read using the *ESR? query. After the contents of this register are masked by the standard event status enable register, the logical sum of all bits is connected to the ESB bit of the status byte register. The contents of this register are cleared (that is, set to 0) when the register is read using the *CLS command or *ESR? query. This register consists of 8 bits, and each bit has the following contents. PON (Bit 7) After the power is turned on, this bit is set to 1. (Bit 6) The instrument does not use bit 6.

Bit 6 is always set to 0. CME (Bit 5) If a command error occurs, this bit is set to 1.

This indication shows that some error exists in the command syntax. EXE (Bit 4) If an execution error occurs, this bit is set to 1.

This indication shows that the command cannot be executed or could not be completely normally.

DDE (Bit 3) If a device-specific error occurs, this bit is set to 1.

It is the summary message of the device-specific error event status register.

QYE (Bit 2) If a query error occurs, this bit is set to 1.

This indication shows that an error occurs when the controller attempts to read the message from the instrument without sending the query command, or the next message is sent before the response message has not been completely read.

(Bit 1) The instrument does not use bit 1.

Bit 1 is always set to 0. OPC (Bit 0) When the operation is completed, this bit is set to 1.

This bit supports the *OPC-command-based controller-device synchronization.

― 30 ―

2.2.5 Standard Event Status Enable Register The standard event status enable register masks the standard event status register. A message is returned to the ESB bit of the status byte register, depending on the results of masking. If the corresponding bit in the enable register is set to 1, the corresponding event is enabled (reflected on ESB bit in the status byte register), and if set to 0, the event is disabled (not reflected). The mask pattern can be set using the *ESE command and read using an *ESE? query. Whether or not the contents of this register are cleared (to 0) as the power is turned on is set using the *PSC command. This does not directly affect the device clear and the *CLS command. Standard event status The command error occurs on the instrument if: - The command being sent does not exist. - The parameter of the sent command has the number different from specified number. - The parameter of the sent command has the format different from specified format.

0 OPCCME PON EXE DDE QYE 0

ANDANDANDAND

Ｘ

AND AND

ＸＸ

OR

Power ON

Command error

Execution error

Unit specific error

Query error

Operatin completion

Standard event status register

This is read by *ESR? query

Standard event status enable register

This is set by *ESE command and

read by *ESE? query

Not used

To ESB bit of the status byte register

Not used

― 31 ―

2.2.6 Output Queue The output queue is an output buffer in which the response message to the controller is stored. Appropriate response messages are stored in the output queue, depending on the type of query. The MAV bit of the status byte register is set to 1 so long as data of one byte or greater exists in the output queue. The contents of this output queue are cleared (that is, set to 0) when the power is turned on or the device clear command is executed. When the output queue is not empty and a new program message is sent before the controller reads all the data bytes, a query error occurs and the contents of the output queue are also cleared.

― 32 ―

2.2.7 Device-Specific Error Condition Status Register It is the register to report the abnormal state of the instrument and can be read by :DECR? query. This register is used to know the latest state. If change in each abnormal state is received by SRQ, use the device-specific error event status register (and enable register). This register consists of 8 bits, and each bit has the following contents. (Bit 7) This bit is not used in the instrument. This bit is normally set at "0". (Bit 6) This bit is not used in the instrument. This bit is normally set at "0". (Bit 5) This bit is not used in the instrument. This bit is normally set at "0". (Bit 4) This bit is not used in the instrument. This bit is normally set at "0". LIM (Bit 3) When the limiter is set to the collector supply because of Overdrive, 1 is

read out. In the normal state, 0 is read out. OH (Bit 2) When Overheat state occurs (temperature rising in the instrument), 1 is

read out. In the normal state, 0 is read out. OL2 (Bit 1) When the collector supply output is limited because of Overload (over

current), 1 is read out. In the normal state, 0 is read out. OL1 (Bit 0) When the collector supply output is forcibly set to 0.0 % because of

Overload (over current), 1 is read out. In the normal state, 0 is read out.

― 33 ―

2.2.8 Device-Specific Error Event Status Register It is the register to report change in the abnormal state of the instrument. This register can be read using the :DEER? query. This register is used when the service request is issued because of change in abnormal state. To acquire the latest abnormal state, use the device-specific error condition status register instead of this register. After the contents of this register are masked by the device-specific error event status enable register, the logical sum of all bits is connected to the DDE bit of the standard event status register. The contents of this register are cleared (that is, set to 0) when the register is read using the *CLS command or :DEER? query. This register consists of 8 bits, and each bit has the following contents. (Bit 7) This bit is not used in the instrument. This bit is normally set at "0". (Bit 6) This bit is not used in the instrument. This bit is normally set at "0". (Bit 5) This bit is not used in the instrument. This bit is normally set at "0". (Bit 4) This bit is not used in the instrument. This bit is normally set at "0". LIM (Bit 3) When LIM bit in DECR register is changed: i.e., 0 ⇒ 1 or 1 ⇒ 0, 1 is set. OH (Bit 2) When OH bit in DECR register is changed: i.e., 0 ⇒ 1 or 1 ⇒ 0, 1 is set. OL2 (Bit 1) When OL2 bit in DECR register is changed: i.e., 0 ⇒ 1 or 1 ⇒ 0, 1 is set. OL1 (Bit 0) When OL1 bit in DECR register is changed: i.e., 0 ⇒ 1 or 1 ⇒ 0, 1 is set.

― 34 ―

2.2.9 Device-Specific Error Event Status Enable Register The device-specific error event status enable register masks the device-specific error event status register. A message is returned to the DDE bit of the standard event status register, depending on the results of masking. If the corresponding bit in the enable register is set to 1, the corresponding event is enabled (reflected on DDE bit in the standard event status register), and if set to 0, the event is disabled (not reflected). The mask pattern can be set using the :DEEE command and read using an :DEEE? query. Whether or not the contents of this register are cleared (to 0) as the power is turned on is set using the *PSC command. This does not directly affect the device clear and the *CLS command.

The DDE bit of the standard event status register

OR

ANDANDANDAND

LIM bit changes in DECR register

OH bit changes in DECR register

OL2 bit changes in DECR register

OL1 bit changes in DECR register

Device-Specific Error Event Status Register

This is read by DEER? query

Device-Specific Error Event Status Enable Register

This is set by DEEE command and

read by DEEE? query

Not used

0 0 0 LIM OH OL20 OL1

ＸＸＸＸ

Not used Not used Not used

― 35 ―

2.2.10 Measurement Condition Status Register It is the register to report the measurement state of the instrument and can be read by :MCSR? query. This register is used to know the latest state. If change in each measurement state is received by SRQ, use the measurement event status register (and the enable register). This register consists of 8 bits, and each bit has the following contents. (Bit 7) This bit is not used in the instrument. This bit is normally set at "0". (Bit 6) This bit is not used in the instrument. This bit is normally set at "0". (Bit 5) This bit is not used in the instrument. This bit is normally set at "0". (Bit 4) This bit is not used in the instrument. This bit is normally set at "0". HCB (Bit 3) When the breaker for HIGH CURRENT output of the collector supply is

disconnected, 1 is read out. In the normal state, 0 is read out. HVB (Bit 2) When the breaker for HIGH VOLTAGE output of the collector supply is

disconnected, 1 is read out. In the normal state, 0 is read out. ITL (Bit 1) When the interlock occurs, 1 is read out. In the normal state, 0 is read out. (Bit 0) This bit is not used in the instrument. This bit is normally set at "0".

― 36 ―

2.2.11 Measurement Event Status Register It is the register to report change in measurement state of the instrument. This register can be read using the :MESR? query. This register is used when the service request is issued because of change in measurement state. To acquire the latest measurement state, use the measurement condition status register instead of this register. After the contents of this register are masked by the measurement event status enable register, the logical sum of all bits is connected to the MEV bit of the status byte register. The contents of this register are cleared (that is, set to 0) when the register is read using the *CLS command or :MESR? query. This register consists of 8 bits, and each bit has the following contents. (Bit 7) This bit is not used in the instrument. This bit is normally set at "0". (Bit 6) This bit is not used in the instrument. This bit is normally set at "0". (Bit 5) This bit is not used in the instrument. This bit is normally set at "0". (Bit 4) This bit is not used in the instrument. This bit is normally set at "0". HCB (Bit 3) When HCB bit in MCSR register is changed: i.e., 0 ⇒ 1 or 1 ⇒ 0, 1 is set. HVB (Bit 2) When HCB bit in MCSR register is changed: i.e., 0 ⇒ 1 or 1 ⇒ 0, 1 is set. ITL (Bit 1) When ITL bit in MCSR register is changed: i.e., 0 ⇒ 1 or 1 ⇒ 0, 1 is set. SDR (Bit 0) If SWEEP measurement or SINGLE measurement finishes, 1 is set.

― 37 ―

2.2.12 Measurement Event Status Enable Register The measurement event status enable register masks the measurement event status register. A message is returned to the MEV bit of the status byte register, depending on the results of masking. If the corresponding bit in the enable register is set to 1, the corresponding event is enabled (reflected on MEV bit in the status byte register), and if set to 0, the event is disabled (not reflected). The mask pattern can be set using the :MESE command and read using an :MESE? query. Whether or not the contents of this register are cleared (to 0) as the power is turned on is set using the *PSC command. This does not directly affect the device clear and the *CLS command.

The MEV bit of the status byte register

OR

ANDANDANDAND

HCB bit changes in MCSR register

HVB bit changes in MCSR register

ITL bit changes in MCSR register

Measurement completion

Measurement Event Status Register

This is read by MESR? query

Measurement Event Status Enable Register

This is set by MESE command and

read by MESE? query

Not used

0 0 0 HCB HVB ITL0 SDR

ＸＸＸＸ

Not used Not used Not used

― 38 ―

2.3 Command List

The command list in this section shows all commands the instrument supports. Commands are grouped and listed in each classification table. - (?) in the table indicates that there is a corresponding query. - Uppercase command name indicates the short format. - Functions of commands in short and long formats are the same.

One message unit can include short and long format commands. - If a model name is written in the remarks of the table, it indicates that command/query

are available only for the model in it

Table 2-1 Common Commands

Function Parent command Sub command

1 Sub command

2 Remarks Explanation

page

Device-specific information reading out

*IDN? 45

Reset *RST 46

Completed action *OPC(?) 47

Wait *WAI 48

Status register clear *CLS 49

Event status register enable *ESE(?) 50

Event status register reading out

*ESR? 52

Powering on enable register clear

*PSC(?) 53

Status register enable *SRE(?) 54

Status byte reading out *STB? 56

Manual trigger *TRG 58

Panel setting recall *RCL 59

Panel setting saving *SAV 60

Test *TST? 61

― 39 ―

Table 2-2 Device-Specific Status Byte Control-Related


1 Sub command


page

Device-specific error condition status register reading out

DECR? 63

Device-specific error event status register reading out

DEER? 64

Device-specific error event status enable register setting

DEEE(?) 65

Measurement condition status register reading out

MCSR? 67

Measurement event status register reading out

MESR? 68

Measurement event status enable register setting

MESE(?) 69

Table 2-3 Step Generator Control Related


1 Sub command


page

Output mode setting MODe(?) 71

Output source setting SouRCe(?) 72

Voltage output range setting VOLtage(?) 73

Current output range setting CURrent(?) 75

Output polarity setting POLarity(?) 77

No. of steps setting NUMber(?) 78

Offset setting OFFset(?) 79

Sweep measurement resolution setting

SWeepSTeps(?) 80

Offset mode setting OFfsetMoDe(?) 81

Output 1/10 setting DIV10(?) 82

Pulse width setting PulseWIDth(?) 83

Measurement point setting

STeP

PulsePOInt(?) 85

― 40 ―

Table 2-4 Collector Supply Control-Related


1 Sub command


page

Output unit setting UNIt(?) 86

Output variable setting VARiable(?) 88

Hardware looping setting LOopingHard(?) 89

Software looping setting LOoPingSoft(?) 90

No. of SWEEP measurement points setting

SWeepSTeps(?) 91

HV output mode setting MODe(?) 92

HV output polarity setting POLarity(?) 94

HV output peak voltage setting

PKVolt(?) 95

HV output peak power setting PKPower(?) 97

HV output cycle setting

HV

FREquency(?) 98

HC output polarity setting POLarity(?) CS-3200,3300 99

HC output peak voltage setting

PKVolt(?) CS-3200,3300 100

HC output peak power setting PKPower(?) CS-3200,3300 101

HC output pulse interval setting

CollectorSuPply

HC

InTerVal(?) CS-3200,3300 103

― 41 ―

Table 2-5 Screen Display Control-Related


1 Sub command


page

Waveform drawing mode setting

VECtor(?) 105

Averaging status setting STAtus(?) 106

No. of averaging times settingAVErage

COUnt(?) 107

Persistence display status setting

STAtus(?) 108

Persistence display length setting

PERsist LENgth(?) 109

REF waveform display status setting

STAtus(?) 110

REF waveform display No. setting

REFview NUMber(?) 111

Reverse display setting INVert(?) 113

Vertical axis zoom setting VERtical(?) 114

Horizontal zoom setting ZOoM

HORizontal(?) 115

Vertical axis position setting VERtical(?) 116

Horizontal axis position setting POSition

HORizontal(?) 118

Vertical axis source/sense setting

VERtical(?) 120

Horizontal axis source/sense setting

HORizontal(?) 122

Waveform display mode setting

VIEwmode(?) 124

Wave1st display waveform type/sense setting

W1(?) 125

Wave2nd display waveform type/sense setting

DISplay

WAVe W2(?) 127

― 42 ―

Table 2-6 Cursor Control-Related


1 Sub command


page

Cursor mode setting MODe(?) 129

Setting of display update interval for cursor measurement result

RATe(?) 130

DOT cursor position (step) setting

STeP(?) 131

DOT cursor position (index) setting

InDeX(?) 132

fLINE cursor outer frame position setting

OUTer(?) 133

WINDOW cursor upper side position setting

UP(?) 135

WINDOW cursor lower side position setting

LOW(?) 136

WINDOW cursor right side position setting

Right(?) 137

WINDOW cursor left side position setting

WINdow

Left(?) 138

Cursor measurement value (X, Y) acquisition

XY? 140

fLINE cursor measurement value acquisition

FLINe? 141

Cursor measurement value (β/gm) acquisition

CURsor

BGM? 142

Table 2-7 System Control-Related


1 Sub command


page

Beep sound status setting BEeP(?) 143

Powering on setup state setting

poweronDEF(?) 144

External output status setting STAtus(?) 145

External output voltage level setting

AUX VOLt(?) 146

Date and time setting

SYStem

DATe(?) 147

― 43 ―

Table 2-8 Display Illumination Control-Related


1 Sub command


page

Waveform illumination setting TRaCe(?) 149

Grid illumination setting GRId(?) 150

Cursor illumination setting CURsor(?) 151

REF waveform illumination setting

REF(?) 152

Backlight illumination setting

INTen

LIGht(?) 153

Table 2-9 Configuration Control


1 Sub command


page Configuration setting CONfig(?) 154

Table 2-10 Measurement Control


1 Sub command


page Measurement mode setting MEAsure(?) 155

Table 2-11 Data Saving-Related


1 Sub command


page

Setup saving SETup 157

Measurement waveform saving

TRaCe 159

REF waveform saving

SAVe

REF 160

Screen hard copy saving COPy 161

Table 2-12 Data Recall-Related


1 Sub command


page

Setup recalling SETup 163

Measurement waveform recalling

TRaCe 165

REF waveform recalling

ReCaLl

REF 166

― 44 ―

Table 2-13 Data Deletion-Related


1 Sub command


page

Setup deletion SETup 167

Measurement waveform deletion

TRaCe 169

REF waveform deletion

DELete

REF 170

Table 2-14 Data Transfer-Related


1 Sub command


page

Transfer format setting (adapting to DTWAVE)

DTFORM(?) 172

Setup transfer DTSET(?) 173

Waveform data transfer DTWAVE? 174

Waveform information transfer DTINFO? 176

Screen hard copy transfer DTCOPY? 177

― 45 ―

2.4 Common Commands

This section describes the commands defined in the IEEE Std.488.2 standard, which are built-into the instrument. Asterisk is attached at the beginning of the command.

2.4.1 *IDN? (Device Information Reading Out) The instrument can be recognized through the system interface using the *IDN? query. ■ Query Query syntax

*IDN? Response message [VenderID],[Model],[SerialNo.],[SoftVer]

[VenderID],[Model] in format, [SerialNo.] in format, and [SoftVer] in format are returned. The response consists of 4 fields delimited by comma and contents of each field are as follows: Field 1 Manufacturer name IWATSU Field 2 Model name CS-3x00 (x is 0 to 9) Field 3 Serial number 0 to 4095 Field 4 Firmware level ASCII numeric value ( format)

Remarks

For the response data, 4 fields compose format.

― 46 ―

2.4.2 *RST (Reset) When the instrument receives *RST command, it initializes the internal setup to the specified values. For setup specified values, see "Default Setting" in the Instruction Manual. However, it does not initialize "settings not to be recalled" including remote-related settings (e.g., IP address for LAN). ■ Command Command syntax

*RST

― 47 ―

2.4.3 *OPC/*OPC? (Completed Action) When the instrument receives the *OPC command, it sets the operation completion message (OPC bit) of the standard event status register to "1" after the operation of the devices, which are specified by commands and queries sent before this command, has been completed. It can be used not only for detecting the completed action of a usual command but also for the measurement action setting command on the instrument for the purpose below: It may take much time to finish measurement in SWEEP measurement mode or SINGLE measurement mode. *OPC command allows you to detect the timing of finishing measurement. (If the measurement finishes when *OPC command is received, 1 is set.) When the instrument receives the *OPC? query, it stores the ASCII character "1" into the output queue instead of setting of the OPC bit (the ASCII character "1" is not set in the standard event status register). If *OPC? query is sent once, the response message to finish the measurement using the measurement action setting command is not returned. Therefore, if the measurement action setting command is sent, send *OPC? query command finally. ■ Command Command syntax

*OPC ■ Query Query syntax

*OPC? Response message 1

The response message is "1" in the format.

― 48 ―

2.4.4 *WAI (Wait) When the instrument receives the *WAI command, it holds the execution of subsequent commands and queries until the operation of the devices, which are specified by commands and queries sent before this command, has been completed. ■ Command Command syntax

*WAI

― 49 ―

2.4.5 *CLS (Status Register Clear) *CLS command clears registers below of the instrument. - Standard event status register - Measurement event status register - Device-specific error event status register Furthermore, it clears the summary bit in the status byte register which reflects the contents of this register. ■ Command Command syntax

*CLS

― 50 ―

2.4.6 *ESE/*ESE? (Event Status Register Enable Setting) The *ESE command is used to set each bit of the standard event status enable register. It is possible to obtain the current contents of the standard event status enable register using the *ESE? query. ■ Command Command syntax

*ESE [Mask setting] [Mask setting] is a parameter to set the standard event status enable register and is a numeric value ranging from "0" to "255" in the format. One meaning is assigned to each bit of the standard event status register. If the corresponding bit in the enable register is set to 1, the corresponding event is enabled (reflected on ESB bit in the status byte register), and if set to 0, the event is disabled (not reflected).

Error If any value out of the setting range is set, the value is rounded down within the setting range and the execution error is returned. In addition, if the value below the resolution within the setting range is set, the value is rounded down to the resolution. An error does not occur.

■ Query Query syntax

*ESE?

Response message [Mask] [Mask] is the numeric value in format which is obtained by weighting the value of each bit in the standard event status enable register by exponentiation of "2". Range: 0 to 189.

― 51 ―

Remarks Structure of standard event status enable register Bit Weighting Meaning 7 128 PON-Power ON 6 64 (URQ)-Not used in the instrument 5 32 CME-Command error 4 16 EXE-Execution error 3 8 DDE-Device specific error 2 4 QYE-Query error 1 2 (RQC)-Not used in the instrument 0 1 OPC-Operation complete The instrument does not use bit 1 and 6. Therefore, even though all bits of this register are set at "1", the maximum value of the response message becomes 189 (=255-64-2).

― 52 ―

2.4.7 *ESR? (Event Status Register Reading Out Setting) It is possible to obtain the current contents of the standard event status register using the *ESR? query. When the contents of the standard event status register are read, they are then cleared. ■ Query Query syntax

*ESR?

Response message [Status] [Status] is the numeric value in format which is obtained by weighting the value of each bit in the standard event status register by exponentiation of "2". Range: 0 to 189.

Remarks Structure of standard event status register Bit Weighting Meaning 7 128 PON-Power ON 6 64 (URQ)-Not used in the instrument 5 32 CME-Command error 4 16 EXE-Execution error 3 8 DDE-Device specific error 2 4 QYE-Query error 1 2 (RQC)-Not used in the instrument 0 1 OPC-Operation complete The instrument does not use bit 1 and 6. Therefore, even though all bits of this register are set at "1", the maximum value of the response message becomes 189 (=255-64-2).

― 53 ―

2.4.8 *PSC/*PSC? (Powering On Enable Register Clear Setting) *PSC command controls the automatic clear at powering on 4 enable registers below: - Service request enable register - Standard event status enable register - Measurement event status enable register - Device-specific error event status enable register The values set by the *PSC command can be obtained using the *PSC? query. If the value of the response data is "0", the status of each enable register is retained even while the power is off. If the value of the response data is "1", this shows that each of above enable registers is cleared when the power is turned on again.

■ Command Command syntax

*PSC [PSC flag setting] [PSC flag setting] is the parameter to set the power-on status clear flag and uses numeric values from 0 to 1 in format. When [psc_flag_arg] is set at "0", the status of each enable register is retained even while the power is turned off. When [psc_flag_arg] is set at "1" (value other than "0"), each enable register is cleared when the power is turned on again.



*PSC?

Response message [PSC flag] [PSC flag] is a numeric value showing the contents of the power on status clear flag and is normally "0" or "1" in the format.

― 54 ―

2.4.9 *SRE/*SRE? (Status Register Enable Setting) The *SRE command is used to set each bit of the service request enable register. It is possible to obtain the current contents of the service request enable register using the *SRE? query. ■ Command Command syntax

*SRE [Mask setting] [Mask setting] is a parameter to set the service request enable register and is a numeric value ranging from "0" to "255" in the format. One meaning is assigned to each bit of the service request enable register. If the corresponding bit in the enable register is set to 1, the corresponding event is enabled (this causes the service request to occur), and if set to 0, the event is disabled (this does not cause the service request to occur).



*SRE?

Response message [Mask] [Mask] is the numeric value in format which is obtained by weighting the value of each bit in the service request enable register by exponentiation of "2". Range: 0 to 49.

― 55 ―

Remarks Structure of service request enable register Bit Weighting Meaning 7 128 CS3X00-Since the instrument does not use this bit, the

bit is always set at "0". 6 64 RQS/MSS-Request service/message summery status 5 32 ESB- Standard event status 4 16 MAV-Message available 3 8 CS3X00-Since the instrument does not use this bit, the

bit is always set at "0". 2 4 CS3X00-Since the instrument does not use this bit, the


bit is always set at "0". 0 1 MEV-Measurement event status The response data is created assuming that bit 6 is always "0" regardless of the designation of the *SRE command parameter. However, note that this bit is always determined as enable during actual operation. The instrument does not use bits 1 to 3 and bit 7. Since bit 6 is always regarded as 0, the maximum value of the response message is 49 (=32+16+1) even if all bits are set to 1.

― 56 ―

2.4.10 *STB? (Status Byte Reading Out) The status byte and master summery status bit (MSS message) can be read using the *STB? query. ■ Query Query syntax

*STB?

Response message [Status] [Status] is the numeric value in format which is obtained by weighting the value of each bit in the status byte register by exponentiation of "2". Range: 0 to 113.

Remarks Structure of status byte register Bit Weighting Meaning 7 128 CS3X00-Since the instrument does not use this bit, the

bit is always set at "0". 6 64 RQS/MSS-Request service/message summery status 5 32 ESB-Summary of standard event status 4 16 MAV-Message available 3 8 CS3X00-Since the instrument does not use this bit, the



bit is always set at "0". 0 1 MEV- Summary of measurement event status The instrument does not use bit 1 to 3 and bit 7. Therefore, even though all bits of this register are set at "1", the maximum value of the response message becomes 113 (=64+32+16+1). When the contents of the status byte register are read using the *STB? query, the MSS message is used for bit 6 instead of RQS in conformity with the IEEE Std.488.2 standard. Other bits become the same values read by the serial polling. The MSS message is obtained by logical OR of all bits except for bit 6 after the contents of the status byte register are masked (logical AND) according to the contents of the service request enable register.

― 57 ―

The RQS message is basically retained in the status byte register until the serial polling is performed. On the contrary, the MSS message affects the internal status of the device at real-time.

― 58 ―

2.4.11 *TRG (Manual Trigger) *TRG command executes the measurement in SINGLE measurement mode. It is ignored in other than SINGLE measurement mode (no execution error occurs). ■ Command Command syntax

*TRG

― 59 ―

2.4.12 *RCL (Panel Setting Recall) The setup file saved in the internal memory of the instrument can be recalled using the *RCL [Memory number specification] command. ■ Command Command syntax

*RCL [Memory number specification] [Memory number specification] is used to specify a parameter for setting of the memory No. to be recalled and is a numeric value ranging from "0" to "256" in the format. However, if 0 is set, the inner setup is initialized to the specified values, similar to *RST command and :ReCaLl:SETup DEF command. A numeric value corresponding to the memory No. to be selected for the save/recall operation of the local operation is specified.

Error If the value obtained by rounding down [Memory number specification] to the integer is less than 0 or exceeds 256, the execution error occurs and recall action is not carried out. If the memory number not saving the setup data is set when the value obtained by rounding down [Memory number specification] to the integer is 1 to 256, the execution error occurs and recall action is not carried out.

― 60 ―

2.4.13 *SAV (Panel Setting Saving) The panel specification is saved into the internal memory of the instrument using the *SAV [Memory number specification] command. ■ Command Command syntax

*SAV [Memory number specification] [Memory number specification] is used to specify a parameter for setting of the memory No. to be save and is a numeric value ranging from "1" to "256" in the format. A numeric value corresponding to the memory No. to be selected for the save/recall operation of the local operation is specified.

Error If the value obtained by rounding down [Memory number specification] to the integer is less than 1 or exceeds 256, the execution error occurs and save action is not carried out.

― 61 ―

2.4.14 *TST? (Test) *TST? query performs the simple system test of the instrument. ■ Query Query syntax

*TST?

Response message [TestResult] [TestResult] is the numeric value indicating the result of the simple system test: i.e., 0 or 1 in format. 0: Normal, 1: Abnormal

― 62 ―

2.5 Hardware-Specific Commands

This section describes the hardware specific commands built-into the instrument. In addition, for common command prescribed by IEEE Std.488.2, see "2.4 Common Commands". Common items - For the command whose parameter is , if a value

exceeding the range is set, the value is rounded down within the range and the execution error is returned.

- For the command whose parameter is , if a parameter not to be selected is set, the command is ignored; i.e., command error.

― 63 ―

2.5.1 Device-Specific Status Byte Control-Related

2.5.1.1 DECR? Query (Device-Specific Error Condition Status Register Reading Out) It is possible to obtain the current contents of the device-specific error condition status register using the :DECR? query. ■ Query Query syntax

:DECR?

Response message [Status] [Status] is the numeric value in format which is obtained by weighting the value of each bit in the device-specific error condition status register by exponentiation of "2". Range: 0 to 15.

Remarks Structure of device-specific error condition status register Bit Weighting Meaning 7 128 Not used in the instrument (Always 0) 6 64 Not used in the instrument (Always 0) 5 32 Not used in the instrument (Always 0) 4 16 Not used in the instrument (Always 0) 3 8 LIM State where limiter is set because of

Overdrive 2 4 OH Overheat state (temperature increase in

instrument) 1 2 OL2 State where the collector supply output is

limited because of Overload (over current) 0 1 OL1 State where the collector supply output is

forcibly set to 0.0 % because of Overload (over current)

The instrument does not use bit 4 to 7. Therefore, even though all bits of this register are set at "1", the maximum value of the response message becomes 15 (=8+4+2+1).

― 64 ―

2.5.1.2 DEER? Query (Device-Specific Error Event Status Register Reading Out) It is possible to obtain the current contents of the device-specific error event status register using the :DEER? query. When the contents of the device-specific error event status register are read, they are then cleared. ■ Query Query syntax

:DEER?

Response message [Status] [Status] is the numeric value in format which is obtained by weighting the value of each bit in the device-specific error event status register by exponentiation of "2". Range: 0 to 15.

Remarks Structure of device-specific error event status register Bit Weighting Meaning 7 128 Not used in the instrument (Always 0) 6 64 Not used in the instrument (Always 0) 5 32 Not used in the instrument (Always 0) 4 16 Not used in the instrument (Always 0) 3 8 LIM When LIM bit in DECR register is changed:

i.e., 0 ⇒ 1 or 1 ⇒ 0, 1 is set. 2 4 OH When OH bit in DECR register is changed:

i.e., 0 ⇒ 1 or 1 ⇒ 0, 1 is set. 1 2 OL2 When OL2 bit in DECR register is changed:

i.e., 0 ⇒ 1 or 1 ⇒ 0, 1 is set. 0 1 OL1 When OL1 bit in DECR register is changed:

i.e., 0 ⇒ 1 or 1 ⇒ 0, 1 is set. The instrument does not use bit 4 to 7. Therefore, even though all bits of this register are set at "1", the maximum value of the response message becomes 15 (=8+4+2+1).

― 65 ―

2.5.1.3 DEEE/DEEE? (Device-Specific Error Event Status Enable Register Setting) The :DEEE command is used to set each bit of the device-specific error event status enable register. It is possible to obtain the current contents of the device-specific error event status enable register using the :DEEE? query. ■ Command Command syntax

:DEEE [Mask setting] [Mask setting] is a parameter to set the device-specific error event status enable register and is a numeric value ranging from "0" to "255" in the format. One meaning is assigned to each bit of the command process status register. If the corresponding bit in the enable register is set to 1, the corresponding event is enabled (reflected on DDE bit in the standard event status register), and if set to 0, the event is disabled (not reflected).



:DEEE?

Response message [Mask] [Mask] is the numeric value in format which is obtained by weighting the value of each bit in the command process status enable register by exponentiation of "2". Range: 0 to 15.

― 66 ―

Remarks Structure of device-specific error event status enable register Bit Weighting Meaning 7 128 Not used in the instrument (Always 0) 6 64 Not used in the instrument (Always 0) 5 32 Not used in the instrument (Always 0) 4 16 Not used in the instrument (Always 0) 3 8 LIM Corresponding to LIM bit in DEER register 2 4 OH Corresponding to OH bit in DEER register 1 2 OL2 Corresponding to OL2 bit in DEER register 0 1 OL1 Corresponding to OL1 bit in DEER register The instrument does not use bit 4 to 7. Therefore, even though all bits of this register are set at "1", the maximum value of the response message becomes 15 (=8+4+2+1).

― 67 ―

2.5.1.4 MCSR? Query (Measurement Condition Status Register Reading Out) It is possible to obtain the current contents of the measurement condition status register using the :MCSR? query. ■ Query Query syntax

:MCSR?

Response message [Status] [Status] is the numeric value in format which is obtained by weighting the value of each bit in the measurement condition status register by exponentiation of "2". Range: 0 to 14.

Remarks Structure of measurement condition status register Bit Weighting Meaning 7 128 Not used in the instrument (Always 0) 6 64 Not used in the instrument (Always 0) 5 32 Not used in the instrument (Always 0) 4 16 Not used in the instrument (Always 0) 3 8 HCB State where the breaker for HIGH

CURRENT output of the collector supply is disconnected

2 4 HVB State where the breaker for HIGH VOLTAGE output of the collector supply is disconnected

1 2 ITL State where the interlock occurs 0 1 Not used in the instrument (Always 0) The instrument does not use bit 0 and bit 4 to 7. Therefore, even though all bits of this register are set at "1", the maximum value of the response message becomes 14 (=8+4+2).

― 68 ―

2.5.1.5 MESR? Query (Measurement Event Status Register Reading Out) It is possible to obtain the current contents of the measurement event status register using the :MESR? query. When the contents of the measurement event status register are read, they are then cleared. ■ Query Query syntax

:MESR?

Response message [Status] [Status] is the numeric value in format which is obtained by weighting the value of each bit in the measurement event status register by exponentiation of "2". Range: 0 to 15.

Remarks Structure of measurement event event status register Bit Weighting Meaning 7 128 Not used in the instrument (Always 0) 6 64 Not used in the instrument (Always 0) 5 32 Not used in the instrument (Always 0) 4 16 Not used in the instrument (Always 0) 3 8 HCB When HCB bit in MCSR register is changed:

i.e., 0 ⇒ 1 or 1 ⇒ 0, 1 is set. 2 4 HVB When HVB bit in MCSR register is changed:

i.e., 0 ⇒ 1 or 1 ⇒ 0, 1 is set. 1 2 ITL When ITL bit in MCSR register is changed:

i.e., 0 ⇒ 1 or 1 ⇒ 0, 1 is set. 0 1 SDR At the completion of measurement, 1 is set. The instrument does not use bit 4 to 7. Therefore, even though all bits of this register are set at "1", the maximum value of the response message becomes 15 (=8+4+2+1).

― 69 ―

2.5.1.6 MESE/MESE? (Measurement Event Status Enable Register Setting) The :MESE command is used to set each bit of the measurement event status enable register. It is possible to obtain the current contents of the measurement event status enable register using the :MESE? query. ■ Command Command syntax

:MESE [Mask setting] [Mask setting] is a parameter to set the measurement event status enable register and is a numeric value ranging from "0" to "255" in the format. One meaning is assigned to each bit of the device event status register. If the corresponding bit in the enable register is set to 1, the corresponding event is enabled (reflected on MEV bit in the status byte register), and if set to 0, the event is disabled (not reflected).



:MESE?

Response message [Mask] [Mask] is the numeric value in format which is obtained by weighting the value of each bit in the measurement event status enable register by exponentiation of "2". Range: 0 to 15.

― 70 ―

Remarks Structure of measurement event status enable register Bit Weighting Meaning 7 128 Not used in the instrument (Always 0) 6 64 Not used in the instrument (Always 0) 5 32 Not used in the instrument (Always 0) 4 16 Not used in the instrument (Always 0) 3 8 HCB Corresponding to HCB bit in MESR register 2 4 HVB Corresponding to HVB bit in MESR register 1 2 ITL Corresponding to ITL bit in MESR register 0 1 SDR Corresponding to SDR bit in MESR register The instrument does not use bit 4 to 7. Therefore, even though all bits of this register are set at "1", the maximum value of the response message becomes 15 (=8+4+2+1).

― 71 ―

2.5.2 Step Generator Control Related

2.5.2.1 STePgen:MODe/STePgen:MODe? :STePgen:MODe command sets the output mode of the step generator. :STePgen:MODe? query reads the current output mode of the step generator. ■ Command Command syntax

:STePgen:MODe [StepMode] [StepMode]

Contents STEP Step-shaped waveform PULSE Pulse wave

Error The following shows the linkage setting of the collector supply when setting the output mode of the step generator.

Collector supply Step generator Output unit Output mode STEP PULSE

AC Without interlock Without interlock SINE Without interlock Change to DC DC Change to SIN Without interlock

HV

LEAK Without interlock *1 Execution error *2 HC － Execution error *2 Without interlock *1 : The icon of the step generator output mode in the instrument displays DC. *2 : The setting is not executed.


:STePgen:MODe?

Response message [StepMode] [StepMode] is returned in format.

― 72 ―

2.5.2.2 STePgen:SouRCe/STePgen:SouRCe? :STePgen:SouRCe command switches current/voltage of the step generator output source. :STePgen:SouRCe? query reads the current output source of the step generator. ■ Command Command syntax

:STePgen:SouRCe [StepSource] [StepSource]

Contents CURRENT Voltage output VOLTAGE Current output

Error There is no error specific to this command.

Remarks When the output source of the step generator is switched, each range of VOLTAGE/C

Documents

Remote Control Manual Curve Tracer CS-3000 Series1].pdf · Remote Control Manual Curve Tracer CS-3000 Series . i Introduction Thank you for purchasing this Iwatsu’s instrument