Hacking the Rigol DHO800/900 Scope

[AndyBig]

Today I spent many hours trying to add a color to the probe divider value on an enabled channel and have the value change color depending on whether the channel is on or off. I recompiled and reinstalled the application probably 200 times. I learned a lot of new and strange things about the DALVIK language )

[AndyBig]

Also take a look here
Sparrow/smali/com/rigol/scope/R$color.smali

lots of color definitions in that file too.

[roott@localhost scope]# grep "7f060029" "R\$color.smali"
.field public static final bg_channel1_color:I = 0x7f060029

I don’t just watch it, I add my names and meanings of colors and interface elements to it

[AndyBig]

rsync can be used on other side and get files via sshd. Same as scp command.

Yes, I didn't think about that

[Randy222]

Today I spent many hours trying to add a color to the probe divider value on an enabled channel and have the value change color depending on whether the channel is on or off. I recompiled and reinstalled the application probably 200 times. I learned a lot of new and strange things about the DALVIK language )

no leap year in a DHO. 

[norbert.kiszka]

Today I spent many hours trying to add a color to the probe divider value on an enabled channel and have the value change color depending on whether the channel is on or off. I recompiled and reinstalled the application probably 200 times. I learned a lot of new and strange things about the DALVIK language )

no leap year in a DHO. 

5 year later... TV news: some hackers managed to build DHO4804 oscilloscope from a DHO802.

[AndyBig]

no leap year in a DHO. 

Why not? Of course have

[norbert.kiszka]

I have idea to write script to automatically send created screenshots from scope to ssh or ftp. Somebody works on the scope, goes to other place with computer and all screenshots are already on local disk. I wrote this, because sometimes I have some nice ideas, which later I forget, so maybe somebody will remind me this later on this forum.

[flaotte]

at this point... just force it to spit out all the data over API and write linux based software for computer 

[AndyBig]

I re-created a project to change the application and transferred all the changes made to it to fix them in git. The project was posted on github - https://github.com/Andy-Big/DHO800_900_Sparrow_project

By the way, today I tried to decompile the application versions 00.01.01.00.00 and 00.01.02.00.02 and compare the resulting sources. Yes, there really are differences, but not so big that it would pose a problem when a new version is released. Of course, you will have to tinker for about an hour to make all the changes from the new version, checking that they will not spoil my changes, but this is not such a big problem, considering how “frequently” new versions are released

[norbert.kiszka]

at this point... just force it to spit out all the data over API and write linux based software for computer 

There are already bunch of different software on Linux for oscilloscopes (downloading, viewing and measurements of waveforms, remote screenshots, change settings via network and many more), so what is Your point?

[norbert.kiszka]

I re-created a project to change the application and transferred all the changes made to it to fix them in git. The project was posted on github - https://github.com/Andy-Big/DHO800_900_Sparrow_project

By the way, today I tried to decompile the application versions 00.01.01.00.00 and 00.01.02.00.02 and compare the resulting sources. Yes, there really are differences, but not so big that it would pose a problem when a new version is released. Of course, you will have to tinker for about an hour to make all the changes from the new version, checking that they will not spoil my changes, but this is not such a big problem, considering how “frequently” new versions are released

What are .so libs are for? Anyway, some little idiot-proof readme will be preety useful.

[AceyTech]

I have idea to write script to automatically send created screenshots from scope to ssh or ftp.

There are several here already using SSH or FTP to get screenshots, video recordings, and/or setup files from their scopes. Or even using the web control interface or with SCPI commands.
And there are some saving to NAS using NFS mount via busybox; bypassing the internal SDCard. 

You can search the forum here for examples, if you don't want to reinvent the wheel.

[AndyBig]

What are .so libs are for? Anyway, some little idiot-proof readme will be preety useful.

The largest one - libscope-auklet.so - implements all the operating functions of the oscilloscope. All work with the FPGA is done through it, saving and loading parameters, determining the model and the capabilities available to it, checking licenses and keys, and much more. Together with the FPGA, it forms the functional core of the oscilloscope.
The rest, judging by their names, are for working with .png images, for working with .pdf, for servicing the keyboard and indicators panel, general functions of C++ libraries.

Yes, I'll have to make some kind of readme

[norbert.kiszka]

What are .so libs are for? Anyway, some little idiot-proof readme will be preety useful.

The largest one - libscope-auklet.so - implements all the operating functions of the oscilloscope. All work with the FPGA is done through it, saving and loading parameters, determining the model and the capabilities available to it, checking licenses and keys, and much more. Together with the FPGA, it forms the functional core of the oscilloscope.
The rest, judging by their names, are for working with .png images, for working with .pdf, for servicing the keyboard and indicators panel, general functions of C++ libraries.

So You disassembled it and made some changes?

[AndyBig]

So You disassembled it and made some changes?

[norbert.kiszka]

So You disassembled it and made some changes?

Heh. I was suspecting this change in xml and graphic files. Eventually in app binary instead of FPGA. Quite big surprise.

[AndyBig]

Heh. I was suspecting this change in xml and graphic files. Eventually in app binary instead of FPGA. Quite big surprise.

Not only. Changes are also made to the application's executable files.

[norbert.kiszka]

Heh. I was suspecting this change in xml and graphic files. Eventually in app binary instead of FPGA. Quite big surprise.

Not only. Changes are also made to the application's executable files.

Disassembling takes much more effort than play with xml files. Big thx for sharing.

[AndyBig]

Disassembling takes much more effort than play with xml files. Big thx for sharing.

Changing resources alone won't get you far

[Randy222]

There is no rsync command in the oscilloscope system

there's also no less which is ridiculous and annoying. it should be easy, however, to install busybox there, which contains all those small utilities.
same for rsync actually.

The dho droid has toybox, but no less in there.

[Randy222]

BTW. print screen key on USB keyboard works. File path and name for example: [last file system]/media/0/Screenshots/Screenshot_20130118-090648.png

It does work, but on my 804 I had to change droid settings for screen pics, it was not set to internal storage, so prtscn was throwing err "cannot save image".

[norbert.kiszka]

BTW. print screen key on USB keyboard works. File path and name for example: [last file system]/media/0/Screenshots/Screenshot_20130118-090648.png

It does work, but on my 804 I had to change droid settings for screen pics, it was not set to internal storage, so prtscn was throwing err "cannot save image".

Thats little strange. Mine 924S never had this issue. Maybe different firmware version I guess.

[AndyBig]

So I did it! The channel widgets in the bottom panel now display the actual probe divider value that was set for the channel.

[norbert.kiszka]

Speaking of it. Another useful thing will be custom probe ratio. Like 11, 12, 13 but I think that probably can be hard. But... In some earlier firmware it was different, In 02.0.02 we have x20 x50 and somewhere before it was only powers of ten - so we can make diffs.

[Mechatrommer]

So I did it! The channel widgets in the bottom panel now display the actual probe divider value that was set for the channel.

do we really need the decimal place?