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

[bbf]

Hello,

I have a problem with my Tekway DST1062B - the scope hangs with white screen after running for about 30 seconds to 30 minutes. I have tried upgrading the factory firmware to version 2.06.3 (111202.0) - no change. I have not tried to hack the scope yet.

Hardware version shown is 10050x555583e8, serial number T 1G/005 003613.

Do you have any advice? Thank you!

Ivo

[aghp]

Hello,

I have a problem with my Tekway DST1062B - the scope hangs with white screen after running for about 30 seconds to 30 minutes. I have tried upgrading the factory firmware to version 2.06.3 (111202.0) - no change. I have not tried to hack the scope yet.

Hardware version shown is 10050x555583e8, serial number T 1G/005 003613.

Do you have any advice? Thank you!

Ivo

HW fail can not repair with upgrading FW!

Nearly sure it is main board fail. I have seen this situation "more than one time".
Take contact seller or if seller do not care then to Hantek service for repair or spare part main board. (It must be free or nearly free to you if warranty is still valid)

[tinhead]

Backup tool for Hantek Handhelds : DSO1062B/BV/S, DSO1102B/BV/S, DSO1202B/BV/S

- download the attached file and unzip the dso1kb_backup_tool.up (MD5 41873654111d34ef71c6f7ecc10a9951)
- copy the dso1kb_backup_tool.up to flash drive, ensure nothing else on that drive
- insert flash drive into Handheld usb port
- run firmware update (Utility, Page 1/5, Uptdate and F4 to confirm)

Handheld will reboot automatically after "firmware update" is ready (in this case backup of firmware).
Now you can remove flash drive and save the content in a secure location.

[pgup62]

   

Hello,

    I have a problem with my Tekway DST1062B - the scope hangs with white screen after running for about 30 seconds to 30 minutes. I have tried upgrading the factory firmware to version 2.06.3 (111202.0) - no change. I have not tried to hack the scope yet.

    Hardware version shown is 10050x555583e8, serial number T 1G/005 003613.

    Do you have any advice? Thank you!

    Ivo

This white screen can come from 3.3V regulator that should perform a voltage between 3.2~3.4. If this voltage is lower than 3.2V,then it may produce this white screen.
Elec3i has met this kind of behaviour already and has changed the power unit in some DSO to avoid this, It is why we test our devices one by one with at least 72 hours burn-in period...

[bbf]

Hello pgup62,
thank you very much! It seems that some tuning of the 3.3 V regulator circuit helped. (I hope )

[pgup62]

Yes, sure it will 
For now in Elec3i, we are promoting hand-held DSO1102B/DSO1062B and bench scopes DSO5102B (hw: 10070 0x555583e9) at 489.00 EUR net price !!! for some time.

[tinhead]

For now in Elec3i, we are promoting hand-held DSO1102B/DSO1062B

Pascal,

as already asked here :

https://www.eevblog.com/forum/product-reviews-photos-and-discussion/hantek-dso1202b-or-owon-sds7102/msg87209/#msg87209

- are these Handhelds with or without LAN?
- are these Handhelds true CATIII certified (KTK-1, KTK10 fuses + protection or simple 250V fuses?)

[stef_teta]

Hi,

I recently bought a DST1102B for my hackerspace and few ppl have used recently. After their use (sampling/recording/etc) the oscilloscope is freezing, randomly. Really randomly. On my own opinion, I think there is some broken samples still remaining on the file system, cause when I do a "df" on the debug console, I got :
Filesystem      1K-blocks      Used      Available       Use        Mount
/dev/root        63152          63152          0             100%        /
[...]

I would like to know :
- Where are recorded the samples before recording them on an usb key ?
- Is it normal to have the root filesystem used at 100% ?
- Have you ever met this problem before ?

Thanks a lot, waiting for your answer

... Later, I will put the hack on the track. Later

[tinhead]

I recently bought a DST1102B for my hackerspace and few ppl have used recently. After their use (sampling/recording/etc) the oscilloscope is freezing, randomly. Really randomly.

heh, you should probably kill some ppl for that

On my own opinion, I think there is some broken samples still remaining on the file system, cause when I do a "df" on the debug console, I got :
Filesystem      1K-blocks      Used      Available       Use        Mount
/dev/root        63152          63152          0             100%        /

