Anritsu MT9083 Series Operation Manual page 80

Chapter 4 OTDR Commands
4.5.9 TRACe:LOAD:DATA? Command
Syntax: TRACe:LOAD:DATA?<wsp><start>,<end>,<space>
Parameters: <start> Starting distance (km)
Floating point format
Range: 0.0 － (Current distance range - <space>*resolution)
<end> Ending distance (km)
Floating point format
Range: (<start>+<space>*resolution) － (Current distance range).
<space> data point spacing in terms of resolution
Numeric format
Range: 1 － ((Max number of data points between <start> and <end) distance)
<start> Starting distance (km)
Numeric format
Range: 0.0 － (Current distance range - <space>*resolution)
Start value must be less or equal to end value.
Description: TRACe:LOAD:DATA? command has 4 mode.
TRACe:LOAD:DATA?
Get full trace data.
TRACe:LOAD:DATA? <start>
<start>: Start position of the trace data. Distance unit is km.
Get all the trace data form specified start point to the end of distance range.
TRACe:LOAD:DATA? <start>,<end>
<start>: Start position of the trace data. Distance unit is km.
<end>:End position of the trace data. Distance unit is km.
Get all the trace data form specified start to end position.
TRACe:LOAD:DATA? <start>,<end>,<space>
<start>: Start position of the trace data. Distance unit is km.
<end>:End position of the trace data. Distance unit is km.
<space> data point spacing in terms of resolution.
Get the trace data form specified start to end position at the interval specified by
space.
Refer to Section 2.5 "Message Format – Binary Data" for further details.
trac:load:data? 0.0, 10.0, 1 --- "BINARY ARRAY"
Example:
#510006 //SCPI data size message for binary data transfer followed by array of data
point bytes. First four bytes – unsigned long (big endian) for number of data points
to follow,
Every next two bytes – unsigned short for each data point requested
Response: Requested data points as an array of bytes per SCPI binary transfer specifications.
Errors: (–225, "std_illegalState, Trace Not Ready")
(–224, "std_illegalValue, Invalid Parameter Value")
4-28