Tektronix Computer Hardware 070 9180 01 User Manual
User Manual  
Option 01  
VXI Interface Daughter Board  
070-9180-01  
This document applies for firmware version 1.00  
and above.  
 
WARRANTY  
Tektronix warrants that this product will be free from defects in materials and workmanship for a period of three (3) years  
from the date of shipment. If any such product proves defective during this warranty period, Tektronix, at its option, either  
will repair the defective product without charge for parts and labor, or will provide a replacement in exchange for the  
defective product.  
In order to obtain service under this warranty, Customer must notify Tektronix of the defect before the expiration of the  
warranty period and make suitable arrangements for the performance of service. Customer shall be responsible for  
packaging and shipping the defective product to the service center designated by Tektronix, with shipping charges prepaid.  
Tektronix shall pay for the return of the product to Customer if the shipment is to a location within the country in which the  
Tektronix service center is located. Customer shall be responsible for paying all shipping charges, duties, taxes, and any  
other charges for products returned to any other locations.  
This warranty shall not apply to any defect, failure or damage caused by improper use or improper or inadequate  
maintenance and care. Tektronix shall not be obligated to furnish service under this warranty a) to repair damage resulting  
from attempts by personnel other than Tektronix representatives to install, repair or service the product; b) to repair  
damage resulting from improper use or connection to incompatible equipment; or c) to service a product that has been  
modified or integrated with other products when the effect of such modification or integration increases the time or  
difficulty of servicing the product.  
THIS WARRANTY IS GIVEN BY TEKTRONIX WITH RESPECT TO THIS PRODUCT IN LIEU OF ANY  
OTHER WARRANTIES, EXPRESSED OR IMPLIED. TEKTRONIX AND ITS VENDORS DISCLAIM ANY  
IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.  
TEKTRONIX’ RESPONSIBILITY TO REPAIR OR REPLACE DEFECTIVE PRODUCTS IS THE SOLE AND  
EXCLUSIVE REMEDY PROVIDED TO THE CUSTOMER FOR BREACH OF THIS WARRANTY. TEKTRONIX  
AND ITS VENDORS WILL NOT BE LIABLE FOR ANY INDIRECT, SPECIAL, INCIDENTAL, OR  
CONSEQUENTIAL DAMAGES IRRESPECTIVE OF WHETHER TEKTRONIX OR THE VENDOR HAS  
ADVANCE NOTICE OF THE POSSIBILITY OF SUCH DAMAGES.  
 
Table of Contents  
General Safety Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  
Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  
iii  
vii  
Getting Started  
Product Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  
Accessories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  
Controls and Indicators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  
Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  
Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  
Installation Checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  
Functional Check . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  
1–1  
1–4  
1–4  
1–4  
1–5  
1–9  
1–10  
Operating Basics  
Functional Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  
Power-on . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  
Instrument I/O: VXIbus Basics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  
2–1  
2–1  
2–2  
Syntax and Commands  
Command Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  
3–1  
Functional Command Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  
System Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  
Module Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  
3–11  
3–11  
3–11  
Command Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  
IEEE-488.2 Common Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  
3–15  
3–59  
Status and Events  
Status and Event Reporting System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  
Status Byte Register . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  
Service Request Enable Register . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  
Standard Event Status Register . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  
Event Status Enable Register . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  
The Output Queue . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  
The System Error and Event Queue . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  
Status and Event Reporting Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  
Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  
4–1  
4–1  
4–2  
4–3  
4–4  
4–4  
4–4  
4–5  
4–6  
Appendices  
Appendix A: Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  
Appendix B: Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  
Appendix C: User Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  
A–1  
B–1  
C–1  
i
Option 01 VXI Interface Module User Manual  
 
Table of Contents  
Appendix D: Replaceable Parts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  
Parts Ordering Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  
Using the Replaceable Parts List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  
D–1  
D–1  
D–2  
Glossary and Index  
ii  
Option 01 VXI Interface Module User Manual  
 
General Safety Summary  
Review the following safety precautions to avoid injury and prevent damage to  
this product or any products connected to it.  
Only qualified personnel should perform service procedures.  
While using this product, you may need to access other parts of the system. Read  
the General Safety Summary in other system manuals for warnings and cautions  
related to operating the system.  
Injury Precautions  
Avoid Electric Overload  
To avoid electric shock or fire hazard, do not apply a voltage to a terminal that is  
outside the range specified for that terminal.  
Avoid Electric Shock  
To avoid injury or loss of life, do not disconnect probes or test leads from this  
product while it is connected to a voltage source.  
Do Not Operate Without  
Covers  
To avoid electric shock or fire hazard, do not operate this product with covers or  
panels removed.  
Use Proper Fuse  
To avoid fire hazard, use only the fuse type and rating specified for this product.  
To avoid electric shock, do not operate this product in wet or damp conditions.  
Do Not Operate in  
Wet/Damp Conditions  
Do Not Operate in an  
Explosive Atmosphere  
To avoid injury or fire hazard, do not operate this product in an explosive  
atmosphere.  
Avoid Exposed Circuitry  
To avoid injury, remove jewelry such as rings, watches, and other metallic  
objects. Do not touch exposed connections and components when power is  
present.  
Product Damage Precautions  
Provide Proper Ventilation  
To prevent product overheating, provide proper ventilation.  
iii  
Option 01 VXI Interface Module User Manual  
 
General Safety Summary  
Do Not Operate With  
Suspected Failures  
If you suspect there is damage to this product, have it inspected by qualified  
service personnel.  
Safety Terms and Symbols  
Terms in This Manual  
These terms may appear in this manual:  
WARNING. Warning statements identify conditions or practices that could result  
in injury or loss of life.  
CAUTION. Caution statements identify conditions or practices that could result in  
damage to this product or other property.  
Terms on the Product  
These terms may appear on the product:  
DANGER indicates an injury hazard immediately accessible as you read the  
marking.  
WARNING indicates an injury hazard not immediately accessible as you read the  
marking.  
CAUTION indicates a hazard to property including the product.  
Symbols on the Product  
The following symbols may appear on the product:  
DANGER  
High Voltage  
Protective Ground  
(Earth) Terminal  
ATTENTION  
Refer to Manual  
Double  
Insulated  
Certifications and Compliances  
Safety Certification of  
Plug-in or VXI Modules  
For modules (plug-in or VXI) that are safety certified by Underwriters Laborato-  
ries, UL Listing applies only when the module is installed in a UL Listed  
product.  
For modules (plug-in or VXI) that have cUL or CSA approval, the approval  
applies only when the module is installed in a cUL or CSA approved product.  
iv  
Option 01 VXI Interface Module User Manual  
 
General Safety Summary  
Compliances  
Consult the product specifications for Overvoltage Category, and Safety Class.  
Overvoltage Category  
The following defines overvoltage categories:  
CAT III: Distribution level mains, fixed installation.  
CAT II: Local level mains, appliances, portable equipment  
CAT I: Signal level, special equipment or parts of equipment, telecommunica-  
tion, electronics  
v
Option 01 VXI Interface Module User Manual  
 
Preface  
This manual assumes you are familiar with VXIbus instruments and operation  
and with the purpose and function of this instrument.  
Please read and follow all instructions for installation and configuration. Use the  
Installation Checklist to ensure proper installation and to record your initial  
settings.  
The Operating Basics section gives a summary of VXIbus operation and  
presents an overview of the operation of this instrument.  
The Syntax and Commands section provides a summary of all the commands  
followed by detailed descriptions of each command.  
The Status and Events section contains an explanation of the Status and Event  
Reporting System and lists the system messages. Appendix B: Examples contains  
example programs that demonstrate the programmable features of this instru-  
ment.  
You may also want to keep the Reference Guide by the instrument.  
Conventions  
The names of all switches, controls, and indicators appear in this manual exactly  
as they appear on the instrument.  
Specific conventions for programming are given in the sections Syntax and  
Commands and Appendix B: Examples.  
vii  
Option 01 VXI Interface Module User Manual  
 
Getting Started  
This section begins with a brief description of the Option 01 VXI Interface  
Module, and explains how to configure and install the module on a relay  
switching module in a VXIbus mainframe. When the Option 01 is installed on a  
relay module, a quick functional check (described in this section of the User  
Manual for the relay module) assures that the instrument operates properly.  
Product Description  
The Option 01 VXI Interface Module is a printed circuit board assembly for use  
in a mainframe conforming to the VXIbus Specification. The Option 01 provides  
a VXI word serial protocol servant interface to the SurePatht family of VXI  
relay modules. The Option 01 is a daughter board assembly measuring approxi-  
mately 3I × 9I that is installed as an optional daughter board on one of the  
SurePatht C-size VXI switching modules. The daughter board accepts  
SCPI-compatible commands from its commander using VXI word serial  
protocol. The daughter board controls the relay module on which it is installed,  
and controls additional relay modules installed in adjacent slots to its right via  
the VXI P2 local bus. The daughter board is capable of controlling from one to  
12 relay modules including members of the SurePatht family of relay switching  
modules and VX4372 and VX4374 Scanner Slave modules. In this document,  
these modules will be referred to as “local bus slaves.”  
The VXI Interface Module includes the following features:  
H
CPU:  
Zilog Z88C00 Microcontroller with 20 MHz Clock  
64 Kbyte of EPROM and 32 Kbyte of RAM  
VXI Interface:  
H
VXI Rev 1.4 Message Based Device. IEEE-488.2 device  
Supports Fast Handshake word serial protocol data transfers  
Logical Address selectable with two rotary hexadecimal switches  
Interrupter level selectable with a rotary hexadecimal switch. Selects one of  
seven levels or disables interrupt generation  
Command programmable control of one to eight VXI TTL triggers  
Command programmable monitoring of one or more VXI TTL triggers  
1–1  
Option 01 VXI Interface Module User Manual  
 
Getting Started  
The Local Bus Interface function of the Option 01 provides serial I/O interface  
for control of scanner slave and SurePatht relay modules, monitors the power  
fuses of all local bus slave modules that it controls, and provides a serial input  
interface to identify each local bus slave that it controls.  
As part of the self test, SurePatht modules automatically verify the control  
logic every time a relay operation is performed.  
Figure 1–1 shows the Option 01.installed on a SurePatht relay module.  
Figure 1–2 shows a typical SurePatht configuration.  
LOGICAL  
ADDRS  
Option 01  
LO  
HI  
INTRPT  
Switches as viewed  
from the rear of instrument  
(labels are on the back shield)  
F1291  
Figure 1–1: Option 01 Indicators and Switch Locations  
1–2  
Option 01 VXI Interface Module User Manual  
 
Getting Started  
VXI interface &  
slave controller  
daughter board  
Backplane  
connectors  
Front panel  
connectors  
VXI backplane  
local bus  
Daughter board  
connectors  
Figure 1–2: Typical SurePath Configuration  
Fuses  
Each relay module that the Option 01 Module controls has a fuse that limits the  
amount of current that the module can draw from the VXI backplane +5 V power  
pins. This fuse protects the module in case of an accidental shorting of the power  
bus or any other situation where excessive current might be drawn.  
The Option 01 Module monitors the state of the fuses of each of the relay  
modules that it controls. If a fuse opens on one of these modules, the Option 01  
Module will assert SYSFAIL* on the VXIbus.  
If the +5 V fuse on the module on which the Option 01 Module is installed  
opens, the VXIbus Resource Manager will be unable to assert SYSFAIL  
INHIBIT on the Option 01 to disable SYSFAIL*.  
If a +5 V fuse opens, remove the fault before replacing the fuse. Replacement  
fuse information is given in the Specifications section of the user manual for the  
appropriate relay module.  
BITE (Built-in Test  
Equipment)  
Built-in Test Equipment (BITE) is provided by extensive self tests that are  
automatically invoked on power-on and can also be invoked on command.  
Circuitry tested includes the CPU and all memory, and the relay control circuitry  
on each relay module controlled by the Option 01.  
1–3  
Option 01 VXI Interface Module User Manual  
 
Getting Started  
Accessories  
Table 1–1 lists the standard accessories included with the Option 01.  
Table 1–1: Standard Accessories  
Accessory  
Part Number  
070-9180-XX  
070-9198-XX  
Option 01 User Manual  
Option 01 Reference  
Controls and Indicators  
Switches  
The following controls are provided to select the functions of the Option 01  
operating environment.  
The Logical Address switches and VMEbus Interrupt Level Select switch must be  
correctly set to insure proper operation. See Configuration for details on how to  
set the switches.  
Configuration  
The following switches must be correctly set to ensure proper operation. Refer to  
Figure 1–1 for their physical locations.  
Logical Address Switches  
Each functional module in a VXIbus System must be assigned a unique logical  
address, from 1 to decimal 255 (hexadecimal FF). The base VMEbus address of  
the Option 01 is set to a value between hexadecimal C0 (C00016) and hexadeci-  
mal FF (FFC016) by two hexadecimal rotary switches. Align the desired switch  
position with the arrow on the module shield.  
The physical address of the instrument is on a 64 byte boundary. If the Logical  
Address switch representing the most significant digit (LA–HI) of the logical  
address is set to position X and the switch representing the least significant digit  
(LA–LO) of the logical address is set to position Y, then the base physical  
address of the Option 01 will be [(4016 × XY16) + C00016].  
1–4  
Option 01 VXI Interface Module User Manual  
 
Getting Started  
For example:  
Base Physical Address  
hex  
L.A.  
HI  
LO  
decimal  
A
16  
0
16  
A
16  
(64 * 10) + 49152 = 49792 (40 * A ) + C000 = C280  
16 16 16 16  
15  
16  
1
16  
5
16  
(64 * 21) + 49152 = 50496 (40 * 15 ) + C000 = C540  
16 16 16 16  
LA. is the Logical Address  
IEEE-488 Address  
In order to use and program the Option 01 daughter board in an IEEE-488  
environment you must know the IEEE-488 address of the module. Different  
manufacturers of IEEE-488 interface devices might have different algorithms for  
equating a logical address with an IEEE-488 address. Consult the operating  
manual of the IEEE-488 Interface Slot 0 module being used.  
VMEbus Interrupt Level  
Select Switch  
Each function module in a VXIbus System can generate an interrupt at a  
specified level on the VMEbus to request service from the interrupt handler  
located on its commander. Set the interrupt level to the same level as the  
interrupt handler on that commander. The VMEbus interrupt level on which the  
Option 01 daughter board generates interrupts is set by a rotary switch. Align the  
desired switch position with the arrow on the module shield.  
Valid VMEbus Interrupt Level Select switch settings are one through seven, with  
setting one equivalent to level one, and so on. The level chosen should be the  
same as the level set on the Option 01 interrupt handler, typically the module  
commander. Setting the switch to zero or eight will disable the module inter-  
rupts. Do not use switch settings nine through F.  
Interrupts are used by the module to return VXIbus Protocol Events to the  
module commander. Refer to the Operating Basics section for more information  
on interrupts.  
Installation  
This section describes how to install the Option 01.  
Tools Required  
A Torxt T-10 driver set is required for proper installation.  
Requirements and  
Cautions  
The Option 01 daughter board is installed on a C-size VXIbus instrument  
module and therefore may be installed in any C- or D-size VXIbus mainframe  
slot other than slot 0. To install the module in a D-size mainframe, consult the  
operating manual for the mainframe. Refer to Configuration for information on  
1–5  
Option 01 VXI Interface Module User Manual  
 
Getting Started  
selecting and setting the Logical Address switch of the module. This switch  
defines the programming address of your module. To avoid confusion, it is  
recommended that the slot number and the logical address be the same.  
NOTE. Verify that the mainframe is able to provide adequate cooling and power  
with this module installed. Refer to the mainframe Operating Manual for  
instructions.  
If the installed Option 01 is used in a Tektronix mainframe, all Option 01  
cooling requirements are met.  
Installation Procedure  
Follow these steps to install the Option 01.  
CAUTION. The Option 01 daughter board is a piece of electronic equipment and  
therefore has some susceptibility to electrostatic damage (ESD). ESD precau-  
tions must be taken whenever the module is handled.  
1. Record the revision levels, serial numbers (located on the label on the top  
shield of the host module and on a sticker on the Option 01), and switch  
settings on the Installation Checklist.  
2. Verify that the switches are set to the correct values. Refer to Configuration  
for more information on setting switches.  
3. Install the Option 01 on the SurePatht switching module (see Figure 1–3):  
a. Align the sockets on the Option 01 with the connectors on the switching  
module.  
b. Gently seat the Option 01 into the connectors.  
c. Use the screws provided to secure the Option 01 to the switching module  
on the five standoffs.  
1–6  
Option 01 VXI Interface Module User Manual  
 
Getting Started  
Connectors  
Option 01  
Switching Module  
Connectors  
Figure 1–3: Mounting the Option 01  
1–7  
Option 01 VXI Interface Module User Manual  
 
Getting Started  
4. Make sure that the mainframe power is off.  
5. Insert the module with the Option 01 installed into one of the instrument  
slots of the mainframe (see Figure 1–4). Refer to the User Manual for the  
switching module for detailed installation instructions.  
Figure 1–4: Module Installation  
1–8  
Option 01 VXI Interface Module User Manual  
 
Getting Started  
Installation Checklist  
Installation parameters will vary depending on the mainframe being used. Be  
sure to consult the mainframe operating manual before installing and operating  
the module.  
Revision Level: __________  
Serial No.: __________  
Mainframe Slot Number:__________  
Switch Settings:__________  
VXIbus Logical Address Switch:__________  
Interrupt Level Select Switch:__________  
Cable Installed (if any):__________  
Performed by: _______________________  
Date: _____________  
1–9  
Option 01 VXI Interface Module User Manual  
 
Getting Started  
Functional Check  
The Option 01 VXI Interface Module executes a self test at power-on, on  
direction of a VXIbus hard or soft reset condition, or on command. The  
power-on self test consists of an interface self test and an instrument self test.  
The self test requested by command performs only the instrument self test. A  
VXIbus hard reset occurs when another device, such as the VXIbus Resource  
Manager, asserts the backplane line SYSRESET*. A VXIbus soft reset occurs  
when another device, such as the Option 01 commander, sets the Reset bit in the  
Option 01 Control register.  
During power-on, or a hard or soft reset, the following actions take place:  
1. The SYSFAIL* (VME system-failure) line is set active, indicating that the  
module is executing a self test, and the Failed LED is lighted. For a soft  
reset, SYSFAIL* is set. All Tektronix commanders will simultaneously set  
SYSFAIL INHIBIT to prevent the resource manager from prematurely  
reporting the failure of a card.  
2. On completion of the interface self test, SYSFAIL* is un-asserted. If the test  
fails, the SYSFAIL* line remains active. If the interface self test passed, the  
SYSFAIL* line is released, and the module enters the VXIbus PASSED state  
(ready for normal operation). If it failed, the module enters the VXIbus  
FAILED state.  
3. The instrument self test, as described in the *TST? command description is  
then executed. This tests the Option 01 VXI Interface daughter board and  
any relay modules under its control. If the self test fails, the module makes  
an internal record of the failure(s) that occur.  
The default condition of the Option 01 Module after the completion of power-on  
self test is as follows:  
All relays on modules controlled by the Option 01 (except VX4320  
Modules) are set to the normally open position.  
The VX4320 RF Multiplexer module contains eight 4-to-1 RF multiplexers.  
After a power-on self test is performed by the Option 01, it closes channel 1  
of each section of each VX4320 that it controls.  
You can run the self test at any time during normal operation by using the *TST?  
command. At the end of a self test initiated by this command, the module is  
restored to its pre-test state.  
1–10  
Option 01 VXI Interface Module User Manual  
 
Getting Started  
During a commanded self test:  
1. SYSFAIL* is not asserted.  
2. The module executes the same instrument self test as is executed upon power  
on.  
3. When the self test is completed, the modules controlled by the Option 01 are  
restored to their pre-test state.  
SYSFAIL* Operation  
SYSFAIL* becomes active during power-on, hard or soft reset, or self test, or if  
the module loses 5 V power. When the mainframe Resource Manager detects  
SYSFAIL* set, it will attempt to inhibit the line. This causes the Option 01 VXI  
Interface Module to deactivate SYSFAIL* except when +5 V power is lost on  
the relay module on which it is installed.  
1–11  
Option 01 VXI Interface Module User Manual  
 
