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

[campodea]

I'm pretty sure they are cumulative...

[morris6]

A tip for those of you that do the LA board addition to prevent this disaster:

OK guys,

Let this be a warning to all of you upgraders. Be very carefull when fitting the MSO add-on card to the mainboard.

My glasses are not strong enough, it was off by one row when I did a first test after loading the new software.

A flash, some smoke and the S3C2440 SOC is looking very dead now with its newly formed bubble. 

Maurits

When you didn't yet solder the strip of contacts in the mainboard consider this:

The strip I received with the LA-board was 34 pairs of pins instead of the needed 30 pairs. I cut of 4 pairs. However, you can make a kind of fitting slot or shroud by cutting of just two pairs. Now push or pull the pairs of pins at both ends upwards, flush with the bottom of the strip and then bend the tops inwards, like a square hook. This way you cannot push the LA board on the pins in the wrong, one row off, position. I think there is room on the main board for the extra pin pair at either end.

Good luck, Maurits

[tinhead]

Backup tool for the new MSO models :

 - Tekway MST1062B, MST1102B, MST1202B
 - Hantek MSO5062D, MSO5102D, MSO5202D
 - Voltcraft MSO5062B, MSO5102B

simply download, unpack and read how to use ... it contains also some informations and tools to allow restore of the backup

[ElektroQuark]

DSO1062D received.
 
2.06.3 (121023.0)
10070x555583eb
DAC LTC2601

[tinhead]

Thanks!

[ElektroQuark]

I must read a ton of pages now to properly update to 200MHz.
Thank you, Tinhead.
If you need a pic, ask, it's open right now in the bench at home waiting for me.

[LEECH666]

I found the DSO-BW-Changer Tool that you can find here fairly easy to change the bandwidth to 200 Mhz.

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

Basically all you need is a USB (A to B) Cable that you hook up to the PC / Scope and then you click the setting you want.
Not sure if I needed the USB driver from the Hantek page installed, but IIRC I did install it.

http://www.hantek.com/Product/64Driver/DSO5000.rar

[ElektroQuark]

Thank you LEECH666.

I have read many of the pages and I think am ready to change it. I will use the USART connection, rename and edit files to change it to HANTEK DSO5202B. First a backup will be done.

I have downloaded also the files with the correct icons, I have yet to find in with folder they must be stored. I'm reading...

[ElektroQuark]

W
 
 
What is the correct commad:
 
mv dso1062d dso5202b
or
mv dso1062d DSP5202B

[ElektroQuark]

I can not see any files in /
ls clears screen on terminal and nothing appears.

[tinhead]

W
 
 
What is the correct commad:
 
mv dso1062d dso5202b
or
mv dso1062d DSP5202B

none of them!

internally, and this is what makes the difference, the 60MHz benchtop model name is dst1062b, and the 200MHz model name is dst1202b. So the proper command, for benchtop models, is

mv /dst1062b /dst1202b

[tinhead]

I can not see any files in /
ls clears screen on terminal and nothing appears.

and this question was answered as well

1 - you connected vice versa (txd and rxd) -> when it is wrong you will not see any messages while booting,
simply power cycle dso and watch the terminal output.

or

2 - you connected properly, but your DSO already booted, then simply push space and ctrl+c keys

[ElektroQuark]

This is a Voltcraft DSO-1062D and I want a DSO5202B as target.
 
I'm logged as root, I can go to /bin or /logo but can not list any file.
I killed dsod too.
 
If type ls screen blanks and promt dissapears. When press ENTER, promt appears again.

[tinhead]

This is a Voltcraft DSO-1062D and I want a DSO5202B as target.

and still does not matter, Voltcraft DSO-1062D is nothing else than Hantek DSO-5062B which is Tekway DST1062B <- therefore the DSO name you need to change from is /dst1062b. You wish to change to Hantek DSO5303B, which is nothing else than Tekway DST1202B  <- therefore you have to change to /dst1202b.

I'm logged as root, I can go to /bin or /logo but can not list any file.
If type ls screen blanks and promt dissapears. When press ENTER, promt appears again.

i have no idea what you doing, when you in, and you killed dsod and dso.exe you should see dirs and files ...
but hey, maybe you shoudl ensure you killed really all

killall dso.exe
killall dsod

when there is no process to kill, linux wil tell you this. Simply type it few times (and push enter key hehe), ok?

[ElektroQuark]

I start the oscilloscope.

I see all the boot log through terminal aplication.

When the DSO has started: space control c ENTER.
root promt appears. Oscilloscope screen freezes.

killall dsod ENTER (if not the timer reboots the oscilloscope).

If I type ls ENTER the terminal screen clears completely and nothing appears.

If I hit ENTER again the root promt appears again.

I can go into bin directory if I type cd /bin ENTER.

I can go to logo directory if I type /logo ENTER.

But I can not list any file or directory if I do ls ENTER

vi /sys.inf ENTER clears terminal screen completely too, another ENTER shows promt again.

mv /dst1062b /dst1202b seems to work, I do not received any error about files not found.

I will try including killall dso.exe

Thank you again Tinhead.

[paul]

