Agilent 16500B Data Sheet

Download

Errata

16500B Programmers Guide 16500-97009

April 1994

Title & Document Type:

Manual Part Number:

Revision Date:

HP References in this Manual

This manual may contain references to HP or Hewlett-Packard. Please note that HewlettPackard's former test and measurement, semiconductor products and chemical analysis businesses are now part of Agilent Technologies. We have made no changes to this manual copy. The HP XXXX referred to in this document is now the Agilent XXXX. For example, model number HP8648A is now model number Agilent 8648A.

About this Manual

We’ve added this manual to the Agilent website in an effort to help you support your product. This manual provides the best information we could find. It may be incomplete or contain dated information, and the scan quality may not be idea l. If we find a better copy in the future, we will add it to the Agilent website.

Support for Your Product

Agilent no longer sells or supports this product. You will find any other available product information on the Agilent Test & Measurement website:

www.tm.agilent.com

Search for the model number of this product, and the resulting product page will guide you to any available information. Our service centers may be able to perform calibration if no repair parts are needed, but no other support from Agilent is available.

Programmer’s Guide

Publication number 16500-97009 Second edition, April 1994

For Safety information, Warranties, and Regulatory information, see the pages behind the index

HP 16500B/16501A Logic Analysis System

In This Book

This programmer’s guide contains general information, mainframe level commands, and programming examples for programming the HP 16500B/16501A Logic Analysis System. This guide focuses on how to program the system over the HP-IB and the RS-232C interfaces. However, if you have the optional HP 16500L LAN Interface Module, you will need to use the

HP 16500L LAN Interface Module User’s Guide along with this guide to

program the system over the LAN. Along with the programmer’s guides for

the individual modules, this guide provides a complete set of programming information for your system.

Organization

When you received your HP 16500B you received two binders, Volume 1 and Volume 2. The Volume 2 binder gives you a place to insert the module programmer’s guides when the Volume 1 binder is full.

As you purchase additional measurement modules, insert their programmer’s guides in the back of this binder or in the second binder.

Introduction to Programming

Programming Over HP-IB

Programming Over RS-232C

Programming and Documentation Conventions

Message Communication and System Functions

Status Reporting

Error Messages

Common Commands

Mainframe Commands

SYSTem Subsystem

MMEMory Subsystem

INTermodule Subsystem

Programming Examples

What is in the HP 16500B/16500A Programmer’s Guide?

The HP 16500B/16501A Programmer’s Guide is organized in three parts.

Index

iii

Part 1 Part 1 consists of chapters 1 through 7 and contains general information about programming basics, HP-IB and RS-232C interface requirements, documentation conventions, status reporting, and error messages. If you are already familiar with IEEE 488.2 programming and HP-IB or RS-232C, you may want to just scan these chapters. If you are new to programming logic analyzers 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 HP-IB," or chapter 3, "Programming Over RS-232C" for information concerning the physical connection between the HP 16500B/16501A Logic Analysis System 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, chapter 13, contains program examples of actual tasks that show you how to get started in programming the HP 16500B/ 16501A Logic Analysis System at the mainframe level. 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 programming language that allows communications over HP-IB, RS-232C, or the optional HP 16500L LAN Interface Module.

Part 1 General Information

1 Introduction to Programming

Introduction 1–2

Talking to the Logic Analysis System 1–3

Talking to Individual System Modules 1–4 Initialization 1–4 Instruction Syntax 1–6 Output Command 1–6 Device Address 1–7 Instructions 1–7 Instruction Terminator 1–8 Header Types 1–9 Duplicate Keywords 1–10 Query Usage 1–11 Program Header Options 1–12 Parameter Data Types 1–13 Selecting Multiple Subsystems 1–15

Receiving Information from the Logic Analysis System 1–16

Response Header Options 1–17 Response Data Formats 1–18 String Variables 1–19 Numeric Base 1–20 Numeric Variables 1–20 Definite-Length Block Response Data 1–21 Multiple Queries 1–22 System Status 1–23

Contents–1

Contents

2 Programming Over HP-IB

Interface Capabilities 2–3 Command and Data Concepts 2–3 Talk/Listen Addressing 2–3 HP-IB Bus Addressing 2–4 Local, Remote, and Local Lockout 2–5 Bus Commands 2–6

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–5 Cable Examples 3–6 Configuring the Logic Analysis System Interface 3–9 Interface Capabilities 3–10 RS-232C Bus Addressing 3–11 Lockout Command 3–12

4 Programming and Documentation Conventions

Truncation Rule 4–3 Infinity Representation 4–4 Sequential and Overlapped Commands 4–4 Response Generation 4–4 Syntax Diagrams 4–5 Notation Conventions and Definitions 4–5 The Command Tree 4–6 Tree Traversal Rules 4–8 Command Set Organization 4–9 Subsystems 4–10 Program Examples 4–12

Contents–2

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–8 Parallel Poll 6–9 Polling HP-IB Devices 6–11 Configuring Parallel Poll Responses 6–11 Conducting a Parallel Poll 6–12 Disabling Parallel Poll Responses 6–13 HP-IB Commands 6–13

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 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

