9518-01
Instruction Manual
GB-IB INTERFACE
For 3532-50, 3522-50, 3511-50 LCR HiTESTER
Sept. 2018 Revised edition 10
9518A983-10 18-09H
EN
Contents
Introduction i
Chapter 1 Before Use 1
1.1 Check of External Appearance and Accessories 1
1.2 Shipping Precautions
1.3 Points for Attention During Use
1.4 Installing the GP-IB Interface
Chapter 2 Overview 5
2.1 Introduction to the 9518-01 GP-IB INTERFACE 5
2.2 Specifications
Chapter 3 Names of Parts 7
3.1 Controls and Connections 7
Chapter 4 Operation 9
4.1 Setting the GP-IB Device Address 9
4.2 Communication Methods by the GP-IB
4.3 Message Format
11
12
2
3
4
6
4.4 Headers 13
4.5 Data Formats
4.6 Message Terminators
4.7 Separators
4.8 Abbreviation of Compound Commands
4.9 Output Queue
4.10 Input Buffer
4.11 Status Model
4.12 Status Byte Register
4.13 Event Registers
4.14 GP-IB Commands
9518A983-10
4.3.1 Program Message 12
4.3.2 Response Messages 12
14
15
15
16
17
18
19
20
22
28
Chapter 5 Command Reference for the
3532-50/3522-50 29
5.1 Command Summary 30
5.2 Format of Command Explanations
5.3 Particular Commands
5.4 Commands Specific to the 3532-50/3522-50
5.5 Response Format for Queries as Numerical Value
5.6 Initialization Items
34
35
42
92
94
Chapter 6 Command Reference for 3511-50 95
6.1 Command Summary 95
6.2 Format of Command Explanations
6.3 Particular Commands
6.4 Commands Specific to the 3511-50
98
99
106
Chapter 7 Sample Programs 133
Chapter 8 Device Compliance Statement 145
Chapter 9 Troubleshooting 149
────────────────────────────────────────────────────
Introduction
Thank you for purchasing the HIOKI 9518-01 GP-IB INTERFACE for the
3532-50, 3522-50 and 3511-50 LCR HiTESTERs.
To obtain maximum performance from the product, please read this manual
first, and keep it handy for future reference.
This manual contains information and warnings essential for safe operation
of the product and for maintaining it in safe operating condition. Before
using the product, be sure to carefully read the following safety notes.
The following symbols in this manual indicate the relative importance of
cautions and warnings.
i
WARNING
CAUTION
NOTE
Indicates that incorrect operation presents a significant
hazard that could result in serious injury or death to
the user.
Indicates that incorrect operation presents a possibility
of injury to the user or damage to the product.
Advisory items related to performance or correct operation
of the product.
────────────────────────────────────────────────────
ii
────────────────────────────────────────────────────
────────────────────────────────────────────────────
1
────────────────────────────────────────────────────
Chapter 1
Before Use
1.1 Check of External Appearance and Accessories
When you receive the product, inspect it carefully to ensure that no damage
occurred during shipping.
In particular, check the accessories, panel switches, and connectors. If
damage is evident, or if it fails to operate according to the specifications,
contact your dealer or Hioki representative.
(1) 9518-01 GP-IB INTERFACE
(2) This instruction manual
────────────────────────────────────────────────────
1.1 Check of External Appearance and Accessories
2
────────────────────────────────────────────────────
1.2 Shipping Precautions
If reshipping the unit, preferably use the original packing.
If this is not available, use the following procedure.
1. Wrap the unit in plastic sheeting.
2. After wrapping cushioning material around the unit, pack it into a
cardboard box, and then seal up the box with adhesive tape.
────────────────────────────────────────────────────
1.2 Shipping Precautions
3
────────────────────────────────────────────────────
1.3 Points for Atte ntion During Use
(1) If you change the device address of the 3532-50/3522-50/3511-50 while
using it, you should immediately turn the power off and on again. If you do
not do so, the address change will not be registered by the bus, and problems
will occur.
(2) Always be sure to secure the GP-IB cable to the 9518-01 unit by tightening
up the fixing screws provided.
(3) Program messages sent just after the power has been turned on are executed
after the self test has terminated.
(4) It is vital that the proper data format is used when inputting commands with
data values to the 3532-50/3522-50/3511-50 unit.
(5) For details of the various functions, refer to the instruction manuals for the
3532-50/3522-50/3511-50 unit.
────────────────────────────────────────────────────
1.3 Points for Attention During Use
4
────────────────────────────────────────────────────
1.4 Installing the GP-IB Interface
WARNING
CAUTION
To avoid electric shock accident, before removing or replacing an input
module, confirm that the instrument is turned off and that the power cord
and connection cables are disconnected.
The mounting screws must be firmly tightened or the input unit may not
perform to specifications, or may even fail.
To avoid the danger of electric shock, never operate the product with an
input module removed. To use the product after removing an input
module, install a blank panel over the opening of the removed module.
When inserting in the interface, hold the metal plate. Directly touching the
board may cause static electricity and lead to damage of the instrument.
(Using the wrist strap for preventing static electricity when inserting is
recommended.)
The space for fitting the 9518-01 GP-IB INTERFACE in the rear panel of
the 3532-50/3522-50/3511-50 are covered with a blanking plate. Follow
these three steps to install the 9518-01 interface:
1. Remove the fixing screws, and take off the blanking plate.
2. Insert the 9518-01 GP-IB INTERFACE into the exposed slot in the rear of
the unit in the figure below.
3. Push the 9518-01 firmly into place, and fix with the screws removed in
step 1.
────────────────────────────────────────────────────
1.4 Installing the GP-IB Interface
5
────────────────────────────────────────────────────
Chapter 2
Overview
2.1 Introduction to the 9518-01 GP-IB INTERFACE
By connecting the 9518-01 GP-IB INTERFACE to the 3532-50/352250/3511-50, it is possible to control the main unit via the GP-IB bus. This
unit is compliance with the following standard.
NOTE
Compliance standard : IEEE 488.1-1987
Further, the 9518-01 is designed with reference to the following standard:
Reference standard : IEEE 488.2-1987
On the 9518-01, if the outp ut queue becomes full, i t is cleared and a
query error is generated. This differs from the IEEE 488.2 specificat ion,
which only stip ulates the clearin g of the output queue and the out putt ing
of a query error when a deadlock state occurs, that is, when both t he
input buffer and the out put queue have become full, and continuation of
processing has become impossible.
────────────────────────────────────────────────────
2.1 Introduction to the 9518-01 GP-IB INTERFACE
6
────────────────────────────────────────────────────
2.2 Specifications
Interface Functions
SH1
AH1
T6
L4
SR1
RL1
PP0
DC1
All source handshake functions
All acceptor handshake functions
Basic talk functions
Serial poll function
No talk-only mode
The talker cancellation function with MLA (My Listen
Address)
Basic listener functions
No listen-only mode
The listener cancellation function with MTA (My Talk
Address) is provided.
All service request functions
All remote/local functions
No parallel polling function
All device clear functions
DT1
C0
All device trigger functions
No controller function
ASCII codes are used.
────────────────────────────────────────────────────
2.2 Specifications
7
────────────────────────────────────────────────────
Chapter 3
Names of Parts
3.1 Controls and Connections
(1) 3532-50/3522-50 Initial Screen
LOCAL key
LOCAL key
During communications (in the remote state), the
remote state is displayed on the screen. Press this key to resume the normal
state (local state).
However, this key is disabled if the GP-IB controller has put the unit into
the local lock out state. (Pressing the key has no effect.)
In the remote state, the initial screen is forcibly displayed excluding the
following conditions.
･
When executing OPEN/SHORT correction or sending the execution
command (correction execution screen appears).
･
When the magnification display screen appears.
LOCAL
key to release the
────────────────────────────────────────────────────
3.1 Controls and Connections
8
A
────────────────────────────────────────────────────
(2) 9518-01 GP-IB INTERFACE outer panel
WARNING
In order t o prevent any danger of elec tr ic shock to the operator, check
carefull y th at the power c abl e a nd t he connect ors to the 3 532-50 /35 2250/3511-50 have been removed first, before c onne c ti ng t he GP-IB cable
to this connector.
ddress switches GP-IB connector
Address swi tches
These are used to set the device address of the 3532-50/3522-50 units on the
GP-IB bus. For how to set these switches, refer to Section 4.1, "Setting the
GP-IB Device Address."
GP-IB connector
Connect the GP-IB cable to this connector.
────────────────────────────────────────────────────
3.1 Controls and Connections
9
────────────────────────────────────────────────────
Chapter 4
Operation
4.1 Setting the GP-IB Device Address
･
The address of the 3532-50/3522-50/3511-50 units (called the device) on the
GP-IB bus can be set to any number from 0 to 30.
NOTE
･
Use the Address switches on the GP-IB panel to set the device address.
･
On dispatch from the factory, this address is initially set to 1.
･
If this address is (apparently) set to 31, i.e. if all the switches are in the ON
position, then the bus lines of the 3532-50/3522-50/3511-50 are disabled.
･
Always the Address switch for TALK ONLY is in the OFF position, since it
is not used.
If you change the bus address while the 3532-50, 3522-50 or 3511-50 is
being used, then you should i mmediat ely turn the power off and on again.
If this is not done, the address will not be ch a nged to the new one.
────────────────────────────────────────────────────
4.1 Setting the GP-IB Device Address
10
────────────────────────────────────────────────────
Address switches
Address
Switch settings
Address
Switch settings
Address
Switch settings
12345 12345 12345
0 00000 10 01010 20 00101
1 10000 11 11010 21 10101
2 01000 12 00110 22 01101
3 11000 13 10110 23 11101
4 00100 14 01110 24 00011
5 10100 15 11110 25 10011
6 01100 16 00001 26 01011
7 11100 17 10001 27 11011
8 00010 18 01001 28 00111
9 10010 19 11001 29 10111
0: OFF 1: ON 30 01111
────────────────────────────────────────────────────
4.1 Setting the GP-IB Device Address
11
────────────────────────────────────────────────────
4.2 Communication Methods by the GP-IB
･
In order to control the 3532-50/3522-50/3511-50 by the GP-IB, there are
several kinds of messages.
･
Of these, program messages are those received by the 3532-50/3522-
50/3511-50 from the computer, while response messages are those sent from
the 3532-50/3522-50/3511-50 to the computer.
Command messages
Program messages
Messages
Response messages
(1) Program messages
Program messages are command messages or query messages.
Query messages
･
Command messages
are orders for controls of the 3532-50/3522-50/
3511-50, such as for making measurement condition settings or for reset or
the like.
Example FREQUENCY
<data>
(Command message which sets the frequency)
･
Query messages
are orders for responses relating to results of operation,
results of measurement, or the state of 3532-50/3522-50/3511-50 settings.
(A question mark "?" is suffixed at the end of the command.)
Example FREQUENCY?
(Queries the current frequency)
(2) Response messages
It represents the response data for query messages from the 3532-50/352250/3511-50.
Example FREQUENCY 1.000E+03
(Current frequency is 1 kHz.).
Computer
Program messages
Response messages
────────────────────────────────────────────────────
4.2 Communication Methods by the GP-IB
3532-50/3522-50/3511-50
12
────────────────────────────────────────────────────
4.3 Message Format
The commands for the 3532-50/3522-50/3511-50 are as far as possible
mnemonic. Furthermore, all commands have a long form, and an
abbreviated short form.
4.3.1 Program Message
The program message is made up from header and data portions
Example
:
Command message to set frequency to 1 kHz
FREQUENCY 1000
1 2 3
1
Header portion
Space separating header portion and data portion.
2
3
Data portion (ASCII-format text or numeric values.
Some messages have no data portions...query messages, etc.)
A command header can be abbreviated. The whole command form is
referred to as the "long form" and the abbreviated form as the "short form."
In this manual, the short form is written in upper case letters, and then this
is continued in lower case letters so as to constitute the long form. Either of
these forms will be accepted during operation, but intermediate forms will
not be accepted. Further, during operation both lower case letters and upper
case letters will be accepted without distinction.
For "FREQUENCY", either "FREQuency" (the long form) or "FREQ" (the
short form) will be accepted. However, any one of "FREQU", or "FRE" is
wrong and will generate an error.
4.3.2 Response Messages
It represents the response message for query messages from the 353250/3522-50/3511-50.
Response messages generated by the 3532-50/3522-50/3511-50 are in long
form and in upper case letters.
Example FREQUENCY 1.000E+03
(Current frequency is 1 kHz.)
NOTE
────────────────────────────────────────────────────
4.3 Message Format
If an error occurs when the query message is received, the query does not
produce response message.
13
(
)
────────────────────────────────────────────────────
4.4 Headers
(1) Program message headers
There are three types of header: simple commands, compound commands,
and standard common commands.
･
Simple command header
A header consisting of a single word beginning with a letter.
Examples :HEADer
･
Compound command header
A header consisting of a sequence of words separated by colons.
Examples :BEEPer:KEY, RANGe:AUTO
･
Standard command header
A header begins with an asterisk (*) to indicate that it is a standard
command, and continues with a standard command stipulated by IEEE
488.2.
Examples
*
RST
, etc.
, etc.
, etc.
NOTE
(2) Response message
Headers in response messages can be enabled or disabled by using the
"HEADer" command.
Example
(Query message
When frequency is set to 1 kHz:
:FREQUENCY?
asking for the current setting of the frequency.
Response message when headers are on.
:FREQUENCY 1000
Headerportion)(Dataportion
Response message when headers are off.
(Data portion only)
1000
The headers are set to off when powering on.
)
────────────────────────────────────────────────────
4.4 Headers
14
────────────────────────────────────────────────────
4.5 Data Formats
The 3532-50/3522-50/3511-50 use character string data and decimal numeric
data, and the type used varies according to the command in question.
(1) Character data
Character string data must always begin with an alphabetic character, and
the characters following can be either alphabetic characters or numerals.
Although in character data either upper case letters or lower case letters are
accepted, response messages output by the 3532-50/3522-50/3511-50 are
always in upper case letters.
Example :TRIGger INT
(2) Decimal data
The numeric data values are all represented in decimal, in three formats
identified as NR1, NR2 and NR3, and each of these can appear as either a
signed number or an unsigned number. Unsigned numbers are taken as
positive.
Further, if the accuracy of a numerical value exceeds the limit which the
3532-50/3522-50/3511-50 can deal, it is rounded off. (5 and above is
rounded up; 4 and below is rounded down).
NR1 format - integer data.
Examples +12, -23, 34
NR2 format - fixed point numbers.
Examples +1.23, -23.45, 3.456
NR3 format - floating point numbers.
Examples +1E-2, -2.3E+4
The term "NRf format" includes all these three formats.
When the 3532-50/3522-50/3511-50 is receiving it accepts NRf format, but
when it is sending response messages it utilizes whichever one of the
formats NR1 to NR3 is indicated in the specified command.
Examples :RANGe 6
:RANGe +6.012
:RANGe 0.0006E4
────────────────────────────────────────────────────
4.5 Data Formats
15
────────────────────────────────────────────────────
4.6 Message Terminators
The 3532-50/3522-50/3511-50 recognize either a linefeed character (LF) or
the EOI signal, or both, as message terminators.
To terminate a response message, the 3532-50/3522-50/3511-50 always
provide the appropriate EOI signal, and also sends a terminating character
sequence. By the use of the ":TRANsmit:TERMinator" command either of
the following can be selected as response message terminator sequence:
(1) LF (linefeed only)
(2) CR + LF (carriage return plus linefeed)
NOTE
When powering on, the message terminators are (1).
A detailed explanation of the "TRANsmit:TERMinator" command is given in
Section 5.4.
4.7 Separators
(1) Message unit separator
A semicolon (;) is used as a message unit separator when it is desired to set
out several messages on a single line.
Example :RANGe:AUTO ON;:BEEP:KEY ON
NOTE
When messages are combined in this way, if a syntax error occurs, all
subsequent messages up to the next terminator will be ignored.
(2) Header separator
In a message which has a header and data, a space (represented by " " in
the examples) is used as the header separator to separate the header from the
data.
Example :LEVel V
; *
IDN?
(3) Data separator
If a message has several data items, commas (,) are required as data
separators for separating these data items from one another.
Example :COMParator:FLIMit:ABSolute
────────────────────────────────────────────────────
<lower limit> ,<upper limit>
4.6 Message Terminators
16
────────────────────────────────────────────────────
4.8 Abbreviation of Compound Commands
When several compound headers have a common head portion (for example,
:BEEPer:KEY
and
:BEEPer:COMParator
writing them directly following on from one another, this common portion
(
:BEEPer:
in this example) can be omitted from each command.
This common portion is called "the current path", by analogy with the
general concept of the current directory in the directory structure of UNIX or
MSDOS, and until it is cleared the analysis of following commands is
performed by deeming them to be preceded by the current path which has
been curtailed in the interests of brevity. This manner of using the current
path is shown in the following example:
Normal expression
:BEEPer:KEY ON;:BEEPer:COMParator NG
Abbreviated expression
:BEEPer: KEY ON;COMParator NG
, etc.), then, when and only when
This becomes the current path, and can be
curtailed from the following messages.
The current path is cleared when the power is turned on, when a colon (:)
appears at the start of a command, and when a message terminator is
detected.
Messages of standard command form can be executed without relation to the
current path. Further, they have no effect upon the current path.
With the 3532-50/3522-50, there are 11 possible current paths:
:APPLication:DISPlay
:BEEPer:
:COMParator:FLIMit:
:COMParator:SLIMit:
:CORRection:
:LEVel:
:LIMiter:
:MEASure:
:RANGe:
:TRIGger:
:SCALe:
With the 3511-50, there are 4 possible current paths:
:COMParator:
:CORRection:
:RANGe:
────────────────────────────────────────────────────
4.8 Abbreviation of Compound Commands
:BEEPer:
17
────────────────────────────────────────────────────
4.9 Output Queue
Response messages accumulate in the output queue and are read out as data
and cleared by the controller.
The output queue is also cleared in the following circumstances:
･
When a device clear is issued.
･
Whenthepoweristurnedoffandturnedonagain.
The 3532-50/3522-50/3511-50 have an output queue of 300 bytes capacity.
If the response messages overflow this limit of 300 bytes, a query error is
generated, and the output queue is cleared. Further, if a new message is
received while the output queue still contains data, the output queue is
cleared, and a query error is generated.
────────────────────────────────────────────────────
4.9 Output Queue
18
────────────────────────────────────────────────────
4.10 Input Buffer
The 3532-50/3522-50/3511-50 have an input buffer of 300 bytes capacity.
Messages which are received are put into this buffer and executed in order.
If the data accumulated in this buffer exceeds 300 bytes the buffer becomes
full, and until a space again becomes available in the buffer the GP-IB
interface bus goes into the waiting state.
────────────────────────────────────────────────────
4.10 Input Buffer
19
q
────────────────────────────────────────────────────
4.11 Status Model
In its implementation of the serial polling function using service requests, the
3532-50/3522-50/3511-50 employ the status model specified by IEEE 488.2.
The term "event" refers to any phenomenon which generates a service
request.
Status byte register (STB)
Represents standard event register
Generation of service
request (SRQ)
Data is present in the output queue
Bits represent corresponding event registers
bit 7 bit 5 bit 4 bit 3 bit 2 bit 1 bit 0
bit 7 bit 6 bit 5 bit 4 bit 3 bit 2 bit 1 bit 0
bit 6
RQS
MSS
Logical sum & & & &
X ESB MAV ESB1 ESB0
ESB MAV ESB1 ESB0
Service request enable register (SRER)
Generation of Service Re
uests
The status byte register holds information relating to the event registers and
the output queue.
It is further possible to use the service request enable register as a mask to
select the items required. If any of the bits selected by the mask becomes 1,
bit 6 (the master summary status or MSS bit) is also set to 1, an RQS
message is generated, and this generates a service request.
────────────────────────────────────────────────────
4.11 Status Model
20
────────────────────────────────────────────────────
4.12 Status Byte Register
(1) Status byte register (STB)
The status byte register is an 8-bit register whose contents are output from
the 3532-50/3522-50/3511-50 to the controller, when serial polling is being
performed.
If any bit in the status byte register has changed from 0 to 1 (provided that it
is a bit which has been set in the service request enable register as a bit
which can be used), then the MSS bit is set to 1. Simultaneously with this
the RQS bit is also set to 1, and a service request is generated.
Status byte register (STB)
bit 7 bit 5 bit 4 bit 3 bit 2 bit 1 bit 0
Unused ESB MAV Unused Unused ESB1 ESB0
bit 6
RQS
MSS
Logical sum & & & &
bit 7 bit 6 bit 5 bit 4 bit 3 bit 2 bit 1 bit 0
Unused X ESB MAV Unused Unused ESB1 ESB0
Service request enable register (SRER)
The RQS bit is synchronized with service requests, and is read out and
simultaneously cleared when serial polling is being performed. Although the
MSS bit is only read out on an"*
STB?"
query, on a"*
command for
CLS"
example it is not cleared until the event is cleared.
────────────────────────────────────────────────────
4.12 Status Byte Register
21
────────────────────────────────────────────────────
Status Byte Register Bit Assignments
Bit 7
Bit 6
RQS
MSS
Bit 5
ESB
Bit 4
MAV
Bit 3
Bit 2
Bit 1
ESB1
Bit 0
ESB0
Unused.
Set to 1 when a service request is issued.
Logical sum of the other bits of the status byte register
Standard event summary (logical sum) bit
Shows a logical sum of the standard event status register.
Message available.
Shows that there is at least one message in the output queue.
Unused.
Unused.
Event summary bit 1
Shows a logical sum of event status register 1.
Event summary bit 0
Shows a logical sum of event status register 0.
(2) Service request enable register (SRER)
This register masks the status byte register. Setting a bit of this register to 1
enables the corresponding bit of the status byte register to be used.
────────────────────────────────────────────────────
4.12 Status Byte Register
22
)
────────────────────────────────────────────────────
4.13 Event Registers
(1) Standard event status register (SESR)
The standard event status register is an 8-bit register. If any bit in the
standard event status register is set to 1 (after masking by the standard event
status enable register), bit 5 (ESB) of the status byte register is set to 1.
Status byte register(STB
RQS
MSS
bit 5
ESB MA
Standard event status register (SESR)
bit 7 bit 6 bit 5 bit 4 bit 3 bit 2 bit 1 bit 0
PON URQ CME EXE DDE QYE RQC OPC
Logical sum & & & & & & & &
bit 7 bit 6 bit 5 bit 4 bit 3 bit 2 bit 1 bit 0
PON URQ CME EXE DDE QYE RQC OPC
Standard event status enable register (SESER)
The standard event status register is cleared in the following three situations:
1. When a"*
2. When an"*
command is received.
CLS"
ESR?"
query is received.
3. When the unit is powered on.
────────────────────────────────────────────────────
4.13 Event Registers
23
────────────────────────────────────────────────────
(2) Standard event status enable register (SESER)
Setting any bit of the standard event status enable register to 1 enables the
corresponding bit of the standard event status register to be accessed.
Standard Event Status Register (SESR) Bit Assignments
Bit 7
PON
Bit 6
URQ
Bit 5
CME
Bit 4
EXE
Power on flag.
When the power is turned on, or on recovery from a power
cut, this bit is set to 1.
User request.
Not used by the 3532-50/3522-50/3511-50.
Command error.
When a command which has been received contains a
syntactic or semantic error, this bit is set to 1.
･
The command is not supported by the 3532-50/352250/3511-50.
･
There is a mistake in a program header.
･
The number of data parameters is wrong.
･
The format of the parameters is wrong.
Execution error.
When for some reason a command which has been received
cannot be executed, this bit is set to 1.
･
The designated data value is outside the set range.
･
The designated data value is not acceptable.
･
Execution is impossible because some other function is
being performed.
Bit 3
DDE
Bit 2
QYE
Bit 1
RQC
Bit 0
OPC
Device dependent error.
When a command cannot be executed due to some cause other
than a command error, a query error, or an execution error,
this bit is set to 1.
･
Execution is impossible due to an abnormality inside the
3532-50/3522-50/3511-50.
･
During open or short circuit compensation, valid data cannot
be obtained.
Query error.
This bit is set to 1 when a query error is detected by the
output queue control.
･
When an attempt has been made to read the output queue
when it is empty.
･
When the data overflows the output queue.
･
When data in the output queue has been lost.
Request for controller authority.
Not used by the 3532-50/3522-50/3511-50.
Operation terminated.
This bit is set to 1 when an "*OPC" command is executed,
when the operation of all the messages up to the "*OPC"
command has been completed.
────────────────────────────────────────────────────
4.13 Event Registers
24
────────────────────────────────────────────────────
(3) Event status registers specific to the 3532-50/3522-50/3511-50 (ESR0
and ESR1)
Two 8-bit event status registers are provided for managing events on the
3532-50/3522-50/3511-50. If any bit in one of these event status registers is
set to 1 (after masking by the corresponding event status enable register), the
following happens:
･
For event status register 0, bit 0 of the status byte register (ESB0) is set to 1.
･
For event status register 1, bit 1 of the status byte register (ESB1) is set to 1.
bit 1 bit 0
ESB1 ESB0
Logical sum & & & & & & &
3532-50/3522-50
Event status register 0 (ESR0)
bit 7 bit 6 bit 5 bit 4 bit 3 bit 2 bit 1 bit 0
Unused COF LOF IOF IUF IDX EOM CEM
bit 7 bit 6 bit 5 bit 4 bit 3 bit 2 bit 1 bit 0
Unused COF LOF IOF IUF IDX EOM CEM
Event status enable register 0 (ESER0)
Event status register 1 (ESR1)
bit 7 bit 6 bit 5 bit 4 bit 3 bit 2 bit 1 bit 0
Unused AND SLO SIN SHI FLO FIN FHI
Logical sum & & & & & & &
bit 7 bit 6 bit 5 bit 4 bit 3 bit 2 bit 1 bit 0
Unused AND SLO SIN SHI FLO FIN FHI
Event status enable register 1 (ESER1)
────────────────────────────────────────────────────
4.13 Event Registers
Loading...