Rigol DHO800/900 new firmware... 1.03

[Fungus]

Not anymore... 01.02.00.02 is the latest version there now.

I reported it, I guess they took it down.

[sandor626]

ho fatto l'aggiornamento del firmware all'ultima versione . Ho notato il bug che è presente   quando la finestra XY  è ingrandita .  Invece, se oltre la finestra XY  è aperta anche una altra finestra , tutto sembra funzionare bene 

[newbrain]

ho fatto l'aggiornamento del firmware all'ultima versione . Ho notato il bug che è presente   quando la finestra XY  è ingrandita .  Invece, se oltre la finestra XY  è aperta anche una altra finestra , tutto sembra funzionare bene

Ciao sandor626, visto che questo è il secondo messaggio in italiano che posti, considera che la lingua ufficiale del forum è l'inglese - se ci mettiamo a parlare ognuno la propria, diventa un casino!
Molti membri qui magari non protestano, ma salteranno a pie' pari il tuo messaggio. Google Translate funziona bene, ma non sta a chi legge usarlo.
Qualcuno sul forum mette il testo in inglese e poi quello nella loro lingua (un paio di persone al massimo), penso che sia accettabile per messaggi brevi, perché un lettore nativo potrebbe cogliere qualche dettaglio in più che si perderebbe nella traduzione.

Hi sandor626, as this is the second message you posted in Italian, let me remind you that the official language of the forum is English - if everyone starts using their own native language, it soon becomes a mess!
Many members here will probably not complain, but will just skip the message. Google Translate works quite well, but is not on the reader to use it.
I've seen a couple of posters writing the English text first, followed by their language, I find that acceptable for short messages, as a native reader might get some more nuances that might get lost in translation.

Hej sandor626, eftersom det här är det andra meddelandet du postade på italienska, låt mig påminna dig...ci siamo capiti!

[sandor626]

OK !

[sandor626]

I updated the firmware to the latest version. I noticed the bug that is present when the XY window is maximized. However, if in addition to the XY window another window is also open, everything seems to work fine

[csuhi17]

I updated the firmware to the latest version. I noticed the bug that is present when the XY window is maximized. However, if in addition to the XY window another window is also open, everything seems to work fine

You Be careful, because if you turn off the scope in active XY mode, you can easily brick your device!
It was already mentioned in the previous posts, but that's why you can't access the firmware version anymore!

[sandor626]

The download of version 1.03 is blocked from site rigolna.com, but it is not blocked from site rigol.com.
I also wrote in another post that the file of the firmware  located on rigolna.com  must be unzipped for two time .

[Fungus]

I've had another fiddle this weekend but no joy. There doesn't seem to be any way to wipe the saved settings when it's in this state.

I finally broke my warranty seal and put Dave's original firmware image on an SD card to see if it would boot. It starts up but it does the same thing - the 'scope app crashes on startup.

Rigol are working on a fix.

[mrisco]

I've had another fiddle this weekend but no joy.

If you want to test, I could implement an apk with a solution.

[Fungus]

I've had another fiddle this weekend but no joy.

If you want to test, I could implement an apk with a solution.

Did you try breaking yours yet?

[Fungus]

you can easily brick your device!

Technically not a "brick", it still boots, other apps work, just not the 'scope app.

[mrisco]

Did you try breaking yours yet?

I'm working with it and don't have another one, so no.

[Fungus]

Did you try breaking yours yet?

I'm working with it and don't have another one, so no.

Fair enough 

Do you know a way to make the "su" command to work on these? It gives an error.

The upgrade scripts need root user to run. I tried running them with ADB in root mode but they complain about not being root user.

I can obviously edit the scripts to take out the check for root but then I'm not sure if they succeed.or not.

[rpro]

Do you know a way to make the "su" command to work on these? It gives an error.

Try

adb connect ip:55555
adb shell

...and once inside the shell just type

su

this will switch the shell user ID to root. E.g.,

logname

will return 'root'.  (To exit back to your pc, you will need to type 'exit' twice.)

[csuhi17]

you can easily brick your device!

Technically not a "brick", it still boots, other apps work, just not the 'scope app.

I hope so, but for now you can make your device unusable with it.

I think that if it could be solved simply, then Rigol would have already told you the way.
If nothing else, they would write a program or code that, if you run it, resets the device.
I hope they solve the problem.

[Fungus]

Try

adb connect ip:55555
adb shell

Ah, I didn't know you could do that. I thought "shell" was just to execute single shell commands, eg. "adb shell ls /".

That'll make playing around a lot easier 

[Fungus]

I think that if it could be solved simply, then Rigol would have already told you the way.
If nothing else, they would write a program or code that, if you run it, resets the device.
I hope they solve the problem.

There needs to be a way to reset the settings, eg. by holding down the "DEFAULT" button at power-on.

I always assumed there was a way, there is on other devices they make, eg DS1054Z, but not on these.

Luckily I haven't needed my 'scope this week because I'm busy doing other things (it's back-to-school week).

[shapirus]

Try

adb connect ip:55555
adb shell

Ah, I didn't know you could do that. I thought "shell" was just to execute single shell commands, eg. "adb shell ls /".

That'll make playing around a lot easier 

You can also run "adb root" after "adb connect", that'll change user to root by default.

[Fungus]

You can also run "adb root" after "adb connect", that'll change user to root by default.

That's what I was doing before, but it's not the same thing.

eg. The scripts on the 'scope tell me I'm not root if I do that.

ie. This fails:

Code: [Select]

# Make sure only root can run our script
if [[ $EUID -ne 0 ]]; then
echo "YOU must be as root" 1>&2
exit 1
fi


[sandor626]

after updating the firmware to 1.03, everything seemed to be fine. But when I launched the XY view the scope froze.
It was then that I read a comment that recommended double-tapping the default key.
Since then the scope starts up fine, and runs XY in a window as long as you also have the standard window side by side.
In any case it never freezes during the initial loading phase

[RAPo]

But be very, very careful: if you close the scope with only xy-window active, people experience a bricked scope.
I downgraded and will install a new firmware only after 3 weeks with no user complaints (here or on YouTube).

after updating the firmware to 1.03, everything seemed to be fine. But when I launched the XY view the scope froze.
It was then that I read a comment that recommended double-tapping the default key.
Since then the scope starts up fine, and runs XY in a window as long as you also have the standard window side by side.
In any case it never freezes during the initial loading phase

[ebastler]

But be very, very careful: if you close the scope with only xy-window, active people experience a bricked scope.

That's mean. Why should active people fare worse than others? 

[RAPo]

I stand corrected. Will move the comma.
PS: https://youtu.be/sxfxy-3dGz0?si=BtefZ9Uyn5GPJAzm

But be very, very careful: if you close the scope with only xy-window, active people experience a bricked scope.

That's mean. Why should active people fare worse than others? 

[Fungus]

But be very, very careful: if you close the scope with only xy-window active, people experience a bricked scope.
I downgraded and will install a new firmware only after 3 weeks with no user complaints (here or on YouTube).

I had XY and normal window open.

[Fungus]

after updating the firmware to 1.03, everything seemed to be fine. But when I launched the XY view the scope froze.
It was then that I read a comment that recommended double-tapping the default key.
Since then the scope starts up fine, and runs XY in a window as long as you also have the standard window side by side.
In any case it never freezes during the initial loading phase

You can't say we didn't tell you not to...