Desktop DSO for hardware and firmware development of MCU systems

[Wilson__]

Please recommend for hardware/firmware MCU development

4 channels, 600 to 1400 USD

Prefer 10 inches screen

Firmware stable, minor bugs

1GSa/s 50MHz, 8 to 12 bits or higher

Decode UART, SPI, I2C

UL/IEC safety EMC approval

Optional SA channels and signal generator 

SIGLENT SDS1000X HD, Rigol or similar

[KungFuJosh]

Since you're at the price point, you should compare the SDS1000X HD to the SDS2000X Plus and see whether you prefer the 12 bits, or the other more powerful features on the Plus.

The SDS2000X Plus is the more mature scope of the two, so you're much less likely to experience any bugs. Siglent is generally good about fixing that stuff anyway tho.

[tautech]

Please recommend for hardware/firmware MCU development

I'm gunna back Josh and add, if you are to need theLA/MSO option, SPL2016 that only fits 2k and up series scopes is a professional product unlike SLA1016 that fits SDS1000X HD models.

IMO, this alone at your budget would push me to SDS2104X Plus......

[Wilson__]

Many thanks.  I have been using old tools for decades.  They served the work purpose.   

Now, wanting a new digital scope to help firmware debug and verify SPI/I2C analogue signal quality at 10MHz square wave.   These 4-ch scope decodes SPI full duplex traffic by hooking on MISO, MOSI, CLOCK ad nChipSelect, right?

I can pay the high price point if necessary.  If the low side can do those specific task, it is ok too. 

How about SDS1104X-E (Amazon Choice, first available Nov 2017) and SDS804X HD (first available April 2024)?   Would year 2017 safer bet that 6 months (teething) baby?  This forum has 40 pages on software issue on another brand 8xx/9xx.  Need to avoid that. 

[tautech]

Many thanks. I have been using old tools for decades.  They served the work purpose. 

They did but latest generation have a far bigger toolset.
While we can set up for stable triggering the trigger suite in modern scopes take this to a new level where we can configure to find Runt pulses or outta spec pulses to name just 2.

Now, wanting a new digital scope to help firmware debug and verify SPI/I2C analogue signal quality at 10MHz square wave.   These 4-ch scope decodes SPI full duplex traffic by hooking on MISO, MOSI, CLOCK and ChipSelect, right?

100%

How about SDS1104X-E (Amazon Choice, first available Nov 2017) and SDS804X HD (first available April 2024)?   Would year 2017 safer bet that 6 months (teething) baby?  This forum has 40 pages on software issue on another brand 8xx/9xx.  Need to avoid that.

SDS1104X-E is a very capable low cost DSO too however if also uses the SLA1016 MSO/LA probe set too as does SDS800X HD however these both are 7" display which for occasional use might be fine but for a substantial project 10" displays will be better.

Some little history if I may of the latest models, the GUI has been developed over some years along with the touch interface and mouse support starting IIRC in SDS5000X models when we only had the more basic features of the 1000X, 2000X and X-E models.
Whereas today the same GUI is used from 800 X HD all the way to the $ 7000A models albeit the top of the line models offer more features and much higher BW.
This allows us to sample the GUI with a $340 DSO before investing further......

[nctnico]

Problem is that both Rigol and Siglent only decode part of the signal which is on screen. With several digital channels enabled and needing zoom to force more width, you'll run out of screen space quickly. Another problem is that the packet numbering in a list display will change when more or less packets get 'in sight'.

An R&S RTB2004 is a better choice especially if your use is commercial. The RTB2004 has far less compromises (for example: decoded data can be rotated 90 degrees making far more information fit on screen) and is ideal for doing firmware / MCU debugging and it has been on the market long enough to be available on the used market. But it likely is not going to fit your budget. I have the RTM3004 (one step up from the RTB2004) which runs mostly the same software as the RTB2004 and this scope is just perfect for my professional use (which is also developing embedded firmware & hardware).

[tautech]

Problem is that both Rigol and Siglent only decode part of the signal which is on screen.

So, have 100 packets on the screen !

[coromonadalix]

better invest into a separate logic analyzer ...  you can get some powerful ones with high bandwidth

Kingst  LAxxxx
DsLogic 

Salae   too pricy

EDIT  just saw this

Maybe worth a look ?
https://www.eevblog.com/forum/testgear/ngscopeclient-ultimate-acquisition-software-protocol-decoder-debug-tool/

[guenthert]

Problem is that both Rigol and Siglent only decode part of the signal which is on screen.

So, have 100 packets on the screen !

Hmmh, I find an oscilloscope helpful to get an idea of signal quality.  When troubleshooting a RS485 connection however, I found myself hacking together a MCU plus RS485 receiver to monitor the communication.  Same with GPIB.  Is the built-in protocol decoder more than a gimmick (much like the built-in FFT)?

[NE666]

Rigol MSO5074 all the way, imho, which is why I own one. Built-in "half decent" sig gen and LA (although you need to purchase a cable/pod for the latter).

2GS/s on all four channels together (8GS/s on single channel), can be 'liberated' easily to 350MHz, so it can handle fast content on edges. Front-end is known to be noisy but it's of no real issue to digital signal applications for MCUs etc., only for low-level analogue applications.

On offer at present with Rigol and their main distributors (about 750USD in the UK at present, inc. taxes).  No need, again imho, to up your budget for the application you describe. Save the extra for a capable external LA with good trigger and decode options.

Rigol don't have the best reputation for not releasing buggy new products (certainly not with me) but this one has been out there for a number of years and had reached the 'stable' state.

