Rigol DHO800/900 new firmware... 1.03

[thm_w]

I spent almost 1000 euros on an oscilloscope, my DHO 924S, which doesn't work.
I will wait another 15 days, if Rigol does not solve the problem by releasing a stable firmware version, I will return the oscilloscope to Rigol Italia asking for a refund of what I paid.

You should have read here first, DHO900 is a poor choice. DHO 804 is decent value.

When I e-mailed Rigol about the DM800 series bugs, the responses were unbelievably bad.  First response was they'd send my comments to R&D for investigation, which is total deflection because people have already commented about this so they surely know about it.  Second response (first response from R&D) was just some marketing junk about how their DMM was better than their previous ones. I hit them again with all of the proof of the issues with links to Youtube timestamps and EEVblog forum posts and their response back was please provide proof of the issues, completely ignoring the proof already provided!  They also said they weren't going to consider the issues reported on the EEVblog since they were from an "informal forum" and that they were not going to investigate the issue any further.

I completely get what you are saying, but to get a good response you need to make a very clear explanation of: what the bug is, why it negatively affects your work, and how to reproduce it. Single bug at a time.

Anything outside of that is just a suggestion that the support person may or may not care to pursue.

[J-R]

When I e-mailed Rigol about the DM800 series bugs, the responses were unbelievably bad.  First response was they'd send my comments to R&D for investigation, which is total deflection because people have already commented about this so they surely know about it.  Second response (first response from R&D) was just some marketing junk about how their DMM was better than their previous ones. I hit them again with all of the proof of the issues with links to Youtube timestamps and EEVblog forum posts and their response back was please provide proof of the issues, completely ignoring the proof already provided!  They also said they weren't going to consider the issues reported on the EEVblog since they were from an "informal forum" and that they were not going to investigate the issue any further.

I completely get what you are saying, but to get a good response you need to make a very clear explanation of: what the bug is, why it negatively affects your work, and how to reproduce it. Single bug at a time.

Anything outside of that is just a suggestion that the support person may or may not care to pursue.

I did, I explicitly stated the mV to 30V issue...

We can see that Fungus has someone's ear on this issue, but the point remains that frequently issues don't get addressed.

[sandor626]

news ?

[Fungus]

Nearly there...

[sandor626]

What firmware version "bricked" your scope? v00.01.03.00.04 or v00.01.03.00.06?
I'm still able to download v00.01.03.00.06 from supportint.rigol.com

hey my friend don't do it, with any damn version, wait for Rigol to provide a new version with clarifications

[ptluis]

What firmware version "bricked" your scope? v00.01.03.00.04 or v00.01.03.00.06?
I'm still able to download v00.01.03.00.06 from supportint.rigol.com

hey my friend don't do it, with any damn version, wait for Rigol to provide a new version with clarifications

Don't worry mine is still waiting in the shopping cart   

[mrisco]

@Fungus, to have it more clear, you was able to "downgrade" your entire firmware by loading an µSD card with a previous version. But that not solve the error. So the 0.1.0.2 also have a bug but it is only evident under certain values saved in the NVRAM. Is that correct?

[Fungus]

@Fungus, to have it more clear, you was able to "downgrade" your entire firmware by loading an µSD card with a previous version. But that not solve the error. So the 0.1.0.2 also have a bug but it is only evident under certain values saved in the NVRAM. Is that correct?

Yes.

There doesn't seem to be an easy way to wipe the NVRAM. I assume it's because Android doesn't know anything about it, it's all done by the 'scope app.

From what I know things are moving at Rigol, but there's a lot of layers of people and big timezone differences.

[mrisco]

Yes.

Could you provide me the detailed steps to brick the device?
I'm a little tired of waiting to Rigol to solve this issue.

[mrisco]

Yes.

There doesn't seem to be an easy way to wipe the NVRAM. I assume it's because Android doesn't know anything about it, it's all done by the 'scope app.

From what I know things are moving at Rigol, but there's a lot of layers of people and big timezone differences.

