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

[tinhead]

Hello, Im running HW 0x555583e8 SW 120224.0 and have been using my scope a lot recently, being no master I found an annoying bug,

tthere is major bug inside this firmware, or actually last (already 3) firmwares. The reason is that Hantek/Tekway
is working on the timebase procedure - the whole part has been re-written and does have bugs.
They has been notified about and actually they knew it. The good news it - they working on several bugs now,
so soon new firmware with fiex timebase will be available (and probably already the version 1:2:5 instead of 2:4:8 timebase ratio)

When having just captured a single seq and pressed any menu button, the graph gets compressed in order to get space for the menu bar, this seems Ok, but if you want to measure time with the cursor, you end up measing an horizontally (time) compressed  graph, aka, you measure more time than the actual real time.

cursor is screen position nd not data position related, when you change screen size the data is not valid anymore.

[Mark]

Mark

shit, i have to answer your PM ...

There is newer firmware since day or two available on Hantek website, it does not change that much (if any)
but it is GPL compliant^^

Regards the measurments, sure click Meas button, chose with blue cursor keys the item you wish to change, click F5
to modify and select with F1 the source of measurments.

There are 4 measruments visible in same time, however you can scroll with these blue cursor keys between 4 pages - so you can setup on page 1 and two channel1 and pages 3 and 4 channel 2 - then in principle just scrol up and down between
pages.

Thanks for the reply tinhead. 
The problem is, I have done what you said, but it does not change to ch2 when I press F1 (yes, ch2 is on). 
Even when channel 1 is off and channel 2 is th eonly one displayed, it won't display amy ch2 measurements or allow ch2 to be selected by pressing F1. 
I will upgrade the firmware and see if this is fixed. 

