MDO3000 Programmer Manual.pdf - 第302页
Commands Listed in A lphabetical Order WFMOutpre? ACQuire:MODe Arguments <Block> is the waveform data in binary format. The waveform is forma tted as follows: <IEEE488.2 binary block h eader><data><n…
Commands Listed in Alphabetical Order
where:Nisasin
gle decimal or hexadecimal digit indicating the number of digits
to follow. <N-digits> are the decimal digits representing the number of bytes in
the data that immediately follows this binary block header.
The Waveform Transfer command group text contains more comprehensive
information. (See page 2-95, Waveform Tr
ansfer Command Group.)
(See page D-1, Wa veform Transfer (WFMOutpre and CURVe Query) Examples.)
NOTE. In order to guarantee that the waveform data returned from
CURVE?
queries of multiple waveforms are correlated to the same acquisition, you
should use single sequence acquisition mode to acquire the wa
veform data
from a single acquisition. Single sequence acquisition mode is enabled using
ACQuire:STOPAfter
SEQuence
.
NOTE. Aseriesofexamplesofwaveformtransfer command sequences is included
as an appendix. (See page D-1, Waveform Transfer (WFMOutpre and CURVe
Query) Examples.)
Example 1: Analog Waveform (channel 1 - 4)
Example 2: Digital Waveform (channel DO-D15)
Example 3: The Digital Collection with 4 Bytes Per Point with MagniVu Off
Example 4: The Digital Collection with 8 Bytes Per Point with MagniVu Off
Example 5: The Digital Collection with 4 Bytes Per Point with MagniVu On
Example 6: The Digital Collection with 8 Bytes Per Point with MagniVu On
Example 7: RF Frequency Domain Waveform
Group
Waveform Transfer
Syntax
CURVe { <Block>|<asc curve>}
CURVe?
Related Commands
DATa:DESTination
DATa:ENCdg
DATa:SOUrce
DATa:STARt
DATa:STOP
WFMInpre?
MDO4000/B/C, MSO/DPO4000B and MDO3000 Series Oscilloscopes Programmer Manual 2-271
Commands Listed in Alphabetical Order
WFMOutpre?
ACQuire:MODe
Arguments
<Block> is the waveform data in binary format. The waveform is formatted as
follows:
<IEEE488.2 binary block header><data><newline>
<IEEE488.2 binary block> is the header, which is defined as #N<N-digits>
N is a single decimal or hexadecimal digit indicating the number of digits
to follow.
<N-digits> are the decimal digits representing the number of bytes in
the data that immediately follows this binary block header. (Use the
WFMInpre:BYT_Nr command to set the width for waveforms transferred
into the oscilloscope. Use WFMOutpre:BYT_Nr to set the width for
waveforms transferred out from the oscilloscope.)
<data> is the curve data.
<newline> is a single byte new line character at the end of the data.
<asc cu rve> is the waveform data in ASCII format. The format for ASCII data
is
<NR1>[,<NR1>..], where each <NR1> represents a data point. For RF frequency
domain waveforms, the data is transmitted as 4-byte floating point values (NR2
or NR3).
Examples
CURVe 0 ,1,4,32,-120 … — This command sends ASCII data values to the
specified destination reference waveform (DATa:DESTination).
CURVe # 510000<10000 binary byte s> — This command sends
10,000 binary data bytes to the specified destination reference waveform
(DATa:DESTination).
CURVE? with ASCII encoding, START and STOP of 1 and 10 respectively, and a
width set to 1 might return
:CURVe 61 ,62,61,60,60,-59,-59,-58,-58,-59
CURVe?
with ASCII encoding, START and STOP of 1 and 5
respectively, and
DATa:SOUrce set to RF_NORMal might return :CURVE
1.20635E-11,6.30522E-12,1.46334E-11,8.97143E-12,4.87173E-12.
CURVe?
with ASCII encoding, START and STOP of 1 and 5
respectively, and
DATa:SOUrce settoRF_NORMalmightreturn:CURVE
1.20635E-11,6.30522E-12,1.46334E-11,8.97143E-12,4.87173E-12
.
2-272 MDO4000/B/C, MSO/DPO4000B and MDO3000 Series Oscilloscopes Programmer Manual
Commands Listed in Alphabetical Order
NOTE. Curve dat
a is transferred from the oscilloscope asynchronously, depending
on the length of the curve record. Such transfers may require several seconds
to complete. During this period, the oscilloscope will not respond to the user
controls. You can interrupt these asynchronous data transfers by sending a device
clear message to the oscilloscope or by interrupting the query with another
command or query. In order to verify that curve data has been completely
transferre
d, it is recommended that you follow such queries with an *ESR?
query to verify there are no error bits set. You can also check the event queue to
determine the cause of the error, if any. If the error was caused by an interrupted
query, then the asynchronous data transfer was not complete when the *ESR?
query was sent. In such cases, it may be necessary to increase the program's
time-out value to ensure that all data is transferred and read.
DATa
These commands specify the format and location of waveform data that is
transferred using the CURVe command, or return the format and location of the
waveform data that is transferred with the CURVe? query. You can use the
INIT
argum
ent to reset all of the
DATa parameters to default values. (Note that the *RST
and FACtor y commands do not reset the DATa parameters.) You can use the
SNap argument to automatically set the DATa:STARt and DATa: STOP values to
the starting and stopping point of the waveform cursors (if on). Note that setting
DATa:STARt and DAT a:STOP automatically sets WFMOutpre:NR_Pt.
(See page 2-95, Waveform Transfer Command Group.)
Group
Waveform Transfer
Syntax
DATa {I NIT|SNAp}
DATa?
Related Commands
CURVe,
DATa:STARt,
DATa:STOP,
DATa:ENCdg,
WFMInpre:NR_Pt,
WFMOutpre:NR_Pt?
Arguments
INIT initializes the waveform data parameters to their factory defaults except
for DATa:STOP, which is set to the current acquisition record length. The data
waveform preamble parameters are initialized to the following values:
MDO4000/B/C, MSO/DPO4000B and MDO3000 Series Oscilloscopes Programmer Manual 2-273