I could set the time base to 2ns/div without any hacking, but I made the hack.
At the first seem nothing changed but I checked the sys.inf file and the [DST type]dst1202b so I think it's fine.
At the first seem nothing changed but I checked the sys.inf file and the [DST type]dst1202b so I think it's fine.that's ok, all what one can see after hack is if the filename has been really changed from /dst1062b or /dst1102b to /dst1202b.
Well, and of course faster risetime/beter frequency response when measured.
I tried to switch dual-window mode after capturing a signal but the signal disappeared...if I use the dual-window mode from the beginning it's working. Is it a bug or I make something wrong?
Can someone validate this on actual "P" model? If so, you guys should send Hantek an email,
you have "P" model so you can check if new fw will work better.
If so, you guys should send Hantek an email, you have "P" model so you can check if new fw will work better.
Finally, is there a substitute (i.e. drop-in replacement) for the DM9000AEP chip? I can't seem to find it anywhere near (in online store from my country). The other components (RJ45 socket, magnetics, and 25MHz osscilator are not that critical) Thanks!
for DM9000AEP use ebay, e.g. item 171272339299 or 301232128882.
Is it worth to make the LAN access? Does it give extra function?
Before trying the BW hack, I tried to backup my DSO5102B ( bought some 3 weeks ago) using dso usb tool and nanddump. I entered those commands :
nanddump -o -b -f /mnt/udisk/dump/boot.bin /dev/mtd0
nanddump -o -b -f /mnt/udisk/dump/logo.bin /dev/mtd1
nanddump -o -b -f /mnt/udisk/dump/kernel.bin /dev/mtd2
nanddump -o -b -f /mnt/udisk/dump/root.bin /dev/mtd3
The first 3 worked somehow but nanddump remained blocked at root.bin. It was continuously writing in the USB device so I unplugged it without waiting the end ( after something like 45 min) and root.bin was over 1.9 Go. This seems to be a known bug but I don't know if it is related to some models or completely random. Anyway, here are the system info :
model : Hantek DSO5102B
sw version : 3.30.0 (140610.0)
hw version : 1010x5555830f
serial number : T 1G/012 016***
The DSO was updated once with the latest firmware from Hantek before attempting the backup.
I didn't find any solution to the issue in this ( quite long) thread so if there is another way to make a full backup, I'm opened to suggestions.Have a look there :https://www.eevblog.com/forum/testgear/hantek-hdg2002b-awg-5mhz-or-100mhz-let's-see!/msg476550/#msg476550
you should be able to run the three commands needed via the DSO-USB-Tool.
It just uses another version of nanddump that should work. The 4 files will be zipped in the dump.tar.gz file and you should be able to extract them on a PC with 7zip for example or on a linux machine with the tar command.
(root.log)
ECC failed: 0
ECC corrected: 0
Number of bad blocks: 2
Number of bbt blocks: 0
Block size 131072, page size 2048, OOB size 64
Dumping data starting at 0x00000000 and ending at 0x07900000...
OK thanks.
Is there a way to update the .up backup file to work on the 5000p's? How are they created?
After hacking the scope to 200Mhz, I flashed the 5202P firmware - even though it was the same version, it seemed to flash OK. But the bootup screen still shows the old model - is there a way to change that?
Do you mean 3.40.0(140208.0)?
re. 'digital filter', do you mean the optional 20Mhz bandwidth limit?
I have an extra yellow bar below the waveform when using Autoset (with Pk-Pk, Mean, Freq and Period readouts).
I also sometimes get a massive yellow box with tons of readouts that take up most of the screen. I haven't figured out yet what triggers that, or how to toggle it ...
First, System Info still lists the 5072p model - is that normal?