Products > Test Equipment

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

<< < (470/566) > >>

Mark_O:

--- Quote from: Teneyes on April 08, 2014, 07:52:44 am ---A High Speed Test of  RS232 Data Recording & decoding
 I used:
...
          475 Byte Block
...
          Recorded 508  Frames

  For a Total of  241300  Bytes recorded

--- End quote ---

Yes, and the key point being that the same results would have been obtained if those 508 frames had gaps of seconds or minutes or hours between them, regardless of the inter-frame latencies.  (Plus, you could turn on the ClockTag, and see the date/time stamp for each frame.)

That's the power of segmented captures.

Mark_O:

--- Quote from: Teneyes on April 08, 2014, 01:36:15 am ---Data Decoding Limit  ( RS232 test)

it appears that to Decode without  Errors, at least 28 Pts must be allocated for Each 'BIT' of data or else the Decode will miss a byte.

To test I used:
            2ms/div
            70Kpts/display
            89.2Kb.s   all OK   = 28.027 Pts/bit
            89.4Kb/s   Errors occuring
See Pics

--- End quote ---

I'm not so sure about that.   It's not decoding from those 28 samples (or less) per bit cell.  It's decoding from what's on the screen.  When you zoom in too far (or equivalently, increase your bit stream and thereby compress what's on-screen), then decodes will fail.

In your second test at 89.4Kb/s, if you had just zoomed out a bit from the 100us/div you were at, then it would have had more bits to work with, and started "working" again.  Even though the sample Pts/dataBit hadn't changed at all.

I think.  ;D

So the real conclusion would be that with 10-bit RS232 bytes (at 1 Start, 8 Data, and 1 Stop each), the 700 points on-screen can support up to 12 bytes at once, but not 13.

Teneyes:

--- Quote from: Mark_O on April 08, 2014, 09:54:30 am ---In your second test at 89.4Kb/s, if you had just zoomed out a bit from the 100us/div you were at, then it would have had more bits to work with, and started "working" again.  Even though the sample Pts/dataBit hadn't changed at all.
I think.  ;D

--- End quote ---
EDIT:    This Bug is Fixed in Latest Firmware 00.03.00.01.03
Note last displays shows  90KBytes/s= 900,000b/s

 Just to make it Clear to all; Zooming has no effect if there are Decoding errors. The decoding is done on the full un-Zoomed data.  Below I show 3 displays where the errors still exists. Note you can see the error gaps

In order to make full used of the 140KPts I fill the full display with DATA  (by increasing byte count in the frame/segments or reducing the time of the display (<timebase)   

Also Note that  if there are errors in non- Record mode there will be errors in the recorded frame ( same recorded points are used, Not the display data)

PS  I captured all 3 frames into eevblog from the DSO in 150 seconds , using RUU

Teneyes:

--- Quote from: Mark_O on April 08, 2014, 09:39:34 am ---..the key point being that the same results would have been obtained if those 508 frames had gaps of seconds or minutes or hours between them, regardless of the inter-frame latencies.  (Plus, you could turn on the ClockTag, and see the date/time stamp for each frame.)
That's the power of segmented captures.

--- End quote ---
I agree and here is an example ( thanks for pointing out TimeTag)
high speed data (1Mb/s), short bursts(100us) , with recording that could record for 5.5 Days

Teneyes:
With more and more people stating and receiving the New FW 00.03.00.00, I thinking it would good to report new Bugs here.  Marmad has kept a good list on the 3rd post of this Blog.  Altough Marmad usually confirms all bugs himself , I think it would be helpful for a few others to confirm any reports.  Also if any Fixs to an existing bug is a complete fixed.

These are Bugs I have found:

     #03__01   The Clear Button does not work.
              EDIT:    Fixed in Firmware 00.03.00.01.03

     #03__02   The decode display does not clear when decode is turned off
              EDIT:    Fixed in Firmware 00.03.00.01.03

     #03__03   Once the lg(CH1) advance Math function is applied you can Edit the function;
                   If the Expression button is press the DSO hangs. and if in start Last System. the
                   attempt to change the expression , will hang the DSO!!! :--   :--
              EDIT:    Fixed in Firmware 00.03.00.01.03


     #03__04   The Set Counter Menu has display Error (unnecessary scrolling,small )  see Pics
                   This occurs when system 'System'-'Power On' - is set to 'Last' and the trigger is
                   NOT set to EDGE trigger.
                   Power cycle after PULSE trigger causes 3 items in Menu ,most others 2 items set in Menu
                   Auto Setup Button resets trigger to Edge  and all 4 Menu Items??? (CH1,Ch2,Ext,Off)
              EDIT:    Not Fixed in Firmware 00.03.00.01.03

If anyone ventures onto Fw 00.03.00.00, please help to confirm any of these.

Edit 1  Added more info on Bug #03__04

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