Remote Control
R&S
®
CMW500
161
User Manual 1173.9463.02 ─ 02
Two non-conflicting measurements, executed in parallel
RPM acts on sub-instrument level
If the R&S CMW500 is split into several sub-instruments, each of them is equipped with
independent hardware and software resources in order to run the tasks assigned to it.
The RPM principles apply to each sub-instrument separately. Due to the independance
of sub-instruments, hardware and software resource conflicts between units cannot
occur.
This does not apply to software license keys.
Example:
To run two instances of a mea-
surement in parallel requires two license keys. If only one license key is active the RPM
mechanisms apply even if the two instances of the measurement are run on different sub-
instruments.
See also
6.4.5.2
Queuing of Measurements
The R&S CMW500 queues conflicting measurements in order to ensure that no results
are lost when a new measurement is started. Adding a new measurement to the queue
switches the preceding measurement into single-shot mode (if it is a continuous mea-
surement). As a result, the instrument can acquire a valid set of measurement results for
every measurement in the queue.
Example for queued conflicting measurements
Command
Comment
*RST
INITiate:<FWA>:<Meas1>
Start measurement 1 in single-shot mode (default setting for
remote control)
INITiate:<FWA>:<Meas2>
Start a new measurement 2. The new measurement will be
queued.
FETCh:<FWA>:<Meas1>:STATe:ALL?
Query the measurement substates of measurement 1. The
response (
RUN, ADJ, ACT
) indicates that the measurement is
running with all necessary adjustments finished, that the neces-
sary resources are allocated and that results are being acquired.
FETCh:<FWA>:<Meas2>:STATe:ALL?
Query the measurement substates of measurement 2. The
response (
RUN, PEND, QUE
) indicates that the measurement
is running but still queued, waiting for resource allocation.
Control of the Instrument
