New Hantek DSO2X1X models?

[michal_nt1]

Hi everyone !

Can you guys tell me if this  is normal for this scope to display waveforms like this in the ROLL mode ?(HORIZ MENU)
  I attached two screenshots  , one  1 kHz sine wave and the other one 50 Hz.   Maybe there are some settings I missed
so that I can watch it in more human readable manner?


My scope is DSO2D15
 In short, managed to update from original 20201221  to  version   20210416(with adventures...)
Running firmware 3000.

[imk]

michal_nt1
turn the timebase knob clockwise
imk

[michal_nt1]

Hi imk

it looks like I can move only counter clockwise  using the nob  described as SEC/DIV on the phisical panel,  turning clockwise
dosent seem to change anything in regard of solving the problem.

[imk]

michal_nt1

My scope is all boxed up, so i can't easily test what you're trying to do.
Have you tried the Auto Set button, it generally finds a fairly good waveform display starting point.

[michal_nt1]

Hi imk

of course I did,
I ran mutiple checks with diffrent settings before posting ,   what I recall( but im not 100 %  sure) that it displayed
right before the update .  Thats the reason why I asked  on the forum if its normal.   Anyways, thanks a lot imk for
super quick replies.

[imk]

michal_nt1
Ah did not realize you had it working before you did an update.
So are you saying is it worked as you expected it to do, then you have done an update and now the timebase control does not seem to work correctly?
If so on DaveidAlph's gdrive, see his post you will find his archive of all the work he has done on this scope.
There you should find some very useful information and various firmwear updates  and his recommendations.

[michal_nt1]

Hi Imk,
 The thing is that Im not really sure if  the device was working ok or not, I recall some things but I cant tell for sure...
I wish that the owners of this scope would make  a check  in  the ROLL mode in  frequencies lets say between 50 Hz and  2 kHz and share their results . Whats funny when I go above about 100 kHz  the waveform becomes "human readable" but it
looks like the trace expands or shrinks depending on the frequency..   I think that what I should see in the roll time  is a period passing  by from right to left with given time by the  sec/div  knob ...
Correct me if Im wrong .

[DavidAlfa]

Another really annoying issue I found today.
If you set adquisition in average mode (ex. to clean up the signal), when you save the picture it will save the last, non-filtered snapshot!
Damn you Hantek!
Edit: It turns out it was the avg is resetted inmediately after saving, but the picture is ok.
But if you push stop, then yes, it will be resetted!

michal, the wave issue is because you're breaking nyquist (sampled signal frequency/ adcs ample rate), and hantek does pretty much nothing to filter it.
You can see that with the wavegen...ex 1KHz, it will look ok at 200uS/div, but if you go back to 10...100mS range, it will show a completely different signal.

[michal_nt1]

DavidAlfa,  thanks for a comprihensive  answer   

[Gerasim]

Hello Michal! I have a big request for you. Can you back up your 2d15 for me? It’s very simple. Go to the DavidAlf folder with the name GDrive. There you will find the file "dso3kb bakup builder.upk". Copy it to your USB stick and run it on your device. After that, a new file will appear on your flash drive - your backup copy. I would really like you to send it to me, but rather leave a download link in this thread. At one time I did not create such a copy and now I am suffering. Thank you!

[DavidAlfa]

What issues are you having?

The serial, model, HW, FW version, wavegen calibration... All can be restored easily with the available mods.

[michal_nt1]

Hi Gerasim,
 The problem is that I dont have original files either... Briefly, my scope came with  version 20201221 and FW 3000, then I upgraded it to  dso3kb_20210416,
then downgraded to dso3kb_20210311 (for testing purposes) and the scope started to freeze. After couple of restarts it became nonresponsive.
 ( I could see the screen, like 2 relay cliks on start  and beeps when keys pressed and that was about it ... .) To  fix the scope I used  platform tools 20201221, 
it fixed it but some ID's were removed  like model and serial, so I used the script form DavidAlpha to change ID's. Luckly I had pictures of ID's taken before. Then I realized  that there was an issue with calibration , because platform tools uses diffrent FW  so to fix calibration  upgraded from utility menu using the firmware changer  dso3kb_FW3000 in DavidAlfa's folder,  that changes FW to original 3000. Now I hope everything is as it was before upgrades.  Who knows...   Everything you need with instructions is in DavidAlfa's google drive.

[DavidAlfa]

Check the FAQ in my signature to see what updates can be applied safely. As long as FW is not changed, everything will be ok
Platform-tools 20201221 also uses FW3000, so there shouldn't be any issues?

I also had a lot of freezing 2 weeks ago.
All seemed correct, fw , model were ok, but it freezed very easily. I'm pretty sure I had flashed platform-tools 20201221 and then upgraded to 20210416.
Since then I flashed it few times already.
Currently, everything is undefined, I only bothered to restore the wave gen calibration... and no freezing!

[Gerasim]