I have been testing the new firmware and checking if the delayed sweep bug has been fixed, I started to record the result (attached below) against the 1KHz  probe calibrator with the trigger point offset to 500uS  and then 1.000mS to see if any errors were cumulative. Which they are not, the error is the same at 1.000mS as it is at 500uS.

At first it looked as if the bug was fixed at 4K memory depth (with some small issues) a bit strange at 40K useless with 512K but still perfect at 1M

However with the offset / delayed sweep set to 1.002mS with 1M memory it all goes horribly wrong. See screen grab attached.

As this is a 1KHz square wave the rising edge should be just to left (a couple of pixels) of the middle of  the screen with a offset of 1.002ms. Not 184uS (2.3 squares, best estimate) as shown in the screen grab.
BTW it is spot on with 1.000mS, it just jumps over if you set more than 1.001mS.


Delayed Sweep Bug (Bug number 15 on Tinhead`s list) with firmware 1301114

 
Time Base   Error at memory depth.   
               4K         40K        512K          1M
200us     ok           ok           ok            ok
80           ok         -12us        ok           ok
40           ok         -6us        +94us       ok
20           ok         -3.2us     +297us*   ok
8             ok         +18us     +418us*   ok
4             ok         +10us     +459us     ok
2             ok         +29us*   +479us*   ok
800ns     1.8us    +41us*    +419us*  ok
400ns     900ns   +495us                    ok
200ns     440ns   +495us                    ok
80ns         *                                         ok

 * off the screen, trigger point adjusted (in stop) to find error time.
Delayed sweep set to 1.000mS,  using built in 1KHz calibrator.

(Sorry the table looks horrible, I have now attached it as a doc file)

Delayed sweep works, sort of, but use with caution.

Paul.

[tinhead]

i've got new firmware - for testing - for 1Mpoint benchtop Tekway/Hantek/Voltcraft models, so if someone wish to test
it use this link:

http://www.mikrocontroller.net/attachment/168234/dst1kb_2.06.3_15202b_fact_130131.0_.zip

and let me know if you found something. I've checked with the bug list, and almost all bugs are fixed,
but few things are not yet as they should be.

Btw, check measure menu, all the "cryptic" named measurments got icons.

[tinhead]

I have been testing the new firmware and checking if the delayed sweep bug has been fixed, I started to record the result (attached below) against the 1KHz  probe calibrator with the trigger point offset to 500uS  and then 1.000mS to see if any errors were cumulative.

first of all thanks for the effort. If you don't mind, could you repeat your measurments with the firmware 130131.0 from link above?

[carloscuev]

for 1Mpoint benchtop Tekway/Hantek/Voltcraft models

Just to be sure, that's the classic "B" model? because I have that, and I remember being able to do 1Mpoint, but now I've checked and now I can't select 1Mpoint, currently running FW 2.06.3(130114.0) maybe It's disabled in this version.

[mightyzen]

Just to be sure, that's the classic "B" model? because I have that, and I remember being able to do 1Mpoint, but now I've checked and now I can't select 1Mpoint, currently running FW 2.06.3(130114.0) maybe It's disabled in this version.

The 1Mpoint option is only available when a single channel is active.

[carloscuev]

The 1Mpoint option is only available when a single channel is active.

Just re-checked and nope, in this version (130114.0) it's disabled, can anyone double check that?

[mightyzen]

Just re-checked and nope, in this version (130114.0) it's disabled, can anyone double check that?

I'm running tinheads latest (test) version 130131.0 and 1M is enabled when only single channel active.

[carloscuev]

I'm running tinheads latest (test) version 130131.0 and 1M is enabled when only single channel active.

Just updated firmware to latest 130131.0 and I still can't

[fresher]

Hi, first post her

I also have this Scope. I notice right now that the 1Mpoint option is only on 200us not available. When you turn to 400us or 80us than you can select 1Mpoint. Is this a bug??

[tinhead]

with in 200us/DIV the 1Mpoint was never available, same for 2Mpoint, it is disabled while in 400us/DIV.
Call this bug if you wish, but it is by design like that (this is not that we can't "patch" the firmware to remove these restrictions,
but note that the FPGA will not sample anything when such illegal selection has been chosed, see picture - no signal but freq
counter is counting - here square - 1khz signal).

Btw, i recall i thought they tried to implement it, but i was wrong:

First of all the 200us/div and 1M was not working from the beginning. Right after i recognized it on a very
first firmware i send it as bug report - i don't know when exactly but one on next firmwares was able
to enable 1M in 200us/div but zoom was not working. So i asked again and got answer
that the way how the DSO is designed they can't enable 200us/DIV and 1M - the next fw version then was
not capable again of doing 200us/div and 1M. I thought, what a bummer, but anyway,
it works below and above 200us/div, or just with 512k while in 200us/div.

I've checked right now again this old fw, and honestly zoom was another bug with no relation to memory depth.
There is possible to seelect 1M in 200us/DIV, but the firmware is still using 512k, so no i correct myself, 1M and 200us/DIV
it was never really possible.

In my eyes, it was design decision, exact like e.g. in dual window mode no option to remove menu. Is it not possible?
For sure it is, but they chosed to not allow it and we have to accept it.