First picture on EEVblog of the new R&S MXO4 series oscilloscope :)

[EEVblog]

I've been busy with other videos and scopes, and there was this 
It's being swapped tomorrow.
https://odysee.com/@eevblog:7/MXO4-Screw-Loose:2

Ah come on, really ? Would have made the "take it apaaaat" one screw faster.

I was actually on a live stream with them going over some of the advanced features when I discovered it. I promised I wouldn't take it apart so they could investigate.

[maxwell3e10]

Is there any update on MXO4? A noise spectrum and characterization of waveform update rate under different conditions would be nice!

[EEVblog]

Is there any update on MXO4? A noise spectrum and characterization of waveform update rate under different conditions would be nice!

Plan is to work on it this week. I just got back from a few weeks walkabout.
But I also have other videos I want to get finished, mailbag shelf is full, all the usual excuses...

[EEVblog]

Finishing shooting the MXO4 unboxing video and tried to test the 4.5Mwfms/sec update, and, well, I don't see it 

[EEVblog]

Finishing shooting the MXO4 unboxing video and tried to test the 4.5Mwfms/sec update, and, well, I don't see it 

I had the measurements turned on. They said they are going to improve this in future firmware. So much for the ASIC.

[goaty]

Settings are the same or comparable ? Like trigger level ?
Update rate on the RTB2k also varies a lot and does rarely reach 50k/s.

[2N3055]

Finishing shooting the MXO4 unboxing video and tried to test the 4.5Mwfms/sec update, and, well, I don't see it 

I had the measurements turned on. They said they are going to improve this in future firmware. So much for the ASIC.

That is analytic scope. It is not used that way...
And 4.5 Mtriggers in segmented mode is very good and very useful.

Set scope to long capture and set search for pulse width less than normal clock width. You will have 100% POI.
Or use pulse width trigger, with segmented mode, and assemble statistics of how glitch happens... Also 100% POI..

[goaty]

I wonder why there is this huge "blind time" of more then a millisecond.
That must be some parameters.
Of course one can use fast segmentation mode, but why it needs so much time between triggers ?

[armandine2]

analytic scope versus a display scope?

[bozidarms]

That is analytic scope.

"Analytic scope" without at least Trends, Tracks and Histograms???

I don't really believe that...

[2N3055]

That is analytic scope.

"Analytic scope" without at least Trends, Tracks and Histograms???

I don't really believe that...

Are you serious ?
Honestly I didn't even check so far...  I EXPECTED it to have at least that...
1000€ scopes have that nowadays...
Thank you for this nugget of information... 

That is absolutely epic fail...
What is the price for then... ?

[bozidarms]

Not even simply Histicons ?!?

Prices from Batronix:

R&S® MXO44-2410       4x 1 GHz                                 € 22.848,- inkl. 19% MwSt.

R&S® MXO4-B1 MSO Option                                          € 3.332,-
R&S® MXO4-B6 Funktionsgenerator                               € 1.666,-
R&S® MXO4-B108 Speichererweiterung 800 Mpts            € 3.094,-
R&S® MXO4-K510 I2C, SPI, RS232, UART Dekoder          € 2.856,-
R&S® MXO4-K520 CAN, CAN-FD, CAN-XL Dekoder           € 2.856,-
R&S® MXO4-K36 Bode Plot                                            € 2.380,-
                                                                                -------------------------
                                                                                  € 39.032,- 

[EEVblog]

Finishing shooting the MXO4 unboxing video and tried to test the 4.5Mwfms/sec update, and, well, I don't see it 

I had the measurements turned on. They said they are going to improve this in future firmware. So much for the ASIC.

That is analytic scope. It is not used that way...
And 4.5 Mtriggers in segmented mode is very good and very useful.

Set scope to long capture and set search for pulse width less than normal clock width. You will have 100% POI.
Or use pulse width trigger, with segmented mode, and assemble statistics of how glitch happens... Also 100% POI..

No, it has nothing to do with segmented mode at all.
It is literally an architecture bug/limitation where if you turn on the horizontal measurements (like frequency) the update rate drops from 1M/wfs/s to 1K/wfs/s.

[nctnico]

Seems reasonable to me as the data needs to be processed for the measurement. Ofcourse there is a choice between using only the Nth acquisition to base calculations on OR doing calculations on all acquisitions. In the first option there is a disconnect between what is shown on screen and what is being calculated.

[EEVblog]

[EEVblog]