I would like to know :
- Where are recorded the samples before recording them on an usb key ?
- Is it normal to have the root filesystem used at 100% ?
- Have you ever met this problem before ?

- tmp fs
- no, it should be never like that, typical used space is about 40-50%
- no never ever

You should check root fs for strane files, look in /param/ (and subdirs), /mnt (and subdirs if any) and / itself,
if you don't know if specific files are necessary or not just ask here, i will answer then.

[niebieski20]

Hi
I just receive my DSO5102B
First I change it into DSO5202B and everything works great. Thanks for great job with reverese engineering.
Now I have a HW 10070 of PCB and there is a space on it for RJ45 for LAN and I wonder if it is possible to just add this connector and enable this option in firmware???

[paul]

Hi,

Unfortunately I had the same problem as djeans, my scope locked up at the weekend. Totally unresponsive, powers up ok but just freezes after the hantek logo with the normal scope display, both traces on, run button lit up etc.
I tried the reset tool over USB but that did not work.
I am in the process of making a lead up for the uart, but which files do I delete and can they be backed up first ?
From a earlier post 
remove the /param/sav/run* and /param/sav/run*

arent these two the same ? Or am I missing something.

Paul.

[tinhead]

Unfortunately I had the same problem as djeans, my scope locked up at the weekend.

it seems to be issue with the latest models (what is your version in system info->hw? 555583e8 or 83e9 ?)

I tried the reset tool over USB but that did not work.

yeah, it works as long scope is responding to anything.
If (due broken setting file - the one in /param/sav ...) the dso.exe is unable to startup properly the USB reset tools is not working.

From a earlier post 
remove the /param/sav/run* and /param/sav/run*
arent these two the same ? Or am I missing something.

that was typo, it should be
- remove the /param/sav/run* and /param/sav/udisk/run*

[pgup62]

   

it seems to be issue with the latest models (what is your version in system info->hw? 555583e8 or 83e9 ?)

No, this behaviour can also be found on oldest versions (0x10050 555583e8) !

[tinhead]

   

it seems to be issue with the latest models (what is your version in system info->hw? 555583e8 or 83e9 ?)

No, this behaviour can also be found on oldest versions (0x10050 555583e8) !

sure, even the hw0 will sometimes write worng values into setting file, especialy when you power off
DSO while it was wrinting this file.

But now it seems to be just too much, i know already 6 ppl having exact same issue and  all 6 have latest hw version
with 83e9 design - within few days twice to number of issues from last 2 yrs ...

What additional unfortunate is the fact that the "default setup" button is not doing anything, before a
DSO with broken setup was always booting and it was enough to push once default setup button .. now ppl
have to disasemble scopes and delete manualy the file ...

[pgup62]

Well a bit tricky: hw or sw or both ?
last 25 devices (0x10070 555583e9) show normal behaviour after booting-up and 72 hours continuous operation. we have 2 old versions (10050 555583e8) that have this after boot-up freeze behaviour, one just after HMI appears (menus and waveforms), another within 20seconds-1hour after boot.
It seems that this can be a hw attitude (power voltage fall for instance from FPGA  or CPU sides).

[paul]

I have had the scope for a few months, and it has locked up a few times but always reset itself when I switched it off and on again. It was quite bad with the original firmware 110531.1 but after I upgraded to 110909 it was very stable.
However I upgraded it to 111226 two weeks ago and it started locking up again ! this time I had just changed the memory depth and did not notice that had locked up until after 30 seconds or more, and it does not matter how many times its switched off and on it remains totally locked up.

The hardware version is 83e8

BTW I didnt notice that the header is a 2mm pitch until I tried to plug in my 0.1” lead, and am I right in assuming that the uart is 3.3V ?

Thanks for all of your help
Paul.

[tinhead]

However I upgraded it to 111226 two weeks ago and it started locking up again !

you can update to 2.06.3(120112.1)
you will find it here :

http://hotfile.com/dl/142100356/1d87527/2.06.3_120112.1.zip.html
(MD5 371c00942b43b88df49eb23ca4ede99d)

BTW I didnt notice that the header is a 2mm pitch until I tried to plug in my 0.1” lead, and am I right in assuming that the uart is 3.3V ?

