New Hantek DSO2X1X models?

[vistorik]

Try to use

Code: [Select]

hexdump -C /cache/dds_calibration.dat

Yes, it helped:

Code: [Select]

phoenix login: root
unix:path=/var/run/dbus/system_bus_socket,guid=b5541119dc7a0579c1a406840000000d
# cd /cache
# ls -hl
total 12
-rw-r--r--    1 root     root           0 Jan  1 00:00 anolis.conf
-rw-r--r--    1 root     root        2.1K Jan  1 00:02 cali.dat
-rw-------    1 root     root          40 Jan  1 00:00 dds_calbration.dat
-rw-r--r--    1 root     root         239 Jan  1 00:00 system.inf
# hexdump -C dds_calbration.dat
00000000  10 00 10 00 00 00 00 00  75 cc 79 c6 be e4 ea 3f  |........u.y....?|
00000010  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  |................|
00000020  84 46 b0 71 fd 4b 1f 40                           |.F.q.K.@|
#
Thanks. Another question. Is there an easy way to copy a file from the device's file system to a Windows computer and vice versa using the PuTTY? I cannot use the front usb port of the device because the back port is is used for connection to the computer. I'm sorry for this question, but I couldn't find any suitable and simple linux command(s).

[DavidAlfa]

You can use zmodem, I've used it many times.
Windows support is messy, better use Linux/Ubuntu.

You can also use SecureCRT software, it fully supports zmodem, it's really handy, you can download the demo.
To receive a file from the scope, you only need to run "sz <file>" in the shell, it will automatically receive it.
For sending, just drag&drop a file onto the terminal and it'll send it.

[vistorik]

You can use zmodem, I've used it many times.
Windows support is messy, better use Linux/Ubuntu.

You can also use SecureCRT software, it fully supports zmodem, it's really handy, you can download the demo.
To receive a file from the scope, you only need to run "sz <file>" in the shell, it will automatically receive it.
For sending, just drag&drop a file onto the terminal and it'll send it.

Thanks. I've used SecureCRT and it works.

[chaicl]

I just received my DSO2C10.  When I plugged in a USB, the DSO kept beeping. I wonder is there a maximum size for the USB drive?  I tried 2T and 256G both beeped unendingly...

[trazor]

Just arrived to this thread. My 2C10 is bricked. Contacted support and they sent my an update file, which obviously I can't execute because I can't get the UI working. Anyway. Attached the file so proficient users can take a look. I will go 30 pages back and start the unbrick procedure. This device is a mess and I regret not having spent 100 dollars more to get a Rigol 1202ze.

[DavidAlfa]

When I plugged in a USB, the DSO kept beeping.

Use only FAT32 formatted drives.

My 2C10 is bricked. Contacted support and they sent my an update file, which obviously I can't execute because I can't get the UI working.

Thanks for the update.
Is it still working, but unresponsive to the keypad?
Try connecting it to the computer, does it get recognized?
If so, you could send a factory reset command through scpi.

Install SCPI (Available at Hantek download page).
Connect the scope to the computer.
Open SCPI console and write "PRIVate:FACTORY:RESET"
(Keep uppercase/lowercase as that).
All settings will be resetted and should work again, avoiding the flashing step.

[trazor]

The device is connected but doesn't respond to any input using "DigitalScope" application or the "Keysight Connector Expert IO". I will need to use platform tools 

[DavidAlfa]

Is the scpi driver installed?

No worries. Did you make any picture of system info or a backup using Backup Builder?

- Run latest platform-tools
- Apply USB Fix (Will require several presses on Update to make the USB work, this is what USB Fix will address)
- If you made a backup, restore the full package.

Otherwise:
- Install the original FW version if different, use FW Changer.
- Restore original SN, HW with Script Launcher.

[trazor]

Is the scpi driver installed?

Yes it was.

No worries. Did you make any picture of system info or a backup using Backup Builder?

I did not take any picture since I was naively using the device (with occasional reboots) until it bricked by selecting 8Ms and doing a "single seq". Then googled and arrived to this thread. I understand that I lost the serial number, calibration for signal generator, etc.

I'm quite worried. I did the recovery operation with platform tools versions:

»  2021.07.26, FW3202 (first time)
»  2021.05.17, FW3102 (second time)

all steps went good without errors but the DSO doesn't boot after. It shows the QR image and then locks at the following screen "Hantek Your testing solution provider"

Has this happened before? I think I saw the pinout for the serial port in this thread. Should I try to see the boot logs?

