Remote control commandsMXO 4 Series
633User Manual 1335.5337.02 ─ 07
Table 17-5: Header data
Position Meaning Example
1 XStart, acquisition time before trigger, in s -5E-008 = - 50 ns
2 XStop, acquisition time after trigger, in s 5E-008 = 50 ns
3 Number of measurement events = number of points
in the track waveform
1000
4 Always 1 1
Suffix:
<mg>
.
1...16, index of the measurement
Usage: Query only
Asynchronous command
MEASurement<mg>:TRACk:DATA[:VALues]? [<Offset>[,<Length>]]
Returns the data of the indicated track waveform for transmission from the instrument
to the controlling computer. The data can be used in MATLAB, for example.
Without parameters, the complete waveform is retrieved. Using the offset and length
parameters, data can be retrieved in smaller portions, which makes the command
faster. If you send only one parameter, it is interpreted as offset, and the data is
retrieved from offset to the end of the waveform.
Suffix:
<mg>
.
1...16, index of the measurement
Query parameters:
<Offset> Number of offset track points, which are ignored in the data
transfer.
[<Length>] Number of track points to be retrieved.
Return values:
<Data> List of values according to the format and content settings.
Usage: Query only
Asynchronous command
17.13 Cursor measurements
Some of the commands in the following chapter are asynchronous. An overlapping or
asynchronous command does not automatically finish executing before the next com-
mand starts executing. If overlapping commands must be executed in a defined order,
e.g. to avoid wrong measurement results, they must be serviced sequentially.
To prevent an overlapping execution of commands, one of the commands *OPC,
*OPC? or *WAI can be used after the command or a command set.
Cursor measurements
To Next Page
Loading...
