Siglent SDS2000X Plus

[james38]

Hello,

maybe I am wrong and I have missunderstood CAN-Trigger and decode or its a real bug.

When I change to trigger setup choose "serial" then protocol "CAN"
I get only one source presented under  "Signal".

As far as I know it must be 2 channels one for CAN-H and one for CAN-L isn't it?

The documentation in 16.5.1 CAN Signal Setting speak about "connect CAN-H and CAN-L and then set the mapping realtion between the two channels" too.

But how do I make this?
I thought is like i2c where are two sources present but in this case its not. By the way its the same on CAN-FD.

Firmware is the latest 1.3.7R5

Any hints ?

Regards Chris

[0xdeadbeef]

CAN is differential, so there is no different information on Can-Lo and CAN-Hi.

[james38]

CAN is differential, so there is no different information on Can-Lo and CAN-Hi.

Yes you are right.
I have read some documents about CAN in the meantime and it is as you said.
The information is on both the same only one is inverted.

Regards chris

[tautech]

Thanks. Perhaps these are bugs. I will report them in the specialized bugs thread, although I’m not sure if anyone from Siglent reads those posts or actually cares.

Oh, boy! This scope gives me a lot of headache! In addition to the previous questions posted here, which are still not clear to me:

• https://www.eevblog.com/forum/testgear/siglent-sds2000x-plus-coming/msg3551527/#msg3551527
• https://www.eevblog.com/forum/testgear/siglent-sds2000x-plus-coming/msg3551491/#msg3551491

what am I doing wrong this time?

I am trying to set up the user-adjustable rise-time and fall-time measurements. It works okay with percentage values. But I cannot make them work with absolute values for C1, C3, etc.: that is, for any values that I select for Horizontal parameters I get an "Invalid threshold" error message. But they seem to be working perfectly okay for the Math channels, e.g F1 (which is the sum of C1+C3). See screenshots attached.

I even calculated the absolute values to match the percentage values, and the absolute measurement setting still does not work for the C channels. What am I doing wrong here? 

Thanks a lot!

I am getting the same errors

Just browsed through the release notes of a beta version of the next firmware.
Most if not all of what has been discussed in the last few months seems to have been addressed. 

[Martin72]

Well, I think it´s time to "clean up" the bug thread, when the new firmware comes up.
I currently have vacation for 3 weeks, I´ll start with it at the forthcomung weekend.

[tautech]

Well, I think it´s time to "clean up" the bug thread, when the new firmware comes up.
I currently have vacation for 3 weeks, I´ll start with it at the forthcomung weekend.

They might have a tweak or 2 to do before public release as some of us have already provided feedback on some simple things proposed in the release notes however this is only for new scopes outta the factory whereas those that already know and use these scopes and have already made their preferred settings it should not affect them.

Whether or not we get listened to is another matter.

[Martin72]

Hi Rob,

I´ve meant it in general, what we´ve noticed so far in this thread, what was solved from siglent, what´s still to do and so on...

[Markus2801A]

Just browsed through the release notes of a beta version of the next firmware.
Most if not all of what has been discussed in the last few months seems to have been addressed. 

Where can I find this information?
Would be interesting to read what's coming up next :-)

[2N3055]

Just browsed through the release notes of a beta version of the next firmware.
Most if not all of what has been discussed in the last few months seems to have been addressed. 

Where can I find this information?
Would be interesting to read what's coming up next :-)

You can't... Tautech has some info from beta test proces..  He already said all he can.. 

What can I say, he's a tease....

Unfortunately, you'll need to wait and see...

[tautech]

Just browsed through the release notes of a beta version of the next firmware.
Most if not all of what has been discussed in the last few months seems to have been addressed. 

Where can I find this information?
Would be interesting to read what's coming up next :-)

You can't... Tautech has some info from beta test proces..  He already said all he can.. 

What can I say, he's a tease....

More teasing.... 
~35 changes coming plus a few further requests added since the beta FW was put in front of beta testers.

I can say it will be well worth the wait and not just for the fixes but also the new features added.

[Martin72]

Feel like a child can´t wait for christmas 

[Michael YYZ]

Looking forward to it. It's been a long wait... almost nine months. Fingers crossed! 

More teasing.... 
~35 changes coming plus a few further requests added since the beta FW was put in front of beta testers.

