21165803 rev 002 Remote Operation Getting Started Guide This guide describes remote operation and control of a Transport Module, Multi-Service Application Module (MSAM), or T-BERD/MTS 5800 using SCPI commands. SCPI command syntax and format requirements are presented along with instructions on how to establish a connection to a module and initiate example applications.
Remote Operation Getting Started Guide About the T-BERD/MTS 8000, 6000A, and 5800 About the T-BERD/MTS 8000, 6000A, and 5800 Before beginning a remote session, you should be familiar with the products and modules, ⁄ ⁄ found in the T-BERD MTS 8000 and T-BERD MTS 6000A Dual Module Carrier, Transport Module, and MSAM Getting Started Guide and T-BERD/MTS 5800 Getting Started Manual.
Page 3
Remote Operation Getting Started Guide About the T-BERD/MTS 8000, 6000A, and 5800 – JDSU Ethernet test set — A test set marketed by JDSU and designed to transmit an Acterna Test Packet (ATP) payload. These packets carry a time stamp used to calcu- late a variety of test results.
Remote Operation Getting Started Guide Remote control flow – T-BERD ⁄ MTS 8000 and T-BERD ⁄ MTS 6000A — The family of products, typically a combination of a base unit, a battery module, and one or more application modules. The Dual Module Carrier (DMC) can be used on the T-BERD / MTS 8000 platform to test using two MSAMs.
Page 5
Remote Operation Getting Started Guide Command syntax and format requirements :SENSE:DATA? cstatus:physical:signal Setup and action values are case-sensitive. :SENSe:PAYLoad:BERT:PATTern ALL_ONESCorrect :SENSe:PAYLoad:BERT:PATTern all_onesIncorrect Sockets and All remote control communications are socket-based TCP/IP. Any message passed via messages remote control must be terminated with a newline character ("\n") as shown (or ENTER in direct entry mode).
Remote Operation Getting Started Guide Getting the module port number Getting the module port number Starting remote The first step is to start remote operation operation 1 Open a TCP/IP socket connection to the unit on port 8000. 2 Start remote operation. *REM IMPORTANT: The *REM command must always be the first command sent after opening a...
Remote Operation Getting Started Guide Getting the remote control port number <slice> – SLIC1 - specify this location when connecting to an MTS-6000A MSAM to the transport module connected directly to the MTS-8000. – SLIC2, SLIC3 - specify this location when connecting to the second or third transport module (counting from the front) on an MTS-8000.
Page 8
Remote Operation Getting Started Guide Getting the remote control port number 4 Enable the remote control socket and return its port number :SYST:FUNC:PORT? <side>,<slice>,"BERT" Returns this module's remote control port number. If the module is not in a ready state, the response will be -1.
Page 9
Remote Operation Getting Started Guide Getting the remote control port number Remote Mode To inform the local user of the base unit of the GUI mode specified by the remote opera- Indicators tions, one of two icons will display on the GUI. Read-Only The Read-Only icon will display when the *REM <access-mode>...
Page 10
Remote Operation Getting Started Guide Getting the remote control port number The operation complete query from the SCPI standard is recognized, but does not have the *OPC? same behavior the standard describes. This due to the fact that in remote control, commands are processed serially;...
Remote Operation Getting Started Guide Working with applications :SYSTem:ERRor? The return from this command will be 0, "No error" There will be no return until the *RST command is finished. When the 0, "No error" response is received, the desired module connection has been completed.
Page 12
Remote Operation Getting Started Guide Working with applications > :SYSTem:ERRor? -113, "Undefined header; could not find ':sense:misspelled:command'" List Available :SYSTem:APPLication:APPLications? Applications This command returns a comma-separated list of all applications that can be launched in addition to any applications currently running. If an existing application is using a particular interface, then all other applications that use that interface type will be unavailable unless another suitable interface is available.
Page 13
Remote Operation Getting Started Guide Working with applications Examples: Launch 2G Fibre Channel on port 1 (or port 2 if port 1 is unavailable) > :SYSTem:APPLication:LAUNch TermFc1GL2Traffic Launch 2G Fibre Channel on port 2 > :SYSTem:APPLication:LAUNch TermFc1GL2Traffic 2 Another key difference from launching the test on the GUI is that in remote control, the test will come up in the "stopped"...
Remote Operation Getting Started Guide Using setups, actions, and results This command creates a remote control session with the selected application. :SESSion:CREate This command starts a previously created remote control session. :SESSion:STARt This command terminates the current remote control session. The session will automati- :SESSion:END cally be ended when an application is shut down or the remote connection is terminated.
Page 15
Remote Operation Getting Started Guide Using setups, actions, and results Setup values To change a setup, issue the SCPI command for that setup followed by the new value. The specification command in the following example sets (or changes) the receive pattern on port 2 to all ones: :SENSe:PAYLoad:BERT:PATTern1 ALL_ONES For setups that are arrays, you can specify an index or list indices of the array element(s)
Page 16
Remote Operation Getting Started Guide Using setups, actions, and results Correct format :SENSe:PAYLoad:BERT:PATTern ALL_ONES Incorrect format :SENSe:PAYLoad:BERT:PATTern "ALL_ONES" :SENSe:PAYLoad:BERT:PATTern all_ones Investigate the command line specifications, found elsewhere in this document, for a more complete list of string values and enumerated values that apply to various commands. Query values To query the current value of the setup, issue the SCPI command for that setup followed by a question mark.
Page 17
Remote Operation Getting Started Guide Using setups, actions, and results The following command toggles error rate insertion (reverses its state) for line 0. :SOURce:PAYLoad:BERT:INSert:TSE:RATE Executing the same command a second time without a parameter will turn error rate inser- tion back to its original state (OFF). Port Definition As with setups, the zero-based port index (0 for port 1 and 1 for port 2) may optionally be specified at the end of the command (or before the "?"...
Page 18
Remote Operation Getting Started Guide Using setups, actions, and results NOTE Not-a-Number formats from the SCPI standard are supported. If a result is not applicable or is out of range, a result query will return an appropriate value as shown below. 9.91e+37 Not Applicable/Not Ready (cannot be calculated from current information)
Remote Operation Getting Started Guide Rebooting an instrument Rebooting an instrument To reboot the unit, establish a socket connection to port 8000. The *REM command must be sent first. Then send the following command: :SYSTem:REBoot The time to reboot will depend on the platform type. Query the :SYST:FUNC:READY? <side>,<slice>,"BERT"...
Page 20
Remote Operation Getting Started Guide Example remote control procedures 2 Open a TCP/IP socket connection to the unit on the port number returned by the previous step. > *REM (Optional query to verify the > :SYST:FUNC:READY? PWRS,SLIC1,"BERT" BERT application is running and ready to communicate, returns "0" or "1") (Query for the port number to >...
Page 21
Remote Operation Getting Started Guide Example remote control procedures 1 Open a TCP/IP socket connection to the unit on port 8000. > *REM (Optional query to verify the module is > MOD:FUNC:SEL? OPPS,SLIC1,"BERT" powered on, returns "OFF" or "ON") (Query for the module's port number) >...
Page 22
Remote Operation Getting Started Guide Example remote control procedures Application interaction Querying for running Once the test unit is in remote control mode, the following commands may be useful to applications determine what applications can be launched. > :SYSTem:APPLication:APPLications? Get a list of available application names. The return value for this command depends on what is currently running.
Page 23
Remote Operation Getting Started Guide Example remote control procedures > :SYSTem:ERRor? 0, "No error" > :INITiate Start the test. (When applications are launched through remote control, they begin in the "stopped" state). > :SYSTem:ERRor? 0, "No error" When using remote control with the GUI enabled and an desired application is already running, a similar process can be followed to connect to it.
Page 24
Remote Operation Getting Started Guide Example remote control procedures > :SENSe:DATA? CSTatus:PDH:DS1:AIS Query the AIS alarm result If the unit is self-looped, it will detect the AIS. > :SOURce:PDH:DS1:INSert:AIS OFF Turn the alarm back off > :SENSe:DATA? CSTatus:PDH:DS1:AIS Query the AIS alarm result again Configuring a timed There are three test timing modes: not timed, timed test, and delayed-start timed test.
Remote Operation Getting Started Guide Demo Remote Control Scripts Leaving remote The *GUI command shuts down all applications running under remote contol and restores control mode the GUI interface. This command may take some time to finish processing. The ":SYSTem:ERRor?" query will still indicate when *GUI is complete, but most other remote control commands (except *REM, *RST, etc.) will no longer work.