New Siglent SDS1202X-E oscilloscope based on Xilinx Zynq-7000 SoC architecture

[pascal_sweden]

The Chinese press release dates back from January:
https://mp.weixin.qq.com/s?__biz=MzA3NDMwMzY3Mw==&mid=2650216528&idx=1&sn=b009e094f3442e64f9827c1204e68739

The oscilloscope is listed on the Chinese site from Siglent:
http://www.siglent.com/oscilloscope/SDS1000X-E%20Series

First tab: Technical summary
Second tab: User guide and data sheet
Third tab: Options
Fourth tab: Pricing in China for this model and other models

You can use Google Translate to translate the article about the Zynq-7000 SoC architecture.
However Google Translate seems to discard the pictures.

[EEVblog]

There will not be a 70MHz, or 100MHz (the one I have), only a 200MHz version.
http://www.siglent.com/prodcut-db.aspx?id=1529&tid=1&T=2

And the 400k wfs update rate is marketing wank. That's in segmented mode.

And the Chinese Yuan pricing seems way off to what I am told, way too high.

[pascal_sweden]

There also seems to be an SDS-1000X-C series.

What does the "C" stand for? China?

[tautech]

There will not be a 70MHz, or 100MHz (the one I have), only a 200MHz version.
http://www.siglent.com/prodcut-db.aspx?id=1529&tid=1&T=2
And the 400k wfs update rate is marketing wank. That's in segmented mode.

You must have missed this:
Waveform capture rate of 100,000 frames / sec (normal mode); 400,000 frames per second (Sequence mode)
from this page:
http://www.siglent.com/oscilloscope/SDS1000X-E%20Series

There also seems to be an SDS-1000X-C series.

What does the "C" stand for? China?

Yep.

[JPortici]

in the press released from xilinx cited in the other topic they talked about full memory decoding. does it mean it will decode on the full 14 MSps? (instead of only acquiring 1.4 MSps with decode on as it does now)

[pascal_sweden]

Good point!

And I also wonder if it can be called hardware protocol decoding now.

We all look forward to Dave's upcoming review!

[EEVblog]

There will not be a 70MHz, or 100MHz (the one I have), only a 200MHz version.
http://www.siglent.com/prodcut-db.aspx?id=1529&tid=1&T=2
And the 400k wfs update rate is marketing wank. That's in segmented mode.

You must have missed this:
Waveform capture rate of 100,000 frames / sec (normal mode); 400,000 frames per second (Sequence mode)
from this page:
http://www.siglent.com/oscilloscope/SDS1000X-E%20Series

That's what I said, segmented mode is sequence mode. They are pushing that number instead of the normal number.

[EEVblog]

in the press released from xilinx cited in the other topic they talked about full memory decoding. does it mean it will decode on the full 14 MSps? (instead of only acquiring 1.4 MSps with decode on as it does now)

Yes, that's the claim. Have not tried it tough.

[rf-loop]

in the press released from xilinx cited in the other topic they talked about full memory decoding. does it mean it will decode on the full 14 MSps? (instead of only acquiring 1.4 MSps with decode on as it does now)

Yes. Just same way as X/X+ but not rejected max 1.4M sample (because more brute force). And as we remember what ever is acquisition memory length it is equal with display width. (zoom for details).

[tautech]

There will not be a 70MHz, or 100MHz (the one I have), only a 200MHz version.
http://www.siglent.com/prodcut-db.aspx?id=1529&tid=1&T=2
And the 400k wfs update rate is marketing wank. That's in segmented mode.

You must have missed this:
Waveform capture rate of 100,000 frames / sec (normal mode); 400,000 frames per second (Sequence mode)
from this page:
http://www.siglent.com/oscilloscope/SDS1000X-E%20Series

That's what I said, segmented mode is sequence mode. They are pushing that number instead of the normal number.

Fair enough....but on the Chinese website scope overview page only. Migrate to the page I linked and both normal and sequence wfm/s rates are listed just as I'd translated and pasted them in.
But what will matter more in the near future is how it's listed on the English Siglent websites, I strongly suspect it will fall into line with what's presently on the scope overview page, that being normal then sequence mode.
http://siglentamerica.com/pd.aspx?tid=1&T=1

[rf-loop]

There will not be a 70MHz, or 100MHz (the one I have), only a 200MHz version.
http://www.siglent.com/prodcut-db.aspx?id=1529&tid=1&T=2
And the 400k wfs update rate is marketing wank. That's in segmented mode.

You must have missed this:
Waveform capture rate of 100,000 frames / sec (normal mode); 400,000 frames per second (Sequence mode)
from this page:
http://www.siglent.com/oscilloscope/SDS1000X-E%20Series

That's what I said, segmented mode is sequence mode. They are pushing that number instead of the normal number.

Pushing and pushing...

In chinese side:

First :
Inside Product Overview text one sentence.

"waveform capture rates up to 400,000 frames per second (Sequence mode)"

And just after some sentences there read (without even scrolling page down, in same view, if just tiny eyes movement, under scope front image) very clearly:

"
Key Features:

