@Asmyldof yeah, the more or less commercial copper plating all seems to be mostly sulphuric acid based. also, is the uk still in the eu or will it cost extra customs money? ^^
can anyone help me understand what this means: "Timebase Accuracy ±50 ppm measured over 1 ms interval" in an oscilloscope datasheet ( this one, page 4 )
the BK Precision 2190D has 100Mhz bandwidth, 1G samples per sec, or 500Ms/s in dual channel mode (which is how i'm using it). Which time value should I be applying the 50ppm to?
how would this reflect in measurements in terms of jitter?
i'm trying to understand how much jitter I am seeing in a signal (time between two rising edges, one on each channel) can be due to oscilloscope timing jitter
Can I assume the sample clock is 1Ghz, and the +-50ppm is that sample clock jitter?
seems like 50ppm of 1Ghz is pretty good, so i guess it's not what i'm seeing.
I am slightly confused about the relevance to jitter, afaik such accuracy specifications only tell how much off it can be from its true frequency, not how much it jumps arund within these borders
like, your clock could run at perfect 999.99995MHz with no jitter at all
So if you measure 1ms between two edges, you could be 50ppm off in that measurement, but in theory it could have 0 phase noise and be always that same 50ppm off all the time
I think there is somewhere an eevblog video aobut a pll programming bug in some rigol scopes where dave shows how small after the fix the phase noise really is
well the jitter in question, that I'm trying to check if the scope has anything to do with it, is in the order of +-7 nanoseconds. The scope has a time division down to 2.5 nsec/div, and it appears the accuracy is good enough that a whole bunch of samples taken comparing the difference between two signals leading edges shouldn't show any jitter from the scope
well i'm not talking about visible jitter of the waveform on the screen, i'm talking about timing error between two waveforms in the nanoseconds, which have leading edges about 720 nanoseconds apart, on two different channels
so if you do start/stop sampling, have the static waveforms on the screen, and do some t1 - t2 deltas
in any price range I would expect that for the smallest timebase settings you can see a stable waveform in a almost stable way. a pixel or two, maybe even three wobbling would be fine, but not multiple divisions
if i had a continuous signal might be able to see if my scope is doing like that rigol in Dave's video. In this case it's two channels of discontinuous signals with large delays between them (720ns) and the +-7ns jitter between the two signals rising edges is the thing i'm trying to measure (and determine if the scope is adding to that or not). There is a lot of stuff between the two reference signals that could be contributing to the jitter that are reasonable enough to make the jitter...
like an LED turn-on/off time, photodiode reaction speeds, TIA and second-stage amplifier phase delays/jitter and finally the comparator on the output with the 6mv hysteresis.
Get some clean signal of known good quality first, verify for your own well sleeping that you can't seeany jitter, then use the scope assuming there isn't any to measure your signal
yeah. Would measuring the same signal on both channels work? Wouldn't have the ~720 nanosecond difference between them but at least cross-channel jitter might become visible
if they are sampled sequentially there could be though right?
i don't think they are sampled concurrently, that's why the 1G/s goes down to 500M/s because it has to do two conversions one after the other on different channels
To be honest, you should not see any scope based "jitter" between signals, because a clock should be highly stable, meaning even if there is jitter, it should not be +100% to -100% between edges
When soldering SMD components, the 2-pinned ones (like resistors, capacitors, ...) are the hardest in my opinion.
I started long time ago with the 1206 format. Then scaled down to 0804, 0603 and finally I'm working with the 0402 ones.
I'm facing a new challenge right now. Once I get some flux on ...
@KyranF My interpretation is if the scope shows you a rising edge 1 ms after the trigger event, then the actual time that edge happened is between 0.99995 ms and 1.00005 ms after the trigger event. I don't expect this spec to tell you anything about jitter, more about the "long"-term accuracy of the timebase.
Jitter should be a separate spec, and the errors it causes are additive on top of the timebase accuracy spec.
I noticed you live in Netherlands, that makes you my neighbour. I live in Belgium (Leuven). In 3 weeks, I will also start as a freelancer. I'll build a lab too.
Props can mean compliment / respect / credit, for example:
Erika gets props for the great work she did on the music.
Wiktionary states that props is:
(slang) proper respect or proper recognition for another person; an expression of approval or a special acknowledgment; accolade or accol...
Many people don't need a jack-hammer, but a road-worker would have a sore day without one
What did you measure them with? If it was measured with a true RMS multimeter (most multimeters are, except the super cheap ones), then the value you measured is your RMS value. — Felthry9 mins ago
Anyone care to enlighten me as to when the market suddenly got flooded with actual true RMS meters?
@Asmyldof I think this person has just gone insane from exposure to reality, and has created a world of delusion where people do reasonable things like spending the extra dollar to actually measure the desired value, instead of measuring a completely different thing and making extremely unreliable assumptions about it having a relationship with the desired measurement.
Since, you know, there's enough food for everyone and the purpose of money (to decide who starves) is obsolete and so spending an extra dollar isn't the difference between life and death but getting a voltage 10% wrong possibly could be
It's a very logical delusional world to create for oneself
I'm more concerned with the illusion that this person seems to have with everything being printed on every multimeter being true, that might be just as lethal
So while I agree it's dangerous, I can understand the user's sentiment in choosing to live in that delusion. It's fucking infuriating that any meter would lack a reasonable RMS measurement when sufficient hardware costs less than the enclosure and user interface
At the very least, have a mode that spends a few seconds taking a good RMS reading for a steady wave
Sampling of signal to include sufficient RMS of square waves, especially up to 10kHz or so isn't "dirt cheap" in comparison. Nor is the extra calibration process
That's going from standard DMM chips to customised embedded.
@MickLH If you want true RMS you need wave shape information. Wave shape agnostic would be what multimeters tend to call RMS measurements and can be off by as much as 30% on certain wave shapes
While that's true for Fluke and Keysight, and indeed, they have more and more True RMS and less and less non-so, it's very untrue for any mfg that doesn't do "exotics"
Because the majority of people will buy it and read "RMS" and be happy and it only costs $2 to build
It's sad that legislation is unskilled. It's really about as bad as writing "non-toxic*" on a bar of soap and then in fine print having "* actually is toxic to ingest"
Anybody want to play Root Cause Analysis? I have an LTC2640 DAC, and the output is not equal to the reference voltage times the programmed code divided by 4096. Any spitballs what is wrong?
:37120727 For example, I program it to mid-scale (2048 counts). I measure the reference voltage (external reference) as 4.269 V, output voltage 0.201 V.
@Asmyldof This is the main one I haven't eliminated. Unfortunately it's write-only SPI, so I can't verify that what I wrote is what the chip received.
So it's a bit tricky. The reference is the divided down output voltage of a voltage regulator. The output connects to the feedback pin of the regulator. I have 4x this circuit on my board, and only two fail.
Also I had no problems on the two Rev 1 boards I built. This is the first Rev 2 board.
If I start stepping up from there, the regulator output doesn't change for a few steps...then it will randomly change to some other value than what I expect for the code I just programmed....then be stuck for a few more changes...then change again to another random value.
@Marla I checked and the load current is less than 1 mA.
When debugging issues with our high performance software I tend to log debug statistics and whatnot in megabytes per second and then start verifying them step by step until I find an anomaly... I woild apply a similar principle here
its done in our household like, once a year probably
@ThePhoton I haven't checked the datasheet, but you haven'tl ike, loaded it down or so? maybe a wrong resistor at the output? Tried measuring it with the output disconnected to the rest?