1mV / div = Really ?
please see my post about 1074z [no one mention it]
I wish they had the MSO4000 on display! Dang nab it!
I wish they had the MSO4000 on display! Dang nab it!
Agreed, I'm tired of waiting. Seriously thinking about a Hameg HMO3000.
please see my post about 1074z [no one mention it]What post?
What post?
What are you saying about the 1mv/div range?
- There is a second concern, and more annoying, with the trending method - It only trends post trigger! If the trigger is in centre of display then you end up waiting a half display of sweep time before any activity occurs. This can be minutes! This, combined with the time based (rather than display based) trigger position, kind of makes for a lot of fiddling to get immediate visualisation of acquisitions.
Trivial gripe: CLEAR, AUTO and SINGLE keys really do seem to be useless. Why would one want to clear all traces? I've used auto setting before, it never gets what I want and it totally loses the settings I had set. A separate button to set single trigger mode, say what?, there is a simple to use trigger mode button straight below that!
Not so trivial: In the acquisition menu, what does Sin(x)/x setting do? I don't see any effect on traces. The help makes a vague reference to interleaving. This setting is one of those settings, I mentioned previously, that doesn't stay set. Maybe it doesn't really need a user setting at all?
... Just noticed another one to be wary of: Peak acquisition mode places it's two min-max values in successive sample points in the trace. This allows the memory depth to be shown as unchanging between Normal and Peak modes. I had wondered why that parameter didn't change. The problem with this configuration is when zooming in to look at the fine detail, instead of seeing a continuous min-max block fill, you see a triangle wave at half the sample rate toggling between the upper and lower values. A sudo alias of sorts. This is a behaviour that Peak mode is meant to avoid.
As long as this is true: "Microsoft has not released the official exFAT file system specification, and ..so on", imho, there is not any reason use this in serious lab equipments.
- There is a second concern, and more annoying, with the trending method - It only trends post trigger! If the trigger is in centre of display then you end up waiting a half display of sweep time before any activity occurs. This can be minutes! This, combined with the time based (rather than display based) trigger position, kind of makes for a lot of fiddling to get immediate visualisation of acquisitions.Not sure where you're appropriating the word 'trending' from (2D graphics?) but:
1) The DSO can't display pre-trigger data until it's acquired a trigger (it's a given of the way triggering systems work on a DSO). If you want to have less pre-trigger display (and less of a wait with slow horizontal scale settings), then just adjust the trigger position - it's the same on every DSO.
2) If the DS1000Z series is like my DS2000 series, then you can just switch from normal Y-T acquisition to Roll mode via the Horizontal -> Timebase menu setting, if that's what you prefer.
QuoteTrivial gripe: CLEAR, AUTO and SINGLE keys really do seem to be useless. Why would one want to clear all traces? I've used auto setting before, it never gets what I want and it totally loses the settings I had set. A separate button to set single trigger mode, say what?, there is a simple to use trigger mode button straight below that!You might not realize it now, but CLEAR is very often handy - especially when having multiple REFerence traces, buses, etc.
Also, the SINGLE key is NOT the same thing as the button to set single-trigger mode: once it's in single-trigger mode and a trigger occurs - the DSO goes to STOP. The SINGLE button takes it back to WAITing for the next single trigger - the mode button does NOT.
QuoteNot so trivial: In the acquisition menu, what does Sin(x)/x setting do? I don't see any effect on traces. The help makes a vague reference to interleaving. This setting is one of those settings, I mentioned previously, that doesn't stay set. Maybe it doesn't really need a user setting at all?I'm not trying to be unnecessarily mean here, but if you don't know what Sin(x)/x interpolation is on a DSO, you probably need to do a bit of reading on the subject. Such as this.
Quote... Just noticed another one to be wary of: Peak acquisition mode places it's two min-max values in successive sample points in the trace. This allows the memory depth to be shown as unchanging between Normal and Peak modes. I had wondered why that parameter didn't change. The problem with this configuration is when zooming in to look at the fine detail, instead of seeing a continuous min-max block fill, you see a triangle wave at half the sample rate toggling between the upper and lower values. A sudo alias of sorts. This is a behaviour that Peak mode is meant to avoid.This is how ALL DSOs handle Peak Acquisition - look at the chart from Tektronix:
...
No offense, but I think you need to do some basic reading on DSOs and their operation.
My old scope achieves what I'm talking about. I described it in my second post.
The STOP/START key performs that function. The SINGLE key is completely pointless.
So, we are talking about filling in sample points in the stored trace that weren't actually sampled because the hardware interleaving means the sampler was on another channel?
Or maybe it's talking about trace rendering to display? Shouldn't that be in the display setting menu rather than the acquisition setting menu?
Have a careful re-read of what I've said. Maybe I need to be clearer. Ask me what I meant if something is confusing.
My old scope achieves what I'm talking about. I described it in my second post.Yes, you described Roll mode - which the Rigol does perfectly well (as mentioned).
QuoteThe STOP/START key performs that function. The SINGLE key is completely pointless.Strange, then Rigol has redefined those buttons on your DS1000Z because they act differently on the DS2000. The RUN/STOP button puts the DSO into AUTO mode - it does NOT reset SINGLE mode - so the SINGLE button on my DSO is far from pointless.
No, you were perfectly clear. You wrote 'Just noticed another one to be wary of...' as if you thought Rigol was doing something unusual in it's Peak Detect implementation
You also wrote: 'This is a behaviour that Peak mode is meant to avoid.'- which is incorrect.
It's not a separate non-triggering mode. It's integral and doesn't require any adjustments and doesn't impose extra limits or exceptions.
Ah, my inexperience with the Rigols is showing here. Strange behaviour for the START to force auto triggering but that would be a good explanation. I don't have it with me so can't confirm right now.
Hmm, I regularly stop a Normal trigger mode when inspecting a deep capture. Then restart it again after completing my examination. I presume pressing the START key will flip it to Auto triggering instead of just resuming the Normal triggering ...
QuoteNo, you were perfectly clear. You wrote 'Just noticed another one to be wary of...' as if you thought Rigol was doing something unusual in it's Peak Detect implementationYes!
QuoteYou also wrote: 'This is a behaviour that Peak mode is meant to avoid.'- which is incorrect.We differ on opinion there.
Yes, I re-edited my comment above when I realized you were talking about something different than Roll mode. Now I assume you mean a Scan mode (from left to right - Roll mode always displays from right to left) and I'm curious what that DSO is actually displaying if there's been no trigger - and what happens to the display when a trigger occurs.
On the DS2000, pressing RUN/STOP while stopped in Normal mode will just re-start Normal mode.
...which, as I pointed out with the Tektronix diagram (which shows a triangle wave at high magnification of a Peak Detect acquisition) is not the case at all.
...
Any acquisition mode that does post-processing on the samples for a specific effect is likely to show artifacts when magnifying the waveform - this is not behavior which Peak Detect could ever avoid.
Um, um, nooo...! The Tek example is terrible. I didn't look carefully at it first time around but I now see that method is done incorrectly. The two stored samples, of one interval, are treated as separate intervals of time from a rendering point of view. But they don't correspond to the equivalent shape through time of the original signal.
They are really nothing more that a min-max of one interval. They should be treated as such when displayed.