Products > Test Equipment
REVIEW - Rigol DS2072 - First Impressions of the DS2000 series from Rigol
<< < (419/566) > >>
marmad:

--- Quote from: Wim13 on January 03, 2014, 07:45:51 pm ---I think it slows down and makes FW complicated , now the FW has everytime
make decisions and have to think , ohh this is a A or a non A.

--- End quote ---

Really? I haven't noticed any slowing down - the newer FW seems better to me. Can you give a specific example to demonstrate?
Giorg:
Today I've updated directly from SW 00.01.01.00.02, HW 1.0.2.0.0 with all options installed and 200 bw to latest FW version. I've also cleared the memory as suggested. Any warning about this procedure? Anything else I should know?

Scope freezed while changing time division today, but maybe it's not related to the update.

thank you!
marmad:
While working on the new version of RUU, I've discovered two (relatively minor) firmware bugs involving SCPI commands (and added to the list on page 1). One of them is old (I noticed it already back in v.01.00.00.03) - one of them is new in this version. When reading display memory from the DSO, you should always get back 1400 bytes (unless you STOP the DSO and zoom out).

1) OLD BUG: When in HighRes mode and reading display memory from the DSO, if the time base is <= 20us, the DSO returns 1398 bytes instead of 1400.

2) NEW BUG: When the DSO is STOPped and reading display memory from the DSO while zooming out (i.e. make the time base bigger so the waveform is shrinking on the screen), the DSO returns (correctly) a decreasing number of display memory bytes until < 6, and then it incorrectly starts sending 1400 bytes every time (which is a nonsense waveform) instead of 2 (a single line).

You can see bug #2 in action (non-destructively) if you run RUU, then RUN and STOP the DSO with a small sample length. Then start zooming out. When the waveform reaches a single vertical line on the DSO screen, RUU will start displaying a wild, nonsense waveform - which is some part of overwritten display memory which the DSO is sending (incorrectly) to RUU. Kind of funny...  ;D
PA0PBZ:

--- Quote from: EV on December 27, 2013, 12:52:48 pm ---Traces when using type as dots or vectors look quite different. Why?
Time base 1 ns, Ch1 and Ch2 both on, HW 1, BW 300 MHz.

--- End quote ---
Carrington asked me to test this on my non-A hardware version 2 scope, with latest software and all upgrades and I get the following. Not sure if I missed a setting but it looks ok:

(Had no input for CH2 at hand)

Oops... looks the same at 1nS...
PA0PBZ:
And 1nS  :palm:

Navigation
Message Index
Next page
Previous page
There was an error while thanking
Thanking...

Go to full version
Powered by SMFPacks Advanced Attachments Uploader Mod