Rigol DS1054Z faulty, changing offset

[plazma]

My scope suddenly broke down. Now there is a changing offset depending on Y-scale. Self calibration didn't help.
I recently updated the firmware but can't say if the faut came directly after update or few days later.

In the attached pictures the probe is connected to the test waveform. Y-scale is changed between pictures.

The fault is in all channels. 1 & 4 also go negative. 2&4 only got positive changing offset.

Anyone seen the same before? Possible faults and fixes?
 

[RoGeorge]

Try to downgrade the firmware to a former known working version, using the disk attached as a zip file in the linked message:
https://www.eevblog.com/forum/testgear/new-rigol-ds1054z-oscilloscope/msg3613778/#msg3613778

The disk attached there does not contain any firmware, it only contains a signature that makes a downgrade possible, you have to copy on that disk the firmware version you prefer to downgrade to.

[Fungus]

My scope suddenly broke down.
...
I recently updated the firmware but can't say if the faut came directly after update or few days later.

It's not a coincidence. Get it reflashed ASAP.

You can use the method in the previous post or this one

[plazma]

Strange. Now the self-cal passed and the scope works normally again.

Thanks for the links. I'll save them incase I need to downgrade.

[tautech]

Strange. Now the self-cal passed and the scope works normally again.

Was there a reboot involved ?
Always good practice to reboot after a FW install.

[plazma]

Was there a reboot involved ?
Always good practice to reboot after a FW install.

Yes after the flaw there was reboots and a failed self-cal and few more reboots.

[RoGeorge]

Mine never ever failed at recalibration along the years, no matter what firmware version, and I don't know similar complains about autocalibration, so I suspect a recalibration failure might indicate some other problem waiting to happen, or maybe an intermittent kind failure of your oscilloscope.  A recalibration fail is not normal.

[marcus h]

Was there a reboot involved ?
Always good practice to reboot after a FW install.

Yes after the flaw there was reboots and a failed self-cal and few more reboots.

I think tautech meant a reboot directly after the firmware update, not after you noticing the flaw.

[MarkF]

I seem to remember getting a calibration failure once when I had NOT allowed enough time for the scope to warm up.
I like to have the scope running for at least 1/2 hour before doing a calibration.

[tautech]

Was there a reboot involved ?
Always good practice to reboot after a FW install.

Yes after the flaw there was reboots and a failed self-cal and few more reboots.

I think tautech meant a reboot directly after the firmware update, not after you noticing the flaw.

Nearly.
Not sure how Z's update but FW updates in our stuff requires a reboot directly after FW install and the following shutdown always takes a little longer than is usual which to me indicates the OS is still sorting out applying the new FW.

The 2nd boot is when everything returns to normal.
Then we run the instrument for ~15mins (don't forget it's already been running for 5-10) and do SelfCal and such.