1. Manuals
  2. Brands
  3. Agilent Technologies Manuals
  4. Remote Control
  5. OmniBER 720
  6. Manual

Agilent Technologies OmniBER 720 Manual

Hide thumbs Also See for OmniBER 720:
Agilent Technologies OmniBER 720 Manual
1
2
3
4
5
Table Of Contents
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
Table of Contents

Advertisement

Quick Links

Download this manual
Agilent Technologies OmniBER 720 Manual

Advertisement

Table of Contents
loading

Related Manuals for Agilent Technologies OmniBER 720

Summary of Contents for Agilent Technologies OmniBER 720

  • Page 1 Artisan Technology Group is your source for quality new and certified-used/pre-owned equipment SERVICE CENTER REPAIRS WE BUY USED EQUIPMENT • FAST SHIPPING AND DELIVERY Experienced engineers and technicians on staff Sell your excess, underutilized, and idle used equipment at our full-service, in-house repair center We also offer credit for buy-backs and trade-ins •...
  • Page 2 Remote Control OmniBER 720 Artisan Technology Group - Quality Instrumentation ... Guaranteed | (888) 88-SOURCE | www.artisantg.com...
  • Page 3 Agilent Technologies UK Limited Telecommunications Networks Test Division South Queensferry West Lothian, Scotland EH30 9TG Artisan Technology Group - Quality Instrumentation ... Guaranteed | (888) 88-SOURCE | www.artisantg.com...
  • Page 4 Remote Control Manual OmniBER 720 OmniBER 720 Artisan Technology Group - Quality Instrumentation ... Guaranteed | (888) 88-SOURCE | www.artisantg.com...
  • Page 5 In This Book This manual contains all the information necessary for remote control of the OmniBER 720. Artisan Technology Group - Quality Instrumentation ... Guaranteed | (888) 88-SOURCE | www.artisantg.com...

  • Page 6: Table Of Contents

    Connecting the OmniBER 720 via GPIB....3 Operating Distances..........3 Communication with the System Controller ..3 Connecting the OmniBER 720 to RS-232-C ... 4 OmniBER 720 RS-232-C Port....... 4 Connecting to a Computer ........5 Connection via a Modem........6 Connecting to a "Dumb"...
  • Page 7 List of Contents Parameters ..............2-3 Remote Control Commands ........2-5 INSTrument subsystem..........2-6 SOURce subsystem .............2-7 SOURce subsystem - Transmitter Common Commands2-8 SENSe subsystem ............2-11 SENSe subsystem - Receiver Common Commands ...2-12 SENSe Subsystem - Test Timing.........2-14 SENSe subsystem - Analysis Control......2-16 SENSe subsystem - Result Returning Commands ..2-17 Common Results ............2-17 SENSe subsystem - Trouble Scan Results....2-18...
  • Page 8 List of Contents Payload Layer Selection ........3-14 TUG Channel............3-15 TU Payload and Test Pattern ......... 3-16 Background Settings..........3-19 SOURce subsystem - Transmitter SDH OVERHEAD SETUP 3-22 SOURce subsystem - Transmitter SDH Test Function Com- mands ................3-34 INPut subsystem ............3-60 SENSe subsystem - Receiver SDH Settings....3-63 SDH Mapping settings...........
  • Page 9 List of Contents SDH Tributary Path FEBE Analysis Results ..3-88 SDH Block Based Bit Analysis Results ....3-88 TCM Path IEC Analysis Results ......3-89 TCM REI Analysis Results ........3-89 TCM OEI Analysis Results ........3-90 TCM Errors Analysis Results.........3-90 SDH M.2101 Analysis Results.......3-91 SDH Service Disruption Results ......3-92 SDH Optical Power Result........3-92 SDH Pointer Activity Results.........3-93...
  • Page 10 List of Contents SONET Mapping settings........4-60 SPE Layer Selection ..........4-61 VT Layer Selection..........4-61 Payload Layer Selection ........4-62 VT Group............... 4-63 VT Payload and Test Pattern ......... 4-64 SENSe subsystem - Receiver SONET Test Function Com- mands ................4-67 SENSe subsystem - Alarm Scan Control.....4-73 SENSe subsystem - SONET Tributary Scan Control ..4-75 SENSe subsystem - REI-L Result Enable/Disable ..4-77...
  • Page 11 Serial Poll (SPOLL) ..........37 Remote Enable (REMOTE) ........37 Local Lockout (LOCAL LOCKOUT) ....38 Local (LOCAL) ............38 7 Application Program Examples Initializing the OmniBER 720 ........7-2 List of Contents-8 Artisan Technology Group - Quality Instrumentation ... Guaranteed | (888) 88-SOURCE | www.artisantg.com...
  • Page 12 Setup the OmniBER 720 SDH Tx......7-3 Setup the OmniBER 720 SDH Rx ......7-5 Setup the OmniBER 720 SDH Tx to add Errors & Alarms7-6 Setup the OmniBER 720 SDH Tx Overhead Bytes . 7-7 Setup the OmniBER 720 SDH Tx for Overhead Byte Sequencing ...............
  • Page 13 List of Contents General Index Command Index List of Contents-10 Artisan Technology Group - Quality Instrumentation ... Guaranteed | (888) 88-SOURCE | www.artisantg.com...

  • Page 14: Methods Of Remote Control

    Methods of Remote Control Artisan Technology Group - Quality Instrumentation ... Guaranteed | (888) 88-SOURCE | www.artisantg.com...
  • Page 15 Methods of Remote Control Methods of Remote Control The OmniBER 720 can be remotely controlled in one of four ways: GPIB Provides a parallel interface that allows the connection of other devices to the system for example: Frequency Counter; Printer;...

  • Page 16: Connecting The Omniber 720 Via Gpib

    Communication with the System Controller Each device in the system must have a unique address to allow the controller to access each one individually. On the OmniBER 720 the address is set on the OTHER display under REMOTE CONTROL: To set the GPIB Address press...

  • Page 17: Connecting The Omniber 720 To Rs-232-C

    PC, Modem or Terminal, and an explanation of controller type. OmniBER 720 RS-232-C Port The OmniBER 720 acts as DCE (Data Communications Equipment), see Table 1-1 for a list of port connections. Artisan Technology Group - Quality Instrumentation ... Guaranteed | (888) 88-SOURCE | www.artisantg.com...

  • Page 18: Connecting To A Computer

    Methods of Remote Control Table 1-1 OmniBER 720 RS-232-C port connections OmniBER 720 Signal Input/Output Pin # Output Output Input Input Output Input Output Connecting to a Computer Table 1-2 OmniBER 720 to Computer Signal PC Pin # Signal OmniBER720...

  • Page 19: Connection Via A Modem

    RS-232-C cable Agilent Part Number 24542M (9 pin to 25 pin) will provide this connection. Controller Type Two methods of controlling the OmniBER 720 via RS-232-C are available: Simple method of control when commands are issued manually Terminal on a command by command basis.

  • Page 20: Terminal Mode

    Methods of Remote Control Terminal Mode Terminal mode is provided to allow the OmniBER 720 to be controlled by a "dumb" terminal and provides the following features: When connection is established via RS-232-C the OmniBER 720 responds with a "prompt".

  • Page 21: Connecting The Omniber 720 To A Lan

    The PORT NUMBER and MAC ADDRESS are assigned to the OmniBER 720 at the time of shipment. Connect the OmniBER 720 LAN interface to the LAN network. The OmniBER 720 must now be configured to accept the IP address, Subnet Mask and Default Gateway IP Address. Press...

  • Page 22: Current Settings

    BOOTP server on the network. When YES is selected the power must be cycled on the OmniBER 720 to allow for a change of settings. When power is restored the OmniBER 720 will issue BOOTP requests until it receives a reply from a suitably configured BOOTP server.

  • Page 23: New Settings (Keyboard Entry)

    Configuration The OmniBER 720 can only accept one tcp connection at a time and it cannot establish an outgoing call. The connection has to be directed to port 5001. For Example (from a UNIX system): telnet <IP address>...

  • Page 24: Controlling The Omniber 720

    The simplest way to verify the connection and become familiar with remote RS-232-C operation is to send a few commands and observe their effect. In this example using a terminal we will: • Take the OmniBER 720 under remote control • Initialize the OmniBER 720 •...

  • Page 25: To Initialize The Omniber 720

    To Initialize the OmniBER 720 Regardless of the current setup the following command will initialize the OmniBER 720. It sets the OmniBER 720 to the factory default settings and clears all registers. *RST It is recommended that you do not rely on default settings but program each setting to what you require.

  • Page 26: Remote Control Hints & Tips

    The order in which you should send the corresponding SCPI commands will usually follow the order in which you set up the OmniBER 720’s Front Panel. This can be seen in the Application Examples listed in the Manual. These could be used as a starting point in order to find the SCPI commands that correspond to particular OmniBER 720 Front Panel settings.

  • Page 27: Command Completion

    (of 128 bytes) exists in the OmniBER 720 between the RS-232 port and the SCPI parser. The effect of this is that even if the OmniBER 720 accepts the last character of a command, it cannot be assumed that it will immediately be executed - there could be several commands ahead of this one waiting in the buffer.

  • Page 28: Gating Control

    Stored Measurement Graphics is selected or not) to start gating. When the MEAS bit is set to one it means that the OmniBER 720 is gating. If it is required to retrieve Short Term results while the OmniBER 720 is gating then the STP bit (DB6) in the INSTrument status register can be used to determine when short term results can read i.e.

  • Page 29: User Locks

    Remote Control Hints & Tips User Locks User locks are a mechanism used within the OmniBER 720 to prevent the user selecting a particular instrument feature when some other selection takes priority. An example of this would be if you tried to modify the value of a SDH/SONET...

  • Page 30: Common Commands

    Common SCPI Command Reference SCPI Command Format, see page 2-2 Remote Control Commands, see page 2-5 INSTrument subsystem, see page 2-6 SOURce subsystem, see page 2-7 SOURce subsystem - Transmitter Common Commands, see page 2-8 SENSe subsystem, see page 2-see page 2-11 SENSe subsystem - Receiver Common Commands, see page 2-12 SENSe subsystem - Test Timing, see page 2-14 SENSe subsystem - Analysis Control, see page 2-16...

  • Page 31: Scpi Command Format

    SCPI Command Format SCPI Command Format Instrument functions such as making measurements, retrieving data, and querying status, are performed by stringing together SCPI "nodes" into commands. The SCPI commands are based on a hierarchical structure called a "subsystem" that comprises a top level "root"...

  • Page 32: Scpi Long Form Command Headers

    SCPI Command Format SCPI Long Form Command Headers The general rule for SCPI long form command headers that are greater than four characters in length is as follows: • Abbreviated short form mnemonics - the first four characters from the long form command header are used unless the fourth character is a vowel.
  • Page 33 SCPI Command Format Table 2-1 Parameter Types Parameter Description Types <string> Any set of ASCII characters enclosed within single quotes or double quotes. Examples are '1111111111111111' and"0000000000000000". <block> Used to transfer large quantities of related data. Blocks can be sent as definite length blocks (#<numeric><numeric>) or indefinite length blocks (#0).

  • Page 34: Remote Control Commands

    The remote control commands in this manual have been grouped into Sections that relate to instrument functions. These have then been split into Subsystems The Subsystems used in the OmniBER 720 are listed in table 2-2. Table 2-2 SCPI Subsystems...

  • Page 35: Instrument Subsystem

    INSTrument subsystem INSTrument subsystem The INSTrument subsystem is used to control the coupling between the transmitter and the receiver as provided on the OTHER SETTINGS CONTROL display. :INSTrument:COUPle <mode> <discrete> = Independent RTTX Coupled After a reset the receiver and transmitter coupling will be OFF. If the instrument is testing and the receiver and transmitter are coupled, changing certain transmitter settings will generate an error because the coupled receiver setting cannot be changed because of testing lock.

  • Page 36: Source Subsystem

    SOURce subsystem SOURce subsystem The SOURce subsystem contains commands that allow the transmitter settings to be set. The commands within the SOURce subsystem have been arranged as follows: Chapter 2 SOURce subsystem - Transmitter Common Commands Chapter 3 SDH SOURce subsystem - Transmitter SDH/SONET Chapter 4 SONET Settings Commands.

  • Page 37: Source Subsystem - Transmitter Common Commands

    SOURce subsystem - Transmitter Common Commands SOURce subsystem - Transmitter Common Commands :SOURce:DATA:TELecom:SOURce <discrete> <discrete> = OPT1 STM-0/STM-1 Optical OPT4 STM-0/STM-1/STM-4 Optical OPT16 STM-0/STM-1/STM-4/STM-16 Optical OC-1/OC-3 OC12 OC-1/OC-3/OC-12 OC48 OC-1/OC-3/OC-12/OC-48 Selects the output port.The output characteristics of each port are controlled by the :OUTPut subsystem.
  • Page 38 SOURce subsystem - Transmitter Common Commands :SOURce:DATA:TELecom:SOURce? Returns : <discrete> :SOURce:DATA:TELecom:TFUNction <discrete> <discrete> = NONE Test function off SONet PDHPayload requires a SONET option Selects the transmitter test function source. The corresponding query returns the transmitter test function source in discrete form as shown above.
  • Page 39 SOURce subsystem - Transmitter Common Commands • :SOURce:DATA:TELecom:SONet:PDHPayload:ERRor:TYPE <discrete> for SONET PDH payload errors. The corresponding query returns NONE or RATE. :SOURce:DATA:TELecom:ERRor:BIT? Returns : <discrete> 2-10 Artisan Technology Group - Quality Instrumentation ... Guaranteed | (888) 88-SOURCE | www.artisantg.com...

  • Page 40: Sense Subsystem

    SENSe subsystem SENSe subsystem The SENSe subsystem contains the commands that control the Receiver. These have been arranged in the following manner: Chapter 2 SENSe subsystem - Receiver Common Commands SENSe Subsystem - Test Timing TIMING CONTROL SENSe subsystem - Analysis Control MISC SENSe subsystem - Trouble Scan Results SENSe subsystem - Result Returning...

  • Page 41: Sense Subsystem - Receiver Common Commands

    SENSe subsystem - Receiver Common Commands SENSe subsystem - Receiver Common Commands :SENSe:DATA:TELecom:SENSe <discrete> <discrete> = OPT1 STM-0/STM-1 Optical OPT4 STM-0/STM-1/STM-4 Optical OPT16 STM-0/STM-1/STM-4/STM-16 Optical OC-1/OC-3 OC12 OC-1/OC-3/OC-12 OC48 OC-1/OC-3/OC-12/OC-48 Selects the input port. The input characteristics of each port are controlled by the INPut subsystem.
  • Page 42 SENSe subsystem - Receiver Common Commands The corresponding query returns the selected input port in discrete form, as listed above. :SENSe:DATA:TELecom:SENSe? Returns : <discrete> :SENSe:DATA:TELecom:TEST <boolean> <boolean> = 0 or OFF Stop the current test 1 or ON Start a new test Start/Stop the test as RUN/STOP The corresponding query returns the test state as 0 or 1.

  • Page 43: Sense Subsystem - Test Timing

    SENSe Subsystem - Test Timing SENSe Subsystem - Test Timing :SENSe:DATA:TELecom:TEST:TYPE <discrete> <discrete> = MANual Manual Test period SINGle Single Test period TIMed Timed Start Test period Selects the type of test period. If SING or TIM is selected, the duration is set using :SENS:DATA:TEL:TEST:PER.
  • Page 44 SENSe Subsystem - Test Timing :SENSe:DATA:TELecom:TEST:STARt <numeric>,<numeric>,<numeric>, <numeric>, <numeric> <numeric> = 1970 to 2069 Year <numeric> = 1 to 12 Month <numeric> = 1 to 31 <numeric> = 0 to 23 Hour <numeric> = 0 to 59 Minute Sets the test period start time when :SENS:DATA:TEL:TEST:TYPE <TIM> is selected.

  • Page 45: Sense Subsystem - Analysis Control

    SENSe subsystem - Analysis Control SENSe subsystem - Analysis Control :SENSe:DATA:TELecom:TEST:SUSPend <boolean> <boolean> = 0 or OFF G821 Analysis 1 or ON Suspend test during Signal Loss Sets the state of Analysis Control. The corresponding query returns the state of Analysis Control as 0 or 1. :SENSe:DATA:TELecom:TEST:SUSPend? Returns : <boolean>...

  • Page 46: Sense Subsystem - Result Returning Commands

    SENSe subsystem - Result Returning Commands SENSe subsystem - Result Returning Commands Common Results :SENSe:DATA? <string> <string> = "ETIMe" Returns the elapsed Time "ASEConds:PLOSs" Power loss “ASEConds:PSL” Pattern Sync Loss 2-17 Artisan Technology Group - Quality Instrumentation ... Guaranteed | (888) 88-SOURCE | www.artisantg.com...

  • Page 47: Sense Subsystem - Trouble Scan Results

    SENSe subsystem - Trouble Scan Results SENSe subsystem - Trouble Scan Results :SENSe:DATA:TELecom:TSCan:TYPE? Returns: <discrete> No Trouble ADET Alarms Detected Errors Detected Returns the Trouble Scan state. :SENSe:DATA:TELecom:TSCan:ERRors? Returns: <numeric>,<result> <numeric> = 0 to 4 Number of Troublescan error messages <discrete>...
  • Page 48 SENSe subsystem - Trouble Scan Results Trouble Scan Results and Priority RS B1 BIP MS B2 BIP PATH B3 BIP TCM ERR VC3 PATH BIP TU2 BIP TU12 BIP A1A2 FRAME MS FEBE/MS-REI TCM PATH IEC TCM OEI TCM REI PATH FEBE/HP-REI PATH IEC /HP-IEC VC3 PATH FEBE...

  • Page 49: Common System Commands

    Common System Commands Common System Commands SENSe subsystem - Configuring Graphics SENSe subsystem - Managing Graphics Stores SENSe subsystem - Retrieving Graphics Store Data SENSe subsystem - Retrieving Data for a Single Graph SENSe subsystem -Obtaining Graphics End of Measurement Results STATus Subsystem SYSTem Subsystem IEEE common capabilities...

  • Page 50: Sense Subsystem - Configuring Stored Measurements And Graphics

    SENSe subsystem - Configuring Stored Measurements and Graphics SENSe subsystem - Configuring Stored Measurements and Graphics :SENSe:DATA:TELecom:SMG <discrete> <discrete> = Storage Off ON or T1Second 1 Second resolution T1Minute 1 Minute resolution T15Minute 15 Minute resolution T1Hour 1 Hour resolution Sets the resolution of the stored measurements and graphics (SMG).
  • Page 51 SENSe subsystem - Configuring Stored Measurements and Graphics :SENSe:DATA:TELecom:SMG:STORe <discrete> <discrete> = INTernal Graphics store location DISK Disk storage Selects the storage location for the stored measurements and graphics (SMG). The corresponding query returns the storage location in discrete form. :SENSe:DATA:TELecom:SMG:STORe? Returns: <discrete>...

  • Page 52: Sense Subsystem - Managing Graphics Stores

    SENSe subsystem - Managing Graphics Stores SENSe subsystem - Managing Graphics Stores :SENSe:DATA:TELecom:SMG:CATalog? Requests a catalogue of the SMG store data. A record, as described, is produced for each SMG store being used. Returns: <record-1> <record-2> <record-10> <record-n> = <numeric>,<numeric>,<numeric>,<numeric>,<numeric>, <numeric>,<numeric>,<numeric>,<numeric>...
  • Page 53 SENSe subsystem - Managing Graphics Stores :SENSe:DATA:TELecom:SMG:SIZE? Requests the capacity of the graphics store and the number of store locations in use. The store size is a constant for a given instrument. Returns: <numeric>,<numeric> <numeric> = 702000 Store size <numeric> = 0 to 702000 Stores used :SENSe:DATA:TELecom:SMG:DELete <numeric>...

  • Page 54: Sense Subsystem - Retrieving Graphics Store Data

    SENSe subsystem - Retrieving Graphics Store Data SENSe subsystem - Retrieving Graphics Store Data The data used to construct all the graphs within a given store location can be extracted from the instrument and processed by a PC. The following glossary is applicable to the commands within the following sections.
  • Page 55 SENSe subsystem - Retrieving Graphics Store Data Do not rely upon the order or the total number of these labels from one version of the instrument to the next. Returns: <numeric> {,<string> {,<string> {...}}} <numeric> Number of strings to follow. <string>...
  • Page 56 SENSe subsystem - Retrieving Graphics Store Data :SENSe:DATA:TELecom:SMG:HDATa:PACKed? <numeric> <numeric> = -9 to 0 Graphics Store Location Disk Storage Returns a series of numerics (number of unchanged samples and histogram data) and 8 bit binary strings (alarm bar graph data), separated by commas. All results are returned even if some of those graph elements are not applicable to the particular instrument configuration at the time the measurement was made.
  • Page 57 SENSe subsystem - Retrieving Graphics Store Data :SENSe:DATA:TELecom:SMG:ALABels? <numeric>,<numeric> <numeric> = -9 to 0 Graphics Store Location Disk Storage <numeric> = 0 to n Graph number Requests the alarm labels from the selected SMG store and graph number. Do not rely upon the order or the total number of these labels from one version of the instrument to the next.

  • Page 58: Sense Subsystem - Retrieving Data For A Single Graph Element

    SENSe subsystem - Retrieving Data for a Single Graph Element SENSe subsystem - Retrieving Data for a Single Graph Element The data associated with each individual graph element may be obtained using one of the following commands: :SENSe:DATA:TELecom:SMG:EDATa? <numeric>,<numeric> <numeric> = -9 to 0 Graphics Store Location Disk Storage...
  • Page 59 SENSe subsystem - Retrieving Data for a Single Graph Element :SENSe:DATA:TELecom:SMG:VDATa? <numeric>,<numeric> <numeric> = -9 to 0 Graphics Store Location Disk Storage <numeric> = 0 to n Graph number Returns the number of data points that contributed to the graph element, followed by pairs of data points which include the elapsed time since the start of the measurement absoluted to January 1 1970, and either the histogram count or binary weighted alarm data value at that elapsed time.

  • Page 60: Sense Subsystem -Obtaining Graphics End Of Measurement Results

    SENSe subsystem -Obtaining Graphics End of Measurement Results SENSe subsystem -Obtaining Graphics End of Measurement Results :SENSe:DATA:TELecom:SMG:DATA? <numeric>,<string> <numeric> = -9 to 0 Graphics Store Location Disk Storage <string> = "ECOunt:SDH:FRAMe" SDH Frame error count "ECOunt:SDH:RSBip" B1 RS BIP error count "ECOunt:SDH:MSBip"...
  • Page 61 SENSe subsystem -Obtaining Graphics End of Measurement Results "ERATio:SDH:FEBE" or Path FEBE/HP-REI error ratio "ERATio:SDH:REI" "ERATio:SDH:PIEC" Path IEC error ratio "ERATio:SDH:TRIB:FEBE" or TU FEBE/LP-REI error ratio "ERATio:SDH:TRIB:REI" "ERATio:SDH:TRIB:PBIP" TU path BIP error ratio “ERATio:SDH:TCM:PIEC” TCM Path IEC error ratio “ERATio:SDH:TCM:REI” TCM REI error ratio “ERATio:SDH:TCM:OEI”...
  • Page 62 SENSe subsystem -Obtaining Graphics End of Measurement Results "ASEConds:SDH:K1K2" K1K2 change seconds "ASEConds:SDH:PFERf" or STM Path FERF/HP-RDI "ASEConds:SDH:RDI" seconds "ASEConds:SDH:OPSL" Overhead Pattern Sync Loss "ASEConds:SDH:TRIB:LOP" TU Loss of pointer seconds "ASEConds:SDH:TRIB:PAIS" TU Path AIS seconds "ASEConds:SDH:TRIB:PFERf" or TU Path FERF/LP-RDI seconds "ASEConds:SDH:TRIB:RDI"...
  • Page 63 SENSe subsystem -Obtaining Graphics End of Measurement Results "ERATio:SONet:CVIec" CV-IEC error ratio "ERATio:SONet:TRIB:REIV" REI-V (VT FEBE) error ratio "ERATio:SONet:TRIB:CVV" CV-V (VT path BIP) error ratio "PACTivity:SONet:NDFSeconds" SPE Pointer NDF seconds "PACTivity:SONet:MNDFseconds" SPE Pointer MNDF seconds "PACTivity:SONet:PCOunt" SPE Pointer +ve Adj Count "PACTivity:SONet:NCOunt"...

  • Page 64: Status Subsystem

    STATus subsystem STATus subsystem This subsystem controls the status reporting registers. SCPI defined status registers QUEStionable, OPERation and INSTrument are provided. In addition instrument defined status registers DATA, SDH, SDH2, SDH3, SON, SON2 and SON3 are provided. For detailed information on status reporting refer to Section 6 of this manual.
  • Page 65 STATus subsystem :STATus:<Status Register>:PTRansition? Returns : <numeric> :STATus:<Status Register>:NTRansition <numeric> Sets the negative Transition filter. Setting a bit in the negative Transition Filter shall cause a 1 to 0 transition in the corresponding bit of the <Status Register>’s Condition register to cause a 1 to be written in the corresponding bit of the <Status Register>’s Event register.

  • Page 66: System Subsystem

    SYSTem Subsystem SYSTem Subsystem :SYSTem:WINDow<type> Selects the display type, Single or Multiple. Selection of SINGle results in faster remote operation. <type> = SINGle Selects single window display MULTiple Selects multiple window display The corresponding query returns the display type. :SYSTem:WINDow? Returns : <type>...
  • Page 67 The corresponding query returns the state of KEYBOARD LOCK as 0 or 1. :SYSTem:KLOCk? Returns : <boolean> :SYSTem:LOCal Set the OmniBER 720 to Local (keyboard) control. :SYSTem:REMote Set the OmniBER 720 to Remote control. 2-38 Artisan Technology Group - Quality Instrumentation ... Guaranteed | (888) 88-SOURCE | www.artisantg.com...
  • Page 68 The serial number is returned as a string in the form "GBnnnnnnnn". GB signifies the country of origin (Great Britain). :SYSTem:CONF <block> <block> = #0 type Block Sets the OmniBER 720 to the state defined by the Block data. The corresponding query returns the instrument state in block form. :SYSTem:CONF? Returns : #0<block>...
  • Page 69 SYSTem Subsystem :SYSTem:PRINt:AUTO <boolean> <boolean> = 0 or OFF 1 or ON Determines whether the selected results are logged to the selected logging device. If OFF is selected results can only be logged using :SYSTem:PRINt. If ON is selected further selection of :SYSTem:PRINt:PERiod <period> is required. The corresponding query returns the logging state as 0 or 1.
  • Page 70 SYSTem Subsystem :SYSTem:PRINt:UPERiod <numeric>, <discrete> <numeric> = 1 to 99 <discrete> = Hours (1 - 99) Minutes (10 - 99) Sets the USER defined logging period in the range 10 to 99 minutes or 1 to 99 hours. The corresponding query returns the User defined period in numeric, discrete form, as listed above.
  • Page 71 SYSTem Subsystem In conjunction with :SYSTem:PRINt:SPAN <content> determines the type of selected results to be logged to the selected logging device. The corresponding query returns the result content in discrete form, as listed above. :SYSTem:PRINt:CONTent? Returns : <content> :SYSTem:PRINt:SPAN <content> <content>...
  • Page 72 SYSTem Subsystem :SYSTem:PRINt:MODE <mode> <mode> = NORMal Normal print format COMPressed Compressed print format Only valid when RS232 or Parallel printer is selected. Determines the column width of the printed results. The corresponding query returns the print mode in discrete form, as listed above. :SYSTem:PRINt:MODE? Returns : <mode>...
  • Page 73 SYSTem Subsystem RS232 RS-232-C external printer DISK Internal Disc Drive PARallel Centronics external printer Selects the logging device for results logging. The corresponding query returns the logging device selected in discrete form as listed above. :SYSTem:LOGGing:DEVice? Returns : <type> :SYSTem:PRINt:DEMand <mode> <mode>...
  • Page 74 SYSTem Subsystem DISK Send screen dump information to floppy disk Selects the destination of screen dump information. The corresponding query returns the current selection :SYSTem:PRINt:SDUMp:COMPression <boolean> <boolean> = 0 or OFF Deselect compression of screen dump information 1 or ON Select compression of screen dump information :SYSTem:DISK:FORMat...
  • Page 75 SYSTem Subsystem Saves required information to disk. If PRN is selected further selection of :SYSTem:DISK:SAVE:MODE <discrete> is required. :SYSTem:DISK:SAVE:MODE <discrete> <discrete> = APPend Add to file OVERwrite Overwrite existing file Designates the position within the file to which the results are saved if the file type is PRN.
  • Page 76 SYSTem Subsystem <store> = 1 to 4 Instrument store number <directory> = Up to 256 Alphanumeric character string <filename> = Up to 8 Alphanumeric character string <overwrite> = Copying to Disk: If file exists will not overwrite. Copying to Instrument: If Option structure is different from stored configuration will not copy.
  • Page 77 SYSTem Subsystem <overwrite> = If file exists will not overwrite Will overwrite automatically Copy stored measurement graphics from instrument store to Disk. Set :SYSTem:DISK:FILE:COPY:SMG:FORMat <type> to NORM or CSV before issuing this command. :SYSTem:DISK:FILE:DELete <filename> <filename> = Up to 12 Alphanumeric character string including extension :SYSTem:DISK:DIRectory:DELete Delete current directory.
  • Page 78 SYSTem Subsystem List only files with PRN extension <format> = SHORt List file name only LONG List file name, file size, date & time modified DESCription list file name, file description Returns directory list. :SYSTem:DISK:PWD? Returns : <string> Returns directory name. :SYSTem:DISK:FREE? Returns : <numeric>...
  • Page 79 SYSTem Subsystem :SYSTem:SSETting:LOCK? Returns : <boolean> :SYSTem:SSETting:LABel <numeric>,<string> <numeric> = 1 to 4 Stored Setting number <string> = 1 to 24 Stored Settings store label characters Titles the Store Setting location with the contents of the string. The corresponding query returns the title of the selected Stored Setting location as a string.

  • Page 80: Ieee Common Capabilities

    *IDN? Identification Query - Returns the Manufacture Name, Model Number & Name, Serial Number, Firmware Revision Number as a string: "AGILENT TECHNOLOGIES, J1407A, OMNIBER , GBnnnnnnnn, A.nn.nn" GB signifies the country of origin (Great Britain). 2-51 Artisan Technology Group - Quality Instrumentation ... Guaranteed | (888) 88-SOURCE | www.artisantg.com...
  • Page 81 *LRN? Learn Query - Returns the instrument settings configuration in <#0 Block> form. *OPC Operation Complete - Masks the OPC bit in the Event Status Register. *OPC? Operation Complete Query - Returns a 1 when the OPC bit in the Event Status Register is set to 1 (true).
  • Page 82 Trigger - Not implemented on OmniBER 720. *TRG? Trigger Query - Not implemented on OmniBER 720. *WAI Wait To Continue - Not implemented on the OmniBER 720. 2-53 Artisan Technology Group - Quality Instrumentation ... Guaranteed | (888) 88-SOURCE | www.artisantg.com...
  • Page 83 IEEE common capabilities *TST Initiate Self Test *TST? Self Test Query 2-54 Artisan Technology Group - Quality Instrumentation ... Guaranteed | (888) 88-SOURCE | www.artisantg.com...

  • Page 84: Sdh Command Reference

    SDH SCPI Command Reference OUTPut subsystem, see page 3- 3. SOURce subsystem - Transmitter SDH Settings Commands, see page 3- 7. SDH Mapping Settings, see page 3-11. SOURce subsystem - Transmitter SDH OVERHEAD SETUP, see page 3- 22. SOURce subsystem - Transmitter SDH Test Function Commands, see page 3-34. INPut subsystem, see page 3 60.
  • Page 85 This chapter contains detailed information on the SCPI (Standard Commands for Programming Instruments) and IEEE 488.2 common commands you will use when writing programs to control your OmniBER 720 for SDH operation. Please also refer to chapter 2 Common Commands for general information on SCPI command formats and for a list of commands that are common to SDH and SONET.

  • Page 86: Output Subsystem

    SDH Command Reference OUTPut subsystem OUTPut subsystem This subsystem controls the characteristics of the instrument’s output ports. :OUTPut:TELecom:OPT1:RATE <discrete> <discrete> = STM0 STM-0 optical STM1 STM-1 Optical Selects the output rate for the STM-0/STM-1 optical output port. This command is only valid when :SOURce:DATA:TELecom:SOURce <discrete>...
  • Page 87 SDH Command Reference OUTPut subsystem :OUTPut:TELecom:OPT1:LASer <boolean> <boolean> = 0 or OFF 1 or ON Controls the state of the laser (ON or OFF) on the Optical module. The corresponding query returns the state of the laser as 0 or 1. :OUTPut:TELecom:OPT1:LASer? Returns : <boolean>...
  • Page 88 SDH Command Reference OUTPut subsystem Selects the wavelength of the output optical signal on the Optical module. The corresponding query returns the output optical wavelength in discrete form, as listed above. :OUTPut:TELecom:OPT4:WAVelength? Returns : <discrete> :OUTPut:TELecom:OPT4:LASer <boolean> <boolean> = 0 or OFF 1 or ON Controls the state of the laser (ON or OFF) on the Optical module.
  • Page 89 SDH Command Reference OUTPut subsystem :OUTPut:TELecom:OPT16:RATE? Returns : <discrete> :OUTPut:TELecom:OPT16:INTerface? Returns: <discrete> Returns the selected output port interface in discrete form - always OPTical. :OUTPut:TELecom:OPT16:WAVelength <discrete> <discrete> = NM1310 1310 nm NM1550 1550 nm Selects the wavelength of the output optical signal on the Optical module. Only valid for Dual Wavelength options.

  • Page 90: Source Subsystem - Transmitter Sdh Settings Commands3-7

    SDH Command Reference SOURce subsystem - Transmitter SDH Settings Commands SOURce subsystem - Transmitter SDH Settings Commands SDH Clock settings :SOURce:CLOCk:SDH:SOURce <discrete> <discrete> = INTernal Internal EXTernal External MTS Clock/Data ROPT0 STM-0 Optical RMON0 STM-0 Monitor ROPT1 STM-1 Optical RMON1 STM-1 Monitor ROPT4 STM-4 Optical...
  • Page 91 SDH Command Reference SOURce subsystem - Transmitter SDH Settings Commands Selects the transmitter SDH EXT MTS clock sync source format. The corresponding query returns the EXT MTS clock sync source format in discrete form as listed above. :SOURce:CLOCk:SDH:FORMat? Returns : <discrete>...

  • Page 92: Thru Mode Settings

    SDH Command Reference SOURce subsystem - Transmitter SDH Settings Commands Thru mode settings :SOURce:DATA:TELecom:SDH:THRumode <discrete> <discrete> = INTernal Select Normal SDH Mode THRu Select SDH Thru Mode Selects/Deselects SDH THRU mode. The corresponding query returns the THRU mode state in discrete form as listed above.
  • Page 93 SDH Command Reference SOURce subsystem - Transmitter SDH Settings Commands :SOURce:DATA:TELecom:SDH:THRumode:PAYLoad:OVERwrite:ENABle <boolean> <boolean> = 0 or OFF 1 or ON Enable the thru-mode payload overwrite. The corresponding query returns the payload overwrite enable state in discrete form as listed above. :SOURce:DATA:TELecom:SDH:THRumode:PAYLoad:OVERwrite:ENABle? 0 or 1 Returns :...

  • Page 94: Sdh Mapping Settings

    SDH Command Reference SOURce subsystem - Transmitter SDH Settings Commands SDH Mapping Settings :SOURce:DATA:TELecom:SDH:AU4 <numeric> <numeric> = 1 to 16 AU-4 number. Only valid if :OUTPut:TELecom:OPT16:RATE <discrete> is set to a rate higher than STM-1. Selects the transmitted STM-1 AU-4 that is selected for test. The corresponding query returns the STM-1 AU-4 selected for test in numeric form, as listed above.

  • Page 95: Tandem Connection Monitoring (Tcm) - Sdh Only3

    SDH Command Reference SOURce subsystem - Transmitter SDH Settings Commands The corresponding query returns the AU-4-4C selected for test in numeric form, as listed on previous page. :SOURce:DATA:TELecom:SDH:AU4C? Returns : <numeric> Tandem Connection Monitoring (TCM) - SDH ONLY :SOURce:DATA:TELecom:SDH:TCM:PATH <discrete> <...

  • Page 96: Au Layer Selection

    SDH Command Reference SOURce subsystem - Transmitter SDH Settings Commands :SOURce:DATA:TELecom:SDH:TCM:APID:DATA <string> Sets the user defined pattern that is to be transmitted in the TC-APId message. The pattern should be 15 characters long. If less than 15 characters are input, the instrument will pad with the required number of NULL characters and a frame marker byte with CRC7 is added to the string.

  • Page 97: Tu Layer Selection

    SDH Command Reference SOURce subsystem - Transmitter SDH Settings Commands :SOURce:DATA:TELecom:SDH:AU3? Returns : <numeric> TU Layer Selection :SOURce:DATA:TELecom:SDH:PAYLoad <discrete> <discrete> = VC4 or M140 140 Mb/s STM-0 TU3 or M34 34 Mb/s TU12 or M2 2 Mb/s VC-2 TU11 or DS1 TU11 VC4_4C VC-4-4c...

  • Page 98: Tug Channel

    SDH Command Reference SOURce subsystem - Transmitter SDH Settings Commands :SOURce:DATA:TELecom:SDH:MAPPing? Returns: <discrete> :SOURce:DATA:TELecom:SDH:TRIButary:MAPPing <discrete> <discrete> = BULK Bulk Filled Selects the transmitter low order mapping. Only valid if :SOURce:DATA:TELecom:SDH:PAYLoad <discrete> is set to TU3, TU12 or TU11. The corresponding query returns the low order mapping in discrete short form. :SOURce:DATA:TELecom:SDH:TRIButary:MAPPing? Returns: <discrete>...

  • Page 99: Tu Payload And Test Pattern

    SDH Command Reference SOURce subsystem - Transmitter SDH Settings Commands :SOURce:DATA:TELecom:SDH:TRIButary <numeric> <numeric> = 1 to 3 Tributary Number for TU-12 1 to 4 Tributary number for TU-11 Selects the SDH Transmitter active TU within the selected TUG2. The corresponding query returns the active tributary in numeric form. :SOURce:DATA:TELecom:SDH:TRIButary? Returns : <numeric>...
  • Page 100 SDH Command Reference SOURce subsystem - Transmitter SDH Settings Commands :SOURce:DATA:TELecom:SDH:PAYLoad:PATTern <discrete> <discrete> = PRBS9 PRBS11 PRBS15 PRBS23 AZERo All Zeros AONE All Ones P1010 Word 1010 P1000 Word 1000 UWORd 16 Bit User Word Selects the transmitter SDH payload data pattern. See: :SOURce:DATA:TELecom:SDH:PAYLoad:TYPE <discrete>.
  • Page 101 SDH Command Reference SOURce subsystem - Transmitter SDH Settings Commands Selects the PRBS pattern polarity. The corresponding query returns the polarity in discrete form as listed above. :SOURce:DATA:TELecom:SDH:PRBS:POLarity? Returns: <discrete> :SOURce:DATA:TELecom:SDH:PAYLoad:OFFSet <numeric> <numeric> = -100 to +100 Parts per Million -0.000100 to 0.000100 % or Ratio <suffix>...

  • Page 102: Background Settings

    SDH Command Reference SOURce subsystem - Transmitter SDH Settings Commands TU2-4C TU2-5C TU2-6C <numeric> = 1 to 6 TU2-2C selected (second parameter) 1 to 5 TU2-3C selected Selects the TU2 concatenation (first parameter)and starting at TU (second parameter). The corresponding query returns the TU2 concatenation and starting at TU in numeric form as listed above.
  • Page 103 SDH Command Reference SOURce subsystem - Transmitter SDH Settings Commands :SOURce:DATA:TELecom:SDH:AU4:BACKground <discrete> <discrete> = UNEQuipped Fixed at 00000000 AS_FG As Foreground Selects the payload in the background (non test) AU-4s. This command only applies if the selected mapping is AU4. The corresponding query returns the type of payload in the background AU-4s in discrete short form.
  • Page 104 SDH Command Reference SOURce subsystem - Transmitter SDH Settings Commands :SOURce:DATA:TELecom:SDH:PRIMary:BACKground:PAYLoad :PATTern? Returns: <discrete> :SOURce:DATA:TELecom:SDH:TUG3:BACKground:PAYLoad:PATTern <numeric> <discrete> <numeric> = 1 to 3 TUG 3 to be configured <discrete> TU-3 structure TU12 TU-12 structure UWORd User Defined Selects the structure in a background TUG3. This command is only valid if the selected TUG3 is not the current foreground.

  • Page 105: Source Subsystem - Transmitter Sdh Overhead Setup

    SDH Command Reference SOURce subsystem - Transmitter SDH OVERHEAD SETUP SOURce subsystem - Transmitter SDH OVERHEAD SETUP Lists the settings for the commands associated with the TRANSMIT OVERHEAD SETUP display. :SOURce:DATA:TELecom:SDH:OVERhead:DEFault Sets all overhead bytes to their default value: Byte Value Byte Value...
  • Page 106 SDH Command Reference SOURce subsystem - Transmitter SDH OVERHEAD SETUP Sets the binary value for the selected transmitter section overhead byte. All overhead bytes in the transmitted signal can be configured. The required byte is specified by 3 command parameters The first parameter, STM-1 Number, identifies an STM-1 within the signal.
  • Page 107 SDH Command Reference SOURce subsystem - Transmitter SDH OVERHEAD SETUP K2|D4|D5|D6|D7|D8|D9|D10|D11 D12|S1/Z1|M1/Z2|E2 X11|X12|X13|X21|X22|X23|X31|X32|X33| X41|X42|X52|X53|X61|X62|X63| X71|X72|X73|X81|X82|X83|X91|X92|X93 <string> = "00" to "FF" Sets the hexadecimal value for the selected transmitter transport overhead byte. All overhead bytes in the transmitted signal can be configured. The required byte is specified by 3 command parameters The first parameter, STM-1 Number, identifies an STM-1 within the signal.
  • Page 108 SDH Command Reference SOURce subsystem - Transmitter SDH OVERHEAD SETUP :SOURce:DATA:TELecom:SDH:POVerhead:DATA <discrete>,<string> <discrete> = C2|G1|F2|H4|Z3/F3|Z4/K3|Z5/N1|V5 <string> = "xx00xxx0" to "xx11xxx1" for V5 “00000000 to 11111111 not V5 Sets the binary value of the specified VC-4-NC/VC-4/VC-3 High Order POH overhead byte. The corresponding query returns the value of the specified STM-1 path overhead byte as a string, as described above.
  • Page 109 SDH Command Reference SOURce subsystem - Transmitter SDH OVERHEAD SETUP :SOURce:DATA:TELecom:SDH:POVerhead:SLABel? Returns: <discrete> :SOURce:DATA:TELecom:SDH:POVerhead:J1:PATTern <discrete> <discrete> = DEFault 64 NULL characters TEST Test Message USER User Defined CRC7Test GB(serial number) CRC7User User Defined Sets the type of pattern that is to be transmitted in the J1 byte of the STM path overhead.
  • Page 110 SDH Command Reference SOURce subsystem - Transmitter SDH OVERHEAD SETUP :SOURce:DATA:TELecom:SDH:POVerhead:J1:CRC7 <string> This command sets the CRC7 based user defined string that is to be transmitted using the J1 byte and configures the instrument to use this string. The string can be up to 15 characters in length;...
  • Page 111 SDH Command Reference SOURce subsystem - Transmitter SDH OVERHEAD SETUP :SOURce:DATA:TELecom:SDH:TRIButary:POVerhead:DATA? <discrete> Returns: <string> :SOURce:DATA:TELecom:SDH:OVERhead:J0:PATTern <discrete> <discrete> = FIXed Fixed Byte TEST GB(serial number) USER User Defined Sets the type of pattern that is to be transmitted in the J0 byte of the STM regenerator section overhead.
  • Page 112 SDH Command Reference SOURce subsystem - Transmitter SDH OVERHEAD SETUP Returns a 15 byte block of data. Each byte represents the hexadecimal value of an ASCII character "00" to "FF". The 15 hexadecimal numbers are preceded by the header "#215". If FIXed was returned in response to :SOURce:DATA:TELecom:SDH:OVerhead:J0:PATTern?, this query command is not valid.
  • Page 113 SDH Command Reference SOURce subsystem - Transmitter SDH OVERHEAD SETUP :SOURce:DATA:TELecom:SDH:TRIButary:POVerhead:J1? Returns : <string> :SOURce:DATA:TELecom:SDH:TRIButary:POVerhead:J1:CRC7 <string> This command sets the CRC7 based user defined string that is to be transmitted using the J1 byte of the TU3 path overhead, and configures the instrument to use this string.
  • Page 114 SDH Command Reference SOURce subsystem - Transmitter SDH OVERHEAD SETUP The corresponding query returns the type of pattern being transmitted in VC-2, VC- 11 or VC-12 path overhead byte J2 in discrete form as listed above. :SOURce:DATA:TELecom:SDH:TRIButary:POVerhead:J2:PATTern? Returns : <discrete> :SOURce:DATA:TELecom:SDH:TRIButary:POVerhead:J2 <string>...
  • Page 115 SDH Command Reference SOURce subsystem - Transmitter SDH OVERHEAD SETUP :SOURce:DATA:TELecom:SDH:TRIButary:POVerhead:V5:SLABel <numeric> <numeric> = 0 to 7 Sets the VC-2, VC-12 or VC-11 signal label (Byte V5) value. The corresponding query returns the signal label value in numeric form. :SOURce:DATA:TELecom:SDH:TRIButary:POVerhead:V5:SLABel? Returns : <numeric>...
  • Page 116 SDH Command Reference SOURce subsystem - Transmitter SDH OVERHEAD SETUP :SOURce:DATA:TELecom:SDH:POVerhead:H4Sequence <discrete> <discrete> = LONG Long Sequence SHORt Short Sequence C0C1 COC1 Sequence Sets the H4 path overhead byte sequence length when :SOURce:DATA:TELecom:SDH:PAYLoad <discrete> is set to TU2, TU11 or TU12.

  • Page 117: Source Subsystem - Transmitter Sdh Test Function Commands

    SDH Command Reference SOURce subsystem - Transmitter SDH Test Function Commands SOURce subsystem - Transmitter SDH Test Function Commands :SOURce:DATA:TELecom:SDH:TFUNction:TYPE <discrete> <discrete> = ERRor Errors & Alarms POINter Pointer SEQuence Overhead sequences STESt Optical Stress MSPMessages MSP messages IDCC Insert Datacomm OBERtest Overhead BER test Selects the SDH transmit test function type.
  • Page 118 SDH Command Reference SOURce subsystem - Transmitter SDH Test Function Commands TCM Outgoing Error Indication TCBip TCM BIP TUBip Tributary BIP LPRei Tributary FEBE FRAMe Frame TCM errors are only available in SDH mode Selects SDH transmit test function error type when :SOURce:DATA:TELecom:SDH:TFUNction:TYPE <discrete>is set to ERR .
  • Page 119 SDH Command Reference SOURce subsystem - Transmitter SDH Test Function Commands All except Frame errors USER User error rate Frame Errors only Frame Errors only THRee Frame Errors only FOUR Frame Errors only Selects the transmitter SDH Error rate of the error type selected by :SOURce:DATA:TELecom:SDH:ERRor:TYPE <discrete>.
  • Page 120 SDH Command Reference SOURce subsystem - Transmitter SDH Test Function Commands Note that the maximum user defined error rate is dependent on both error type and line rate. The corresponding query returns the user defined SDH Error Add rate in numeric form.
  • Page 121 SDH Command Reference SOURce subsystem - Transmitter SDH Test Function Commands :SOURce:DATA:TELecom:SDH:PDHPayload:ERRor:RATE? Returns: <discrete> :SOURce:DATA:TELecom:SDH:PDHPayload:ERRor:RATE:USER <numeric> <numeric>= 1.1E-3 to 0.1E-9 mantissa resolution 0.1, exponent resolution 1 Sets the user defined SDH PDH payload Error Add rate of the error type selected by :SOURce:DATA:TELecom:SDH:PDHPayload:ERRor:TYPE <discrete>.
  • Page 122 SDH Command Reference SOURce subsystem - Transmitter SDH Test Function Commands :SOURce:DATA:TELecom:SDH:ERRor:MSPThreshold:NERRors? Returns : <numeric> :SOURce:DATA:TELecom:SDH:ERRor:MSPThreshold:EINTerval <discrete> <discrete> = MS10 10 milliseconds MS100 100 milliseconds 1 second 10 seconds S100 100 seconds S1000 1,000 seconds S10000 10,000 seconds Sets the interval between MSP Threshold errors when :SOURce:DATA:TELecom:SDH:ERRor:RATE <discrete>is set to MSPT .
  • Page 123 SDH Command Reference SOURce subsystem - Transmitter SDH Test Function Commands PAIS Path AIS HPRDi Path FERF PUNequipped Path Unequipped TCLom TCM Loss of Multiframe IAIS TCM Incoming AIS TCRDi TCM Remote Defect Indication TCM Outgoing Defect Indication TULop TU Loss of Pointer TUPais TU Path AIS LPRDi...
  • Page 124 SDH Command Reference SOURce subsystem - Transmitter SDH Test Function Commands Selects the Pointer adjustment type when :SOURce:DATA:TELecom:SDH:TFUNction:TYPE <discrete> is set to POIN. The corresponding query returns the pointer adjustment type in discrete form as listed above. :SOURce:DATA:TELecom:SDH:POINter? Returns : <discrete>...
  • Page 125 SDH Command Reference SOURce subsystem - Transmitter SDH Test Function Commands :SOURce:DATA:TELecom:SDH:POINter:IDECrement <numeric> <numeric> = 1 to 10 TU-3, AU-3, AU-4, AU-4Nc 1 to 5 TU-2, TU-12, TU-11 Selects the number of places by which the pointer is to be incremented or decremented when :SOURce:DATA:TELecom:SDH:TFUNction:TYPE <discrete>...
  • Page 126 SDH Command Reference SOURce subsystem - Transmitter SDH Test Function Commands :SOURce:DATA:TELecom:SDH:TRIButary:POINter:TRANsmitted? Returns: <numeric> Returns the currently transmitted value of the TU pointer in numeric form. :SOURce:DATA:TELecom:SDH:TRIButary:POINter:VALue <numeric> <numeric> = 0 to 764 for TU-3 0 to 427 for TU-2 0 to 139 for TU-12 0 to 103...
  • Page 127 SDH Command Reference SOURce subsystem - Transmitter SDH Test Function Commands :SOURce:DATA:TELecom:SDH:POINter:ADJust Adjust pointer to new settings if :SOURce:DATA:TELecom:SDH:POINter <discrete> is set to BURS or NPO . :SOURce:DATA:TELecom:SDH:POINter:OFFSet <discrete> <discrete> = SIGNal Line offset VC-4 rate offset TU rate offset Determines whether the Output signal rate, VC Rate or TU rate is offset.
  • Page 128 SDH Command Reference SOURce subsystem - Transmitter SDH Test Function Commands :SOURce:DATA:TELecom:SDH:POINter:G783 <discrete> <discrete> = PASingle Periodic alternate single (a) WADDed Periodic with added (b) WCANcelled Periodic with cancelled (c) DOUBle Periodic alternate double (d) RSINgle Repeating single (e) RBURst Repeating burst (f) RPTRansient Repeating phase transient...
  • Page 129 SDH Command Reference SOURce subsystem - Transmitter SDH Test Function Commands (Obsolete) Set the type of G.783 pointer sequence when :SOURce:DATA:TELe- com:SDH:TFUNction:TYPE <discrete> is set to POIN and :SOURce:DATA:TELe- com:SDH:POINter <discrete> is set to G783 and :SOURce:DATA:TELecom:SDH:POINter:G783 <discrete> :is set to SING. The corresponding query returns the type in discrete form as listed above.
  • Page 130 SDH Command Reference SOURce subsystem - Transmitter SDH Test Function Commands :SOURce:DATA:TELecom:SDH:POINter:G783:POLarity? Returns : <discrete> :SOURce:DATA:TELecom:SDH:POINter:G783:INTerval <numeric><suffix> <numeric> = 1 to 500 See text <suffix> = milliseconds seconds Selects the interval between G.783 adjustments. (AU-4, AU-4-NC, AU-3, TU-3) Range is 7.5ms, 10ms, 20ms, 30ms, 34ms, 40ms to 100ms in 10ms steps.
  • Page 131 SDH Command Reference SOURce subsystem - Transmitter SDH Test Function Commands :SOURce:DATA:TELecom:SDH:SEQuence <discrete> <discrete> = STOP Stop current sequence STARt Start new sequence Starts/Stops a Single or Repeat run Sequence. The corresponding query returns the Sequence mode in discrete form as listed above.
  • Page 132 SDH Command Reference SOURce subsystem - Transmitter SDH Test Function Commands K1K2 | D4D12 | S1 | Z1 | Multiplexer Overhead Z2 | M1 | E2 J1 | C2 | G1 | F2 | H4 | F3 | Path Overhead K3 | N1 Selects the overhead byte into which the overhead sequence is to be inserted when :SOURce:DATA:TELecom:SDH:TFUNction:TYPE <discrete>...
  • Page 133 SDH Command Reference SOURce subsystem - Transmitter SDH Test Function Commands :SOURce:DATA:TELecom:SDH:SEQuence:DATA <discrete>,<string> <discrete> = A | B | C | D | E <string> = "00" to "FFFFFFFFFFFFFFFFFF" Sets the Sequence data pattern for the designated block to the hexadecimal value contained in the string.
  • Page 134 SDH Command Reference SOURce subsystem - Transmitter SDH Test Function Commands The corresponding query returns the frame_count in numeric form. :SOURce:DATA:TELecom:SDH:SEQuence:FCOunt? <numeric> Returns : <numeric> Frame count :SOURce:DATA:TELecom:SDH:STESt:SPATtern <discrete> <discrete> = AZERos All Zero’s pattern AONes All Ones pattern G958 G.958 sequence Selects the pattern used in the Optical stress test when :SOURce:DATA:TELecom:SDH:TFUNction:TYPE <discrete>...
  • Page 135 SDH Command Reference SOURce subsystem - Transmitter SDH Test Function Commands :SOURce:DATA:TELecom:SDH:MSPMessages:TOPology <discrete> <discrete> = LINear Linear protection RING Ring protection Selects the type of protection topology. The corresponding query returns the selected protection topology in discrete short form. :SOURce:DATA:TELecom:SDH:MSPMessages:TOPology? Returns: <discrete>...
  • Page 136 SDH Command Reference SOURce subsystem - Transmitter SDH Test Function Commands FSWitch Forced Switch (1110) LOPRotection Lockout Of Protection (1111) Selects the transmitter SDH MSP message to be transmitted (K1 Byte, Bits 1 to 4). Only valid if :SOURce:DATA:TELecom:TFUNction <discrete> is set to SDH and :SOURce:DATA:TELecom:SDH:TFUNction:TYPE <discrete>...
  • Page 137 SDH Command Reference SOURce subsystem - Transmitter SDH Test Function Commands Working Channel 13 Working Channel 14 Extra Traffic Channel Selects the transmitter SDH MSP message channel (K1 Byte, Bits 5 to 8). Only valid if :SOURce:DATA:TELecom:TFUNction <discrete> is set to SDH and :SOURce:DATA:TELecom:SDH:TFUNction:TYPE <discrete>...
  • Page 138 SDH Command Reference SOURce subsystem - Transmitter SDH Test Function Commands Selects the SDH transmitter Linear MSP architecture (K2 Byte, Bit 5). Only valid if :SOURce:DATA:TELecom:TFUNction <discrete> is set to SDH and :SOURce:DATA:TELecom:SDH:TFUNction:TYPE <discrete> is set to MSPM and :SOURce:DATA:TELecom:SDH:MSPMessages:TOPology <discrete> is set to LIN.
  • Page 139 SDH Command Reference SOURce subsystem - Transmitter SDH Test Function Commands ERINg Exerciser - Ring (0011) ESPan Exerciser - Span (0100) WTRestore Wait to Restore (0101) MSRing Manual Switch - Ring (0110) MSSPan Manual Switch - Span (0111) SDRing Signal Degrade - Ring (1000) SDSPan Signal Degrade - Span (1001) SDPRotection...
  • Page 140 SDH Command Reference SOURce subsystem - Transmitter SDH Test Function Commands :SOURce:DATA:TELecom:SDH:MSPMessages:DNODe? Returns: <string> :SOURce:DATA:TELecom:SDH:MSPMessages:SNODe <string> <string> = "0000" to "1111" Selects the SDH transmitter Ring MSP message source node (K2 Byte, Bits 1 to 4) . Only valid if :SOURce:DATA:TELecom:TFUNction <discrete> is set to SDH and :SOURce:DATA:TELecom:SDH:TFUNction:TYPE <discrete>...
  • Page 141 SDH Command Reference SOURce subsystem - Transmitter SDH Test Function Commands P011 P100 P101 Selects the SDH transmitter Ring MSP messages status code (K2 Byte, Bits 6 to 8). Only valid if :SOURce:DATA:TELecom:TFUNction <discrete> is set to SDH and :SOURce:DATA:TELecom:SDH:TFUNction:TYPE <discrete> is set to MSPM and :SOURce:DATA:TELecom:SDH:MSPMessages:TOPology <discrete>...
  • Page 142 SDH Command Reference SOURce subsystem - Transmitter SDH Test Function Commands D8|D9|D10|D11|D12|X22|X Multiplexer Overhead 23|X32|X33 S1/Z1|Z1|M1/Z2|E2| Multiplexer Overhead J1|C2|G1|F2|H4|Z3/F3| Path Overhead Z4/K3|Z5/N1 Selects the TX overhead byte used for the overhead BER test when :SOURce:DATA:TELecom:SDH:TFUNction:TYPE <discrete> is set to OBER. The corresponding query returns the overhead byte identity in discrete form as listed above.

  • Page 143: Input Subsystem

    SDH Command Reference INPut subsystem INPut subsystem This subsystem controls the characteristics of the instrument’s input ports. :INPut:TELecom:OPT1:RATE <discrete> <discrete> = STM0 STM-0 optical STM1 STM-1 Optical Selects the input rate for the STM-0/STM-1 optical input port. Is only valid when Option STM-0/STM-1 Optical Interface is fitted and :SENSe:DATA:TELecom:SENSe <discrete>...
  • Page 144 SDH Command Reference INPut subsystem STM4 STM-4 Optical Selects the input rate for the STM-0/STM-1/STM-4 optical input port. Is only valid when Option STM-0/STM-1/STM-4 Optical Interface is fitted and :SENSe:DATA:TELecom:SENSe <discrete> is set to OPT4. The corresponding query returns the STM-0/STM-1/STM-4 input rate in discrete form as listed above.
  • Page 145 SDH Command Reference INPut subsystem :INPut:TELecom:OPT16:RATE? Returns : <discrete> :INPut:TELecom:OPT16:INTerface <discrete> <discrete> = OPTical Optical input MONitor Protected Monitor Input Selects the input interface on the Optical modules. The corresponding query returns the input interface in discrete form, as listed above. :INPut:TELecom:OPT16:INTerface? Returns: <discrete>...

  • Page 146: Sense Subsystem - Receiver Sdh Settings

    SDH Command Reference SENSe subsystem - Receiver SDH Settings SENSe subsystem - Receiver SDH Settings SDH Mapping settings :SENSe:DATA:TELecom:SDH:AU4 <numeric> <numeric> = <numeric> 1 to 16 AU-4 under test Selects the AU-4 within an STM-N for test. Only valid if :INPut:TELecom:OPT1:RATE <discrete>...

  • Page 147: Tandem Connection Monitoring (Tcm) - Sdh Only3

    SDH Command Reference SENSe subsystem - Receiver SDH Settings Selects the AU-3 within an AUG for test. Only valid if the selected mapping is AU-3. The corresponding query returns the test AU-3 number. :SENSe:DATA:TELecom:SDH:AU3? Returns : <numeric> :SENSe:DATA:TELecom:SDH:AU4C <numeric> <numeric> = <numeric>...

  • Page 148: Au Layer Selection

    SDH Command Reference SENSe subsystem - Receiver SDH Settings AU Layer Selection :SENSe:DATA:TELecom:SDH:AU:TYPE <discrete> <discrete> = AU4_4c AU4_16c Set the AU mapping into an STM-N frame. The corresponding query returns the AU type in discrete form as listed above. :SENSe:DATA:TELecom:SDH:AU:TYPE? Returns: <discrete>...

  • Page 149: Payload Layer Selection

    SDH Command Reference SENSe subsystem - Receiver SDH Settings Payload Layer Selection :SENSe:DATA:TELecom:SDH:MAPPing <discrete> <discrete> = BULK Bulk Filled (C-4 or C-3) Selects the Receiver SDH payload for single payload cases. Only valid if :SENSe:DATA:TELecom:SDH:PAYLoad <discrete> is set to VC3, VC4, VC4-4c or VC4-16c.

  • Page 150: Tug Channel

    SDH Command Reference SENSe subsystem - Receiver SDH Settings TUG Channel :SENSe:DATA:TELecom:SDH:TUG3 <numeric> <numeric> = 1 to 3 Selects the SDH Receiver active TUG3 within the AU4. The corresponding query returns the active TUG-3 number in numeric form. :SENSe:DATA:TELecom:SDH:TUG3? Returns : <numeric>...

  • Page 151: Tu Payload And Test Pattern

    SDH Command Reference SENSe subsystem - Receiver SDH Settings TU Payload and Test Pattern :SENSe:DATA:TELecom:SDH:PAYLoad:TYPE <discrete> <discrete> = UNFRamed No framing The corresponding query returns the framing in discrete form as listed above. :SENSe:DATA:TELecom:SDH:PAYLoad:TYPE? Returns : <discrete> :SENSe:DATA:TELecom:SDH:PAYLoad:STRucture <discrete> <discrete> = UNSTructured All rates Determines whether the receiver is to expect any structure in the PDH payload.
  • Page 152 SDH Command Reference SENSe subsystem - Receiver SDH Settings UWORd 16 Bit User Word LIVE Live Traffic Selects the receiver SDH payload data pattern. If UWORd is selected, the word pattern is set using :SENSe:DATA:TELecom:SDH:PAYLoad:UWORd <string>. The corresponding query returns the receiver SDH payload data pattern in discrete form as listed above.
  • Page 153 SDH Command Reference SENSe subsystem - Receiver SDH Settings :SENSe:DATA:TELecom:SDH:TRIButary:CONCatenate <numeric>,<numeric> <numeric> = Concatenation Off TU2-2c TU2-3c TU2-4c TU2-5c TU2-6c <numeric> = 1 to 6 TU2-2c selected 1 to 5 TU2-3c selected 1 to 4 TU2-4c selected 1 to 3 TU2-5c selected 1 to 2 TU2-6c selected...

  • Page 154: Sense Subsystem - Receiver Sdh Test Function Commands3

    SDH Command Reference SENSe subsystem - Receiver SDH Test Function Commands SENSe subsystem - Receiver SDH Test Function Commands Lists the commands associated with the RECEIVE TEST FUNCTION display. :SENSe:DATA:TELecom:SDH:TFUNction:TYPE <discrete> <discrete> = NONE OCAPture Overhead Capture DDCC DCC Drop PGRaph Pointer Graph OBERtest...
  • Page 155 SDH Command Reference SENSe subsystem - Receiver SDH Test Function Commands :SENSe:DATA:TELecom:SDH:OCAPture:CHANnel <discrete> <discrete> = A1A2 |C1/J0 | Z0 | E1 | F1 | RS Overhead D1D3 H1H2 | K1K2 | D4D12 | S1 | MS Overhead Z1_1|Z1_2 | Z1_3 | Z2_4 | Z2_5 | M1 | Z2_5 | Z2_6 | E2 J1 | C2 | G1 | F2 | H4 | Z3/F3 | Path Overhead...
  • Page 156 SDH Command Reference SENSe subsystem - Receiver SDH Test Function Commands :SENSe:DATA:TELecom:SDH:OCAPture:OHBYte? Returns: <discrete> :SENSe:DATA:TELecom:SDH:OCAPture:COLumn <numeric> <numeric> = 1 to 9 Selects the Section overhead column from which to capture. This only applies to Z1 and Z2. The corresponding query returns the column to be captured in numeric form. :SENSe:DATA:TELecom:SDH:OCAPture:COLumn? <numeric>= 1 to 9...
  • Page 157 SDH Command Reference SENSe subsystem - Receiver SDH Test Function Commands :SENSe:DATA:TELecom:SDH:OCAPture:TRIGger? Returns : <discrete> :SENSe:DATA:TELecom:SDH:OCAPture:TRIGger:PATTern <string> Sets the Overhead Capture Trigger Pattern to the hexadecimal value contained in the string. The number of hexadecimal characters in the string is dependent on the overhead byte or bytes selected.
  • Page 158 SDH Command Reference SENSe subsystem - Receiver SDH Test Function Commands TU12 TU11 AU4_4c AU4_16c Selects the type of pointer to be captured for pointer graph. The corresponding query returns the type of pointer, in discrete short form. :SENSe:DATA:TELecom:SDH:PGRaph:PTYPe? Returns: <discrete>...
  • Page 159 SDH Command Reference SENSe subsystem - Receiver SDH Test Function Commands K1 | K2 | D4 | D5 | D6 | D7 | D8 | MS Overhead D9 | D10 | D11 | D12 | S1/Z1 | M1/Z1 | E2 | J1 | C2 | G1 | F2 | H4 | Z3/F3 | Path Overhead Z4/K3 | Z5/N1...

  • Page 160: Sense Subsystem - Alarm Scan Control

    SDH Command Reference SENSe subsystem - Alarm Scan Control SENSe subsystem - Alarm Scan Control :SENSe:DATA:TELecom:SDH:ASCan:MODE <discrete> <discrete> = AUTomatic Automatic receiver configuration RSETtings Fixed receiver configuration Selects the SDH alarm scan mode. The corresponding query returns the alarm scan mode in discrete short form. :SENSe:DATA:TELecom:SDH:ASCan:MODE? Returns: <discrete>...
  • Page 161 SDH Command Reference SENSe subsystem - Alarm Scan Control :SENSe:DATA:TELecom:SDH:ASCan? Returns: <boolean> 3-78 Artisan Technology Group - Quality Instrumentation ... Guaranteed | (888) 88-SOURCE | www.artisantg.com...

  • Page 162: Sense Subsystem - Sdh Tributary Scan Control

    SDH Command Reference SENSe subsystem - SDH Tributary Scan Control SENSe subsystem - SDH Tributary Scan Control :SENSe:DATA:TELecom:SDH:TSCan:PERiod <numeric>, <suffix> <numeric> = 1 to 99 <suffix> = Days Hours Minutes Seconds Sets the test duration for each tributary. The corresponding query returns the test duration for each tributary. :SENSe:DATA:TELecom:SDH:TSCan:PERiod? Returns: <numeric>,<suffix>...

  • Page 163: Sense Subsystem - Ms-Rei Measurements Enable/Disable3

    SDH Command Reference SENSe subsystem - MS-REI Measurements Enable/Disable The corresponding query returns the alarm scan state as 0 or 1. :SENSe:DATA:TELecom:SDH:TSCan? Returns: <boolean> SENSe subsystem - MS-REI Measurements Enable/Disable :SENSe:DATA:TELecom:SDH:MSRei <boolean> <boolean> = 0 or OFF MS REI measurements off 1 or ON MS REI measurments on Allows measurement of MS-REI to be suppressed.

  • Page 164: Sense Subsystem - Result Returning Commands

    SDH Command Reference SENSe subsystem - Result Returning Commands SENSe subsystem - Result Returning Commands Frequency Results (SDH) :SENSe:DATA? <"result"> Result = "FREQuency:SDH:GATE1S" RX SDH clock frequency (1s gate) "FREQuency:SDH[:GATE16S]" RX SDH clock frequency (16s gate) "FOFPpm:SDH[:GATE16S]" RX SDH clock offset in ppm (16s gate) "FOFHz:SDH[:GATE16S]"...

  • Page 165: Tcm Short Term Results

    SDH Command Reference SENSe subsystem - Result Returning Commands "ERATio:SDH:STERm:FEBE" or FEBE/REI error ratio "ERATio:SDH:STERmREI" "ECOunt:SDH:STERm:PIEC" PIEC error count "ERATio:SDH:STERm:PIEC" PIEC error ratio "ECOunt:SDH:STERm:TRIB:PBIP" TU path BIP error count "ERATio:SDH:STERm:TRIB:PBIP" TU path BIP error ratio "ECOunt:SDH:STERm:TRIB:FEBE" TU FEBE/LP REI error count or "ECOunt:SDH:STERm:TRIB:REI"...

  • Page 166: Tcm Cumulative Results

    SDH Command Reference SENSe subsystem - Result Returning Commands "ERATio:SDH:RSBip" RS B1 BIP error ratio "ECOunt:SDH:MSBip" MS B2 BIP error count "ERATio:SDH:MSBip" MS B2 BIP error ratio "ECOunt:SDH:MFEBe" or MS FEBE/MS REI error count. See page 4-80. "ECOunt:SDH:"MSRei" "ERATio:SDH:MFEBe" or MS FEBE/MS REI error ratio.

  • Page 167: Sdh Rs B1 Bip Analysis Results

    SDH Command Reference SENSe subsystem - Result Returning Commands "ECOunt:SDH:TCM:OEI" TCM OEI error count "ERATio:SDH:TCM:OEI" TCM OEI error ratio "ECOunt:SDH:TCM:ERR" TCM Error error count "ERATio:SDH:TCM:ERR" TCM Error error ratio SDH RS B1 BIP Analysis Results :SENSe:DATA? <"result"> Result= "ESEConds:SDH:RSBip:ANALysis" Error Seconds "SESeconds:SDH:RSBip:ANALysis"...

  • Page 168: Sdh Path Ms Febe Analysis Results

    SDH Command Reference SENSe subsystem - Result Returning Commands "UASeconds:SDH:MSBip:ANALysis" Unavailable seconds "PUASeconds:SDH:MSBip:ANALysis" Path Unavailable seconds SDH Path MS FEBE Analysis Results :SENSe:DATA? <"result"> If you wish to disable the MSRei measurement, see page 4-80. Result= "ESEConds:SDH:MFEBe:ANALysis" or Error Seconds "ESEConds:SDH:MSRei:ANALysis"...

  • Page 169: Sdh Path Febe Analysis Results

    SDH Command Reference SENSe subsystem - Result Returning Commands Result= "ESEConds:SDH:PBIP:ANALysis" Error Seconds "SESeconds:SDH:PBIP:ANALysis" Severely Errored Seconds "EBCount:SDH:PBIP:ANALysis" Errored block count "BBECount:SDH:PBIP:ANALysis" Background block error count "ESRatio:SDH:PBIP:ANALysis" Error Second Ratio "SESRatio:SDH:PBIP:ANALysis" Severely Errored Second Ratio "BBERatio:SDH:PBIP:ANALysis" Background Block Error ratio "UASeconds:SDH:PBIP:ANALysis"...

  • Page 170: Sdh Path Iec Analysis Results

    SDH Command Reference SENSe subsystem - Result Returning Commands SDH Path IEC Analysis Results :SENSe:DATA? <"result"> Result= "ESEConds:SDH:PIEC:ANALysis" Error Seconds "SESeconds:SDH:PIEC:ANALysis" Severely Errored Seconds "EBCount:SDH:PIEC:ANALysis" Errored block count "BBECount:SDH:PIEC:ANALysis" Background block error count "ESRatio:SDH:PIEC:ANALysis" Error Second Ratio "SESRatio:SDH:PIEC:ANALysis" Severely Errored Second Ratio "BBERatio:SDH:PIEC:ANALysis"...

  • Page 171: Sdh Tributary Path Febe Analysis Results

    SDH Command Reference SENSe subsystem - Result Returning Commands SDH Tributary Path FEBE Analysis Results :SENSe:DATA? <"result"> Result = "ESEConds:SDH:TRIB:FEBE:ANALysis" or Error Seconds "ESEConds:SDH:TRIB:REI:ANALysis" "SESeconds:SDH:TRIB:FEBE:ANALysis" or Severely Errored Seconds "SESeconds:SDH:TRIB:REI:ANALysis" "EBCount:SDH:TRIB:FEBE:ANALysis" or Errored block count "EBCount:SDH:TRIB:REI:ANALysis" "BBECount:SDH:TRIB:FEBE:ANALysis" or Background block error count "BBECount:SDH:TRIB:REI:ANALysis"...

  • Page 172: Tcm Path Iec Analysis Results

    SDH Command Reference SENSe subsystem - Result Returning Commands "SESRatio:SDH:BLKBit:ANALysis" Severely Errored Second Ratio "BBERatio:SDH:BLKBit:ANALysis" Background Block Error ratio "UASeconds:SDH:BLKBit:ANALysis" Unavailable seconds TCM Path IEC Analysis Results :SENSe:DATA? <"result"> Result= "ESEConds:SDH:TCM:PIEC:ANALysis" Error Seconds "SESeconds:SDH:TCM:PIEC:ANALysis" Severely Errored Seconds "EBCount:SDH:TCM:PIEC:ANALysis" Errored block count "BBECount:SDH:TCM:PIEC:ANALysis"...

  • Page 173: Tcm Oei Analysis Results

    SDH Command Reference SENSe subsystem - Result Returning Commands TCM OEI Analysis Results :SENSe:DATA? <"result"> Result= "ESEConds:SDH:TCM:OEI:ANALysis" Error Seconds "SESeconds:SDH:TCM:OEI:ANALysis" Severely Errored Seconds "EBCount:SDH:TCM:OEI:ANALysis" Errored block count "BBECount:SDH:TCM:OEI:ANALysis" Background block error count "ESRatio:SDH:TCM:OEI:ANALysis" Error Second Ratio "SESRatio:SDH:TCM:OEI:ANALysis" Severely Errored Second Ratio "BBERatio:SDH:TCM:OEI:ANALysis"...

  • Page 174: Sdh M.2101 Analysis Results

    SDH Command Reference SENSe subsystem - Result Returning Commands SDH M.2101 Analysis Results :SENSe:DATA? <“result”> Result = “ESEConds:SDH:LOW:RECeive:ANALysis: Low Order Path Receive Direction Errored Seconds M2101” “SESeconds:SDH:LOW:RECeive:ANALysis: Low Order Path Receive Direction Severely Errored Seconds M2101” “UASeconds:SDH:LOW:RECeive:ANALysis: Low Order Path Receive Direction Unavailable Seconds M2101”...

  • Page 175: Sdh Service Disruption Results

    SDH Command Reference SENSe subsystem - Result Returning Commands “UASeconds:SDH:SECTion:RECeive:ANAL Section Layer Path Receive Direction Unavailable Seconds ysis:M2101” “ESEConds:SDH:SECTion:TRANsmit:ANAL Section Layer Path Transmit Direction Errored Seconds ysis:M2101” “SESeconds:SDH:SECTion:TRANsmit:ANA Section Layer Path Transmit Direction Severely Errored Seconds Lysis:M2101” “UASeconds:SDH:SECTion:TRANsmit:ANA Section Layer Path Transmit Direction Unavailable Seconds Lysis:M2101”...

  • Page 176: Sdh Pointer Activity Results

    SDH Command Reference SENSe subsystem - Result Returning Commands SDH Pointer Activity Results :SENSe:DATA? <"result"> Result= "PACTivity:SDH:PVALue" AU Pointer value "PACTivity:SDH:NDFSeconds" AU Pointer NDF seconds "PACTivity:SDH:MNDFseconds" AU Pointer MNDF seconds "PACTivity:SDH:PCOunt" AU Pointer +ve Adj Count "PACTivity:SDH:PSEConds" AU Pointer +ve Adj Seconds "PACTivity:SDH:NCOunt"...

  • Page 177: Tcm Alarm Seconds Results

    SDH Command Reference SENSe subsystem - Result Returning Commands "ASEConds:SDH:MSAis" Multiplexer Section AIS "ASEConds:SDH:PAIS" Path AIS "ASEConds:SDH:PSLoss" Pattern Synchronization Loss "ASEConds:SDH:MSRDi" Multiplexer Section Remote Defect "ASEConds:SDH:PFERf" or STM Path FERF/HP-RDI "ASEConds:SDH:RDI" "ASEConds:SDH:K1K2" K1K2 byte change "ASEConds:SDH:TRIB:LOP" TU Loss Of Pointer "ASEConds:SDH:TRIB:PAIS"...

  • Page 178: Fetch Subsystem

    SDH Command Reference FETCh subsystem FETCh subsystem The FETCh subsystem is used to retrieve data directly accumulated by the instrument. :FETCh:STRing:DATA:TELecom:SDH:TCM:APID? Returns: <string> Returns the Tandem Connection Monitoring (TCM) Access Point Identifier as a 16 ASCII character string if CRC7 is not detected, 15 ASCII character string if CRC7 is detected.
  • Page 179 SDH Command Reference FETCh subsystem returned as a string. If the string contains any non printing characters then ~ is substituted. This is a snapshot of the overhead byte and is captured once per second. :FETCh:STRing:DATA:TELecom:SDH:J1:HEXadecimal? Returns : <block> If interfacing at STM-1/4/16, returns the value of the VC-3, VC-4, VC-4-NC J1 path trace byte as 64 hexadecimal numbers (15 if CRC7 is detected).
  • Page 180 SDH Command Reference FETCh subsystem returned. If the string contains any non-printing characters then ~ is substituted. This is a snapshot of the received path trace and is only updated once per second. :FETCh:STRing:DATA:TELecom:SDH:TRIButary:J2:HEXadecimal? Returns: <block> Returns the value of the J2 path trace byte as 15 or 16 hexadecimal numbers. The OmniBER 718 attempts to align the received pattern by detecting the CRC7 byte.
  • Page 181 SDH Command Reference FETCh subsystem <discrete> = A1|A2|C1/J0/ Byte Name Z0|B1|E1|F1|D1|D2|D3|H1|H2 H3|B2|K1|K2||D11 D12|Z1/S1|Z2/ M1|E2|X13|X21|X22|X23|X31 X32|X33|X52|X53|X61|X62|X63 X71|X72|X73|X81|X82|X83|X93 Returns the selected overhead byte as an 8 bit binary string in the range "00000000" to "11111111". The byte number is given by its defined name if it has one. Undefined bytes are represented by <Xrc>, where r is the numerical value of the bytes row in the transport overhead and c is the numerical value of the bytes column in the transport overhead.
  • Page 182 SDH Command Reference FETCh subsystem :FETCh:SCALar:DATA:TELecom:SDH:POVerhead? <discrete> <discrete> = J1|B3|C2|G1|F2|H4|Z3/F3|Z4/ K3|Z5/N1 Obtains the value of the named path overhead byte. The value of the named byte is returned as a string in the range "00000000" to "11111111". This is a snapshot of the overhead byte and is captured once per second.
  • Page 183 SDH Command Reference FETCh subsystem one for each path scanned. The value of the numeric indicates the status of the scanned path. The following values are valid. Value State No Problems Detected Alarms or Errors Detected Path Unequipped Loss of Pointer H4 Multiframe Loss Invalid For a specific signal structure, the format of the returned strings are shown below:...
  • Page 184 SDH Command Reference FETCh subsystem b) STM-1 AU-4 TU-3 This signal consists of 1 AU-4 containing 3 TUG-3’s each of which contains 1 TU- 3. In this configuration there are 4 paths, 1 at the AU-4 level and 3 at the TU-3 level. Again, the single AU path is defined as a group on its own.
  • Page 185 SDH Command Reference FETCh subsystem 0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 1,1,1,0,0,1,0,0,0,0,0,0,0,0,0,1,1,0,0,0,0 2,2,2,2,2,2,2,2,2,2,2,2,2,2,2,2,2,2,2,2,2 d) STM-1 AU-4 TU-11 This signal again consists of 1 AU-4 containing 3 TUG-3’s. In this case however, the TUG-3’s each contain 7 TUG-2’s. These TUG-2’s each contain 4 TU-11’s. In terms of paths the signal comprises 1 path at the AU-4 level and 84 paths at the TU- 11 level.
  • Page 186 SDH Command Reference FETCh subsystem -> AU3#1, AU3#2, AU3#3 AU-3 #1 -> TU#1,TU#2,TU#3,TU#4,TU#5,TU#6,TU#7 AU-3 #2 -> TU#1,TU#2,TU#3,TU#4,TU#5,TU#6,TU#7 AU-3 #3 -> TU#1,TU#2,TU#3,TU#4,TU#5,TU#6,TU#7 For Example, the output could look like: 0,1,1 1,1,1,0,0,1,0 2,2,2,2,2,2,2 0,0,0,0,1,0,0 f) STM-1 AU-3 VC-3 This signal consists of 3 AU-3s each containing 1 VC-3. In this configuration there are 3 paths, 3 at the AU-3 level and no lower paths.
  • Page 187 SDH Command Reference FETCh subsystem AU-3 #3 -> As Above The output will look like: 1,2,0 0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 1,1,1,0,0,1,0,0,0,0,0,0,0,0,0,1,1,0,0,0,0 2,2,2,2,2,2,2,2,2,2,2,2,2,2,2,2,2,2,2,2,2 h) STM-1 AU-3 TU-11 This signal again consists of 3 AU-3s. In this case however, the AU-3’s each contain 7 TUG-2’s. These TUG-2’s each contain 4 TU-11’s. In terms of paths the signal comprises 3 paths at the AU-3 level and 84 paths at the TU-11 level.
  • Page 188 SDH Command Reference FETCh subsystem defined as one group. For this configuration, 2 groups are returned with the following format: AU-3 Group -> AU-3 AU-3#1 -> TU-2#1,TU-2#2,TU-2#3,TU-2#4,TU-2#5,TU-2#6,TU-2#7 The output will look like: 1,1,1,0,0,0,0 j) STM-0 AU-3 TU-12 This signal again comprises 1 AU-3 containing 7 TUG-2’s. However, this time the TUG-2’s each contain 3 TU-12’s.
  • Page 189 SDH Command Reference FETCh subsystem 1],[7-2],[7-3],[7-4] The output will look like: 1,1,1,1,0,0,0,0,0,1,1,1,1,1,1,1,1,1,0,0,0,2,0,0,0,0,0,1 l) Unrecognized Structure When Alarm Scan is operating in AUTO mode, it is possible that due to various signal alarm conditions, it may not be able to determine the structure for a particular group of paths.
  • Page 190 SDH Command Reference FETCh subsystem TUG-3 #1 -> TU#1,TU#2,TU#3,TU#4,TU#5,TU#6,TU#7 TUG-3 #2 -> TU#1,TU#2,TU#3,TU#4,TU#5,TU#6,TU#7 TUG-3 #3 -> TU#1,TU#2,TU#3,TU#4,TU#5,TU#6,TU#7 For Example, the output could look like: 1,1,1,0,0,1,0 1,1,1,0,0,1,1 0,0,0,0,1,0,0 b) STM-1 AU-4 TU-3 This signal consists of 1 AU-4 containing 3 TUG-3’s each of which contains 1 TU- 3.
  • Page 191 SDH Command Reference FETCh subsystem 0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 1,1,1,0,0,1,0,0,0,0,0,0,0,0,0,1,1,0,0,0,0 1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1 d) STM-1 AU-4 TU-11 This signal again consists of 1 AU-4 containing 3 TUG-3’s. In this case however, the TUG-3’s each contain 7 TUG-2’s. These TUG-2’s each contain 4 TU-11’s. There are therefore 84 (3*7*4) tributaries which must be scanned. The 84 TU-11 paths are arranged in 3 groups corresponding to their allocation with the 3 TUG-3’s.
  • Page 192 SDH Command Reference FETCh subsystem NOTE: TU-12’s designated thus [TUG-2# - TU-12#] TUG-2 -> [1-1],[1-2],[1-3],[2-1],[2-2],[2-3],[3-1], [3-2],[3-3],[4-1],[4-2],[4-3],[5-1],[5-2], [5-3],[6-1],[6-2],[6-3],[7-1],[7-2],[7-3] The output will look like: 1,1,1,0,0,0,0,1,1,1,1,1,1,1,0,0,1,0,0,0,0 g) STM-0 AU-3 TU-11 This signal again comprises 1 AU-3 containing 7 TUG-2’s. However, this time the TUG-2’s each contain 4 TU-11’s.
  • Page 193 SDH Command Reference FETCh subsystem :FETCh:ARRay:DATA:TELecom:SDH:PGRaph? Returns: <array> Returns an array of 576 bytes, 2 bytes for each of the possible 288 points on the displayed pointer graph. The 2 bytes at each point indicate the maximum and minimum offset at that point. Each byte has 3 numeric entries separated by commas. The value of the 3 numeric entries, <range bit>,<validity bit>,<offset value>, provide the following information: Range bit...
  • Page 194 SDH Command Reference FETCh subsystem :FETCh:ARRay:DATA:TELecom:SDH:OCAPture? <numeric> <numeric = 1 to 16 Overhead channels Returns: <array> Returns an array with the number of entries determined by <numeric> and separated by CR/LF. Each entry consists of an alphanumeric string and a numeric separated by commas. The alphanumeric string provide the hexadecimal value of the captured data.
  • Page 195 SDH Command Reference FETCh subsystem :FETCh:ARRay:DATA:TELecom:SDH:OVERhead? <numeric>,<numeric> < > numeric <numeric> = 1 to 27 (Byte) <numeric> = 1 to 16 (STM-1 Number) <numeric> = (Columns 1,4,7) (Columns 2,5,8) (Columns 3,6,9) Returns the value of the selected transport overhead bytes as an array of strings. Each string is in the range "00000000"...

  • Page 196: Sonet Command Reference

    SONET SCPI Command Reference OUTPut subsystem, see page 4-3 SOURce subsystem - Transmitter SONET Settings Commands, see page 4-8 SONET Mapping Settings, see page 4-12 SOURce subsystem - Transmitter SONET OVERHEAD SETUP, see page 4-21 SOURce subsystem - Transmitter SONET Test Function Commands, see page 4-31 INPut subsystem, see page 4-57 SENSe subsystem - Receiver SONET Settings, see page 4-60 SENSe subsystem - Receiver SONET Test Function Commands, see page 4-67...
  • Page 197 This chapter contains detailed information on the SCPI (Standard Commands for Programming Instruments) and IEEE 488.2 common commands you will use when writing programs to control your OmniBER 720 for SONET operation. Please also refer to chapter 2 Common Commands for general information on SCPI command formats and for a list of commands that are common to SONET operation;...

  • Page 198: Output Subsystem

    OUTPut subsystem OUTPut subsystem This subsystem controls the characteristics of the instrument’s output ports. :OUTPut:TELecom:OC3:RATE <discrete> <discrete> = OC-1 optical OC-3 Optical Selects the output rate for the OC-1/OC-3 optical output port. This command is only valid when :SOURce:DATA:TELecom:SOURce <discrete> is set to OC3. The corresponding query returns the OC-1/OC-3 output rate in discrete form as listed above.
  • Page 199 OUTPut subsystem :OUTPut:TELecom:OC3:LASer <boolean> <boolean> = 0 or OFF 1 or ON Controls the state of the laser (ON or OFF) on the Optical module. The corresponding query returns the state of the laser as 0 or 1. :OUTPut:TELecom:OC3:LASer? Returns : <boolean>...
  • Page 200 OUTPut subsystem :OUTPut:TELecom:OC12:WAVelength <discrete> <discrete> = NM1310 1310 nm NM1550 1550 nm Selects the wavelength of the output optical signal on the Optical module. The corresponding query returns the output optical wavelength in discrete form, as listed above. :OUTPut:TELecom:OC12:WAVelength? Returns : <discrete>...
  • Page 201 OUTPut subsystem OC48 OC-48 Optical Selects the output rate for the OC-1/OC-3/OC-12/OC-48 optical output port. This command is only valid when :SOURce:DATA:TELecom:SOURce <discrete> is set to OC48. The corresponding query returns the OC-1/OC-3/OC-12/OC-48 output rate in discrete form as listed above. If the OC-48 port is not selected, OC-48 will be returned as the default.
  • Page 202 OUTPut subsystem :OUTPut:TELecom:OC48:LASer? Returns : <boolean> 0 or 1 Artisan Technology Group - Quality Instrumentation ... Guaranteed | (888) 88-SOURCE | www.artisantg.com...

  • Page 203: Source Subsystem - Transmitter Sonet Settings Commands

    SOURce subsystem - Transmitter SONET Settings Commands SOURce subsystem - Transmitter SONET Settings Commands SONET Clock settings :SOURce:CLOCk:SONet:SOURce <discrete> <discrete> = INTernal Internal EXTernal External Clock/Data ROC1 OC-1 Optical RMN1 STS-1 Monitor ROC3 OC-3 Optical RMN3 STS-3 Monitor ROC12 OC-12 Optical RMN12 STS-12 Monitor ROC48...
  • Page 204 SOURce subsystem - Transmitter SONET Settings Commands 64kb/s data DS1Bits DS1 bit rate M10Ref 10 MHz Reference Selects the transmitter SONET EXT clock sync source format. The corresponding query returns the EXT clock sync source format in discrete form as listed above. :SOURce:CLOCk:SONet:FORMat? Returns : <discrete>...

  • Page 205: Thru Mode Settings

    SOURce subsystem - Transmitter SONET Settings Commands :SOURce:CLOCk:SONet:FOFFset:OFFSet? Returns : <numeric> Thru mode settings :SOURce:DATA:TELecom:SONet:THRumode <discrete> <discrete> = INTernal Select Normal SONET Mode THRU Select SONET Thru Mode Selects/Deselects SONET THRU mode. The corresponding query returns the THRU mode state in discrete form as listed above.
  • Page 206 SOURce subsystem - Transmitter SONET Settings Commands :SOURce:DATA:TELecom:SONet:THRumode:PAYLoad:OVERwrite? Returns : <discrete> :SOURce:DATA:TELecom:SONet:THRumode:PAYLoad:OVERwrite:ENABl e <boolean> <boolean> = 0 or OFF 1 or ON Enable the thru-mode payload overwrite. The corresponding query returns the payload overwrite enable state in discrete form as listed above. :SOURce:DATA:TELecom:SONet:THRumode:PAYLoad:OVERwrite:ENABl Returns : <boolean>...

  • Page 207: Sonet Mapping Settings

    SOURce subsystem - Transmitter SONET Settings Commands SONET Mapping Settings :SOURce:DATA:TELecom:SONet:STS3 <numeric> <numeric> = 1 to 16 STS3 number under test. Only valid if :OUTPut:TELecom:OC48:RATE <discrete>, is set to a rate higher than STS-3. Selects the transmitted STS-3 that is selected for test. The corresponding query returns the STS-3 selected for test in numeric form, as listed above.

  • Page 208: Spe Layer Selection

    SOURce subsystem - Transmitter SONET Settings Commands :SOURce:DATA:TELecom:SONet:STS12c <numeric> <numeric> = 1 to 4 STS12 number under test. :SOURce:DATA:TELecom:SONet:STS12c? Returns : <numeric> SPE Layer Selection :SOURce:DATA:TELecom:SONet:SPE:TYPE <discrete> < discrete> = STS3c STS1 STS12c STS48c Set the SPE mapping into an STS-N frame. The corresponding query returns the SPE layer in discrete form as listed above.

  • Page 209: Vt Layer Selection

    SOURce subsystem - Transmitter SONET Settings Commands VT Layer Selection :SOURce:DATA:TELecom:SONet:PAYLoad <discrete> <discrete> = STS3c STS-3c STS1 STS-1 VT2 or M2 2 Mb/s VT-6 STS12c STS-12c STS48c STS-48c VT15 or DS1 VT-1.5 This command selects the SONET transmitter mapping. The corresponding query returns the SONET mapping in discrete form, as listed above.

  • Page 210: Vt Group

    SOURce subsystem - Transmitter SONET Settings Commands :SOURce:DATA:TELecom:SONet:TRIButary:MAPPing <discrete> <discrete> = BULK Bulk Filled Selects the transmitter low order mapping. Only valid if :SOURce:DATA:TELecom:SONet:PAYLoad <discrete> is set to VT2 or VT15. The corresponding query returns the low order mapping in discrete short form. :SOURce:DATA:TELecom:SONet:TRIButary:MAPPing? Returns: <discrete>...

  • Page 211: Vt Payload And Test Pattern

    SOURce subsystem - Transmitter SONET Settings Commands VT Payload and Test Pattern :SOURce:DATA:TELecom:SONet:PAYLoad:TYPE <discrete> <discrete> = UNFRamed No framing The corresponding query returns the framing in discrete form as listed above. :SOURce:DATA:TELecom:SONet:PAYLoad:TYPE? Returns : <discrete> :SOURce:DATA:TELecom:SONet:PAYLoad:STRucture <discrete> <discrete> = UNSTructured All rates Selects whether or not the PDH payload signal is to have any further structure or not.
  • Page 212 SOURce subsystem - Transmitter SONET Settings Commands Selects the transmitter SONET payload data pattern. If UWORd is selected, the word pattern is set using :SOURce:DATA:TELecom:SONet:PAYLoad:UWORd <string>. The corresponding query returns the transmitter SONET payload data pattern in discrete form, as listed above. :SOURce:DATA:TELecom:SONet:PAYLoad:PATTern? Returns : <discrete>...
  • Page 213 SOURce subsystem - Transmitter SONET Settings Commands Sets the 140, 34, 2 Mb/s, DS3 or DS1 payload frequency offset in parts per million (ppm). The corresponding query returns the offset in numeric form. :SOURce:DATA:TELecom:SONet:PAYLoad:OFFSet? Returns: <numeric> :SOURce:DATA:TELecom:SONet:TRIButary:CONCatenate <numeric>, <numeric> <numeric> = (first Concatenation Off parameter) VT6-2c...

  • Page 214: Background Settings

    SOURce subsystem - Transmitter SONET Settings Commands Background Settings :SOURce:DATA:TELecom:SONet:PRIMary:BACKground:PAYLoad :PATTern <discrete> <discrete> = PRBS9 PRBS15 NUMBered (VT-6 or framed VT-2/VT-1.5) P1100 word 1100 Selects the background payload pattern for VTs within the foreground VT Group. The corresponding query returns the background pattern in discrete form as listed above.
  • Page 215 SOURce subsystem - Transmitter SONET Settings Commands Selects the payload in the background (non test) STS-3s. This command only applies if the interface rate is higher than STS-3. The corresponding query returns the type of payload in the background STS-3s in discrete short form.

  • Page 216: Source Subsystem - Transmitter Sonet Overhead Setup

    SOURce subsystem - Transmitter SONET OVERHEAD SETUP SOURce subsystem - Transmitter SONET OVERHEAD SETUP Lists the settings for the commands associated with the TRANSMIT OVERHEAD SETUP display. :SOURce:DATA:TELecom:SONet:OVERhead:DEFault Sets all overhead bytes to their default value : Byte Value Byte Value Byte Value...
  • Page 217 SOURce subsystem - Transmitter SONET OVERHEAD SETUP X32|X33|X41|X42|X52|X53|X61|X62|X63 X71|X72|X73|X81|X82|X83|X91|X92|X93 <string> = "00000000" to "11111111" Sets the binary value for the selected transmitter section overhead byte. The byte number is given by its defined name if it has one. Undefined bytes are represented by "Xrc", where r is the numerical value of the bytes row in the transport overhead and c is the numerical value of the bytes column in the transport overhead.
  • Page 218 SOURce subsystem - Transmitter SONET OVERHEAD SETUP Sets the hexadecimal value for the selected transmitter transport overhead byte. The byte number is given by its defined name if it has one. Undefined bytes are represented by "Xrc", where r is the numerical value of the bytes row in the transport overhead and c is the numerical value of the bytes column in the transport overhead.
  • Page 219 SOURce subsystem - Transmitter SONET OVERHEAD SETUP LOCKed Locked VT (00000011) DS3asyn Asynchronous DS3 (00000100) DS4Naasyn Asynchronous DS4NA (00010010) ATM (00010011) DQDB DQDB (00010100) FDDI FDDI (00010101) USER User Defined Sets the value of the STS POH path label (C2 Byte). To update the USER byte value use the :SOURce:DATA:TELecom:SONet:POVerhead:DATA <discrete>, <string>...
  • Page 220 SOURce subsystem - Transmitter SONET OVERHEAD SETUP :SOURce:DATA:TELecom:SONet:POVerhead:J1 <string> Sets the user defined pattern that is to be transmitted in the J1 byte of the STS path overhead. The pattern should be 64 characters long, terminated with CR/LF. If less than 64 characters are input, the instrument will pad with the required number of NULL characters and terminate with CR/LF.
  • Page 221 SOURce subsystem - Transmitter SONET OVERHEAD SETUP :SOURce:DATA:TELecom:SONet:TRIButary:POVerhead:DATA <discrete>, <string> <discrete>= V5|Z6|Z7 Sets the value of the specific VT-2, VT-1.5 or VT-6 path overhead byte to the value specified by string (in the range "00000000" to "11111111"). The byte is specified by the first parameter.
  • Page 222 SOURce subsystem - Transmitter SONET OVERHEAD SETUP characters. The pattern repeats every 16 characters and is transmitted character by character in subsequent frames. The corresponding query returns the value of the user defined pattern as a string, as defined above. If the string contains any non printing characters, ~ is substituted. If FIXed was returned in response to:SOURce:DATA:TELecom:SONet:OVERhead:J0:PATTern?, this query command is not valid.
  • Page 223 SOURce subsystem - Transmitter SONET OVERHEAD SETUP :SOURce:DATA:TELecom:SONet:TRIButary:POVerhead:J2:PATTern? Returns : <discrete> :SOURce:DATA:TELecom:SONet:TRIButary:POVerhead:J2 <string> Sets the user defined pattern that is to be transmitted in the J2 byte of the VT-6, VT- 2 or VT-1.5 path overhead. The pattern should be 15 characters long. If less than 15 characters are input, the instrument will pad with the required number of NULL characters and a frame marker byte with CRC7 is added to the string.
  • Page 224 SOURce subsystem - Transmitter SONET OVERHEAD SETUP :SOURce:DATA:TELecom:SONet:TRIButary:POVerhead:V5:SLABel <numeric> <numeric> = 0 to 7 Sets the VT-6, VT-2 or VT-1.5 signal label (Byte V5) value. The corresponding query returns the signal label value in numeric form. :SOURce:DATA:TELecom:SONet:TRIButary:POVerhead:V5:SLABel? Returns : <numeric> :SOURce:DATA:TELecom:SONet:POVerhead:H4Sequence <discrete>...
  • Page 225 SOURce subsystem - Transmitter SONET OVERHEAD SETUP DONTusesync Do not use for synchronization (1111) USER Selects the SONET SYNC message type (S1 Byte Bits 5 to 8). To update the USER byte value use either the :SOURce:DATA:TELecom:SONet:OVERhead:DATA <numeric>, <numeric>, <discrete>, <string> or the :SOURce:DATA:TELecom:SONet:OVERhead:DATA:HEXadecimal <numeric>, <numeric>, <discrete>, <string>...

  • Page 226: Source Subsystem - Transmitter Sonet Test Function Commands

    :SOURce subsystem - Transmitter SONET Test Function Commands :SOURce subsystem - Transmitter SONET Test Function Commands :SOURce:DATA:TELecom:SONet:TFUNction:TYPE <discrete> <discrete> = ERRor Errors & Alarms POINter Pointer SEQuence Overhead sequences STESt Optical Stress APSMessages APS messages IDCC Insert Datacomm OBERtest Overhead BER test Selects the SONET transmit test function type.
  • Page 227 :SOURce subsystem - Transmitter SONET Test Function Commands REIP REI-P (Path FEBE) CVIec CV-IEC CV-V (VT Path BIP) REIV REI-V (VT Path FEBE) Selects SONET transmit test function error type when :SOURce:DATA:TELecom:SONet:TFUNction:TYPE <discrete>is set to ERR . Further selection of :SOURce:DATA:TELecom:SONet:ERRor:RATE <discrete> is required.
  • Page 228 :SOURce subsystem - Transmitter SONET Test Function Commands Frame Errors only Frame Errors only THRee Frame Errors only FOUR Frame Errors only Selects the transmitter SONET Error rate of the error type selected by :SOURce:DATA:TELecom:SONet:ERRor:TYPE <discrete>. This command is applicable when :SOURce:DATA:TELecom:TFUNction <discrete> is set to SONet. If bit errors are to be added to the PDH payload then :SOURce:DATA:TELecom:TFUNction <discrete>...
  • Page 229 :SOURce subsystem - Transmitter SONET Test Function Commands 1.0E-4 error rate 1.0E-5 error rate 1.0E-6 error rate 1.0E-7 error rate USER User defined error rate Sets the PDH Payload error rate for the error type selected by :SOURce:DATA:TELecom:SONet:PDHPayload:ERRor:TYPE <discrete>. This command is applicable when :SOURce:DATA:TELecom:SOURce <discrete>...
  • Page 230 :SOURce subsystem - Transmitter SONET Test Function Commands :SOURce:DATA:TELecom:SONet:ERRor:APSThreshold:NERRors <numeric> <numeric> = 0 to 640 for STS 0 0 to 1920 for STS1 0 to 7680 for STS12 0 to 30720 for STS48 Sets the number of errors for the APS Threshold when :SOURce:DATA:TELecom:SONet:ERRor:RATE <discrete>...
  • Page 231 :SOURce subsystem - Transmitter SONET Test Function Commands :SOURce:DATA:TELecom:SONet:ERRor:APSThreshold:EINTerval? Returns : <discrete> :SOURce:DATA:TELecom:SONet:ALARm <discrete> <discrete> = NONE Alarms Off Loss of Signal Loss of Frame Severely Errored Frame Defect AISL Line AIS (AIS-L) RDIL Line FERF (RDI-L) LOPP Loss of Pointer (LOP-P) AISP Path AIS (AIS-P) RDIP...
  • Page 232 :SOURce subsystem - Transmitter SONET Test Function Commands :SOURce:DATA:TELecom:SONet:ALARm:SSEFrame Generates a single Severely Errored Frame alarm. :SOURce:DATA:TELecom:SONet:POINter <discrete> <discrete> = BURSt Adds bursts NPOinter New Pointer OFFSet Adds offset in ppm T1105 Adds T1.105/GR-253 sequence Selects the Pointer adjustment type when :SOURce:DATA:TELecom:SONet:TFUNction:TYPE <discrete>...
  • Page 233 :SOURce subsystem - Transmitter SONET Test Function Commands ALTernate Selects the direction of the pointer burst adjustment when :SOURce:DATA:TELecom:SONet:TFUNction:TYPE <discrete> is set to POIN. The corresponding query returns the pointer burst direction in discrete form as listed above. :SOURce:DATA:TELecom:SONet:POINter:DIRection? Returns : <discrete>...
  • Page 234 :SOURce subsystem - Transmitter SONET Test Function Commands Selects the SPE New Pointer value when :SOURce:DATA:TELecom:SONet:TFUNction:TYPE <discrete> is set to POIN and :SOURce:DATA:TELecom:SONet:POINter <discrete> is set to NPO. The corresponding query returns the new pointer value in numeric form as listed above.
  • Page 235 :SOURce subsystem - Transmitter SONET Test Function Commands Selects the type of new pointer when :SOURce:DATA:TELecom:SONet:TFUNction:TYPE <discrete> is set to POIN and :SOURce:DATA:TELecom:SONet:POINter <discrete> is set to NPO. The corresponding query returns the type of new pointer in discrete form as listed above.
  • Page 236 :SOURce subsystem - Transmitter SONET Test Function Commands Selects the amount of offset applied to the Output Signal Rate or the SPE Rate or the VT Rate when :SOURce:DATA:TELecom:SONet:TFUNction:TYPE <discrete> is set to POIN and :SOURce:DATA:TELecom:SONet:POINter <discrete> is set to OFFS.
  • Page 237 :SOURce subsystem - Transmitter SONET Test Function Commands Selects the pattern of the T1.105/GR-253 pointer sequence when :SOURce:DATA:TELecom:SONet:TFUNction:TYPE <discrete> is set to POIN and :SOURce:DATA:TELecom:SONet:POINter <discrete> is set to T1105 and :SOURce:DATA:TELecom:SONet:POINter:T1105 <discrete> is set to PNOR, PADD or PCAN. The corresponding query returns the T1.105/GR-253 pattern in discrete form as listed above.
  • Page 238 :SOURce subsystem - Transmitter SONET Test Function Commands The corresponding query returns the T1.105/GR-253 interval as listed above. The default suffix unit is seconds. :SOURce:DATA:TELecom:SONet:POINter:T1105:INTerval? Returns : <numeric>, <suffix> :SOURce:DATA:TELecom:SONet:POINter:T1105:SEQuence <discrete> <discrete> = STOP Stop the current T1.105/GR-253 pointer sequence STARt Start a T1.105/GR-253 pointer sequence INITialize...
  • Page 239 :SOURce subsystem - Transmitter SONET Test Function Commands :SOURce:DATA:TELecom:SONet:SEQuence:MODE <discrete> <discrete> = SINGle Single Run REPeat Repeat Run Selects the type of SEQUENCE when :SOURce:DATA:TELecom:SONet:TFUNction:TYPE <discrete> is set to SEQ. The corresponding query returns the type of Sequence in discrete form as listed above.
  • Page 240 :SOURce subsystem - Transmitter SONET Test Function Commands Sets the STS-1 Number of the byte to be sequenced. The corresponding query returns the STS-1 Number in numeric form. :SOURce:DATA:TELecom:SONet:SEQuence:STS1? Returns: <numeric> :SOURce:DATA:TELecom:SONet:SEQuence:STS3:SELect <numeric> <numeric> = 1 to 16 Selects STS-3 number for channels that occur in more than one STS-3. The corresponding query returns the STS-3 number in numeric form.
  • Page 241 :SOURce subsystem - Transmitter SONET Test Function Commands :SOURce:DATA:TELecom:SONet:SEQuence:ORDer <discrete>, <discrete>, <discrete>, <discrete>, <discrete> <discrete> = A | B | C | D | E Selects the order of transmission for the blocks of data used in the sequence. The corresponding query returns the block order in discrete form as listed above. :SOURce:DATA:TELecom:SONet:SEQuence:ORDer? Returns : <discrete>, <discrete>, <discrete>, <discrete>, <discrete>...
  • Page 242 :SOURce subsystem - Transmitter SONET Test Function Commands :SOURce:DATA:TELecom:SONet:STESt:SPATtern? Returns : <discrete> :SOURce:DATA:TELecom:SONet:STESt:BLENgth <numeric> <numeric> = 2 to 85 OC-1 2 to 259 OC-3 2 to 1042 OC-12 2 to 4174 OC-48 Selects the block length used in the SONET Optical stress test when :SOURce:DATA:TELecom:SONet:TFUNction:TYPE <discrete>...
  • Page 243 :SOURce subsystem - Transmitter SONET Test Function Commands RREQuest Reverse Request (0010) THRee Not Used (0011) EXERcise Exercise (0100) FIVE Not Used (0101) WTRestore Wait To Restore (0110) SEVen Not Used (0111) MSWitch Manual Switch (1000) NINE Not Used (1001) SDLPriority Signal Degrade Low Priority (1010) SDHPriority...
  • Page 244 :SOURce subsystem - Transmitter SONET Test Function Commands Working Channel 1 Working Channel 2 Working Channel 3 Working Channel 4 Working Channel 5 Working Channel 6 Working Channel 7 Working Channel 8 Working Channel 9 Working Channel 10 Working Channel 11 Working Channel 12 Working Channel 13 Working Channel 14...
  • Page 245 :SOURce subsystem - Transmitter SONET Test Function Commands :SOURce:DATA:TELecom:SONet:APSMessages:BRIDge <string> <string> = "0000" to "1111" Selects the SONET transmitter Linear APS message bridged channel (K2 Byte, Bits 1 to 4). Only valid if :SOURce:DATA:TELecom:TFUNction <discrete> is set to SONet and :SOURce:DATA:TELecom:SONet:TFUNction:TYPE <discrete> is set to APSM and :SOURce:DATA:TELecom:SONet:APSMessages:TOPology <discrete>...
  • Page 246 :SOURce subsystem - Transmitter SONET Test Function Commands Selects the SONET transmitter Linear APS messages reserved bits (K2 Byte, Bits 6 to 8) in numeric form. Only valid if :SOURce:DATA:TELecom:TFUNction <discrete> is set to SONet and :SOURce:DATA:TELecom:SONet:TFUNction:TYPE <discrete> is set to APSM and :SOURce:DATA:TELecom:SONet:APSMessages:TOPology <discrete>...
  • Page 247 :SOURce subsystem - Transmitter SONET Test Function Commands SFSPan Signal Fail - Span (1100) FSRing Forced Switch Ring (1101) FSSPan Forced Switch - Span(1110) LOPRotection Lockout Of Protection (1111) Selects the transmitter Ring APS message to be transmitted (K1 Byte, Bits 1 to 4). Only valid if :SOURce:DATA:TELecom:TFUNction <discrete>...
  • Page 248 :SOURce subsystem - Transmitter SONET Test Function Commands Selects the SONET transmitter Ring APS message source node (K2 Byte, Bits 1 to 4) . Only valid if :SOURce:DATA:TELecom:TFUNction <discrete> is set to SONet and :SOURce:DATA:TELecom:SONet:TFUNction:TYPE <discrete> is set to APSM and :SOURce:DATA:TELecom:SONet:APSMessages:TOPology <discrete> is set to RING.
  • Page 249 :SOURce subsystem - Transmitter SONET Test Function Commands Selects the SONET transmitter Ring APS messages status code (K2 Byte, Bits 6 to 8). Only valid if :SOURce:DATA:TELecom:TFUNction <discrete> is set to SONet and :SOURce:DATA:TELecom:SONet:TFUNction:TYPE <discrete> is set to APSM and :SOURce:DATA:TELecom:SONet:APSMessages:TOPology <discrete> is set to RING.
  • Page 250 :SOURce subsystem - Transmitter SONET Test Function Commands J1|C2|G1|F2|H4|Z3| Path Overhead Z4|N1 Selects the TX overhead byte used for the overhead BER test when :SOURce:DATA:TELecom:SONet:TFUNction:TYPE <discrete> is set to OBER. M0 is valid at STS-1 only. The corresponding query returns the overhead byte identity in discrete form as listed above.
  • Page 251 :SOURce subsystem - Transmitter SONET Test Function Commands The corresponding query returns the STS-3 number in numeric form. :SOURce:DATA:TELecom:SONet:OBERtest:STS3:SELect? Returns: <numeric> :SOURce:DATA:TELecom:SONet:OBERtest <discrete> <discrete> = ONCE Single error Injects a single overhead BER error when SOURce:DATA:TELecom:SONet:TFUNction:TYPE <discrete> is set to OBER.

  • Page 252: Input Subsystem

    INPut subsystem INPut subsystem This subsytem controls the characteristics of the instrument’s input ports. :INPut:TELecom:OC3:RATE <discrete> <discrete> = OC-1 optical OC-3 Optical Sets the input rate for the optical input port. :SENSe:DATA:TELecom:SENSe <discrete> is set to OC3. The corresponding query returns the OC-3 input rate in discrete form, as listed above.
  • Page 253 INPut subsystem Sets the input rate for the optical input port. :SENSe:DATA:TELecom:SENSe <discrete> is set to OC12. The corresponding query returns the OC-12 input rate in discrete form, as listed above. :INPut:TELecom:OC12:RATE? Returns : <discrete> :INPut:TELecom:OC12:INTerface <discrete> <discrete> = OPTical Optical input MONitor Protected Monitor Input...
  • Page 254 INPut subsystem :INPut:TELecom:OC48:INTerface <discrete> <discrete> = OPTical Optical input MONitor Protected Monitor Input Selects the input interface on the Optical modules. The corresponding query returns the input interface in discrete form, as listed above. :INPut:TELecom:OC48:INTerface? Returns: <discrete> 4-59 Artisan Technology Group - Quality Instrumentation ... Guaranteed | (888) 88-SOURCE | www.artisantg.com...

  • Page 255: Sense Subsystem - Receiver Sonet Settings

    SENSe subsystem - Receiver SONET Settings SENSe subsystem - Receiver SONET Settings SONET Mapping settings :SENSe:DATA:TELecom:SONet:STS3 <numeric> <numeric> = 1 to 16 STS-3 Number under test Selects the STS-3 number under test. Only valid if :INPut:TELecom:OC3:RATE <discrete> is set a rate higher than STS3. The corresponding query returns the test STS3 number.

  • Page 256: Spe Layer Selection

    SENSe subsystem - Receiver SONET Settings :SENSe:DATA:TELecom:SONet:STS12c <numeric> <numeric> = 1 to 4 STS-12c Number under test SPE Layer Selection :SENSe:DATA:TELecom:SONet:SPE:TYPE <discrete> <discrete> = STS3c STS1 STS12c STS48c Set the SPE mapping into an STS-N frame. The corresponding query returns the SPE layer in discrete form as listed above. :SENSe:DATA:TELecom:SONet:SPE:TYPE? Returns: <discrete>...

  • Page 257: Payload Layer Selection

    SENSe subsystem - Receiver SONET Settings VT2 or M2 2 Mb/s VT-6 STS12c STS48c VT15 or DS1 VT-1.5 This command selects the SONET receiver mapping The corresponding query returns the mapping in discrete form, as listed above. :SENSe:DATA:TELecom:SONet:PAYLoad? Returns : <discrete>...

  • Page 258: Vt Group

    SENSe subsystem - Receiver SONET Settings :SENSe:DATA:TELecom:SONet:PRIMary:TS0 <boolean> <boolean> = 0 or OFF Data in TS0 1 or ON Signaling in TS0 Determines the content of TS0 as Data/Signaling. The corresponding query returns the TS0 state in numeric form. :SENSe:DATA:TELecom:SONet:PRIMary:TS0? Returns : <boolean>...

  • Page 259: Vt Payload And Test Pattern

    SENSe subsystem - Receiver SONET Settings VT Payload and Test Pattern :SENSe:DATA:TELecom:SONet:PAYLoad:TYPE <discrete> <discrete> = UNFRamed No framing The corresponding query returns the framing in discrete form as listed above. :SENSe:DATA:TELecom:SONet:PAYLoad:TYPE? Returns : <discrete> :SENSe:DATA:TELecom:SONet:PAYLoad:STRucture <discrete> <discrete> = UNSTructured All rates Determines whether the receiver is to expect any structure in the PDH payload.
  • Page 260 SENSe subsystem - Receiver SONET Settings UWORd 16 Bit User Word LIVE Live Traffic Selects the receiver SONET payload data pattern. If UWORd is selected, the word pattern is set using :SENSe:DATA:TELecom:SONet:PAYLoad:UWORd <string>. The corresponding query returns the receiver SONET payload data pattern in discrete form as listed above.
  • Page 261 SENSe subsystem - Receiver SONET Settings :SENSe:DATA:TELecom:SONet:PRBS:POLarity? Returns : <discrete> :SENSe:DATA:TELecom:SONet:TRIButary:CONCatenate <numeric>,<numeric> <numeric> = Concatenation Off VT6-2c VT6-3c VT6-4c VT6-5c VT6-6c <numeric> = 1 to 6 VT6-2c selected 1 to 5 VT6-3c selected 1 to 4 VT6-4c selected 1 to 3 VT6-5c selected 1 to 2 VT6-6c selected...

  • Page 262: Sense Subsystem - Receiver Sonet Test Function Commands

    SENSe subsystem - Receiver SONET Test Function Commands SENSe subsystem - Receiver SONET Test Function Commands Lists the commands associated with the RECEIVE TEST FUNCTION display. : SENSe:DATA:TELecom:SONet:TFUNction:TYPE <discrete> <discrete> = NONE OCAPture Overhead Capture DDCC DCC Drop PGRaph Pointer Graph OBERtest Overhead BER Selects the active Receiver Test Function.
  • Page 263 SENSe subsystem - Receiver SONET Test Function Commands :SENSe:DATA:TELecom:SONet:OCAPture:OHBYte <discrete> <discrete> = A1A2 | J0/Z0 | E1 | F1 | D1D3| Section Overhead BNDA1A2|X22|X23|X32|X33 H1H2 | K1K2 | D4D12 | S1/Z1 Line Overhead | M1/Z2| E2 J1 | C2 | G1 | F2 | H4 | Z3 | Z4 | Path Overhead Selects the overhead byte or bytes to be captured.
  • Page 264 SENSe subsystem - Receiver SONET Test Function Commands Only valid if a rate higher than STS-3 is selected. Selects STS-3 number for channels that occur in more than one STS-3. The corresponding query returns the STS-3 number in numeric form. :SENSe:DATA:TELecom:SONet:OCAPture:STS3:SELect? Returns: <numeric>...
  • Page 265 SENSe subsystem - Receiver SONET Test Function Commands The corresponding query returns the Trigger Pattern selected, as a string as described above. :SENSe:DATA:TELecom:SONet:OCAPture:TRIGger:PATTern? Returns : <string> :SENSe:DATA:TELecom:SONet:DDCC <discrete> <discrete> = SDCC Section DCC LDCC Line DCC Selects the DataCommunications channel to be dropped via the rear panel DROP port.
  • Page 266 SENSe subsystem - Receiver SONET Test Function Commands :SENSe:DATA:TELecom:SONet:PGRaph:PTYPe? Returns: <discrete> :SENSe:DATA:TELecom:SONet:PGRaph:CINTerval <discrete> <discrete> = SEC1 1 second interval SEC5 5 second interval SEC20 20 second interval MIN1 1 minute interval MIN5 5 minute interval MIN20 20 minute interval Selects the pointer graph capture interval. The corresponding query returns the pointer graph capture interval, in discrete form as listed above.
  • Page 267 SENSe subsystem - Receiver SONET Test Function Commands :SENSe:DATA:TELecom:SONet:OBERtest:STS3? Returns: <discrete> :SENSe:DATA:TELecom:SONet:OBERtest:STS1 <numeric> <numeric>= 1 to 3 Sets the STS-1 Number (within the currently selected STS-3) of the Section overhead of the channel for the receiver overhead BER test function. This command is only valid if : SENSe:DATA:TELecom:SONet:TFUNction:TYPE <discrete>...

  • Page 268: Sense Subsystem - Alarm Scan Control

    SENSe subsystem - Alarm Scan Control SENSe subsystem - Alarm Scan Control :SENSe:DATA:TELecom:SONet:ASCan:MODE <discrete> <discrete> = AUTomatic Automatic receiver configuration RSETtings Fixed receiver configuration Selects the SONET alarm scan mode. The corresponding query returns the alarm scan mode in discrete short form. :SENSe:DATA:TELecom:SONet:ASCan:MODE? Returns: <discrete>...
  • Page 269 SENSe subsystem - Alarm Scan Control The corresponding query returns the alarm scan state as 0 or 1. :SENSe:DATA:TELecom:SONet:ASCan? Returns: <boolean> 4-74 Artisan Technology Group - Quality Instrumentation ... Guaranteed | (888) 88-SOURCE | www.artisantg.com...

  • Page 270: Sense Subsystem - Sonet Tributary Scan Control

    SENSe subsystem - SONET Tributary Scan Control SENSe subsystem - SONET Tributary Scan Control :SENSe:DATA:TELecom:SONet:TSCan:PERiod <numeric>, <suffix> <numeric> = 1 to 99 <suffix> = Days Hours Minutes Seconds Sets the test duration for each tributary. The corresponding query returns the test duration for each tributary. :SENSe:DATA:TELecom:SONet:SONet:TSCan:PERiod? Returns: <numeric>,<suffix>...
  • Page 271 SENSe subsystem - SONET Tributary Scan Control :SENSe:DATA:TELecom:SONet:TSCan <boolean> <boolean> = 0 or OFF Stop the current tributary scan 1 or ON Start a new tributary scan Start/Stop the SONET tributary scan. The corresponding query returns the alarm scan state as 0 or 1. :SENSe:DATA:TELecom:SONet:TSCan? Returns: <boolean>...

  • Page 272: Sense Subsystem - Rei-L Result Enable/Disable

    SENSe subsystem - REI-L Result Enable/Disable SENSe subsystem - REI-L Result Enable/ Disable :SENSe:DATA:TELecom:SONet:REIL? Returns: <boolean> 4-77 Artisan Technology Group - Quality Instrumentation ... Guaranteed | (888) 88-SOURCE | www.artisantg.com...

  • Page 273: Sense Subsystem - Result Returning Commands

    SENSe subsystem - Result Returning Commands SENSe subsystem - Result Returning Commands Frequency Results (SONET) :SENSe:DATA? <"result"> Result = "FREQuency:SONet:GATE1S" RX SONET clock frequency (1s gate) "FREQuency:SONet[:GATE16S]" RX SONET clock frequency (16s gate) "FOFPpm:SONet[:GATE16S]" RX SONET clock offset in ppm (16s gate) "FOFHz:SONet[:GATE16S]"...

  • Page 274: Sonet Cumulative Results

    SENSe subsystem - Result Returning Commands "ERATio:SONet:STERm:CVIec" CV-IEC error ratio "ECOunt:SONet:STERm:TRIB:CVV" VT Path BIP error count "ERATio:SONet:STERm:TRIB:CVV" VT Path BIP error ratio "ECOunt:SONet:STERm:TRIB:REIV" VT FEBE error count "ERATio:SONet:STERm:TRIB:REIV" VT FEBE error ratio SONET Cumulative Results :SENSe:DATA? <"result"> Result = "ECOunt:SONet:FRAMe" Frame error count "ERATio:SONet:FRAMe"...

  • Page 275: Sonet Section B1 Bip (Cv-S) Analysis Results

    SENSe subsystem - Result Returning Commands SONET Section B1 BIP (CV-S) Analysis Results :SENSe:DATA? <"result"> Result= "ESEConds:SONet:CVS:ANALysis" Error Seconds "SESeconds:SONet:CVS:ANALysis" Severely Errored Seconds "EBCount:SONet:CVS:ANALysis" Errored block count "BBECount:SONet:CVS:ANALysis" Background block error count "ESRatio:SONet:CVS:ANALysis" Error Second Ratio "SESRatio:SONet:CVS:ANALysis" Severely Errored Second Ratio "BBERatio:SONet:CVS:ANALysis"...

  • Page 276: Sonet Path B3 Bip (Cv-P) Analysis Results

    SENSe subsystem - Result Returning Commands Result= "ESEConds:SONet:REIL:ANALysis" Error Seconds "SESeconds:SONet:REIL:ANALysis" Severely Errored Seconds "EBCount:SONet:REIL:ANALysis" Errored block count "BBECount:SONet:REIL:ANALysis" Background block error count "ESRatio:SONet:REIL:ANALysis" Error Second Ratio "SESRatio:SONet:REIL:ANALysis" Severely Errored Second Ratio "BBERatio:SONet:REIL:ANALysis" Background Block Error ratio "UASeconds:SONet:REIL:ANALysis" Unavailable seconds "PUASeconds:SONet:REIL:ANALysis"...

  • Page 277: Sonet Cv-Iec Analysis Results

    SENSe subsystem - Result Returning Commands "EBCount:SONet:REIP:ANALysis" Errored block count "BBECount:SONet:REIP:ANALysis" Background block error count "ESRatio:SONet:REIP:ANALysis" Error Second Ratio "SESRatio:SONet:REIP:ANALysis" Severely Errored Second Ratio "BBERatio:SONet:REIP:ANALysis" Background Block Error ratio "UASeconds:SONet:REIP:ANALysis" Unavailable seconds "PUASeconds:SONet:REIP:ANALysis" Path Unavailable seconds SONET CV-IEC Analysis Results :SENSe:DATA? <"result">...

  • Page 278: Sonet Virtual Tributary Path Febe (Rei-V) Analysis Results

    SENSe subsystem - Result Returning Commands "SESRatio:SONet:TRIB:CVV:ANALysis" Severely Errored Second Ratio "BBERatio:SONet:TRIB:CVV:ANALysis" Background Block Error ratio "UASeconds:SONet:TRIB:CVV:ANALysis" Unavailable seconds "PUASeconds:SONet:TRIB:CVV:ANALysis" Path Unavailable seconds SONET Virtual Tributary Path FEBE (REI-V) Analysis Results :SENSe:DATA? <"result"> Result = "ESEConds:SONet:TRIB:REIV:ANALysis" Error Seconds "SESeconds:SONet:TRIB:REIV:ANALysis" Severely Errored Seconds "EBCount:SONet:TRIB:REIV:ANALysis"...

  • Page 279: Sonet M.2101 Analysis Results

    SENSe subsystem - Result Returning Commands "BBERatio:SONet:BLKBit:ANALysis" Background Block Error ratio "UASeconds:SONet:BLKBit:ANALysis" Unavailable seconds SONET M.2101 Analysis Results :SENSe:DATA? <“result”> Result = “ESEConds:SONet:LOW:RECeive:ANALysi Low Order Path Receive Direction Errored Seconds s:M2101” “SESeconds:SONet:LOW:RECeive:ANALysi Low Order Path Receive Direction Severely Errored s:M2101” Seconds “UASeconds:SONet:LOW:RECeive:ANALysi Low Order Path Receive...

  • Page 280: Sonet Service Disruption Results

    SENSe subsystem - Result Returning Commands “UASeconds:SONet:HIGH:TRANsmit:ANAL High Order Path Transmit Direction Unavailable Seconds ysis:M2101” “ESEConds:SONet:SECTion:RECeive:ANA Section Layer Path Receive Direction Errored Seconds Lysis:M2101” “SESeconds:SONet:SECTion:RECeive:ANA Section Layer Path Receive Direction Severely Errored Lysis:M2101” Seconds “UASeconds:SONet:SECTion:RECeive:ANA Section Layer Path Receive Direction Unavailable Seconds Lysis:M2101”...

  • Page 281: Sonet Optical Power Result

    SENSe subsystem - Result Returning Commands SONET Optical Power Result :SENSe:DATA? <"result"> Result = "OPOWer:SONet" Optical power (dBm) SONET Pointer Activity Results :SENSe:DATA? <"result"> Result "PACTivity:SONet:PVALue" SPE Pointer value "PACTivity:SONet:NDFSeconds" SPE Pointer NDF seconds "PACTivity:SONet:MNDFseconds" SPE Pointer MNDF seconds "PACTivity:SONet:PCOunt" SPE Pointer +ve Adj Count "PACTivity:SONet:PSEConds"...

  • Page 282: Sonet Alarm Seconds Results

    SENSe subsystem - Result Returning Commands SONET Alarm Seconds Results :SENSe:DATA? <"result"> Result = "ASEConds:SONet:LOS" Loss Of Signal "ASEConds:SONet:LOF" Loss Of Frame "ASEConds:SONet:SEF" Severely Errored Frame Defect "ASEConds:SONet:H4MF" H4 Multiframe Loss "ASEConds:SONet:LOPP" Loss Of Pointer (LOP-P) "ASEConds:SONet:AISL" Line AIS (AIS-L) "ASEConds:SONet:AISP"...

  • Page 283: Fetch Subsystem

    FETCh subsystem FETCh subsystem The FETCh subsystem is used to retrieve data directly accumulated by the instrument. :FETCh:STRing:DATA:TELecom:SONet:J0? Returns: <string> The value of the STS-N Section overhead J0 byte is returned as a 16 ASCII character string if CRC7 is not detected, 15 ASCII character string if CRC7 is detected.
  • Page 284 Returns: <string> Returns the 15 or 16 byte J2 path trace as a string. The OmniBER 720 attempts to align the received pattern by detecting the CRC7 byte. If the CRC7 byte is detected, a 15 byte pattern is returned. If the CRC7 byte is not detected, a 16 byte pattern is returned.
  • Page 285 FETCh subsystem :FETCh:STRing:DATA:TELecom:SONet:S1? Returns : <string> The value of the SYNC S1 byte (bits 5-8) is returned as a 4 bit string in the range "0000" to "1111". :FETCh:SCALar:DATA:TELecom:SONet:OVERhead? <numeric>,<numeric>, <discrete> <numeric> range 1 to 16 =(STS3#) <numeric> range 1 to 3 =(STS1#) <discrete>...
  • Page 286 FETCh subsystem :FETCh:SCALar:DATA:TELecom:SONet:POVerhead? <discrete> <discrete> = J1|B3|C2|G1|F2|H4|Z3|Z4|N1 Obtains the value of the named path overhead byte. The value of the named byte is returned as a string in the range "00000000" to "11111111". This is a snapshot of the overhead byte and is captured once per second. Returns: <string>...
  • Page 287 FETCh subsystem Value State No Problems Detected Alarms or Errors Detected Path Unequipped Loss of Pointer H4 Multiframe Loss Invalid For a specific signal structure, the format of the returned strings are shown below: a) STS-3 STS-1 VT-6 This signal consists of 3 STS-1s each of which contains 7 VT-Groups. The VT- Groups’s in turn each contain 1 VT-6.
  • Page 288 FETCh subsystem b) STS-3 STS-1 Full SPE This signal consists of 3 STS-1s each containing 1 Full SPE. In this configuration there are 3 paths, 3 at the STS-1 level and no lower paths. For this configuration, 3 arrays are returned with the following format: STS-3 ->...
  • Page 289 FETCh subsystem d) STS-3 STS-1 VT-1.5 This signal again consists of 3 STS-1s. In this case however, the STS-1’s each contain 7 VT-Groups. These VT-Groups’s each contain 4 VT-1.5’s. In terms of paths the signal comprises 3 paths at the STS-1 level and 84 paths at the VT-1.5 level.
  • Page 290 FETCh subsystem f) STS-1 VT-2 This signal again comprises 1 STS-1 containing 7 VT-Groups’s. However, this time the VT-Groups’s each contain 3 VT-2’s. As before, the STS-1 path is defined as a group on its own, while the 7 VT-2 paths are also defined as one group. For this configuration, 2 groups are returned with the following format: NOTE: VT-2’s designated thus [VT-Grp# - VT-2#]...
  • Page 291 FETCh subsystem :FETCh:ARRay:DATA:TELecom:SONet:TSCan? Returns (each of one or <numeric>{,<numeric} more rows): The results returned are those for the last FULL scan. Results from partial scans are not available. If no full scan has been completed since the instrument was powered up, this command will return -1.
  • Page 292 FETCh subsystem STS-1 -> [1-1],[1-2],[1-3],[2-1],[2-2],[2-3],[3-1], [3-2],[3-3],[4-1],[4-2],[4-3],[5-1],[5-2], [5-3],[6-1],[6-2],[6-3],[7-1],[7-2],[7-3] The output will look like: 1,1,1,0,0,0,0,1,1,1,1,1,1,1,0,0,1,0,0,0,0 c) STS-1 VT-1.5 This signal again comprises 1 STS-1 containing 7 VT-Groups. However, this time the VT-Groups each contain 4 VT-1.5’s. There are therefore 28 (7*4) tributaries to be scanned.
  • Page 293 FETCh subsystem :FETCh:ARRay:DATA:TELecom:SONet:PGRaph? Returns: <numeric>,<numeric>, <numeric>,... <numeric>,<numeric>, <numeric> Returns an array of 576 bytes, 2 bytes for each of the possible 288 points on the displayed pointer graph. The 2 bytes at each point indicate the maximum and minimum offset at that point. Each byte has 3 numeric entries separated by commas. The value of the 3 numeric entries, <range bit>,<validity bit>,<offset value>, provide the following information: Range bit...
  • Page 294 FETCh subsystem :FETCh:ARRay:DATA:TELecom:SONet:OCAPture? <numeric> <numeric> = 1 to 16 Overhead channels Returns an array with the number of entries determined by <numeric> and separated by CR/LF. Each entry consists of an alphanumeric string and a numeric separated by commas. The alphanumeric string provide the hexadecimal value of the captured data. The length of the string depends upon the overhead channel selected for capture, two hexadecimal characters/overhead byte.
  • Page 295 FETCh subsystem overhead byte and is captured once per second. The array always begins with byte 1 of the transport overhead and ends with the byte number specified by the first parameter. Number Name Number Name Number Name J0/Z0 S1/Z1 M0/M1/Z2 Returns (each of one or more rows): <string>,{<string>}...

  • Page 296: Status Reporting

    Status Reporting Artisan Technology Group - Quality Instrumentation ... Guaranteed | (888) 88-SOURCE | www.artisantg.com...
  • Page 297 Status Reporting Status Reporting The status reporting capability of the OmniBER 720 is provided by the Status Registers and the Status Byte. The STATus subsystem and some IEEE common capability commands control the status registers and the status byte. The following status registers are provided in the OmniBER 720 and con- form to IEEE 488.2:...
  • Page 298 Status Reporting General Status Register The status registers conform to IEEE 488.2 and each comprises 4 registers as shown in Figure 5-1. For the commands which access and control these registers, see “STATus subsystem” on page 2-35 Figure 5-1 General Status Register Condition Register Monitors the defined status conditions.

  • Page 299: Status Byte

    QUEStionable status register. MAV - Message Available. Remains set until all output messages are read from the OmniBER 720. ESR - Event status register summary. Indicates that a bit has been set in the Event status register.

  • Page 300: Standard Event Status Register

    Status Reporting Standard Event Status Register *ESR? - Returns the Standard Event Status Register value in numeric form. *ESE <numeric> - Sets the event enable register mask. *ESE? - Returns the current mask setting. OPC - Operation Complete. RQC - Request Control. QUE - Query Error.

  • Page 301: Questionable Status Register

    Status Reporting QUEStionable Status Register Provides a summary of the DATA status register. For related commands, see “STATus subsystem” on page 2-35 Example: STATus:QUEStionable:EVENt? DB15 DB14 DB13 DB12 DB11 DB10 DATA DB0 - DB8 Not used, always read as 0. DATA - DATA status register summary.

  • Page 302: Operation Status Register

    Status Reporting OPERation Status Register Provides a summary of the INSTrument status register, and reports when a measurement is being made. For related commands, see “STATus subsystem” on page 2-35 Example: STATus:OPERation:EVENt? DB15 DB14 DB13 DB12 DB11 DB10 INST MEAS DB0 - DB3 Not used, always reads as 0.

  • Page 303: Instrument Status Register

    Status Reporting INSTrument Status Register Reports the instrument status. For related commands, see “STATus subsystem” on page 2-35 Example: STATus:INSTrument:EVENt? DB15 DB14 DB13 DB12 DB11 DB10 DISK SMG - Graphics Results enabled. LQE - Logging Queue Empty. EOT - End Of Test period. Not used, always read as 0.

  • Page 304: Data Status Register

    Status Reporting DATA Status Register Summarizes the alarm status registers shown. In addition provides a Power Failed alarm indication. For related commands, see “STATus subsystem” on page 2-35 Example: STATus:DATA:EVENt? DB15 DB14 DB13 DB12 DB11 DB10 SDH3/ SON3 SDH2/ SDH/ SON2 DB0, DB1 Reserved for future use, always read as 0.

  • Page 305: Isummary Status Register

    Status Reporting ISUMmary Status Register Provides alarm indications summarised from SDH/SONET status register and should be used in preference to the SDH/SONET status register. This register provides a summary of the SDH/SONET status register for each of the conditions shown below, see also the diagram on page 4-19. Use this register to determine the status of the instrument independent of its configuration.

  • Page 306: Isummary Status Register Sources

    Status Reporting ISUMmary Status Register Sources Refer to the following Table for an indication of the source of common alarm conditions ISUM SONET Data Bit Name Data Bit Name Data Bit Name MS-AIS AIS-L AU-AIS AIS-P TU-AIS AIS-V MS-RDI RDI-L HP-RDI RDI-P LP-RDI...

  • Page 307: Sdh Status Register

    Status Reporting SDH Status Register Provides primary alarm indications related to the SDH signal. For related commands, see “STATus subsystem” on page 2-41 Example: STATus:SDH:EVENt? DB15 DB14 DB13 DB12 DB11 DB10 LPRDI TUAIS TULOP HPRDI MSRDI AUAIS MSAIS LOS - Loss Of Signal. LOF - Loss Of Frame.

  • Page 308: Sdh2 Status Register

    Status Reporting SDH2 Status Register Provides miscellaneous SDH monitoring. For related commands, see “STATus subsystem” on page 2-41 Example: STATus:SDH2:EVENt? DB15 DB14 DB13 DB12 DB11 DB10 ALSC K1K2 TMNDF TNDF TPADJ MNDF PADJ PADJ - AU Pointer Adjust. NDF - AU Pointer New Data Flag. MNDF - AU Pointer Missing New Data Flag.

  • Page 309: Sdh3 Status Register

    Status Reporting SDH3 Status Register Provides miscellaneous SDH monitoring. For related commands, see “STATus subsystem” on page 2-41 Example: STATus:SDH3:EVENt? DB15 DB14 DB13 DB12 DB11 DB10 FMU_1S TC_RDI TC_IAIS TC_LOM P1P0 P1P0 LOM DB1 - DB7 Not used, always read as 0. FMU_1S - Frequency Measurement Updated.

  • Page 310: Sonet Status Register

    Status Reporting SONet Status Register Provides primary alarm indications related to the SONET signal. For related commands, see “STATus subsystem” on page 2-35 Example: STATus:SONet:EVENt? DB15 DB14 DB13 DB12 DB11 DB10 RDIV AISV LOPV RDIP RDIL AISP AISL LOPP LOS - Loss Of Signal. LOF - Loss Of Frame.

  • Page 311: Sonet2 Status Register

    Status Reporting SONet2 Status Register Provides miscellaneous SONET monitoring. For related commands, see “STATus subsystem” on page 2-35 Example: STATus:SONet2:EVENt? DB15 DB14 DB13 DB12 DB11 DB10 ALSC K1K2 TMNDF TNDF TPADJ MNDF PADJ PADJ - SPE Pointer Adjust. NDF - SPE Pointer New Data Flag. MNDF - SPE Pointer Missing New Data Flag.

  • Page 312: Sonet3 Status Register

    Status Reporting SONet3 Status Register Provides miscellaneous SONET monitoring. For related commands, see “STATus subsystem” on page 2-35 Example: STATus:SONet3:EVENt? DB15 DB14 DB13 DB12 DB11 DB10 FMU_1S P1P0 P1P0 LOM Not used, always read as 0. DB1 - DB7 FMU_1S - Frequency Measurement Updated. (1s gate). Not used, always read as 0.

  • Page 313: Disk Status Register

    Status Reporting DISK Status Register Provides miscellaneous floppy disk monitoring. For related commands, see “STATus subsystem” on page 2-35 Example: STATus:DISK:EVENt? DB15 DB14 DB13 DB12 DB11 DB10 FMT - Formatting Disk. Not used, always read as 0. DB1 - DB15 5-18 Artisan Technology Group - Quality Instrumentation ...
  • Page 314 Status Reporting Figure 5-2 Status Registers Relationship 1 5-19 Artisan Technology Group - Quality Instrumentation ... Guaranteed | (888) 88-SOURCE | www.artisantg.com...
  • Page 315 Status Reporting Figure 5-3 Status Register Relaqtionship 2 5-20 Artisan Technology Group - Quality Instrumentation ... Guaranteed | (888) 88-SOURCE | www.artisantg.com...

  • Page 316: Programmed Status Reporting

    Status Reporting Figure 5-4 Status Registers Relationship 3 Programmed Status Reporting When a condition is detected, a summary bit is generated by the Status Register which detects the condition. The summary bit in most cases passes through other Status Registers before affecting the Status Byte. These other Status Registers also generate a summary bit, therefore to report a condition requires the setting of the Event Enable Register mask in all registers in the chain.
  • Page 317 Status Reporting Programming Interrupts 1) Define which conditions you want reported. To do this, set the Event Enable Register mask of the Status Register that first detects the defined conditions. Set the Event Enable Register mask of all subsequent Status Registers between the reporting Status Register and the Status Byte.
  • Page 318 60 ! The program starts a 10 second BER measurement on the O 70 ! then continually reads and displays the OmniBER 720 Short-Term 80 ! BER until a Service Request is received from the OmniBER 720 . 90 ! When this happens, the Controller will suspend current activity 100 ! and read registers to determine the cause of the SRQ.
  • Page 319 Status Reporting 190 ! exists. 191 ! 200 PRINT CHR$(12) !Clear screen 210 PRINT TABXY(27,1);"Service Request - Demo Program" 220 ! 230 COM J1407a !Common variable(s) 240 J1407a=705 ! assign variable to default address 250 CALL Init_instr ! Sub to initialize the OmniBER 260 ! 270 CALL Config_regs_14 ! Sub to configure OmniBER regs for SRQ...
  • Page 320 Status Reporting 460 ! 470 ! 480 ! 490 SUB Config_regs_14 500 ! This sub sets up the conditions for generating an SRQ. 510 ! In this case, an SRQ will occur when Signal Loss or FRame Loss 520 ! alarms are detected. 530 ! An SRQ is also set to occur at the end of the Measurement period.
  • Page 321 Status Reporting 670 ! 680 OUTPUT J1407a;":STAT:DATA:PTR 4;NTR 0" 690 ! Set the Transition Filter to pass positive transitions in Bit 2 700 !of the Data Status register. 710 OUTPUT J1407a;":STAT:DATA:ENAB 4" 720 !Enable the SONet data bit in the Data Status register to set 730 !the data summary bit in the Questionable status register 740 ! 750 !
  • Page 322 Status Reporting 940 !Set the transition filter to pass positive transitions in bit 13 950 !of the Operation status register 960 OUTPUT J1407a;":STAT:OPER:ENAB 8192" 970 !Enable the instrument summary bit in Operation status register 980 !to set the Operation register summary bit in the status byte 990 ! 1000 ! 1010 OUTPUT J1407a;"*SRE 200"...
  • Page 323 Status Reporting 1210 CASE 0 ! interrupt from unspecified device 1220 PRINT CHR$(12) !Clear screen 1229 PRINT TABXY(20,10);"The Controller has received an interrupt from" 1230 PRINT TABXY(20,11);"Remove all unspecified equipment from HP-IB" 1231 STOP 1232 ! 1240 CASE 192 ! End of Test Period (rqs[64]+oper[128]) 1250 CALL Read_meas_rslt ! measurement has ended, so read back result.
  • Page 324 Status Reporting 1430 WAIT 2 ! allow time for initialization 1440 OUTPUT J1407a;"*RST" ! set instrument to default settings 1450 WAIT 2 ! allow time for initialization 1460 DISP 1470 SUBEND 1480 ! 1490 ! 1500 SUB Tx_setup 1510 ! 1520 !sub to setup the OmniBER transmitter 1530 COM J1407a !Common variable(s)
  • Page 325 1710 ! 1720 ! 1730 SUB Rx_setup 1740 ! 1750 !sub to setup the OmniBER Receiver 1760 COM J1407a !Common variable(s) 1770 ! Use default 1780 SUBEND 1790 ! 1800 ! 1810 SUB Results_setup 1820 ! 1830 ! Sub to setup the Results page 1840 COM J1407a !Common variable(s) 1850 OUTPUT J1407a;"SENS:DATA:TEL:TEST:TYPE SING"...
  • Page 326 Status Reporting 2110 SUB Read_meas_rslt 2120 ! 2130 ! Sub to read back the OmniBER result 2140 COM J1407a !Common variable(s) 2150 ! 2160 WAIT 2 2170 OUTPUT J1407a;"SENS:DATA? ""ERAT:BIT""" 2180 ! Return the measurement result BER Ratio 2190 ENTER J1407a;Ber_ratio ! Read back bit error results 2200 PRINT TABXY(27,12);...
  • Page 327 Status Reporting 2390 ! 2400 PRINT TABXY(27,10);"SHORT-TERM BER COUNT IS ";Short_rate 2410 WAIT 1 2420 PRINT TABXY(25,10);" " 2430 !PRINT CHR$(12) !Clear screen 2440 UNTIL Forever 2450 SUBEND 2460 ! 2470 ! 2480 SUB Read_Sonet_reg 2490 ! 2500 ! Sub to read the SONet register 2510 COM J1407a !Common variable(s) 2520 !
  • Page 328 Status Reporting 2830 PRINT CHR$(12) !Clear screen 2840 PRINT TABXY(20,10);"A Status Alarm has occurred on the OmniBER " 2843 PRINT TABXY(20,11);"Check instrument Front Panel to see cause " 2860 END SELECT 2870 ! 2871 STOP 2880 ! 2920 ! 2930 SUBEND 5-33 Artisan Technology Group - Quality Instrumentation ...
  • Page 329 Status Reporting 5-34 Artisan Technology Group - Quality Instrumentation ... Guaranteed | (888) 88-SOURCE | www.artisantg.com...

  • Page 330: General Information

    General Information Artisan Technology Group - Quality Instrumentation ... Guaranteed | (888) 88-SOURCE | www.artisantg.com...

  • Page 331: Scpi Overview

    General Information General Information This chapter contains general remote control information. • SCPI Overview - Gives a brief overview of the SCPI Standard. • GPIB Universal Commands - Describes the GPIB Universal commands. SCPI Overview Standard Commands for Programmable Instruments (SCPI) is a standard of the SCPI Consortium that provides guidelines for remote programming commands for instruments.

  • Page 332: Gpib Universal Commands

    Remote Enable (REMOTE) The Remote command instructs the instrument to enter the REMOTE state and be ready to accept instructions via GPIB. When the OmniBER 720 receives this command it illuminates the front panel REMOTE indicator. for example: REMOTE 705 (where 7 is the Bus I/O select code and 05 is the device address).

  • Page 333: Local Lockout (Local Lockout)

    General Information Local Lockout (LOCAL LOCKOUT) It is recommended that the Local Lockout command is sent after the Remote command. This disables the front panel local key preventing the return to local mode and thus any interference to the instrument settings. It should always be preceded by the REMOTE command.

  • Page 334: Application Program Examples

    Application Program Examples Artisan Technology Group - Quality Instrumentation ... Guaranteed | (888) 88-SOURCE | www.artisantg.com...

  • Page 335: Initializing The Omniber 720

    Initializing the OmniBER 720 The following commands can be used to initialize the OmniBER 720. They setup the OmniBER 720 for remote operation, retrieve various instrument details and couple the transmitter to the receiver. Table 7-1 OmniBER 720 Initialization Comment SCPI Command Ref.

  • Page 336: Setup The Omniber 720 Sdh Tx

    Setup the OmniBER 720 SDH Tx The following commands can be used to setup the OmniBER 720 SDH Transmitter to generate a STM-1 Optical signal with a TU-12 Unframed payload. Table 7-2 OmniBER 720 SDH Tx Setup Comment SCPI Command Ref.
  • Page 337 Table 7-2 OmniBER 720 SDH Tx Setup, continued Comment SCPI Command Ref. Set Pattern to 4-19. SOURce:DATA:TELecom:SDH:PAYLoad:PATTern PRBS15 2^15-1 PRBS Set PRBS Polarity 4-21. SOURce:DATA:TELecom:SDH:PRBS:POLarity INVerted to be Inverted Setup B/G Mappings Set Background TUG3 #2 4-24. SOURce:DATA:TELecom:SDH:TUG3:BACKground:PAYLoad: to TU-12 Mapping...

  • Page 338: Setup The Omniber 720 Sdh Rx

    Setup the OmniBER 720 SDH Rx The following commands can be used to setup the OmniBER 720 SDH Receiver to receive a STM-4 Optical signal with a TU-12 Unframed payload. Table 7-3 OmniBER 720 SDH Rx Setup Comment SCPI Command Ref.

  • Page 339: Setup The Omniber 720 Sdh Tx To Add Errors & Alarms7-6

    Setup the OmniBER 720 SDH Tx to add Errors & Alarms The following commands can be used to setup the OmniBER 720 SDH Transmitter to generate errors and alarms using the SDH Test Function. Table 7-4 OmniBER 720 SDH Tx Error & Alarm Add...

  • Page 340: Setup The Omniber 720 Sdh Tx Overhead Bytes

    Setup the OmniBER 720 SDH Tx Overhead Bytes The following commands can be used to setup the OmniBER 720 SDH Transmitter Overhead bytes. It is assumed that a STM-4 signal is selected. Table 7-5 OmniBER 720 SDH Tx Overhead Setup...

  • Page 341: Setup The Omniber 720 Sdh Tx For Overhead Byte

    Setup the OmniBER 720 SDH Tx for Overhead Byte Sequencing The following commands can be used to setup the OmniBER 720 SDH Transmitter to generate an Overhead byte sequence. It is assumed that a STM-4 signal is selected. Table 7-6...

  • Page 342: Perform Omniber 720 Sdh Rx Measurements

    Perform OmniBER 720 SDH Rx Measurements The following commands can be used to setup the OmniBER 720 SDH Receiver to perform B3 measurements. Table 7-7 OmniBER 720 SDH Rx Measurements Comment SCPI Command Ref. Setup Results Timing Control Set Short Term Period 2-19.
  • Page 343 Setup the OmniBER 720 SDH Rx to retrieve Overhead Monitor Bytes The following commands can be used to retrieve the OmniBER 720 SDH Receiver’s Overhead Monitor byte values. Table 7-8 OmniBER 720 SDH Rx Overhead Monitor Comment SCPI Command Ref.

  • Page 344: Setup The Omniber 720 Sdh Rx To Perform Overhead Byte Capture

    Setup the OmniBER 720 SDH Rx to perform Overhead Byte Capture The following commands can be used to setup the OmniBER 720 SDH Receiver to capture selected Overhead bytes. Table 7-9 OmniBER 720 SDH Rx Overhead Byte Capture Comment SCPI Command Ref.

  • Page 345: Setup The Omniber 720 Sonet Tx

    Setup the OmniBER 720 SONET Tx The following commands can be used to setup the OmniBER 720 SONET Transmitter to transmit an OC-12 Optical signal with a VT-2 unframed payload. Table 7-10 OmniBER 720 SONET Tx Setup Comment SCPI Command Ref.

  • Page 346: Setup The Omniber 720 Sonet Tx To Add Errors & Alarms

    Setup the OmniBER 720 SONET Tx to add Errors & Alarms The following commands can be used to setup the OmniBER 720 SONET Transmitter to generate errors and alarms using the SONET Test Function. Table 7-11 OmniBER 720 SONET Tx Error & Alarm Add...

  • Page 347: Setup The Omniber 720 Sonet Tx Overhead Bytes7-14

    Setup the OmniBER 720 SONET Tx Overhead Bytes The following commands can be used to setup the OmniBER 720 SONET Transmitter Overhead bytes. It is assumed that a OC-12 signal is selected. Table 7-12 OmniBER 720 SONET Tx Overhead Setup...

  • Page 348: Setup The Omniber 720 Sonet Tx For Overhead Byte

    Setup the OmniBER 720 SONET Tx for Overhead Byte Sequencing The following commands can be used to setup the OmniBER 720 SONET Transmitter to generate an Overhead byte sequence. It is assumed that an OC-12 signal is selected. Table 7-13...

  • Page 349: Setup The Omniber 720 Sonet Rx

    Setup the OmniBER 720 SONET Rx The following commands can be used to setup the OmniBER 720 SONET Receiver to receive a OC-12 Optical signal with a VT-2 unframed payload. Table 7-14 OmniBER 720 SONET Rx Setup Comment SCPI Command Ref.

  • Page 350: Perform Omniber 720 Sonet Rx Measurements

    Perform OmniBER 720 SONET Rx Measurements The following commands can be used to setup the OmniBER 720 SONET Receiver to perform B3 measurements. Table 7-15 OmniBER 720 SONET Rx Measurements Comment SCPI Command Ref. Setup Results Timing Control Set Short Term Period...

  • Page 351: Setup The Omniber 720 Sonet Rx To Retrieve Overhead Monitor Bytes

    Setup the OmniBER 720 SONET Rx to retrieve Overhead Monitor Bytes The following commands can be used to retrieve the OmniBER 720 SONET Receiver’s Overhead Monitor byte values. Table 7-16 OmniBER 720 SONET Rx Overhead Monitor Comment SCPI Command Ref.

  • Page 352: Scpi Error Messages

    SCPI Error Messages Artisan Technology Group - Quality Instrumentation ... Guaranteed | (888) 88-SOURCE | www.artisantg.com...
  • Page 353 SCPI Error Messages SCPI Error Messages The system-defined error/event numbers are chosen on an enumerated (”1 of N”) basis. The SCPI defined error/event numbers and the error description portions of the ERRor query response are listed here. The first error/event described in each class (for example, −100, −200, −300, −400) is a “generic”...
  • Page 354 SCPI Error Messages IEEE 488.2 < PROGRAM MESSAGE >. Events that generate command errors shall not generate execution errors, device- specific errors, or query errors. −100 Command error This is the generic syntax error for devices that cannot detect more specific errors. This code indicates only that a Command Error as defined in IEEE 488.2, 11.5.1.1.4 has occurred.
  • Page 355 SCPI Error Messages −109 Missing parameter Fewer parameters were received than required for the header; for example, the *ESE common command requires one parameter, so receiving *ESE is not allowed. −110 Command header error An error was detected in the header. This error message should be used when the device cannot detect the more specific errors described for errors −111 through −...
  • Page 356 SCPI Error Messages −123 Exponent too large The magnitude of the exponent was larger than 32000 (see IEEE 488.2, 7.7.2.4.1). −124 Too many digits The mantissa of a decimal numeric data element contained more than 255 digits excluding leading zeros (see IEEE 488.2, 7.7.2.4.1). −128 Numeric data not allowed A legal numeric data element was received, but the device does not accept one in...
  • Page 357 SCPI Error Messages −144 Character data too long The character data element contains more than twelve characters (see IEEE 488.2, 7.7.1.4). −148 Character data not allowed A legal character data element was encountered where prohibited by the device. −150 String data error This error, as well as errors −151 through −159, are generated when parsing a string data element.
  • Page 358 SCPI Error Messages −170 Expression error This error, as well as errors −171 through −179, are generated when parsing an expression data element. This particular error message should be used if the device cannot detect a more specific error. −171 Invalid expression The expression data element was invalid (see IEEE 488.2, 7.7.7.2);...
  • Page 359 SCPI Error Messages − − Execution Errors [ 299, 200 ] An < error/event number > in the range [−299, −200 ] indicates that an error has been detected by the instrument’s execution control block. The occurrence of any error in this class should cause the execution error bit (bit 4) in the event status register (IEEE 488.2, section 11.5.1) to be set.
  • Page 360 SCPI Error Messages −211 Trigger ignored Indicates that a GET, *TRG, or triggering signal was received and recognized by the device but was ignored because of device timing considerations; for example, the device was not ready to respond. Note: a DT0 device always ignores GET and treats *TRG as a Command Error.
  • Page 361 SCPI Error Messages −222 Data out of range Indicates that a legal program data element was parsed but could not be executed because the interpreted value was outside the legal range as defined by the device (see IEEE 488.2, 11.5.1.1.5.) −223 Too much data Indicates that a legal program data element of block, expression, or string type was...
  • Page 362 SCPI Error Messages −251 Missing mass storage Indicates that a legal program command or query could not be executed because of missing mass storage; for example, an option that was not installed. Definition of what constitutes missing mass storage is device-specific. −252 Missing media Indicates that a legal program command or query could not be executed because of a...
  • Page 363 SCPI Error Messages −258 Media protected Indicates that a legal program command or query could not be executed because the media was protected; for example, the write-protect tab on a disk was present. The definition of what constitutes protected media is device-specific. −260 Expression error Indicates that an expression program data element related error occurred.
  • Page 364 SCPI Error Messages −274 Macro parameter error Indicates that the macro definition improperly used a macro parameter placeholder (see IEEE 488.2, 10.7.3). −275 Macro definition too long Indicates that a syntactically legal macro program data sequence could not be executed because the string or block contents were too long for the device to handle (see IEEE 488.2, 10.7.6.1).
  • Page 365 SCPI Error Messages −282 Illegal program name The name used to reference a program was invalid; for example, redefining an existing program, deleting a nonexistent program, or in general, referencing a nonexistent program. −283 Illegal variable name An attempt was made to reference a nonexistent variable in a program. −284 Program currently running Certain operations dealing with programs may be illegal while the program is...
  • Page 366 SCPI Error Messages − − Query Errors [ 399, 300 ] An < error/event number > in the range [−399, −300 ] indicates that the instrument has detected an error which is not a command error, a query error, or an execution error;...
  • Page 367 SCPI Error Messages −313 Calibration memory lost Indicates that nonvolatile calibration data used by the *CAL? command has been lost. −314 Save/Recall memory lost Indicates that the nonvolatile data saved by the *SAV? command has been lost. −315 Configuration memory lost Indicates that the nonvolatile data saved by the device has been lost.
  • Page 368 SCPI Error Messages − − Query Errors [ 499, 400 ] An < error/event number > in the range [−499, −400 ] indicates that the output queue control of the instrument has detected a problem with the message exchange protocol described in IEEE 488.2, chapter 6. The occurrence of any error in this class should cause the query error bit (bit 2) in the event status register (IEEE 488.2, section 11.5.1) to be set.
  • Page 369 SCPI Error Messages −440 Query UNTERMINATED after indefinite response Indicates that a query was received in the same program message after a query requesting an indefinite response was executed (see IEEE 488.2, 6.5.7.5.7.) 8-36 Artisan Technology Group - Quality Instrumentation ... Guaranteed | (888) 88-SOURCE | www.artisantg.com...

  • Page 370: Scpi Backwards Compatibility Differences

    SCPI Backwards Compatibility Differences Artisan Technology Group - Quality Instrumentation ... Guaranteed | (888) 88-SOURCE | www.artisantg.com...
  • Page 371 SCPI Backwards Compatibility Differences SCPI Backwards Compatibility Differences This chapter lists those commands for which it has not been possible to continue from a previous version of instrument software to the current version. SCPI forward compatibility is treated with high priority when instrument features evolve.
  • Page 372 SCPI Backwards Compatibility Differences Once, all three backgrounds could be programmed and only the two in context at any time would be in effect. The other would be masked by the foreground selection. Now, there are only two background channels, called LO and HI. LO can be channel 1 (if the foreground is not in channel 1) or 2.
  • Page 373 :SOURce:DATA:TELecom:SDH:THRumode:PAYLoad:OVERwrite:ENABle <boolean> Tandem Connection Monitoring Feature The introduction of the SDH Tandem Connection Monitoring (TCM) feature has impacted the following areas: • Removal of SONET CV-IEC functionality. This affects CV-IEC error generation [ see :SOURce:DATA:TELecom:SONet:ERRor:TYPE <discrete> ] and the error/ analysis results containing CVIec in the parameter.
  • Page 374 General Index General Index Alarms SDH, 3-39 SONET, 4-36 Application Program Examples , 7-1 Backwards Compatibility , 37 BOOTP Cables Command Errors , 20 Command Reference , 3-2, 4-2 Command Syntax , 2-2 Connecting the LAN to the Instrument Remote Control Interface , 10 Connecting to a LAN Connecting to HP-IB...
  • Page 375 General Index Managing Stores, 2-23 Obtaining End of Measurement Results, 2-31 Retrieving Data for a Single Graph, 2-29 Retrieving Store Data, 2-25 Hints & Tips , 13 HP-IB Communication with the System Controller HP-IB Operating Distances HP-IB Universal Commands , 37 IEEE common capabilities , 2-51 Initialization...
  • Page 376 General Index Query Errors , 33 Receiver Common Commands, 2-12 SDH AU Layer Selection, 3-65 SDH Mapping settings, 3-63 SDH overhead capture, 3-71 SDH Settings, 3-63 SDH Test Function Commands, 3-71 SDH TUG Channel, 3-67 SONET Settings, 4-60 SONET SPE Layer Selection, 4-61 SONET Test Function Commands, 4-67 SONET VT Group, 4-63 Remote Control Commands...
  • Page 377 General Index SONET Pointer Activity, 4-86 SONET REI-P Analysis, 4-81 SONET Service Disruption, 4-85 SONET Short Term, 4-78 SONET Tributary Path CV-V Analysis, 4-82 SONET Tributary Path REI-V Analysis, 4-83 TCM Alarm Seconds, 3-94 TCM Cumulative, 3-83 TCM Errors Analysis, 3-90 TCM OEI Analysis, 3-90 TCM Path IEC Analysis, 3-89 TCM REI Analysis, 3-89...
  • Page 378 General Index Standard Event, 5-5 Status Registers , 14 Status Reporting , 5-2 STATus subsystem , 2-35 Subnet Mask SYSTem Subsystem , 2-37 Tandem Connection Monitoring (TCM) , 3-12, 3-64, 3-95 , 3-83 Terminal Test Timing , 2-14 Thru Mode Backwards Compatibility, 39 to PC Transmitter...
  • Page 379 General Index Index-6 Artisan Technology Group - Quality Instrumentation ... Guaranteed | (888) 88-SOURCE | www.artisantg.com...
  • Page 380 Command Index Command Index *CLS 2-51 *ESE <numeric> 2-51 *ESE? 2-51 *ESR? 2-51 *IDN? 2-51 *LRN? 2-52 *OPC 2-52 *OPT? 2-52 *PSC <numeric> 2-52 *RCL <numeric> 2-53 *RST 2-53 *SAV <numeric> 2-53 *SRE <numeric> 2-53 *SRE? 2-53 *STB? 2-53 *TRG 2-53 *TRG? 2-53 *TST 2-54 *TST? 2-54...
  • Page 381 Command Index :FETCh:SCALar:DATA:TELecom:SDH:TRIButary:POVerhead:SLABel? 3-99 :FETCh:SCALar:DATA:TELecom:SDH:TRIButary:POVerhead? <discrete> 3-99 :FETCh:SCALar:DATA:TELecom:SONet:OVERhead? <numeric>,<numeric>, <discrete> 4-90 :FETCh:SCALar:DATA:TELecom:SONet:POVerhead? <discrete> 4-91 :FETCh:SCALar:DATA:TELecom:SONet:TRIButary:POVerhead:SLABel? 4-91 :FETCh:SCALar:DATA:TELecom:SONet:TRIButary:POVerhead? <discrete> 4-91 :FETCh:STRing:DATA:TELecom:SDH:J0:HEXadecimal? 3-95 :FETCh:STRing:DATA:TELecom:SDH:J0? 3-95 :FETCh:STRing:DATA:TELecom:SDH:J1:HEXadecimal? 3-96 :FETCh:STRing:DATA:TELecom:SDH:J1? 3-95 :FETCh:STRing:DATA:TELecom:SDH:K1? 3-97 :FETCh:STRing:DATA:TELecom:SDH:K2? 3-97 :FETCh:STRing:DATA:TELecom:SDH:S1? 3-97 :FETCh:STRing:DATA:TELecom:SDH:TCM:APID? 3-95 :FETCh:STRing:DATA:TELecom:SDH:TRIButary:J1:HEXadecimal? 3-96 :FETCh:STRing:DATA:TELecom:SDH:TRIButary:J1? 3-96 :FETCh:STRing:DATA:TELecom:SDH:TRIButary:J2:HEXadecimal? 3-97 :FETCh:STRing:DATA:TELecom:SONet:J0:HEXadecimal? 4-88 :FETCh:STRing:DATA:TELecom:SONet:J0? 4-88 :FETCh:STRing:DATA:TELecom:SONet:J1:HEXadecimal? 4-88...
  • Page 382 Command Index :OUTPut:TELecom:OC12:LASer <boolean> 4-5 :OUTPut:TELecom:OC12:RATE <discrete> 4-4 :OUTPut:TELecom:OC12:WAVelength <discrete> 4-5 :OUTPut:TELecom:OC3:LASer <boolean> 4-4 :OUTPut:TELecom:OC3:RATE <discrete> 4-3 :OUTPut:TELecom:OC3:RATE? 4-3 :OUTPut:TELecom:OC3:WAVelength <discrete> 4-3 :OUTPut:TELecom:OC48:LASer <boolean> 4-6 :OUTPut:TELecom:OC48:RATE <discrete> 4-5 :OUTPut:TELecom:OC48:WAVelength <discrete> 4-6 :OUTPut:TELecom:OPT1:LASer <boolean> 3-4 :OUTPut:TELecom:OPT1:RATE <discrete> 3-3 :OUTPut:TELecom:OPT1:WAVelength <discrete> 3-3 :OUTPut:TELecom:OPT16:LASer <boolean>...
  • Page 383 Command Index :SENSe:DATA:TELecom:SDH:PAYLoad:PATTern <discrete> 3-68 :SENSe:DATA:TELecom:SDH:PAYLoad:STRucture <discrete> 3-68 :SENSe:DATA:TELecom:SDH:PAYLoad:TYPE <discrete> 3-68 :SENSe:DATA:TELecom:SDH:PAYLoad:UWORd <string> 3-69 :SENSe:DATA:TELecom:SDH:PGRaph:CINTerval <discrete> 3-75 :SENSe:DATA:TELecom:SDH:PGRaph:PTYPe <discrete> 3-74 :SENSe:DATA:TELecom:SDH:PRBS:POLarity <discrete> 3-69 :SENSe:DATA:TELecom:SDH:PRIMary:TS0 <boolean> 3-66 :SENSe:DATA:TELecom:SDH:TCM:PATH <discrete> 3-64 :SENSe:DATA:TELecom:SDH:TFUNction:TYPE <discrete> 3-71 :SENSe:DATA:TELecom:SDH:TRIButary <numeric> 3-67 :SENSe:DATA:TELecom:SDH:TRIButary:CONCatenate <numeric>,<numeric> 3-70 :SENSe:DATA:TELecom:SDH:TRIButary:MAPPing <discrete> 3-66 :SENSe:DATA:TELecom:SDH:TSCan <boolean>...
  • Page 384 Command Index :SENSe:DATA:TELecom:SONet:MAPPing <discrete> 4-62 :SENSe:DATA:TELecom:SONet:OBERtest:STS1 <numeric> 4-72 :SENSe:DATA:TELecom:SONet:OBERtest:STS3 <discrete> 4-71 :SENSe:DATA:TELecom:SONet:OBERtest:STS3:SELect <numeric> 4-72 :SENSe:DATA:TELecom:SONet:OCAPture <discrete> 4-67 :SENSe:DATA:TELecom:SONet:OCAPture:OHBYte <discrete> 4-68 :SENSe:DATA:TELecom:SONet:OCAPture:STS1 <numeric> 4-68 :SENSe:DATA:TELecom:SONet:OCAPture:STS3:SELect <numeric> 4-68 :SENSe:DATA:TELecom:SONet:OCAPture:TRIGger <discrete> 4-69 :SENSe:DATA:TELecom:SONet:OCAPture:TRIGger:PATTern <string> 4-69 :SENSe:DATA:TELecom:SONet:PAYLoad <discrete> 4-61 :SENSe:DATA:TELecom:SONet:PAYLoad:PATTern <discrete> 4-64 :SENSe:DATA:TELecom:SONet:PAYLoad:STRucture <discrete> 4-64 :SENSe:DATA:TELecom:SONet:PAYLoad:TYPE <discrete>...
  • Page 385 Command Index :SOURce:CLOCk:SDH:FOFFset:OFFSet <numeric><suffix> 3-8 :SOURce:CLOCk:SDH:FORMat <discrete> 3-7 :SOURce:CLOCk:SDH:SOURce <discrete> 3-7 :SOURce:CLOCk:SONet:FOFFset <boolean> 4-9 :SOURce:CLOCk:SONet:FOFFset:OFFSet <numeric><suffix> 4-9 :SOURce:CLOCk:SONet:FORMat <discrete> 4-8 :SOURce:CLOCk:SONet:SOURce <discrete> 4-8 :SOURce:DATA:TELecom:ERRor:BIT <discrete> 2-9 :SOURce:DATA:TELecom:SDH:ALARm <discrete> 3-39 :SOURce:DATA:TELecom:SDH:ALARm:SOOFrame 3-40 :SOURce:DATA:TELecom:SDH:AU:TYPE <discrete> 3-13 :SOURce:DATA:TELecom:SDH:AU3 <numeric> 3-13 :SOURce:DATA:TELecom:SDH:AU3:BACKground <discrete> 3-19 :SOURce:DATA:TELecom:SDH:AU4 <numeric>...
  • Page 386 Command Index :SOURce:DATA:TELecom:SDH:OVERhead:DATA:HEXadecimal <numeric>, <numeric>, <discrete>, <string> 3-23 :SOURce:DATA:TELecom:SDH:OVERhead:DEFault 3-22 :SOURce:DATA:TELecom:SDH:OVERhead:J0 <string> 3-28 :SOURce:DATA:TELecom:SDH:OVERhead:J0:HEXadecimal? 3-28 :SOURce:DATA:TELecom:SDH:OVERhead:J0:PATTern <discrete> 3-28 :SOURce:DATA:TELecom:SDH:OVERhead:SBYTe <discrete> 3-33 :SOURce:DATA:TELecom:SDH:PAYLoad <discrete> 3-14 :SOURce:DATA:TELecom:SDH:PAYLoad:OFFSet <numeric> 3-18 :SOURce:DATA:TELecom:SDH:PAYLoad:PATTern <discrete> 3-17 :SOURce:DATA:TELecom:SDH:PAYLoad:STRucture <discrete> 3-16 :SOURce:DATA:TELecom:SDH:PAYLoad:TYPE <discrete> 3-16 :SOURce:DATA:TELecom:SDH:PAYLoad:UWORd <string> 3-17 :SOURce:DATA:TELecom:SDH:PDHPayload:ERRor:RATE <discrete> 3-37 :SOURce:DATA:TELecom:SDH:PDHPayload:ERRor:RATE:USER <numeric>...
  • Page 387 Command Index :SOURce:DATA:TELecom:SDH:PRBS:POLarity <discrete> 3-17 :SOURce:DATA:TELecom:SDH:PRIMary:BACKground:PAYLoad:PATTern <discrete> 3-20 :SOURce:DATA:TELecom:SDH:SEQuence <discrete> 3-48 :SOURce:DATA:TELecom:SDH:SEQuence:CHANnel:SELect <numeric> 3-49 :SOURce:DATA:TELecom:SDH:SEQuence:COLumn <numeric> 3-49 :SOURce:DATA:TELecom:SDH:SEQuence:DATA <discrete>,<string> 3-50 :SOURce:DATA:TELecom:SDH:SEQuence:FCOunt <numeric>, <numeric> 3-50 :SOURce:DATA:TELecom:SDH:SEQuence:MODE <discrete> 3-48 :SOURce:DATA:TELecom:SDH:SEQuence:OHBYte <discrete> 3-48 :SOURce:DATA:TELecom:SDH:SEQuence:ORDer <discrete>, <discrete>, <discrete>, <discrete>, <discrete> 3-50 :SOURce:DATA:TELecom:SDH:STESt:BLENgth <numeric> 3-51 :SOURce:DATA:TELecom:SDH:STESt:SPATtern <discrete>...
  • Page 388 Command Index :SOURce:DATA:TELecom:SDH:TUG3:BACKground:PAYLoad:PATTern:UWORd <numeric> <string> 3- :SOURce:DATA:TELecom:SONet:ALARm <discrete> 4-36 :SOURce:DATA:TELecom:SONet:ALARm:SSEFrame 4-37 :SOURce:DATA:TELecom:SONet:APSMessages:ARCHitecture <discrete> 4-50 :SOURce:DATA:TELecom:SONet:APSMessages:BRIDge <string> 4-50 :SOURce:DATA:TELecom:SONet:APSMessages:CHANnel <numeric> 4-48 :SOURce:DATA:TELecom:SONet:APSMessages:DNODe <string> 4-52 :SOURce:DATA:TELecom:SONet:APSMessages:DOWNload 4-54 :SOURce:DATA:TELecom:SONet:APSMessages:PCODe <discrete> 4-53 :SOURce:DATA:TELecom:SONet:APSMessages:RCODe <discrete> 4-51 :SOURce:DATA:TELecom:SONet:APSMessages:REQuest <discrete> 4-47 :SOURce:DATA:TELecom:SONet:APSMessages:REServed <numeric> 4-50 :SOURce:DATA:TELecom:SONet:APSMessages:SCODe <discrete> 4-53 :SOURce:DATA:TELecom:SONet:APSMessages:SNODe <string>...
  • Page 389 Command Index :SOURce:DATA:TELecom:SONet:PAYLoad:UWORd <string> 4-17 :SOURce:DATA:TELecom:SONet:PDHPayload:ERRor:RATE <discrete> 4-33 :SOURce:DATA:TELecom:SONet:PDHPayload:ERRor:RATE:USER <numeric> 4-34 :SOURce:DATA:TELecom:SONet:PDHPayload:ERRor:TYPE <discrete> 4-33 :SOURce:DATA:TELecom:SONet:POINter <discrete> 4-37 :SOURce:DATA:TELecom:SONet:POINter:ACTion 4-38 :SOURce:DATA:TELecom:SONet:POINter:ADJust 4-40 :SOURce:DATA:TELecom:SONet:POINter:DIRection <discrete> 4-37 :SOURce:DATA:TELecom:SONet:POINter:IDECrement <numeric> 4-38 :SOURce:DATA:TELecom:SONet:POINter:NPOinter <discrete> 4-39 :SOURce:DATA:TELecom:SONet:POINter:OFFSet <discrete> 4-40 :SOURce:DATA:TELecom:SONet:POINter:OFFSet:RATE <numeric>, <suffix> 4-40 :SOURce:DATA:TELecom:SONet:POINter:T1105 <discrete> 4-41 :SOURce:DATA:TELecom:SONet:POINter:T1105:INTerval <numeric>, <suffix>...
  • Page 390 Command Index :SOURce:DATA:TELecom:SONet:SPE:TYPE <discrete> 4-13 :SOURce:DATA:TELecom:SONet:STESt:BLENgth <numeric> 4-47 :SOURce:DATA:TELecom:SONet:STESt:SPATtern <discrete> 4-46 :SOURce:DATA:TELecom:SONet:STS1 <numeric> 4-13 :SOURce:DATA:TELecom:SONet:STS1:BACKground <discrete> 4-19 :SOURce:DATA:TELecom:SONet:STS12c <numeric> 4-13 :SOURce:DATA:TELecom:SONet:STS12c BACKground <discrete> 4-20 :SOURce:DATA:TELecom:SONet:STS3 <numeric> 4-12 :SOURce:DATA:TELecom:SONet:STS3:BACKground <discrete> 4-19 :SOURce:DATA:TELecom:SONet:TFUNction:TYPE <discrete> 4-31 :SOURce:DATA:TELecom:SONet:THRumode <discrete> 4-10 :SOURce:DATA:TELecom:SONet:THRumode:COVerwrite <boolean> 4-11 :SOURce:DATA:TELecom:SONet:THRumode:PAYLoad:OVERwrite:ENABle <boolean> 4-11 :SOURce:DATA:TELecom:SONet:TRIButary <numeric>...
  • Page 391 Command Index :SYSTem:DISK:CD <string> 2-49 :SYSTem:DISK:DIRectory:CREate <filename> 2-48 :SYSTem:DISK:DIRectory? <extension>,<format> 2-48 :SYSTem:DISK:FILE:COPY:CNF <to>,<store>,<directory>,<filename>,<overwrite> 2-46 :SYSTem:DISK:FILE:COPY:SMG <store>,<directory>,<filename>,<overwrite> 2-47 :SYSTem:DISK:FILE:COPY:SMG:FORMat <type> 2-47 :SYSTem:DISK:FILE:DELete <filename> 2-48 :SYSTem:DISK:FILE:REName <from_filename>,<to_dir>, <filename>, <overwrite> 2-48 :SYSTem:DISK:FORMat 2-45 :SYSTem:DISK:FREE? 2-49 :SYSTem:DISK:LABel <string> 2-45 :SYSTem:DISK:PWD? 2-49 :SYSTem:DISK:RECall <extension>,<filename>,<confirm> 2-46 :SYSTem:DISK:SAVE <extension>,<filename>,<overwrite>...
  • Page 392 Command Index :SYSTem:VERSion? 2-39 :SYSTem:WINDow<type> 2-37 SOURce:DATA:TELecom:SONet:THRumode:PAYLoad:OVERwrite <discrete> 4-10 Command Index-13 Artisan Technology Group - Quality Instrumentation ... Guaranteed | (888) 88-SOURCE | www.artisantg.com...
  • Page 393 Command Index Command Index-14 Artisan Technology Group - Quality Instrumentation ... Guaranteed | (888) 88-SOURCE | www.artisantg.com...
  • Page 394 Sales and Service Offices An up-to-date list of Agilent Offices is available through the Agilent Technologies Website at URL: http://www.agilent.com Artisan Technology Group - Quality Instrumentation ... Guaranteed | (888) 88-SOURCE | www.artisantg.com...
  • Page 395 In This Book This book contains the information required for remote control of the OmniBER 720. Printed in U.K. 12/00 J1407-90013 Artisan Technology Group - Quality Instrumentation ... Guaranteed | (888) 88-SOURCE | www.artisantg.com...
  • Page 396 Artisan Technology Group is your source for quality new and certified-used/pre-owned equipment SERVICE CENTER REPAIRS WE BUY USED EQUIPMENT • FAST SHIPPING AND DELIVERY Experienced engineers and technicians on staff Sell your excess, underutilized, and idle used equipment at our full-service, in-house repair center We also offer credit for buy-backs and trade-ins •...

Table of Contents