Operating Basics  
The Option 01 VXI Interface Module is a VXIbus message-based instrument and  
communicates using the VXIbus Word Serial Protocol. The module is pro-  
grammed by issuing ASCII characters from the system controller to the Option  
01 via the module VXIbus commander and the VXIbus mainframe backplane.  
Refer to the manual for the VXIbus device that will be the Option 01 daughter  
board’s commander for details on the operation of that device.  
If the module commander is a Tektronix IEEE-488 Interface Module, refer to the  
operating manual for the module and Appendix B: Examples in this manual for  
information on how the system controller communicates with the commander  
being used.  
Functional Overview  
The Option 01 VXI Interface Module is a printed circuit board that resides on a  
C-size VXI module belonging to the Tektronix “SurePath” family of relay  
modules. This family of relay modules includes the VX4320 RF Mux, VX4330  
Scanner/Mux, VX4350 General Purpose Switch, and VX4380 Matrix modules.  
Commands conforming to the 1994 SCPI and IEEE-488.2 specifications are sent  
to the Option 01. The Option 01 parses these commands and controls the module  
on which it is installed and additional SurePath modules installed in contiguous  
slots to its right. VX4372 and VX4374 Scanner Slave modules can also be  
controlled by the Option 01.  
Power-on  
The instrument runs its self test and is ready for programming five seconds after  
power-on. The VXIbus Resource Manager can add an additional delay. The  
Power LED of each relay module controlled by the Option 01 will be on. The  
Failed LED on each of these modules will be off. The default condition of the  
module after power-on is listed in the *RST command description. Self-test  
failures are described in the *TST? command description.  
The format and syntax for the command strings are described in the Command  
Syntax section. A complete description of each command in alphabetical order is  
in the Command Descriptions section.  
2–1  
Option 01 VXI Interface Module User Manual  
 
Operating Basics  
Instrument I/O: VXIbus Basics  
NOTE. If the user’s mainframe has other manufacturers’ computer boards  
operating in the role of VXIbus foreign devices, the assertion of BERR* (as  
defined by the VXIbus Specification) may cause operating problems on these  
boards.  
The Option 01 Module, when installed on a switching module, is a C-size single  
slot VXIbus Message-Based Word Serial instrument. It uses the A16, D16 VME  
interface available on the backplane P1 connector and does not require any A24  
or A32 address space. The module is a D16 interrupter.  
The Option 01 daughter board is neither a VXIbus commander nor a VMEbus  
master; therefore it does not have a VXIbus Signal register. The Option 01 is a  
VXIbus message-based servant.  
The module supports the Normal Transfer Mode of the VXIbus using the Write  
Ready, Read Ready, Data In Ready (DIR), and Data Out Ready (DOR) bits of  
the module Response register.  
A Normal Transfer Mode read of the Option 01 daughter board proceeds as  
follows:  
1. The commander reads the Option 01 Response register and checks if the  
Write Ready and DOR bits are true. If they are, the commander proceeds to  
the next step. If not, the commander continues to poll these bits until they  
become true.  
2. The commander writes the Byte Request command (hexadecimal 0DEFF) to  
the Data Low register of the Option 01.  
3. The commander reads the Option 01 Response register and checks if the  
Read Ready and DOR bits are true. If they are, the commander proceeds to  
the next step. If not, the commander continues to poll these bits until they  
become true.  
4. The commander reads the Option 01 Data Low register.  
A Normal Transfer Mode write to the Option 01 daughter board proceeds as  
follows:  
1. The commander reads the Option 01 Response register and checks if the  
Write Ready and DIR bits are true. If they are, the commander proceeds to  
the next step. If not, the commander continues to poll the Write Ready and  
DIR bits until they are true.  
2. The commander writes the Byte Available command which contains the data  
(hexadecimal 0BCXX or 0BDXX, depending on the End bit) to the Data  
Low register of the Option 01.  
2–2  
Option 01 VXI Interface Module User Manual  
 
Operating Basics  
The module also supports the Fast Handshake Mode during readback. In this  
mode, the module is capable of transferring data at optimal backplane speed  
without needing the commander to test any of the handshake bits. The Option 01  
daughter board asserts BERR* to switch from Fast Handshake Mode to Normal  
Transfer Mode, per VXI Specification. The Option 01 Read Ready, Write Ready,  
DIR and DOR bits react properly, in case the commander does not support the  
Fast Handshake Mode.  
A Fast Handshake Transfer Mode read of the Option 01 daughter board proceeds  
as follows:  
1. The commander writes the Byte Request command (hexadecimal 0DEFF) to  
the Option 01 Data Low register.  
2. The commander reads the Option 01 Data Low register.  
A Fast Handshake Transfer Mode write of the Option 01 daughter board  
proceeds as follows:  
The commander writes the Byte Available command which contains the data  
(hexadecimal 0BCXX or 0BDXX, depending on the End bit) to the Data  
Low register of the Option 01. The commander may immediately write  
another Byte Available command without having to check the Response  
register.  
The module has no registers beyond those defined for VXIbus message based  
devices. All communications with the module are through the Data Low register,  
the Response register, or the VXIbus interrupt cycle. Any attempt by another  
module to read or write to any undefined location of the Option 01’s address  
space may cause incorrect operation of the module.  
As with all VXIbus devices, the Option 01 daughter board has registers located  
within a 64 byte block in the A16 address space. The base address of the Option  
01 device registers is determined by the device unique logical address and can be  
calculated as follows:  
Base Address = V16 * 4016 + C00016  
where V is the logical address of the device as set by the Logical Address  
switches.  
2–3  
Option 01 VXI Interface Module User Manual  
 
Operating Basics  
Configuration Registers  
Table 2–1 contains a list of the Option 01 Configuration registers and a complete  
description of each register. The offset is relative to the module base address.  
Table 2–1: Register Definitions  
Address  
(hexadecimal)  
Register  
ID Register  
Device Type  
Status  
Type  
RO  
RO  
R
Value (Bits 15–0)  
0000  
1011 1111 1111 1101 (hexadecimal BFFD)  
See Device Type definition below  
Defined by state of interface  
Defined by state of interface  
Not used  
0002  
0004  
Control  
0004  
W
Offset  
0006  
WO  
RO  
RO  
Protocol  
Response  
Data High  
Data Low  
Data Low  
0008  
1111 0111 1111 1111 (hexadecimal F7FF)  
Defined by state of the interface  
Not used  
000A  
000C  
000E  
W
R
Not fixed; command-dependent  
Not fixed; command-dependent  
000E  
RO is Read Only  
WO is Write Only  
R is Read  
W is Write  
The Register Bit definitions are listed in Tables 2–2 and 2–3.  
Table 2–2: Register Bit Definitions  
Register  
ID  
Bit Definition  
hexadecimal BFFD  
hexadecimal F7FF  
Protocol  
2–4  
Option 01 VXI Interface Module User Manual  
 
Operating Basics  
The contents of the Device register of the Option 01 Module depends on the  
model number of the relay module that it is installed on, as shown in Table 2–3.  
Table 2–3: Device Register Bit Definitions  
Relay Model No.  
VX4320  
Device Register Contents  
hexadecimal FCBF  
hexadecimal F6B5  
hexadecimal F6A1  
hexadecimal F683  
VX4330  
VX4350  
VX4380  
2–5  
Option 01 VXI Interface Module User Manual  
 
Command Syntax  
Command protocol and syntax for the Option 01 daughter board are as follows:  
H
A command string consists of a string of ASCII-encoded characters  
terminated by a <program message terminator>. The <program message  
terminator> is optional white space, followed by any one of the following  
command terminations:  
a line feed <LF> or new line <NL> character (hexadecimal 0A, decimal  
10)  
the END bit set  
the END bit with a line feed <LF> or new line <NL>  
The command string is buffered until the terminator is encountered, at which  
time the entire string is processed.  
H
In addition to terminating a command, the semi-colon character directs the  
SCPI command parser to interpret the next command with the assumption  
that all characters up to and including the last colon in the previous  
command have just been parsed. In the following example, the Option 01 is  
installed on a VX4380 Module. Two additional VX4380 Modules are  
installed in consecutive slots to the right of the first VX4380. Under these  
conditions, the commands  
route:open:all m1<LF>  
route:open:all m2<LF>  
route:open:all m3<LF>  
cause all relays on all three VX4380 Modules to open. Note that each of  
these commands is terminated by a line feed. An equivalent method of  
sending these commands using the semi-colon character as a terminator is  
route:open:all m1; all m2; all m3<LF>  
After a line feed or END bit is used to terminate a command, the parser no  
longer makes the assumption described above. Thus, after the command  
route:open:all m1; all m2<LF>  
is parsed, the command  
all m2<LF>  
is no longer valid.  
3–1  
Option 01 VXI Interface Module User Manual  
 
Command Syntax  
In the next example, the Option 01 is installed on a VX4330 Module. Two  
additional VX4330 Modules are installed in consecutive slots to the right of  
the first VX4330. The commands  
route:configure:join m1,(1:6)<LF>  
route:configure:join m2,(1:2)<LF>  
route:configure:join m3,(1:4)<LF>  
connect the commons of sections 1 through 6 on the first VX4330, sections 1  
and 2 on the second VX4330 and sections 1 through 4 on the third VX4330.  
An equivalent way to send these commands using the semi-colon as a  
terminator is  
route:configure:join m1,(1:6); join m2,(1:2); join  
m3(1:4)<LF>  
Note that <LF> in these examples represents a single line feed character.  
H
White space characters can be used to make a command string more  
readable. These characters are ASCII-encoded bytes in the range hexadeci-  
mal 00–09 and 0B–20 (decimal 0–9 and 11–32). This range includes the  
ASCII control characters and the space, but excludes the line feed <NL>.  
White space characters are ignored when legally encountered in a command  
string. White space is allowed anywhere in a command string, except for the  
following:  
Within a program mnemonic ( for example RO UTE )  
Around a colon (:) mnemonic separator (for example ROUTE: CLOSE  
or ROUTE :CLOSE)  
Between a mnemonic and a (?) (for example CLOSE ?)  
Following an asterisk (*) (for example * STB?)  
Within a number (for example 12 34)  
Within a module name specified in a [ROUTe:]MODule[:DEFine]  
command (for example ROUTE:MODULE:DEFINE RFM UX, 1).  
At least one white space character is required between a command/query  
header and its associated arguments. For example in the command  
route:configure:join m1,(1:6)  
the command header is the string “route:configure:join”. The arguments  
associated with this command are the module name “m1” and the section list  
“(1:6)”. At least one white space character must be sent before the first  
argument.  
3–2  
Option 01 VXI Interface Module User Manual  
 
Command Syntax  
In the query  
route:close? (@m1(1:64))  
the query header is the string “route:close?”. The argument associated with  
this query is the channel list “(@m1(1:64))”. At least one white space  
character must be sent before the channel list argument.  
H
H
All characters in a command can be sent in either upper or lower case form.  
Multiple data parameters passed by a command are separated by a comma  
(,).  
H
A question mark (?) following a command indicates that a response will be  
returned. All responses from the module are terminated with a carriage return  
<CR> and a line feed <LF> (hexadecimal 0A) character.  
H
In the command descriptions, the following special characters are used.  
Except for the colon (:), these characters are not part of the command and  
should not be sent. If an optional field is omitted, the default for the  
command is applied.  
[ ]  
Brackets indicate an optional field  
A bar indicates a logical OR choice  
A colon is used to separate command fields  
Field indicator  
|
:
< >  
Syntax Example  
Capital letters indicate the minimum required characters which need to be sent.  
Lower case letters are optional. For example, the syntax of the trigger source  
command is given as  
TRIGger[:SEQuence]:SOURce BUS | HOLD | IMMediate | TTLTrg<n>  
Each of the following is a valid form of this command:  
trigger:sequence:source bus  
trig:seq:sour hold  
Trig:SOUR IMM  
Trig:Sour TTLTRG1  
Trig:Sour TTLT1  
Trigger:Source Immediate  
3–3  
Option 01 VXI Interface Module User Manual  
 
Command Syntax  
SCPI/IEEE 488.2  
Command Elements  
The definition of elements used in SCPI/IEEE 488.2 commands and command  
descriptions is as follows:  
<NR1> ASCII integer representation of a decimal number.  
<NRf> ASCII integer, fixed point or floating point representation of a decimal  
number.  
<module_name> A user-defined ASCII string to be associated with the local bus  
address of a relay module. <module_name> strings must start with a letter and  
may consist of alphanumeric characters, underscores, and digits. The maximum  
length of a <module_name> is 12 characters.  
<channel_spec> One or more <NR1> ASCII strings separated by “!” characters  
that specify a relay on a relay module. The format of a <channel_spec> field for  
each of the SurePath relay modules is:  
H
VX4320 RF Multiplexer: <NR1> ! <NR1>  
The range of the first <NRf> field is 1 to 4. This field specifies a relay  
within one of the sections of the VX4320. The range of the second <NRf>  
field is 1 to 8. This field specifies a section of the VX4320. A one-dimen-  
sional <channel_spec> may also be used to specify a channel on a VX4320  
Module. The one-dimensional <channel_spec> is given by the formula:  
( (section – 1 ) × 4 ) + relay.  
where variables “section” and “relay” are section and relay numbers  
specified in a two-dimensional <channel_spec>.  
H
VX4330 Scanner/Multiplexer: <NR1> ! <NR1>  
The first <NR1> field specifies a relay within the specified section. The  
range of this <NR1> field depends on the current configuration of the section  
of the VX4330 specified in the second <NR1> field. The range of the second  
<NR1> field is 1 to 6. This field specifies a section of the VX4330.  
1 – 10  
1 – 20  
1 – 20  
1 – 40  
4-wire  
4-wire independent  
2-wire  
1-wire  
3–4  
Option 01 VXI Interface Module User Manual  
 
Command Syntax  
H
H
VX4350 General Purpose Switching module: <NR1>  
The range of this field is 1 to 64. It specifies one of 64 relays on the  
VX4350.  
VX4380 Matrix: <NR1> ! <NR1> ! <NR1>  
The range of the first <NR1> field is 1 to 4. It specifies the row of a relay in  
one of the sections of the VX4380. The range of the second <NR1> field is 1  
to 16. It specifies the column of a relay in one of the sections of the VX4380.  
The range of the third <NR1> field is 1 to 4. It specifies a section of the  
VX4380. A one dimensional <channel_spec> may also be used to specify a  
channel on a VX4380 Module. The one dimensional <channel_spec> is  
given by the formula:  
( (section – 1 ) × 64 ) + ( ( row – 1 ) × 16 ) + column  
where variables “section” and “row” and “column” are section, row, and  
column numbers specified in a three-dimensional <channel_spec>.  
<channel_list> A list of channel numbers on one or more relay modules.  
The limits on the channel numbers in a <channel_list> depend on the model  
number of the relay module(s) specified in the <channel_list>. The syntax of a  
<channel_list> is shown in the following diagram:  
<channel_range>  
!
!
:
<NR1>  
<NR1>  
<channel_list>  
,
,
(
@
<module_name>  
(
)
)
<channel_range>  
A module_name is an ASCII string that has been associated with a relay module  
in a ROUTe:MODule:DEFine command. A channel_range may consist of a  
single <channel_spec> or a range of <channel_spec>s. A range of <chan-  
nel_spec>s is indicated by two <channel_spec>s separated by a colon (:)  
character. A <channel_spec> may have one, two or three dimensions depending  
on the architecture of the relay module it applies to.  
3–5  
Option 01 VXI Interface Module User Manual  
 
Command Syntax  
The following are examples of valid <channel_list>s for Tektronix VX4320,  
VX4330, VX4350, VX4372, VX4374, and VX4380 relay modules. In these  
examples it is assumed that the Option 01 is installed on a VX4320 Module. A  
VX4330, VX4350, VX4372, VX4374, and VX4380 are installed in consecutive  
slots to the right of the VX4320. The default module names for the VX4320,  
VX4330, VX4350, VX4372, VX4374 and VX4380 in this example are m1, m2,  
m3, m4, m5, and m6 respectively. These module names may be overridden by  
specifying new module names with the [ROUTe:]MODule[DEFine] command. It  
is also assumed in these examples that all sections on the VX4330 Module have  
been configured as 10-to-1 4-wire scanners.  
<channel_list>  
(@m1(1!2))  
Channels Specified  
Channel number 1 of section 2 on the VX4320 Module.  
(@m1(4!1,3!8))  
Channel number 4 in section 1 and relay number 3 in section 8  
of the VX4320 Module.  
(@m1(4!1:4!8))  
Channel number 4 in sections 1 through 8 on the VX4320  
Module.  
(@m1(4!1,4!2,4!3,4!4,  
4!5,4!6,4!7,4!8))  
Channel number 4 in sections 1 through 8 on the VX4320  
Module.  
(@m2(1!6))  
Channel 1 in section 6 of the VX4330 Module.  
(@m2(1!1:10!6))  
All channels on the VX4330 Module in the following order: 1!1,  
1!2, 1!3, 1!4, 1!5, 1!6, 2!1, 2!2, 2!3, 2!4, 2!5, 2!6, ... , 10!1,  
10!2, 10!3, 10!4, 10!5, 10!6.  
(@m2(1!3:10!3))  
(@m3(1:64))  
All 10 channels in section 3 of the VX4330.  
All 64 channels on the VX4350  
(@m3(1,2,3,10,11,  
20:13))  
Channels 1, 2, 3, 10, 11, and 20 through 13 on the VX4350.  
(@m4(1!2))  
(@m5(3!1))  
(@m6(1!13!3))  
Channel 1 in section 2 of the VX4372.  
Channel 3 in section 1 of the VX4374.  
The channel that connects row 1 to column 13 in section 3 of  
the VX4380.  
(@m6(65))  
The channel that connects row 1 to column 1 in section 2 of  
the VX4380.  
(@m6(1!1!2))  
(@m6(1:16))  
Same as the previous example.  
The channels that connect columns 1 through 16 to row 1 in  
section 1 of the VX4380.  
(@m6(1!1!1:1!16!1))  
(@m6(1!1!1:2!3!4))  
Same as the previous example.  
Channels 1!1!1, 1!1!2, 1!1!3, 1!1!4, 1!2!1, 1!2!2, 1!2!3, 1!2!4,  
1!3!1, 1!3!2, 1!3!3, 1!3!4, 2!1!1, 2!1!2, 2!1!3, 2!1!4, 2!2!1,  
2!2!2, 2!2!3, 2!2!4, 2!3!1, 2!3!2, 2!3!3, 2!3!4 on the VX4380  
Module.  
3–6  
Option 01 VXI Interface Module User Manual  
 
Command Syntax  
As the <channel_list> syntax diagram shows, channels on more than one relay  
module may be specified in a <channel_list>. The next example specifies  
channels on three different relay modules.  
<channel_list>  
Channels Specified  
(@m1(1!1), m2(4!6),  
m6(3!13!2))  
Channel 1 of section 1 on the VX4320, Channel 4 of section 6  
of the VX4330, and the channel on the VX4380 that connects  
row 3 to column 13 in section 2.  
As mentioned above, the module names used in <channel_list>s may be  
specified with a [ROUTe:]MODule[:DEFine] command. The command  
route:module:Define rfmux, 1  
changes the module name assigned to the VX4320 to “rfmux”. The following  
<channel_list> can then be used to specify channels on the VX4320.  
(@rfmux(3!1,2!2))  
specifies channel 3 in section 1 and channel 2 in section 2 of the VX4320.  
The order in which channels are specified is important in the [ROUTe:] CLOSE?  
<channel_list> and [ROUTe:]OPEN? <channel_list> queries. The states of the  
channels are returned in the same order that the channels are specified in the  
<channel_list>.  
The order in which channels are specified is also important in the [ROUTe:]  
SCAN <channel_list> command. This determines the order in which the relays  
will be closed each time a trigger event is detected.  
The order in which channels are specified in a <channel_list> is important in the  
[ROUTe:]CLOSe <channel_list> command when channels in the same section of  
a VX4320 or a VX4330 are specified. A VX4320 can close only one channel in a  
section. If a [ROUTe:]CLOSE <channel_list> command specifies more than one  
relay in a section of a VX4320, the last channel in the <channel_list> will be  
closed.  
For example, the command  
close (@m2(1!1,2!1))  
will close channel 2 of section 1 of the VX4320.  
A VX4330 can close only one channel in a group of joined sections that have  
been specified in a [ROUTe:]CLOSe:MODe SCAN,<module_name>,<sec-  
tion_list> command. If more than one channel in such a group of sections is  
3–7  
Option 01 VXI Interface Module User Manual  
 
