Filter
Top Products
1333
Trace/Detector
Query Trace Data
More Information
The format and byte-ordering of the sent or received data is dependent on the FORMat:DATA and
FORMat:BORDer commands. ASCII data consists of a string of comma separated values. REAL or
INTeger data is sent as a definite length block, with a header describing the data to follow.
For example, a four point trace might look like this if in ASCII (FORMat:DATA ASCIi):
–5.87350E+01, –5.89110E+01, –5.87205E+01, –5.12345E+01<NL><END>
and like this if in INTeger with 4 bytes per point (FORMat:DATA INT,32):
#216<16 bytes of data><NL><END>
where the 2 in the #216 means “2 digits of numeric data to follow”, and the 16 is the 2 digits and means
“16 binary bytes to follow” (this is the definite length block format).
Note that the data is terminated with <NL><END>. (For GPIB this is newline, or linefeed, followed by
EOI set true. For LAN, this is newline only.)
Notes: The TRACe[:DATA] command is of the form:
:TRACe:DATA <trace>,<data>
where <trace> can be one of the following parameters:
TRACE1,TRACE2,TRACE3,TRACE4,TRACE5,TRACE6
and where <data> can be
- ASCII data, which consists of a string of values separated by comma
or
- REAL or INTeger sent as a definite length block, with a header describing the
data to follow.
Couplings: Sweep points will affect the amount of data
The FORMat:DATA command describes the different types of data formats
that can be used with trace data.
Use the FORMat:BORDer command to set the byte order.
Initial S/W Revision: Prior to A.02.00
Remote Command: :TRACe[:DATA]? TRACE1 | TRACE2 | TRACE3 | TRACE4 |
TRACE5 | TRACE6
Example: TRAC TRACE1,–1,–2,–3,–4,–5 sends five points to Trace 1. Assuming that
FORMat:DATA is set to ASCII, Y-axis unit is set to dBm, and sweep points is
set to 5, this will result in Trace 1 consisting of the five points –1 dBm, –2
dBm, –3 dBm, –4 dBm, and –5 dBm.
TRAC? TRACE2 queries the test set for the contents of trace 2.
Initial S/W Revision: Prior to A.02.00