Hantek - Tekway - DSO hack - get 200MHz bw for free

[tinhead]

Do you know if both of the latter models are hackable to 200mhz with your method?

if you would read the thread or use search you would find out that there is still everythign hackable,
no matter what model.

I wouldn't mind the extra memory but do you know what the video does for BMV model?

playing videos, put the usb flash drive with some p0rn and play on DSO during lunch break.

[tlu]

Thanks Tinhead for the answer. I think I could live without the porn and pick up the BM with an extra 1M of recording time.

[tinhead]

But, but, but, Extech is soooo ISO9000 certified. That is for sure worth the higher price ... *ducks and runs*

hehe yeah, luckily we know that ISO9001 certificated does not means anything about quality of products.
I could tell you really bad sotry about so called certificates of what so ever from Chinese manufacturers,
as well Hantek, but i think most poeple don't need to read once agains such things - we all know that
most of these cheap products are for example not properly calibrated (like DMM in these Hantek Handhelds).
So maybe is Extech so expensive because they need to pay "US proven philips screw driver an one work hour"
to calibrate DMMs and to print cal papers - who knows.
What's definitely different is the enclosure color, but ehm still lot of $$$ in price difference.
Even the batter pack costs 129.99$, for that price is must be packaged by a virgin girl.

[Fet]

luckily we know that ISO9001 certificated does not means anything about quality of products.

2nd that,, 

More like;;;;;;;;;;;;;;;;;;;;;;;;

LOTs of Paper Trail!  Translated, "he went that way!" <----  /\  ---->
                                                                                               l
                                                                                               l

Or ,
Sorta  Sounds like a Woodstock, http://en.wikipedia.org/wiki/File:Woodstock_redmond_stage.JPG , went to Washington DC moment , http://en.wikipedia.org/wiki/File:WhiteHouseSouthFacade.JPG .


I wanted a Hantek DSO1062B and then I learned that in fact “Flir” was given or entered into an Exclusive agreement with Hantek to sell Hanteks under the “Extech” name, here in The States.

So, Hum?? Lets see, at about Triple the original price,

Kinda lends one to wonder if “Flir” was awarded some US Government fulfillment ~ Supply Contract and Flir changed the name to protect the , Hum,    Aha? , Hum?, Oh!

Oh, so cynical , hUm!

[albertr]

Gentoo Linux kernel: 3.5.0
Xorg
LXDE - Desktop environment
XChat -  IRC client
terminal windows behind


Now we got almost everything, working on fpga configuration...

open source DSO soft will be directly for fbdev(lcd) not for xorg due to memory usage, this is quite far future but everything is going good

flodins,

I'm very interested in your work. Any progress update since July?

-albertr

[tlu]

Wow, is that really gentoo linux running on the hantek scope?

[carloscuev]

Hello Tinhead, sorry if you've said it but I couldn't find it in the last 5 pages. Does the older HW version 0x555583E8 could be hackable to a MSO ?
Thanks !

[tlu]

Hello Tinhead, sorry if you've said it but I couldn't find it in the last 5 pages. Does the older HW version 0x555583E8 could be hackable to a MSO ?
Thanks !

I'm also interested in that hack as well.

[jakezilla]

Hello Tinhead, sorry if you've said it but I couldn't find it in the last 5 pages. Does the older HW version 0x555583E8 could be hackable to a MSO ?
Thanks !

I'm also interested in that hack as well.

I am also interested in buying a MSO (Hantek MSO5062D from aliexpress.com to be exact) and doing this hack to it, but I am also having an issue trying to find the info in this thread. A Search in Thread button would be nice...

https://www.eevblog.com/forum/general-chat/hantek-tekway-dso-hack-get-200mhz-bw-for-free/msg146070/#msg146070 - In this post tinhead talks about adding the MSO board to a hacked DSO, so a hacked MSO can be created, but can you start with an MSO?

[carloscuev]

