Siglent SDS2000X Plus - Bugs / Missing Features / Feature Requests

[Pinörkel]

Just a little update on this: I found someone with an SDS2204X+ at work who could reliably reproduce the issue on his scope. Consequently, I created an error description, including steps to reproduce the issue and equipped my dealer with this, to contact Siglent about it. Hopefully, they can locate and fix the issue. Until then, I have to fall back to only using the left half of recorded data.

After months and several attempts of not following my step-by-step tutorial for reproducing the issue, Siglent was finally able to confirm and solve the issue. Apparently it was not a firmware, but a hardware issue, since they replaced the whole mainboard after they could not pinpoint the exact source of the issue. After that, I was not able to reproduce the issue any more.

However, upon in-depth testing of the repaired scope I discovered that the logic probe of the scope is faulty. The signal path of channel D0 seems to be broken. Probing the same signal with D0 and D1, it is only displayed on channel D1. This is not an issue of the probe head, since swapping in another probe head does not improve the behavior. It is, however, possible to capacitively couple a signal into D0 by putting the same signal into D1 to D7.

[BillB]

Looking to pick up an SDS2104 Plus, and this is what the display looks like.  Does the newer version have an inverse display mode, or is this a defect?

[tautech]

Looking to pick up an SDS2104 Plus, and this is what the display looks like.  Does the newer version have an inverse display mode, or is this a defect?

Yes it's a defect but could be as simple as the display ribbon cable needs reseating.....although this requires almost complete disassembly. 
Likely to display just fine via the webserver.....

I have seen this as an intermittent fault on another 10" display model.....and all associated parts were replaced under warranty.

[BillB]

aw, crap.

[mawyatt]

That doesn't look like ours, likely what Rob indicated. We have one if you are interested send a PM.

Best

[KungFuJosh]

It's been a long time since I had one of those scopes, but I though it had an inverted display mode? That's exactly what the image looks like. 🤷

[tautech]

It's been a long time since I had one of those scopes, but I though it had an inverted display mode? That's exactly what the image looks like. 🤷

Yes for screenshots only.

[BillB]

Stupid CoPilot AI convinced me that was the case, but after arguing with it and digging through all the user guides and revision notes, I didn't see anything like that.  I know the SHS815 had this mode, and the SDS2000X+ could change trace colors but didn't seem to have a full blown invert.  Of course, all of this after I hit the buy button.   

[tautech]

Stupid CoPilot AI convinced me that was the case, but after arguing with it and digging through all the user guides and revision notes, I didn't see anything like that.  I know the SHS815 had this mode, and the SDS2000X+ could change trace colors but didn't seem to have a full blown invert.  Of course, all of this after I hit the buy button.   

Disassembly is not horrible but you must follow some defined steps, not all of which are in the Service manual. 
I made some notes about it when replacing a mainboard under warranty and put them in the POI list in the SDS2000X Plus main thread:
https://www.eevblog.com/forum/testgear/siglent-sds2000x-plus-coming/

[BillB]

Disassembly is not horrible but you must follow some defined steps, not all of which are in the Service manual. 
I made some notes about it when replacing a mainboard under warranty and put them in the POI list in the SDS2000X Plus main thread:
https://www.eevblog.com/forum/testgear/siglent-sds2000x-plus-coming/

Thanks for the valuable link.  Good grief that looks like a bit of work just to get to that cable!  I know you might only have a sample set of one or two examples of this, but any odds that this is indeed just a cable issue vs being a more involved repair? 

I ask that, given the scope being somewhat new-ish, I've got a message into SiglentNA to see what they might do for me.  So, I might not spend too much time on this if they offer something reasonable. 

[KungFuJosh]

I ask that, given the scope being somewhat new-ish, I've got a message into SiglentNA to see what they might do for me.  So, I might not spend too much time on this if they offer something reasonable.

If you know that the scope is less than 3 years old, then it's covered under warranty and they will repair it. If you don't know, send them the serial number and ask if it's still under warranty.

[BillB]

If you know that the scope is less than 3 years old, then it's covered under warranty and they will repair it. If you don't know, send them the serial number and ask if it's still under warranty.

The FPGA version is 2024-01-29, so I'm thinking it is. 

[tautech]

