| Products > Test Equipment |
| REVIEW - Rigol DS2072 - First Impressions of the DS2000 series from Rigol |
| << < (499/566) > >> |
| Teneyes:
@Nikwing You may wish to try Limit BW to 20MHz to limit the noise. and I think you will need an Amplifier to boost the 5 mv Note to All: my displays of Cardiac pulses are from a Rigol DG4000 , using 16000Pts Arb Function (built in). All displays captured easily with Marmad's RUU (a Plug) |
| Purevector:
I think I may have found a bug. Since upgrading to 3.00.01.03, whenever I plug in the scope, it automatically powers up. Before it just used to fade the power button. The power mode in the settings is Default, not Open. I did try both. Going back to V2 did not fix the issue. When I turn the scope off and unplug it it takes a few seconds for the power led to completely turn off. If I then plug the unit in, it boots up on its own. |
| Galaxyrise:
--- Quote from: NikWing on June 19, 2014, 04:34:51 pm ---the 2nd problem is about measuring. I try to measure/calibrate an ECG circuit, setting it to 5 mV/DIV. If I don't use high res, it's really impossible to measure anything. --- End quote --- You shouldn't have a "fat" trace at 5mV/div (it should be about 1/10 a division.) If you unplug everything from the scope, is the trace still fat? If not, then you're letting noise in from somewhere and should adjust your measurement setup. It's pretty easy to pick up 5mV of noise. How large is the signal you're looking for? In general, if you're trying to measure anything smaller than ~2mV you should either be measuring something slow enough that you can use hires (I've captured a 100uVpp ripple this way) or you should use a preamplifier (and everything being amplified has to be super low noise.) --- Quote ---increasing the time base to something like 10 ... 100 ms/DIV makes the DSO totally slow, no matter what sample memory I select (the lesser the memory, the weaker the visibility of the curve on the screen) I still remember my old HP DSO which was nothing compared to the Rigol and I was able to measure and display what I wanted to. What do I have to do to get a nearly clear curve on screen? I can't see an ECG curve on the Rigol because it refreshes so slowly :/ --- End quote --- 100ms/div means 1.4s per capture. Has nothing to do with memory depth! You have a couple of avenues to make your life easier here, but these time bases are always a bit clumsy because making adjustments (like vertical offset) clears the screen. 1) As others suggested, use roll mode. This is what I usually do for my slow measurements (and I've had it all the way to 1000s/div!) Hires is really good in roll mode. 2) Set the trigger point to exactly the left side of the screen. In normal y-t mode, the scope needs to have captured enough data to fill in from the beginning of the waveform to the trigger before it can actually trigger. So if your trigger is in the center of the screen, and you're at 100ms/div, then the scope needs to have 700ms of data before it can arm the trigger. By moving the trigger point to the left of the screen, the trigger can arm "immediately" after the previous waveform is captured. When the time base is slow enough, the scope will even display the in-progress waveform, making it feel a lot more responsive. |
| jlmoon:
Hello, I know this might be a bit off topic, since we're discussing the 2000 series scopes, Has anyone noticed any vertical amplifier offset (no signal applied with 50 ohm termination on input AC or DC coupling selected) in the range of 100 - 200 uV when in the 500uV / div range. I also noticed that channel 1 has a bit more than channel 2. My particular model is a DS2202, are we splitting hairs with a Chinese scope playing in the grass? |
| marmad:
--- Quote from: Galaxyrise on June 23, 2014, 06:53:44 pm ---1) As others suggested, use roll mode. This is what I usually do for my slow measurements (and I've had it all the way to 1000s/div!) Hires is really good in roll mode. --- End quote --- Peak detect is also very handy in roll mode. --- Quote ---2) Set the trigger point to exactly the left side of the screen. In normal y-t mode, the scope needs to have captured enough data to fill in from the beginning of the waveform to the trigger before it can actually trigger. So if your trigger is in the center of the screen, and you're at 100ms/div, then the scope needs to have 700ms of data before it can arm the trigger. By moving the trigger point to the left of the screen, the trigger can arm "immediately" after the previous waveform is captured. When the time base is slow enough, the scope will even display the in-progress waveform, making it feel a lot more responsive. --- End quote --- This isn't precisely correct (although it works this way in many circumstances). In Y-T mode, the DSO captures the pre-trigger buffer data from the beginning of sample memory to the set trigger position - but sample memory doesn't always correspond to screen memory (what you see on the display). That's why there's the bar above the screen center - to show you how much of sample memory you're seeing - and your trigger position within it. In the attached screenshot, I have my trigger position set to screen left as you suggest - but it would still take 7 seconds before the buffer is filled (and I would start to see the trace). So you have to keep an eye on the location of your trigger position within the current sample memory depth - not just the screen memory. |
| Navigation |
| Message Index |
| Next page |
| Previous page |