I can say it will be well worth the wait and not just for the fixes but also the new features added.

[tautech]

New Siglent option bundle promotion:
For all sales areas except NA unfortunately. 
Expires Sept 30 2021

With new purchases of SDS2000X Plus DSO's:
MSO SPL2016 HW with license and 50 MHz AWG/FG license for just $ 219 !

https://int.siglent.com/info/detail-49.html

[AaronLee]

New Siglent option bundle promotion:
For all sales areas except NA unfortunately. 
Expires Sept 30 2021

With new purchases of SDS2000X Plus DSO's:
MSO SPL2016 HW with license and 50 MHz AWG/FG license for just $ 219 !

https://int.siglent.com/info/detail-49.html

On the page for that link it says, "This promotion is only applicable to the European and AAAS region". What is AAAS region? Does the new purchase need to be made within the promotion period? I bought mine last month, would that qualify?

[rf-loop]

New Siglent option bundle promotion:
For all sales areas except NA unfortunately. 
Expires Sept 30 2021

With new purchases of SDS2000X Plus DSO's:
MSO SPL2016 HW with license and 50 MHz AWG/FG license for just $ 219 !

https://int.siglent.com/info/detail-49.html

On the page for that link it says, "This promotion is only applicable to the European and AAAS region". What is AAAS region? Does the new purchase need to be made within the promotion period? I bought mine last month, would that qualify?

It is well and detailed told in Siglent web side. https://www.siglenteu.com/news-article/summer-time-special-bundle-save-up-to-e496-with-a-new-sds2000x-plus-oscilloscope-and-option-bundle/

There is said example these

For a limited time, all new SDS2000X Plus purchases can get an option bundle for only €199. This bundle includes the SPL2016 and MSO and function generator activation licenses.

1. The SDS2000X Plus series oscilloscopes must be purchased from an authorized SIGLENT distributor.
.
.
.
5. All Offers are valid from August 2nd , 2021 to September 30th, 2021.

If purchased before 2.8.21 it is NOT new purchase inside 2.8. - 30.9.2021.

Old time I remember I purchase very expensive prosumer grade video camera (somewhere late -80s. Price was more than my quite good  salary at this time in two month. Just after some days there come big offer... not more than around 50%...  I remember my feel... life is... )

[blurpy]

I don't have this scope, but I'm curious of a couple of things for audio use.

1. There was a post a while ago asking about getting THD calculated when using the FFT. Any news about that?

2. Would be nice to be able to display watts, and perhaps the formula editor could be the way to go. I can't see any way of using measurements in the editor however. Is it possible to enter something like this? RMS(C1) * RMS(C1) / 8
Ideally it would be a custom "measurement" since it doesn't need a trace, but I can't see a way of doing that.

[hpw]

I´ve meant it in general, what we´ve noticed so far in this thread, what was solved from siglent, what´s still to do and so on...

Since today I have may a new one using current FW... (did not search on this lengthy thread)

1. running on 8 bit, vector display mode, on CH1 a digital square wave (0.3 low to 3V high) as 10MHz with 0.5ns rise/falling time
2. trigger about the half of the wave, show with cursor some 20% to 80% rise time as 0.5ns
3. add also color mode
4. all looks fine so far showing about 2 waves, with some small overshoots

than as soon I

5. enable Ch2, with or without 50E input, as nothing to display just enabled

6. On Ch1, the edges and overshoots gets modulated as like 50Hz, changed square from 10MHz to 49Mhz with same behavior

7. Change than from vector to pixel mode

8.  all looks than fine .... No any more edge modulations visible 

is this known?

IMHO it would be nice to have a thread moderated with current  so easier to track as a bug tracking system 

[Martin72]

I think, this will fitting better in the bug/missing features thread...

[2N3055]

I´ve meant it in general, what we´ve noticed so far in this thread, what was solved from siglent, what´s still to do and so on...

Since today I have may a new one using current FW... (did not search on this lengthy thread)

1. running on 8 bit, vector display mode, on CH1 a digital square wave (0.3 low to 3V high) as 10MHz with 0.5ns rise/falling time
2. trigger about the half of the wave, show with cursor some 20% to 80% rise time as 0.5ns
3. add also color mode
4. all looks fine so far showing about 2 waves, with some small overshoots

than as soon I