Command Syntax  
specified in a [ROUTe:]CLOSe <channel_list> command, the last channel  
specified will be closed. For example, the commands  
route:configure:join m2,(1:6)  
route:close:mode scan,m2,(1:6)  
join the commons of all six sections of the VX4330 Module and set the mode of  
the [ROUTe]:CLOSE <channel_list> to scan mode for all six sections of the  
VX4330.  
The command  
route:close (@m2(1!1,1!6))  
will then result in channel 1 of section 6 being closed and all other channels on  
the module being opened.  
output queue The Output queue of the Option 01 VXI Interface is used to return  
replies to queries received by the interface. Bit 4 (the MAV bit) of the Status  
Byte register is set to indicate that this queue is not empty. The DOR bit in the  
VXI Response register is also set to indicate that this queue is not empty. The  
commander of the Option 01 VXI Interface monitors the DOR bit to determine  
when it may read a message from the Output queue.  
<section_list> One or more <nr1> fields separated by comma (,) or colon (:)  
characters and enclosed in left and right parentheses. A <section_list> is used to  
specify the sections of a relay module to be acted upon by a [ROUTe:]CONFig-  
ure or [ROUTe:]CLOSe:MODE command. The following are examples of valid  
<section_list>s.  
For commands directed to a VX4330 which has six scanner sections:  
<section_list>  
(1:6)  
Sections Specified  
Sections 1 through 6  
Sections 1, 2 and 3  
(1,2,3)  
(1:3,5:6)  
(1:3,5,6)  
(3)  
Sections 1 through 3 and 5 and 6  
Same as previous example  
Section 3  
3–8  
Option 01 VXI Interface Module User Manual  
 
Command Syntax  
For commands directed to a VX4372 or VX4374 which has two scanner  
sections:  
<section_list>  
(1)  
Sections Specified  
Section 1  
(1,2)  
Sections 1 and 2  
Sections 1 and 2  
(1:2)  
error/event queue When the command parser detects a syntax error or data range  
error, it places an error message describing the error in the Error/Event queue.  
Bit 2 of the Status Byte Register is set to indicate that this queue is not empty.  
Bit 5 of the Standard Event Status Register (the Command Error bit) is set if the  
parser detects a syntax error. Bit 4 of the Standard Event Status register (the  
Execution Error bit) is set if the parser detects a numeric argument that is out of  
range. When a SYSTem:ERRor? query is received, an error message is dequeued  
from the Error/Event queue and placed in the Output queue.  
3–9  
Option 01 VXI Interface Module User Manual  
 
Functional Command Groups  
This section lists the Option 01 system and module commands.  
System Commands  
The following low-level commands are typically sent by the module’s command-  
er, and are transparent to the user of the module. (An exception is the Read STB  
command, which is sent whenever a Serial Poll on an IEEE-488 system is  
performed.) Most commanders or Slot 0 devices have specific ASCII commands  
that cause the commander to send one of these low-level commands to a  
specified instrument. Refer to the operating manual of the commander or Slot 0  
device for information on these commands.  
Command  
Effect  
Begin Normal Operation  
Byte Available  
The module begins operation if it has not already done so.  
Transfers module commands to this module.  
Byte Request  
Requests the module to return a byte of data from the output  
queue.  
Clear  
The module clears its VXIbus interface and any pending  
commands. Current module operations are unaffected.  
Clear Lock  
Read Protocol  
Read STB  
Set Lock  
Clears the Lock bit of the Response register.  
The module returns its protocol to its commander.  
The module returns its VXI status byte to its commander.  
Set the Lock bit of the Response register.  
Trigger  
Close the next relay in a scan list that has been defined by a  
ROUTe:SCAN <channel_list> command. A VXI Trigger  
command is enabled as a trigger source by a ROUTe:SE-  
Quence:SOURce BUS command.  
Module Commands  
A summary of the Option 01-specific and IEEE-488.2 Common Commands is  
listed in Tables 3–1 and 3–2 below. The next section, Command Descriptions,  
includes detailed descriptions of each command. Appendix B: Examples shows  
examples of command usage.  
3–11  
Option 01 VXI Interface Module User Manual  
 
Syntax and Commands  
Table 3–1: Summary of Option 01-Specific SCPI Commands  
Subsystem Command  
ABORt  
Functions Controlled  
Place initiated scan in the idle state  
Close specified relays; DWELl  
CLOSe  
CONFigure  
ID?  
Configuration: DISJoin, JOIN  
Return model numbers of modules controlled by the Option 01  
INITiate  
Place trigger subsystem in armed state: IMMediate,  
CONTinuous  
MODule  
MODE  
OPEN  
Module name functions: DEFine, CATalog?, DELete  
VX4330 only; set mode to scan or mux  
Open specified relays: ALL, DWELl  
OUTPut  
PFAil  
Enable or disable selected VXI TTL trigger  
Specify state of latching relays on powerfail  
Define a list of relay closures to scan through  
Status register functions: OPERation, QUESstionable  
System-level functions: ERRor?, PRESet, VERSion?  
Scan list functions: COUNt, DELay, IMMediate, SOURce  
SCAN  
STATus  
SYSTem  
TRIGger  
Table 3–2: Summary of IEEE-488.2 Common Commands  
Command/Syntax  
Description  
Clear Status  
*CLS  
Clears the SCPI and IEEE 488.2 event registers and  
the SCPI error/event queue, and the output queue.  
Standard Event Status Enable  
*ESE <NRf>  
Sets the contents of the Standard Event Status Enable  
register.  
Standard Event Status Enable Query  
*ESE?  
Returns the current value of the Standard Event  
Status Enable register in <nr1> format.  
Standard Event Status Register Query Returns the current value of the Standard Event  
*ESR?  
Status register in <nr1> format, then set the contents  
of this register to 0.  
Identification Query  
*IDN?  
Returns an ASCII string in the output queue which  
identifies the board.  
Operation Complete  
*OPC  
Sets bit 0 (the Operation Complete bit) of the  
Standard Event Status register when all pending  
device operations have been completed.  
Operation Complete Query  
*OPC?  
Places the ASCII character 1 in the output queue  
when all pending device operations have been  
completed.  
3–12  
Option 01 VXI Interface Module User Manual  
 
Syntax and Commands  
Table 3–2: Summary of IEEE-488.2 Common Commands (Cont.)  
Command/Syntax  
Description  
Reset*  
*RST  
The Option 01 VXI interface is placed in its power-up  
state with some exceptions.  
Service Request Enable  
*SRE <NRf>  
Sets the contents of the Service Request Enable  
register.  
Service Request Enable Query  
*SRE?  
Returns the current value of the Service Request  
Enable register in <nr1> format.  
Read Status Byte Query  
*STB?  
Returns the current value of the Status Byte register in  
<nr1> format.  
Trigger  
*TRG  
Equivalent to a VXI Trigger command.  
Self-Test Query  
*TST?  
Performs a self test of the Option 01 VXI Interface  
daughter board and any relay modules under its  
control. Place a “0” or “1” into the output queue to  
indicate whether the self test passed or failed.  
Wait-to-Continue  
*WAI  
Does not execute any further commands or queries  
until all pending operations have been completed.  
3–13  
Option 01 VXI Interface Module User Manual  
 
Command Descriptions  
This section lists the Option 01-specific SCPI commands and queries in  
alphabetic order. The IEEE-488.2 Common Commands are listed in the next  
section. A summary listing of the SCPI command set for the Option 01 is as  
follows:  
ABORt  
[ROUTe:]CLOSe <channel_list>  
[ROUTe:]CLOSe:DWELl <module_name>,<nrf>  
[ROUTe:]CLOSe:MODE <mode>,<module_name>,<section_list>  
[ROUTe:]CONFigure <configuration>,<module_name>,<section_list>  
[ROUTe:]CONFigure:DISJoin <module_name>  
[ROUTe:]CONFigure:JOIN <module_name>,<section_list>  
[ROUTe:]ID?  
INITiate:CONTinuous  
INITiate[:IMMediate]  
[ROUTe:]MODule[:DEFine] <module_name>,<nrf>  
[ROUTe:]MODule:CATalog?  
[ROUTe:]MODule:DELete[:NAME] <module_name>  
[ROUTe:]MODule:DELete:ALL  
[ROUTe:]OPEN <channel_list>  
[ROUTe:]OPEN:ALL [module_name]  
[ROUTe:]OPEN:DWELl <module_name>,<nrf>  
OUTPut:TTLTrg<n>[:STATe] ON | OFF | <nrf>  
[ROUTe:]PFAil <action_at_powerfail>  
[ROUTe:]SCAN <channel_list>  
STATus:OPERation:CONDition?  
STATus:OPERation:ENABle  
STATus:OPERation[:EVENt?]  
STATus:QUEStionable:CONDition?  
STATus:QUEStionable:ENABle  
STATus:QUEStionable[:EVENt?]  
SYSTem:ERRor?  
SYSTem:PRESet  
SYSTem:VERSion?  
3–15  
Option 01 VXI Interface Module User Manual  
 
Command Descriptions  
TRIGger[:SEQuence]:COUNt  
TRIGger[:SEQuence]:DELay  
TRIGger[:SEQuence][:IMMediate]  
TRIGger[:SEQuence]:SOURce BUS | HOLD | IMMediate | TTLTrg<n>  
3–16  
Option 01 VXI Interface Module User Manual  
 
Command Descriptions  
ABORt  
Command Syntax  
Query Syntax  
*RST Value  
Limits  
ABORt  
N/A  
N/A  
N/A  
Related Commands  
ROUTe:SCAN  
INITiate[:IMMediate]  
TRIGger[:SEQuence]:SOURce  
TRIGger[:SEQuence]:IMMediate  
TRIGger[:SEQuence]:COUNt  
TRIGger[:SEQuence]:DELay  
Description  
Examples  
This command places an initiated scan sequence in the idle state.  
The following example defines a scan sequence of 10 relays. The sequence is  
aborted after the third relay in the sequence is closed. In this example, module  
names m1 and m2 refer to VX4380 Modules. After a scan sequence is aborted,  
triggers are no longer accepted by the Option 01 until another INITiate [:IM-  
Mediate] command is received.  
Command  
Response  
route:scan  
(@m1(1:5),m2(60:64))  
Define a scan sequence.  
trigger:sequence:  
source hold  
This command disables the following trigger sources: VXI TTL  
triggers, VXI Trigger commands, *TRG command, Immediate  
triggers. The TRIGger[:SEQuence][:IMMediate] command,  
however, overrides this command. It triggers the module and  
skips the delay specified in a previously issued TRIGger  
[:SEQuence]:DELay command.  
initiate:immediate  
Initiate the scan sequence.  
trig  
trig  
Close the first relay in the sequence.  
Open the first relay and close the second relay in the  
sequence.  
3–17  
Option 01 VXI Interface Module User Manual  
 
Command Descriptions  
Command  
Response  
trig  
Open the second relay and close the third relay in the se-  
quence.  
abort  
Abort the scan sequence.  
3–18  
Option 01 VXI Interface Module User Manual  
 
Command Descriptions  
CLOSe  
Command Syntax  
[ROUTe:]CLOSe<channel_list>  
Query Syntax  
Query Response  
*RST Value  
[ROUTe:]CLOSe?<channel_list>  
Indicates which relays are closed.  
All relays on all modules are set to the open position.  
Limits  
The limits on the relay numbers in the <channel_list> portion of this command  
depend on the model number of the relay module(s) specified in the <chan-  
nel_list>. The syntax of a <channel_list> is described by the following diagram:  
<channel_range>  
!
!
:
<NR1>  
<NR1>  
<channel_list>  
,
,
(
@
<module_name>  
(
)
)
<channel_range>  
A module_name is an ASCII string that has been associated with a relay module  
in a ROUTe:MODule:DEFine command. A channel_range may consist of a  
single relay number or a range of relay numbers. A range of relay numbers is  
indicated by two relay numbers separated by a “:” character.  
A relay number may have one, two, or three dimensions depending on the  
architecture of the relay module containing the relay. For example, the VX4350  
contains 64 SPDT relays. Only one-dimensional relay numbers are supported for  
this module. The VX4380 Module contains four 4×16 2-wire matrices. Three-  
dimensional channel numbers are supported for this module. The first specifies  
the row, the second specifies the column, and the third specifies the matrix  
containing the relay. Multi-dimensional relay numbers are represented by  
integers separated by “!” characters. See the user manuals for the VX4320,  
3–19  
Option 01 VXI Interface Module User Manual  
 
Command Descriptions  
VX4330, VX4350, and VX4380 for more information on the format of relay  
numbers for these modules.  
Related Commands  
[ROUTe:]OPEN <channel_list>  
[ROUTe:]MODule:DEFine  
OUTPut:TTLTrg<n>[:STATe]  
Description  
Examples  
This command closes the relays specified in the <channel_list> portion of this  
command.  
In these examples the Option 01 is installed on a VX4350 Module. A VX4380  
and VX4320 are installed in consecutive slots to the right of the slot containing  
the VX4350. The default module names for the VX4350, VX4380 and VX4320  
in this configuration are m1, m2, and m3 respectively. These module names may  
be altered with the [ROUTe:]MODule:DEFine command.  
Command  
Response  
route:close (@m3(4!8)) Close relay 4 in section 8 of the VX4320 RF Mux Module.  
route:close  
(@m1(1,2,3,10:64))  
Close relays 1,2,3 and 10 through 64 on the VX4350 General  
Purpose Switch Module.  
route:close  
(@m2(3!16!4))  
Close row 3, column 16 of section 4 of the VX4380 Matrix  
Module.  
route:close  
(@m3(2!1:2!8))  
Close relay 2 in sections 1 through 8 on the VX4320 RF Mux  
Module.  
route:close  
(@m3(4!8),m2(3!16!4))  
Combined effect of examples 1 and 3.  
route:module:define  
rfmux,3  
route:close  
Close channel 3 of section 2 on the VX4320 Module after  
redefining its module name to “rfmux”.  
(@rfmux(3!2))  
route:close  
(@m2(1!1!1,4!6!2))  
Close the following relays on the VX4380 Matrix Module:  
Row  
Column Section  
1
4
1
6
1
2
route:close?  
(@m1(1,2,3,4))  
1 1 0 0  
This response indicates that relays 1 and 2 on the VX4350 are  
closed and relays 3 and 4 on this module are open.  
route:close?  
(@rfmux(3!2))  
1
This response indicates that channel 3 of section 2 of the  
VX4320 is closed. Note that a route:module:define rfmux,3  
command has been received prior to this query.  
3–20  
Option 01 VXI Interface Module User Manual  
 
Command Descriptions  
Command Syntax  
[ROUTe:]CLOSe  
:DWELl<module_name>,<nrf>  
Query Syntax  
*RST Value  
Limits  
N/A  
The close dwell time of all modules is set to 0 seconds.  
The value of the time specified in this command must be between 0 and 6.5535  
seconds.  
Related Commands  
[ROUTE:]CLOSe  
[ROUTe:]SCAN  
OUTPut:TTLTrg<n>[:STATE]  
Description  
Examples  
Set the time to wait after closing a relay before proceeding and pulsing any  
enabled VXI TTL trigger signals.  
In this example the Option 01 is installed on a VX4330 Module.  
Command  
Response  
output:ttltrg1:state  
on  
Enable VXI TTL trigger 1.  
route:close:dwell  
m1,.25  
Set the close dwell time for the VX4330 to 0.25 seconds.  
Set the open dwell time for the VX4330 to 0.5 seconds.  
route:open:dwell  
m1,0.5  
route:close  
(@m1(1!3:10!3))  
Close relays 1 through 10 in section 3 of the VX4330, wait 0.25  
seconds, then pulse VXI TTL trigger 1.  
route:scan  
(@m1(1!6:20!6))  
Define a scan list consisting of relays 1 through 20 in section 6  
of the VX4330.  
trigger:Sequence:  
source ttltrg2  
Define VXI TTL trigger 2 as the trigger source for the defined  
scan list.  
trigger:sequence:  
delay 1  
Set the trigger delay time to 1 second.  
initiate:immediate  
Initiate the scan sequence.  
3–21  
Option 01 VXI Interface Module User Manual  
 
Command Descriptions  
After this sequence, each time the VXI TTL trigger 2 is pulsed low, the  
following sequence of events occurs:  
1. One second delay. This is the delay specified in the trigger:Sequence:delay  
command.  
2. The current relay in the scan list is opened.  
3. 0.5 second delay. This is the delay specified in the route:open:dwell  
command.  
4. Close the next relay in the scan list.  
5. 0.25 second delay. This is the delay specified in the route:close:dwell  
command.  
6. Pulse VXI TTL trigger 1 low for 3 msec.  
Command Syntax  
Query Syntax  
*RST Value  
[ROUTe:]CLOSe:MODE <mode>,<module_name>,<section_list>  
N/A  
All sections of all VX4330 Modules are set to operate in the mux mode. In this  
mode one or more channels in a section may be closed at the same time.  
Limits  
This command applies only to the VX4330 Module. The section numbers in the  
<section_list> argument must be between 1 and 6.  
Related Commands  
[ROUTe:]CONFigure:JOIN  
[ROUTe:]CONFigure:DISJoin  
[ROUTE:]CONFigure  
Description  
This command is supported only for VX4330 Modules. It sets the mode of  
operation of sections on a VX4330 to scan or mux. When this command is  
received, all relays in the sections specified in the <section_list> argument are  
opened. In the mux mode, one or more relays in a section may be closed at the  
same time. When a relay is closed in a section that has been set to scan mode, all  
relays in that section are opened before the relay is closed. If several sections are  
set to operate in scan mode and the commons of these sections are joined (see the  
[ROUTe:]CONFigure:JOIN command) then when a relay is closed in any of the  
sections, all relays in all of the sections are opened first.  
3–22  
Option 01 VXI Interface Module User Manual  
 
Command Descriptions  
Examples  
In these examples the Option 01 is installed on a VX4330 Module. Two addi-  
tional VX4330 Modules are installed in consecutive slots to the right of this  
module.  
Command  
Response  
route:mode mux  
m1,(1:6)  
Set all six sections of the first VX4330 to mux mode.  
route:conf  
twire,m1,(1:6)  
Configure all six sections of the first VX4330 to 20-to-1 2-wire  
scanner/mux.  
route:close mode  
scan,m3,(1:3)  
Close the first 10 relays in section one of the first VX4330.  
Set sections 1 through 3 on the third VX4330 to scan mode.  
3–23  
Option 01 VXI Interface Module User Manual  
 
Command Descriptions  
CONFigure  
Command Syntax  
Query Syntax  
*RST Value  
[ROUTe:]CONFigure <configuration>,<module_name>,<section_list>  
N/A  
N/A  
Limits  
This command is valid only for VX4330 Scanner Modules. The section numbers  
specified in the <section_list> portion of this command must be between 1 and 6  
for this command.  
Related Commands  
Description  
[ROUTe:]CLOSe  
[ROUTe:]CLOSe:MODE  
[ROUTe:]OPEN  
Each section of a VX4330 Module may be configured as a 40-to-1 1-wire  
scanner, or as a 20-to-1 2-wire scanner/mux, or as a 10-to-1 4-wire scanner/mux.  
Also, each section may be configured as a 10-to-1 4-wire scanner with indepen-  
dent control of the upper and lower halves of the 4-wire common. The <configu-  
ration> portion of this command indicates which of these configurations is  
selected according to the following table.  
<configuration>  
OWIRE  
Configuration  
40-to-1 1-wire scanner  
20-to-1 2-wire scanner/mux  
10-to-1 4-wire scanner/mux  
TWIRE  
FWIRE  
FWIRI  
10-to-1 4-wire scanner/mux with independent control of the  
upper and lower halves of the 4-wire common.  
The <module_name> argument of the command indicates which module the  
command is directed to. The specified <module_name> is associated with a relay  
module with a [ROUTe:]MODule:DEFine command.  
The <section_list> argument indicates which sections of the selected module are  
to be configured. All relays in the section(s) specified in this list are opened  
when the [ROUTe:]CONFigure command is received.  
3–24  
Option 01 VXI Interface Module User Manual  
 
