Products > Test Equipment
REVIEW - Rigol DS2072 - First Impressions of the DS2000 series from Rigol
ve7xen:
--- Quote from: XaS on June 05, 2013, 01:03:35 pm ---Thank you all for checking, it seems to be solved in 01.00.00.03 indeed. I couldn't find this particular problem in the first post, that's why I asked here. It seems like this wasn't discovered so far.
--- End quote ---
I noticed it, but didn't think it was a bug. Since turning measurements on/off is so unergonomic I just thought it was expected behaviour. Nice to see they fixed it, I hadn't noticed yet.
I'd still prefer pressing a measurement that already exists to toggle it off and not give a useless error on screen, going into the measure menu is cumbersome when they've got a dedicated always-present menu just for measurements.
Ruben57:
I’ve encountered a problem with my DS4024 which is similar to problems people have had with their DS2000 series. After reading through this thread (79 pages!) I found out why my trial options disappeared overnight (I did a self calibration :palm:). Anyhow, I ‘understand’ the situation on the DS2000 series but I was wondering if there was something similar for the DS4000 series? I have looked around but can't find it anywhere.
Also, I found a minor bug with the DS4024 and was wondering if that bug was present on the DS2000 series as well, since they appear to share a similar platform. Paul Price started a thread in the General Chat section and I detailed the bug in that thread, so rather than repeating it here you can read it there.
https://www.eevblog.com/forum/chat/rigol-ds4024-sweep-behavior/15/
There is also an odd display characteristic on the DS4024, which is detailed in that thread. Does the DS2000 series also behave like that?
marmad:
--- Quote from: Ruben57 on June 06, 2013, 02:19:28 am ---I’ve encountered a problem with my DS4024 which is similar to problems people have had with their DS2000 series. After reading through this thread (79 pages!) I found out why my trial options disappeared overnight (I did a self calibration :palm:). Anyhow, I ‘understand’ the situation on the DS2000 series but I was wondering if there was something similar for the DS4000 series? I have looked around but can't find it anywhere.
--- End quote ---
I don't know about this - I haven't heard anything one way or the other.
--- Quote ---Also, I found a minor bug with the DS4024 and was wondering if that bug was present on the DS2000 series as well, since they appear to share a similar platform. Paul Price started a thread in the General Chat section and I detailed the bug in that thread, so rather than repeating it here you can read it there.
https://www.eevblog.com/forum/chat/rigol-ds4024-sweep-behavior/15/
--- End quote ---
I just tested at 200ms/div, trigger position at 1.414s (see attached image) - no problem.
--- Quote ---There is also an odd display characteristic on the DS4024, which is detailed in that thread. Does the DS2000 series also behave like that?
--- End quote ---
Yes, the DS2000 does the same, but it's clear to me what Rigol are doing. It has to do with intensity grading/persistence: extend the 'Display' menu, and watch the 'PersistTime' selection when you switch from 100ms -> 200ms - it grays out - meaning it's no longer active above 100ms. At <= 100ms/div, the Rigol is capturing full screens of data so that they can be combined into the intensity/persistence map (impossible to do when 'rolling'). Whether you like this behavior or not is a question of preference, but that appears to be why they're doing it.
jamesb:
I just recently received my DS2202 and I'm loving it so far!
Thanks for all of the information in this thread - at well over 70 pages, it seems I've got some reading to do :)
When I first bought the scope, I (not knowing any better) did a self-calibration but somehow did not lose the trial licenses. I'll be sure to check what firmware version I've got but my suspicions are that it is the 01.00.00.05 version.
Man .. what a difference from my dying Tek 465 !! This thing is simply unbelievable!
mklimasz:
Hello
This is my first post in this blog, so if I miss something or misread the (lenghty) thread then please just point me to the right source. I have found some posts regarding the subject of my interest, but found no definite answer to my questions... In particular: Will that scope fit into the job?
I'm planning to buy a scope (DS2072?) for hunting signal instabilities (phase shifts, glitches) in AVR applications. Having said that, the primary signal sources would be non-periodic transmission bursts, carried directly between peripherals or via serial line buffers & cables, of a carrier certainly not more than 10MHz (with possible extension towards 20MHz in the future). I expect these to be pretty stable (as I've taken every effort possible while designing the circuits, and also keeping the transmission rates sane) but want to make sure what's really happening and how far from instability the circuits are. I'm wondering (as already stated above) if that scope would fit in. I already asked the distributor (I live in Poland) to setup the test bench to check how capable in glitches-hunting the scope really is (signals of before-mentioned nature, testing for min pulse duration that would be consistently recognized as problem / triggered properly; also testing under which settings the detection would run best (wfs/s), and: how much amplitude / main waveform placement of the glitch is enough to get through triggering routine). Real life experience, however, may render different results, and that's why I'm interested in getting an independent opinion.
At the moment I think the most effective would be to trigger the scope whenever a pulse below certain duration is detected (while I can evaluate what to expect on the signal lines based on transmission parameters / clock of the core used), however that's the second question I'd like Your opinion about: Would that be a proper way of triggering, or my idea is not correct?
I'd really appreciate Your point of view, as I'd like to spend on a scope wisely (and, most preferably, only once). It may equally show that Rigol is enough or that I should still save more to get the right scope for the purpose...
Kind regards,
Michal
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version