Sony 3026 Operating and maintenance manual

Programmer Manual
3026
Realtime Spectrum Analyzer
071-0419-00
This document supports firmware version 1.10.

Copyright Sony/Tektronix Corporation. All rights reserved.
Copyright Tektronix, Inc. All rights reserved.
Tektronix products are covered by U.S. and foreign patents, issued and pending. Information in this publication supercedes
that in all previously published material. Specifications and price change privileges reserved.
Printed in Japan.
Sony/Tektronix Corporation, P.O.Box 5209, Tokyo Int’l, Tokyo 100–31 Japan
Tektronix, Inc., P.O. Box 1000, Wilsonville, OR 97070–1000
TEKTRONIX and TEK are registered trademarks of Tektronix, Inc.

3026 Programmer Manual 
  
Preface v. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
 
Getting Started 1-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Installing for GPIB Communication 1-2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
 
Syntax 2-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
SCPI Commands and Queries 2-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
IEEE 488.2 Common Commands 2-6. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Command Groups 2-9. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Command Summaries 2-9. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Command Descriptions 2-15. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
   
Status and Events 3-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Registers 3-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Status Registers 3-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Enable Registers 3-4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Queues 3-6. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Status and Event Processing Sequence 3-7. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Messages 3-8. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Error Messages and Codes 3-11. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Command Errors 3-11. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Execution Errors 3-12. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Device Specific Errors 3-14. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Query Errors 3-15. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Device Errors 3-15. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Appendix A: Character Chart A–1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Appendix B: Reserved Words B–1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Appendix C: Interface Specification C–1. . . . . . . . . . . . . . . . . . . . . . . . . . .
Interface Functions C–1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Interface Messages C–2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Appendix D: Factory Initialization Settings D–1. . . . . . . . . . . . . . . . . . . . .

Index Index–1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Table of Contents
 3026 Programmer Manual
  
Figure 1-1: Functional layers in GPIB system 1-1. . . . . . . . . . . . . . . . . . .
Figure 1-2: GPIB connector 1-2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 1-3: GPIB system configurations 1-3. . . . . . . . . . . . . . . . . . . . . . . .
Figure 2-1: Example of SCPI subsystem hierarchy tree 2-1. . . . . . . . . . .
Figure 2-2: Example of abbreviating a command 2-3. . . . . . . . . . . . . . . .
Figure 2-3: Example of chaining commands and queries 2-4. . . . . . . . . .
Figure 2-4: Example of omitting root and lower-level nodes in a chained
message 2-4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 3-1: The Status Byte Register (SBR) 3-2. . . . . . . . . . . . . . . . . . . . .
Figure 3-2: The Standard Event Status Register (SESR) 3-3. . . . . . . . . .
Figure 3-3: The Event Status Enable Register (ESER) 3-5. . . . . . . . . . . .
Figure 3-4: The Service Request Enable Register (SRER) 3-5. . . . . . . . .
Figure 3-5: Status and event processing sequence 3-7. . . . . . . . . . . . . . . .

Table of Contents
3026 Programmer Manual 
  
Table 2-1: Parameter types used in syntax descriptions 2-2. . . . . . . . . . .
Table 2-2: BNF symbols and meanings 2-6. . . . . . . . . . . . . . . . . . . . . . . .
Table 2-3: CALCULATE commands 2-9. . . . . . . . . . . . . . . . . . . . . . . . . .
Table 2-4: DISPLAY Commands 2-10. . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 2-5: HARDCOPY commands 2-11. . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 2-6: MEMORY commands 2-11. . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 2-7: SENSE commands 2-11. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 2-8: SOURCE commands 2-12. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 2-9: STATUS commands 2-12. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 2-10: SYSTEM commands 2-13. . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 2-11: TRIGGER commands 2-13. . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 2-12: COMMON commands 2-14. . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 2-13: Other commands 2-14. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 3-1: SRB bit functions 3-2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 3-2: SESR bit functions 3-3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 3-3: Command errors 3-11. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 3-4: Execution errors 3-12. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 3-5: Device specific errors 3-14. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 3-6: Query errors 3-15. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table A–1: ASCII & GPIB Code Chart A–1. . . . . . . . . . . . . . . . . . . . . . . .
Table C–1: GPIB interface function implementation C–1. . . . . . . . . . . . .
Table C–2: GPIB interface messages C–2. . . . . . . . . . . . . . . . . . . . . . . . . .
Table D–1: Factory initialized settings D–1. . . . . . . . . . . . . . . . . . . . . . . . .

Table of Contents
 3026 Programmer Manual

3026 Programmer Manual 