Seems reasonable to me as the data needs to be processed for the measurement. Ofcourse there is a choice between using only the Nth acquisition to base calculations on OR doing calculations on all acquisitions. In the first option there is a disconnect between what is shown on screen and what is being calculated.

Not when you realise that the veritcal measurements and cursors have absolutely no impact at all on the waveform speed. It's only very specific horizontal measurements like Frequency which drops the update rate three orders of magnitude.

[nctnico]

If you use an R&S scope for a while, you'll see that using the 'Nsingle' setting for doing a segmented recording is a very efficient way to setup a segmented recording sequence. But I agree it isn't very standard and takes some getting used to. I just used it myself a couple of days ago (on the RTM3004).

[Fungus]

If only there were things called manuals where you could go and type the word "single" and have the answer in a few seconds:



https://scdn.rohde-schwarz.com/ur/pws/dl_downloads/pdm/cl_manuals/user_manual/1335_5337_01/MXO4_UserManual_en_03.pdf

( )

[BU508A]

Marco Reps is measuring the noise of some ADR1000 with a MXO4:

https://youtu.be/mmsBT3Fuggk?t=3030

He uploaded the video two days ago.

[EEVblog]

If only there were things called manuals where you could go and type the word "single" and have the answer in a few seconds:

Except when the manual is wrong. You have to go into the Segmented menu to find the option to change it.

[EEVblog]

Marco Reps is measuring the noise of some ADR1000 with a MXO4:
https://youtu.be/mmsBT3Fuggk?t=3030
He uploaded the video two days ago.

Cool. The Rigol is (slightly) lower noise than the MXO4 though. No surprise given the MXO4 has a 1.5GHz front end. Even if you bandwidth limit, the inherent design noise is higher.

[EEVblog]

If you use an R&S scope for a while, you'll see that using the 'Nsingle' setting for doing a segmented recording is a very efficient way to setup a segmented recording sequence.

Agreed. Segmented mode on most scopes is rather fiddly and annoying in comparison.

[bozidarms]

Noise values ​​for one "Industry-leading system architecture: 18-bit vertical resolution/12-bit ADC" are not so exceptional low as R&S would like them to be.

For MXO4 is stated - RMS noise floor ( HD mode active for bandwidth ≤ 500 MHz)

sensitivity:

HDO4: analog bandwidth   1 GHz               LeCroy HDO  1 GHz

0.5 mV/    98 µV                                                       
1 mV/       104 µV                                                         145 μVrms
2 mV/       116 µV                                                         145 μVrms
5 mV/       152 µV                                                         150 μVrms
10 mV/      238 µV                                                        155 μVrms
20 mV/      436 µV                                                        185 μVrms
50 mV/      1.01 mV                                                      275 μVrms
100 mV/    2.47 mV                                                      500 μVrms
200 mV/    4.43 mV                                                      1.75 mVrms
500 mV/    10.13 mV                                                    2.75 mVrms
1 V/div      19.96 mV                                                    4.90 mVrms

For example, every LeCroy HD Oscilloscope has in sensitivity over 2mV  significantly better values, partly 4x better!

That is not bashing, only pure facts.
BUT, real bashing can one find on R&S official pages:

https://scdn.rohde-schwarz.com/ur/pws/dl_downloads/dl_common_library/dl_brochures_and_datasheets/pdf_1/Comp_sheet_-_MXO4_vs_Lecroy_WaveSurfer_4000HD.pdf

https://scdn.rohde-schwarz.com/ur/pws/dl_downloads/dl_common_library/dl_brochures_and_datasheets/pdf_1/Comp_sheet_-_MXO4_vs_Tektronix_4_Series_MSO_v1.00.pdf

https://scdn.rohde-schwarz.com/ur/pws/dl_downloads/dl_common_library/dl_brochures_and_datasheets/pdf_1/Comp_sheet_-_MXO4_vs_Keysight_4000_X_v1.00.pdf

If you read something like that, you will be speechless - it's amazing that a company with such a reputation uses such lousy and dirty tricks. - just sad.

[EEVblog]

If you read something like that, you will be speechless - it's amazing that a company with such a reputation uses such lousy and dirty tricks. - just sad.

Every manufacturer does those comparisons. Lie by omission is the marketing modus operandi.

[Fungus]

If only there were things called manuals where you could go and type the word "single" and have the answer in a few seconds:

Except when the manual is wrong. You have to go into the Segmented menu to find the option to change it.

They must have moved it around.

Still, the clue is there...