Siglent SDS3000X HD and upgraded SDS1000X HD

[pasha]

Oscilloscope : SDS3034X HD
Software ver.: 1.0.3.3

[Martin72]

Hi,

Set scope to default values( default setting is in the acquisition menu folder), then try again.

[egonotto]

Hello,

I also have 1.0.3.3. Enclosed is the picture of me. It is convenient to use the web interface. Then you can get a screenshot by pressing a button.

Best regards
egonotto

[pasha]

@Martin72; I did it but the result did not change, it gets better after a few restarts. I can't use it like this all the time.
@egonotto, i have not cable connection.

[Martin72]

it gets better after a few restarts.

 

"Better" or the way it should be?

[egonotto]

Hello,

I have also had a problem with an incorrect Stdev measurement a few times. Switching the scope off and on always helped.

Best regards
egonotto

[KungFuJosh]

Note the difference in frequency values between what you two and Pasha are testing. Pasha's examples are significantly different frequencies.

[Martin72]

Switching the scope off and on always helped.

But that should not be THE solution, then something is not quite right.

[pasha]

I will try to install the published firmware,
@KungFuJosh changing the frequency doesn't help much.
@Martin72; better "sorry : the way it should be"

[Martin72]

Note the difference in frequency values between what you two and Pasha are testing. Pasha's examples are significantly different frequencies.

At first he had 4Mhz, which I also used for my pictures.
Then he had 10Mhz and finally 1Mhz....

[KungFuJosh]

Note the difference in frequency values between what you two and Pasha are testing. Pasha's examples are significantly different frequencies.

At first he had 4Mhz, which I also used for my pictures.
Then he had 10Mhz and finally 1Mhz....

10MHz and 20MHz. Another had something like 27kHz vs 349MHz.

Look at both numbers on each screenshot.

[Martin72]

This is what was (incorrectly) measured, look at the hardware counter.
I used this as a guide and set my generator accordingly.

[egonotto]

Hello,

yes, that is correct. The important question is whether it is a software problem that can be rectified with new firmware.
Pasha's last picture had 1 MHz like my last picture. But that shouldn't have any influence on the error.

Best regards
egonotto

[tautech]

Hello,

sometimes the setting is a bit tricky. If I only change the source, this is often ignored. However, if I reactivate the phase, it adopts the setting.

Best regards
egonotto

Please document this in detail and if it it is just a 3kX HD issue or if it can be replicated in other models.
TIA

[Martin72]

This has existed since 2000Xplus, and I complained about it at the time.
In my opinion, it also makes no sense to differentiate between "Simple" and "Advance".
Measuring point 1, which source, which value, done.
Measuring point 2, which source, which value, done.
And so on, but that's not how it works with siglent.

[pasha]

I upgraded to 1.0.3.7 but the problem is still the same.

[egonotto]

Hello,

when I changed the source for the phase measurement, the change was ignored. I had closed the menu with the X. I then noticed that the phase was sometimes deactivated in the menu. Then I always reactivated the phase and it worked.

Best regards
egonotto

PS: The name of the screenshots is now generated differently. Previously it was e.g. ScreenImg (97) now it is e.g. ScreenImg - 2024-07-11T014135.631.

[KungFuJosh]

This is what was (incorrectly) measured, look at the hardware counter.
I used this as a guide and set my generator accordingly.

I'm curious if them being measured incorrectly is related to his issue. You and Ego didn't have that problem.

[2N3055]

Hello,

when I changed the source for the phase measurement, the change was ignored. I had closed the menu with the X. I then noticed that the phase was sometimes deactivated in the menu. Then I always reactivated the phase and it worked.

Best regards
egonotto

PS: The name of the screenshots is now generated differently. Previously it was e.g. ScreenImg (97) now it is e.g. ScreenImg - 2024-07-11T014135.631.

When you open Measurement window you have to select source and then measurement to apply change.. That is how it was implemented.
In Simple measurement mode, there are no 2ch measurements.


This is something that simply works and I have no idea why @Pasha sees this.

I would like to point out to a Analysis menu -> Analysis Gate.
If analysis Gate is set to just a fraction of memory it will measure only there.

Also, if in Measure->Config ->Amplitude strategy and Thresholds need to be set to proper settings


I would recommend @Pasha to start a scope while repeatedly pressing Math button during boot.
That should restore scope to full factory settings.
And try again.

[pasha]

@2N3055, start a scope while repeatedly pressing Math button during boot.
not responce

[egonotto]

@2N3055, start a scope while repeatedly pressing Math button during boot.
not responce

Hello,

please measure Stdev for an active channel without having anything connected to the input .

Best regards
egonotto

[2N3055]

@2N3055, start a scope while repeatedly pressing Math button during boot.
not responce

I assure you it works..
You need to try again.
Just keep on pressing..
It will not say anything but scope will have all user set options reset to factory..

[pasha]

@2N3055, i wil try.

[pasha]

@2N3055, It worked for a while, but when I restarted it went back to its previous state

[pasha]

@egonotto