The programming commands are identical, regardless of the type of remote control interface
that is used.
The ANT-20 must be switched to remote control mode manually. In remote control mode,
manual control of the ANT-20 is not possible.
To set the ANT-20 to remote control mode, follow these steps
ANT-20, ANT-20E with
Windows 3.11:⇒ Double-click on the “Remote” icon in the “ANT-20” group in the
“Program Manager” window.
Windows95:1. Enable remote control mode using the taskbar:
“Start/ANT-20/Remote On”.
2. Double-click on the “ANT-20” icon on the desktop
– or –
use the taskbar: “Start/ANT-20/ANT-20”.
To switch back to normal manual control, follow these steps
ANT-20, ANT-20E with
Windows 3.11:⇒ Double-click on the “Remote Disable” icon in the “ANT-20”
group in the “Program Manager” window.
Windows95:1. Disable remote control mode using the taskbar:
“Start/ANT-20/Remote Off”.
2. Double-click on the “ANT-20” icon on the desktop
– or –
use the taskbar: “Start/ANT-20/ANT-20”.
IntroductionI-1
Page 26
1 ANT-20, ANT-20E, ANT-20SEANT-20 (Mainframe)
From the viewpoint of remote control, each measuring module in the ANT-20 is a fully remotecontrollable instrument with its own SCPI command tree, status reporting system and common
command set.
The measuring module to be controlled is selected using the command
MODule:SELect <module_name> (see Sec. 1.1.2).
The instrument’s display shows which measuring modules exist and which one is selected for
remote control.
A built-in monitor function can be switched on for debugging purposes (see Sec. 1.1.3).
To change the type of the remote control interface and/or its accompanying configuration
parameters, the batch file remote.bat must be edited.
ANT-20, ANT-20E with
Windows 3.11:1. Double-click on the “Remote Configuration” icon in the
“ANT-20” group in the “Program Manager” window to edit the
remote.bat file.
2. Follow the on-screen instructions.
Windows95:1. Click on the “Remote Configuration” icon via taskbar: “Start/
ANT-20/Remote Configuration” to edit the remote.bat file.
2. Follow the on-screen instructions.
1.1.2Module selection
The remote control interface of the ANT-20 supports multiple internal mea suring modules. The
module selection provides a mechanism to select one of these measuring modules for remote
control.
This command selects the measuring module specified by <module_na me> for remote contro l
and deselects all others. All subsequent commands (including commands in subsequent
program messages) are passed to the selected measuring module. All other measuring
modules are unavailable for programming until selected.
<module_name>:
BASIC:Selects BASIC Module
JITTER:Selects JITTER Module for bit rates up to STM4/OC12 (extension slot)
JITT16:Selects JITTER Module for bit rates of STM16/OC48 (extension slot)
BAG:Selects BAG Module (Broadband Analyzer/Generator)
(not available for ABT-20)
(not available for ABT-20)
1
[no query]
Note: • This command has no query form.
• After power-on, the BASIC measuring module is selected.
• If the MODule:SELect <module_name> command is required in a program
message, it must be the first (or the only) command in that program message.
I-2Introduction
Page 27
ANT-20 (Mainframe)1 ANT-20, ANT-20E, ANT-20SE
1.1.3Monitor mode
A monitor function can be switched on or off in remote control mode. If it is switched on, the
instrument displays all messages sent to and from the instrument, corresponding to each
operating step performed.
1.1.4LabWindows/CVI driver
A LabWindows/CVI instrument driver is available for each measuring module.
Instrument drivers reduce application program development time and simplify instrument
control by eliminating the need to learn the complex programming commands fo r each
measuring module.
1.2GPIB Remote Control interface
This section describes the GPIB Remote Control interface for applications using the ANT- 20 as
a remote controlled instrument.
Other applications using the ANT-20 as a GPIB controller for controlling external instruments
are also possible (e.g. running the WG CA TS Test Executive BN 3045 on the ANT-20 to control
the ANT-20 measurement hardware plus external instruments).
To allow both these mutually exclusive operating modes to b e used, the GPIB Remote Cont rol
interface and installation comprises all the software required for both operating modes.
1.2.1Items included
The Remote Control GPIB (PCMCIA) Option BN 3035/92.10 comprises:
ANT-20, ANT-20E with
Windows 3.11:• PCMCIA GPIB card including PCMCIA to GPIB cable
Windows95:• PCMCIA GPIB card including PCMCIA to GPIB cable
(2 meters)
• CardWare User’s Manual (Award Software Inc.)
• Distribution disk: CardWare Version 2.0 (Award Software Inc.)
• Installation disks: ANT-20 PCMCIA System (configured
CardWare 2.0),
ANT-20 GPIB Remote Control (includes NI-488.2)
• ANT-20 GPIB (NI-488.2) for Windows 3.x
• Operating Manual: Remote Control
• Brochure “SCPI and IEEE 488, Programmer‘s Introduction”
(2 meters)
• Installation disks: ANT-20 GPIB Remote Control for Windows95
(includes NI-488.2M)
• Operating Manual: Remote Control
• Brochure “SCPI and IEEE 488, Programmer‘s Introduction”
IntroductionI-3
Page 28
1 ANT-20, ANT-20E, ANT-20SEANT-20 (Mainframe)
1.2.2Installation
1.2.2.1Overview
The PCMCIA GPIB interface from National Instruments Corp. (NI) is used with the NI-488.2/
NI-488.2M software for GPIB Remote Control.
For ANT-20 with Windows 3.11 only:
• The NI-488.2 software requires standardized PCMCIA system software with Socket and
Card Services (version 2.0 or higher) to be installed.
• A software called CardWare (written by Award Software Inc.) is used as PCMCIA system
software. It can also be used with a wide variety of other PCMCIA cards.
• The CardWare software contained on the installation disk is already configured for use with
the ANT-20.
1.2.2.2Software installation
Software installation under Windows 3.11
If you ordered the Remote Control GPIB Option BN 3035/92.10 together with your ANT-20, the
required software packages are already installed on the ANT-20 and the icons “Remote”,
“Remote Disable” and “Remote Configuration” are shown in the “ANT-20” group in th e “Program
Manager” window.
Note: A release code is required to enable the Remote Control GPIB Option.
For detailed information contact your nearest Wavetek Wandel Goltermann Service
Center. The addresses are listed at the end of this manual.
When contacting the Service Center, always quote:
• The serial number of the ANT-20
• The version number of the ANT-20 software package
If you ordered the Remote Control GPIB Option BN 3035/92.10 separately, install the software
packages as follows:
Installing the PCMCIA System software
1. Start or return to Windows.
2. Insert the ANT-20 PCMCIA System installation disk into drive A:.
3. Choose “Run ...” from the “File” menu in the “Program Manager” wind ow and
type the following command into the dialog box:
A:\setup
Confirm with “OK”.
4. After complete installation exit Windows, remove the installation disk from drive A:, and
reboot the ANT-20.
Installing the GPIB Remote Control software
1. Start or return to Windows.
2. Insert the ANT-20 GPIB Remote Control installation disk into drive A:.
I-4Introduction
Page 29
ANT-20 (Mainframe)1 ANT-20, ANT-20E, ANT-20SE
3. Choose “Run ...” from the “File” menu in the “Program Manager” window and
type the following command into the dialog box:
A:\setup
Confirm with “OK”.
4. After complete installation exit Windows, remove the installation disk from drive A:, and
reboot the ANT-20.
Installing the ANT-20 Remote Control software
1. Start or return to Windows
2. Choose “Run...” from the “File” menu in the “Program Manager” window and
type the following command into the dialog box:
C:\ANT20.SUP\DISK1\setup.exe
Confirm with “OK”.
3. Follow the on-screen instructions to install the ANT-20 Remote Control.
4. After complete installation exit Windows, and reboot the ANT-20.
After this installation procedure, the ANT-20 can be set to remote control mode by doubleclicking on the “Remote” icon in the “ANT-20” group in the “Program Manager” window.
Installing the GPIB (NI-488.2) for Windows 3.x
This software is required for applications that use the ANT-20 as a GPIB controller for
controlling external instruments (e.g. for running the WG CATS Test Executive BN 3045 on the
ANT-20 to control the ANT-20 measurement hardware plus external instruments).
1. Start or return to Windows.
2. Insert the installation disk ANT-20 GPIB (NI-488.2) for Windows 3.x into drive A:.
3. Choose “Run...” from the “File” menu in the “Program Manager” window and type the
following command into the dialog box:
A:\setup
Confirm with “OK”.
4. Follow the on-screen instructions to complete the installation.
5. After complete installation exit Windows, remove the installation disk from drive A:, and
reboot the ANT-20.
After this installation procedure, you can access the “NI-488.2 PCMCIA GPIB So ftware” g ro up
in the “Program Manager” window.
To view or modify the NI-488.2 software configuration, double-click the “GPIB” icon from the
“Control Panel” in the “Main” group of the “Program Manager” window.
Software installation under Windows95
If you ordered the Remote Control GPIB Option BN 3035/92.10 together with your ANT-20, the
required software packages are already installed on the ANT-20 and the icons “Remote On”,
“Remote Off” and “Remote Configuration” ar e shown in the Windows95 file folder “ANT-20”.
Note: A release code is required to enable the Remote Control GPIB Option.
For detailed information contact your nearest Wavetek Wandel Goltermann Service
Center. The addresses are listed at the end of this manual.
When contacting the Service Center, always qu o te :
• The serial number of the ANT-20
• The version number of the ANT-20 software package
Verify the PCMCIA GPIB card installation as described in section “Verify the PCMCIA GPIB
card installation” below.
IntroductionI-5
Page 30
1 ANT-20, ANT-20E, ANT-20SEANT-20 (Mainframe)
If you ordered the Remote Control GPIB Option BN 3035/92.10 separately, install the software
packages as follows:
Installing the GPIB Remote Control software
1. Start or return to Windows95.
2. Insert the ANT-20 GPIB Remote Control for Windows95 installation disk 1 into drive A:.
3. Click the Windows95 “Start” button, choose “Run ...” and
type the following command into the dialog box:
A:\setup
Confirm with “OK”.
4. Follow the on-screen instructions during the installation procedure and en ter
C:\Tmp\Gpib
as GPIB distribution directory.
5. After completion, click the Windows95 “Start” button, choose “Run...” and
type the following command into the dialog box:
C:\Tmp\Gpib\gpib9513.exe
Confirm with “OK”.
6. Follow the on-screen instructions during the setup procedure and use the default selection
for components to install (all components selected).
7. After complete installation:
– Shut down the ANT-20.
– Remove the installation disk from drive A:.
– Insert the PCMCIA GPIB card into a free PCMCIA slot.
– Reboot the ANT-20.
Enable support for DOS applications as described below (by default, DOS sup port is disabled):
1. Return to Windows95, click the Windows95
“Start” button, choose “Settings” and then
choose “Control Panel” from the submenu.
In the “Control Panel” window, double-click the “System” icon.
2. In the “Device Manager” tab of the “System Properties” window,
choose “View devices by type”,
click on the “National Instruments GPIB Interfaces” icon in the list and then
click on the “Properties” button.
3. In the “General” tab in the “National Instruments GPIB Interfaces Pr opertie s” window se lect
the checkbox “Enable Support for DOS GPIB Applications” and confirm with “OK”.
4. Reboot the ANT-20.
Verify the PCMCIA GPIB card installation
1. The PCMCIA GPIB card must be in the slot!
2. Click the Windows95 “Start” button, choose “Settings” and then
choose “Control Panel” from the submenu.
In the “Control Panel” window, double-click the “System” icon.
3. In the “Device Manager” tab of the “System Properties” window,
choose “View devices by type”,
double-click the “National Instruments GPIB Interfaces” icon in the list and then
double-click “PCMCIA GPIB” in the sublist.
4. In the “GPIB Settings” tab of the “PCMCIA GPIB Properties” window, the entry for
“Interface Name” must be “GPIB0”. If it is not, change it to “GPIB0”.
5. Deactivate the “System Controller” checkbox.
(All other parameters are properly set by starting the ANT-20 remote control mode after
completion of the installation procedure.)
6. Confirm with “OK”.
I-6Introduction
Page 31
ANT-20 (Mainframe)1 ANT-20, ANT-20E, ANT-20SE
Installing the ANT-20 Remote Control software
1. Start or return to Windows95.
2. Click the Windows95 “Start” button,
choose “Run...” and type the following command into the dialog box:
C:\ANT20.SUP\DISK1\setup.exe
Confirm with “OK”.
3. Follow the on-screen instructions to install the ANT-20 Remote Control and select only the
“Remote Control Software” as component to install.
The following patch installation described in steps 4, 5 and 6 is only required for ANT-20
software versions less or equal 7.0. It has no effect on versions greater than 7.0.
4. Insert the ANT-20 GPIB Remote Control for Windows95 installation disk 3 into drive A:.
5. Click on the Windows95 “Start” button, choose “Run...” and
type the following command into the dialog box:
A:\setup
Confirm with “OK”.
6. Follow the on-screen instructions.
After completion, remove the installation disk from drive A:.
Note: Only for ANT-20 software versions less or equal 7.0:
If there is any need to execute C:\ANT20.SUP\DISK1\setup.exe (with the component
“Remote Control Software” selected) at a later time again, the above described patch
installation (steps 4, 5 and 6) must also be executed again.
7. Exit Windows95 and reboot the AN T- 20 .
After this installation procedure, you can enable the remote control mode by using the taskbar:
1. “Start/ANT-20/Remote On”.
2. Then double-click on the “ANT-20” icon on the desktop or
use the taskbar: “Start/ANT-20/ANT-20”.
1.2.2.3Hardware installation
1. Insert the PCMCIA GPIB card into a free PCMCIA socket the same way you insert a disk into
a floppy drive.
The PCMCIA GPIB has no jumpers or switches to set, and you do not need to power down
the ANT-20 when you insert or remove the card.
2. Connect the PCMCIA GPIB cable to the PCMCIA GPIB card.
IntroductionI-7
Page 32
1 ANT-20, ANT-20E, ANT-20SEANT-20 (Mainframe)
1.2.3Connecting to GPIB
The GPIB Remote Control interface is equipped with a standar d 24-way con nector con forming
to IEEE 488.1.
GPIB cables of various lengths are available for connecting the ANT-20 to other instr uments
and to the bus controller:
• 1.2 m long: Part number K 420
• 2.0 m long: Part number K 421
Note: • The total length of GPIB cable must not exceed 2 meters x the number of
instruments in the interface system.
• Up to 15 instruments can be connected to the interface system. The maximum cable
run used to connect a group of instruments is 20 meters. For more info rmation re fer
to the IEEE 488.1 standard.
• Longer distances can be bridged using interface couplers (2-wire or 4-wire
connections, if necessary with suitable modems).
1.2.4Device address
Each instrument in the interface system must have a unique address to allow the controller to
access each one individually.
The ANT-20 address can be changed by editing the remote.bat batch file.
Any address in the range 0 to 30 can be selected.
ANT-20, ANT-20E with
Windows 3.11:1. Double-click on the “Remote Configuration” icon in the
“ANT-20” group in the “Program Manager” window to edit the
remote.bat file.
2. Follow the on-screen instructions.
Windows95:1. Click on the “Remote Configuration” icon via taskbar: “Start/
ANT-20/Remote Configuration” to edit the remote.bat file.
2. Follow the on-screen instructions.
Note: Make sure that a given address is used only once within the interface system. The
controller address is reserved for the controller.
AH1Acceptor HandshakeComplete capability
T8TalkerNo Talk Only capability
No Serial Poll capability
L4ListenerNo Listen Only capability
SR0Service RequestNo capability
RL0Remote/LocalNo capability
PP0Parallel PollNo capability
DC1Device ClearComplete capability
DT0Device TriggerNo capability
C0ControllerNo capability
Table I-2Interface functions conforming to the IEEE 488.1 standard
1.2.5.2Device Clear
When the IEEE 488 interface message Device Clear ( DCL) o r Selected Device Clea r (SDC) is
sent to the ANT-20, a device clear message is routed to all internal measuring modules,
regardless of whether they are selected or deselected.
The device clear message initializes remote control of the instrument and ensures that a
subsequently sent program message will be accepted and processed.
No instrument initialization is performed by DCL or SDC. To initialize the instrument, select
every measuring module and send the reset command
*RST (MODule:SELect <module_name>; *RST).
1.3V.24/V.28 (RS 232) Remote Control interface
1.3.1Items included
The Remote Control V.24/RS 232 Option BN 3035/91.01 consists of
• Remote Control Operating Manual
• Brochure “SCPI and IEEE 488, Programmer’s Introduction”
1.3.2Installation
For remote control via RS 232 the built-in serial port (COM1) of the embedded PC-AT is used.
IntroductionI-9
Page 34
1 ANT-20, ANT-20E, ANT-20SEANT-20 (Mainframe)
1.3.2.1Software installation
Software installation under Windows 3.11
If you ordered the Remote Control V.24/V.28 ( RS 232) Option BN 3035/91.01 together with your
ANT-20, the required software package is already installed on the ANT-20 and the icons
“Remote”, “Remote Disable” and “Remote Configuration” are shown in the “ANT-20” group in
the “Program Manager” window.
Note: A release code is required to enable the Rem ote Control V.24/V.28 (RS 23 2) Option.
For detailed information contact your nearest Wavetek Wandel Goltermann Se rvice
Center. The addresses are listed at the end of this manual.
When contacting the Service Center, always quote:
• The serial number of the ANT-20
• The version number of the ANT-20 software package
If you ordered the Remote Control V.24/V.28 ( RS 232) Option BN 3035/91.01 separately, install
the software package as follows:
Installing the ANT-20 Remote Control software
1. Start or return to Windows
2. Choose “Run...” from the “File” menu in the “Program Manager” window and
type the following command into the dialog box:
C:\ANT20.SUP\DISK1\setup.exe
Confirm with “OK”.
3. Follow the on-screen instructions to install the ANT-20 Remote Control.
4. After complete installation exit Windows, and reboot the ANT-20.
After this installation procedure, the ANT-20 can be set to remote control mode by doubleclicking on the “Remote” icon in the “ANT-20” group in the “Program Manager” window.
Software installation under Windows95
If you ordered the Remote Control V.24/V.28 ( RS 232) Option BN 3035/91.01 together with your
ANT-20, the required software package is already installed on the ANT-20 and the icons
“Remote On”, “Remote Off” and “Remote Configuration” are shown in the Windows95 file folder
“ANT-20”.
Note: A release code is required to enable the Rem ote Control V.24/V.28 (RS 23 2) Option.
For detailed information contact your nearest Wavetek Wandel Goltermann Se rvice
Center. The addresses are listed at the end of this manual.
When contacting the Service Center, always quote:
• The serial number of the ANT-20
• The version number of the ANT-20 software package
I-10Introduction
Page 35
ANT-20 (Mainframe)1 ANT-20, ANT-20E, ANT-20SE
If you ordered the Remote Control V.24/V.28 (RS 232) Option BN 3035/91.01 separately, install
the software package as follows:
Installing the ANT-20 Remote Control software
1. Start or return to Windows95.
2. Click the Windows95 “Start” button,
choose “Run...” and type the following command into the dialog box:
C:\ANT20.SUP\DISK1\setup.exe
Confirm with “OK”.
3. Follow the on-screen instructions to install the ANT-20 Remote Control.
4. After complete installation exit Windows95, and reboot the ANT-20.
After this installation procedure, you can enable the remote control mode by using the taskbar:
1. “Start/ANT-20/Remote On”.
2. Then double-click on the “ANT-20” icon on the desktop or
use the taskbar: “Start/ANT-20/ANT-20”.
1.3.3Connecting to V.24/V.28 (RS 232)
The interface connector (serial port COM1) is a 9-way SUB-D male connector.
PinITU-T
V.24
3103D1BATXDTransmitted dataO
2104D2BBRXDReceived dataI
7105S2CARTSRequest to sendO
8106M2CBCTSReady for sending/Clear to sendI
6107M1CCDSRDate set readyI
5102E2ABSGNDSignal ground or common return1109M5CFDCDData channel received line signal
The connection of an ANT-20 to a PC is shown below. Both the ANT-20 and the PC function as
Data Terminal Equipment (DTE):
Fig. I-19-way connection
Fig. I-225-way connection
An appropriate cable with both 9-way and 25-way SUB-D female connectors on each end is
available:
Part number K 764 (3.0 m long)
I-12Introduction
Page 37
ANT-20 (Mainframe)1 ANT-20, ANT-20E, ANT-20SE
1.3.4Transmission parameters
The baud rate can be changed by editing the remote.bat batch file.
ANT-20, ANT-20E with
Windows 3.11:1. Double-click on the “Remote Configuration” icon in the
“ANT-20” group in the “Program Manager” window to edit the
remote.bat file.
2. Follow the on-screen instructions.
Windows95:1. Click on the “Remote Configuration” icon via taskbar: “Start/
ANT-20/Remote Configuration” to edit the remote.bat file.
2. Follow the on-screen instructions.
The following baud rates can be selected:
• 1200 bit/s
• 2400 bit/s
• 4800 bit/s
• 9600 bit/s
• 19200 bit/s
• 38400 bit/s
• 57600 bit/s
The interface operates in full-duplex (FDX) mode.
The other transmission parameters are fixed and cannot be changed:
ParameterSetting
ParityNone
Number of stop bits per character1
Number of data bits per character8
Flow controlHardware handshake by control lines RTS/CTS
There is no functional equivalence to the GPIB interface functions Service Request and Serial
Poll.
However, the GPIB interface function Device Clear is simulated by a BREAK signal
(see Sec. 1.3.5.2,Page I-14).
1.3.5.2Device Clear
When the BREAK signal is sent to the ANT-20, a device clear message is routed to all internal
measuring modules, regardless of whether they are selected or desel ected.
BREAK is detected when the RXD input is at positive voltage (i.e. logical 0 or SPACE) for the
entire character frame including the stop bit.
The device clear message initializes remote control of the instrument and ensures that a
subsequently sent program message will be accepted and processed.
No instrument initialization is performed by the device clear message.
To initialize the instrument, select every measuring module and send the reset command *RST
(MODule:SELect <module_name>; *RST).
I-14Introduction
Page 39
ANT-20 (Mainframe)2 DominoCOM ANT-20
2DominoCOM ANT-20
2.1General information
2.1.1Items included
The delivery includes the following items relating to remote control:
• PCMCIA GPIB card including PCMCIA to GPIB cable (2 meters)
• Configuration disk: DominoCOM ANT-20 Remote Control
• Remote Control Operating Manual
• Brochure “SCPI and IEEE 488, Programmer‘s Introduction”
For DominoCOM ANT-20 with Windows 3.11 only:
• CardWare User´s Manual (Award Software Inc.)
• Distribution disk: CardWare Version 2.0 (Award Software Inc.)
2.1.2Overview
The DominoCOM ANT-20 can be remotely controlled using the
• IEEE 488 (IEC 625) interface, often referred to as GPIB
– or –
• V.24/V.28 (RS 232) interface
The programming commands are identical, regardless of the type of remote control interface
that is used.
From the viewpoint of remote control, each measuring module in the DominoCOM ANT-20 is a
fully remote-controllable instrument with its own SCPI command tree, status reporting system
and common command set.
The measuring module to be controlled is selected using the command
MODule:SELect <module_name> (see Sec. 2.1.5,Page I-17).
Refer to Sec. 2.1.3,Page I-15 for changing the type of remote control interface and/or its
accompanying configuration parameters.
DominoCOM ANT-20 can operate in the ANT-20 mode with the use of an external monitor,
keyboard and mouse. Refer to Sec. 2.1.4,Page I-16, for detailed information.
2.1.3Changing the configuration
To change the type of remote control interface and/or its accompanying configuration
parameters, follow these steps
1. Edit the remote.bat batch file (on the configuration disk) by using an external PC.
Refer to the readme.txt file (on the configuration disk) for detailed editing information.
2. Insert the configuration disk into drive A: of the DominoCOM ANT-20 and reboot the
DominoCOM ANT-20 (switch power off, then power on ).
IntroductionI-15
Page 40
2 DominoCOM ANT-20ANT-20 (Mainframe)
2.1.4ANT-20 mode
By connecting an external monitor, keyboard and mouse to the embedded PC-AT, the
DominoCOM ANT-20 can be operated in the same way as an ANT-20.
The display shows which measuring modules exist and which one is selected for remote
control.
A monitor function can be switched on for debugging purposes during remote control mode that
displays all messages sent to and from the DominoCOM ANT-20, corresponding to each
operating step performed.
Edit the remote.bat batch file (for changing the type of the remote control interface and/or its
accompanying configuration parameters) as follows:
DominoCOM ANT-20 with
Windows 3.11:1. Double-click on the “Remote Configuration” icon in the “ANT-20”
group in the “Program Manager” window.
2. Follow the on-screen instructions.
Windows95:1. Click on the “Remote Configuration” icon via taskbar: “Start/
ANT-20/Remote Configuration”.
2. Follow the on-screen instructions.
To leave remote control mode and enter normal manual control, follow these steps
DominoCOM ANT-20 with
Windows 3.11:⇒ Double-click on the “Remote Disable” icon in the “ANT-20”
group in the “Program Manager” window.
Windows95:1. Disable remote mode using the taskbar: “Start/ANT-20/Remote
Off”.
2. Then double-click on the “ANT-20” icon on the desktop or
use the taskbar: “Start/ANT-20/ANT-20”.
To switch back to remote control mode, follow these steps
DominoCOM ANT-20 with
Windows 3.11:⇒ Double-click on the “Remote” icon in the “ANT-20” group in the
“Program Manager” window.
Windows95:1. Enable remote mode using the taskbar: “Start/ANT-20/Remote
On”.
2. Then double-click on the “ANT-20” icon on the desktop or
use the taskbar: “Start/ANT-20/ANT-20”.
I-16Introduction
Page 41
ANT-20 (Mainframe)2 DominoCOM ANT-20
2.1.5Module selection
The remote control interface of the DominoCOM ANT-20 supports multiple internal measuring
modules. The module selection provides a mechanism to select one of these measuring
modules for remote control.
This command selects the measuring module specified by <module_name> for remo te co ntrol
and deselects all others. All subsequent commands (including commands in subsequent
program messages) are passed to the selected measuring module. All other measuring
modules are unavailable for programming until selected.
<module_name>:
BASIC:Selects BASIC Module
JITTER:Selects JITTER Module for bit rates up to STM4/OC12 (extension slot)
(not available for ABT-20)
JITT16:Selects JITTER Module for bit rates of STM16/OC48 (extension slot)
(not available for ABT-20)
BAG:Selects BAG Module (Broadband Analyzer/Generator)
Note: • This command has no query form.
• After power-on, the BASIC measuring module is selected.
• If the MODule:SELect <module_name> command is required in a program
message, it must be the first (or the only) command in that program message.
1
[no query]
2.1.6LabWindows/CVI driver
A LabWindows/CVI instrument driver is available for each measuring module.
Instrument drivers reduce application program development time and simplify instrument
control by eliminating the need to learn the complex programming commands fo r each
measuring module.
2.2GPIB Remote Control interface
This section describes the GPIB Remote Control interface for applications using the
DominoCOM ANT-20 as a remote controlled instrument.
Applications using the DominoCOM ANT-20 as a GPIB Controller for controlling external
instruments are also possible (e.g. running the WG CATS Test Executive BN 3045 on the
DominoCOM ANT-20 to control the DominoCOM ANT-20 measurement hardware plus external
instruments).
To allow both these mutually exclusive operating modes to b e used, the GPIB Remote Cont rol
interface and installation comprises all the software required for both operating modes.
IntroductionI-17
Page 42
2 DominoCOM ANT-20ANT-20 (Mainframe)
2.2.1Installation
2.2.1.1Overview
The PCMCIA GPIB interface from National Instruments Corp. (NI) is used with the NI-488.2/
NI-488.2M software for GPIB Remote Control. This software is already installed on the
DominoCOM ANT-20.
For DominoCOM ANT-20 with Windows 3.11 only:
• The NI-488.2 software requires standardized PCMCIA system software with Socket and
Card Services (version 2.0 or higher) to be installed.
• A software called CardWare (written by Award Software Inc.) is used as PCMCIA system
software. It can also be used with a wide variety of other PCMCIA cards.
• The CardWare software is already installed on the DominoCOM ANT-20 and suitably
configured.
2.2.1.2Configuration for GPIB
Set the configuration parameters:
• Interface type GPIB
• Device address
by editing the remote.bat batch file.
Refer to Sec. 2.1.3,Page I-15, for detailed information.
Each instrument in the interface system must have an unique addre ss to allow the controller to
access each one individually.
Any address in the range 0 to 30 can be selected.
Note: Make sure that a given address is used only once within the interface system. The
controller address is reserved for the controller.
2.2.1.3Hardware installation
1. Insert the PCMCIA GPIB card into a free PCMCIA socket the same way you insert a disk into
a floppy drive.
The PCMCIA GPIB has no jumpers or switches to set, and you do not need to power do wn
the DominoCOM ANT-20 when you insert or remove the card.
2. Connect the PCMCIA GPIB cable to the PCMCIA GPIB card.
I-18Introduction
Page 43
ANT-20 (Mainframe)2 DominoCOM ANT-20
2.2.2Connecting to GPIB
The GPIB Remote Control interface is equipped with a stand ard 24- way connector conforming
to IEEE 488.1.
GPIB cables of various lengths are available for connecting the DominoCOM ANT-20 to other
instruments and to the bus controller:
• 1.2 m long: Part number K 420
• 2.0 m long: Part number K 421
Note: • The total length of GPIB cable must not exceed 2 meters x the number of
instruments in the interface system.
• Up to 15 instruments can be connected to the interface system. The m aximum cable
run used to connect a group of instruments is 20 meters. For more informatio n re fer
to the IEEE 488.1 standard.
• Longer distances can be bridged using interface couplers (2-wire or 4-wire
connections, if necessary with suitable modems).
Table I-6Interface functions conforming to the IEEE 488.1 standard
No Serial Poll capability
IntroductionI-19
Page 44
2 DominoCOM ANT-20ANT-20 (Mainframe)
2.2.3.2Device Clear
When the IEEE 488 interface message Device Clear ( DCL ) or Sele cted Device Clear (SDC) is
sent to the DominoCOM ANT-20, a device clear message is routed to all internal measuring
modules, regardless of whether they are selected or deselected.
The device clear message initializes remote control of the instrument and ensures that a
subsequently sent program message will be accepted and processed.
No instrument initialization is performed by DCL or SDC.
To initialize the instrument, select every measuring module and send the reset command
*RST (MODule:SELect <module_name>; *RST).
I-20Introduction
Page 45
ANT-20 (Mainframe)2 DominoCOM ANT-20
2.3V.24/V.28 (RS 232) Remote Control interface
2.3.1Installation
2.3.1.1Overview
For remote control via RS 232 the built-in serial port (COM1) of the embedded PC-AT is used.
2.3.1.2Configuration for V.24/V.28 (RS 232)
Set the configuration parameters:
• Interface type V.24/V.28 (RS 232)
• Baud rate
by editing the remote.bat batch file.
Refer to Sec. 2.1.3,Page I-15.
The following baud rates can be selected:
• 1200 bit/s
• 2400 bit/s
• 4800 bit/s
• 9600 bit/s
• 19200 bit/s
• 38400 bit/s
• 57600 bit/s
The interface operates in full-duplex (FDX) mode.
The other transmission parameters are fixed and cannot be changed:
ParameterSetting
ParityNone
Number of stop bits per character1
Number of data bits per character8
Flow controlHardware handshake by control lines RTS/CTS
The interface connector (serial port COM1) is a 9-way SUB-D male connector.
PinITU-T
V.24
3103D1BATXDTransmitted dataO
2104D2BBRXDReceived dataI
7105S2CARTSRequest to sendO
8106M2CBCTSReady for sending/Clear to sendI
6107M1CCDSRDate set readyI
5102E2ABSGNDSignal ground or common return1109M5CFDCDData channel received line signal
The connection of a DominoCOM ANT-20 to a PC is shown below.
Both the DominoCOM ANT-20 and the PC function as Data Terminal Equipment (DTE):
Fig. I-39-way connection
Fig. I-425-way connection
An appropriate cable with both 9-way and 25-way SUB-D female connectors on each end is
available:
Part number K 764 (3.0 m long)
IntroductionI-23
Page 48
2 DominoCOM ANT-20ANT-20 (Mainframe)
2.3.3Interface functions
2.3.3.1Overview
There is no functional equivalence to the GPIB interface functions Service Request and Serial
Poll.
However, the GPIB interface function Device Clear is simulated by a BREAK signal
(see Sec. 2.3.3.2,Page I-24).
2.3.3.2Device Clear
When the BREAK signal is sent to the DominoCOM ANT-20, a device clear message is routed
to all internal measuring modules, regardless of whether they are selected or deselected.
BREAK is detected when the RXD input is at positive voltage (i.e. logical 0 or SPACE) for the
entire character frame including the stop bit.
The device clear message initializes remote control of the instrument and ensures that a
subsequently sent program message will be accepted and processed.
No instrument initialization is performed by the device clear message.
To initialize the instrument, select every measuring module and send the reset command
*RST (MODule:SELect <module_name>; *RST).
I-24Introduction
Page 49
ANT-20 (Mainframe)3 TX/RX SCPI block diagram
3TX/RX SCPI block diagram
V.11
Basic module
Through 4
ext.Mod.
SOURCE:
JITTER
Jitter mod.
[25]
Ref.Clock Input
[23]
Jitter Input
Ref.Clock Output
[22]
[21]
V.11
SOURCE:
DATA:TEL
ATM
from RX
SOURCE:
DATA:TEL
Aux.Clock
Synthesizer
SDH
PDH
*chain
TX-Trib.
RX-Trib.
OUTPUT:TEL
:OPTIC
STM-1/4
OUTPUT:TEL
:LINE
1.5-155M
OUTPUT:TEL
:AUX
1.5-140M
optic
[18]
Line
bal
[13]
Aux.
[11]
[15]
TX
electrical
optic
OUTPUT:
TEL
STM-16
Through 16
SENSE:
JITTER
Jitter dem.
Dem.
Ref.
[24]
[26]
SENSE:
DATA:TEL:
ATM
Jitter Output
Trigger
Ref.2048
TSE
TX Frame
TX Pattern
Through 1
OUTPUT:
TRIGGER
SENSE:
DATA:TEL:
PDH
SENSE:
DATA:TEL:
SDH
V.11
INPUT:TEL
:AUX
1.5-140M
INPUT:TEL
:LINE
1.5-155M
INPUT:TEL
:OPTIC
STM-1/4
Through 4
INPUT:
STM-16
Aux.
[10]
bal
[12]
Line
[15]
optic
unbal.
STM-1/4
TEL
optic
electrical
RX
[17]
[16]
Fig. I-5TX/RX SCPI block diagram
IntroductionI-25
Page 50
4 Operating informationANT-20 (Mainframe)
4Operating information
This chapter gives the programmer some basic information which should make it easier to
program this device.
• Program messages are executed in the order they are received from the controller.
However, the execution of any command does not start b efore the PMT (Progra m Message
Terminator <NL>) or any other sequential command is received. This gives full flexibility in
controlling the device without the need to worry about the dependencies between individual
commands, because the settings of coupled commands received within a single message
are checked after the whole message is received.
• Commands are treated as “overlapped commands” except where otherwise noted.
Overlapped commands allow the next command to be executed before the preceding
command has finished execution. This gives better performance and makes it possible to
change some settings while a measurement is running, for example. You can use the
common command *WAI to force sequential operation whenever you need to.
• Any error detected within a program message is written into the error queue. You can read
entries out of the error queue using the SYST:ERR? command. Any program message is
read from the input buffer and parsed as far as possible to detect potential errors.
Nevertheless, the device setting may be undefined after any error.
• Queries are not allowed to have side effects. Thus, queries of commands set in the same
program message will return the old command setting.
• Note that using the SCPI short form of the commands (capital letters) will reduce operational
overhead and can increase your system performance.
• The input buffer size is 4096 bytes (4 kB).
• The output buffer size is 8192 bytes (8 kB). Requesting a response with more than
8192 bytes would cause a query error.
I-26Introduction
Page 51
ANT-20 (Mainframe)5 Command hierarchy
5Command hierarchy
5.1Introduction
This section is intended to give programmers an overview of the hierarchical relationships
between the commands.
Each command is independent. However, since the parameters are related, each par ameter
has a priority between 1 and 4, with 1 being the highest and 4 the lowest.
If a higher-priority parameter is modified, lower-priority param eters may be automatically
modified as well. This automatic mechanism assures logically consistent instrument settings
that comply with standards, thereby avoiding error messages. It also simplifies programming
since many settings are made automatically and do not need to be programmed.
The priorities come into play when individual commands are sent to the instrument. However , if
multiple commands are grouped in a command sequence, the priorities are inactive within the
command sequence.
Note:Send individual commands in order of decreasing priority so that settings are not
overwritten by subsequent commands.
If you transmit command sequences, be careful to pro vid e consistent data since the
instrument does not make automatic corrections in this case.
5.2Command hierarchy (generator)
Remote CommandPriority
*RST on page R-51
:SOUR:DATA[:TEL]:STAN on page R-2542
:SOUR:MODE on page R-2553
:SOUR:DATA[:TEL]:NEL on page R-864
:SOUR:DATA[:TEL]:SOUR:DIV on page R-2525
:SOUR:DATA[:TEL]:SDH:RATE on page R-2136
:SOUR:DATA[:TEL]:SOUR[:SOCK] on page R-2537
:SOUR:DATA[:TEL]:SDH:MAPP on page R-1688
:SOUR:DATA[:TEL]:SDH:MAPP:CONC[:MODE] on page R-1709
:SOUR:DATA[:TEL]:SDH:MAPP:TUFL on page R-1729
:SOUR:DATA[:TEL]:SDH:PAYL:TYPE on page R-19510
:SOUR:DATA[:TEL]:SDH:TRIB:MAPP on page R-23511
:SOUR:DA TA[:TEL]:SDH:CHAN on page R-14412
:SOUR:DATA[:TEL]:SDH:STMN:CHAN on page R-21712
all other commands of node :SOUR:DATA[:TEL]:SDH on page R-135 ff13
Table I-9Command hierarchy (generator)
IntroductionI-27
Page 52
5 Command hierarchyANT-20 (Mainframe)
Remote CommandPriority
:SOUR:DATA[:TEL]:PDH:RATE on page R-12912
:SOUR:DATA[:TEL]:PDH:FRAM on page R-10413
:SOUR:DATA[:TEL]:PDH:PAYL:TYPE on page R-12814
:SOUR:DATA[:TEL]:PDH:M2:FRAM on page R-10715
:SOUR:DATA[:TEL]:PDH:M34:FTYP on page R-11615
:SOUR:DATA[:TEL]:PDH:M140:FTYP on page R-12315
:SOUR:DATA[:TEL]:PDH:DS1:FRAM on page R-9615
:SOUR:DATA[:TEL]:PDH:DS3:FRAM on page R-10115
all other commands of node :SOUR:DATA[:TEL]:PDH on page R-91 ff16
:SOUR:DATA[:TEL]:ATM:NINT on page R-7417
:SOUR:DATA[:TEL]:ATM:PAYL:TYPE on page R-7518
:SOUR:DATA[:TEL]:ATM:HEAD:CLP on page R-70 and other commands of
the ...:HEAD node.
:SOUR:DATA[:TEL]:ATM:DIST:TYPE on page R-6620
all other commands of node :SOUR:DATA[:TEL]:ATM on page R-58 ff21
all other transmitter commands22
Table I-9Command hierarchy (generator)
5.3Command hierarchy (receiver)
Remote CommandPriority
*RST on page R-51
[:SENS]:DATA[:TEL]:STAN on page R-3782
[:SENS]:MODE on page R-4063
[:SENS]:DATA[:TEL]:SDH:RATE on page R-3706
[:SENS]:DATA[:TEL]:SENS on page R-3787
[:SENS]:DATA[:TEL]:SDH:MAPP on page R-3578
19
(continued)
[:SENS]:DATA[:TEL]:SDH:MAPP:CONC[:MODE] on page R-3589
[:SENS]:DATA[:TEL]:SDH:MAPP:TUFL on page R-3609
[:SENS]:DATA[:TEL]:SDH:PAYL:TYPE on page R-36510
[:SENS]:DATA[:TEL]:SDH:TRIB:MAPP on page R-37511
[:SENS]:DATA[:TEL]:SDH:CHAN on page R-35312
[:SENS]:DATA[:TEL]:SDH:STMN:CHAN on page R-37212
Table I-10Command hierarchy (receiver)
I-28Introduction
Page 53
ANT-20 (Mainframe)5 Command hierarchy
Remote CommandPriority
all other commands of node [:SENS]:DATA[:TEL]:SDH on page R-352 ff13
[:SENS]:DATA[:TEL]:PDH:RATE on page R-35012
[:SENS]:DATA[:TEL]:PDH:FRAM on page R-33413
[:SENS]:DATA[:TEL]:PDH:PAYL:TYPE on page R-34914
[:SENS]:DATA[:TEL]:PDH:M2:FRAM on page R-33615
[:SENS]:DATA[:TEL]:PDH:M34:FTYP on page R-34015
[:SENS]:DATA[:TEL]:PDH:M140:FTYP on page R-34515
[:SENS]:DATA[:TEL]:PDH:DS1:FRAM on page R-33115
[:SENS]:DATA[:TEL]:PDH:DS3:FRAM on page R-33315
all other commands of node [:SENS]:DATA[:TEL]:PDH on page R-330 ff16
[:SENS]:DATA[:TEL]:ATM:NINT on page R-32017
[:SENS]:DATA[:TEL]:ATM:VCI on page R-32318
[:SENS]:DATA[:TEL]:A TM:VCI:FILT on page R-32318
[:SENS]:DATA[:TEL]:A TM:VPI on page R-32418
[:SENS]:DATA[:TEL]:A TM:PAYL:TYPE on page R-32119
all other commands of node [:SENS]:DATA[:TEL]:ATM on page R-316 ff20
all other receiver commands21
Table I-10Command hierarchy (rec eiver)
(continued)
IntroductionI-29
Page 54
6 Programming examplesANT-20 (Mainframe)
6Programming examples
This chapter contains some short sample programs to help you get familiar with the remote
control operation of this device.
6.1Notation
The sample programs are written in C programming language style using the fun ctions “clear” ,
“write”, “wait” and “read” as placeholders for the different functions used by programmers
depending on their programing language.
Note: A “NOEND” as the second parameter of the function “write” indicates that the same
program message is continued in the next line without sending a program message
terminator (PMT). An “END” indicates that a program message terminat or (PMT) should
be sent.
Multiple commands can be appended into one “big” program message using NOEND.
Checking of coupled parameters and the ex ecution of all commands starts after the PMT
or any sequential command is received.
6.2Example 1 (PDH measurement)
This sample program performs a simple 2 Mbit/s FAS (frame alignment signal) measurement.
Note that the default device setting after a *RST command is a 2 Mbit/s framed PDH signal.
// Send device clear to reset input buffer
// and output queue.
// Initialize communication protocol.
clear();
// Clear status register and error queue.
write (“*CLS”, END);
// Reset device to standard setting.
// TX and RX set to 2 Mbit/s (E1) framed signal.
write (“*RST”, END);
// Select 2 Mbit/s FAS error
// count and alarm ratio as requested results.
write (“SENS:FUNC:ON ’ARAT:PDH:M2:FAS’”,END);
write (“SENS:FUNC:ON ’ECO:PDH:M2:FAS’",END);
// Set measurement duration to 1 sec.
write (“SENS:SWE:TIME 1 s”, END);
// start measurement.
write (“INIT”, END);
// Wait until measurement has finished and
// place results into the output queue.
write (“*WAI;SENS:DATA:FIN?”,END);
// Read response from device.
read();
I-30Introduction
Page 55
ANT-20 (Mainframe)6 Programming examples
6.3Example 2 (SDH C4 measurement)
This sample program performs a STM1 155 Mbit/s measurement using a C4 mapping which
includes a PDH 140 Mbit/s signal.
// Send device clear to reset input buffer
// and output queue.
// Initialize communication protocol.
clear();
// Clear status register and error queue.
write (“*CLS”, END);
// Reset device to standard setting.
// TX and RX set to 2 Mbit/s (E1) framed signal.
write (“*RST”, END);
// Set transmitter to SDH mode.
write (“:SOUR:MODE SDH;” ,NOEND);
// Set transmitter bit rate to STM1/STS3 (is default).
// Set transmitter bit rate to STS1.
write (“:SOUR:DATA:SDH:RATE STS1;”,NOEND);
// Set STS1SPE mapping.
write (“:SOUR:DATA:SDH:MAPP STS1SPE;”,NOEND);
// select payload type (can be ATM or PATT (bulk) or PDH (DSn)|
write (“:SOUR:DATA:SDH:PAYL:TYPE PDH;”,NOEND);
write (“:SOUR:DATA:PDH:RATE DS3,DS3;”,END);
// Set receiver to synchronous mode (SONET).
write (“:SENS:DATA:STAN ANSI;” , END);
write (“:SENS:MODE SDH;”,NOEND);
// Set receiver bit rate to STM1 (is default).
write (“:SENS:DATA:SDH:RATE STS1;”,NOEND);
// Set STS1SPE mapping.
write (“:SENS:DATA:SDH:MAPP STS1SPE;”,NOEND);
// select payload type (can be ATM or PATT (bulk) or PDH (DSn)|
write (“:SENS:DATA:SDH:PAYL:TYPE PDH;”,NOEND);
write (“:SENS:DATA:PDH:RATE DS3,DS3;”,END);
// read and compare results
write (“:sens:data:act?;”, END)
read();
test int 50 “test status of CST:SIGN”
test mask 0 245 “LOS !”
test int 53 “test status of CST:PDH2 result (Defects DS1)”
test mask 2 253 “Defect not LOF1.5”
test int 100 “test status ECO:TSE result”
test float 0 “bit error not 0”
test int 130 “test status ECO:CODE result”
test float 0 “BPV not 0”
IntroductionI-35
Page 60
7 Release NotesANT-20 (Mainframe)
7Release Notes
This section contains a summary of all additions included from So ftware Release V6.6 onwards.
7.1New commands
Summary of all new commands included from Software Release V6.6 onwards
:SOUR:DATA[:TEL]:PDH:DS3:FEAC[:ALAR] on page R-98
:SOUR:DATA[:TEL]:PDH:DS3:FEAC:LOOP[:TYPE] on page R-99
:SOUR:DATA[:TEL]:PDH:DS3:FEAC:LOOP:CODE on page R-100
:SOUR:DATA[:TEL]:SDH:ERR:FLEN on page R-162
:SOUR:DATA[:TEL]:SDH:MAPP:OFFS on page R-169
:SOUR:DATA[:TEL]:SDH:OVER:SEQ[:ACT] on page R-186
:SOUR:DATA[:TEL]:SDH:OVER:SEQ:MNP:DATA on page R-187
:SOUR:DATA[:TEL]:SDH:OVER:SEQ:POS:POH on page R-189
:SOUR:DATA[:TEL]:SDH:OVER:SEQ:POS:SOH | TOH on page R-190
:SOUR:DATA[:TEL]:SDH:OVER:SEQ:TYPE on page R-192
[:SENS]:DATA[:TEL]:PDH:DS3:FEAC:LOOP:RES on page R-332
[:SENS]:DATA[:TEL]:SDH:OVER:TCM:RES on page R-364
:FETC:SCAL[:DATA][:TEL][:SDH]:OVER? on page R-423
:FETC:STR[:DATA][:TEL][:SDH]:TCMonitoring:TRACe? on page R-432
Summary of all new commands included from Software Release V7.0 onwards
:SOUR:DATA[:TEL]:SDH:MAPP:CONC:CSIZ on page R-171
:SOUR:DATA[:TEL]:SDH:POIN:SSB on page R-207
:SOUR:DATA[:TEL]:SDH:OVER:SEQ:TCM:DATA on page R-191
:SOUR:DATA[:TEL]:SDH:OVER:SEQ:TCM:DATA:BLOC on page R-193
:INP:CLOC:WAND[:STAT] on page R-257
[:SENS]:DATA[:TEL]:SDH:MAPP:CONC:CSIZ on page R-359
Summary of all new commands included from Software Release V7.1 onwards
:OUTP[:TEL]:OPT3[:STAT] on page R-50
:SOUR:DATA[:TEL]:SDH:OVER[i]:DATA on page R-175
:SOUR:DATA[:TEL]:SDH:OVER[i]:DATA:BLOC on page R-177
:SOUR:DATA[:TEL]:SDH:OVER[i]:PRES on page R-179
:SOUR:DATA[:TEL]:SDH:OVER[i]:RDAT on page R-182
:SOUR:DATA[:TEL]:SDH:OVER[i]:RDAT:BLOC on page R-183
[:SENS]:DATA[:TEL]:ANAL:M2101:ALL on page R-304
[:SENS]:DATA[:TEL]:ANAL:M2101:ALL? on page R-304
[:SENS]:DATA[:TEL]:ANAL:M2101:BISO:BBE? on page R-304
[:SENS]:DATA[:TEL]:ANAL:M2101:BISO:ES? on page R-305
[:SENS]:DATA[:TEL]:ANAL:M2101:BISO:MULT on page R-305
[:SENS]:DATA[:TEL]:ANAL:M2101:BISO:MULT? on page R-305
[:SENS]:DATA[:TEL]:ANAL:M2101:BISO:SEP? on page R-306
[:SENS]:DATA[:TEL]:ANAL:M2101:BISO:SES? on page R-306
[:SENS]:DATA[:TEL]:ANAL:M2101:EVAL on page R-306
[:SENS]:DATA[:TEL]:ANAL:M2101:EVAL? on page R-307
[:SENS]:DATA[:TEL]:ANAL:M2101:S1:BBE? on page R-307
[:SENS]:DATA[:TEL]:ANAL:M2101:S1:ES? on page R-307
[:SENS]:DATA[:TEL]:ANAL:M2101:S1:SEP? on page R-308
I-36Introduction
Page 61
ANT-20 (Mainframe)7 Release Notes
[:SENS]:DATA[:TEL]:ANAL:M2101:S1:SES? on page R-308
[:SENS]:DATA[:TEL]:ANAL:M2101:S2:BBE? on page R-308
[:SENS]:DATA[:TEL]:ANAL:M2101:S2:ES? on page R-308
[:SENS]:DATA[:TEL]:ANAL:M2101:S2:SEP? on page R-309
[:SENS]:DATA[:TEL]:ANAL:M2101:S2:SES? on page R-309
[:SENS]:DATA[:TEL]:ANAL:M2101:UAS:LIM[:STAT] on page R-310
[:SENS]:DATA[:TEL]:ANAL:M2101:UAS:LIM[:STAT]? on page R-310
[:SENS]:DATA[:TEL]:ANAL:M2101:UAS:LIM:UPP on page R-310
[:SENS]:DATA[:TEL]:ANAL:M2101:UAS:LIM:UPP? on page R-311
[:SENS]:DATA[:TEL]:ANAL:M2101:UAS:MODE on page R-311
[:SENS]:DATA[:TEL]:ANAL:M2101:UAS:MODE? on page R-311
[:SENS]:DATA[:TEL]:LED:AUL[:STAT] on page R-325
[:SENS]:DATA[:TEL]:LED:TUL[:STAT] on page R-326
:[SENS]:DATA[:TEL]:SDH:OVER:TCM:TYPE on page R-364
Summary of all new commands included from Software Release V7.2 onwards
:SOUR:DATA[:TEL]:SDH:STSN:CHAN on page R-218
:SOUR:DATA[:TEL]:SDH:STSV:CHAN on page R-219
[:SENS]:DATA[:TEL]:SDH:STSN:CHAN on page R-373
[:SENS]:DATA[:TEL]:SDH:STSV:CHAN on page R-374
[:SENS]:DATA[:TEL]:ANAL:G828:ALL on page R-291
[:SENS]:DATA[:TEL]:ANAL:G828:ALL? on page R-291
[:SENS]:DATA[:TEL]:ANAL:G828:EVAL on page R-291
[:SENS]:DATA[:TEL]:ANAL:G828:EVAL? on page R-292
[:SENS]:DATA[:TEL]:ANAL:G828:SEPI[:STAT] on page R-292
[:SENS]:DATA[:TEL]:ANAL:G828:SEPI[:STAT]? on page R-292
[:SENS]:DATA[:TEL]:ANAL:G828:SES:THR on page R-292
[:SENS]:DATA[:TEL]:ANAL:G828:SES:THR? on page R-293
[:SENS]:DATA[:TEL]:ANAL:G828:SES:THR:AUTO on page R-293
[:SENS]:DATA[:TEL]:ANAL:G828:SES:THR:AUTO? on page R-293
[:SENS]:DATA[:TEL]:ANAL:G828:UAS:LIM[:STAT] on page R-294
[:SENS]:DATA[:TEL]:ANAL:G828:UAS:LIM[:STAT]? on page R-294
[:SENS]:DATA[:TEL]:ANAL:G828:UAS:LIM:UPP on page R-294
[:SENS]:DATA[:TEL]:ANAL:G828:UAS:LIM:UPP? on page R-294
[:SENS]:DATA[:TEL]:ANAL:G828:UAS:MODE on page R-295
[:SENS]:DATA[:TEL]:ANAL:G826:UAS:MODE? on page R-290
[:SENS]:DATA[:TEL]:ANAL:G829:EVAL on page R-295
[:SENS]:DATA[:TEL]:ANAL:G829:EVAL? on page R-296
[:SENS]:DATA[:TEL]:ANAL:G829:SES:THR on page R-296
[:SENS]:DATA[:TEL]:ANAL:G829:SES:THR? on page R-296
[:SENS]:DATA[:TEL]:ANAL:G829:SES:THR:AUTO on page R-297
[:SENS]:DATA[:TEL]:ANAL:G829:SES:THR:AUTO? on page R-297
[:SENS]:DATA[:TEL]:ANAL:M2101:SEPI[:STAT] on page R-309
[:SENS]:DATA[:TEL]:ANAL:M2101:SEPI[:STAT]? on page R-309
[:SENS]:DATA[:TEL]:ANAL:M2101:VERSion on page R-311
[:SENS]:DATA[:TEL]:ANAL:M2101:VERSion? on page R-312
IntroductionI-37
Page 62
7 Release NotesANT-20 (Mainframe)
7.2Changed commands
Summary of all changed commands included from Software Release V6.6 onwards
:TRIG2[:SEQ]:LOG:SOUR on page R-30 <source> TCMF added
:SOUR:DATA[:TEL]:PAYL:PA TT on page R-88 <pattern> IQRSS20 added
:SOUR:DATA[:TEL]:PDH:ALAR[:MODE] on page R-92 <alarm> FEAC added
:SOUR:DATA[:TEL]:PDH:ERR[:MODE] on page R-102 <error> CP45 added
:SOUR:DATA[:TEL]:SDH:ERR[:MODE] on page R-165 <mode> PER added
[:SENS]:DATA[:TEL]:PAYL:PATT on page R-328 <pattern> IQRSS20 added
[:SENS]:DATA:EVEN:NUMB? on page R-267 added new codes for the event memory
[:SENS]:FUNC[:ON] on page R-381 added new results for previous commands:
• Result IDs for :SENS:DATA and :SENS:FUNC commands on page R-382
• Result IDs for SDH/SONET results on page R-384
• Alarm field “CSTatus:SDH2”/“HSTatus:SDH2” on page R-274
• Alarm field “CSTatus:PDH2”/“HSTatus:PDH2” on page R-279
• Result field “CSTatus:TCMonitoring”/“HSTatus:TCMonitoring” on page R-281
• Result field “CSTatus:FEAC:LOOP:ON”/“CSTatus:FEAC:LOOP:OFF”/
“HSTatus:FEAC:LOOP:ON”/“HSTatus:FEAC:LOOP:OFF” on page R-280
Summary of all changed commands included from Software Release V7.0 onwards
:SOUR:DATA[:TEL]:SDH:ALAR[:MODE] on page R-136 <alarm> AISC5 ... 16 and
LOPC5 ... 16 added
:SOUR:DATA[:TEL]:SDH:STMN:BCH on page R-216 mode EQUipped added
:SOUR:DATA[:TEL]:SDH:OVER:SEQ[: ACT] on page R-186 mode FSEQ added
An index [i] has been introduced for the STM-16/STS-48 SOH byte s in the following commands:
:SOUR:DATA[: TEL]:SDH:OVER[i]:DA T A on page R-175
:SOUR:DATA[: TEL]:SDH:OVER[i]:DA T A:BLOC on page R-177
:SOUR:DATA[: TEL]:SDH:OVER[i]:PRES on page R-179
:SOUR:DATA[: TEL]:SDH:OVER[i]:RDA T on page R-182
:SOUR:DATA[: TEL]:SDH:OVER[i]:RDA T:BLOC on page R-183
:OUTP:CLOC[1]:DIV[:STAT] on page R-35: the exact settings ON | OFF are explained only in
conjunction with the Jitter Module and O.171/O.172 options.
Summary of all changed commands included from Software Release V7.1 onwards
:STAT:QUES:COND?onpageR-16
:SOUR:CLOC:FOFF:OFFS on page R-53
:SOUR:DATA[:TEL]:SDH:ALAR:FLEN on page R-135
:SOUR:DATA[:TEL]:SDH:ERR:FLEN on page R-162
:SOUR:DATA[:TEL]:SDH:ERR[:MODE] on page R-165
:SOUR:DATA[:TEL]:SDH:RATE on page R-213
:OUTP[:TEL]:OPT2:WLEN on page R-49
[:SENS]:DATA[:TEL]:ANAL[:TYPE] on page R-314
[:SENS]:DATA[:TEL]:ANAL[:TYPE]? on page R-314
:FETC[:ARR][:DATA][:TEL][:SDH]:OVER? on page R-414
:FETC[:ARR][:DATA][:TEL][:SDH]:OVER:PART[i]? on page R-415
:FETC[:ARR][:DATA][:TEL][:SDH]:OVER:CPARt[i]? on page R-416
:FETC:SCAL[:DATA][:TEL][:SDH]:OVER? on page R-423
:FETC:SCAL[:DATA][:TEL][:SDH]:OVER:PART[i]? on page R-425
:FETC:SCAL[:DATA][:TEL][:SDH]:OVER:CPARt[i]? on page R-426
I-38Introduction
Page 63
ANT-20 (Mainframe)7 Release Notes
Summary of all changed commands included from Software Release V7.2 onwards
:SOUR:DATA[:TEL]:SDH:CHAN on page R-144
:SOUR:DATA[:TEL]:SDH:STMN:CHAN on page R-217
[:SENS]:DATA[:TEL]:SDH:CHAN on page R-353
[:SENS]:DATA[:TEL]:SDH:STMN:CHAN on page R-372
[:SENS]:DATA[:TEL]:ANAL:G826:EVAL on page R-286
[:SENS]:DATA[:TEL]:ANAL:G826:EVAL? on page R-287
IntroductionI-39
Page 64
7 Release NotesANT-20 (Mainframe)
Notes:
I-40Introduction
Page 65
ANT-20 (Mainframe)*CAL?
Command reference
1Common commands
Instrument behavior is based on:
IEEE Standard Codes, Formats, ANSI/IEEE Std 488.2-1992.
The common commands that are implemented are given below in alphabe tical
order.
*CAL?
Instrument calibration query.
ParameterNone
CommentsRequests the instrument to perform an internal self calibration and to return the
result. The response indicates whether or not the instrument completed the
calibration without error. A value of 0 indicates that the calibration has been
completed successfully.
The instrument signals the need for calibration using the bit 8 of the “questionable
status register” (see Status register structure on page R-11).
See also “WG SCPI and IEEE488 Programmer’s Introduction” for more details.
Note: The instrument is set to the reset state (as set by a *RST command) after a
*CAL? command.
Response0:Calibration has been completed successfully
-1:Calibration failed
-2:Calibration failed (warm-up time not reached)
-3:calibration failed (EEPROM write error)
-10:Calibration failed (calibration currently not possible)
Example*CAL?
Response: 0
Related commandsNone
Common commandsR-1
Page 66
*CLSANT-20 (Mainframe)
*CLS
Clear Status Command.
ParameterNone
CommentsClears the data accumulated in the registers. Causes a partial initialization of
remote control. The masks contained in the registers (ENABLE Register) are not
altered (see also SCPI Syntax and Style Section 4.1.3.2).
The following actions take place:
• Clearing of all EVENT registers in the status register structure.
• Clearing of the error queue and all other que ues which affect the status register
structure.
• Interruption of an *OPC synchronization possibly underway, without a 1 being
entered into bit 0 of the standard event status register.
• Interruption of an *OPC? synchronization possibly underway, without a 1 be ing
entered into the output queue.
See also “WG SCPI and IEEE488 Programmer’s Introduction” for more details.
Example*CLS
Related commands*RST on page R-5
*ESE
*ESE <mask> Standard Event Status Enable Command.
ParameterNameTypeRangeDefault
masknumeric
CommentsSets the mask for the ESR register.
See also “WG SCPI and IEEE488 Programmer’s Introduction” for more details.
Example*ESE 32
Related commands*ESR? on page R-3
*ESE?onpageR-3
#H00 - #HFF or
#B00000000 - #B11111111 or
0 - 255
0
R-2Common commands
Page 67
ANT-20 (Mainframe)*ESE?
*ESE?
Standard Event Status Enable Query.
ParameterNone
CommentsReads the mask for the ESR register.
See also “WG SCPI and IEEE488 Programmer’s Introduction” for more details.
Example*ESE?
Response: 64
Related commands*ESR? on page R-3
*ESE on page R-2
*ESR?
Standard Event Status Register Query.
ParameterNone
CommentsReads out the status register ESR. Range from 0 - 255.
See also “WG SCPI and IEEE488 Programmer’s Introduction” for more details.
Example*ESR?
Response: 64
Related commands*ESE on page R-2
Common commandsR-3
Page 68
*IDN?ANT-20 (Mainframe)
*IDN?
Identification Query.
ParameterNone
CommentsReads out the instrument identification consisting of 4 fields, separated by “,”:
Note: The setting is synchronized to the next, device-internal complete second. As
a result, erroneous values can be read if you do a read-out immediately after
a previous setting!
The setting is not changed by a *RST command.
DependenciesNone
ExampleSYST:TIME 12,10,0sets the time of day to 12:10:0.
Related commands:SYST:DATE on page R-9
:SYST:TIME?
:SYSTem:TIME? provides the current time of day of the instrument.
Example:SYST:TIME?
Response: 23,50,59
:SYST:VERS?
:SYSTem:VERSion? provides the SCPI version number on which this instrument is
based.
Example:SYST:VERS?
Response: 1996.0for version 1996 release 0.
R-10SYSTEM subsystem
Page 75
ANT-20 (Mainframe)
3STATUS subsystem
3.1Status register structure
The status register structure is oriented towards the one issued by the SCPI, but with the addition of
:STATus:SEQuence register and the event and capture FIFOs. The following figure shows the status
register structure:
STATus:QUEStionable?
STM64/Oc192 laser heat up
STM64/OC192 laser asynchron
Calibration
Overhead Byte
Capture FIFO
not used
AU Pointer
TU Pointer
SDH Alarm
(reserved)
ATM Alarm
OH sequence insertion
BPV/Code Error
Payload Error
SDH Error
PDH Error
ATM Error
Feac Loop
not used
Calibrating
Measuring
Wait for Trigger
8
9
10
STATus:SEQuence?
0
1
2
3
4
6
7
8
9
10
11
12
13
14
15
STATus:OPERation?
0
4
5
Event FIFO
Error Queue
SOH/TOH Byte Capture Gate
SOH/TOH Block Capture Trigger
Operation Complete
Device Dependent Error
APS Gate
not used
(not supported)
Query Error
Execution Error
Command Error
(not supported)
Power On
8
9
10
*ESR?
0
1
2
3
4
5
6
7
MAV
RQS
Status Register
*STB?
0
1
2
3
4
5
6
7
Standard Event Status Register
Fig. R-1Status register structure
STATUS subsystemR-11
Page 76
:STATus:OPERation registerANT-20 (Mainframe)
3.2STATUS commands
:STATus:OPERation register
The OPERation status register contains conditions which are part of the
instrument’s normal operation.
:STAT:OPER:COND?
:STATus:OPERation:CONDition? provides the current value of the condition
register.
CommentsBit positionMeaning
0If this bit is set the instrument is currently performing a calibration.
4If this bit is set the instrument is currently measuring.
5If this bit is set the instrument is in a “wait for trigger” state of the
trigger model (e.g. waiting for the start time during a timer
controlled measurement).
8This bit indicates the start and end of the measurement interval for
the APS (Automatic Protection Switch) measurement. A “1”
indicates that the switching condition has been attained
corresponding to the set sensor
([:SENS]:DATA[:TEL]:APS:SENS on page R-315). A “0” indicates
the end of the following measurement interval, see also
[:SENS]:DATA[:TEL]:A PS:GATE on page R-315.
9If this bit is set the instrument is currently performing a SDH/
SONET overhead byte capture measurement. See also T RIGGER
2 subsystem on page R-27 ff.
10If this bit is set the instrument is currently performing the capture
process for a complete homogeneous SDH/SONET overhead
fetch result. See also TRIGGER 3 subsystem on page R-33 ff.
See SCPI handbook “Command Reference”
or “WG SCPI and IEEE488 Programmer’s Introduction” for more details.
Example:STAT:OPER:COND?
Response: 0
R-12STATUS subsystem
Page 77
ANT-20 (Mainframe):STAT:OPER:ENAB
:STAT:OPER:ENAB
:STATus:OPERation:ENABle <value> specifies the value of the enable register.
See SCPI handbook “Command Reference”
or “WG SCPI and IEEE488 Programmer’s Introduction” for more details.
ParameterNameTypeRangeDefault
valuenumeric#H0000 - #H7FFF or
Note: Bit 15 cannot be set.
Example:STAT:OPER:ENAB 16
:STAT:OPER:ENAB?
:STATus:OPERation:ENABle? provides the current setting of the enable register.
See SCPI handbook “Command Reference”
or “WG SCPI and IEEE488 Programmer’s Introduction” for more details.
Example:STAT:OPER:ENAB?
Response: 0STAT:OPER:ENAB 16
:STAT:OPER[:EVEN]?
:STATus:OPERation[:EVENt]? reads the event register.
#H0
#B0000000000000000 #B0111111111111111 or
0 - 32767
See SCPI handbook “Command Reference”
or “WG SCPI and IEEE488 Programmer’s Introduction” for more details.
Note: Reading the event register clears its content.
Example:STAT:OPER?
Response: 16if measuring event was detected.
STATUS subsystemR-13
Page 78
:STAT:OPER:NTRANT-20 (Mainframe)
:STAT:OPER:NTR
:STATus:OPERation:NTRansition <value> specifies the value of the negative
transition register.
See SCPI handbook “Command Reference”
or “WG SCPI and IEEE488 Programmer’s Introduction” for more details.
ParameterNameTypeRangeDefault
valuenumeric#H0000 - #H7FFF or
Note: Bit 15 cannot be set.
Example:STAT:OPER:NTR 16
:STAT:OPER:NTR?
:STATus:OPERation:NTRansition? provides the current setting of the negative
transition register.
See SCPI handbook “Command Reference”
or “WG SCPI and IEEE488 Programmer’s Introduction” for more details.
Example:STAT:OPER:NTR?
Response: 0
:STAT:OPER:PTR
#H0
#B0000000000000000 #B0111111111111111 or
0 - 32767
:STATus:OPERation:PTRansition <value> specifies the value of the positive
transition register.
See SCPI handbook “Command Reference”
or “WG SCPI and IEEE488 Programmer’s Introduction” for more details.
ParameterNameTypeRangeDefault
valuenumeric#H0000 - #H7FFF or
#B0000000000000000 #B0111111111111111 or
0 - 32767
Note: Bit 15 cannot be set.
Example:STAT:OPER:PTR 16
R-14STATUS subsystem
#H0
Page 79
ANT-20 (Mainframe):STAT:OPER:PTR?
:STAT:OPER:PTR?
:STATus:OPERation:PTRansition? provides the current setting of the positive
transition register.
See SCPI handbook “Command Reference”
or “WG SCPI and IEEE488 Programmer’s Introduction” for more details.
Example:STAT:OPER:PTR?
Response: 0
:STAT:PRES
:STATus:PRESet performs a preset of the status register structure.
See SCPI handbook “Command Reference” for mor e details.
ParameterNone
CommentsThe following actions are taken:
- :STAT:OPER:ENAB is set to all 0’s.
- :STAT:QUES:ENAB is set to all 0’s.
- :STAT:SEQ:ENAB is set to all 1’s.
- all positive transition registers (…:PTR) are set to all 1’s.
Example:STAT:PRES
:STATus:QUEStionable register
The QUEStionable status register set contains bits which give an indication of the
quality of various aspects of the signal.
STATUS subsystemR-15
Page 80
:STAT:QUES:COND?ANT-20 (Mainframe)
:STAT:QUES:COND?
:ST ATus:QUEStionable:CONDition? provides the current value of the questionable
status register.
Comments
Example:STAT:QUES:COND?
Bit positionMeaning
8If this bit is set results can be questionable because the module
needs a calibration (use the *CAL? query to initiate a calibration).
9This bit is set while the laser is in the warm-up phase. This phase
always starts at power on. The bit is only activated for STM60 /
OC192 operation.
10This bit is set while the laser is in an unsettled state. This state
occurs each time the laser is switched on. The bit is only activated
for STM60/OC192 operation.
See SCPI handbook “Command Reference”
or “WG SCPI and IEEE488 Programmer’s Introduction” for more details.
Response: 0
:STAT:QUES:ENAB
:ST ATus:QUEStionable:ENABle <value> specifies the value of the enable register.
See SCPI handbook “Command Reference”
or “WG SCPI and IEEE488 Programmer’s Introduction” for more details.
ParameterNameTypeRangeDefault
valuenumeric#H0000 - #H7FFF or
#B0000000000000000 #B0111111111111111 or
0 - 32767
Note: Bit 15 cannot be set.
Example:STAT:QUES:ENAB 16
#H0
:STAT:QUES:ENAB?
:ST A Tus:QUEStionable:ENABle? pr ovides the current setting of the enable register.
See SCPI handbook “Command Reference”
or “WG SCPI and IEEE488 Programmer’s Introduction” for more details.
Example:STAT:QUES:ENAB?
Response: 0
R-16STATUS subsystem
Page 81
ANT-20 (Mainframe):STAT:QUES[:EVEN]?
:STAT:QUES[:EVEN]?
:STATus:QUEStionable[:EVENt]? reads the event register.
See SCPI handbook “Command Reference”
or “WG SCPI and IEEE488 Programmer’s Introduction” for more details.
Note: Reading the event register clears its content.
Example:STAT:QUES?
Response: 16if measuring event was detected.
:STAT:QUES:NTR
:STATus:QUEStionable:NTRansition <value> specifies the value of the negative
transition register.
See SCPI handbook “Command Reference”
or “WG SCPI and IEEE488 Programmer’s Introduction” for more details.
ParameterNameTypeRangeDefault
valuenumeric#H0000 - #H7FFF or
#B0000000000000000 #B0111111111111111 or
0 - 32767
Note: Bit 15 cannot be set.
Example:STAT:QUES:NTR 16
#H0
:STAT:QUES:NTR?
:STATus:QUEStionable:NTRansition? provides the current setting of the negative
transition register.
See SCPI handbook “Command Reference”
or “WG SCPI and IEEE488 Programmer’s Introduction” for more details.
Example:STAT:QUES:NTR?
Response: 0
STATUS subsystemR-17
Page 82
:STAT:QUES:PTRANT-20 (Mainframe)
:STAT:QUES:PTR
:STATus:QUEStionable:PTRansition <value> specifies the value of the positive
transition register.
See SCPI handbook “Command Reference”
or “WG SCPI and IEEE488 Programmer’s Introduction” for more details.
ParameterNameTypeRangeDefault
valuenumeric#H0000 - #H7FFF or
Note: Bit 15 cannot be set.
Example:STAT:QUES:PTR 16
:STAT:QUES:PTR?
:STATus:QUEStionable:PTRansition? provides the current setting of the positive
transition register.
See SCPI handbook “Command Reference”
or “WG SCPI and IEEE488 Programmer’s Introduction” for more details.
Example:STAT:QUES:PTR?
Response: 0
:STAT:SEQ register
#H0
#B0000000000000000 #B0111111111111111 or
0 - 32767
This status register indicates the states of any dynamic error/alarm/pointer
sequence. This indication allows the user to get control over the state of running
sequences. A bit set to “1” indicates a running sequence. A bit set to “0” indi cates a
finished sequence.
If bit 7 is set, then valid data are present in the FIFO of the SDH/SONET overhead
capture measurement. The data can be read with the command
:FETC[:ARR][:DATA][:TEL][:SDH]:OVER:CA PT? on page R-417.
Note: This status register is only accessed in the case of sequences of finite le ngth
such as single defect insertions or pointer sequences in “SINGle” mode.
:STAT:SEQ:COND?
:STATus:SEQuence:CONDition?
See SCPI handbook “Command Reference”
or “WG SCPI and IEEE488 Programmer’s Introduction” for more details.
R-18STATUS subsystem
Page 83
ANT-20 (Mainframe):STAT:SEQ:ENAB
Example:STAT:SE Q:COND?
Response: 0
:STAT:SEQ:ENAB
:STATus:SEQuence:ENABle <value> specifies the value of the enable register.
See SCPI handbook “Command Reference”
or “WG SCPI and IEEE488 Programmer’s Introduction” for more details.
ParameterNameTypeRangeDefault
valuenumeric#H0000 - #H7FFF or
Note: Bit 15 cannot be set.
Example:STAT:SE Q:ENAB 4
:STAT:SEQ:ENAB?
:STATus:SEQuence:ENABle? provides the current setting of the enable register.
See SCPI handbook “Command Reference”
or “WG SCPI and IEEE488 Programmer’s Introduction” for more details.
Example:STAT:SE Q:ENAB?
Response: 0
:STAT:SEQ[:EVEN]?
:STATus:SEQuence[:EVENt]? reads the event register.
#H0
#B0000000000000000 #B0111111111111111 or
0 - 32767
See SCPI handbook “Command Reference”
or “WG SCPI and IEEE488 Programmer’s Introduction” for more details.
Note: Reading the event register clears its content.
Example:STAT:SEQ?
Response: 0
STATUS subsystemR-19
Page 84
:STAT:SEQ:NTRANT-20 (Mainframe)
:STAT:SEQ:NTR
:STATus:SEQuence:NTRansition <value> specifies the value of the negative
transition register.
See SCPI handbook “Command Reference”
or “WG SCPI and IEEE488 Programmer’s Introduction” for more details.
ParameterNameTypeRangeDefault
valuenumeric#H0000 - #H7FFF or
Note: Bit 15 cannot be set.
Example:STAT:SEQ:NTR 4
:STAT:SEQ:NTR?
:STATus:SEQuence:NTRansition? provides the current setting of the negative
transition register.
See SCPI handbook “Command Reference”
or “WG SCPI and IEEE488 Programmer’s Introduction” for more details.
Example:STAT:SEQ:NTR?
Response: 0
:STAT:SEQ:PTR
#H0
#B0000000000000000 #B0111111111111111 or
0 - 32767
:STATus:SEQuence:PTRansition <value> specifies the value of the positive
transition register.
See SCPI handbook “Command Reference”
or “WG SCPI and IEEE488 Programmer’s Introduction” for more details.
ParameterNameTypeRangeDefault
valuenumeric#H0000 - #H7FFF or
#B0000000000000000 #B0111111111111111 or
0 - 32767
Note: Bit 15 cannot be set.
Example:STAT:SEQ:PTR 8
R-20STATUS subsystem
#H0
Page 85
ANT-20 (Mainframe):STAT:SEQ:PTR?
:STAT:SEQ:PTR?
:STATus:SEQuence:PTRansition? provides the current setting of the positive
transition register.
See SCPI handbook “Command Reference”
or “WG SCPI and IEEE488 Programmer’s Introduction” for more details.
Example:ST AT:SEQ:PTR?
Response: 0
STATUS subsystemR-21
Page 86
:STAT:SEQ:PTR?ANT-20 (Mainframe)
Notes:
R-22STATUS subsystem
Page 87
ANT-20 (Mainframe):ABOR[1]
4TRIGGER 1 subsystem
The Trigger subsystem is used for Start/Stop control of measurements (see also
[:SENS]:SWE on page R-407)
:ABOR[1]
:ABORt[1] halts a measurement in progress or a timer sequence.
Note: A measurement in progress is halted at the end of the next full second to
ensure homogeneous results.
If the results are to be read after ending a measurement with ABORt[1], it is
a good idea to insert a *W AI command between the ABORt[1] command and
the read command for the results.
ParameterNone
DependenciesThis command works only if a measurement has been previously activated using
:INIT[1][:IMM][:ALL] on page R-23.
Example:ABOR
Related commands:INIT[1][:IMM][:ALL] on page R-23
:TRIG[1][:SEQ]:SOUR on page R-24
:TRIG[1][:SEQ]:STIM on page R-25
:INIT[1][:IMM][:ALL]
:INITiate[1][:IMMediate][:ALL] starts the measurement on the next trigger.
ParameterNone
DependenciesNone
CommentsThe measurement is started on the next trigger. This can be when the next full
second is reached, or under timer control, by reaching the time preset with
:TRIG[1][:SEQ]:STIM on page R-25. The trigger condition to be fulfilled is specified
using :TRIG[1][:SEQ]:SOUR on page R-24.
Example:INIT
Related commands:ABOR[1] on page R-23
:TRIG[1][:SEQ]:SOUR on page R-24
:TRIG[1][:SEQ]:STIM on page R-25
TRIGGER 1 subsystemR-23
Page 88
:TRIG[1][:SEQ]:SOURANT-20 (Mainframe)
:TRIG[1][:SEQ]:SOUR
:TRIGger[1][:SEQuence]:SOURce <source> specifies the trigger source for the
TRIGGER subsystem.
ParameterNameTypeRangeDefault
sourcediscreteAINTernal | STIMe |
IMMediate
DependenciesNone
CommentsAINTernal:The trigger condition is satisfied when the next complete second is
reached.
STIMe:The trigger condition is satisfied when the start time set with
:TRIG[1][:SEQ]:STIM on page R-25 is reached.
IMMediate:The trigger condition is satisfied in an
asynchronous manner, i.e. at the next possible point in time.
Example:TRIG[1][:SEQ]:SOUR STIMfor the timer as a trigger source.
Related commands:INIT[1][:IMM][:ALL] on page R-23
:ABOR[1] on page R-23
:TRIG[1][:SEQ]:STIM on page R-25
AINT
:TRIG[1][:SEQ]:SOUR?
This query provides the current trigger source setting.
Example:TRIG[1][:SEQuence]:SOUR?
Response: AINT
for activated internal triggering at the next complete second.
R-24TRIGGER 1 subsystem
Page 89
ANT-20 (Mainframe):TRIG[1][:SEQ]:STIM
:TRIG[1][:SEQ]:STIM
:TRIGger[1][:SEQuence]:STIMe
<year>,<month>,<day>,<hour>,<minute>,second> specifies the starting time of a
timer-based measurement.
DependenciesEffective only if :TRIG[1][:SEQ]:SOUR STIM.
CommentsThis command is used to set the point in time at which a timer-based measurement
is to start.
Example:TRIG:STIM 1996,6,3,18,30,00sets the measurement start
to June 3, 1996 at 18:30:00
Related commands:INIT[1][:IMM][:ALL] on page R-23
:ABOR[1] on page R-23
:TRIG[1][:SEQ]:SOUR on page R-24
:TRIG[1][:SEQ]:STIM?
:TRIGger[1][:SEQuence]:STIMe? This query provides the current setting of the
measurement start time.
Example:TRIG:STIM?
Response: 1995,12,31,23,30,20
for measurement start on December, 31, 1995 at 23:30:20.
TRIGGER 1 subsystemR-25
Page 90
:TRIG[1][:SEQ]:STIM?ANT-20 (Mainframe)
Notes:
R-26TRIGGER 1 subsystem
Page 91
ANT-20 (Mainframe):ABOR2
5TRIGGER 2 subsystem
The Trigger 2 subsystem is used for Start/Stop control of SDH/SONET overhead
data capture measurements (see also [:SENS]:FUNC:EVEN[:ON] on page R-405
and :FETC[:ARR][:DATA][:TEL][:SDH]:OVER:CAPT? on page R-417 ff.
The status of a running capture measurement is indicated in the sta tus register (see
Status register structure on page R-11 ff.) as follows:
Bit 9 (STAT:OPER)
Capture Gate
Bit 7 (STAT:SEQ)
Capture data available
INIT2
Capture trigger satisfied
All capture data read
(FIFO is empty)
Fig. R-2Capture measurement
Note: All commands in this group are valid only if the option BN 3035/90.15 is
available.
More captured data available
Capture aborted
:ABOR2
:ABORt2 halts a capture measurement in progress.
Note: A capture measurement in progress is halted at the end of the next full
second to ensure homogeneous results.
If the results are to be read after ending a measurement with ABORt2, it is a
good idea to insert a *WAI command between the ABORt2 command and
the read command for the results.
ParameterNone
DependenciesThis command works only if a capture measurement wa s previously activated using
:INIT2[:IMM][:ALL] on page R-28.
CommentsA running capture measurement can be manually terminated with this command.
The measurement is automatically interrupted if the capture FIFO is full so that no
further data can be recorded.
TRIGGER 2 subsystemR-27
Page 92
:INIT2[:IMM][:ALL]ANT-20 (Mainframe)
Example:ABOR2
Related commands:INIT2[:IMM][:ALL] on page R-28
:TRIG2[:SEQ]:LOG:SOUR on page R-30
:TRIG2[:SEQ]:LOG:TYPE on page R-31
:TRIG2[:SEQ]:LOG:VAL on page R-32
:INIT2[:IMM][:ALL]
:INITiate2[:IMMediate][:ALL] starts the capture measurement.
ParameterNone
DependenciesOption 90.15 is required for capture mea surements.
Example:INIT2
Related commands:ABOR2 on page R-27
:TRIG2[:SEQ]:LOG:SOUR on page R-30
:TRIG2[:SEQ]:LOG:TYPE on page R-31
:TRIG2[:SEQ]:LOG:VAL on page R-32
:FETC[:ARR][:DATA][:TEL][:SDH]:OVER:CA PT? on page R-417
:TRIG2[:SEQ]:LOG:OBYT
:TRIGger2[:SEQuence]:LOGic:OBYTe <byte> determines the SOH/TOH byte or
byte pair (K1K2) whose changes in value are to be recorded.
DependenciesThe set values of :TRIG2[:SEQ]:LOG:VAL and :TRIG2[:SEQ]:LOG:OBYT are
evaluated for the trigger source VALue and NVALue.
For STM0/STS1, only bytes in the 1st, 4th and 7th column are allowed (i.e. A11 is
possible but not A12 and A13).
For STM4/OC12, the A1,A2,B1 bytes are not selectable.
For STM16/OC48, the A1,A2,B1 bytes are not selectable.
The selectable POH bytes are depending on the selected mapping (e.g. the
received signal must contain a low path to select the LP-POH bytes).
CommentsA11
A12
A13
A21
etc. up to
X99
Bytes without a standardized name are indicated by their line and column numbers
in the SOH/TOH with a prefixed ‘X’.
e.g. X25 indicates the byte in line 2 and column 5 (next to the E1 byte).
Example:TRIG2:LOG:OBYT D2
selects the D2 byte for capture measurement.
Related commands:INIT2[:IMM][:ALL] on page R-28
:ABOR2 on page R-27
:TRIG2[:SEQ]:LOG:VAL on page R-32
:TRIG2[:SEQ]:LOG:SOUR on page R-30
:TRIG2[:SEQ]:LOG:TYPE on page R-31
Value for the 1st A1 byte of the SOH as comparison byte
Value for the 2nd A1 byte of the SOH as comparison byte
Value for the 3rd A1 byte of the SOH as comparison byte
Value for the 1st A2 byte of the SOH as comparison byte
Value for the SOH byte line 9, column 9 as comparison byte
:TRIG2[:SEQ]:LOG:OBYT?
:TRIGger2[:SEQuence]:LOGic:OBYTe? This query provides the set value for the
SOH comparison byte for the trigger condition of the capture measurement.
Example:TRIG2:LOG:OBYTE?
K1K2 for the corresponding SOH comparison byte.
TRIGGER 2 subsystemR-29
Page 94
:TRIG2[:SEQ]:LOG:SOURANT-20 (Mainframe)
:TRIG2[:SEQ]:LOG:SOUR
: T RIGger2[:SEQuence]:LOGic:SOURce <source> determines the trigger source for
the capture measurement.
ParameterNameTypeRangeDefault
sourcediscreteMANual | VALue | NVALue |
AUAIS | AULOP | MSRDI |
MSAIS | TCMFrame
DependenciesFor VALue/NVALue, the set values of :TRIG2[:SEQ]:LOG:VAL and
:TRIG2[:SEQ]:LOG:OBYT are evaluated.
CommentsMANual:The SOH bytes selected with :TRIG2[:SEQ]:LOG:OBYT are
evaluated. If the measurement is started, recording begins
immediately.
VALue:The capture measurement is started if the comparison pattern
entered with :TRIG2[:SEQ]:LOG:VAL matches the received value
of the SOH byte selected with :TRIG2[:SEQ]:LOG:OBYT.
NVALue:The capture measurement is started if the comparison pattern
entered with :TRIG2[:SEQ]:LOG:VAL does not match the received
value of the SOH byte selected with :TRIG2[:SEQ]:LOG:OBYT.
AUAIS:The data recording is started if the alarm AUAIS is detected.
AULOP:The data recording is started if the alarm AULOP is detected
MSRDI:The data recording is started if the alarm MSRDI is detected.
MSAIS:The data recording is started if the alarm MSAIS is detected.
TCMFrameTandem Connection Monitoring recording begins with the next
TCM-FAS-WORD that is found.
Example:TRIG2:LOG:SOUR MSAIS
VALue
Related commands:INIT2[:IMM][:ALL] on page R-28
:ABOR2 on page R-27
:TRIG2[:SEQ]:LOG:VAL on page R-32
:TRIG2[:SEQ]:LOG:TYPE on page R-31
:TRIG2[:SEQ]:LOG:SOUR?
: T RIGger2[:SEQuence]:LOGic:SOURce? This query provides the set trigger sou rce
for the capture measurement.
Example:TRIG2:LOG:SOUR?
Response: MANfor manual triggering of the capture measurement.
R-30TRIGGER 2 subsystem
Page 95
ANT-20 (Mainframe):TRIG2[:SEQ]:LOG:TYPE
:TRIG2[:SEQ]:LOG:TYPE
:TRIGger2[:SEQuence]:LOGic:TYPE <value> determines the time frame for data
recording, referred to the trigger time point of the capture measurement.
ParameterNameTypeRangeDefault
valuediscreteAFTerAFTer
DependenciesNone
CommentsAFTer:The recording time frame of the capture measuremen t begins after
the trigger.
Example:TRIG2:LOG:TYPE AFT
Related commands:INIT2[:IMM][:ALL] on page R-28
:ABOR2 on page R-27
:TRIG2[:SEQ]:LOG:SOUR on page R-30
:TRIG2[:SEQ]:LOG:VAL? on page R-32
:TRIG2[:SEQ]:LOG:OBYT on page R-28
:TRIG2[:SEQ]:LOG:TYPE?
:TRIGger2[:SEQuence]:LOGic:TYPE? This query provides the set value of the
recording time frame for the capture measurement.
Example:TRIG2:LOG:TYPE?
Response: AFTfor recording after the trigger event.
TRIGGER 2 subsystemR-31
Page 96
:TRIG2[:SEQ]:LOG:VALANT-20 (Mainframe)
:TRIG2[:SEQ]:LOG:VAL
:TRIGger2[:SEQuence]:LOGic:VALue <pattern> determines the comparison
pattern with which an SOH byte set with :TRIG2[:SEQ]:LOG:OBYT is compared to
attain the trigger condition of the capture measurement.
ParameterNameTypeRangeDefault
patternstringString with the allowable
characters “0” | “1” | “X” | “x” ,
16 characters long.
DependenciesThe pattern set here is evaluated only for :TRIG2[:SEQ]:LOG:SOUR = VALue or
NVALue.
Commentspattern:Only the characters “0”, “1”, “X”, “x” are allowed.
A length of 16 characters is required.
For 1 byte capture, only the first 8 characters are valid.
“X” | “x”:This bi t position is irrelevant for the trigger condition.
“1’’A logical 1 is necessary at this bit position to attain the trigger
condition.
“0’’A logical 0 is necessary at this bit position to attain the trigger
condition.
After the trigger condition is attained, the comparison value set here is no longer
relevant, all subsequent byte changes are recorded regardless of the comparison
value!
Example:TRIG2:LOG:VAL “XXXXXXXXXXXXXX01”
For K1K2 capture, Bit0 is set to 1 and Bit1 to 0 as the trigger condition.
:TRIG2:LOG:VAL “XXXXXX01XXXXXXXX”
For 1 byte capture, Bit0 is set to 1 and Bit1 to 0 as the trigger condition since only
the first 8 characters are relevant.
Related commands:INIT2[:IMM][:ALL] on page R-28
:ABOR2 on page R-27
:TRIG2[:SEQ]:LOG:TYPE on page R-31
:TRIG2[:SEQ]:LOG:SOUR on page R-30
:TRIG2[:SEQ]:LOG:OBYT on page R-28
“XXXXXXXX
XXXXXXXX”
:TRIG2[:SEQ]:LOG:VAL?
:TRIGger2[:SEQuence]:LOGic:VALue? This query provides the set value of the
comparison pattern for the trigger condition of the capture measurement.
Example:TRIG2:LOG:VAL?
Response: “XXXXXXXX0011X001”for the corresponding comparison pattern.
R-32TRIGGER 2 subsystem
Page 97
ANT-20 (Mainframe):ABOR3
6TRIGGER 3 subsystem
The Trigger 3 subsystem is used to start and stop the capture process for a
complete homogeneous SDH overhead fetch result.
The following are required: Signal structure STM16/OC48 and options
BN 3035/91.53, BN 3035/91.54 or BN 3035/91.59 (STM16c/OC48c hardware
options).
:ABOR3
:ABORt3 halts the capture process started with :INIT3.
ParameterNone
DependenciesThis command works only if the capture process has been previously activated
using :INIT3[:IMM][:ALL] on page R-33.
Example:ABOR3
Related commands:INIT3[:IMM][:ALL] on page R-33
:INIT3[:IMM][:ALL]
:INITiate3[:IMMediate][:ALL] starts the capture process.
ParameterNone
DependenciesNone
Comments:INIT3 starts the capture process for a complete homogeneous SDH o verhead fetch
result.
Example:INIT3
Related commands:ABOR3 on page R-33
:FETC[:ARR][:DATA][:TEL][:SDH]:OVER:CPARt[i]? on page R-416
:FETC:SCAL[:DATA][:TEL][:SDH]:OVER:CPARt[i]? on page R-426
TRIGGER 3 subsystemR-33
Page 98
:INIT3[:IMM][:ALL]ANT-20 (Mainframe)
Notes:
R-34TRIGGER 3 subsystem
Page 99
ANT-20 (Mainframe):OUTP:CLOC[1]:DIV[:STAT]
7OUTPUT subsystem
:OUTP:CLOC[1]:DIV[:STAT]
:OUTPut:CLOCk[1]:DIVider[:STATe] <state> switches the clock output divider for
port [24] on or off.
ParameterNameTypeRangeDefault
statebooleanON | OFF | 0 | 1OFF
DependenciesIs only valid if [:SENS]:DATA[:TEL]:SDH:RATE = STM4.
A setting = ON is mandatory for STM-4 Wander measurements in conjunction
with the Jitter Module for options BN 3035/90.67 or O.172 BN 3035/90.86 with
firmware release 7.0 or later (not possible for ABT-20 devi ce s ).
A setting = ON is mandatory for STM-4 JITTER measurements in conjunction
with the Jitter Module ONLY for option O.172 BN 3035/90.86 with firmware
release 7.0 or later (not possible for ABT-20 devices).
A setting = OFF is mandatory for STM-4 JITTER measurements in conjunction
with the Jitter Module ONLY for option BN 3035/90.67 with firmware release
earlier than 7.0 (not possible for ABT-20 devices).
CommentsON | 1:The STM4 clock divider is switched on producing a 155 Mbit/s
clock signal at port [24] instead of the normal 622 Mbit/s.
The setting in conjunction with the Jitter Module is explained
above.
OFF | 0:Output divider off.
The setting in conjunction with the Jitter Module is explained
above.
Example:OUTP:CLOC:DIV ONswitches the clock output divider on.
Related commands[:SENS]:DATA[:TEL]:SDH:RATE on page R-370
On Jitter Module: [:SENS]:DATA[:TEL]:RATE = STM4; [:SENS]:MODE.
:OUTP:CLOC[1]:DIV[:STAT]?
This query provides the status of the clock output divider.
Example:OUTP:CLOC:DIV?
Response: 1if the clock output divider is switched on.
OUTPUT subsystemR-35
Page 100
:OUTP:CLOC2[:STAT]ANT-20 (Mainframe)
:OUTP:CLOC2[:STAT]
:OUTPut:CLOCk2[:STATe] <state> switches the 2488 MHz clock output (port [42])
on or off.
ParameterNameTypeRangeDefault
statebooleanON | OFF | 0 | 1OFF
DependenciesIs only valid if :SOUR:DATA[:TEL]:SDH:RATE = STM16. The output signal is only
valid if the receiver gets a valid STM16/OC48 input signal.
CommentsON | 1:Output on
OFF | 0:Output off
This output is automatically switched ON if
:SOUR:DA TA[:TEL]:SDH:RATE = STM16 is set.
Example:OUTP:CLOC2 ONswitches the clock output on.
Related commands:OUTP:CLOC3[:STAT] on page R-37
:OUTP:CLOC2[:STAT]?
This query provides the status of the 2488 MHz clock output.
Example:OUTP:CLOC2?
Response: 1if the clock output is switched on.
R-36OUTPUT subsystem
Loading...
+ hidden pages
You need points to download manuals.
1 point = 1 manual.
You can buy points or you can get point for every manual you upload.