Command Descriptions  
Examples  
In these examples the Option 01 is installed on a VX4330 Module. Two addi-  
tional VX4330 Modules are installed in consecutive slots to the right of this  
module.  
Command  
Response  
route:configure  
fwire,m1,(1:6)  
Configure all six sections of the first VX4330 as 10-to-1 4-wire  
scanners.  
route:mode  
scan,m1,(1:3)  
Set the mode of operation of sections 1, 2, and 3 of the first  
VX4330 to scan. In this mode, only one channel in a section is  
closed at a time.  
route:mode  
mux,m1,(4:6)  
Set the mode of operation of sections 4, 5 and 6 of the first  
VX4330 to mux. In this mode one or more channels in a  
section may be closed at the same time.  
rout:conf owire,m3,(1) Configure section 1 of the third VX4330 as a 40-to-1 1-wire  
scanner.  
rout:conf  
twire,m2,(2,3)  
Configure sections 2 and 3 of the second VX4330 as 20-to-1  
2-wire scanners.  
route:configure  
fwiri,m3,(1:6)  
Configure all six sections of the third VX4330 as 10-to-1 4-wire  
scanners with independent control of upper and lower  
commons.  
route:close (@m3(1!1)) Connect the lower half of channel 1, section 1, to the lower half  
of the 4-wire common. In this example, section 1 is assumed to  
be configured as a 10-to-1 4-wire scanner with independent  
control of the upper and lower halves of the 4-wire common.  
route:close  
(@m3(20!1))  
Connect the upper half of the 10th channel of section 1 to the  
upper half of the 4-wire common. In this example, section 1 is  
assumed to be configured as a 10-to-1 4-wire scanner with  
independent control of the upper and lower halves of the 4-wire  
common.  
Note that in OWIRE configuration, unintended connections can be made  
between the inputs that are paired with the selected MUX inputs. When selecting  
even numbered relays for multiplexing, contact pairs for odd number relays are  
also connected together.  
In OWIRE configuration, the inputs are switched in pairs onto the two–wire bus  
of the relay section. Input 1 (relay 1a_Lo) and input 2 (relay 1a_Hi) will be  
switched at the same time, input 3 (relay 1b_Lo) and input 4 (relay 1b_Hi) will  
be switched at the same time, etc. The odd numbered inputs connect to the  
two–wire Lo bus and the even numbered inputs connect to the two–wire Hi bus.  
The Scanner/MUX one–wire output is switched to either the odd relay (Lo) or  
even relay (Hi) bus according to the last one–wire channel closed in the given  
section, or any section to which it is joined.  
3–25  
Option 01 VXI Interface Module User Manual  
 
Command Descriptions  
Scan mode: any one of the inputs can be individually connected to the  
one-wire output without any concern.  
Mux mode: any group of even inputs or any group of odd inputs can be  
connected to the one-wire output at the same time.  
OWIRE configuration: each section of the VX4330 is a 1×20 Hi wire MUX  
and a 1×20 Lo wire MUX, with switching between Hi and Low performed  
automatically.  
The VX4330 can not function as a 1×40 MUX.  
Examples  
In these examples the Option 01 is installed on a VX4330 Module.  
Command  
Response  
route:configure:join m1, (5:6)  
Connect the 4 commons of sections 5 and 6 on the VX4330.  
This joins the following pins:  
Com_5a_Lo to Com_6a_Lo  
Com_5a_Hi to Com_6a_Hi  
Com_5b_Lo to Com_6b_Lo  
Com_5b_Hi to Com_6b_Hi  
route:configure: owire,m1,  
(5:6)  
Configure sections 5 and 6 of the VX4330 as 40-to-1 1-wire  
scanners. This closes the 2-wire relays in sections 5 and 6  
joining all of the Com_xx_Lo pins together into one Lo group,  
and all of the Com_xx_Hi pins into one Hi group.  
route:mode mux,m1, (5:6)  
route:close (@m1 (1:5))  
Set the mode of operation of sections 5 and 6 of the VX4330 to  
mux.  
The In_01_Lo pin of section 5 (1:5) is connected to the Lo  
(odd) group. The inadvertent connection of In_02_Hi is made to  
the Hi (even) group.  
route:close (@m1 (4:6))  
Note the unexpected result here because we attempted to  
connect both even and odd inputs. The 1Wire_5a and  
1Wire_6a pins are now connected to the Hi (even) group to  
connect (4:6). But (2:5) is now connected instead of the  
original (1:5).  
Command Syntax  
[ROUTe:]CONFigure  
:DISJoin <module_name>  
Query Syntax  
*RST Value  
N/A  
All sections on all scanner modules are disjoined.  
3–26  
Option 01 VXI Interface Module User Manual  
 
Command Descriptions  
Limits  
N/A  
Related Commands  
[ROUTe:]CONFigure:JOIN  
[ROUTE:]CONFigure  
[ROUTe:]CLOSe:MODE  
Description  
Examples  
Disconnect the commons of all sections of a scanner module. This command is  
supported for VX4330, VX4372, and VX4374 Modules.  
In these examples the Option 01 is installed on a VX4330 Module. Two addi-  
tional VX4330 Modules are installed in consecutive slots to the right of this  
module. A VX4374 is installed in the slot to the right of the third VX4330.  
Command  
Response  
route:configure:  
disjoin m1  
Disconnect the commons of the first VX4330.  
rout:conf:disj m4  
Disconnect the commons of the two sections of the VX4374.  
Command Syntax  
[ROUTe:]CONFigure  
:JOIN <module_name>,<section_list>  
Query Syntax  
*RST Value  
Limits  
N/A  
All sections on all scanner modules are disjoined.  
This command is supported for VX4330, VX4374, and VX4372 Modules. The  
section numbers specified in the <section_list> argument must be between 1 and  
6 for VX4330 modules. Section numbers 1 and 2 are valid for VX4374 and  
VX4372 Modules.  
Related Commands  
Description  
[ROUTe:]CONFigure:DISJoin,  
[ROUTE:]CONFigure,  
[ROUTe:]MODE  
This command connects the commons of adjacent sections on scanner modules.  
On VX4330 modules, if a section that is configured as a 4-wire scanner is joined  
to a section that is configured as a 1-wire or 2-wire scanner, only the lower half  
of the 4-wire scan common is connected. If a 4-wire section is joined to another  
4-wire section, both halves of the 4-wire scan common are joined. Also for the  
3–27  
Option 01 VXI Interface Module User Manual  
 
Command Descriptions  
VX4330, if two or more sections that are set to scan mode are joined, then when  
a [ROUTe:]CLOSe command closes a relay in one of these sections, all relays in  
the sections are opened before the specified relay is closed.  
Examples  
In these examples the Option 01 is installed on a VX4330 Module. Two addi-  
tional VX4330 Modules are installed in consecutive slots to the right of this  
module. A VX4374 is installed in the slot to the right of the third VX4330.  
Command  
Response  
route:configure:join  
m1,(1:3)  
Connect the commons of sections 1, 2, and 3 on the first  
VX4330.  
rout:conf:join  
m4,(1:2)  
Connect the commons of the two sections of the VX4374.  
route:close:mode  
scan,m2,(1:4)  
Set the mode of operation of sections 1 through 4 on the  
second VX4330 to scan mode. In this mode, only one relay is a  
section is closed at a time.  
route:conf  
twire,m2,(1:4)  
Configure sections 1 through 4 on the second VX4330 as  
20-to-1 2-wire scanners.  
route:conf:join  
m2,(1:4)  
Connect the commons of sections 1 through 4 on the second  
VX4330. Since these sections have been set to operate in the  
scan mode, and have been configured as 20-to-1 2-wire  
scanners, these sections now comprise a single 80-to-1 2-wire  
scanner.  
route:close  
(@m2(10!1))  
Close channel 10 of section 1 of the second VX4330.  
route:close (@m2(2!4)) Close channel 2 of section 4 of the second VX4330. Since the  
first four sections of this module are joined and are set to  
operate in the scan mode, all relays in sections 1 through 4 of  
this module are opened before this relay is closed.  
3–28  
Option 01 VXI Interface Module User Manual  
 
Command Descriptions  
ID?  
Command Syntax  
*RST Value  
[ROUTe:]ID?  
N/A  
Limits  
N/A  
Related Commands  
Description  
[ROUTe:]MODule:CATalog?  
This query returns a list of the model numbers of the modules controlled by the  
Option 01. The first model number returned is that of the module that the Option  
01 is installed on. Subsequent model numbers are those of modules in consecu-  
tive slots to the right of the first module.  
Examples  
In these examples the Option 01 is installed on a VX4350 Module. A VX4380,  
VX4330, and VX4320 are installed in consecutive slots to the right of the slot  
containing the VX4350. The default module names for the VX4350, VX4380,  
VX4330 and VX4320 in this configuration are m1, m2, m3, and m4 respectively.  
These module names may be altered with the [ROUTe:]MODule:DEFine com-  
mand.  
Command  
Response  
route:id?  
VX4350, VX4380, VX4330, VX4320  
“M1”, “M2”, “M3”, “M4”  
route:module:Catalog?  
route:close (@m1(1))  
route:open:all m2  
Close relay number 1 on the VX4350.  
Open all relays on the VX4380.  
route:close (@m3(1!6)) Close relay number 1 in section 6 of the VX4330  
route:close  
(@m4(3!1:3!8))  
Close relay number 3 in all eight sections of the VX4320.  
3–29  
Option 01 VXI Interface Module User Manual  
 
Command Descriptions  
INITiate  
Command Syntax  
INITiate  
[:IMMediate]  
Query Syntax  
Query Response  
*RST Value  
N/A  
N/A  
The trigger subsystem is in the idle state.  
Related Commands  
ABORt  
ROUTe:SCAN  
TRIGger[:SEQuence][:SOURce]  
TRIGger[:SEQuence][:IMMediate]  
TRIGger[:SEQuence][:COUNt]  
TRIGger[:SEQuence][:DELay]  
Description  
Examples  
This command places the trigger subsystem in the armed state. In this state, a  
trigger event enabled by the TRIGger[:SEQuence]:SOURce command closes the  
next relay in a scan sequence, after opening the previous relay in the sequence.  
After a sufficient number of triggers have been received to cycle through a scan  
list the number of times specified in a TRIGger:[SEQuence] :COUNt command,  
the trigger subsystem is placed in the idle state. In this state, triggers are ignored.  
Command  
Response  
route:scan  
(@m1(1,2),m2(60))  
Define a scan sequence consisting of relays 1 and 2 on relay  
module m1 and relay 60 on module m2.  
trigger:sequence:count Define the number of times to sequence through the scan list  
1
before setting the state of the trigger subsystem back to the  
idle state.  
trigger:sequence:  
source hold  
This command disables the following trigger sources: VXI TTL  
triggers, VXI Trigger commands, *TRG command, and  
Immediate triggers. The TRIGger[:SEQuence][:IMMediate]  
command, however, overrides this command. It triggers the  
module and skips the delay specified in a previously issued  
TRIGger[:SEQuence]:DELay command.  
initiate:immediate  
trig  
Initiate the scan sequence.  
Close the first relay in the sequence.  
3–30  
Option 01 VXI Interface Module User Manual  
 
Command Descriptions  
Command  
Response  
trig  
Open the first relay and close the second relay in the  
sequence.  
trig  
trig  
Open the second relay and close the third relay in the  
sequence.  
Open the third relay in the sequence. Place the trigger  
subsystem in the idle state.  
Command Syntax  
INITiate  
:CONTinuous  
Query Syntax  
Query Response  
*RST Value  
N/A  
N/A  
The trigger subsystem is placed in the IDLE state.  
Related Commands  
ABORt  
[ROUTe:]SCAN  
TRIGger[:SEQuence]:SOURce  
TRIGger[:SEQuence]:IMMediate  
TRIGger[:SEQuence]:DELay  
Description  
Examples  
If a scan list has been defined by a [ROUTe:]SCAN command, this command  
places the trigger subsystem in the armed state. In this state, a trigger event  
enabled by the TRIGger[:SEQuence]:SOURce command opens the currently  
closed channel in a scan list and closes the next channel in the list. Triggers  
continue to be recognized until an ABORt command is received, which returns  
the trigger subsystem to the IDLE state.  
In this example, it is assumed that the Option 01 daughter board is installed on a  
VX4330 Module and that the default module name “m1” is in effect.  
Command  
Response  
conf twire,m1,(1)  
scan (@m1(1!1:20!1))  
Set the configure section 1 of the VX4330 to 20-to-1 twire.  
Define a scan list consisting of channels 1 through 20 in  
section on of the VX4330 Module.  
trigger:Sequence:count Set the number of times to sequence through a scan list (when  
an INITiate[:IMMediate] command is received) to 2.  
2
3–31  
Option 01 VXI Interface Module User Manual  
 
Command Descriptions  
Command  
Response  
trigger:sequence:  
source hold  
Disable all trigger sources.  
initiate:continuous  
trigger:seq:imm  
Place the trigger subsystem in the arm state.  
Override the hold placed on triggers. Close channel 1 in  
section 1 of the VX4330.  
trigger:seq:imm  
Override the hold placed on triggers. Open channel 1 in section  
1, then close channel 2 in section 1 of the VX4330.  
trigger:seq:sour imm  
Remove the hold placed on triggers. Set the trigger source to  
immediate. This causes the sequencing of the scan list  
indefinitely or until an ABORt command is received.  
ABOR  
Return the trigger subsystem to the idle state. Open the  
currently closed relay in the scan list.  
initiate:immediate  
Place the trigger subsystem in the arm state, sequence through  
the scan list twice, then return the trigger subsystem to the idle  
state.  
3–32  
Option 01 VXI Interface Module User Manual  
 
Command Descriptions  
MODule  
Command Syntax  
[ROUTe:]MODule  
[:DEFine] <module_name>,<nrf>  
Query Syntax  
[ROUTe:]MODule  
[:DEFine]? <module_name>  
Query Response  
*RST Value  
See examples.  
Default module names are assigned as follows:  
The module that has a Option 01 VXI Interface daughter board installed is  
assigned module name “M1”.  
Modules without the Option 01 VXI Interface daughter board in consecutive  
slots to the right of module “M1” are assigned module names “M2”, “M3”, ...,  
“M11”.  
Limits  
A module name may consist of up to 12 characters. The name must start with a  
letter and may consist of alphanumeric characters, underscores, and digits.  
Related Commands  
[ROUTe]:MODule:DELete[:NAME]  
[ROUTe]:MODule:DELete:ALL  
[ROUTe:]MODule:CATalog?  
Description  
Examples  
This command assigns a module name to a relay switching module. This name is  
used to identify the module in channel lists in [ROUTe:]OPEN,  
[ROUTe:]CLOSe, and [ROUTe:]SCAN commands.  
In these examples the Option 01 is installed on a VX4350 Module. A VX4380  
and VX4330 are installed in consecutive slots to the right of the slot containing  
the VX4350.  
Command  
Response  
route:module:define  
gp_switch,1  
Assign module name “gp_switch” to the VX4350.  
route:close  
(@gp_switch(1:64))  
Close all 64 relays on the VX4350.  
3–33  
Option 01 VXI Interface Module User Manual  
 
Command Descriptions  
Command  
Response  
route:module:define  
matrix,2  
Assign module name “matrix” to the VX4380.  
route:close (@matrix  
(4!16!3))  
Close the relay at row 4 column 16 in section 3 of the VX4380.  
1
route:module:define?  
gp_switch  
Command Syntax  
[ROUTe:]MODule  
:CATalog?  
*RST Value  
Limits  
N/A  
N/A  
Related Commands  
[ROUTe]:MODule:DEFine[:NAME]  
[ROUTe]:MODule:DELete[:NAME],  
[ROUTe]:MODule:DELete:ALL  
Description  
Examples  
This command returns a list of defined module names.  
In these examples the Option 01 is installed on a VX4350 Module. A VX4380  
and VX4330 are installed in consecutive slots to the right of the slot containing  
the VX4350.  
Command  
Response  
route:module:catalog?  
“M1”, “M2”, “M3”  
route:module:define  
matrix_1,2  
Assign module name “matrix_1” to the VX4380.  
route:module:catalog?  
“M1”, “MATRIX_1”, “M3”  
2
route:module:define?  
matrix_1  
route:module:delete  
matrix_1  
Delete module name “matrix_1”  
“M1”, “M3”  
route:module:catalog?  
3–34  
Option 01 VXI Interface Module User Manual  
 
Command Descriptions  
Command Syntax  
[ROUTe:]MODule  
:DELete  
[:NAME] <module_name>  
Query Syntax  
*RST Value  
N/A  
N/A  
N/A  
Limits  
Related Commands  
[ROUTe]:MODule:DEFine[:NAME]  
[ROUTe]:MODule:CATalog?  
[ROUTe:]MODule:DELete[:ALL]  
Description  
Examples  
This command deletes a module name definition. After this command is  
executed, the specified module name is no longer associated with a relay  
module.  
Command  
Response  
route:module:catalog?  
“M1”, “M2”, “M3”  
route:module:delete m1 Delete module name “M1”  
route:module:catalog?  
“M2”, “M3”  
Command Syntax  
[ROUTe:]MODule  
:DELete  
:ALL  
Query Syntax  
*RST Value  
Limits  
N/A  
N/A  
N/A  
3–35  
Option 01 VXI Interface Module User Manual  
 
Command Descriptions  
Related Commands  
[ROUTe]:MODule:DEFine[:NAME]  
[ROUTe]:MODule:CATalog?  
[ROUTe:]MODule:DELete[:NAME]  
Description  
Examples  
This command will delete all module name definitions.  
Command  
Response  
route:module:catalog?  
“M1”, “M2”, “M3”  
Delete all module names  
route:module:deĆ  
lete:all  
route:module:catalog?  
“ ”  
3–36  
Option 01 VXI Interface Module User Manual  
 
Command Descriptions  
OPEN  
Command Syntax  
Query Syntax  
Query Response  
*RST Value  
[ROUTe:]OPEN <channel_list>  
[ROUTe:]OPEN? <channel_list>  
See examples.  
All relays on all modules are set to the open position.  
Limits  
The limits on the relay numbers in the <channel_list> portion of this command  
depend on the model number of the relay module(s) specified in the <chan-  
nel_list>. The syntax of a <channel_list> is described by the following diagram:  
<channel_range>  
!
!
:
<NR1>  
<NR1>  
<channel_list>  
,
,
(
@
<module_name>  
(
)
)
<channel_range>  
A module_name is an ASCII string that has been associated with a relay module  
in a ROUTe:MODule:DEFine command. A channel_range may consist of a  
single relay number or a range of relay numbers. A range of relay numbers is  
indicated by two relay numbers separated by a “:” character.  
A relay number may have one, two, or three dimensions depending on the  
architecture of the relay module containing the relay. For example, the VX4350  
contains 64 SPDT relays. Only one-dimensional relay numbers are supported for  
this module. The VX4380 Module contains four 4 × 16 2-wire matrices.  
Three-dimensional channel numbers are supported for this module. The first  
specifies the row, the second specifies the column and the third specifies the  
matrix containing the relay. Multi-dimensional relay numbers are represented by  
integers separated by “!” characters. See the manuals for the VX4330, VX4350,  
3–37  
Option 01 VXI Interface Module User Manual  
 
Command Descriptions  
and VX4380 for more information on the format of relay numbers for these  
modules.  
The [ROUTe:]OPEN command is not supported for the VX4320 Module. This  
module contains eight 4-to-1 RF multiplexors. One and only one channel in each  
multiplexor is closed at all times.  
Related Commands  
Description  
[ROUTe:]CLOSe <channel_list>  
[ROUTe:]MODule:DEFine  
This command closes the relays specified in the <channel_list> portion of this  
command.  
Examples  
In these examples the Option 01 is installed on a VX4350 Module. A VX4380  
and VX4330 are installed in consecutive slots to the right of the slot containing  
the VX4350. The default module names for the VX4350, VX4380, and VX4330  
in this configuration are m1, m2, and m3 respectively. These module names may  
be altered with the [ROUTe:]MODule:DEFine command.  
Command  
Response  
route:open (@m3(4!6))  
Open relay 4 in section 6 of the VX4330 Scanner Module.  
route:open  
(@m1(1,2,3,10:64))  
Open relays 1,2,3 and 10 through 64 on the VX4350 General  
Purpose Switch Module.  
route:open  
(@m2(3!16!4))  
Open row 3, column 16 of section 4 of the VX4380 Matrix  
Module.  
route:open  
(@m3(2!1:2!3))  
Open relay 2 in sections 1 through 3 on the VX4330 Scanner  
Module.  
route:open  
(@m3(4!6),m2(3!16!4))  
Combined effect of examples 1 and 3.  
route:module:define  
scanner,3  
Open channel 3 of section 2 on the VX4330 Module after  
redefining its module name to “scanner”.  
route:open (@scanner  
(3!2))  
route:open  
(@m2(1!1!1,4!6!2))  
Open the following relays on the VX4380 matrix Module:  
Row  
Column Section  
1
4
1
6
1
2
3–38  
Option 01 VXI Interface Module User Manual  
 
