Siglent SDS3000X HD and upgraded SDS1000X HD

[egonotto]

Hello,

this looks similar to the error I had twice as far as I remember correctly. However, switching the device off and on always helped.

Best regards
egonotto

[pasha]

@egonotto,
But turning it off and on doesn't always work

[egonotto]

@egonotto,
But turning it off and on doesn't always work

Hello,

Does it help at least sometimes? If so, how often did it help and how often did it not?
I have now checked. It was on 25.5 and 20.6, so I only had the error twice. I hope it's not a hardware error. Have you contacted Siglent?

Best regards
egonotto

[Martin72]

This is all very strange and reminds me that I also wanted to test it on my scope.
Which I will do "tomorrow".

[egonotto]

This is all very strange and reminds me that I also wanted to test it on my scope.
Which I will do "tomorrow".

Hello,

for me, the error occurs very rarely. Twice in six weeks. I had previously thought that it was a software error, but what pasha reports scares me a little.
I have no idea how I can reproduce the error. When I have had the error, it has always happened immediately after switching on. You can only see the error if you take a measurement.

Best regards
egonotto

[Martin72]

Hi,

When I have had the error, it has always happened immediately after switching on.

Just speculation, but it may have something to do with the internal calibration, which is displayed as finished 10 minutes after the start.

I have no idea how I can reproduce the error.

If it happens to me too, there are three different scopes where this has occurred.
Then you would have to make sure that you can actually reproduce it, i.e. at least the initial conditions must be the same for all of them.
But we are not there yet.

[pasha]

@egonotto, this is probably a bug, but I don't think I should worry about whether it's measuring correctly this time every time I turn on the oscilloscope.

[egonotto]

Hello,

I still haven't understood how often the error occurs with pasha. Is it always? Or most of the time?

If it occurs very often with pasha, he should contact Siglent. Looking for an error that occurs very rarely, as in my case, is extremely difficult.

Best regards
egonotto

[egonotto]

Hello,

another thing that surprises me, is how little influence the bandwidth limitation has on the noise.

Best regards
egonotto

[pasha]

@egonotto, %50   

[Martin72]

I could be wrong, but with the selected time base the lower frequencies tend to be dominant.

[egonotto]

I could be wrong, but with the selected time base the lower frequencies tend to be dominant.

Hello,

are the values for your device similar?

Best regards
egonotto

[egonotto]

@egonotto, %50   

Hello,

that's bad. Do you want to contact Siglent? Or do you want to complain to the dealer about your device?

Does the error sometimes occur even if the device has been running for a while without any problems?

Best regards
egonotto

[Martin72]

are the values for your device similar?

We will see it later.

[pasha]

@egonotto, %50   

Hello,

that's bad. Do you want to contact Siglent? Or do you want to complain to the dealer about your device?

Does the error sometimes occur even if the device has been running for a while without any problems?

Best regards
egonotto

yes, I will contact.
The problem starts when you first start up and continues until you restart. Sometimes it is necessary to reboot several times.

[Martin72]

Proposal:
Switch on the scope and wait 15 minutes.
Then do what you always do.

[Martin72]

@egonotto:

What settings should I make on the scope for comparison?

[egonotto]

@egonotto:

What settings should I make on the scope for comparison?

Hello,

thanks,
channel 1: 1 V/div and channel 4: 1 V/div,
1 ms/div,
10 Mpts,
bandwidth limitation 20 MHz and 200 MHz,
Memory Management Auto, Max Mem Depth 10M.

Best regards
egonotto

[Martin72]

Hi,
So I have now played around a bit.
Nothing "strange" has happened in the meantime.
But at first I didn't measure anything, nothing was displayed except ***- "thanks" to the new analysis gate.
Then as specified 20M and 200M, looks normal compared to your measurements.
Interesting though:
This was measured in a cold state, after approx. 10min the now familiar message "Calibration completed" appears - And lo and behold....
Ch4 is now significantly better, has come much closer to CH1.
We should keep this in mind when "serious" measurements are due.
First of all, wait...

Martin

[pasha]

Very sensitive multimeters had such a warning.
warm up time

[Martin72]

It should be noted that this message "Calibration Completed" is exclusive to the SDS3000X HD, it is not available on the 2000Xplus, 2000X HD, SDS800X HD.
But yes, a little hint, perhaps displaying "warmup" in a corner, that would be something nice.
(Lecroy scopes show this if you want to activate the self-calibration (is then blocked with the note)).

[pasha]

In fact, "warm up time" is valid for all oscilloscopes, even very old devices can be observed to behave differently 10 minutes after starting up compared to the beginning, specially in mV level measurements.

[Martin72]

There is no question that every appliance needs a certain warm-up time.

[KungFuJosh]

Yeah, tons of test gear require warm-up time. For example, the MXO 5 datasheet specifies:
"Three hours of storage at ambient temperature followed by 60 minutes of warm-up operation"

10 or 15 minutes isn't too bad. 😉

[pasha]