Products > Test Equipment
Rigol HDO1000 and HDO4000 12bit oscilloscopes launched in China
Martin72:
Hi,
Today I´ve played with the Ultra mode again, the update rates, table will follow.
And for the very last I did a short "silent movie" ;) about the very nice UI...
And now time to say goodbye rigol..Many thanks to batronix for the support.
teddychn:
--- Quote from: Martin72 on February 21, 2023, 09:14:56 pm ---
And unfortunately the "default" and "auto setup" buttons are directly touchable on the rigol (on the same height like the other buttons).
This is the price you must pay for a smaller design I guess, altough there´s a little space left on the front, see pic.
Roll mode you can access via the acquire menu ( just press the acquire button on the front or touch the horizontal icon on the screen (or the field with the samplerate)).
Roll mode is either auto or off - the "scale" shows 50ms, but you can´t change it, maybe reserved for future firmware update.
--- End quote ---
Thanks, Martin,
I compared the SDS2000X Plus with the 2000X HD and the HDO4000. Although the 2000X HD has seven fewer buttons than the 2000X Plus, I still can feel comfortable using it. The HDO4000 has more buttons and knobs than the 2000X HD, but I'm not sure about its maneuverability. However, its auto-scroll mode sounds good, and the graphical interface should make it more manageable.
Actually, I just dislike switching between normal/auto mode back and forth for some trigger modes on some scopes.
Ted
Martin72:
Summary of my 2.5 week test of the Rigol DHO4204 Scope, part 1.
As mentioned at the beginning, the "touch quality" is very decent, even if it doesn't quite reach that of an SDS2000X HD.
Despite the 10" screen, it is compact in size and should fit on any table.
The screen itself is clear and bright, and the resolution is very good.
The touch panel is precise and responds quickly.
The absolute minus point are the fans, the Scope produces a volume that is only surpassed by the infamous WaveJet series from Lecroy - very annoying and cannot be a permanent condition.
The boot time is pleasantly short, after a bit more than half a minute you can already start.
Now we come to the two highlights, so for me personally.
On the one hand, of course, the 12-bit resolution plus the pleasingly low noise - I only knew this from Siglent, but it's nice that Rigol has it now.
The second highlight is without any doubt the new graphical user interface.
No long searching around, everything is accessible as if on a platter, really very well done, you don't really need the "hardware buttons" anymore - This just calls for a tabletscope from Rigol.
Less good are the undoubtedly existing bugs and the somewhat meager equipment in general.
For example, the FFT function, which sometimes delivers confusing results, the lack of functionality (no averaging, no peak detect mode, no chooseable amount of points).
That you can not swap the parameters in measurements, only add or take away, that something is wrong with the acquisition modes, can not be right, that you can not switch between vector and dot mode, etc, etc..
But these are things that Rigol can easily fix with software updates, in my opinion.
Part 2 follows.
Martin72:
Here the table with the wfms/s.
As mentioned before this can´t be the normal mode on the rigol.
Ultra and "Normal" are looking very similar, the blindtime between the packages are greater in the ultra mode.
Second part of my summary will following in the evening..
Martin
rf-loop:
--- Quote from: Martin72 on February 25, 2023, 02:04:41 pm ---Here the table with the wfms/s.
As mentioned before this can´t be the normal mode on the rigol.
Ultra and "Normal" are looking very similar, the blindtime between the packages are greater in the ultra mode.
Second part of my summary will following in the evening..
Martin
--- End quote ---
In Sequence mode there is important to measure guaranteed maximum speed. This what matters.
In Sequence mode we need trust what is minimum trigger interval when not any single trigger event do not drop out! (reason is, imho, obvious)
With 50ns/div SDS200XHD is most fast.
Its guaranteed maximum speed is (my data) ~511,5 ksegment/s
How to test it. You need burst signal. (I have measured it using 80000 pulse burst and segments in oscilloscope sequence 80000. And other t/div / memory values using maximal amount of segments in sequence.
Set scope for 50ns/div, 1k memory length. No matter if dots or vectors and if interpolation is Sinc or x.
Set sequence for 80000 segments
Then without signal start oscilloscope Sequence (now it is waiting trigger)
Start burst. As long as it capture all 80000 signal signal speed is below sequence acquisition guaranteed max speed.
Set now busrt (example pulses, freq 568180kHz as is value in your table)
Somewhere before 80000 it stops acquisition (and waiting more pulses) because some pulses are dropped out , not captured.
Now drop this burst frequency until it can reliable capture every single pulse. Repeat it over ten times until you are sure it never drops any single pulse (segment).
I can say guaranteed maximum speed is 510 ksegment/s (perhaps tiny bit over but there need be some marginal if promise something)
Then about normal mode wfm/s speed. In your table it looks like there is peak value what exist inside acquisition cycle burst.
When we talk wfm/s speed we need handle it using average speed (this we can use example for propability calculations for glitch hunting etc)
SDS2000XHD maximum average wfm/s speed is 98kwfm/s (display mode dots, 50ns/div, single channel in use and trigger just basic edge)
Peak value inside acquisition burst is just bit over 108kwfm/s as is in your table. This is not wfm/s speed it is peak value.
I have measured average speed using HP53131A (with very accurate reference).
Here below is part from my old tests (it is still "preliminary")
Then yesterday and today I did some check about these my values and I did not find errors... (naturally values are bit rounded (down)) :
ETA: Later now after carefully look my collected data... there are some inexplicable exceptions what need further tests and with some different test method.
During normal wfm/s test display looks this below.
Next image below. SDS2000X HD Trig out is connected to SDS2000X Plus. Here can see how it looks like.
Same trig out out signal what go to SDS2kX+ input is splitted and go to HP53131A input and there is used 3s gate time for get value what can see in my table.
Using these kind of fast universal counters need use enough long gate time because signal is not continuous wfm. Also when test other wfm speed with other settings counter Auto trigger leveling may lead to very weird results >> manual level set.
I will not comment on Rigol's results. But the things said earlier about Siglent also raised some small doubts about the Rigol numbers.
@Martin72
What is your SDS2000X HD HW version?
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version