OST User Manual

10 Gb/s Optical Standards Test System
User’s / Programmer’s Manual
August 15, 2005

Version 6.X CIRNOS
Circadiant Systems, Inc.

7660 Imperial Way
Suite C-103
Allentown, PA 18195-1016
i
Copyright Circadiant Systems, Inc., 2005. All rights reserved. Reproduction, adaptation, or translation
without prior written permission is prohibited, except as allowed under copyright laws.
Printed in the USA.
Notice. The information contained in this document is subject to change without notice. Companies,
names, and data used in examples are fictitious unless otherwise noted. Circadiant makes no
warranty of any kind with regard to this material, including but not limited to the implied warranties
of merchantability and fitness for a particular purpose. Circadiant shall not be liable for errors
contained herein or for incidental or consequential damages in connection with the furnishing,
performance, or use of this manual.
ii
Warranty
General. All Circadiant Products and Services (including all Circadiant Software) are warranted
against defects in material and workmanship for one year from the date of shipment by Circadiant
("Warranty"). If any Circadiant Product or Service has a defect in material or workmanship during the
Warranty period, please contact Circadiant at (610) 871-0500 or (866) 871-2500 for help. For repair
service, Customer is responsible for any shipping charges, freight, insurance and proper packaging to
prevent breakage in transit to and from Circadiant, except that Circadiant will be responsible for the
same to return to Customer a Product or Service repaired or replaced under Warranty. All shipments
of repaired or replaced Products or Services by Circadiant will be F.O.B. at the Circadiant facility. In
the unlikely event that a Product or Service under Warranty cannot be repaired or replaced, Circadiant
in its sole discretion may refund Customer's purchase price actually received for the Product or
Service, and all further obligations of the parties for that Product or Service will be deemed
terminated.
Disclaimer of Warranties. THE WARRANTY EXPRESSLY STATED IN THIS AGREEMENT IS

THE ONLY WARRANTY PROVIDED BY Circadiant TO CUSTOMER. Circadiant DISCLAIMS
ALL OTHER WARRANTIES, EXPRESS OR IMPLIED, INCLUDING ANY WARRANTIES OF
QUIET ENJOYMENT, MERCHANTABILITY, TITLE, ACCURACY, OR FITNESS FOR A
PARTICULAR PURPOSE.
Limitation. The Warranty does not apply to defects or problems resulting from any actions or
omissions by Customer or others, such as mishandling, improper interfacing, operation outside of
design limits, misapplication (including use with hardware or software not manufactured or approved
by Circadiant), improper repair, unauthorized modification, or mis-calibration. Circadiant will not be
liable for any damages in excess of the purchase price actually paid by Customer for the Product or
Service provided by Circadiant. In no event will Circadiant be required to pay or reimburse any
manufacturing costs, lost profits, goodwill, or any indirect, special, incidental or consequential
damages, whether based on contract, tort or other legal theory. Circadiant shall not be liable for
normal manufacturing defects or customary variances from specifications.
Special Conditions. Circadiant’s Products and Services (including Circadiant Software) are not
fault-tolerant, and they may not be used in the operation of nuclear facilities, aircraft navigation or
communication systems, air traffic control, direct life support machines or weapons systems, or for
any other use in which the failure of the Product or Service could lead to or cause death, personal
injury or severe physical or environmental damage ("Unauthorized Uses"). Customer indemnifies and
hold harmless Circadiant, its suppliers, and their respective officers, directors, employees, agents,
affiliates, successors and assigns against all claims, costs, damages and expenses (including attorneys'
and expert witness' fees) arising out of or in connection with any Unauthorized Use or any claim for
property damage, personal injury or death associated with any use of a Product or Service, even if
such claim alleges that Circadiant was negligent regarding the design, manufacture or provision of the
Product or Service.
Service and Software License. "Software" means computer programs developed or owned by
Circadiant that have been provided by Circadiant to Customer as part of a Product or Service,
including all associated user documentation. Customer is granted a non-exclusive, non-transferable
right and license to use any Circadiant Service or Circadiant Software for Customer's internal
business purposes only. Customer may not (i) assign, transfer, sublicense, lease, rent or engage in any
time-sharing of the Software; (ii) modify or create any derivative works of the Software; or (iii)
reverse engineer, decompile or otherwise attempt to extract the source code of the Software. For any
Software embedded in a Product, Customer may transfer its license rights to the embedded Software
solely in connection with a sale or other transfer of the Product in which the Software is embedded.
iii
Customer shall use all reasonable efforts to keep any non-public portions of all Services and Software
confidential, and shall not disclose non-public portions of the Services or Software to third parties
other than the Customer's affiliates, agents and consultants who have agreed in writing to comply
with the obligations of confidentiality pursuant to this Agreement. Customer's right to use the
Services or Software under this Agreement may be terminated for a material breach of the
aforementioned limitations.
iv
General Safety Information
Warning. The WARNING sign denotes a hazard. It calls attention to a procedure which, if not
correctly performed or adhered to, could result in injury or loss of life. Do not proceed beyond a
warning sign until the indicated conditions are fully understood and met.
Caution. The CAUTION sign denotes a hazard. It calls attention to a procedure which, if not
correctly performed or adhered to, could result in damage to or destruction of the product. Do not
proceed beyond a caution sign until the indicated conditions are fully understood and met.
This product has been designed and tested in accordance with IEC Publication 61010-1, Safety
Requirements for Electrical Equipment for Measurement, Control, and Laboratory Use, and has been
supplied in a safe condition. The instruments documentation contains information and warnings that
must be followed by the you to ensure safe operation and to maintain the product in a safe condition.
WARNING: If this instrument is not used as specified, the protection provided by the equipment
could be impaired. This instrument must be used in a normal condition (in which all
means for protection are intact) only.
WARNING: To prevent electrical shock, disconnect the instrument from its power supply before
cleaning. Use a dry cloth or one slightly dampened with water to clean the external
case parts. Do not attempt to clean internally.
WARNING: This is a Safety Class 1 M product (provided with a protective earthing ground
incorporated in the power cord). The mains plug shall only be inserted in a socket
outlet provided with a protective earth contact. Any interruption of the protective
conductor inside or outside of the product is likely to make the product dangerous.
Intentional interruption is prohibited.
WARNING: Complies with 21 CFR 1040.10 and 1040.11 except for deviations pursuant to Laser
Notice No. 50, dated January 2001. It is designated Class 1 M according to IEC
60825-1 Edition 1.2: 2001-08.
WARNING: No operator serviceable parts inside. Refer maintenance and servicing to qualified
personnel.
WARNING: Do not operate the unit if external moisture is present. Use a clean cloth to dry the
external case parts. No liquids should be permitted near the instrument.
WARNING: Do not look (with the naked eye, fiberscope, or any other device) into any optical
output or any fiber/device attached to the output while the laser is in operation.
WARNING: Always disconnect both ends of fiber optic cables before visually inspecting the fiber
ends. Always disable all optical sources before removing the fiber optic cables.
v
WARNING: Do not enable the laser when no fiber or a device is connected to the A3308.
CAUTION: This instrument operates on 24 V DC input. Always use the power supply and cable
assembly shipped with this instrument.
CAUTION: This instrument requires an ambient temperature of 0 to 35oC. Do not block the intake
or outlet cooling fans. Do not vent warm air from other equipment near the intake fan
of the A3308.
CAUTION: This unit is not a handheld instrument.
CAUTION: This unit is for indoor use only.
CAUTION: Fiber optic connectors are easily jeopardized by dirty or damaged accessories and
cables. Expensive instrument repairs, damaged cables, and compromised
measurements are risked by attaching items which are flawed or dirty.
CAUTION: Always use the shielded AC mains to power supply cable shipped with this instrument.
CAUTION: Always use the cable between the OSTís power supply and the OST shipped with this
instrument.
CAUTION: Always use the power supply cable assembly between the A3301 and the A3308
shipped with this instrument.
CAUTION: Always use the shielded Ethernet cable assembly between the A3301 and the A3308
CAUTION: Always use the shielded Ethernet cable assembly between the A3308 and the A3318
vi
Keep the connectors and fibers clean. It is extremely important to keep the fibers used for
testing and the connectors of the 10 Gb/s Optical Standards Test System clean. This will help to
insure repeatable and accurate measurements as well as avoid costly repairs. One possibility for
viewing the conditioning of the fiber and the connectors on the 10 Gb/s OST System is to use a
Westover Scientific fiberscope with adaptor probes:
FBPT-SC-FK- Modified SC Bulkhead Adapter Probe Tip
FMA-U25 - Universal 2.5 mm Adapter Probe Tip
These adapter probe tips will enable you to view the fibers on the 10 Gb/s OST System without
removing the interchangeable connector.
Laser Classification
The Circadiant A3308 is a Class 1M laser product with Class IIIB laser radiation. The laser emits
invisible laser radiation at 1550 ± 20 nm wavelength. The total power of light energy radiated out of
the instrument is less than 12 dBm. Operator precautions are necessary to maintain safety. Observe
all caution and warning procedures.
The Circadiant A3318 850 nm/Electrical OST Interface is a Class 1M laser product with Class 1M
laser radiation. The laser emits invisible laser radiation at 850 nm and at 1310 nm wavelengths. The
total power of light energy radiated out of the instrument is less than 0 dBm at 850 nm and is less than
+12 dBm at 1310 nm. Operator precautions are necessary to maintain safety. Observe all caution and
warning procedures.
vii
viii
Table of Contents
Chapter 1: Introduction .......................................................................1
1.1 Product Overview ......................................................................................1
1.2 Accessories ................................................................................................2
1.3 A3308 10 Gb/s Optical Standards Tester Setup and Installation ..............2
1.4 A3318 850 nm/Electrical OST Interface Setup and Installation ...............2
1.5 Connecting to a LAN .................................................................................2
1.6 Printer Configuration .................................................................................3
1.7 Help ...........................................................................................................4
Chapter 2: Instrument Overview ........................................................5

2.1 A3308 10 Gb/s Optical Standards Tester Front Panel ..............................5
2.2 A3308 10 Gb/s Optical Standards Tester Rear Panel ..............................10
2.3 A3308 10 Gb/s Optical Standards Tester Touch Screen Interface ..........12
2.4 A3318 850 nm/Electrical OST Interface Front Panel ..............................15
2.5 A3318 850 nm/Electrical OST Interface Rear Panel ...............................17
2.6 Layer 1 Tests ...........................................................................................17
2.7 SONET/SDH Features .............................................................................19
2.8 10 GE LAN/WAN Features .....................................................................19
2.9 PoS Features ............................................................................................19
2.10 OTN Features ........................................................................................20
2.11 Testing 1310 nm Devices ......................................................................20
Chapter 3: Signal Configuration .......................................................21

3.1 Traffic Configuration ...............................................................................21
3.2 Mode Selection .......................................................................................30
3.3 Stressed Eye and Other Degradations (Optics) .......................................32
3.4 Switch Setup ............................................................................................36
3.5 Clock Settings ..........................................................................................43
3.6 Operating the Transmit Section of the A3308 .........................................44
3.7 RX Operations .........................................................................................48
3.8 Bit Error Rate Testing and the BERT Bar ...............................................48
Chapter 4: Other Modes ....................................................................55

4.1 IntelliScriptTM ........................................................................................55
4.2 External Instrument Control ....................................................................58
4.3 Internal Process Control ..........................................................................65
4.4 Admin ......................................................................................................70
Chapter 5: RX Tests ..........................................................................81
ix
5.1 Sensitivity ................................................................................................82
5.2 Overload ................................................................................................108
5.3 BER vs. OSNR ......................................................................................111
5.4 IsoBER ...................................................................................................113
Chapter 6: TX Tests ........................................................................117

6.1 Path Penalty (Dispersion Penalty) .........................................................117
6.2 Internal Sensitivity .................................................................................121
6.3 DUT TX Power .....................................................................................122
Chapter 7: SONET/SDH Tests .......................................................125

7.1 Transmit Features ..................................................................................125
7.2 SONET/SDH BERT Bar Monitoring ....................................................129
7.3 SONET/SDH Statistics & Error Injection Control ................................130
7.4 Statistics .................................................................................................135
Chapter 8: PoS Tests .......................................................................137

8.1 PoS .........................................................................................................137
8.2 PoS Statistics & Error Injection Control ...............................................140
Chapter 9: OTN Tests .....................................................................143

9.1 OTN Traffic Configuration ....................................................................143
9.2 OTN Statistics and Error Monitoring ....................................................144
9.3 Transmit Features ..................................................................................145
Chapter 10: 10GE LAN/WAN Tests ..............................................147

10.1 10GE LAN/WAN ................................................................................147
10.2 802.3 Statistics & Error Injection Control ...........................................151
Chapter 11: Remote Operation .......................................................155

11.1 Remote Database Access using ODBC ...............................................155
11.2 SCPI Control ........................................................................................156
11.3 Generalized Programming Flow Example ...........................................158
Chapter 12: Debug Station ..............................................................167

12.1 Introduction .........................................................................................167
12.2 Hardware Setup ...................................................................................167
12.3 Configuring the Debug Station Application ........................................168
12.4 Running the Debug Station Application ..............................................172
12.5 Test Sequence ......................................................................................176
12.6 Troubleshooting ...................................................................................179
12.7 Debug Station Web Results Access .....................................................180
x
Chapter 13: SCPI Commands .........................................................183
13.1 SCPI Command Set .............................................................................183
13.2 SCPI Return Codes .............................................................................259
Chapter 14: Quick Start Guides ......................................................263

14.1 A3308 10 Gb/s Optical Standards Tester ............................................264
14.2 A3318 850 nm/Electrical OST Interface .............................................271
Chapter 15: Procedures ...................................................................277

15.1 Cleaning the OST Optical Interfaces ...................................................278
15.2 1550 nm/1310 nm Wavelength Calibration .........................................282
15.3 Cleaning the OST Airflow Fans ..........................................................290
Chapter 16: Application Briefs .......................................................293

16.1 Stressed Receiver Conformance Testing .............................................294
16.2 Optical Sensitivity Testing ..................................................................296
16.3 BER vs. OSNR Testing .......................................................................298
16.4 Path Penalty Testing ............................................................................300
16.5 Transmitter Optical Output Power Testing .........................................302
16.6 Optical Overload Testing .....................................................................304
16.7 Debug Testing of Manufacturing Rejects and Customer Returns .......306
16.8 Test Set Calibration .............................................................................308
16.9 Transmitter Functional Testing ...........................................................310
16.10 IntelliScriptTM Testing .....................................................................312
16.11 IntelliTimeTM Testing ......................................................................314
16.12 IntelliPassTM Testing ........................................................................316
16.13 Golden Transmitters ..........................................................................318
Chapter 17: Technical Briefs ..........................................................321

17.1 OSNR ...................................................................................................322
17.2 BER vs. OSNR ....................................................................................328
17.3 Sensitivity Measurement Algorithms ..................................................332
17.4 Straight-Line BERTM Plots ..................................................................337
Chapter 18: Glossary of Acronyms ................................................345

18.1 Glossary of Acronyms .........................................................................345
Index .............................................................................................. 357
xi
xii
CHAPTER 1 Introduction
As more and more international standards require systems be tested with real-world signals, such as
the IEEE 802.3ae 10 GigE standard, it becomes important that the system building blocks also
perform properly with real-world signals. Like links on a chain, every component must handle the
stresses and strains of real-world conditions or the overall system will not pass the real-world tests
mandated by these new international standards. The 10 Gb/s OST System enables you to
automatically and thoroughly test components, modules, line cards, and systems with a variety of
protocols, in numerous test configurations, and with applied real-world signal degradations that,
when combined with unprecedented test repeatability, gives you exceptional confidence in your test
results.
This manual covers all A3308 10 Gb/s Optical Standards Tester, A3301 OST System Controller, and
A3318 850 nm/Electrical OST Interface product variations. However, not all features and options are
active in each model. In some cases, features and options are visible but grayed out, making them
inactive.
1.1 Product Overview

The 10 Gb/s OST System enables you to accomplish essential single mode and multi-mode physical
layer tests. These tests include: Optical Sensitivity, Optical Overload, Optical Path Penalty, Optical
Modulation Amplitude, Extinction Ratio, IsoBER and Stressed Receiver Conformance tests. In
addition to its unique physical layer capabilities, the instrument performs SONET/SDH protocol
(Layer 2) and PoS, 10 Gb/s Ethernet traffic (Layer 3) tests. It can generate SONET/SDH frames,
monitor/change key SONET overhead parameters, generate and detect SONET/SDH alarms and
errors, and load the SONET payload with 10GE WAN frames or IP packets. At Layer 3 it can
generate IP/10GE LAN and WAN traffic at full line rate and maintain detailed packet statistics on
transmission performance. These testing capabilities are combined with the ability to degrade the
signal to worst case conditions providing a higher degree of confidence in the equipment shipped.
Complex multilayer protocol tests are generated automatically and the results are plotted in patent-
pending formats.
1
Introduction
1.2 Accessories
The 10 Gb/s Optical Standards Test System consists of an A3301 OST System Controller and an
A3308 10 Gb/s Optical Standards Tester. In addition, the 10 Gb/s OST System ships with the
following items:
• AC/DC converter
• Keyboard
• Mouse
• User’s/Programmer’s manual (this manual)
• Miscellaneous cables and dust covers
• Memory Stick
The A3318 850 nm/Electrical OST Interface operates in conjunction with the A3308 10 Gb/s Optical
Standards Tester. Accessories that ship with the A3318 include:
• Ethernet cable to connect between the A3318 and A3308
• Power cord
• Optical fiber jumper cables: FC-LC (50/125 µ m, FC-LC (62.5/125 µ m), FC-SC (50/125 µ m),
FC-SC 62.5/125 µ m), and two FC-FC (single mode)
• 50 Ohm coax cable
• Laser on/off key
1.3 A3308 10 Gb/s Optical Standards Tester Setup and

Installation
See CHAPTER 14 Quick Start Guide for the A3308 10 Gb/s Optical Standards Tester.
1.4 A3318 850 nm/Electrical OST Interface Setup and

Installation
See CHAPTER 14 Quick Start Guide for the A3318 850 nm/Electrical OST Interface.
1.5 Connecting to a LAN

Printing screen shots and test results to a network printer, remote access of the OST via ethernet and
read access to the database via ODBC are some of the features available to you when the 10 Gb/s
OST System is connected to a LAN. The 10 Gb/s OST System can also be controlled using SCPI
commands over a LAN. The 10 Gb/s OST System when connected to a LAN, will automatically
detect the network settings requirements and configure the appropriate settings. To make the external
network connections, simply plug in the external network cable, activate the port via the “Admin”
screen, and set the IP address. To connect the 10 Gb/s OST System to the LAN for one of these
2
Printer Configuration
purposes simply connect the 10/100 Remote Control port on the A3301 to the network (see Figure 1-
1). The connection from the A3301 to the A3308 remains the same. Power up the 10 Gb/s OST
System.
10/100 IN
LAN
TO OST
A3301
TO OSTC
A3318
TO OST
TO OST
A3308
FIGURE 1-1: 10 Gb/s OST System Connected to a LAN
1.6 Printer Configuration

The 10 Gb/s OST System is capable of printing most of the screens (including setup and test results)
to either a local or a network printer. Follow the steps below to install a printer for the type of
connection desired. To add a printer you will need to attach a keyboard to the system. To attach a
keyboard simply plug the supplied keyboard into the PS2 keyboard connection on the A3301.
Adding a Printer. To install either a “Local Printer” or a “Jet Direct” printer use the following
procedure. The “Local Printer” can be connected to either the parallel port or the USB port of the
A3301. A “Jet Direct” printer is a network printer. To Install a “Jet Direct” printer the 10 Gb/s OST
System must first be connected to the network, then the printer can be installed. Follow the
instructions for connecting to a network before you attempt to install a “Jet Direct” (network) printer.
1. To install a “Local Printer” connect the printer to either the parallel port or the USB port of the
A3301.
2. To Install a “Jet Direct” Printer connect the 10 Gb/s OST System to the network. Power up the
printer and the 10 Gb/s OST System.
3. Select the ADMIN tab on the bottom of the A3301 display.
4. Click on the SELECT PRINTER icon and a window will appear showing any printer currently
configured for this system.
5. Click on the NEW icon and an “Add A New Printer Queue” Dialog window will appear.
6. Click on the NEXT box and the “Set the Print Queue Name and Type” window will be displayed.
This is where the type of printer name and type of connection are selected.
7. In the “Queue Name” box enter a name for the printer.
3
Introduction
8. Next Select the type of connection “Queue Type”. The two types of connections described in this
manual are either “Local Printer” or “Jet Direct”. Follow either the “Local Printer or “Jet Direct”
printer procedure below to complete the installation.
Local Printer. Select the “Local Printer” button and press Next. This will open the “Configure a
Local Printer” window.
1. Under device it will display /dev/lp0 and under Model it will display the printer manufacturer and
model.
2. If this is ok press next. This will open the “Select a Print Driver” window.
Jet Direct Printer. Select the “Jet Direct” button and press next. This will open the “Configure a Jet
Direct Printer” dialog box.
1. Enter the IP address of the printer you are adding.
2. Scroll down the list until you find the manufacturer of the printer being installed.
3. Click on that symbol next to the manufacturer and a list of printers will appear.
4. Scroll down until you find the model of the printer. Click on the symbol next to that model
number, and a list of drivers will appear.
5. Most of the time the first driver in the list is the best driver for printer. Select the driver and press
next. This will bring you to the “Finish and Create the New Print Queue” window.
6. The printer and driver just entered will be displayed in the window. If this is correct select finish.
This will bring you back to the “Select Printer” window, listed in the window should be the printer
just added.
7. To the left of the printer should be a check mark indicating this is the default printer. If you have
more than one printer configured it may not be the default printer. To make it the default printer,
highlight the printer and click on “Default” and they “Apply”.
8. A message stating “lpd restart succeeded” will appear. Click “ok”.
9. To verify the printer was configured properly and the driver is working, click on “Test”. Select the
appropriate type of test page for the desired language or country.
10. If it is a color printer there will be color in the printout. Verify the printout is correct.
11. If the printout is correct select “File”, “Exit” to return to normal operation of the unit.
1.7 Help
Touching the Help button in the bottom left corner of the GUI will display this manual. Additional
help may also be obtained by calling Circadiant Systems, Inc. at (610) 871-0500 or (866) 871-2500
during normal business hours, or (866) 630-2510 for emergency technical product support after
business hours.
4
CHAPTER 2 Instrument Overview
The 10 Gb/s Optical Standards Test System provides optical component and network equipment
makers with a purpose-built, intelligent optical test system, capable of generating, detecting, and
testing PRBS, SONET/SDH, PoS, 10 GE LAN, and 10 GE WAN traffic. The 10 Gb/s OST System
uniquely automates, consolidates, and intelligently analyzes everyday standard tests critical to the
quality and reliability of products through a single, compact solution. This Chapter provides a brief
overview of each of components that make up the 10 Gb/s OST System and their features.
2.1 A3308 10 Gb/s Optical Standards Tester Front Panel

The front panel of the A3308 10 Gb/s Optical Standards Tester contains input and output connectors
necessary for normal testing operation. Status indicator LEDs enable you to see at a glance if normal
conditions prevail. Figure 2-1 shows the front panel of the A3308. A description of each numbered
part is given below.
1. POWER Push Button. This button is a lighted power switch for the A3308 module only. When
the module is off, pressing this button will start the power up and initialization process. The switch
will light red during most of the power up cycle, before going through a series of blinking lights and
finally to a steady green when initialization is complete. When a shut down has been initiated, the
switch will blink orange until the device completes the shutdown.
During normal operation, the power push button should not be used to shut down the device. A
software initiated shutdown from the administration screen on the A3301 display is recommended.
However, pressing the power button when the module is in the ready state will also initiate a shut
down. Alternatively, as with a PC, if you hold down this power button for 5 seconds, the device will
immediately shut down.
2. SUBNET Ethernet Port LEDs. These LEDs correspond to 10/100 BaseT Ethernet ports on the
instrument and indicate whether an Ethernet connection has been detected (LINK row) and whether
there is activity on that connection (DATA row). The LINK row lights green while the DATA row
lights amber.
Each pair of LEDs refers to a specific ethernet port. The first three pairs are dedicated to the Ethernet
subnet used exclusively for internal communication within the Circadiant series of test instruments.
5
Instrument Overview
The first two pairs refer respectively to input and output RJ45 ethernet ports on the rear panel which
are used to connect the A3308 to the local Circadiant subnet in a daisychain fashion. Note that the IN
(upstream) port must be connected to a module chain that begins with the A3301 control module. The
OUT port may be used to connect additional Circadiant modules to the local controller. The third pair
(INT) refers to an ethernet connection internal to the A3308. They indicate if data is being transferred
into or out of this module from/to the data stream.
2 10
11
12
3
4
5 13
6
7 14
8
15
16
17
FIGURE 2-1: Front Panel of the A3308
During normal operation, the LINK lights must be illuminated on the IN and INT ports with the
DATA lights flashing irregularly due to command traffic. The OUT port LEDs will behave similarly
if downstream modules are connected.
3. START/STOP, I/O Connectors and A/B EVENT LEDs. User defined digital I/O traffic may be
connected to these SMA connectors for timing purposes. The input cable impedance must be 50
6
A3308 10 Gb/s Optical Standards Tester Front Panel
ohms. The output signal is TTL. If the connector is configured as an input, the LED will light steady
green. If the connector is configured as an output, the LED will light steady red. The LED will flash
off if an event is detected/generated.
4. 1 Hz Clock Connectors. Reserved for future expansion.
5. 8 kHz Clock, RX OUT Connector. An 8 kHz BITS (Building Integrated Time Source) clock
derived from the incoming OC-192c/STM-64c optical signal is supplied at the RX OUT connector.
The connector is 50 ohm terminated; the signal is AC-coupled, 0.6 V peak to peak.
6. 8 kHz Clock, TX IN Connector and LED. An external, DC coupled, TTL/LVTTL 8 kHz BITS
clock signal may be connected via the TX IN SMA connector. If connected, this signal can be used to
clock the A3308 transmitter. If this clock has been selected for timing the ACTIVE LED will light to
indicate that a clock signal must be available here.
7. TRIG OUT Connector and Corresponding LEDs. The TRIG OUT connector is used primarily
to supply a trigger signal to an external oscilloscope. You can configure this output to supply a 155.52
MHz, 161.13 MHz, or a 167.33 MHz clock signal synchronous with either the RX clock or the TX
clock—the LEDs will indicate which clock has been selected. The output signal is typically 0.6 V
peak to peak. The connector is 50 ohm terminated. Note that the receive and transmit sides of the
instrument may operate within two distinct clock domains. Configure this output appropriately when
using this signal as a trigger for an external instrument (e.g. an oscilloscope measuring eye diagrams).
8. TX REF IN Connector and LED. An external, 50 ohm terminated, AC-coupled, 155.52 MHz,
161.13 MHz, or a 167.33 MHz clock may be connected via this TX IN connector. The input signal
must be 0.2 V - 1.0 V peak to peak and the input is 50 ohm terminated. This signal can be used to
clock the A3308 transmitter. If this clock has been selected for timing the ACTIVE LED will light to
indicate that a clock signal must be available here.
9. LASER CONTROL Key and LASER STATUS LED. Laser safety interlock key for the internal
Class 1M laser. If the key is turned to DISABLE, the laser can not be powered. When the key is
turned to ENABLE, the laser may be powered if all other interlocks are cleared. (In addition to the
front panel key interlock, a remote laser safety interlock connector on the rear panel provides an
additional safety mechanism for the laser. This connector must be shorted in order for the laser to
operate.)
The LASER STATUS LED indicates the status of the internal laser. This LED will light red if either
the front panel LASER CONTROL key is turned to disable or the remote interlock connection on the
rear panel is not cleared. If all hardware interlocks have been removed but software has not enabled
the laser, the LASER STATUS LED will blink green. The LASER STATUS LED will light steady
green if and only if the laser is powered.
7
Instrument Overview
WARNING: Do not enable the laser without a fiber or equivalent device attached to the TX
OUTPUT connector.
WARNING: The Laser Control key should be turned to the DISABLE position before making or
removing any optical connections.
CAUTION: All cables and accessories should be clean and undamaged in order to protect the fiber
optic connectors.
CAUTION: When changing adapters make sure that the female end does not get
scratched/damaged
10. MODULE ADDRESS LED. This LED lights green when the A3301 addresses the A3308.
11. TX/RX Monitor Port (Optical). The monitor port is a tap of either the transmitted or the
received signal for output to an external device, such as a oscilloscope or an OSA. Selection is made
through either the Switch Setup window of the GUI or the remote interface. If the TX monitor is
selected the output power will be approximately +5 dBm. If RX monitor is selected the output will
vary depending on the power of the receive signal. It is always best to check the monitor port power
prior to connecting to any instrument.
12. OSNR Monitor Port. The OSNR monitor port is a tap of the optical transmit signal path and is
used to measure the OSNR level of either the OST’s internal transmitter or an external transmitter,
before the signal goes through the OST’s optical filter.
13. Reference Transmitter. These connectors are intended for use with proprietary signals (such as
11.1 Gb/s) or as a means to drive the device under test with your own transmitter. The ENABLED
LED will light green when traffic is routed through the connectors. Dust covers are provided for these
connectors and should be in place when the connectors are not being used. These connectors utilize
the same interchangeable optical connectors as the TX output and RX input.
8
A3308 10 Gb/s Optical Standards Tester Front Panel
NOTE: “IN” and “OUT” designate where the optical signal enters (IN) the 10 Gb/s OST
System from the TX port of the reference device and leaves (OUT) the 10 Gb/s OST
System to the RX port of the reference device.
WARNING: Do not look (with the naked eye, fiberscope or any other device) into any optical output
or any fiber/device attached to the output while an external laser connected to the
device is in operation.
14. TX OUTPUT Connector and TX Lock LED. The connector is an interchangeable single mode
optical connector which supports ST, SC, DIN, DIA, and FC connector styles using supplied
adaptors. It supplies the high speed optical signal from the internal laser. The total power of light
energy radiated out of the TX OUTPUT connector may be up to 8 mW. A laser safety dust cover is
provided for the TX OUTPUT connector. This cover must be removed when attaching cables and
should be replaced when the connector is not being used.
This bicolor LED lights green when the transmitter has locked onto the transmit clock signal. If there
is no lock, the LED will be red.
15. RX INPUT and Corresponding LEDs. This interchangeable optical connector supports ST,
SC, DIN, DIA and FC connector styles using supplied adaptors. An external transmitter may be
connected here. When an external laser is connected to RX INPUT, the EXTERNAL LOOP
OUTPUT (item # 10) connector may emit laser radiation regardless of DC power applied to the unit
or LASER CONTROL status. The total optical power radiated out of EXTERNAL LOOP OUTPUT
is dependent on the external laser connected to RX INPUT and could be 8 mW maximum.
WARNING: Always terminate the EXTERNAL LOOP OUTPUT connector or cover with cap when
RX INPUT is loaded.
The INPUT POWER LED will light green if the optical power is within safe, usable limits. If the
optical signal is below the usable limit, the LED will remain off. The LED will light red if the optical
power through RX INPUT is above the safe, usable limit.
If the receive clock has locked onto a signal of the appropriate frequency, the RX LOCK LED will
light green, otherwise the LED will be red.
The PATTERN SYNC LED will light green when the device has verified a pattern match on outgoing
and incoming signals.
The FRAME LED will light green if a SONET/SDH frame is detected and the ERRORS LED will
light red when errors in the frame or the pattern are detected.
16. Reference Receiver. These connectors are intended for use with proprietary signals (such as
11.1 Gb/s). The device connected to these ports would be used to remove the proprietary encoding
and then the standard (SONET, 10GE) signal would be analyzed by the A3308. The ENABLED LED
will light green when traffic is routed through the connectors. Safety covers are provided for these
connectors and should be in place when the connectors are not being used. These connectors utilize
the same interchangeable optical connectors as the TX output and RX input.
9
Instrument Overview
NOTE: “IN” and “OUT” designate where the optical signal enters (IN) the 10 Gb/s OST System
from the TX port of the reference device and leaves (OUT) the 10 Gb/s OST System to
the RX port of the reference device.
17. EXTERNAL LOOP Connectors. These universal optical connectors must be used together and
provide single mode ST, SC, DIN, DIA, and FC compatible connectors (using supplied adaptors) for
an external spool of fiber. These connectors are intended for use in path penalty measurements. The
ENABLED LED will light green when traffic is routed through the connectors. Safety covers are
provided for these connectors and should be in place when the connectors are not being used.
NOTE: “IN” and “OUT” are to designate where the optical signal enters (IN) and leaves
(OUT) the 10 Gb/s OST System.
WARNING: Do not look (with the naked eye, fiberscope, or any other device) into any optical
output or any fiber/device attached to the output while an external laser connected to
the device is in operation.
2.2 A3308 10 Gb/s Optical Standards Tester Rear Panel

Figure 2-2 shows the rear panel of the A3308. Power In is +24 V DC provided by an 8-pin DIN
connector power supplied from the 3301. The Emergency Shutoff power rocker switch next to the
DIN connectors affects power to this module only. Obviously, it should be used in an emergency only.
Normally the unit should be shut down through the A3301 GUI or using the power switch on the front
of the A3308.
CAUTION: Only use the power supply and power cable assembly shipped with the instrument.
1. Exhaust/Intake Fan. One fan is an exhaust fan and as such is blowing warm air out of the 10
Gb/s OST System. The other fan draws room air into the OST. The fans are covered by an EMI filter.
The filters must be installed in order to comply with standards.
CAUTION: Do not block the cooling fans on the rear panel. At least 2” of space should be available
behind the instrument.
10
A3308 10 Gb/s Optical Standards Tester Rear Panel
2
7
3
FIGURE 2-2: Rear Panel of the A3308
CAUTION: Do not vent warm air from other equipment near the intake fan of the A3308. Ambient
temperature must be 0 to 35oC.
11
Instrument Overview
2. Laser Safety Interlock. This SMA connector is used for a Laser Safety Interlock. This connector
may be used to connect the 10 Gb/s OST System to your automatic laser shut off system. This
connector MUST be shorted in order for the laser to operate.
CAUTION: Do not apply voltage to the Laser Safety Interlock port.
3. OUT RJ45 10/100 BaseT. The OUT connector is used to connect multiple Circadiant modules in
the 10 Gb/s OST System in daisy chain fashion. This output is connected to the next test modules IN
connector. This port has a corresponding LED indicator light on the front panel.
4. IN RJ45 10/100 BaseT. The IN connector is used to connect this module to the A3301 or any
other upstream device. Note that the upstream device can be any other A3308 module but the
upstream connection must begin with an A3301 for controlling purposes. This port has a
corresponding LED indicator light on the front panel.
5. Maintenance Port. This port is intended for use only by a qualified maintenance personnel.
CAUTION: Connecting a monitor or any other equipment directly into this port will result in
damage to the monitor or other equipment and possibly damage the A3308.
6. Power In. The +24V DC Power In DIN can be daisy chained from the A3301 or directly from an
AC/DC power cube.
CAUTION: An A3308 should not be powered directly from an AC/DC power cube.
7. Emergency Shutoff Power Switch. The rear panel power switch will interrupt the normal
operation of the A3308 and should not be used to power down the module. The front panel push
button will initiate a shut down procedure. Under normal operating conditions when a shutdown is
initiated from the A3301 GUI the A3308 will also shut down.
2.3 A3308 10 Gb/s Optical Standards Tester Touch Screen

Interface
The A3308 can be controlled via the touch screen interface of the A3301 or, via a GPIB interface or
an ethernet 10/100 BaseT connection from an external computer (using the standard SCPI command
set) through the A3301 command unit. For more information about the remote operation of the 10
Gb/s OST System, see CHAPTER 11. An overview of the supplied command software and GUI as
they relate to the 10 Gb/s OST System is given here. Detailed information and instructions for the
various tests can be found within CHAPTER 3 through 10.
Figure 2-3 shows a sample screenshot of the GUI interface. In this case, 10GE LAN traffic is being
generated. A description of each numbered area is given below.
12
A3308 10 Gb/s Optical Standards Tester Touch Screen Interface
3
4
5
6 7 8 9 10 11
FIGURE 2-3: Sample GUI Screenshot
1. Modes. The tabs along the top of the display screen indicate the modes of operation you may
choose. A brief description of each tab is listed below.
Test Control. The tab color green indicates that traffic is defined and started. The color yellow
indicates that traffic has not been started.
IntelliScriptTM. Enables you to define a series of separate tests. All test variables may be defined
for each test in the series. Additionally, you may control the settings of external lab instruments
through the GPIB interface. For instance, an environmental chamber may be used to allow similar
groups of tests to be run through a sequence of temperatures over the course of many hours. For more
information about these modes, see CHAPTER 5.
External Instrument Control. Enables you to control external instruments such as oscilloscopes
and OSA’s from the A3301.
Internal Process Control. Enables you to track the calibration of the A3308.
The information in the central area of the user interface is dependent on which tab has been selected
above and what operations have been specified by you. At startup, you must first define a
transmission signal. After traffic has been configured, relevant testing icons are available in the main
13
Instrument Overview
window of the display screen. Test configuration screens and results are displayed here when
appropriate.
2. Signal Configuration. This is the main screen through which you select the various tests to be
performed. The available tests and the accompanying icons, depend on the type of traffic selected.
3. Protocol Status Bar. This bar changes based on the type of traffic (protocol) being generated. In
this example the traffic being generated is 10GE LAN. The status indicators operate the same
regardless of the type of traffic being generated. The left half of the virtual LEDs indicates the current
status of the signal being received. If it is green then that particular error condition is not being
detected. If it is red then that error condition exists. The right half of the virtual LEDs is the history
status. If it is green the error condition has not existed since the last time the test was reset. If it is
yellow then the condition was seen at least once since the beginning of the test. There is also an
elapsed time counter indicating the elapsed time since the reset button was pressed. The reset button
will clear the elapsed time counter and reset the LEDs to green.
4. BERT Bar. This bar appears above the TX/RX bar and provides dynamic updates of the current
Bit Error Rate. It also gives you instant access to many of the BER testing features. A more thorough
description is given in CHAPTER 3.
5. TX/RX Bar. The transmitted and received power and optical wavelength are displayed here and
can be adjusted by touching the appropriate icons. You can also access software controls for enabling
the laser. Clock lock indicators on both the TX and RX sides indicate if the clocks are locked on to the
signal and are green when a valid clock is detected. The indicators will turn red if the 10 Gb/s OST
System can not lock on either the TX or the RX clock.
6. Help. This manual and other help documents can be referenced via this tab.
7. Administration. This button will display configuration settings for the A3301 and external
devices. Software updates, setting the IP address, and adjusting the date, time, sound level, and
touchscreen settings are all done under the Administration section. Additionally, the connections to
external slave modules as well as keyboard and printer options are specified here. Finally, the
software initialized shutdown is performed from the Administration screen.
8. Connected Device Selection. This area shows the (user assigned or default) name of the slave
unit that is currently controlled by the A3301. Touching the area will allow you to select any of the
slave devices that are connected to the A3301. After a module is selected, all following touch screen
commands will be sent to that device.
9. TX Single Mode. This shows the OST is configured to output a single mode optical signal.
Touching the button brings up the option to select other configurations including 850 nm multi-mode,
digital electrical, and variable electrical. The OST’s GUI is context sensitive; allowable options and
operations change depending on the mode selected. Modes other than TX Single Mode require the
use of the A3318 850 nm/Electrical OST Interface.
10. RX Single Mode. This shows the OST is configured to receive a single mode optical signal.
Touching the button brings up the option to select other configurations including 850 nm multi-mode
and digital electrical. The OST’s GUI is context sensitive; allowable options and operations change
depending on the mode selected. Modes other than RX Single Mode require the use of the A3318 850
nm/Electrical OST Interface.
14
A3318 850 nm/Electrical OST Interface Front Panel
11. Status. Touching the Status button will call up a display of system messages. These systems
messages can be informative, indicate a warning, or elaborate on an error condition during the
execution of a test.
2.4 A3318 850 nm/Electrical OST Interface Front Panel

1 2 5 6 7 8 9
3 4 10 11
FIGURE 2-4: Front Panel of the A3318
1. Digital In From DUT. These connectors are used to input electrical signals from DUTs to the
A3318. They may both be used for differential operation or just one connector may be used for
single-ended operation. In single-ended mode, the unused connector must be terminated. The LED is
illuminated when the 10 Gb/s Optical Standards Test System is configured to accept electrical signals
from the DUT.
2. Digital Out to DUT. These connectors are used to output electrical signals from the A3318 to a
DUT. They may both be used for differential operation or just one connector may be used for single-
ended operation. In single-ended mode, the unused connector must be terminated. The LED is
illuminated when the 10 Gb/s Optical Standards Test System is configured to output electrical signals
to the DUT.
3. REF CLK In. The reference clock in connector accepts a 1/64 of the data rate external reference
clock signal. The A3308’s TRIG OUT connects via an SMA cable to this connector. You may input
your own reference clock signal.
4. TRIG Out. The trigger out connector is a buffered version of the REF CLK IN signal and may be
used to trigger an oscilloscope.
5. 10G Electrical Out to DUT. An analog electrical signal may be outputted to the DUT via this
connector. This signal may contain a variety of degradations chosen by you in the OST’s signal
configuration setup menu.
6. RX SM From OST. This interchangeable optical connector supports ST, SC, DIN, DIA and FC
connector styles and accepts single mode signals from the A3308.
15
Instrument Overview
7. TX SM to OST. This interchangeable optical connector support ST, SC, DIN, DIA and FC
connector styles and transmits single mode signals to the A3308.
8. RX MM From DUT. This interchangeable optical connector support ST, SC, DIN, DIA and FC
connector styles and accepts multi-mode signals from the Device Under Test. The fiber behind the
bulkhead adapter is 62.5/125 µ m.
9. TX MM to DUT. This interchangeable optical connector support ST, SC, DIN, DIA and FC
connector styles and transmits multi-mode signals from the Device Under Test. The fiber behind the
bulkhead adapter is 50/125 µ m.
10. Status LEDs. The “north” red LED is on to indicate that the status of the A3318’s operating
system is OK. Note that it is a red LED and it will never turn green – in this case the red indicates a
normal and acceptable operating condition. The “east” LED is illuminated only when communication
is taking place between the A3318 and the A3308. The “south” LED indicates the operating system is
loading. The “west” LED is illuminated when power is on.
11. Laser Control Key. When the key is turned to enable, the A3318 allows its single mode and
multi-mode lasers to function. If the key is turned to disable, the lasers inside the A3318 are not
allowed to function. The A3318’s Laser Control Key does not control the lasers used in the A3308.
16
A3318 850 nm/Electrical OST Interface Rear Panel
2.5 A3318 850 nm/Electrical OST Interface Rear Panel
1 2 3
4 5
FIGURE 2-5: Rear Panel of the A3318
1. Fans. Cooling fans are not filtered and do not need periodic cleaning.
2. Power On/Off Rocker Switch. Each rocker switch turns on or off its associated redundant power
supply.
3. AC Power Inputs. Connect AC power to the A3318 via these redundant power supplies. Either
power input may be used by itself, or if both are used, they function as redundant power supplies. AC
input range is 100 – 240 V, 60 – 50 Hz. Each power supply is a module and may be exchanged on
failure.
4. OST In. The Ethernet cable from the A3308 connects to this RJ45 input.
5. Additional Connectors. These connectors are for Circadiant factory use only. No user
connections are allowed. Damage to the A3318 is possible if connections are made to these inputs;
damage is not covered under the warranty.
2.6 Layer 1 Tests

Essential physical layer (Layer 1) tests can be accomplished with this module. What used to be a
time-consuming and lengthy process has now been automated and results are plotted in patent-
pending formats. A brief description of each test is given below. While bitstream traffic is typically
used for these tests, they may also be performed with other types of traffic. You can for example
perform a receiver sensitivity test with 10GE WAN traffic using FCS byte as the error source. This
ability is especially useful when trying to run a Sensitivity or Stressed Receiver Conformance Test on
a device or line card that requires framing, such as a XENPAK module.
2.6.1 RX Tests
Sensitivity quantifies the performance of the optical signal receiver by measuring the Bit Error Rate
(BER) of the received signal as a function of the input optical power level. The 10 Gb/s OST System
17
Instrument Overview
automatically calculates and plots sensitivity. Plots are made on the correct Straight-Line BER™
scale to immediately highlight poor sensitivity performance. The test can be performed and plotted
based on BER vs. Average Optical Power or BER vs. OMA. See the Application Brief “Optical
Sensitivity Testing” on page 296.
CAUTION: When using the AutoBER selection in the sensitivity measurement, the 10 Gb/s OST
System will perform a “fast sensitivity measurement” which is a rough measurement of
the sensitivity of the device under test. During the “fast sensitivity” measurement the
10 Gb/s OST System output power will go as high as the maximum output setting. In
order to prevent damaging the device under test, verify that the maximum output power
setting is at a safe level by clicking on the OUT actual power button on the 10 Gb/s
OST System in the power bar.
Overload is a measurement of the maximum optical power a receiver can handle before the BER
reaches a predetermined unacceptable limit. The 10 Gb/s OST System automatically increases optical
power while monitoring BER up to a user-defined limit in order to measure optical overload. If the
overload value is greater than the maximum safe output of the 10 Gb/s OST System as defined by
you, then the overload is reported as “greater than” that value. See the Application Brief “Optical
Overload Testing” on page 304.
BER vs. OSNR (Optical Signal to Noise Ratio) sensitivity quantifies the performance of the optical
signal recovery in the presence of optical noise. The 10 Gb/s OST System monitors BER while the
built-in Erbium Doped Fiber Amplifier (EDFA) steadily increases the noise floor level to determine
the maximum OSNR tolerable for signal recovery with a BER less than some user defined limit.
The 10 Gb/s OST System can perform a BER vs. OSNR test on devices that are at data rates other
than 9.95 Gb/s, 10.3 Gb/s or 10.7 Gb/s by connecting a golden device to the reference transmitter
and/or reference receiver ports on the 10 Gb/s OST System. Using these ports the 10 Gb/s OST
System can also run a BER vs. OSNR test on proprietary signals such as FEC coding. See Section 5.3
for more details. See the Application Brief “BER vs. OSNR Testing” on page 298.
IsoBER displays combinations of optical power and OSNR that produce the same defined BER. The
OST automatically measures BER vs. OSNR at fixed optical power levels and then plots the user-
defined BER value associated with that combination of OSNR and optical power. You may define a
mask and if any of the plotted points fall in the masked area, the DUT is classified as FAIL. If none of
the points touch the mask, the DUT is classified as a PASS. This test is helpful in determining the
operating range of long-haul telecommunication systems; from high optical power with poor OSNR,
to low optical power with excellent OSNR and points in between.
2.6.2 TX Tests
Internal Sensitivity is essentially the same as the first part of a Path Penalty test whereby receiver
sensitivity is measured with only a short length of fiber between the TX DUT and the OST. The
Internal Sensitivity test allows you to use the OST’s internal receiver as a reference receiver when
measuring the performance of a TX DUT. This provides a way to measure the performance
differences among a set of transmitters and between transmitter types.
Path Penalty is a standard measurement of the quality of an optical transmitter. It quantifies the
degradation in transmission performance between the ideal system with no impairments and a real-
world system with typical impairments introduced by long-distance fiber transmission (e.g. chromatic
dispersion). The OST automatically measures optical path penalty in dB. An external spool of fiber is
18
SONET/SDH Features
attached to the test instrument through universal optical connectors located on the front panel of the
10 Gb/s OST System. See the Application Brief “Path Penalty Testing” on page 300.
DUT TX Power is the measurement of the average optical power in dBm or mW from the device
under test. The OST measures the output power of the device under test and verifies it is within the
range you specified. See the Application Brief “Transmitter Optical Output Power Testing” on
page 302.
2.7 SONET/SDH Features

In addition to the physical layer tests described above, the 10 Gb/s OST System is capable of
performing SONET/SDH (Layer 2) tests: it can generate SONET/SDH frames, adjust the overhead,
and generate and detect alarms and errors. When you elect to generate SONET/SDH traffic, the
payload can be filled with either a PRBS 215, PRBS 223, and PRBS 231 test pattern.
Transmit Features include:

• TX Error Generation
• Alarm generation and detection
• Overhead Generation
Receive Features include:

• RX Error Monitoring
• Anomaly Measurement
2.8 10 GE LAN/WAN Features

When choosing 10GE LAN traffic generation you have control of the traffic flow settings such as
TX/RX Pause Control, Interpacket Gap and Link Failure Detection. You have control of the entire
802.3 header with the exception of the preamble, which is fixed. Source and Destination address are
either fixed or incremented from a starting address to a specified ending address.
The IP header setup is similar to 802.3 where you have control over most of the IP header and
payload. Two patterns (all 0s, and 1010...) are available for the payload. The payload length can be set
by you and includes the ability to generate runt packets.
The A3308 also supports the generation of MPLS labels. You have full control over the entire MPLS
label.
2.9 PoS Features

When choosing PoS data traffic generation, you may specify a standard HDLC, or a CISCO HDLC
session. In standard PPP mode the 10 Gb/s OST System will automatically negotiate and establish the
session giving error codes in english if the session fails. You may specify the restart timer, max
19
Instrument Overview
terminate, max configure, max failure, maximum receive unit, and magic number parameters for the
session.
2.10 OTN Features

When you choose to generate OTN traffic, you may specify the type of traffic encapsulated in the
OTN frame: Bitstream, SONET with Bitstream in SONET Payload, SONET with POS in SONET
Payload, SONET with 10GE WAN in SONET Payload, SDH with Bitstream in SDH Payload, SDH
with POS in SDH Payload, and SDH with 10GE WAN in SDH Payload. You may also separately
enable or disable scrambling and FEC.
2.11 Testing 1310 nm Devices

The receiver of the A3308 10 Gb/s Optical Standards Tester is a wide band receiver and has a range of
1290 nm to 1565 nm. The A3308 has been calibrated over that entire range so that accurate
measurements are obtained. To ensure proper measurements you must set the wavelength of the
signal being received by the OST. To do this click on the wavelength button on the IN side of the
OUT / IN bar (Figure 2-6) and enter in the desired wavelength.
A calibration factor can be added to the transmitter to compensate for the difference in power between
a 1550 nm device and a 1310 nm device. To do this set the A3308 transmitter power to a level that is
within the range of the DUT (-5 dBm for example). Disconnect the fiber going into the DUT and
connect it to a power meter. Set the power meter for 1310 nm and note the power measurement. The
difference between the A3308 transmitter power out and the measured power on the power meter is
the CalFactor that needs to be entered into the A3308.
To enter the CalFactor, click on the calibration button on the OUT / IN bar (Figure 2-6) on the bottom
of the screen. Click on the CalFactor box and enter the CalFactor you just calculated, then click OK.
The Corrected Power box on the OUT side of the of the OUT /IN bar should now show the same
power as what you just measured on the power meter.
Traffic Type Wavelength
FIGURE 2-6: TX/RX Bar
For more information on calibration, see Section 3.6.3 or the Wavelength Calibration Procedure in
CHAPTER 15.
20
CHAPTER 3 Signal Configuration
In this chapter, the general operation of the A3308 10 Gb/s Optical Standards Tester is explained. For
the sake of clarity it will be assumed that the touch screen interface on the command unit is being
used (a mouse can be connected to the A3308 and used as the input device if desired). The A3308 can
also be controlled via the GPIB interface or an ethernet 10/100 BaseT connection from an external
computer using the standard SCPI command set. For more information about the remote operation of
the A3308, see CHAPTER 11.
It is also assumed that you have familiarized yourself with the connectors on the instrument and have
completed the initial setup and installation. See CHAPTER 1 and CHAPTER 2 for more information
on these areas.
The first time the A3308 is connected to the A3301 OST System Controller, the system must be
configured and external devices must be set and identified. These operations and other general
operations pertaining to the A3301 are performed by touching the Administration button at the
bottom of the GUI.
3.1 Traffic Configuration

To establish the format and protocol of the OST’s output signal you must configure the
transmission traffic. Six types of data can be generated by the A3308 for testing
purposes: Bitstream, SONET/SDH, 10GE LAN, 10GE WAN, OTN and PoS. Bitstream data refers to
PRBS patterns without any framing (unframed): the type of signal traditionally generated by standard
Bit Error Rate testers. SONET/SDH data includes a SONET/SDH frame overhead. PRBS patterns are
available for the payload of the SONET/SDH traffic. In addition specific types of packet data can be
sent within a SONET/SDH frame; the payload can be filled with PPP traffic or 10GE WAN (IEEE
802.3ae) traffic which can carry MPLS/IP data. The A3308 can also generate 10GE LAN traffic.
Once the A3308 has been powered up, the GUI interface can be used to configure traffic and begin
testing. However, all hardware safety interlocks must be satisfied. See Section 3.6.1 Removing the
Hardware Safety Interlocks for more information about the safety interlocks.
At the initial startup, you are immediately directed to the traffic configuration screen. At other times,
selecting the Traffic Configuration icon in the Signal Configuration column of the main window or
21
Signal Configuration
pressing the Traffic button on the TX/RX bar brings up the interface for configuring all types of
traffic. In the traffic configuration window, you may select traffic types by touching the appropriate
signal type in the left-most column. The middle column will display all layers of the signal that may
be defined. The specific descriptions for configuring each type of traffic are given below.
Once a traffic type has been selected and configured, a tab in the upper left corner of the GUI screen
will display which type of traffic is being generated (e.g., SONET: Bitstream - 9.95 Gb/s or 10GE
LAN 10.3 Gb/s). Test icons relevant to the type of traffic will also become available in the main
window such as the specific statistics and error injection.
There are several icons along the bottom of the window that are common to all types of traffic
generation. From the left, they are Start, Load, Save, Save PNG, Save to USB, Print, and Exit. Start
will begin traffic generation according to the parameters entered and exit the traffic configuration
window. Load and Save are used to either retrieve and save different traffic configurations. Saved
configurations can be activated for comparison purposes on a specific test or for automatically
running a series of tests. If you wish to have a copy of the traffic configuration settings, touching
Save PNG will create a PNG file that you can retrieve via a web browser. Save to USB option allows
you to save a file to a USB device. Print will print a snapshot of the screen to a printer, Exit will
cancel any changes entered by you and exit the traffic configuration screen.
Being able to save different test configurations is especially useful for testing different types of
devices or for running multiple passes of the same test while varying one parameter of the test
configuration.
3.1.1 Bitstream
FIGURE 3-1: Bitstream Data Traffic Configuration
22
Traffic Configuration
Bitstream (unframed) data is often used for physical layer tests. After selecting Traffic Configuration,
you should select Bitstream at the top of the left-most column. The main window will display Figure
3-1. The standard predefined PRBS pattern available are 27-1, 215-1, 223-1, and 231-1 and alternating
1’s and 0’s..
The Disable Autosynchronize option is selected mainly for transmit only mode. Selecting this option
will cause the receiver to not synchronize on the user pattern.
3.1.2 10GE LAN
FIGURE 3-2: 10GE LAN Protocol Error Bar
See Table 3-2 for a list of alarms that are included in the 10GE LAN Protocol Error Bar.
TABLE 3-1: Alarms on 10GE LAN
10GE Acronyms Error

Frame Sync Frame Synchronization
Link Link Errors
Pause Pause State
FCS Error Frame Check Sequence Error
PCS Error Packet Check Sequence Error
LCD No frame lock
Loc. Fault Local fault
Rem. Fault Remote Fault
Frag Fragmented frames
Under Under Sized Frames
Over Over Sized Frames
Jabber Number greater then max frame size
IPG Inter Packet Gap
When generating IEEE 802.3ae LAN traffic, you may specify the IEEE 802.3ae setup which includes
TX/RX Pause Control, Interpacket Gap and Link Failure Detection. Then the IEEE 802.3ae Header
and Payload needs to be defined. This is followed by the IP Header and Payload definitions and
optional MPLS labels. See CHAPTER 8 for more details about 10GE LAN traffic generation, error
injection and statistics.
3.1.3 SONET/SDH
This section refers to SONET/SDH-framed traffic containing Bitstream, PoS or 10GE WAN data in
the payload. To simplify explanations, the SONET settings are described. If you wish for an SDH
frame, the corresponding selections under SDH should be made in the left-most column of the traffic
configuration screen. All other selections are then similar to those described below.
23
FIGURE 3-3: Overhead Setup
3.1.3.1 Bitstream
If you wish to generate PRBS traffic within a SONET frame, Bitstream should be selected under
SONET in the left-most column. The available test patterns are 215-1, 223-1, and 231-1. You may
choose to save a set of definitions for the frame and payload that can then be recalled at any time
(using the Save and Load icons).
You may choose to invert the signal being transmitted or received. This selection indicates whether
high/low is interpreted as 1/0 or 0/1. Normal payload scrambling is available or the scrambling may
be turned off using the Payload Scrambling check box. And finally, a Bit Error Rate for errors
injected into the TX signal may be specified at Inject Errors.
NOTE: Options which are greyed out are not available for bitstream traffic within a
SONET/SDH frame but may be available for simple bitstream signal.
Once SONET/SDH traffic has been configured and you have returned back to the main screen by
pressing Start, the SONET/SDH error bar will appear above the BERT bar (see Figure 3-4). This bar
has error indicators that show the current status and history since reset of a variety of SONET/SDH
alarm conditions. When an error occurs, the left half of the indicator will turn red while the error
24
condition exists and then the right half will turn amber to indicate an error has occurred since the last
reset. See Table 3-2 for a list of errors that are included in the SONET/SDH error bar.
TABLE 3-2: SONET/SDH Errors
SONET Acronym Error

LOF Loss Of Frame
OOF Out Of Frame
AIS–L Alarm Indication Signal - Line
RDI–L Remote Defect Indication - Line
REI–L Remote Error Indication - Line
AIS–P Alarm Indication Signal - Path
RDI–P Remote Defect Indication - Path
REI–P Remote Error Indication - Path
B1, B2, B3 Section, Line, & Path BIP errors
The Reset button will restart the timer and erase the error history. The elapsed time since reset appears
in the window on the right of the bar.
FIGURE 3-4: SONET/SDH Error Bar
When Bitstream, PoS, 10 GE WAN traffic has been configured and you have returned back to the
main screen by pressing Start, the protocol error bar (see Figure 3-5) will appear above the BERT bar
depending on the type of traffic being generated. On the left end of the Protocol bar it will indicate the
type of traffic being generated, in this example PoS traffic is being generated. This will change when
the traffic being generated is changed.
The protocol bar has error indicators that show the current status and history since reset of a variety of
protocol alarm conditions. When an error occurs, the left half of the indicator will turn red while the
error condition exists and then the right half will turn amber to indicate an error has occurred since the
last reset. See Table 3-3 for a list of errors that are included in the PoS protocol error bar.
FIGURE 3-5: PoS Protocol Error Bar
25
TABLE 3-3: PoS Errors
PoS Acronym Error Condition

PPP Link Up PPP Link Up/Failure
LOF Loss Of Frame
OOF Out Of Frame
TX Data Transmit Data
RX Data Receive Data
FCS Error Frame Check Sequence Error
Oversize Oversize Packet Error
Undersize Undersize Packet Error
Aborts Aborted Frames
IP Checksum IP Checksum Error
3.1.3.2 PoS
In addition to supporting Bitstream (unframed PRBS) traffic in the SONET payload the A3308 also
supports Packet over SONET (PoS). Selecting PoS under the SONET heading in the left column will
change the selections available in the protocol setup (center) column. When PPP Setup is selected,
you can enter the PPP session negotiation parameters, see Figure 3-6.
You may specify a standard HDLC or a CISCO HDLC session. If Enable PPP Link Negotiation is
selected, the A3308 will automatically negotiate the magic number and establish the PPP session.
You may specify the maximum configure requests, the maximum terminate requests, the retry
timeout, magic number parameters for the session, maximum receive unit, or negotiate IP address.
For more detailed information about PoS Traffic Generation and Statistics, see CHAPTER 8.
26
FIGURE 3-6: SONET PoS PPP Setup
3.1.4 10GE WAN
FIGURE 3-7: 10GE WAN Protocol Bar
When generating IEEE 802.3ae WAN traffic, you may specify the IEEE 802.3ae setup which
includes TX/RX Pause Control, Interpacket Gap and Link Failure Detection. Then the IEEE 802.3ae
Header and Payload needs to be defined. This is followed by the IP Header and Payload definitions
and optional MPLS labels. See CHAPTER 10 for more details about 10GE WAN traffic generation,
error insertion and statistics.
3.1.5 OTN
To configure the OST for OTN traffic, choose the Traffic Configuration icon under the Signal
Configuration column of the main screen and then OTN from the list of traffic types.
Selecting tabs under the OTN Setup provides access to individual setup screens for each type of
protocol. See that protocol or Bitstream section of the manual for detailed setup information for each
tab.
27
For OTN Bitstream traffic the payload type is set to FE and for OTN SONET and OTN SDH the
payload type is set to 3. You may also choose to separately enable or disable scrambling and FEC.
You may select two Tandem Connection Monitoring (TCM) fields to monitor.
FIGURE 3-8: OTN Setup Screen
FIGURE 3-9: OTN/ODU Error Bar
TABLE 3-4: OTN/ODU Errors
OTN/ODU
Acronym Error
AIS Alarm Injection Signal
OCI Open Connection Indication
LCK Lock
PM-BIP Path Monitor - Bit Interlocked Parity
PM-BEI Path Monitor - Backward error Indicator
PM-BDI Path Monitor - Backward Defect Indicator
NEW-FTFL New - Fault Typecasting
NEW-TTI New - Trail Trace Identifier
28
FIGURE 3-10: OTN/OTU Error Bar
TABLE 3-5: OTN/OTU Errors
OTN /OTU
Acronym Error
LOF Loss of Signal
OOF Out of Frame
LOM Loss of Multi-frame
OOM Out of Multi-frame
AIS Alarm Indication signal
IAE Incoming Alignment Error
SM BIP Section Monitor - Bit Interleaved Parity
SM BEI Section Monitor - Backward error Indicator
SM BDI Section Monitor - Backward Defect Indicator
Corrected 0’s Corrected zeros
Corrected 1’s Corrected ones
Corrected Bits Corrected bits
Uncorrected Uncorrected
29
3.2 Mode Selection
FIGURE 3-11: Single Mode, Multi-Mode, Digital Electrical and Variable Electrical Mode
Selection
In the “Mode Selection” tab you may select how the A3308 10 Gb/s Optical Standards Tester is
configured. Only the TX Single Mode and RX Single Mode are selectable unless you also have an
attached A3318 850 nm/Electrical OST Interface.
To reach the Mode Selection tab directly, press either the TX or the RX mode button located at the
bottom of the GUI. You may also touch one of the icons under the Signal Configuration column. (See
Figure 2-3) and then press the Mode Selection tab.
The A3318 850 nm/Electrical OST Interface operates in conjunction with the A3308 10 Gb/s Optical
Standards Tester and allows you to select between a multi-mode fiber output, a digital electrical
output and a variable electrical output. You may configure the A3318 850 nm/Electrical OST
Interface to accept a signal via its multi-mode receiver or its digital electrical input.
The A3318 850 nm/Electrical OST Interface converts single mode signals from the A3308 into a
multi-mode, digital electrical or variable electrical signals. When 850 nm multi-mode signals or
digital electrical signals enter the A3318 850 nm/Electrical OST Interface, they are converted to
single mode and sent to the A3308.
The GUI is context sensitive, and mode selections made here effect changes throughout the GUI.
30
Mode Selection
In TX Mode “850 nm Multi-Mode”, optical power settings in the Sensitivity test and the TX/RX bar
apply to the multi-mode laser in the A3318 850 nm/Electrical OST Interface.
In TX Mode “Digital Electrical”, the A3318 850 nm/Electrical OST Interface outputs either a
differential electrical signal based on the signal received from the A3308. Custom degradations are
not available in the “Digital Electrical” mode. One of the digital “TO DUT” ports may be terminated
for single-ended operation.
In TX Mode “Variable Electrical”, the A3318 850 nm/Electrical OST Interface transmits an analog
electrical signal that corresponds to the signal received from the A3308. In the Signal Configuration
“Degradation” tab you can choose either to have no degradation or define a custom setup. You may
also control the peak-to-peak voltage by touching the Vpp button on the TX/RX bar. This brings up
an input number pad as shown in Figure 3-12.
FIGURE 3-12: Enter Volts Peak-To-Peak
In TX Mode “Single Mode”, the A3318 850 nm/Electrical OST Interface is not utilized. The DUT
receives a signal directly from the A3308 10 Gb/s Optical Standards Tester.
In RX Mode “850 nm Multi-Mode”, the A3318’s 850 nm receiver is active. On the GUI’s TX/RX bar,
the average power, calibration factor, and wavelength refer to the signal received by the A3318 850
nm/Electrical OST Interface.
In RX Mode “Digital Electrical”, the A3318’s differential electrical input is active. One of the digital
“FROM DUT” ports may be terminated for single-ended operation. On the GUI’s TX/RX bar, the
signal detect status is displayed.
31
3.3 Stressed Eye and Other Degradations (Optics)
FIGURE 3-13: 10G Base-L Optical Degradation
Selecting the Optics tab while in the Traffic Configuration screen or selecting the Stressed Eye and
Other Degradation icon from the main screen will display Figure 3-13. Here you may choose various
options and define how the optical signal transmitted by the A3308 is degraded. Degradations include
the IEEE 802.3ae stressed receiver conformance test parameters for (9.95/10.3/10.5) G Base-L and
(9.95/10.3/10.5) G Base-E. In addition you can create custom degraded signals by choosing to add
horizontal or vertical jitter, degrading OSNR, lowering extinction ratio and or enabling the 4th order
Bessel-Thompson Stressed Eye Filter.
Combined Results. As various optical degradations are added to the signal, the overall extinction
ratio changes and available optical ranges are limited. The A3308 displays these values in the
Combined Results table under the following entries.
• Effective Extinction Ratio
• OMA (dB)
• P avg (dBm)
No Optical Degradation. If this option is selected the A3308 will output a clean signal. Once traffic
is started, the TX/RX bar will display “None Optical Degrade”.
(9.95/10.3/10.5) G Base-L (2.2 dB VECP, 3.5 dB ER). If this option is selected, the A3308 will
output an IEEE 802.3ae (9.95/10.3/10.5) G Base-L quality signal. You may test at multiple jitter
frequencies by selecting the Swept Jitter option or may test at a single frequency by selecting single
32
Stressed Eye and Other Degradations (Optics)
point jitter. No additional calibration is required to have an IEEE 802.3ae 10G Base-L signal. The 2.2
dB VECP refers to the specified Vertical Eye Closure Penalty. The 3.5 dB ER refers to the specified
extinction ratio.The 4th order Bessell-Thompson filter is included in the A3308’s internal signal path.
(9.95/10.3/10.5) G Base-E (2.7 dB VECP, 3.0 dB ER). If this option is selected, the A3308 will
output an IEEE 802.3ae (9.95/10.3/10.5) G Base-E quality signal. You may test at multiple jitter
frequencies by selecting the Swept Jitter option or may test at a single frequency by selecting single
point jitter. No additional calibration is required to have an IEEE 802.3ae 10G Base-L signal. The 2.7
dB VECP refers to the specified Vertical Eye Closure Penalty. The 3.0 dB ER refers to the specified
extinction ratio.The 4th order Bessel-Thompson filter is included in the A3308’s internal signal path.
FIGURE 3-14: 10G Base-E Optical Degradation
Single Point Jitter. The signal quality chosen determines the fixed jitter frequencies and amplitude
that can be applied to the signal. These fixed frequencies and amplitudes correspond to the jitter
template defined in the IEEE 802.3ae standards and are displayed via the pull down menu. The DUT
must work over the full range of applied jitter specified in the standards: 0.04 MHz to 10 times the
loop bandwidth of the receiver.
33
TABLE 3-6: 10G Base-L Single Point Jitter
Frequency
MHz Amplitude (peak-to-peak)
40.0 0.12
20.0 0.12
10.0 0.12
4.0 0.12
2.0 0.1
1.0 0.2
0.4 0.5
0.2 1.0
0.1 2.0
0.04 5.0
TABLE 3-7: 10G Base-E Swept Jitter
Frequency
MHz Amplitude (peak-to-peak) Dwell Time (ms)
40.0 0.12 100
20.0 0.12 100
10.0 0.12 100
4.0 0.12 100
2.0 0.1 100
1.0 0.2 100
0.4 0.5 100
0.2 1.0 100
0.1 2.0 100
0.04 5.0 100
Swept Jitter. If this option is selected, the A3308 outputs the 10G Base-L or 10G Base-E quality
signal you selected with the added jitter at the frequencies and amplitudes shown in the Table 3-7.
Custom Setup. This option enables partial degradation of the A3308’s output signal by supporting
OSNR Degrade, adding phase jitter single point or swept, adding amplitude interference, changing
the extinction ratio and enabling the stressed eye filter. Once the signal is configured and traffic
started the TX/RX bar will display “Custom Optical Degrade”.
• Copy from Standard. Various standard degradation options are displayed when this option is
selected. On selecting an option, the custom menu will be populated with the values necessary to
achieve the selected standard degradation.
• Degrade OSNR. Long reach optical communication systems typically must contend with optical
noise in the form of Amplified Spontaneous Emission (ASE) noise due to the presence of optical
amplifiers in the transmission link. This noise at a wavelength close to the transmission
34
Stressed Eye and Other Degradations (Optics)
wavelength will produce “beat noise” in the receiver. Here, you may opt to test their device in the
presence of a specified OSNR level. The selectable range is 5 to 55 dB.
• Horizontal (Phase Jitter). The A3308 has the ability to add Phase Jitter to the optical test signal.
You can specify a fixed amplitude (UI p-p) at a specified frequency within the jitter mask in
Figure 3-15. During the Stressed Receiver Conformance Test the A3308 will sweep through a
range of varying amplitudes and frequencies as described in IEEE 802.3ae standard.
• Vertical (Amplitude Interference). The A3308 provides you with the ability to turn on and off a
secondary laser which can be used to determine the effect of additional signals going through the
same fiber. The interfering laser wavelength is approximately 30 nm away from the primary laser.
You select the power ratio and modulation frequency of the interfering laser used in the S/X
measurement.
• Extinction Ratio Configuration. This option allows you to specify an extinction ratio level for
the DUT. The extinction ratio is defined as:
P1
10 ⋅ log ⎛ ------⎞
⎝ P 0⎠
where P 1 is the power, measured in dBm, of a “one” and P 0 is the power, measured in dBm, of a
“zero”. For long range SONET/SDH applications, you may wish to set the extinction ratio to 8.2
dB. For 10GE stressed receiver conformance testing you may wish to set the extinction ration to 3
dB. The extinction ratio selected may not be accurately produced, multiple degradations are
simultaneously enabled.
• Enable Stressed Eye Filter. The A3308 includes a 4th order Bessel-Thompson filter as specified
in the 802.3ae standard. You can choose to have this filter enabled or disabled.
FIGURE 3-15: Jitter Mask
35
3.4 Switch Setup
FIGURE 3-16: Switch Setup
NOTE: Changes are only made when the “Start” or “Apply Now” buttons are selected.
External TX In (From Ref TX). Touching the Reference TX Switch/External TX block toggles the
display between showing the Internal TX and the External TX block with In and Out ports. When the
External TX block is shown, the signal from the external TX is fed into the OST via the In From Ref
TX connector on the front panel of the A3308. When the External TX block is not shown, the In port
is inactive.
The In from Ref TX port is typically used to connect to a “Golden TX” or to a DUT for a Path Penalty
test. Once the External TX signal is sent into the OST, it may be degraded in the OST’s “optical
cloud”. In the “optical cloud” the signal’s optical power may be attenuated, extinction ratio lowered,
OSNR shrunk, and an interfering signal laser may be coupled with the main External TX’s signal to
add vertical jitter. It is not possible to add horizontal jitter to the External TX signal.
To obtain the desired OSNR level or specified extinction ratio value for a signal leaving the Out
Transmit to DUT connector optical port, the OST adds degradation to the External signal. Therefore,
it is necessary to first calibrate the TX signal so the OST will add the correct amount of degradation.
This is accomplished by touching the External TX Touch to Recalibrate block which initiates a
calibration with a user supplied Optical Spectrum Analyzer.
36
Switch Setup
FIGURE 3-17: OSA Not Configured
Before an external transmitter can be calibrated, it must first be recognized by the OST through the
Admin tab.
37
FIGURE 3-18: Calibration for External Transmitter
You can load a previously saved calibration or the factory calibration. However, it is unlikely that the
factory calibration will be correct for an external TX since the wavelength and spectral shape of the
external TX will probably be different than the factory calibration. You may also proceed without
modifying the calibration.
38
Switch Setup
FIGURE 3-19: Calibration Instructions
Step 1: CAUTION: DISCONNECT DUT FROM OST BEFORE CALIBRATING. The OST will put
out high-powered signals > +10 dBm that may damage your receiver during calibration. You must
disconnect your DUT from the OST’s “TO DUT” port before pressing OK.
Step 2: If your OST is configured with an OSNR port, connect the OSA to the OSNR port. If your
OST is not configured with an OSNR port, connect the OST to the “TO DUT” port.
Step 3: Connect a GPIB cable between the OST’s “GPIB MASTER” port and the OSA’s GPIB
SLAVE port.
Step 4: Press OK to begin the automatic calibration sequence.
The OST is fairly agnostic with respect to the signal that can travel through the optical cloud. The
External TX’s signal must be single mode, in the 1310/1550 bands, and the passive throughput
architecture of the OST accommodates low-speed to very high-speed signals. This port could be used,
for example to input a 43 Gb/s signal for a BER vs. OSNR test. If 1310 signals are used as an input,
the EDFA Bypass Switch should be put into the Bypass state.
External TX Out (Out To Ref TX). When the External TX block is shown, the signal from the
OST’s internal TX leaves the OST via the Out to Ref TX connector on the front panel of the A3308.
When the External TX block is not shown, this Out port is inactive.
The Out To Ref Tx port is typically used to connect to an RX which is in loopback mode with the
External TX. This allows the OST to send out known patterns from the Internal TX at a relatively
high optical power levels to assure very low BER rates, and then to compare it when it comes back to
the Internal RX to arrive at a BER rate for the DUT.
External RX Out (Out To Ref RX). Touching the Reference RX Switch/External RX block toggles
the display between showing only the Internal RX or the External RX block with In and Out ports.
39
When the External RX block is shown, the signal entering the OST’s In Receive from DUT or In Path
In port is switched to the External RX. When the External TX block is not shown, the Out port is
inactive. Only when the Internal RX is shown, will the signal is switched directly to the Internal RX.
This Internal RX port is typically used to connect to a “Golden RX” or an RX designed to receive
FEC encoded signals that must be converted back to the signal type the OST originally outputted.
External RX In (In From Ref RX). This port receives a signal from a TX associated with the
External RX and feeds it to the OST’s Internal RX. The port is typically used to connect to the TX
which receives a loopback signal from the External RX. This TX’s optical power level should be set
to a relatively high power level to assure very low BER rates between the TX and Internal RX.
Transmit to DUT/A3318 (Out). Signal traffic leaves the OST from this port. The signal from this
port may be configured with or without degradation to the optical signal or may include degradation.
If you have activated the External TX, its output from the OST will be via this port. Between the
Internal TX and/or the External TX and this port, the OST may be configured to add degradations to
the optical signal. If you select to send the signal through the EDFA, the signal will also pass through
a narrow line width filter. If the EDFA is bypassed, the filter is also bypassed. The filter only works in
the 1550 nm band.
Monitor Port (Out). This port may be configured to monitor traffic leaving or entering the OST.
Pressing the Monitor Port Switch toggles the state of the switch. Arrows indicate the direction of the
light path. If a signal from an External TX 1310 nm source is used, you should bypass the EDFA by
placing the EDFA Bypass Switch in bypass mode. In this case, the monitor port will have a much
lower power signal. When this port is configured to monitor the signal entering the OST, all of the
signal entering the In From DUT Port is redirected to the Monitor Port Out. This configuration is also
automatically used during an Internal Sensitivity test. Typically, monitor ports are used to connect
oscilloscopes or OSA’s.
Receive from DUT/A3318 (In). Signal traffic enters the OST from this port. Typically, this port is
connected to the DUT’s TX or the TX that is receiving a loopback signal from a DUT’s RX. After the
signal enters the OST, it is directed to the Internal RX, or you may send it into a loop of fiber via the
Path Penalty Loop Switch, and/or to an external RX via the Reference RX Switch. The maximum
input power of the signal entering this port is +5 dBm. External attenuators should be utilized to avoid
damaging the Internal RX. The signal may be further attenuated by utilizing the OST’s RX Power
Governor. If the Path Penalty Loop switch is in bypass mode, this port is inactive. If the Path Penalty
Loop switch is in Auto mode, the port will be active only during the Path Penalty Test. If the Path
Penalty switch is in Through Fiber Loop mode, the port is active and signals entering this port go
through the switch towards the Internal RX.
Path Out (Out). Traffic leaves the OST via this port and typically connects to a spool of SM fiber for
use with a path penalty measurement. If the Path Penalty Loop switch is in bypass mode, this port is
inactive. If the Path Penalty Loop switch is in Auto mode, the port will be active only during the Path
Penalty Test. If the Path Penalty switch is in Through Fiber Loop mode, the port is active and signals
entering the Receive from DUT (In) port are directed via the Path Penalty Loop Switch to this port.
Path In (In). After traffic passes through the Path Penalty Loop it reenters the OST via this port. The
maximum input power of the signal entering this port is +5 dBm. External attenuators should be
utilized to avoid damaging the Internal RX. The signal may be further attenuated by utilizing the
OST’s RX Power Governor. Typically, a spool of SM fiber is attached to this port for use with a path
penalty measurement. If the Path Penalty Loop switch is in bypass mode, this port is inactive. If the
Path Penalty Loop switch is in Auto mode, the port will be active only during the Path Penalty Test. If
40
Switch Setup
the Path Penalty switch is in Through Fiber Loop mode, the port is active and any signals entering this
port go through the switch towards the Internal RX.
Reference TX Switch. This switch directs the optical signal from the OST’s TX to either of the two
output ports Transmit to DUT port and To Ref TX. This is a toggle switch. red lines with arrows
indicate the selected path. In the default state, the OST’s TX signal exits the OST via the OUT
Transmit to DUT (Out) port. This enables an RX associated with the External TX to be put in
loopback mode so the signal from the OST is translated and then sent out the External TX.
Translations may include wavelength, Forward Error Correction, protocol, transmission speed, or the
use of a “Golden TX”. The translated signal reenters the OST via the External TX port (In). The
translated signal may then be optically degraded. Degradations include optical power, vertical eye
closure, OSNR and extinction ratio.
Reference RX Switch. This switch directs the optical signal to either the OST’s Internal RX or to the
External RX port (Out). Pressing in the area of the Reference RX Switch block toggles the state of the
switch. Red lines with arrows indicate the selected path. In the default state, the signal from the In
Receive from DUT port and the In Path In port are sent to the Internal RX. If an External RX is used,
the signal exits the OST via the Out External RX port. This enables an RX associated with the
External TX to be put in loopback mode so the signal from the OST is translated and then sent back to
the OST via the In External RX port where it is then sent to the OST’s Internal RX. Translations may
include wavelength, Forward Error Correction, protocol, transmission speed, or the use of a “Golden
TX”.
EDFA Bypass Switch. This switch is either in AUTO, Bypass EDFA, or Through EDFA mode. In
AUTO mode, the OST’s software automatically controls the state of the switch. Red lines with arrows
indicate the selected path. The switch allows the optical signal to either pass through the EDFA (and a
narrow pass filter) or to bypass the EDFA (and a narrow pass filter). Typically, this switch is put into
bypass mode only when a 1310 nm TX is connected to the OST via the In External TX port. This is
because a 1310 nm source is greatly attenuated when it passes through an EDFA. The default state of
the switch is AUTO mode with the optical signal passing through the EDFA. If the switch is in EDFA
Bypass mode, the OST is unable to degrade the OSNR of the optical signal.
RX Power Governor. This icon shows the user-defined maximum power limit permitted to pass this
point of the optical path. The RX Power Governor is used to limit the input power to a receiver so it is
not damaged or to set the optical power level at the RX.
The RX Power Governor may be used to limit the power to the OST’s Internal RX or an External RX.
An attenuator and power meter are used in combination to reduce high optical power levels to the
selected level. Because it does take some time to react and then move the attenuator after a high
power signal is measured, the RX is susceptible to short bursts of high power. The RX Power
Governor is not to be relied on as a fool-proof method of protecting an RX. You must take care not to
send in too high an optical power signal.
The RX Power Governor will set the incoming optical power level to the desired level if the incoming
signal is higher than selected. If the incoming signal is lower than selected, the RX Power Governor
will monitor the optical signal and reduce its power level should it rise above the selected value.
Touching the RX Power Governor brings up an input number pad on the screen. This is where you
enter the maximum power value on the RX signal path.
Monitor Port Switch. This switch is either in AUTO, Monitor Input, or Monitor Output mode.
Touching the screen repeatedly cycles through the modes. Red lines with arrows indicate the selected
41
path. The switch sends either a portion of the incoming optical signal to the Out Monitor Port or a
portion of the outgoing signal to the Out Monitor Port.
In AUTO mode, the OST’s software controls the state of the switch. Default mode is AUTO.
When the Monitor Port Switch is in the Monitor Input mode, a portion of the incoming signal, after
the Path Penalty Switch, is split off and sent to the Out Monitor Port.
When the Monitor Port Switch is in the Monitor Output mode, a portion of the outgoing signal, after
the EDFA Bypass Switch, is split off and sent to the Out Monitor Port. The power level of this signal
is amplified through the EDFA, unless the EDFA is bypassed, and may be in the region of +5 dBm or
more of optical power. You may wish to use attenuators to prevent damage to a receiver.
PPL Switch. PPL is an acronym for Path Penalty Loop. This switch is either in AUTO, Bypass Fiber
Loop, or Through Fiber Loop mode. Touching the screen repeatedly cycles through the modes. Red
lines with arrows indicate the selected path.
After traffic enters the OST via the In Receive from DUT port, this switch controls whether or not it
passes through a user supplied loop of fiber before proceeding towards the Internal or External RX.
Typically, a spool of SM fiber is attached to this port for use with a path penalty measurement.
In the AUTO mode, the OST’s software automatically controls the state of the switch.
In the Bypass Fiber Loop mode, the optical signal does not go through the loop of fiber.
In the Through Fiber Loop mode, the optical signal exits out of the OST via the Out Path Out port and
reenters via the In Path In port. You supply the desired length of fiber and other components or
impairments along the optical path.
OSNR Out. This port is not displayed on the Switch Setup screen. It is a tap of the optical signal in
the A3308 just before the optical filter. This allows you to monitor the OSNR of an external
transmitter.
42
Clock Settings
3.5 Clock Settings
FIGURE 3-20: Clock Source and Clock Rate
In the “Clock Settings” tab you may select the clock source and the clock rate.
Clock Source: You may select either the OST’s internal clock source or provide their own external
clock source to establish TX and RX timing.
• Internal. If this radio button is selected, the OST automatically generates timing based on internal
crystals.
• External. If this radio button is selected, the OST will utilize timing coming from the TX REF IN
connector. You may provide a clock somewhat faster, slower, or with some jitter and wander
added. The maximum deviation from a perfect signal that may be applied will vary from unit to
unit and is not specified. A minimum deviation of +/- 20 ppm is supported. Hardware in the OST
will limit the effective range.
Clock Rate: You may select the rate of the clock to be used when traffic is configured to Bitstream
PRBS. This establishes the transmission rate of the OST. If you select protocol traffic, the rate is
automatically defined by the traffic type. Rates that are grayed out are not selectable.
• 9.95328. If this radio button is selected, the OST’s Internal TX will output a signal at 9.95328
Gb/s. If an external clock source is selected, you should supply a 155.52 MHz input signal to the
TX REF IN connector.
• 10.3125. If this radio button is selected, the OST’s Internal TX will output a signal at 10.3125
Gb/s. If an external clock source is selected, you should supply a 161.1328 MHz input signal to
the TX REF IN connector.
43
• 10.70922532. If this radio button is selected, the OST’s Internal TX will output a signal at
10.70922532 Gb/s. If an external clock source is selected, you should supply a 167.3316 MHz
input signal to the TX REF IN connector.
3.6 Operating the Transmit Section of the A3308

WARNING: Complies with 21 CFR 1040.10 and 1040.11 except for deviations pursuant to Laser
Notice No. 50, dated January 2001. It is designated Class 1M according to IEC
60825-1 Edition 1.2: 2001-08.
The A3308 comes with a Class 1M laser for traffic generation installed internally. The transmitted
power can be adjusted from +11 dBm to -35 dBm.
3.6.1 Removing the Hardware Safety Interlocks

In order to generate traffic and begin using the product the laser must be enabled. After turning on the
A3308, it is necessary to remove the safety interlocks. A remote interlock connector on the rear panel
provides a safety mechanism for your external safety interlock system. This connector must be
shorted in order for the laser to operate. If there is no external safety interlock system, the provided
SMA shorting plug must be used. Additionally, the laser safety interlock key on the front panel must
be turned to ENABLE. If both interlocks are cleared, the Laser On LED on the front panel will blink
green and the laser may be powered by you using the GUI.
WARNING: Do not enable the laser without a fiber or an equivalent device attached to the TX
OUTPUT connector.
3.6.2 The TX/RX Bar
NOTE: The laser cannot be turned on or adjusted before traffic has been configured. You must
define a signal for testing purposes before making adjustments using the TX/RX bar.
See Section 3.1 Traffic Configuration for more information about generating traffic.
The transmit side of the bar is discussed in detail. However, the receive operations are analogous and
refer to signal being received through the RX INPUT connector on the front panel. Operations
specific to RX side discussed in more detail in Section 3.7 RX Operations.
FIGURE 3-21: TX/RX Bar
The transmitted power and optical wavelength are displayed and marked. When the Actual Power
button is touched, a pop-up window (Figure 3-22) appears allowing you to enable or disable the laser
and adjust the average optical power level. You may also specify which power units to display (dBm
or mW). The “Maximum Power” entry box allows you to specify the maximum transmit power level
from the OST so as not to damage the DUT.
44
Operating the Transmit Section of the A3308
FIGURE 3-22: Output Power Setup
The average optical power level reported by the A3308 is calibrated to the input and output
connectors. In addition, it can be calibrated (see Calibration Factor below) by you to points outside of
the instrument (e.g., the end of the fiber jumper). A built-in output attenuator is used to adjust the
transmitted power to a user specified level. The average optical transmitted power can be directly
adjusted from -35 dBm to -6 dBm.
The OMA and the Laser Status option are now set via the Output Power Setup screen Figure 3-22.
OMA. Optical Modulation Amplitude (OMA) is a quantity defined for the new 10GE standard for
NRZ systems. OMA is the difference in optical power for the nominal "1" and "0" levels of the
optical signal. The OMA of received signals may be displayed in the A3308's graphical user
interface, by selecting the OMA option on the Output Power Setup screen and is expressed in dB or
mW. See Figure 3-21.
Laser Status. Information about the status of the laser is given along the bottom row of the GUI
screen in the TX/RX bar (see Figure 3-21). The Laser Status indicator will display one of the
messages.
1. H/W interlock tripped
2. Laser key is disabled
3. User disabled
4. ON
45
WARNING: Do not enable the laser when no fiber or equivalent device is attached to the TX
OUTPUT connector.
or any fiber/device attached to the output while the laser is in operation.
3.6.3 Calibration Factor
In the default mode, the calibration factor is set to 0 dB and the power shown in the TX Power
indicator represents the true average optical power of the signal produced at the TX OUTPUT
connector. See Figure 2-1, Connector 14. Accurate measurements of many physical layer quantities
(e.g., sensitivity) require that the true power transmitted into the DUT be known. Adjusting the
calibration factor allows the instrument to correct for losses in the optical components connecting the
A3308 to the DUT so that the TX Power indicator shows the actual optical power transmitted into the
DUT.
Figure 3-23 shows the window that pops up when the calibration. button on the TX/RX bar is
touched. You can manually adjust the calibration factor value by touching the CalFactor entry
window and entering a value on the keypad or by using the slider. The Actual Power is listed and the
Corrected Power will show the power level with the calibration factor taken into account. The
Corrected Power should match the power measured at the DUT using an accurate power meter. You
may instead choose to directly specify the Corrected Power and let the A3308 deduce the calibration
factor.
NOTE: Calibration factor is the difference between the Requested Power into the DUT vs. the
Requested Power Out from OST front panel.
Alternatively, the calibration factor can be determined automatically. First, insert the end of the fiber
pigtail that would ordinarily be connected to the DUT should be inserted into the RX INPUT of the
A3308 see Figure 2-1 connector 15. Next, you select Auto Calibrate from the pop-up window. The
internal power meter measures the power present on the fiber and adjusts the calibration factor so that
the Corrected Power (as reported in the TX power window) matches the measured result.
The CalFactor Assistant helps you determine the appropriate calibration factor for either of the two
modes described above. When this button is touched, text explaining both the Auto Calibrate and
Manual Modes is displayed. Touching either the Manual or AutoCal buttons will bring up further
explanations and diagrams for connections between the test instrument and the DUT.
46
Operating the Transmit Section of the A3308
FIGURE 3-23: TX Calibration Factor
You may save and retrieve calibration factors from the pop-up menu using the Save and Load buttons.
This allows you to conveniently compensate for several different optical paths (e.g., different ports on
an optical switch) without having to constantly recalibrate this important section of the instrument.
When are you done setting the calibration factor, you should select OK or Cancel.
Wavelength. The wavelength on the TX end cannot be changed, it is hardware dependent.
Traffic. The traffic indicator will display the current traffic selected by you on the traffic generation
page.
Optical Degradation. The optical degradation indicator will display degradation selected by you on
the Optics page. The four options are None, 10G-L, 10G-E, and Custom.
Switch Status. The switch setup indicator will display the switch status for the EDFA Bypass switch,
Monitor Port switch, PPL switch, Ref TX/RX switch selected by you on the Switch setup page.
TX Clock. Indicates clock status of the transmitter.
Trigger Source. The Trigger Source button configures the TRIG CLOCK OUT connector on the
front panel of the A3308 to supply a 155.52 MHz, 161.1328 MHz, or 167.33164 MHz clock signal
synchronous with either the RX clock or the TX clock. It is a toggle button. The intent is to provide a
convenient selection of trigger signal source for eye diagram testing using a third-party oscilloscope.
Extinction Ratio. Extinction ratio is the ratio of the optical power between the “1” state and the “0”
state of an optical signal. The A3308 measures the extinction ratio of the received signal and is
displayed in the ER window on the TX/RX bar and is expressed in dB. See Figure 3-21.
47
3.7 RX Operations
The A3308 accepts signals from your DUT in the RX INPUT connector on the front panel of the
A3308. If this signal is within safe, usable limits the INPUT POWER LED will light green. The LED
will remain off if no signal is detected and if the incoming power signal is too high, the LED will light
red. The A3308 accepts a large input power range from -40 dBm to +10 dBm.
On the GUI, the RX side of the TX/RX bar displays the power, OMA and the ER of the incoming
signal. In addition, you can set the wavelength of the incoming signal, the receive wavelength range is
1280 - 1620 nm. By touching the power button, you may toggle between units of dBm and mW. As
with the TX signal, the RX signal may be calibrated to the input connector or to points outside of the
instrument by using a calibration factor. The RX operation of the calibration factor is similar to the
TX operation (see Section 3.6.2 The TX/RX Bar). Since power losses are typically wavelength
dependant, a calibration factor is only appropriate at a particular wavelength. Therefore, unless the
DUT is transmitting at approximately the same wavelength as the DUT, Auto Calibrate is not
recommended.
The RX Clock indicator at the end of the TX/RX bar shows whether the receive clock has locked on
to the high speed optical signal.
3.8 Bit Error Rate Testing and the BERT Bar

Figure 3-24 shows the BERT bar which appears above the TX/RX bar. This bar provides dynamic
updates of the current Bit Error Rate and gives you instant access to many of the BER testing features.
FIGURE 3-24: BERT Bar
The BERT setup button serves as both the title for the BERT bar and as a button which calls up a
menu to set some basic parameters for the BERT bar. Currently, there are two settings controlled
within this menu (see Figure 3-25).
FIGURE 3-25: BERT Setup
48
Bit Error Rate Testing and the BERT Bar
Error Source for Gating and Instantaneous BER. This is a group of six choices in a drop down
menu as follows: Bit Errors, B1, B2, B3, SEQBRK, FCS, and M1. Bit Error is only available when a
bitstream data pattern is being generated and detected by the A3308; otherwise this selection is not
displayed Similarly, the other error counters are only available with framed data: SONET/SDH, or
PoS; they are not available with unframed data. FCS option is available for 10GE LAN and 10GE
WAN traffic
Audible Error Alarm. When selected the unit will generate an audible alarm every time an error of
the type selected in the Error Source is identified.
Audible SyncLoss Alarm. When selected the unit will generate an audible alarm for the duration
the SyncLoss Alarm is detected.
OK and Cancel. Will either accept or cancel any setup changes just made.
Next on the BERT bar are two error indicators (see Figure 3-24). Both indicators are split and show
the current error status on the left and the history since reset on the right. The Pattern Sync indicator
shows whether the device has verified a pattern match on outgoing and incoming signals. The Pattern
Sync indicator on the GUI and the LED on the front panel of the A3308 should match. The error
indicator below that shows current bit errors.
To the right of the error indicators is a display of the Bit Error Rate (BER). This value is dynamically
updated approximately once a second during testing. Underneath that value is a strip meter that
displays the same information graphically.
3.8.1 Measurement Control
The next three buttons are used to configure special BER tests. The pop-up windows are shown in
Figure 3-26. This section controls how long data is accumulated. In general, the “gate” is the time
during which the data is accumulated. The results display updates only when the gate interval is
complete.
49
FIGURE 3-26: Gate Type, Gate Value for Time Gate Type, and Gate Control
3.8.1.1 Gate Type
If gating is selected, this button controls the three different ways in which gating is implemented.
Selecting this brings up an OK/Cancel menu with three radio buttons: “Time”, “Errors”, and
“Uncertainty”. Gating by “time” indicates that the measurement will integrate errors until a certain
period of time has passed. Gating by “errors” indicates that the A3308 will continue to record data
until a particular number of errors are accumulated. Gating by “uncertainty” is similar to gating by
“errors”, but the measurement continues until the statistical uncertainty on the number of errors is
achieved. Gating by “uncertainty” control is only available if the “Gate Control” (discussed below) is
set to “Single” or “Repeat”; it is grayed out if “Gate Control” is set to “Accumulate”. Whatever
“Gate Type” is chosen, the name should be reflected in the “Desired” and “Actual” controls discussed
below. When choosing gate type “Error” and “Uncertainty” you must specify the error source.
Desired Time. This button control allows you to select how much time/errors/uncertainty is required
to complete one data recording gate. The name of the button should appear on the bottom of the
control as “Desired Time”, “Desired Errors”, or “Desired Uncertainty”. The number field above the
name on the button is accessed by clicking on the button, and the field formatting should change
based on what the name of the button is: Time (DD:HH:MM:SS), Errors (Integer number),
Uncertainty (number between 0 and 1). This button is greyed out (and the style is set to “Desired
Time” with a field entry of 00:00:00:00 if “Gate Type” is set to Accumulate.
Actual Time. This indicator shows the amount of Time/Errors/Uncertainty that has accumulated in
the current gate cycle. The name is context sensitive based on what the “Gate Type” is: “Actual
50
Time”, “Actual Errors”, or “Actual Uncertainty”. The field format is context sensitive exactly as
described for the “Desired” field. If “Gate Type” is set to accumulate, this field should report “Actual
Time” since the start of the measurement.
Progress Bar. The progress bar is a bar graph that spans the area below the “Desired” button and
“Actual” indicator. It graphically displays the “Actual” to “Desired” ratio. It tracks the completion of
the current gating cycle. The progress bar is inactive if “Gate Type” is set to accumulate.
Gate Control. Clicking on this button brings up an OK/Cancel radio button menu with four choices:
“Single”, “Repeat”, “Accumulate”, and “Accumulate Totals Instantaneous Rates”
1. “Single”. Implies that once the measurement has started one gating cycle will be completed, the
results area will be updated, and the measurement will stop until you interact with the BERT bar
again. During the single gate, the progress bar and actual fields will be updated.
2. “Repeat”. Implies that unless you interact with the BERT bar sometime in the future, once the
measurement has started, each gating cycle will be followed by another. During each gating cycle, the
progress bar and actual fields will be updated. The results fields are each updated at the end of each
gating cycle.
3. “Accumulate”. Implies that data will continue to be accumulated until you select “Stop” (The
Start/Stop control is discussed next). In the “Accumulate” mode, the results fields are updated every
measurement period (approximately 1 second). The results are accumulated from the beginning of the
test. Measurement data is collected from the time you select start to the time the stop button is
pressed.
4. “Accumulate Totals Instantaneous Rates”. In this mode the A3308 gives a snap shot of what
happened during the previous measurement period (approximately 1 second). The measurements are
not from the time you select start.
Start/Stop. Pressing the “Start” button initiates a BERT bar measurement. This button is only
available if there is no BERT bar measurement in progress. Once a measurement has commenced the
“Start” button changes to a “Stop” button. Pressing the “Stop” button stops the measurement in
progress. There are three possibilities when pressing the “Stop” button:
1. If the Gate Control is “Accumulate”, the results fields should show the last updates.
2. If the Gate Control is “Single”, the results displays should go from blank to the results as of the
point at which the stop was pressed. The Actual Time/Error/Uncertainty field should show the
answer as of when the counter was stopped.
3. If the measurement was gated as “Repeat” and at least one gating cycle has completed, the results
do not update; the result of the previous gate should remain on the screen, and the “Actual
Time/Error/Uncertainty” should be shown as a complete cycle: the result from the last cycle of the
gate. (If a single cycle has not yet completed, then the results and the Actual
Time/Error/Uncertainty field should behave as described in the “Single” section above.)
3.8.2 Results
The results section shows three result pairs; each pair is one column with the value in the top row and
the uncertainty in the bottom row. Each pair shows the result value along with its associated
uncertainty.
While appearing separate, the three pairs are treated by the GUI as one contiguous button. Clicking
anywhere in this region invokes a menu which contains a column of all possible result names along
51
with three columns of radio buttons, each one of which corresponds to the same column on the BERT
bar. The field names are context sensitive; they are only available if the corresponding data is being
transmitted. (For example, SONET Errors are only available if SONET traffic is being generated,
etc.)
Uncertainties on all of these quantities are to be calculated using binomial statistics as detailed in
Circadiant’s BER Measurements paper.
Bit Errors: This is available only if bitstream traffic is being generated; otherwise the option is
greyed out. This is the total number of bit errors observed in the gating period.
Bit Error Rate: This is available only if bitstream traffic is being generated; and is defined as the
total number of errors divided by the total number of transmitted bits. This is the Bit Error Rate
observed in the gating period. Displayed as #.##E-##.
Omit Errors (1 misidentified as 0): This is available only if bitstream traffic is being generated;
otherwise the option is not listed. This is the number of errors where logical ones were misidentified
as logical zeros.
Omit Error Rate (1 misidentified as 0): This is available only if bitstream traffic is being
generated; otherwise the option is not listed. This is the error rate determined by dividing the number
of omit errors by the total number of bits. Displayed as #.##E-##.
Omit Fraction (1 misidentified as 0) This is available only if bitstream traffic is being generated;
otherwise the option is not listed. This is the number of omit errors divided by the total number of
errors. Ideally, this quantity would always be equal to 0.5. Displayed as 0.###.
Insert Errors (0 misidentified as 1): This is available only if bitstream traffic is being generated;
otherwise the option is not listed. This is the number of errors where logical 0 were misidentified as
logical 1.
Insert Error Rate (0 misidentified as 1): This is available only if bitstream traffic is being
generated; otherwise the option is not listed. This is the error rate determined by dividing the number
of insert errors by the total number of bits. Displayed as #.##E-##.
Insert Fraction (0 misidentified as 1): This is available only if bitstream traffic is being generated;
otherwise the option is not listed. This is the number of insert errors divided by the total number of
errors. Ideally, this quantity would always be equal to 0.5. Displayed as 0.###.
3.8.2.1 SONET/SDH Coding Errors
B1 Errors (CV-S). This is available only with SONET framed traffic. The total number of B1 errors
within the gate period; B1 errors are also called Section Layer Coding Violations (CV-S). The field
name on BERT bar: “B1 (CV-S)”. For SDH framed traffic, this is called B1 Errors (CV-R) since for
SDH it is the counter for the regenerator section.
B1 Error Rate. This is available only with SONET/SDH framed traffic. This is the number of B1
errors divided by the total number of bits sent.
B1 Corrected Error Rate. This is available only with SONET/SDH framed traffic. This is the B1
Error Rate corrected using the formula defined in Circadiant’s BER Measurement paper.
52
B2 Errors (CV-L). This is available only with SONET/SDH framed traffic. The total number of B2
errors within the gate period; B2 errors are also called Line Layer Coding Violations (CV-L).
Fieldname on BERT bar: “B2 (CV-L)”. For SDH framed traffic, this is called B2 Errors (CV-MS)
since for SDH it is the counter for the regenerator section.
B3 Errors (CV-P). This is available only with SONET/SDH framed traffic. The total number of B3
errors within the gate period; B3 errors are also called Path Layer Coding Violations (CV-P). The
field name on BERT bar is: “B3 (CV-P)”. For SDH framed traffic, this is called B3 Errors (CV-HP)
since for SDH it is the counter for the regenerator section.
M1 Errors (REI-L). This is available only with SONET/SDH framed traffic. This is the number of
errors reported by the M1 byte in the SONET/SDH frame. This is described in section 3.3.2.2 of
GR253, Revision 2. Fieldname on BERT bar: “M1 (REI-L)”. For SDH framed traffic, this is called
M1 Errors (MS-REI) since for SDH it is the counter for the multiplex section.
M1 Error Rate. This is available only with SONET/SDH framed traffic. This is the number of
errors reported by the M1 byte in the SONET/SDH frame divided by the total number of bits
transmitted.
Section Errored Seconds (ES-S). According to Section 6.2.2.3.1 of GR253, Revision 2, “The ES–S
parameter is a count of the number of seconds during which (at any point during the second) at least
one Section layer BIP error was detected or an SEF (Severely Errored Framing) or LOS (Loss of
Signal) defect was present.”
For SDH framed traffic, this is called Regenerator Section Errored Seconds (ES-R) since for SDH it
is the counter for the regenerator section.
Section Severely Errored Seconds (SES-S). The severely errored seconds is the count of seconds
in which 8,854 or more errors were BIP (B1) errors were detected.
Section Unavailable Seconds (Unavail Sec). Is the count in seconds that section becomes
unavailable. A section becomes unavailable at the onset of 10 consecutively seconds that qualify as
SES-S and continues to be unavailable until the onset of 10 consecutive seconds that do not qualify as
an SES-S.
3.8.2.2 Ethernet Coding Errors
FCS Derived BER. This available only with 10GE LAN and 10GE WAN traffic.
53
FCS Err’d Frame. This is the number of frames with Frame checksum error. This is available only
with 10GE LAN and 10GE WAN traffic.
SEQBRK. This is the number of times that the repeating sequence imbedded into the first 16 bits of
the IP payload by the OST is broken. Each out of sequence break is calculated as one bit error.
54
CHAPTER 4 Other Modes
4.1 IntelliScriptTM
The IntelliScriptTM feature is a very powerful productivity enhancer. IntelliScriptTM allows you to
define an automated sequence of tests using a simple point-and-click interface. Any of the built-in
tests with the user defined parameters can be included. In addition, this feature can (in a development
lab for instance) be used to run a complete suite of diagnostic tests over the course of many hours.
You simply initiate the test series and return at your leisure to collect the results. In manufacturing
applications, IntelliScript™ allows for efficient pass/fail testing with automatic report generation.
With a barcode reader a suite of tests can be run just by scanning the barcode of the DUT and naming
the configuration appropriately.
Figure 4-1 shows the main window after selecting the IntelliScript™ tab along the top of the GUI.
The top window, labelled Test Information, allows you to identify the IntelliScript™ series for future
reference and to specify what action should be taken in the event of a test failure. The Stop on Fail
feature improves throughput in cases where continuing the sequence would be useless. The A3308
can also generate an e-mail message if a failure is detected and/or generates an audible alarm. In the
calibration file field you have two options NONE and FACTORY. NONE implies use current
calibration, FACTORY means reload factory calibration.
NOTE: Desired test and signal configurations must already be defined and saved to be selected
from the IntelliScript™ menu. Test configurations are defined and saved from their
respective setup screens while signal configurations are defined and saved from the
main signal configuration menu.
Below the Test Information window is the IntelliScript™ Setup window. Along the bottom of the
setup window are the icons Start, Add Config, Load, Save, Move Up, Move Down, Hide Config,
Clear All, Save PNG, and Print. To add a test to the sequence select Add Config. Once a test is added,
you may touch the buttons under Test, Test Configuration, and Traffic Type/Signal Configuration to
determine which test will be run and which previously saved test and signal configurations will be
used. The test in the sequence can be rearranged or hidden using the Move Up, Move Down, and Hide
Config icons.
55
Other Modes
For each test there are a three check box options available.
1. The “Active” checkbox, when selected will run that test during the IntelliScript™ test execution.
2. The “Print” checkbox, when selected, outputs the test results to a printer.
3. The “Page Break After” checkbox, when selected, will allow the test results to first be printed on a
page, if selected, and then will eject the page from the printer.
FIGURE 4-1: IntelliScriptTM Setup
Action. Pressing one of the buttons in the “Action” column brings up a Test Selection dialog box
with a pull-down list of available tests such as Sensitivity, Overload, BER vs. OSNR, or IsoBER.
Select the test you want and press OK.
You also may choose to Define Traffic that lets you establish the traffic output by the 10 Gb/s Optical
Standards Test System and used in subsequent IntelliScriptTM tests.
You may also choose an external instrument to control, if previously defined (See Section 4.2). Select
the Test Type, Select the Device ID and, if desired, provide a test alias. The test alias will then be
available on the pull-down list of available tests under the “Action” column.
Configuration. Pressing one of the buttons under the Configuration column allows you to load a
previously defined test configuration and run the test chosen using that configuration.
Traffic Type/Signal Configuration. All IntelliScriptTM are run using the current configuration
unless a specific Traffic Type/Signal Configuration is activated. Tests will continue to be run using
the defined Traffic Type/Signal Configuration until a new Traffic Type/Signal Configuration is
56
IntelliScriptTM
selected. This allows you, for example, to run the same sensitivity test using 10 Gigabit Ethernet
protocol, pass/fail criteria, time, and fit algorithm first using the standard “L” Long-Reach stressed
receiver conformance degradation and then after defining a new Traffic Type/Signal Configuration to
run the same test using the “E” Extended-Reach standard degradation.
User Parameters. This feature will be enabled on a future software release and may not be selected
by you at this time.
Compare. You can specify a reference result to superpose on the test result.
Once testing is begun, you will be transferred to the IntelliScript™ results screen shown in Figure 4-
2. Here, the test name and configurations are listed and the test status is updated as each test in the
series is completed. This screen may be saved or printed using the icons at the bottom of the window.
The test series may also be stopped and restarted. The result summary column shows the test status.
In order to access a saved IntelliScript™ series, click on the Load icon, select the appropriate file and
then click OK. Clicking Start will begin the test sequence.
FIGURE 4-2: IntelliScriptTM Results Page
57
Other Modes
4.2 External Instrument Control
FIGURE 4-3: External Instrument Control Main Screen
Touching this tab brings up the main screen shown in Figure 4-3 with a series of icons, representing
instrument types, which may be controlled by you through the OST. Communication with, and device
identity of external instruments are set up in the External Instrument Configuration section found on
the Admin page. The GPIB Master connection is used as the communication link between the OST
and External Instruments. In a future software release, an External Instrument’s Address may be
entered as an IP address and the communication will be via the A3301 System Controller’s 10/100
Remote Control RJ45 connector. Grayed-out icons are not controllable by the OST at this time.
Touching the icon for the desired instrument type brings up a detailed instrument control menu.
External Instruments may be configured and then run through IntelliScript™.
4.2.1 Optical Spectrum Analyzer Control

This menu page is essentially an Optical Spectrum Analyzer (OSA) control panel. The OST is first
directed to interface with a particular OSA via Setup. Then five steps are followed to obtain
measurements. Actions are performed in sequential order once either IntelliScript™ is run or the
Execute All Selected Actions button is pressed.
Setup. In this section you enter the ID number of the instrument and establish the Pass Criteria for
the DUT.
1. Initialization. In this step you can choose to initialize the OSA or to bypass the step.
58
External Instrument Control
• Initialize. This is a recommended step.

• Bypass Initialization.
2. AutoLocate. In this step the desired signal is properly positioned on the OSA screen.
• Auto Measure. The OSA will automatically locate the optical signal on the screen by utilizing
the OSA’s auto measurement routine.
• FF Center. The OSA will use a fast algorithm to determine the center wavelength and will return
the center wavelength value. This is typically a faster routine than the Auto Measure because the
scanned wavelength range is narrower than the OSA’s built-in auto measurement routine and the
OST has a more limited wavelength range than the OSA.
• Execute All Selected Action. This will execute actions selected in Steps 1-5 via their check box.
Click individual action buttons to execute action immediately.
FIGURE 4-4: Optical Spectrum Analyser Control
3. In this step, information about the peak optical signal is obtained. Results may be obtained
without additional OSA sweeps in this step. If you wish to obtain a fresh sweep, the Auto Acquire
button should be pressed. It is not necessary to select any step 3 test parameters if only step 4 is
desired.
• Manual Acquire. This performs a single sweep on the OSA.
• Auto Acquire. When selected the OSA will perform a new sweep before measuring OSNR,
amplitude or lambda.
59
Other Modes
• Mkr OSNR. This returns the OSNR as measured by the OSA. The value returned may be less
accurate then the OSNR using the Circadiant algorithm in Step 4. Some OSA’s do not support this
measurement.
• Mkr Amplitude. Returns the value of the peak amplitude.
• Mkr Lambda. Returns the wavelength of the peak.
4. In this step sweep measurements will be made automatically on the OSA to obtain the results.
• OSNR. The OSNR of the peak signal is measured utilizing Circadiant Systems OSNR
algorithms. For more information on Circadiant Systems OSNR algorithms, please visit
http://www.circadiant.com and read the Optical Signal to Noise Ratio Tech Brief in the
Technology section of the web site http://www.circadiant.com/technology/index.html.
5. Raw Write/Read. In this step you may write to or read from the OSA.
• Raw Write. Passes a command straight to the OSA.
• Raw Read. Reads a response from the OSA.
Results. In this section of the screen, test results are displayed.
4.2.2 Optical Oscilloscope Control
FIGURE 4-5: Optical Oscilloscope Control Screen
60
4.2.3 Optical Switch Control
FIGURE 4-6: Optical Switch Control Screen
61
Other Modes
4.2.4 Wavelength Meter Control
FIGURE 4-7: Wavelength Meter Control Screen
62
4.2.5 Power Supply Control
FIGURE 4-8: Power Supply Control Screen
63
Other Modes
4.2.6 Temperature Controller
FIGURE 4-9: Temperature Controller Screen
64
Internal Process Control
4.3 Internal Process Control
FIGURE 4-10: Internal Process Control - Main Screen
Utilizing Circadiant’s Secured-Accuracy™ feature, you can always check to see that the OST is in
calibration. The Secured-Accuracy™ feature takes advantage of the OST’s system-like performance.
Instead of a stand-alone instrument, the OST includes enough combined instrumentation to perform a
SelfTest. After an OST is calibrated, each OST has a base-line SelfTest run on many of its own
parameters. Results are stored in a series of Internal Process Control charts. You have the option of
running the same SelfTest routines at any time and observing if the SelfTest results are still within
manufacturing tolerances. The Circadiant Secured-Accuracy™ feature provides concrete evidence
that the OST is in calibration prior to the commencement of a test. This ensures that test results are
accurate and are not due to test set drift.
To reach the Internal Process Control GUI pages, press the “Internal Process Control” tab at the top of
the GUI. If pressing the Internal Process Control tab does not work, exit from what you are doing and
retry from that point.
Press the appropriate “Setup Instructions” button for a view of the proper cable configurations for the
A3308 or the A3318 that must be in place before conducting a SelfTest.
To run the SelfTest, press the appropriate “Go to SelfTest Control” button for the A3308 or the
A3318.
To look at the saved process control charts, press the “View Control Charts” icon or you may connect
a web browser to the A3301 and point to the address located in the Process Control Charts
instructions as shown in Figure 4-10.
65
Other Modes
4.3.1 SelfTest Setup

This section includes a photo of the A3308 in loopback mode and a description of how to perform the
Circadiant Secured-Accuracy™ SelfTest. In loopback mode, a Single Mode cable is connected
between the OUT TRANSMIT TO DUT port and the IN RECEIVE FROM DUT port.
FIGURE 4-11: A3308 Single Mode SelfTest Setup Instructions
66
FIGURE 4-12: A3318 Multi-Mode SelfTest Setup Instructions
Introduction. Circadiant recommends executing the SelfTest sequence frequently (e.g., once daily).
Along with verifying the functionality of the critical elements within the OST, the SelfTest sequence
also varies optical degradation parameters within the OST and verifies that the measured loopback
sensitivity behaves as expected. Since the loopback sensitivity depends critically on each of these
parameters, it demonstrates that the OST is functioning correctly. The parametric results from each
SelfTest are stored internally to allow long-term monitoring of measurement repeatability. Instead of
simply relying on the calibration certificate, the results of these SelfTests can be viewed as control
charts to verify directly that measurements that were made in the past have the same meaning as
measurements that are made today or in the future.
Progress. The progress bar displays the percent complete for the entire SelfTest sequence. The
elapsed time sequence shows time in seconds from the start of run.
Results. The results area shows the sequence of tests, updated with their status fields as they
execute. If all results are shown as PASS, the OST is within calibration tolerances. Detailed time
series of individual parametric results are available in the process control charts.
Go Back. To view the process control charts at the conclusion of the Secured-Accuracy™ SelfTest
feature, you may press the Go Back icon and then press the View Control Charts Icon.
At the conclusion of each run, you must select either Accept or Reject results. Only if you select
accept will the results be saved.
67
Other Modes
4.3.2 SelfTest Results
FIGURE 4-13: A3308 Single Mode SelfTest Results
68
FIGURE 4-14: A3318 Multi-Mode SelfTest Results
4.3.3 Process Control Charts

Each test result is recorded on a process control chart. Upper and lower boundaries are visible, as is
each data point located on the vertical axis (displaying the value) and the horizontal axis (displaying
the date). The resolution is very fine and some movement from a test to test is expected on such a fine
scale.
Select the View Control Charts icon below to view and/or generate reports of the SelfTest results
versus time. The control charts offer direct evidence of the repeatability of the measurement system.
If the OST is attached to a LAN, the control charts can also be viewed via a web browser, directed to
the OST’s address, and then following links to “Process Control Charts”.
The OST’s address is available from the “Set IP Address” icon on the ADMIN screen. For further
help with web access to this system, launch the web browser from the ADMIN screen and follow the
“Help” link.
Print All Plots. Pressing this icon on an Internal Process Control chart will cause all of the Internal
Process Control charts to print.
Zoom. Pressing this icon directs you to touch the plot in the desired zoom area. You may then zoom
in zoom out or in Auto Range, may zoom both axes, just the horizontal axis or just the vertical axis.
Previous Plot. Pressing this icon repeatedly will cycle through all the plots in reverse order.
69
Other Modes
Next Plot. Pressing this icon repeatedly will cycle through all the plots, in order.
4.4 Admin
The A3301 Controller setup and External Device Configuration are accessed via the Administration
screen.
FIGURE 4-15: Administration Screen
70
Admin
4.4.1 A3301 Configuration
FIGURE 4-16: GPIB Manager Screen
GPIB. The A3308 10 Gb/s Optical Standards Tester has two GPIB interfaces available. One is a
Master which can be used to control external devices. This could be another instrument such as a
oscilloscope or OSA, or it could be an oven or power supply. The second allows another computer to
control the A3308.
You may configure the primary address (PAD) of the master and slave interfaces by selecting this
icon. A radio button is also available to startup the service that will allow remote control of the A3308
via GPIB or ethernet.
FIGURE 4-17: Set IP Address Screen
Set IP Address. Pressing this icon brings up a menu that allows you to set the Boot Protocol, IP
Address, Subnet Mask and Gateway Address.
Set Date & Time. Pressing this icon brings up a clock setting application.
71
Other Modes
FIGURE 4-18: SMTP Mail Configuration Screen
FIGURE 4-19: Modify Recipient E-mail on Test Failure Screen
E-Mail Configuration. Pressing this icon brings up the SMTP Mail Configuration. The address
entered in the “Enter E-mail address to use for sending mail” field becomes the “From” address when
the OST is used to send mails, such as when you choose to send an E-Mail on a Test Failure. You
must also enter the SMTP server name. The server must be configured by your IT department to
allow E-mail from the OSTC.
Touch Screen Calibration. Pressing this icon guides you through a short touch screen calibration
process.
72
Admin
FIGURE 4-20: Volume Control Screen
Adjust Audio Volume. Pressing this icon brings up a volume control slide bar and a mute control.
FIGURE 4-21: Operating System Software Update Screen
Software Update via CD. Pressing this icon while a new operating system CD is in the CD
Read/Write drive will guide you through the update process. Pressing the icon without a CD also
allows you to determine the version of the Circadiant Network Operating System (CIRNOS) that is
running on the A3301 and the A3308.
Browser. Touching this icon brings up the help menu, access to view or download results, a list of
GNU General Public Licenses, Log files, Images, the IntelliScript™ Debug Station, and Process
Control Charts.
Shut Down System. Touching this icon brings up a window asking if you really want to shutdown or
to cancel. This is the preferred way to shut the A3301 and A3308 down. This allows everything to be
73
Other Modes
closed properly. Cutting power abruptly by pulling the plug or pressing the ON/OFF buttons to cut
power may, intermittently, lead to data loss or problems with the CIRNOS. If power is abruptly cut,
the bootup time may be lengthened the next time the OST is powered up.
4.4.2 IP Address and Network Configuration
FIGURE 4-22: Remote Administration
Remote OST Administration. Touching this icon brings you to a tool that allows Circadiant
Systems to help diagnose problems with your A3308 10 Gb/s Optical Standards Tester, A3318 850
nm/Electrical OST Interface and A3301 OST System Controller. This tool should only be used under
the direction of a Circadiant authorized support representative. Pressing “Start” initiates a connection
with the Circadiant Systems support center. A Circadiant Systems product support engineer must
open the appropriate port at the Circadiant product support center for the connection to be made.
Without live Circadiant support help, no connection is possible and this tool is inoperable.
Do not press “Start” without live on-site Circadiant help because cancelling the request can leave
your OST in an unstable condition. It is recommended that the OST be restarted if you happen to
press “Start” to initiate Remote Administration followed by pressing “Cancel”.
To establish the link between your Optical Standards Tester and the Circadiant Systems product
support center, your Circadiant representative will press “Start” and your OST will be placed under
Remote Control by a Circadiant product support engineer. If you have trouble establishing the link,
you may need to turn off firewalls between your OST and the Internet.
74
Admin
FIGURE 4-23: GUI Preferences for Status Bar and Balloon Help Configuration
FIGURE 4-24: GUI Preferences for Miscellaneous Categories
GUI Preferences. Touching this icon brings up a window that lets you set your preferences for status
bar and help configurations.
75
Other Modes
4.4.3 External Device Configuration
FIGURE 4-25: Backup and File Management Screen
Backup & File Management. Touching this icon brings up a list of directories and files on the left
and right. Files on the left may be selected for backup to USB Drive. Files on the right may be
selected for restore from the USB Drive.
When you click on the Backup & File Management icon the results are stored in a database on the
internal hard drive. You have several options for retrieving the results. USB memory stick are
supported. To save the results to USB memory stick, follow the procedure below.
Click on the administration tab on the bottom of the screen.
In the External Device Configuration section click on Backup & File Management.
Select Backup to device: USB Drive
Select files and click ok.
When the backup is complete the backup successful message will be displayed on the screen.
The extensions for the file types are:
.res = Test Results file
.par = Test Parameter file
.cfg = Test Configuration file
76
Admin
You can also save to USB directly from the Test Results page Access to the results can also be
obtained by the web browser interface. If a 3301 is on a LAN, you can access DB entries directly (via
ODBC).
Select Printer. Touching this icon brings up a window that allows you to configure printers with the
OST. The printer selected in this window will be the printer used to print the OST results.
FIGURE 4-26: Connect to External Device Screen
77
Other Modes
FIGURE 4-27: Connect to A3318 Screen
Connect to External Device. Touching this icon brings up a window that allows you to add or
remove OST’s from control by the A3301 System Controller.
FIGURE 4-28: External Instrument Configuration & Definition Screen
External Instrument Configuration. Touching this icon brings up a window that allows you to
assign addresses, slot numbers and channels for external instruments connected to the OST.
78
Admin
FIGURE 4-29: Feature Activation Screen
Feature Activation. Touching this icon brings up a window that enables you to turn on locked-out
CIRNOS features with passwords supplied by Circadiant Systems.
79
Other Modes
80
CHAPTER 5 RX Tests
The A3308 10 Gb/s Optical Standards Tester makes a variety of RX measurements including
Sensitivity, S/X Measurement, Overload, IsoBER, and BER vs. OSNR. You must select and
configure the desired type of traffic prior to making measurements. You may wish to first verify that
the A3308 is operating error free by placing it in loopback mode and running SelfTest through the use
of the built-in Internal Process Control feature.
FIGURE 5-1: Main Window
81
RX Tests
NOTE: All tests performed by the A3308 include user controlled setup options. Many of these
options are repeated between tests. Detailed descriptions of the common functions are
provided in the Sensitivity section of the User’s Manual. Options and features unique
to S/X Measurement, Overload, IsoBER, BER vs. OSNR, Path Penalty, and Optical
Power are covered in the sections of the User’s Manual specific to those tests.
5.1 Sensitivity
To measure the Sensitivity of a DUT, select the Sensitivity icon under RX Tests. This
test characterizes the minimum input signal required to produce a specified BER. The
Sensitivity test screen displays six tabs that define the configurations for the Sensitivity tests. Initially
the Basic tab is displayed. Use of each of these tabs is described in the following sections.
The Basic tab sets the four major test configurations.
Initialization tab establishes the parameters governing how the A3308 will start a test.
Mode Control tab refines the parameters of the mode selected on the Basic tab.
FastScan Control tab sets the default or custom values for FastScan Control.
Fit, Uncertainty, Pass Criteria tab sets the Fit Quality metric, the statistical methodologies to
calculate test results, and the status for determining why the A3308 reported a fail result.
Summary tab displays the all parameter values set for the test.
Note: From the Basic configuration tab you can apply factory defaults to all five tabs by
selecting the orange button tagged “Reset All Tabs To Defaults”. All entry fields when
selected will display a virtual keyboard for editing. Overwrite any default value by
using the virtual keyboard.
At the bottom of each tab are the following icons:
FIGURE 5-2: Sensitivity Screen Icons
Start initiates the test.
Load lists the saved test configurations. You may select a configuration to load from the list.
Save stores the current configuration.
Save PNG performs a screen capture and saves the file on the A3308’s hard drive.
82
Sensitivity
Print performs a screen capture and sends it to a printer. The screen capture is not saved. The printer
is selected through the Administration screen under External Device Configuration.
Exit takes you back to the main GUI screen.
5.1.1 Basic Configuration Tab
Use the Basic Configuration tab to set the four major test configurations: AutoBER, AutoPower,
IntelliTime™ Mode, IntelliPass™ Mode. Only one test mode may be selected at a time. Modes
AutoBER and IntelliPassTM allow for an option of using FastScan Results Only. Follow Steps 1-4
illustrated on the tab.
Follow Steps 1,2,3,4
FIGURE 5-3: Optical Sensitivity Setup Screen (Basic)
5.1.1.1 Step 1: Choose Test Mode & Features

The Step 1 section of the Basic tab summarizes the different test modes. Detailed descriptions of the
algorithms are given in the following sections.
In AutoBER test mode, a Bit Error Ratio (BER) vs. power or BER vs. OMA plot is automatically
generated with you selecting the range of BERs to be tested. If the FastScan Results Only option is
enabled, the measurement stops once the FastScan successfully establishes a fit, and this fit is used in
lieu of the full measurement to compute the final result.
83
RX Tests
BER is displayed on the vertical axis and power on the horizontal axis. You may have the testing
begin from high BER (e.g. 1E-5) to low BER (e.g. 1E-12) or from low BER to high BER. A FastScan
is first performed by the A3308 to determine the approximate power range that corresponds to the
user selected BER range. Once the approximate power range is identified, TX output power is set to a
level that corresponds to the user selected Start BER value.
Power levels are stepped through the approximate power range based on your selected options.
Testing is stopped after data taking is completed at the Finish BER selected value. The AutoBER
mode speeds testing of DUTs where a priori information of the appropriate power ranges that
correspond to desired BER test levels are unknown.
In AutoPower test mode, a BER vs. power plot is automatically generated with you selecting the
optical power range to be tested. BER is displayed on the vertical axis and power on the horizontal
axis. Testing begins at the start power and concludes at the finish power. You may test from low
power to high power or from high power to low power.
In IntelliTime™ mode, you enter the time allotted for the test. The A3308 uses its own algorithms to
provide the lowest possible measurement uncertainty using the allotted time. Algorithms determine
the amount of time spent taking data at each input level. One may observe that relatively less time is
spent on receiver input levels corresponding to high BER levels and more time is spent accumulating
data corresponding to low BER levels. The A3308 automatically adjusts the input levels to the
receiver under test. At the conclusion of the allotted time, testing stops.
IntelliPass™ mode reduces cycle time in manufacturing environments. You may allow the test to run
only until a passing value is reached. This can save valuable test time by quickly identifying which
devices perform significantly better specifications. A maximum time to spend on each device must be
specified by you. To the extent that it is not possible to pass the device within the time frame given, a
device fails by default with an “UNKNOWN” condition. You can modify this behavior in the Mode
Control tab. If the FastScan Results Only option is enabled, the initial AutoBER portion of the
IntelliPass™ algorithm is replaced by the FastScan result. The measurement then proceeds to post-
test (floor search and salvage, see Section 5.1.3.3)
Set one of the test modes as listed in the following table.
TABLE 5-1: Test Modes and Features
Mode/ Feature Field Description and Values

AutoBER Start BER The value at which the A3308 begins to make measurements.
The start BER value may be either a high BER or a low BER.
This provides you with the option of beginning to make BER
measurements either at high power or at low power.
Finish BER The finish BER value that is entered into this box is the last
BER level that will be tested by the A3308.
AutoPower Start Power Start Power (dBm). The value at which the A3308 begins to
(dBm) make measurements. The Start Power value may be either a
high power or a low power. This provides you with the option of
beginning to make BER measurements either at high power or
at low power.
Finish Power The last power level value at which BER measurements are
(dBm) made.
84
Sensitivity
TABLE 5-1: Test Modes and Features
Mode/ Feature Field Description and Values

IntelliTime™ Time (min). Timer value in minutes. The A3308 will continue to take test
data until the timer expires.
IntelliPass™. Max Time The A3308 will continue to take test data until the number of
(min) minutes entered in this field have passed or may stop taking data
if the device under test passes or fails prior to the maximum
time.
FastScan Checkbox This option is only valid in conjunction with AutoBER and
Results Only IntelliPassTM modes. When selected, the initial test concludes
with the FastScan results which substitute for the measurement
results. The post-test components (error floor and salvage) are
executed without change, as selected by you.
Power Type Total Aver- The horizontal axis of the BER vs. Power plot will be scaled in
(Results will age Power average power units.
be measured
versus this)
OMA The horizontal axis of the BER plot will be scaled in Optical
Modulation Units. OMA is a specification of optical signal
amplitude.
Average The horizontal axis of the BER plot will be scaled in average
Power of power units without including the additional optical power of
Signal Laser the secondary laser in the A3308, if the secondary laser is on.
Only NOTE: This feature will be enabled on a future software release
and may not be selected by you at this time.
Sensitivity This value defines the BER for which the measurement result
Definition (horizontal value of average power or OMA) is reported. Typi-
(BER) cally this would be set to 1E-12. The defined pass criterion in
step 3 sets the horizontal axis for determining if a DUT passes
or fails. The other criteria that you can select if a cut is made on
uncertainty or Fit Quality in “Fit, Uncertainty, Pass Criteria” tab
must be passed for the DUT to have an overall PASS include
Uncertainty and Fit. If just one of these three pass/fail criteria is
not met, the DUT will FAIL the test.
Refer to the other configuration tabs for additional control over measurement algorithms.
5.1.1.2 Step 2: Choose Signal Configuration(s) for Run Control
In this step, you select the type of signal to be used when each test is run by activating the
configuration. You can use the following screen to select and activate the signal configuration. To
activate a configuration, click on the Active box for the corresponding configuration.
The current configuration file current.cfg is the currently selected traffic. You may chose other
configurations that were saved in the signal configuration page. The signal configuration includes the
85
RX Tests
type of traffic, the selected optical degradations, the switch set-up and the clock settings that were
chosen under the Signal Configuration column of the main GUI screen. You can also select the error
source for the measurement if the signal configuration file supports more than one error source. Error
sources include:
FCS. If there is a frame check sum error in an Ethernet frame the OST assumes one bit was in error.
SEQBRK. This is the beta feature in Version 6. If there is a sequence break, the OST assumes one
bit error. With this error source selected, the OST transmits Ethernet SNAP frames with a repeating
sequence of numbers placed in the first 16 bits of the IP payload. SEQBRK is intended to be used to
test switches and routers with architectures that will not pass PRBS traffic or packets with errors from
one port to another. SEQBRK is useful when loopback can not be configured on a router linecard.
The A3308 will display the test results on the same screen for up to ten different signal configurations
in a different color or symbol. This provides you with an easy way to compare the performance of a
DUT with various signal configurations (for example, with and without various stresses applied).
FIGURE 5-4: Signal Configuration Selection Screen
TABLE 5-2: Signal Configuration Icons
Icons Description
Add Configuration You may load saved signal configurations by pressing the Add Configuration
icon, then selecting the desired file by clicking on the folder icon next to it.
Edit Configuration You may modify a saved signal configuration by first highlighting the file name
and then pressing the Edit Configuration button. Once all changes to the signal
configuration tabs are completed, you save the file as either the same name or
may choose a new name for the file.
Rename Configuration You may rename a file by first highlighting the file name and then pressing the
Rename Configuration button. A list of saved configuration files with the high-
lighted filename ready to be overwritten with a new name will be displayed.
Using the virtual keypad the new filename can be entered.
Move Up You may change the order the configurations are run in by highlighting a signal
configuration and then selecting Move Up or Move Down. Selecting Move Up
will cause the selected test to advance by one test towards the first test to be con-
ducted.
86
Sensitivity
TABLE 5-2: Signal Configuration Icons
Icons Description
Move Down You may change the order the tests are run in by highlighting a signal configura-
tion and then selecting Move Up or Move Down. Selecting Move Down will
cause the selected test to drop by one test towards the last test to be conducted.
Hide Configuration You may clear a particular traffic configuration from running by highlighting the
signal configuration and then selecting Hide Configuration. This will not delete
the underlying saved file.
5.1.1.3 Step 3: Define Pass Criteria

You can set the Sensitivity (dBm) field to set the horizontal axis value for pass/fail criteria for a
DUT. If the test result is equal to or better than this value, the Sensitivity criterion would be passed.
Note that Fit and Uncertainty also must pass for an overall pass. If one or more of the three criteria
Fail, the DUT will not Pass. See Pass Criteria tab (Section 5.1.5.4) for additional settings.
5.1.1.4 Step 4: Enter Information About DUT

The following DUT specific fields are optional with default values set to “NULL”. As is true for all
entry fields, the default value may be changed via the virtual keyboard. Values may be entered in
these fields through a bar code scanner attached to the A3308’s PS2 port:
• Serial Number
• Product Code
• Comments
5.1.2 Initialization Tab
The Initialization tab is used to establish the parameters governing how the A3308 will start a test.
You may elect to conduct a Pretest to make sure the DUT is a viable candidate for a PASS. You may
also locate the worst performing point over a range of jitter values and perform testing at that point.
You may invoke the A3308’s factory defaults for this tab. This is accomplished by pressing the Reset
to Defaults button. This will not change any settings outside of the options in this tab.
87
RX Tests
FIGURE 5-5: Sensitivity Initialization
The Execute Pretest option conducts a Pretest on a DUT before the main test routine starts. A Power
Level and length of Time for a pretest must be entered. The A3308 will then determine if the DUT is
error free at that power value for that length of time. If so, the remainder of test will be conducted. If
there is one or more error in that length of time, the DUT will automatically fail and the remainder of
the test will be terminated. A Jitter pretest applies only to signal configurations with swept jitter
enabled, and it is recommended that this selection be enabled whenever swept jitter is used.
“Swept Jitter” implies that the clock jitter being applied to the signal is continuously being cycled
through all chosen points. Thus if a sensitivity measurement is performed, only a fraction of the time
is spent at each point. The “find worst case jitter” option allows the test to spend all of its time at the
jitter point that is most stressful for the DUT. During the initialization portion of the reset, the power
is reduced to yield a BER of approximately 1E-8. Each jitter is then tested in turn to determine which
point yields the worst BER. That point is then selected and the test proceeds to completion. The status
window (accessed by pressing the status button located to the left of the clock) shows the worst case
jitter.
Note that the typical DUT should exhibit worst case performance at the highest jitter frequencies.
Furthermore, while this “find worst case jitter” option allows the measurement to spend all of its time
on the worst point, this option does use time during the initialization. Therefore in the interest of time,
if the DUT is well understood, it is more efficient to use single point jitter and restrict the use of swept
jitter to device characterization.
Where you choose 10GE (L) and 10GE (E) and enable Swept Jitter on the Optical Degradation tab of
the Traffic Configuration menu, all 10 available jitter steps will be tested. When you have chosen the
88
Sensitivity
Custom Setup, one to 10 of the defined jitter frequency/amplitude points may be tested. Dwell times
at each point may be set from 0 to 5000 ms by pressing the configure button on the Optical
Degradation menu.
TABLE 5-3: Sensitivity Initialization
Test Field Description

Pretest Power Level (dBm) The value in this field sets the optical power level going to
the DUT for the duration of the Pretest. A constant power
level is maintained throughout the pretest.
Time (seconds) The value in this field sets the duration of the Pretest. If no
errors have occurred during the period, the main test will
begin. If one or more error occurs during the Pretest, the
DUT will automatically fail and the remainder of test will be
terminated.
Jitter Worst case jitter is at NOTE: This feature will be enabled on a future software
highest frequency release and may not be selected by you at this time.
unless BER perfor-
mance at another point
is worse than highest
frequency jitter BER
performance at ___%
CL
Worst case jitter is If you set the traffic configuration to include swept jitter in
point with worst BER the Optical Degradation menu, this feature directs the A3308
performance regard- to conduct the sensitivity test at the worst performing jitter
less of statistical point. The worst case point is automatically determined by
uncertainties first establishing and then fixing the optical power level
associated with a 1E-8 BER. The BER is then measured at
every jitter step and the worst performing point is identified.
The sensitivity measurement will be made with the applied
worst case jitter frequency and amplitude.
5.1.3 Mode Control

The Mode Control tab is used to refine the parameters of the test mode selected in the Basic tab. The
A3308 conducts tests in one of three modes: AutoBER/AutoPower, IntelliPass™, or IntelliTime™.
The screen displayed in the Mode Control tab is context sensitive. For example, if
AutoBER/AutoPower is the mode selected in the Basic tab, then only the parameters related to that
mode may be changed. If you wish to change the mode under which the DUT will be tested, you
should return to the Basic tab and revise the selection there.
89
RX Tests
FIGURE 5-6: Sensitivity Mode Control
You may invoke the A3308’s factory defaults for this tab. This is accomplished by pressing the Reset
to Defaults button. All three mode options shown on the Mode Control tab page will revert back to
factory settings when the Reset to Defaults button is pressed. No changes are made to any settings on
other tabs.
5.1.3.1 AutoBER/AutoPower Test Mode

In the AutoBER and the AutoPower test mode, a Bit Error Ratio (BER) vs. power plot is
automatically generated. BER is displayed on the vertical axis and power on the horizontal axis.
Within the Mode Control tab, you may select either the step size between data points, e.g. 0.5 dB, or
may select the number of data points to be taken. You also have the option to set how long data will
be collected at each point based on time, error count, or uncertainty.
90
Sensitivity
TABLE 5-4: Mode Control Tab - Data Point Control for AutoBER & AutoPower
Control Field Description

Data Point Step size (dB) If this option is selected, you may specify the dB value
Control the A3308 will increment by along the horizontal axis
during the test. The minimum step size range is 0.01
dB and the maximum step size is 5 dB.
Number of points If this option is selected, you may specify how many
including start & points will be recorded. The minimum number of
finish points that may be specified is three, and the maxi-
mum number specified is 20. The final number of data
points taken in the measurement may deviate from
your request because the algorithm estimates the
range of power and the size of the power step required
for the measurement. This estimate may be somewhat
inaccurate and the actual number of data points taken
may differ from the request; fewer or additional data
points may be taken. The difference is usually within
one or two data points for a typical device.
91
RX Tests
TABLE 5-4: Mode Control Tab - Data Point Control for AutoBER & AutoPower
Control Field Description

Time Control Continue recording at If this option is selected, the A3308 will accumulate
each point until mea- data at each point for either a specified maximum
suring time per point number of seconds or until an auxiliary condition set
is at most ____ sec- by you is met. The auxiliary condition can be statisti-
onds
cal uncertainty or total number of errors observed (see
fields 2 and 3 below).If the auxiliary condition is not
met, the A3308 will continue acquiring data until the
maximum time entered in this field is reached. How-
ever, if the auxiliary condition is met before the maxi-
mum time is reached, data acquisition will cease for
the current point, and the measurement will move to
the next data point (unless this was the last point to be
measured). At times, more data may be taken then
necessary, e.g. when data acquisition occurs for a high
BER point, the error may accumulate faster than the
A3308A’s processor performs its calculation and
decide whether the auxiliary condition is met.
Statistical uncer- The value set in this field is the desired Statistical
tainty is less than Uncertainty for the measurement. If during the
__% of BER allowed time limitation of the test, the A3308 calcu-
lates the statistical uncertainty to be equal to or less
than the value entered, data acquisition will stop and
the A3308 will either move to the next data point, or if
it is the last point to be tested, the test will conclude.
You may enter an uncertainty value between 0.15%
and 100%.
Errors are observed The value set in this field is the desired minimum
number of errors to be observed for each data point
within the allotted time limitation of the test. You may
enter an error count from 1 to 432,000.
Record data at each Timer value in seconds. The A3308 will take data at
point for exactly __ each point until the timer value is reached. This option
seconds is not ordinarily recommended because some time
may be wasted acquiring data at high BER points.
5.1.3.2 IntelliPass™ Mode
In the IntelliPass™ mode, a test is run only until a passing or failing value is reached or the maximum
time to spend on the device is reached. In this mode, a DUT that has great performance will quickly
pass, and a DUT that has very bad performance will quickly fail. Marginal devices will require
additional time.
The options for IntelliPass™ mode include a test for an error floor (to increase the likelihood that a
DUT that causes an initial PASS is in fact acceptable) or a test conducted near the PASS/FAIL
threshold to determine if an initial FAIL can in fact be considered a PASSing device.
If you select the “Perform Post Test (to check for error floor)”, a post test will be conducted on a
DUT. The post test helps to determine if an error floor is present. For example, under normal
92
Sensitivity
IntelliPass™, a DUT can be quickly tested to a BER of 1E-10, with the Pass definition set to 1E-12.
The A3308 will automatically extrapolate from the tested 1E-10 point to the 1E-12 level and will
return a value corresponding to a point on the horizontal axis along with Fit and Confidence Levels.
The error floor test algorithm uses the result of the measurement to establish a power at which no
errors should be observed. The power is set to this value, and the A3308 collects data for an amount
of time computed on the basis of user-specified parameters (see Table 5-5 below). If no errors are
observed, the test passes, otherwise the test FAILS.
The options listed in Table 5-5 enable you to establish the probabilities of falsely failing a device,
falsely passing a device, and choosing where to test for an error floor.
If you select the “Attempt to salvage initial failures” option, an attempt will be made to convert a
DUT from FAIL to PASS if this option is selected. The intent of the salvage feature is to
accommodate devices that substantially deviate from linearity on a standard sensitivity plot by
bending downwards1. You may consider activating this feature if the DUT is expected to exhibit this
behavior due to its design features.
The Salvage Disposition fields allow you to select the final result of the measurement to be displayed
(and logged in the database if the measurement is automated) for various outcomes of the salvage
attempt. Salvage disposition allows for greater flexibility in classification of devices that required the
salvage attempt.
1. bending downwards: exhibits less errors at a particular power than predicted with a linear sensitivity plot.
93
RX Tests
TABLE 5-5: Mode Control Tab - IntelliPass™ Mode
Option Field Description

Perform Post Test Probability of The value entered in this field is the allowable proba-
falsely failing a bility that a device labeled FAIL should have been a
device PASS. The value of this parameter is used by the algo-
rithm to compute the power at which the post-test is
run. False failure would occur due to statistical fluctu-
ations in the receiver. As a rule, set this parameter to a
very small probability value, unless the DUT over-
loads at powers that are very close to the maximum
power reached in the base test.
Probability of The value entered in this field is the allowable proba-
falsely passing a bility that a device labeled PASS should have been a
device FAIL. The value of this parameter influences moder-
ately the time required to run the test. To improve this
probability, the test must be run for a longer duration.
A false pass would occur due to statistical fluctuations
in the measurement.
Error floor level to The BER value entered in this field determines the
reject level of error floor that the A3308 will attempt
exclude, consistent with the remaining two parame-
ters. The value of this parameter influences strongly
the time required for the test (is inversely proportional
to the change in the error floor level).
This error floor The amount of time to test for an error floor is dis-
rejection will take played. This value is not directly set by you, it is
___ secs. Reduce derived from the 3 previous fields.
the time by increas-
ing the error floor or
increasing the prob-
ability of falsely
passing a device
94
Sensitivity
TABLE 5-5: Mode Control Tab - IntelliPass™ Mode

Attempt to sal- Salvage pass/fail You enter the desired confidence level for the salvage
vage initial fail- confidence level attempt in this field.
ures NOTE: Lower confidence level yields faster test com-
pletion.
This note on the screen derives from the relationship
between test time and confidence levels. The more
time spent testing, the higher the confidence level in
the result and conversely, the less time spent testing,
the lower the confidence level in the result.
Salvage fail disposi- You may choose to classify a Salvage failure as either
tion UNKNOWN or FAIL.
Salvage unresolved You may choose to classify an unresolved salvage test
disposition as either UNKNOWN or FAIL.
Salvage pass dispo- You may choose to classify a Salvage pass as either
sition UNKNOWN or PASS.
5.1.3.3 IntelliTime™ Mode
There are no additional options beyond the parameters set in the Basic tab for the IntelliTime™
mode. In this mode you enter the time allotted for the test. The A3308 then uses its own algorithms to
provide the lowest possible measurement uncertainty using the allotted time. Algorithms determine
the amount of time spent taking data at each input level.
5.1.3.4 All Modes

All Modes refers to AutoBER, AutoPower, IntelliPass™, and IntelliTime™ modes.
If you select the Pause time for device stabilization (seconds) option, the pause time is enabled. The
data acquisition for each point is delayed by the number of seconds entered by you in this field. The
delay begins from when the power level for a data point is set. This feature may be useful for DUTs
that include a circuit that adjusts some of the DUT’s behavior based on an input power level or error
rate. The Pause time for device stabilization gives the circuit time to complete the adjustments for a
given power level prior to the beginning of a measurement.
NOTE: The Pause time applies only to the final measurement, but NOT to the FastScan. If the
use of Pause time is required, you are advised to select “Execute Binary Search” on the
FastScan Control tab.
95
RX Tests
5.1.4 FastScan Control Tab
You may select default values for FastScan Control or may customize the settings. FastScan applies
only to AutoBER, IntelliTime™, and IntelliPass™. AutoPower mode does not use FastScan. The
purpose of running a fast scan is to establish where the BER range of interest lies with respect to the
input conditions.
FIGURE 5-7: Sensitivity FastScan Control
All FastScan tests are executed from high power to low power. Once the algorithm has determined
the input condition range associated with the BER level that must be tested, testing proceeds.
FastScan may, for example, identify that the BER range of 1E-5 to 1E-12 corresponds approximately
to an optical power range of -18 dBm to -14 dBm for a DUT. Testing begins at the Start BER input
condition.
The FastScan procedure contains three distinct algorithms which are arranged into a “waterfall”
model in the following order (left to right on the A3308 screen)
• Fine Scan
• Coarse Scan
• Step Scan
If the first algorithm in the sequence fails, the A3308 automatically proceeds to the next algorithm. If
the next algorithm is not enabled (box not checked), the A3308 skips this algorithm and proceeds to
96
Sensitivity
the next algorithm in sequence. Any algorithm that succeeds terminates the FastScan sequence. If
none of the algorithms succeed, the FastScan fails and the measurement is terminated.
If you select the Reset to Defaults button, the factory default conditions for FastScan Control
overwrites values entered by you.
When you select the Execute binary search radio button, a binary search algorithm will be used in
lieu of the FastScan test to locate the region of test based on the default slope. The algorithm looks for
errors at the expected sensitivity value entered by you. If no errors are present, the algorithm looks for
errors at the highest power and then the lowest power. If no errors are found, or an out of frame
condition is detected, the algorithm will begin subdividing the range between high and low power in
an effort to locate a region where some errors are detected. The Default slope value you enter will be
used with the binary search algorithm. Once the first point within the sensitivity range is found, the
default slope will be used to calculate the power range for the measurement. FastScan is enabled and
disabled with the Execute FastScan radio button.
Once FastScan has located the correct input power range associated with the BER level that must be
tested, no further FastScans will be conducted. In general, a FastScan algorithm succeeds if it
establishes a viable fit to data within a scanned range. Individual algorithms use different strategies
towards the same goal of establishing a viable fit to data. By selecting individual algorithms you can
create your own FastScan strategies, customized for the properties of a particular Device Under Test.
The value entered in the Approximate expected sensitivity (Pavg or OMA) dBm field will become
a focal point for the first FastScan test. Performing a FastScan near the actual sensitivity point of the
DUT saves time since additional FastScan operations may not have to be performed if the first
attempt to locate the BER region of interest is successful. It is not essential that you enter a value that
is close to sensitivity of the DUT, but it will decrease the time the test takes. The FastScan algorithm
will expand the region to be tested automatically.
Override the factory defaults by selecting the Override Slope box. The slope refers to the Straight-
Line BER™ that is superimposed over the plot. The Maximum slope to fit value refers to how steep
the Straight-Line BER™ plot is considered acceptable, whereas the Minimum slope to fit value
refers to how shallow the Straight-Line BER™ is considered acceptable.
97
RX Tests
5.1.4.1 Fine Scan

If this option is selected, FastScan will begin with a fine scan around the Approximate Expected
Sensitivity value.
NOTE: Using fine scan is particularly useful when all DUTs are expected to fall into a fairly
narrow range of sensitivity. This is because time is saved by beginning with the
approximate sensitivity range immediately rather than measuring over a wide range
and then narrowing the range down to determine the proper starting conditions
associated with the start BER value.
TABLE 5-6: Sensitivity FastScan Control: Fine Scan

Override default The factory defaults may be overridden by selecting
values for fine this box
scan Fine scan range The Fine scan range defines how narrow or wide a
(dBm) range will be tested around the Approximate Sensitiv-
ity Value.
Fine scan step The Fine scan step size defines the initial interval
(dBm) between data points.
Fine scan range pad The Fine scan range pad defines how much farther
(for extending sub- additional fine scan tests will be run if necessary.
sequent scans) Additional Fine scans are run if the initial fine scan
(dBm) does not determine an adequate fit but does reveal at
least one data point in frame at the edge of the scan
range. The scan will be repeated, with the power range
extended on the side of the range that is in frame, by
the pad value entered in this field.
Use last mea- When this option is selected, the last test result is used
sured data to set the Fine scan range.
NOTE: Using the last measured data will speed up testing if a set of DUTs are all expected to
have approximately the same performance.
98
Sensitivity
5.1.4.2 Coarse Scan

The default test range for coarse scan begins at 1 dB lower than the maximum optical power set from
the TX/RX bar. The default value for the lowest power of the coarse scan is -30 dBm.
If a Coarse Scan encounters a region with a very steep transition between high errors and no errors,
the Coarse Scan will be repeated in a region around the transition, unless the Quick abort function is
enabled. If Coarse Scan is not able to plot a slope, the algorithm will fail. The failure will be reported
and the test aborted unless the “Step Scan” feature is selected. In that case a Step Scan will be
conducted on the DUT.
TABLE 5-7: Sensitivity FastScan Control: Coarse Scan

Override default When selected, the default Coarse scan values will be
range values for replaced by the following user selected conditions.
coarse scan. Higher power for You may find it will save Coarse Scan test time by
initial coarse scan reducing the Higher power limit to a value closer to
(dBm). the expected bottom of the nearly error free region of
the DUT.
Lower power for You may find it will save Coarse Scan test time by
initial coarse scan increasing the lower power limit closer to a DUT’s
(dBm). operational limit. For example for an APD receiver,
the lower power can be reduced to -30 dBm.
Power step in The value entered in this field sets the granularity of
coarse scan (dBm). measurements for the Coarse scan.
Quick abort The Quick abort prevents Coarse Scan from running
twice when a region with a very steep transition
between high errors and no errors is detected over a
range defined in the Step Range field. This function
saves some testing time by performing one scan
instead of two scans before proceeding to the Step
Scan where an ultra-fine scan is performed around the
region where the steep transition occurred.
Step Range (dBm) You define the range over which there may be a tran-
sition between many errors and no errors. If such a
transition occurs within this range, FastScan will
either fail (if Step Scan is not enabled) or the DUT
will be tested by the Step Scan algorithm.
99
RX Tests
5.1.4.3 Step Scan

If this option is selected, the Step Scan algorithm is enabled. This algorithm analyzes steep transitions
between many errors and no errors in an attempt to locate the defined test region. It also allows you to
enable a systematic scan over specific range of input power. The Step Scan succeeds if one of the
two outcomes is achieved:
• A viable fit is obtained. The slope of this fit is bound by the upper slope limit, but it is not bound
by the lower slope limit, as this algorithm expects a very steep step transition.
• A step transition is seen within the region of ultra-fine scan, even if the fit was not established due
to an insufficient number of data points with errors. The A3308 will compute the sensitivity based
on the width of the step, and warn you via the Status window that the result quoted is based solely
on the edge (step) detection. In this condition, the plot will show the step transition with no fit
overlaid.
TABLE 5-8: Sensitivity FastScan Control: Step Scan

Ultra-fine step The value in this field defines how close together the
(dBm) scanned points are over the region located during the
Step Scan.
Override default If this option is selected the default Step Scan values
range values for will be replaced by the following user selected condi-
coarse scan tions.
Higher power for The upper power level for a step scan.
initial step scan
(dBm)
Lower power for The lower power level for a step scan.
initial step scan
(dBm)
Power step scan The interval for scan points. Testing begins at the high
(dBm) power level and decrements by this value until the
Lower power for initial step scan is reached.
100
Sensitivity
5.1.5 Fit, Uncertainty, and Pass Criteria Tab
FIGURE 5-8: Sensitivity Fit, Uncertainty, and Pass Criteria
5.1.5.1 Fit
Fit relates to the Straight-Line BER™ plotted over the accumulated data points. The Fit Quality
metric captures how well the Straight-Line BER™ matches the data points. The Fit Quality is defined
by you in the Pass Criteria section of the Fit, Uncertainty, Pass Criteria tab.
You may select the highest BER data point (Maximum BER to be used in fitting algorithm for
each error type) used in calculations to superimpose the Straight-Line BER™ over the data points.
You may find it helpful to set the BER fit threshold at a low value to avoid using data points where
receivers may exhibit non-Gaussian behavior. Keeping the threshold low enough improves the
accuracy of the calculated sensitivity value.
After you select the Error Source in the Basic tab, you may then set its Fit Threshold. The value you
enter in the Fit Threshold box represents the maximum BER value that will be included in Fit
calculations. While data may be taken above this threshold (poorer BERs), those data points will not
be included in the calculations to determine the fit to the Straight-Line BERTM.
101
RX Tests
5.1.5.2 Uncertainty
You have the option to utilize a variety of statistical methodologies to calculate test results.
Confidence level for individual error bars. Each data point has an error associated with it. The
larger the percentage value entered, the larger the error bar will be. You may observe the error bars
shrinking as more data is collected. The default value is one Sigma. This means that if the test were
repeated again and again, 68.3% of all measurements taken would have the data point within the
range specified by the uncertainty. The A3308 utilizes Poisson statistics to determine the size of the
error bars. For reference, a list of Confidence Levels corresponding to the first few multiples of
standard deviation is listed below:
• 1 Sigma = 68.27%
• 2 Sigma = 95.45%
• 3 Sigma = 99.73%
• 4 Sigma = 99.99366%
• 5 Sigma = 99.99994%
Confidence level for final result. The value entered in this field is the confidence level used to
calculate the uncertainty value. The closer this level is to 100 percent, the larger the uncertainty on the
result (in dB) will be. Error rates are statistical by nature. Because a test can be repeated several times
with each run yielding a different result, one must look beyond a single calculated answer and include
a statement relating to the probability that the answer shown would be likely to occur if the test was
repeated. In a sensitivity test for example, the uncertainty would be shown as a plus/minus dB value
such as a sensitivity of -10 dBm with an uncertainty of +/- 0.22 dB at a 95.45% confidence level.
Uncertainty calculation for final result. You have the option to select which algorithm is used to
calculate uncertainty.
• Statistical. By default, the A3308 utilizes the statistical process to calculate uncertainty. The well-
known maximum likelihood fit methodology is utilized to establish the range of uncertainty
around the intersection of the Straight-Line BER™ fit with the BER level set by you. Typically,
the statistical process will produce the smallest uncertainty value. However, DUTs with
pathological behavior such as an error floor, may not have a well represented uncertainty value
because the data points with a large amount of statistics will dominate the fit and the uncertainty.
Yet, the data points with low error rates are typically of highest interest. DUTs with error floors
may pass a sensitivity and Uncertainty test but fail for Fit Quality.
• Systematic. The systematic process of calculating uncertainty is based on determining the
stability of the Straight-Line BER™ fit. The error is determined by comparing multiple fits, each
based on a subset of the data points. The largest difference between the fit result based on the full
data set and of the fit results based on the subset of data is reported as the uncertainty value.
Each fit weighs data points according to their statistical error. The subsets include a minimum of
three data points and do not include data points above the threshold level set by you. Straight-Line
BER™ plots are made starting with the three data points associated with the lowest BER and the
intersection point with the defined BER level is determined. A series of subsequent Straight-Line
BER™ plots are made by adding one additional data point at a time. In each case the excursion
from the Straight-Line BER™ plot displayed is calculated. This process is repeated starting with
the three data points associated with the highest BER level. The largest difference between
intersection points is the maximum excursion and is reported as the uncertainty value. You may
find this method to be useful in identifying the effects of an error floor. The systematic process
102
Sensitivity
typically produces the largest Uncertainty of the three methods utilized on the A3308: systematic,
statistical/systematic, and statistical.
• Statistical/Systematic. The statistical/systematic process is the same as the systematic process
with one major difference; fits to data points are weighted for statistical significance when
determining the maximum excursion. You may notice that on the results screen the uncertainty is
constantly updated. However in the statistical/systematic process, the uncertainty displayed does
not include the weighting factors while the test is running. The weighting factors are only
calculated at the conclusion of the test due to their computationally intensive nature.
5.1.5.3 Fit Algorithm Control
You have the option of utilizing a variety of statistical methodologies to calculate the fit of the
Straight-Line BER™ to the set of data points. The main purpose of the Fit Quality metric is to
establish a PASS/FAIL criteria for data points on a Straight-Line BER™ plot. An ideally performing
DUT exhibits linear performance; all of the data points appear on a straight line and the line fit to the
points goes through all the points. Data points that appear to curve could be indicative of an
undesirable error floor. While poorly performing DUTs may be apparent to a trained engineer, in a
manufacturing environment, volume production demands simple PASS/FAIL criteria. The Fit
Quality metric is designed to quantify the degree of non-linearity a DUT is allowed to have and still
be considered a PASS.
Each statistical methodology has its own advantages and disadvantages. There is no perfect
methodology. Depending on the statistical technique chosen, the line through the data points is
drawn differently.
Note: While a test is being run, an intermediate line fit to the data points appears on the
screen and a projected numerical result is displayed of the expected sensitivity at the
defined BER value. The regression technique, without weighting and without including
the statistical uncertainties of the data, is used to draw the fit through the points and to
calculate the displayed intermediate results. The regression technique is used because it
is a computationally rapid technique - useful for rapid-fire updates to the screen as data
is obtained. However, at the conclusion of a test, the final result is shown using the
statistical methodologies you selected.
Max likelihood. When you select this statistical technique to establish the fit of the Straight-Line
BER™ plot to the data points, you employ the well-known statistical technique of maximum
likelihood fit.
Regression. When you select this statistical technique to establish the fit of the Straight-Line BER™
plot to the data points, a standard linear regression formula is used. The regression result method does
not make optimal use of the acquired information; per-point statistical uncertainties are not included
in the calculations and a weighting factor may or may not be enabled and set by you to help derive
slope and intercept. DUTs with linear performance plot nearly the same way if you use maximum
likelihood or the regression method; however, DUTs with curved performance plot differently.
Tangent. When you select this statistical technique to establish the fit of the Straight-Line BER™
plot to the data points, only the N points closest to the BER definition are used in calculating the fit.
The maximum likelihood statistical technique is then used for that subset. By default N is 4. For the
typical curved case this is more pessimistic (and more realistic) than either maximum likelihood or
regression. However, since it does not use all the information it will provide a less precise result for
the straight-line case.
103
RX Tests
Use weights. To activate weighting, select this box. Weighting results in more emphasis on points
closer to the BER definition, at the expense of discarding information from points far away from the
BER definition.
Expo. coefficient: A larger weighting factor results in more emphasis on points closer to
the BER definition, at the expense of discarding information from points far away from the
BER definition.
Tangent points: The value in this field sets the number of points closest to the BER
definition that are used to calculate the fit line when the Tangent Fit Algorithm Control
technique is selected.
5.1.5.4 Pass Criteria

For a DUT to pass a sensitivity test when Uncertainty and Fit Quality metrics are enabled, all of the
following three conditions must be met: Sensitivity, Uncertainty, and Fit Quality. If even one of the
three conditions fails, the DUT will fail. By selecting Status on the results screen, you may determine
why the A3308 reported a fail result.
Sensitivity. The worst-case sensitivity that you will accept is entered in this field. If the sensitivity is
equal to or better than this value, the DUT will pass this criterion. Sensitivity associates a BER with
an input power level. The point at which the Straight-Line BER™ intersects the BER level defined by
you is the reported sensitivity. The error range around the reported sensitivity value is calculated with
statistical, statistical/systematic or systematic methodology:
• Uncertainty (dB). The Uncertainty that you will accept is entered in this field. If the Uncertainty
is equal to or better than this value, the DUT will pass this criteria. The required Uncertainty in
this field is compared with the Uncertainty calculated with the statistical, systematic, or
statistical/systematic process described above. By default, the A3308 utilizes the statistical
process.
• Fit Quality. The Fit Quality is a measure of how well the line drawn through the data points
matches up to the data points. You may enable/disable Fit Quality as a Pass Criteria. If enabled,
the DUT must pass the sensitivity definition AND Fit Quality. If Uncertainty is also enabled as a
Pass Criteria, a DUT must meet all three Pass Criteria to receive an overall PASS. The value you
will accept is entered in either the Raw Metric or Confidence Level field. If the Fit Quality is
equal to or better than the selected Raw Metric or Confidence Level cut value, the DUT will pass
this criterion. The statistical methodology used to determine the Fit Quality is chosen in the Fit
Quality Control section of the GUI. You may cut on the Raw Metric calculated result or cut on the
computed Confidence Level of the Raw Metric. Selecting either Raw Metric or Confidence Level
in the Pass Criteria section of the GUI also automatically changes the selection in the Fit Quality
Control section.
• Raw Metric. The Raw Metric is the numerical result of the Fit Quality Control calculation. Each
Fit Quality Control method produces a different result; you will have to determine acceptable
ranges for the Raw Metric Pass Criteria for each Fit Quality Control method you use. For this
reason, you may prefer to use the Confidence Level rather than the Raw Metric because the
Confidence Level has uniform meaning independent of the method used to compute the fit
quality. The larger the number you enter in the Raw Metric Pass Criteria field indicates an
acceptance of larger deviations. In general, 1 is considered ideal performance.
• Confidence. The Confidence Level is the fraction of the distribution of the Raw Metric that is
worse than the measured value for a set of linear devices. With statistical fluctuations only, 100%
is the best confidence level and 0% is the worst confidence level. The interpretation of the
confidence level is the same for any of the Fit Quality Control methodologies. A typical setting for
104
Sensitivity
the Confidence field is 68.27%; corresponding to 1 Sigma. See Section 5.1.5.2 Uncertainty for a
reference list of standard deviation values.
NOTE: You may define the sensitivity to be a lower BER than is actually tested e.g. data may
be taken between 1E-5 and 1E-12 but the sensitivity value may be set at 1E-14. This
ability to extrapolate sensitivity is a powerful feature of the A3308.
5.1.5.5 Fit Quality Control

You have the option to utilize a variety of statistical methodologies to calculate how well the line fits
the data points.
Runs test. The runs test is a non-parametric measure that simply counts “runs” of points where a run
is a group of consecutive measured points on the same side (above or below) the fitted line. The runs
test is an extremely robust and model-independent metric, but requires many data points to
differentiate a good fit from a bad fit. For small point sets (<10) it will forgive quite bad fits. For large
point sets it will declare as bad a non-linear plot - even if the absolute deviations from linearity are
visually small.
x-Residual RMS. The x-residual RMS is the Root-Mean-Square of absolute deviations of the data
points from the fitted line. You may observe that this methodology is perhaps the closest to measuring
the deviation as perceived by the eye. However, there is no absolute scale to the RMS, so you must
provide a normalization coefficient in the box labeled “Norm. Coeff.”
Norm Coeff. The normalization coefficient value you enter here is only used with the x-
Residual RMS Fit Quality Control method. The coefficient normalizes the data. Large
values allow loose fits; small values require tight fits for a DUT to PASS the Fit Quality Pass
Criteria.
χ 2. The chi-squared Fit Quality Control method is the simplest method and is the most common
measure of fit quality in standard statistics. If you take N points, the (normalized) chi-squared is the
mean of squares of (i'th measured value – fit value at i)/(uncertainty on i'th value) over the N points.
For a linear fit, the chi-squared tends to be close to 1; low values mean the fit is close to the points and
high values mean the fit is far away from the points. Note that chi-squared works best for small
sensitivity ranges (e.g. BER1e-8 to 1e-11). Over larger ranges, most DUTs deviate significantly from
linearity even if they look linear to your eye. The default Fit Quality Control method is the Truncated
chi-squared method that selects a small set of points near the BER definition and uses them to
calculate the chi-squared fit.
Truncated χ 2. The truncated chi-squared Fit Quality Control method is a variant of the chi-squared
method. Only a limited number of points near the BER definition are used to determine the quality of
the fit of the line to the data points. This method is well-suited to use in sensitivity measurements
where non-linearities over wide ranges may make traditional chi-squared based measurements a poor
measure of fit.
Points. The point value you enter here is only used with the truncated chi-squared Fit
Quality Control method and sets the number of points closest to the BER definition that are
used to calculate the quality of the fit using a chi-squared technique. Data points that are not
included in the truncated chi-squared calculation have no bearing on the Fit Quality Control
Pass Criteria.
105
RX Tests
Report On. For all of the Fit Quality Control methods, you may use either the raw metric or the
confidence level for that value. Selecting either Raw Metric or Confidence Level in the Fit Quality
Control section of the GUI also automatically changes the selection in the Pass Criteria section and
vice versa.
Raw Metric. The raw metric is the numerical result of the Fit Quality Control calculation. Each Fit
Quality Control method produces a different result; you will have to determine acceptable ranges for
the Raw Metric Pass Criteria for each Fit Quality Control method you use.
Confidence Level. The confidence level for any raw metric is the fraction of the distribution of the
metric that is worse than the measured value for a set of linear devices - with statistical fluctuations
only. 100% is the best confidence level; 0% is the worst confidence level; and for a group of perfectly
linear devices the CL is uniformly distributed between 0% and 100%. The interpretation of the
confidence level is the same for any of the Fit Quality Control methodologies.
5.1.5.6 Selected Action(s) on Test Failure.

The A3308 will only pass a DUT if the Sensitivity, Uncertainty, and Fit Quality all pass. Should any
of these criteria not be met, the DUT will fail. You have the option to send an e-mail or to sound an
audible alarm upon failure:
• E-mail. If this option is selected, whenever a test fails, all e-mail addresses selected will receive
notification of the failure.
• Modify Recipients. By selecting this field you may add or remove E-mail addresses from the
notification on failure list.
• Audible Alarm. If this option is selected, whenever a test fails the A3308 will produce an alarm
for a short period of time.
• Intelligent FaultFinder™. This feature will be enabled on a future software release and may not
be selected by you at this time.
106
Sensitivity
5.1.6 Summary
FIGURE 5-9: Sensitivity Test Parameter Summary
Displays all parameter values set for the test.
107
RX Tests
FIGURE 5-10: Sensitivity Measurement Results
5.2 Overload
You may automatically measure the optical input power at which a receiver overloads
and generates errors. If the overload value is greater than the maximum safe output of
the A3308 (as defined by you) the overload will be reported as greater than (max output) value. The
test will abort if the error rate is > 10-6.
108
Overload
FIGURE 5-11: Overload Setup
TABLE 5-9: Overload Setup
Feature Field Description

Device Type Identifying the correct type of detector, APD or
PIN, is not required because this input is no
longer utilized in the overload measurement
algorithm. Future software releases will elimi-
nate this option.
Approximate Overload When available, you may specify the approxi-
mate overload of the DUT in this field. It is not
required.
109
RX Tests
TABLE 5-9: Overload Setup
Feature Field Description

Overload BER
Definition
Auto In this option, a BER vs. Power plot is generated
using the Upper Power and Lower Power values
as boundaries of the range. Data is taken at each
point until either the desired uncertainty is met,
or the maximum amount of time allotted to
spend on a point expires. Intervals between mea-
surements are determined by you defined step
size or a total number of desired measurement
points. FastScan measurements are not made in
Overload mode because the test range is pre-
defined by you.
Upper Power (dBm) The maximum optical power level the DUT will
be tested to is entered in this field. Testing
begins at high power and ends at the lower
power level.
Lower Power (dBm) The minimum optical power level the DUT will
be tested to is entered in this field. The last data
point measured is the lower power limit.
Desired Uncertainty per The value entered in this field is the desired
Point minimum statistical uncertainty of the measure-
ment for each data point measured. This value is
reached only if enough time is allotted. If the
Max Time per Point is reached prior to the
Desired Uncertainty per Point, the A3308 will
move to the next measurement point, or if that
point is the last measurement point, the test will
conclude.
Max Time per Point The value entered in this field is the maximum
amount of time spent on each measurement
point. This value is reached only if the Desired
Uncertainty per Point has not been met. If the
Desired Uncertainty per Point is reached prior to
the expiration of allotted test time, the A3308
will move to the next measurement point, or if
that point is the last measurement point, the test
will conclude.
Step size (dB) The value entered in this field determines the
interval between data point measurements.
Points The value entered in this field sets the number of
data points taken in the Overload measurement.
NOTE: The Overload application does not include the Basic, Initialization, Mode Control,
FastScan Control, and Fit, Uncertainty, Pass Criteria tabs found in other RX tests.
110
BER vs. OSNR
FIGURE 5-12: Overload Measurement Results
5.3 BER vs. OSNR

To measure the effects of Optical Signal to Noise Ratio (OSNR) on a DUT, you select
the BER vs. OSNR icon under RX Tests to bring up a series of options.
The A3308 generates a signal with calibrated OSNR levels at a specified optical power level. The
A3308 creates a plot showing the BER over a range of OSNR levels. BER vs. OSNR quantifies the
performance of the optical signal recovery of a DUT in the presence of optical noise. The A3308
monitors BER while the built-in Erbium Doped Fiber Amplifier (EDFA) increases or decreases noise
to step through the range of OSNR levels.
NOTE: If you choose a signal configuration with an ER set to run BER vs. OSNR, then the ER
will not be kept constant throughout the test. The result will in fact be dependent on the
starting values of OSNR, VECP, and ER on the Optical Degradation page.
111
RX Tests
FIGURE 5-13: BER vs. OSNR Setup
• Auto OSNR. This setting is similar to the AutoPower feature in a Sensitivity plot. In Auto OSNR
test mode, a BER vs. OSNR plot is automatically generated with you selecting the OSNR range to
be tested. BER is displayed on the vertical axis and OSNR on the horizontal axis. Testing begins
at the start OSNR level and concludes at the finish OSNR level. You may test from low OSNR to
high OSNR or from high OSNR to low OSNR.
• Start OSNR (dB). The Start OSNR value that is entered into this box is where the A3308 begins
to make measurements. The start OSNR value may be either a high OSNR or a low OSNR. This
provides you with the option of beginning to make BER measurements at the either the higher
OSNR level or at lower OSNR level.
• Finish OSNR (dB). The Finish Power value that is entered into this box is the last OSNR level at
which BER measurements are made.
• Transmission (TX) Power (dBm). The value entered in this field sets the power coming out of
the A3308’s TRANSMIT TO DUT port. The value must be in the range of -45 dBm to 10 dBm.
NOTE: Jitter pretest and FastScan are not supported.
112
IsoBER
FIGURE 5-14: BER vs. OSNR Measurement Results
5.4 IsoBER
To plot the various combinations of optical power and OSNR that produce the same
BER, you select the IsoBER icon under RX Tests to bring up a series of options.
The 10 Gb/s OST System automatically measures BER vs. OSNR at fixed optical power levels and
then plots the user-defined BER value associated with that combination of OSNR and optical power.
You may define a mask and if any of the plotted points fall in the masked area, the DUT is classified
as FAIL. If all points do not touch the mask, the DUT is classified as a PASS. This test is helpful in
determining the operating range of long-haul telecommunication systems; from high optical power
with excellent OSNR to low optical power with poor OSNR and points in-between.
NOTE: If you choose a signal configuration with an ER set to run BER vs. OSNR, then the ER
will not be kept constant throughout the test. The result will in fact be dependent on the
starting values of OSNR, VECP, and ER on the Optical Degradation page.
113
RX Tests
FIGURE 5-15: IsoBER Setup
NOTE: Jitter pretest and FastScan are not supported.
114
IsoBER
FIGURE 5-16: IsoBER Measurement Results
115
RX Tests
116
CHAPTER 6 TX Tests
6.1 Path Penalty (Dispersion Penalty)

All tests performed by the A3308 10 Gb/s Optical Standards Tester include user
controlled setup options. Many of these options are repeated between tests. Detailed
descriptions of the common functions are provided in the Sensitivity section of the User’s Manual.
Options and features unique to S/X Measurement, Overload, BER vs OSNR, Path Penalty, IsoBER
and Optical Power are covered in the sections of the User’s Manual specific to those tests.
The Path Penalty test allows you to check the quality of a DUT’s transmitter by measuring the
difference in optical power needed to reach a given BER between a short length of fiber and a long
length of fiber. Typically, more optical power is needed on a RX after passing through a long length
of fiber to reach satisfactory BERs. Chromatic dispersion, reflections, scattering, components and
other degradations contribute to an overall penalty of a signal passing through a network. In some
cases a transmitter may have either positive or negative chirp aimed at optimizing its performance in
a particular network. This can result in an improvement in performance between the short and long
paths.
Path Penalty is the difference between the short path and the long path sensitivity at the Path Penalty
BER definition level and is measured in dB.
The A3308 does not include a long length of fiber. Instead, the A3308 has a Path In and a Path Out
connector to include a user supplied spool of fiber and any other network components such as
EDFAs, Dispersion Compensation Fiber, optical switches, or patch panels in the long path. The
A3308 first makes a sensitivity measurement going through the short path. Then an internal optical
switch in the A3308 is automatically activated to include the fiber and components attached to the
Path In and Path Out connectors. Another sensitivity measurement is made and the difference in dB
between the BER of the long and short path is calculated and displayed as the measurement result.
A common implementation for measuring Path Penalty is for the A3308 to output a signal pattern to a
DUT’s RX. The optical power level of the signal is held constant. This signal is looped-back to the
DUT’s TX. It is the DUT’s TX that is being measured.
If you wish to measure the performance of the DUT’s TX with a reference RX from the same product
family, the A3308 switch setup is configured with the External RX ports activated. The OUT TO REF
117
TX Tests
RX carries the signal traversing both the long (from PATH IN) and the short (RECEIVE FROM
DUT) paths. The IN FROM REF RX port on the A3308 receives the high-powered, loop-backed
signal coming from a TX that re-transmits what the reference RX receives. Refer to Section 3.4
Switch Setup for details on Switch Setup.
FIGURE 6-1: Path Penalty Setup
118
Path Penalty (Dispersion Penalty)
TABLE 6-1: Path Penalty AutoPower Test Setup

Auto Pwr Start Pwr Short: In the Path Penalty AutoPower test mode, a BER vs.
Long: (dBm) power plot is automatically generated with you select-
ing two optical power ranges to be tested. The short
range refers to the link without additional fiber added,
Finish Pwr Short: and the long range refers to the link with a spool of
Long: (dBm) fiber added. BER is displayed on the vertical axis and
power on the horizontal axis. Testing begins at the
start power and concludes at the finish power. Users
may test from low power to high power or from high
power to low power.
Transmission (TX) The value entered in this field sets the power coming
Power (dBm) out of the A3308’s TRANSMIT TO DUT port. In a
Path Penalty test, this power is held constant. The
optical power level entered in this field has priority
over the Requested Power into DUT value set by you
in the TX Power Setup. However, the Maximum
Power Out set by you in the TX Power Setup may not
be exceeded. A window will open and advise you if
the Path Penalty Transmission (TX) Power level is set
above the Maximum Power Out value. You may either
lower the Path Penalty Transmission (TX) Power to a
level equal to or less than the overall maximum optical
power set by you in the TX Setup window (accessed
by pressing the Actual Power button located on the
TX/RX bar) or raise the Maximum Power Out in the
TX Setup window.
Path Penalty Defini- The value entered in this field sets the vertical axis
tion (BER) measurement level at which to calculate the differ-
ence, in dB, between the short and long StraightLine
BERTM measurements.
Step 3 Define Penalty ≤ (dB) The value entered in this field defines the pass crite-
Pass Criteria rion of how great the difference may be for determin-
ing if a DUT passes or fails. If enabled, the other
criteria that must be passed for the DUT to have an
overall Pass include Uncertainty and Fit. If just one of
these three pass/fail criteria is not met, the DUT will
Fail the test.
Fit, Uncertainty, X Fit Quality Fit Quality may be set at different values for the short
Pass Criteria ≥ Short% Long% and long paths.
119
TX Tests
FIGURE 6-2: Path Penalty Results Screen
Two StraightLine BERTM plots appear on a Path Penalty Results screen; short path and long path.
Each plot has its sensitivity, slope and fit displayed. The difference between the two sensitivity plots
is displayed under the column labeled Penalty Uncertainty (dB). The Path Penalty is the top value.
The uncertainty, in dB, of the Path Penalty measurement is shown below the Path Penalty value.
The short path is indicated by a solid circle and its data is displayed in the Path Penalty Results field
on top of the Long path data. In some cases the Long path may have a negative penalty indicating that
the performance was better through the spool of the fiber than just through the short length of the
fiber. This may occur for example, if a transmitter has a negative chirp designed into it.
120
Internal Sensitivity
6.2 Internal Sensitivity

The Internal Sensitivity test is essentially the same as the first part of a Path Penalty test
whereby receiver sensitivity is measured with only a short length of fiber between the
TX DUT and the OST. The Internal Sensitivity test allows you to use the OST’s internal receiver as a
reference receiver when measuring the performance of a TX DUT. This provides a way to measure
the performance differences among a set of transmitters and between transmitter types.
FIGURE 6-3: Internal Sensitivity Basic Configuration
121
TX Tests
6.3 DUT TX Power

You may automatically measure the optical output power of a transmitter and compare
the result to the allowable range of values. If the power level is within the specified range, the DUT is
a Pass. If the power level is outside the specified range, either too high or too low, the DUT is a Fail.
FIGURE 6-4: TX Power Setup
122
DUT TX Power
TABLE 6-2: TX Power Setup
Field Description
Units You may select to specify optical power in dBm or in mW by
choosing the appropriate radio button. The units displayed in the
Transmission (TX) Power, Minimum Power and Maximum
power will toggle between dBm and mW following your selec-
tion. The A3308 automatically converts entered values between
dBm and mW.
Transmission (TX) Power The value entered in this field sets the power coming out of the
(dBm) out of the A3308’s TRANSMIT TO DUT port. In a DUT TX
Power test, this power is held constant.
The optical power level entered in this field has priority over the
Requested Power into DUT value set by you in the TX Power
Setup. However, the Maximum Power Out set by you in the TX
Power Setup may not be exceeded. A window will open and
advise you if the OST Output Power level is set above the Maxi-
mum Power Out value. You may either lower the OST Output
Power to a level equal to or less than the overall maximum optical
power set by you in the TX Setup window (accessed by pressing
the Actual Power button located on the TX/RX bar) or raise the
Maximum Power Out in the TX Setup window.
Minimum Power (dBm) The lowest acceptable optical power is entered in this field.
Maximum Power (dBm) The highest acceptable optical power is entered in this field.
123
TX Tests
FIGURE 6-5: TX Power Results Screen
Power (dBm). The optical power of the DUT is displayed under the Power (dBm) column.
Status. The Pass/Fail result is displayed under the Status column. If the power level is within the
specified range, the DUT is a PASS. If the power level is outside the specified range, either too high
or too low, the DUT will FAIL.
NOTE: No plot is generated for this test.
124
CHAPTER 7 SONET/SDH Tests
In order to perform any of the following tests you must have already selected and configured the
desired type of traffic. You may also verify that the A3308 10 Gb/s Optical Standards Tester is
operating error free by placing it in loopback mode and comparing the data transmitted by the A3308
to that received by the A3308. Once error-free operation is verified, your DUT should be hooked up
normally to the A3308 and testing may begin.
7.1 Transmit Features

To collect statistics on SONET/SDH traffic, the OST must be generating SONET/SDH traffic. See
Section 3.1 Traffic Configuration for traffic setup instructions and options.
125
SONET/SDH Tests
FIGURE 7-1: Overhead and Path Setup
126
Transmit Features
FIGURE 7-2: Payload Setup
NOTE: The GUI is context sensitive. Not all setup options are available in all cases.
127
SONET/SDH Tests
Anomaly Measurement. Table 7-1 shows the error conditions which may be measured for
SONET/SDH applications.
TABLE 7-1: Error & Anomaly Measurements

SONET ES Errored Seconds
SES Severely Errored Seconds
UAS Unavailable Seconds
CSES Consecutive Severely Errored Seconds
M1 Remote Error Indicator-Line
B1 Errors Section BIP Errors
B2 Errors Line BIP Errors
B3 Errors Path BIP Errors
Corr B1 Error Corrected B1 Errors
SDH BBE Bad Block Error
ES Errored Seconds
SES Severely Errored Seconds
UAS Unavailable Seconds
B1 Errors Regenerator Section BIP 8
B2 Errors Multiplexer Section BIP 24
B3 Errors Path BIP Errors
M1 Errors MS Remote Error Indicator
128
SONET/SDH BERT Bar Monitoring
7.2 SONET/SDH BERT Bar Monitoring
FIGURE 7-3: BERT Bar Monitor Choices
You may monitor parameters on an on-going basis by setting up the BERT Bar to display 3
parameters of interest. Press anywhere over the area to the right of the green Start arrow to bring up a
list of available choices. Select three and press OK.
129
SONET/SDH Tests
7.3 SONET/SDH Statistics & Error Injection Control
FIGURE 7-4: Main GUI Screen with Statistics & Error Injection
To monitor SONET/SDH performance, first start they type of traffic you wish to monitor by first
pressing the Traffic Configuration icon under the Signal Configuration column or pressing the Traffic
button located on the TX bar and then configuring the SONET or SDH type of traffic you want. The
GUI is context sensitive. When SONET traffic is active, the main GUI page displays a SONET
Statistics & Error Injection Control icon. When SDH traffic is active, the main GUI page displays an
SDH Statistics & Error Injection Control icon. Press the icon to enter SONET/SDH Statistics and
Error Injection control. There are three areas to control: BERT, SDH and Bitstream. A list of
SONET/SDH error and anomaly measurements are shown in Table 7-1.
130
SONET/SDH Statistics & Error Injection Control
7.3.1 BERT
FIGURE 7-5: BERT Statistics
There are no Error Injection Control Options with SONET/SDH BERT.
You may simultaneously monitor five sets of statistics. Press one of the boxes under the “Click to
Select Error Type” column for a list of available parameters. See Figure 7-6.
131
SONET/SDH Tests
FIGURE 7-6: Statistical Parameters Available to Monitor
You may scroll through the list to view all available parameters. Select the parameter you wish to
monitor and press OK.
132
SONET/SDH Statistics & Error Injection Control
7.3.2 SONET/SDH
FIGURE 7-7: SONET/SDH Error Injection Control and Statistics Screen
TABLE 7-2: SONET Error and Alarm Generation

None Error injection not active
OOF Out Of Frame
AIS–L Alarm Indication Signal - Line
AIS-P Alarm Indication Signal - Path
RDI–L Remote Defect Indication - Line
RDI-P Remote Defect Indication - Path
REI–L Remote Error Indication - Line
REI–P Remote Error Indication - Path
B1 Section Bit Interleaved Parity
B2 Line Bit Interleaved Parity
B3 Path Bit Interleaved Parity
Other A different layer such as PoS or 10 GE WAN
133
SONET/SDH Tests
TABLE 7-3: SDH Error & Alarm Generation

None Error injection not active
OOF Out Of Frame
MS-AIS Multiplex Section Alarm Indication Signal
AU-AIS Administrative Unit Alarm Indication Signal
MS-RDI Multiplex Section Remote Defect Indication
HP-RDI Higher-order Path Remote Defect Indication
MS-REI Multiplex Section Remote Error Indication
HP-REI Higher-order Path Remote Error Indication
B1 Section Bit Interleaved Parity
B2 Line Bit Interleaved Parity
B3 Path Bit Interleaved Parity
Other A different layer such as PoS or 10 GE WAN
You may inject one type of error at a time by selecting the radio button next to the desired parameter.
Pressing the name of the parameter brings up a screen shown in Figure 7-8 that gives you control over
the how often the error will be applied.
FIGURE 7-8: Error Injection Rate Control
134
Statistics
7.3.3 Payload
FIGURE 7-9: Bitstream Payload
There are no Error Injection Control Options with bitstream in the payload. In the case of
SONET/SDH with PoS or 10GE WAN in the payload, the context-sensitive GUI has active Error
Injection Controls. For more information, see CHAPTER 8 or CHAPTER 10.
You may simultaneously monitor the sets of statistics shown by pressing the green Start arrow.
7.4 Statistics
The A3308 10 Gb/s Optical Standards Tester provides you with several statistics concerning the
transmitted and received signal. By selecting the SONET Statistics & Error Injection icon you can get
a lot of information about the received signal. The error conditions detected by the A3308 are the Bit
Error Rates and Total Bit Errors for B1, B2, and B3 Bytes, as well as the M1 Byte. The A3308 also
provides the B1, B2 and B3 total Corrected Errors and Corrected Error Rate. In addition to the errors
just listed, the A3308 provides Total Errored Seconds, Severely Errored Seconds, and Unavailable
Seconds. See Table 7-2.
135
SONET/SDH Tests
FIGURE 7-10: SONET Statistics & Error Injection Control
The B1, B2 and B3 bytes are BIP-8 error bytes and as such have theoretical limits. The corrected Bit
Error Rate indicates what the error rate would be if there were not any limits to these bytes.
Error Injection. The SONET (or SDH) Statistics & Error Injection Control screen enables you to
inject either B1, B2, or B3 errors. By clicking on the orange box that indicates the type of error to be
inserted, a window will pop up providing you with additional options for how the errors are inserted.
Errors are inserted in a Continuous mode or Burst mode. If burst mode is selected you can insert
either a single burst or a repeating burst, where the A3308 will insert the selected error type for a
specified number of seconds. If repeating burst is selected, the burst repeat rate is configured by the
number of seconds in which the errors will be inserted after X seconds for the duration defined by the
burst length.
In addition to inserting errors the A3308 can insert the following alarms;
SDH: LOF, OOF, MS-AIS, MS-RDI, MS-REI, HP-REI, HP-RDI
SONET: LOF, OOF, AIS-L, RDI-L, REI-L, REI-P, RDI-P
To enable error or alarm injection simply select the button next to the error or alarm desired and select
apply. To stop the error condition simply select None and press Apply. The error injection may also be
turned off by pressing the Stop Error Injection button. See Table 7-2. If the “Other” button is selected
then errors are currently being injected at another layer of the signal. For example if the signal
configuration is PoS and B1 errors are being injected, the PoS statistics page will have the “Other”
button selected indicating errors are being injected from another statistics page.
136
CHAPTER 8 PoS Tests
In order to perform any of the following tests, you must have already selected and configured the
desired type of traffic. You may also verify that the A3308 10 Gb/s Optical Standards Tester is
operating error free by placing it in loopback mode and comparing the data transmitted by the A3308
to that received by the A3308. Once error-free operation is verified, your DUT should be hooked up
normally to the A3308 and testing may begin.
8.1 PoS
In addition to supporting Bitstream (unframed PRBS) traffic in the SONET payload the A3308 10
Gb/s Optical Standards Tester also supports Packet over SONET (PoS). Selecting PoS under the
SONET heading in the left column will change the selections available in the protocol setup (center)
column. When PPP: Set Up is selected, you can enter the PPP session negotiation parameters (see
Figure 8-1). If Enable PPP link negotiation is selected, the A3308 will automatically negotiate the
magic number and establish the session, giving error codes in English if the session fails. You may
specify the maximum configure requests, the maximum terminate requests, the retry timeout, magic
number parameters for the session, maximum receive unit, or negotiate IP address (a description of
these options is given below).
Scrambling. The transmitter or the receiver can be enabled or disabled by simply selecting the
appropriate check box in the scrambling window. The A3308 is capable of scrambling either the
transmitter or the receiver independently or both can be scrambled simultaneously.
Enable MPLS. Negotiates the support of MPLS protocol with peer.
Max-Configure. Similar to max-terminate, this counter indicates the number of configure-request

packets sent without receiving a valid configure-ack, configure-nak, or configure-reject before
assuming that the peer is unable to respond. Max-configure defaults to 10 transmissions.
Max-Terminate. This counter indicates the number of terminate-request packets sent without
receiving a terminate-ack (acknowledge) before assuming that the peer is unable to respond. The
default is 5 transmissions.
137
PoS Tests
FIGURE 8-1: PoS PPP Setup
Retry Timeout. The restart timer is used to time transmissions of configure-request and terminate-
request packets when negotiating a PPP session. Expiration of the restart timer causes a timeout event
and retransmission of the corresponding configure-request and terminate-request packets. The default
value is three seconds.
Negotiate Magic Number. This configuration option provides a method to detect looped-back links.
Maximum-Receive-Unit (MRU). This configuration option may be sent to inform the peer that the
instrument can receive larger packets or to request that the peer send smaller packets. The default
value is 1232 bytes. This option is used only to indicate an implementation capability, the peer is not
required to maximize the use of the capacity.
NCP. Allows for configuring the IP protocol modules on both ends of the point-to-point link. Allows
the end points to negotiate IP addresses.
Once the session is established, the A3308 can generate full line rate IP traffic and insert it into the
SONET/SDH frame. Figure 8-2 shows the PoS traffic configuration screen. When IP Header &
Payload is selected in the center column, you can define the entire IP header. Ramping of source and
destination addresses can be enabled using mask field. Two patterns are available for the payload: All
0s and Alternate 1s and 0s.
138
PoS
FIGURE 8-2: PoS IP Header
The final PoS Traffic tab is the IP MPLS setup. If desired you can configure up to four MPLS
headers. To enable MPLS labels check the MPLS support box on the top of the MPLS setup tab. (See
Figure 8-3.)
139
PoS Tests
FIGURE 8-3: MPLS Setup
8.2 PoS Statistics & Error Injection Control
PoS Statistics: From the main screen you select the PoS Statistics & Error Injection Control icon.
The A3308 tracks both the transmit and receive statistics for Total IP Packets, Total IP Bad
Checksum, IP Packets filtered, IP Bad Checksum filtered, FCS Errored PPP Frames, Aborted PPP
Frames, Undersized PPP Frames and Oversize PPP Frames (see Figure 8-4). Displayed are the total
counts as well as the rate for the various parameters. The A3308 also shows the transmitted statistics
making it easy to compare what is transmitted to what is received. If a parameter displays a “---” in
one of the column, then measurement for that parameter is not supported.
140
PoS Statistics & Error Injection Control
FIGURE 8-4: PoS Statistics & Error Injection Control.
TABLE 8-1: PoS Statistics
Transmit & Receive Statistics

IP packets
IP Bad Chksm
IP Packet (filtered)
IP Bad Chksm (filtered)
PPP frames
FCS Err PPP Frames
Aborted PPP Frames
Undersize PPP Frames
Oversize PPP Frames
PoS Error Injection Control: Either FCS or IP Checksum errors can be inserted into PoS traffic.
There are three options for inserting errors:
• Insert errors into 100% of the packets.
• Insert a single burst of errors for a specified time.
• Insert a repeating burst where the duration of the burst and the repeat rate are both defined by you.
To configure the error insertion mode, click on the orange box for the type of errors that are desired.
A popup window will appear with the selections available for the desired error condition. Once the
141
PoS Tests
insertion mode in selected click ok. The radio button next to the error type must be selected and then
click on apply to start the error generation.
142
CHAPTER 9 OTN Tests
In order to perform tests with OTN traffic, you must first select and configure the desired type of
traffic. You may also verify that the A3308 10 Gb/s Optical Standards Tester is operating error free by
placing it in loopback mode and comparing the data transmitted by the A3308 to that received by the
A3308. Once error-free operation is verified, your DUT should be hooked up normally to the A3308
and testing may begin.
9.1 OTN Traffic Configuration

To configure the OST for OTN traffic, choose the Traffic Configuration icon under the Signal
Configuration column of the main screen and then OTN from the list of traffic types.
Selecting tabs under the OTN Setup provides access to individual setup screens for each type of
protocol. See that protocol or Bitstream section of the manual for detailed setup information for each
tab.
For OTN Bitstream traffic the payload type is set to FE and for OTN Sonet and OTN SDH the
payload type is set to 3. You may also choose to separately enable or disable scrambling and FEC.
The OTN header may not be modified as of the release date of the manual.
143
OTN Tests
FIGURE 9-1: OTN/SONET/10GE WAN Traffic Setup
9.2 OTN Statistics and Error Monitoring

Pressing the button to the left of the LEDs on the Error Bar toggles the Error Bar
through different displays. For example, if the active OTN traffic is SDH with POS in
the SDH payload, the Error Bar will toggle between OTN OTU, OTN ODU, SDH, and PoS.
Selecting the OTN Statistics & Error Injection icon under the Statistics & Error Injection column of
the main screen enables you to monitor the OTN TX and RX statistics and to inject errors into the
OTN signal.
144
Transmit Features
9.3 Transmit Features
FIGURE 9-2: OTN Statistics & Error Injection Control
TX Error Generation. The OTN Statistics & Error Injection Control screen enables you to inject
either OTUais, ODUais, ODUclk, ODUoci. By clicking on the orange box that indicates the type of
error to be inserted, a window will pop up providing you with additional options for how the errors
are inserted.
Errors are inserted in a Continuous mode or Burst mode. If burst mode is selected you can insert
either a single burst or a repeating burst, where the A3308 will insert the selected error type for a
specified number of seconds. If repeating burst is selected, the burst repeat rate is configured by the
number of seconds in which the errors will be inserted after X seconds for the duration defined by the
burst length.
TABLE 9-1: OTN Error and Alarm Generation
Errors
OTU-AIS Optical Transmit Unit - Alarm Injection signal
ODU-AIS Optical Data Unit - Alarm Injection signal
ODU-LCK Optical Data Unit - Lock
ODU-OCI Optical Data Unit - Optical Connection Indication
145
OTN Tests
TX and RX Statistics. The list of OTN parameters for which statistics may be captured is shown in
Table 9-2. To begin capturing statistics, press the green Start arrow in the Statistics frame. Counts and
rates are updated until the red stop button is pressed or the gate control condition is met.
TABLE 9-2: OTN Statistics
Transmit & Receive Statistics
OTN Frames
SM-BIP
PM-BIP
SM-BEI
PM-BEI
CORR_0S
CORR_1s
CORR_BIT
UNCORR
The error type and uncertainty may be selected from the pull-down menu. See Table 9-3.
TABLE 9-3: Gate Errors and Uncertainty

BIPSM
BIPPM
BEISM
BEIPM
FECCORRBIT0
FECCORRBIT1
FECCORRBIT
FECUNCORR
FECTOTBITERR
B1
B2
B3
M1
146
CHAPTER 10 10GE LAN/WAN Tests
In order to perform any of the following tests you must have already selected and configured the
desired type of traffic. You may also verify that the DUT is operating error free by placing it in
loopback mode and comparing the data transmitted by the A3308 10 Gb/s Optical Standards Tester to
that received by the A3308. Once error-free operation is verified your DUT should be hooked up
normally to the A3308 and testing may begin. In addition to the tests listed in this section, the A3308
can perform any of the physical layer tests such as sensitivity, with this protocol traffic.
NOTE: Configuration setup screens for both LAN and WAN traffic are identical. Therefore, in
this chapter, the screen shots from only WAN setup are used.
10.1 10GE LAN/WAN

When generating IEEE 802.3ae WAN traffic, you may specify the IEEE 802.3ae setup which
includes RX Pause Control, Interpacket Gap and Link Failure Detection. Then the IEEE 802.3ae
Header and Payload needs to be defined. This is followed by the IP Header and Payload definitions
and optional MPLS labels.
10.1.1 802.3ae Setup
This window (Figure 10-1) allows you to define the RX Pause control. This is done by specifying a
specific device address or by using the standard multicast address.
Pause Control. Device Address is the machine address for the device transmitting packets to the
A3308. When the Enable RX Pause Control is selected the A3308 will respond to a multicast pause
command. When Enable for device address is selected the A3308 will respond when it detects the
proper device address as defined in the device address window.
Interpacket Gap. Is the delay between sending out packets. The time is defined in Bytes, and is
selectable by you with a minimum of 12 Bytes to a maximum of 264 Bytes.
147
10GE LAN/WAN Tests
FIGURE 10-1: 10GE WAN Setup
802.3ae. The two 802.3ae patterns that may be transmitted are CRPAT and CJPAT. The CRPAT
pattern is intended to provide a broad spectra content and minimal peaking that can be used for the
measurement of the jitter either at the component or system level.The CJPAT “Continuous Jitter Test
Pattern” is intended to expose a receiver’s CDR to large instantaneous phase jumps.
Link Failure Detection. Is enabled by default but can be disabled by you. When a failure is detected
the A3308 will generate a failure notification packet.
User-Defined Ordered Sets. Local and remote faults are detected using standard ordered sets. User
defined ordered sets allow for debugging link issues.
10.1.2 802.3ae Header & Payload Setup

(See Figure 10-2)
Preamble. This value is fixed according to the IEEE 802.3ae standard and cannot be changed by
you.
SFD. Is the start of frame delimiter and is defined by you.
Source/Destination Address. Ramping of addresses can be enabled using mask field. Specifying 0
in the mask byte allows ramping on that byte to be enabled. Source address 1:1:1:1:1:1 and
destination address 1:1:1:1:1:255 mask 1:1:1:1:1:0 allows ramping on the last byte.
148
10GE LAN/WAN
Length/Type. This selection can be used to generate length errors. By default the length is Auto
Calculated. Length errors can be generated by selecting manual and entering an incorrect packet
length.
LLC/Snap & Type. These settings are used to define the type of traffic being carried in the 802.3ae
packets. The defaults are for IP data and should only be changed by experienced users.
Scramble Payload. Present only for WAN traffic. This is done using X43 scrambler.
FIGURE 10-2: 10GE WAN 802.3ae Header & Payload Setup
10.1.3 IP Header and Payload
Version, IHL, Total Length, Flags, Fragment Offset and Header Checksum. These values are
either fixed or calculated by the A3308 and are not selectable by you.
Type of Service. This field denotes the priority of the packet and can be set by you.
Identification. Is a random number generated to identify the specific packet transmitted.
Source/Destination Address. Ramping of addresses can be enabled using mask field. Specifying 0
in the mask byte allows ramping on that byte to be enabled. Source address 1:1:1:1:1:1 and
destination address 1:1:1:1:1:255 mask 1:1:1:1:1:0 allows ramping on the last byte.
149
10GE LAN/WAN Tests
IP Payload. The number of bytes in the IP payload is selectable by you. Values from 17 to 1474 can
be entered. The A3308 enables you to generate invalid packets, undersized or runt error will be
generated if you select 17 bytes as the length.
IP Payload. The A3308 can generate three different IP Payloads. Valid selections include All 0’s,
All 1’s or Alternating 1’s and 0’s.
FIGURE 10-3: 10GE WAN IP Header and Payload Setup
10.1.4 IP MPLS Setup
MPLS Labels. The A3308 supports the generation of up to four MPLS labels. To activate the use of
labels the MPLS Support block at the top of the MPLS setup page must be selected (Figure 10-4).
You have control over label values, time to live field and experimental bit fields. Ramping is
supported on the label fields.
150
802.3 Statistics & Error Injection Control
FIGURE 10-4: 10GE WAN MPLS Setup
10.2 802.3 Statistics & Error Injection Control
802.3 Statistics. From the main screen select the 802.3 Statistics & Error Injection icon which will
bring you to the statistics and error inject page. For a complete list of the transmit and receive
statistics tracked by the A3308 see Table 10-1.
Error Injection Control. The following types of errors can be inserted by the A3308, either FCS, IP
Checksum and TXPause errors. Once enabled the FCS and IP Checksum errors can be controlled in
three different ways. The first method is Continuous Insertion which will insert errored bytes into
100% of the packets. The second option is to insert a single burst of errors for a specified time. The
third method is to insert a repeating burst where the duration of the burst and the repeat rate are both
defined by you.
The TXPause error setup screen (see Figure 10-5) allows the user to configure the insertion type
(Single Frame, Periodic), TX Pause time (wait time for the receiver to start transmitting on receive of
a pause frame) and the frequency at which the OST sends out the pause frame may be set in seconds
(Coarse) or milliseconds (Fine).
151
10GE LAN/WAN Tests
FIGURE 10-5: TX Pause Setup Screen
152
802.3 Statistics & Error Injection Control
TABLE 10-1: 10GE WAN Statistics
Transmit & Receive Statistics Transmit & Receive Statistics

Signal Detect Broadcast Frames
Frame Sync Non-Zero 802.3 Time Pause
Pause State Pause End Frames
Hiber State Valid 64 Byte Frame
LCDP Valid 65-127 Byte Frame
Local Fault Valid 128-255 Byte Frame
Remote Fault Valid 256-511 Byte Frame
Valid Frames Valid 512-1023 Byte Frame
Valid Bytes in Good Frame Valid 1024-1518 Byte Frame
Errored Frames Valid >1518 Byte Frame
Errored Bytes in Frame Errored 64 Byte Frame
Hiber Frames Errored 65-127 Byte Frame
Frame Fragments Errored 128-255 Byte Frame
Frame Jabber (Ovr & FCS) Errored 256-511 Byte Frame
FCS errored Frame Errored 512-1023 Byte Frame
PCS Frame Decode Error Errored 1024-1518 Byte Frame
Frame Length Errors Errored >1518 Byte Frame
Preamble Errors IP Packets
Dropped Frames IP Bad Checksum
Undersize Frames IP Packet (filtered)
Oversize Frames IP Bad Checksum (filtered)
Multicast Frames
153
10GE LAN/WAN Tests
154
CHAPTER 11 Remote Operation
In addition to the touch screen interface on the A3301 OST System Controller, the 10 Gb/s OST
System may be controlled or monitored via an external computer. A GPIB interface or an Ethernet
10/100 BaseT connection from the external computer may be used (using the standard SCPI
command set). These two methods of remote operation are described in this chapter.
11.1 Remote Database Access using ODBC
11.1.1 Install the postgre drivers.

The drivers can be obtained in the following two locations.
1. Download the driver from tap://gborg.postgresql.org/project/psqlodbc/genpage.php?downloads
2. Connect the 3301 to your LAN (see Section 1.5 Connecting to a LAN to get the IP address of the
3301) and point your browser to the OSTs webserver http://<OSTC IP address>/gpl/GPL.html
Unzip the package and install the driver
11.1.2 Create a connection to the OST.

1. In Excel, select Data/Get External Data/New Database Query from the menu
2. Highlight "New Data Source" and click OK in the "Choose Data Source" Window
3. Enter a name for this database connection. You will need to remember this name whenever you
connect to the 3301 database.
4. Select the "PostgreSQL" driver and click on CONNECT
5. Enter the following info:
Database Name: cirnos Server: <serial Number/IP address>
User Name: dbuser Password: <empty>
6. You will now be able to view data and perform queries on the database tables.
NOTE: The tables and their entries are READONLY and are not user modifiable.
155
Remote Operation
11.2 SCPI Control

Using either a GPIB cable or a 10/100 BaseT Ethernet connection, the standard SCPI command set
may be used to remotely monitor and control the test system. Every operation that can be performed
by the GUI may also be done remotely using the SCPI command set. A list of the relevant SCPI
Commands is given in the CHAPTER 13. A brief description of some basic GPIB concepts, the
remote operation setup, and command syntax are given here. A summary list of the SCPI command
set is also given below.
11.2.1 Ethernet Interface

The A3301 communicates with the A3308 via an Ethernet interface. There is an additional RJ45
connector on both the A3301 and the A3308 which serve two purposes. The first is to enable the
A3301 to interface to multiple A3308’s and the second is to enable connecting the A3301 to an
existing LAN. By connecting the A3301 to the existing LAN, test results can be e-mailed or printed
on a network printer.
11.2.2 GPIB Interface

GPIB (General Purpose Interface Bus) is the common acronym for the industry-wide standard for
interconnecting scientific instruments and computers for control purposes. A GPIB system may
consist of one or more “talkers” and “listeners” and at least one “controller”. The talkers supply data
on the bus while the listeners accept data from the bus. A controller designates talkers and listeners
and may change their characteristics. The A3301 may be either a talker/listener (slave) or a controller
(Master). Two independent GPIB ports are standard with the A3301. This enables you to control other
instruments with the 10 Gb/s OST System, such as an oscilloscope, OSA or power supply.
11.2.2.1 Setting up the GPIB Controller

The two GPIB connectors for the 10 Gb/s OST System are on the rear panel of the A3301 (see Figure
11-1). Your computer must have the appropriate GPIB interface in order to control the test system in
this manner. The cable from your controller should be connected to the GPIB port labelled “slave.” If
other scientific instruments are on the interface, the GPIB cables may be connected in parallel from
the controller or a serial connection may be stacked onto the slave connector. The GPIB slave
connector on the A3301 suffices to connect the entire 10 Gb/s Optical Standards Test System
(including all Circadiant slave units) to the interface.
156
SCPI Control
GPIB GPIB
Slave Master
FIGURE 11-1: A3301 Rear Panel
The GPIB “master” port on the A3301 can be used when the A3301 is to be the GPIB controller for
other instruments. It may also be used in conjunction with the slave port (that is, when the A3301 is a
GPIB listener and/or talker). In that case, the A3301 receives instructions from the controller that
direct the A3301 to send control messages to its own external units on the GPIB. Additionally, special
commands from the external controller that must be sent to an instrument that is being controlled by
the A3301 will be forwarded by the A3301.
The settings listed below are used to configure the GPIB interface. Refer to the external computer’s
GPIB documentation for details. Typical values are given here, however, these values may be
adjusted by you.
TABLE 11-1: Typical GPIB Interface Configuration

Primary GPIB address 0 through 30
Secondary GPIB address NONE
Timeout 10 sec
Serial poll timeout 1 sec
Terminate read on EOS NO
Set EOI with EOS on writes Yes
Type of compare on EOS 7-bit
EOS byte 00h
To adjust these values, select the GPIB icon from the Administration screen on the GUI.
157
Remote Operation
11.2.2.2 Switching to Remote Operation

On receiving the following command, the instrument with switch into remote mode:
INSTrument:Select:ID N where N is the number of OST connected (usually 1).
11.2.2.3 Command Syntax

It is assumed that if you wish to utilize the GPIB interface you have a working knowledge of GPIB
programming for instrument control. A brief review of command syntax and structure is given here.
For further reference, please see the ANSI/IEEE-488.2-1987 standard.
The syntax of the GPIB command set for the 10 Gb/s Optical Standards Test System follows the rules
defined in the ANSI/IEEE-488.2-1987 standard. For the sake of clarity, the letters which must be
contained in the GPIB command or query are shown in uppercase. However, the commands are not
case sensitive. Lowercase letters are used to identify optional letters which may be used to make
control programs more readable. A single space must separate a command from its parameters or
data. Extra spaces may come before a comma, semicolon, or terminator to improve readability, but
too many spaces can overflow the data I/O buffer (10,000 bytes). There should be no space between a
query mnemonic and its question mark.
11.3 Generalized Programming Flow Example

The following is a programming example for running a sensitivity test remotely (Version 4.X). The
commands are the same whether the A3301 is controlled via Ethernet or GPIB. The program, when
using GPIB, was written for a National Instrument IEEE488 interface and assumes that the drivers are
already loaded on the machine. Since Visual Basic also has forms associated with it, only portions of
the code are presented below, and the entire example is available upon request.
158
Generalized Programming Flow Example
This example assumes that the Signal Configuration and Sensitivity parameter files were previously
setup using the GUI. One can also manually setup each of these parameters, but since there are so
many commands available, it is easier to start with a stored file.
Define Function and Variables
Select Instrument
Reset GPIB
Set Max Output Power to 0dB
Reset Sensitivity Subsystem
Load Signal Config
Start Traffic
Load Parameter File
Configure Error Source
Start Sensitivity Test
Loop until Test Finished
Get Details
Exit Function
159
Remote Operation
Below is a code snippet in VB for running a sensitivity test (Lets and Gets have been removed). In
practice you would call the following functions from a GUI, also Winsock1 referenced below would
also be on a form:
• DeviceOpen
• TestSensitivity
Option Explicit
Private mvarUseEnet As Boolean
Private mvarGPIBAddress As Integer
Private mvarBoardId As Integer
Private mvarIPAddress As String
Private intDev As Integer 'Holds Unique Id From NI Driver
Private objEnetConnectionObject As Winsock 'Setup on a different form
Private mvarSleepTime As Integer
'******************************************************************
'** Class Name: clsA3301 **
'** Date Modified: 01/21/2004 **
'** Description: **
'** The following class is used to communicate with the A3301. It uses the **
'** variable mvarUseEnet to determine whether to use GPIB or Ethernet.
'******************************************************************
Public Function TestSensitivity() As String()
'Function returns the following array
'Array(0) = Sensitivity
'Array(1) = Slope
'Array(2) = Sigma
'Array(3) = Status
'This function also has ties to the Progressbar on the main screen - this is for
ease of display only.
Dim strReturn As String
Dim intOpc As Integer
Dim strData(4) As String
On Error GoTo TestSensitivityError
SendCommand ("INSTR:SELE:ID 1")
Call waitWDoEvents(1) 'Sleep 1 second
SendCommand ("OUTPUT:TELECOM:OST:MAXPOWER -5") 'Set Max
Output Power
SendCommand ("IQ:SENSITIVITY:RESET"): WaitForFinished (5)
'Reset Sensitivity Subsystem
SendCommand ("OUTPUT:TELECOM:TRAFFIC:CONFIGURE:LOAD
/Signal_Conf/OC192/Unframmed/default.cfg"): WaitForFinished (5) 'Load
Signal Config
SendCommand ("OUTPUT:TELECOM:TRAFFIC:CONFIGURE:START
0"): WaitForFinished (5) 'Start Traffic
160
SendCommand ("IQ:SENSITIVITY:CONFIG:LOAD
/Sensitivity/OC192_common/default.par"): WaitForFinished (5) 'Load
Parameter File
SendCommand ("IQ:SENSITIVITY:CONF:ERROR PRBS"):
WaitForFinished (5) 'Configure Error Source
SendCommand ("IQ:SENSITIVITY:START ") 'Start Sensitivity Test
Call waitWDoEvents(3) 'Sleep 3 seconds
Do
Call waitWDoEvents(1) 'Sleep 1 second
SendCommand ("IQ:SENS:RESULT:SUMMARY?") 'Used Only To Update
A Progress Bar
Call ReadCommand(strReturn, 500) 'Used Only To Update A Progress Bar
frmMainScreen.ProgressBarSens.value =
CInt(parseResultsString(strReturn, "PERCENT"))'Used Only To Update A
Progress Bar
SendCommand ("*OPC?") 'Check If Test Is Finished Yet
Call ReadCommand(strReturn, 500)
Debug.Print (strReturn)
intOpc = CInt(Trim(strReturn))
Loop Until (intOpc = 1) 'Loop Until *OPC = 1 (Test Finished)
SendCommand ("IQ:SENS:RESULT:SUMMARY?") 'Returns a delimited
String
Call ReadCommand(strReturn, 500)
strData(0) = parseResultsString(strReturn, "POWER") 'Sensitivity Result
strData(1) = parseResultsString(strReturn, "SLOPE") 'Slope
strData(2) = parseResultsString(strReturn, "UNCERT") 'Uncertainty
strData(3) = parseResultsString(strReturn, "RESULT") 'Status
frmMainScreen.ProgressBarSens.value = 100
TestSensitivity = strData
Exit Function
TestSensitivityError:
Call MsgBox("ERROR: " + Err.Description, vbCritical, "ERROR")
Err.Clear
TestSensitivity = strData
frmMainScreen.ProgressBarSens.value = 100
End Function
Private Function parseResultsString(Data As String, whatParam As String) As

String
'Parses the Result Summary And Returns whatParam as a string
'Valid values for whatParam are as follows:
'PERCENT,POWER,SLOPE,RESULT,UNCERT
Dim retString As String
Dim tmpStr() As String
Dim key As String
161
Remote Operation
Dim i As Integer
Dim cnt As Integer
retString = ""
tmpStr = parseString(Data, " ")
cnt = UBound(tmpStr)
Select Case UCase(whatParam)
Case Is = "PERCENT"
key = "PERCENT_"
Case Is = "POWER"
key = "PWR_"
Case Is = "UNCERT"
key = "PWERR_"
Case Is = "SLOPE"
key = "SLOPE"
Case Is = "RESULT"
key = "RSL_"
Case Else
key = ""
End Select
If key = "" Then
parseResultsString = retString
Exit Function
End If
i=0
Do
If InStr(1, tmpStr(i), key) > 0 Then
retString = tmpStr(i + 1)
Exit Do
End If
i=i+1
Loop Until (i > cnt)
parseResultsString = retString
End Function
Private Function parseString(Data As String, Optional delimiter = " ") As

String()
'Function parses result string into an array of alternating name value pairs
'i.e. array(9) = PERCENT array(10) = 100 etc
Dim pos As Integer
Dim pos2 As Integer
Dim strReturn() As String
Dim i As Integer
i=0
pos2 = 0
ReDim strReturn(Len(Data) / 2)
162
Do
pos = pos2 + 1
pos2 = InStr(pos2 + 1, Data, delimiter)
If (pos2 = 0) Then Exit Do
strReturn(i) = Mid(Data, pos, pos2 - pos)
i=i+1
Loop Until (pos2 < 1)
ReDim Preserve strReturn(i - 1)
parseString = strReturn
End Function
Private Function WaitForFinished(Optional TimeOutSeconds As Integer = 50)

As Boolean
'Function Returns a True if Success, False if timeout was reached or error
occurred
Dim Data As Integer
Dim strReturn As String
Dim StartTime As Date
Dim Success As Boolean
'Exit Function
Success = True
StartTime = Now
Data = 999
Do While (Data <> 1) And (Success = True) And (DateDiff("s", StartTime,
Now) < TimeOutSeconds)
Success = SendCommand("*OPC?")
waitWDoEvents (0.1)
Success = ReadCommand(strReturn)
If IsNumeric(Trim(strReturn)) Then
Data = CInt(Trim(strReturn))
Debug.Print Data
Else
Data = 99
End If
Loop
If (DateDiff("s", StartTime, Now)) >= TimeOutSeconds Then Success = False
WaitForFinished = Success
End Function
Public Sub waitWDoEvents(Seconds As Single)

Dim intTime As Integer
Dim X As Integer
intTime = Seconds * 10
For X = 1 To intTime
Sleep (100)
163
Remote Operation
DoEvents
Next X
End Sub
Public Function DeviceOpen() As Boolean

'Function returns a false if an error has occurred
On Error GoTo DeviceOpenError
DeviceOpen = True
If Not mvarUseEnet Then
Call ibdev(mvarBoardId, mvarGPIBAddress, 0, 13, 10, 10, intDev)
Call ibclr(intDev)
If (ibsta And EERR) Then
'Check For GPIB Error
DeviceOpen = False
End If
Else
objEnetConnectionObject.RemoteHost = mvarIPAddress
objEnetConnectionObject.RemotePort = 2018
objEnetConnectionObject.Connect
DoEvents
End If
Exit Function
DeviceOpenError:
Err.Clear
DeviceOpen = False
End Function
Public Function SendCommand(Command As String)

Dim intCounter As Integer
SendCommand = True 'Assume Pass
intCounter = 0
'Use GPIB
Call ibwrt(intDev, Command)
SendCommand = False
End If
Else
'Use Enet
objEnetConnectionObject.SendData (Command + vbLf)
If objEnetConnectionObject.State = sckError Then
'Check For Enet Error
SendCommand = False
End If
164
End If
Sleep (25)
DoEvents
If SendCommand = False Then
Call Err.Raise(vbObjectError + 1000, "SendCommand", "Error Sending
Command:" + Command)
End If
End Function
Public Function ReadCommand(DataString As String, Optional Length As

Integer = 1000)
Dim time1 As Date
ReadCommand = True 'Assume Pass
DataString = Space(Length)
time1 = Now
'Use GPIB
Call ibrd(intDev, DataString)
ReadCommand = False
End If
Else
'Use Enet
Do While DateDiff("s", time1, Now) < 10 'Wait 10 Seconds
Sleep (10)
If Len(frmTCPSocket.EnetDataReceived) < 2 Then
'Loop Again
Else
'Data Has Arrived
DataString = frmTCPSocket.EnetDataReceived
frmTCPSocket.EnetDataReceived = ""
Exit Do
End If
DoEvents
Loop
If DateDiff("s", time1, Now) >= 10 Then
Debug.Print "*********** Read Command Timeout ************"
End If
End If
If ReadCommand = False Then
Call Err.Raise(vbObjectError + 1001, "ReadCommand", "Error Getting
Data")
End If
165
Remote Operation
End Function
Option Explicit
Private mvarEnetDataReceived As String
Dim strDataReceived As String
'******************************************************************
'** Form Name: frmTCPSocket **
'** Date Modified: 01/21/2004 **
'** Description: **
'** Very simple socket implementation. No error handling **
*******************************************************************
Private Sub Form_Load()
strDataReceived = ""
End Sub
Private Sub Winsock1_DataArrival(ByVal bytesTotal As Long)

Dim strDummy As String
Winsock1.GetData strDummy, vbString
strDataReceived = strDataReceived + strDummy
If InStr(1, strDataReceived, vbLf) > 1 Then
'Entire Message Received
mvarEnetDataReceived = strDataReceived
strDataReceived = ""
End If
'DoEvents
End Sub
Public Property Let EnetDataReceived(ByVal vData As String)
mvarEnetDataReceived = vData
End Property
Public Property Get EnetDataReceived() As String

EnetDataReceived = mvarEnetDataReceived
End Property
166
CHAPTER 12 Debug Station
12.1 Introduction
This chapter is a “getting started” guide to the Circadiant 10 Gb/s Optical Standards Test System
optical debug station application. The application runs a sequence of tests on an optical Device Under
Test (DUT) using both Circadiant’s suite of tests and tests based on external devices controlled via
GPIB.
The test flow is set up so that basic failures are tested before attempting to check for more subtle
problems. For example achieving sync is tested before trying to measure sensitivity. A “stop-on-fail”
feature is available allowing the test sequence to be cut short on the first failure to avoid wasting time
on further tests.
Some of the benefits of the Circadiant solution to reduce costs and increase productivity include:
• Integration of optical components into a small, portable box
• Automation of key tasks in software, controlled by a simple GUI
• Excellent consistency and repeatability of results
• OC192 SONET (9.95 Gb/s), 10G Ethernet LAN (10.3 Gb/s) and OTN (10.7) rates
12.2 Hardware Setup

This section describes additional steps required to use the debug station application. The application
requires external devices:
• an optical switch with at least 3 outputs, supported models are JDS Fitel, Dicon GP 700,
Continium Photonics Direct Light.
• Agilent 86100A infiniium DCA
• Agilent 86120C wavemeter
167
Debug Station
NOTE: If the intended devices to be tested do not supply an electrical trigger signal appropriate
for triggering the DCA then a clock recovery module for the scope is also necessary. If
such a module is used it must be placed in the left slot of the DCA mainframe.
Only the OC192 SONET rate is currently supported for the clock recovery module, however many
devices (e.g., many transponder test boards) supply an electrical trigger signal, which enables DCA
testing of devices running at 9.95, 10.3 or 10.7 Gb/s.
The switch, DCA and wavemeter GPIB connections must be daisy chained together and connected to
the GPIB master port on the A3301 System Controller.
NOTE: Other GPIB devices may be on the same bus, however, if there is another controller
(e.g., a PC running LabVIEW) on the bus there may be contention for control of the
slave devices resulting in unpredictable behavior.
The DUT RX should be connected to the OST TX. The DUT TX must be connected to the switch
input. Three of the switch outputs must be connected to the OST RX, DCA, and wavemeter. All
optical connectors should be cleaned and inspected prior to mating. The optical paths should be
checked for losses due to fiber breaks or kinks, improperly mated connections etc. with a handheld
optical power meter.
NOTE: The power meter measurements can be used to determine the TX and RX calibration
factors which can be set on the A3301 System Controller front panel. If these factors
are set then the OST will automatically take them into account in its measurements and
tests.
12.3 Configuring the Debug Station Application

The debug station application is configured via web access. This is available from the Optical
Standards Tester Controller (OSTC) Admin page. Use the web browser icon and navigate to the
Debug Station link. Alternatively, any computer running a standard web browser such as Netscape or
Internet Explorer with network connectivity to the A3301 System Controller may be used to access
the web features via the URL http: //<OSTC_address>. With the appropriate VPN setup provided by
your IT department this allows remote access to the A3301 System Controller. If the A3301 System
Controller is on a private LAN then depending on your company policy machines may be assigned an
address via DHCP or may use a static IP addresses. The A3301 System Controller network settings
are configurable from the Administration page. In either case, your network administrator should be
able to provide an acceptable address and handle the appropriate record keeping, DNS administration
etc. If this has been done correctly you should be able to use the A3301 System Controller name as
the address, e.g., http: //a1b21136/.
NOTE: If your network administrator is delayed in providing an address, as a temporary

measure it is possible to connect from another computer directly to the A3301 System
Controller. Example: You have a laptop with a static IP address 192.168.100.20 (i.e., in
the private 192.168 address space.) Use a crossover (host to host) ethernet cable to
connect from the laptop ethernet interface to the ethernet IN interface on the A3301
System Controller. Configure the A3301 System Controller with the static IP address
192.168.100.21. At this point from the laptop the A3301 System Controller web access
would be available via the URL http: //192.168.100.21/.
168
Configuring the Debug Station Application
12.3.1 Web Access
The web access feature allows remote configuration of the debug station and remote access to results.
Figure 12-1 shows the top level web access page. The links on this page implement browser access to
saved images and results files from manual test runs, and access to the debug station pages.
• The debug station top page (see Figure 12-2). links to utility pages to configure the GPIB setup
and define the parameters for a new type or model of DUT. It also provides a utility to access and
print IntelliScript™ results and for convenience includes the same image access links available on
the top level page. Some web access features require java. Java is available for free download
from http://java.sun.com installed and enables on the browser.
FIGURE 12-1: Top Level Web Access Page
12.3.2 Debug Station Web Configuration

To configure a test sequence for a particular type of DUT (e.g., a new linecard model) first visit the
“Configure a DUT Type” page (see Figure 12-4). The GPIB setup parameters are echoed at the top of
the page. If these do not correspond to the actual parameters of the setup then visit the “Configure
GPIB” page (see Figure 12-3) to change the GPIB IDs of the instruments or the switch settings
needed to send the DUT TX signal to the DCA, wavemeter and OST. Alternatively, the GPIB IDs and
169
Debug Station
switch settings in the setup could be adjusted to match the default configuration if that is more
convenient.
Once the GPIB IDs and switch settings are correct, enter the appropriate parameters for the DUT
model in the web form. The form can be preloaded with values from any existing configuration,
available at the top of the page by using the LOAD FORM button. The model ID should match the
model ID barcode if the barcode scanner is to be used later to select the test configuration for any
specific devices to be tested.
Once the values in the form are considered to be correct, select the “Create” button at either the top or
bottom of the page. This creates the configuration on the A3301 System Controller. At this point the
configuration is available for selection from the IntelliScript™ “Load” menu on the A3301 System
Controller.
NOTE: If the GPIB setup is changed then any saved debug station test configurations must be
updated. To update, simply reload the saved configuration into the web form and select
the create button.
FIGURE 12-2: Debug Station
170
Configuring the Debug Station Application
FIGURE 12-3: Hardware Setup
171
Debug Station
FIGURE 12-4: Hardware Configuration
12.4 Running the Debug Station Application
12.4.1 Selecting a Configuration

When the OST/OSTC system is powered up it should display a screen similar to Figure 12-5. There
are several tabs across the top of the screen, the currently active is colored and the others are grey.
NOTE: When interpreting screen shots in this chapter, it is important to remember that the
system recalls the most recently used settings, so your screen may show different
content depending on your previous activity.
Navigate to the IntelliScript™ setup screen using the ‘IntelliScript™” tab Figure 12-6. You may now
load your desired configuration using the “Load” icon in the task bar, located below the
“IntelliScript™ Set Up” window. This will bring up a menu of configurations. You can select one by
touching the rectangle to the left of the desired configuration, by keying the name into the entrybox,
or by scanning the product model barcode. Select OK after making your selection.
NOTE: The configuration files have a .par extension. You need not type the extension when
entering the name with the keyboard or scanner. If you scan or type in a non-existent
172
Running the Debug Station Application
configuration the system will display an error message and will leave the current
configuration unchanged.
FIGURE 12-5: Initial Setup Screen On Power Up
173
Debug Station
FIGURE 12-6: IntelliScript™ Setup Screen
When you have selected a test configuration, you should set the serial number of the DUT for archival
purposes. Touch the “serial number” field in the top left of the “Test Information” window. This will
bring up an input keypad on which you can enter the serial number by scanning the serial number
barcode, by using the keyboard, or by using the touchscreen keypad. Touch OK when done. To enable
the stop-on-fail feature, ensure that the “Stop Test” checkbox in the “Action on Test Failure” window
is checked. The IntelliScript™ application is now configured and ready to run.
NOTE: The debug station sequence is a specific IntelliScript™ sequence. Once loaded, the
usual IntelliScript™ features are available. e.g. Actions can be reordered, individual
actions may be toggled on or off, renamed, assigned new test or signal configurations,
etc. The resulting IntelliScript™ sequences may be saved and from the touchscreen
interface, and these saved configurations are available for later use.
174
Running the Debug Station Application
FIGURE 12-7: IntelliScript™ Setup Screen Configured and Ready To Go
12.4.2 Executing and Interpreting Results
To initiate the run, touch the “Start” icon in the task bar. The setup screen will be replaced by the
results screen and the test sequence will begin. The configuration may specify dialogs which give
instructions and pause execution. In that case you should ensure that the instructions have been
fulfilled and select OK when done.
Each action in the sequence is defined by:

• Action type
The actions are labelled by a mnemonic, shown in the leftmost column. The mnemonic is an
arbitrary label which can be used to remind the operator of the purpose of the test. The action type
refers to the code path used by the OST. In some cases such as Sensitivity it has obvious meaning.
In other cases (GPIB and Single Action) they are not necessarily meaningful to the user, but
instead are used internally to define paths to configuration and results data. Some actions do not
represent a DUT test, but instead define a related task such as a user dialog or manipulating an
external switch.
• Action configuration
The action configuration defines the test control configuration and is a meaningful descriptor.
• Signal configuration
The action configuration defines the test control configuration and is a meaningful descriptor. The
signal configuration defines the optical signal from the Circadiant TX, including the bitrate,
protocol and payload along with optical parameters such as power and OSNR. Depending on the
DUT type this column may not be meaningful for all tests.
175
Debug Station
If the system reports test failure, there are two possible interpretations
• The DUT has failed, reported as “Failed”
• The test failed to perform a measurement, reported as “Unknown”
Ordinarily measurement failures should not occur for simple tests which have a clear result, such as
power or synch. However, for more complex aggregate tests such as sensitivity it is possible for the
test to fail because control parameters such as time-outs are set inappropriately.
In cases of doubt, it is possible for the complex tests to repeat the failing test. This also allows logging
the detailed graphical representation of the test. e.g. Suppose that a particular DUT with serial number
DUT1 and model type TXN133030 fails on the RX sensitivity step of the sequence. The operator can
choose to repeat and view this test. To do so, exit IntelliScript™ and return to the top menu by
touching the main tab to the left of the IntelliScript™ tab, which will display the last used signal
configuration, e.g., “SONET: Bitstream - 9.95 Gb/s”. Touch the “Traffic Configuration” icon. Touch
“load” on the task bar. Select the TXN133030 signal configuration file, after navigating to the
appropriate directory if necessary. Touch OK to load it. Touch the “Start” icon to initiate the traffic.
The GUI will return to the top menu. Touch the “Sensitivity” icon, this will take you into the
Sensitivity setup page. From the task bar touch the “Load” icon. Select the
rx_sensitivity_TXN133030 configuration and touch OK. Select the “Start” icon in the task bar to
initiate the test. The system will run the Sensitivity test in exactly the same way as it ran in the
IntelliScript™ sequence for TXN133030. The system will display a plot and results summary which
can be viewed, printed, saved or emailed. Viewing this information can provide deeper insight into
the behavior of the DUT than a simple pass/fail decision and parametric result.
12.5 Test Sequence

This section describes the sequence of IntelliScript™ actions in detail.
12.5.1 Initial Dialog

The initial dialog pops up before any actions are performed. This provides an opportunity to specify
instructions to the operator regarding setup of the DUT. The message also contains a reminder to set
an appropriate maximum power, as some later tests such as Overload and BER vs. OSNR need to set
the OST TX power based on information provided by the user. If prevented from doing so by the
limit defined on the GUI, those tests will be unable to perform their measurements and will report
status Unknown.
12.5.2 Select_OST
This is a GPIB action which sets the switch so that the signal from the DUT/TX goes to the OST RX.
See Section 12.6.1 Failures in GPIB Actions
12.5.3 TXPower
The OST measures the average optical power from the DUT TX and requires that it fall in the range
specified. Note that optical losses in the fibers, switch and connectors may be calibrated out by
setting the RX calfactor on the powerbar.
176
Test Sequence
12.5.4 Select_Lambda
This is a GPIB action which sets the switch so that the signal from the DUT TX goes to the
wavemeter. See Section 12.6.1 Failures in GPIB Actions.
12.5.5 TXWavelength
The wavemeter is instructed to measure the wavelength of the light. The OST requires that it fall in
the range specified. This action may fail if the A3301 System Controller is unable to gain control of
the wavemeter. This could occur if the wavemeter is controlled by another GPIB master, or if its
GPIB ID is configured incorrectly or the GPIB cabling is incorrect. A failure is reported as
no_device.
12.5.6 Select_OST
See Section 12.5.2 Select_OST
12.5.7 TXModulation
The OST measures the extinction ratio in dB of the optical signal and requires that it fall in the range
specified. A low extinction ratio would indicate failure of the DUT TX to modulate the signal.
12.5.8 TXFrequency
The OST checks whether its clock recovery is able to lock to the signal from the DUT. A failure
indicates a mismatch in the frequency of the signal, e.g., if the DUT is running at OC192 rate but it
ought to be running at 10GE LAN rate.
12.5.9 TXSynch
The OST checks whether it is able to synch to the signal from the DUT, e.g., it is able to achieve
SONET framing.
12.5.10 InternalSens
The OST measures the sensitivity of its own RX by varying the attenuation between the DUT TX and
its own RX. A value higher than expected indicates a problem with the TX signal quality from the
DUT.
12.5.11 Select_DCA
This is a GPIB action which sets the switch so that the signal from the DUT TX goes to the DCA. See
Section 12.6.1 Failures in GPIB Actions.
12.5.12 DCA_Acquire
The A3301 System Controller instructs the DCA to acquire an eye and measure several parameters
based on the observed waveform. See Section 12.6.1 Failures in GPIB Actions. The action may also
fail if the DCA is not triggered. The results are cached for use in the subsequent tests.
The quantities measured are:
• Crossing Jitter is the peak-to-peak value of the jitter measured at the eye crossing.
• Extinction Ratio is measured to cross check the OST ER measurement.
177
Debug Station
• TxPower is measured to cross check the OST TxPower measurement.
( µ1 – µ0 )
Q = ------------------------
( σ1 – σ0 )
where the numerator is the mean value of the zeros (i=0) or ones (i=1) level of the eye and the
denominator is the corresponding standard deviation.
12.5.13 DCA_Q
The A3301 System Controller requires that the measured Q falls in the range specified.
12.5.14 DCA_XJitter
The A3301 System Controller requires that the measured crossing jitter falls in the range specified.
12.5.15 DCA_ER
The A3301 System Controller requires that the measured ER falls in the range specified. The range is
the same as for the corresponding OST test.
12.5.16 DCA_TxPower
The A3301 System Controller requires that the measured average optical power falls in the range
specified. The range is the same as for the corresponding OST test.
12.5.17 DCA_Eyemask
The A3301 System Controller acquires control of the DCA and runs a mask test using the mask file
specified in the web form. See Section 12.6.1 Failures in GPIB Actions. Failure may occur if the
specified mask file is not available on the DCA, e.g., if the mask file name were misspelled in the web
form entry process. The DUT fails the mask test if the number of mask violations exceeds the number
entered in the web form.
12.5.18 Select_OST
See Section 12.5.2 Select_OST
12.5.19 Loopback Dialog

This provides the opportunity to give instructions on how to put the DUT into loopback mode. For the
case where the DUT does not reframe, e.g., if the DUT is a transponder, this step is redundant. This
dialog pauses processing until the user selects OK.
12.5.20 RxSynch
The OST checks whether it is able to synch to the signal from the DUT, e.g., it is able to achieve
SONET framing. From the point of view of the OST this is the same as the TxSynch test, however for
TxSynch the DUT is reframing while in RxSynch the DUT is in loopback and is not reframing. For
DUT’s which do not reframe (e.g., transponders) the RxSynch and TxSynch tests are the same.
178
Troubleshooting
12.5.21 RxSensitivity
The OST measures the sensitivity of the DUT receiver by varying the attenuation between its own TX
and the DUT RX. It checks that the result falls in the range specified and meets minimal requirements
on the uncertainty and fit quality of the Straight-Line BER™ fit.
12.5.22 RxOverload
The OST measures the overload point and checks that the result falls in the range specified, or verifies
that the DUT runs error-free up to the required overload value.
12.5.23 RxSensSlope
The OST retrieves the slope of the Straight-Line BER™ sensitivity plot obtained previously in
RxSensitivity. It checks that the result lies within the specified range. The expected slope depends on
the type of receiver. A properly functioning PIN device should have a slope near 1.0, while APDs
tend to have lower slopes, in the neighborhood of 0.7.
12.5.24 RxErrFloor
The OST runs for the specified length of time at nominal power and measures the BER averaged over
that time. It checks that the result is less than the specified threshold.
12.5.25 RxOsnrSens
The OST runs a BER vs. OSNR test at the specified power and checks that the measured OSNR
sensitivity is at least as good as the specified threshold. The optical signal to noise ratio is varied
using the built in EDFAs, simulating the amplified spontaneous emission (ASE) noise induced by
optical amplifiers in long haul fiber systems.
NOTE: The OSNR sensitivity depends on the choice of power. The power should be set well
over the sensitivity of the receiver and well below the overload level.
12.5.26 SXPenalty
The OST measures the sensitivity difference with and without an interfering laser signal impairment.
It checks that the absolute value of the difference is less than the specified threshold.
12.5.27 DispPenalty
The OST measures the sensitivity difference of its own RX using the signal from the DUT TX with
and without an intervening spool of fiber. It checks that the difference is less than the specified
threshold. The fiber spool must be attached to the path penalty ports on the front panel of the OST.
The OST takes care of switching the loop in and out of the light path.
12.6 Troubleshooting
12.6.1 Failures in GPIB Actions
In general, any GPIB action may fail if
179
Debug Station
• The GPIB slave device (e.g., switch, wavemeter, DCA) is missing or powered off
• The GPIB slave device or the A3301 System Controller is not correctly cabled to the GPIB bus
• The GPIB ID of the slave device is not correctly configured using the web setup
• A GPIB master other than the A3301 System Controller is controlling the target slave device
A failure in which the System Controller could not recognize or gain control of the slave device is
reported as no_device. Each slave device has additional device-specific and action-specific failure
modes.
12.6.2 Test Reports - Unknown

Diagnostic messages are available using the Status button on the GUI. An Unknown result often
indicates a gross problem. Further insight can be obtained by running the offending test manually. To
do so, return to the signal configuration page, load the appropriate signal configuration using the
Load button and select Start. Proceed to the test page of the offending test and load the appropriate
test configuration using the Load button and select Start. This will duplicate the IntelliScript™ test in
manual mode, which has identical behavior but which will provide additional graphical feedback.
12.7 Debug Station Web Results Access

While running the IntelliScript™ sequence, immediate interactive feedback is available on the A3301
System Controller front panel. The results are archived on the A3301 System Controller and are
available for later analysis via web access.
NOTE: Security is your responsibility. Web access should be restricted to the appropriate
individuals by the usual VPN/firewall tools.
Access to consolidated IntelliScript™ results is available in several formats. Follow the “View or
Download Results” link and choose to index either by timestamp or serial number see Figure 12-8.
Follow the link for any run to view results on simple web pages. The pages can be downloaded to the
machine on which the browser runs, e.g., by right clicking and selecting “Save Page As” or similar
browser function. The results may also be retrieved programmatically by downloading the URLs
using utilities such as fetch or lwp-download available on unix-like systems such as FreeBSD, linux
or SunOS.
In addition the results are stored in a SQL database on the OSTC, which may be accessed via ODBC,
JDBC, or similar standard utilities.
180
Debug Station Web Results Access
FIGURE 12-8: Debug Station Results Access Page
181
Debug Station
182
CHAPTER 13 SCPI Commands
13.1 SCPI Command Set
:IDN?
Description: Returns a string describing the instrument, e.g.
Circadiant OSTC 3301.
Example:
:IDN?
Returns "Circadiant OSTC 3301".
:INPut:TELecom:OST:INPower?
Description: Queries the input power to the A3308. Returned value
is in dBm.
Example:
>> input:telecom:ost:inpower?
[0 15] INPower -10.00
>>
:INPut:TELecom:OST:OMA?
Description: Queries the OMA meter on the RX port. Units are
defined by the :INPut:TELecom:OST:OMA:UNITs command,
and can be in mW or dBm.
Example: None.
:INPut:TELecom:OST:OMA:UNITs <MW|DBM>
Description: Sets or queries the control for the units of the OMA
meter
on the RX port.
Example: None.
:INPut:TELecom:OST:POWer?
183
SCPI Commands
Description: Queries the optical power meter on the RX port. Units are
defined by the :INPut:TELecom:OST:POWer:UNITs command,
and can be in mW or dBm.
Example: None.
:INPut:TELecom:OST:POWer:CALFactor <power>
Description: The query returns the current calibration factor on the
input
side of the OST. The units are can be either dBm or mW,
as defined by :INPut:TELecom:OST:UNITs.
Example:
To retrieve the input calibration factor in dBm:
:INPut:TELecom:OST:POWer:UNITs dBm
:INPut:TELecom:OST:POWer?
:INPut:TELecom:OST:CALSave <filename>
Description: This command saves the RX Calibration factor in the
designated file.
Example:
None
:INPut:TELecom:OST:POWer:MAXSafe <power>
Description: The query returns the current maximum power that can be
safely
shone into the OST.
By sending a value, the power will be set. All powers are in dBm.
Example:
To set the maximum safe power to 10dBm
:INPut:TELecom:OST:POWer:MAXSafe 10
:INPut:TELecom:OST:POWer:UNITs <dBm|mW>
Description: The query returns the current units for measuring the
input power.
By sending a value, the power units will be set.
Example:
To set the input power to mW:
:INPut:TELecom:OST:POWer:UNITs mW
:INPut:TELecom:OST:RXER?
Description: Queries the Extinction Ratio meter on the RX port.
Returns a value in mW. If the input power is too
low, the response is "RXER ---- ", if the monitor
power switch is in the wrong configuration, then
the response is "RXER **** ".
Example: None.
:INPut:TELecom:OST:RXLock?
Description: The query returns the current state of the RX signal lock
for
the selected OST.
184
SCPI Command Set
Returns either "LOCK ON" or "LOCK OFF".
Example:
To detect whether the state of the RX signal is locked or unlocked:
:INST:SELE:ID 1
:INPut:TELecom:OST:RXLock?
:INPut:TELecom:OST:RXMode <?|'SMODE'|'MMODE'|'DEMODE'>
Description: Set or query the RX mode of the A3318. Valid
values are
SMODE Single Mode
MMODE Multi Mode
DEMODE Digital Electric Mode
Example:
>> input:telecom:ost:rxmode MMODE
[0 0]
>> input:telecom:ost:rxmode?
[0 18] OC48_RXMode MMODE
>>
:INPut:TELecom:OST:RXPower <power>
Description: Queries or sets the optical power at the RX governor.
Units are controlled by the INPut:TELecom:OST:POWer:UNITs command.
Example: None.
:INPut:TELecom:OST:SAVe <filename>
Description: Saves maximum power, RX power units and RX wavelength
and OMA to the file.
Example: None
:INPut:TELecom:OST:WAVelength <nm>
Description: The query returns the current RX wavelength.
By sending a value, the wavelength will be set in nanometers.
This value is used to calculate the correct input power, and is
displayed on the OSTC.
Example:
To query the current RX wavelength:
:inst:SELE:id 1
:input:TELecom:OC48:wave?
Returns "INP_WAVELEN 1310"
:INSTrument:ATTach <IpAddress>
Description: Attaches to a running OSTC, without restarting
connections
to existing OSTCs.
Example:
:INST:ATTach a3223135
:INSTrument:BESSel?
Description: Queries the existence of a Bessel filter.
185
SCPI Commands
Returns 1 if Bessel filter is installed.
Example:
%% inst:bessel?
[0 8] BESSEL 1
:INSTrument:BESSel:SET <Integer|?>
Description: Set or query the state of the Bessel filter. The number
1 means
that the Bessel filter is engaged, 0 means it is not engaged.
Example: None.
:INSTrument:CATalog?
Description: The query returns the current serial numbers of the OSTs
connected to this OSTC. Arguments can be "C" for currently
connected OSTs, and "D" for currently disconnected OSTs.
Example:
To list the current OSTs:
inst:CATalog
Returns
1 a6a26143 [0 12] 1 a6a26143
:INSTrument:CLCal <Boolean>
Description: Enable or disable the clock calibration spigot.
Example: None.
:INSTrument:HJITter <UI> <MHz> <type>

Description: To set or recall the Horizontal Jitter. UI is in unit
intervals, and MHz is in MHz. The type can be
-1 to switch off jitter
0 to use single point analog
1 to use saw wave digital
2 to sweep
Example: None.
:INSTrument:INIT
Description: Reloads the calibration files after a calibration has
been performed.
Example: None.
:INSTrument:LICense
Description: Queries license database for licenses installed on the
OST. Returns 0 if license is installed, 1074 if license is not
installed.
Example:
%% inst:LICense?
[0 47] {Stressed Eye} 0 {OSNR} 0 {Protocol} 0 {OTN} 0
:INSTrument:LOWSpeed:FREQuency <kHz>
186
SCPI Command Set
Description: Sets or queries the Low Speed laser modulation frequency

in kHz.
Example: None.
:INSTrument:LOWSpeed:MODulation <integer>
Description: Sets the sinusoidal modulation of the Low Speed Laser.
No query is available. The allowed set value is between
0 and FFFF (hex).
Example: None.
:INSTrument:LOWSpeed:SET <0|1>
Description: The query returns the current state of the Low Speed
laser.
By sending a value, the Low Speed laser can be switched on or off.
Example:
To turn on the Low Speed laser:
:INST:SELE:ID 1
:INST:LOWSpeed:SET 1
:INSTrument:OPTics:LIMits?
Description: Queries optical capabilities of the OST.
TXPO TX Power
TXER TX Extinction Ratio
OSNR Optical Signal to Noise Ratio
OMAB OMA Bypass
MODL Modulation Laser Power
GLPO 10GL Power
GLOM 10GL OMA
GEPO 10GE Power
GEOM 10GE OMA
GLUI 10GL Limiting horizontal jitter UI at high frequency
GEUI 10GE Limiting horizontal jitter UI at high frequency
MUIn Maximum Unit Interval for jitter at frequencies 40kHz, 100kHz,
etc.
Example:
%% inst:optics:limits?
[0 214] TXPO 9.80 TXER 12.24 OSNR 52.86 OMAB 1.85 MODL 0.00 GLPO 2.70
GLOM 2.00 GEPO 2.20 GEOM 0.90 GLUI 0.12 GEUI 0.07 MUI0 7.94 MUI1 9.17
MUI2 12.28 MUI3 12.80 MUI4 9.13 MUI5 6.00 MUI6 3.07 MUI7 0.95 MUI8
0.32 MUI9 0.10
:INSTrument:OPTics:LIMits:105Extend?
Description: Queries the stressed eye parameters for 10.5 GB/s
Extended.
Example:
%% inst:optics:limits:105extend?
[0 172] EOSNR 0 ENAHjitter 1 TYPHjitter single FRQHjitter 40
AMPHjitter 0.12 ENAVjitter 1 TYPVjitter sine FRQVjitter 100.00
AMPVjitter 9.20 EEXTinction 1 EXTinction 3.05 EFILter 1
:INSTrument:OPTics:LIMits:105Long?
Description: Queries the stressed eye parameters for 10.5GB/s Long.
187
SCPI Commands
Example:
%% inst::optics:limits:105long?
:INSTrument:OPTics:LIMits:10GExtend?
Description: Queries the stressed eye parameters for 10.3GB/s
Extended.
Example:
:instrument:optics:limits:10GExtend?
AMPVjitter 9.20 EEXTinction -1 EXTinction 3.38 EFILter 1
:INSTrument:OPTics:LIMits:10GLong?
Example:
:instrument:optics:limits:10GLong?
AMPHjitter 0.12 ENAVjitter 1
TYPVjitter sine FRQVjitter 100.00 AMPVjitter 12.50 EEXTinction 1
EXTinction 3.90 EFILter 1
:INSTrument:OPTics:LIMits:10GShort?
Description: Queries the stressed eye parameters for 10.3GB/d Short
Range.
Example:
>> instrument:optics:limits:10gshort?
[0 176] EOSNR 0 ENAHjitter 1 TYPHjitter single FRQHjitter 40.00
:INSTrument:OPTics:LIMits:995Extend?
Description: Queries the stressed eye parameters for 9.95GB/s
Extended.
Example:
:instrument:optics:limits:995extend?
AMPHjitter 0.12 ENAVjitter 1 TYPVjitter sine
FRQVjitter 100.00 AMPVjitter 9.20 EEXTinction 1 EXTinction 3.95
EFILter 1
:INSTrument:OPTics:LIMits:995Long?
Example:
:instrument:optics:limits:995long ?
AMPHjitter 0.07 ENAVjitter 1 TYPVjitter sine
FRQVjitter 100.00 AMPVjitter 9.20 EEXTinction 1 EXTinction 3.95
188
SCPI Command Set
EFILter 1
:INSTrument:OPTics:LIMits:TXRates?
Description: Queries the list of supported transmit rates.
Example:
>> inst:optics:limits:txrates
[0 48] 2 15 13 5 17 23 8 19 21 3 16 14 6 18 24 9 20 22
:INSTrument:OPTics:LIMits:UIMaxlist:J103ui?
Description: Returns the maximum jitter amplitudes for this OST at
10.3GB/sec for 0.04MHz to 40MHz.
Example:
:instrument:optics:limits:UIMaxlist:J103ui?
[0 53] 7.53 9.33 10.86 12.43 11.19 7.24 4.58 1.39 0.45 0.07
Example:
[0 53] 7.69 9.52 11.09 12.70 11.43 7.40 4.67 1.42 0.46 0.08
Example:
:instrument:optics:limits:UIMaxlist:J107ui ?
[0 55] 8.66 11.36 14.08 15.44 13.43 10.22 6.38 1.79 0.54 0.1
Example:
[0 54] 8.11 10.05 11.70 13.40 12.06 7.80 4.93 1.50 0.48 0.08
Description: Queries the maximum jitter amplitudes for this OST at
Example:
>> INSTrument:OPTics:LIMits:UIMaxlist:J113ui?
[0 53] 0.15 0.80 2.11 7.43 10.35 12.61 9.58 9.87 10.02 8.23
Description:Returns the maximum jitter amplitudes for this OST at
Example:
189
SCPI Commands
[0 53] 7.31 9.05 10.54 12.07 10.87 7.03 4.44 1.35 0.44 0.07
Example:
[0 52] 7.94 9.17 12.28 12.80 9.13 6.00 3.07 0.95 0.32 0.10
Example:
[0 52] 7.94 9.17 12.28 12.80 9.13 6.00 3.07 0.95 0.32 0.10
:INSTrument:OPTics:LOOPback <Integer|?>
Description: Sets or queries the status of internal loop-back.
Example:
:instrument:optics:LOOPback ?
[0 11] LOOPback 1
:INSTrument:OPTics:RECall <Integer>
Description: Reloads optical settings which were
stored with a previous command.
Example:
%% inst:optics:store 2
[0 0]
%% inst:optics:recall 2
[0 0]
:INSTrument:OPTics:STORe <Integer>
Description: Saves the current optical settings of the
OST, which can be recalled at a later time.
Example:
%% inst:optics:store 2
[0 0]
%% inst:optics:recall 2
[0 0]
:INSTrument:OSNR?
Description: Queries whether the unit supports setting the TX OSNR.
Returns 1 if OSNR is supported, 0 if not.
Example: None.
:INSTrument:OSTType?
Description: The query returns the type of OST currently selected.
190
SCPI Command Set
Example:
To query the type of OST:
:INST:SELE:ID 1
:INST:OSTTYPE
Returns [0 13] OSTType OC48
:INSTrument:OTF:STEP <Number-Steps>
Description: Moves the Optical Tunable Filter.
Example:
For calibration use only.
:INSTrument:OTF:TUNe
Description: Runs a tune on the OTF. Leaves the wiper at the
maximum TX Power value. Limits on the wiper value
are kept in OTF.CFG.
Example:
:INSTrument:PRBSonly?
Description: Queries whether this OST can support PRBS traffic only.
Returns 1 if only PRBS patterns are supported.
Example:
>> INSTrument:PRBSonly?
[0 10] PRBSonly 0
:INSTrument:RELease <number>
Description: Releases the specified OST for use by another
controller.
Example:
To connect to an OST, release, and list currently connected devices:
:INST:SELE:ID 1
:INST:CATalog C
Returns 1 a6a26143 [0 12] 1 a6a26143
:INST:REL 1
:INST:CATalog C
Returns [0 0]
:INSTrument:SELect:ID <number>
Description: Selects the OST by number, for the proceeding SCPI
commands.
Example:
To list and set available OSTs:
:INST:CATalog?
:INST:SELE:ID 1
:INSTrument:SELect:INETname <IpAddress>
Description: Selects the OST by serial number, for the proceeding SCPI
commands.
Example:
191
SCPI Commands
To list and set available OSTs:

:INST:CATalog?
:INST:SELE:INET a3223135
:INSTrument:SWITch:EDFa <0|1>
Description: Switches the EDFAs out (1) or in (0) of the optical
circuit.
The query returns the last setting.
Example:
:INST:SWIT:EDFA 1
Bypasses the amplifiers from the TX side.
:INSTrument:SWITch:ER <0|1>
Description: Switches the Extinction Ratio circuit to TX (0) or RX
(1).
The query returns the last setting.
Example:
:INST:SWIT:ER 0
Switches the ER monitor to TX.
:INSTrument:SWITch:PPL <0|1>
Description: The query returns the state of the Path Penalty Loop.
Switches the Path Penalty Loop fiber out (0) or in (1)
of the light path between the input connector and the
internal receiver.
Example:
Switch the Path Penalty Loop fiber in to the light path:
INST:SWITch:PPL 1
:INSTrument:SWITch:RX <0|1>
Description: Switches the customers RX spigots in (1) or out (0) of
the optical circuit. The query returns the last setting.
Example:
:INST:SWIT:RX 1
Connects the customers OTN decoder transponder into the OST.
:INSTrument:SWITch:TX <0|1>
Description: Switches the customers TX spigots in (1) or out (0) of
the
optical circuit. The query returns the last setting.
Example:
:INST:SWIT:TX 1
Connects the customers OTN encoder transponder into the OST.
:INSTrument:VERSion:OST?
Description: The query returns the current software version and build
date of the
Optical Standards Tester.
Example:
:inst:VERSion:OST?
192
SCPI Command Set
Returns "[0 36] 2.30 Mon May 13 20:07:55 EDT 2002".
:INSTrument:VERSion:OSTC?
Description: The query returns the current software version and build
date of the
Optical Standards Test Controller.
Example:
:inst:VERSion:OSTC?
Returns "[0 36] 2.30 Mon May 13 20:07:55 EDT 2002".
:INSTrument:VERSion:XLTR?
Description: Returns the firmaware version of the A3318 850 XLTR
if it is connected.
Example:
>> INSTrument:VERSion:XLTR?
[0 59] Circadiant Systems. A3318 ofc2005+ 20050223213306 rev 0:0:0
>>
:INSTrument:VJITter <ILPR> <MHz> <type>

Description: To set or recall the Vertical Jitter. ILPR is the
interfering
laser power ratio in dB, and MHz is the frequency in MHz.
The type is
-1 for OFF
0 for sinusoidal jitter
1 for square wave jitter
Example: None.
:INSTrument:XLTR:CONNect <Integer|?>
Description: Sets or queries the state of the connection to the
850 translator module. The query returns a 1 if the module is
connected
and a 0 if not connected. Setting a 0 will disconnect the 850 module on
the next restart, and a 1 will reconnect.
Example: None.
:INSTrument:XLTR:NAMe?
Description: Queries the name of the 850nm translator module
which was calibrated with this OST.
Example: None.
:IQ:BUFFer <Buffer-Number>
Description: The command sets or returns the current buffer number.
Example: None.
:IQ:INTScript:CALFile <Calibration-Name>
Description: Loads calibration identified by "Calibration-Name" for
the
193
SCPI Commands
set of Intelliscript tests. The query returns the name of

the current calibration, or NULL if the regular calibration
is being used.
Example: None.
:IQ:INTScript:CODe <CodeNumber>
Description: Set or queries the code number saved with the list of
tests in Intelliscript.
Example: None.
:IQ:INTScript:COMMent <Comment-String>
Description: Sets and queries the comment which is saved with a set
of tests in
Intelliscript.
Example: None.
:IQ:INTScript:CONFig:DELete <Filename>
Description: Deletes the current configuration from the database.
Example:
%% iq:intscript:config:save INTScript/streets/test.par
[0 0]
%% iq:intscript:config:list?
[0 66] 0 "INTScript/streets/lastused.par" 1
"INTScript/streets/test.par"
%% iq:intscript:config:delete INTScript/streets/test.par
[0 0]
[0 35] 0 "INTScript/streets/lastused.par"
:IQ:INTScript:CONFig:EXISt <Filename>
Description: Queries if a configuration files exits or not.
Returns TRUE or FALSE.
Example:
%% iq:intscript:config:exist INTScript/streets/lastused.par
[0 11] EXISt TRUE
%% iq:intscript:config:exist INTScript/streets/test.par
[1069 12] EXISt FALSE
:IQ:INTScript:CONFig:LIST?
Description: Lists existing intelliscript configuration files.
Example:
:IQ:INTScript:CONFig:LOAD <Filename>
Description: Loads the entry into the database as the
current configuration.
194
SCPI Command Set
Example:
%% iq:intscript:config:load INTScript/streets/lastused.par
[0 0]
:IQ:INTScript:CONFig:RST
Description: Clears the current intelliscript configuration.
Example:
%% iq:intscript:config:rst
[0 0]
:IQ:INTScript:CONFig:SAVe <Filename>
Description: Saves current configuration to database.
Example:
%% iq:intscript:config:save INTScript/streets/test.par
[0 0]
[0 66] 0 "INTScript/streets/lastused.par" 1
"INTScript/streets/test.par"
%% iq:intscript:config:delete INTScript/streets/test.par
[0 0]
:IQ:INTScript:CURRent ?
Description: Returns the current test number (0 through 50) which is
running on the OST.
Example:
IQ:INTScript:CURRent ?
Returns -> CURRENT 3
:IQ:INTScript:EMAil <useraccount@computer.com>
Description: Sets or queries the email account to which error messages
are sent if
a test failure occurs.
Example: None.
:IQ:INTScript:FAULt <0|1>
Description: Set or recall the Stop on Fault feature in Intelliscript.
If value is 0 the Intelliscript will continue if an action
fails. If value is 1, then if an action fails, the remaining
tests will be marked as "ABORTED", and the script will
return immediately without executing subsequent actions.
Example: None.
:IQ:INTScript:NTESt?
Description: Queries the number of tests in the schedule list.
Example: None.
195
SCPI Commands
:IQ:INTScript:RESEt
Description: Resets the OST to prepare it for the next Intelliscript
run.
Example: None.
:IQ:INTScript:RUN <RunNumber>
Description: Sets or queries the run number associated with an
Intelliscript run.
Example: None.
:IQ:INTScript:SERial <serialNumber>
Description: Sets or queries the serial number associated with the
list of Intelliscript tests.
Example: None.
:IQ:INTScript:SETup <Integer|?>
Description: Set or query the next intelliscript test.
Example:
%% iq:intscript:setup?
[0 228] SETup 0 ACTive 0 DOSave 0 PRINt 1 PBReak 0 TEST
"setCurrentTraffic" TCONfig "default.par" SIGFile
"Signal_Conf/OC192_common/SONET/Unframed/default.cfg" USRParam "."
CMPWith "NULL" TNAMe "Define Traffic" DEViceid "NULL" EXPand 1
%% iq:intscript:setup 1
[0 0]
%% iq:intscript:setup?
[0 227] SETup 1 ACTive 0 DOSave 0 PRINt 0 PBReak 0 TEST
"setCurrentTraffic" TCONfig "default.par" SIGFile
"Signal_Conf/OC192_common/SONET/Unframed/default.cfg" USRParam "."
CMPWith "NULL" TNAMe "Intelliscript" DEViceid "NULL" EXPand 0
:IQ:INTScript:SETup:ACTive <0|1>
Description: Boolean to activate or deactivate a particular test
in an Intelliscript schedule.
Example: None.
:IQ:INTScript:SETup:CMPWith <Result-Name>
Description: Compares the test with the previous values in file
"Result-Name". The query returns the name of the
comparison results.
Example: None.
:IQ:INTScript:SETup:DEViceid <String|?>
Description: Set or query the device id for an External Instrument
Test.
Example: None.
196
SCPI Command Set
:IQ:INTScript:SETup:DOSave <0|1>
Description: Boolean to specify if the results will be saved
or not for a particular test.
Example: None.
:IQ:INTScript:SETup:EXPand <Integer|?>
Description: Set or query the flag which controls whether
the OSTC should display the expanded test.
Example: None.
:IQ:INTScript:SETup:PBReak <0|1>
Description: Boolean to indicate if a page break should be
added after this test in the results print out.
Example: None.
:IQ:INTScript:SETup:PRINt <0|1>
Description: Boolean for whether test results should be printed.
Example: None.
:IQ:INTScript:SETup:SIGFile <SignalFile>
Description: Sets or queries the signal file to be run with this test.
Example: None.
:IQ:INTScript:SETup:TCONfig <configurationName>
Description: Sets or queries the configuration parameters to be run
with this test.
Example: None.
:IQ:INTScript:SETup:TEST <Test-Type>
Description: Specifies or queries the type of test, e.g. Sensitivity,
path-penalty, SXPenalty, TXPower, etc.
Example: None.
:IQ:INTScript:SETup:TNAMe <Test-Name>
Description: Set or query a name to be associated with a name for
the test. The name can be used by the customer for
identification purposes.
Example: None.
:IQ:INTScript:SETup:USRParam <CustomerParameters>
Description: Sets or queries a parameter string which will be added to
the command line when starting a test. Used, for instance,
in the GPIB test.
Example: None.
197
SCPI Commands
:IQ:INTScript:STATus?
Description: Returns the current status of the running Intelliscript.
For each test, the command will list the name, parameter
configuration, signal configuration and status.
Example: None.
:IQ:INTScript:STOP
Description: Stops all the running intelliscript tests.
Example:
%% iq:ints:stop
[0 0]
:IQ:INTScript:TAG <String|?>
Description: Sets or queries the identifying tag saved with
each set of tests.
Example: None.
:IQ:SELFcal:ERRCode?
Description: Returns the error code of the previous self calibration.
Example: None.
:IQ:SELFcal:EXSLastused?
Description: Queries whether a self-calibration has already been
executed for this OST.
Example: None.
:IQ:SELFcal:FACTory
Description: Loads the original calibration constants which were
shipped with
the OST.
Example: None.
:IQ:SELFcal:LASTcal <New-Calibration>
Description: Loads the calibration labeled "New-Calibration" as the
current calibration.
Example: None.
:IQ:SELFcal:LISTcal?
Description: Queries the list of self calibrations.
Example:
%% iq:selfcal:listcal
[0 12] test1 test2
:IQ:SELFcal:MANual <New-Calibration>
198
SCPI Command Set
Description: Creates a new calibration names New-Calibration, from

the
previous self-calibration.
Example: None.
:IQ:SELFcal:MSG?
Description: Returns message from the current or last self
calibration.
Example: None.
:IQ:SELFcal:PERCent?
Description: Returns an estimate of the percentage completion of the
running
self calibration.
Example: None.
:IQ:SELFcal:RESet
Description: Initializes variables in SELFCAL subsystem.
Example: None.
:IQ:SELFcal:STARt
Description: Starts the self calibration process.
Example: None.
:IQ:SELFcal:STOP
Description: Halts the running self calibration process.
Example: None.
:IQ:TestType:APPLy
Description: Applies new settings to the running test.
Example: None.
:IQ:TestType:CONFig:ADVanced:BASic:BERD <Float|?>
Description: Bit Error Rate at which the final measurement will
be quoted.
Example: None.
:IQ:TestType:CONFig:ADVanced:BASic:BESTtime <Float|?>
Description: Number of minutes within which the test is requested to
run
for IntelliTime.
Example: None.
:IQ:TestType:CONFig:ADVanced:BASic:CODe <String|?>
199
SCPI Commands
Description: Sets or queries the product code associated with this

test.
Example: None.
:IQ:TestType:CONFig:ADVanced:BASic:COMMent <String|?>
Description: Sets or queries the comment associated with this test.
Example: None.
:IQ:TestType:CONFig:ADVanced:BASic:DISType
<?|'AvgPwr'|'OMA'|'AvgPwrSigLaser'>
Description: Set or query the type of variable for the display of the
X axis.
Example: None.
:IQ:TestType:CONFig:ADVanced:BASic:EFAStfail <Boolean|?>
Description: Set or query the flag which will stop the test after
running fast scan.
Example: None.
:IQ:TestType:CONFig:ADVanced:BASic:INTMaxtime <Float|?>
Description: Sets or queries the maximum time that the
Intellipass version of the test will run.
Example: None.
:IQ:TestType:CONFig:ADVanced:BASic:INTPowerratio <Float|?>
Description: Set or query the interfering power ratio in dB.
Example: None.
:IQ:TestType:CONFig:ADVanced:BASic:ISCKed <Boolean|?>
Description: Sets or queries the boolean to signify which signal
configurations will be run with this test.
Example: None.
:IQ:TestType:CONFig:ADVanced:BASic:LERR <Float|?>
Description: Sets or queries the lower bit error rate to define
the range over which the test should be run.
Example: None.
:IQ:TestType:CONFig:ADVanced:BASic:LTYPe <Integer|?>
Description: Set or query the method for defining the Y axis
during an automatic measurement. LTYPe 0 will use
the error rate, LTYPe 1 will use power.
Example: None.
200
SCPI Command Set
:IQ:TestType:CONFig:ADVanced:BASic:MODFrequency <Float|?>
Description: Set or query the modulation frequency (kHz).
Example: None.
:IQ:TestType:CONFig:ADVanced:BASic:P1ENd <Float|?>
Description: End point of the first measurement of the test.
Example: None.
:IQ:TestType:CONFig:ADVanced:BASic:P1STart <Float|?>
Description: Starting point of the first measurement of the test.
Example: None.
:IQ:TestType:CONFig:ADVanced:BASic:P2ENd <Float|?>
Description: End point of the second measurement of the test.
Example: None.
:IQ:TestType:CONFig:ADVanced:BASic:P2STart <Float|?>
Description: Starting point of the second measurement of the test.
Example: None.
:IQ:TestType:CONFig:ADVanced:BASic:PVALue <Float|?>
Description: Sets or queries the pass criterion of the value
measure by the test.
Example: None.
:IQ:TestType:CONFig:ADVanced:BASic:RST
Description: Initializes the parameters on the
"Basic" tab on the test setup page to reasonable defaults.
Example: None.
:IQ:TestType:CONFig:ADVanced:BASic:SERNum <String|?>
Description: Set or query the serial number for the Device Under Test.
Example: None.
:IQ:TestType:CONFig:ADVanced:BASic:SGERror
<?|'B1'|'B2'|'B3'|'M1'|'PRBS'|'EJITT'|'FCS'|'PCS'|'ETHSKIP'|'BIPSM'|'BIPP
M'|'BIPTCM1'|'BIPTCM2'|'BIPTCM3'|'BIPTCM4'|'BIPTCM5'|'BIPTCM6'|'
BEISM'|'BEIPM'|'BEITCM1'|'BEITCM2'|'BEITCM3'|'BEITCM4'|'BEITCM
5'|'BEITCM6'|'FECCORRBIT0'|'FECCORRBIT1'|'FECCORRBIT'|'FECUN
CORR'|'FECTOTBITERR'>
Description: Defines a list of error types, one for each signal file
as displayed on the run control screen.
Example: None.
201
SCPI Commands
:IQ:TestType:CONFig:ADVanced:BASic:SIGFile <filename1 filename2 ...|?>

Description: Defines a list of Signal Configuration files as
displayed on the run control screen.
Example: None.
:IQ:TestType:CONFig:ADVanced:BASic:TEST <?|'AUTO-POWER'|'AUTO-
BER'|'INTELLIPASS'|'INTELLITIME'|'FASTSCAN'>
Description: Set or query the test type.
Example: None.
:IQ:TestType:CONFig:ADVanced:BASic:TXPower <Float|?>
Description: Set or query the transmit power from the OST for this
test.
Example: None.
:IQ:TestType:CONFig:ADVanced:BASic:UERR <Float|?>
Description: Sets or queries the upper bit error rate for the
Y-axis.
Example: None.
:IQ:TestType:CONFig:ADVanced:FASTscan:APPX <Float|?>
Description: Sets or queries the approximate value of the
measurement.
When set correctly, this value will shorten the time to run the test.
Example: None.
:IQ:TestType:CONFig:ADVanced:FASTscan:COARse <Integer|?>
Description: Set or query the flag which controls whether a coarse
fast scan should be performed before a test.
Example: None.
:IQ:TestType:CONFig:ADVanced:FASTscan:COARse:HIGH <Float|?>
Description: Set or query the coarse scan high power, in dB.
Example: None.
:IQ:TestType:CONFig:ADVanced:FASTscan:COARse:LOW <Float|?>
Description: Set or query the low limit for a coarse fast scan (in
dB).
Example: None.
:IQ:TestType:CONFig:ADVanced:FASTscan:COARse:OVERride <Integer|?>
Description: Set or query the flag to control whether the HIGH, LOW
and STEP
202
SCPI Command Set
size should take affect.
Example: None.
:IQ:TestType:CONFig:ADVanced:FASTscan:COARse:QKAStep <Float|?>
Description: Sets or queries the Quick Abort step size (in dB).
Example: None.
:IQ:TestType:CONFig:ADVanced:FASTscan:COARse:SELaborts <Integer|?>
Description: Set or query the flag which controls quick abort
functionality.
Example: None.
:IQ:TestType:CONFig:ADVanced:FASTscan:COARse:STEP <Float|?>
Description: Set or query the coarse scan step size (in dB).
Example: None.
:IQ:TestType:CONFig:ADVanced:FASTscan:DEFSlope <Float|?>
Description: Set or query the default slope use in the Fast Scan.
Example: None.
:IQ:TestType:CONFig:ADVanced:FASTscan:DEGappx <Float|?>
Description: Set or query the expected sensitivity for the Fast Scan
(in dB).
Example: None.
:IQ:TestType:CONFig:ADVanced:FASTscan:FINe <Integer|?>
Description: Set or query the flag which controls whether a fine
scan should be performed.
Example: None.
:IQ:TestType:CONFig:ADVanced:FASTscan:FINe:ISSKipdegraded
<Integer|?>
Description: Set of query the flag which skips the Fine Fast Scan on
the
degraded part of the test.
Example: None.
:IQ:TestType:CONFig:ADVanced:FASTscan:FINe:OVERride <Integer|?>
Description: Set or query the flag which controls whether the default
values for range, step and padding should be overridden.
Example: None.
:IQ:TestType:CONFig:ADVanced:FASTscan:FINe:PAD <Float|?>
203
SCPI Commands
Description: Set or query the power range to extend a fine scan

if fails to find a region with bit errors.
Example: None.
:IQ:TestType:CONFig:ADVanced:FASTscan:FINe:RANGe <Float|?>
Description: Set or query the range in dB, over which the fine scan
will be run.
Example: None.
:IQ:TestType:CONFig:ADVanced:FASTscan:FINe:STEP <Float|?>
Description: Set or query the step size in dB of the fine scan.
Example: None.
:IQ:TestType:CONFig:ADVanced:FASTscan:FINe:USELastdata <Integer|?>
Description: Set or query the flag which controls whether to use data
from
the last test to estimate correct values for the fine scan.
Example: None.
:IQ:TestType:CONFig:ADVanced:FASTscan:LOWerslope <Float|?>
Description: Set or query the lowest possible slope when running Fast
Scan.
Example: None.
:IQ:TestType:CONFig:ADVanced:FASTscan:OVERride <Integer|?>
Description: Set or query the flag to control overriding Fast Scan,
and
use binary scan only.
Example: None.
:IQ:TestType:CONFig:ADVanced:FASTscan:RST
Description: Initializes the parameters on the "FastScan Control"
tab on the test setup page to reasonable defaults.
Example: None.
:IQ:TestType:CONFig:ADVanced:FASTscan:SLOPe <Integer|?>
Description: Set or query the flag which controls whether to override
the values for the minimum and maximum values of the
slope used in Fast Scan.
Example: None.
:IQ:TestType:CONFig:ADVanced:FASTscan:STEP <Integer|?>
Description: Set or query the flag which controls whether Step Scan
should be performed.
204
SCPI Command Set
Example: None.
:IQ:TestType:CONFig:ADVanced:FASTscan:STEP:HIGH <Float|?>
Description: Set or query the highest power in dBm for a step scan.
Example: None.
:IQ:TestType:CONFig:ADVanced:FASTscan:STEP:LOW <Float|?>
Description: Set or query the lowest power for a Step Scan (in dBm).
Example: None.
:IQ:TestType:CONFig:ADVanced:FASTscan:STEP:OVERride <Integer|?>
Description: Step or query the flag which controls whether to override
defaults
for STEP, LOW and HIGH.
Example: None.
:IQ:TestType:CONFig:ADVanced:FASTscan:STEP:STEP <Float|?>
Description: Set or query the estimated size of the step in the
Step Scan.
Example: None.
:IQ:TestType:CONFig:ADVanced:FASTscan:STEP:ULTStep <Float|?>
Description: Set or query the granularity in power range used to
investigate the Step (in dB).
Example: None.
:IQ:TestType:CONFig:ADVanced:FASTscan:UPPerslope <Float|?>
Description: Set or query the value of the maximum possible slope used
in the
Fast Scan.
Example: None.
:IQ:TestType:CONFig:ADVanced:FITuncert:ALARm <Boolean|?>
Description: Set or query the flag which controls whether an audible
alarm will sound when a test fails.
Example: None.
:IQ:TestType:CONFig:ADVanced:FITuncert:B1Fit <Float|?>
Description: Set or query the maximum Error Rate used for B1 errors.
Example: None.
205
SCPI Commands
Example: None.
Example: None.
:IQ:TestType:CONFig:ADVanced:FITuncert:BEIPm <Float|?>
Description: Set or query the maximum Error Rate used for BEIPM type
errors.
Example: None.
:IQ:TestType:CONFig:ADVanced:FITuncert:BEISm <Float|?>
Description: Set oq query the maximum Error Rate used for BEISM
errors.
Example: None.
:IQ:TestType:CONFig:ADVanced:FITuncert:BIPPm <Float|?>
Description: Set or query the maximum Error Rate used for BIPPM
errors.
Example: None.
:IQ:TestType:CONFig:ADVanced:FITuncert:BIPSm <Float|?>
Description: Set or query the maximum Error Rate used for BIPSM
errors.
Example: None.
:IQ:TestType:CONFig:ADVanced:FITuncert:CHI1 <Float|?>
Description: Set or query the pass value for the chi squared
value of the fit. Tests will not pass this criteria if they have a poor
fit quality. The test is enabled with
:IQ:TestType:CONFig:ADVanced:FITuncert:CHI1:ENABle 1
Example: None.
:IQ:TestType:CONFig:ADVanced:FITuncert:CHI1:ENABle <Boolean|?>
Description: Set or query whether the Chi-squared quality of the
straight-line fit(s) should be used to determine if the test passed.
Example: None.
:IQ:TestType:CONFig:ADVanced:FITuncert:CHI2 <Float|?>
Description: Set or query the pass value for the chi squared
value of the second fit. The pass criteria is enabled with
:IQ:TestType:CONFig:ADVanced:FITuncert:CHI1:ENABle. Tests will not
pass
this criteria if they have a poor fit quality.
Example: None.
206
SCPI Command Set
:IQ:TestType:CONFig:ADVanced:FITuncert:EMAil <Boolean|?>
Description: Enable or disable a flag to email a screen shot if
the test fails. The OSTC must be correctly configured on
the network for this to happen, and a valid email server needs to be
configured as well. Please check the "Set IP Address" and "E-Mail
Configuration" icons on the ADMIN screen.
Example: None.
:IQ:TestType:CONFig:ADVanced:FITuncert:ETHSkip <Float|?>
Description: Set or query the maximum Error Rate used for ETHSkip
errors.
Example: None.
:IQ:TestType:CONFig:ADVanced:FITuncert:FCSFit <Float|?>
Description: Set or query the maximum Bit Error Rate used for FCS
errors.
Example: None.
:IQ:TestType:CONFig:ADVanced:FITuncert:FECCorrected:BIT <Float|?>
Description: Set or query the maximum error rate used for
Forward Error Correction errors (total inserts and omits).
Example: None.
:IQ:TestType:CONFig:ADVanced:FITuncert:FECCorrected:BIT0 <Float|?>
Description: Set or query the maximum error rate used for Forward
Error
Correction insert errors (0 is misinterpreted as a 1).
Example: None.
:IQ:TestType:CONFig:ADVanced:FITuncert:FECCorrected:BIT1 <Float|?>
Description: Set or query the maximum error rate used for
Foreward Error Correction omit errors (1 is misinterpreted as a 0).
Example: None.
:IQ:TestType:CONFig:ADVanced:FITuncert:FECUncorrected <Float|?>
Description: Set or query the maximum Error Rate used for FEC
(uncorrected) errors.
Example: None.
:IQ:TestType:CONFig:ADVanced:FITuncert:FINConfidence <Float|?>
Description: set or query the confidence level used to determine
whether
a fit is good or not.
Example: None.
207
SCPI Commands
:IQ:TestType:CONFig:ADVanced:FITuncert:HIOSnr <Boolean|?>
Description: Set or query flag which controls whether the
Hi-OSNR pass criteria are used in the IsoBER test.
Example: None.
:IQ:TestType:CONFig:ADVanced:FITuncert:HIPower <Boolean|?>
Description: Set or query the flag which controls whether the Hi-Power
parameters are used in the IsoBer test.
Example: None.
:IQ:TestType:CONFig:ADVanced:FITuncert:HOOSnr <Float|?>
Description: Set or query the value of the passing OSNR for the
Hi-OSNR test in IsoBER.
Example: None.
:IQ:TestType:CONFig:ADVanced:FITuncert:HOPower <Float|?>
Description: Set or query the Power used for the passing criteria
in the Hi-OSNR test in IsoBER.
Example: None.
:IQ:TestType:CONFig:ADVanced:FITuncert:HPOSnr <Float|?>
Description: Set or query the OSNR used as a pass criteria in the
Hi-Power test in IsoBER.
Example: None.
:IQ:TestType:CONFig:ADVanced:FITuncert:HPPower <Float|?>
Description: Set or query the Power used as a passing criteria in
the Hi-Power test in IsoBER.
Example: None.
:IQ:TestType:CONFig:ADVanced:FITuncert:INDConfidence <Float|?>
Description: Set or query the confidence level used to determine
whether
an individual error rate measurement is used in the overall fit.
Example: None.
:IQ:TestType:CONFig:ADVanced:FITuncert:M1Fit <Float|?>
Description: Set or query the maximum Bit Error Rate used for M1
errors.
Example: None.
:IQ:TestType:CONFig:ADVanced:FITuncert:PRBSfit <Float|?>
Description: Set or query the maximum Bit Error Rate used for PRBS
208
SCPI Command Set
errors.
Example: None.
:IQ:TestType:CONFig:ADVanced:FITuncert:PUNCertain <Float|?>
Description: Set or query the "Uncertainty" value for a passing
criteria. Test results which have a large uncertainties will fail this
criteria. The criteria is used when
:IQ:TestType:CONFig:ADVanced:FITuncert:PUNCertain:ENABle is set to
1.
Example: None.
:IQ:TestType:CONFig:ADVanced:FITuncert:PUNCertain:ENABle
<Boolean|?>
Description: Enable or disable the "Uncertainty" pass criteria.
A test with a bad projected test value will fail this criteria.
Example: None.
:IQ:TestType:CONFig:ADVanced:FITuncert:RST
Description: Initializes the parameters on the
"Fit, Uncertainty, Pass Criteria" tab on the test setup
page to reasonable defaults.
Example: None.
:IQ:TestType:CONFig:ADVanced:FITuncert:STATtype <Integer|?>
Description: Set or query the type of data used to calculate the
uncertainty
in the final fit.
0 Statistical only.
1 Systematic only.
2 Both statistical and systematic.
Example: None.
:IQ:TestType:CONFig:ADVanced:FITuncert:TOTBiterr <Float|?>
Description: Set or query the maximum error rate used for TOTBiterr
errors.
Example: None.
:IQ:TestType:CONFig:ADVanced:INITialization:EJITter <Boolean|?>
Description: Set or query the flag which controls the Jitter pretest.
If set,
the horizontal jitter is swept through full range, and the value
which causes highest Bit Errors is used to execute the test.
Example: None.
:IQ:TestType:CONFig:ADVanced:INITialization:PRETest <Boolean|?>
Description: Set or query the flag which controls whether a pretest is
performed.
209
SCPI Commands
Example: None.
:IQ:TestType:CONFig:ADVanced:INITialization:PRTPower <Float|?>
Description: Set or query the power (in dBm) for the pretest
measurement.
Example: None.
:IQ:TestType:CONFig:ADVanced:INITialization:PRTTime <Float|?>
Description: Set or query the time for the pretest measurement (in
seconds).
Example: None.
:IQ:TestType:CONFig:ADVanced:INITialization:RST
Description: Initializes variables under the initialization
tab on the test setup page to reasonable defaults.
Example: None.
:IQ:TestType:CONFig:ADVanced:MODe:EPOSttest <Integer|?>
Description: Set or query the flag which controls whether a Post Test
error floor check is made in Intellipass mode.
Example: None.
:IQ:TestType:CONFig:ADVanced:MODe:ESALvage <Integer|?>
Description: Set or query the flag which controls the salvage test in
Intellipass mode. The salvage test is useful for non-linear
devices, which exhibit unexpectedly lower error rates
at low powers.
Example: None.
:IQ:TestType:CONFig:ADVanced:MODe:ESTabilize <Boolean|?>
Description: Set or query the flag which controls whether the
data acquisition waits a certain number of seconds before
measuring the bit error rate.
Example: None.
:IQ:TestType:CONFig:ADVanced:MODe:ESTabilize:TIMe <Float|?>
Description: Set or query the dwell time in seconds before measuring
the error rate at the current power.
Example: None.
:IQ:TestType:CONFig:ADVanced:MODe:ISPoints <Boolean|?>
Description: Choose the method of point distribution, use 0 to pick
the
points by step size, and 1 to pick by number of points.
210
SCPI Command Set
Example: None.
:IQ:TestType:CONFig:ADVanced:MODe:MAXTime <Float|?>
Description: Set the maximum number of seconds to wait at a point in
the test.
Example: None.
:IQ:TestType:CONFig:ADVanced:MODe:PFAilprob <Float|?>
Description: Set or query the probability of falsely failing a
device in intellipass mode.
Example: None.
:IQ:TestType:CONFig:ADVanced:MODe:PFLoor <Float|?>
Description: Set or query the Bit Error Rate at which the
intellipass post test takes place. The post test
will wait at this Bit Error Rate until the customer
defined probabilities of pass/fail are met.
Example: None.
:IQ:TestType:CONFig:ADVanced:MODe:POINts <Integer|?>
Description: Define the number of points to measure for the test.
Example: None.
:IQ:TestType:CONFig:ADVanced:MODe:PPASsprob <Float|?>
Description: Set or query the probability of falsely passing a device
in intellipass mode.
Example: None.
:IQ:TestType:CONFig:ADVanced:MODe:PSTep <Float|?>
Description: Size of the steps along the X-axis.
Example: None.
:IQ:TestType:CONFig:ADVanced:MODe:RST
Description: Initializes all variables on the Mode Control
test set-up screen to reasonable defaults.
Example: None.
:IQ:TestType:CONFig:ADVanced:MODe:SCONfidence <Float|?>
Description: Set or query the confidence level that a device under
test will pass or fail the salvage test. This test
assumes the device in non-linear, and exhibits lower
than expected errors at low powers.
Example: None.
:IQ:TestType:CONFig:ADVanced:MODe:SFAildispose
211
SCPI Commands
<?|'UNKNOWN'|'FAIL'>
Description: Set or query the disposition for the salvage test. If a
device fail
the salvage test, and this disposition is set to FAIL then the test
result will be set to fail.
Example: None.
:IQ:TestType:CONFig:ADVanced:MODe:SPASsdispose
<?|'UNKNOWN'|'PASS'>
Description: Set or query the pass disposition for the salvage test.
If this field
is set to PASS, then devices must pass the salvage test in order for
them
to receive a PASS in the final result.
Example: None.
:IQ:TestType:CONFig:ADVanced:MODe:SUNResolved
<?|'UNKNOWN'|'FAIL'>
Description: Set or query the unresolved disposition for the salvage
test. If devices
give an inconclusive result for this test, and the disposition is set
to FAIL, then the device will be failed.
Example: None.
:IQ:TestType:CONFig:ADVanced:MODe:TCContinue <Integer|?>
Description: Set or query the flag which controls the time it takes to
count errors at each power. If TCContinue is 0, the time is controlled
by
TCSeconds, TCERrors, TCUNcert. If set to 1, then the time
at each point will be TCMinseconds.
Example: None.
:IQ:TestType:CONFig:ADVanced:MODe:TCERrors <Float|?>
Description: Set or control the minimum number of errors seen at each
power
when TCContinue is 0.
Example: None.
:IQ:TestType:CONFig:ADVanced:MODe:TCMinseconds <Float|?>
Description: Set or query the minimum number of seconds at each power
when
TCContinue is 1.
Example: None.
:IQ:TestType:CONFig:ADVanced:MODe:TCSeconds <Float|?>
Description: Set or query the maximum number of seconds to count
errors at each power
when TCContinue is 0 and TCTYpe is 0.
212
SCPI Command Set
Example: None.
:IQ:TestType:CONFig:ADVanced:MODe:TCTYpe <Integer|?>
Description: Set or query the flag used to control the maximum amount
of time
to collect data at each power, when TCContinue is 0. If TCTYpe is
0, then TCMinseconds and TCERrors are used. If TCType is 1, then
TCUNcert and TCERrors are used.
Example: None.
:IQ:TestType:CONFig:ADVanced:MODe:TCUNcert <Float|?>
Description: Set or query the minimum amount of time to count errors
at each
point when TCContinue is 0 and TCType is 1. The counting will stop
when
the statistical uncertainty in the in the measurement has reached this
value.
Example: None.
:IQ:TestType:CONFig:DELete <Filename>
Description: Delete this configuration from the database.
Example: None.
:IQ:TestType:CONFig:DIS1 <integer>
Description: Sets or queries the error type displayed on the
statistics page.
Example: None.
statistics page.
Example: None.
statistics page.
Example: None.
statistics page.
Example: None.
213
SCPI Commands
statistics page.
Example: None.
:IQ:TestType:CONFig:ERRalarm <0|1>
Description: Sets or queries the audible alarm.
Example: None.
:IQ:TestType:CONFig:ERRor <PRBS|B1|B2|M1|B3|FCS>
Description: Set or query the error type for the test.
Example: None.
:IQ:TestType:CONFig:EXISt <Filename>
Description: Returns 1 if this configuration exists in the database,
and 0
if is does not exist.
Example: None.
:IQ:TestType:CONFig:ErrorType:BURSt <?|'All'|'Single'|'Repeat'|'None'>
Description: Set or query the Burst type for the Error Injection test.
Errors can
be put in the payload or header in different modes.
All an error in every frame
Single one error only
Repeat errors are added per frame or per second.
Example: None.
:IQ:TestType:CONFig:ErrorType:BURSt:LENGth:FRAMe <Integer|?>
Description: Set or query the number of consecutive frames or packets
in which
errors are injected.
Example: None.
:IQ:TestType:CONFig:ErrorType:BURSt:LENGth:SEConds <Integer|?>
Description: Set or query the burst length in seconds for which errors
are injected.
Example: None.
:IQ:TestType:CONFig:ErrorType:BURSt:LENGth:SELect
<?|'Time'|'Frames'|'Packets'>
Description: Set or query the type of the burst length for error
injection. Burst lengths
can be the number of seconds, frames or packets.
Example: None.
:IQ:TestType:CONFig:ErrorType:BURSt:REPeat:FRAMe <Integer|?>
214
SCPI Command Set
Description: Set or query the number of frames or packets between

error bursts.
Example: None.
:IQ:TestType:CONFig:ErrorType:BURSt:REPeat:SEConds <Integer|?>
Description: Set or query the number of seconds between error bursts.
Example: None.
:IQ:TestType:CONFig:ErrorType:BURSt:REPeat:SELect
<?|'Time'|'Frames'|'Packets'>
Description: Set or query the method of selecting the repetition rate
between error bursts.
Example: None.
:IQ:TestType:CONFig:GTCTrl
<SINGLE|REPEAT|UNTIMED|CONTINUOUS>
Description: Set or query the gate control type.
Example: None.
:IQ:TestType:CONFig:GTTYpe:DERRor <errors>
Description: Set or query the number of errors for the
"Errors" gate type on the BERT bar.
Example: None.
:IQ:TestType:CONFig:GTTYpe:DERerrtype <PRBS|B1|B2|M1|B3|FCS>
Description: Set or query the error type for the BERT bar gate.
Example: None.
:IQ:TestType:CONFig:GTTYpe:DTIMe <seconds>
Description: Set or query the number of seconds for the gate
for type "Time" gating on the BERT bar.
Example: None.
:IQ:TestType:CONFig:GTTYpe:DUNCertain <uncertainty>
Description: Set or query the value of the uncertainty for the
BERT bar when the gating is chosen to be "Uncertainty".
Example: None.
:IQ:TestType:CONFig:GTTYpe:DUNerrtype <PRBS|B1|B2|M1|B3|FCS>
Description: Set or query the type of error for the BERT bar when
"Uncertainty" gating is chosen.
Example: None.
215
SCPI Commands
:IQ:TestType:CONFig:LIST
Description: List all available parameter configurations for this
test
from the database.
Example: None.
:IQ:TestType:CONFig:LOAD <Filename>
Description: Load the parameter list for the test from the database
into the
current configuration.
Example: None.
:IQ:TestType:CONFig:QERR
Description: Set or query the error source for the Quick BERT bar.
Valid values are:
B1, B2, B3, M1, PRBS, EJITT, FCS, PCS, ETHSKIP, BIPSM, BIPPM,
BIPTCM1,
BIPTCM2, BIPTCM3, BIPTCM4, BIPTCM5, BIPTCM6, BEISM, BEIPM,
BEITCM1,
BEITCM2, BEITCM3, BEITCM4, BEITCM5, BEITCM6, FECCORRBIT0,
FECCORRBIT1,
FECCORRBIT, FECUNCORR, FECTOTBITERR, IPLOST, SEQCHK, 1GEThfcs,
1GCHksum
Example:
>> IQ:BERT:CONFIG:QERR?
[0 19] BER_Type "PRBS"
:IQ:TestType:CONFig:RST
Description: Resets all parameters for the current test to reasonable
defaults.
Example: None.
:IQ:TestType:CONFig:SAVe <Filename>
Description: Saves the current configuration parameters in the
database.
Example: None.
:IQ:TestType:CONFig:SELect
<?|'NONe'|'LOS'|'LOF'|'OOF'|'AISL'|'RDIL'|'REIP'|'AISP'|'RDIP'|'M1'|'B1'|'
B2'|'B3'|'REIL'|'ETHFcs'|'POSFcs'|'IPCHksum'|'OTHer'|'MSAis'|'MSRDi'|'M
SREi'|'HPRei'|'TXPause'|'OTNoof'|'OTUKais'|'ODUKais'|'ODULck'|'ODUOci
'|'GENais'|'AUAis'|'HPRDi'|'SMBDi'|'PMBDi'>
Description: Set or query the error type used for this test.
Example: None.
:IQ:TestType:RESEt
Description: Command to initialize all test parameters to 0.
216
SCPI Command Set
Example: None.
:IQ:TestType:RESUlt:ID:CLEar
Description: Deletes the results in buffer number ID, and moves all
results
in buffer ID and higher, down one buffer.
Example: None.
:IQ:TestType:RESUlt:ID:DELete <Filename>
Description: Deletes a saved result file from the database.
Example: None.
:IQ:TestType:RESUlt:ID:DETails
Description: Returns the list of results from the database.
Example:
%% iq:sens:result:1:load Sensitivity/a1234567/j.res
[0 0]
%% iq:sens:result:1:details
[0 2253] RESULT_DETAILS " " "Start Time" 19:00:00 "End Time" 19:00:00
"Total Points" 20 "Signal File" "Signal_Conf/a1234567/current.cfg"
"OST Name" "streets" "Error Source" UNKNOWN STANDARD_DETAILS " "
"Average Value" -13.22 "High Value" -13.13 "Low Value" -13.30
DATA_ACQUISITION_DETAILS " " "Corrected BER" 1.7E-05,1.5E-05,1E-05,
5.1E-06,6.2E-06,1.8E-06,2E-06,1.2E-06,4.6E-07,1.9E-07,3.5E-07,2.8E-
07,
7.7E-08,3.4E-08,1.5E-08,6.4E-09,7.4E-09,3.2E-09,1.4E-09,1.1E-09,2E-
10,
2E-10,0,0,0 "Slope" -0.96 "Intercept" -19.63 "CHI Square" 93.13
"Number of Points" 22 "X" -15.48,-15.40,-15.31,-15.22,-15.14,-15.05,
-14.97,-14.88,-14.79,-14.71,-14.62,-14.54,-14.45,-14.36,-14.28,-
14.19,
-14.11,-14.02,-13.94,-13.85,-13.76,-13.68,0.00,0.00,0.00 "Y" -4.82,
-4.87,-4.94,-5.08,-5.05,-5.28,-5.27,-5.36,-5.52,-5.67,-5.57,-5.60,
-5.80,-5.92,-6.02,-6.13,-6.12,-6.22,-6.32,-6.34,-6.53,-
6.53,0.00,0.00,
0.00 "Number of Errors"
87153.00,72739.00,50598.00,25603.00,31059.00,
8996.00,9982.00,5795.00,2288.00,929.00,1728.00,1382.00,387.00,168.0
0,
75.00,32.00,37.00,16.00,14.00,11.00,3.00,3.00,0.00,0.00,0.00
"Number of Bits" 10000000000.00,10000000000.00,10000000000.00,
10000000000.00,10000000000.00,10000000000.00,10000000000.00,
10000000000.00,10000000000.00,10000000000.00,10000000000.00,
10000000000.00,10000000000.00,10000000000.00,10000000000.00,
10000000000.00,10000000000.00,10000000000.00,20000000000.00,
20000000000.00,30000000000.00,30000000000.00,0.00,0.00,0.00
"Number Of Runs" 11 "runs test CL" 93.13 "chisq CL" 0.00
"horizontal rms" 0.06 "horiz rms CL" 55.61 INPUT_PARAMETER_DETAILS "
"
"Approximate_Value" 0.00 "IntelliTime_Duration(min)" 0.00
"BER_Definition" 0.00e+00 "Pass_Fit_Quality0" 0.00
"Pass_Fit_Quality1" 0.00
"DUT_Code" "NULL" "Comments" "NULL" "Command" "NULL" "Display_Type"
AvgPwr
"IntelliPass_Max_Time(min)" 0.00 "Lower_BER" 0.00e+00 "Max_Power"
217
SCPI Commands
0.000000
"Max_Time_per_Point(sec)" 0.00 "Min_Power" 0.000000 "Num_Times" 0
"Start_Power" 0.00 "End_Power" 0.00 "Start_Power" 0.00 "End_Power"
0.00
"Requested_Number_Points" 0 "Pretest_Power" 0.00 "Pretest_Time(sec)"
0.00
"Requested_Power_Step" 0.00 "Pass_Uncertainty" 0.00 "Pass_Value"
0.00
"DUT_Serial_Number" "NULL" "Test_Type" UNKNOWN "Input_Tx_Power" 0.00
"Upper_BER" 0.00e+00 "Desired_Uncertainty_per_Point" 0.00
:IQ:TestType:RESUlt:ID:DETails:COMMa
Description: Returns the results of a previously loaded test in the
form
of comma separated tables.
Example:
%% iq:sens:result:1:details:comma
[0 2253] RESULT_DETAILS," "
"Start Time",19:00:00
"End Time",19:00:00
"Total Points",20
"Signal File","Signal_Conf/a1234567/current.cfg"
"OST Name","streets"
"Error Source",UNKNOWN
STANDARD_DETAILS," "
"Average Value",-13.22
"High Value",-13.13
"Low Value",-13.30
DATA_ACQUISITION_DETAILS," "
"Corrected BER",1.7E-05,1.5E-05,1E-05,5.1E-06,6.2E-06,1.8E-06,2E-
06,1.2E-06,
4.6E-07,1.9E-07,3.5E-07,2.8E-07,7.7E-08,3.4E-08,1.5E-08,6.4E-
09,7.4E-09,3.2E-09,
1.4E-09,1.1E-09,2E-10,2E-10,0,0,0
"Slope",-0.96
"Intercept",-19.63
"CHI Square",93.13
"Number of Points",22
"X",-15.48,-15.40,-15.31,-15.22,-15.14,-15.05,-14.97,-14.88,-
14.79,-14.71,-14.62,
-14.54,-14.45,-14.36,-14.28,-14.19,-14.11,-14.02,-13.94,-13.85,-
13.76,-13.68,
0.00,0.00,0.00
"Y",-4.82,-4.87,-4.94,-5.08,-5.05,-5.28,-5.27,-5.36,-5.52,-5.67,-
5.57,-5.60,
-5.80,-5.92,-6.02,-6.13,-6.12,-6.22,-6.32,-6.34,-6.53,-
6.53,0.00,0.00,0.00
"Number of
Errors",87153.00,72739.00,50598.00,25603.00,31059.00,8996.00,9982.0
0,
5795.00,2288.00,929.00,1728.00,1382.00,387.00,168.00,75.00,32.00,37
.00,16.00,
14.00,11.00,3.00,3.00,0.00,0.00,0.00
"Number of
Bits",10000000000.00,10000000000.00,10000000000.00,10000000000.00,
10000000000.00,10000000000.00,10000000000.00,10000000000.00,1000000
0000.00,
10000000000.00,10000000000.00,10000000000.00,10000000000.00,1000000
0000.00,
10000000000.00,10000000000.00,10000000000.00,10000000000.00,2000000
0000.00,
218
SCPI Command Set
20000000000.00,30000000000.00,30000000000.00,0.00,0.00,0.00
"Number Of Runs",11
"runs test CL",93.13
"chisq CL",0.00
"horizontal rms",0.06
"horiz rms CL",55.61
INPUT_PARAMETER_DETAILS," "
"Approximate_Value",0.00
"IntelliTime_Duration(min)",0.00
"BER_Definition",0.00e+00
"Pass_Fit_Quality0",0.00
"Pass_Fit_Quality1",0.00
"DUT_Code","NULL"
"Comments","NULL"
"Command","NULL"
"Display_Type",AvgPwr
"IntelliPass_Max_Time(min)",0.00
"Lower_BER",0.00e+00
"Max_Power",0.000000
"Max_Time_per_Point(sec)",0.00
"Min_Power",0.000000
"Num_Times",0
"Start_Power",0.00
"End_Power",0.00
"Start_Power",0.00
"End_Power",0.00
"Requested_Number_Points",0
"Pretest_Power",0.00
"Pretest_Time(sec)",0.00
"Requested_Power_Step",0.00
"Start_Power",0.00
"End_Power",0.00
"Requested_Number_Points",0
"Pretest_Power",0.00
"Pretest_Time(sec)",0.00
"Requested_Power_Step",0.00
"Pass_Uncertainty",0.00
"Pass_Value",0.00
"DUT_Serial_Number","NULL"
"Test_Type",UNKNOWN
"Input_Tx_Power",0.00
"Upper_BER",0.00e+00
"Desired_Uncertainty_per_Point",0.00
:IQ:TestType:RESUlt:ID:DETails:SEMi
Description: Returns the results of a previously loaded test in the
form of semi-colon separated tables.
Example:
>> iq:sens:results:list?
[0 37] 0 "starting" 1 "simulation" 2 "mode"
>> iq:sens:1:load simulation
[0 0]
>> iq:sens:result:1:details:semi
[0 1268] RESULT_DETAILS: " " ;"Start Time": "Wed Dec 31 19:00:00
196
9";"End Time": "Wed Dec 31 19:00:00 1969";"Total Points": 0;"Signal
File":
"NULL";"OST Name": "NULL";"Error Source": UNKNOWN;STANDARD_DETAILS
: " " ;"Average Value": 0.00;"High Value": 0.00;"Low Value":
0.00;DATA_ACQUISITION_DETAILS: " " ;"Number of Points": 0;"Slope":
0.00;"Intercept": 0.00;"Fit Quality": 0.00;"Number of Runs in Fit":
219
SCPI Commands
0;"Runs Test CL": 0.00;"Chisq CL": 0.00;"Horizontal RMS": 0.00;"Ho

riz RMS CL": 0.00;PROTOCOL_STATUS_DETAILS: " "
;INPUT_PARAMETER_DETAILS:
" " ;"Approximate_Value": 0.00;"IntelliTime_Duration(min)":
0.00;"BE
R_Definition": 0.00e+00;"Pass_Fit_Quality0":
0.00;"Pass_Fit_Quality1":
0.00;"DUT_Code": "NULL";"Comments": "NULL";"Command": "NULL";"
Display_Type": AvgPwr;"IntelliPass_Max_Time(min)":
0.00;"Lower_BER":
0.00e+00;"Max_Power": 0.000000;"Max_Time_per_Point(sec)":
0.00;"Min_Power"
: 0.000000;"Num_Times": 0;"Start_Power0": 0.00;"End_Power0":
0.00;"Start_Power1": 0.00;"End_Power1":
0.00;"Requested_Number_Points":
0;"Pretest_Power": 0.00;"Pretest_Time(sec)":
0.00;"Requested_Power_St
ep": 0.00;"Pass_Uncertainty": 0.00;"Pass_Value":
0.00;"DUT_Serial
_Number": "NULL";"Test_Type": UNKNOWN;"Input_Tx_Power": 0.00;"Up
per_BER": 0.00e+00;"Desired_Uncertainty_per_Point": 0.00;
:IQ:TestType:RESUlt:ID:DUT <String|?>
Description: Returns the name of the Device Under Test.
Example:
%% iq:sens:result:1:DUT?
[0 11] DUT "NULL"
:IQ:TestType:RESUlt:ID:ENDTime <Time|?>
Description: Returns the time when the test stopped.
Example:
%% iq:sens:result:1:ENDTime?
[0 17] ENDTime 19:00:00
:IQ:TestType:RESUlt:ID:ERRorsource
<?|'B1'|'B2'|'B3'|'M1'|'PRBS'|'EJITT'|'FCS'|'PCS'|'ETHDROP'|'BIPSM'|'BIP
PM'|'BIPTCM1'|'BIPTCM2'|'BIPTCM3'|'BIPTCM4'|'BIPTCM5'|'BIPTCM6'|
'BEISM'|'BEIPM'|'BEITCM1'|'BEITCM2'|'BEITCM3'|'BEITCM4'|'BEITCM
5'|'BEITCM6'|'FECCORRBIT0'|'FECCORRBIT1'|'FECCORRBIT'|'FECUN
CORR'>
Description: Returns the error source used in the bit error rate
calculation.
Example:
%% iq:sens:result:0:ERRorsource?
[0 17] ERRorsource PRBS
:IQ:TestType:RESUlt:EXISt <Filename>
Description: Queries whether a named result exists in the database.
Example:
[0 89] 0 "Sensitivity/a1234567/autosave/2004_02_02_16_48_19.res" 1
"Sensitivity/a1234567/j.res"
%% iq:sens:result:exist j
220
SCPI Command Set
%% iq:sens:result:exist j.res
%% iq:sens:result:exist Sensitivity/a1234567/j.res
[0 11] EXISt TRUE
:IQ:TestType:RESUlt:ID:LIST?
Description: Lists existing entries in the database for this
type of test.
Example:
%% iq:sens:result:list?
:IQ:TestType:RESUlt:ID:LOAD <Filename>
Description: Loads a particular results file from the database
into the instrument. The ID is the buffer number,
and up to 10 buffers can be displayed. If Filename
addresses more than one entry in the database, then
the results will be loaded into consecutive buffers
starting at ID.
Example:
%% iq:sens:result:list?
%% iq:sens:result:1:load Sensitivity/a1234567/j.res
[0 0]
%% iq:sens:result:1:ERRorsource?
[0 17] ERRorsource PRBS
:IQ:TestType:RESUlt:ID:NDATa <Integer|?>
Description: Query the number of separate fits made in the test.
For instance, sensitivity returns 1, and path penalty returns
2.
Example:
%% iq:sens:resu:1:ndata?
[0 8] NDATa 1
:IQ:TestType:RESUlt:ID:OSTName <String|?>
Description: Queries the serial name of the OST on which
the test ran.
Example:
%% iq:sens:resu:1:OSTName?
[0 18] OSTName "a1234567"
:IQ:TestType:RESUlt:ID:PASS <?|'RUNNING'|'PASS'|'FAIL'|'NA'>
Description: Returns the status of the test.
Example:
%% iq:sens:resu:1:pass?
[0 10] PASS PASS
:IQ:TestType:RESUlt:ID:RST
221
SCPI Commands
Description: Resets all parameters for the current test to reasonable

defaults.
Example: None.
:IQ:TestType:RESUlt:ID:RXMode
<?|'Single_Mode'|'850nm_Multimode'|'Digital_Electrical'>
Description: Returns the RX mode for the test. Single_Mode is
available
for the A3308, and 850nm_Multimode and Digital_Electrical are
available on
the A3318.
Example: None.
:IQ:TestType:RESUlt:ID:SAVe <Filename>
Description: Saves the current results buffer into the named entry
in the database.
Example:
%% iq:sens:resu:list?
"Sensitivity/a1234567/j.res" 2
"Sensitivity/a1234567/autosave/2004_02_10_16_38_13.res" 3
"Sensitivity/a1234567/k.res"
%% iq:sens:resu:1:save Sensitivity/a1234567/temp.res
[0 0]
%% iq:sens:resu:list?
"Sensitivity/a1234567/j.res" 2
"Sensitivity/a1234567/autosave/2004_02_10_16_38_13.res" 3
"Sensitivity/a1234567/k.res" 4 "Sensitivity/a1234567/temp.res"
:IQ:TestType:RESUlt:ID:STANdard:AVVLue <Float|?>
Description: Returns the major value of the result for this test.
Example:
%% iq:sens:result:1:standard:LWVLue?
[0 14] LWVLue -13.24
%% iq:sens:result:1:standard:HIVLue?
[0 14] HIVLue -13.09
%% iq:sens:result:1:standard:AVVLue?
[0 14] AVVLue -13.17
:IQ:TestType:RESUlt:ID:STANdard:DEFinition <Float|?>
Description: Returns the Bit Error Rate at which the test result was
measured.
Example:
%% iq:sens:result:1:standard:definition?
[0 20] DEFinition 1.00e-12
:IQ:TestType:RESUlt:ID:STANdard:EXTRapolated <Boolean|?>
Description: Returns whether the result was extrapolated from the
test data.
Example: None.
222
SCPI Command Set
:IQ:TestType:RESUlt:ID:STANdard:HIVLue <Float|?>
Description: Returns the highest value of the result with one
sigma confidence.
Example:
[0 14] LWVLue -13.24
[0 14] HIVLue -13.09
[0 14] AVVLue -13.17
:IQ:TestType:RESUlt:ID:STANdard:LWVLue <Float|?>
Description: Returns the lowest measured result for the test, within
one sigma confidence.
Example:
[0 14] LWVLue -13.24
[0 14] HIVLue -13.09
[0 14] AVVLue -13.17
:IQ:TestType:RESUlt:ID:STANdard:VALid <Boolean|?>
Description: Queries whether the results is valid. The command
returns 0 if the OST could not ascertain whether the
test passed or failed.
Example:
%% iq:sens:resu:1:Standard:valid?
[0 8] VALid 1
:IQ:TestType:RESUlt:ID:STRTtime <Time|?>
Description: Returns the time that the test was started.
Example:
%% iq:sens:result:1:STRTtime?
[0 18] STRTtime 19:00:00
:IQ:TestType:RESUlt:ID:SUMMary
Description: Returns a summary of the results for the test running in
the specified buffer.
Example:
%% iq:sens:resu:1:summary
[0 473] NTEST 3 SERIALNO_0 NULL SIGFILE_0
Signal_Conf/a1234567/current.cfg
RSLT_VALID_0 1 PERCENT_0 99 PWR_0 -13.19 PWERR_0 0.06 CHISQ0_0 93.13
SLOPE0_0 -0.946 RSL_0 PASS SERIALNO_1 NULL SIGFILE_1
Signal_Conf/a1234567/current.cfg RSLT_VALID_1 1 PERCENT_1 99 PWR_1 -
13.19
PWERR_1 0.06 CHISQ0_1 93.13 SLOPE0_1 -0.946 RSL_1 PASS SERIALNO_2
NULL
SIGFILE_2 Signal_Conf/a1234567/current.cfg RSLT_VALID_2 1 PERCENT_2
99
223
SCPI Commands
PWR_2 -13.19 PWERR_2 0.06 CHISQ0_2 93.13 SLOPE0_2 -0.946 RSL_2 PASS
:IQ:TestType:RESUlt:ID:TESTber <Float|?>
Description: Queries the Bit Error Rate at which the test
result is measured.
Example:
%% iq:sens:resu:1:TESTber?
[0 17] TESTber 1.00e-12
:IQ:TestType:RESUlt:ID:TOTalpoints <Integer|?>
Description: Returns the total number of points used in the
fit for the test.
Example:
%% iq:sens:resu:1:TOTalpoints?
[0 15] TOTalpoints 20
:IQ:TestType:RESUlt:ID:TXMode
<?|'Single_Mode'|'850nm_Multimode'|'Digital_Electrical'|'Variable_Electrical'
>
Description: Returns the TX mode for the test. Single_Mode is
available
for the A3308, and 850nm_Multimode, Digital_Electrical and
Variable_Electrical
modes are available for the A3318.
Example: None.
:IQ:TestType:RESUlt:ID:WJFReq <Float|?>
Description: Returns the Jitter Frequency in MHz found during the
worst case jitter point pretest.
Example: None.
:IQ:TestType:RESUlt:ID:WJUi <Float|?>
Description: Queries the Jitter Amplitude in unit intervals which was
found during the worst case jitter point pretest.
Example: None.
:IQ:TestType:STARt <signal Configuration>

Description: Starts the test. The argument is the index of the signal
file.
Example:
# select the OST
INST:SELE:ID 1
# Load and start traffic
SYST:FILE:LOAD Signal_Conf/default.cfg
OUTP:TELE:TRAFFIC:CONF:START
# Load test set-up parameters
SYST:FILE:LOAD Sensitivity/default.par
# Start a test
IQ:SENS:START
224
SCPI Command Set
:IQ:TestType:STATus?
Description: To query the status of the running test.
Returns 1047 if the test is still running.
Example: None.
:IQ:TestType:STOP
Description: This command stops the running test.
Example: None.
:IQ:TestType:TYPe
Description: Set or query the type of errors being injected.
Valid values are:
"NONe",
"LOS",
"LOF",
"OOF",
"AISL",
"RDIL",
"REIP",
"AISP",
"RDIP",
"M1",
"B1",
"B2",
"B3",
"REIL" ,
"ETHFcs" ,
"POSFcs",
"IPCHksum",
"OTHer",
"MSAis",
"MSRDi",
"MSREi",
"HPRei",
Example: None.
:MEMory:FETCh:802e:DATa?
Description: Queries the 802e data (LAN/WAN).
Example: None.
:MEMory:FETCh:ATIMe?
Description: Queries the actual time, number of errors or
absolute uncertainty for which the BERT ran.
Example: None.
:MEMory:FETCh:BERT?
Description: Queries all the data for the running BER test.
Example: None.
225
SCPI Commands
:MEMory:FETCh:DAQ:BERHi?
Description: Queries the upper error on each BER point in the fit.
The values are returned as a comma delimited list.
Example: None.
:MEMory:FETCh:DAQ:BERLo?
Description: Queries the lower error for each BER point in the fit.
Example: None.
:MEMory:FETCh:DAQ:CBER?
Description: Queries the BER values for each point.
Example: None.
:MEMory:FETCh:DAQ:ETHernet:DFRames?
Description: Queries the dropped frames for each point in the fit.
Example: None.
:MEMory:FETCh:DAQ:ETHernet:E1Level?
Description: Queries number of errored ethernet frames which
are between 64-127 bytes.
Example: None.
Example: None.
Example: None.
Description: Queries number of errored ethernet frames which are
between
512-1023 bytes.
Example: None.
Example: None.
226
SCPI Command Set
:MEMory:FETCh:DAQ:ETHernet:EBIT?
Description: Query the number of bit errors for each point.
Example: None.
:MEMory:FETCh:DAQ:ETHernet:EBYTes?
Description: Query the number of errored bytes for each point.
Example: None.
:MEMory:FETCh:DAQ:ETHernet:EFRames?
Description: Query number of errored frames.
Example: None.
:MEMory:FETCh:DAQ:ETHernet:FCS?
Description: Query number of Frame Check Sequence errors.
Example: None.
:MEMory:FETCh:DAQ:ETHernet:NBIT?
Description: Query number of bits.
Example: None.
:MEMory:FETCh:DAQ:ETHernet:PCS?
Description: Query number of Physical Coding Sublayer errors.
Example: None.
:MEMory:FETCh:DAQ:ETHernet:PREamble?
Description: Queries number of preamble errors.
Example: None.
:MEMory:FETCh:DAQ:ETHernet:V1Level?
Description: Query the number of valid ethernet frames between the
sizes of 64-127 bytes.
Example: None.
Description: Queries the number of valid ethernet frames between
128-255 frames.
Example: None.
256-511 bytes.
227
SCPI Commands
Example: None.
512-1023 bytes.
Example: None.
Description: Queries the number of valid ethernet frames
between 1024-1518 bytes.
Example: None.
:MEMory:FETCh:DAQ:ETHernet:VBYTes?
Description: Queries the number of valid bytes.
Example: None.
:MEMory:FETCh:DAQ:ETHernet:VFRames?
Description: Queries the valid number of ethernet frames.
Example: None.
:MEMory:FETCh:DAQ:POWer?
Description: Queries the powers (X-axis) used in the fit.
Example: None.
:MEMory:FETCh:DAQ:PRBS:EBITs?
Description: Queries the number of errored bits per point in
the fit.
Example: None.
:MEMory:FETCh:DAQ:PRBS:NBITs?
Description: Queries the number of bits per point
in the fit.
Example: None.
:MEMory:FETCh:DAQ:SONet:B1?
Description: Queries the number of B1s per point in the fit.
Example: None.
Example: None.
228
SCPI Command Set
Example: None.
:MEMory:FETCh:DAQ:SONet:FRAMes?
Description: Queries the number of frames per point in the fit.
Example: None.
:MEMory:FETCh:DAQ:SONet:M1?
Description: Queries the number of M1s per point in the fit.
Example: None.
:MEMory:FETCh:GIGe:DATa
Description: Queries the 1GigE statistical information.
Example:
>> :MEMory:FETCh:GIGe:DATa?
[0 688] SIGDET OK SYNCH OK PAUSES NO REMF OK FRMOK 1453597.77 OCTOK
95937452.74
FRMBAD 0.00 FCSE 0.00 FCSBER 0.00e+00 UNDE 0.00 OVRE 0.00 MCAST
1453597.77
BCAST 0.00 NPAUSE 0.00 POK_0 1453597.77 POK_1 0.00 POK_2 0.00 POK_3
0.00
POK_4 0.00 POK_5 0.00 TPOK_0 1453597.77 TPOK_1 0.00 TPOK_2 0.00 TPOK_3
0.00
TPOK_4 0.00 TPOK_5 0.00 TMCAST 1453597.77 TBCAST 0.00 C_FRMOK 0.00
C_OCTOK 0.00
C_FRMBAD 0.00 C_FCSE 0.00 C_FCSBER 0.00e+00 C_UNDE 0.00 C_OVRE 0.00
C_MCAST 0.00
C_BCAST 0.00 C_NPAUSE 0.00 C_NPAUSE 0.00 C_POK_0 0.00 C_POK_1 0.00
C_POK_2 0.00
C_POK_3 0.00 C_POK_4 0.00 C_POK_5 0.00 C_TPOK_0 0.00 C_TPOK_1 0.00
C_TPOK_2 0.00
C_TPOK_3 0.00 C_TPOK_4 0.00 C_TPOK_5 0.00 C_TMCAST 0.00 C_TBCAST 0.00
:MEMory:FETCh:OTN:DATa
Description: Queries the OTN statistical information.
Example: None.
:MEMory:FETCh:POSe:DATa?
Description: Queries the Packet Over SONET statistical data.
Example: None.
:MEMory:FETCh:PRBS:DATa?
Description: Queries the Pseudo-Random Bit Sequencing statistical
data.
Example: None.
229
SCPI Commands
:MEMory:FETCh:QBER:DATa?
Description: Queries the statistical data for the Quick BER
monitor.
Example: None.
:MEMory:FETCh:SONet:DATa?
Description: Queries the SONET/SDH statistical data.
Example: None.
:MEMory:FETCh:STATus:802e
Description: Queries the Ethernet 802.3 status flags, i.e. SIGDET_B,
SYNCH_B,
LINK_B, HIBER_B, PAUSE_B, FCS_B, PCS_B, LCD_B, LOCF_B, REMF_S,
FRAG_B, UNDER_B, OVER_B, JABBER_B, IPG_B.
Example: None.
:MEMory:FETCh:STATus:GIGe
Description: Queries status of 1GigE status flags from the last
test.
Example:
>> MEMory:FETCh:STATus:GIGe?
[0 146] SIGDET_B 0 SYNCH_B 0 PAUSE_B 0 HIBER_B -1 LCD_B -1 LOCF_B -1
REMF_S 0
LINK_B 0 FCS_B 0 PCS_B -1 UNDER_B 0 OVER_B 0 JABBER_B -1 FRAG_B -1
IPG_B -1
:MEMory:FETCh:STATus:OTN1
Description: Queries the OTN1 flags, i.e. LOF, OOF, LOM, OOM, AIS,
IAE,
SMBIP, SMBEI, SMBDI, CORRBIT, CORR0, CORR1, UNCORR.
Example: None.
Description: Queries the OTN2 flags, i.e. AIS, OCI, LCK, PMBIP, PMBEI,
PMBDI, NEWFTFL, NEWTTI.
Example: None.
Description: Queries the OTN3 flags, i.e. TCM1BIP, TCM1BEI, TCM1BDI,
TCM2BIP, TCM2BEI, TCM2BDI, TCM3BIP, TCM3BEI, TCM3BDI.
Example: None.
Description: Queries the OTN4 flags, i.e. TCM4BIP, TCM4BEI, TCM4BDI,
230
SCPI Command Set
TCM5BIP, TCM5BEI, TCM5BDI, TCM6BIP, TCM6BEI, TCM6BDI.
Example: None.
:MEMory:FETCh:STATus:POS?
Description: Queries the Packet Over SONET status flags,
i.e. LINKUP, OOF, LOF, FCSERR, OVERSIZE, UNDERSIZE,
ABORT, TX, RX, IPCHKSUM.
Example: None.
:MEMory:FETCh:STATus:SONet?
Description: Queries the SONET/SDH status flags,
i.e. B1, B2, B3, M1, REIP, REIL,
RDIP, RDIL, AISL, AISP, SF, SD, OOF, LOF.
Example: None.
:MEMory:FETCh:TestType:DATa <Buffer-Number>
Description: Queries the data in one of the five buffers
for the current test. The data includes the
X, Y (+/- Yerrors) for each point and line
of the fits for the test as name-value pairs.
Example: None.
:MEMory:FETCh:TestType:HIST <Buffer-Number>
Description: Queries the histogram limits for one of the
five buffers for the current test. The information
is returned as name-value pairs and contains the
minimum and maximum values on the axes.
Example: None.
:MEMory:FETCh:TestType:RESults:FITQ?
Description: Queries the current fit quality (or fit qualities
if there are more than one fit) for the running test.
Example: None.
:MEMory:FETCh:TestType:RESults:NPOints?
Description: Queries the number of points take so far for
each fit for the current test.
Example: None.
:MEMory:FETCh:TestType:RESults:PERCent?
Description: Queries an estimate fraction (in percent) of
the amount of data taken before the test
will be completed.
Example: None.
:MEMory:FETCh:TestType:RESults:SIGMa?
231
SCPI Commands
Description: Queries the estimated error on the measurement

for the current test.
Example: None.
:MEMory:FETCh:TestType:RESults:STATus?
Description: Queries the status of the current test. Response
returns PENDING, RUNNING, PASSED, FAILED, ABORTED
or UNKNOWN.
Example: None.
:MEMory:FETCh:TestType:RESults:VALue?
Description: Queries the current estimate of the result
for the current test.
Example: None.
:MESG:GETall?
Description: Queries all status messages from the OST.
Example: None.
:MESG:SINGle?
Description: Returns the last message in the message buffer.
Returns CDATAEMPTY if no message is available.
Example:
:INST:SELE:ID 1
:MESG:SINGLE?
Returns [0 1045] if no message is available.
:OPC?
Description: Queries state of running test. Returns COPC if a test is
running.
Example:
:OPC?
:OUTPut:ATTenuation <dB>
Description: Set or request the value of the current attenuator in dB.
Example: None.
:OUTPut:ATTenuation:ADC?
Description: Read a raw ADC value for the current attenuator.
The current attenuator is set with :OUTPut:ATTenuation:SELect.
If the attenuator is of type MOTOR, the ADC value is the wiper.
For MEMS attenuators, the ADC value is that of the corresponding
power meter.
Example:
232
SCPI Command Set
:OUTPut:ATTenuation:DAC <ADC Value>

Description: Sets the raw ADC value for the current attenuator.
The current attenuator is set with :OUTPut:ATTenuation:SELect.
Works with MEMS type attenuators only.
Example:
:OUTPut:ATTenuation:INITialize
Description: Calls the attenuator initialization function.
For calibration purposes only.
Example: None.
:OUTPut:ATTenuation:SELect <attenID>
Description: Sets the attenuator identifier for the
OUTPut:ATTenuation subsystem.
The argument can be an integer, or the attenuator name.
Example:
:OUTPut:ATTenuation:STEP <Number-Steps>
Description: Moves the wiper on a MOTOR type attenuator by a number
of steps.
Example:
:OUTPut:ATTenuation:ZERo <0|1>
Description: Sets (1) or clears (0) the ZERO bit on the current
attenuator. Works for MEMS attenuators only.
Example:
:OUTPut:TELecom:OST:CALFactor <dB>
Description: Sets or queries the calibration factor on the output
side of the OST. Units are in dB.
Example:
To set the TX cal factor to 2.1dB:
:OUTPut:TELecom:OST:CALFactor 2.1
:OUTPut:TELecom:OST:CALSave <filename>
Description: Saves the TX Cal factor to filename.
Example: None.
:OUTPut:TELecom:OST:CLOCk <ClockType>
Description: Sets or queries the TX clock source. The clock type is
defined as follows:
2 TXCLK_155M_INTERNAL
3 TXCLK_155M_EXTERNAL
233
SCPI Commands
13 TXCLK_GIGE_INTERNAL
14 TXCLK_GIGE_EXTERNAL
15 TXCLK_OC48_INTERNAL
16 TXCLK_OC48_EXTERNAL
Example:
To generate the TX clock for 10GE LAN from the internal clock:
:output:TELecom:OST:clock 4
:OUTPut:TELecom:OST:DEGType <nooptics|10gbasel|10gbasee|custom>
Description: Query the type of optical degradation currently set.
Example: None.
:OUTPut:TELecom:OST:EDFa:ADC0?
Description: Reads input photocell on EDFA_PRE.
Example:
Description: Reads output photocell on EDFA_PRE.
Example:
Description: Reads input photocell on EDFA_BOOST.
Example:
Description: Reads output photocell on EDFA_BOOST.
Example:
:OUTPut:TELecom:OST:EDFa:BOOSt <0|1>
Description: Sets the the BOOST EDFA on (1) or off (0).
Example:
:OUTPut:TELecom:OST:EDFa:PRE <0|1>
234
SCPI Command Set
Description: Switches on (1) or off (0) the PRE EDFA.
Example:
:OUTPut:TELecom:OST:EDFa:SET <ON|OFF>
Description: Queries or switches the EDFA(s) on or off. The query
returns:
0 Both EDFAs off
1 PRE on only
2 BOOST on only
3 Both EDFAs are on.
Example:
To turn on the EDFA:
:output:TELecom:OST:EDFa ON
:OUTPut:TELecom:OST:ERAT <ExtinctionRatio>
Description: Set or query the extinction ratio using the
secondary laser.
Example: None.
:OUTPut:TELecom:OST:ERMeter <ExtinctionRatio>
Description: Queries the extinction ratio of the optical
signal coming out of the OST.
Example:
To set and read back the extinction ratio:
OUTPut:TELecom:OST:ERATio 10.0
OUTPut:TELecom:OST:ERATio?
Returns [0 9] ER 10.31
:OUTPut:TELecom:OST:LASer <ON|OFF>
Description: Turns the transponder laser ON or OFF, or queries its
state.
This command also switches the EDFA(s) into the correct state, and
will
power up the devices in the correct order. The EDFA(s) can be switched
off after the laser is ON.
Example:
:inst:SELE:id 1
:output:TELecom:OST:laser on
output:TELecom:OST:laser?
Returns [0 8] LASR ON
:OUTPut:TELecom:OST:MAXPower <dBm>
Description: Sets or queries the maximum TX power from the OST in dBm
as set by the customer. The MAXPower can not be greater than
the power as read by :OUTPut:TELecom:OST:POWer:LIMit? command.
Example: None.
:OUTPut:TELecom:OST:MAXSavepower <filename>
Description: Save the maximum output power to a disk file.
235
SCPI Commands
Example: None.
:OUTPut:TELecom:OST:OMA <OMA>
Description: Set or query the Optical Modulation Amplitude from
the TX side of the OST. Units can be set or queried
with the :OUTPut:TELecom:OST:OMA:UNITs command.
Example: None.
:OUTPut:TELecom:OST:OMA:UNITs <dBm|mW
Description: Set or query the units for the output OMA
meter.
Example: None.
:OUTPut:TELecom:OST:OMETer <OMA>
Description: Set or query the output Optical Modulation
Amplitude of the OST. Units are chosen with
the OUTPUT:TELecom:OST:OMA:UNITs command.
Example: None.
:OUTPut:TELecom:OST:OSNR <dBm>
Description: Set or query the Optical Signal to Noise Ratio of the
transmitted signal. Note that if the requested value
is out of range, the OSNR will be set to the closest
value, and error code 1051 will be returned.
Example:
:inst:SELE:id 1
:OUTPut:TELecom:OST:OSNR 20
:OUTPut:TELecom:OST:OSNR?
Returns [0 11] OSNR 20.12
:OUTPut:TELecom:OST:OSNR 60
:OUTPut:TELecom:OST:OSNR?
Returns [1051 11] OSNR 51.21
:OUTPut:TELecom:OST:OUTPower?
Description: Query the output power from the OST.
Example: None.
:OUTPut:TELecom:OST:POWer <power>
Description: Set or query the optical power from the TX side
going towards the DUT. Units can be set or queried with
the :OUTPut:TELecom:OST:POWer command.
Example: None.
:OUTPut:TELecom:OST:POWer:LIMit?
Description: Query the maximum output power of the OST.
Example: None.
236
SCPI Command Set
:OUTPut:TELecom:OST:POWer:UNITs <dBm|mW>
Description: Set or query the units to define subsequent TX power
commands.
Valid values are dBm and mW.
Example:
To query the current units being used:
OUTPut:tel:OST:pow:units?
[0 15] OUTP_UNITs dBm
:OUTPut:TELecom:OST:SAVe <filename>
Description: Saves Maximum Power and Power Units to the specified
file.
Example: None.
:OUTPut:TELecom:OST:TRAFfic
Description: Queries the status of traffic.
Example:
%% OUTPut:TELecom:OST:TRAFfic?
[0 11] TRAFfic ON
:OUTPut:TELecom:OST:TXLock?
Description: Queries that status of the TX lock.
Example:
:OUTPut:TELecom:OST:TXLock?
[0 9] LOCK OFF
:OUTPut:TELecom:OST:TXMode
<?|'SMODE'|'MMODE'|'DEMODE'|'VEMODE'>
Description: Set or query the TX mode. Single is supported for
the A3308. Multi, Digital Electrical and Variable Electrical are
supported on the A3318.
Example:
>> OUTPut:TELecom:OST:TXMode?
[0 18] OUTP_TXMode SMODE
:OUTPut:TELecom:OST:VPP
Description: Set or query the Variable Electrical output
from the A3318. Units are in Volts peak-to-peak.
Example: None.
:OUTPut:TELecom:OST:WAVelength?
Description: Queries the TX wavelength, result is in nanometers.
Example:
:OUTP:TELecom:OST:WAVE?
[0 20] OUTP_WAVELEN 1555.8
237
SCPI Commands
:OUTPut:TELecom:OST:XPONder <NORM|10G_L|10G_E|CUSTOM>
Description: Set or query the Vertical Eye Closure
Parameters for the OST.
Example: None.
:OUTPut:TELecom:TRAFfic:CONFig:8023:DADDress <Ethernet Address>

Description: Set or query the ethernet address to be transmitted for
pause
control.
Example: None.
:OUTPut:TELecom:TRAFfic:CONFig:8023:DLFDetection <0|1>
Description: Set or query flag to disable local fault detection.
Example: None.
:OUTPut:TELecom:TRAFfic:CONFig:8023:EDADdress <0|1>
Description: Set or query flag for Enable Device Address for
RX Pause Control.
Example: None.
:OUTPut:TELecom:TRAFfic:CONFig:8023:EDES <Ethernet Address>

Description: Set or query the ending destination ethernet address.
The destination address of transmitted ethernet packets
can be ramped between two ethernet addresses, this
command defines the ending ethernet address. The
starting ethernet destination address
is set with :OUTPut:TELecom:TRAFfic:CONFig:8023:SDES
Example: None.
:OUTPut:TELecom:TRAFfic:CONFig:8023:ELLC <LLCType>
Description: Set or query the Logical Link Control type.
Example: None.
:OUTPut:TELecom:TRAFfic:CONFig:8023:EOUi <Identifier>
Description: Set or query the Organizationally Unique Identifier.
Example: None.
:OUTPut:TELecom:TRAFfic:CONFig:802e:ESPecpattern <Integer|?>
Description: Enables or disables one of the special patterns for the
802.3ae payload. The pattern is chosen with the
:OUTPut:TELecom:TRAFfic:CONFig:802e:SPECtype command, (CRPAT or
CJPAT).
Example: None.
:OUTPut:TELecom:TRAFfic:CONFig:8023:ESRC <Ethernet Address>
238
SCPI Command Set
Description: Set or query the ending source ethernet address.

The source address of transmitted ethernet packets
command defines the ending ethernet address. The
starting ethernet source address
is set with :OUTPut:TELecom:TRAFfic:CONFig:8023:SSRC
Example: None.
:OUTPut:TELecom:TRAFfic:CONFig:8023:EUDorderedsets <0|1>
Description: Set or query the flag which controls User Defined
Ordered Sets.
Example: None.
:OUTPut:TELecom:TRAFfic:CONFig:8023:IG4Xbytes <number Bytes>

Description: Set or query the number of inter-packet gap bytes. The
actual
size of the inter-packet gap will be this number, times 4, plus
12.
Example: None.
:OUTPut:TELecom:TRAFfic:CONFig:8023:LENType <0|1>
Description: Set or query the flag which controls setting the
packet length. If LENType is 0, the packet length
is calculated automatically. If LENType is 1, then
the length is set or queried with
:OUTPut:TELecom:TRAFfic:CONFig:8023:MANLength.
Example: None.
:OUTPut:TELecom:TRAFfic:CONFig:8023:MANLength <Number Bytes>

Description: Set or query the length of the packet header when
:OUTPut:TELecom:TRAFfic:CONFig:8023:LENType is 1.
If LENType is 0, the packet length is calculated
automatically.
Example: None.
:OUTPut:TELecom:TRAFfic:CONFig:8023:MANType <Ethernet-Protocol-
Type>
Description: Set or query the Ethernet Protocol Type. This command is
active
only when :OUTPut:TELecom:TRAFfic:CONFig:8023:TYPe is 1.
Example: None.
:OUTPut:TELecom:TRAFfic:CONFig:8023:MDES <Ethernet-Mask>
Description: Set or query the destination ethernet address mask.
can be ramped between two ethernet addresses. The ethernet
address is incremented between packets. This command
specifies which byte in the ethernet address is incremented.
The starting and ending ethernet destination addresses
are set with :OUTPut:TELecom:TRAFfic:CONFig:8023:SDES and
239
SCPI Commands
:OUTPut:TELecom:TRAFfic:CONFig:8023:EDES.
Example: None.
:OUTPut:TELecom:TRAFfic:CONFig:8023:MSRC <Ethernet-Mask>
Description: Set or query the source ethernet address mask.
can be ramped between two ethernet addresses. The ethernet
address is incremented between packets. This command
specifies which byte in the ethernet address is incremented.
The starting and ending ethernet source addresses
are set with :OUTPut:TELecom:TRAFfic:CONFig:8023:SSRC and
:OUTPut:TELecom:TRAFfic:CONFig:8023:ESRC.
Example: None.
:OUTPut:TELecom:TRAFfic:CONFig:8023:RXPControl <0|1>
Description: Set or query the flag to control RX Pause Control.
Example: None.
:OUTPut:TELecom:TRAFfic:CONFig:8023:SDES <Ethernet-Address>
Description: Set or query the starting destination ethernet address.
command defines the starting ethernet address. The
ending ethernet destination address
is set with :OUTPut:TELecom:TRAFfic:CONFig:8023:EDES.
Example: None.
:OUTPut:TELecom:TRAFfic:CONFig:8023:SFD <offset>
Description: Set or query the Start Frame Delimiter.
Example: None.
:OUTPut:TELecom:TRAFfic:CONFig:802e:SPECtype <?|'CRPAT'|'CJPAT'>
Description: Chooses either the Continuous Random Test Pattern or
Continuous Jitter Pattern for the 802.3ae payload. The pattern is
enabled
or disabled with :OUTPut:TELecom:TRAFfic:CONFig:802e:ESPEcpattern.
Example: None.
:OUTPut:TELecom:TRAFfic:CONFig:8023:SSRC <Ethernet-Address>
Description: Set or query the starting source ethernet address.
command defines the starting ethernet address. The
ending ethernet source address
is set with :OUTPut:TELecom:TRAFfic:CONFig:8023:ESRC.
Example: None.
:OUTPut:TELecom:TRAFfic:CONFig:8023:TXPAmount <interval>
240
SCPI Command Set
Description: Set or query the TX Pause control interval. Units are

in 512 bits. Active when
:OUTPut:TELecom:TRAFfic:CONFig:8023:TXPControl is 1.
Example: None.
:OUTPut:TELecom:TRAFfic:CONFig:8023:TXPControl <0|1>
Description: Set or query the flag which controls TX Pause
Control.
Example: None.
:OUTPut:TELecom:TRAFfic:CONFig:8023:TXRFrames <frames>
Description: Set or query the repeat rate for TX Pause control. Units
are the number of frames between which the pause interval
is repeated. Active when
:OUTPut:TELecom:TRAFfic:CONFig:8023:TXPControl is 1.
Example: None.
:OUTPut:TELecom:TRAFfic:CONFig:8023:TYPe <0|1>
Description: Set or query the flag which controls the Ethernet
Protocol Type setting. If TYPe is 0, the Ethernet
Protocol Type is set automatically to 0x800. If
TYPe is 1, then the value is set with
:OUTPut:TELecom:TRAFfic:CONFig:8023:MANType.
Example: None.
:OUTPut:TELecom:TRAFfic:CONFig:8023:U2Definedset <byte>
Description: Set or query the second byte in the user defined
ordered set.
Example: None.
Description: Set or query the third byte in the user defined
ordered set.
Example: None.
Description: Set or query the fourth byte in the user defined
ordered set.
Example: None.
:OUTPut:TELecom:TRAFfic:CONFig:8023:X43Scramble <0|1>
Description: Set or query the flag which controls the X43 scrambling
of the 802.3 payload. This is not available for LAN
traffic.
Example: None.
241
SCPI Commands
:OUTPut:TELecom:TRAFfic:CONFig:8023:X66Bitblocks <Number-Blocks>
Description: Set or query the repetition rate of transmitting the User
Defined Ordered Set in units of 66 bits. This rate is
active when :OUTPut:TELecom:TRAFfic:CONFig:8023:EUDorderedsets
is 1.
Example: None.
:OUTPut:TELecom:TRAFfic:CONFig:CLOCksettings:APPLy
Description: Command to apply the current clock settings.
Example: None.
:OUTPut:TELecom:TRAFfic:CONFig:CLOCksettings:CLOCk <clock-Type>
Description: Set or query the clock type. Valid values for the clock
type
are
13 TXCLK_GIGE_INTERNAL
14 TXCLK_GIGE_EXTERNAL
15 TXCLK_OC48_INTERNAL
16 TXCLK_OC48_EXTERNAL
Example: None.
:OUTPut:TELecom:TRAFfic:CONFig:DAUTosync <Boolean|?>
Description: Disables auto-synchronization capability. For Bit stream
payload, the OST normally inserts a 2^7 PRBS test pattern to attain
synchronization. If this option is chosen, the test pattern is not
inserted, and the OST will not be able to synchronize.
Example: None.
:OUTPut:TELecom:TRAFfic:CONFig:DELete <Filename>
Description: Deletes the named Traffic configuration file from the
database.
Example:
%% OUTPut:TELecom:TRAFfic:CONFig:exist
[0 11] EXISt TRUE
%% OUTPut:TELecom:TRAFfic:CONFig:delete
[0 0]
242
SCPI Command Set
:OUTPut:TELecom:TRAFfic:CONFig:EXISt <Filename>
Description: Queries the existence of a named traffic configuration
in the database.
Example:
[0 11] EXISt TRUE
%% OUTPut:TELecom:TRAFfic:CONFig:delete
[0 0]
:OUTPut:TELecom:TRAFfic:CONFig:INSError <0|1>
Description: Set or query the flag which controls error insertion.
Example: None.
:OUTPut:TELecom:TRAFfic:CONFig:INSValue <exponent>
Description: Set or query the error injection rate. The rate is
expressed as a log, e.g. INSValue -6 will inject
errors every microsecond. The error injection is
activated with :OUTPut:TELecom:TRAFfic:CONFig:INSError 1.
Example: None.
:OUTPut:TELecom:TRAFfic:CONFig:LAYer <identifier>
Description: Set or query the current layer. Valid values are
0 LAYER_UNFRAMED
1 LAYER_SONET
2 LAYER_SONET_ETHER
3 LAYER_SONET_ETHER_IP
4 LAYER_POS
5 LAYER_ETHER_LAN
6 LAYER_ETHER_IP_LAN
7 LAYER_ATM
8 LAYER_OTN
Example: None.
:OUTPut:TELecom:TRAFfic:CONFig:LIST <Signal-Configuration>
Description: Returns list of attributes in the database for a
signal configuration.
Example: None.
:OUTPut:TELecom:TRAFfic:CONFig:LOAD <Signal-Configuration>
Description: Loads the signal configuration ready for the next test.
Example: None.
:OUTPut:TELecom:TRAFfic:CONFig:OPTics:AMPHjitter <UI>
243
SCPI Commands
Description: Set or query the horizontal jitter amplitude in

unit intervals.
Example: None.
:OUTPut:TELecom:TRAFfic:CONFig:OPTics:AMPVjitter <MHz>
Description: Set or query the vertical jitter amplitude in MHz.
Example: None.
:OUTPut:TELecom:TRAFfic:CONFig:OPTics:APPLy
Description: Applies latest changes made to the optics subsystem
to the OST.
Example: None.
:OUTPut:TELecom:TRAFfic:CONFig:OPTics:C8023sweptset <Boolean|?>
Description: Sets or queries the flag which controls the swept jitter
for
the 10G-E or 10G-L ethernet.
Example:
%% OUTPut:TELecom:TRAFfic:CONFig:OPTics:C8023sweptset ?
[0 16] C8023sweptset 1
:OUTPut:TELecom:TRAFfic:CONFig:OPTics:CTTYphjitter
<?|'std'|'custom'>
Description: Set or query the type of horizontal swept jitter.
Example:
%% :OUTPut:TELecom:TRAFfic:CONFig:OPTics:CTTYphjitter?
[0 17] CTTYphjitter std
:OUTPut:TELecom:TRAFfic:CONFig:OPTics:EEXTinction <0|1>
Description: Enable the flag which controls setting the extinction
ratio. The extinction ratio value can be set with
:OUTPut:TELecom:TRAFfic:CONFig:OPTics:EXTinction.
Example: None.
:OUTPut:TELecom:TRAFfic:CONFig:OPTics:EEYestress <0|1>
Description: Set or query the control flag for changing eye stress
parameters.
Example: None.
:OUTPut:TELecom:TRAFfic:CONFig:OPTics:EFILter <Boolean|?>
Description: Set or query the flag which controls the Bessel filter.
Example:
%% OUTPut:TELecom:TRAFfic:CONFig:OPTics:EFILter?
[0 10] EFILter 0
:OUTPut:TELecom:TRAFfic:CONFig:OPTics:ENAHjitter <0|1>
244
SCPI Command Set
Description: Set or query the flag which controls the horizontal

jitter.
Example: None.
:OUTPut:TELecom:TRAFfic:CONFig:OPTics:ENAVjitter <0|1>
Description: Set or query the flag which controls vertical eye
jitter.
Example: None.
:OUTPut:TELecom:TRAFfic:CONFig:OPTics:EOSNr <0|1>
Description: Set or query the flag which controls changing the
Optical to Signal Noise Ratio.
Example: None.
:OUTPut:TELecom:TRAFfic:CONFig:OPTics:EXTinction <dB>
Description: Set or query the output extinction ratio from the OST in
dB. The flag :OUTPut:TELecom:TRAFfic:CONFig:OPTics:EEXTinction
must be set to 1 for this value to take affect.
Example: None.
:OUTPut:TELecom:TRAFfic:CONFig:OPTics:FRQHjitter <MHz>
Description: Set or query the frequency of the horizontal eye jitter.
Example: None.
:OUTPut:TELecom:TRAFfic:CONFig:OPTics:FRQVjitter <MHz>
Description: Set or query the frequency of the vertical eye jitter.
Example: None.
:OUTPut:TELecom:TRAFfic:CONFig:OPTics:OPTType <Degradation-Type>
Description: Set or query the optical degradation type. Valid values
are
nooptics, 10gbasel, 10gbasee or custom.
Example: None.
:OUTPut:TELecom:TRAFfic:CONFig:OPTics:OSNR <dB>
Description: Set or query the Optical to Signal Noise Ratio.
Example: None.
:OUTPut:TELecom:TRAFfic:CONFig:OPTics:RXMode
<?|'SMODE'|'MMODE'|'DEMODE'>
Description: Set or query the RX mode. Single is supported for
the A3308. Multi and Digital Electrical are supported on the A3318.
Example: None.
245
SCPI Commands
:OUTPut:TELecom:TRAFfic:CONFig:OPTics:SSAMphjitter <Float|?>
Description: Set or query the amplitude of the horizontal jitter in
UI.
Example:
%% OUTPut:TELecom:TRAFfic:CONFig:OPTics:SSAMphjitter?
[0 18] SSAMphjitter 5.00
:OUTPut:TELecom:TRAFfic:CONFig:OPTics:SSDTimehjitter <Integer|?>
Description: Set or query the dwell time for the horizontal jitter in
milliseconds.
Example:
%% OUTPut:TELecom:TRAFfic:CONFig:OPTics:SSDTimehjitter?
[0 19] SSDTimehjitter 100
:OUTPut:TELecom:TRAFfic:CONFig:OPTics:SSFRqhjitter <Float|?>
Description: Set or query the frequency of the horizontal jitter in
MHz.
Example:
%% OUTPut:TELecom:TRAFfic:CONFig:OPTics:SSFRqhjitter?
[0 18] SSFRqhjitter 0.04
:OUTPut:TELecom:TRAFfic:CONFig:OPTics:STYPhjitter
<?|'single'|'digital'|'swept'|'best'>
Description: Set or query the type of horizontal jitter.
Example:
%% OUTPut:TELecom:TRAFfic:CONFig:OPTics:STYPhjitter?
[0 19] STYPhjitter single
:OUTPut:TELecom:TRAFfic:CONFig:OPTics:SWNoptsjitter <Integer|?>
Description: Set or query the number of jitter points used in the
sweep.
Example:
%% OUTPut:TELecom:TRAFfic:CONFig:OPTics:SWNoptsjitter?
[0 17] SWNoptsjitter 10
:OUTPut:TELecom:TRAFfic:CONFig:OPTics:SWPTjitter
Description: Set or query the list of swept jitter points. The list
contains sets of
three numbers:
Frequency in MHz
Amplitude in UI
Dwell time in milliseconds.
Example:
%% OUTPut:TELecom:TRAFfic:CONFig:OPTics:SWPTjitter?
[0 124] SWPTjitter "0.04 5 100 0.1 2 100 0.2 1 100 0.4 0.5 100 1 0.2
100 2 0.1 100 4 0.05 100 10 0.05 100 20 0.05 100 40 0.05 100 "
:OUTPut:TELecom:TRAFfic:CONFig:OPTics:TXMode
<?|'SMODE'|'MMODE'|'DEMODE'|'VEMODE'>
246
SCPI Command Set
Description: Seq or query the TX mode. Single is supported on the

A3308.
The A3318 supports Multi, Digital Electrical and Variable Electrical
modes.
Example: None.
:OUTPut:TELecom:TRAFfic:CONFig:OPTics:TYPHjitter <single|swept>
Description: Set or query the type of horizontal jitter. Single will
keep
the jitter at one point, swept will sweep the horizontal
jitter over the whole range available from the OST.
Example: None.
:OUTPut:TELecom:TRAFfic:CONFig:OPTics:TYPVjitter <sine|square>
Description: Set or query the shape of the vertical jitter. Valid
values
are square wave or sinusoidal wave.
Example: None.
:OUTPut:TELecom:TRAFfic:CONFig:OTN:FECSwitch <Boolean|?>
Description: Sets or queries the flag which will disable Forward
Error Correction in OTN traffic.
Example:
%% OUTPut:TELecom:TRAFfic:CONFig:OTN:FECSwitch?
[0 12] FECSwitch 0
:OUTPut:TELecom:TRAFfic:CONFig:OTN:RXPYldtype <Integer|?>
Description: Set or query the expected OTN payload type.
Example: None.
:OUTPut:TELecom:TRAFfic:CONFig:OTN:SCRSwitch <Boolean|?>
Description: Sets or queries the flag which disables OTN scrambling.
Example:
%% OUTPut:TELecom:TRAFfic:CONFig:OTN:FECSwitch?
[0 12] FECSwitch 0
:OUTPut:TELecom:TRAFfic:CONFig:OTN:TCM1 <Boolean|?>
Description: Set or query whether Tandem Connection Monitor 1
is active.
Example: None.
is active.
Example: None.
247
SCPI Commands
is active.
Example: None.
is active.
Example: None.
is active.
Example: None.
is active.
Example: None.
:OUTPut:TELecom:TRAFfic:CONFig:OTN:TXPYldtype <Integer|?>
Description: Set or query the transmitted Payload Type.
Example: None.
:OUTPut:TELecom:TRAFfic:CONFig:POS:IP
Description: Loads the current IP header.
Example: None.
:OUTPut:TELecom:TRAFfic:CONFig:POS:IP:EDES <IP Address>

Description: Set or query the ending destination Internet Protocol
address.
The destination address of transmitted packets can be ramped
between two addresses, this command defines the ending IP
address. The starting destination address
is set with :OUTPut:TELecom:TRAFfic:CONFig:POS:IP:SDES
Example: None.
:OUTPut:TELecom:TRAFfic:CONFig:POS:IP:ESRC <IP Address>

Description: Set or query the ending source Internet Protocol
address.
The source address of transmitted packets can be ramped
between two addresses, this command defines the ending IP
address. The starting source address
is set with :OUTPut:TELecom:TRAFfic:CONFig:POS:IP:SSRC.
Example: None.
248
SCPI Command Set
:OUTPut:TELecom:TRAFfic:CONFig:POS:IP:IPID <word>
Description: Set or query the identification word in the IP header.
Example: None.
:OUTPut:TELecom:TRAFfic:CONFig:POS:IP:LBLNumber <Label-
Number>
Description: Set or query the current label for Multi protocol Label
Switching. Valid values are 1 to 4.
Example: None.
:OUTPut:TELecom:TRAFfic:CONFig:POS:IP:MDES <Ethernet-Mask>
Description: Set or query the destination Internet Protocol address
mask.
The destination address of transmitted packets can be
ramped between two addresses. The address is incremented
between packets. This command specifies which byte in
the address is incremented. The starting and ending
destination addresses are set with
:OUTPut:TELecom:TRAFfic:CONFig:POS:IP:SDES and
:OUTPut:TELecom:TRAFfic:CONFig:POS:IP:EDES.
Example: None.
:OUTPut:TELecom:TRAFfic:CONFig:POS:IP:MES <0|1>
Description: Set or query the End of Stack flag for the
current MPLS label.
Example: None.
:OUTPut:TELecom:TRAFfic:CONFig:POS:IP:MEX <0-7>
Description: Set or query the three experimental bits in the
current MPLS label.
Example: None.
:OUTPut:TELecom:TRAFfic:CONFig:POS:IP:MHLE <Hop-Level>
Description: Set or query the Hop Level End for the current
MPLS label.
Example: None.
:OUTPut:TELecom:TRAFfic:CONFig:POS:IP:MHLS <Hop-Level>
Description: Set or query the Hop Level Start for the current
MPLS label.
Example: None.
:OUTPut:TELecom:TRAFfic:CONFig:POS:IP:MPLS <0|1>
Description: Set or query the flag which controls
MPLS support.
Example: None.
249
SCPI Commands
:OUTPut:TELecom:TRAFfic:CONFig:POS:IP:MSRC <Ethernet-Mask>
Description: Set or query the source Internet Protocol address mask.
The source address of transmitted packets can be
ramped between two addresses. The address is incremented
between packets. This command specifies which byte in
the address is incremented. The starting and ending
source addresses are set with
:OUTPut:TELecom:TRAFfic:CONFig:POS:IP:SSRC and
:OUTPut:TELecom:TRAFfic:CONFig:POS:IP:ESRC.
Example: None.
:OUTPut:TELecom:TRAFfic:CONFig:POS:IP:MTL <word>
Description: Set or query the Time To Live word in the current
MPLS label.
Example: None.
:OUTPut:TELecom:TRAFfic:CONFig:POS:IP:MTOTalmplslabels <0-4>
Description: Set or query the total number of MPLS labels.
Example: None.
:OUTPut:TELecom:TRAFfic:CONFig:POS:IP:PAYLength <Number-Bytes>
Description: Set or query the number of bytes in the IP payload.
Example: None.
:OUTPut:TELecom:TRAFfic:CONFig:POS:IP:POPTion <Payload-Option>
Description: Set or query the IP payload option. Valid values are
r1 all ones
r0 all zeroes
ralt alternating zeroes and ones
Example: None.
:OUTPut:TELecom:TRAFfic:CONFig:POS:IP:PRTL <Integer|?>
Description: Set or query the protocol word in the IP header.
Example: None.
:OUTPut:TELecom:TRAFfic:CONFig:POS:IP:SDES <IP Address>

Description: Set or query the starting destination Internet Protocol
address.
The destination address of transmitted packets can be ramped
between two addresses, this command defines the starting IP
address. The ending destination address
is set with :OUTPut:TELecom:TRAFfic:CONFig:POS:IP:EDES.
Example: None.
:OUTPut:TELecom:TRAFfic:CONFig:POS:IP:SSRC <IP Address>
250
SCPI Command Set
Description: Set or query the starting source Internet Protocol

address.
The source address of transmitted packets can be ramped
between two addresses, this command defines the starting IP
address. The ending source address
is set with :OUTPut:TELecom:TRAFfic:CONFig:POS:IP:ESRC.
Example: None.
:OUTPut:TELecom:TRAFfic:CONFig:POS:IP:TOS <Service-Type>
Description: Set or query the type of service. Valid values are 0 to
255.
Example: None.
:OUTPut:TELecom:TRAFfic:CONFig:POS:IP:TTL <0-255>
Description: Set or query the Time To Live field in the
Internet Protocol header.
Example: None.
:OUTPut:TELecom:TRAFfic:CONFig:POS:PPP:CONRequest <0-100>
Description: Set or query the maximum number of times a point to point
configuration request will be sent.
Example: None.
:OUTPut:TELecom:TRAFfic:CONFig:POS:PPP:EMPLs <0|1>
Description: Set or query the flag which controls whether
Multi-protocol Label Switching will be negotiated.
Example: None.
:OUTPut:TELecom:TRAFfic:CONFig:POS:PPP:EMRu <0|1>
Description: Set or query the flag which controls whether to
override the default Maximum Receive Unit transmit
and receive sizes.
Example: None.
:OUTPut:TELecom:TRAFfic:CONFig:POS:PPP:EPPP <0|1>
Description: Set or query the flag which controls point-to-point
link negotiation.
Example: None.
:OUTPut:TELecom:TRAFfic:CONFig:POS:PPP:HDLC <0|1>
Description: Set or query the type of point-to-point negotiation.
A value of 0 indicates CISCO HDLC and 1 indicates
RFC 2615.
Example: None.
:OUTPut:TELecom:TRAFfic:CONFig:POS:PPP:IPDesired <IP-address>
251
SCPI Commands
Description: Set or query the desired Internet Protocol address.
Example: None.
:OUTPut:TELecom:TRAFfic:CONFig:POS:PPP:IPNegotiated?
Description: Query the negotiated Internet Protocol address.
Example: None.
:OUTPut:TELecom:TRAFfic:CONFig:POS:PPP:NEGMagic <0|1>
Description: Set or query the flag which controls whether the magic
number should be negotiated.
Example: None.
:OUTPut:TELecom:TRAFfic:CONFig:POS:PPP:NEGipaddress <0|1>
Description: Set or query the flag which controls whether the
Internet Protocol address should be negotiated.
Example: None.
:OUTPut:TELecom:TRAFfic:CONFig:POS:PPP:RTIMeout <seconds>
Description: Set or query the number of seconds to wait between trying
to
negotiate a point-to-point link.
Example: None.
:OUTPut:TELecom:TRAFfic:CONFig:POS:PPP:RXDesired <bytes>
Description: Set or query the number of bytes for the desired
maximum receive unit buffer on the receive side.
Example: None.
:OUTPut:TELecom:TRAFfic:CONFig:POS:PPP:RXSCramble <0|1>
Description: Set or query the flag which controls the payload
scrambling on the receive side.
Example: None.
:OUTPut:TELecom:TRAFfic:CONFig:POS:PPP:TERRequest <1-100>
Description: Set or query the maximum number of retries for
termination requests.
Example: None.
:OUTPut:TELecom:TRAFfic:CONFig:POS:PPP:TXDesired <bytes>
Description: Set or query the maximum size of the receive buffer on
the transmit side.
Example: None.
:OUTPut:TELecom:TRAFfic:CONFig:POS:PPP:TXSCramble <0|1>
252
SCPI Command Set
Description: Set or query the flag which controls payload scrambling

on the transmit side.
Example: None.
:OUTPut:TELecom:TRAFfic:CONFig:POS:RESTart
Description: Command to re-negotiate the Point-to-Point Protocol.
Example: None.
:OUTPut:TELecom:TRAFfic:CONFig:PRBStype <PRBStype>
Description: Set or query the Pseudo-Random Bit Sequence type.
Valid values are
r15 2**15
r23 2**23
r31 2**31
for SONET/SDH mode, and r31 (2**31) for Bit-stream mode.
Example: None.
:OUTPut:TELecom:TRAFfic:CONFig:PRNum <Integer|?>
Description: Set or query the number of consecutive 0's and 1's to
set in the bit-stream payload.
Example: None.
:OUTPut:TELecom:TRAFfic:CONFig:RESet
Description: Command to reset signal traffic configuration to
defaults.
Example: None.
:OUTPut:TELecom:TRAFfic:CONFig:RST
Description: Set the Signal Configuration to SONET bit-stream 2^31
with no optical degradation.
Example: None.
:OUTPut:TELecom:TRAFfic:CONFig:RXINvert <0|1>
Description: Set or query flag which controls automatic
bit inversion of received data.
Example: None.
:OUTPut:TELecom:TRAFfic:CONFig:SAVe <Traffic-Configuration>
Description: Command to save the existing traffic configuration into
the defined file.
Example: None.
:OUTPut:TELecom:TRAFfic:CONFig:SONet:C2BYte <Integer|?>
Description: Set or query the C2 Byte in the SONET overhead. Numbers
are in decimal, between 0 and 255.
253
SCPI Commands
Example:
>> OUTP:TELE:TRAFF:CONF:SONET:C2BYTE?
[0 9] C2BYte 0
>> OUTP:TELE:TRAFF:CONF:SONET:C2BYTE 127
[0 0]
>> OUTP:TELE:TRAFF:CONF:SONET:C2BYTE?
[0 11] C2BYte 127
:OUTPut:TELecom:TRAFfic:CONFig:SONet:J1BYte <Integers|?>
Description: Set or query the first 64 J1 bytes in the SONET overhead.
By default all bytes are zero, except the 49th byte which is 137 (dec)
or
89 (hex). All integers should be entered as decimal numbers between
0 and 255.
Example:
>> OUTP:TELE:TRAFF:CONF:SONET:J1BYTE?
[0 137] J1BYte 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 137 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
>> OUTP:TELE:TRAFF:CONF:SONET:J1BYTE 1 2 3 4 5
[0 0]
>> OUTP:TELE:TRAFF:CONF:SONET:J1BYTE?
[0 135] J1BYte 1 2 3 4 5 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
:OUTPut:TELecom:TRAFfic:CONFig:SONet:K1BYte <Integer|?>
Description: Set or query the K1 byte in the SONET overhead. The
value is a decimal integer.
Example:
>> OUTP:TELE:TRAFF:CONF:SONET:K1BYTE?
[0 9] K1BYte 0
>> OUTP:TELE:TRAFF:CONF:SONET:K1BYTE 127
[0 0]
[0 11] K1BYte 127
:OUTPut:TELecom:TRAFfic:CONFig:SONet:K2BYte <Integer|?>
Description: Set or query the K2 byte in the SONET overhead.
The value is a decimal number, and only the 5 most significant bits
are
available.
Example:
>> OUTP:TELE:TRAFF:CONF:SONET:K2BYTE 248
[0 0]
[0 11] K2BYte 248
:OUTPut:TELecom:TRAFfic:CONFig:STARt
Description: Command to start the current traffic configuration.
254
SCPI Command Set
Example: None.
:OUTPut:TELecom:TRAFfic:CONFig:SWITchpath:APPLy
Description: Command to apply the current switch-path settings to the
OST.
Example: None.
:OUTPut:TELecom:TRAFfic:CONFig:SWITchpath:CALType <type>
Description: Set or query the current calibration type. Valid values
are "LASTUSED", "SAVED", "INITIATE_FULL" and
"INITIATE_HIRES".
Example: None.
:OUTPut:TELecom:TRAFfic:CONFig:SWITchpath:FCALfile <name>
Description: Set or query the name of the calibration which will be
used
to save the data from a full calibration sequence.
Example: None.
:OUTPut:TELecom:TRAFfic:CONFig:SWITchpath:HCALfile <name>
Description: Set or query the name which will be given to the next
high resolution calibration.
Example: None.
:OUTPut:TELecom:TRAFfic:CONFig:SWITchpath:LOSNr <OSNR>
Description: Set or query the lower value for Optical Signal to Noise
Ration for the next high resolution calibration.
Example: None.
:OUTPut:TELecom:TRAFfic:CONFig:SWITchpath:RXGovernor <power>
Description: Set or query the maximum power which will appear at the
"Reference RX" port, when the "Reference RX Switch" is
being used.
Example: None.
:OUTPut:TELecom:TRAFfic:CONFig:SWITchpath:SCALfile <name>
Description: Set or query the name of the current calibration.
Example: None.
:OUTPut:TELecom:TRAFfic:CONFig:SWITchpath:SEDFa <0|1|2>
Description: Set or query the position of the "EDFA Bypass Switch".
A value of 2 means the erbium doped fiber amplifier
(EDFA) is in operation. A value of 1 means the EDFA
is not being used. A value of 0 means that the OST
has control of the switch.
255
SCPI Commands
Example: None.
:OUTPut:TELecom:TRAFfic:CONFig:SWITchpath:SMONitor <0|1>
Description: Set or query the "Monitor Port Switch". A value of 2
means the Monitor Port is connected to the transmit
side. A value of 1 means the Monitor Port is connected
to the receive side. A value of 0 means that the
OST has control of the switch.
Example: None.
:OUTPut:TELecom:TRAFfic:CONFig:SWITchpath:SPPL <0|1|2>
Description: Set or query the Path Penalty Loop switch. A value of
2 means that the Path Out and Path In are not
being used. A value of 1 means that the Path In
and Path Out ports are in the receive side. A value
of 0 means that the OST has control of the switch.
Example: None.
:OUTPut:TELecom:TRAFfic:CONFig:SWITchpath:SRRef <0|1|2>
Description: Set or query the Reference RX Switch. A value of 0
means that Ref RX ports are not connected to the
RX side. A value of 1 means that the Ref RX ports
are connected in to the receive side.
Example: None.
:OUTPut:TELecom:TRAFfic:CONFig:SWITchpath:STRef <0|1>
Description: Set or query the Reference TX Switch. A value of 0
means that the TX Ref ports are not connected in
to the transmit side. A value of 1 means that the
TX Ref ports are connected in to the transmit side.
Example: None.
:OUTPut:TELecom:TRAFfic:CONFig:SWITchpath:UOSNr <OSNR>
Description: Set or query the upper Optical to Signal Noise Ratio
for the next high resolution calibration.
Example: None.
:OUTPut:TELecom:TRAFfic:CONFig:TABMain <Page-Name>
Description: Set or query the current traffic configuration screen
name.
Example: None.
:OUTPut:TELecom:TRAFfic:CONFig:TABSub <Page-Number>
Description: Set or query the current sub-page number displayed
on the screen.
Example: None.
256
SCPI Command Set
:OUTPut:TELecom:TRAFfic:CONFig:TXINvert <0|1>
Description: Set or query flag which controls automatic
bit inversion of transmitted traffic.
Example: None.
:RST
Description: Resets the OST, stopping all running tests.
Example:
:RST
:SYSTem:BEEP
Description: Makes the 3301 beep.
Example: None.
:SYSTem:CLIEnt <binary|ASCII>
Description: Sets the communication type between comServ and the
client to binary.
The initial communication mode is ASCII.
In ASCII mode, comServ messages are formatted as follows
"Error Code" "Number of succeeding pairs" "optional-data"
"Error Code" is a 4 character array representing the error code
"Number of succeeding pairs" is a 4 character array that
represents the number of pairs of data to follow
"optional-data"
In binary mode, comServ messages are formatted as follows
"Error Code" "number of bytes to follow" "optional-data"
where "Error Code" is an integer representing the error code
"number of bytes to follow" is an integer representing
the number of bytes of data that will follow
"optional-data"
Example:
To set the binary communication type to binary
:SYSTem:CLIEnt binary
:SYSTem:LOGin:ADMinistrator <password>
Description: Allows customers who know the password
to run administrative tasks.
Example:
:system:login:admin Password
:SYSTem:LOGin:CALibration <password>
Description: Allows customer to run calibration commands.
Example: None.
:SYSTem:LOGin:USER <password>
Description: Changes privilege back to normal.
Example: None.
257
SCPI Commands
:SYSTem:NOVPair <Name-Value pair flag>

Description: Sets the configuration parameter for Name-Value
response.
When set to 1, subsequent SCPI commands will be returned as
"NAME VALUE" pairs, otherwise the SCPI response is "VALUE"
only.
Example: None.
:SYSTem:REMote <0|1>
Description: Set or query the flag to indicate of the OST is in
remote mode.
Example: None.
:SYSTem:SHUTdown <ALL|node-name>
Description: Allows remote nodes with system privileges to shut down
this OSTC and connected OSTs.
Example:
To shut down the system remotely:
:SYSTem:LOGin:ADMinistrator Password
:SYSTem:SHUTdown ALL
:SYSTem:SYNChronize
Description: Synchronizes the OST system clock with the OSTC.
Example: None.
258
SCPI Return Codes
13.2 SCPI Return Codes

TABLE 13-1: SCPI Return Codes
Name Number Description:

CSUCCESS 0 /* success */
CESYN 1025 /* syntax error */
CESOCK 1026 /* socket error */
CEPIPE 1027 /* pipe error */
CENODEV 1028 /* no such device */
CEIO 1029 /* I/O error */
CSOCKCLOSE 1030 /* socket close */
CNOARGS 1031 /* argument error */
CDENIED 1032 /* request denied */
CNOCONN 1033 /* not connected */
CAPPLERR 1034 /* unspecified application error */
CAPPLTAERR 1035 /* application data error */
CAPPPCIERR 1036 /* pci write/read verification error */
CENOMEM 1037 /* memory allocation error */
CIQTEST 1038 /* IQ test failure */
CMONACC 1039 /* Control access denied monitor access only */
CFOPEN 1040 /* File Open eror */
CFCREATE 1041 /* File Create error */
CNOTREADY 1042 /* (Data) Not Ready */
CTERMACTION 1043 /* Terminate Action (not an error) */
CHRDWRERROR 1044 /* Hardware Error */
CDATAEMPTY 1045 /* Requested Data Not in Shared Memory. Try again later ? */
CEFTP 1046 /* File transfer failure */
COPC 1047 /* SCPI operation not complete */
CTSTERR 1048 /* Device under test shows unusual/unexpected behavior */
CSTKEMPTY 1049 /* Stack empty */
CBUFOVERRUN 1050 /* Stack buffer overrun error */
CBUFSHORT 1051 /* Dest. buffer short, el cheapo */
CLOS 1052 /* Loss Of Signal */
CEXEC 1053 /* Cannot execute */
CPKTNXM. 1054 /* Tx packet has not been transmitted */
COOR 1055 /* Out Of Range */
CREM 1056 /* Remote Enabled */
COSNROOR 1058 /* OSNR Out Of Range */
CEROOR 1059 /* ER Out Of Range */
COMAOOR 1060 /* OMA Out Of Range */
COORLO 1061 /* Out of Range on low side (below min) */
259
SCPI Commands
TABLE 13-1: SCPI Return Codes
Name Number Description:

COORHI 1062 /* Out of Range on high side (above max) */
CSWNCP 1063 /* Switch NOT in correct position */
CCALIB 1064 /* Calibration not loaded correctly */
CUSERLIMIT 1065 /* request exceeds user specified limit */
CINIT 1066 /* value not initialized */
CDBINIT 1067 /* database not initialized */
CDBQUERY 1068 /* database query error */
CNOENTRY 1069 /* database such row */
CEBUF 1070 /* invalid buffer */
CJITNS 1071 /* jitter not selected */
CNOICS 1072 /* no instrument control server available */
CICSERR 1073 /* instrument control server error */
CNOLICENSE 1074 /* Feature not licensed, please call Customer Support */
CNOFREQCAL 1075 /* Calibration file not present for this frequency */
CUNSUPPRATE 1076 /* Unsupported Bit Rate */
260
SCPI Return Codes
261
SCPI Commands
262
CHAPTER 14 Quick Start Guides
The following pages are the Quick Start Guides for the A3308 10 Gb/s Optical Standards Tester and
A3318 850 nm/Electrical OST Interface.
263
Quick Start Guides
14.1 A3308 10 Gb/s Optical Standards Tester
14.1.1 WARNINGS!
A3308 10 Gb/s Optical Standards Tester Warnings
REMINDER! Clean the filters on the rear panel fans periodically to keep air flow at a maximum to
allow the OST to keep cool.
14.1.2 STEP 1 - Unpacking and Contents

Remove all contents from the box and place the Optical Standards Tester (OST) on a stable table.
Verify that all the accessories are included.
A3308 10 Gb/s Optical Standards Tester
264
AC/DC Power Supply
Sacrificial Jumper Cables 10/100 LAN Cable
DC Power Cable Keys & Register Memory Stick
Calibration Certificate Keyboard A3308 OST User’s Manual
265
Quick Start Guides
14.1.3 STEP 2 - Power Connections
A. Plug one end of the DC Power Cable into the connector on the A3301 labeled POWER OUT. Plug
the other end into the A3308 connector labeled 24 VDC IN. Hand tighten each screw on the DIN
connectors.
NOTE: The DIN connectors are keyed to match the connectors on the A3301 and A3308 can
only be connected one way.
B. Verify that the power switch on the AC/DC Power Supply is in the OFF position.
C. Plug the DIN connector of the AC/DC Power Supply into the connector on the A3301 labeled
POWER IN. Hand tighten each screw on the DIN Connectors.
D. Plug the AC/DC Power Supply into a wall receptacle.
266
14.1.4 STEP 3 - LAN Connections
A. Plug one end of the 10/100 LAN Cable into the connector labeled 10/100 OUT on the A3301 and
plug the other end into the connector labeled FROM OST/OSTC.
B. Make sure the RJ45 Connectors “click” into place. Verify that the LAN Cable is securely seated by
pulling lightly on each connector.
267
Quick Start Guides
14.1.5 STEP 4 - Power Up
A. Plug the AC/DC Power Supply into a wall receptacle.
B. Verify that the black A33XX POWER Emergency Shutoff rocker switch on the rear panel of the
A3308 is turned to the ON position.
C. Turn the power switch on the AC/DC Power Supply to the ON position. The A3301 will begin the
Power Up cycle.
D. Press the square ON/STANDBY power switch on the A3308 to the ON position. The power switch
LED will flash red while the A3308 is powering up. When the power switch LED turns to a steady
green, the A3308 is operational.
E. The A3301 will poll the Ethernet Bus for the LAN connection to the A3308 for several minutes. If
the A3301 does not detect the A3308, it will display a Troubleshooting Guide on the screen.
F. Once the A3301 is communicating with the A3308, the Traffic Configuration Setup will appear on
the screen.
NOTE: To Power Down the OST, select the ADMIN Tab at the bottom of the screen. Select
Shut Down System, then click the OK button. Wait for the OST to Power Down before
turning off the AC/DC Power Supply.
268
14.1.6 STEP 5 - Self Tests
A. Connect one end of a perfectly clean Sacrificial Jumper Cable into the TRANSMIT TO DUT
connector and the other end into the RECEIVE FROM DUT connector.
B. Turn the LASER CONTROL key to the ON position.
C. Press the green START Arrow located on the Graphical User Interface screen to begin generating
traffic.
D. Press the SENSITIVITY icon located under RX Tests, and then press the green START Arrow. If
the STATUS displays a PASS at the conclusion of the Sensitivity Test, the OST is functioning
properly. Press the red EXIT Arrow to return to the Main Menu.
E. Allow the OST to warm up for one hour. Press the INTERNAL PROC. CTRL. Tab to bring up the
Internal Process Control Menu.
269
Quick Start Guides
F. Follow the directions on the screen to perform a Self Test. Passing all Self Tests confirms that the
OST’s calibration is OK and is providing the same range of test results as prior to being shipped from
Circadiant Systems. Pressing the green ACCEPT RESULTS check mark saves the Self Test results on
the OST’s Internal Process Control charts.
G. Attach all nine Sacrificial Jumper Cables. Congratulations, you are ready to begin testing.
ALERT!!! Sacrificial Jumper Cables are provided with the OST to protect the connectors and
fibers on the A3308 from dirt and damage. It is strongly recommended that these
jumpers be installed whenever the system is being used. Damage to the optical
connectors on the OST is NOT covered under the Warranty.
14.1.7 Registration & Technical Support

Please remember to register your 10 Gb/s OST online at the Customer Support section of the
Circadiant website at: http://www.circadiant.com/support/
By registering, you will be assured of receiving important updates and Technical Support for your
OST.
Contact Circadiant Technical Support by calling 866-630-2510 or visiting the Circadiant website at:
http://www.circadiant.com/support/
270
A3318 850 nm/Electrical OST Interface
14.2 A3318 850 nm/Electrical OST Interface
14.2.1 WARNINGS!
A3318 850 nm/Electrical OST Interface Warnings
14.2.2 STEP 1 - Unpacking and Contents

A. Read all safety warnings on the WARNINGS page of this Quick Start Guide.
B. Verify the OST is fully operational, is calibrated and the laser key is set to OFF.
C. Remove all contents from the box and place the A3318 Optical Standards Tester (OST) on a stable
table. Verify that all the accessories are included.
271
Quick Start Guides
Ethernet Cable
One Coax Cable

AC Power Cable
Two Single Mode Cables

One 50/125 µm Multi-Mode Cable
One 62/125 µm Multi-Mode Cable
Two Laser ON/OFF Keys
272
14.2.3 STEP 2 - Basic Connections
Power Connection
A. Connect the AC power cable into either the top or bottom redundant power supply receptacle.
B. Connect the plug into an AC outlet.
C. Optional: Connect a second AC power cable for power supply redundancy.
NOTE: For eye safety, the power switch should be pushed to the ON position only after all
optical cable connections are made. A green LED will illuminate when power is
detected.
Ethernet Connection
A. Attach one end of the Ethernet cable to the A3308 connector marked with an arrow pointing inside
the circle next to “OSTC” (Optical Standards Tester Controller) and the other end to the A3318
connector marked with an arrow pointing inside the circle next to “OSTC”.
273
Quick Start Guides
B. Make sure the RJ45 connectors “click” into place. Verify that the Ethernet cable is securely seated
by pulling lightly on each connector.
14.2.4 STEP 3 - Optical Connections
A. Connect a single mode cable between the A3318 RX SM Connector and the A3308 To DUT
Connector.
B. Connect a single mode cable between the A3318 TX SM Connector and A3308 From DUT
Connector.
C. Connect a 62.5/125 µm cable to the A3318 RX MM Connector.
D. Connect a 50/125 µm cable to the A3318 TX MM Connector.
E. Connect the coax cable between the A3318 REF CLK In Connector and the A3308 TX REF Out
Connector. Use a torque wrench to tighten the SMA connections to 1 Nm.
F. Insert one of the Laser Control Keys into the A3318.
274
14.2.5 STEP 4 - Self Test
A. Connect one end of the 62.5/125 µm cable to the 50/125 µm cable. Turn the A3318 power switch
to the ON position and wait approximately 2 minutes for the A3318 to boot up.
B. Press the “Admin” tab on the A3301 GUI and select “Connect to A3318”.
C. Enable “Connect to (A3318 Serial Number)” and press “OK”.
D. Press “Continue”. This will restart the OST and detect the A3318.
E. Turn the A3318 and A3308 Laser Control Key to the ON position.
F. Press the “Mode Selection” tab on the A3301 GUI, select TX Mode as 850 nm Multi-Mode and
select RX Mode as 850 nm Multi-Mode.
G. Press the “Traffic” tab and select Bitstream.
H. Press the “Degradation” tab and select No Optical Degradation.
I. Press the “Switch Setup” tab and confirm AUTO is displayed over the three switches.
J. Press the “Clock Settings” tab and select 10.3 Gb/s bit rate using “Internal” clock source.
K. Press the green start arrow to begin generating traffic.
L. Press the “Sensitivity” icon under “RX Tests”.
M. Press the “Load” icon and press “OK” to load the default test settings.
N. Press the green “Start” arrow. If the STATUS displays a PASS at the conclusion of the test, the
OST and A3318 are functioning properly. Press the red EXIT arrow to return to the main menu.
NOTE: To disconnect the A3318 from the OST, press the “Admin” tab, press the “Connect to
A3318” icon and deselect the box next to “Connect to (A3318 Serial Number)”.
275
Quick Start Guides
14.2.6 STEP 5 - Process Control Charts
A. Allow the OST and A3318 to warm up for one hour. Press the “Internal Proc. Ctrl.” tab to bring up
the Internal Process Control menu.
B. Follow the directions on the screen to perform an A3318 Multi-Mode SelfTest. Passing all
SelfTests confirms that the calibration of the OST and A3318 is OK and is providing the same range
of test results as prior to being shipped from Circadiant Systems. Pressing the green ACCEPT
RESULTS check mark saves the SelfTest results as OST Internal Process Control charts.
ALERT!!! The short Sacrificial Jumper Cables are provided with the OST and A3318 to protect
the connectors on the from dirt, scratches and damage. It is strongly recommended that
these jumpers be installed whenever the system is being used. Damage to the optical
connectors on the OST and A3318 is NOT covered under the Warranty.
14.2.7 Registration & Technical Support

Please remember to register your A3318 850 nm/Electrical OST Interface online at the Customer
Support section of the Circadiant website at: http://www.circadiant.com/support/
By registering, you will be assured of receiving important updates and Technical Support for your
A3318 850 nm/Electrical OST Interface.
Contact Circadiant Technical Support by calling 866-630-2510 or visiting the Circadiant website at:
http://www.circadiant.com/support/
276
CHAPTER 15 Procedures
The following pages are documents outlining the Procedures for:
• “Cleaning the OST Optical Interfaces” on page 278

• “1550 nm/1310 nm Wavelength Calibration” on page 282
• “Cleaning the OST Airflow Fans” on page 290
277
Procedures
15.1 Cleaning the OST Optical Interfaces
UHDOZRUOGRSWLFDOWHVWLQJ
&OHDQLQJWKH267
2SWLFDO,QWHUIDFHV
&DUHIXOFOHDQLQJDQGFDUHRIRSWLFDO
LQWHUIDFHVRQWKH267LVHVVHQWLDOIRUSURSHU
PHDVXUHPHQWV&OHDQLQWHUIDFHVDUHFULWLFDO
IRUSURSHUVHQVLWLYLW\PHDVXUHPHQWVDQGFRXOG
PHDQWKHGLIIHUHQFHEHWZHHQJRRGDQGEDG
PHDVXUHPHQWV
,QSUHSDUDWLRQVWDUWZLWK
TXDOLW\FOHDQLQJSURGXFWVDQGDQ
XQFRQWDPLQDWHGZRUNVXUIDFH
$3UHPRLVWHQHG´2SWLFDO*UDGHµFRWWRQ
ZLSHVZRUNWKHEHVWIRUUHPRYLQJD
YDULHW\RIGLUWDQGGXVWLVRSURS\O
DOFRKROVKRXOGEHWKHRQO\FOHDQLQJ
DJHQWXVHGIRUWKHSXUSRVHRIFOHDQLQJ
ÀEHURSWLFFRQQHFWRUV$FDQRI´2SWLFDO
*UDGHµGU\FRPSUHVVHGDLULVKHOSIXOIRU
EORZLQJRXWORRVHGHEULV
7KHVHSURGXFWVDUHDYDLODEOHDW
KWWSZZZÀEHULQVWUXPHQWVDOHVFRP
/LQNWR´'U\:LSHVµ
KWWSVZZZÀVFDWDORJFRPGHIDXOWDVS":0)1 :HE3URGX
FW&DWDORJ,WHP :0)7 ' :3* (3+RPHSDJH2QOLQH :7,'
:5(& :.(< >@
/LQNWR´,VR:LSHVµ
KWWSVZZZÀVFDWDORJFRPGHIDXOWDVS":0)1 :HE3URGX
FW&DWDORJ,WHP :0)7 ' :3* (3+RPHSDJH2QOLQH :7,'
:5(& :.(< >@
278
Cleaning the OST Optical Interfaces
&DUHIXOO\UHPRYHWKH%XONKHDG
&RQQHFWRUV
$7XUQRII/DVHU
%3XVKGRZQZDUGRQEDUODWFK
279
Procedures
&*HQWO\VOLGHFRQQHFWRURXWZDUG
&OHDQWKH)HUUXOH
$&DUHIXOO\EORZGU\FRPSUHVVHGDLUJHQWO\
RYHUWKHWHVWIHUUXOH
%2QFHORRVHGLUWKDVEHHQEORZQDZD\
DSSO\DQ,VRSURS\OPRLVWHQHGFOHDQLQJ
ZLSHRYHUWKHVXUIDFHRIWKHWHVW
IHUUXOH0DNHVXUH\RXUKDQGVKDYH
EHHQWKRURXJKO\ZDVKHGDQGGULHG'LUW\
KDQGVFRQWDLQRLOVWKDWFDQZLFNLQWRWKH
,VRSURS\OZLSHDQGGHIHDWWKHFOHDQLQJ
SURFHVV
280
Cleaning the OST Optical Interfaces
&'U\WKHIHUUXOHZLWKDGU\FRWWRQZLSH
DQGLQVSHFWWKHIHUUXOHIRUFOHDQOLQHVV$
GHYLFHVXFKDVWKH:HVWRYHU)LEHU2SWLF
,QVSHFWLRQ6\VWHPLVUHFRPPHQGHG
'5HSHDWSURFHVVXQWLOLQWHUIDFHLVFOHDQ

()LQDOO\FDUHIXOO\UHSODFHWKHEXONKHDG
MDFN/LIWKDQGOHXQWLOLWJHQWO\VQDSV
LQWRSODFH
:$51,1*
1HYHU XVH D WHOHVFRSLF LQVSHFWLRQ VFRSH RQ WKH WUDQVPLW LQWHUIDFH 7KH RSWLFDO
DPSOLÀHUVRIWKHV\VWHPFUHDWHKDUPIXOOHYHOVRIOLJKWWKDWZLOOGDPDJHWKHKXPDQ
H\H
DJSDBEJBOUTZTUFNT JOD
LPSHULDOZD\VXLWHF
DOOHQWRZQSD
SKRQHWROOIUHH
ID[HPDLOLQIR#FLUFDGLDQWFRP
ZZZFLUFDGLDQWFRP
&N &RS\ULJKW&LUFDGLDQW6\VWHPV,QF
$OO5LJKWV5HVHUYHG
281
Procedures
15.2 1550 nm/1310 nm Wavelength Calibration
QPQP
:DYHOHQJWK&DOLEUDWLRQ
2SWLFDO6WDQGDUGV7HVWHUV267VZLOODFFXUDWHO\WHVW $IWHUFDOLEUDWLRQ267VZLWKQPWUDQVPLWWHUV
ERWKQPDQGQPWUDQVPLWWHUVDQGUHFHLYHUV ZLOOWHVWUHFHLYHUVWKDWZLOOEHRSHUDWHGDW
ZKHQGLIIHUHQFHVEHWZHHQWUDQVPLWWHUZDYHOHQJWKVDQG QP6LPLODUO\DIWHUFDOLEUDWLRQ267VZLWKQP
UHFHLYHURSHUDWLRQDOZDYHOHQJWKVDUHFRPSHQVDWHGZLWK WUDQVPLWWHUVZLOOWHVWUHFHLYHUVWKDWZLOOEHRSHUDWHG
DFDOLEUDWLRQIDFWRU7KLVQPQP:DYHOHQJWK DWQP267VZLWKHLWKHUQPRUQP
&DOLEUDWLRQ3URFHGXUHSURYLGHVVWHSE\VWHSLQVWUXFWLRQV WUDQVPLWWHUVZLOOWHVWQPRUQPWUDQVPLWWHUV
IRUFDOLEUDWLQJWKH267WRWHVWQPDQGQP DIWHUZDYHOHQJWKFDOLEUDWLRQ
WUDQVPLWWHUVDQGUHFHLYHUV
2677UDQVPLWWHU:DYHOHQJWK&DOLEUDWLRQ4XLFN
5HIHUHQFH
'875HFHLYHU
2677\SH &DOLEUDWH267 2SHUDWLRQDO 267&DOLEUDWLRQ)DFWRU
:DYHOHQJWK
QP6LQJOH0RGH 7; QP $SSUR[LPDWHO\G%
QP6LQJOH0RGH 7; QP $SSUR[LPDWHO\G%
QP6LQJOH0RGH 7; QP 1RW5HTXLUHG
2675HFHLYHU:DYHOHQJWK&DOLEUDWLRQ4XLFN
5HIHUHQFH
'877UDQVPLWWHU
2677\SH &DOLEUDWH267 2SHUDWLRQDO 267&DOLEUDWLRQ)DFWRU
:DYHOHQJWK
(QWHU'87WUDQVPLWWHU
QPRUQP6LQJOH
5; QP ZDYHOHQJWKIRUDXWRPDWLFIDFWRU\
0RGH
FDOLEUDWLRQ
(QWHU'87WUDQVPLWWHU
QP6LQJOH0RGH 5; QP ZDYHOHQJWKIRUDXWRPDWLFIDFWRU\
FDOLEUDWLRQ
282
1550 nm/1310 nm Wavelength Calibration
%DFNJURXQG
7KHPHDVXUHGVHQVLWLYLW\RIDQRSWLFDOUHFHLYHUZLOOGLIIHU 7KLVPHDQVWKDWIRUDQPWUDQVPLWWHUWREH
GHSHQGLQJRQZKHWKHULWLVWHVWHGZLWKOLJKWHQHUJ\DW FDOLEUDWHGWRVLPXODWHDQPWUDQVPLWWHUDGGLWLRQDO
QPRUDWQP$WWKHPRVWIXQGDPHQWDOOHYHO SKRWRQVDUHQHHGHGDQGDSRVLWLYHW\SLFDOO\
OLJKWLVFDUULHGE\SKRWRQV7KHVHQVLWLYLW\GLIIHUHQFHLV G%FDOLEUDWLRQIDFWRUPXVWEHXVHG)RUDQP
FDXVHGE\WKHIDFWWKDWHQHUJ\FDUULHGE\DSKRWRQLV WUDQVPLWWHUWREHFDOLEUDWHGWRVLPXODWHDQP
GHSHQGHQWRQLWVZDYHOHQJWK7KLVLVVXHLVGLVFXVVHGLQ WUDQVPLWWHUIHZHUSKRWRQVDUHQHHGHGDQGDQHJDWLYH
PRVW4XDQWXP0HFKDQLFVWH[WERRNV W\SLFDOO\G%FDOLEUDWLRQIDFWRUPXVWEHXVHG

$WQPHDFKSKRWRQFDUULHV/(66OLJKWHQHUJ\WKDQ 'HSHQGLQJRQWKHDFFXUDF\GHVLUHGFDOLEUDWLRQIDFWRUV
SKRWRQVDWQPWKHUHIRUHLIDSRZHUPHWHUPHDVXUHV UDQJHIURPWKHXVHRIW\SLFDOYDOXHVWRXVLQJSRZHU
²G%PRISRZHUDWQPDQGWKHZDYHOHQJWK PHWHUREVHUYDWLRQVRUPDNLQJFDUHIXOUHVSRQVLYLW\
ZHUHWRVKLIWWRQPPRUHSKRWRQVDUHUHTXLUHG PHDVXUHPHQWV0DQ\HQJLQHHUVXVHDW\SLFDOYDOXHWR
WRSURGXFHWKHVDPH²G%PRISRZHU6RWKH6$0( FRPSHQVDWHIRUWKHGLIIHUHQFHEHWZHHQQPDQG
DPRXQWRISRZHUDWDGLIIHUHQWZDYHOHQJWKLVFDUULHGE\D QP2WKHUVVZLWFKWKHZDYHOHQJWKPRGHRIDQRSWLFDO
',))(5(17QXPEHURISKRWRQV$IWHUEHLQJDEVRUEHGE\ SRZHUPHWHUEHWZHHQQPDQGQPWRREWDLQD
DQRSWLFDOGHWHFWRUHDFKSKRWRQFUHDWHV21(HOHFWURQ FDOLEUDWLRQIDFWRU9HU\SUHFLVHFDOLEUDWLRQYDOXHVPD\
KROHSDLUDQGWKXVDWLQ\DPRXQWRISKRWRFXUUHQWD EHDWWDLQHGE\VDPSOLQJRUXQLWVGHSHQGLQJRQWKH
VWUHDPRIHOHFWURQV YDULDWLRQRIWKHXQLWVDQGWKHQDYHUDJLQJWKHDFWXDO
SKRWRFXUUHQWLQWKHELDVFLUFXLWRI'87SKRWRGHWHFWRUVIRU
*LYHQWKH6$0(DPRXQWRIOLJKWSRZHUWKHUHDUHPRUH ERWKZDYHOHQJWKVRIOLJKW
SKRWRQVDQGWKXVPRUHHOHFWURQKROHSDLUVDWQP
WKDQDWQPDQGWKHUHIRUHPRUHSKRWRFXUUHQWDW
ORQJHUZDYHOHQJWKV7KHKLJKHUSKRWRFXUUHQWFUHDWHVD
ORJLQFUHDVHLQVHQVLWLYLW\
283
Procedures
7;5;%DU
&DOLEUDWLRQ3URFHGXUH QP2677;6LPXODWHVQP
:LWKDQP267WUDQVPLWWHUXVHD²G%FDOLEUDWLRQ 7RKDYHWKHQP2677;VLPXODWHDQPVRXUFHD
IDFWRUWRVLPXODWHQP7KH²G%FDOLEUDWLRQ G%FDOLEUDWLRQIDFWRUPXVWEHHQWHUHGLQWKH´287WR
IDFWRULVDW\SLFDOYDOXH<RXPD\VXEVWLWXWHDGLIIHUHQW '87µVLGHRIWKH7;5;EDU
YDOXHVSHFLÀFWRD'87UHFHLYHUW\SH
3UHVVWKH´&DO)DFWRUµEXWWRQORFDWHGRQWKHOHIWVLGH
RIWKH5;7;EDU
QP2677;WR6LPXODWHQP
3UHVVWKHER[QH[WWR´&DO)DFWRUµEXWWRQWRRSHQ
7RKDYHWKHQP2677;VLPXODWHDQPVRXUFHD WKH´7UDQVPLW&DOLE)DFWRUµ,QSXW1XPEHU3DG
²G%FDOLEUDWLRQIDFWRUPXVWEHHQWHUHGLQWKH´287WR
'87µVLGHRIWKH7;5;EDU
3UHVVWKH´&DO)DFWRUµEXWWRQORFDWHGRQWKHOHIWVLGH
RIWKH5;7;EDU
3UHVVWKHER[QH[WWRWKH´&DO)DFWRUµEXWWRQWRRSHQ
WKH´7UDQVPLW&DOLE)DFWRUµ,QSXW1XPEHU3DG
&KDQJHWKHVLJQWRSRVLWLYHHQWHUDQGZKHQ
LVGLVSOD\HGSUHVV´2.µWRFRQÀUPWKHQXPEHUDQG
´2.µWRDSSO\WKHFDOLEUDWLRQIDFWRU
&KDQJHWKHVLJQWRQHJDWLYHHQWHUDQGZKHQ
LVGLVSOD\HGSUHVV´2.µWRFRQÀUPWKHQXPEHUDQG
´2.µWRDSSO\WKHFDOLEUDWLRQIDFWRU
284
2675;QP6HWXS 2675;QP6HWXS
7RVHWXSWKH267WRUHFHLYHQPOLJKWMXVWFKDQJH 7RVHWXSWKH267WRUHFHLYHQPOLJKWMXVWFKDQJH
WKHLQFRPLQJZDYHOHQJWKEXWWRQDQGWKHSRZHUPHWHUVLQ WKHLQFRPLQJZDYHOHQJWKEXWWRQDQGWKHSRZHUPHWHUVLQ
WKH267ZLOODXWRPDWLFDOO\EHFDOLEUDWHGWRWKHLUQP WKH267ZLOODXWRPDWLFDOO\EHFDOLEUDWHGWRWKHLUQP
IDFWRU\VHWWLQJ IDFWRU\VHWWLQJ
3UHVVWKHZDYHOHQJWKEXWWRQRQWKHULJKWVLGHRIWKH 3UHVVWKHZDYHOHQJWKEXWWRQRQWKHULJKWVLGHRIWKH
5;7;EDUWRRSHQWKH´6HW5HFHLYH/DPEGDµ,QSXW 5;7;EDUWRRSHQWKH´6HW5HFHLYH/DPEGDµ,QSXW
1XPEHU3DG 1XPEHU3DG
(QWHU´µ (QWHU´µ
3UHVV´2.µ 3UHVV´2.µ
285
Procedures
6HWXSZLWK&RPSHQVDWLRQIRU&DEOH 3UHVV´$XWR&DOLEUDWHµ

&RQQHFWRU/RVVHV%HWZHHQWKH267DQG 1RWHWKH´&DO)DFWRUµYDOXH
'87

2677;6LGH&DEOH&RQQHFWRU:DYHOHQJWK
&DOLEUDWLRQ6HWXS
7RUHPRYHWKHFDEOHORVVEHWZHHQWKH267·V
WUDQVPLWWHUDQGWKH'87·VUHFHLYHUIURPWKHWHVW
UHVXOWVDQGDOVRDGMXVWIRUQPRUQP
RSHUDWLRQ
6HWWKHZDYHOHQJWKRQWKHULJKWVLGHRIWKH
5;7;EDUWRQPIRU267VZLWKDQP
7UDQVPLWWHU)RU267VZLWKDQPWUDQVPLWWHU
VHWWKHZDYHOHQJWKWRQP7KH267·V
WUDQVPLWWHUZDYHOHQJWKLVGLVSOD\HGRQWKHOHIW
VLGHRIWKH7;5;EDU $GGWKH´&DO)DFWRUµIURP6WHSWRWKH
DSSURSULDWHZDYHOHQJWKFDOLEUDWLRQIDFWRU
6HH´%DFNJURXQGµDERYHIRUDGLVFXVVLRQRI
XVLQJDW\SLFDOYDOXHDSRZHUPHWHUGLIIHUHQFH
3UHVVWKH´&DO)DFWRUµEXWWRQORFDWHGRQWKHOHIW RUDUHVSRQVLYLW\PHDVXUHPHQWWRREWDLQWKH
VLGHRIWKH5;7;EDU ZDYHOHQJWKFDOLEUDWLRQIDFWRU
7;&DOLEUDWLRQIDFWRU
QP267
3UHVV´&DO)DFWRU$VVLVWDQWµ DSSUR[LPDWHO\G%
7;&DOLEUDWLRQIDFWRU
QP267
DSSUR[LPDWHO\G%
7KLVVXPLVWKHFRPELQHGFDOLEUDWLRQIDFWRUWKDW
LQFOXGHVWKHORVVRIWKHFRQQHFWRUVFDEOHVDQG
WKHZDYHOHQJWKRIIVHW
3UHVVWKHER[QH[WWR´&DO)DFWRUµWRRSHQWKH
´7UDQVPLW&DOLE)DFWRUµ,QSXW1XPEHU3DG
3UHVV´$XWR&DO0RGH+HOSµWRVHHDSLFWXUHRI
KRZWKHFDEOHVVKRXOGEHFRQÀJXUHG
(QWHUWKHFRPELQHGFDOLEUDWLRQIDFWRUIURP6WHS
DQGSUHVV´2.µDQG´2.µ
286
2675;6LGH&DEOH&RQQHFWRU:DYHOHQJWK 3UHVV´$XWR&DO0RGH+HOSµWRVHHDSLFWXUHRI

&DOLEUDWLRQ6HWXS KRZWKHFDEOHVVKRXOGEHFRQÀJXUHG
7RUHPRYHWKHFDEOHORVVEHWZHHQWKH267·VUHFHLYHU
DQGWKH'87·VWUDQVPLWWHUDQGDGMXVWIRUQPRU
QPRSHUDWLRQ
3UHVVWKHZDYHOHQJWKEXWWRQRQWKHULJKWVLGHRI
WKH5;7;EDUWRRSHQWKH´6HW5HFHLYH/DPEGDµ
,QSXW1XPEHU3DG
(QWHU´µLIWKHOLJKWHQWHULQJWKH267LV
QPHQWHU´µLIWKHOLJKWHQWHULQJWKH267LV
QPRUHQWHUWKHH[DFWZDYHOHQJWKRIWKH
'877; 3UHVV´$XWR&DOLEUDWHµ
3UHVV´2.µ
3UHVV´2.µ
3UHVVWKH´&DO)DFWRUµEXWWRQORFDWHGRQWKH
ULJKWVLGHRIWKH5;7;EDU
3UHVV´&DO)DFWRU$VVLVWDQWµ
287
Procedures
LPSHULDOZD\VXLWHF
DOOHQWRZQSD
SKRQHWROOIUHH
/DVW8SGDWHG6HSWHPEHU ZZZFLUFDGLDQWFRP
$OO5LJKWV5HVHUYHG
288
289
Procedures
15.3 Cleaning the OST Airflow Fans
&OHDQLQJWKH267
$LUÁRZ)DQV
5HJXODUFOHDQLQJRIWKH267IDQVNHHSVDLUÁRZ
DWDPD[LPXPDQGDOORZVWKH267WRNHHSFRRO
DQGSURYLGHVUHSHDWDEOHWHVWUHVXOWV
7XUQWKH267RIIIROORZLQJWKH
VWDQGDUGVKXWGRZQSURFHGXUHV
5HPRYHWKHPDLQSRZHUVXSSO\FDEOH
IURPWKH$9LQSXWFRQQHFWRU
&KHFNWRHQVXUHWKH9SRZHU
LQGLFDWRU/('LVQRWLOOXPLQDWHG
&DUHIXOO\UHPRYHDOOWKXPEVFUHZV
IURPWKH$WKDWKROGWKHIDQ
SURWHFWLRQVFUHHQVLQSODFH
8VLQJDVRIWSODVWLFEUXVKOLNHD
WRRWKEUXVKJHQWO\VZHHSWKHJUDWH
FRYHULQJWKHWRSIDQ8VHDGRZQZDUG
PRWLRQWRHQVXUHWKDWGXVWLVQRW
SXVKHGEDFNLQWRWKH267
290
Cleaning the OST Airflow Fans
:LWKWKHVDPHVRIWEUXVKOLJKWO\
VZHHSWKHGXVWIURPWKHUHPRYDEOH
JUDWH%HFDUHIXOQRWWRGDPDJHWKH
HPERVVHGFRUUXJDWLRQV
/LJKWO\VZHHSDQ\GXVWIURPWKH
IDQJUDWHORFDWHGRQWKHEDFNRIWKH
$%HFDUHIXOQRWWRGDPDJHWKH
HPERVVHGFRUUXJDWLRQV
&DUHIXOO\UHSODFHWKHIDQSURWHFWLRQ
VFUHHQDQGIDQSURWHFWLRQJUDWHVRQ
WKH$5HSODFHWKHWKXPEVFUHZV
RQWKHIDQJUDWHV
5HFRQQHFWWKHSRZHUVXSSOLHVDQG
SRZHUXSWKH267(QVXUHWKDWDOOIDQV
DUHSURYLGLQJDLUÁRZ
LPSHULDOZD\VXLWHF
DOOHQWRZQSD
SKRQHWROOIUHH
ZZZFLUFDGLDQWFRP
$OO5LJKWV5HVHUYHG
291
Procedures
292
CHAPTER 16 Application Briefs
The following Application Briefs are included in this chapter.

• “Stressed Receiver Conformance Testing” on page 294
• “Optical Sensitivity Testing” on page 296
• “BER vs. OSNR Testing” on page 298
• “Path Penalty Testing” on page 300
• “Transmitter Optical Output Power Testing” on page 302
• “Optical Overload Testing” on page 304
• “Debug Testing of Manufacturing Rejects and Customer Returns” on page 306
• “Test Set Calibration” on page 308
• “Transmitter Functional Testing” on page 310
• “IntelliScriptTM Testing” on page 312
• “IntelliTimeTM Testing” on page 314
• “IntelliPassTM Testing” on page 316
• “Golden Transmitters” on page 318
293
Application Briefs
16.1 Stressed Receiver Conformance Testing
&RQVROLGDWLRQ$XWRPDWLRQ'HJUDGDWLRQ
7KH&LUFDGLDQW6\VWHPV2SWLFDO6WDQGDUGV7HVWHU267
6WUHVVHG5HFHLYHU FRQVROLGDWHVOD\HURQHWZRDQGWKUHHLQVWUXPHQWVDQG
FRPSRQHQWVFRPPRQO\XVHGWRWHVWRSWLFDOFRPPXQLFDWLRQ
&RQIRUPDQFH V\VWHPVDQGDXWRPDWHVVWDQGDUGWUDQVPLWWHUDQGUHFHLYHUWHVWV
XVLQJFOHDQRUGHJUDGHGWHVWVLJQDOV
7HVWLQJ 2SWLFDO6HQVLWLYLW\9DU\WKHRSWLFDOSRZHUOHYHORU2SWLFDO
0RGXODWLRQ$PSOLWXGH20$ZKLOHPDLQWDLQLQJWKH%(5OHYHO
$XWRPDWLFDOO\SORWDQGFDOFXODWHWKH'87·VUHFHLYHUVHQVLWLYLW\
6WUHVVHGUHFHLYHUFRQIRUPDQFHWHVWLQJLV %(5YV26156WHSWKURXJKDUDQJHRIFDOLEUDWHG2SWLFDO6LJQDOWR
WKHNH\WHVWIRUHVWDEOLVKLQJFRPSOLDQFH 1RLVH5DWLRVZKLOHPDLQWDLQLQJDFRQVWDQWRSWLFDOSRZHU$XWRPDWLFDOO\
SORWDQGFDOFXODWHWKH'87·VUHFHLYHU%(5YV2615VHQVLWLYLW\
WRWKH*LJDELW(WKHUQHW,(((DH 2SWLFDO3DWK3HQDOW\3HUIRUPWZRVHQVLWLYLW\PHDVXUHPHQWVZLWK
VWDQGDUGVSHFLÀFDWLRQV7KLVWHVW DQGZLWKRXWWKH'87·VWUDQVPLWWHUVLJQDOSDVVLQJWKURXJKDVSRROVRI
ÀEHU$XWRPDWLFDOO\SORWHDFKVHQVLWLYLW\WHVWDQGFDOFXODWHWKHRSWLFDO
GHWHUPLQHVLIDUHFHLYHULVDEOHWRRSHUDWH SRZHUGLIIHUHQFHEHWZHHQWKHPDWDVHOHFWHG%(5OHYHO
DWDORZ%(5UDWHZLWKDVLJQLÀFDQWO\ 7UDQVPLWWHU2SWLFDO2XWSXW3RZHU&RPSDUHWKHWRWDORSWLFDO
RXWSXWSRZHUHPLWWHGE\WKH'87·VWUDQVPLWWHUWRWKHGHÀQHGPLQLPXP
GHJUDGHGRSWLFDOLQSXWGHVLJQHGWR DQGPD[LPXPUDQJH$XWRPDWLFDOO\FDWHJRUL]HWKH'87DVD3$66RU)$,/
VLPXODWHZRUVWFDVHFRQGLWLRQV 2SWLFDO2YHUORDG0DNHVHQVLWLYLW\PHDVXUHPHQWVZKLOHVWHSSLQJ
WKURXJKDUDQJHRIKLJKRSWLFDOSRZHUV$XWRPDWLFDOO\SORWDQGFDOFXODWH
WKHRSWLFDOLQSXWSRZHUDWZKLFKWKH'87·VUHFHLYHURYHUORDGVDQG
JHQHUDWHVHUURUV
,VVXHV 3UREOHPV
'HEXJ7HVWLQJ'LDJQRVHSURGXFWIDLOXUHVZLWKWKH267E\
7KHSULQFLSDOSUREOHPVIDFLQJVWUHVVHGUHFHLYHU DXWRPDWLFDOO\PDNLQJSURJUHVVLYHO\PRUHGLIÀFXOWPHDVXUHPHQWVIURPD
FRQIRUPDQFHWHVWLQJDUHFRQÀJXULQJWKHWHVWVHWXS SUHSURJUDPPHGOLVWRIWHVWV,QGHEXJPRGHWKH267FRQWUROVD'&$
FUHDWLQJDGHJUDGHGVLJQDOWKDWLVFRPSOLDQWZLWK ZDYHPHWHUDQGDQRSWLFDOVZLWFKWRJHQHUDWHWHVWGDWDWKDWZRXOGWDNH
WKH,(((DHVSHFLÀFDWLRQVDQGPDLQWDLQLQJ KRXUVWRFROOHFWPDQXDOO\
FDOLEUDWLRQ
6;3HQDOW\3HUIRUPWZRVHQVLWLYLW\PHDVXUHPHQWVZLWKDQGZLWKRXW
w &RQÀJXUDWLRQ6HWWLQJXSDYHU\FRPSOH[VHW DQDGGHGLQWHUIHULQJVLJQDO$XWRPDWLFDOO\SORWHDFKVHQVLWLYLW\WHVWDQG
RIWHVWLQVWUXPHQWVLVWLPHFRQVXPLQJDQG FDOFXODWHWKHDGGLWLRQDORSWLFDOSRZHUUHTXLUHGE\WKH'87·VUHFHLYHUWR
H[SHQVLYH UHDFKDVHOHFWHG%(5OHYHOZLWKDQDSSOLHGLQWHUIHULQJVLJQDO
w '
HJUDGHG6LJQDO&UHDWLQJDSUHFLVHO\GHÀQHG 6HFXUHG$FFXUDF\&DOLEUDWLRQ7HVWZLWKRXWZRUU\LQJDERXW
GHJUDGHGVLJQDOIRUWHVWLQJLVYHU\GLIÀFXOW WKH267GULIWLQJRXWRIFDOLEUDWLRQEHFDXVHHDFK267LVDVHOIFRQWDLQHG
2SWLFDO0RGXODWLRQ$PSOLWXGH20$MLWWHUWK PHDVXUHPHQWV\VWHP6HOIFKHFNLQWHUQDOSURFHVVFRQWUROFKDUWVEHJLQ
RUGHU%HVVHO7KRPSVRQÀOWHULQWHUIHULQJVRXUFH ZKLOHWKH267LVVWLOODWWKH&LUFDGLDQWIDFWRU\WRDVVXUHWKH267LVDOZD\V
DQGH[WLQFWLRQUDWLRPXVWDOOEHFRQWUROOHGDQG LQFDOLEUDWLRQ
VHWDWWKHSURSHUOHYHOV 6WUDLJKW/LQH%(53ORWVHQVLWLYLW\WHVWVRSWLFDOSRZHU20$
w &DOLEUDWLRQ0DLQWDLQLQJSURSHUVLJQDOOHYHOV RU2615YV%(5RQWKHSURSHUVFDOHVXFKWKDWWKHGDWDZLOOIDOORQD
WHVWDIWHUWHVWLVDFRPSOLFDWHGDQGODERULRXV VWUDLJKWOLQHIRUDZHOOEHKDYHGGHYLFH8QH[SHFWHGEHKDYLRULVUHYHDOHG
WDVN7KLVFRPSOH[LW\PDNHVWUDGLWLRQDO LPPHGLDWHO\DQGFRQFOXVLYHO\WRWKHXVHU
LPSOHPHQWDWLRQVLOOVXLWHGIRUPDQXIDFWXULQJ ,QWHOOL6FULSW7HVWLQJ6HTXHQFHWKURXJKVWDQGDUGEXLOWLQWHVWVDQG
HQYLURQPHQWV FRQWUROH[WHUQDOLQVWUXPHQWVVXFKDVHQYLURQPHQWDOFKDPEHUVSRZHU
VXSSOLHV26$VRSWLFDOVZLWFKHVRVFLOORVFRSHVDQGZDYHOHQJWKPHWHUV
294
Stressed Receiver Conformance Testing
3UHYLRXV:D\ &LUFDGLDQW:D\
&RQÀJXUDWLRQ$OOWKHLQVWUXPHQWVDQGFRPSRQHQWVQHHGHG
WRPDNHVWUHVVHGUHFHLYHUFRQIRUPDQFHWHVWVDUHFRQVROL
GDWHGLQWRDVLQJOH2SWLFDO6WDQGDUGV7HVWHU267DQGWKH
WHVWSURFHGXUHLVDXWRPDWHG5HSHDWDELOLW\LVH[FHOOHQW
'HJUDGHG6LJQDO7KHVWUHVVHGH\HVLJQDOLVIDFWRU\VHW
7KHUHLVQRQHHGIRUDOHQJWK\VHWXSSURFHGXUHRUIRUDQ\
H[WHUQDOFDOLEUDWLRQ6LPSO\VHOHFWWKHW\SHRIGHVLUHGWHVW
VLJQDOIURPDPHQXDQGSUHVV´6WDUWµ
&DOLEUDWLRQ7KH267·V6HFXUHG$FFXUDF\FDOLEUDWLRQIHD
WXUHDVVXUHV\RXWKDWWKH267LVDOZD\VLQFDOLEUDWLRQ
$QDO\VLV0DNLQJVWUHVVHGUHFHLYHUFRQIRUPDQFHWHVW
PHDVXUHPHQWVZLWKDQ267LVVLPSOHDQGWKHUHVXOWVDUH
KLJKO\UHSHDWDEOH)DFWRU\GHJUDGHGVLJQDOVHWXSVHQVXUH
FRUUHODWLRQZLWKRWKHUYHQGRUV0HDVXULQJFRPSOLDQFHWR
WKHVWDQGDUGGRHVQRWUHTXLUHWKHLQYROYHPHQWRI5 'HQ
JLQHHUV&RVWUHGXFWLRQDQGFRPSRQHQWVRXUFLQJDFWLYLWLHV
FDQEHSHUIRUPHGE\PDQXIDFWXULQJHQJLQHHUV
&RQÀJXUDWLRQ1XPHURXVLQVWUXPHQWVKDGWREHDVVHPEOHGDQG
VHWXSWRSHUIRUPWKLVQHZW\SHRIWHVWLQFOXGLQJDIUHTXHQF\
V\QWKHVL]HUFORFNVRXUFHWHVWSDWWHUQJHQHUDWRUWKRUGHU%HVVHO
7KRPSVRQÀOWHUVLQXVRLGDODPSOLWXGHLQWHUIHULQJVRXUFHRSWLFDO
DWWHQXDWRU(2FRQYHUWHURVFLOORVFRSHDQG%(57

'HJUDGHG6LJQDO$QLQWULFDWHVHYHQVWHSSURFHGXUHKDGWREH
IROORZHGWRSURGXFHDGHJUDGHGVLJQDO6HWWKHVLJQDOVSHHG
7XUQRQFDOLEUDWLRQSDWWHUQ$GMXVWWKHH[WLQFWLRQUDWLR
0HDVXUH20$RIWKHWHVWVLJQDO6HWWKH9HUWLFDO(\H&ORVXUH
3HQDOW\9(&3ZLWKOLQHDUSKDVHÀOWHUVLQXVRLGDOLQWHUIHUHQFHDQG
VLQXVRLGDOMLWWHU'HFUHDVHWKH20$DPSOLWXGH7XUQRQWHVW
SDWWHUQ-LWWHUDQGDPSOLWXGHOHYHOVZHUHLWHUDWLYHO\FKDQJHGLQ
WKLVSURFHGXUHWRGHWHUPLQHFRPSOLDQFHWRWKHVWDQGDUG
&DOLEUDWLRQ0DLQWDLQLQJFDOLEUDWLRQRIWKHWHVWVLJQDOUHTXLUHG
DVLJQLÀFDQWDPRXQWRIGHGLFDWLRQGXHWRWKHODUJHQXPEHURI
LQGLYLGXDOLQVWUXPHQWVLQWKHWHVWVHWDUUDQJHPHQWWKHQXPEHURI
LQWHUFRQQHFWLRQFDEOHVXVHGDQGWKHOHQJWK\VWHSE\VWHSSURFHVV
WKDWZDVIROORZHGWRFUHDWHWKHGHJUDGHGVLJQDO
$JSDBEJBOU4ZTUFNT *OD
,PSHULDO:D\6XLWH&
$QDO\VLV&UHDWLQJDVWUHVVHGUHFHLYHUFRQIRUPDQFHWHVWZLWKD $OOHQWRZQ3$
UDFNIXOORIHTXLSPHQWZDVGLIÀFXOWWLPHFRQVXPLQJDQGIUDXJKW
7HO 7ROO)UHH
ZLWKWKHSRVVLELOLW\RIHUURU7HVWUHSHDWDELOLW\ZDVSRRUDQG
FRUUHODWLRQZLWKRWKHUYHQGRU·VWHVWUHVXOWVZDVXQFHUWDLQ )D[ (PDLOLQIR#FLUFDGLDQWFRP
+LJKO\WUDLQHGHQJLQHHUVZHUHQHHGHGWRVHWXSWKHWHVW 9LVLWRXUZHEVLWHKWWSZZZFLUFDGLDQWFRP
$OO5LJKWV5HVHUYHG
295
Application Briefs
16.2 Optical Sensitivity Testing
2SWLFDO6HQVLWLYLW\ FRQVROLGDWHVOD\HURQHWZRDQGWKUHHLQVWUXPHQWVDQG
7HVWLQJ V\VWHPVDQGDXWRPDWHVVWDQGDUGWUDQVPLWWHUDQGUHFHLYHUWHVWV
6WUHVVHG5HFHLYHU&RQIRUPDQFH*HQHUDWHDFDOLEUDWHG,(((
DHGHJUDGHGVLJQDOMLWWHUÀOWHULQWHUIHULQJVLJQDOH[WLQFWLRQUDWLR
ZKLOHYDU\LQJWKH2SWLFDO0RGXODWLRQ$PSOLWXGH20$$XWRPDWLFDOO\SORW
2SWLFDOVHQVLWLYLW\WHVWLQJLVJHQHUDOO\ DQGFDOFXODWHWKH'87·VUHFHLYHUVHQVLWLYLW\
UHJDUGHGDVWKHPRVWLPSRUWDQWDVSHFW %(5YV26156WHSWKURXJKDUDQJHRIFDOLEUDWHG2SWLFDO6LJQDOWR
1RLVH5DWLRVZKLOHPDLQWDLQLQJDFRQVWDQWRSWLFDOSRZHU$XWRPDWLFDOO\
LQHYDOXDWLQJWKHTXDOLW\RIRSWLFDO SORWDQGFDOFXODWHWKH'87·VUHFHLYHU%(5YV2615VHQVLWLYLW\
UHFHLYHUV6HQVLWLYLW\WHVWLQJGHWHUPLQHV 2SWLFDO3DWK3HQDOW\3HUIRUPWZRVHQVLWLYLW\PHDVXUHPHQWVZLWK
DQGZLWKRXWWKH'87·VWUDQVPLWWHUVLJQDOSDVVLQJWKURXJKDVSRROVRI
WKHPLQLPXPRSWLFDOSRZHUQHHGHG ÀEHU$XWRPDWLFDOO\SORWHDFKVHQVLWLYLW\WHVWDQGFDOFXODWHWKHRSWLFDO
WRJXDUDQWHHDQDFFHSWDEOH%(5OHYHO SRZHUGLIIHUHQFHEHWZHHQWKHPDWDVHOHFWHG%(5OHYHO
RIDUHFHLYHURUV\VWHP,QDQRSWLFDO 7UDQVPLWWHU2SWLFDO2XWSXW3RZHU&RPSDUHWKHWRWDORSWLFDO
VHQVLWLYLW\WHVWLQSXWSRZHUWRWKH DQGPD[LPXPUDQJH$XWRPDWLFDOO\FDWHJRUL]HWKH'87DVD3$66RU)$,/
UHFHLYHUXQGHUWHVWLVYDULHGZKLOHWKH%(5 2SWLFDO2YHUORDG0DNHVHQVLWLYLW\PHDVXUHPHQWVZKLOHVWHSSLQJ
LVPRQLWRUHGDQGWKHVHQVLWLYLW\UHVXOWVDUH WKHRSWLFDOLQSXWSRZHUDWZKLFKWKH'87·VUHFHLYHURYHUORDGVDQG
JHQHUDWHVHUURUV
WKHQFDOFXODWHG
DXWRPDWLFDOO\PDNLQJSURJUHVVLYHO\PRUHGLIÀFXOWPHDVXUHPHQWVIURPD
SUHSURJUDPPHGOLVWRIWHVWV,QGHEXJPRGHWKH267FRQWUROVD'&$
,VVXHV 3UREOHPV ZDYHPHWHUDQGDQRSWLFDOVZLWFKWRJHQHUDWHWHVWGDWDWKDWZRXOGWDNH
KRXUVWRFROOHFWPDQXDOO\
7KHSULQFLSDOSUREOHPVIDFHGLQVHQVLWLYLW\WHVWLQJ
DUHPDLQWDLQLQJWHVWVHWFDOLEUDWLRQRSWLPL]LQJWKH 6;3HQDOW\3HUIRUPWZRVHQVLWLYLW\PHDVXUHPHQWVZLWKDQGZLWKRXW
LQSXWVLJQDODQGJHQHUDWLQJWKH%(5VWDWLVWLFV DQDGGHGLQWHUIHULQJVLJQDO$XWRPDWLFDOO\SORWHDFKVHQVLWLYLW\WHVWDQG
FDOFXODWHWKHDGGLWLRQDORSWLFDOSRZHUUHTXLUHGE\WKH'87·VUHFHLYHUWR
w &DOLEUDWLRQ$IWHUFRPSOH[RSWLFDOVHQVLWLYLW\ UHDFKDVHOHFWHG%(5OHYHOZLWKDQDSSOLHGLQWHUIHULQJVLJQDO
VHWXSVDUHFRQÀJXUHGWLPHFRQVXPLQJDQG
SDLQVWDNLQJFDOLEUDWLRQURXWLQHVPXVWEH 6HFXUHG$FFXUDF\&DOLEUDWLRQ7HVWZLWKRXWZRUU\LQJDERXW
FRQGXFWHGRQDUHJXODUEDVLV WKH267GULIWLQJRXWRIFDOLEUDWLRQEHFDXVHHDFK267LVDVHOIFRQWDLQHG
PHDVXUHPHQWV\VWHP6HOIFKHFNLQWHUQDOSURFHVVFRQWUROFKDUWVEHJLQ
w ,QSXW6LJQDO7RRPXFKWLPHPD\EHVSHQW ZKLOHWKH267LVVWLOODWWKH&LUFDGLDQWIDFWRU\WRDVVXUHWKH267LVDOZD\V
LWHUDWLYHO\VHDUFKLQJIRUWKHFRUUHFWRSWLFDO LQFDOLEUDWLRQ
SRZHUVWRWHVWDQGWKHWHVWVLJQDOPD\EH
GLIÀFXOWWRSURGXFHZLWKUHTXLUHGSURWRFROV 6WUDLJKW/LQH%(53ORWVHQVLWLYLW\WHVWVRSWLFDOSRZHU20$
RU2615YV%(5RQWKHSURSHUVFDOHVXFKWKDWWKHGDWDZLOOIDOORQD
H[WLQFWLRQUDWLRVDQGRWKHUDGGHGGHJUDGDWLRQV
VWUDLJKWOLQHIRUDZHOOEHKDYHGGHYLFH8QH[SHFWHGEHKDYLRULVUHYHDOHG
w 6WDWLVWLFV$IWHUFDSWXULQJ%(5UHVXOWVLWLV LPPHGLDWHO\DQGFRQFOXVLYHO\WRWKHXVHU
RIWHQGLIÀFXOWWRDGGWKHQHFHVVDU\VWDWLVWLFDO
,QWHOOL6FULSW7HVWLQJ6HTXHQFHWKURXJKVWDQGDUGEXLOWLQWHVWVDQG
TXDOLÀFDWLRQVWRWKHVHQVLWLYLW\YDOXH FRQWUROH[WHUQDOLQVWUXPHQWVVXFKDVHQYLURQPHQWDOFKDPEHUVSRZHU
296
Optical Sensitivity Testing
&DOLEUDWLRQ$OOWKHLQVWUXPHQWVDQGFRPSRQHQWVQHHGHG
WRPDNHVHQVLWLYLW\PHDVXUHPHQWVDUHFRQVROLGDWHGLQWR
WKH2SWLFDO6WDQGDUGV7HVWHU267DQGWKHYDULRXVHOH
PHQWVDUHIXVLRQVSOLFHGWRJHWKHUFUHDWLQJDYHU\VWDEOH
DQGUHSHDWDEOHSODWIRUP7LPHVSHQWRQWHVWVHWFDOLEUD
WLRQLVSUDFWLFDOO\HOLPLQDWHGZLWKWKH267·V6HFXUHG$FFX
UDF\FDOLEUDWLRQVWDQGDUGIHDWXUH
,QSXW6LJQDO7LPHVSHQWKXQWLQJIRUWKHFRUUHFWRSWLFDO
SRZHUWHVWUDQJHLVHOLPLQDWHGZLWKWKH267·V$XWR%(5
DOJRULWKPWKDWDXWRPDWLFDOO\ORFDWHVDQGWHVWVRQO\RYHU
WKHGHVLUHG%(5UDQJH7KH267·VRXWSXWVLJQDOPD\EHVHW
&DOLEUDWLRQ1XPHURXVLQVWUXPHQWVVXFKDVSRZHUPHWHUV WRDYDULHW\RIWUDIÀFW\SHV35%6621(7*(:$1*(
DWWHQXDWRUVVLJQDOJHQHUDWRUVDQGDQDO\]HUVDQGFRXSOHUVKDG /$1*3R6271DQGWKHTXDOLW\RIWKHVLJQDOGHJUDGHG
WRZRUNLQFRQFHUWWRSURGXFHVHQVLWLYLW\PHDVXUHPHQWVDQGWKH H[WLQFWLRQUDWLR2615MLWWHULQWHUIHULQJODVHU*ROGHQ
VHWXSZRXOGFKDQJHGXHWRLQGLYLGXDOLQVWUXPHQWGULIWDQGWKH WUDQVPLWWHUVPD\EHXWLOL]HGDXWRPDWLFDOO\FDOLEUDWHG
ODUJHQXPEHURIRSWLFDOFDEOHVDQGLQWHUIDFHVWKDWZHUHUHTXLUHG DQGWKHLUVLJQDOVRSWLRQDOO\GHJUDGHGE\WKH267
$VDUHVXOWWHVWVHWFDOLEUDWLRQZDVDFRQVWDQWWLPHFRQVXPLQJ
FKRUH 6WDWLVWLFV2SWLFDOVHQVLWLYLW\UHVXOWVDUHDXWRPDWLFDOO\GLV
SOD\HGRQWKH267·V6WUDLJKW/LQH%(5SORWVRXQH[SHFWHG
,QSXW6LJQDO$QLWHUDWLYHSURFHVVZDVXVHGWRORFDWHWKHÀ[HG UHVXOWVDUHLPPHGLDWHO\DSSDUHQWDQGFODVVLÀHGDV3$66RU
RSWLFDOSRZHUOHYHOVXVHGWRPDNH%(5PHDVXUHPHQWV2IWHQ )$,/6WDWLVWLFDODQDO\VLVLVLQFOXGHGDOORZLQJD'87WREH
VLJQDOVZHUHJHQHUDWHGIURPWHVWVHWVWKDWKDGKLJKH[WLQFWLRQ FKDUDFWHUL]HGIRUH[DPSOHDVKDYLQJD%(5DW
UDWLRVUHVXOWLQJLQRYHURSWLPLVWLFSHUIRUPDQFHUHVXOWV G%PG%ZLWKDFRQÀGHQFHOHYHO
5HTXLUHPHQWVWKDWUHFHLYHUVKDGWREHWHVWHGZLWKWKHWUDIÀF
W\SHDGHYLFHZRXOGRSHUDWHXQGHULQWKHÀHOGOHGWRFRPSOH[ $QDO\VLV&RQVROLGDWLRQDQGDXWRPDWLRQSURGXFHKLJKO\
WHVWVHWVFRQÀJXUHGZLWKDYDULHW\RIWUDIÀFVRXUFHV35%6 UHSHDWDEOHVHQVLWLYLW\WHVWUHVXOWVVKULQNJXDUGEDQGV
621(7*(:$1*(/$1271HWF«DQGDGGHGGHJUDGDWLRQV UHGXFHWHVWWLPHVLPSURYHGHYLFHVSHFLÀFDWLRQVLQFUHDVH
VXFKDVH[WLQFWLRQUDWLRMLWWHUDQG26156RPHWLPHV´*ROGHQµ \LHOGVDQGLPSURYHTXDOLW\
WUDQVPLWWHUVZHUHXVHGWRVLPXODWHUHDOZRUOGFRQGLWLRQV
$OWKRXJKZKHQDGGLWLRQDOWHVWVHWVZHUHQHHGHGFRUUHODWLRQ
EHWZHHQWHVWVHWVZDVRIWHQDSUREOHP
6WDWLVWLFV6RPHWLPHVWDEOHVRIRSWLFDOSRZHUYV%(5ZHUH
WUDQVODWHGWRJUDSKVVRD%(5FXUYHFRXOGEHREVHUYHGDQGWKH
VHQVLWLYLW\FDOFXODWHGIURPWKHLQWHUVHFWLRQRIWKH%(5OHYHOZLWK
WKHFXUYH7\SLFDOO\WKLVZDVGRQHXVLQJDORJORJVFDOH%XW
UDUHO\ZDVDQ\NLQGRIVWLSXODWLRQPDGHDERXWWKHVWDWLVWLFDO
FRQÀGHQFHOHYHORIWKHUHVXOWDQGWKHWROHUDQFHDURXQGWKH
TXRWHGVHQVLWLYLW\YDOXH
$QDO\VLV3UREOHPVLQPDNLQJUHOLDEOHVHQVLWLYLW\PHDVXUHPHQWV
DGGHGJXDUGEDQGVWRUHFHLYHUVSHFLÀFDWLRQVWKDWKXUW
PDUNHWSODFHFRPSHWLWLYHQHVVDQGORZHUHGPDQXIDFWXULQJ $JSDBEJBOU4ZTUFNT *OD
\LHOGV,QFRUUHFWVHQVLWLYLW\UHVXOWVVRPHWLPHVOHGWRWKH
VKLSPHQWRIUHFHLYHUVDQGV\VWHPVWKDWGLGQRWPHHWJXDUDQWHHG ,PSHULDO:D\6XLWH&
VSHFLÀFDWLRQVDQGSURGXFWUHWXUQUDWHVZHUHDIIHFWHG $OOHQWRZQ3$
7HO 7ROO)UHH
)D[ (PDLOLQIR#FLUFDGLDQWFRP
9LVLWRXUZHEVLWHKWWSZZZFLUFDGLDQWFRP
$OO5LJKWV5HVHUYHG
297
Application Briefs
16.3 BER vs. OSNR Testing
%(5YV2615 FRQVROLGDWHVOD\HURQHWZRDQGWKUHHLQVWUXPHQWVDQG
2SWLFDO6HQVLWLYLW\9DU\WKHRSWLFDOSRZHUOHYHORU2SWLFDO
%LW(UURU5DWLR%(5YV2SWLFDO6LJQDOWR 6WUHVVHG5HFHLYHU&RQIRUPDQFH*HQHUDWHDFDOLEUDWHG,(((
1RLVH5DWLR2615LVDNH\TXDOLW\WHVW DHGHJUDGHGVLJQDOMLWWHUÀOWHULQWHUIHULQJVLJQDOH[WLQFWLRQUDWLR
IRUUHFHLYHUVXVHGLQRSWLFDOO\DPSOLÀHG DQGFDOFXODWHWKH'87·VUHFHLYHUVHQVLWLYLW\
V\VWHPV5HFHLYHUVPXVWPDLQWDLQORZ%(5 2SWLFDO3DWK3HQDOW\3HUIRUPWZRVHQVLWLYLW\PHDVXUHPHQWVZLWK
OHYHOVGXULQJSRRU2615FRQGLWLRQVFUHDWHG ÀEHU$XWRPDWLFDOO\SORWHDFKVHQVLWLYLW\WHVWDQGFDOFXODWHWKHRSWLFDO
E\QRLVHLQWURGXFHGE\DFDVFDGHRI(UELXP SRZHUGLIIHUHQFHEHWZHHQWKHPDWDVHOHFWHG%(5OHYHO
'RSHG)LEHU$PSOLÀHUV(')$V,QD 7UDQVPLWWHU2SWLFDO2XWSXW3RZHU&RPSDUHWKHWRWDORSWLFDO

%(5YV2615WHVWRSWLFDOSRZHULVKHOG DQGPD[LPXPUDQJH$XWRPDWLFDOO\FDWHJRUL]HWKH'87DVD3$66RU)$,/
FRQVWDQWZKLOHWKH2615OHYHOLVYDULHGDQG 2SWLFDO2YHUORDG0DNHVHQVLWLYLW\PHDVXUHPHQWVZKLOHVWHSSLQJ
WKH%(5PHDVXUHG WKHRSWLFDOLQSXWSRZHUDWZKLFKWKH'87·VUHFHLYHURYHUORDGVDQG
JHQHUDWHVHUURUV
,VVXHV 3UREOHPV SUHSURJUDPPHGOLVWRIWHVWV,QGHEXJPRGHWKH267FRQWUROVD'&$
7KHSULQFLSDOSUREOHPVIDFHGGXULQJ%(5YV ZDYHPHWHUDQGDQRSWLFDOVZLWFKWRJHQHUDWHWHVWGDWDWKDWZRXOGWDNH
2615WHVWLQJDUHWKHWHVWVHWV·DELOLW\WRPDLQWDLQ KRXUVWRFROOHFWPDQXDOO\
FRQVWDQWSRZHUOHYHOVZKLOHFKDQJLQJ2615OHYHOV 6;3HQDOW\3HUIRUPWZRVHQVLWLYLW\PHDVXUHPHQWVZLWKDQGZLWKRXW
FRUUHODWLQJ%(5YV2615PHDVXUHPHQWVDQG DQDGGHGLQWHUIHULQJVLJQDO$XWRPDWLFDOO\SORWHDFKVHQVLWLYLW\WHVWDQG
VWD\LQJLQFDOLEUDWLRQ FDOFXODWHWKHDGGLWLRQDORSWLFDOSRZHUUHTXLUHGE\WKH'87·VUHFHLYHUWR
w &RQVWDQW3RZHU$GGLQJRUVXEWUDFWLQJ$PSOLÀHG UHDFKDVHOHFWHG%(5OHYHOZLWKDQDSSOLHGLQWHUIHULQJVLJQDO
6WLPXODWHG(PLVVLRQ$6(QRLVHFDXVHVWKH 6HFXUHG$FFXUDF\&DOLEUDWLRQ7HVWZLWKRXWZRUU\LQJDERXW
RSWLFDOSRZHUOHYHOWRFKDQJH7KLVUHTXLUHV WKH267GULIWLQJRXWRIFDOLEUDWLRQEHFDXVHHDFK267LVDVHOIFRQWDLQHG
LWHUDWLYHDGMXVWPHQWVRIERWKWKHDGGHGQRLVH PHDVXUHPHQWV\VWHP6HOIFKHFNLQWHUQDOSURFHVVFRQWUROFKDUWVEHJLQ
DQGWKHRSWLFDOSRZHUOHYHORIWKH%(5WHVWVLJQDO ZKLOHWKH267LVVWLOODWWKH&LUFDGLDQWIDFWRU\WRDVVXUHWKH267LVDOZD\V
LQRUGHUWRREWDLQWKHGHVLUHG2615OHYHODWD LQFDOLEUDWLRQ
FRQVWDQWRYHUDOORSWLFDOSRZHUOHYHO
6WUDLJKW/LQH%(53ORWVHQVLWLYLW\WHVWVRSWLFDOSRZHU20$
w &RUUHODWLRQ%(5YV2615WHVWUHVXOWVFDQYDU\ RU2615YV%(5RQWKHSURSHUVFDOHVXFKWKDWWKHGDWDZLOOIDOORQD
JUHDWO\EHWZHHQWHVWVHWV VWUDLJKWOLQHIRUDZHOOEHKDYHGGHYLFH8QH[SHFWHGEHKDYLRULVUHYHDOHG
LPPHGLDWHO\DQGFRQFOXVLYHO\WRWKHXVHU
w &DOLEUDWLRQ%(5YV2615WHVWLQJLVHVSHFLDOO\
UHOLDQWRQFDUHIXODQGDFFXUDWHWHVWVHW ,QWHOOL6FULSW7HVWLQJ6HTXHQFHWKURXJKVWDQGDUGEXLOWLQWHVWVDQG
FDOLEUDWLRQ6PDOOYDULDWLRQVLQWKHWHVWVHWXS FRQWUROH[WHUQDOLQVWUXPHQWVVXFKDVHQYLURQPHQWDOFKDPEHUVSRZHU
FDQVLJQLÀFDQWO\DOWHUWKHWHVWUHVXOWV VXSSOLHV26$VRSWLFDOVZLWFKHVRVFLOORVFRSHVDQGZDYHOHQJWKPHWHUV
298
BER vs. OSNR Testing
&RQVWDQW3RZHU7KH267DXWRPDWLFDOO\PDLQWDLQVDFRQ
VWDQWSRZHUDWDQ\JLYHQ2615WHVWOHYHO
&RUUHODWLRQ%(5YV2615WHVWPHWKRGRORJLHVDUHVWDQGDUG
L]HGDQGFRUUHODWLRQEHWZHHQ267VLVH[FHOOHQW
&DOLEUDWLRQ7KH267·V6HFXUHG$FFXUDF\FDOLEUDWLRQ
IHDWXUHDVVXUHV\RXWKDWWKH267LVDOZD\VLQFDOLEUDWLRQ
8VHUVXSSOLHGUHIHUHQFHWUDQVPLWWHUVDUHDXWRPDWLFDOO\
FDOLEUDWHG
$QDO\VLV%(5YV2615WHVWLQJFDQQRZEHSHUIRUPHG
DXWRPDWLFDOO\ZLWKH[FHOOHQWUHSHDWDELOLW\DQGFRUUHODWLRQ
WKURXJKRXWJOREDO5 'DQGPDQXIDFWXULQJRSHUDWLRQV2Q
JRLQJFRVWUHGXFWLRQDQGFRPSRQHQWUHSODFHPHQWDFWLYLWLHV
FDQEHSHUIRUPHGE\PDQXIDFWXULQJHQJLQHHULQJZLWKRXW
LQYROYLQJ5 'HQJLQHHUVRUWKHLUWHVWHTXLSPHQW

)RUDPRUHGHWDLOHGGHVFULSWLRQRI&LUFDGLDQW·VWHVWLQJ
&RQVWDQW3RZHU,WHUDWLYHDGMXVWPHQWVKDGWREHPDGHWR(')$ PHWKRGRORJ\GRZQORDGWKHIROORZLQJWZR7HFKQLFDO%ULHIV
SXPSODVHUVDQGWRDWWHQXDWRUVLQRUGHUWRPDLQWDLQDFRQVWDQW KWWSZZZFLUFDGLDQWFRPWHFKQRORJ\SGIWESGIDQG
RSWLFDOSRZHUOHYHODWDQ\JLYHQ2615OHYHO1RQOLQHDU(')$JDLQ KWWSZZZFLUFDGLDQWFRPWHFKQRORJ\SGIWESGI
FRPSOLFDWHGPDWWHUV6HWWLQJHDFKWHVWSRLQWUHTXLUHGUHSHDWHG
PHDVXUHPHQWVZLWKDQ2SWLFDO6SHFWUXP$QDO\]HU26$DQG
RSWLFDOSRZHUPHWHUV

&RUUHODWLRQ%(5YV2615UHVXOWVYDULHGEHWZHHQWHVWVHWV
&RQWULEXWLQJWRWKLVZDVYHQGRUVXVLQJGLIIHUHQW26$VLQFRQVLVWHQW
UHVROXWLRQEDQGZLGWKVLQGLYLGXDOPHWKRGVRIFDOFXODWLQJ2615
DQGXQHTXDO$6(ÀOWHUV
&DOLEUDWLRQ2SWLFDOFRQQHFWRUVFDEOHPRYHPHQWDQG
WHPSHUDWXUHHIIHFWVDOOSOD\HGKDYRFRQ%(5YV2615WHVWVHW
FDOLEUDWLRQ&RPSRXQGLQJVHQVLWLYHFDOLEUDWLRQUHTXLUHPHQWVZDV
WKHQHHGWRPDLQWDLQFDOLEUDWLRQRYHUORQJWLPHSHULRGV(UURU
SURQHPDQXDO%(5YV2615WHVWVWRRNKRXUVWRUXQ
$QDO\VLV5HFHLYHUVDUHQRLVHOLPLWHGUDWKHUWKDQRSWLFDOSRZHU
OLPLWHGLQÀEHUDPSOLÀHGV\VWHPVPDNLQJJRRG%(5YV2615
UHVXOWVHVVHQWLDOWRPDLQWDLQLQJORZV\VWHPHUURUUDWHV%XW
WKHGLIÀFXOW\LQPDNLQJ%(5YV2615WHVWVOHGWRVXEVWLWXWLRQV
RIVLPSOHUWHVWVVXFKDVUHFHLYHUHOHFWULFDOEDQGZLGWK
FKDUDFWHUL]DWLRQ,QHYLWDEO\SURGXFWUHWXUQUDWHVZHUHDIIHFWHG
DQGSDLQIXOFRUUHODWLRQVWXGLHVKDGWREHFRQGXFWHGEHWZHHQ
GLVVLPLODUWHVWVHWV ,PSHULDO:D\6XLWH&
$OOHQWRZQ3$
7HO 7ROO)UHH
$OO5LJKWV5HVHUYHG
299
Application Briefs
16.4 Path Penalty Testing
3DWK3HQDOW\ FRQVROLGDWHVOD\HURQHWZRDQGWKUHHLQVWUXPHQWVDQG
'LVSHUVLRQ3HQDOW\ 2SWLFDO6HQVLWLYLW\9DU\WKHRSWLFDOSRZHUOHYHORU2SWLFDO
3DWKSHQDOW\WHVWLQJLVDNH\WUDQVPLWWHU 6WUHVVHG5HFHLYHU&RQIRUPDQFH*HQHUDWHDFDOLEUDWHG,(((
TXDOLW\WHVW7UDQVPLWWHUVPXVWZRUNRYHU DHGHJUDGHGVLJQDOMLWWHUÀOWHULQWHUIHULQJVLJQDOH[WLQFWLRQUDWLR
DVSHFLÀHGOHQJWKRIÀEHUZLWKRXWDQHUURU DQGFDOFXODWHWKH'87·VUHFHLYHUVHQVLWLYLW\
ÁRRU7KHSHQDOW\LVWKHG%GLIIHUHQFH %(5YV26156WHSWKURXJKDUDQJHRIFDOLEUDWHG2SWLFDO6LJQDOWR
LQPHDVXUHGVHQVLWLYLW\RIDUHIHUHQFH SORWDQGFDOFXODWHWKH'87·VUHFHLYHU%(5YV2615VHQVLWLYLW\
UHFHLYHUEHWZHHQDVKRUWDQGDORQJÀEHU 7UDQVPLWWHU2SWLFDO2XWSXW3RZHU&RPSDUHWKHWRWDORSWLFDO
OLQN DQGPD[LPXPUDQJH$XWRPDWLFDOO\FDWHJRUL]HWKH'87DVD3$66RU)$,/
2SWLFDO2YHUORDG0DNHVHQVLWLYLW\PHDVXUHPHQWVZKLOHVWHSSLQJ
,VVXHV 3UREOHPV WKHRSWLFDOLQSXWSRZHUDWZKLFKWKH'87·VUHFHLYHURYHUORDGVDQG
JHQHUDWHVHUURUV
7KHSULQFLSDOSUREOHPVIDFHGLQSDWKSHQDOW\
WHVWLQJDUHFRQÀUPLQJWKHUHLVQRHUURUÁRRU 'HEXJ7HVWLQJ'LDJQRVHSURGXFWIDLOXUHVZLWKWKH267E\
FDOFXODWLQJVKRUWDQGORQJSDWKVHQVLWLYLW\ DXWRPDWLFDOO\PDNLQJSURJUHVVLYHO\PRUHGLIÀFXOWPHDVXUHPHQWVIURPD
PHDVXUHPHQWVDWHTXDO%(5OHYHOVDQGPDLQWDLQLQJ SUHSURJUDPPHGOLVWRIWHVWV,QGHEXJPRGHWKH267FRQWUROVD'&$
FDOLEUDWLRQ ZDYHPHWHUDQGDQRSWLFDOVZLWFKWRJHQHUDWHWHVWGDWDWKDWZRXOGWDNH
KRXUVWRFROOHFWPDQXDOO\
w (UURU)ORRU&UHDWLQJDWHVWIRUDQHUURUÁRRU
DGGHGSRZHUGRHVQRWLPSURYHWKH%(5OHYHO 6;3HQDOW\3HUIRUPWZRVHQVLWLYLW\PHDVXUHPHQWVZLWKDQGZLWKRXW
LQ5 'DQGPDQXIDFWXULQJLVFKDOOHQJLQJ DQDGGHGLQWHUIHULQJVLJQDO$XWRPDWLFDOO\SORWHDFKVHQVLWLYLW\WHVWDQG
WLPHFRQVXPLQJPXOWLSOH%(5YVSRZHUOHYHO FDOFXODWHWKHDGGLWLRQDORSWLFDOSRZHUUHTXLUHGE\WKH'87·VUHFHLYHUWR
UHDFKDVHOHFWHG%(5OHYHOZLWKDQDSSOLHGLQWHUIHULQJVLJQDO
PHDVXUHPHQWVDUHPDGHDWUHODWLYHO\KLJK
RSWLFDOSRZHUOHYHOVWKHUHVXOWVSORWWHGDQGWKH 6HFXUHG$FFXUDF\&DOLEUDWLRQ7HVWZLWKRXWZRUU\LQJDERXW
VORSHVHYDOXDWHG WKH267GULIWLQJRXWRIFDOLEUDWLRQEHFDXVHHDFK267LVDVHOIFRQWDLQHG
w 6HQVLWLYLW\&DOFXODWLRQV:ULWLQJVRIWZDUHDQG
ZKLOHWKH267LVVWLOODWWKH&LUFDGLDQWIDFWRU\WRDVVXUHWKH267LVDOZD\V
FUHDWLQJYDOLGDOJRULWKPVWRLQWHUSRODWHEHWZHHQ LQFDOLEUDWLRQ
DQGH[WUDSRODWHEH\RQG%(5GDWDSRLQWVUHTXLUHV
VSHFLDOL]HGVWDWLVWLFDONQRZOHGJH 6WUDLJKW/LQH%(53ORWVHQVLWLYLW\WHVWVRSWLFDOSRZHU20$
w &DOLEUDWLRQ7LPHFRQVXPLQJDQGSDLQVWDNLQJ VWUDLJKWOLQHIRUDZHOOEHKDYHGGHYLFH8QH[SHFWHGEHKDYLRULVUHYHDOHG
FDOLEUDWLRQURXWLQHVPXVWEHFRQGXFWHGRQD LPPHGLDWHO\DQGFRQFOXVLYHO\WRWKHXVHU
UHJXODUEDVLV,QFOXGLQJDQRSWLFDOVZLWFKLQ
WKHWHVWVHWHVFDODWHVWKHGLOLJHQFHUHTXLUHGWR ,QWHOOL6FULSW7HVWLQJ6HTXHQFHWKURXJKVWDQGDUGEXLOWLQWHVWVDQG
PDLQWDLQDFFXUDWHFDOLEUDWLRQ FRQWUROH[WHUQDOLQVWUXPHQWVVXFKDVHQYLURQPHQWDOFKDPEHUVSRZHU
300
Path Penalty Testing
(UURU)ORRU7KH267DXWRPDWLFDOO\)$,/6WUDQVPLWWHUVZLWK
HUURUÁRRUVE\PHDVXULQJWKHVORSHRIWKHVKRUWDQGORQJ
SDWKVDQGUDWLQJWKHÀWRIWKHOLQHWRWKHGDWDSRLQWV
6HQVLWLYLW\&DOFXODWLRQV$OJRULWKPVGHVLJQHGLQWRWKH267
GHWHUPLQHWKHVHQVLWLYLW\RIWKHVKRUWDQGORQJSDWKVDWWKH
VDPH%(5OHYHODQGDSDWKSHQDOW\UHVXOWLVTXLFNO\FDOFX
ODWHGDQGGLVSOD\HG8VHUVXSSOLHGUHIHUHQFHUHFHLYHUVDUH
DOVRDFFRPPRGDWHG
&DOLEUDWLRQ7KH267·V6HFXUHG$FFXUDF\FDOLEUDWLRQIHD
WXUHDVVXUHV\RXWKDWWKH267LVDOZD\VLQFDOLEUDWLRQ
$QDO\VLV7KH267SDWKSHQDOW\WHVWLQJLVEDVHGRQVRSKLV
WLFDWHGDOJRULWKPVDQGLQFOXGHVFKHFNVIRUHUURUÁRRUV
(UURU)ORRU7KHRSWLFDOSRZHUOHYHOFRUUHVSRQGLQJWRDGHVLUHG 7UDQVPLWWHUWHVWLQJLQDPDQXIDFWXULQJHQYLURQPHQWLV
%(5OHYHOLHKDGWREHGHWHUPLQHGPRUHSRZHUDGGHG VLPSOHDFFXUDWHDQGUHSHDWDEOH&RVWUHGXFWLRQDQG
WRWKHVLJQDODQGWKH%(5OHYHOUHPHDVXUHG,IWRRPDQ\HUURUV FRPSRQHQWUHSODFHPHQWDFWLYLWLHVPD\EHSHUIRUPHGE\
ZHUHPHDVXUHGDWKLJKHUSRZHUOHYHOVWKDQVWDWLVWLFDOO\SUHGLFWHG PDQXIDFWXULQJHQJLQHHULQJZLWKRXWLQYROYLQJ5 'HQJL
WKHUHZDVDQHUURUÁRRU*DXJLQJWKHDSSURSULDWHSRZHUOHYHO QHHUVRUWKHLUWHVWHTXLSPHQW
RIIVHWVDQGGHWHUPLQLQJWKHSUHVHQFHRIHUURUÁRRUVZDVD
SURJUDPPLQJRUGHDO
6HQVLWLYLW\&DOFXODWLRQV3ORWVRQORJORJVFDOHVZHUHÀWWHGZLWK
GLIÀFXOW\WRDFFXUDWHO\SURGXFHFXUYHGOLQHVDQGOHGWRÁDZHG
SDWKSHQDOW\FDOFXODWLRQV
&DOLEUDWLRQ7KHGHPDQGVRIDFFXUDWHO\PDNLQJWZRLGHQWLFDO
PHDVXUHPHQWVZLWKWKHH[FHSWLRQRIDQDGGHGOHQJWKRIÀEHU
WRRQHRIWKHPPHDQWH[WUDWLPHZDVVSHQWFDOLEUDWLQJSDWK
SHQDOW\WHVWVHWVWRREWDLQJRRGUHVXOWV7KHODUJHQXPEHU
RILQWHUFRQQHFWVDQGLQVWUXPHQWVXVHGWRPDNHSDWKSHQDOW\
PHDVXUHPHQWVQHFHVVLWDWHGSDLQVWDNLQJPHWKRGLFDOFDOLEUDWLRQ
URXWLQHV
$QDO\VLV0DNLQJVXUHDWUDQVPLWWHUZRUNHGRYHULWVLQWHQGHG
UDQJHUHTXLUHGPRUHWKDQDVLPSOHJRQRJRWHVWRYHUDOHQJWK
RIÀEHUEXWLPSOHPHQWLQJDFFHSWDEOHSDWKSHQDOW\WHVWVZDV
GLIÀFXOW&KHFNLQJIRUHUURUÁRRUVZDVHDV\IRUDWUDLQHG
HQJLQHHUWRVHHZKHQSORWWHGEXWGLIÀFXOWWRZULWHLQWR $JSDBEJBOU4ZTUFNT *OD
SURGXFWLRQWHVWVRIWZDUH
,PSHULDO:D\6XLWH&
$OOHQWRZQ3$
7HO 7ROO)UHH
$OO5LJKWV5HVHUYHG
301
Application Briefs
16.5 Transmitter Optical Output Power Testing
7UDQVPLWWHU FRQVROLGDWHVOD\HURQHWZRDQGWKUHHLQVWUXPHQWVDQG
2SWLFDO2XWSXW V\VWHPVDQGDXWRPDWHVVWDQGDUGWUDQVPLWWHUDQGUHFHLYHUWHVWV
3RZHU7HVWLQJ 2SWLFDO6HQVLWLYLW\9DU\WKHRSWLFDOSRZHUOHYHORU2SWLFDO
7KHRSWLFDORXWSXWSRZHUIURPD 6WUHVVHG5HFHLYHU&RQIRUPDQFH*HQHUDWHDFDOLEUDWHG,(((
WUDQVPLWWHULVQRUPDOO\VSHFLÀHGWREH DHGHJUDGHGVLJQDOMLWWHUÀOWHULQWHUIHULQJVLJQDOH[WLQFWLRQUDWLR
ZLWKLQDUDQJH,WPXVWEHKLJKHQRXJK DQGFDOFXODWHWKH'87·VUHFHLYHUVHQVLWLYLW\
WRHQDEOHWKHVLJQDOWRWUDYHOWKURXJKD %(5YV26156WHSWKURXJKDUDQJHRIFDOLEUDWHG2SWLFDO6LJQDOWR
VSHFLÀHGDPRXQWRIDWWHQXDWLRQEXWQRW SORWDQGFDOFXODWHWKH'87·VUHFHLYHU%(5YV2615VHQVLWLYLW\
WRRKLJKWKDWLWZLOOVDWXUDWHLWVFRPSDQLRQ 2SWLFDO3DWK3HQDOW\3HUIRUPWZRVHQVLWLYLW\PHDVXUHPHQWVZLWK
UHFHLYHUZKHQRSHUDWHGXVLQJDPLQLPDO ÀEHU$XWRPDWLFDOO\SORWHDFKVHQVLWLYLW\WHVWDQGFDOFXODWHWKHRSWLFDO
DPRXQWRIÀEHUEHWZHHQWKHWZRGHYLFHV SRZHUGLIIHUHQFHEHWZHHQWKHPDWDVHOHFWHG%(5OHYHO
7UDQVPLWWHURSWLFDORXWSXWSRZHULV 2SWLFDO2YHUORDG0DNHVHQVLWLYLW\PHDVXUHPHQWVZKLOHVWHSSLQJ
VSHFLÀHGLQP:RUG%P WKHRSWLFDOLQSXWSRZHUDWZKLFKWKH'87·VUHFHLYHURYHUORDGVDQG
JHQHUDWHVHUURUV
,VVXHV 3UREOHPV SUHSURJUDPPHGOLVWRIWHVWV,QGHEXJPRGHWKH267FRQWUROVD'&$
0HDVXULQJWKHGLUHFWRSWLFDOSRZHURIDWUDQVPLWWHU ZDYHPHWHUDQGDQRSWLFDOVZLWFKWRJHQHUDWHWHVWGDWDWKDWZRXOGWDNH
FRQQHFWHGWRDSRZHUPHWHUXVLQJDVKRUWOHQJWK KRXUVWRFROOHFWPDQXDOO\
RIÀEHULVVWUDLJKWIRUZDUG7KHSUREOHPVEHJLQ 6;3HQDOW\3HUIRUPWZRVHQVLWLYLW\PHDVXUHPHQWVZLWKDQGZLWKRXW
ZKHQLQWHJUDWLQJWUDQVPLWWHURSWLFDORXWSXWSRZHU DQDGGHGLQWHUIHULQJVLJQDO$XWRPDWLFDOO\SORWHDFKVHQVLWLYLW\WHVWDQG
PHDVXUHPHQWVLQWRPDQXIDFWXULQJWHVWVHWV7RGR FDOFXODWHWKHDGGLWLRQDORSWLFDOSRZHUUHTXLUHGE\WKH'87·VUHFHLYHUWR
WKLVUHTXLUHVFDUHIXOFDOLEUDWLRQDQGSURJUDPPLQJ UHDFKDVHOHFWHG%(5OHYHOZLWKDQDSSOLHGLQWHUIHULQJVLJQDO
WRREWDLQFRQVLVWHQWO\DFFXUDWHPHDVXUHPHQWV
6HFXUHG$FFXUDF\&DOLEUDWLRQ7HVWZLWKRXWZRUU\LQJDERXW
w &DOLEUDWLRQ0XOWLSOHRSWLFDOLQWHUIDFHVLQDWHVW WKH267GULIWLQJRXWRIFDOLEUDWLRQEHFDXVHHDFK267LVDVHOIFRQWDLQHG
VHWUHÁHFWDQGDWWHQXDWHWKHRSWLFDOVLJQDOV PHDVXUHPHQWV\VWHP6HOIFKHFNLQWHUQDOSURFHVVFRQWUROFKDUWVEHJLQ
$FFXPXODWHGGLUWDQGVFUDWFKHGFRQQHFWRUV ZKLOHWKH267LVVWLOODWWKH&LUFDGLDQWIDFWRU\WRDVVXUHWKH267LVDOZD\V
FKDQJHWKHDPRXQWRIDWWHQXDWLRQ7KHLQVHUWLRQ LQFDOLEUDWLRQ
ORVVRISDVVLYHFRPSRQHQWVEHWZHHQWKH
WUDQVPLWWHUDQGWKHRSWLFDOSRZHUPHWHUUHTXLUHV 6WUDLJKW/LQH%(53ORWVHQVLWLYLW\WHVWVRSWLFDOSRZHU20$
FRPSHQVDWLRQLQRUGHUWRREWDLQDFFXUDWHRSWLFDO
SRZHUPHDVXUHPHQWV LPPHGLDWHO\DQGFRQFOXVLYHO\WRWKHXVHU
w 3
URJUDPPLQJ6RIWZDUHPXVWEHZULWWHQWR ,QWHOOL6FULSW7HVWLQJ6HTXHQFHWKURXJKVWDQGDUGEXLOWLQWHVWVDQG
FUHDWHDWHVWVHWFDOLEUDWLRQSURFHGXUHDQG FRQWUROH[WHUQDOLQVWUXPHQWVVXFKDVHQYLURQPHQWDOFKDPEHUVSRZHU
GHÀQHPD[LPXPDQGPLQLPXPRSWLFDOSRZHU VXSSOLHV26$VRSWLFDOVZLWFKHVRVFLOORVFRSHVDQGZDYHOHQJWKPHWHUV
UDQJHV
302
Transmitter Optical Output Power Testing
&DOLEUDWLRQ7KH6HFXUHG$FFXUDF\FDOLEUDWLRQIHDWXUH
RIWKH267DVVXUHVWKDWWKH267LVDOZD\VLQFDOLEUDWLRQ
3DVVLYHORVVHVEHWZHHQWKHWUDQVPLWWHU'87DQGWKH267
DUHHDVLO\IDFWRUHGRXWZLWKDQDXWRPDWHGSURFHGXUH
WKDWDVVXUHVDFFXUDWHPHDVXUHPHQWV7KH267·VEXLOW
LQSRZHUPHWHULVWXQHGIRUQPDQGQP
ZLQGRZSHUIRUPDQFH%\VLPSO\HQWHULQJWKHWUDQVPLWWHU
ZDYHOHQJWKWKH267FDOFXODWHVWKHDFFXUDWHSRZHUOHYHO
)XVLRQVSOLFHVLQVLGHWKH267OLPLWWKHQXPEHURIRSWLFDO
LQWHUIDFHVIRUFRQVLVWHQWWHVWPHDVXUHPHQWV
3URJUDPPLQJ0HDVXULQJRSWLFDORXWSXWSRZHULVRQHRI
WKH267·VDXWRPDWHGWHVWSURJUDPV7KHPD[LPXPDQG
&DOLEUDWLRQ7UDQVPLWWHURSWLFDORXWSXWSRZHUZDVRQHRIPDQ\ PLQLPXPG%RUP:3$66)$,/YDOXHVDUHHDVLO\HQWHUHG
WHVWVFRQGXFWHGRQWUDQVPLWWHUVDQGUHFHLYHUV7KHXVXDOWHVWVHW XVLQJWKH267·VYHU\XVHUIULHQGO\*UDSKLFDO8VHU,QWHUIDFH
KDGQXPHURXVLQVWUXPHQWVDQGSDVVLYHFRPSRQHQWVZLWKODUJH *8,
QXPEHUVRIRSWLFDOLQWHUIDFHVUHTXLULQJFDUHIXOKDQGOLQJDQG
FOHDQLQJ3RZHUORVVFDXVHGE\DOOWKHVSOLWWHUVDWWHQXDWRUV $QDO\VLV0DNLQJRSWLFDOSRZHUPHDVXUHPHQWVZLWK
FRQQHFWRUVVZLWFKHVDQGÀEHUKDGWREHPHDVXUHGDQGIDFWRUHG DQ267LVHDV\&DOLEUDWLRQLVDXWRPDWHGDQGWKH
LQWRWKHFDOLEUDWLRQSURFHGXUH(YHQFDEOHPRYHPHQWFRQQHFWRU SURJUDPPLQJLVDOUHDG\GRQH
VXUIDFHTXDOLW\DQGGLUWFKDQJHGWKHFDOLEUDWLRQIDFWRU5HJXODU
DQGWLPHFRQVXPLQJFDOLEUDWLRQSURFHGXUHVKDGWREHUXQ

3URJUDPPLQJ6WDQGDUGL]HGSURJUDPPLQJWHVWODQJXDJHV
ZHUHXVHGWRFRQWUROWHVWVHWV,IWKHVLJQDOSDVVHGWKURXJKDQ
DWWHQXDWRUWKHQWKHSURJUDPKDGWRIDFWRULQWKHDWWHQXDWRUVHW
SRLQW/RRNXSWDEOHVZHUHXVHGWRFRPSHQVDWHIRUZDYHOHQJWK
GHSHQGHQF\2SWLFDOSRZHUPHDVXUHPHQWVKDGWREHDGMXVWHG
EDVHGRQWKHSRZHUORVVWKURXJKSDVVLYHFRPSRQHQWV(DFK
WUDQVPLWWHUW\SHWHVWHGKDGWRKDYHLWVRZQSURJUDPVSHFLI\LQJ
WKHPLQLPXPDQGPD[LPXPRSWLFDOSRZHU3$66)$,/OHYHOV$Q\
QHZWUDQVPLWWHURUFKDQJHGGHYLFHVSHFLÀFDWLRQUHTXLUHGFKDQJHV
WRWKHSURJUDPPLQJFRGH
$QDO\VLV(YHQUHODWLYHO\VLPSOHRSWLFDOSRZHUPHDVXUHPHQWV
GHPDQGHGULJRURXVDWWHQWLRQWRGHWDLOWRREWDLQDFFXUDWHUHVXOWV
7HVWVHWGULIWPDGHFDOLEUDWLRQDFRQVWDQWFKRUH
,PSHULDO:D\6XLWH&
$OOHQWRZQ3$
7HO 7ROO)UHH
$OO5LJKWV5HVHUYHG
303
Application Briefs
16.6 Optical Overload Testing
2SWLFDO2YHUORDG FRQVROLGDWHVOD\HURQHWZRDQGWKUHHLQVWUXPHQWVDQG
2SWLFDOUHFHLYHUVPXVWRSHUDWHYLUWXDOO\ 6WUHVVHG5HFHLYHU&RQIRUPDQFH*HQHUDWHDFDOLEUDWHG,(((
DHGHJUDGHGVLJQDOMLWWHUÀOWHULQWHUIHULQJVLJQDOH[WLQFWLRQUDWLR
HUURUIUHHRYHUDZLGHUDQJHRIRSWLFDO
SRZHUV2YHUORDGWHVWLQJGHWHUPLQHVLI DQGFDOFXODWHWKH'87·VUHFHLYHUVHQVLWLYLW\
DUHFHLYHUKDVDORZ%(5ZKLOHRSHUDWLQJ %(5YV26156WHSWKURXJKDUDQJHRIFDOLEUDWHG2SWLFDO6LJQDOWR
ZLWKKLJKHURSWLFDOLQSXWSRZHUV SORWDQGFDOFXODWHWKH'87·VUHFHLYHU%(5YV2615VHQVLWLYLW\
2SWLFDO3DWK3HQDOW\3HUIRUPWZRVHQVLWLYLW\PHDVXUHPHQWVZLWK
,VVXHV 3UREOHPV ÀEHU$XWRPDWLFDOO\SORWHDFKVHQVLWLYLW\WHVWDQGFDOFXODWHWKHRSWLFDO
SRZHUGLIIHUHQFHEHWZHHQWKHPDWDVHOHFWHG%(5OHYHO
7KHSULQFLSDOSUREOHPVIDFHGLQRYHUORDGWHVWLQJ
7UDQVPLWWHU2SWLFDO2XWSXW3RZHU&RPSDUHWKHWRWDORSWLFDO
DUHREWDLQLQJKLJKRXWSXWSRZHUWHVWVRXUFHV
PDNLQJKLJKSRZHU%(5PHDVXUHPHQWVDQG
DQGPD[LPXPUDQJH$XWRPDWLFDOO\FDWHJRUL]HWKH'87DVD3$66RU)$,/
PDLQWDLQLQJFDOLEUDWLRQ
w +LJK3RZHU5HFHLYHUVPXVWEHWHVWHGDWKLJK DXWRPDWLFDOO\PDNLQJSURJUHVVLYOH\PRUHGLIÀFXOWPHDVXUHPHQWVIURPD
RSWLFDOSRZHUOHYHOVWRJXDUDQWHHHUURUIUHH SUHSURJUDPPHGOLVWRIWHVWV,QGHEXJPRGHWKH267FRQWUROVD'&$
SHUIRUPDQFHEXWWHVWHTXLSPHQWLVQRWUHDGLO\ ZDYHPHWHUDQGDQRSWLFDOVZLWFKWRJHQHUDWHWHVWGDWDWKDWZRXOGWDNH
DYDLODEOHSURYLGLQJKLJKHQRXJKRXWSXWSRZHU KRXUVWRFROOHFWPDQXDOO\
OHYHOV$VDUHVXOWYDOXDEOHWHVWHQJLQHHULQJ
UHVRXUFHVDUHVSHQWWRGHVLJQDVVHPEOH 6;3HQDOW\3HUIRUPWZRVHQVLWLYLW\PHDVXUHPHQWVZLWKDQGZLWKRXW
DQDGGHGLQWHUIHULQJVLJQDO$XWRPDWLFDOO\SORWHDFKVHQVLWLYLW\WHVWDQG
DQGGHJEXJFXVWRPWHVWVHWVZLWKRSWLFDOO\
DPSOLÀHGVLJQDOV
w %(50HDVXUHPHQWV7KH%(5YVRSWLFDOSRZHU
6HFXUHG$FFXUDF\&DOLEUDWLRQ7HVWZLWKRXWZRUU\LQJDERXW
SHUIRUPDQFHRIDUHFHLYHUQHDURYHUORDG
WKH267GULIWLQJRXWRIFDOLEUDWLRQEHFDXVHHDFK267LVDVHOIFRQWDLQHG
FDQFKDQJHUDSLGO\IURPHUURUIUHHWRORWV PHDVXUHPHQWV\VWHP6HOIFKHFNLQWHUQDOSURFHVVFRQWUROFKDUWVEHJLQ
RIHUURUV)LQGLQJWKHDSSURSULDWHUDQJH ZKLOHWKH267LVVWLOODWWKH&LUFDGLDQWIDFWRU\WRDVVXUHWKH267LVDOZD\V
RIRSWLFDOSRZHUWRWHVWLVRIWHQIUXVWUDWLQJ LQFDOLEUDWLRQ
²HVSHFLDOO\ZKHQK\VWHUHVLVLVLQYROYHG
w &DOLEUDWLRQ0DLQWDLQLQJFDOLEUDWLRQRI RU2615YV%(5RQWKHSURSHUVFDOHVXFKWKDWWKHGDWDZLOOIDOORQD
FRPSOH[WHVWHTXLSPHQWZLWKPDQ\RSWLFDO VWUDLJKWOLQHIRUDZHOOEHKDYHGGHYLFH8QH[SHFWHGEHKDYLRULVUHYHDOHG
LQWHUFRQQHFWVLVGLIÀFXOWDQGWLPHFRQVXPLQJ LPPHGLDWHO\DQGFRQFOXVLYHO\WRWKHXVHU
\HWQHFHVVDU\IRU5 'RUPDQXIDFWXULQJ
HQJLQHHUVWRREWDLQPHDQLQJIXOWHVWUHVXOWV ,QWHOOL6FULSW7HVWLQJ6HTXHQFHWKURXJKVWDQGDUGEXLOWLQWHVWVDQG
FRQWUROH[WHUQDOLQVWUXPHQWVVXFKDVHQYLURQPHQWDOFKDPEHUVSRZHU
:RUOGZLGHPXOWLIDFLOLW\PDQXIDFWXULQJ
VLJQLÀFDQWO\LQWHQVLÀHVWKLVSUREOHP
304
Optical Overload Testing
+LJK3RZHU7KHQP267LQFOXGHVDEXLOWLQ(')$ZLWK
DÀOWHUWRSURGXFHKLJKRXWSXWSRZHUVLJQDOVVXLWDEOHIRU
RSWLFDORYHUORDGWHVWLQJ
%(50HDVXUHPHQWV2YHUORDGPHDVXUHPHQWURXWLQHV
DUHSUHSURJUDPPHGDQGDSSURSULDWH%(5OHYHOVDUH
DXWRPDWLFDOO\WHVWHG7KHUHVXOWVDUHSORWWHGDQGWKHKLJK
RSWLFDOSRZHUOHYHOWKDWSURGXFHVDVSHFLÀHG%(5OHYHOLV
GLVSOD\HGQH[WWRD3$66)$,/LQGLFDWRU
$QDO\VLV$XWRPDWLRQRIRSWLFDORYHUORDGWHVWLQJDVVXUHV
WKDWHDFKGHVLJQFKDQJHZLOOQRWFDXVHDUHFHLYHU
+LJK3RZHU6HQLRUHQJLQHHUVVSHQWSUHFLRXVWLPHWRGHVLJQ WRSURGXFHHUURUVDWWKHWRSRIWKHVSHFLÀHGLQSXW
DVVHPEOHDQGGHEXJVHQVLWLYLW\WHVWVHWVZLWKDQGDGGHG(')$WR SRZHUUDQJH2QJRLQJFRVWUHGXFWLRQDQGFRPSRQHQW
ERRVWWKH%(57RUSURWRFRODQDO\]HU·VQPRXWSXW'87VZHUH UHSODFHPHQWDFWLYLWLHVPD\EHSHUIRUPHGE\PDQXIDFWXULQJ
RFFDVLRQDOO\GDPDJHGE\KLJKRSWLFDOSRZHUEXUVWVFDXVHGE\IXOO\ HQJLQHHULQJZLWKRXWLQYROYLQJ5 'HQJLQHHUVDQGWKHLUWHVW
FKDUJHG(')$V$ÀOWHUZDVDOVRLQFOXGHGLQWKHWHVWVHWWRUHPRYH HTXLSPHQW
WKHXQZDQWHGSRZHUDGGHGE\WKH(')$
%(50HDVXUHPHQWV,QPDQ\FDVHVRYHUORDGZDVQRWD
SURJUDPPHGWHVW)RUHDFKQHZGHVLJQ5 'HQJLQHHUVPDQXDOO\
DGMXVWHGDWWHQXDWRUVDQGWUDFNHGDQGSORWWHGWKH%(5DWKLJK
LQSXWSRZHUOHYHOVLQRUGHUWRWHVWDVPDOOVDPSOHRIUHFHLYHUVIRU
RSWLFDORYHUORDG
&DOLEUDWLRQ'LVWXUELQJWHVWHTXLSPHQWE\DGGLQJDQ(')$DQG
ÀOWHUUHTXLUHGFDUHIXOFDOLEUDWLRQ6RPHWLPHVRSWLFDOVZLWFKHV
ZHUHDGGHGWRWKHWHVWVHWWRSHUPDQHQWO\DFFRPPRGDWHWKH(')$
DQGÀOWHUEXWWKHVHDGGHGDGGLWLRQDOFRPSOH[LW\DQGLQFUHDVHG
GDLO\FDOLEUDWLRQUHTXLUHPHQWV
$QDO\VLV5HFHLYHUVQHHGHGWREHWHVWHGIRURSWLFDORYHUORDG
LQFDVHDXVHUFRQQHFWHGDKRWWUDQVPLWWHUEDFNWREDFNZLWK
DUHFHLYHUEXWWKLVWHVWKDVRIWHQEHHQRPLWWHGEHFDXVHWKHUH
ZDVQRVWDQGDUGWHVWHTXLSPHQWZLWKKLJKHQRXJKRXWSXWSRZHU
DYDLODEOH$VDUHVXOWQRQFRPSOLDQWSURGXFWVZHUHVKLSSHGDQG
UHWXUQUDWHVZHUHLPSDFWHG
,PSHULDO:D\6XLWH&
$OOHQWRZQ3$
7HO 7ROO)UHH
$OO5LJKWV5HVHUYHG
305
Application Briefs
16.7 Debug Testing of Manufacturing Rejects and Customer

Returns
'HEXJ7HVWLQJRI FRQVROLGDWHVOD\HURQHWZRDQGWKUHHLQVWUXPHQWVDQG
0DQXIDFWXULQJ5HMHFWV V\VWHPVDQGDXWRPDWHVVWDQGDUGWUDQVPLWWHUDQGUHFHLYHUWHVWV
DQG&XVWRPHU5HWXUQV 2SWLFDO6HQVLWLYLW\9DU\WKHRSWLFDOSRZHUOHYHORU2SWLFDO
'HEXJWHVWLQJRISURGXFWVWKDWIDLO 6WUHVVHG5HFHLYHU&RQIRUPDQFH*HQHUDWHDFDOLEUDWHG,(((
LQSURGXFWLRQDQGIDLOXUHDQDO\VLVRI DHGHJUDGHGVLJQDOMLWWHUÀOWHULQWHUIHULQJVLJQDOH[WLQFWLRQUDWLR
FXVWRPHUUHWXUQVDUHPDMRUGLOHPPDV DQGFDOFXODWHWKH'87·VUHFHLYHUVHQVLWLYLW\
IDFLQJPDQXIDFWXULQJH[HFXWLYHV %(5YV26156WHSWKURXJKDUDQJHRIFDOLEUDWHG2SWLFDO6LJQDOWR
&RPSRXQGWKDWZLWKVXEFRQWUDFWRUVZLWK SORWDQGFDOFXODWHWKH'87·VUHFHLYHU%(5YV2615VHQVLWLYLW\
JOREDOORFDWLRQVDQGWKHSUREOHPVDUH 2SWLFDO3DWK3HQDOW\3HUIRUPWZRVHQVLWLYLW\PHDVXUHPHQWVZLWK
H[DFHUEDWHGHYHQIXUWKHU ÀEHU$XWRPDWLFDOO\SORWHDFKVHQVLWLYLW\WHVWDQGFDOFXODWHWKHRSWLFDO
7UDQVPLWWHU2SWLFDO2XWSXW3RZHU&RPSDUHWKHWRWDORSWLFDO
,VVXHV 3UREOHPV RXWSXWSRZHUHPLWWHGE\WKH'87·VWUDQVPLWWHUWRWKHGHÀQHGPLQLPXP
7KHGLIÀFXOWLVVXHKHUHLVGR,GLVUXSWSURGXFWLRQ
RUZRUNRQWKH´ERQHSLOHµRIUHMHFWVZLWKWKH 2SWLFDO2YHUORDG0DNHVHQVLWLYLW\PHDVXUHPHQWVZKLOHVWHSSLQJ
HTXLSPHQWDQGHQJLQHHULQJUHVRXUFHVDWKDQG"'R WKURXJKDUDQJHRIKLJKRSWLFDOSRZHUV$XWRPDWLFDOO\SORWDQGFDOFXODWH
,ZRUNRQ\LHOGRSWLPL]DWLRQDQGFRVWUHGXFWLRQRU WKHRSWLFDOLQSXWSRZHUDWZKLFKWKH'87·VUHFHLYHURYHUORDGVDQG
PDNHWKHELOOLQJVSODQQXPEHUKDSSHQ"+RZUHDOO\ JHQHUDWHVHUURUV
FULWLFDOLVWKDWFXVWRPHU)0$",I,DVNP\)DU(DVW 6;3HQDOW\3HUIRUPWZRVHQVLWLYLW\PHDVXUHPHQWVZLWKDQGZLWKRXW
VXEFRQWUDFWRUWRGLYHUWSURGXFWLRQWRZRUNRQ DQDGGHGLQWHUIHULQJVLJQDO$XWRPDWLFDOO\SORWHDFKVHQVLWLYLW\WHVWDQG
WKLVFDQ,VWLOOPDNHP\ELOOLQJVSODQ"'RHVWKH FDOFXODWHWKHDGGLWLRQDORSWLFDOSRZHUUHTXLUHGE\WKH'87·VUHFHLYHUWR
VXEFRQWUDFWRUKDYHWKHWHFKQLFDOUHVRXUFHVWRGHDO UHDFKDVHOHFWHG%(5OHYHOZLWKDQDSSOLHGLQWHUIHULQJVLJQDO
ZLWKWKLV"+RZZHOOGRZHFRUUHODWHEHWZHHQP\ 6HFXUHG$FFXUDF\&DOLEUDWLRQ7HVWZLWKRXWZRUU\LQJDERXW
VXEFRQWUDFWRUV·WHVWLQJDQGRXU5 'FHQWHURUZLWK WKH267GULIWLQJRXWRIFDOLEUDWLRQEHFDXVHHDFK267LVDVHOIFRQWDLQHG
WKHFXVWRPHU" PHDVXUHPHQWV\VWHP6HOIFKHFNLQWHUQDOSURFHVVFRQWUROFKDUWVEHJLQ
LQFDOLEUDWLRQ
7KH6ROXWLRQ 6WUDLJKW/LQH%(53ORWVHQVLWLYLW\WHVWVRSWLFDOSRZHU20$
:KDWLI\RXKDGDSURGXFWLRQWHVWHUFURVVLQJ RU2615YV%(5RQWKHSURSHUVFDOHVXFKWKDWWKHGDWDZLOOIDOORQD
PXOWLSOHSURGXFWW\SHVWKDWFRXOGDXWRPDWLFDOO\ VWUDLJKWOLQHIRUDZHOOEHKDYHGGHYLFH8QH[SHFWHGEHKDYLRULVUHYHDOHG
SHUIRUPIDLOXUHDQDO\VLVLQDQRSHUDWRUIULHQGO\ LPPHGLDWHO\DQGFRQFOXVLYHO\WRWKHXVHU
ZD\ELQWKHIDLOXUHVDQGKDGWKHIXUWKHU ,QWHOOL6FULSW7HVWLQJ6HTXHQFHWKURXJKVWDQGDUGEXLOWLQWHVWVDQG
DELOLW\WRGRZQORDGWKHDQDO\VLVGDWDLQWRDZHE FRQWUROH[WHUQDOLQVWUXPHQWVVXFKDVHQYLURQPHQWDOFKDPEHUVSRZHU
DFFHVVLEOHGDWDEDVHIRUJOREDODQDO\VLV:KDW VXSSOLHV26$VRSWLFDOVZLWFKHVRVFLOORVFRSHVDQGZDYHOHQJWKPHWHUV
LIWKDWWHVWHUZDVFRUUHODWHGWR\RXU5 'DQG
FXVWRPHU·VWHVWHUV":KDWLPSDFWFRXOGWKDWKDYH
LQPLQLPL]LQJ:,3LQYHQWRULHVORZHULQJFRVWVRQ
DUHDOWLPHEDVLVZKLOHPDNLQJFXVWRPHUVKDSS\"
7KH&LUFDGLDQW267EULQJVWKHVHFDSDELOLWLHVWR
\RXUJOREDOPDQXIDFWXULQJHQYLURQPHQW
306
Debug Testing of Manufacturing Rejects and Customer Returns
&RVW$YRLGDEOHFRVWVZHUHLQFXUUHGEHFDXVHRIWKHORQJIHHGEDFN &RVW8VLQJWKH267SURGXFWWHVWLQJIDLOXUHVDUHTXLFNO\
ORRSEHWZHHQSURGXFWIDLOXUHDQGZKHQWKHIDLOXUHPHFKDQLVP GHEXJJHGDQGUHDG\IRUUHZRUNDQGVKLSPHQW,QYHQWRU\
ZDVXQGHUVWRRG([WUDODERUDQGPDWHULDOZDVQHHGHGWR FRVWVGURSUHYHQXHVULVHDQGZULWHRIIVDUHUHGXFHG
FRYHUVFUDSUDWHVDQGZDUUDQWHHUHSDLUV7KHUHZDVDOVRWKH
RSSRUWXQLW\FRVWDVVRFLDWHGZLWKFRQWLQXLQJWREXLOGGHIHFWLYH 3ULRULW\7HVWIDLOXUHVGXULQJPDQXIDFWXULQJDUHGLDJQRVHG
SURGXFWORQJHUWKDQQHFHVVDU\ IDVWHUDQGUHVROYHGPRUHHDVLO\5DSLGFRUUHFWLYHDFWLRQ
UHGXFHVVFUDSUDWHV
3ULRULW\7KHUHZDVQHYHUDFRQYHQLHQWWLPHWRZRUNRQWKH
´ERQHSLOHµWKHUHZDVDOZD\VDKLJKHUSULRULW\5 'HQJLQHHUV 'LIÀFXOW\'HEXJWHVWLQJLVVLPSOLÀHG$WUHPHQGRXV
ZDQWHGWRPHHWWKHLUQHZSURGXFWLQWURGXFWLRQVFKHGXOHVLQVWHDG DPRXQWRILQIRUPDWLRQLVDXWRPDWLFDOO\JHQHUDWHGRQD
RIVROYLQJPDQXIDFWXULQJSUREOHPV IDLOHGSURGXFW5HODWLYHO\XQWUDLQHGWHFKQLFLDQVFDQFRQ
GXFWWKHWHVWLQJ
'LIÀFXOW\7LPHFRQVXPLQJDQGPHWKRGLFDOGHEXJWHVWLQJZDV
UHTXLUHGWRXQGHUVWDQGYH[LQJSUREOHPVQRWUHYHDOHGLQUHJXODU &RUUHODWLRQ(DFK267LVFRUUHODWHGWRDOORWKHU267VLQWKH
PDQXIDFWXULQJWHVW7KHQHHGWRSHUIRUPDZLGHUDQJHRI ZRUOGDQGSURGXFHVWKHVDPHWHVWUHVXOWVIRUPDQXIDFWXU
WHVWVRQPDQ\GLIIHUHQWSURGXFWVPHDQWWKHPRVWLQGHPDQG LQJVXEFRQWUDFWRUV5 'DQGFXVWRPHUV
HQJLQHHUVDQGWHFKQLFLDQVZHUHDOVRWKHEHVWVXLWHGWRZRUNWKH
GHEXJVWDWLRQ7KHQHHGWRERUURZWHVWHTXLSPHQWIURP5 'RU *OREDO'DWDEDVH'HWDLOHGGHEXJWHVWGDWDLVDYDLODEOH
PDQXIDFWXULQJWRFRQGXFWVRPHWHVWVZDVDKLQGUDQFHWRWLPHO\ WKURXJKWKH267·VZHEEURZVHU7KLVVKRUWHQVWKHSUREOHP
DQGHIÀFLHQWIDLOXUHDQDO\VLV UHVROXWLRQWLPHEHFDXVHHQJLQHHUVDOORYHUWKHZRUOGKDYH
IXOODFFHVVWRWKHGHEXJWHVWGDWD
&RUUHODWLRQ&RUUHODWLRQEHWZHHQPDQXIDFWXULQJWHVWVWDWLRQV
RQWKHVDPHÁRRUZDVKDUGHQRXJKEXWFRUUHODWLRQEHWZHHQ
PDQXIDFWXULQJVXEFRQWUDFWRUV5 'DQGFXVWRPHUVZKLOHDOZD\V
DJRDOZDVQHYHUDUHDOLW\
*OREDO'DWDEDVH:KHQUHMHFWVZHUHVXEMHFWHGWRDGGLWLRQDO
WHVWVWKHGHWDLOHGWHVWGDWDZDVRXWVLGHRIWKHPDQXIDFWXULQJ
GDWDEDVHDQGZDVLQDFFHVVLEOHWRHQJLQHHUVWKDWZHUHQRW
FROORFDWHGZLWKWKHWHVWHTXLSPHQW7KLVLQHIÀFLHQF\GHOD\HG
SUREOHPUHVROXWLRQHVSHFLDOO\ZKHQGHEXJWHVWLQJDQG5 'ZHUH
LQGLVWDQWWLPH]RQHV $JSDBEJBOU4ZTUFNT *OD
,PSHULDO:D\6XLWH&
$OOHQWRZQ3$
7HO 7ROO)UHH
$OO5LJKWV5HVHUYHG
307
Application Briefs
16.8 Test Set Calibration
7HVW6HW FRQVROLGDWHVOD\HURQHWZRDQGWKUHHLQVWUXPHQWVDQG
&DOLEUDWLRQ V\VWHPVDQGDXWRPDWHVVWDQGDUGWUDQVPLWWHUDQGUHFHLYHUWHVWV
&DOLEUDWLQJWHVWVHWVLVHVVHQWLDOLI 6WUHVVHG5HFHLYHU&RQIRUPDQFH*HQHUDWHDFDOLEUDWHG,(((
YDOLGWHVWUHVXOWVDUHWREHREWDLQHG DHGHJUDGHGVLJQDOMLWWHUÀOWHULQWHUIHULQJVLJQDOH[WLQFWLRQUDWLR
&DOLEUDWLRQLQFOXGHVHQVXULQJWKHDFFXUDF\ DQGFDOFXODWHWKH'87·VUHFHLYHUVHQVLWLYLW\
RIWKHLQGLYLGXDOLQVWUXPHQWVLQWKHWHVW %(5YV26156WHSWKURXJKDUDQJHRIFDOLEUDWHG2SWLFDO6LJQDOWR
VHWE\FRPSDULQJWKHPZLWKUHOHYDQW SORWDQGFDOFXODWHWKH'87·VUHFHLYHU%(5YV2615VHQVLWLYLW\
VWDQGDUGV,WDOVRLQFOXGHVHVWDEOLVKLQJ 2SWLFDO3DWK3HQDOW\3HUIRUPWZRVHQVLWLYLW\PHDVXUHPHQWVZLWK
WKDWWKHDUUDQJHPHQWRILQVWUXPHQWV ÀEHU$XWRPDWLFDOO\SORWHDFKVHQVLWLYLW\WHVWDQGFDOFXODWHWKHRSWLFDO
DQGLQWHUFRQQHFWVLVVWDELOL]HGDQG SRZHUGLIIHUHQFHEHWZHHQWKHPDWDVHOHFWHG%(5OHYHO
DQ\FRPSHQVDWLQJDGMXVWPHQWVDUH 7UDQVPLWWHU2SWLFDO2XWSXW3RZHU&RPSDUHWKHWRWDORSWLFDO
LPSOHPHQWHG DQGPD[LPXPUDQJH$XWRPDWLFDOO\FDWHJRUL]HWKH'87DVD3$66RU)$,/
,VVXHV 3UREOHPV 2SWLFDO2YHUORDG0DNHVHQVLWLYLW\PHDVXUHPHQWVZKLOHVWHSSLQJ

7KHSULQFLSDOSUREOHPVIDFHGGXULQJWHVWVHW WKHRSWLFDOLQSXWSRZHUDWZKLFKWKH'87·VUHFHLYHURYHUORDGVDQG
FDOLEUDWLRQDUHWKHLQDELOLW\WRFRQÀUPWKDWWKH JHQHUDWHVHUURUV
LQGLYLGXDOLQVWUXPHQWVLQWKHWHVWVHWDUHFDOLEUDWHG
RUWKDWWKHHQWLUHWHVWVHWLVFDOLEUDWHGDQGWKH DXWRPDWLFDOO\PDNLQJSURJUHVVLYOH\PRUHGLIÀFXOWPHDVXUHPHQWVIURPD
OHQJWK\WLPHUHTXLUHGWRSHUIRUPFDOLEUDWLRQ SUHSURJUDPPHGOLVWRIWHVWV,QGHEXJPRGHWKH267FRQWUROVD'&$
SURFHGXUHV ZDYHPHWHUDQGDQRSWLFDOVZLWFKWRJHQHUDWHWHVWGDWDWKDWZRXOGWDNH
w ,QGLYLGXDO,QVWUXPHQW&DOLEUDWLRQ,QVWUXPHQWV KRXUVWRFROOHFWPDQXDOO\
FDQGULIWRUEHNQRFNHGRXWRIFDOLEUDWLRQ7HVW 6;3HQDOW\3HUIRUPWZRVHQVLWLYLW\PHDVXUHPHQWVZLWKDQGZLWKRXW
LQVWUXPHQWVDUHW\SLFDOO\FDOLEUDWHGHYHU\ DQDGGHGLQWHUIHULQJVLJQDO$XWRPDWLFDOO\SORWHDFKVHQVLWLYLW\WHVWDQG
PRQWKVDJDLQVWDVWDQGDUG$QDQQXDOFDOLEUDWLRQ FDOFXODWHWKHDGGLWLRQDORSWLFDOSRZHUUHTXLUHGE\WKH'87·VUHFHLYHUWR
VWLFNHULVQRJXDUDQWHHWKDWDQLQVWUXPHQWZLOO UHDFKDVHOHFWHG%(5OHYHOZLWKDQDSSOLHGLQWHUIHULQJVLJQDO
DFWXDOO\UHPDLQLQFDOLEUDWLRQ
w 7
HVW6HW&DOLEUDWLRQ,WLVDIRUPLGDEOHWDVNWR RU2615YV%(5RQWKHSURSHUVFDOHVXFKWKDWWKHGDWDZLOOIDOORQD
FDOLEUDWHDQHQWLUHFRPSOH[KLJKVSHHGRSWLFDO VWUDLJKWOLQHIRUDZHOOEHKDYHGGHYLFH8QH[SHFWHGEHKDYLRULVUHYHDOHG
WHVWVHWZLWKDP\ULDGRISRWHQWLDOLQVWUXPHQW LPPHGLDWHO\DQGFRQFOXVLYHO\WRWKHXVHU
DGMXVWPHQWVQXPHURXVRSWLFDODQGHOHFWULFDO ,QWHOOL6FULSW7HVWLQJ6HTXHQFHWKURXJKVWDQGDUGEXLOWLQWHVWVDQG
LQWHUFRQQHFWVORQJFDOLEUDWLRQSURFHGXUHVDQG FRQWUROH[WHUQDOLQVWUXPHQWVVXFKDVHQYLURQPHQWDOFKDPEHUVSRZHU
LQWKHHQGFRUUHODWHZLWKFXVWRPHUVDQGRWKHU VXSSOLHV26$VRSWLFDOVZLWFKHVRVFLOORVFRSHVDQGZDYHOHQJWKPHWHUV
PDQXIDFWXULQJWHVWVHWV
w 7LPH$VLJQLÀFDQWDPRXQWRIWLPHLVVSHQW
HDFK\HDUFDOLEUDWLQJ5 'DQGPDQXIDFWXULQJ
WHVWVHWV7KLVGUDLQVSURGXFWLYHZRUNWLPH
IURPQHZSURGXFWGHYHORSPHQWDQGVXSSUHVVHV
PDQXIDFWXULQJFDSDFLW\
308
Test Set Calibration
,QGLYLGXDO,QVWUXPHQW&DOLEUDWLRQ7KH267LVDVHOI
FKHFNLQJV\VWHP&DOLEUDWLRQRIWKH267LVDXWRPDWLFDOO\
FKHFNHGWRWKHGD\WKH267ZDVPDGHZLWKDQRYHUDOO3$66
RU)$,/YDOXHVKRZQDQGGHWDLOHGUHVXOWVGLVSOD\HGRQD
VHULHVRILQWHUQDOSURFHVVFRQWUROFKDUWV
7HVW6HW&DOLEUDWLRQ&DOLEUDWLRQLVHDV\WKH267·V
LQWHUQDOFDOLEUDWLRQSURFHGXUHLVDXWRPDWHG&RQQHFWLRQV
EHWZHHQWKH267DQGD'87DUHDOVRDXWRPDWLFDOO\
FDOLEUDWHGVRDFFXUDWHUHVXOWVDUHFHUWDLQ%HFDXVHDOO267V
FRUUHODWHZLWKHDFKRWKHUFRUUHODWLRQZLWKFXVWRPHUVDQG
FRQWUDFWPDQXIDFWXUHUVLVDVVXUHG
7LPH7KH267UXQVWKURXJKDVHOIFDOLEUDWLRQURXWLQHLQ
DSSUR[LPDWHO\PLQXWHV
,QGLYLGXDO,QVWUXPHQW&DOLEUDWLRQ(YHU\PRQWKVDQLQVWUXPHQW $QDO\VLV,WLVQRORQJHUQHFHVVDU\WRUHO\RQDQQXDO
ZDVHLWKHUVHQWRXWIRUFDOLEUDWLRQRUDFRPSDQ\ZRXOGFRPH FDOLEUDWLRQVWLFNHUVRUSHUIRUPFRPSOLFDWHGDQGWLPH
LQDQGSHUIRUPRQVLWHFDOLEUDWLRQ7KLVGLVUXSWHG5 'DQG FRQVXPLQJGDLO\FDOLEUDWLRQURXWLQHV:LWKOHVVWLPH
PDQXIDFWXULQJIRUZHHNVDWDWLPH2IWHQGXSOLFDWHWHVW VSHQWFDOLEUDWLQJPDQXIDFWXULQJFDSDFLW\LVLQFUHDVHG
LQVWUXPHQWVKDGWREHSXUFKDVHGWRNHHSWHVWVHWVRSHUDWLRQDO DQGPRUHWLPHLVDYDLODEOHIRUQHZSURGXFWGHYHORSPHQW
GXULQJDQQXDOFDOLEUDWLRQF\FOHV &RQÀGHQFHLQWHVWUHVXOWVLVGUDPDWLFDOO\LQFUHDVHG
EHFDXVHFDOLEUDWLRQLVDVVXUHG
7HVW6HW&DOLEUDWLRQ0DQXIDFWXULQJDQG5 'HQJLQHHUVDOZD\V
ZRUULHGWKDWWKHWHVWVHWLQFOXGLQJWKHLQVWUXPHQWVDQGVRIWZDUH
ZHUHQRORQJHULQFDOLEUDWLRQ:DVWKHUHDORRVHFDEOH":DVD
FRQQHFWRUGLUW\":DVWKHUHDUHÁHFWLRQFUHDWLQJLQWHUPLWWHQW
SUREOHPV"'LGVRPHRQHFKDQJHVRPHWKLQJ",VWKHUHDEXJLQWKH
PRVWUHFHQWVRIWZDUHUHYLVLRQWKDWPLJKWEHFDXVLQJWKHWHVWVHW
WREHRIIE\G%",VWKHUHFRUUHODWLRQZWKFXVWRPHUV",VWKHUH
FRUUHODWLRQZLWKFRQWUDFWPDQXIDFWXUHUV"
7LPH,QPDQXIDFWXULQJLWZDVFRPPRQIRUWKHÀUVWVKLIWRI
WKHGD\WRFDOLEUDWHWKHWHVWVHW'HSHQGLQJRQWKHWHVWVHW
WKLVFRXOGWDNHIURPDSSUR[LPDWHO\PLQXWHVWRPRUHWKDQDQ
KRXU$GGLWLRQDOFDOLEUDWLRQVZHUHUXQZKHQXQH[SHFWHGIDLOXUHV
RFFXUUHGLQDQDWWHPSWWRGHWHUPLQHLIWKHSURGXFWZDVEDGRULI
WKHWHVWVHWVLPSO\ZHQWRXWRIFDOLEUDWLRQ5 'UDQFDOLEUDWLRQ
URXWLQHVSULRUWREHJLQQLQJLPSRUWDQWWHVWV
$QDO\VLV7HVW6HW&DOLEUDWLRQLVYLWDOWRDEXVLQHVV4XDOLW\
\LHOGVDQGVSHFLÀFDWLRQVZHUHSHULRGLFDOO\LPSDFWHGE\LQFRUUHFW
FDOLEUDWLRQV5HO\LQJRQFDOLEUDWLRQVWLFNHUVZDVDJDPEOH
&DOLEUDWLRQFRVWVZHUHEXULHGLQPDQXIDFWXULQJRYHUKHDGDQG5 '
EXGJHWVEXWWKH\DPRXQWHGWRDKLGGHQWD[RQDOOPDQXIDFWXULQJ $JSDBEJBOU4ZTUFNT *OD
DQG5 'DFWLYLWLHV+LJKO\WUDLQHGHQJLQHHUVZHUHQHHGHGWRVHW
,PSHULDO:D\6XLWH&
XSWKHWHVW
$OOHQWRZQ3$
7HO 7ROO)UHH
$OO5LJKWV5HVHUYHG
309
Application Briefs
16.9 Transmitter Functional Testing
7UDQVPLWWHU FRQVROLGDWHVOD\HURQHWZRDQGWKUHHLQVWUXPHQWVDQG
)XQFWLRQDO7HVWLQJ V\VWHPVDQGDXWRPDWHVVWDQGDUGWUDQVPLWWHUDQGUHFHLYHUWHVWV
7KHEDVLFIXQFWLRQDOLW\RIDWUDQVPLWWHU 6WUHVVHG5HFHLYHU&RQIRUPDQFH*HQHUDWHDFDOLEUDWHG,(((
LVFRQÀUPHGE\WHVWLQJDWUDQVPLWWHU DHGHJUDGHGVLJQDOMLWWHUÀOWHULQWHUIHULQJVLJQDOH[WLQFWLRQUDWLR
FRQQHFWHGWRDUHIHUHQFHUHFHLYHUYLD DQGFDOFXODWHWKH'87·VUHFHLYHUVHQVLWLYLW\
DVKRUWOHQJWKRIÀEHUDQGGHWHUPLQLQJ %(5YV26156WHSWKURXJKDUDQJHRIFDOLEUDWHG2SWLFDO6LJQDOWR
WKDWWKHPHDVXUHGUHFHLYHUVHQVLWLYLW\LV SORWDQGFDOFXODWHWKH'87·VUHFHLYHU%(5YV2615VHQVLWLYLW\
DFFHSWDEOH 2SWLFDO3DWK3HQDOW\3HUIRUPWZRVHQVLWLYLW\PHDVXUHPHQWVZLWK
,VVXHV 3UREOHPV 7UDQVPLWWHU2SWLFDO2XWSXW3RZHU&RPSDUHWKHWRWDORSWLFDO
7KHSULQFLSDOSUREOHPVIDFHGLQWUDQVPLWWHU RXWSXWSRZHUHPLWWHGE\WKH'87·VWUDQVPLWWHUWRWKHGHÀQHGPLQLPXP
IXQFWLRQDOWHVWLQJDUHGHWHUPLQLQJWKHUHFHLYHU DQGPD[LPXPUDQJH$XWRPDWLFDOO\FDWHJRUL]HWKH'87DVD3$66RU)$,/
VHQVLWLYLW\FRQÀJXULQJWKHWHVWVHWXSDQG 2SWLFDO2YHUORDG0DNHVHQVLWLYLW\PHDVXUHPHQWVZKLOHVWHSSLQJ
PDLQWDLQLQJWHVWVHWFDOLEUDWLRQ WKURXJKDUDQJHRIKLJKRSWLFDOSRZHUV$XWRPDWLFDOO\SORWDQGFDOFXODWH
w 6HQVLWLYLW\:KHQXVLQJDUHIHUHQFHUHFHLYHU WKHRSWLFDOLQSXWSRZHUDWZKLFKWKH'87·VUHFHLYHURYHUORDGVDQG
LWLVGHVLUDEOHWRKDYHDOOWUDQVPLWWHUVWHVWHG JHQHUDWHVHUURUV
WRWKHVDPH%(5OHYHOVRGLIIHUHQFHVEHWZHHQ 'HEXJ7HVWLQJ'LDJQRVHSURGXFWIDLOXUHVZLWKWKH267E\
WUDQVPLWWHUVDUHLPPHGLDWHO\DSSDUHQWEXW DXWRPDWLFDOO\PDNLQJSURJUHVVLYHO\PRUHGLIÀFXOWPHDVXUHPHQWVIURPD
LQWHUSRODWLQJEHWZHHQDQGH[WUDSRODWLQJEH\RQG SUHSURJUDPPHGOLVWRIWHVWV,QGHEXJPRGHWKH267FRQWUROVD'&$
WHVWSRLQWVUHTXLUHVVSHFLDOL]HGVWDWLVWLFDO ZDYHPHWHUDQGDQRSWLFDOVZLWFKWRJHQHUDWHWHVWGDWDWKDWZRXOGWDNH
NQRZOHGJH KRXUVWRFROOHFWPDQXDOO\
w &
RQÀJXUDWLRQ6HWWLQJXSDFRPSOH[WHVW 6;3HQDOW\3HUIRUPWZRVHQVLWLYLW\PHDVXUHPHQWVZLWKDQGZLWKRXW
VHWXVLQJQXPHURXVLQVWUXPHQWVDQGSDVVLYH DQDGGHGLQWHUIHULQJVLJQDO$XWRPDWLFDOO\SORWHDFKVHQVLWLYLW\WHVWDQG
FRPSRQHQWVLVWLPHFRQVXPLQJDQGH[SHQVLYH FDOFXODWHWKHDGGLWLRQDORSWLFDOSRZHUUHTXLUHGE\WKH'87·VUHFHLYHUWR
w &DOLEUDWLRQ7LPHFRQVXPLQJDQGSDLQVWDNLQJ
FDOLEUDWLRQURXWLQHVPXVWEHFRQGXFWHGRQD 6HFXUHG$FFXUDF\&DOLEUDWLRQ7HVWZLWKRXWZRUU\LQJDERXW
UHJXODUEDVLV WKH267GULIWLQJRXWRIFDOLEUDWLRQEHFDXVHHDFK267LVDVHOIFRQWDLQHG
LQFDOLEUDWLRQ
310
Transmitter Functional Testing
6HQVLWLYLW\5XQQLQJVRSKLVWLFDWHGDOJRULWKPVWKH267
DXWRPDWLFDOO\GHWHUPLQHVUHFHLYHUVHQVLWLYLW\XVLQJWKH
WUDQVPLWWHUXQGHUWHVWDVDVLJQDOVRXUFH
&RQÀJXUDWLRQ$OOWKHLQVWUXPHQWVDQGFRPSRQHQWVQHHGHG
WRPDNHWUDQVPLWWHUIXQFWLRQDOWHVWVDUHFRQVROLGDWHG
LQWRDVLQJOH2SWLFDO6WDQGDUGV7HVWHU2677KH267KDV
DQ´,QWHUQDO6HQVLWLYLW\µWHVWSURJUDPWKDWDXWRPDWLFDOO\
PHDVXUHVUHFHLYHUVHQVLWLYLW\ZKLOHDWUDQVPLWWHU'87
LVFRQQHFWHG0XOWLSOHSURWRFROVFDQEHJHQHUDWHGE\
WKH267
:LWKDQLQWHUQDOORRSEDFNEHWZHHQWKH267·VWUDQVPLWWHU
DQGUHFHLYHUWKH´,QWHUQDO6HQVLWLYLW\µDSSOLFDWLRQEHFRPHV
DVHOIWHVWWKDWFRQÀUPVWKH267LVLQFDOLEUDWLRQ
6HQVLWLYLW\'DWDSRLQWVSORWWHGRQDORJORJVFDOHZHUHÀWWHG $QDO\VLV7UDQVPLWWHUIXQFWLRQDOWHVWVDUHPXFKHDVLHU
ZLWKGLIÀFXOWWRDFFXUDWHO\SURGXFHFXUYHGOLQHVDQGOHGWRÁDZHG ZLWKDQ2670DQ\WUDQVPLWWHUÁDZVDUHGLVFRYHUHGGXULQJ
UHFHLYHUVHQVLWLYLW\FDOFXODWLRQV WKLVWHVW+RZHYHUIRUDSSOLFDWLRQVWKDWHPSOR\ORQJ
OHQJWKVRIÀEHUEHWZHHQDUHFHLYHUDQGWUDQVPLWWHUSDWK
&RQÀJXUDWLRQ1XPHURXVLQVWUXPHQWVDQGFRPSRQHQWVKDG SHQDOW\WHVWLQJVKRXOGDOVREHFRQVLGHUHG
WREHFRQÀJXUHGWRSHUIRUPWUDQVPLWWHUIXQFWLRQDOWHVWLQJ,I
35%6SDWWHUQVIURPD%(57ZHUHLQDGHTXDWHVSHFLDOSURWRFRO
JHQHUDWRUVDQGDQDO\]HUVKDGWREHXVHGVXFKDV*(:$1*(
/$1RU271DQGWKHVHFRPSOLFDWHGWKHWHVWVHWXSHYHQPRUH
&DOLEUDWLRQ0DLQWDLQLQJFDOLEUDWLRQRIWKHWHVWVLJQDOUHTXLUHG
DVLJQLÀFDQWDPRXQWRIHQJLQHHULQJGHGLFDWLRQGXHWRWKHODUJH
QXPEHURILQGLYLGXDOLQVWUXPHQWVLQWKHWHVWVHWDQGWKHQXPEHU
RILQWHUFRQQHFWLRQFDEOHVXVHG
$QDO\VLV3UREOHPVDVVRFLDWHGZLWKVHWWLQJXSDQGPDNLQJ
DFFXUDWHUHFHLYHUVHQVLWLYLW\PHDVXUHPHQWVOHGWRVLPSO\WHVWLQJ
WUDQVPLWWHUVIRUHUURUIUHHSHUIRUPDQFHDWUHODWLYHO\KLJKSRZHU
OHYHOVIRUDJLYHQDPRXQWRIWLPH7KLVDOORZHGWUDQVPLWWHUV
ZLWKGHIHFWVVXFKDVVORZHGULVHRUIDOOWLPHVRUH[FHVVLYHMLWWHU
WRSDVVIXQFWLRQDOWHVWLQJ
,PSHULDO:D\6XLWH&
$OOHQWRZQ3$
7HO 7ROO)UHH
$OO5LJKWV5HVHUYHG
311
Application Briefs
16.10 IntelliScriptTM Testing
,QWHOOL6FULSW 70
FRQVROLGDWHVOD\HURQHWZRDQGWKUHHLQVWUXPHQWVDQG
7KH267,QWHOOL6FULSWWHVWPRGHDOORZV 6WUHVVHG5HFHLYHU&RQIRUPDQFH*HQHUDWHDFDOLEUDWHG,(((
VHTXHQFLQJWKURXJKVWDQGDUG267WHVWV DHGHJUDGHGVLJQDOMLWWHUÀOWHULQWHUIHULQJVLJQDOH[WLQFWLRQUDWLR
DQGFRQWUROVH[WHUQDOLQVWUXPHQWVVXFKDV DQGFDOFXODWHWKH'87·VUHFHLYHUVHQVLWLYLW\
HQYLURQPHQWDOFKDPEHUVSRZHUVXSSOLHV %(5YV26156WHSWKURXJKDUDQJHRIFDOLEUDWHG2SWLFDO6LJQDOWR
26$VRSWLFDOVZLWFKHVRVFLOORVFRSHVDQG SORWDQGFDOFXODWHWKH'87·VUHFHLYHU%(5YV2615VHQVLWLYLW\
ZDYHOHQJWKPHWHUV 2SWLFDO3DWK3HQDOW\3HUIRUPWZRVHQVLWLYLW\PHDVXUHPHQWVZLWK
,VVXHV 3UREOHPV 7UDQVPLWWHU2SWLFDO2XWSXW3RZHU&RPSDUHWKHWRWDORSWLFDO
7KHSULQFLSDOSUREOHPIDFLQJ5 'HQJLQHHUVLV RXWSXWSRZHUHPLWWHGE\WKH'87·VWUDQVPLWWHUWRWKHGHÀQHGPLQLPXP
YHULI\LQJWKDWDGHVLJQLVUHDG\WREHWUDQVIHUUHGWR DQGPD[LPXPUDQJH$XWRPDWLFDOO\FDWHJRUL]HWKH'87DVD3$66RU)$,/
PDQXIDFWXULQJ0DQXIDFWXULQJWHVWHQJLQHHUVPXVW 2SWLFDO2YHUORDG0DNHVHQVLWLYLW\PHDVXUHPHQWVZKLOHVWHSSLQJ
WKHQGHYHORSDQGSURJUDPIXOO\DXWRPDWHGWHVW WKURXJKDUDQJHRIKLJKRSWLFDOSRZHUV$XWRPDWLFDOO\SORWDQGFDOFXODWH
VHWV WKHRSWLFDOLQSXWSRZHUDWZKLFKWKH'87·VUHFHLYHURYHUORDGVDQG
w 'HVLJQ9HULÀFDWLRQ1HZSURGXFWGHVLJQVDUH JHQHUDWHVHUURUV
UDUHO\UHDG\IRUPDQXIDFWXULQJDQGWKHUH 'HEXJ7HVWLQJ'LDJQRVHSURGXFWIDLOXUHVZLWKWKH267E\
LVDOZD\VFRQFHUQLQ5 'ZKHQDQHZGHVLJQLV DXWRPDWLFDOO\PDNLQJSURJUHVVLYHO\PRUHGLIÀFXOWPHDVXUHPHQWVIURPD
WUDQVIHUUHGWRSURGXFWLRQ'HVLJQFKDQJHVPDGH SUHSURJUDPPHGOLVWRIWHVWV,QGHEXJPRGHWKH267FRQWUROVD'&$
FORVHWRWKH5 '0DQXIDFWXULQJKDQGRIILQFUHDVH ZDYHPHWHUDQGDQRSWLFDOVZLWFKWRJHQHUDWHWHVWGDWDWKDWZRXOGWDNH
WKHSUREDELOLW\RIPDQXIDFWXULQJSUREOHPV KRXUVWRFROOHFWPDQXDOO\
EHFDXVHSURGXFWTXDOLW\SUHGLFWLRQVLQFOXGHPRUH
DVVXPSWLRQVGXHWRWKHODFNRIDFRPSOHWHVXLWH 6;3HQDOW\3HUIRUPWZRVHQVLWLYLW\PHDVXUHPHQWVZLWKDQGZLWKRXW
DQDGGHGLQWHUIHULQJVLJQDO$XWRPDWLFDOO\SORWHDFKVHQVLWLYLW\WHVWDQG
RIWHVWGDWD
w 3URJUDPPLQJ2UFKHVWUDWLQJDFRPSOH[WHVW UHDFKDVHOHFWHG%(5OHYHOZLWKDQDSSOLHGLQWHUIHULQJVLJQDO
VHWWRDXWRPDWLFDOO\WHVWD'87UHTXLUHVD 6HFXUHG$FFXUDF\&DOLEUDWLRQ7HVWZLWKRXWZRUU\LQJDERXW
ODUJHDPRXQWRIWLPHFRQVXPLQJSURJUDPPLQJ WKH267GULIWLQJRXWRIFDOLEUDWLRQEHFDXVHHDFK267LVDVHOIFRQWDLQHG
([SDQGLQJPDQXIDFWXULQJFDSDFLW\RURXWVRXUFLQJ PHDVXUHPHQWV\VWHP6HOIFKHFNLQWHUQDOSURFHVVFRQWUROFKDUWVEHJLQ
WRFRQWUDFWPDQXIDFWXUHUVDOVRUHTXLUHV ZKLOHWKH267LVVWLOODWWKH&LUFDGLDQWIDFWRU\WRDVVXUHWKH267LVDOZD\V
VLJQLÀFDQWDPRXQWVRIQHZSURJUDPPLQJ2IWHQ LQFDOLEUDWLRQ
WKHRULJLQDOPDQXIDFWXULQJWHVWVHWFDQQRWVLPSO\
EHUHSOLFDWHGVRPHRIWKHLQVWUXPHQWVDQG 6WUDLJKW/LQH%(53ORWVHQVLWLYLW\WHVWVRSWLFDOSRZHU20$
FRPSRQHQWVXVHGRQWKHRULJLQDOWHVWVHWDUHQR
ORQJHUDYDLODEOHOHWDORQHGHVLUDEOH
312
IntelliScriptTM Testing
'HVLJQ9HULÀFDWLRQ7UDIÀFVHWXSVDQGWHVWFRQÀJXUDWLRQV
DUHVDYHGVHSDUDWHO\LQWKH267SURYLGLQJ5 'HQJLQHHUV
ZLWKJUHDWWHVWÁH[LELOLW\([WHUQDOLQVWUXPHQWVDUH
DOVRFRQWUROODEOHE\WKH2677KHYDULRXVWHVWVDUH
'HVLJQ9HULÀFDWLRQ3UHVVXUHZDVDOZD\VRQ5 'WRPHHWQHZ RUGHUHGWKURXJKWKH,QWHOOL6FULSWVHWXSPHQXVWRUXQ
SURGXFWGHYHORSPHQWVFKHGXOHVEXWXQH[SHFWHGSUREOHPVGXULQJ DXWRPDWLFDOO\RQHWHVWDIWHUDQRWKHUGD\DQGQLJKWZLWK
GHYHORSPHQWLQHYLWDEO\VTXHH]HGWKHWLPHDYDLODEOHIRUIXOO RSWLRQDO(PDLOQRWLÀFDWLRQRQIDLOXUH5HSHDWLQJWKHVDPH
GHVLJQYHULÀFDWLRQWHVWLQJ:LWKRXWDXWRPDWLRQWKHUHZDVQR EDWWHU\RIWHVWVRQDOOSURGXFWLWHUDWLRQVPDNHVIRUVWDEOH
WLPHWRFRQGXFWDOOWKHWHVWV5 'UHDOO\ZDQWHGWRGRWRDVVXUH QHZSURGXFWGHVLJQV)RUH[DPSOHDVD*3,%0DVWHUWKH
WKHQHZSURGXFWGHVLJQZDVUHDG\6FKHGXOHVHLWKHUVOLSSHGRULW 267FRQWUROVHQYLURQPHQWDOFKDPEHUVSRZHUVXSSOLHVDQG
ZDVGHFLGHGWRDFFHSWWKHLQFUHDVHGULVNRIKDYLQJPDQXIDFWXULQJ '&$VHQDEOLQJFRUQHUVWHVWLQJRIUHFHLYHUVHQVLWLYLW\SDWK
SUREOHPV SHQDOW\DQGH\HPDVNZLWK*LJ(/$1*LJ(:$1
621(76'+DQG35%6WUDIÀF
3URJUDPPLQJ7KHUHZDVDQDUURZZLQGRZRIWLPHEHWZHHQ
5 'GHFODULQJDGHVLJQÀQLVKHGDQGPDQXIDFWXULQJEHJLQQLQJ 3URJUDPPLQJ%\XVLQJDQ267WKHPRVWGLIÀFXOWFRGH
SURGXFWLRQ0DQXIDFWXULQJWHVWVHWFRQVWUXFWLRQZDVRQWKH LVDOUHDG\ZULWWHQ6WDQGDUGWHVWVDUHSUHSURJUDPPHG
FULWLFDOSDWKEHFDXVHWKRXVDQGVRIOLQHVRISURJUDPPLQJFRGH HOLPLQDWLQJWKHKXJHWDVNRIZULWLQJFRGHWRFRQWURO
ZHUHQHHGHGWRRSHUDWHWKHYDULRXVWHVWLQVWUXPHQWVDQG LQGLYLGXDODWWHQXDWRUVVZLWFKHVSRZHUPHWHUVHWF7KH
VXIÀFLHQWWLPHZDVQHHGHGWRGHEXJWKHFRGHRQDFFRXQWRI ,QWHOOL6FULSWWHVWLQJIHDWXUHLVVLPSOHWRVHWXSHQDEOLQJ
SURGXFWDQGWHVWVHWLGLRV\QFUDVLHV ORQJFKDLQVRIWHVWVWREHTXLFNO\SURJUDPPHGIRUGLIIHUHQW
W\SHVRI'87V
$QDO\VLV&XVWRPHUDQGFRPSHWLWRUGULYHQQHZSURGXFW
GHYHORSPHQWVFKHGXOHVSXWJUHDWSUHVVXUHRQ5 'DQG $QDO\VLV8VLQJWKH267,QWHOOL6FULSWWHVWLQJIHDWXUHV
PDQXIDFWXULQJ3URGXFWWHVWLQJDEVRUEHGWRRPXFKDYDLODEOH 5 'DQGPDQXIDFWXULQJFDQUHGXFHQHZSURGXFW
WLPH²5 'WHVWLQJZDVGRQHPDQXDOO\DQGPDQXIDFWXULQJWHVW LQWURGXFWLRQWLPHVLPSURYHSURGXFWGHVLJQVDQGHQKDQFH
VHWVWRRNWRRORQJWRDVVHPEOHSURJUDPDQGGHEXJ PDQXIDFWXUDELOLW\7HVWLQJFRUUHODWLRQEHWZHHQ5 'DQG
ZRUOGZLGHPXOWLIDFLOLW\PDQXIDFWXULQJORFDWLRQVLV
VLJQLÀFDQWO\HQKDQFHG
,PSHULDO:D\6XLWH&
$OOHQWRZQ3$
7HO 7ROO)UHH
$OO5LJKWV5HVHUYHG
313
Application Briefs
16.11 IntelliTimeTM Testing
,QWHOOL7LPH 70
7KH267,QWHOOL7LPHWHVWPRGHRSWLPL]HV 6WUHVVHG5HFHLYHU&RQIRUPDQFH7HVW*HQHUDWHDFDOLEUDWHG
VWDQGDUGWHVWVWRUXQZLWKWKHORZHVW ,(((DHGHJUDGHGVLJQDOMLWWHUÀOWHULQWHUIHULQJVLJQDOH[WLQFWLRQ
SRVVLEOHPHDVXUHPHQWXQFHUWDLQW\IRU UDWLRZKLOHYDU\LQJWKH2SWLFDO0RGXODWLRQ$PSOLWXGH20$
DQ\VHOHFWHGSHULRGRIWLPH,QWHOOL7LPH
%(5YV26156WHSWKURXJKDUDQJHRIFDOLEUDWHG2SWLFDO6LJQDOWR
PRGHDXWRPDWLFDOO\WHVWV'87VRYHU 1RLVH5DWLRVZKLOHPDLQWDLQLQJDFRQVWDQWRSWLFDOSRZHU$XWRPDWLFDOO\
PXOWLSOHSRZHUOHYHOVDQGLVXVHGIRUSDWK SORWDQGFDOFXODWHWKH'87·VUHFHLYHU%(5YV2615VHQVLWLYLW\
SHQDOW\WHVWLQJWUDQVPLWWHUIXQFWLRQDO 2SWLFDO3DWK3HQDOW\3HUIRUPWZRVHQVLWLYLW\PHDVXUHPHQWVZLWK
WHVWLQJVHQVLWLYLW\WHVWLQJ6;SHQDOW\ DQGZLWKRXWWKH'87·VWUDQVPLWWHUVLJQDOSDVVLQJWKURXJKDVSRROVRI
WHVWLQJRYHUORDGWHVWLQJDQG%(5YV2615
WHVWLQJ
2SWLFDO3RZHU&RPSDUHWKHWRWDORSWLFDORXWSXWSRZHUHPLWWHGE\
WKH'87·VWUDQVPLWWHUWRWKHGHÀQHGPLQLPXPDQGPD[LPXPUDQJH
$XWRPDWLFDOO\FDWHJRUL]HWKH'87DVD3$66RU)$,/
,VVXHV 3UREOHPV 2SWLFDO2YHUORDG0DNHVHQVLWLYLW\PHDVXUHPHQWVZKLOHVWHSSLQJ
6RPHRIWKHSUREOHPVIDFLQJ5 'HQJLQHHUVDUH WKURXJKDUDQJHRIKLJKRSWLFDOSRZHUV$XWRPDWLFDOO\SORWDQGFDOFXODWH
GHFLGLQJKRZORQJHDFKGDWDSRLQWPXVWEHWHVWHG WKHRSWLFDOLQSXWSRZHUDWZKLFKWKH'87·VUHFHLYHURYHUORDGVDQG
LQRUGHUWRJHQHUDWHYDOLGVWDWLVWLFVVHOHFWLQJWKH JHQHUDWHVHUURUV
ULJKWGDWDSRLQWVWRWHVWDQGWKHQLQWHUSUHWLQJWKH
WHVWUHVXOWV 'HEXJ7HVWLQJ'LDJQRVHSURGXFWIDLOXUHVZLWKWKH267E\
w 7HVW7LPH/RQJWHVWWLPHVLQFUHDVHWKH SUHSURJUDPPHGOLVWRIWHVWV,QGHEXJPRGHWKH267FRQWUROVD'&$
VWDWLVWLFDOFRQÀGHQFHOHYHOLQWKH%(5WHVW ZDYHPHWHUDQGDQRSWLFDOVZLWFKWRJHQHUDWHWHVWGDWDWKDWZRXOGWDNH
UHVXOWVEXWVKRUWWHVWWLPHVPD\SURGXFH KRXUVWRFROOHFWPDQXDOO\
VWDWLVWLFDOO\PHDQLQJOHVVUHVXOWV5 'HQJLQHHUV
VHWXSWHVWWLPHVZLWKOLWWOHFRQVLGHUDWLRQJLYHQ 6;3HQDOW\3HUIRUPWZRVHQVLWLYLW\PHDVXUHPHQWVZLWKDQGZLWKRXW
WRWKHVWDWLVWLFDOXQFHUWDLQW\RIWKHLUWHVWSODQ DQDGGHGLQWHUIHULQJVLJQDO$XWRPDWLFDOO\SORWHDFKVHQVLWLYLW\WHVWDQG
VSHQGLQJWRRPXFKWLPHWHVWLQJDWVRPHSRZHU FDOFXODWHWKHDGGLWLRQDORSWLFDOSRZHUUHTXLUHGE\WKH'87·VUHFHLYHUWR
OHYHOVDQGQRWHQRXJKWLPHDWRWKHUV UHDFKDVHOHFWHG%(5OHYHOZLWKDQDSSOLHGLQWHUIHULQJVLJQDO
w 'DWD3RLQW6HOHFWLRQ7HVWLQJDWUHODWLYHO\KLJK 6HFXUHG$FFXUDF\&DOLEUDWLRQ7HVWZLWKRXWZRUU\LQJDERXW
SRZHUVFRUUHVSRQGVWRYHU\ORZ%(5OHYHOVEXW WKH267GULIWLQJRXWRIFDOLEUDWLRQEHFDXVHHDFK267LVDVHOIFRQWDLQHG
DJUHDWGHDORIWHVWWLPHLVUHTXLUHGIRUHQRXJK PHDVXUHPHQWV\VWHP6HOIFKHFNLQWHUQDOSURFHVVFRQWUROFKDUWVEHJLQ
HUURUVWREHFRXQWHGWRYHULI\WKHH[FHOOHQW%(5 ZKLOHWKH267LVVWLOODWWKH&LUFDGLDQWIDFWRU\WRDVVXUHWKH267LVDOZD\V
OHYHODVVRFLDWHGZLWKWKDWLQSXWSRZHU/RFDWLQJ LQFDOLEUDWLRQ
WKHFRUUHFWRSWLFDOSRZHUUDQJHWRWHVWRYHULV
WLPHFRQVXPLQJ 6WUDLJKW/LQH%(53ORWVHQVLWLYLW\WHVWVRSWLFDOSRZHU20$
w ,QWHUSUHWLQJ5HVXOWV5 'HQJLQHHUVPXVW RU2615YV%(5RQWKHSURSHUVFDOHVXFKWKDWWKHGDWDZLOOIDOORQD
GHWHUPLQHLIWKHLUUHVXOWVDUHJRRGRUEDG VWUDLJKWOLQHIRUDZHOOEHKDYHGGHYLFH8QH[SHFWHGEHKDYLRULVUHYHDOHG
7KHXQFHUWDLQW\RIWKHGDWDSRLQWVPXVWEH LPPHGLDWHO\DQGFRQFOXVLYHO\WRWKHXVHU
FRQVLGHUHGHVSHFLDOO\LIWKH'87·VSHUIRUPDQFH ,QWHOOL6FULSW7HVWLQJ6HTXHQFHWKURXJKVWDQGDUGEXLOWLQWHVWVDQG
LVFORVHWRD)$,/OHYHO5 'HQJLQHHUVKDYH FRQWUROH[WHUQDOLQVWUXPHQWVVXFKDVHQYLURQPHQWDOFKDPEHUVSRZHU
GLIÀFXOW\FRPSDULQJWKHUHVXOWVWRSUHYLRXVWHVWV VXSSOLHV26$VRSWLFDOVZLWFKHVRVFLOORVFRSHVDQGZDYHOHQJWKPHWHUV
314
IntelliTimeTM Testing
7HVW7LPH7KH267·V,QWHOOL7LPHWHVWPRGHDOORZV5 '
HQJLQHHUVWRVLPSO\VSHFLI\WKHWLPHWKH\ZDQWWRUXQ
WKHWHVWIRUDQGRQO\VWDWLVWLFDOO\YDOLGWHVWUHVXOWVDUH
JHQHUDWHG+LJK%(5UHVXOWVDUHTXLFNO\JHQHUDWHGE\WKH
7HVW7LPH,QD*EVV\VWHPDQDYHUDJHRIRQHHUURUHYHU\ 267EHIRUHSURJUHVVLQJRQWRORZHUDQGORZHU%(5OHYHOV
VHFRQGVFRUUHVSRQGVWRD%(5OHYHO&RQVLGHULQJDOVRWKH 7LPHLVQRWZDVWHGWDNLQJWRRPXFKGDWDDWKLJK%(5OHYHOV
UDQGRPGLVWULEXWLRQRIHUURUVLWLVFOHDUWKDWWHVWLQJWRD%(5 QRULVWLPHVSHQWFROOHFWLQJGDWDDWOHYHOVZKHQWKHUHLVQRW
OHYHORUORZHUUHTXLUHGOHQJWK\WHVWWLPHVWRREWDLQVWDWLVWLFDOO\ HQRXJKWLPHWRFROOHFWHQRXJKGDWDWREHPHDQLQJIXO
YDOLGUHVXOWV1HYHUWKHOHVV%(5OHYHOVREWDLQHGIURPVKRUWWHVW
WLPHVZHUHUHJXODUO\UHSRUWHGZLWKRXWFKDUDFWHUL]LQJWKHODUJH 'DWD3RLQW6HOHFWLRQ7KH267UDSLGO\ORFDWHVWKHSRZHU
SRVVLEOHYDULDWLRQLQWKHUHVXOWVWKDWPLJKWRFFXULIWKHWHVWZHUH OHYHOVWKDWQHHGWREHWHVWHG
UHSHDWHG
,QWHUSUHWLQJ5HVXOWV5HVXOWVDUHDXWRPDWLFDOO\GLVSOD\HG
'DWD3RLQW6HOHFWLRQ7KHYDULDWLRQLQ'87SHUIRUPDQFH RQWKH267·V6WUDLJKW/LQH%(5SORWVRXQH[SHFWHGUHVXOWV
SUHFOXGHGPDNLQJDOO%(5PHDVXUHPHQWVDWWKHVDPHSRZHU DUHLPPHGLDWHO\DSSDUHQW6WDWLVWLFDODQDO\VLVLVLQFOXGHG
OHYHOVDQGPHDQW5 'HQJLQHHUVKDGWRDGMXVWDWWHQXDWRUVORRN DOORZLQJD'87WREHFKDUDFWHUL]HGIRUH[DPSOHDVKDYLQJ
DWSRZHUPHWHUVDQGWKHQORRNDWWKHGLVSOD\HG%(5OHYHOVRQWKH DVHQVLWLYLW\RI%(5DWG%PG%
WHVWHTXLSPHQWWRNQRZLIWKHGDWDSRLQWZDVLQWKHDFFHSWDEOH
UDQJH7KLVKLJKO\LWHUDWLYHDQGPDQXDOWHVWSURFHGXUHZDVWHG $QDO\VLV7KH267,QWHOOL7LPHWHVWPRGHVLJQLÀFDQWO\
VLJQLÀFDQWDPRXQWVRIWLPH LPSURYHV5 'SURGXFWLYLW\6KRUWWHVWWLPHV\LHOG
VWDWLVWLFDOO\YDOLGUHVXOWVWKDWDOORZGHVLJQFKDQJHV
,QWHUSUHWLQJ5HVXOWV7DEOHVRIRSWLFDOSRZHUYV%(5ZHUH WREHFKDUDFWHUL]HGDVIDYRUDEOHRUXQIDYRUDEOHZLWK
WUDQVODWHGWRJUDSKVVRD%(5FXUYHFRXOGEHREVHUYHGDQGWKH FRQÀGHQFH/RQJWHVWWLPHVDOORZGHVLJQVWREHWHVWHG
VHQVLWLYLW\FDOFXODWHGIURPWKHLQWHUVHFWLRQRIWKH%(5OHYHOZLWK WRORZ%(5OHYHOV$XWRPDWLFGDWDSRLQWVHOHFWLRQVSHHGV
WKHFXUYH7\SLFDOO\WKLVZDVGRQHXVLQJDORJORJVFDOH%XW WHVWLQJUHVXOWLQJLQEHWWHUFKDUDFWHUL]HGGHVLJQVDQG
PDQXDOO\FROOHFWHGGDWDDQGPDQXDOO\GUDZQSORWVZHUHSURQH IHZHUPDQXIDFWXULQJSUREOHPV6RSKLVWLFDWHGVWDWLVWLFDO
WRKXPDQHUURUDQGWKHFXUYHGGDWDSRLQWVW\SLFDORIORJORJ DOJRULWKPVDQGFRPSXWDWLRQVHOLPLQDWHWKHQHHGIRU5 '
VFDOHVDOORZHGHUURUÁRRUVWRJRXQGLDJQRVHG)XUWKHUPRUH
WKHVWDWLVWLFDOXQFHUWDLQW\RIRQHVHWRIPHDVXUHPHQWVZDVQRW HQJLQHHUVWRJXHVVDWWHVWSRLQWVDQG%(5OHYHOV
FRQVLGHUHGZKHQFRPSDUHGDJDLQVWSUHYLRXVWHVWUHVXOWVDQGOHG
WRIDOVHFRQFOXVLRQV
$QDO\VLV5 'HQJLQHHUVVSHQWDODUJHSDUWRIWKHLUGD\WHVWLQJ
SURWRW\SHVLQVWHDGRIZRUNLQJRQQHZGHVLJQV6ORZSDLQIXO
WHVWLQJLQHYLWDEO\OHGWRQRWHQRXJKWHVWLQJDQGFRPELQHGZLWK
DODFNRIDWWHQWLRQWR%(5VWDWLVWLFVWKHFKDQFHVRIGHVLJQ
ÁDZVJRLQJXQGHWHFWHGLQFUHDVHGFUHDWLQJVFKHGXOHGHOD\VDQG
PDQXIDFWXULQJSUREOHPV
,PSHULDO:D\6XLWH&
$OOHQWRZQ3$
7HO 7ROO)UHH
$OO5LJKWV5HVHUYHG
315
Application Briefs
16.12 IntelliPassTM Testing
,QWHOOL3DVV 70
7KH267,QWHOOL3DVVWHVWPRGHPLQLPL]HV 6WUHVVHG5HFHLYHU&RQIRUPDQFH*HQHUDWHDFDOLEUDWHG,(((
WKHWLPHGXULQJSURGXFWLRQWHVWLQJE\ DHGHJUDGHGVLJQDOMLWWHUÀOWHULQWHUIHULQJVLJQDOH[WLQFWLRQUDWLR
LQWHOOLJHQWO\FDOFXODWLQJWKHDPRXQWRI DQGFDOFXODWHWKH'87·VUHFHLYHUVHQVLWLYLW\
WLPHWRVSHQGRQD'87$WHVWLVUXQRQO\ %(5YV26156WHSWKURXJKDUDQJHRIFDOLEUDWHG2SWLFDO6LJQDOWR
XQWLOD3$66)$,/YDOXHLVUHDFKHGRUWKH SORWDQGFDOFXODWHWKH'87·VUHFHLYHU%(5YV2615VHQVLWLYLW\
PD[LPXPWLPHWRVSHQGWHVWLQJWKH'87 2SWLFDO3DWK3HQDOW\3HUIRUPWZRVHQVLWLYLW\PHDVXUHPHQWVZLWK
LVUHDFKHG,QWHOOL3DVVPRGHLVXVHG ÀEHU$XWRPDWLFDOO\SORWHDFKVHQVLWLYLW\WHVWDQGFDOFXODWHWKHRSWLFDO
LQWUDQVPLWWHUIXQFWLRQDOWHVWLQJSDWK SRZHUGLIIHUHQFHEHWZHHQWKHPDWDVHOHFWHG%(5OHYHO
SHQDOW\WHVWLQJVHQVLWLYLW\WHVWLQJ6; 7UDQVPLWWHU2SWLFDO2XWSXW3RZHU&RPSDUHWKHWRWDORSWLFDO
SHQDOW\WHVWLQJRYHUORDGWHVWLQJDQG%(5 DQGPD[LPXPUDQJH$XWRPDWLFDOO\FDWHJRUL]HWKH'87DVD3$66RU)$,/
YV2615WHVWLQJ 2SWLFDO2YHUORDG0DNHVHQVLWLYLW\PHDVXUHPHQWVZKLOHVWHSSLQJ
WKHRSWLFDOLQSXWSRZHUDWZKLFKWKH'87·VUHFHLYHURYHUORDGVDQG
JHQHUDWHVHUURUV
,VVXHV 3UREOHPV 'HEXJ7HVWLQJ'LDJQRVHSURGXFWIDLOXUHVZLWKWKH267E\
7KHSULQFLSDOSUREOHPVIDFLQJPDQXIDFWXULQJWHVW DXWRPDWLFDOO\PDNLQJSURJUHVVLYHO\PRUHGLIÀFXOWPHDVXUHPHQWVIURPD
HQJLQHHUVDUHRSWLPL]LQJWKHWHVWLQJWLPHRID'87 SUHSURJUDPPHGOLVWRIWHVWV,QGHEXJPRGHWKH267FRQWUROVD'&$
VFUHHQLQJIRUHUURUÁRRUVDQGREWDLQLQJIDOVH3$66 ZDYHPHWHUDQGDQRSWLFDOVZLWFKWRJHQHUDWHWHVWGDWDWKDWZRXOGWDNH
RUIDOVH)$,/UHVXOWVIURPD'87 KRXUVWRFROOHFWPDQXDOO\
w 7LPH2SWLPL]DWLRQ6SHFLDOL]HGVWDWLVWLFDO 6;3HQDOW\3HUIRUPWZRVHQVLWLYLW\PHDVXUHPHQWVZLWKDQGZLWKRXW
NQRZOHGJHLVQHHGHGWRGHWHUPLQHDGHTXDWH'87 DQDGGHGLQWHUIHULQJVLJQDO$XWRPDWLFDOO\SORWHDFKVHQVLWLYLW\WHVWDQG
WHVWWLPHVZKLFKDUHORQJHQRXJKWRREWDLQYDOLG FDOFXODWHWKHDGGLWLRQDORSWLFDOSRZHUUHTXLUHGE\WKH'87·VUHFHLYHUWR
UHVXOWV UHDFKDVHOHFWHG%(5OHYHOZLWKDQDSSOLHGLQWHUIHULQJVLJQDO
w (UURU)ORRU&UHDWLQJDWHVWIRUDQHUURUÁRRU 6HFXUHG$FFXUDF\&DOLEUDWLRQ7HVWZLWKRXWZRUU\LQJDERXW
WKH267GULIWLQJRXWRIFDOLEUDWLRQEHFDXVHHDFK267LVDVHOIFRQWDLQHG
DGGHGSRZHUGRHVQRWLPSURYHWKH%(5OHYHO
LVGLIÀFXOWWRLPSOHPHQWGXHWRWKHQHHGWR
FRUUHFWO\H[WUDSRODWH'87RSWLFDOVHQVLWLYLWLHVWR
LQFDOLEUDWLRQ
KLJKHURSWLFDOSRZHUOHYHOV
w )DOVH5HVXOWV$GHHSXQGHUVWDQGLQJRI%(5 RU2615YV%(5RQWKHSURSHUVFDOHVXFKWKDWWKHGDWDZLOOIDOORQD
VWDWLVWLFVLVQHHGHGWRLPSOHPHQWPDQXIDFWXULQJ VWUDLJKWOLQHIRUDZHOOEHKDYHGGHYLFH8QH[SHFWHGEHKDYLRULVUHYHDOHG
WHVWVEHFDXVHRIWKHSUREDELOLW\RILQFRUUHFWO\ LPPHGLDWHO\DQGFRQFOXVLYHO\WRWKHXVHU
FDWHJRUL]LQJVRPH'87VDV3$66RU)$,/
316
IntelliPassTM Testing
7LPH2SWLPL]DWLRQ7HVWVZHUHUXQIRUWKHVDPHDPRXQWRI 7LPH2SWLPL]DWLRQ7KH267,QWHOOL3DVVWHVWLQJIHDWXUHV
WLPHRUXQWLODFHUWDLQDPRXQWRIHUURUVZHUHFRXQWHGDWHDFK UHGXFHWHVWWLPHVE\TXLFNO\SDVVLQJRUIDLOLQJ'87VEDVHG
RSWLFDOSRZHUWHVWSRLQW'87VZLWKHLWKHUH[FHSWLRQDOO\JRRG RQJRRGRUEDGSHUIRUPDQFHXVLQJVWDWLVWLFDOSUREDELOLWLHV
SHUIRUPDQFHRUFOHDUIDLOXUHVZHUHWHVWHGIRUWKHVDPHDPRXQWRI 7KLVLVDFFRPSOLVKHGE\ÀUVWPHDVXULQJWKH%(5RID'87
WLPHZKLFKZDVWHGYDOXDEOHWHVWVWDWLRQWLPH YHU\TXLFNO\DWUHODWLYHO\ORZSRZHUOHYHOVWRREWDLQDVHW
RIKLJK%(5GDWDSRLQWVWKDWDUHÀWWHGZLWKDOLQHWKDWLV
(UURU)ORRU'HWHUPLQLQJWKHGLIIHUHQWSRZHUOHYHORIIVHWVQHHGHG WKHQH[WUDSRODWHGWRWKH3$66)$,/%(5OHYHO'HSHQGLQJ
WRVFUHHQIRUDQHUURUÁRRUIRUHDFK'87WHVWHGUHTXLUHGLQWULFDWH RQWKHGHVLUHGFRQÀGHQFHOHYHOWKH'87LVWKHQWHVWHG
WHVWVHWSURJUDPPLQJZLWKFRPSOLFDWHGVWDWLVWLFDOIXQFWLRQV QHDUWKHSRZHUOHYHOWKDWLVSUHGLFWHGWRFRUUHVSRQGWR
WKH3$66)$,/%(5OHYHO7KLVGHWHUPLQHVLIWKH'87LVD
)DOVH5HVXOWV6WDWLVWLFVZHUHQRWXVHGWRVHWWHVWSDUDPHWHUVWKDW GHÀQLWH)$,/ZKLFKVWRSVWKHWHVWLQJRULVDSUREDEOH
ZRXOGJHQHUDWHDJUHHGXSRQIDOVH3$66DQGIDOVH)$,/OHYHOV 3$66DQGHVWDEOLVKHVZKDWDGGLWLRQDODXWRPDWHGWHVWLQJLV
UHTXLUHG
$QDO\VLV0DQXIDFWXULQJF\FOHWLPHVZHUHXQQHFHVVDULO\H[WHQGHG
E\WHVWLQJJRRGRUEDG'87VIRUWKHVDPHLQGLVFULPLQDWHDPRXQW (UURU)ORRU1RPLQDOO\SDVVHG'87VDUHDXWRPDWLFDOO\
RIWLPH4XDOLW\OHYHOVZHUHORZHUHGE\SDVVLQJ'87VWKDWVKRXOG VFUHHQHGIRUVHOHFWDEOH%(5HUURUÁRRUVEHIRUHDÀQDO3$66
KDYHIDLOHGDQG\LHOGVZHUHORZHUHGE\IDLOLQJ'87VWKDWFRXOG LVGLVSOD\HG
KDYHSDVVHG
)DOVH5HVXOWV8VHUVHVWDEOLVKWKHSUREDELOLW\RIIDOVHO\
IDLOLQJD'87WKHSUREDELOLW\RIIDOVHO\SDVVLQJD'87DQG
WKH267DGMXVWVWHVWWLPHVDFFRUGLQJO\
$QDO\VLV7KH267,QWHOOL3DVVWHVWLQJIHDWXUHVXVH
DGYDQFHGVWDWLVWLFDODOJRULWKPVWRRSWLPL]HWHVWWLPHV
UHGXFHPDQXIDFWXULQJF\FOHWLPHVDQGLPSURYHTXDOLW\
DQG\LHOGOHYHOV
,PSHULDO:D\6XLWH&
$OOHQWRZQ3$
7HO 7ROO)UHH
$OO5LJKWV5HVHUYHG
317
Application Briefs
16.13 Golden Transmitters
*ROGHQ FRQVROLGDWHVOD\HURQHWZRDQGWKUHHLQVWUXPHQWVDQG
7UDQVPLWWHUV V\VWHPVDQGDXWRPDWHVVWDQGDUGWUDQVPLWWHUDQGUHFHLYHUWHVWV
*ROGHQ7UDQVPLWWHUVSURYLGHFRQVLVWHQW 6WUHVVHG5HFHLYHU&RQIRUPDQFH*HQHUDWHDFDOLEUDWHG,(((
VLJQDOVWRWHVWUHFHLYHUVDQGDUHW\SLFDOO\ DHGHJUDGHGVLJQDOMLWWHUÀOWHULQWHUIHULQJVLJQDOH[WLQFWLRQUDWLR
RIWKHVDPHFODVVRIWUDQVPLWWHUVWKDWZLOO DQGFDOFXODWHWKH'87·VUHFHLYHUVHQVLWLYLW\
EHXVHGZLWKWKHUHFHLYHUVLQDV\VWHP %(5YV26156WHSWKURXJKDUDQJHRIFDOLEUDWHG2SWLFDO6LJQDOWR
*ROGHQ7UDQVPLWWHUVPXVWEHXVHGZKHQ SORWDQGFDOFXODWHWKH'87·VUHFHLYHU%(5YV2615VHQVLWLYLW\
SURSULHWDU\FRGLQJVFKHPHVDUHXVHG 2SWLFDO3DWK3HQDOW\3HUIRUPWZRVHQVLWLYLW\PHDVXUHPHQWVZLWK
WKDWDUHQRWDYDLODEOHLQVWDQGDUGWHVW ÀEHU$XWRPDWLFDOO\SORWHDFKVHQVLWLYLW\WHVWDQGFDOFXODWHWKHRSWLFDO
HTXLSPHQWLQFOXGLQJ6%6VXSSUHVVLRQ)(& SRZHUGLIIHUHQFHEHWZHHQWKHPDWDVHOHFWHG%(5OHYHO
DQGRXWRIEDQGVLJQDOLQJ 7UDQVPLWWHU2SWLFDO2XWSXW3RZHU&RPSDUHWKHWRWDORSWLFDO
2SWLFDO2YHUORDG0DNHVHQVLWLYLW\PHDVXUHPHQWVZKLOHVWHSSLQJ
,VVXHV 3UREOHPV WKURXJKDUDQJHRIKLJKRSWLFDOSRZHUV$XWRPDWLFDOO\SORWDQGFDOFXODWH
7KHSULQFLSDOSUREOHPVHQFRXQWHUHGZKHQXVLQJ WKHRSWLFDOLQSXWSRZHUDWZKLFKWKH'87·VUHFHLYHURYHUORDGVDQG
*ROGHQ7UDQVPLWWHUVDUHHQVXULQJWKHLUVLJQDO JHQHUDWHVHUURUV
TXDOLW\DQGREWDLQLQJLGHQWLFDOO\SHUIRUPLQJ*ROGHQ 'HEXJ7HVWLQJ'LDJQRVHSURGXFWIDLOXUHVZLWKWKH267E\
7UDQVPLWWHUVZKHQUHSOLFDWLQJSURGXFWLRQWHVWVHWV DXWRPDWLFDOO\PDNLQJSURJUHVVLYHO\PRUHGLIÀFXOWPHDVXUHPHQWVIURPD
w 6LJQDO4XDOLW\1RWHQRXJKDWWHQWLRQLVJLYHQWR SUHSURJUDPPHGOLVWRIWHVWV,QGHEXJPRGHWKH267FRQWUROVD'&$
VHOHFWLQJ*ROGHQ7UDQVPLWWHUV,QPDQ\FDVHV ZDYHPHWHUDQGDQRSWLFDOVZLWFKWRJHQHUDWHWHVWGDWDWKDWZRXOGWDNH
DPDQXIDFWXULQJHQJLQHHUVLPSO\DVNV5 'IRU KRXUVWRFROOHFWPDQXDOO\
DWUDQVPLWWHUWRXVHDQGWKDWGHYLFHVHOHFWHG 6;3HQDOW\3HUIRUPWZRVHQVLWLYLW\PHDVXUHPHQWVZLWKDQGZLWKRXW
DWUDQGRPEHFRPHVWKH*ROGHQ7UDQVPLWWHU DQDGGHGLQWHUIHULQJVLJQDO$XWRPDWLFDOO\SORWHDFKVHQVLWLYLW\WHVWDQG
7KRXJKWKLVPD\SURGXFHUHSHDWDEOH FDOFXODWHWKHDGGLWLRQDORSWLFDOSRZHUUHTXLUHGE\WKH'87·VUHFHLYHUWR
PHDVXUHPHQWVRQWKHSURGXFWLRQOLQHSURGXFW UHDFKDVHOHFWHG%(5OHYHOZLWKDQDSSOLHGLQWHUIHULQJVLJQDO
TXDOLW\LQWKHÀHOGLVQRWJXDUDQWHHG([WLQFWLRQ
5DWLR2SWLFDO6LJQDOWR1RLVH5DWLR2615 6HFXUHG$FFXUDF\&DOLEUDWLRQ7HVWZLWKRXWZRUU\LQJDERXW
FKLUSULVHDQGIDOOWLPHVDQGMLWWHUSHUIRUPDQFH WKH267GULIWLQJRXWRIFDOLEUDWLRQEHFDXVHHDFK267LVDVHOIFRQWDLQHG
RID*ROGHQ7UDQVPLWWHUPD\DOORZ'87UHFHLYHUV PHDVXUHPHQWV\VWHP6HOIFKHFNLQWHUQDOSURFHVVFRQWUROFKDUWVEHJLQ
WR3$66SURGXFWLRQWHVWLQJEXWWKHUHFHLYHUVPD\ ZKLOHWKH267LVVWLOODWWKH&LUFDGLDQWIDFWRU\WRDVVXUHWKH267LVDOZD\V
)$,/LQWKHÀHOGZKHQSDLUHGZLWKORZHUTXDOLW\ LQFDOLEUDWLRQ
WUDQVPLWWHUV
w 7HVW6HW5HSOLFDWLRQ,WLVGLIÀFXOWWRREWDLQ RU2615YV%(5RQWKHSURSHUVFDOHVXFKWKDWWKHGDWDZLOOIDOORQD
LGHQWLFDO*ROGHQ7UDQVPLWWHUVZKHQUHSOLFDWLQJ VWUDLJKWOLQHIRUDZHOOEHKDYHGGHYLFH8QH[SHFWHGEHKDYLRULVUHYHDOHG
WHVWVHWV*ROGHQ7UDQVPLWWHUVRIYDU\LQJVLJQDO LPPHGLDWHO\DQGFRQFOXVLYHO\WRWKHXVHU
TXDOLW\SURGXFHGLIIHUHQWUHFHLYHU%(5UHVXOWVD
VLWXDWLRQZKHUHVRPHUHFHLYHUV3$66RQRQHWHVW ,QWHOOL6FULSW7HVWLQJ6HTXHQFHWKURXJKVWDQGDUGEXLOWLQWHVWVDQG
VWDWLRQEXW)$,/RQDQRWKHU²DFDOLEUDWLRQDQG FRQWUROH[WHUQDOLQVWUXPHQWVVXFKDVHQYLURQPHQWDOFKDPEHUVSRZHU
FRUUHODWLRQPDQXIDFWXULQJFRQXQGUXP VXSSOLHV26$VRSWLFDOVZLWFKHVRVFLOORVFRSHVDQGZDYHOHQJWKPHWHUV
318
Golden Transmitters
6LJQDO4XDOLW\7KH267LQFOXGHVD*ROGHQ7UDQVPLWWHU
LQSXWDQGRXWSXWFRQQHFWRU7KH*ROGHQ7UDQVPLWWHU·V
VLJQDOLVGHJUDGHG([WLQFWLRQ5DWLRRU2615LQVLGHWKH
267WRDFFXUDWHO\SURYLGHWKHFKRVHQVLJQDOTXDOLW\
OHYHO)LUVWWKH267DXWRPDWLFDOO\FDOLEUDWHVWKH*ROGHQ
6LJQDO4XDOLW\0DQXIDFWXULQJWHVWLQJUHVXOWVXVLQJ*ROGHQ 7UDQVPLWWHUZLWKDXVHUVXSSOLHGH[WHUQDO2SWLFDO6SHFWUXP
7UDQVPLWWHUVZHUHQRWFRUUHODWHGZLWK5 'RWKHUPDQXIDFWXULQJ $QDO\]HUDQGWKHQLWDGGVWKHDSSURSULDWHDPRXQWRIVLJQDO
ORFDWLRQVRUZLWKFXVWRPHUV·WHVWUHVXOWVEHFDXVHRIWKHXQLTXH GHJUDGDWLRQ
FKDUDFWHULVWLFVRIWKH*ROGHQ7UDQVPLWWHU,QVRPHFDVHVWKH
*ROGHQ7UDQVPLWWHUZRXOGKDYHDKLJK([WLQFWLRQ5DWLRRUKLJK 7HVW6HW5HSOLFDWLRQ5HSOLFDWLQJWHVWVHWVLVHDV\XVLQJ
2615VLJQDOWKDWSURGXFHGRYHUO\RSWLPLVWLF%(5UHVXOWV2UWKH 267VEHFDXVHWKHVLJQDOTXDOLW\RI*ROGHQ7UDQVPLWWHUVFDQ
*ROGHQ7UDQVPLWWHUZRXOGKDYHDORZ([WLQFWLRQ5DWLRRUORZ2615 DOOEHFDOLEUDWHGWRWKHVDPHOHYHO7KH267XVHV*ROGHQ
WKDWGHFUHDVHGPDQXIDFWXULQJ\LHOGVEXWKHOSHGNHHSSURGXFW 7UDQVPLWWHUVWRDXWRPDWLFDOO\DQGFRQVLVWHQWO\WHVWRSWLFDO
UHWXUQUDWHVGRZQ%XWPRUHOLNHO\WKH*ROGHQ7UDQVPLWWHUZDV UHFHLYHUVHQVLWLYLW\%(5YV26152SWLFDO2YHUORDGDQG
JLYLQJD´W\SLFDOµSHUIRUPDQFHDQGH[WUDPDUJLQZDVDGGHGWRWKH 6;3HQDOW\
WHVWVSHFLÀFDWLRQWRNHHSSURGXFWUHWXUQUDWHVGRZQ
$QDO\VLV7KH267DOORZV5 'JOREDOPDQXIDFWXULQJ
7HVW6HW5HSOLFDWLRQ0DQXIDFWXULQJHQJLQHHUVKDGWRVHDUFK ORFDWLRQVDQGFXVWRPHUVWRDFKLHYHH[FHOOHQW%(5WHVW
WKURXJKFDQGLGDWHVRISRVVLEOH*ROGHQ7UDQVPLWWHUVWKDWZRXOG FRUUHODWLRQ7KLVIDFLOLWDWHVWURXEOHIUHHKDQGRIIVIURP
SURGXFHVLPLODUUHFHLYHU%(5UHVXOWVZKHQEXLOGLQJQHZWHVW 5 'WRPDQXIDFWXULQJHQDEOHVWKHUDSLGH[SDQVLRQRI
VWDWLRQVRUUHSODFLQJ*ROGHQ7UDQVPLWWHUVWRDYRLGDVLWXDWLRQ PDQXIDFWXULQJWHVWLQJFDSDFLW\ZLWKRXWPDQXIDFWXULQJ
ZKHUHVRPHUHFHLYHUVZRXOG3$66RQRQHWHVWVWDWLRQEXW)$,/ HQJLQHHUVVSHQGLQJWLPHVROYLQJFRUUHODWLRQSUREOHPV
RQDQRWKHU,IWKHPDQXIDFWXULQJHQJLQHHUVZHUHOXFN\RUKDGD DQGSURYLGHVDSODWIRUPWKDWHVWDEOLVKHVFRUUHODWLRQZLWK
ODUJHQXPEHURIWUDQVPLWWHUVWRFKRRVHIURPWKH\FRXOGPDLQWDLQ FXVWRPHUV
DUHDVRQDEOHFRUUHODWLRQEHWZHHQWHVWVHWV,IDPDWFKLQJ
WUDQVPLWWHUFRXOGQRWEHORFDWHGFRUUHODWLRQVWXGLHVKDGWREH
FRQGXFWHGDQGVKRSÁRRUVSHFLÀFDWLRQVFKDQJHGEDVHGRQWKHWHVW
VHWVEHLQJXVHG
$QDO\VLV7HVWUHVXOWVIURPGLIIHUHQWWHVWVHWVZHUHLQFRQVLVWHQW
ZKHQ*ROGHQ7UDQVPLWWHUVZHUHXVHG+DSKD]DUGVHOHFWLRQ
RI*ROGHQ7UDQVPLWWHUVDQGWKHGLIÀFXOW\LQGXSOLFDWLQJWKHP
FUHDWHGWHVWVHWFRUUHODWLRQSUREOHPVZKHQRXWVRXUFLQJWR
FRQWUDFWPDQXIDFWXUHUVDQGJHQHUDWHGVWLFN\FRUUHODWLRQ
SUREOHPVZLWKFXVWRPHUV $JSDBEJBOU4ZTUFNT *OD
,PSHULDO:D\6XLWH&
$OOHQWRZQ3$
7HO 7ROO)UHH
$OO5LJKWV5HVHUYHG
319
Application Briefs
320
CHAPTER 17 Technical Briefs
The following pages are Technical Briefs published by Circadiant Systems:

• “OSNR” on page 322
• “BER vs. OSNR” on page 328
• “Sensitivity Measurement Algorithms” on page 332
• “Straight-Line BERTM Plots” on page 337
321
Technical Briefs
17.1 OSNR
INTRODUCTION: Optical Signal to Noise Ratio (OSNR) is the measure of the ratio of sig-
nal power to noise power in an optical channel. For a typical optical communication sys-
tem for which the OSNR is relevant, the signal consists usually of nearly monochromatic
modulated light superimposed on a background comprised of (mostly unmodulated) opti-
cal power distributed over a broad wavelength range - a range including the signal wave-
length. This noise arises typically in optical amplification and it is better thought of as a
power density rather than a total power. The OSNR is usually measured with an OSA (Opti-
cal Spectrum Analyzer) and is defined as [Eq.1]:
OSNR = 10dB ⋅ Log 10 ⎛ ----⎞

S
⎝ N⎠
where the symbol S represents the (linear) optical signal power and the symbol N is the
(linear) optical noise power. This simple definition glosses over the details including the
not-so-simple issue of the bandwidth settings for the OSA used to determine both S and N;
these issues are discussed in the Nitty Gritty section below.
OSNR is important because it suggests a degree of impairment when the optical signal is
carried by an optical transmission system that includes optical amplifiers. The detection
of the signal is typically affected by attenuation and dispersion. With the use of amplifi-
ers, there is the additional impairment because of noise seen in the receiver due to the
presence of ASE (Amplified Spontaneous Emission) noise. In practice, the use of an ampli-
fier will help improve the signal because the increase in the signal amplitude will help
overcome noise generated in the receiver's front end. However, the optical background
(noise) that accompanies the desired optical signal will be amplified along with the signal;
consequently, the OSNR will tend to degrade as it passes through the transmission system.
The optical noise near the signal wavelength can impair the receiver's ability to properly
decode the signal because of optical interference between the optical signal and optical
noise. This impairment can be a bigger contributor to the BER than the power fluctuations
in the optical noise, especially when an optical filter centered on the signal wavelength is
placed ahead of the receiver.
In systems where the OSNR is relevant, a filter is often placed in front of the optical
receiver. Sometimes an "ASE" filter is used, particularly after an amplifier is used as a "pre-
amp"; in other cases, an optical deMUX (demultiplexer) serves as a filter. An ASE filter is
intended to cut down on the total ASE light by having an optical bandwidth large com-
pared to the signal (so as not to affect the signal) yet narrow compared to the bandwidth
associated with the ASE background. Then the total integrated ASE power is largely
reduced. The ASE filter is not expected to change the OSNR; the intention is to reduce the
total power in the ASE noise so as to not overload the receiver front end and to make total
optical power measurements closer to the signal power. In the case where an optical
deMUX is used, its primary purpose is usually to single out a particular optical channel, but
in the process it removes ASE light that is not near the signal wavelength.
Care is required to measure the OSNR correctly. The details described here cover the cali-
bration procedure for the OST (Optical Standards Tester), but they can be used in general.
The job hinges upon determination and separation of the optical signal S and the optical
noise N. In principle, the task is trivial. First, capture all of the power due only to the sig-
nal. This measured total signal power, S, has no contribution from background noise. Then
determine how much noise power, N, is contained within a narrow wavelength range of
322
OSNR
the signal. The customary procedure is to integrate the noise power in a 0.1 nm wide win-
dow centered on the signal wavelength although a 1.0 nm window is sometimes used.
Once these two values are known, the definition presented above can be used to deter-
mine the OSNR.
If the OSNR degradation is generated in a lab environment by using a coupler to superim-

pose ASE noise on the signal, then the trivial description above can be used directly since
an OSA can be placed downstream from the coupler, and S and N can be measured inde-
pendently by 'turning off' N while measuring S and vice versa.
If the OSNR is generated using a more real-world method where the signal actually passes
through an amplifier, S and N can't be easily separated since turning off the signal affects
the noise level. And turning off the noise, i.e. the amplifier(s), kills the signal. In this
case, the OSNR must be measured in situ; this is the situation in a realistic DWDM environ-
ment. Loosely speaking, this is done by measuring the total power in the peak and then
determining S by subtracting the amount of background noise that contributes to that
peak. The background noise is found by examining the noise contribution on either side of
the peak. Subsequently, infer the value for N by examining the noise contribution on
either side of the peak and calculate the amount of noise that is expected to be present in
a specific window (usually 0.1 nm, sometimes 1.0 nm) centered on the signal peak.
OSA BANDWIDTH: Ignoring for the moment that the background optical noise may
have wavelength dependence, the OSA will produce different responses to a modulated
optical signal depending upon its measurement bandwidth. Most OSAs used to study the
OSNR will be constructed around a grating based monochromator. One changes the band-
width (the word "bandwidth" remains to be defined, but it is related to the optical width
of the measurement window) by varying the slit spacing. In the middle of the pass band,
the response will be flat-topped. Thus, each point making up the trace displayed on the
OSA is an indication of the total optical power observed within the measurement window.
This also implies that a significant amount of power in any particular point is also con-
tained in the adjacent trace points since the bandwidth size is usually larger than the sep-
aration between points.
As the bandwidth is increased, the peak height increases also. This increase is due to two
causes. First, the modulated signal has some finite optical width, i.e., it spans some
wavelength range; if the measuring bandwidth is too small, some of the signal is discrimi-
nated against and one does not get a peak corresponding to the total signal power. The
second reason is that the background light will be present throughout the measurement. It
is best thought of as a "power density" with units, say, of mW/nm. Increasing the band-
width will cause the background contribution to grow, even adding to the detected peak.
There are at least two major concepts associated with bandwidth for an OSA where the
particular implementation of these concepts is manufacturer dependent. The first, the
most common definition of bandwidth, is the optical Full Width at Half Maximum (FWHM)
323
Technical Briefs
FIGURE 17.1-1:
for the measurement - the 3 dB width. This is usually associated with the phrase 'resolu-
tion bandwidth' and is typically quoted in nanometers. Increasing the resolution band-
width increases the monochromator slit width in a traditional OSA design. The second
concept is noise equivalent bandwidth, or integrated bandwidth, where for a given noise
equivalent bandwidth the OSA reports the power that would have been collected by an
ideal filter with this width having vertical sides and a flat top. Such a filter would ideally
be used to determine the background noise level. Clearly the OSA makes some assump-
tions about the optical signal being linear in the vicinity of the filter when reporting this
value.
Note that almost any filter characteristic can be used to determine the noise level, N,
provided that one knows the equivalent collection efficiency compared to an idealized
"window" with a flat top and vertical skirts. Most current OSA instruments supply this
equivalency automatically when "one pushes a button" to do noise measurements. With
older OSAs one might need to do one's own calibration by scanning a monochromatic
source and integrating the power response with respect to wavelength. Finally, note that
324
OSNR
the discrimination range of the OSA near the center wavelength is also relevant for OSNR
measurements since this is determined by the steepness of the wavelength response in the
skirts of the pass band. If the skirt width is too wide, then noise measurements can't be
made close to the signal wavelength since too much of the signal power 'leaks' into the
noise measurement.
THE NITTY-GRITTY: The measurements are done using an OSA that has a known mea-
surement bandwidth, BWM, which is large enough that the modulated signal fits inside.
With a filter this wide, the peak seen around the signal will accurately portray the total
signal power plus the local background level. For a typical 10 Gb/s transmitter, the mea-
surement resolution bandwidth, BWM, of 0.2 nm or 0.5 nm will provide essentially the
same peak value for the signal, once the background noise is subtracted off (see the linear
plots). A measurement bandwidth of 0.1 nm or lower will result in some signal power fall-
ing outside the quoted filter width; for example, a measurement bandwidth of 0.1 nm
would cause an under measurement of a 10 Gb modulated signal by about 0.7 dB. The sig-
nal, S, in mW is then determined by subtracting out the background level under the peak.
This background level is determined by first scanning enough to each side of the signal
peak that the background level is observed without contamination from the signal skirts.
The background level under the peak can then be inferred by interpolating between the
levels observed on either side of the peak. Note that these levels are all measured using
the same BWM used to determine the peak power and then interpolating between the two
values to infer the local background under the peak. This BWM may be indeed different
than the "reference bandwidth", BWR, that which is used to report the "noise power", N.
Determining the noise power under the peak, N, uses the same technique as is used to
determine the local background level under the peak, except that the measurement must
be made to yield power levels in a noise equivalent bandwidth. With the knowledge of
the measurement bandwidth being used, one scans enough to each side of the signal peak
that the background level is observed without contamination from the signal skirts. Notice
in the logarithmic plots the differing measurement bandwidths will result in different
apparent background power levels. These background levels reconcile to the same power
level when one uses the customary noise equivalent bandwidth, BWR, of 0.1 nm (1.0 nm is
sometimes used instead). Thus one would add 10 dB to the level seen with a measurement
made with a noise equivalent BW = 0.01 nm, subtract 3 dB for BW=0.2 nm, or subtract 7
dB for a BW=0.5 nm. All of the background values for the noise N in this 0.1 nm noise
equivalent bandwidth, BWR, would then match. Here it must be understood that the cor-
rections are for comparisons of the noise equivalent bandwidths (or integrated band-
widths), not resolution bandwidths.
Once S and N are known, the OSNR can be found by using equation (1). The notational con-
vention is to assign "units" to the answer: "dB/.1 nm" if a 0.1 nm reference bandwidth was
used for the value of N. If one had used the less common convention of calculating N for a
1 nm bandwidth, then the units of "dB/nm" would be used. The numerical value for the
same system would be 10 ("dB") less, because there would be 10 times more noise in the
increased reference bandwidth. The most common usage is to report results in dB/.1 nm.
Life is not quite so easy; the background may have some wavelength dependence.
Depending upon how careful one wishes to be and how much one can discern about the
background, one may interpolate the background level at the center of the signal by lin-
early interpolating the value from two points that flank the signal yet are just far enough
away to avoid being "contaminated" by the signal skirts. This linear interpolation is often
used by automated OSNR measurements available from a commercial test apparatus
(OSA).
The Circadiant OST generates a signal with adjustable OSNR degradation. This generated
signal is not embedded into a DWDM. The OST further contains an optical filter that causes
325
Technical Briefs
the background noise to be peaked in the region of the signal. A more accurate determi-
nation of the noise underneath the peak is obtained by sampling several points to each
side of the peak beyond the signal skirt and doing a quadratic interpolation for the
expected noise at the signal wavelength. The estimate is improved by using quadratic
interpolation rather than the automated linear interpolation techniques often supplied
FIGURE 17.1-2:
with the OSA. Including higher order polynomial terms in a Taylor series interpolation is
not warranted for the interpolation interval used here.
CONCLUSIONS: One can summarize the measurement process for a single modulated
signal superimposed on a noise background that is typically peaked from passing through
an optical filter such as an ASE filter. A measurement bandwidth that is wide enough that
the modulated signal is completely contained within its flat-topped bandwidth is chosen.
One then scans across the neighboring background, over the peak, and the neighboring
background on the other side. Using the scans of the background away from the modu-
lated signal one can do a quadratic interpolation of the background level underneath the
signal peak. The background level is then subtracted from the peak to obtain the signal
power without the contribution from the background. Before determining the OSNR, one
chooses a reference bandwidth, usually 0.1 nm and then rescales the height of the inter-
polated noise by using the ratio of the reference bandwidth to the integrated measure-
ment bandwidth. If the reference bandwidth is narrower than the integrated
measurement bandwidth, the fitted background is lowered. Finally, the OSNR is the differ-
326
OSNR
ence of the signal (in dBm) less the interpolated background (in dBm) corrected to the ref-
erence bandwidth. The resulting OSNR is assigned units of dB/.1 nm (or dB/nm if the
reference bandwidth chosen was 1 nm).
The use of a quadratic fit is appropriate for a single signal passing through an ASE filter. If
one is measuring the OSNR in a DWDM environment, where there is barely enough space to
measure the noise background in the valley between neighboring signals, only a linear
interpolation is done; see TIA/EIA-526-19, OFSTP-19, "Optical Signal-to-Noise Measure-
ment Procedures of Dense Wavelength-Division Multiplexed Systems."
In describing the OSNR it is important to make sure that the measurement method is
clearly understood and stated. The assumed value of the reference bandwidth should be
clearly indicated as either the typical 0.1 nm or as 1.0 nm. Conventionally, following the
numerical value with "dB/.1nm" or "dB/nm" indicates this.
327
Technical Briefs
17.2 BER vs. OSNR

INTRODUCTION: The BER (Bit Error Ratio) is a fundamental quality measure for digital
communications. Whereas a study of the BER versus Power is good to characterize the
reception of weak, unamplified digital optical signals, the study of BER versus OSNR is
good to characterize the reception of strong, amplified optical signals. Once a signal has
been degraded to a certain level of OSNR, the BER for a certain receiver design cannot be
improved regardless of signal strength. Thus, in the design of an amplified digital trans-
mission system, the final, delivered OSNR becomes a major issue and concern. It is then a
question of whether the receiver can produce an adequate BER from that OSNR.
Modern communications systems over fiber optics strive for and usually succeed in obtain-
ing a BER of 10-12 and better (lower!). Another Tech Brief, "Straight-Line BERTM Plots"
(TB010) describes how it is often possible to plot the BER versus Power (the received aver-
age optical signal power) and obtain a plot that is so close to a straight line that interpola-
tion or moderate extrapolation is plausible. It will be shown later that the plot of BER
versus OSNR is similarly useful.
Also, another Tech Brief, "OSNR" defined OSNR and how is it measured. It is the OSNR
(Optical Signal to Noise Ratio) that can be observed in systems that include optical ampli-
fication. The "noise" here is the presence of ASE (Amplified Spontaneous Emission) noise
that is generated within the amplification process and is relatively broadband. One of the
consequences of having a low OSNR is that no matter how strong the signal presented to a
good receiver, there will be errors associated with the presence of the ASE. The exact
level of BER for a given OSNR depends upon the receiver.
Depending upon the receiver, one could determine the minimum acceptable OSNR to
achieve a given BER. To improve upon this BER it would be necessary to increase the
OSNR, use Forward Error Correction (FEC), and/or to use a different receiver.
NOISE CONTRIBUTION: The ASE can contribute electrical noise to the analog signal
that follows the OE (Opto-Electric) conversion, usually a photodiode. By operating at large
signal levels, this noise contribution is the only one that concerns us here; it means that
the BER no longer is a function of attenuation in front of the receiver. Attenuation in front
of the receiver reduces both the desired eye size and the noise that is superimposed upon
it; thus the decision level remains the same number of sigma away from the inner edge of
the eye. The noise from ASE is expected to be Gaussian (normally distributed) because it
arises from the linear superposition of many, statistically independent contributions from
all the different wavelength components of the ASE. The noise contribution from the ASE
appears as a "BER floor" in the usual plot of the BER versus signal power plots.
The instantaneous electrical current produced in the photo detector is proportional to the
instantaneous received optical power, P(t), which depends upon the combination of the
instantaneous signal power, S(t), and the instantaneous ASE power, N(t). Since these two
sources of light are arriving from the same single-mode fiber to the receiver, they may
optically interfere. In this Tech Brief, phase and polarization issues are simplified by
assuming that taking the square root of the power provides the "optical amplitude". Thus
one takes as the optical amplitude of the optical signal, S ( t ) , and of the ASE, N ( t ) . The
combined optical amplitude is the sum of these two amplitudes and squaring this com-
bined amplitude should be indicative of the total optical power, thus:
P(t ) = S(t) + 2 S(t) N(t) + N(t)

The three terms on the right-hand side are, respectively, left to right: the signal power,
the "interference term", and the ASE power. Thus there are two types of noise terms
328
BER vs. OSNR
expected from the ASE. One type of noise will have an electrical amplitude contribution
that is proportional to the total ASE power received, N(t), the other will be a contribution
proportional only to the square-root of the ASE power: 2 S ( t ) N ( t ) . Because of the
finite bandwidth of the receiver, generally comparable to the data rate, much of the time
dependence of each term will not be observable. If the electrical response of the receiver
is limited, say, to 10 GHz, then two optical spectral components that are separated by
more than 0.08 nm (for 1550 nm operation) will have an interference beat frequency that
exceeds the electrical bandwidth, and that interference contribution will not be seen.
Where the BER is relatively low (because S>>N) the magnitude of the contributions of the
three terms decreases sharply from leftmost term to rightmost term. The leftmost term
provides the desired signal whose time dependence is intended to just fit inside the
receiver electrical bandwidth. The middle term represents the beat or interference term
between the signal and the ASE fields. There is not expected to be any long-term correla-
tion between the terms so there is no "DC" contribution, but contributions come from
those spectral portions of the ASE whose optical wavelength is so close to the signal opti-
cal wavelength that the difference frequency is within the electrical receiver bandwidth,
perhaps 8 GHz when operating at 10 Gb/s. The most likely contribution of the rightmost
term is its DC component making the effective extinction ratio for the receiver less; the
time dependence of this term is very broad high frequency noise that has as least as much
trouble getting through the receiver's electrical bandwidth as that of the middle term.
Under special circumstances the contribution from the third (right-most) term can be
noticeable. If the BER is relatively high then the ratio of the terms is not so large. Also, if
the ASE exists over a very large range, the total, integrated ASE power can be larger than
the signal power. Both the DC component and the electrical noise power that can enter
the receiver's low-pass filtering will grow in proportion to the optical bandwidth (keeping
the ASE optical power density fixed).
Sometimes an ASE filter or optical demultiplexing filter is used after an optically amplified
system. This filter is usually much broader than the signal bandwidth and much narrower
than the total ASE spectrum. This filter does NOT improve the OSNR (the ratio of the left
to middle terms), but it does reduce the contribution of the third (rightmost) term. It is
helpful for sensitive receivers that might be adversely affected by the large ASE back-
ground of the pre-amplifier.
In the electrical domain, the signal current is proportional to the leftmost term, S(t),
while the middle term provides the principle source of electrical current noise. Thus the
electrical signal-to-noise is usually proportional to S ⁄ N , namely OSNR . In a compan-
ion Tech Brief, "Straight-Line BER PlotsTM" (TB010), Circadiant recommends a particular
method of plotting. It exploits an expected relationship between the electrical signal to
noise and the observed BER. This method is to plot the vertical scale with the BER in a
non-linear fashion where the underlying linear function is (10 dB)·Log10(erfc-1(2·BER)).
When "BER versus Power" is being plotted the horizontal axis is in dBm: (10
dBm)·Log10(P(mW)). This method of plotting can be readily extended to "BER versus
OSNR"; here the horizontal axis would be in (10 dB)·Log10(OSNR). In one case the electri-
cal signal to noise is expected to scale with P(mw), in the other case the electrical signal
to noise is expected to scale with OSNR . The resulting plots of "BER versus OSNR" will
resemble plots of "BER versus Power", but the square root dependence:
1
Log 10 OSNR = --- ⋅ Log 10 ( OSNR )
2
will make the slopes half as large in the OSNR case compared to the P(mW) case so long as
the horizontal axis is in logarithmic units (dB or dBm).
329
Technical Briefs
The middle term also indicates that most of the fluctuations that lead to errors will be in
the reception of logic 1s compared to logic 0s because S(t) is larger for the former. Thus,
if the decision threshold is set at the 50% level, omit errors will dominate the BER.
IMPROVING BER FOR GIVEN OSNR: The OSNR basically creates a BER floor and
increasing the optical input to the receiver does not improve the BER because the source
of noise scales with the signal. Careful adjustment of the receiver's bandwidth can help. If
the receiver has excessive electrical bandwidth, more electrical noise from the middle
and last term contribute to the error rate. If the receiver has insufficient electrical band-
width, it will degrade the eye opening. One wants to have the bandwidth controlled to
maintain maximum eye opening relative to the "hiss" produced from the ASE.
A second improvement would be to lower the decision threshold toward the 0s level.
There is less electrical noise associated with the lower level; the BER is minimized by
placing the decision level where the distance to each level is proportional to the noise
ratios. A similar adjustment is often contemplated for APDs (Avalanche Photo Detectors)
in shot noise dominated applications.
EXPERIMENTAL CONFIRMATION: The attached figure shows an automatic test of

BER versus OSNR that was done with Circadiant's OST (Optical Standards Tester). Not only
does it confirm the straight-line behavior expected in the plot, but shows the reduced
slope as well. The horizontal range is about 4.5 dB, whereas typical sensitivity plots
involving optical power usually span about half that.
FIGURE 17.2-1:
330
BER vs. OSNR
CONCLUSIONS: The BER is expected to be a typical function of the electrical signal

current compared to the electrical noise current. Where the OSNR is the principle deter-
minant of BER one usually finds that the electrical signal is proportional to S and the elec-
trical noise that results in reducing the vertical eye opening is proportional to
S ( t ) N ( t ) . The optimum positioning of the decision threshold should be closer to the
bottom of the eye because the vertical eye closing due to this term will be coming more
from the top of the eye than from the bottom of the eye. The ratio of the leftmost to mid-
dle terms is proportional to S ⁄ N , which is seen as the square root of the OSNR. When
one plots the BER versus OSNR using the methods described in "Circadiant Plotting Meth-
ods" (TB010), one observes a reasonably straight plot but with the slope being only half as
large as the ideal slope for reception where the electrical signal to noise scales linearly
with signal power. This half slope is a result of the square-root dependence.
For amplified systems, the ability of the receiver to provide the requisite BER in the pres-
ence of a designed level of OSNR may be its most important characteristic.
331
Technical Briefs
17.3 Sensitivity Measurement Algorithms

INTRODUCTION: The sensitivity of a fiber optic digital receiver is the minimum aver-
age optical power required by the receiver to perform with a given level of BER. It used
to be common to specify the required BER (Bit Error Ratio) to be 10-9 for slower data
rates. Now with the data rates typically at 10 Gb/s, the usual required BER is better than
10-12 under worst case conditions. In practice equipment is rarely operating under worst-
case conditions; it is likely that systems in normal operation do not show a measurable
BER.
Even if fiber optic receivers are mass produced, their sensitivities will be distributed and
usually the user will want to have each unit characterized either by the manufacturer or
by incoming inspection (or both). Reduced sensitivity in a receiver can be due to a large
number of factors. Such factors include the quality of the fiber termination and align-
ment, the optical filters and coatings, the photo detector, and the frequency response
and noise levels in the input circuitry. Rather than trying to determine each of these fac-
tors individually, the user wants the peace of mind that the digital communication is vir-
tually error free.
Traditionally, the receiver to be tested is placed in a test set up where the input pattern
is generated and the signal power adjusted. The received digital pattern is compared to
the expected pattern and errors are noted. This arrangement is potentially time consum-
ing because there are so many measurements to be made for each and every receiver
needing testing. There is a fair amount of data to be processed and careful record keeping
is a must. One is concerned here with ways to minimize the effort and time to guarantee
sensitivity goals are met for a given receiver.
In the following, the methods provided by Circadiant's Optical Standards Tester (OST) are
described. It will be seen that the ability to follow a detailed sequence of individual BER
tests and to determine the underlying sensitivity automatically results in faster and more
accurate testing and data logging. The needed test parameters are explained for each
type of automated measurement technique. The corresponding portions of the OST set-up
screen are shown as illustration.
PRETEST: Occasionally, a receiver is "broken". It could be that the fiber coupling does
not exist or that the photo detector or circuitry is defective. Because of this possibility,
one may elect to do a very quick pretest to see if the device can be rejected without
resorting to a sensitivity scan.
The pretest uses a selected power level where one expects that any functioning receiver
would have a better sensitivity value than this. The power chosen should not be higher
than the rated maximum power for the receiver (so as to not do damage), nor should it be
possibly in the saturation level for the receiver. If even one bit error is seen during the
selected time interval for the pretest, the device fails the pretest. The device test is
aborted without having used much time.
The pretest is able to reliably see a BER that is higher than about 10/(number of bits
transmitted during pretest). So, for example, a 1 second pretest at 10 Gb/s will reject vir-
tually all devices that have a BER greater than 10/1010 (> 10-9).
AUTO POWER: When the user wants a BER versus power plot for the range of interest,
he or she can set up the test sequence to be carried out automatically. The parameters
that need to be supplied are the range described in terms of start and finish power. Also
332
Sensitivity Measurement Algorithms
the user specifies either the number of test points desired or the power change between
test points.
In the course of generating each point, how much time is one willing to spend? This can be
more usefully restated as: "How precise does the BER need to be?" For the high BER one
can record data for very little time and still have very narrow limits on the estimated BER;
not so for the low BER points. Thus the user specifies two remaining constraints: The
desired accuracy (i.e. uncertainty) and the maximum time the user is willing to allow data
to be recorded for each point.
In order to have an uncertainty in the BER of 30%, one needs at least about 10 errors
observed. See the Tech Brief on "Uncertainty for BER Measurements" (WP009). If one is
willing to take 3 seconds for a point that has 10 errors, one has seen about 3·1010 bits
transmitted and so the two constraints (uncertainty and time) match here at a BER of
about 3.3·10-9. Thus it is expected that for the higher BER cases one will achieve an
uncertainty smaller than the requested one in a short time and the data taking for that
point can be stopped quickly. For cases where the BER is lower, one will usually not have
enough errors by the time one will run out of time. Here the data taking for this test point
will stop at the end of the selected time and the measured BER will have larger than the
requested uncertainty.
FIGURE 17.3-1: “Auto” BER. Portion of Circadiant Optical Standards Tester showing set up
for “Auto” test.
AUTO BER: This is similar to "Auto Power" but is a bit more automated in that one can
describe the desired range indirectly in terms of BER. This way, different devices being
tested will be analyzed over the range that is of most interest in terms of BER.
333
Technical Briefs
The software in the controller needs to find the equivalent power range from the data
being given and so the tester needs to take additional data beyond the data points that
produce the plot. In many cases the testing is actually faster because the range of interest
can be narrowed and fewer points are then needed in the plot. If the user supplies a rea-
sonable estimate of the sensitivity, the search effort is shortened and even more time is
saved.
INTELLITIMETM: This test mode will appeal more toward the R&D side. Here a total
amount of time to test is specified, say, an hour over lunch or several hours overnight.
The test is carried out in a way to get as much of the sensitivity plot as possible in this
allotted time. Of course, the allotted time chosen can be shorter or longer. There is no
emphasis on passing or failing a particular specification.
In order to have a meaningful result, one needs to have a number of errors seen during the
taking of each test point. Say, this number is 10 errors, resulting in a typical uncertainty of
30%. Allocating 90%, say, of the total test toward the lowest BER point (highest power),
one can allocate 9% to the next lowest BER point that is about 10 times higher BER, 0.9%
to the next lowest BER, etc. In this way, one plans, say, the three lowest BER points.
One starts off with a fast Auto BER plot (short compared to the total time allotted), then
one plans the next lower BER measurement using a power based upon the extrapolated
BER needed to have, say those 10 errors on average in 1% of the remaining time. If the
number of points seen is close to the expected number, one can continue the linear
extrapolation, otherwise, one raises or lowers the estimated power to use to get about 10
errors in the remaining 10% of the remaining time. After this measurement is made one
again checks to see if the number of errors is close to the expected number. If not, one
revises the extrapolation to plan the power level to be used to test for 100% of the
remaining time to get the target number of errors. In this way, one uses one's testing time
more effectively.
334
Sensitivity Measurement Algorithms
FIGURE 17.3-2: IntelliTimeTM Testing. Portion of Circadiant Optical Standards Tester

showing set up for IntelliTimeTM test.
Further refinements are possible. If, during a test, the errors appear to be coming in much
faster than expected, one could terminate the test early to have more time for further
tests. In this way, if a high BER floor is found, it may be possible to follow it a lot further
than if one refuses to take more than the original number of points planned.
HYSTERESIS: All of the above discussion assumes that the device under test or the sub-
system under test is responding in a fixed manner that depends only upon the current
power. There are instances where this is not true. If one has previously tested in a high
BER regime, some part of the test system may have changed.
For example a SONET framer may have lost framing. A more elaborate example is where
the subsystem under test went into a protection-switching mode whereby a new path (and
hence a new behavior) was selected.
Protection switching should be disabled. If there are framers, mute circuits, or other BER
sensitive switches involved, try to disable their operation or work around their propensi-
ties. It may be good to perform most of the testing first at better (lower) BER and not go
to the lower power, (higher) BER at the beginning of testing.
Hysteresis effects may be observed by performing tests back-to-back where the start and
finish power (or BER) values are reversed.
CONCLUSIONS: By using special testing algorithms, it is possible to obtain more tests

and more information in a given amount of testing time. This is one of the big advantages
of using a purpose built testing system that has a controller that is able to supervise the
335
Technical Briefs
BER tests, the power levels and the time spent on each test dynamically. By automatically
presenting the data while the test is progressing the operator can better appreciate the
peculiarity of any device under test, even before the data is submitted to the database for
later examination.
336
Straight-Line BERTM Plots
17.4 Straight-Line BERTM Plots
INTRODUCTION: In plotting results of BER versus optical power or BER versus OSNR, it
is possible to use plotting paper analogous to "semi-log" paper in which one expects that
for idealized reception, at least, the plots will be straight lines. (Note: "semi-log paper
does NOT work here!) The straight-line plots provide an obvious way to fit experimental
data and also to interpolate/extrapolate. It may be necessary to extrapolate to low BER
regions where data may not have been taken because of time constraints.
BER Theory: The BER (Bit Error Ratio) results from the statistical effects of various
forms of noise combining with the ideal signal to cause the receiver to occasionally pro-
duce bit errors. In general, the greater the size of the statistical effects, hereafter
referred to as "noise", compared to the size of the signal, the higher the observed BER.
The incoming optical signal reaching the receiver is first converted to an electrical signal
by means of a PIN or APD photo detector. The electrical signal is typically so weak that the
electrical noise of the input receiver electronics cannot be ignored. Sometimes, for the
APD (Avalanche Photo Detector), the gain within the detection process is large enough
that one actually sees noise effects due to the quantum nature of light and the photoelec-
tric effect; such noise is called "shot noise". In optically amplified transmission systems,
ASE (Amplified Spontaneous Emission) noise accompanies the incoming optical signal. The
OSNR (Optical Signal to Noise Ratio) often characterizes this admixture. The finite OSNR is
also a form of noise that interferes with the accurate determination of the original digital
content of the data.
Any of these forms of noise are expected to be "Gaussian" (with the possible exception of
quantum shot noise when there are very few photons/bit and Poisson statistics are appro-
priate). That is to say, the deviation of the electrical signal from the ideal, noiseless case
follows a normal distribution,
x2
1 – ---
P ( x ) = ---------- e 2
2π
where x is the measure of standard deviations (number of σ).
The results of the additional noise are seen in eye patterns captured on a digital oscillo-
scope. One sees in the accompanying figure [Figure 1] that the display of the eye "looks
fuzzy". The eye pattern is just the overlaying of many bits in the detected signal. To use
the eye to estimate the BER, one should use "infinite persistence". If the middle of the eye
is clear of traces, it suggests that the use of a decision level and a time position will
enable the receiver process to convert the received analog signal back to a synchronous
digital stream with each bit properly detected. To the extent that there are occasional
traces across the middle of the eye, it suggests that for these traces there is a strong pos-
sibility that data bits are misinterpreted and will result in bit errors.
337
Technical Briefs
FIGURE 17.4-1:
The next figure [Figure 2] concentrates on the central temporal portion of the eye and
provides algebraic symbols to be more specific in the following presentation.
338
FIGURE 17.4-2:
The bottom portion of the eye is the "0 level". Its average value is given by µ0 and its vari-
ability is given by σ0. The top portion of the eye is the "1 level". Its average value is given
by m1 and its variability is given by σ1. Near the middle of the eye will be the decision
threshold located at D. Any electrical signal below D will be interpreted as a logic "0", and
any signal above D will be interpreted as a logic "1". To the extent that the decision level
properly and completely separates the 0 level and the 1 level, there will be no errors. But
because a normal distribution always has some probability density at any given distance
from the mean, there will always be some, albeit very occasional, errors.
The accompanying 3-part figure [Figure 3] shows how the proximity of the decision point
D when close to µ0 will yield errors where transmitted 0s are decoded as 1s (figure part A)
and when close to µ1 will yield errors where transmitted 1s are decoded as 0s (figure part
B). If the eye is very open, namely (µ1−µ0) >>σ0,σ1, then D can be chosen to yield very
few errors (figure part C). To calculate the frequency of these two types of errors, one
needs to evaluate the integral under the normal distribution, as indicated by shading in
parts A and B of the figure.
339
Technical Briefs
FIGURE 17.4-3:
One can use the standard function, erfc(x), called the "complementary error function," to
evaluate these integrals associated with the error probabilities. This function is defined:
∞
∫
2
2 –t
erfc ( x ) ≡ ------- e dt
π
x
A good reference point to use in a "sanity check" is that erfc(0)=1.
340
As an intermediate step the Q0 and Q1 are defined as the relative distance of each rail
from the decision level measured in units of r.m.s. noise:
( D – µ0 )
Q 0 = --------------------
σ0
and
( µ1 – D )
Q 1 = --------------------
σ1
The use of the Q with the complementary error function gives the probability for errors:
Q0
P ( 0 → 1 ) = --- ⋅ erfc ⎛ -------⎞
1
2 ⎝ 2⎠
and
Q
P ( 1 → 0 ) = --- ⋅ erfc ⎛⎝ ------1-⎞⎠
1
2 2
By assuming that there are fractions f0 of 0s and f1 of 1s in the data pattern,
BER = f 0 ⋅ P ( 0 → 1 ) + f 1 ⋅ P ( 1 → 0 )
A well-designed receiver will locate the decision level, D, so that the BER is minimized.
This minimization occurs at: Q0 = Q1, namely where σ0/σ1 = (D-µ0)/(µ1-D). Thus one can
keep things simple if one defines a universal Q = Q0 = Q1 that results in the simplification:
BER = --- ⋅ erfc ⎛ -------⎞

1 Q
2 ⎝ 2⎠
This expression is easily inverted:
–1
Q = 2 ⋅ erfc ( 2 ⋅ BER )
Based upon various assumptions, the noise terms are either independent of the signal,
proportional to the square root of the optical power, or proportional to the optical power.
These cases correspond to the noise in the input receiver electronics, in the shot noise, or
present from the optical input, respectively. The separation between the levels, µ0, D,
and µ1, is usually proportional to the input optical power.
Thus it is expected that the value of Q is proportional to some power of the input optical
signal. Q is proportional to the signal if the noise is constant in the receiver, it is propor-
tional to the square root of the optical signal if shot noise dominates, and it is indepen-
dent of optical power where the OSNR contribution to the noise dominates.
341
Technical Briefs
Plotting: In order to convert mathematical power relationships (linear, square root,

etc.) to linear plots one can plot the log of Q versus the log of optical power. One can
achieve this by using dB-like units for the Q factor along the vertical axis,
Q ( dB ) = ( 10dB ) log (Q)

10
–1
( 10dB ) log ( Q ) = ( 10dB ) log 10 ( erfc ( 2 ⋅ BER ) )
10
and by using dBm to represent power along the horizontal axis,
P ( dBm ) = ( 10dBm ) ⋅ log 10 ( P ( mW ) )
The 2 has been dropped because it is just an additive constant after a logarithm is
taken.
As seen in the accompanying specialized plotting paper supplied by Circadiant [Figure 4],
one can cover quite a few decades of BER (here 10-4 down to 10-16) with a few dB range in
power (here 8 dB).
342
FIGURE 17.4-4:
Under more typical experimental conditions, one may not wish to explore very low BER
due to time constraints and to limit oneself to about 3 dB range in optical power and less
than 5 decades of BER as seen in typical Circadiant automatic plots. In this supplied exam-
ple [Figure 5], it can be seen that although the plot stopped at a BER of 1·10-8, one can
be confident in using a linear extrapolation here to estimate that power needed to
achieve 1·10-10 is -19.32 ±0.08 dBm because of the quality of the linear fit. Of course, if
one has the testing time available, it is good to take another data point closer to the
power level, -19.3 dBm, to reduce the amount of extrapolation needed.
343
Technical Briefs
FIGURE 17.4-5:
Different kinds of receivers have been investigated in this manner and it is also common to
find that the slope of the straight-line fit is shallower for APD based receivers than for PIN
based receivers. This is understandable in view of the PIN sensitivity being exclusively
dominated by noise present in the preamplifier electronics, whereas the APD sensitivity is
affected by optical power dependent shot noise.
Finally: Although this style of plotting is not common, it is well worth the effort of using
this type of plot. Additional information about the DUT (Device Under Test) performance
is revealed with this type of plot that might otherwise be difficult to discern if more
traditional plotting is used or if the data is in tabular form. The Circadiant Optical
Standards Tester automatically plots data on the Straight-Line BERTM plot and includes a
BER extrapolation function. Circadiant's web site, http://www.circadiant.com, allows one
to enter the BER with corresponding power levels and then generate a Straight-Line BERTM
plot. Web generated plots may be saved and super-imposed for comparison purposes. Pads
of the Straight-Line BERTM plot paper are also available from Circadiant on request.
344
CHAPTER 18 Glossary of Acronyms
18.1 Glossary of Acronyms

10GE LAN 10 Gb/s Ethernet Local Area Network
10GE WAN 10 Gb/s Ethernet Wide Area Network
AAL ATM adaptation layer
AIS–L line alarm indication signal for SONET traffic (signal error)
AIS–P STS path alarm indication signal for SONET traffic (signal error)
AIS–V VT path alarm indication signal for SONET traffic (signal error)
ANSI American National Standards Institute
APD avalanche photo diode
APS automatic protection switching
ATM asynchronous transmit mode
ATN attention (GPIB interface management line)
AU–AIS administrative unit alarm indication signal for SDH traffic (signal error)
BBE background block error (signal error)
BER Bit Error Rate
BERT Bit Error Rate tester
BIP binary interleave parity
BITS building integrated time signal
CD Compact Disk
CRC cyclic redundancy check
CSES consecutive severely errored seconds (signal error)
CV coding violation (signal error)
CV–L line layer coding violation for SONET traffic (signal error)
345
Glossary of Acronyms
CV–HP path layer coding violation for SDH traffic (signal error)
CV–MS multiplex section coding violation for SDH traffic (signal error)
CV–P STS path layer coding violation for SONET traffic (signal error)
CV–R regenerator section coding violation for SDH traffic (signal error)
CV–S section layer coding violation for SONET traffic (signal error)
DAV data valid (GPIB handshake line)
DIO# data in/out line, 1 through 8 (GPIB data lines)
DUT device under test
EB errored block (signal error)
EDFA Erbium doped fiber amplifier
EOI end or identify (GPIB interface management line)
ER Extinction Ratio
ES errored seconds (signal error)
ESA errored second type A (signal error)
ESB errored second type B (signal error)
ES–L near end line errored seconds for SONET traffic (signal error)
ES–MS multiplex section errored seconds for SDH traffic (signal error)
ES–R regenerator section errored seconds for SDH traffic (signal error)
ES–S section errored seconds for SONET traffic (signal error)
FCS Frame Check Sequence
GE Gigabit Ethernet
GPIB general purpose interface bus (ANSI/IEEE Standard 488.2-1987)
GUI graphical user interface
HDLC High Level Data Link Control
HEC header error correction
HP–PLM high order path payload label mismatch for SDH traffic (signal error)
HP–RDI high order path remote defect indication for SDH traffic (signal error)
HP–REI high order path remote error indication for SDH traffic (signal error)
HP–TIM high order path trace identifier mismatch for SDH traffic (signal error)
HP–UNEQ high order path unequipped defect for SDH traffic (signal error)
IEEE Institute of Electrical and Electronics Engineers
IFC interface clear (GPIB interface management line)
IP internet protocol
ISI inter-symbol interference
IsoBER Iso Bit Error Rate is a test that contour maps the various combinations of optical power and
OSNR that produce the same BER.
346
ITU–T International Telecommunications Union-Telecommunications

LAN Local Area Network
LED Light Emitting Diode
LLC Logic Link Control
LOF loss of frame (signal error)
LOM loss of multiframe (signal error)
LOP loss of pointer (signal error)
LOP–P STS path loss of pointer for SONET traffic (signal error)
LOP–V virtual tributary path loss of pointer for SONET traffic (signal error)
LOS loss of signal (signal error)
LP–PLM low order path payload label mismatch for SDH traffic (signal error)
LP–RDI low order path remote defect indication for SDH traffic (signal error)
LP–REI low order path remote error indication for SDH traffic (signal error)
LP–RFI low order path remote failure indication for SDH traffic (signal error)
LP–TIM low order path trace identifier mismatch for SDH traffic (signal error)
LP–UNEQ low order path unequipped defect for SDH traffic (signal error)
LSS loss of sequence synchronization (signal error)
LVTTL low voltage transistor to transistor logic
MPLS multi protocol label switching
MRU maximum receive unit
MS–AIS Multiplex Section alarm indication signal for SDH traffic (signal error)
MS-RDI Multiplex Section Remote Defect Indicator for SDH traffic (signal error)
MS–REI Multiplex Section Remote Error Indication for SDH traffic (signal error)
NDAC not data accepted (GPIB handshake line)
NNI network to network interface
NRFD not ready for data (GPIB handshake line)
OAM operations, administration, and maintenance
OMA Optical Modulation Amplitude
OOF Out of Frame (signal error)
OS Operating System
OSA Optical Spectrum Analyzer
OSNR Optical Signal to Noise Ratio
OST Optical Standards Tester
OSTC Optical Standards Tester Controller
OTN Optical Transport Network
347
PCS Frame Decode Error

PLM–P STS path payload label mismatch for SONET traffic (signal error)
PLM–V virtual tributary path payload label mismatch for SONET traffic (signal error)
PoS packet over SONET
PPP point to point protocol
PRBS pseudo-random bits per second
RDI–L line remote defect indication for SONET traffic (signal error)
RDI–P STS path remote defect indication for SONET traffic (signal error)
RDI–V virtual tributary path remote defect indication for SONET traffic (signal error)
REI–L line remote error indication for SONET traffic (signal error)
REI–P STS path remote error indication for SONET traffic (signal error)
REI–V virtual tributary path remote error indication for SONET traffic (signal error)
REN remote enabled (GPIB interface management line)
RFI–L line remote failure indication for SONET traffic (signal error)
RFI–P STS path remote failure indication for SONET traffic (signal error)
RFI–V virtual tributary path remote failure indication for SONET traffic (signal error)
RS–TIM regenerator section trace identifier mismatch for SDH traffic (signal error)
RX receive
SCPI standard commands for programmable instruments
SD signal degrade (signal error)
SDH synchronous digital hierarchy
SEF severely errored frame (signal error)
SEQBRK Sequence Break is an error source check that counts the number of times that a repeating
sequence imbedded into the first 16 bits of the IP payload by the Optical Standards Tester is broken.
SES severely errored seconds (signal error)
SES-S severely errored seconds - section
SF signal fail (signal error)
SFD Start of Frame Delimiter
SMSR side mode suppression ratio
SONET synchronous optical network
SRQ service request (GPIB interface management line)
STM synchronous transport module
STS synchronous transfer signal
Tcl/Tk Tool Command Language / Tool Kit
TDM time division multiplexing
TIM–P STS path trace identifier mismatch for SONET traffic (signal error)
348
TIM–S section trace identifier mismatch for SONET traffic (signal error)
TIM–V virtual tributary trace identifier mismatch for SONET traffic (signal error)
TSE test sequence error
TTL transistor to transistor logic
TU–AIS tributary unit alarm indication signal for SDH traffic (signal error)
TU–LOM tributary unit loss of multiframe for SDH traffic (signal error)
TU–LOP tributary unit loss of pointer for SDH traffic (signal error)
TX transmit
UAS unavailable seconds (signal error)
UNEQ–P path unequipped defect for SONET traffic (signal error)
UNEQ–V virtual tributary path unequipped defect for SONET traffic (signal error)
UNI user to network interface
VCI virtual channel identifier
VPI virtual path identifier
VT virtual tributary path
WAN Wide Area Network
349
350
Index
Numerics Audible SyncLoss Alarm .............49 ES-S .................................................53
10 Gb/s Optical Standards Test System Error Source for Gating and Ethernet Interface ..........................156
Overview ............................5 Instantaneous BER ...............49 Ethernet Port LEDs ............................5
10 GE WAN/LAN Features .............19 Error Sources ...............................48 Exhaust/Intake Fan ..........................10
10/100 BaseT Gate Type .....................................50 External Instrument Control ......13, 58
IN .................................................12 Measurement Control ..................49 Optical Oscilloscope Control .......60
OUT .............................................12 Results ..........................................51 Optical Spectrum Analyzer Control 58
10GE LAN Traffic Configuration ....23 Setup ............................................48 Optical Switch Control ................61
10GE WAN Traffic Configuration ...27 Bitstream Data Traffic Configuration 22 Power Supply Control .................63
10GE WAN/LAN Tests ..................147 Temperature Controller ................64
802.3 Statistics & Error Injection Control C Wavelength Meter Control ..........62
151 CalFactor Assistant ..........................46 External Loop ..................................10
Calibration Factor ............................46 External Receiver ..............................9
A Clock External Transmitter ..........................8
A3308 .................................................2 1 Hz ................................................7 Extinction Ratio ...............................35
Front Panel .....................................5 155.52 MHz ...................................7
Operating Transmit Section .........44 161.13 MHz ...................................7 F
Rear Panel ....................................10 167.33 MHz ...................................7 FastScan Control Tab .......................96
Setup and Installation .....................2 8 kHz RX Out ................................7 Fine Scan .........................................98
A3318 vii, 1, 2, 14, 30, 31, 65, 67, 69, 74, 8 kHz TX In ...................................7 Fit Quality ......................................104
263 Trig Clock Out ...............................7 Front Panel
Setup and Installation .....................2 TX Clock In ...................................7 A3308 ............................................5
Accessories ........................................2 Coarse Scan .....................................99 External Loop ..............................10
Adding a Printer .................................3 Confidence Level .............................95 I/O Connectors ...............................6
Alarm Generation ............................19 Connecting to a LAN .........................2 Laser Control Key .........................7
Anomaly Measurement ....................19 Corr B2 ER ......................................53 Laser Status LED ...........................7
Application Briefs ..........................293 Corr B3 ER ......................................53 Module Address .............................8
Auto BER .........................................83 Corrected Power Out .......................44 Monitor Port ..................................8
Auto Power ......................................83 CV-L ................................................53 OSNR Monitor Port .......................8
CV-MS .............................................53 Power Push Button ........................5
B CV-P .................................................53 Reference Receiver ........................9
B1 (CV-R) ........................................52 CV-R ................................................52 Reference Transmitter ....................8
B1 (CV-S) ........................................52 CV-S .................................................52 RX Input ........................................9
B1 Corr ER ......................................52 RX Out 8 kHz Clock .....................7
B1 Corrected Error Rate ..................52 D Start/Stop .......................................6
B1 Err Rate ......................................52 Debug Station Trig Clock Out ...............................7
B1 Error Rate ...................................52 Application Configuration .........168 TX Clock In ...................................7
B1 Errors (CV-R) .............................52 Hardware Setup .........................167 TX In 8 kHz Clock ........................7
B1 Errors (CV-S) .............................52 Introduction ................................167 TX Lock .........................................9
B2 (CV-L) ........................................53 Running the Application ............172 TX Output ......................................9
B2 (CV-MS) .....................................53 Test Sequence ............................176
B2 Corrected Error Rate ..................53 Troubleshooting .........................179 G
B2 Err Rate ......................................53 Web Results Access ...................180 Glossary of Acronyms ...................345
B2 Error Rate ...................................53 Dispersion Penalty .........................117 GPIB Interface ...............................156
B2 Errors (CV-L) .............................53 Downstream Device selection .........14 GUI
B2 Errors (CV-MS) ..........................53 Administration .............................14
B3 (CV-HP) .....................................53 E BERT Bar ..............................14, 48
B3 Corrected Error Rate ..................53 EDFA ...............................................18 Downstream Device Selection .....14
B3 Err Rate ......................................53 EDFA Bypass Switch .......................41 Help .............................................14
B3 Error Rate ...................................53 E-Mail Configuration .......................72 Laser Status ..................................45
B3 Errors (CV-HP) ..........................53 Emergency Shutoff Power Switch ...12 Modes ..........................................13
B3 Errors (CV-P) .............................53 Enable MPLS .................................137 Out/In Bar ....................................14
bending downwards .........................93 Erbium Doped Fiber Amplifier .......18 Overview .....................................12
BER vs. OSNR .............................. 111 Errors Protocol Status Bar ......................14
BERT Bar ...................................14, 48 SONET/SDH Coding ...................52 Slave Unit Selection ....................14
Audible Error Alarm ....................49 ES-R .................................................53 Status ............................................15
351
Trigger Source ..............................47 Ethernet ..........................................5 Power ...............................................10
RX Input ........................................9 Power Connector .............................12
H TX Lock .........................................9 Power Push Button ............................5
Hardware Safety ..............................44 Power Switch
HDLC ...............................................19 M Emergency ...................................12
Help ..............................................4, 14 M1 (MS-REI) ...................................53 PPP Session .....................................19
Help Desk ..........................................4 M1 (REI-L) ......................................53 Printer ..............................................77
M1 Err Rate .....................................53 Printer Configuration .........................3
I M1 Error Rate ..................................53 Protocol Status Bar ..........................14
Installation .........................................2 M1 Errors (MS-REI) ........................53
Instrument Overview .........................5 M1 Errors (REI-L) ...........................53 R
IntelliPass ...................................84, 85 Magic Number ...............................138 Rear Panel
IntelliPass Mode ..............................92 Maintenance Port .............................12 A3308 ..........................................10
IntelliScript ......................................55 Max Power Out ................................44 Emergency Power Switch ............12
IntelliTime ..................................84, 85 Max-Configure ..............................137 Maintenance Port .........................12
IntelliTime Mode .............................95 Maximum-Receive-Unit ................138 Power ...........................................10
Internal Process Control. ..................65 Max-Terminate ...............................137 Power In .......................................12
Internal Sensitivity ...........................18 Mode Control ...................................89 RJ45 IN ........................................12
Introduction ........................................1 Module Address .................................8 RJ45 OUT ....................................12
IP Monitor Port .......................................8 Safety Interlock ............................12
Traffic Generation ......................140 Monitor Port (Out) ...........................40 Receive from DUT ..........................40
MRU ..............................................138 Reference RX Switch ......................41
J Reference Transmitter ........................8
Jitter Mask ........................................35 O Reference TX Switch .......................41
Optical Overload ......................18, 108 Regenerator Section Errored Seconds (ES-
L Optical Path Penalty ................18, 117 R) .....................................53
LAN Connection ................................2 Optical Sensitivity .....................17, 82 REI-L ...............................................53
Laser Control Key ..............................7 Optical Signal to Noise Ratio Sensitivity Remote Operation ..........................155
Laser Enabled ..................................44 18 Database Access using ODBC ..155
Laser Safety Optics ...............................................32 Generalized Programming Flow
Laser Control Key ..........................7 OSA .................................................58 Example .............................158
Safety Interlock ......................12, 44 OSNR Monitor Port ...........................8 SCPI Control ..............................156
Laser Safety Interlock ......................12 OST System Overview ......................1 Retry Timeout ................................138
Laser Status ......................................45 Other Modes ....................................55 RX Error Monitoring .......................19
Layer 1 OTN Features ...................................20 RX Input ............................................9
BER vs. OSNR .................... 18, 111 OTN Tests ......................................143 RX Operations .................................48
Optical Overload ..................18, 108 Statistics and Error Monitoring ..144 RX Tests .....................................17, 81
Optical Path Penalty ...................117 Transmit Features .......................145 BER vs. OSNR .......................... 111
Optical Sensitivity ........................82 TX and RX Statistics .................146 BER vs.OSNR .............................18
Path Penalty .................................18 TX Error Generation ..................145 Optical Overload ..........................18
RX Tests .......................................17 OTN Traffic Configuration ......27, 143 Optical Sensitivity .......................17
SensitivityTests ............................17 Out/In Bar ........................................14 Overload ....................................108
Tests Output Power Setup .........................45 Sensitivity ....................................82
TX Power ...................................122 Overhead Generation .......................19
Layer 2 S
Alarm Generation ........................19 P Safety Interlock ..........................12, 44
Anomaly Measurement ........19, 128 Pass Criteria ...................................104 SCPI Command Set ...............183, 263
Error Generation ..........................19 Path In ..............................................40 SCPI Commands ............183, 263, 277
Overhead Generation ...................19 Path Out ...........................................40 SCPI Return Codes ........................259
Receive Features ..........................19 Path Penalty .....................................10 Scrambling .....................................137
RX Error Monitoring ...................19 Physical Layer SDH
SONET/SDH Features See Layer 1 see SONET/SDH
Transmit Features .........................19 PoS .................................................137 Section Errored Seconds (ES-S) ......53
Layer 3 PoS Error Injection Control ...........141 Secured-Accuracy™ ........................65
10GE LAN Traffic .......................23 PoS Features ....................................19 SelfTest ............................................66
10GE WAN Traffic ......................27 Pos Statistics ..................................140 SEQBRK .....................49, 54, 86, 348
IP Traffic ....................................140 PoS Tests ........................................137 Setup ..................................................2
OTN Traffic .................................27 Magic Number ...........................138 Shut Down .......................................73
PoS ...............................................19 Max-Configure ..........................137 Signal Configuration ........................21
PoS Traffic .................................140 Max-Terminate ...........................137 Signal to Noise Ratio Sensitivity .....18
SONET/SDH Traffic ....................23 MRU ..........................................138 Slave Unit Selection ........................14
LED Retry Timeout ............................138 SONET/SDH
A/B Event ......................................6 Traffic Generation ......................140 Coding Errors ..............................52
352
Features ........................................19 T Troubleshooting
Receive Features ..........................19 Technical Briefs .............................321 Debug Station ............................179
Traffic Configuration ...................23 Testing 1310 nm Devices .................20 TX and RX Statistics
Transmit Features .........................19 Touch Screen Interface ....................12 OTN ...........................................146
TX Error Generation ....................19 Traffic Configuration .......................21 TX Clock In .......................................7
SONET/SDH Tests ........................125 10GE LAN ...................................23 TX Error Generation ................19, 145
Anomaly Measurement ..............128 10GE WAN ..................................27 TX Lock .............................................9
SONET Statistics & Error Injection Bitstream ......................................22 TX Output ..........................................9
130 Optics ...........................................32 TX Power .......................................122
Transmit Features .......................125 SONET/SDH ...............................23 TX Tests ................................... 18, 117
Start/Stop, I/O ....................................6 Stressed Eye .................................32 DUT TX Power ...................19, 122
Statistics and Error Monitoring Traffic Generation Internal Sensitivity .......................18
OTN ...........................................144 IP ................................................140 Path Penalty ......................... 18, 117
Status ................................................15 OTN .............................................27 TX/RX Bar ......................................44
Step Scan ........................................100 PoS .............................................140
Stressed Eye .....................................32 Transmit Features U
Stressed Receiver Conformance Test 35 OTN ...........................................145 Uncertainty ....................................102
Support ...............................................4 SONET/SDH .............................125
Switch Setup ....................................36 TRANSMIT TO DUT ...................112 W
Trig Clock Out ...................................7 Warranty ...........................................iii
Trigger Source .................................47
353
354

OST User Manual

Загружено:

Сведения о документе

Оригинальное название

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

OST User Manual

Загружено:

Авторское право:

Доступные форматы

10 Gb/s Optical Standards Test System

User’s / Programmer’s Manual

August 15, 2005

Circadiant Systems, Inc.

Printed in the USA.

Disclaimer of Warranties. THE WARRANTY EXPRESSLY STATED IN THIS AGREEMENT IS

CAUTION: This unit is not a handheld instrument.

CAUTION: This unit is for indoor use only.

FBPT-SC-FK- Modified SC Bulkhead Adapter Probe Tip

FMA-U25 - Universal 2.5 mm Adapter Probe Tip

Chapter 2: Instrument Overview ........................................................5

Chapter 3: Signal Configuration .......................................................21

Chapter 4: Other Modes ....................................................................55

Chapter 5: RX Tests ..........................................................................81

Chapter 6: TX Tests ........................................................................117

Chapter 7: SONET/SDH Tests .......................................................125

Chapter 8: PoS Tests .......................................................................137

Chapter 9: OTN Tests .....................................................................143

Chapter 10: 10GE LAN/WAN Tests ..............................................147

Chapter 11: Remote Operation .......................................................155

Chapter 12: Debug Station ..............................................................167

Chapter 14: Quick Start Guides ......................................................263

Chapter 15: Procedures ...................................................................277

Chapter 16: Application Briefs .......................................................293

Chapter 17: Technical Briefs ..........................................................321

Chapter 18: Glossary of Acronyms ................................................345

Index .............................................................................................. 357

1.1 Product Overview

1.3 A3308 10 Gb/s Optical Standards Tester Setup and

1.4 A3318 850 nm/Electrical OST Interface Setup and

1.5 Connecting to a LAN

FIGURE 1-1: 10 Gb/s OST System Connected to a LAN

1.6 Printer Configuration

2.1 A3308 10 Gb/s Optical Standards Tester Front Panel

FIGURE 2-1: Front Panel of the A3308

4. 1 Hz Clock Connectors. Reserved for future expansion.

2.2 A3308 10 Gb/s Optical Standards Tester Rear Panel

FIGURE 2-2: Rear Panel of the A3308

CAUTION: Do not apply voltage to the Laser Safety Interlock port.

2.3 A3308 10 Gb/s Optical Standards Tester Touch Screen

FIGURE 2-3: Sample GUI Screenshot

2.4 A3318 850 nm/Electrical OST Interface Front Panel

FIGURE 2-4: Front Panel of the A3318

2.5 A3318 850 nm/Electrical OST Interface Rear Panel

FIGURE 2-5: Rear Panel of the A3318

2.6 Layer 1 Tests

2.7 SONET/SDH Features

Transmit Features include:

Receive Features include:

2.8 10 GE LAN/WAN Features

2.9 PoS Features

2.10 OTN Features

2.11 Testing 1310 nm Devices

Traffic Type Wavelength

FIGURE 2-6: TX/RX Bar

3.1 Traffic Configuration

FIGURE 3-1: Bitstream Data Traffic Configuration

3.1.2 10GE LAN

FIGURE 3-2: 10GE LAN Protocol Error Bar

10GE Acronyms Error

FIGURE 3-3: Overhead Setup

SONET Acronym Error

FIGURE 3-4: SONET/SDH Error Bar