... they have an offset of 3-4 mV on that scale (0,3-0,4 of div) ...
... they have an offset of 3-4 mV on that scale (0,3-0,4 of div) ...
Well, an Oscilloscope isn't made to measure voltages. It's made to show you voltage characteristics.
Cheers
hammy
I know how to use scope for quite some time, and I do measure voltage with my 6.5 digit voltmeter when I need precision..
But you don't know that so I thank you for you just being friendly and trying to teach me..
Please correct me any time if I don't make sense in the future too....
I know how to use scope for quite some time, and I do measure voltage with my 6.5 digit voltmeter when I need precision..
But you don't know that so I thank you for you just being friendly and trying to teach me..
Please correct me any time if I don't make sense in the future too....
No offense intended!
I see your point ...
You did it correctly. When you "delete" number 3, it's just grayed out. If you add the same one again, it's just re-enabled in the same location. If, instead, a new one is enabled, then the others shift to replace the grayed out ones and the new one is added at the end. I guess you could call the behaviors enable/disable/replace -- no delete.
... they have an offset of 3-4 mV on that scale (0,3-0,4 of div) ...
Well, an Oscilloscope isn't made to measure voltages. It's made to show you voltage characteristics.
Cheers
hammy
How do I completely clear a measurement? I was trying to set my scope to duplicate some of the setups here and if I pressed the wrong measurement, I can't figure out how to make it go away completely. If I delete it, it stays grayed out and a new measurement will just be added.
Long-pressing the 'Measure' button clears all the measures :-)
But here is a screenshot I sent to Rigol (and got no reply ) . All three channels are connected to the compensation terminal, are all identical probes, etc. The only difference is V/div. This is more than a 400% mistake. Does that fall under the definition of "precision" or "accuracy"? I don't think so. I call this a Bug.
Long-pressing the 'Measure' button clears all the measures :-)LOL as soon I get to lab I'm gonna try it... Epic...
Long-pressing the 'Measure' button clears all the measures :-)LOL as soon I get to lab I'm gonna try it... Epic...
I read that in the manual now, press and hold measure to clear all measurements. But if you enable one (I enabled the last one), they all come back grayed out, except the last one enabled. The same thing if I use the All Items Delete button. So how do I get rid of them all and just enable only one again, without excess grayed out clutter coming back?
But here is a screenshot I sent to Rigol (and got no reply ) . All three channels are connected to the compensation terminal, are all identical probes, etc. The only difference is V/div. This is more than a 400% mistake. Does that fall under the definition of "precision" or "accuracy"? I don't think so. I call this a Bug.
BTW, this signal has some jitter and the voltage spikes you see are real. Vrms seems off.
BTW, this signal has some jitter and the voltage spikes you see are real. Vrms seems off.
What happens if you look at "Per.RMS" instead or put a decent number of waveforms on screen?
But here is a screenshot I sent to Rigol (and got no reply ) . All three channels are connected to the compensation terminal, are all identical probes, etc. The only difference is V/div. This is more than a 400% mistake. Does that fall under the definition of "precision" or "accuracy"? I don't think so. I call this a Bug.
The scope specs are rated full scale. If I had a 160V full scale panel meter and fed it 3V, how much absolute error would you expect on that voltage reading? Then it's digital 8 bit with a resolution of 1 bit and consider there is real analog noise, what voltage range are we talking now? Now take that figure and perform some floating point math and see where we are.
I'm not saying the scope is right, but I also think we should keep some things in perspective.
I'm not saying I'm an expert either, but is anything in my screenshot out of spec?
I understand what you folks are saying, but is the number outside the specification? I showed that the same measurement set up more reasonably is within spec. It's the same signal and same measurement.
If you take your trusty high accuracy DVMs and feed them 0.01 volts and have it set to a 100+V range, are you going to complain if one meter says 0.01 and another is 400% off (0.04)?
I totally understand that it is a software bug and could be fixed, but if both channels were closer in value yet still just as far off, then what? It's in spec! (I think anyway...)
I understand what you folks are saying, but is the number outside the specification? I showed that the same measurement set up more reasonably is within spec. It's the same signal and same measurement.
If you take your trusty high accuracy DVMs and feed them 0.01 volts and have it set to a 100+V range, are you going to complain if one meter says 0.01 and another is 400% off (0.04)?
I totally understand that it is a software bug and could be fixed, but if both channels were closer in value yet still just as far off, then what? It's in spec! (I think anyway...)
I said I understood it was a bug, but what real world measurement fails for you, that is my point? It's a nice anecdote; however, if you were really measuring low-level DC or noise in the low mv range, who would be setting the scale to 160V?
Of course, I could be wrong and this is certainly a nuisance, but I've found it's best to use equipment in ways that enhance its performance rather than in ways magnify its weaknesses. That is true for anything.
BTW, I think in single channel mode, the performance of the scope is outstanding, and that is why I think this bug is nuisance, because it certainly need not be this way.