right, it is 2mm pitch and 3.3V level UART

[paul]

Thank you tinhead, I now have a working scope again. (DSO5102B  hw 83e8)
Without your help I would be sending it back to china and hoping for a warranty repair, which would probably cost a lot in delivery and take a few weeks for it to be returned.

I only deleted the /param/sav/run file (I only found one) and it booted up OK, if it didnt I was going to try the other files in /param/sav/udisk.

I still think this is a bug in the current firmware 111226, (its still the latest available on the Hantek website) as I didnt have any problems until I upgraded.

Can it be downgrade to a older firmware ? I am a bit reluctant to upgrade again   (although I have downloaded the link)

Thank you again
Paul.

[tinhead]

don't worry, the latest version here is working better as the latest version on Hantek website.

I remember i developed downgrade firmware ... here is it
https://www.eevblog.com/forum/index.php?topic=1571.msg63001#msg63001

It should work with 83e8 hw1007 (i would not recommend to install it on hw1007 83e9)
So you can try it, if you not happy you can still install the latest fw again.

[Kampfwurst]

it would be helpful if all the firmware Updates are for example on the first page.

[tinhead]

it would be helpful if all the firmware Updates are for example on the first page.

THEY ARE ON FIRST PAGE!

i'm trying always to maintain this thread, deleting old fw/tools, updating all the links on the first page ...
so all ppl have to do is check there ...

[sobomax]

Hi
I just receive my DSO5102B
First I change it into DSO5202B and everything works great. Thanks for great job with reverese engineering.
Now I have a HW 10070 of PCB and there is a space on it for RJ45 for LAN and I wonder if it is possible to just add this connector and enable this option in firmware???

There is an instruction on page 70 on how to connect LAN using $5 USB dongle.

-Maxim

[sobomax]

sobomax :

I think I have looked everywhere but I can't seem to find your network adapter supported list.

Also, any code updates ?

Hey Douglas, not much happening here really. I don't have any hardware list, but you can just take release notes for the 2.6.13 kernel and see what is supported there. This should give you a pretty good idea. Or you can just take your laptor with the i386 version of 2.6.13 running in the virtual machine to the shop and try to plug few and see which one works.

The kernel itself is now online here: https://github.com/sobomax/hantek_dso_kernel

Right now it's just stock qq2440 code, but in the next hour or so I will be checking in some small fixes required to build it with the recent 4.x gcc. The original code still assumes 3.4.

-Maxim

[McCurrent]

@patz:

Is it possible to add an option to your software which allows me to change back to the 1062b and not only one way to 1202b?

best regards
Johannes

Hi,

should be possible, I'll have a look at it ASAP.

Sorry, Patz,

I was impatient    .

I extended your sources to switch between all bandwidthes at will.

[McCurrent]

Hi tinhead, amazing thread!

Thx for sharing your work with us  .

Hi,

it works! Communication is done through the official USB driver.

I attached the first version as EXE file. Use at your own risk!



Some feedback if it is working would be nice. Tested with Hantek DSO5102B.

I just took patz' sources to turn my Tekway DST1062 into a DST1202.

But in fact I'm not quite sure whether I was really successfull, thus I have a couple of questions.

• After I changed the bandwidth, TTScope identifies the scope with the new bandwidth, and I may switch to 2ns timebase, but the scopes system information still reads dst1062b.
  Is this the suspected behaviour?
  
  
• Unfortunately I don't have a adequate source to check the actual bandwidth, thus I just "listened" to some USB communication to get an idea of it (poor thing, I know).
  The rise-time improvement was from 5,7ns to 4ns (3.7 at best, 61MHz -> 95Mhz)
  Now I'm considering my probes.
  
  Pinsonne offers three different accessories probes. One for each bandwidth, but they all seem to be identical.
  Of courxe I have only the 60MHz version.
  http://www.pinsonne-elektronik.de/pi10/pd111.html
  http://www.pinsonne-elektronik.de/pi10/pd108.html
  http://www.pinsonne-elektronik.de/pi10/pd107.html
  
  Do you have any experience, which bandwidth you could reach with the original probes?
  
  
• How did you test your improvements?
  Did you take the original probes or something different?
  
  

cheers
McCurrent