I found a bug I am unable to reproduce but I was stuck in 40ms per division and when trying to switch to 20ms per division or less, the 2 channels stopped working, even after rebooting several times, trying to disable and re-enable channels didn't worked, I entered Horizontal Menu and moved some things and knobs and suddenly I got my signals again. I'll be tring to find out how to reproduce this bug and post steps here if someone is interested.

[tlu]

Maybe it just needed a little time to adjust to the new time base settings. Did it totally locked up on you? Which firmware are you on? Did you tried to go to the lowest time base setting when you got stuck?

Which firmware are you on? I would like to see if I could reproduce what you are seeing on my Hantek to see if this is a bug or just an isolated issue with certain scope. If it is a bug we should reported to have it fix in the next release of the firmware.

[carloscuev]

I'm using the newest 120808.2 firmware, I waited long enough (~30seconds) before starting to push buttons. Not totally locked, it I went back to 40ms per div. The 2 channels reappeared.

[tlu]

Well, since you can't reproduce this error it will be hard to tell if this is a real bug in the firmware or not. Personally, I have not ran into that situation while doing measurements and changing time base scale.

[Jane]

Can anyone  let me know what the differences are between Hantek  and Tekway oscilloscopes?
Which is better Hantek  or Tekway?
(I heard Hantek has a better software but sometimes hangs.)
And is it true that hardware is the same?
ANd which one has a better( more proffesional) support?
Thanks

[Freeze]

First of all thank you very much for this great work and guide.

I bought a PCE DSO5062B and followed the steps to change it to DSO5202B.
This worked very well. The bandwith increased, but I've got the problem that the device restarts every 10 seconds even if I'm not connected to the UART anymore (also the UART-USB-converter is unplugged).

I've disabled the watchdog in the init.d and now the reboots are gone.

The question is, why is the watchdog resetting the device?


Here the contents of the relevant files:

Code: [Select]

[DST type]dst1202b
[soft version]2.06.3(120808.0)
[fpga version]0x555583eb
[start time]15
[update time]1
- /sys.inf 1/5 20%


Code: [Select]

/dst1202b
- /tmpdst 1/1 100%


Code: [Select]

dst1202b
- /logotype 0/0 100%


Code: [Select]

pce_DSO5202B
- /logotype.dis 1/1 100%


Thank you very much in advance.

[tinhead]

The question is, why is the watchdog resetting the device?

this is exactly what a watchdog have to do: if the main process, in the case of this DSO the dso.exe exectable,
terminates the watchdog have to re-initialize the device, which is on a these DSO reboot (to ensure that memory has been cleaned-up and all necessary sub-processes restarted properly).

[tinhead]

Hello Tinhead, sorry if you've said it but I couldn't find it in the last 5 pages. Does the older HW version 0x555583E8 could be hackable to a MSO ?
Thanks !

I'm also interested in that hack as well.