Command Descriptions  
Command  
Response  
route:open?  
(@m1(1,2,3,4))  
1 1 0 0  
This response indicates that relays 1 and 2 on the VX4350 are  
open and relays 3 and 4 on this module are closed.  
route:open? (@scanner  
(3!2))  
1
This response indicates that channel 3 of section 2 of the  
VX4320 is open. Note that a route:module:define scanner,3  
command has been received prior to this query.  
Command Syntax  
[ROUTe:]OPEN  
:ALL [module_name]  
Query Syntax  
*RST Value  
N/A  
All relays on all modules are set to the open position.  
N/A  
Limits  
Related Commands  
[ROUTe:]CLOSe  
[ROUTe:]MODule:DEFine  
Description  
If a module name is not specified in this command, open all relays on all  
modules controlled by the Option 01. If a module name is specified, open all  
relays on the specified module only. In either case do not change the state of the  
configuration relays on VX4330 Modules.  
The [ROUTe:]OPEN command is not supported for the VX4320 Module. This  
module contains eight 4-to-1 RF multiplexors. One and only one channel in each  
multiplexor is closed at all times.  
Command  
Response  
Examples  
ROUTE:OPEN:ALL  
Open all relays on all Modules controlled by the VX4300. Do  
not change the state of the configuration relays on VX4330  
Modules.  
rout:open:all  
Same as the first example.  
route:open:all gp  
Open all relays on the module that has been assigned module  
name “gp”. See the [ROUTe:]MODule:DEFine command.  
3–39  
Option 01 VXI Interface Module User Manual  
 
Command Descriptions  
Command Syntax  
[ROUTe:]OPEN  
:DWELl <module_name>,<nrf>  
Query Syntax  
*RST Value  
Limits  
N/A  
The open dwell time of all modules is set to 0 seconds.  
The value of the time specified in this command must be between 0 and 6.5535  
seconds.  
Related Commands  
[ROUTE:]OPEN  
[ROUTe:]SCAN  
Description  
Examples  
This command sets the time to wait after opening a relay before proceeding.  
In the following example the Option 01 is installed on a VX4330 Module.  
Command  
Response  
output:ttltrg1:state  
on  
Enable VXI TTL trigger 1.  
route:close:dwell  
m1,.25  
Set the close dwell time for the VX4330 to 0.25 seconds.  
Set the open dwell time for the VX4330 to 0.5 seconds.  
route:open:dwell  
m1,0.5  
route:scan  
(@m1(1!6:20!6))  
Define a scan list consisting of relays 1 through 20 in section 6  
of the VX4330.  
trigger:Sequence:  
source ttltrg2  
Define VXI TTL trigger 2 as the trigger source for the defined  
scan list.  
trigger:sequence:delay Set the trigger delay time to 1 second.  
1
initiate:immediate  
Initiate the scan sequence.  
After this sequence, each time the VXI TTL trigger 2 is pulsed low, the  
following sequence of events occurs:  
1. One second delay. This is the delay specified in the trigger:Sequence:delay  
command.  
2. The current relay in the scan list is opened.  
3–40  
Option 01 VXI Interface Module User Manual  
 
Command Descriptions  
3. 0.5 second delay. This is the delay specified in the route:open:dwell  
command.  
4. Close the next relay in the scan list.  
5. 0.25 second delay. This is the delay specified in the route:close:dwell  
command.  
6. Pulse VXI TTL trigger 1 low for 3 msec.  
3–41  
Option 01 VXI Interface Module User Manual  
 
Command Descriptions  
OUTPut  
Command Syntax  
OUTPut  
:TTLTrg<n>  
[:STATe] ON | OFF | <nrf>  
Query Syntax  
OUTPut  
:TTLTrg<n>  
[:STATe]?  
Query Response  
*RST Value  
Indicates whether a VXI TTL trigger is enabled.  
All VXI TTL triggers are disabled.  
Related Commands  
ROUTe:CLOSe  
ROUTe:SCAN  
Description  
Examples  
One or more VXI TTL triggers may be enabled. Triggers that are enabled are  
pulsed low for 3 msec after a relay is closed by the Option 01 after a time  
specified by the ROUTe:CLOSe:DWELl command.  
Command  
Response  
output:ttltrg1:state  
on  
Enable driving VXI TTL trigger 1.  
outp:ttlt2 off  
Disable driving VXI TTL trigger 2.  
Enable driving VXI TTL trigger 7.  
outp:ttlt7:stat 1  
output:ttltrg4:state?  
1
This response indicates that VXI TTL trigger 4 is enabled.  
3–42  
Option 01 VXI Interface Module User Manual  
 
Command Descriptions  
PFAil  
Command Syntax  
Query Syntax  
*RST Value  
[ROUTe:]PFAil <action_at_powerfail>  
N/A  
All relays on all modules are opened when power is removed from the VXI  
chassis.  
Limits  
Related Commands  
Description  
N/A  
N/A  
This command specifies the state that all latching relays on all modules  
controlled by the Option 01 are to be placed in when power is removed from the  
VXI chassis containing the modules. <action_at_powerfail> must be OPEN or  
SAME. If OPEN is specified, all latching relays are opened at powerfail. If  
SAME is specified, all latching relays are left in their current state at powerfail.  
NOTE. VXI chassis +5 V power is maintained for 4 milliseconds after ACFAIL is  
asserted, in compliance with VXI Specifications. This allows for orderly system  
shutdown and implementation of the PFAil OPEN option.  
Command  
Response  
Examples  
route:pfail same  
route:pfail open  
Leave all latching relays in their current state at powerfail.  
Open all latching relays at powerfail.  
3–43  
Option 01 VXI Interface Module User Manual  
 
Command Descriptions  
SCAN  
Command Syntax  
Query Syntax  
*RST Value  
Limits  
[ROUTe:]SCAN <channel_list>  
N/A  
No scan list is defined.  
The limits on the relay numbers in the <channel_list> portion of this command  
depend on the model number of the relay module(s) specified in the <chan-  
nel_list>. The syntax of a <channel_list> is described by the following diagram:  
<channel_range>  
!
!
:
<NR1>  
<NR1>  
<channel_list>  
,
,
(
@
<module_name>  
(
)
)
<channel_range>  
A module_name is an ASCII string that has been associated with a relay module  
in a ROUTe:MODule:DEFine command. A channel_range may consist of a  
single relay number or a range of relay numbers. A range of relay numbers is  
indicated by two relay numbers separated by a “:” character.  
A relay number may have one, two, or three dimensions depending on the  
architecture of the relay module containing the relay. For example, the VX4350  
contains 64 SPDT relays. Only one-dimensional relay numbers are supported for  
this module. The VX4380 Module contains four 4 × 16 2-wire matrices. Three-  
dimensional channel numbers are supported for this module. The first specifies  
the row, the second specifies the column, and the third specifies the matrix  
containing the relay. Multi-dimensional relay numbers are represented by  
integers separated by “!” characters. See the user manuals for the VX4320,  
VX4330, VX4350, and VX4380 for more information on the format of relay  
numbers for these modules.  
3–44  
Option 01 VXI Interface Module User Manual  
 
Command Descriptions  
Related Commands  
TRIGger[:SEQuence]:SOURce  
TRIGger[:SEQuence]:COUNt  
TRIGger[:SEQuence]:DELay  
TRIGger[:SEQuence]:IMMediate  
INITiate[:IMMediate]  
[ROUTe:]CLOSe:DWELl  
[ROUTe:]OPEN:DWELl  
Description  
This command defines a list of relay closures to sequence through. This list is  
called a scan list. When the ROUTe:SCAN <channel_list> command is received,  
all relays in this list are opened. In addition to defining a scan list, a trigger  
source must be specified using the TRIGger[:SEQuence]:SOURce command.  
Trigger events are not recognized until triggers are armed by an INITiate  
[:IMMediate] or INITiate:CONTinuous command.  
When the first trigger event is detected, the first relay in the scan list is closed.  
When the second trigger event is detected, the first relay is opened and the  
second relay is closed. When the nth trigger event is detected, the (n–1)th relay is  
opened and the nth relay is closed. The act of opening the (n–1)th relay and  
closing the nth relay is called sequencing the scan list. At any given time after  
the first trigger event is detected, only one relay in the scan list is closed.  
The TRIGger[:SEQuence]:COUNt command may optionally be used to specify  
the number of times to sequence through the entire scan list. The TRIGger  
[:SEQuence]:DELay, [ROUTe:]CLOSe:DWELl, and [ROUTe:]OPEN:DWELl  
commands may optionally be used to specify the time to wait after a trigger  
event is detected, a relay is closed or a relay is opened. A TRIGger[:SEQuence]  
[:IMMediate] command causes the scan list to be sequenced without the delay  
specified by a previously issued TRIGger[:SEQuence]:DELay command.  
Examples  
In these examples the Option 01 is installed on a VX4350 Module. A VX4380  
and VX4330 are installed in consecutive slots to the right of the slot containing  
the VX4350.  
Command  
Response  
route:module:define  
gp,1  
Assign module name “gp” to the VX4350.  
route:module:define  
matrix,2  
Assign module name “matrix” to the VX4380.  
Assign module name “scan” to the VX4330.  
route:module:define  
scan,3  
route:scan  
Define a scan list consisting of relays 1 through 64 on the  
VX4350, relays at row 1, column 1 of section 1 and row 2,  
column 10 of section 3 of the VX4380 and relays 1 through 20  
of section 1 of the VX4330.  
(@gp(1:64),maĆ  
trix(1!1!1, 2!10!3),  
scan(1!1:20!1))  
3–45  
Option 01 VXI Interface Module User Manual  
 
Command Descriptions  
Command  
Response  
trigger:sequence:  
source immediate  
Define a trigger source of “immediate”. This means to  
sequence through the scan list without waiting for a trigger  
event.  
trigger:sequence:count Sequence through the entire scan list five times.  
5
route:close:dwell  
gp,.5  
Wait 0.5 seconds after closing a relay on the VX4350.  
initiate:immediate  
*OPC  
Begin sequencing through the scan list.  
Set the Operation Complete bit of the Standard Event Status  
register after sequencing through the scan list five times.  
3–46  
Option 01 VXI Interface Module User Manual  
 
Command Descriptions  
STATus  
Command Syntax  
STATus  
:OPERation  
:CONDition?  
*RST Value  
Limits  
0
N/A  
N/A  
Related Commands  
Description  
This query returns the contents of the SCPI Status Operation Condition register.  
For the Option 01, the value of this register is always equal to 0.  
Command  
Response  
Examples  
status:operation:  
condition?  
00000  
Command Syntax  
STATus  
:OPERation  
:ENABle  
Query Syntax  
STATus:  
OPERation  
:ENABle?  
*RST Value  
Limits  
0
N/A  
N/A  
Related Commands  
Description  
This command sets the contents of the SCPI Status Operation Event Enable  
register.  
3–47  
Option 01 VXI Interface Module User Manual  
 
Command Descriptions  
Command  
Response  
Examples  
status:operation:  
enable 1  
stat:oper:enab?  
00001  
Command Syntax  
STATus  
:OPERation  
[:EVENt?]  
*RST Value  
Limits  
0
N/A  
N/A  
Related Commands  
Description  
This query returns the contents of the SCPI Status Operation Event register. For  
the Option 01, the value of this register is always equal to 0.  
Command  
Response  
Examples  
status:operation:  
event?  
00000  
Command Syntax  
STATus  
:QUEStionable  
:CONDition?  
*RST Value  
Limits  
0
N/A  
N/A  
Related Commands  
Description  
This query returns the contents of the SCPI Status Questionable Condition  
register. For the Option 01, the value of this register is always equal to 0.  
3–48  
Option 01 VXI Interface Module User Manual  
 
Command Descriptions  
Command  
Response  
Examples  
status:questionable:  
condition?  
00000  
Command Syntax  
STATus  
:QUEStionable  
:ENABle  
Query Syntax  
STATus  
:QUEStionable  
:ENABle?  
Query Response  
*RST Value  
Indicates whether the Status Operation Event is enabled.  
0
Limits  
N/A  
N/A  
Related Commands  
Description  
This command sets the contents of the SCPI Status Operation Event Enable  
register.  
Command  
Response  
Examples  
status:questionable:  
enable 1  
stat:ques:enab?  
00001  
3–49  
Option 01 VXI Interface Module User Manual  
 
Command Descriptions  
Command Syntax  
STATus  
:QUEStionable  
[:EVENt?]  
*RST Value  
Limits  
0
N/A  
N/A  
Related Commands  
Description  
This query returns the contents of the SCPI Status Questionable Event register.  
For the Option 01, the value of this register is always equal to 0.  
Command  
Response  
Examples  
status:questionable:  
event?  
00000  
3–50  
Option 01 VXI Interface Module User Manual  
 
Command Descriptions  
SYSTem  
Command Syntax  
SYSTem  
:ERRor?  
Query Response  
Each response is terminted with a carriage return <CR> and a line feed<LF>.  
0,“No error”  
–102, “Syntax error; 1 dimensional <channel_spec> invalid for VX4330  
module”  
–102, “Syntax error; 2 dimensional <channel_spec> invalid for VX4350  
module”  
–102, “Syntax error; 3 dimensional <channel_spec> invalid for VX43xx  
module”  
–102, “Syntax error; channel dimension mismatch”  
–102, “Syntax error; integer field greater than 10 characters”  
–102, “Syntax error; Missing module name”  
–102, “Syntax error; Module address not specified”  
–102, “Syntax error; Module name already defined”  
–102, “Syntax error; Module name length greater than 12 characters”  
–102, “Syntax error; Non-contiguous section numbers”  
–102, “Syntax error; ROUTe:CONFigure command invalid for VX43xx module”  
–102, “Syntax error; ROUTe:DISJoin command invalid for VX43xx module”  
–102, “Syntax error; ROUTe:JOIN command invalid for VX43xx module”  
–102, “Syntax error; ROUTe:MODE command invalid for VX43xx module”  
–102, “Syntax error; Undefined module name”  
–102, “Syntax error; Unexpected x detected while ...”  
–121, “Invalid character in number”  
–123, “Exponent too large”  
–200, “Execution error; Reserved”  
–200, “Execution error; Scan list undefined”  
3–51  
Option 01 VXI Interface Module User Manual  
 
Command Descriptions  
–211, “Trigger ignored”  
–213, “Init ignored”  
–222, “Data out of range; Channel number x on module y”  
–222, “Data out of range; Channel number x!x on module y”  
–222, “Data out of range; Channel number x!x!x on module y”  
–222, “Data out of range; Invalid module address specified”  
–222, “Data out of range; Invalid section number”  
–222, “Data out of range; Invalid sequence count”  
–222, “Data out of range; Invalid trigger delay”  
–222, “Data out of range; Invalid VXI TTL Trigger level”  
–222, “Data out of range; Maximum value for ESE command is 255”  
–222, “Data out of range; Maximum value for SRE command is 255”  
–222, “Data out of range; Invalid dwell time specified.”  
–223, “Too much data; Channel list array overflow”  
–223, “Too much data; Input buffer overflow”  
–223, “Too much data; Output buffer full”  
–223, “Too much data; Scan list array overflow”  
–240, “Hardware error; Shift register verification error – module y”  
–240, “Hardware error; Unrecognized module x, y”  
–350, “Queue overflow; Error/event queue”  
–350, “Queue overflow; Output queue”  
*RST Value  
The error/event queue is empty.  
N/A  
Limits  
Related Commands  
*ESR?  
*STB?  
3–52  
Option 01 VXI Interface Module User Manual  
 
Command Descriptions  
Description  
If an error condition is detected by the Option 01, it places an error message  
describing the condition in the error/event queue. The SYSTem:ERRor? query  
requests the Option 01 to remove the oldest message in the error/event queue and  
place it into the output queue. If the error/event queue is empty, a “No error”  
message is placed in the output queue.  
Command  
Response  
Examples  
SYSTEM:ERROR?  
syst:err?  
0, “No error”  
–222,“Data out of range; Invalid section number”  
Command Syntax  
SYSTem:  
PRESet  
Query Syntax  
*RST Value  
N/A  
N/A  
Limits  
N/A  
Related Commands  
Description  
ROUTe:OPEN:ALL  
Channel 1 of all sections on all VX4320 Modules is closed. All relays on all  
modules (except VX4320 Modules) are set to the open position. The PON bit of  
the Standard Event Status register is not affected by this command.  
Command  
Response  
no response  
no response  
Examples  
system:preset  
syst:pres  
Command Syntax  
SYSTem  
:VERSion?  
*RST Value  
Limits  
N/A  
N/A  
3–53  
Option 01 VXI Interface Module User Manual  
 
Command Descriptions  
Related Commands  
Description  
None  
This query returns the following ASCII string in the output queue:  
“1994.0”  
Command  
Response  
“1994.0”  
“1994.0”  
Examples  
system:version?  
syst:vers?  
3–54  
Option 01 VXI Interface Module User Manual  
 
Command Descriptions  
TRIGger  
Command Syntax  
TRIGger  
[:SEQuence]  
:COUNt  
Query Syntax  
*RST Value  
N/A  
1
Limits  
The count specified in this command must be between 1 and 65535.  
Related Commands  
ABORt, ROUTe:SCAN  
TRIGger[:SEQuence]:SOURce  
TRIGger[:SEQuence][:IMMediate]  
TRIGger[:SEQuence]:DELay  
Description  
Examples  
This command specifies the number of times to sequence through an entire scan  
sequence.  
Command  
Response  
route:scan  
(@m1(1,2),m2(1:64))  
Define a scan sequence consisting of relays 1 and 2 on relay  
module m1 and relays 1 through 64 on module m2.  
trigger:sequence:count Define the number of times to sequence through the scan list  
2
before setting the state of the trigger subsystem back to the  
idle state.  
trigger:sequence:  
source:immediate  
Sequence through the scan list without waiting for a trigger  
event after an INITiate[:Immediate] command is received.  
initiate:immediate  
Initiate the scan sequence. Sequence through the entire scan  
list two times.  
Command Syntax  
Query Syntax  
TRIGger  
[:SEQuence]  
:DELay  
N/A  
3–55  
Option 01 VXI Interface Module User Manual  
 
Command Descriptions  
*RST Value  
0
Limits  
The time specified in this command must be between 0 and 6.5535 seconds.  
Related Commands  
ABORt, ROUTe:SCAN  
TRIGger[:SEQuence]:SOURce  
TRIGger[:SEQuence][:IMMediate]  
TRIGger[:SEQuence]:DELay  
Description  
Examples  
This command specifies the time to wait after a trigger event is detectedbefore  
opening the current relay in a scan list. A trigger event is enabled with teh  
TRIGger:[SEQuence]:SOURce command.  
Command  
Response  
route:scan  
(@m1(1,2),m2(1:64))  
Define a scan sequence consisting of relays 1 and 2 on relay  
module m1 and relays 1 through 64 on module m2.  
trigger:sequence:count Define the number of times to sequence through the scan list  
2
before setting the state of the trigger subsystem back to the  
idle state.  
trigger:sequence:delay Wait 0.5 seconds after a trigger event is detected before open-  
0.5  
ing the current relay in a scan list and closing the next relay in  
the list.  
trigger:sequence:  
source ttltrg2  
Sequence to the next relay in a scan list when VXI TTL trigger  
2 is asserted.  
initiate:immediate  
Initiate the scan sequence. Sequence through the entire scan  
list two times. Wait 0.5 seconds after VXI TTL trigger 2 is as-  
serted before sequencing to the next relay in the list.  
Command Syntax  
TRIGger  
[:SEQuence]  
[:IMMediate]  
Query Syntax  
*RST Value  
Limits  
N/A  
N/A  
N/A  
3–56  
Option 01 VXI Interface Module User Manual  
 
Command Descriptions  
Related Commands  
ABORt, ROUTe:SCAN  
TRIGger[:SEQuence]:SOURce  
TRIGger[:SEQuence]:COUNt  
TRIGger[:SEQuence]:DELay  
Description  
Examples  
Sequence to the next relay in an initiated scan list without waiting for a trigger  
event and without waiting the time specified in a TRIGger[:SEQuence]:DELay  
command.  
Command  
Response  
route:scan  
(@m1(1,2),m2(1:64))  
Define a scan sequence consisting of relays 1 and 2 on relay  
module “m1” and relays 1 through 64 on module m2.  
trigger:sequence count Define the number of times to sequence through the scan list  
2
before setting the state of the trigger subsystem back to the  
idle state.  
trigger:sequence:delay Wait 0.5 seconds after a trigger event is detected before  
0.5  
opening the current relay in a scan list and closing the next  
relay in the list.  
trigger:sequence:  
source:ttltrg2  
Sequence to the next relay in a scan list when VXI TTL trigger  
2 is asserted.  
initiate:immediate  
Initiate the scan sequence. Sequence through the entire scan  
list 2 times. Wait 0.5 seconds after VXI TTL trigger 2 is  
asserted before sequencing to the next relay in the list.  
trigger:sequence:  
immediate  
Sequence to the next relay in the scan list without waiting for  
VXI TTL trigger 2 to be asserted. Do not wait 0.5 seconds to  
sequence to the next relay.  
Command Syntax  
TRIGger  
[:SEQuence]  
:SOURce BUS | HOLD | IMMediate | TTLTrg<n>  
Query Syntax  
*RST Value  
N/A  
IMMediate  
Limits  
N/A  
Related Commands  
ABORt, ROUTe:SCAN  
TRIGger[:SEQuence][:SOURce]  
TRIGger[:SEQuence][:IMMediate]  
3–57  
Option 01 VXI Interface Module User Manual  
 