[Fungus]

Now, wanting a new digital scope to help firmware debug and verify SPI/I2C analogue signal quality at 10MHz square wave.   These 4-ch scope decodes SPI full duplex traffic by hooking on MISO, MOSI, CLOCK ad nChipSelect, right?

Yes.

They also have features to (eg.) allow you to trigger on specific data values.

I can pay the high price point if necessary.  If the low side can do those specific task, it is ok too. 

For purely digital work you should put the Rigol MSO5074 on your shortlist, too. The base model can easily be unlocked to 350Mhz and it has a lot of memory, sample rate, etc.

12 bits simply isn't needed.

Problem is that both Rigol and Siglent only decode part of the signal which is on screen.

Simply not true for most of them these days.

(check individual models, but... generally not true)

[Performa01]

Neeed to correct some clueless comments.

Just to make clear: The zoom view on a Siglent SDS2000X Plus and up is big enough compared to the small fraction of the fairly big 10" screen used for the main view, which serves as a detailed overview. There's certainly enough space for the zoom view.

And no, the list view on a Siglent always shows all captured frames in the same order and the numbering doesen't change, regardless which part is zoomed.

Attached is an old example of an SPI decoding of 245 frames, zoomed in on the last part of the stream. Main and list view show all 245 frames while the zoom view alows close inspection of any details.

[KungFuJosh]

If you have the budget to go higher than the SDS2000X Plus, then compare it with the SDS2000X HD. Either one would be a great scope for your needs, and both are based on a 500MHz platform.

[Wilson__]

Many thanks.  Any comment on the below four models, 1xx to 300 USD?   

What sampling rate do I need for MCU SPI signals at 10 to 40MHz clock rate. 

Kingst says 200M samples per second for 40MHz signal.  5 data points on high low cycle.

DSLogic says 10 to 100 sampling clock over SPI signal rate.

Just scanned the doc, the ngscopeclient software look amazing and promising.

[nctnico]

Keep in mind that a logic analyser hides any problem in the analog domain while most problems occur in the analog domain. Many years ago I was involved in a project and the engineer at a customer had been struggling for 2 or 3 weeks to get a simple RS485 bus working on their part of the project. So I went over and disconnected the digital probes and connected the analog probes to the RS485 bus. The problem became clear within 5 minutes after that; the timing to switch between send & receive was all wrong.

[Wilson__]

One poster kindly pointed to the ngscopeclient software.  Scanned doc, amazing and promising.  One driver was developed in Siglent SDS2000X Plus.

Is Siglent SDS2000X Plus firmware enough aged, stable and no-issue for normal use?  Amazon says was released July 2021

[NE666]

When it comes to a separate LA you might want to take a look at Digilent's "Digital Discovery".

It's at the upper end of the price range of the other LAs you've listed but it has a lot of additional functionality too (including SPI and I2C slave/host capabilities). The spec sheet says that it supports up to 800MS/s on 8 channels, supports up to 24 channels in total and is good for 100Mhz input signals. Importantly, their (free) WaveForms software looks pretty good, as does their support.

I noted earlier today that the ngscopeclient project claims to support the Analogue Discovery devices already. Given that they use the same WaveForms software as their digital kin, perhaps the latter is also supported by ngscopeclient, or that support might easily be added relatively easily?

[2N3055]

Digital Discovery is good but inputs are not protected and have very low input range, logic only.
It is more specialized thing. I use it for pattern generation, for instance.

Just get SDS2104X Plus if you can afford it.
You don't need GLScope client.
SDS2000X+ decodes more protocols than you need.
It is a fully featured scope that simply works, it is self contained and is a steal for the money.

You can get one of those cheap LA for just decoding stuff on PC, for when you are decoding long interchanges of messages when debugging software part.

[Wilson__]

Effective ADC bit (ENOB) is about 1.5 to 2 less than the specification?  8 bit ADC has 6 bit real accuracy and resolve 64 steps of digital SPI signal.  Would that be enough for task below?

How much sampling rate do I need to see the signal, without risk of missing some short time glitch?  SDS2104 is 1GSa/s when all 4 ch activated, right?  For 20MHz SPI clock, 50 dots per cycle. Enough?

On speed alone, Rigol MSO5074 is exceptional high 8GSa/s for 700 UK pounds.

I need the tool to do proper design verification after MCU software function ok. 

Look at analogue waveform of signal sent between MCU and external chip over SPI.  Verify data sheet setup time, hold time.  Also, signal integity.  Smooth rise fall of signal.  No ringing, overshoot, undershoot. 

Catch any rare occurrence signal that can fail the system once in, says, every 100 hours running.  Says, "poor" power supply voltage dropped when multiple loads are switched at same time due to rare situations/software event.

[KungFuJosh]

Don't consider the Righoul MSO5000 without reading this thread first: https://www.eevblog.com/forum/testgear/review-rigol-mso5000-tests-bugs-questions/

[Fungus]

Effective ADC bit (ENOB) is about 1.5 to 2 less than the specification?  8 bit ADC has 6 bit real accuracy and resolve 64 steps of digital SPI signal.  Would that be enough for task below?

Yes.

You're mostly interested in timing between channels and signal rise times, not precise voltage levels.

How much sampling rate do I need to see the signal, without risk of missing some short time glitch?  SDS2104 is 1GSa/s when all 4 ch activated, right?  For 20MHz SPI clock, 50 dots per cycle. Enough?

You're not interested in a "cycle", you're interested in looking at the rising/falling edges.

There's not really a "too much" for that.