Contents–3

Contents

*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–10 CESR (Combined Event Status Register) 9–11 EOI (End Or Identify) 9–13 LER (LCL Event Register) 9–13 LOCKout 9–14 MENU 9–15 MESE<N> (Module Event Status Enable) 9–16 MESR<N> (Module Event Status Register) 9–18 RMODe 9–19 RTC (Real-time Clock) 9–20 SELect 9–21 SETColor 9–23 STARt 9–24 STOP 9–25 XWINdow 9–26

10 SYSTem Subsystem

DATA 10–5 DSP (Display) 10–6 ERRor 10–7 HEADer 10–8 LONGform 10–9 PRINt 10–10 SETup 10–12

Contents–4

11 MMEMory Subsystem

AUToload 11–8 CATalog 11–9 CD (Change Directory) 11–10 COPY 11–11 DOWNload 11–12 INITialize 11–14 LOAD [:CONFig] 11–15 LOAD :IASSembler 11–16 MKDir (Make Directory) 11–17 MSI (Mass Storage Is) 11–18 PACK 11–19 PURGe 11–20 PWD (Present Working Directory) 11–21 REName 11–22 STORe [:CONFig] 11–23 UPLoad 11–24 VOLume 11–26

Contents

12 INTermodule Subsystem

:INTermodule 12–4 DELete 12–5 HTIMe 12–6 INPort 12–7 INSert 12–8 PORTEDGE 12–9 PORTLEV 12–10 SKEW<N> 12–11 TREE 12–12 TTIMe 12–13

Contents–5

Contents

Part 3 Programming Examples

13 Programming Examples

Transferring the Mainframe Configuration 13–3 Checking for Intermodule Measurement Completion 13–6 Sending Queries to the Logic Analysis System 13–7 Getting ASCII Data with PRINt? ALL Query 13–9 Reading the disk with the CATalog? ALL query 13–10 Reading the Disk with the CATalog? Query 13–11 Printing to the disk 13–12

Index

Contents–6

Part 1

1 Introduction to Programming 1-1 2 Programming Over HP-IB 2-1 3 Programming Over RS232C 3-1 4 Programming and Documentation Conventions 4-1 5 Message Communication and System Functions 5-1 6 Status Reporting 6-1 7 Error Messages 7-1

General Information

Introduction to Programming

1–1

Introduction

This chapter introduces you to the basics of remote programming and is organized in two sections. The first section, "Talking to the Logic Analysis System," concentrates on initializing the bus, program syntax and the elements of a syntax instuction. The second section, "Receiving Information from the Logic Analysis System," discusses how queries are sent and how to retrieve query results from the system.

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 HP 16500B Logic Analysis System. There are three general categories of use. You can:

• Set up the system and start measurements

• Retrieve setup information and measurement results from the

measurement modules

• Send measurement data to the measurement modules

The instructions listed in this manual give you access to the functions of the mainframe. This programming reference is designed to provide a concise description of each instruction for the mainframe. Individual module instruction descriptions are in the Programmer’s Guide for each respective module.

See Also Refer to the HP 16500L LAN Interface Module User’s Guide if you have the

optional HP 16500L LAN Interface Module.

1–2

Introduction to Programming

Talking to the Logic Analysis System

In general, computers acting as controllers communicate with the instrument by sending and receiving messages over a remote interface, such as HP-IB, RS-232C, or the optional Ethernet LAN interface module.

This guide focuses on the HP-IB and RS-232C interfaces, however, if you plan to communicate over the LAN with the optional HP 16500L LAN Interface Module, you will need to refer to the HP 16500L LAN Interface Module User’s Guide to understand how to send the commands in this guide.

When programming the HP 16500B with the HP 16501A Expansion Frame connected, most of the remote operation of the expansion frame is transparent. The only time a progamming command is affected by the presence of the expansion frame is when the number of slots is specified or returned from a query.

Instructions for programming the system 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 system. For example, HP 9000 Series 300 BASIC uses the OUTPUT statement for sending commands and queries to the system. 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

Introduction to Programming

Talking to Individual System Modules

Talking to individual system modules within the HP 16500B Logic Analysis System is done by preceding the module commands with the SELECT command and the number of the slot in which the desired module is installed. The mainframe is selected in the same way as an installed module by using the SELECT 0 command

Example

To select the module in slot 3 use the following:

OUTPUT XXX;":SELECT 3"

See Also Chapter 6, "Mainframe Commands" for more information on the SELECT

command.

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 HP-IB, CLEAR will also reset the parser in the logic analysis system. The parser is the program resident in the logic analysis system that reads the instructions you send to it from the controller.

After clearing the interface, you could, for example, preset the logic analyzer module 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.

1–4

Introduction to Programming

Initialization

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

exists) into the system.

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

Example Program This program demonstrates a simple HP BASIC command structure used to

program the logic analysis system.

