Rigol DS1000z/2000/4000/6000 Waveform Capture Utility

[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?