Products > Test Equipment
Need help hacking DP832 for multicolour option.
WhichEnt2:
tossu, how do you look into DG1000Z firmware? I tried the python version of descrambler, but output is a complete mess, not anyting readable in strings output at all.
ealex:
thanks for the hack.
quick hint for linux users: if you connect it via USB it will be detected as an usbtmcX device:
--- Code: ---[38355.860413] usb 5-1.2: config 1 interface 0 altsetting 0 endpoint 0x81 has an invalid bInterval 80, changing to 10
[38355.860415] usb 5-1.2: config 1 interface 0 altsetting 0 bulk endpoint 0x82 has invalid maxpacket 64
[38355.860417] usb 5-1.2: config 1 interface 0 altsetting 0 bulk endpoint 0x3 has invalid maxpacket 64
[38355.861908] usb 5-1.2: New USB device found, idVendor=1ab1, idProduct=0e11, bcdDevice= 0.02
[38355.861909] usb 5-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[38355.861910] usb 5-1.2: Product: DP800 Serials
[38355.861912] usb 5-1.2: Manufacturer: Rigol Technologies.
[38355.861913] usb 5-1.2: SerialNumber: DP8C163953058
[38355.939460] usbcore: registered new interface driver usbtmc
--- End code ---
it's a simple char device -> you can use echo and cat to access it:
--- Code: ---# echo ":SYSTem:VERSion?" > /dev/usbtmc3
# cat /dev/usbtmc3
1999.0
^C^C^C^C
# echo ":PROJ:SET MODEL,DP832A" > /dev/usbtmc3
--- End code ---
it works with a FAT16 partition on a newer USB stick - just make it the first partition on the stick
tv84:
--- Quote from: tossu on April 07, 2019, 02:15:07 am ---It seems you got a hang of my hack pretty quickly before any explanation. I assume you got figured it out completely as you were able to check it for other models. Did the magic values help? What's the another specimen? Could you tell how did you thought I did it? I haven't really read other Rigol hacking threads so I might be asking some stupid questions. If that's the case, please point me to the right direction.
--- End quote ---
You took advantage of my parsings but you deserve full credit for this discovery! :clap: (the main reason of my parsings is to allow the kind of work you did)
In the meantime, the method has been confirmed to work on DG1000Z (as expected, even with a different sector). Of course, I was only able to somewhat understand what you did based on the magic values that you published. Even after your explanation is not something very easy to recreate without diving into the MQX toolchain.
The other specimen can be used, for example, in the DS1054Z and also in the MSO5000/7000 (it's for ARM only)
You can have a taste of it, here:
https://www.eevblog.com/forum/testgear/rigol-ds1000z-firmware-patch-plugins/msg1473517/#msg1473517
Based on known Rigol's way of doing things, it was not hard to figure out what you had accomplished (even if you were not fully aware at the time). Without previous knoweledge of Rigol hacks it's even more amazing!
Even the "brute-force" method of the file in the disk is poetry. BTW , it wouldn't work in the other specimen because the sector is one of the disk reserved sectors.
2N3055:
--- Quote from: tv84 on April 07, 2019, 10:13:33 am ---
In the meantime, the method has been confirmed to work on DG1000Z (as expected, even with a different sector).
--- End quote ---
Does DG1000Z work with same magic sector as DP800 or it is another one.. Syntax for a model command is the same I presume?
Thks!
tv84:
--- Quote from: 2N3055 on April 07, 2019, 10:37:03 am ---
--- Quote from: tv84 on April 07, 2019, 10:13:33 am ---
In the meantime, the method has been confirmed to work on DG1000Z (as expected, even with a different sector).
--- End quote ---
Does DG1000Z work with same magic sector as DP800 or it is another one.. Syntax for a model command is the same I presume?
Thks!
--- End quote ---
It's a different sector but tossu file works also with that sector. Syntax should be the same.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version