10 CLEAR XXX !Initialize instrument interface 20 OUTPUT XXX;":SYSTEM:HEADER ON"!Turn headers on 30 OUTPUT XXX;":SYSTEM:LONGFORM ON" !Turn longform on 40 DIM Card$[100] !Reserve memory for string variable 50 OUTPUT XXX;":CARDCAGE?" !Verify which modules are loaded 60 ENTER XXX;Card$ !Enter result in a string variable 70 PRINT Card$ !Print result of query 80 OUTPUT XXX;":MMEM:LOAD:CONFIG ’TEST E’,5" !Load configuration file

!into module in slot E 90 OUTPUT XXX;":SELECT 5" !Select module in slot E 100 OUTPUT XXX;":MENU 5,3: !Select menu for module in slot E 60 OUTPUT XXX;":RMODE SINGLE" !Select run mode 70 OU TPUT XXX;":S TART" !Run the me asurement

See Also Chapter 11, "MMEMory Subsystem" for more information on the LOAD

command.

1–5

Figure 1-1

Introduction to Programming

Instruction Syntax

To program the system 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.

Program Message Syntax

Output Command

The output command depends on the language you choose to use. Throughout this guide, HP 9000 Series 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–6

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 HP-IB, see chapter 2, "Programming over HP-IB." If you are using RS-232C, see chapter 3, "Programming Over RS-232C." If you are using the HP 16500L LAN option, see chapter 3 in the HP 16500L User’s Reference.

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 for the mainframe 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–7

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 system.

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–8

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 :RM ODE SINGLE<t erminator>

Introduction to Programming

Header Types

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: <subsystem>:<subsystem>:<function><white_space>

Example :MMEMORY:LOAD:CONFIG "FILE "

1–9

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–10

Introduction to Programming

Query Usage

Logic analysis system instructions that are immediately followed by a question mark (?) are queries. After receiving a query, the logic analysis system parser places the response in the output buffer. The output message remains in the buffer until it is read or until another 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 system is currently configured. They are also used to get results of measurements made by the modules in the system.

Example This instruction places the current full-screen time for machine 1 of the logic

analyzer module, which is in slot 2, in the output buffer.

:SEL EC T 2: MACHINE1:T WA VEFORM:RAN GE?

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 :SELECT 2: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 from the Logic Analysis System."

1–11

Introduction to Programming

Program Header Options

Program headers can be sent using any combination of uppercase or lowercase ASCII characters. System 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 selfdocumenting. 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:

OUT PUT XXX;":SY STEM:HEADER ON;L ONGFORM ON"

Short form:

OUT PUT XXX;":SY ST:HEAD ON;LONG ON "

1–12

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 chapter11). These syntax rules also show how data may be formatted when sent back from the system 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. Do not combine an exponent with a unit.

See Also Tables 5-1 and 5-2 in chapter 5, "Message Communications and System

Functions," list all available suffixes.

Example The following numbers are all equal:

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

The system will recognize binary, octal, and hexadecimal base numbers. The base of a number is specified with a prefix. The recognized prefixes are #B for binary, #Q for octal, and #H for hexadecimal. The absence of a prefix indicates the number is decimal which is the default base.

Example The following numbers are all equal:

#B11100 = #Q34 = #H1C = 28

1–13

Introduction to Programming

Parameter Data Types

You may not specify a base in conjunction with either exponents or unit suffixes. Additionally, negative numbers must be expressed in decimal.

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 can not be used interchangeably. 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 long form or short form (if one exists) may be used. Uppercase and lowercase letters may be mixed freely. When receiving responses, uppercase letters will be used exclusively. The use of long form or short form in a response depends on the setting you last specified via the SYSTem:LONGform command.

1–14

Introduction to Programming

Selecting Multiple Subsystems

You can send multiple program commands and program queries for different subsystems within the same selected module on the same line by separating each command with a semicolon. The colon following the semicolon enables you to enter a new subsystem. <instruction header><data>;

:<instruction header><data><terminator>

Multiple commands may be any combination of simple, compound and common commands.

Example :SELECT 2:MACHINE1:ASSIGN2;:SYSTEM:HEADERS ON

1–15

Introduction to Programming

Selecting Multiple Subsystems

Receiving Information from the Logic Analysis System

After receiving a query (logic analysis system instruction followed by a question mark), the system 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 system’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 :SYSTEM:LONGFORM?, 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–16

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/OFF command. 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 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.

Examples The following examples show some possible responses for a

:SELECT 2:MACHINE1:SFORMAT:THRESHOLD2? query: with HEADER OFF:

with HEADER ON and LONGFORM OFF:

:SE L 2:MACH1:SF OR:THR2 <white_s pace><data><te rminator>

with HEADER ON and LONGFORM ON:

:SEL EC T 2: MACHINE1:S FO RMAT:THRES HOLD2 <white _s pace> <dat a> <t erminator>

See Also Chapter 10, "SYSTem Subsystem" for information on turning the HEADER

and LONGFORM commands on and off.

1–17

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 :SELECT 2:MACHINE1:

TFORMAT: LAB? ’ADDR’ query.

