Products > Test Equipment

REVIEW - Rigol DS2072 - First Impressions of the DS2000 series from Rigol

<< < (372/566) > >>

Carrington:

--- Quote from: marmad on December 13, 2013, 04:40:26 pm ---Thanks, JDubU. It looks more or less identical with HW v.1. I'm guessing, given their general design, they couldn't make it any better without some major changes. 160 - 230ns is certainly usable; if they would allow External Trigger to be a source to the other trigger types (for cross-triggering purposes), the slightly longer-than-normal delay would matter even less.

--- End quote ---

In conjunction with a LA that allows post/pre trigger this delay isn't a problem.

EV:
I installed BW 300M option to my DS2202. Here are rise time tests with Tek type 284 pulse generator.

In pic 1 I have used BNC cable with 50 ohm feed through terminator. Rise time has changed from 1.4 ns to 1.2 ns and over shoot from 8 % to 10 %. It is not a big change.

In pic 2 I have used 10X probe with 50 ohm feed through terminator between probe tip and generator output connector. Rise time is about 1 ns and over shoot 17 %.

AndersAnd:

--- Quote from: EV on December 14, 2013, 08:08:30 am ---I installed BW 300M option to my DS2202. Here are rise time tests with Tek type 284 pulse generator.

In pic 1 I have used BNC cable with 50 ohm feed through terminator. Rise time has changed from 1.4 ns to 1.2 ns and over shoot from 8 % to 10 %. It is not a big change.

In pic 2 I have used 10X probe with 50 ohm feed through terminator between probe tip and generator output connector. Rise time is about 1 ns and over shoot 17 %.
--- End quote ---
What HW version does your DS2202 have?

EV:
It is HW1, picture is before updates.


--- Quote from: AndersAnd on December 14, 2013, 03:03:40 pm ---What HW version does your DS2202 have?

--- End quote ---

dschnell:
Hi,

watch out, first post  ::)

After reading (almost) completely the 2 main threads about 2072 I finally bought a 2072 used. I upgraded all options with the already installed latest 1.X fw, then upgraded to newest 2.X firmware via bootloader method but _without_ uninstalling upgraded options (but with FRAM reset), then installed all 2.X available options and now have "non-standard ;)" 200M + 300M options installed.
Otherwise just minor hassles: first reboot after fw upgrade: no go, installed again newest fw, again FRAM reset: it finally booted up, installation of newest options via riglol codes then went without any glitch.

Do I have to expect unusual behavior because of the activated 200M+300M options ? I played around and haven't seen any strangeness because of that. Then again: this is my first scope and I am just an embedded SW engineer interested in hw, so probably I could not recognize :-//.

Anything special I should examine a used scope for ?

Next question: I am on a MAC. Is there any tool I could use on that platform to remote control the scope or do I have to run some Windows VM?

Navigation

[0] Message Index

[#] Next page

[*] Previous page

There was an error while thanking
Thanking...
Go to full version
Powered by SMFPacks Advanced Attachments Uploader Mod