[Fungus]

No ringing, overshoot, undershoot. 

Those measurements will mostly be down to your probing technique, not the 'scope itself.

You should be OK with ordinary probes at 20Mhz clock frequencies, even if you have to resort to the little springs that come in the bag.

You could add little spring-probing points to your PCBs to make life easier, or even places to solder in an SMA connector.

[2N3055]

Effective ADC bit (ENOB) is about 1.5 to 2 less than the specification?  8 bit ADC has 6 bit real accuracy and resolve 64 steps of digital SPI signal.  Would that be enough for task below?

How much sampling rate do I need to see the signal, without risk of missing some short time glitch?  SDS2104 is 1GSa/s when all 4 ch activated, right?  For 20MHz SPI clock, 50 dots per cycle. Enough?

On speed alone, Rigol MSO5074 is exceptional high 8GSa/s for 700 UK pounds.

I need the tool to do proper design verification after MCU software function ok. 

Look at analogue waveform of signal sent between MCU and external chip over SPI.  Verify data sheet setup time, hold time.  Also, signal integity.  Smooth rise fall of signal.  No ringing, overshoot, undershoot. 

Catch any rare occurrence signal that can fail the system once in, says, every 100 hours running.  Says, "poor" power supply voltage dropped when multiple loads are switched at same time due to rare situations/software event.

Don't get into sampling rate rabbit hole.For digital signals, your scope is limited with front end slew rate not sampling frequency. And since SDS200XPlus is 500MHz/800ps design, and MSO5000 is 350MHz/1ns it is obvious which one will have slight advantage here.
But that is least important.
In latest firmware for SDS200XPlus  Siglent introduced I2C and SPI verification/test option that will automatically test compliance (when properly parametrized) and make an comprehensive PASS/ FAIL report.
This is something that so far was only available on high end scopes and option alone was 2-3x times more expensive than complete SDS2000X+ scope.

[tggzzz]

Now, wanting a new digital scope to help firmware debug and verify SPI/I2C analogue signal quality at 10MHz square wave.   These 4-ch scope decodes SPI full duplex traffic by hooking on MISO, MOSI, CLOCK ad nChipSelect, right?

General principle:

• first look at analogue waveforms to ensure the waveforms will be correctly interpreted by receivers as digital signals. A scope is a suitable analogue domain tool
• once that is assured, flip to the digital domain, and use digital domain tools such as logic and protocol analysers

There are many simple cheap effective digital domain tools, e.g. Salae clones and BusPirate5. The better ones don't merely capture and post-process, but filter out the boring crap then capture and post process.

What sampling rate do I need for MCU SPI signals at 10 to 40MHz clock rate. 

