Hacking the HDO1k/HDO4k Rigol 12 bit scope

[markone]

Tested a bit more, it looks like you can only have a side by side or top / bottom layout.  Event table is kind of mandatory as the way protocol decoding info is displayed in the waveform is kind of hard to read the values of the frames.  If I want to take advantage of the full sample memory, stop and zoom to decode, I cannot do it... as soon as I change the timebase, it says TOO MANY EVENTS or something like that and it does not decode. If I set it to a timebase where it still decodes, the update rate is like 1Hz... for a 115,200 baud rate UART decoding!!!  No wonder why it hangs with a 45MHz SPI signal... and it does not even decode correctly the frames.  I really cannot understand Rigol, they did not do the basic testing before releasing the scope, like someone sitting with the scope and testing it??

I've been busy with work so had only like 1-2 hour total to play with the scope, but will try make more tests during the weekend.

EDIT (TOO MANY EVENTS): The message I get is "There are too many results".  You can stop and zoom and get the packets.  But it works only up to 20ms timebase.  If you want to set 50ms or higher, then it says Operation Disabled.  Still a lot of freeze/reboot issues.

EDIT 2: Created new HDO1000 BUGs topic. https://www.eevblog.com/forum/testgear/new-rigol-hdo1000-12-bit-dso-bugs/

I agree 100%, what you describe is simply unacceptable, i would dare to say that this product line is not ready to be sold, given the situation i fear that i'll be forced to buy something else, probably an MSO5074, i already use it at a customer's lab and I think it is at least decent.

I smell that this time Rigol has outsourced FW/SW development to a new external supplier who is not up to par, something I'm seeing more and more often.

[oliv3r]

Hmm, buggy behaviour of the HDO1k doesn't bode well for the HDO4k...more expensive, more half-finished features, more bugs? Time will tell.

Since the software stack tends to be 'identical' (or asian style copy->paste modify; then modify each version individually with the same fixes) quite likely. Also don't expect all bugs to be fixed on all platforms because of this. But hey, maybe they've learned how to do proper software development for the HDO 

EDIT 2: Created new HDO1000 BUGs topic. https://www.eevblog.com/forum/testgear/new-rigol-hdo1000-12-bit-dso-bugs/

Thanks! Lets keep bug discussions in that thread. I'll update the main post with this!

[idolclub]

Rigol HDO 1000 and HDO 4000 has been renamed to DHO 1000 and DHO 4000 on November 7, 2022.

HDO1000 --> DHO1000

HDO4000 --> DHO4000

[tv84]

Rigol HDO 1000 and HDO 4000 has been renamed to DHO 1000 and DHO 4000 on November 7, 2022.

HDO1000 --> DHO1000

HDO4000 --> DHO4000

Another bug??   

[tautech]

Rigol HDO 1000 and HDO 4000 has been renamed to DHO 1000 and DHO 4000 on November 7, 2022.

HDO1000 --> DHO1000

HDO4000 --> DHO4000

Another bug??   

Nah, they left those with the previous model.
Reset, starts from zero again.

[tv84]

The other was the little-endian model. Now it's the big-endian one! 

[Fungus]

Rigol HDO 1000 and HDO 4000 has been renamed to DHO 1000 and DHO 4000 on November 7, 2022.

HDO1000 --> DHO1000

Suddenly all the ones with "HDO" on the front are worth a lot of money on eBay...

[2N3055]

I see that naming on Rigol Japan and China...
Funny thing is if you Google translate it it will also "translate" DHO4000->HDO4000 in translated text  ...
Maybe LeCroy wasn't happy... ?

But I think why this premature push happened.. I missed this news (not following Rigol in detail..)  :

https://www.rigol.eu/NEWS/news/53.html

Now they have stockholders to answer to. There was probably large pressure to show something, anything,  despite not being ready...
And maybe even with a blessing of the board: "... phone manufacturers do it all the time, so can we.."

[Fungus]

I think why this premature push happened..

The reason is obvious: "November"

[markone]

Now they have stockholders to answer to. There was probably large pressure to show something, anything,  despite not being ready...
And maybe even with a blessing of the board: "... phone manufacturers do it all the time, so can we.."

This is something that i'm sadly used to, lot of work rushed out of the door (under high management pressure) to meet deadlines commitments, with the certainty that there will be consequences  ...