5. enable Ch2, with or without 50E input, as nothing to display just enabled

6. On Ch1, the edges and overshoots gets modulated as like 50Hz, changed square from 10MHz to 49Mhz with same behavior

7. Change than from vector to pixel mode

8.  all looks than fine .... No any more edge modulations visible 

is this known?

IMHO it would be nice to have a thread moderated with current  so easier to track as a bug tracking system 

How about if you enable CH1 and CH3 ?

[bdunham7]

is this known?

It's entirely expected if you figure out the actual bandwidth of the signal you are looking at vs. the sample rate in the two configurations (CH1 only vs CH1 + CH2).  Also, in vector mode the scope does a sinc interpolation of each frame and overlays the resulting lines from each frame, whereas in dot mode it simply overlays the dots.  If the sample clock was exactly matched to the input frequency at some fixed ratio, this wouldn't make much difference, but since it isn't, the samples all line up differently with the edge of the waveform each cycle, a sort of faux ETS.  That's good for dots, bad for vectors if you are getting close to the Nyquist limit.

I'm assuming you have this hacked to 500MHz.  What is generating the input signal?

[rf-loop]

I´ve meant it in general, what we´ve noticed so far in this thread, what was solved from siglent, what´s still to do and so on...

Since today I have may a new one using current FW... (did not search on this lengthy thread)

1. running on 8 bit, vector display mode, on CH1 a digital square wave (0.3 low to 3V high) as 10MHz with 0.5ns rise/falling time
2. trigger about the half of the wave, show with cursor some 20% to 80% rise time as 0.5ns
3. add also color mode
4. all looks fine so far showing about 2 waves, with some small overshoots

than as soon I

5. enable Ch2, with or without 50E input, as nothing to display just enabled

6. On Ch1, the edges and overshoots gets modulated as like 50Hz, changed square from 10MHz to 49Mhz with same behavior

7. Change than from vector to pixel mode

8.  all looks than fine .... No any more edge modulations visible 

is this known?

IMHO it would be nice to have a thread moderated with current  so easier to track as a bug tracking system 

Btw, fast edges corners wobbling is not modulation... it is one form of aliasing and also possible "gibbs ears" (Gibbs phdenomenon) due to Sinc interpolation when not enough samples.




Long time ago I have somehow tried tell about  Sequential Acquisition Random Interleaving (SARI) just my name for it for make clear it is not same as LeCroy RIS aka Random Interleaved Sampling mode, but somehow its small cousin.
But unfortunately it is only by my native Finnish language..   here (near end of page).


The feature can be used in many situations as long as user know its features and limits in the particular oscilloscope user are using, in this case Siglent. But with it is also very easy to drop to trap. (one critical parameter is trigger engine used data stream and its sample interval what is not always same as ADC current displayed samplerate. )

Here signal is 45MHz square wave... and samplerate is 50MSa/s  selected just for demonstration. Square wave freq 45MHz and sampled 50MSa/s. Where 3rd harmonic is 5.4*fNyquist

Of course depending signal ans scope and settings it may look much more nice and also without persistence, when wfm/s is enough.
btw, carefully look samplerate and displayed signal frequency.

One acquisition have only small amount of dots...  display frame have many acquistions overlaid (as many acquistions as it have done in last TFT cycle). One single acquisition dots are marked red.



Also here is forum is some old treads about these things with some examples if I remember right.

[gf]

Does that still work at the maximum sample rate (in order to get superresolution beyond the maximum sample rate), or is this functionality limited to lower sample rates?

[ If the acquisition sample rate is lower, and the ADC still runs at full speed, then the signal is oversampled anway in the first place, and RIS-like downsampling to the acquisition sample rate can be emulataed digitally in the FPGA w/o need for a TDC or varying ADC clock phase. ]

[hpw]

How about if you enable CH1 and CH3 ?

Yeah    ...

gear needs replaced by professional stuff as it goes with SSA 200Hz Span & 1Hz BW and synthesizer jitter (also wobbling)

[2N3055]

How about if you enable CH1 and CH3 ?

Yeah    ...

gear needs replaced by professional stuff as it goes with SSA 200Hz Span & 1Hz BW and synthesizer jitter (also wobbling)

??

[hpw]

SSA 200Hz Span & 1Hz BW and synthesizer jitter (also wobbling)

??

See pictures....