In the digital domain thinking in terms of frequency frequently (ho ho) leads to unhelpful and outright false reasoning. (Classic example is"scope bandwidth needs to be 5* clock frequency". That's rubbish; consider a 1Hz digital signal. The required bandwidth depends solely on transition time)

It is much better, simpler and clearer to think in terms of time and bit/baud rate.

In the digital domain with digital signals either:

• connect the UUT's clock to a flip-flop's clock, and use that to capture the UUT's data in the flip flop. That requires one sample per clock
• connect the UUT's clock and UUT's data to flip flop inputs, asynchronously sample the pair, and interpret the data stream to find an edge in the clock signal. The clock input must be inferred while the data input is stable, and that defines the sampling rate. To pick extreme figures, if you have a 100ns bit period but the data is only valid for 10ns within that 100ns, then you have to be able to locate the clock within the 10ns that the data is valid. You will probably want to sample every 2 or 3ns to ensure the edge is located sufficiently accurately.

[tautech]

In latest firmware for SDS200XPlus  Siglent introduced I2C and SPI verification/test option that will automatically test compliance (when properly parametrized) and make an comprehensive PASS/ FAIL report.
This is something that so far was only available on high end scopes and option alone was 2-3x times more expensive than complete SDS2000X+ scope.

And while you typed I grabbed some screenshots for Wilson_ .....

[tautech]

And now setup with a LAN connection to PC at the bench a webserver capture and remote screenshot of how the Serial Test parameter values are adjusted.

[tautech]

Effective ADC bit (ENOB) is about 1.5 to 2 less than the specification?  8 bit ADC has 6 bit real accuracy and resolve 64 steps of digital SPI signal.  Would that be enough for task below?

How much sampling rate do I need to see the signal, without risk of missing some short time glitch?  SDS2104 is 1GSa/s when all 4 ch activated, right?  For 20MHz SPI clock, 50 dots per cycle. Enough?

On speed alone, Rigol MSO5074 is exceptional high 8GSa/s for 700 UK pounds.

Divided down by the # of channels in use, as is the memory depth.
I don't remember by how much but a search should reveal the facts.

OTOH SDS2000X Plus uses 2 ADC's, each 2 GSa/s and with 200 Mpts memory each, therefore 1 GSa/s and 100 Mpts memory depth with all channels active.

[Wilson__]

oh!  14 pages long.

[Wilson__]

It will be 100 dots per cycle in 2 ch mode but need alternate trigger than directly decode the 4 actual signal wires of SPI.

[Wilson__]

Many thanks for the info.  That is very nice and neat. 

World moved on.  Would take lot of human  to move cursors (since time of CRT analogue scope with digital marker/cursor) and copy the timing number. now is auto

[tautech]

Further decode and zoom examples.....
All I have with SPI signal is STB-3

[Wilson__]

If you have the budget to go higher than the SDS2000X Plus, then compare it with the SDS2000X HD. Either one would be a great scope for your needs

Many thanks for info.  My use is design verification.  Use DSO to inspect signal lines to confirm that there is no abnormal glitch nor invalid signal. Are below correct?

1. The MCU and external chips works at 10MHz SPI clock.  Likely these silicon are tens of nm node and will not response to glitch that is many times narrower than the normal 10MHz wanted-signal.

2. SDS2000X Plus is 1 or 2GSa/s in 4 or 2 channel mode.  So, I got 100 to 200 dots for the 10MHz signal.  Spec. also says 1ns peak detection.  Presumably, refers to best case signal at full swing voltage (3.3 volts).  Presumably, the scope will detect lower-voltage glitch at, says, 1 volt, of a few ns long. 

3. SDS2000X Plus will do the job, right?  If the scope does not see any glitch, the glitch energy, (voltage multipy time) should be too weak to cause the chip to response, right?

[2N3055]

If you have the budget to go higher than the SDS2000X Plus, then compare it with the SDS2000X HD. Either one would be a great scope for your needs

Many thanks for info.  My use is design verification.  Use DSO to inspect signal lines to confirm that there is no abnormal glitch nor invalid signal. Are below correct?

1. The MCU and external chips works at 10MHz SPI clock.  Likely these silicon are tens of nm node and will not response to glitch that is many times narrower than the normal 10MHz wanted-signal.

2. SDS2000X Plus is 1 or 2GSa/s in 4 or 2 channel mode.  So, I got 100 to 200 dots for the 10MHz signal.  Spec. also says 1ns peak detection.  Presumably, refers to best case signal at full swing voltage (3.3 volts).  Presumably, the scope will detect lower-voltage glitch at, says, 1 volt, of a few ns long. 

3. SDS2000X Plus will do the job, right?  If the scope does not see any glitch, the glitch energy, (voltage multipy time) should be too weak to cause the chip to response, right?

You are doing too much of presumptions.

1ns Peak detection means it is in peak detect mode.
In which it will detect a 1ns pulse.

How wide pulse it will detect in normal sampling mode depends on rise/fall times of the pulse.
If pulse has sub ns edges, it will pretty much detect a 3ns pulse with full amplitude.
To cut the story short, SDS2000X+ ( with full BW) is going to be more than fast enough to look into SPI. 

But we are suddenly talk about low digit ns. To deal with that you need 1GHz + scope ...
And some good probing.

Even to achieve full BW of SDS2000X+ your biggest problem will be probing and will be most limiting factor.

[Wilson__]

To cut the story short, SDS2000X+ ( with full BW) is going to be more than fast enough to look into SPI.

Even to achieve full BW of SDS2000X+ your biggest problem will be probing and will be most limiting factor.

Sorry, coming from thru-hole age.  How to probe QFN chip SPI signals?  'Test version' PCB with test point?

Googled says, https://www.edn.com/oscilloscope-probe-accessories-its-the-little-things-that-matter/

[tggzzz]

1. The MCU and external chips works at 10MHz SPI clock.  Likely these silicon are tens of nm node and will not response to glitch that is many times narrower than the normal 10MHz wanted-signal.

Don't bet on it. Or rather it depends on "how many".

If it is important, measure it, taking account of PSU voltage, temperature, phase of the moon, chip manufacturer, IC datestamp etc.

In digital circuits the frequency is unimportant, but the timing is important. If you violate, say the t_hold, then it doesn't matter if the signal is 1MHz or 1Hz (and unlike t_setup it won't be ameliorated by reducing the clock frequency)

[nctnico]

To cut the story short, SDS2000X+ ( with full BW) is going to be more than fast enough to look into SPI.

Even to achieve full BW of SDS2000X+ your biggest problem will be probing and will be most limiting factor.

Sorry, coming from thru-hole age.  How to probe QFN chip SPI signals?  'Test version' PCB with test point?

Solder thin (enamel) wires to the best possible location. Typically you'll want to use series resistors on SPI interfaces to dampen reflections so these are good points. Otherwise you'll need to solder really thin (enamel) wires to QFN pads and bring them to a 2.54mm header or something like that. Not impossible to do but still a nuisance.

[2N3055]

To cut the story short, SDS2000X+ ( with full BW) is going to be more than fast enough to look into SPI.

Even to achieve full BW of SDS2000X+ your biggest problem will be probing and will be most limiting factor.

Sorry, coming from thru-hole age.  How to probe QFN chip SPI signals?  'Test version' PCB with test point?

Googled says, https://www.edn.com/oscilloscope-probe-accessories-its-the-little-things-that-matter/

One of the often forgotten things is "design for test". Provide test points for critical signals. Not only on prototype.
If you change layout from prototype to production, how do you know you didn't influence things?
You can solder in short extensions to probe tip (making sure you have good ground), use spring ground or similar.

Really high speed active probes are mostly solder in..

For some probing, you can use 10x LoZ probe together with 50Ω inputs..

Trick is to minimise capacity (to minimise circuit load) and inductance as seen by probe.. And to stay with high enough DC resistance to minimize DC load. Art of compromises.

Ideally you could use an active probe, but we if are talking about budget options, maybe something homemade or by one of the members here that occasionally spin some prototypes..

[tautech]

If you have the budget to go higher than the SDS2000X Plus, then compare it with the SDS2000X HD. Either one would be a great scope for your needs

Many thanks for info.  My use is design verification.  Use DSO to inspect signal lines to confirm that there is no abnormal glitch nor invalid signal. Are below correct?

