-
RE: Programmable oscilloscope MSO64B can't read HardCopy screenshot data,but MDO3054 can do it
Hi Sunny,
HARDCOPY
has been deprecated in the newer scopes, you should useSAVE:IMAGE
andFILESystem:READFile
instead. -
RE: Oscilloscope Series 6
Hi Om,
How long do you want to capture for and at what sample rate?
Oscilloscopes aren't really meant for long "continuous" acquisitions, so I would suggest you look into using the FastFrame functionality on your machine to take your measurement.
Not quite sure what you want to do with your coincidence window, could you explain that further? -
RE: Flatness Verification for Oscilloscope TDS 5052
Hi Denis,
Page 4-27 of the service manual contains the procedure for bandwidth testing, that's the only flatness we specify.
If you'd like to test to a higher spec then you can modify the test for your needs. -
RE: MSO58B Program issues (can not change Reference Level--Set Level in absolute) with python
Hi Cheng,
I would suggest tryingMEASU:MEAS1:REFL:METHOD absolute
-
RE: Single Cursor Measurement Uncertainty and Determinining Sample Rate
Hi John,
The manual specifies the delta time measurement accuracy at full bandwidth for single-shot sample mode to be: +- (1 sample interval + 50 ppm x |reading| + 0.6 ns).
You are correct that the sample interval is 1/sample rate, and the sample rate is set by the user. The scope has a record length of 2500 samples, if you set the time/div to 100 ms/div, and considering there are a total of 10 horizontal divisions, then we have 2500 S / 1 s = 2.5 kS/s, so your sample interval is 400 us. -
RE: Low-frequency triggering
Hi Jessalyn,
What are your trigger and horizontal settings? Would you be able to share a picture of those menus?
More information on the waveform you're trying to trigger on would be useful tool. -
RE: Channel RMS measurement different from DVM AC RMS Measurement on MDO3024 Scope
As Alan said, the hardware DVM will have significantly lower bandwidth than the scope, so that's a possible source of error.
Another source would be the fact that you're averaging a noisy signal. which inherently changes your measurement as the noise is part of your signal and counts to RMS too.
I also see some very fast spikes on your averaged waveform, which could be an artifact of trigger jitter+averaging which will affect your measurements.
The DVM measurement is done through hardware similar to digital DMM. It's inherently much lower bandwidth than the scope channel.
It also runs independently of the acquisition hardware, it's a live read of what's on the channel at that moment, not what was on it during the last acquisition.
The other measurements are calculated after the signal is captured by the ADC and processed (for your example, in your case, the waveforms are averaged before measurements are taken) and are calculated again when a new acquisition is displayed.
So there are, at least, 3 ways in which the measurement and DVM systems work that could explain the discrepancies you're seeing: bandwidth, post-processing and triggered/free run. -
RE: Download data directly from scope
HI Anirudhh,
You have a few options:
1) The free basic tier of TekScope.
2) The free community made TekScope Utility. -
RE: Has anyone edited arbitrary waveform of AFG1062 in C++?(by using DATA:DATA EMEMory)
Hi Du,
I've attached my example Python script for sending waveforms to the AFG1k, let me know if you have any questions. -
RE: Channel RMS measurement different from DVM AC RMS Measurement on MDO3024 Scope
Hi James,
There are countless things that could cause this issue, here are just a few:
1) Are the "true RMS" DMMs? If not, their RMS readings may only be valid for specific waveforms.
2) Are your probes properly compensated?
3) What's the bandwidth of your signal? DMMs don't measure high frequencies well.
I'd need to know more about your signals to be able to help you narrow it down more.