Rigol DS1000z/2000/4000/6000 Waveform Capture Utility

[AlessandroAU]

I posted this Utility in the Rigol DS1000/DS2000 jitter thread and since it seemed to attract some interest I figured I'd start a new topic.

Its written in Labview so you will need the Labview RTE http://www.ni.com/download/labview-run-time-engine-2014/4887/en/

Looking at the VISA commands this should also be compatible be somewhat compatible with the entire DS series from Rigol. I would expect the Real-time Capture to have no issues but there may be problems with the Long Memory Capture on other models scopes (I am using a DS1074z). If you have a DS2000/4000/6000 please test this and let me know.


Current Version V2.2.3


Rigol V2.2.3

http://s000.tinyupload.com/index.php?file_id=90659414641703074947

Rigol V2.2.1:

http://s000.tinyupload.com/index.php?file_id=06194785972356290806

Rigol V2.2

Download Link: http://s000.tinyupload.com/index.php?file_id=16159701921368811937

Source: http://s000.tinyupload.com/index.php?file_id=05957966868497599811

Known Bugs:

Long Memory Capture only supports one channel at a time and trigger channel must be the same as capture channel. For now it is a good idea to disable other channels when using this.

Memory Depth setting is only updated when a new menu selection is made.

In real-time capture mode changing channel options sometimes results in a communication error, stop cont. sampling before changing memory settings to avoid this.

Waveform statistics cannot compute more than 3Mpoints of data (labview limitation) currently statistics are calculated from the first 50Kpoints to improve speed.

Rigol DS1074z Bugs:

Scope complains of 'Invalid Input' but processes commands anyway. (Perhaps I do not known the exact sequence it expects) commands work regardless.

When using :WAV:DATA? to request samples there is an upper limit of exactly 1179644 data points that can be downloaded at any one time requesting more points using :WAV:START and :WAV:STOP will result in a no data being returned at all.

Note this is when downloading the data as bytes ie :WAV:FORM BYTE, if using :WAV:FORM ASC (ascii) the limit is reduced to around 60Kpoints.

However it is possible to download the entire waveform memory in blocks and this is the technique I have used to download more than 1.1Mpoints.

[0ff]

Dear AlessandroAU,

your Utility seems to be quite cool!
Unfortunately, being on a mac I can't run your tool (as it's compiled for windows).

Would you be able to compile this as a mac app? (I don't know anything about labview, maybe you can just select this as output?)

Thanks in advance!

[pa3bca]

Hi AllesandroAU,
Unfortunately something broke between your original version and the latest (2.2). I cannot reproduce my original nice FFT.
I compared both versions with identical scope settings. (same as the one you re-published)
If I do a long mem capture (1.2 Mpts) the capture(buffer) in 2.2 is corrupt (see screenshot below).
Also the FFT is obviously incorrect (even when based on the capture buffer). See the other screenshots.
Also I see an almost permanent message on the scope screen: Parameter Limited! which indicates an input error.
(also did a long memory capture with 12 Mpts, with scope also on 12 Mpts settings, see below. no difference).

Do you need any more info from me to troubleshoot?

[AlessandroAU]

Hi AllesandroAU,
Unfortunately something broke between your original version and the latest (2.2). I cannot reproduce my original nice FFT.
I compared both versions with identical scope settings. (same as the one you re-published)
If I do a long mem capture (1.2 Mpts) the capture(buffer) in 2.2 is corrupt (see screenshot below).
Also the FFT is obviously incorrect (even when based on the capture buffer). See the other screenshots.
Also I see an almost permanent message on the scope screen: Parameter Limited! which indicates an input error.
(also did a long memory capture with 12 Mpts, with scope also on 12 Mpts settings, see below. no difference).

Do you need any more info from me to troubleshoot?

Very odd, it works fine on my unit.

Can you confirm the following happens:

1. Make sure only one channel is enabled and that the trigger channel is the same channel as which you are capturing from.

2. When changing the memory depth the number the change is reflected under the acquire menu on the rigol screen.

3. Does the run/stop button turn red during the capture and back to green afterwards

5. Does channel selection on the real-time screen work for you?

4. Does realtime and screen shot capture work for you?

Also do you have 12mpoints or 24mpoints option on your scope?

[AlessandroAU]

Dear AlessandroAU,

your Utility seems to be quite cool!
Unfortunately, being on a mac I can't run your tool (as it's compiled for windows).

