And Keysight proves that it is perfectly possible to have high update rates AND deep memory at the same time.Keysight own Salesmens University have perhaps own basic math book. 1M memory need one M samples to fill. If sampling speed is 1GSa/s it takes 1ms and even with zero blind time (impossible) 1kwfm/s. But when deep memory is selected and scope is running for high update rates it can not capture deep memory, but salesmens forget to tell it.... Yes there can do example last acquisition trick.... and fool users (I do not know what is Keysight salesmens trick for this).There is no fooling users. Now you sound like the sales brochure you loath so much.
Just run two acquisition systems in parallel. One for storage and one for display. I have implemented something similar a couple of years ago. Works like a charm.QuoteBut how about deep full mem measurements during this high speed update rate with deep memory, how salesmens jump over this lazy fox. Oh... they never promised...No oscilloscope can measurements / math realtime. And it seems Siglent does ERES and Sin x/x interpolation in software which is even worse. But then again I don't really care about waveform update rates. I rather have an oscilloscope which offers a high rate of productivity (=least amount of twiddling knobs). The latter is where Siglent needs to improve.
But that still doesn't give you acquisition beyond the edge of the screen even if there is enough memory to do so. And Keysight proves that it is perfectly possible to have high update rates AND deep memory at the same time.
In many cases waveform update rate doesn't really matter when debugging digital / mixed signal circuits. Regulary I use normal mode and take single shots of specific events. It would be logical to have the centre of the screen as the centre point of the memory (half left, half right). At the point where this starts to matter you'll need to choose the time/div and trigger offset settings so you capture the part of the signal you want. But with deep memory this isn't difficult. The biggest benefit of deep memory is that you don't have to care so much about the trigger.
4MPts isn't exactly deep indeed but the way (-I think-) Keysight works it is easely expandable to 40Mpts, 400MPts, 4Gpts. Doesn't really matter.
And Keysight doesn't sacrifice anything. If I'm right they use two parallel acquisition systems. One with the large memory which works like a continuous circular buffer and one with a short buffer (enough to fill the screen) to do high update rates. Once you press stop Keysight scopes wait until the rest of the large memory buffer is filled before allowing the user to scroll left / right. It is a very simple & elegant solution.
My Tektronix MDO3k seems to capture the full memory depth that you set regardless of time-base. I guess that is the point to setting the memory in the first place.. since that setting would serve no purpose if it was time-base dependent.
If it have 10M memory length and 5GSa/s and IF it always use full memory regardless of timebase how it reach nearly 300kwfm/s capturing speed. Yes of course it can not. With 5GSa/s alone 10Msamle takes 2ms. (I believe there is other mode for max wfm speed)
If user have 1ns/div setting and IF screen is (just for easy numbers) 1 div wide... user can see 10ns and 1999980 ns is out from display and rest are invisible included to true visual blind time.
4MPts isn't exactly deep indeed but the way (-I think-) Keysight works it is easely expandable to 40Mpts, 400MPts, 4Gpts. Doesn't really matter.
And Keysight doesn't sacrifice anything. If I'm right they use two parallel acquisition systems. One with the large memory which works like a continuous circular buffer and one with a short buffer (enough to fill the screen) to do high update rates. Once you press stop Keysight scopes wait until the rest of the large memory buffer is filled before allowing the user to scroll left / right. It is a very simple & elegant solution.
4MPts isn't exactly deep indeed but the way (-I think-) Keysight works it is easely expandable to 40Mpts, 400MPts, 4Gpts. Doesn't really matter.
And Keysight doesn't sacrifice anything. If I'm right they use two parallel acquisition systems. One with the large memory which works like a continuous circular buffer and one with a short buffer (enough to fill the screen) to do high update rates. Once you press stop Keysight scopes wait until the rest of the large memory buffer is filled before allowing the user to scroll left / right. It is a very simple & elegant solution.Can you please explain what you mean by: Keysight works it is easely expandable to 40Mpts, 400MPts, 4Gpts. Doesn't really matter. It sounds interesting
Who can check if this model can use internal signal generator for BP use only without FG license installed.
4MPts isn't exactly deep indeed but the way (-I think-) Keysight works it is easely expandable to 40Mpts, 400MPts, 4Gpts. Doesn't really matter.
And Keysight doesn't sacrifice anything. If I'm right they use two parallel acquisition systems.
One with the large memory which works like a continuous circular buffer and one with a short buffer (enough to fill the screen) to do high update rates. Once you press stop Keysight scopes wait until the rest of the large memory buffer is filled before allowing the user to scroll left / right. It is a very simple & elegant solution.
Maybe I should activate this 27 times to know it - No..
So if you stop the aquisition in normal trigger mode and the trigger event happened e.g. 10ms before, the circular buffer was filled again multiple times. Sorry, but this just doesn't seem to be a feasible approach.
I don't think getting deep into the nitty-gritty of implementation details is very helpful.
I don't think getting deep into the nitty-gritty of implementation details is very helpful.It is as it helps us understand how each brand addresses their memory depth management and why they each have selected a particular scheme.
A facit that needs further discussion so to better understand Siglents implementation is their continuously running History buffer of some 200 MPts.
I'm quite sure nobody cares about history mode because it basically is an acquisition mode without clearly defined boundaries.
Lecroy also relies on history mode and on the memorydepth management - I think, when having full memorydepth independend from timebase is an important thing, they would implement it.
But they don´t and I´m sure they could if they want, there must be a reason why some brands doing it and some brands don´t.
Wether they´re so called A-Brands or not.
They'd be fools to weaken themselves against the competition.
I'm quite sure nobody cares about history mode because it basically is an acquisition mode without clearly defined boundaries.
You don't, you've already stated you don't care about wfps and hence blind time.....others do !
The age old discussion of DSO vs CRO has much to do about blind time of DSO's so why would a designer implement a memory management scheme where blind time could impact on scope usability ?
Somehow you managed to pick all the oscilloscopes with the least amount of memory in their price range.
Well... R&S has the RTC1000 series and an RTB2002 is in a similar price bracket. Tektronix TBS2000 series is also very nice to use although no decoding.