Header on; Longform on

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

Header on;Longform off

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

Header off; Longform on

"ADDR ",19,POSITIVE<terminator>

Header off; Longform off

"ADDR ",19,POS<terminator>

See Also The individual commands in Part 2 of this guide contain information on the

format (alpha or numeric) of the data returned from each query.

1–18

Introduction to Programming

String Variables

Because there are so many ways to code numbers, the HP 16500B Logic Analysis System handles 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 system, 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 slot 3. In BASIC, the & operator is used for string concatenation.

10 LET Machine$ = ":SELECT 3:MACHINE2" !Send all instructions to machine 2 in

!slo t 3 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$.

ENTE R XX X; Result$

In the language used for this guide (HP BASIC 6.2), string variables are casesensitive and must be expressed exactly the same each time they are used.

The output of the system 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–19

Introduction to Programming

Numeric Base

Example The following example shows logic analyzer module data being returned to a

string variable with headers off:

10 OUTPUT XXX;":SYSTEM:HEADER OFF" 20 DI M Rang$[30] 30 OUTPUT XXX;":SELECT 2:MACHINE1:TWAVEFORM:RANGE?" 40 EN TER XXX;Rang $ 50 PR INT 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 on screen. 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.

1–20

Introduction to Programming

Definite-Length Block Response Data

Example The following example shows logic analyzer module data being returned to a

numeric variable.

10 OUTPUT XXX;":SYSTEM:HEADER OFF" 20 OUTPUT XXX;":SELECT 2:MACHINE1:TWAVEFORM:RANGE?" 30 EN TER XXX;Rang 40 PR INT Rang 50 END

This time the format of the number (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 block 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 HP16500B Logic Analysis System.

1–21

Figure 1-2

Introduction to Programming

Multiple Queries

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

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.

Multiple Queries

You can send multiple queries to the system 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.

1–22

Introduction to Programming

System Status

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

System Status

Status registers track the current status of the mainframe and the installed modules. By checking the system status, you can find out whether an operation has been completed, whether a module is receiving triggers, and more.

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

and the installed modules.

1–23

1–24

Programming Over HP-IB

2–1

Introduction

This section describes the interface functions and some general concepts of the HP-IB. In general, these functions are defined by IEEE 488.1 (HP-IB 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

Programming Over HP-IB

Interface Capabilities

The interface capabilities of the HP 16500B, 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 HP-IB 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 commands and responses found in chapters 9 through 12 of this guide for the mainframe and the respective Programmer’s Guides for each module installed in the mainframe.

Talk/Listen Addressing

By using the touchscreen fields in the System Configuration menu, the HP-IB interface can be placed in either talk only mode, "Printer connected to HP-IB," or in addressed talk/listen mode, "Controller connected to HP-IB."

See Also Chapter 4, "The HP-IB and RS-232C Interfaces" in the HP 16500B User’s

Reference)

2–3

Programming Over HP-IB

HP-IB Bus Addressing

Talk only mode must be used when you want the system to talk directly to a printer without the aid of a controller. Addressed talk/listen mode is used when the system will operate in conjunction with a controller. When the system is in the addressed talk/listen mode, the following is true:

Each device on the HP-IB 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.

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.

•

HP-IB Bus Addressing

Because HP-IB 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 HP-IB controllers.

2–4

Programming Over HP-IB

Local, Remote, and Local Lockout

Instrument Address (Selects the Instrument)

Each instrument on the HP-IB 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.

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 analysis system will accept and execute bus commands while in local mode, and the front panel will also be entirely active. If the HP 16500B is in remote mode, the system will go from remote to local with any touchscreen, mouse, or keyboard 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 HP-IB states. It also resets the system to the power-on defaults and purges any acquired data in the acquisition memory of all the installed modules.

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. 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

Programming Over HP-IB

Bus Commands

See Also :SYSTem:LOCKout in chapter 9, "Mainframe Commands"

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 system.

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

Programming Over RS-232C

3–1

Introduction

This chapter describes the interface functions and some general concepts of the RS-232C. The RS-232C interface on this instrument is Hewlett-Packard’s 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

Programming Over RS-232C

Interface Operation

The HP 16500B Logic Analysis System 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 an HP 16500B Logic Analysis System 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 analysis system must remain high for proper operation.

With extended hardwire operation, a high on the CTS input allows the logic analysis system to send data, and a low disables the logic analysis system 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 analysis system 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 HP 16500B Logic Analysis system 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 HP cable recommendations for hardware handshake.

3–3

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 analysis system and the controller. The three-wire interface provides no hardware means to control data flow between the controller and the logic analysis system. 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 analysis system 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 analysis system)

•

Pin 3 RD (Receive Data into logic analysis system)

•

The TD (Transmit Data) line from the logic analysis system must connect to the RD (Receive Data) line on the controller. Likewise, the RD line from the logic analysis system must connect to the TD line on the controller. Internal pull-up resistors in the logic analysis system assure the DCD, DSR, and CTS lines remain high when you are using a three-wire interface.

