New Rigol DS1054Z oscilloscope

[McBryce]

"- Modified the failure when downloading waveform to the source module" ??

So it still fails, just differently?

McBryce.

[SimonD]

Someone brave ?   

[Daruosha]

I applied the update and the options remained untouched you can safely do the upgrade.

[Housedad]

Awesome! Thanks, Dwaine, Darousha!

[BravoV]

Someone brave ?   

Sigh ... really tempting but really scared, especially my old boot version ... 

[MrW0lf]

" - Fixed bugs about Measure"

16k for measurements like for FFT? Hmm... Probably not... But maybe fixed mess with <> signs etc. Would be interesting what exactly is fixed now.

[SimonD]

OK! Just another succesive update. PLUSES still remain!

[screwbreaker]

Sigh ... really tempting but really scared, especially my old boot version ... 

Ok, this is confusing to me. According to Rigol the problem was with boot version 0.0.0.13 or below. Your version is 0.0.1.0 which is higher than 0.0.0.13, so your boot version is ok for the update.

I think there are too many non significant zeros in the boot version, they make a lot of confusion.

In this topic "Just Upgrade my Rigol DS1054Z to the 4.04 firmware": https://www.eevblog.com/forum/testgear/just-upgrade-my-rigol-ds1054z-to-the-4-04-firmware/msg1068309/#msg1068309
User "Robuster" show a screenshot of his DS1054Z and the firmware version is 0.0.0.12, so versions below 0.0.1.0 really exists.

[borjam]

OK! Just another succesive update. PLUSES still remain!

Honestly, we'll miss it the day they fix the typo!!! 

[Fungus]

[Updated Contents]
--------------------
v00.04.04.03.02  2017/02/06
     - Improved the LXI module
     - Fixed the freeze problem when upgrading based on the boot version of
       0.0.0.13
     - Improved the menu in the language of Traditional Chinese and Korean
     - Modified the failure when downloading waveform to the source module
     - Fixed bugs about reading the memory data through SCPI commands
     - Fixed bugs about Measure
     - Fixed bugs about Filter

The "freeze problem when upgrading based on the boot version of 0.0.0.13" was the reason they pulled the previous firmware.

- Fixed bugs about Measure
- Fixed bugs about Filter

So that's it all fixed then.

[Fungus]

OK! Just another succesive update. PLUSES still remain!

Honestly, we'll miss it the day they fix the typo!!! 

I'm starting to think that's an inside joke at Rigol...

[Fungus]

" - Fixed bugs about Measure"

16k for measurements like for FFT? Hmm... Probably not... But maybe fixed mess with <> signs etc. Would be interesting what exactly is fixed now.

You're the expert. 

[Fungus]

Lone madmen trying to check the numbers are luckily either banned, hunted down or given up

That wasn't the reason you were banned.

Not one person ever has denied your numbers.

[MrW0lf]

You're the expert. 

don't have it. Almost willing to make bet that if it has 16k calculus now, will buy one again and go over it with LICKI couple times out of great joy. But bet goes both ways not sure what I would want you to go over with LICKI so better not

[Fungus]

Maybe "Fixed bugs about Measure" means they improved the RMS measurements or something like that.

[Fungus]

I noticed that the rise times say "<XXus" when you're zoomed out. Did it do that before? I don't remember.

It was one of the things Wolfie complained a lot about. Did they change it?

eg.

[frozenfrogz]

After updating to the latest firmware and running the self-calibration afterwards, I had a strange double-trace happening. It is gone now and I still need to reproduce it, but have not seen such behavior before :/
Maybe it was a hick-up, or something radiating into my signal path - I will do some further investigation...

[MrW0lf]

I noticed that the rise times say "<XXus" when you're zoomed out. Did it do that before? I don't remember.

It did in "one line" mode, did not notice it in other modes. However sometimes it was wrong. Here is test about this (quite long):
https://www.eevblog.com/forum/testgear/testing-dso-auto-measurements-accuracy-across-timebases/msg1096096/#msg1096096
Some outtakes that would instantly reveal if anything has improved with this:

Input: square wfm, frequency: 666.666666Hz, duty 66%
Math check: Period: 1.5ms; +Width: 0.99ms; -Width: 0.51ms

Old results for "one line" mode, did not show <> neither in big table or 4-line measurements (Cur/Avg/Dev/Cnt & Cur/Avg/Max/Min):



Note all <> signs were wrong, except rise. If it is single trace yes you can zoom in and inspect, however it is 4ch scope and may want to monitor multiple signals with quite different freq with some basic level of confidence (keeping eye on motor driver etc).

[xrunner]

Hey MrW0lf, is your signature in error -

MrW0lf=MrWolf. Personal messages please to MrW0lf only.

Shouldn't the "=' be "not equal" ?



Note the not equal character/sign does not work on the forum

[Assafl]

Did pressing a soft button scroll through the options before? I never knew it did that. Much better than the indent-less knob....

[McBryce]

Did pressing a soft button scroll through the options before? I never knew it did that. Much better than the indent-less knob....

Yes, it always did that, but you still have to press the knob to confirm the selection, otherwise the popup menu stays on the screen. 

McBryce.

[hexreader]

Did pressing a soft button scroll through the options before? I never knew it did that. Much better than the indent-less knob....

Yes, it always did that, but you still have to press the knob to confirm the selection, otherwise the popup menu stays on the screen. 

McBryce.

Just press another button (I usually go for the 'down' button) to clear the menu from the screen.

I too go to extreme lengths to avoid using that horrible rotary selection knob.

[frozenfrogz]

After updating to the latest firmware and running the self-calibration afterwards, I had a strange double-trace happening. It is gone now and I still need to reproduce it, but have not seen such behavior before :/
Maybe it was a hick-up, or something radiating into my signal path - I will do some further investigation...

Turns out I am picking up massive EM radiation @50Hz

This is with the clip-on heads for the probes, touching the tip with my finger (me being the antenna).
The only thing I changed in the last days was switching the Sunon fan for a Gelid Silent 5. Can anyone having done the fan mod confirm it is not an issue related to the fan?

[hexreader]

What multiplier setting is set in the "probe" menu item?

Is your probe switched to x1 or x10?

I get 4Vpp using myself as an aerial at home - tried with Rigol and with an Instek scope using standard Rigol scope probe.

Interestingly it makes little difference whether I switch the probe to x1 or to x10  the trace remains about the same (which might be interpreted as changing from 4Vpp to 40Vpp).

I could probably work out an explanation for this behaviour if I though hard enough, but to be honest, I can't be bothered. It is not like measuring mains pick-up is a sensible thing to do anyway.

I have not done a fan mod.

[Housedad]

double check your mains ground too.