hi hansibull,
thanks for your sharing, finally I got my account sorted so I can reply in this thread.
I made a CNC version mount adapter based on your model, the AL6061 CNC part is stupidly strong for this uasage. the reason I made it out AL is in my country AL-CNC(+sand blusting+anodizing) is cheaper than 3D printing.
of course, you see I made some grinding on the part as I forget the BNC notch, but anyway I've updated the model based on that, I've also attached the model here in case someone need it.
the screws needed are:
M3*14mm staineless Torx, 5pcs, for fixing the adapter onto the scope;
M4*16mm staineless socket head countersunk screws, 4pcs, for fixing VESA mount(my VESA mount plat is 2mm thick, can adjust the screw length based on the plate thickness)
M4 blind thumb screws, inner thread depth is 6.5mm, 4 pcs
thanks again for sharing the model, cheers!
Nice work!!
Not a criticism but a question, why not move the VESA mount to the right away from the fan opening?
Since it's a VESA mount having a slight imbalance with the offset mount shouldn't be a problem and leaves a clearer air path for the fan.
Best,
Siglent SDG2122X: Ch1, 1MHz, 4Vpp, Sine
Ch2, 1.00001 MHz, 4Vpp, Sine
Scope F1: FFT(C1+C2)
3 different results, as shown below. Ideally, I would expect two peaks at 3dbV.
With ERES 1.0, the peaks are about 0dBV
Aha! Flattop window amplitudes about spot on!
You need to use Flattop window.
Take a note that measured signal is not in harmonic relation to bin frequency..
This measurement is at very edge.
You are measuring two signals 10Hz away, with a RBW that is almost 5Hz. There will be significant bleed between bins.
Try with 15-20 Hz spacing
ERES 3 with that low sampling frequency will act as low pass filter. Don't use it here, it has no use with FFT.
Enable split view and you will see it in time domain.
Averaging will work well with channel it is triggered on. The other channel with different frequency will not average properly.
You cannot use it. Enable split view and you will see it in time domain.
To make sure amplitude is OK, set AWG for 50 Ω and scope inputs for 50 Ω.
hi hansibull,
thanks for your sharing, finally I got my account sorted so I can reply in this thread.
I made a CNC version mount adapter based on your model, the AL6061 CNC part is stupidly strong for this uasage. the reason I made it out AL is in my country AL-CNC(+sand blusting+anodizing) is cheaper than 3D printing.
of course, you see I made some grinding on the part as I forget the BNC notch, but anyway I've updated the model based on that, I've also attached the model here in case someone need it.
the screws needed are:
M3*14mm staineless Torx, 5pcs, for fixing the adapter onto the scope;
M4*16mm staineless socket head countersunk screws, 4pcs, for fixing VESA mount(my VESA mount plat is 2mm thick, can adjust the screw length based on the plate thickness)
M4 blind thumb screws, inner thread depth is 6.5mm, 4 pcs
thanks again for sharing the model, cheers!
Nice work!!
Not a criticism but a question, why not move the VESA mount to the right away from the fan opening?
Since it's a VESA mount having a slight imbalance with the offset mount shouldn't be a problem and leaves a clearer air path for the fan.
Best,
hi mawyatt,
you are right on the point, scope to be off-centered and we can place a device holder (like probes/DMMs holder) on the empty side, seems elegent, isn't it? will try to make one when available.
cheers for the idea~
Kind regards
Well, it looks like channel 1, 2 AND 3 on my scope are dead.... Barely used it and this thing is just junk.
Never used for anything but a few volts peak-to-peak and I never used channel 3 or 4 until just now......
I have tried a full reset and self calibration, and no change. Channel 1 and 2 also have weird offsets as you cycle through the ranges too.
Putting a 10MHz sine in from my Tektronix SG5030 levelled sine wave generator and I get these results:
Ch1, 50R, DC, x1
500uV/div @ 5mV p-p input = >4.26mV p-p
1mV/div @ 5mV p-p input = 6.5mV p-p
2mV/div @ 5mV p-p input = 9.3mV p-p
5mV/div @ 5mV p-p input = 9.3mV p-p
10mV/div @ 10mV p-p input = 18.2mV p-p
20mV/div @ 100mV p-p input = 19.8mV p-p
50mV/div @ 100mV p-p input = 62.3mV p-p
100mV/div @ 500mV p-p input = 610.5mV p-p
200mV/div @ 1V p-p input = 200mV p-p
500mV/div @ 1V p-p input = 627mV p-p
1V/div @ 5V p-p input = 6.13V p-p
Ch2, 50R, DC, x1
500uV/div @ 5mV p-p input = >4.26mV p-p
1mV/div @ 5mV p-p input = 6.5mV p-p
2mV/div @ 5mV p-p input = 9.3mV p-p
5mV/div @ 5mV p-p input = 9.5mV p-p
10mV/div @ 10mV p-p input = 18.5mV p-p
20mV/div @ 100mV p-p input = 20.1mV p-p
50mV/div @ 100mV p-p input = 63.0mV p-p
100mV/div @ 500mV p-p input = 616.2mV p-p
200mV/div @ 1V p-p input = 202mV p-p
500mV/div @ 1V p-p input = 635mV p-p
1V/div @ 5V p-p input = 6.18V p-p
Ch3, 50R, DC, x1
500uV/div @ 5mV p-p input = >4.26mV p-p
1mV/div @ 5mV p-p input = 5.3mV p-p
2mV/div @ 5mV p-p input = 5.3mV p-p
5mV/div @ 5mV p-p input = 5.3mV p-p
10mV/div @ 10mV p-p input = 10.6mV p-p
20mV/div @ 100mV p-p input = 100.7mV p-p
50mV/div @ 5mV p-p input = 320mV p-p
100mV/div @ 5mV p-p input = 640mV p-p
200mV/div @ 1V p-p input = 1.01mV p-p
500mV/div @ 1V p-p input = 1.02mV p-p
1V/div @ 5V p-p input = 5.06V p-p
Ch4, 50R, DC, x1
500uV/div @ 5mV p-p input = >4.26mV p-p
1mV/div @ 5mV p-p input = 5.3mV p-p
2mV/div @ 5mV p-p input = 5.3mV p-p
5mV/div @ 5mV p-p input = 5.3mV p-p
10mV/div @ 10mV p-p input = 10.5mV p-p
20mV/div @ 100mV p-p input = 100.6mV p-p
50mV/div @ 100mV p-p input = 101.5mV p-p
100mV/div @ 500mV p-p input = 502.9mV p-p
200mV/div @ 1V p-p input = 1.01mV p-p
500mV/div @ 1V p-p input = 1.02mV p-p
1V/div @ 5V p-p input = 5.04V p-p
I bought it at christmas, so maybe still under warranty? Problem is I bought it in Australia and now am in Japan, so I have no idea how warranty will now work (or not as the case may be).
If there's no warranty, this one might be for the scrap pile?
@ TERRA Operative
Can you perform a self calibration cycle?
I did a self calibration cycle before running the posted tests, no improvement.
I checked on the Siglent website for warranty status and this scope has a couple years left, except I bought it in Australia and took it back to Japan with me, so that'll make things fun..
I sent of an email to Siglent to see what the go is..
Well, it looks like channel 1, 2 AND 3 on my scope are dead.... Barely used it and this thing is just junk.
Never used for anything but a few volts peak-to-peak and I never used channel 3 or 4 until just now......
I have tried a full reset and self calibration, and no change. Channel 1 and 2 also have weird offsets as you cycle through the ranges too.
Putting a 10MHz sine in from my Tektronix SG5030 levelled sine wave generator and I get these results:
Ch1, 50R, DC, x1
500uV/div @ 5mV p-p input = >4.26mV p-p
1mV/div @ 5mV p-p input = 6.5mV p-p
2mV/div @ 5mV p-p input = 9.3mV p-p
5mV/div @ 5mV p-p input = 9.3mV p-p
10mV/div @ 10mV p-p input = 18.2mV p-p
20mV/div @ 100mV p-p input = 19.8mV p-p
50mV/div @ 100mV p-p input = 62.3mV p-p
100mV/div @ 500mV p-p input = 610.5mV p-p
200mV/div @ 1V p-p input = 200mV p-p
500mV/div @ 1V p-p input = 627mV p-p
1V/div @ 5V p-p input = 6.13V p-p
Ch2, 50R, DC, x1
500uV/div @ 5mV p-p input = >4.26mV p-p
1mV/div @ 5mV p-p input = 6.5mV p-p
2mV/div @ 5mV p-p input = 9.3mV p-p
5mV/div @ 5mV p-p input = 9.5mV p-p
10mV/div @ 10mV p-p input = 18.5mV p-p
20mV/div @ 100mV p-p input = 20.1mV p-p
50mV/div @ 100mV p-p input = 63.0mV p-p
100mV/div @ 500mV p-p input = 616.2mV p-p
200mV/div @ 1V p-p input = 202mV p-p
500mV/div @ 1V p-p input = 635mV p-p
1V/div @ 5V p-p input = 6.18V p-p
Ch3, 50R, DC, x1
500uV/div @ 5mV p-p input = >4.26mV p-p
1mV/div @ 5mV p-p input = 5.3mV p-p
2mV/div @ 5mV p-p input = 5.3mV p-p
5mV/div @ 5mV p-p input = 5.3mV p-p
10mV/div @ 10mV p-p input = 10.6mV p-p
20mV/div @ 100mV p-p input = 100.7mV p-p
50mV/div @ 5mV p-p input = 320mV p-p
100mV/div @ 5mV p-p input = 640mV p-p
200mV/div @ 1V p-p input = 1.01mV p-p
500mV/div @ 1V p-p input = 1.02mV p-p
1V/div @ 5V p-p input = 5.06V p-p
Ch4, 50R, DC, x1
500uV/div @ 5mV p-p input = >4.26mV p-p
1mV/div @ 5mV p-p input = 5.3mV p-p
2mV/div @ 5mV p-p input = 5.3mV p-p
5mV/div @ 5mV p-p input = 5.3mV p-p
10mV/div @ 10mV p-p input = 10.5mV p-p
20mV/div @ 100mV p-p input = 100.6mV p-p
50mV/div @ 100mV p-p input = 101.5mV p-p
100mV/div @ 500mV p-p input = 502.9mV p-p
200mV/div @ 1V p-p input = 1.01mV p-p
500mV/div @ 1V p-p input = 1.02mV p-p
1V/div @ 5V p-p input = 5.04V p-p
I bought it at christmas, so maybe still under warranty? Problem is I bought it in Australia and now am in Japan, so I have no idea how warranty will now work (or not as the case may be).
If there's no warranty, this one might be for the scrap pile?
Hi!
Did you try how it works on 1MΩ input with external 50Ω terminator?
Before going further, could you please apply/reapply latest FW and then run self-cal again, if you didn't try that already.
I have recycled the ac line power to correct a similar issue. Unplugged/replugged it from the AC source and it worked in my case.
Well, happy days.
I reflashed the firmware and ran a full self cal and it's all good again.
Dunno WTF happened, but it's ok now......
Thanks to 2N3055!
I reflashed the firmware and ran a full self cal and it's all good again.
It was all planned to make you like the unit even more!
Good to hear that it was just software and easily repairable. Most probably 2N3055 will report the issue. Strange that the full reset didn't correct the issue, unless some file got corrupted.
Well, happy days.
I reflashed the firmware and ran a full self cal and it's all good again.
Dunno WTF happened, but it's ok now......
Thanks to 2N3055!
Pleasure is all mine!
I'm glad all is OK now.
I have it for quite some time and it has been reliable so far. And I think it is most used scope in my lab.
I reflashed the firmware and ran a full self cal and it's all good again.
It was all planned to make you like the unit even more!
Good to hear that it was just software and easily repairable. Most probably 2N3055 will report the issue. Strange that the full reset didn't correct the issue, unless some file got corrupted.
I make it a point to do full default to factory setting of the scope before FW update.
As these scopes sometimes gain significant new core features in new FW, that way I know that for sure combination of internal states and variables will upgrade fine, because FW surely knows how to upgrade all internal structures when they are default.
That is not necessary and it usually goes just fine, but I am risk averse....Just a good practice, same as doing FW update when powered from UPS...
Dunno WTF happened, but it's ok now......
I also had this with my 2504X HD, but I ran the self-calibration several times without flashing again, then it was fine again.
And it also came on suddenly, from one day to the next... And then never again.
I was confronted with something similar just after the scope was a few days old after running self cal. Offset problems on all channels and wrong amplitudes shown as if the volt/div setting are not working anymore. I ran the self cal two times after which the problem was solved.
There must be a bug in there. But I haven't found or stumbled upon a method to reproduce this behavior.
There is also an other problem with the self call routine in that sometimes after running a self cal you can see an offset on a random channel. Not much but enough to bother me.
Just from the comments of Martin and temperance I would say there are 2 bugs at play here: the one that caused the problem and one in the factory reset (where you need to do it multiples times in order to fully reset...)
I also had this with my 2504X HD, but I ran the self-calibration several times without flashing again, then it was fine again. And it also came on suddenly, from one day to the next... And then never again.
Just like Martin I have never seen this problem again. But it kind of bothers me that the calibration might be off without me knowing about it. As such I found myself double checking measurements just to be sure.
I found this in my mailbox. I reported this problem to the distributor Jan 11 2023:
"Het eerder beschreven probleem met de gain/off set voor CH1 doet zich ook bij anderen voor:
https://www.eevblog.com/forum/testgear/siglent-sds2000x-hd-12bit-(published-for-chinese-domestic-market-only)/msg4625605/#msg4625605Na een paar keer kalibreren is het probleem verholpen."
The e-mail in question to the distributor contains a screenshot showing the noise on CH1 with a shorted input when the gain / volt/div are wrong after the scope managed to load wrong calibration values.
Here we go again. Lost calibration yesterday. Same as before, reset to default does not help. Had to remove ac line power again and run a new calibration. All captures were with a 4Vpp input.
Does anyone know if an upcoming update might address this issue? Not real happy at the moment
Here we go again. Lost calibration yesterday. Same as before, reset to default does not help. Had to remove ac line power again and run a new calibration. All captures were with a 4Vpp input.
Does anyone know if an upcoming update might address this issue? Not real happy at the moment
Captures indicate a 10x probe was being used.
Did you run Probe Check to exclude the probe from being the problem ?
Here we go again. Lost calibration yesterday. Same as before, reset to default does not help. Had to remove ac line power again and run a new calibration. All captures were with a 4Vpp input.
Does anyone know if an upcoming update might address this issue? Not real happy at the moment
Could you please post Info page: FW and HW rev.
If you didn't try it yet, please download latest FW and reapply it again, with factory defaulting a scope before..
I presume you are normally shutdown scope with soft button or menu command.
I went and checked and this is not a widespread problem. I have the scope for 2 years now and had other problems with early FWs but never had this calibration error.
My scope would possibly be different HW rev..
Here we go again. Lost calibration yesterday. Same as before, reset to default does not help. Had to remove ac line power again and run a new calibration. All captures were with a 4Vpp input.
Does anyone know if an upcoming update might address this issue? Not real happy at the moment
The phenomenon seems to be related to startup, and the following attempts can be made
1. Can multiple restarts work properly?
2. Upgrade to the same software version as everyone else.
3. Contact Siglent Company and have them analyze your issue.
.... and some scopes you should recheck the datasheets for.
Hello,
which scope do you mean? Perhaps MXO 4 or MXO 5?
RTB, RTM and RTA have far more than twice as much segmented memory. RTA has about 2 GSa segmented memory.
Cleverscope CS328A uses double buffers and makes the second buffer available for segmented memory.
The MHO3 has about 2 times 860 MSa of segmented memory.
If I remember correctly, I have more than 300 MSa of segmented memory in my DHO1074.
Best regards
egonotto
Very interesting comparation. I've found that DHO1074 have 124 frames, all channels enabled, 1Mpts / channel. Total 4 x 124Mpts. For only one channel enabled at 1Mpts, we have 496 frames.
Regarding the loss of calibration:
1/ not a probe issue
2/ I always shut it down with the soft button
3/ multiple restarts do not restore the calibration to normal
Firmware has been reflashed. Will report back if appropriate. Thanks everyone!
What is minimum rising/falling edge trigger sensitivity level on SDS2000X HD?
On some other scopes trigger level needs to be
at least 0.25-0.3 div from min/max signal level.