Products > Test Equipment

REVIEW - Rigol DS2072 - First Impressions of the DS2000 series from Rigol

<< < (171/566) > >>

MikeR:

--- Quote from: marmad on April 23, 2013, 09:40:23 pm ---
--- Quote from: MikeR on April 22, 2013, 04:23:04 pm ----Anyhow the .wfm file format is rather odd, baudline is able to parse unsigned bytes easily - it will display the spectrum showing e.g radio channels in the right places but only for sample rates set to 1GS/Sec, the file was captured at 2GS/sec, if I load that setting the sample rate accordingly they are in the wrong "spot" suggesting the original data isnt 2GS/sec.

--- End quote ---

Why would this be your conclusion? That equipment programmed to write it's own invented file format isn't doing it correctly? But that the third party software IS reading the file correctly?

As I mentioned already, the format described in wfm_view and other online sources for the DS1000 series is not valid anymore. The locations in the header of pertinent information (sample rate, sample size, etc) - and the manner in which the DSO stores sample data has been altered quite substantially. It's likely that with 2GSa/s the Rigol is storing the data in a different fashion than with 1GSa/s - since the 2GSa/s setting was not available in the DS1000 series. No one has published specs on the new format yet - or written any readers. My Rigol doesn't have any problems writing - and then later reading - a 2GSa/s WFM file - so clearly the fault is in the software. So, instead of claiming, as you did first, that the Rigol wasn't sampling at 2GSa/s - or secondly, that the Rigol isn't writing the 2GSa/s to the file (both of which are easy to prove otherwise) - you should be studying the new format and discovering the changes so that you can get Baudline to work correctly.

--- End quote ---

It not my conclusion since its still being investigated. I haven't "claimed" anything here just stated my ongoing observations. Which stands currently that the 2GS/s wfm file when loaded into baudline only seems to be at 1GS/Sec, why is still to be determined and I am working with the baudline author to add support for the file format having supplied many example waveforms.

Update:
That observation is for the .wfm file *only*

- The CSV output mode does contain the full 2GS/Sec when configured to capture at that speed.
as shown in the attachments.

Same 50 Mhz signal.

Loading the .wfm with a samplerate (in baudline) set to 1GS/sec results in the 50Mhz signal being
at 50 Mhz, which triggered my original question.

-M

marmad:

--- Quote from: MikeR on April 23, 2013, 10:35:05 pm ---I haven't "claimed" anything here just stated my ongoing observations.

--- End quote ---

You wrote:

--- Quote ---It "seems" to be sampling at 2GS/sec.
--- End quote ---
and

--- Quote ---...suggesting the original data isnt 2GS/sec.
--- End quote ---

Both of those 'observation' were implying that the Rigol was doing something wrong - when it was ridiculously easy to prove that it was doing those things correctly with simple experiments - and thus Baudline was at fault .


--- Quote ---Which stands currently that the 2GS/s wfm file when loaded into baudline only seems to be at 1GS/Sec

--- End quote ---

Yes, because Baudline is obviously reading the file incorrectly.

MikeR:

--- Quote from: marmad on April 23, 2013, 11:21:43 pm ---
--- Quote from: MikeR on April 23, 2013, 10:35:05 pm ---I haven't "claimed" anything here just stated my ongoing observations.

--- End quote ---

You wrote:

--- Quote ---It "seems" to be sampling at 2GS/sec.
--- End quote ---
and

--- Quote ---...suggesting the original data isnt 2GS/sec.
--- End quote ---

Both of those 'observation' were implying that the Rigol was doing something wrong - when it was ridiculously easy to prove that it was doing those things correctly with simple experiments - and thus Baudline was at fault .


--- Quote ---Which stands currently that the 2GS/s wfm file when loaded into baudline only seems to be at 1GS/Sec

--- End quote ---

Yes, because Baudline is obviously reading the file incorrectly.

--- End quote ---

Well not really, my understanding was incorrect. Baudline was reading the file correctly it was just in the wrong order / format. Now this has been solved and its showing a full 1 Ghz of spectrum from the 56M captured wfm.

Same is probably true for the 1400 :wav:data? points thats currently capturing at 30FPS or over 68K samples /sec over LAN so extending the same decoding to that code should be trivial.

-M



 

marmad:

--- Quote from: MikeR on April 25, 2013, 06:43:00 pm ---Well not really, my understanding was incorrect. Baudline was reading the file correctly it was just in the wrong order / format.
--- End quote ---

So you think Rigol was writing their own invented file format the wrong way?  ;)  I think it would probably be more accurate to say that Baudline was not reading Rigol's new version of it's .WFM format correctly.

marmad:

--- Quote from: Evi on April 22, 2013, 04:02:45 pm ---I do agree, Mark. But if so, why not to make a separate topic for FW updates to put there FW files. Because now everybody here need each time to ask his dealer for help.

--- End quote ---

@Evi: Good idea. I will ask my dealer if he thinks it would be a problem for Rigol if we keep copies of the already-released FW versions available here. BTW, I sent you a PM about FW, too.

Navigation

[0] Message Index

[#] Next page

[*] Previous page

There was an error while thanking
Thanking...
Go to full version
Powered by SMFPacks Advanced Attachments Uploader Mod