Would you be able to compile this as a mac app? (I don't know anything about labview, maybe you can just select this as output?)

Thanks in advance!

Unfortunately I cannot compile it into a max executable as I don't have access to the OSX Labview Environment.

Possibly it may work in VMware?

[pa3bca]

Very odd, it works fine on my unit.

Can you confirm the following happens:

1. Make sure only one channel is enabled and that the trigger channel is the same channel as which you are capturing from.

2. When changing the memory depth the number the change is reflected under the acquire menu on the rigol screen.

3. Does the run/stop button turn red during the capture and back to green afterwards

5. Does channel selection on the real-time screen work for you?

4. Does realtime and screen shot capture work for you?

Also do you have 12mpoints or 24mpoints option on your scope?

1: One channel enabled, trigger on this channel
2:Yes, but only the first few times. After some buffer capturing all goes south, and nothing works any more (must restart scope and application te be able to capture again)
3:Yes
4:Realtime: Yes. Screenshot: No. Screen stays black. And after I try to get a screenshot I need to restart the application in order to be able to get a capture... (and realtime screen also fails).
After trying a few time I suddenly got a better result. See screenshot. Although even here there are serious glitches in the captured waveform. The FFT here however looks ok.
But right after that a next capture failed again.

Yes I do have 12 and 24 Mpts available. But same results here

[AlessandroAU]

Very odd, it works fine on my unit.

Can you confirm the following happens:

1. Make sure only one channel is enabled and that the trigger channel is the same channel as which you are capturing from.

2. When changing the memory depth the number the change is reflected under the acquire menu on the rigol screen.

3. Does the run/stop button turn red during the capture and back to green afterwards

5. Does channel selection on the real-time screen work for you?

4. Does realtime and screen shot capture work for you?

Also do you have 12mpoints or 24mpoints option on your scope?

1: One channel enabled, trigger on this channel
2:Yes, but only the first few times. After some buffer capturing all goes south, and nothing works any more (must restart scope and application te be able to capture again)
3:Yes
4:Realtime: Yes. Screenshot: No. Screen stays black. And after I try to get a screenshot I need to restart the application in order to be able to get a capture... (and realtime screen also fails).
After trying a few time I suddenly got a better result. See screenshot. Although even here there are serious glitches in the captured waveform. The FFT here however looks ok.
But right after that a next capture failed again.

Yes I do have 12 and 24 Mpts available. But same results here

What firmware are you running?

[pa3bca]

What firmware are you running?

Ooh old.. Software Version is 00.02.03.SP5
(nb: your v1 app runs perfectly every time)

[AlessandroAU]

What firmware are you running?

Ooh old.. Software Version is 00.02.03.SP5
(nb: your v1 app runs perfectly every time)

I'm running 4.00 so rigol may had made some changes to their firmware since then.

Can you try this Version?:

Rigol V2.2.1:

http://s000.tinyupload.com/index.php?file_id=06194785972356290806

[JDubU]

Mostly works on my DS2072 (HW v2.0, FW v00.03.01).

The only obvious problem that I noted on a quick test using the scope's 1KHz probe calibration square wave was that, in the Long Memory Capture, there is a large impulse-like discontinuity between each sample chunk.  It looks like the DS2000 scope wants total number of samples to be a 10x multiple of 1.4  instead of the DS1000's 10x multiple of 1.2.

[AlessandroAU]

Mostly works on my DS2072 (HW v2.0, FW v00.03.01).

The only obvious problem that I noted on a quick test using the scope's 1KHz probe calibration square wave was that, in the Long Memory Capture, there is a large impulse-like discontinuity between each sample chunk.  It looks like the DS2000 scope wants total number of samples to be a 10x multiple of 1.4  instead of the DS1000's 10x multiple of 1.2.

Can you through the ultrasigma control center send the following: WAV:START 1;:WAV:STOP 100;:WAV:DATA?

and paste me the result?

[JDubU]

Can you through the ultrasigma control center send the following: WAV:START 1;:WAV:STOP 100;:WAV:DATA?

and paste me the result?

-> :WAV:START 1;:WAV:STOP 100;:WAV:DATA?
<- (Return Count:112)
#9000000100ŽƒŽƒ†€ƒ~~‚}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}

Edit:
The result changes when command is repeated:
-> :WAV:START 1;:WAV:STOP 100;:WAV:DATA?
<- (Return Count:112)
#9000000100ŽƒŽƒ…€ƒ~‚}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}

-> :WAV:START 1;:WAV:STOP 100;:WAV:DATA?
<- (Return Count:112)
#9000000100Ž‚Ž‚…€ƒ~~‚~}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}

-> :WAV:START 1;:WAV:STOP 100;:WAV:DATA?
<- (Return Count:112)
#9000000100ŽƒŽƒ†€ƒ~‚~}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}

-> :WAV:START 1;:WAV:STOP 100;:WAV:DATA?
<- (Return Count:112)
#9000000100ŽƒŽƒ…€ƒ~~‚}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}

-> :WAV:START 1;:WAV:STOP 100;:WAV:DATA?
<- (Return Count:112)
#9000000100ŽƒŽƒ†ƒ~‚~}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}

-> :WAV:START 1;:WAV:STOP 100;:WAV:DATA?
<- (Return Count:112)
#9000000100ŽƒŽƒ…€ƒ~~‚~}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}

-> :WAV:START 1;:WAV:STOP 100;:WAV:DATA?
<- (Return Count:112)
#9000000100ŽƒŽƒ…ƒ~~‚}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}

-> :WAV:START 1;:WAV:STOP 100;:WAV:DATA?
<- (Return Count:112)
#9000000100Ž‚Ž‚†€ƒ~‚~~}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}

-> :WAV:START 1;:WAV:STOP 100;:WAV:DATA?
<- (Return Count:112)
#9000000100Ž‚Ž‚…€ƒ~~‚~}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}

[pa3bca]

I'm running 4.00 so rigol may had made some changes to their firmware since then.

Can you try this Version?:

Rigol V2.2.1:

http://s000.tinyupload.com/index.php?file_id=06194785972356290806

Same issues. The first time I power up your program it works ok (1.2 Mpts). Also on 12 Mpts.  There are a few glitches in the captured buffer but probably not enough to upset the FFT calculation.
But if I then try 24 Mpts I only get a flat line in the buffer window, and nothing in the FFT window. And then the 12 and 1.2 Mpts captures produce the same errors as can be seen on my previous screenshots (hickups in the buffer window, and FFT way off).
Screencapture still does not work. And after I try a screencapture the realtime display acts funny. Have to enable/diable it a few times for it to start again.

Also the scope's screen is flashing errors like crazy (all versions of them)
I have to restart both the scope and the program to get them to play nice again (but then only at 1.2 and 12 Mpts)

[nixfu]

I am just curious if you guys thank that this could replace the need to purchase an actual SA?

I have a DS1074z, and I need to maybe check some filter responses, and maybe look at RFI or such stuff, or even look for harmonics on a transmitter.

I have almost every piece of gear I ever have told myself I needed, except for an SA because they are soooo expensive compared to most other gear.

So, for a hobbyist can this replace the need for a SA for mostly simple stuff when combined with a good signal generator, and a DS10xxZ scope?

[pa3bca]

I am just curious if you guys thank that this could replace the need to purchase an actual SA?

I have a DS1074z, and I need to maybe check some filter responses, and maybe look at RFI or such stuff, or even look for harmonics on a transmitter.

I have almost every piece of gear I ever have told myself I needed, except for an SA because they are soooo expensive compared to most other gear.

So, for a hobbyist can this replace the need for a SA for mostly simple stuff when combined with a good signal generator, and a DS10xxZ scope?

Up to a point: yes. If you look at my comparison between the DSA815 and the FFT analysis you can see that up to say 3 MHz and -50dBm they are almost exactly the same. But further down in amplitude they begin to differ somewhat.
So i think that is useable as a SA substitute to possibly a few tens of MHz (remember the scope's BW is only 100 MHz and de sampling rate "only"  1GSa/s). And signals below say -50 dBm are also under suspicion. The scope's AD converters are only 8 bits, and by massively oversampling (say 12 to 25 MPts) you can up the dynamic range to possibly a practical 12 bits (I'm guessing here but the -70 dBm noisefloor of the FFT's seem to suggest this).
A real SA goes to at least 1.5 GHz (as my DSA815) and has a much larger dynamic range. the DANL is -130 dBm for the 815....

[AlessandroAU]

I am just curious if you guys thank that this could replace the need to purchase an actual SA?

I have a DS1074z, and I need to maybe check some filter responses, and maybe look at RFI or such stuff, or even look for harmonics on a transmitter.

I have almost every piece of gear I ever have told myself I needed, except for an SA because they are soooo expensive compared to most other gear.

So, for a hobbyist can this replace the need for a SA for mostly simple stuff when combined with a good signal generator, and a DS10xxZ scope?

Up to a point: yes. If you look at my comparison between the DSA815 and the FFT analysis you can see that up to say 3 MHz and -50dBm they are almost exactly the same. But further down in amplitude they begin to differ somewhat.
So i think that is useable as a SA substitute to possibly a few tens of MHz (remember the scope's BW is only 100 MHz and de sampling rate "only"  1GSa/s). And signals below say -50 dBm are also under suspicion. The scope's AD converters are only 8 bits, and by massively oversampling (say 12 to 25 MPts) you can up the dynamic range to possibly a practical 12 bits (I'm guessing here but the -70 dBm noisefloor of the FFT's seem to suggest this).
A real SA goes to at least 1.5 GHz (as my DSA815) and has a much larger dynamic range. the DANL is -130 dBm for the 815....

You must consider fft processing gain which is equal to 10log (m/2) where m is the number of samples. So the noise floor of the fft can actually reach that low (-130dbm)!

Edit: See Image

[pa3bca]

You must consider fft processing gain which is equal to 10log (m/2) where m is the number of samples. So the noise floor of the fft can actually reach that low (-130dbm)!

Yes theoretically. But -130 dBm starting from a cheap scope with an 8 bits ADC?.
The scope itself is 8 bits, so almost 50 dB dynamic range. To get to 130 dB you would have to get 200 Mpts (80 dB = 10 log (200x10^6  /2). Perfectly doable.
But... Using these formulas, with 24 MPts (see screenshots below) the FFT would add 10 log ((24 x 10^6)/2) = - 71 dB!
If all were perfect I would expect the noisefloor to be at -50-71 = -120 dB. I only see -80 (also at 200 MHz and there I would not expect to see any "real" signal out of the scope). So there seems to be 40 dB missing somewhere. I am no expert on FFT (calculations) so I do not have the answer to this puzzle.

Also if you look at the screenshots below there is a significant discrepancy after say 5 MHz. The FFT (with 24 MPts) shows peaks that are not there (according to the DSA815).
So the FFT is certainly usable as a substitute for an SA, but up to a point (obviously in frequency, but also in amplitude. Although I do not know how to discern where the useability ends...)
Rigol DSA815:

24 Mpts FFT from DS1074Z:

[JDubU]

Is that a new version of the capture utility that has been updated for DS2000 and DS4000?
Is there a download link for it?

[AlessandroAU]

Fair enough the dynamic range is not that high, but its definitely possible to have a noise floor at -130ish with 24mpoints (by zooming in). However I concede that the best dynamic range appears to be around 105dBm, which is still very good.

Also, just to show that is possible to take measurements exceeding 8 bits limit; Look at image 3, the scope is set to 5v/div or 40v max range. A 10mv pk-p signal is applied.

This is 20*log10(0.01/40) = -72db below full scale, a full 22db or so below the 8 bit resolution limit. Even though the waveform looks like barely like anything, thanks to the mathematics of the Fourier transform this signal is still measurable. Very neat!

Edit:
The tektronix MDO series also only uses an 8bit adc internally but has a DANL of -130dbm from 50khz to 5mhz (http://www.tek.com/datasheet/mdo4000/mdo4000b-series-datasheet-0) so it is definitely possible approach this kinda of performance with 8 bits.

also see: https://www.google.com.au/url?sa=t&rct=j&q=&esrc=s&source=web&cd=22&ved=0CC4QFjABOBQ&url=http%3A%2F%2Fwww.tek.com%2Fdl%2F48W-28882-2%252520%252520%252520MDO%252520Performance%252520WP_.pdf&ei=p_2YVOHwJcLZ8gWIsoKABg&usg=AFQjCNHaLpRkqk9Fxl4CPInDNz58hWFfLQ&sig2=vefpuXdZKo0KQWZVw9PI1g&bvm=bv.82001339,d.dGc&cad=rja

Just wanted to make people aware of this fact! I would trust the scope for use as an SA up to its bandwidth of 100MHz personally.

[AlessandroAU]

Is that a new version of the capture utility that has been updated for DS2000 and DS4000?
Is there a download link for it?

I am still working on support for other scopes, currently it is quite hard as I only have access to a 1074z. So far my program only detects which series scope is selected. It does not yet load configuration changes for the higher model scopes. If you have a ds2000 I could send you a WIP to try if you would like.

[JDubU]

I am still working on support for other scopes, currently it is quite hard as I only have access to a 1074z. So far my program only detects which series scope is selected. It does not yet load configuration changes for the higher model scopes. If you have a ds2000 I could send you a WIP to try if you would like.

I do have a DS2000 and would be happy to test a WIP.

[AlessandroAU]

I am still working on support for other scopes, currently it is quite hard as I only have access to a 1074z. So far my program only detects which series scope is selected. It does not yet load configuration changes for the higher model scopes. If you have a ds2000 I could send you a WIP to try if you would like.

I do have a DS2000 and would be happy to test a WIP.

Let me know if this version works for you:

V2.2.3

http://s000.tinyupload.com/?file_id=90659414641703074947

pa3bca, Please also try that version and let me know if it fixes any of the issues you were having.

[aroby]

I tried the prior version (2.2.1) with my DS2072A / DS2302A.  I had to manually enter TCPIP::10.10.10.45::INSTR in the drop down menu, but it was able to connect.  With 2.2.3, I do the same and just get Error in the Model Detected field.

Anthony

[AlessandroAU]

I tried the prior version (2.2.1) with my DS2072A / DS2302A.  I had to manually enter TCPIP::10.10.10.45::INSTR in the drop down menu, but it was able to connect.  With 2.2.3, I do the same and just get Error in the Model Detected field.

Anthony

I haven't implemented TCP/IP, can you try with usb?

Edit, Hang on, were you able to connect over TCP/IP in version 2.2.1 and download a waveform?

[aroby]

I haven't implemented TCP/IP, can you try with usb?

Edit, Hang on, were you able to connect over TCP/IP in version 2.2.1 and download a waveform?

Yes.  Just tried it again.  I can do a screen capture.  In the Realtime Capture tab, I can select channels, I can see a waveform (but it says "Input is invalid!" on the scope), if I change the scales on the scope, the graphs change.  On Long Memory Capture, changing the # of points gets reflected on the scope (albeit with the issues previously described).  When I hit Capture, the scope Stops, I get Input is invalid, and nothing gets displayed.

[aroby]

Just tried 2.2.3 with USB.  I can connect and it detects a DS2000 series.  I can change channels (although 3 & 4 are not present on the scope!).  I can't do a continuous sample and get a waveform - scope just displays input is invalid, changing the scope scales has no effect on the charts, I can't get a screenshot.  And when I exit, I get a dialog box saying Resetting VI: Rigol_Capture.vi, which I can only get rid of by killing the process.

So, for me, 2.2.3 is broken compared to 2.2.1

[AlessandroAU]

Just tried 2.2.3 with USB.  I can connect and it detects a DS2000 series.  I can change channels (although 3 & 4 are not present on the scope!).  I can't do a continuous sample and get a waveform - scope just displays input is invalid, changing the scope scales has no effect on the charts, I can't get a screenshot.  And when I exit, I get a dialog box saying Resetting VI: Rigol_Capture.vi, which I can only get rid of by killing the process.

So, for me, 2.2.3 is broken compared to 2.2.1

Its very odd that that real-time mode has broken, I have not made any changes.

I took a look at the ds2000 programming guide, looks like prehaps the ds2000 needs a few extra commands to get the memory buffer. Also removed a command from realtime mode, prehaps it will work now.

Also added a manual model override function. -so if you were using tcpip in version 2.2.1 it should work now provided you set the model. Actually I had no idea labview automatically handles VISA over TCPIP like that. So that's a win

V2.2.3.1

http://s000.tinyupload.com/?file_id=22255824192654410391

[Bud]

DS2072A

2.2.3 and 2.2.3.1 are unusable to me... The most I can get is a screen capture, and not always. In other tabs the program just freezes and I have to kill via Windows Task Manager

2.2 worked at least somewhat, I can make screenshots, in Real Time Capture it displays a static picture of waveform and FFT (no real time update), but in Long memory Capture just displays a straight line  in Waveform window. Anyway, 2.2 at least not freezing and does grab some data.

[Bud]

Just discovered something. If in 2.2.3.1 I select the device *and* set Manual Model Overwrite to DS2000, then the program behaves similar to 2.2

 I can do screen capture, I can see static waveform/FFT in Real Time Capture tab (still no realtime update, though the program reflects X and Y scale changes if I change it on the scope) , nothing displayed in Long Memory capture, though I can see the "LED" lights blinking as I press Capture button

EDIT: I was in USB mode
EDIt2: TCPIP did not work. The program just froze
EDIT3: I am on Win7 64 , 32-bit LabView Runtime

[pa3bca]

Its very odd that that real-time mode has broken, I have not made any changes.

I took a look at the ds2000 programming guide, looks like prehaps the ds2000 needs a few extra commands to get the memory buffer. Also removed a command from realtime mode, prehaps it will work now.

Also added a manual model override function. -so if you were using tcpip in version 2.2.1 it should work now provided you set the model. Actually I had no idea labview automatically handles VISA over TCPIP like that. So that's a win

V2.2.3.1

http://s000.tinyupload.com/?file_id=22255824192654410391

Hi
V2.2.3.1 has the following issues:
- If I start out with  Long Memory Capture it works.
- If I then switch to Realtime waveform, no waveform is shown on the screen (but it does update, the graticules jump in some out-ranging mode?)
- Screenshot still does not work.
-  If I then go back to Long Memory Capture the program locks up and I need to force-close it
nb: after the first malfunction the scope shows the "Parameter Limited" error, which stays there

[Bud]

That NI LabView Runtime is finiki. It killed TCP/IP capability on both Rigol's Ultra Sigma and 3rd party RUU programs. USB still works on both after LabView Runtime install but TCP/ IP does not anymore.

[Bud]

V2.2.3.1 has the following issues:
- If I start out with  Long Memory Capture it works.
- If I then switch to Realtime waveform, no waveform is shown on the screen (but it does update, the graticules jump in some out-ranging mode?)
- Screenshot still does not work.
-  If I then go back to Long Memory Capture the program locks up and I need to force-close it

This is weird. Here is what I have compared to yours:

- I tried starting in Long Memory Capture and it worked just once, subsequent capture does not work displaying just the blank waveform/FFT windows.
- If I then switch  to Realtime waveform, I can capture static waveform and its FFT, no real time update. Every time I cycle the capture button it grabs a static picture, and the scope screen flickers and says "Invalid data"
- If I then switch  to Screenshot Capture, I can capture screens no problem each time I press the capture button

I also noticed in Real Time capture the FFT displays different spectrum depending on the timescale, which makes me think it is incorrectly calculated or the waveform data it is using is invalid. I have attached 3 screenshots of a same 100MHz signal with different timescale, you can see they all show different FFT data.

[AlessandroAU]

V2.2.3.1 has the following issues:
- If I start out with  Long Memory Capture it works.
- If I then switch to Realtime waveform, no waveform is shown on the screen (but it does update, the graticules jump in some out-ranging mode?)
- Screenshot still does not work.
-  If I then go back to Long Memory Capture the program locks up and I need to force-close it

This is weird. Here is what I have compared to yours:

- I tried starting in Long Memory Capture and it worked just once, subsequent capture does not work displaying just the blank waveform/FFT windows.
- If I then switch  to Realtime waveform, I can capture static waveform and its FFT, no real time update. Every time I cycle the capture button it grabs a static picture, and the scope screen flickers and says "Invalid data"
- If I then switch  to Screenshot Capture, I can capture screens no problem each time I press the capture button

I also noticed in Real Time capture the FFT displays different spectrum depending on the timescale, which makes me think it is incorrectly calculated or the waveform data it is using is invalid. I have attached 3 screenshots of a same 100MHz signal with different timescale, you can see they all show different FFT data.

When the number of samples is fixed and the sample rate changes the FFT spectrum changes with timescale. The FFT is a compromise between upper frequency limit and spectral resolution. Especially since here we are limited by the number of points in the display buffer (hence the point of the long capture feature). The graphs looks fine, the fundamental frequency of 100MHz appears to be correctly identified in all cases, which means the scope is downloading the waveform and its info properly.

The sub-harmonic in the 3rd image is caused by one of the higher harmonics being aliased back into the 1st nyquist zone. (Due to the jitter issue)

[Bud]

Especially since here we are limited by the number of points in the display buffer (hence the point of the long capture feature).

OK if I understand correctly it seems one has to be careful in Real Time screen and not squash the waveform too much so the display buffer contains a quality representation of the waveform, i.e. fits not too many periods of the signal.

[AlessandroAU]

Especially since here we are limited by the number of points in the display buffer (hence the point of the long capture feature).

OK if I understand correctly it seems one has to be careful in Real Time screen and not squash the waveform too much so the display buffer contains a quality representation of the waveform, i.e. fits not too many periods of the signal.

This is true, http://zone.ni.com/reference/en-XX/help/372416B-01/svtconcepts/fft_funda/ is a good primer if you wish to learn more.

pa3bca, you're running firmware version 2 or something on your scope right? (I'm on 4) The reason I ask is that it is very unusual that screenshot capture does not work for you. The screenshot sub VI I have implemented comes directly from rigol's examples available on their documents page for the ds1000z series scopes.

I have found it even worked on my rigol signal generator. Anyway have you considered updating your firmware?, I think it could possibly solve some of the problems you're having. There should be no reason the program behaves differently for you if we have the same series scope.

[pa3bca]

pa3bca, you're running firmware version 2 or something on your scope right? (I'm on 4) The reason I ask is that it is very unusual that screenshot capture does not work for you. The screenshot sub VI I have implemented comes directly from rigol's examples available on their documents page for the ds1000z series scopes.

I have found it even worked on my rigol signal generator. Anyway have you considered updating your firmware?, I think it could possibly solve some of the problems you're having. There should be no reason the program behaves differently for you if we have the same series scope.

@AlessandroAU: I bit the bullet and installed the "latest brand new firmware" (that seems to fix the 5us jitter issues others have..).
Funny thing: The screenshot function now works with my 1074Z. But the other issues remain the same.
Directly to long mem capture: all ok.
But as soon as I use screen capture and/or Realtime waveform and then go back to Long memory capture: the scope then flashes a stream of errors at me, and the output is corrupt.
I also exchanged the USB cables/ports/hubs: no difference (not expected, but just to be sure)
Strange...
My bonus from the new FW: measurements display a bit nicer /  better readable.

[JDubU]

DS2072, HW v2.0, FW 00.03.01

As was previously posted, must set "Manual Model Override" to DS2000 before attempting to display any waveforms.  If set later (or left in Auto), lots of unexpected problems occur including program lockup.  Also, Long Memory Capture "Number of Points" drop down does not get set to DS2000 choices (stays in DS1000 mode until program restart and Manual Model Override gets properly set first).

Cannot change channel settings in Realtime Capture while Cont. Sampling is enabled.  Sometimes works but newly enabled channel does not get actual waveform until Cont. Sampling button is cycled off then on.  Sometimes locks up program requiring task manager kill then restart.

Long Memory Capture "Number of Points" drop down does not synchronize properly -- have to select value twice before the scope and the program's number of points become synchronized.  Also, the "Number of Points" drop down does not synchronize to the proper choices when channels are disabled or enabled on the scope itself.

Once the "Number of Points" drop down is properly set and synchronized with the scope, the Long Memory Capture only works properly with single chunk scans (14k and 140K point counts).  Take a look at the "Data Points" and "Downloading Chunks" fields in the attached screen shots.  Ignore the Model and Manual Model Override fields in these images.  I changed the connection type to LPT1 after each scan to keep the scope serial number private.

[pa3bca]

@AlessandroAU: I bit the bullet and installed the "latest brand new firmware" (that seems to fix the 5us jitter issues others have..).
Funny thing: The screenshot function now works with my 1074Z. But the other issues remain the same.
Directly to long mem capture: all ok.
But as soon as I use screen capture and/or Realtime waveform and then go back to Long memory capture: the scope then flashes a stream of errors at me, and the output is corrupt.
I also exchanged the USB cables/ports/hubs: no difference (not expected, but just to be sure)
Strange...
My bonus from the new FW: measurements display a bit nicer /  better readable.

[nixfu]

BUMP because people are looking for this after the new review video by dave.

[AlessandroAU]

After updating to the latest firmware I run into a bunch of errors and strange behavior grrr. Will investigate soon

[Andycap]

This has the potential to be a great tool.  I had a play around with it last night and apart from the function errors that kept showing up on the scope (DS1054z 100mhz) it ran great.  I did not have any crashes in the 3 hours that I was using it.  I did find a few layout errors and also would be great if it was resizable and auto scale the windows inside the main screen.

Keep up the great work. 

[rosbuitre]

Just tried 2.2.3 with USB.  I can connect and it detects a DS2000 series.  I can change channels (although 3 & 4 are not present on the scope!).  I can't do a continuous sample and get a waveform - scope just displays input is invalid, changing the scope scales has no effect on the charts, I can't get a screenshot.  And when I exit, I get a dialog box saying Resetting VI: Rigol_Capture.vi, which I can only get rid of by killing the process.

So, for me, 2.2.3 is broken compared to 2.2.1

Its very odd that that real-time mode has broken, I have not made any changes.

I took a look at the ds2000 programming guide, looks like prehaps the ds2000 needs a few extra commands to get the memory buffer. Also removed a command from realtime mode, prehaps it will work now.

Also added a manual model override function. -so if you were using tcpip in version 2.2.1 it should work now provided you set the model. Actually I had no idea labview automatically handles VISA over TCPIP like that. So that's a win

V2.2.3.1

http://s000.tinyupload.com/?file_id=22255824192654410391

Hi AlessandroAU
Have available a new version?, this can not be downloaded.
Thanks for your effort !!

Regards

[cubitus]

Hello,

I can not run properly Rigol_V2.2.3.exe here are the launch of errors.

What to do?

thank you

[miguelvp]

Hello,

I can not run properly Rigol_V2.2.3.exe here are the launch of errors.

What to do?

thank you

From the OP

Its written in Labview so you will need the Labview RTE http://www.ni.com/download/labview-run-time-engine-2014/4887/en/

[cubitus]

Hello,

This does not change anything ...

[bozidarms]

Hi to all,

i have try (DS4012) this great software, but have some problems-
1.instability
2.on FFt screen levels are 10dB too low
Is any further plans for improvements or work on it - think that software  has the potential to be a great tool
Tnx, regards,

Bozidar

[AlessandroAU]

Hello,

This does not change anything ...

You have a very strange error, it cannot find the files that should have been installed with the labview RTE. Do you install the RTE to a strange location?

[zxc_pavel]

Good day. Links in your post are broken now. Could you update it, please?
Thanks

[antoniobeta]

I posted this Utility in the Rigol DS1000/DS2000 jitter thread and since it seemed to attract some interest I figured I'd start a new topic.

Its written in Labview so you will need the Labview RTE http://www.ni.com/download/labview-run-time-engine-2014/4887/en/

Looking at the VISA commands this should also be compatible be somewhat compatible with the entire DS series from Rigol. I would expect the Real-time Capture to have no issues but there may be problems with the Long Memory Capture on other models scopes (I am using a DS1074z). If you have a DS2000/4000/6000 please test this and let me know.


Current Version V2.2.3


Rigol V2.2.3

http://s000.tinyupload.com/index.php?file_id=90659414641703074947

Rigol V2.2.1:

http://s000.tinyupload.com/index.php?file_id=06194785972356290806

Rigol V2.2

Download Link: http://s000.tinyupload.com/index.php?file_id=16159701921368811937

Source: http://s000.tinyupload.com/index.php?file_id=05957966868497599811

Known Bugs:

Long Memory Capture only supports one channel at a time and trigger channel must be the same as capture channel. For now it is a good idea to disable other channels when using this.

Memory Depth setting is only updated when a new menu selection is made.

In real-time capture mode changing channel options sometimes results in a communication error, stop cont. sampling before changing memory settings to avoid this.

Waveform statistics cannot compute more than 3Mpoints of data (labview limitation) currently statistics are calculated from the first 50Kpoints to improve speed.

Rigol DS1074z Bugs:

Scope complains of 'Invalid Input' but processes commands anyway. (Perhaps I do not known the exact sequence it expects) commands work regardless.

When using :WAV:DATA? to request samples there is an upper limit of exactly 1179644 data points that can be downloaded at any one time requesting more points using :WAV:START and :WAV:STOP will result in a no data being returned at all.

Note this is when downloading the data as bytes ie :WAV:FORM BYTE, if using :WAV:FORM ASC (ascii) the limit is reduced to around 60Kpoints.

However it is possible to download the entire waveform memory in blocks and this is the technique I have used to download more than 1.1Mpoints.

Hi! All links seems to be dead. Could you please reupload?