Products > Test Equipment

A newbie needs some help with my first DSO

<< < (18/25) > >>

bdunham7:

--- Quote from: awakephd on June 03, 2024, 12:39:19 am ---All, I am very sorry to have kicked over what is apparently an old and hotly debated ant hill regarding memory and zoom and such.

--- End quote ---

It's actually worth discussing and if you can tolerate the squabbling and understand the issue, you'll probably gain something.  You appear to already have figured out what it is about in the general sense.  It's not like we're having fistfights here.

tggzzz:

--- Quote from: awakephd on June 03, 2024, 12:39:19 am ---All, I am very sorry to have kicked over what is apparently an old and hotly debated ant hill regarding memory and zoom and such.

I will repeat that as a newbie, I have no dog in this fight, other than seeking to understand how to use the scope I actually have (as opposed to the ones that I don't have which happen to handle things differently).

--- End quote ---

That's a very sane attitude :) Learn to use whatever tool you have to its best advantage.

Learning any complex tool takes time and energy; being simpler is an advantage of analogue scopes.

The number of people that have detailed experience of more than one similar tool is very limited. Various people have allegedly noted something to the effect that "academic fights are so vicious because the stakes are so small".



--- Quote from: awakephd on June 03, 2024, 12:23:56 am ---A very primitive signal generator (basic sine, square, triangle waves), plus whatever I can generate from an Atmel ATTiny84 or Arduino Nano, i.e, I2C, SPI, UART, plus PWM at various frequencies. And for a "real" test, I am planning to test and experiment with the effectiveness of basic R/C de-bounce filters on various switches.

--- End quote ---

That's an excellent cross-section :)

The debouncing should show an advantage of digitising scopes over analogue scopes. While it is possible to use an analogue scope, it is useful to be able to push the button many times and use infinite persistence to overlay multiple traces.

I'd regard I2C/SPI/UART as being more or less equivalent, and just use whatever's most convenient.

What you haven't explicitly mentioned is correlating two or more signals, e.g. time delays between signals, or triggering on the combination of several signals.

You might also like to explore signal integrity issues. Classic examples are poorly constructed (TTL) digital counters, or octal buffers driving a heavily loaded bus.

Have fun, whenever you can :)

nctnico:

--- Quote from: bdunham7 on June 03, 2024, 01:55:58 am ---
--- Quote --- author=nctnico link=topic=430231.msg5527699#msg5527699 date=1717337486]
Along a similar line you can argue that the history buffer is a useless feature / gimmick because the same can be accomplished using segmented recording which also allows finer control over the precise number of segments.

--- End quote ---

I would actually agree with that and don't find much utility in having the history buffer as a default.  I'm especially annoyed that the SINGLE mode on my SDS2354X+ wipes appears to wipe out the history so you always only have one capture.  It might be occasionally useful to take repeated single captures and save them all.  In fact you can easily do this using the EXT TRIG and a pushbutton.  So while I don't find the SINGLE memory management to be as appalling as you do, Siglent and it's proxies and proponents here have to reckon with the fact that they've not implemented a useful alternative system.

--- End quote ---
On the R&S RTM3004 it is implemented the same. Each press on the single button wipes the history. I don't quite see the logic in doing this either but maybe it is done to make sure each capture is made using the exact same configuration. However, on the R&S scope there is a setting to tell how many captures need to be taken in single mode before the entire acquisition 'session' is completely over.

Electro Fan:

--- Quote from: Fungus on June 03, 2024, 12:38:32 am ---
--- Quote from: 2N3055 on June 02, 2024, 12:18:21 pm ---Why do you think you cannot move around captured buffer on Siglent? You can. Exactly the same as on any other scope.

--- End quote ---

But normally there's nothing there.

(unless you previously zoomed out, re-captured, then zoomed in again trying to remember the horizontal scale you were at before you did all that, yes, we got that...)

--- End quote ---

Not trying to debate, but I think Fungus’ comment is correct - yes?

Electro Fan:

--- Quote from: tautech on June 02, 2024, 08:57:30 pm ---
--- Quote from: nctnico on June 02, 2024, 02:11:26 pm ---I know the zoom window can be used for even finer control but that comes at the price of needing to mess with 2 timebases and giving up what is most dearest to me on an oscilloscope: vertical space.

--- End quote ---
Here is where you are not fully conversant with Siglent DSO development, much different to how Zoom mode and memory management was implemented in the past.

Now when your fingers are on the timebase encoder Zoom mode is engaged with just a press, < not new, but toggling between windows in Zoom mode is just another press of the timebase encoder and in those models that offer memory management the main timbase can be zoomed out an order of magnitude more than most DSO's available.....while in Stop mode.

12bit SDS2000X HD, 8bit SDS5000X and all higher BW models have this capability which can negate the need for Zoom mode yet in Zoom mode the trigger point is always visible so to have a reference point when panning through a capture.

--- End quote ---

- is there a link to a video showing this? Thx

Navigation

[0] Message Index

[#] Next page

[*] Previous page

There was an error while thanking
Thanking...
Go to full version
Powered by SMFPacks Advanced Attachments Uploader Mod