User Guide OTDR OTDR Series for FTB-500
Copyright © 1997–2011 EXFO Inc. All rights reserved. No part of this publication may be reproduced, stored in a retrieval system or transmitted in any form, be it electronically, mechanically, or by any other means such as photocopying, recording or otherwise, without the prior written permission of EXFO Inc. (EXFO). Information provided by EXFO is believed to be accurate and reliable.
Contents Contents Certification Information ..................................................................................................... viii 1 Introducing the Optical Time Domain Reflectometer ................................ 1 Main Features .........................................................................................................................3 Trace Acquisition Modes .........................................................................................................
Contents 6 Testing Fibers in Advanced Mode ..............................................................63 Setting the Autorange Acquisition Time ...............................................................................68 Setting the IOR, RBS Coefficient, and Helix Factor ................................................................69 Setting Distance Range, Pulse Width, and Acquisition Time .................................................71 Enabling the High-Resolution Feature .................
Contents 9 Analyzing Traces and Events ................................................................... 129 Trace Display and Events Table Description .........................................................................130 Event Pane .........................................................................................................................131 Measure Pane .....................................................................................................................
Contents 12 Creating and Printing Trace Reports .......................................................207 Adding Information to the Test Results ...............................................................................207 Customizing the Report ......................................................................................................212 Printing a Report ...............................................................................................................
Contents A Technical Specifications ........................................................................... 287 B Description of Event Types ...................................................................... 293 Span Start ..........................................................................................................................294 Span End ...........................................................................................................................294 Short Fibers .....
Certification Information Certification Information FCC Information Electronic test equipment is exempt from Part 15 compliance (FCC) in the United States. However, compliance verification tests are systematically performed on most EXFO equipment. Information Electronic test equipment is subject to the EMC Directive in the European Union. The EN61326 standard prescribes both emission and immunity requirements for laboratory, measurement, and control equipment.
Certification Information DECLARATION OF CONFORMITY Application of Council Directive(s): Manufacturer’s Name: Manufacturer’s Address: Equipment Type/Environment: Trade Name/Model No.: 2006/95/EC - The Low Voltage Directive 2004/108/EC - The EMC Directive 2006/66/EC - The Battery Directive 93/68/EEC - CE Marking And their amendments EXFO Inc.
Certification Information DECLARATION OF CONFORMITY Application of Council Directive(s): Manufacturer’s Name: Manufacturer’s Address: Equipment Type/Environment: Trade Name/Model No.: 2006/95/EC - The Low Voltage Directive 2004/108/EC - The EMC Directive 2006/66/EC - The Battery Directive 93/68/EEC - CE Marking And their amendments EXFO Inc.
Certification Information DECLARATION OF CONFORMITY Application of Council Directive(s): Manufacturer’s Name: Manufacturer’s Address: Equipment Type/Environment: Trade Name/Model No.: 2006/95/EC - The Low Voltage Directive 2004/108/EC - The EMC Directive 2006/66/EC - The Battery Directive 93/68/EEC - CE Marking And their amendments EXFO Inc.
Certification Information DECLARATION OF CONFORMITY Application of Council Directive(s): Manufacturer’s Name: Manufacturer’s Address: Equipment Type/Environment: Trade Name/Model No.: 2006/95/EC - The Low Voltage Directive 2004/108/EC - The EMC Directive 2006/66/EC - The Battery Directive 93/68/EEC - CE Marking And their amendments EXFO Inc.
Certification Information DECLARATION OF CONFORMITY Application of Council Directive(s): Manufacturer’s Name: Manufacturer’s Address: Equipment Type/Environment: Trade Name/Model No.: 2006/95/EC - The Low Voltage Directive 2004/108/EC - The EMC Directive 2006/66/EC - The Battery Directive 93/68/EEC - CE Marking And their amendments EXFO Inc.
1 Introducing the Optical Time Domain Reflectometer The Optical Time Domain Reflectometer allows you to characterize a fiber-optic span, usually optical fiber sections joined by splices and connectors. The optical time domain reflectometer (OTDR) provides an inside view of the fiber, and can calculate fiber length, attenuation, breaks, total return loss, and splice, connector and total losses.
Introducing the Optical Time Domain Reflectometer OTDR Visual fault locator (VFL) port (optional) Handle OTDR port (singlemode or multimode) Other models 2 OTDR
Introducing the Optical Time Domain Reflectometer Main Features Main Features The OTDR: OTDR ³ Can be used with the FTB-500 (refer to the FTB-500 user guide) and the FTB-200 v2 Compact Modular Platform (refer to the FTB-200 v2 user guide). ³ Offers impressive dynamic range with short dead zones. ³ Performs quick acquisitions with low noise levels to enable accurate low-loss splice location. ³ Acquires OTDR traces made of up to 256 000 points that provide a sampling resolution as fine as 4 cm.
Introducing the Optical Time Domain Reflectometer Trace Acquisition Modes Trace Acquisition Modes The OTDR application provides the following trace acquisition modes: ³ Auto: Automatically calculates fiber length, sets acquisition parameters, acquires traces, and displays event tables and acquired traces. ³ Advanced: Offers all the tools needed to perform integral OTDR tests and measurements and gives you control over all test parameters.
Introducing the Optical Time Domain Reflectometer Available OTDR Models OTDR Models Description Singlemode ³ 1310 nm and 1550 nm. FTB-7200D-B ³ 35 dB dynamic range and 1 m event dead zone, useful to locate closely spaced events. ³ High-resolution feature to obtain more data points per acquisition. Data points will be closer to each other, resulting in a greater distance resolution for the trace.
Introducing the Optical Time Domain Reflectometer Available OTDR Models OTDR Models Singlemode FTB-7400E-XXXXB Description ³ Attenuation dead zone of 4 m for pinpoint event location ³ Up to 40 dB dynamic range with 0.8 m event dead zone. ³ Acquires up to 256 000 data points while sampling a single trace. ³ Up to four test wavelengths (1310 nm, 1383 nm, 1550 nm,1625 nm) for CWDM and DWDM link characterization Singlemode FTB-7500E-XXXXB ³ Event dead zone of 0.
Introducing the Optical Time Domain Reflectometer OTDR Basic Principles OTDR Basic Principles An OTDR sends short pulses of light into a fiber. Light scattering occurs in the fiber due to discontinuities such as connectors, splices, bends, and faults. An OTDR then detects and analyzes the backscattered signals. The signal strength is measured for specific intervals of time and is used to characterize events.
Introducing the Optical Time Domain Reflectometer OTDR Basic Principles An OTDR uses the effects of Rayleigh scattering and Fresnel reflection to measure the fiber’s condition, but the Fresnel reflection is tens of thousands of times greater in power level than the backscatter. ³ Rayleigh scattering occurs when a pulse travels down the fiber and small variations in the material, such as variations and discontinuities in the index of refraction, cause light to be scattered in all directions.
Introducing the Optical Time Domain Reflectometer Conventions Conventions Before using the product described in this manual, you should understand the following conventions: WARNING Indicates a potentially hazardous situation which, if not avoided, could result in death or serious injury. Do not proceed unless you understand and meet the required conditions. CAUTION Indicates a potentially hazardous situation which, if not avoided, may result in minor or moderate injury.
2 Safety Information WARNING Do not install or terminate fibers while a light source is active. Never look directly into a live fiber and ensure that your eyes are protected at all times. WARNING Use of controls, adjustments and procedures for operation and maintenance other than those specified herein may result in hazardous radiation exposure or impair the protection provided by this unit.
Safety Information Laser Safety Information (Models with VFL) Laser Safety Information (Models with VFL) Your instrument is a Class 3R laser product in compliance with standards IEC 60825-1 and 21 CFR 1040.10. It is potentially harmful in direct intrabeam viewing.
3 Getting Started with Your OTDR Inserting and Removing Test Modules CAUTION Never insert or remove a module while the FTB-500 is turned on. This will result in immediate and irreparable damage to both the module and unit. WARNING When the laser safety LED ( ) is flashing on the FTB-500, at least one of your modules is emitting an optical signal. Please check all modules, as it might not be the one you are currently using. To insert a module into the FTB-500: 1. Exit ToolBox and turn off your unit. 2.
Getting Started with Your OTDR Inserting and Removing Test Modules ³ (4-slot model) identification sticker must be on left side and retaining screw hole under connector pins. Identification sticker on left side Connector pins at the back Retaining screw hole at the back FTB-500 right panel ³ Protruding edges on right side (eight-slot model) identification sticker must be facing up and connector pins at the right of the retaining screw hole.
Getting Started with Your OTDR Inserting and Removing Test Modules Note: If you are using larger or heavier modules, place them near the bottom of the unit as much as possible. 4. Insert the protruding edges of the module into the grooves of the receptacle’s module slot. 5. Push the module all the way to the back of the slot, until the retaining screw makes contact with the receptacle casing. 6. Place the FTB-500 so that its left panel is facing you.
Getting Started with Your OTDR Inserting and Removing Test Modules 7. While applying slight pressure to the module, turn the retaining screw clockwise until it is tightened. This will secure the module into its “seated” position.
Getting Started with Your OTDR Inserting and Removing Test Modules 8. If you are using a larger or heavier module, use a front module lock to hold them securely in place. Simply place the retaining part against the module, then screw in the holding pin. When you turn on the unit, the startup sequence will automatically detect the module.
Getting Started with Your OTDR Inserting and Removing Test Modules To remove a module from the FTB-500: 1. Exit ToolBox and turn off your unit. 2. Position the FTB-500 so that the left panel is facing you. 3. Turn the retaining screw counterclockwise until it stops. The module will be slowly released from the slot. Turn retaining screw knob(s) counterclockwise FTB-500 left panel 4. Place the FTB-500 so that the right panel is facing you.
Getting Started with Your OTDR Inserting and Removing Test Modules 5. Hold the module by its sides or by the handle (NOT by the connector) and pull it out. 6. Cover empty slots with the supplied protective covers. CAUTION Failure to reinstall protective covers over empty slots will result in ventilation problems.
Starting the OTDR Application Starting the OTDR Application Your Optical Time Domain Reflectometer module can be configured and controlled from its dedicated ToolBox application. Note: For details about ToolBox, refer to the FTB-500 user guide. To start the application: 1. From the main window, select the module to use. It will turn blue to indicate that it is highlighted. Selected module 2. Click the corresponding button in the Module Applications box.
Starting the OTDR Application The main window (shown below) contains all the commands required to control the OTDR: Title bar Data display Split bar Button bar Control Center Status bar The main window will differ from the illustration above if you opened traces the last time you worked with the OTDR.
Starting the OTDR Application Split Bar A split bar divides the data display and Control Center. You can drag it up or down to obtain a larger view of the graph or table display. Status Bar The status bar, located at the bottom of the main window, identifies the operational status of the Optical Time Domain Reflectometer. Control mode Local: Module controlled locally only. Remote: Module controlled remotely, but local commands can also be used (some products only).
Timer Timer Once the acquisition has begun, a timer is displayed on the status bar, indicating the remaining time until the next acquisition. Time dial Timer ³ If you increase the time on the Time dial during the acquisition, the timer will adjust the countdown accordingly. ³ If you modify the value on the Distance or Pulse dial during the acquisition, the timer is reset. Exiting the Application Closing any application that is not currently being used helps freeing system memory.
4 Setting Up Your OTDR Installing the EXFO Universal Interface (EUI) The EUI fixed baseplate is available for connectors with angled (APC) or non-angled (UPC) polishing. A green border around the baseplate indicates that it is for APC-type connectors. Green border indicates APC option Bare metal (or blue border) indicates UPC option To install an EUI connector adapter onto the EUI baseplate: 1. Hold the EUI connector adapter so the dust cap opens downwards. 2 3 4 2.
Setting Up Your OTDR Cleaning and Connecting Optical Fibers Cleaning and Connecting Optical Fibers IMPORTANT To ensure maximum power and to avoid erroneous readings: ³ Always inspect fiber ends and make sure that they are clean as explained below before inserting them into the port. EXFO is not responsible for damage or errors caused by bad fiber cleaning or handling. ³ Ensure that your patchcord has appropriate connectors. Joining mismatched connectors will damage the ferrules.
Setting Up Your OTDR Cleaning and Connecting Optical Fibers 3. Carefully align the connector and port to prevent the fiber end from touching the outside of the port or rubbing against other surfaces. If your connector features a key, ensure that it is fully fitted into the port’s corresponding notch. 4. Push the connector in so that the fiber-optic cable is firmly in place, thus ensuring adequate contact.
Setting Up Your OTDR Defining Cables Defining Cables You can specify the way cables and fibers will be identified and add comments about the tests you perform. You can include this information in reports later. To speed up information entry, you can define cable profiles. For each new test, the application will use the active cable profile to fill out the boxes, preventing you from entering repetitive information.
Setting Up Your OTDR Defining Cables Defining a Cable Name or Identifier You can define a cable name or identifier for your cable. You can also modify existing names and delete them as needed. To define the cable name or identifier: 1. From the main window, press Setup. 2. From the Setup dialog box, select the Cable tab. 3. Press the button next to the Cable ID box. 4. Select a name from the list, or type the desired name in the upper box.
Setting Up Your OTDR Defining Cables Defining the Cable Location You can specify where ends A and B of your cable are located. You can also swap A and B locations, which is useful when you perform bidirectional tests using the same hardware for both directions. You can modify already defined locations or delete them as needed. To define the cable location: 1. From the main window, press Setup. 2. From the Setup dialog box, select the Cable tab.
Setting Up Your OTDR Defining Cables 3. Enter the desired location: 3a. From the appropriate Locations box (A or B), type the location directly. OR Press the button next to the A (or B) box. 3b. Select a location from the list, or type the name in the upper box. To transfer location to the list To remove location from the list 4. Press OK to confirm your selection. The selected name becomes the current cable name. 5. Repeat the same procedure for Location B. 6.
Setting Up Your OTDR Defining Cables Defining Subset (or Fiber) Names You can define the way subsets, such as buffer tubes or fiber ribbons, will be identified. You can also define your own fiber name or identifier using the same method. Each time you launch an acquisition, the subset and fiber names will change according to a pattern you will have previously defined. These names are made of a static part (alphanumeric) and a variable part (numeric).
Setting Up Your OTDR Defining Cables Before incrementing the subset's variable part, the application must process all fibers in the subset. Example: ³ Subset 1 - Fiber 1 ³ Subset 1 - Fiber 2 ³ Subset 1 - Fiber... ³ Subset 2 - Fiber 1 ³ ... Note: If you also want to identify your fiber with a color code, see Identifying Fibers with Colors on page 36.
Setting Up Your OTDR Defining Cables To define the subset or fiber name: 1. From the main window, press Setup. 2. From the Setup dialog box, select the Cable tab. 3. Press the button next to the Subset ID box, then select the Use Subset box. OR Press the 34 button next to the Fiber ID box.
Setting Up Your OTDR Defining Cables 4. Set the various parameters according to your needs. Static part Variable part (incremented) identification will be used in the next subset (or fiber) name. Number of digits composing the subset variable part Incrementation type Incrementation behavior (to build the variable part). Ensure that the value composing the variable part corresponds to the number that should appear in the next subset or fiber name. 5. Press OK to confirm your selection.
Setting Up Your OTDR Defining Cables Identifying Fibers with Colors In addition to defining a custom name for your fibers, you can also add a color, based on the default ITU color code or on your own color codes. A color code consists of a set of colors identified by a name and an abbreviation. For each color code, the application displays a color table showing the full and abbreviated color names as well as a number indicating the sequential order of these colors in the code.
Setting Up Your OTDR Defining Cables 3. Press the button next to the Color ID box. 4. From the Color Code In Use list, select a color code. OR Select None if you prefer not to use color information. For information on how to create your own color codes, see the corresponding procedure on page 43. 5. Under Color Identification, select your preference between the Full Name of the color, or its Abbreviation. 6. Press OK to confirm.
Setting Up Your OTDR Defining Cables To create a custom color code: 1. From the main window, press Setup. 2. From the Setup dialog box, select the Cable tab. 3. Press the button next to the Color ID box. 4. From the Color Setup dialog box, press New Code. 5. In the Color Name field, enter a color name. 6. Press OK. You return to the Color Setup dialog box. The added color code is displayed in the Color Code in Use list. The color table is empty. You must add color names to the new color code.
Setting Up Your OTDR Defining Cables To delete a color code: 1. From the Color Setup dialog box, in the Color Code in Use list, select the color code to delete. 2. Press Delete Code. 3. In the confirmation dialog box, press Yes. You return to the Color Setup dialog box. To export color codes: 1. From the Color Setup dialog box, press Export Code(s). 2. From the Export Following Code(s) list, select the all the boxes corresponding to the color codes to export in the .clr file. 3. Press Export.
Setting Up Your OTDR Defining Cables 4. If necessary, from the list of drives and folders, select a storage location. Current storage location 5. In the Filename box, enter the name you want to use for the file that will contain all the exported color codes. 6. Press OK. 7. Press OK one more time to acknowledge the confirmation message. You return to the Color Setup dialog box. Note: By default, exported color code lists are saved in the ColorCode folder.
Setting Up Your OTDR Defining Cables To import color codes: 1. From the unit/computer on which you want to import color codes, open the Color Setup dialog box and press Import Code(s). 2. In the Import Color Code dialog box, select the .clr file (containing the list of color codes) you want to import. 3. Press OK. Note: By default, this dialog box opens in the ColorCode folder. The factory default path is D:\ToolBox\User Files\OTDR\ColorCode.
Setting Up Your OTDR Defining Cables 4. From the Import Color Code dialog box, in the Code(s) to Import list, select the boxes corresponding to the desired color codes. 5. Press Import. 6. Press OK to acknowledge the confirmation message. You return to the Color Setup dialog box. Note: To use one of the newly imported color codes, you must select it manually.
Setting Up Your OTDR Defining Cables To add a color to a code: 1. From the Color Setup dialog box, in the Color Code in Use list, select the color code to which you want to add a color, and press Add Color. 2. From the New Color dialog box, enter the desired information. 3. Press OK. You return to the Color Setup dialog box. The added color is displayed as the last item in the color table. Note: To insert a new color between existing colors, use the Insert Color function described below.
Setting Up Your OTDR Defining Cables To modify a color name: 1. From the Color Setup dialog box, in the Color Code In Use list, select the color code you want to modify. 2. In the color table, select the color you want to modify, and press Modify Color. 3. From the Modify Color dialog box, enter the desired information. 4. Press OK. You return to the Color Setup dialog box. To delete a color: 1. From the Color Setup dialog box, in the Color Code In Use list, select the color code you want to modify. 2.
Setting Up Your OTDR Defining Cables Entering Cable Manufacturer Information You can enter information such as the manufacturer of the cable that houses the fiber being tested. To enter cable manufacturer information: 1. From the main window, press Setup. 2. From the Setup dialog box, select the Cable tab. 3. In the Cable Mfr. box, enter the desired information. 4. Press Apply to confirm the changes, then OK to return to the main window.
Setting Up Your OTDR Defining Cables Entering Fiber Type Information You can enter information such as the type of fiber being tested. To enter fiber type information: 1. From the main window, press Setup. 2. From the Setup dialog box, select the Cable tab. 3. In the Fiber Type box, enter the desired information. 4. Press Apply to confirm the changes, then OK to return to the main window.
Setting Up Your OTDR Defining Cables Entering Job Information and Comments You can enter job information such as the name of the job and other useful information that will be saved with all new traces. To enter job information: 1. From the main window, press Setup. 2. From the Setup dialog box, select the Cable tab. 3. Press the Job and Comments button.
Setting Up Your OTDR Defining Cables 4. From the Job and Comments dialog box, enter information in the appropriate boxes. You can use to add those entries to a list; if you use them often, doing so will make them easier to recall. 5. When all the information has been entered in the Job and Comments dialog box, press Close to save the information. 6. Press Apply to confirm the changes, then OK to return to the main window.
Setting Up Your OTDR Defining Cables Reverting to Default Cable Parameters You can clear the information appearing in the Cable tab and revert to default cable parameters. To revert to default values: 1. From the main window, press Setup. 2. From the Setup dialog box, select the Cable tab. 3. Press the Default button. 4. Press Apply to confirm the changes, then OK to return to the main window.
Setting Up Your OTDR Naming Trace Files Automatically Naming Trace Files Automatically Note: The autonaming feature is not available in “offline” mode. When you activate the automatic file naming function, the application builds a file name according to your specifications each time you start an acquisition. You can specify the information you want to include in the file names and in which order each item should appear.
Setting Up Your OTDR Naming Trace Files Automatically To view the current file name structure: From the main window, press Setup. The current file naming scheme is displayed to the right of the Filename box. To configure the automatic file naming: 1. From the button bar, press Setup. 2. From the Setup dialog box, press the Cable tab. 3. Press the button appearing next to the Filename box to open the File Autonaming dialog box.
Setting Up Your OTDR Naming Trace Files Automatically 4. Select the Use File Autonaming box to be able to set the file autonaming parameters. To modify the order of appearance of the selected components in the file name Items that can be included in the file name To select the test direction To add your own information Item that will separate the selected components ³ Filename Components, select the boxes corresponding to the information you wish to include in your file names.
Setting Up Your OTDR Naming Trace Files Automatically ³ You can include information about the test direction by selecting the desired option. ³ You can also add a static name that will always appear in the file name by entering it in the Custom box. The items will appear in the same order they are listed (from top to bottom). The first selected item will become the first item in the file name, the second selected item will become the second item in the file name, etc. 5.
Setting Up Your OTDR Enabling or Disabling the First Connector Check Enabling or Disabling the First Connector Check The first connector check feature is used to verify that the fibers are properly connected to the OTDR. It verifies the injection level and displays a message when an unusually high loss occurs at the first connection, which could indicate that no fiber is connected to the OTDR port. By default, this feature is not enabled.
Setting Up Your OTDR Launch Conditions for Multimode Measurements Launch Conditions for Multimode Measurements In a multimode fiber network, the attenuation of a signal is highly dependent on the mode distribution (or launch condition) of the source that emits this signal. In the same way, the attenuation reading performed by any test instrument will also depend on the mode distribution of its light source. A single light source cannot be conditioned for both 50 μm (50 MMF) and 62.5 μm (62.
Setting Up Your OTDR Launch Conditions for Multimode Measurements The table below gives information about tests with the 50 μm and 62.5 μm fibers. Fiber type 50 μm Recommended mode filter Perform a five-turn mandrel-wrap (wrapping the patchcord a minimum of five turns around the mandrel tool) on the patchcord connecting the OTDR to the fiber under test. As per FOTP-34: Remarks Nominal launch conditions are overfilled.
5 Testing Fibers in Auto Mode Auto mode automatically evaluates fiber length, sets acquisition parameters, acquires traces, and displays event tables and acquired traces. You can select an option that will allow you to modify fiber settings (IOR also known as group index, RBS coefficient, and helix factor) or analysis detection thresholds (splice loss, reflectance, and end-of-fiber detection) once the test is complete. For more information, see Viewing and Modifying Current Trace Settings on page 153.
Testing Fibers in Auto Mode Once the acquisition is complete or interrupted, the analysis starts for acquisitions of 5 seconds or more. After analysis, the trace is displayed and events appear in the events table. For more information, see Analyzing Traces and Events on page 129.
Testing Fibers in Auto Mode To acquire traces in Auto mode: 1. Clean the connectors properly (see Cleaning and Connecting Optical Fibers on page 26). 2. Connect a fiber to the OTDR port. If your unit is equipped with two OTDR ports, ensure that you connect the fiber to the appropriate port (singlemode, singlemode live, or multimode), depending on the wavelength you intend to use. CAUTION Never connect a live fiber to the OTDR port without a proper setup.
Testing Fibers in Auto Mode 4. Select the Auto mode. 4a. From the main window, press Setup then select the Mode tab. 4b. Under Mode, select Auto. ³ If you want to edit fiber settings after the test, select the Enable Editing for Current Trace Settings box. Clear the box if you prefer not to edit the settings. ³ If you always want to start in Auto mode, select the corresponding box. Clear the box if you prefer to select the test mode yourself. 4c.
Testing Fibers in Auto Mode 7. Select the boxes corresponding to the desired test wavelengths. You must select at least one wavelength. 8. If you want to clear the settings the OTDR has determined to start with a new set of OTDR settings, press Reset OTDR Settings. 9. Press Start. If the first connector check feature is enabled, a message will appear if there is a problem with the injection level (see Enabling or Disabling the First Connector Check on page 54). 10.
6 Testing Fibers in Advanced Mode Advanced mode offers all the tools you need to perform complete OTDR tests and measurements manually and gives you control over all test parameters. Note: Most parameters can only be set if you select Advanced mode first. Once you have finished selecting your settings, you can simply return to the test mode you prefer. By default, in Advanced mode, all available test wavelengths are selected.
Testing Fibers in Advanced Mode Although the application sets the acquisition parameters, you can modify these values as needed, even while the acquisition is in progress. The OTDR simply restarts the averaging each time a modification is made. Note: You can interrupt the acquisition at any time. The application will display the information acquired to that point. Once the acquisition is complete or interrupted, the analysis starts for acquisitions of 5 seconds or more.
Testing Fibers in Advanced Mode You can save the trace after analysis. If former results have not been saved yet, the application prompts you to save them before starting a new acquisition. To acquire traces: 1. Clean the connectors properly (see Cleaning and Connecting Optical Fibers on page 26). 2. Connect a fiber to the OTDR port.
Testing Fibers in Advanced Mode 3. Select Advanced mode. 3a. From the main window, press Setup then select the Mode tab. 3b. Under Mode, select Advanced. IMPORTANT Press Apply to ensure the Advanced mode is activated. Otherwise, the tabs containing the parameters you can set will remain hidden. 3c. Press Apply, then OK. 4. If you want the application to provide automatic acquisition values, set the autorange acquisition time (see Setting the Autorange Acquisition Time on page 68). 5.
Testing Fibers in Advanced Mode 8. If your OTDR supports singlemode, singlemode live, or multimode wavelengths, under Wavelengths, from the list, select the desired fiber type (for live-fiber testing, select SM Live; for C fiber, select 50 μm and for D fiber, select 62.5 μm). 9 8 9. Select the boxes corresponding to the desired test wavelengths. You must select at least one wavelength. 10. Select the desired distance, pulse, and time values.
Testing Fibers in Advanced Mode Setting the Autorange Acquisition Time Setting the Autorange Acquisition Time When performing automatic acquisitions in Advanced mode (see Testing Fibers in Advanced Mode on page 63) or before activating Auto mode (see Testing Fibers in Auto Mode on page 57), you can set an autorange acquisition time for the OTDR to average acquisitions over a set time period. The application uses this value to determine the best settings for the test.
Testing Fibers in Advanced Mode Setting the IOR, RBS Coefficient, and Helix Factor Setting the IOR, RBS Coefficient, and Helix Factor You should set the IOR (group index), RBS coefficient and helix factor before performing tests in order to apply them to all newly acquired traces. However, you can also set them at a later time in the Trace Info pane to reanalyze a specific trace (see Viewing and Modifying Current Trace Settings on page 153).
Testing Fibers in Advanced Mode Setting the IOR, RBS Coefficient, and Helix Factor By setting the helix factor, the length of the OTDR distance axis is always equivalent to the physical length of the cable (not the fiber). To set the IOR, RBS, and helix factor parameters: 1. From the main window, press the Setup button. 2. From the Setup window, go to the Acquisition tab. 3. Under Fiber Settings, from the Wavelength(s) list, select the wavelength you want to use to set IOR and RBS.
Testing Fibers in Advanced Mode Setting Distance Range, Pulse Width, and Acquisition Time Setting Distance Range, Pulse Width, and Acquisition Time The distance range, pulse width and acquisition time are set with the controls in the Advanced main window. ³ Distance: corresponds to the distance range of the fiber span to be tested according to the selected measurement units (see Selecting the Distance Units on page 116).
Testing Fibers in Advanced Mode Setting Distance Range, Pulse Width, and Acquisition Time ³ Time: corresponds to the acquisition duration (period during which results will be averaged). Generally, longer acquisition times generate cleaner traces (this is especially true with long-distance traces) because as the acquisition time increases, more of the noise is averaged out. This averaging increases the signal-to-noise ratio (SNR) and the OTDR’s ability to detect small events.
Testing Fibers in Advanced Mode Setting Distance Range, Pulse Width, and Acquisition Time To set the parameters: From the OTDR pane: ³ Press the dial corresponding to the parameter you wish to set (the selection marker will move clockwise). OR ³ Press directly the value to select it. The selection marker will go to that value immediately. Selection marker Parameters setting dials If you want the application to provide automatic acquisition values, move at least one dial to the Auto position.
Testing Fibers in Advanced Mode Enabling the High-Resolution Feature Enabling the High-Resolution Feature If your OTDR model is FTB-7000D or later, You can select the high-resolution feature to obtain more data points per acquisition. This way, the data points will be closer to each other, which will result in a greater distance resolution for the trace.
Testing Fibers in Advanced Mode Enabling the High-Resolution Feature To enable the high-resolution feature: From the main window, select the OTDR pane.Select the High-Resolution Acquisition box. Note: If your OTDR supports singlemode, singlemode live, or multimode wavelengths, the high-resolution feature will be activated either for the singlemode, singlemode live, or multimode wavelengths, depending on the selected fiber type.
Testing Fibers in Advanced Mode Enabling or Disabling Analysis After Acquisition Enabling or Disabling Analysis After Acquisition The OTDR trace acquisition procedure will be completed by the analysis. You can either choose to automatically analyze each trace immediately after the acquisition, or perform the analysis whenever it suits you best. When the analysis process is disabled, the Event table of a newly acquired trace will be empty.
Testing Fibers in Advanced Mode Enabling or Disabling Analysis After Acquisition To enable or disable the analysis after trace acquisition: 1. From the main window, press Setup. 2. Go to the Acquisition tab. 3. If you want the OTDR to automatically analyze an acquired trace, select the Analyze After Acquisition box. If you clear the check box, the trace will be acquired without being analyzed. 4. Press Apply to confirm and OK to return to the main window.
Testing Fibers in Advanced Mode Setting Pass/Fail Thresholds Setting Pass/Fail Thresholds You can activate and set Pass/Fail threshold parameters for your tests. You can set thresholds for splice loss, connector loss, reflectance, fiber section attenuation, span loss, span length, and span ORL. You can apply the same pass/fail thresholds to all test wavelengths or apply them separately to each one. You can set different pass/fail thresholds for each available test wavelength.
Testing Fibers in Advanced Mode Setting Pass/Fail Thresholds The following table provides the default, minimum and maximum thresholds. Test Default Minimum Maximum Splice loss (dB) 0.500 0.015 5.000 Connector loss (dB) 1.000 0.015 5.000 Reflectance (dB) –40.00 –80.00 0.00 0.40 0.00 5.000 45.000 0.000 45.000 Span length (km) 0.00 0.0000 300.0000 Span ORL (dB) 15.00 15.00 40.
Testing Fibers in Advanced Mode Setting Pass/Fail Thresholds To set pass/fail thresholds: 1. From the main window, select Setup, then select the Thresholds tab. 2. Under Pass/Fail Thresholds, select the Fail and/or Warning boxes to enable the fail and warning thresholds boxes, respectively. 2 3 Threshold to set Values associated with the threshold to set Note: You must select the Fail box if you want the application to identify the faults in the Event table. 3.
Testing Fibers in Advanced Mode Setting Pass/Fail Thresholds 4. Select the wavelength to which you want to apply the thresholds: ³ To apply the same pass/fail thresholds setup to trace acquisitions performed at all wavelengths, press the Apply Settings to All Wavelengths button. OR ³ To specify a specific wavelength for which to set pass/fail thresholds, select the desired wavelength from the Wavelengths box and press Apply to confirm your changes.
Testing Fibers in Advanced Mode Setting Pass/Fail Thresholds To view event status: 1. From the main window, go to the Result tab. The events’ status, at each wavelength, is indicated by a symbol. Pass (green) Warning (yellow) Fail (red) Note: If you see “- - -” instead of a status icon, either there is no threshold, or the status is unknown. Press Status Details for more information. 2.
Testing Fibers in Advanced Mode Setting a Default Span Start and Span End Setting a Default Span Start and Span End By default, the span start and span end of a fiber are assigned, respectively, to the first event (the launch level event) and the last event (often a non-reflective or reflective end event) of a trace. You can change the default fiber span that will be applied during the initial trace analysis.
Testing Fibers in Advanced Mode Setting a Default Span Start and Span End To change the default span start and span end for traces: 1. From the main window, press Setup. 2. From the Setup window, go to the Acquisition tab. 3. Under Span Start and Span End, go to the Position box and enter the desired value, using the distance units displayed to the right of the field. to the Position box and enter the desired value, using the distance units displayed to the right of the field.
Testing Fibers in Advanced Mode Saving the Span-Start and Span-End Information Saving the Span-Start and Span-End Information Saving the modified span-start and span-end information allows you to reapply the current span start and span end of a trace when you reanalyze, instead of applying the default fiber span originally used for the acquisition. For details on setting a default span start and end for trace acquisitions, see Setting a Default Span Start and Span End on page 83.
Testing Fibers in Advanced Mode Selecting the Operation Mode Selecting the Operation Mode There are two operation modes available: ³ Manual mode is available only when you work with a switch. It is used to acquire traces one at a time. Before each acquisition, you must select the desired channel from the list of channels you had previously configured.
Testing Fibers in Advanced Mode Selecting the Operation Mode To select the operation mode: 1. From the main window, press Setup. 2. From the Setup window, go to the Automation tab. 3. Under Operation Mode, select the desired mode. If you have chosen Auto mode, ³ If you only want one sequence, select Single. ³ If you want to repeat the sequences until you press Stop, select Infinite. From the Interval section, in the h box, enter the number of hours between the sequences.
Testing Fibers in Advanced Mode Setting Optical Switch Parameters Setting Optical Switch Parameters You can configure your switch to use any combination of channels in the desired order (for example, channel 2, then 4, then 1 will be tested). It is always possible to reset the order to the default value (channel 1, then 2, then 3, and so on). You can test with a switch in Advanced mode only. IMPORTANT The application can only use switches whose type matches the fiber type (singlemode or multimode).
Testing Fibers in Advanced Mode Setting Optical Switch Parameters 4. From the Channel Selection section, select the boxes corresponding to the channels you want to use and clear the boxes of those you do not want to use. Note: You can quickly select/deselect channels by using the Select All and Deselect All buttons. 5. If necessary, rearrange the order of the channels. 5a. From the list of channel, select a channel to move. 5b. Use the Move Up and/or Move Down buttons to modify the order. 6.
Testing Fibers in Advanced Mode Retesting Channels Retesting Channels At the end of an acquisition sequence, you can view the test results (see Viewing Test Results on page 136). It is possible to retest all the fibers with a specific status (pass, warning or fail) or a single fiber at a specific wavelength. Note: You can only retest fibers in Advanced mode, just after the test is complete.
Testing Fibers in Advanced Mode Retesting Channels 2. Press the Retest Channels button. Event pass/fail status Fiber identification Test wavelength 3. Specify which channels must be retested. ³ If you want to retest fibers according to their status, select Retest channel(s) based on the following status then select all the boxes corresponding to the desired status. OR ³ If you want to retest a specific fiber, select Retest channel(s) according to selected/highlighted Result list item.
Testing Fibers in Advanced Mode Monitoring Fiber in Real-Time Mode Monitoring Fiber in Real-Time Mode The application allows you to immediately view sudden changes in the fiber link. In this mode, the trace is refreshed instead of averaged until you stop the Real Time mode (to change settings before launching the test) or launch an acquisition with the current settings. Note: You can only use one wavelength at a time to monitor your fiber.
7 Testing Fibers in Template Mode Template mode allows you to test fibers and compare them to a reference trace that was previously acquired and analyzed. Template Principle Cables contain numerous fibers. Theoretically, on all these fibers, you will find the same events at the same location (due to connectors, splices, etc.). Template mode allows you to test these fibers one after the other quickly and efficiently and ensures that no event remains undetected.
Testing Fibers in Template Mode Restrictions of Template Mode You can save the trace after analysis. If former results have not been saved yet, the application prompts you to save them before starting a new acquisition. Template mode can be used on an unlimited number of traces, as long as you have at least one reference trace. Thus, you can use Template mode to automate trace acquisition or documentation tasks at the office.
Testing Fibers in Template Mode Restrictions of Template Mode Item Pulse width To be valid...
Testing Fibers in Template Mode Processing Traces Processing Traces In Template mode, you can process traces: ³ directly from the OTDR application (with an OTDR) ³ on an FTB-500 without an OTDR, or on a computer where the OTDR Viewer or FastReporter is installed. Operations performed with a module are described in detail in the following sections. At the end of each section, a note will indicate how to achieve the same results on a computer.
Testing Fibers in Template Mode Acquiring the Reference Trace Acquiring the Reference Trace You must acquire a reference trace before you activate the Template mode. The acquisition parameters you define for this reference trace will be used to acquire subsequent traces. To acquire the reference trace: 1. Clean the connectors properly (see Cleaning and Connecting Optical Fibers on page 26). 2. Connect a fiber to the OTDR port.
Testing Fibers in Template Mode Acquiring the Reference Trace 4. If desired, add comments to specific events (for more information, see Entering Comments on page 178). 5. If desired, enter information and comments about the current job (for more information, see Entering Job Information and Comments on page 47). 6. Once the analysis is complete, save the trace by pressing Save in the button bar.
Testing Fibers in Template Mode Acquiring Traces in Template Mode Acquiring Traces in Template Mode To select Template mode, you must first open your reference trace (newly acquired and saved trace or open trace file) in the application. For details, see Opening Trace Files on page 179 and Defining a Reference Trace on page 183. If you want your reference trace to be more accurate, you can update it with the new events that might be found.
Testing Fibers in Template Mode Acquiring Traces in Template Mode CAUTION Never connect a live fiber to the OTDR port without a proper setup. Any incoming optical power ranging from –65 dBm to –40 dBm will affect the OTDR acquisition. The way the acquisition will be affected depends on the selected pulse width. Any incoming signal greater than –20 dBm could damage your OTDR permanently. For live-fiber testing, refer to the SM Live port specifications for the characteristics of the built-in filter. 2.
Testing Fibers in Template Mode Acquiring Traces in Template Mode 3. Select the Template mode. 3a. From the main window, press Setup, then select the Mode tab. 3b. Under Mode, select Template. If necessary, select Reference Update to update your reference trace for the next acquisitions. If you want the application to automatically start Template mode after updating the reference trace, select the Switch to Template Mode After box and enter a number of acquisitions in the corresponding box.
Testing Fibers in Template Mode Acquiring Traces in Template Mode 3d. If you want to automatically apply the fiber span defined in the template reference trace to all acquired traces, select the Apply reference fiber span to current traces during post-processing check box. If you clear the box, the analysis will be performed on the common portion of the areas delimited by the span start and end of the reference trace and the span start and end of the main trace. 3e.
Testing Fibers in Template Mode Acquiring Traces in Template Mode 4. If applicable, the application will display the number of new events detected for each wavelength. 4a. Press OK to close the dialog box. Note: You can only add events to the reference trace during reference update. Note: If you chose the Keep all newly detected events feature for the acquisitions that will be performed after the update, you may find it useful to add newly detected events to obtain a more accurate reference trace.
Testing Fibers in Template Mode Acquiring Traces in Template Mode 5. Question marks will appear in the Event table to identify new events not found on the reference trace. If you want to add these marked events to the reference trace, press Add to Ref. You can also delete unwanted events with the Delete button. ³ Asterisks (“*”) identify events that were not found on the main trace, but that were added because they exist on the reference trace.
Testing Fibers in Template Mode Acquiring Traces in Template Mode 5a. Once the analysis is complete, save the trace by pressing Save in the button bar. If you have activated the autonaming feature, the application will use a file name based on the autonaming parameters you defined (see Naming Trace Files Automatically on page 50). Note: The application will only display the Save As dialog box if you have activated the feature to always be prompted when you save a file.
Testing Fibers in Template Mode Acquiring Traces in Template Mode 6. Once the reference update is complete (or if you did not select the reference update), the application automatically switches to Template mode. New events will be managed according to the option you selected at step 3c. Perform acquisitions in Template mode as follows: 6a. Press Start.
Testing Fibers in Template Mode Acquiring Traces in Template Mode 6c. Once the analysis is complete, save the trace by pressing Save in the button bar. If you have activated the autonaming feature, the application will use a file name based on the autonaming parameters you defined (see Naming Trace Files Automatically on page 50). Note: The application will only display the Save As dialog box if you have activated the feature to always be prompted when you save a file.
8 Customizing the Application You can customize the appearance and behavior of your OTDR application. Selecting the Default File Format You can define the default file format the application will use when you save your traces. By default, traces are saved in native (.trc) format, but you can configure your unit to save them in other formats. The available formats are the same as those presented in Saving a Trace in a Different Format on page 199.
Customizing the Application Selecting the Default File Format To select the default file format: 1. From the main window, press Setup, then select the General tab. 2. From the Default Format for New File box, select the desired format. 3. Press Apply to confirm the changes, then OK to return to the main window.
Customizing the Application Enabling or Disabling File Name Confirmation Enabling or Disabling File Name Confirmation By default, each time you save a file, the application prompts you to confirm the file name. If you disable the file name confirmation, the application will directly use a file name based on autonaming settings (see Naming Trace Files Automatically on page 50).
Customizing the Application Enabling or Disabling File Name Confirmation To enable or disable file name confirmation: 1. From the main window window, press Setup, then select the General tab. 2. If you want to confirm file name each time you press Save, select the Always Show Confirmation Window on Save check box. OR If you never want to be prompted, clear the check box. 3. Press Apply to confirm the changes, then OK to return to the main window.
Customizing the Application Enabling or Disabling Confirmation before Discarding Unnamed Trace Enabling or Disabling Confirmation before Discarding Unnamed Trace By default, each time you press the Start button when a trace has not been saved, the application prompts you to confirm if you want to save the trace or not. If you disable the confirmation, the application will discard the unnamed trace directly. To enable or disable confirmation: 1.
Customizing the Application Displaying or Hiding Pass/Fail Messages Displaying or Hiding Pass/Fail Messages The application can display messages indicating the event status of all the traces associated with the current fiber (one trace per wavelength). The current fiber corresponds to the fiber associated with the current trace in the Result tab of the main window (see Displaying or Hiding a Trace on page 147).
Customizing the Application Displaying or Hiding Pass/Fail Messages To display the messages: 1. From the main window, press Setup, then select the Thresholds tab. 2. Ensure that the Fail and/or Warning check boxes are selected. If not, the application will not use the associated thresholds and no message will be displayed. 3. Under Popup Messages, select the check boxes corresponding to the desired status. 4. Press Apply to confirm the changes, then OK to return to the main window.
Customizing the Application Selecting the Distance Units Selecting the Distance Units You can select the measurement units that will be used throughout the application, except for certain values such as the pulse and the wavelength. By convention, these values are always expressed in meters (nanometers for the wavelengths). Distance units The default distance units are the kilometers. Note: If you select Kilometers (km) or Kilofeet (kf), m and f may appear instead to display more precise measurements.
Customizing the Application Selecting the Distance Units To select the distance units for your display: 1. From the main window, press the Setup button. 2. From the Setup dialog box, select the General tab. 3. In the Distance Unit list, select the distance units to display. 4. Press Apply to confirm the changes, then OK to return to the main window. Once you exit the Setup dialog box, in the bottom right-hand corner of the trace display, you will notice that the distance unit abbreviation has changed.
Customizing the Application Customizing the Acquisition Distance Range Values Customizing the Acquisition Distance Range Values Note: This function is available in Advanced mode only. If your OTDR model is FTB-7000D or later, youYou can customize the values associated with the Distance dial. Once the customization is complete, you are ready to set the distance range value for your test. For more information, see Setting Distance Range, Pulse Width, and Acquisition Time on page 71.
Customizing the Application Customizing the Acquisition Distance Range Values To customize the distance range values: 1. From the main window, select Setup, then the Acquisition tab. 2. Press the Customize Settings button. 3. If your OTDR supports singlemode, multimode or filtered wavelengths, specify the desired fiber type. 4 3 4. From the Distance list, select the value you want to modify (the value will become highlighted), then press the Edit button.
Customizing the Application Customizing the Acquisition Time Values Customizing the Acquisition Time Values Note: This function is available in Advanced mode only. You can customize the values associated with the Time dial. The acquisition time values represent the time during which the OTDR will average acquisitions. If your OTDR model is FTB-7000D or later, youYou can even define acquisition time as short as 5 seconds (10 seconds for older modules).
Customizing the Application Customizing the Acquisition Time Values To customize the acquisition time values: 1. From the main window, select Setup, then the Acquisition tab. 2. Press the Customize Settings button. 3. From the Time(s) list, select the value you want to modify (the value will become highlighted), then press the Edit button. Note: You can revert to factory values by pressing the Default button. 4. In the displayed dialog box, enter the new value and confirm with OK.
Customizing the Application Defining the Number of Digits Displayed after the Decimal Point Defining the Number of Digits Displayed after the Decimal Point You can set the number of digits that will be displayed after the decimal point for the following values: ³ Span loss ³ Reflectance ³ Section attenuation ³ Span length ³ Span ORL This will affect the way values are displayed and, possibly, the status of the results (pass, warning or fail).
Customizing the Application Defining the Number of Digits Displayed after the Decimal Point To define the number of digits that will be displayed after the decimal point: 1. From the button bar, select Setup then select the General tab. 2. Press the Configure button. 3. Modify the number of digits as follows: 3a. Select the desired value from the list. 3b. In the Resolution box, type the desired value or use the buttons located on each side of the box to adjust the value. 3c.
Customizing the Application Enabling or Disabling the Beep Emitted After Acquisitions Enabling or Disabling the Beep Emitted After Acquisitions The application can emit a sound to inform you that the acquisition sequence is complete. To enable or disable the beep: 1. From the main window, select Setup, then select the Acquisition tab. 2. If you want to enable the beep, select the Beep when acquisition sequence is complete box. OR If you prefer to disable the beep, clear the box. 3.
Customizing the Application Defining OTDR Setups Defining OTDR Setups Once you have established all your configuration parameters, you may choose to save your setup for future use. You can also modify existing OTDR setups or delete them as needed. Note: To speed up the OTDR setup definition, you can use an already existing setup, make the changes you need and save it under a new name (see the procedure on page 126). To save an OTDR setup: 1.
Customizing the Application Defining OTDR Setups To modify an existing OTDR setup: 1. From the main window, press the Setup button. 2. From the Setup dialog box, select the General tab. 3. In the Configure OTDR Using list, ensure that Saved Setup is selected. 4. From the Saved Setup dialog box, select the desired OTDR setup. 5. Make any changes you want and press Save. ³ If you want to modify the existing file (overwriting it), keep the file name as is and press OK.
Customizing the Application Defining OTDR Setups To delete an OTDR setup: 1. From the main window, press the Setup button. 2. From the Setup dialog box, select the General tab. 3. In the Configure OTDR Using list, ensure that Saved Setup is selected. IMPORTANT Once an OTDR setup is deleted, it cannot be recovered. 4. From the Saved Setup dialog box, select the OTDR setup to delete and press Delete. 5. When the application prompts you to confirm, press Yes.
Customizing the Application Selecting an OTDR Setup Selecting an OTDR Setup You can select which OTDR setup you will use for your test session. There are two possibilities: ³ Current Setup: to retrieve the last configuration used. ³ Saved Setup: to specify which of the saved configurations you want to use. To select an OTDR setup: 1. From the main window, press the Setup button. 2. From the Setup dialog box, select the General tab. 3. In the Configure OTDR Using list, select Current Setup.
9 Analyzing Traces and Events Once the acquired trace is analyzed, it appears in the trace display and the events are displayed in the events table at the bottom of the screen.The trace display and events table are explained in the following sections. You can also reanalyze existing traces. For information on the various file formats you can open with the application, see Opening Trace Files on page 179.
Analyzing Traces and Events Trace Display and Events Table Description Trace Display and Events Table Description The application shows the analysis results both on a graph and in a table. The events, that are detailed in the events table (see Event Pane on page 131), are marked by numbers along the displayed trace. Default injection level Event no.
Analyzing Traces and Events Event Pane Once the trace is acquired, you can change trace display parameters (such as the grid and zoom window display). For more information, see Setting Trace Display Parameters on page 140. Note: Drag the split bar between the trace display and tabs to change their relative dimensions on the screen. If you want to zoom in on an event selected in the events table, see Using Zoom Controls on page 137.
Analyzing Traces and Events Event Pane The events table lists all the events detected on the fiber. An event can be defined as the point at which change in the transmission properties of light can be measured. Events can consist of losses due to transmission, splices, connectors or breaks. If the event is not within the established thresholds, its status will be set to “warning” or “fail”.
Analyzing Traces and Events Event Pane ³ Att.: Attenuation (loss/distance) measured for each fiber section. Note: The attenuation value is always presented in dB per kilometers even if the distance units you selected are not the kilometers. This follows the standards of the fiber-optic industry that provides the attenuation values in dB per kilometers. ³ Cumul.: Cumulative loss from the trace span start to span end; the running total is provided at the end of each event and fiber section.
Analyzing Traces and Events Event Pane To quickly locate an event in the events table: Select the event on the trace. The list scrolls automatically to the event you selected. Graph Event no.
Analyzing Traces and Events Measure Pane Measure Pane The application shows two, three or four markers: a, A, B, and b, depending on the button you pressed under Measurements. These markers can be repositioned along the trace to calculate loss, attenuation, reflectance, and optical return loss (ORL). You can reposition all markers by using the controls in the Markers section. You can drag them directly from the trace display. Selecting marker A or B will move the a-A or B-b pair.
Analyzing Traces and Events Viewing Test Results Viewing Test Results The application allows you to view current results directly after an acquisition sequence or to reload data from existing files. To view test results: From the main window, select the Result tab.
Analyzing Traces and Events Using Zoom Controls Using Zoom Controls Use the zoom controls to change the scale of the trace display. With the zoom controls, a magnifying glass icon appears in the trace display. When the scale changes, the trace display is always centered on the area surrounding the magnifying glass icon.
Analyzing Traces and Events Using Zoom Controls ³ When you manually zoom in or out on a trace, the application will apply the new zoom factor and marker positions to the other traces (wavelengths) of a same file and on the reference file, if applicable. Both the zoom factor and marker positions will be saved along with the trace (same settings for all wavelengths).
Analyzing Traces and Events Using Zoom Controls To automatically zoom in on the selected event: 1. From the main window, select the Graph tab and press the Event button. 2. From the events table, select the desired event. 3. Press to automatically adjust the zoom factor. To apply the same zoom factor and marker positions to all traces that are open: From the main window, select the Graph tab and press . To revert to the complete graph view: Press the OTDR button.
Analyzing Traces and Events Setting Trace Display Parameters Setting Trace Display Parameters You can set display preferences such as: ³ the grid: You can display or hide the grid appearing on the graph’s background. By default, the grid is displayed. ³ the graph background: You can display the graph with a black (invert color feature) or a white background. By default, the background is white. Note: The application always prints graphs with a white background in the reports.
Analyzing Traces and Events Setting Trace Display Parameters To set the trace display parameters: 1. From the main window, press the Setup button, then select the General tab. 2. Select the boxes corresponding to the item you want to display on the graph. OR To hide them, clear the boxes. To display a black background Changes will be applied once you exit the Setup dialog box. Press Apply to confirm the changes, then OK to return to the main window.
Analyzing Traces and Events Customizing the Event Table Customizing the Event Table Note: This function is available in Advanced mode only. You can include or exclude items from the events table to better suit your needs. Note: Hiding the fiber sections, the merged events or the comments will not delete these items. ³ Fiber sections: You can display or hide fiber sections in the events table and in the linear view, depending on the types of values you want to display.
Analyzing Traces and Events Customizing the Event Table ³ Launch level: In the events table, the Launch Level event is represented by the icon. In the Att. column, the injection level value for that event is identified by the @ symbol. You can hide the injection level value and symbol from the Att. column, but not the icon. ³ Including span start and span end: When applicable, the application will include the losses caused by the span start and span end events to the span ORL and span loss values.
Analyzing Traces and Events Customizing the Event Table To customize the events table appearance: 1. From the main window, press the Setup button, then select the Events Table tab. 2. Select the boxes corresponding to the item you want to display or include in the table. OR To hide them, clear the boxes. 3. Press Apply to confirm and OK to return to the main window.
Analyzing Traces and Events Selecting the Pulse Width Unit Selecting the Pulse Width Unit You can select the unit that is used in the Trace Info window to express the pulse value. The pulse value can be expressed in units of time or distance (see Selecting the Distance Units on page 116). To select the pulse width unit: 1. From the main window, press Setup. 2. From the Setup dialog box, select the General tab. 3. Press the arrow next to the Pulse Width box arrow and select the desired unit. 4.
Analyzing Traces and Events Selecting a Trace Display Mode Selecting a Trace Display Mode You can choose the way the application will display traces on-screen and in reports. The available choices are: ³ Complete Trace: to display the whole trace and full acquisition distance. ³ Span: to display the trace from the span start to the span end. ³ Optimum: to display the trace with a minimum amount of noise after the fiber end. To select a trace display mode: 1.
Analyzing Traces and Events Displaying or Hiding a Trace Displaying or Hiding a Trace There are two ways of displaying or hiding traces in the OTDR test application. ³ You can view, in turn, all the trace files you have opened, including main and reference traces, as well as multiwavelength traces. ³ You can select the fibers and the wavelengths (for multiwavelength files) that will be available when using the navigation bar.
Analyzing Traces and Events Displaying or Hiding a Trace To specify which traces to display or hide: 1. From the main window, select the Result tab. 2 Current trace indicator 3 2. Select the boxes corresponding to the traces to display. OR Clear the boxes to hide them. Note: A hidden trace cannot be displayed with the navigation bar. In multiwavelength trace files, you can show or hide traces independently. 3.
Analyzing Traces and Events Clearing Traces from the Display Clearing Traces from the Display Note: This feature is available in all test modes. However, you have to be in Advanced mode to set the application to automatically clear the traces from the display (except the reference trace) before launching the acquisition. Note: Clearing traces from the display does not delete them from the disk.
Analyzing Traces and Events Clearing Traces from the Display To clear traces from the display: 1. From the main window, on the button bar, press Close. 2. From the Close File(s) dialog box, select the check boxes corresponding to the files you want to clear. You can use the Select All or Deselect All button to speed up your selection. 3. Press OK to confirm.
Analyzing Traces and Events Clearing Traces from the Display To set automatic clearing of the trace display: 1. From the main window, press the Setup button. 2. From the Setup dialog box, select the Acquisition tab, then select the Clear all files other than the reference file when beginning acquisition sequence box. 3. Press Apply to confirm the changes, then OK to return to the main window. Once you launch your test, the files will be automatically closed.
Analyzing Traces and Events Modifying Space Between Traces on the Graph Modifying Space Between Traces on the Graph For easier viewing of the traces appearing on the graph, you can increase or decrease the vertical space between each of them. To increase or decrease the space between traces: 1. From the Graph tab in the main window, press Spacing. 2. Adjust trace spacing using buttons and slider in the Trace Spacing dialog box.
Analyzing Traces and Events Viewing and Modifying Current Trace Settings Viewing and Modifying Current Trace Settings You can view the trace parameters and modify them at your convenience. Note: Parameter modification is only possible in Advanced mode and in Auto mode (if you selected the Enable Editing for Current Trace Settings in the Mode tab). For more information on the activation and deactivation of this feature, see Testing Fibers in Auto Mode on page 57.
Analyzing Traces and Events Viewing and Modifying Current Trace Settings To view trace settings: Press the Trace Info button. Trace information Trace settings information Note: Even if more than one trace is available, the Trace Info pane only shows one at a time. To display the traces in turn, use the navigation bar. The active trace appears in black in the trace display. These parameters are displayed: 154 ³ Time: Time at which the acquisition was completed, with the time zone.
Analyzing Traces and Events Viewing and Modifying Current Trace Settings OTDR ³ Avg. Splice Loss: Average of all non-reflective events between span start and span end. ³ Max. Splice Loss: Maximum loss of all non-reflective events between span start and span end. ³ Span ORL: ORL calculated either between the span start and the span end, or on the total fiber span, depending on the option you have selected in the Setup window. ³ High-Resolution Acq.
Analyzing Traces and Events Viewing and Modifying Current Trace Settings To modify the current trace settings: 1. From the main window, go to the Graph tab and press the Trace Info button. 2. Press the Edit Current Trace Settings button. 3. Enter the desired values for the current trace in the appropriate boxes. OR If you want to revert to default values, press Default.
Analyzing Traces and Events Viewing and Modifying Current Trace Settings ³ You can change the fiber type of a multimode trace. The application will adjust the fiber type of all multimode wavelengths (traces). ³ Unless you are absolutely sure of the different parameter values, revert to default values to avoid fiber setting mismatches. You should do the same for other multimode wavelengths. ³ If you already know the IOR value, you can enter it in the corresponding box.
Analyzing Traces and Events Changing the Loss and Reflectance of Events Changing the Loss and Reflectance of Events Note: This function is available in Advanced mode only.
Analyzing Traces and Events Changing the Loss and Reflectance of Events To change the loss and reflectance of an event: 1. Select the event for which you want to modify the loss or reflectance. 2. Press Change. A magnifying glass icon and four markers (a, A, B, and b) appear in the trace display. You can reposition all markers directly by dragging them, or by pressing where you want to relocate them on the graph. Selecting marker A or B will move the a-A or B-b pair.
Analyzing Traces and Events Changing the Loss and Reflectance of Events 3. Position marker A as close as possible to the event, and submarker a (to the left of marker A) as far as possible from marker A , without including the preceding event. The area between markers A and a must not include any significant variation. For more information on positioning markers, see Using Markers on page 187. 4.
Analyzing Traces and Events Changing the Loss and Reflectance of Events 5. If you selected a reflective event, you can modify the echo status using the Event Type button. 6. Press the button corresponding to the desired event type. Loss and reflectance are calculated automatically, based on the position of the markers. 7. Press OK to accept the modifications you have made or Cancel to return to the events table without saving the changes.
Analyzing Traces and Events Inserting Events Inserting Events You can insert events in the event table manually. This could be useful, for example, if you know that there is a splice at a given location, but the analysis does not detect it because it is hidden in the noise or because the splice loss is lower than the minimum detection threshold (see Setting Pass/Fail Thresholds on page 78). You can add this event to the events table manually.
Analyzing Traces and Events Inserting Events 3. Select the location where you want to insert an event. Four markers are available to measure the inserted event, but only marker A identifies where the event will be inserted. Use one of the following methods: ³ Enter the location of the new event in the Location box. ³ Use the marker arrows to move marker A on the trace display. 4. Once you have determined the location, press the Event Type button. 5.
Analyzing Traces and Events Deleting Events Deleting Events Note: This function is available in Advanced mode only. Almost any event can be deleted from the events table, except: ³ end of analysis ³ fiber section ³ launch level ³ echo ³ end of fiber ³ span start ³ span end Note: The “End-of-fiber” event indicates the span end that was set for the first analysis of the trace, not the span end assigned to another event or distance from the span end in the Acquisition tab.
Analyzing Traces and Events Changing the Attenuation of Fiber Sections Changing the Attenuation of Fiber Sections Note: This function is available in Advanced mode only. You can change the attenuation value of fiber sections. IMPORTANT If you reanalyze a trace, all of the modifications made to the fiber sections will be lost and the events table will be re-created. Note: If you want to modify events, see Changing the Loss and Reflectance of Events on page 158.
Analyzing Traces and Events Changing the Attenuation of Fiber Sections 3. Position markers as desired to modify the attenuation value. For more information on positioning markers, see Using Markers on page 187. Note: The markers serve only to set the new attenuation value. Their actual locations will not be modified. Fiber section loss and attenuation are displayed respectively in the Loss (LSA) and Att. (LSA) boxes. Loss and reflectance values 4.
Analyzing Traces and Events Setting the Analysis Detection Thresholds Setting the Analysis Detection Thresholds Note: This function is available in Advanced mode only. To optimize event detection, you can set the following analysis detection thresholds: ³ Splice loss threshold: To display or hide small non-reflective events.
Analyzing Traces and Events Setting the Analysis Detection Thresholds The following examples show how different splice-loss threshold levels can affect the number of displayed events, especially small non-reflective events such as those caused by two splices. Three traces are shown, corresponding to three threshold level settings. Event location Threshold at 0.05 dB Threshold at 0.1 dB Threshold at 0.15 dB Not displayed Not displayed First splice ³ Second splice Threshold at 0.
Analyzing Traces and Events Setting the Analysis Detection Thresholds To set the analysis detection thresholds: 1. From the main window, press Setup. 2. From the Setup dialog box, select the Acquisition tab. 3. Under Detection Threshold Analysis, set the parameters. ³ Enter the desired values in the appropriate boxes. OR ³ Under Detection Threshold Analysis, select the default settings by pressing Default. 4. Press Apply to confirm the changes, then OK to return to the main window.
Analyzing Traces and Events Analyzing or Reanalyzing a Trace Analyzing or Reanalyzing a Trace Note: This function is available in Advanced mode only. You can analyze a displayed trace at any time. Analyzing or reanalyzing a trace will: ³ produce an events table for a trace, if there was none (for example, the Analyze After Acquisition feature was not selected; see Enabling or Disabling Analysis After Acquisition on page 76). ³ reanalyze a trace acquired with a previous version of the software.
Analyzing Traces and Events Analyzing or Reanalyzing a Trace To analyze or reanalyze a trace: 1. From the main window, select the Graph tab, then press the Event button. 2. Press the Analyze button. Pass/Fail messages will be displayed if you selected that feature (see Setting Pass/Fail Thresholds on page 78). 3. Press Close to return to the main window.
Analyzing Traces and Events Analyzing the Fiber on a Specific Fiber Span Analyzing the Fiber on a Specific Fiber Span Note: This function is available in Advanced mode only. If you want to focus your fiber analysis on a specific fiber span, you can define events (new or existing) as a span start and/or span end. You can even define a fiber span for short fibers by placing the span start and the span end on the same event.
Analyzing Traces and Events Analyzing the Fiber on a Specific Fiber Span ³ Use one of the double-arrow buttons to move marker A from event to event; this will designate an existing event as a span event. Note: Each of the first three elements may lead to the creation of a new event, except if your location corresponds to an already existing event on the trace. 4. Press Set Span Event to set the span start or span end marker on the appropriate event in the trace display.
Analyzing Traces and Events Enabling or Disabling the Detection of Reflective Ends of Fiber Enabling or Disabling the Detection of Reflective Ends of Fiber By default, the application stops the analysis as soon as there is too much noise on a trace to ensure accurate measurements. However, you can configure the application to search the “noisy” portion of the trace to detect strong reflective events (such as those caused by UPC connectors) and set the span end at this point.
Analyzing Traces and Events Enabling or Disabling the Detection of Reflective Ends of Fiber The table below shows the differences you will notice in the event table depending on if you enable the detection of reflective ends of fiber or not.
Analyzing Traces and Events Enabling or Disabling the Detection of Reflective Ends of Fiber IMPORTANT The analysis will stop as soon as the loss of an event crosses the end-of-fiber (EoF) threshold. The application will mark the event as an end-of-fiber event. In this case, even if you selected the option, the application will not search the “noisy” portion of the trace for reflective ends of fiber.
Analyzing Traces and Events Enabling or Disabling the Detection of Reflective Ends of Fiber 3. If you want to enable the option, under End-of-Fiber parameters, select the Reflective end-of-fiber detection box. OR If you prefer to disable the option, clear the box. 4. Press Apply to confirm the changes, then OK to return to the main window.
Analyzing Traces and Events Entering Comments Entering Comments Note: This function can be used in Advanced mode only. Once you have acquired or opened a trace, you may wish to add comments to specific events. They will appear at the bottom of the events table whenever the specified event is selected. The comments will be saved and can be accessed or changed at any time by opening the trace file and performing the same procedure.
Analyzing Traces and Events Opening Trace Files Opening Trace Files You can open as many trace files as there is available memory, except in Template mode, which only allows you to open two files at a time (reference trace and main trace). For the application, all trace files are equal. For this reason, if you want a particular trace to be considered as the reference trace, you must set it as such (see Defining a Reference Trace on page 183).
Analyzing Traces and Events Opening Trace Files Type of file Trace that has been saved with a manual zoom. Zoom Marker Application zooms in on the first trace (wavelength) of the file, according to the zoom area and zoom factor that were saved with the file. Application does not zoom in on the selected events. Markers are displayed in the same state they were when you saved the file. Markers will remain at the same location even if you switch to another trace.
Analyzing Traces and Events Opening Trace Files The application can open trace files saved in different formats, but does not necessarily allow all operations on them. File format File extension Display Native .trc 3 3 3 Telcordia (Bellcore) EXFO version 100 .sor 3 3 3 Telcordia (Bellcore) EXFO version 200 .sor 3 3 3 FTB-100 version 2.7 .ftb100 3 3 3 FTB-300 .ftb300 3 3 3 Telcordia (Bellcore) non-EXFO version 100 .sor 3 2 2 Telcordia (Bellcore) non-EXFO version 200 .
Analyzing Traces and Events Opening Trace Files To open a trace file: 1. From the button bar, press Open. 2. From the list, select the desired file (ensure that it becomes highlighted). Note: You can select the Show Preview box to display an overview of the trace(s) to ensure you will open the appropriate file. Note: You can load several files at the same time by selecting the Allow Multiple Selection box before choosing the files from the list (all the selected files will become highlighted). 3.
Analyzing Traces and Events Defining a Reference Trace Defining a Reference Trace A reference trace is used to compare fibers within the same cable, monitor fiber deterioration or compare fibers before and after installation. Once a trace file has been opened, you can define it as the reference trace. The application will then display it, in red, on the graph. There is only one reference file open at a time. A trace cannot be a reference and a main (current) trace at the same time.
Analyzing Traces and Events Defining a Reference Trace To define a reference trace manually: 1. Load the trace you want to use as the reference trace (see Opening Trace Files on page 179). 2. From the main window, select the Result tab. 3. Select the trace you want to use as reference (ensure that it is highlighted) and press Set as Reference. The name of the file set as reference is displayed in red and to its left.
10 Analyzing the Results Manually Once a trace has been acquired or opened, you can use markers and zoom in on or out of any event or trace segment to measure splice loss, fiber section attenuation, reflectance, and optical return loss. Selecting the Attenuation and Loss Values that Will Be Displayed By default, in the Measure tab, the application only displays the values obtained by using the same measurement methods as the analysis, that is the four-point event loss and the A-B LSA attenuation.
Analyzing the Results Manually Selecting the Attenuation and Loss Values that Will Be Displayed To select the attenuation and loss values that will be displayed: 1. From the button bar, press Setup then go to the General tab. 2. Press the Measurement Method button. 3. Select which values you want to see in the Measure tab. 4. Press OK to confirm your selection. 5. Press OK to return to the main window.
Analyzing the Results Manually Using Markers Using Markers You can use markers to view the position and relative power of an event. Markers are available when you press Measure from the main window, as well as in the Change and Insert windows, accessible from the Event pane. To move a marker: 1. Press the button corresponding to the marker you want to move. 2. Once the appropriate marker is selected, use the right and left arrow buttons to move the marker along the trace.
Analyzing the Results Manually Getting Event Distances and Relative Powers Getting Event Distances and Relative Powers The OTDR test application automatically calculates the position of an event and displays this distance in the events table. You can retrieve the position of an event as well as the distance between events manually. You can also display various relative power readings. Distances and relative powers correspond to the X-axis and Y-axis, respectively.
Analyzing the Results Manually Getting Event Loss (Four-Point and Least-Square Approximation) Getting Event Loss (Four-Point and Least-Square Approximation) Event loss (expressed in dB) is calculated by measuring the signal level reduction in Rayleigh backscatter (RBS) caused by this event. Event loss can result from both reflective and non-reflective events. Two loss calculations are provided simultaneously: the four-point event loss and the A-B LSA loss.
Analyzing the Results Manually Getting Event Loss (Four-Point and Least-Square Approximation) ³ a Four-point event loss: the LSA method is used to fit a straight line to the backscatter data within the two regions defined by markers a, A and b, B, that is over the regions to the left and to the right of the event bordered by markers A and B, respectively.
Analyzing the Results Manually Getting Event Loss (Four-Point and Least-Square Approximation) ³ A-B LSA loss: the loss of the event bordered by the markers A and B is obtained by fitting a straight line to the backscatter data between these two markers. A-B LSA loss a b The event is then obtained by the reduction in power (dB) over the distance between the two markers, as calculated from the slope of the fitted line.
Analyzing the Results Manually Getting Event Loss (Four-Point and Least-Square Approximation) To get event loss: 1. From the main window, go to the Graph tab and press the Measure button. 2. In the Measurements section, press Loss. Markers a, A, B and b appear on the graph. 3. Zoom in and position marker A at the end of the linear area preceding the event to be measured. For more information, see Using Zoom Controls on page 137 and Using Markers on page 187. 4.
Analyzing the Results Manually Getting Event Loss (Four-Point and Least-Square Approximation) 5. Position marker B at the beginning of the linear area following the event to be measured. 6. Position submarker b at the end of the linear area following the event to be measured (must not include any significant events).
Analyzing the Results Manually Getting Attenuation (Two-Point and Least-Square Approximation) Getting Attenuation (Two-Point and Least-Square Approximation) A two-point attenuation measurement gives the reduction in Rayleigh backscatter level as a function of distance (always expressed in dB/km to follow the standards of the fiber-optic industry) between two selected points. Only those two points are used to perform the calculation and there is no averaging.
Analyzing the Results Manually Getting Attenuation (Two-Point and Least-Square Approximation) To get attenuation: 1. From the main window, go to the Graph tab and press the Measure button. 2. In the Measurements section, press the Att. button. Markers A and B appear on the graph. 3. Place markers A and B at any two points on the trace. For more information, see Using Markers on page 187. 4. Zoom in on the trace and fine-tune the marker positioning if necessary.
Analyzing the Results Manually Getting Reflectance Getting Reflectance Reflectance is the ratio of reflected light to input light. Note: When performing reflectance measurements on recalled traces from non-EXFO test equipment that were saved in Telcordia (Bellcore) format, the results displayed could be less accurate than with EXFO file format. To get reflectance: 1. From the main window, go to the Graph tab and press the Measure button 2. In the Measurements section, press the Refl. button.
Analyzing the Results Manually Getting Optical Return Loss (ORL) Getting Optical Return Loss (ORL) Note: You must use a singlemode OTDR for ORL calculations. The ORL measurement may not be displayed if the acquisition was obtained with older OTDR modules.
11 Managing Trace Files Once you have acquired traces, or when you want to work with them after an acquisition, you will need to save, open, rename, and delete trace files. Saving a Trace in a Different Format By default, the application saves the traces in EXFO format (.trc). However, you can configure the application to save traces directly in other formats (see Selecting the Default File Format on page 109).
Managing Trace Files Saving a Trace in a Different Format File format Native File extension .trc Description Compatible with ToolBox version 6.21 or later, the FTB-500, FTB-400 platform, the FTB-200, FTB-150, and AXS-100 Series units. For more information, see OTDR Trace File Compatibility on page 204. ToolBox 6.7 - 6.20 .trc Compatible with ToolBox version 6.7 or later, the FTB-500, the FTB-400 platform, the FTB-200, FTB-150, and AXS-100 Series units.
Managing Trace Files Saving a Trace in a Different Format File format FTB-300 File extension .ftb300 Description ³ Compatible with ToolBox 5 and the FTB-300 UTS, as well as with all versions of ToolBox 6. ³ If the original file has more than one wavelength, the application will generate a .trc file for each of them. ASCII .asc A 500-point trace with all acquisition parameters in ASCII format ASCII+ .
Managing Trace Files Saving a Trace in a Different Format To save a file in another format: 1. From the main window, select the Result tab and, from the list, select the file you want to save in another format (ensure that it is highlighted). 2. Press Save As.
Managing Trace Files Saving a Trace in a Different Format 3. From the Save as dialog box, select the desired file format. If necessary, change the file name appearing in the corresponding box. 4. Press OK to save the file in the selected format.
Managing Trace Files OTDR Trace File Compatibility OTDR Trace File Compatibility The table presented hereafter shows the compatibility between the format of a specific trace and the software that you may use to open that trace.
Managing Trace Files OTDR Trace File Compatibility Software used to open the file... File generated with... ToolBox ToolBox ToolBox ToolBox FTB-100 FTB-100 FTB-100 5.5 6.5 or 6.7 to 6.21 or 2.5 or 2.6 or 2.7 2.8 or earlier 6.20 later earlier later/ FTB-150 FTB-200 AXS-100 a. b. c. d. e. f. ToolBox 5.5 X X X X Conva Conva Conva ToolBox 6.5 or earlier Convb X X X Conva Conva Conva ToolBox 6.7 to 6.20 Convc Convc X X Conva,d Conva Conva ToolBox 6.
Managing Trace Files Copying, Moving, Renaming, or Deleting Trace Files Copying, Moving, Renaming, or Deleting Trace Files If you want to copy, move, rename, or delete trace files, you will have to process the files manually via Windows Explorer. For more information, refer to Microsoft Windows Help.
12 Creating and Printing Trace Reports For future reference, you can add notes on the location and identification of the tested fiber, type of job performed and general comments related to a trace in trace reports. You can specify which information must be included in your printed documents. You can recall a trace in the OTDR application, modify the related information and save the changes with the trace.
Creating and Printing Trace Reports Adding Information to the Test Results Note: You can view traces from non-EXFO test equipment that were saved in the Telcordia (Bellcore) format. However, you cannot create reports with these traces or add report information to them. To speed up the documentation process, you can recall the information from the cable setup (Cable tab of the Setup dialog box).
Creating and Printing Trace Reports Adding Information to the Test Results To add information to the test results: 1. From the main window, once a trace has been acquired or reopened, select the Result tab. 2. From the trace list, select the desired trace and press Report/Documentation.
Creating and Printing Trace Reports Adding Information to the Test Results 3. Select one of the tabs (Fiber, Job, or Comments) and enter information in the appropriate boxes. Note: The information in the Test Date, Test Time, Unit A, and Serial Number A boxes is provided by the application and cannot be edited. 4. Press OK to confirm and return to the main window. The information is saved with the trace and can be viewed or changed at any time.
Creating and Printing Trace Reports Adding Information to the Test Results To clear all the information from tab: Press the Clear Fields button. To retrieve information from the cable window: Press Recall from Cable Setup. To transfer the new information to the cable setup: Press Update Cable Setup. Note: You can also update the cable setup with report information recorded in recalled traces from non-EXFO test equipment saved in Telcordia (Bellcore) format.
Creating and Printing Trace Reports Customizing the Report Customizing the Report You can customize your report before printing it by specifying which type of document you want, which information will appear in your report and in what order. You can even insert or remove page breaks between sections. If you choose the compressed format, you cannot insert page breaks between sections. If you choose the multitrace format, you cannot remove sections from the report or insert page breaks between sections.
Creating and Printing Trace Reports Customizing the Report The application offers the following types of reports: Report format Sample Normal 5-31 2002-0 Job ID tor Contrac er Custom e Test Dat Ope rB Operato File ID Fiber n A LocatioMfr. Cable ID Subset 4 6 A a A to B A to B Distance LSA Los s Trace Wavelen Filenam gth Hardwa e Serial re Number Softwar Range e IOR RBS dB 40.00 : 0.00 : N/A 0 km, 0.03 2 dB : 0.11 : 16.9 2 km 48 dB : 131 0 : 3 Lamnm (SM) : FTB bda.
Creating and Printing Trace Reports Customizing the Report The following table shows the various items that can appear on a report: Item appearing on the report Summarized Compressed Multi-trace Job information: test date and time (including the time zone), unit serial and model numbers, company, job and customer ID, operators A and B. X X Cable information: a single table containing information such as the fiber ID, cable ID, location A and B.
Creating and Printing Trace Reports Customizing the Report Item appearing on the report Marker information: a, A, b, B, and A to B distances, as well as A to B attenuation, loss, and ORL. Summarized Compressed Multi-trace X X X X X X X This item is not available in Auto mode. Test and cable setup for main and reference traces: file name, OTDR model, software version, wavelength, distance, IOR, RBS, acquisition time, pulse width, and helix factor.
Creating and Printing Trace Reports Customizing the Report To customize your report: 1. From the main window, press the Print button. 2. From the Print Configuration dialog box, select the Report tab. 3. From the Format list, select the desired type of report. 4 4. From the Content list, select all the boxes corresponding to the sections you want to include in your report. You can remove any unwanted section by clearing the corresponding boxes. Note: You cannot remove sections of a multitrace report.
Creating and Printing Trace Reports Customizing the Report 5. If you selected the Multi-Trace format, from the Report Content list, select the section you want to include in the report. 6. If necessary, rearrange the order of appearance of the various sections. 6a. From the Content list, select the section to move (ensure that the item is highlighted). 6b. Use the Move Up and/or Move Down buttons. Note: You cannot rearrange the order of sections of a multitrace report.
Creating and Printing Trace Reports Customizing the Report 7. If you selected the Normal format and you want to add or remove breaks, proceed as follows To add a page break, from the Content list, select the section before which you want to insert a page break (ensure that the item is highlighted) and press Add Page Break. OR To remove a page break, from the Content list, select the page break to remove (ensure that the item is highlighted) and press Remove Page Break.
Creating and Printing Trace Reports Customizing the Report 9. If necessary, you can add a footer to your report by selecting the Print Footer box. If you prefer not to see the printing date, select the Page Number Only box. 10. If you selected Multi-Trace, you can also: ³ Add a cover page to your report by selecting the Cover Page check box. You can include a logo on this cover page by pressing the Select button and select the logo file.
Creating and Printing Trace Reports Printing a Report Note: In the Bidirectional Analysis tool, this option is only available if you selected the Print AB and BA Traces box. ³ You can select the Print with zoom item if you want the traces to be printed with the zoom factor you selected: Manual zoom: Graphs will be printed exactly as they appear on screen. The same zoom factor will be applied to all traces (wavelengths) of a particular file.
Creating and Printing Trace Reports Printing a Report ³ Print All Traces: to print all the traces that are loaded in the application. Each open file will generate a distinct report. ³ Print Visible Traces: to print all the traces that are selected in the Result tab of the main window (see Displaying or Hiding a Trace on page 147).
Creating and Printing Trace Reports Printing a Report To print your report: 1. From the main window, press Print. 2. If necessary, from the Print Configuration window, press the Print Setup button to change the current printer and its parameters. 3. In the Number of Copies box, enter the desired value. 4. From the Print Range section, select the box corresponding to the traces you want to print. 5. Press Print. The application will keep in memory the items you have included in your reports for future use.
13 Using the OTDR as a Light Source or VFL Note: This function is available in Advanced mode only. ³ If you want to perform measurements with a power meter and your OTDR as a source, the OTDR port can transmit a special tone. This port can be used only to transmit—not detect that tone. You can also activate the auto-off feature that will stop the light emission automatically after the specified lapse of time.
Using the OTDR as a Light Source or VFL To use your OTDR as a source: 1. Clean the connectors properly (see Cleaning and Connecting Optical Fibers on page 26). 2. Connect one end of the fiber under test to the OTDR port. If your unit is equipped with two OTDR ports, ensure that you connect the fiber to the appropriate port (singlemode, singlemode live, or multimode), depending on the wavelength you intend to use. 3. From the main window, go to the Source tab. Ensure that Wavelength is selected. 4.
Using the OTDR as a Light Source or VFL 5. Select the desired modulation. With the Modulation dial, ³ For loss measurement, with a power meter at the other end, select CW (to set the source to continuous output). IMPORTANT Measurements using the CWsetting must always be taken using a GeX detector. An OTDR source is very powerful and it will certainly saturate Ge and InGaAs detectors, which usually saturate at 6 dBm, while GeX detectors saturates at 26 dBm.
Using the OTDR as a Light Source or VFL To identify fiber faults visually: 1. Clean the connectors properly (see Cleaning and Connecting Optical Fibers on page 26). 2. Connect the fiber under test to the VFL port. 3. From the main window, go to the Source tab, then select VFL. 4. With the Modulation dial, select 1 Hz or CW. Choose 1 Hz to set the VFL to 1 Hz pulsed output, and CW to set it to a continuous output. 5. From the Auto-Off box, select the duration after which you want the laser to shut off.
14 Analyzing Bidirectional Traces Note: The OTDR Bidirectional Analysis utility is available only from the Applications tab of ToolBox If two OTDR traces are acquired in opposite directions on the same fiber span, the OTDR Bidirectional Analysis utility allows you to match the corresponding events. The application performs a bidirectional analysis and generates an events table with the averaged loss for each event; that is, the average of the losses obtained from both directions.
Analyzing Bidirectional Traces Starting and Exiting the Bidirectional Analysis Utility Starting and Exiting the Bidirectional Analysis Utility To start the Bidirectional Analysis utility: 1. From ToolBox, go to the Applications tab. 2. Press OTDR Bidirectional. The main window is displayed. If you are using this utility for the first time, or if you have closed the files before exiting last time you used the utility, no trace will be automatically loaded.
Analyzing Bidirectional Traces Starting and Exiting the Bidirectional Analysis Utility The main window contains buttons allowing you to access the following panes: ³ Results for the A->B trace, presented in a table ³ Results for the B->A trace, presented in a table ³ Results for the bidirectional trace, presented in a table ³ Options to modify span-start and span-end values ³ Information about the A->B trace and settings used ³ Information about the B ->A trace and settings used ³ Information
Analyzing Bidirectional Traces Creating Bidirectional Trace Files Creating Bidirectional Trace Files To work with the OTDR Bidirectional Analysis utility, you must acquire and save the traces (in the OTDR application) before opening them with the Bidirectional Analysis utility. You can open unidirectional trace files to combine them into a bidirectional trace. It is possible to use both single-wavelength and multiwavelength traces.
Analyzing Bidirectional Traces Creating Bidirectional Trace Files The A->B and B->A traces must respect the following criteria: Item To be valid... Pulse width Must be identical for both traces. Fiber types Use only traces acquired using singlemode fibers. Acquisition offset Must be set to zero for both traces. Wavelengths Must be identical for both traces. Trace Both must be unidirectional files (.trc files).
Analyzing Bidirectional Traces Creating Bidirectional Trace Files To create a bidirectional trace file: 1. If necessary, clear the window by pressing the Close button on the button bar. The application will prompt you if some files have not been saved. 2. From the button bar, press Open. 3. In the Open dialog box, select Create Bidirectional File by Opening A->B File and B->A File.
Analyzing Bidirectional Traces Creating Bidirectional Trace Files 4. Select the files to open. 4a. Press the Select button, on the right of the A->B File Path box. 4b. Select the first file (ensure that it is highlighted) and press OK. Note: You can select the Show Preview box to display an overview of the trace(s) to ensure you will open the appropriate file. 4c. Press the Select button, on the right of the B->A File Path box. 4d. Select the second file (ensure that it is highlighted) and press OK. 5.
Analyzing Bidirectional Traces Opening Existing Bidirectional Trace Files Opening Existing Bidirectional Trace Files You can open previously merged bidirectional traces to view results or to reanalyze the trace. To open an existing bidirectional trace file: 1. If necessary, clear the window by pressing the Close button on the button bar. The application will prompt you if any files have not been saved. 2. From the button bar, press Open. 3. In the Open dialog box, select Open Existing Bidirectional File.
Analyzing Bidirectional Traces Opening Existing Bidirectional Trace Files 4. Press the Select button, on the right of the Bidirectional File Path box. 5. Select the desired file (ensure that it is highlighted) and press OK. Note: You can select the Show Preview box to display an overview of the trace(s) to ensure you will open the appropriate file. 6. Back to the Open dialog box, press OK to confirm.
Analyzing Bidirectional Traces Viewing Test Results Viewing Test Results The application allows you to view the results of the A->B and B->A traces according to the thresholds defined in the Bidirectional Analysis tool. You can also view the corresponding graph and obtain more information about the status of the bidirectional and/or A->B and B->A status. To view test results: From the main window, select the Result tab.
Analyzing Bidirectional Traces Analyzing the Fiber on a Specific Fiber Span Analyzing the Fiber on a Specific Fiber Span If you want to focus your fiber analysis on a specific fiber span, you can define events (new or existing) as span start and span end. Span start and span end are defined on both the A->B and B->A trace. Traces are aligned on the span start of the A->B trace and on the span end of the B->A trace. The two other span events are not used in the bidirectional analysis.
Analyzing Bidirectional Traces Analyzing the Fiber on a Specific Fiber Span To set a fiber span: 1. From the main window, press the Span button. 2. Select the Span Start or Span End option according to the type of span event you want to create for the A->B and B->A trace.
Analyzing Bidirectional Traces Analyzing the Fiber on a Specific Fiber Span 3. Enter the span event location by moving marker A along the trace using one of the following options: ³ Drag marker A to position it to the desired span event location. ³ Enter a distance value in the Position box. ³ Use the single-arrow buttons to move marker A on the trace. ³ Use one of the double-arrow buttons to move marker A from event to event; this will designate an existing event as a span event.
Analyzing Bidirectional Traces Analyzing Bidirectional Traces Analyzing Bidirectional Traces You can use either single-wavelength or multiwavelength trace files for bidirectional analysis. For details, see Creating Bidirectional Trace Files on page 230 and Opening Existing Bidirectional Trace Files on page 234. Once the trace files are open, you can proceed with the analysis.
Analyzing Bidirectional Traces Analyzing Bidirectional Traces The bidirectional event table lists all the events detected on the fiber.
Analyzing Bidirectional Traces Changing Event Tables Changing Event Tables You can change event tables and edit the A->B and B->A traces. If you change events in one event table, the bidirectional event table will be adjusted accordingly.
Analyzing Bidirectional Traces Viewing and Modifying Current Trace Parameters Viewing and Modifying Current Trace Parameters You can view the current trace parameters for the bidirectional trace as well as for the A -> B and B -> A traces. However, you can only modify the analysis settings for the current A->B and B->A traces, not for the bidirectional trace.
Analyzing Bidirectional Traces Viewing and Modifying Current Trace Parameters To view trace parameters: Press the Bidir. Info, A->B Info or B->A Info button. Trace information Event tolerance (Bidir. Info pane) or trace settings information Edit Tolerance or Edit Current Trace Settings (A->B Info and B -> A Info) button The following parameters are displayed: ³ Pulse: Pulse width used to perform the acquisition. ³ Length: Measured length of the total fiber span between span start and span end.
Analyzing Bidirectional Traces Viewing and Modifying Current Trace Parameters Parameters specific to the A->B or B->A trace are also displayed: OTDR ³ Range: Acquisition range. ³ Span ORL: ORL calculated between the span start and the span end, or can include them, depending on the settings you have chosen in the setup window. ³ High-Resolution Acq.: Indicates whether or not the acquisitions were performed using the high-resolution feature.
Analyzing Bidirectional Traces Viewing and Modifying Current Trace Parameters To modify the current trace settings: 1. From the main window, press the A->B Info or B->A Info button then press the Edit Current Trace Settings button. 2. Enter values for the current trace in the appropriate boxes. OR Revert to default values by pressing the Default button. If you already know the IOR value, you can enter it in the corresponding box.
Analyzing Bidirectional Traces Viewing and Modifying Current Trace Parameters 3. Press OK to confirm. You return to the Trace Info pane. Note: Modifying the current trace parameters in the A->B Info or B->A Info pane affects the trace that is displayed. To change the tolerance interval value: 1. Press the Bidir. Info button and then Edit Tolerance. 2. Enter the desired value in the Tolerance (to be adjusted) box. OR Press Default to use to the default tolerance value. 3. Press OK.
Analyzing Bidirectional Traces Saving Traces Saving Traces After recalling, analyzing and displaying the two traces in the bidirectional table, these traces may be stored as a merged bidirectional trace in order to facilitate file management. All information in the tables, comments and reports for A->B, B->A, as well as the bidirectional trace will be saved in the bidirectional file. By default, the application saves the bidirectional file only.
Analyzing Bidirectional Traces Saving Traces 2. From the Save As dialog box, select a folder or create one to save your file. Go up to parent folder Create a folder 3. From File To Be Saved, select the file you want to save. 4. In the Filename box, type a name for your file and press OK. IMPORTANT If you specified an existing file name, the application will display a warning message. To avoid losing data, press Yes only if you want to overwrite the existing file.
Analyzing Bidirectional Traces Documenting Results Documenting Results After acquiring a trace, you might want to include or update information about the tested fiber and job or add comments. For more information, see Adding Information to the Test Results on page 207. Creating a Report You can customize your report before printing it by specifying which type of document you want, which information will appear in your report and in what order. For more information, see Customizing the Report on page 212.
15 Preparing for Automation or Remote Control Your OTDR can be controlled automatically or remotely after configuring the appropriate parameters. EXFO supplies commands that follow the guidelines determined by the SCPI consortium as well as LabVIEW drivers. EXFO also supplies COM properties and events allowing you to build your own application. Detailed information on the provided commands can be found in SCPI Command Reference on page 311.
Preparing for Automation or Remote Control You can display a monitor window allowing you to view information related to your OTDR such as the current parameters, status, etc. The provided information is updated according to the SCPI commands you send to the OTDR. The window is divided into sections corresponding to specific SCPI commands. References to the various commands are presented in the following pages. 1 2 3 4 5 8 6 7 Note: You cannot edit information directly from this window.
Preparing for Automation or Remote Control To display the monitor window: 1. From ToolBox, go to the Modules tab. 2. Press Monitor 7000. You can hide (minimize) the monitor window and make it appear as needed. To hide the monitor window: Use the button on the upper-right corner of the window. To show a hidden monitor window: 1. Press the Program Switcher button. This button is located on the front panel of the FTB-500 (for more information, refer to the FTB-500 user guide). 2.
Preparing for Automation or Remote Control ³ Acquisition Configuration: Current parameters used for acquisition. 1 See :CONFigure[1..n]:ACQuisition:MODE? on page 373 See :CONFigure[1..n]:ACQuisition: WAVelength? on page 381 See :CONFigure[1..n]:ACQuisition:RANGe? on page 377 See :CONFigure[1..n]:ACQuisition:PULSe? on page 374 See :CONFigure[1..n]:ACQuisition: DURation? on page 367 ³ 2 Analysis Settings: Current values used for analysis. See :CONFigure[1..
Preparing for Automation or Remote Control ³ 3 Loaded File: File name and path of the currently loaded file. See :MMEMory[1..n]:LOAD:NAME? on page 413 ³ 4 File Management: Saving behavior and file type. The file type (format) reflects the setting you make with the corresponding SCPI command. Consequently, it will not be updated at the loading of a file. See :MMEMory[1..n]:STORe:TRACe: OVERwrite? on page 418 See :MMEMory[1..
Preparing for Automation or Remote Control ³ Auto Setting Results: Acquisition values suggested by the application to get the best possible results. If you want to use this feature, remember to set the OTDR’s acquisition mode to ACQuisition first. 6 IMPORTANT The OTDR parameters are NOT automatically set to the suggested values. You must set them yourself using the appropriate SCPI commands. See :FETCh[1..n]:ASETting:RANGe? on page 399 See :FETCh[1..n]:ASETting:PULSe? on page 398 See :FETCh[1..
Preparing for Automation or Remote Control ³ Active Trace Information: Information available for the selected (active) trace. When you are working with a loaded file, you can specify which of the available traces will become the active trace. The related information is automatically refreshed according to your selection.
16 Maintenance To help ensure long, trouble-free operation: ³ Always inspect fiber-optic connectors before using them and clean them if necessary. ³ Keep the unit free of dust. ³ Clean the unit casing and front panel with a cloth slightly dampened with water. ³ Store unit at room temperature in a clean and dry area. Keep the unit out of direct sunlight. ³ Avoid high humidity or significant temperature fluctuations. ³ Avoid unnecessary shocks and vibrations.
Maintenance Cleaning EUI Connectors Cleaning EUI Connectors Regular cleaning of EUI connectors will help maintain optimum performance. There is no need to disassemble the unit. IMPORTANT If any damage occurs to internal connectors, the module casing will have to be opened and a new calibration will be required. To clean EUI connectors: 1. Remove the EUI from the instrument to expose the connector baseplate and ferrule. Turn Pull Push 2. Moisten a 2.
Maintenance Cleaning EUI Connectors 5. Repeat steps 3 to 4 with a dry cleaning tip. Note: Make sure you don’t touch the soft end of the cleaning tip. 6. Clean the ferrule in the connector port as follows: 6a. Deposit one drop of isopropyl alcohol on a lint-free wiping cloth. IMPORTANT Isopropyl alcohol may leave residues if used abundantly or left to evaporate (about 10 seconds). Avoid contact between the tip of the bottle and the wiping cloth, and dry the surface quickly. 6b.
Maintenance Verifying Your OTDR Verifying Your OTDR You can perform several tests to ensure your OTDR operates within specifications. Deviation is measured to determine if the OTDR needs recalibration. Setting your OTDR to zero can only be done at EXFO. However, you can test your OTDR to verify the accuracy of its measurement origin. To measure the deviation: 1. Connect at least 2 km of fiber to the OTDR output port. 2. Set the distance range at 2.5 km and acquisition time at 180 seconds. 3.
Maintenance Verifying Your OTDR To evaluate the launch level: 1. Connect at least 2 km of fiber to the OTDR port. ³ Ensure that the OTDR port and connectors are properly cleaned and that the fiber settings are accurate (IOR, Helix factor and RBS). ³ Do not use a test jumper between the OTDR and the fiber under test to limit the number of connectors. 2.
Maintenance Verifying Your OTDR To verify the OTDR’s zero: 1. Connect a patchcord, approximately 10 m long, to the OTDR port. The exact length of the jumper must have been measured mechanically. Ideally, you should use an unjacketed patchcord. ³ Ensure that the OTDR port and connectors are correctly cleaned. ³ Ensure that the fiber settings are accurate (IOR, Helix factor and RBS). 2. Set the distance range to less than 2 km, the pulse width to 10 ns and the acquisition time to 30 s. 3.
Maintenance Verifying Your OTDR To measure the event and attenuation dead zones: 1. Connect 2 km of fiber directly to the OTDR port. Use the shortest pulse width and distance range possible. ³ Ensure that the OTDR port and connectors are correctly cleaned. ³ Ensure that the fiber settings are accurate (IOR, Helix factor, and RBS). 2. Measure the length (E) of the first reflection at 1.5 dB from the maximum, as shown below. This is the event dead zone. 3.
Maintenance Verifying Your OTDR To measure the dynamic range: 1. Connect the OTDR as indicated below. Other configurations are possible, such as the one explained in the section on how to determine measurement range, if you use the shortest fiber length from that setup. In all cases, the fiber should have several sections longer than 2 km, with no loss greater than 8 dB and with an average attenuation not exceeding 1 dB/km.
Maintenance Verifying Your OTDR 2. Set the distance range to 160 km (singlemode fiber), the pulse width to the longest value available and the acquisition time to 180 seconds. 1 dB Dynamic range Dynamic range is the difference between the launch level and the position on the curve where the peak-to-peak noise level is 1 dB, plus a correction factor relative to the noise amplitude (which is 5.2 dB).
Maintenance Verifying Your OTDR To determine the measurement range (singlemode models only): 1. Connect the OTDR as indicated below. Other configurations are possible, but the fiber should have several sections longer than 2 km, with no loss greater than 8 dB and with the average attenuation not exceeding 1 dB/km. A variable attenuator will be used to adjust the loss in the span. One or several non-reflective events with a nominal loss of 0.5 dB should be present.
Maintenance Verifying Your OTDR 2. Set the distance range to 80 km (singlemode fiber), the pulse width to the longest value available and the acquisition time to 180 seconds. The measurement range using the non-reflective event method represents the amount of attenuation (dB) between the launch level and a 0.5 dB splice (which can be detected and measured to an accuracy of ± 0.1 dB). You can measure it by simply making an acquisition on a fiber with a known attenuation and a known 0.5 dB splice.
Maintenance Recalibrating the Unit Recalibrating the Unit Manufacturing and service center calibrations are based on the ISO/IEC 17025 Standard, which states that calibration documents must not contain a recommended calibration interval, unless this has been previously agreed upon with the customer. Validity of specifications depends on operating conditions.
Maintenance Recycling and Disposal (Applies to European Union Only) Recycling and Disposal (Applies to European Union Only) Recycle or dispose of your product (including electric and electronic accessories) properly, in accordance with local regulations. Do not dispose of it in ordinary garbage receptacles. This equipment was sold after August 13, 2005 (as identified by the black rectangle).
17 Troubleshooting Solving Common Problems Problem Cause Solution New module is not working. The software version installed on your FTB-500 is too old for the module currently being used. Update the OTDR software version using the CD that came with your new module (refer to the Update Manager online help). The application does not use your custom thresholds. The thresholds have been defined on the wrong wavelength.
Troubleshooting Solving Common Problems Problem Cause The application displays a message indicating that a “live fiber error” occurred and the fiber was not connected to the SM Live port. Light has been detected on the OTDR port during the acquisition or while you were monitoring a fiber in real-time mode. Solution Disconnect the fiber from the OTDR port. Press OK to close the message. Start another acquisition without any fiber connected to the OTDR.
Troubleshooting Solving Common Problems Problem Cause The application displays a message indicating that a “live fiber error” occurred and the fiber was connected to the SM Live port. The level of integrated power in the filter bandwidth of the SM Live port is too high. A transmission wavelength from the network could be too close to the SM Live wavelength. Solution Disconnect the fiber from the OTDR port. Press OK to close the message.
Troubleshooting Error Messages Error Messages Error Message ToolBox Fatal Error: OTDR Card Module Memory Error Possible Cause Solution The module could have a defective memory. Verify that the instrument has not been modified by the user. There could be a conflict between the module and another item on the BUS (for example, a network card). If the instrument has been modified, try the module in another FTB-500. The OTDR does not recognize the requested communication port.
Troubleshooting Error Messages Error Message Possible Cause Solution ToolBox Fatal Error: OTDR Card Module Unknown Model Error This error arises if the software version is incompatible with the hardware, or less frequently, if the module memory has been corrupted. Take note of the module serial number and the software version. ToolBox Fatal Error: OTDR Card Module APD Error The photodetector is not Return the module to EXFO. working. The module should not be used.
Troubleshooting Error Messages Error Message Possible Cause Solution Communication test The module is not able to with the module has perform the commands failed. properly. Contact EXFO. Unable to read The software version installed current version of the on your FTB-500 is too old for calibration EEPROM. the module currently being used. Update ToolBox software version (refer to the FTB-400 Universal Test System user guide).Update the OTDR software version (refer to the Update Manager online help).
Troubleshooting Viewing Online Documentation Viewing Online Documentation An online version of the Optical Time Domain Reflectometer user guide is available at all times from the application. Note: You will also find a printable PDF version on your installation DVD. To access online help: In the button bar, click About then click User Guide.
Troubleshooting Contacting the Technical Support Group Contacting the Technical Support Group To obtain after-sales service or technical support for this product, contact EXFO at one of the following numbers. The Technical Support Group is available to take your calls from Monday to Friday, 8:00 a.m. to 7:00 p.m. (Eastern Time in North America). For detailed information about technical support, visit the EXFO Web site at www.exfo.com.
Troubleshooting Transportation You may also be requested to provide software and module version numbers.This information, as well as technical support contact information, can be found by clicking About in the function bar Transportation Maintain a temperature range within specifications when transporting the unit. Transportation damage can occur from improper handling.
18 Warranty General Information EXFO Inc. (EXFO) warrants this equipment against defects in material and workmanship for a period of one year from the date of original shipment. EXFO also warrants that this equipment will meet applicable specifications under normal use.
Warranty Liability Liability EXFO shall not be liable for damages resulting from the use of the product, nor shall be responsible for any failure in the performance of other items to which the product is connected or the operation of any system of which the product may be a part. EXFO shall not be liable for damages resulting from improper usage or unauthorized modification of the product, its accompanying accessories and software.
Warranty Service and Repairs Service and Repairs EXFO commits to providing product service and repair for five years following the date of purchase. To send any equipment for service or repair: 1. Call one of EXFO’s authorized service centers (see EXFO Service Centers Worldwide on page 286). Support personnel will determine if the equipment requires service, repair, or calibration. 2.
Warranty EXFO Service Centers Worldwide EXFO Service Centers Worldwide If your product requires servicing, contact your nearest authorized service center. EXFO Headquarters Service Center 400 Godin Avenue Quebec (Quebec) G1M 2K2 CANADA EXFO Europe Service Center Omega Enterprise Park, Electron Way Chandlers Ford, Hampshire S053 4SE ENGLAND EXFO Telecom Equipment (Shenzhen) Ltd. 3rd Floor, Building 10, Yu Sheng Industrial Park (Gu Shu Crossing), No.
A Technical Specifications IMPORTANT The following technical specifications can change without notice. The information presented in this section is provided as a reference only. To obtain this product’s most recent technical specifications, visit the EXFO Web site at www.exfo.com.
Technical Specifications All specifications valid at 23º C ± 2º C with an FC/PC connector for the FTB-7300E, with FC/APC for FTB-730, unless otherwise specified. TECHNICAL SPECIFICATIONS Model FTB-7300E a FTB-730 b Wavelength (nm) c 1310 ± 20/1490 ± 10/1550 ± 20/1625 ± 10/1650 ± 7 1310 ± 20/1490 ± 10/1550 ± 20/1625 ± 10 Dynamic range at 20 +s (dB) d 39/35/37/39 e/37 39/35/37/39 Event dead zone (m) f 0.8 0.8 Attenuation dead zone (m) f 4/4.5/4.5/4.5/4.5 4/4.5/4.5/4.5 Distance range (km) 1.
Technical Specifications All specifications valid at 23 °C ± 2 °C with an FC/PC connector, unless otherwise specified. TECHNICAL SPECIFICATIONS Model a FTB-7400E-XXXX FTB-7400E-CWS Wavelengths (nm) b 1310 ± 20/1383 ± 1/1550 ± 20/1625 ± 10 1470 ± 3/1490 ± 3/1510 ± 3/1530 ± 3 1550 ± 3/1570 ± 3/1590 ± 3/1610 ± 3 Dynamic range at 20 +s (dB) c 42/40/41/41 41/41/ 41/41 41/41/ 40/40 Event dead zone (m) d 0.8 0.8 0.8 Attenuation dead zone (m) d 4/4/4.5/4.5 4/4.5/4.5 4/4.5/4.
Technical Specifications All specifications valid at 23 °C ± 2 °C with an FC/PC connector, unless otherwise specified. TECHNICAL SPECIFICATIONS Model a FTB-7500E Wavelengths (nm) b 1310 ± 20/1550 ± 20/1625 ± 10 Dynamic range at 20 +s (dB) c 45/45/45 Event dead zone (m) d 0.8 Attenuation dead zone (m) d 4/4.5/4.5 Distance range (km) 1.25, 2.5, 5, 10, 20, 40, 80, 160, 260, 400 Pulse width (ns) 5, 10, 30, 50, 100, 275, 500, 1000, 2500, 10 000, 20 000 Linearity (dB/dB) b ± 0.
Technical Specifications All specifications valid at 23 °C ± 2 °C with an FC/PC connector, unless otherwise specified. TECHNICAL SPECIFICATIONS Model a FTB-7600E Wavelengths (nm) b 1310 ± 20/1550 ± 20/1625 ± 10 Dynamic range at 20 +s (dB) c 50/50/48 g Event dead zone (m) d 1/1.5/1 Attenuation dead zone (m) d 5/5/5 Distance range (km) 1.25, 2.5, 5, 10, 20, 40, 80, 160, 260, 400 Pulse width (ns) 5, 10, 30, 100, 275, 1000, 2500, 10 000, 20 000 Linearity (dB/dB) b ± 0.
B Description of Event Types This section describes all types of events that may appear in the events table generated by the application. Here is a guide to the descriptions: OTDR ³ Each type of event has its own symbol. ³ Each type of event is represented by a graph of a fiber trace, which illustrates the power reflected back toward the source as a function of distance. ³ An arrow points to the location of the event type in the trace.
Description of Event Types Span Start Span Start The Span Start of a trace is the event that marks the beginning of the fiber span. By default, the Span Start is placed on the first event of a tested fiber (typically the first connector of the OTDR itself). You can make another event the start of the span you want to focus your analysis on. This will set the beginning of the events table at a specific event along the trace.
Description of Event Types Continuous Fiber Continuous Fiber Reflected power (dB) Continuous fiber Distance (km) This event indicates that the selected acquisition range was shorter than the fiber length. OTDR ³ The fiber end was not detected because the analysis process ended before reaching the end of the fiber. ³ The acquisition distance range should therefore be increased to a value greater than the fiber length. ³ There is no loss or reflectance specified for continuous fiber events.
Description of Event Types End of Analysis End of Analysis Reflected power (dB) Distance (km) This event indicates that the pulse width used did not provide enough dynamic range to get to the end of the fiber. 296 ³ The analysis ended before reaching the end of the fiber because the signal-to-noise ratio was too low. ³ The pulse width should therefore be increased so the signal reaches the end of the fiber with a sufficient signal-to-noise ratio.
Description of Event Types Non-Reflective Event Non-Reflective Event Reflected power (dB) Non-reflective event Linear downward slope due to Rayleigh backscatter Distance (km) This event is characterized by a sudden decrease in the Rayleigh backscatter signal level. It appears as a discontinuity in the downward slope of the trace signal. OTDR ³ This event is often caused by splices, macrobends, or microbends in the fiber. ³ A loss value is specified for non-reflective events.
Description of Event Types Reflective Event Reflective Event Reflected power (dB) Clipped level Reflective events Distance (km) Reflective events appear as spikes in the fiber trace. They are caused by an abrupt discontinuity in the index of refraction. 298 ³ Reflective events cause a significant portion of the energy initially launched into the fiber to be reflected back toward the source.
Description of Event Types Positive Event Positive Event Reflected power (dB) Positive event Distance (km) This event indicates a splice with an apparent gain, due to the junction of two fiber sections having different fiber backscatter characteristics (backscatter and backscatter capture coefficients). OTDR ³ A loss value is specified for positive events. The loss specified does not indicate the true loss of the event.
Description of Event Types Launch Level Launch Level Reflected power (dB) Launch level event position Second event Launch level Linear area Distance (km) This event indicates the level of the signal launched into the fiber. ³ The figure above shows how the launch level is measured. A straight line is plotted using least-square approximation to fit all trace points in the linear area between the first and second detected events.
Description of Event Types Fiber Section Fiber Section Reflected power (dB) Fiber section Fiber section Distance (km) This symbol denotes a fiber section with no event. OTDR ³ The sum of all fiber sections contained in an entire fiber trace equals the total fiber length. Detected events are distinct even if they cover more than one point on the trace. ³ A loss value is specified for fiber section events. No reflectance is specified for this type of event.
Description of Event Types Merged Event Merged Event Reflected power (dB) Reflective events Point A Point B Total loss (Δ dB) Merged Reflective event position Distance (km) This symbol denotes an event combined with one or more other events. It also indicates the total loss produced by the merged events following it in the events table. 302 ³ A Merged Event is composed of subevents.
Description of Event Types Merged Event ³ OTDR The total loss (Δ dB) produced by the events is measured by plotting two straight lines. ³ The first line is plotted by fitting, through least-square approximation, trace points in the linear area preceding the first event. ³ The second line is plotted by fitting, through least-square approximation, trace points in the linear area following the second event.
Description of Event Types Pass/Fail Tests Pass/Fail Tests As an example about pass/fail tests, let us consider the situation below: Merged event Merged sub-events: 2 reflective losses 1 non-reflective loss Thresholds: Event loss Reflective loss: 0.5 dB Non-reflective Loss: 0.2 dB For a merged event, it is possible to determine the global event loss, but not the contribution of each sub-event. This is why the pass/fail test may sometimes lead to “false positive” or “false negative” results.
Description of Event Types Pass/Fail Tests All Event Types Are Tested In the first case, where all event types are tested, the pass/fail conditions are as follows: ³ If the event loss is less than or equal to the smallest threshold value, then the event status is Pass. ³ If the event loss is greater than the sum of the number of sub-events of a type, multiplied by the threshold value for this event type, then the event status is Fail.
Description of Event Types Pass/Fail Tests Not All Event Types Are Tested In this situation, the only thing that we can clearly know is when the loss has a Pass status. If the global event loss is less than or equal to the smallest threshold value (a value that is tested, of course), we are sure that the merged event status is Pass. Otherwise, we cannot know, so the status of the event is Unknown.
Description of Event Types Pass/Fail Tests Effect of Event Status in the Global Trace Status ³ A trace status is, by default, set to Unknown. ³ If a trace is set to Fail once, it remains with that status (it cannot be set back to Pass or Unknown). ³ Whenever an event status is Fail, so is the trace status. ³ If an event status is Pass, the trace status can change from Unknown to Pass. ³ If an event status is Unknown, the trace status remains the same.
Description of Event Types Echo Echo Reflected power (dB) OTDR connector Second connector End connector Echo Lightwave travel Distance (km) This symbol indicates that a reflective event has been detected after the end of the fiber. 308 ³ In the example above, the launched pulse travels up to the end connector and is reflected back toward the OTDR. Then, it reaches the second connector and is reflected again toward the end connector. It is then reflected back to the OTDR.
Description of Event Types Reflective Event (Possible Echo) Reflective Event (Possible Echo) Reflected power (dB) OTDR connector Second connector Third connector Reflective event (possible echo) Distance (km) This symbol indicates a reflective event that can be a real reflection or an echo produced by another stronger reflection located closer to the source. ³ In the example above, the launched pulse hits the third connector, is reflected back to the OTDR and reflected again into the fiber.
C SCPI Command Reference This appendix presents detailed information on the commands and queries supplied with your Optical Time Domain Reflectometer. IMPORTANT Since the FTB-500 can house many instruments, you must explicitly specify which instrument you want to remotely control.
SCPI Command Reference Quick Reference Command Tree Quick Reference Command Tree Command Parameter(s) P. ABORt[1..n] 318 CALCulate[1..
SCPI Command Reference Quick Reference Command Tree Command SLOSs? THReshold Parameter(s) P. TRC1|TRC2|TRC3|TRC4,,,, 349 EOFiber TRC1|TRC2|TRC3|TRC4, EOFiber? TRC1|TRC2|TRC3|TRC4 REFLectance TRC1|TRC2|TRC3|TRC4, REFLectance? TRC1|TRC2|TRC3|TRC4 357 SLOSs TRC1|TRC2|TRC3|TRC4, 359 SLOSs? TRC1|TRC2|TRC3|TRC4 361 TRC1|TRC2|TRC3|TRC4 362 ,, 364 TORL? CONFigure[1..
SCPI Command Reference Quick Reference Command Tree Command Parameter(s) LOW? LIST? P.
SCPI Command Reference Quick Reference Command Tree Command Parameter(s) RANGe? CFConnector? 400 DURation? TRC1|TRC2|TRC3|TRC4 401 HRESolution? TRC1|TRC2|TRC3|TRC4 402 LFIBer? 403 PULSe? TRC1|TRC2|TRC3|TRC4 404 RANGe? TRC1|TRC2|TRC3|TRC4 405 STEP? TRC1|TRC2|TRC3|TRC4 406 TRACe[1..n] [DATA]? 407 POINts? 408 WAVelength? INITiate[1..
SCPI Command Reference Quick Reference Command Tree Command Parameter(s) P.
SCPI Command Reference Quick Reference Command Tree Command Parameter(s) CATalog? POINts? OTDR P.
SCPI Command Reference Product-Specific Commands—Description Product-Specific Commands—Description :ABORt[1..n] Description This command is used to stop the scan, measurement or acquisition in progress. This command is an event and, therefore, has no associated *RST condition or query form. However, on *RST, the equivalent of an ABORt command is performed on any acquisition in progress. *RST does not affect this command. 318 Syntax :ABORt[1..
SCPI Command Reference Product-Specific Commands—Description :CALCulate[1..n]:ANAlysis [:UNIDirectional] Description This command performs a unidirectional analysis. It creates or modifies the event table for the specified trace index acquisition data. For this command to be accepted, at least one acquisition must be performed. *RST does not affect this command. Syntax :CALCulate[1..
SCPI Command Reference Product-Specific Commands—Description :CALCulate[1..n]:ATTenuation? Description This query returns the value of the attenuation measured between two markers, for the trace corresponding to the specified trace index. *RST clears this setting. Syntax :CALCulate[1..n]:ATTenuation?TRC1|TR C2|TRC3|TRC4,, Parameter(s) ³ Label: The program data syntax for the first parameter is defined as a element.
SCPI Command Reference Product-Specific Commands—Description :CALCulate[1..n]:ATTenuation? Response(s) Attenuation: The response data syntax for is defined as a element. Returns the attenuation value in dB/meter, between marker A and marker B. OTDR Example(s) CONF:ACQ:MODE ACQUISITION INIT INIT:STAT? Returns 0 when acquisition is complete. CALC:ATT? TRC1,0,102.6 Ex.: Returns 1.963 CALC:ATT? TRC1,0 M,0.1026 KM Ex.: Returns 1.963 CALC:ATT? TRC1,0 KM,102.6 M Ex.
SCPI Command Reference Product-Specific Commands—Description :CALCulate[1..n]:CLValue? Description This query returns the curve level value at a specific position, for the trace corresponding to the specified trace index. *RST clears this setting. Syntax :CALCulate[1..n]:CLValue?TRC1|TRC2|T RC3|TRC4, Parameter(s) ³ Label: The program data syntax for the first parameter is defined as a element.
SCPI Command Reference Product-Specific Commands—Description :CALCulate[1..n]:CLValue? Response(s) Current Level Value: The response data syntax for is defined as a element. Returns the curve level value in dB, at the position specified by marker A. OTDR Example(s) CONF:ACQ:MODE ACQUISITION INIT INIT:STAT? Returns 0 when acquisition is complete. CALC:CLV? TRC1,100.3 Ex.: Returns –20.371 CALC:CLV? TRC1,0.1003 KM Ex.: Returns –20.371 CALC:CLV? TRC1,100.
SCPI Command Reference Product-Specific Commands—Description :CALCulate[1..n]:EVENt? Description This query returns an event from the event table after performing an analysis on the trace corresponding to the specified trace index. You must supply the index of the event that you want to retrieve. *RST clears the event table. Syntax :CALCulate[1..
SCPI Command Reference Product-Specific Commands—Description :CALCulate[1..n]:EVENt? Response(s) Event: The response data syntax for is defined as a element. Returns the event from the event table corresponding to the specified trace index.
SCPI Command Reference Product-Specific Commands—Description :CALCulate[1..n]:EVENt? The End of analysis event does not necessarily correspond to the last event of a fiber link. It indicates that the analysis has stopped before the end of the link because the instrument has reached the limit of its dynamic range. In most cases, the OTDR analysis will return the type of the last event as being either reflective or non-reflective (event type 3 or 2).
SCPI Command Reference Product-Specific Commands—Description :CALCulate[1..n]:EVENt:COUNt? Description This query returns the number of events after performing an analysis on the trace corresponding to the specified trace index. Since *RST clears the event table, the number of events will be 0. Syntax :CALCulate[1..n]:EVENt:COUNt?TRC1|TR C2|TRC3|TRC4 Parameter(s) Label: The program data syntax for the first parameter is defined as a element.
SCPI Command Reference Product-Specific Commands—Description :CALCulate[1..n]:EVENt:COUNt? Response Syntax Response(s) EventCount: The response data syntax for is defined as a element. Returns the number of available events for the specified trace index. Example(s) 328 CONF:ACQ:MODE ACQUISITION INIT INIT:STAT? Returns 0 when acquisition is complete. CALC:ANA TRC1 CALC:EVEN:COUN? TRC1 Ex.: Returns 4 (corresponding to 4 events).
SCPI Command Reference Product-Specific Commands—Description :CALCulate[1..n]:HFACtor Description This command sets the helix factor that will be used for the specified trace index. Using this command will recalculate the event table automatically. *RST clears this setting. Syntax OTDR :CALCulate[1..
SCPI Command Reference Product-Specific Commands—Description :CALCulate[1..n]:HFACtor Parameter(s) ³ Label: The program data syntax for the first parameter is defined as a element. The allowed elements for this parameter are: TRC1|TRC2|TRC3|TRC4. Trace index of the available wavelengths. ³ HelixFactor: The program data syntax for is defined as a element. Sets the helix factor.
SCPI Command Reference Product-Specific Commands—Description :CALCulate[1..n]:HFACtor? Description This query returns the helix factor used for the specified trace index. Since *RST clears the helix factor value, the returned value will be 0. Syntax :CALCulate[1..n]:HFACtor?TRC1|TRC2|T RC3|TRC4 Parameter(s) Label: The program data syntax for the first parameter is defined as a element.
SCPI Command Reference Product-Specific Commands—Description :CALCulate[1..n]:HFACtor? Response(s) HelixFactor: The response data syntax for is defined as a element. Returns the helix factor used by the trace corresponding to the specified trace index. 332 Example(s) CONF:ANA:HFAC 2 CONF:ACQ:MODE ACQUISITION INIT INIT:STAT? Returns 0 when acquisition is complete. CALC:HFAC? TRC1 Returns 2 See Also MMEMory[1..n]:LOAD:TRACe TRACe[1..
SCPI Command Reference Product-Specific Commands—Description :CALCulate[1..n]:INJection[:LEVel]? Description This query returns the injection level for the specified trace. The value is undefined if the trace is not analyzed. Syntax :CALCulate[1..n]:INJection[:LEVel]?TRC1 |TRC2|TRC3|TRC4 Parameter(s) Label: The program data syntax for the first parameter is defined as a element. The allowed elements for this parameter are: TRC1|TRC2|TRC3|TRC4.
SCPI Command Reference Product-Specific Commands—Description :CALCulate[1..n]:IORefraction Description This command sets the index of refraction that will be used for the trace corresponding to the specified trace index. Using this command will recalculate the event table automatically. *RST clears this setting. Syntax 334 :CALCulate[1..
SCPI Command Reference Product-Specific Commands—Description :CALCulate[1..n]:IORefraction Parameter(s) ³ Label: The program data syntax for the first parameter is defined as a element. The allowed elements for this parameter are: TRC1|TRC2|TRC3|TRC4. Trace index of the available wavelengths. ³ IOR: The program data syntax for is defined as a element. Sets the index of refraction. OTDR Example(s) CONF:ANA:IOR 1.
SCPI Command Reference Product-Specific Commands—Description :CALCulate[1..n]:IORefraction? Description This query returns the index of refraction used for the trace corresponding to the specified trace index. Since *RST clears the index of refraction value, the returned value will be 0. Syntax :CALCulate[1..n]:IORefraction?TRC1|TR C2|TRC3|TRC4 Parameter(s) Label: The program data syntax for the first parameter is defined as a element.
SCPI Command Reference Product-Specific Commands—Description :CALCulate[1..n]:IORefraction? Response(s) IOR: The response data syntax for is defined as a element. Returns the index of refraction used by the trace corresponding to the specified trace index. OTDR Example(s) CONF:ANA:IOR 1.5 CONF:ACQ:MODE ACQUISITION INIT INIT:STAT? Returns 0 when acquisition is complete. CALC:IOR? TRC1 Returns 1.5 See Also MMEMory[1..n]:LOAD:TRACe TRACe[1..
SCPI Command Reference Product-Specific Commands—Description :CALCulate[1..n]:LOSS? Description This query returns the loss between two markers measured by least-square approximation, for the trace corresponding to the specified trace index. *RST clears this value. Syntax :CALCulate[1..n]:LOSS?TRC1|TRC2|TRC 3|TRC4,, Parameter(s) ³ Label: The program data syntax for the first parameter is defined as a element.
SCPI Command Reference Product-Specific Commands—Description :CALCulate[1..n]:LOSS? Response(s) Loss: The response data syntax for is defined as a element. Returns the loss value in dB, between marker A and marker B. OTDR Example(s) CONF:ACQ:MODE ACQUISITION INIT INIT:STAT? Returns 0 when acquisition is complete. CALC:LOSS? TRC1,10,104 Ex.: Returns 0.458 CALC:LOSS? TRC1,10 M,0.104 KM Ex.: Returns 0.458 CALC:LOSS? TRC1,0.01 KM,104 M Ex.: Returns 0.
SCPI Command Reference Product-Specific Commands—Description :CALCulate[1..n]:ORL? Description This query returns the value of the Optical Return Loss measured between two markers, for the trace corresponding to the specified trace index. *RST clears this value. Syntax :CALCulate[1..n]:ORL?TRC1|TRC2|TRC3 |TRC4,, Parameter(s) ³ Label: The program data syntax for the first parameter is defined as a element.
SCPI Command Reference Product-Specific Commands—Description :CALCulate[1..n]:ORL? Response(s) ORL: The response data syntax for is defined as a element. Returns the Optical Return Loss value in dB, between marker A and marker B. OTDR Example(s) CONF:ACQ:MODE ACQUISITION INIT INIT:STAT? Returns 0 when acquisition is complete. CALC:ORL? TRC1,10,100 Ex.: Returns 30.305 CALC:ORL? TRC1,10 M, 0.100 KM Ex.: Returns 30.305 CALC:ORL? TRC1,0.01 KM,100 M Ex.: Returns 30.
SCPI Command Reference Product-Specific Commands—Description :CALCulate[1..n]:REFLectance? Description This query returns the reflectance value measured between two markers, for the trace corresponding to the specified trace index. *RST clears this value. Syntax 342 :CALCulate[1..
SCPI Command Reference Product-Specific Commands—Description :CALCulate[1..n]:REFLectance? Parameter(s) ³ Label: The program data syntax for the first parameter is defined as a element. The allowed elements for this parameter are: TRC1|TRC2|TRC3|TRC4. Trace index of the available wavelengths. ³ SubMarkerA: The program data syntax for is defined as a element. Specifies the submarker A position, in meters.
SCPI Command Reference Product-Specific Commands—Description :CALCulate[1..n]:REFLectance? Response(s) Reflectance: The response data syntax for is defined as a element. Returns the reflectance value in dB, calculated using all three markers. 344 Example(s) CONF:ACQ:MODE ACQUISITION INIT INIT:STAT? Returns 0 when acquisition is complete. CALC:REF? TRC1,0,0.1 KM,200 Ex.: Returns – 24.549 CALC:REF? TRC1,0 M,100,200 M Ex.: Returns – 24.
SCPI Command Reference Product-Specific Commands—Description :CALCulate[1..n]:RBScatter Description This command sets the Rayleigh backscatter that will be used for the trace corresponding to the specified trace index. Using this command will recalculate the event table automatically. *RST clears this setting. Syntax OTDR :CALCulate[1..
SCPI Command Reference Product-Specific Commands—Description :CALCulate[1..n]:RBScatter Parameter(s) ³ Label: The program data syntax for the first parameter is defined as a element. The allowed elements for this parameter are: TRC1|TRC2|TRC3|TRC4. Trace index of the available wavelengths. ³ RBS: The program data syntax for is defined as a element. Sets the Rayleigh backscatter. 346 Example(s) CONF:ANA:RBS –79.
SCPI Command Reference Product-Specific Commands—Description :CALCulate[1..n]:RBScatter? Description This query returns the Rayleigh backscatter used for the trace corresponding to the specified trace index. Since *RST clears the RBS value, the returned value will be 0. Syntax :CALCulate[1..n]:RBScatter?TRC1|TRC2| TRC3|TRC4 Parameter(s) Label: The program data syntax for the first parameter is defined as a element.
SCPI Command Reference Product-Specific Commands—Description :CALCulate[1..n]:RBScatter? 348 Example(s) CONF:ANA:RBS –80 CONF:ACQ:MODE ACQUISITION INIT INIT:STAT? Returns 0 when acquisition is complete. CALC:RBS? TRC1 Returns –80 Notes Reset to a new default value when wavelength and range change. See Also MMEMory[1..n]:LOAD:TRACe TRACe[1..
SCPI Command Reference Product-Specific Commands—Description :CALCulate[1..n]:SLOSs? Description This query returns the value of the measured loss for a given splice identified using four markers, for the trace corresponding to the specified trace index. *RST clears this value. Syntax :CALCulate[1..n]:SLOSs?TRC1|TRC2|TR C3|TRC4,,,, Parameter(s) ³ Label: The program data syntax for the first parameter is defined as a element.
SCPI Command Reference Product-Specific Commands—Description :CALCulate[1..n]:SLOSs? Parameter(s) ³ MarkerB: The program data syntax for is defined as a element. Specifies the marker B position, in meters. ³ SubMarkerB: The program data syntax for is defined as a element. Specifies the submarker B position, in meters. Return the splice loss value, calculated using all four markers.
SCPI Command Reference Product-Specific Commands—Description :CALCulate[1..n]:SLOSs? CALC:SLOS? TRC1,10 M,100 M,200 M,300 M Ex.: Returns 0.058 CALC:SLOS? TRC1,0.01 KM, 0.1 KM, 0.2 KM,0.3 KM Ex.: Returns 0.058 OTDR Notes See the section on loss measurement in the FTB-7000 Optical Time Domain Reflectometer user guide. See Also CALCulate[1..n]:ANAlysis:[UNIDirectional] CALCulate[1..n]:EVENt:COUNt? CALCulate[1..n]:EVENt? MMEMory[1..n]:LOAD:TRACe TRACe[1..
SCPI Command Reference Product-Specific Commands—Description :CALCulate[1..n]:THReshold:EOFiber Description This command sets the end-of-fiber threshold that will be used for the specified trace index. Using this command will regenerate the event table automatically. *RST clears this setting. Syntax 352 :CALCulate[1..
SCPI Command Reference Product-Specific Commands—Description :CALCulate[1..n]:THReshold:EOFiber Parameter(s) ³ Label: The program data syntax for the first parameter is defined as a element. The allowed elements for this parameter are: TRC1|TRC2|TRC3|TRC4. Trace index of the available wavelengths. ³ End-of-Fiber: The program data syntax for is defined as a element. Sets the end-of-fiber threshold.
SCPI Command Reference Product-Specific Commands—Description :CALCulate[1..n]:THReshold:EOFiber? Description This query returns the end-of-fiber threshold used for the specified trace index. *RST clears this value. Syntax :CALCulate[1..n]:THReshold:EOFiber?TR C1|TRC2|TRC3|TRC4 Parameter(s) Label: The program data syntax for the first parameter is defined as a element. The allowed elements for this parameter are: TRC1|TRC2|TRC3|TRC4.
SCPI Command Reference Product-Specific Commands—Description :CALCulate[1..n]:THReshold: REFLectance Description This command sets the reflectance threshold that will be used for the specified trace index. Using this command will regenerate the event table automatically. *RST clears this setting. Syntax OTDR :CALCulate[1..
SCPI Command Reference Product-Specific Commands—Description :CALCulate[1..n]:THReshold: REFLectance Parameter(s) ³ Label: The program data syntax for the first parameter is defined as a element. The allowed elements for this parameter are: TRC1|TRC2|TRC3|TRC4. Trace index of the available wavelengths. ³ Reflectance: The program data syntax for is defined as a element. Sets the reflectance threshold.
SCPI Command Reference Product-Specific Commands—Description :CALCulate[1..n]:THReshold: REFLectance? Description This query returns the reflectance threshold used for the specified trace index. *RST clears this value. Syntax :CALCulate[1..n]:THReshold:REFLectance?TRC1|TRC2|TRC3|TRC4 Parameter(s) Label: The program data syntax for the first parameter is defined as a element. The allowed elements for this parameter are: TRC1|TRC2|TRC3|TRC4.
SCPI Command Reference Product-Specific Commands—Description :CALCulate[1..n]:THReshold: REFLectance? Response(s) Reflectance: The response data syntax for is defined as a element. Returns the reflectance threshold used by the trace corresponding to the specified trace index. 358 Example(s) CONF:ANA:THR:REFL -72.1 CONF:ACQ:MODE ACQ INIT INIT:STAT? Returns 0 when acquisition is complete. CALC:THR:REFL? TRC1 Returns -72.1 See Also MMEMory[1..
SCPI Command Reference Product-Specific Commands—Description :CALCulate[1..n]:THReshold:SLOSs Description This command sets the splice loss threshold that will be used for the specified trace index. Using this command will regenerate the event table automatically. *RST clears this setting. Syntax OTDR :CALCulate[1..
SCPI Command Reference Product-Specific Commands—Description :CALCulate[1..n]:THReshold:SLOSs Parameter(s) ³ Label: The program data syntax for the first parameter is defined as a element. The allowed elements for this parameter are: TRC1|TRC2|TRC3|TRC4. Trace index of the available wavelengths. ³ Splice Loss: The program data syntax for is defined as a element. Sets the splice loss threshold.
SCPI Command Reference Product-Specific Commands—Description :CALCulate[1..n]:THReshold:SLOSs? Description This query returns the splice loss threshold used for the specified trace index. *RST clears this value. Syntax :CALCulate[1..n]:THReshold:SLOSs?TRC 1|TRC2|TRC3|TRC4 Parameter(s) Label: The program data syntax for the first parameter is defined as a element. The allowed elements for this parameter are: TRC1|TRC2|TRC3|TRC4.
SCPI Command Reference Product-Specific Commands—Description :CALCulate[1..n]:TORL? Description This query returns the sum of all optical return loss (ORL) values measured on the total fiber length, for the trace corresponding to the specified trace index. This total ORL value does not include the launch reflection. A negative total value indicates that the real value is smaller. *RST clears this value. Syntax :CALCulate[1..
SCPI Command Reference Product-Specific Commands—Description :CALCulate[1..n]:TORL? Response(s) TotalOrl: The response data syntax for is defined as a element. Returns the total ORL value, in dB. OTDR Example(s) CONF:ACQ:MODE ACQUISITION INIT INIT:STAT? Returns 0 when acquisition is complete. CALC:ANA TRC1 CALC:TORL? TRC1 Ex.: Returns 20.416 See Also MMEMory[1..n]:LOAD:TRACe TRACe[1..
SCPI Command Reference Product-Specific Commands—Description :CONFigure[1..n]:ACQuisition Description This command specifies the wavelength, range and pulse that will be used for the next acquisition. *RST does not affect this command. Syntax :CONFigure[1..n]:ACQuisition,, Parameter(s) ³ Wavelength: The program data syntax for is defined as a element. Sets the wavelength, in meters.
SCPI Command Reference Product-Specific Commands—Description :CONFigure[1..n]:ACQuisition Example(s) CONF:ACQ:WAV:LIST? Returns the available wavelength list CONF:ACQ:RANG:LIST? 1310 NM Returns the available range list (where 1310 is an item of CONF:ACQ:WAV:LIST?) CONF:ACQ:PULS:LIST? 1310 NM,1250 M Returns the available pulse list (where 1250 is an item of CONF:ACQ:RANG:LIST?) CONF:ACQ 1310 NM,1250 M,10 NS (where 10 is an item of CONF:ACQ:PULS:LIST?) See Also OTDR CONFigure[1..
SCPI Command Reference Product-Specific Commands—Description :CONFigure[1..n]:ACQuisition: DURation Description This command specifies the duration that will be used for the next acquisition. *RST reverts this setting to default value. Syntax :CONFigure[1..n]:ACQuisition:DURation |MAXimum|MINimum|DEFault Parameter(s) Duration: The program data syntax for is defined as a element. The special forms MINimum, MAXimum and DEFault are accepted on input.
SCPI Command Reference Product-Specific Commands—Description :CONFigure[1..n]:ACQuisition: DURation? Description This query returns the current duration setting. *RST reverts this setting to default value. Syntax :CONFigure[1..n]:ACQuisition:DURation?[MINimum|MAXimum|DEFault] Parameter(s) Parameter 1: The program data syntax for the first parameter is defined as a element. The allowed elements for this parameter are: MINimum|MAXimum|DEFault.
SCPI Command Reference Product-Specific Commands—Description :CONFigure[1..n]:ACQuisition: DURation? Response(s) Duration: The response data syntax for is defined as a element. Returns the duration, in seconds. 368 Example(s) CONF:ACQ:DUR 10 CONF:ACQ:DUR? Returns 10 See Also FETCh[1..n]:DURation? FETCh[1..
SCPI Command Reference Product-Specific Commands—Description :CONFigure[1..n]:ACQuisition: HRESolution Description This command enables the high-resolution feature that allows you to obtain more data points per acquisition (greater distance resolution for the trace). *RST reverts this setting to default value. Syntax :CONFigure[1..n]:ACQuisition:HRESolution Parameter(s) HighResolution: The program data syntax for is defined as a element.
SCPI Command Reference Product-Specific Commands—Description :CONFigure[1..n]:ACQuisition: HRESolution? Description This query returns a value indicating if the high-resolution feature is enabled for the next acquisition. *RST reverts this setting to default value. Syntax :CONFigure[1..n]:ACQuisition:HRESolution? Parameter(s) None Response Syntax Response(s) HighResolution: The response data syntax for is defined as a element.
SCPI Command Reference Product-Specific Commands—Description :CONFigure[1..n]:ACQuisition:MODE Description This command specifies the mode that will be used for the next acquisition. Acquisition: Allows the OTDR to perform a standard acquisition. Auto Setting: Lets the OTDR evaluates the length of the fiber and finds the appropriate range and pulse width. Check First Connector: Used to detect a low injection level. Real Time: Used to view sudden changes in the fiber under test.
SCPI Command Reference Product-Specific Commands—Description :CONFigure[1..n]:ACQuisition:MODE Sets the acquisition mode. 372 Example(s) CONF:ACQ:MODE? Ex.: Returns ASETTING CONF:ACQ:MODE ACQ CONF:ACQ:MODE? Returns ACQUISITION See Also INITiate[1..n][:IMMediate] ABORt[1..
SCPI Command Reference Product-Specific Commands—Description :CONFigure[1..n]:ACQuisition:MODE? Description This query returns the current acquisition mode. *RST sets the current acquisition mode to ACQUISITION. Syntax :CONFigure[1..n]:ACQuisition:MODE? Parameter(s) None Response Syntax Response(s) Mode: The response data syntax for is defined as a element. Returns the current acquisition mode.
SCPI Command Reference Product-Specific Commands—Description :CONFigure[1..n]:ACQuisition:PULSe? Description This query returns the current pulse setting. *RST reverts this setting to default value. Syntax :CONFigure[1..n]:ACQuisition:PULSe? Parameter(s) None Response Syntax Response(s) Pulse: The response data syntax for is defined as a element. Returns the pulse, in seconds.
SCPI Command Reference Product-Specific Commands—Description :CONFigure[1..n]:ACQuisition:PULSe: LIST? Description This query returns the list of available pulses for the specified wavelength and range. *RST does not affect this command. Syntax :CONFigure[1..n]:ACQuisition:PULSe:LIST?, Parameter(s) ³ Wavelength: The program data syntax for is defined as a element.
SCPI Command Reference Product-Specific Commands—Description :CONFigure[1..n]:ACQuisition:PULSe: LIST? Response(s) PulseList: The response data syntax for is defined as a element. Returns the list of valid pulses, in seconds. 376 Example(s) CONF:ACQ:WAV:LIST? Returns a wavelength list.
SCPI Command Reference Product-Specific Commands—Description :CONFigure[1..n]:ACQuisition:RANGe? Description This query returns the current range setting. *RST reverts this setting to default value. Syntax :CONFigure[1..n]:ACQuisition:RANGe? Parameter(s) None Response Syntax Response(s) Range: The response data syntax for is defined as a element. Returns the range, in meters. OTDR Example(s) CONF:ACQ 1310 NM,1250 M,10 NS CONF:ACQ:RANG? Returns 1.
SCPI Command Reference Product-Specific Commands—Description :CONFigure[1..n]:ACQuisition:RANGe: LIMit:HIGH? Description This query returns the highest possible value for the acquisition range, at the specified wavelength. *RST does not affect this command. Syntax :CONFigure[1..n]:ACQuisition:RANGe:LIMit:HIGH ? Parameter(s) Wavelength: The program data syntax for is defined as a element.
SCPI Command Reference Product-Specific Commands—Description :CONFigure[1..n]:ACQuisition:RANGe: LIMit:LOW? Description This query returns the lowest possible value for the acquisition range, at the specified wavelength. *RST does not affect this command. Syntax :CONFigure[1..n]:ACQuisition:RANGe:LIMit:LOW ? Parameter(s) Wavelength: The program data syntax for is defined as a element.
SCPI Command Reference Product-Specific Commands—Description :CONFigure[1..n]:ACQuisition:RANGe: LIST? Description This query returns the list of available ranges for the specified wavelength. *RST does not affect this command. Syntax :CONFigure[1..n]:ACQuisition:RANGe:LIST? Parameter(s) Wavelength: The program data syntax for is defined as a element. Specifies the wavelength, in meters, that filters out invalid ranges from all ranges.
SCPI Command Reference Product-Specific Commands—Description :CONFigure[1..n]:ACQuisition: WAVelength? Description This query returns the current wavelength setting. *RST reverts this setting to default value. Syntax :CONFigure[1..n]:ACQuisition:WAVelength? Parameter(s) None Response Syntax Response(s) Wavelength: The response data syntax for is defined as a element. Returns the wavelength, in meters.
SCPI Command Reference Product-Specific Commands—Description :CONFigure[1..n]:ACQuisition: WAVelength:LIST? Description This query returns the list of all available wavelengths. *RST does not affect this command. Syntax :CONFigure[1..n]:ACQuisition:WAVelength:LIST? Parameter(s) None Response Syntax Response(s) WavelengthList: The response data syntax for is defined as a element.
SCPI Command Reference Product-Specific Commands—Description :CONFigure[1..n]:ANAlysis:HFACtor Description This command sets the helix factor that will be used for the next acquisition. *RST returns this setting to default value. Syntax :CONFigure[1..n]:ANAlysis:HFACtor|MAXimum|MINimum|DEFault Parameter(s) HelixFactor: The program data syntax for is defined as a element. The special forms MINimum, MAXimum and DEFault are accepted on input.
SCPI Command Reference Product-Specific Commands—Description :CONFigure[1..n]:ANAlysis:HFACtor? Description This query returns the helix factor that will be used for the next acquisition. *RST reverts this setting to default value. Syntax :CONFigure[1..n]:ANAlysis:HFACtor?[MIN imum|MAXimum|DEFault] Parameter(s) Parameter 1: The program data syntax for the first parameter is defined as a element.
SCPI Command Reference Product-Specific Commands—Description :CONFigure[1..n]:ANAlysis: IORefraction Description This command sets the index of refraction that will be used for the next acquisition. *RST reverts this setting to default value. Syntax :CONFigure[1..n]:ANAlysis:IORefraction |MAXimum|MINimum|DEFault Parameter(s) IOR: The program data syntax for is defined as a element. The special forms MINimum, MAXimum and DEFault are accepted on input.
SCPI Command Reference Product-Specific Commands—Description :CONFigure[1..n]:ANAlysis: IORefraction? Description This query returns the index of refraction that will be used for the next acquisition. *RST reverts this setting to default value. Syntax :CONFigure[1..n]:ANAlysis:IORefraction?[MINimum|MAXimum|DEFault] Parameter(s) Parameter 1: The program data syntax for the first parameter is defined as a element.
SCPI Command Reference Product-Specific Commands—Description :CONFigure[1..n]:ANAlysis:RBScatter Description This command sets the Rayleigh backscatter that will be used for the next acquisition. *RST reverts this setting to default value. Syntax :CONFigure[1..n]:ANAlysis:RBScatter|MAXimum|MINimum|DEFault Parameter(s) RBS: The program data syntax for is defined as a element. The special forms MINimum, MAXimum and DEFault are accepted on input.
SCPI Command Reference Product-Specific Commands—Description :CONFigure[1..n]:ANAlysis: RBScatter? Description This query returns the Rayleigh backscatter that will be used for the next acquisition. *RST reverts this setting to default value. Syntax :CONFigure[1..n]:ANAlysis:RBScatter?[MI Nimum|MAXimum|DEFault] Parameter(s) Parameter 1: The program data syntax for the first parameter is defined as a element.
SCPI Command Reference Product-Specific Commands—Description :CONFigure[1..n]:ANAlysis:THReshold: EOFiber Description This command sets the end-of-fiber threshold that will be used for the next acquisition. *RST returns this setting to default value. Syntax :CONFigure[1..n]:ANAlysis:THReshold:EOFiber< wsp>|MAXimum|MINimum|DE Fault Parameter(s) End-of-Fiber: The program data syntax for is defined as a element.
SCPI Command Reference Product-Specific Commands—Description :CONFigure[1..n]:ANAlysis:THReshold: EOFiber? Description This query returns the end-of-fiber threshold that will be used for the next acquisition. *RST reverts this setting to default value. Syntax :CONFigure[1..n]:ANAlysis:THReshold:EOFiber?[ MINimum|MAXimum|DEFault] Parameter(s) Parameter 1: The program data syntax for the first parameter is defined as a element.
SCPI Command Reference Product-Specific Commands—Description :CONFigure[1..n]:ANAlysis:THReshold: REFLectance Description This command sets the reflectance threshold that will be used for the next acquisition. *RST returns this setting to default value. Syntax :CONFigure[1..n]:ANAlysis:THReshold:REFLecta nce|MAXimum|MINimu m|DEFault Parameter(s) Reflectance: The program data syntax for is defined as a element.
SCPI Command Reference Product-Specific Commands—Description :CONFigure[1..n]:ANAlysis:THReshold: REFLectance? Description This query returns the reflectance threshold that will be used for the next acquisition. *RST reverts this setting to default value. Syntax :CONFigure[1..n]:ANAlysis:THReshold:REFLecta nce?[MINimum|MAXimum|DEFault] Parameter(s) Parameter 1: The program data syntax for the first parameter is defined as a element.
SCPI Command Reference Product-Specific Commands—Description :CONFigure[1..n]:ANAlysis:THReshold: SLOSs Description This command sets the splice loss threshold that will be used for the next acquisition. *RST returns this setting to default value. Syntax :CONFigure[1..n]:ANAlysis:THReshold:SLOSs|MAXimum|MINimum|DEFault Parameter(s) Splice Loss: The program data syntax for is defined as a element.
SCPI Command Reference Product-Specific Commands—Description :CONFigure[1..n]:ANAlysis:THReshold: SLOSs? Description This query returns the splice loss threshold that will be used for the next acquisition. *RST reverts this setting to default value. Syntax :CONFigure[1..n]:ANAlysis:THReshold:SLOSs?[< wsp>MINimum|MAXimum|DEFault] Parameter(s) Parameter 1: The program data syntax for the first parameter is defined as a element.
SCPI Command Reference Product-Specific Commands—Description :ERRor[1..n]? Description This command queries the last error or event. *RST does not affect this query. Syntax :ERRor[1..n]? Parameter(s) None Response Syntax Response(s) Error: The response data syntax for is defined as a element. Returns the specified error. A zero value in the number field indicates that no error or event has occurred.
SCPI Command Reference Product-Specific Commands—Description :ERRor[1..n]? D = HelpFile E = HelpContext F = Interface G = AdditionalInfo 396 Example(s) ERR? Ex.: Returns: "#10", if no error ERE? Ex.: Returns: #3126Exfo.Instrument7000.Instrument7000.1,-10 73471488,"An offset error occured in the module.",,,"{...}","Instrument7000:Initialize" Notes {...
SCPI Command Reference Product-Specific Commands—Description :FETCh[1..n]:ASETting:DURation? Description This query returns the duration found after an initiate (INIT) command. Note that acquisition mode (CONF:ACQ:MODE) must be set to ASETting. Since *RST clears the duration value, the returned value will be 0. Syntax :FETCh[1..
SCPI Command Reference Product-Specific Commands—Description :FETCh[1..n]:ASETting:PULSe? Description This query returns the pulse found after an initiate (INIT) command. Note that acquisition mode (CONF:ACQ:MODE) must be set to ASETting. Since *RST clears the pulse value, the returned value will be 0. Syntax :FETCh[1..n]:ASETting:PULSe? Parameter(s) None Response Syntax Response(s) Pulse: The response data syntax for is defined as a element.
SCPI Command Reference Product-Specific Commands—Description :FETCh[1..n]:ASETting:RANGe? Description This query returns the range found after an initiate (INIT) command. Note that acquisition mode (CONF:ACQ:MODE) must be set to ASETting. Since *RST clears the range value, the returned value will be 0. Syntax :FETCh[1..n]:ASETting:RANGe? Parameter(s) None Response Syntax Response(s) Range: The response data syntax for is defined as a element.
SCPI Command Reference Product-Specific Commands—Description :FETCh[1..n]:CFConnector? Description This query returns a state indicating whether the first connector has been found or not, after an initiate (INIT) command. Note that acquisition mode (CONF:ACQ:MODE) must be set to CFConnector. *RST clears this setting. Syntax :FETCh[1..
SCPI Command Reference Product-Specific Commands—Description :FETCh[1..n]:DURation? Description This query returns the duration for the trace corresponding to the specified trace index. *RST clears this setting. Syntax :FETCh[1..n]:DURation?TRC1|TRC2|TRC 3|TRC4 Parameter(s) Label: The program data syntax for the first parameter is defined as a element. The allowed elements for this parameter are: TRC1|TRC2|TRC3|TRC4.
SCPI Command Reference Product-Specific Commands—Description :FETCh[1..n]:HRESolution? Description This query returns a value indicating if the high-resolution feature was enabled for the current trace. *RST clears this setting. Syntax :FETCh[1..n]:HRESolution?TRC1|TRC2|T RC3|TRC4 Parameter(s) Label: The program data syntax for the first parameter is defined as a element. The allowed elements for this parameter are: TRC1|TRC2|TRC3|TRC4.
SCPI Command Reference Product-Specific Commands—Description :FETCh[1..n]:LFIBer? Description This query returns a state indicating whether live activity has been found on the fiber, after an initiate (INIT) command. This is valid for all acquisition modes. *RST clears this setting. Syntax :FETCh[1..n]:LFIBer? Parameter(s) None Response Syntax Response(s) LiveFiberState: The response data syntax for is defined as a element.
SCPI Command Reference Product-Specific Commands—Description :FETCh[1..n]:PULSe? Description This query returns the pulse for the specified trace index. *RST clears this setting. Syntax :FETCh[1..n]:PULSe?TRC1|TRC2|TRC3| TRC4 Parameter(s) Label: The program data syntax for the first parameter is defined as a element. The allowed elements for this parameter are: TRC1|TRC2|TRC3|TRC4. Trace index of the available wavelengths.
SCPI Command Reference Product-Specific Commands—Description :FETCh[1..n]:RANGe? Description This query returns the range for the trace corresponding to the specified trace index. *RST clears this setting. Syntax :FETCh[1..n]:RANGe?TRC1|TRC2|TRC3| TRC4 Parameter(s) Label: The program data syntax for the first parameter is defined as a element. The allowed elements for this parameter are: TRC1|TRC2|TRC3|TRC4.
SCPI Command Reference Product-Specific Commands—Description :FETCh[1..n]:STEP? Description This query returns the step between each point of the trace corresponding to the specified trace index. *RST clears this setting. Syntax :FETCh[1..n]:STEP?TRC1|TRC2|TRC3|T RC4 Parameter(s) Label: The program data syntax for the first parameter is defined as a element. The allowed elements for this parameter are: TRC1|TRC2|TRC3|TRC4.
SCPI Command Reference Product-Specific Commands—Description :FETCh[1..n]:TRACe[1..n][:DATA]? Description This query returns all the points of a trace. It can be used with already-completed acquisitions or acquisitions in progress. *RST clears this setting. Syntax :FETCh[1..n]:TRACe[1..n][:DATA]? Parameter(s) None Response Syntax Response(s) Data: The response data syntax for is defined as a element.
SCPI Command Reference Product-Specific Commands—Description :FETCh[1..n]:TRACe[1..n]:POINts? Description This query returns the number of points of the trace. It can be used with already-completed acquisitions or acquisitions in progress. *RST clears this setting. Syntax :FETCh[1..n]:TRACe[1..n]:POINts? Parameter(s) None Response Syntax Response(s) PointsCount: The response data syntax for is defined as a element.
SCPI Command Reference Product-Specific Commands—Description :FETCh[1..n]:WAVelength? Description This query returns the wavelength for the trace corresponding to the specified trace index. *RST clears this setting. Syntax :FETCh[1..n]:WAVelength?TRC1|TRC2|T RC3|TRC4 Parameter(s) Label: The program data syntax for the first parameter is defined as a element. The allowed elements for this parameter are: TRC1|TRC2|TRC3|TRC4.
SCPI Command Reference Product-Specific Commands—Description :INITiate[1..n][:IMMediate] Description This command starts the acquisition according to the active acquisition mode. Acquisition mode: ACQuisition: Acquisition stops after the duration value has elapsed. REALtime: Acquisition is in progress until an abort event is sent. CFConnector: Acquisition stops after determining the injection level at the first connector. ASETting: Acquisition stops after determining the adequate range and pulse values.
SCPI Command Reference Product-Specific Commands—Description :INITiate[1..n]:STATe? Description This query returns a state indicating whether an acquisition is in progress or stopped (ABORt). *RST sets state to OFF (all acquisitions are stopped). Syntax :INITiate[1..n]:STATe? Parameter(s) None Response Syntax Response(s) AcquisitionState: The response data syntax for is defined as a element.
SCPI Command Reference Product-Specific Commands—Description :MMEMory[1..n]:DATA:TYPE? Description This query returns the current file format. *RST sets type to BINARY. Syntax :MMEMory[1..n]:DATA:TYPE? Parameter(s) None Response Syntax Response(s) FileType: The response data syntax for is defined as a element. Returns the file format.
SCPI Command Reference Product-Specific Commands—Description :MMEMory[1..n]:LOAD:NAME? Description This query returns the name of the current loaded file. *RST clears this setting. Syntax :MMEMory[1..n]:LOAD:NAME? Parameter(s) None Response Syntax Response(s) FileName: The response data syntax for is defined as a element. Returns the loaded file name. OTDR Example(s) MMEM:LOAD:TRAC "Trace1.trc" MMEM:LOAD:NAME? Returns "Trace1.
SCPI Command Reference Product-Specific Commands—Description :MMEMory[1..n]:LOAD:TRACe Description This command is used to load traces from a file. *RST does not affect this command. Syntax :MMEMory[1..n]:LOAD:TRACe Parameter(s) FileName: The program data syntax for is defined as a element. The parameter can either be only the filename or the filename and its path. If no path is specified, the default path is used.
SCPI Command Reference Product-Specific Commands—Description :MMEMory[1..n]:STORe:TRACe Description This command is used to store traces to a file. *RST does not affect this command. Syntax :MMEMory[1..n]:STORe:TRACe Parameter(s) FileName: The program data syntax for is defined as a element. The parameter can either be only the filename or the filename and its path. If no path is specified, the default path is used.
SCPI Command Reference Product-Specific Commands—Description :MMEMory[1..n]:STORe:TRACe: OVERwrite Description This command specifies if an existing file can be overwritten without generating an error when the MMEMory:STORe:TRACe command is used. Attempting to save a new file under the name of an existing file will generate an error if the value is set to OFF. *RST sets overwrite to OFF. Syntax :MMEMory[1..
SCPI Command Reference Product-Specific Commands—Description :MMEMory[1..n]:STORe:TRACe: OVERwrite Enables or disables the right to overwrite an existing file. Example(s) CONF:ACQ:MODE ACQ INIT INIT:STAT? Returns 0 when acquisition is complete. MMEM:STOR:TRAC:OVER? Ex.: Returns 0 MMEM:STOR:TRAC "Trace3.trc" If file already exists, an error occurs. MMEM:STOR:TRAC:OVER 1 MMEM:STOR:TRAC "Trace3.trc" File will save without generating errors.
SCPI Command Reference Product-Specific Commands—Description :MMEMory[1..n]:STORe:TRACe: OVERwrite? Description This query indicates if an existing file can be overwritten. *RST sets overwrite to OFF. Syntax :MMEMory[1..n]:STORe:TRACe:OVERwrite? Parameter(s) None Response Syntax Response(s) Overwrite: The response data syntax for is defined as a element. Overwrite state. 1 - (TRUE) Always overwrites file.
SCPI Command Reference Product-Specific Commands—Description :SOURce[1..n]:FREQuency:BURSt Description This command sets the frequency of the source''s ON-OFF modulated signal during its ON period (modulation for fiber identification). This signal is referred to as "burst signal" . *RST reverts this setting to its default value. Syntax :SOURce[1..
SCPI Command Reference Product-Specific Commands—Description :SOURce[1..n]:FREQuency:BURSt MINimum allows to set the instrument to the smallest supported value. MAXimum allows to set the instrument to the greatest supported value. DEFault allows the instrument to select a value for the parameter. Frequency of the sources burst signal, in hertz. 420 Example(s) SOUR:FREQ:BURS 1000 SOUR:FREQ:BURS:STAT ON SOUR:POW:STAT:TIME 60 SOUR:POW:STAT ON See Also SOURce[1..
SCPI Command Reference Product-Specific Commands—Description :SOURce[1..n]:FREQuency:BURSt? Description This query returns the frequency of the source's ON-OFF modulated signal during its ON period (modulation for fiber identification). This signal is referred to as "burst signal" . *RST reverts this setting to its default value. Syntax :SOURce[1..
SCPI Command Reference Product-Specific Commands—Description :SOURce[1..n]:FREQuency:BURSt? Response(s) BurstFrequency: The response data syntax for is defined as a element. Frequency of the sources burst signal, in hertz. 422 Example(s) SOUR:FREQ:BURS 1000 SOUR:FREQ:BURS? Returns 1.000000e+3 See Also SOURce[1..n]:FREQuency:BURSt SOURce[1..n]:FREQuency:BURSt:STATe SOURce[1..n]:FREQuency:PRF SOURce[1..n]:FREQuency:PRF:STATe SOURce[1..
SCPI Command Reference Product-Specific Commands—Description :SOURce[1..n]:FREQuency:BURSt:STATe Description This command turns on or off the burst signal of the source (modulation for fiber identification). At *RST, the burst signal state of the source is set to OFF (source emits in continuous output- CW). Syntax :SOURce[1..n]:FREQuency:BURSt:STATe Parameter(s) State: The program data syntax for is defined as a element.
SCPI Command Reference Product-Specific Commands—Description :SOURce[1..n]:FREQuency:BURSt: STATe? Description This query returns a value indicating the current state of the source's burst signal. At *RST, the burst signal state of the source is set to OFF (source emits in continuous output- CW). Syntax :SOURce[1..n]:FREQuency:BURSt:STATe? Parameter(s) None Response Syntax Response(s) State: The response data syntax for is defined as a element.
SCPI Command Reference Product-Specific Commands—Description :SOURce[1..n]:FREQuency:PRF Description This command sets the repetition frequency of the on-off modulation of the source signal that is periodically switched on and off (flashing pattern). This characteristic is referred to as "Pulsed Repetition Frequency" (PRF). *RST reverts this setting to its default value. Syntax :SOURce[1..
SCPI Command Reference Product-Specific Commands—Description :SOURce[1..n]:FREQuency:PRF 426 Example(s) SOUR:FREQ:PRF 1000 SOUR:FREQ:PRF:STAT ON SOUR:POW:STAT:TIME 60 SOUR:POW:STAT ON Notes Using a flashing pattern makes fiber identification easier. In a flashing pattern, the modulated signal will be sent for 1 second, then will be off for the next second, then will be sent again for 1 second, and so on. See Also SOURce[1..n]:FREQuency:PRF? SOURce[1..n]:FREQuency:PRF:STATe SOURce[1..
SCPI Command Reference Product-Specific Commands—Description :SOURce[1..n]:FREQuency:PRF? Description This query returns the repetition frequency of the on-off modulation of the source signal that is periodically switched on and off (flashing pattern). This characteristic is referred to as "Pulsed Repetition Frequency" (PRF). *RST reverts this setting to its default value. Syntax :SOURce[1..
SCPI Command Reference Product-Specific Commands—Description :SOURce[1..n]:FREQuency:PRF? Response(s) PulsedRepetitionFrequency: The response data syntax for is defined as a element. Pulsed Repetition Frequency (PRF) of the sources signal. 428 Example(s) SOUR:FREQ:PRF 1000 SOUR:FREQ:PRF? Returns 1.000000e+3 See Also SOURce[1..n]:FREQuency:PRF SOURce[1..n]:FREQuency:PRF:STATe SOURce[1..n]:FREQuency:BURSt SOURce[1..
SCPI Command Reference Product-Specific Commands—Description :SOURce[1..n]:FREQuency:PRF:STATe Description This command is used to turn on or off the pulsed repetition frequency (PRF) of the source (enable or disable the flashing pattern). At *RST, the PRF signal state is set to OFF. Syntax :SOURce[1..n]:FREQuency:PRF:STATe Parameter(s) State: The program data syntax for is defined as a element.
SCPI Command Reference Product-Specific Commands—Description :SOURce[1..n]:FREQuency:PRF:STATe? Description This query returns a value indicating the current state of the source's pulsed repetition frequency (PRF) signal (flashing pattern enabled or disabled). At *RST, the PRF signal state is set to OFF. Syntax :SOURce[1..n]:FREQuency:PRF:STATe? Parameter(s) None Response Syntax Response(s) State: The response data syntax for is defined as a element.
SCPI Command Reference Product-Specific Commands—Description :SOURce[1..n]:POWer:STATe Description This command turns the source on or off. *RST sets the source to OFF. Syntax :SOURce[1..n]:POWer:STATe Parameter(s) State: The program data syntax for is defined as a element. The special forms ON and OFF are accepted on input for increased readability. ON corresponds to 1 and OFF corresponds to 0. New power state of the source.
SCPI Command Reference Product-Specific Commands—Description :SOURce[1..n]:POWer:STATe? Description This query returns a value indicating the state of the source (on or off). *RST sets the source to OFF. Syntax :SOURce[1..n]:POWer:STATe? Parameter(s) None Response Syntax Response(s) State: The response data syntax for is defined as a element. State of the source power. 0: Source is off. 1: Source is on.
SCPI Command Reference Product-Specific Commands—Description :SOURce[1..n]:POWer:STATe:TIME Description This command sets the duration after which the source will stop emitting light automatically (auto-off feature). Note that this command does not turn the source on. *RST sets this value to 600 seconds. Syntax :SOURce[1..n]:POWer:STATe:TIME Parameter(s) Duration: The program data syntax for is defined as a element.
SCPI Command Reference Product-Specific Commands—Description :SOURce[1..n]:POWer:STATe:TIME? Description This query returns a value indicating the duration after which the source will stop emitting light automatically (auto-off feature). *RST sets this value to 600 seconds. Syntax :SOURce[1..n]:POWer:STATe:TIME? Parameter(s) None Response Syntax Response(s) Duration: The response data syntax for is defined as a element.
SCPI Command Reference Product-Specific Commands—Description :SOURce[1..n]:VFLocator:AM:INTernal: FREQuency Description This command selects the internal modulation frequency of the visual fault locator (VFL). The internal modulation corresponds to 50 % of the duty cycle at the selected frequency. *RST sets the modulation frequency to 0 Hz (CW). Syntax :SOURce[1..
SCPI Command Reference Product-Specific Commands—Description :SOURce[1..n]:VFLocator:AM:INTernal: FREQuency MINimum allows to set the instrument to the smallest supported value. MAXimum allows to set the instrument to the greatest supported value. DEFault allows the instrument to select a value for the parameter. New modulation frequency: 1 or 0 (CW). 436 Example(s) SOUR:VFL:AM:INT:FREQ 1 SOUR:VFL:AM:STAT ON SOUR:VFL:POW:STAT ON See Also SOURce[1..
SCPI Command Reference Product-Specific Commands—Description :SOURce[1..n]:VFLocator:AM:INTernal: FREQuency? Description This query returns a value indicating the current internal modulation frequency. If the visual fault locator (VFL) is in CW mode, the function will return 0. *RST sets the modulation frequency to 0 Hz (CW). Syntax :SOURce[1..
SCPI Command Reference Product-Specific Commands—Description :SOURce[1..n]:VFLocator:AM:INTernal: FREQuency? Response(s) Frequency: The response data syntax for is defined as a element. The response corresponds to the internal modulation frequency of the VFL, in Hz. If the VFL is in CW mode, the returned value is 0. 438 Example(s) SOUR:VFL:AM:INT:FREQ 1 SOUR:VFL:AM:INT:FREQ? Returns 1 See Also SOURce[1..n]:VFLocator:AM:INTernal:FREQuenc y SOURce[1..
SCPI Command Reference Product-Specific Commands—Description :SOURce[1..n]:VFLocator:AM:STATe Description This command turns ON or OFF the amplitude modulation of the visual fault locator (VFL). At *RST, this value is set to OFF. Syntax :SOURce[1..n]:VFLocator:AM:STATe Parameter(s) State: The program data syntax for is defined as a element. The special forms ON and OFF are accepted on input for increased readability.
SCPI Command Reference Product-Specific Commands—Description :SOURce[1..n]:VFLocator:AM:STATe? Description This query returns a value indicating the current state of the amplitude modulation (on or off) of the visual fault locator (VFL). At *RST, the amplitude modulation state is set to OFF. Syntax :SOURce[1..n]:VFLocator:AM:STATe? Parameter(s) None Response Syntax Response(s) State: The response data syntax for is defined as a element.
SCPI Command Reference Product-Specific Commands—Description :SOURce[1..n]:VFLocator:POWer:STATe Description This command turns the visual fault locator (VFL) on or off. *RST sets the visual fault locator to OFF. Syntax :SOURce[1..n]:VFLocator:POWer:STATe Parameter(s) State: The program data syntax for is defined as a element. The special forms ON and OFF are accepted on input for increased readability. ON corresponds to 1 and OFF corresponds to 0.
SCPI Command Reference Product-Specific Commands—Description :SOURce[1..n]:VFLocator:POWer: STATe? Description This query returns a value indicating if the visual fault locator (VFL) is on or off. *RST sets the VFL to OFF. Syntax :SOURce[1..n]:VFLocator:POWer:STATe? Parameter(s) None Response Syntax Response(s) State: The response data syntax for is defined as a element. Power state of the VFL (on or off).
SCPI Command Reference Product-Specific Commands—Description :SOURce[1..n]:VFLocator:POWer:STATe: TIME Description This command sets the duration after which the visual fault locator (VFL) will stop emitting light automatically (auto-off feature). Note that this command does not turn the VFL on. *RST sets this value to 600 seconds. Syntax :SOURce[1..
SCPI Command Reference Product-Specific Commands—Description :SOURce[1..n]:VFLocator:POWer:STATe: TIME MINimum allows to set the instrument to the smallest supported value. MAXimum allows to set the instrument to the greatest supported value. DEFault allows the instrument to select a value for the parameter. Duration after which the laser will stop emitting light automatically, in seconds.
SCPI Command Reference Product-Specific Commands—Description :SOURce[1..n]:VFLocator:POWer:STATe: TIME? Description This query returns a value indicating the duration after which the visual fault locator (VFL) will stop emitting light automatically (auto-off feature). *RST sets this value to 600 seconds. Syntax :SOURce[1..
SCPI Command Reference Product-Specific Commands—Description :SOURce[1..n]:VFLocator:POWer:STATe: TIME? Response(s) Duration: The response data syntax for is defined as a element. Duration after which the laser will stop emitting light automatically, in seconds. 446 Example(s) SOUR:VFL:POW:STAT:TIME 60 SOUR:VFL:POW:STAT:TIME? Returns 60 See Also SOURce[1..n]:VFLocator:POWer:STATe:TIME SOURce[1..n]:VFLocator:POWer:STATe SOURce[1..n]:VFLocator:AM:STATe? SOURce[1..
SCPI Command Reference Product-Specific Commands—Description :SOURce[1..n]:WAVelength Description This command selects the wavelength of the source, in meters. At *RST, the wavelength that will be selected depends on the instrument you have. Syntax :SOURce[1..n]:WAVelength|MAXimum|MINimum|DEFault Parameter(s) Wavelength: The program data syntax for is defined as a element. The special forms MINimum, MAXimum and DEFault are accepted on input.
SCPI Command Reference Product-Specific Commands—Description :SOURce[1..n]:WAVelength? Description This query returns the output wavelength of the currently selected source, in meters. At *RST, the wavelength that will be selected depends on the instrument you have. Syntax :SOURce[1..n]:WAVelength?[MINimum| MAXimum|DEFault] Parameter(s) Parameter 1: The program data syntax for the first parameter is defined as a element.
SCPI Command Reference Product-Specific Commands—Description :SOURce[1..n]:WAVelength? Response(s) Wavelength: The response data syntax for is defined as a element. Current wavelength, in meters. OTDR Example(s) SOUR:WAV 1550.0E-9 SOUR:WAV? Returns 1550.0E-9 See Also SOURce[1..n]:WAVelength SOURce[1..
SCPI Command Reference Product-Specific Commands—Description :SOURce[1..n]:WAVelength:LIST? Description This query returns the list of all available wavelengths. *RST does not affect this command. Syntax :SOURce[1..n]:WAVelength:LIST? Parameter(s) None Response Syntax Response(s) WavelengthList: The response data syntax for is defined as a element. Returns the list of all available wavelengths, in meters.
SCPI Command Reference Product-Specific Commands—Description :TRACe[1..n][:DATA]? Description This query returns all points of the trace corresponding to the specified trace index. The trace is the result of a complete acquisition cycle or a loaded file. *RST clears this setting. Syntax :TRACe[1..n][:DATA]?TRC1|TRC2|TRC3| TRC4 Parameter(s) Label: The program data syntax for the first parameter is defined as a element.
SCPI Command Reference Product-Specific Commands—Description :TRACe[1..n][:DATA]? Response(s) Data: The response data syntax for is defined as a element. Returns a list of power values representing the trace. Each power value represents a point in the trace and is always returned in dB as a type. 452 Example(s) CONF:ACQ:MODE ACQ INIT INIT:STAT? Returns 0 when acquisition is complete.
SCPI Command Reference Product-Specific Commands—Description :TRACe[1..n]:CATalog? Description This query returns all the available labels associated to a trace, at a given wavelength. *RST clears this setting. Syntax :TRACe[1..n]:CATalog? Parameter(s) None Response Syntax Response(s) Catalog: The response data syntax for is defined as a element. Returns a list of labels corresponding to the acquired or loaded wavelengths.
SCPI Command Reference Product-Specific Commands—Description :TRACe[1..n]:POINts? Description This query returns the number of points of the trace corresponding to the specified trace index. The trace is the result of a complete acquisition cycle or a loaded file. *RST clears this setting. Syntax :TRACe[1..n]:POINts?TRC1|TRC2|TRC3| TRC4 Parameter(s) Label: The program data syntax for the first parameter is defined as a element.
SCPI Command Reference Product-Specific Commands—Description :TRACe[1..n]:POINts? Response(s) PointsCount: The response data syntax for is defined as a element. Returns the number of points. OTDR Example(s) CONF:ACQ:MODE ACQ INIT INIT:STAT? Returns 0 when acquisition is complete. TRAC:POIN? TRC1 Returns the number of points. See Also MMEMory[1..n]:LOAD:TRACe TRACe[1..n][:DATA]? MMEMory[1..
Index Index ***** indication ........................................ 196 A About button ............................................ 281 accuracy, trace ............................................ 74 acquiring traces Advanced mode....................... 63, 72, 120 Auto mode ............................................ 59 real time ................................................ 92 Template mode...................................... 99 acquisition automatic, in Advanced mode...............
Index percentage of events aligned............... 238 printing traces ..................................... 250 purpose ............................................... 227 restrictions................................... 227, 230 starting ................................................ 228 bidirectional trace discarding the original files.................. 248 file content .......................................... 248 saving .................................................. 248 Busy, module status ......
Index distance between events ................................... 188 equation .................................................. 7 range ..................................................... 71 E end-of-fiber detection threshold ..... 153, 155, 167, 245 event ................................................... 294 entering comments ................................... 178 equation of distance ..................................... 7 equipment returns ....................................
Index sections display.................................... 142 type in Trace Info. tab.......................... 154 type information.................................... 46 see also fiber span ................................. 83 fiber ends, cleaning..................................... 26 fiber parameters, setting acquisition-specific (Advanced)............ 153 acquisition-specific (Bidirectional)........ 243 fiber parameters, setting default values ...... 69 fiber section attenuation threshold ..........
Index modification ........................................ 158 non-reflective events average ...... 155, 244 span threshold....................................... 78 splice, threshold .................................... 78 LSA measurement method definition ............................................. 194 vs. four-point....................................... 189 vs. two-point ....................................... 194 M maintenance EUI connectors..................................... 260 front panel....
Index P parameters Advanced mode..................................... 68 cable...................................................... 28 helix factor............................................. 69 IOR ........................................................ 69 Rayleigh backscatter coefficient............. 69 Template mode ..................................... 94 trace display ........................................ 140 pass/fail test disabling................................................ 79 enabling ..
Index format, native...................................... 199 format, Telcordia (Bellcore).................. 199 trace autonaming .................................. 50 traces................................................... 241 saving traces in different formats.............. 199 selecting active trace .......................................... 148 Automatic OTDR test wavelength .... 57, 63 OTDR setup.......................................... 125 test wavelength, automatically ........
Index template trace appearance .................. 102 testing ................................................... 93 working with traces............................... 96 Template OTDR. see Template mode template trace appearance........................ 102 test wavelength, forced selection.......... 61, 67 testing Advanced mode..................................... 63 Auto mode ............................................ 57 Template mode ..................................... 93 theory, OTDR..............
Index length .......................................... 154, 244 reflectance threshold ................... 155, 245 splice loss threshold..................... 155, 245 time ............................................. 154, 244 tolerance (Bidir. Info.) .......................... 244 total loss .............................................. 154 total/average loss................................. 244 wavelength.......................................... 154 trace name, changing default .....................
NOTICE 抩⛙ CHINESE REGULATION ON RESTRICTION OF HAZARDOUS SUBSTANCES ₼⦌␂ℝ☀⹂䓸德棟Ⓟ䤓屓⸩ NAMES AND CONTENTS OF THE TOXIC OR HAZARDOUS SUBSTANCES OR ELEMENTS CONTAINED IN THIS EXFO PRODUCT ▔⚺⦷㦻 EXFO ℶ❐₼䤓㦘㹡㦘⹂䓸德㒥⏒侯䤓⚜䱿✛⚺摞 O X Indicates that this toxic or hazardous substance contained in all of the homogeneous materials for this part is below the limit requirement in SJ/T11363-2006 嫷䯉年㦘㹡㦘⹂䓸德⦷年捷ↅ㓏㦘⧖德㧟㠨₼䤓⚺摞⧖⦷ SJ/T11363-2006 㪖屓⸩䤓 棟摞尐㻑ⅴₚᇭ Indicates that this toxic or hazardous substance contained in at least one of the
MARKING REQUIREMENTS 㪖㽷尐㻑 Product Environmental protection use period (years) Logo ℶ❐ 䘾⬒≬㔳∎䞷㦮棟 ( ) 㪖㉦ This Exfo product 㦻 EXFO ℶ❐ Batterya 䟄㻯 a a. If applicable.
P/N: 1060496 www.EXFO.com · info@exfo.com CORPORATE HEADQUARTERS 400 Godin Avenue Quebec (Quebec) G1M 2K2 CANADA Tel.: 1 418 683-0211 · Fax: 1 418 683-2170 EXFO AMERICA 3701 Plano Parkway, Suite 160 Plano TX, 75075 USA Tel.: 1 972 907-1505 · Fax: 1 972 836-0164 EXFO EUROPE Omega Enterprise Park, Electron Way Chandlers Ford, Hampshire S053 4SE ENGLAND Tel.: +44 2380 246810 · Fax: +44 2380 246801 EXFO ASIA-PACIFIC 151 Chin Swee Road #03-29, Manhattan House SINGAPORE 169876 Tel.