3–4

Programming Over RS-232C

Extended Interface with Hardware Handshake

With the extended interface, both the software and the hardware can control the data flow between the logic analysis system and the controller. This allows you to have more control of data flow between devices. The logic analysis system uses the following connections on its RS-232C interface for extended interface communication:

Pin 7 SGND (Signal Ground)

•

Pin 2 TD (Transmit Data from logic analysis system)

•

Pin 3 RD (Receive Data into logic analysis system)

•

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 analysis system

•

which can be used to control incoming data flow. Pin 5 CTS (Clear To Send) is an input to the logic analysis system which

•

controls data flow from the logic analysis system. Pin 6 DSR (Data Set Ready) is an input to the logic analysis system

•

which controls data flow from the logic analysis system within two bytes. Pin 8 DCD (Data Carrier Detect) is an input to the logic analysis system

•

which controls data flow from the logic analysis system within two bytes. Pin 20 DTR (Data Terminal Ready) is an output from the logic analysis

•

system which is enabled as long as the logic analysis system is turned on.

The RTS (Request To Send), is an output from the logic analysis system 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 analysis system, which control data flow from the logic analysis system. Internal pull-up resistors in the logic analysis system 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 analysis system to send data to the controller. A low on any one of these

3–5

Programming Over RS-232C

Cable Examples

lines will disable the logic analysis system data transmission. Pulling the CTS line low during data transmission will stop logic analysis system data transmission immediately. Pulling either the DSR or DCD line low during data transmission will stop logic analysis system data transmission, but as many as two additional bytes may be transmitted from the logic analysis system.

Cable Examples

HP 9000 Series 300

Figure 3-1 is an example of how to connect the HP 16500B Logic Analysis System 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 analysis system.

Figure 3-1

Cable Example

3–6

Figure 3-2

Programming Over RS-232C

Cable Examples

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 HP 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

•

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

3–7

Figure 3-3

Programming Over RS-232C

Cable Examples

Figure 3-3 shows the schematic of a 25-pin male to 25-pin male cable 5 meters in length. The following HP cable supports this configuration:

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

•

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

Figure 3-4 shows the schematic of a 9-pin female to 25-pin male cable. The following HP 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

•

3–8

Figure 3-4

Programming Over RS-232C

Configuring the Logic Analysis System Interface

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

Configuring the Logic Analysis System 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 chapter 4, "The HP-IB and RS232-C Interfaces" in the HP 16500B Logic Analysis System User’s Reference.

3–9

Programming Over RS-232C

Interface Capabilities

The baud rate, stop bits, parity, protocol, and data bits must be configured exactly the same for both the controller and the logic analysis system to properly communicate over the RS-232C bus. The RS-232C interface capabilities of the HP 16500B Logic Analysis System 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 data flow. 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 data flow.

XON/XOFF XON/XOFF stands for Transmit On/Transmit Off. With this mode, the receiver (controller or logic analysis system) controls data flow, and, can request that the sender (logic analysis system or controller) stop data flow. 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 HP 16500B Logic Analysis System 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–10

Programming Over RS-232C

RS-232C Bus Addressing

The controller and the HP 16500B Logic Analysis System 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 the RS-232C interface, refer to the HP 16500B

Logic Analysis System User’s Reference. For information on RS-232C voltage levels and connector pinouts, refer to the HP 16500B Logic Analysis System Service Guide.

RS-232C Bus Addressing

The RS-232C address you must use is dependent on the computer or controller you are using to communicate with the logic analysis system.

HP Vectra Personal Computers or compatibles

If you are using an HP Vectra Personal Computer or compatible, it must have an unused serial port to which you connect the logic analysis system’s RS-232C port. The proper address for the serial port is dependent on the hardware configuration of your computer. Additionally, your communications software must be configured to address the proper serial port. Refer to your computer and communications software manuals for more information on setting up your serial port address.

HP 9000 Series 300 Controllers

Each RS-232C interface card for the HP 9000 Series 300 Controller has its own interface select code. This code is used by the controller for directing commands and communications to the proper interface by specifying the correct interface code for the device address.

Generally, the interface select code can be any decimal value between 0 and 31, except for those interface codes which are reserved by the controller for internal peripherals and other internal interfaces. This value can be selected through switches on the interface card. For example, if your RS-232C interface select code is 9, the device address required to communicate over the RS-232C bus is 9. For more information, refer to the reference manual for your interface card or controller.

3–11

Programming Over RS-232C

Lockout Command

To lockout the front-panel controls, use the SYSTem command LOCKout. When this function is on, all controls (except the power switch) are entirely locked out. Local control can only be restored by sending the :LOCKout OFF command.

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

certain RS-232C states. It also resets the logic analysis system to the power-on defaults and purges any acquired data in the acquisition memory of all the installed modules.

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

3–12

Programming and Documentation Conventions

4–1

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

Programming and Documentation Conventions

Truncation Rule

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

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

•

short form. When the long form has more than four characters the short form 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 OFF DATA DATA START STAR LONGFORM LONG DELAY DEL ACCUMULATE ACC

