Hi All,
In the past when I would insert a USB stick with a DS2000 '.GEL' file the DSO would display the version number and prompt "OK" to install ,but now It will only prompt if it is a new FW version. see Pix.
Has anyone else seen this?
When I go back to older version (boot/help), I do not get the update prompt just the 'USB device detected'.
Also
Has anyone ever seen all:
100M
200M
300M Bandwidth options displayed like in Pix
marmad:
I would appreciate hearing more from you on the issues you had. Have you learned anything else since your experiences with the DS2000, FR v.3, and the 300MHz BW Option?
Thank you for any information you can add since your post in Reply 2524, Ted552
If you install the 300MHz option on a DS2000, your scope's rise-time is indeed lowered, however you also gain a fair amount of overshoot on pulses. The overshoot measured with a TEK 284 (70 pico sec. step) was in the order of 15%. So I decided that this is not acceptable for me, and turned it off.
marmad:
I would appreciate hearing more from you on the issues you had. Have you learned anything else since your experiences with the DS2000, FR v.3, and the 300MHz BW Option?
Thank you for any information you can add since your post in Reply 2524, Ted552
[Additional]:
Now, in terms of the continual hanging problem - I haven't seen it happen again since I removed the 300MHz option and downgraded to v.2 - then upgraded back to v.3 later after my work was done. But I was working with Roll mode and some rather atypical settings - so it's possible that the same settings with v.3 but without 300MHz would also cause the hanging - I just haven't been able to reproduce it since. So at this point, it's unknown if it's just a bug that exists in v.3 with certain settings - or is linked to 300MHz option being installed. But I have to say, before I ever began using the 300MHz option, the DS2000 crashed or hung fairly infrequently - but it's happened many more times with it installed. But more info is definitely needed to pinpoint the source of this problem.
If you install the 300MHz option on a DS2000, your scope's rise-time is indeed lowered, however you also gain a fair amount of overshoot on pulses. The overshoot measured with a TEK 284 (70 pico sec. step) was in the order of 15%. So I decided that this is not acceptable for me, and turned it off.
this 15% more overshoot is from the 200MHz set DS2000, but until you know what the rise signal should look like ( measured on a much higher bandwidth scope ) then maybe seeing an overshoot increase is actually right ? the lower bandwidth just wouldn't have the ability to capture it ?
this 15% more overshoot is from the 200MHz set DS2000, but until you know what the rise signal should look like ( measured on a much higher bandwidth scope ) then maybe seeing an overshoot increase is actually right ? the lower bandwidth just wouldn't have the ability to capture it ?Not in this case; the Tek 284 has no overshoot and a rise time of 70 ps.
"Which is Better??? "
"Which is Better??? "
As you can see by the flat traces that I manually created the data for the waveforms and re-loaded the sample data into the DSO and the DSO created the Traces, always with SinX/X interpolation.
1. In the first display the sample data is at one level and then jumps to the Higher level in one sample period (500ns).
NOTE how the SinX/X interpolation displays a pre and post step ringing.
To explain in more detail. I saved a waveform file from the DS2000 (at 140pts/disp)) to a USB Stick.
I then transfered this file to a PC. I then used a Hex Editor to put in the Sample data into the files that I wanted the DSO to Display. , There is NO real voltages measurement Data.
I set the first 70 data samples for 1 div above the bottom of the display
then
I set next 70 data samples for 1 div below the top of the display.
I then loaded the waveform file into the DSO (w/USB)
The ringing you see is the result of the DSO trying to make a sine wave with the SinX/X interpolation function.
2. In the second display the step change of level was created for a smoothly change to resrtiction the SinX/X effect.
See the Dot Samples in this Display.
You can see the Dots are a gradual curve at the bottom and top of the Step change in the Sample Data.
I think a lot of the overshoot when displaying a step change is the SinX/X function. A user has to look at where the sample dots are to determine if there was a real indication of overshoot.
The #1 display shows a 10% overshoot when there was absolutely Zero overshoot !
As for the Front end BW of the DS2000 we know that there is a Programmable BW Amplifier that has the selections of 20,100,200,350,650 and 750 MHz so I assume 300MHZ option opens up the BW to 350MHz
This is NOT due to Sin X/ X interpolation. Besides that, the sin interpolation is only done between sample points.....
The first picture in this post was done running the scope bandwidth at 200MHz. you can already see how much overshoot it has. Test done at 300MHz show even more overshoot. NOT due to sin interpolation.
.......
So as far I'm concerned this myth has been busted for the DS2000 series
Thanks Orange.
I think you tested on the DS2072 Non-A , with older Firmware
My displays indicate nothing about the Analog specifications of the DSO.
Yes the vector display follows thorough the sample points and (SinX/X is used between data points)
I may have missed the post, is there any difference in the front end of the DS2000A to improve the spec.? (higher BW) Although the latest FW allows the option for DS2302 (300MHz), was there any changes to the frontend in the DS2000A hardware for a faster response (with what overshoot??)
Besides Rigol sales , I doubt anyone has both DS2000 and DS2000A to do a test with same pulse.
and with only a few sample points/div I think it would be hard to determine any difference when testing at the limits of the DSO specifications.
Just thinking,why I like 1ns/div? I am old and slow to multiple by 2, for 2ns/div
Well that's a good question. I would assume that Rigol has adapted the front-end of the new DS2000A to compensate for the excessive overshoot with the 300MHz model. But I don't know for sure, I don't own one.
@ Othello
You may wish to check the full firmware Version (see 3rd post here for - F7 F6 F7 Util)
if you are at 00.00.01.00.05 then Yes update FW
See bug list ( post #3). you can always go back.
On a lighter side
A Rigol tames a wild One yes wild
@Teneyes: I am guessing you live in the toronto area.
@Teneyes: I am guessing you live in the toronto area.
I think he's about 4000km west of Toronto.
On a lighter side
A Rigol tames a wild One yes wild