Anritsu MT9083 Series Operation Manual
  1. Manuals
  2. Brands
  3. Anritsu Manuals
  4. Remote Control
  5. MT9083 Series
  6. Operation manual
Anritsu MT9083 Series Operation Manual

Anritsu MT9083 Series Operation Manual

Access master remote control
Hide thumbs
Table of Contents

Advertisement

Quick Links

MT9083 Series
ACCESS Master

Remote Control

Operation manual

Fourth Edition
• For safety and warning information, please read this
manual before attempting to use the equipment.
• Additional safety and warning information is provided
within
the
MT9083A2/B2/C2
Operation Manual. Please also refer to this document
before using the equipment.
• Keep this manual with the equipment.
ANRITSU CORPORATION
Document No.: M-W3636AE-4.0
ACCESS
Master

Advertisement

Table of Contents
loading

Related Manuals for Anritsu MT9083 Series

Summary of Contents for Anritsu MT9083 Series

  • Page 1: Remote Control

    MT9083 Series ACCESS Master Remote Control Operation manual Fourth Edition • For safety and warning information, please read this manual before attempting to use the equipment. • Additional safety and warning information is provided within MT9083A2/B2/C2 ACCESS Master Operation Manual. Please also refer to this document before using the equipment.
  • Page 2 Ensure that you clearly understand the meanings of the symbols BEFORE using the equipment. Some or all of the following symbols may be used on all Anritsu equipment. In addition, there may be other labels attached to products that are not shown in the diagrams in this manual.

  • Page 3: About This Manual

    About This Manual This operation manual describes the SCPI (Standard Commands for Programmable Instruments) commands for the MT9083A2/B2/C2 ACCESS Master. MT9083 Series ACCESS Master Operation Manual Operations for the MT9083 Series Operation ACCESS Master main frame are manuals for described. MT9083 Series...

  • Page 4: Table Of Contents

    Table of Contents About This Manual ........Chapter 1 Overview ........About Remote Control ..........1-2 Applications ..............1-2 Chapter 2 Before Use ........ Preparing Equipment ..........2-2 Connecting Equipment ..........2-3 Setting Ethernet ............2-5 Checking Connection ..........2-7 Message Format ............
  • Page 5 Appendix A Recommended USB-Ethernet converter ...

  • Page 7: Chapter 1 Overview

    Chapter 1 Overview This chapter explains remote control of the MT9083A2/B2/C2 ACCESS Master. About Remote Control ..........1-2 Applications ..............1-2...

  • Page 8: About Remote Control

    Chapter 1 Outline 1.1 About Remote Control The remote control function sends commands via the communications interface from the remote control PC to set the measuring instrument and read the measurement results and measuring instrument conditions. The MT9083A2/B2/C2 ACCESS Master (this instrument hereafter) uses the Ethernet interface for remote control.

  • Page 9: Chapter 2 Before Use

    Chapter 2 Before use This chapter explains the preparations for using remote control. Preparing Equipment ............ 2-2 Connecting Equipment ..........2-3 2.2.1 Connecting USB-Ethernet converter ....2-3 2.2.2 Connecting External Equipment ....... 2-4 Setting Ethernet ............2-5 Checking Connection ............ 2-7 Message Format ............

  • Page 10: Preparing Equipment

     Program development tools The PC must be able to run the program development tools. USB-Ethernet converter We recommend using the Anritsu USB-Ethernet converter, which is confirmed as working. Other commercial converters can be used but some may have compatibility problems.

  • Page 11: Connecting Equipment

    Connecting Equipment 2.2 Connecting Equipment 2.2.1 Connecting USB-Ethernet converter Connect the USB-Ethernet converter to the USB Down Port on the top edge of the ACCESS Master. Figure 2.2.1-1 ACCESS Master and USB-Ethernet converter If the converter is connected while the power is on, processing will be suspended and the Remote Setup screen displayed.

  • Page 12: Connecting External Equipment

    Chapter 2 Before use 2.2.2 Connecting External Equipment Connect the external equipment with a LAN cable to the LAN port of the USB-Ethernet converter connected to the instrument. Use a crossover cable to connect one PC controller. When connecting multiple pieces of external equipment, use a network hub.

  • Page 13: Setting Ethernet

    Setting Ethernet 2.3 Setting Ethernet Instrument settings such as IP address are set at the Remote Setup Screen. The Remote screen is displayed by the following two methods.  Press Remote Setup (f1) at the Top Menu.  With the power on, connect the USB-Ethernet converter to the USB Down port.
  • Page 14 Chapter 2 Before use Set the IP Address. The input setting range is 0.0.0.1 to 255.255.255.254. Use the instrument’s numeric keypad or the Left/Right/Up/Down Arrow keys to input the numeric values. The default setting is 192.168.1.2. Set the IP Netmask. The input setting range is 0.0.0.0 to 255.255.255.255 and the default setting is 255.255.255.0.

  • Page 15: Checking Connection

    Checking Connection 2.4 Checking Connection Check that the link between the PC and instrument has been established. Click Programs at the Windows Start menu. Click Accessories. Click Command Prompt. Input the commands shown in the screen below. This example shows how to set the IP address to 192.168.1.2. Figure 2.4-1 Executing Ping Command Check that the “Request timed out”...

  • Page 16: Message Format

    Chapter 2 Before use 2.5 Message Format Messages are composed of character strings for executing commands and character strings indicating the message end. When sending messages to this instrument, terminate the line with CR/LF; received messages are terminated with CR/LF. Messages are composed of the following types: Program Messages: Messages sent from PC to instrument...
  • Page 17 Message Format Example: *ESR? TOPMenu:UNIT:CATalog? SOUR:PULS:ENH? When linking multiple program messages, separate the message using semicolons (;).The maximum number of linked messages is 12.If 13 or more messages are sent, the 13th and subsequent messages are discarded. Example: SOUR:WAV 1310;SOUR:RAN 100;SOUR:RES 0;INIT;*WAI The data format is character string data, numeric data, and binary data.
  • Page 18 Chapter 2 Before use 2.6 Checking Instrument Status This instrument has registers indicating the status, such as errors and command execution status. This section explains these registers. 2.6.1 Register Structure Figure 2.6.1-1 shows the structure of the registers indicating the instrument status.

  • Page 19: Checking Instrument Status

    Checking Instrument Status Each register uses 8-bit data. The register output values are the binary totals for each bit shown in Figure 2.6.1-1. Table 2.6.1-1 Register Bit Binary Conversion Values Binary Binary value value To read the status byte register, set the service request enable register. The logical product of these two registers is read by *STB .

  • Page 20: Status Byte Register

    Chapter 2 Before use 2.6.2 Status Byte Register The meaning of each bit of the status byte register is shown in the following table. Table 2.6.2-1 Meaning of Status Byte Register Explanation OSR (Operation Status Register) Displays the equipment’s operation status. Currently only 1 can be set during OTDR measurement.

  • Page 21: Event Register

    Checking Instrument Status 2.6.3 Event Register Standard Event Status Register The meaning of each bit of the standard event status register is listed in the table below. Table 2.6.3-1 Meaning of Standard Event Status Register Explanation Power-on Becomes 1 at power-on and 0 each time 1 is read. User Request Not used;...

  • Page 22: Controlling Message Sync

    Chapter 2 Before use 2.7 Controlling Message Sync The following messages (12 types max.) can be received during measurement by this instrument and analysis of measurement results. However, if a message is sent to change the measurement parameters before the previous processing is completed, the message is discarded and the correct measurement conditions will not be set.
  • Page 23 Controlling Message Sync Using *WAI The *WAI common command instructs processing to wait until processing of the message sent before the *WAI command is completed before executing the next command. Example of Use: INIT ; *WAI ; SOUR:WAV 1550; INIT Wavelength change after measurement completed SOUR:WAV 1550 INIT...
  • Page 24 Chapter 2 Before use Using *OPC and *ESR? The *OPC common command sets the standard event status register bit to 0 and displays the OPC bit. Examples of Use: *CLS Sets the OPC bit to 0. *ESE 1 Sets standard event status enable bit to 1 INIT Executes averaging measurement Sets so as to change standard event status...
  • Page 25 Controlling Message Sync Querying Measurement End The instrument program messages query the end of processing execution. These queries send the following messages after confirming the processing end. Example of Use, 1: When averaging measurement is 60 s Executes averaging measurement INIT SENS:AVER:TIM? Queries elapsed averaging time...

  • Page 26: Switching Sm Unit And Mm Unit

    Chapter 2 Before use 2.8 Switching SM Unit and MM unit Two OTDR units for single mode fiber (measurement wavelength: 1310/1550 nm ) and multimode fiber (measurement wavelength: 850/1300 nm) can be installed in this instrument according to the number of the option unit (e.g. MT9083B2 Option 063). Switch between the SM unit and MM units as described below.

  • Page 27: Moving To Another Measurement Mode From Top Menu

    Moving to Another Measurement Mode from Top Menu 2.9 Moving to Another Measurement Mode from Top Menu In addition to OTDR measurement, this instrument has other built-in measurement mode functions such as Light Source and Power Meter. To use these measurements, it is necessary to switch measurement mode. The remote control modes supported by the current MT9083A2/B2/C2 are Top Menu and OTDR (Standard).
  • Page 28 Chapter 2 Before use Example of Use 2: To measure with MM unit after measuring with SM unit using MT9083B2-063 (MM 850/1300 nm/SM 1310/1550 nm) INSTrument:NSELect? Queries current measurement mode At 2 response: >2 OTDR (Standard) mode INST:NSEL 1 Moves to Top Menu Queries installed OTDR TOPMenu:UNIT:CATalog:FULL? Multimode unit installed a unit 1;...

  • Page 29: Chapter 3 Platform Scpi Commands

    Chapter 3 Platform SCPI Commands This chapter details the SCPI commands for the MT9083A2/B2/C2 platform. Star (IEEE 488.2) Subsystem Commands ....3-4 3.1.1 *CLS Clear Status Command ......3-4 3.1.2 *ESE Standard Event Status Enable Command ............3-4 3.1.3 *ESE? Standard Event Status Enable Query ... 3-4 3.1.4 *ESR? Standard Event Status Register Query..............
  • Page 30 Chapter 3 Platform SCPI Commands 3.3.15 STATus:OPERation:INSTrument :ISUMmary#:ENABle? ........3-14 3.3.16 STATus:OPERation:INSTrument :ISUMmary#[:EVENt]? ........3-14 3.3.17 STATus:QUEStionable[:EVENt]? ....3-15 3.3.18 STATus:QUEStionable:CONDition? ....3-15 3.3.19 STATus:QUEStionable:BIT#:CONDition? ..3-15 3.3.20 STATus:QUEStionable:BIT#:ENABle .... 3-15 3.3.21 STATus:QUEStionable:BIT#:ENABle? ..3-16 3.3.22 STATus:QUEStionable:BIT#[:EVENt]? ..3-16 3.3.23 STATus:QUEStionable:ENABle ....3-16 3.3.24 STATus:QUEStionable:ENABle? ....
  • Page 31 Chapter 3 Platform SCPI Commands 3.5.6 TOPMenu:UNIT:NSELect? ......3-23...

  • Page 32: Star (Ieee 488.2) Subsystem Commands

    Chapter 3 Platform SCPI Commands 3.1 Star (IEEE 488.2) Subsystem Commands 3.1.1 *CLS Clear Status Command Syntax: *CLS Description: The Clear Status command *CLS clears all the event registers summarized in the Status Byte register. Except for the output queue, all queues summarized in the Status Byte register are emptied.

  • Page 33: Esr? Standard Event Status Register Query

    Parameters: None Response: The identification string terminated by <END> Example: *IDN? −> ANRITSU, MT9083C2-053, 6200123456<END> 3.1.6 *OPC Operation Complete Command Syntax: *OPC Description: A device is in the Operation Complete Command Active State (OCAS) after it has executed *OPC. The device returns to the Operation Complete Command Idle State (OCIS) whenever the No Operation Pending flag is TRUE, at the same time setting the OPC bit of the SESR TRUE.

  • Page 34: Opc? Operation Complete Query

    Chapter 3 Platform SCPI Commands 3.1.7 *OPC? Operation Complete Query Syntax: *OPC? Description: A device is in the Operation Complete Query Active State (OQAS) after it has executed *OPC?. The device returns to the Operation Complete Query Idle State (OQIS) whenever the No Operation Pending flag is TRUE, at the same time placing a “1"...

  • Page 35: Sre Service Request Enable Command

    Star (IEEE 488.2) Subsystem Commands 3.1.9 *SRE Service Request Enable Command Syntax: *SRE<wsp><value> Description: The standard Service Request Enable command (*SRE) sets bits in the Service Request Enable register. A 1 in a bit in the enable register enables the corresponding bit in the Service Request Enable register.

  • Page 36: Stb? Read Status Byte Query

    Chapter 3 Platform SCPI Commands 3.1.11 *STB? Read Status Byte Query Syntax: *STB? Description: The Status Byte query *STB? returns the contents of the Status Byte register. The Master Summary Status (MSS) bit is true when any enabled bit of the STB register is set (excluding Bit 6).

  • Page 37: System Subsystem Commands

    System Subsystem Commands 3.2 System Subsystem Commands 3.2.1 SYSTem:ERRor? Syntax: SYSTem:ERRor? Description: Returns the contents of the SCPI error queue. Removes the returned entry from the queue. Parameters: None Response: The number of the latest error, sorted by the error commands sending order, and its meaning.

  • Page 38: System:light

    Chapter 3 Platform SCPI Commands 3.2.5 SYSTem:LIGHt? Syntax: SYSTem:LIGHt? Description: Checks if the backlight is turned ON or OFF. Parameters: None Response: Possible responses are: 0 = The backlight is OFF. 1 = The backlight is ON. Example: SYST:LIGH? -> 0<END> 3.2.6 SYSTem:LIGHt Syntax: SYSTem:LIGHt<wsp><value>...

  • Page 39: Status Subsystem Commands

    Status Subsystem Commands 3.3 Status Subsystem Commands All commands in this section are prepared for future functions. All the registers regarding these commands are set to 0 now. 3.3.1 STATus:OPERation[:EVENt]? Syntax: STATus:OPERation[:EVENt]? Description: Queries the operation event register. Parameters: None Response: The bit value for the operation event register as a short value (0 ..

  • Page 40: Status:operation:bit#:Enable

    Chapter 3 Platform SCPI Commands 3.3.5 STATus:OPERation:BIT#:ENABle? Syntax: STATus:OPERation:BIT<n>:ENABle? Description: Returns the operation enable mask for the event register specified bit. The value of <n> is restricted from 8 to 12 and represents bits 8 through 12 Parameters: None Response: The bit value for the operation enable mask as a short value (0 ..

  • Page 41: Status:operation:instrument:condition

    Status Subsystem Commands 3.3.9 STATus:OPERation:INSTrument:CONDition? Syntax: STATus:OPERation:INSTrument:CONDition? Description: Queries the instrument operation condition register. Parameters: None Response: The bit value for the operation condition register as a short value (0 .. +32767) Example: STAT:OPER:INST:COND? −> 16<END> 3.3.10 STATus:OPERation:INSTrument:ENABle Syntax: STATus:OPERation:INSTrument:ENABle<wsp><value> Description: Sets the instrument operation enable mask for the event register.

  • Page 42: Status:operation:instrument:isummary#:Condition

    Chapter 3 Platform SCPI Commands 3.3.13 STATus:OPERation:INSTrument:ISUMmary#:CONDition? Syntax: STATus:OPERation:INSTrument:ISUMmary<n>:CONDition? Description: Queries the instrument operation condition register of the specified instrument. The value of <n> is restricted from 1 to 14 and represents the logical instruments id assigned to the SCPI controlled instrument by the INSTrument subsystem. Parameters: None Response:...

  • Page 43: Status:questionable[:Event]

    Status Subsystem Commands 3.3.17 STATus:QUEStionable[:EVENt]? Syntax: STATus:QUEStionable[:EVENt]? Description: Queries the questionable event register Parameters: None Response: The bit value for the questionable event register as a short value (0 .. +32767) Example: STAT:QUES? −> 0<END> 3.3.18 STATus:QUEStionable:CONDition? Syntax: STATus:QUEStionable:CONDition? Description: Queries the questionable condition register Parameters: None...

  • Page 44: Status:questionable:bit#[:Event]

    Chapter 3 Platform SCPI Commands 3.3.21 STATus:QUEStionable:BIT#:ENABle? Syntax: STATus:QUEStionable:BIT<n>:ENABle? Description: Returns the questionable enable mask for the event register specified bit. The value of <n> is restricted from 9 to 12 and represents bits 9 through 12 Parameters: None Response: The bit value for the questionable enable mask as a short value (0 ..

  • Page 45: Status:questionable:instrument:condition

    Status Subsystem Commands 3.3.25 STATus:QUEStionable:INSTrument:CONDition? Syntax: STATus:QUEStionable:INSTrument:CONDition? Description: Queries the questionable instrument condition register. Parameters: None Response: The bit value for the questionable condition register as a short value (0 .. +32767) Example: STAT:QUES:INST:COND? −> 8<END> 3.3.26 STATus:QUEStionable:INSTrument:ENABle Syntax: STATus:QUEStionable:INSTrument:ENABle<wsp><value> Description: Sets the questionable instrument enable mask for the event register Parameters:...

  • Page 46: Status:questionable:instrument:isummary#:Condition

    Chapter 3 Platform SCPI Commands 3.3.29 STATus:QUEStionable:INSTrument:ISUMmary#:CONDition? Syntax: STATus:QUEStionable:INSTrument:ISUMmary<n>:CONDition? Description: Queries the specified logical instrument questionable instrument condition register. The value of <n> is restricted from 1 to 14 and represents the logical instruments id assigned to the SCPI controlled instrument by the INSTrument subsystem.

  • Page 47: Status:preset

    Status Subsystem Commands 3.3.33 STATus:PRESet Syntax: STATus:PRESet Description: Resets both the operation enable mask and questionable enable mask to 0 Parameters: None Response: None Example: STAT:PRES 3-19...

  • Page 48: Instrument Subsystem Commands

    Chapter 3 Platform SCPI Commands 3.4 Instrument Subsystem Commands 3.4.1 INSTrument:CATalog? Syntax: INSTrument:CATalog? Description: Returns the list of SCPI controllable instruments on MT9083A2/B2/C2 that are identified as SCPI controllable instruments Parameters: None Response: comma-separated list of string identifiers of all SCPI controllable logical instruments Example: INST:CAT? −>...

  • Page 49: Instrument[:Select]

    Instrument Subsystem Commands 3.4.5 INSTrument[:SELect] Syntax: INSTrument:SELect<wsp><string_id> Description: Sets the specified logical instrument to be currently selected instrument Parameters: The string instrument identifier assigned by the Instrument subsystem for the instrument to be selected as a string value Response: None Example: INST:SEL OTDR_STD 3.4.6 INSTrument[:SELect]?

  • Page 50: Topmenu Subsystem Commands

    Chapter 3 Platform SCPI Commands 3.5 TOPMenu Subsystem Commands 3.5.1 TOPMenu:UNIT:CATalog? Syntax: TOPMenu:UNIT:CATalog? Description: Returns the list of Units installed on MT9083A2/B2/C2 that can be selected prior to starting OTDR instrument Parameters: None Response: comma-separated list of string identifiers of all installed Units Example: TOPM:UNIT:CAT? −>...

  • Page 51: Topmenu:unit:nselect

    TOPMenu Subsystem Commands 3.5.5 TOPMenu:UNIT:NSELect Syntax: TOPMenu:NSELect<wsp><num_id> Description: Sets the specified Unit to be currently selected to run with OTDR instrument. Parameters: The numeric value identifier assigned by the TOPMenu subsystem for the Unit to be selected as a short value Response: None Example:...
  • Page 52 Chapter 3 Platform SCPI Commands 3-24.

  • Page 53: Chapter 4 Otdr Commands

    Chapter 4 OTDR Commands This chapter details the SCPI commands for the MT9083A2/B2/C2 Standard OTDR application. The Command Summary section presents a brief summary of each command, while each command is detailed in the subsequent sections. Command Summary ............. 4-4 Root Level Commands ..........
  • Page 54 Chapter 4 OTDR Commands 4.4.11 SENSe:FIBer:BSC? Command ...... 4-17 4.4.12 SENSe:HOFFset Command ......4-17 4.4.13 SENSe:HOFFset? Command ......4-17 4.4.14 SENSe:VOFFset Command ......4-18 4.4.15 SENSe:VOFFset? Command ......4-18 4.4.16 SENSe:ACURsor Command ......4-18 4.4.17 SENSe:ACURsor? Command ......4-18 4.4.18 SENSe:BCURsor Command ......4-19 4.4.19 SENSe:BCURsor? Command ......
  • Page 55 Chapter 4 OTDR Commands4.1 Command Summary 4.6.10 DISPlay:SCALe:VERTical Command .... 4-35 4.6.11 DISPlay:SCALe:VERTical? Command ..4-35...

  • Page 56: Command Summary

    Chapter 4 OTDR Commands 4.1 Command Summary The Command Summary section provides a list of the SCPI commands for the MT9083A2/B2/C2 Standard OTDR application, and a brief description for each command. Commands and queries in this section can be received only in the OTDR (Standard) mode.
  • Page 57 Command Summary SENSe:TRACe:READy? - Queries if the trace data is ready. SENSe:CONCheck - Sets connection check option ON or OFF. SENSe:CONCheck? - Queries if the connection check option enabled. SENSe:LIVCheck - Sets live fiber check option ON or OFF. SENSe:LIVCheck? - Queries if the live fiber check option enabled. SENSe:FIBer:IOR - Sets fiber IOR value.
  • Page 58 Chapter 4 OTDR Commands Display Subsystem Commands DISPlay:MODE – Sets Current display mode (From A, From B, From Origin). DISPlay:MODE? – Queries current display mode. DISPlay:ZOOM:FULL – Sets zoom to view full trace in current display mode. DISPlay:ZOOM:HORIzontal – Set the display zoom level in current display mode. DISPlay:ZOOM:HORIzontal? –...

  • Page 59: Root Level Commands

    Root Level Commands 4.2 Root Level Commands These commands start/stop OTDR test sequence 4.2.1 ABORt Command Syntax: ABORt Parameters: None Description: Aborts the active test. The trace data will be lost. Example: abor Response: None Errors: (–200, "std_execGen, Test is Inactive") 4.2.2 STOP Command Syntax: STOP...
  • Page 60 Chapter 4 OTDR Commands 4.2.4 INITiate:AUTo Command Syntax: INITiate:AUTo Parameters: None Description: Starts OTDR auto-test. All test parameters are automatically obtained during the pre-scan. This command is an overlapped command. When this command is executed with “Wavelength all” selected, the measurement starts with the minimum wavelength, and no measurement is done for other wavelengths.

  • Page 61: Source Subsystem Commands

    SOURce Subsystem Commands 4.3 SOURce Subsystem Commands The SOURce subsystem controls/query OTDR’s optical source parameters. 4.3.1 SOURce:WAVelength:AVAilable? Command Syntax: SOURce:WAVelength:AVAilable? Parameters: None Description: Queries the list of available wavelengths. Example: sour:wav:ava? --- 1310, 1550<END> Response: List of available wavelength in nanometers (NM). Errors: None 4.3.2 SOURce:WAVelength Command...
  • Page 62 Chapter 4 OTDR Commands 4.3.4 SOURce:RANge:AVAilable? Command Syntax: SOURce:RANge:AVAilable? Parameters: None Description: Queries the list of available ranges for current wavelength settings. Example: sour:ran:ava? --- 5.0, 10.0, 20.0, 50.0, 100.0, 200.0, 300.0<END> Response: List of available ranges in kilometers (KM). Errors: None 4.3.5 SOURce:RANge Command...
  • Page 63 SOURce Subsystem Commands 4.3.8 SOURce:RESo Command Syntax: SOURce:RESo<wsp><value> Parameters: <value> Integer format Range: 0|1|2, 0-Low Density, 1-High Density, 2-Very High Density Available resolution values are dependant on current range settings. Description: Set current resolution. Example: sour:res 1 Response: None Errors: (–200, "std_execGen, Test is Active") (–224, "std_illegalParmValue, Invalid Parameter Value") 4.3.9 SOURce:RESo? Command...
  • Page 64 Chapter 4 OTDR Commands 4.3.11 SOURce:PULSe Command Syntax: SOURce:PULSe<wsp><value> Parameters: <value> Numeric format Range: Integer PW value returned by querying available pulse width command. Available pulse width values are dependant on current range/resolution settings. Description: Set current pulse width. Example: sour:puls 100 Response: None...
  • Page 65 SOURce Subsystem Commands 4.3.14 SOURce:PULSe:ENHanced Command Syntax: SOURce:PULSe:ENHanced<wsp><value> Parameters: <value> Boolean format Range: 1|0. Description: Set current pulse width’s enhanced mode. Example: sour:puls:enh 0 Response: None Errors: (–200, "std_execGen, Test is Active") (–104, "std_wrongParamType, Data Type Error") (–224, "std_illegalParmValue, Invalid Parameter Value") 4.3.15 SOURce:PULSe:ENHanced? Command Syntax: SOURce:PULSe:ENHanced?

  • Page 66: Sense Subsystem Commands

    Chapter 4 OTDR Commands 4.4 SENSe Subsystem Commands The SENSe subsystem lets you control/query OTDR’s measurement parameters. 4.4.1 SENSe:AVERages? Command Syntax: SENSe:AVERages? Parameters: None Description: Queries number of averages that have been completed on the trace or since the test started Example: sens:aver? --- 4096<END>...
  • Page 67 SENSe Subsystem Commands 4.4.4 SENSe:CONCheck? Command Syntax: SENSe:CONCheck? Parameters: None Description: Queries if connection check option is ON. Example: sens:conc? --- 1<END> Response: Possible response values: 1 = Connection check is ON. 0 = Connection check is OFF. Errors: None 4.4.5 SENSe:CONCheck Command Syntax: SENSe:CONCheck<wsp><value>...
  • Page 68 Chapter 4 OTDR Commands 4.4.7 SENSe:LIVCheck:Command Syntax: SENSe:LIVCheck<wsp><value> Parameters: <value> Boolean value 1 or on = Live fiber check is ON. 0 or off = Live fiber check is OFF. Description: Sets live fiber check option ON or OFF. Example: sens:livc ON<END>...
  • Page 69 SENSe Subsystem Commands 4.4.10 SENSe:FIBer:BSC Command Syntax: SENSe:FIBer:BSC<wsp><value> Parameters: <value> Floating point format Range: –90.0 - –40.0 Description: Sets backscatter coefficient. This value will be used for the next test. Example: sens:fib:bsc –83.0 Response: None Errors: (–200, "std_execGen, Test is Active") (–224, "std_illegalParmValue, Invalid Parameter Value") 4.4.11 SENSe:FIBer:BSC? Command Syntax:...
  • Page 70 Chapter 4 OTDR Commands 4.4.14 SENSe:VOFFset Command Syntax: SENSe:VOFFset<wsp><value> Parameters: <value> Floating point format Range: Offset value can be set plus/minus current dynamic range. (–64.0 to 64.0) Description: Set vertical offset for the displayed trace(s). Offset value units – DB. Example: sens:voff –5.0 Response:...
  • Page 71 SENSe Subsystem Commands 4.4.18 SENSe:BCURsor Command Syntax: SENSe:BCURsor<wsp><value> Parameters: <value> Floating point format Range: 0.0 – Current distance range. Description: Set B cursor position. Cursor position units – Km. Example: sens:bcur 20.5 Response: None Errors: (–224, "std_illegalParmValue, Invalid Parameter Value") 4.4.19 SENSe:BCURsor? Command Syntax: SENSe:BCURsor?
  • Page 72 Chapter 4 OTDR Commands 4.4.21 SENSe:LSALeft? Command Syntax: SENSe:LSALeft? Parameters: None Description: Query left LSA values. Example: sens:lsal? --- 0.0, 0.5<END> Response: Start and stop for left LSA marker. Start and stop units – kilometers (KM). Errors: (–400, "std_queryGen, LSA Inactive State") 4.4.22 SENSe:LSARight Command Syntax: SENSe:LSARight<wsp><start>,<stop>...
  • Page 73 SENSe Subsystem Commands 4.4.24 SENSe:LOSS:MODE Command Syntax: SENSe:LOSS:MODE<wsp><value> Parameters: <value> Integer format Range: 0|1|2|3|4|5|6 0 = Splice Loss Mode 1 = Two-point Loss Mode 2 = Two-point LSA 3 = dB/km Loss Mode 4 = dB/km LSA Loss Mode 5 = Two-point Attenuation Corrected Loss Mode 6 = ORL Loss Mode Description: Set current Loss Mode.
  • Page 74 Chapter 4 OTDR Commands 4.4.26 SENSe:ORL:MODE Command Syntax: SENSe:ORL:MODE<wsp><value> Parameters: <value> Integer format Range: 0|1|2 0 = A Cursor 1 = Origin 2 = Full Trace Description: Set current ORL Mode. Example: sens:orl:mode 0 Response: None Errors: (–224, "std_illegalParmValue, Invalid Parameter Value") 4.4.27 SENSe:ORL:MODE? Command Syntax: SENSe:ORL:MODE?
  • Page 75 SENSe Subsystem Commands 4.4.29 SENSe:ANALyze:PARameters? Command Syntax: SENSe:ANALyze:PARameters? Parameters: none Description: Query current Analysis parameters. Example: sens:anal:par? --- 0.050000, –60.000000, 3.000000,10.000000<END> Response: <event loss>,<reflectance>,<end loss>,<pon loss><END> Errors: None 4.4.30 SENSe:ANALyze:AUTO Command Syntax: SENSe:ANALyze:AUTO<wsp><value> Parameters: <value> Boolean format Range: 0|1 0 = Auto-analysis is OFF. 1 = Auto-analysis is ON.

  • Page 76: Trace Subsystem Commands

    Chapter 4 OTDR Commands 4.5 TRACe Subsystem Commands The TRACe subsystem provides access to the trace analysis and trace data. 4.5.1 TRACe:PARameters? Command Syntax: TRACe:PARameters? Parameters: None Description: Get main OTDR parameters used to collect the trace data. <wave>, <range>, <pulse>, <avg>, <reso>, <ior>, <bsc>, <enh><END> Example: trac:par? --- 1310, 16.415554, 50, 6144, 0.656621, 1.467700, –78.500000, 1<END>...
  • Page 77 TRACe Subsystem Commands 4.5.4 TRACe:ANALyze:ORL Command Syntax: TRACe:ANALyze:ORL Parameters: <none> Description: Performs ORL calculations on the trace. This command is an overlapped command. Example: trac:anal:orl Response: None Errors: (–200, "std_execGen, Test is Active") (–200, "std_execGen, Trace Not Ready") (–200, "std_execGen, Invalid Loss Mode") 4.5.5 TRACe:MDLOss? Command Syntax: TRACe:MDLOss?
  • Page 78 Chapter 4 OTDR Commands 4.5.7 TRACe:LOAD:SOR? Command Syntax: TRACe:LOAD:SOR? Parameters: None Description: Get SOR trace object. Refer to Section 2.5 “Message Format – Binary Data” for further details. Example: trac:load:sor? --- “BINARY ARRAY” #524047 //SCPI data size message for binary data transfer followed by array of SOR file bytes.
  • Page 79 TRACe Subsystem Commands (Cont’d) Example: trac:load:text? #6140479 //SCPI data size message for binary data transfer = 1310 nm //Wavelength FBR = SM //Fiber Type = 5 km // = 50 ns [ER] //Pulse Width and resolution type AVG = 6144 //Number of hardware averages IOR = 1.467700 //IOR value BSC = –78.50 //BSC value DATE = 08/13/09 //Date of test...
  • Page 80 Chapter 4 OTDR Commands 4.5.9 TRACe:LOAD:DATA? Command Syntax: TRACe:LOAD:DATA?<wsp><start>,<end>,<space> Parameters: <start> Starting distance (km) Floating point format Range: 0.0 － (Current distance range - <space>*resolution) <end> Ending distance (km) Floating point format Range: (<start>+<space>*resolution) － (Current distance range). <space> data point spacing in terms of resolution Numeric format Range: 1 －...
  • Page 81 (-109, "std_tooFewParameters, Missing Parameter") (-224, "std_illegalParmValue, Invalid Parameter Value") 4.5.11 TRACe:HEADer? Command Syntax: TRACe:HEADer? Parameters: None. Description: Get Trace Header Example: trac:head? --- OT, 1, 1, ABC, Tokyo, Yokohama, 1, Anritsu, TEST<END> Response: Nine header. Errors: (-108, "std_tooManyParameters, Parameter not Allowed") 4-29...
  • Page 82 Chapter 4 OTDR Commands 4.5.12 TRACe:STORe:SOR Command Syntax: TRACe:STORe:SOR<wsp><filepath&name> Parameters: <filepath&name> File path and file name to save the SOR file Description: Store the SOR file in internal memory of MT9083. Example: trac:stor:sor test.sor test.sor file is stored in root folder of internal memory. trac:stor:sor TEST/test.sor test.sor file is stored in TEST folder of internal memory.

  • Page 83: Display Subsystem Commands

    DISPlay Subsystem Commands 4.6 DISPlay Subsystem Commands The DISPlay subsystem provides access to the display mode and display zooming/scaling. 4.6.1 DISPlay:MODE Command Syntax: DISPlay:MODE<wsp><mode> Parameters: <mode> Display mode Numeric format Range: 0|1|2 0 – From A, 1 – From B, 2 – From Origin Description: Set display mode (From Origin, From A, From B).
  • Page 84 Chapter 4 OTDR Commands 4.6.4 DISPlay:ZOOM:HORIzontal Command Syntax: DISPlay:ZOOM:HORIzontal<wsp><level> Parameters: <level> Zoom level Numeric format Range: 0 – (6 - 16) Depends on current distance range 0 – Full zoom in, (6 – 16) – Full Zoom out Note: The maximum value for each distance is as follows. 0.5 km : 6 1 km : 7 2.5 km : 8...
  • Page 85 DISPlay Subsystem Commands 4.6.6 DISPlay:ZOOM:VERTical Command Syntax: DISPlay:ZOOM:VERTical<wsp><level> Parameters: <level> Zoom level Numeric format Range: 0 – 7 0 – Full zoom in, 7 – Full Zoom out Description: Set Vertical display zoom to specified level Example: disp:zoom:vert 2 Response: None Errors: (–224, "std_illegalValue, Invalid Parameter Value")
  • Page 86 Chapter 4 OTDR Commands 4.6.8 DISPlay:SCALe:HORIzontal Command Syntax: DISPlay:SCALe:HORIzontal<wsp><scale> Parameters: <scale> Horizontal scale range value in km Floating point format Range: 0.0096 – (0.5040 - 300.0000) Depends on current distance range (0.5 – 300) 0.0096 – Full zoom in, (0.5040 - 300.0000) – Full Zoom out Note: There are 17 predefined scale ranges (0.0096, 0.0144, 0.0288, 0.0528, 0.1008, 0.2544, 0.5040, 1.0032, 2.5008, 5.0016, 10.0032, 25.0032, 50.0016, 100.0032, 200.0016, 250.0032, 300.0000), the specified <scale>...
  • Page 87 DISPlay Subsystem Commands 4.6.10 DISPlay:SCALe:VERTical Command Syntax: DISPlay:SCALe:VERTical<wsp><scale> Parameters: <scale> Vertical scale range value in dB Floating point format Range: 0.5 – 65 0.5 – Full zoom in, 65 – Full Zoom out Note: There are 8 predefined scale ranges (0.5, 1.25, 2.5, 5, 12.5, 25, 50, 65), the specified <scale>...
  • Page 88 Chapter 4 OTDR Commands 4-36.
  • Page 89 Appendix A Recommended USB-Ethernet converter These USB-Ethernet converters manufactured by other companies are confirmed to work. Manufacturer Model name Planex UE-200TX-G Buffalo LUA-U2-KTX Buffalo LUA2-U2-ATX D-Link DUB-E100 Linksys USB200M Linksys USB300M...
  • Page 90 Appendix A Recommended USB-Ethernet converter A-2.

Table of Contents