| Products > Test Equipment |
| Functional comparison of R&S RTB2000, Siglent SDS2000X and Keysight DSOX1000 |
| << < (23/39) > >> |
| rf-loop:
--- Quote from: Someone on April 05, 2022, 10:48:18 am --- --- Quote from: rf-loop on April 05, 2022, 10:22:12 am --- --- Quote from: RBBVNL9 on April 05, 2022, 09:43:22 am ---SDS - “Seq. Acq. Switch” set to off. When it is turned on, I see sets of n acquisitions (where n is the number set by the “Seq Segment” parameter” with almost 100mS in between, so a considerable drop in the number of trigger events per second. --- End quote --- This is really weird. Even If I test with this same signal with SDS1104X-E and 200us/div and Sequence. I take oneshot sequence with 50MSa/s 140k length and when I look segments time stamps they have all 3ms (3000us) delta time. So 333.33 segments in second. Then I change it to 14k memory so 5MSa/s and look 1900 segment single sequence. Every single segment in sequence time stamp delta time is 3ms. So 333.33... segment/s Then with 1GSa/s 2.8M current mem lenght (one segment length)... still all 19 segments delta time is 3ms.... 333.33... segment/s --- End quote --- I think the explanation is good, with the sequence mode in run mode: [n sequences without gaps] 100ms processing interval [n sequences without gaps] 100ms processing interval... etc Interesting it was not in a circular mode (does not support it?) where the sequences capture around forever until stop is pressed. --- End quote --- It was nice you rise this circular mode up. Siglent do not have it (least yet afaik) It works sequentially. (kind of burst) It take one sequence (user defined n amount of segments in one fast *) sequence) and after this is ready, it processes all of these for display - stacking (overlay) them all, without interleaving together in one TFT image. And this take time, in some cases it may take really long time and during this it do not capture signal at all (just total blind). After then (in continuous mode) it start new squence. Trigger mode Normal (and also Autyo) mode is this repeating sequence mode and Single run just one single sequence and after all n seqments captured it stop and then processes all these for display n segments overlaid. In some cases it may be useful if there is "circular" or this kind of continuous mode where it can capture as normal fast sequence mode but without user defined n, working just as circular buffer or fifo... how want think it. It capture segments until user or some signal stop it. After then can look last captured segments (limited by total available memory and user defined seegment length). Only after stop it can display what is captured. (Siglent HW can not simultaneously handle displaying signal and run fast sequence mode capturing.) But this kind of mode is not implemented. Is this kind of mode useful or not... and if, when. *) fast mean that it can repeat trig "fast". (fastest trig interval 2us) |
| nctnico:
--- Quote from: rf-loop on April 05, 2022, 01:03:28 pm --- --- Quote from: Someone on April 05, 2022, 10:48:18 am --- --- Quote from: rf-loop on April 05, 2022, 10:22:12 am --- --- Quote from: RBBVNL9 on April 05, 2022, 09:43:22 am ---SDS - “Seq. Acq. Switch” set to off. When it is turned on, I see sets of n acquisitions (where n is the number set by the “Seq Segment” parameter” with almost 100mS in between, so a considerable drop in the number of trigger events per second. --- End quote --- This is really weird. Even If I test with this same signal with SDS1104X-E and 200us/div and Sequence. I take oneshot sequence with 50MSa/s 140k length and when I look segments time stamps they have all 3ms (3000us) delta time. So 333.33 segments in second. Then I change it to 14k memory so 5MSa/s and look 1900 segment single sequence. Every single segment in sequence time stamp delta time is 3ms. So 333.33... segment/s Then with 1GSa/s 2.8M current mem lenght (one segment length)... still all 19 segments delta time is 3ms.... 333.33... segment/s --- End quote --- I think the explanation is good, with the sequence mode in run mode: [n sequences without gaps] 100ms processing interval [n sequences without gaps] 100ms processing interval... etc Interesting it was not in a circular mode (does not support it?) where the sequences capture around forever until stop is pressed. --- End quote --- It was nice you rise this circular mode up. Siglent do not have it (least yet afaik) --- End quote --- AFAIK the history buffer should work thay way (although likely not with fast sequence mode). |
| Someone:
--- Quote from: rf-loop on April 05, 2022, 01:03:28 pm ---It was nice you rise this circular mode up. Siglent do not have it (least yet afaik) --- End quote --- I am not fully familiar with all these models, thanks for confirming how the Siglent handles it: burst - display - burst - display - etc As I recall the Keysight 1100 and 1200 have a (speed crippled in the 1100) segmented buffer, that does not display them until you stop and manually request it. But it can be switched between circular and one shot. The run/single buttons are not used as the obvious controls for that, more confusions. Would be interesting to hear more on what options and controls the R&S (optional?) segmented and history modes have, looks like more depth/options than the other two. My favourite implementation of history/segmented memory is the Lecroy Wavejet 300 (oem: Iwatsu) it is a good balance of realtime update rate, and continuous "replay" segment history. Priced well above the comparisons considered here though. |
| Someone:
--- Quote from: nctnico on April 05, 2022, 01:15:21 pm --- --- Quote from: Someone on April 05, 2022, 10:48:18 am --- --- Quote from: rf-loop on April 05, 2022, 10:22:12 am --- --- Quote from: RBBVNL9 on April 05, 2022, 09:43:22 am ---SDS - “Seq. Acq. Switch” set to off. When it is turned on, I see sets of n acquisitions (where n is the number set by the “Seq Segment” parameter” with almost 100mS in between, so a considerable drop in the number of trigger events per second. --- End quote --- This is really weird. Even If I test with this same signal with SDS1104X-E and 200us/div and Sequence. I take oneshot sequence with 50MSa/s 140k length and when I look segments time stamps they have all 3ms (3000us) delta time. So 333.33 segments in second. Then I change it to 14k memory so 5MSa/s and look 1900 segment single sequence. Every single segment in sequence time stamp delta time is 3ms. So 333.33... segment/s Then with 1GSa/s 2.8M current mem lenght (one segment length)... still all 19 segments delta time is 3ms.... 333.33... segment/s --- End quote --- I think the explanation is good, with the sequence mode in run mode: [n sequences without gaps] 100ms processing interval [n sequences without gaps] 100ms processing interval... etc Interesting it was not in a circular mode (does not support it?) where the sequences capture around forever until stop is pressed. --- End quote --- AFAIK the history buffer should work thay way (although likely not with fast sequence mode). --- End quote --- Looking at the manual, and getting the confirmation from rf-loop, the Siglent does not have any continuous mode. While the Keysight does not have any mode where it will do displays along the way. Quite different, orthogonal, and singular/forceful/narrow minded in their approaches! |
| egonotto:
Hello, RBBVNL9 wrote: " "RTA behave little wilder." Can you perhaps elaborate on what you mean here? " in RTB the blind time seems has always the same length just as the non blind time, so the picture looks almost periodic. Different in RTA there has the blind time several length as the non blind time. It looks noway periodic. Best regards egonotto |
| Navigation |
| Message Index |
| Next page |
| Previous page |