Please try the apks from: https://github.com/mriscoc/RIGOL_DHO800_DHO900_GUI/releases/tag/SPGUI0.2.1 and if there are errors paste the log here.

Installing the apk manually
Rename the downloaded file to SparrowExt.apk and open a terminal (CMD) window inside of the folder where
the file is located. Execute the following commands, replacing ###.###.###.### with the correct IP of the device.

Code: [Select]

adb connect ###.###.###.###:55555
adb root
adb shell

::####################################################################################
::# Uninstall old version
::####################################################################################
am force-stop com.rigol.launcher
am force-stop com.rigol.scope
pm uninstall com.rigol.scope
exit

::####################################################################################
::# Scope APK install
::####################################################################################
adb push SparrowExt.apk /mnt/tmp/app/SparrowExt.apk
adb shell
pm install -g -r /mnt/tmp/app/SparrowExt.apk
reboot

I was unable to brick the device with this version.

[Fungus]

Yes.

Could you provide me the detailed steps to brick the device?
I'm a little tired of waiting to Rigol to solve this issue.

Set it to restore previous settings on power-on.

Open an XY window.

Turn it off.

[mrisco]

Set it to restore previous settings on power-on.

Open an XY window.

Turn it off.

Ok, I do that with the 0.1.0.3.6 version and the device responds normally. If I left only the XY window open, after the reboot there are the normal wave window with the XY window aside

[Fungus]

Ok, I do that with the 0.1.0.3.6 version and the device responds normally. If I left only the XY window open, after the reboot there are the normal wave window with the XY window aside

I think I had two windows open - normal and XY.

I'd just posted about how I pressed default twice to get XY mode working so I guess I did that right before I powered off.

I went to bed right after I powered off so it was next day when it found the bug. I don't remember the exact sequence.

Rigol managed to reproduce it easily.

I thought there was going to be a new firmware this week but here we are at the weekend. 

AFAIK the firmware exists but they're working on a way for ordinary people to fix affected 'scopes (without command line ADB hacking).

[mrisco]

In principle I expected that the apk that I linked would solve your issue automatically.

[TimFox]

Ok, I do that with the 0.1.0.3.6 version and the device responds normally. If I left only the XY window open, after the reboot there are the normal wave window with the XY window aside

I think I had two windows open - normal and XY.

I'd just posted about how I pressed default twice to get XY mode working so I guess I did that right before I powered off.

I went to bed right after I powered off so it was next day when it found the bug. I don't remember the exact sequence.

Rigol managed to reproduce it easily.

I thought there was going to be a new firmware this week but here we are at the weekend. 

AFAIK the firmware exists but they're working on a way for ordinary people to fix affected 'scopes (without command line ADB hacking).

Do your contacts have any updates about the Bode-plot bug I reported last year?

[Fungus]

Do your contacts have any updates about the Bode-plot bug I reported last year?

I haven't asked them.

[sandor626]

Set it to restore previous settings on power-on.

Open an XY window.

Turn it off.

My oscilloscope still crashed after installing 1.03.00.06.

I had selected, as an option on reboot, restore last mode. And I had the XY window open.
Upon reboot, my scope crashed after doing what appeared to be a normal boot.
So I ended up with the black screen.

 Reading some comments online, I pressed the default button twice (for two seconds) in succession.
And then I rebooted.

My oscilloscope has started working again, or seems to be working.

But I will never repeat the death sequence again!!

 I prefer to wait for Rigol.

Or someone who can give a convincing explanation for the bug

[Fungus]

Reading some comments online, I pressed the default button twice (for two seconds) in succession.

When do you press it?

I've tried holding it down at startup, it didn't do anything.

[sandor626]

When do you press it?

I've tried holding it down at startup, it didn't do anything.

I pressed the "default" button, after the entire boot procedure (after the "game" of the illuminated buttons was over). That is, with the black screen and the keys off (not bright)

[mrisco]

I think I had two windows open - normal and XY.

In my case the scope app doesn't crash