Page 2 - ii
Page 3 - In This Book; iii
In This Book This programmer’s guide contains generalinformation, instrument level commands,logic analyzer commands, oscilloscopemodule commands, pattern generatormodule commands, and programmingexamples for programming the AgilentTechnologies 1670G-series logicanalyzers. This guide focuses on how t...
Page 4 - Part 1; Part 1, consists of chapters 1 through 7 and contains general
Part 1 Part 1, consists of chapters 1 through 7 and contains general information about programming basics, GPIB and RS-232-C interfacerequirements, documentation conventions, status reporting, and errormessages. If you are already familiar with IEEE 488.2 programming and GPIB orRS-232-C, you may wan...
Page 6 - Part 6, chapter 43, contains program examples of actual tasks
Part 6 Part 6, chapter 43, contains program examples of actual tasks that show you how to get started in programming the Agilent1670G-series logic analyzers. The complexity of your programs and thetasks they accomplish are limited only by your imagination. Theseexamples are written in HP Basic 6.2; ...
Page 7 - vii
MEASure Subsystem 33 TIMebase Subsystem 34 MARKer Subsystem 32 DISPlay Subsystem 31 TRIGger Subsystem 35 WAVeform Subsystems 36 Programming the Pattern Generator 37 FORMat Subsystem 38 SEQuence Subsystem 39 MACRo Subsystem 40 SYMBol Subsystem 41 DATA and SETup Commands 42 Programming Examples 43 Ind...
Page 8 - viii
Page 9 - Table of Contents; Part 1 General Information; Talking to the Instrument 1–3; Programming Over GPIB; Contents–1
Table of Contents Part 1 General Information 1 Introduction to Programming the Agilent Technologies 1670G- Series Logic Analyzer Talking to the Instrument 1–3 Initialization 1–4Instruction Syntax 1–5Output Command 1–5Device Address 1–6Instructions 1–6Instruction Terminator 1–7Header Types 1–8Duplica...
Page 10 - Bus Commands 2–6; Programming and Documentation Conventions; Contents; Contents–2
Bus Commands 2–6 3 Programming Over RS-232-C Interface Operation 3–3RS-232-C Cables 3–3Minimum Three-Wire Interface with Software Protocol 3–4Extended Interface with Hardware Handshake 3–4Cable Examples 3–6Configuring the Logic Analyzer Interface 3–8Interface Capabilities 3–9RS-232-C Bus Addressing ...
Page 11 - Contents–3
Key Features 6–6Serial Poll 6–7 7 Error Messages Device Dependent Errors 7–3Command Errors 7–3Execution Errors 7–4Internal Errors 7–4Query Errors 7–5 Part 2 Instrument Commands 8 Common Commands *CLS (Clear Status) 8–5*ESE (Event Status Enable) 8–6*ESR (Event Status Register) 8–7*IDN (Identification...
Page 12 - Contents–4
LER (LCL Event Register) 9–11LOCKout 9–12MENU 9–12MESE<N> (Module Event Status Enable) 9–14MESR<N> (Module Event Status Register) 9–16RMODe 9–18RTC (Real-time Clock) 9–18SELect 9–19SETColor 9–21STARt 9–22STOP 9–22XWINdow 9–23 10 Module Level Commands ARMLine 10–5DBLock 10–5MACHine 10–6WL...
Page 13 - Contents–5
LOAD[:CONFig] 12–14LOAD:IASSembler 12–15MKDir (Make Directory) 12–16MSI (Mass Storage Is) 12–17PACK 12–18PURGe 12–18PWD (Present Working Directory) 12–19REName 12–19STORe[:CONFig] 12–20UPLoad 12–21VOLume 12–22 Part 3 Logic Analyzer Commands 13 MACHine Subsystem MACHine 13–4ARM 13–5ASSign 13–6LEVelar...
Page 14 - Contents–6
15 SFORmat Subsystem SFORmat 15–6CLOCk 15–6LABel 15–7MASTer 15–9MOPQual 15–10MQUal 15–11REMove 15–12SETHold 15–12SLAVe 15–14SOPQual 15–15SQUal 15–16THReshold 15–16 16 STRigger (STRace) Subsystem Qualifier 16–7STRigger (STRace) (State Trigger) 16–9ACQuisition 16–9BRANch 16–10CLEar 16–12FIND 16–13MLEN...
Page 15 - 8 SWAVeform Subsystem; Contents–7
CLRPattern 17–8DATA 17–9LINE 17–9MMODe (Marker Mode) 17–10OPATtern 17–11OSEarch 17–12OSTate 17–13OTAG 17–14OVERlay 17–15REMove 17–15RUNTil (Run Until) 17–16TAVerage 17–17TMAXimum 17–17TMINimum 17–18VRUNs 17–18XOTag 17–19XOTime 17–19XPATtern 17–20XSEarch 17–21XSTate 17–21XTAG 17–22 18 SWAVeform Subsy...
Page 16 - Contents–8
19 SCHart Subsystem SCHart 19–4ACCumulate 19–4CENTer 19–5HAXis 19–5VAXis 19–6 20 COMPare Subsystem COMPare 20–4CLEar 20–5CMASk 20–5COPY 20–6DATA 20–6FIND 20–8LINE 20–8MENU 20–9RANGe 20–9RUNTil (Run Until) 20–10SET 20–12 21 TFORmat Subsystem TFORmat (Timing Format) 21–4ACQMode 21–5LABel 21–6REMove 21...
Page 17 - 3 TWAVeform Subsystem; Contents–9
MLENgth 22–15RANGe 22–16SEQuence 22–17SPERiod 22–18TCONtrol (Timer Control) 22–19TERM 22–20TIMER 22–21TPOSition (Trigger Position) 22–22 23 TWAVeform Subsystem TWAVeform 23–7ACCumulate 23–7ACQuisition 23–8CENTer 23–8CLRPattern 23–9CLRStat 23–9DELay 23–9INSert 23–10MLENgth 23–11MMODe (Marker Mode) 23...
Page 22 - Programming Overview 37–3
35 TRIGger Subsystem CONDition 35–5DELay 35–7LEVel 35–8LOGic 35–10MODE 35–11PATH 35–12SLOPe 35–12SOURce 35–13 36 WAVeform Subsystem Format for Data Transfer 36–3Data Conversion 36–5COUNt? 36–8DATA? 36–8FORMat 36–9POINts? 36–9PREamble? 36–10RECord 36–11SOURce 36–11SPERiod? 36–12TYPE? 36–12VALid? 36–1...
Page 23 - Pattern Generator Level Commands 37–7; 8 FORMat Subsystem; FORMat Subsystem 38–2; 9 SEQuence Subsystem; SEQuence Subsystem 39–2; 0 MACRo Subsystem; MACRo Subsystem 40–2
Example Pattern Generator Program 37–3Selecting the Pattern Generator 37–4Command Set Organization 37–5 Pattern Generator Level Commands 37–7 STEP 37–8RESume 37–10 38 FORMat Subsystem FORMat Subsystem 38–2 CLOCk 38–3DELay 38–4LABel 38–5MODe 38–7REMove 38–8 39 SEQuence Subsystem SEQuence Subsystem 39...
Page 24 - 1 SYMBol Subsystem; SYMBol Subsystem 41–2; 2 DATA and SETup Commands; Data and Setup Commands 42–2; Part 6 Programming Examples
41 SYMBol Subsystem SYMBol Subsystem 41–2 BASE 41–4PATTern 41–5RANGe 41–6REMove 41–7WIDTh 41–8 42 DATA and SETup Commands Data and Setup Commands 42–2 SYSTem:DATA 42–4SYSTem:SETup 42–5 Part 6 Programming Examples 43 Programming Examples Making a Timing Analyzer Measurement 43–3Making a State Analyze...
Page 25 - General Information
Page 28 - Introduction; Set up the instrument and start measurements.
Introduction This chapter introduces you to the basics of remote programming andis organized in two sections. The first section, "Talking to theInstrument," concentrates on initializing the bus, program syntax andthe elements of a syntax instruction. The second section, "ReceivingInforma...
Page 29 - Talking to the Instrument; Example; Each part of the above statement is explained in this section.
Talking to the Instrument In general, computers acting as controllers communicate with theinstrument by sending and receiving messages over a remoteinterface, such as GPIB or RS-232-C. Instructions for programmingthe Agilent Technologies 1670G-series logic analyzer will normallyappear as ASCII chara...
Page 30 - 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 aCLEAR command that clears the interface buffer. If you are using GPIB,CLEAR will also reset the parser in the logic analyzer. The parser is th...
Page 31 - Output Command; Instruction Syntax
Instruction Syntax To program the logic analyzer remotely, you must have an understanding ofthe command format and structure. The IEEE 488.2 standard governs syntaxrules pertaining to how individual elements, such as headers, separators,parameters and terminators, may be grouped together to form com...
Page 32 - Instruction Header
Device Address The location where the device address must be specified also depends on thehost language that you are using. In some languages, this could be specifiedoutside the output command. In BASIC, this is always specified after thekeyword OUTPUT. The examples in this manual use a generic addr...
Page 33 - Instruction Terminator
When you look up a query in this programmer’s reference, you’ll find aparagraph labeled "Returned Format" under the one labeled "Query." Thesyntax definition by "Returned format" will always show the instructionheader in square brackets, like [:SYSTem:MENU], which means the t...
Page 34 - Header Types; Simple Command Header
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 areexamples of simple command headers typically used in this logic analyzer.The syntax is: <function><ter...
Page 35 - Duplicate Keywords
Common Command Header Common command headers control IEEE 488.2 functions within the logicanalyzer, such as, clear status. The syntax is: *<command header><terminator> No white space or separator is allowed between the asterisk and thecommand header. *CLS is an example of a common comman...
Page 36 - ? you must follow that with an input; 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 theresponse in the output buffer. The output message remains in the bufferuntil it is read or until another logic analyzer instruction is...
Page 37 - Program Header Options
Program Header Options Program headers can be sent using any combination of uppercase orlowercase ASCII characters. Logic analyzer responses, however, are alwaysreturned in uppercase. Both program command and query headers may be sent in either long form(complete spelling), short form (abbreviated s...
Page 38 - Numeric data; The following numbers are all equal:; Parameter Data Types
Parameter Data Types There are three main types of data which are used in parameters. They arenumeric, string, and keyword. A fourth type, block data, is used only for a fewinstructions: the DATA and SETup instructions in the SYSTem subsystem(see chapter 11); the CATalog, UPLoad, and DOWNload instru...
Page 40 - Selecting Multiple Subsystems
Selecting Multiple Subsystems You can send multiple program commands and program queries for differentsubsystems on the same line by separating each command with a semicolon.The colon following the semicolon enables you to enter a new subsystem. <instruction header><data>;:<instructio...
Page 41 - Receiving Information from the Instrument; , you must follow that query with an input statement.; To read the result of the query command
Receiving Information from the Instrument After receiving a query (logic analyzer instruction followed by a questionmark), the logic analyzer interrogates the requested function and places theanswer in its output queue. The answer remains in the output queue until itis read, or, until another comman...
Page 42 - command. If the state of the; The following examples show some possible responses for a; Response Header Options
Response Header Options The format of the returned ASCII string depends on the current settings ofthe SYSTEM HEADER and LONGFORM commands. The general format is <instruction_header><space><data><terminator> The header identifies the data that follows (the parameters) and is c...
Page 43 - The following are possible responses to the; Response Data Formats
Response Data Formats Both numbers and strings are returned as a series of ASCII characters, asdescribed in the following sections. Keywords in the data are returned in thesame format as the header, as specified by the LONGform command. Likethe headers, the keywords will always be in uppercase. Exam...
Page 44 - String Variables; operator is used for
String Variables Because there are so many ways to code numbers, the AgilentTechnologies 1670G-series logic analyzer handles almost all data as ASCIIstrings. Depending on your host language, you may be able to use othertypes when reading in responses. Sometimes it is helpful to use string variables ...
Page 45 - After the program runs, the controller displays:; Numeric Base; precedes the returned data, the value is in the binary; Numeric Variables
The output of the logic analyzer may be numeric or character data dependingon what is queried. Refer to the specific commands, in Parts 2 and 3 of thisguide, for the formats and types of data returned from queries. Example The following example shows logic analyzer data being returned to a stringvar...
Page 46 - For example, for transmitting 80 bytes of data, the syntax would be:; Definite-Length Block Response Data
This time the format of the number (such as, whether or not exponentialnotation is used) is dependent upon your host language. The output willresemble 1.E-5 in BASIC. Definite-Length Block Response Data Definite-length block response data, also referred to as block data, allows anytype of device-dep...
Page 47 - Multiple Queries
Multiple Queries You can send multiple queries to the logic analyzer within a single programmessage, but you must also read them back within a single program message.This can be accomplished by either reading them back into a string variableor into multiple numeric variables. Example You can read th...
Page 48 - Instrument Status
Instrument Status Status registers track the current status of the logic analyzer. By checkingthe instrument status, you can find out whether an operation has beencompleted, whether the instrument is receiving triggers, and more.Chapter 6, "Status Reporting," explains how to check the status...
Page 49 - Programming Over GPIB
Page 51 - Interface Capabilities
Interface Capabilities The interface capabilities of the Agilent 1670G-series logic analyzer, asdefined by IEEE 488.1 are SH1, AH1, T5, TE0, L3, LE0, SR1, RL1, PP0, DC1,DT1, C0, and E2. Command and Data Concepts GPIB has two modes of operation: command mode and data mode. The busis in command mode w...
Page 52 - Communicating Over the GPIB Bus (HP 9000 Series 200/300 Controller)
If the controller addresses the instrument to talk, it will remain configured totalk until it receives: • an interface clear message (IFC) • another instrument’s talk address (OTA) • its own listen address (MLA) • a universal untalk (UNT) command If the controller addresses the instrument to listen,...
Page 54 - Device Clear; Bus Commands
Bus Commands The following commands are IEEE 488.1 bus commands (ATN true). IEEE488.2 defines many of the actions which are taken when these commands arereceived by the logic analyzer. Device Clear The device clear (DCL) or selected device clear (SDC) commands clear theinput and output buffers, rese...
Page 57 - Interface Operation
Interface Operation The Agilent 1670G-series logic analyzer can be programmed with a controllerover RS-232-C using either a minimum three-wire or extended hardwireinterface. The operation and exact connections for these interfaces aredescribed in more detail in the following sections. When you arepr...
Page 58 - Pin 2 TD (Transmit Data from logic analyzer); Extended Interface with Hardware Handshake; Minimum Three-Wire Interface with Software Protocol
Minimum Three-Wire Interface with Software Protocol With a three-wire interface, the software (as compared to interfacehardware) controls the data flow between the logic analyzer and thecontroller. The three-wire interface provides no hardware means to controldata flow between the controller and the...
Page 60 - Cable Examples; HP Vectra Personal Computers and Compatibles
Cable Examples HP 9000 Series 300 Figure 3-1 is an example of how to connect the Agilent 1670G-series to theHP 98628A interface card of an HP 9000 series 300 controller. For moreinformation on cabling, refer to the reference manual for your specificcontroller. Because this example does not have the ...
Page 62 - Agilent 1670G-Series Logic Analyzers User’s Guide.; Configuring the Logic Analyzer Interface
Figure 3-4 shows the schematic of a 9-pin female to 25-pin male cable. Thefollowing cables support this configuration: • 24542G, DB-9(F) to DB-25(M), 3 meter • 24542H, DB-9(F) to DB-25(M), 3 meter, shielded • 45911-60009, DB-9(F) to DB-25(M), 1.5 meter Figure 3-4 9-pin (F) to 25-pin (M) Cable Config...
Page 63 - Protocol; With a three-wire interface, selecting None for the protocol does; Data Bits
Interface Capabilities The baud rate, stopbits, parity, protocol, and databits must be configuredexactly the same for both the controller and the logic analyzer to properlycommunicate over the RS-232-C bus. The RS-232-C interface capabilities ofthe Agilent 1670G-series logic analyzer are listed belo...
Page 64 - See Also; For more information on the RS-232-C interface, refer to the; HP Vectra Personal Computers or compatibles
The controller and the Agilent 1670G-series logic analyzer must be in thesame bit mode to properly communicate over the RS-232-C. This means thatthe controller must have the capability to send and receive 8-bit data. See Also For more information on the RS-232-C interface, refer to the Agilent 1670G...
Page 65 - Lockout Command; OFF; C A U T I O N
Lockout Command To lockout the front-panel controls, use the instrument command LOCKout.When this function is on, all controls (except the power switch) are entirelylocked out. Local control can only be restored by sending the :LOCKout OFF command. C A U T I O N Cycling the power will also restore l...
Page 69 - Truncation Examples; Programming and Documentation Conventions; Truncation Rule
Truncation Rule The truncation rule for the keywords used in headers and parameters is: If the long form has four or fewer characters, there is no change in the shortform. When the long form has more than four characters the short form isjust the first four characters, unless the fourth character is...
Page 70 - Infinity Representation
Infinity Representation The representation of infinity is 9.9E+37 for real numbers and 32767 forintegers. This is also the value returned when a measurement cannot bemade. Sequential and Overlapped Commands IEEE 488.2 makes the distinction between sequential and overlappedcommands. Sequential comman...
Page 71 - Square brackets indicate that the enclosed items are optional.; The Command Tree; Notation Conventions and Definitions
Notation Conventions and Definitions The following conventions are used in this manual when describingprogramming rules and example. < > Angular brackets enclose words or characters that are used to symbolize aprogram code parameter or a bus command ::= "is defined as." For example, A ...
Page 72 - Tree Traversal Rules
Command Types As shown in chapter 1, in the topic, "Header Types," there are three types ofheaders. Each header has a corresponding command type. This sectionshows how they relate to the command tree. System Commands The system commands reside at the top level of the command tree. These comm...
Page 76 - Alphabetic Command Cross-Reference
Table 4-2 Alphabetic Command Cross-Reference Command Subsystem ACCumulate SCHart, SWAVeform, TWAVeform, ACQMode TFORmat ACQuisition STRigger, SWAVeform, TTRigger,TWAVeform ARM MACHine ASSign MACHine AUToload MMEMory AUTorange TINTerval BASE SYMBolBEEPer Mainframe BRANch STRigger, TTRigger BUCKet OVE...
Page 78 - AUToload; Subsystems; Command Set Organization
Command Set Organization The command set for the Agilent 1670G-series logic analyzers is divided into19 separate groups: common commands, system commands, and 17 sets ofsubsystem commands. Each of the 19 groups of commands is described in aseparate chapter in Parts 2 and 3, "Commands." Each ...
Page 79 - Keywords in short form, numbers using an exponential format.; Program Examples
• TTRigger - allows access to the timing trigger functions. • TWAVeform - allows access to the timing waveforms functions. • TLISt - allows access to the timing listing functions. • SYMBol - allows access to the symbol specification functions. • SPA - allows access to the System Performance Analysis...
Page 83 - Functional Elements; The input buffer of the instrument is the memory area; Output Queue; The output queue of the instrument is the memory area; Parser; The instrument’s parser is the component that interprets the; Protocols
Protocols The protocols of IEEE 488.2 define the overall scheme used by the controllerand the instrument to communicate. This includes defining when it isappropriate for devices to talk or listen, and what happens when the protocolis not followed. Functional Elements Before proceeding with the descr...
Page 84 - Message Communication and System Functions
Protocol Overview The instrument and controller communicate using <program message> s and <response message> s. These messages serve as the containers into which sets of program commands or instrument responses are placed. <program message> s are sent by the controller to the instr...
Page 85 - A command error will be reported if the instrument; Execution Error; An execution error will be reported if a parameter is; Device-specific Error; A device-specific error will be reported if the; Query Error; A query error will be reported if the proper protocol for; Syntax Diagrams
Protocol Exceptions If an error occurs during the information exchange, the exchange may not becompleted in a normal manner. Some of the protocol exceptions are shownbelow. Command Error A command error will be reported if the instrument detects a syntax error or an unrecognized command header. Exec...
Page 87 - Syntax Overview
Syntax Overview This overview is intended to give a quick glance at the syntax defined byIEEE 488.2. It will help you understand many of the things about the syntaxyou need to know. IEEE 488.2 defines the blocks used to build messages which are sent to theinstrument. A whole string of commands can t...
Page 89 - Upper/Lower Case Equivalence; SINGLE; Suffix Multiplier
Upper/Lower Case Equivalence Upper and lower case letters are equivalent. The mnemonic SINGLE has the same semantic meaning as the mnemonic single . <white space> <white space> is defined to be one or more characters from the ASCII set of 0 - 32 decimal, excluding 10 decimal (NL). <wh...
Page 90 - Suffix Unit; The suffix units that the instrument will accept are shown
Suffix Unit The suffix units that the instrument will accept are shown in table 5-2. Table 5-2 <suffix unit> Suffix Referenced Unit V Volt S Second Message Communication and System Functions Syntax Overview 5–10
Page 91 - Status Reporting
Page 92 - the output queue will also be cleared.
Introduction Status reporting allows you to use information about the instrument inyour programs, so that you have better control of the measurementprocess. For example, you can use status reporting to determinewhen a measurement is complete, thus controlling your program, sothat it does not get ahe...
Page 94 - MAV - message available; Indicates whether there is a response in the output queue.; ESB - event status bit; Event Status Register
Event Status Register The Event Status Register is an IEEE 488.2-defined register. The bits in thisregister are latched. Once an event happens which sets a bit, that bit willonly be cleared if the register is read. Service Request Enable Register The Service Request Enable Register is an 8-bit regis...
Page 95 - EXE - execution error; Indicates whether the protocol for queries has been violated.; RQC - request control; Always returns a 0 from the Agilent 1670G-series logic analyzer.; OPC - operation complete; Bit Definitions
MSG - message Indicates whether there is a message in the message queue (Notimplemented in the Agilent 1670G-series logic analyzer). PON - power on Indicates power has been turned on. URQ - user request Always returns a 0 from the Agilent 1670G-series logic analyzer. CME - command error Indicates wh...
Page 96 - LCL - remote to local; Indicates whether a remote to local transition has occurred.; MSB - module summary bit; Operation Complete; Status Byte; The Status Byte is cleared with the *CLS common command.; 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 status registers has occurred. Key Features A few of the most important features of Status Reporting are listed in thefollowing paragraphs. Operati...
Page 97 - Serial Poll
Figure 6-2 Service Request Enabling Serial Poll The Agilent 1670G-series logic analyzer supports the IEEE 488.1 serial pollfeature. When a serial poll of the instrument is requested, the RQS bit isreturned on bit 6 of the status byte. Status Reporting Serial Poll 6–7
Page 99 - Error Messages
Page 101 - Device Dependent Errors
Device Dependent Errors 200 Label not found 201 Pattern string invalid 202 Qualifier invalid 203 Data not available 300 RS-232-C error Command Errors –100 Command error (unknown command)(generic error) –101 Invalid character received –110 Command header error –111 Header delimiter error –120 Numeric...
Page 102 - Execution Errors
Execution Errors –200 Can not do (generic execution error) –201 Not executable in Local Mode –202 Settings lost due to return-to-local or power on –203 Trigger ignored –211 Legal command, but settings conflict –212 Argument out of range –221 Busy doing something else –222 Insufficient capability or ...
Page 103 - Query Errors
–321 ROM checksum –322 Hardware and firmware incompatible –330 Power on test failed –340 Self test failed –350 Too many errors (error queue overflow) Query Errors –400 Query error (generic) –410 Query INTERRUPTED –420 Query UNTERMINATED –421 Query received. Indefinite block response in progress –422...
Page 105 - Instrument Commands
Page 107 - Common Commands
Page 111 - Common Command Parameter Values
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, anddata structures, including the device defined error queue and status...
Page 112 - Query
*ESE (Event Status Enable) Command *ESE <mask> The *ESE command sets the Standard Event Status Enable Register bits.The Standard Event Status Enable Register contains a bit to enable thestatus indicators detailed in table 8-2. A 1 in any bit position of the StandardEvent Status Enable Register...
Page 113 - Standard Event Status Enable 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 S...
Page 114 - The Standard Event Status Register
Table 8-3 shows the Standard Event Status Register. The table details themeaning of each bit position in the Standard Event Status Register and thebit weight. When you read Standard Event Status Register, the valuereturned is the total bit weight of all the bits that are high at the time youread the...
Page 120 - Parallel Poll Enable Register
Table 8-4 Parallel Poll Enable Register Bit Position Bit Weight Enables 15 -8 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 implemen...
Page 122 - Agilent 1670G-Series Service Request Enable Register
Table 8-5 Agilent 1670G-Series Service Request Enable Register Bit Position Bit Weight Enables 15-8 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 ...
Page 123 - Status Byte Register
Table 8-6 Status Byte Register Bit Position Bit Weight Bit Name Condition 7 128 not used 6 64 MSS 0 = instrument has no reason for service1 = instrument is requesting service 5 32 ESB 0 = no event status conditions have occurred1 = an enabled event status condition has occurred 4 16 MAV 0 = no outpu...
Page 131 - Mainframe Parameter Values
Table 9-1 Mainframe Parameter Values Parameter Values value An integer from 0 to 65535 module An integer 0 or 1 (2 through 10 unused) menu An integer enable_value An integer from 0 to 255 index An integer from 0 to 5 day An integer from 1 through 31 month An integer from 1 through 12 year An integer...
Page 132 - BEEPer
BEEPer Command :BEEPer [{ON|1}|{OFF|0}] The BEEPer command sets the beeper mode, which turns the beeper soundof the instrument on and off. When BEEPer is sent with no argument, thebeeper will be sounded without affecting the current mode. Example OUTPUT XXX;":BEEPER" OUTPUT XXX;":BEEP ON...
Page 133 - CAPability
CAPability Query :CAPability? The CAPability? query returns the system language and lower level capabilitysets implemented in the device. Table 9-2 lists the capability sets implemented in the Agilent 1670G-serieslogic analyzer. Returned Format [:CAPability] IEEE488,1987,SH1,AH1,T5,L4,SR1,RL1,PP1,DC...
Page 134 - CARDcage
CARDcage Query :CARDcage? The CARDcage? query returns 10 integers which identify the card setup thatis installed in the logic analyzer. The Agilent 1670G-series logic analyzersalways return the same series of integers since the analyzers are notexpandable the way an 16500 logic analysis system is. T...
Page 137 - The EOI? query returns the current status of EOI.
EOI (End Or Identify) Command :EOI {{ON|1}|{OFF|0}} The EOI command specifies whether or not the last byte of a reply from theinstrument is to be sent with the EOI bus control line set true or not. If EOIis turned off, the logic analyzer will no longer be sending IEEE 488.2compliant responses. Examp...
Page 138 - MENU; LOCKout
LOCKout Command :LOCKout {{ON|1}|{OFF|0}} The LOCKout command locks out or restores front panel operation. Whenthis function is on, all controls (except the power switch) are entirely lockedout. Example OUTPUT XXX;":LOCKOUT ON" Query :LOCKout? The LOCKout? query returns the current status of...
Page 139 - Menu Parameter Values
Table 9-5 Menu Parameter Values Parameters Menu 0,0 System External I/O 0,1 System Hard Disk 0,2 System Flexible 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 Mi...
Page 144 - RMODe
RMODe Command :RMODe {SINGle|REPetitive} The RMODe command specifies the run mode for the logic analyzer. After specifying the run mode, use the STARt command to start the acquisition. Example OUTPUT XXX;":RMODE SINGLE" Query :RMODe? The query returns the current setting. Returned Format [:R...
Page 145 - SELect
<hour> integer from 0 to 23 <minute> integer from 0 to 59 <second> integer from 0 to 59 Example This example sets the real-time clock for 1 January 1992, 20:00:00 (8 PM). OUTPUT XXX;":RTC 1,1,1992,20,0,0" Query :RTC? The RTC? query returns the real-time clock setting. Retur...
Page 147 - SETColor
SETColor Command :SETColor {<color>,<hue>,<sat>,<lum>|DEFault} The SETColor command is used to change a grayscale shade on the logicanalyzer screen, or to return to the default screen colors. The colors on aremote display are not affected. Four parameters are sent with thecom...
Page 148 - STOP; STARt
STARt Command :STARt The STARt command starts the logic analyzer running in the specified runmode (see RMODe). The STARt command is an overlapped command. An overlapped command is acommand that allows execution of subsequent commands while the deviceoperations initiated by the overlapped command are...
Page 149 - To open a window specifying and storing the display name:; XWINdow
XWINdow Command :XWINdow {OFF|0}:XWINdow {ON|1}[,<display name>] The XWINdow command opens or closes a window on an X Window displayserver, that is, a networked workstation or personal computer with X Windowsoftware. The XWINdow ON command opens a window. If no display nameis specified, the di...
Page 151 - Module Level Commands
Page 152 - ARMLine
Introduction The logic analyzer module-level commands access the global functionsof the Agilent 1670G-series logic analyzer. These commands are: • ARMLine • MACHine • WLISt • DBLock 10–2
Page 154 - Module Level Parameter Values
Table 10-1 Module Level Parameter Values Parameter Type of Parameter or Command Reference machine_num MACHine{1|2} arm_parm arm parameters see chapter 13 assign_parm assignment parameters see chapter 13 level_parm level parameters see chapter 13 name_parm name parameters see chapter 13 rename_parm r...
Page 155 - DBLock
ARMLine Command :ARMLine MACHine{1|2} The ARMLine command selects which machine (analyzer) generates the armout signal. This command is only valid when two analyzers are on. However,the query is always valid. Example OUTPUT XXX;":ARMLINE MACHINE1" Query :ARMLine? Returned Format [:ARMLine]MA...
Page 156 - WLISt; MACHine
Query :DBLock? The DBLock query returns the current data block format selection. Returned Format [:DBLock]{PACKed | UNPacked}<NL> Example OUTPUT XXX;":DBLock?" MACHine Command :MACHine{1|2} The MACHine command selects which of the two machines (analyzers) thesubsequent commands or quer...
Page 157 - SYSTem Subsystem
Page 160 - SYSTem Parameter Values
Table 11-1 SYSTem Parameter Values Parameter Values block_data Data in IEEE 488.2 format. string A string of up to 68 alphanumeric characters. pathname A string of up to 10 alphanumeric characters for LIF in thefollowing form: NNNNNNNNNN orA string of up to 64 alphanumeric characters for DOS in one ...
Page 161 - The format depends on the type of data; DATA
DATA Command :SYSTem:DATA <block_data> The DATA command allows you to send and receive acquired data to andfrom a controller in block form. This helps saving block data for: • Reloading to the logic analyzer • Processing data later in the logic analyzer • Processing data in the controller The ...
Page 163 - ERRor
ERRor Query :SYSTem:ERRor? [NUMeric|STRing] The ERRor query returns the oldest error from the error queue. The optionalparameter determines whether the error string should be returned along withthe error number. If no parameter is received, or if the parameter isNUMeric, then only the error number i...
Page 164 - HEADer
HEADer Command :SYSTem:HEADer {{ON|1}|{OFF|0}} The HEADer command tells the instrument whether or not to output aheader for query responses. When HEADer is set to ON, query responses willinclude the command header. Example OUTPUT XXX;":SYSTEM:HEADER ON" Query :SYSTem:HEADer? The HEADer? quer...
Page 165 - LONGform
LONGform Command :SYSTem:LONGform {{ON|1}|{OFF|0}} The LONGform command sets the longform variable, which tells theinstrument how to format query responses. If the LONGform command is setto OFF, command headers and alpha arguments are sent from the instrumentin the abbreviated form. If the the LONGf...
Page 166 - PRINt
PRINt Command :SYSTem:PRINt ALL[,DISK, <pathname>[,<msus>]] :SYSTem:PRINt PARTial,<start>,<end>[,DISK, <pathname>[,<msus>]]:SYSTem:PRINt SCReen[,DISK, <pathname> [,<msus>], {BTIF|CTIF|PCX|EPS}] The PRINt command initiates a print of the screen or listi...
Page 167 - SETup
The print query should NOT be sent with any other command or query on thesame command line. The print query never returns a header. Also, sinceresponse data from a print query may be sent directly to a printer withoutmodification, the data is not returned in block mode. Example OUTPUT 707;":SYST...
Page 169 - MMEMory Subsystem
Page 174 - MMEMory Parameter Values
Table 12-1 MMEMory Parameter Values Parameter Values auto_file A string of up to 10 alphanumeric characters for LIF in thefollowing form: "NNNNNNNNNN"orA string of up to 12 alphanumeric characters for DOS in thefollowing form: "NNNNNNNN.NNN" msus Mass Storage Unit specifier. INTernal...
Page 175 - for the hard disk drive and
AUToload Command :MMEMory:AUToload {{OFF|0}|{<auto_file>}}[,<msus>] The AUToload command controls the autoload feature which designates a setof configuration files to be loaded automatically the next time the instrumentis turned on. The OFF parameter (or 0) disables the autoload feature....
Page 176 - ALL; CATalog
<auto_file> A string of up to 10 alphanumeric characters for LIF in the following form: NNNNNNNNNN orA string of up to 12 alphanumeric characters for DOS in the following form: NNNNNNNN.NNN Example OUTPUT XXX;":MMEMORY:AUTOLOAD?" CATalog Query :MMEMory:CATalog? [[All][<msus>]] Th...
Page 177 - Returned Format
Returned Format [:MMEMory:CATalog] <block_data> <block_data> ASCII block containing < filename> <file_type> <file_description> Example This example is for sending the CATALOG? ALL query: OUTPUT 707;":MMEMORY:CATALOG? ALL" This example is for sending the CATALOG?...
Page 178 - for the flexible disk drive.; COPY
COPY Command :MMEMory:COPY <name>[,<msus>],<new_name>[,<msus>] The COPY command copies one file to a new file or an entire disk’s contentsto another disk. The two <name> parameters are the filenames. The first pair of parameters specifies the source file. The second pai...
Page 179 - DOWNload
DOWNload Command :MMEMory:DOWNload <name>[,<msus>],<description>,<type>,<block_data> The DOWNload command downloads a file to the mass storage device. The <name> parameter specifies the filename, the <description> parameter specifies the file descriptor, and...
Page 180 - File Types
Table 12-2 File Types File File Type 1660E/ES and 1670G ROM Software -15599 1660E/ES and 1670G System Software -15598 1660E/ES and 1670G System External I/O -15605 1660E/ES Logic Analyzer Software -15597 1660E/ES Logic Analyzer Configuration -16096 1670G Logic Analyzer Software -15595 1670G Logic An...
Page 181 - INITialize
INITialize Command :MMEMory:INITialize [{LIF|DOS}[,<msus>]] The INITialize command formats the disk in either LIF (Logical InformationFormat) or DOS (Disk Operating System). If no format is specified, then theinitialize command will format the disk in the LIF format. <msus> Mass Storage ...
Page 186 - PURGe; PACK
PACK Command :MMEMory:PACK [<msus>] The PACK command packs the files on a LIF disk. If a DOS disk is in thedrive when the PACK command is sent, no action is taken. <msus> Mass Storage Unit specifier. INTernal0 for the hard disk drive and INTernal1 for the flexible disk drive. Example OUT...
Page 187 - REName
PWD (Present Working Directory) Query :MMEMory:PWD? [<msus>] The PWD query returns the present working directory for the specified drive.If the <msus> option is not sent, the present working directory will be returned for the current drive. Returned Format [:MMEMory:PWD] <directory>...
Page 189 - UPLoad
Example 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 arestored. "X" refers to either an __ (double und...
Page 190 - VOLume
Example 10 DIM Block$[32000] !allocate enough memory for block data 20 DIM Specifier$[2] 30 OUTPUT XXX;":EOI ON" 40 OUTPUT XXX;":SYSTEM HEAD OFF" 50 OUTPUT XXX;":MMEMORY:UPLOAD? ’FILE1’" !send upload query 60 ENTER XXX USING "#,2A";Specifier$ !read in #8 70 ENTER XXX ...
Page 191 - Logic Analyzer Commands
Page 193 - MACHine Subsystem
Page 196 - MACHine Subsystem Parameter Values; Selector
Table 13-1 MACHine Subsystem Parameter Values Parameter Value arm_source {RUN | INTermodule | MACHine {1|2}} pod_list {NONE | <pod_num>[, <pod_num>]...} pod_num integer from 1 to 8 arm_level integer from 1 to 11 representing sequence level machine_name string of up to 10 alphanumeric cha...
Page 197 - ARM
ARM Command :MACHine{1|2}:ARM <arm_source> The ARM command specifies the arming source of the specified analyzer(machine). The RUN option disables the arm source. For example, if you donot want to use either the intermodule bus or the other machine to arm thecurrent machine, you specify the RU...
Page 198 - ASSign
ASSign Command :MACHine{1|2}:ASSign <pod_list> The ASSign command assigns pods to a particular analyzer (machine). TheASSign command will assign two pods for each pod number you specifybecause pods must be assigned to analyzers in pairs. NONE clears all podsfrom the specified analyzer (machine...
Page 199 - LEVelarm
LEVelarm Command :MACHine{1|2}:LEVelarm <arm_level> The LEVelarm command allows you to specify the sequence level for aspecified machine that will be armed by the Intermodule Bus or the othermachine. This command is only valid if the specified machine is on and thearming source is not set to R...
Page 200 - NAME
NAME Command :MACHine{1|2}:NAME <machine_name> The NAME command allows you to assign a name of up to 10 characters to aparticular analyzer (machine) for easier identification. <machine_name> string of up to 10 alphanumeric characters Example OUTPUT XXX;":MACHINE1:NAME ’DRAMTEST’"...
Page 201 - string of up to 8 alphanumeric characters; RESource
<new_text> string of up to 8 alphanumeric characters <state_terms> {A|B|C|D|E|F|G|I| RANGe1 | RANGe2 | TIMer1 | TIMer2} Example OUTPUT XXX;":MACHINE1:RENAME A,’DATA’" Query :MACHine{1|2}:RENAME? <res_id> The REName query returns the current names for specified terms assigne...
Page 202 - TYPE; Only one timing analyzer can be specified at a time.
Query :MACHine{1|2}:RESOURCE? The RESource query returns the current resource terms assigned to thespecified analyzer. Returned Format [:MACHine{1|2}:RESOURCE] <res_id>[,<res_id>,...]<NL> Example OUTPUT XXX;":MACHINE1:RESOURCE?" TYPE Command :MACHine{1|2}:TYPE <analyzer ...
Page 203 - WLISt Subsystem
Page 206 - WLISt Subsystem Parameter Values
Table 14-1 WLISt Subsystem Parameter Values Parameter Value delay_value real number between -2500 s and +2500 s module_spec 1 bit_id integer from 0 to 31 label_name string of up to 6 alphanumeric characters line_num_mid_screen integer from -1032192 to +1032192 time_value real number time_range real ...
Page 207 - DELay
DELay Command :WLISt:DELay <delay_value> The DELay command specifies the amount of time between the timingtrigger and the horizontal center of the the timing waveform display. Theallowable values for delay are − 2500 s to +2500 s. <delay_value> real number between − 2500 s and +2500 s Ex...
Page 208 - INSert
INSert Command :WLISt:INSert [<module_spec>,]<label_name>[,{<bit_id>|OVERlay|ALL}] The INSert command inserts waveforms in the timing waveform display. Thewaveforms are added from top to bottom up to a maximum of 96 waveforms.Once 96 waveforms are present, each time you insert anot...
Page 209 - LINE; OSTate; integer
LINE Command :WLISt:LINE <line_num_mid_screen> The LINE command allows you to scroll the timing analyzer listing vertically.The command specifies the state line number relative to the trigger that theanalyzer highlights at the center of the screen. <line_num_mid_ screen> integer from -10...
Page 210 - RANGe; OTIMe
OTIMe Command :WLISt:OTIMe <time_value> The OTIMe command positions the O Marker on the timing waveforms in themixed mode display. If the data is not valid, the command performs noaction. <time_value> real number Example OUTPUT XXX;":WLIST:OTIME 40.0E − 6" Query :WLISt:OTIMe? The...
Page 211 - The RANGe query returns the current full-screen time.; REMove; The REMove command deletes all waveforms from the display.; XOTime; real number
Query :WLISt:RANGe? The RANGe query returns the current full-screen time. Returned Format [:WLISt:RANGe] <time_value><NL> Example OUTPUT XXX;":WLIST:RANGE?" REMove Command :WLISt:REMove The REMove command deletes all waveforms from the display. Example OUTPUT XXX;":WLIST:REMO...
Page 212 - XSTate; XTIMe
XSTate Query :WLISt:XSTate? The XSTate query returns the state where the X Marker is positioned. If datais not valid, the query returns 2147483647. Returned Format [:WLISt:XSTate] <state_num><NL> <state_num> integer Example OUTPUT XXX;":WLIST:XSTATE?" XTIMe Command :WLISt:X...
Page 213 - SFORmat Subsystem
Page 217 - SFORmat Subsystem Parameter Values
Table 15-1 SFORmat Subsystem Parameter Values Parameter Value <N> an integer from 1 to 8 label_name string of up to 6 alphanumeric characters polarity {POSitive | NEGative} clock_bits format (integer from 0 to 65535) for a clock (clocks are assignedin decreasing order) upper_bits format (integ...
Page 218 - CLOCk; SFORmat
SFORmat Selector :MACHine{1|2}:SFORmat The SFORmat (State Format) selector is used as a part of a compoundheader to access the settings in the State Format menu. It always follows theMACHine selector because it selects a branch directly below the MACHinelevel in the command tree. Example OUTPUT XXX;...
Page 219 - LABel
Query :MACHine{1|2}:SFORmat:CLOCk<N>? The CLOCk query returns the current clocking mode for a given pod. Returned Format [:MACHine{1|2}:SFORmat:CLOCK<N>] <clock_mode><NL> Example OUTPUT XXX; ":MACHINE1:SFORMAT:CLOCK2?" LABel Command :MACHine{1|2}:SFORmat:LABel<name...
Page 221 - MASTer
MASTer Command :MACHine{1|2}:SFORmat:MASTer<clock_id>,<clock_spec> The MASTer clock command allows you to specify a master clock for a givenmachine. The master clock is used in all clocking modes (Master, Slave, andDemultiplexed). Each command deals with only one clock (J,K,L,M);therefor...
Page 222 - MOPQual
MOPQual Command :MACHine{1|2}:SFORmat:MOPQual<clock_pair_id>,<qual_operation> The MOPQual (master operation qualifier) command allows you to specifyeither the AND or the OR operation between master clock qualifier pair 1 and2, or between master clock qualifier pair 3 and 4. For example, ...
Page 223 - MQUal
MQUal Command :MACHine{1|2}:SFORmat:MQUal<qual_num>,<clock_id>,<qual_level> The MQUal (master qualifier) command allows you to specify the levelqualifier for the master clock. <qual_num> {1|2|3|4} <clock_id> {J|K|L|M} <qual_level> {OFF|LOW|HIGH} Example OUTPUT XXX...
Page 224 - SETHold
REMove Command :MACHine{1|2}:SFORmat:REMove {<name>|ALL} The REMove command allows you to delete all labels or any one label for agiven machine. <name> string of up to 6 alphanumeric characters Example OUTPUT XXX;":MACHINE2:SFORMAT:REMOVE ’A’" OUTPUT XXX;":MACHINE2:SFORMAT:RE...
Page 225 - Setup and hold values
Table 15-2 Setup and hold values For one clock and one edge For one clock and both edges Multiple Clocks 0 = 3.5/0.0 ns 0 = 4.0/0.0 ns 0 = 4.5/0.0 ns 1 = 3.0/0.5 ns 1 = 3.5/0.5 ns 1 = 4.0/0.5 ns 2 = 2.5/1.0 ns 2 = 3.0/1.0 ns 2 = 3.5/1.0 ns 3 = 2.0/1.5 ns 3 = 2.5/1.5 ns 3 = 3.0/1.5 ns 4 = 1.5/2.0 ns ...
Page 226 - SLAVe
SLAVe Command :MACHine{1|2}:SFORmat:SLAVe<clock_id>,<clock_spec> The SLAVe clock command allows you to specify a slave clock for a givenmachine. The slave clock is only used in the Slave and Demultiplexedclocking modes. Each command deals with only one clock (J,K,L,M);therefore, a comple...
Page 227 - SOPQual
SOPQual Command :MACHine{1|2}:SFORmat:SOPQual<clock_pair_id>,<qual_operation> The SOPQual (slave operation qualifier) command allows you to specifyeither the AND or the OR operation between slave clock qualifier pair 1 and2, or between slave clock qualifier pair 3 and 4. For example you ...
Page 228 - THReshold; SQUal
SQUal Command :MACHine{1|2}:SFORmat:SQUal<qual_num>,<clock_id>,<qual_level> The SQUal (slave qualifier) command allows you to specify the level qualifierfor the slave clock. <qual_num> {1|2|3|4} <clock_id> {J|K|L|M} <qual_level> {OFF|LOW|HIGH} Example OUTPUT XXX;&...
Page 236 - STRigger Subsystem Parameter Values
Table 16-1 STRigger Subsystem Parameter Values Parameter Value branch_qualifier <qualifier> to_lev_num integer from 1 to last level proceed_qualifier <qualifier> occurrence number from 1 to 1048575 label_name string of up to 6 alphanumeric characters start_pattern "{#B{0|1} . . . |#Q...
Page 237 - Qualifier
Qualifier The qualifier for the state trigger subsystem can be terms A - J, Timer 1 and2, and Range 1 and 2. In addition, qualifiers can be the NOT boolean functionof terms, timers, and ranges. The qualifier can also be an expression orcombination of expressions as shown below and figure 16-2, "...
Page 238 - Qualifier Rules; The following rules apply to qualifiers:
<term3a> { A | NOTA } <term3b> { B | NOTB } <term3c> { C | NOTC } <term3d> { D | NOTD } <term3e> { E | NOTE } <term3f> { F | NOTF } <term3g> { G | NOTG } <term3h> { H | NOTH } <term3i> { I | NOTI } <term3j> { J | NOTJ } <range3a> { IN...
Page 239 - ACQuisition
STRigger (STRace) (State Trigger) Selector :MACHine{1|2}:STRigger The STRigger selector is used as a part of a compound header to access thesettings found in the State Trace menu. It always follows the MACHineselector because it selects a branch directly below the MACHine level in thecommand tree. E...
Page 240 - integer from 1 to; BRANch
BRANch Command :MACHine{1|2}:STRigger:BRANch<N><branch_qualifier>,<to_level_number> The BRANch command defines the branch qualifier for a given sequencelevel. When this branch qualifier is matched, it will cause the triggersequence to jump to the specified sequence level. The terms...
Page 242 - AND; CLEar
Example The following example would be used to specify this complex qualifier. OUTPUT XXX;":MACHINE1:STRIGGER:BRANCH1 ’((A OR B) AND (F OR G))’, 2" Terms A through E, RANGE 1, and TIMER 1 must be grouped togetherand terms F through J, RANGE 2, and TIMER 2 must be grouped together.In the firs...
Page 243 - FIND
FIND Command :MACHine{1|2}:STRigger:FIND<N><proceed_qualifier>,<occurrence> The FIND command defines the proceed qualifier for a given sequence level.The qualifier tells the state analyzer when to proceed to the next sequencelevel. When this proceed qualifier is matched the specifi...
Page 244 - MLENgth
Query :MACHine{1|2}:STRigger:FIND<N>? The FIND query returns the current proceed qualifier specification for agiven sequence level. Returned Format [:MACHine{1|2}:STRigger:FIND<N>] <proceed_qualifier>,<occurrence><NL> Example OUTPUT XXX;":MACHINE1:STRIGGER:FIND4?...
Page 246 - SEQuence
Query :MACHine{1|2}:STRigger:RANGe<N>? The RANGe query returns the range recognizer end point specifications forthe range. Returned Format [:MACHine{1|2}:STRigger:RANGe<N>] <label_name>,<start_pattern>, <stop_pattern><NL> Example OUTPUT XXX;":MACHINE1:STRIGGER...
Page 247 - STORe
Query :MACHine{1|2}:STRigger:SEQuence? The SEQuence query returns the current sequence specification. Returned Format [:MACHine{1|2}:STRigger:SEQuence] <number_of_levels>, <level_of_trigger><NL> Example OUTPUT XXX;":MACHINE1:STRIGGER:SEQUENCE?" STORe Command :MACHine{1|2}:S...
Page 248 - TAG
Query :MACHine{1|2}:STRigger:STORe<N>? The STORe query returns the current store qualifier specification for a givensequence level <N>. Returned Format [:MACHine{1|2}:STRigger:STORe<N>] <store_qualifier><NL> Example OUTPUT XXX;":MACHINE1:STRIGGER:STORE4?" TAG Co...
Page 249 - TAKenbranch
Query :MACHine{1|2} :STRigger:TAG? The TAG query returns the current count tag specification. Returned Format [:MACHine{1|2}:STRigger:TAG] {OFF|TIME|<state_tag_qualifier>}<NL> Example OUTPUT XXX;":MACHINE1:STRIGGER:TAG?" TAKenbranch Command :MACHine{1|2}:STRigger:TAKenbranch {STO...
Page 250 - TCONtrol
TCONtrol Command :MACHine{1|2}:STRigger:TCONtrol<N> <timer_num>,{OFF|STARt|PAUSe|CONTinue} The TCONtrol (timer control) command allows you to turn off, start, pause,or continue the timer for the specified level. The time value of the timer isdefined by the TIMER command. There are two ti...
Page 251 - TERM
TERM Command :MACHine{1|2}:STRigger:TERM<term_id>,<label_name>,<pattern> The TERM command allows you to specify a pattern recognizer term in thespecified machine. Each command deals with only one label in the giventerm; therefore, a complete specification could require several comm...
Page 252 - TIMER
Query :MACHine{1|2}:STRigger:TERM?<term_id>,<label_name> The TERM query returns the specification of the term specified by termidentification and label name. Returned Format [:MACHine{1|2}:STRAce:TERM] <term_id>,<label_name>,<pattern><NL> Example OUTPUT XXX;":...
Page 253 - TPOSition
TPOSition Command :MACHine{1|2}:STRigger:TPOSition{STARt|CENTer|END| POSTstore,<poststore >} The TPOSition (trigger position) command allows you to set the trigger atthe start, center, end or at any position in the trace (poststore). Poststore isdefined as 0 to 100 percent with a poststore of ...
Page 255 - SLISt Subsystem
Page 260 - SLISt Subsystem Parameter Values
Table 17-1 SLISt Subsystem Parameter Values Parameter Value mod_num 1 (2 through 10 not used) mach_num {1|2} col_num integer from 1 to 61 line_number integer from -1032192 to +1032192 label_name a string of up to 6 alphanumeric characters base {BINary|HEXadecimal|OCTal|DECimal|TWOS|ASCii|SYMBol|IASS...
Page 261 - COLumn; SLISt
SLISt Selector :MACHine{1|2}:SLISt The SLISt selector is used as part of a compound header to access thosesettings normally found in the State Listing menu. It always follows theMACHine selector because it selects a branch directly below the MACHinelevel in the command tree. Example OUTPUT XXX;"...
Page 262 - CLRPattern
<col_num> integer from 1 to 61 <module_num> 1 (2 through 10 are not used) <label_name> a string of up to 6 alphanumeric characters <base> {BINary|HEXadecimal|OCTal|DECimal|TWOS|ASCii|SYMBol| IASSembler} for labels or {ABSolute|RELative} for tags Example OUTPUT XXX;":MACHI...
Page 265 - OPATtern
Query :MACHine{1|2}:SLISt:MMODe? The MMODe query returns the current marker mode selected. Returned Format [:MACHine{1|2}:SLISt:MMODe] <marker_mode><NL> Example OUTPUT XXX;":MACHINE1:SLIST:MMODE?" OPATtern Command :MACHine{1|2}:SLISt:OPATtern<label_name>,<label_pattern&g...
Page 266 - OSEarch
Query :MACHine{1|2}:SLISt:OPATtern? <label_name> The OPATtern query returns the pattern specification for a given label name. Returned Format [:MACHine{1|2}:SLISt:OPATtern] <label_name>,<label_pattern><NL> Example OUTPUT XXX;":MACHINE1:SLIST:OPATTERN? ’A’" OSEarch Com...
Page 268 - OTAG
OTAG Command :MACHine{1|2}:SLISt:OTAG{<time_value>|<state_value>} The OTAG command specifies the tag value on which the O Marker should beplaced. The tag value is time when time tagging is on, or states when statetagging is on. If the data is not valid tagged data, no action is performed...
Page 269 - OVERlay
OVERlay Command :MACHine{1|2}:SLISt:OVERlay<col_num>,<module_num>,MACHine{1|2},<label_name> The OVERlay command allows you to add time-correlated labels from theother analyzer to the state listing. <col_num> integer from 1 to 61 <module_num> 1 (2 through 10 not used) &l...
Page 271 - TMAXimum; TAVerage
TAVerage Query :MACHine{1|2}:SLISt:TAVerage? The TAVerage query returns the value of the average time between the Xand 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 markerswas successful, resulting in valid...
Page 272 - VRUNs; TMINimum
TMINimum Query :MACHine{1|2}:SLISt:TMINimum? The TMINimum query returns the value of the minimum time between the Xand O markers. If data is not valid, the query returns 9.9E37. Returned Format [:MACHine{1|2}:SLISt:TMINimum] <time_value><NL> <time_value> real number Example OUTPUT ...
Page 273 - XOTag
XOTag Query :MACHine{1|2}:SLISt:XOTag? The XOTag query returns the time from the X to the O marker when markermode is time or the number of states from the X to the O marker whenmarker mode is state. If there is no data in the time mode the query returns9.9E37. If there is no data in the state mode,...
Page 274 - XPATtern
XPATtern Command :MACHine{1|2}:SLISt:XPATtern<label_name>,<label_pattern> The XPATtern command allows you to construct a pattern recognizer termfor the X marker which is then used with the XSEarch criteria when movingthe marker on patterns. Since this command deals with only one label at...
Page 275 - The XSEarch query returns the search criteria for the X marker.; XSEarch
XSEarch Command :MACHine{1|2}:SLISt:XSEarch <occurrence>,<origin> The XSEarch command defines the search criteria for the X marker, which isthen used with the associated XPATtern recognizer specification whenmoving the markers on patterns. The origin parameter tells the markerto begin a ...
Page 276 - XTAG
Example OUTPUT XXX;":MACHINE1:SLIST:XSTATE?" XTAG Command :MACHine{1|2}:SLISt:XTAG{<time_value>|<state_value>} The XTAG command specifies the tag value on which the X marker should beplaced. The tag value is time when time tagging is on or states when statetagging is on. If the d...
Page 277 - SWAVeform Subsystem
Page 280 - SWAVeform Subsystem Parameter Values; SWAVeform
Table 18-1 SWAVeform Subsystem Parameter Values Parameter Value number_of_samples integer from -1032192 to +1032192 label_name string of up to 6 alphanumeric characters bit_id {OVERlay|<bit_num>|ALL} bit_num integer representing a label bit from 0 to 31 range_values integer from 10 to 5000 (re...
Page 281 - ACCumulate
ACCumulate Command :MACHine{1|2}:SWAVeform:ACCumulate{{ON|1}|{OFF|0}} The ACCumulate command allows you to control whether the waveformdisplay gets erased between individual runs or whether subsequentwaveforms are displayed over the previous waveforms. Example OUTPUT XXX;":MACHINE1:SWAVEFORM:ACC...
Page 282 - CENTer
Query MACHine{1|2}:SWAVeform:ACQuisition? The ACQusition query returns the current acquisition mode. Returned Format [MACHine{1|2}:SWAVeform:ACQuisition] {AUTOmatic|MANual}<NL> Example OUTPUT XXX;":MACHINE2:SWAVEFORM:ACQUISITION?" CENTer Command :MACHine{1|2}:SWAVeform:CENTer <marke...
Page 283 - CLRStat
CLRStat Command :MACHine{1|2}:SWAVeform:CLRStat The CLRStat command allows you to clear the waveform statistics withouthaving to stop and restart the acquisition. Example OUTPUT XXX;":MACHINE1:SWAVEFORM:CLRSTAT" DELay Command :MACHine{1|2}:SWAVeform:DELay <number_of_samples> The DELay ...
Page 285 - The RANGe query returns the current range value.
Query :MACHine{1|2}:SWAVeform:MLENgth? The MLENgth query returns the current analyzer memory depth selection. Returned Format [:MACHine{1|2}:SWAVeform:MLENgth] <memory_length><NL> Example OUTPUT XXX;":MACHINE1:SWAVEFORM:MLENGTH?" RANGe Command MACHine{1|2}:SWAVeform:RANGe <num...
Page 289 - SCHart Subsystem
Page 290 - The commands in the SCHart subsystem are:
Introduction The State Chart subsystem provides the commands necessary forprogramming the Agilent 1670G-series logic analyzer State Chartdisplay. The commands allow you to build charts of label activity,using data normally found in the Listing display. The chart’s Y axis isused to show data values f...
Page 291 - SCHart Subsystem Parameter Values
SCHart Subsystem Syntax Diagram Table 19-1 SCHart Subsystem Parameter Values Parameter Value state_low_value integer from -1032192 to + 1032192 state_high_value integer from <state_low_value> to +1032192 label_name a string of up to 6 alphanumeric characters label_low_value string from 0 to 2 ...
Page 292 - SCHart
SCHart Selector :MACHine{1|2}:SCHart The SCHart selector is used as part of a compound header to access thesettings found in the State Chart menu. It always follows the MACHineselector because it selects a branch below the MACHine level in thecommand tree. Example OUTPUT XXX;":MACHINE1:SCHART:VA...
Page 293 - HAXis
CENTer Command MACHine{1|2}:SCHart:CENTer <marker_type> The CENTer command centers the waveform display about the specifiedmarkers. The markers are placed on the waveform in the SLISt subsystem. <marker_type> {X|O|XO|TRIGger} Example OUTPUT XXX;":MACHINE1:SCHART:CENTER XO" HAXis ...
Page 294 - VAXis
Example OUTPUT XXX;":MACHINE1:SCHART:HAXIS STATES, − 100, 100" OUTPUT XXX;":MACHINE1:SCHART:HAXIS ’READ’, ’ − 511’, ’511’, 0,300" Query MACHine{1|2}:SCHart:HAXis? The HAXis query returns the current horizontal axis label and scaling. Returned Format [:MACHine{1|2}:SCHart:HAXis] {STAt...
Page 297 - COMPare Subsystem
Page 300 - COMPare Subsystem Parameter Values; COMPare
Table 20-1 COMPare Subsystem Parameter Values Parameter Value label_name string of up to 6 characters care_spec "{*|.}..." * care . don’t care line_num integer from -245760 to +245760 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} . . ...
Page 301 - CMASk
CLEar Command :MACHine{1|2}:COMPare:CLEar The CLEar command clears all "don’t cares" in the reference listing andreplaces them with zeros except when the CLEar command immediatelyfollows the SET command (see SET command). Example OUTPUT XXX;":MACHINE2:COMPARE:CLEAR CMASk Command :MACHine...
Page 303 - a string of up to 6 alphanumeric characters
<label_name> a string of up to 6 alphanumeric characters <line_num> integer from –245760 to +245760 <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} . . . }" Example OUTPUT XXX;":MACHINE...
Page 307 - real number from
End points for the INRange and OUTRange should be at least 8 ns apart sincethis is the minimum time resolution of the time tag counter. There are two conditions which are based on a comparison of the acquiredstate data and the compare data image. You can run until one of thefollowing conditions is t...
Page 308 - SET
SET Command :MACHine{1|2}:COMPare:SET The SET command sets every state in the reference listing to "don’t cares." Ifyou send the SET command by mistake you can immediately send the CLEarcommand to restore the previous data. This is the only time the CLEarcommand will not replace "don’t c...
Page 309 - TFORmat Subsystem
Page 310 - ACQMode
Introduction The TFORmat subsystem contains the commands available for theTiming Format menu in the Agilent 1670G-series logic analyzer. Thesecommands are: • ACQMode • LABel • REMove • THReshold 21–2
Page 312 - TFORmat Subsystem Parameter Values
Table 21-1 TFORmat Subsystem Parameter Values Parameter Value <N> an integer from 1 to 8, indicating pod name string of up to 6 alphanumeric characters polarity {POSitive | NEGative} upper_bits format (integer from 0 to 65535) for a pod (pods areassigned in decreasing order) lower_bits format ...
Page 321 - TTRigger Parameter Values
Table 22-1 TTRigger Parameter Values Parameter Value branch_qualifier <qualifier> to_level_num integer from 1 to last level proceed_qualifier <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...
Page 328 - RANGE 2; In the first level, the operators you can use are
Terms A through E, RANGE 1, and EDGE1 must be grouped together and terms F, G, RANGE 2 , and EDGE2 , and 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 G)) is not allowed because th...
Page 329 - EDGE; For 16 bits assigned:
EDGE Command :MACHine{1|2}:TTRigger:EDGE<N> <label_name>,<edge_spec> The EDGE command defines edge specifications for a given label. Edgespecifications can be R (rising), F (falling), E (either), or "." (don’t care). Edges are sent in the same string with the rightmost stri...
Page 334 - SPERiod
Query :MACHine{1|2}:TTRigger:SEQuence? The SEQuence query returns the current sequence specification. Returned Format [:MACHine{1|2}:TTRigger:SEQuence] <number_of_levels>, <level_of_trigger><NL> Example OUTPUT XXX;":MACHINE1:TTRIGGER:SEQUENCE?" SPERiod Command :MACHine{1|2}...
Page 339 - TWAVeform Subsystem
Page 344 - TWAVeform Parameter Values
Table 23-1 TWAVeform Parameter Values Parameter Value delay_value real number between -2500 s and +2500 s module_spec 1 bit_id integer from 0 to 31 label_name string of up to 6 alphanumeric characters label_pattern "{#B{0|1|X} . . . |#Q{0|1|2|3|4|5|6|7|X} . . . | #H{0|1|2|3|4|5|6|7|8|9|A|B|C|D|E...
Page 345 - or; TWAVeform
TWAVeform Selector :MACHine{1|2}:TWAVeform The TWAVeform selector is used as part of a compound header to access thesettings found in the Timing Waveforms menu. It always follows theMACHine selector because it selects a branch below the MACHine level in thecommand tree. Example OUTPUT XXX;":MACH...
Page 350 - OCONdition
MMODe (Marker Mode) Command :MACHine{1|2}:TWAVeform:MMODe{OFF|PATTern|TIME|MSTats} The MMODe command selects the mode controlling marker movement andthe display of the marker readouts. When PATTern is selected, the markerswill be placed on patterns. When TIME is selected, the markers move basedon ti...
Page 353 - The OSEarch query returns the search criteria for the O marker.
Query :MACHine{1|2}:TWAVeform:OSEarch? The OSEarch query returns the search criteria for the O marker. Returned Format [:MACHine{1|2}:TWAVeform:OSEarch] <occurrence>,<origin><NL> Example OUTPUT XXX;":MACHINE1:TWAVEFORM:OSEARCH?" OTIMe Command :MACHine{1|2}:TWAVeform:OTIMe &...
Page 356 - The SPERiod command sets the sample period of the timing analyzer.; The SPERiod query returns the current sample period.
SPERiod Command :MACHine{1|2}:TWAVeform:SPERiod <samp_period> The SPERiod command sets the sample period of the timing analyzer. <samp_period> real number from 4 ns to 100 us Example OUTPUT XXX;":MACHINE1:TWAVEFORM:SPERIOD 50E − 9" Query :MACHine{1|2}:TWAVeform:SPERiod? The SPERi...
Page 359 - XCONdition; The XCONdition query returns the current setting.
XCONdition Command :MACHine{1|2}:TWAVeform:XCONdition{ENTering|EXITing} The XCONdition command specifies where the X marker is placed. The Xmarker can be placed on the entry or exit point of the XPATtern when in thePATTern marker mode. Example OUTPUT XXX; ":MACHINE1:TWAVEFORM:XCONDITION ENTERING...
Page 363 - TLISt Subsystem
Page 368 - TLISt Parameter Values
Table 24-1 TLISt Parameter Values Parameter Value mod_num 1 (2 through 10 not used) col_num integer from 1 to 61 line_number integer from -1032192 to +1032192 label_name a string of up to 6 alphanumeric characters base {BINary|HEXadecimal|OCTal|DECimal|TWOS|ASCii|SYMBol|IASSembler} for labels or {AB...
Page 369 - TLISt
TLISt Selector :MACHine{1|2}:TLISt The TLISt selector is used as part of a compound header to access thosesettings normally found in the Timing Listing menu. It always follows theMACHine selector because it selects a branch directly below the MACHinelevel in the command tree. Example OUTPUT XXX;"...
Page 372 - The MMODe query returns the current marker mode selected.
Query :MACHine{1|2}:TLISt:LINE? The LINE query returns the line number for the state currently in the box atthe center of the screen. Returned Format [:MACHine{1|2}:TLISt:LINE] <line_num_mid_screen><NL> Example OUTPUT XXX;":MACHINE1:TLIST:LINE?" MMODe (Marker Mode) Command :MACHi...
Page 378 - The RUNTil query returns the current stop criteria.
The RUNTil query returns the current stop criteria. Returned Format [:MACHine{1|2}:TLISt:RUNTil] <run_until_spec><NL> Example OUTPUT XXX;":MACHINE1:TLIST:RUNTIL?" TAVerage Query :MACHine{1|2}:TLISt:TAVerage? The TAVerage query returns the value of the average time between the Xan...
Page 385 - SPA Subsystem
Page 390 - SPA Subsystem Parameter Values
Table 25-1 SPA Subsystem Parameter Values Parameter Value bucket_num 0 to (number of valid buckets - 1) high_patt <pattern> label_name a string of up to 6 alphanumeric characters low_patt <pattern> memory {4096 | 8192 | 16384 | 32768 | 65536 |131072 | 262144 | 524288 | 1032192 } o_patt &...
Page 391 - MODE
MODE Command :SPA{1|2}:MODE {OVERView|HISTogram|TINTerval} The MODE command selects which menu to display: State Overview, StateHistogram, or Time Interval. A query returns the current menu mode. Example OUTPUT XXX;":SPA1:MODE OVERView" OUTPUT XXX;":SPA2:MODE HISTogram" OUTPUT XXX;...
Page 411 - SYMBol Subsystem
Page 412 - BASE
Introduction The SYMBol subsystem contains the commands to define symbols onthe controller and download them to the Agilent 1670G-series logicanalyzer. The commands in this subsystem are: • BASE • PATTern • RANGe • REMove • WIDTh 26–2
Page 414 - SYMBol Parameter Values
Table 26-1 SYMBol Parameter Values Parameter Value 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} . . . }...
Page 415 - SYMBol
SYMBol Selector :MACHine{1|2}:SYMBol The SYMBol selector is used as a part of a compound header to access thecommands used to create symbols. It always follows the MACHine selectorbecause it selects a branch directly below the MACHine level in the commandtree. Example OUTPUT XXX;":MACHINE1:SYMBO...
Page 416 - PATTern
PATTern Command :MACHine{1|2}:SYMBol:PATTern <label_name>,<symbol_name>,<pattern_value> The PATTern command creates a pattern symbol for the specified label. Because don’t cares (X) are allowed in the pattern value, it must always beexpressed as a string. You may still use differen...
Page 418 - WIDTh
REMove Command :MACHine{1|2}:SYMBol:REMove The REMove command deletes all symbols from a specified machine. Example OUTPUT XXX;":MACHINE1:SYMBOL:REMOVE" WIDTh Command :MACHine{1|2}:SYMBol:WIDTh <label_name>,<width_value> The WIDTh command specifies the width (number of characters...
Page 419 - DATA and SETup Commands
Page 420 - Re-loading to the logic analyzer
Introduction The DATA and SETup commands are SYSTem commands that sendand receive block data between the Agilent 1670G-series logicanalyzer and a controller. Use the DATA instruction to transferacquired timing and state data, and the SETup instruction to transferinstrument configuration data. This i...
Page 421 - Data is sent to the controller in binary form.; Binary; Data Format
Data Format To understand the format of the data within the block data, keep theseimportant things 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...
Page 424 - Byte Position; Section Data; bytes - Revision Code; Section Header Description
Section Header Description The section header uses bytes 1 through 16 (this manual begins counting at1; 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 instruct...
Page 425 - indicates that data; Data Preamble Description
The values stored in the preamble represent the captured data currentlystored in this structure and not the current analyzer configuration. Forexample, the mode of the data (bytes 33 and 103) may be STATE withtagging, while the current setup of the analyzer is TIMING. The next 70 bytes are for Analy...
Page 428 - Pod positions 7 and 8 will contain invalid data for Agilent 1671G.; Acquisition Data Description
Acquisition Data Description The acquisition data section consists of a variable number of bytes dependingon the acquisition mode and the tag setting. The data is grouped in rows ofbytes with one sample from each pod in a single row. Model Clock Pod Bytes Data Bytes Total Bytes Per Row 1672G 4 bytes...
Page 430 - maximum number of valid rows); Tag Data Description
Tag Data Description If tags are enabled for one or both analyzers, the tag data follows theacquisition data. The first byte of the tag data is determined as follows: 591 + (bytes per row × maximum number of valid rows) Each row of the tag data array consists of one (single tags enabled) or two(both...
Page 433 - Oscilloscope Commands
Page 436 - AUToscale
Introduction Oscilloscope Root Level commands control the basic operation of theoscilloscope. Refer to figure 28-1 for the module level syntaxcommand diagram. The Root Level commands are: • AUToscale • DIGitize This chapter only applies to the oscilloscope option. 28-2
Page 437 - Oscilloscope Root Level Commands
Figure 28-1 Root Level Command Syntax Diagram AUToscale Command :AUToscale The AUToscale command causes the oscilloscope to automatically select thevertical sensitivity, vertical offset, trigger source, trigger level, and timebasesettings for optimum viewing of any input signals. The trigger source ...
Page 439 - DIGitize
DIGitize Command :DIGitize The DIGitize command is used to acquire waveform data for transfer overGPIB and RS-232-C. The command initiates Repetitive Run for theoscilloscope and the analyzer if it is grouped with the oscilloscope via GroupRun. If a RUNtil condition has been specified in any module, ...
Page 441 - ACQuire Subsystem
Page 442 - COUNt
Introduction The Acquire Subsystem commands are used to set up acquisitionconditions for the DIGitize command of the oscilloscope system. Thesubsystem contains commands to select the type of acquisition andthe number of averages to be taken if the average type is chosen.Refer to Figure 28-1 for the ...
Page 443 - ACQuire Parameter Values
Figure 29-1 ACQuire Subsystem Syntax Diagram Table 29-1 ACQuire Parameter Values Parameter Value count_arg {2|4|8|16|32|64|128|256} The number of averages to betaken of each time point. ACQuire Subsystem 29-3
Page 447 - CHANnel Subsystem
Page 450 - CHANnel Parameter Values; COUPling
Table 30-1 CHANnel Parameter Values Parameter Value channel_number {1|2} offset_arg a real number defining the voltage at the center of the display. Theoffset 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 >...
Page 451 - ECL
Query :CHANnel<N>:COUPling? The COUPling query returns the current input impedance for the specifiedchannel. Returned Format [:CHANnel<N>:COUPling:] {DC|AC|DCFifty}<NL> Example OUTPUT XXX;":CHANNEL1:COUPLING?" ECL Command :CHANnel<N>:ECL The ECL command sets the verti...
Page 452 - OFFSet
OFFSet Command :CHANnel<N>:OFFSet <value> The OFFSet command sets the voltage that is represented at center screenfor the selected channel. The allowable offset voltage values are shown inthe table below. The table represents values for a Probe setting of 1:1. Theoffset value is recompen...
Page 453 - PROBe
PROBe Command :CHANnel<N>:PROBe <atten> The PROBe command specifies the attenuation factor for an external probeconnected to a channel. The command changes the channel voltagereferences such as range, offset, trigger level, and automatic measurements.The actual sensitivity is not changed...
Page 455 - TTL
TTL Command :CHANnel<N>:TTL The TTL command sets the vertical range, offset, and trigger level for theselected input channel for optimum viewing of TTL signals. TTL values are: Range: 6.0 V (1.50 V per division) Offset: 2.5 V Trigger Level: 1.62 V <N> {1|2 } Example OUTPUT XXX;":CHAN...
Page 457 - DISPlay Subsystem
Page 460 - DISPlay Parameter Values
Table 31-1 DISPlay Parameter Values Parameter Value slot_# 1 or 2 1=analyzer, 2=oscilloscope. bit_id an integer from 0 to 31. channel_# 1 or 2. label_str up to five characters enclosed in single quotes making up alabel name. label_id a string of 1 alpha and 1 numeric character for theoscilloscope, o...
Page 461 - CONNect
CONNect Command :DISPlay:CONNect {{ON|1}|{OFF|0}} The CONNect command sets the Connect Dots mode. When ON, eachdisplayed sample dot will be connected to the adjacent dot by a straight line.When OFF, only the sampling points will be displayed. Example OUTPUT XXX;":DISPLAY:CONNECT ON" Query :D...
Page 464 - MINus
MINus Command :DISPlay:MINus [<module_number>,]<label>,<label> The MINus command algebraically subtracts one channel from another andinserts the resultant waveform on the display. The first parameter is anoptional module specifier, always 2 for the oscilloscope. The next twoparamet...
Page 465 - PLUS
PLUS Command :DISPlay:PLUS [<module_number>,]<label>,<label> The PLUS command algebraically adds two channels and inserts theresultant waveform to the current display. The first parameter is an optionalmodule specifier, always 2 for the oscilloscope. The next two parameters arethe ...
Page 467 - MARKer Subsystem
Page 468 - This chapter only applies to the oscilloscope option.
Introduction The oscilloscope has four markers for making time and voltagemeasurement. These measurements may be made automatically ormanually. Additional features include the run until time (RUNTil)mode and the ability to center on trigger or markers in the displayarea (CENTer) and . The RUNTil mod...
Page 471 - MARKer Parameter Values
Figure 32-1 (continued) MARKer Subsystem Syntax Diagram (continued) Table 32-1 MARKer Parameter Values Parameter Value channel_# {1|2} marker_time time in seconds lt_arg time in seconds gt_arg time in seconds inrange_gt time in seconds inrange_lt time in seconds level level in volts outrange_gt time...
Page 472 - AVOLt
AVOLt Command :MARKer:AVOLt CHANnel<N>,<level> The AVOLt command moves the A marker to the specified voltage on theindicated channel. <N> {1|2} <level> the desired marker voltage level, ± (2 × maximum offset) Example OUTPUT XXX;":MARKER:AVOLT CHANNEL1,2.75" Query :MAR...
Page 473 - level in volts of the B marker minus the A marker; BVOLt; the desired marker voltage level,
ABVolt? Query :MARKer:ABVolt? The ABVolt query returns the difference between the A marker voltage andthe B marker voltage (Vb – Va). Returned Format [:MARKer:ABVolt]<level><NL> <level> level in volts of the B marker minus the A marker Example OUTPUT XXX;":MARKER:ABVOLT?" B...
Page 474 - MSTats
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. TheCENTer command adjusts the timebase delay to cause the trace to becentered around the indicated marker (s/Div remai...
Page 475 - OAUTo
OAUTo Command :MARKer:OAUTo {MANual|CHANnel<N>,<type>,<level>,<slope>,<occurrence>} The OAUTo command specifies the automatic placement specification forthe O marker. The first parameter specifies if automarker placement is to bein the manual mode or on a specified chan...
Page 478 - SHOW
SHOW Command :MARKer:SHOW {SAMPle|MARKer} The SHOW command allows you to select either SAMPle rate or MARKerdata (when markers are enabled) to appear on the oscilloscope menus abovethe waveform area. The SAMPle rate or MARKer data appears on the channel, trigger, display,and auto-measure menus. Mark...
Page 480 - TMODe
TMODe Command :MARKer:TMODe {OFF|ON|AUTO} The TMODe command allows you to select the time marker mode. Thechoices are OFF, ON, and AUTO. When OFF, time marker measurementscannot be made. When the time markers are turned on, the X and O markerscan be moved to make time and voltage measurements. The A...
Page 481 - VMODe
VMODe Command :MARKer:VMODe {{OFF|0} | {ON|1}} The VMODe command allows you to select the voltage marker mode. Thechoices are OFF or ON. When OFF, voltage marker measurements cannot bemade. When the voltage markers are turned on, the A and B markers can bemoved to make voltage measurements. When use...
Page 484 - XAUTo
XAUTo Command :MARKer:XAUTo {MANual|CHANnel<N>,<type>,<level>,<slope>,<occurrence>} The XAUTo command specifies the automatic placement specification forthe X marker. The first parameter specifies if automarker placement is to bein the Manual mode or on a specified chan...
Page 485 - time in seconds from trigger marker to X marker
XOTime? Query :MARKer:XOTime? The XOTime query returns the time in seconds from the X marker to the Omarker. If data is not valid, the query returns 9.9E37. Returned Format [:MARKer:XOTime]<time><NL> <time> real number Example OUTPUT XXX;":MARKER:XOTIME?" XTIMe Command :MAR...
Page 487 - MEASure Subsystem
Page 489 - MEASure Parameter Values
Figure 33-1 MEASure Subsystem Syntax Diagram Table 33-1 MEASure Parameter Values Parameter Value channel_# {1|2} MEASure Subsystem 33-3
Page 495 - SOURce
SOURce Command :MEASure:SOURce CHANnel<N> The SOURce command specifies the source to be used for subsequentmeasurements. If the source is not specified, the last waveform source isassumed. <N> {1|2} Example OUTPUT XXX;":MEASURE:SOURCE CHAN1" Query :MEASure:SOURce? The SOURce quer...
Page 499 - TIMebase Subsystem
Page 500 - The commands of the TIMebase subsystem are:; This chapter applies only to the oscilloscope option.
Introduction The commands of the TIMebase Subsystem control the Timebase,Trigger Delay Time, and the Timebase Mode. If TRIGgered mode is tobe used, ensure that the trigger specifications of the TriggerSubsystem have been set. The commands of the TIMebase subsystem are: • DELay • MODe • RANGe This ch...
Page 501 - TIMebase Parameter Values
Figure 34-1 TIMebase Subsystem Syntax Diagram Table 34-1 TIMebase Parameter Values Parameter Value delay_arg delay time in seconds, from -2500 seconds through +2500 seconds. range_arg a real number from 1 ns through 5 s TIMebase Subsystem 34-3
Page 505 - TRIGger Subsystem
Page 506 - See Figure 35-1 for the TRIGger Subsystem Syntax Diagram.
Introduction The commands of the Trigger Subsystem set all the trigger conditionsnecessary for generating a trigger for the oscilloscope. Many of thecommands in the Trigger subsystem may be used in either the EDGEor the PATTern trigger mode. If a command is a valid command forthe chosen trigger mode...
Page 508 - TRIGger Parameter Values
Figure 35-1 (continued) TRIGger Subsystem Syntax Diagram (continued) Table 35-1 TRIGger Parameter Values Parameter Value channel_# An integer from 1 to 2 count_# an integer from 1 through 32000 level_value a real number from -6.0 V to +6.0 V time a real number from 20 ns through 160 ms TRIGger Subsy...
Page 509 - CONDition
CONDition Command :TRIGger:[MODE PATTern:] CONDition {ENTer|EXIT|GT,<time>|LT,<time>|RANGe,<time>,<time>} The CONDition command specifies if a trigger is to be generated on entry(ENTer) to a specific logic pattern, when exiting (EXIT) the specifiedpattern, or if a specified p...
Page 510 - real number between 20 ns and 160 ms
When LT (less than) is selected, the oscilloscope will trigger on the firsttransition that causes the pattern specification to be false, after the patternhas been true for the number of times specified by the trigger event count(DELAY command). The first event in the sequence will occur when thespec...
Page 512 - For EDGE trigger mode:; For EDGE trigger mode:; LEVel
LEVel Command For EDGE trigger mode: :TRIGger:[MODE EDGE:SOURce CHANnel<N>;]LEVel<value> For PATTern trigger mode: :TRIGger:[MODE PATTern:PATH CHANnel<N>;]LEVel<value> The LEVel command sets the trigger level voltage for the selected source orpath. This command cannot be used...
Page 514 - LOGic
LOGic Command :TRIGger:[MODE PATTern;PATH CHANnel<N>;] LOGic{HIGH|LOW|DONTcare} The LOGic command sets the logic for each trigger path in the PATTerntrigger mode. The choices are HIGH, LOW, and DONTcare. The trigger levelset by the LEVel command determines logic high and low threshold levels.A...
Page 516 - SLOPe; PATH
PATH Command :TRIGger:[MODE PATTern;]PATH CHANnel<N> The PATH command is used to select a trigger path for the subsequentLOGic and LEVel commands. This command can only be used in thePATTern trigger mode. <N> {1|2} Example OUTPUT XXX;":TRIGGER:PATH CHANNEL1" Query :TRIGger:PATH? ...
Page 517 - The SLOPe query returns the slope of the current trigger source.; The SOURce query returns the current trigger source.
Query :TRIGger:SLOPe? The SLOPe query returns the slope of the current trigger source. Returned Format [:TRIGger:SLOPe] {POSitive|NEGative}<NL> Example OUTPUT XXX;":TRIG:SOUR CHAN1;SLOP?" SOURce Command :TRIGger:[MODE EDGE;]SOURce CHANnel<N> The SOURce command is used to select t...
Page 519 - WAVeform Subsystem
Page 521 - BYTE Format; Format for Data Transfer
Format for Data Transfer There are three formats for transferring waveform data over the remoteinterface. These formats are WORD, BYTE, or ASCII. WORD and BYTE formatted waveform records are transmitted using thearbitrary block program data format specified in IEEE-488.2. When you usethis format, th...
Page 522 - WORD Format; ASCII Format
WORD Format Word data is two bytes wide with the most significant byte of each wordbeing transmitted first. In WORD format, the 15 least significant bitsrepresent the waveform data. The possible range of data is divided into32768 vertical increments. The WORD data structure for normal and averageacq...
Page 523 - Conversion from Data Value to Voltage; would result in the following calculation:; Conversion from Data Value to Trigger Point; Data Conversion
Data Conversion Data sent from the oscilloscope is raw data and must be scaled for usefulinterpretation. The values used to interpret the data are the X and Yreferences, X and Y origins, and X and Y increments. These values are readfrom the waveform preamble (see the PREamble command) or by thequeri...
Page 525 - WAVeform Parameter Values
Figure 36-3 (continued) WAVeform Subsystem Syntax Diagram (Continued) Table 36-1 WAVeform Parameter Values Parameter Value channel_# {1|2} WAVeform Subsystem Data Conversion 36-7
Page 527 - FORMat; The FORMat query returns the current format.
FORMat Command :WAVeform:FORMat {BYTE|WORD|ASCii} The FORMat command specifies the data transmission mode of waveformdata over the remote interface. See "Format for Data Transfer" earlier in thischapter for information on the formats. Example OUTPUT XXX;":WAV:FORM WORD" Query :WAVefo...
Page 529 - RECord
RECord Command :WAVeform:[SOURce CHANnel<N>;]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 entire8000-point record of the specified channel is transmitted over the bus. InWINdow mode, only th...
Page 530 - The SOURce query returns the presently selected channel.; time in seconds
Query :WAVeform:SOURce? The SOURce query returns the presently selected channel. Returned Format [:WAVeform:SOURce] CHANnel<N><NL> Example OUTPUT XXX;":WAVEFORM:SOURCE?" SPERiod? Query :WAVeform:SPERiod? The SPERiod query returns the present sampling period. The sample periodis d...
Page 535 - Pattern Generator Commands
Page 538 - Programming the Pattern Generator; Programming overview and instructions to help you get started
Programming the Pattern Generator This chapter provides you with the information needed to programthe pattern generator of the Agilent 1670G-series logic analyzer. • Programming overview and instructions to help you get started • Pattern Generator command tree • Alphabetic command-to-subsystem direc...
Page 539 - Programming Overview; Example Pattern Generator Program; Program Comments
Programming Overview This section introduces you to the basic command structure used toprogram the pattern generator. Example Pattern Generator Program A typical pattern generator program includes the following tasks: • select the pattern generator • set program parameters • define a pattern generat...
Page 540 - To select the pattern generator, use this command:; Selecting the Pattern Generator
Line 30 assigns label ’A’, positive polarity and assigns the seven leastsignificant bits of pod 5 Line 40 assigns label ’B’ and assigns all eight bits of pod 4 Line 50 removes all program lines Line 60 inserts a new line (after line 0) in the INIT SEQUENCE portion of theprogram. Line 70 inserts a ne...
Page 542 - Table 37-1 shows the alphabetical command to subsystem directory.; Alphabetical Command to Subsystem Directory
Table 37-1 shows the alphabetical command to subsystem directory. Table 37-1 Alphabetical Command to Subsystem Directory Command Where Used BASE SYMBol CLOCk FORMat COLumn SEQuence DELay FORMat EPATtern SEQuence INSert MACRo, SEQuence LABel FORMat MODe FORMat NAME MACRo PARameter MACRo PATTern SYMBo...
Page 543 - Pattern Generator Level Commands
Pattern Generator Level Commands The Pattern Generator Level Commands control the operation of patterngenerator programs. The two commands are STEP and RESume. Pattern Generator Level Syntax Diagram count = integer from 1 to 100,000 specifying the number of vectors stepped. 37–7
Page 544 - The STEP query returns the current count.; STEP
STEP Command/Query The STEP command consists of four types: the STEP Count command, theSTEP command, the the STEP query, and the STEP FSTate command. The STEP Count command specifies the vector range for the STEPcommand. The valid vector range for the STEP Count command is from 1 to100,000. The defa...
Page 545 - This example queries and prints the step count.
Query :STEP? Returned Format [STEP] <count> Example 10 DIM Sc$[100]20 OUTPUT XXX;":STEP?"30 ENTER XXX;Sc$ 40 PRINT Sc$50 END This example queries and prints the step count. STEP FSTatecommand Syntax :STEP FSTate Example OUTPUT XXX;":STEP FSTATE" Programming the Pattern Generato...
Page 546 - RESume
RESume Command When the pattern generator encounters a BREAK instruction, programexecution is halted. The RESume command allows the program to continueuntil another BREAK instruction is encountered, or until the end of theprogram is reached. Command Syntax :RESume Example OUTPUT XXX;":RESUME"...
Page 547 - FORMat Subsystem
Page 549 - Greater than 50 MHz and less than or equal to 100 MHz (GTFifty); This example queries and prints the current clock settings.
CLOCk Command/Query The CLOCk command is used to specify the clock source for the patterngenerator. The choices are INTernal or EXTernal. With an internal clocksource, the clock period must also be specified (real number value). With an external clock source, the clock frequency range must be specif...
Page 550 - The query returns the current clock out delay value.
DELay Command/Query The DELay command is used to specify the clock out delay. The clock outdelay setting allows positioning of the clock with respect to the data. Thedelay setting that corresponds to zero is uncalibrated and must be measuredby the user to determine the basic clock/data timing. Subse...
Page 551 - In half channel mode, only pods one and three are used.
LABel Command/Query The LABel command inserts a new label or modifies the contents of anexisting label. If more than 126 labels are specified, and an attempt is madeto insert another new label, the last label (bottom label) will be modified. Only 16 labels may be inserted or modified at a time. If m...
Page 552 - This example queries and prints the definition of label ’A’.
<channel assignment> a string in one of the following forms: ’#B01...’ for binary ’#Q01234567..’ for octal ’#H0123456789ABCDEF...’ for hexadecimal ’0123456789...’ for decimal. Example Full channel mode, all bits on pod 4: OUTPUT XXX;":FORMAT:LABEL ’DATA’,POS,255,255,0,0" Example Half c...
Page 553 - MODe
MODe The MODe command is used to specify either FULL or HALF channel outputmode. Half channel mode allows a higher output data rate (greater than 100MHz), but with only 20 channels per . Full channel output mode limits the maximum data rate to 100 MHz butallows use of 40 channels per . The output mo...
Page 555 - SEQuence Subsystem
Page 558 - an integer specifying the column that is to receive the new label
COLumn Command/Query The COLumn command allows you to reorder the labels in the Sequence andMacro menus and set the numerical base for each label. Label order in theFormat menu is not changed when the COLUMN command is used. The first parameter of the command specifies the column number, followedby ...
Page 559 - See next page for an example.; EPATtern
EPATtern Command/Query The EPATtern command is used to specify the event patterns used by theWAIT and IF commands. The pattern generator has three external inputqualifiers (WAIT2, WAIT1, and WAIT0). There are eight combinations of thethree input qualifiers that may be OR’ed together to create an eve...
Page 563 - Command Syntax
inserting lines as needed. The repeat loop is assigned a loop number by thesystem and is used to connect the limits of the repeat loop. Note that there are location restrictions on the use of the REPeat instruction. MACRo# The MACRo# instruction is used to invoke a previously defined user macro. The...
Page 564 - PROGram
PROGram Command/Query The PROGram command is used to modify an existing pattern generatorsequence line. The first parameter is the line number. The instruction to be modified is atthe specified line number. Note that some lines cannot be modified(SEQUENCE START and END) and some instructions can hav...
Page 566 - REPeat; The REPeat instruction allows a group of sequence states to be
REPeat The REPeat instruction allows a group of sequence states to be executed repetitively some number of times. The repeat count isspecified in the optional instruction argument parameter. The REPeat and END LOOP sequence lines cannot be modified other than bychanging the loop count. MACRo# The MA...
Page 569 - MACRo Subsystem
Page 573 - Instructions; The NOOP instruction means there is no operation for this line.; BREak; The BREak instruction causes the execution of the sequence to
INSert Command The INSert command is the basic command used to build a pattern generatormacro. This command is used to insert (or add) a macro statement after thespecified line number. The first parameter is the line number. The instruction and/or data will beinserted in the macro after the specifie...
Page 574 - SIGNal; The SIGNal instruction outputs a signal to the internal; WAIT; The WAIT instruction causes the pattern generator to stop and; The REPeat instruction allows a group of states to be executed
SIGNal The SIGNal instruction outputs a signal to the internal Intermodule Bus (IMB). This signal is used to trigger the logic analyzer. WAIT The WAIT instruction causes the pattern generator to stop and wait for the occurrence of the specified event pattern(s). The event tobe waited for by this par...
Page 576 - The query returns the user-defined macro name.
NAME Command/Query The NAME command is used to specify a name for a macro. This name willthen appear in the front panel lists and displays in place of the more generic"Macro #" string. The name cannot be used to reference the macro in programs. It is intendedfor use as a means to clarify or ...
Page 577 - The query returns the current status of a parameter and its name.; PARameter
PARameter Command/Query The PARameter command is used to enable and name parameters for amacro. The parameter name is optional, and if used, is for use on displaysand listings only. When a parameter is enabled, macro calls from thesequence can pass values to the macro. These values can then be used ...
Page 592 - Data and Setup Commands; Definition of Block Data
Data and Setup Commands The DATA and SETup commands are system commands that allow you tosend and receive instrument configuration, setup and program data to andfrom a controller in block form. This is useful for saving block data forre-loading the pattern generator. This chapter explains how to use...
Page 597 - Programming Examples
Page 600 - Making a timing analyzer measurement
Introduction This chapter contains short, usable, and tested program examplesthat cover the most asked for cases. HP BASIC 6.2. • Making a timing analyzer measurement • Making a state analyzer measurement • Making a state compare analyzer measurement • Transferring logic analyzer configuration betwe...
Page 601 - Making a Timing Analyzer Measurement
Making a Timing Analyzer Measurement This program sets up the logic analyzer to make a simple timing analyzermeasurement. This example can be used with the E2433 Logic AnalyzerTraining Board to acquire and display the output of the ripple counter. It canalso be modified to make any timing analyzer m...
Page 603 - Making a State Analyzer Measurement
Making a State Analyzer Measurement This state analyzer program selects the Agilent 1670G-series logic analyzer,displays the configuration menu, defines a state machine, displays the statetrigger menu, and sets a state trigger for multilevel triggering. This programthen starts a single acquisition m...
Page 607 - Making a State Compare Measurement
Making a State Compare Measurement This program example acquires a state listing, copies the listing to thecompare listing, acquires another state listing, and compares both listings tofind differences. This program is written so that you can run it with the E2433 Logic AnalyzerTraining Board. This ...
Page 612 - This program uses the; Transferring the Logic Analyzer Configuration
Transferring the Logic Analyzer Configuration This program uses the SYSTem:SETup ? query to transfer the logic analyzer configuration to your controller. This program also uses the SYSTem:SETup command to transfer a logic analyzer configuration from the controller backto the logic analyzer. The SYST...
Page 615 - Checking for Measurement Completion
Checking for Measurement Completion You can append this program or insert it into another program when youneed to know when a measurement is complete. If it is at the end of aprogram it will tell you when measurement is complete. If you insert it into aprogram, it will halt the program until the cur...
Page 616 - ENTER; Sending Queries to the Logic Analyzer
Sending Queries to the Logic Analyzer This program example contains the steps required to send a query to thelogic analyzer. Sending the query alone only puts the requested informationin an output buffer of the logic analyzer. You must follow the query with an ENTER statement to transfer the query r...
Page 619 - Index; Index–1
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–532767, 4–49.9E+37, 4–4::=, 4–5 , 4–5[...
Page 620 - Index–2
OVERView:HIGH, 25–9OVERView:LABel, 25–10OVERView:LOW, 25–11OVERView:OMARker, 25–13OVERView:XMARker, 25–15PACK, 12–18PATTern, 26–6PRINt, 11–10PURGe, 12–18RANGe, 14–8, 16–15, 18–9, 20–9, 22–16, 23–17, 26–7 REMove, 14–9, 15–12, 17–15, 18–10, 21–7, 23–17, 24–15, 26–8 REName, 12–19, 13–8RESource, 13–9RMO...
Page 621 - Index–3
G GET, 2–6Group execute trigger, 2–6 H HAXis command/query, 19–5HEADer command, 1–16, 11–8Headers, 1–6, 1–8, 1–11HISTogram:HSTatistic query, 25–16HISTogram:LABel command/query, 25–17HISTogram:OTHer command/query,25–18HISTogram:QUALifier command/query,25–19HISTogram:RANGe command/query,25–20HISTogram...
Page 622 - Index–4
P PACK command, 12–18Parameter syntax rules, 1–12Parameters, 1–7Parity, 3–9Parse tree, 5–8Parser, 5–3PATTern command, 26–6PON, 6–5Preamble description, 27–6PRINt command, 11–10program example sending queries to the logic analyzer, 28–18 state analyzer, 28–5state compare, 28–9SYSTem:SETup command, 28...
Page 623 - Index–5
XTAG, 17–22, 24–21XTIMe, 14–10, 23–25 Query errors, 7–5query program example, 28–18Query responses, 1–15, 4–4Question mark, 1–10QYE, 6–5 R RANGe command, 26–7RANGe command/query, 14–8, 16–15,18–9, 20–9, 22–16, 23–17Receive Data (RD), 3–4, 3–5Remote, 2–5Remote enable, 2–5REMove command, 14–9, 15–12, ...
Page 624 - Index–6
SFORmat Subsystem, 15–3SLISt Subsystem, 17–3STRigger Subsystem, 16–3, 16–4, 16–5SWAVeform Subsystem, 18–3SYMBol Subsystem, 26–3TFORmat Subsystem, 21–3TLISt Subsystem, 24–3TTRigger Subsystem, 22–3TWAVeform Subsystem, 23–3, 23–4WLISt Subsystem, 14–3 Syntax diagrams IEEE 488.2, 5–5 System commands, 4–6...