This is the Programmer Manual for the 3026 Realtime Spectrum Analyzer. This
manual provides information on operating the instrument over a General Purpose
Interface Bus (GPIB) interface.
This manual provides the following information:
HGetting Started describes how to connect and set up for remote operation.
HSyntax and Commands defines the command syntax and processing
conventions and describes each command in the realtime spectrum analyzer
command set.
HStatus and Events explains the status information and event messages
reported by the realtime spectrum analyzer.
HAppendices contains various topics of use to the programmer.
HIndex contains an index to this manual.
 
Other documentation for the realtime spectrum analyzer includes:
HThe 3026 User Manual (Tektronix part number 071-0418-xx) describes the
operation of the instrument.
HThe 3026 Service Manual (Tektronix part number 071-0420-xx) provides
information for maintaining and servicing the Data Generator.

Preface
 3026 Programmer Manual

 

3026 Programmer Manual 
 
The 3026 Realtime Spectrum Analyzer has a GPIB interface. Almost all
menu-controlled and front-panel controlled functions can be performed through
the GPIB interface using the programming command set (described in Command
Syntax).
The GPIB interface conforms to ANSI/IEEE Std 488.1-1987, which specifies the
hardware interface, its basic functional protocol, and a set of interface messages
(codes) that control the interface functions. This instrument also conforms to
ANSI/IEEE Std 488.2-1987 which specifies Codes, Formats, Protocols, and
Common Commands to support the system application. The functional layers of
the GPIB system are shown in Figure 1-1.
)$% !"!  % ( )$% !"!  % )
 
) %(   % %#&%&#$
!%  $$$
!! ! $   &#$
'*$" $$$

"
)
'
 
% #
 
% #
"
)
'
 
% #
  %# & %! )#
 $$ !& %! & %! )#
 !! )$% & %! )#
 ' & %! )#
     

Getting Started
 3026 Programmer Manual
   
Connect a GPIB cable from the GPIB controller to the ANSI/IEEE Std 488 port
(GPIB) connector on the rear panel of the realtime spectrum analyzer (see Figure
1-2). For example, when using an MS-DOS compatible controller, connect the
GPIB cable between the National Instrument PC2A GPIB board and the realtime
spectrum analyzer GPIB connector.
 
  
Instruments can be connected to the GPIB in linear or star configurations or in a
combination of both configurations. A linear hookup is one where a GPIB cable
is used to string one device to a second, and then another GPIB cable is used to
string from a second to a third, and so on until all devices in the system are
connected. A star setup is one where one end of all the GPIB cables in the
system are attached to one device. Refer to Figure 1-3 for these GPIB system
configurations.

Getting Started
3026 Programmer Manual 
 
 
   
 


 



    






 
   
Consider the following restrictions when distributing instruments on the GPIB
bus:
1. No more than 15 total devices (including the controller) can be included on a
signal bus.
2. In order to maintain the electrical characteristics of the bus, one device load
must be connected for every two meters of cable (most often, each device
represents one device load to the bus).
3. The total cable length (cumulative) must not exceed 66 feet (20 meters).
4. At least two-thirds of the device loads must be powered on.


Getting Started
 3026 Programmer Manual
To set the GPIB parameters, proceed as follows:
1. Press the UTILITY button on the front panel.
2. Press the GPIB bottom button.
3. Press the Talker Listener side button.
This sets the communication mode to Talker/Listener.
. The realtime spectrum analyzer accepts as a terminator either the
software LF (Line Feed), sent as the last data byte, or the hardware EOI, with
the EOI line asserted concurrently with the last data byte sent.
4. Set the GPIB address using the rotary knob or the front-panel keypad. The
value can be set from 1 to 30.
  


 

3026 Programmer Manual 2 1
Syntax
This section contains information on the Standard Commands for Programmable
Instruments (SCPI) and IEEE 488.2 Common Commands you can use to
program your 3026 Realtime Spectrum Analyzer. The information is organized
in the following subsections:
HSCPI Commands and Queries – This subsection describes the SCPI
command organization and syntax
HIEEE 488.2 Common Commands – This subsection lists the commands and
argument structures that are common to all SCPI commands
SCPI Commands and Queries
SCPI is a standard created by a consortium that provides guidelines for remote
programming of instruments. These guidelines provide a consistent program-
ming environment for instrument control and data transfer. This environment
uses defined programming messages, instrument responses, and data format
across all SCPI instruments, regardless of manufacturer. The realtime spectrum
analyzer uses a command language based on the SCPI standard.
The SCPI language is based on a hierarchical or tree structure (see Figure 2-1)
that represents a subsystem. The top level of the tree is the root node; it is
followed by one or more lower-level nodes.




 


