Page 1 Publication number 16555-97011 First edition, January 1997 For Safety information, Warranties, and Regulatory information, see the pages behind the Index © Copyright Hewlett-Packard Company 1987, 1990, 1993, 1994, 1997 All Rights Reserved HP 16554A, HP 16555A, and HP 16555D State/Timing Logic Analyzers...
Page 3 This guide, combined with the HP 16500/16501A Programmer’s Guide, provides you with the information WLISt Subsystem needed to program the HP 16554A and HP 16555A/D logic analyzer modules. Each module has its own reference to SFORmat Subsystem supplement the mainframe manual since not all mainframes will be configured with the same modules.
Page 4 Part 3, chapter 18, contains program examples of actual tasks that show you how to get started in programming the HP 16554A and HP 16555A/D logic analyzers. These examples are written in HP BASIC 6.2; however, the program concepts can be used in any other popular programming language.
Page 5 SYMBol Subsystem SPA Subsystem DATA and SETup Commands Programming Examples Index...
Page 7: Table Of Contents
Contents Part 1 General Information 1 Programming the HP 16554A/ HP 16555A/HP 16555D Selecting the Module 1–3 Programming the Logic Analyzer 1–3 Mainframe Commands 1–5 Command Set Organization 1–8 Module Status Reporting 1–12 MESE<N> 1–13 MESR<N> 1–15 2 Module Level Commands ARMLine 2–5...
Page 8 Contents 4 WLISt Subsystem WLISt 4–4 DELay 4–5 INSert 4–6 LINE 4–7 MINus 4–8 OSTate 4–9 OTIMe 4–9 OVERlay 4–10 PLUS 4–11 RANGe 4–12 REMove 4–12 XOTime 4–13 XSTate 4–13 XTIMe 4–14 5 SFORmat Subsystem SFORmat 5–6 CLOCk 5–6 LABel 5–7 MASTer 5–9 MODE 5–10 MOPQual 5–11...
Page 9 Contents 6 STRigger (STRace) Subsystem Qualifier 6–6 STRigger (STRace) 6–8 ACQuisition 6–8 BRANch 6–9 CLEar 6–11 FIND 6–12 MLENgth 6–13 RANGe 6–14 SEQuence 6–15 STORe 6–16 TAG 6–17 TAKenbranch 6–18 TCONtrol 6–19 TERM 6–20 TIMER 6–21 TPOSition 6–22 7 SLISt Subsystem SLISt 7–7 COLumn 7–7 CLRPattern 7–8...
Page 10 Contents XOTag 7–19 XOTime 7–19 XPATtern 7–20 XSEarch 7–21 XSTate 7–22 XTAG 7–22 8 SWAVeform Subsystem SWAVeform 8–4 ACCumulate 8–5 ACQuisition 8–5 CENTer 8–6 CLRPattern 8–6 CLRStat 8–7 DELay 8–7 INSert 8–8 MLENgth 8–8 RANGe 8–9 REMove 8–10 TAKenbranch 8–10 TPOSition 8–11 9 SCHart Subsystem SCHart 9–4...
Page 11 Contents FIND 10–8 LINE 10–9 MENU 10–9 RANGe 10–10 RUNTil 10–11 SET 10–12 11 TFORmat Subsystem TFORmat 11–4 ACQMode 11–5 LABel 11–6 REMove 11–7 THReshold 11–8 12 TTRigger (TTRace) Subsystem Qualifier 12–6 TTRigger (TTRace) 12–8 ACQuisition 12–9 BRANch 12–9 CLEar 12–12 EDGE 12–13 FIND 12–14 MLENgth 12–16...
Page 12 Contents 13 TWAVeform Subsystem TWAVeform 13–7 ACCumulate 13–7 ACQuisition 13–8 CENTer 13–9 CLRPattern 13–9 CLRStat 13–9 DELay 13–10 INSert 13–11 MLENgth 13–12 MINus 13–13 MMODe 13–14 OCONdition 13–15 OPATtern 13–16 OSEarch 13–17 OTIMe 13–18 OVERlay 13–18 PLUS 13–19 RANGe 13–20 REMove 13–20 RUNTil 13–21 SPERiod 13–22...
Page 13 Contents 14 TLISt Subsystem TLISt 14–7 COLumn 14–7 CLRPattern 14–8 DATA 14–9 LINE 14–9 MMODe 14–10 OCONdition 14–11 OPATtern 14–12 OSEarch 14–13 OSTate 14–14 OTAG 14–14 REMove 14–15 RUNTil 14–16 TAVerage 14–17 TMAXimum 14–17 TMINimum 14–18 VRUNs 14–18 XCONdition 14–19 XOTag 14–19 XOTime 14–20 XPATtern 14–20...
Page 14 Contents 16 SPA Subsystem MODE 16–7 OVERView:BUCKet 16–8 OVERView:HIGH 16–9 OVERView:LABel 16–10 OVERView:LOW 16–11 OVERView:MLENgth 16–12 OVERView:OMARker 16–13 OVERView:OVSTatistic 16–14 OVERView:XMARker 16–15 HISTogram:HSTatistic 16–16 HISTogram:LABel 16–17 HISTogram:OTHer 16–18 HISTogram:QUALifier 16–19 HISTogram:RANGe 16–20 HISTogram:TTYPe 16–21 TINTerval:AUTorange 16–22 TINTerval:QUALifier 16–23 TINTerval:TINTerval 16–24 TINTerval:TSTatistic 16–25 17 DATA and SETup Commands Introduction 17–2...
Page 15 Contents Part 3 Programming Examples 18 Programming Examples Making a Timing Analyzer Measurement 18–3 Making a State Analyzer Measurement 18–5 Making a State Compare Analyzer Measurement 18–9 Transferring the Logic Analyzer Configuration 18–14 Checking for Measurement Completion 18–18 Sending Queries to the Logic Analyzer 18–19 Index Contents–9...
Page 16 Contents–10...
Page 17: Part 1 General Information
Part 1 1 Introduction to Programming 2 Module Level Commands General Information...
Page 19: Programming The Hp 16554A/ Hp 16555A/Hp 16555D
Programming the HP 16554A/ HP 16555A/HP 16555D...
Page 20 Introduction This chapter introduces you to the basic command structure used to program the logic analyzer. Also included is an example program that sets up the timing analyzer for a basic timing measurement. Additional program examples are in chapter 18. 1–2...
Page 21: Selecting The Module
E, then the command: :SELect would select this module. For more information on the select command, refer to the HP 16500/16501A Programmer’s Guide. It is available through your HP Sales Office. Programming the Logic Analyzer A typical logic analyzer program will do the following: •...
Page 22 OUTPUT XXX;":START" The three Xs (XXX) after the "OUTPUT" statements in the previous example refer to the device address required for programming over either HP-IB or RS-232-C. Refer to your controller manual and programming language reference manual for information on initializing the interface.
Page 23: Mainframe Commands
The first five two-digit numbers identify the card type. The identification number for the HP 16554A and HP 16555A/D logic analyzers is 34. A "−1" in the first part of the string indicates no card is installed in the slot.
Page 24 The optional, second parameter specifies the desired menu in the module. The second parameter defaults to 0 if it is not specified. The query returns the currently selected and displayed menu. For the HP 16554A/HP 16555A/HP 16555D Logic Analyzers: • •...
Page 25 Programming the HP 16554A/ HP 16555A/HP 16555D Mainframe Commands STOP Command The STOP command stops the specified module. If the specified module is configured as part of an intermodule run, STOP will stop all associated modules. STARt and STOP are overlapped commands. Overlapped commands allow execution of subsequent commands while the logic analyzer operations initiated by the overlapped command are still in progress.
Page 26: Command Set Organization
Programming the HP 16554A/ HP 16555A/HP 16555D Command Set Organization Command Set Organization The command set for the HP 16554A/HP 16555A/HP 16555D is divided into module-level commands and subsystem commands. Module-level commands are listed in Chapter 2, "Module Level Commands" and each of the subsystem commands are covered in their individual chapters starting with Chapter 3, "MACHine Subsystem."...
Page 27 Programming the HP 16554A/ HP 16555A/HP 16555D Command Set Organization Figure 1-1 HP 16554A/HP 16555A/HP 16555D Command Tree 1–9...
Page 28 Programming the HP 16554A/ HP 16555A/HP 16555D Command Set Organization Table 1-1 Alphabetical Command-to-Subsystem Directory Command Where Used Command Where Used ACCumulate SCHart, SWAVeform, TWAVeform MOPQual SFORmat ACQMode TFORmat MQUal SFORmat ACQuisition STRigger, SWAVeform, TTRigger, NAME MACHine TWAVeform OCONdition TLISt, TWAVeform...
Page 29 Programming the HP 16554A/ HP 16555A/HP 16555D Command Set Organization Table 1-1, continued Alphabetical Command-to-Subsystem Directory, continued Command Where Used Command Where Used TCONtrol STRigger, TTRigger VAXis SCHart TERM STRigger, TTRigger VRUNs SLISt, TLISt, TWAVeform THReshold SFORmat, TFORmat WIDTh SYMBol...
Page 30: Module Status Reporting
Module Event Status Enable Register (MESE<N>). The MESE<N> and MESR<N> instructions are not used in conjunction with the SELect command, so they are not listed in the HP 16554A/HP 16555A/ HP 16555D’s command tree. The following descriptions of the MESE<N> and MESR<N> instructions provide the module specific information needed to enable and interpret the contents of the registers.
Page 31: Mese
Refer to table 1-2 for information about the Module Event Status register bits, bit weights, and what each bit masks for the module. Complete information for status reporting is in chapter 6 of the HP 16500/16501A Programmer’s Guide manual. {1|2|3|4|5|6|7|8|9|10} number of slot in which the module resides. 1 <N>...

Page 32 Programming the HP 16554A/ HP 16555A/HP 16555D MESE<N> Table 1-2 Module Event Status Enable Register (A "1" enables the MESR bit) Weight Enables Not used Not used Not used Not used Pattern searches failed Trigger found RNT-Run until satisfied MC-Measurement complete The Module Event Status Enable Register contains a mask value for the bits to be enabled in the Module Event Status Register (MESR).
Page 33: Mesr
Programming the HP 16554A/ HP 16555A/HP 16555D MESR<N> MESR<N> Query :MESR<N>? The MESR<N> query returns the contents of the Module Event Status register. When you read the MESR, the value returned is the total bit weights of all bits that are set at the time the register is read. Reading the register clears the Module Event Status Register.