1. The MCU and external chips works at 10MHz SPI clock.  Likely these silicon are tens of nm node and will not response to glitch that is many times narrower than the normal 10MHz wanted-signal.

2. SDS2000X Plus is 1 or 2GSa/s in 4 or 2 channel mode.  So, I got 100 to 200 dots for the 10MHz signal.  Spec. also says 1ns peak detection.  Presumably, refers to best case signal at full swing voltage (3.3 volts).  Presumably, the scope will detect lower-voltage glitch at, says, 1 volt, of a few ns long. 

3. SDS2000X Plus will do the job, right?  If the scope does not see any glitch, the glitch energy, (voltage multipy time) should be too weak to cause the chip to response, right?

The modern DSO is pretty powerful at finding stuff you might not even think is present.....it's all about using the features available to see that you might have a problem then applying the toolset to capture them.



This ^^^ screenshot is a good example where some Persistence shows it's present then we can narrow in and seen if it's a one off or repetitive.
In this post I did a similar exercise with the older SDS1104X-E which gives some idea of using a few of the scopes features:
https://www.eevblog.com/forum/testgear/siglent-sds1204x-e-released-for-domestic-markets-in-china/msg1370717/#msg1370717

[Wilson__]

If you have the budget to go higher than the SDS2000X Plus, then compare it with the SDS2000X HD. Either one would be a great scope for your needs

Many thanks for info.  My use is design verification.  Use DSO to inspect signal lines to confirm that there is no abnormal glitch nor invalid signal. Are below correct?

1. The MCU and external chips works at 10MHz SPI clock.  Likely these silicon are tens of nm node and will not response to glitch that is many times narrower than the normal 10MHz wanted-signal.

2. SDS2000X Plus is 1 or 2GSa/s in 4 or 2 channel mode.  So, I got 100 to 200 dots for the 10MHz signal.  Spec. also says 1ns peak detection.  Presumably, refers to best case signal at full swing voltage (3.3 volts).  Presumably, the scope will detect lower-voltage glitch at, says, 1 volt, of a few ns long. 

3. SDS2000X Plus will do the job, right?  If the scope does not see any glitch, the glitch energy, (voltage multipy time) should be too weak to cause the chip to response, right?

The modern DSO is pretty powerful at finding stuff you might not even think is present.....it's all about using the features available to see that you might have a problem then applying the toolset to capture them.



This ^^^ screenshot is a good example where some Persistence shows it's present then we can narrow in and seen if it's a one off or repetitive.
In this post I did a similar exercise with the older SDS1104X-E which gives some idea of using a few of the scopes features:
https://www.eevblog.com/forum/testgear/siglent-sds1204x-e-released-for-domestic-markets-in-china/msg1370717/#msg1370717

Comparing SDS1104X-E and SDS2104X-Plus.  Does the cheaper unit have same toos/function (trigger, search, measure) for the purpose of design verification, to hunt for abnormal signals in 10MHz SPI signal between MCU and external chips?

Is there more differences than what I found so far from scanning manual:

500MSa/s   vs   1000MSa/s in 4 channels mode (MISO, MOSI, Clock, nChipSelect), 500M is 50 samples per 10MHz signal pulse.  Enough to see abnormal glitch, runt, overshoot, undershoot???

7 Mpts/CH  vs  100Mpts, 7M captures 140,000 pulses at 50 samples per pulse. 

No histogram, still has StdDev to qualtify signal jitter.

7 inches and non-touch screen.   Needs a few more human seconds to use knobs to active a function, right?

[tautech]

If you have the budget to go higher than the SDS2000X Plus, then compare it with the SDS2000X HD. Either one would be a great scope for your needs

Many thanks for info.  My use is design verification.  Use DSO to inspect signal lines to confirm that there is no abnormal glitch nor invalid signal. Are below correct?

1. The MCU and external chips works at 10MHz SPI clock.  Likely these silicon are tens of nm node and will not response to glitch that is many times narrower than the normal 10MHz wanted-signal.

2. SDS2000X Plus is 1 or 2GSa/s in 4 or 2 channel mode.  So, I got 100 to 200 dots for the 10MHz signal.  Spec. also says 1ns peak detection.  Presumably, refers to best case signal at full swing voltage (3.3 volts).  Presumably, the scope will detect lower-voltage glitch at, says, 1 volt, of a few ns long. 

3. SDS2000X Plus will do the job, right?  If the scope does not see any glitch, the glitch energy, (voltage multipy time) should be too weak to cause the chip to response, right?

The modern DSO is pretty powerful at finding stuff you might not even think is present.....it's all about using the features available to see that you might have a problem then applying the toolset to capture them.



This ^^^ screenshot is a good example where some Persistence shows it's present then we can narrow in and seen if it's a one off or repetitive.
In this post I did a similar exercise with the older SDS1104X-E which gives some idea of using a few of the scopes features:
https://www.eevblog.com/forum/testgear/siglent-sds1204x-e-released-for-domestic-markets-in-china/msg1370717/#msg1370717

Comparing SDS1104X-E and SDS2104X-Plus.  Does the cheaper unit have same toos/function (trigger, search, measure) for the purpose of design verification, to hunt for abnormal signals in 10MHz SPI signal between MCU and external chips?

Is there more differences than what I found so far from scanning manual:

500MSa/s   vs   1000MSa/s in 4 channels mode (MISO, MOSI, Clock, nChipSelect), 500M is 50 samples per 10MHz signal pulse.  Enough to see abnormal glitch, runt, overshoot, undershoot???