Thank you for your answers! But I know all this and at the moment I have a copy, which was provided to me by DavidAlfa. I also used the generator calibration file. In principle, everything suits me, except for small moments. The generator works quite well at voltages above 1v, but as the voltage drops, the shoulder skew increases greatly. So everyone? It is possible that Hantec calibrates the generator separately for each scope and therefore the calibration files of different devices may not match. So I wanted to try installing a backup from other devices, hoping that the result would be better.

[DavidAlfa]

That's because your calibration is wrong, make a new one!
The same happened to me:
https://www.eevblog.com/forum/testgear/new-hantek-dso2x1x-models/msg3585539/#msg3585539

[Gerasim]

We probably didn't understand each other). I meant the offset of the generator amplitude in min and max. I've calibrated many times and reset the scope to default. It does not help. Only by manually shifting the amplitude can you more or less achieve some result and set the signal to the center. But I wish I didn't have to do this. But that's okay! Will live!))

[DavidAlfa]

I've been debugging i2c signals. Must say that at least this decoder work great!
Here the overclock makes a brutal difference:

[imk]

I've been debugging i2c signals. Must say that at least this decoder work great!
Here the overclock makes a brutal difference:

Hello David,
I found the i2c decoder worked VERY well at times, but sometimes I have lockup issues and had to power cycle, then after restart the i2c decoder would not sync correctly so i had to power cycle it a second time to get it to work correctly , most odd.
So are instruction for the overclock on your gdrive and how much did you overclock by please.
ian

[DavidAlfa]

Everything is inside Mods / Overclocking folder.
By default it's set to 696MHz(CPU) / 192MHz (RAM). More than that crashed for me.
To change the multipliers, check the script "oc_manager", edit it before running the update package, as thefiles in the usb/overclock folder are copied to the system.
If you want to change the multipliers after installing, just edit the usb files and run the installer again, no need to remove first.

However, I found an issue, only if you flashed platform-tools 20210517. 20201221 and 20210129 are ok.
The keyboard kernel module doesn't output keyboard messages like previous versions, so the overclock script won't be able to detect if you pushed F0 key to skip it.
If the system hangs, then the only way to recover will be platform tools.
However I tested replacing that file (/dso/etc/fpga_i2c_kbd.ko) with the 20210129 version, and it works.
Last update that changes that file is 20210311.

[rtausx]

I'm new to this community. I started running into some issues with my new DSO2C10 today. It started freezing a lot trying to decode some I2C to the point where it would not respond at all after a reboot; the default setup button did not respond at all.

After a few hours of reading around the forum, I decided to try the platform-tools but it seems that the ones available at DavidAlfa's Gdrive are not suitable for my FW version. 

I think I need the platform tools for FW3200, does anyone have it?

I tried the three available in the Gdrive and after restarting the scope it will just show the Hantek logo...

Thanks

[rtausx]

I'm new to this community. I started running into some issues with my new DSO2C10 today. It started freezing a lot trying to decode some I2C to the point where it would not respond at all after a reboot; the default setup button did not respond at all.

After a few hours of reading around the forum, I decided to try the platform-tools but it seems that the ones available at DavidAlfa's Gdrive are not suitable for my FW version. 

I think I need the platform tools for FW3200, does anyone have it?

I tried the three available in the Gdrive and after restarting the scope it will just show the Hantek logo...

Thanks

Forgot to mention that my scope was running FW3200, 20210416 before all this.

[DavidAlfa]

Try flashing any platform tools version you like. I'd try the latest. Then use FW changer to restore FW3200.
But before flashing anything try to backup your system with the backup builder!
If it hangs shortly after boot, try pressing quickly default setup button, hopefully it will be enought to run the mods.

[rtausx]

Try flashing any platform tools version you like. I'd try the latest. Then use FW changer to restore FW3200.
But before flashing anything try to backup your system with the backup builder!
If it hangs shortly after boot, try pressing quickly default setup button, hopefully it will be enought to run the mods.

Thanks for getting back to me. I actually tried the latest platform-tools 20210517 and wanted to clarify that after it finished flashing, the scope rebooted as expected but it's now stuck with the Hantek logo so I have no way to get to the system update menu unfortunately.

I think I soft bricked it by using the wrong platform tools for my fw version 3200.

I will appreciate any further insight.

[DavidAlfa]

I'm pretty sure it failed uploading some file and you didn't read the update window.
First remove the USB drive, you can't have both plugged in.
As far a I know it's impossible to brick it.
Read my FAQ. USB 3.0 ports give problems.
Read carefully the output of the update process.

[Gerasim]

rtausx I, too, a couple of times after using platform tools, the scope showed only a splash screen.  Repeat the procedure one more time.  Make sure that the driver is displayed correctly in the device manager and immediately run cmds.bad.  And if the driver is not detected, then reinstall it using zadig.exe.  And run cmds.bad right away.  Good luck!