Products > Test Equipment
A newbie needs some help with my first DSO
<< < (14/25) > >>
tggzzz:

--- Quote from: Someone on June 02, 2024, 01:34:36 am ---...
for your reading pleasure, a separate 562 post thread on just that topic, linking to the context that nctnico intentionally leaves out (which makes this blatant inflammatory posting):
https://www.eevblog.com/forum/testgear/oscilloscope-zoom-out-quirk/msg3060638/#msg3060638
Dismissal of using a zoom window for... ill-defined/unsubstantiated reasons. Perhaps this forum will get another several thousand posts of crap on this topic over the next 10 years?

--- End quote ---

Interesting, for several reasons.
tautech:

--- Quote from: tggzzz on June 02, 2024, 08:35:38 am ---
--- Quote from: tautech on June 01, 2024, 09:08:09 pm ---Oh FFS
Please you 2 go get a room together, not one where the OP is attempting to get his head around the featureset of his first DSO.

--- End quote ---

I tend to agree.

I did post use-cases for which advanced features are used, but they were ignored.

--- End quote ---
And rightly so.

Did you not walk before you could run......sure this stuff is pretty straight forward to many of us but some need a helping hand before just getting past basic features.
tggzzz:

--- Quote from: tautech on June 02, 2024, 08:43:26 am ---
--- Quote from: tggzzz on June 02, 2024, 08:35:38 am ---
--- Quote from: tautech on June 01, 2024, 09:08:09 pm ---Oh FFS
Please you 2 go get a room together, not one where the OP is attempting to get his head around the featureset of his first DSO.

--- End quote ---

I tend to agree.

I did post use-cases for which advanced features are used, but they were ignored.

--- End quote ---
And rightly so.

Did you not walk before you could run......sure this stuff is pretty straight forward to many of us but some need a helping hand before just getting past basic features.

--- End quote ---

Often it is useful to be aware of use cases so that:

* you can recognise them when they arise
* you gain perspective of why certain features are present
* you choose the most appropriate tool for the job, e.g. avoiding using a hammer with screws
It is always useful to have knowledge that exceeds the current requirements. That way you know the boundaries, and that you haven't unwittingly strayed outside the boundaries.

However with modern DSOs the boundaries are a little like this[1]
https://www.google.co.uk/maps/place/Netherlands/@51.4459163,4.9256093,21z/data=!4m6!3m5!1s0x47c609c3db87e4bb:0xb3a175ceffbd0a9f!8m2!3d52.132633!4d5.291266!16zL20vMDU5ajI?entry=ttu
but that's an advantage, isn't it.

[1] to get the best understanding, slowly zoom out 4 or  5 times, concentrating on the boundaries :)
nctnico:

--- Quote from: BillyO on June 02, 2024, 12:43:57 am ---
--- Quote from: nctnico on June 02, 2024, 12:31:47 am ---If (part of) your work (like mine) consists of doing single shot measurements, then history doesn't matter. It is wasted memory because the previous measurement simply isn't relevant. So please give me the choice to have full memory in a single shot even though some or most of it doesn't show on screen right away.

--- End quote ---
Can you explain this a little better (not being argumentative, but I just don't understand)?  What is it you are looking for that can ONLY occur after the moment of acquisition?

--- End quote ---
I need to take you a step back here.

First of all: When you measure something, you want to be able to make a relation between cause and effect so you can draw a conclusion from the measurement result. This may sound obvious but for many it requires training to measure / collect data in a way so it is possible to establish a singular cause & effect relationship.

Secondly: I'm not looking at something which can only occur after the moment of acquisition. I just want 1 acquisition with as much data as possible so I can see what happened before AND after an event. I might not always need the data but with shorter memory DSOs I have often wished to have more data in order to have more information about what happened before and after an error condition. That can show the problem so it can be fixed right away or can give valueable glues on what to set triggers for and thus save a lot of time (and money) instead of poking around in the dark. Keep in mind that my typical measurements are for DUTs which are highly sequential through hardware and/or software.

Back to the history buffer: When I'm debugging / testing embedded firmware / FPGA / hardware, each single shot measurement represents a new version with a fix or change. Which means that whatever is in the history buffer is no longer relevant information as I won't be able to match a specific acquisition with a specific change somewhere. There is no way to draw a meaningfull conclusion from the data in the history buffer. So I rather have no history buffer at all if that means getting more memory for the current acquisition.

A history buffer is only usefull if you can record all relevant information in/by the oscilloscope itself (input versus output) without making changes to the DUT. That way you can draw a meaningfull conclusion from the acquisitions in the history buffer. Keep in mind though that a history buffer and segmented recording are functionally equal it is just that an automatic history buffer is easier to use / setup.
Fungus:
Please post an example of where filling up the memory is worse.

(Or where not filling it up is better...)
Navigation
Message Index
Next page
Previous page
There was an error while thanking
Thanking...

Go to full version
Powered by SMFPacks Advanced Attachments Uploader Mod