Agilent Technologies TV Converter Box 1660A User Manual

Programmer’s Guide

Publication number 01660-97033

Second edition, January 2000

For Safety information, Warranties, and Regulatory

information, see the pages behind the index

 Copyright Agilent Technologies 1992-2000

Agilent Technologies

1660A/AS-Series Logic

Analyzers

Download from Www.Somanuals.com. All Manuals Search And Download.

In This Book

Introduction to Programming

Programming Over GPIB

Programming Over RS-232C

This programmer’s guide contains general

information, mainframe level commands,

logic analyzer commands, oscilloscope

module commands, and programming

examples for programming the

Programming and

Documentation Conventions

Message Communication

and System Functions

1660-series logic analyzers. This guide

focuses on how to program the

instrument over the GPIB and the

RS-232C interfaces.

Status Reporting

Error Message

Instruments covered by the

1660-Series Programmer’s Guide

The 1660-series logic analyzers are

available with or without oscilloscope

measurement capabilities. The

1660A-series logic analyzers contain only

a logic analyzer. The 1660AS-series logic

analyzers contain both a logic analyzer

and a digitizing oscilloscope.

Common Commands

Mainframe Commands

SYSTem Subsystem

MMEMory Subsystem

INTermodule Subsystem

MACHine Subsystem

WLISt Subsystem

What is in the 1660-Series

Programmer’s Guide?

The 1660-Series Programmer’s Guide

is organized in five parts.

Part 1 Part 1 consists of chapters 1

through 7 and contains general

information about programming basics,

GPIB and RS-232C interface

requirements, documentation

conventions, status reporting , and error

messages.

iii

Download from Www.Somanuals.com. All Manuals Search And Download.

If you are already familiar with IEEE 488.2 programming and GPIB or

RS-232C, you may want to just scan these chapters. If you are new to

programmiung the system, you should read part 1.

Chapter 1 is divided into two sections. The first section, "Talking to the

Instrument," concentrates on program syntax, and the second section,

"Receiving Information from the Instrument," discusses how to send queries

and how to retrieve query results from the instrument.

Read either chapter 2, "Programming Over GPIB," or chapter 3,

"Programming Over RS-232C" for information concerning the physical

connection between the 1660-series logic analyzer and your controller.

Chapter 4, "Programming and Documentation Conventions," gives an

overview of all instructions and also explains the notation conventions used

in the syntax definitions and examples.

Chapter 5, "Message Communication and System Functions," provides an

overview of the operation of instruments that operate in compliance with the

IEEE 488.2 standard.

Chapter 6 explains status reporting and how it can be used to monitor the

flow of your programs and measurement process.

Chapter 7 contains error message descriptions.

Part 2 Part 2, chapters 8 through 12, explain each command in the

command set for the mainframe. These chapters are organized in

subsystems with each subsystem representing a front-panel menu.

The commands explained in this part give you access to common commands,

mainframe commands, system level commands, disk commands, and

intermodule measurement commands. This part is designed to provide a

concise description of each command.

Part 3 Part 3, chapters 13 through 25 explain each command in the

subsystem command set for the logic analyzer. Chapter 26 contains

information on the SYSTem:DATA and SYSTem:SETup commands for

the logic analyzer.

The commands explained in this part give you access to all the commands

used to operate the logic analyzer portion of the 1660-series system. This

part is designed to provide a concise description of each command.

Part 4 Part 4, chapters 27 through 35 explain each command in the

subsystem command set for the oscilloscope.

Download from Www.Somanuals.com. All Manuals Search And Download.

SFORmat Subsystem

STRigger (STRace) Subsystem

SLISt Subsystem

The commands explained in this part give

you access to all the commands used to

operate the oscilloscope portion of the

1660-series system. This part is designed

to provide a concise description of each

command.

SWAVeform Subsystem

SCHart Subsystem

Part 5 Part 5, chapter 36 contains

program examples of actual tasks that

show you how to get started in

programming the 1660-series logic

analyzers. The complexity of your

programs and the tasks they accomplish

are limited only by your imagination.

These examples are written in HP BASIC

6.2; however, the program concepts can

be used in any other popular

COMPare Subsystem

TFORmat Subsystem

programming language that allows

communications over GPIB or RS-232

buses.

TRIGger {TRACe} Subsystem

TWAVeform Subsystem

TLISt Subsystem

SYMbol Subsystem

DATA and SETup Commands

Oscilloscope Root Level

Commands

ACQuire Subsystem

Download from Www.Somanuals.com. All Manuals Search And Download.

CHANnel Subsystem

DISPlay Subsystem

MARKer Subsystem

MEASure Subsystem

TIMebase Subsystem

TRIGger Subsystem

WAVeform Subsystem

Programming Examples

Index

vii

Download from Www.Somanuals.com. All Manuals Search And Download.

viii

Download from Www.Somanuals.com. All Manuals Search And Download.

Contents

Part 1 General Information

1 Introduction to Programming

Talking to the Instrument 1–3

Initialization 1–4

Instruction Syntax 1–5

Output Command 1–5

Device Address 1–6

Instructions 1–6

Instruction Terminator 1–7

Header Types 1–8

Duplicate Keywords 1–9

Query Usage 1–10

Program Header Options 1–11

Parameter Data Types 1–12

Selecting Multiple Subsystems 1–14

Receiving Information from the Instrument 1–15

Response Header Options 1–16

Response Data Formats 1–17

String Variables 1–18

Numeric Base 1–19

Numeric Variables 1–19

Definite-Length Block Response Data 1–20

Multiple Queries 1–21

Instrument Status 1–22

2 Programming Over GPIB

Interface Capabilities 2–3

Command and Data Concepts 2–3

Addressing 2–3

Communicating Over the GPIB Bus (HP 9000 Series 200/300 Controller) 2–4

Local, Remote, and Local Lockout 2–5

Bus Commands 2–6

Contents–1

Download from Www.Somanuals.com. All Manuals Search And Download.

Contents

3 Programming Over RS-232C

Interface Operation 3–3

RS-232C Cables 3–3

Minimum Three-Wire Interface with Software Protocol 3–4

Extended Interface with Hardware Handshake 3–4

Cable Examples 3–6

Configuring the Logic Analzer Interface 3–8

Interface Capabilities 3–9

RS-232C Bus Addressing 3–10

Lockout Command 3–11

4Programming and Documentation Conventions

Truncation Rule 4–3

Infinity Representation 4–4

Sequential and Overlapped Commands 4–4

Response Generation 4–4

Syntax Diagrams 4–4

Notation Conventions and Definitions 4–5

The Command Tree 4–5

Tree Traversal Rules 4–6

Command Set Organization 4–14

Subsystems 4–15

Program Examples 4–16

5 Message Communication and System Functions

Protocols 5–3

Syntax Diagrams 5–5

Syntax Overview 5–7

6 Status Reporting

Event Status Register 6–4

Service Request Enable Register 6–4

Bit Definitions 6–4

Key Features 6–6

Serial Poll 6–7

Contents–2

Download from Www.Somanuals.com. All Manuals Search And Download.

Contents

7 Error Messages

Device Dependent Errors 7–3

Command Errors 7–3

Execution Errors 7–4

Internal Errors 7–4

Query Errors 7–5

Part 2 Mainframe Commands

8 Common Commands

*CLS (Clear Status) 8–5

*ESE (Event Status Enable) 8–6

*ESR (Event Status Register) 8–7

*IDN (Identification Number) 8–9

*IST (Individual Status) 8–9

*OPC (Operation Complete) 8–11

*OPT (Option Identification) 8–12

*PRE (Parallel Poll Enable Register Enable) 8–13

*RST (Reset) 8–14

*SRE (Service Request Enable) 8–15

*STB (Status Byte) 8–16

*TRG (Trigger) 8–17

*TST (Test) 8–18

*WAI (Wait) 8–19

9 Mainframe Commands

BEEPer 9–6

CAPability 9–7

CARDcage 9–8

CESE (Combined Event Status Enable) 9–9

CESR (Combined Event Status Register) 9–10

EOI (End Or Identify) 9–11

LER (LCL Event Register) 9–11

LOCKout 9–12

MENU 9–12

Contents–3

Download from Www.Somanuals.com. All Manuals Search And Download.

Contents

MESE<N> (Module Event Status Enable) 9–14

MESR<N> (Module Event Status Register) 9–16

RMODe 9–18

RTC (Real-time Clock) 9–19

SELect 9–20

SETColor 9–22

STARt 9–23

STOP 9–24

10 SYSTem Subsystem

DATA 10–5

DSP (Display) 10–6

ERRor 10–7

HEADer 10–8

LONGform 10–9

PRINt 10–10

SETup 10–11

11 MMEMory Subsystem

AUToload 11–8

CATalog 11–9

COPY 11–10

DOWNload 11–11

INITialize 11–13

LOAD [:CONFig] 11–14

LOAD :IASSembler 11–15

MSI (Mass Storage Is) 11–16

PACK 11–17

PURGe 11–17

REName 11–18

STORe [:CONFig] 11–19

UPLoad 11–20

VOLume 11–21

Contents–4

Download from Www.Somanuals.com. All Manuals Search And Download.

Contents

12 INTermodule Subsystem

:INTermodule 12–5

DELete 12–5

HTIMe 12–6

INPort 12–6

INSert 12–7

SKEW<N> 12–8

TREE 12–9

TTIMe 12–10

Part 3 Logic Analyzer Commands

13 MACHine Subsystem

MACHine 13–4

ARM 13–5

ASSign 13–5

LEVelarm 13–6

NAME 13–7

REName 13–8

RESource 13–9

TYPE 13–10

14WLISt Subsystem

WLISt 14–4

DELay 14–5

INSert 14–6

LINE 14–7

OSTate 14–8

OTIMe 14–8

RANGe 14–9

REMove 14–10

XOTime 14–10

XSTate 14–11

XTIMe 14–11

Contents–5

Download from Www.Somanuals.com. All Manuals Search And Download.

Contents

15 SFORmat Subsystem

SFORmat 15–6

CLOCk 15–6

LABel 15–7

MASTer 15–9

MODE 15–10

MOPQual 15–11

MQUal 15–12

REMove 15–13

SETHold 15–13

SLAVe 15–15

SOPQual 15–16

SQUal 15–17

THReshold 15–18

16 STRigger (STRace) Subsystem

Qualifier 16–7

STRigger (STRace) 16–9

ACQuisition 16–9

BRANch 16–10

CLEar 16–12

FIND 16–13

RANGe 16–14

SEQuence 16–16

STORe 16–17

TAG 16–18

TAKenbranch 16–19

TCONtrol 16–20

TERM 16–21

TIMER 16–22

TPOSition 16–23

17 SLISt Subsystem

SLISt 17–7

COLumn 17–7

Contents–6

Download from Www.Somanuals.com. All Manuals Search And Download.

Contents

CLRPattern 17–8

DATA 17–9

LINE 17–9

MMODe 17–10

OPATtern 17–11

OSEarch 17–12

OSTate 17–13

OTAG 17–13

OVERlay 17–14

REMove 17–15

RUNTil 17–15

TAVerage 17–17

TMAXimum 17–17

TMINimum 17–18

VRUNs 17–18

XOTag 17–19

XOTime 17–19

XPATtern 17–20

XSEarch 17–21

XSTate 17–22

XTAG 17–22

18 SWAVeform Subsystem

SWAVeform 18–4

ACCumulate 18–5

ACQuisition 18–5

CENTer 18–6

CLRPattern 18–6

CLRStat 18–7

DELay 18–7

INSert 18–8

RANGe 18–8

REMove 18–9

TAKenbranch 18–9

TPOSition 18–10

Contents–7

Download from Www.Somanuals.com. All Manuals Search And Download.

Contents

19 SCHart Subsystem

SCHart 19–4

ACCumulate 19–4

HAXis 19–5

VAXis 19–7

20 COMPare Subsystem

COMPare 20–4

CLEar 20–5

CMASk 20–5

COPY 20–6

DATA 20–7

FIND 20–9

LINE 20–10

MENU 20–10

RANGe 20–11

RUNTil 20–12

SET 20–13

21 TFORmat Subsystem

TFORmat 21–4

ACQMode 21–5

LABel 21–6

REMove 21–7

THReshold 21–8

22 TTRigger (TTRace) Subsystem

Qualifier 22–6

TTRigger (TTRace) 22–8

ACQuisition 22–9

BRANch 22–9

CLEar 22–12

FIND 22–13

GLEDge 22–14

RANGe 22–15

Contents–8

Download from Www.Somanuals.com. All Manuals Search And Download.

Contents

SEQuence 22–17

SPERiod 22–18

TCONtrol 22–19

TERM 22–20

TIMER 22–21

TPOSition 22–22

23 TWAVeform Subsystem

TWAVeform 23–7

ACCumulate 23–7

ACQuisition 23–8

CENTer 23–8

CLRPattern 23–9

CLRStat 23–9

DELay 23–9

INSert 23–10

MMODe 23–11

OCONdition 23–12

OPATtern 23–13

OSEarch 23–14

OTIMe 23–15

RANGe 23–16

REMove 23–16

RUNTil 23–17

SPERiod 23–18

TAVerage 23–19

TMAXimum 23–19

TMINimum 23–20

TPOSition 23–20

VRUNs 23–21

XCONdition 23–22

XOTime 23–22

XPATtern 23–23

XSEarch 23–24

XTIMe 23–25

Contents–9

Download from Www.Somanuals.com. All Manuals Search And Download.

Contents

24TLISt Subsystem

TLISt 24–7

COLumn 24–7

CLRPattern 24–8

DATA 24–9

LINE 24–9

MMODe 24–10

OCONdition 24–11

OPATtern 24–11

OSEarch 24–12

OSTate 24–13

OTAG 24–14

REMove 24–14

RUNTil 24–15

TAVerage 24–16

TMAXimum 24–16

TMINimum 24–17

VRUNs 24–17

XCONdition 24–18

XOTag 24–18

XOTime 24–19

XPATtern 24–19

XSEarch 24–20

XSTate 24–21

XTAG 24–22

25 SYMBol Subsystem

SYMBol 25–4

BASE 25–5

PATTern 25–6

RANGe 25–6

REMove 25–7

WIDTh 25–8

Contents–10

Download from Www.Somanuals.com. All Manuals Search And Download.

Contents

26 DATA and SETup Commands

Data Format 26–3

:SYSTem:DATA 26–4

Section Header Description 26–6

Section Data 26–6

Data Preamble Description 26–6

Acquisition Data Description 26–10

Time Tag Data Description 26–12

Glitch Data Description 26–14

SYSTem:SETup 26–15

RTC_INFO Section Description 26–17

Part 4Oscilloscope Commands

27 Oscilloscope Root Level Commands

AUToscale 27–3

DIGitize 27–5

28 ACQuire Subsystem

COUNt 28–4

TYPE 28–4

29 CHANnel Subsystem

COUPling 29–4

ECL 29–5

OFFSet 29–6

PROBe 29–7

RANGe 29–8

TTL 29–9

30 DISPlay Subsystem

ACCumulate 30–4

CONNect 30–5

INSert 30–5

Contents–11

Download from Www.Somanuals.com. All Manuals Search And Download.

Contents

LABel 30–7

MINus 30–8

OVERlay 30–8

PLUS 30–9

REMove 30–9

31 MARKer Subsystem

AVOLt 31–6

ABVolt? 31–7

BVOLt 31–7

CENTer 31–8

MSTats 31–8

OAUTo 31–9

OTIMe 31–10

RUNTil 31–11

SHOW 31–12

TAVerage? 31–12

TMAXimum? 31–13

TMINimum? 31–13

TMODe 31–14

VMODe 31–15

VOTime? 31–16

VRUNs? 31–16

VXTime? 31–17

XAUTo 31–18

XOTime? 31–19

XTIMe 31–19

32 MEASure Subsystem

ALL? 32–5

FALLtime? 32–6

FREQuency? 32–6

NWIDth? 32–7

OVERshoot? 32–7

PERiod? 32–8

PREShoot? 32–8

Contents–12

Download from Www.Somanuals.com. All Manuals Search And Download.

Contents

PWIDth? 32–9

RISetime? 32–9

SOURce 32–10

VAMPlitude? 32–11

VBASe? 32–11

VMAX? 32–12

VMIN? 32–12

VPP? 32–13

VTOP? 32–13

33 TIMebase Subsystem

DELay 33–4

MODE 33–5

RANGe 33–6

34TRIGger Subsystem

CONDition 34–5

DELay 34–7

LEVel 34–8

LOGic 34–10

MODE 34–11

PATH 34–12

SLOPe 34–12

SOURce 34–13

35 WAVeform Subsystem

Format for Data Transfer 35–4

Data Conversion 35–6

COUNt? 35–9

DATA? 35–9

FORMat 35–10

POINts? 35–10

PREamble? 35–11

RECord 35–12

SOURce 35–12

Contents–13

Download from Www.Somanuals.com. All Manuals Search And Download.

Contents

SPERiod? 35–13

TYPE? 35–13

VALid? 35–14

XINCrement? 35–15

XORigin? 35–16

XREFerence? 35–16

YINCrement? 35–17

YORigin? 35–17

YREFerence? 35–18

Part 5 Programming Examples

36 Programming Examples

Making a Timing analyzer measurement 36–3

Making a State analyzer measurement 36–5

Making a State Compare measurement 36–9

Transferring the logic analyzer configuration 36–14

Transferring the logic analyzer acquired data 36–17

Checking for measurement completion 36–21

Sending queries to the logic analyzer 36–22

Getting ASCII Data with PRINt? ALL Query 36–24

Reading the disk with the CATalog? ALL query 36–25

Reading the Disk with the CATalog? Query 36–26

Printing to the disk 36–27

Transferring waveform data in Byte format 36–28

Transferring waveform data in Word format 36–30

Using AUToscale and the MEASure:ALL? Query 36–32

Using Sub-routines in a measurement program 36–33

Contents–14

Download from Www.Somanuals.com. All Manuals Search And Download.

Part 1

General Information

Download from Www.Somanuals.com. All Manuals Search And Download.

Introduction to Programming

Download from Www.Somanuals.com. All Manuals Search And Download.

Introduction

This chapter introduces you to the basics of remote programming and

is organized in two sections. The first section, "Talking to the

Instrument," concentrates on initializing the bus, program syntax and

the elements of a syntax instuction. The second section, "Receiving

Information from the Instrument," discusses how queries are sent and

how to retrieve query results from the mainframe instruments.

The programming instructions explained in this book conform to

IEEE Std 488.2-1987, "IEEE Standard Codes, Formats, Protocols, and

Common Commands." These programming instructions provide a

means of remotely controlling the 1660-series logic analyzers. There

are three general categories of use. You can:

• Set up the instrument and start measurements

• Retrieve setup information and measurement results

• Send measurement data to the instrument

The instructions listed in this manual give you access to the

measurements and front panel features of the 1660-series logic

analyzers. The complexity of your programs and the tasks they

accomplish are limited only by your imagination. This programming

reference is designed to provide a concise description of each

instruction.

1–2

Download from Www.Somanuals.com. All Manuals Search And Download.

Talking to the Instrument

In general, computers acting as controllers communicate with the instrument

by sending and receiving messages over a remote interface, such as GPIB or

RS-232C. Instructions for programming the 1660-series logic analyzers will

normally appear as ASCII character strings embedded inside the output

statements of a "host" language available on your controller. The host

language’s input statements are used to read in responses from the

1660-series logic analyzers.

For example, HP 9000 Series 200/300 BASIC uses the OUTPUT statement for

sending commands and queries to the 1660-series logic analyzers. After a

query is sent, the response can be read in using the ENTER statement. All

programming examples in this manual are presented in HP BASIC.

Example

This Basic statement sends a command that causes the logic analyzer’s

machine 1 to be a state analyzer:

OUTPUT XXX;":MACHINE1:TYPE STATE" <terminator>

Each part of the above statement is explained in this section.

1–3

Download from Www.Somanuals.com. All Manuals Search And Download.

Introduction to Programming

Initialization

To make sure the bus and all appropriate interfaces are in a known state,

begin every program with an initialization statement. BASIC provides a

CLEAR command that clears the interface buffer. If you are using GPIB,

CLEAR will also reset the parser in the logic analyzer. The parser is the

program resident in the logic analyzer that reads the instructions you send to

it from the controller.

After clearing the interface, you could preset the logic analyzer to a known

state by loading a predefined configuration file from the disk.

Refer to your controller manual and programming language reference manual

for information on initializing the interface.

Example

This BASIC statement would load the configuration file "DEFAULT " (if it

exists) into the logic analyzer.

OUTPUT XXX;":MMEMORY:LOAD:CONFIG ’DEFAULT ’"

Refer to chapter 10, "MMEMory Subsystem" for more information on the

LOAD command.

Example Program

This program demonstrates the basic command structure used to program

the 1660-series logic analyzers.

10 CLEAR XXX !Initialize instrument interface

20 OUTPUT XXX;":SYSTEM:HEADER ON"!Turn headers on

30 OUTPUT XXX;":SYSTEM:LONGFORM ON"

40 OUTPUT XXX;":MMEM:LOAD:CONFIG ’TEST E’"

!Turn longform on

!Load configuration file

50 OUTPUT XXX;":MENU FORMAT,1"

60 OUTPUT XXX;":RMODE SINGLE"

!Select Format menu for machine 1

!Select run mode

70 OUTPUT XXX;":START"

!Run the measurement

1–4

Download from Www.Somanuals.com. All Manuals Search And Download.

Introduction to Programming

Instruction Syntax

To program the logic analyzer remotely, you must have an understanding of

the command format and structure. The IEEE 488.2 standard governs syntax

rules pertaining to how individual elements, such as headers, separators,

parameters and terminators, may be grouped together to form complete

instructions. Syntax definitions are also given to show how query responses

will be formatted. Figure 1-1 shows the three main syntactical parts of a

typical program statement: Output Command, Device Address, and

Instruction. The instruction is further broken down into three parts:

Instruction header, White space, and Instruction parameters.

Figure 1-1

Program Message Syntax

Output Command

The output command depends on the language you choose to use.

Throughout this guide, HP 9000 Series 200/300 BASIC 6.2 is used in the

programming examples. If you use another language, you will need to find

the equivalents of Basic Commands, like OUTPUT, ENTER and CLEAR in

order to convert the examples. The instructions are always shown between

the double quotes.

1–5

Download from Www.Somanuals.com. All Manuals Search And Download.

Introduction to Programming

Device Address

The location where the device address must be specified also depends on the

host language that you are using. In some languages, this could be specified

outside the output command. In BASIC, this is always specified after the

keyword OUTPUT. The examples in this manual use a generic address of

XXX. When writing programs, the number you use will depend on the cable

you use, in addition to the actual address. If you are using an GPIB, see

chapter 2, "Programming over GPIB." If you are using RS-232C, see

chapter 3, "Programming Over RS-232C."

Instructions

Instructions (both commands and queries) normally appear as a string

embedded in a statement of your host language, such as BASIC, Pascal or C.

The only time a parameter is not meant to be expressed as a string is when

the instruction’s syntax definition specifies block data. There are just a few

instructions which use block data.

Instructions are composed of two main parts: the header, which specifies the

command or query to be sent; and the parameters, which provide additional

data needed to clarify the meaning of the instruction. Many queries do not

use any parameters.

Instruction Header

The instruction header is one or more keywords separated by colons (:). The

command tree in figure 4-1 illustrates how all the keywords can be joined

together to form a complete header (see chapter 4, "Programming and

Documentation Conventions").

The example in figure 1-1 shows a command. Queries are indicated by

adding a question mark (?) to the end of the header. Many instructions can

be used as either commands or queries, depending on whether or not you

have included the question mark. The command and query forms of an

instruction usually have different parameters.

1–6

Download from Www.Somanuals.com. All Manuals Search And Download.

Introduction to Programming

Instruction Terminator

When you look up a query in this programmer’s reference, you’ll find a

paragraph labeled "Returned Format" under the one labeled "Query." The

syntax definition by "Returned format" will always show the instruction

header in square brackets, like [:SYSTem:MENU], which means the text

between the brackets is optional. It is also a quick way to see what the

header looks like.

White Space

White space is used to separate the instruction header from the instruction

parameters. If the instruction does not use any parameters, white space

does not need to be included. White space is defined as one or more spaces.

ASCII defines a space to be a character, represented by a byte, that has a

decimal value of 32. Tabs can be used only if your controller first converts

them to space characters before sending the string to the instrument.

Instruction Parameters

Instruction parameters are used to clarify the meaning of the command or

query. They provide necessary data, such as: whether a function should be

on or off, which waveform is to be displayed, or which pattern is to be looked

for. Each instruction’s syntax definition shows the parameters, as well as the

range of acceptable values they accept. This chapter’s "Parameter Data

Types" section has all of the general rules about acceptable values.

When there is more than one parameter, they are separated by commas (,).

White space surrounding the commas is optional.

Instruction Terminator

An instruction is executed after the instruction terminator is received. The

terminator is the NL (New Line) character. The NL character is an ASCII

linefeed character (decimal 10).

The NL (New Line) terminator has the same function as an EOS (End Of

String) and EOT (End Of Text) terminator.

1–7

Download from Www.Somanuals.com. All Manuals Search And Download.

Introduction to Programming

Header Types

There are three types of headers: Simple Command, Compound Command,

and Common Command.

Simple Command Header

Simple command headers contain a single keyword. START and STOP are

examples of simple command headers typically used in this logic analyzer.

The syntax is: <function><terminator>

When parameters (indicated by <data>) must be included with the simple

command header, the syntax is: <function><white_space><data>

Example

:RMODE SINGLE<terminator>

Compound Command Header

Compound command headers are a combination of two or more program

keywords. The first keyword selects the subsystem, and the last keyword

selects the function within that subsystem. Sometimes you may need to list

more than one subsystem before being allowed to specify the function. The

keywords within the compound header are separated by colons. For

example, to execute a single function within a subsystem, use the following:

:<subsystem>:<function><white_space><data><terminator>

Example

:SYSTEM:LONGFORM ON

To traverse down one level of a subsystem to execute a subsystem within

that subsystem, use the following:

:MMEMORY:LOAD:CONFIG "FILE "

1–8

Download from Www.Somanuals.com. All Manuals Search And Download.

Introduction to Programming

Duplicate Keywords

Common Command Header

Common command headers control IEEE 488.2 functions within the logic

analyzer, such as, clear status. The syntax is:

*<command header><terminator>

No white space or separator is allowed between the asterisk and the

command header. *CLS is an example of a common command header.

Combined Commands in the Same Subsystem

To execute more than one function within the same subsystem, a semicolon

(;) is used to separate the functions:

:<subsystem>:<function><white

space><data>;<function><white space><data><terminator>

Example

:SYSTEM:LONGFORM ON;HEADER ON

Duplicate Keywords

Identical function keywords can be used for more than one subsystem. For

example, the function keyword MMODE may be used to specify the marker

mode in the subsystem for state listing or the timing waveforms:

• :SLIST:MMODE PATTERN - sets the marker mode to pattern in

the state listing.

• :TWAVEFORM:MMODE TIME- sets the marker mode to time in the

timing waveforms.

SLIST and TWAVEFORM are subsystem selectors, and they determine which

marker mode is being modified.

1–9

Download from Www.Somanuals.com. All Manuals Search And Download.

Introduction to Programming

Query Usage

Logic analyzer instructions that are immediately followed by a question mark

(?) are queries. After receiving a query, the logic analyzer parser places the

response in the output buffer. The output message remains in the buffer

until it is read or until another logic analyzer instruction is issued. When

read, the message is transmitted across the bus to the designated listener

(typically a controller).

Query commands are used to find out how the logic analyzer is currently

configured. They are also used to get results of measurements made by the

logic analyzer.

Example

This instruction places the current full-screen time for machine 1 in the

output buffer.

:MACHINE1:TWAVEFORM:RANGE?

In order to prevent the loss of data in the output buffer, the output buffer

must be read before the next program message is sent. Sending another

command before reading the result of the query will cause the output buffer

to be cleared and the current response to be lost. This will also generate a

"QUERY UNTERMINATED" error in the error queue. For example, when you

send the query :TWAVEFORM:RANGE? you must follow that with an input

statement. In Basic, this is usually done with an ENTER statement.

In Basic, the input statement, ENTER XXX; Range, passes the value across

the bus to the controller and places it in the variable Range.

Additional details on how to use queries is in the next section of this chapter,

"Receiving Information for the Instrument."

1–10

Download from Www.Somanuals.com. All Manuals Search And Download.

Introduction to Programming

Program Header Options

Program headers can be sent using any combination of uppercase or

lowercase ASCII characters. Logic analyzer responses, however, are always

returned in uppercase.

Both program command and query headers may be sent in either long form

(complete spelling), short form (abbreviated spelling), or any combination of

long form and short form.

Programs written in long form are easily read and are almost self-

documenting. The short form syntax conserves the amount of controller

memory needed for program storage and reduces the amount of I/O activity.

The rules for short form syntax are discussed in chapter 4, "Programming and

Documentation Conventions."

Example

Either of the following examples turns on the headers and long form.

Long form:

OUTPUT XXX;":SYSTEM:HEADER ON;LONGFORM ON"

Short form:

OUTPUT XXX;":SYST:HEAD ON;LONG ON"

1–11

Download from Www.Somanuals.com. All Manuals Search And Download.

Introduction to Programming

Parameter Data Types

There are three main types of data which are used in parameters. They are

numeric, string, and keyword. A fourth type, block data, is used only for a few

instructions: the DATA and SETup instructions in the SYSTem subsystem

(see chapter 10); the CATalog, UPLoad, and DOWNload instructions in the

MMEMory subsystem (see chapter 11). These syntax rules also show how

data may be formatted when sent back from the 1660-series logic analyzers

as a response.

The parameter list always follows the instruction header and is separated

from it by white space. When more than one parameter is used, they are

separated by commas. You are allowed to include one or more white spaces

around the commas, but it is not mandatory.

Numeric data

For numeric data, you have the option of using exponential notation or using

suffixes to indicate which unit is being used. However, exponential notation

is only applicable to the decimal number base. Tables 5-1 and 5-2 in chapter

5, "Message Communications and System Functions," list all available

suffixes. Do not combine an exponent with a unit.

Example

The following numbers are all equal:

28 = 0.28E2 = 280E-1 = 28000m = 0.028K.

The base of a number is shown with a prefix. The available bases are binary

(#B), octal (#Q), hexadecimal (#H) and decimal (default).

Example

The following numbers are all equal:

#B11100 = #Q34 = #H1C = 28

You may not specify a base in conjunction with either exponents or unit

suffixes. Additionally, negative numbers must be expressed in decimal.

1–12

Download from Www.Somanuals.com. All Manuals Search And Download.

Introduction to Programming

Parameter Data Types

When a syntax definition specifies that a number is an integer, that means

that the number should be whole. Any fractional part would be ignored,

truncating the number. Numeric parameters that accept fractional values are

called real numbers.

All numbers are expected to be strings of ASCII characters. Thus, when

sending the number 9, you send a byte representing the ASCII code for the

character "9" (which is 57, or 0011 1001 in binary). A three-digit number,

like 102, will take up three bytes (ASCII codes 49, 48 and 50). This is taken

care of automatically when you include the entire instruction in a string.

String data

String data may be delimited with either single (’) or double (") quotes.

String parameters representing labels are case-sensitive. For instance, the

labels "Bus A" and "bus a" are unique and should not be used

indiscriminately. Also pay attention to the presence of spaces, because they

act as legal characters just like any other. So, the labels "In" and " In" are

also two different labels.

Keyword data

In many cases a parameter must be a keyword. The available keywords are

always included with the instruction’s syntax definition. When sending

commands, either the longform or shortform (if one exists) may be used.

Uppercase and lowercase letters may be mixed freely. When receiving

responses, upper-case letters will be used exclusively. The use of longform

or shortform in a response depends on the setting you last specified via the

SYSTem:LONGform command (see chapter 10).

1–13

Download from Www.Somanuals.com. All Manuals Search And Download.

Introduction to Programming

Selecting Multiple Subsystems

You can send multiple program commands and program queries for different

subsystems on the same line by separating each command with a semicolon.

The colon following the semicolon enables you to enter a new subsystem.

Multiple commands may be any combination of simple, compound and

common commands.

Example

:MACHINE1:ASSIGN2;:SYSTEM:HEADERS ON

1–14

Download from Www.Somanuals.com. All Manuals Search And Download.

Receiving Information from the Instrument

After receiving a query (logic analyzer instruction followed by a question

mark), the logic analyzer interrogates the requested function and places the

answer in its output queue. The answer remains in the output queue until it

is read, or, until another command is issued. When read, the message is

transmitted across the bus to the designated listener (typically a controller).

The input statement for receiving a response message from an logic

analyzer’s output queue usually has two parameters: the device address and

a format specification for handling the response message.

All results for queries sent in a program message must be read before another

program message is sent. For example, when you send the query

:MACHINE1:ASSIGN?, you must follow that query with an input statement.

In Basic, this is usually done with an ENTER statement.

The format for handling the response messages is dependent on both the

controller and the programming language.

Example

To read the result of the query command :SYSTEM:LONGFORM?you can

execute this Basic statement to enter the current setting for the long form

command in the numeric variable Setting.

ENTER XXX; Setting

1–15

Download from Www.Somanuals.com. All Manuals Search And Download.

Introduction to Programming

Response Header Options

The format of the returned ASCII string depends on the current settings of

the SYSTEM HEADER and LONGFORM commands. The general format is

<instruction_header><space><data><terminator>

The header identifies the data that follows (the parameters) and is controlled

by issuing a :SYSTEM:HEADER ON/OFFcommand. If the state of the

header command is OFF, only the data is returned by the query.

The format of the header is controlled by the :SYSTEM:LONGFORM ON/OFF

command. If long form is OFF , the header will be in its short form and the

header will vary in length, depending on the particular query. The separator

between the header and the data always consists of one space.

A command or query may be sent in either long form or short form, or in any

combination of long form and short form. The HEADER and LONGFORM

commands only control the format of the returned data, and, they have no

affect on the way commands are sent.

Refer to chapter 10, "SYSTem Subsystem" for information on turning the

HEADER and LONGFORM commands on and off.

Examples

The following examples show some possible responses for a

:MACHINE1:SFORMAT:THRESHOLD2?query:

with HEADER OFF:

with HEADER ON and LONGFORM OFF:

:MACH1:SFOR:THR2 <white_space><data><terminator>

with HEADER ON and LONGFORM ON:

:MACHINE1:SFORMAT:THRESHOLD2 <white_space><data><terminator>

1–16

Download from Www.Somanuals.com. All Manuals Search And Download.

Introduction to Programming

Response Data Formats

Both numbers and strings are returned as a series of ASCII characters, as

described in the following sections. Keywords in the data are returned in the

same format as the header, as specified by the LONGform command. Like

the headers, the keywords will always be in uppercase.

Examples

The following are possible responses to the MACHINE1: TFORMAT: LAB?

’ADDR’ query.

Header on; Longform on

MACHINE1:TFORMAT:LABEL "ADDR ",19,POSITIVE<terminator>

Header on;Longform off

MACH1:TFOR:LAB "ADDR ",19,POS<terminator>

Header off; Longform on

"ADDR ",19,POSITIVE<terminator>

Header off; Longform off

"ADDR ",19,POS<terminator>

Refer to the individual commands in Parts 2 through 4 of this guide for

information on the format (alpha or numeric) of the data returned from each

query.

1–17

Download from Www.Somanuals.com. All Manuals Search And Download.

Introduction to Programming

String Variables

Because there are so many ways to code numbers, the 1660-series logic

analyzers handle almost all data as ASCII strings. Depending on your host

language, you may be able to use other types when reading in responses.

Sometimes it is helpful to use string variables in place of constants to send

instructions to the 1660-series logic analyzers, such as, including the headers

with a query response.

Example

This example combines variables and constants in order to make it easier to

switch from MACHINE1 to MACHINE2. In BASIC, the &operator is used for

string concatenation.

5 OUTPUT XXX;":SELECT 1"

!Select the logic analyzer

10 LET Machine$ = ":MACHINE2"

!Send all instructions to machine 2

20 OUTPUT XXX; Machine$ & ":TYPE STATE" !Make machine a state analyzer

30 ! Assign all labels to be positive

40 OUTPUT XXX; Machine$ & ":SFORMAT:LABEL ’CHAN 1’, POS"

50 OUTPUT XXX; Machine$ & ":SFORMAT:LABEL ’CHAN 2’, POS"

60 OUTPUT XXX; Machine$ & ":SFORMAT:LABEL ’OUT’, POS"

99 END

If you want to observe the headers for queries, you must bring the returned

data into a string variable. Reading queries into string variables requires little

attention to formatting.

Example

This command line places the output of the query in the string variable

Result$.

ENTER XXX;Result$

In the language used for this book (HP BASIC 6.2), string variables are case-

sensitive and must be expressed exactly the same each time they are used.

The output of the logic analyzer may be numeric or character data depending

on what is queried. Refer to the specific commands, in Part 2 of this guide,

for the formats and types of data returned from queries.

1–18

Download from Www.Somanuals.com. All Manuals Search And Download.

Introduction to Programming

Numeric Base

Example

The following example shows logic analyzer data being returned to a string

variable with headers off:

10 OUTPUT XXX;":SYSTEM:HEADER OFF"

20 DIM Rang$[30]

30 OUTPUT XXX;":MACHINE1:TWAVEFORM:RANGE?"

40 ENTER XXX;Rang$

50 PRINT Rang$

60 END

After running this program, the controller displays: +1.00000E-05

Numeric Base

Most numeric data will be returned in the same base as shown onscreen.

When the prefix #B precedes the returned data, the value is in the binary

base. Likewise, #Q is the octal base and #H is the hexadecimal base. If no

prefix precedes the returned numeric data, then the value is in the decimal

base.

Numeric Variables

If your host language can convert from ASCII to a numeric format, then you

can use numeric variables. Turning off the response headers will help you

avoid accidently trying to convert the header into a number.

Example

The following example shows logic analyzer data being returned to a numeric

variable.

10 OUTPUT XXX;":SYSTEM:HEADER OFF"

20 OUTPUT XXX;":MACHINE1:TWAVEFORM:RANGE?"

30 ENTER XXX;Rang

40 PRINT Rang

50 END

1–19

Download from Www.Somanuals.com. All Manuals Search And Download.

Introduction to Programming

Definite-Length Block Response Data

This time the format of the number (such as, whether or not exponential

notation is used) is dependant upon your host language. In Basic, the output

will look like: 1.E-5

Definite-Length Block Response Data

Definite-length block response data, also refered to as block data, allows any

type of device-dependent data to be transmitted over the system interface as

a series of data bytes. Definite-length blick data is particularly useful for

sending large quantities of data, or, for sending 8-bit extended ASCII codes.

The syntax is a pound sign ( # ) followed by a non-zero digit representing the

number of digits in the decimal integer. Following the non zero digit is the

decimal integer that states the number of 8-bit data bytes to follow. This

number is followed by the actual data.

Indefinite-length block data is not supported on the 1660-series logic

analyzers.

For example, for transmitting 80 bytes of data, the syntax would be:

Figure 1-2

Definite-length Block Response Data

The "8" states the number of digits that follow, and "00000080" states the

number of bytes to be transmitted, which is 80.

1–20

Download from Www.Somanuals.com. All Manuals Search And Download.

Introduction to Programming

Multiple Queries

You can send multiple queries to the logic analyzer within a single program

message, but you must also read them back within a single program message.

This can be accomplished by either reading them back into a string variable

or into multiple numeric variables.

Example

You can read the result of the query :SYSTEM:HEADER?;LONGFORM? into

the string variable Results$ with the command:

ENTER XXX; Results$

When you read the result of multiple queries into string variables, each

response is separated by a semicolon.

Example

The response of the query :SYSTEM:HEADER?:LONGFORM? with HEADER

and LONGFORM turned on is:

:SYSTEM:HEADER 1;:SYSTEM:LONGFORM 1

If you do not need to see the headers when the numeric values are returned,

then you could use numeric variables. When you are receiving numeric data

into numeric variables, the headers should be turned off. Otherwise the

headers may cause misinterpretation of returned data.

Example

The following program message is used to read the query

:SYSTEM:HEADERS?;LONGFORM? into multiple numeric variables:

ENTER XXX; Result1, Result2

1–21

Download from Www.Somanuals.com. All Manuals Search And Download.

Introduction to Programming

Instrument Status

Status registers track the current status of the logic analyzer. By checking

the instrument status, you can find out whether an operation has been

completed, whether the instrument is receiving triggers, and more.

Chapter 6, "Status Reporting," explains how to check the status of the

instrument.

1–22

Download from Www.Somanuals.com. All Manuals Search And Download.

Programming Over GPIB

Download from Www.Somanuals.com. All Manuals Search And Download.

Introduction

This section describes the interface functions and some general

concepts of the GPIB. In general, these functions are defined by IEEE

488.1 (GPIB bus standard). They deal with general bus management

issues, as well as messages which can be sent over the bus as bus

commands.

2–2

Download from Www.Somanuals.com. All Manuals Search And Download.

Programming Over GPIB

Interface Capabilities

The interface capabilities of the 1660-series logic analyzers, as defined by

IEEE 488.1 are SH1, AH1, T5, TE0, L3, LE0, SR1, RL1, PP0, DC1, DT1, C0,

and E2.

Command and Data Concepts

The GPIB has two modes of operation: command mode and data mode. The

bus is in command mode when the ATN line is true. The command mode is

used to send talk and listen addresses and various bus commands, such as a

group execute trigger (GET). The bus is in the data mode when the ATN line

is false. The data mode is used to convey device-dependent messages across

the bus. These device-dependent messages include all of the instrument

commands and responses found in chapters 8 through 35 of this manual.

Addressing

By using the front-panel I/O and SELECT keys, the GPIB interface can be

placed in either talk only mode, "Printer connected to GPIB," or in addressed

talk/listen mode, "Controller connected to GPIB," (see chapter 16, "The

RS-232/GPIB Menu" in the Agilent Technologies 1660-Series Logic

Analyzer User’s Reference). Talk only mode must be used when you want

the logic analyzer to talk directly to a printer without the aid of a controller.

Addressed talk/listen mode is used when the logic analyzer will operate in

conjunction with a controller. When the logic analyzer is in the addressed

talk/listen mode, the following is true:

Each device on the GPIB resides at a particular address ranging from 0 to

30.

•

The active controller specifies which devices will talk and which will listen.

•

An instrument, therefore, may be talk-addressed, listen-addressed, or

unaddressed by the controller.

•

2–3

Download from Www.Somanuals.com. All Manuals Search And Download.

Programming Over GPIB

Communicating Over the GPIB Bus (HP 9000 Series 200/300 Controller)

If the controller addresses the instrument to talk, it will remain configured to

talk until it receives:

an interface clear message (IFC)

•

another instrument’s talk address (OTA)

•

its own listen address (MLA)

•

a universal untalk (UNT) command.

•

If the controller addresses the instrument to listen, it will remain configured

to listen until it receives:

an interface clear message (IFC)

•

its own talk address (MTA)

•

a universal unlisten (UNL) command.

•

Communicating Over the GPIB Bus (HP 9000 Series

200/300 Controller)

Because GPIB can address multiple devices through the same interface card,

the device address passed with the program message must include not only

the correct instrument address, but also the correct interface code.

Interface Select Code (Selects the Interface)

Each interface card has its own interface select code. This code is used by

the controller to direct commands and communications to the proper

interface. The default is always "7" for GPIB controllers.

Instrument Address (Selects the Instrument)

Each instrument on the GPIB port must have a unique instrument address

between decimals 0 and 30. The device address passed with the program

message must include not only the correct instrument address, but also the

correct interface select code.

2–4

Download from Www.Somanuals.com. All Manuals Search And Download.

Programming Over GPIB

Local, Remote, and Local Lockout

Example

For example, if the instrument address is 4 and the interface select code is 7,

the instruction will cause an action in the instrument at device address 704.

DEVICE ADDRESS = (Interface Select Code) X 100 + (Instrument

Address)

Local, Remote, and Local Lockout

The local, remote, and remote with local lockout modes may be used for

various degrees of front-panel control while a program is running. The logic

analyzer will accept and execute bus commands while in local mode, and the

front panel will also be entirely active. If the 1660-series logic analyzer is in

remote mode, the logic analyzer will go from remote to local with any front

panel activity. In remote with local lockout mode, all controls (except the

power switch) are entirely locked out. Local control can only be restored by

the controller.

Hint

Cycling the power will also restore local control, but this will also reset

certain GPIB states. It also resets the logic analyzer to the power-on defaults

and purges any acquired data in the acquisition memory.

The instrument is placed in remote mode by setting the REN (Remote

Enable) bus control line true, and then addressing the instrument to listen.

The instrument can be placed in local lockout mode by sending the local

lockout (LLO) command (see SYSTem:LOCKout in chapter 9, "Mainframe

Commands"). The instrument can be returned to local mode by either

setting the REN line false, or sending the instrument the go to local (GTL)

command.

2–5

Download from Www.Somanuals.com. All Manuals Search And Download.

Programming Over GPIB

Bus Commands

The following commands are IEEE 488.1 bus commands (ATN true). IEEE

488.2 defines many of the actions which are taken when these commands are

received by the logic analyzer.

Device Clear

The device clear (DCL) or selected device clear (SDC) commands clear the

input and output buffers, reset the parser, clear any pending commands, and

clear the Request-OPC flag.

Group Execute Trigger (GET)

The group execute trigger command will cause the same action as the

START command for Group Run: the instrument will acquire data for the

active waveform and listing displays.

Interface Clear (IFC)

This command halts all bus activity. This includes unaddressing all listeners

and the talker, disabling serial poll on all devices, and returning control to the

system controller.

2–6

Download from Www.Somanuals.com. All Manuals Search And Download.

Programming Over RS-232C

Download from Www.Somanuals.com. All Manuals Search And Download.

Introduction

This chapter describes the interface functions and some general

concepts of the RS-232C. The RS-232C interface on this instrument is

Agilent Technologies’ implementation of EIA Recommended Standard

RS-232C, "Interface Between Data Terminal Equipment and Data

Communications Equipment Employing Serial Binary Data

Interchange." With this interface, data is sent one bit at a time, and

characters are not synchronized with preceding or subsequent data

characters. Each character is sent as a complete entity without

relationship to other events.

3–2

Download from Www.Somanuals.com. All Manuals Search And Download.

Programming Over RS-232C

Interface Operation

The 1660-series logic analyzers can be programmed with a controller over

RS-232C using either a minimum three-wire or extended hardwire interface.

The operation and exact connections for these interfaces are described in

more detail in the following sections. When you are programming a

1660-series logic analyzer over RS-232C with a controller, you are normally

operating directly between two DTE (Data Terminal Equipment) devices as

compared to operating between a DTE device and a DCE (Data

Communications Equipment) device.

When operating directly between two DTE devices, certain considerations

must be taken into account. For a three-wire operation, XON/XOFF must be

used to handle protocol between the devices. For extended hardwire

operation, protocol may be handled either with XON/XOFF or by

manipulating the CTS and RTS lines of the RS-232C link. For both three-

wire and extended hardwire operation, the DCD and DSR inputs to the logic

analyzer must remain high for proper operation.

With extended hardwire operation, a high on the CTS input allows the logic

analyzer to send data, and a low disables the logic analyzer data transmission.

Likewise, a high on the RTS line allows the controller to send data, and a low

signals a request for the controller to disable data transmission. Because

three-wire operation has no control over the CTS input, internal pull-up

resistors in the logic analyzer assure that this line remains high for proper

three-wire operation.

RS-232C Cables

Selecting a cable for the RS-232C interface depends on your specific

application, and, whether you wish to use software or hardware handshake

protocol. The following paragraphs describe which lines of the 1660-series

logic analyzer are used to control the handshake operation of the RS-232C

relative to the system. To locate the proper cable for your application, refer

to the reference manual for your computer or controller. Your computer or

controller manual should describe the exact handshake protocol your

controller can use to operate over the RS-232C bus. Also in this chapter you

will find cable recommendations for hardware handshake.

3–3

Download from Www.Somanuals.com. All Manuals Search And Download.

Programming Over RS-232C

Minimum Three-Wire Interface with Software Protocol

With a three-wire interface, the software (as compared to interface

hardware) controls the data flow between the logic analyzer and the

controller. The three-wire interface provides no hardware means to control

data flow between the controller and the logic analyzer. Therefore,

XON/OFF protocol is the only means to control this data flow. The

three-wire interface provides a much simpler connection between devices

since you can ignore hardware handshake requirements.

The communications software you are using in your computer/controller must

be capable of using XON/XOFF exclusively in order to use three-wire interface

cables. For example, some communications software packages can use

XON/XOFF but are also dependent on the CTS, and DSR lines being true to

communicate.

The logic analyzer uses the following connections on its RS-232C interface for

three-wire communication:

Pin 7 SGND (Signal Ground)

•

Pin 2 TD (Transmit Data from logic analyzer)

•

Pin 3 RD (Receive Data into logic analyzer)

•

The TD (Transmit Data) line from the logic analyzer must connect to the RD

(Receive Data) line on the controller. Likewise, the RD line from the logic

analyzer must connect to the TD line on the controller. Internal pull-up

resistors in the logic analyzer assure the DCD, DSR, and CTS lines remain

high when you are using a three-wire interface.

Extended Interface with Hardware Handshake

With the extended interface, both the software and the hardware can control

the data flow between the logic analyzer and the controller. This allows you

to have more control of data flow between devices. The logic analyzer uses

the following connections on its RS-232C interface for extended interface

communication:

3–4

Download from Www.Somanuals.com. All Manuals Search And Download.

Programming Over RS-232C

Extended Interface with Hardware Handshake

Pin 7 SGND (Signal Ground)

•

Pin 2 TD (Transmit Data from logic analyzer)

Pin 3 RD (Receive Data into logic analyzer)

The additional lines you use depends on your controller’s implementation of

the extended hardwire interface.

Pin 4 RTS (Request To Send) is an output from the logic analyzer which

can be used to control incoming data flow.

•

Pin 5 CTS (Clear To Send) is an input to the logic analyzer which

controls data flow from the logic analyzer.

•

Pin 6 DSR (Data Set Ready) is an input to the logic analyzer which

controls data flow from the logic analyzer within two bytes.

•

Pin 8 DCD (Data Carrier Detect) is an input to the logic analyzer which

controls data flow from the logic analyzer within two bytes.

•

Pin 20 DTR (Data Terminal Ready) is an output from the logic analyzer

which is enabled as long as the logic analyzer is turned on.

•

The TD (Transmit Data) line from the logic analyzer must connect to the RD

(Receive Data) line on the controller. Likewise, the RD line from the logic

analyzer must connect to the TD line on the controller.

The RTS (Request To Send), is an output from the logic analyzer which can

be used to control incoming data flow. A true on the RTS line allows the

controller to send data and a false signals a request for the controller to

disable data transmission.

The CTS (Clear To Send), DSR (Data Set Ready), and DCD (Data Carrier

Detect) lines are inputs to the logic analyzer, which control data flow from

the logic analyzer. Internal pull-up resistors in the logic analyzer assure the

DCD and DSR lines remain high when they are not connected. If DCD or

DSR are connected to the controller, the controller must keep these lines

along with the CTS line high to enable the logic analyzer to send data to the

controller. A low on any one of these lines will disable the logic analyzer data

transmission. Pulling the CTS line low during data transmission will stop

logic analyzer data transmission immediately. Pulling either the DSR or DCD

line low during data transmission will stop logic analyzer data transmission,

but as many as two additional bytes may be transmitted from the logic

analyzer.

3–5

Download from Www.Somanuals.com. All Manuals Search And Download.

Programming Over RS-232C

Cable Examples

HP 9000 Series 300

Figure 3-1 is an example of how to connect the 1660-series logic analyzer to

the HP 98628A Interface card of an HP 9000 series 300 controller. For more

information on cabling, refer to the reference manual for your specific

controller.

Because this example does not have the correct connections for hardware

handshake, you must use the XON/XOFF protocol when connecting the logic

analyzer.

Figure 3-1

Cable Example

HP Vectra Personal Computers and Compatibles

Figures 3-2 through 3-4 give examples of three cables that will work for the

extended interface with hardware handshake. Keep in mind that these

cables should work if your computer’s serial interface supports the four

common RS-232C handshake signals as defined by the RS-232C standard.

The four common handshake signals are Data Carrier Detect (DCD), Data

Terminal Ready (DTR), Clear to Send (CTS), and Ready to Send (RTS).

Figure 3-2 shows the schematic of a 25-pin female to 25-pin male cable. The

following cables support this configuration:

HP 17255D, DB-25(F) to DB-25(M), 1.2 meter

•

HP 17255F, DB-25(F) to DB-25(M), 1.2 meter, shielded.

•

In addition to the female-to-male cables with this configuration, a

male-to-male cable 1.2 meters in length is also available:

HP 17255M, DB-25(M) to DB-25(M), 1.2 meter

•

3–6

Download from Www.Somanuals.com. All Manuals Search And Download.

Programming Over RS-232C

Cable Examples

Figure 3-2

25-pin (F) to 25-pin (M) Cable

Figure 3-3 shows the schematic of a 25-pin male to 25-pin male cable 5

meters in length. The following cable supports this configuration:

HP 13242G, DB-25(M) to DB-25(M), 5 meter

•

Figure 3-3

25-pin (M) to 25-pin (M) Cable

3–7

Download from Www.Somanuals.com. All Manuals Search And Download.

Programming Over RS-232C

Configuring the Logic Analzer Interface

Figure 3-4 shows the schematic of a 9-pin female to 25-pin male cable. The

following cables support this configuration:

HP 24542G, DB-9(F) to DB-25(M), 3 meter

•

HP 24542H, DB-9(F) to DB-25(M), 3 meter, shielded

•

HP 45911-60009, DB-9(F) to DB-25(M), 1.5 meter

•

Figure 3-4

9-pin (F) to 25-pin (M) Cable

Configuring the Logic Analzer Interface

The RS-232C menu field in the System Configuration Menu allows you access

to the RS-232C Configuration menu where the RS-232C interface is

configured. If you are not familiar with how to configure the RS-232C

interface, refer to the Agilent Technologies 1660-Series Logic Analyzer

User’s Reference.

3–8

Download from Www.Somanuals.com. All Manuals Search And Download.

Programming Over RS-232C

Interface Capabilities

The baud rate, stopbits, parity, protocol, and databits must be configured

exactly the same for both the controller and the logic analyzer to properly

communicate over the RS-232C bus. The RS-232C interface capabilities of

the 1660-series logic analyzers are listed below:

Baud Rate: 110, 300, 600, 1200, 2400, 4800, 9600, or 19.2k

•

Stop Bits: 1, 1.5, or 2

•

Parity: None, Odd, or Even

•

Protocol: None or XON/XOFF

•

Data Bits: 8

•

Protocol

NONE With a three-wire interface, selecting NONE for the protocol

does not allow the sending or receiving device to control dataflow. No

control over the data flow increases the possibility of missing data or

transferring incomplete data.

With an extended hardwire interface, selecting NONE allows a hardware

handshake to occur. With hardware handshake, the hardware signals control

dataflow.

XON/XOFF XON/XOFF stands for Transmit On/Transmit Off. With this

mode, the receiver (controller or logic analyzer) controls dataflow, and,

can request that the sender (logic analyzer or controller) stop dataflow.

By sending XOFF (ASCII 19) over its transmit data line, the receiver

requests that the sender disables data transmission. A subsequent XON

(ASCII 17) allows the sending device to resume data transmission.

Data Bits

Data bits are the number of bits sent and received per character that

represent the binary code of that character. Characters consist of either 7 or

8 bits, depending on the application. The 1660-series logic analyzer supports

8 bit only.

8 Bit Mode Information is usually stored in bytes (8 bits at a time).

With 8-bit mode, you can send and receive data just as it is stored,

without the need to convert the data.

3–9

Download from Www.Somanuals.com. All Manuals Search And Download.

Programming Over RS-232C

RS-232C Bus Addressing

The controller and the 1660-series logic analyzer must be in the same bit

mode to properly communicate over the RS-232C. This means that the

controller must have the capability to send and receive 8 bit data.

See Also

For more information on this command see chapter 10, "System Commands."

3–11

Download from Www.Somanuals.com. All Manuals Search And Download.

3–12

Download from Www.Somanuals.com. All Manuals Search And Download.

Programming and

Documentation Conventions

Download from Www.Somanuals.com. All Manuals Search And Download.

Introduction

This chapter covers the programming conventions used in

programming the instrument, as well as the documentation

conventions used in this manual. This chapter also contains a detailed

description of the command tree and command tree traversal.

4–2

Download from Www.Somanuals.com. All Manuals Search And Download.

Programming and Documentation Conventions

Truncation Rule

The truncation rule for the keywords used in headers and parameters is:

If the longform has four or fewer characters, there is no change in the

•

shortform. When the longform has more than four characters the

shortform is just the first four characters, unless the fourth character is

a vowel. In that case only the first three characters are used.

There are some commands that do not conform to the truncation rule by design.

These will be noted in their respective description pages.

Some examples of how the truncation rule is applied to various commands

are shown in table 4-1.

Table 4-1

Truncation Examples

Long Form

Short Form

OFF

DATA

STAR

LONG

DEL

START

LONGFORM

DELAY

ACCUMULATE

ACC

4–3

Download from Www.Somanuals.com. All Manuals Search And Download.

Programming and Documentation Conventions

Infinity Representation

The representation of infinity is 9.9E+37 for real numbers and 32767 for

integers. This is also the value returned when a measurement cannot be

made.

Sequential and Overlapped Commands

IEEE 488.2 makes the distinction between sequential and overlapped

commands. Sequential commands finish their task before the execution of

the next command starts. Overlapped commands run concurrently; therefore,

the command following an overlapped command may be started before the

overlapped command is completed. The overlapped commands for the

1660-series logic analyzers are STARt and STOP.

Response Generation

IEEE 488.2 defines two times at which query responses may be buffered.

The first is when the query is parsed by the instrument and the second is

when the controller addresses the instrument to talk so that it may read the

response. The 1660-series logic analyzers will buffer responses to a query

when it is parsed.

Syntax Diagrams

At the beginning of each chapter in Parts 2 through 4, "Commands," is a

syntax diagram showing the proper syntax for each command. All characters

contained in a circle or oblong are literals, and must be entered exactly as

shown. Words and phrases contained in rectangles are names of items used

with the command and are described in the accompanying text of each

command. Each line can only be entered from one direction as indicated by

the arrow on the entry line. Any combination of commands and arguments

that can be generated by following the lines in the proper direction is

syntactically correct. An argument is optional if there is a path around it.

When there is a rectangle which contains the word "space," a white space

character must be entered. White space is optional in many other places.

4–4

Download from Www.Somanuals.com. All Manuals Search And Download.

Programming and Documentation Conventions

Notation Conventions and Definitions

The following conventions are used in this manual when describing

programming rules and example.

< > Angular brackets enclose words or characters that are used to symbolize a

program code parameter or a bus command

::= "is defined as." For example, A ::= B indicates that A can be replaced by B in

any statement containing A.

"or." Indicates a choice of one element from a list. For example, A | B

indicates A or B, but not both.

... An ellipsis (trailing dots) is used to indicate that the preceding element may

be repeated one or more times.

[ ] Square brackets indicate that the enclosed items are optional.

{ } When several items are enclosed by braces and separated by vertical bars (|),

one, and only one of these elements must be selected.

XXX Three Xs after an ENTER or OUTPUT statement represent the device

address required by your controller.

<NL> Linefeed (ASCII decimal 10).

The Command Tree

The command tree (figure 4-1) shows all commands in the 1660-series logic

analyzers and the relationship of the commands to each other. Parameters

are not shown in this figure. The command tree allows you to see what the

1660-series logig analyzer parser expects to receive. All legal headers can be

created by traversing down the tree, adding keywords until the end of a

branch has been reached.

4–5

Download from Www.Somanuals.com. All Manuals Search And Download.

Programming and Documentation Conventions

Tree Traversal Rules

Command Types

As shown in chapter 1, "Header Types," there are three types of headers.

Each header has a corresponding command type. This section shows how

they relate to the command tree.

System Commands The system commands reside at the top level of

the command tree. These commands are always parsable if they occur at

the beginning of a program message, or are preceded by a colon. START

and STOP are examples of system commands.

Subsystem Commands Subsystem commands are grouped together

under a common node of the tree, such as the MMEMORY commands.

Common Commands Common commands are independent of the tree,

and do not affect the position of the parser within the tree. *CLS and

*RST are examples of common commands.

Tree Traversal Rules

Command headers are created by traversing down the command tree. For

each group of keywords not separated by a branch, one keyword must be

selected. As shown on the tree, branches are always preceded by colons. Do

not add spaces around the colons. The following two rules apply to traversing

the tree:

A leading colon (the first character of a header) or a <terminator> places the

parser at the root of the command tree.

Executing a subsystem command places you in that subsystem until a leading

colon or a <terminator> is found. The parser will stay at the colon above the

keyword where the last header terminated. Any command below that point

can be sent within the current program message without sending the

keywords(s) which appear above them.

4–6

Download from Www.Somanuals.com. All Manuals Search And Download.

Programming and Documentation Conventions

Tree Traversal Rules

The following examples are written using HP BASIC 6.2 on a HP 9000 Series

200/300 Controller. The quoted string is placed on the bus, followed by a

carriage return and linefeed (CRLF). The three Xs (XXX) shown in this

manual after an ENTER or OUTPUT statement represents the device address

required by your controller.

Example 1

In this example, the colon between SYSTEM and HEADERis necessary since

SYSTEM:HEADER is a compound command. The semicolon between the

HEADERcommand and the LONGFORMcommand is the required <program

message unit separator> . The LONGFORM command does not need

SYSTEMpreceding it, since the SYSTEM:HEADERcommand sets the parser

to the SYSTEM node in the tree.

OUTPUT XXX;":SYSTEM:HEADER ON;LONGFORM ON"

Example 2

In the first line of this example, the subsystem selector is implied for the

STORE command in the compound command. The STOREcommand must

be in the same program message as the INITIALIZE command, since the

<program message terminator> will place the parser back at the root

of the command tree.

A second way to send these commands is by placing MMEMORY: before the

STORE command as shown in the fourth line of this example 2.

OUTPUT XXX;":MMEMORY:INITIALIZE;STORE ’FILE ’,’FILE

DESCRIPTION’"

OUTPUT XXX;":MMEMORY:INITIALIZE"

OUTPUT XXX;":MMEMORY:STORE ’FILE ’,’FILE DESCRIPTION’"

Example 3

In this example, the leading colon before SYSTEM tells the parser to go back

to the root of the command tree. The parser can then see the

SYSTEM:PRINT command.

OUTPUT XXX;":MMEM:CATALOG?;:SYSTEM:PRINT ALL"

4–7

Download from Www.Somanuals.com. All Manuals Search And Download.

Programming and Documentation Conventions

Tree Traversal Rules

Figure 4-1

1660-Series Logic Analyzer Command Tree

4–8

Download from Www.Somanuals.com. All Manuals Search And Download.

Programming and Documentation Conventions

Tree Traversal Rules

Figure 4-1 (continued)

1660-Series Logic Analyzer Command Tree (continued)

4–9

Download from Www.Somanuals.com. All Manuals Search And Download.

Programming and Documentation Conventions

Tree Traversal Rules

Figure 4-1 (continued)

1660-Series Logic Analyzer Command Tree (continued)

4–10

Download from Www.Somanuals.com. All Manuals Search And Download.

Programming and Documentation Conventions

Tree Traversal Rules

Table 4-2

Alphabetic Command Cross-Reference

Command

Subsystem

Command

Subsystem

ABVOLt

MARKer

DSP

SYSTem

ACCumulate

SCHart, SWAVeform, TWAVeform,

DISPlay

ECL

CHANnel

EOI

ERRor

Mainframe

SYSTem

MEASure

ACQMode

ACQuisition

TFORmat

STRigger, SWAVeform, TTRigger,

TWAVeform

FALLtime

FIND

FORMat

FREQuency

GLEDge

HAXis

COMPare, STRigger, TTRigger

WAVeform

MEASure

ALL

ARM

MEASure

MACHine

ASSign

AUToload

AUToscale

AVOLt

MACHine

TTRigger

MMEMory

SCHart

MODULE LEVEL

MARKer

HEADer

HTIMe

SYSTem

INTermodule

SFORmat

BASE

SYMBol

Mainframe

MOPQual

MQUal

MSI

BEEPer

BRANch

BVOLt

SFORmat

MMEMory

STRigger, TTRigger

MARKer

NAME

CAPability

CARDcage

CATalog

CENTer

CESE

Mainframe

MACHine

OCONdition

OPATtern

OSEarch

OSTate

OTAG

Mainframe

TLISt, TWAVeform

MMEMory

SLISt, TLISt, TWAVeform

SLISt, TLISt, WLISt

SWAVeform, TWAVeform, MARKer

Mainframe

CESR

Mainframe

COMPare, STRigger, TTRigger

SFORmat

SLISt, SWAVeform, TLISt, TWAVeform

SWAVeform, TWAVeform

COMPare

SLISt, TLISt

TRIGger

DISPlay

COMPare, MMEMory

ACQuire, WAVeforml

CHANNel

COMPare, SLISt, SYSTem, TLISt,

WAVeform

SWAVeform, TWAVeform, WLISt,

TIMebase. TRIGger

INTermodule

CLEar

SLISt, TLISt

OTIMe

OVERlay

PACK

MMEMory

PATTern

PURGe

RANGe

CLOCk

TWAVeform, WLISt

SLISt

CLRPattern

CLRStat

CMASk

COLumn

CONDition

CONNect

COPY

SYMBol

SYSTem

MMEMory

COMPare, STRigger, SWAVeform,

SYMBol, TTRigger, TWAVeform, WLISt

SFORmat, SLISt, SWAVeform, SYMBol,

TFORmat, TLISt, TWAVeform,

COUNt

COUPling

DATA

REMove

WLISt

REName

RESource

RMODe

RTC

MACHine

MMEMory

MACHine

Mainframe

DELay

DELete

DIGitize

ROOT

MMEMory

DOWNload

4–11

Download from Www.Somanuals.com. All Manuals Search And Download.

Programming and Documentation Conventions

Tree Traversal Rules

Table 4-2 (continued)

Alphabetic Command Cross-Reference (continued)

Command

Subsystem

Command

Subsystem

INITialize

INPort

MMEMory

PLUS

POINts

PREamble

PREShoot

PROBe

PURGe

PWIDth

RANGe

DISPlay

INTermodule

WAVeform

INSert

INTermodule, SWAVeform, TWAVeform,

WLISt, DISPlay

SFORmat, TFORmat, DISPlay

Mainframe

TRIGger

MACHine

SYSTem

WAVeform

LABel

MEASure

LER

CHANnel

LEVel

MMEMory

LEVelarm

LINE

MEASure

COMPare, SLISt, TLISt, WLISt

MMEMory

COMPare, STRigger, SWAVeform,

SYMBol, TTRigger, TWAVeform, WLISt,

CHANnel, TIMebase

WAVeform

LOAD

LOCKout

LOGic

LONGform

MASTer

Mainframe

RECord

TREE

TTIMe

TYPE

UPLoad

VAXis

TRIGger

INTermodule

SYSTem

INTermodule

SFORmat

MACHine

COMPare, Mainframe

Mainframe

MMEMory

MESE

MESR

SCHart

Mainframe

DISPlay

VOLume

VRUNs

WIDTh

XCONdition

XOTag

XOTime

XPATtern

XSEarch

XSTate

XTAG

MMEMory

MINus

MMODe

MODE

MOPQual

MQUal

MSI

SLISt, TLISt, TWAVeform

SYMBol

SLISt, TLISt, TWAVeform

SFORmat, TIMebase, TRIGger

SFORmat

TLISt, TWAVeform

SLISt, TLISt

SFORmat

SLISt, TLISt, TWAVeform, WLISt

SLISt, TLISt, TWAVeform

SLISt, TLISt, WLISt

SLISt, TLISt

MMEMory

MSTats

NAME

MARKer

MACHine

NWIDth

OAUTo

OCONdition

OFFSet

OPATtern

OSEarch

OSTate

OTAG

MEASure

MARKer

XTIMe

TWAVeform, WLISt

TLISt, TWAVeform

CHANnel

SLISt, TLISt, TWAVeform

SLISt, TLISt, WLISt

SLISt, TLISt

OTIMe

OVERlay

OVERshoot

PACK

TWAVeform, WLISt, MARKer

SLISt, DISPlay

MEASure

MMEMory

PATH

TRIGger

PERiod

PATTern

MEASure

SYMBol

4–12

Download from Www.Somanuals.com. All Manuals Search And Download.

Programming and Documentation Conventions

Tree Traversal Rules

Table 4-2 (continued)

Alphabetic Command Cross-Reference (continued)

Command

Subsystem

Command

Subsystem

REMove

SFORmat, SLISt, SWAVeform, SYMBol,

TFORmat, TLISt, TWAVeform, DISPlay

MACHine

TPOSition

STRigger, SWAVeform, TTRigger,

TWAVeform

REName

RESource

RISetime

RMODe

RTC

TREE

Intermodule

MMEMory

TTIMe

INTermodule

CHANnel

MACHine

TTL

MEASure

TYPE

MACHine, ACQuire, WAVeform

MMEMory

Mainframe

UPLoad

VALid

Mainframe

WAVeform

RUNTil

COMPare, SLISt, TLISt, TWAVeform,

MARKer

VAMPlitude

VAXis

MEASure

SCHart

SELect

SEQuence

SET

Mainframe

VBAse

VOLume

VRUNs

WIDTh

XCONdition

XOTag

XOTime

XPATtern

XSEarch

XSTate

XTAG

MEASure

STRigger, TTRigger

COMPare

MMEMory

SLISt, TLISt, TWAVeform

SYMBol

SETColor

SETHold

SETup

Mainframe

SFORmat

TLISt, TWAVeform

SLISt, TLISt

SYSTem

SHOW

MARKer

SLISt, TLISt, TWAVeform, WLISt

SLISt, TLISt, TWAVeform

SLISt, TLISt, WLISt

SLISt, TLISt

SKEW

INTermodule

SLAVe

SFORmat

SLOPe

TRIGger

SOPQual

SOURce

SPERiod

SQUal

SFORmat

MEASure, TRIGger, WAVeform

TTRigger, TWAVeform, WAVeform

SFORmat

XTIMe

TWAVeform, WLISt

STARt

Mainframe

MMEMory, STRigger

STRigger

STOP

STORe

TAG

TAKenbranch

TAVerage

TCONtrol

TERM

THReshold

TIMER

TMAXimum

TMINimum

TMODe

STRigger, SWAVeform

SLISt, TLISt, TWAVeform, MARKer

STRigger, TTRigger

SFORmat, TFORmat

STRigger, TTRigger

SLISt, TLISt, TWAVeform, MARKer

MARKer

4–13

Download from Www.Somanuals.com. All Manuals Search And Download.

Programming and Documentation Conventions

Command Set Organization

Table 4-2 (continued)

Alphabetic Command Cross-Reference (continued)

Command

Subsystem

Command

Subsystem

VMAX

MEASure

XSTate

SLISt, TLISt, WLISt

SLISt, TLISt

TWAVeform, WLISt, MARKer

WAVeform

VMIN

MEASure

XTAG

VMODe

VOLume

VOTime

VPP

MARKer

XTIMe

MMEMory

YINCrement

YORigin

MARKer

MEASure

YREFerence

VRUNs

VTOP

VXTime

WIDTh

XAUTo

XCONdition

XINCrement

SLISt, TLISt, TWAVeform, MARKer

MEASure

MARKer

SYMBol

MARKer

TLISt, TWAVeform

WAVeform

XORigin

WAVeform

XOTag

SLISt, TLISt

XOTime

XPATtern

XREFerence

SLISt, TLISt, TWAVeform, WLISt, MARKer

SLISt, TLISt, TWAVeform

WAVeform

XSEarch

SLISt, TLISt, TWAVeform

Command Set Organization

The command set for the 1660-series logic analyzers is divided into 28

separate groups: common commands, mainframe commands, system

commands and 23 sets of subsystem commands. Each of the 28 groups of

commands is described in a seperate chapter in Parts 2 through 4,

"Commands." Each of the chapters contain a brief description of the

subsystem, a set of syntax diagrams for those commands, and finally, the

commands for that subsystem in alphabetical order. The commands are

shown in the long form and short form using upper and lowercase letters. As

an example AUToloadindicates that the long form of the command is

AUTOLOAD and the short form of the command is AUT. Each of the

commands contain a description of the command, its arguments, and the

command syntax.

4–14

Download from Www.Somanuals.com. All Manuals Search And Download.

Programming and Documentation Conventions

Subsystems

There are 23 subsystems in this instrument. In the command tree (figure

4-1) they are shown as branches, with the node above showing the name of

the subsystem. Only one subsystem may be selected at a time. At power on,

the command parser is set to the root of the command tree; therefore, no

subsystem is selected. The 23 subsystems in the 1660-series logic analyzers

are:

SYSTem - controls some basic functions of the instrument.

•

MMEMory - provides access to the internal disk drive.

•

INTermodule - provides access to the Intermodule bus (IMB).

•

MACHine - provides access to analyzer functions and subsystems.

•

WLISt - allows access to the mixed (timing/state) functions.

•

SFORmat - allows access to the state format functions.

•

STRigger - allows access to the state trigger functions.

•

SLISt - allows access to the state listing functions.

•

SWAVeform - allows access to the state waveforms functions.

•

SCHart - allows access to the state chart functions.

•

COMPare - allows access to the compare functions.

•

TFORmat - allows access to the timing format functions.

•

TTRigger - allows access to the timing trigger functions.

•

TWAVeform - allows access to the timing waveforms functions.

•

TLISt - allows access to the timing listing functions.

•

SYMBol - allows access to the symbol specification functions.

•

ACQuire - sets up acquisition conditions for the digitize function.

•

CHANnel - controls the oscilloscope channel display and vertical axis.

•

DISPlay - allows data to be displayed.

•

MARKer - allows access to the oscilloscope’s time and voltage markers.

•

MEASure - allows automatic parametric measurements.

•

TIMebase - controls the oscilloscope timebase and horizontal axis.

•

4–15

Download from Www.Somanuals.com. All Manuals Search And Download.

Programming and Documentation Conventions

Program Examples

TRIGger - allows access to the oscilloscope’s trigger functions.

•

WAVeform - used to transfer waveform data from the oscilloscope to a

controller.

•

Program Examples

The program examples in the following chapters and chapter 36,

"Programming Examples," were written on an HP 9000 Series 200/300

controller using the HP BASIC 6.2 language. The programs always assume a

generic address for the 1660-series logic analyzers of XXX.

In the examples, you should pay special attention to the ways in which the

command and/or query can be sent. Keywords can be sent using either the

long form or short form (if one exists for that word). With the exception of

some string parameters, the parser is not case-sensitive. Uppercase and

lowercase letters may be mixed freely. System commands like HEADer and

LONGform allow you to dictate what forms the responses take, but they have

no affect on how you must structure your commands and queries.

Example

The following commands all set the Timing Waveform Delay to 100 ms.

Keywords in long form, numbers using the decimal format.

OUTPUT XXX;":MACHINE1:TWAVEFORM:DELAY .1"

Keywords in short form, numbers using an exponential format.

OUTPUT XXX;":MACH1:TWAV:DEL 1E-1"

Keywords in short form using lowercase letters, numbers using a suffix.

OUTPUT XXX;":mach1:twav:del 100ms"

In these examples, the colon shown as the first character of the command is

optional on the 1660-series logic analyzers. The space between DELay and the

argument is required.

4–16

Download from Www.Somanuals.com. All Manuals Search And Download.

Message Communication and

System Functions

Download from Www.Somanuals.com. All Manuals Search And Download.

Introduction

This chapter describes the operation of instruments that operate in

compliance with the IEEE 488.2 (syntax) standard. It is intended to

give you enough basic information about the IEEE 488.2 Standard to

successfully program the logic analyzer. You can find additional

detailed information about the IEEE 488.2 Standard in ANSI/IEEE Std

488.2-1987, "IEEE Standard Codes, Formats, Protocols, and

Common Commands."

The 1660-series logic analyzer is designed to be compatible with other

Agilent Technologies IEEE 488.2 compatible instruments.

Instruments that are compatible with IEEE 488.2 must also be

compatible with IEEE 488.1 (GPIB bus standard); however, IEEE

488.1 compatible instruments may or may not conform to the IEEE

488.2 standard. The IEEE 488.2 standard defines the message

exchange protocols by which the instrument and the controller will

communicate. It also defines some common capabilities, which are

found in all IEEE 488.2 instruments. This chapter also contains a few

items which are not specifically defined by IEEE 488.2, but deal with

message communication or system functions.

The syntax and protocol for RS-232C program messages and response

messages for the 1660-series logic analyzer are structured very similar

to those described by 488.2. In most cases, the same structure shown

in this chapter for 488.2 will also work for RS-232C. Because of this,

no additional information has been included for RS-232C.

5–2

Download from Www.Somanuals.com. All Manuals Search And Download.

Message Communication and System Functions

Protocols

The protocols of IEEE 488.2 define the overall scheme used by the controller

and the instrument to communicate. This includes defining when it is

appropriate for devices to talk or listen, and what happens when the protocol

is not followed.

Functional Elements

Before proceeding with the description of the protocol, a few system

components should be understood.

Input Buffer The input buffer of the instrument is the memory area

where commands and queries are stored prior to being parsed and

executed. It allows a controller to send a string of commands to the

instrument which could take some time to execute, and then proceed to

talk to another instrument while the first instrument is parsing and

executing commands.

Output Queue The output queue of the instrument is the memory area

where all output data (<response messages>) are stored until read by

the controller.

Parser The instrument’s parser is the component that interprets the

commands sent to the instrument and decides what actions should be

taken. "Parsing" refers to the action taken by the parser to achieve this

goal. Parsing and executing of commands begins when either the

instrument recognizes a <program message terminator> (defined later in

this chapter) or the input buffer becomes full. If you wish to send a long

sequence of commands to be executed and then talk to another

instrument while they are executing, you should send all the commands

before sending the <program message terminator>.

5–3

Download from Www.Somanuals.com. All Manuals Search And Download.

Message Communication and System Functions

Protocols

Protocol Overview

The instrument and controller communicate using <program message>s and

<response message>s. These messages serve as the containers into which

sets of program commands or instrument responses are placed. <program

message>s are sent by the controller to the instrument, and <response

message>s are sent from the instrument to the controller in response to a

query message. A <query message> is defined as being a <program

message> which contains one or more queries. The instrument will only talk

when it has received a valid query message, and therefore has something to

say. The controller should only attempt to read a response after sending a

complete query message, but before sending another <program message>.

The basic rule to remember is that the instrument will only talk when

prompted to, and it then expects to talk before being told to do something

else.

Protocol Operation

When the instrument is turned on, the input buffer and output queue are

cleared, and the parser is reset to the root level of the command tree.

The instrument and the controller communicate by exchanging complete

<program message>s and <response message>s. This means that the

controller should always terminate a <program message> before attempting

to read a response. The instrument will terminate <response message>s

except during a hardcopy output.

If a query message is sent, the next message passing over the bus should be

the <response message>. The controller should always read the complete

<response message> associated with a query message before sending another

<program message> to the same instrument.

The instrument allows the controller to send multiple queries in one query

message. This is referred to as sending a "compound query." As will be

noted later in this chapter, multiple queries in a query message are separated

by semicolons. The responses to each of the queries in a compound query

will also be separated by semicolons.

Commands are executed in the order they are received.

5–4

Download from Www.Somanuals.com. All Manuals Search And Download.

Message Communication and System Functions

Syntax Diagrams

Protocol Exceptions

If an error occurs during the information exchange, the exchange may not be

completed in a normal manner. Some of the protocol exceptions are shown

below.

Command Error A command error will be reported if the instrument

detects a syntax error or an unrecognized command header.

Execution Error An execution error will be reported if a parameter is

found to be out of range, or if the current settings do not allow execution

of a requested command or query.

Device-specific Error A device-specific error will be reported if the

instrument is unable to execute a command for a strictly device

dependent reason.

Query Error A query error will be reported if the proper protocol for

reading a query is not followed. This includes the interrupted and

unterminated conditions described in the following paragraphs.

Syntax Diagrams

The example syntax diagram is in this chapter are similar to the syntax

diagrams in the IEEE 488.2 specification. Commands and queries are sent to

the instrument as a sequence of data bytes. The allowable byte sequence for

each functional element is defined by the syntax diagram that is shown.

The allowable byte sequence can be determined by following a path in the

syntax diagram. The proper path through the syntax diagram is any path

that follows the direction of the arrows. If there is a path around an element,

that element is optional. If there is a path from right to left around one or

more elements, that element or those elements may be repeated as many

times as desired.

5–5

Download from Www.Somanuals.com. All Manuals Search And Download.

Message Communication and System Functions

Syntax Diagrams

Figure 5-1

Example syntax diagram

5–6

Download from Www.Somanuals.com. All Manuals Search And Download.

Message Communication and System Functions

Syntax Overview

This overview is intended to give a quick glance at the syntax defined by

IEEE 488.2. It will help you understand many of the things about the syntax

you need to know.

IEEE 488.2 defines the blocks used to build messages which are sent to the

instrument. A whole string of commands can therefore be broken up into

individual components.

Figure 5-1 is an example syntax diagram and figure 5-2 shows a breakdown of

an example <program message>. There are a few key items to notice:

A semicolon separates commands from one another. Each <program

message unit> serves as a container for one command. The <program

message unit>s are separated by a semicolon.

•

A <program message> is terminated by a <NL> (new line). The

•

recognition of the <program message terminator>, or <PMT>, by the

parser serves as a signal for the parser to begin execution of commands.

The <PMT> also affects command tree traversal (Chapter 4,

"Programming and Documentation Conventions").

Multiple data parameters are separated by a comma.

•

The first data parameter is separated from the header with one or more

spaces.

•

The header MACHINE1:ASSIGN 2,3 is an example of a compound header.

It places the parser in the machine subsystem until the <NL> is

encountered.

•

A colon preceding the command header returns you to the top of the

command tree.

•

5–7

Download from Www.Somanuals.com. All Manuals Search And Download.

Message Communication and System Functions

Syntax Overview

Figure 5-2

<program message> Parse Tree

5–8

Download from Www.Somanuals.com. All Manuals Search And Download.

Message Communication and System Functions

Syntax Overview

Upper/Lower Case Equivalence

Upper and lower case letters are equivalent. The mnemonic SINGLE has

the same semantic meaning as the mnemonic single.

<white space> is defined to be one or more characters from the ASCII set of

0 - 32 decimal, excluding 10 decimal (NL). <white space> is used by several

instrument listening components of the syntax. It is usually optional, and can

be used to increase the readability of a program.

Suffix Multiplier The suffix multipliers that the instrument will accept

are shown in table 5-1.

Table 5-1

Value

Mnemonic

1E18

1E15

1E12

1E9

1E6

1E3

1E-3

1E-6

1E-9

1E-12

1E-15

1E-18

5–9

Download from Www.Somanuals.com. All Manuals Search And Download.

Message Communication and System Functions

Syntax Overview

Suffix Unit The suffix units that the instrument will accept are shown

in table 5-2.

Table 5-2

Suffix

Referenced Unit

Volt

Second

5–10

Download from Www.Somanuals.com. All Manuals Search And Download.

Status Reporting

Download from Www.Somanuals.com. All Manuals Search And Download.

Introduction

Status reporting allows you to use information about the instrument in

your programs, so that you have better control of the measurement

process. For example, you can use status reporting to determine

when a measurement is complete, thus controlling your program, so

that it does not get ahead of the instrument. This chapter describes

the status registers, status bytes and status bits defined by IEEE

488.2 and discusses how they are implemented in the 1660-series

logic analyzers. Also in this chapter is a sample set of steps you use to

perform a serial poll over GPIB.

The status reporting feature available over the bus is the serial poll.

IEEE 488.2 defines data structures, commands, and common bit

definitions. There are also instrument-defined structures and bits.

The bits in the status byte act as summary bits for the data structures

residing behind them. In the case of queues, the summary bit is set if

the queue is not empty. For registers, the summary bit is set if any

enabled bit in the event register is set. The events are enabled via the

corresponding event enable register. Events captured by an event

read with their associated commands. The *CLS command clears all

event registers and all queues except the output queue. If *CLS is

sent immediately following a <program message terminator>, the

output queue will also be cleared.

6–2

Download from Www.Somanuals.com. All Manuals Search And Download.

Status Reporting

Figure 6-1

Status Byte Structures and Concepts

6–3

Download from Www.Somanuals.com. All Manuals Search And Download.

Status Reporting

Event Status Register

The Event Status Register is an IEEE 488.2 defined register. The bits in this

bit will only be cleared if the register is read.

Service Request Enable Register

The Service Request Enable Register is an 8-bit register. Each bit enables

the corresponding bit in the status byte to cause a service request. The sixth

bit does not logically exist and is always returned as a zero. To read and

write to this register, use the *SRE? and *SRE commands.

Bit Definitions

The following mnemonics are used in figure 6-1 and in chapter 8, "Common

Commands:"

MAV - message available

Indicates whether there is a response in the output queue.

ESB - event status bit

Indicates if any of the conditions in the Standard Event Status Register are

set and enabled.

MSS - master summary status

Indicates whether the device has a reason for requesting service. This bit is

returned for the *STB? query.

RQS - request service

Indicates if the device is requesting service. This bit is returned during a

serial poll. RQS will be set to 0 after being read via a serial poll (MSS is not

reset by *STB?).

6–4

Download from Www.Somanuals.com. All Manuals Search And Download.

Status Reporting

Bit Definitions

MSG - message

Indicates whether there is a message in the message queue (Not

implemented in the 1660-series logic analyzers).

PON - power on

Indicates power has been turned on.

URQ - user request

Always returns a 0 from the 1660-series logic analyzer.

CME - command error

Indicates whether the parser detected an error.

The error numbers and strings for CME, EXE, DDE, and QYE can be read from a

device-defined queue (which is not part of IEEE 488.2) with the query

:SYSTEM:ERROR?.

EXE - execution error

Indicates whether a parameter was out of range, or inconsistent with current

settings.

DDE - device specific error

Indicates whether the device was unable to complete an operation for device

dependent reasons.

QYE - query error

Indicates whether the protocol for queries has been violated.

RQC - request control

Always returns a 0 from the 1660-series logic analyzer.

OPC - operation complete

Indicates whether the device has completed all pending operations. OPC is

controlled by the *OPC common command. Because this command can

appear after any other command, it serves as a general-purpose operation

complete message generator.

6–5

Download from Www.Somanuals.com. All Manuals Search And Download.

Status Reporting

Key Features

LCL - remote to local

Indicates whether a remote to local transition has occurred.

MSB - module summary bit

Indicates that an enable event in one of the modules Status registers has

occurred.

Key Features

A few of the most important features of Status Reporting are listed in the

following paragraphs.

Operation Complete

The IEEE 488.2 structure provides one technique that can be used to find

out if any operation is finished. The *OPC command, when sent to the

instrument after the operation of interest, will set the OPC bit in the

Standard Event Status Register. If the OPC bit and the RQS bit have been

enabled, a service request will be generated. The commands that affect the

OPC bit are the overlapped commands.

Example

OUTPUT XXX;"*SRE 32 ; *ESE 1" !enables an OPC service

request

Status Byte

The Status Byte contains the basic status information which is sent over the

bus in a serial poll. If the device is requesting service (RQS set), and the

controller serial-polls the device, the RQS bit is cleared. The MSS (Master

Summary Status) bit (read with *STB?) and other bits of the Status Byte are

not be cleared by reading them. Only the RQS bit is cleared when read.

The Status Byte is cleared with the *CLS common command.

6–6

Download from Www.Somanuals.com. All Manuals Search And Download.

Status Reporting

Serial Poll

Figure 6-2.

Service Request Enabling

Serial Poll

The 1660-series logic analyzer supports the IEEE 488.1 serial poll feature.

When a serial poll of the instrument is requested, the RQS bit is returned on

bit 6 of the status byte.

6–7

Download from Www.Somanuals.com. All Manuals Search And Download.

Status Reporting

Serial Poll

Using Serial Poll (GPIB)

This example will show how to use the service request by conducting a serial

poll of all instruments on the GPIB bus. In this example, assume that there

are two instruments on the bus: a Logic Analyzer at address 7 and a printer at

address 1.

The program command for serial poll using HP BASIC 6.2 is Stat =

SPOLL(707). The address 707 is the address of the logic analyzer in the this

example. The command for checking the printer is Stat = SPOLL(701)

because the address of that instrument is 01 on bus address 7. This

command reads the contents of the GPIB Status Register into the variable

called Stat. At that time bit 6 of the variable Stat can be tested to see if it is

set (bit 6 = 1).

The serial poll operation can be conducted in the following manner:

1 Enable interrupts on the bus. This allows the controller to see the

SRQ line.

2 Disable interrupts on the bus.

3 If the SRQ line is high (some instrument is requesting service) then

check the instrument at address 1 to see if bit 6 of its status register is

high.

4 To check whether bit 6 of an instruments status register is high, use

the following BASIC statement•: IF BIT (Stat, 6) THEN

5 If bit 6 of the instrument at address 1 is not high, then check the

instrument at address 7 to see if bit 6 of its status register is high.

6 As soon as the instrument with status bit 6 high is found check the

rest of the status bits to determine what is required.

The SPOLL(707) command causes much more to happen on the bus than

simply reading the register. This command clears the bus automatically,

addresses the talker and listener, sends SPE (serial poll enable) and SPD

(serial poll disable) bus commands, and reads the data. For more

information about serial poll, refer to your controller manual, and

programming language reference manuals.

After the serial poll is completed, the RQS bit in the 1660-series logic

analyzer Status Byte Register will be reset if it was set. Once a bit in the

Status Byte Register is set, it will remain set until the status is cleared with a

*CLS command, or the instrument is reset.

6–8

Download from Www.Somanuals.com. All Manuals Search And Download.

Error Messages

Download from Www.Somanuals.com. All Manuals Search And Download.

Introduction

This chapter lists the error messages that relate to the 1660-series

logic analyzers.

7–2

Download from Www.Somanuals.com. All Manuals Search And Download.

Error Messages

Device Dependent Errors

200 Label not found

201 Pattern string invalid

202 Qualifier invalid

203 Data not available

300 RS-232C error

Command Errors

–100 Command error (unknown command)(generic error)

–101 Invalid character received

–110 Command header error

–111 Header delimiter error

–120 Numeric argument error

–121 Wrong data type (numeric expected)

–123 Numeric overflow

–129 Missing numeric argument

–130 Non numeric argument error (character,string, or block)

–131 Wrong data type (character expected)

–132 Wrong data type (string expected)

–133 Wrong data type (block type #D required)

–134 Data overflow (string or block too long)

–139 Missing non numeric argument

–142 Too many arguments

–143 Argument delimiter error

–144 Invalid message unit delimiter

7–3

Download from Www.Somanuals.com. All Manuals Search And Download.

Error Messages

Execution Errors

–200 Can Not Do (generic execution error)

–201 Not executable in Local Mode

–202 Settings lost due to return-to-local or power on

–203 Trigger ignored

–211 Legal command, but settings conflict

–212 Argument out of range

–221 Busy doing something else

–222 Insufficient capability or configuration

–232 Output buffer full or overflow

–240 Mass Memory error (generic)

–241 Mass storage device not present

–242 No media

–243 Bad media

–244 Media full

–245 Directory full

–246 File name not found

–247 Duplicate file name

–248 Media protected

Internal Errors

–300 Device Failure (generic hardware error)

–301 Interrupt fault

–302 System Error

–303 Time out

–310 RAM error

–311 RAM failure (hardware error)

–312 RAM data loss (software error)

–313 Calibration data loss

–320 ROM error

7–4

Download from Www.Somanuals.com. All Manuals Search And Download.

Error Messages

Query Errors

–321 ROM checksum

–322 Hardware and Firmware incompatible

–330 Power on test failed

–340 Self Test failed

–350 Too Many Errors (Error queue overflow)

Query Errors

–400 Query Error (generic)

–410 Query INTERRUPTED

–420 Query UNTERMINATED

–421 Query received. Indefinite block response in progress

–422 Addressed to Talk, Nothing to Say

–430 Query DEADLOCKED

7–5

Download from Www.Somanuals.com. All Manuals Search And Download.

7–6

Download from Www.Somanuals.com. All Manuals Search And Download.

Part 2

Mainframe Commands

Download from Www.Somanuals.com. All Manuals Search And Download.

Common Commands

Download from Www.Somanuals.com. All Manuals Search And Download.

Introduction

The common commands are defined by the IEEE 488.2 standard.

These commands must be supported by all instruments that comply

with this standard. Refer to figure 8-1 and table 8-1 for the common

commands syntax diagram.

The common commands control some of the basic instrument

functions; such as, instrument identification and reset, how status is

read and cleared, and how commands and queries are received and

processed by the instrument. The common commands are:

*CLS

•

*ESE

•

*ESR

•

*IDN

•

*IST

•

*OPC

•

*OPT

•

*PRE

•

*RST

•

*SRE

•

*STB

•

*TRG

•

*TST

•

*WAI

•

Common commands can be received and processed by the 1660-series

logic analyzers, whether they are sent over the bus as separate

program messages or within other program messages. If an

instrument subsystem has been selected and a common command is

received by the instrument, the logic analyzer will remain in the

selected subsystem.

8–2

Download from Www.Somanuals.com. All Manuals Search And Download.

Common Commands

Example

If the program message in this example is received by the logic

analyzer, it will initialize the disk and store the file and clear the status

information. This is not be the case if some other type of command is

received within the program message.

":MMEMORY:INITIALIZE;*CLS; STORE ’FILE ’,’DESCRIPTION’"

Example

This program message initializes the disk, selects the module in slot A,

then stores the file. In this example, :MMEMORY must be sent again

in order to reenter the memory subsystem and store the file.

":MMEMORY:INITIALIZE;:SELECT 1;:MMEMORY:STORE ’FILE ’,

’DESCRIPTION’"

Status Registers

Each status register has an associated status enable (mask) register.

By setting the bits in the status enable register you can select the

status information you wish to use. Any status bits that have not been

masked (enabled in the enable register) will not be used to report

status summary information to bits in other status registers.

Refer to chapter 6, "Status Reporting," for a complete discussion of

how to read the status registers and how to use the status information

available from this instrument.

8–3

Download from Www.Somanuals.com. All Manuals Search And Download.

Common Commands

Figure 8-1

Common Commands Syntax Diagram

8–4

Download from Www.Somanuals.com. All Manuals Search And Download.

Common Commands

*CLS (Clear Status)

Table 8-1

Common Command Parameter Values

Parameter

Values

mask

An integer, 0 through 255.

An integer, 0 through 65535.

pre_mask

*CLS (Clear Status)

Command

*CLS

The *CLS common command clears all event status registers, queues, and

data structures, including the device defined error queue and status byte. If

the *CLS command immediately follows a <program message terminator>,

the output queue and the MAV (Message Available) bit will be cleared. Refer

to chapter 6, "Status Reporting," for a complete discussion of status.

Example

OUTPUT XXX;"*CLS"

8–5

Download from Www.Somanuals.com. All Manuals Search And Download.

Common Commands

*ESE (Event Status Enable)

Command

*ESE <mask>

The *ESE command sets the Standard Event Status Enable Register bits.

The Standard Event Status Enable Register contains a bit to enable the

status indicators detailed in table 8-2. A 1 in any bit position of the Standard

Event Status Enable Register enables the corresponding status in the

Standard Event Status Enable Register. Refer to Chapter 6, "Status

Reporting" for a complete discussion of status.

<mask> An integer from 0 to 255

Example

In this example, the *ESE 32 command will enable CME (Command Error),

bit 5 of the Standard Event Status Enable Register. Therefore, when a

command error occurs, the event summary bit (ESB) in the Status Byte

OUTPUT XXX;"*ESE 32"

Query

*ESE?

The *ESE query returns the current contents of the enable register.

Returned Format

Example

OUTPUT XXX;"*ESE?"

8–6

Download from Www.Somanuals.com. All Manuals Search And Download.

Common Commands

*ESR (Event Status Register)

Table 8-2

Standard Event Status Enable Register

Bit Position

Bit Weight

Enables

128

PON - Power On

URQ - User Request

CME - Command Error

EXE - Execution Error

DDE - Device Dependent Error

QYE - Query Error

RQC - Request Control

OPC - Operation Complete

*ESR (Event Status Register)

Query

*ESR?

The *ESR query returns the contents of the Standard Event Status Register.

Reading the register clears the Standard Event Status Register.

Returned Format

<status> An integer from 0 to 255

Example

If a command error has occurred, and bit 5 of the ESE register is set, the

string variable Esr_event$ will have bit 5 (the CME bit) set.

10 OUTPUT XXX;"*ESE 32

20 OUTPUT XXX;"*ESR?"

30 ENTER XXX; Esr_event$

!Enables bit 5 of the status register

!Queries the status register

!Reads the query buffer

8–7

Download from Www.Somanuals.com. All Manuals Search And Download.

Common Commands

*ESR (Event Status Register)

Table 8-3 shows the Standard Event Status Register. The table details the

meaning of each bit position in the Standard Event Status Register and the

bit weight. When you read Standard Event Status Register, the value

returned is the total bit weight of all the bits that are high at the time you

read the byte.

Table 8-3

The Standard Event Status Register

Bit Position

Bit Weight

Bit Name

Condition

128

PON

0 = register read - not in power up mode

1 = power up

URQ

CME

0 = user request - not used - always zero

0 = no command errors

1 = a command eror has been detected

EXE

DDE

QYE

0 = no execution errors

1 = an execution error has been detected

0 = no device dependent error has been detected

1 = a device dependent error has been detected

0 = no query errors

1 = a query error has been detected

RQC

OPC

0 = request control - not used - always zero

0 = operation is not complete

1 = operation is complete

8–8

Download from Www.Somanuals.com. All Manuals Search And Download.

Common Commands

*IDN (Identification Number)

Query

*IDN?

The *IDN? query allows the instrument to identify itself. It returns the string:

"HEWLETT-PACKARD,1660A,0,REV <revision_code>"

An *IDN? query must be the last query in a message. Any queries after the

*IDN? in the program message are ignored.

Returned Format

HEWLETT-PACKARD,1660A,0,REV <revision code>

<revision Four digit-code in the format XX.XXrepresenting the current ROM revision.

code>

Example

OUTPUT XXX;"*IDN?"

*IST (Individual Status)

Query

*IST?

The *IST query allows the instrument to identify itself during parallel poll by

allowing the controller to read the current state of the IEEE 488.1 defined

"ist" local message in the instrument. The response to this query is

dependent upon the current status of the instrument.

Figure 8-2 shows the *IST data structure.

Returned Format

<id> 0 or 1

Indicates the "ist" local message is false.

Indicates the "ist" local message is true.

8–9

Download from Www.Somanuals.com. All Manuals Search And Download.

Common Commands

*IST (Individual Status)

Example

OUTPUT XXX;"*IST?"

Figure 8-2

*IST Data Structure

8–10

Download from Www.Somanuals.com. All Manuals Search And Download.

Common Commands

*OPC (Operation Complete)

Command

*OPC

The *OPC command will cause the instrument to set the operation complete

bit in the Standard Event Status Register when all pending device operations

have finished. The commands which affect this bit are the overlapped

commands. An overlapped command is a command that allows execution of

subsequent commands while the device operations initiated by the

overlapped command are still in progress. The overlapped commands for the

1660-series logic analyzers are STARt and STOP.

Example

OUTPUT XXX;"*OPC"

Query

*OPC?

The *OPC query places an ASCII "1" in the output queue when all pending

device operations have been completed.

Returned Format

1<NL>

Example

OUTPUT XXX;"*OPC?"

8–11

Download from Www.Somanuals.com. All Manuals Search And Download.

Common Commands

*OPT (Option Identification)

Query

*OPT?

The *OPT query identifies the software installed in the 1660-series logic

analyzer. This query returns nine parameters. The first parameter indicates

whether you are in the system. The next two parameters indicate any

software options installed, and the next parameter indicates whether

intermodule is available for the system. The last five parameters list the

installed software for the modules in slot A through E for an 16500A logic

analysis mainframe. However, the 1660-series logic analyzers have only two

slots (A and B); therefore, only the first and second parameters of the last

five parameters will be relevant. A zero in any of the last eight parameters

indicates that the corresponding software is not currently installed. The

name returned for software options and module software is the same name

that appears in the field in the upper-left corner of the menu for each option

or module.

Returned Format

{SYSTEM},{<option>|0},{<option>|0},{INTERMODULE|0},{<module>|0}

,{<module>|0},{<module>|0},{<module>|0},{<module>|0}<NL>

<option> Name of software option.

<module> Name of module software.

Example

OUTPUT XXX;"*OPT?"

8–12

Download from Www.Somanuals.com. All Manuals Search And Download.

Common Commands

*PRE (Parallel Poll Enable Register Enable)

Command

*PRE <mask>

The *PRE command sets the parallel poll register enable bits. The Parallel

Poll Enable Register contains a mask value that is ANDed with the bits in the

Status Bit Register to enable an "ist" during a parallel poll. Refer to table 8-4

for the bits in the Parallel Poll Enable Register and for what they mask.

<pre_mask> An integer from 0 to 65535.

Example

This example will allow the 1660-series logic analyzers to generate an "ist"

when a message is available in the output queue. When a message is

available, the MAV (Message Available) bit in the Status Byte Register will be

high.

Output XXX;"*PRE 16"

Query

*PRE?

The *PRE? query returns the current value of the register.

Returned format

<mask> An integer from 0 through 65535 representing the sum of all bits that are set. .

Example

OUTPUT XXX;"*PRE?"

8–13

Download from Www.Somanuals.com. All Manuals Search And Download.

Common Commands

*RST (Reset)

Table 8-4

1660-Series Logic Analyzer Parallel Poll Enable Register

Bit Position

Bit Weight

Enables

15 -8

Not used

128

Not used

MSS - Master Summary Status

ESB - Event Status

MAV - Message Available

LCL - Local

Not used

MSB - Module Summary

*RST (Reset)

The *RST command is not implemented on the 1660-series logic analyzer.

The 1660-series logic analyzer will accept this command, but the command

has no affect on the logic analyzer.

The *RST command is generally used to place the logic analyzer in a

predefined state. Because the 1660-series logic analyzer allows you to store

predefined configuration files for individual modules, or for the entire system,

resetting the logic analyzer can be accomplished by simply loading the

appropriate configuration file. For more information, refer to chapter 11,

"MMEMory Subsystem."

8–14

Download from Www.Somanuals.com. All Manuals Search And Download.

Common Commands

*SRE (Service Request Enable)

Command

*SRE <mask>

The *SRE command sets the Service Request Enable Register bits. The

Service Request Enable Register contains a mask value for the bits to be

enabled in the Status Byte Register. A one in the Service Request Enable

will disable the bit. Refer to table 8-5 for the bits in the Service Request

Enable Register and what they mask.

Refer to Chapter 6, "Status Reporting," for a complete discussion of status.

<mask> An integer from 0 to 255

Example

This example enables a service request to be generated when a message is

available in the output queue. When a message is available, the MAV

(Message Available) bit will be high.

OUTPUT XXX;"*SRE 16"

Query

*SRE?

The *SRE query returns the current value.

Returned Format

<mask> An integer from 0 to 255 representing the sum of all bits that are set.

Example

OUTPUT XXX;"*SRE?"

8–15

Download from Www.Somanuals.com. All Manuals Search And Download.

Common Commands

*STB (Status Byte)

Table 8-5

1660-Series Logic Analyzer Service Request Enable Register

Bit Position

Bit Weight

Enables

15-8

not used

128

not used

MSS - Master Summary Status (always 0)

ESB - Event Status

MAV - Message Available

LCL- Local

not used

MSB - Module Summary

*STB (Status Byte)

Query

*STB?

The *STB query returns the current value of the instrument’s status byte.

The MSS (Master Summary Status) bit, and, not the RQS (Request Service)

bit is reported on bit 6. The MSS indicates whether or not the device has at

least one reason for requesting service. Refer to table 8-6 for the meaning of

the bits in the status byte.

Refer to Chapter 6, "Status Reporting" for a complete discussion of status.

Returned Format

<value> An integer from 0 through 255

Example

OUTPUT XXX;"*STB?"

8–16

Download from Www.Somanuals.com. All Manuals Search And Download.

Common Commands

*TRG (Trigger)

Table 8-6

The Status Byte Register

Bit Position

Bit Weight

Bit Name

Condition

128

0 = not Used

MSS

ESB

MAV

LCL

0 = instrument has no reason for service

1 = instrument is requesting service

0 = no event status conditions have occurred

1 = an enabled event status condition has occurred

0 = no output messages are ready

1 = an output message is ready

0 = a remote-to-local transition has not occurred

1 = a remote-to-local transition has occurred

not used

MSB

0 = a module or the system has activity to report

1 = no activity to report

0 = False = Low

1 = True = High

*TRG (Trigger)

Command

*TRG

The *TRG command has the same effect as a Group Execute Trigger (GET).

That effect is as if the START command had been sent for intermodule group

run. If no modules are configured in the Intermodule menu, this command

has no effect.

Example

OUTPUT XXX;"*TRG"

8–17

Download from Www.Somanuals.com. All Manuals Search And Download.

Common Commands

*TST (Test)

Query

*TST?

The *TST query returns the results of the power-up self-test. The result of

that test is a 9-bit mapped value which is placed in the output queue. A one

in the corresponding bit means that the test failed and a zero in the

corresponding bit means that the test passed. Refer to table 8-7 for the

meaning of the bits returned by a TST? query.

Returned Format

<result> An integer 0 through 511

Example

10 OUTPUT XXX;"*TST?"

20 ENTER XXX;Tst_value

Table 8-7

Bits Returned by *TST? Query (Power-Up Test Results)

Bit Position

Bit Weight

Test

256

128

Disk Test

not used

Front-panel Test

HIL Test

Display Test

Interupt Test

RAM Test

ROM Test

8–18

Download from Www.Somanuals.com. All Manuals Search And Download.

Common Commands

*WAI (Wait)

Command

*WAI

The *WAI command causes the device to wait until completing all of the

overlapped commands before executing any further commands or queries.

An overlapped command is a command that allows execution of subsequent

commands while the device operations initiated by the overlapped command

are still in progress. Some examples of overlapped commands for the

1660-series logic analyzers are STARt and STOP.

Example:

OUTPUT XXX;"*WAI"

8–19

Download from Www.Somanuals.com. All Manuals Search And Download.

8–20

Download from Www.Somanuals.com. All Manuals Search And Download.

Mainframe Commands

Download from Www.Somanuals.com. All Manuals Search And Download.

Introduction

Mainframe commands control the basic operation of the instrument

for the 1660-series logic analyzers. The 1660-series logic analyzers are

similar to a 16500A logic analysis system with either a single logic

analyzer module (1660A) or one logic analyzer and one oscilloscope

module (1660AS) installed.

The main difference in mainframe commands for the 1660-series logic

analyzers is the number of modules. In the 1660 series logic analyzers,

module 0 contains the system level commands, module 1 contains the

logic analyzer level commands, and module 2 contains the

oscilloscope module commands. The command parser in the

1660-series logic analyzers is designed to accept programs written for

the 16500A logic analysis system with a 16550A logic analyzer and/or

oscilloscope modules. The main difference is how you specify the

SELECT command. Remember, the 1660-series logic analyzer is

equivalent only to a mainframe with up to two modules; therefore, if

you specify 3 through 10 for the SELECT command in your program,

the command parser will take no action.

This chapter contains mainframe commands with a syntax example

for each command. Each syntax example contains parameters for the

1600-series logic analyzers only. Refer to figure 9-1 and table 9-1 for

the Mainframe commands syntax diagram. The mainframe commands

are:

• BEEPer

• CAPability

• CARDcage

• CESE

• CESR

• EOI

• LER

• LOCKout

• MENU

• MESE

• MESR

• RMODe

• RTC

• SELect

• SETColor

• STARt

• STOP

9–2

Download from Www.Somanuals.com. All Manuals Search And Download.

Mainframe Commands

Figure 9-1

Mainframe Commands Syntax Diagram

9–3

Download from Www.Somanuals.com. All Manuals Search And Download.

Mainframe Commands

Figure 9-1 (continued)

Mainframe Commands Syntax Diagram (continued)

9–4

Download from Www.Somanuals.com. All Manuals Search And Download.

Mainframe Commands

Table 9-1

Mainframe Parameter Values

Parameter

Values

An integer from 0 to 65535.

value

module

enable_value

index

day

An integer 0 through 2 (3 through 10 unused).

An integer.

An integer from 0 to 255.

An integer from 0 to 5.

An integer from 1 through 31

An integer from 1 through 12

An integer from 1990 through 2089

An integer from 0 through 23

An integer from 0 through 59

An integer from 1 to 7.

month

year

hour

minute

second

color

hue

An integer from 0 to 100.

sat

lum

9–5

Download from Www.Somanuals.com. All Manuals Search And Download.

Mainframe Commands

BEEPer

Command

:BEEPer [{ON|1}|{OFF|0}]

The BEEPer command sets the beeper mode, which turns the beeper sound

of the instrument on and off. When BEEPer is sent with no argument, the

beeper will be sounded without affecting the current mode.

Example

OUTPUT XXX;":BEEPER"OUTPUT XXX;":BEEP ON"

Query

:BEEPer?

The BEEPer? query returns the mode currently selected.

Returned Format

[:BEEPer] {1|0}<NL>

Example

OUTPUT XXX;":BEEPER?"

9–6

Download from Www.Somanuals.com. All Manuals Search And Download.

Mainframe Commands

CAPability

Query

:CAPability?

The CAPability query returns the HP-SL (HP System Language) and lower

level capability sets implemented in the device.

Table 9-2 lists the capability sets implemented in the 1660-series logic

analyzers.

Returned Format

[:CAPability]

IEEE488,1987,SH1,AH1,T5,L4,SR1,RL1,PP1,DC1,DT1,C0,E2<NL>

Example

OUTPUT XXX;":CAPABILITY?"

Table 9-2

1660-Series Logic Analyzer Capability Sets

Mnemonic

Capability Name

Implementation

Source Handshake

Acceptor Handshake

Talker (or TE - Extended Talker)

Listener (or LE - Extended Listener)

Service Request

SH1

AH1

SR1

RL1

PP1

DC1

DT1

Remote Local

Parallel Poll

Device Clear

Device Trigger

Any Controller

Electrical Characteristic

9–7

Download from Www.Somanuals.com. All Manuals Search And Download.

Mainframe Commands

CARDcage

Query

:CARDcage?

The CARDcage query returns a series of integers which identify the modules

that are installed in the mainframe. The returned string is in two parts. The

first five two-digit numbers identify the card type. The identification number

for the logic analyzer is 32. The identification number for the oscilloscope is

13. A "-1" in the first part of the string indicates no card is installed in the

slot.

The five single-digit numbers in the second part of the string indicate which

slots have cards installed. The module assignment for the logic analyzer will

always be 1. The second number will contain a 0 unless the oscilloscope

module is installed (1660AS), in which case it will return a 1. The possible

values for the module assignment are 0 and 1 where 0 indicates the module

software is not recognized or not loaded.

Returned Format

[:CARDcage]

<ID>,<ID>,<ID>,<ID>,<ID><assign>,<assign>,<assign>,

<ID> An integer indicating the card identification number.

<assign> An integer indicating the module assignment.

Example

OUTPUT XXX;":CARDCAGE?"

9–8

Download from Www.Somanuals.com. All Manuals Search And Download.

Mainframe Commands

CESE (Combined Event Status Enable)

Command

:CESE <value>

The CESE command sets the Combined Event Status Enable register. This

combined status of all of the MESE (Module Event Status Enable) registers

of the 1660-series logic analyzer. Table 9-3 lists the bit values for the CESE

<value> An integer from 0 to 65535

Example

OUTPUT XXX;":CESE 32"

Query

:CESE?

The CESE? query returns the current setting.

Returned Format

[:CESE] <value><NL>

Example

OUTPUT XXX;":CESE?"

Table 9-3

1660-Series Logic Analyzer Combined Event Status Enable Register

Bit

Weight

Enables

3 to 15

not used

oscilloscope

logic analyzer

Intermodule

9–9

Download from Www.Somanuals.com. All Manuals Search And Download.

Mainframe Commands

CESR (Combined Event Status Register)

Query

:CESR?

The CESR query returns the contents of the Combined Event Status register.

This register contains the combined status of all of the MESRs (Module Event

Status Registers) of the 1660-series logic analyzer. Table 9-4 lists the bit

values for the CESR register.

Returned Format

Example

[:CESR] <value><NL>

<value> An integer from 0 to 65535

OUTPUT XXX;":CESR?"

Table 9-4

1660-Series Logic Analyzer Combined Event Status Register

Bit

Bit Weight

Bit Name

Condition

3 to 15

0 = not used

Oscilloscope

Logic analyzer

Intermodule

0 = No new status

1 = Status to report

0 = No new status

1 = Status to report

0 = No new status

1 = Status to report

9–10

Download from Www.Somanuals.com. All Manuals Search And Download.

Mainframe Commands

EOI (End Or Identify)

Command

:EOI {{ON|1}|{OFF|0}}

The EOI command specifies whether or not the last byte of a reply from the

instrument is to be sent with the EOI bus control line set true or not. If EOI

is turned off, the logic analyzer will no longer be sending IEEE 488.2

compliant responses.

Example

OUTPUT XXX;":EOI ON"

Query

:EOI?

The EOI? query returns the current status of EOI.

Returned Format

[:EOI] {1|0}<NL>

Example

OUTPUT XXX;":EOI?"

LER (LCL Event Register)

Query

:LER?

The LER query allows the LCL Event Register to be read. After the LCL

Event Register is read, it is cleared. A one indicates a remote-to-local

transition has taken place. A zero indicates a remote-to-local transition has

not taken place.

Returned Format

[:LER] {0|1}<NL>

Example

OUTPUT XXX;":LER?"

9–11

Download from Www.Somanuals.com. All Manuals Search And Download.

Mainframe Commands

LOCKout

Command

:LOCKout {{ON|1}|{OFF|0}}

The LOCKout command locks out or restores front panel operation. When

this function is on, all controls (except the power switch) are entirely locked

out.

Example

OUTPUT XXX;":LOCKOUT ON"

Query

:LOCKout?

The LOCKout query returns the current status of the LOCKout command.

Returned Format

[:LOCKout] {0|1}<NL>

Example

OUTPUT XXX;":LOCKOUT?"

Command

:MENU <module>[,<menu>]

The MENU command puts a menu on the display. The first parameter

specifies the desired module. The optional second parameter specifies the

desired menu in the module (defaults to 0). Table 9-5 lists the parameters

and the menus.

<module> Selects module or system (integer) 0 selects the system, 1 selects the logic

analyzer, and 2 selects the oscilloscope. –2, –1 and 3 to 10 unused)

<menu> Selects menu (integer)

9–12

Download from Www.Somanuals.com. All Manuals Search And Download.

Mainframe Commands

Example

Table 9-5

OUTPUT XXX;":MENU 0,1"

Menu Parameter Values

Parameters

0,0

0,2

0,3

0,4

1,0

1,1

1,2

1,3

1,4

1,5

1,6

1,7

1,8

1,9

1,10

1,11

1,12

1,13

2,0

2,1

2,2

2,3

2,4

2,5

System RS-232/GPIB

System Disk

System Utilities

System Test

Analyzer Configuration

Format 1

Format 2

Trigger 1

Trigger 2

Waveform 1

Waveform 2

Listing 1

Listing 2

Mixed

Compare 1

Compare 2

Chart 1

Chart 2

Channel

Trigger

Display

Auto-measure

Marker

Calibration

9–13

Download from Www.Somanuals.com. All Manuals Search And Download.

Mainframe Commands

MESE<N> (Module Event Status Enable)

Query

:MENU?

The MENU query returns the current menu selection.

Returned Format

[:MENU] <module>,<menu><NL>

Example

OUTPUT XXX;":MENU?"

MESE<N> (Module Event Status Enable)

Command

:MESE<N> <enable_value>

The MESE command sets the Module Event Status Enable register. This

specifies the module, and the parameter specifies the enable value. For the

1660-series logic analyzer, the <N> index 0, 1, or 2 refers to system, logic

analyzer, or oscilloscope respectively.

<N> An integer 0 through 2 (3 through 10 unused).

<enable_value> An integer from 0 through 255

Example

OUTPUT XXX;":MESE1 3"

Query

:MESE<N>?

The query returns the current setting. Tables 9-6, 9-7, and 9-8 list the

Module Event Status Enable register bits, bit weights, and what each bit

masks for the mainframe, logic analyzer, and oscilloscope respectively.

[:MESE<N>] <enable_value><NL>

Returned Format

Example

OUTPUT XXX;":MESE1?"

9–14

Download from Www.Somanuals.com. All Manuals Search And Download.

Mainframe Commands

MESE<N> (Module Event Status Enable)

Table 9-6

1660-Series Mainframe (Intermodule) Module Event Status Enable Register

Bit Position

Bit Weight

Enables

128

not used

RNT - Intermodule Run Until Satisfied

MC - Intermodule Measurement Complete

Table 9-7

1660-Series Logic Analyzer Module Event Status Enable Register

Bit Position

Bit Weight

Enables

128

not used

Pattern searches failed

Trigger found

RNT - Run Until Satisfied

MC - Measurement Complete

9–15

Download from Www.Somanuals.com. All Manuals Search And Download.

Mainframe Commands

MESR<N> (Module Event Status Register)

Table 9-8

1660-Series Oscilloscope Module Event Status Enable Register

Bit Position

Bit Weight

Enables

128

not used

Number of averages met

Auto triggered

Trigger received

RNT - Run Until Satisfied

MC - Measurement Complete

MESR<N> (Module Event Status Register)

Query

:MESR<N>?

The MESR query returns the contents of the Module Event Status register.

The <N> index specifies the module. For the 1660 series logic analyzer, the

<N> index 0, 1, or 2 refers to system, logic analyzer, or oscilloscope

respectively.

Refer to table 9-9 for information about the Module Event Status Register

bits and their bit weights for the system, table 9-10 for the logic analyzer, and

table 9-11 for the oscilloscope.

Returned Format

[:MESR<N>] <enable_value><NL>

<N> An integer 0 through 10 (3 through 10 unused).

<enable_value> An integer from 0 through 255

Example

OUTPUT XXX;":MESR1?"

9–16

Download from Www.Somanuals.com. All Manuals Search And Download.

Mainframe Commands

MESR<N> (Module Event Status Register)

Table 9-9

1660-Series Logic Analyzer Mainframe Module Event Status Register

Bit

Bit Weight

Bit Name

Condition

128

0 = not used

RNT

0 = Intermodule Run until not satisfied

1 = Intermodule Run until satisfied

0 = Intermodule Measurement not satisfied

1 = Intermodule Measurement satisfied

Table 9-10

1660-Series Logic Analyzer Module Event Status Register

Bit

Bit Weight

Condition

128

0 = not used

1 = One or more pattern searches failed

0 = Pattern searches did not fail

1 = Trigger found

0 = Trigger not found

0 = Run until not satisfied

1 = Run until satisfied

0 = Measurement not satisfied

1 = Measurement satisfied

9–17

Download from Www.Somanuals.com. All Manuals Search And Download.

Mainframe Commands

RMODe

Table 9-11

1660-Series Oscilloscope Module Event Status Register

Bit

Bit Weight

Bit Name

Condition

128

0 = not used

1 = Number of averages satisfied

0= Number of averages not satisfied

1 = Auto trigger received

0= Auto trigger not received

1= Trigger received

0= Trigger not received

RNT

1 = Run until satisfied

0 = Run until not satisfied

1 = Measurement complete

0 = Measurement not complete

RMODe

Command

:RMODe {SINGle|REPetitive}

The RMODe command specifies the run mode for the selected module (or

Intermodule). If the selected module is in the intermodule configuration,

then the intermodule run mode will be set by this command.

After specifying the run mode, use the STARt command to start the acquisition.

Example

OUTPUT XXX;":RMODE SINGLE"

9–18

Download from Www.Somanuals.com. All Manuals Search And Download.

Mainframe Commands

RTC (Real-time Clock)

Query

:RMODe?

The query returns the current setting.

Returned Format

[:RMODe] {SINGle|REPetitive}<NL>

Example

OUTPUT XXX;":RMODE?"

RTC (Real-time Clock)

Command

:RTC {<day>,<month>,<year>,<hour>,<minute>,

<second>|DEFault}

The real-time clock command allows you to set the real-time clock to the

current date and time. The DEFault option sets the real-time clock to 01

January 1990, 12:00:00 (24-hour format).

<day> integer from 1 to 31

<month> integer from 1 to 12

<year> integer from 1990 to 2089

<hour> integer from 0 to 23

<minute> integer from 0 to 59

<second> integer from 0 to 59

Example

This example sets the real-time clock for 1 January 1992, 20:00:00 (8 PM).

OUTPUT XXX;":RTC 1,1,1992,20,0,0"

9–19

Download from Www.Somanuals.com. All Manuals Search And Download.

Mainframe Commands

SELect

Query

:RTC?

The RTC query returns the real-time clock setting.

Returned Format

[:RTC] <day>,<month>,<year>,<hour>,<minute>,<second>

Example

OUTPUT XXX;":RTC?"

SELect

Command

:SELect <module>

The SELect command selects which module (or system) will have parser

control. SELect defaults to System (0) at power up. The appropriate module

(or system) must be selected before any module (or system) specific

commands can be sent. SELECT 0 selects the System, SELECT 1 selects the

logic analyzer (state and timing), and SELECT 2 selects the oscilloscope

module. Select –2, –1 and, 3 through 10 are accepted but no action will be

taken. When a module is selected, the parser recognizes the module’s

commands and the System/Intermodule commands. When SELECT 0 is

used, only the System/Intermodule commands are recognized by the parser.

Figure 9-2 shows the command tree for the SELect command.

The command parser in the 1660-series logic analyzers is designed to accept

programs written for the 16500A logic analysis system with a 16550A logic

analyzer module; however, if the parameters 3 through 10 are sent, the

1660-series logic analyzer will take no action.

<module> An integer 0 through 2 (–2, –1, and 3 through 10 unused).

Example

OUTPUT XXX;":SELECT 0"

9–20

Download from Www.Somanuals.com. All Manuals Search And Download.

Mainframe Commands

SELect

Query

:SELect?

The SELect? query returns the current module selection.

Returned Format

[:SELect] <module><NL>

Example

OUTPUT XXX;":SELECT?"

Figure 9-2

Not Used

Select Command Tree

9–21

Download from Www.Somanuals.com. All Manuals Search And Download.

Mainframe Commands

SETColor

Command

:SETColor {<color>,<hue>,<sat>,<lum>|DEFault}

The SETColor command is used to change one of the selections on the CRT,

or to return to the default screen colors. Four parameters are sent with the

command to change a color:

Color Number (first parameter)

•

Hue (second parameter)

•

Saturation (third parameter)

•

Luminosity (last parameter)

•

<color> An integer from 1 to 7

<hue> An integer from 0 to 100.

<sat> An integer from 0 to 100.

<lum> An integer from 0 to 100

Color Number 0 cannot be changed.

Example

OUTPUT XXX;":SETCOLOR 3,60,100,60"

OUTPUT XXX;":SETC DEFAULT"

Query

:SETColor? <color>

The SETColor query returns the luminosity values for a specified grey scale.

Returned Format

[:SETColor] <color>,<hue>,<sat>,<lum><NL>

Example

OUTPUT XXX;":SETCOLOR? 3"

9–22

Download from Www.Somanuals.com. All Manuals Search And Download.

Mainframe Commands

STARt

Command

:STARt

The STARt command starts the selected module (or Intermodule) running in

the specified run mode (see RMODe). If the specified module is in the

Intermodule configuration, then the Intermodule run will be started.

The STARt command is an overlapped command. An overlapped command is a

command that allows execution of subsequent commands while the device

operations initiated by the overlapped command are still in progress.

Example

OUTPUT XXX;":START"

9–23

Download from Www.Somanuals.com. All Manuals Search And Download.

Mainframe Commands

STOP

Command

:STOP

The STOP command stops the selected module (or Intermodule). If the

specified module is in the Intermodule configuration, then the Intermodule

run will be stopped.

The STOP command is an overlapped command. An overlapped command is a

command that allows execution of subsequent commands while the device

operations initiated by the overlapped command are still in progress.

Example

OUTPUT XXX;":STOP"

9–24

Download from Www.Somanuals.com. All Manuals Search And Download.

SYSTem Subsystem

Download from Www.Somanuals.com. All Manuals Search And Download.

Introduction

SYSTem subsystem commands control functions that are common to

the entire 1660-Series logic analysis system, including formatting

query responses and enabling reading and writing to the advisory line

of the instrument. The command parser in the 1660-series logic

analyzer is designed to accept programs written for the 16500A logic

analysis system with a 16550A logic analyzer module and a 16532A

oscilloscope module.

Refer to figure 10-1 and table 10-1 for the System Subsystem

commands syntax diagram. The SYSTem Subsystem commands are:

DATA

•

DSP

•

ERRor

•

HEADer

•

LONGform

•

SETup

•

10–2

Download from Www.Somanuals.com. All Manuals Search And Download.

SYSTem Subsystem

Figure 10-1

System Subsystem Commands Syntax Diagram

10–3

Download from Www.Somanuals.com. All Manuals Search And Download.

SYSTem Subsystem

System Subsystem Commands Syntax Diagram (Continued)

SYSTem Parameter Values

Table 10-1

Parameter

Values

block_data

string

Data in IEEE 488.2 format.

A string of up to 68 alphanumeric characters.

10–4

Download from Www.Somanuals.com. All Manuals Search And Download.

SYSTem Subsystem

DATA

Command

:SYSTem:DATA <block_data>

The DATA command allows you to send and receive acquired data to and

from a controller in block form. This helps saving block data for:

Reloading to the logic analyzer or oscilloscope

•

Processing data later in the logic analyzer or oscilloscope

•

Processing data in the controller.

•

The format and length of block data depends on the instruction being used

and the configuration of the instrument. This chapter describes briefly the

syntax of the Data command and query. Because the mainframe by itself

does not have acquired data, and the capabilities of the DATA command and

query vary for each module, the DATA command and query are described in

detail in the respective modules command section. See chapter 26, "DATA

and SETup Commands" for additional information when using the logic

analyzer, or chapter 35, "WAVeform Subsystem" when using the oscilloscope

module.

Example

OUTPUT XXX;":SYSTEM:DATA" <block_data>

<block_data> <block_length_specifier><section>

<block_length_ #8<length>

specifier>

<length> The total length of all sections in byte format (must be represented with 8

digits)

<section_ 16 bytes, described in the "Section Header Description" section in the

header> individual modules command section.

<section_data> The format depends on the type of data

10–5

Download from Www.Somanuals.com. All Manuals Search And Download.

SYSTem Subsystem

DSP (Display)

Query

:SYSTem:DATA?

The SYSTem:DATA query returns the block data. The data sent by the

SYSTem:DATA query reflects the configuration of the machines when the

last run was performed. Any changes made since then through either

front-panel operations or programming commands do not affect the stored

configuration.

Returned Format

[:SYSTem:DATA] <block_data><NL>

Example

See chapter 36, "Programming Examples" for an example on transferring data.

DSP (Display)

Command

:SYSTem:DSP <string>

The DSP command writes the specified quoted string to a device-dependent

portion of the instrument display.

<string> A string of up to 68 alphanumeric characters

Example

OUTPUT XXX;":SYSTEM:DSP ’The message goes here’"

10–6

Download from Www.Somanuals.com. All Manuals Search And Download.

SYSTem Subsystem

ERRor

Query

:SYSTem:ERRor? [NUMeric|STRing]

The ERRor query returns the oldest error from the error queue. The optional

parameter determines whether the error string should be returned along with

the error number. If no parameter is received, or if the parameter is

NUMeric, then only the error number is returned. If the value of the

parameter is STRing, then the error should be returned in the following form:

<error_number>,<error_message (string)>

A complete list of error messages for the 1660A-series logic analyzer is shown

in chapter 7, "Error Messages." If no errors are present in the error queue, a

zero (No Error) is returned.

Returned Formats

Numeric:

[:SYSTem:ERRor] <error_number><NL>

String:

[:SYSTem:ERRor] <error_number>,<error_string><NL>

<error_number> An integer

<error_string> A string of alphanumeric characters

Examples

Numeric:

10 OUTPUT XXX;":SYSTEM:ERROR?"

20 ENTER XXX;Numeric

String:

50 OUTPUT XXX;":SYST:ERR? STRING"

60 ENTER XXX;String$

10–7

Download from Www.Somanuals.com. All Manuals Search And Download.

SYSTem Subsystem

HEADer

Command

:SYSTem:HEADer {{ON|1}|{OFF|0}}

The HEADer command tells the instrument whether or not to output a

header for query responses. When HEADer is set to ON, query responses will

include the command header.

Example

OUTPUT XXX;":SYSTEM:HEADER ON"

Query

:SYSTem:HEADer?

The HEADer query returns the current state of the HEADer command.

Returned Format

[:SYSTem:HEADer] {1|0}<NL>

Example

OUTPUT XXX;":SYSTEM:HEADER?"

Headers should be turned off when returning values to numeric variables.

10–8

Download from Www.Somanuals.com. All Manuals Search And Download.

SYSTem Subsystem

LONGform

Command

:SYSTem:LONGform {{ON|1}|{OFF|0}}

The LONGform command sets the longform variable, which tells the

instrument how to format query responses. If the LONGform command is set

to OFF, command headers and alpha arguments are sent from the instrument

in the abbreviated form. If the the LONGform command is set to ON, the

whole word will be output. This command has no affect on the input data

messages to the instrument. Headers and arguments may be input in either

the longform or shortform regardless of how the LONGform command is set.

Example

OUTPUT XXX;":SYSTEM:LONGFORM ON"

Query

:SYSTem:LONGform?

The query returns the status of the LONGform command.

Returned Format

[:SYSTem:LONGform] {1|0}<NL>

Example

OUTPUT XXX;":SYSTEM:LONGFORM?"

10–9

Download from Www.Somanuals.com. All Manuals Search And Download.

SYSTem Subsystem

Command

:SYSTem:PRINt {ALL|PARTial,<start>,<end>},

DISK,<pathname>

:SYSTem:PRINt SCReen{BTIF|CTIF|PCX|EPS},

DISK,<pathname>

The PRINt command initiates a print of the screen or listing buffer over the

current PRINTER communication interface to the printer or to a file on the

disk. The PRINT SCREEN option allows you to specify a graphics type.

BTIF format is black & white, CTIF and PCX format is color. If a file

extension is not specified, one is appended automatically to the file name.

The PRINT PARTIAL option allows you to specify a START and END state

number.

<pathname> A string of up to 10 alphanumeric characters for LIF in the following form:

NNNNNNNNNN when the file resides in the present working directory, or a

string of up to 64 alphanumeric characters for DOS in the following forms:

NNNNNNNN.NNN or \NAME_DIR|FILENAME when the file does not reside

in the present working directory.

<start>, <end> An integer specifying a state number.

Example

This instuctrion prints the screen to the printer:

OUTPUT XXX;":SYSTEM:PRINT SCREEN"

This instruction prints all, to a file named STATE:

OUTPUT 707;":SYSTEM:PRINT ALL, DISK,’STATE’"

This instruction prints partial data to a file named LIST.

OUTPUT 707;":SYSTEM:PRINT PARTIAL,-9,30, DISK,’list’

Query

:SYSTem:PRINt? {SCReen|ALL}

The PRINt query sends the screen or listing buffer data over the current

CONTROLLER communication interface to the controller.

10–10

Download from Www.Somanuals.com. All Manuals Search And Download.

SYSTem Subsystem

SETup

The print query should NOT be sent with any other command or query on the

same command line. The print query never returns a header. Also, since

response data from a print query may be sent directly to a printer without

modification, the data is not returned in block mode.

Example

OUTPUT 707;":SYSTEM:PRINT? SCREEN"

SETup

Command

:SYStem:SETup <block_data>

The :SYStem:SETup command configures the logic analyzer module as

defined by the block data sent by the controller. This chapter describes

briefly the syntax of the Setup command and query. Because of the

capabilites and importance of the Setup command and query, a complete

chapter is dedicated to it. The dedicated chapter is chapter 26, "DATA and

SETup Commands."

<block_data> <block_length_specifier><section>

<block_length_ #8<length>

specifier>

<length> The total length of all sections in byte format (must be represented with 8

digits)

<section_ 16 bytes, described in the "Section Header Description" section in chapter 26.

header>

<section_data> Format depends on the type of data

10–11

Download from Www.Somanuals.com. All Manuals Search And Download.

SYSTem Subsystem

SETup

The total length of a section is 16 (for the section header) plus the length of

the section data. So when calculating the value for <length>, don’t forget

to include the length of the section headers.

Example

OUTPUT XXX USING "#,K";":SYSTEM:SETUP " <block_data>

Query

:SYStem:SETup?

The SYStem:SETup query returns a block of data that contains the current

configuration to the controller.

Returned Format

[:SYStem:SETup] <block_data><NL>

Example

See "Transferring the logic analyzer configuration" in chapter 27,

"Programming Examples" for an example.

10–12

Download from Www.Somanuals.com. All Manuals Search And Download.

MMEMory Subsystem

Download from Www.Somanuals.com. All Manuals Search And Download.

Introduction

The MMEMory (mass memory) subsystem commands provide access

to disk drive. The 1600-series logic analyzers support both LIF

(Logical Information Format) and DOS (Disk Operating System)

formats.

The 1660-series logic analyzers have only one disk drive; however,

programs written for the 16500A logic analysis system that contain

the MSI (Mass Storage Is) parameter will be accepted but no action is

taken. Refer to figure 11-1 and table 11-1 for the MMEMory

Subsystem commands syntax diagram. The MMEMory subsystem

commands are:

• AUToload

• CATalog

• COPY

• DOWNload

• INITialize

• LOAD

• MSI

• PACK

• PURGe

• REName

• STORe

• UPLoad

• VOLume

11–2

Download from Www.Somanuals.com. All Manuals Search And Download.

MMEMory Subsystem

<msus> refers to the mass storage unit specifier; however, it is not needed for

the 1660-series logic analyzers since they have only one drive. The <msus>

parameter is shown in the command syntax examples as a reminder that for the

the 16500A logic analysis system can be used on the 1660-series logic analyzers.

If you are not going to store information to the configuration disk, or if the disk

you are using contains information you need, it is advisable to write protect

your disk. This will protect the contents of the disk from accidental damage due

to incorrect commands being mistakenly sent.

11–3

Download from Www.Somanuals.com. All Manuals Search And Download.

MMEMory Subsystem

Figure 11-1

Mmemory Subsystem Commands Syntax Diagram

11–4

Download from Www.Somanuals.com. All Manuals Search And Download.

MMEMory Subsystem

Figure 11-1

Mmemory Subsystem Commands Syntax Diagram (Continued)

11–5

Download from Www.Somanuals.com. All Manuals Search And Download.

MMEMory Subsystem

Figure 11-1

Mmemory Subsystem Commands Syntax Diagram (Continued)

11–6

Download from Www.Somanuals.com. All Manuals Search And Download.

MMEMory Subsystem

Table 11-1

MMEMory Parameter Values

Values

Parameter

auto_file

A string of up to 10 alphanumeric characters for LIF in the

following form: "NNNNNNNNNN"

A string of up to 12 alphanumeric characters for DOS in the

following form: "NNNNNNNN.NNN"

msus

name

Mass Storage Unit specifier (not needed by 1660-series.

16500A <msus>is accepted but no action is taken).

A string of up to 10 alphanumeric characters for LIF in the

following form: "NNNNNNNNNN"

A string of up to 12 alphanumeric characters for DOS in the

following form: "NNNNNNNN.NNN"

description

type

A string of up to 32 alphanumeric characters.

An integer, refer to table 11-2.

block_data

ia_name

Data in IEEE 488.2 format.

A string of up to 10 alphanumeric characters for LIF in the

following form: "NNNNNNNNNN"

A string of up to 12 alphanumeric characters for DOS in the

following form: "NNNNNNNN.NNN"

new_name

module

A string of up to 10 alphanumeric characters for LIF in the

following form: "NNNNNNNNNN"

A string of up to 12 alphanumeric characters for DOS in the

following form: "NNNNNNNN.NNN"

An integer, 0 through 2.

11–7

Download from Www.Somanuals.com. All Manuals Search And Download.

MMEMory Subsystem

AUToload

Command

:MMEMory:AUToload {{OFF|0}|{<auto_file>}}[,<msus>]

The AUToload command controls the autoload feature which designates a set

of configuration files to be loaded automatically the next time the instrument

is turned on. The OFF parameter (or 0) disables the autoload feature. A

string parameter may be specified instead to represent the desired autoload

file. If the file is on the current disk, the autoload feature is enabled to the

specified file.

<auto_file> A string of up to 10 alphanumeric characters for LIF in the following form:

NNNNNNNNNN

A string of up to 12 alphanumeric characters for DOS in the following form:

NNNNNNNN.NNN

<msus> Mass Storage Unit Specifier (not needed by 1660-series. 16500A <msus> is

accepted but no action is taken).

Examples

OUTPUT XXX;":MMEMORY:AUTOLOAD OFF"

OUTPUT XXX;":MMEMORY:AUTOLOAD ’FILE1_A’"

OUTPUT XXX;":MMEMORY:AUTOLOAD ’FILE2 ’,INTERNAL0"

Query

:MMEMory:AUToload?

The AUToload query returns 0 if the autoload feature is disabled. If the

autoload feature is enabled, the query returns a string parameter that

specifies the current autoload file. The appropriate slot designator is

included in the filename and refers to the slot designator A for the logic

analyzer or B for the oscilloscope. If the slot designator is _ (underscore)

the file is for the system.

Returned Format

[:MMEMory:AUToload] {0|<auto_file>},<msus><NL>

11–8

Download from Www.Somanuals.com. All Manuals Search And Download.

MMEMory Subsystem

CATalog

<auto_file> A string of up to 10 alphanumeric characters for LIF in the following form:

NNNNNNNNNN

A string of up to 12 alphanumeric characters for DOS in the following form:

NNNNNNNN.NNN

Example

OUTPUT XXX;":MMEMORY:AUTOLOAD?"

CATalog

Query

:MMEMory:CATalog? [[All,][<msus>]]

The CATalog query returns the directory of the disk in one of two block data

formats. The directory consists of a 51 character string for each file on the

disk when the ALLoption is not used. Each file entry is formatted as follows:

"NNNNNNNNNN TTTTTTT FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF"

where N is the filename, T is the file type (see table 11-2), and F is the file

description.

The optional parameter ALL returns the directory of the disk in a

70-character string as follows:

"NNNNNNNNNNNN TTTTTTT FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF

DDMMMYY HH:MM:SS"

where N is the filename, T is the file type (see table 11-2), F is the file

description, and, D, M, Y, and HH:MM:SS are the date, month, year, and time

respectively in 24-hour format.

The <msus>is not needed by 1660-series; however, the 16500A <msus> is

accepted but no action is taken.

11–9

Download from Www.Somanuals.com. All Manuals Search And Download.

MMEMory Subsystem

COPY

<msus> Mass Storage Unit Specifier (not needed by 1660-series. 16500A <msus> is

accepted but no action is taken).

Returned Format

[:MMEMory:CATalog] <block_data>

<block_data> ASCII block containing <filename> <file_type>

<file_description>

Example 1

This example is for sending the CATALOG? ALLquery:

OUTPUT 707;":MMEMORY:CATALOG? ALL"

Example 2

This example is for sending the CATALOG? query without the ALL option.

Keep in mind if you do not use the ALLoption with a DOS disk, each

filename entry will be truncated at 51 characters:

OUTPUT 707;":MMEMORY:CATALOG?"

COPY

Command

:MMEMory:COPY <name>[,<msus>],<new_name>[,<msus>]

The COPY command copies one file to a new file or an entire disk’s contents

to another disk. The two <name>parameters are the filenames. The first

pair of parameters specifies the source file. The second pair specifies the

destination file. An error is generated if the source file doesn’t exist, or if the

destination file already exists.

The <msus>is not needed by 1660-series. 16500A <msus> is accepted but

no action is taken.

11–10

Download from Www.Somanuals.com. All Manuals Search And Download.

MMEMory Subsystem

DOWNload

<name> A string of up to 10 alphanumeric characters for LIF in the following form:

NNNNNNNNNN

A string of up to 12 alphanumeric characters for DOS in the following form:

NNNNNNNN.NNN

<new_name> A string of up to 10 alphanumeric characters for LIF in the following form:

NNNNNNNNNN

A string of up to 12 alphanumeric characters for DOS in the following form:

NNNNNNNN.NNN

<msus> Mass Storage Unit Specifier (not needed by 1660-series. 16500A <msus>is

accepted but no action is taken).

Examples

To copy the contents of "FILE1" to "FILE2:

OUTPUT XXX;":MMEMORY:COPY ’FILE1’,’FILE2’"

DOWNload

Command

:MMEMory:DOWNload <name>[,<msus>],<description>,

The DOWNload command downloads a file to the mass storage device. The

<name>parameter specifies the filename, the <description>parameter

specifies the file descriptor, and the <block_data>contains the contents

of the file to be downloaded.

The <msus>is not needed by 1660-series. 16500A <msus> is accepted but

no action is taken.

Table 11-2 lists the file types for the <type>parameter.

11–11

Download from Www.Somanuals.com. All Manuals Search And Download.

MMEMory Subsystem

DOWNload

<name> A string of up to 10 alphanumeric characters for LIF in the following form:

NNNNNNNNNN

A string of up to 12 alphanumeric characters for DOS in the following form:

NNNNNNNN.NNN

<msus> Mass Storage Unit Specifier (not needed by 1660-series. 16500A <msus>is

accepted but no action is taken).

<description> A string of up to 32 alphanumeric characters

<type> An integer (see table 11-2)

<block_data> Contents of file in block data format

Example

OUTPUT XXX;":MMEMORY:DOWNLOAD ’SETUP ’,INTERNAL0,’FILE CREATED FROM SETUP

QUERY’,-16127,#800000643..."

Table 11-2

File Types

File

File Type

1660-Series System Software

–15608

–15609

–15605

–16095

–15607

–16115

–15606

–15615

–15614

–5813

1660-Series ROM Software

1660-Series System Configuration

1660-Series Logic Analyzer Configuration

1660-Series Logic Analyzer Software

1660-Series Logic Analyzer with Oscilloscope Configuration

1660-Series Oscilloscope Software

Autoload File

Inverse Assembler

Text Type (LIF from Print to Disk)

11–12

Download from Www.Somanuals.com. All Manuals Search And Download.

MMEMory Subsystem

INITialize

Command

:MMEMory:INITialize [{LIF|DOS}[,<msus>]]

The INITialize command formats the disk in either LIF (Logical Information

Format) or DOS (Disk Operating System). The <msus> is not needed by

1660-series. 16500A <msus> is accepted but no action is taken. If no

format is specified, then the initialize command will format the disk in the LIF

format.

<msus> Mass Storage Unit Specifier (not needed by 1660-series. 16500A <msus>is

accepted but no action is taken).

Examples

OUTPUT XXX;":MMEMORY:INITIALIZE DOS"

OUTPUT XXX;":MMEMORY:INITIALIZE LIF,INTERNAL0"

Once executed, the initialize command formats the specified disk, permanently

erasing all existing information from the disk. After that, there is no way to

retrieve the original information.

11–13

Download from Www.Somanuals.com. All Manuals Search And Download.

MMEMory Subsystem

LOAD [:CONFig]

Command

:MMEMory:LOAD[:CONfig] <name>[,<msus>][,<module>]

The LOAD command loads a configuration file from the disk into the logic

analyzer, oscilloscope, software options, or the system. The <name>

parameter specifies the filename from the disk. The optional <module>

parameter specifies which module(s) to load the file into. The accepted

values are 0 for system, 1 for logic analyzer, and 2 for the oscilloscope. Not

specifying the <module>parameter is equivalent to performing a ’LOAD

ALL’ from the front panel which loads the appropriate file for the system,

logic analyzer, oscilloscope, and any software option.

<name> A string of up to 10 alphanumeric characters for LIF in the following form:

NNNNNNNNNN

A string of up to 12 alphanumeric characters for DOS in the following form:

NNNNNNNN.NNN

<msus> Mass Storage Unit Specifier (not needed by 1660-series. 16500A <msus>is

accepted but no action is taken).

<module> An integer, 0 through 2

Examples

OUTPUT XXX;":MMEMORY:LOAD:CONFIG ’FILE ’"

OUTPUT XXX;":MMEMORY:LOAD ’FILE ’,0"

OUTPUT XXX;":MMEM:LOAD:CONFIG ’FILE A’,INTERNAL0,1"

11–14

Download from Www.Somanuals.com. All Manuals Search And Download.

MMEMory Subsystem

LOAD :IASSembler

Command

:MMEMory:LOAD:IASSembler <IA_name>[,<msus>],{1|2}

[,<module>]

This variation of the LOAD command allows inverse assembler files to be

loaded into a module that performs state analysis. The <IA_name>

parameter specifies the inverse assembler filename from the desired

<msus>. The parameter after the optional <msus> specifies which machine

to load the inverse assembler into.

The optional <module>parameter is used to specify which slot the state

analyzer in. 1 refers to the logic analyzer. If this parameter is not specified,

the state analyzer will be selected.

<IA_name> A string of up to 10 alphanumeric characters for LIF in the following form:

NNNNNNNNNN

A string of up to 12 alphanumeric characters for DOS in the following form:

NNNNNNNN.NNN

<msus> Mass Storage Unit Specifier (not needed by 1660-series. 16500A <msus>is

accepted but no action is taken).

<module> An integer, always 1

Examples

OUTPUT XXX;":MMEMORY:LOAD:IASSEMBLER ’I68020 IP’,1"

OUTPUT XXX;":MMEM:LOAD:IASS ’I68020 IP’,INTERNAL0,1,2"

11–15

Download from Www.Somanuals.com. All Manuals Search And Download.

MMEMory Subsystem

MSI (Mass Storage Is)

Command

:MMEMory:MSI [<msus>]

The MSI command selects a default mass storage device; however, it is not

needed by 1660-series logic analyzers because they have only one disk drive.

If the 16500A <msus>is sent to the 1660-series logic analyzer, it is accepted

but no action is taken.

<msus> Mass Storage Unit Specifier (not needed by 1660-series. 16500A <msus>is

accepted but no action is taken).

Examples

OUTPUT XXX;":MMEMORY:MSI"

OUTPUT XXX;":MMEM:MSI INTERNAL0"

Query

:MMEMory:MSI?

The MSI? query returns the current MSI setting. Because the 1660-series

logic analyzers have only one disk drive, Internal0is always returned.

Returned Format

[:MMEMory:MSI] <msus><NL>

Example

OUTPUT XXX;":MMEMORY:MSI?"

11–16

Download from Www.Somanuals.com. All Manuals Search And Download.

MMEMory Subsystem

PACK

Command

:MMEMory:PACK [<msus>]

The PACK command packs the files on the LIF disk the disk in the drive. If a

DOS disk is in the drive when the PACK command is sent, no action is taken.

<msus> Mass Storage Unit Specifier (not needed by 1660-series. 16500A <msus>is

accepted but no action is taken).

Examples

OUTPUT XXX;":MMEMORY:PACK"

OUTPUT XXX;":MMEM:PACK INTERNAL0"

PURGe

Command

:MMEMory:PURGe <name>[,<msus>]

The PURGe command deletes a file from the disk in the drive. The <name>

parameter specifies the filename to be deleted.

<name> A string of up to 10 alphanumeric characters for LIF in the following form:

NNNNNNNNNN

A string of up to 12 alphanumeric characters for DOS in the following form:

NNNNNNNN.NNN

<msus> Mass Storage Unit Specifier (not needed by 1660-series. 16500A <msus>is

accepted but no action is taken).

11–17

Download from Www.Somanuals.com. All Manuals Search And Download.

MMEMory Subsystem

REName

Examples

OUTPUT XXX;":MMEMORY:PURGE ’FILE1’"

OUTPUT XXX;":MMEM:PURG ’FILE1’,INTERNAL0"

Once executed, the purge command permanently erases all the existing

information about the specified file. After that, there is no way to retrieve the

original information.

REName

Command

:MMEMory:REName <name>[,<msus>],<new_name>

The REName command renames a file on the disk in the drive. The <name>

parameter specifies the filename to be changed and the <new_name>

parameter specifies the new filename.

You cannot rename a file to an already existing filename.

<name> A string of up to 10 alphanumeric characters for LIF in the following form:

NNNNNNNNNN

A string of up to 12 alphanumeric characters for DOS in the following form:

NNNNNNNN.NNN

<msus> Mass Storage Unit Specifier (not needed by 1660-series. 16500A <msus>is

accepted but no action is taken).

<new name> A string of up to 10 alphanumeric characters for LIF in the following form:

NNNNNNNNNN

A string of up to 12 alphanumeric characters for DOS in the following form:

NNNNNNNN.NNN

11–18

Download from Www.Somanuals.com. All Manuals Search And Download.

MMEMory Subsystem

STORe [:CONFig]

Examples

OUTPUT XXX;":MMEMORY:RENAME ’OLDFILE’,’NEWFILE’"

OUTPUT XXX;":MMEM:REN ’OLDFILE’[,INTERNAL1],’NEWFILE’"

STORe [:CONFig]

Command

:MMEMory:STORe [:CONfig]<name>[,<msus>],

<description>[,<module>]

The STORe command stores module or system configurations onto a disk.

The [:CONFig] specifier is optional and has no effect on the command. The

<name>parameter specifies the file on the disk. The <description>

parameter describes the contents of the file. The optional <module>

parameter allows you to store the configuration for either the system, the

logic analyzer, or the oscilloscope. 2 refers to the oscilloscope, 1 refers to the

logic analyzer, and 0 refers to the system.

If the optional <module>parameter is not specified, the configurations for

the system, logic analyzer, and oscilloscope are stored.

<name> A string of up to 10 alphanumeric characters for LIF in the following form:

NNNNNNNNNN

A string of up to 12 alphanumeric characters for DOS in the following form:

NNNNNNNN.NNN

<msus> Mass Storage Unit Specifier (not needed by 1660-series. 16500A <msus>is

accepted but no action is taken).

<description> A string of up to 32 alphanumeric characters

<module> An integer, 0 through 2

11–19

Download from Www.Somanuals.com. All Manuals Search And Download.

MMEMory Subsystem

UPLoad

Examples

OUTPUT XXX;":MMEM:STOR ’DEFAULTS’,’SETUPS FOR ALL MODULES’"

OUTPUT XXX;":MMEMORY:STORE:CONFIG ’STATEDATA’,INTERNAL0,

’ANALYZER 1 CONFIG’,1"

The appropriate module designator "_X" is added to all files when they are

stored. "X" refers to either an __ (double underscore) for the system or an _A

for the logic analyzer.

UPLoad

Query

:MMEMory:UPLoad? <name>[,<msus>]

The UPLoad query uploads a file. The <name>parameter specifies the file to

be uploaded from the disk. The contents of the file are sent out of the

instrument in block data form.

This command should only be used for 16550A or 1660-series configuration files.

<name> A string of up to 10 alphanumeric characters for LIF in the following form:

NNNNNNNNNN

A string of up to 12 alphanumeric characters for DOS in the following form:

NNNNNNNN.NNN

<msus> Mass Storage Unit Specifier (not needed by 1660-series. 16500A <msus>is

accepted but no action is taken).

Returned Format

[:MMEMory:UPLoad] <block_data><NL>

11–20

Download from Www.Somanuals.com. All Manuals Search And Download.

MMEMory Subsystem

VOLume

Example

10 DIM Block$[32000]

20 DIM Specifier$[2]

30 OUTPUT XXX;":EOI ON"

!allocate enough memory for block data

40 OUTPUT XXX;":SYSTEM HEAD OFF"

50 OUTPUT XXX;":MMEMORY:UPLOAD? ’FILE1’"

60 ENTER XXX USING "#,2A";Specifier$

!send upload query

!read in #8

70 ENTER XXX USING "#,8D";Length !read in block length

80 ENTER XXX USING "-K";Block$

90 END

!read in file

VOLume

Query

:MMEMory:VOLume? [<msus>]

TheVOLume query returns the volume type of the disk. The volume types

are DOS or LIF. Question marks (???) are returned if there is no disk, if the

disk is not formatted, or if a disk has a format other than DOS or LIF.

<msus> Mass Storage Unit Specifier (not needed by 1660-series. 16500A <msus>is

accepted but no action is taken).

Returned Format

[:MMEMory:VOLume]{DOS|LIF|???}<NL>

OUTPUT XXX;":MMEMORY:VOLUME?"

Example

11–21

Download from Www.Somanuals.com. All Manuals Search And Download.

11–22

Download from Www.Somanuals.com. All Manuals Search And Download.

INTermodule Subsystem

Download from Www.Somanuals.com. All Manuals Search And Download.

Introduction

The INTermodule subsystem commands specify intermodule arming

from the rear-panel input BNC (ARMIN) or to the rear-panel output

BNC (ARMOUT). Refer to figure 12-1 and table 12-1 for the

INTermodule Subsystem commands syntax diagram. The

INTermodule commands are:

• DELete

• HTIMe

• INPort

• INSert

• SKEW

• TREE

• TTIMe

12–2

Download from Www.Somanuals.com. All Manuals Search And Download.

INTermodule Subsystem

Figure 12-1

Intermodule Subsystem Commands Syntax Diagram

12–3

Download from Www.Somanuals.com. All Manuals Search And Download.

INTermodule Subsystem

Figure 12-1

Intermodule Subsystem Commands Syntax Diagram (Continued)

12–4

Download from Www.Somanuals.com. All Manuals Search And Download.

INTermodule Subsystem

:INTermodule

Table 12-1

INTermodule Parameter Values

Parameter

Value

module

index

An integer, 1 to 10 (3 through 10 unused)

A numeric, – 1.0 to 1.0 in seconds.

setting

:INTermodule

Selector

:INTermodule

The INTermodule selector specifies INTermodule as the subsystem the

commands or queries following will refer to. Because the INTermodule

command is a root level command, it will normally appear as the first element

of a compound header.

Example

OUTPUT XXX;":INTERMODULE:HTIME?"

DELete

Command

:DELete {ALL|OUT|<module>}

The DELete command is used to delete a module, PORT OUT, or an entire

intermodule tree. The <module>parameter sent with the delete command

refers to the slot location of the module. The logic analyzer is slot 1 and the

oscilloscope is slot 2.

<module> An integer, 1 through 10 (3 through 10 unused)

Example

OUTPUT XXX;":INTERMODULE:DELETE ALL"

OUTPUT XXX;":INTERMODULE:DELETE 1"

12–5

Download from Www.Somanuals.com. All Manuals Search And Download.

INTermodule Subsystem

HTIMe

Query

:HTIMe?

The HTIMe query returns a value representing the internal hardware skew in

the Intermodule configuration. If there is no internal skew, or if intermodule

bus is not configured, 9.9E37 is returned.

The internal hardware skew is only a display adjustment for time-correlated

waveforms. The value returned is the average propagation delay of the trigger

lines through the intermodule bus circuitry. The value is for reference only

because the value returned by TTIMe includes the internal hardware skew

represented by HTIMe.

Returned Format

[:INTermodule:HTIMe]

<value_1>,<value_2>,<value_3>,<value_4>,<value_5><NL>

<value_1> Skew for logic analyzer (real number)

<value_2> Skew for oscilloscope (real number)

Example

OUTPUT XXX;":INTERMODULE:HTIME?"

INPort

Command

:INPort {{ON|1}|{OFF|0}}

The INPort command causes intermodule acquisitions to be armed from the

Input port.

Example

OUTPUT XXX;":INTERMODULE:INPORT ON"

12–6

Download from Www.Somanuals.com. All Manuals Search And Download.

INTermodule Subsystem

INSert

Query

:INPort?

The INPort query returns the current setting.

Returned Format

[:INTermodule:INPort] {1|0}<NL>

Example

OUTPUT XXX;":INTERMODULE:INPORT?"

INSert

Command

:INSert {<module>|OUT},{GROUP|<module>}

The INSert command adds PORT OUT to the Intermodule configuration. The

first parameter selects the logic analyzer or PORT OUT to be added to the

intermodule configuration, and the second parameter tells the instrument

where the logic analyzer or PORT OUT will be located. A "1" corresponds to

the slot location of the logic analyzer, and a "2" corresponds to the slot

location of the oscilloscope.

<module> An integer, 1 through 10 (3 through 10 unused)

Examples

OUTPUT XXX;":INTERMODULE:INSERT 1,GROUP"

OUTPUT XXX;":INTERMODULE:INSERT 2,GROUP"

OUTPUT XXX;":INTERMODULE:INSERT OUT,2"

12–7

Download from Www.Somanuals.com. All Manuals Search And Download.

INTermodule Subsystem

SKEW<N>

Command

:SKEW<N> <setting>

The SKEW command sets the skew value for a module. The <N> index value

is the module number (1 corresponds to the logic analyzer, 2 corresponds to

the oscilloscope, and 3 through 10 unused). The <setting> parameter is the

skew setting (– 1.0 to 1.0) in seconds.

<N> An integer, 1 through 10 (3 through 10 unused)

<setting> A real number from –1.0 to 1.0 seconds

Example

OUTPUT XXX;":INTERMODULE:SKEW1 3.0E-9"

Query

:SKEW<N>?

The query returns the user defined skew setting.

Returned Format

[INTermodule:SKEW<N>] <setting><NL>

Example

OUTPUT XXX;":INTERMODULE:SKEW1?"

12–8

Download from Www.Somanuals.com. All Manuals Search And Download.

INTermodule Subsystem

TREE

Command

:TREE <module>,<module>

The TREE command allows an intermodule setup to be specified in one

command. The first parameter is the intermodule arm value for module A

(logic analyzer). The second parameter corresponds to the intermodule arm

value for PORT OUT. A –1 means the module is not in the intermodule tree,

a 0 value means the module is armed from the Intermodule run button

(Group run), and a positive value indicates the module is being armed by

another module with the slot location 1 to 10. A 1 corresponds to the slot

location of the module A (logic analyzer, 2 corresponds to the slot location of

the module B (oscilloscope) and 3 through 10 are unused.

An integer, −1 through 10 (3 through 10 unused)

Example

OUTPUT XXX;":INTERMODULE:TREE 0,-1,-1,-1,1"

Query

:TREE?

The TREE? query returns a string that represents the intermodule tree. A −1

means the module is not in the intermodule tree, a 0 value means the module

is armed from the Intermodule run button (Group run), and a positive value

indicates the module is being armed by another module with the slot location

1 to 10. A 1 corresponds to the slot location of the module A (logic analyzer)

and 2 through 10 are unused.

Returned Format

[INTermodule:TREE]

<module_1>,<module_2>,<module_3>,<module_4>,<module_5><NL>

Example

OUTPUT XXX;":INTERMODULE:TREE?"

12–9

Download from Www.Somanuals.com. All Manuals Search And Download.

INTermodule Subsystem

TTIMe

Query

:TTIMe?

The TTIMe query returns values representing the absolute intermodule

trigger time for all of the modules in the Intermodule configuration. The first

value is the trigger time for the module in slot A, the second value is for the

module in slot B, the third value is for slot C, etc.

The value 9.9E37 is returned when:

The module in the corresponding slot is not time correlated; or

•

A time correlatable module did not trigger.

•

The trigger times returned by this command have already been offset by the

INTermodule:SKEW values and internal hardware skews (INTermodule:HTIMe).

Returned Format

[:INTermodule:TTIMe]

<value_1>,<value_2>,<value_3>,<value_4>,<value_5><NL>

<value_1> Trigger time for module in slot A (real number)

<value_2> Trigger time for module in slot B (real number)

<value_3> Trigger time for module in slot C (real number)

NOT USED

<value_10) Trigger time for module in slot J (real number)

Example

OUTPUT XXX;":INTERMODULE:TTIME?"

12–10

Download from Www.Somanuals.com. All Manuals Search And Download.

Part 3

Logic Analyzer Commands

Download from Www.Somanuals.com. All Manuals Search And Download.

MACHine Subsystem

Download from Www.Somanuals.com. All Manuals Search And Download.

Introduction

The MACHine subsystem contains the commands that control the

machine level of operation of the logic analyzer. The functions of

three of these commands reside in the State/Timing Configuration

menu. These commands are:

• ASSign

• NAME

• TYPE

Even though the functions of the following commands reside in the

Trace menu they are at the machine level of the command tree and

are therefore located in the MACHine subsystem. These commands

are:

• ARM

• LEVelarm

• REName

• RESource

13–2

Download from Www.Somanuals.com. All Manuals Search And Download.

MACHine Subsystem

Figure 13-1

Machine Subsystem Syntax Diagram

13–3

Download from Www.Somanuals.com. All Manuals Search And Download.

MACHine Subsystem

MACHine

Table 13-1

Machine Parameter Values

Parameter

Values

arm_source

pod_list

{RUN|INTermodule|MACHine{1|2}}

{NONE|<pod num>[,<pod num>]...}

{1|2|3|4|5|6|7|8}

pod_num

arm_level

machine_name

res_id

An integer from 1 to 11 representing sequence level

A string of up to 10 alphanumeric characters

<state_terms>for state analyzer or

{<state_terms>|GLEDge{1|2}} for timing analyzer

new_text

A string of up to 8 alphanumeric characters

state_terms

res_terms

{A|B|C|D|E|F|G|H|I|J|RANGE{1|2}|TIMER{1|2}}

{<res id>[,<res id>]...}

MACHine

Selector

:MACHine<N>

The MACHine <N> selector specifies which of the two analyzers (machines)

available in the 1660-series logic analyzer the commands or queries following

will refer to. Because the MACHine<N> command is a root level command, it

will normally appear as the first element of a compound header.

<N> {1|2}(the machine number)

Example

OUTPUT XXX; ":MACHINE1:NAME ’TIMING’"

13–4

Download from Www.Somanuals.com. All Manuals Search And Download.

MACHine Subsystem

ARM

Command

:MACHine{1|2}:ARM <arm_source>

The ARM command specifies the arming source of the specified analyzer

(machine). The RUN option disables the arm source. For example, if you do

not want to use either the intermodule bus or the other machine to arm the

current machine, you specify the RUN option.

<arm_source> {RUN|INTermodule|MACHine{1|2}}

Example

OUTPUT XXX;":MACHINE1:ARM MACHINE2"

Query

:MACHine{1|2}:ARM?

The ARM query returns the source that the current analyzer (machine) wil

be armed by.

Returned Format

[:MACHine{1|2}:ARM] <arm_source>

Example

OUTPUT XXX;":MACHINE:ARM?"

ASSign

Command

:MACHine{1|2}:ASSign <pod_list>

The ASSign command assigns pods to a particular analyzer (machine). The

ASSign command will assign two pods for each pod number you specify

because pods must be assigned to analyzers in pairs.

<pod_list> {NONE|<pod >#[, <pod >#]...}

<pod># {1|2|3|4|5|6|7|8}

13–5

Download from Www.Somanuals.com. All Manuals Search And Download.

MACHine Subsystem

LEVelarm

Example

OUTPUT XXX;":MACHINE1:ASSIGN 5, 2, 1"

Query

:MACHine{1|2}:ASSign?

The ASSign query returns which pods are assigned to the current analyzer

(machine).

Returned Format

[:MACHine{1|2}:ASSign] <pod_list><NL>

<pod_list> {NONE|<pod >#[, <pod >#]...}

<pod># {1|2|3|4|5|6|7|8}

Example

OUTPUT XXX;":MACHINE1:ASSIGN?"

LEVelarm

Command

:MACHine{1|2}:LEVelarm <arm_level>

The LEVelarm command allows you to specify the sequence level for a

specified machine that will be armed by the Intermodule Bus or the other

machine. This command is only valid if the specified machine is on and the

arming source is not set to RUN with the ARM command.

<arm_level> An integer from 1 to the maximum number of levels specified in the

appropriate trigger menu.

Example

OUTPUT XXX;":MACHINE1:LEVELARM 2"

Query

:MACHine{1|2}:LEVelarm?

The LEVelarm query returns the current sequence level receiving the arming

for a specified machine.

13–6

Download from Www.Somanuals.com. All Manuals Search And Download.

MACHine Subsystem

NAME

Returned Format:

[:MACHine{1|2}:LEVelarm] <arm_level><NL>

<arm_level> An integer from 1 to 11 representing sequence level

Example

OUTPUT XXX;":MACHINE1:LEVELARM?"

NAME

Command

:MACHine{1|2}:NAME <machine_name>

The NAME command allows you to assign a name of up to 10 characters to a

particular analyzer (machine) for easier identification.

<machine_name> A string of up to 10 alphanumeric characters

Example

OUTPUT XXX;":MACHINE1:NAME ’DRAMTEST’"

Query

:MACHine{1|2}:NAME?

The NAME query returns the current analyzer name as an ASCII string.

Returned Format

[:MACHine{1|2}:NAME] <machine_name><NL>

<machine_name> A string of up to 10 alphanumeric characters

Example

OUTPUT XXX;":MACHINE1:NAME?"

13–7

Download from Www.Somanuals.com. All Manuals Search And Download.

MACHine Subsystem

REName

Command

:MACHine{1|2}:REName {<res_id>, <new_text> |

DEFault}

The REName command allows you to assign a specific name of up to eight

characters to terms A through J, Range 1 and 2, and Timer 1 and 2 in the

state analyzer. In the timing analyzer, GLEDge (glitch/edge) 1 and 2 can be

renamed in addition to the terms available in the state analyzer. The

DEFault option sets all resource term names to the default names assigned

when turning on the instrument.

<res_id> <state_terms>for state analyzer

{<state_terms>|GLEDge{1|2}} for timing analyzer

<new_text> A string of up to 8 alphanumeric characters

Example

OUTPUT XXX;":MACHINE1:RENAME A,’DATA’"

Query

:MACHine{1|2}:RENAME? <res_id>

The REName query returns the current names for specified terms assigned

to the specified analyzer.

Returned Format

[:MACHine{1|2}:RENAME] <res_id>,<new_text><NL>

<res_id> <state_terms>for state analyzer

{<state_terms>|GLEDge{1|2}} for timing analyzer

<new_text> A string of up to 8 alphanumeric characters

Example

OUTPUT XXX;":MACHINE1:RENAME? D"

13–8

Download from Www.Somanuals.com. All Manuals Search And Download.

MACHine Subsystem

RESource

Command

:MACHine{1|2}:RESource <res_terms>

The RESource command allows you to assign resource terms A through J,

Range 1 and 2, and Timer 1 and 2 to a particular analyzer (machine 1 or 2).

In the timing analyzer only, two additional resource terms are available. These

terms are GLEDge (Glitch/Edge) 1 and 2. These terms will always be assigned to

the the machine that is configured as the timing analyzer.

<res_terms> {A|B|C|D|E|F|G|H|I|J|TIMer1|TIMer2|RANGe1|RANGe2}

Example

OUTPUT XXX;":MACHINE1:RESOURCE A,C,RANGE1"

Query

:MACHine{1|2}:RESOURCE?

The RESource query returns the current resource terms assigned to the

specified analyzer.

Returned Format

[:MACHine{1|2}:RESOURCE] <res_terms>[,<res_terms>,...]<NL>

<res_terms> {A|B|C|D|E|F|G|H|I|J|TIMer1|TIMer2|RANGe1|RANGe2}

Example

OUTPUT XXX;":MACHINE1:RESOURCE?"

13–9

Download from Www.Somanuals.com. All Manuals Search And Download.

MACHine Subsystem

TYPE

Command

:MACHine{1|2}:TYPE <analyzer_type>

The TYPE command specifies what type a specified analyzer (machine) will

be. The analyzer types are state or timing. The TYPE command also allows

you to turn off a particular machine.

Only one timing analyzer can be specified at a time.

<analyzer_type> {OFF|STATe|TIMing}

Example

OUTPUT XXX;":MACHINE1:TYPE STATE"

Query

:MACHine{1|2}:TYPE?

The TYPE query returns the current analyzer type for the specified analyzer.

Returned Format

[:MACHine{1|2}:TYPE] <analyzer_type><NL>

<analyzer_type> {OFF|STATe|TIMing}

Example

OUTPUT XXX;":MACHINE1:TYPE?"

13–10

Download from Www.Somanuals.com. All Manuals Search And Download.

WLISt Subsystem

Download from Www.Somanuals.com. All Manuals Search And Download.

Introduction

The WLISt subsystem contains the commands available for the

Timing/State mixed mode display. The X and O markers can only be

placed on the waveforms in the waveform portion of the Timing/State

mixed mode display. The XSTate and OSTate queries return what

states the X and O markers are on. Because the markers can only be

placed on the timing waveforms, the queries return what state (state

acquisition memory location) the marked pattern is stored in.

In order to have mixed mode, one machine must be a state analyzer with time

tagging on (use MACHine<N>:STRigger:TAG TIME).

The WLISt subsystem commands are:

• DELay

• INSert

• LINE

• OSTate

• OTIMe

• RANGe

• REMove

• XOTime

• XSTate

• XTIMe

14–2

Download from Www.Somanuals.com. All Manuals Search And Download.

WLISt Subsystem

Figure 14-1

WLISt Subsystem Syntax Diagram

14–3

Download from Www.Somanuals.com. All Manuals Search And Download.

WLISt Subsystem

WLISt

Table 14-1

WLISt Parameter Values

Parameter

Value

delay_value

module_spec

Real number between −2500 s and +2500 s

{1|2|3|4|5|6|7|8|9|10}(slot where timing card is

installed, 2 through 10 unused)

bit_id

An integer from 0 to 31

label_name

String of up to 6 alphanumeric characters

line_num_mid_screen

An integer from −8191 to +8191

String containing <acquisition spec>{1|2}

Real number

waveform

time_value

time_range

Real number between 10 ns and 10 ks

WLISt

Selector

:WLISt

The WLISt (Waveforms/LISting) selector is used as a part of a compound

header to access the settings normally found in the Mixed Mode menu.

Because the WLISt command is a root level command, it will always appear

as the first element of a compound header.

The WLISt subsystem is only available when one or more state analyzers, with

time tagging on, are specified.

Example

OUTPUT XXX;":WLIST:XTIME 40.0E−6"

14–4

Download from Www.Somanuals.com. All Manuals Search And Download.

WLISt Subsystem

DELay

Command

:MACHine{1|2}:WLISt:DELay <delay_value>

The DELay command specifies the amount of time between the timing

trigger and the horizontal center of the the timing waveform display. The

allowable values for delay are −2500 s to +2500 s.

<delay_value>

Real number between −2500 s and +2500 s

Example

OUTPUT XXX;":MACHINE1:WLIST:DELAY 100E−6"

Query

:MACHine{1|2}:WLISt:DELay?

The DELay query returns the current time offset (delay) value from the

trigger.

Returned Format

[:MACHine{1|2}:WLISt:DELay] <time_value><NL>

<delay_value>

Real number between −2500 s and +2500 s

Example

OUTPUT XXX;":MACHINE1:WLIST:DELAY?"

14–5

Download from Www.Somanuals.com. All Manuals Search And Download.

WLISt Subsystem

INSert

Command

:MACHine{1|2}:WLISt:INSert [<module_spec>,]

<label_name>[,{<bit_id>|OVERlay|ALL}]

The INSert command inserts waveforms in the timing waveform display. The

waveforms are added from top to bottom up to a maximum of 96 waveforms.

Once 96 waveforms are present, each time you insert another waveform, it

replaces the last waveform.

The first parameter specifies from which module the waveform is coming

from; however, the 1660A-series logic analyzers are single-module

instruments. Therefore, this parameter is not needed. It is described here as

a reminder that programs for the 16500A logic analysis system can be used.

The second parameter specifies the label name that will be inserted. The

optional third parameter specifies the label bit number, overlay, or all. If a

number is specified, only the waveform for that bit number is added to the

screen.

If you specify OVERlay, all the bits of the label are displayed as a composite

overlaid waveform. If you specify ALL, all the bits are displayed sequentially.

If you do not specify the third parameter, ALL is assumed.

<module_spec> {1|2|3|4|5|6|7|8|9|10} (not needed)

<label_name> String of up to 6 alphanumeric characters

<bit_id> An integer from 0 to 31

Examples

Inserting a logic analyzer waveform:

OUTPUT XXX;":MACHINE1:WLIST:INSERT 3, ’WAVE’,10"

14–6

Download from Www.Somanuals.com. All Manuals Search And Download.

WLISt Subsystem

LINE

Command

:MACHine{1|2}:WLISt:LINE <line_num_mid_screen>

The LINE command allows you to scroll the state analyzer listing vertically.

The command specifies the state line number relative to the trigger that the

analyzer highlights at the center of the screen.

<line_num_mid_

screen>

An integer from −8191 to +8191

Example

OUTPUT XXX;":MACHINE1:WLIST:LINE 0"

:MACHine{1|2}:WLISt:LINE?

Query

The LINE query returns the line number for the state currently in the box at

center screen.

Returned Format

[:MACHine{1|2}:WLISt:LINE] <line_num_mid_screen><NL>

Example

OUTPUT XXX;":MACHINE1:WLIST:LINE?"

14–7

Download from Www.Somanuals.com. All Manuals Search And Download.

WLISt Subsystem

OSTate

Query

:WLISt:OSTate?

The OSTate query returns the state where the O Marker is positioned. If data

is not valid, the query returns 32767.

Returned Format

[:WLISt:OSTate] <state_num><NL>

<state_num>

An integer from −8191 to +8191

Example

OUTPUT XXX;":WLIST:OSTATE?"

OTIMe

Command

:WLISt:OTIMe <time_value>

The OTIMe command positions the O Marker on the timing waveforms in the

mixed mode display. If the data is not valid, the command performs no

action.

<time_value> A real number

Example

OUTPUT XXX;":WLIST:OTIME 40.0E−6"

14–8

Download from Www.Somanuals.com. All Manuals Search And Download.

WLISt Subsystem

RANGe

Query

:WLISt:OTIMe?

The OTIMe query returns the O Marker position in time. If data is not valid,

the query returns 9.9E37.

Returned Format

[:WLISt:OTIMe] <time_value><NL>

<time_value> A real number

Example

OUTPUT XXX;":WLIST:OTIME?"

RANGe

Command

:MACHine{1|2}:WLISt:RANGe <time_value>

The RANGe command specifies the full-screen time in the timing waveform

menu. It is equivalent to ten times the seconds per division setting on the

display. The allowable values for RANGe are from 10 ns to 10 ks.

<time_value> A real number between 10 ns and 10 ks

Example

OUTPUT XXX;":MACHINE1:WLIST:RANGE 100E−9"

Query

:MACHine{1|2}:WLISt:RANGe?

The RANGe query returns the current full-screen time.

Returned Format

[:MACHine{1|2}:WLISt:RANGe] <time_value><NL>

<time_value> A real number between 10 ns and 10 ks

Example

OUTPUT XXX;":MACHINE1:WLIST:RANGE?"

14–9

Download from Www.Somanuals.com. All Manuals Search And Download.

WLISt Subsystem

REMove

Command

:MACHine{1|2}:WLISt:REMove

The REMove command deletes all waveforms from the display.

Example

OUTPUT XXX;":MACHINE1:WLIST:REMOVE"

XOTime

Query

:MACHine{1|2}:WLISt:XOTime?

The XOTime query returns the time from the X marker to the O marker. If

data is not valid, the query returns 9.9E37.

Returned Format

[:MACHine{1|2}:WLISt:XOTime] <time_value><NL>

<time_value> A real number

Example

OUTPUT XXX;":MACHINE1:WLIST:XOTIME?"

14–10

Download from Www.Somanuals.com. All Manuals Search And Download.

WLISt Subsystem

XSTate

Query

:WLISt:XSTate?

The XSTate query returns the state where the X Marker is positioned. If data

is not valid, the query returns 32767.

Returned Format

[:WLISt:XSTate] <state_num><NL>

<state_num> An integer

Example

OUTPUT XXX;":WLIST:XSTATE?"

XTIMe

Command

:WLISt:XTIMe <time_value>

The XTIMe command positions the X Marker on the timing waveforms in the

mixed mode display. If the data is not valid, the command performs no

action.

<time_value> A real number

Example

OUTPUT XXX;":WLIST:XTIME 40.0E−6"

14–11

Download from Www.Somanuals.com. All Manuals Search And Download.

WLISt Subsystem

XTIMe

Query

:WLISt:XTIMe?

The XTIMe query returns the X Marker position in time. If data is not valid,

the query returns 9.9E37.

Returned Format

[:WLISt:XTIMe] <time_value><NL>

<time_value> A real number

Example

OUTPUT XXX;":WLIST:XTIME?"

14–12

Download from Www.Somanuals.com. All Manuals Search And Download.

SFORmat Subsystem

Download from Www.Somanuals.com. All Manuals Search And Download.

Introduction

The SFORmat subsystem contains the commands available for the

State Format menu in the 1660A-series logic analyzers. These

commands are:

• CLOCk

• LABel

• MASTer

• MODE

• MOPQual

• MQUal

• REMove

• SETHold

• SLAVe

• SOPQual

• SQUal

• THReshold

15–2

Download from Www.Somanuals.com. All Manuals Search And Download.

SFORmat Subsystem

Figure 15-1

SFORmat Subsystem Syntax Diagram

15–3

Download from Www.Somanuals.com. All Manuals Search And Download.

SFORmat Subsystem

Figure 15-1

SFORmat Subsystem Syntax Diagram (continued)

15–4

Download from Www.Somanuals.com. All Manuals Search And Download.

SFORmat Subsystem

Table 15-1

SFORmat Parameter Values

Parameter

Values

<N>

{{1|2}|{3|4|5|6}|{7|8}}

String of up to 6 alphanumeric characters

{POSitive|NEGative}

label_name

polarity

clock_bits

Format (integer from 0 to 63) for a clock (clocks are assigned

in decreasing order)

upper_bits

lower_bits

Format (integer from 0 to 65535) for a pod (pods are assigned

in decreasing order)

Format (integer from 0 to 65535) for a pod (pods are assigned

in decreasing order)

clock_id

{J|K|L|M|N|P}

{OFF|RISing|FALLing|BOTH}

{1|2}

clock_spec

clock_pair_id

qual_operation

qual_num

{AND|OR}

{1|2|3|4}

qual_level

pod_num

{OFF|LOW|HIGH}

{1|2|3|4|5|6|7|8}

{0|1|2|3|4|5|6|7|8|9}

set_hold_value

value

voltage (real number) −6.00 to +6.00

15–5

Download from Www.Somanuals.com. All Manuals Search And Download.

SFORmat Subsystem

SFORmat

Selector

:MACHine{1|2}:SFORmat

The SFORmat (State Format) selector is used as a part of a compound

header to access the settings in the State Format menu. It always follows the

MACHine selector because it selects a branch directly below the MACHine

level in the command tree.

Example

OUTPUT XXX;":MACHINE2:SFORMAT:MASTER J, RISING"

CLOCk

Command

:MACHine{1|2}:SFORmat:CLOCk<N> <clock_mode>

The CLOCk command selects the clocking mode for a given pod when the

pod is assigned to the state analyzer. When the MASTer option is specified,

the pod will sample all 16 channels on the master clock. When the SLAVe

option is specified, the pod will sample all 16 channels on the slave

clock. When the DEMultiplex option is specified, only one pod of a pod pair

can acquire data. The 16 bits of the selected pod will be clocked by the

demultiplex master for labels with bits assigned under the Master pod. The

same 16 bits will be clocked by the demultiplex slave for labels with bits

assigned under the Slave pod. The master clock always follows the slave

clock when both are used.

<N> {{1|2}| {3|4}|{5|6}|{7|8}}1 through 8 for the HP 1660A, 1 through

6 for the HP 1661A, 1 through 4 for the HP 1662A, and 1 through 2 for the HP

1663A.

<clock_mode> {MASTer|SLAVe|DEMultiplex}

Example

OUTPUT XXX;":MACHINE1:SFORMAT:CLOCK2 MASTER"

15–6

Download from Www.Somanuals.com. All Manuals Search And Download.

SFORmat Subsystem

LABel

Query

:MACHine{1|2}:SFORmat:CLOCk<N>?

The CLOCk query returns the current clocking mode for a given pod.

Returned Format

[:MACHine{1|2}:SFORmat:CLOCK<N>] <clock_mode><NL>

Example

OUTPUT XXX; ":MACHINE1:SFORMAT:CLOCK2?"

LABel

Command

:MACHine{1|2}:SFORmat:LABel <name>,[<polarity>,

<clock_bits>, <upper_bits>, <lower_bits>

[,<upper_bits>,<lower_bits>]...]

The LABel command allows you to specify polarity and assign channels to

new or existing labels. If the specified label name does not match an existing

label name, a new label will be created.

The order of the pod-specification parameters is significant. The first one

listed will match the highest numbered pod assigned to the machine you’re

using. Each pod specification after that is assigned to the next highest

numbered pod. This way they match the left-to-right descending order of the

pods you see on the Format display. Not including enough pod specifications

results in the lowest numbered pod(s) being assigned a value of zero (all

channels excluded). If you include more pod specifications than there are

pods for that machine, the extra ones will be ignored. However, an error is

reported anytime when more than 13 pod specifications are listed.

The polarity can be specified at any point after the label name.

Because pods contain 16 channels, the format value for a pod must be

between 0 and 65535 (2¹⁶−1). When giving the pod assignment in binary

(base 2), each bit will correspond to a single channel. A "1" in a bit position

means the associated channel in that pod is assigned to that pod and bit. A

"0" in a bit position means the associated channel in that pod is excluded

from the label. For example, assigning #B1111001100 is equivalent to

entering "......****..**.." from the front panel.

A label can not have a total of more than 32 channels assigned to it.

<name> String of up to 6 alphanumeric characters

15–7

Download from Www.Somanuals.com. All Manuals Search And Download.

SFORmat Subsystem

LABel

<polarity> {POSitive|NEGative}

<clock_bits> Format (integer from 0 to 63) for a clock (clocks are assigned in decreasing

order)

<upper_bits> Format (integer from 0 to 65535) for a pod (pods are assigned in decreasing

order)

<lower_bits> Format (integer from 0 to 65535) for a pod (pods are assigned in decreasing

order)

Examples

OUTPUT XXX;":MACHINE2:SFORMAT:LABEL ’STAT’, POSITIVE,

0,127,40312"

OUTPUT XXX;":MACHINE2:SFORMAT:LABEL ’SIG 1’, #B11,

#B0000000011111111,#B0000000000000000 "

Query

:MACHine{1|2}:SFORmat:LABel? <name>

The LABel query returns the current specification for the selected (by name)

label. If the label does not exist, nothing is returned. The polarity is always

returned as the first parameter. Numbers are always returned in decimal

format.

Returned Format

[:MACHine{1|2}:SFORmat:LABel] <name>,<polarity>

[, <clock_bits>, <upper_bits>, <lower_bits>]<NL>

Example

OUTPUT XXX;":MACHINE2:SFORMAT:LABEL? ’DATA’"

15–8

Download from Www.Somanuals.com. All Manuals Search And Download.

SFORmat Subsystem

MASTer

Command Syntax:

:MACHine{1|2}:SFORmat:MASTer <clock_id>,

<clock_spec>

The MASTer clock command allows you to specify a master clock for a given

machine. The master clock is used in all clocking modes (Master, Slave, and

Demultiplexed). Each command deals with only one clock (J,K,L,M,N,P);

therefore, a complete clock specification requires six commands, one for

each clock. Edge specifications (RISing, FALLing, or BOTH) are ORed.

At least one clock edge must be specified.

<clock_id> {J|K|L|M|N|P}

<clock_spec> {OFF|RISing|FALLing|BOTH}

Example

OUTPUT XXX;":MACHINE2:SFORMAT:MASTER J, RISING"

Query

:MACHine{1|2}:SFORmat:MASTer? <clock_id>

The MASTer query returns the clock specification for the specified clock.

Returned Format

[:MACHine{1|2}:SFORmat:MASTer]<clock_id>,<clock_spec><NL>

Example

OUTPUT XXX;":MACHINE2:SFORMAT:MASTER? <clock_id>"

15–9

Download from Www.Somanuals.com. All Manuals Search And Download.

SFORmat Subsystem

MODE

Command

:MACHine{1|2}:SFORmat:MODE <acq_mode>

The MODE command allows you to select the acquistion mode of the state

analyzer. The modes are either full-channel with 4 Kbit of memory depth per

channel or half-channel with 8 Kbit of memory depth per channel.

<acq_mode> {FULL|DEEPmemory}

Example

OUTPUT XXX;":MACHine1:SFORMAT:MODE FULL"

Query

:MACHine{1|2}:SFORmat:MODE?

The MODE query returns the current acquistion mode.

Returned Format

[:MACHine{1|2}:SFORmat:MODE] <acq_mode><NL>

Example

OUTPUT XXX;":MACHINE1:SFORMAT:MODE?"

15–10

Download from Www.Somanuals.com. All Manuals Search And Download.

SFORmat Subsystem

MOPQual

Command

:MACHine{1|2}:SFORmat:MOPQual <clock_pair_id>,

<qual_operation>

The MOPQual (master operation qualifier) command allows you to specify

either the AND or the OR operation between master clock qualifier pair 1 and

2, or between master clock qualifier pair 3 and 4. For example, you can

specify a master clock operation qualifer 1 AND 2.

<clock_pair_id> {1|2}

<qual_ {AND|OR}

operation>

Example

OUTPUT XXX;":MACHINE1:SFORMAT:MOPQUAL 1,AND"

Query

:MACHine{1|2}:SFORmat:MOPQUal? <clock_pair_id>

The MOPQual query returns the operation qualifier specified for the master

clock.

Returned Format:

[:MACHine{1|2}:SFORmat:MOPQUal <clock_pair_id>]

<qual_operation><NL>

Example

OUTPUT XXX;":MACHine1:SFORMAT:MOPQUAL? 1"

15–11

Download from Www.Somanuals.com. All Manuals Search And Download.

SFORmat Subsystem

MQUal

Command

:MACHine{1|2}:SFORmat:MQUal

<qual_num>,<clock_id>,<qual_level>

The MQUal (master qualifier) command allows you to specify the level

qualifier for the master clock.

<qual_num> {{1|2}|{3|4}}1 through 4 for HP 1660A, HP 1661A, HP 1662A; or, 1 or 2

for HP 1663A.

<clock_id> {J|K|L|M|N|P}

<qual_level> {OFF|LOW|HIGH}

Example

OUTPUT XXX;":MACHINE2:SFORMAT:MQUAL 1,J,LOW"

Query

:MACHine{1|2}:SFORmat:MQUal? <qual num>

The MQUal query returns the qualifier specified for the master clock.

Returned Format

[:MACHine{1|2}:SFORmat:MQUal] <qual_level><NL>

Example

OUTPUT XXX;":MACHINE2:SFORMAT:MQUAL? 1"

15–12

Download from Www.Somanuals.com. All Manuals Search And Download.

SFORmat Subsystem

REMove

Command

:MACHine{1|2}:SFORmat:REMove {<name>|ALL}

The REMove command allows you to delete all labels or any one label for a

given machine.

<name> String of up to 6 alphanumeric characters

Examples

OUTPUT XXX;":MACHINE2:SFORMAT:REMOVE ’A’"

OUTPUT XXX;":MACHINE2:SFORMAT:REMOVE ALL"

SETHold

Command

:MACHine{1|2}:SFORmat:SETHold <pod_num>,

<set_hold_value>

The SETHold (setup/hold) command allows you to set the setup and hold

specification for the state analyzer.

Even though the command requires integers to specify the setup and hold, the

query returns the current settings in a string. For example, if you send the

integer 0 for the setup and hold value, the query will return 3.5/0.0 ns as an

ASCII string when you have one clock and one edge specified.

15–13

Download from Www.Somanuals.com. All Manuals Search And Download.

SFORmat Subsystem

SETHold

<pod_num> {{1|2}|{3|4}|{5|6}|{7|8}}1 through 8 for the HP 1660A, 1 through

6 for the HP 1661A, 1 through 4 for the HP 1662A, and 1 through 2 for the HP

1663A.

<set_hold_ An integer {0|1|2|3|4|5|6|7|8|9} representing the setup and hold

value> values in table 15-2.

Table 15-2

Setup and hold values

For one clock and one

edge

For one clock and both

edges

For multiple clocks

0 = 3.5/0.0 ns

1 = 3.0/0.5 ns

2 = 2.5/1.0 ns

3 = 2.0/1.5 ns

4 = 1.5/2.0 ns

5 = 1.0/2.5 ns

6 = 0.5/3.0 ns

7 = 0.0/3.5 ns

N/A

0 = 4.0/0.0

1 = 3.5/0.5

2 = 3.0/1.0

3 = 2.5/1.5

4 = 2.0/2.0

5 = 1.5/2.5

6 = 1.0/3.0

7 = 0.5/3.5

8 = 0.0/4.0

N/A

0 = 4.5/0.0

1 = 4.0/0.5

2 = 3.5/1.0

3 = 3.0/1.5

4 = 2.5/2.0

5 = 2.0/2.5

6 = 1.5/3.0

7 = 1.0/3.5

8 = 0.5/4.0

9 = 0.0/4.5

N/A

Example

OUTPUT XXX;":MACHINE2:SFORMAT:SETHOLD 1,2"

Query

:MACHine{1|2}:SFORMAT:SETHOLD? <pod_num>

The SETHold query returns the current setup and hold settings.

Returned Format

[:MACHine{1|2}:SFORmat:SETHold <pod_num>] <set_hold_value><NL>

Example

OUTPUT XXX;":MACHINE2:SFORMAT:SETHOLD? 3"

15–14

Download from Www.Somanuals.com. All Manuals Search And Download.

SFORmat Subsystem

SLAVe

Command

:MACHine{1|2}:SFORmat:SLAVe

<clock_id>,<clock_spec>

The SLAVe clock command allows you to specify a slave clock for a given

machine. The slave clock is only used in the Slave and Demultiplexed

clocking modes. Each command deals with only one clock (J,K,L,M,N,P);

therefore, a complete clock specification requires six commands, one for

each clock. Edge specifications (RISing, FALLing, or BOTH) are ORed.

When slave clock is being used at least one edge must be specified.

<clock_id> {J|K|L|M|N|P}

<clock_spec> {OFF|RISing|FALLing|BOTH}

Example

OUTPUT XXX;":MACHINE2:SFORMAT:SLAVE J, RISING"

Query

:MACHine{1|2}:SFORmat:SLAVe?<clock id>

The SLAVe query returns the clock specification for the specified clock.

Returned Format

[:MACHine{1|2}:SFORmat:SLAVe] <clock_id>,<clock_spec><NL>

Example

OUTPUT XXX;":MACHINE2:SFORMAT:SLAVE? K"

15–15

Download from Www.Somanuals.com. All Manuals Search And Download.

SFORmat Subsystem

SOPQual

Command

:MACHine{1|2}:SFORmat:SOPQual <clock_pair_id>,

The SOPQual (slave operation qualifier) command allows you to specify

either the AND or the OR operation between slave clock qualifier pair 1 and

2, or between slave clock qualifier pair 3 and 4. For example you can specify

a slave clock operation qualifer 1 AND 2.

<clock_pair_id> {1|2}

<qual_ {AND|OR}

operation>

Example

OUTPUT XXX;":MACHine2:SFORMAT:SOPQUAL 1,AND"

Query

:MACHine{1|2}:SFORmat:SOPQual? <clock pair id>

The SOPQual query returns the operation qualifier specified for the slave

clock.

Returned Format

[:MACHine{1|2}:SFORmat:SOPQual <clock_pair_id>]

<qual_operation><NL>

Example

OUTPUT XXX;":MACHiNE2:SFORMAT:SOPQUAL? 1"

15–16

Download from Www.Somanuals.com. All Manuals Search And Download.

SFORmat Subsystem

SQUal

Command

:MACHine{1|2}:SFORmat:SQUal <qual_num>,<clock_id>,

<qual_level>

The SQUal (slave qualifier) command allows you to specify the level qualifier

for the slave clock.

<qual_num> {{1|2}|{3|4}}1 through 4 for HP 1660A, HP 1661A, HP 1662A; or, 1 or 2

for HP 1663A.

<clock_id> {J|K|L|M|N|P}

<qual_level> {OFF|LOW|HIGH}

Example

OUTPUT XXX;":MACHINE2:SFORMAT:SQUAL 1,J,LOW"

Query

:MACHine{1|2}:SFORmat:SQUal?<qual_num>

The SQUal query returns the qualifier specified for the slave clock.

Returned Format

[:MACHine{1|2}:SFORmat:SQUal] <clock_id>,<qual_level><NL>

Example

OUTPUT XXX;":MACHINE2:SFORMAT:SQUAL? 1"

15–17

Download from Www.Somanuals.com. All Manuals Search And Download.

SFORmat Subsystem

THReshold

Command

:MACHine{1|2}:SFORmat:THReshold<N>

{TTL|ECL|<value>}

The THReshold command allows you to set the voltage threshold for a given

pod to ECL, TTL, or a specific voltage from −6.00 V to +6.00 V in 0.05 volt

increments.

<N> {{1|2}|{3|4}|{5|6}|{7|8}}1 through 8 for the HP 1660A, 1 through

6 for the HP 1661A, 1 through 4 for the HP 1662A, and 1 through 2 for the HP

1663A.

<value>

Voltage (real number) −6.00 to +6.00

TTL Default value of +1.6 V

ECL

Default value of −1.3 V

Example

OUTPUT XXX;":MACHINE1:SFORMAT:THRESHOLD1 4.0"

Query

:MACHine{1|2}:SFORmat:THReshold<N>?

The THReshold query returns the current threshold for a given pod.

Returned Format

[:MACHine{1|2}:SFORmat:THReshold<N>] <value><NL>

Example

OUTPUT XXX;":MACHINE1:SFORMAT:THRESHOLD4?"

15–18

Download from Www.Somanuals.com. All Manuals Search And Download.

STRigger (STRace) Subsystem

Download from Www.Somanuals.com. All Manuals Search And Download.

Introduction

The STRigger subsystem contains the commands available for the

State Trigger menu in the 1660A-series logic analyzers. The State

Trigger subsystem will also accept the STRace Command as used in

previous 1650-series logic analyzers to eliminate the need to rewrite

programs containing STRace as the Command keyword. The

STRigger subsystem commands are:

• ACQuisition

• BRANch

• CLEar

• FIND

• RANGe

• SEQuence

• STORe

• TAG

• TAKenbranch

• TCONtrol

• TERM

• TIMER

• TPOSition

16–2

Download from Www.Somanuals.com. All Manuals Search And Download.

STRigger (STRace) Subsystem

Figure 16-1

STRigger Subsystem Syntax Diagram

16–3

Download from Www.Somanuals.com. All Manuals Search And Download.

STRigger (STRace) Subsystem

Figure 16-1 (continued)

STRigger Subsystem Syntax Diagram (continued)

16–4

Download from Www.Somanuals.com. All Manuals Search And Download.

STRigger (STRace) Subsystem

Figure 16-1 (continued)

STRigger Subsystem Suntax Diagram (continued)

16–5

Download from Www.Somanuals.com. All Manuals Search And Download.

STRigger (STRace) Subsystem

Table 16-1

STRigger Parameter Values

Values

Parameter

branch_qualifier

to_lev_num

integer from 1 to last level

proceed_qualifier

occurrence

number from 1 to 1048575

string of up to 6 alphanumeric characters

label_name

start_pattern

"{#B{0|1} . . . |

#Q{0|1|2|3|4|5|6|7} . . . |

#H{0|1|2|3|4|5|6|7|8|9|A|B|C|D|E|F} . .

. |

{0|1|2|3|4|5|6|7|8|9} . . . }"

stop_pattern

"{#B{0|1} . . . |

#Q{0|1|2|3|4|5|6|7} . . . |

#H{0|1|2|3|4|5|6|7|8|9|A|B|C|D|E|F} . .

. |

{0|1|2|3|4|5|6|7|8|9} . . . }"

num_of_levels

lev_of_trig

integer from 2 to 12

integer from 1 to (number of existing sequence levels − 1)

store_qualifier

state_tag_qualifier

timer_num

{1|2}

timer_value

term_id

400 ns to 500 seconds

{A|B|C|D|E|F|G|H|I|J}

pattern

"{#B{0|1|X} . . . |

#Q{0|1|2|3|4|5|6|7|x} . . . |

#H{0|1|2|3|4|5|6|7|8|9|A|B|C|D|E|F|x}...|

{0|1|2|3|4|5|6|7|8|9} . . . }"

see "Qualifier" on page 16-7

qualifier

post_value

integer from 0 to 100 representing percentage

16–6

Download from Www.Somanuals.com. All Manuals Search And Download.

STRigger (STRace) Subsystem

Qualifier

The qualifier for the state trigger subsystem can be terms A through J, Timer

1 and 2, and Range 1 and 2. In addition, qualifiers can be the NOT boolean

function of terms, timers, and ranges. The qualifier can also be an expression

or combination of expressions as shown below and figure 16-2, "Complex

Qualifier," on page 16-11.

The following parameters show how qualifiers are specified in all commands

of the STRigger subsystem that use <qualifier>.

<qualifier> {"ANYSTATE"|"NOSTATE"|"<expression>"}

<expression> {<expression1a>|<expression1b>|<expression1a> OR

<expression1b>|<expression1a> AND <expression1b>}

<expression1a> {<expression1a_term>|(<expression1a_term>[ OR

<expression1a_term>]* )|(<expression1a_term>[ AND

<expression1a_term>]* )}

<expression1a_ { <expression2a>|<expression2b>|<expression2c>|<expression2d>}

term>

<expression1b> {<expression1b_term>|( <expression1b_term>[ OR

<expression1b_term>]* )|(<expression1b_term>[ AND

<expression1b_term>]* )}

<expression1b_ {<expression2e>|<expression2f>|<expression2g>|<expression2h>}

term>

<expression2a> {<term3a>|<term3b>|(<term3a> <boolean_op> <term3b>)}

<expression2b> {<term3c>|<range3a>|(<term3c> <boolean_op> <range3a>)}

<expression2c> {<term3d>}

<expression2d> {<term3e>|<timer3a>|(<term3e> <boolean_op> <timer3a>)}

<expression2e> {<term3f>|<term3g>|(<term3f> <boolean_op> <term3g>)}

<expression2f> {<term3h>|<range3b>|(<term3h> <boolean_op> <range3b>)}

<expression2g> {<term3i>}

<expression2h> {<term3j>|<timer3b>|(<term3e> <boolean_op> <timer3b>)}

<boolean_op> {AND|NAND|OR|NOR|XOR|NXOR}

<term3a> {A|NOTA}

16–7

Download from Www.Somanuals.com. All Manuals Search And Download.

STRigger (STRace) Subsystem

Qualifier

<term3b> {B|NOTB}

<term3c> {C|NOTC}

<term3d> {D|NOTD}

<term3e> {E|NOTE}

<term3f> {F|NOTF}

<term3g> {G|NOTG}

<term3h> {H|NOTH}

<term3i> {I|NOTI}

<term3j> {J|NOTJ}

<range3a> {IN_RANGE1|OUT_RANGE1}

<range3b> {IN_RANGE2|OUT_RANGE2}

<timer3a> {TIMER1<|TIMER1>}

<timer3b> {TIMER2<|TIMER2>}

Qualifier Rules

The following rules apply to qualifiers:

Qualifiers are quoted strings and, therefore, need quotes.

Expressions are evaluated from left to right.

•

Parenthesis are used to change the order evaluation and, therefore, are

optional.

An expression must map into the combination logic presented in the

combination pop-up menu within the STRigger menu (see figure 16-2 on

page 16-12).

•

Examples

’A’

’( A OR B )’

’(( A OR B ) AND C )’

’(( A OR B ) AND C AND IN_RANGE2 )’

’(( A OR B ) AND ( C AND IN_RANGE1 ))’

’IN_RANGE1 AND ( A OR B ) AND C’

16–8

Download from Www.Somanuals.com. All Manuals Search And Download.

STRigger (STRace) Subsystem

STRigger (STRace)

Selector

:MACHine{1|2}:STRigger

The STRigger (STRace) (State Trigger) Command is used as a part of a

compound header to access the settings found in the State Trace menu. It

always follows the MACHine Command because it selects a branch directly

below the MACHine level in the command tree.

Example

OUTPUT XXX;":MACHINE1:STRIGGER:TAG TIME"

ACQuisition

Command

:MACHine{1|2}:STRigger:ACQuisition

{AUTOmatic|MANual}

The ACQuisition command allows you to specify the acquisition mode for the

State analyzer.

Example

OUTPUT XXX;":MACHINE1:STRIGGER:ACQUISITION AUTOMATIC"

Query

:MACHine{1|2}:STRigger:ACQuisition?

The ACQuisition query returns the current acquisition mode specified.

Returned Format

[:MACHine{1|2}:STRigger:ACQuisition] {AUTOmatic|MANual}<NL>

Example

OUTPUT XXX;":MACHINE1:STRIGGER:ACQUISITION?"

16–9

Download from Www.Somanuals.com. All Manuals Search And Download.

STRigger (STRace) Subsystem

BRANch

Command

:MACHine{1|2}:STRigger:BRANch<N>

<branch_qualifier>,<to_level_number>

The BRANch command defines the branch qualifier for a given sequence

level. When this branch qualifier is matched, it will cause the sequencer to

jump to the specified sequence level.

The terms used by the branch qualifier (A through J) are defined by the

TERM command. The meaning of IN_RANGEand OUT_RANGEis

determined by the RANGE command.

Within the limitations shown by the syntax definitions, complex expressions

may be formed using the AND and ORoperators. Expressions are limited to

what you could manually enter through the State Trigger menu. Regarding

parentheses, the syntax definitions on the next page show only the required

ones. Additional parentheses are allowed as long as the meaning of the

expression is not changed. Figure 16-2 shows a complex expression as seen

in the State Trigger menu.

Example

The following statements are all correct and have the same meaning. Notice

that the conventional rules for precedence are not followed. The expressions

are evaluated from left to right.

OUTPUT XXX;":MACHINE1:STRIGGER:BRANCH1 ’C AND D OR F OR G’, 1"

OUTPUT XXX;":MACHINE1:STRIGGER:BRANCH1 ’((C AND D) OR

(F OR G))’, 1"

OUTPUT XXX;":MACHINE1:STRIGGER:BRANCH1 ’F OR (C AND D) OR

G’,1"

<N> An integer from 1 to <number_of_levels>

<to_level_ An integer from 1 to <number_of_levels>

number>

<number_of_ An integer from 2 to the number of existing sequence levels (maximum 12)

levels>

<branch_ <qualifier>see "Qualifier" on page 16-7

qualifier>

16–10

Download from Www.Somanuals.com. All Manuals Search And Download.

STRigger (STRace) Subsystem

BRANch

Examples

OUTPUT XXX;":MACHINE1:STRIGGER:BRANCH1 ’ANYSTATE’, 3"

OUTPUT XXX;":MACHINE2:STRIGGER:BRANCH2 ’A’, 7"

OUTPUT XXX;":MACHINE1:STRIGGER:BRANCH3 ’((A OR B) OR NOTG)’,

Query

:MACHine{1|2}:STRigger:BRANch<N>?

The BRANch query returns the current branch qualifier specification for a

given sequence level.

Returned Format

[:MACHine{1|2}:STRigger:BRANch<N>] <branch_qualifier>,

<to_level_num><NL>

Example

OUTPUT XXX;":MACHINE1:STRIGGER:BRANCH3?"

Figure 16-2

Complex qualifier

Figure 16-2 is a front panel representation of the complex qualifier (a OR b)

AND(g OR h).

16–11

Download from Www.Somanuals.com. All Manuals Search And Download.

STRigger (STRace) Subsystem

CLEar

Example

This example would be used to specify this complex qualifier.

OUTPUT XXX;":MACHINE1:STRIGGER:BRANCH1 ’((A OR B) AND

(G OR H))’, 2"

Terms A through E, RANGE 1, and TIMER 1 must be grouped together and

terms F through J, RANGE 2, and TIMER 2 must be grouped together. In the

first level, terms from one group may not be mixed with terms from the other.

For example, the expression ((A OR IN_RANGE2) AND (C OR H)) is not allowed

because the term C cannot be specified in the E through J group.

In the first level, the operators you can use are AND, NAND, OR, NOR,

XOR, NXOR. Either ANDor ORmay be used at the second level to join the

two groups together. It is acceptable for a group to consist of a single term.

Thus, an expression like (B AND G)is legal, since the two operands are

both simple terms from separate groups.

CLEar

Command

:MACHine{1|2}:STRigger:CLEar

{All|SEQuence|RESource}

The CLEar command allows you to clear all settings in the State Trigger

menu and replace them with the default, clear only the Sequence levels, or

clear only the resource term patterns.

Example

OUTPUT XXX;":MACHINE1:STRIGGER:CLEAR RESOURCE"

16–12

Download from Www.Somanuals.com. All Manuals Search And Download.

STRigger (STRace) Subsystem

FIND

Command

:MACHine{1|2}:STRigger:FIND<N>

<proceed_qualifier>,<occurrence>

The FIND command defines the proceed qualifier for a given sequence level.

The qualifier tells the state analyzer when to proceed to the next sequence

level. When this proceed qualifier is matched the specified number of times,

the sequencer will proceed to the next sequence level. In the sequence level

where the trigger is specified, the FIND command specifies the trigger

qualifier (see SEQuence command).

The terms A through J are defined by the TERM command. The meaning of

IN_RANGEand OUT_RANGEis determined by the RANGe command.

Expressions are limited to what you could manually enter through the State

Trigger menu. Regarding parentheses, the syntax definitions below show

only the required ones. Additional parentheses are allowed as long as the

meaning of the expression is not changed. See figure 16-2 for a detailed

example.

<N>

An integer from 1 to (number of existing sequence levels −1)

<occurrence> An integer from 1 to 1048575

<proceed_ <qualifier>see "Qualifier" on page 16-7

qualifier>

Examples

OUTPUT XXX;":MACHINE1:STRIGGER:FIND1 ’ANYSTATE’, 1"

OUTPUT XXX;":MACHINE1:STRIGGER:FIND3 ’((NOTA AND NOTB) OR G)’, 1"

16–13

Download from Www.Somanuals.com. All Manuals Search And Download.

STRigger (STRace) Subsystem

RANGe

Query

:MACHine{1|2}:STRigger:FIND4?

The FIND query returns the current proceed qualifier specification for a

given sequence level.

Returned Format

[:MACHine{1|2}:STRigger:FIND<N>] <proceed_qualifier>,

Example

OUTPUT XXX;":MACHINE1:STRIGGER:FIND<N>?"

RANGe

Command

:MACHine{1|2}:STRigger:RANGE

<label_name>,<start_pattern>,<stop_pattern>

The RANGe command allows you to specify a range recognizer term for the

specified machine. Since a range can only be defined across one label and,

since a label must contain 32 or less bits, the value of the start pattern or stop

pattern will be between (2³²)−1 and 0.

Because a label can only be defined across a maximum of two pods, a range

term is only available across a single label; therefore, the end points of the

range cannot be split between labels.

When these values are expressed in binary, they represent the bit values for

the label at one of the range recognizers’ end points. Don’t cares are not

allowed in the end point pattern specifications.

16–14

Download from Www.Somanuals.com. All Manuals Search And Download.

STRigger (STRace) Subsystem

RANGe

<label_name> String of up to 6 alphanumeric characters

<start_pattern> "{#B{0|1} . . . |

#Q{0|1|2|3|4|5|6|7} . . . |

#H{0|1|2|3|4|5|6|7|8|9|A|B|C|D|E|F} . . . |

{0|1|2|3|4|5|6|7|8|9} . . . }"

<stop_pattern> "{#B{0|1} . . . |

#Q{0|1|2|3|4|5|6|7} . . . |

#H{0|1|2|3|4|5|6|7|8|9|A|B|C|D|E|F} . . . |

{0|1|2|3|4|5|6|7|8|9} . . . }"

Examples

OUTPUT XXX;":MACHINE1:STRIGGER:RANGE ’DATA’, ’127’, ’255’ "

OUTPUT XXX;":MACHINE1:STRIGGER:RANGE ’ABC’, ’#B00001111’,

’#HCF’ "

Query

:MACHine{1|2}:STRigger:RANGe?

The RANGe query returns the range recognizer end point specifications for

the range.

Returned Format

[:MACHine{1|2}:STRAce:RANGe] <label_name>,<start_pattern>,

<stop_pattern><NL>

Example

OUTPUT XXX;":MACHINE1:STRIGGER:RANGE?"

16–15

Download from Www.Somanuals.com. All Manuals Search And Download.

STRigger (STRace) Subsystem

SEQuence

Command

:MACHine{1|2}:STRigger:SEQuence

<number_of_levels>,

<level_of_trigger>

The SEQuence command redefines the state analyzer trace sequence. First,

it deletes the current trace sequence. Then it inserts the number of levels

specified, with default settings, and assigns the trigger to be at a specified

sequence level. The number of levels can be between 2 and 12 when the

analyzer is armed by the RUN key.

<number_of_ An integer from 2 to 12

levels>

<level_of_

trigger>

An integer from 1 to (number of existing sequence levels −1)

Example

OUTPUT XXX;":MACHINE1:STRIGGER:SEQUENCE 4,3"

Query

:MACHine{1|2}:STRigger:SEQuence?

The SEQuence query returns the current sequence specification.

Returned Format

[:MACHine{1|2}:STRigger:SEQuence] <number_of_levels>,

<level_of_trigger><NL>

<number_of_ An integer from 2 to 12

levels>

<level_of_

trigger>

An integer from 1 to (number of existing sequence levels −1)

Example

OUTPUT XXX;":MACHINE1:STRIGGER:SEQUENCE?"

16–16

Download from Www.Somanuals.com. All Manuals Search And Download.

STRigger (STRace) Subsystem

STORe

Command

:MACHine{1|2}:STRigger:STORe<N> <store_qualifier>

The STORe command defines the store qualifier for a given sequence level.

Any data matching the STORe qualifier will actually be stored in memory as

part of the current trace data. The qualifier may be a single term or a

complex expression. The terms A through J are defined by the TERM

command. The meaning of IN_RANGE1and 2and OUT_RANGE1and 2is

determined by the RANGecommand.

Expressions are limited to what you could manually enter through the State

Trigger menu. Regarding parentheses, the syntax definitions below show

only the required ones. Additional parentheses are allowed as long as the

meaning of the expression is not changed.

A detailed example is provided in figure 16-2 on page 16-12.

<N> An integer from 1 to the number of existing sequence levels (maximum 12)

<store_ <qualifier>see "Qualifier" on page 16-7

qualifier>

Examples

OUTPUT XXX;":MACHINE1:STRIGGER:STORE1 ’ANYSTATE’"

OUTPUT XXX;":MACHINE1:STRIGGER:STORE2 ’OUT_RANGE1’"

OUTPUT XXX;":MACHINE1:STRIGGER:STORE3 ’(NOTC AND NOTD AND

NOTH)’"

Query

:MACHine{1|2}:STRigger:STORe<N>?

The STORe query returns the current store qualifier specification for a given

sequence level <N>.

Returned Format

[:MACHine{1|2}:STRigger:STORe<N>] <store_qualifier><NL>

Example

OUTPUT XXX;":MACHINE1:STRIGGER:STORE4?"

16–17

Download from Www.Somanuals.com. All Manuals Search And Download.

STRigger (STRace) Subsystem

TAG

Command

:MACHine{1|2}:STRigger:TAG

{OFF|TIME|<state_tag_qualifier>}

The TAG command selects the type of count tagging (state or time) to be

performed during data acquisition. State tagging is indicated when the

parameter is the state tag qualifier, which will be counted in the qualified

state mode. The qualifier may be a single term or a complex expression. The

terms A through J are defined by the TERM command. The terms

IN_RANGE1 and 2 and OUT_RANGE1 and 2 are defined by the RANGe

command.

Expressions are limited to what you could manually enter through the State

Trigger menu. Regarding parentheses, the syntax definitions below show

only the required ones. Additional parentheses are allowed as long as the

meaning of the expression is not changed. A detailed example is provided in

figure 16-2 on page 16-12.

<state_tag_ <qualifier>see "Qualifier" on page 16-7

qualifier>

Examples

OUTPUT XXX;":MACHINE1:STRIGGER:TAG OFF"

OUTPUT XXX;":MACHINE1:STRIGGER:TAG TIME"

OUTPUT XXX;":MACHINE1:STRIGGER:TAG ’(IN_RANGE OR NOTF)’"

OUTPUT XXX;":MACHINE1:STRIGGER:TAG ’((IN_RANGE OR A) AND E)’"

Query

:MACHine{1|2}:STRigger:TAG?

The TAG query returns the current count tag specification.

Returned Format

[:MACHine{1|2}:STRigger:TAG]

{OFF|TIME|<state_tag_qualifier>}<NL>

Example

OUTPUT XXX;":MACHINE1:STRIGGER:TAG?"

16–18

Download from Www.Somanuals.com. All Manuals Search And Download.

STRigger (STRace) Subsystem

TAKenbranch

Command

:MACHine{1|2}:STRigger:TAKenbranch {STORe|NOSTore}

The TAKenbranch command allows you to specify whether the state causing

a sequence level change is stored or not stored for the specified machine.

Both a state that causes the sequencer to proceed or a state that causes the

sequencer to branch is considered a sequence level change. A branch can

also jump to itself and this also considered a sequence level change. The

state causing the branch is defined by the BRANch command.

Example

OUTPUT XXX;":MACHINE2:STRIGGER:TAKENBRANCH STORE"

Query

:MACHine{1|2}:STRigger:TAKenbranch?

The TAKenbranch query returns the current setting.

Returned Format

[:MACHine{1|2}:STRigger:TAKenbranch] {STORe|NOSTore}<NL>

Example

OUTPUT XXX;":MACHINE2:STRIGGER:TAKENBRANCH?

16–19

Download from Www.Somanuals.com. All Manuals Search And Download.

STRigger (STRace) Subsystem

TCONtrol

Command

:MACHine{1|2}:STRigger:TCONtrol<N> <timer_num>,

{OFF|STARt|PAUSe|CONTinue}

The TCONtrol (timer control) command allows you to turn off, start, pause,

or continue the timer for the specified level. The time value of the timer is

defined by the TIMER command. There are two timers and they are

independently available for either machine. Neither timer can be assigned to

both machines simultaneously.

<N> An integer from 1 to the number of existing sequence levels (maximum 12)

<timer_num> {1|2}

Example

OUTPUT XXX;":MACHINE2:STRIGGER:TCONTROL6 1, PAUSE"

Query

:MACHine{1|2}:STRigger:TCONTROL<N>? <timer_num>

The TCONtrol query returns the current TCONtrol setting of the specified

level.

Returned Format

[:MACHine{1|2}:STRigger:TCONTROL<N> <timer_num>]

{OFF|STARt|PAUSe|CONTinue}<NL>

<N> An integer from 1 to the number of existing sequence levels (maximum 12)

<timer_num> {1|2}

Example

OUTPUT XXX;":MACHINE2:STRIGGER:TCONTROL?6 1"

16–20

Download from Www.Somanuals.com. All Manuals Search And Download.

STRigger (STRace) Subsystem

TERM

Command

:MACHine{1|2}:STRigger:TERM

<term_id>,<label_name>,

The TERM command allows you to specify a pattern recognizer term in the

specified machine. Each command deals with only one label in the given

term; therefore, a complete specification could require several commands.

Since a label can contain 32 or less bits, the range of the pattern value will be

between 2³²− 1 and 0. When the value of a pattern is expressed in binary, it

represents the bit values for the label inside the pattern recognizer term.

Because the pattern parameter may contain don’t cares and be represented

in several bases, it is handled as a string of characters rather than a number.

All 10 terms (A through J) are available for either machine but not both

simultaneously. If you send the TERM command to a machine with a term

that has not been assigned to that machine, an error message "Legal

command but settings conflict" is returned.

<term_id> {A|B|C|D|E|F|G|H|I|J}

<label_name> A string of up to 6 alphanumeric characters

<pattern> "{#B{0|1|X} . . . |

#Q{0|1|2|3|4|5|6|7|X} . . . |

#H{0|1|2|3|4|5|6|7|8|9|A|B|C|D|E|F|X} . . . |

{0|1|2|3|4|5|6|7|8|9} . . . }"

Example

OUTPUT XXX;":MACHINE1:STRIGGER:TERM A,’DATA’,’255’ "

OUTPUT XXX;":MACHINE1:STRIGGER:TERM B,’ABC’,’#BXXXX1101’ "

16–21

Download from Www.Somanuals.com. All Manuals Search And Download.

STRigger (STRace) Subsystem

TIMER

Query

:MACHine{1|2}:STRigger:TERM?

<term_id>,<label_name>

The TERM query returns the specification of the term specified by term

identification and label name.

Returned Format

[:MACHine{1|2}:STRAce:TERM]

<term_id>,<label_name>,<pattern><NL>

Example

OUTPUT XXX;":MACHINE1:STRIGGER:TERM? B,’DATA’ "

TIMER

Command

:MACHine{1|2}:STRigger:TIMER{1|2} <time_value>

The TIMER command sets the time value for the specified timer. The limits

of the timer are 400 ns to 500 seconds in 16 ns to 500 µs increments. The

increment value varies with the time value of the specified timer. There are

two timers and they are independently available for either machine. Neither

timer can be assigned to both machines simultaneously.

<time_value> A real number from 400 ns to 500 seconds in increments which vary from 16

ns to 500 µs.

Example

OUTPUT XXX;":MACHINE1:STRIGGER:TIMER1 100E−6"

16–22

Download from Www.Somanuals.com. All Manuals Search And Download.

STRigger (STRace) Subsystem

TPOSition

Query

:MACHine{1|2}:STRigger:TIMER{1|2}?

The TIMER query returns the current time value for the specified timer.

Returned Format

[:MACHine{1|2}:STRigger:TIMER{1|2}] <time_value><NL>

<time_value> A real number from 400 ns to 500 seconds in increments which vary from 16

ns to 500 µs.

Example

OUTPUT XXX;":MACHINE1:STRIGGER:TIMER1?"

TPOSition

Command

:MACHine{1|2}:STRigger:TPOSition

{STARt|CENTer|END|POSTstore,<poststore>}

The TPOSition (trigger position) command allows you to set the trigger at

the start, center, end or at any position in the trace (poststore). When STARt

is specified, approximately 16 states are stored before the trigger. When

END is specified, approximately 16 states are stored after the trigger.

Poststore is defined as 0 to 100 percent. When 0 or 100 percent is specified,

the trigger is actually the first or last state respectively.

<poststore> An integer from 0 to 100 representing percentage of poststore.

Examples

OUTPUT XXX;":MACHINE1:STRIGGER:TPOSITION END"

OUTPUT XXX;":MACHINE1:STRIGGER:TPOSITION POSTstore,75"

16–23

Download from Www.Somanuals.com. All Manuals Search And Download.

STRigger (STRace) Subsystem

TPOSition

Query

:MACHine{1|2}:STRigger:TPOSition?

The TPOSition query returns the current trigger position setting.

Returned Format

[:MACHine{1|2}:STRigger:TPOSition] {STARt|CENTer|END|

POSTstore,<poststore>}<NL>

Example

OUTPUT XXX;":MACHINE1:STRIGGER:TPOSITION?"

16–24

Download from Www.Somanuals.com. All Manuals Search And Download.

SLISt Subsystem

Download from Www.Somanuals.com. All Manuals Search And Download.

Introduction

The SLISt subsystem contains the commands available for the State

Listing menu in the 1660A logic analyzer. These commands are:

• COLumn

• CLRPattern

• DATA

• RUNTil

• TAVerage

• TMAXimum

• TMINimum

• VRUNs

• LINE

• MMODe

• OPATtern

• OSEarch

• OSTate

• OTAG

• XOTag

• XOTime

• XPATtern

• XSEarch

• XSTate

• OVERlay

• REMove

• XTAG

17–2

Download from Www.Somanuals.com. All Manuals Search And Download.

SLISt Subsystem

Figure 17-1

SLISt Subsystem Syntax Diagram

17–3

Download from Www.Somanuals.com. All Manuals Search And Download.

SLISt Subsystem

Figure 17-1 (continued)

SLISt Subsystem Syntax Diagram (continued)

17–4

Download from Www.Somanuals.com. All Manuals Search And Download.

SLISt Subsystem

Figure 17-1 (continued)

SLISt Subsystem Syntax Diagram (continued)

17–5

Download from Www.Somanuals.com. All Manuals Search And Download.

SLISt Subsystem

Table 17-1

SLISt Parameter Values

Parameter

Values

module_num

mach_num

col_num

{1|2|3|4|5|6|7|8}(2 through 10 not used)

{1|2}

Integer from 1 to 61

line_number

Integer from −8191 to +8191

label_name

base

A string of up to 6 alphanumeric characters

{BINary|HEXadecimal|OCTal|DECimal|TWOS|ASCi

i|SYMBol|IASSembler} for labels or

{ABSolute|RELative}for tags

line_num_mid_screen

label_pattern

Integer from −8191 to +8191

"{#B{0|1|X} . . . |

#Q{0|1|2|3|4|5|6|7|X} . . . |

#H{0|1|2|3|4|5|6|7|8|9|A|B|C|D|E|F|X} . .

. |

{0|1|2|3|4|5|6|7|8|9} . . . }"

occurrence

Integer from −8191 to +8192

time_value

Real number

state_value

run_until_spec

Real number

{OFF|LT,<value>|GT,<value>|INRange,<value>,

<value>|OUTRange,<value>,<value>}

value

Real number

17–6

Download from Www.Somanuals.com. All Manuals Search And Download.

SLISt Subsystem

SLISt

Selector

:MACHine{1|2}:SLISt

The SLISt selector is used as part of a compound header to access those

settings normally found in the State Listing menu. It always follows the

MACHine selector because it selects a branch directly below the MACHine

level in the command tree.

Example

OUTPUT XXX;":MACHINE1:SLIST:LINE 256"

COLumn

Command

:MACHine{1|2}:SLISt:COLumn <col_num>

[,<module_num>, MACHine{1|2}],<label_name>,<base>

The COLumn command allows you to configure the state analyzer list display

by assigning a label name and base to one of the 61 vertical columns in the

menu. A column number of 1 refers to the left most column. When a label is

assigned to a column it replaces the original label in that column.

When the label name is "TAGS," the TAGS column is assumed and the next

parameter must specify RELative or ABSolute.

A label for tags must be assigned in order to use ABSolute or RELative state

tagging.

17–7

Download from Www.Somanuals.com. All Manuals Search And Download.

SLISt Subsystem

CLRPattern

<col_num> integer from 1 to 61

<module_num> {1|2|3|4|5|6|7|8|9|10}(2 through 10 not used)

<label_name> string of up to 6 alphanumeric characters

<base> {BINary|HEXadecimal|OCTal|DECimal|TWOS|ASCii|SYMBol|

IASSembler} for labels

{ABSolute|RELative} for tags

Example

OUTPUT XXX;":MACHINE1:SLIST:COLUMN 4,’A’,HEX"

Query

:MACHine{1|2}:SLISt:COLumn? <col_num>

The COLumn query returns the column number, label name, and base for the

specified column.

Returned Format

[:MACHine{1|2}:SLISt:COLumn] <col_num>,<module_num>,

MACHine{1|2},<label_name>,<base><NL>

Example

OUTPUT XXX;":MACHINE1:SLIST:COLUMN? 4"

CLRPattern

Command

:MACHine{1|2}:SWAVeform:CLRPattern {X|O|ALL}

The CLRPattern command allows you to clear the patterns in the selected

Specify Patterns menu.

Example

OUTPUT XXX;":MACHINE1:SWAVEFORM:CLRPATTERN X"

17–8

Download from Www.Somanuals.com. All Manuals Search And Download.

SLISt Subsystem

DATA

Query

:MACHine{1|2}:SLISt:DATA?

<line_number>,<label_name>

The DATA query returns the value at a specified line number for a given

label. The format will be the same as the one shown in the listing display.

Returned Format

[:MACHine{1|2}:SLISt:DATA] <line_number>,<label_name>,

<pattern_string><NL>

<line_number>

integer from −8191 to +8191

<label_name> string of up to 6 alphanumeric characters

<pattern_ "{#B{0|1|X} . . . |

string> #Q{0|1|2|3|4|5|6|7|X} . . . |

#H{0|1|2|3|4|5|6|7|8|9|A|B|C|D|E|F|X} . . . |

{0|1|2|3|4|5|6|7|8|9} . . . }"

Example

OUTPUT XXX;":MACHINE1:SLIST:DATA? 512, ’RAS’"

LINE

Command

:MACHine{1|2}:SLISt:LINE <line_num_mid_screen>

The LINE command allows you to scroll the state analyzer listing vertically.

The command specifies the state line number relative to the trigger that the

analyzer highlights at the center of the screen.

<line_num_mid_

screen>

integer from −8191 to +8191

Example

OUTPUT XXX;":MACHINE1:SLIST:LINE 0"

17–9

Download from Www.Somanuals.com. All Manuals Search And Download.

SLISt Subsystem

MMODe

Query

:MACHine{1|2}:SLISt:LINE?

The LINE query returns the line number for the state currently in the box at

the center of the screen.

Returned Format

[:MACHine{1|2}:SLISt:LINE] <line_num_mid_screen><NL>

Example

OUTPUT XXX;":MACHINE1:SLIST:LINE?"

MMODe

Command

:MACHine{1|2}:SLISt:MMODe <marker_mode>

The MMODe command (Marker Mode) selects the mode controlling the

marker movement and the display of marker readouts. When PATTern is

selected, the markers will be placed on patterns. When STATe is selected

and state tagging is on, the markers move on qualified states counted

between normally stored states. When TIME is selected and time tagging is

enabled, the markers move on time between stored states. When MSTats is

selected and time tagging is on, the markers are placed on patterns, but the

readouts will be time statistics.

<marker_mode> {OFF|PATTern|STATe|TIME|MSTats}

Example

OUTPUT XXX;":MACHINE1:SLIST:MMODE TIME"

Query

:MACHine{1|2}:SLISt:MMODe?

The MMODe query returns the current marker mode selected.

Returned Format:

[:MACHine{1|2}:SLISt:MMODe] <marker_mode><NL>

Example

OUTPUT XXX;":MACHINE1:SLIST:MMODE?"

17–10

Download from Www.Somanuals.com. All Manuals Search And Download.

SLISt Subsystem

OPATtern

Command

:MACHine{1|2}:SLISt:OPATtern

<label_name>,<label_pattern>

The OPATtern command allows you to construct a pattern recognizer term

for the O Marker which is then used with the OSEarch criteria when moving

the marker on patterns. Because this command deals with only one label at a

time, a complete specification could require several invocations.

When the value of a pattern is expressed in binary, it represents the bit

values for the label inside the pattern recognizer term. In whatever base is

used, the value must be between 0 and 2³²− 1, since a label may not have

more than 32 bits. Because the <label_pattern>parameter may contain

don’t cares, it is handled as a string of characters rather than a number.

<label_name> string of up to 6 alphanumeric characters

<label_pattern> "{#B{0|1|X} . . . |

#Q{0|1|2|3|4|5|6|7|X} . . . |

#H{0|1|2|3|4|5|6|7|8|9|A|B|C|D|E|F|X} . . . |

{0|1|2|3|4|5|6|7|8|9} . . . }"

Examples

OUTPUT XXX;":MACHINE1:SLIST:OPATTERN ’DATA’,’255’ "

OUTPUT XXX;":MACHINE1:SLIST:OPATTERN ’ABC’,’#BXXXX1101’ "

Query

:MACHine{1|2}:SLISt:OPATtern? <label_name>

The OPATtern query returns the pattern specification for a given label name.

Returned Format

[:MACHine{1|2}:SLISt:OPATtern]

<label_name>,<label_pattern><NL>

Example

OUTPUT XXX;":MACHINE1:SLIST:OPATTERN? ’A’"

17–11

Download from Www.Somanuals.com. All Manuals Search And Download.

SLISt Subsystem

OSEarch

Command

:MACHine{1|2}:SLISt:OSEarch <occurrence>,<origin>

The OSEarch command defines the search criteria for the O marker, which is

then used with associated OPATtern recognizer specification when moving

the markers on patterns. The origin parameter tells the marker to begin a

search with the trigger, the start of data, or with the X marker. The actual

occurrence the marker searches for is determined by the occurrence

parameter of the OSEarch recognizer specification, relative to the origin. An

occurrence of 0 places the marker on the selected origin. With a negative

occurrence, the marker searches before the origin. With a positive

occurrence, the marker searches after the origin.

integer from −8191 to +8191

<origin> {TRIGger|STARt|XMARker}

Example

OUTPUT XXX;":MACHINE1:SLIST:OSEARCH +10,TRIGGER"

Query

:MACHine{1|2}:SLISt:OSEarch?

The OSEarch query returns the search criteria for the O marker.

Returned Format

[:MACHine{1|2}:SLISt:OSEarch] <occurrence>,<origin><NL>

Example

OUTPUT XXX;":MACHINE1:SLIST:OSEARCH?"

17–12

Download from Www.Somanuals.com. All Manuals Search And Download.

SLISt Subsystem

OSTate

Query

:MACHine{1|2}:SLISt:OSTate?

The OSTate query returns the line number in the listing where the O marker

resides (−8191 to +8191). If data is not valid, the query returns 32767.

[:MACHine{1|2}:SLISt:OSTate] <state_num><NL>

Returned Format

<state_num>

an integer from −8191 to +8191, or 32767

Example

OUTPUT XXX;":MACHINE1:SLIST:OSTATE?"

OTAG

Command

:MACHine{1|2}:SLISt:OTAG

<time_value>|<state_value>}

The OTAG command specifies the tag value on which the O Marker should be

placed. The tag value is time when time tagging is on, or states when state

tagging is on. If the data is not valid tagged data, no action is performed.

<time_value> real number

<state_value> integer

Example

:OUTPUT XXX;":MACHINE1:SLIST:OTAG 40.0E−6"

17–13

Download from Www.Somanuals.com. All Manuals Search And Download.

SLISt Subsystem

OVERlay

Query

:MACHine{1|2}:SLISt:OTAG?

The OTAG query returns the O Marker position in time when time tagging is

on or in states when state tagging is on, regardless of whether the marker

was positioned in time or through a pattern search. If data is not valid, the

query returns 9.9E37 for time tagging, or returns 32767 for state tagging.

[:MACHine{1|2}:SLISt:OTAG] {time_value>|<state_value>}<NL>

Returned Format

<time_value> real number

<state_value> integer

Example

OUTPUT XXX;":MACHINE1:SLIST:OTAG?"

OVERlay

Command

:MACHine{1|2}:SLISt:OVERlay

<col_num>,<module_num>,

MACHine{1|2},<label_name>

The OVERlay command allows you to add time-correlated labels from other

modules or machines to the state listing.

<col_num> integer from 1 to 61

<Module_num> integer 1 through 10 (2 through 10 unused)

<label_name> string of up to 6 alphanumeric characters

Example

OUTPUT XXX;":MACHINE1:SLIST:OVERlay,25,5,MACHINE2,’DATA’"

17–14

Download from Www.Somanuals.com. All Manuals Search And Download.

SLISt Subsystem

REMove

Command

:MACHine{1|2}:SLISt:REMove

The REMove command removes all labels, except the leftmost label, from

the listing menu.

Example

OUTPUT XXX;":MACHINE1:SLIST:REMOVE"

RUNTil

Command

:MACHine{1|2}:SLISt:RUNTil <run_until_spec>

The RUNTil (run until) command allows you to define a stop condition when

the trace mode is repetitive. Specifying OFF causes the analyzer to make

runs until either the display’s STOP field is touched, or, when the STOP

command is issued.

There are four conditions based on the time between the X and O markers.

Using this difference in the condition is effective only when time tags have

been turned on (see the TAG command in the STRace subsystem). These

four conditions are as follows:

The difference is less than (LT) some value.

•

The difference is greater than (GT) some value.

•

The difference is inside some range (INRange).

•

The difference is outside some range (OUTRange).

•

End points for the INRange and OUTRange should be at least 8 ns apart since

this is the minimum time resolution of the time tag counter.

17–15

Download from Www.Somanuals.com. All Manuals Search And Download.

SLISt Subsystem

RUNTil

There are two conditions which are based on a comparison of the acquired

state data and the compare data image. The analyzer can run until one of the

following conditions is true:

Every channel of every label has the same value (EQUal).

•

Any channel of any label has a different value (NEQual).

•

The RUNTil instruction (for state analysis) is available in both the SLISt and

COMPare subsystems.

<run_until_ {OFF|LT,<value>|GT,<value>|INRange,<value>,<value>

spec> |OUTRange,<value>,<value>|EQUal|NEQual}

<value>

real number from −9E9 to +9E9

Example

OUTPUT XXX;":MACHINE1:SLIST:RUNTIL GT,800.0E−6"

Query

:MACHine{1|2}:SLISt:RUNTil?

The RUNTil query returns the current stop criteria.

Returned Format

[:MACHine{1|2}:SLISt:RUNTil] <run_until_spec><NL>

Example

OUTPUT XXX;":MACHINE1:SLIST:RUNTIL?"

17–16

Download from Www.Somanuals.com. All Manuals Search And Download.

SLISt Subsystem

TAVerage

Query

:MACHine{1|2}:SLISt:TAVerage?

The TAVerage query returns the value of the average time between the X

and O Markers. If the number of valid runs is zero, the query returns 9.9E37.

Valid runs are those where the pattern search for both the X and O markers

was successful, resulting in valid delta-time measurements.

Returned Format:

[:MACHine{1|2}:SLISt:TAVerage] <time_value><NL>

<time_value> real number

Example

OUTPUT XXX;":MACHINE1:SLIST:TAVERAGE?"

TMAXimum

Query

:MACHine{1|2}:SLISt:TMAXimum?

The TMAXimum query returns the value of the maximum time between the X

and O Markers. If data is not valid, the query returns 9.9E37.

[:MACHine{1|2}:SLISt:TMAXimum] <time_value><NL>

Returned Format

<time_value> real number

Example

OUTPUT XXX;":MACHINE1:SLIST:TMAXIMUM?"

17–17

Download from Www.Somanuals.com. All Manuals Search And Download.

SLISt Subsystem

TMINimum

Query

:MACHine{1|2}:SLISt:TMINimum?

The TMINimum query returns the value of the minimum time between the X

and O Markers. If data is not valid, the query returns 9.9E37.

[:MACHine{1|2}:SLISt:TMINimum] <time_value><NL>

Returned Format

<time_value> real number

Example:

OUTPUT XXX;":MACHINE1:SLIST:TMINIMUM?"

VRUNs

Query

:MACHine{1|2}:SLISt:VRUNs?

The VRUNs query returns the number of valid runs and total number of runs

made. Valid runs are those where the pattern search for both the X and O

markers was successful resulting in valid delta time measurements.

[:MACHine{1|2}:SLISt:VRUNs] <valid_runs>,<total_runs><NL>

Returned Format

<valid_runs> zero or positive integer

<total_runs> zero or positive integer

Example:

OUTPUT XXX;":MACHINE1:SLIST:VRUNS?"

17–18

Download from Www.Somanuals.com. All Manuals Search And Download.

SLISt Subsystem

XOTag

Query

:MACHine{1|2}:SLISt:XOTag?

The XOTag query returns the time from the X to O markers when the marker

mode is time or number of states from the X to O markers when the marker

mode is state. If there is no data in the time mode the query returns 9.9E37.

If there is no data in the state mode, the query returns 32767.

Returned Format

[:MACHine{1|2}:SLISt:XOTag] {<XO_time>|<XO_states>}<NL>

<XO_time> real number

<XO_states> integer

Example

OUTPUT XXX;":MACHINE1:SLIST:XOTAG?"

XOTime

Query

:MACHine{1|2}:SLISt:XOTime?

The XOTime query returns the time from the X to O markers when the

marker mode is time or number of states from the X to O markers when the

marker mode is state. If there is no data in the time mode the query returns

9.9E37. If there is no data in the state mode, the query returns 32767.

[:MACHine{1|2}:SLISt:XOTime] {<XO_time>|<XO_states>}<NL>

Returned Format

<XO_time> real number

<XO_states> integer

Example

OUTPUT XXX;":MACHINE1:SLIST:XOTIME?"

17–19

Download from Www.Somanuals.com. All Manuals Search And Download.

SLISt Subsystem

XPATtern

Command

:MACHine{1|2}:SLISt:XPATtern <label_name>,

<label_pattern>

The XPATtern command allows you to construct a pattern recognizer term

for the X Marker which is then used with the XSEarch criteria when moving

the marker on patterns. Since this command deals with only one label at a

time, a complete specification could require several invocations.

When the value of a pattern is expressed in binary, it represents the bit

values for the label inside the pattern recognizer term. In whatever base is

used, the value must be between 0 and 2³²− 1, since a label may not have

more than 32 bits. Because the <label_pattern>parameter may contain

don’t cares, it is handled as a string of characters rather than a number.

<label_name> string of up to 6 alphanumeric characters

<label_pattern> "{#B{0|1|X} . . . |

#Q{0|1|2|3|4|5|6|7|X} . . . |

#H{0|1|2|3|4|5|6|7|8|9|A|B|C|D|E|F|X} . . . |

{0|1|2|3|4|5|6|7|8|9} . . . }"

Examples

OUTPUT XXX;":MACHINE1:SLIST:XPATTERN ’DATA’,’255’ "

OUTPUT XXX;":MACHINE1:SLIST:XPATTERN ’ABC’,’#BXXXX1101’ "

Query

:MACHine{1|2}:SLISt:XPATtern? <label_name>

The XPATtern query returns the pattern specification for a given label name.

Returned Format

[:MACHine{1|2}:SLISt:XPATtern]

<label_name>,<label_pattern><NL>

Example

OUTPUT XXX;":MACHINE1:SLIST:XPATTERN? ’A’"

17–20

Download from Www.Somanuals.com. All Manuals Search And Download.

SLISt Subsystem

XSEarch

Command

:MACHine{1|2}:SLISt:XSEarch <occurrence>,<origin>

The XSEarch command defines the search criteria for the X Marker, which is

then with associated XPATtern recognizer specification when moving the

markers on patterns. The origin parameter tells the Marker to begin a search

with the trigger or with the start of data. The occurrence parameter

determines which occurrence of the XPATtern recognizer specification,

relative to the origin, the marker actually searches for. An occurrence of 0

places a marker on the selected origin.

integer from −8191 to +8191

<origin> {TRIGger|STARt}

Example

OUTPUT XXX;":MACHINE1:SLIST:XSEARCH +10,TRIGGER"

Query

:MACHine{1|2}:SLISt:XSEarch?

The XSEarch query returns the search criteria for the X marker.

Returned Format

[:MACHine{1|2}:SLISt:XSEarch] <occurrence>,<origin><NL>

Example

OUTPUT XXX;":MACHINE1:SLIST:XSEARCH?"

17–21

Download from Www.Somanuals.com. All Manuals Search And Download.

SLISt Subsystem

XSTate

Query

:MACHine{1|2}:SLISt:XSTate?

The XSTate query returns the line number in the listing where the X marker

resides (−8191 to +8191). If data is not valid, the query returns 32767.

[:MACHine{1|2}:SLISt:XSTate] <state_num><NL>

Returned Format

<state_num>

integer from −8191 to +8191, or 32767

Example

OUTPUT XXX;":MACHINE1:SLIST:XSTATE?"

XTAG

Command

:MACHine{1|2}:SLISt:XTAG

{<time_value>|<state_value>}

The XTAG command specifies the tag value on which the X Marker should be

placed. The tag value is time when time tagging is on or states when state

tagging is on. If the data is not valid tagged data, no action is performed.

<time_value> real number

<state_value> integer

Example

OUTPUT XXX;":MACHINE1:SLIST:XTAG 40.0E−6"

17–22

Download from Www.Somanuals.com. All Manuals Search And Download.

SLISt Subsystem

XTAG

Query

:MACHine{1|2}:SLISt:XTAG?

The XTAG query returns the X Marker position in time when time tagging is

on or in states when state tagging is on, regardless of whether the marker

was positioned in time or through a pattern search. If data is not valid tagged

data, the query returns 9.9E37 for time tagging, or retruns 32767 for state

tagging.

Returned Format

[:MACHine{1|2}:SLISt:XTAG] {<time_value>|<state_value>}<NL>

Example

OUTPUT XXX;":MACHINE1:SLIST:XTAG?"

17–23

Download from Www.Somanuals.com. All Manuals Search And Download.

17–24

Download from Www.Somanuals.com. All Manuals Search And Download.

SWAVeform Subsystem

Download from Www.Somanuals.com. All Manuals Search And Download.

Introduction

The commands in the State Waveform subsystem allow you to

configure the display so that you can view state data as waveforms on

up to 96 channels identified by label name and bit number. The 11

commands are analogous to their counterparts in the Timing

Waveform subsystem. However, in this subsystem the x-axis is

restricted to representing only samples (states), regardless of

whether time tagging is on or off. As a result, the only commands

which can be used for scaling are DELay and RANge.

The way to manipulate the X and O markers on the Waveform display

is through the State Listing (SLISt) subsystem. Using the marker

commands from the SLISt subsystem will affect the markers on the

Waveform display.

The commands in the SWAVeform subsystem are:

• ACCumulate

• ACQuisition

• CENter

• CLRPattern

• CLRStat

• DELay

• INSert

• RANGe

• REMove

• TAKenbranch

• TPOSition

18–2

Download from Www.Somanuals.com. All Manuals Search And Download.

SWAVeform Subsystem

Figure 18-1

SWAVeform Subsystem Syntax Diagram

18–3

Download from Www.Somanuals.com. All Manuals Search And Download.

SWAVeform Subsystem

SWAVeform

Table 18-1

SWAVeform Parameter Values

Parameter

Value

number_of_samples

integer from −8191 to +8191

label_name

bit_id

string of up to 6 alphanumeric characters

{OVERlay|<bit_num>|ALL}

integer representing a label bit from 0 to 31

bit_num

range_values

integer from 10 to 5000 (representing (10 × states/Division))

{X|O|XO|TRIGger}

mark_type

percent

integer from 0 to 100

SWAVeform

Selector

:MACHine{1|2}:SWAVeform

The SWAVeform (State Waveform) selector is used as part of a compound

header to access the settings in the State Waveform menu. It always follows

the MACHine selector because it selects a branch directly below the

MACHine level in the command tree.

Example

OUTPUT XXX;":MACHINE2:SWAVEFORM:RANGE 40"

18–4

Download from Www.Somanuals.com. All Manuals Search And Download.

SWAVeform Subsystem

ACCumulate

Command

:MACHine{1|2}:SWAVeform:ACCumulate

{{ON|1}|{OFF|0}}

The ACCumulate command allows you to control whether the waveform

display gets erased between individual runs or whether subsequent

waveforms are allowed to be displayed over the previous waveforms.

Example

OUTPUT XXX;":MACHINE1:SWAVEFORM:ACCUMULATE ON"

Query

:MACHine{1|2}:SWAVeform:ACCumulate?

The ACCumulate query returns the current setting. The query always shows

the setting as the characters, "0" (off) or "1" (on).

Returned Format

[:MACHine{1|2}:SWAVeform:ACCumulate] {0|1}<NL>

Example

OUTPUT XXX;":MACHINE1:SWAVEFORM:ACCUMULATE?"

ACQuisition

Command

:MACHine{1|2}:SWAVeform:ACQuisition

{AUTOmatic|MANual}

The ACQuisition command allows you to specify the acquisition mode for the

state analyzer. The acquisition modes are automatic and manual.

Example

OUTPUT XXX;":MACHINE2:SWAVEFORM:ACQUISITION AUTOMATIC"

18–5

Download from Www.Somanuals.com. All Manuals Search And Download.

SWAVeform Subsystem

CENTer

Query

:MACHine{1|2}:SWAVeform:ACQuisition?

The ACQusition query returns the current acquisition mode.

Returned Format

[:MACHine{1|2}:SWAVeform:ACQuisition] {AUTOmatic|MANual}<NL>

Example

OUTPUT XXX;":MACHINE2:SWAVEFORM:ACQUISITION?"

CENTer

Command

:MACHine{1|2}:SWAVeform:CENTer <marker_type>

The CENTer command allows you to center the waveform display about the

specified markers. The markers are placed on the waveform in the SLISt

subsystem.

<marker_type> {X|O|XO|TRIGger}

Example

OUTPUT XXX;":MACHINE1:SWAVEFORM:CENTER X"

CLRPattern

Command

:MACHine{1|2}:SWAVeform:CLRPattern {X|O|ALL}

The CLRPattern command allows you to clear the patterns in the selected

Specify Patterns menu.

Example

OUTPUT XXX;":MACHINE1:SWAVEFORM:CLRPATTERN"

18–6

Download from Www.Somanuals.com. All Manuals Search And Download.

SWAVeform Subsystem

CLRStat

Command

:MACHine{1|2}:SWAVeform:CLRStat

The CLRStat command allows you to clear the waveform statistics without

having to stop and restart the acquisition.

Example

OUTPUT XXX;":MACHINE1:SWAVEFORM:CLRSTAT"

DELay

Command

:MACHine{1|2}:SWAVeform:DELay <number_of_samples>

The DELay command allows you to specify the number of samples between

the State trigger and the horizontal center of the screen for the waveform

display. The allowed number of samples is from −8191 to +8191.

<number_of_ integer from –8191 to +8191

samples>

Example

OUTPUT XXX;":MACHINE2:SWAVEFORM:DELAY 127"

Query

:MACHine{1|2}:SWAVeform:DELay?

The DELay query returns the current sample offset value.

Returned Format

[:MACHine{1|2}:SWAVeform:DELay] <number_of_samples><NL>

<number_of_ integer from –8191 to +8191

samples>

Example

OUTPUT XXX;":MACHINE1:SWAVEFORM:DELAY?"

18–7

Download from Www.Somanuals.com. All Manuals Search And Download.

SWAVeform Subsystem

INSert

Command

:MACHine{1|2}:SWAVeform:INSert

<label_name>,<bit_id>

The INSert command allows you to add waveforms to the state waveform

display. Waveforms are added from top to bottom on the screen. When 96

waveforms are present, inserting additional waveforms replaces the last

waveform. Bit numbers are zero based, so a label with 8 bits is referenced as

bits 0 through 7. Specifying OVERlay causes a composite waveform display

of all bits or channels for the specified label.

<label_name> string of up to 6 alphanumeric characters

<bit_id> {OVERlay|<bit_num>ALL}

<bit_num> integer representing a label bit from 0 to 31

Examples

OUTPUT XXX;":MACHINE1:SWAVEFORM:INSERT ’WAVE’, 19"

OUTPUT XXX;":MACHINE1:SWAVEFORM:INSERT ’ABC’, OVERLAY"

OUTPUT XXX;":MACH1:SWAV:INSERT ’POD1’, #B1001"

RANGe

Command

:MACHine{1|2}:SWAVeform:RANGe <number_of_samples>

The RANGe command allows you to specify the number of samples across

the screen on the State Waveform display. It is equivalent to ten times the

states per division setting (states/Div) on the front panel. A number between

10 and 5000 may be entered.

<number_of_ integer from 10 to 5000

samples>

Example

OUTPUT XXX;":MACHINE2:SWAVEFORM:RANGE 80"

18–8

Download from Www.Somanuals.com. All Manuals Search And Download.

SWAVeform Subsystem

REMove

Query

:MACHine{1|2}:SWAVeform:RANGe?

The RANGe query returns the current range value.

Returned Format

[:MACHine{1|2}:SWAVeform:RANGe] <number_of_samples><NL>

<number_of_ integer from 10 to 5000

samples>

Example

OUTPUT XXX;":MACHINE2:SWAVEFORM:RANGE?"

REMove

Command

:MACHine{1|2}:SWAVeform:REMove

The REMove command allows you to clear the waveform display before

building a new display.

Example

OUTPUT XXX;":MACHINE1:SWAVEFORM:REMOVE"

TAKenbranch

Command

:MACHine{1|2}:SWAVeform:TAKenbranch

{STORe|NOSTore}

The TAKenbranch command allows you to control whether the states that

cause branching are stored or not stored. This command is only available

when the acquisition mode is set to manual.

Example

OUTPUT XXX;":MACHINE2:SWAVEFORM:TAKENBRANCH STORE"

18–9

Download from Www.Somanuals.com. All Manuals Search And Download.

SWAVeform Subsystem

TPOSition

Query

:MACHine{1|2}:SWAVeform:TAKenbranch?

The TAKenbranch query returns the current setting.

Returned Format

[:MACHine{1|2}:SWAVeform:TAKenbranch] {STORe|NOSTore}<NL>

Example

OUTPUT XXX;":MACHINE2:SWAVEFORM:TAKENBRANCH?"

TPOSition

Command

:MACHine{1|2}:SWAVeform:TPOSition

{STARt|CENTer|END|POSTstore,<percent>}

The TPOSition command allows you to control where the trigger point is

placed. The trigger point can be placed at the start, center, end, or at a

percentage of post store. The post store option is the same as the User

Defined option when setting the trigger point from the front panel.

The TPOSition command is only available when the acquisition mode is set to

manual.

<percent> integer from 1 to 100

Example

OUTPUT XXX;":MACHINE2:SWAVEFORM:TPOSITION CENTER"

18–10

Download from Www.Somanuals.com. All Manuals Search And Download.

SWAVeform Subsystem

TPOSition

Query

:MACHine{1|2}:SWAVeform:TPOSition?

The TPOSition query returns the current trigger setting.

Returned Format

[:MACHine{1|2}:SWAVeform:TPOSition]

{STARt|CENTer|END|POSTstore,

<percent> integer from 1 to 100

Example

OUTPUT XXX;":MACHINE2:SWAVEFORM:TPOSition?"

18–11

Download from Www.Somanuals.com. All Manuals Search And Download.

18–12

Download from Www.Somanuals.com. All Manuals Search And Download.

SCHart Subsystem

Download from Www.Somanuals.com. All Manuals Search And Download.

Introduction

The State Chart subsystem provides the commands necessary for

programming the Chart display of 1660A-series logic analyzers. The

commands allow you to build charts of label activity, using data

normally found in the Listing display. The chart’s Y-axis is used to

show data values for the label of your choice. The X-axis can be used

in two different ways. In one, the X-axis represents states (shown as

rows in the State Listing display). In the other, the X-axis represents

the data values for another label. When states are plotted along the

X-axis, X and O markers are available. Because the State Chart

display is simply an alternative way of looking at the data in the State

Listing, the X and O markers can be manipulated through the SLISt

subsystem. Because the programming commands do not force the

menus to switch, you can position the markers in the SLISt subsystem

and see the effects in the State Chart display.

The commands in the SCHart subsystem are:

ACCumulate

•

HAXis

•

VAXis

•

19–2

Download from Www.Somanuals.com. All Manuals Search And Download.

SCHart Subsystem

Figure 19-1

SCHart Subsystem Syntax Diagram

19–3

Download from Www.Somanuals.com. All Manuals Search And Download.

SCHart Subsystem

SCHart

Table 19-1

SCHart Parameter Values

Parameter

Values

state_low_value

state_high_value

label_name

integer from –8191 to +8191

integer from <state_low_value> to +8191

string of up to 6 alphanumeric characters

string from 0 to 2³²− 1 (#HFFFF)

label_low_value

string from <label_low_value> to 2³²− 1 (#HFFFF)

string from 0 to 2³²− 1 (#HFFFF)

label_high_value

low_value

string from low_value to 2³²− 1 (#HFFFF)

high_value

SCHart

Selector

:MACHine{1|2}:SCHart

The SCHart selector is used as part of a compound header to access the

settings found in the State Chart menu. It always follows the MACHine

selector because it selects a branch below the MACHine level in the

command tree.

Example

OUTPUT XXX;":MACHINE1:SCHART:VAXIS ’A’, ’0’, ’9’"

ACCumulate

Command

:MACHine{1|2}:SCHart:ACCumulate {{ON|1}|{OFF|0}}

The ACCumulate command allows you to control whether the chart display

gets erased between each individual run or whether subsequent waveforms

are allowed to be displayed over the previous waveforms.

19–4

Download from Www.Somanuals.com. All Manuals Search And Download.

SCHart Subsystem

HAXis

Example

OUTPUT XXX;":MACHINE1:SCHART:ACCUMULATE OFF"

Query

:MACHine{1|2}:SCHart:ACCumulate?

The ACCumulate query returns the current setting. The query always shows

the setting as the character "0" (off) or "1" (on).

Returned Format

[:MACHine{1|2}:SCHart:ACCumulate] {0|1}<NL>

Example

OUTPUT XXX;":MACHINE1:SCHART:ACCUMULATE?"

HAXis

Command

:MACHine{1|2}:SCHart:HAXis {STAtes,

<state_low_value>,<state_high_value>|<label_name>,

<label_low_value>,<label_high_value>}

The HAXis command allows you to select whether states or a label’s values

will be plotted on the horizontal axis of the chart. The axis is scaled by

specifying the high and low values.

The shortform for STATES is STA. This is an intentional deviation from the

normal truncation rule.

19–5

Download from Www.Somanuals.com. All Manuals Search And Download.

SCHart Subsystem

HAXis

<state_low_

value>

integer from −8191 to +8191

<state_high_ integer from <state_low_value>to +8191

value>

<label_name> string of up to 6 alphanumeric characters

string from 0 to 2³²−1 (#HFFFF)

<label_low_

value>

<label_high_ string from <label_low_value>to 2³²–1 (#HFFFF)

value>

Examples

OUTPUT XXX;":MACHINE1:SCHART:HAXIS STATES, −100, 100"

OUTPUT XXX;":MACHINE1:SCHART:HAXIS ’READ’, ’−511’, ’511’"

Query

:MACHine{1|2}:SCHart:HAXis?

The HAXis query returns the current horizontal axis label and scaling.

Returned Format

[:MACHine{1|2}:SCHart:HAXis] {STAtes,<state_low_value>,

<state_high_value>|<label_name>,<label_low_value>,

<label_high_value>}

Example

OUTPUT XXX;":MACHINE1:SCHART:HAXIS?"

19–6

Download from Www.Somanuals.com. All Manuals Search And Download.

SCHart Subsystem

VAXis

Command

:MACHine{1|2}:SCHart:VAXis

<label_name>,<low_value>,<high_value>

The VAXis command allows you to choose which label will be plotted on the

vertical axis of the chart and scale the vertical axis by specifying the high

value and low value.

<label_name> string of up to 6 alphanumeric characters

string from 0 to 2³²−1 (#HFFFF)

<low_value>

<high_value>

string from <low_value>to 2³²−1 (#HFFFF)

Examples

OUTPUT XXX;":MACHINE2:SCHART:VAXIS ’SUM1’, ’0’, ’99’"

OUTPUT XXX;":MACHINE1:SCHART:VAXIS ’BUS’, ’#H00FF’, ’#H0500’"

Query

:MACHine{1|2}:SCHart:VAXis?

The VAXis query returns the current vertical axis label and scaling.

Returned Format

[:MACHine{1|2}:SCHart:VAXis] <label_name>,<low_value>,

<high_value><NL>

Example

OUTPUT XXX;":MACHINE1:SCHART:VAXIS?"

19–7

Download from Www.Somanuals.com. All Manuals Search And Download.

19–8

Download from Www.Somanuals.com. All Manuals Search And Download.

COMPare Subsystem

Download from Www.Somanuals.com. All Manuals Search And Download.

Introduction

Commands in the state COMPare subsystem provide the ability to do a

bit-by-bit comparison between the acquired state data listing and a

compare data image. The commands are:

• CLEar

• CMASk

• COPY

• DATA

• FIND

• LINE

• MENU

• RANGe

• RUNTil

• SET

20–2

Download from Www.Somanuals.com. All Manuals Search And Download.

COMPare Subsystem

Figure 20-1

COMPare Subsystem Syntax Diagram

20–3

Download from Www.Somanuals.com. All Manuals Search And Download.

COMPare Subsystem

COMPare

Table 20-1

Compare Parameter Values

Parameter

Values

label_name

care_spec

string of up to 6 characters

string of characters "{*|.}..."

care

don’t care

line_num

integer from –8191 to +8191

data_pattern

"{B{0|1|X} . . . |

#Q{0|1|2|3|4|5|6|7|X} . . . |

#H{0|1|2|3|4|5|6|7|8|9|A|B|C|D|E|F|X} .

. . |

{0|1|2|3|4|5|6|7|8|9} . . . }"

difference_occurence

start_line

integer from 1 to 8192

integer from –8191 to +8191

integer from <start_line>to +8191

stop_line

COMPare

Selector

:MACHine{1|2}:COMPare

The COMPare selector is used as part of a compound header to access the

settings found in the Compare menu. It always follows the MACHine selector

because it selects a branch directly below the MACHine level in the command

tree.

Example

OUTPUT XXX;":MACHINE1:COMPARE:FIND? 819"

20–4

Download from Www.Somanuals.com. All Manuals Search And Download.

COMPare Subsystem

CLEar

Command

:MACHine{1|2}:COMPare:CLEar

The CLEar command clears all "don’t cares" in the reference listing and

replaces them with zeros except when the CLEar command immediately

follows the SET command (see SET command).

Example

OUTPUT XXX;":MACHINE2:COMPARE:CLEAR"

CMASk

Command

:MACHine{1|2}:COMPare:CMASk

<label_name>,<care_spec>

The CMASk (Compare Mask) command allows you to set the bits in the

channel mask for a given label in the compare listing image to "compares" or

"don’t compares."

<label_name> A string of up to 6 alphanumeric characters

<care_spec> A string of characters "{*|.}..." (32 characters maximum)

<*> An indicator that tells the logic analyzer that it cares about this bit.

<.> An indicator that tells the logic analyzer that it does not care about this bit

(don’t care).

Example

OUTPUT XXX;":MACHINE2:COMPARE:CMASK ’DATA’, ’*.**..**’"

20–5

Download from Www.Somanuals.com. All Manuals Search And Download.

COMPare Subsystem

COPY

Query

:MACHine{1|2}:COMPare:CMASk <label_name>?

The CMASk query returns the state of the bits in the channel mask for a

given label in the compare listing image.

Returned Format

[:MACHine{1|2}:COMPare:CMASk] <label_name>,<care_spec>

<label name> A string of up to 6 alphanumeric characters

<care_spec> A string of characters "{*|.}..." (32 characters maximum)

<*> An indicator that tells the logic analyzer that it cares about this bit.

<.> An indicator that tells the logic analyzer that it does not care about this bit

(don’t care).

Example

OUTPUT XXX;":MACHINE2:COMPARE:CMASK ’DATA’?"

COPY

Command

:MACHine{1|2}:COMPare:COPY

The COPY command copies the current acquired State Listing for the

specified machine into the Compare Reference template. It does not affect

the compare range or channel mask settings.

Example

OUTPUT XXX;":MACHINE2:COMPARE:COPY"

20–6

Download from Www.Somanuals.com. All Manuals Search And Download.

COMPare Subsystem

DATA

Command

:MACHine{1|2}:COMPare:DATA {<label_name>,

<line_num>,<data_pattern>|<line_num>,

<data_pattern>[, <data_pattern>]... }

The DATA command allows you to edit the compare listing image for a given

label and state row. When DATA is sent to an instrument where no compare

image is defined (such as at power-up) all other data in the image is set to

don’t cares.

Not specifying the <label_name>parameter allows you to write data

patterns to more than one label for the given line number. The first pattern

is placed in the left-most label, with the following patterns being placed in a

left-to-right fashion (as seen on the Compare display). Specifying more

patterns than there are labels simply results in the extra patterns being

ignored.

Because don’t cares (Xs) are allowed in the data pattern, it must always be

expressed as a string. You may still use different bases; although, don’t cares

cannot be used in a decimal number.

<label_name> A string of up to 6 alphanumeric characters

<line_num> An integer from –8191 to +8191

<data pattern> A string in one of the following forms:

"{B{0|1|X} . . . |

#Q{0|1|2|3|4|5|6|7|X} . . . |

#H{0|1|2|3|4|5|6|7|8|9|A|B|C|D|E|F|X} . . . |

{0|1|2|3|4|5|6|7|8|9} . . . }"

Examples

OUTPUT XXX;":MACHINE2:COMPARE:DATA ’CLOCK’, 42, ’#B011X101X’"

OUTPUT XXX;":MACHINE2:COMPARE:DATA ’OUT3’, 0, ’#HFF40’"

OUTPUT XXX;":MACHINE1:COMPARE:DATA 129, ’#BXX00’, ’#B1101’,

’#B10XX’"

OUTPUT XXX;":MACH2:COMPARE:DATA −511, ’4’, ’64’, ’16’, 256’,

’8’, ’16’"

20–7

Download from Www.Somanuals.com. All Manuals Search And Download.

COMPare Subsystem

DATA

Query

:MACHine{1|2}:COMPare:DATA?

<label_name>,<line_num>

The DATA query returns the value of the compare listing image for a given

label and state row.

Returned Format

[:MACHine{1|2}:COMPare:DATA] <label_name>,<line_num>,

<data_pattern><NL>

<label_name> A string of up to 6 alphanumeric characters

<line_num> An integer from –8191 to +8191

<data pattern> A string in one of the following forms:

"{B{0|1|X} . . . |

#Q{0|1|2|3|4|5|6|7|X} . . . |

#H{0|1|2|3|4|5|6|7|8|9|A|B|C|D|E|F|X} . . . |

{0|1|2|3|4|5|6|7|8|9} . . . }"

Example

10 DIM Label$[6], Response$[80]

15 PRINT "This program shows the values for a signal’s

Compare listing"

20 INPUT "Enter signal label: ", Label$

25 OUTPUT XXX;":SYSTEM:HEADER OFF" !Turn headers off (from

responses)

30 OUTPUT XXX;":MACHINE2:COMPARE:RANGE?"

35 ENTER XXX; First, Last

!Read in the range’s end-points

40 PRINT "LINE ", "VALUE of "; Label$

45 FOR State = First TO Last

state

!Print compare value for each

50 OUTPUT XXX;":MACH2:COMPARE:DATA? ’" & Label$ & "’," &

VAL$(State)

55 ENTER XXX; Response$

60 PRINT State, Response$

65 NEXT State

70 END

20–8

Download from Www.Somanuals.com. All Manuals Search And Download.

COMPare Subsystem

FIND

Query

:MACHine{1|2}:COMPare:FIND?

<difference_occurrence>

The FIND query is used to get the line number of a specified difference

occurence (first, second, third, etc) within the current compare range, as

dictated by the RANGe command (see page 20-11). A difference is counted

for each line where at least one of the current labels has a discrepancy

between its acquired state data listing and its compare data image.

Invoking the FIND query updates both the Listing and Compare displays so

that the line number returned is in the center of the screen.

Returned Format

[:MACHine{1|2}:COMPare:FIND] <difference_occurrence>,

<line_number><NL>

<difference_ integer from 1 to 8192

occurrence>

<line_number> integer from –8191 to +8191

Example

OUTPUT XXX;":MACHINE2:COMPARE:FIND? 26"

20–9

Download from Www.Somanuals.com. All Manuals Search And Download.

COMPare Subsystem

LINE

Command

:MACHine{1|2}:COMPare:LINE <line_num>

The LINE command allows you to center the compare listing data about a

specified line number.

<line_num> An integer from –8191 to +8191

Example

OUTPUT XXX;":MACHINE2:COMPARE:LINE –511"

Query

:MACHine{1|2}:COMPare:LINE?

The LINE query returns the current line number specified.

Returned Format

[:MACHine{1|2}:COMPare:LINE] <line_num>}<NL>

<line_num> An integer from –8191 to +8191

Example

OUTPUT XXX;":MACHINE4:COMPARE:LINE?"

Command

:MACHine{1|2}:COMPare:MENU {REFerence|DIFFerence}

The MENU command allows you to display the reference or the difference

listings in the Compare menu.

Example

OUTPUT XXX;":MACHINE2:COMPARE:MENU REFERENCE"

20–10

Download from Www.Somanuals.com. All Manuals Search And Download.

COMPare Subsystem

RANGe

Command

:MACHine{1|2}:COMPare:RANGe

{FULL|PARTial,<start_line>,<stop_line>}

The RANGe command allows you to define the boundaries for the

comparison. The range entered must be a subset of the lines in the acquire

memory.

<start_line> integer from –8191 to +8191

<stop_line> integer from <start_line> to +8191

Examples

OUTPUT XXX;":MACHINE2:COMPARE:RANGE PARTIAL, –511, 512"

OUTPUT XXX;":MACHINE2:COMPARE:RANGE FULL"

Query

:MACHine{1|2}:COMPare:RANGe?

The RANGe query returns the current boundaries for the comparison.

Returned Format

[:MACHine{1|2}:COMPare:RANGe] {FULL|PARTial,<start_line>,

<stop_line>}<NL>

<start_line> integer from –8191 to +8191

<stop_line> integer from <start_line> to +8191

Example

OUTPUT 707;":MACHINE1:COMPARE:RANGE?"

20–11

Download from Www.Somanuals.com. All Manuals Search And Download.

COMPare Subsystem

RUNTil

Command

:MACHine{1|2}:COMPare:RUNTil {OFF| LT,<value>|GT,

<value>|INRange,<value>,<value>|OUTRange,<value>,<v

alue>|EQUal|NEQual}

The RUNTil (run until) command allows you to define a stop condition when

the trace mode is repetitive. Specifying OFF causes the analyzer to make

runs until either the display’s STOP field is touched or the STOP command is

issued.

There are four conditions based on the time between the X and O markers.

Using this difference in the condition is effective only when time tags have

been turned on (see the TAG command in the STRace subsystem). These

four conditions are as follows:

The difference is less than (LT) some value.

•

The difference is greater than (GT) some value.

•

The difference is inside some range (INRange).

•

The difference is outside some range (OUTRange).

•

End points for the INRange and OUTRange should be at least 8 ns apart since

this is the minimum time resolution of the time tag counter.

There are two conditions which are based on a comparison of the acquired

state data and the compare data image. You can run until one of the

following conditions is true:

Every channel of every label has the same value (EQUal).

•

Any channel of any label has a different value (NEQual).

•

The RUNTil instruction (for state analysis) is available in both the SLISt and

COMPare subsystems.

<value>

real number from −9E9 to +9E9

20–12

Download from Www.Somanuals.com. All Manuals Search And Download.

COMPare Subsystem

SET

Example

OUTPUT XXX;":MACHINE2:COMPARE:RUNTIL EQUAL"

Query

:MACHine{1|2}:COMPare:RUNTil?

The RUNTil query returns the current stop criteria for the comparison when

running in repetitive trace mode.

Returned Format

[:MACHine{1|2}:COMPare:RUNTil] {OFF| LT,<value>|GT,<value>l

INRange,<value>,<value>|OUTRange,<value>,<value>|EQUal|NEQual}

<NL>

<value>

real number from −9E9 to +9E9

Example

OUTPUT XXX;":MACHINE2:COMPARE:RUNTIL?"

SET

Command

:MACHine{1|2}:COMPare:SET

The SET command sets every state in the reference listing to "don’t cares." If

you send the SET command by mistake you can immediately send the CLEar

command to restore the previous data. This is the only time the CLEar

command will not replace "don’t cares" with zeros.

Example

OUTPUT XXX;":MACHINE2:COMPARE:SET"

20–13

Download from Www.Somanuals.com. All Manuals Search And Download.

20–14

Download from Www.Somanuals.com. All Manuals Search And Download.

TFORmat Subsystem

Download from Www.Somanuals.com. All Manuals Search And Download.

Introduction

The TFORmat subsystem contains the commands available for the

Timing Format menu in the 1660-series logic analyzers. These

commands are:

• ACQMode

• LABel

• REMove

• THReshold

21–2

Download from Www.Somanuals.com. All Manuals Search And Download.

TFORmat Subsystem

Figure 21-1

TFORmat Subsystem Syntax Diagram

21–3

Download from Www.Somanuals.com. All Manuals Search And Download.

TFORmat Subsystem

TFORmat

Table 21-1

TFORmat Paramter Values

Parameter

Values

size

{FULL|HALF}

<N>

{1|2|3|4|5|6|7|8}

string of up to 6 alphanumeric characters

{POSitive|NEGative}

name

polarity

pod_specification

format (integer from 0 to 65535) for a pod (pods are

assigned in decreasing order)

value

voltage (real number) −6.00 to +6.00

TFORmat

Selector

:MACHine{1|2}:TFORmat

The TFORmat selector is used as part of a compound header to access those

settings normally found in the Timing Format menu. It always follows the

MACHine selector because it selects a branch directly below the MACHine

level in the language tree.

Example

OUTPUT XXX;":MACHINE1:TFORMAT:ACQMODE?"

21–4

Download from Www.Somanuals.com. All Manuals Search And Download.

TFORmat Subsystem

ACQMode

Command

:MACHine{1|2}:TFORmat:ACQMode {TRANSitional

<size>|CONVentional <size>|GLITch}

The ACQMode (acquisition mode) command allows you to select the

acquisition mode for the timing analyzer. The options are:

conventional mode at full-channel 250 MHz

•

conventional mode at half-channel 500 Mhz

•

transitional mode at full-channel 125 MHz

•

transitional mode at half-channel 250 MHz

•

glitch mode.

•

<size> {FULL|HALF}

Example

OUTPUT XXX;":MACHINE2:TFORMAT:ACQMODE TRANSITIONAL HALF"

Query

:MACHine{1|2}:TFORmat:ACQMode?

The ACQMode query returns the current acquisition mode.

Returned Format

[:MACHine{1|2}:TFORmat:ACQMode] {TRANSitional

<size>|CONVentional <size>|GLITch}<NL>

<size> {FULL|HALF}

Example

OUTPUT XXX;":MACHINE2:TFORMAT:ACQMODE?"

21–5

Download from Www.Somanuals.com. All Manuals Search And Download.

TFORmat Subsystem

LABel

Command

:MACHine{1|2}:Tformat:LABel <name>,[<polarity>,

<clock_bits>, <upper_bits>, <lower_bits>

[,<upper_bits>,<lower_bits>]...]

The LABel command allows you to specify polarity and to assign channels to

new or existing labels. If the specified label name does not match an existing

label name, a new label will be created.

The order of the pod-specification parameters is significant. The first one

listed will match the highest numbered pod assigned to the machine you’re

using. Each pod specification after that is assigned to the next highest

numbered pod. This way they match the left-to-right descending order of the

pods you see on the Format display. Not including enough pod specifications

results in the lowest numbered pods being assigned a value of zero (all

channels excluded). If you include more pod specifications than there are

pods for that machine, the extra ones will be ignored. However, an error is

reported anytime more than 13 pod specifications are listed.

The polarity can be specified at any point after the label name.

Because pods contain 16 channels, the format value for a pod must be

between 0 and 65535 (2¹⁶−1). When giving the pod assignment in binary

(base 2), each bit will correspond to a single channel. A "1" in a bit position

means the associated channel in that pod is assigned to that pod and bit. A

"0" in a bit position means the associated channel in that pod is excluded

from the label. For example, assigning #B1111001100 is equivalent to

entering "......****..**.." from the front panel.

A label can not have a total of more than 32 channels assigned to it.

<name> string of up to 6 alphanumeric characters

<polarity> {POSitive|NEGative}

<clock_bits> format (integer from 0 to 63) for a clock (clocks are assigned in decreasing

order)

<upper_bits> format (integer from 0 to 65535) for a pod (pods are assigned in decreasing

order)

<lower_bits> format (integer from 0 to 65535) for a pod (pods are assigned in decreasing

order)

21–6

Download from Www.Somanuals.com. All Manuals Search And Download.

TFORmat Subsystem

REMove

Examples

OUTPUT XXX;":MACHINE2:TFORMAT:LABEL ’STAT’, POSITIVE,

0,127,40312"

OUTPUT XXX;":MACHINE2:TFORMAT:LABEL ’SIG 1’,

#B11,#B0000000011111111,

#B0000000000000000 "

Query

:MACHine{1|2}:Tformat:LABel? <name>

The LABel query returns the current specification for the selected (by name)

label. If the label does not exist, nothing is returned. Numbers are always

returned in decimal format.

Returned Format

[:MACHine{1|2}:Tformat:LABel] <name>,<polarity>[,

<name> string of up to 6 alphanumeric characters

<polarity> {POSitive|NEGative}

Example

OUTPUT XXX;":MACHINE2:TFORMAT:LABEL? ’DATA’"

REMove

Command

:MACHine{1|2}:TFORmat:REMove {<name>|ALL}

The REMove command allows you to delete all labels or any one label

specified by name for a given machine.

<name> string of up to 6 alphanumeric characters

Examples

OUTPUT XXX;":MACHINE1:TFORMAT:REMOVE ’A’"

OUTPUT XXX;":MACHINE1:TFORMAT:REMOVE ALL"

21–7

Download from Www.Somanuals.com. All Manuals Search And Download.

TFORmat Subsystem

THReshold

Command

:MACHine{1|2}:TFORmat:THReshold<N> {TTL|ECL|<value>}

The THReshold command allows you to set the voltage threshold for a given

pod to ECL, TTL, or a specific voltage from −6.00 V to +6.00 V in 0.05 volt

increments.

<N> pod number {1|2|3|4|5|6|7|8}

<value>

voltage (real number) −6.00 to +6.00

TTL default value of +1.6 V

ECL

default value of −1.3 V

Example

OUTPUT XXX;":MACHINE1:TFORMAT:THRESHOLD1 4.0"

Query

:MACHine{1|2}:TFORmat:THReshold<N>?

The THReshold query returns the current threshold for a given pod.

Returned Format

[:MACHine{1|2}:TFORmat:THReshold<N>] <value><NL>

Example

OUTPUT XXX;":MACHINE1:TFORMAT:THRESHOLD2?"

21–8

Download from Www.Somanuals.com. All Manuals Search And Download.

TTRigger (TTRace) Subsystem

Download from Www.Somanuals.com. All Manuals Search And Download.

Introduction

The TTRigger subsystem contains the commands available for the

Timing Trigger menu in the 1660-series logic analyzers. The Timing

Trigger subsystem will also accept the TTRace selector as used in

previous 1650-series logic analyzers to eliminate the need to rewrite

programs containing TTRace as the selector keyword. The TTRigger

subsystem commands are:

• ACQuisition

• BRANch

• CLEar

• FIND

• GLEDge

• RANGe

• SEQuence

• SPERiod

• TCONtrol

• TERM

• TIMER

• TPOSition

22–2

Download from Www.Somanuals.com. All Manuals Search And Download.

TTRigger (TTRace) Subsystem

Figure 22-1

TTRigger Subsystem Syntax Diagram

22–3

Download from Www.Somanuals.com. All Manuals Search And Download.

TTRigger (TTRace) Subsystem

Figure 22-1 (continued)

TTRigger Subsystem Syntax Diagram (continued)

22–4

Download from Www.Somanuals.com. All Manuals Search And Download.

TTRigger (TTRace) Subsystem

Table 22-1

TTRigger Parameter Values

Parameter

Values

branch_qualifier

to_lev_num

integer from 1 to last level

proceed_qualifier

occurrence

number from 1 to 1048575

label_name

string of up to 6 alphanumeric characters

glitch_edge_spec

string consisting of {R|F|E|G|.} R, F, and E represents

rising, falling, either edge respectively. G represents a glitch

and a period (.)represents a don’t care.

start_pattern

stop_pattern

"{#B{0|1} . . . |

#Q{0|1|2|3|4|5|6|7} . . . |

#H{0|1|2|3|4|5|6|7|8|9|A|B|C|D|E|F} . .

. |

{0|1|2|3|4|5|6|7|8|9} . . . }"

"{#B{0|1} . . . |

#Q{0|1|2|3|4|5|6|7} . . . |

#H{0|1|2|3|4|5|6|7|8|9|A|B|C|D|E|F} . .

. |

{0|1|2|3|4|5|6|7|8|9} . . . }"

num_of_levels

lev_of_trig

integer from 1 to 10

integer from 1 to (number of existing sequence levels)

store_qualifier

state_tag_qualifier

timer_num

{1|2}

timer_value

term_id

400 ns to 500 seconds

{A|B|C|D|E|F|G|H|I|J}

pattern

"{#B{0|1|X} . . . |

#Q{0|1|2|3|4|5|6|7|X} . . . |

#H{0|1|2|3|4|5|6|7|8|9|A|B|C|D|E|F|X} .

. . |

{0|1|2|3|4|5|6|7|8|9} . . . }"

qualifier

see "Qualifier" on page 22-6

post_store

time_val

integer from 0 to 100 representing percentage

integer from 0 to 500 representing seconds

22–5

Download from Www.Somanuals.com. All Manuals Search And Download.

TTRigger (TTRace) Subsystem

Qualifier

The qualifier for the timing trigger subsystem can be terms A through J,

Timer 1 and 2, and Range 1 and 2. In addition, qualifiers can be the NOT

boolean function of terms, timers, and ranges. The qualifier can also be an

expression or combination of expressions as shown below and figure 22-2,

"Complex Qualifier," on page 22-11.

The following parameters show how qualifiers are specified in all commands

of the TTRigger subsystem that use <qualifier>.

<qualifier> {"ANYSTATE"|"NOSTATE"|"<expression>"}

<expression> {<expression1a>|<expression1b>|<expression1a> OR

<expression1b>|<expression1a> AND <expression1b>}

<expression1a> {<expression1a_term>|(<expression1a_term>[OR

<expression1a_term>]* )|(<expression1a_term>[AND

<expression1a_term>]* )}

<expression1a_ {<expression2a>|<expression2b>|<expression2c>|

term> <expression2d>}

<expression1b> {<expression1b_term>|(<expression1b_term>[OR

<expression1b_term>]* )|(<expression1b_term>[AND

<expression1b_term>]* )}

<expression1b_ {<expression2e>|<expression2f>|<expression2g>|

term> <expression2h>}

<expression2a> {<term3a>|<term3b>|(<term3a> <boolean_op> <term3b>)}

<expression2b> {<term3c>|<range3a>|(<term3c> <boolean_op> <range3a>)}

<expression2c> {<term3d>|<gledge3a|(<term3d> <boolean_op> <gledge3a>)}

<expression2d> {<term3e>|<timer3a>|(<term3e> <boolean_op> <timer3a>)}

<expression2e> {<term3f>|<term3g>|(<term3f> <boolean_op> <term3g>)}

<expression2f> {<term3h>|<range3b>|(<term3h> <boolean_op> <range3b>)}

<expression2g> {<term3i>|<gledge3b>|(<term3i> <boolean_op> <gledge3b>)}

<expression2h> {<term3j>|<timer3b>|(<term3e> <boolean_op> <timer3b>)}

22–6

Download from Www.Somanuals.com. All Manuals Search And Download.

TTRigger (TTRace) Subsystem

Qualifier

<boolean_op> {AND|NAND|OR|NOR|XOR|NXOR}

<term3a> {A|NOTA}

<term3b> {B|NOTB}

<term3c> {C|NOTC}

<term3d> {D|NOTD}

<term3e> {E|NOTE}

<term3f> {F|NOTF}

<term3g> {G|NOTG}

<term3h> {H|NOTH}

<term3i> {I|NOTI}

<term3j> {J|NOTJ}

<range3a> {IN_RANGE1|OUT_RANGE1}

<range3b> {IN_RANGE2|OUT_RANGE2}

<gledge3a> {GLEDge1|NOT GLEDge1}

<gledge3b> {GLEDge2|NOT GLEDge2}

<timer3a> {TIMER1<|TIMER1>}

<timer3b> {TIMER2<|TIMER2>}

* = is optional such that it can be used zero or more times

+ = must be used at least once and can be repeated

22–7

Download from Www.Somanuals.com. All Manuals Search And Download.

TTRigger (TTRace) Subsystem

TTRigger (TTRace)

Qualifier Rules

The following rules apply to qualifiers:

Qualifiers are quoted strings and, therefore, need quotes.

•

Expressions are evaluated from left to right.

•

Parenthesis are used to change the order evaluation and, therefore, are

optional.

•

An expression must map into the combination logic presented in the

combination pop-up menu within the TTRigger menu.

•

Examples

’A’

’( A OR B )’

’(( A OR B ) AND C )’

’(( A OR B ) AND C AND IN_RANGE2 )’

’(( A OR B ) AND ( C AND IN_RANGE1 ))’

’IN_RANGE1 AND ( A OR B ) AND C’

TTRigger (TTRace)

Selector

:MACHine{1|2}:TTRigger

The TTRigger (TTRace) (Trace Trigger) selector is used as a part of a

compound header to access the settings found in the Timing Trace menu. It

always follows the MACHine selector because it selects a branch directly

below the MACHine level in the command tree.

Example

OUTPUT XXX;":MACHINE1:TTRIGGER:TAG TIME"

22–8

Download from Www.Somanuals.com. All Manuals Search And Download.

TTRigger (TTRace) Subsystem

ACQuisition

Command

:MACHine{1|2}:TTRigger:ACQuisition

{AUTOmatic|MANual}

The ACQuisition command allows you to specify the acquisition mode for the

Timing analyzer.

Example

OUTPUT XXX;":MACHINE1:TTRIGGER:ACQUISITION AUTOMATIC"

Query

:MACHine{1|2}:TTRigger:ACQuisition?

The ACQuisition query returns the current acquisition mode specified.

Returned Format

[:MACHine{1|2}:TTRigger:ACQuisition] {AUTOmatic|MANual}<NL>

Example

OUTPUT XXX;":MACHINE1:TTRIGGER:ACQUISITION?"

BRANch

Command

:MACHine{1|2}:TTRigger:BRANch<N>

<branch_qualifier>,<to_level_number>

The BRANch command defines the branch qualifier for a given sequence

level. When this branch qualifier is matched, it will cause the sequencer

to jump to the specified sequence level.

The terms used by the branch qualifier (A through J) are defined by the

TERM command. The meaning of IN_RANGEand OUT_RANGEis

determined by the RANGE command.

Within the limitations shown by the syntax definitions, complex expressions

may be formed using the ANDand OR operators. Expressions are limited to

what you could manually enter through the Timing Trigger menu. Regarding

parentheses, the syntax definitions on the next page show only the required

ones. Additional parentheses are allowed as long as the meaning of the

22–9

Download from Www.Somanuals.com. All Manuals Search And Download.

TTRigger (TTRace) Subsystem

BRANch

expression is not changed. Figure 22-2, on page 22-11 shows a complex

expression as seen in the Timing Trigger menu.

Example

The following statements are all correct and have the same meaning. Notice

that the conventional rules for precedence are not followed. The expressions

are evaluated from left to right.

OUTPUT XXX;":MACHINE1:TTRIGGER:BRANCH1 ’C AND D OR F OR G’, 1"

OUTPUT XXX;":MACHINE1:TTRIGGER:BRANCH1 ’((C AND D) OR (F OR

G))’, 1"

OUTPUT XXX;":MACHINE1:TTRIGGER:BRANCH1 ’F OR (C AND D) OR

G’,1"

<N> integer from 1 to <number_of_levels>

<to_level_ integer from 1 to <number_of_levels>

number>

<number_of_ integer from 1 to the number of existing sequence levels (maximum 10)

levels>

<branch_ <qualifier>see "Qualifier" on page 22-6

qualifier>

Examples

OUTPUT XXX;":MACHINE1:TTRIGGER:BRANCH1 ’ANYSTATE’, 3"

OUTPUT XXX;":MACHINE2:TTRIGGER:BRANCH2 ’A’, 7"

OUTPUT XXX;":MACHINE1:TTRIGGER:BRANCH3 ’((A OR B) OR NOTG)’,

22–10

Download from Www.Somanuals.com. All Manuals Search And Download.

TTRigger (TTRace) Subsystem

BRANch

Query Syntax

:MACHine{1|2}:TTRigger:BRANch<N>?

The BRANch query returns the current branch qualifier specification for a

given sequence level.

Returned Format

Example

[:MACHine{1|2}:TTRigger:BRANch<N>] <branch_qualifier>,

<to_level_num><NL>

OUTPUT XXX;":MACHINE1:TTRIGGER:BRANCH3?"

Figure 22-2

Complex Qualifier

Figure 22-2 is a front-panel representation of the complex qualifier (a OR

b) And (g OR h).

Example

This example would be used to specify this complex qualifier.

OUTPUT XXX;":MACHINE1:TTRIGGER:BRANCH1 ’((A OR B) AND

(G OR H))’, 2"

22–11

Download from Www.Somanuals.com. All Manuals Search And Download.

TTRigger (TTRace) Subsystem

CLEar

Terms A through E, RANGE 1, GLITCH/EDGE1, and TIMER 1 must be grouped

together and terms F through J, RANGE 2, GLITCH/EDGE2, and TIMER 2 must be

grouped together. In the first level, terms from one group may not be mixed

with terms from the other. For example, the expression ((A OR IN_RANGE2)

AND (C OR H)) is not allowed because the term C cannot be specified in the E

through J group.

In the first level, the operators you can use are AND, NAND, OR, NOR,

XOR, NXOR. Either ANDor OR may be used at the second level to join the

two groups together. It is acceptable for a group to consist of a single term.

Thus, an expression like (B AND G)is legal since the two operands are both

simple terms from separate groups.

CLEar

Command

:MACHine{1|2}:TTRigger:CLEar

{All|SEQuence|RESource}

The CLEar command allows you to clear all settings in the Timing Trigger

menu and replace them with the default, clear only the sequence levels, or

clear only the resource term patterns.

Example

OUTPUT XXX;":MACHINE1:TTRIGGER:CLEAR RESOURCE"

22–12

Download from Www.Somanuals.com. All Manuals Search And Download.

TTRigger (TTRace) Subsystem

FIND

Command

:MACHine{1|2}:TTRigger:FIND<N>

<time_qualifier>,<condition_mode>

The FIND command defines the time qualifier for a given sequence level.

The qualifier tells the timing analyzer when to proceed to the next sequence

level. When this proceed qualifier is matched the specified number of times,

the sequencer will proceed to the next sequence level. In the sequence level

where the trigger is specified, the FIND command specifies the trigger

qualifier (see SEQuence command).

The terms A through J are defined by the TERM command. The meaning of

IN_RANGEand OUT_RANGEis determined by the RANGe command.

Expressions are limited to what you could manually enter through the Timing

Trigger menu. Regarding parentheses, the syntax definitions below show

only the required ones. Additional parentheses are allowed as long as the

meaning of the expression is not changed. See figure 12-2 on page 12-11 for

a detailed example.

<N>

integer from 1 to the number of existing sequence levels (maximum 10)

<condition_ {{GT|LT}, <duration_time>|OCCurrence, <occurrence>}

mode>

GT greater than

LT less than

<duration_time> real number from 8 ns to 5.00 seconds depending on sample period

<occurrence> integer from 1 to 1048575

<time_ <qualifier>see "Qualifier" on page 22-6

qualifier>

Examples

OUTPUT XXX;":MACHINE1:TTRIGGER:FIND1 ’ANYSTATE’, GT, 10E−6"

OUTPUT XXX;":MACHINE1:TTRIGGER:FIND3 ’((NOTA AND NOTB) OR

G)’, OCCURRENCE, 10"

22–13

Download from Www.Somanuals.com. All Manuals Search And Download.

TTRigger (TTRace) Subsystem

GLEDge

Query

:MACHine{1|2}:TTRigger:FIND4?

The FIND query returns the current time qualifier specification for a given

sequence level.

Returned Format

[:MACHine{1|2}:TTRigger:FIND<N>] <condition_mode>,

Example

OUTPUT XXX;":MACHINE1:TTRIGGER:FIND<N>?"

GLEDge

Command

:MACHine{1|2}:TTRigger:GLEDge<N> <label_name>,

<glitch_edge_spec>

The GLEDge (glitch/edge) command allows you to define edge and glitch

specifications for a given label. Edge specifications can be R(rising), F

(falling), E (either), or "." (don’t care). Glitch specifications consist of G

(glitch) or "." (don’t care). Edges and glitches are sent in the same string

with the right most string character specifying what the right most bit will be.

The <glitch_edge_spec> string length must match the exact number of bits

assigned to the specified label. If the string length does not match the number

of bits, the "Parameter string invalid" message is displayed.

<N> {1|2}

<label_name> string of up to 6 alphanumeric characters

<glitch_edge_ string consisting of {R|F|E|G|.| [to total number of bits]}

spec>

22–14

Download from Www.Somanuals.com. All Manuals Search And Download.

TTRigger (TTRace) Subsystem

RANGe

Example

For 8 bits assigned and no glitch:

OUTPUT XXX;":MACHINE1:TTRIGGER:GLEDGE1 ’DATA’, ’....F..E’"

For 16 bits assigned with glitch:

OUTPUT XXX;":MACHINE1:TTRIGGER:GLEDGE1 ’DATA’,

’....GGG.....F..R’"

Query

:MACHine{1|2}:TTRigger:GLEDe<N>? <label_name>

The GLEDge query returns the current specification for the given label.

Returned Format

[:MACHine{1|2}:TTRigger:GLEDe<N>]

<label_name>,<glitch_edge_pattern><NL>

Example

OUTPUT XXX;":MACHINE1:TTRIGGER:GLEDGE1? ’DATA’"

RANGe

Command

:MACHine{1|2}:TTRigger:RANGE <label_name>,

<start_pattern>,<stop_pattern>

The RANGe command allows you to specify a range recognizer term for the

specified machine. Since a range can only be defined across one label and,

since a label must contain 32 or less bits, the value of the start pattern or stop

pattern will be between (2³²)−1 and 0.

Since a label can only be defined across a maximum of two pods, a range term

is only available across a single label; therefore, the end points of the range

cannot be split between labels.

When these values are expressed in binary, they represent the bit values for

the label at one of the range recognizers’ end points. Don’t cares are not

allowed in the end point pattern specifications.

22–15

Download from Www.Somanuals.com. All Manuals Search And Download.

TTRigger (TTRace) Subsystem

RANGe

<label_name> string of up to 6 alphanumeric characters

<start_pattern> "{#B{0|1} . . . |

#Q{0|1|2|3|4|5|6|7} . . . |

#H{0|1|2|3|4|5|6|7|8|9|A|B|C|D|E|F} . . . |

{0|1|2|3|4|5|6|7|8|9} . . . }"

<stop_pattern> "{#B{0|1} . . . |

#Q{0|1|2|3|4|5|6|7} . . . |

#H{0|1|2|3|4|5|6|7|8|9|A|B|C|D|E|F} . . . |

{0|1|2|3|4|5|6|7|8|9} . . . }"

Examples

OUTPUT XXX;":MACHINE1:TTRIGGER:RANGE ’DATA’, ’127’, ’255’ "

OUTPUT XXX;":MACHINE1:TTRIGGER:RANGE ’ABC’, ’#B00001111’,

’#HCF’ "

Query

:MACHine{1|2}:TTRigger:RANGe?

The RANGe query returns the range recognizer end point specifications for

the range.

Returned Format

[:MACHine{1|2}:STRAce:RANGe] <label_name>,<start_pattern>,

<stop_pattern><NL>

Example

OUTPUT XXX;":MACHINE1:TTRIGGER:RANGE?"

22–16

Download from Www.Somanuals.com. All Manuals Search And Download.

TTRigger (TTRace) Subsystem

SEQuence

Command

:MACHine{1|2}:TTRigger:SEQuence <number_of_levels>

The SEQuence command defines the timing analyzer trace sequence. First,

it deletes the current trace sequence. Then, it inserts the number of levels

specified, with default settings. The number of levels can be between 1 and

10 when the analyzer is armed by the RUN key.

<number_of_ integer from 1 to 10

levels>

Example

OUTPUT XXX;":MACHINE1:TTRIGGER:SEQUENCE 4"

Query

:MACHine{1|2}:TTRigger:SEQuence?

The SEQuence query returns the current sequence specification.

Returned Format

[:MACHine{1|2}:TTRigger:SEQuence] <number_of_levels>,

<level_of_trigger><NL>

Example

OUTPUT XXX;":MACHINE1:TTRIGGER:SEQUENCE?"

22–17

Download from Www.Somanuals.com. All Manuals Search And Download.

TTRigger (TTRace) Subsystem

SPERiod

Command

:MACHine{1|2}:TTRigger:SPERiod <sample_period>

The SPERiod command allows you to set the sample period of the timing

analyzer in the Conventional and Glitch modes. The sample period range

depends on the mode selected and is as follows:

2 ns to 8 ms for Conventional Half Channel 500 MHz

•

4 ns to 8 ms for Conventional Full Channel 250 MHz

•

4 ns for Transitional Half Channel

•

8 ns for Transitional Full Channel

•

8 ns to 8 ms for Glitch Half Channel 125 MHz

•

<sample_period> real number from 2 ns to 8 ms depending on mode

Example

OUTPUT XXX;":MACHINE1:TTRIGGER:SPERIOD 50E−9"

Query

:MACHine{1|2}:TTRigger:SPERiod?

The SPERiod query returns the current sample period.

Returned Format

[:MACHine{1|2}:TTRigger:SPERiod] <sample_period><NL>

<sample_period> real number from 2 ns to 8 ms depending on mode

Example

OUTPUT XXX;":MACHINE1:TTRIGGER:SPERIOD?"

22–18

Download from Www.Somanuals.com. All Manuals Search And Download.

TTRigger (TTRace) Subsystem

TCONtrol

Command

:MACHine{1|2}:TTRigger:TCONtrol<N> <timer_num>,

{OFF|STARt|PAUSe|CONTinue}

The TCONtrol (timer control) command allows you to turn off, start, pause,

or continue the timer for the specified level. The time value of the timer is

defined by the TIMER command.

<N> integer from 1 to the number of existing sequence levels (maximum 10)

<timer_num> {1|2}

Example

OUTPUT XXX;":MACHINE2:TTRIGGER:TCONTROL6 1, PAUSE"

Query

:MACHine{1|2}:TTRigger:TCONTROL<N>? <timer_num>

The TCONtrol query returns the current TCONtrol setting of the specified

level.

Returned Format

[:MACHine{1|2}:TTRigger:TCONTROL<N> <timer_num>]

{OFF|STARt|PAUSe|CONTinue}<NL>

Example

OUTPUT XXX;":MACHINE2:TTRIGGER:TCONTROL6? 1"

22–19

Download from Www.Somanuals.com. All Manuals Search And Download.

TTRigger (TTRace) Subsystem

TERM

Command

:MACHine{1|2}:TTRigger:TERM

<term_id>,<label_name>,<pattern>

The TERM command allows you to a specify a pattern recognizer term in the

specified machine. Each command deals with only one label in the given

term; therefore, a complete specification could require several commands.

Since a label can contain 32 or less bits, the range of the pattern value will be

between 2³²− 1 and 0. When the value of a pattern is expressed in binary, it

represents the bit values for the label inside the pattern recognizer term.

Since the pattern parameter may contain don’t cares and be represented in

several bases, it is handled as a string of characters rather than a number.

All 10 terms (A through J) are available to either machine but not both

simultaneously. If you send the TERM command to a machine with a term

that has not been assigned to that machine, an error message "Legal

command but settings conflict" is returned.

<term_id> {A|B|C|D|E|F|G|H|I|J}

<label_name> string of up to 6 alphanumeric characters

<pattern> "{#B{0|1|X} . . . |

#Q{0|1|2|3|4|5|6|7|X} . . . |

#H{0|1|2|3|4|5|6|7|8|9|A|B|C|D|E|F|X} . . . |

{0|1|2|3|4|5|6|7|8|9} . . . }"

Example

OUTPUT XXX;":MACHINE1:TTRIGGER:TERM A,’DATA’,’255’ "

OUTPUT XXX;":MACHINE1:TTRIGGER:TERM B,’ABC’,’#BXXXX1101’ "

22–20

Download from Www.Somanuals.com. All Manuals Search And Download.

TTRigger (TTRace) Subsystem

TIMER

Query

:MACHine{1|2}:TTRigger:TERM?

<term_id>,<label_name>

The TERM query returns the specification of the term specified by term

identification and label name.

Returned Format

[:MACHine{1|2}:STRAce:TERM] <term_id>,<label_name>,

Example

OUTPUT XXX;":MACHINE1:TTRIGGER:TERM? B,’DATA’ "

TIMER

Command

:MACHine{1|2}:TTRigger:TIMER{1|2} <time_value>

The TIMER command sets the time value for the specified timer. The limits

of the timer are 400 ns to 500 seconds in 16 ns to 500 µs increments. The

increment value varies with the time value of the specified timer.

<time_value> real number from 400 ns to 500 seconds in increments which vary from 16 ns

to 500 µs.

Example

OUTPUT XXX;":MACHINE1:TTRIGGER:TIMER1 100E−6"

Query

:MACHine{1|2}:TTRigger:TIMER{1|2}?

The TIMER query returns the current time value for the specified timer.

Returned Format

[:MACHine{1|2}:TTRigger:TIMER{1|2}] <time_value><NL>

Example

OUTPUT XXX;":MACHINE1:TTRIGGER:TIMER1?"

22–21

Download from Www.Somanuals.com. All Manuals Search And Download.

TTRigger (TTRace) Subsystem

TPOSition

Command

:MACHine{1|2}:TTRigger:TPOSition

{STARt|CENTer|END|DELay, <time_val>|

POSTstore,<poststore>}

The TPOSition (trigger position) command allows you to set the trigger at

the start, center, end or at any position in the trace (poststore). Poststore is

defined as 0 to 100 percent with a poststore of 100 percent being the same as

start position and a poststore 0 percent being the same as an end trace.

<time_val>

real number from either (2 × sample period) or 16 ns whichever is greater to

(1048575 × sample period).

<poststore> integer from 0 to 100 representing percentage of poststore.

Examples

OUTPUT XXX;":MACHINE1:TTRIGGER:TPOSITION END"

OUTPUT XXX;":MACHINE1:TTRIGGER:TPOSITION POSTstore,75"

Query

:MACHine{1|2}:TTRigger:TPOSition?

The TPOSition query returns the current trigger position setting.

Returned Format

[:MACHine{1|2}:TTRigger:TPOSition] {STARt|CENTer|END|DELay,

<time_val>|POSTstore,<poststore>}<NL>

Example

OUTPUT XXX;":MACHINE1:TTRIGGER:TPOSITION?"

22–22

Download from Www.Somanuals.com. All Manuals Search And Download.

TWAVeform Subsystem

Download from Www.Somanuals.com. All Manuals Search And Download.

Introduction

The TWAVeform subsystem contains the commands available for the

Timing Waveforms menu in the 1660-series logic analyzer. These

commands are:

• ACCumulate

• ACQuisition

• CENter

• CLRPattern

• CLRStat

• DELay

• INSert

• MMODe

• REMove

• RUNTil

• SPERiod

• TAVerage

• TMAXimum

• TMINimum

• TPOSition

• VRUNs

• OCONdition

• OPATtern

• OSEarch

• OTIMe

• XCONdition

• XOTime

• XPATtern

• XSEarch

• XTIMe

• RANGe

23–2

Download from Www.Somanuals.com. All Manuals Search And Download.

TWAVeform Subsystem

Figure 23-1

TWAVeform Subsystem Syntax Diagram

23–3

Download from Www.Somanuals.com. All Manuals Search And Download.

TWAVeform Subsystem

Figure 23-1 (continued)

TWAVeform Subsystem Syntax Diagram (continued)

23–4

Download from Www.Somanuals.com. All Manuals Search And Download.

TWAVeform Subsystem

Figure 23-1 (continued)

TWAVeform Subsystem Syntax Diagram (continued)

23–5

Download from Www.Somanuals.com. All Manuals Search And Download.

TWAVeform Subsystem

Table 23-1

TWAVeform Parameter Values

Parameter

Value

delay_value

real number between −2500 s and +2500 s

module_spec

bit_id

{1|2|3|4|5|6|7|8|9|10}2 through 10 unused

integer from 0 to 31

waveform

string containing <acquisition_spec>{1|2}

{A|B|C|D|E|F|G|H|I|J} (slot where acquisition card is located)

string of up to 6 alphanumeric characters

acquisition_spec

label_name

label_pattern

"{#B{0|1|X} . . . |

#Q{0|1|2|3|4|5|6|7|X}...|

#H{0|1|2|3|4|5|6|7|8|9|A|C|D|E|F|X}...|

{0|1|2|3|4|5|6|7|8|9|X}...}"

occurrence

time_value

label_id

integer

real number

string of one alpha and one numeric character

slot number in which the time base card is installed

real number between 10 ns and 10 ks

module_num

time_range

run_until_spec

{OFF|LT,<value>|GT,<value>|INRange<value>,

<value>|OUTRange<value>,<value>}

greater than

less than

value

time_val

real number

real number from 0 to 500 representing seconds

23–6

Download from Www.Somanuals.com. All Manuals Search And Download.

TWAVeform Subsystem

TWAVeform

Selector

:MACHine{1|2}:TWAVeform

The TWAVeform selector is used as part of a compound header to access the

settings found in the Timing Waveforms menu. It always follows the

MACHine selector because it selects a branch below the MACHine level in the

command tree.

Example

OUTPUT XXX;":MACHINE1:TWAVEFORM:DELAY 100E−9"

ACCumulate

Command

:MACHine{1|2}:TWAVeform:ACCumulate <setting>

The ACCumulate command allows you to control whether the chart display

gets erased between each individual run or whether subsequent waveforms

are allowed to be displayed over the previous ones.

<setting> {0|OFF} or {1|ON}

Example

OUTPUT XXX;":MACHINE1:TWAVEFORM:ACCUMULATE ON"

Query

:MACHine{1|2}:TWAVeform:ACCumulate?

The ACCumulate query returns the current setting. The query always shows

the setting as the characters, "0" (off) or "1" (on).

Returned Format

[:MACHine{1|2}:TWAVeform:ACCumulate] {0|1}<NL>

Example

OUTPUT XXX;":MACHINE1:TWAVEFORM:ACCUMULATE?"

23–7

Download from Www.Somanuals.com. All Manuals Search And Download.

TWAVeform Subsystem

ACQuisition

Command

:MACHine{1|2}:TWAVeform:ACQuisition

{AUTOmatic|MANual}

The ACQuisition command allows you to specify the acquisition mode for the

state analyzer. The acquisition modes are automatic and manual.

Example

OUTPUT XXX;":MACHINE2:TWAVEFORM:ACQUISITION AUTOMATIC"

Query

MACHine{1|2}:TWAVeform:ACQuisition?

The ACQuisition query returns the current acquisition mode.

Returned Format

[:MACHine{1|2}:TWAVeform:ACQuisition] {AUTOmatic|MANual}<NL>

Example

OUTPUT XXX;":MACHINE2:TWAVEFORM:ACQUISITION?"

CENTer

Command

:MACHine{1|2}:Twaveform:CENTer <marker_type>

The CENTer command allows you to center the waveform display about the

specified markers.

<marker_type> {X|O|XO|TRIGger}

Example

OUTPUT XXX;":MACHINE1:TWAVEFORM:CENTER X"

23–8

Download from Www.Somanuals.com. All Manuals Search And Download.

TWAVeform Subsystem

CLRPattern

Command

:MACHine{1|2}:TWAVeform:CLRPattern {X|O|ALL}

The CLRPattern command allows you to clear the patterns in the selected

Specify Patterns menu.

Example

OUTPUT XXX;":MACHINE1:TWAVEFORM:CLRPATTERN ALL"

CLRStat

Command

:MACHine{1|2}:Twaveform:CLRStat

The CLRStat command allows you to clear the waveform statistics without

having to stop and restart the acquisition.

Example

OUTPUT XXX;":MACHINE1:TWAVEFORM:CLRSTAT"

DELay

Command

:MACHine{1|2}:TWAVeform:DELay <delay_value>

The DELay command specifies the amount of time between the timing

trigger and the horizontal center of the the timing waveform display. The

allowable values for delay are −2500 s to +2500 s. If the acquisition mode is

automatic, then in glitch acquisition mode, as delay becomes large in an

absolute sense, the sample rate is adjusted so that data will be acquired in

the time window of interest. In transitional acquisition mode, data may not

fall in the time window since the sample period is fixed and the amount of

time covered in memory is dependent on how frequent the input signal

transitions occur.

23–9

Download from Www.Somanuals.com. All Manuals Search And Download.

TWAVeform Subsystem

INSert

<delay_value>

real number between −2500 s and +2500 s

Example

OUTPUT XXX;":MACHINE1:TWAVEFORM:DELAY 100E−6"

Query

:MACHine{1|2}:TWAVeform:DELay?

The DELay query returns the current time offset (delay) value from the

trigger.

Returned Format

[:MACHine{1|2}:TWAVeform:DELay] <delay_value><NL>

Example

OUTPUT XXX;":MACHINE1:TWAVEFORM:DELAY?"

INSert

Command

:MACHine{1|2}:TWAVeform:INSert [<module_spec>,]

<label_name>[,{<bit_id>|OVERlay|ALL}]

The INSert command allows you to add waveforms to the state waveform

display. Waveforms are added from top to bottom on the screen. When 96

waveforms are present, inserting additional waveforms replaces the last

waveform. Bit numbers are zero based, so a label with 8 bits is referenced as

bits 0 through 7. Specifying OVERlay causes a composite waveform display

of all bits or channels for the specified label. If you do not specify the third

parameter, ALL is assumed.

<module_spec> {1|2|3|4|5|6|7|8|9|10}2 through 10 unused.

<label_name> string of up to 6 alphanumeric characters

<bit_id> integer from 0 to 31

Example

OUTPUT XXX;":MACHINE1:TWAVEFORM:INSERT 1, ’WAVE’,10"

23–10

Download from Www.Somanuals.com. All Manuals Search And Download.

TWAVeform Subsystem

MMODe

Command

:MACHine{1|2}:TWAVeform:MMODe

{OFF|PATTern|TIME|MSTats}

The MMODe (Marker Mode) command selects the mode controlling marker

movement and the display of the marker readouts. When PATTern is

selected, the markers will be placed on patterns. When TIME is selected, the

markers move on time. In MSTats, the markers are placed on patterns, but

the readouts will be time statistics.

Example

OUTPUT XXX; ":MACHINE1:TWAVEFORM:MMODE TIME"

Query

:MACHine{1|2}:TWAVeform:MMODe?

The MMODe query returns the current marker mode.

Returned Format

[:MACHine{1|2}:TWAVeform:MMODe] <marker_mode><NL>

<marker_mode> {OFF|PATTern|TIME|MSTats}

Example

OUTPUT XXX;":MACHINE1:TWAVEFORM:MMODE?"

23–11

Download from Www.Somanuals.com. All Manuals Search And Download.

TWAVeform Subsystem

OCONdition

Command

:MACHine{1|2}:TWAVeform:OCONdition

{ENTering|EXITing}

The OCONdition command specifies where the O marker is placed. The O

marker can be placed on the entry or exit point of the OPATtern when in the

PATTern marker mode.

Example

OUTPUT XXX; ":MACHINE1:TWAVEFORM:OCONDITION ENTERING"

Query

:MACHine{1|2}:TWAVeform:OCONdition?

The OCONdition query returns the current setting.

Returned Format

[:MACHine{1|2}:TWAVeform:OCONdition] {ENTering|EXITing}<NL>

Example

OUTPUT XXX;":MACHINE1:TWAVEFORM:OCONDITION?"

23–12

Download from Www.Somanuals.com. All Manuals Search And Download.

TWAVeform Subsystem

OPATtern

Command

:MACHine{1|2}:TWAVeform:OPATtern

<label_name>,<label_pattern>

The OPATtern command allows you to construct a pattern recognizer term

for the O marker which is then used with the OSEarch criteria and

OCONdition when moving the marker on patterns. Since this command deals

with only one label at a time, a complete specification could require several

invocations.

When the value of a pattern is expressed in binary, it represents the bit

values for the label inside the pattern recognizer term. In whatever base is

used, the value must be between 0 and 2³²− 1, since a label may not have

more than 32 bits. Because the <label_pattern>parameter may contain

don’t cares, it is handled as a string of characters rather than a number.

<label_name> string of up to 6 alphanumeric characters

<label_pattern> "{#B{0|1|X} . . . |

#Q{0|1|2|3|4|5|6|7|X} . . . |

#H{0|1|2|3|4|5|6|7|8|9|A|B|C|D|E|F|X} . . . |

{0|1|2|3|4|5|6|7|8|9} . . . }"

Example

OUTPUT XXX; ":MACHINE1:TWAVEFORM:OPATTERN ’A’,’511’"

Query

:MACHine{1|2}:TWAVeform:OPATtern? <label_name>

The OPATtern query, in pattern marker mode, returns the pattern

specification for a given label name. In the time marker mode, the query

returns the pattern under the O marker for a given label. If the O marker is

not placed on valid data, don’t cares (X) are returned.

Returned Format

[:MACHine{1|2}:TWAVeform:OPATtern] <label_name>,

<label_pattern><NL>

Example

OUTPUT XXX;":MACHINE1:TWAVEFORM:OPATTERN? ’A’"

23–13

Download from Www.Somanuals.com. All Manuals Search And Download.

TWAVeform Subsystem

OSEarch

Command

:MACHine{1|2}:TWAVeform:OSEarch

The OSEarch command defines the search criteria for the O marker which is

then used with the associated OPATtern recognizer specification and the

OCONdition when moving markers on patterns. The origin parameter tells

the marker to begin a search with the trigger or with the X marker. The

actual occurrence the marker searches for is determined by the occurrence

parameter of the OPATtern recognizer specification, relative to the origin.

An occurrence of 0 places a marker on the selected origin. With a negative

occurrence, the marker searches before the origin. With a positive

occurrence, the marker searches after the origin.

<origin> {STARt|TRIGger|XMARker}

integer from −8192 to +8192

Example

OUTPUT XXX; ":MACHINE1:TWAVEFORM:OSEARCH +10,TRIGGER"

Query

:MACHine{1|2}:TWAVeform:OSEarch?

The OSEarch query returns the search criteria for the O marker.

Returned Format

[:MACHine{1|2}:TWAVeform:OSEarch] <occurrence>,<origin><NL>

Example

OUTPUT XXX;":MACHINE1:TWAVEFORM:OSEARCH?"

23–14

Download from Www.Somanuals.com. All Manuals Search And Download.

TWAVeform Subsystem

OTIMe

Command

:MACHine{1|2}:TWAVeform:OTIMe <time_value>

The OTIMe command positions the O marker in time when the marker mode

is TIME. If data is not valid, the command performs no action.

<time_value>

real number −2.5 ks to +2.5 ks

Example

OUTPUT XXX; ":MACHINE1:TWAVEFORM:OTIME 30.0E−6"

Query

:MACHine{1|2}:TWAVeform:OTIMe?

The OTIMe query returns the O marker position in time. If data is not valid,

the query returns 9.9E37.

Returned Format

[:MACHine{1|2}:TWAVeform:OTIMe] <time_value><NL>

Example

OUTPUT XXX;":MACHINE1:TWAVEFORM:OTIME?"

23–15

Download from Www.Somanuals.com. All Manuals Search And Download.

TWAVeform Subsystem

RANGe

Command

:MACHine{1|2}:TWAVeform:RANGe <time_value>

The RANGe command specifies the full-screen time in the timing waveform

menu. It is equivalent to ten times the seconds-per-division setting on the

display. The allowable values for RANGe are from 10 ns to 10 ks.

<time_range> real number between 10 ns and 10 ks

Example

OUTPUT XXX;":MACHINE1:TWAVEFORM:RANGE 100E−9"

Query

:MACHine{1|2}:TWAVeform:RANGe?

The RANGe query returns the current full-screen time.

Returned Format

[:MACHine{1|2}:TWAVeform:RANGe] <time_value><NL>

Example

OUTPUT XXX;":MACHINE1:TWAVEFORM:RANGE?"

REMove

Command

:MACHine{1|2}:TWAVeform:REMove

The REMove command deletes all waveforms from the display.

Example

OUTPUT XXX;":MACHINE1:TWAVEFORM:REMOVE"

23–16

Download from Www.Somanuals.com. All Manuals Search And Download.

TWAVeform Subsystem

RUNTil

Command

:MACHine{1|2}:TWAVeform:RUNTil <run_until_spec>

The RUNTil (run until) command defines stop criteria based on the time

between the X and O markers when the trace mode is in repetitive. When

OFF is selected, the analyzer will run until either the STOP touch screen field

is touched, or, the STOP command is sent. Run until time between X and O

marker options are:

Less Than (LT) a specified time value.

•

Greater Than (GT) a specified time value.

•

In the range (INRange) between two time values.

•

Out of the range (OUTRange) between two time values

•

End points for the INRange and OUTRange should be at least 2 ns apart since

this is the minimum time at which data is sampled.

This command affects the timing analyzer only, and has no relation to the

RUNTil commands in the SLISt and COMPare subsystems.

<run_until_ {OFF|LT,<value>|GT,<value>|INRange<value>,<value>|

spec> OUTRange<value>,<value>}

<value> real number

Examples

OUTPUT XXX;":MACHINE1:TWAVEFORM:RUNTIL GT, 800.0E−6"

OUTPUT XXX;":MACHINE1:TWAVEFORM:RUNTIL INRANGE, 4.5, 5.5"

Query

:MACHine{1|2}:TWAVeform:RUNTil?

The RUNTil query returns the current stop criteria.

Returned Format

[:MACHine{1|2}:TWAVeform:RUNTil] <run_until_spec><NL>

Example

OUTPUT XXX;":MACHINE1:TWAVEFORM:RUNTIL?"

23–17

Download from Www.Somanuals.com. All Manuals Search And Download.

TWAVeform Subsystem

SPERiod

Command

:MACHine{1|2}:TWAVeform:SPERiod <sample_period>

The SPERiod command allows you to set the sample period of the timing

analyzer in the Conventional and Glitch modes. The sample period range

depends on the mode selected and is as follows:

2 ns to 8 ms for Conventional Half Channel 500 MHz

•

4 ns to 8 ms for Conventional Full Channel 250 MHz

•

8 ns to 8 ms for Glitch Half Channel 125 MHz

•

<sample_period> real number from 2 ns to 8 ms depending on mode

Example

OUTPUT XXX;":MACHINE1:TWAVEFORM:SPERIOD 50E−9"

Query

:MACHine{1|2}:TWAVeform:SPERiod?

The SPERiod query returns the current sample period.

Returned Format

[:MACHine{1|2}:TWAVeform:SPERiod] <sample_period><NL>

Example

OUTPUT XXX;":MACHINE1:TWAVEFORM:SPERIOD?"

23–18

Download from Www.Somanuals.com. All Manuals Search And Download.

TWAVeform Subsystem

TAVerage

Query

:MACHine{1|2}:TWAVeform:TAVerage?

The TAVerage query returns the value of the average time between the

X and O markers. If there is no valid data, the query returns 9.9E37.

[:MACHine{1|2}:TWAVeform:TAVerage] <time_value><NL>

Returned Format

<time_value> real number

Example

OUTPUT XXX;":MACHINE1:TWAVEFORM:TAVERAGE?"

TMAXimum

Query

:MACHine{1|2}:TWAVeform:TMAXimum?

The TMAXimum query returns the value of the maximum time between the X

and O markers. If there is no valid data, the query returns 9.9E37.

[:MACHine{1|2}:TWAVeform:TMAXimum] <time_value><NL>

Returned Format

<time_value> real number

Example

OUTPUT XXX;":MACHINE1:TWAVEFORM:TMAXIMUM?"

23–19

Download from Www.Somanuals.com. All Manuals Search And Download.

TWAVeform Subsystem

TMINimum

Query

:MACHine{1|2}:TWAVeform:TMINimum?

The TMINimum query returns the value of the minimum time between the X

and O markers. If there is no valid data, the query returns 9.9E37.

[:MACHine{1|2}:TWAVeform:TMINimum] <time_value><NL>

Returned Format

<time_value> real number

Example

OUTPUT XXX;":MACHINE1:TWAVEFORM:TMINIMUM?"

TPOSition

Command

:MACHine{1|2}:TWAVeform:TPOSition

{STARt|CENTer|END|DELay,<time_val>|

POSTstore,<percent>}

The TPOSition command allows you to control where the trigger point is

placed. The trigger point can be placed at the start, center, end, at a

percentage of post store, or at a value specified by delay. The post store

option is the same as the User Definedoption when setting the trigger

point from the front panel.

The TPOSition command is only available when the acquisition mode is set to

manual.

<time_val> real number from 0 to 500 seconds

<percent> integer from 1 to 100

Example

OUTPUT XXX;":MACHINE2:TWAVEFORM:TPOSITION CENTER"

23–20

Download from Www.Somanuals.com. All Manuals Search And Download.

TWAVeform Subsystem

VRUNs

Query

:MACHine{1|2}:TWAVeform:TPOSition?

The TPOSition query returns the current trigger setting.

Returned Format

[:MACHine{1|2}:TWAVeform:TPOSition] {STARt|CENTer|END|DELay,

<time_val>|POSTstore,<percent>}<NL>

<time_val> real number from 0 to 500 seconds

Example

OUTPUT XXX;":MACHINE2:TWAVEFORM:TPOSition?"

VRUNs

Query

:MACHine{1|2}:TWAVeform:VRUNs?

The VRUNs query returns the number of valid runs and total number of runs

made. Valid runs are those where the pattern search for both the X and O

markers was successful resulting in valid delta time measurements.

[:MACHine{1|2}:TWAVeform:VRUNs] <valid_runs>,<total_runs><NL>

Returned Format

<valid_runs> zero or positive integer

<total_runs> zero or positive integer

Example

OUTPUT XXX;":MACHINE1:TWAVEFORM:VRUNS?"

23–21

Download from Www.Somanuals.com. All Manuals Search And Download.

TWAVeform Subsystem

XCONdition

Command

:MACHine{1|2}:TWAVeform:XCONdition

{ENTering|EXITing}

The XCONdition command specifies where the X marker is placed. The X

marker can be placed on the entry or exit point of the XPATtern when in the

PATTern marker mode.

Example

OUTPUT XXX; ":MACHINE1:TWAVEFORM:XCONDITION ENTERING"

Query

:MACHine{1|2}:TWAVeform:XCONdition?

The XCONdition query returns the current setting.

Returned Format

[:MACHine{1|2}:TWAVeform:XCONdition] {ENTering|EXITing}<NL>

Example

OUTPUT XXX;":MACHINE1:TWAVEFORM:XCONDITION?"

XOTime

Query

:MACHine{1|2}:TWAVeform:XOTime?

The XOTime query returns the time from the X marker to the O marker. If

data is not valid, the query returns 9.9E37.

Returned Format

[:MACHine{1|2}:TWAVeform:XOTime] <time_value><NL>

<time_value> real number

Example

OUTPUT XXX;":MACHINE1:TWAVEFORM:XOTIME?"

23–22

Download from Www.Somanuals.com. All Manuals Search And Download.

TWAVeform Subsystem

XPATtern

Command

:MACHine{1|2}:TWAVeform:XPATtern <label_name>,

<label_pattern>

The XPATtern command allows you to construct a pattern recognizer term

for the X marker which is then used with the XSEarch criteria and

XCONdition when moving the marker on patterns. Since this command deals

with only one label at a time, a complete specification could require several

iterations.

When the value of a pattern is expressed in binary, it represents the bit

values for the label inside the pattern recognizer term. In whatever base is

used, the value must be between 0 and 2³²− 1, since a label may not have

more than 32 bits. Because the <label_pattern> parameter may contain

don’t cares, it is handled as a string of characters rather than a number.

<label_name> string of up to 6 alphanumeric characters

<label_pattern> "{#B{0|1|X} . . . |

#Q{0|1|2|3|4|5|6|7|X} . . . |

#H{0|1|2|3|4|5|6|7|8|9|A|B|C|D|E|F|X} . . . |

{0|1|2|3|4|5|6|7|8|9} . . . }"

Example

OUTPUT XXX; ":MACHINE1:TWAVEFORM:XPATTERN ’A’,’511’"

Query

:MACHine{1|2}:TWAVeform:XPATtern? <label_name>

The XPATtern query, in pattern marker mode, returns the pattern

specification for a given label name. In the time marker mode, the query

returns the pattern under the X marker for a given label. If the X marker is

not placed on valid data, don’t cares (X)are returned.

Returned Format

[:MACHine{1|2}:TWAVeform:XPATtern] <label_name>,

<label_pattern><NL>

Example

OUTPUT XXX;":MACHINE1:TWAVEFORM:XPATTERN? ’A’"

23–23

Download from Www.Somanuals.com. All Manuals Search And Download.

TWAVeform Subsystem

XSEarch

Command

:MACHine{1|2}:TWAVeform:XSEarch

The XSEarch command defines the search criteria for the X marker which is

then used with the associated XPATtern recognizer specification and the

XCONdition when moving markers on patterns. The origin parameter tells

the marker to begin a search with the trigger. The occurrence parameter

determines which occurrence of the XPATtern recognizer specification,

relative to the origin, the marker actually searches for. An occurrence of 0

(zero) places a marker on the origin.

<origin> {TRIGger|STARt}

integer from −8192 to +8192

Example

OUTPUT XXX; ":MACHINE1:TWAVEFORM:XSEARCH,+10,TRIGGER"

Query

:MACHine{1|2}:TWAVeform:XSEarch?

The XSEarch query returns the search criteria for the X marker.

Returned Format

[:MACHine{1|2}:TWAVeform:XSEarch] <occurrence>,<origin><NL>

Example

OUTPUT XXX;":MACHINE1:TWAVEFORM:XSEARCH?"

23–24

Download from Www.Somanuals.com. All Manuals Search And Download.

TWAVeform Subsystem

XTIMe

Command

:MACHine{1|2}:TWAVeform:XTIMe <time_value>

The XTIMe command positions the X marker in time when the marker mode

is TIME. If data is not valid, the command performs no action.

<time_value>

real number from −2.5 ks to +2.5 ks

Example

OUTPUT XXX; ":MACHINE1:TWAVEFORM:XTIME 40.0E−6"

Query

:MACHine{1|2}:TWAVeform:XTIMe?

The XTIMe query returns the X marker position in time. If data is not valid,

the query returns 9.9E37.

Returned Format

[:MACHine{1|2}:TWAVeform:XTIMe] <time_value><NL>

Example

OUTPUT XXX;":MACHINE1:TWAVEFORM:XTIME?"

23–25

Download from Www.Somanuals.com. All Manuals Search And Download.

23–26

Download from Www.Somanuals.com. All Manuals Search And Download.

TLISt Subsystem

Download from Www.Somanuals.com. All Manuals Search And Download.

Introduction

The TLISt subsystem contains the commands available for the Timing

Listing menu in the 1660-series logic analyzers and is the same as the

SLISt subsystem with the exception of the OCONdition and

XCONdition commands. The TLISt subsystem commands are:

• COLumn

• CLRPattern

• DATA

• LINE

• MMODe

• OCONdition

• OPATtern

• OSEarch

• OSTate

• OTAG

• REMove

• RUNTil

• TAVerage

• TMAXimum

• TMINimum

• VRUNs

• XCONdition

• XOTag

• XOTime

• XPATtern

• XSEarch

• XSTate

• XTAG

24–2

Download from Www.Somanuals.com. All Manuals Search And Download.

TLISt Subsystem

Figure 24-1

TLISt Subsystem Syntax Diagram

24–3

Download from Www.Somanuals.com. All Manuals Search And Download.

TLISt Subsystem

Figure 24-1 (continued)

TLISt Subsystem Syntax Diagram (continued)

24–4

Download from Www.Somanuals.com. All Manuals Search And Download.

TLISt Subsystem

Figure 24-1 (continued)

TLISt Subsystem Syntax Diagram (continued)

24–5

Download from Www.Somanuals.com. All Manuals Search And Download.

TLISt Subsystem

Table 24-1

TLISt Parameter Values

Parameter

Values

module_num

mach_num

col_num

{1|2|3|4|5|6|7|8|9|10}2 through 10 not used

{1|2}

integer from 1 to 61

line_number

integer from −8191 to +8191

label_name

base

string of up to 6 alphanumeric characters

{BINary|HEXadecimal|OCTal|DECimal|TWOS|

ASCii|SYMBol|IASSembler}for labels

{ABSolute|RELative} for tags

line_num_mid_screen

label_pattern

integer from −8191to +8191

"{#B{0|1|X} . . . |

#Q{0|1|2|3|4|5|6|7|X} . . . |

#H{0|1|2|3|4|5|6|7|8|9|A|B|C|D|E|F|X} . . .|

{0|1|2|3|4|5|6|7|8|9} . . . }"

occurrence

integer from −8191 to +8191

real number

time_value

state_value

run_until_spec

real number

{OFF|LT,<value>|GT,<value>|INRange,<value>,

<value>|OUTRange,<value>,<value>}

value

real number

24–6

Download from Www.Somanuals.com. All Manuals Search And Download.

TLISt Subsystem

TLISt

Selector

:MACHine{1|2}:TLISt

The TLISt selector is used as part of a compound header to access those

settings normally found in the Timing Listing menu. It always follows the

MACHine selector because it selects a branch directly below the MACHine

level in the command tree.

Example

OUTPUT XXX;":MACHINE1:TLIST:LINE 256"

COLumn

Command

:MACHine{1|2}:TLISt:COLumn

<col_num>[,<module_num>,

MACHine{1|2}],<label_name>,<base>

The COLumn command allows you to configure the timing analyzer

list display by assigning a label name and base to one of the 61 vertical

columns in the menu. A column number of 1 refers to the left most column.

When a label is assigned to a column it replaces the original label in that

column.

When the label name is "TAGS," the TAGS column is assumed and the next

parameter must specify RELative or ABSolute.

A label for tags must be assigned in order to use ABSolute or RELative state

tagging.

24–7

Download from Www.Somanuals.com. All Manuals Search And Download.

TLISt Subsystem

CLRPattern

<col_num> integer from 1 to 61

<module_num> {1|2|3|4|5|6|7|8|9|10} 2 through 10 unused

<label_name> a string of up to 6 alphanumeric characters

<base> {BINary|HEXadecimal|OCTal|DECimal|TWOS|ASCii|SYMBol|

IASSembler} for labels

{ABSolute|RELative} for tags

Example

OUTPUT XXX;":MACHINE1:TLIST:COLUMN 4,1,’A’,HEX"

Query

:MACHine{1|2}:TLISt:COLumn? <col_num>

The COLumn query returns the column number, label name, and base for the

specified column.

Returned Format

[:MACHine{1|2}:TLISt:COLumn] <col_num>,<module_num>

,MACHine{1|2},<label_name>,<base><NL>

Example

OUTPUT XXX;":MACHINE1:TLIST:COLUMN? 4"

CLRPattern

Command

:MACHine{1|2}:TLISt:CLRPattern {X|O|ALL}

The CLRPattern command allows you to clear the patterns in the selected

Specify Patterns menu.

Example

OUTPUT XXX;":MACHINE1:TLIST:CLRPATTERN O"

24–8

Download from Www.Somanuals.com. All Manuals Search And Download.

TLISt Subsystem

DATA

Query

:MACHine{1|2}:TLISt:DATA? <line_number>,

<label_name>

The DATA query returns the value at a specified line number for a given

label. The format will be the same as the one shown in the Listing display.

Returned Format

[:MACHine{1|2}:TLISt:DATA] <line_number>,<label_name>,

<pattern_string><NL>

<line_number>

integer from −8191 to +8191

<label_name> string of up to 6 alphanumeric characters

<pattern_ "{#B{0|1|X} . . . |

string> #Q{0|1|2|3|4|5|6|7|X} . . . |

#H{0|1|2|3|4|5|6|7|8|9|A|B|C|D|E|F|X} . . . |

{0|1|2|3|4|5|6|7|8|9} . . . }"

Example

OUTPUT XXX;":MACHINE1:TLIST:DATA? 512, ’RAS’"

LINE

Command

:MACHine{1|2}:TLISt:LINE <line_num_mid_screen>

The LINE command allows you to scroll the timing analyzer listing vertically.

The command specifies the state line number relative to the trigger that the

analyzer highlights at the center of the screen.

<line_num_mid_

screen>

integer from −8191 to +8191

Example

OUTPUT XXX;":MACHINE1:TLIST:LINE 0"

24–9

Download from Www.Somanuals.com. All Manuals Search And Download.

TLISt Subsystem

MMODe

Query

:MACHine{1|2}:TLISt:LINE?

The LINE query returns the line number for the state currently in the box at

the center of the screen.

Returned Format

[:MACHine{1|2}:TLISt:LINE] <line_num_mid_screen><NL>

Example

OUTPUT XXX;":MACHINE1:TLIST:LINE?"

MMODe

Command

:MACHine{1|2}:TLISt:MMODe <marker_mode>

The MMODe command (Marker Mode) selects the mode controlling the

marker movement and the display of marker readouts. When PATTern is

selected, the markers will be placed on patterns. When TIME is selected, the

markers move on time between stored states. When MSTats is selected, the

markers are placed on patterns, but the readouts will be time statistics.

<marker_mode> {OFF|PATTern|TIME|MSTats}

Example

OUTPUT XXX;":MACHINE1:TLIST:MMODE TIME"

Query

:MACHine{1|2}:TLISt:MMODe?

The MMODe query returns the current marker mode selected.

Returned Format

[:MACHine{1|2}:TLISt:MMODe] <marker_mode><NL>

Example

OUTPUT XXX;":MACHINE1:TLIST:MMODE?"

24–10

Download from Www.Somanuals.com. All Manuals Search And Download.

TLISt Subsystem

OCONdition

Command

:MACHine{1|2}:TLISt:OCONdition {ENTering|EXITing}

The OCONdition command specifies where the O marker is placed. The O

marker can be placed on the entry or exit point of the OPATtern when in the

PATTern marker mode.

Example

OUTPUT XXX; ":MACHINE1:TLIST:OCONDITION ENTERING"

Query

:MACHine{1|2}:TLISt:OCONdition?

The OCONdition query returns the current setting.

Returned Format

[:MACHine{1|2}:TLISt:OCONdition] {ENTering|EXITing}<NL>

Example

OUTPUT XXX;":MACHINE1:TLIST:OCONDITION?"

OPATtern

Command

:MACHine{1|2}:TLISt:OPATtern

<label_name>,<label_pattern>

The OPATtern command allows you to construct a pattern recognizer term

for the O Marker which is then used with the OSEarch criteria when moving

the marker on patterns. Since this command deals with only one label at a

time, a complete specification could require several iterations.

When the value of a pattern is expressed in binary, it represents the bit

values for the label inside the pattern recognizer term. In whatever base is

used, the value must be between 0 and 2³²− 1, since a label may not have

more than 32 bits. Because the <label_pattern> parameter may contain don’t

cares, it is handled as a string of characters rather than a number.

24–11

Download from Www.Somanuals.com. All Manuals Search And Download.

TLISt Subsystem

OSEarch

<label_name> string of up to 6 alphanumeric characters

<label_ "{#B{0|1|X} . . . |

pattern> #Q{0|1|2|3|4|5|6|7|X} . . . |

#H{0|1|2|3|4|5|6|7|8|9|A|B|C|D|E|F|X} . . . |

{0|1|2|3|4|5|6|7|8|9} . . . }"

Examples

OUTPUT XXX;":MACHINE1:TLIST:OPATTERN ’DATA’,’255’ "

OUTPUT XXX;":MACHINE1:TLIST:OPATTERN ’ABC’,’#BXXXX1101’ "

Query

:MACHine{1|2}:TLISt:OPATtern? <label_name>

The OPATtern query returns the pattern specification for a given label name.

Returned Format

[:MACHine{1|2}:TLISt:OPATtern]

<label_name>,<label_pattern><NL>

Example

OUTPUT XXX;":MACHINE1:TLIST:OPATTERN? ’A’"

OSEarch

Command

:MACHine{1|2}:TLISt:OSEarch <occurrence>,<origin>