I don't know if it is related, but before the recovery the device locked up in graph screen, tried to setup parameters (because some buttons turned off) but I don't remember hearing the relay clicks.

[trazor]

Ok. Found the problem. The "English readme" is wrong. It says to do:

1) sunxi-fel uboot images/uboot_fastboot.bin
2) click cmds.bat

If I do (1) the first command on cmds.bat fails (which I didn't notice because it happens fast). So, I succeeded skipping (1)

@DavidAlfa in your excellent guide you may remove the string "For more info, refer to the the readme file inside platform-tools package." and put in red "Don't follow instructions in the readme_English.docx file!" . That file is a trap for fools like me. 

[DavidAlfa]

Ah, FW3202 platform tools has a weird english readme, not like the others, and it's missing the PDF file.
Will correct it.

Edit: Actually most Readme files were wrong!
Made new ones, you can check it out here (If Hantek can't properly make a simple Readme, guess their programming quality lol).
Added usb fix, serial/model/Pcb fix and FW versions, so everything required to restore the scope comes in a single package.

Created new update package for 2022.09.21 software, keeping only the the update of the software (The FW isn't updated forcefully). Apparently It just updates Russian translations.
Created new FW package, adding FW3205. Seems for 3200+ only, breaks calibration on FW3000-3102.
Updated all Platform-tools packages with the new Readme and fixes.
(Edit:2022.09.28 was the same software as 2022.09.21, it just enforced the FW3205 update. So renaming to 2022.09.21.)


BTW, CH1 had became a lot noisier than CH2, picking up high frequency spikes of about 100mV.
Fixed by just twisting/pressing hard on the BNC connector! SO just try that if you're having a similar issue.
Both have now a noise of about 1/5 division at 2/20mV/div (1/10x).
Edit:  Tapping on CH1 BNC creates some rattle noise, probably the nut is loose from one of the thousand times I opened it, which would explain the RF noise.

[vistorik]

(Edit:2022.09.28 was the same software as 2022.09.21, it just enforced the FW3205 update. So renaming to 2022.09.21.)

David, it seems that the dso3kb_20220921.upk from your drive.google.com/drive/ doesn't update to the FW3205. The do_update.sh doesn't have such command:

Code: [Select]

#cp /dso/app/phoenix /mnt/udisk/
#cp /lib/firmware/psram_board_test.fs.bin /mnt/udisk/

cp $WORKPATH/package/help/help.db /dso/app/
cp $WORKPATH/package/font /dso/app/ -rf
cp $WORKPATH/package/root/* -rf /

#cp /dso/app/res /mnt/udisk -a
#cp $WORKPATH/package/app /dso/app/ -rf
#cp $WORKPATH/package/vga_test /dso/app/ -rf
#cp $WORKPATH/package/vga12MHz.txt /dso/app/ -rf
The dso3kb_20220921_fpga_3205.upk updates to the FW3205.

[DavidAlfa]

Its seems you didn't read properly:

Created new update package for 2022.09.21 software, keeping only the the update of the software (The FW isn't updated forcefully).

So anyone can update to this software version without flashing the FW. Is it clear now?
There's a FW3205 update package to manually update it, but also the original package was added to the "non-safe" updates that will update the fpga, causing issues in a non-compatible system.

Created new FW package, adding FW3205.

»  Quick glance  «
...
»  For scopes coming with FW320x, update to FW3202, FW3203(Fix for noisy spikes in 4M/8M memory depths), or FW3205 (New version, barely tested yet).
    Features or compatibility of FW3204 are unknown, but it seems to break the decoder, try installing FW3202 or FW3205. 
...
»  System Updates  «
...
These can be applied safely:
...
»  2022.09.21 (Only fixes Russian translation?)
...
These will update the fpga FW version:
...
»  2022.09.21_fpga_3205 -> Sets FW3205
...
»  Firmware versions  «
...
»  3205_B205 (Supposedly it fixes the decoding problems from 3204)

[vistorik]

And what does meen this?

(Edit:2022.09.28 was the same software as 2022.09.21, it just enforced the FW3205 update. So renaming to 2022.09.21.)

[DavidAlfa]

Because I also got the package dso3kb_20220928.
When checking the differences, the software (phoenix) was exactly the same (2020.09.21, same md5 hash), the only difference was the forced fpga update:

Code: (20220921) [Select]

cp /lib/firmware/psram_board_test.fs.bin /mnt/udisk/

Code: (20220928) [Select]

#cp /lib/firmware/psram_board_test.fs.bin /mnt/udisk/
So I just renamed the 2022.09.28 package to 2022.09.21, which only updates the software, to avoid confusion with the nosense name 2022.09.28 (As the software is still .21).
Then the "original" 2022.09.21 that updates to FW3205 was renamed to 2022.09.21_fpga_3205.

[vistorik]

Then the "original" 2022.09.21 that updates to FW3205 was renamed to 2022.09.21_fpga_3205.

Thanks. Now it's clear. I just didn't notice the file 2022.09.21_fpga_3205.upk on your drive.google.com/drive.

[DavidAlfa]

Because you're faster at finding issues than me at updating things, I was on the process of updating the Drive/FAQ when you posted, the file wasn't there yet

[DavidAlfa]

Updated Backup Builder, now all possible backup combinations are generated:
Removed Eeprom_backup package, now redundant.

»  Backup Builder: Backups all important system data and builds three main update packages, so you can quickly restore them:
     »  dso3kb_CNxxx.upk: Restores Model, Serial, HW, FW, Generator calibration, preserving the existing software.
     »  dso3kb_CNxxx_FULL.upk: Restores Model, Serial, HW, FW, Generator calibration and dso, overwriting the existing software.
     »  dso3kb_CNxxx_EE.upk: Restores system EEPROM.
     Extra packages:
     »  dso3kb_CNxxx_FPGA.upk: Restores only the FW (fpga).
     »  dso3kb_CNxxx_Calibration.upk: Restores only the Generator calibration.
     »  dso3kb_CNxxx_Model.upk: Restores only the Model, Serial, PCB.
     »  dso3kb_CNxxx_Software.upk: Restores only the software.
     Additionally, it will create a tar.bz2 for each package to allow easy inspection of the files.

[Maxie]

My scope broke down. It was switched on, but I wasn't using it, was just soldering something. I left a waveform on the screen from the previous measurement.
Suddenly it started making a clicking noise so I looked up. The screen is now blank, the startup relay keeps clicking about 2x a second and all the colorfull button lights blink as well.
It is as if the scope is trying to power on but the protection kicks in. I was hoping it may have overheated so tried a few hours later to switch it back on, but this behavior is now permanent. Maybe there is a short circuit or something?
Now I have to open it and look inside. Haven't opened it yet, about 10 months old and probably has 20-30 hours usage.
If anyone has an idea what could have gone wrong, please reply.

[morgan_flint]

Might well be a power supply failure, it has been reported that the main diodes are a bit underrated and get very hot. I'd open the scope and check the power supply output voltages as a first check.

Th PS schematics (and all the schematics, in fact) are here.

The diodes marked as D5 (two SS310 in parallel) are the "main diodes" I was referring to.

[Pierre74]

My scope suddenly lost calibration, and i cannot re-calibrate it, i get an error 0x511d1 only and have crazy DC offsets on both channels. I previously updated the software with the official SW update from the Hantek website, but i don't know what stock SW and FW was on the scope. Now it's on FW 3203, SW 220210.00. The scope worked fine for a week with this software. Can this be a software issue or is it hardware related? If anyone have a clue, please reply.

[DavidAlfa]

Install fw3102 and try calibration again.
Read the FAQ on Page 8

[Maxie]

I'd open the scope and check the power supply output voltages as a first check.

Thank you for the advice and the links to the schematics.
I have done this, there is in fact something wrong with the PS board.
It has 3 voltages, +8V -8V and +5V and all of them are not stable, jumping all around the place.
If I supply +5V to the mainboard, the scope boots up and freezes at the HW initialize phase. I guess it needs the 8V rails.
I'm now checking the components on the PS board. The diodes look fine ...

[mwb1100]

Haven't opened it yet, about 10 months old and probably has 20-30 hours usage.

Surely Hantek provides at least a 1 year warranty? (but maybe not, I couldn't find any warranty info from a quick googling)

[Maxie]

OK, my scope is back up and running.
Unsoldered the diodes and the capacitors on the secondary side, tested them one by one.
Also tested all the resistors. Unsoldered the buck IC and the DK124.
Couldn't check the transformer waveform since I had no working scope, but everything else checked out fine.
Started to loose hope. Injected voltage and checked the feedback circuit. Everything was OK.
Then I soldered wires to the optocoupler, and manually switched the diode side. The voltage drop on the diode was good but the transistor never went low resistance.  Of course its always the last part you check.
I changed it with a through-hole 817C I had in my parts bin and the PS came back to life.
It now has stable output voltages.