If you know that the scope is less than 3 years old, then it's covered under warranty and they will repair it. If you don't know, send them the serial number and ask if it's still under warranty.

The FPGA version is 2024-01-29, so I'm thinking it is. 

Send SN# by PM and I'll look it up.

ETA
SDS2PFFD8**** is 2024 production.

[KungFuJosh]

If you know that the scope is less than 3 years old, then it's covered under warranty and they will repair it. If you don't know, send them the serial number and ask if it's still under warranty.

The FPGA version is 2024-01-29, so I'm thinking it is. 

Nice! You should be good to go then.

[BillB]

 Got the scope today and ran it through its paces.  Everything looks good and works except the display.  Already got an RMA for repair.  Thanks all!

Webserver and functions all work great

The Probe check function is pretty cool.  I noticed running through it a few times, it would complain that the 10:1 probe its checking was really something like 9.74 or so and ask if I wanted to keep that attenuation value instead.  I swapped the probe to a different port and repeated and it passed fine.  Moved the probe back to the same port and redid the check at 10:1 and it came back fine.  Had that happen on a few probes on different ports, but eventually I got to the point that all probes checked out on their original ports at 10:1.  Is this to be expected?

[tautech]

Got the scope today and ran it through its paces.  Everything looks good and works except the display.  Already got an RMA for repair.  Thanks all!

Webserver and functions all work great

The Probe check function is pretty cool.  I noticed running through it a few times, it would complain that the 10:1 probe its checking was really something like 9.74 or so and ask if I wanted to keep that attenuation value instead.  I swapped the probe to a different port and repeated and it passed fine.  Moved the probe back to the same port and redid the check at 10:1 and it came back fine.  Had that happen on a few probes on different ports, but eventually I got to the point that all probes checked out on their original ports at 10:1. Is this to be expected?

Is everything clean and spotless ?
Good/sound connection to the probe compensation output also ?

What model probes, 1x/10x or fixed 10x ?
The only other thing I might suggest is to cycle the 10x/1x probe switch a few times in case the switch contacts have oxidised.

[BillB]

Is everything clean and spotless ?
Good/sound connection to the probe compensation output also ?

What model probes, 1x/10x or fixed 10x ?
The only other thing I might suggest is to cycle the 10x/1x probe switch a few times in case the switch contacts have oxidised.

These are all PP215's, and everything is looking brand new.  Cycled switches during initial testing.  Re-ran today, and all passed on first try!  When I did it the first time, I compensated the first one before the check, but then realized that the check would prompt for compensation, so I didn't pre-compensate any of the others.  Some of them were quite a bit off; I wonder if that could have affected the attenuation measurement?  Anyway, I guess I'm good to go now.   

I did manage to score another ebay coup on a "new" SP3050A, but I'll check that out after the scope comes back from Siglent NA and I perform the necessary enhancements.   

[KungFuJosh]

I did manage to score another ebay coup on a "new" SP3050A, but I'll check that out after the scope comes back from Siglent NA and I perform the necessary enhancements.

I have a couple of those.

[tautech]

Is everything clean and spotless ?
Good/sound connection to the probe compensation output also ?

What model probes, 1x/10x or fixed 10x ?
The only other thing I might suggest is to cycle the 10x/1x probe switch a few times in case the switch contacts have oxidised.

These are all PP215's, and everything is looking brand new.  Cycled switches during initial testing.  Re-ran today, and all passed on first try!  When I did it the first time, I compensated the first one before the check, but then realized that the check would prompt for compensation, so I didn't pre-compensate any of the others.  Some of them were quite a bit off; I wonder if that could have affected the attenuation measurement?  Anyway, I guess I'm good to go now.   

For a uncompensated 10x probe, Probe Check would certainly produce an incorrect channel input attenuation result.

We mostly trust our probes but having Probe Check as a further sanity check is valuable just as it is for setting an accurate input attenuation for any of our homebrew DIY probes.

Siglent don't offer a 100x probe so we get them from another supplier and Probe Check identifies these at ~98:1 which is near enough in my book but Probe Check can automatically adjust input attenuation to cancel this small error when greater precision is required.
Pretty good feature which can be found across the range and it's even in the cheap SDS800X HD models.