Jeremy Li

Dear all,
1. Is it possible to transfer both analog waveform data and spectrum view data in one trigger event?(MSO 4 Series)  if yes, how should I do, how to input the string after DATa:SOUrce<?>

I tried to fetch（CH1,CH2) and then fetch SV (CH1_SV_NORMal, CH2_SV_NORMal data), but it seems only able to fetch one sv data, and I still not sure if the SV data corresponding to the channel and current analog data.  

 2. How can I know how many data points(DATa:STOP)  should I set for the curve? command to fetch SV data.  the MDO 3 series is a fixed 750 data points in the mannual.

3.  Should I use 10*log(1000 * x)  to calculate the SV (CH1_SV_NORMal) DATA? the output seems didn't match what I have saw on the scope screen.

Hi Teles,

Thanks for the information.

May I ask if the bandwidth of the RF input channel in 3 Series MDO models is normally higher than the 4 Series MSO models?

Is the Spectrum View of 4 Series MSO models(MSO44)  type of scopeFFT? Or it is same as the built in RF channel of 3 Series MDO with different kind of probe?

Dear All,

The Tektronix 3 Series MDO models have a built-in RF input,while  4 Series MSO modes don't have this input.

 3 Series MDO (RF Commands ) , 4 Series (Spectrum View commands)
As described in the  3 Series MDO programmer manual:
MDO instruments calculate Fast Fourier Transform calculations (FFTs) with
a 1,000 to ~2,000,000 point output, depending on the acquisition settings. It
then reduces that FFT output into a 750 pixel-wide display

Is that means the RF function could be calculated according to the measurement of CH1-CH4 channels even we don't have RF input on 3 Series MDO models.

Could someone tell me more about the difference,  thanks in advance.

Hi 
I found the MSO44/46 also have issue when connecting via USB, it seems the "CLEAR" command would make them stop response. but via LXI, they seem working well. even if I was able to capture data from the scope, it is easily lose communication when connecting via USB.

Hi Teles.
Thank you very much.  It is ok now by adding "type+class ".

The command for MSO 4 series doesn't work correctly for MDO 34, It seems only below type could be selected.
Syntax TRIGger:A:TYPe {EDGe|LOGIc|PULSe|BUS|VIDeo}

But below commmand is working fine if we select the timeout type manually.
TRIGger:A:TIMEOut:POLarity
TRIGger:A:TIMEOut:SOUrce