(PS, I didn't send you a PM, so it must have been someone else). 
Thanks again, 

[carloscuev]

tthere is major bug inside this firmware, or actually last (already 3) firmwares. The reason is that Hantek/Tekway
is working on the timebase procedure - the whole part has been re-written and does have bugs.
They has been notified about and actually they knew it. The good news it - they working on several bugs now,
so soon new firmware with fiex timebase will be available (and probably already the version 1:2:5 instead of 2:4:8 timebase ratio)

Thanks tinhead ! I would love if I could have vertical position for each channel in coarse mode, do you know if it's a future planned feature?

[Crenwick]

Hi,

I just downloaded the FW from Hantek and this is the filename dst1kb_2.06.3_15202b_fact(120423.0).up

Is this a new one ?

Regards,

[Mark]

Mark

shit, i have to answer your PM ...

There is newer firmware since day or two available on Hantek website, it does not change that much (if any)
but it is GPL compliant^^

Regards the measurments, sure click Meas button, chose with blue cursor keys the item you wish to change, click F5
to modify and select with F1 the source of measurments.

There are 4 measruments visible in same time, however you can scroll with these blue cursor keys between 4 pages - so you can setup on page 1 and two channel1 and pages 3 and 4 channel 2 - then in principle just scrol up and down between
pages.

Thanks for the reply tinhead. 
The problem is, I have done what you said, but it does not change to ch2 when I press F1 (yes, ch2 is on). 
Even when channel 1 is off and channel 2 is th eonly one displayed, it won't display amy ch2 measurements or allow ch2 to be selected by pressing F1. 
I will upgrade the firmware and see if this is fixed. 

(PS, I didn't send you a PM, so it must have been someone else). 
Thanks again,

Installed 120423.0 and it has fixed the above issue, thanks.  I now have measurements on channel 2. 

I updated my previous post with this bug which still remains with 120423.0 firmware for DSO1202B handheld. 
To prevent it from being lost on the previous page I'll copy it here again in the hope someone can verify the same on their scope, it would be interesting to know if this "bug" also exists on the desktop models. 

When viewing a low freqwave, such as the 1khz probe compensation output, trigger on the rising edge and scroll the waveform to view the falling edge in the middle of the screen (I want to do this to measure jitter in the pulse width).  Start with something like 400us/div.  Trigger marker shows approx 500us from rising edge trigger to falling edge in middle of screen.
Now change the timebase to 20us/div and note how you have to scroll the waveform again to get the falling edge in the middle of the screen again, and now the time between the trigger and the falling edge is displayed as 350us.
At 8us/div, the time from rising edge trigger to falling edge is displayed as 290us.
At 4us/div, the time from rising edge trigger to falling edge is displayed as 270us.
At 2us/div, the time from rising edge trigger to falling edge is displayed as 260us.
At 800ns/div, the time from rising edge trigger to falling edge is displayed as 255us.  etc etc.  Should be 500us obviously. 

[paul]

@Mark

My DSO5102 desktop scope behaves the same. I think this is a long standing bug, I posted about it here :- 

https://www.eevblog.com/forum/general-chat/hantek-tekway-dso-hack-get-200mhz-bw-for-free/msg94907/#msg94907

But I think you described it better than I did.

Paul.

[Mark]

@Mark

My DSO5102 desktop scope behaves the same. I think this is a long standing bug, I posted about it here :- 

https://www.eevblog.com/forum/general-chat/hantek-tekway-dso-hack-get-200mhz-bw-for-free/msg94907/#msg94907

But I think you described it better than I did.

Paul.

Thanks Paul.  I did read the full thread before buying, but must have missed your post. 
As you note the bug is better with 1M point memory enabled, but it makes the scope very slow to use, I don't know if they have a slower processor on the handhelds to save battery life, but I have to hold some buttons for about 1 sec when using 1M or the keypress doesn't register. 
I also bought an OWON 8102 at the same time and it doesn't have this bug even with only 10k memory enabled. 

[Mark]

Installed 120423.0 and it has fixed the above issue, thanks.  I now have measurements on channel 2. 

The DSO1202B crashed at the weekend while I was playing around with it, and when it rebooted I had lost measurements on channel 2 again!  Firmware still showed the upgraded number. 
Flashed firmware again and it's showing channel 2 measurements again.  Maybe there is a way of resetting the scope which will fix this if it happens again instead of reflash. 

[tinhead]

Installed 120423.0 and it has fixed the above issue, thanks.  I now have measurements on channel 2. 

The DSO1202B crashed at the weekend while I was playing around with it, and when it rebooted I had lost measurements on channel 2 again!  Firmware still showed the upgraded number. 
Flashed firmware again and it's showing channel 2 measurements again.  Maybe there is a way of resetting the scope which will fix this if it happens again instead of reflash.

Use the attached usb tool (special version of www.dreisiebner.at/dso-usb-tool ), to delete delete the file /param/sav/run*  (which is the setting profile)
In principle even the "default" button (save button and then F4 or F5?) should do the same,
if not try to delete the file above. You can also delete the sys.inf and then reboot:


rm /param/sav/r*
rm /sys.inf


EDIT: The attached usb tool is actually special version for handhelds, not
everything works but shell/settings/screenshot are already ok.
You will need to remove the "zip" in file names and use winrar to unpack it.

[quarros]

Hi guys.

This month my Hantek DSO5102B decided enough is enough, and froze up (knobs not working) so i had to open it up, hack it with my Seeeduino via UART, but when I did I found something unexpected. On the right side (top view) of the scope main PCB I saw a MicroSD card slot facing the buzzer. This got me curious whether it is something usable or not because i saw the pads on other images but in my case it was populated. Should I desolder the buzzer and try it out?

[tinhead]

right, the SD slot is something what BM/BVM model are using.

In principle it can be used on B models, however not from firmware itself (shell for sure).
When you wish to use it from firmware level you will need to have different kernel - 2.6.30.4 (which is the case on BM/BMV models),
this is becuase the firmware is checking the kernel version while displaying/hidding menus or allowing/disallowing access to functions.

For sure you need additionally to have same "license set" in your EEPROM, but thi is mariginal change only.
Now as the kernel sources are available you can in piinciple compile your own 2.6.30.4 kernel (and when you so far then you can ask me how
to enable licenses in eeprom).

[quarros]

(and when you so far they you can ask me how to enable licenses in eeprom).

Sorry can you rephrase that? Im not sure what you mean.

[tinhead]

(and when you so far they you can ask me how to enable licenses in eeprom).

Sorry can you rephrase that? Im not sure what you mean.

and when you so far then you can ask me how to enable licenses in eeprom

[quarros]

(and when you so far they you can ask me how to enable licenses in eeprom).

Sorry can you rephrase that? Im not sure what you mean.

and when you so far then you can ask me how to enable licenses in eeprom

Ok I think I got you. Thanks

I was just curious about the possibility. However isn't it possible with the current kernel to create a mounting point in the filesystem that points to the SD card as an extension of the root filesystem? Because if it is, than we could use that to record waveforms on the scope I believe. But maybe it is just wishful thinking on my part.

[tinhead]

(and when you so far they you can ask me how to enable licenses in eeprom).

Sorry can you rephrase that? Im not sure what you mean.

and when you so far then you can ask me how to enable licenses in eeprom

Ok I think I got you. Thanks

I was just curious about the possibility. However isn't it possible with the current kernel to create a mounting point in the filesystem that points to the SD card as an extension of the root filesystem? Because if it is, than we could use that to record waveforms on the scope I believe. But maybe it is just wishful thinking on my part.

in the latest firmware, utility -> page3/3 -> Option -> Wave you can already save a lot of waveforms.
When set to "Flash" the internand NAND will be used ( /param/sav/wave_sav/ directory ). This is already cool
, and you can already save 999 waveform like that ... but when you e.g. set memory depth to 1Mpoint such saved
waveform takes already 1.5MByte in NAND memory .. so be careful

SD and USB options in this menu can be only selecred WHEN you have kernel 2.6.30.4 AND the SD license installed,
which is in principle only one entry in EEPROM.

Btw, in case you build your own 2.6.30.4, the mount point for SD card need to be /mnt/sd

[Mark]

Use the attached usb tool (special version of www.dreisiebner.at/dso-usb-tool ), to delete delete the file /param/sav/run*  (which is the setting profile)
In principle even the "default" button (save button and then F4 or F5?) should do the same,
if not try to delete the file above. You can also delete the sys.inf and then reboot:


rm /param/sav/r*
rm /sys.inf


EDIT: The attached usb tool is actually special version for handhelds, not
everything works but shell/settings/screenshot are already ok.
You will need to remove the "zip" in file names and use winrar to unpack it.

Thanks tinhead, good suggestion about the setting profle.  Thanks also for the usb tool, I will have a play with it later. 

[prpplague]

Hi guys.

This month my Hantek DSO5102B decided enough is enough, and froze up (knobs not working) so i had to open it up, hack it with my Seeeduino via UART, but when I did I found something unexpected. On the right side (top view) of the scope main PCB I saw a MicroSD card slot facing the buzzer. This got me curious whether it is something usable or not because i saw the pads on other images but in my case it was populated. Should I desolder the buzzer and try it out?

if you plan on hacking around with your Hantek on regular bases, you might want to look at the procedure a number of people have used to add an easy to access uart connection to their das_oszi:

http://elinux.org/Das_Oszi_3.5MM_Uart

Dave

[cww]

Hi  All

Looked through the 80 some pages on this topic and I haven't been able to deduce what part of the saga applies here and now. I am teetering between the Hantek and the Owon. I like the Hantek because of it's features and because it runs Linux. The Owon doesn't have the split zoom and update speed but it offers battery operation which would be handy for some things that I do. Kinda like a cordless drill.
How about a snapshot of the current situation?

[tinhead]

I am teetering between the Hantek and the Owon. I like the Hantek because of it's features and because it runs Linux. The Owon doesn't have the split zoom and update speed but it offers battery operation which would be handy for some things that I do. Kinda like a cordless drill.
How about a snapshot of the current situation?

well, then buy Hantek Handheld, like DSO1062B, 1102B, 1202B (or as BV verion) - you will get battery, split zoom and Linux.

[cww]

Not too big on the handheld scopes, just not my thing.  But what I am looking for is: If I order the DSO5102B  Hantek today from Circuit Specialists, which I almost did last night, what can I expect.

Does the 200 Mhz hack still work.
Bugs?
Updates since the reviews?
I did look through the backlog but it's hard to follow what would apply to what's available today.

[quarros]

if you plan on hacking around with your Hantek on regular bases, you might want to look at the procedure a number of people have used to add an easy to access uart connection to their das_oszi:

http://elinux.org/Das_Oszi_3.5MM_Uart

Dave

Thank you for the suggestion.
I have thought about something similar, but that is an ideal solution.
Thanks

[tinhead]

removed

[NCG]

Nice!

Considering the amount of time all this has taken - is there Tinhead Beer Fund somewhere to receive small tokens of appreciations ?

[tinhead]

Nice!

Considering the amount of time all this has taken - is there Tinhead Beer Fund somewhere to receive small tokens of appreciations ?

well, when you like my work scroll up and give me 5 stars!

[Parsley]

Nice!

Considering the amount of time all this has taken - is there Tinhead Beer Fund somewhere to receive small tokens of appreciations ?

well, when you like my work scroll up and give me 5 stars!

DONE! Great job, thank you! :-)