Instructions
Table Of Contents
- Cover
- Contents
- 1 For Your Safety
- 2 Getting Started
- 3 Waveform Setup
- 3.1 Connecting Probes
- 3.2 Vertical Setup
- 3.3 Horizontal Setup
- 3.4 Acquisition Control
- 3.5 Roll Mode
- 3.6 Trigger
- 3.6.1 General Trigger Settings
- 3.6.2 Edge Trigger
- 3.6.3 Glitch Trigger
- 3.6.4 Width Trigger
- 3.6.5 Video/TV Trigger
- 3.6.6 External Trigger (R&S RTH1002)
- 3.6.7 Pattern Trigger (R&S RTH-K19)
- 3.6.8 State Trigger (R&S RTH-K19)
- 3.6.9 Runt Trigger (R&S RTH-K19)
- 3.6.10 Slew Rate Trigger (R&S RTH-K19)
- 3.6.11 Data2Clock Trigger (R&S RTH-K19)
- 3.6.12 Serial Pattern Trigger (R&S RTH-K19)
- 3.6.13 Timeout Trigger (R&S RTH-K19)
- 3.6.14 Interval Trigger (R&S RTH-K19)
- 3.6.15 Window Trigger (R&S RTH-K19)
- 3.6.16 Protocol Trigger (R&S RTH-K1, -K2, -K3, -K9 and -K10)
- 4 Waveform Analysis
- 5 Mask Testing
- 6 Spectrum Analysis
- 6.1 FFT Mode
- 6.2 Spectrum Mode (Option R&S RTH-K18)
- 6.3 Harmonics Measurement (Option R&S RTH-K34)
- 7 Multimeter Measurements
- 8 Data Logging
- 9 Protocol Analysis
- 10 Logic Analyzer (R&S RTH-B1 MSO)
- 11 Frequency Counter (R&S RTH-K33)
- 12 Documenting Results
- 13 General Instrument Setup
- 14 Network Connections
- 15 Remote Control Commands
- 15.1 Conventions used in Command Description
- 15.2 Mode
- 15.3 Waveform Setup
- 15.3.1 Automatic Setup
- 15.3.2 Vertical Setup
- 15.3.3 Horizontal Setup
- 15.3.4 Acquisition Control
- 15.3.5 Trigger
- 15.3.5.1 General Trigger Settings
- 15.3.5.2 Edge Trigger
- 15.3.5.3 Glitch Trigger
- 15.3.5.4 Width Trigger
- 15.3.5.5 Video/TV Trigger
- 15.3.5.6 External Trigger (R&S RTH1002)
- 15.3.5.7 Pattern Trigger (R&S RTH-K19)
- 15.3.5.8 State Trigger (R&S RTH-K19)
- 15.3.5.9 Runt Trigger (R&S RTH-K19)
- 15.3.5.10 Slew Rate Trigger (R&S RTH-K19)
- 15.3.5.11 Data2Clock Trigger (R&S RTH-K19)
- 15.3.5.12 Serial Pattern Trigger (R&S RTH-K19)
- 15.3.5.13 Timeout Trigger (R&S RTH-K19)
- 15.3.5.14 Interval Trigger (R&S RTH-K19)
- 15.3.5.15 Window Trigger (R&S RTH-K19)
- 15.4 Waveform Analysis
- 15.5 Mask Testing
- 15.6 Spectrum Analysis
- 15.7 Digital Multimeter (R&S RTH1002)
- 15.8 Voltmeter (R&S RTH1004)
- 15.9 Counter Mode (R&S RTH-K33)
- 15.10 Data Logging
- 15.11 Protocol Analysis
- 15.12 Logic Analyzer (R&S RTH-B1 MSO)
- 15.13 Documenting Results
- 15.14 General Instrument Setup
- 15.15 WLAN Connection (Option R&S RTH-K200/200US)
- 15.16 User Scripting (R&S RTH-K38)
- Annex
- List of Commands
Command Sequence and Synchronization
R&S
®
Scope Rider RTH
518User Manual 1326.1578.02 ─ 15
B Command Sequence and Synchronization
IEEE 488.2 defines a distinction between overlapped (asynchronous) and sequential
commands:
●
A sequential command finishes executing before the next command starts execut-
ing. Commands that are processed quickly are usually implemented as sequential
commands.
●
An overlapping or asynchronous command does not automatically finish executing
before the next command starts executing. Usually, overlapping commands take
longer to process and allow the program to do other tasks while being executed. If
overlapping commands must be executed in a defined order, e.g. to avoid wrong
measurement results, they must be serviced sequentially. This method is called
synchronization between the controller and the instrument.
As a rule, send commands and queries in different program messages, i.e. in separate
command lines.
Do not combine queries with commands that affect the queried value in one program
message because the response to the query is not predictable.
The following messages always return correct results:
:CHAN:SCAL 0.01;POS 1
:CHAN:SCAL?
Result: 0.01 (10 mV/div)
Reason: Setting commands within one command line, even though they are implemen-
ted as sequential commands, are not necessarily serviced in the order in which they
have been received.
For further information, refer to:
●
rohde-schwarz.com/rckb: Rohde & Schwarz web page that provides information on
instrument drivers and remote control.
●
"Automatic Measurement Control - A tutorial on SCPI and IEEE 488.2" from John
M. Pieper (R&S order number 0002.3536.00). The book offers detailed information
on concepts and definitions of SCPI.
B.1 Preventing Overlapping Execution
To prevent an overlapping execution of commands, one of the commands *OPC,
*OPC? or *WAI can be used. All three commands cause a certain action only to be
carried out after the hardware has been set. The controller can be forced to wait for the
corresponding action to occur.
Preventing Overlapping Execution