Products > Test Equipment

A newbie needs some help with my first DSO

<< < (17/25) > >>

awakephd:

--- Quote from: egonotto on June 02, 2024, 12:49:59 am ---Hello,

It would be good if awakephd would say what signal sources he has available, so that you could suggest better experiments.

Best regards
egonotto

--- End quote ---

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.

Fungus:

--- 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...)

awakephd:
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). From where I sit (in a sea of ignorance!), I honestly don't see why this argument is so consuming. Despite many suggestions to the contrary, it is not clear to me - perhaps because of my ignorance - that one approach is superior to the other; they are simply different. Maybe each approach offers some advantages over the other ... but in the end it seems like arguing over a preference for apples vs. oranges.

One more time, I plead my ignorance - perhaps I just don't know enough to appreciate the finer nuances of the argument. From what I can see, you are all experienced users who are getting really good use out of your preferred scopes ... in which case, why give a fig if someone else prefers and is getting really good use out of a scope that does things differently??

KungFuJosh:

--- Quote from: awakephd on June 03, 2024, 12:39:19 am ---One more time, I plead my ignorance - perhaps I just don't know enough to appreciate the finer nuances of the argument. From what I can see, you are all experienced users who are getting really good use out of your preferred scopes ... in which case, why give a fig if someone else prefers and is getting really good use out of a scope that does things differently??

--- End quote ---

It's not you, none of their conversation belongs in this thread. I mentioned previously that the only thing that matters is as you said, learning to use the scope you have. Them debating different brand philosophies is completely useless, and counterproductive here.

bdunham7:

--- Quote --- author=nctnico link=topic=430231.msg5527699#msg5527699 date=1717337486]
allows me to not having to think about how to setup the scope precisely to capture what I need...

--- End quote ---

Yes, you're a fast-thinking knob twiddler.  That's not meant as an insult, just a humorous description of how I see a certain set of people whose brains appear to operate very differently than mine.  I can't operate a scope without knowing where the settings are at.  And yes, bad encoders enrage me just as much as anyone else.


--- Quote ---No matter what, the data I need is there

--- End quote ---

Unless it isn't.  It will be there if the record length at the scopes fastest undecimated sampling rate is long enough.  Otherwise it won't.  And on something like a 1M Megazoom scope at 2GSa/s, that's a half a millisecond.  Deliberately setting the timebase  (no zoom needed if you don't like it for some reason, such as the zoom window taking half the screen) to what you need will cause the scope to slow down the sample rate appropriately.  Possibly this isn't commonly an issue with your scopes as you use them, but it will come up in common uses using your technique.


--- Quote ---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. 

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