Command Descriptions  
TRIGger[:SEQuence][:COUNt]  
TRIGger[:SEQuence][:DELay]  
Description  
This command selects a trigger source. When a trigger event is detected from an  
enabled trigger source, the next relay in an initiated scan sequence is closed after  
the current closed relay is opened.  
The action of opening the currently closed relay and closing the next relay in a  
scan list is called sequencing the scan list.  
Specifying BUS in the TRIGger[:SEQuence]:SOURce command enables a  
IEEE488.1 Group Execute Trigger command to sequence the scan list.  
It is assumed that the commander of the Option 01 is a IEEE488 talker/listener  
and that this device converts a IEEE488.1 GET command to a VXI Trigger  
command.  
Specifying HOLD in the TRIGger[:SEQuence]:SOURce command disables all  
trigger sources.  
Specifying IMMediate in the TRIGger[:SEQuence]:SOURce command causes  
the Option 01 to sequence through the scan list without waiting for a trigger  
event.  
Specifying TTLTrg<n> in the TRIGger[:SEQuence]:SOURce command enables  
one of eight VXI TTL triggers to act as a trigger source. <n> is a single digit  
between 0 and 7.  
Command  
Response  
Examples  
route:scan  
(@m1(1,2),m2(1:64))  
Define a scan sequence consisting of relays 1 and 2 on relay  
module “m1” and relays 1 through 64 on module m2.  
trigger:sequence:count Define the number of times to sequence through the scan list  
2
before setting the state of the trigger subsystem back to the  
idle state.  
trigger:sequence:  
source:immediate  
Sequence through the scan list without waiting for a trigger  
event after an INITiate[:Immediate] command is received.  
initiate:immediate  
Initiate the scan sequence. Sequence through the entire scan  
list two times.  
3–58  
Option 01 VXI Interface Module User Manual  
 
IEEE-488.2 Common Commands  
This section lists the IEEE-488.2 common commands and queries recognized by  
the Option 01.  
*CLS  
Clear Status. This commands clears the following:  
Event Status register (ESR)  
Error/Event queue  
Output queue  
*ESE <NRf>  
Event Status Enable (ESE) command. This command defines the mask for  
setting the Event Status Summary bit (bit 5) in the Status Byte register (*STB?).  
The mask is logically ANDed with the Event Status register (*ESR?) to  
determine whether or not to set the Event Status Summary bit. The mask can be  
any numeric value from 0 to 255, corresponding to the encoded bits of the ESR  
register. A “1” in a bit position enables reporting of the function. A “0” disables  
it. The *ESE register is cleared at power-on, or by writing an *ESE 0 command  
only. If <mask> is not specified, it defaults to 0.  
For example, the command *ESE 37 (hexadecimal 25, binary 00010101) enables  
setting the Event Status Summary bit whenever an operation is complete, a query  
error is detected, or an execution error is detected.  
*ESE?  
*ESR?  
Event Status Enable (ESE) query. This command returns the value of the Event  
Status Enable register as a numeric value from 0 to 255. For example, a value of  
32 (hexadecimal 40, binary 00100000) indicates that command error reporting is  
enabled.  
Event Status Register (ESR) query. This command returns the value of the Event  
Status register. The *ESR command is destructively read (that is, read and  
cleared). The Event Status Summary bit in the Status Byte (*STB?) is also  
cleared by a read of the ESR. The ESR is set to 128 on power-on (bit 7) set. It is  
3–59  
Option 01 VXI Interface Module User Manual  
 
IEEE-488.2 Common Commands  
cleared by an *ESR? or *CLS command only. When converted to a binary  
number, the bits of the ESR correspond to:  
bit 0 (LSB)  
Operation Complete  
Request Control  
Query error  
1
2
3
4
5
6
Device Dependent error  
Execution error  
Command error  
User Request  
7 (MSB)  
Power On  
The Error bits are set whenever the module detects an error. The error values  
from –100 to –199 are Command errors. Error values from –200 to –299 are  
Execution errors. Error values from –300 to –399 are Device Dependent errors.  
Error values from –400 to –499 are Query errors (see the SYSTem:ERRor  
command description).  
The Request Control and User Request bits are unused, and are always reported  
as zeroes.  
The Operation Complete bit is set in response to an *OPC command. A 1  
indicates that the module has completed all pending commands and queries.  
*IDN?  
Identification query; This returns a 4-field response. Field 1 is the manufacturer,  
field 2 the model, field 3 the serial number, and field 4 contains both the SCPI  
and the firmware version levels. For the Option 01, the serial number field is  
always a 0. The response syntax is:  
TEKTRONIX,VX43xx,0,SCPI:94.0 FW1.1<LF>  
where xx indicates the model number of the relay module that the Option 01 is  
installed on:  
Value of xx  
Model Number  
VX4320  
20  
30  
50  
80  
VX4330  
VX4350  
VX4380  
3–60  
Option 01 VXI Interface Module User Manual  
 
IEEE-488.2 Common Commands  
*OPC  
Operation Complete. This command causes the module to set the Operation  
Complete bit in the Event Status register (ESR) when all pending commands and  
queries are complete.  
*OPC?  
Operation Complete query. This command causes the module to place a “1” in  
the Output queue when all pending commands and queries are complete. All  
commands following *OPC are suspended until the pending operations are  
complete. The *OPC? command does not affect the OPC bit in the Event Status  
register.  
*RST  
Reset. This command causes the Option 01 to open all relays on all modules  
under its control, except for VX4320 Modules. Channel 1 in each section of each  
VX4320 Module is closed. This command sets the Option 01 Module to its  
power-on state with the following exceptions: the Error/Event queue, Output  
queue, Standard Event Status Enable register, SCPI Status Operation Event  
Enable register and SCPI Status Questionable Event Enable register are not  
cleared.  
The condition of the Option 01 daughter board and the switching modules that it  
controls after receipt of a *RST command is as follows:  
Contents of the SCPI Status Operation Event register = 0  
Contents of the SCPI Status Operation Condition register = 0  
Contents of the SCPI Status Questionable Event register = 0  
Contents of the SCPI Status Questionable Condition register = 0  
All VXI TTL triggers are disabled  
Trigger subsystem is in the idle state  
Trigger source = IMMediate  
Number of times to sequence through an entire scan list = 1  
Time in seconds to wait after a trigger event is detected before sequencing to  
the Next relay in a scan list = 0  
All relays on all modules are set to the open position  
No scan list is defined  
Default module names are assigned as follows:  
The module that has a Option 01 VXI Interface daughter board installed  
is assigned module name “M1”.  
Modules without the Option 01 VXI Interface daughter board in  
3–61  
Option 01 VXI Interface Module User Manual  
 
IEEE-488.2 Common Commands  
consecutive slots to the right of module “M1” are assigned module  
names “M2”, “M3”, ..., “M11”.  
All sections on all scanner modules are disjoined  
All sections of all VX4330 Modules are set to operate in the mux mode  
Close dwell time of all modules is set to 0 seconds  
Open dwell time of all modules is set to 0 seconds  
All relays on all modules are opened when power is removed from the VXI  
chassis  
*SRE <mask>  
Service Request Enable (SRE) register. This command defines a mask that is  
ANDed with the contents of the Status Byte register. If the result of this  
operation is non-zero, the Option 01 generates a VXI Request True interrupt.  
Bits 0, 1, 3, 6, and 7 of the SRE register are not used. Bits 2, 4, and 5 are set to  
enable VXI Request True interrupts to be generated under the conditions listed in  
the following table.  
Bit No.  
Meaning  
bit0 (LSB)  
Not used  
1
2
3
4
5
Not used  
The Error/Event queue contains one or more error messages  
Not used  
The Output queue contains one or more query responses  
The contents of the Standard Event Status register ANDed with the  
contents of the Standard Event Status Enable register produces a  
non-zero result.  
6
7
Not used  
Not used  
*SRE?  
Service Request Enable (SRE) query. This command returns the value of the  
Service Request Enable register as a numeric value from 0 to 255. Bit 6 is  
unused, and is reported as zero.  
*STB?  
Status Byte Query. This query returns the value of the Status Byte register as a  
numeric value between 0 and 255. The Status Byte register contents (with the  
3–62  
Option 01 VXI Interface Module User Manual  
 
IEEE-488.2 Common Commands  
exception of bit 6) are also returned in response to a VXI Read STB command.  
Bit 6 is read destructively in response to a VXI Read STB command. Bit 6 is not  
read destructively is response to a *STB? query. The Status Byte register is  
encoded as follows:  
Bit No.  
bit 0 (lsb)  
bit 1  
Meaning  
Not used  
Not used  
bit 2  
Set when the Error/Event queue contains one or more error messages.  
Not used  
bit 3  
bit 4  
Set when the Output buffer contains one or more query responses.  
bit 5  
Set when the contents of the Standard Event Status register ANDed  
with the contents of the Standard Event Status Enable register  
produces a non-zero result.  
bit 6  
Set when the contents of bits 0 through 5 and bit 7 of the Status Byte  
register ANDed with the contents of the Service Request Enable  
register produce a non-zero result.  
If bit 6 becomes set, the Option 01 will generate a VXI Request True  
interrupt on the VME interrupt level selected by its interrupt level select  
switch. If bit 6 becomes set and the Status Byte register is read using a  
VXI Read STB command, bit 6 will be reported as being set. In  
response to subsequent VXI Read STB commands, bit 6 will be  
reported as being cleared.  
If bit 6 becomes set and the Status Byte register is read using a *STB?  
query, bit 6 will be reported as being set. Bit 6 will continue to be  
reported as set in reponse to *STB queries until the contents of bits 0  
through 5 and bit 7 of the Status Byte register ANDed with the contents  
of the Service Request Enable register is equal to 0.  
bit 7  
Not used.  
3–63  
Option 01 VXI Interface Module User Manual  
 
IEEE-488.2 Common Commands  
*TRG  
Trigger Command. This command is equivalent to a VXI Trigger command.  
This command is valid only after the following commands have been received  
by the Option 01:  
Command  
Description  
[ROUTe:]SCAN  
<channel_list>  
Define a scan list  
TRIGger  
[:SEQuence]  
:SOURce BUS  
Select a VXI Trigger command as a trigger source.  
INITiate[:IMMediate]  
Initiate the scan list. This command places the trigger  
subsystem in the “ARM” state. The trigger subsystem remains  
in this state until the Option 01 has sequenced through the  
entire scan list “n” times, where “n” has been previously  
specified in a TRIGger[:SEQuence]:COUNT command. The  
trigger subsystem then returns to the IDLE state. The trigger  
subsystem also returns to the IDLE state if an ABORt  
command is received by the Option 01.  
After these commands have been issued, a *TRG command will cause the  
Option 01 to take the following actions:  
Generate a trigger delay that has previously been specified in a TRIGger  
[:SEQuence]:DELay command.  
Open the currently closed channel .  
Generate the open delay that has previously been specified in a  
[ROUTe:]OPEN:DWELl command.  
Close the next channel in the scan list.  
Generate the close delay that has previously been specified in a  
[ROUTe:]CLOSe:DWELl.  
Pulse one or more VXI TTL trigger signals that have been enabled by a  
previously issued OUTPut:TTLTRG<n>[:STATe] ON command.  
If the module containing the channel is a scanner module, pulse the  
appropriate front panel encode signal.  
If another *TRG command is received before this sequence is complete, a SCPI  
–211,“Trigger ignored” error message will be placed in the Error/Event queue.  
The *TRG command will continue to have this effect until the trigger subsystem  
is placed in the IDLE state. If additional *TRG commands are recieved after the  
3–64  
Option 01 VXI Interface Module User Manual  
 
IEEE-488.2 Common Commands  
trigger system is placed in the IDLE state, the Option 01 will place SCPI  
–211,“Trigger Ignored” error messages in the Error/Event queue.  
The IEEE-488.2 Specification equates the *TRG command with an IEEE-488.1  
Group Execute Trigger (GET) command. IEEE-488-to-VXI interface modules  
typically convert IEEE-488.1 GET commands to VXI Trigger commands. For  
this reason, the Option 01 equates the *TRG command with a VXI Trigger  
command.  
*TST?  
Self Test query. In response to this query, the Option 01 performs a self test of  
each of the switching modules under its control. During self test, the Option 01  
verifies that it can properly control the relay drive circuitry of each switching  
module under its control. After the self test is complete, each module is restored  
to its pretest state. If all modules pass self test, an ASCII “0” is placed in the  
Output buffer. If one or more modules fail the self test, an ASCII “1” is placed in  
the Output buffer and error message(s) describing the failure are queued in the  
Error/Event queue. Issue a SYSTem:ERRor? query to read these error messages.  
*WAI  
Wait to Continue. This command causes the module to wait until all pending  
commands and queries are complete. All commands following *WAI are  
suspended until the pending operations are complete.  
3–65  
Option 01 VXI Interface Module User Manual  
 
Status and Events  
The Status and Event Reporting System reports asynchronous events and errors  
that occur in the Option 01 VXI Interface Module. This system consists of four  
8-bit registers and two queues that you access through the command language.  
You can use these registers and queues to query the instrument status and control  
the interrupts that report events.  
In general, after an interrupt occurs, first conduct a serial poll, query the registers  
to see why the interrupt occurred, and then send the SYSTem:ERRor? query to  
see a descriptive error message.  
This section describes the four registers and two queues of the Status and Event  
Reporting system. For each register, you are given a description, a table  
describing all of the bits, and an example of how to use the register.  
The Status and Event Reporting process, synchronizing programming com-  
mands, and the system messages are also described in this section.  
Status and Event Reporting System  
The Status and Event Reporting system monitors and reports such events as an  
error occurring or the availability of a response to a query. This system includes  
descriptions of the following registers and queues:  
H
H
H
H
H
H
Status Byte register  
Service Request Enable register  
Standard Event Status register  
Event Status Enable register  
Output queue  
System Error and Event queue  
Status Byte Register  
The Status Byte register, shown in Table 4–1, summarizes information from  
other registers. Use a serial poll or a *STB? query to read the contents of the  
Status Byte register. The response is the sum of the decimal values for all bits  
set. When you use a serial poll, bit 6 shows Request Service information. When  
you use the *STB? query, bit 6, the Master Status Summary bit, indicates that  
bits 5, 4, or 2 may be set.  
4–1  
Option 01 VXI Interface Module User Manual  
 
Status and Events  
Table 4–1: The Status Byte Register  
Decimal  
Value  
Bit  
0–1  
2
Function  
–
4
Not used.  
Error/Event queue Not Empty indicates that information is  
contained in the Error/Event queue and is waiting to be read.  
3
4
–
Not used.  
16  
Message Available shows that output is available in the Output  
queue.  
5
6
32  
64  
Event Status Bit indicates that one or more events have occurred  
and the corresponding bits in the Standard Event Status register  
have been set.  
Request Service (obtained from a serial poll) shows that the  
Option 01 has requested service from the GPIB controller.  
Master Status Summary (obtained from *STB? query) summarizes  
the Event Status bit, Message Available bits, and Error/Event  
queue Not Empty bits in the Status Byte register.  
7
–
Not used.  
A common example of using the Status Byte register is to enable the Message  
Available bit. This is done by sending an *SRE 16 command to the Option 01  
VXI Interface Module. If the *STB? query returns a value of 80, bit 4 (decimal  
value of 16) and bit 6 (decimal value of 64) have been set (giving a decimal sum  
of 80). Bit 4 indicates that a message is available in the output queue. Bit 6  
indicates that a bit in the Status Byte register that has been enabled by setting the  
corresponding bit in the Service Request Enable register (in this case bit 4) has  
been set.  
Service Request Enable  
Register  
The Service Request Enable register, shown in Table 4–2, controls which bits in  
the Status Byte register will generate a service request. Use the *SRE command  
to set bits in the Service Request Enable register. Use the *SRE? query to see  
which bits in this register are enabled. The response from this query is the sum  
of the decimal values for all bits set.  
Table 4–2: The Service Request Enable Register  
Decimal  
Value  
Bit  
0–1  
2
Function  
–
4
Not used  
Error/Event queue Bit indicates that a service request will be  
generated when a message is placed in the Error/Event queue.  
4–2  
Option 01 VXI Interface Module User Manual  
 
Status and Events  
Table 4–2: The Service Request Enable Register (Cont.)  
Decimal  
Value  
Bit  
Function  
3
8
Not used  
4
16  
Message Available Bit indicates that a service request will be  
generated when a message is placed in the Output queue.  
5
32  
–
Event Status Bit indicates that events summarized in bit 5 of the  
Status Byte register will generate a service request.  
6–7  
Not used  
If, for example, the *SRE? query returns a value of 48, bits 4 and 5 are set in the  
Service Request Enable register. Any event that causes the Message Available bit  
(bit 4) or Event Status bit (bit 5) to be set in the Status Byte register now  
generates an interrupt. If you want an interrupt to be generated only when the  
Event Status bit (bit 5) is set, use the *SRE 32 command.  
Standard Event Status  
Register  
The Standard Event Status register, shown in Table 4–3, records many types of  
events that can occur in the Option 01. Use the *ESR? query to read the contents  
of this register. The response is the sum of the decimal values for all bits set.  
Reading this register clears all bits so the register can accumulate information  
about new events.  
Table 4–3: The Standard Event Status Register  
Decimal  
Value  
Bit  
Function  
0
1
Operation Complete shows that the operation is complete. This bit  
is set when all pending operations complete following a *OPC  
command.  
1
2
3
4
–
Not used  
4
Query Error shows that data in the Output queue was lost.  
8
Not used  
16  
Execution Error shows that an error occurred while the Option 01  
was executing a command or query. Table 4–6 on page 4–7 lists  
the execution error messages.  
5
32  
Command Error shows that an error occurred while the Option 01  
was parsing a command or query. Table 4–5 on page 4–6 lists the  
command error messages.  
6
7
–
Not used  
128  
Power On shows that the Option 01 was powered on.  
4–3  
Option 01 VXI Interface Module User Manual  
 
Status and Events  
The following example assumes that all bits have been enabled using the Event  
Status Enable register (see the next section for information about this register). If  
a *ESR? query returns a value of 128, bit 7 (decimal value of 128) is set  
indicating that the instrument is in the initial power-on state.  
Event Status Enable  
The Event Status Enable register, shown in Table 4–4, controls which events are  
summarized in the Event Status bit (bit 5) of the Status Byte register. Use the  
*ESE command to set bits in the Event Status Enable register. Use the *ESE?  
query to see what bits in the Event Status Enable register are set. The response  
from this query is the sum of the decimal values for all bits summarized in the  
event status bit of the Status Byte register.  
Register  
Table 4–4: The Event Status Enable Register  
Decimal  
Value  
Bit  
Function  
0
1
Set bit 5 of the Status Byte register when bit 1 (the Operation  
Complete bit) of the Standard Event Status register is set.  
1
2
2
4
Not used  
Set bit 5 of the Status Byte register when bit 2 (the Query Error bit )  
of the Standard Event Status register is set.  
3
4
8
Not used  
16  
Set bit 5 of the Status Byte register when bit 4 (the Execution Error  
bit) of the Standard Event Status register is set.  
5
32  
Set bit 5 of the Status Byte register when bit 5 (the Command Error  
bit) of the Standard Event Status register is set.  
6
7
64  
Not used  
128  
Set bit 5 of the Status Byte register when bit 7 (the Power On bit) of  
the Standard Event Status register is set.  
If, for example, the *ESE? query returns a value of 255, all bits are set,  
indicating that all events will set the event status bit (bit 5) of the Status Byte  
register.  
The Output Queue  
The Option 01 stores query responses in the Output queue.  
The System Error and  
Event Queue  
The Option 01 error and event messages are stored in the System Error and  
Event queue. Use the SYSTem:ERRor? query to get the event number and a text  
description of the event. Reading an event removes it from the queue. The Event  
queue stores detailed information for up to 10 events; the events are stored in  
first-in first-out order.  
4–4  
Option 01 VXI Interface Module User Manual  
 
