Configuration
R&S
®
FSW-K7
108
User Manual 1173.9240.02 ─ 23
Furthermore, the RUN CONT key controls the Sequencer, not individual sweeps. RUN
CONT starts the Sequencer in continuous mode.
For details on the Sequencer, see the R&S
FSW User Manual.
Remote command:
Single Sweep/ RUN SINGLE
After triggering, starts the number of sweeps set in "Sweep Count". The measurement
stops after the defined number of sweeps has been performed.
While the measurement is running, the "Single Sweep" softkey and the RUN SINGLE
key are highlighted. The running measurement can be aborted by selecting the high-
lighted softkey or key again.
Note:
Sequencer. If the Sequencer is active, the "Single Sweep" softkey only controls
the sweep mode for the currently selected channel. However, the sweep mode only
takes effect the next time the Sequencer activates that channel, and only for a chan-
nel-defined sequence. In this case, the Sequencer sweeps a channel in single sweep
mode only once.
If the Sequencer is active in MSRT mode, the "Single Sweep" function does not start
data capturing. It merely affects trace averaging over multiple sequences. In this case,
no trace averaging is performed.
Furthermore, the RUN SINGLE key controls the Sequencer, not individual sweeps.
RUN SINGLE starts the Sequencer in single mode.
If the Sequencer is off, only the evaluation for the currently displayed measurement
channel is updated.
For details on the Sequencer, see the R&S
FSW User Manual.
Remote command:
Continue Single Sweep
After triggering, repeats the number of sweeps set in "Sweep Count", without deleting
the trace of the last measurement.
While the measurement is running, the "Continue Single Sweep" softkey and the RUN
SINGLE key are highlighted. The running measurement can be aborted by selecting
the highlighted softkey or key again.
Remote command:
Refresh ( MSRA / MSRT only)
This function is only available if the Sequencer is deactivated and only for
MSRA /
MSRT slave applications
.
The data in the capture buffer is re-evaluated by the currently active slave application
only. The results for any other slave applications remain unchanged.
This is useful, for example, after evaluation changes have been made or if a new
sweep was performed from another slave application; in this case, only that slave
application is updated automatically after data acquisition.
Data Acquisition
