Siglent SDS2000X HD, missing Features and Bugs

[tautech]

Thank you. I have tried rapidly and repeatedly pressing the Math button during startup without success. I'll try again.

Replied to your PM and sorry we/I don't yet have a HD recovery package.
Contact Ohio:
support@siglentna.com

For our info, do you know the firmware version it was running, latest is V1.2.1.1

[Ulrich.G]

I'm wondering whether there is somewhere a counter how many times the scope has been already powered up. I'm pretty sure its not available in the scope system information. Is there a SCPI command which returns this information?

[JBK]

Thanks to everyone who replied about the startup issue I was having. I finally got the 'MATH' button technique to work after about 30 or so restarts.

[2N3055]

Thanks to everyone who replied about the startup issue I was having. I finally got the 'MATH' button technique to work after about 30 or so restarts.

OK now check if firmware is latest one. Also perform full factory reset of the scope. That should clean up any internal variables and settings to safe beginning values..

[Ulrich.G]

Keep pressing Math key at boot...Be persistent..
If it got stuck in some "unusual" internal stat that might help..

Which functionality is behind the Math button during the boot process?

______________

Just saw, thats described in the SDS2000X HD service manual (page 57) as troubleshooting procedure. Maybe starting the scope with default parameters or so.

[tautech]

I'm wondering whether there is somewhere a counter how many times the scope has been already powered up. I'm pretty sure its not available in the scope system information. Is there a SCPI command which returns this information?

It's carefully tucked away in the PW protected Developer Options. Best you keep outta there 

[Martin72]

I know the PW - By three we both are writing it down here and see if it´s the same.
One, two...

[JBK]

OK now check if firmware is latest one. Also perform full factory reset of the scope. That should clean up any internal variables and settings to safe beginning values..

I'm running the latest 1.2.1.1 firmware. I'll perform a factory reset. It's looking like this was just a one-off incident. The scope has been stable otherwise.

[tautech]

OK now check if firmware is latest one. Also perform full factory reset of the scope. That should clean up any internal variables and settings to safe beginning values..

I'm running the latest 1.2.1.1 firmware. I'll perform a factory reset. It's looking like this was just a one-off incident. The scope has been stable otherwise.

Also Secure Erase which IIRC is in the Save/Recall menu. This will erase all User settings.

[Ulrich.G]

I know the PW - By three we both are writing it down here and see if it´s the same.
One, two...

 

[Ulrich.G]

It's carefully tucked away in the PW protected Developer Options. Best you keep outta there 

I'm wondering why Siglent hides this, in their SPD3303X series power supplies its displayed on an info screen.

[tautech]

It's carefully tucked away in the PW protected Developer Options. Best you keep outta there 

I'm wondering why Siglent hides this, in their SPD3303X series power supplies its displayed on an info screen.

Since the new DSO UI was released in SDS5000X the boot # info has been hidden whereas all previous DSO's it was available. Maybe they no longer think it's important to anyone. 

[graybeard]

...but who has CD players these days ? 

I keep a SATA DVD drive in an powered enclosure with a USB cable.   I also have a USB floppy drive.    Both are occasionally useful.

[Martin72]

I wonder when the next update will come...
The longer it lasts the better it gets, I hope.

It will be superior I guess...

[TopQuark]

Probe readout pin customisation

I recently got myself a couple of Cal Test CT4200 x1 probes, they have a readout pin connected to ground with 1k ohms. When I plug the probe in, the scope recognises the probe is plugged in, but sets the input attenuation setting to 10x.

I measured the original probes that came with the SDS2kX HD (SP5050A), and the resistance between readout pin and ground is 11k ohms.

The scope recognises everything between a short to 49k ohms as a 10x probe being plugged in.

While there don't seem to be standards stating the readout pin resistance vs attenuation setting, perhaps the scope can let users set custom resistance ranges to match the probe attenuation setting? (assuming the readout pin resistance is read with an ADC)

As it stands, the scope's behaviour may lead to erroneous readings with certain probes. I know this is an edge case, but point still stands.

[tautech]

Probe readout pin customisation

I recently got myself a couple of Cal Test CT4200 x1 probes, they have a readout pin connected to ground with 1k ohms. When I plug the probe in, the scope recognises the probe is plugged in, but sets the input attenuation setting to 10x.

I measured the original probes that came with the SDS2kX HD (SP5050A), and the resistance between readout pin and ground is 11k ohms.

The scope recognises everything between a short to 49k ohms as a 10x probe being plugged in.

While there don't seem to be standards stating the readout pin resistance vs attenuation setting, perhaps the scope can let users set custom resistance ranges to match the probe attenuation setting? (assuming the readout pin resistance is read with an ADC)

As it stands, the scope's behaviour may lead to erroneous readings with certain probes. I know this is an edge case, but point still stands.

100%

Unfortunately the only sense probes properly recognised are 10x in 2000 class DSO's. 
I've thrown mud about this and it seems only the more upmarket models get the attenuation ratios correct. 

For other than 10x you need set attenuation manually. 

[Ulrich.G]

100%

Unfortunately the only sense probes properly recognised are 10x in 2000 class DSO's. 
I've thrown mud about this and it seems only the more upmarket models get the attenuation ratios correct. 

For other than 10x you need set attenuation manually. 

Maybe its time that at least the active probes are not longer controlled by proprietary connectors but by USB interface. There seems to be an unspoken agreement to support active probes only by oscilloscopes with a bandwidth higher than 500Mhz. Am I wrong with that?

[tautech]

Maybe its time that at least the active probes are not longer controlled by propietary connectors but by USB interface. There seems to be an unspoken agreement to support active probes only by oscilloscopes with a bandwidth higher than 500Mhz. Am I wrong with that?

