R&S
®
CMW 500 Remote Control
Control of the Instrument
Operating Manual 1202.3986.32 – 03 98
QUE) indicates that the measurement is
running but still queued, waiting for resource
allocation.
FETCh:<FWA>:<Meas1>...CURRent
?
(or similar command syntax for reading
measurement results)
Wait until the end of the statistics cycle of
measurement 1 and retrieve the results.
FETCh:<FWA>:<Meas2>:STATe:ALL
?
Query the measurement substates of
measurement 2. The response (RUN, ADJ,
ACT) indicates that measurement 2 is now
active.
CONFigure:<FWA>:<Meas1>:REPet
ition?
CONFigure:<FWA>:<Meas1>:REPet
ition?
Query the r
epetition mode of measurements 1
and 2. Measurement 1 is in single shot mode
(SING), measurement 2 is still in continuous
mode (CONT).
5.4.8.3 Causes for Task Conflicts
Resource conflicts may arise for the following reasons:
Hardware Resource Conflicts
A generator requires an independent output channel (digital and analog RF transmitter
stages). Mobile transmitter measurements (TX measurements) generally require their
own input channel (analog and digital RF receiver stages).
The number of tasks that the instrument can service in parallel depends on the number
of independent channels. The R&S CMW 500 can be equipped with up to 4
independent input/output channels.
System Resource Conflicts
In addition to the hardware resources required for TX and RX channels, other system
resources may cause limitations: memory size, possible connections between modules
(e.g. trigger lines, I/Q data lines etc.)
Software Option Conflicts
Many R&S CMW 500 features must be enabled using a firmware option key. To be run
in parallel, several measurements of the same type may require several enabled
software options. A resource conflict arises whenever the required number of software
options is not available.
The RPM principles are not valid for tasks which cause a software option conflict.
To Next Page
Loading...