4–3

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 HP 16500B Logic Analysis System 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 HP 16500B Logic Analysis System will buffer responses to a query when it is parsed.

Syntax Diagrams

At the beginning of each chapter in Part 2, "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

4–4

Programming and Documentation Conventions

Notation Conventions and Definitions

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.

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 HP 16500B Logic Analysis System and the relationship of the commands to each other. You should notice that the common commands are not actually connected to the

4–5

Programming and Documentation Conventions

The Command Tree

other commands in the command tree. After a <NL> (linefeed - ASCII decimal 10) has been sent to the instrument, the parser will be set to the root of the command tree. Parameters are not shown in this figure. The command tree allows you to see what the system’s 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.

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.

Figure 4-1

HP 16500B Command Tree

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.

4–6

Programming and Documentation Conventions

Tree Traversal Rules

Command headers are created by traversing down the command tree. A legal command header from the command tree in figure 4-1 would be :MMEMORY:INITIALIZE. This is refered to as a compound header. 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. For example, the colon preceding MMEMORY (:MMEMORY) in the above example 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

4–7

Programming and Documentation Conventions

Tree Traversal Rules

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. For example, the colon separating MMEMORY and INITIALIZE is the location of the parser when this compund header is parsed.

The following examples are written using HP BASIC 6.2 on a HP 9000 Series 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 HEADER is necessary since

SYSTEM:HEADER is a compound command. The semicolon between the HEADER command and the LONGFORM command is the required <program message unit separator> . The LONGFORM command does not need SYSTEM preceding it, since the SYSTEM:HEADER command sets the parser to the SYSTEM node in the tree.

OUT PUT XXX;":SY STEM:HEADER ON;L ONGFORM ON"

4–8

Programming and Documentation Conventions

Command Set Organization

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

STORE command in the compound command. The STORE command 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’"

OUT PUT XXX;":MM EMORY:INITIALI ZE" OUT PUT XXX;":MM EMORY:STORE ’FIL E ’,’FILE DESCRIPTI ON’"

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.

OUT PUT XXX;":MM EM:CATALOG?;:S YSTEM:PRINT ALL"

Command Set Organization

The command set for the HP 16500B Logic Analysis System mainframe is divided into 5 separate groups as shown in figure 4-1. The command groups are: common commands, mainframe commands, and 3 sets of subsystem commands. In addition to the command tree in figure 4-1, a command to subsystem cross-reference is shown in table 4-2.

Each of the 5 groups of commands is described in a seperate chapter in Part 2, "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.

4–9

Programming and Documentation Conventions

Subsystems

The commands are shown in the long form and short form using upper and lowercase letters. As an example, AUToload indicates 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.

Subsystems

There are three subsystems in the mainframe. 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 three subsystems in the HP 16500B Logic Analysis System 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).

•

4–10

Table 4-2

Alphabetic Command Cross-Reference

Programming and Documentation Conventions

Subsystems

*CLS Common *ESE Common *ESR Common *IDN Common *IST Common *OPC Common *OPT Common *PRE Common *RST Common *SRE Common *STB Common *TRG Common *TST Common *WAI Common AUToload MMEMory BEEPer Mainframe CAPability Mainframe CARDcage Mainframe CATalog MMEMory CD MMEMory CESE Mainframe CESR Mainframe COPY MMEMory DATA SYSTem DELete INTermodule DOWNload MMEMory DSP SYSTem EOI Mainframe ERRor SYSTem HEADer SYSTem HTIMe INTermodule INITialize MMEMory INPort INTermodule INSert INTermodule

LER Mainframe LOAD MMEMory LOCKout Mainframe LONGform SYSTem MENU Mainframe MESE Mainframe MESR Mainframe MKDir MMEMory MSI MMEMory PACK MMEMory PORTedge INTermodule PORTlev INTermodule PRINt SYSTem PURGe MMEMory PWD MMEMory REName MMEMory RMODe Mainframe RTC Mainframe SELect Mainframe SETColor Mainframe SKEW INTermodule STARt Mainframe STOP Mainframe STORe MMEMory STup SYSTem TREE INTermodule TTIMe INTermodule UPLoad MMEMory VOLume MMEMory

4–11

Programming and Documentation Conventions

Program Examples

The program examples in chapter 13, "Programming Examples," were written on an HP 9000 Series 300 controller using the HP BASIC 6.2 language. The programs always assume a generic address for the HP 16500B Logic Analysis System 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 logic analyzer’s Timing Waveform Delay

to 100 ms. Keywords in long form, numbers using the decimal format.

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

Keywords in short form, numbers using an exponential format.

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

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

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

In these examples, the colon shown as the first character of the command is optional on the HP 16500B Logic Analysis System. The space between DELay and the argument is required.

4–12

Message Communication and System Functions

