Choosing between two oscilloscopes

[Gyro]

By the way: there are also complaints about Rigol, not just Hantek.
I think the more popular a device is, the more grumbling there is in the comments.

I've never got the fuss about the 5ns/div bug. Sure, they ought to fix it,  the trace is dimmer but you can still see it ok. I did replace the fan with a Gelid Silent 5 one, which makes it much quieter. You need to strip back the correct one of the 3 wires, crimp a connector (or patch on a spare one) to the other two and get the warranty label off in one piece though.

[radiolistener]

Is that what you mean?

I'm referring to the case where an incorrect waveform appears due to aliasing. This effect occurs when the time scale is increased (more time per division) until the oscilloscope starts to reduces its sample rate.

In your first screenshot, the sample rate is 1 GS/s, so aliasing issues won’t occur at this time scale for frequencies up to 500 MHz.

However, on the second screenshot, the sample rate has been reduced to 1.25 MS/s, which brings aliasing into play at this time scale.

The most effective way to observe this aliasing effect is by using a square wave with a frequency above the Nyquist limit (half of the sample rate). In this situation, the oscilloscope will display an incorrect frequency for the square wave. With the settings shown in your second screenshot, try a square wave above 625 kHz (for example 625 kHz, 1.25 MHz, 2.5 MHz, etc) the oscilloscope will display very incorrect frequency waveform.

[Aldo22]

With the settings shown in your second screenshot, try a square wave above 625 kHz (for example 625 kHz, 1.25 MHz, 2.5 MHz, etc) the oscilloscope will display very incorrect frequency waveform.

OK, but isn't that a general phenomenon?
You cannot select the sampling rate directly on the DSO2000. It is always an automatic result of the selected memory depth and the time scale.
In the screenshot you can see the scenario you mentioned.
It's true that it doesn't show the waveform, but it's very obvious that it's not what I want to see.
The (I think hardware-) frequency counter still shows the correct frequency (625.060kHz).
When I see something like this, I intuitively turn the S/div knob or increase the memory depth or press “Auto Set”.
So far this has never led me into error.

What is the Hantek specific problem?

[Aldo22]

By the way, for complete idiots like me, the DSO2000 also has a continuous auto mode (Horiz. and Vert.). 
I don't normally use it, but it's helpful if you want to use the scope as a DMM replacement via SCPI, as it always works in the optimum range (like auto range).
I don't have a DMM from which I could read the data on the PC,  so I use the scope for that.
I find it quite useful and sufficiently accurate, considering it's "total crap" for most people here. 

[mike_mike]

Today I received the DSO and I am wondering which software should I install in my PC for downloading jpg or png screenshots from the DSO using USB cable ?

I saw that on the site is mentioned UltraSigma and UltraScope but if I set the image type to JPG then the settings are not saved, and it is still saving the screenshots in bmp format, but I need jpg or png.

[radiolistener]

When I see something like this, I intuitively turn the S/div knob or increase the memory depth or press “Auto Set”.
So far this has never led me into error.

You showed the simple case where user wants to reduce time scale, but this is not the only case when this effect can occur. It is possible to get nice square waveform on the oscilloscope, but it will be completely incorrect because actual frequency is much higher than you will see.

Even experienced user can be confused, I often catch this despite the fact that I well know about this issue and how/why it happens.

What is the Hantek specific problem?

The problem is that it shows just a filled square instead of signal details, because it don't have digital phosphor. It has too small sampling memory and as result it leads to bad experience with low frequency signals. And as I remember, it has some input frontend issues.
 Low sensitivity, noise, low speed, etc. This is just a box of issues, but not oscilloscope.


For car repairs and school demonstration, such an oscilloscope may be suitable, but it is very expensive and bulky for this, although you can find a cheaper and more mobile alternative. For electronics, it is better to take something more or less worthwhile from the brands.

[Gyro]

Today I received the DSO and I am wondering which software should I install in my PC for downloading jpg or png screenshots from the DSO using USB cable ?

I saw that on the site is mentioned UltraSigma and UltraScope but if I set the image type to JPG then the settings are not saved, and it is still saving the screenshots in bmp format, but I need jpg or png.

Sorry, I can't help you with Rigol s/w as I run Linux. I just use a USB stick for screen captures. For best image quality for reasonable size it's best to use png (via the stick anyway).

[Aldo22]

The problem is that it shows just a filled square instead of signal details, because it don't have digital phosphor. It has too small sampling memory and as result it leads to bad experience with low frequency signals. And as I remember, it has some input frontend issues.
 Low sensitivity, noise, low speed, etc. This is just a box of issues, but not oscilloscope.

You always try to convince people of problems with cheap devices where there are no problems.
You've already done that to me in the Zeeweii thread.

