Common analysis and display functions
R&S
®
FSVA3000/ R&S
®
FSV3000
621
User Manual 1178.8520.02 ─ 08
7.6.6
Reference: ASCII file export format
Trace data can be exported to a file in ASCII format for further evaluation in other appli-
cations. This reference describes in detail the format of the export files for result data.
The data of the file header consist of three columns, each separated by a semicolon:
parameter name; numeric value; basic unit. The data section starts with the keyword
"Trace <n>" (<n> = number of stored trace). The measured data follows in one or sev-
eral columns (depending on the measurement), which are also separated by a semico-
lon.
The results are output in the same order as they are displayed on the screen: window
by window, trace by trace, and table row by table row.
7.7
Event-based actions
During a measurement, specific events require that you take a certain action. The
R&S
FSV/A allows you to automize such tasks.
The event-based actions feature allows you to capture a particular state of the device
under test. Then you can document it for further research or start a specific procedure.
The mechanism triggers one or more actions at the end of a sweep if a certain condi-
tion applies. The combinations of condition and actions are called
rules
. Each applica-
tion individually specifies its own set of rules. Triggering conditions are referred to as
events
. Typical examples are exceeding or going below a limit value, the (non-) viola-
tion of a limit line, hitting a marker value, etc. The range of actions includes taking a
screenshot, starting a separate program, saving I/Q data, etc. Also, continuous sweep-
ing can be stopped to retain the data of a particular state of the system.
Some general conditions apply to event-based actions:
●
A maximum of 5 rules can be defined for each application.
●
The base unit applications (Spectrum, I/Q analyzer, Analog Demodulation) are
counted together and thus support a total of 5 rules over all three applications.
Rules defined in one application are visible, but cannot be edited or enabled, in the
other two applications. The same applies to different measurements within a single
application (e.g. SEM and ACLR).
●
Only the currently active measurement channel processes rules.
●
The R&S
FSV/A in general, or any applications, do not perform a validity check on
the rules.
●
When you save and then recall the instrument settings, any rule definitions are also
stored and loaded, including their state.
●
After an instrument preset or restart, the rules are maintained, but disabled. The
trigger count for rules is cleared.
Event-based actions
