Page 1 $XWRUDQJLQJ &RPEL6FRSH ™ ,QVWUXPHQW 30%30%30% 30%30% SCPI Users Manual 02/- Nov-1998 ®...
Page 2 Microsoft, and Microsoft QuickBASIC are trademarks of Microsoft Corporation. IBM is a registered trademark of International Business Machines Corporation. ™ CombiScope is a trademark of Fluke Corporation. PCIIA is a trademark of National Instruments Corporation. HPGL is a trademark of Hewlett-Packard Company. ©...
Page 3 CONTENTS Page 1 ABOUT THIS MANUAL ....... . 1-1 1.1 What this Manual Contains ......1-1 2 GETTING STARTED WITH SCPI PROGRAMMING .
Page 4 3.3 Measuring Signal Characteristics ......3-8 3.3.1 The MEASure? query ......3-8 3.3.2 Benefits of using parameters .
Page 5 3.9 Post Processing ........3-45 3.9.1 How to do post processing .
Page 6 3.16 Saving/Restoring Instrument Setups ..... 3-78 3.16.1 How to restore initial settings ..... . . 3-78 3.16.2 How to save/restore a setup via instrument memory .
Page 7 B CROSS REFERENCES ....... B-1 B.1 Cross Reference Front Panel Keys / Commands ..B-1 B.2 Cross Reference Softkey Menus / Commands .
Page 8: About This Manual
ABOUT THIS MANUAL 1 - 1 1 ABOUT THIS MANUAL The SCPI Programming Manual for the CombiScope™ instruments describes how to program your CombiScope™ instrument via the IEEE bus using SCPI commands. 1.1 What this Manual Contains A complete table of contents is given at the beginning of the manual. Chapter 1 ABOUT THIS MANUAL Explains what the SCPI programming manual for the CombiScopes...
Page 9: E Summary Of System Settings
1 - 2 ABOUT THIS MANUAL Appendix A APPLICATION PROGRAM EXAMPLES Appendix A describes some application program examples. The application programs are supplied on floppy. Appendix B CROSS REFERENCES Appendix B gives cross references between SCPI commands and front panel keys, softkey menu options, and instrument functions. Appendix C MANUAL CONVENTIONS Appendix C explains which abbreviations and symbols are used in...
Page 10: Getting Started With Scpi Programming
GETTING STARTED WITH SCPI PROGRAMMING 2 - 1 2 GETTING STARTED WITH SCPI PROGRAMMING 2.1 Preparations for SCPI Programming To program your CombiScope instrument, you need a system setup and a programming environment. Various program examples (refer to PROGRAM EXAMPLE:) are given in the following sections. These program examples can be executed one at a time or chained together for a complete tutorial.
Page 11 2 - 2 GETTING STARTED WITH SCPI PROGRAMMING The parameters of these drivers are defined by the device handler GPIB.COM and by the QuickBASIC program code. The following drivers and parameters are used in the program examples: • The IEEE-488.2 driver "Send" is used to send a command or query to an instrument.
Page 12 GETTING STARTED WITH SCPI PROGRAMMING 2 - 3 • <response> A response string sent by the instrument as a response to a query. • <eot> An "end of text" indication: 0 = program message to be continued (no action) 1 = end of program message (sends End-message + EOI true) •...
Page 13: Initializing The Combiscope Instrument
2 - 4 GETTING STARTED WITH SCPI PROGRAMMING 2.2 Initializing the CombiScope Instrument 2.2.1 How to reset the CombiScope instrument The instrument itself can be reset by sending the RST command. This sets the instrument to a fixed setup optimized for remote operation. The status and error data of the instrument can be cleared by sending the CLS command.
Page 14: Error Reporting
GETTING STARTED WITH SCPI PROGRAMMING 2 - 5 2.3 Error Reporting Instrument errors are usually caused by programming or setting errors. They are reported by the instrument during the execution of each command. To make sure that a program is running properly, you must query the instrument for possible er- rors after every functional command.
Page 15: Acquiring Traces
2 - 6 GETTING STARTED WITH SCPI PROGRAMMING 2.4 Acquiring Traces Trace acquisitions are started via the INITiate commands. A single acquisition is done by sending a single INITiate command. Continuous acquisitions are done by sending the INITiate:CONTinuous ON command. The TRACe? query allows you to acquire a trace of signal samples from one of the following sources: •...
Page 16: How To Acquire A Single Shot Trace
GETTING STARTED WITH SCPI PROGRAMMING 2 - 7 2.4.1 How to acquire a single shot trace In the program example, a single shot trace acquisition of 8192 8-bit samples is done with a probe connected to input channel 1. The trace sample bytes are read from the GPIB as string characters.
Page 17: How To Acquire Repetitive Traces
2 - 8 GETTING STARTED WITH SCPI PROGRAMMING 2.4.2 How to acquire repetitive traces In the program example, 5 trace acquisitions of 512 16-bit samples are done via a probe connected to channel 2. The trace sample bytes are read from the GPIB as string characters and written to the file TRACE5.DAT on the hard disk.
Page 18: Measuring Signal Characteristics
GETTING STARTED WITH SCPI PROGRAMMING 2 - 9 2.5 Measuring Signal Characteristics The measurement instructions allow you to make a complete measurement. This includes the configuration of the instrument, the initiation of the trigger system, and the fetching of the acquisition data. The measurement instructions can be used at different levels, varying in processing time.
Page 19: How To Make A Single Shot Measurement
2 - 10 GETTING STARTED WITH SCPI PROGRAMMING 2.5.1 How to make a single shot measurement The MEASure? query allows you to make a single-shot measurement, and the FETCh? query allows you to fetch more signal characteristics. PROGRAM EXAMPLE: ’ ***** ’Measure and print the AC-RMS, peak to peak, and amplitude of ’the signal on channel 1.
Page 20: Using The Combiscope Instruments
USING THE COMBISCOPE INSTRUMENTS 3 - 1 3 USING THE COMBISCOPE INSTRUMENTS 3.1 Introduction This chapter explains how to access the functions of the CombiScope instruments family in a remote programming environment. For that purpose, the CombiScope instrument is equipped with an IEEE-488 compatible GPIB interface and implements a full SCPI compatible command set which provides an extensive range of remote control facilities.
Page 21 3 - 2 USING THE COMBISCOPE INSTRUMENTS As the example already shows, the commands are easy to learn and self- explanatory to both novice and expert users. The learning curve is considerably decreased for new instruments or instrument functions with which the programmer is not familiar.
Page 22: Fundamental Programming Concepts
USING THE COMBISCOPE INSTRUMENTS 3 - 3 3.2 Fundamental Programming Concepts The remote operation of your CombiScope instrument can be accessed using different programming concepts. The concept to be chosen depends upon the application of the instrument in the remote programming environment. Each of the four concepts has it own benefits and trade-offs.
Page 23: Measurement Instructions
3 - 4 USING THE COMBISCOPE INSTRUMENTS Trade-off: This way of programming is cumbersome and tricky, because additional information on the front panel display is not always available remotely. Example: DISPlay:MENU TRIGger Activates the TRIGGER softkey menu. SYSTem:KEY 4 Simulates the pressing of softkey 4. The effect is that TRIGGER menu option "noise"...
Page 24: Single Function Programming Using The Instrument Model
USING THE COMBISCOPE INSTRUMENTS 3 - 5 The measurement instructions are easy to use and do not require any special knowledge of the instrument. The programming concept reduces simple measurement tasks with complex instruments to simple instructions, leaving the setup complexity to the instrument. The measurement instructions are extremely useful when the application does not require the precise setting of instrument functions.
Page 25: Instrument Setup
3 - 6 USING THE COMBISCOPE INSTRUMENTS Functions in a particular subsystem are always controlled by commands that begin with the name of that subsystem. For example, a command that programs the input coupling is INPut:COUPling DC. All programmable settings can be queried easily. The query form is obtained from the command by simply removing the parameter and adding a question mark.
Page 26: Front Panel Simulation
USING THE COMBISCOPE INSTRUMENTS 3 - 7 Example for the instrument cursor settings: → Send SYSTem:SET? 32 Queries oscilloscope instrument settings of node 32, which are the cursor settings. ← Read <settings> Reads the cursor settings. → Send SYSTem:SET <settings> Restores the cursor settings.
Page 27: Measuring Signal Characteristics
3 - 8 USING THE COMBISCOPE INSTRUMENTS 3.3 Measuring Signal Characteristics As explained in section 3.2.1 "Measurement instructions", the measurement instruction set is a new approach in the remote operation of programmable instruments. This instruction set allows you to request a particular characteristic of the input signal.
Page 28: Benefits Of Using Parameters
USING THE COMBISCOPE INSTRUMENTS 3 - 9 3.3.2 Benefits of using parameters The generic form of a measurement instruction is as follows: MEASure[:VOLTage]:<measure_function>? [[<voltage_parameters>,]<measure_parameters>][,<channel_list>] The :VOLTage keyword is a default node, which specifies the signal characteristic to be measured, relates to the voltage component of the signal. The <measure_function>...
Page 29 3 - 10 USING THE COMBISCOPE INSTRUMENTS Examples: MEASure:AMPLitude? This query measures the amplitude of a waveform at the default input channel 1. After the acquisition, the resulting amplitude is returned. MEASure:VOLTage:AMPLitude? 10, (@2) This query measures the amplitude of a signal at channel 2 (@2). But, since it specifies the expected voltage value (10 volts), it will complete the measurement faster.
Page 30: Waveform Measurements
USING THE COMBISCOPE INSTRUMENTS 3 - 11 3.3.3 Waveform measurements The following figure shows the terms used for pulse measurements and the key words that are used as header nodes in the measurement instructions. TMAXimum MAXimum RISE RISE TIME FALL FALL TIME OVERshoot PREShoot...
Page 31 3 - 12 USING THE COMBISCOPE INSTRUMENTS Examples: MEASure:FALL:TIME? (@3) Measures the time interval during which the pulse at channel 3 decreases from 90% to 10% of its amplitude. MEASure:RISE:TIME? 20,80 Measures the time interval during which the pulse at the default channel 1 increases from 20% to 80% of its amplitude.
Page 32: Customizing Settings
USING THE COMBISCOPE INSTRUMENTS 3 - 13 3.3.4 Customizing settings Often, you need more precise control of the measurements than possible with the MEASure? query. The combination of CONFigure and READ? is provided to allow you to program one or more settings that are vital to your application. Executing this sequence of instructions is equivalent to sending MEASure? For setting up the instrument, CONFigure uses the same measure functions and parameters as MEASure?.
Page 33: Multiple Measurements
3 - 14 USING THE COMBISCOPE INSTRUMENTS READ? Requests to execute the default DC measurement. Since this is not possible with the chosen configuration, an execution error is generated and no result is returned. CONFigure:RISE:TIME Configures the CombiScope instrument to perform a rise time measurement.
Page 34: Multiple Characteristics From A Single Acquisition
USING THE COMBISCOPE INSTRUMENTS 3 - 15 READ:FREQuency? Starts the acquisition and returns the measured frequency. READ:FREQuency? Starts a next acquisition and returns the new frequency result. READ:FREQuency? Etc. 3.3.6 Multiple characteristics from a single acquisition. It is often necessary to determine several signal characteristics from the last acquired waveform.
Page 35: Trigger Control Via Gpib
3 - 16 USING THE COMBISCOPE INSTRUMENTS 3.3.7 Trigger control via GPIB You need a separate GPIB command to start a measurement synchronized with other instruments. This is done by sending the TRG command or the GET (Group Execute Trigger) code. The MEASure? and READ? queries do not allow you to do so, because such a setup causes a query error.
Page 36: Fetching Characteristics From Memory Traces
USING THE COMBISCOPE INSTRUMENTS 3 - 17 3.3.8 Fetching characteristics from memory traces The FETCh? query not only allows you to determine a characteristic from the last acquired waveform, it also allows you to calculate a signal characteristic from a waveform that is stored in a trace memory element.
Page 37: Acquisition
3 - 18 USING THE COMBISCOPE INSTRUMENTS 3.4 Acquisition 3.4.1 Acquisition control Several commands exist to control the acquisition process. The following diagram shows the possible states of the acquisition process, and the way they are affected by commands. IDLE state *RST ABORt power on...
Page 38 USING THE COMBISCOPE INSTRUMENTS 3 - 19 or by setting INITiate:CONTinuous to ON. The INITiate[:IMMediate] command causes the CombiScope instrument to perform one complete acquisition cycle. Upon completion of the cycle the instrument returns to the IDLE state. The INItiate:CONTinuous command is used to select whether the instrument is continuously initiated or not.
Page 39: Triggering
3 - 20 USING THE COMBISCOPE INSTRUMENTS 3.4.1.1 Triggering After the measurement is initiated, the CombiScope instrument starts the real acquisition when the trigger conditions are satisfied, e.g., when the selected trigger event occurs. The trigger conditions can be ignored during a specific hold- off time, which can be programmed using the TRIGger:HOLDoff command.
Page 40 USING THE COMBISCOPE INSTRUMENTS 3 - 21 Trigger Slope The TRIGger:SLOPe command allows you to define the trigger edge for all input channels, which can be POSitive, NEGative, or EITHer. After a RST command the TRIGger:SLOPe is set to POSitive. PROGRAM EXAMPLE: ’Configures channel 2 CALL Send(0, 8, "CONFigure:PTPeak (@2)", 1)
Page 41 3 - 22 USING THE COMBISCOPE INSTRUMENTS DC COUPLING (0 Hz cutoff frequency): DC coupling causes the signal to be passed over the full bandwidth (from 0 Hz to 60/100/200 MHz). -3dB DC COUPLING FULL BANDWIDTH FREQ. ST7427 Figure 3.4 DC Coupling PROGRAM EXAMPLE: *** Select DC coupling on input signal channel 2.
Page 42: Video Triggering
USING THE COMBISCOPE INSTRUMENTS 3 - 23 LF-REJECT (30 KHz cutoff frequency): LF reject (HF passed) causes the signal to be LF -REJECT passed from the cutoff frequency (30 KHz) to the full bandwidth frequency (60/100/200 MHz). -3dB 30kHz FULL BANDWIDTH FREQ.
Page 43 3 - 24 USING THE COMBISCOPE INSTRUMENTS The video trigger mode can be programmed to field1, field2, or lines using the TRIGger:VIDeo:FIELd... commands. The video trigger line can be programmed using the TRIGger:VIDeo:LINE command. The video system can be selected using the TRIGger:VIDeo:FORMat:... commands.
Page 44: The Trigger Modes
USING THE COMBISCOPE INSTRUMENTS 3 - 25 3.4.1.3 The trigger modes A combination of the INITiate:CONTinuous and TRIGger:SOURce command allows you to define the following trigger modes: INITiate TRIGger Trigger mode: :CONTinuous :SOURce >>>Single-shot<<< Generates one sweep, regardless of any IMMediate trigger settings (valid after RST).
Page 45 3 - 26 USING THE COMBISCOPE INSTRUMENTS Only in the single-shot and multiple-shot trigger mode (INITiate:CONTinuous OFF), the bits 3 (SWEeping) and 5 (Waiting for TRIGger) in the OPERation status are valid. Also the Operation Complete bit (OPC bit 0) in the standard Event Status Register (ESR) is valid.
Page 46: Pre- And Post-Triggering
USING THE COMBISCOPE INSTRUMENTS 3 - 27 3.4.1.4 Pre- and post-triggering When pre-triggering is selected, the real trace acquisition begins before the moment that the trigger occurs. Triggering occurs when the trigger conditions are satisfied and the instrument leaves the "Wait for TRIGger" state as shown in the trigger diagram of figure 3.3.
Page 47: External Triggering
3 - 28 USING THE COMBISCOPE INSTRUMENTS 3.4.1.5 External triggering External triggering is only possible for the PM33x0B CombiScope instruments. Channel 4 is used as the external trigger channel with the following view possibilities: attenuator positions 0.1 and 1 V/div (AMP key). trigger slope positive or negative (EXT TRIG key).
Page 48: Reading Trace Acquisitions
USING THE COMBISCOPE INSTRUMENTS 3 - 29 3.4.2 Reading trace acquisitions Once acquisitions are completed, the resulting traces ares placed in TRACe memory, as shown in the following figure. TRACe INPut SENSe memory CH 1 INPut[1] :VOLTage[1] CH 2 INPut2 :VOLTage2 :SWEep CH 3...
Page 49: Single-Shot Acquisition
3 - 30 USING THE COMBISCOPE INSTRUMENTS 3.4.2.1 Single-shot acquisition PROGRAM EXAMPLE: In this example a single-shot trace acquisition is done via channel 1. The trace bytes are entered as characters in the string response$. ’Dimensions trace buffer DIM response AS STRING * 1033 ’Resets the instrument CALL Send(0, 8, "...
Page 50: Conversion Of Trace Data
USING THE COMBISCOPE INSTRUMENTS 3 - 31 3.4.3 Conversion of trace data The trace data is sent as a block of binary codes. Trace samples can be formatted to consist of 8 bits (1 byte) or 16 bits (2 bytes) codes, which can be selected by the FORMat command.
Page 51: Conversion Of 8-Bit Samples To Integer
3 - 32 USING THE COMBISCOPE INSTRUMENTS 3.4.3.1 Conversion of 8-bit samples to integer As an example a conversion of a trace of 512 "8-bit" samples is shown. The format is as follows: trace bytes # 3 5 1 4 <8> <byte 1> . . . <byte 512> <checksum> <NL> trace sample 512 trace sample 1 byte with decimal value 8...
Page 52: Conversion Of 16-Bit Samples To Integer
USING THE COMBISCOPE INSTRUMENTS 3 - 33 3.4.3.2 Conversion of 16-bit samples to integer As an example a conversion of a trace of 512 "16-bit" samples is shown. The format is as follows: trace bytes # 4 1 0 2 6 <16> <msb 1> <lsb 1> . . . <msb 512> <lsb 512> <checksum> <NL> trace sample 512 trace sample 1 byte with decimal value 16...
Page 53: Conversion To Voltage Values
3 - 34 USING THE COMBISCOPE INSTRUMENTS 3.4.3.3 Conversion to voltage values Screen positions correspond to voltage values. This relation is shown in the figure below, and is determined by the settings that are programmed by the SENSe:VOLTage:RANGe:PTPeak SENSe:VOLTage:RANGe:OFFSet commands. Screen Amplitude Trace sample...
Page 54 USING THE COMBISCOPE INSTRUMENTS 3 - 35 PROGRAM EXAMPLE: In this program example a trace of 512 samples from the actual signal at input channel 1 is read. The received data block is converted to an array of voltages. After each sample conversion the voltage value is printed.
Page 55: Averaging Acquisition Data
3 - 36 USING THE COMBISCOPE INSTRUMENTS 3.5 Averaging Acquisition Data Acquired traces and measured signal characteristics can be averaged over a number of acquisitions. The preprocessing AVERAGE function of the CombiScopes instruments can be enabled by using the SENSe:AVERage[STATe] command.
Page 56 USING THE COMBISCOPE INSTRUMENTS 3 - 37 The following diagram shows the possible states of the acquisition process when "averaging" is on, and the way they are affected by commands. IDLE state *RST ABORt power on INIT INIT:CONT ON INITiated state INIT:CONT ON Wait for AVERage state SENSe:AVERage:COUNt...
Page 57: Channel Selection
3 - 38 USING THE COMBISCOPE INSTRUMENTS 3.6 Channel Selection Input channels can be switched on or off by using the SENSe:FUNCtion[:ON] or SENSe:FUNCtion:OFF commands. An input channel is selected by specifying the parameter "XTIMe:VOLTage<n>", where the numeric suffix <n> specifies the input channel number.
Page 58: Signal Conditioning
USING THE COMBISCOPE INSTRUMENTS 3 - 39 3.7 Signal Conditioning The INPut subsystem allows you to condition the input signals, such as AC/DC/GROund coupling, input filtering, and input impedance selection. In the digital mode, the SENSe:VOLTage<n>:RANGe:AUTO command allows you to enable autoranging of the attenuation for each of the input channels <n> separately.
Page 59: Input Filtering
3 - 40 USING THE COMBISCOPE INSTRUMENTS 3.7.2 Input filtering The INPut:FILTer command allows you to turn the common low-pass filter (bandwidth limiter) on or off for all input channels at the same time. The cutoff frequency is fixed at 20 MHz. After a RST command, the filter is turned off.
Page 60: Autoranging Attenuators
USING THE COMBISCOPE INSTRUMENTS 3 - 41 Because the programmed PTPeak and OFFSet values directly affect the trace values, they can be used to calculate the voltage amplitude of the corresponding trace samples. As explained in section 3.4.3.3 "Conversion to voltage values", the voltage amplitude of a trace sample can be calculated from the equations: Vs = (Ts / 200) PTPeak - OFFSet...
Page 61: Time Base Control
3 - 42 USING THE COMBISCOPE INSTRUMENTS 3.8 Time Base Control In the digital mode, the SENSe:SWEep:TIME:AUTO command allows you to enable autoranging of the main timebase (MTB). 3.8.1 Number of samples The TRACe:POINts command allows you to set the number of sample points, which is the total acquisition length for all traces.
Page 62: Real Time Acquisition
USING THE COMBISCOPE INSTRUMENTS 3 - 43 PROGRAM EXAMPLE: ’Requests sweep time CALL Send(0, 8, "SENSe:SWEep:TIME?, 1) ’Reads sweep time CALL Receive(0, 8, STIME$, 256) ’Requests number of trace points CALL Send(0, 8, "TRACe:POINts? CH1, 1) ’Reads number of trace points CALL Receive(0, 8, TPOINTS$, 256) ’Converts string to variable SWETIM = VAL(STIME$)
Page 63: Autoranging Time Base
3 - 44 USING THE COMBISCOPE INSTRUMENTS 3.8.4 Autoranging time base The AUTO RANGE function of the Main Time Base (MTB) adjusts the time base automatically, so that two to six waveform periods are displayed on the screen. If a waveform doesn't contain enough information to calculate its period, the time base is adjusted to acquire a minimum of two periods.
Page 64: Post Processing
USING THE COMBISCOPE INSTRUMENTS 3 - 45 3.9 Post Processing TRACe CH 1 M1_1 M2_1 M3_1 M50_1 CALCulate1 CH 2 M1_2 M2_2 M3_2 M50_2 SENSe CH 3 M1_3 M2_3 M3_3 M50_3 CH 4 M1_4 M2_4 M3_4 M50_4 CALCulate2 ST7161 Figure 3.17 Post processing control 3.9.1 How to do post processing...
Page 65: Specify The Settings Of The Post Processing Function
3 - 46 USING THE COMBISCOPE INSTRUMENTS TRACe CALCulate CH 1 M1_1 M2_1 M3_1 M50_1 CALCulate[1] CH 2 M1_2 M2_2 M3_2 M50_2 SENSe CH 3 M1_3 M2_3 M3_3 M50_3 CH 4 M1_4 M2_4 M3_4 M50_4 CALCulate2 CALCulate:FEED "M3_2" ST7162 CALCulate2:FEED "M2_4" Figure 3.18 Post processing feed definition 3.9.1.2...
Page 66: Check The Result Of The Post Processing Function
USING THE COMBISCOPE INSTRUMENTS 3 - 47 3.9.1.4 Check the result of the post processing function. The results of the post processing functions :MATH :TRANsform:FREQuency :TRANsform:HISTogram are stored in M1_1 for CALCulate1 and in M2_1 for CALCulate2, regardless of the input (feed) trace. The results of the post processing functions :FILTer:FREQuency :INTegral...
Page 67: Mathematical Calculations
3 - 48 USING THE COMBISCOPE INSTRUMENTS 3.9.2 Mathematical calculations Mathematical calculations can be performed on 2 traces using the CALCulate1:MATH and CALCulate2:MATH functions. These functions comply with the front panel features MATH1 and MATH2 respectively. The calculation can be an addition (+), a subtraction (-), or a multiplication ( ).
Page 68: Frequency Domain Transformations
USING THE COMBISCOPE INSTRUMENTS 3 - 49 Scaling can be adjusted with the "CURSORS TRACK and delta" knobs via the MATHPLUS - PARAM menu option. PROGRAM EXAMPLE: ’Integral CALC1 on CALL Send(0, 8, "CALCulate:INTegral:STATe ON", 1) CALL Send(0, 8, "CALCulate2:DERivative:POINts 35", 1)’35 differential points ’Differential CALC2 on CALL Send(0, 8, "CALCulate2:DERivative:STATe ON", 1) 3.9.4...
Page 69 3 - 50 USING THE COMBISCOPE INSTRUMENTS Trace sample value Trace point 16-bits value 8-bits top - - - - - 25600 - 0 dB - - - - - - - 19200 - 10 dB - - - - - - - 12800 - 20 dB - - - - - - -...
Page 70 USING THE COMBISCOPE INSTRUMENTS 3 - 51 Absolute FFT amplitudes are calculated from the true signal using the information on the actual attenuator setting in the range from 5 V/div. to 2 mV/div. This results in an offset value to be added to the relative FFT amplitude for each attenuator setting.
Page 71 3 - 52 USING THE COMBISCOPE INSTRUMENTS dBm - 50Ω offset calculation: From the Vrms offset value the dBm-50Ω offset value is calculated as follows: ⁄ dBm 50Ω offset – 20 * Vrms offset 0,2236068 Note: P *R 1E-3 *50 0,2236068 Example for attenuator setting 0.5 V/div.: ⁄...
Page 72 USING THE COMBISCOPE INSTRUMENTS 3 - 53 SUMMARY OF CALCULATED OFFSET VALUES: ATTENUATOR SETTING: Vrms: dBm-50Ω: dBm-600Ω: dBµV: V/div + 11.18034 + 33.9794 + 23.187588 + 140.9691 4.4721359 + 26.0206 + 15.228787 + 133.0103 2.236068 + 20.0 9.2081872 + 126.9897 1.118034 + 13.9794 3.1875874...
Page 73 3 - 54 USING THE COMBISCOPE INSTRUMENTS PROGRAM EXAMPLE: The following program example converts a relative or absolute FFT trace of 512 samples of 1 or 2 bytes from the signal on channel 1 via the MATH1 feature as follows: •...
Page 74: Histogram Functions
USING THE COMBISCOPE INSTRUMENTS 3 - 55 3.9.5 Histogram functions The HISTogram function calculates an amplitude distribution of the incoming trace. The number of points in the histogram trace is 512. Each point in the histogram specifies the number of times that a data point of the incoming trace is within a particular amplitude belt.
Page 75: Trace Memory
3 - 56 USING THE COMBISCOPE INSTRUMENTS 3.10 Trace Memory The trace memory of the CombiScopes instruments consists of space for channel acquisition traces (CH1 to CH4) and memory register traces (M1 to M8 and M9 to M50 extended). The amount of acquisition and register space depends on the following: •...
Page 76: Trace Formatting
USING THE COMBISCOPE INSTRUMENTS 3 - 57 The following table shows the relation between the trace acquisition length (TRACe:POINts) and the available channel (CHx) and memory traces (Mx). TRACe:POINts CHANNELS: MEMORY REGISTERS: STANDARD: (PM33x0B) (2+EXT) M1 .. M8 (2+EXT) M1 .. M2 M1 ..
Page 77: Copying Traces To Memory
3 - 58 USING THE COMBISCOPE INSTRUMENTS 3.10.2 Copying traces to memory The TRACe:COPY command allows you to copy the contents of a memory register to another memory register. This allows you to fill a memory register with traces from one of the following sources: •...
Page 78: Writing Data To Trace Memory
USING THE COMBISCOPE INSTRUMENTS 3 - 59 3.10.3 Writing data to trace memory The TRACe command allows you to write data from the controller into a memory register. The following possibilities are available: • Write a previously read trace using the TRACe? query. Example: Send →...
Page 79: Reading Data From Trace Memory
3 - 60 USING THE COMBISCOPE INSTRUMENTS 3.10.4 Reading data from trace memory The TRACe? query allows you to read the contents from one of the following trace memory registers: • An acquisition trace from one of the input channels (CH1 to CH4). •...
Page 80: Screen/Display Functions
USING THE COMBISCOPE INSTRUMENTS 3 - 61 3.11 Screen/Display Functions 3.11.1 Brightness control The DISPlay:BRIGhtness command allows you to control the brightness of the trace(s) displayed on the screen of your CombiScope instrument on a scale from 0.0 (low) to 1.0 (high). After a RST command, the brightness intensity is 0.18.
Page 81: Readout Of Measurement Data
3 - 62 USING THE COMBISCOPE INSTRUMENTS 3.11.2.1 Readout of measurement data The DISPlay:WINDow[1]:TEXT<n>:DATA? query allows you to acquire measured data as displayed on the upper line(s) of the screen of your CombiScope instrument. The following measured data values can be selected by specifying the number <n>...
Page 82 USING THE COMBISCOPE INSTRUMENTS 3 - 63 Example: Send → ’Switches MEAS1 & 2 off Send → DISPlay:MENU MEASure ’Switches MEASURE menu on Send → SYSTem:KEY 2;KEY 4 ’Switches MEAS1 and MEAS2 on Send → DISPlay:WINDow:TEXT1:DATA? ’Requests MEAS1 data Read ← pkpk,6000E-04,V ’Response = peak-to-peak 0.6 volt.
Page 83 3 - 64 USING THE COMBISCOPE INSTRUMENTS PROGRAM EXAMPLE: Read and print the DC and frequency characteristic of the actual signal using the MEAS1 and MEAS2 functions. The program stops to let you make the requested MEAS selections. DIM response AS STRING * 30 ’Displays MEASURE menu CALL Send(0, 8, "DISPlay:MENU MEASure", 1) ’...
Page 84: Display Of User-Defined Text
USING THE COMBISCOPE INSTRUMENTS 3 - 65 3.11.2.2 Display of user-defined text The DISPlay:WINDow2:TEXT commands allow you to define and clear the user text on the screen area of your CombiScope instrument. After a RST command, the display of the previously defined user text is turned off. PROGRAM EXAMPLE 1: (text as string data) ’Enables display of text CALL Send(0, 8, "DISPlay:WINDow2:TEXT:STATe ON", 1)
Page 85: Print/Plot Functions
3 - 66 USING THE COMBISCOPE INSTRUMENTS 3.12 Print/Plot Functions The HCOPy:DEVice <TYPE> command allows you to select a hardcopy device. The following selections can be made: DEVICE: TYPE: NOTE: Plotter HPGL HPGL plot data format Plotter HP7440 Plotter HP7550 Plotter HP7475A Plotter...
Page 86 USING THE COMBISCOPE INSTRUMENTS 3 - 67 read PLOTTER response 1) Send the query send data plot/print HCOPy:DATA? via the GPIB. data 2) Read the block response PRINTER data via the GPIB. 3) Send the print/plot data part data to the printer/plotter. buffer send HCOPy:DATA?
Page 87: Real-Time Clock
3 - 68 USING THE COMBISCOPE INSTRUMENTS 3.13 Real-Time Clock The real-time clock keeps track of the current date and time. The date and time are stamped on acquired waveforms to be sent to a computer or to be output to a hardcopy device.
Page 88 USING THE COMBISCOPE INSTRUMENTS 3 - 69 PROGRAM EXAMPLE: ’ ***** ’Calibrate the instrument and print the calibration result. ’ ***** ’Starts the calibration CALL Send (0, 8, " * CAL?", 1) ’Disables the time out mechanism CALL IbTMO(0, 0) response$ = "...
Page 89: Status Reporting
3 - 70 USING THE COMBISCOPE INSTRUMENTS 3.15 Status Reporting Status reporting is done via the status reporting system, which is completely described in chapter 5 "THE STATUS REPORTING SYSTEM" of the SCPI Users Handbook. The following figure shows the principle of the standard Status Byte (STB) register and the Service Request Generation (SRQ) mechanism: Standard OPERation...
Page 90: Operation Status Data
USING THE COMBISCOPE INSTRUMENTS 3 - 71 3.15.1.1 Operation status data CONDition filter EVENt ENABle CALibrating RANGing SWEeping wait for TRIGger Digital mode Pass/Fail valid Pass/Fail status STATus:OPERation :CONDition? :PTRansition(?) :NTRansition(?) :EVENt? :ENABle(?) ST7442 Figure 3.24 The Operation Status structure BIT: MEANING: CALibrating This bit is set during the time that the instrument is performing a calibration.
Page 91: Questionable Status Data
3 - 72 USING THE COMBISCOPE INSTRUMENTS 3.15.1.2 Questionable status data CONDition filter EVENt ENABle VOLTage TEMPerature CALibration Overload 50Ω STATus:QUEStionable:CONDition? :PTRansition(?) :NTRansition(?) :EVENt? :ENABle(?) ST7157 Figure 3.25 The Questionable Status structure BIT: MEANING: VOLTage This bit is set if a digital sample value is clipped at the maximum or minimum value while a FETCh? query is done on the sample array.
Page 92: How To Reset The Status Data
USING THE COMBISCOPE INSTRUMENTS 3 - 73 3.15.2 How to reset the status data CLS command allows you to clear the following status data structures: • All event status registers, such as the following: standard event status register (ESR) status byte register (STB) operation event status register (STATus:OPERation:EVENt) questionable event status register (STATus:QUEStionable:EVENt) •...
Page 93: How To Enable Status Reporting
3 - 74 USING THE COMBISCOPE INSTRUMENTS 3.15.3 How to enable status reporting The principle of using the status reporting mechanism is explained by showing two program examples. In the first example the standard Status Byte (STB) is checked to signal "operation completed". In the second example the SRQ mechanism is used to signal "operation completed"...
Page 94: Program Example Using A Service Request (Srq)
USING THE COMBISCOPE INSTRUMENTS 3 - 75 3.15.3.2 Program example using a service request (SRQ) PROGRAM EXAMPLE: In this example the "Service Request" mechanism is used to detect whether or not a "CONFigure:AC" + "INITiate" operation is completed. If completed, an SRQ is generated to continue with fetching and printing the AC-RMS value.
Page 95: How To Report Errors
3 - 76 USING THE COMBISCOPE INSTRUMENTS 3.15.4 How to report errors Instrument errors usually caused by programming or setting errors, can be reported by the instrument during the execution of each command. To make sure that a program is running properly, you should query the instrument for possible errors after every functional command.
Page 96: Error-Reporting Using The Srq Mechanism
USING THE COMBISCOPE INSTRUMENTS 3 - 77 3.15.4.2 Error-reporting using the SRQ mechanism Program an error-reporting routine and use the "Service Request (SRQ) Generation" mechanism to interrupt the execution of the program to execute the error-reporting routine. PROGRAM EXAMPLE: ON PEN GOSUB ErrorCheck PEN ON ’...
Page 97: Saving/Restoring Instrument Setups
3 - 78 USING THE COMBISCOPE INSTRUMENTS 3.16 Saving/Restoring Instrument Setups This level of programming involves all functions in the CombiScopes instruments, i.e., complete instrument setups are processed. This allows you to program one or more functions that are not individually programmable. The following possibilities can be programmed: •...
Page 98: Front Panel Simulation
USING THE COMBISCOPE INSTRUMENTS 3 - 79 3.17 Front Panel Simulation The use of "front panel simulation" commands must be restricted to special applications or front panel functions that are not supported by SCPI commands. Bear in mind the differences between different instruments from the same family, as described in the beginning of this chapter.
Page 99: How To Simulate The Operation Of A Softkey Menu
3 - 80 USING THE COMBISCOPE INSTRUMENTS PROGRAM EXAMPLE: ’Resets the instrument CALL Send(0, 8, " * RST", 1) ’Enables the UTILITY softkey menu CALL Send(0, 8, "SYSTem:KEY 104", 1) ’Selects the PROBE option CALL Send(0, 8, "SYSTem:KEY 2", 1) ’Selects the PROBE CORR option CALL Send(0, 8, "SYSTem:KEY 5", 1) ’Selects the 10:1 option...
Page 100: Functions Not Directly Programmable
USING THE COMBISCOPE INSTRUMENTS 3 - 81 3.18 Functions not Directly Programmable Not all front panel functions are individually programmable with SCPI commands. However, the SYSTem:SET and SAV/ RCL commands can be used to access the following functions: Cursor functions see CURSORS menu (appendix B.2.2) Logic Triggering see TRIGGER menu (appendix B.2.10)
Page 101: Command Reference
COMMAND REFERENCE 4 - 1 4 COMMAND REFERENCE In the first section the notation conventions concerning the specification of the syntax and data types are given. In the second section a summary of all commands and associate parameters is given in alphabetical order. This gives you a quick reference of the SCPI com- mands.
Page 102 End message (via the EOI line of the GPIB interface). META SYMBOL: MEANING: EXPLANATION: Is defined to be Specifies equality. Example: <manufacturer> = FLUKE Alternative Specifies an "either" "or" choice. Example: <result> = 0 | 1 < ... > Non-terminal A non-terminal is a message element...
Page 103: Data Types
COMMAND REFERENCE 4 - 3 Notes: A space character that needs to be part of a message is specified as SP. Spaces within a syntax specification that are not specified as SP are used for formatting purposes to improve the readability; they don’t have any semantical meaning.
Page 104 4 - 4 COMMAND REFERENCE <integer> = <digit> {<digit>} Integer notation that specifies a number. <numeric_data> = <NRf> | <hexadecimal_data> | <octal_data> | <binary_data> Any decimal or non-decimal numeric data type. <hexadecimal_data> = #H <hex_digit> {<hex_digit>} <hex_digit> is one of the characters 0 .. 9 or A .. F. <octal_data>...
Page 105: Command Summary
COMMAND REFERENCE 4 - 5 4.2 Command Summary The following list is a summary of all commands and parameters in alphabetical order, beginning with the common commands. The corresponding queries of the commands are not listed. If a command has no query, this is reported in the column NOTES as "no query".
Page 106 4 - 6 COMMAND REFERENCE COMMAND: PARAMETERS: NOTES: ABORt no query CALCulate<n> <n> =[1] | 2 :DERivative alias = :DIFFerential :POINTs <numeric_data> | MAX | MIN range = 3, 5, .., 129 :STATe <Boolean> :FEED "<trace_name>" <trace_name> = CHn | Mi_n n = 1 ..
Page 107 COMMAND REFERENCE 4 - 7 COMMAND: PARAMETERS: NOTES: DISPlay :BRIGhtness <NRf> | MAXimum | MINimum <NRf> = 0.00 .. 1.00 :MENU [:NAME] TBMode | TRIGger | DMODe | SETups | CURSors | ACQuire | DISPlay | MATH | MEASure | SAVE | RECall | UTIL | VERTical :STATE <Boolean>...
Page 108 4 - 8 COMMAND REFERENCE COMMAND: PARAMETERS: NOTES: INPut<n> <n> = [1] | 2 | 3 | 4 :COUPling AC | DC | GROund :FILTer [:LPASs] [:STATe] <Boolean> :FREQuency? query only response = 2E+7 :IMPedance <NRf> | MAXimum | MINimum <NRf>...
Page 109 COMMAND REFERENCE 4 - 9 COMMAND: PARAMETERS: NOTES: SENSe :AVERage [:STATe] <Boolean> :COUNt <NRf> | MAXimum | MINimum <NRf> = 2, 4, .., 4096 :TYPE? response = SCAL :FUNCtion [:ON] "XTIMe:VOLTage<...>" no query :OFF "XTIMe:VOLTage<...>" no query :STATe? "XTIMe:VOLTage<...>" query only <...>...
Page 110 4 - 10 COMMAND REFERENCE COMMAND: PARAMETERS: NOTES: SYSTem :BEEPer :STATe <Boolean> :COMMunicate :SERial :CONTrol :DTR ON | STANdard :RTS ON | STANdard [:RECeive] | TRANsmit :BAUD <numeric_value> 75 | 110 | 150 | 300 | 600 | 1200 | 2400 | 4800 | 9600 | 19200 | 38400 :BITS...
Page 111 COMMAND REFERENCE 4 - 11 COMMAND: PARAMETERS: NOTES: TRIGger [:SEQuence[1] | STARt] :FILTer :HPASs :FREQuency 30 KHz = HF-reject :STATe <Boolean> :LPASs :FREQuency 0 | 10 | 3E4 0 = DC coupling 10 = AC coupling 30000 = LF-reject :STATe <Boolean>...
Page 112 4 - 12 COMMAND REFERENCE Note 1: <voltage_parameters> = [<expected_voltage> [,<resolution>]] Note 2: <measure_function> <measure_parameters> :AMPLitude [:DC] :FALL :OVERshoot :PREShoot :TIME [<reference_low> [,<reference_high>[,<expected_time> [,<time_resolution>]]] :FREQuency [<expected_frequency> [,<frequency_resolution>]] :HIGH :LOW :MAXimum :MINimum :NDUTycycle [<reference_middle>] :NWIDth [<reference_middle>] :PDUTycycle [<reference_middle>] :PERiod [<expected_period> [,<period_resolution>]] :PTPeak :PWIDth [<reference_middle>]...
Page 113: Command Descriptions
COMMAND REFERENCE 4 - 13 4.3 Command Descriptions The description of corresponding commands and queries is combined. Each command/query description starts on a new page. A description consists of the following parts: COMMAND HEADER Syntax: Specifies the syntax of a command or query (header + parameters) to be placed on the GPIB.
Page 114 4 - 14 COMMAND REFERENCE Errors: Specifies possible error numbers plus their meaning. The error number, plus the corresponding text can be requested by sending the SYSTem:ERROR? or STATus:QUEue? query. Front panel compliance: Specifies the compliance with front panel operations. PROGRAMMING NOTES: •...
Page 115 COMMAND REFERENCE 4 - 15 CAL? CALibration Syntax: CAL? Response: 0 | 1 0 Calibration okay. 1 Calibration not okay. Description: This query performs an automatic internal self-calibration and reports the result of that calibration. No external means or operator interface is needed. The response indicates whether or not the instrument completed the self-calibration without error.
Page 116 4 - 16 COMMAND REFERENCE Clear Status Syntax: Description: CLS command clears the following status data structures: 1. Clears all Event Status Registers, such as the following: - Standard Event Status Register ( ESR?) - Status Byte Register ( STB?) - Operation Event Status register (STATus:OPERation:EVENt) - Questionable Event Status Register (STATus:QUEStionable:EVENt) 2.
Page 117 COMMAND REFERENCE 4 - 17 Event Status Enable Syntax: ESE <numeric_data> Query form: ESE? Response: <integer> Description: The command sets and the query reports the contents of the standard Event Status Enable register (ESE). The range of the 8-bit ESE contents is between 0 and 255 decimal.
Page 118 4 - 18 COMMAND REFERENCE ESR? Event Status Register Syntax: ESR? Response: <integer> Description: ESR? query reports the contents of the standard Event Status Register (ESR) and clears it. The range of the 8-bit ESR contents is between 0 and 255 decimal.
Page 119 The <UFO_id> parameter identifies the version of the Universal Front processor software. Example: → Send IDN? ← Read FLUKE,PM3384B,0,SW3394BIM V4.0 1996-10-02:UHM V1.0:UFO V2.0 Front panel compliance: IDN? query is the remote equivalent of the Maintenance option of the UTILITY menu.
Page 120 4 - 20 COMMAND REFERENCE Operation Complete Syntax: Query form: OPC? Response: Description: OPC command causes the instrument to set the operation complete bit (OPC) in the standard Event Status Register (ESR), when all pending operations have been finished. When the OPC command is received, the OPC bit is set in ESR register when all pending operations have been completed.
Page 121 COMMAND REFERENCE 4 - 21 OPT? Option identification Syntax: OPT? Response: <option> {,<option>} <option> <name>:<serial_nr>:<sw_level> <name> IEEE | EXT | EM | MP <serial_nr> Serial number is always 0. <sw_level> Software level is always 0. Description: OPT? query reports which options are present. If <option>...
Page 122 4 - 22 COMMAND REFERENCE Recall instrument setup Syntax: RCL <numeric_data> Description: RCL command restores instrument settings from one of the internal memory registers 0 .. 10. The settings in memory register 0 are standard settings, which can only be recalled. The settings in the memory registers 1 through 10 are programmable by sending the SAV command.
Page 123 COMMAND REFERENCE 4 - 23 Reset Syntax: Description: RST command resets the instrument. The hardware and software of the instrument is initialized without affecting any of the IEEE interface conditions. The instrument turns into a fixed setup, which is optimized for remote operation. This fixed setup is different from the setup that can be recalled via the front panel softkeys and the SETUPS menu, which is optimized for local control.
Page 124 4 - 24 COMMAND REFERENCE FUNCTION: DEFAULT SETTING(S): TB mode Realtime only OFF Event delay OFF Acquisition length 512 (samples of 16 bits) Trigger Level MAX Acquire Averaging OFF Peak detection OFF Envelope OFF Autoranging attenuators OFF Acquisition Locked Pre-trigger view 50% of MTB (-5 ms) Bandwidth limiter Measure 1 &...
Page 125 COMMAND REFERENCE 4 - 25 Save instrument setup Syntax: SAV <numeric_data> Description: SAV command saves the current instrument settings into one of the internal memory registers 1 .. 10. The settings in memory register 0 are standard settings, which can only be recalled. The settings in the memory registers 0 through 10 can be recalled by sending the RCL command.
Page 126 4 - 26 COMMAND REFERENCE Service Request Enable Syntax: SRE <numeric_data> Query form: SRE? Response: <integer> Description: The command sets and the query reports the contents of the Service Request Enable (SRE) register. The range of the 8-bit ES R contents is between 0 and 255 decimal.
Page 127 COMMAND REFERENCE 4 - 27 STB? Status Byte Syntax: STB? Response: <integer> Description: STB? query reports the contents of the Status Byte register (STB). The range of the 8-bit STB contents is between 0 and 255 decimal. The Status Byte Register contains the summary status of all overlaying status registers and queues.
Page 128 4 - 28 COMMAND REFERENCE Trigger Syntax: Description: TRG command triggers the instrument by generating a Group Execute Trigger (GET) code. Example: → Resets the instrument. Send *RST → GPIB becomes trigger source. Send TRIGger:SOURce BUS → Initiates the instrument once. Send INITiate →...
Page 129 COMMAND REFERENCE 4 - 29 TST? Self-test Syntax: TST? Response: 0 | 1 0 Self-test okay. 1 Self-test not okay. Description: TST? query initiates a RAM/ROM test in the instrument and returns the result of the test. The result of the RAM/ROM test is 0, if the test is completed without detecting any error.
Page 130 4 - 30 COMMAND REFERENCE Wait-to-continue Syntax: Description: WAI command prevents the instrument to execute any further command until all previous commands and queries have been completed. The command is used to force sequential execution of commands by the instrument. On receipt of the WAI command, the instrument executes all pending commands and queries before it executes the next command or query.
Page 131 COMMAND REFERENCE 4 - 31 ABORt Syntax: ABORt Description: The ABORt command resets the trigger system and places it in the "IDLE" state. Pending actions that were already started are finished immediately. The ABORt command is not finished until the pending actions have been terminated. Note: The commands RST and ABORt have the same effect on the trigger...
Page 132 4 - 32 COMMAND REFERENCE CALCulate<n>:DERivative:POINts CALCulate<n>:DERivative:STATe Syntax: CALCulate<n>:DERivative:POINts <numeric_data> | MAXimum | MINimum CALCulate<n>:DERivative:STATe <Boolean> <n> [1] | 2 <numeric_data> 3, 5, 7, ..., 127, 129 Alias: An alias for :DERivative is :DIFFerential. Query form: CALCulate<n>:DERivative:POINts? [MINimum | MAXimum] Response: 3 | 5 | ..
Page 133 COMMAND REFERENCE 4 - 33 CALCulate<n>:FEED Syntax: CALCulate<n>:FEED "<trace_name>" Note: The parameter "<trace_name>" is <string_data>. Therefore, it may be specified between single quotes as well, i.e., ’<trace_name>’. <n> [1] | 2 <trace_name> A trace name which is a predefined <acquisition_trace> or <memory_trace>. <acquisition_trace>...
Page 134 4 - 34 COMMAND REFERENCE CALCulate<n>:FILTer[:GATE]:FREQuency:POINts CALCulate<n>:FILTer[:GATE]:FREQuency:STATe Syntax: CALCulate<n>:FILTer[:GATE]:FREQuency:POINts <numeric_data> | MAXimum | MINimum CALCulate<n>:FILTer[:GATE]:FREQuency:STATe <Boolean> <n> [1] | 2 <Numeric_data> 3, 5, 7, .. , 39, 41 Query form: CALCulate<n>:FILTer[:GATE]:FREQuency:POINts? [MINimum | MAXimum] Response: 3 | 5 | .. | 41 If MINimum was specified, 3 is returned.
Page 135 COMMAND REFERENCE 4 - 35 CALCulate<n>:INTegral:STATe Syntax: CALCulate<n>:INTegral:STATe <Boolean> <n> [1] | 2 Query form: CALCulate<n>:INTegral:STATe? Response: 0 | 1 Integrate function turned off. Integrate function turned on. Description: This command switches the integrate function on or off. The result of the integrate function is stored in M1_n for CALCulate1 and in M2_n for CALCulate2 depen- dent on the input source CHn or Mi_n (n = 1, 2, 3, 4).
Page 136 4 - 36 COMMAND REFERENCE CALCulate<n>:MATH[:EXPRession] Syntax: CALCulate<n>:MATH[:EXPRession] ( <trace_name> <operation> <trace_name> ) <n> [1] | 2 <trace_name> A trace name which is a predefined <acquisition_trace> or <memory_trace>. <acquisition_trace> CH1 | CH2 | CH3 | CH4 <memory_trace> Mi_1 | Mi_2 | Mi_3 | Mi_4 Note: - i = 1 ..
Page 137 COMMAND REFERENCE 4 - 37 CALCulate<n>:MATH:STATe Syntax: CALCulate<n>:MATH:STATe <Boolean> <n> [1] | 2 Query form: CALCulate<n>:MATH:STATe? Response: 0 | 1 Mathematics function turned off. Mathematics function turned on. Description: This command switches the specified mathematics function on or off. If the mathematics function is switched on, the internal scale and offset are reset to initial values.
Page 138 4 - 38 COMMAND REFERENCE CALCulate<n>:TRANsform:FREQuency:STATe CALCulate<n>:TRANsform:FREQuency:TYPE CALCulate<n>:TRANsform:FREQuency:WINDow Syntax: CALCulate<n>:TRANsform:FREQuency:STATe <Boolean> CALCulate<n>:TRANsform:FREQuency:TYPE ABSolute | RELative CALCulate<n>:TRANsform:FREQuency:WINDow RECTangular | HAMMing | HANNing <n> [1] | 2 Query form: CALCulate<n>:TRANsform:FREQuency:STATe? Response: 0 | 1 Query form: CALCulate<n>:TRANsform:FREQuency:TYPE? Response: ABS | REL Query form: CALCulate<n>:TRANsform:FREQuency:WINDow? RECT | HAMM | HANN Response: Description:...
Page 139 COMMAND REFERENCE 4 - 39 Example: → Send CALCulate2:TRANsform:FREQuency:TYPE RELative Selects relative MATH2-FFT calculation. → Send CALCulate2:TRANsform:FREQuency:WINDow HANNing Selects MATH2-FFT-HANNing window. → Send CALCulate2:TRANsform:FREQuency:STATe ON Switches MATH2-FFT on. Front panel compliance: The CALCulate1 and CALCulate2 commands use the MATH1 and MATH2 features of the CombiScope instrument.
Page 140 4 - 40 COMMAND REFERENCE CALCulate<n>:TRANsform:HISTogram:STATe Syntax: CALCulate<n>:TRANsform:HISTogram:STATe <Boolean> <n> [1] | 2 Query form: CALCulate<n>:TRANsform:HISTogram:STATe? Response: 0 | 1 Histogram function turned off. Histogram function turned on. Description: This command switches the HISTogram function on or off. The result of the histogram function is stored in M1_1 for CALCulate1 and in M2_1 for CALCulate2.
Page 141 COMMAND REFERENCE 4 - 41 CALibration[:ALL] Syntax: CALibration[:ALL] Query form: CALibration[:ALL]? Response: 0 | 1 Description: The CALibration command performs an automatic internal self-calibration. No external means or operator interface is needed. The CALibration command is an overlapped command, which means that during calibration the "Calibrating" bit (0) in the OPERation status can be read to check whether calibration has finished or not.
Page 142 4 - 42 COMMAND REFERENCE Example: → Resets the instrument. Send → Starts auto calibration. Send CALibration → Requests for oper. conditions. Send STATus:OPERation:CONDition? ← Reads condition register. Read <cond_reg> Loops while calibration busy. WHILE (bit 0 of <cond_reg) = 1) →...
Page 143 COMMAND REFERENCE 4 - 43 CONFigure Syntax: CONFigure[:VOLTage]<measure_function> [[ (<voltage_parameters>),] <measure_parameters>] [,<channel_list>] The syntax elements are specified with the MEASure? query. Description: The CONFigure command is part of the measurement instruction set. It sets up the instrument in order to perform the measurement as specified by the <measure_function>...
Page 144 4 - 44 COMMAND REFERENCE Example 1: → CONFigure:VOLTage:AC 0.6,(@2) Configures AC-RMS channel 2, Send expected voltage 600 mV. → Channel 2 AC coupled. Send INPut2:COUPling AC → Initiates + fetches AC-RMS Send READ:AC? (@2) value. ← Read <first measured AC-RMS value> →...
Page 145 COMMAND REFERENCE 4 - 45 DISPlay:BRIGhtness Syntax: DISPlay:BRIGhtness <Numeric_data> | MINimum | MAXimum <Numeric_data> 0.0 .. 1.0 MINimum Equals 0.0 Trace display is fully blanked. MAXimum Equals 1.0 Trace display has full intensity. Query form: DISPlay:BRIGhtness? [MINimum | MAXimum] Response: <NR3>...
Page 146 4 - 46 COMMAND REFERENCE DISPlay:MENU[:NAME] Syntax: DISPlay:MENU[:NAME] <character_data> <character_data> FRONT PANEL SOFTKEY NAME TBMode TB MODE (main time base) TRIGger TRIGGER DMODe (delayed time base) SETups SETUPS CURSors CURSORS ACQuire ACQUIRE DISPlay DISPLAY MATH MATH MEASure MEASURE SAVE SAVE RECall RECALL UTIL...
Page 147 COMMAND REFERENCE 4 - 47 DISPlay:MENU:STATe Syntax: DISPlay:MENU:STATe <Boolean> Query form: DISPlay:MENU:STATe? Response: 0 | 1 Display turned off. Display turned on. Description: Switches the display of the softkey menu field on or off. After a RST command, the display is turned off. Example: →...
Page 148 4 - 48 COMMAND REFERENCE DISPlay:WINDow[1]:TEXT<n>:DATA? Syntax: DISPlay:WINDow[1]:TEXT<n>:DATA? Indicates that the measurement result field is window 1. <n> 1 | 2 | 10 | 11 | 12 | 13 | 20 | 21 | 30 | 40 | 51 | 52 | 60 | 61 MEAS1 result is returned.
Page 149 COMMAND REFERENCE 4 - 49 The measurement data functions must be enabled first, or the error message -221 "Settings conflict" is generated. If the oscilloscope is in the analog mode, the error message -221 "Settings conflict;Digital mode required" is generated. The following measurement data values can be selected by specifying the number <n>...
Page 150 4 - 50 COMMAND REFERENCE DISPlay:WINDow2:TEXT[1]:CLEar Syntax: DISPlay:WINDow2:TEXT[1]:CLEar Indicates that the user text field is window 2. Is optional and has no meaning. Description: This command clears the contents of the user text field from the screen of the oscilloscope. The result is that the user text is no longer displayed. Example: →...
Page 151 COMMAND REFERENCE 4 - 51 DISPlay:WINDow2:TEXT[1]:DATA Syntax: DISPlay:WINDow2:TEXT[1]:DATA <string_data> | <block_data> Indicates that the user text field is window 2. <string_data> Maximum 64 characters. Examples: "this is a string" ’this also’ <block_data> Maximum 64 data bytes. ↓ Examples: #01.25 k (indefinite length) ↓...
Page 152 4 - 52 COMMAND REFERENCE dec sym dec sym dec sym dec sym dec sym dec sym dec sym dec sym " ° & µ ’ Ω ↑ ↓ < > Table 4.1 Display character set for CombiScope instruments Notes: - The left value (dec) is the decimal value of the code and the right value (sym) is the oscilloscope symbol.
Page 153 COMMAND REFERENCE 4 - 53 DISPlay:WINDow2:TEXT[1]:STATe Syntax: DISPlay:WINDow2:TEXT[1]:STATe <Boolean> Indicates that the user text field is window 2. Query form: DISPlay:WINDow2:TEXT[1]:STATe? Response: 0 | 1 Display turned off. Display turned on. Description: Switches the display of the user text field on or off. After a RST command, the display of user text is turned off.
Page 154 4 - 54 COMMAND REFERENCE FETCh? Syntax: FETCh[:VOLTage]<measure_function>? [[ (<voltage_parameters>),] <measure_parameters>] [,<channel_list> | <trace_list>] <trace_list> = (@<trace_name>) <trace_name> = <acquisition_trace> | <memory_trace> <acquisition_trace> = CH1 | CH2 | CH3 | CH4 These are predefined names for traces that contain the acquisition result of the input channels 1 to 4.
Page 155 COMMAND REFERENCE 4 - 55 Description: The FETCh? queries are part of the measurement instruction set. They return the signal characteristic from the last initiated measurement, as specified by the <measure function> part of the query header. An initiate command must precede a FETCh? query. The initiate command may be given either explicitly as INITiate[:IMMediate] command, or explicitly by a READ? or MEASure? query.
Page 156 4 - 56 COMMAND REFERENCE Example 1: → MEASure:VOLTage:AC? 0.6,(@2) Measures AC- RMS on Send channel 2, expected voltage 600 mV. ← Read <the measured AC-RMS value> → Fetches the DC Send FETCh:DC? (@2) component. ← Read <the measured DC component> →...
Page 157 COMMAND REFERENCE 4 - 57 FORMat[:DATA] Syntax: FORMat[:DATA] INTeger[, 8 | 16] INTeger,8 Trace point of 8 bits (one byte). INTeger,16 Trace point of 16 bits (two bytes). Query form: FORMat[:DATA]? Response: INT,8 | INT,16 INT,8 Trace point consists of one byte. INT,16 Trace point consists of two bytes.
Page 158 4 - 58 COMMAND REFERENCE HCOPy:DATA? Syntax: HCOPy:DATA? Response: <indefinite_block> Description: This query returns a data block of indefinite length containing a hardcopy of the picture on the oscilloscope display, according to the current printer/plotter selections. These selections can be made through the UTIL - PRINT & PLOT softkey menu options.
Page 159 COMMAND REFERENCE 4 - 59 HCOPy:DEVice Syntax: HCOPy:DEVice HPGL | HP7440 | HP7550 | HP7475A| HP7470A | PM8277 | PM8278 | FX80 | LQ1500 | HP2225 | HPLASER | HP540 | DUMP_M1 HPGL HPGL plot data format. HP7440, HP7550, HP7475A, HP7470A, Plotters.
Page 160 4 - 60 COMMAND REFERENCE INITiate:CONTinuous Syntax: INITiate:CONTinuous <Boolean> Query form: INITiate:CONTinuous? Response: 1 | 0 Continuous automatic initiation is ON. Continuous automatic initiation is OFF. Description: The INITiate:CONTinuous command selects whether the trigger system is continuously initiated or not. When INITiate:CONTinuous is ON, the trigger system is continuously initiating acquisitions.
Page 161 COMMAND REFERENCE 4 - 61 INITiate[:IMMediate] Syntax: INITiate[:IMMediate] Description: This command causes the trigger system to be initiated once only, i.e., initiates one acquisition cycle. The actual acquisition starts when all trigger conditions have been met. After the acquisition has completed, the trigger system returns to the IDLE state.
Page 162 4 - 62 COMMAND REFERENCE INPut<n>:COUPling Syntax: INPut<n>:COUPling AC | DC | GROund <n> [1] | 2 | 3 | 4 Query form: INPut<n>:COUPling? <n> [1] | 2 | 3 | 4 Response: AC | DC | GRO Description: Selects the vertical input coupling of a specified <n> input channel. If AC is specified, the DC offset value is excluded.
Page 163 COMMAND REFERENCE 4 - 63 INPut<n>:FILTer[:LPASs][:STATe] INPut<n>:FILTer[:LPASs]:FREQuency? Syntax: INPut<n>:FILTer[:LPASs][:STATe] <Boolean> <n> [1] | 2 | 3 | 4 INPut<n>:FILTer[:LPASs]:FREQuency? [MINimum | MAXimum] MINimum Fixed at 20 MHz MAXimum Fixed at 20 MHz Note: Channel 3 is not applicable for PM33x0B. 2.00E+07 Response: Query form: INPut<n>:FILTer[:LPASs][:STATe]?
Page 164 4 - 64 COMMAND REFERENCE INPut<n>:IMPedance Syntax: INPut<n>:IMPedance <NRf> | MINimum | MAXimum <n> [1] | 2 | 3 | 4 <NRf> 50 | 1E6 Ω <MINimum> Equals 5.00E+01 (50 Ω <MAXimum> Equals 1.00E+06 (1 M Note: Channel 3 is not applicable for PM33x0B. Query form: INPut<n>:IMPedance? [MINimum] | [MAXimum] <n>...
Page 165 COMMAND REFERENCE 4 - 65 INPut<n>:POLarity Syntax: INPut<n>:POLarity NORMal | INVerted <n> 2 | 4 Note: Input 4 is not applicable for PM33x0B. Query form: INPut<n>:POLarity? <n> 2 | 4 Response: NORM | INV Description: The INPut<n>:POLarity command sets the polarity of the signal on the input channels two and four.
Page 166 4 - 66 COMMAND REFERENCE INSTrument:NSELect INSTrument[:SELect] Syntax: INSTrument:NSELect <NRf> | MINimum | MAXimum INSTrument[:SELect] DIGital | ANALog <NRf> 1 | 2 1 | MINimum The digital mode (ANALOG key) is activated. 2 | MAXimum The analog mode is activated. DIGital The digital mode (ANALOG key) is activated.
Page 167 COMMAND REFERENCE 4 - 67 MEASure? Syntax: MEASure[:VOLTage]<measure_function>? [[ (<voltage_parameters>),] <measure_parameters>] [,<channel_list>] <voltage_parameters> = [<expected_voltage> [,<resolution>]] <expected_voltage> = <NRf> | DEFault Specifies the voltage that is expected at the input. <resolution> = <NRf> | DEFault This parameter may be added for reasons of compatibility with similar...
Page 168 4 - 68 COMMAND REFERENCE :FALL:OVERshoot No parameters. Measures the overshoot of the first falling edge of a waveform, expressed as a percentage of the waveform AMPLitude. The fall overshoot is the difference between the LOW value and the MINimum negative peak value to which the signal initially falls, as shown in figure 3.2.
Page 169 COMMAND REFERENCE 4 - 69 :MINimum No parameters. Measures the MINimum instantaneous voltage value of the waveform. The unit of MINimum is volt. :NDUTycycle <reference_middle> Measures the negative duty cycle. The negative duty cycle is the ratio (percentage) of the negative width (NWIDth) and the PERiod of the waveform, as shown in figure 3.2.
Page 170 4 - 70 COMMAND REFERENCE :TMINimum No parameters. Measures the time of the first occurrence of the MINimum voltage of the input signal. The unit of TMINimum is seconds. :RISE:OVERshoot No parameters. Measures the overshoot of the first rising edge of a waveform, expressed as a percentage of the waveform AMPLitude.
Page 171 COMMAND REFERENCE 4 - 71 <expected_time> = <NRf> | DEFault Specifies the time value that is expected to be measured. The unit of <expected_time> is second. <time_resolution> = <NRf> | DEFault Specifies the resolution of the time measurement to be executed.
Page 172 4 - 72 COMMAND REFERENCE Limitations: The oscilloscope is only able to calculate rise and fall time characteristics, if the <low_reference> and <high_reference> parameters are limited to 1/8 division from their maximum and minimum. The limit of 0.125 divisions (noise level) depends on the vertical sensitivity of the top-to-top value (PTPeak) of the actual signal and is calculated as follows: <low>...
Page 173 COMMAND REFERENCE 4 - 73 Description: The MEASure? queries are part of the measurement instruction set. They provide an automatic measurement of the signal characteristics as specified by the <measure_function> part in the query header. In one operation, the instrument is configured or set up, the acquisition initiated, and the result returned.
Page 174 4 - 74 COMMAND REFERENCE READ? Syntax: READ[:VOLTage]<measure_function>? [[ (<voltage_parameters>),] <measure_parameters>] [,<channel_list>] The syntax elements are specified with the MEASure? query. Response: <NR3> Example: <1.25E-01> = 0.125 Description: The READ? queries are part of the measurement instruction set. They start a measurement and return the signal characteristic that is specified by the <measure function>...
Page 175 COMMAND REFERENCE 4 - 75 Note: Because the READ? query leaves instrument settings unaffected, it can very well be used as follows to read a measured value within a cursor limited acquisition area: Press the CURSORS key on the front panel to enable the use of cursors.
Page 176 4 - 76 COMMAND REFERENCE SENSe:AVERage[:STATe] Syntax: SENSe:AVERage[:STATe] <Boolean> Query form: SENSe:AVERage[:STATe]? Response: 0 | 1 AVERAGE function switched off. AVERAGE function switched on. Description: Switches the preprocessing AVERAGE function on or off. If switched on, measurement values and acquisition traces are averaged according to the average count factor (SENSe:AVERage:COUnt).
Page 177 COMMAND REFERENCE 4 - 77 SENSe:AVERage:COUNt SENSe:AVERage:TYPE? Syntax: SENSe:AVERage:COUNt <NRf> <NRf> 2 | 4 | 8 | 16 | ... | 2048 | 4096 SENSe:AVERage:TYPE? Response: SCAL Query form: SENSe:AVERage:COUNt? [MINinum | MAXimum] Response: 2 | 4 | 8 | 16 | ... | 2048 | 4096 If MINimum was specified, 2 is returned.
Page 178 4 - 78 COMMAND REFERENCE SENSe:FUNCtion:OFF SENSe:FUNCtion[:ON] SENSe:FUNCtion:STATe? Syntax: SENSe:FUNCtion:OFF "XTIMe:VOLTage<n>" SENSe:FUNCtion:OFF "XTIMe:VOLTage:SUM <i,j>" SENSe:FUNCtion[:ON] "XTIMe:VOLTage<n>" SENSe:FUNCtion[:ON] "XTIMe:VOLTage:SUM <i,j>" <n> [1] | 2 | 3 | 4 1 = CH1, 2 = CH2, 3 = CH3, 4 = CH4 Note: CH3 not applicable for PM33x0B.
Page 179 COMMAND REFERENCE 4 - 79 The parameters "XTIMe:VOLTage<n>" and "XTIMe:VOLTage:SUM <i,j>" are of the type <string_data> (specified between double or single quotes). Execution error -221 "Settings conflict" is generated, if the execution of a command causes the last input channel or the addition of two input channels to be turned off. In the analog mode, the added trace (e.g., CH1+CH2) as well as both channel traces (e.g., CH1, CH2) are displayed.
Page 180 4 - 80 COMMAND REFERENCE SENSe:SWEep:OFFSet:TIME Syntax: SENSe:SWEep:OFFSet:TIME <NRf> | MINimum | MAXimum <NRf> The trigger delay time in seconds. A negative value causes a pre-trigger view time, whereas a positive value causes a post-trigger delay time. MINimum Selects the minimum possible pre-trigger view time. MAXimum Selects the maximum possible post-trigger delay time.
Page 181 COMMAND REFERENCE 4 - 81 SENSe:SWEep:PDETection[:STATe] Syntax: SENSe:SWEep:PDETection[:STATe] <Boolean> Query form: SENSe:SWEep:PDETection[:STATe]? Response: 0 | 1 0 Peak detection switched off. 1 Peak detection switched on. Description: Switches peak detection on or off. If peak detection is switched on, the MTB range is limited to sequential sampling from 250 nanoseconds through 200 seconds per division (for MTB ranges, refer to the SENSe:SWEep:TIME command).
Page 182 4 - 82 COMMAND REFERENCE SENSe:SWEep:REALtime[:STATe] Syntax: SENSe:SWEep:REALtime[:STATe] <Boolean> Query form: SENSe:SWEep:REALtime[:STATe]? Response: 0 | 1 Real-time mode switched off. Real-time mode switched on. Description: Switches the ’real- time’ mode of the acquisition on or off. If the ’real-time’ sampling mode is switched on, the MTB range is limited to sequential sampling from 250 nanoseconds through 200 seconds per division (for MTB ranges, refer to the SENSe:SWEep:TIME command).
Page 183 COMMAND REFERENCE 4 - 83 SENSe:SWEep:TIME Syntax: SENSe:SWEep:TIME <NRf> | MINimum | MAXimum <NRf> The sweep time in seconds. MINimum Selects the minimum possible sweep time. MAXimum Selects the maximum possible sweep time. Query form: SENSe:SWEep:TIME? [MINimum | MAXimum] Response: <NR3>...
Page 184 4 - 84 COMMAND REFERENCE Limitations: • The MTB value of 2 ns is only possible for the PM339xB CombiScope instruments. • If SENSe:SWEep:REALtime is ON, the MTB range is from 200 seconds to 250 nanoseconds, and sequential sampling is not guaranteed. In a similar way, the time value Ts that is associated with a trace sample point can be calculated from the following expression: Ts = <sample_index>...
Page 185 COMMAND REFERENCE 4 - 85 SENSe:SWEep:TIME:AUTO Syntax: SENSe:SWEep:TIME:AUTO <Boolean> Query form: SENSe:SWEep:TIME:AUTO? Response: 0 | 1 0 Autoranging MTB switched off. 1 Autoranging MTB switched on. Description: Switches the autoranging function of the Main Time Base (MTB) on or off. In the analog mode, the error message -221 "Settings conflict;Digital mode required"...
Page 186 4 - 86 COMMAND REFERENCE SENSe:VOLTage<n>[:DC]:RANGe:AUTO Syntax: SENSe:VOLTage<n>[:DC]:RANGe:AUTO <Boolean> <n> [1] | 2 | 3 | 4 Note: Channel 3 and 4 not applicable for PM33x0B. Query form: SENSe:VOLTage<n>[:DC]:RANGe:AUTO? Response: 0 | 1 Autoranging attenuator channel <n> switched off. Autoranging attenuator channel <n> switched on. Description: Switches the autoranging function of channel <n>...
Page 187 COMMAND REFERENCE 4 - 87 SENSe:VOLTage<n>[:DC]:RANGe:OFFSet Syntax: SENSe:VOLTage<n>[:DC]:RANGe:OFFSet <NRf> | MINimum | MAXimum <n> [1] | 2 | 3 | 4 Note: Channel 3 and 4 not applicable for PM33x0B. <NRf> The vertical offset for channel <n> in volts. MINimum Selects the minimum possible vertical offset.
Page 188 4 - 88 COMMAND REFERENCE SENSe:VOLTage<n>[:DC]:RANGe:PTPeak Syntax: SENSe:VOLTage<n>[:DC]:RANGe:PTPeak <NRf> | MINimum | MAXimum <n> [1] | 2 | 3 | 4 Note: Channel 3 not applicable for PM33x0B. <NRf> The vertical sensitivity for channel <n> in peak-to- peak volts, expressed in full scale (8 divisions). MINimum Selects the minimum possible peak-to-peak value.
Page 189 COMMAND REFERENCE 4 - 89 After a RST command, the peak-to-peak value is reset as follows: For channel 1 to 1.6V: vertical sensitivity = 200 mV/div. For channel 2 to 0.4V: vertical sensitivity = 50 mV/div. For channel 3 and 4 to 8V: vertical sensitivity = 1 V/div. Note: If a 10:1 probe is connected to a channel, the peak-to-peak value is 10 times higher.
Page 190 4 - 90 COMMAND REFERENCE STATus:OPERation:CONDition? STATus:OPERation:ENABle STATus:OPERation[:EVENt]? STATus:OPERation:NTRansition STATus:OPERation:PTRansition Syntax: STATus:OPERation:CONDition? STATus:OPERation:ENABle <NRf> STATus:OPERation[:EVENt]? STATus:OPERation:NTRansition <NRf> STATus:OPERation:PTRansition <NRf> <NRf> Range from 0 to 32767. Query form: STATus:OPERation:ENABle? STATus:OPERation:NTRansition? STATus:OPERation:PTRansition? Response: <NR1> Description: The STATus:OPERation:CONDition? query reports the contents of the operation condition register.
Page 191 COMMAND REFERENCE 4 - 91 The STATus:OPERation:PTRansition command sets the contents of the positive transition filter of the operation register structure. The positive transition filter specifies which bits in the operation condition register, that make a positive transition (0 -> 1), set the corresponding bit in the operation event register. For example, when you set bit 2 in this filter, it will set bit 2 in the operation event register at the time bit 2 in the operation condition register is set (changed from 0 to 1).
Page 192 4 - 92 COMMAND REFERENCE STATus:PRESet Syntax: STATus:PRESet Description: The PRESet command is used to set the status data structure in such a way, that device-dependent events are reported at a higher level through the mandatory part of the status reporting mechanism. The PRESet command affects only the enable registers and the transition filters for the device-dependent status data structures.
Page 193 COMMAND REFERENCE 4 - 93 STATus:QUEStionable:CONDition? STATus:QUEStionable:ENABle STATus:QUEStionable[:EVENt]? STATus:QUEStionable:NTRansition STATus:QUEStionable:PTRansition Syntax: STATus:QUEStionable:CONDition? STATus:QUEStionable:ENABle <NRf> STATus:QUEStionable[:EVENt]? STATus:QUEStionable:NTRansition <NRf> STATus:QUEStionable:PTRansition <NRf> <NRf> Range from 0 to 32767. Query form: STATus:QUEStionable:ENABle? STATus:QUEStionable:NTRansition? STATus:QUEStionable:PTRansition? Response: <NR1> Description: The STATus:QUEStionable:CONDition? query reports the contents of the questionable condition register.
Page 194 4 - 94 COMMAND REFERENCE The STATus:QUEStionable:PTRansition command sets the contents of the positive transition filter of the questionable register structure. The positive transition filter specifies which bits in the questionable condition register, that make a positive transition (0 -> 1), set the corresponding bit in the questionable event register.
Page 195 COMMAND REFERENCE 4 - 95 STATus:QUEue[:NEXT]? Syntax: STATus:QUEue[:NEXT]? Response: <error_number>,"<error_description>" <error_number> A predefined number. If 0 (zero) is returned, there are no errors in the queue. <error_description> A short description of the error. When there are no errors in the queue, the description is "No error".
Page 196 4 - 96 COMMAND REFERENCE SYSTem:BEEPer SYSTem:BEEPer:STATe Syntax: SYSTem:BEEPer SYSTem:BEEPer:STATe <Boolean> Query form: SYSTem:BEEPer:STATe? Response: 0 | 1 Beeper disabled. Beeper enabled. Description: The SYST:BEEP command causes a beep of about 1 second to be generated by the instrument, even if the SYSTem:BEEPer:STATe is OFF. The SYST:BEEP:STAT command enables or disables the beeper of the instrument.
Page 197 COMMAND REFERENCE 4 - 97 SYSTem:COMMunicate:SERial:CONTrol:DTR SYSTem:COMMunicate:SERial:CONTrol:RTS Syntax: SYSTem:COMMunicate:SERial:CONTrol:DTR ON | STANdard SYSTem:COMMunicate:SERial:CONTrol:RTS ON | STANdard Selects the "3 wire" option. The DTR or RTS line is always asserted. STANdard Selects the "7 wire" option. Query form: SYSTem:COMMunicate:SERial:CONTrol:DTR? SYSTem:COMMunicate:SERial:CONTrol:RTS? Response: ON | STAN "3 wire"...
Page 198 4 - 98 COMMAND REFERENCE SYSTem:COMMunicate:SERial[:RECeive]:BAUD SYSTem:COMMunicate:SERial:TRANsmit:BAUD SYSTem:COMMunicate:SERial[:RECeive]:BITS SYSTem:COMMunicate:SERial:TRANsmit:BITS SYSTem:COMMunicate:SERial[:RECeive]:PACE SYSTem:COMMunicate:SERial:TRANsmit:PACE SYSTem:COMMunicate:SERial[:RECeive]:PARity[:TYPE] SYSTem:COMMunicate:SERial:TRANsmit:PARity[:TYPE] Syntax: SYSTem:COMMunicate:SERial[:RECeive]:BAUD <baudrate> SYSTem:COMMunicate:SERial:TRANsmit:BAUD <baudrate> <baudrate> 75 | 110 | 150 | 300 | 600 | 1200 | 2400 | 4800 | 9600 | 19200 | 38400 | MIN | MAX SYSTem:COMMunicate:SERial[:RECeive]:BITS 7 | 8 SYSTem:COMMunicate:SERial:TRANsmit:BITS 7 | 8 SYSTem:COMMunicate:SERial[:RECeive]:PACE XON | NONE...
Page 199 COMMAND REFERENCE 4 - 99 Query form: SYSTem:COMMunicate:SERial[:RECeive]:PACE? SYSTem:COMMunicate:SERial:TRANsmit:PACE? Response: XON | NONE X-on/X-off handshake enabled. NONE No X-on/X-off handshaking. Query form: SYSTem:COMMunicate:SERial[:RECeive]:PARity[:TYPE]? SYSTem:COMMunicate:SERial:TRANsmit:PARity[:TYPE]? Response: EVEN | ODD | NONE Description: BAUD sets the baudrate of the EIA-232-D (RS-232-C) interface for both the receive and transmit channel.
Page 200 4 - 100 COMMAND REFERENCE SYSTem:DATE Syntax: SYSTem:DATE <year>,<month>,<day> <year> <NRf> | MINimum | MAXimum Range from 1992 to 2091. <month> <NRf> | MINimum | MAXimum Range from 1 to 12. <day> <NRf> | MINimum | MAXimum Range from 1 to 31. Query form: SYSTem:DATE? [MINimum | MAXimum , MINimum | MAXimum, MINimum | MAXimum] Response:...
Page 201 COMMAND REFERENCE 4 - 101 SYSTem:ERRor? Syntax: SYSTem:ERRor? Response: <error_number>,"<error_description>" <error_number> A predefined number. If 0 (zero) is returned, there are no errors in the queue. <error_description> A short description of the error. When there are no errors in the queue, the description is "No error".
Page 202 4 - 102 COMMAND REFERENCE SYSTem:KEY Syntax: SYSTem:KEY <NRf> | MINimum | MAXimum <NRf> Reference number to a key: 1, 2, 3, 4, 5, 6: softkey-1 (top) to softkey-6 (bottom) 101, 102, 103, etc.: top row of keys (left to right) •...
Page 203 COMMAND REFERENCE 4 - 103 FRONT PANEL KEY <NR1> FRONT PANEL KEY <NR1> EXCEPTIONS Softkey 1 (top) VERT MENU Softkey 2 AVERAGE Softkey 3 TRIG 1 Softkey 4 TRIG 2 Softkey 5 TRIG 3 only for PM33x4B EXT TRIG for PM33x0B Softkey 6 (bottom) TRIG 4 AUTOSET...
Page 204 4 - 104 COMMAND REFERENCE Example 1: → Simulates the pressing of AUTOSET. Send SYSTem:KEY 101 → Send SYSTem:KEY? ← Returns the last key simulation. Read Example 2: → Resets the instrument. Send *RST → Enables UTILITY softkey menu. Send DISPlay:MENU UTIL →...
Page 205 COMMAND REFERENCE 4 - 105 SYSTem:SET Syntax: SYSTem:SET <indefinite_block> Query form: SYSTem:SET? [<node_nr> | MINimum | MAXimum] <node_nr> A number specifying which node settings. The following nodes are supported: End node indicator. 1|2|3|4 Channel 1 (MINimum) / 2 / 3 / 4 settings Probe scale settings Common vertical settings Horizontal settings...
Page 206 4 - 106 COMMAND REFERENCE Limitations: For the PM33x0B CombiScope instruments: Input channel 3 (CH3) is not applicable. Input channel 4 (CH4) is limited to external trigger view. Example: → Queries for cursor instrument settings. Send SYSTem:SET? 32 ← Reads cursor instrument settings. Read <curs_setup>...
Page 207 COMMAND REFERENCE 4 - 107 SYSTem:TIME Syntax: SYSTem:TIME <hour>,<minute>,<second> <hour> <NRf> | MINimum | MAXimum Range from 0 to 23. <minute> <NRf> | MINimum | MAXimum Range from 0 to 59. <second> <NRf> | MINimum | MAXimum Range from 0 to 59. Query form: SYSTem:TIME? [MINimum | MAXimum , MINimum | MAXimum , MINimum | MAXimum] Response:...
Page 208 4 - 108 COMMAND REFERENCE SYSTem:VERSion? Syntax: SYSTem:VERSion? Response: YYYY.V YYYY The year number of the SCPI version. The approved revision number within the year. Description: Reports the version of the SCPI command set to which your instrument complies. The year and revision number within that year is returned, e.g., 1992.0. RST command doesn’t change the current SCPI version.
Page 209 COMMAND REFERENCE 4 - 109 TRACe:COPY Syntax: TRACe:COPY <destination_trace>,<source_trace> Alias: DATA:COPY <destination_trace>,<source_trace> <source_trace> CHn | Mi_n <destination_trace> Mi_n n = 1 .. 4 i = 1 .. 8 (standard memory) i = 1 .. 50 (extended memory) Description: Copies a trace from one trace memory (source) to another (destination). The contents of the <source_trace>...
Page 210 4 - 110 COMMAND REFERENCE TRACe[:DATA] Syntax: TRACe[:DATA] <destination_trace> , <NRf> | <definite_block> Alias: DATA[:DATA] <destination_trace> , <NRf> | <definite_block> <destination_trace> Mi_n n = 1 .. 4 i = 1 .. 8 (standard memory) i = 1 .. 50 (extended memory) <NRf>...
Page 211 COMMAND REFERENCE 4 - 111 Description: The TRACe? query reads a binary trace block from channel acquisition memory (CH1 to CH4) or from register memory (M1 to M8 for standard memory and M9 to M50 for extended memory). The TRACe command writes a binary trace block to register memory (M1 to M8 for standard memory and M9 to M50 for extended memory).
Page 212 4 - 112 COMMAND REFERENCE → Requests channel 1 trace. Send TRACe? CH1 ← Reads channel 1 trace. Read <block_data> Determine nr.of.samples from <block_data>. → Queries peak-to-peak. Send SENSe:VOLTage:RANGe:PTPeak? ← Reads peak-to-peak. Read <peak-to-peak> → Queries offset. Send SENSe:VOLTage:RANGe:OFFSet? ← Reads offset.
Page 213 COMMAND REFERENCE 4 - 113 TRACe:POINts Syntax: TRACe:POINts <source_trace> [,<acquisition_length>] Alias: DATA:POINts <source_trace> [,<acquisition_length>] <source_trace> CHn | Mi_n n = 1 .. 4 i = 1 .. 8 (standard memory) i = 1 .. 50 (extended memory) <acquisition_length> <NRf> | MINimum | MAXimum <NRf>...
Page 214 4 - 114 COMMAND REFERENCE Description: Defines the trace length (number of trace points) for all traces. The acquisition length and the length of all internal traces is programmed to the value specified in <acquisition_length>. If the <acquisition_length) parameter is omitted, the default value of 512 is assumed.
Page 215 COMMAND REFERENCE 4 - 115 TRIGger[:SEQuence[1]]:FILTer:HPASs:FREQuency TRIGger[:STARt]:FILTer:HPASs:FREQuency TRIGger[:SEQuence[1]]:FILTer:HPASs:STATe TRIGger[:STARt]:FILTer:HPASs:STATe Syntax: TRIGger[:SEQuence[1]]:FILTer:HPASs:FREQuency <NRf> | MINimum | MAXimum TRIGger[:SEQuence[1]]:FILTer:HPASs:STATe <Boolean> Alias: TRIGger[:STARt]:FILTer:HPASs:FREQuency <NRf> | MINimum | MAXimum TRIGger[:STARt]:FILTer:HPASs:STATe <Boolean> <NRf> The cutoff frequency expressed in hertz. The only possible value is 30000, which defines HF-reject (LF- pass).
Page 216 4 - 116 COMMAND REFERENCE Description: The TRIGger:FILTer:HPASs:FREQuency command sets the MTB cutoff frequency always at the fixed value of 30000 Hz (all values are rounded to 30 KHz). The TRIGger:FILTer:HPASs:STATe command activates (ON) or deactivates (OFF) the MTB high-pass filter. Activating the MTB high-pass filter: automatically deactivates the MTB low-pass filter.
Page 217 COMMAND REFERENCE 4 - 117 TRIGger[:SEQuence[1]]:FILTer:LPASs:FREQuency TRIGger[:STARt]:FILTer:LPASs:FREQuency TRIGger[:SEQuence[1]]:FILTer:LPASs:STATe TRIGger[:STARt]:FILTer:LPASs:STATe Syntax: TRIGger[:SEQuence[1]]:FILTer:LPASs:FREQuency <NRf> | MINimum | MAXimum TRIGger[:SEQuence[1]]:FILTer:LPASs:STATe <Boolean> Alias: TRIGger[:STARt]:FILTer:LPASs:FREQuency <NRf> | MINimum | MAXimum TRIGger[:STARt]:FILTer:LPASs:STATe <Boolean> <NRf> The cutoff frequency expressed in hertz. Possible values are: Defines trigger DC coupling (MINimum). Defines trigger AC coupling.
Page 218 4 - 118 COMMAND REFERENCE Description: The TRIGger:FILTer:LPASs:FREQuency command sets the MTB cutoff frequency, which defines the trigger coupling. The specified frequency values are rounded as follows: - 0 .. 4.99 is rounded to 0 Hz, i.e., DC coupling. - 5 .. 4999.99 is rounded to 10 Hz, i.e., AC coupling.
Page 219 COMMAND REFERENCE 4 - 119 TRIGger[:SEQuence[1]]:HOLDoff TRIGger[:STARt]:HOLDoff Syntax: TRIGger[:SEQuence[1]]:HOLDoff <NRf> | MINimum | MAXimum Alias: TRIGger[:STARt]:HOLDoff <NRf> | MINimum | MAXimum <NRf> The hold-off value expressed in percent. The range is from 0.00 (MINimum = 0 %) to 1.00 (MAXImum = 100 %). Query form: TRIGger[:SEQuence[1]]:HOLDoff? [MINimum | MAXimum] TRIGger[:STARt]:HOLDoff? [MINimum | MAXimum] Response:...
Page 220 4 - 120 COMMAND REFERENCE TRIGger[:SEQuence[1]]:LEVel TRIGger[:SEQuence[1]]:LEVel:AUTO TRIGger[:STARt]:LEVel TRIGger[:STARt]:LEVel:AUTO Syntax: TRIGger[:SEQuence[1]]:LEVel <NRf> | MINimum | MAXimum TRIGger[:SEQuence[1]]:LEVel:AUTO <Boolean> Alias: TRIGger[:STARt]:LEVel <NRf> | MINimum | MAXimum TRIGger[:STARt]:LEVel:AUTO <Boolean> <NRf> The trigger level expressed in volts. MINimum Selects the minimum possible trigger level. MAXimum Selects the maximum possible trigger level.
Page 221 COMMAND REFERENCE 4 - 121 After a RST command, the trigger level is MAXimum and auto level peak-peak is switched off. Notice that there exists a coupling between programming the attenuator (vertical sensitivity) and the trigger level. If the attenuator is changed, the trigger level is also adapted to keep the signal display on the screen.
Page 222 4 - 122 COMMAND REFERENCE TRIGger[:SEQuence[1]]:SLOPe TRIGger[:STARt]:SLOPe Syntax: TRIGger[:SEQuence[1]]:SLOPe POSitive | NEGative | EITHer Alias: TRIGger[:STARt]:SLOPe POSitive | NEGative | EITHer POSitive Positive trigger edge. NEGative Negative trigger edge. EITHer Triggering is done at a positive and at a negative edge.
Page 223 COMMAND REFERENCE 4 - 123 Example: → Configures AC-RMS CH2. Send CONFigure:AC (@2) → Sets real-time mode on. Send SENSe:SWEep:REALtime ON → Trigger source becomes Send TRIGger:SOURce INTernal2 channel 2. → Trigger level becomes 20 mV. Send TRIGger:LEVel .02 → Triggering is done at positive Send TRIGger:SLOPe EITHer...
Page 224 4 - 124 COMMAND REFERENCE TRIGger[:SEQuence[1]]:SOURce TRIGger[:STARt]:SOURce Syntax: TRIGger[:SEQuence[1]]:SOURce IMMediate | INTernal<n> | EXTernal | LINE | BUS Alias: TRIGger[:STARt]:SOURce IMMediate | INTernal<n> | EXTernal | LINE | BUS IMMediate Immediate sweeping (no waiting for a trigger). INTernal<n> Input channel <n> is used as trigger source. <n>...
Page 225 COMMAND REFERENCE 4 - 125 Description: Controls the trigger source. The command selects the source, and the query returns the source that triggers the acquisition. If a trigger source other than IMMediate, INTernal<n>, LINE, or BUS is active, execution error -221 is generated at receipt of the query.
Page 226 4 - 126 COMMAND REFERENCE TRIGger[:SEQuence[1]]:TYPE TRIGger[:STARt]:TYPE Syntax: TRIGger[:SEQuence[1]]:TYPE EDGE | VIDeo | LOGic Alias: TRIGger[:STARt]:TYPE EDGE | VIDeo | LOGic | GLITch EDGE Selects edge triggering. VIDeo Selects TV video triggering. LOGic Selects logic triggering (only for PM3384B-94B). GLITch Selects glitch triggering (only for PM33x0B).
Page 227 COMMAND REFERENCE 4 - 127 TRIGger[:SEQuence[1]]:VIDeo:FIELd[:NUMBer] TRIGger[:STARt]:VIDeo:FIELd[:NUMBer] TRIGger[:SEQuence[1]]:VIDeo:FIELd:SELect TRIGger[:STARt]:VIDeo:FIELd:SELect Syntax: TRIGger[:SEQuence[1]]:VIDeo:FIELd[:NUMBer] <NRf> | MINimum | MAXimum TRIGger[:SEQuence[1]]:VIDeo:FIELd:SELect ALL | NUMBer Alias: TRIGger[:STARt]:VIDeo:FIELd[:NUMBer] <NRf> | MINimum | MAXimum TRIGger[:STARt]:VIDeo:FIELd:SELect ALL | NUMBer <NRf> 1 | 2 1 | MINimum Selects field1 triggering. 2 | MAXimum Selects field2 triggering.
Page 228 4 - 128 COMMAND REFERENCE Description: The TRIGger:VIDeo:FIELd:SELect command programs the video trigger mode to "field" or "lines". The TRIGger:VIDeo:FIELd[:NUMBer] command selects between "field1" and "field2". After a RST command, lines triggering (ALL) and field number 1 is selected. Notice that there exists a coupling between selecting field1/field2 using the TRIGger:VIDeo:FIELd[:NUMBer] command and selecting the line number using the TRIGger:VIDeo:LINE command.
Page 229 COMMAND REFERENCE 4 - 129 TRIGger[:SEQuence[1]]:VIDeo:FORMat[:TYPE]:LPFRame TRIGger[:STARt]:VIDeo:FORMat[:TYPE]:LPFRame TRIGger[:SEQuence[1]]:VIDeo:FORMat[:TYPE] TRIGger[:STARt]:VIDeo:FORMat[:TYPE] Syntax: TRIGger[:SEQuence[1]]:VIDeo:FORMat[:TYPE]:LPFRame <NRf> | MINimum | MAXimum TRIGger[:SEQuence[1]]:VIDeo:FORMat[:TYPE] PAL | SCAM | SECAM | NTSC | HDTV Alias: TRIGger[:STARt]:VIDeo:FORMat[:TYPE]:LPFRame <NRf> | MINimum | MAXimum TRIGger[:STARt]:VIDeo:FORMat[:TYPE] PAL | SCAM | SECAM | NTSC | HDTV <NRf>...
Page 230 4 - 130 COMMAND REFERENCE Response: 525 | 625 | 1050 | 1125 | 1250 NTSC standard selected (525 lines/frame). PAL (default) or SECAM standard selected (625 lines/frame). 1050 HDTV standard selected (1050 lines/frame). 1125 HDTV standard selected (1125 lines/frame). 1250 HDTV standard selected (1250 lines/frame).
Page 231 COMMAND REFERENCE 4 - 131 Example: → Selects NTSC, 525 Send TRIGger:VIDeo:FORMat NTSC lines/frame. → Selects PAL, Send TRIGger:VIDeo:FORMat PAL lines/frame. → Selects SECAM, 625 Send TRIGger:VIDeo:FORMat SECAM lines/frame. → Selects HDTV, 1050 Send TRIGger:VIDeo:FORMat:LPFRame 1050 lines/frame. → Selects HDTV, 1125 Send TRIGger:VIDeo:FORMat:LPFRame 1125 lines/frame.
Page 232 4 - 132 COMMAND REFERENCE TRIGger[:SEQuence[1]]:VIDeo:LINE TRIGger[:STARt]:VIDeo:LINE TRIGger[:SEQuence[1]]:VIDeo:SSIGnal[:POLarity] TRIGger[:STARt]:VIDeo:SSIGnal[:POLarity] Syntax: TRIGger[:SEQuence[1]]:VIDeo:LINE <NRf> | MINimum | MAXimum TRIGger[:SEQuence[1]]:VIDeo:SSIGnal[:POLarity] POSitive | NEGative Alias: TRIGger[:STARt]:VIDeo:LINE <NRf> | MINimum | MAXimum TRIGger[:STARt]:VIDeo:SSIGnal[:POLarity] POSitive | NEGative <NRf> 1 .. 1250 1 | MINimum Selects video line 1. 1250 | MAXimum Selects video line 1250 (only for HDTV).
Page 233 COMMAND REFERENCE 4 - 133 Description: The TRIGger:VIDeo:LINE command selects the video line number. Depending on the video system selected, the following ranges are valid: > NTSC from 1 to 525 > PAL or SECAM from 1 to 625 > HDTV from 1 to 1250 The TRIGger:VIDeo:SSIGnal command selects the video signal polarity.
Page 234: A Application Program Examples
APPLICATION PROGRAM EXAMPLES A - 1 APPENDIX A APPLICATION PROGRAM EXAMPLES The program examples are written for the CombiScopes with the IEEE option installed. No other instrument is required to execute these examples. For system and programming environment requirements to execute these examples, refer to section 2.1 "Preparations for SCPI programming".
Page 235: A.1 Measuring Signal Characteristics
A - 2 APPLICATION PROGRAM EXAMPLES A.1 Measuring Signal Characteristics Measuring signal characteristics can be done in either of the following ways: 1) Using the measurement instructions. Example A.1.1 shows how to do that automatically by letting the CombiScope instrument select the best possible settings.
Page 236 APPLICATION PROGRAM EXAMPLES A - 3 ’Termination Receive on EOI StopEOI% = 256 ’Clears Output Screen ’Clears the GPIB interface CALL SendIFC(0) ’Timeout at 10 seconds CALL IBTMO(0, 13) ’ ’*** Reset the instrument and clear the status data. cmd$ = "*RST;*CLS" CALL Send(0, 8, cmd$, EndEOI%) CALL errorcheck ’...
Page 237: A.1.2 Making Programmed Measurements
A - 4 APPLICATION PROGRAM EXAMPLES A.1.2 Making programmed measurements In the following example the overshoot value on the rising edge of the Probe Adjust signal is measured. This is done by programming the input conditions in the RUN mode (INITiate:CONTinuous ON), followed by a single-shot measurement of the peak-to-peak (PTPeak) value and the rise time overshoot percentage (RISE:OVERshoot).
Page 238: A.1.3 Reading Measurement Values
APPLICATION PROGRAM EXAMPLES A - 5 A.1.3 Reading measurement values In the following example measurement values are read into the computer as calculated by the front panel MEAS1 and MEAS2 features during a single-shot measurement. Application summary: • Configure for measuring AC-RMS by sending: CONFigure:AC and initiate a single-shot by sending: INITiate •...
Page 239: A.3 Saving/Recalling Instrument Setups
A - 6 APPLICATION PROGRAM EXAMPLES A.3 Saving/Recalling Instrument Setups The following examples use the save/recall features for instrument setups. Saving and recalling can be done via internal memory (refer to A.3.1) and remotely via computer disk space (refer to A.3.2). These features can be used for non-supported functions, e.g., Cursor Measurements.
Page 240: A.3.2 Save/Recall Settings To/From Computer Disk Memory
APPLICATION PROGRAM EXAMPLES A - 7 • Routine ServReq does the following: Serial polls the status byte to reset the SRQ mechanism. Reads the ESR byte to clear the OPC bit. Sets the SRQ.detected flag to signal that an SRQ interrupt occurred. •...
Page 241 A - 8 APPLICATION PROGRAM EXAMPLES • If an SRQ is generated (acquisition finished), the dT cursor value is read and printed by sending: DISPlay:WINDow:TEXT20:DATA? Request to stop or to repeat this test (do Repeat.test1 again). • Routine ServReq does the following: Serial polls the status byte to reset the SRQ mechanism.
Page 242: A.4 Making A Hardcopy Of The Screen
APPLICATION PROGRAM EXAMPLES A - 9 A.4 Making a Hardcopy of the Screen In the following example a hardcopy of the screen picture is made as follows: 1) Enter the hardcopy of the screen in HPGL data format. 2) Send the entered data buffer to a HPGL plotter connected via the IEEE bus. Application summary: IEEE IEEE...
Page 243: A.5 Pass/Fail Testing
A - 10 APPLICATION PROGRAM EXAMPLES A.5 Pass/Fail Testing The following examples use the SYSTem:SET command for storing and restoring instrument setups, which can be used for non-supported functions, such as, Pass/Fail Testing. Before executing one of the programs, a pass/fail test setup must be created by hand via the front panel, including: 1) Generation of a signal that must be tested.
Page 244: A.5.2 Restoring A Pass/Fail Test Setup
APPLICATION PROGRAM EXAMPLES A - 11 • Routine Save.Envreg does the following: Requests for a memory register to read the envelope from, e.g. 2_1. Requests the reference envelope by sending e.g.: TRACe? M2_1 and by reading the envelope data (envelope$). Writes the envelope register, length, plus data to the opened file.
Page 245: A.5.3 Running A Pass/Fail Test
A - 12 APPLICATION PROGRAM EXAMPLES A.5.3 Running a pass/fail test In the following example the current pass/fail test setup is started and monitored. During monitoring, use is made of the pass/fail status bit (bit 10) in the OPERation status register to detect a failing waveform. The OPERation bit (bit 7) in the standard status byte is used to generate a service request (SRQ) when a failing waveform is detected.
Page 246: B Cross References
CROSS REFERENCES B - 1 APPENDIX B CROSS REFERENCES B.1 Cross Reference Front Panel Keys / Commands The front panel picture is copied from the operation guide, showing the SCPI commands corresponding to front panel keys. SENS:SWE:OFFS:TIME TRIG:HOLD CAL? INST INIT:CONT ANAL AUTO SET...
Page 247 B - 2 CROSS REFERENCES...
Page 248: B.2 Cross Reference Softkey Menus / Commands
CROSS REFERENCES B - 3 B.2 Cross Reference Softkey Menus / Commands The menu pictures are copied from or refer to menus in the operation guide. The relationship to the corresponding SCPI command(s) is also shown. B.2.1 ACQUIRE menu DIGITAL ACQUIRE ACQUIRE TRACK...
Page 249: B.2.2 Cursors Menu
B - 4 CROSS REFERENCES B.2.2 CURSORS menu Programmable with the SAV/ RCL and SYST:SET commands. CURSORS CURSORS (MEAS) READOUT (MATH) T 1/ T DISP:WIND:TEXT :DATA? on off T-ratio ph T-trg = | | # T=360 auto V1 V2 DISP:WIND:TEXT :DATA? V-ratio V=100%...
Page 250: B.2.3 Display Menu
CROSS REFERENCES B - 5 B.2.3 DISPLAY menu ANALOG MODE: DISPLAY DISPLAY X-DEFL on off X-SOURCE ANALOG X-DEFL TEXT line RETURN TRACK USE: for Position ∆ for Character DIGITAL MODE: DISPLAY EDIT DISPLAY X vs Y TEXT USER TEXT TRIG IND on off on off on off...
Page 251: B.2.4 Mathplus Math Menu
B - 6 CROSS REFERENCES B.2.4 MATHPLUS MATH menu CALC :MATH:STAT MATH MATH MATH PLUS PLUS MATH 1 MATH 2 filter on off on off SCALE PARAM CALC :FILT:FREQ:STAT DISPLAY DISPLAY CALC :INT:STAT SOURCE SOURCE yes no yes no CALC :DIFF:STAT MATH 2 MATH 1 CALC :TRAN:FREQ:STAT...
Page 252 CROSS REFERENCES B - 7 CALC :MATH[:EXPR] MATH n MATH AREA LIMITED yes no TRACK TRACK LEFT filter samples ∆ RIGHT ∆ samples ∆ ∆ CALC :FEED ∆ RETURN ENTER MATH MATH MATH INTEGR PARAM PARAM PARAM TRACK WINDOW LIMITED LIMITED yes no yes no...
Page 253 B - 8 CROSS REFERENCES...
Page 254: B.2.5 Measure Menu
CROSS REFERENCES B - 9 B.2.5 MEASURE menu MEASURE MEASURE SELECT SELECT SELECT MEAS n MEAS n MEAS n MEAS 1 volt volt volt pkpk time time time delay delay delay freq on off period TRACK TRACK TRACK MEAS2 pulse rise rise pkpk...
Page 255: B.2.7 Save/Recall Menu
B - 10 CROSS REFERENCES B.2.7 SAVE/RECALL menu SAVE CLEAR& CLEAR CLEAR SAVE ACQ PROTECT MEMORY MEMORY MEMORY MEMORY CONFIRM CONFIRM TRACK TRACK PROTECT TRAC[:DATA] save on off clear TRAC:COPY clear COPY ARE YOU OVERRULE PROTECT? SURE ? clear CLEAR& RETURN PROTECT RECALL...
Page 256: B.2.9 Tb Mode Menu
CROSS REFERENCES B - 11 B.2.9 TB MODE menu SYST:SET RCL/ SAV ANALOG: TB MODE TB MODE EVENT EVENT DELAY DELAY on off on off auto INIT:CONT ON TRACK trig single COUNT 1022 CHANNEL 1 2 3 4 ∆ ∆ ANALOG LEVEL +99.8mV...
Page 257: B.2.10 Trigger Menu
B - 12 CROSS REFERENCES B.2.10 TRIGGER menu ANALOG MODE: TRIGGER TRIGGER TRIGGER TRIGGER MAIN TB MAIN TB MAIN TB edge tv edge tv edge tv TRIG:TYPE field 1 field 1 INT3 TRIG:SOUR LINE field 2 field 2 line lines lines TRACK level-pp...
Page 258 CROSS REFERENCES B - 13 VIDEO SYSTEM hdtv ntsc TRIG:VID:FORM[:TYPE] secam LINES 1050 TRIG:VID:FORM:LPFR 1125 1250 ENTER TRIGGER TRIGGER TRIGGER MAIN TB MAIN TB MAIN TB edge tv edge tv edge tv logic logic logic state state state pattern pattern pattern glitch glitch...
Page 259: B.2.11 Utility Menu
B - 14 CROSS REFERENCES B.2.11 UTILITY menu UTILITY UTIL UTIL UTIL PROBE PROBE CORR PROBE AUTOSET SWITCH autoset PROBE setups SCREEN & 10:1 SOUND 20:1 REMOTE 50:1 SETUP 100:1 PRINT & PROBE PLOT & CORR CLOCK REFER TO MAINTE- SERVICE RETURN RETURN...
Page 260 CROSS REFERENCES B - 15 UTIL UTIL UTIL UTIL AUTOSET AUTOSET AUTOSET AUTOSET PROBE TRIG VERT AUTOSET PROBE CHANNELS UNAFFECT scan yes no default unaffect unaffect userprog ac dc setups unaffect Ω 50Ω VERT unaffect TRIG PROBE RETURN RETURN RETURN RETURN UTIL UTIL...
Page 261: B.2.12 Vertical Menu
B - 16 CROSS REFERENCES B.2.12 VERTICAL menu VERTICAL MENU BW LIMIT INP:FILT on off 50Ω CH1 INP1:IMP on off 50Ω CH2 INP2:IMP on off 50Ω CH3 INP3:IMP on off 50Ω CH4 INP4:IMP on off ST7441 50 Ω /1 M Ω only applicable for PM3394B. Note:...
Page 262: B.3 Cross Reference Functions / Commands
CROSS REFERENCES B - 17 B.3 Cross Reference Functions / Commands This section describes the SCPI commands that are related to the oscilloscope functions and frontpanel keys. The oscilloscope functions and keys are described in chapter 5 "Function Reference" of the Operating Guide. The SCPI commands are specified in chapter 4 "COMMAND REFERENCE"...
Page 263 B - 18 CROSS REFERENCES FUNCTION + KEYS/MENUS RELATED SCPI COMMAND(S) AUTOSET key AUTOSET SYSTem:KEY 101 AUTOSET SEQUENCE key STATUS SYSTem:KEY 201 key TEXT OFF SYSTem:KEY 801 menu UTILITY AUTOSET or PROBE DISPlay:MENU UTIL - softkeys n = 1 .. 6 SYSTem:KEY n AUTOSET USERPROG key UTILITY...
Page 264 CROSS REFERENCES B - 19 FUNCTION + KEYS/MENUS RELATED SCPI COMMAND(S) CURSOR READOUT key CURSORS SYSTem:KEY 204 menu CURSORS DISPlay:MENU CURSors READOUT DISPlay:WINDow[1]:TEXT<n>:DATA? DELAY SENSe:SWEep:OFFSet:TIME menu TB MODE EVENT DELAY DISPlay:MENU TBMode - softkeys n = 1 .. 6 SYSTem:KEY n - select pos/neg slope TRIGger:SLOPe DELAY MEASUREMENT...
Page 265 B - 20 CROSS REFERENCES FUNCTION + KEYS/MENUS RELATED SCPI COMMAND(S) FFT - FAST FOURIER TRANSFORMATION (MATHPLUS) key MATH SYSTem:KEY 111 menu MATH DISPlay:MENU MATH - softkeys n=1 .. 6 SYSTem:KEY n - MATH1(2) FFT ON/OFF CALCulate[1|2]:TRANsform:FREQuency:STATE - PARAM select FFT windows CALCulate[1|2]:TRANsform:FREQuency: WINDow RECTangular|HAMMing|HANNing - read FFT amplitude/frequency...
Page 266 CROSS REFERENCES B - 21 FUNCTION + KEYS/MENUS RELATED SCPI COMMAND(S) INPUT COUPLING INPut[<n>]:COUPling AC|DC|GROund key ON (toggled ON) SENSe:FUNCtion key ON CH1 SYSTem:KEY 803 key ON CH2 SYSTem:KEY 806 key ON CH3 SYSTem:KEY 809 (PM33x4B) key ON CH4 SYSTem:KEY 812 (PM33x4B) key TRIG VIEW EXT SYSTem:KEY 812 (PM33x0B) key AC/DC/GND...
Page 267 B - 22 CROSS REFERENCES FUNCTION + KEYS/MENUS RELATED SCPI COMMAND(S) MATHEMATICS CALCulate[1|2]: ..key MATH menu MATH DISPlay:MENU MATH - softkeys n = 1 .. 6 SYSTem:KEY n MEASURE MENU MEASure? CONFigure + READ? CONFigure + INITiate + FETCh? key MEASURE SYSTem:KEY 110 menu MEASURE...
Page 268 CROSS REFERENCES B - 23 FUNCTION + KEYS/MENUS RELATED SCPI COMMAND(S) PROBE SCALING (MATHPLUS) SAV, SYSTem:SET PROBE UTILITIES key UTILITY SYSTem:KEY 104 menu UTILITY PROBE DISPlay:MENU UTIL - softkeys n = 1 .. 6 SYSTem:KEY n REMOTE CONTROL IEEE-488.2 key STATUS / LOCAL SYSTem:KEY 201 key UTILITY SYSTem:KEY 104...
Page 269 B - 24 CROSS REFERENCES FUNCTION + KEYS/MENUS RELATED SCPI COMMAND(S) STANDARD FRONT/FRONT PANEL RESET SYSTem:SET key SETUPS SYSTem:KEY 103 menu FRONT SETUPS DISPlay:MENU SETups - softkeys n = 1 .. 6 SYSTem:KEY n - recall - save Status handling ESE, ESR?, SRE,...
Page 270 CROSS REFERENCES B - 25 FUNCTION + KEYS/MENUS RELATED SCPI COMMAND(S) TIMEBASE MODES key TB MODE SYSTem:KEY 409 menu TB MODE DISPlay:MENU TBMode - softkeys n = 1 .. 6 SYSTem:KEY n - AUTO INITiate:CONTinuous ON TRIGger:SOURce IMMediate - TRIG INITiate:CONTinuous ON TRIGger:SOURce INTernal<n>...
Page 271 B - 26 CROSS REFERENCES FUNCTION + KEYS/MENUS RELATED SCPI COMMAND(S) TRIGGERING OF SWEEPS - send GET code - abort trigger system ABORt - initiate trigger system continuously INITiate:CONTinuous - initiate trigger system once only INITiate[:IMMediate] TRIGGER COUPLING key TRIGGER SYSTem:KEY 209 key DTB SYSTem:KEY 402...
Page 272 CROSS REFERENCES B - 27 FUNCTION + KEYS/MENUS RELATED SCPI COMMAND(S) TV TRIGGER TRIGger:TYPE VIDEO key TRIGGER SYSTem:KEY 209 menu TRIGGER DISPlay:MENU TRIGger - field1, field2, lines TRIGger:VIDeo:FIELd[:NUMBer] TRIGger:VIDeo:FIELd:SELect - select line number (TRACK) TRIGger:VIDeo:LINE - pos/neg signal polarity TRIGger:VIDeo:SSIGnal - VIDEO SYSTEM TRIGger:VIDeo:FORMat[:TYPE] TRIGger:VIDeo:FORMat[:TYPE]:LPFRame...
Page 273 B - 28 CROSS REFERENCES FUNCTION + KEYS/MENUS RELATED SCPI COMMAND(S) VOLT MEASUREMENTS key MEASURE SYSTem:KEY 110 menu MEASURE DISPlay:MENU MEASure - softkeys n = 1 .. 6 SYSTem:KEY n - MEAS 1 & MEAS 2 DISPlay:WINDow[1]:TEXT<1|2>:DATA? - dc voltage MEASure[:DC]? - rms voltage MEASure:AC?
Page 274: C Manual Conventions
MANUAL CONVENTIONS C - 1 APPENDIX C MANUAL CONVENTIONS C.1 Abbreviations Used ABBREVIATIONS USED (in alphabetical order) - ADC = Analog to Digital Convertor - AH = Acceptor Handshake - ANSI = American National Standards Institute - ASCII = American Standard Code for Information Interchange = Controller - CAL = Calibration...
Page 275 C - 2 MANUAL CONVENTIONS - IDY = Identify - IDN = Identification - IEC = International Electrotechnical Commission - IEEE = Institute of Electrical and Electronic Engineers - i.e. = id est (that is) - IFC = Interface Clear - INT = Internal - I/O...
Page 276 MANUAL CONVENTIONS C - 3 - RAM = Random Access Memory - RCL = Recall - REN = Remote Enable - RL = Remote Local - rms = root mean square - rmt = response message terminator - rmu = response message unit - RQC = Request Control - RQS...
Page 277: C.2 Glossary Of Symbols Used
C - 4 MANUAL CONVENTIONS C.2 Glossary of Symbols Used µ = micro voltage (1E-6) - dB = decibell - dBm = decibell with respect to 1 mW µ µ - dB = decibell with respect to 1 √ - Vrms = RMS voltage (Peak / - Hz = Hertz...
Page 278: C.4 List Of Figures
MANUAL CONVENTIONS C - 5 C.4 List of Figures Figure 3.1 The instrument model for CombiScope instruments Figure 3.2 Pulse characteristics Figure 3.3 The trigger model for acquisitions Figure 3.4 DC Coupling Figure 3.5 AC Coupling Figure 3.6 LF Reject Figure 3.7 HF Reject Figure 3.8...
Page 279: C.5 Documents Referenced
C - 6 MANUAL CONVENTIONS C.5 Documents Referenced 1) General Purpose Interface Bus (GPIB) IEC 625-1 / IEEE-488.1 Order number: 4822 872 80193 2) SCPI - Standard Commands for Programmable Instruments Order number: 4822 872 80194 3) SCPI in the German language (Standard Kommandos für Programmierbare Instrumenten) Order number: 4822 872 80174 4) SCPI in the French language...
Page 280: D Standards Information
STANDARDS INFORMATION D - 1 APPENDIX D STANDARDS INFORMATION D.1 SCPI Conformance Information All commands comply to the SCPI standard 1994.0, except for the following: RST condition of the SENSe:VOLTage<n>[:DC]:RANGe:AUTO ON | OFF command. Exception: After RST, autoranging MTB is switched off. RST condition of the SENSe:SWEep:TIME:AUTO ON | OFF command.
Page 281: D.2 List Of Implemented Ieee-488.2 Syntactical Elements
D - 2 STANDARDS INFORMATION D.2 List of Implemented IEEE-488.2 Syntactical Elements The following list of elements is used in the common and SCPI commands: <PROGRAM MESSAGE> Represents a sequence of zero or more <PROGRAM MESSAGE UNIT> elements, separated by <PROGRAM MESSAGE UNIT SEPARATOR> ELEMENTS.
Page 282 STANDARDS INFORMATION D - 3 <PROGRAM MESSAGE UNIT SEPARATOR> Separates the <PROGRAM MESSAGE UNIT> elements from one another in a <PROGRAM MESSAGE>. Only the semicolon (;) is allowed as program message unit separator. <PROGRAM DATA SEPARATOR> Separates sequential <PROGRAM DATA> elements that are related to the same command program header.
Page 283 SUMMARY OF SYSTEM SETTINGS E - 1 APPENDIX E SUMMARY OF SYSTEM SETTINGS The following table identifies which instrument settings belong to which node. NODE NR: SPECIFICATION: End node settings length = 1 byte zero Channel 1/2/3/4 settings 1 | 2 | 3 | 4 length = 8 bytes attenuation, channel on/off, input coupling DC/AC/grounded, invert on/off,...
Page 284 E - 2 SUMMARY OF SYSTEM SETTINGS Delayed timebase settings length = 13 bytes delayed timebase, trigger mode edge, TV, trigger level, delayed timebase on/off, trigger slope pos/neg, noise suppression on/off, trigger source CH1/2/3/4, mtb, trigger delay, trigger coupling AC, DC, LF reject, HF reject.
Page 285 SUMMARY OF SYSTEM SETTINGS E - 3 65 | 66 MATH1/2 settings length = 22 bytes MATH1/2 selection, limited on/off, FFT filter Hamming/Hanning/Rectangle, adjustify scale/offset, source1/source2, Y-cursors/X-cursors, mathematics type add, subtract, multiply, filter, integrate, differentiate, fast fourier, histogram, source MATH1/2 CHn, Mi_j, scale, offset, filter window width, differentiate window width, FFT area left/right border, Y- offset integrate limited area, FFT absolute/relative readout.
Page 286 INDEX I - 1 Numerics 16-bit samples ..........3-33 3 wire .
Page 287 I - 2 INDEX Bandwidth....... . . 3-22, 3-40, 4-23, 4-24, 4-63 Bandwidth Limiter .
Page 288 INDEX I - 3 DC coupling ........3-21, 3-22, 4-117 Decimal numeric program data.
Page 289 I - 4 INDEX EXAPPA32.BAS ..........A-8 EXAPPA4.BAS .
Page 290 INDEX I - 5 GET ....... 3-16, 3-20, 4-28, 4-56, 4-124, B-26 Glitch settings .
Page 291 I - 6 INDEX Internal memory ........4-22, 4-24, 4-25 Invert .
Page 292 INDEX I - 7 Measuring signal characteristics........A-2 Memory.
Page 293 I - 8 INDEX Pacing ........... . . 4-99 PAL.
Page 294 INDEX I - 9 Questionable condition register ........4-93 Questionable event enable register .
Page 295 I - 10 INDEX Screen position........3-31, 3-34, 3-49 SECAM.
Page 296 INDEX I - 11 T ............3-62 T1-trg .
Page 297 I - 12 INDEX TV standard ..........3-23, 4-130 TV trigger .

This manual is also suitable for:

Combiscope pm3384b Combiscope pm3394b Combiscope pm3380b Combiscope pm3390b

Fluke CombiScope PM3370B User Manual

Quick Links

Related Manuals for Fluke CombiScope PM3370B

Summary of Contents for Fluke CombiScope PM3370B

This manual is also suitable for:

Table of Contents