Yeah it's audible when sitting at my other desk ~3 meters away. The picture attached in the previous post is indeed just captured from an audio analyzer app on the phone. The phone app also shows the 6.1 kHz peak just fine at a few meters distance.
I can't seem to find the "Sound off" option? But it's constant, even with the channels disabled, scampling stopped etc.
Utility/System settings/Beeper
Result please ?
It has nothing to do with sounds of the scope.
Yeah it's audible when sitting at my other desk ~3 meters away. The picture attached in the previous post is indeed just captured from an audio analyzer app on the phone. The phone app also shows the 6.1 kHz peak just fine at a few meters distance.
I can't seem to find the "Sound off" option? But it's constant, even with the channels disabled, scampling stopped etc.
I never was bothered by it because I don't hear it.
So I went and measured.
At 1m distance there is slight peak at cca 6kHz but that one is at -88dB ..... So 4 orders of magnitude less than what you have. No wonder I can't hear it.
To investigate further with phone stuck right at the scope, touching it. So there is mechanical transfer too, so worst case scenario acoustically. It was no worse than -67dB.
That is 2 orders of magnitude less that what you claim at some meters.
And it is connected with screen backlight, by the way...
It is not a functional problem. It is not a general problem. It seem to be your particular scope combined with your sensitive hearing that is unlucky combination.
If it bothers you that much, please present the problem to Siglent support through vendor you purchased it from. I'm sure they will find some way to help you.
100% but still possibly a design problem and we need to listen and feedback to HQ for their deeper tests...
I doubt it is any kind of general design problem electrically. Some capacitors and magnetics simply sing.
My scope has exactly same frequency and I had to look for the frequency with microphone and analyser to find it, how quiet acoustically it is.
His scope might simply miss a drop of glue or some peculiarity with soldering or whatever. There might be some variation with his scope specifically but it is not a general design problem, or all of them would have it. But he should report it to Siglent because they might want to know to see if there is some manufacturing issue for a batch or simply his is statistical anomaly.
He might have unlucky component that so happens to sing at that exact frequency.
If that screen PWM frequency is under software control, this might even be solved with nudging PWM frequency few 100Hz up or down, out of mechanical resonance of the "singer"..