Nowadays this is the main tragedy for FW developers, marketing promise and sell the impossible, than R&D has to keep the pace ... and sometime you loose the customer.

[bob808]

Yeah once they take your money the don't have any real incentive to fix it, or fix it quickly. They're not getting anything out of it, anymore. 
This was an issue with computer gaming. Games would release barely playable and you'd have to hope they'd release an update fixing the issues. This was solved by offering games as a service. Always connected to the internet, they keep selling you stuff in the game, and seems to make sense. Games get better in time, they make more money.
Wouldn't be surprised if oscilloscope manufacturers would at least think about this, if not try it. You get the hardware for relatively cheap but you need a monthly subscription. They could find a way to make it work, upside being good software support. Kind of dystopic tho. 

edit:
If we take this HDO1k/4k example in reality Rigol is a hardware making company trying to sell their hardware with somewhat functioning software. Just that all their hardware on the 1k/4k series is basically the same, and they use some software tricks to better monetize them.
Ideally they'd sell us the hardware and have truly open software, or at least leave the enthusiasts in the userbase to also get an alternative open-source app going on their hardware. Android/RK3399 fits the bill for this. But then again they wouldn't be able to sell the (relatively) same hardware for such large price differences (take HDO1074 vs HDO4804).

[TK]

Are you opening it?

Unfortunately no, in case I need to return it

[TK]

I received my HDO1074 from Valuetronics in the US

Perfect!
Please let us know if the "upgrade" method from this thread is working.

adb works and I got the file with the private key.  I used the go program to generate the license codes, but did not try applying them, as they are for HDO4K...

[bob808]

anything interesting in logcat? can you get the dtb file?

[tv84]

but did not try applying them, as they are for HDO4K...

That's irrelevant. As stated before, the FW doesn't check that designation.

[trinacria]

Does the riglol upgrade work yet? Or is it still a work in progress? Can someone report if it has worked for them?

[lgo51]

Ditto - inquiring minds need to know   

Does the riglol upgrade work yet? Or is it still a work in progress? Can someone report if it has worked for them?

[skander36]

adb works and I got the file with the private key.  I used the go program to generate the license codes, but did not try applying them, as they are for HDO4K...

Did you check? In case they are not working for HDO1K you should get an error message. I don't think you will brick something.
Or you just returned it?

[black_cat]

Mini Desktop
Gesture(手势导航)

[tv84]

Does the riglol upgrade work yet? Or is it still a work in progress? Can someone report if it has worked for them?

If you are looking for someone who used the keygen in this thread to license his HDO, you can see it here.

[maxwell3e10]

Does the riglol upgrade work yet? Or is it still a work in progress? Can someone report if it has worked for them?

If you are looking for someone who used the keygen in this thread to license his HDO, you can see it here.

Q: Does one really need adb.exe? How is it different from using telnet and su?

[trinacria]

If you are looking for someone who used the keygen in this thread to license his HDO, you can see it here.

Oops, I realize now that I forgot to specify "for the 1k". At least we now have pics for both.

[bob808]

https://play.google.com/store/apps/details?id=com.id.doom3bfg&gl=US
Can you run it?

[markone]

Here is the lic gen ... just needs the key file from the device to work ....
The device id being field 0 is just a guess as the code ignores that field anyways ...

Worked like a charm and couldn't possibly be easier

Tools used:

• Android SDK Platform Tools
• Go compiler

Usage [Windows]:

Code: [Select]

[b]./adb.exe connect [scope-ip]:55555
./adb pull /rigol/data/Key.data
go run .\rgtool.go
insert generated codes via SCPI interface on scope-website[/b]


A couple of question about that :

1) this script works also with HDO1000 scopes ?
2) what does mean "insert generated codes via SCPI interface on scope-website" ?

[skander36]

Rigol EU keep it's promise and delivered the HDO1072 scope today.
Attached is the file rigol.go modified for HDO1000. (just two options from the whole list - BW7T20 and RLU).
For reverting to factory license configuration: :SYSTem:OPTion:UNINSTall.
Many thanks to AlphaRne and all that helped with this!

The scope is pretty impressive with this new UI, low noise frontend, and  sturdy aspect, and not the last web interface which is as fast as those from RTB2k series.
Cons: noisy fan.

LE: @markone - is about the web interface (SCPI Panel Control)