5–1

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 analysis system. 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 HP 16500B Logic Analysis System is designed to be compatible with other Hewlett-Packard IEEE 488.2 compatible instruments. Instruments that are compatible with IEEE 488.2 must also be compatible with IEEE 488.1 (HP-IB 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 HP 16500B Logic Analysis System are structured very similar to those described by IEEE 488.2. In most cases, the same structure shown in this chapter for IEEE 488.2 will also work for RS-232C. Because of this, no additional information has been included for RS-232C.

5–2

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 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

Message Communication and System Functions

Protocols

Protocol Overview

The instrument and controller communicate using program messages and response messages. These messages serve as the containers into which sets of program commands or instrument responses are placed. Program messages are sent by the controller to the instrument, and response messages 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. An important 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 messages and response messages. This means that the controller should always terminate a program message before attempting to read a response. The instrument will terminate response messages 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 noted in chapter 1, "Multiple Queries," 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

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 in this chapter is 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

Figure 5-1

Message Communication and System Functions

Syntax Diagrams

Example syntax diagram

5–6

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 units 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.

Multiple data parameters are separated by a comma.

•

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

•

spaces. The header SYSTEM:LONGFORM OFF 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.

See Also Chapter 4, "Programming and Documentation Conventions"

5–7

Figure 5-2

Message Communication and System Functions

Syntax Overview

<program message> Parse Tree

5–8

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 EX 1E15 PE 1E12 T 1E9 G 1E6 MA 1E3 K 1E-3 M 1E-6 U 1E-9 N 1E-12 P 1E-15 F 1E-18 A

5–9

Table 5-2

Message Communication and System Functions

Syntax Overview

Suffix Unit The suffix units that the instrument will accept are shown in table 5-2.

Suffix Referenced Unit

V Volt S Second

5–10

Status Reporting

6–1

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 HP 16500B Logic Analysis System. Also in this chapter is a sample set of steps you use to perform a serial poll over HP-IB.

The status reporting features available over the bus are the serial and parallel polls. 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 register remain set until the register is read or cleared. Registers are 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

Figure 6-1

Status Reporting

Status Byte Structures and Concepts

6–3

Status Reporting

Event Status Register

The Event Status Register is an IEEE 488.2 defined register. The bits in this register are "latched." That is, once an event happens which sets a bit, that 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

Status Reporting

Bit Definitions

MSG - message

Indicates whether there is a message in the message queue (Not implemented in the HP 16500B Logic Analysis System).

PON - power on

Indicates power has been turned on.

URQ - user request

Always returns a 0 from the HP 16500B Logic Analysis System.

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 HP 16500B Logic Analysis System.

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

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.

Figure 6-2.

Service Request Enabling

6–6

Status Reporting

Serial Poll

The HP 16500B Logic Analysis System 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.

Using Serial Poll (HP-IB)

This example will show how to use the service request by conducting a serial poll of all instruments on the HP-IB bus. In this example, assume that there are two instruments on the bus: the logic analyzsis system 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 analysis system 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 HP-IB Status Register into the

6–7

Status Reporting

Parallel Poll

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 HP 16500B Logic Analysis System 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.

Parallel Poll

Parallel poll is a controller initiated operation which is used to obtain information from several devices simultaneously. When a controller initiates a Parallel Poll, each device returns a Status Bit via one of the DIO data lines. Device DIO assignments are made by the controller using the PPC (Parallel Poll Configure) sequence. Devices respond either individually, each on a separate DIO line; collectively on a single DIO line; or any combination of these two ways. When responding collectively, the result is a logical AND (True High) or logical OR (True Low) of the groups of status bits.

6–8

Status Reporting

Parallel Poll

Figure 6-3 shows the Parallel Poll Data Structure. The summary bit is sent in response to a Parallel Poll. This summary bit is the "ist" (individual status) local message.

The Parallel Poll Enable Register determines which events are summarized in the ist. The *PRE command is used to write to the enable register and the *PRE? query is used to read the register. The *IST? query can be used to read the "ist" without doing a parallel poll.

6–9

Figure 6-3

Status Reporting

Parallel Poll

Parallel Poll Data Structure

6–10

Status Reporting

Polling HP-IB Devices

Parallel Poll is the fastest means of gathering device status when several devices are connected to the bus. Each device (with this capability) can be programmed to respond with one bit of status when parallel polled. This makes it possible to obtain the status of several devices in one operation. If a device responds affirmatively to a parallel poll, more information about its specific status can be obtained by conducting a serial poll of the device.

Configuring Parallel Poll Responses

Certain devices, including the HP 16500B Logic Analysis System, can be remotely programmed by a controller to respond to a parallel poll. A device which is currently configured for a parallel poll responds to the poll by placing its current status on one of the bus data lines. The response and the data-bit number can then be programmed by the PPC (parallel poll configure) statement. No multiple listeners can be specified in this statement. If more than one device is to respond on a single bit, each device must be configured with a separate PPC statement.

Example ASSIGN @Device TO 707

PPOL L CO NF IGURE @Devic e; Mask

6–11

Status Reporting

Conducting a Parallel Poll

The value of Mask (any numeric expression can be specified) is first rounded and then used to configure the device’s parallel response. The least significant 3 bits (bits 0 through 2) of the expression are used to determine which data line the device is to respond on (place its status on). Bit 3 specifies the "true" state of the parallel poll response bit of the device. A value of 0 implies that the device’s response is 0 when its status bit message is true.

Example The following statement configures the device at address 07 on the interface

select code 7 to respond by placing a 0 on bit 4 when its status response is "true."

PPOL L CO NF IGURE 707;4

Conducting a Parallel Poll

The PPOLL (Parallel Poll) function returns a single byte containing up to 8 status bit messages for all devices on the bus capable of responding to the poll. Each bit returned by the function corresponds to the status bit of the device(s) configured to respond to the parallel poll (one or more devices can respond on a single line). The PPOLL function can only be executed by the controller. It is initiated by the simultaneous assertion of ATN and EOI.

Example Res ponse = PPOLL( 7)

6–12

Disabling Parallel Poll Responses

The PPU (Parallel Poll Unconfigure) statement gives the controller the capability of disabling the parallel poll responses of one or more devices on the bus.

Examples The following statement disables device 5 only:

PPOL L UN CO NFIGURE 705

This statement disables all devices on interface select code 8 from responding to a parallel poll:

PPOL L UN CO NFIGURE 8

If no primary address is specified, all bus devices are disabled from responding to a parallel poll. If a primary address is specified, only the specified devices (which have the parallel poll configure capability) are disabled.

Status Reporting

Disabling Parallel Poll Responses

HP-IB Commands

The following paragraphs describe actual HP-IB commands which can be used to perform the functions of the Basic commands shown in the previous examples.

Parallel Poll Unconfigure Command

The parallel poll unconfigure command (PPU) resets all parallel poll devices to the idle state (unable to respond to a parallel poll).

Parallel Poll Configure Command

The parallel poll configure command (PPC) causes the addressed listener to be configured according to the parallel poll enable secondary command PPE.

6–13

Status Reporting

HP-IB Commands

Parallel Poll Enable Command

The parallel poll enable secondary command (PPE) configures the devices which have received the PPC command to respond to a parallel poll on a particular HP-IB DIO line with a particular level.

Parallel Poll Disable Command

The parallel poll disable secondary command (PPD) disables the devices which have received the PPC command from responding to the parallel poll.

Table 6-1

Parallel Poll Commands

Command Mnemonic Decimal

Code

Parallel Poll Unconfigure (Multiline Command)

Parallel Poll Configure (Addressed Command)

Parallel Poll Enable (Secondary Command)

Parallel Poll Disable (Secondary Command)

PPU 21 NAK

PPC 05 ENQ

PPE 96-111 I-O

PPD 112 P

ASCII/ISO Character

6–14

Error Messages

7–1

Introduction

This chapter lists the error messages that relate to the HP 16500B Logic Analysis System.

7–2

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

Error Messages

7–3

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

7–4

–320 ROM error –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

Error Messages

Query Errors

7–5

7–6

Part 2

8 Common Commands 8-1

9 Mainframe Commands 9-1 10 SYSTem Subsystem 10-1 11 MMEMory Subsystem 11-1 12 INTermodule Subsystem 12-1

Commands

Common Commands

8–1

Agilent 16500B Data Sheet

Specifications and Main Features

Frequently Asked Questions

User Manual

In This Book

Contents

General Information

Introduction to Programming

Talking to the Logic Analysis System

Talking to Individual System Modules

Initialization

Instruction Syntax

Output Command

Device Address

Instructions

Instruction Terminator

Header Types

Duplicate Keywords

Query Usage

Program Header Options

Parameter Data Types

Selecting Multiple Subsystems

Receiving Information from the Logic Analysis System

Response Header Options

Response Data Formats

String Variables

Numeric Base

Numeric Variables

Definite-Length Block Response Data

Multiple Queries

System Status

Programming Over HP-IB

Interface Capabilities

Command and Data Concepts

Talk/Listen Addressing

HP-IB Bus Addressing

Local, Remote, and Local Lockout

Bus Commands

Programming Over RS-232C

Interface Operation

RS-232C Cables

Minimum Three-Wire Interface with Software Protocol

Extended Interface with Hardware Handshake

Cable Examples

Configuring the Logic Analysis System Interface

Interface Capabilities

RS-232C Bus Addressing

Lockout Command

Programming and Documentation Conventions

Truncation Rule

Infinity Representation

Sequential and Overlapped Commands

Response Generation

Syntax Diagrams

Notation Conventions and Definitions

The Command Tree

Tree Traversal Rules

Command Set Organization

Subsystems

Program Examples

Message Communication and System Functions

Protocols

Syntax Diagrams

Syntax Overview

Status Reporting

Event Status Register

Service Request Enable Register

Bit Definitions

Key Features

Serial Poll

Parallel Poll

Polling HP-IB Devices

Configuring Parallel Poll Responses

Conducting a Parallel Poll

Disabling Parallel Poll Responses

HP-IB Commands

Error Messages

Device Dependent Errors

Command Errors

Execution Errors