Rigol DHO800/900 new firmware... 1.03

[mrisco]

Could you als please take a look at the FFT app? With new firmware it is not working anymore. It gives a connect error (remote execute error) and displays the signal wave

Ok, thanks for the report.

[csuhi17]

XY mode doesn't work for me, the app crashes.

[Fungus]

XY mode doesn't work for me, the app crashes.

Yep, I just tried it. It instantly crashes the app.

I just sent a message to Rigol EU about it. Let's see what happens.

https://eu.rigol.com/eu/quote/feedback

[mrisco]

Yep, I just tried it. It instantly crashes the app.

Have you tried resetting to factory settings?

[axantas]

Regarding the XY-mode crash: I just did some quick and dirty things with it, but I could not get it crashing on an original 924S.

And I finally can continue my antique analog TV work with a functionning video-trigger, that I can confirm working now.

[Fungus]

Yep, I just tried it. It instantly crashes the app.

Have you tried resetting to factory settings?

Yay! That did it.

Just press the "default" button twice and it starts working...

[Fungus]

So... this seems to fix all bugs, at least on the DHO800*.  I don't know about Bode plot on the DHO900.

This is the firmware they should have released six months ago.

(*) Have I forgotten any?

[shapirus]

So... this seems to fix all bugs, at least on the DHO800*.

Are screenshots still taken in the JPEG format in webcontrol?

I remember fixing this and changing the format to PNG in my own repacked version of the webcontrol apk.

Also, IIRC, I changed the resolution of the screen video recorder's stream (the one that you can save as file, not the live control one) from 1920x1080 to native.

[Fungus]

So... this seems to fix all bugs, at least on the DHO800*.

Are screenshots still taken in the JPEG format in webcontrol?

Yep.

That should be changed...

Also, IIRC, I changed the resolution of the screen video recorder's stream (the one that you can save as file, not the live control one) from 1920x1080 to native.

I haven't checked that one.

[Randy222]

So here is where we say "I downloaded the 00.01.03.00.06 version, but not installing it because of all the new issues" ?

I guess we wait for Rigol to push out a new 1.0.3.x ?

[Fungus]

So here is where we say "I downloaded the 00.01.03.00.06 version, but not installing it because of all the new issues" ?

What "new issues"?

This is a good round of bug fixes. I think there's none left now on DHO804.

Also some new features.

[mrisco]

I have updated the firmware and starting the mod process of the Sparrow.apk, looks like a lot of work ahead.

[Fungus]

I have updated the firmware and starting the mod process of the Sparrow.apk, looks like a lot of work ahead.

 

The silver lining is that Rigol probably isn't going to release another firmware anytime soon.

[mrisco]

Could you als please take a look at the FFT app? With new firmware it is not working anymore. It gives a connect error (remote execute error) and displays the signal wave

I've updated the firmware to the latest version and the FFT app is working.

[ebastler]

So... this seems to fix all bugs, at least on the DHO800

How about FFT-related bugs?

- Messed-up Flattop window function
- RBW without unit and with dubious values
- RBW not coming back to the same value after you switch the timebase up and back down a few steps

I saw these in the DHO1000, but to my knowledge the 800/900 series had inherited them too. Have they been addressed?

[csuhi17]

Yep, I just tried it. It instantly crashes the app.

Have you tried resetting to factory settings?

Thanks, it works for me too.
I have "Load last : Default" set, I thought that was enough. it looks like setting it to "Default" doesn't reset everything to default. Then I misunderstood the manual.

[csuhi17]

So... this seems to fix all bugs, at least on the DHO800

How about FFT-related bugs?

- Messed-up Flattop window function
- RBW without unit and with dubious values
- RBW not coming back to the same value after you switch the timebase up and back down a few steps

I saw these in the DHO1000, but to my knowledge the 800/900 series had inherited them too. Have they been addressed?

I checked the "flat_top" FFT table but it hasn't changed, it's the same as firmware 1.02.

[Fungus]

I have updated the firmware and starting the mod process of the Sparrow.apk, looks like a lot of work ahead.

Maybe when you've got it all working you could upload an image of the SD card.

That seems like the easiest/safest way for the maximum number of people to be able to use it.

[RAPo]

Strange not at my side, even with a reinstall and pressing default settings on the scope.

Could you als please take a look at the FFT app? With new firmware it is not working anymore. It gives a connect error (remote execute error) and displays the signal wave

I've updated the firmware to the latest version and the FFT app is working.

[sandor626]

il file che ho scaricato da Rigol è doppiamente zippato  ( doppiamente compresso )  !!
va estratto due volte 

[Howardlong]

After couple of hours of use in a real bench setup today doing some real work, this firmware update 10.01.03 [aka DHO800_DHO900(Software)UpdateV00.01.03.00.06.zip] finally makes this a usable scope.

At least Rigol realised that the firmware needed more than just a bit of minor warranty tweaking.

Some things I've noticed, mostly being irritating niggles rather than a reason to reject purchase.

o No trigger holdoff on any of the serial triggers.

o Default button resetting probe attenuation settings, trigger/decode default levels and LA thresholds to zero, rendering the button far less useful than it could be: the Siglent method where you can select your own default settings instead of factory defaults is the best solution I've found for this. As it stands, the factory default settings will almost always need quite a bit of fiddling. I have my own defaults saved as a setup, but there's more prodding than necessary just to load a setup.

o No hi-res mode, useful in real time acquisitions of noisy signals: can be worked around with a math lowpass.

