Configuring the internal baseband source
R&S
®
SMM100A
190
User Manual 1179.1341.02 ─ 05
{MWV_SEGMENTx_COMMENT: text}
(optional for multi-segment waveforms)
The tag contains a user comment for a specific segment
x = [0…NumOfSeg-1]
in
the multi-segment waveform in ASCII format.
Example:
{MWV_SEGMENT1_FILES: segment 1 contains a QPSK
signal.}
Usage:
Setting only
{CONTROL LIST WIDTH4–Length: #m0m1…mx…mM-1}
(optional for waveforms and multi-segment waveforms)
The tag contains a binary marker element stream, which is output synchronously to the
I/Q sample sequence. One marker element
mx
consists of 4 bit, which are assigned to
the 3 possible marker traces of the instrument (1 bit per marker trace). One 4-bit
marker element is required for every I/Q sample in the
WAVEFORM
tag. Hence, the
number of marker elements
m
should be equal to the number of I/Q samples. The
CONTROL LENGTH
tag has to contain the number of all marker elements
m
.
Figure 4-20: Marker element in 4-bit binary format bit order
tags are a more compact way to define
markers. In principle, however, the
CONTROL LIST WIDTH4
format can also be used
instead of the
MARKER LIST x
tags.
For multi-segment waveforms, the
CONTROL LIST WIDTH4
format is required for
marker definition. The binary marker streams of the individual segments are directly
concatenated (without any gap) to one collectively marker stream.
Setting parameters:
Length
Defines the number of bytes in the
CONTROL LIST WIDTH4
tag
in ASCII Format and is calculated as follows:
Length = Size of "#" (1 byte) + Number of marker elements m
x
*
(4 bit) / (8 bits/byte)
The value is rounded up for byte alignment.
mx
Marker element in 4-bit binary format.
Example:
{CONTROL LIST WIDTH4-51: #m
0
m
1
…m
x
…m
99
}
100 marker elements, each marker element with 4 bits
Usage:
Setting only
Using the arbitrary waveform generator (ARB)
