There's also Rigol's WFM converter, but again it only works with DS4000 and DS6000 series, so I had no luck with that either. I found the open source pyRigolWFM tool for reading WFM files, but unfortunately it only seems to support the DS1000 series and doesn't work with files produced by DS2072A. Exporting to those is much faster than to the text-based CSV format, but on the other hand it creates binary blobs that apparently only the scope itself can read. Luckily, there's also an option for a binary export that creates WFM files. I planned to do many captures, so that approach was clearly unusable. I'm guessing exporting a full 14 Msample capture would take an hour - I've never had the patience to actually wait for one to finish and the progress indicator indeed remained pegged at 0% until I reset the scope in frustration. Exporting 1.4 Msamples took nearly 6 minutes. DS2072A indeed has this feature, however I soon found out that it is unbearably slow. On most modern digital scopes that's a simple matter of exporting a trace to a CSV file on a USB stick.
Recently I was using it to capture some waveforms that I wanted to further process on my computer. I'm not joking - I think there's some kind of a double-buffering issue there. Like for example the screenshot tool that sometimes, but not always, captures a perfectly plausible PNG that actually contains something different than what was displayed on the physical screen at the time.
It can be buggy at times though and with experience I learned to avoid some of its features.
It's quite a featureful little two-channel digital scope that mostly does the job that I need it for. fwiw.At work I use a Rigol DS2072A oscilloscope. my advice in case capture process (wfm export from dso) cant be made the same time and place as PC post processing or data analysis, we should make screenshot capture to the USB stick used to save the wfm file, so later in pc we can verify the data captured from DSO (screen) was the same (offset and scaling) as whats saved in the wfm file. by default, we assume no bug (data discrepancey) going on (Settings -> Data Trans. Method) and (Settings -> Manual Trans Setting) and scaling in case we encountered this bug. VisaDSO provides manual data offset (Settings -> Data Trans. but i cant remember if they are the same as csv or not because if we closely deal with this we will encounter some form of weirdness (bug?) ie sometime the data we downloaded whether directly to PC through USB, or in wfm/csv files is not tally with whats shown on the dso screen, so we need to double check what we get in files/pc compared to dso screen. There is no need to decode, everything is plain raw (8 bit) value.
0 kommentar(er)