no, the hw 0x can not be hacked to MSO. The reason is very simple, the i/o header on hw0 is not having all necessary SoC pins connected.
Sure, you could use additional PCB with small µC and Flash memory to configure the FPGA on the MSO PCB (you can't use the rbf file to program config device, a µC is here necessary),
and sure you could maybe connect missing pins (maybe) with soem wires but that's not a good solution at all - even not for test - therefor my answer is "no way"

[Freeze]

The question is, why is the watchdog resetting the device?

this is exactly what a watchdog have to do: if the main process, in the case of this DSO the dso.exe exectable,
terminates the watchdog have to re-initialize the device, which is on a these DSO reboot (to ensure that memory has been cleaned-up and all necessary sub-processes restarted properly).

Then the question is, why is dso.exe terminated? Respectively, how can I be sure that this is really the cause for the watchdog reset?
The device is working fine after disabling the watchdog, so I don't understand why the watchdog is resetting it.

You're right. The device really hangs up.
Hm, what could be the cause for this?

Running it as DSO5102B seems to work. But why is DSO5202B not working?

I've got resets with DSO5102B also. Thats really disappointing

[noWhereMan]

Hi,

is http://www.pce-instruments.com/deutsch/messtechnik-im-online-handel/messgeraete-fuer-alle-parameter/oszilloskop-pce-holding-gmbh-speicheroszilloskop-pce-dso5062b-det_257116.htm?_list=kat&_listpos=4 same as Hantek DSO5102B?

[Freeze]

Hi,

is http://www.pce-instruments.com/deutsch/messtechnik-im-online-handel/messgeraete-fuer-alle-parameter/oszilloskop-pce-holding-gmbh-speicheroszilloskop-pce-dso5062b-det_257116.htm?_list=kat&_listpos=4 same as Hantek DSO5102B?

I bought exactly the same. It's a Hantek DSO5062B / Tekway DST1062B with 60 MHz bandwith as mentioned in the description of the device.
I tried to change it to DSO5102B/DSO5202B, but sometimes it's restarting. Don't know why.

[beard]

Hello Everybody!
I have been reading this thread for a while and finally purchased my DSO1062b and decided to hack it.
It has firmware version 2.01.1 (120909.0) and hardware version 0x555583e8
The funny (or maybe not so funny) thing is that when I connect to it through the UART interface using minicom, I get a constant stream of messages:
power_ioctl:IOCTL_SCAN_POWER_BI_TOUT:1                                         
power_ioctl:IOCTL_SCAN_POWER_BI_TOUT:0   
which come with ~1 second interval
I have not been able to figure out what those messages are supposed to mean, when I kill dso process, the messages stop, and the oscilloscope reboots in a few seconds (as expected).
I have been able to apply the hack successfully and all the functions seem to work fine, but those messages bother me - does anyone have any idea what these "power_ioctl" messages may mean?
Thank you in advance!

P.S. If anyone needs the original firmware from my scope - I have backed it up and can share.

[tinhead]

I have been reading this thread for a while and finally purchased my DSO1062b and decided to hack it.
It has firmware version 2.01.1 (120909.0) and hardware version 0x555583e8
...
P.S. If anyone needs the original firmware from my scope - I have backed it up and can share.

oh yes, i don't hae 120909.0 yet, so if you don't mind make a backup and send me PM with download location.

The funny (or maybe not so funny) thing is that when I connect to it through the UART interface using minicom, I get a constant stream of messages:
power_ioctl:IOCTL_SCAN_POWER_BI_TOUT:1                                         
power_ioctl:IOCTL_SCAN_POWER_BI_TOUT:0   
which come with ~1 second interval
..
I have been able to apply the hack successfully and all the functions seem to work fine, but those messages bother me - does anyone have any idea what these "power_ioctl" messages may mean?

yes, they coming from the driver "dso-power.ko", which is power management driver. You can find it in the
handheld GPL kernel sources (DSO_handscope\linux-2.6.30.4_640x480_lz_120410.tar.gz) in drivers/char/EmbedSky_power_man.* files

[tinhead]

The question is, why is the watchdog resetting the device?

1- you got DOA device
2- you screwed something up (typo?), which is causing somewhere an error in the dso.exe
3- something is different in the pce-instruments firmware version (whcih i doubt, but who knows, maybe Hantek screwed something up)

[beard]

Hello Tinhead,

I sent you a PM with the download link.
Thank you very much for your comment, I will try to figure out what those messages mean, but are they normal, have you seen those before?

[Freeze]

The question is, why is the watchdog resetting the device?

1- you got DOA device
2- you screwed something up (typo?), which is causing somewhere an error in the dso.exe
3- something is different in the pce-instruments firmware version (whcih i doubt, but who knows, maybe Hantek screwed something up)

I've flashed the original firmware that I've backed up with the fw3dump tool and did the hack one more time.
Unfortunately the behaviour is the same. So I don't think it's caused by doing something wrong in the software changes from dst1062b to dst1202b.

Is it possible that this is a hardware problem? I mean that the components of this particular device can't handle this high bandwidths?

The silly thing is that I needed to solder cables in the appropriate pinheader holes of the UART, thus the warranty should be gone...