7 Mpts/CH  vs  100Mpts, 7M captures 140,000 pulses at 50 samples per pulse. 

No histogram, still has StdDev to qualtify signal jitter.

7 inches and non-touch screen.   Needs a few more human seconds to use knobs to active a function, right?

TBH, today if wanting a lower cost solution and happy with a 7" display, SDS814X HD is where it's at.

[KungFuJosh]

SDS1104X-E and SDS2104X-Plus

My first scope was a Rigol piece of trash, that spawned my general hate for Rigol.

My second scope was the SDS1104X-E. It was a great scope, and generally met my needs at the time. But there is simply no comparison when jumping up to the SDS2104X Plus (my 3rd scope). The screen quality, general speed, additional features/triggers etc.

A very important difference for me is the far superior web console on the 2000 level scopes. I imagine you will likely be using the web console once your tests are setup. For that alone I wouldn't consider a lesser scope.

I sold my SDS2104X Plus because I had an opportunity to get an SDS2104X HD at a great price. I feel like the level between these two scopes is also a leap forward, but I wouldn't be sad at all if I was still using the SDS2104X+.

All that said, if budget is your biggest concern, get an SDS800X HD scope. If performance is your concern, start at the 2000 level, whether it's the Plus or HD, you'll be happy.

[Wilson__]

If you have the budget to go higher than the SDS2000X Plus, then compare it with the SDS2000X HD. Either one would be a great scope for your needs

Many thanks for info.  My use is design verification.  Use DSO to inspect signal lines to confirm that there is no abnormal glitch nor invalid signal. Are below correct?

1. The MCU and external chips works at 10MHz SPI clock.  Likely these silicon are tens of nm node and will not response to glitch that is many times narrower than the normal 10MHz wanted-signal.

2. SDS2000X Plus is 1 or 2GSa/s in 4 or 2 channel mode.  So, I got 100 to 200 dots for the 10MHz signal.  Spec. also says 1ns peak detection.  Presumably, refers to best case signal at full swing voltage (3.3 volts).  Presumably, the scope will detect lower-voltage glitch at, says, 1 volt, of a few ns long. 

3. SDS2000X Plus will do the job, right?  If the scope does not see any glitch, the glitch energy, (voltage multipy time) should be too weak to cause the chip to response, right?

The modern DSO is pretty powerful at finding stuff you might not even think is present.....it's all about using the features available to see that you might have a problem then applying the toolset to capture them.



This ^^^ screenshot is a good example where some Persistence shows it's present then we can narrow in and seen if it's a one off or repetitive.
In this post I did a similar exercise with the older SDS1104X-E which gives some idea of using a few of the scopes features:
https://www.eevblog.com/forum/testgear/siglent-sds1204x-e-released-for-domestic-markets-in-china/msg1370717/#msg1370717

Comparing SDS1104X-E and SDS2104X-Plus.  Does the cheaper unit have same toos/function (trigger, search, measure) for the purpose of design verification, to hunt for abnormal signals in 10MHz SPI signal between MCU and external chips?

Is there more differences than what I found so far from scanning manual:

500MSa/s   vs   1000MSa/s in 4 channels mode (MISO, MOSI, Clock, nChipSelect), 500M is 50 samples per 10MHz signal pulse.  Enough to see abnormal glitch, runt, overshoot, undershoot???

7 Mpts/CH  vs  100Mpts, 7M captures 140,000 pulses at 50 samples per pulse. 

No histogram, still has StdDev to qualtify signal jitter.

7 inches and non-touch screen.   Needs a few more human seconds to use knobs to active a function, right?

TBH, today if wanting a lower cost solution and happy with a 7" display, SDS814X HD is where it's at.

Many thanks.  From SDS814X HD user manual, it has a new trigger mode, among manys, that seem to fit my speific SPI signal hunting.

Being new to modern MSO, please kindly advise if below is correct understanding:

1. Is trigger setup ">, <, in-range and out-of-range" for a numberic value for the setup time and holdtime respectively?

2. If I set trigger "setup time < data sheet value", and let the McU run overnight.  if the scope did not trigger, there was no glitch nor rare abnormal events leading to non-compliance of "setup time should be longer than datasheet value".

3. If I capture a random frame of data to full memory of the scope (tens of ms of MCU real run time at 1GSa/s), I can use SEARCH with "setup_time of >1ns", I should get 100% event hit. 

Slowly increase, to says, 100ns, as data sheet, if still got 100% event hit, this VERIFY that the data frame meet the data sheet value.

Further increase time to get 50% event hit, this will be the medium value of the circuit's setup time, right?

[Fungus]

2. If I set trigger "setup time < data sheet value", and let the McU run overnight.  if the scope did not trigger, there was no glitch nor rare abnormal events leading to non-compliance of "setup time should be longer than datasheet value".

Even better: Modern DSOs can configure segmented memory and record all the events separately, along with a count of how many there were.

(assuming there's not too many of them to fit in the 'scopes memory ... )

[tatel]

I you want a MSO option that works fine, you should have a look at this user report linked below. I don't think you'll be happy with SDS1104X-E for that, you'd better get at least Rigol MSO5000 or Siglent SDS2000, or perhaps the new siglents 800 HD, and even then, I would ask for some real user-experience-based report about the specific model you're looking at, before pulling the trigger

https://www.eevblog.com/forum/testgear/siglent-sds1204x-e-released-for-domestic-markets-in-china/msg3528422/#msg3528422

[Fungus]

or perhaps the new siglents 800 HD

The Siglent 800DH logic option is a weird USB thing. I'd take a good look at reviews before deciding on that.

