I recently ran a test comparing the SPI triggering and decoding speed of Keysight EDUX1002G (modded to DSOX1102G) and Siglent SDS1104X-E
The details of the test was posted in a different thread:
https://www.eevblog.com/forum/testgear/everyday-bench-scope-a-3-way-race-edux1002a-gds-1054b-sds1202x-e/msg2412507/#msg2412507
Summary of test: STM32 nucleo board running @ 180MHz. 45MHz SPI clock. The test outputs 50,000 full cycles of 8 frames from 1 byte to 8 bytes. When a button is pressed, it sends a frame with 1 byte with value 0x3F. Normally one of the 8 frames has byte value 0x37 in the same position.
Conclusion: Keysight was able to trigger 50,000 times per second when triggering on byte value 0x37. Siglent SDS1104X-E triggered 3,000 times. The difference is due to the fact that the Keysight is doing Serial triggering and decoding in the ASIC and the Siglent implemented it in software after the memory was sampled.
In initial tests, I used a GWInstek GDS1054B and Micsig TO1104 with similar results to the Siglent SDS1104X-E, all of them have serial triggering and decoding implemented in software.
Keysight is really lot of more fast to trig serial. This is natural due to very different design.
Of course also slow software system have still one advantage. It can decode offline. So or so, KS is lot of more fast and thats it.
But still I need ask did you all for get best speed using Siglent.
Why I ask:
I have not system what I can use for this speed of SPI or any other serial trigger and/or decode.
So for this I can not say "anything".
But if look Siglent maximum wfm/s speed. It is also limiting factor.
If it freerun as fast as it can...
1 channel on.
Display mode dots
Delay 0
50ns/div
No measurements
Trigger Normal, edge
Signal square (tested with 5MHz and 20MHz)
average is roughly 118kwfm/s
burst speed roughly 128kwfm/s (between TFT refreshs, there is extra blind time every TFT refresh (40ms period) roughly 3.5ms)
1 channel on.
Display mode Vextors (Sinc or x)
Delay 0
50ns/div
No measurements
Trigger Normal, edge
Signal square (tested with 5MHz and 20MHz)
average is roughly 20kwfm/s
burst speed roughly 22kwfm/s (between TFT refreshs, there is extra blind time every TFT refresh (40ms period) roughly 3.5ms)
And now, same but 4 channels on. As need be with full SPI.
All 4 channels on.
Display mode dots
Delay 0
50ns/div
No measurements
Trigger Normal, edge
Signal square (tested with 5MHz and 20MHz)
average is roughly 10.5kwfm/s
burst speed roughly 11.4kwfm/s (between TFT refreshs, there is extra blind time every TFT refresh (40ms period) roughly 3.5ms)
All 4 channels on.
Display mode vectors (Sinc on (x is bit faster ))
Delay 0
50ns/div
No measurements
Trigger Normal, edge
Signal square (tested with 5MHz and 20MHz)
average is roughly
4kwfm/sburst speed roughly 4.5kwfm/s (between TFT refreshs, there is extra blind time every TFT refresh (40ms period) roughly 3.5ms)
As can see even if decode or serial trigger do not affect this make limit, so even if Siglent works hard for make decode faster and tso also serial trigger it can not go very fast due to limits of maximum wfm/s except if they do not make very extremely radical changes.
But perhaps if need maximize Siglent speed as it is now, it is good to use display mode dots or least linear interpolation what also (in some cases) may give tiny amount more speed. But dots mode give much more. (If dots mode is selected no matter if there is Sinc or x selected)
Normally for digital pulse streams linear interpolation is ok, specially when signal is fast related to samplerate so it do not generate "fake" overshoots. (gibbs ears)
I have no idea how much these different settings may affect for high speed serial trigger and decoding speed.
(Btw, decoding affect also maximum wfm/s speed. When it capture between TFT refresh not so much but Decode need more time between TFT refresh. (exmple as told in this test, it was around 3.5ms and if I just only turn decode on with some random settings and without serial signals etc, just only push Decode function on. Every TFT period this blind time cap (some processing) rise to around 20ms. What of course drop also average wfm/s speed.
(segmented acquisition do not have at all this processing time during acquisition but after sequence, then display processing time is - long - because it overlay all segments to TFT (before start next sequence if repeating is selected) also trig rearm is faster. Least with normal signals, example just with previous test (50ns/div and total 45526 segments) all channels on, 20MHz signal independent of display modes, etc... 320ksegment/s (kwfm)
and then one channel in use 487ksegment/s)