Programmer’s Guide Publication number 01660-97033 Second edition, January 2000 For Safety information, Warranties, and Regulatory information, see the pages behind the index Copyright Agilent Technologies 1992-2000 All Rights Reserved Agilent Technologies 1660A/AS-Series Logic Analyzers
ii
In This Book This programmer’s guide contains general information, mainframe level commands, logic analyzer commands, oscilloscope module commands, and programming examples for programming the 1660-series logic analyzers. This guide focuses on how to program the instrument over the GPIB and the RS-232C interfaces. Instruments covered by the 1660-Series Programmer’s Guide The 1660-series logic analyzers are available with or without oscilloscope measurement capabilities.
If you are already familiar with IEEE 488.2 programming and GPIB or RS-232C, you may want to just scan these chapters. If you are new to programmiung the system, you should read part 1. Chapter 1 is divided into two sections. The first section, "Talking to the Instrument," concentrates on program syntax, and the second section, "Receiving Information from the Instrument," discusses how to send queries and how to retrieve query results from the instrument.
The commands explained in this part give you access to all the commands used to operate the oscilloscope portion of the 1660-series system. This part is designed to provide a concise description of each command. Part 5 Part 5, chapter 36 contains program examples of actual tasks that show you how to get started in programming the 1660-series logic analyzers. The complexity of your programs and the tasks they accomplish are limited only by your imagination. These examples are written in HP BASIC 6.
vi
29 CHANnel Subsystem 30 DISPlay Subsystem 31 MARKer Subsystem 32 MEASure Subsystem 33 TIMebase Subsystem 34 TRIGger Subsystem 35 WAVeform Subsystem 36 Programming Examples Index vii
viii
Contents Part 1 General Information 1 Introduction to Programming Talking to the Instrument 1–3 Initialization 1–4 Instruction Syntax 1–5 Output Command 1–5 Device Address 1–6 Instructions 1–6 Instruction Terminator 1–7 Header Types 1–8 Duplicate Keywords 1–9 Query Usage 1–10 Program Header Options 1–11 Parameter Data Types 1–12 Selecting Multiple Subsystems 1–14 Receiving Information from the Instrument 1–15 Response Header Options 1–16 Response Data Formats 1–17 String Variables 1–18 Numeric Base 1–19 N
Contents 3 Programming Over RS-232C Interface Operation 3–3 RS-232C Cables 3–3 Minimum Three-Wire Interface with Software Protocol 3–4 Extended Interface with Hardware Handshake 3–4 Cable Examples 3–6 Configuring the Logic Analzer Interface 3–8 Interface Capabilities 3–9 RS-232C Bus Addressing 3–10 Lockout Command 3–11 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–4 Notation Conve
Contents 7 Error Messages Device Dependent Errors 7–3 Command Errors 7–3 Execution Errors 7–4 Internal Errors 7–4 Query Errors 7–5 Part 2 Mainframe Commands 8 Common Commands *CLS (Clear Status) 8–5 *ESE (Event Status Enable) 8–6 *ESR (Event Status Register) 8–7 *IDN (Identification Number) 8–9 *IST (Individual Status) 8–9 *OPC (Operation Complete) 8–11 *OPT (Option Identification) 8–12 *PRE (Parallel Poll Enable Register Enable) 8–13 *RST (Reset) 8–14 *SRE (Service Request Enable) 8–15 *STB (Status Byte)
Contents MESE (Module Event Status Enable) 9–14 MESR (Module Event Status Register) 9–16 RMODe 9–18 RTC (Real-time Clock) 9–19 SELect 9–20 SETColor 9–22 STARt 9–23 STOP 9–24 10 SYSTem Subsystem DATA 10–5 DSP (Display) 10–6 ERRor 10–7 HEADer 10–8 LONGform 10–9 PRINt 10–10 SETup 10–11 11 MMEMory Subsystem AUToload 11–8 CATalog 11–9 COPY 11–10 DOWNload 11–11 INITialize 11–13 LOAD [:CONFig] 11–14 LOAD :IASSembler 11–15 MSI (Mass Storage Is) 11–16 PACK 11–17 PURGe 11–17 REName 11–18 STORe [:CONFig] 11–1
Contents 12 INTermodule Subsystem :INTermodule 12–5 DELete 12–5 HTIMe 12–6 INPort 12–6 INSert 12–7 SKEW 12–8 TREE 12–9 TTIMe 12–10 Part 3 Logic Analyzer Commands 13 MACHine Subsystem MACHine 13–4 ARM 13–5 ASSign 13–5 LEVelarm 13–6 NAME 13–7 REName 13–8 RESource 13–9 TYPE 13–10 14 WLISt Subsystem WLISt 14–4 DELay 14–5 INSert 14–6 LINE 14–7 OSTate 14–8 OTIMe 14–8 RANGe 14–9 REMove 14–10 XOTime 14–10 XSTate 14–11 XTIMe 14–11 Contents–5
Contents 15 SFORmat Subsystem SFORmat 15–6 CLOCk 15–6 LABel 15–7 MASTer 15–9 MODE 15–10 MOPQual 15–11 MQUal 15–12 REMove 15–13 SETHold 15–13 SLAVe 15–15 SOPQual 15–16 SQUal 15–17 THReshold 15–18 16 STRigger (STRace) Subsystem Qualifier 16–7 STRigger (STRace) 16–9 ACQuisition 16–9 BRANch 16–10 CLEar 16–12 FIND 16–13 RANGe 16–14 SEQuence 16–16 STORe 16–17 TAG 16–18 TAKenbranch 16–19 TCONtrol 16–20 TERM 16–21 TIMER 16–22 TPOSition 16–23 17 SLISt Subsystem SLISt 17–7 COLumn 17–7 Contents–6
Contents CLRPattern 17–8 DATA 17–9 LINE 17–9 MMODe 17–10 OPATtern 17–11 OSEarch 17–12 OSTate 17–13 OTAG 17–13 OVERlay 17–14 REMove 17–15 RUNTil 17–15 TAVerage 17–17 TMAXimum 17–17 TMINimum 17–18 VRUNs 17–18 XOTag 17–19 XOTime 17–19 XPATtern 17–20 XSEarch 17–21 XSTate 17–22 XTAG 17–22 18 SWAVeform Subsystem SWAVeform 18–4 ACCumulate 18–5 ACQuisition 18–5 CENTer 18–6 CLRPattern 18–6 CLRStat 18–7 DELay 18–7 INSert 18–8 RANGe 18–8 REMove 18–9 TAKenbranch 18–9 TPOSition 18–10 Contents–7
Contents 19 SCHart Subsystem SCHart 19–4 ACCumulate 19–4 HAXis 19–5 VAXis 19–7 20 COMPare Subsystem COMPare 20–4 CLEar 20–5 CMASk 20–5 COPY 20–6 DATA 20–7 FIND 20–9 LINE 20–10 MENU 20–10 RANGe 20–11 RUNTil 20–12 SET 20–13 21 TFORmat Subsystem TFORmat 21–4 ACQMode 21–5 LABel 21–6 REMove 21–7 THReshold 21–8 22 TTRigger (TTRace) Subsystem Qualifier 22–6 TTRigger (TTRace) ACQuisition 22–9 BRANch 22–9 CLEar 22–12 FIND 22–13 GLEDge 22–14 RANGe 22–15 Contents–8 22–8
Contents SEQuence 22–17 SPERiod 22–18 TCONtrol 22–19 TERM 22–20 TIMER 22–21 TPOSition 22–22 23 TWAVeform Subsystem TWAVeform 23–7 ACCumulate 23–7 ACQuisition 23–8 CENTer 23–8 CLRPattern 23–9 CLRStat 23–9 DELay 23–9 INSert 23–10 MMODe 23–11 OCONdition 23–12 OPATtern 23–13 OSEarch 23–14 OTIMe 23–15 RANGe 23–16 REMove 23–16 RUNTil 23–17 SPERiod 23–18 TAVerage 23–19 TMAXimum 23–19 TMINimum 23–20 TPOSition 23–20 VRUNs 23–21 XCONdition 23–22 XOTime 23–22 XPATtern 23–23 XSEarch 23–24 XTIMe 23–25 Contents–9
Contents 24 TLISt Subsystem TLISt 24–7 COLumn 24–7 CLRPattern 24–8 DATA 24–9 LINE 24–9 MMODe 24–10 OCONdition 24–11 OPATtern 24–11 OSEarch 24–12 OSTate 24–13 OTAG 24–14 REMove 24–14 RUNTil 24–15 TAVerage 24–16 TMAXimum 24–16 TMINimum 24–17 VRUNs 24–17 XCONdition 24–18 XOTag 24–18 XOTime 24–19 XPATtern 24–19 XSEarch 24–20 XSTate 24–21 XTAG 24–22 25 SYMBol Subsystem SYMBol 25–4 BASE 25–5 PATTern 25–6 RANGe 25–6 REMove 25–7 WIDTh 25–8 Contents–10
Contents 26 DATA and SETup Commands Data Format 26–3 :SYSTem:DATA 26–4 Section Header Description 26–6 Section Data 26–6 Data Preamble Description 26–6 Acquisition Data Description 26–10 Time Tag Data Description 26–12 Glitch Data Description 26–14 SYSTem:SETup 26–15 RTC_INFO Section Description 26–17 Part 4 Oscilloscope Commands 27 Oscilloscope Root Level Commands AUToscale 27–3 DIGitize 27–5 28 ACQuire Subsystem COUNt 28–4 TYPE 28–4 29 CHANnel Subsystem COUPling 29–4 ECL 29–5 OFFSet 29–6 PROBe 29–7 RA
Contents LABel 30–7 MINus 30–8 OVERlay 30–8 PLUS 30–9 REMove 30–9 31 MARKer Subsystem AVOLt 31–6 ABVolt? 31–7 BVOLt 31–7 CENTer 31–8 MSTats 31–8 OAUTo 31–9 OTIMe 31–10 RUNTil 31–11 SHOW 31–12 TAVerage? 31–12 TMAXimum? 31–13 TMINimum? 31–13 TMODe 31–14 VMODe 31–15 VOTime? 31–16 VRUNs? 31–16 VXTime? 31–17 XAUTo 31–18 XOTime? 31–19 XTIMe 31–19 32 MEASure Subsystem ALL? 32–5 FALLtime? 32–6 FREQuency? 32–6 NWIDth? 32–7 OVERshoot? 32–7 PERiod? 32–8 PREShoot? 32–8 Contents–12
Contents PWIDth? 32–9 RISetime? 32–9 SOURce 32–10 VAMPlitude? 32–11 VBASe? 32–11 VMAX? 32–12 VMIN? 32–12 VPP? 32–13 VTOP? 32–13 33 TIMebase Subsystem DELay 33–4 MODE 33–5 RANGe 33–6 34 TRIGger Subsystem CONDition 34–5 DELay 34–7 LEVel 34–8 LOGic 34–10 MODE 34–11 PATH 34–12 SLOPe 34–12 SOURce 34–13 35 WAVeform Subsystem Format for Data Transfer 35–4 Data Conversion 35–6 COUNt? 35–9 DATA? 35–9 FORMat 35–10 POINts? 35–10 PREamble? 35–11 RECord 35–12 SOURce 35–12 Contents–13
Contents SPERiod? 35–13 TYPE? 35–13 VALid? 35–14 XINCrement? 35–15 XORigin? 35–16 XREFerence? 35–16 YINCrement? 35–17 YORigin? 35–17 YREFerence? 35–18 Part 5 Programming Examples 36 Programming Examples Making a Timing analyzer measurement 36–3 Making a State analyzer measurement 36–5 Making a State Compare measurement 36–9 Transferring the logic analyzer configuration 36–14 Transferring the logic analyzer acquired data 36–17 Checking for measurement completion 36–21 Sending queries to the logic analyzer
Part 1 General Information
1 Introduction to Programming
Introduction This chapter introduces you to the basics of remote programming and is organized in two sections. The first section, "Talking to the Instrument," concentrates on initializing the bus, program syntax and the elements of a syntax instuction. The second section, "Receiving Information from the Instrument," discusses how queries are sent and how to retrieve query results from the mainframe instruments. The programming instructions explained in this book conform to IEEE Std 488.
Talking to the Instrument In general, computers acting as controllers communicate with the instrument by sending and receiving messages over a remote interface, such as GPIB or RS-232C. Instructions for programming the 1660-series logic analyzers will normally appear as ASCII character strings embedded inside the output statements of a "host" language available on your controller. The host language’s input statements are used to read in responses from the 1660-series logic analyzers.
Introduction to Programming Initialization Initialization To make sure the bus and all appropriate interfaces are in a known state, begin every program with an initialization statement. BASIC provides a CLEAR command that clears the interface buffer. If you are using GPIB, CLEAR will also reset the parser in the logic analyzer. The parser is the program resident in the logic analyzer that reads the instructions you send to it from the controller.
Introduction to Programming Instruction Syntax Instruction Syntax To program the logic analyzer remotely, you must have an understanding of the command format and structure. The IEEE 488.2 standard governs syntax rules pertaining to how individual elements, such as headers, separators, parameters and terminators, may be grouped together to form complete instructions. Syntax definitions are also given to show how query responses will be formatted.
Introduction to Programming Device Address 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.
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.
Introduction to Programming Header Types 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.
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: * No white space or separator is allowed between the asterisk and the command header. *CLS is an example of a common command header.
Introduction to Programming Query Usage Query Usage Logic analyzer instructions that are immediately followed by a question mark (?) are queries. After receiving a query, the logic analyzer parser places the response in the output buffer. The output message remains in the buffer until it is read or until another logic analyzer instruction is issued. When read, the message is transmitted across the bus to the designated listener (typically a controller).
Introduction to Programming Program Header Options Program Header Options Program headers can be sent using any combination of uppercase or lowercase ASCII characters. Logic analyzer responses, however, are always returned in uppercase. Both program command and query headers may be sent in either long form (complete spelling), short form (abbreviated spelling), or any combination of long form and short form. Programs written in long form are easily read and are almost selfdocumenting.
Introduction to Programming Parameter Data Types Parameter Data Types There are three main types of data which are used in parameters. They are numeric, string, and keyword. A fourth type, block data, is used only for a few instructions: the DATA and SETup instructions in the SYSTem subsystem (see chapter 10); the CATalog, UPLoad, and DOWNload instructions in the MMEMory subsystem (see chapter 11).
Introduction to Programming Parameter Data Types When a syntax definition specifies that a number is an integer, that means that the number should be whole. Any fractional part would be ignored, truncating the number. Numeric parameters that accept fractional values are called real numbers. All numbers are expected to be strings of ASCII characters. Thus, when sending the number 9, you send a byte representing the ASCII code for the character "9" (which is 57, or 0011 1001 in binary).
Introduction to Programming Selecting Multiple Subsystems Selecting Multiple Subsystems You can send multiple program commands and program queries for different subsystems on the same line by separating each command with a semicolon. The colon following the semicolon enables you to enter a new subsystem. ;: Multiple commands may be any combination of simple, compound and common commands.
Receiving Information from the Instrument After receiving a query (logic analyzer instruction followed by a question mark), the logic analyzer interrogates the requested function and places the answer in its output queue. The answer remains in the output queue until it is read, or, until another command is issued. When read, the message is transmitted across the bus to the designated listener (typically a controller).
Introduction to Programming Response Header Options 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 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.
Introduction to Programming Response Data Formats Response Data Formats Both numbers and strings are returned as a series of ASCII characters, as described in the following sections. Keywords in the data are returned in the same format as the header, as specified by the LONGform command. Like the headers, the keywords will always be in uppercase. Examples The following are possible responses to the MACHINE1: TFORMAT: LAB? ’ADDR’ query.
Introduction to Programming String Variables String Variables Because there are so many ways to code numbers, the 1660-series logic analyzers handle almost all data as ASCII strings. Depending on your host language, you may be able to use other types when reading in responses. Sometimes it is helpful to use string variables in place of constants to send instructions to the 1660-series logic analyzers, such as, including the headers with a query response.
Introduction to Programming Numeric Base Example The following example shows logic analyzer data being returned to a string variable with headers off: 10 20 30 40 50 60 OUTPUT XXX;":SYSTEM:HEADER OFF" DIM Rang$[30] OUTPUT XXX;":MACHINE1:TWAVEFORM:RANGE?" ENTER XXX;Rang$ PRINT Rang$ END After running this program, the controller displays: +1.00000E-05 Numeric Base Most numeric data will be returned in the same base as shown onscreen.
Introduction to Programming Definite-Length Block Response Data This time the format of the number (such as, whether or not exponential notation is used) is dependant upon your host language. In Basic, the output will look like: 1.E-5 Definite-Length Block Response Data Definite-length block response data, also refered to as block data, allows any type of device-dependent data to be transmitted over the system interface as a series of data bytes.
Introduction to Programming Multiple Queries Multiple Queries You can send multiple queries to the logic analyzer within a single program message, but you must also read them back within a single program message. This can be accomplished by either reading them back into a string variable or into multiple numeric variables.
Introduction to Programming Instrument Status Instrument Status Status registers track the current status of the logic analyzer. By checking the instrument status, you can find out whether an operation has been completed, whether the instrument is receiving triggers, and more. Chapter 6, "Status Reporting," explains how to check the status of the instrument.
2 Programming Over GPIB
Introduction This section describes the interface functions and some general concepts of the GPIB. In general, these functions are defined by IEEE 488.1 (GPIB bus standard). They deal with general bus management issues, as well as messages which can be sent over the bus as bus commands.
Programming Over GPIB Interface Capabilities Interface Capabilities The interface capabilities of the 1660-series logic analyzers, as defined by IEEE 488.1 are SH1, AH1, T5, TE0, L3, LE0, SR1, RL1, PP0, DC1, DT1, C0, and E2. Command and Data Concepts The GPIB has two modes of operation: command mode and data mode. The bus is in command mode when the ATN line is true. The command mode is used to send talk and listen addresses and various bus commands, such as a group execute trigger (GET).
Programming Over GPIB Communicating Over the GPIB Bus (HP 9000 Series 200/300 Controller) If the controller addresses the instrument to talk, it will remain configured to talk until it receives: • • • • an interface clear message (IFC) another instrument’s talk address (OTA) its own listen address (MLA) a universal untalk (UNT) command.
Programming Over GPIB Local, Remote, and Local Lockout Example For example, if the instrument address is 4 and the interface select code is 7, the instruction will cause an action in the instrument at device address 704. DEVICE ADDRESS = (Interface Select Code) X 100 + (Instrument Address) Local, Remote, and Local Lockout The local, remote, and remote with local lockout modes may be used for various degrees of front-panel control while a program is running.
Programming Over GPIB Bus 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 logic analyzer. Device Clear The device clear (DCL) or selected device clear (SDC) commands clear the input and output buffers, reset the parser, clear any pending commands, and clear the Request-OPC flag.
3 Programming Over RS-232C
Introduction This chapter describes the interface functions and some general concepts of the RS-232C. The RS-232C interface on this instrument is Agilent Technologies’ implementation of EIA Recommended Standard RS-232C, "Interface Between Data Terminal Equipment and Data Communications Equipment Employing Serial Binary Data Interchange." With this interface, data is sent one bit at a time, and characters are not synchronized with preceding or subsequent data characters.
Programming Over RS-232C Interface Operation Interface Operation The 1660-series logic analyzers can be programmed with a controller over RS-232C using either a minimum three-wire or extended hardwire interface. The operation and exact connections for these interfaces are described in more detail in the following sections.
Programming Over RS-232C Minimum Three-Wire Interface with Software Protocol Minimum Three-Wire Interface with Software Protocol With a three-wire interface, the software (as compared to interface hardware) controls the data flow between the logic analyzer and the controller. The three-wire interface provides no hardware means to control data flow between the controller and the logic analyzer. Therefore, XON/OFF protocol is the only means to control this data flow.
Programming Over RS-232C Extended Interface with Hardware Handshake • Pin 7 SGND (Signal Ground) • Pin 2 TD (Transmit Data from logic analyzer) • Pin 3 RD (Receive Data into logic analyzer) The additional lines you use depends on your controller’s implementation of the extended hardwire interface. • Pin 4 RTS (Request To Send) is an output from the logic analyzer which can be used to control incoming data flow.
Programming Over RS-232C Cable Examples Cable Examples HP 9000 Series 300 Figure 3-1 is an example of how to connect the 1660-series logic analyzer to the HP 98628A Interface card of an HP 9000 series 300 controller. For more information on cabling, refer to the reference manual for your specific controller. Because this example does not have the correct connections for hardware handshake, you must use the XON/XOFF protocol when connecting the logic analyzer.
Programming Over RS-232C Cable Examples Figure 3-2 25-pin (F) to 25-pin (M) Cable Figure 3-3 shows the schematic of a 25-pin male to 25-pin male cable 5 meters in length.
Programming Over RS-232C Configuring the Logic Analzer Interface Figure 3-4 shows the schematic of a 9-pin female to 25-pin male cable. The following cables support this configuration: • HP 24542G, DB-9(F) to DB-25(M), 3 meter • HP 24542H, DB-9(F) to DB-25(M), 3 meter, shielded • HP 45911-60009, DB-9(F) to DB-25(M), 1.
Programming Over RS-232C Interface Capabilities Interface Capabilities The baud rate, stopbits, parity, protocol, and databits must be configured exactly the same for both the controller and the logic analyzer to properly communicate over the RS-232C bus. The RS-232C interface capabilities of the 1660-series logic analyzers are listed below: • • • • • Baud Rate: 110, 300, 600, 1200, 2400, 4800, 9600, or 19.2k Stop Bits: 1, 1.
Programming Over RS-232C RS-232C Bus Addressing The controller and the 1660-series logic analyzer must be in the same bit mode to properly communicate over the RS-232C. This means that the controller must have the capability to send and receive 8 bit data. See Also For more information on the RS-232C interface, refer to the Agilent Technologies 1660-Series Logic Analyzer User’s Reference.
Programming Over RS-232C Lockout Command 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.
3–12
4 Programming and Documentation Conventions
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.
Programming and Documentation Conventions Truncation Rule Truncation Rule The truncation rule for the keywords used in headers and parameters is: • If the longform has four or fewer characters, there is no change in the shortform. When the longform has more than four characters the shortform is just the first four characters, unless the fourth character is a vowel. In that case only the first three characters are used. There are some commands that do not conform to the truncation rule by design.
Programming and Documentation Conventions Infinity Representation 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.
Programming and Documentation Conventions Notation Conventions and Definitions 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.
Programming and Documentation Conventions Tree Traversal Rules Command Types As shown in chapter 1, "Header Types," there are three types of headers. Each header has a corresponding command type. This section shows how they relate to the command tree. System Commands The system commands reside at the top level of the command tree. These commands are always parsable if they occur at the beginning of a program message, or are preceded by a colon. START and STOP are examples of system commands.
Programming and Documentation Conventions Tree Traversal Rules The following examples are written using HP BASIC 6.2 on a HP 9000 Series 200/300 Controller. The quoted string is placed on the bus, followed by a carriage return and linefeed (CRLF). The three Xs (XXX) shown in this manual after an ENTER or OUTPUT statement represents the device address required by your controller. Example 1 In this example, the colon between SYSTEM and HEADER is necessary since SYSTEM:HEADER is a compound command.
Programming and Documentation Conventions Tree Traversal Rules Figure 4-1 1660-Series Logic Analyzer Command Tree 4–8
Programming and Documentation Conventions Tree Traversal Rules Figure 4-1 (continued) 1660-Series Logic Analyzer Command Tree (continued) 4–9
Programming and Documentation Conventions Tree Traversal Rules Figure 4-1 (continued) 1660-Series Logic Analyzer Command Tree (continued) 4–10
Programming and Documentation Conventions Tree Traversal Rules Table 4-2 Alphabetic Command Cross-Reference Command ABVOLt ACCumulate ACQMode ACQuisition ALL ARM ASSign AUToload AUToscale AVOLt BASE BEEPer BRANch BVOLt CAPability CARDcage CATalog CENTer CESE CESR CLEar CLOCk CLRPattern CLRStat CMASk COLumn CONDition CONNect COPY COUNt COUPling DATA DELay DELete DIGitize DOWNload Subsystem MARKer SCHart, SWAVeform, TWAVeform, DISPlay TFORmat STRigger, SWAVeform, TTRigger, TWAVeform MEASure MACHine MACHine
Programming and Documentation Conventions Tree Traversal Rules Table 4-2 (continued) Alphabetic Command Cross-Reference (continued) Command INITialize INPort INSert LABel LER LEVel LEVelarm LINE LOAD LOCKout LOGic LONGform MASTer MENU MESE MESR MINus MMODe MODE MOPQual MQUal MSI MSTats NAME NWIDth OAUTo OCONdition OFFSet OPATtern OSEarch OSTate OTAG OTIMe OVERlay OVERshoot PACK PATH PERiod PATTern Subsystem MMEMory INTermodule INTermodule, SWAVeform, TWAVeform, WLISt, DISPlay SFORmat, TFORmat, DISPlay Mai
Programming and Documentation Conventions Tree Traversal Rules Table 4-2 (continued) Alphabetic Command Cross-Reference (continued) Command REMove REName REName RESource RISetime RMODe RTC RUNTil SELect SEQuence SET SETColor SETHold SETup SHOW SKEW SLAVe SLOPe SOPQual SOURce SPERiod SQUal STARt STOP STORe TAG TAKenbranch TAVerage TCONtrol TERM THReshold TIMER TMAXimum TMINimum TMODe Subsystem SFORmat, SLISt, SWAVeform, SYMBol, TFORmat, TLISt, TWAVeform, DISPlay MACHine MMEMory MACHine MEASure Mainframe Ma
Programming and Documentation Conventions Command Set Organization Table 4-2 (continued) Alphabetic Command Cross-Reference (continued) Command VMAX VMIN VMODe VOLume VOTime VPP VRUNs VTOP VXTime WIDTh XAUTo XCONdition XINCrement Subsystem MEASure MEASure MARKer MMEMory MARKer MEASure SLISt, TLISt, TWAVeform, MARKer MEASure MARKer SYMBol MARKer TLISt, TWAVeform WAVeform XORigin XOTag XOTime XPATtern XREFerence WAVeform SLISt, TLISt SLISt, TLISt, TWAVeform, WLISt, MARKer SLISt, TLISt, TWAVeform WAVeform
Programming and Documentation Conventions Subsystems Subsystems There are 23 subsystems in this instrument. In the command tree (figure 4-1) they are shown as branches, with the node above showing the name of the subsystem. Only one subsystem may be selected at a time. At power on, the command parser is set to the root of the command tree; therefore, no subsystem is selected.
Programming and Documentation Conventions Program Examples • TRIGger - allows access to the oscilloscope’s trigger functions. • WAVeform - used to transfer waveform data from the oscilloscope to a controller. Program Examples The program examples in the following chapters and chapter 36, "Programming Examples," were written on an HP 9000 Series 200/300 controller using the HP BASIC 6.2 language. The programs always assume a generic address for the 1660-series logic analyzers of XXX.
5 Message Communication and System Functions
Introduction This chapter describes the operation of instruments that operate in compliance with the IEEE 488.2 (syntax) standard. It is intended to give you enough basic information about the IEEE 488.2 Standard to successfully program the logic analyzer. You can find additional detailed information about the IEEE 488.2 Standard in ANSI/IEEE Std 488.2-1987, "IEEE Standard Codes, Formats, Protocols, and Common Commands.
Message Communication and System Functions Protocols 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.
Message Communication and System Functions Protocols Protocol Overview The instrument and controller communicate using s and s. These messages serve as the containers into which sets of program commands or instrument responses are placed. s are sent by the controller to the instrument, and s are sent from the instrument to the controller in response to a query message.
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.
Message Communication and System Functions Syntax Diagrams Figure 5-1 Example syntax diagram 5–6
Message Communication and System Functions Syntax Overview 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.
Message Communication and System Functions Syntax Overview Figure 5-2 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. is defined to be one or more characters from the ASCII set of 0 - 32 decimal, excluding 10 decimal (NL). 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.
Message Communication and System Functions Syntax Overview Suffix Unit The suffix units that the instrument will accept are shown in table 5-2.
6 Status Reporting
Introduction Status reporting allows you to use information about the instrument in your programs, so that you have better control of the measurement process. For example, you can use status reporting to determine when a measurement is complete, thus controlling your program, so that it does not get ahead of the instrument. This chapter describes the status registers, status bytes and status bits defined by IEEE 488.2 and discusses how they are implemented in the 1660-series logic analyzers.
Status Reporting Figure 6-1 Status Byte Structures and Concepts 6–3
Status Reporting Event Status Register 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.
Status Reporting Bit Definitions MSG - message Indicates whether there is a message in the message queue (Not implemented in the 1660-series logic analyzers). PON - power on Indicates power has been turned on. URQ - user request Always returns a 0 from the 1660-series logic analyzer. CME - command error Indicates whether the parser detected an error. The error numbers and strings for CME, EXE, DDE, and QYE can be read from a device-defined queue (which is not part of IEEE 488.
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.
Status Reporting Serial Poll Figure 6-2. Service Request Enabling Serial Poll The 1660-series logic analyzer supports the IEEE 488.1 serial poll feature. When a serial poll of the instrument is requested, the RQS bit is returned on bit 6 of the status byte.
Status Reporting Serial Poll Using Serial Poll (GPIB) This example will show how to use the service request by conducting a serial poll of all instruments on the GPIB bus. In this example, assume that there are two instruments on the bus: a Logic Analyzer at address 7 and a printer at address 1. The program command for serial poll using HP BASIC 6.2 is Stat = SPOLL(707). The address 707 is the address of the logic analyzer in the this example.
7 Error Messages
Introduction This chapter lists the error messages that relate to the 1660-series logic analyzers.
Error Messages Device Dependent Errors Device Dependent Errors 200 201 202 203 300 Label not found Pattern string invalid Qualifier invalid Data not available RS-232C error Command Errors –100 –101 –110 –111 –120 –121 –123 –129 –130 Command error (unknown command)(generic error) Invalid character received Command header error Header delimiter error Numeric argument error Wrong data type (numeric expected) Numeric overflow Missing numeric argument Non numeric argument error (character,string, or block)
Error Messages Execution Errors Execution Errors –200 –201 –202 –203 –211 –212 –221 –222 –232 –240 –241 –242 –243 –244 –245 –246 –247 –248 Can Not Do (generic execution error) Not executable in Local Mode Settings lost due to return-to-local or power on Trigger ignored Legal command, but settings conflict Argument out of range Busy doing something else Insufficient capability or configuration Output buffer full or overflow Mass Memory error (generic) Mass storage device not present No media Bad media Medi
Error Messages Query Errors –321 –322 –330 –340 –350 ROM checksum Hardware and Firmware incompatible Power on test failed Self Test failed Too Many Errors (Error queue overflow) Query Errors –400 –410 –420 –421 –422 –430 Query Error (generic) Query INTERRUPTED Query UNTERMINATED Query received.
7–6
Part 2 Mainframe Commands
8 Common Commands
Introduction The common commands are defined by the IEEE 488.2 standard. These commands must be supported by all instruments that comply with this standard. Refer to figure 8-1 and table 8-1 for the common commands syntax diagram. The common commands control some of the basic instrument functions; such as, instrument identification and reset, how status is read and cleared, and how commands and queries are received and processed by the instrument.
Common Commands Example If the program message in this example is received by the logic analyzer, it will initialize the disk and store the file and clear the status information. This is not be the case if some other type of command is received within the program message. ":MMEMORY:INITIALIZE;*CLS; STORE ’FILE Example ’,’DESCRIPTION’" This program message initializes the disk, selects the module in slot A, then stores the file.
Common Commands Figure 8-1 Common Commands Syntax Diagram 8–4
Common Commands *CLS (Clear Status) Table 8-1 Common Command Parameter Values Parameter Values mask An integer, 0 through 255. pre_mask An integer, 0 through 65535. *CLS (Clear Status) Command *CLS The *CLS common command clears all event status registers, queues, and data structures, including the device defined error queue and status byte. If the *CLS command immediately follows a , the output queue and the MAV (Message Available) bit will be cleared.
Common Commands *ESE (Event Status Enable) *ESE (Event Status Enable) Command *ESE The *ESE command sets the Standard Event Status Enable Register bits. The Standard Event Status Enable Register contains a bit to enable the status indicators detailed in table 8-2. A 1 in any bit position of the Standard Event Status Enable Register enables the corresponding status in the Standard Event Status Enable Register. Refer to Chapter 6, "Status Reporting" for a complete discussion of status.
Common Commands *ESR (Event Status Register) Table 8-2 Standard Event Status Enable Register Bit Position Bit Weight Enables 7 128 PON - Power On 6 64 URQ - User Request 5 32 CME - Command Error 4 16 EXE - Execution Error 3 8 DDE - Device Dependent Error 2 4 QYE - Query Error 1 2 RQC - Request Control 0 1 OPC - Operation Complete *ESR (Event Status Register) Query *ESR? The *ESR query returns the contents of the Standard Event Status Register.
Common Commands *ESR (Event Status Register) Table 8-3 shows the Standard Event Status Register. The table details the meaning of each bit position in the Standard Event Status Register and the bit weight. When you read Standard Event Status Register, the value returned is the total bit weight of all the bits that are high at the time you read the byte.
Common Commands *IDN (Identification Number) *IDN (Identification Number) Query *IDN? The *IDN? query allows the instrument to identify itself. It returns the string: "HEWLETT-PACKARD,1660A,0,REV " An *IDN? query must be the last query in a message. Any queries after the *IDN? in the program message are ignored. Returned Format HEWLETT-PACKARD,1660A,0,REV Example Four digit-code in the format XX.XX representing the current ROM revision.
Common Commands *IST (Individual Status) Example OUTPUT XXX;"*IST?" Figure 8-2 *IST Data Structure 8–10
Common Commands *OPC (Operation Complete) *OPC (Operation Complete) Command *OPC The *OPC command will cause the instrument to set the operation complete bit in the Standard Event Status Register when all pending device operations have finished. The commands which affect this bit are the overlapped commands. An overlapped command is a command that allows execution of subsequent commands while the device operations initiated by the overlapped command are still in progress.
Common Commands *OPT (Option Identification) *OPT (Option Identification) Query *OPT? The *OPT query identifies the software installed in the 1660-series logic analyzer. This query returns nine parameters. The first parameter indicates whether you are in the system. The next two parameters indicate any software options installed, and the next parameter indicates whether intermodule is available for the system.
Common Commands *PRE (Parallel Poll Enable Register Enable) *PRE (Parallel Poll Enable Register Enable) Command *PRE The *PRE command sets the parallel poll register enable bits. The Parallel Poll Enable Register contains a mask value that is ANDed with the bits in the Status Bit Register to enable an "ist" during a parallel poll. Refer to table 8-4 for the bits in the Parallel Poll Enable Register and for what they mask. Example An integer from 0 to 65535.
Common Commands *RST (Reset) Table 8-4 1660-Series Logic Analyzer Parallel Poll Enable Register Bit Position Bit Weight 15 -8 Enables Not used 7 128 Not used 6 64 MSS - Master Summary Status 5 32 ESB - Event Status 4 16 MAV - Message Available 3 8 LCL - Local 2 4 Not used 1 2 Not used 0 1 MSB - Module Summary *RST (Reset) The *RST command is not implemented on the 1660-series logic analyzer.
Common Commands *SRE (Service Request Enable) *SRE (Service Request Enable) Command *SRE The *SRE command sets the Service Request Enable Register bits. The Service Request Enable Register contains a mask value for the bits to be enabled in the Status Byte Register. A one in the Service Request Enable Register will enable the corresponding bit in the Status Byte Register. A zero will disable the bit. Refer to table 8-5 for the bits in the Service Request Enable Register and what they mask.
Common Commands *STB (Status Byte) Table 8-5 1660-Series Logic Analyzer Service Request Enable Register Bit Position Bit Weight 15-8 Enables not used 7 128 not used 6 64 MSS - Master Summary Status (always 0) 5 32 ESB - Event Status 4 16 MAV - Message Available 3 8 LCL- Local 2 4 not used 1 2 not used 0 1 MSB - Module Summary *STB (Status Byte) Query *STB? The *STB query returns the current value of the instrument’s status byte.
Common Commands *TRG (Trigger) Table 8-6 The Status Byte Register Bit Position Bit Weight Bit Name Condition 7 128 6 64 MSS 0 = instrument has no reason for service 1 = instrument is requesting service 5 32 ESB 0 = no event status conditions have occurred 1 = an enabled event status condition has occurred 4 16 MAV 0 = no output messages are ready 1 = an output message is ready 3 8 LCL 0 = a remote-to-local transition has not occurred 1 = a remote-to-local transition has occurred 2 4
Common Commands *TST (Test) *TST (Test) Query *TST? The *TST query returns the results of the power-up self-test. The result of that test is a 9-bit mapped value which is placed in the output queue. A one in the corresponding bit means that the test failed and a zero in the corresponding bit means that the test passed. Refer to table 8-7 for the meaning of the bits returned by a TST? query.
Common Commands *WAI (Wait) *WAI (Wait) Command *WAI The *WAI command causes the device to wait until completing all of the overlapped commands before executing any further commands or queries. An overlapped command is a command that allows execution of subsequent commands while the device operations initiated by the overlapped command are still in progress. Some examples of overlapped commands for the 1660-series logic analyzers are STARt and STOP.
8–20
9 Mainframe Commands
Introduction Mainframe commands control the basic operation of the instrument for the 1660-series logic analyzers. The 1660-series logic analyzers are similar to a 16500A logic analysis system with either a single logic analyzer module (1660A) or one logic analyzer and one oscilloscope module (1660AS) installed. The main difference in mainframe commands for the 1660-series logic analyzers is the number of modules.
Mainframe Commands Figure 9-1 Mainframe Commands Syntax Diagram 9–3
Mainframe Commands Figure 9-1 (continued) Mainframe Commands Syntax Diagram (continued) 9–4
Mainframe Commands Table 9-1 Mainframe Parameter Values Parameter Values value An integer from 0 to 65535. module An integer 0 through 2 (3 through 10 unused). menu An integer. enable_value An integer from 0 to 255. index An integer from 0 to 5.
Mainframe Commands BEEPer BEEPer Command :BEEPer [{ON|1}|{OFF|0}] The BEEPer command sets the beeper mode, which turns the beeper sound of the instrument on and off. When BEEPer is sent with no argument, the beeper will be sounded without affecting the current mode. Example OUTPUT XXX;":BEEPER"OUTPUT XXX;":BEEP ON" Query :BEEPer? The BEEPer? query returns the mode currently selected.
Mainframe Commands CAPability CAPability Query :CAPability? The CAPability query returns the HP-SL (HP System Language) and lower level capability sets implemented in the device. Table 9-2 lists the capability sets implemented in the 1660-series logic analyzers.
Mainframe Commands CARDcage CARDcage Query :CARDcage? The CARDcage query returns a series of integers which identify the modules that are installed in the mainframe. The returned string is in two parts. The first five two-digit numbers identify the card type. The identification number for the logic analyzer is 32. The identification number for the oscilloscope is 13. A "-1" in the first part of the string indicates no card is installed in the slot.
Mainframe Commands CESE (Combined Event Status Enable) CESE (Combined Event Status Enable) Command :CESE The CESE command sets the Combined Event Status Enable register. This register is the enable register for the CESR register and contains the combined status of all of the MESE (Module Event Status Enable) registers of the 1660-series logic analyzer. Table 9-3 lists the bit values for the CESE register.
Mainframe Commands CESR (Combined Event Status Register) CESR (Combined Event Status Register) Query :CESR? The CESR query returns the contents of the Combined Event Status register. This register contains the combined status of all of the MESRs (Module Event Status Registers) of the 1660-series logic analyzer. Table 9-4 lists the bit values for the CESR register.
Mainframe Commands EOI (End Or Identify) EOI (End Or Identify) Command :EOI {{ON|1}|{OFF|0}} The EOI command specifies whether or not the last byte of a reply from the instrument is to be sent with the EOI bus control line set true or not. If EOI is turned off, the logic analyzer will no longer be sending IEEE 488.2 compliant responses. Example OUTPUT XXX;":EOI ON" Query :EOI? The EOI? query returns the current status of EOI.
Mainframe Commands LOCKout LOCKout Command :LOCKout {{ON|1}|{OFF|0}} The LOCKout command locks out or restores front panel operation. When this function is on, all controls (except the power switch) are entirely locked out. Example OUTPUT XXX;":LOCKOUT ON" Query :LOCKout? The LOCKout query returns the current status of the LOCKout command. Returned Format [:LOCKout] {0|1} Example OUTPUT XXX;":LOCKOUT?" MENU Command :MENU [,
Mainframe Commands MENU Example OUTPUT XXX;":MENU 0,1" Table 9-5 Menu Parameter Values Parameters Menu 0,0 System RS-232/GPIB 0,2 System Disk 0,3 System Utilities 0,4 System Test 1,0 Analyzer Configuration 1,1 Format 1 1,2 Format 2 1,3 Trigger 1 1,4 Trigger 2 1,5 Waveform 1 1,6 Waveform 2 1,7 Listing 1 1,8 Listing 2 1,9 Mixed 1,10 Compare 1 1,11 Compare 2 1,12 Chart 1 1,13 Chart 2 2,0 Channel 2,1 Trigger 2,2 Display 2,3 Auto-measure 2,4 Marker 2,5 Calibra
Mainframe Commands MESE (Module Event Status Enable) Query :MENU? The MENU query returns the current menu selection. Returned Format [:MENU] ,
Mainframe Commands MESE (Module Event Status Enable) Table 9-6 Table 9-7 1660-Series Mainframe (Intermodule) Module Event Status Enable Register Bit Position Bit Weight Enables 7 128 not used 6 84 not used 5 32 not used 4 16 not used 3 8 not used 2 4 not used 1 2 RNT - Intermodule Run Until Satisfied 0 1 MC - Intermodule Measurement Complete 1660-Series Logic Analyzer Module Event Status Enable Register Bit Position Bit Weight Enables 7 128 not used 6 84 not used 5
Mainframe Commands MESR (Module Event Status Register) Table 9-8 1660-Series Oscilloscope Module Event Status Enable Register Bit Position Bit Weight Enables 7 128 not used 6 84 not used 5 32 not used 4 16 Number of averages met 3 8 Auto triggered 2 4 Trigger received 1 2 RNT - Run Until Satisfied 0 1 MC - Measurement Complete MESR (Module Event Status Register) Query :MESR? The MESR query returns the contents of the Module Event Status register.
Mainframe Commands MESR (Module Event Status Register) Table 9-9 Table 9-10 1660-Series Logic Analyzer Mainframe Module Event Status Register Bit Bit Weight Bit Name Condition 7 128 0 = not used 6 64 0 = not used 5 32 0 = not used 4 16 0 = not used 3 8 0 = not used 2 4 0 = not used 1 2 RNT 0 = Intermodule Run until not satisfied 1 = Intermodule Run until satisfied 0 1 MC 0 = Intermodule Measurement not satisfied 1 = Intermodule Measurement satisfied 1660-Series Logic Anal
Mainframe Commands RMODe Table 9-11 1660-Series Oscilloscope Module Event Status Register Bit Bit Weight Bit Name Condition 7 128 0 = not used 6 64 0 = not used 5 32 0 = not used 4 16 1 = Number of averages satisfied 0= Number of averages not satisfied 3 8 1 = Auto trigger received 0= Auto trigger not received 2 4 1= Trigger received 0= Trigger not received 1 2 RNT 1 = Run until satisfied 0 = Run until not satisfied 0 1 MC 1 = Measurement complete 0 = Measurement not complete
Mainframe Commands RTC (Real-time Clock) Query :RMODe? The query returns the current setting. Returned Format [:RMODe] {SINGle|REPetitive} Example OUTPUT XXX;":RMODE?" RTC (Real-time Clock) Command :RTC {,,,,, |DEFault} The real-time clock command allows you to set the real-time clock to the current date and time. The DEFault option sets the real-time clock to 01 January 1990, 12:00:00 (24-hour format).
Mainframe Commands SELect Query :RTC? The RTC query returns the real-time clock setting. Returned Format [:RTC] ,,,,, Example OUTPUT XXX;":RTC?" SELect Command :SELect The SELect command selects which module (or system) will have parser control. SELect defaults to System (0) at power up. The appropriate module (or system) must be selected before any module (or system) specific commands can be sent.
Mainframe Commands SELect Query :SELect? The SELect? query returns the current module selection.
Mainframe Commands SETColor SETColor Command :SETColor {,,,|DEFault} The SETColor command is used to change one of the selections on the CRT, or to return to the default screen colors. Four parameters are sent with the command to change a color: • • • • Color Number (first parameter) Hue (second parameter) Saturation (third parameter) Luminosity (last parameter) An integer from 1 to 7 An integer from 0 to 100. An integer from 0 to 100.
Mainframe Commands STARt STARt Command :STARt The STARt command starts the selected module (or Intermodule) running in the specified run mode (see RMODe). If the specified module is in the Intermodule configuration, then the Intermodule run will be started. The STARt command is an overlapped command. An overlapped command is a command that allows execution of subsequent commands while the device operations initiated by the overlapped command are still in progress.
Mainframe Commands STOP STOP Command :STOP The STOP command stops the selected module (or Intermodule). If the specified module is in the Intermodule configuration, then the Intermodule run will be stopped. The STOP command is an overlapped command. An overlapped command is a command that allows execution of subsequent commands while the device operations initiated by the overlapped command are still in progress.
10 SYSTem Subsystem
Introduction SYSTem subsystem commands control functions that are common to the entire 1660-Series logic analysis system, including formatting query responses and enabling reading and writing to the advisory line of the instrument. The command parser in the 1660-series logic analyzer is designed to accept programs written for the 16500A logic analysis system with a 16550A logic analyzer module and a 16532A oscilloscope module.
SYSTem Subsystem Figure 10-1 System Subsystem Commands Syntax Diagram 10–3
SYSTem Subsystem System Subsystem Commands Syntax Diagram (Continued) Table 10-1 SYSTem Parameter Values Parameter Values block_data Data in IEEE 488.2 format. string A string of up to 68 alphanumeric characters.
SYSTem Subsystem DATA DATA Command :SYSTem:DATA The DATA command allows you to send and receive acquired data to and from a controller in block form. This helps saving block data for: • Reloading to the logic analyzer or oscilloscope • Processing data later in the logic analyzer or oscilloscope • Processing data in the controller. The format and length of block data depends on the instruction being used and the configuration of the instrument.
SYSTem Subsystem DSP (Display) Query :SYSTem:DATA? The SYSTem:DATA query returns the block data. The data sent by the SYSTem:DATA query reflects the configuration of the machines when the last run was performed. Any changes made since then through either front-panel operations or programming commands do not affect the stored configuration. Returned Format [:SYSTem:DATA] Example See chapter 36, "Programming Examples" for an example on transferring data.
SYSTem Subsystem ERRor ERRor Query :SYSTem:ERRor? [NUMeric|STRing] The ERRor query returns the oldest error from the error queue. The optional parameter determines whether the error string should be returned along with the error number. If no parameter is received, or if the parameter is NUMeric, then only the error number is returned.
SYSTem Subsystem HEADer HEADer Command :SYSTem:HEADer {{ON|1}|{OFF|0}} The HEADer command tells the instrument whether or not to output a header for query responses. When HEADer is set to ON, query responses will include the command header. Example OUTPUT XXX;":SYSTEM:HEADER ON" Query :SYSTem:HEADer? The HEADer query returns the current state of the HEADer command.
SYSTem Subsystem LONGform LONGform Command :SYSTem:LONGform {{ON|1}|{OFF|0}} The LONGform command sets the longform variable, which tells the instrument how to format query responses. If the LONGform command is set to OFF, command headers and alpha arguments are sent from the instrument in the abbreviated form. If the the LONGform command is set to ON, the whole word will be output. This command has no affect on the input data messages to the instrument.
SYSTem Subsystem PRINt PRINt Command :SYSTem:PRINt {ALL|PARTial,,}, DISK, :SYSTem:PRINt SCReen{BTIF|CTIF|PCX|EPS}, DISK, The PRINt command initiates a print of the screen or listing buffer over the current PRINTER communication interface to the printer or to a file on the disk. The PRINT SCREEN option allows you to specify a graphics type. BTIF format is black & white, CTIF and PCX format is color.
SYSTem Subsystem SETup The print query should NOT be sent with any other command or query on the same command line. The print query never returns a header. Also, since response data from a print query may be sent directly to a printer without modification, the data is not returned in block mode. Example OUTPUT 707;":SYSTEM:PRINT? SCREEN" SETup Command :SYStem:SETup The :SYStem:SETup command configures the logic analyzer module as defined by the block data sent by the controller.
SYSTem Subsystem SETup The total length of a section is 16 (for the section header) plus the length of the section data. So when calculating the value for , don’t forget to include the length of the section headers. Example OUTPUT XXX USING "#,K";":SYSTEM:SETUP Query :SYStem:SETup? " The SYStem:SETup query returns a block of data that contains the current configuration to the controller.
11 MMEMory Subsystem
Introduction The MMEMory (mass memory) subsystem commands provide access to disk drive. The 1600-series logic analyzers support both LIF (Logical Information Format) and DOS (Disk Operating System) formats. The 1660-series logic analyzers have only one disk drive; however, programs written for the 16500A logic analysis system that contain the MSI (Mass Storage Is) parameter will be accepted but no action is taken. Refer to figure 11-1 and table 11-1 for the MMEMory Subsystem commands syntax diagram.
MMEMory Subsystem refers to the mass storage unit specifier; however, it is not needed for the 1660-series logic analyzers since they have only one drive. The parameter is shown in the command syntax examples as a reminder that for the the 16500A logic analysis system can be used on the 1660-series logic analyzers. If you are not going to store information to the configuration disk, or if the disk you are using contains information you need, it is advisable to write protect your disk.
MMEMory Subsystem Figure 11-1 Mmemory Subsystem Commands Syntax Diagram 11–4
MMEMory Subsystem Figure 11-1 Mmemory Subsystem Commands Syntax Diagram (Continued) 11–5
MMEMory Subsystem Figure 11-1 Mmemory Subsystem Commands Syntax Diagram (Continued) 11–6
MMEMory Subsystem Table 11-1 MMEMory Parameter Values Parameter Values auto_file A string of up to 10 alphanumeric characters for LIF in the following form: "NNNNNNNNNN" or A string of up to 12 alphanumeric characters for DOS in the following form: "NNNNNNNN.NNN" msus Mass Storage Unit specifier (not needed by 1660-series. 16500A is accepted but no action is taken).
MMEMory Subsystem AUToload AUToload Command :MMEMory:AUToload {{OFF|0}|{}}[,] The AUToload command controls the autoload feature which designates a set of configuration files to be loaded automatically the next time the instrument is turned on. The OFF parameter (or 0) disables the autoload feature. A string parameter may be specified instead to represent the desired autoload file. If the file is on the current disk, the autoload feature is enabled to the specified file.
MMEMory Subsystem CATalog A string of up to 10 alphanumeric characters for LIF in the following form: NNNNNNNNNN or A string of up to 12 alphanumeric characters for DOS in the following form: NNNNNNNN.NNN Example OUTPUT XXX;":MMEMORY:AUTOLOAD?" CATalog Query :MMEMory:CATalog? [[All,][]] The CATalog query returns the directory of the disk in one of two block data formats. The directory consists of a 51 character string for each file on the disk when the ALL option is not used.
MMEMory Subsystem COPY Returned Format Example 1 Mass Storage Unit Specifier (not needed by 1660-series. 16500A is accepted but no action is taken). [:MMEMory:CATalog] ASCII block containing This example is for sending the CATALOG? ALL query: OUTPUT 707;":MMEMORY:CATALOG? ALL" Example 2 This example is for sending the CATALOG? query without the ALL option.
MMEMory Subsystem DOWNload A string of up to 10 alphanumeric characters for LIF in the following form: NNNNNNNNNN or A string of up to 12 alphanumeric characters for DOS in the following form: NNNNNNNN.NNN A string of up to 10 alphanumeric characters for LIF in the following form: NNNNNNNNNN or A string of up to 12 alphanumeric characters for DOS in the following form: NNNNNNNN.NNN Examples Mass Storage Unit Specifier (not needed by 1660-series.
MMEMory Subsystem DOWNload A string of up to 10 alphanumeric characters for LIF in the following form: NNNNNNNNNN or A string of up to 12 alphanumeric characters for DOS in the following form: NNNNNNNN.NNN Mass Storage Unit Specifier (not needed by 1660-series. 16500A is accepted but no action is taken).
MMEMory Subsystem INITialize INITialize Command :MMEMory:INITialize [{LIF|DOS}[,]] The INITialize command formats the disk in either LIF (Logical Information Format) or DOS (Disk Operating System). The is not needed by 1660-series. 16500A is accepted but no action is taken. If no format is specified, then the initialize command will format the disk in the LIF format. Examples Mass Storage Unit Specifier (not needed by 1660-series.
MMEMory Subsystem LOAD [:CONFig] LOAD [:CONFig] Command :MMEMory:LOAD[:CONfig] [,][,] The LOAD command loads a configuration file from the disk into the logic analyzer, oscilloscope, software options, or the system. The parameter specifies the filename from the disk. The optional parameter specifies which module(s) to load the file into. The accepted values are 0 for system, 1 for logic analyzer, and 2 for the oscilloscope.
MMEMory Subsystem LOAD :IASSembler LOAD :IASSembler Command :MMEMory:LOAD:IASSembler [,],{1|2} [,] This variation of the LOAD command allows inverse assembler files to be loaded into a module that performs state analysis. The parameter specifies the inverse assembler filename from the desired . The parameter after the optional specifies which machine to load the inverse assembler into.
MMEMory Subsystem MSI (Mass Storage Is) MSI (Mass Storage Is) Command :MMEMory:MSI [] The MSI command selects a default mass storage device; however, it is not needed by 1660-series logic analyzers because they have only one disk drive. If the 16500A is sent to the 1660-series logic analyzer, it is accepted but no action is taken. Mass Storage Unit Specifier (not needed by 1660-series. 16500A is accepted but no action is taken).
MMEMory Subsystem PACK PACK Command :MMEMory:PACK [] The PACK command packs the files on the LIF disk the disk in the drive. If a DOS disk is in the drive when the PACK command is sent, no action is taken. Examples Mass Storage Unit Specifier (not needed by 1660-series. 16500A is accepted but no action is taken). OUTPUT XXX;":MMEMORY:PACK" OUTPUT XXX;":MMEM:PACK INTERNAL0" PURGe Command :MMEMory:PURGe [,] The PURGe command deletes a file from the disk in the drive.
MMEMory Subsystem REName Examples OUTPUT XXX;":MMEMORY:PURGE ’FILE1’" OUTPUT XXX;":MMEM:PURG ’FILE1’,INTERNAL0" Once executed, the purge command permanently erases all the existing information about the specified file. After that, there is no way to retrieve the original information. REName Command :MMEMory:REName [,], The REName command renames a file on the disk in the drive.
MMEMory Subsystem STORe [:CONFig] Examples OUTPUT XXX;":MMEMORY:RENAME ’OLDFILE’,’NEWFILE’" OUTPUT XXX;":MMEM:REN ’OLDFILE’[,INTERNAL1],’NEWFILE’" STORe [:CONFig] Command :MMEMory:STORe [:CONfig][,], [,] The STORe command stores module or system configurations onto a disk. The [:CONFig] specifier is optional and has no effect on the command. The parameter specifies the file on the disk. The parameter describes the contents of the file.
MMEMory Subsystem UPLoad Examples OUTPUT XXX;":MMEM:STOR ’DEFAULTS’,’SETUPS FOR ALL MODULES’" OUTPUT XXX;":MMEMORY:STORE:CONFIG ’STATEDATA’,INTERNAL0, ’ANALYZER 1 CONFIG’,1" The appropriate module designator "_X" is added to all files when they are stored. "X" refers to either an __ (double underscore) for the system or an _A for the logic analyzer. UPLoad Query :MMEMory:UPLoad? [,] The UPLoad query uploads a file. The parameter specifies the file to be uploaded from the disk.
MMEMory Subsystem VOLume Example 10 20 30 40 50 60 70 80 90 DIM Block$[32000] !allocate enough memory for block data DIM Specifier$[2] OUTPUT XXX;":EOI ON" OUTPUT XXX;":SYSTEM HEAD OFF" OUTPUT XXX;":MMEMORY:UPLOAD? ’FILE1’" !send upload query ENTER XXX USING "#,2A";Specifier$ !read in #8 ENTER XXX USING "#,8D";Length !read in block length ENTER XXX USING "-K";Block$ !read in file END VOLume Query :MMEMory:VOLume? [] TheVOLume query returns the volume type of the disk.
11–22
12 INTermodule Subsystem
Introduction The INTermodule subsystem commands specify intermodule arming from the rear-panel input BNC (ARMIN) or to the rear-panel output BNC (ARMOUT). Refer to figure 12-1 and table 12-1 for the INTermodule Subsystem commands syntax diagram.
INTermodule Subsystem Figure 12-1 Intermodule Subsystem Commands Syntax Diagram 12–3
INTermodule Subsystem Figure 12-1 Intermodule Subsystem Commands Syntax Diagram (Continued) 12–4
INTermodule Subsystem :INTermodule Table 12-1 INTermodule Parameter Values Parameter Value module An integer, 1 to 10 (3 through 10 unused) index An integer, 1 to 10 (3 through 10 unused) setting A numeric, – 1.0 to 1.0 in seconds. :INTermodule Selector :INTermodule The INTermodule selector specifies INTermodule as the subsystem the commands or queries following will refer to.
INTermodule Subsystem HTIMe HTIMe Query :HTIMe? The HTIMe query returns a value representing the internal hardware skew in the Intermodule configuration. If there is no internal skew, or if intermodule bus is not configured, 9.9E37 is returned. The internal hardware skew is only a display adjustment for time-correlated waveforms. The value returned is the average propagation delay of the trigger lines through the intermodule bus circuitry.
INTermodule Subsystem INSert Query :INPort? The INPort query returns the current setting. Returned Format [:INTermodule:INPort] {1|0} Example OUTPUT XXX;":INTERMODULE:INPORT?" INSert Command :INSert {|OUT},{GROUP|} The INSert command adds PORT OUT to the Intermodule configuration.
INTermodule Subsystem SKEW SKEW Command :SKEW The SKEW command sets the skew value for a module. The index value is the module number (1 corresponds to the logic analyzer, 2 corresponds to the oscilloscope, and 3 through 10 unused). The parameter is the skew setting (– 1.0 to 1.0) in seconds. An integer, 1 through 10 (3 through 10 unused) A real number from –1.0 to 1.0 seconds Example OUTPUT XXX;":INTERMODULE:SKEW1 3.
INTermodule Subsystem TREE TREE Command :TREE , The TREE command allows an intermodule setup to be specified in one command. The first parameter is the intermodule arm value for module A (logic analyzer). The second parameter corresponds to the intermodule arm value for PORT OUT.
INTermodule Subsystem TTIMe TTIMe Query :TTIMe? The TTIMe query returns values representing the absolute intermodule trigger time for all of the modules in the Intermodule configuration. The first value is the trigger time for the module in slot A, the second value is for the module in slot B, the third value is for slot C, etc. The value 9.9E37 is returned when: • The module in the corresponding slot is not time correlated; or • A time correlatable module did not trigger.
Part 3 Logic Analyzer Commands
13 MACHine Subsystem
Introduction The MACHine subsystem contains the commands that control the machine level of operation of the logic analyzer. The functions of three of these commands reside in the State/Timing Configuration menu. These commands are: • ASSign • NAME • TYPE Even though the functions of the following commands reside in the Trace menu they are at the machine level of the command tree and are therefore located in the MACHine subsystem.
MACHine Subsystem Figure 13-1 Machine Subsystem Syntax Diagram 13–3
MACHine Subsystem MACHine Table 13-1 Machine Parameter Values Parameter Values arm_source {RUN|INTermodule|MACHine{1|2}} pod_list {NONE|[,]...
MACHine Subsystem ARM ARM Command :MACHine{1|2}:ARM The ARM command specifies the arming source of the specified analyzer (machine). The RUN option disables the arm source. For example, if you do not want to use either the intermodule bus or the other machine to arm the current machine, you specify the RUN option.
MACHine Subsystem LEVelarm Example OUTPUT XXX;":MACHINE1:ASSIGN 5, 2, 1" Query :MACHine{1|2}:ASSign? The ASSign query returns which pods are assigned to the current analyzer (machine). Returned Format # Example [:MACHine{1|2}:ASSign] {NONE|#[, #]...
MACHine Subsystem NAME Returned Format: Example [:MACHine{1|2}:LEVelarm] An integer from 1 to 11 representing sequence level OUTPUT XXX;":MACHINE1:LEVELARM?" NAME Command :MACHine{1|2}:NAME The NAME command allows you to assign a name of up to 10 characters to a particular analyzer (machine) for easier identification.
MACHine Subsystem REName REName Command :MACHine{1|2}:REName {, | DEFault} The REName command allows you to assign a specific name of up to eight characters to terms A through J, Range 1 and 2, and Timer 1 and 2 in the state analyzer. In the timing analyzer, GLEDge (glitch/edge) 1 and 2 can be renamed in addition to the terms available in the state analyzer. The DEFault option sets all resource term names to the default names assigned when turning on the instrument.
MACHine Subsystem RESource RESource Command :MACHine{1|2}:RESource The RESource command allows you to assign resource terms A through J, Range 1 and 2, and Timer 1 and 2 to a particular analyzer (machine 1 or 2). In the timing analyzer only, two additional resource terms are available. These terms are GLEDge (Glitch/Edge) 1 and 2. These terms will always be assigned to the the machine that is configured as the timing analyzer.
MACHine Subsystem TYPE TYPE Command :MACHine{1|2}:TYPE The TYPE command specifies what type a specified analyzer (machine) will be. The analyzer types are state or timing. The TYPE command also allows you to turn off a particular machine. Only one timing analyzer can be specified at a time. {OFF|STATe|TIMing} Example OUTPUT XXX;":MACHINE1:TYPE STATE" Query :MACHine{1|2}:TYPE? The TYPE query returns the current analyzer type for the specified analyzer.
14 WLISt Subsystem
Introduction The WLISt subsystem contains the commands available for the Timing/State mixed mode display. The X and O markers can only be placed on the waveforms in the waveform portion of the Timing/State mixed mode display. The XSTate and OSTate queries return what states the X and O markers are on. Because the markers can only be placed on the timing waveforms, the queries return what state (state acquisition memory location) the marked pattern is stored in.
WLISt Subsystem Figure 14-1 WLISt Subsystem Syntax Diagram 14–3
WLISt Subsystem WLISt Table 14-1 WLISt Parameter Values Parameter Value delay_value Real number between −2500 s and +2500 s module_spec {1|2|3|4|5|6|7|8|9|10} (slot where timing card is installed, 2 through 10 unused) bit_id An integer from 0 to 31 label_name String of up to 6 alphanumeric characters line_num_mid_screen An integer from −8191 to +8191 waveform String containing {1|2} time_value Real number time_range Real number between 10 ns and 10 ks WLISt Selector :W
WLISt Subsystem DELay DELay Command :MACHine{1|2}:WLISt:DELay The DELay command specifies the amount of time between the timing trigger and the horizontal center of the the timing waveform display. The allowable values for delay are −2500 s to +2500 s. Real number between −2500 s and +2500 s Example OUTPUT XXX;":MACHINE1:WLIST:DELAY 100E−6" Query :MACHine{1|2}:WLISt:DELay? The DELay query returns the current time offset (delay) value from the trigger.
WLISt Subsystem INSert INSert Command :MACHine{1|2}:WLISt:INSert [,] [,{|OVERlay|ALL}] The INSert command inserts waveforms in the timing waveform display. The waveforms are added from top to bottom up to a maximum of 96 waveforms. Once 96 waveforms are present, each time you insert another waveform, it replaces the last waveform.
WLISt Subsystem LINE LINE Command :MACHine{1|2}:WLISt:LINE The LINE command allows you to scroll the state analyzer listing vertically. The command specifies the state line number relative to the trigger that the analyzer highlights at the center of the screen.
WLISt Subsystem OSTate OSTate Query :WLISt:OSTate? The OSTate query returns the state where the O Marker is positioned. If data is not valid, the query returns 32767. Returned Format Example [:WLISt:OSTate] An integer from −8191 to +8191 OUTPUT XXX;":WLIST:OSTATE?" OTIMe Command :WLISt:OTIMe The OTIMe command positions the O Marker on the timing waveforms in the mixed mode display. If the data is not valid, the command performs no action.
WLISt Subsystem RANGe Query :WLISt:OTIMe? The OTIMe query returns the O Marker position in time. If data is not valid, the query returns 9.9E37. Returned Format Example [:WLISt:OTIMe] A real number OUTPUT XXX;":WLIST:OTIME?" RANGe Command :MACHine{1|2}:WLISt:RANGe The RANGe command specifies the full-screen time in the timing waveform menu. It is equivalent to ten times the seconds per division setting on the display.
WLISt Subsystem REMove REMove Command :MACHine{1|2}:WLISt:REMove The REMove command deletes all waveforms from the display. Example OUTPUT XXX;":MACHINE1:WLIST:REMOVE" XOTime Query :MACHine{1|2}:WLISt:XOTime? The XOTime query returns the time from the X marker to the O marker. If data is not valid, the query returns 9.9E37.
WLISt Subsystem XSTate XSTate Query :WLISt:XSTate? The XSTate query returns the state where the X Marker is positioned. If data is not valid, the query returns 32767. Returned Format Example [:WLISt:XSTate] An integer OUTPUT XXX;":WLIST:XSTATE?" XTIMe Command :WLISt:XTIMe The XTIMe command positions the X Marker on the timing waveforms in the mixed mode display. If the data is not valid, the command performs no action.
WLISt Subsystem XTIMe Query :WLISt:XTIMe? The XTIMe query returns the X Marker position in time. If data is not valid, the query returns 9.9E37.
15 SFORmat Subsystem
Introduction The SFORmat subsystem contains the commands available for the State Format menu in the 1660A-series logic analyzers.
SFORmat Subsystem Figure 15-1 SFORmat Subsystem Syntax Diagram 15–3
SFORmat Subsystem Figure 15-1 SFORmat Subsystem Syntax Diagram (continued) 15–4
SFORmat Subsystem Table 15-1 SFORmat Parameter Values Parameter Values {{1|2}|{3|4|5|6}|{7|8}} label_name String of up to 6 alphanumeric characters polarity {POSitive|NEGative} clock_bits Format (integer from 0 to 63) for a clock (clocks are assigned in decreasing order) upper_bits Format (integer from 0 to 65535) for a pod (pods are assigned in decreasing order) lower_bits Format (integer from 0 to 65535) for a pod (pods are assigned in decreasing order) clock_id {J|K|L|M|N|P} clock_s
SFORmat Subsystem SFORmat SFORmat Selector :MACHine{1|2}:SFORmat The SFORmat (State Format) selector is used as a part of a compound header to access the settings in the State Format menu. It always follows the MACHine selector because it selects a branch directly below the MACHine level in the command tree.
SFORmat Subsystem LABel Query :MACHine{1|2}:SFORmat:CLOCk? The CLOCk query returns the current clocking mode for a given pod. Returned Format [:MACHine{1|2}:SFORmat:CLOCK] Example OUTPUT XXX; ":MACHINE1:SFORMAT:CLOCK2?" LABel Command :MACHine{1|2}:SFORmat:LABel ,[, , , [,,]...] The LABel command allows you to specify polarity and assign channels to new or existing labels.
SFORmat Subsystem LABel {POSitive|NEGative} Format (integer from 0 to 63) for a clock (clocks are assigned in decreasing order) Format (integer from 0 to 65535) for a pod (pods are assigned in decreasing order) Format (integer from 0 to 65535) for a pod (pods are assigned in decreasing order) Examples OUTPUT XXX;":MACHINE2:SFORMAT:LABEL ’STAT’, POSITIVE, 0,127,40312" OUTPUT XXX;":MACHINE2:SFORMAT:LABEL ’SIG 1’, #B11, #B0000000011111111,#B0000000000
SFORmat Subsystem MASTer MASTer Command Syntax: :MACHine{1|2}:SFORmat:MASTer , The MASTer clock command allows you to specify a master clock for a given machine. The master clock is used in all clocking modes (Master, Slave, and Demultiplexed). Each command deals with only one clock (J,K,L,M,N,P); therefore, a complete clock specification requires six commands, one for each clock. Edge specifications (RISing, FALLing, or BOTH) are ORed. At least one clock edge must be specified.
SFORmat Subsystem MODE MODE Command :MACHine{1|2}:SFORmat:MODE The MODE command allows you to select the acquistion mode of the state analyzer. The modes are either full-channel with 4 Kbit of memory depth per channel or half-channel with 8 Kbit of memory depth per channel. {FULL|DEEPmemory} Example OUTPUT XXX;":MACHine1:SFORMAT:MODE FULL" Query :MACHine{1|2}:SFORmat:MODE? The MODE query returns the current acquistion mode.
SFORmat Subsystem MOPQual MOPQual Command :MACHine{1|2}:SFORmat:MOPQual , The MOPQual (master operation qualifier) command allows you to specify either the AND or the OR operation between master clock qualifier pair 1 and 2, or between master clock qualifier pair 3 and 4. For example, you can specify a master clock operation qualifer 1 AND 2.
SFORmat Subsystem MQUal MQUal Command :MACHine{1|2}:SFORmat:MQUal ,, The MQUal (master qualifier) command allows you to specify the level qualifier for the master clock. {{1|2}|{3|4}} 1 through 4 for HP 1660A, HP 1661A, HP 1662A; or, 1 or 2 for HP 1663A.
SFORmat Subsystem REMove REMove Command :MACHine{1|2}:SFORmat:REMove {|ALL} The REMove command allows you to delete all labels or any one label for a given machine. Examples String of up to 6 alphanumeric characters OUTPUT XXX;":MACHINE2:SFORMAT:REMOVE ’A’" OUTPUT XXX;":MACHINE2:SFORMAT:REMOVE ALL" SETHold Command :MACHine{1|2}:SFORmat:SETHold , The SETHold (setup/hold) command allows you to set the setup and hold specification for the state analyzer.
SFORmat Subsystem SETHold Table 15-2 {{1|2}|{3|4}|{5|6}|{7|8}} 1 through 8 for the HP 1660A, 1 through 6 for the HP 1661A, 1 through 4 for the HP 1662A, and 1 through 2 for the HP 1663A. An integer {0|1|2|3|4|5|6|7|8|9} representing the setup and hold values in table 15-2. Setup and hold values For one clock and one edge For one clock and both edges For multiple clocks 0 = 3.5/0.0 ns 0 = 4.0/0.0 0 = 4.5/0.0 1 = 3.0/0.5 ns 1 = 3.5/0.5 1 = 4.0/0.5 2 = 2.5/1.0 ns 2 = 3.
SFORmat Subsystem SLAVe SLAVe Command :MACHine{1|2}:SFORmat:SLAVe , The SLAVe clock command allows you to specify a slave clock for a given machine. The slave clock is only used in the Slave and Demultiplexed clocking modes. Each command deals with only one clock (J,K,L,M,N,P); therefore, a complete clock specification requires six commands, one for each clock. Edge specifications (RISing, FALLing, or BOTH) are ORed.
SFORmat Subsystem SOPQual SOPQual Command :MACHine{1|2}:SFORmat:SOPQual , The SOPQual (slave operation qualifier) command allows you to specify either the AND or the OR operation between slave clock qualifier pair 1 and 2, or between slave clock qualifier pair 3 and 4. For example you can specify a slave clock operation qualifer 1 AND 2.
SFORmat Subsystem SQUal SQUal Command :MACHine{1|2}:SFORmat:SQUal ,, The SQUal (slave qualifier) command allows you to specify the level qualifier for the slave clock. {{1|2}|{3|4}} 1 through 4 for HP 1660A, HP 1661A, HP 1662A; or, 1 or 2 for HP 1663A.
SFORmat Subsystem THReshold THReshold Command :MACHine{1|2}:SFORmat:THReshold {TTL|ECL|} The THReshold command allows you to set the voltage threshold for a given pod to ECL, TTL, or a specific voltage from −6.00 V to +6.00 V in 0.05 volt increments. {{1|2}|{3|4}|{5|6}|{7|8}} 1 through 8 for the HP 1660A, 1 through 6 for the HP 1661A, 1 through 4 for the HP 1662A, and 1 through 2 for the HP 1663A. Voltage (real number) −6.00 to +6.00 TTL Default value of +1.
16 STRigger (STRace) Subsystem
Introduction The STRigger subsystem contains the commands available for the State Trigger menu in the 1660A-series logic analyzers. The State Trigger subsystem will also accept the STRace Command as used in previous 1650-series logic analyzers to eliminate the need to rewrite programs containing STRace as the Command keyword.
STRigger (STRace) Subsystem Figure 16-1 STRigger Subsystem Syntax Diagram 16–3
STRigger (STRace) Subsystem Figure 16-1 (continued) STRigger Subsystem Syntax Diagram (continued) 16–4
STRigger (STRace) Subsystem Figure 16-1 (continued) STRigger Subsystem Suntax Diagram (continued) 16–5
STRigger (STRace) Subsystem Table 16-1 STRigger Parameter Values Parameter Values branch_qualifier to_lev_num integer from 1 to last level proceed_qualifier occurrence number from 1 to 1048575 label_name string of up to 6 alphanumeric characters start_pattern "{#B{0|1} . . . | #Q{0|1|2|3|4|5|6|7} . . . | #H{0|1|2|3|4|5|6|7|8|9|A|B|C|D|E|F} . . . | {0|1|2|3|4|5|6|7|8|9} . . . }" stop_pattern "{#B{0|1} . . . | #Q{0|1|2|3|4|5|6|7} . . .
STRigger (STRace) Subsystem Qualifier Qualifier The qualifier for the state trigger subsystem can be terms A through J, Timer 1 and 2, and Range 1 and 2. In addition, qualifiers can be the NOT boolean function of terms, timers, and ranges. The qualifier can also be an expression or combination of expressions as shown below and figure 16-2, "Complex Qualifier," on page 16-11. The following parameters show how qualifiers are specified in all commands of the STRigger subsystem that use .
STRigger (STRace) Subsystem Qualifier {B|NOTB} {C|NOTC} {D|NOTD} {E|NOTE} {F|NOTF} {G|NOTG} {H|NOTH} {I|NOTI} {J|NOTJ} {IN_RANGE1|OUT_RANGE1} {IN_RANGE2|OUT_RANGE2} {TIMER1<|TIMER1>} {TIMER2<|TIMER2>} Qualifier Rules The following rules apply to qualifiers: • Qualifiers are quoted strings and, therefore, need quotes.
STRigger (STRace) Subsystem STRigger (STRace) STRigger (STRace) Selector :MACHine{1|2}:STRigger The STRigger (STRace) (State Trigger) Command is used as a part of a compound header to access the settings found in the State Trace menu. It always follows the MACHine Command because it selects a branch directly below the MACHine level in the command tree.
STRigger (STRace) Subsystem BRANch BRANch Command :MACHine{1|2}:STRigger:BRANch , The BRANch command defines the branch qualifier for a given sequence level. When this branch qualifier is matched, it will cause the sequencer to jump to the specified sequence level. The terms used by the branch qualifier (A through J) are defined by the TERM command. The meaning of IN_RANGE and OUT_RANGE is determined by the RANGE command.
STRigger (STRace) Subsystem BRANch Examples OUTPUT XXX;":MACHINE1:STRIGGER:BRANCH1 ’ANYSTATE’, 3" OUTPUT XXX;":MACHINE2:STRIGGER:BRANCH2 ’A’, 7" OUTPUT XXX;":MACHINE1:STRIGGER:BRANCH3 ’((A OR B) OR NOTG)’, 1" Query :MACHine{1|2}:STRigger:BRANch? The BRANch query returns the current branch qualifier specification for a given sequence level.
STRigger (STRace) Subsystem CLEar Example This example would be used to specify this complex qualifier. OUTPUT XXX;":MACHINE1:STRIGGER:BRANCH1 ’((A OR B) AND (G OR H))’, 2" Terms A through E, RANGE 1, and TIMER 1 must be grouped together and terms F through J, RANGE 2, and TIMER 2 must be grouped together. In the first level, terms from one group may not be mixed with terms from the other.
STRigger (STRace) Subsystem FIND FIND Command :MACHine{1|2}:STRigger:FIND , The FIND command defines the proceed qualifier for a given sequence level. The qualifier tells the state analyzer when to proceed to the next sequence level. When this proceed qualifier is matched the specified number of times, the sequencer will proceed to the next sequence level.
STRigger (STRace) Subsystem RANGe Query :MACHine{1|2}:STRigger:FIND4? The FIND query returns the current proceed qualifier specification for a given sequence level. Returned Format [:MACHine{1|2}:STRigger:FIND] , Example OUTPUT XXX;":MACHINE1:STRIGGER:FIND?" RANGe Command :MACHine{1|2}:STRigger:RANGE ,, The RANGe command allows you to specify a range recognizer term for the specified machine.
STRigger (STRace) Subsystem RANGe String of up to 6 alphanumeric characters "{#B{0|1} . . . | #Q{0|1|2|3|4|5|6|7} . . . | #H{0|1|2|3|4|5|6|7|8|9|A|B|C|D|E|F} . . . | {0|1|2|3|4|5|6|7|8|9} . . . }" "{#B{0|1} . . . | #Q{0|1|2|3|4|5|6|7} . . . | #H{0|1|2|3|4|5|6|7|8|9|A|B|C|D|E|F} . . . | {0|1|2|3|4|5|6|7|8|9} . . .
STRigger (STRace) Subsystem SEQuence SEQuence Command :MACHine{1|2}:STRigger:SEQuence , The SEQuence command redefines the state analyzer trace sequence. First, it deletes the current trace sequence. Then it inserts the number of levels specified, with default settings, and assigns the trigger to be at a specified sequence level. The number of levels can be between 2 and 12 when the analyzer is armed by the RUN key.
STRigger (STRace) Subsystem STORe STORe Command :MACHine{1|2}:STRigger:STORe The STORe command defines the store qualifier for a given sequence level. Any data matching the STORe qualifier will actually be stored in memory as part of the current trace data. The qualifier may be a single term or a complex expression. The terms A through J are defined by the TERM command. The meaning of IN_RANGE1 and 2 and OUT_RANGE1 and 2 is determined by the RANGe command.
STRigger (STRace) Subsystem TAG TAG Command :MACHine{1|2}:STRigger:TAG {OFF|TIME|} The TAG command selects the type of count tagging (state or time) to be performed during data acquisition. State tagging is indicated when the parameter is the state tag qualifier, which will be counted in the qualified state mode. The qualifier may be a single term or a complex expression. The terms A through J are defined by the TERM command.
STRigger (STRace) Subsystem TAKenbranch TAKenbranch Command :MACHine{1|2}:STRigger:TAKenbranch {STORe|NOSTore} The TAKenbranch command allows you to specify whether the state causing a sequence level change is stored or not stored for the specified machine. Both a state that causes the sequencer to proceed or a state that causes the sequencer to branch is considered a sequence level change. A branch can also jump to itself and this also considered a sequence level change.
STRigger (STRace) Subsystem TCONtrol TCONtrol Command :MACHine{1|2}:STRigger:TCONtrol , {OFF|STARt|PAUSe|CONTinue} The TCONtrol (timer control) command allows you to turn off, start, pause, or continue the timer for the specified level. The time value of the timer is defined by the TIMER command. There are two timers and they are independently available for either machine. Neither timer can be assigned to both machines simultaneously.
STRigger (STRace) Subsystem TERM TERM Command :MACHine{1|2}:STRigger:TERM ,, The TERM command allows you to specify a pattern recognizer term in the specified machine. Each command deals with only one label in the given term; therefore, a complete specification could require several commands. Since a label can contain 32 or less bits, the range of the pattern value will be between 232 − 1 and 0.
STRigger (STRace) Subsystem TIMER Query :MACHine{1|2}:STRigger:TERM? , The TERM query returns the specification of the term specified by term identification and label name. Returned Format [:MACHine{1|2}:STRAce:TERM] ,, Example OUTPUT XXX;":MACHINE1:STRIGGER:TERM? B,’DATA’ " TIMER Command :MACHine{1|2}:STRigger:TIMER{1|2} The TIMER command sets the time value for the specified timer.
STRigger (STRace) Subsystem TPOSition Query :MACHine{1|2}:STRigger:TIMER{1|2}? The TIMER query returns the current time value for the specified timer. Returned Format Example [:MACHine{1|2}:STRigger:TIMER{1|2}] A real number from 400 ns to 500 seconds in increments which vary from 16 ns to 500 µs.
STRigger (STRace) Subsystem TPOSition Query :MACHine{1|2}:STRigger:TPOSition? The TPOSition query returns the current trigger position setting.
17 SLISt Subsystem
Introduction The SLISt subsystem contains the commands available for the State Listing menu in the 1660A logic analyzer.
SLISt Subsystem Figure 17-1 SLISt Subsystem Syntax Diagram 17–3
SLISt Subsystem Figure 17-1 (continued) SLISt Subsystem Syntax Diagram (continued) 17–4
SLISt Subsystem Figure 17-1 (continued) SLISt Subsystem Syntax Diagram (continued) 17–5
SLISt Subsystem Table 17-1 SLISt Parameter Values Parameter Values module_num {1|2|3|4|5|6|7|8} (2 through 10 not used) mach_num {1|2} col_num Integer from 1 to 61 line_number Integer from −8191 to +8191 label_name A string of up to 6 alphanumeric characters base {BINary|HEXadecimal|OCTal|DECimal|TWOS|ASCi i|SYMBol|IASSembler} for labels or {ABSolute|RELative} for tags line_num_mid_screen Integer from −8191 to +8191 label_pattern "{#B{0|1|X} . . . | #Q{0|1|2|3|4|5|6|7|X} . . .
SLISt Subsystem SLISt SLISt Selector :MACHine{1|2}:SLISt The SLISt selector is used as part of a compound header to access those settings normally found in the State Listing menu. It always follows the MACHine selector because it selects a branch directly below the MACHine level in the command tree.
SLISt Subsystem CLRPattern integer from 1 to 61 {1|2|3|4|5|6|7|8|9|10} (2 through 10 not used) string of up to 6 alphanumeric characters {BINary|HEXadecimal|OCTal|DECimal|TWOS|ASCii|SYMBol| IASSembler} for labels or {ABSolute|RELative} for tags Example OUTPUT XXX;":MACHINE1:SLIST:COLUMN 4,’A’,HEX" Query :MACHine{1|2}:SLISt:COLumn? The COLumn query returns the column number, label name, and base for the specified column.
SLISt Subsystem DATA DATA Query :MACHine{1|2}:SLISt:DATA? , The DATA query returns the value at a specified line number for a given label. The format will be the same as the one shown in the listing display. Returned Format Example [:MACHine{1|2}:SLISt:DATA] ,, integer from −8191 to +8191 string of up to 6 alphanumeric characters "{#B{0|1|X} . . . | #Q{0|1|2|3|4|5|6|7|X} . . .
SLISt Subsystem MMODe Query :MACHine{1|2}:SLISt:LINE? The LINE query returns the line number for the state currently in the box at the center of the screen. Returned Format [:MACHine{1|2}:SLISt:LINE] Example OUTPUT XXX;":MACHINE1:SLIST:LINE?" MMODe Command :MACHine{1|2}:SLISt:MMODe The MMODe command (Marker Mode) selects the mode controlling the marker movement and the display of marker readouts.
SLISt Subsystem OPATtern OPATtern Command :MACHine{1|2}:SLISt:OPATtern , The OPATtern command allows you to construct a pattern recognizer term for the O Marker which is then used with the OSEarch criteria when moving the marker on patterns. Because this command deals with only one label at a time, a complete specification could require several invocations.
SLISt Subsystem OSEarch OSEarch Command :MACHine{1|2}:SLISt:OSEarch , The OSEarch command defines the search criteria for the O marker, which is then used with associated OPATtern recognizer specification when moving the markers on patterns. The origin parameter tells the marker to begin a search with the trigger, the start of data, or with the X marker.
SLISt Subsystem OSTate OSTate Query :MACHine{1|2}:SLISt:OSTate? The OSTate query returns the line number in the listing where the O marker resides (−8191 to +8191). If data is not valid, the query returns 32767.
SLISt Subsystem OVERlay Query :MACHine{1|2}:SLISt:OTAG? The OTAG query returns the O Marker position in time when time tagging is on or in states when state tagging is on, regardless of whether the marker was positioned in time or through a pattern search. If data is not valid, the query returns 9.9E37 for time tagging, or returns 32767 for state tagging.
SLISt Subsystem REMove REMove Command :MACHine{1|2}:SLISt:REMove The REMove command removes all labels, except the leftmost label, from the listing menu. Example OUTPUT XXX;":MACHINE1:SLIST:REMOVE" RUNTil Command :MACHine{1|2}:SLISt:RUNTil The RUNTil (run until) command allows you to define a stop condition when the trace mode is repetitive. Specifying OFF causes the analyzer to make runs until either the display’s STOP field is touched, or, when the STOP command is issued.
SLISt Subsystem RUNTil There are two conditions which are based on a comparison of the acquired state data and the compare data image. The analyzer can run until one of the following conditions is true: • Every channel of every label has the same value (EQUal). • Any channel of any label has a different value (NEQual). The RUNTil instruction (for state analysis) is available in both the SLISt and COMPare subsystems.
SLISt Subsystem TAVerage TAVerage Query :MACHine{1|2}:SLISt:TAVerage? The TAVerage query returns the value of the average time between the X and O Markers. If the number of valid runs is zero, the query returns 9.9E37. Valid runs are those where the pattern search for both the X and O markers was successful, resulting in valid delta-time measurements.
SLISt Subsystem TMINimum TMINimum Query :MACHine{1|2}:SLISt:TMINimum? The TMINimum query returns the value of the minimum time between the X and O Markers. If data is not valid, the query returns 9.9E37. Returned Format Example: [:MACHine{1|2}:SLISt:TMINimum] real number OUTPUT XXX;":MACHINE1:SLIST:TMINIMUM?" VRUNs Query :MACHine{1|2}:SLISt:VRUNs? The VRUNs query returns the number of valid runs and total number of runs made.
SLISt Subsystem XOTag XOTag Query :MACHine{1|2}:SLISt:XOTag? The XOTag query returns the time from the X to O markers when the marker mode is time or number of states from the X to O markers when the marker mode is state. If there is no data in the time mode the query returns 9.9E37. If there is no data in the state mode, the query returns 32767.
SLISt Subsystem XPATtern XPATtern Command :MACHine{1|2}:SLISt:XPATtern , The XPATtern command allows you to construct a pattern recognizer term for the X Marker which is then used with the XSEarch criteria when moving the marker on patterns. Since this command deals with only one label at a time, a complete specification could require several invocations.
SLISt Subsystem XSEarch XSEarch Command :MACHine{1|2}:SLISt:XSEarch , The XSEarch command defines the search criteria for the X Marker, which is then with associated XPATtern recognizer specification when moving the markers on patterns. The origin parameter tells the Marker to begin a search with the trigger or with the start of data. The occurrence parameter determines which occurrence of the XPATtern recognizer specification, relative to the origin, the marker actually searches for.
SLISt Subsystem XSTate XSTate Query :MACHine{1|2}:SLISt:XSTate? The XSTate query returns the line number in the listing where the X marker resides (−8191 to +8191). If data is not valid, the query returns 32767.
SLISt Subsystem XTAG Query :MACHine{1|2}:SLISt:XTAG? The XTAG query returns the X Marker position in time when time tagging is on or in states when state tagging is on, regardless of whether the marker was positioned in time or through a pattern search. If data is not valid tagged data, the query returns 9.9E37 for time tagging, or retruns 32767 for state tagging.
17–24
18 SWAVeform Subsystem
Introduction The commands in the State Waveform subsystem allow you to configure the display so that you can view state data as waveforms on up to 96 channels identified by label name and bit number. The 11 commands are analogous to their counterparts in the Timing Waveform subsystem. However, in this subsystem the x-axis is restricted to representing only samples (states), regardless of whether time tagging is on or off. As a result, the only commands which can be used for scaling are DELay and RANge.
SWAVeform Subsystem Figure 18-1 SWAVeform Subsystem Syntax Diagram 18–3
SWAVeform Subsystem SWAVeform Table 18-1 SWAVeform Parameter Values Parameter Value number_of_samples integer from −8191 to +8191 label_name string of up to 6 alphanumeric characters bit_id {OVERlay||ALL} bit_num integer representing a label bit from 0 to 31 range_values integer from 10 to 5000 (representing (10 × states/Division)) mark_type {X|O|XO|TRIGger} percent integer from 0 to 100 SWAVeform Selector :MACHine{1|2}:SWAVeform The SWAVeform (State Waveform) selector is used as
SWAVeform Subsystem ACCumulate ACCumulate Command :MACHine{1|2}:SWAVeform:ACCumulate {{ON|1}|{OFF|0}} The ACCumulate command allows you to control whether the waveform display gets erased between individual runs or whether subsequent waveforms are allowed to be displayed over the previous waveforms. Example OUTPUT XXX;":MACHINE1:SWAVEFORM:ACCUMULATE ON" Query :MACHine{1|2}:SWAVeform:ACCumulate? The ACCumulate query returns the current setting.
SWAVeform Subsystem CENTer Query :MACHine{1|2}:SWAVeform:ACQuisition? The ACQusition query returns the current acquisition mode. Returned Format [:MACHine{1|2}:SWAVeform:ACQuisition] {AUTOmatic|MANual} Example OUTPUT XXX;":MACHINE2:SWAVEFORM:ACQUISITION?" CENTer Command :MACHine{1|2}:SWAVeform:CENTer The CENTer command allows you to center the waveform display about the specified markers. The markers are placed on the waveform in the SLISt subsystem.
SWAVeform Subsystem CLRStat CLRStat Command :MACHine{1|2}:SWAVeform:CLRStat The CLRStat command allows you to clear the waveform statistics without having to stop and restart the acquisition. Example OUTPUT XXX;":MACHINE1:SWAVEFORM:CLRSTAT" DELay Command :MACHine{1|2}:SWAVeform:DELay The DELay command allows you to specify the number of samples between the State trigger and the horizontal center of the screen for the waveform display.
SWAVeform Subsystem INSert INSert Command :MACHine{1|2}:SWAVeform:INSert , The INSert command allows you to add waveforms to the state waveform display. Waveforms are added from top to bottom on the screen. When 96 waveforms are present, inserting additional waveforms replaces the last waveform. Bit numbers are zero based, so a label with 8 bits is referenced as bits 0 through 7. Specifying OVERlay causes a composite waveform display of all bits or channels for the specified label.
SWAVeform Subsystem REMove Query :MACHine{1|2}:SWAVeform:RANGe? The RANGe query returns the current range value. Returned Format Example [:MACHine{1|2}:SWAVeform:RANGe] integer from 10 to 5000 OUTPUT XXX;":MACHINE2:SWAVEFORM:RANGE?" REMove Command :MACHine{1|2}:SWAVeform:REMove The REMove command allows you to clear the waveform display before building a new display.
SWAVeform Subsystem TPOSition Query :MACHine{1|2}:SWAVeform:TAKenbranch? The TAKenbranch query returns the current setting. Returned Format [:MACHine{1|2}:SWAVeform:TAKenbranch] {STORe|NOSTore} Example OUTPUT XXX;":MACHINE2:SWAVEFORM:TAKENBRANCH?" TPOSition Command :MACHine{1|2}:SWAVeform:TPOSition {STARt|CENTer|END|POSTstore,} The TPOSition command allows you to control where the trigger point is placed.
SWAVeform Subsystem TPOSition Query :MACHine{1|2}:SWAVeform:TPOSition? The TPOSition query returns the current trigger setting.
18–12
19 SCHart Subsystem
Introduction The State Chart subsystem provides the commands necessary for programming the Chart display of 1660A-series logic analyzers. The commands allow you to build charts of label activity, using data normally found in the Listing display. The chart’s Y-axis is used to show data values for the label of your choice. The X-axis can be used in two different ways. In one, the X-axis represents states (shown as rows in the State Listing display).
SCHart Subsystem Figure 19-1 SCHart Subsystem Syntax Diagram 19–3
SCHart Subsystem SCHart Table 19-1 SCHart Parameter Values Parameter Values state_low_value integer from –8191 to +8191 state_high_value integer from to +8191 label_name string of up to 6 alphanumeric characters label_low_value string from 0 to 232 − 1 (#HFFFF) label_high_value string from to 232 − 1 (#HFFFF) low_value string from 0 to 232 − 1 (#HFFFF) high_value string from low_value to 232 − 1 (#HFFFF) SCHart Selector :MACHine{1|2}:SCHart The SCHart s
SCHart Subsystem HAXis Example OUTPUT XXX;":MACHINE1:SCHART:ACCUMULATE OFF" Query :MACHine{1|2}:SCHart:ACCumulate? The ACCumulate query returns the current setting. The query always shows the setting as the character "0" (off) or "1" (on).
SCHart Subsystem HAXis integer from −8191 to +8191 integer from to +8191 string of up to 6 alphanumeric characters string from 0 to 232−1 (#HFFFF) string from to 232–1 (#HFFFF) Examples OUTPUT XXX;":MACHINE1:SCHART:HAXIS STATES, −100, 100" OUTPUT XXX;":MACHINE1:SCHART:HAXIS ’READ’, ’−511’, ’511’" Query :MACHine{1|2}:SCHart:HAXis? The HAXis query returns the current horiz
SCHart Subsystem VAXis VAXis Command :MACHine{1|2}:SCHart:VAXis ,, The VAXis command allows you to choose which label will be plotted on the vertical axis of the chart and scale the vertical axis by specifying the high value and low value.
19–8
20 COMPare Subsystem
Introduction Commands in the state COMPare subsystem provide the ability to do a bit-by-bit comparison between the acquired state data listing and a compare data image.
COMPare Subsystem Figure 20-1 COMPare Subsystem Syntax Diagram 20–3
COMPare Subsystem COMPare Table 20-1 Compare Parameter Values Parameter Values label_name string of up to 6 characters care_spec string of characters "{*|.}..." * care . don’t care line_num integer from –8191 to +8191 data_pattern "{B{0|1|X} . . . | #Q{0|1|2|3|4|5|6|7|X} . . . | #H{0|1|2|3|4|5|6|7|8|9|A|B|C|D|E|F|X} . . . | {0|1|2|3|4|5|6|7|8|9} . . .
COMPare Subsystem CLEar CLEar Command :MACHine{1|2}:COMPare:CLEar The CLEar command clears all "don’t cares" in the reference listing and replaces them with zeros except when the CLEar command immediately follows the SET command (see SET command).
COMPare Subsystem COPY Query :MACHine{1|2}:COMPare:CMASk ? The CMASk query returns the state of the bits in the channel mask for a given label in the compare listing image. Returned Format
COMPare Subsystem DATA DATA Command :MACHine{1|2}:COMPare:DATA {, ,|, [, ]... } The DATA command allows you to edit the compare listing image for a given label and state row. When DATA is sent to an instrument where no compare image is defined (such as at power-up) all other data in the image is set to don’t cares.
COMPare Subsystem DATA Query :MACHine{1|2}:COMPare:DATA? , The DATA query returns the value of the compare listing image for a given label and state row. Returned Format [:MACHine{1|2}:COMPare:DATA] ,, A string of up to 6 alphanumeric characters An integer from –8191 to +8191 A string in one of the following forms: "{B{0|1|X} . . . | #Q{0|1|2|3|4|5|6|7|X} . . .
COMPare Subsystem FIND FIND Query :MACHine{1|2}:COMPare:FIND? The FIND query is used to get the line number of a specified difference occurence (first, second, third, etc) within the current compare range, as dictated by the RANGe command (see page 20-11). A difference is counted for each line where at least one of the current labels has a discrepancy between its acquired state data listing and its compare data image.
COMPare Subsystem LINE LINE Command :MACHine{1|2}:COMPare:LINE The LINE command allows you to center the compare listing data about a specified line number. An integer from –8191 to +8191 Example OUTPUT XXX;":MACHINE2:COMPARE:LINE –511" Query :MACHine{1|2}:COMPare:LINE? The LINE query returns the current line number specified.
COMPare Subsystem RANGe RANGe Command :MACHine{1|2}:COMPare:RANGe {FULL|PARTial,,} The RANGe command allows you to define the boundaries for the comparison. The range entered must be a subset of the lines in the acquire memory.
COMPare Subsystem RUNTil RUNTil Command :MACHine{1|2}:COMPare:RUNTil {OFF| LT,|GT, |INRange,,|OUTRange,,|EQUal|NEQual} The RUNTil (run until) command allows you to define a stop condition when the trace mode is repetitive. Specifying OFF causes the analyzer to make runs until either the display’s STOP field is touched or the STOP command is issued. There are four conditions based on the time between the X and O markers.
COMPare Subsystem SET Example OUTPUT XXX;":MACHINE2:COMPARE:RUNTIL EQUAL" Query :MACHine{1|2}:COMPare:RUNTil? The RUNTil query returns the current stop criteria for the comparison when running in repetitive trace mode.
20–14
21 TFORmat Subsystem
Introduction The TFORmat subsystem contains the commands available for the Timing Format menu in the 1660-series logic analyzers.
TFORmat Subsystem Figure 21-1 TFORmat Subsystem Syntax Diagram 21–3
TFORmat Subsystem TFORmat Table 21-1 TFORmat Paramter Values Parameter Values size {FULL|HALF} {1|2|3|4|5|6|7|8} name string of up to 6 alphanumeric characters polarity {POSitive|NEGative} pod_specification format (integer from 0 to 65535) for a pod (pods are assigned in decreasing order) value voltage (real number) −6.00 to +6.
TFORmat Subsystem ACQMode ACQMode Command :MACHine{1|2}:TFORmat:ACQMode {TRANSitional |CONVentional |GLITch} The ACQMode (acquisition mode) command allows you to select the acquisition mode for the timing analyzer. The options are: • • • • • conventional mode at full-channel 250 MHz conventional mode at half-channel 500 Mhz transitional mode at full-channel 125 MHz transitional mode at half-channel 250 MHz glitch mode.
TFORmat Subsystem LABel LABel Command :MACHine{1|2}:Tformat:LABel ,[, , , [,,]...] The LABel command allows you to specify polarity and to assign channels to new or existing labels. If the specified label name does not match an existing label name, a new label will be created. The order of the pod-specification parameters is significant.
TFORmat Subsystem REMove Examples OUTPUT XXX;":MACHINE2:TFORMAT:LABEL ’STAT’, POSITIVE, 0,127,40312" OUTPUT XXX;":MACHINE2:TFORMAT:LABEL ’SIG 1’, #B11,#B0000000011111111, #B0000000000000000 " Query :MACHine{1|2}:Tformat:LABel? The LABel query returns the current specification for the selected (by name) label. If the label does not exist, nothing is returned. Numbers are always returned in decimal format.
TFORmat Subsystem THReshold THReshold Command :MACHine{1|2}:TFORmat:THReshold {TTL|ECL|} The THReshold command allows you to set the voltage threshold for a given pod to ECL, TTL, or a specific voltage from −6.00 V to +6.00 V in 0.05 volt increments. pod number {1|2|3|4|5|6|7|8} voltage (real number) −6.00 to +6.00 TTL default value of +1.6 V ECL default value of −1.3 V Example OUTPUT XXX;":MACHINE1:TFORMAT:THRESHOLD1 4.
22 TTRigger (TTRace) Subsystem
Introduction The TTRigger subsystem contains the commands available for the Timing Trigger menu in the 1660-series logic analyzers. The Timing Trigger subsystem will also accept the TTRace selector as used in previous 1650-series logic analyzers to eliminate the need to rewrite programs containing TTRace as the selector keyword.
TTRigger (TTRace) Subsystem Figure 22-1 TTRigger Subsystem Syntax Diagram 22–3
TTRigger (TTRace) Subsystem Figure 22-1 (continued) TTRigger Subsystem Syntax Diagram (continued) 22–4
TTRigger (TTRace) Subsystem Table 22-1 TTRigger Parameter Values Parameter Values branch_qualifier to_lev_num integer from 1 to last level proceed_qualifier occurrence number from 1 to 1048575 label_name string of up to 6 alphanumeric characters glitch_edge_spec string consisting of {R|F|E|G|.} R, F, and E represents rising, falling, either edge respectively. G represents a glitch and a period (.) represents a don’t care. start_pattern "{#B{0|1} . . .
TTRigger (TTRace) Subsystem Qualifier Qualifier The qualifier for the timing trigger subsystem can be terms A through J, Timer 1 and 2, and Range 1 and 2. In addition, qualifiers can be the NOT boolean function of terms, timers, and ranges. The qualifier can also be an expression or combination of expressions as shown below and figure 22-2, "Complex Qualifier," on page 22-11. The following parameters show how qualifiers are specified in all commands of the TTRigger subsystem that use .
TTRigger (TTRace) Subsystem Qualifier {AND|NAND|OR|NOR|XOR|NXOR} {A|NOTA} {B|NOTB} {C|NOTC} {D|NOTD} {E|NOTE} {F|NOTF} {G|NOTG} {H|NOTH} {I|NOTI} {J|NOTJ} {IN_RANGE1|OUT_RANGE1} {IN_RANGE2|OUT_RANGE2} {GLEDge1|NOT GLEDge1} {GLEDge2|NOT GLEDge2} {TIMER1<|TIMER1>} {TIMER2<|TIMER2>} * = is optional such that it ca
TTRigger (TTRace) Subsystem TTRigger (TTRace) Qualifier Rules The following rules apply to qualifiers: • Qualifiers are quoted strings and, therefore, need quotes. • Expressions are evaluated from left to right. • Parenthesis are used to change the order evaluation and, therefore, are optional. • An expression must map into the combination logic presented in the combination pop-up menu within the TTRigger menu.
TTRigger (TTRace) Subsystem ACQuisition ACQuisition Command :MACHine{1|2}:TTRigger:ACQuisition {AUTOmatic|MANual} The ACQuisition command allows you to specify the acquisition mode for the Timing analyzer. Example OUTPUT XXX;":MACHINE1:TTRIGGER:ACQUISITION AUTOMATIC" Query :MACHine{1|2}:TTRigger:ACQuisition? The ACQuisition query returns the current acquisition mode specified.
TTRigger (TTRace) Subsystem BRANch expression is not changed. Figure 22-2, on page 22-11 shows a complex expression as seen in the Timing Trigger menu. Example The following statements are all correct and have the same meaning. Notice that the conventional rules for precedence are not followed. The expressions are evaluated from left to right.
TTRigger (TTRace) Subsystem BRANch Query Syntax :MACHine{1|2}:TTRigger:BRANch? The BRANch query returns the current branch qualifier specification for a given sequence level. Returned Format [:MACHine{1|2}:TTRigger:BRANch] , Example OUTPUT XXX;":MACHINE1:TTRIGGER:BRANCH3?" Figure 22-2 Complex Qualifier Figure 22-2 is a front-panel representation of the complex qualifier (a OR b) And (g OR h).
TTRigger (TTRace) Subsystem CLEar Terms A through E, RANGE 1, GLITCH/EDGE1, and TIMER 1 must be grouped together and terms F through J, RANGE 2, GLITCH/EDGE2, and TIMER 2 must be grouped together. In the first level, terms from one group may not be mixed with terms from the other. For example, the expression ((A OR IN_RANGE2) AND (C OR H)) is not allowed because the term C cannot be specified in the E through J group. In the first level, the operators you can use are AND, NAND, OR, NOR, XOR, NXOR.
TTRigger (TTRace) Subsystem FIND FIND Command :MACHine{1|2}:TTRigger:FIND , The FIND command defines the time qualifier for a given sequence level. The qualifier tells the timing analyzer when to proceed to the next sequence level. When this proceed qualifier is matched the specified number of times, the sequencer will proceed to the next sequence level.
TTRigger (TTRace) Subsystem GLEDge Query :MACHine{1|2}:TTRigger:FIND4? The FIND query returns the current time qualifier specification for a given sequence level. Returned Format [:MACHine{1|2}:TTRigger:FIND] , Example OUTPUT XXX;":MACHINE1:TTRIGGER:FIND?" GLEDge Command :MACHine{1|2}:TTRigger:GLEDge , The GLEDge (glitch/edge) command allows you to define edge and glitch specifications for a given label.
TTRigger (TTRace) Subsystem RANGe Example For 8 bits assigned and no glitch: OUTPUT XXX;":MACHINE1:TTRIGGER:GLEDGE1 ’DATA’, ’....F..E’" For 16 bits assigned with glitch: OUTPUT XXX;":MACHINE1:TTRIGGER:GLEDGE1 ’DATA’, ’....GGG.....F..R’" Query :MACHine{1|2}:TTRigger:GLEDe? The GLEDge query returns the current specification for the given label.
TTRigger (TTRace) Subsystem RANGe string of up to 6 alphanumeric characters "{#B{0|1} . . . | #Q{0|1|2|3|4|5|6|7} . . . | #H{0|1|2|3|4|5|6|7|8|9|A|B|C|D|E|F} . . . | {0|1|2|3|4|5|6|7|8|9} . . . }" "{#B{0|1} . . . | #Q{0|1|2|3|4|5|6|7} . . . | #H{0|1|2|3|4|5|6|7|8|9|A|B|C|D|E|F} . . . | {0|1|2|3|4|5|6|7|8|9} . . .
TTRigger (TTRace) Subsystem SEQuence SEQuence Command :MACHine{1|2}:TTRigger:SEQuence The SEQuence command defines the timing analyzer trace sequence. First, it deletes the current trace sequence. Then, it inserts the number of levels specified, with default settings. The number of levels can be between 1 and 10 when the analyzer is armed by the RUN key.
TTRigger (TTRace) Subsystem SPERiod SPERiod Command :MACHine{1|2}:TTRigger:SPERiod The SPERiod command allows you to set the sample period of the timing analyzer in the Conventional and Glitch modes.
TTRigger (TTRace) Subsystem TCONtrol TCONtrol Command :MACHine{1|2}:TTRigger:TCONtrol , {OFF|STARt|PAUSe|CONTinue} The TCONtrol (timer control) command allows you to turn off, start, pause, or continue the timer for the specified level. The time value of the timer is defined by the TIMER command.
TTRigger (TTRace) Subsystem TERM TERM Command :MACHine{1|2}:TTRigger:TERM ,, The TERM command allows you to a specify a pattern recognizer term in the specified machine. Each command deals with only one label in the given term; therefore, a complete specification could require several commands. Since a label can contain 32 or less bits, the range of the pattern value will be between 232 − 1 and 0.
TTRigger (TTRace) Subsystem TIMER Query :MACHine{1|2}:TTRigger:TERM? , The TERM query returns the specification of the term specified by term identification and label name. Returned Format [:MACHine{1|2}:STRAce:TERM] ,, Example OUTPUT XXX;":MACHINE1:TTRIGGER:TERM? B,’DATA’ " TIMER Command :MACHine{1|2}:TTRigger:TIMER{1|2} The TIMER command sets the time value for the specified timer.
TTRigger (TTRace) Subsystem TPOSition TPOSition Command :MACHine{1|2}:TTRigger:TPOSition {STARt|CENTer|END|DELay, | POSTstore,} The TPOSition (trigger position) command allows you to set the trigger at the start, center, end or at any position in the trace (poststore). Poststore is defined as 0 to 100 percent with a poststore of 100 percent being the same as start position and a poststore 0 percent being the same as an end trace.
23 TWAVeform Subsystem
Introduction The TWAVeform subsystem contains the commands available for the Timing Waveforms menu in the 1660-series logic analyzer.
TWAVeform Subsystem Figure 23-1 TWAVeform Subsystem Syntax Diagram 23–3
TWAVeform Subsystem Figure 23-1 (continued) TWAVeform Subsystem Syntax Diagram (continued) 23–4
TWAVeform Subsystem Figure 23-1 (continued) TWAVeform Subsystem Syntax Diagram (continued) 23–5
TWAVeform Subsystem Table 23-1 TWAVeform Parameter Values Parameter Value delay_value real number between −2500 s and +2500 s module_spec {1|2|3|4|5|6|7|8|9|10} 2 through 10 unused bit_id integer from 0 to 31 waveform string containing {1|2} acquisition_spec {A|B|C|D|E|F|G|H|I|J} (slot where acquisition card is located) label_name string of up to 6 alphanumeric characters label_pattern "{#B{0|1|X} . . . | #Q{0|1|2|3|4|5|6|7|X}...| #H{0|1|2|3|4|5|6|7|8|9|A|C|D|E|F|X}...
TWAVeform Subsystem TWAVeform TWAVeform Selector :MACHine{1|2}:TWAVeform The TWAVeform selector is used as part of a compound header to access the settings found in the Timing Waveforms menu. It always follows the MACHine selector because it selects a branch below the MACHine level in the command tree.
TWAVeform Subsystem ACQuisition ACQuisition Command :MACHine{1|2}:TWAVeform:ACQuisition {AUTOmatic|MANual} The ACQuisition command allows you to specify the acquisition mode for the state analyzer. The acquisition modes are automatic and manual. Example OUTPUT XXX;":MACHINE2:TWAVEFORM:ACQUISITION AUTOMATIC" Query MACHine{1|2}:TWAVeform:ACQuisition? The ACQuisition query returns the current acquisition mode.
TWAVeform Subsystem CLRPattern CLRPattern Command :MACHine{1|2}:TWAVeform:CLRPattern {X|O|ALL} The CLRPattern command allows you to clear the patterns in the selected Specify Patterns menu. Example OUTPUT XXX;":MACHINE1:TWAVEFORM:CLRPATTERN ALL" CLRStat Command :MACHine{1|2}:Twaveform:CLRStat The CLRStat command allows you to clear the waveform statistics without having to stop and restart the acquisition.
TWAVeform Subsystem INSert real number between −2500 s and +2500 s Example OUTPUT XXX;":MACHINE1:TWAVEFORM:DELAY 100E−6" Query :MACHine{1|2}:TWAVeform:DELay? The DELay query returns the current time offset (delay) value from the trigger.
TWAVeform Subsystem MMODe MMODe Command :MACHine{1|2}:TWAVeform:MMODe {OFF|PATTern|TIME|MSTats} The MMODe (Marker Mode) command selects the mode controlling marker movement and the display of the marker readouts. When PATTern is selected, the markers will be placed on patterns. When TIME is selected, the markers move on time. In MSTats, the markers are placed on patterns, but the readouts will be time statistics.
TWAVeform Subsystem OCONdition OCONdition Command :MACHine{1|2}:TWAVeform:OCONdition {ENTering|EXITing} The OCONdition command specifies where the O marker is placed. The O marker can be placed on the entry or exit point of the OPATtern when in the PATTern marker mode. Example OUTPUT XXX; ":MACHINE1:TWAVEFORM:OCONDITION ENTERING" Query :MACHine{1|2}:TWAVeform:OCONdition? The OCONdition query returns the current setting.
TWAVeform Subsystem OPATtern OPATtern Command :MACHine{1|2}:TWAVeform:OPATtern , The OPATtern command allows you to construct a pattern recognizer term for the O marker which is then used with the OSEarch criteria and OCONdition when moving the marker on patterns. Since this command deals with only one label at a time, a complete specification could require several invocations.
TWAVeform Subsystem OSEarch OSEarch Command :MACHine{1|2}:TWAVeform:OSEarch , The OSEarch command defines the search criteria for the O marker which is then used with the associated OPATtern recognizer specification and the OCONdition when moving markers on patterns. The origin parameter tells the marker to begin a search with the trigger or with the X marker.
TWAVeform Subsystem OTIMe OTIMe Command :MACHine{1|2}:TWAVeform:OTIMe The OTIMe command positions the O marker in time when the marker mode is TIME. If data is not valid, the command performs no action. real number −2.5 ks to +2.5 ks Example OUTPUT XXX; ":MACHINE1:TWAVEFORM:OTIME 30.0E−6" Query :MACHine{1|2}:TWAVeform:OTIMe? The OTIMe query returns the O marker position in time. If data is not valid, the query returns 9.9E37.
TWAVeform Subsystem RANGe RANGe Command :MACHine{1|2}:TWAVeform:RANGe The RANGe command specifies the full-screen time in the timing waveform menu. It is equivalent to ten times the seconds-per-division setting on the display. The allowable values for RANGe are from 10 ns to 10 ks. real number between 10 ns and 10 ks Example OUTPUT XXX;":MACHINE1:TWAVEFORM:RANGE 100E−9" Query :MACHine{1|2}:TWAVeform:RANGe? The RANGe query returns the current full-screen time.
TWAVeform Subsystem RUNTil RUNTil Command :MACHine{1|2}:TWAVeform:RUNTil The RUNTil (run until) command defines stop criteria based on the time between the X and O markers when the trace mode is in repetitive. When OFF is selected, the analyzer will run until either the STOP touch screen field is touched, or, the STOP command is sent. Run until time between X and O marker options are: • • • • Less Than (LT) a specified time value. Greater Than (GT) a specified time value.
TWAVeform Subsystem SPERiod SPERiod Command :MACHine{1|2}:TWAVeform:SPERiod The SPERiod command allows you to set the sample period of the timing analyzer in the Conventional and Glitch modes.
TWAVeform Subsystem TAVerage TAVerage Query :MACHine{1|2}:TWAVeform:TAVerage? The TAVerage query returns the value of the average time between the X and O markers. If there is no valid data, the query returns 9.9E37. Returned Format Example [:MACHine{1|2}:TWAVeform:TAVerage] real number OUTPUT XXX;":MACHINE1:TWAVEFORM:TAVERAGE?" TMAXimum Query :MACHine{1|2}:TWAVeform:TMAXimum? The TMAXimum query returns the value of the maximum time between the X and O markers.
TWAVeform Subsystem TMINimum TMINimum Query :MACHine{1|2}:TWAVeform:TMINimum? The TMINimum query returns the value of the minimum time between the X and O markers. If there is no valid data, the query returns 9.9E37.
TWAVeform Subsystem VRUNs Query :MACHine{1|2}:TWAVeform:TPOSition? The TPOSition query returns the current trigger setting. Returned Format Example [:MACHine{1|2}:TWAVeform:TPOSition] {STARt|CENTer|END|DELay, |POSTstore,} real number from 0 to 500 seconds OUTPUT XXX;":MACHINE2:TWAVEFORM:TPOSition?" VRUNs Query :MACHine{1|2}:TWAVeform:VRUNs? The VRUNs query returns the number of valid runs and total number of runs made.
TWAVeform Subsystem XCONdition XCONdition Command :MACHine{1|2}:TWAVeform:XCONdition {ENTering|EXITing} The XCONdition command specifies where the X marker is placed. The X marker can be placed on the entry or exit point of the XPATtern when in the PATTern marker mode. Example OUTPUT XXX; ":MACHINE1:TWAVEFORM:XCONDITION ENTERING" Query :MACHine{1|2}:TWAVeform:XCONdition? The XCONdition query returns the current setting.
TWAVeform Subsystem XPATtern XPATtern Command :MACHine{1|2}:TWAVeform:XPATtern , The XPATtern command allows you to construct a pattern recognizer term for the X marker which is then used with the XSEarch criteria and XCONdition when moving the marker on patterns. Since this command deals with only one label at a time, a complete specification could require several iterations.
TWAVeform Subsystem XSEarch XSEarch Command :MACHine{1|2}:TWAVeform:XSEarch , The XSEarch command defines the search criteria for the X marker which is then used with the associated XPATtern recognizer specification and the XCONdition when moving markers on patterns. The origin parameter tells the marker to begin a search with the trigger.
TWAVeform Subsystem XTIMe XTIMe Command :MACHine{1|2}:TWAVeform:XTIMe The XTIMe command positions the X marker in time when the marker mode is TIME. If data is not valid, the command performs no action. real number from −2.5 ks to +2.5 ks Example OUTPUT XXX; ":MACHINE1:TWAVEFORM:XTIME 40.0E−6" Query :MACHine{1|2}:TWAVeform:XTIMe? The XTIMe query returns the X marker position in time. If data is not valid, the query returns 9.9E37.
23–26
24 TLISt Subsystem
Introduction The TLISt subsystem contains the commands available for the Timing Listing menu in the 1660-series logic analyzers and is the same as the SLISt subsystem with the exception of the OCONdition and XCONdition commands.
TLISt Subsystem Figure 24-1 TLISt Subsystem Syntax Diagram 24–3
TLISt Subsystem Figure 24-1 (continued) TLISt Subsystem Syntax Diagram (continued) 24–4
TLISt Subsystem Figure 24-1 (continued) TLISt Subsystem Syntax Diagram (continued) 24–5
TLISt Subsystem Table 24-1 TLISt Parameter Values Parameter Values module_num {1|2|3|4|5|6|7|8|9|10} 2 through 10 not used mach_num {1|2} col_num integer from 1 to 61 line_number integer from −8191 to +8191 label_name string of up to 6 alphanumeric characters base {BINary|HEXadecimal|OCTal|DECimal|TWOS| ASCii|SYMBol|IASSembler} for labels or {ABSolute|RELative} for tags line_num_mid_screen integer from −8191to +8191 label_pattern "{#B{0|1|X} . . . | #Q{0|1|2|3|4|5|6|7|X} . . .
TLISt Subsystem TLISt TLISt Selector :MACHine{1|2}:TLISt The TLISt selector is used as part of a compound header to access those settings normally found in the Timing Listing menu. It always follows the MACHine selector because it selects a branch directly below the MACHine level in the command tree.
TLISt Subsystem CLRPattern integer from 1 to 61 {1|2|3|4|5|6|7|8|9|10} 2 through 10 unused a string of up to 6 alphanumeric characters {BINary|HEXadecimal|OCTal|DECimal|TWOS|ASCii|SYMBol| IASSembler} for labels or {ABSolute|RELative} for tags Example OUTPUT XXX;":MACHINE1:TLIST:COLUMN 4,1,’A’,HEX" Query :MACHine{1|2}:TLISt:COLumn? The COLumn query returns the column number, label name, and base for the specified column.
TLISt Subsystem DATA DATA Query :MACHine{1|2}:TLISt:DATA? , The DATA query returns the value at a specified line number for a given label. The format will be the same as the one shown in the Listing display. Returned Format Example [:MACHine{1|2}:TLISt:DATA] ,, integer from −8191 to +8191 string of up to 6 alphanumeric characters "{#B{0|1|X} . . . | #Q{0|1|2|3|4|5|6|7|X} . . .
TLISt Subsystem MMODe Query :MACHine{1|2}:TLISt:LINE? The LINE query returns the line number for the state currently in the box at the center of the screen. Returned Format [:MACHine{1|2}:TLISt:LINE] Example OUTPUT XXX;":MACHINE1:TLIST:LINE?" MMODe Command :MACHine{1|2}:TLISt:MMODe The MMODe command (Marker Mode) selects the mode controlling the marker movement and the display of marker readouts.
TLISt Subsystem OCONdition OCONdition Command :MACHine{1|2}:TLISt:OCONdition {ENTering|EXITing} The OCONdition command specifies where the O marker is placed. The O marker can be placed on the entry or exit point of the OPATtern when in the PATTern marker mode. Example OUTPUT XXX; ":MACHINE1:TLIST:OCONDITION ENTERING" Query :MACHine{1|2}:TLISt:OCONdition? The OCONdition query returns the current setting.
TLISt Subsystem OSEarch string of up to 6 alphanumeric characters "{#B{0|1|X} . . . | #Q{0|1|2|3|4|5|6|7|X} . . . | #H{0|1|2|3|4|5|6|7|8|9|A|B|C|D|E|F|X} . . . | {0|1|2|3|4|5|6|7|8|9} . . . }" Examples OUTPUT XXX;":MACHINE1:TLIST:OPATTERN ’DATA’,’255’ " OUTPUT XXX;":MACHINE1:TLIST:OPATTERN ’ABC’,’#BXXXX1101’ " Query :MACHine{1|2}:TLISt:OPATtern? The OPATtern query returns the pattern specification for a given label name.
TLISt Subsystem OSTate Example OUTPUT XXX;":MACHINE1:TLIST:OSEARCH +10,TRIGGER" Query :MACHine{1|2}:TLISt:OSEarch? The OSEarch query returns the search criteria for the O marker. Returned Format [:MACHine{1|2}:TLISt:OSEarch] , Example OUTPUT XXX;":MACHINE1:TLIST:OSEARCH?" OSTate Query :MACHine{1|2}:TLISt:OSTate? The OSTate query returns the line number in the listing where the O marker resides (−8191 to +8191). If data is not valid, the query returns 32767.
TLISt Subsystem OTAG OTAG Command :MACHine{1|2}:TLISt:OTAG The OTAG command specifies the tag value on which the O Marker should be placed. The tag value is time. If the data is not valid tagged data, no action is performed. real number Example :OUTPUT XXX;":MACHINE1:TLIST:OTAG 40.0E−6" Query :MACHine{1|2}:TLISt:OTAG? The OTAG query returns the O Marker position in time regardless of whether the marker was positioned in time or through a pattern search.
TLISt Subsystem RUNTil RUNTil Command :MACHine{1|2}:TLISt:RUNTil The RUNTil (run until) command allows you to define a stop condition when the trace mode is repetitive. Specifying OFF causes the analyzer to make runs until either the display’s STOP field is touched, or, until the STOP command is issued. There are four conditions based on the time between the X and O markers as follows: • • • • The difference is less than (LT) some value. The difference is greater than (GT) some value.
TLISt Subsystem TAVerage TAVerage Query :MACHine{1|2}:TLISt:TAVerage? The TAVerage query returns the value of the average time between the X and O Markers. If the number of valid runs is zero, the query returns 9.9E37. Valid runs are those where the pattern search for both the X and O markers was successful, resulting in valid delta-time measurements.
TLISt Subsystem TMINimum TMINimum Query :MACHine{1|2}:TLISt:TMINimum? The TMINimum query returns the value of the minimum time between the X and O Markers. If data is not valid, the query returns 9.9E37. Returned Format Example [:MACHine{1|2}:TLISt:TMINimum] real number OUTPUT XXX;":MACHINE1:TLIST:TMINIMUM?" VRUNs Query :MACHine{1|2}:TLISt:VRUNs? The VRUNs query returns the number of valid runs and total number of runs made.
TLISt Subsystem XCONdition XCONdition Command :MACHine{1|2}:TLISt:XCONdition {ENTering|EXITing} The XCONdition command specifies where the X marker is placed. The X marker can be placed on the entry or exit point of the XPATtern when in the PATTern marker mode. Example OUTPUT XXX; ":MACHINE1:TLIST:XCONDITION ENTERING" Query :MACHine{1|2}:TLISt:XCONdition? The XCONdition query returns the current setting.
TLISt Subsystem XOTime XOTime Query :MACHine{1|2}:TLISt:XOTime? The XOTime query returns the time from the X to O markers. If there is no data in the time mode the query returns 9.9E37.
TLISt Subsystem XSEarch Examples OUTPUT XXX;":MACHINE1:TLIST:XPATTERN ’DATA’,’255’ " OUTPUT XXX;":MACHINE1:TLIST:XPATTERN ’ABC’,’#BXXXX1101’ " Query :MACHine{1|2}:TLISt:XPATtern? The XPATtern query returns the pattern specification for a given label name.
TLISt Subsystem XSTate Query :MACHine{1|2}:TLISt:XSEarch? The XSEarch query returns the search criteria for the X marker. Returned Format [:MACHine{1|2}:TLISt:XSEarch] , Example OUTPUT XXX;":MACHINE1:TLIST:XSEARCH?" XSTate Query :MACHine{1|2}:TLISt:XSTate? The XSTate query returns the line number in the listing where the X marker resides (−8191 to +8191). If data is not valid, the query returns 32767.
TLISt Subsystem XTAG XTAG Command :MACHine{1|2}:TLISt:XTAG The XTAG command specifies the tag value on which the X Marker should be placed. The tag value is time. If the data is not valid tagged data, no action is performed. real number Example OUTPUT XXX;":MACHINE1:TLIST:XTAG 40.0E−6" Query :MACHine{1|2}:TLISt:XTAG? The XTAG query returns the X Marker position in time regardless of whether the marker was positioned in time or through a pattern search.
25 SYMBol Subsystem
Introduction The SYMBol subsystem contains the commands that allow you to define symbols on the controller and download them to the 1660-series logic analyzers.
SYMBol Subsystem Figure 25-1 SYMBol Subsystem Syntax Diagram 25–3
SYMBol Subsystem SYMBol Table 25-1 SYMBol Parameter Values Parameter Values label_name string of up to 6 alphanumeric characters symbol_name string of up to 16 alphanumeric characters pattern_value "{#B{0|1|X} . . . | #Q{0|1|2|3|4|5|6|7|X} . . . | #H{0|1|2|3|4|5|6|7|8|9|A|B|C|D|E|F|X} . . . | {0|1|2|3|4|5|6|7|8|9} . . . }" start_value "{#B{0|1} . . . | #Q{0|1|2|3|4|5|6|7} . . . | #H{0|1|2|3|4|5|6|7|8|9|A|B|C|D|E|F} . . . | {0|1|2|3|4|5|6|7|8|9} . . . }" stop_value "{#B{0|1} . . .
SYMBol Subsystem BASE BASE Command :MACHine{1|2}:SYMBol:BASE , The BASE command sets the base in which symbols for the specified label will be displayed in the symbol menu. It also specifies the base in which the symbol offsets are displayed when symbols are used. BINary is not available for labels with more than 20 bits assigned. In this case the base will default to HEXadecimal.
SYMBol Subsystem PATTern PATTern Command :MACHine{1|2}:SYMBol:PATTern , , The PATTern command allows you to create a pattern symbol for the specified label. Because don’t cares (X) are allowed in the pattern value, it must always be expressed as a string. You may still use different bases, though don’t cares cannot be used in a decimal number.
SYMBol Subsystem REMove string of up to 6 alphanumeric characters string of up to 16 alphanumeric characters "{#B{0|1} . . . | #Q{0|1|2|3|4|5|6|7} . . . | #H{0|1|2|3|4|5|6|7|8|9|A|B|C|D|E|F} . . . | {0|1|2|3|4|5|6|7|8|9} . . . }" "{#B{0|1} . . . | #Q{0|1|2|3|4|5|6|7} . . . | #H{0|1|2|3|4|5|6|7|8|9|A|B|C|D|E|F} . . . | {0|1|2|3|4|5|6|7|8|9} . . .
SYMBol Subsystem WIDTh WIDTh Command :MACHine{1|2}:SYMBol:WIDTh , The WIDTh command specifies the width (number of characters) in which the symbol names will be displayed when symbols are used. The WIDTh command does not affect the displayed length of the symbol offset value.
26 DATA and SETup Commands
Introduction The DATA and SETup commands are SYSTem commands that allow you to send and receive block data between the 1660-series logic analyzer and a controller. Use the DATA instruction to transfer acquired timing and state data, and the SETup instruction to transfer instrument configuration data. This is useful for: • Re-loading to the logic analyzer • Processing data later • Processing data in the controller This chapter explains how to use these commands.
DATA and SETup Commands Data Format Data Format To understand the format of the data within the block data, there are four important things to keep in mind. • • • • Data is sent to the controller in binary form. Each byte, as described in this chapter, contains 8 bits. The first bit of each byte is the MSB (most significant bit). Byte descriptions are printed in binary, decimal, or ASCII depending on how the data is described.
DATA and SETup Commands :SYSTem:DATA :SYSTem:DATA Command :SYSTem:DATA The SYSTem:DATA command transmits the acquisition memory data from the controller to the 1660-series logic analyzer. The block data consists of a variable number of bytes containing information captured by the acquisition chips. The information will be in one of three formats, depending on the type of data captured. The three formats are glitch, transitional, conventional timing or state.
DATA and SETup Commands :SYSTem:DATA 16 bytes, described in chapter 26, "Section Header Description". Format depends on the specific section. Example OUTPUT XXX;":SYSTEM:DATA" The total length of a section is 16 (for the section header) plus the length of the section data. So when calculating the value for , don’t forget to include the length of the section headers.
DATA and SETup Commands Section Header Description Section Header Description The section header uses bytes 1 through 16 (this manual begins counting at 1; there is no byte 0). The 16 bytes of the section header are as follows: Byte Position 1 10 bytes - Section name ("DATA space space space space space space" in ASCII for the DATA instruction).
DATA and SETup Commands Data Preamble Description The next 40 bytes are for Analyzer 1 Data Information.
DATA and SETup Commands Data Preamble Description Byte Position 26 1 byte - Master chip for this analyzer. This decimal value returns which chip’s time tag data is valid in a non-transitional mode; for example, state with time tags.
DATA and SETup Commands Data Preamble Description Byte Position 61 101 40 bytes - The next 40 bytes are for Analyzer 2 Data Information. They are organized in the same manner as Analyzer 1 above, but they occupy bytes 61 through 100. 26 bytes - Number of valid rows of data (starting at byte 177) for each pod. The 26 bytes of this group are organized as follows: Bytes 1 and 2 - Unused Bytes 3 and 4 - Unused. Bytes 5 and 6 - Unused. Bytes 7 and 8 - Unused. Bytes 9 and 10 - Unused.
DATA and SETup Commands Acquisition Data Description Byte Position 127 26 bytes - Row of data containing the trigger point. This byte group is organized in the same way as the data rows (starting at byte 101 above). These binary numbers are base zero numbers which start from the first sample stored for a specific pod. For example, if bytes 151 and 152 contained a binary number with a decimal equivalent of +1018, the data row having the trigger is the 1018th data row on pod 1.
DATA and SETup Commands Acquisition Data Description Byte Position clock lines Pod 81 Pod 71 pod 62 pod 52 pod 43 pod 33 pod 2 pod 14 177 2 bytes 2 bytes 2 bytes 2 bytes 2 bytes 2 bytes 2 bytes 2 bytes 2 bytes 195 2 bytes 2 bytes 2 bytes 2 bytes 2 bytes 2 bytes 2 bytes 2 bytes 2 bytes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
DATA and SETup Commands Time Tag Data Description Time Tag Data Description The time tag data starts at the end of the acquired data. Each data row has an 8-byte time tag for each chip (2-pod set). The starting location of the time tag data is immediately after the last row of valid data (maximum data byte + 1). If an analyzer is in a non-transitional mode, the master chip (byte 26) is the only chip with valid time-tag data.
DATA and SETup Commands Time Tag Data Description Byte (x + 8 ) through (x + 15) (64 bits starting with the MSB) - First sample tag for pods 5 and 6. Byte (x + 16 ) through (x + 23) (64 bits starting with the MSB) - Second sample tag for pods 5 and 6. . . . Byte (y) through (y+ 7) (64 bits starting with the MSB) - Last sample tag for pods 5 and 6. Byte (y + 8 ) through (y + 15) (64 bits starting with the MSB) - First sample tag for pods 7 and 8.
DATA and SETup Commands Glitch Data Description Glitch Data Description In the glitch mode, each pod has two bytes assigned to indicate where glitches occur in the acquired data. For each row of acquired data there will be a corresponding row of glitch data. The glitch data is organized in the same way as the acquired data. The glitch data is grouped in 18-byte rows for the 1660A. The number of rows is stored in byte positions 101 through 126.
DATA and SETup Commands SYSTem:SETup SYSTem:SETup Command :SYStem:SETup The SYStem:SETup command configures the logic analyzer module as defined by the block data sent by the controller. The length of the configuration data block can be up to 350,784 bytes in the 1660A. There are four data sections which are always returned.
DATA and SETup Commands SYSTem:SETup #8 The total length of all sections in byte format (must be represented with 8 digits)
DATA and SETup Commands RTC_INFO Section Description RTC_INFO Section Description The RTC_INFO section contains the real time of the acquired data. Because the time of the acquired data is important to certain measurements, this section describes how to find the real-time clock data. Because the number of sections in the SETup data block depends on the logic analyzer configuration, the RTC_INFO section will not always be in the same location within the block. Therefore, the section must be found by name.
26–18
Part 4 Oscilloscope Commands
27 Oscilloscope Root Level Commands
Introduction Oscilloscope Root Level commands control the basic operation of the oscilloscope. Refer to figure 27-1 for the module level syntax command diagram.
Oscilloscope Root Level Commands AUToscale Figure 27-1 Root Level Command Syntax Diagram AUToscale Command :AUToscale The AUToscale command causes the oscilloscope to automatically select the vertical sensitivity, vertical offset, trigger source, trigger level and timebase settings for optimum viewing of any input signals. The trigger source is the lowest channel on which the trigger was found. If no trigger is found, the oscilloscope defaults to auto-trigger.
Oscilloscope Root Level Commands AUToscale Example 10 20 25 30 40 50 60 70 OUTPUT XXX;":SELECT 2" OUTPUT XXX;":AUTOSCALE" WAIT 5 DIM Me$[200] OUTPUT ;":MEASURE:SOURCE CHANNEL1;ALL?" ENTER XXX;Me$ PRINT Me$ END The three Xs (XXX) after the OUTPUT and ENTER statements in the above example refer to the device address required for programming over either GPIB or RS-232-C. Refer to chapter 1, "Introduction to Programming" for information on initializing the interface.
Oscilloscope Root Level Commands DIGitize DIGitize Command :DIGitize The DIGitize command is used to acquire waveform data for transfer over GPIB. The command initiates the Repetitive Run for the oscilloscope and any modules that are grouped together in Group Run through the Intermodule Bus. If a RUNtil condition has been specified in any module, the oscilloscope and the grouped modules will acquire data until the RUNtil conditions have been satisfied.
27-6
28 ACQuire Subsystem
Introduction The Acquire Subsystem commands are used to set up acquisition conditions for the DIGitize command. The subsystem contains commands to select the type of acquisition and the number of averages to be taken if the average type is chosen. Refer to Figure 28-1 for the ACQuire Subsystem Syntax Diagram.
ACQuire Subsystem Figure 28-1 ACQuire Subsystem Syntax Diagram Table 28-1 ACQuire Parameter Values Parameter Value count_arg An integer that specifies the number of averages to be taken of each time point. The choices are 2, 4, 8, 16, 32, 64, 128, or 256. Acquisition Type Normal In the Normal mode, with the ACCumulate command OFF, the oscilloscope acquires waveform data and then displays the waveform.
ACQuire Subsystem COUNt COUNt Command :ACQuire:COUNt The COUNt command specifies the number of acquisitions for the running weighted average. This command generates an error if Normal acquisition mode is specified. {2|4|8|16|32|64|128|256} Example OUTPUT XXX;":ACQUIRE:COUNT 16" Query :ACQuire:COUNt? The COUNt query returns the last specified count.
ACQuire Subsystem TYPE Query :ACQuire:TYPE? The TYPE query returns the last specified type.
28-6
29 CHANnel Subsystem
Introduction The Channel Subsystem commands control the channel display and the vertical axis of the oscilloscope. Each channel must be programmed independently for all offset, range and probe functions. When ECL or TTL commands are executed, the vertical range, offset and trigger levels are automatically set for optimum viewing. Refer to figure 29-1 for the CHANnel Subsystem Syntax Diagram.
CHANnel Subsystem Figure29-1 CHANnel Subsystem Syntax Diagram 29-3
CHANnel Subsystem COUPling Table 29-1 CHANnel Parameter Values Parameter Value channel_number An integer from 1 to 2. offset_arg a real number defining the voltage at the center of the display. The offset range is as follows (for a 1:1 probe setting): Vertical Sensitivity Vertical Range Offset Voltage 4 mV - 100 mV/div 16 mV - 400 mV ±2 V >100 mV - 400 mV/div >400 mV - 1.6 V ±10 V >400 mV - 2.5 V/div >1.6 V - 10 V ±50 V >2.
CHANnel Subsystem ECL Query :CHANnel:COUPling? The COUPling query returns the current input impedance for the specified channel. Returned Format [:CHANnel:COUPling:] {DC|AC|DCFifty} Example OUTPUT XXX;":CHANNEL1:COUPLING?" ECL Command :CHANnel:ECL The ECL command sets the vertical range, offset, and trigger levels for the selected input channel for optimum viewing of ECL signals. The set ECL: values are: Range: 2.0 V (500 mV per division) Offset: -1.3 V Trigger level: -1.
CHANnel Subsystem OFFSet OFFSet Command :CHANnel:OFFSet The OFFSet command sets the voltage that is represented at center screen for the selected channel. The allowable offset voltage is shown in the table below. The table represents values for a Probe setting of 1:1. The offset value is recompensated whenever the probe attenuation factor is changed. An integer, from 1 to 2.. allowable offset voltage value shown in the table below.
CHANnel Subsystem PROBe PROBe Command :CHANnel:PROBe The PROBe command specifies the attenuation factor for an external probe connected to a channel. The command changes the channel voltage references such as range, offset, trigger level and automatic measurements. The actual sensitivity is not changed at the channel input. The allowable probe attenuation factor is an integer from 1 to 1000. An integer, from 1 to 2.
CHANnel Subsystem RANGe RANGe Command :CHANnel:RANGe The RANGe command defines the full-scale (4 * Volts/Div) vertical axis of the selected channel. The values for the RANGe command are dependent on the current probe attenuation factor for the selected channel. The allowable range for a probe attenuation factor of 1:1 is 16 mV to 40 V. For a larger probe attenuation factor, multiply the range limit by the probe attenuation factor. An integer, from 1 to 2.
CHANnel Subsystem TTL TTL Command :CHANnel:TTL The TTL command sets the vertical range, offset, and trigger level for the selected input channel for optimum viewing of TTL signals. The set TTL values are: Range: 6.0 V (1.50 V per division) Offset: 2.5 V Trigger Level: 1.62 V Example An integer, from 1 to 2. OUTPUT XXX;":CHANNEL1:TTL" To return to "Preset User" change the CHANnel:RANGe, CHANel:OFFSet, or TRIGger:LEVel value.
29-10
30 DISPlay Subsystem
Introduction The Display Subsystem is used to control the display of data. Refer to Figure 30-1 for the DISPlay Subsystem Syntax Diagram.
DISPlay Subsystem Figure 30-1 DISPlay Subsystem Syntax Diagram 30-3
DISPlay Subsystem ACCumulate Table 30-1 DISPlay Parameter Values Parameter Value slot_# a number from 1 or 2 identifying the oscilloscope/analyzer card slot. 1=analyzer, 2=oscilloscope. bit_id an integer from 0 to 31. channel_# an integer from 1 to 2. label_str up to five characters enclosed in single quotes making up a label name. label_id a string of 1 alpha and 1 numeric character for the oscilloscope, or 6 characters for the timing modules.
DISPlay Subsystem CONNect CONNect Command :DISPlay:CONNect {{ON|1}|{OFF|0}} The CONNect command sets the Connect Dots mode. When ON, each displayed sample dot will be connected to the adjacent dot by a straight line. The waveform is easier to see in this mode. When OFF, only the sampling points will be displayed. Example OUTPUT XXX;":DISPLAY:CONNECT ON" Query :DISPlay:CONNect? The CONNect query reports if connect is on or off.
DISPlay Subsystem INSert Always 2
DISPlay Subsystem LABel LABel Command :DISPlay:LABel CHANnel, The LABel command is used to assign a label string to an oscilloscope channel. For single channel traces, the label string (up to five characters) appears on the left of the waveform area of the display. Note that the label string cannot be used in place of the channel number when programming the oscilloscope module.
DISPlay Subsystem MINus MINus Command :DISPlay:MINus [,]
DISPlay Subsystem PLUS PLUS Command :DISPlay:PLUS [,]
DISPlay Subsystem REMove 30-10
31 MARKer Subsystem
Introduction In addition to automatic parametric measurements, the oscilloscope has four markers for making time and voltage measurement. These measurements may be made automatically or manually. Additional features include the centering of trigger or markers in the display area (CENTer) and the run until time (RUNTil) mode. The RUNTil mode allows you to set a stop condition based on the time interval between the X marker and the O marker.
MARKer Subsystem Figure 31-1 MARKer Subsystem Syntax Diagram 31-3
MARKer Subsystem Figure 31-1 MARKer Subsystem Syntax Diagram (Cont’d) 31-4
MARKer Subsystem Figure 31-1 MARKer Subsystem Syntax Diagram (Cont’d) Table 31-1 MARKer Parameter Values Parameter Value channel_# An integer from 1 to 2.
MARKer Subsystem AVOLt AVOLt Command :MARKer:AVOLt CHANnel, The AVOLt command moves the A marker to the specified voltage on the indicated channel. An integer from 1 to 2 the desired marker voltage level, ranging from ±(2 x maximum offset) Example OUTPUT XXX;":MARKER:AVOLT CHANNEL1,2.75" Query :MARKer:AVOLt? The AVOLt query returns the current voltage and channel selection for the A marker.
MARKer Subsystem ABVolt? ABVolt? Query :MARKer:ABVolt? The ABVolt query returns the difference between the A marker voltage and the B marker voltage (Vb - Va). Returned Format Example [:MARKer:ABVolt] level in volts of the B marker minus the A marker OUTPUT XXX;":MARKER:ABVOLT?" BVOLt Command :MARKer:BVOLt CHANnel, The BVOLt command moves the B marker to the specified voltage on the indicated channel.
MARKer Subsystem CENTer Query :MARKer:BVOLt? The BVOLt query returns the current voltage and channel selection for the B marker. Returned Format [:MARKer:BVOLt]CHANnel, Example OUTPUT XXX;":MARKER:BVOLT?" CENTer Command :MARKer:CENTer {TRIGger|X|O} The CENTer command allows you to position the indicated marker (TRIGger, X, or O) at the center of the waveform area on the scope display.
MARKer Subsystem OAUTo Query :MARKer:MSTats? The MSTats query returns the current setting. Returned Format [:MARKer:MSTats]{1|0} Example OUTPUT XXX;":MARKER:MSTATS?" OAUTo Command :MARKer:OAUTo{ MANual|CHANnel,,, ,} The OAUTo command specifies the automatic placement specification for the O marker. The first parameter specifies if automarker placement is to be in the manual mode or on a specified channel.
MARKer Subsystem OTIMe Query :MARKer:OAUTo? The OAUTo query returns the current settings. Returned Format [:MARKer:OAUTo] CHANnel, ,, Example OUTPUT XXX;":MARKER:OAUTO?" If is not specified, the marker type will default to PERCent. OTIMe Command :MARKer:OTIMe The OTIMe command moves the O marker to the specified time with respect to the trigger marker.
MARKer Subsystem RUNTil RUNTil Command :MARKer:RUNTil {OFF|LT,
MARKer Subsystem SHOW SHOW Command :MARKer:SHOW {SAMPle|MARKer} The SHOW command allows you to select either SAMPle rate or MARKer data (when markers are enabled) to appear on the oscilloscope menus above the waveform area. The SAMPle rate or MARKer data appears on the channel, trigger, display, and auto-measure menus. Marker data is always present on the marker menu. While sample rate data is only present on the marker menu when time markers are turned off.
MARKer Subsystem TMAXimum? TMAXimum? Query :MARKer:TMAXimum? The TMAXimum query returns the value of the maximum time between the X and O markers. If there is no valid data, the query returns 9.9E37. Returned Format
MARKer Subsystem TMODe TMODe Command :MARKer:TMODe {OFF|ON|AUTO} The TMODe command allows you to select the time marker mode. The choices are: OFF, ON and AUTO. When OFF, time marker measurements cannot be made. When the time markers are turned on, the X and O markers can be moved to make time and voltage measurements. The AUTO mode allows you to make automatic marker placements by specifying channel, slope, and occurrence count for each marker. Also the Statistics mode may be used when AUTO is chosen.
MARKer Subsystem VMODe VMODe Command :MARKer:VMODe {{OFF|0} | {ON|1}} The VMODe command allows you to select the voltage marker mode. The choices are: OFF or ON. When OFF, voltage marker measurements cannot be made. When the voltage markers are turned on, the A and B markers can be moved to make voltage measurements. When used in conjunction with the time markers (TMODe), both "delta t" and "delta v" measurements are possible.
MARKer Subsystem VOTime? VOTime? Query :MARKer:VOTime? CHANNEL The VOTime query returns the current voltage level of the selected source at the O marker. Returned Format Example [:MARKer:VOTime] An integer from 1 to 2 level in volts where the O marker crosses the waveform OUTPUT XXX;":MARKER:VOTIME? CHANNEL1" For compatibility with older modules, the OVOLt query will function the same as the VOTime query.
MARKer Subsystem VXTime? VXTime? Query :MARKer:XVOLt? CHANnel The VXTime query returns the current voltage level of the selected channel at the X marker. Returned Format Example [:MARKer:VXTime] An integer from 1 to 2 level in volts where the X marker crosses the waveform OUTPUT XXX;":MARKER:VXTIME? CHANNEL1" For compatibility with older modules, the XVOLt query will function the same as the VXTime query.
MARKer Subsystem XAUTo XAUTo Command :MARKer:XAUTo{MANual|CHANnel, ,,,} The XAUTo command specifies the automatic placement specification for the X marker. The first parameter specifies if automarker placement is to be in the Manual mode or on a specified channel. If a channel is specified, four other parameters must be included in the command syntax. The four parameters are: marker type, level, slope and the occurrence count.
MARKer Subsystem XOTime? XOTime? Query :MARKer:XOTime? The XOTime query returns the time in seconds from the X marker to the O marker. If data is not valid, the query returns 9.9E37. Returned Format
MARKer Subsystem XTIMe Query :MARKer:XTIMe? The XTIMe query returns the time in seconds between the X marker and the trigger marker.
32 MEASure Subsystem
Introduction The commands/queries in the Measure Subsystem are used to make automatic parametric measurements on displayed waveforms. Measurements are made on the displayed waveform(s) specified by the SOURce command. If the source is not specified, the last waveform source specified is assumed. Measurements are made in the following manner: Frequency The frequency of the first complete cycle displayed is measured using the 50% level.
MEASure Subsystem Preshoot and Overshoot Preshoot and overshoot measure the perturbation on a waveform above or below the top and base voltages. Preshoot Is a perturbation before a rising or a falling edge and measured as a percentage of the top-base voltage. Overshoot Is a perturbation after a rising or falling edge and is measured as a percentage of the top-base voltage. For complete details of the measurement algorithms, refer to the User’s Reference Manual.
MEASure Subsystem Figure 32-1 MEASure Subsystem Syntax Diagram Table 32-1 MEASure Parameter Values Parameter Value channel_# An integer from 1 to 2 32-4
MEASure Subsystem ALL? ALL? Query :MEASure:[SOURce CHANnel;]ALL? The ALL query makes a set of measurements on the displayed waveform using the selected source.
MEASure Subsystem FALLtime? FALLtime? Query :MEASure:[SOURce CHANnel;]FALLtime? The FALLtime query makes a fall time measurement on the selected channel. The measurement is made between the 90% to the 10% voltage point of the first falling edge displayed on screen.
MEASure Subsystem NWIDth? NWIDth? Query :MEASure:[SOURce CHANnel;]NWIDth? The NWIDth query makes a negative width time measurement on the selected channel. The measurement is made between the 50% points of the first falling and the next rising edge displayed on screen.
MEASure Subsystem PERiod? PERiod? Query :MEASure:[SOURce CHANnel;]PERiod? The PERiod query makes a period measurement on the selected channel. The measurement is equivalent to the inverse of the frequency. Returned Format Example [:MEASure:PERiod] An integer from 1 to 2 waveform period in seconds OUTPUT XXX;":MEASURE:SOURCE CHANNEL1;PERIOD?" PREShoot? Query :MEASure:[SOURce CHANnel;]PREShoot? The PREShoot query makes the preshoot measurement on the selected channel.
MEASure Subsystem PWIDth? PWIDth? Query :MEASure:[SOURce CHANnel;]PWIDth? The PWIDth query makes a positive pulse width measurement on the selected channel. The measurement is made by finding the time difference between the 50% points of the first rising and the next falling edge displayed on screen.
MEASure Subsystem SOURce SOURce Command :MEASure:SOURce CHANnel The SOURce command specifies the source to be used for subsequent measurements. If the source is not specified, the last waveform source is assumed. An integer from 1 to 2 Example OUTPUT XXX;":MEASURE:SOURCE CHAN1" Query :MEASure:SOURce? The SOURce query returns the presently specified channel.
MEASure Subsystem VAMPlitude? VAMPlitude? Query :MEASure:[SOURce CHANnel;]VAMPlitude? The VAMPlitude query makes a voltage measurement on the selected channel. The measurement is made by finding the relative maximum (VTOP) and minimum (VBASe) points on screen.
MEASure Subsystem VMAX? VMAX? Query :MEASure:[SOURce CHANnel;]VMAX? The VMAX query returns the absolute maximum voltage of the selected source. Returned Format Example [:MEASure:VMAX] An integer from 1 to 2 maximum voltage of selected waveform OUTPUT XXX;":MEASURE:SOURCE CHAN2;VMAX?" VMIN? Query :MEASure:[SOURce CHANnel;]VMIN? The VMIN query returns the absolute minimum voltage present on the selected source.
MEASure Subsystem VPP? VPP? Query :MEASure:[SOURce CHANnel;]VPP? The VPP query makes a peak to peak voltage measurement on the selected source. The measurement is made by finding the absolute maximum (VMAX) and minimum (VMIN) points on the displayed waveform.
32-14
33 TIMebase Subsystem
Introduction The commands of the Timebase Subsystem control the Timebase, Trigger Delay Time, and the Timebase Mode. If TRIGgered mode is to be used, ensure that the trigger specifications of the Trigger Subsystem have been set. Refer to Figure 33-1 for the TIMebase Subsystem Syntax Diagram.
TIMebase Subsystem Figure 33-1 TIMebase Subsystem Syntax Diagram Table 33-1 TIMebase Parameter Values Parameter Value delay_arg delay time in seconds, from -2500 seconds through +2500 seconds. The full range is available for panning the waveform when acquisition is stopped. Refer to the User’s Reference Manual for a list of the available Delay Pre-trigger and Delay Post-trigger ranges while running and making acquisitions.
TIMebase Subsystem DELay DELay Command :TIMebase:DELay The DELay command sets the time between the trigger and the center of the screen. delay time in seconds, from -2500 seconds through +2500 seconds. The full range is available for panning the waveform when acquisition is stopped. Refer to the Oscilloscopes User’s Reference manual for a list of the available Delay Pre-trigger and Delay Post-trigger ranges while running and making acquisitions.
TIMebase Subsystem MODE MODE Command :TIMebase:MODE {TRIGgered|AUTO} The MODE command sets the oscilloscope timebase to either Auto or Triggered mode. When the AUTO mode is chosen, the oscilloscope waits approximately 50 ms for a trigger to occur. If a trigger is not generated within that time, then auto trigger is executed. If a signal is not applied to the input, a baseline is displayed.
TIMebase Subsystem RANGe RANGe Command :TIMebase:RANGe The RANGe command sets the full-scale horizontal time in seconds. The RANGE value is ten times the value in the s/Div field. time in seconds Example OUTPUT XXX;":TIMEBASE:RANGE 2US" Query :TIMebase:RANGe? The RANGe query returns the current setting.
34 TRIGger Subsystem
Introduction The commands of the Trigger Subsystem allow you to set all the trigger conditions necessary for generating a trigger. Many of the commands in the Trigger subsystem may be used in either the EDGE or the PATTern trigger mode. If a command is a valid command for the chosen trigger mode, then that setting will be accepted by the oscilloscope. However, if the command is not valid for the trigger mode, an error will be generated.
TRIGger Subsystem Figure 34-1 TRIGger Subsystem Syntax Diagram 34-3
TRIGger Subsystem figure 34-1 TRIGger Subsystem Syntax Diagram (Cont’d) Table 34-1 TRIGger Parameter Values Parameter Value channel_# An integer from 1 to 2 count_# an integer from 1 through 32000 time a real number from 20 ns through 160 ms 34-4
TRIGger Subsystem CONDition CONDition Command :TRIGger:[MODE PATTern;]CONDition {ENTer|EXIT|GT,
TRIGger Subsystem CONDition When LT (less than) is selected, the oscilloscope will trigger on the first transition that causes the pattern specification to be false, after the pattern has been true for the number of times specified by the trigger event count (DELAY command). The first event in the sequence will occur when the specified pattern is true for a time less than that indicated by the trigger specification.
TRIGger Subsystem DELay DELay Command :TRIGger:DELay [EVENt,] The DELay command is used to specify the number of events at which trigger occurs. The time delay (see TIMe:DELay) is counted after the events delay. The DELay command cannot be used in the IMMediate trigger mode. integer from 1 to 32000 Example OUTPUT XXX;":TRIGGER:DELAY 5" Query :TRIGger:DELay? The DELay query returns the current trigger events count.
TRIGger Subsystem LEVel LEVel Command For EDGE trigger mode: :TRIGger:[MODE EDGE;SOURce {CHANnel;]LEVel For PATTern trigger mode: :TRIGger:[MODE PATTern;PATH {CHANnel};]LEVel The LEVel command sets the trigger level voltage for the selected source or path. This command cannot be used in the IMMediate trigger mode. In EDGE trigger mode, the SOURce command is used; in PATTern mode, the trigger PATH is used for the trigger level source.
TRIGger Subsystem LEVel Query For EDGE trigger mode: :TRIGger:[MODE EDGE;SOURce {CHANnel};]LEVel? For PATTern trigger mode: :TRIGger:[MODE PATTern;PATH {CHANnel};]LEVel? The LEVel query returns the trigger level for the current path or source.
TRIGger Subsystem LOGic LOGic Command :TRIGger:[MODE PATTern;PATH {CHANnel};] LOGic {HIGH|LOW|DONTcare} The LOGic command sets the logic for each trigger path in the PATTern trigger mode. The choices are HIGH, LOW and DONTcare. The trigger level set by the LEVel command determines logic high and low threshold levels.
TRIGger Subsystem MODE MODE Command :TRIGger:MODE {EDGE|PATTern|IMMediate} The MODE command allows you to select the trigger mode for the oscilloscope. The EDGE mode will trigger the oscilloscope on an edge whose slope is determined by the SLOPe command at a voltage set by the LEVel command. The PATTern mode will trigger the oscilloscope on entering or exiting a specified pattern of the two internal channels and external trigger.
TRIGger Subsystem PATH PATH Command :TRIGger:[MODE PATTern;]PATH {CHANnel} The PATH command is used to select a trigger path for the subsequent LOGic and LEVel commands. This command can only be used in the PATTern trigger mode. An integer from 1 or 2 Example OUTPUT XXX;":TRIGGER:PATH CHANNEL1" Query :TRIGger:PATH? The PATH query returns the current trigger path.
TRIGger Subsystem SOURce Query :TRIGger:SLOPe? The SLOPe query returns the slope of the current trigger source. Returned Format [:TRIGger:SLOPe] {POSitive|NEGative} Example OUTPUT XXX;":TRIG:SOUR CHAN1;SLOP?" SOURce Command :TRIGger:[MODE EDGE;]SOURce {CHANnel} The SOURce command is used to select the trigger source and is used for any subsequent SLOPe and LEVel commands. This command can only be used in the EDGE trigger mode.
34-14
35 WAVeform Subsystem
Introduction The commands of the Waveform subsystem are used to transfer waveform data from the oscilloscope to a controller. The waveform record is actually contained in two portions; the waveform data and preamble. The waveform data is the actual data acquired for each point when a DIGitize command is executed. The preamble contains the information for interpreting waveform data. Data in the preamble includes number of points acquired, format of acquired data, average count and the type of acquired data.
WAVeform Subsystem Average Mode In the Average mode, the oscilloscope averages the data points on the waveform with previously acquired data. Averaging helps eliminate random noise from the displayed waveform. In this mode ACCumulate is set to OFF. When Average mode is selected the number of averages must also be specified using the COUNt command. Previously displayed waveform data is erased from the display and the newly averaged waveform is displayed.
WAVeform Subsystem Format for Data Transfer Format for Data Transfer There are three formats for transferring waveform data over the remote interface. These formats are WORD, BYTE, or ASCII. WORD and BYTE formatted waveform records are transmitted using the arbitrary block program data format specified in IEEE-488.2. When you use this format, the ASCII character string "#8 " is sent before the actual data. The ’s are eight ASCII numbers which indicate how many data bytes will follow.
WAVeform Subsystem Format for Data Transfer WORD Format Word data is two bytes wide with the most significant byte of each word being transmitted first. In WORD format, the 15 least significant bits represent the waveform data. The possible range of data is divided into 32768 vertical increments. The WORD data structure for normal and average acquisition types are shown in figure 35-2. If all "1’s are returned in the 15 least significant bits, the waveform is clipped at the top of the screen.
WAVeform Subsystem Data Conversion Data Conversion Data sent from the oscilloscope is raw data and must be scaled for useful interpretation. The values used to interpret the data are the X and Y references, X and Y origins, and X and Y increments. These values are read from the waveform preamble (see the PREamble command) or by the queries of these values.
WAVeform Subsystem Data Conversion Figure 35-3 WAVeform Subsystem Syntax Diagram 35-7
WAVeform Subsystem Data Conversion Figure 35-3 WAVeform Subsystem Syntax Diagram (Cont’d) Table 35-1 WAVeform Parameter Values Parameter Value channel_# an integer from 1 to 2 35-8
WAVeform Subsystem COUNt? COUNt? Query :WAVeform:COUNt? The COUNt query returns the count last specified in the ACQuire Subsystem. Returned Format Example [:WAVeform:COUNt] {2|4|8|16|32|64|128|256} OUTPUT XXX;":WAVEFORM:COUNT?" DATA? Query :WAVeform:[SOURce CHANnel;]DATA? The DATA query returns the waveform record stored in a specified channel buffer. The WAVeform:SOURce command is used to select the specified channel.
WAVeform Subsystem FORMat FORMat Command :WAVeform:FORMat {BYTE|WORD|ASCii} The FORMat command specifies the data transmission mode of waveform data over the remote interface. Example OUTPUT XXX;":WAV:FORM WORD" Query :WAVeform:FORMat?" The FORMat query returns the currently specified format.
WAVeform Subsystem PREamble? PREamble? Query :WAVeform[:SOURce CHANnel;]PREamble? The PREamble query returns the preamble of the specified channel. The channel is specified using the SOURCE command.
WAVeform Subsystem RECord RECord Command :WAVeform:RECord {FULL|WINDow} The RECord command specifies the data you want to receive over the bus. The choices are FULL or WINdow. When FULL is chosen, the entire 8000 point record of the specified channel is transmitted over the bus. In WINdow mode, only the data displayed on screen will be returned. Example OUTPUT XXX;":WAV:SOUR CHAN1;REC FULL" Query :WAVeform:RECord? The RECord query returns the present mode chosen.
WAVeform Subsystem SPERiod? Query :WAVeform:SOURce? The SOURce query returns the presently selected channel. Returned Format [:WAVeform:SOURce] CHANnel Example OUTPUT XXX;":WAVEFORM:SOURCE?" SPERiod? Query :WAVeform:SPERiod? The SPERiod query returns the present sampling period. The sample period is determined by the DELay and the RANGe commands of the TIMEbase subsystem.
WAVeform Subsystem VALid? VALid? Query :WAVeform:VALid? The VALid query checks the oscilloscope for acquired data. If a measurement is completed, and data has been acquired by all channels, then the query reports a 1. A 0 is reported if no data has been acquired for the last acquisition.
WAVeform Subsystem XINCrement? XINCrement? Query :WAVeform:XINCrement? The XINCrement query returns the X-increment currently in the preamble. This value is the time difference between the consecutive data points. X-increment is determined by the RECord mode as follows: • In FULL record mode, the X-increment equals the time period between data samples (or sample period). • In WINDow record mode, the X-increment is the time between data points on the logic analyzer front panel.
WAVeform Subsystem XORigin? XORigin? Query :WAVeform:[SOURce CHANnel;]XORigin? The XORigin query returns the X-origin value currently in the preamble. The value represents the time of the first data point in memory with respect to the trigger point.
WAVeform Subsystem YINCrement? YINCrement? Query :WAVeform:[SOURce CHANnel;]YINCrement? The YINCrement query returns the Y-increment value currently in the preamble. This value is the voltage difference between consecutive data values.
WAVeform Subsystem YREFerence? YREFerence? Query :WAVeform:YREFerence? The YREFerence query returns the Y-reference value currently in the preamble. This value specifies the data value at center screen where Y-origin occurs.
Part 5 Programming Examples
36 Programming Examples
Introduction This chapter contains short, usable, and tested program examples that cover the most asked for examples. The examples are written in HP Basic 6.0.
Programming Examples Making a Timing analyzer measurement Making a Timing analyzer measurement This program sets up the logic analyzer to make a simple timing analyzer measurement. This example can be used with E2433-60004 Logic Analyzer Training board to acquire and display the output of the ripple counter. It can also be modified to make any timing analyzer measurement.
Programming Examples Making a Timing analyzer measurement 350 360 370 380 390 400 410 420 430 440 450 460 470 480 490 500 510 520 530 540 550 560 570 580 590 600 610 620 630 640 650 660 670 680 690 700 710 720 730 740 750 760 770 ! OUTPUT 707;":MACH1:TWAVEFORM:REMOVE" OUTPUT 707;":MACH1:TWAVEFORM:INSERT ’COUNT’, ALL" OUTPUT 707;":MACH1:TWAVEFORM:RANGE 1E-6" OUTPUT 707;":MENU 1,5" ! ! **************************************************************** ! Run the timing analyzer in single mode.
Programming Examples Making a State analyzer measurement Making a State analyzer measurement This state analyzer program selects the 1660-series logic analyzer, displays the configuration menu, defines a state machine, displays the state trigger menu, sets a state trigger for multilevel triggering. This program then starts a single acquisition measurement while checking for measurement completion. This program is written in such a way you can run it with the E2433-60004 Logic Analyzer Training Board.
Programming Examples Making a State analyzer measurement 310 320 330 340 350 360 370 380 390 400 410 420 430 440 450 460 470 480 490 500 510 520 530 540 550 560 570 580 590 600 610 620 630 640 650 660 670 680 690 700 710 720 730 740 750 ! ! Display the state trigger menu. ! OUTPUT 707;":MENU 1,3" ! ! Create a 5 level trigger specification with the trigger on the ! fourth level.
Programming Examples Making a State analyzer measurement 760 770 780 790 800 810 820 830 840 850 860 870 880 890 900 910 920 930 940 950 960 970 980 990 1000 1010 1020 1030 1040 1050 1060 1070 1080 1090 1100 1110 1120 1130 1140 1150 1160 1170 1180 1190 1200 OUTPUT 707;":MACHINE1:STRIGGER:STORE4 ’(C OR D OR IN_RANGE1)’" ! ! ************************ NOTE *********************** ! The FIND command selects the trigger in the ! sequence level specified as the trigger level.
Programming Examples Making a State analyzer measurement 1210 1220 1230 1240 1250 1260 1270 1280 1290 1300 ! ************************ VIEW THE RESULTS ***************************** ! Display the State Listing and select a line number in the listing that ! allows you to see the beginning of the listing on the logic analyer ! display.
Programming Examples Making a State Compare measurement Making a State Compare measurement This program example acquires a state listing, copies the listing to the compare listing, acquires another state listing, and compares both listings to find differences. This program is written in such a way you can run it with the E2433-60004 Logic Analyzer Training Board. This example is the same as the "State Compare" example in chapter 3 of the E2433-90910 Logic Analyzer Training Guide.
Programming Examples Making a State Compare measurement 330 340 350 360 370 380 390 400 410 420 430 440 450 460 470 480 490 500 510 520 530 540 550 560 570 580 590 600 610 620 630 640 650 660 670 680 690 700 710 720 730 740 750 760 770 ! FF hex for the "a" term which will be the trigger term, and store ! no states until the trigger is found.
Programming Examples Making a State Compare measurement 780 ! 790 ! Line 4090 of the listing is now displayed at center screen 800 ! in order to show the last four states acquired. In this 810 ! example, the last four states are stable. However, in some 820 ! cases, the end points of the listing may vary thus causing 830 ! a false failure in compare. To eliminate this problem, a 840 ! partial compare can be specified to provide predicable end 850 ! points of the data.
Programming Examples Making a State Compare measurement 1210 1220 1230 1240 1250 1260 1270 1280 1290 1300 1310 1320 1330 1340 1350 1360 1370 1380 1390 1400 1410 1420 1430 1440 1450 1460 1470 1480 1490 1500 1510 1520 1530 1540 1550 1560 1570 1580 1590 1600 1610 1620 1630 1640 1650 ! enters the line numbers and error numbers. ! DIM Line$[20] DIM Error$[4] DIM Comma$[1] ! ! *********************************************************************** ! Display the Difference listing.
Programming Examples Making a State Compare measurement 1660 1670 1680 1690 1700 1710 1720 1730 1740 1750 1760 1770 1780 1790 1800 1810 1820 1830 1840 1850 Error_line=IVAL(Line$,10) IF Error_line=Error_line2 THEN GOTO 1780 Error_line2=Error_line ! ! ************************************************************************ ! Print the error numbers and the corresponding line numbers on the ! controller screen.
Programming Examples Transferring the logic analyzer configuration Transferring the logic analyzer configuration This program uses the SYSTem:SETup query to transfer the configuration of the logic analyzer to your controller. This program also uses the SYSTem:SETup command to transfer a logic analyzer configuration from the controller back to the logic analyzer. The configuration data will set up the logic analyzer according to the data.
Programming Examples Transferring the logic analyzer configuration 280 290 300 310 320 330 340 350 360 370 380 390 400 410 420 430 440 450 460 470 480 490 500 510 520 530 540 550 560 570 580 600 610 620 630 640 650 660 670 680 690 700 710 720 730 OUTPUT 707;":SYSTEM:HEADER ON" OUTPUT 707;":SYSTEM:LONGFORM ON" OUTPUT @Comm;"SELECT 1" OUTPUT @Comm;":SYSTEM:SETUP?" ! ! ******************** ENTER THE BLOCK SETUP HEADER ********************* ! Enter the block setup header in the proper format.
Programming Examples Transferring the logic analyzer configuration 740 750 760 770 780 790 800 810 820 830 840 850 860 870 880 890 900 910 920 930 940 950 960 970 980 990 1000 1010 1020 1030 1040 1050 1060 1070 1080 1090 1100 1110 1120 1130 1140 1150 1160 1170 ! ********************* SEND THE SETUP COMMAND ************************** ! Send the Setup command ! OUTPUT @Comm USING "#,15A";":SYSTEM:SETUP #" PRINT "SYSTEM:SETUP command has been sent" PAUSE ! ! ********************* SEND THE BLOCK SETUP *******
Programming Examples Transferring the logic analyzer acquired data Transferring the logic analyzer acquired data This program uses the SYSTem:DATA query to transfer acquired data to your controller. It is useful for getting acquired data for setting up the logic analyzer by the controller at a later time. This query differs from the SYSTem:SETup query because it transfers only the acquired data.
Programming Examples Transferring the logic analyzer acquired data 200 210 220 230 240 250 260 270 280 290 300 310 320 330 340 350 360 370 380 390 400 410 420 430 440 450 460 470 480 490 500 510 520 530 540 550 560 570 580 600 610 620 630 640 650 Numbytes=0 ! ! ************** RE-INITIALIZE TRANSFER BUFFER POINTERS ****************** ! CONTROL @Buff,3;1 CONTROL @Buff,4;0 ! ! *********************** SEND THE DATA QUERY ************************** OUTPUT 707;":SYSTEM:HEADER ON" OUTPUT 707;":SYSTEM:LONGFORM ON
Programming Examples Transferring the logic analyzer acquired data 660 670 680 690 700 710 720 730 740 750 760 770 780 790 800 810 820 830 840 850 860 870 880 890 900 910 920 930 940 950 960 970 980 990 1000 1010 1020 1030 1040 1050 1060 1070 1080 1090 1100 ! ********************* SEND THE DATA ********************************** ! Make sure buffer is not empty.
Programming Examples Transferring the logic analyzer acquired data 1110 1120 1130 1140 1150 1160 1170 ! ******************** SEND TERMINATING LINE FEED ********************** ! Send the terminating linefeed to properly terminate the data string.
Programming Examples Checking for measurement completion Checking for measurement completion This program can be appended to or inserted into another program when you need to know when a measurement is complete. If it is at the end of a program it will tell you when measurement is complete. If you insert it into a program, it will halt the program until the current measurement is complete.
Programming Examples Sending queries to the logic analyzer Sending queries to the logic analyzer This program example contains the steps required to send a query to the logic analyzer. Sending the query alone only puts the requested information in an output buffer of the logic analyzer. You must follow the query with an ENTER statement to transfer the query response to the controller. When the query response is sent to the logic analyzer, the query is properly terminated in the logic analyer.
Programming Examples Sending queries to the logic analyzer 310 320 330 340 350 360 370 380 390 400 410 420 430 440 450 ! Send the query. In this example the MENU? query is sent. All ! queries except the SYSTem:DATA and SYSTem:SETup can be sent with ! this program. ! OUTPUT 707;"MENU?" ! ! **************************************************************** ! The two lines that follow transfer the query response from the ! query buffer to the controller and then print the response.
Programming Examples Getting ASCII Data with PRINt? ALL Query Getting ASCII Data with PRINt? ALL Query This program example shows you how to get ASCII data from a state listing using the PRINt? ALL query. There are two things you must keep in mind: • You must select the logic analyzer, which is always SELECT 1 for the 1660-series logic analyzers. • You must select the proper menu. The only menus that allow you to use the PRINt? ALL query are the listing menus and the disk menu.
Programming Examples Reading the disk with the CATalog? ALL query Reading the disk with the CATalog? ALL query The following example program reads the catalog of the disk currently in the logic analyzer disk drive. The CATALOG? ALL query returns the entire 70-character field. Because DOS directory entries are 70 characters long, you should use the CATALOG? ALL query with DOS disks.
Programming Examples Reading the Disk with the CATalog? Query Reading the Disk with the CATalog? Query This example program uses the CATALOG? query without the ALL option to read the catalog of the disk currently in the logic analyzer disk drive. However, if you do not use the ALL option, the query only returns a 51-character field. Keep in mind if you use this program with a DOS disk, each filename entry will be truncated at 51 characters.
Programming Examples Printing to the disk Printing to the disk This program prints acquired data to a disk file. The file can be either on a LIF or DOS disk. If you print the file to a DOS disk, you will be able to view the file on a DOS compatible computer using any number of file utility programs.
Programming Examples Transferring waveform data in Byte format Transferring waveform data in Byte format This program sets up the oscilloscope module to move oscilloscope waveform data from the 1660-series to a controller in Byte format.
Programming Examples Transferring waveform data in Byte format 390 400 410 420 430 440 450 460 470 490 500 510 ENTER 707 USING "#,B";Waveform(*) ENTER 707 USING "#,B";Lastchar ! !*************** Print the waveform data *********************** PRINT "Header = ";Header$ PRINT PRINT "Press CONTINUE to display waveform data" PRINT PRINT Waveform(*) PRINT PRINT Lastchar END 36–29
Programming Examples Transferring waveform data in Word format Transferring waveform data in Word format This program sets up the oscilloscope module to move oscilloscope waveform data from the 1660-series to a controller in Word format.
Programming Examples Transferring waveform data in Word format 390 400 410 420 430 440 450 460 470 480 490 500 510 ENTER 707 USING "#,B";Waveform(*) ENTER 707 USING "#,B";Lastchar ! ! *************** Print the waveform data *********************** PRINT "Header = ";Header$ PRINT PRINT "Press CONTINUE to display waveform data" PRINT PAUSE PRINT Waveform(*) PRINT PRINT Lastchar END 36–31
Programming Examples Using AUToscale and the MEASure:ALL? Query Using AUToscale and the MEASure:ALL? Query This very simple program example shows how to use Autoscale to acquire a waveform and the MEASure:ALL? query to read in the measurement results.
Programming Examples Using Sub-routines in a measurement program Using Sub-routines in a measurement program This program example shows a measurement example using sub-routines in HP BASIC. The tasks perfumed in this example are: • Initializing the interface and the oscilloscope • Digitizing the acquired signal data • Measuring and printing the frequency and peak-to-peak voltage of the acquired signal.
Programming Examples Using Sub-routines in a measurement program 320 330 340 350 360 370 380 390 400 410 420 430 440 450 460 470 480 490 500 510 520 530 540 550 560 570 580 590 CLEAR @Isc !clear GPIB interface OUTPUT @Scope;":SELECT 2" !select the oscilloscope OUTPUT @Scope;"*RST" !set oscilloscope to default config OUTPUT @Scope;":AUTOSCALE" !AUTOSCALE OUTPUT @Scope;":SYST:HEADER OFF" !turn headers off CLEAR SCREEN !clear screen RETURN ! !DIGITIZE waveform to acquire data and stop oscilloscope for furthe
Index ! *CLS command, 8–5 *ESE command, 8–6 *ESR command, 8–7 *IDN command, 8–9 *IST command, 8–9 *OPC command, 8–11 *OPT command, 8–12 *PRE command, 8–13 *RST command, 8–14 *SRE command, 8–15 *STB command, 8–16 *TRG command, 8–17 *TST command, 8–18 *WAI command, 8–19 ..., 4–5 32767, 4–4 9.
Index REMove, 14–10, 15–13, 17–15, 18–9, 21–7,Command errors, 7–3 DSP, 10–6 Command mode, 2–3 23–16, 24–14, 25–7, 30–9 EOI, 9–11 Command set organization, 4–14 REName, 11–18, 13–8 FIND, 16–13, 22–13 Command structure, 1–4 RESource, 13–9 FORMat, 35–10 Command tree, 4–5 RMODe, 9–18 GLEDge, 22–14 RUNTil, 17–15, 20–12, 23–17, 24–15, 31–11 SELect, 9–21 HAXis, 19–5 Command types, 4–6 SCHart, 19–4 HEADer, 1–16, 10–8 Commands SELect, 9–20 INITialize, 11–13 ACCumulate, 30–4 SEQuence, 16–16, 22–17 INPort, 12–6 AUTos
Index ESB, 6–4 Data mode, 2–3 Event Status Register, 6–4 Data preamble, 26–6, 26–7, 26–8, 26–9 Example DATA query, 17–9, 24–9 Using AUToscale, 27–4 Data Terminal Equipment, 3–3 Examples Data Terminal Ready(DTR), 3–5 program, 36–2 data to time conversion, 35–6 EXE, 6–5 data transfer, 35–2, 35–12 Execution errors, 7–4 data transfer format, 35–4, 35–5 Exponents, 1–12 data transmission mode, 35–10 data value to trigger point conversion, 35–6 Extended interface, 3–4 DATA?, 35–9 DataCommunications Equipment, 3–3
Index Identification number, 9–8 Identifying modules, 9–8 IEEE 488.1, 2–2, 5–2 IEEE 488.1 bus commands, 2–6 IEEE 488.
Index None, 3–9 POINts, 35–10 XON/XOFF, 3–9 points on screen, 35–10 Protocol exceptions, 5–5 POINts?, 35–10 Protocols, 5–3 PON, 6–5 PURGe command, 11–17 positive pulse width measurement, 32–9 PWIDth, 32–9 preamble, 35–2, 35–11 PWIDth?, 32–9 Preamble description, 26–6 PREamble?, 35–11 preset user, 29–5, 29–9 Q PREShoot, 32–8 Query, 1–6, 1–10, 1–16 preshoot measurement, 32–8 *ESE, 8–6 PREShoot?, 32–8 *ESR, 8–7 PRINt command, 10–10 *IDN, 8–9 Printer mode, 2–3 *IST, 8–9 Printing to the disk, 36–27 *OPC, 8–11 P
Index SYSTem:DATA, 10–6, 26–5 DATA, 10–6, 17–9, 20–8, 24–9, 26–5, 35–9 OSEarch, 17–12, 23–14, 24–13 SYStem:SETup, 10–12, 26–16 OSTate, 14–8, 17–13, 24–13 DATA?, 35–9 TAG, 16–18 OTAG, 17–14, 24–14 DELay, 14–5, 18–7, 23–10, 33–4, 34–7 TAKenbranch, 16–19, 18–10 OTIMe, 14–9, 23–15, 31–10 DELay?, 33–4, 34–7 TAVerage, 17–17, 23–19, 24–16, 31–12 OTIMe?, 31–10 EOI, 9–11 TAVerage?, 31–12 OVERshoot, 32–7 ERRor, 10–7 TCONtrol, 16–20, 22–19 OVERshoot?, 32–7 FALLtime, 32–6 TERM, 16–22, 22–21 OVOLt, 31–7, 31–16 FALLtime
Index 31–19 XOTime?, 31–19 XPATtern, 17–20, 23–23, 24–20 Xreference, 35–16 XREFerence?, 35–16 XSEarch, 17–21, 23–24, 24–21 XSTate, 14–11, 17–22, 24–21 XTAG, 17–23, 24–22 XTIMe, 14–12, 23–25 XTIMe?, 31–20 XVOLt, 31–17 YINCrement, 35–17 YINCrement?, 35–17 YORigin, 35–17 YORigin?, 35–17 YREFerence, 35–18 YREFerence?, 35–18 Query errors, 7–5 query program example, 36–22 Query responses, 1–15, 4–4 Question mark, 1–10 QYE, 6–5 R RANGe, 29–8, 33–6 RANGe command, 25–6 RANGe command/query, 14–9, 16–14, 16–15, 18–8,
Index SYSTem:SETup command pro35–6, 35–7, 35–8, 35–9, 35–10, 35–11, INTermodule, 12–2 gram example, 36–14 35–12, 35–13, 35–14, 35–15, 35–16, 35–17, MACHine, 13–2 SYSTem:SETup query program MARKer, 31–1, 31–2, 31–3, 31–4, 31–5, 35–18 example, 36–14 WLISt, 14–1, 14–3, 14–4, 14–5, 14–6, 14–7, 31–6, 31–7, 31–8, 31–9, 31–10, 31–11, 31–12, 31–13, 31–14, 31–15, 31–16, 31–17, 14–8, 14–9, 14–10, 14–11, 14–12 Subsystem commands, 4–6 31–18, 31–19, 31–20 T subtracting waveforms, 30–8 MEASure, 32–1, 32–2, 32–3, 32–4, 3
Index transferring waveform data program example, 36–28, 36–30 Transmit Data (TD), 3–4, 3–5 TREE command, 12–9 trigger count:See trigger , 34–2 trigger delay, 33–4, 34–2, 34–7 trigger level voltage, 34–8 trigger logic, 34–10 trigger mode, 34–11 trigger path, 34–12 trigger slope, 34–12 trigger source, 34–13 TRIGger Subsystem, 34–2 triggered timebase mode, 33–5 Truncation rule, 4–3 TTIMe query, 12–10 TTL, 29–9 TTRigger , 22–8 TTRigger/TTRace Subsystem, 22–1, 22–3, 22–4, 22–5, 22–6, 22–7, 22–8, 22–9, 22–10, 2
Index–10
© Copyright Agilent Technologies 1992-2000 All Rights Reserved. Reproduction, adaptation, or translation without prior written permission is prohibited, except as allowed under the copyright laws. Restricted Rights Legend Use, duplication, or disclosure by the U.S. Government is subject to restrictions set forth in subparagraph (C) (1) (ii) of the Rights in Technical Data and Computer Software Clause in DFARS 252.227-7013. Agilent Technologies, 3000 Hanover Street, Palo Alto, CA 94304 U.S.A.
Product Warranty This Agilent Technologies product has a warranty against defects in material and workmanship for a period of one year from date of shipment. During the warranty period, Agilent Technologies will, at its option, either repair or replace products that prove to be defective. For warranty service or repair, this product must be returned to a service facility designated by Agilent Technologies.