Status and Events  
Status and Event Reporting Process  
Figure 4–1 shows how to use the Status and Event Reporting system. In the  
explanation that follows, numbers in parentheses refer to the circled numbers in  
Figure 4–1.  
1
7
6
6
5
4
3
3
2
1
1
0
Standard Event Status  
register  
Power  
On  
—
—
Command Execution  
Error Error  
Query  
—
—
Operation  
—
Event  
queue  
Event  
Event  
Event  
Error  
Complete  
Read using *ESR?  
2
Event Status Enable  
register  
Read using *ESE?  
Write using *ESE  
7
5
4
2
0
Power  
On  
Command Execution  
Query  
Operation  
—
Output  
queue  
Byte  
Byte  
Byte  
Error  
Error  
Error  
Complete  
4
3
1
6
Request  
Service  
7
5
4
3
—
2
1
—
0
—
Status Byte  
register  
Read using *STB?  
—
Event  
Message  
queue Not  
Empty  
Status Bit Available  
6
Master  
Status  
6
5
Service Request Enable  
register  
7
6
5
4
3
2
1
0
—
—
Event  
Message  
—
—
—
—
Read using *SRE?  
Write using *SRE  
Status Bit Available  
Figure 4–1: Status and Event Reporting Process  
When an event occurs the appropriate bit in the Standard Event Status register is  
set to one and the event is recorded in the Event queue (1). If the corresponding  
bit in the Event Status Enable register is also enabled (2), then the event status  
bit in the Status Byte register is set to one (3).  
4–5  
Option 01 VXI Interface Module User Manual  
 
Status and Events  
When output is sent to the Output queue (for example, a response to a query), the  
message available bit in the Status Byte register is set to one (4).  
When a bit in the Status Byte register is set to one and the corresponding bit in  
the Service Request Enable register is enabled (5), the master status summary bit  
in the Status Byte register is set to one and a service request is generated (6).  
Messages  
The Option 01 generates error messages in response to events caused by  
commands or queries. Each type of event sets a specific bit in the Standard Event  
Status register. Thus, each message is associated with a specific Standard Event  
Status register bit. In the message tables that follow, the associated Standard  
Event Status register bit is specified in the table title. Not shown in the tables are  
secondary messages giving more detail about the cause of the error or the  
meaning of the message. These secondary messages are shown for each  
command and query in Syntax and Commands.  
Table 4–5 shows the error messages generated by improper command syntax.  
Check to see that the command is properly formatted and that it follows the rules  
in Syntax and Commands.  
Table 4–5: Command Error Messages (Bit 5 in Standard Event Status  
register)  
Code  
–102  
–102  
–102  
–102  
–102  
–102  
Message  
Syntax error; 1 dimensional <channel_spec> invalid for VX4330 module  
Syntax error; 2 dimensional <channel_spec> invalid for VX4350 module  
Syntax error; 3 dimensional <channel_spec> invalid for VX43xx module  
Syntax error; channel dimension mismatch  
Syntax error; integer field greater than 10 characters  
Syntax error; Missing module name  
Syntax error; Module name already defined  
–102  
–102  
–102  
–102  
–102  
–102  
–102  
–102  
–102  
Syntax error; Module name already defined  
Syntax error; Module name length greater than 12 characters  
Syntax error; Non–contiguous section numbers  
Syntax error; ROUTe:CONFigure command invalid for VX43xx module  
Syntax error; ROUTe:DISJoin command invalid for VX43xx module  
Syntax error; ROUTe:JOIN command invalid for VX43xx module  
Syntax error; ROUTe:MODE command invalid for VX43xx module  
Syntax error; Undefined module name  
Syntax error; Unexpected x detected while ...  
4–6  
Option 01 VXI Interface Module User Manual  
 
Status and Events  
Table 4–5: Command Error Messages (Bit 5 in Standard Event Status  
register) (Cont.)  
Code  
–121  
–123  
Message  
Invalid character in number  
Exponent too large  
Table 4–6 lists the execution error messages that can occur during execution of a  
command. Parameter y in these error messages represents the local bus address  
of the module that the error message applies to. A value of 1 indicates the  
module containing the Option 01 daughter board, a value of 2 the module in the  
next slot to the right, and so on.  
Table 4–6: Execution Error Messages (Bit 4 in Standard Event Status  
register)  
Code  
–200  
–200  
–211  
–213  
–222  
–222  
–222  
–222  
–222  
–222  
–222  
–222  
–222  
–222  
–222  
–223  
–223  
–223  
–223  
–240  
–241  
Message  
Execution error; Reserved  
Execution error; scan list undefined  
Trigger ignored  
Init ignored  
Data out of range; Channel number x on module y  
Data out of range; Channel number x!x on module y  
Data out of range; Channel number x!x!x on module y  
Data out of range; Invalid module address specified  
Data out of range; Invalid section number  
Data out of range; invalid sequence count  
Data out of range; invalid trigger delay  
Data out of range; Invalid VXI TTL Trigger level  
Data out of range; Maximum value for ESE command is 255  
Data out of range; Maximum value for SRE command is 255  
Data out of range; invalid dwell time specified.  
Too much data; channel list array overflow  
Too much data; Input buffer overflow  
Too much data; Output buffer full  
Too much data; scan list array overflow  
Hardware error; shift register verification error – module m  
Hardware error; Unrecognized module d, d  
4–7  
Option 01 VXI Interface Module User Manual  
 
Status and Events  
Table 4–7 lists the device dependent error messages that can occur during Option  
01 operation.  
Table 4–7: Device Dependent Error Messages (Bit 3 in Standard Event Status  
register)  
Code  
–350  
–350  
Message  
Queue overflow; error/event queue  
Queue overflow; output queue  
4–8  
Option 01 VXI Interface Module User Manual  
 
Appendix A: Specifications  
Table A–1: VXI Instrument Characteristics  
Characteristics  
Description  
VXI General Characteristics  
The instrument provides a VXI interface that complies with Revision 1.4.  
The VXI interface is defined by the VXI Consortium, Inc.  
Message Based (1.4)  
Interface Type  
Protocols  
Word Serial (WSP)  
TTL Outputs  
VXI TTLTRG* Lines TTLTRG0* through TTLTRG7* under program control.  
Product Compliance to Regulations  
(VX4320, VX4330, VX4350, VX4380 only)  
Product Safety  
UL, cUL, UL classified to IEC–1010–1.  
IEC Characteristics  
Overvoltage Category:  
Safety:  
CAT I  
Class I  
EMC  
Per EC Council Directive 89/336 EEC (EC–92), the following standards and limits  
apply to the requirements for equipment to be used in residential, commercial, and  
light industrial environments. They are specified in EN–50081–1, the Generic  
Emission Standard, and in EN 50082–1, the Generic Immunity Standard. For  
equipment that is also intended to be used in industrial environments, the standards  
and limits specified in EN 50081–2 and EN 50082–2 should be used in addition.  
Emissions  
Emissions shall be within the limits specified by the following requirements:  
Enclosure:  
AC Mains:  
EN 55011 Class A limit for radiated emissions.  
EN 55011 Class A limit for radiated emissions.  
EN 60555–2: Power line harmonics  
Immunity, Enclosure, Radio Frequen- No state change when the instrument is subjected to a 3 V/M electromagnetic field  
cy Electromagnetic Field; IEC 801–3 over the frequency range of 27 MHz to 500 MHz.  
Immunity, Enclosure, Electrostatic  
Discharge (ESD); IEC 801–2  
Up to 8 kV with no loss of stored data, change to control settings, degradation of  
performance, or temporary loss of function. No state change.  
Immunity, Fast Transients, Common No loss of stored data, change to control settings, degradation of performance, or  
Mode; IEC 801–4  
temporary loss of function will occur when the instrument is subjected to the transients  
as described below.  
Port  
Peak Voltage – kV Tr/Th – ns  
Rep. Freq. – kHz  
Signal & control  
AC Power  
0.5  
1
5/50  
5/50  
5
5
A–1  
Option 01 VXI Interface Module User Manual  
 
Appendix A: Specifications  
Table A–1: VXI Instrument Characteristics  
Characteristics  
Description  
EN 55011, Class A  
The instrument complies with the requirements of EN 55011 for radiated, conducted,  
and magnetic emissions, when installed in a suitable VXI chassis. A suitable VXI  
chassis is defined as one which contains adequate EMC shielding which makes  
contact with the RF gasket on the front and rear shields of the VX43xx Module.  
FCC  
The instrument complies with the requirements of FCC CFR 47, Part 15, Subpart B,  
Class A for radiated and conducted emissions.  
Table A–2: Environmental/Reliability Characteristics  
Characteristics  
Temperature  
Operating  
Description  
Meets or exceeds MIL-T-28800E for Type III, 0 to 50_ C external ambient, when  
operated in a mainframe providing Class 3 equipment.  
Non-operating  
–40_ C to +71_ C  
Airflow as required by the host module, –10_ C/55_ C for 10_ C (or less) temperature  
rise of internal air, as measured at the cooling air exit points, and with no heat transfer  
either to or from any adjacent VXI modules.  
Relative Humidity  
Operating  
Up to 95% at up to 30_ C, and up to 45%, at up to 50_ C.  
Up to 95%, at up to 50_ C.  
Non-operating  
Altitude (1) Operating  
Altitude (2)  
6,000 ft. altitude.  
Meets or exceeds MIL-T-28800E for Type III, (operating to 10,000 ft., non-operating to  
15,000 ft.). Derate maximum operating temperature above TBD ft. by degree C per  
1000 ft.  
Table A–3: Option 01-Specific Characteristics  
Characteristics  
Description  
VME Interrupter Level  
VXI Logical Address  
VXI Dynamic Addressing  
Switch selectable to a level between 1 and 7.  
Switch selectable to a value between 0 and 255.  
Not supported.  
Contents of device/manufacturer dependent  
VXI registers.  
ID Register  
BFFD hexadecimal.  
Device Type  
Set according to the model number of the slave module that the interface is installed  
on as specified in the following table. (Convert the last 3 digits of the model number to  
hex, take the one’s complement, AND with F7FF.)  
A–2  
Option 01 VXI Interface Module User Manual  
 
Appendix A: Specifications  
Table A–3: Option 01-Specific Characteristics (Cont.)  
Characteristics  
Description  
Slave Module Model No.  
VX4320  
Register Contents (hexadecimal)  
F6BF  
F6B5  
F6A1  
F683  
VX4330  
VX4350  
VX4380  
VXI TTL Trigger Outputs  
VXI TTL Trigger Inputs  
One or more of the VXI TTLTRG* signals may be driven. All TTLTRG* outputs may be  
disabled.  
One of the VXI TTLTRG* signals may be selected to be polled or to act as an interrupt  
source to the module’s microprocessor.  
A–3  
Option 01 VXI Interface Module User Manual  
 
Appendix B: Examples  
This example script demonstrates how the some of the various programmable  
features of the Option 01 are used to control from 1 to 12 relay modules. These  
modules can consist of any combination of VX4320, VX4330, VX4350,  
VX4372, VX4374 and VX4380 relay modules. In these examples, the Option 01  
is installed on a VX4320 Module. A VX4330, VX4350, VX4372, VX4374, and  
VX4380 are installed in consecutive slots to the right of the VX4320.  
It is assumed the module has completed its power-on self test. For information  
on specific commands or syntax, please review the Syntax and Commands  
section.  
H
Query the identity of the module that the Option 01 is installed on.  
WRITE  
READ  
*IDN?  
TEKTRONIX,VX4320,0,SCPI:94.0 FW:1.1<CR><LF>  
H
Query the card for any self-test errors.  
WRITE  
READ  
*TST?  
0
Note that a response of 0 indicates that all modules controlled by the Option  
01 daughter board passed the self test. A response of 1 indicates that one or  
more modules have failed the self test. In that case, SYSTem:ERRor?  
queries should be issued to determine which modules failed the self test.  
H
H
Query the identity of all the modules controlled by the Option 01  
WRITE  
READ  
route:id?  
VX4320 VX4330 VX4350 VX4372 VX4374 VX4380  
Query the module names assigned to each of the modules controlled by the  
Option 01.  
WRITE  
READ  
route:module:catalog?  
"M1", "M2", "M3", "M4", "M5", "M6"  
The names listed in the response to this query correspond to the modules in  
the response to the route:id? query.  
H
Check the contents of the Standard Event Status register.  
WRITE  
READ  
*ESR?  
128  
B–1  
Option 01 VXI Interface Module User Manual  
 
Appendix B: Examples  
This response indicates that the Power On bit of the Standard Event Status  
register is set. This indicates that this is the first time an *ESR? query has  
been sent to the Option 01 since power was applied to the module.  
H
Check the contents of the Standard Event Status register again.  
WRITE  
READ  
*ESR?  
000  
The content of the Standard Event Status register is equal to zero because  
this register is read destructively. That is, it is set to zero after its contents are  
reported following an *ESR? query.  
H
H
Enable VXI TTL trigger 1 to be pulsed low for 3 µsec after a channel is  
closed on any of the relay modules.  
WRITE  
output:ttltrg1:state on  
Check to see if VXI TTL trigger 1 is enabled.  
WRITE  
READ  
output:ttltrg1:State?  
1
A response of 1 indicates that VXI TTL trigger 1 is enabled. A response of 0  
indicates that this trigger is disabled.  
H
H
Close channel 3 in section 5 of the VX4320 Module.  
WRITE  
close (@m1(3!5))  
Configure the VX4330 as a 240-to-1 1-wire scanner.  
WRITE  
WRITE  
WRITE  
route:conf:join m2,(1:6)  
route:conf owire,m2,(1:6)  
route:close:mode scan,m2,(1:6)  
H
H
Close channel 1 of section 1 of the VX4330.  
WRITE route:close (@m2(1!1))  
Close channel 40 of section 2 of the VX4330.  
WRITE route:close (@m2(40!2))  
Note that channel 1 of section 1 will be opened before channel 40 of section  
2 is closed because sections 1 and 2 have been joined and both sections have  
been set to a close mode of “scan”.  
H
Close channels 1 through 10 on the VX4350 Module.  
WRITE  
close (@m3(1:10))  
B–2  
Option 01 VXI Interface Module User Manual  
 
Appendix B: Examples  
H
H
Open channels 11 through 20 on the VX4350 Module.  
WRITE open (@m3(11:20))  
Query the close state of channels 1 through 20 on the VX4350 Module.  
WRITE  
READ  
close? (@m3(1:20))  
1 1 1 1 1 1 1 1 1 1 0 0 0 0 0 0 0 0 0 0  
A query response of 1 indicates that the corresponding channel is closed, and  
a response of 0 indicates that the channel is open.  
H
Query the open state of channels 1 through 20 on the VX4350 Module.  
WRITE  
READ  
open? (@m3(1:20))  
0 0 0 0 0 0 0 0 0 0 1 1 1 1 1 1 1 1 1 1  
A query response of 1 indicates that the corresponding channel is open, and a  
response of 0 indicates that the channel is closed.  
H
H
H
H
H
Join the two sections of the VX4372 Module.  
WRITE  
Close channel 10 in section 1 of the VX4372 Module.  
WRITE close (@m4(10!1))  
Disjoin the two sections of the VX4374 Module.  
WRITE route:conf:disjoin m5  
Close channel 12 of section 2 of the VX4374.  
WRITE route:close (@m5(12!2))  
Query the close state of the 12 channels in section 2 of the VX4374.  
route:conf:join m4,(1,2)  
WRITE  
READ  
route:close? (@m5(1!2:12!2))  
0 0 0 0 0 0 0 0 0 0 0 1  
Note that this query can also be specified as  
route:close? (@m5(13:24))  
H
H
Open all relays in section 4 of the VX4380 Module.  
WRITE  
route:open (@M6(1!1!4:4!16!4))  
Close the relay that joins row 3 to column 12 in section 4 of the VX4380  
Module.  
WRITE  
route:close (@m6(3!12!4))  
B–3  
Option 01 VXI Interface Module User Manual  
 
Appendix B: Examples  
H
Query the close state of the relays in section 4 of the VX4380.  
WRITE  
READ  
route:close? (@m6(1!1!4:4!16!4))  
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0  
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 0 0 0 0  
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0  
Note that the channel close states are returned in the following order:  
1!1!4, 1!2!4, 1!3!4, ..., 1!16!4,  
2!1!4, 2!2!4, 2!3!4, ..., 2!16!4,  
3!1!4, 3!2!4, 3!3!4, ..., 3!16!4,  
4!1!4, 4!2!4, 4!3!4, ..., 4!16!4  
which is the same order in which the channels were specified in the query.  
H
Open all channels on all modules except the VX4320 Module. (Note that one  
channel is always closed in each section of the VX4320, so the OPEN  
command is not supported for this module.)  
WRITE  
route:open:all m2; all m3; all m4; all m5; all  
m6  
H
H
H
Disjoin all sections of the VX4330.  
WRITE  
route:configure:disjoin m2  
Configure sections 1 through 3 of the VX4330 to 4-wire configuration.  
WRITE  
route:Conf fwire,m2,(1:3)  
Define a list of channels to scan through. Define this list as channels 1  
through 10 in section 1 of the VX4330, channels 1 through 10 in section 2 of  
the VX4330, channels 3 through 6 and 60 through 64 on the VX4350,  
channels 1 through 12 in section 1 and 1 through 12 in section 2 of the  
VX4374, and the channels that join row 2 to columns 1 through 16 in section  
1 of the VX4380.  
WRITE  
route:Scan (@m2(1!1:10!1,1!2:10!2),  
m3(3:6,60:64),m5(1:24),m6(2!1!1:2!16!1))  
H
H
Set the time to wait after closing a relay before pulsing a VXI TTL trigger to  
0.1 seconds for each module in the scan list defined in the previous example.  
WRITE  
clos:dwell m2,.1; dwell m3,.1; dwell m5,.1;  
dwell m6,.1  
Set the time to wait after opening a relay to 0.2 seconds for each module in  
the scan list defined above.  
B–4  
Option 01 VXI Interface Module User Manual  
 
Appendix B: Examples  
WRITE  
open:dwell m2,.2; dwell m3,.2; dwell m5,.2;  
dwell m6,.2  
H
H
Set the number of times to sequence through the defined scan list to 3.  
WRITE trigger:Sequence:count 3  
Set the trigger source for the scan list to “immediate”. This programs the  
Option 01 to generate an internal trigger after closing a channel in a scan list  
and waiting for the close dwell (assigned to the module containing the  
channel) to expire.  
WRITE  
trigger:sequence:source immediate  
H
Enable the Operation Complete bit of the Standard Event Status register to  
generate a VXI Request True interrupt to the commander of the Option 01  
Module.  
WRITE  
WRITE  
*SRE 32  
*ESE 1  
H
H
Sequence through the scan list 3 times and set the Operation Complete bit in  
the Standard Event Status register when finished.  
WRITE  
WRITE  
initiate:immediate  
*OPC  
After the Option 01 sequences through the scan list three times, it will  
generate a VXI Request True interrupt to its commander. When the  
commander of the Option 01 detects a Request True interrupt, check the  
contents of the Option 01’s Status Byte register.  
WRITE  
READ  
*STB?  
096  
H
H
This response indicates that bits 5 and 6 of the Status Byte register are set.  
Bit 6 indicates that the Option 01 has generated a request true interrupt. Bit 5  
indicates that the Operation Complete bit in the Standard Event Status  
register has been set. (This bit was enabled to set bit 5 of the Status Byte  
register by the previously issued *ESE 1 command.)  
Read the Standard Event Status register contents.  
WRITE  
READ  
WRITE  
READ  
*ESR?  
001  
*ESR?  
000  
Note that the second read of the Standard Event Status register is zero  
because this register is cleared each time an *ESR? query is received.  
B–5  
Option 01 VXI Interface Module User Manual  
 
Appendix B: Examples  
H
Check the contents of the Status Byte register.  
WRITE  
READ  
*STB?  
000  
The *ESR? query caused the Operation Complete bit of the Standard Event  
Status register to be cleared. This caused bit 5 of the Status Byte register to  
be cleared, which caused bit 6 of the Status Byte register to be cleared.  
B–6  
Option 01 VXI Interface Module User Manual  
 