I'm not completely stupid, I know what I want to measure and roughly what signal to expect.

The Hantek is a perfectly adequate oscilloscope for beginners/hobbyists.
I have had the device for a year now and there is no such problem.

Why are you doing this? What do you get out of it?
Are you getting money from Siglent or Rigol for spreading FUD?
It is not helpful. Please stop, it's getting boring.

[mike_mike]

I just found this app which helps me to connect to the DSO and download the screenshots in jpeg or png format.
 
https://github.com/FireDeveloper/Fire-SCPI

[radiolistener]

Why are you doing this? What do you get out of it?
Are you getting money from Siglent or Rigol for spreading FUD?
It is not helpful. Please stop, it's getting boring.

Companies pay people to promote and defend their products. It's easy to spot such "bloggers" – they advertise low-quality products, claiming they're thrilled with how cheap and functional they are. These people won’t tell the truth because they're paid to lie. You'll easily spot them, as most reviews aren't done for free. The main lie they promote is that such low-quality products are supposedly well-suited for beginners or hobbyists.

I won't take money to deceive people, which allows me to tell the truth as it is. Hantek is very bad choice from technical point of view.

I can tell you many issues of Siglent and Rigol oscilloscopes, but even with all their issues, they still worth to buy instead of Hantek, even if they are twice expensive.

[Aldo22]

I won't take money to deceive people, which allows me to tell the truth as it is. Hantek is very bad choice from technical point of view.

I can tell you many issues of Siglent and Rigol oscilloscopes, but even with all their issues, they still worth to buy instead of Hantek, even if they are twice expensive.

Then don't buy it!

But please stop spoiling people's hobby.
That has religious overtones with you, whether Zeeweii or Hantek or...

But it doesn't help! It doesn't help anyone!

Both the small Zeeweii and the Hantek are great tools in their field and for their price if you don't pay more than necessary (of course you should pay attention to that).
If this category doesn't interest you, then buy in another category.
It's as simple as that.

But don't warn me about devices that I've been perfectly happy with for over a year.
What's the point?

By the way, the TS has now bought a Rigol, which is great.
You no longer need to “warn” him about your imagined problems.

[Gyro]

I have to agree. There are many informative threads on the Hantek on this forum covering all operational features, hacking, bugs etc. in detail. There are also many video reviews covering operation and internal construction. Any purchaser should do their own research before buying a piece of equipment and there is a wealth of information available.

I also don't see any reason to 'rub somebody's nose in it' for owning one, just because it is cheaper and less perfect than the competition (and that's a game that can be played forever more!). It is what it is, and what it is, is very well documented, so give it a rest @radiolistener!

The OP's problem, apart from inexperience, was lack of the same level of information on one of the scopes he was being offered - before expanding his radar to other manufacturers. That issue has been well and truly resolved! Actually, after seeing Kerry Wong's videos on the more expensive of the two Uni-Ts, I was quite intrigued by some of the features, but I'm not in the market right now and I have some reservations with what I saw of the UI that can only be judged hands-on. Anyway, it's somebody else's turn to take a risk and do a full write-up on here!

[mike_mike]

I notified that if I set the trigger to auto and the memory depth is set at 600k or below, then if triggering to the LM555 output (the LM555 is from the psu tester) the waveform doesn't stabilize. But if changing the trigger to normal or set the memory depth above 600k then the waveform is stabilized. Is this normal ?

[xavier60]

I notified that if I set the trigger to auto and the memory depth is set at 600k or below, then if triggering to the LM555 output (the LM555 is from the psu tester) the waveform doesn't stabilize. But if changing the trigger to normal or set the memory depth above 600k then the waveform is stabilized. Is this normal ?

If the 555 is still running at ~18Hz, adjusting the Hold-off might help.

[Aldo22]

I notified that if I set the trigger to auto and the memory depth is set at 600k or below, then if triggering to the LM555 output (the LM555 is from the psu tester) the waveform doesn't stabilize. But if changing the trigger to normal or set the memory depth above 600k then the waveform is stabilized. Is this normal ?

Now that you've opted for the Rigol, I'd ask in the thread for that particular model, otherwise soon no one here will understand what it's all about.
https://www.eevblog.com/forum/testgear/rigol-ds1102z-e/

[Gyro]

It would also be helpful to look through Dave's videos on scope use and anything on the DS1054Z (which Dave probably uses for most videos as it was his recommendation in past years) as the DS1102Z-E is basically the 2 channel 100MHz unlocked version of that scope - but yes, trigger hold-off should help, maybe reduce the bandwidth too in case of high frequency noise pickup.

[mike_mike]

If the 555 is still running at ~18Hz, adjusting the Hold-off might help.

I tried to set the Hold-off at different values but it doesn't help.
I wrote in the dedicated DS1102Z-E topic.