Yet it's arguably DSO user error when any capture is required that an appropriate timebase was not previously selected.
No. I'm talking about legitimately setting the timebase to capture the thing you wanted, no user error. Then perhaps you saw something unexpected and though "gee I wonder what happened before or after that".
I understand what are you saying, but when working on, say, CAN bus, what are the chances you will happen to capture exactly packet with error if you looking at single edge? You don't capture that way looking at that kind of data. You use larger time period, with hundreds of packets and then search and scroll and zoom in and out.
You can't say you understand what I'm saying then immediately go into an example where it's not going to be of value. That is completely opposite to my point!
I'll repeat, there is no logical argument you can make to say that this isn't a potentially useful feature in some circumstances.
Yes, but as these seem to keep coming back to:
Poster A says a scope is not worth considering because it can't do some very specific feature..... not mentioning how that feature might be useful or what situations might make it applicable.
Poster B points out the holes in their point and explains other comparable methods.
Poster A keeps narrowing the goalposts to be "right"
Time was wasted by all and a confusing mess is left behind. The generalised answer is there are many corner cases for test/measurement and they generally aren't applicable unless that matches the users application.
Home
Help
Search
Login
Register