Appendix C: User Service  
This appendix contains service-related information for the Option 01 that covers  
the following topics:  
H
H
H
H
Performance Verification  
Preventive maintenance  
Troubleshooting  
User-replaceable parts  
Performance Verification  
Consult the User Manual of the module on which the Option 01 is mounted. You  
may use the Functional Check procedure listed in the Getting Started section of  
that manual to verify that the module is operating correctly. The instrument has  
been fully tested and calibrated before leaving the factory.  
If the self test indicates a failure, contact your Tektronix field office or represen-  
tative for assistance.  
Preventive Maintenance  
You should perform inspection and cleaning as preventive maintenance.  
Preventive maintenance, when done regularly, may prevent Option 01 malfunc-  
tion and enhance reliability. Inspect and clean the Option 01 as often as  
conditions require by following these steps:  
1. Turn off power and remove the Option 01 from the VXIbus mainframe.  
2. Remove loose dust on the outside of the instrument with a lint-free cloth.  
3. Remove any remaining dirt with a lint-free cloth dampened with water or a  
75% isopropyl alcohol solution. Do not use abrasive cleaners.  
Troubleshooting  
If you suspect a malfunction, first double check connections to and from the  
Option 01. If the trouble persists, perform a self test.  
If the self test indicates a failure, contact your Tektronix field office or represen-  
tative for assistance.  
C–1  
Option 01 VXI Interface Module User Manual  
 
Appendix C: User Service  
User-Replaceable Parts  
Refer to Appendix D for replaceable parts information.  
C–2  
Option 01 VXI Interface Module User Manual  
 
Appendix D: Replaceable Parts  
This section contains a list of the replaceable modules for the <instrument>. Use  
this list to identify and order replacement parts.  
Parts Ordering Information  
Replacement parts are available through your local Tektronix field office or  
representative.  
Changes to Tektronix products are sometimes made to accommodate improved  
components as they become available and to give you the benefit of the latest  
improvements. Therefore, when ordering parts, it is important to include the  
following information in your order.  
H
H
H
H
Part number  
Instrument type or model number  
Instrument serial number  
Instrument modification number, if applicable  
If you order a part that has been replaced with a different or improved part, your  
local Tektronix field office or representative will contact you concerning any  
change in part number.  
Change information, if any, is located at the rear of this manual.  
Module Servicing  
Modules can be serviced by selecting one of the following three options. Contact  
your local Tektronix service center or representative for repair assistance.  
Module Exchange. In some cases you may exchange your module for a reman-  
ufactured module. These modules cost significantly less than new modules and  
meet the same factory specifications. For more information about the module  
exchange program, call 1-800-TEK-WIDE, extension 6630.  
Module Repair and Return. You may ship your module to us for repair, after which  
we will return it to you.  
New Modules. You may purchase replacement modules in the same way as other  
replacement parts.  
D–1  
Option 01 VXI Interface Module User Manual  
 
Appendix D: Replaceable Parts  
Using the Replaceable Parts List  
This section contains a list of the mechanical and/or electrical components that  
are replaceable for the <instrument>. Use this list to identify and order replace-  
ment parts. The following table describes each column in the parts list.  
Parts List Column Descriptions  
Column Column Name  
Description  
1
Figure & Index Number  
Items in this section are referenced by figure and index numbers to the exploded view  
illustrations that follow.  
2
Tektronix Part Number  
Serial Number  
Use this part number when ordering replacement parts from Tektronix.  
3 and 4  
Column three indicates the serial number at which the part was first effective. Column four  
indicates the serial number at which the part was discontinued. No entries indicates the part is  
good for all serial numbers.  
5
6
Qty  
This indicates the quantity of parts used.  
Name & Description  
An item name is separated from the description by a colon (:). Because of space limitations, an  
item name may sometimes appear as incomplete. Use the U.S. Federal Catalog handbook  
H6-1 for further item name identification.  
7
8
Mfr. Code  
This indicates the code of the actual manufacturer of the part.  
This indicates the actual manufacturer’s or vendor’s part number.  
Mfr. Part Number  
Abbreviations  
Abbreviations conform to American National Standard ANSI Y1.1–1972.  
Mfr. Code to Manufacturer  
Cross Index  
The table titled Manufacturers Cross Index shows codes, names, and addresses  
of manufacturers or vendors of components listed in the parts list.  
D–2  
Option 01 VXI Interface Module User Manual  
 
Appendix D: Replaceable Parts  
Manufacturers Cross Index  
Mfr.  
Code  
Manufacturer  
Address  
City, State, Zip Code  
80009  
TEKTRONIX INC  
14150 SW KARL BRAUN DR  
PO BOX 500  
BEAVERTON, OR 97077–0001  
TK2548  
XEROX CORPORATION  
DIV OF XEROX CORPORATION  
14181 SW MILLIKAN WAY  
BEAVERTON, OR 97005  
D–3  
Option 01 VXI Interface Module User Manual  
 
Appendix D: Replaceable Parts  
Replaceable Parts List  
Fig. &  
Tektronix  
Serial No. Serial No.  
Index  
Part Number Effective  
Discont’d  
Qty Name & Description  
Mfr. Code Mfr. Part Number  
Number  
070–9180–XX  
070–9198–XX  
1
1
MANUAL,TECH:USERS  
80009  
070–9180–01  
070–9198–00  
MANUAL,TECH:QUICK REFERENCE GUIDE,VXI  
INTERFACE OPT 01  
TK2548  
1
2
163–0431–01  
160–9792–00  
1
1
IC,MEMORY:CMOS,EPROM,PRGM  
(U31,REF. DESIG. PRINTED ON CKT. BRD.)  
80009  
80009  
163–0431–01  
160–9792–00  
IC,DIGITAL:CMOS,PRGM  
(U45,REF. DESIG. PRINTED ON CKT. BRD.)  
1
2
Figure D–1: Option 01 Exploded View  
D–4  
Option 01 VXI Interface Module User Manual  
 
Glossary and Index  
 
Glossary  
The terms in this glossary are defined as used in the VXIbus System. Although  
some of these terms may have different meanings in other systems, it is  
important to use these definitions in VXIbus applications. Terms which apply  
only to a particular instrument module are noted. Not all terms appear in every  
manual.  
Accessed Indicator  
An amber LED indicator that lights when the module identity is selected by  
the Resource Manager module, and flashes during any I/O operation for the  
module.  
ACFAIL*  
A VMEbus backplane line that is asserted under these conditions: 1) by the  
mainframe Power Supply when a power failure has occurred (either AC line  
source or power supply malfunction), or 2) by the front panel ON/  
STANDBY switch when switched to STANDBY.  
Asynchronous Communication  
Communications that occur outside the normal “command-response” cycle.  
Such communications have higher priority than synchronous communica-  
tion.  
Backplane  
The printed circuit board that is mounted in a VXIbus mainframe to provide  
the interface between VXIbus modules and between those modules and the  
external system.  
Bus Arbitration  
In the VMEbus interface, a system for resolving contention for service  
among VMEbus Master devices on the VMEbus.  
Bus Timer  
A functional module that measures the duration of each data transfer on the  
Data Transfer Bus (DTB) and terminates the DTB cycle if the duration is  
excessive. Without the termination capability of this module, a Bus Master  
attempt to transfer data to or from a non-existent Slave location could result  
in an infinitely long wait for the Slave response.  
Client  
In shared memory protocol (SMP), that half of an SMP channel that does not  
control the shared memory buffers.  
CLK10  
A 10 MHz, ±100 ppm, individually buffered (to each module slot),  
differential ECL system clock that is sourced from Slot 0 and distributed to  
Glossary–1  
Option 01 VXI Interface Module User Manual  
 
Glossary  
Slots 1–12 on P2. It is distributed to each module slot as a single source,  
single destination signal with a matched delay of under 8 ns.  
Commander  
In the VXIbus interface, a device that controls another device (a servant). A  
commander may be a servant of another commander.  
Command  
A directive to a device. There are three types of commands:  
In Word Serial Protocol, a 16-bit imperative to a servant from its com-  
mander.  
In Shared Memory Protocol, a 16-bit imperative from a client to a server, or  
vice versa.  
In a Message, an ASCII-coded, multi-byte directive to any receiving device.  
Communication Registers  
In word serial protocol, a set of device registers that are accessible to the  
commander of the device. Such registers are used for inter-device commu-  
nications, and are required on all VXIbus message-based devices.  
Configuration Registers  
A set of registers that allow the system to identify a (module) device type,  
model, manufacturer, address space, and memory requirements. In order to  
support automatic system and memory configuration, the VXIbus standard  
specifies that all VXIbus devices have a set of such registers, all accessible  
from P1 on the VMEbus.  
C-Size Card  
A VXIbus instrument module that is 340.0 mm × 233.4 mm × 30.48 mm  
(13.4 in. × 9.2 in × 1.2 in).  
Custom Device  
A special-purpose VXIbus device that has configuration registers so as to be  
identified by the system and to allow for definition of future device types to  
support further levels of compatibility.  
Data Transfer Bus  
One of four buses on the VMEbus backplane. The Data Transfer Bus allows  
Bus Masters to direct the transfer of binary data between Masters and Slaves.  
DC SUPPLIES Indicator  
A red LED indicator that illuminates when a DC power fault is detected on  
the backplane.  
Device Specific Protocol  
A protocol for communication with a device that is not defined in the  
VXIbus specification.  
Glossary–2  
Option 01 VXI Interface Module User Manual  
 
Glossary  
D-Size Card  
A VXIbus instrument module that is 340.0 × 366.7 mm × 30.48 mm (13.4 ×  
14.4 in × 1.2 in).  
DTB  
See Data Transfer Bus.  
DTB Arbiter  
A functional module that accepts bus requests from Requester modules and  
grants control of the DTB to one Requester at a time.  
DUT  
Device Under Test.  
ECLTRG  
Six single-ended ECL trigger lines (two on P2 and four on P3) that function  
as inter-module timing resources, and that are bussed across the VXIbus  
subsystem backplane. Any module, including the Slot 0 module, may drive  
and receive information from these lines. These lines have an impedance of  
50 W; the asserted state is logical High.  
Embedded Address  
An address in a communications protocol in which the destination of the  
message is included in the message.  
ESTST  
Extended STart/STop protocol; used to synchronize VXIbus modules.  
Extended Self Test  
Any self test or diagnostic power-on routine that executes after the initial  
kernel self test program.  
External System Controller  
The host computer or other external controller that exerts overall control  
over VXIbus operations.  
FAILED Indicator  
A red LED indicator that lights when a device on the VXIbus has detected an  
internal fault. This might result in the assertion of the SYSFAIL* line.  
IACK Daisy Chain Driver  
The circuit that drives the VMEbus Interrupt Acknowledge daisy chain line  
that runs continuously through all installed modules or through jumpers  
across the backplane.  
ID-ROM  
An NVRAM storage area that provides for non-volatile storage of diagnostic  
data.  
Instrument Module  
A plug-in printed circuit board, with associated components and shields, that  
Glossary–3  
Option 01 VXI Interface Module User Manual  
 
Glossary  
may be installed in a VXIbus mainframe. An instrument module may  
contain more than one device. Also, one device may require more than one  
instrument module.  
Interface Device  
A VXIbus device that provides one or more interfaces to external equipment.  
Interrupt Handler  
A functional module that detects interrupt requests generated by Interrupters  
and responds to those requests by requesting status and identity information.  
Interrupter  
A device capable of asserting VMEbus interrupts and performing the  
interrupt acknowledge sequence.  
IRQ  
The Interrupt ReQuest signal, which is the VMEbus interrupt line that is  
asserted by an Interrupter to signify to the controller that a device on the bus  
requires service by the controller.  
Local Bus  
A daisy-chained bus that connects adjacent VXIbus slots.  
Local Controller  
The instrument module that performs system control and external interface  
functions for the instrument modules in a VXIbus mainframe or several  
mainframes. See Resource Manager.  
Local Processor  
The processor on an instrument module.  
Logical Address  
The smallest functional unit recognized by a VXIbus system. It is often used  
to identify a particular module.  
Mainframe  
Card Cage. For example, the Tektronix VX1410 Intelliframe, an operable  
housing that includes 13 C-size VXIbus instrument module slots.  
Memory Device  
A storage element (such as bubble memory, RAM, and ROM) that has  
configuration registers and memory attributes (such as type and access time).  
Message  
A series of data bytes that are treated as a single communication, with a well  
defined terminator and message body.  
Message Based Device  
A VXIbus device that supports VXI configuration and communication  
registers. Such devices support the word serial protocol, and possibly other  
message-based protocols.  
Glossary–4  
Option 01 VXI Interface Module User Manual  
 
Glossary  
MODID Lines  
Module/system identity lines.  
Physical Address  
The address assigned to a backplane slot during an access.  
Power Monitor  
A device that monitors backplane power and reports fault conditions.  
P1  
The top-most backplane connector for a given module slot in a vertical  
mainframe. The left-most backplane connector for a given slot in a horizon-  
tal mainframe.  
P2  
The bottom backplane connector for a given module slot in a vertical C-size  
mainframe; or the middle backplane connector for a given module slot in a  
vertical D-size mainframe such as the VX1500.  
Query  
A form of command that allows for inquiry to obtain status or data.  
READY Indicator  
A green LED indicator that lights when the power-on diagnostic routines  
have been completed successfully. An internal failure or failure of +5 V  
power will extinguish this indicator.  
Register Based Device  
A VXIbus device that supports VXI register maps, but not high level  
VXIbus communication protocols; includes devices that are register-based  
servant elements.  
Requester  
A functional module that resides on the same module as a Master or  
Interrupt Handler and requests use of the DTB whenever its Master or  
Interrupt Handler requires it.  
Resource Manager  
A VXIbus device that provides configuration management services such as  
address map configuration, determining system hierarchy, allocating shared  
system resources, performing system self test diagnostics, and initializing  
system commanders.  
Self Calibration  
A routine that verifies the basic calibration of the instrument module circuits,  
and adjusts this calibration to compensate for short- and long-term variables.  
Self Test  
A set of routines that determine if the instrument module circuits will  
Glossary–5  
Option 01 VXI Interface Module User Manual  
 
Glossary  
perform according to a given set of standards. A self test routine is per-  
formed upon power-on.  
Servant  
A VXIbus message-based device that is controlled by a commander.  
Server  
A shared memory device that controls the shared memory buffers used in a  
given Shared Memory Protocol channel.  
Shared Memory Protocol  
A communications protocol that uses a block of memory that is accessible to  
both client and server. The memory block operates as a message buffer for  
communications.  
Slot 0 Controller  
See Slot 0 Module. Also see Resource Manager.  
Slot 0 Module  
A VXIbus device that provides the minimum VXIbus slot 0 services to slots  
1 through 12 (CLK10 and the module identity lines), but that may provide  
other services such as CLK100, SYNC100, STARBUS, and trigger control.  
SMP  
See Shared Memory Protocol.  
STARX  
Two (2) bi-directional, 50 W, differential ECL lines that provide for  
inter-module asynchronous communication. These pairs of timed and  
matched delay lines connect slot 0 and each of slots 1 through 12 in a  
mainframe. The delay between slots is less than 5 ns, and the lines are well  
matched for timing skew.  
STARY  
Two (2) bi-directional, 50 W, differential ECL lines that provide for  
inter-module asynchronous communication. These pairs of timed and  
matched delay lines connect slot 0 and each of slots 1 through 12 in a  
mainframe. The delay between slots is less than 5 ns, and the lines are well  
matched for timing skew.  
STST  
STart/STop protocol; used to synchronize modules.  
SYNC100  
A Slot 0 signal that is used to synchronize multiple devices with respect to a  
given rising edge of CLK100. These signals are individually buffered and  
matched to less than 2 ns of skew.  
Synchronous Communications  
A communications system that follows the “command-response” cycle  
Glossary–6  
Option 01 VXI Interface Module User Manual  
 
Glossary  
model. In this model, a device issues a command to another device; the  
second device executes the command; then returns a response. Synchronous  
commands are executed in the order received.  
SYSFAIL*  
A signal line on the VMEbus that is used to indicate a failure by a device.  
The device that fails asserts this line.  
System Clock Driver  
A functional module that provides a 16 MHz timing signal on the Utility  
Bus.  
System Hierarchy  
The tree structure of the commander/servant relationships of all devices in  
the system at a given time. In the VXIbus structure, each servant has a  
commander. A commander may also have a commander.  
Test Monitor  
An executive routine that is responsible for executing the self tests, storing  
any errors in the ID-ROM, and reporting such errors to the Resource  
Manager.  
Test Program  
A program, executed on the system controller, that controls the execution of  
tests within the test system.  
Test System  
A collection of hardware and software modules that operate in concert to test  
a target DUT.  
TTLTRG  
Open collector TTL lines used for inter-module timing and communication.  
VXIbus Subsystem  
One mainframe with modules installed. The installed modules include one  
module that performs slot 0 functions and a given complement of instrument  
modules. The subsystem may also include a Resource Manager.  
Word Serial Protocol  
A VXIbus word oriented, bi-directional, serial protocol for communications  
between message-based devices (that is, devices that include communication  
registers in addition to configuration registers).  
Word Serial Communications  
Inter-device communications using the Word Serial Protocol.  
WSP  
See Word Serial Protocol.  
10-MHz Clock  
A 10 MHz, ±100 ppm timing reference. Also see CLK10.  
Glossary–7  
Option 01 VXI Interface Module User Manual  
 
Glossary  
488-To-VXIbus Interface  
A message based device that provides for communication between the  
IEEE-488 bus and VXIbus instrument modules.  
Glossary–8  
Option 01 VXI Interface Module User Manual  
 
Index  
IEEE 488.2 Commands  
*CLS, 3–59  
A
Accessories, 1–4  
ARM, 3–17  
*ESE, 3–59  
*ESR?, 3–59  
*IDN?, 3–60  
*OPC, 3–61  
*OPC?, 3–61  
*RST, 3–61  
*SRE, 3–62  
*SRE?, 3–62  
*STB?, 3–62  
*TST?, 3–64, 3–65  
*WAI, 3–65  
C
*CLS, 3–59  
command, 3–19, 3–24, 3–28, 3–29, 3–32, 3–36, 3–41,  
3–42, 3–43, 3–47, 3–51, 3–55  
Command Descriptions  
ARM, 3–17  
command, 3–19, 3–24, 3–28, 3–29, 3–32, 3–36,  
3–41, 3–42, 3–43, 3–47, 3–51, 3–55  
command error messages, 4–6  
Command Syntax, 3–1  
*ESE?, 3–59  
IEEE-488 Address, 1–5  
Syntax Example, 3–3  
Commands. See individual command names  
Configuration Registers, 2–4  
M
Maintenance, Preventive, C–1  
Message, Handling, 4–1  
messages. See error messages  
D
device dependent error messages, 4–8  
N
Normal Transfer Mode, 2–2  
E
error messages, 4–6  
O
command errors, 4–6  
*OPC, 3–61  
device dependent errors, 4–8  
execution errors, 4–7  
*ESE, 3–59, 4–4  
OPC bit, 4–3  
*OPC?, 3–61  
Output queue, 4–4  
*ESE?, 3–59, 4–4  
*ESR?, 3–59, 4–3  
Event handling, 4–1  
P
Event Reporting Process, 4–5  
Event Reporting System, 4–1  
Event Status Enable Register, 4–4  
execution error messages, 4–7  
Performance verification, C–1  
Programming, B–1  
Q
Queue  
F
Fast Handshake Mode, 2–3  
Fuses, 1–3  
Output, 4–4  
System Error and Event, 4–4  
I
*IDN?, 3–60  
Index–1  
Option 01 VXI Interface Module User Manual  
 
Index  
Status and Event Reporting System, 4–1  
Status Byte Register, 4–1  
*STB?, 3–62, 4–1  
R
Register  
Event Status Enable, 4–4  
Switches, 1–4  
Service Request Enable, 4–2  
Standard Event Status, 4–3  
Status Byte, 4–1  
Logical Address Switches, 1–4, 1–6  
SYSFAIL*, 1–11  
System Error and Event queue, 4–4  
SYSTem:ERROr?, 4–4  
Replaceable Parts, D-1  
*RST, 3–61  
T
S
Troubleshooting, C–1  
*TST?, 3–64, 3–65  
Service Request Enable Register, 4–2  
Specifications, A–1  
*SRE, 3–62, 4–2  
*SRE?, 3–62, 4–2  
Standard Event Status Register, 4–3  
Status, 4–1  
W
*WAI, 3–65  
Status and Event Reporting Process, 4–5  
Index–2  
Option 01 VXI Interface Module User Manual  
 

Targus Mouse Wireless Optical Stow N GoTM Notebook Mouse 30 User Manual
TDK Power Supply iHA48060A012V User Manual
Telex Stereo Amplifier 811 100 User Manual
Texas Instruments Computer Accessories TI SITARA User Manual
TomTom GPS Receiver XL330 User Manual
Toshiba Camera Accessories ik tf7u User Manual
Toshiba Flat Panel Television 19SL400U User Manual
Trimble Outdoors PDAs Smartphones ST handheld User Manual
United States Stove Stove VF30I User Manual
Viking Range F20542B User Manual