For safety and warning information, please read this
•
Additional safety and warning information is provided
BERTWave
.
•
Remote Control
Operation Manual
11th Edition
manual before attempting to use the equipment.
within the MP2100A/MP2101A/MP2102A
Operation Manual, MP2100B BERTWave Operation
Manual or MP2110A BERTWave Operation Manual
Please also refer to them before using the equipment.
Keep this manual with the equipment.
ANRITSU CORPORATION
Document No.: M-W3773AE-11.0
DANGER
WARNING
CAUTION
Safety Symbols
To prevent the risk of personal injury or loss related to equipment malfunction, Anritsu Corporation uses the
following safety symbols to indicate safety-related information. Ensure that you clearly understand the meanings of
the symbols BEFORE using the equipment. Some or all of the following symbols may be used on all Anritsu
equipment. In addition, there may be other labels attached to products that are not shown in the diagrams in this
manual.
Symbols used in manual
This indicates a very dangerous procedure that could result in serious injury or
death if not performed properly.
This indicates a hazardous procedure that could result in serious injury or death if
not performed properly.
This indicates a hazardous procedure or danger that could result in light-to-severe
injury, or loss related to equipment malfunction, if proper precautions are not taken.
Safety Symbols Used on Equipment and in Manual
The following safety symbols are used inside or on the equipment near operation locations to provide information
about safety items and operation precautions. Ensure that you clearly understand the meanings of the symbols and
take the necessary precautions BEFORE using the equipment.
This indicates an obligatory safety precaution. The obligatory operation is
This indicates a warning or caution. The contents are indicated symbolically in or
This indicates a note. The contents are described in the box.
These indicate that the marked part should be recycled.
This indicates a prohibited operation. The prohibited operation is indicated
symbolically in or near the barred circle.
indicated symbolically in or near the circle.
near the triangle.
BERTWave Series
Remote Control Operation Manual
4 September 2015 (First Edition)
24 April 2019 (11th Edition)
This product and its manuals may require an Export License/Approv al by
the Government of the product's country of origin for re-export from your
country.
Before re-exporting the product or manuals, please contact us to confirm
whet
When you dispose of export-controlled items, the products/manuals need
to be broken/shredded so as not to be unlawfully used for military purpose.
Notes On Export Management
her they are export-controlled items or not.
iii
iv
About This Manual
The manual set for the BERTWave Series consists of the following five
operation manuals:
MP2110A BERTWave Operation Manual
(M-W3831AE)
This manual is intended for those who use the MP2110A BERTWave,
and explains the installation procedure, handling precautions,
connector connection procedures, panel operations, maintenance
procedures, specifications and various functions.
MP2100B BERTWave Operation Manual
(M-W3772AE)
This manual is intended for those who use the MP2100B
BERTWave, and explains the installation procedure, handling
precautions, connector connection procedures, panel operations,
maintenance procedures, specifications and various functions.
In this manual, the models of BERTWave are described as follows.
MP210xA: MP2100A, MP2101A, and MP2102A
this instrument: MP2100A, MP2101A, MP2102A, MP2100B, and
MP2110A
BERTWave: MP2100A, MP2101A, MP2102A, MP2100B, and
MP2110A
II
Table of Contents
1
About This Manual................................................. I
1.4 Restrictions on Software Versions ............................... 1-6
1
1-1
Chapter 1 Overview
1.1 What is Remote Control?
The remote control function sends commands via the communications
interface from the control PC to set the measuring instrument and read
the measurement results and measuring instrument conditions.
The BERTWave supports the Ethernet or GPIB as a control interface.
For MP210xA and MP2100B, the Option 030 is required to use GPIB
interface.
When using either interface, set the number to distinguish the
BERTWave from other equipment. This number must be an IP address
and TCP port number when using the Ethernet interface, or the GPIB
address when using GPIB connection.
The character strings for controlling the BERTWave are called
“command”. The command is composed of the ASCII character strings.
For example, the following command is used to output the signal of the
pulse pattern generator (hereafter, PPG) to the connector.
:OUTput:DATA:OUTput ON
A command for reading data from the BERTWave is called “query”. A
query command has the question symbol (?) appended to the end of string.
For example, sending the following command queries the PPG bit rate set
at the instrument.
:OUTput:BITRate?
1-2
The control PC receives the following response to the query from the
instrument.
1250000
The bit rate is 1250000 kbit/s.
When the BERTWave is measured via remote control, the Remote lamp
on the screen is lit. Only the power switch and the key
on the system menu are valid in this situation. This situation is called
panel lock. To unlock the panel, touch
menu.
Local/Panel Unlock on the system
Local/Panel Unlock
1.2 Main Uses for Remote Control
The main uses for remote control are:
Automation of measurement
To control measuring instruments by executing a program, instead of
touch-panel operations. Measurement can be automated by describing the
control procedures for controlling the measuring instruments, in the
program.
Remote control of instruments
To collect measurement data by controlling measuring instruments
installed at remote locations, over communications lines.
Control of multiple measuring instruments
To measure the characteristics of DUTs via the remote control of multiple
measuring instruments.
1.2 Main Uses for Remote Control
1
Overview
Control PC
E/O
Converter
Optical Fiber
PPG Output
Optical Attenuator
BERTWave
ED1 Input
Optical Receiver
(DUT)
Optical Switch
Optical Power Meter
Figure 1.2-1 Example of Controlling Multiple Instruments
1-3
–25.034
0.011442
–24.523
0.0048758
–24.031
0.001631
–23.536
0.00044241
–23.030
0.000078419
–22.523
0.0000088616
–22.031
0.000000616
–21.524
0.000000016
–21.037
0.00000000028235
Chapter 1 Overview
Figure 1.2-1 shows an example of controlling multiple instruments. In
this example, the bit error rates are measured with changes in the optical
input level of the optical receiver. On the control PC, set the attenuation
of the optical attenuator to read the optical power level measured by the
optical power meter, and the bit error rate measured by the BERTWave.
Table 1.2-1 shows the measurement results that are obtained by changing
the optical attenuation.
Table 1.2-1 Bit Error Rate of Optical Receiver
Optical Power (dBm) Bit Error Rate
1-4
Overview
1.3 Abbreviations
ASCII
American Standard Code for Information Interchange
CR
Carriage Return
ED
Error Detector
EOI
End or Identify
ESER
Event Status Enable Register
ESR
Event Status Register
GPIB
General Purpose Interface Bus
HiSLIP
High Speed LAN Instrument Protocol
IEC
International Electrotechnical Commission
IEEE
Institute of Electrical and Electronics Engineers
LAN
Local Area Network
LF
Line Feed
MAV
Message Available
MSS
Master Summary Status
OSER
Operation Status Enable Register
OSR
Operation Status Register
PC
Personal Computer
PPG
Pulse Pattern Generator
SCPI
Standard Commands for Programmable Interfaces
SRER
Service Request Enable Register
SRQ
Service Request
STB
Status Byte Register
TR
Transition Filter
VISA
Virtual Instrument Software Architecture
VXI-11
VMEbus Extensions for Instrumentation-11
Table 1.3-1 shows the abbreviations used in this operation manual.
Abbreviation Formal name
1.3 Abbreviations
1
Table 1.3-1 Abbreviations
1-5
Chapter 1 Overview
1.4 Restrictions on Software Versions
Some of the commands described in this manual are only available in a
specific version of the MX210000A BERTWave Control Software.
In MP2100B (version 4) and MP2110A (version 5 or later), the
MX210000A version is displayed at the upper right of the application
window.
Figure 1.4-1 Display of Software Version Number (MP2100B, MP2110A)
1-6
1.4 Restrictions on Software Versions
Overview
For MP210xA (version 3 or earlier), confirm the version of MX210000A in
Information dialog box of Setup Utility.
1
Figure 1.4-2 Display of Software Version Number (MP210xA,
MP2100B)
1-7
Chapter 1 Overview
1-8.
Before Use
Chapter 2 Before Use
This chapter explains the preparations for using remote control.
2.1
Connection Types of Remote Controlling .................... 2-2
2.2 Multiple Sessions (Version 5 or later) .......................... 2-3
2.9 Checking If Message Execution Is Completed ........... 2-29
2.9.1 When using Ethernet ..................................... 2-29
2.9.2 When using GPIB.......................................... 2-30
2
2-1
Raw Socket
TCPIP[0]::<IP address|host
TCPIP::192.168.20.3::5001::SOCKET
VXI-11
TCPIP[0]:: <IP address|host name
TCPIP::192.168.20.3::inst0::INSTR
HiSlip
TCPIP[0]:: <IP address|host name
TCPIP::192.168.20.3::hislip::INSTR
GPIB
GPIB[0]::<primary
address>]::INSTR
GPIB::1::INSTR
Chapter 2 Before Use
2.1 Connection Types of Remote Controlling
The following connections can be performed when controlling BERTWave
remotely.
Raw Socket connection
•
VXI-11 connection (version 5 or later)
•
HiSLIP connection (version 5 or later)
•
GPIB connection
•
Table 2.1-1 lists the resource names when performing the connection
using VISA.
Table 2.1-1 VISA Resource Name List
Protocol VISA Resource Name Example
name>::<Port number>::SOCKET
>::inst0::INSTR
>::hislip[0] [,<Port number >]::INSTR
address>[::<secondary
2-2
2.2 Multiple Sessions (Version 5 or later)
Before Use
Raw Socket
30 sessions
VXI-11
30 sessions
HiSLIP
8 sessions
GPIB
1 session
2.2 Multiple Sessions (Version 5 or later)
When Raw Socket, VXI-11, or HiSLIP is used as the protocol, multiple
PCs can connect with MP2110A simultaneously. If the different types of
protocols are used, these PCs are not connected with MP2110A
simultaneously. When controlling the multiple sessions using VXI-11 or
HiSLIP, the session can be locked to perform the exclusion control of the
sessions.
Table 2.2-1 lists the maximum number of sessions for each protocol.
Table 2.2-1 List of Maximum Number of Sessions
2
Protocol
Maximum Number of
Sessions
2-3
Chapter 2 Before Use
2.3 Required Equipment
The equipment required for remote control is as follows
Control PC
•
Ethernet interface
•
GPIB interface*
•
Program development tool
•
Control PC
Prepare the PC that meets the operating environment for the GPIB
interface and program development tools.
Ethernet Interface
Prepare Ethernet-compliant interface and cable.
GPIB Interface*
Prepare IEEE 488.2-compliant GPIB interface and cable.
Program Development Tool
Prepare a tool for developing and running programs for performing
remote control. For the requirements specification of the program
development tool, refer to the manuals that come with the tool you
prepared.
VISA is required for using the sample program explained in Appendix C.
*: The option 030 is required for using GPIB in MP210xA and
MP2100B.
2-4
Before Use
2.4 Connecting Equipment
Control PC
Connecting via LAN
Control PC
Connect using LAN
Network hub
2.4.1 Connecting Ethernet
Connect the Ethernet connector on the side-panel of the BERTWave and
Control PC using LAN cables.
The Ethernet connector is located on the left side panel for MP210xA and
MP2100B, and on the rear panel for MP2110A
Use a LAN cable to connect the BERTWave and Control PC directly. Use a
LAN cable via a network hub when connecting to multiple external
devices.
2.4 Connecting Equipment
2
cable
Figure 2.4.1-1 Direct Connection between BERTWave and Control PC
cables.
External device
Figure 2.4.1-2 Sample Connection with Multiple External Devices
Notes:
MP210xA and MP2100B cannot connect to the network
•
including the address range from 192.168.1.0 to 192.168.1.255.
The control PC may have difficulty in communicating with the
•
BERTWave, depending on the status of communications
between them. The direct connection is recommended to ensure
communication stability.
2-5
GPIB
GPIB connector
GPIB cable
Total cable length: Up to 20 m
Number of devices that can be connected: Up to 15
Chapter 2 Before Use
2.4.2 Connecting GPIB
Connect the GPIB connector on the rear panel of the BERTWave and an
external device using a GPIB cable.
Up to 15 devices, including the control PC can be connected to one
BERTWave unit. Always follow the conditions shown below when
connecting devices.
CAUTION
Always connect the GPIB cable BEFORE turning on the
power to the BERTWave. Connecting it while the power is
on may damage internal circuits.
Cable length between devices: Up to 4 m
2-6
Figure 2.4.2-1 GPIB Cable Connection 1
Before Use
Connect cables without forming loops.
(a) Daisy Chain
(b) Star
(c) Loop
2.4 Connecting Equipment
2
Figure 2.4.2-2 GPIB Cable Connection 2
2-7
Chapter 2 Before Use
2.5 Setting Interface
For details on how to set the interface, refer to 2.14 “Setting Interface for
Remote Control” in the
4.3.10 “Remote Control” in the
2.5.1 MP210xA and MP2100B
1. Switch on the power to the MP210xA or MP2100B.
MP2100B BERTWave Operation Manual
MP2110A BERTWave Operation Manual
and
.
2. Touch
3. Touch
4. In order to use Ethernet, touch the Active Interface button to set the
button display to
GPIB.
When the Option 030 is not installed, the Active Interface button is
disabled.
5. When using Ethernet, set the IP address, subnet mask, gateway and
port number.
The gateway address can be omitted.
The port number can be set from 1024 to 5001.
When using GPIB, set the GPIB address.
6. Touch Apply, and then the settings are completed.
Touch
Note:
Setup Utility at the Selector screen.
Remote Control.
Ethernet. To use GPIB, set the button display to
Exit, and then the set value is deleted.
Do not set the following IP address.
192.168.1.xxx
2-8
Before Use
2.5.2 MP2110A
2.5 Setting Interface
1. Switch on the power to the MP2110A.
2. Click
3. Click
4. Set the GPIB address, IP address, subnet mask, gateway and port
5. Click
Note:
System Menu.
Remote Control.
number.
The gateway address can be omitted.
The port number can be set from 1024 to 5001.
OK, and then the settings are completed.
Click Cancel, and then the set value is deleted.
Do not set the following IP address.
169.254.1.xxx
2
2-9
Chapter 2 Before Use
2.6 Checking Connection
This section describes how to check if the Control PC can recognize the
BERTWave.
For MP210xA and MP2100B, start Main Application before checking the
connection.
1. If the Setup Utility dialog box is displayed, touch
Exit.
2. On the Selector screen, touch
2.6.1 When using Ethernet (Windows 7)
This section explains how to use the free software, Tera Term Version
4.69.
1. When starting Tera Ter m , the
Enter the IP address and TCP port number in the Host.
Set the service to
Click OK.
If the BERTWave IP address is set to 192.168.100.2, and the port
number is set to 5001, set as follows.
Other and protocol to IPv4.
Main Application.
New connection window is opened.
2-10
2. When Ter a Te r m recognizes the BERTWave, the communication
window is displayed.
3. Click
Settings (S) - Terminal (T).. on the menu.
2.6 Checking Connection
Before Use
4. Under New-line, set Receive to LF and Transmit to CR+LF. Select
the Local echo check box and click OK.
5. Send *IDN?.
Confirm that the response is displayed from the BERTWave.
2
2.6.2 When using GPIB
1. Install the software drivers for the GPIB interface.
2. Run the software.
For the operation method, refer to the GPIB interface operation
manual.
3. Check the displayed instrument address.
2-11
Chapter 2 Before Use
2.7 Message Format
2.7.1 Message Types
Messages are composed of the character strings indicating message and
message end. The character string indicating the message end is LF (Line
Feed) or CR (Carriage Return) +LF.
Note:
If LF or CR+LF is not attached to the message end, a timeout error
occurs because the communication does not end.
Messages are composed of the following types depending on the
transmission direction:
Program Messages
Messages sent from control PC to instrument
There are two types of the program messages:
Command
•
This can be used for measurement condition settings and
measurement start.
Query
•
This queries the status and settings of the measuring instrument.
When transmitting the query, the instrument creates a response
message to the query.
Response Messages
Messages sent from instrument to control PC
2-12
Before Use
2.7.2 Message Configuration
The messages are composed of header and data parts separated by more
than a half width space. Program messages always have a header but
sometimes have no data. Response messages always have data but
sometimes have no header.
Header
The command header has the following types:
Simple header
•
The header is composed of alphanumeric characters and underbars,
and the initial character is an alphabetic character.
Example:
Common command header
•
The header is composed of alphanumeric characters and underbars,
and the initial character is an asterisk (*).
Example:
Multiple headers
•
Single headers are linked by colons. Colons can be used at the header.
Multiple headers can be used to configure layered processing.
Example:
Queries have a question mark (?) appended to the header.
STA
*CLS
:SENSE:MEASURE:START
2.7 Message Format
2
Example:
:CONFIGURE?
Data
The data format is character string data, numeric data, and binary data.
String data is ASCII code enclosed in quotation marks.
An example of the program message when inputting
the title is shown below.
Example:
:SYSYEM:MEMORY:STORE 'Model ANR-005',0,ALL
:SYESEM:MEMORY:STORE "Model ANR-005",0,ALL
When quotation marks are included in the character string, paired marks
are used.
Example:
He said "Good product". → "He said ""Good Product""."
He said 'Good product'. → 'He said ''Good Product''.
'
*ESE?
Model ANR-005
at
2-13
Chapter 2 Before Use
In addition, paired quotation marks can be used inside other paired
quotation marks.
Example:
He said "Good product". → 'He said "Good Product".'
He said 'Good product'. → "He said 'Good Product'."
The numeric values can be described by using numeric data, input
numeric values either as decimal, binary, octal, or hexadecimal numbers.
When using the binary, octal, or hexadecimal numbers, put #B, #O, or #H
before the data.
Example:
When using decimal numbers, use integer number, fixed point, or floating
point. The following examples indicate the same values.
Example:
For the binary data, the head string starts with a sign (#) and continues
with data after a numeric value indicating the data length.
Example:
4 digits 2002 bytes binary data
10 #B1010 #O12 #HA
1550 #B11000001110 #O3016 #H60E
-10 -10.00 -1E1
1250 1250.000 1.25E3
0.0023 2.3E-4
#42002an%*qe4445+\…
2-14
2.7 Message Format
Before Use
When there are multiple data in a message, separate each of them with
commas (,).
Example:
:SENSE:MEASURE:EALARM:PERIOD 0,0,1,0
When concatenating multiple program messages, separate the messages
with semicolons (;).
Example:
Note:
When sending multiple messages separated by semicolons, the
maximum length of the concatenated string is 1024 bytes.
When sending a concatenated string of query messages, response
messages are separated by semicolons.
Example:
:INPUT:DATA:ATTFACTOR 1,6
:MOD:ID 5;:DISP:MODE EYE;:SAMP:STAT RUN
:MOD:ID 1;:OUTP:BITR:STAN?;:OUTP:BITR?
>"10G_LAN";10312500
2
2-15
*CLS
Clears stand event register and output queue
*ESE
Sets and queries standard event enable register
*ESR
Queries standard event register
*IDN
Queries product information
*OPC
Sets/queries bit setting and bit 0 for status byte
indicating message processing completion
*OPT
Queries option information
*RST
Initializes BERTWave setting conditions
*SRE
Sets and queries SRER
*STB
Queries status byte register
*TRG
Starts measurement
*WAI
Waits previous sent message completion
Chapter 2 Before Use
2.7.3 Common Commands
The GPIB specifications (IEEE 488.2) define equipment commands. In
this manual, these defined commands are called common commands.
The common commands are divided into mandatory and option
commands. The BERTWave supports the common commands listed in
Table 2.7.3-1.
Command Explanation
Table 2.7.3-1 Common Commands
2.7.4 Device Dependent Commands
In this manual, commands that differ according to the functions of the
measuring instrument are called Device Dependent Commands.
This instrument has two types of Device Dependent Commands.
SCPI
•
Commands meeting SCPI standard
Native
•
Commands consisting of at least three ASCII characters
2-16
Before Use
2.8 Checking Instrument Status
Status Byte Register
Output Queue
Bit
0
Bit
Standard Event Status Register
Power On
Execution Error
Query Error
Logical Sum
Not Used
Bit
0
Operation Status Register
Not Used
Logical Sum
MAV
Logical Sum
Generating
Service Request
Status Register
Bit
Bit
Bit
0
Device Dependent Register
Not Used
CAL Alarm (Yellow)
Not Used
PLL Unlock
Not Used
LOS
Bit
Bit
Bit
*: Version 6 or later
The BERTWave has registers indicating status, such as errors and
command execution status. This section explains these registers.
2.8 Checking Instrument Status
2.8.1 Register Structure
Figure 2.8.1-1 shows the structure of the registers indicating the
instrument status.
15
Not Used
Not Used
Not Used
Not Used
Not Used
Not Used
Not Used
Not Used
Not Used
ED measurement
Not Used
Not Used
Not Used
Not Used
Not Used
Command Error
Not Used
Operation Complete
14
13
12
11
10
9
8
7
6
5
4
3
2
1
7
6
5
4
3
2
1
0
Insertion Error
CR Unlock
SYNC Loss
Bit Error
Not Used
Not Used
Not Used
PPG/ED Ch1 to Ch4
Status Register
15
15
:
:
5
5
4
4
3
3
2
2
1
1
0
0
XFP/SFP+
15
:
4
3
2
PT phase unlock
1
0
CAL Alarm (Red)
15
15
:
:
5
5
4
4
3
3
2
2
1
1
0
0
Scope
Status Register
CRU Unlock*
Not Used
Not Used
2
15
:
8
7
6
5
4
3
2
1
MSS
ESB
Not Used
Not Used
Figure 2.8.1-1 Register Structure
7
6
5
4
3
2
1
2-17
0 1 8
256
1 2 9
512
2 4 10
1024
3 8 11
2048 4 16
12
4096 5 32
13
8192 6 64
14
16382
7
128
15
32764
Chapter 2 Before Use
Each register uses 8-bit or 16-bit data. The register output values are the
decimal totals for each bit shown in Table 2.8.1-1.
Table 2.8.1-1 Register Bit Decimal Conversion Values
Bit
The register has a corresponding bit enable register.
Decimal
value
Bit
Decimal
value
2-18
Before Use
2.8.2 Status Byte Register
Bit
7
6
5
4
3
2
1
0
Status Byte Register
Execution Status
Standard Event Status
Send Queue
Not used
Query Error
Not used
Not used
Logical Sum
Bit
7
6
5
4
3
2
1
0
Service Request
Enable Regist
er
Service
Request
Logical
Product
The status byte register (STB) displays the status of equipment defined
by the GPIB standards. When the equipment status changes, the value in
the STB changes too. It can be used to generate interrupts to the Control
PC. These interrupts are called service requests.
There is a service request enable register (SRER) for the STB. The SRER
can select the status byte bit generating the service request.
2.8 Checking Instrument Status
2
Figure 2.8.2-1 Configuration of Status Byte Register and Service
Request Enable Register
Note:
When using the GPIB interface, the service request is enabled.
The following methods are used to read the status byte register.
Using common *STB? command
•
Using GPIB serial poll (when the Option 030 is installed for MP210xA
•
or MP2100B)
Read the GPIB interface manual for the serial poll method.
When using serial polling, even if bit 6 is 1, it becomes 0 after reading
once.
The
*SRE
and
*SRE?
common commands can be used for setting and
reading the SRER for setting reading of the status byte register. To output
the STB data, set the bit corresponding to the SRER to 1.
2-19
7
This is the logical sum of each bit of the logical product of
the OSR and its event enable register.
6
MSS (Master Summary Register)
of the STB and the SRER.
5
This is the logical sum of each bit of the logical product of
enable register.
4
MAV (Message Available summary)
3
Not used; always 0
2
Becomes 1 at System Error
1
Not used; always 0
0
Not used; always 0
Chapter 2 Before Use
The definition of each bit of the STB is shown in the following table.
Table 2.8.2-1 Bit Definition of Status Byte Register
Bit
It is the logical sum of the bit 5 to 0, bit 7 logical product
the standard event status register and standard event
This is always 1 when there is a response message in the
output queue of this instrument
Bit 7 of the STB indicates information about the OSR.
For details about the information, refer to section 2.8.4 “Operation Status
Register”.
Bit 6 of the STB is called the master summary status (MSS) bit. When it
is 1, there is a notification from BERTWave to the control PC. When it
changes to 1 from 0, a service request is generated.
Explanation
Bit 5 of the STB indicates information about the standard event register.
For details about the information, refer to section 2.8.3 “Standard Event
Status Register”.
The device dependent register data is not indicated in the STB.
Bits 7 and 5 of the STB can be set to 0 using the *CLS common command.
When *CLS is sent after a command or when a query is sent after *CLS,
the send queue is cleared and bit 4 is set to 0.
The SRER cannot be set to 0 by *CLS, so use *SRE.
2-20
Before Use
2.8.3 Standard Event Status Register
Bit
7
6
5
4
3
2
1
0
Standard Event Status
Register
Power-on
Not used
Command error
Execution error
Device dependent error
Not used
Not used
Operation completed
Logical Sum
Bit
7
6
5
4
3
2
1
0
Standard Event Status
Enable Register
Status Byte
Register bit 5
Logical
Product
There is a standard event status enable register (ESE) for the standard
event status register (ESR). The logical product of these two registers and
the logical sum of each bit of this result is output to bit 5 of the STB.
2.8 Checking Instrument Status
2
Figure 2.8.3-1 Configuration of Standard Event Status Register and
Standard Event Status Enable Register
2-21
7
1 if the BERTWave is powered on.
6
Not used; always 0
5
1 if a command error occurs.
Refer to Appendix B, “Error Codes” for details.
4
1 if an execution error occurs.
Refer to Appendix B, “Error Codes” for details.
3
1 if a device-dependent error occurs.
Refer to Appendix B, “Error Codes” for details.
2
Not used; always 0
1
Not used; always 0
0
Operation Complete
sending response data to a query has ended.
Chapter 2 Before Use
The definition of each bit of the ESR is listed in the table below.
Table 2.8.3-1 Bit Definition of Standard Event Status Register
Bit
Changed to 0 if a program message is received.
Becomes 1 when the entire command operation has
completed after *OPC command operation or when
Bit 7 to bit 0 of the ESR can be read by the
The standard event register returns to 0 when read.
The ESE can be set and read using the
output standard event register data, set the bit corresponding to the
enable register to 1.
Explanation
*ESR?
*ESE
and
command.
*ESE?
commands. To
2-22
The bit 0 can be read using the
The standard register can be set to 0 using the
*OPC
command.
*CLS
command.
Before Use
2.8.4 Operation Status Register
The operation status register (OSR) is composed of the following registers:
Operation status condition register
•
Transition filter
•
Operation status event register
•
Operation status enable register (OSER)
•
The operation status condition register indicates changes in the status.
When the status changes, the value of this register also changes.
The OSER records changes in the value of the execution status condition
register. There is a transition filter that defines the write condition before
the OSER. The transition filter sets the OSER to 1 under any of the
following conditions:
2.8 Checking Instrument Status
2
When bit changes from 0 to 1
•
When bit changes from 1 to 0
•
When bit changes from 0 to 1 and bit changes from 1 to 0
•
The OSER sets the OSER output at each bit. The logical product of these
two registers is obtained and the logical sum of each bit of the result is
output at bit 7 of the STB.
2-23
Bit
15
14
13
12
11
10
9
8
7
6
5
4
3
2
1
0
Operation Status
Event Register
Not used
Not used
Not used
Not used
During PPG/ED pattern setting
Not used
Not used
Not used
Not used
Not used
Not used
During ED Measuring
Not used
Not used
Not used
Not used
Logical Sum
Bit
15
14
13
12
11
10
9
8
7
6
5
4
3
2
1
0
Operation Status
Enable Register
Status Byte
Register Bit 7
Logical
product
Bit
15
14
13
12
11
10
9
8
7
6
5
4
3
2
1
0
Transition Filter
Detecting
Status Change
Bit
15
14
13
12
11
10
9
8
7
6
5
4
3
2
1
0
Operation Status
Condition Register
15 to 12
Not used; always 0
11
1 during execution of PPG/ED pattern setting.
10 to 5
Not used; always 0
4
1 during execution of ED measurement.
3 to 0
Not used; always 0
Chapter 2 Before Use
Figure 2.8.4-1 Configuration of Operation Status Condition Register, Operation Status Event
Register, Operation Status Enable Register, and Transition Filter
Each bit definition of the execution status is as follows.
2-24
The commands for confirming the execution start or end time at the OSR
are shown in the following table.
Table 2.8.4-1 Bit Definition of Operation Status Register
Bit
Explanation
2.8 Checking Instrument Status
Before Use
11
:SENSe:MMEMory:PATTern:RECall
:SOURce:PATTern:TYPE
4
[:BERT:ALL]:SENSe:MEASure:STARt
Table 2.8.4-2 Commands for Confirming Execution of operation at
To detect the execution start, set the corresponding bit of the transition
filter to 1 using STATus:OPERation:PTRansition
To detect the execution end, set the corresponding bit of the transition
filter to 1 using STATus:OPERation:NTRansition.
The OSER can be read using :STATus:OPERation[:EVENt]?. When the
register is read, the OSR returns to 0.
The operation status condition register can be read
using :STATus:OPERation:CONDition?.
To set the OSER, use :STATus:OPERation:ENBle. To read the OSER, use
STATus:OPERation:ENBle?. To output the OSR data, set the bit for the
status setting enable register to 1.
When sending :STATus:OPERation:RESet, the operation status event
register is set to 0.
However, sending :STATus:OPERation:RESet does not reset the OSER.
2
2-25
Not used
Not used
Not used
Not used
Not used
Not used
Not used
Not used
Detecting Status Change
Chapter 2 Before Use
2.8.5 Device Dependent Registers
The following registers are called the device dependent registers.
PPG/ED Ch1 to 4 Status Register
•
XFP/SFP+ Status Register
•
Scope Status Register
•
The device dependent register has condition register, transition filter, and
event register as the operation status register does. However there is no
enable register for switching the output at each bit on/off.
Device Dependent
Condition Register
Bit
15
14
Not used
Not used
Not used
Not used
Not used
Status 2
Status 1
Status 0
13
12
11
10
9
8
7
6
5
4
3
2
1
0
Transition Filter
Bit
15
14
13
12
11
10
9
8
7
6
5
4
3
2
1
0
Device Dependent
Event Register
Bit
15
14
13
12
11
10
9
8
7
6
5
4
3
2
1
0
2-26
Figure 2.8.5-1 Configuration of Device Dependent Register
When the value of the device dependent register changes, there is no
effect on the STB. As a result, a service request is not generated to the
control PC.
2.8 Checking Instrument Status
Before Use
15 to 6
Not used; always 0
5
Indicates Omission Error occurs.
4
Indicates Insertion Error occurs.
3
Indicates CR Unlock occurs.
2
Indicates SYNC Loss occurs.
1
Indicates Bit Error occurs.
0
Indicates PLL Unlock occurs.
15 to 2
Not used; always 0
1
Indicates LOS occurs.
0
Indicates Ready status.
15 to 9
Not used; always 0
8
Not used; always 0
7
Indicates CRU Unlock occurs.*1
6
Indicates that Precision Trigger is out of synchronized
5
Indicates that the frequency of trigger input signal is
abnormal. *2
4
Indicates PLL Unlock (No trigger input) occurs.
3
Not used; always 0
2
Indicates CAL alarm (Orange) occurs.
1
Indicates CAL alarm (Red) occurs.
0
Indicates CAL alarm (Yellow) occurs.
Each bit definition of the device dependent register is as follows.
Table 2.8.5-1 Bit Definition of PPG/ED Ch1 to Ch4 Status Register
Bit
Explanation
2
Table 2.8.5-2 Bit Definition of XFP/SFP+ Status Register
Bit
Table 2.8.5-3 Bit Definition of Scope Status Register
Bit
Explanation
Explanation
status. *2
*1: Software version 6 or later
*2: Software version 5 or later
To detect the occurrence of these phenomena, set the transition filter bit
to 1 using the following commands:
:INSTrument:PE{1|2|3|4}:PTRansition
:INSTrument:XSFP:PTRansition
:INSTrument:WAV:PTRansition
To detect the end of these phenomena, set the transition filter bit to 1
using the following commands:
2-27
Chapter 2 Before Use
:INSTrument:PE{1|2|3|4}:NTRansition
:INSTrument:XSFP:NTRansition
:INSTrument:WAV:NTRansition
The device dependent event register can be read using the following
queries:
:INSTrument:PE{1|2|3|4}[:EVENt]?
:INSTrument:XSFP[:EVENt]?
:INSTrument:WAV[:EVENt]?
The device dependent condition register can be read using the following
queries:
:INSTrument:PE{1|2|3|4}:CONDition?
:INSTrument:XSFP:CONDition?
:INSTrument:WAV:CONDition?
The device dependent event register can be initialized using the following
queries:
:INSTrument:PE{1|2|3|4}:RESet
:INSTrument:XSFP:RESet
:INSTrument:WAV:RESet
2-28
2.9 Checking If Message Execution Is Completed
Before Use
2.9 Checking If Message Execution Is Completed
Some of the BERTWave program messages may take several seconds to
several ten seconds to execute. Depending on the interface (Ethernet or
GPIB) you are using, the procedure to check if time-consuming message
execution is completed is different.
2.9.1 When using Ethernet
Even during execution of a program message sent to the BERTWave, the
subsequent message(s) can be sent. However, until execution of the
previously sent message(s) is completed, the subsequent message(s) is not
processed, and is stored in the buffer of the BERTWave.
Therefore, note that execution of the previously sent program message(s)
may not have always been completed, even if the subsequent message(s)
can be sent. To check if execution of a program message is completed, send
a query to receive a response.
Example:
:CALibrate:AMPLitude
:SYSTem:ERRor?
> 0,”No Error”
It may take around 50 seconds to complete execution of
:CALibrate:AMPLitude
the
version 5 or later).
subsequently
AMPLitude
is checked by receiving a response message.
AMPLitude
:SYSTem:ERRor?
Starts Level calibration for Scope
Query for error code and error message
No error
command in this example (in software
is sent, and
, and then execution completion of
2
Note:
If it may take a long time to process the command that precedes the
query, set the sufficient response timeout, with respect to the
command processing time. (Timeout needs to be longer by at least
10 seconds than the command processing time.)
2-29
Chapter 2 Before Use
2.9.2 When using GPIB
Sending the subsequent message is forced to wait, on the control PC, until
execution of the sent message is completed. Therefore, prevent a
communication timeout from occurring during message execution by the
BERTWave, when sending a time-consuming command. Set the sufficient
timeout for GPIB interface of the control PC, with respect to the command
processing time. (Timeout needs to be longer by at least 10 seconds than
the command processing time.)
Example: Sending a command that takes about 20 seconds to execute
1. Set the timeout for GPIB interface to 30 seconds.
2. Send a command which takes time to complete.
3. Reset the timeout to the previous setting.
2-30.
Message List
Chapter 3 Message List
This chapter describes the message details of remote control commands
for BERTWave.
3.1
Rules for Describing Messages ................................... 3-3
3.2 Correspondence Between Panel and Messages ......... 3-4
3.2.1 Messages corresponding to
common operations ......................................... 3-4
3.2.2 Messages corresponding to PPG/ED .............. 3-6
Test Pattern Setting .................................... 3-104
3-2
Message List
3.1 Rules for Describing Messages
<>
Parameters in angled bracket are input by the programmer.
[]
Messages or parameters in square brackets can be omitted.
|
Select one of choices separated by vertical bars. For example,
if A|B|C|D are choices, select one of them.
{}
Group the choices. For example, A|B({C|D}) means that A,
B(C), or B(D) is available.
<binary_data>
This string is in binary data format.
<character>
Alphabet or numeric characters
<file_name>
The string indicates file name and path. The double
Example:
"PATTERN005"
<integer>
Decimal integer
Example: –100, 12500000
<numeric>
Decimal number
Example: 0, 1.2E–6, 2.35
<string>
String data
needed at the beginning and end of the data.
<enable>
On/Off setting
Example: 0, 1, OFF, ON
…
Indicates that multiple parameters or responses are omitted.
>
Precedes a response, in Example of Use.
The following table shows the rules for describing messages.
Table 3.1-1 Rules for Describing Messages
Symbols Usage
quotation marks or single quotation marks are needed at the
beginning and end of the data.
\,/,:,*,?,",<,>,| are not used in the file name.
3.1 Rules for Describing Messages
3
The double quotation marks or single quotation marks are
To turn off, specify 0 or OFF. (Response: 0)
To turn on, specify 1 or ON. (Response: 1)
Some parts of the header strings can be omitted.
The lower-case characters can be omitted, but the upper-case characters
cannot be omitted.
Example:
The following header strings are also acceptable:
:STAT:OPER:EVEN?
:STAT:OPERATION:EVEN?
:STATUS:OPERAT:EVENT?
:STATUS:OPERATION:EVEN?
:STATUS:OPERATION:EVENT?
BERTWave interprets them in the same way.
:STATus:OPERation:EVENt?
3-3
:DISPlay:ACTive
:SYSTem:ERRor:HISTory?
:SOURce:OUTPut:ASET
:SENSe:MEASure:ASTP
:SENSe:MEASure:ASTate?
*TRG
:SYSTem:{DATE|TIME}?
:BERT:ALL:PARam:TRACking
:DISPlay:ACTive:ACResult
*IDN?
:SYSTem:MMEMory:STORe
:SYSTem:PRINt:COPY
:SYSTem:BEEPer:SET
*RST
:SYSTem:MMEMory:RECall
:SYSTem:DISPlay:ALARm
:SYSTem:MMEMory:STORe
:SYSTem:PRINt:COPY
*RST
:SYSTem:MMEMory:RECall
Chapter 3 Message List
3.2 Correspondence Between Panel and Messages
This section explains correspondence between panel and messages.
3.2.1 Messages corresponding to common operations
Figure 3.2.1-1 Messages Corresponding to Common Operations
Figure 3.2.1-2 Messages Corresponding to System Menu (MP210xA, MP2100B)
3-4
Figure 3.2.1-3 Messages Corresponding to System Menu (MP2110A)
3.2 Correspondence Between Panel and Messages
Message List
SYSTem:ERRor:HCLear
:SYSTem:ERRor:HISTory?
:SYSTem:DISPlay:ALARm
:SYSTem:INFormation:ERRor?
3
Figure 3.2.1-4 Messages Corresponding to System Alarm Dialog Box (MP210xA, MP2100B)
3-5
:OUTPut:DATA:AMPLitude
:OUTPut:DATA:OUTPut
:SOURce:PATTern:TYPE
:OUTPut:BITRate:OFFSet
:OUTPut:BITRate:STANdard
:OUTPut:BITRate
:OUTPut:DATA:RELative?
:OUTPut:DATA:ATTFactor
:SOURce:MMEMory:PATTern:
RECall
:SOURce:PATTern:DATA:
LENGth?
:SOURce:PATTern:LOGic
:OUTPut:BITRate:DIVRate
:OUTPut:CMU:EXTClock
:OUTPut:RCLock
:OUTPut:SYNC:SOURce
:SOURce:PATTern:EADDition:SET
:SOURce:PATTern:EADDition:VARiation
:SOURce:PATTern:EADDition:RATE
:SOURce:PATTern:EADDition:SINGle
:OUTPut:RCLock:STATu s ?
:OUTPut:RCLock:APPLy
:OUTPut:RCLock:SELect
Chapter 3 Message List
3.2.2 Messages corresponding to PPG/ED
When controlling PPG/ED, add :BERT[<ch>] to the beginning of the
message header or specify a channel using the :MODule:ID command.
Refer to Section 3.5, “Specifying Module and Channel” for details.
3-6
Figure 3.2.2-1 Messages Corresponding to PPG Panel (MP210xA,
MP2100B)
Message List
:INPut:DATA:INTerface
:INPut:DATA:THReshold
:SENSe:PATTern:TYPE
:INPut:BITRate:STANdard
:INPut:BITRate
:INPut:DATA:ATTFactor
:SENSe:MMEMory:PATTern:
RECall
:SENSe:PATTern:DATA:LENGth?
:SENSe:PATTern:LOGic
:SENSe:MEASure:EALarm:STARt?
:SENSe:MEASure:EALarm:ELAPsed?
:SENSe:MEASure:EALarm:TIMed?
[:BERT:ALL]:CALCulate
:DATA:EALarm?
:SENSe:PARam:TRACking
:INPut:BITRate:DIVRate?
:SENSe:MEASure:EALarm:STOP?
[:BERT:ALL]:CALCulate:DATA:MONitor?
[:BERT:ALL]:SENSe:MEASure
:EALar
[:BERT:ALL]:SENSe:MEASure:
STARt
[:BERT:ALL]:SENSe:MEASure:
STOP
[:BERT:ALL]:SENSe:
MEASure:IMMediate?
[:BERT:ALL]:DISPlay:RESult
:EALarm:HRESet
3.2 Correspondence Between Panel and Messages
3
m : STATe ?
Figure 3.2.2-2 Messages Corresponding to ED Panel–1 (MP210xA, MP2100B)
3-7
Chapter 3 Message List
:SENSe:PATTern:SYNC:ASYNc
:SENSe:PATTern:SYNC:THReshold
:SENSe:PATTern:SYNC:PSMode
:SENSe:PATTern:SYNC:FPOSition
:OUTPut:SYNC:SOURce
:SENSe:MEASure:EALarm:MODE
:SENSe:MEASure:EALarm:PERiod
:DISPlay:RESult:EALarm:MODE
Figure 3.2.2-3 Messages Corresponding to ED Panel–2 (MP210xA, MP2100B)
3-8
3.2 Correspondence Between Panel and Messages
Message List
:OUTPut:DATA:AMPLitude
:OUTPut:BITRate:OFFSet
:OUTPut:DATA:ATTFactor
:SOURce:PATTern:LOGic
:SENSe:PATTern:LOGic
:SENSe:MEASure:EALarm:STARt?
:SENSe:MEASure:EALarm:ELAPsed?
:SENSe:MEASure:EALarm:TIMed?
:SENSe:MEASure:EALarm:STOP?
[:BERT:ALL]:SENSe:MEASure:
EALarm:STATe?
[:BERT:ALL]:CALCulate:DATA:MONitor?
:INPut:DATA:ATTFactor
:INPut:DATA:THReshold
:SENSe:PATTern:TYPE
:INPut:DATA:INTerface
:OUTPut:DATA:RELative?
:OUTPut:DATA:OUTPut
:SOURce:PATTern:TYPE
[:BERT:ALL]:CALCulate:D
ATA:EALarm?
:SENSe:PARam:TRACking
:OUTPut:BITRate:STANdard
:DISPlay:RESult
:OUTPut:BITRate
:OUTPut:BITRate
:OUTPut:RCLock:APPLy
:OUTPut:RCLock:STATu s ?
[:BERT:ALL]:SENSe:MEASure:
STARt
[:BERT:ALL]:SENSe:MEASure:
STOP
[:BERT:ALL]:SENSe:M
EASure:IMMediate?
[:BERT:ALL]:DISPlay:RESult:E
ALarm:HRESet
[:BERT:ALL]:CALCulate:DATA:MONitor:HISTory?
3
Figure 3.2.2-4 Messages Corresponding to PPG/ED Panel–1 (MP2110A)
3-9
:SENSe:MEASure:EALarm:MODE
:DISPlay:RESult:EALarm:MODE
:SENSe:MEASure:EALarm:PERiod
:OUTPut:SYNC:SOURce
:OUTPut:RCLock
:OUTPut:CLOCk:DIVRate?
:SOURce:PATTern:EADDition:SINGle
:OUTPut:CLOCk:SOURce:CHANnel
Chapter 3 Message List
Figure 3.2.2-5 Messages Corresponding to PPG/ED Panel–2 (MP2110A)
3-10
3.2 Correspondence Between Panel and Messages
Message List
[:BERT:ALL]:SENSe:MEASure:STARt
[:BERT:ALL]:SENSe:MEASure:STOP
[:BERT:ALL]:SENSe:MEASure:IMMediate?
[:BERT:ALL]:CALCulate:DATA:MONitor?
3
Figure 3.2.2-6 Messages Corresponding to All BER Measurement-1
3-11
[:BERT:ALL]:CALCulate:DATA:EALarm?
[:BERT:ALL]:DISPlay:RESult:EALarm:HRESet
[:BERT:ALL]:SENSe:MEASure:EALarm:STATe?
Chapter 3 Message List
Figure 3.2.2-7 Messages Corresponding to All BER Measurement-2
3-12
3.2 Correspondence Between Panel and Messages
Message List
:CALCulate:OPTical:STATus?
:SOURce:OPTical:SIGNal:OUTPut
:SOURce:OPTical:SIGNal:WLENgth?
:SOURce:OPTical:XFP:REFClock
3.2.3 Messages corresponding to XFP/SFP+ (MP210xA, MP2100B)
When controlling XFP/SFP+, add :PMODule to the beginning of the
message header or send :MODule:ID 3 first. Refer to Section 3.5,
“Specifying Module and Channel” for details.
3
Figure 3.2.3-1 Messages Corresponding to XFP/SFP+ Panel
3-13
:CONFigure:EXRCorrection
:CALibrate:CGain
:INPut:WAVLength
:INPut:FILTer
:INPut:FILTer:ENABle
:CALibrate:AUTocorrect
:CONFigure:EXRCorrection:FACTor
:CALibrate:SYSTem:CGain
:CALibrate:RESPonsivity
:CALibrate:CALPower
:CALibrate:OEPower[:JUDGe]
Chapter 3 Message List
3.2.4 Messages corresponding to O/E (MP210xA, MP2100B)
When controlling O/E, add :OE to the beginning of the message header or
send :MODule:ID 4 first. Refer to Section 3.5, “Specifying Module and
Channel” for details.
Figure 3.2.4-1 Messages Corresponding to O/E Panel
When controlling Scope, add :SCOPe to the beginning of the message
header or send :MODule:ID 5 first. Refer to Section ,3.5, “Specifying
Module and Channel” for details.
3.2.5.1 Result Window
3
TEQualizer][:{CHA|CHB|CHC|CHD|A
LL}]
Figure 3.2.5.1-1 Messages Corresponding to Scope Panel (MP2110A)
3-15
:DISPlay:WINDow:AUTOscale
:SAMPling:STATus
:DISPlay:WINDow:GRAPhics:CLEar
:DISPlay:WINDow:Y:DIVision:
{CHA|CHB}
:INPut:{CHA|CHB}
:DISPlay:WINDow:X:OFFSets
:DISPlay:WINDow:X:BITs
:DISPlay:WINDow:Y:OFFSets
:{CHA|CHB
:INSTrument:WAV:CONDition?
Chapter 3 Message List
}
Figure 3.2.5.1-2 Messages Corresponding to Scope Panel (MP210xA, MP2100B)
3.2.7 Messages with no corresponding panel operation
Command messages with no corresponding panel operation are listed
below.
For messages corresponding to the status registers, refer to 2.8.4
“Operation Status Register” and 2.8.5 “Device Dependent Registers”.
Table 3.2.7-1 Messages with No Corresponding Panel Operation (SCPI)
Command Details
3-42
3.3 Messages Corresponding to Common Operations
Message List
3.3 Messages Corresponding to Common Operations
3.3.1 Setting system configuration
TRM
Function
This command sets and queries the type of terminator of the response
data.
Syntax
{TRM|:SYSTem:TERMination} 0|1
{TRM|:SYSTem:TERMination}?
Parameter
0 LF+EOI (default)
1 CR+LF+EOI
LF (Line Feed) is 0x0A in ASCII.
CR (Carriage Return) is 0x0D in ASCII.
EOI (End or Identify) is a GPIB interface signal indicating the end of
data.
Response Data
0|1
Example of Use
To set the terminator type to LF+EOI:
TRM 0
TRM?
>TRM 0
GTL (Go to local)
Function
Added in Version 5:
and changes the status to Local.
Example of Use
GTL
This command releases the remote connection status
3
3-43
Chapter 3 Message List
:SYSTem:BEEPer:SET
Function
Only in MP210xA and MP2100B:
buzzer ON/OFF.
Syntax
:SYSTem:BEEPer:SET <enable>
:SYSTem:BEEPer:SET?
Parameter
0|OFF
1|ON
Response Data
0|1
Example of Use
To set buzzer ON:
:SYST:BEEP:SET ON
:SYST:BEEP:SET?
>1
Note:
When this command is used in MP2110A, an error (–113 Undefined
Header) occurs because MP2110A does not support this command.
This command sets and queries the
3-44
Loading...
+ hidden pages
You need points to download manuals.
1 point = 1 manual.
You can buy points or you can get point for every manual you upload.