Products > Test Equipment
Desktop DSO for hardware and firmware development of MCU systems
KungFuJosh:
--- Quote from: Fungus on September 17, 2024, 07:01:39 pm ---The Siglent 800HD logic option is a weird USB thing. I'd take a good look at reviews before deciding on that.
--- End quote ---
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:
--- Quote from: Wilson__ on September 17, 2024, 02:59:17 pm ---
--- Quote from: tautech on September 16, 2024, 10:30:29 am ---
--- Quote from: Wilson__ on September 16, 2024, 10:00:58 am ---
--- Quote from: tautech on September 13, 2024, 08:59:14 pm ---
--- Quote from: Wilson__ on September 13, 2024, 04:36:31 pm ---
--- Quote from: KungFuJosh on September 12, 2024, 05:09:12 pm ---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
--- End quote ---
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?
--- End quote ---
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
--- End quote ---
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?
--- End quote ---
TBH, today if wanting a lower cost solution and happy with a 7" display, SDS814X HD is where it's at.
--- End quote ---
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:
--- End quote ---
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__:
--- Quote from: Fungus on September 17, 2024, 03:26:10 pm ---
--- Quote from: Wilson__ on September 17, 2024, 02:59:17 pm ---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".
--- End quote ---
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 ... )
--- End quote ---
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__:
--- Quote from: tatel on September 17, 2024, 03:49:46 pm ---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
--- End quote ---
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:
--- Quote from: Wilson__ on September 17, 2024, 09:39:51 pm ---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
--- End quote ---
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.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version