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

[benkev]

tinhead,
sorry for my silly question (2.), I was tired

[tinhead]

tinhead,
sorry for my silly question (2.), I was tired

you don't have to sorry, there is nothing silly.

[tinhead]

How to restore original firmware/NAND

imagine you screwed something up and wish to restore the firmware to the original version
(which you of course saved before wth the backup tools from this thread ... you don't? Well do it now.
If it's already too late then send me PM, i can help you to restore your DSO)

There are two ways :
- over JTAG
- over UART/USB

As most ppl don't have a nice H-JTAG USB (or whatever ARM JTAG) i will skip here the restore over JTAG part,
because if you have one you know how to use it
(all you need in principle is to flash in raw mode, so with OOB blocks the combined backup file fw_backup.bin and reboot)

Restore over UART/USB
You need some tools:
- dnw.exe
- supervivi.bin
- vivi.bin (just in case, see later why)

These tools are attached already here:
https://www.eevblog.com/forum/index.php?action=dlattach;topic=1571.0;attach=4153

The dnw.exe need a device driver and inf file, you can find them here:
(from http://www.friendlyarm.net/downloads page)
http://www.friendlyarm.net/dl.php?file=usb-downloaddr-setup_20090421.zip
http://www.friendlyarm.net/dl.php?file=usb-downloaddr_20090421.zip

The first one is complette setup program, the second just inf/device drive, use the one you like, both works
For Win64 users: i know there are some dnw.exe/drivers out there for Win64, search for them or use Win32 to restore

Now the first step is to create a complette restore file, the backup tool from this thread is creating 3 dumps:
boot.bin
kernel.bin
root.bin

They are only MTD partitions backups (with NAND OOB blocks), what missing is some empty space
which has been not saved during backup and NAND MTD endblock.
You can find them here:

(https://www.eevblog.com/forum/index.php?topic=1571.msg26930#msg26930)

https://www.eevblog.com/forum/index.php?action=dlattach;topic=1571.0;attach=4903
https://www.eevblog.com/forum/index.php?action=dlattach;topic=1571.0;attach=4904

Download these two files, put them into a folder with boot.bin, root.bin and kernel.bin
and run from dos prompt following:
copy /B boot.bin + blank.bin + kernel.bin + root.bin + mizi_tag.bin fw_backup.bin

The resulting fw_backup.bin is the full backup wich we need to proceed with restore.

Now connect your DSO over UART to your PC, open the terminal application, connect to whatever com port your
DSO is connected to (set 115200, 8n1) and power up your DSO.

While powering up try multiple times to hit space key, if the boot process have not stopped at following screen power off DSO
and try again until you see something like that :



This is the bootload prompt. Unfortunately the original Tekway/Hantek bootloader have NO USB support
so we have first to upload another one bootloader (with USB support) - that's the supervivi.bin

IMPORTANT: use only the supervivi.bin provided by me, if you use different version the restore might not work properly
or you screw up the MTD patritions.

To do this type in the bootloader prompt following:

load flash vivi x

and click enter. Now in your terminal application (i'm using hyperterm, sure not the best solution but it works)
chose "Transfer->send file", select the supervivi.bin, select Xmodem as protocol
(the x in what you typed in bootloader prompt means Xprotocol too).

Now you should see somehing like this picture:



After this step reboot your DSO, hit again during boot multiple times space key until the DSO stop at such screen:





The next step is to connect the DSO over USB and to install the device drivers to allow dnw.exe to communicate
with DSO. After you installed drivers run the dnw.exe, if everything worked you should see
in the dnw.exe top status line something like USB:OK



If you see this you can continue with fw/NAND restore, if not close dnw.exe, reconnect USB cable and try again.

Now type in the supervivi bootloader menu "r" - this means restore, immediately after that in dnw.exe menu
chose "Usb Port->Transmit/Restore" and chose the previously created full backup fw_backup.bin
Don't wait too long, dnw.exe is sometimes really bitchy with timeouts.

You should see now in the dnw.exe and your terminal application the transfer/flashing progress:






After the supervivi bootloader flashed the NAND with your fw_backup.bin the menu will be shown again, just
scroll back to see the flashing status, here my example (note, my NAND have one bad block, not a bog deal):



That's all, now close dnw.exe, disconnect USB cable from DSO and reboot DSO - you will have
now your original firmware restored.


Note: if you have too many bad NAND sectors the restore might not work, then you will have to buy new empty NAND chip,
solder it and repalce the broken one and of course use ARM JTAG to program the NAND backup (or at least the bootloader).

Extra note: after restore the bootloader is again the original HanTekway vivi.bin (the same as the attached),
if you lazy you can remove it of course by the supervivi.bin - the DSO will still work and you will have
nice way (over USB/dnw.exe) to backup/restore NAND (if you hacking often and have no JTAG cable this is the fastest way)

[drieg]

Awesome, thanks a lot!!!

[tinhead]

you welcome Drieg.


Btw, when you look eactly both bootloader (vivi and supervivi) have "boot system" options,
but don't use them during the firmware/NAND restore - it is better to physicaly power off and on to let the
bootloader initialize properly.

[tinhead]

Firmware bugs

As you know there was a "long" list of bugs send to HanTekway. The good news is - they responded very nicely to that,
provided a combined list (bugs and improvements proposal from all users) with schedule.
They currently working on that list and something will be available soon public,  on the Tekway website there
are already some dead links:



and Hantek did send few days ago testing version to some ppl. I got it too and tested already a bit,
that's the things already fixed in the test version:

- frequency counter decimal point bug (the counter was skipping one position while switching from e.g. 99.1 to 100.1 MHz)
is now fixed, the counter shows proper values.

- dots/vectors icon bug - now it is changing as supposed to do when you switch between modes

- default setting button "color reset" bug fixed - now you color setting will remain when you push "default setup" button

- horizontal scroll bug in long memory and 8ns/4ns/2ns/DIV - the waveform was disapearing when position has been moved,
now it works perfect.

- in vector/dots mode the zoom was showing only crap (in single window mode, dual window was working good)  above a
 specific zoom level - now it is stopping at max possible value and showing a short "max zoom reached" message.


There are also some bugs on which HanTekway was working at the time as they send out the test firmware (so partialy
fixed or with massive amount of debug information):

- digital filters - at current stage they accepting settings, but waveform is not yet looking perfect
- while enabling FFT in dual window mode the sample rate in status line is sometimes displayed wrong
  (turn the hor. knob one step right/left and  it is ok) - this is partialy fixed in the test version.
- FFT full span higher than Nyquist in 800ns to 2ns/DIV - you remember, i have patched that already but it seems that
  some DSOs (hw1005 only!) have issues with my way ... so HanTekway is working on a different solution for that.
  In the test version i can see already preparation for that, so good sign.

All the proposals/improvements are not yer implemented (which make sense as a stable bug free firmware is more important)
- add avarage sampling in long memory mode
- improve equ sampling (less ADCs to remove jitter)
- add extra 20kpoints or 16kpoint or 8kpoint in memory modes (depends on what possible)
- release SDK


Normally i would post the test version here, but this time there is lot of debug code inside slowing down
the DSO (display update, knobs respond, skipping waveforms in higher timebases), so i decided to not do that
but report to you back guys what the status is.

When i look on the combined issue list (schedule and where they are now) it seems that HanTekway will resolve all these
points still before christmas (i just can't wait for the SDK ... crossing fingers and counting seconds )


EDIT: oh well, for those who didn't got that test version but wish to play with it

(MD5 13829cd9b0d91a241865a9de1d73e771):

http://hotfile.com/dl/135986668/411b586/dst1kb_2.06.3_(111124.0).up.html

Note - as said above, the amount of debug code is slowing down a bit the operations, but on the other side there
are already imporvements so it is your decision ...

... and if you wish the same test firmware with patched out most of the debug code (it is still bit sluggish but better than org. version)
and patched out the FFT full span bug (on hw1005 it might/might not work) feel free to test my version:

(MD5 7abfc8d87f20854b8c372e2bd4bf3bac)

http://hotfile.com/dl/136350073/07ca4ca/dst1kb_2.06.3_(111124.0).up.html

NOTE: both HanTekway and my version are universal, you can install them on any Hantek DSO5xxxB or Tekway DST1xxxB DSO

Files deleted - new version available

[Crenwick]

Hip Hip Hantek (and Tinhead  )

That's GREAT news 

[carloscuev]

Could I test it on my Tekway DST1102b ( converted to 200Mhz of course ) ?

[tinhead]

Could I test it on my Tekway DST1102b ( converted to 200Mhz of course ) ?

yes you can, as i said above it works on any Hantek DSO5xxxB or Tekway DST1xxxB DSO

[rf-loop]

Nice work, really nice.

Tinhead DSO5000B, Hantek DSO5..... , Tekway..

TinHanTek DSO5000B

[walt]

which is the reason why the update fail,

step 8, error 0xfb. Failed to decompress upgrade file.   
Checking on 2 different USB storage.

In console

have * in update packet
Search_UdiskUpdateXXXFiles
dst1kb_2.06.3_(111124.0).up  hantek36_1
(006)mem valid cnt=545..time 10s wave frames = 0...
tmp_name : /usr/up/dst1000_4000.up.tmp
gpg: CAST5 encrypted data
pw:0571tekway
gpg: encrypted with 1 passphrase
(007)mem valid cnt=545..time 10s wave frames = 0...
gpg: WARNING: message was not integrity protected
gpg: CAST5 encrypted data
pw:0571tekway
gpg: encrypted with 1 passphrase
(008)mem valid cnt=545..time 10s wave frames = 0...
gpg: WARNING: message was not integrity protected
dst1kb_2.06.3_.up.tar
(009)mem valid cnt=545..time 10s wave frames = 0...
tar: Short header
tekwayup_client
tekwayup_client/update
tekwayup_client/dso.exe
(010)mem valid cnt=545..time 10s wave frames = 0...
(011)mem valid cnt=545..time 10s wave frames = 0...
tar: Write Error: No space left on device
tar: Invalid tar header checksum
Tar_UpdatePacket ok !!
start update sys files
iError :251
Show_UpdateEndWindow end
saved run param ...Save: 0
SaveTypeToFile:write ok 0
ok

WTF? 

[tinhead]

walt,

you should see something like :

tekwayup_client/update
tekwayup_client/dso.exe
tekwayup_client/special
tekwayup_client/update~
tekwayup_client/OurLanguages
tekwayup_client/OurLanguages/English.lan
tekwayup_client/OurLanguages/French.lan
tekwayup_client/OurLanguages/German.lan
tekwayup_client/OurLanguages/Japan.lan
tekwayup_client/OurLanguages/Korean.lan
tekwayup_client/OurLanguages/Tridchn.lan
tekwayup_client/update.sh~
tekwayup_client/sys.inf
tekwayup_client/sys.inf~
upend

but on your scope it ends up right after dso.exe :

tekwayup_client/update
tekwayup_client/dso.exe
tar: Write Error: No space left on device

This can have two reasons :

1-  there is really no space on NAND (which i doubt, but who knows, maybe too many broken sectors)
Check that, do df -h on the shell

2- the firmware update file you downloaded is corrupt - check the MD5 checksum
A corrupt file can't be unpacked and it's causing memory overflow error, which might result as "no space"

[tinhead]

1000st reply ... nice .. and actually funny situation. I was about to make screenshot with
the !1000st reply! from my Tekway :



and i did found a nice thing.

Is it bug? Or feature ? You decide ... switch to XY mode, apply waves (for best result just the same sine wave to both channels)
and change contrast, with contrast set to 0 the XY screen is updating much faster than with contrast set to 15

EDIT: It seems that contrast=0 is always allowing fastest screen update, depends on version the slowest
might be between 8 and 11, then again increasing update speed when changing into max direction.

[walt]

1-  there is really no space on NAND (which i doubt, but who knows, maybe too many broken sectors)
Check that, do df -h on the shell

I manualy unarchive update file, copy to folder usr/up/  from mnt/  . Space is realy enough.
After I run update script, and all OK

2- the firmware update file you downloaded is corrupt - check the MD5 checksum
A corrupt file can't be unpacked and it's causing memory overflow error, which might result as "no space"

I unarchive file on USB storage manualy on PC, end after look #1

[walt]

RAMDISK driver initialized: 16 RAM disks of 4096K size 1024 blocksize
loop: loaded (max 8 devices)
nbd: registered device at major 43
Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
ide: Assuming 50MHz system bus speed for PIO modes; override with idebus=xx
S3C24XX NAND Driver, (c) 2004 Simtec Electronics
s3c2440-nand: mapped registers at c4880000
s3c2440-nand: timing: Tacls 9ns, Twrph0 39ns, Twrph1 9ns
NAND device: Manufacturer ID: 0xec, Chip ID: 0x76 (Samsung NAND 64MiB 3,3V 8-bit)
NAND_ECC_NONE selected by board driver. This is not recommended !!
Scanning device for bad blocks
Bad eraseblock 1797 at 0x01c14000
Creating 3 MTD partitions on "NAND 64MiB 3,3V 8-bit":
0x00000000-0x00030000 : "bootloader"
0x00050000-0x00250000 : "kernel"
0x00250000-0x03ffc000 : "root"
s3c2410-ohci s3c2410-ohci: S3C24XX OHCI
s3c2410-ohci s3c2410-ohci: new USB bus registered, assigned bus number 1
s3c2410-ohci s3c2410-ohci: irq 42, io mem 0x49000000

and empty storage attached

usb 1-1: new full speed USB device using s3c2410-ohci and address 2
scsi0 : SCSI emulation for USB Mass Storage devices
get udisk first!!
hantek1_1   hantek26_1  hantek29_1  hantek3_3   hantek4_16
hantek1_2   hantek28_1  hantek2_1   hantek3_4   hantek4_17
hantek1_3   hantek28_2  hantek30_1  hantek3_5   hantek4_26
hantek1_4   hantek28_3  hantek32_1  hantek3_6
  Vendor: APACER    Model: AH323             Rev: RMAP
  Type:   Direct-Access                      ANSI SCSI revision: 00
SCSI device sda: 7820800 512-byte hdwr sectors (4004 MB)
sda: Write Protect is off
sda: assuming drive cache: write through
SCSI device sda: 7820800 512-byte hdwr sectors (4004 MB)
sda: Write Protect is off
sda: assuming drive cache: write through
 /dev/scsi/host0/bus0/target0/lun0: p4
Attached scsi removable disk sda at scsi0, channel 0, id 0, lun 0


Please press Enter to activate this console.
[root@Tekway-dso /]# df -h
Filesystem                Size      Used Available Use% Mounted on
/dev/root                61.7M     48.0M     13.6M  78% /
none                     30.4M         0     30.4M   0% /tmp
none                     30.4M         0     30.4M   0% /var
/dev/scsi/host0/bus0/target0/lun0/part4      3.7G      0      3.7G   0% /mnt


Whats the hantek1_1... file and where its? USB Storage is empty.


 

[ot1]

I have a Hantek 5102 with hw1005, sw 110229.  I have made no modifications to it.

I just started using it and have a few questions.

1. The SINGLE SEQ button is translucent just like the RUN button, is it suppose to light up as well?

2. Setting the Verticle resolution knobs (either channel)  without probes connected, I see 200 mv of ripple at 50v,  rotating the knobs to 50mv, I would expect the noise peaks to increase in size, like on my analog scope, however the ripple drops to 1.8 mv, this seems strange to me, is this normal for this type of scope?

3. I was going into various menus and the screen froze, it would not respond to any other button presses, stuck on displaying channel 1 setup.  I powered down and back up attempting to duplicate the problem, pushing various buttons, but not rapidly.  Pressing Channel 2 caused it to freeze again, I rebooted again to unfreeze it.  So now I determined that pushing Channel 1 then Channel 2 and back to Channel 1 then Channel 2 with about 5 seconds in between presses would freeze the screen. The 4th time I rebooted, I pressed Default Setup before it froze, since then I have not been able to duplicate the freeze problem.  Unfortunately, I didnt think of recording any of the settings prior to pressing Default Setup.    Has anyone else experienced this problem?



 
 

[tinhead]

I have a Hantek 5102 with hw1005, sw 110229.  I have made no modifications to it.

I just started using it and have a few questions.

1. The SINGLE SEQ button is translucent just like the RUN button, is it suppose to light up as well?

no idea why Hantek decided to made this button translucent, on Tekway is not.
So the answer, as far i know today, it suppose NOT to light up.

This might change, not all shift register (driving LEDs) are in use, same for keyboard. I'm currently soldering
external keyboard to evaluate all open functions ... if any there i will let you/all know.
The reason why i'm doing this is because i recognized that for example the handheld software is
uding doferent keyboard combinations for some buttons, so maybe they exists also on bench model
and can be used for whatsoever (e.g. enable/disable VGA-out on which i'm working these days)

2. Setting the Verticle resolution knobs (either channel)  without probes connected, I see 200 mv of ripple at 50v,  rotating the knobs to 50mv, I would expect the noise peaks to increase in size, like on my analog scope, however the ripple drops to 1.8 mv, this seems strange to me, is this normal for this type of scope?

yes, this is DSO, the level of noise you see is not analog frontend noise but a mix of analog and digital noise.
The digital part is always 1-2 LSB so you see 1-2 "lines" of noise. On 2mV/DIV the analog noise is of couse higher then the digital.

3. I was going into various menus and the screen froze, it would not respond to any other button presses, stuck on displaying channel 1 setup.  I powered down and back up attempting to duplicate the problem, pushing various buttons, but not rapidly.  Pressing Channel 2 caused it to freeze again, I rebooted again to unfreeze it.  So now I determined that pushing Channel 1 then Channel 2 and back to Channel 1 then Channel 2 with about 5 seconds in between presses would freeze the screen. The 4th time I rebooted, I pressed Default Setup before it froze, since then I have not been able to duplicate the freeze problem.  Unfortunately, I didnt think of recording any of the settings prior to pressing Default Setup.    Has anyone else experienced this problem?

this might happen. The reason for that is that all the default settings are updated from one to another firmware revision.
In principle when installing new firmware all settigns shoudl get deleted, however i saw from time to time that
this not happed on my scopes. The defualt button exists luckily, it helps almost always when the scope
manage to write bullshit into the settings.
Imagine you poveroff while DSO is writing these values - the golden rule - wait 10 seconds until last change in menu/setup
before you power off - this is because the DSO is writing cycling (10 sec after) after each change the settings into NAND.
Why they decided to use NAND no idea, EEPROM would be more secure from read/write max life cycle.

[RB1]

Hello everyone this is my first post on the forum. Thank you tinhead and everyone else in this thread for all the great information.

I bought a Hantek DSO5102B from HK a few days ago;
model; DSO5102B
sw version; 2.06.03 (111122.0)
hw version; 10070x555583e8
serial; T1G/012 xxxxxx

I'm not sure if I have a newer formware (111122) than anyone else has?

I have not tried to change the firmware.

There still seems to be a couple of bugs when changing horizontal timebase in some modes.

My noise figures seem typical, compared to other people's screenshots.

My unit has a fan built in, it is very queit and not a lot of airflow, which is probably a good setup.

Minor display bug;
press; Acquire->Equ-time
then MemDepth is greyed out like it is disabled, but still allows memdepth selection.

Function bug;
press; Utility->page3->Filter
the filter does NOTHING at all! No change in waveform or amplitude for any filter type setting or any filter Hz setting. This is disappointing, it almost looks like they disabled the filter completely but left the filter menu working!

The filter can be turned on, and then some other options stop working, like it is not possible with filter on to set Memdepth in Acquire!

It is disappointing that the filter does not work, it would have been very nice to be able to add some low-pass filtering to reduce HF noise on the waveform.

TTScope problem;
I use Win98, and have not been able to successfully set up the drivers for TTScope.exe. I put the drivers in c;\windows\system32 but no good. Also windows cannot auto detect the drivers it keeps looking for a driver file but not able to find it, even when I tell the exact location of the file.

[tinhead]

I'm not sure if I have a newer formware (111122) than anyone else has?

yes, i have 111124.0  and 111202.0. If you don't mind make a backup of the 111122.0 and send me PM
with download link (I'm collecting versions to track changes)

I think i will post 111202.0 today or tommorow.

There still seems to be a couple of bugs when changing horizontal timebase in some modes.

this might be due the firmware version, Hantek/Tekway are working on firmware issues, "unfortunately"
they released few debug firmware versions into production - the 111124.0 is such example.
The 111202.0 not - it is production version where you can clearly see the speed difference.

Minor display bug;
press; Acquire->Equ-time
then MemDepth is greyed out like it is disabled, but still allows memdepth selection.

this is not a bug, these scopes have in Equ time mode only 4k samples, see user manual

Function bug;
press; Utility->page3->Filter
the filter does NOTHING at all! No change in waveform or amplitude for any filter type setting or any filter Hz setting. This is disappointing, it almost looks like they disabled the filter completely but left the filter menu working!

The filter can be turned on, and then some other options stop working, like it is not possible with filter on to set Memdepth in Acquire!

It is disappointing that the filter does not work, it would have been very nice to be able to add some low-pass filtering to reduce HF noise on the waveform.

if you would follow this thread you will see what i wrote about digital filter - the implementation was bad
and HanTekway agreed to re-write it. On the 111202.0 the filter is also disabled as they working on the code,
there is no reason to have it enabled when the code is anyway not working properly.

TTScope problem;
I use Win98, and have not been able to successfully set up the drivers for TTScope.exe. I put the drivers in c;\windows\system32 but no good. Also windows cannot auto detect the drivers it keeps looking for a driver file but not able to find it, even when I tell the exact location of the file.

ehm yeah, Windows 98 ... do you think it is smart to use nearly 14yrs old OS and ask for drivers? For sure i know that in
some environment there is a need to run older Windows version (to have a chance to use other older equipment ),
i worked for years like that with XP now with Vista 32bit (where even my last supported on Win98 hardware is working).

You can try the oldest version of TTScope (only the drivers!), you can find it here http://www.tekwayins.com/pic/TTScope2.0.0.4CH.exe

[clonecrp]

Keep up the great work !

Do you have an English version of TTScope for download too.. ?
Please advise...

Seasons Greetings & Thanks!
Doug

[tinhead]

Doug,

you can use Tekway or Hantek version of TTScope, however currently on Tekway website you will
find only older versions.

Botn English and Chinese versions are actually bi-lingual - so you can install directly as English
or switch later to English.

However, don't expect too much from that software. For remote control - it works slow but it works,
protocol analysis works too, XY more or less (still thinking what this mode can be useful for),
some other features are just piece of crap.

Not because they useless, no, only because someone forgot to change the display resolution.
When you look on www.tekwayins.com you will find some older Tekway models, with 320x240 display and 4:3 ratio.
The TTScope was designed for these scopes - and was working good.
As Tekway released the new scopes with 7" display they actually planed tp change the software
but after the deal with Hantek this never happened. So part of the software is working with the new hardware
but part not (due wrong ratio, memory deepness).

Actually the USB/LAN protocol is simple, when i find some time i will wrote new software (or driver to allow work with LabView).
Hantek promised to release SDK until begin of December - but they still not ready due high work load (they releasing right
now tons of new models - https://www.eevblog.com/forum/index.php?topic=5778.0 )
This is of course not an excuse but only the truth. The status has been also changed to "Jan 2012"
and if this not happens i will fly to China and buy Hantek ^^

[clonecrp]

I'm from the US and didn't make the HK Fare this year ... maybe 2012 Asian Sources (my friend wants to go again) ... much money from here in North West Pennsylvania...

I only had a brief look @ the new models in your link ... Hope my Hantek (near 6 Months old) will not get away. The fan and PS Mods were much fun.

Notes ... shure would like a copy of the network PCB ... & oh ! I may have a spare TI 3.3 vdc power supply device here somewhere..


 

[tinhead]

Hope my Hantek (near 6 Months old) will not get away.

don't worry, they will definitely continue to produce 2 channel models.

It might happen that at some day the B models will get replaced complettly by BM/BMV ( because of the 2Mpoint memeory)
and they will start with BMX (with more sample memory), but these BM/BMV models are in principle still nothing
else than the B models - but just with some gadgets and more sample memory.

[tinhead]

here we go, the latest firmware version - 2.06.3 (111202.0) for Tekway DST1xxxB and Hantek DSO5xxxB models :

http://hotfile.com/dl/137787683/6dc4d32/firmware_111202.0.zip.html
(MD5 1b863a38da71b26c3071822985076952 )

Inside you will find 3 folders, each of them contains different update, chose the one you wish to use :

universal_org -
   this is the original firmware with no modifications

universal_125_short -
   this is patched version to fix the FFT Full span bug. It allows following
   sample rates in short memory mode (4ksamples) :

   800ns/DIV - 250MSs instead of 200MSs
   400ns/DIV - 500MSs instead of 400MSs
   200ns/DIV - 1GSs instead of 800MSs
   80ns/DIV - 1GSs instead of 800MSs
   40ns/DIV - 1GSs instead of 800MSs
   20ns/DIV - 1GSs instead of 800MSs

   All other modes are unchanged.


universal_125_long_and_short
   this is patched version which additionally to the changes above allows
   higher sampling rate in long memory mode (40ksamples, 512ksamples, 1Msamples)
   The maximum resulting sampling rate (depends on timebase and memory depth) is :

   500MSs in single channel mode instead of 400MSs
   250MSs in dual channel mode instead of 200MSs - each channel

Note : i give absolutely no warranty that these changes will work on your DSO,
all these changes are unofficial but tested on Tekway hw0 and Hantek hw1007 models i have.

If you don't like these changes or have issues on your DSO please me a PM.
You can of course always install the "universal_org" over the patched versions.

[RB1]

Thank you very much Tinhead for responding to my post.

...yes, i have 111124.0  and 111202.0. If you don't mind make a backup of the 111122.0 and send me PM
with download link (I'm collecting versions to track changes)...

Sorry I don't know how to do that. Is there an easy way to do it without opening the case or needing to solder to the PCB and get a USB/uart?

Minor display bug;
press; Acquire->Equ-time
then MemDepth is greyed out like it is disabled, but still allows memdepth selection.

this is not a bug, these scopes have in Equ time mode only 4k samples, see user manual

Actually the MemDepth can be changed ok in Equ time mode. It seems to have the normal selection 4k 40k 512k 1M. They can be selected ok when in Equ mode, and appear to work. But they are "greyed-out" in appearance so they appear to be disabled (but still work).

Thanks Tinhead for the information on the filter.

Also thank you for the link to the older TTscope.exe, I will try the drivers for that. My workshop PC runs Win98 and needs the older support for parallel ports etc that only Win98 can provide. I also have some high speed Dos software which needs Win98.