Page 34 Programming the HP 16554A/ HP 16555A/HP 16555D MESR<N> Table 1-3 Module Event Status Register Weight Condition Not used Not used Not used Not used 1 = One or more pattern searches failed 0 = Pattern searches did not fail 1 = Trigger found...
Page 35: Module Level Commands
Module Level Commands...
Page 36 Introduction The logic analyzer module level commands access the global functions of the HP 16554A/HP 16555A/HP 16555D logic analyzer module. These commands are: • ARMLine • DBLock • MACHine • • WLISt 2–2...
Page 37 Module Level Commands Figure 2-1 Module Level Syntax Diagram 2–3...
Page 38 Module Level Commands Table 2-1 Module Level Parameter Values Parameter Type of Parameter or Command Reference machine_num MACHine{1|2} arm_parm arm parameters see chapter 3 assign_parm assignment parameters see chapter 3 level_parm level parameters see chapter 3 name_parm name parameters see chapter 3 rename_parm rename parameters see chapter 3...
Page 39: Armline
Module Level Commands ARMLine ARMLine Command :ARMLine MACHine<N> The ARMLine command selects which machine generates the arm out signal on the IMB (intermodule bus). This command is only valid when two analyzers are on. However, the query is always valid. <N>...
Page 40: Machine
Module Level Commands MACHine The UNPacked option uploads data in a format that is easy to interpret and process. The UNPacked format cannot be downloaded back into the analyzer. Example OUTPUT XXX;":DBLOCK PACKED" Query :DBLock? The DBLock query returns the current data block format selection. Returned Format [:DBLock]{PACKed | UNPacked}<NL>...
Page 41: Spa
Module Level Commands Command :SPA<N> The SPA command selects which of the two analyzers the subsequent commands or queries will refer to. SPA is also a subsystem containing commands that control the logic analyzer SPA functions. See chapter 16 for details about the SPA subsystem.
Page 42 2–8...
Page 43: Part 2 Commands
Part 2 3 MACHine Subsystem 4 WLISt Subsystem 5 SFORmat Subsystem 6 STRigger (STRace) Subsystem 7 SLISt Subsystem 8 SWAVeform Subsystem 9 SCHart Subsystem 10 COMPare 11 TFORmat Subsystem 12 TTRigger (TTRace) Subsystem 13 TWAVeform Subsystem 14 TLISt Subsystem 15 SYMBol Subsystem 16 SPA Subsystem 17 DATA and SETup Commands Commands...
Page 45: Machine Subsystem
MACHine Subsystem...
Page 46 Introduction The MACHine subsystem contains the commands that control the machine level of operation of the logic analyzer. Some of the functions are normally found in the Trigger menu. These commands are: • • LEVelarm The functions of three of these commands reside in the State/Timing Configuration menu.
Page 47 MACHine Subsystem Figure 3-1 Machine Subsystem Syntax Diagram 3–3...
Page 48: Machine
MACHine Subsystem MACHine Table 3-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 12 arm_level integer from 1 to 11 representing sequence level machine_name string of up to 10 alphanumeric characters res_id {<state_terms>|H|J} for state analyzer {<state_terms>|EDGE{1|2}} for timing analyzer...
Page 49: Arm
RUN option. If you are using an HP 16500C mainframe, you can set up OR’d Triggering by arming the module from INTermodule when intermodule is set to Group Run with OR TRIGGER.
Page 50: Assign
MACHine Subsystem ASSign ASSign Command :MACHine{1|2}:ASSign <pod_list> The ASSign command assigns pods to a particular analyzer (machine). The ASSign command will assign two pods for each pod number you specify because pods must be assigned to analyzers in pairs. NONE clears all pods from the specified analyzer (machine) and places them in the "unassigned"...
Page 51: Levelarm
MACHine Subsystem LEVelarm LEVelarm Command :MACHine{1|2}:LEVelarm <arm_level> The LEVelarm command allows you to specify the sequence level for a specified machine that will be armed by the Intermodule Bus or the other machine. This command is only valid if the specified machine is on and the arming source is not set to RUN with the ARM command.
Page 52: Name
MACHine Subsystem NAME NAME Command :MACHine{1|2}:NAME <machine_name> The NAME command allows you to assign a name of up to 10 characters to a particular analyzer (machine) for easier identification. Spaces are valid characters. string of up to 10 alphanumeric characters <machine_name>...
Page 53: Resource
MACHine Subsystem RESource {<state_terms>|H|J} for state analyzer <res_id> {<state_terms>|EDGE{1|2}} for timing analyzer string of up to 8 alphanumeric characters <new_text> <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 assigned to the specified analyzer.
Page 54: Type
MACHine Subsystem TYPE Example OUTPUT XXX;":MACHINE1:RESOURCE A,C,RANGE1" Query :MACHine{1|2}:RESOURCE? The RESource query returns the current resource terms assigned to the specified analyzer. If no resource terms are assigned, no <res_id> is returned. Returned Format [:MACHine{1|2}:RESOURCE] <res_id>[,<res_id>,...]<NL> Example OUTPUT XXX;":MACHINE1:RESOURCE?" TYPE Command :MACHine{1|2}:TYPE <analyzer type>...
Page 55 MACHine Subsystem TYPE Query :MACHine{1|2}:TYPE? The TYPE query returns the current analyzer type for the specified analyzer. Returned Format [:MACHine{1|2}:TYPE] <analyzer type><NL> Example OUTPUT XXX;":MACHINE1:TYPE?" 3–11...
Page 56 3–12...
Page 57 WLISt Subsystem...
Page 58 Introduction The commands in the WLISt (Waveforms/LISting) subsystem control the X and O marker placement on the waveforms portion of the Timing/State mixed mode display. The XSTate and OSTate queries return what states the X and O markers are on. Because the markers can only be placed on the timing waveforms, the queries return what state (state acquisition memory location) the marked pattern is stored In order to have mixed mode, one machine must be a state analyzer...
Page 59 WLISt Subsystem Figure 4-1 WLISt Subsystem Syntax Diagram 4–3...
Page 60: Wlist Subsystem Wlist
0 to 31 label_name string of up to 6 alphanumeric characters line_num_mid_screen integer from -516096 to +516096 (HP 16554A) or -1040384 to +1040384 (HP 16555A) or -2080768 to +2080768 (HP 16555D) waveform string containing <acquisition_spec>{1|2} acquisition_spec {A|B|C|D|E|F|G|H|I|J}...
Page 61: Delay
WLISt Subsystem DELay DELay Command :WLISt:DELay <delay_value> The DELay command specifies the amount of time between the timing trigger and the horizontal center of the the timing waveform display. The allowable values for delay are −2500 s to +2500 s. real number between −2500 s and +2500 s <delay_value>...
Page 62: Insert
WLISt Subsystem INSert INSert Command :WLISt:INSert [<module_spec>,]<label_name> [,{<bit_id>|OVERlay|ALL}] The INSert command inserts waveforms in the timing waveform display. The waveforms are added from top to bottom up to a maximum of 96 waveforms. Once 96 waveforms are present, each time you insert another waveform, it replaces the last waveform.
Page 63: Line
The LINE command allows you to scroll the timing analyzer listing vertically. The command specifies the state line number relative to the trigger. The analyzer then highlights the specified line at the center of the screen. integer from -516096 to +516096 (HP 16554A) <line_num_mid_ or -1040384 to +1040384 (HP 16555A) screen>...
Page 64: Minus
WLISt Subsystem MINus Query :WLISt:LINE? The LINE query returns the line number for the state currently in the data listing roll box at center screen. Returned Format [:WLISt:LINE] <line_num_mid_screen><NL> Example OUTPUT XXX;":WLIST:LINE?" MINus Command :WLISt:MINus <module_spec>,<waveform>,<waveform> The MINus command inserts time-correlated A−B (A minus B) oscilloscope waveforms on the screen.
Page 65: Ostate
WLISt Subsystem OSTate OSTate Query :WLISt:OSTate? The OSTate query returns the state where the O Marker is positioned. If data is not valid, the query returns 2147483647. Returned Format [:WLISt:OSTate] <state_num><NL> integer <state_num> Example OUTPUT XXX;":WLIST:OSTATE?" OTIMe Command :WLISt:OTIMe <time_value> The OTIMe command positions the O Marker on the timing waveforms in the mixed mode display.
Page 66: Overlay
WLISt Subsystem OVERlay Query :WLISt:OTIMe? The OTIMe query returns the O Marker position in time. If data is not valid, the query returns 9.9E37. Returned Format [:WLISt:OTIMe] <time_value><NL> Example OUTPUT XXX;":WLIST:OTIME?" OVERlay Command :WLISt:OVERlay <module_number>,<label> [,<label>]... The OVERlay command overlays two or more oscilloscope waveforms and adds the resultant waveform to the current waveform display.
Page 67: Plus
WLISt Subsystem PLUS PLUS Command :WLISt:PLUS <module_spec>,<waveform>,<waveform> The PLUS command inserts time-correlated A+B oscilloscope waveforms on the screen. The first parameter specifies which slot is the oscilloscope module. 1 through 10 refers to slots A through J. The next two parameters specify which waveforms will be added to each other.
Page 68: Range
WLISt Subsystem RANGe RANGe Command :WLISt:RANGe <time_value> The RANGe command specifies the full-screen time in the timing waveform menu. It is equivalent to ten times the seconds per division setting on the display. The allowable values for RANGe are from 10 ns to 10 ks. real number between 10 ns and 10 ks <time_range>...
Page 69: Xotime
WLISt Subsystem XOTime XOTime Query :WLISt:XOTime? The XOTime query returns the time from the X marker to the O marker. If data is not valid, the query returns 9.9E37. Returned Format [:WLISt:XOTime] <time_value><NL> real number <time_value> Example OUTPUT XXX;":WLIST:XOTIME?" XSTate Query :WLISt:XSTate? The XSTate query returns the state where the X Marker is positioned.
Page 70: Xtime
WLISt Subsystem XTIMe XTIMe Command :WLISt:XTIMe <time_value> The XTIMe command positions the X Marker on the timing waveforms in the mixed mode display. If the data is not valid, the command performs no action. real number <time_value> Example OUTPUT XXX;":WLIST:XTIME 40.0E−6" Query :WLISt:XTIMe? The XTIMe query returns the X Marker position in time.
Page 71 SFORmat Subsystem...
Page 72 Introduction The SFORmat subsystem contains the commands available for the State Format menu in the HP 16554A/HP 16555A/HP 16555D logic analyzer modules. These commands are: • CLOCk • LABel • MASTer • MODE • MOPQual • MQUal • REMove •...
Page 73 SFORmat Subsystem Figure 5-1 SFORmat Subsystem Syntax Diagram 5–3...
Page 74 SFORmat Subsystem Figure 5-1 (continued) SFORmat Subsystem Syntax Diagram (continued) 5–4...
Page 75 SFORmat Subsystem Table 5-1 SFORmat Subsystem Parameter Values Parameter Value <N> an integer from 1 to 12 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 assigned in decreasing order) upper_bits format (integer from 0 to 65535) for a pod (pods are assigned in...
Page 76: Sformat Subsystem Sformat
SFORmat Subsystem SFORmat SFORmat Selector :MACHine{1|2}:SFORmat The SFORmat (State Format) selector is used as a part of a compound header to access the settings in the State Format menu. It always follows the MACHine selector because it selects a branch directly below the MACHine level in the command tree.
Page 77: Label
SFORmat Subsystem LABel Query :MACHine{1|2}:SFORmat:CLOCk<N>? The CLOCk query returns the current clocking mode for a given pod. Returned Format [:MACHine{1|2}:SFORmat:CLOCK<N>] <clock_mode><NL> Example OUTPUT XXX; ":MACHINE1:SFORMAT:CLOCK2?" LABel Command :MACHine{1|2}:SFORmat:LABel <name>[,<polarity>, <clock_bits>, <upper_bits>,<lower_bits> [,<upper_bits>,<lower_bits>]...] The LABel command allows you to specify polarity and assign channels to new or existing labels.
Page 78 SFORmat Subsystem LABel string of up to 6 alphanumeric characters <name> <polarity> {POSitive | NEGative} format (integer from 0 to 65535) for a clock (clocks are assigned in <clock_bits> decreasing order) <upper_bits> format (integer from 0 to 65535) for a pod (pods are assigned in decreasing order) <lower_bits>...
Page 79: Master
SFORmat Subsystem 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 given machine. The master clock is used in all clocking modes (Master, Slave, and Demultiplexed). Each command deals with only one clock (J,K,L,M); therefore, a complete clock specification requires four commands, one for each clock.
Page 80: Mode
The MODE command places an HP 16555 state analyzer in either 100 MHz (normal) or 110 MHz (fast) mode. The HP 16554A has only one state analysis mode, 70 MHz. In 110-MHz mode, the h and j resource terms are not available.
Page 81: Mopqual
SFORmat Subsystem MOPQual MOPQual Command :MACHine{1|2}:SFORmat:MOPQual <clock_pair_id>, <qual_operation> The MOPQual (master operation qualifier) command allows you to specify either the AND or the OR operation between master clock qualifier pair 1/2, or between master clock qualifier pair 3/4. For example, you can specify a master clock operation qualifier 1 AND 2.
Page 82: Mqual
SFORmat Subsystem MQUal MQUal Command :MACHine{1|2}:SFORmat:MQUal <qual_num>, <clock_id>,<qual_level> The MQUal (master qualifier) command allows you to specify the level qualifier for the master clock. <qual_num> {1|2|3|4} <clock_id> {J|K|L|M} <qual_level> {OFF|LOW|HIGH} Example OUTPUT XXX;":MACHINE2:SFORMAT:MQUAL 1,J,LOW" Query :MACHine{1|2}:SFORmat:MQUal? <qual_num> The MQUal query returns the qualifier specified for the master clock. Returned Format [:MACHine{1|2}:SFORmat:MQUal] <qual_level><NL>...
Page 83: Remove
SFORmat Subsystem REMove REMove Command :MACHine{1|2}:SFORmat:REMove {<name>|ALL} The REMove command allows you to delete all labels or any one label for a given machine. string of up to 6 alphanumeric characters <name> Example OUTPUT XXX;":MACHINE1:SFORMAT:REMOVE ’A’" OUTPUT XXX;":MACHINE2:SFORMAT:REMOVE ALL" SETHold Command :MACHine{1|2}:SFORmat:SETHold <pod_num>,<set_hold_value>...
Page 84 SFORmat Subsystem SETHold an integer from 1 to 12 <pod_num> integer {0|1|2|3|4|5|6|7|8|9} representing the following setup and <set_hold_ hold values: value> Table 5-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 0 = 4.5/0.0...
Page 85: Slave
SFORmat Subsystem 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 given machine. The slave clock is only used in the Slave and Demultiplexed clocking modes. Each command deals with only one clock (J,K,L,M); therefore, a complete clock specification requires four commands, one for each clock.
Page 86: Sopqual
SFORmat Subsystem SOPQual SOPQual Command :MACHine{1|2}:SFORmat:SOPQual <clock_pair_id>, <qual_operation> The SOPQual (slave operation qualifier) command allows you to specify either the AND or the OR operation between slave clock qualifier pair 1/2, or between slave clock qualifier pair 3/4. For example you can specify a slave clock operation qualifier 1 AND 2.
Page 87: Squal
SFORmat Subsystem 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 qualifier for the slave clock. <qual_num> {1|2|3|4} <clock_id> {J|K|L|M} <qual_level> {OFF|LOW|HIGH} Example OUTPUT XXX;":MACHINE2:SFORMAT:SQUAL 1,J,LOW" Query :MACHine{1|2}:SFORmat:SQUal?<qual_num> The SQUal query returns the qualifier specified for the slave clock. Returned Format [:MACHine{1|2}:SFORmat:SQUal] <clock_id>,<qual_level><NL>...
Page 88: Threshold
SFORmat Subsystem THReshold THReshold Command :MACHine{1|2}:SFORmat:THReshold<N> {TTL|ECL|<voltage>} The THReshold command allows you to set the voltage threshold for a given pod to ECL, TTL, or a specific voltage from −6.00 V to +6.00 V in 0.05 volt increments. an integer from 1 to 12 indicating pod number <N>...
Page 89 STRigger (STRace) Subsystem...
Page 90 Introduction The STRigger subsystem contains the commands available for the State Trigger menu in the HP 16554A/HP 16555A/HP 16555D logic analyzer modules. The State Trigger subsystem will also accept the STRace selector as used in previous HP 16500-Series logic analyzer modules to eliminate the need to rewrite programs containing STRace as the selector keyword.
Page 91 STRigger (STRace) Subsystem Figure 6-1 STRigger Subsystem Syntax Diagram 6–3...
Page 92 STRigger (STRace) Subsystem Figure 6-1 (continued) STRigger Subsystem Syntax Diagram (continued) 6–4...
Page 93 0 to 100 representing percentage memory_length {4096 | 8192 | 16384 | 32768 | 65536 | 131072 | 262144 | 516096 (HP 16554A only) 524288 | 1040384 (HP 16555A only) 524288 | 1048576 | 2080768 (HP 16555D only)} 6–5...
Page 94: Strigger (Strace) Subsystem Qualifier
STRigger (STRace) Subsystem Qualifier Qualifier The qualifier for the state trigger subsystem can be terms A through J, Timer 1 and 2, and Range 1 and 2. In addition, qualifiers can be the NOT boolean function of terms, timers, and ranges. The qualifier can also be an expression or combination of expressions as shown below and figure 6-2, "Complex Qualifier,"...
Page 95 STRigger (STRace) Subsystem Qualifier <term3a> { A | NOTA } <term3b> { B | NOTB } <term3c> { C | NOTC } <term3d> { D | NOTD } <term3e> { E | NOTE } <term3f> { F | NOTF } <term3g>...
Page 96: Strigger (Strace)
STRigger (STRace) Subsystem STRigger (STRace) STRigger (STRace) Selector :MACHine{1|2}:STRigger The STRigger (STRace) (State Trigger) selector is used as a part of a compound header to access the settings found in the State Trace menu. It always follows the MACHine selector because it selects a branch directly below the MACHine level in the command tree.
Page 97: Branch
STRigger (STRace) Subsystem BRANch BRANch Command :MACHine{1|2}:STRigger:BRANch<N> <branch_qualifier>,<to_level_number> The BRANch command defines the branch qualifier for a given sequence level. When this branch qualifier is matched, it will cause the sequencer to jump to the specified sequence level. The branch qualifier functions like the "else on"...
Page 98 STRigger (STRace) Subsystem BRANch Example OUTPUT XXX;":MACHINE1:STRIGGER:BRANCH1 ’ANYSTATE’, 3" OUTPUT XXX;":MACHINE1:STRIGGER:BRANCH2 ’A’, 7" OUTPUT XXX;":MACHINE1:STRIGGER:BRANCH3 ’((A OR B) OR NOTG)’, 1" Query :MACHine{1|2}:STRigger:BRANch<N>? The BRANch query returns the current branch qualifier specification for a given sequence level. Returned Format [:MACHine{1|2}:STRigger:BRANch<N>] <branch_qualifier>,<to_level_num><NL>...
Page 99: Clear
STRigger (STRace) Subsystem CLEar Example The following example would be used to specify the complex qualifier shown in figure 6-2. 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 together and terms F through J, RANGE 2, and TIMER 2 must be grouped together.
Page 100: Find
STRigger (STRace) Subsystem 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 sequence level. When this proceed qualifier is matched the specified number of times, the sequencer will proceed to the next sequence level.
Page 101: Mlength
Valid memory depths range from 4096 states (or samples) through the maximum system memory depth minus 8192 states (HP 16554A or HP 16555A) or minus 16384 states (HP 16555D). Memory depth is affected by acquisition mode. If the <memory_length> value sent with the command is not a legal value, the closest legal setting will be used.
Page 102: Range
STRigger (STRace) Subsystem RANGe RANGe Command :MACHine{1|2}:STRigger:RANGe<N> <label_name>, <start_pattern>,<stop_pattern> The RANGe command allows you to specify a range recognizer term for the specified machine. Since a range can only be defined across one label and since a label must contain 32 or fewer bits, the value of the start pattern or stop pattern will be between (2 )−1 and 0.
Page 103: Sequence
STRigger (STRace) Subsystem SEQuence Query :MACHine{1|2}:STRigger:RANGe<N>? The RANGe query returns the range recognizer end point specifications for the range. Returned Format [:MACHine{1|2}:STRigger:RANGe<N>] <label_name>,<start_pattern>,<stop_pattern><NL> Example OUTPUT XXX;":MACHINE1:STRIGGER:RANGE1?" SEQuence Command :MACHine{1|2}:STRigger:SEQuence <num_levels>, <trig_level> The SEQuence command redefines the state analyzer trigger sequence. First, it deletes the current sequence.
Page 104: Store
STRigger (STRace) Subsystem STORe STORe Command :MACHine{1|2}:STRigger:STORe<N> <store_qualifier> The STORe command defines the store qualifier for a given sequence level. Any data matching the STORe qualifier will be stored in memory as part of the current trace data. The qualifier may be a single term or a complex expression.
Page 105: Tag
STRigger (STRace) Subsystem Command :MACHine{1|2}:STRigger:TAG {OFF|TIME| state_tag_qualifier < >} The TAG command selects the type of count tagging (state or time) to be performed during data acquisition. State tagging is indicated when the parameter is the state tag qualifier, which will be counted in the qualified state mode.
Page 106: Takenbranch
STRigger (STRace) Subsystem TAKenbranch TAKenbranch Command :MACHine{1|2}:STRigger:TAKenbranch {STORe|NOSTore} The TAKenbranch command allows you to specify whether the state causing the branch is stored or not stored for the specified machine. The states causing the branch are defined by the BRANch and FIND commands. Example OUTPUT XXX;":MACHINE2:STRIGGER:TAKENBRANCH STORE"...
Page 107: Tcontrol
STRigger (STRace) Subsystem 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 is defined by the TIMER command. There are two timers and they are available for either machine but not both machines simultaneously.
Page 108: Term
STRigger (STRace) Subsystem 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 the specified machine. Each command deals with only one label in the given term; therefore, a complete specification could require several commands. Since a label can contain 32 or fewer bits, the range of the pattern value will −...
Page 109: Timer
STRigger (STRace) Subsystem TIMER Query :MACHine{1|2}:STRigger:TERM? <term_id>, <label_name> The TERM query returns the specification of the term specified by term identification and label name. Returned Format [:MACHine{1|2}:STRAce:TERM] <term_id>,<label_name>,<pattern><NL> Example OUTPUT XXX;":MACHINE1:STRIGGER:TERM? B,’DATA’ " TIMER Command :MACHine{1|2}:STRigger:TIMER{1|2} time_value < > The TIMER command sets the time value for the specified timer. The limits of the timer are 400 ns to 500 seconds in 16 ns to 500 µs increments.
Page 110: Tposition
STRigger (STRace) Subsystem TPOSition TPOSition Command :MACHine{1|2}:STRigger:TPOSition {STARt|CENTer|END| POSTstore,<poststore >} The TPOSition (trigger position) command allows you to set the trigger at the start, center, end or at any position in the trace (poststore). Poststore is defined as 0 to 100 percent with a poststore of 100 percent being the same as start position and a poststore of 0 percent being the same as an end trace.
Page 111: Slist Subsystem
SLISt Subsystem...
Page 112 Introduction The SLISt subsystem contains the commands available for the State Listing menu in the HP 16554A/HP 16555A/HP 16555D logic analyzer modules. These commands are: • • COLumn RUNTil • • CLRPattern TAVerage • • DATA TMAXimum • • LINE TMINimum •...
Page 113 SLISt Subsystem Figure 7-1 SLISt Subsystem Syntax Diagram 7–3...
Page 114 SLISt Subsystem Figure 7-1 (continued) SLISt Subsystem Syntax Diagram (continued) 7–4...
Page 115 SLISt Subsystem Figure 7-1 (continued) SLISt Subsystem Syntax Diagram (continued) 7–5...
Page 116 {1|2|3|4|5|6|7|8|9|10} col_num integer from 1 to 61 line_number integer from -516096 to +516096 (HP 16554A) or from -1040384 to +1040384 (HP 16555A) or from -2080768 to +2080768 (HP 16555D) label_name a string of up to 6 alphanumeric characters base...
Page 117: Slist
SLISt Subsystem SLISt SLISt Selector :MACHine{1|2}:SLISt The SLISt selector is used as part of a compound header to access those settings normally found in the State Listing menu. It always follows the MACHine selector because it selects a branch directly below the MACHine level in the command tree.
Page 118: Clrpattern
SLISt Subsystem CLRPattern Query :MACHine{1|2}:SLISt:COLumn? <col_num> The COLumn query returns the column number, module slot, machine, label name, and base for the specified column. Returned Format [:MACHine{1|2}:SLISt:COLumn] <col_num>,<module_num>,MACHine{1|2}, <label_name>,<base><NL> Example OUTPUT XXX;":MACHINE1:SLIST:COLUMN? 4" CLRPattern Command :MACHine{1|2}:SLISt:CLRPattern {X|O|ALL} The CLRPattern command allows you to clear the marker patterns in the Specify Patterns menu.
Page 119: Data
The format will be the same as the one shown in the listing display. Returned Format [:MACHine{1|2}:SLISt:DATA] <line_number>,<label_name>, <pattern_string><NL> integer from -516096 to +516096 (HP 16554A) or from -1040384 to +1040384 <line_number> (HP 16555A) or from -2080768 to +2080768 (HP 16555D) string of up to 6 alphanumeric characters <label_name>...
Page 120: Mmode
SLISt Subsystem MMODe Query :MACHine{1|2}:SLISt:LINE? The LINE query returns the line number for the state currently in the box at the center of the screen. Returned Format [:MACHine{1|2}:SLISt:LINE] <line_num_mid_screen><NL> Example OUTPUT XXX;":MACHINE1:SLIST:LINE?" MMODe Command :MACHine{1|2}:SLISt:MMODe <marker_mode> The MMODe command (Marker Mode) selects the mode controlling the marker movement and the display of marker readouts.
Page 121: Opattern
SLISt Subsystem 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> The OPATtern command allows you to construct a pattern recognizer term for the O Marker which is then used with the OSEarch criteria when moving the marker on patterns.
Page 122: Osearch
0 places the marker on the selected origin. With a negative occurrence, the marker searches before the origin. With a positive occurrence, the marker searches after the origin. integer from -516096 to +516096 (HP 16554A) or from -1040384 to +1040384 <occurrence> (HP 16555A) or from -2080768 to +2080768 (HP 16555D) <origin>...
Page 123: Ostate
If data is not valid , the query returns 2147483647. Returned Format [:MACHine{1|2}:SLISt:OSTate] <state_num><NL> integer from -516096 to +516096 or 2147483647 (HP 16554A), or from <state_num> -1040384 to +1040384 or 2147483647 (HP 16555A) or from -2080768 to +2080768 or 2147483647 (HP 16555D) Example OUTPUT XXX;":MACHINE1:SLIST:OSTATE?"...
Page 124: Otag
SLISt Subsystem 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 be placed. The tag value is time when time tagging is on, or states when state tagging is on. If the data is not valid tagged data, no action is performed. real number <time_value>...
Page 125: Overlay
SLISt Subsystem 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 other modules or machines to the state listing. The added labels are interleaved with the column specified. The column must already contain a label. integer from 1 to 61 <col_num>...
Page 126: Runtil
SLISt Subsystem RUNTil RUNTil Command :MACHine{1|2}:SLISt:RUNTil <run_until_spec> The RUNTil (run until) command allows you to define a stop condition when the trace mode is repetitive. Specifying OFF causes the analyzer to make runs until either the display’s STOP field is touched or the STOP command is issued.
Page 127: Taverage
SLISt Subsystem TAVerage TAVerage Query :MACHine{1|2}:SLISt:TAVerage? The TAVerage query returns the value of the average time between the X and O Markers. If the number of valid runs is zero, the query returns 9.9E37. Valid runs are those where the pattern search for both the X and O markers was successful, resulting in valid time measurements.
Page 128: Tminimum
SLISt Subsystem TMINimum TMINimum Query :MACHine{1|2}:SLISt:TMINimum? The TMINimum query returns the value of the minimum time between the X and O Markers. If data is not valid, the query returns 9.9E37. Returned Format [:MACHine{1|2}:SLISt:TMINimum] <time_value><NL> real number <time_value> Example OUTPUT XXX;":MACHINE1:SLIST:TMINIMUM?" VRUNs Query :MACHine{1|2}:SLISt:VRUNs?
Page 129: Xotag
SLISt Subsystem XOTag XOTag Query :MACHine{1|2}:SLISt:XOTag? The XOTag query returns the time from the X to O markers when the marker mode is time, or number of states from the X to O markers when the marker mode is state. If there is no data in the time mode the query returns 9.9E37. If there is no data in the state mode, the query returns 2147483647.
Page 130: Xpattern
SLISt Subsystem XPATtern XPATtern Command :MACHine{1|2}:SLISt:XPATtern <label_name>,<label_pattern> The XPATtern command allows you to construct a pattern recognizer term for the X marker which is then used with the XSEarch criteria when moving the marker on patterns. Since this command deals with only one label at a time, a complete specification could require several invocations.
Page 131: Xsearch
An occurrence of 0 places a marker on the selected origin. integer from -516096 to +516096 (HP 16554A), or from -1040384 to <occurrence> +1040384 (HP 16555A)or from -2080768 to +2080768 (HP 16555D) <origin>...
Page 132: Xstate
If data is not valid, the query returns 2147483647. Returned Format [:MACHine{1|2}:SLISt:XSTate] <state_num><NL> integer from -516096 to +516096 or 2147483647 (HP 16554A), or from <state_num> -1040384 to +1040384 or 2147483647 (HP 16555A) or from -2080768 to +2080768 or 2147483647 (HP 16555D) Example OUTPUT XXX;":MACHINE1:SLIST:XSTATE?"...
Page 133 SLISt Subsystem XTAG Query :MACHine{1|2}:SLISt:XTAG? The XTAG query returns the X marker position in time when time tagging is on or in states when state tagging is on, regardless of whether the marker was positioned in time or through a pattern search. If data is not valid tagged data, the query returns 9.9E37 for time tagging, or returns 2147483647 for state tagging.
Page 134 7–24...
Page 135: Swaveform Subsystem
SWAVeform Subsystem...
Page 136 Introduction The commands in the State Waveform subsystem allow you to configure the display so that you can view state data as waveforms. Up to 96 channels, identified by label name and bit number, can be displayed at a time. The 12 commands in this subsystem are analogous to their counterparts in the Timing Waveform subsystem.
Page 137 SWAVeform Subsystem Figure 8-1 SWAVeform Subsystem Syntax Diagram 8–3...
Page 138: Swaveform
SWAVeform Table 8-1 SWAVeform Subsystem Parameter Values Parameter Value number_of_samples integer from -516096 to +516096 (HP 16554A) or from -1040384 to +1040384 (HP 16555A) or from -2080768 to +2080768 (HP 16555D) label_name string of up to 6 alphanumeric characters bit_id {OVERlay|<bit_num>|ALL}...
Page 139: Accumulate
SWAVeform Subsystem ACCumulate ACCumulate Command :MACHine{1|2}:SWAVeform:ACCumulate {{ON|1}|{OFF|0}} The ACCumulate command allows you to control whether the waveform display gets erased between individual runs or whether subsequent waveforms are allowed to be displayed over the previous waveforms. Example OUTPUT XXX;":MACHINE1:SWAVEFORM:ACCUMULATE ON" Query MACHine{1|2}:SWAVeform:ACCumulate? The ACCumulate query returns the current setting.
Page 140: Center
SWAVeform Subsystem CENTer Query MACHine{1|2}:SWAVeform:ACQuisition? The ACQuisition query returns the current acquisition mode. Returned Format [MACHine{1|2}:SWAVeform:ACQuisition] {AUTOmatic|MANual}<NL> Example OUTPUT XXX;":MACHINE2:SWAVEFORM:ACQUISITION?" CENTer Command :MACHine{1|2}:SWAVeform:CENTer <marker_type> The CENTer command allows you to center the waveform display about the specified markers. The markers are placed on the waveform in the SLISt subsystem.
Page 141: Clrstat
The DELay command allows you to specify the number of samples between the State trigger and the horizontal center of the screen for the waveform display. integer from -516096 to +516096 (HP 16554A) or from -1040384 to <number_of_ +1040384 (HP 16555A) or from -2080768 to +2080768 (HP 16555D) samples>...
Page 142: Insert
<memory_length> {4096 | 8192 | 16384 | 32768 | 65536 | 131072 | 262144 | 516096 (HP 16554A) | 524288 | 1040384 (HP 16555A) | 524288 | 1048576 | 2080768 (HP 16555D)} 8–8...
Page 143: Range
SWAVeform Subsystem RANGe Example OUTPUT XXX;":MACHINE1:SWAVEFORM:MLENGTH 262144" 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 <number_of_samples> The RANGe command allows you to specify the number of samples across the screen on the State Waveform display.
Page 144: Remove
SWAVeform Subsystem REMove REMove Command :MACHine{1|2}:SWAVeform:REMove The REMove command clears the waveform display before building a new display. Example OUTPUT XXX;":MACHINE1:SWAVEFORM:REMOVE" TAKenbranch Command MACHine{1|2}:SWAVeform:TAKenbranch {STORe|NOSTore} The TAKenbranch command allows you to control whether the states that cause branching are stored or not stored. This command is only available when the acquisition mode is set to manual.
Page 145: Tposition
SWAVeform Subsystem TPOSition TPOSition Command MACHine{1|2}:SWAVeform:TPOSition {STARt|CENTer|END|POSTstore,<percent>} The TPOSition command allows you to control where the trigger point is placed. The trigger point can be placed at the start, center, end, or at a percentage of post store. The post store option is the same as the User Defined option when setting the trigger point from the front panel.
Page 146 8–12...
Page 147: Schart Subsystem
SCHart Subsystem...
Page 148 Introduction The State Chart subsystem provides the commands necessary for programming the HP 16554A/HP 16555A/HP 16555D’s Chart display. The commands allow you to build charts of label activity, using data normally found in the Listing display. The chart’s Y axis is used to show data values for the label of your choice.
Page 149: State_Low_Value
±516096 (HP 16554A), ±1040384 (HP 16555A), or ±2080768 (HP 16555D) state_high_value integer from to 516096 (HP <state_low_value> 16554A), 1040384 (HP 16555A), or 2080768 (HP 16555D) label_name a string of up to 6 alphanumeric characters label_low_value string from 0 to 2 - 1 (#HFFFFFFFF)
Page 150: Schart
SCHart Subsystem SCHart SCHart Selector :MACHine{1|2}:SCHart The SCHart selector is used as part of a compound header to access the settings found in the State Chart menu. It always follows the MACHine selector because it selects a branch below the MACHine level in the command tree.
Page 151: Center
The shortform for STATES is STA. This is an intentional deviation from the normal truncation rule. integer from –516096 to +516096 (HP 16554A), or from –1040384 to <state_low_ +1040384 (HP 16555A), or from –2080768 to +2080768 (HP 16555D) value>...
Page 152: Vaxis
SCHart Subsystem 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] {STAtes,<state_low_value>, <state_high_value>|<label_name>,<label_low_value>, <label_high_value><state_low_value>,<state_high_value>} Example OUTPUT XXX;":MACHINE1:SCHART:HAXIS?" VAXis Command MACHine{1|2}:SCHart:VAXis <label_name>,<low_value>,<high_value>...
Page 153 SCHart Subsystem VAXis Query MACHine{1|2}:SCHart:VAXis? The VAXis query returns the current vertical axis label and scaling. Returned Format [:MACHine{1|2}:SCHart:VAXis] <label_name>,<low_value>, <high_value><NL> Example OUTPUT XXX;":MACHINE1:SCHART:VAXIS?" 9–7...
Page 154 9–8...
Page 155: Compare Subsystem
COMPare Subsystem...
Page 156 Introduction Commands in the state COMPare subsystem provide the ability to do a bit-by-bit comparison between the acquired state data listing and a compare data image. The commands are: • CLEar • CMASk • COPY • DATA • FIND • LINE •...
Page 157 COMPare Subsystem Figure 10-1 COMPare Subsystem Syntax Diagram 10–3...
Page 158: Compare
#Q{0|1|2|3|4|5|6|7|X} ... | #H{0|1|2|3|4|5|6|7|8|9|A|B|C|D|E|F|X} ... | {0|1|2|3|4|5|6|7|8|9} ... }" difference_occurrence integer from 1 to 122880 (HP 16554A) or 253951 (HP 16555A) or 507903 (HP 16555D) start_line integer from –122880 to +122880 (HP 16554A) or –253951 to +253951 (HP 16555A) or -507,903 to +507903 (HP 16555D)
Page 159: Clear
COMPare Subsystem CLEar CLEar Command :MACHine{1|2}:COMPare:CLEar The CLEar command clears all "don’t cares" in the reference listing and replaces them with zeros except when the CLEar command immediately follows the SET command (see SET command). Example OUTPUT XXX;":MACHINE2:COMPARE:CLEAR CMASk Command :MACHine{1|2}:COMPare:CMASk <label_name>, <care__spec>...
Page 160: Copy
COMPare Subsystem COPY COPY Command :MACHine{1|2}:COMPare:COPY The COPY command copies the current acquired State Listing for the specified machine into the Compare Listing template. This makes the current acquisition the reference listing. It does not affect the compare range or channel mask settings.
Page 161 COMPare Subsystem DATA a string of up to 6 alphanumeric characters <label_name> integer from –122880 to +122880 (HP 16554A) or –253951 to +253951 <line_num> (HP 16555A) or –507903 to +507903 (HP 16555D) <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 162: Find
Returned Format [:MACHine{1|2}:COMPare:FIND] <difference_occurrence>, <line_number><NL> integer from 1 to 122880 (HP 16554A) or 253952 (HP 16555A) or 507904 <diff_ (HP 16555D). occurrence> integer from –122880 to +122880 (HP 16554A) or –253951 to +253951 <line_number>...
Page 163: Line
The LINE command allows you to center the compare listing display about a specified line number. The Listing menu also changes so that the specified line is displayed midscreen. integer from –122880 to +122880 (HP 16554A) or –253951 to +253951 <line_num> (HP 16555A) or –507903 to +507903 (HP 16555D).
Page 164: Range
The RANGe command allows you to define the boundaries for the comparison. The range entered must be a subset of the lines in the acquisition memory. integer from –122880 to +122880 (HP 16554A) or –253951 to +253951 <start_line> (HP 16555A) or –507904 to +507904 (HP 16555D)
Page 165: Runtil
COMPare Subsystem RUNTil RUNTil Command :MACHine{1|2}:COMPare:RUNTil {OFF | LT,<value> | GT,<value> | INRange,<value>,<value> | OUTRange,<value>,<value> | EQUal | NEQual} The RUNTil (run until) command allows you to define a stop condition when the trace mode is repetitive. Specifying OFF causes the analyzer to make runs until either the display’s STOP field is touched or the STOP command is issued.
Page 166: Set
COMPare Subsystem Query :MACHine{1|2}:COMPare:RUNTil? The RUNTil query returns the current stop criteria for the comparison when running in repetitive trace mode. Returned Format [:MACHine{1|2}:COMPare:RUNTil] {OFF| LT,<value>|GT,<value>| INRange,<value>,<value>|OUTRange,<value>,<value>|EQUal|NEQual} <NL> Example OUTPUT XXX;":MACHINE2:COMPARE:RUNTIL?" Command :MACHine{1|2}:COMPare:SET The SET command sets every state in the reference listing to "don’t cares." If you send the SET command by mistake you can immediately send the CLEar command to restore the previous data.
Page 167: Tformat Subsystem
TFORmat Subsystem...
Page 168 Introduction The TFORmat subsystem contains the commands available for the Timing Format menu in the HP 16554A/HP 16555A/HP 16555D logic analyzer module. These commands are: • ACQMode • LABel • REMove • THReshold 11–2...
Page 169 TFORmat Subsystem Figure 11-1 TFORmat Subsystem Syntax Diagram 11–3...
Page 170: Tformat
TFORmat Subsystem TFORmat Table 11-1 TFORmat Subsystem Parameter Values Parameter Value <N> an integer from 1 to 12 name string of up to 6 alphanumeric characters polarity {POSitive | NEGative} upper_bits format (integer from 0 to 65535) for a pod (pods are assigned in decreasing order) lower_bits format (integer from 0 to 65535) for a pod (pods are...
Page 171: Acqmode
The ACQMode (acquisition mode) command allows you to select the acquisition mode for the timing analyzer. The options are: • conventional mode at full-channel 125 MHz (HP 16554A) or 250 MHz (HP 16555A/D) • conventional mode at half-channel 250 MHz (HP 16554A) or 500 MHz (HP 16555A/D).
Page 172: Label
TFORmat Subsystem LABel LABel Command :MACHine{1|2}:TFORmat:LABel <name>[,<polarity>, <clock_bits>,[<clock_bits>,]<upper_bits>, <lower_bits>[,<upper_bits>,<lower_bits>]...] The LABel command allows you to specify polarity and to assign channels to new or existing labels. If the specified label name does not match an existing label name, a new label will be created. The order of the pod-specification parameters is significant.
Page 173: Remove
TFORmat Subsystem REMove format (integer from 0 to 65535) for a pod (pods are assigned in decreasing <upper_bits> order) format (integer from 0 to 65535) for a pod (pods are assigned in decreasing <lower_bits> order) Example OUTPUT XXX;":MACHINE2:TFORMAT:LABEL ’STAT’,POSITIVE,0,127, 40312" OUTPUT XXX;":MACHINE2:TFORMAT:LABEL ’SIG 1’, #B11, #B0000000011111111,#B0000000000000000 "...
Page 174: Threshold
TFORmat Subsystem THReshold THReshold Command :MACHine{1|2}:TFORmat:THReshold<N> {TTL|ECL|<value>} The THReshold command allows you to set the voltage threshold for a given pod to ECL, TTL, or a specific voltage from −6.00 V to +6.00 V in 0.05 volt increments. pod number (integer from 1 to 12) <N>...
Page 175: Ttrigger (Ttrace) Subsystem
TTRigger (TTRace) Subsystem...
Page 176 Introduction The TTRigger subsystem contains the commands available for the Timing Trigger menu in the HP 16554A/HP 16555A/HP 16555D logic analyzer module. The Timing Trigger subsystem will also accept the TTRace selector as used in previous HP 16500-series logic analyzer modules to eliminate the need to rewrite programs containing TTRace as the selector keyword.
Page 177 TTRigger (TTRace) Subsystem Figure 12-1 TTRigger Subsystem Syntax Diagram 12–3...
Page 178 TTRigger (TTRace) Subsystem Figure 12-1 (continued) TTRigger Subsystem Syntax Diagram (continued) 12–4...
Page 179 8 ns to 5 s based on the sample period sample_period real number from 4 ns (HP 16554A) or 2 ns (HP 16555A/D) to 8 ms edge_spec string consisting of {E | F | R | .}...
Page 180: Qualifier
TTRigger (TTRace) Subsystem Qualifier Qualifier The qualifier for the timing trigger subsystem can be terms A through G and I, Timer 1 and 2, Range 1 and 2, and Edge 1 and 2. In addition, qualifiers can be the NOT boolean function of terms, timers, and ranges. The qualifier can also be an expression or combination of expressions as shown below and figure 12-2, "Complex Qualifier,"...
Page 181 TTRigger (TTRace) Subsystem Qualifier <term3a> { A | NOTA } <term3b> { B | NOTB } <term3c> { C | NOTC } <term3d> { D | NOTD } <term3e> { E | NOTE } <term3f> { F | NOTF } <term3g>...
Page 182: Ttrigger (Ttrace)
TTRigger (TTRace) Subsystem TTRigger (TTRace) Qualifier Rules The following rules apply to qualifiers: • Qualifiers are quoted strings and, therefore, need quotes. • Expressions are evaluated from left to right. • Parentheses are used to change the order evaluation and, therefore, are optional.
Page 183: Acquisition
TTRigger (TTRace) Subsystem ACQuisition ACQuisition Command :MACHine{1|2}:TTRigger:ACQuisition {AUTOmatic|MANual} The ACQuisition command allows you to specify the acquisition mode for the timing analyzer. Example OUTPUT XXX;":MACHINE1:TTRIGGER:ACQUISITION AUTOMATIC" Query :MACHine{1|2}:TTRigger:ACQuisition? The ACQuisition query returns the current acquisition mode specified. Returned Format [:MACHine{1|2}:TTRigger:ACQuisition] {AUTOmatic|MANual}<NL> Example OUTPUT XXX;":MACHINE1:TTRIGGER:ACQUISITION?"...
Page 184 TTRigger (TTRace) Subsystem BRANch Within the limitations shown by the syntax definitions, complex expressions may be formed using the AND and OR operators. Expressions are limited to what you could manually enter through the Timing Trigger menu. Regarding parentheses, the syntax definitions on the next page show only the required ones.
Page 185 TTRigger (TTRace) Subsystem BRANch Query :MACHine{1|2}:TTRigger:BRANch<N>? The BRANch query returns the current branch qualifier specification for a given sequence level. Returned Format [:MACHine{1|2}:TTRigger:BRANch<N>] <branch_qualifier>,<to_level_num><NL> Example OUTPUT XXX;":MACHINE1:TTRIGGER:BRANCH3?" Figure 12-2 Complex Qualifier Figure 12-2 is a front-panel representation of the complex qualifier (a Or b) Or (f Or g) Example...
Page 186: Clear
TTRigger (TTRace) Subsystem CLEar Terms A through E, RANGE 1, EDGE1, and TIMER 1 must be grouped together and terms F, G, and I, RANGE 2, EDGE2, and TIMER 2 must be grouped together. In the first level, terms from one group may not be mixed with terms from the other.
Page 187: Edge
TTRigger (TTRace) Subsystem EDGE EDGE Command :MACHine{1|2}:TTRigger:EDGE<N> <label_name>, <edge_spec> The EDGE command allows you to define edge specifications for a given label. Edge specifications can be R (rising), F (falling), E (either), or "." (don’t care). Edges are sent in the same string with the rightmost string character specifying what the rightmost bit will be.
Page 188: Find
TTRigger (TTRace) Subsystem FIND Query :MACHine{1|2}:TTRigger:EDGE<N>? <label_name> The EDGE query returns the current specification for the given label. Returned Format [:MACHine{1|2}:TTRigger:EDGE<N>] <label_name>,<edge_spec><NL> Example OUTPUT XXX;":MACHINE1:TTRIGGER:EDGE1? ’DATA’" FIND Command :MACHine{1|2}:TTRigger:FIND<N> <time_qualifier>, <condition_mode> The FIND command defines the qualifier for a given sequence level. The qualifier tells the timing analyzer when to proceed to the next sequence level.
Page 189 TTRigger (TTRace) Subsystem FIND less than real number from 8 ns to 5.00 seconds depending on sample period <duration_ time> integer from 1 to 1048575 <occurrence> Example OUTPUT XXX;":MACHINE1:TTRIGGER:FIND1 ’ANYSTATE’, GT, 10E−6" OUTPUT XXX;":MACHINE1:TTRIGGER:FIND3 ’((NOTA AND NOTB) OR G)’, OCCURRENCE, 10" Query :MACHine{1|2}:TTRigger:FIND4? The FIND query returns the current time qualifier specification for a given...
Page 190: Mlength
The MLENgth command allows you to specify the analyzer memory depth. Valid memory depths range from 4096 samples through the maximum system memory depth minus 8192 samples (HP 16554A/HP 16555A) or minus 16384 samples (HP 16555D). Memory depth is affected by acquisition mode. If the value sent with the command is not a legal value, the <memory_depth>...
Page 191: Range
TTRigger (TTRace) Subsystem RANGe RANGe Command :MACHine{1|2}:TTRigger:RANGe<N> <label_name>, <start_pattern>,<stop_pattern> The RANGe command allows you to specify a range recognizer term for the specified machine. Since a range can only be defined across one label and, since a label must contain 32 or fewer bits, the value of the start pattern or −1 and 0.
Page 192: Sequence
TTRigger (TTRace) Subsystem SEQuence SEQuence Command :MACHine{1|2}:TTRigger:SEQuence <number_of_levels> The SEQuence command defines the timing analyzer trigger sequence. First it deletes the current sequence, then it inserts the number of levels specified, with default settings. The number of levels can be between 1 and 10 when the analyzer is armed by the RUN key.
Page 193: Speriod
SPERiod Command :MACHine{1|2}:TTRigger:SPERiod <sample_period> The SPERiod command allows you to set the sample period of the timing analyzer. real number from 4 ns (HP 16554A) or 2 ns (HP 16555A/D) to 8 ms <sample_period> Example OUTPUT XXX;":MACHINE1:TTRIGGER:SPERIOD 50E−9" Query :MACHine{1|2}:TTRigger:SPERiod? The SPERiod query returns the current sample period.
Page 194: Tcontrol
TTRigger (TTRace) Subsystem TCONtrol TCONtrol Command :MACHine{1|2}:TTRigger:TCONtrol<N> <timer_num>, {OFF|STARt|PAUSe|CONTinue} The TCONtrol (timer control) command allows you to turn off, start, pause, or continue the timer for the specified level. The time value of the timer is defined by the TIMER command. integer from 1 to the number of existing sequence levels (maximum 10) <N>...
Page 195: Term
TTRigger (TTRace) Subsystem TERM TERM Command :MACHine{1|2}:TTRigger:TERM <term_id>, <label_name>,<pattern> The TERM command allows you to a specify a pattern recognizer term in the specified machine. Each command deals with only one label in the given term; therefore, a complete specification could require several commands. Since a label can contain 32 or fewer bits, the range of the pattern value will −...
Page 196: Timer
TTRigger (TTRace) Subsystem TIMER Query :MACHine{1|2}:TTRigger:TERM? <term_id>,<label_name> The TERM query returns the specification of the term indicated by term identification and label name. Returned Format [:MACHine{1|2}:TTRigger:TERM] <term_id>,<label_name>,<pattern><NL> Example OUTPUT XXX;":MACHINE1:TTRIGGER:TERM? B,’DATA’ " TIMER Command :MACHine{1|2}:TTRigger:TIMER{1|2} time_value < > The TIMER command sets the time value for the specified timer. The limits of the timer are 400 ns to 500 seconds in 16 ns to 500 µs increments.
Page 197: Tposition
(2 × sample period) or 16 ns, whichever is greater, to <time_val> (516096 × sample period)(HP 16554A) or (1040384 × sample period) (HP 16555A/D). integer from 0 to 100 representing percentage of poststore.
Page 198 12–24...
Page 199: Twaveform Subsystem
TWAVeform Subsystem...
Page 200 Introduction The TWAVeform subsystem contains the commands available for the Timing Waveforms menu in the HP 16554A/HP 16555A/HP 16555D logic analyzer module. These commands are: • • ACCumulate RANGe • • ACQuisition REMove • • CENTer RUNTil • • CLRPattern SPERiod •...
Page 201 TWAVeform Subsystem Figure 13-1 TWAVeform Subsystem Syntax Diagram 13–3...
Page 202 TWAVeform Subsystem Figure 13-1 (continued) TWAVeform Subsystem Syntax Diagram (continued) 13–4...
Page 203 TWAVeform Subsystem Figure 13-1 (continued) TWAVeform Subsystem Syntax Diagram (continued) 13–5...
Page 204 4 ns (HP 16554A) or 2 ns (HP 16555A/D) to 8 ms marker_type {X | O | XO | TRIGger} memory_length {4096 | 8192 | 16384 | 32768 | 65536 |...
Page 205: Twaveform
TWAVeform Subsystem TWAVeform TWAVeform Selector :MACHine{1|2}:TWAVeform The TWAVeform selector is used as part of a compound header to access the settings found in the Timing Waveforms menu. It always follows the MACHine selector because it selects a branch below the MACHine level in the command tree.
Page 206: Acquisition
TWAVeform Subsystem ACQuisition Query :MACHine{1|2}:TWAVeform:ACCumulate? The ACCumulate query returns the current setting. The query always shows the setting as the characters, "0" (off) or "1" (on). Returned Format [:MACHine{1|2}:TWAVeform:ACCumulate] {0|1}<NL> Example OUTPUT XXX;":MACHINE1:TWAVEFORM:ACCUMULATE?" ACQuisition Command :MACHine{1|2}:TWAVeform:ACQuisition {AUTOmatic|MANual} The ACQuisition command allows you to specify the acquisition mode for the timing analyzer.
Page 207: Center
TWAVeform Subsystem CENTer CENTer Command :MACHine{1|2}:TWAVeform:CENTer <marker_type> The CENTer command allows you to center the waveform display about the specified markers. <marker_type> {X|O|XO|TRIGger} Example OUTPUT XXX;":MACHINE1:TWAVEFORM:CENTER X" CLRPattern Command :MACHine{1|2}:TWAVeform:CLRPattern {X|O|ALL} The CLRPattern command allows you to clear the patterns in the selected Specify Patterns menu.
Page 208: Delay
TWAVeform Subsystem DELay DELay Command :MACHine{1|2}:TWAVeform:DELay <delay_value> The DELay command specifies the amount of time between the timing trigger and the horizontal center of the the timing waveform display. The allowable values for delay are −2500 s to +2500 s. real number between −2500 s and +2500 s <delay_value>...
Page 209: Insert
TWAVeform Subsystem INSert INSert Command :MACHine{1|2}:TWAVeform:INSert [<module_spec>,] <label_name>[,{<bit_id>|OVERlay|ALL}] The INSert command inserts waveforms in the timing waveform display. The waveforms are added from top to bottom up to 96 waveforms. Once 96 waveforms are present, each time you insert another waveform, it replaces the last waveform.
Page 210: Mlength
The MLENgth command allows you to specify the analyzer memory depth. Valid memory depths range from 4096 samples through the maximum system memory depth minus 8192 samples (HP 16554A/HP 16555A) or the maximum system memory depth minus 16384 (HP 16555D). Memory depth is affected by acquisition mode.
Page 211: Minus
TWAVeform Subsystem MINus Query :MACHine{1|2}:TWAVeform:MLENgth? The MLENgth query returns the current analyzer memory depth selection. Returned Format [:MACHine{1|2}:TWAVeform:MLENgth] <memory_length><NL> Example OUTPUT XXX;":MACHINE1:TWAVEFORM:MLENGTH?" MINus Command :MACHine{1|2}:TWAVeform:MINus <module_spec>,<waveform>,<waveform> The MINus command inserts time-correlated A−B (A minus B) oscilloscope waveforms on the display. The first parameter specifies where the oscilloscope master card resides, where 1 through 10 refers to slots A through J.
Page 212: Mmode
TWAVeform Subsystem MMODe MMODe Command :MACHine{1|2}:TWAVeform:MMODe {OFF|PATTern|TIME|MSTats} The MMODe (Marker Mode) command selects the mode controlling marker movement and the display of the marker readouts. When PATTern is selected, the markers will be placed on patterns. When TIME is selected, the markers move on time.
Page 213: Ocondition
TWAVeform Subsystem OCONdition OCONdition Command :MACHine{1|2}:TWAVeform:OCONdition {ENTering|EXITing} The OCONdition command specifies where the O marker is placed. The O marker can be placed on the entry or exit point of the OPATtern when in the PATTern marker mode. Example OUTPUT XXX; ":MACHINE1:TWAVEFORM:OCONDITION ENTERING" Query :MACHine{1|2}:TWAVeform:OCONdition? The OCONdition query returns the current setting.
Page 214: Opattern
TWAVeform Subsystem OPATtern OPATtern Command :MACHine{1|2}:TWAVeform:OPATtern <label_name>, <label_pattern> The OPATtern command allows you to construct a pattern recognizer term for the O marker which is then used with the OSEarch criteria and OCONdition when moving the marker on patterns. Since this command deals with only one label at a time, a complete specification could require several invocations.
Page 215: Osearch
With a positive occurrence, the marker searches after the origin. <origin> {STARt|TRIGger|XMARker} integer from −1040384 to +1040384 (HP 16554A) or from −2088960 to <occurrence> +2088960 (HP 16555A) or from –4177920 to +4177920 (HP 16555D) Example OUTPUT XXX;...
Page 216: Otime
TWAVeform Subsystem OTIMe OTIMe Command :MACHine{1|2}:TWAVeform:OTIMe <time_value> The OTIMe command positions the O marker in time when the marker mode is TIME. If data is not valid, the command performs no action. real number −2.5 ks to +2.5 ks <time_value> Example OUTPUT XXX;...
Page 217: Plus
TWAVeform Subsystem PLUS <module_spec> {1|2|3|4|5|6|7|8|9|10} string containing <acquisition_spec>{1|2} <waveform> {A|B|C|D|E|F|G|H|I|J} (slot where acquisition card is located) <acquisition_ spec> Example OUTPUT XXX;":MACHINE1:TWAVEFORM:OVERLAY 3, ’C1’,’C2’" PLUS Command :MACHine{1|2}:TWAVeform:PLUS <module_spec>, <waveform>, <waveform> The PLUS command inserts time-correlated A+B oscilloscope waveforms on the screen. The first parameter specifies the slot where the oscilloscope module resides.
Page 218: Range
TWAVeform Subsystem RANGe RANGe Command :MACHine{1|2}:TWAVeform:RANGe <time_value> The RANGe command specifies the full-screen time in the timing waveform menu. It is equivalent to ten times the sec/Div setting on the display. The allowable values for RANGe are from 10 ns to 10 ks. real number between 10 ns and 10 ks <time_range>...
Page 219: Runtil
TWAVeform Subsystem RUNTil RUNTil Command :MACHine{1|2}:TWAVeform:RUNTil <run_until_spec> The RUNTil (run until) command defines stop criteria based on the time between the X and O markers when the trace mode is in repetitive. When OFF is selected, the analyzer will run until either the STOP touch screen field is touched, or, the STOP command is sent.
Page 220: Speriod
SPERiod Command :MACHine{1|2}:TWAVeform:SPERiod <sample_period> The SPERiod command allows you to set the sample period of the timing analyzer. real number from 4 ns (HP 16554A) or 2 ns (HP 16555A/D) to 8 ms <sample_period> Example OUTPUT XXX;":MACHINE1:TWAVEFORM:SPERIOD 50E−9" Query :MACHine{1|2}:TWAVeform:SPERiod? The SPERiod query returns the current sample period.
Page 221: Taverage
TWAVeform Subsystem TAVerage TAVerage Query :MACHine{1|2}:TWAVeform:TAVerage? The TAVerage query returns the value of the average time between the X and O markers. If there is no valid data, the query returns 9.9E37. Returned Format [:MACHine{1|2}:TWAVeform:TAVerage] <time_value><NL> real number <time_value> Example OUTPUT XXX;":MACHINE1:TWAVEFORM:TAVERAGE?"...
Page 222: Tminimum
TWAVeform Subsystem TMINimum TMINimum Query :MACHine{1|2}:TWAVeform:TMINimum? The TMINimum query returns the value of the minimum time between the X and O markers. If there is no valid data, the query returns 9.9E37. Returned Format [:MACHine{1|2}:TWAVeform:TMINimum] <time_value><NL> real number <time_value> Example OUTPUT XXX;":MACHINE1:TWAVEFORM:TMINIMUM?"...
Page 223: Vruns
TWAVeform Subsystem VRUNs Query MACHine{1|2}:TWAVeform:TPOSition? The TPOSition query returns the current trigger setting. Returned Format [MACHine{1|2}:TWAVeform:TPOSition] {STARt|CENTer|END|DELay, <time_val>| POSTstore,<percent>}<NL> Example OUTPUT XXX;":MACHINE2:TWAVEFORM:TPOSition?" VRUNs Query :MACHine{1|2}:TWAVeform:VRUNs? The VRUNs query returns the number of valid runs and total number of runs made. Valid runs are those where the pattern search for both the X and O markers was successful resulting in valid time measurements.
Page 224: Xcondition
TWAVeform Subsystem XCONdition XCONdition Command :MACHine{1|2}:TWAVeform:XCONdition {ENTering | EXITing} The XCONdition command specifies where the X marker is placed. The X marker can be placed on the entry or exit point of the XPATtern when in the PATTern marker mode. Example OUTPUT XXX;...
Page 225: Xpattern
TWAVeform Subsystem XPATtern XPATtern Command :MACHine{1|2}:TWAVeform:XPATtern <label_name>,<label_pattern> The XPATtern command allows you to construct a pattern for the X marker which is then used with the XSEarch criteria and XCONdition when moving the marker on patterns. Since this command deals with only one label at a time, a complete specification could require several iterations.
Page 226: Xsearch
An occurrence of 0 places a marker on the origin. <origin> {TRIGger|STARt} integer from from −1040384 to +1040384 (HP 16554A) or from –2088960 to <occurrence> +2088960(HP 16555A) or from –4177920 to +4177920(HP 16555D) Example OUTPUT XXX;...
Page 227: Xtime
TWAVeform Subsystem XTIMe XTIMe Command :MACHine{1|2}:TWAVeform:XTIMe <time_value> The XTIMe command positions the X marker in time when the marker mode is time. If data is not valid, the command performs no action. real number from −2.5 ks to +2.5 ks <time_value>...
Page 228 13–30...
Page 229: Tlist Subsystem
TLISt Subsystem...
Page 230 Introduction The TLISt subsystem contains the commands available for the Timing Listing menu in the HP 16554A/HP 16555A/HP 16555D logic analyzer modules and is the same as the SLISt subsystem (except for the OCONdition and XCONdition commands). The TLISt subsystem commands are: •...
Page 231 TLISt Subsystem Figure 14-1 TLISt Subsystem Syntax Diagram 14–3...
Page 232 TLISt Subsystem Figure 14-1 (continued) TLISt Subsystem Syntax Diagram (continued) 14–4...
Page 233 TLISt Subsystem Figure 14-1 (continued) TLISt Subsystem Syntax Diagram (continued) 14–5...
Page 234 {1|2|3|4|5|6|7|8|9|10} mach_num {1|2} col_num integer from 1 to 61 line_number integer between ±1040384 (HP 16554A), or ±2088960 (HP 16555A) or ±4177920 (HP 16555D) label_name a string of up to 6 alphanumeric characters base {BINary|HEXadecimal|OCTal|DECimal|TWOS |ASCii|SYMBol} for labels or {ABSolute|RELative} for tags integer between ±1040384 (HP 16554A), or ±2088960...
Page 235: Tlist
TLISt Subsystem TLISt TLISt Selector :MACHine{1|2}:TLISt The TLISt selector is used as part of a compound header to access those settings normally found in the Timing Listing menu. It always follows the MACHine selector because it selects a branch directly below the MACHine level in the command tree.
Page 236: Clrpattern
TLISt Subsystem CLRPattern Example OUTPUT XXX;":MACHINE1:TLIST:COLUMN 4,2,’A’,HEX" Query :MACHine{1|2}:TLISt:COLumn? <col_num> The COLumn query returns the column number, data source, label name, and base for the specified column. Returned Format [:MACHine{1|2}:TLISt:COLumn] <col_num>,<module_num>,MACHine{1|2},<label_name>,<base><NL> Example OUTPUT XXX;":MACHINE1:TLIST:COLUMN? 4" CLRPattern Command :MACHine{1|2}:TLISt:CLRPattern {X|O|ALL} The CLRPattern command allows you to clear the patterns for the selected markers in the Specify Patterns menu.
Page 237: Data
The base will be the same as the one shown in the Listing display. Returned Format [:MACHine{1|2}:TLISt:DATA] <line_number>,<label_name>, <pattern_string><NL> integer from –1040384 to +1040384 (HP 16554A) or from –2088960 to <line_number> +2088960 (HP 16555A) or from –4177920 to +4177920 (HP 16555D) string of up to 6 alphanumeric characters <label_name>...
Page 238: Mmode
TLISt Subsystem MMODe Query :MACHine{1|2}:TLISt:LINE? The LINE query returns the line number for the state currently in the data roll box at the center of the screen. Returned Format [:MACHine{1|2}:TLISt:LINE] <line_num_mid_screen><NL> Example OUTPUT XXX;":MACHINE1:TLIST:LINE?" MMODe Command :MACHine{1|2}:TLISt:MMODe <marker_mode> The MMODe command (Marker Mode) selects the mode controlling the marker movement and the display of marker readouts.
Page 239: Ocondition
TLISt Subsystem OCONdition OCONdition Command :MACHine{1|2}:TLISt:OCONdition {ENTering|EXITing} The OCONdition command specifies where the O marker is placed. The O marker can be placed on the entry or exit point of the OPATtern when in the PATTern marker mode. Example OUTPUT XXX; ":MACHINE1:TLIST:OCONDITION ENTERING" Query :MACHine{1|2}:TLISt:OCONdition? The OCONdition query returns the current setting.
Page 240: Opattern
TLISt Subsystem OPATtern OPATtern Command :MACHine{1|2}:TLISt:OPATtern <label_name>, <label_pattern> The OPATtern command allows you to construct a pattern for the O marker which is then used with the OSEarch criteria when moving the marker on patterns. Since this command deals with only one label at a time, a complete specification could require several iterations.
Page 241: Osearch
With a negative occurrence, the marker searches before the origin. With a positive occurrence, the marker searches after the origin. integer from –1040384 to +1040384 (HP 16554A) or from –2088960 to <occurrence> +2088960 (HP 16555A) or from –4177920 to +4177920 (HP 16555D) <origin>...
Page 242: Ostate
The OSTate query returns the line number in the listing where the O marker resides. If data is not valid, the query returns 2147483647. Returned Format [:MACHine{1|2}:TLISt:OSTate] <state_num><NL> 2147483647 or integer from –1040384 to +1040384 (HP 16554A) or from <state_num> –2088960 to +2088960 (HP 16555A) or from –4177920 to +4177920 (HP 16555D) Example OUTPUT XXX;":MACHINE1:TLIST:OSTATE?"...
Page 243: Remove
TLISt Subsystem REMove Query :MACHine{1|2}:TLISt:OTAG? The OTAG query returns the O marker position in time regardless of whether the marker was positioned in time or through a pattern search. If data is not valid, the query returns 9.9E37. Returned Format [:MACHine{1|2}:TLISt:OTAG] <time_value><NL>...
Page 244: Runtil
TLISt Subsystem RUNTil RUNTil Command :MACHine{1|2}:TLISt:RUNTil <run_until_spec> The RUNTil (run until) command allows you to define a stop condition when the run mode is repetitive. Specifying OFF causes the analyzer to make runs until either the display’s STOP field is touched or the STOP command is issued.
Page 245: Taverage
TLISt Subsystem TAVerage TAVerage Query :MACHine{1|2}:TLISt:TAVerage? The TAVerage query returns the value of the average time between the X and O markers. If the number of valid runs is zero, the query returns 9.9E37. Valid runs are those where the pattern search for both the X and O markers was successful, resulting in valid time measurements.
Page 246: Tminimum
TLISt Subsystem TMINimum TMINimum Query :MACHine{1|2}:TLISt:TMINimum? The TMINimum query returns the value of the minimum time between the X and O markers. If data is not valid, the query returns 9.9E37. Returned Format [:MACHine{1|2}:TLISt:TMINimum] <time_value><NL> real number <time_value> Example OUTPUT XXX;":MACHINE1:TLIST:TMINIMUM?" VRUNs Query :MACHine{1|2}:TLISt:VRUNs?
Page 247: Xcondition
TLISt Subsystem XCONdition XCONdition Command :MACHine{1|2}:TLISt:XCONdition {ENTering|EXITing} The XCONdition command specifies where the X marker is placed. The X marker can be placed on the entry or exit point of the XPATtern when in the PATTern marker mode. Example OUTPUT XXX; ":MACHINE1:TLIST:XCONDITION ENTERING" Query :MACHine{1|2}:TLISt:XCONdition? The XCONdition query returns the current setting.
Page 248: Xotime
TLISt Subsystem XOTime XOTime Query :MACHine{1|2}:TLISt:XOTime? The XOTime query returns the time from the X to O markers. If there is no data the query returns 9.9E37. Returned Format [:MACHine{1|2}:TLISt:XOTime] <XO_time><NL> real number <XO_time> Example OUTPUT XXX;":MACHINE1:TLIST:XOTIME?" XPATtern Command :MACHine{1|2}:TLISt:XPATtern <label_name>, <label_pattern>...
Page 249: Xsearch
X pattern, relative to the origin, the marker actually searches for. An occurrence of 0 places a marker on the selected origin. integer from –1040384 to +1040384 (HP 16554A) or from –2088960 to <occurrence> +2088960 (HP 16555A) or from –4177920 to +4177920 (HP 16555D) <origin>...
Page 250: Xstate
The XSTate query returns the line number in the listing where the X marker resides. If data is not valid, the query returns 2147483647. Returned Format [:MACHine{1|2}:TLISt:XSTate] <state_num><NL> 2147483647 or integer from –1040384 to +1040384 (HP 16554A) or from <state_num> –2088960 to +2088960 (HP 16555A) or from –4177920 to +4177920 (HP 16555D).
Page 251: Xtag
TLISt Subsystem XTAG XTAG Command :MACHine{1|2}:TLISt:XTAG <time_value> The XTAG command specifies the tag value on which the X marker should be placed. The tag value is always time for the timing analyzer. If the data is not valid tagged data, no action is performed. real number <time_value>...
Page 252 14–24...
Page 253: Symbol Subsystem
SYMBol Subsystem...
Page 254 Introduction The SYMBol subsystem contains the commands that allow you to define symbols on the controller and download them to the HP 16554A/HP 16555A/HP 16555D logic analyzer modules. The commands in this subsystem are: • BASE • PATTern • RANGe •...
Page 255 SYMBol Subsystem Figure 15-1 SYMBol Subsystem Syntax Diagram 15–3...
Page 256 SYMBol Subsystem Table 15-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}...}" start_value "{#B{0|1}...| stop_value #Q{0|1|2|3|4|5|6|7}...| #H{0|1|2|3|4|5|6|7|8|9|A|B|C|D|E|F}...| {0|1|2|3|4|5|6|7|8|9}...}" width_value integer from 1 to 16 15–4...
Page 257: Symbol
SYMBol Subsystem SYMBol SYMBol Selector :MACHine{1|2}:SYMBol The SYMBol selector is used as a part of a compound header to access the commands used to create symbols. It always follows the MACHine selector because it selects a branch directly below the MACHine level in the command tree.
Page 258: Pattern
SYMBol Subsystem PATTern PATTern Command :MACHine{1|2}:SYMBol:PATTern <label_name>, <symbol_name>,<pattern_value> The PATTern command allows you to create a pattern symbol for the specified label. Because don’t cares (X) are allowed in the pattern value, it must always be expressed as a string. The values may be in binary (#B), octal (#Q), hexadecimal (#H), or decimal (default).
Page 259: Range
SYMBol Subsystem RANGe RANGe Command :MACHine{1|2}:SYMBol:RANGe <label_name>, <symbol_name>,<start_value>,<stop_value> The RANGe command allows you to create a range symbol containing a start value and a stop value for the specified label. The values may be in binary (#B), octal (#Q), hexadecimal (#H) or decimal (default). You can not use don’t cares in any base.
Page 260: Remove
SYMBol Subsystem REMove 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) in which the symbol names will be displayed when symbols are used. The WIDTh command does not affect the displayed length of the symbol offset value.
Page 261: Spa Subsystem
SPA Subsystem...
Page 262 Introduction This chapter provides you with information for programming the System Performance Analysis (SPA) features on the HP 16554A/ HP 16555A/HP 16555D logic analyzer modules. SPA commands have subsystems, indicated by the outdented items in the list. Indented commands must be prefaced with the outdented command above it unless MODE was previously used to set the mode.
Page 263 SPA Subsystem Figure 16-1 SPA Subsystem Syntax Diagram 16–3...
Page 264 SPA Subsystem Figure 16-1 (continued) SPA Subsystem Syntax Diagram (continued) 16–4...
Page 265 SPA Subsystem Figure 16-1 (continued) SPA Subsystem Syntax Diagram (continued) 16–5...
Page 266 <pattern> memory {4096 | 8192 | 16384 | 32768 | 65536 | 131072 | 262144 | 516096 (HP 16554A) 524288 | 1040384 (HP 16555A) 524288 | 1048576 | 2080768 (HP 16555D)} o_patt <pattern> x_patt <pattern> range_num an integer from 0 to 10...
Page 267: Mode
SPA Subsystem MODE MODE Command :SPA{1|2}:MODE {OVERView|HISTogram|TINTerval} The MODE command selects which menu to display: State Overview, State Histogram, or Time Interval. A query returns the current menu mode. Example OUTPUT XXX;":SPA1:MODE OVERView" OUTPUT XXX;":SPA2:MODE HISTogram" OUTPUT XXX;":SPA1:MODE TINTerval" Query :SPA{1|2}:MODE? Returned Format [:SPA{1|2}:MODE] {OVERView|HISTogram|TINTerval}<NL>...
Page 268: Overview:bucket
SPA Subsystem OVERView:BUCKet OVERView:BUCKet Query :SPA{1|2}:OVERView:BUCKet? {SIZE|NUMBer|<bucket_num>} The OVERView:BUCKet query returns data relating to the State Overview measurement. You specify SIZE for width of each bucket, NUMBer for number of buckets, or for the number of hits in the specified <bucket_num>...
Page 269: Overview:high
SPA Subsystem OVERView:HIGH OVERView:HIGH Command :SPA{1|2}:OVERView:HIGH <high_pattern> The OVERView:HIGH command sets the upper boundary of the State Overview measurement. A query returns the current setting of the upper boundary. Setting the upper boundary defaults the data accumulators, statistic counters, and the number of buckets and their size. <high_pattern>...
Page 270: Overview:label
SPA Subsystem OVERView:LABel OVERView:LABel Command :SPA{1|2}:OVERView:LABel <label_name> The OVERView:LABel command selects a new label for collecting the SPA measurements. A query returns the name of the currently selected label. Selecting a new label defaults the State Overview data accumulators, statistic counters, and the number of buckets and their size.
Page 271: Overview:low
SPA Subsystem OVERView:LOW OVERView:LOW Command :SPA{1|2}:OVERView:LOW <low_pattern> The OVERView:LOW command sets the lower boundary of the State Overview measurement. A query returns the current setting of the lower boundary. Setting the lower boundary defaults the data accumulators, statistic counters, and the number of buckets and their size. <low_pattern>...
Page 272: Overview:mlength
The MLENgth command specifies the memory depth. Valid memory depths range from 4096 states (or samples) through the maximum system memory depth minus 8192 states (HP 16554A/HP 16555A) or minus 16384 states (HP 16555D). Memory depth is affected by acquisition mode. If the value sent with the command is not a legal value, the <memory_depth>...
Page 273: Overview:omarker
SPA Subsystem OVERView:OMARker OVERView:OMARker Command :SPA{1|2}:OVERView:OMARker <o_pattern> The OVERView:OMARker command sends the O marker to the lower boundary of the bucket where the specified pattern is located. A request to place the marker outside the defined boundary forces the marker to the appropriate end bucket.
Page 274: Overview:ovstatistic
SPA Subsystem OVERView:OVSTatistic OVERView:OVSTatistic Query :SPA{1|2}:OVERView:OVSTatistic? {XHITs|OHITs|TOTal} The OVERView:OVSTatistic query returns the number of hits associated with the requested statistic or returns the number of hits in the specified bucket. XHITs requests the number of hits in the bucket where the X marker is located.
Page 275: Overview:xmarker
SPA Subsystem OVERView:XMARker OVERView:XMARker Command :SPA{1|2}:OVERView:XMARker <x_pattern> The OVERView:XMARker command sends the X marker to the lower boundary of the bucket where the specified pattern is located. A request to place the marker outside the defined boundary forces the marker to the appropriate end bucket.
Page 276: Histogram:hstatistic
SPA Subsystem HISTogram:HSTatistic HISTogram:HSTatistic Query :SPA{1|2}:HISTogram:HSTatistic? {TOTal|OTHer|<range_number>} The HISTogram:HSTatistic query returns the total number of samples or returns the number of samples in the specified range. Specify TOTal for the total number of samples, OTHer for the number of hits in "other" range, or for the number of hits in that range.
Page 277: Histogram:label
SPA Subsystem HISTogram:LABel HISTogram:LABel Command :SPA{1|2}:HISTogram:LABel <label_name> The HISTogram:LABel command selects a new label for collecting SPA measurements. A query returns the name of the currently selected label. Selecting a new label defaults the State Histogram range names, bucket sizes, and hit accumulators.
Page 278: Histogram:other
SPA Subsystem HISTogram:OTHer HISTogram:OTHer Command :SPA{1|2}:HISTogram:OTHer {INCLuded|EXCLuded} The HISTogram:OTHer command selects including or excluding the "other" histogram bucket. A query returns data indicating whether the "other" bucket is currently included or excluded. Example OUTPUT XXX;":SPA2:HISTogram:OTHer INCLuded" OUTPUT XXX;":SPA1:HISTogram:OTHer EXCLuded" Query :SPA{1|2}:HISTogram:OTHer? Returned Format [:SPA{1|2}:HISTogram:OTHer] {INCLuded|EXCLuded}<NL>...
Page 279: Histogram:qualifier
SPA Subsystem HISTogram:QUALifier HISTogram:QUALifier Command :SPA{1|2}:HISTogram:QUALifier <label_name>, <pattern> The HISTogram:QUALifier command sets the pattern associated with the specified label. The pattern is a condition for triggering and storing the measurement. A query of a label returns the current pattern setting for that label.
Page 280: Histogram:range
SPA Subsystem HISTogram:RANGe HISTogram:RANGe Command :SPA{1|2}:HISTogram:RANGe {OFF | <range_num>, <range_name>,<low_patt>,<high_patt>} The HISTogram:RANGe command turns off all ranges or defines the range name, low boundary, and high boundary of the specified range. Defining a specified range turns on that range. For the specified range, a query returns the name, low boundary, high boundary, and whether the range is on or off.
Page 281: Histogram:ttype
SPA Subsystem HISTogram:TTYPe HISTogram:TTYPe Command :SPA{1|2}:HISTogram:TTYPe {ALL|QUALified} The HISTogram:TTYPe command sets the trigger to trigger on anystate or on qualified state. A query returns the current trace type setting. Example OUTPUT XXX;":SPA2:HISTogram:TTYPe ALL" Query :SPA{1|2}:HISTogram:TTYPe? Returned Format [:SPA{1|2}:HISTogram:TTYPe] {ALL|QUALified}<NL> Example 10 DIM String$[100] 20 OUTPUT XXX;":SELECT 1"...
Page 282: Tinterval:autorange
SPA Subsystem TINTerval:AUTorange TINTerval:AUTorange Command :SPA{1|2}:TINTerval:AUTorange {LOGarithmic|LINear},<min_time>,<max_time> The TINTerval:AUTorange command automatically sets the Time Interval ranges in a logarithmic or linear distribution over the specified range of time. When the AUTorange command is executed, the data accumulators and statistic counters are reset. real number <min_time>...
Page 283: Tinterval:qualifier
SPA Subsystem TINTerval:QUALifier TINTerval:QUALifier Command :SPA{1|2}:TINTerval:QUALifier <label_name>, <start_pattern>,<end_pattern> The TINTerval:QUALifier command defines the start and stop patterns for a specified label. The start and stop patterns determine the time windows for collecting data. A query returns the currently defined start and stop patterns for a given label.
Page 284: Tinterval:tinterval
SPA Subsystem TINTerval:TINTerval TINTerval:TINTerval Command :SPA{1|2}:TINTerval:TINTerval <interval_number>,<min_time>,<max_time> The TINTerval:TINTerval command specifies the minimum and maximum time limits for the given interval. A query returns these limits for a specified interval. 0 to 7 <interval_ number> real number <min_time> real number <max_time>...
Page 285: Tinterval:tstatistic
SPA Subsystem TINTerval:TSTatistic TINTerval:TSTatistic Query :SPA{1|2}:TINTerval:TSTatistic? {TMINimum| TMAXimum|TAVerage|TOTal|TTOTal|<interval_number>} The TINTerval:TSTatistic query returns either the time or the number of samples associated with the requested statistic. The statistics you can request are: • TMINimum - overall minimum interval time • TMAXimum - overall maximum interval time •...
Page 286 16–26...
Page 287: Data And Setup Commands
DATA and SETup Commands...
Page 288: Introduction
The length of the data block can be as big as 20 Mbytes (HP 16554A), 40 Mbytes (HP 16555A), or 80 Mbytes (HP 16555D) in a three-card configuration.
Page 289: Data Format
DATA and SETup Commands Data Format Data Format To understand the format of the data within the block data, there are four important things to keep in mind. • Data is sent to the controller in binary form. • Each byte, as described in this chapter, contains 8 bits. •...
Page 290: System:data
Example OUTPUT XXX;":SYSTEM:DATA" <block data> Do not load UNPacked data into the instrument; it may cause the HP 16500 to lock up. If this happens, cycle power. Only data saved in PACKed mode can be reloaded back into a logic analyzer.
Page 291 DATA and SETup Commands SYSTem:DATA <block data> <block length specifier><section>... <block length #8<length> specifier the total length of all sections in byte format (must be represented with 8 <length> digits) <section> <section header><section data> 16 bytes, described on the following page <section header>...
Page 292: Section Header Description
" in ASCII for the DATA instruction). 1 byte - Reserved 1 byte - Module ID (34 decimal for the HP 16554A and HP 16555A/D master boards, and 35 for expander boards) 4 bytes - Length of block in bytes that when converted to decimal, specifies the number of bytes contained in the data block.
Page 293: Data Preamble Description
4 bytes - Machine data mode, one of the following decimal values: −1 = off 0 = 70 MHz (HP 16554A) or 100 MHz (HP 16555A/D) State data, no tags 1 = 70 MHz (HP 16554A) or 100 MHz (HP 16555A/D) State data with tags...
Page 294 DATA and SETup Commands Data Preamble Description Byte Position 4 bytes - List of pods in this analyzer, where a binary 1 indicates that the corresponding pod is assigned to this analyzer bit 31 bit 30 bit 29 bit 28 bit 27 bit 26 bit 25...
Page 295 DATA and SETup Commands Data Preamble Description Byte Position 4 bytes - Tag type for state mode in one of the following decimal values: 0 = off 1 = time tags 2 = state tags 8 bytes - Trigger offset. The time offset (in picoseconds) from when this analyzer is triggered and when this analyzer provides an output trigger to the IMB or port out.
Page 296 DATA and SETup Commands Data Preamble Description Bytes 241 through 244 contain the number of valid rows of data for Byte Position pod 1 of either the expansion card in a two-card module, or a middle cardslot expansion card in a three-card module. Bytes 245 through 248 contain the number of valid rows of data for pod 4 of the master card.
Page 297: Acquisition Data Description
DATA and SETup Commands Acquisition Data Description Acquisition Data Description The acquisition data section consists of a variable number of bytes depending on the number of cards in the configuration, the acquisition mode, and the state tag setting. The data is grouped in rows of bytes with one sample from each pod in a single row.
Page 298 DATA and SETup Commands Acquisition Data Description The depth of the data array is equal to the pod with the greatest number of rows of valid data. If a pod has fewer rows of valid data than the data array, unused rows will contain invalid data that should be ignored.
Page 299: Time Tag Data Description
DATA and SETup Commands Time Tag Data Description Example A three-card configuration with 516096 valid rows First data byte = byte 591 Last data byte = 14,451,278 [591 + (28 × 516096) - 1] Time Tag Data Description If tags are enabled for one or both analyzers, the tag data follows the acquisition data.
Page 300 10 bytes for the section name header> 1 byte reserved 1 byte for the module ID code (34 for the HP 16554A and HP 16555A/D logic analyzer) 4 bytes for the length of the section data in bytes format depends on the type of data. The total length of a section is 16 (for <section data>...
Page 301: Part 3 Programming Examples
Part 3 18 Programming Examples Programming Examples...
Page 303 Programming Examples...
Page 304 Introduction This chapter contains short, usable, and tested programs that cover the most asked for examples. The examples are written in HP BASIC 6.0. • Making a timing analyzer measurement • Making a state analyzer measurement • Making a state compare analyzer measurement •...
Page 305: Making A Timing Analyzer Measurement
! ****************** TIMING ANALYZER EXAMPLE ****************** for the HP 16554A/HP 16555A/HP 16555D Logic Analyzer ! ************************************************************** ! Select the module slot in which the HP 16554A/HP 16555A/D is installed. ! In this example, it is in slot B of the mainframe. OUTPUT 707;":SELECT 2"...
Page 306 Programming Examples Making a Timing Analyzer Measurement OUTPUT 707;":MACH1:TWAVEFORM:REMOVE" OUTPUT 707;":MACH1:TWAVEFORM:INSERT ’COUNT’, ALL" OUTPUT 707;":MACH1:TWAVEFORM:RANGE 1E-6" OUTPUT 707;":MENU 2,5" ! **************************************************************** ! Run the timing analyzer in single mode. OUTPUT 707;":RMODE SINGLE" OUTPUT 707;":START" ! **************************************************************** ! Set the marker mode (MMODE) to time so that patterns are available ! for marker measurements.
Page 307: Making A State Analyzer Measurement
This program is written so that you can run it with the HP E2433-60004 Logic Analyzer Training Board. This example is the same as the "Multilevel State Triggering" example in chapter 9 of the HP E2433 Logic Analyzer Training Kit.
Page 308 Programming Examples Making a State Analyzer Measurement ! ******************* SETUP THE TRIGGER SPECIFICATION ******************** ! The trigger specification will use five sequence levels with the trigger ! level on level four. Resource terms A through E, and RANGE1 will be ! used to store only desired counts from the 8-bit ripple counter.
Page 309 Programming Examples Making a State Analyzer Measurement ! ***************** CONFIGURE SEQUENCE LEVEL 4 *************************** ! Store a combination of resource terms (C or D or RANGE1) in level 4 and ! Then Trigger on resource term "E." OUTPUT 707;":MACHINE1:STRIGGER:STORE4 ’(C OR D OR IN_RANGE1)’" ! ************************ NOTE *********************** The FIND command selects the trigger in the sequence level specified as the trigger level.
Page 310 Programming Examples Making a State Analyzer Measurement 1170 IF (Status AND 1)=1 THEN GOTO 1190 1180 GOTO 1070 1190 PRINT TABXY(30,15);"Measurement is complete" 1200 1210 ! ************************ VIEW THE RESULTS ***************************** 1220 ! Display the State Listing and select a line number in the listing that 1230 ! allows you to see the beginning of the listing on the logic analyer 1240...
Page 311: Making A State Compare Analyzer Measurement
This program is written so that you can run it with the HP E2433-60004 Logic Analyzer Training Board. This example is the same as the "State Compare"...
Page 312 Programming Examples Making a State Compare Analyzer Measurement ! ****************************************************************** ! Specify two sequence levels, the trigger sequence level, specify ! FF hex for the "a" term which will be the trigger term, and store ! no states until the trigger is found. OUTPUT 707;":MACHINE1:STRIGGER:SEQUENCE 2,1"...
Page 313 Programming Examples Making a State Compare Analyzer Measurement !*********************************************************************** ! Display line 4090 of the compare listing and start the analyzer ! in a repetitive mode. OUTPUT 707;":MACHINE1:COMPARE:LINE 4090" OUTPUT 707;":START" ! Line 4090 of the listing is now displayed at center screen. ! In this example, the states are stable.
Page 314 Programming Examples Making a State Compare Analyzer Measurement 1100 !************************************************************************ 1110 ! Start the logic analyzer to acquire new data and then stop it to compare 1120 ! the data. When the acquistion is stopped, the Compare Listing Menu will 1130 ! be displayed.
Page 315 Programming Examples Making a State Compare Analyzer Measurement 1540 1550 ENTER 707 USING "#,2A";Error$ 1555 ENTER 707 USING "#,1A";Comma$ 1560 ENTER 707 USING "K";Line$ 1570 GOTO 1610 1580 1590 ENTER 707 USING "#,3A";Error$ 1595 ENTER 707 USING "#,1A";Comma$ 1600 ENTER 707 USING "K";Line$ 1610 1620 ! ************************************************************************...
Page 316: Transferring The Logic Analyzer Configuration
SYSTem:DATA command because it only transfers the configuration and not acquired data. ! ****************** SETUP COMMAND AND QUERY EXAMPLE ******************** for the HP 16554A/HP 16555A/HP 16555D ! ********************* CREATE TRANSFER BUFFER ************************* ! Create a buffer large enough for the block data. See "Sending Queries ! to the Logic Analyzer"...
Page 317 Programming Examples Transferring the Logic Analyzer Configuration ! *********************** SEND THE SETUP QUERY ************************** OUTPUT 707;":SYSTEM:HEADER ON" OUTPUT 707;":SYSTEM:LONGFORM ON" OUTPUT @Comm;":SELECT 2" OUTPUT @Comm;":SYSTEM:SETUP?" ! ******************** ENTER THE BLOCK SETUP HEADER ********************* ! Enter the block setup header in the proper format. ENTER @Comm USING "#,B";Byte PRINT CHR$(Byte);...
Page 318 ! Save the transfer buffer pointer so it can be restored after the ! transfer. STATUS @Buff,5;Streg 1000 1010 ! ************ TRANSFER SETUP TO THE MODULE **************** 1020 ! Transfer the setup from the buffer to the HP 16554A/HP 16555A/HP 16555D. 1030 1040 TRANSFER @Buff TO @Comm;COUNT Numbytes,WAIT 1050 18–16...
Page 319 Programming Examples Transferring the Logic Analyzer Configuration 1060 ! ********************** RESTORE BUFFER POINTERS *********************** 1070 ! Restore the transfer buffer pointer 1080 1090 CONTROL @Buff,5;Streg 1100 1110 ! ******************** SEND TERMINATING LINE FEED ********************** 1120 ! Send the terminating linefeed to properly terminate the setup string. 1130 1140 OUTPUT @Comm;""...
Page 320: Checking For Measurement Completion
Programming Examples Checking for Measurement Completion Checking for Measurement Completion This program can be appended to or inserted into another program when you need to know when a measurement is complete. If it is at the end of a program it will tell you when measurement is complete. If you insert it into a program, it will halt the program until the current measurement is complete.
Page 321: Sending Queries To The Logic Analyzer
HP 16554A/HP 16555A/HP 16555D ! ********************* CREATE TRANSFER BUFFER ************************* ! NOTE WELL! The data from the 16554A may be up to 19Mbytes long! ! NOTE WELL! The data from the 16555A may be up to 38Mbytes long!
Page 322 Programming Examples Sending Queries to the Logic Analyzer ! ************* INTITIALIZE VARIABLE FOR NUMBER OF BYTES ***************** ! The variable "Numbytes" contains the number of bytes in the buffer. REAL Numbytes Numbytes=0 ! ************** RE-INITIALIZE TRANSFER BUFFER POINTERS ****************** CONTROL @Buff,3;1 CONTROL @Buff,4;0 ! *********************** SEND THE DATA QUERY ************************** OUTPUT 707;":SYSTEM:HEADER ON"...
Page 323 OUTPUT @Comm USING "#,14A";":SYSTEM:DATA #" PRINT "SYSTEM:DATA command has been sent. Press continue." PAUSE ! ********************* SEND THE BLOCK DATA **************************** ! Send the block data header to the HP 16554A/HP 16555A in the proper ! format. OUTPUT @Comm USING "#,A";"8" Str1$=DVAL$(Numbytes,10) Byte=1 PRINT USING "AAAAAAAA";Str1$[4]...
Page 324 Programming Examples Sending Queries to the Logic Analyzer 1010 ! ************* TRANSFER DATA TO THE HP 16554A/HP 16555 **************** 1020 ! Transfer the data from the buffer to the HP 16554A/HP 16555A. 1030 1040 TRANSFER @Buff TO @Comm;COUNT Numbytes,WAIT 1050...
Page 325: Index
Index CENTer, 8–6, 9–5, 13–9 OVERview:MLENgth, 16–12 A+B, 4–11, 13–19 CLEar, 6–11, 10–5 OVERView:OMARker, 16–13 A,B, 13–18 CLOCk, 5–6 OVERView:XMARker, 16–15 A-B, 13–13 CLRPattern, 7–8, 8–6, 13–9, 14–8 PATTern, 15–6 ACCumulate command/query, 8–5, 9–4, CLRStat, 8–7, 13–9 PLUS, 4–11, 13–19 13–7 CMASk, 10–5 PRINt, 1–7...
Page 326 Index WIDTh, 15–8 WLISt, 2–7, 4–4 EDGE command/query, 12–13 MACHine selector, 2–6, 3–4 XCONdition, 13–26, 14–19 else branch, 6–9 MACHine subsystem, 3–1, 3–3 to 3–11 XMARker, 16–15 else on, 12–9 markers, 4–2, 7–8, 7–10, 7–17, 13–21, XPATtern, 7–20, 13–27, 14–20 entering, 14–11 14–8, 14–10, 14–17 to 14–20, 16–14 XSEarch, 7–21, 13–28, 14–21...
Page 327 Index transferring configuration to analyzer, OMARker, 16–13 OCONdition command/query, 13–15, 14–11 18–14 OPATtern, 7–12, 13–16, 14–12 offset, 4–5 transferring configuration to the OSEarch, 7–13, 13–17, 14–13 OMARker command/query, 16–13 controller, 18–14 OSTate, 4–9, 7–13, 14–14 OPATtern command/query, 7–11, 13–16, OTAG, 7–14, 14–15 14–12 OTHer, 16–18 OR’d trigger, 3–5...
Page 328 Index TSTatistic, 16–25 SLAVe command/query, 5–15 SLISt Subsystem, 7–3 TTYPe, 16–21 SLISt selector, 7–7 STRigger Subsystem, 6–3 to 6–4 TYPE, 3–11 SLISt subsystem, 7–1, 7–3 to 7–23 SWAVeform Subsystem, 8–3 VAXis, 9–7 SOPQual command/query, 5–16 SYMBol Subsystem, 15–3 VRUNs, 7–18, 13–25, 14–18 SPA selector, 2–7 TFORmat Subsystem, 11–3 XCONdition, 13–26, 14–19...
Page 329 Index TSTatistic query, 16–25 TTRace selector, 12–8 TTRigger selector, 12–8 TTRigger/TTRace subsystem, 12–1, 12–3 to 12–23 TTYPe command/query, 16–21 TWAVeform selector, 13–7 TWAVeform Subsystem, 13–1, 13–3 to 13–29 TYPE command/query, 3–10 to 3–11 VAXis command/query, 9–6 to 9–7 vertical scroll, 4–7 VRUNs query, 7–18, 13–25, 14–18 WIDTh command, 15–8 WLISt selector, 2–7, 4–4...
Page 330 Index–6...
Page 331 • © Copyright Hewlett- Safety Safety Symbols Service instructions are for Packard Company 1987, trained service personnel. To This apparatus has been 1990, 1993, 1994, 1997 avoid dangerous electric designed and tested in shock, do not perform any All Rights Reserved. accordance with IEC Instruction manual symbol: service unless qualified to do...
Page 332 This Hewlett-Packard This is the first edition of the Hewlett-Packard edition and of any changed product has a warranty HP 16554A/HP 16555A/ specifically disclaims the pages to that edition. against defects in material HP 16555D Programmer’s implied warranties of and workmanship for a period Guide.

This manual is also suitable for:

16555d 16555a

HP 16554A Programmer's Manual

Part 1 General Information

1 Programming the HP 16554A/ HP 16555A/HP 16555D

2 Module Level Commands

Part 2 Commands

3 Machine Subsystem

4 Wlist Subsystem Wlist

5 Sformat Subsystem Sformat

6 Strigger (Strace) Subsystem Qualifier

7 Slist Subsystem

8 Swaveform Subsystem

9 Schart Subsystem

10 Compare Subsystem

11 Tformat Subsystem

12 Ttrigger (Ttrace) Subsystem

13 Twaveform Subsystem

14 Tlist Subsystem

15 Symbol Subsystem

16 SPA Subsystem

17 DATA and Setup Commands

Part 3 Programming Examples

18 Programming Examples

Quick Links

Need help?

Questions and answers

Related Manuals for HP 16554A

Summary of Contents for HP 16554A