[KungFuJosh]

The Siglent 800HD logic option is a weird USB thing. I'd take a good look at reviews before deciding on that.

It's not that weird being an external analyzer/adapter, but the consensus is that the 2000 level stuff is obviously better. The SPL2016 logic probe used with the nicer scopes with built-in analyzers is also nicer...but my generic SPL2016 copy works well enough for my needs for ~10% of the price. 😉

[tautech]

If you have the budget to go higher than the SDS2000X Plus, then compare it with the SDS2000X HD. Either one would be a great scope for your needs

Many thanks for info.  My use is design verification.  Use DSO to inspect signal lines to confirm that there is no abnormal glitch nor invalid signal. Are below correct?

1. The MCU and external chips works at 10MHz SPI clock.  Likely these silicon are tens of nm node and will not response to glitch that is many times narrower than the normal 10MHz wanted-signal.

2. SDS2000X Plus is 1 or 2GSa/s in 4 or 2 channel mode.  So, I got 100 to 200 dots for the 10MHz signal.  Spec. also says 1ns peak detection.  Presumably, refers to best case signal at full swing voltage (3.3 volts).  Presumably, the scope will detect lower-voltage glitch at, says, 1 volt, of a few ns long. 

3. SDS2000X Plus will do the job, right?  If the scope does not see any glitch, the glitch energy, (voltage multipy time) should be too weak to cause the chip to response, right?

The modern DSO is pretty powerful at finding stuff you might not even think is present.....it's all about using the features available to see that you might have a problem then applying the toolset to capture them.



This ^^^ screenshot is a good example where some Persistence shows it's present then we can narrow in and seen if it's a one off or repetitive.
In this post I did a similar exercise with the older SDS1104X-E which gives some idea of using a few of the scopes features:
https://www.eevblog.com/forum/testgear/siglent-sds1204x-e-released-for-domestic-markets-in-china/msg1370717/#msg1370717

Comparing SDS1104X-E and SDS2104X-Plus.  Does the cheaper unit have same toos/function (trigger, search, measure) for the purpose of design verification, to hunt for abnormal signals in 10MHz SPI signal between MCU and external chips?

Is there more differences than what I found so far from scanning manual:

500MSa/s   vs   1000MSa/s in 4 channels mode (MISO, MOSI, Clock, nChipSelect), 500M is 50 samples per 10MHz signal pulse.  Enough to see abnormal glitch, runt, overshoot, undershoot???

7 Mpts/CH  vs  100Mpts, 7M captures 140,000 pulses at 50 samples per pulse. 

No histogram, still has StdDev to qualtify signal jitter.

7 inches and non-touch screen.   Needs a few more human seconds to use knobs to active a function, right?

TBH, today if wanting a lower cost solution and happy with a 7" display, SDS814X HD is where it's at.

Many thanks.  From SDS814X HD user manual, it has a new trigger mode, among manys, that seem to fit my speific SPI signal hunting.

Being new to modern MSO, please kindly advise if below is correct understanding:

Yep, a significant but certainly not insurmountable learning curve awaits you.

However a DSO provides capability a CRO can't, DSO trigger capabilities are next level....and some and then add how you can inspect a captured signal or its decode.
All you have left is to consider your spend and the features a little more $ can provide.

We have already discussed the Serial Test feature the SDS2000X Plus models offer, not available in the lower cost models.
Take the time to revisit the previous replies and the screenshots .......

[Wilson__]

2. If I set trigger "setup time < data sheet value", and let the McU run overnight.  if the scope did not trigger, there was no glitch nor rare abnormal events leading to non-compliance of "setup time should be longer than datasheet value".

Even better: Modern DSOs can configure segmented memory and record all the events separately, along with a count of how many there were.

(assuming there's not too many of them to fit in the 'scopes memory ... )

After the scope has capture multiple copies of the trigger event plus one screen width of data around trigger point, I can SEARCH the captured data using different 'trigger condition' to find some abnormal events, right?  For example, pulse abnormally higher voltage;  some has RUNT

[Wilson__]

I you want a MSO option that works fine, you should have a look at this user report linked below. I don't think you'll be happy with SDS1104X-E for that, you'd better get at least Rigol MSO5000 or Siglent SDS2000, or perhaps the new siglents 800 HD, and even then, I would ask for some real user-experience-based report about the specific model you're looking at, before pulling the trigger

https://www.eevblog.com/forum/testgear/siglent-sds1204x-e-released-for-domestic-markets-in-china/msg3528422/#msg3528422

I scanned this forum.  Apparent lower model Siglent, LA is a separate sub-system that link to the scope over a cable.  This has limited speed.   Higher end model has the LA circuit inside the scope, run fastrer and better integration.

I shall limit my expection to 4 channel LA, using the scope channel. SPI only need 4 and that fits my task on hand.   I can get an higher model if next task requires and factor into projet cost.

[Performa01]

After the scope has capture multiple copies of the trigger event plus one screen width of data around trigger point, I can SEARCH the captured data using different 'trigger condition' to find some abnormal events, right?  For example, pulse abnormally higher voltage;  some has RUNT

Even better: the always active history stores the trigger events for you without the need for you to do anything for it. Up to 80000 trigger events (depending on timabase and memory depth) can be stored in the history and inspected to your hearts content afterwards. All the tools are available and a couple advanced triggers are supported for event search, which works across the history if so desired. Compared to Sequence mode, history is just not as fast and there is no guaranteed max. dead time (down to 2 µs!), which is still sufficient in many use cases.

[Wilson__]