Yes, it that the only thing that seems drive manufacturers is to capture users into their ecosystem with these horrible proprietary connectors......only horrible in that you can't use them on another brand.

Oh don't worry, many or us behind the scenes have asked for USB powered active probes instantly recognised by the instruments SW and input attenuation and measurement units automatically set to match. However would it be a massive hardship to take active probes to another brand and set them up manually ?

It's not like this is rocket science, our phones have been recognised by PC's for years.

[Martin72]

Hi,

We had already addressed this here months ago, but gladly repeated again:
It would be very good if you could choose the labeling of the vertical axis on the left or right side...

[TopQuark]

Feature Request:

Allow Ch3/Ch4 and Math channel as source for X/Y mode.

I recently ideated about the possibility to measure B-H curves with a scope:

Say you have to characterize a ferrite core, I think the gist of it would look something like: Wind two winding, primary for magnetizing the core, secondary winding for sensing.

- AWG drives primary, an amplifier is probably needed to get reasonable current into the primary to drive it into saturation.
- Measure current into primary + have user input number of pri turns and you get field strength (H), roughly.
- Measure and integrate secondary voltage + have user input number of sec turns and you get flux density (B), roughly.
- Plot in XY and you should have a BH curve.
- Stuff like saturation flux density, coercive force, remanence, hysteresis losses etc. can be calculated with maths.
- Some kind of offset/servo is probably needed to keep the secondary voltage integration in check.
- AWG allows measurement of B-H curves across different frequencies.

I wanted to give it a try with the 2000X HD, but XY mode only support Ch1 and Ch2 as source, but not other physical channels nor math channels 

I really don't want to build an actual integrator circuit to plot B-H curves, when the scope hardware and software is more than capable to do it itself! 

[seronday]

Zone Trigger Issue.

It appears that the Siglent SDS2000X HD has a Zone Trigger issue similar to the one found in the SDS2000X Plus as described in
https://www.eevblog.com/forum/testgear/siglent-sds2000x-plus-coming/msg4428769/#msg4428769

On the SDS2000X HD, the Zone Trigger function also fails to trigger at certain frequencies.

The same test as used for the SDS2104X Plus was applied to the SDS2104X HD.

That is, a signal which consists of a Low amplitude pulse followed by a High amplitude pulse.
The objective is to have the oscilloscope only trigger on the Low amplitude pulse and not on both pulses.

The SDS2104X HD is configured as follows:-

Time / Div    100us
Rising Edge Trigger
Fast Acquisation Mode
Zone trigger 1 is set as "Not Intersect" and placed above the Edge Trigger level in the area where the Higher amplitude pulse would be.

The frequency of the test signal is taken from the SDS On Screen frequency display

An example of the test results is listed below:-

   Triggering works correctly :-    4638Hz to 4982Hz.
   Triggering Fails :-                     4984Hz to5306Hz
   Triggering works correctly :-    5308Hz to 5636Hz

   This pattern keeps repeating

Attached are two screen prints.
 One shows when the Zone Trigger is working. The other shows when the Zone Trigger has Failed.

The frequency ranges where the Zone Trigger Fails depends on the Time / Div , Memory settings and Fast or Slow Aquisation mode.

[2N3055]

Zone Trigger Issue.

It appears that the Siglent SDS2000X HD has a Zone Trigger issue similar to the one found in the SDS2000X Plus as described in
https://www.eevblog.com/forum/testgear/siglent-sds2000x-plus-coming/msg4428769/#msg4428769

On the SDS2000X HD, the Zone Trigger function also fails to trigger at certain frequencies.

The same test as used for the SDS2104X Plus was applied to the SDS2104X HD.

That is, a signal which consists of a Low amplitude pulse followed by a High amplitude pulse.
The objective is to have the oscilloscope only trigger on the Low amplitude pulse and not on both pulses.

The SDS2104X HD is configured as follows:-

Time / Div    100us
Rising Edge Trigger
Fast Acquisation Mode
Zone trigger 1 is set as "Not Intersect" and placed above the Edge Trigger level in the area where the Higher amplitude pulse would be.

The frequency of the test signal is taken from the SDS On Screen frequency display

An example of the test results is listed below:-

   Triggering works correctly :-    4638Hz to 4982Hz.
   Triggering Fails :-                     4984Hz to5306Hz
   Triggering works correctly :-    5308Hz to 5636Hz

   This pattern keeps repeating

Attached are two screen prints.
 One shows when the Zone Trigger is working. The other shows when the Zone Trigger has Failed.

The frequency ranges where the Zone Trigger Fails depends on the Time / Div , Memory settings and Fast or Slow Aquisation mode.

What FW are you running please?

[seronday]

FW Ver. is   1.2.11

Regards

[Martin72]

From the 2k Plus thread:

The beta has only been available for a few weeks so maybe they're ironing out a few issues however that indicates it's quite close.

Well, (I) we made a table of bugs/wishes a couple of months ago, let´s see which points we can cross off then.
For example, if the four math channels should really come and then still work without great performance losses, that would be a great success(for the users and for siglent).
I'm curious to see whether the 5000X will follow suit and especially what will happen with the Siglent/lecroy models (WS3000Z, WS4000HD).

[Martin72]

Hi,

Maybe I´ve found a bug:
Decoding..
Thresholds of the signals are getting lost after restarting the scope.
Example you set the threshold on both channel used (UART, RX/TX) to 1.6V and data will be displayed, after restart no data because the thresholds are now 3.63V on one channel and 743mV on the other.

Martin