Great
Marmad, you know if someone has tried to establish a BW of 300MHz by SPI command?
And this BW was verified?
Thanks
Perhaps, and -3dB @ 233MHz is due to the combination of LMH6518 @ 350MHz and the response of the stages before the LMH6518.
In such case would interesting change the MMBFJ309, N-Chanel RF Amplifier, by another similar with better frequency response.
We only need sniff the SPI of the LMH6518 to check it. Has anyone done that yet?
Hi all,
Is this a bug.....or is it just me intepreting the scope wrongly.?
DS2072 (FW v.01.00.00.03)
- Turn on both channels, probe a couple of different DC voltages.
- Whilst Ch.1 selected go to Vertical menu and select Vavg (yellow). Ch.1 Vavg is now displayed at bottom of screen in yellow.
- Select Ch.2 and go to Vertical menu and select Vavg (blue). Ch.2 is now displayed at bottom of screen in blue.......however, Ch.1 which is still yellow now reads same voltage as Ch.2.
I was looking to have Ch.1 & Ch.2 Vavg at bottom of screen. Whatever I do both the Vavg's at the bottom of the screen always read the same voltage.
PS. If use the DISPLAY ALL function under MEASURE both the V.avg's are displayed correctly in the pop-up.
Ian.
Read the first post of this thread, all the bugs are listed....
And yes it was a bug, solved in the latest FW, you can download on the first page.
I think there are similarities with this:
...
See Q01_1 at page 2, and other small changes to get 200MHz of BW.
...we could get without much difficulty A BW of 300/400MHz...Whatfor? The scope has not been calibrated for this. Maybe a 70Mhz scope was only calibrated for 70 Mhz so even 100 or 200Mhz measurements are not valid...
...we could get without much difficulty A BW of 300/400MHz...Whatfor? The scope has not been calibrated for this. Maybe a 70Mhz scope was only calibrated for 70 Mhz so even 100 or 200Mhz measurements are not valid...Nonsense! The hardware and firmware are identical between the 2072, 2102, and 2202 models. The only difference between models is the entry of a key(s). Many folks here have done exhaustive testing prior to and after applying these keys and have proven this to be fact. I just received my 2072 today and have done some basic tests for myself all of which have tracked the others work just about perfectly. If you go thru the couple of threads regarding the 2072, you can see some excellent plots done by Wim13 showing the vertical bandwidth past 400 MHz.
....
I think it's a bit too early to state that. We have no knowledge that Rigol has calibrated a 2072 for anything higher than 70 MHz (we don't know what their process is in production). Just because you can see stuff visually up to the -3db drop, doesn't mean it's accurate.
re: anti-aliasing having no effect.
I beg to differ. Try the FFT function, with and without AA.
It seems to limit something or other.
Have noticed from videos of people ds2xx2 that all earlier shipments come with switchable x1 x10 probes. Some people mention 350MHz bandwidth. Well my scope came with x10 non selectable , rigol info sheet says 300MHz bandwidth. Now I've got other probes for accessing the 500uV setting, but who else has the x10 only probes ?
--
Darryl
Have noticed from videos of people ds2xx2 that all earlier shipments come with switchable x1 x10 probes. Some people mention 350MHz bandwidth. Well my scope came with x10 non selectable , rigol info sheet says 300MHz bandwidth. Now I've got other probes for accessing the 500uV setting, but who else has the x10 only probes ?
I tried several times, first just the DSA9 key, then the DSAR followed by DSA9 keys but it still stayed a 2072
Another thing I noticed - maybe already known and not a bug.
In 500uV/DIV mode, the scope is internally set to 1mV/DIV and the data scaled by a factor of 2. This can be noticed when reading out the waveform data. The LSB is always 0. This effectively reduces the ADC resolution by 1 bit / dynamic range.