After the scope has capture multiple copies of the trigger event plus one screen width of data around trigger point, I can SEARCH the captured data using different 'trigger condition' to find some abnormal events, right?  For example, pulse abnormally higher voltage;  some has RUNT

Even better: the always active history stores the trigger events for you without the need for you to do anything for it. Up to 80000 trigger events (depending on timabase and memory depth) can be stored in the history and inspected to your hearts content afterwards. All the tools are available and a couple advanced triggers are supported for event search, which works across the history if so desired. Compared to Sequence mode, history is just not as fast and there is no guaranteed max. dead time (down to 2 µs!), which is still sufficient in many use cases.

Many thanks for vast number of tests as in https://www.eevblog.com/forum/testgear/sds800x-hd-review-demonstration-thread/msg5293741/#msg5293741

Part one report shows the scope can capture pulse of two to four ns (presumably depends on 1,2 or 4 ch, at 2, 1 and 0.5MSa/s) and SPI decode at tens of time higher than my 10MHz task-on-hand.

Is the software 'practically' no bug for normal use?  Any reason not to buy this (apart from 2000 series has the new serial test mode that measures dozen SPI signal parameters automatically, bigger screen and build-in LA)?

[tautech]

After the scope has capture multiple copies of the trigger event plus one screen width of data around trigger point, I can SEARCH the captured data using different 'trigger condition' to find some abnormal events, right?  For example, pulse abnormally higher voltage;  some has RUNT

Even better: the always active history stores the trigger events for you without the need for you to do anything for it. Up to 80000 trigger events (depending on timabase and memory depth) can be stored in the history and inspected to your hearts content afterwards. All the tools are available and a couple advanced triggers are supported for event search, which works across the history if so desired. Compared to Sequence mode, history is just not as fast and there is no guaranteed max. dead time (down to 2 µs!), which is still sufficient in many use cases.

Many thanks for vast number of tests as in https://www.eevblog.com/forum/testgear/sds800x-hd-review-demonstration-thread/msg5293741/#msg5293741

Part one report shows the scope can capture pulse of two to four ns (presumably depends on 1,2 or 4 ch, at 2, 1 and 0.5MSa/s) and SPI decode at tens of time higher than my 10MHz task-on-hand.

Is the software 'practically' no bug for normal use?  Any reason not to buy this (apart from 2000 series has the new serial test mode that measures dozen SPI signal parameters automatically, bigger screen and build-in LA)?

Well we have hung our hat on SDS800X HD models as our low cost but advanced solution as its capabilities well exceed all previous Siglent models at this price point.
Only when you need a 10" display other pricier models get suggested however SDS800X HD is just half your initial budget and I know you will be very impressed with its capability as I have 100% confidence it will meet your needs.

[Wilson__]

After the scope has capture multiple copies of the trigger event plus one screen width of data around trigger point, I can SEARCH the captured data using different 'trigger condition' to find some abnormal events, right?  For example, pulse abnormally higher voltage;  some has RUNT

Even better: the always active history stores the trigger events for you without the need for you to do anything for it. Up to 80000 trigger events (depending on timabase and memory depth) can be stored in the history and inspected to your hearts content afterwards. All the tools are available and a couple advanced triggers are supported for event search, which works across the history if so desired. Compared to Sequence mode, history is just not as fast and there is no guaranteed max. dead time (down to 2 µs!), which is still sufficient in many use cases.

Many thanks for vast number of tests as in https://www.eevblog.com/forum/testgear/sds800x-hd-review-demonstration-thread/msg5293741/#msg5293741

Part one report shows the scope can capture pulse of two to four ns (presumably depends on 1,2 or 4 ch, at 2, 1 and 0.5MSa/s) and SPI decode at tens of time higher than my 10MHz task-on-hand.

Is the software 'practically' no bug for normal use?  Any reason not to buy this (apart from 2000 series has the new serial test mode that measures dozen SPI signal parameters automatically, bigger screen and build-in LA)?

Well we have hung our hat on SDS800X HD models as our low cost but advanced solution as its capabilities well exceed all previous Siglent models at this price point.
Only when you need a 10" display other pricier models get suggested however SDS800X HD is just half your initial budget and I know you will be very impressed with its capability as I have 100% confidence it will meet your needs.

Many thanks for advises.  Yes, it is impressive and learning curve ahead.  Bug thread are mostly resolved and few minor bug (beep sound) was discovered recently.  https://www.eevblog.com/forum/testgear/sds800x-hd-bug-reports-firmware/

[awakephd]

The Siglent 800HD logic option is a weird USB thing. I'd take a good look at reviews before deciding on that.

It's not that weird being an external analyzer/adapter, but the consensus is that the 2000 level stuff is obviously better. The SPL2016 logic probe used with the nicer scopes with built-in analyzers is also nicer...but my generic SPL2016 copy works well enough for my needs for ~10% of the price. 😉

Could you say more about your "generic SPL2016 copy"? I wasn't aware (or perhaps have forgotten) that such a thing exists ... ?

[tautech]

The Siglent 800HD logic option is a weird USB thing. I'd take a good look at reviews before deciding on that.

It's not that weird being an external analyzer/adapter, but the consensus is that the 2000 level stuff is obviously better. The SPL2016 logic probe used with the nicer scopes with built-in analyzers is also nicer...but my generic SPL2016 copy works well enough for my needs for ~10% of the price. 😉

Could you say more about your "generic SPL2016 copy"? I wasn't aware (or perhaps have forgotten) that such a thing exists ... ?

Google diy SPL2016