Figure 2 1: Example of SCPI subsystem hierarchy tree
You can create commands and queries from these subsystem hierarchy trees.
Commands specify actions for the instrument to perform. Queries return
measurement data and information about parameter settings.

Syntax
 3026 Programmer Manual
SCPI commands are created by stringing together the nodes of a subsystem
hierarchy and separating each node by a colon.
In Figure 2-1, SENSe is the root node and AVERage, TYPE, COUNt, and RESet
are lower-level nodes. To create a SCPI command, start with the root node
SENSe and move down the tree structure adding nodes until you reach the end of
a branch. Most commands and some queries have parameters; you must include
a value for these parameters. If you specify a parameter value that is out of range,
the parameter will be set to a default value. The command descriptions, which
start on page 2-15, list the valid values for all parameters.
For example, SENSe:AVERage:TYPE OFF is a valid SCPI command created
from the hierarchy tree in Figure 2-1.
To create a query, start at the root node of a tree structure, move down to the end
of a branch, and add a question mark. SENSe:AVERage:TYPE? is an example of
a valid SCPI query using the hierarchy tree in Figure 2-1.
Many commands accept either string or numeric arguments. For example: a
boolean argument can either be “1” or “ON”.
Select signal parameter commands accept either a numeric value or one of the
following strings:
 Use this argument to query the minimum value or set the parameter
value to the minimum acceptable value.
 Use this argument to query the maximum value or set the parameter
value to the maximum acceptable value.
. If the realtime spectrum analyzer does not return a value in response to a
MIN or MAX query, then the values are undefined and an error message is
generated.
Every parameter in the command and query descriptions is of a specified type.
The parameters are enclosed in brackets, such as <pattern>. The parameter type
is listed after the parameter and is enclosed in parentheses, for example,
(discrete). Some parameter types are defined specifically for the realtime
spectrum analyzer command set and some are defined by ANSI/IEEE
488.2-1987 (see Table 2-1).
 
 
 
 

Syntax
3026 Programmer Manual 2Ć3
Table 2Ć1: Parameter types used in syntax descriptions
Parameter Type Description Example
binary Binary numbers #B0110
arbitrary block1A specified length of arbitrary
data
#512234xxxxx...where 5
indicates that the following 5
digits (12234) specify the length
of the data in bytes; xxxxx ...
indicates the data
boolean Boolean numbers or values ON or 1
OFF or 0
discrete A list of specific values MIN, MAX, UP, DOWN
hexadecimal2Hexadecimal numbers
(0-9, A, B, C, D, E, F)
#HAA, #H1
NR12,3 numeric Integers 0, 1, 15, -1
NR22numeric Decimal numbers 1.2, 3.141516, -6.5
NR32numeric Floating point numbers 3.1415E-9, -16.1E5
NRf2numeric Flexible decimal number that
may be type NR1, NR2 or NR3
See NR1, NR2, NR3 examples
string4Alphanumeric characters (must
be within quotation marks)
 esting 1, 2, 3"
1Defined in ANSI/IEEE 488.2 as Definite Lengt Arbitrary Block Response Data."
2An ANSI/IEEE 488.2-1992Ćdefined parameter type.
3Some commands and queries will accept a exadecimal value even t oug t e
parameter type is defined as NR1.
4Defined in ANSI/IEEE 488.2 as String Response Data."

Syntax
2Ć4 3026 Programmer Manual
You can abbreviate most SCPI commands, queries, and parameters to an
accepted short form. This manual shows these short forms as a combination of
upper and lower case letters. The upper case letters indicate the accepted short
form of a command. As shown in Figure 2-2, you can create a short form by
using only the upper case letters. The accepted short form and the long form are
equivalent and request the same action of the instrument.
   

  
   
  
   

SENS:AVER:COUN 100
SENSe:AVERage:COUN 100
Figure 2Ć2: Example of abbre iating a command
You can chain several commands or queries together into a single message. To
create a chained message, first create a command or query, add a semicolon (;),
and then add more commands or queries and semicolons until you are done. If
the command following a semicolon is a root node, precede it with a colon (:).
Figure 2-3 illustrates a chained message consisting of several commands and
queries. The single chained message should end in a command or query, not a
semicolon. Responses to any queries in your message are separated by semico-
lons.
:DISP:MARK:TYPEĂDUAL;:SENS:WINDĂRECT;:SENS:AVER:COUN?;:CALC:ACP:SPAC?
     
    
  
       
100;2.000000E+5
 
Figure 2Ć3: Example of chaining commands and queries
Abbre iating Commands,
Queries, and Parameters
Chaining Commands and
Queries