* Bandwidth: 70MHz, 100MHz, 200MHz

* Real-time sampling rate of up to 1GSa / s

* New generation of SPO technology

    * Waveform capture rate of 100,000 frames per second (normal mode); 400,000 frames per second (Sequence mode)

    * Supports 256 levels of waveform brightness and color temperature display

    * Storage depth of 14Mpts

* Digital triggering system
"

What is pushed, what is wrong?

Perhaps this is too long and in western countries all need today be as instant messaging style. Sad.
But yes, some peoples can not be focused over 5 seconds. Overall this is going more and more bad when all is going to instant messaging.

[tautech]

I'm told there's a fresh off the production line 200 MHz unit on the way to Dave right now. 

[ebastler]

Perhaps this is too long and in western countries all need today be as instant messaging style. Sad.

Is that you, Donald??
 

[GeorgeOfTheJungle]

I'm told there's a fresh off the production line 200 MHz unit on the way to Dave right now. 

@Dave: please check the UART decoder thoroughly, at a fast baud rate (115200 or moar) and at 100ms/div or so (because a rigol 1000z can do that properly).

[thanasisk]

Any approx release date known yet?

[rf-loop]

Any approx release date known yet?

Yes.
(But this info can not yet release.)

[mikeselectricstuff]

I'm told there's a fresh off the production line 200 MHz unit on the way to Dave right now. 

@Dave: please check the UART decoder thoroughly, at a fast baud rate (115200 or moar) and at 100ms/div or so (because a rigol 1000z can do that properly).

115K2 is hardly fast. I'd expect any decent serial decode to go to at least 4Mbaud, ideally more

[nctnico]

I've seen scopes which go to 10Mbaud but on a regular UART this would require a clock speed of 160MHz. Maybe you could get away with 80MHz or 60MHz  on a UART with less clocks per bit but either way it is going beyond what you'd be 'normally' dealing with.

[GeorgeOfTheJungle]

115K2 is hardly fast. I'd expect any decent serial decode to go to at least 4Mbaud, ideally more

Of course the moar the better, but at low sweep speeds (100 ms/div) that's not possible, you'd need ~76MB mem depth/channel to decode @ 4Mbaud

[mikeselectricstuff]

I've seen scopes which go to 10Mbaud but on a regular UART this would require a clock speed of 160MHz. Maybe you could get away with 80MHz or 60MHz  on a UART with less clocks per bit but either way it is going beyond what you'd be 'normally' dealing with.

You don't need 16 clocks per bit. PIC32s can do 12.5Mbaud at 50MHz

[nctnico]

I've seen scopes which go to 10Mbaud but on a regular UART this would require a clock speed of 160MHz. Maybe you could get away with 80MHz or 60MHz  on a UART with less clocks per bit but either way it is going beyond what you'd be 'normally' dealing with.

You don't need 16 clocks per bit. PIC32s can do 12.5Mbaud at 50MHz

Having only 4 clocks per bit will severely hamper the (digital) filtering and timing recovery a UART usually does. Why do you think a UART is typically designed to need 16 clocks per bit?

[mikeselectricstuff]

I've seen scopes which go to 10Mbaud but on a regular UART this would require a clock speed of 160MHz. Maybe you could get away with 80MHz or 60MHz  on a UART with less clocks per bit but either way it is going beyond what you'd be 'normally' dealing with.

You don't need 16 clocks per bit. PIC32s can do 12.5Mbaud at 50MHz

Having only 4 clocks per bit will severely hamper the (digital) filtering and timing recovery a UART usually does. Why do you think a UART is typically designed to need 16 clocks per bit?

To deal with noisy data, which will only happen if your hardware isn't up to the job.
General-purpose  UARTs are designed for use over a wide range of conditions. If you have a clean link ( e.g. RS485), you only need 3x clock to recover 100% good data from a clean stream.
Most UARTs have an option to do 8x to get higher baudrates, some have 4x.

And if your UART is in an FPGA, 160MHz clock is trivial, though once you get over 10MBaud, jitter becomes more of an issue, so self-clocking codes like Manchester tend to be used.

[JPortici]

115K2 is hardly fast. I'd expect any decent serial decode to go to at least 4Mbaud, ideally more

Of course the moar the better, but at low sweep speeds (100 ms/div) that's not possible, you'd need ~76MB mem depth/channel to decode @ 4Mbaud

there would be 40k characters per horizontal division. a scope is probably not the correct tool at this point

[tautech]

115K2 is hardly fast. I'd expect any decent serial decode to go to at least 4Mbaud, ideally more

Of course the moar the better, but at low sweep speeds (100 ms/div) that's not possible, you'd need ~76MB mem depth/channel to decode @ 4Mbaud

there would be 40k characters per horizontal division. a scope is probably not the correct tool at this point

You do know the SDS1kX series decode while in Zoom mode, of course you do you just forgot. 

[JPortici]

i also do know that the 1000x uart decode is limited to about 300 kbaud (too slow)
well, the current manual says 115200 but i may have read 300k somewhere else.

still, missed the point completely (even if we wanted to compare the siglent)