o I've had a couple of times when the scope's stopped showing traces but is otherwise responsive. I reboot fixes it.

o Boot time is fairly slow.

o A couple of times the LA has become confused, with unresponsive channels, and I needed to reboot the scope.

o I may be missing something, but is it possible to have things like math traces in the same window as the main capture traces?

o Is it possible to use a VNC client like RealVNC rather than the web interface (I did try, maybe I have the wrong port?)?

In conclusion, despite my earlier hatred of this scope, Rigol have finally turned a very substantial corner with the new firmware, and it's very much for the better.

[Fungus]

Heads up, guys, I think I found a really bad bug in the new firmware.

I think it's related to the XY mode crash bug which was reported earlier.

Setting defaults lets you open XY window, no problem, but I think I powered down the 'scope yesterday when it was in XY mode and today it won't boot up any more. The 'scope app crashes on startup.

ADB is running OK, even  Webcontrol is running OK, but the scope app won't start.

I found this in the log file which seems to confirm the XY window is the problem:

Code: [Select]

09-09 02:54:40.536  1095  1095 D AndroidRuntime: Shutting down VM
--------- beginning of crash
09-09 02:54:40.536  1095  1095 E AndroidRuntime: FATAL EXCEPTION: main
09-09 02:54:40.536  1095  1095 E AndroidRuntime: Process: com.rigol.scope, PID: 1095
09-09 02:54:40.536  1095  1095 E AndroidRuntime: java.lang.NullPointerException: ServiceEnum.getEWaveGridsFromValue1(t) must not be null
09-09 02:54:40.536  1095  1095 E AndroidRuntime: at com.rigol.scope.views.grid.XYGridRulderView$2.onChanged(GridRulerView.kt:1509)
09-09 02:54:40.536  1095  1095 E AndroidRuntime: at androidx.lifecycle.LiveData.considerNotify(LiveData.java:131)
09-09 02:54:40.536  1095  1095 E AndroidRuntime: at androidx.lifecycle.LiveData.dispatchingValue(LiveData.java:149)
09-09 02:54:40.536  1095  1095 E AndroidRuntime: at androidx.lifecycle.LiveData.setValue(LiveData.java:307)
09-09 02:54:40.536  1095  1095 E AndroidRuntime: at androidx.lifecycle.MutableLiveData.setValue(MutableLiveData.java:50)
09-09 02:54:40.536  1095  1095 E AndroidRuntime: at androidx.lifecycle.LiveData$1.run(LiveData.java:91)
09-09 02:54:40.536  1095  1095 E AndroidRuntime: at android.os.Handler.handleCallback(Handler.java:755)
09-09 02:54:40.536  1095  1095 E AndroidRuntime: at android.os.Handler.dispatchMessage(Handler.java:95)
09-09 02:54:40.536  1095  1095 E AndroidRuntime: at android.os.Looper.loop(Looper.java:154)
09-09 02:54:40.536  1095  1095 E AndroidRuntime: at android.app.ActivityThread.main(ActivityThread.java:6157)
09-09 02:54:40.536  1095  1095 E AndroidRuntime: at java.lang.reflect.Method.invoke(Native Method)
09-09 02:54:40.536  1095  1095 E AndroidRuntime: at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:912)
09-09 02:54:40.536  1095  1095 E AndroidRuntime: at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:802)
09-09 02:55:29.290   559   872 I am_crash: [1374,0,com.rigol.scope,684244549,java.lang.NullPointerException,ServiceEnum.getEWaveGridsFromValue1(t) must not be null,GridRulerView.kt,1509]
09-09 02:55:29.291   559   872 W ActivityManager:   Force finishing activity com.rigol.scope/.MainActivity
09-09 02:55:29.291   559   872 I am_finish_activity: [0,61604609,1283,com.rigol.scope/.MainActivity,force-crash]
09-09 02:55:29.291   559   872 I am_focused_stack: [0,0,1,finishActivity adjustFocus setFocusedActivity]
09-09 02:55:29.292   559   872 I wm_task_moved: [1281,1,0]
09-09 02:55:29.295   559   872 I am_focused_activity: [0,com.rigol.launcher/.MainActivity,finishActivity adjustFocus]
09-09 02:55:29.295   559   872 I am_pause_activity: [0,61604609,com.rigol.scope/.MainActivity]
09-09 02:55:29.297   559   872 I sysui_action: [316,-1]
09-09 02:55:29.298  1374  1374 I Process : Sending signal. PID: 1374 SIG: 9

I've tried downgrading the firmware via command line. It does the same thing.

I even tried an older firmware image (Dave's original image as posted in the hacking thread!) and it still won't start.

How do I get it to revert to default settings on boot (ie. with no XY window open)?

I did "hold down the DEFAULT button" on power-up thing but that doesn't work. There has to be a way, surely, but Google is failing me here.

Bottom line: Do NOT power off your DHO in XY mode until we figure this out!

[mrisco]

Strange not at my side, even with a reinstall and pressing default settings on the scope.

Did you have the FFT Math channel 1 opened?

[mrisco]

Heads up, guys, I think I found a really bad bug in the new firmware.

try with

Code: [Select]

adb shell rm -r /data/data/com.rigol.scope

[Fungus]

try with

Code: [Select]

adb shell rm -r /data/app/com.rigol.scope-2

I don't have that file...

H:\work\ADB>adb shell ls /data/app/
com.rigol.launcher-1
com.rigol.webcontrol-1


I think the current settings are stored in the FRAM, not on the flash.