Products > Test Equipment
A newbie needs some help with my first DSO
<< < (15/25) > >>
2N3055:

--- Quote from: Fungus on June 02, 2024, 11:09:55 am ---Please post an example of where filling up the memory is worse.

(Or where not filling it up is better...)

--- End quote ---

He cannot, because there is none.

If you need long capture you take a long capture (regardless how you do it, by setting manual long memory or long time base).
If you are at shorter time base you are using only small portion of memory so rest is either waisted for nothing or you can put history there and make it useful.
Fungus:
It's not just about zooming, it's about panning left/right after STOP.

The Rigol DS1045Z's serial decoders were widely mocked for only being able to decode what was visible on screen.

To me the Siglent system seems like that except serial decoding was something I only did every other week but zooming/panning is something I do all the time.
2N3055:

--- Quote from: Fungus on June 02, 2024, 12:00:03 pm ---It's not just about zooming, it's about panning left/right after STOP.

The Rigol DS1045Z's serial decoders were widely mocked for only being able to decode what was visible on screen.

To me the Siglent system seems like that except serial decoding was something I only did every other week but zooming/panning is something I do all the time.

--- End quote ---

Why do you think you cannot move around captured buffer on Siglent? You can. Exactly the same as on any other scope.
BillyO:

--- Quote from: nctnico on June 02, 2024, 10:19:45 am ---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.

--- End quote ---
I respectfully remain unconvinced.  I think you have convinced yourself of an advantage that is not there.

Besides, there is a way to do exactly what you want by setting up your capture properly - and in this case you can place your trigger point any where you like in the data captured.  Zoom = Pink Cadillac.  Only has merit to those that "like it".
nctnico:

--- Quote from: BillyO on June 02, 2024, 01:45:45 pm ---
--- Quote from: nctnico on June 02, 2024, 10:19:45 am ---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.

--- End quote ---
I respectfully remain unconvinced.  I think you have convinced yourself of an advantage that is not there.

--- End quote ---
You are allowed to have your own opinion. I'm sorry I can't explain the advantages of zooming out better (they are definitely real, like not having to think about the precise trigger point!) and you feel the need to go down the ridiculing path instead of just respecting other people's ideas even if you don't fully understand them.
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