New Hantek DSO2X1X models?

[DavidAlfa]

Geoff, your repaired backup is ready, download it from the same place .

[DavidAlfa]

I updated dsoflash tool, making a lot of optimizations.
Now both read and write operations take ~24minutes @ 95KB/s (2x faster read), probably as fast as the FEL protocol is capable of.
Binaries and source code updated! 

[DavidAlfa]

Came home, powered it on....

[vistorik]

Geoff, your repaired backup is ready, download it from the same place .

DavidAlfa, the calibration coefficients A = 0.832178 and B = 5.167167 in the binary ee.bin in the dso3kb_CNXXXXXXXXXXXXX_EE.upk and in the dso3kb_CNXXXXXXXXXXXXX_EE.tar.bz2 are wrong. They dont't match the hex values in the dds_calbration.dat in the dso3kb_CNXXXXXXXXXXXXX_Calibration.upk and in the dso3kb_CNXXXXXXXXXXXXX_Calibration.tar.bz2. The correct calibration coefficients that should be in the ee.bin are: A = 0.840267, B = 9.324291. See please the attached photos. This doesn't matter for Geoff since he probably has the correct calibration coefficients in the EEPROM.

[DavidAlfa]

Ah, yeah, that's a backup from my own EEPROM!
Since I flashed my scope with that, fixed the boot issue and made a backup afterwards, missed the fact the EEPROM was still my own.
Edit: Fixed!

[Geoff from Oz]

Thanks Visitorik,
Much appreciate your extra checking (not to mention all the help DavidAlfa has given me).  Glad the calibration settings problem doesn't seem to affect me :-)

[Geoff from Oz]

Hi DavidAlfa,
I've downloaded the repaired package from your Google Drive, and stored it away safely, in case I ever need it. One again, thank you
I'm presuming that the calibration coefficients problem spotted by Visitorik won't be a problem, since it seems that my scope has them already stored in my EEPROM.
Is there any other difference that I should look out for in the repaired backup, or can I just use the backup safely if/whenever I need to?
Cheers
Geoff from Oz
PS Now I have a working scope again, I've been trying to get the Keysight SCPI connection to work (I'm not knowledgeable enough yet to really need it, but it seems like a useful thing to know how to do).  Not having much luck yet though, the IO Connection Expert doesn't detect the scope.  I think it's something on my pc though; the driver for the "USB Test and Measurement Device (IVI)" isn't completely happy, it says it needs further installation (whatever that means).  I will first do a bit of google research, then try removing the devices and starting again. (or possibly, just park the idea for now, I'm keen to get back to the project I was using the scope to explore when the "frozen" problem happened.)

[vistorik]

I'm presuming that the calibration coefficients problem spotted by Visitorik won't be a problem, since it seems that my scope has them already stored in my EEPROM.

Hi Geoff,
you could easily check whether your EEPROM contains the factory calibration coefficients. Run the dso3kb_PT24C02_damp.upk like update from the USB drive. It creates a PT24C02_damp.bin file on this drive. Look at this file in any hex-editor. If you find at the end of this file a string 0.8402679.324291, then your EEPROM has the factory calibration coefficients that correspond to their hex values in the calibration file /cache/dds_calbration.dat.

PS Now I have a working scope again, I've been trying to get the Keysight SCPI connection to work (I'm not knowledgeable enough yet to really need it, but it seems like a useful thing to know how to do).

It is known that Keysight SCPI is not compatible with Windows 11.

[DavidAlfa]

I've downloaded the repaired package from your Google Drive, and stored it away safely, in case I ever need it. One again, thank you

Please re-download it, I added your original EEPROM. That would be all.

[Geoff from Oz]

All looking good, MANY thanks yet again 

you could easily check whether your EEPROM contains the factory calibration coefficients.

Done :-)  My  EEPROM does have the factory calibration coefficients that correspond to their hex values in the calibration file /cache/dds_calbration.dat.

It is known that Keysight SCPI is not compatible with Windows 11.

Duh! You have saved me from much  THANKS

Please re-download it, I added your original EEPROM. That would be all.

Done :-) Downloaded and stored away safely.

[gritzlaszlo]

Hi!
I have a DSO2D15. After a couple of minutes of use it started to show the following symptoms.

https://drive.google.com/file/d/1ByR_9ueos3tpGteahgUM_qE_qPZ1a33M/view?usp=share_link

I waited the recommended 30 minutes of warmup and then tried to do calibration, but it escaped with error message (at the beginnig of the process).

I did full restore with platform tools. The problem still exists.

I have no idea whether it is a hardware or software problem.

Can anyone help me, what are the steps of the calibration process? It could take me closer to the truth

Thanks,

Laszlo

[DavidAlfa]

Perhabs wrong fpga firmware.
Try installing 3102, calibrate again, if getting error then try 3202 or 3205.
If still failing, it might be a hardware issue.

[gritzlaszlo]

Thank you David!
Unfortunately, it seems to be a hardware error.
I tried three different FW versions you suggested. No positive result.
I'm afraid I have to continue exchanging mails with the factory...
So far they have only had ineffective suggestions...
Thank you very much again.

[michael41742]

Need help!
Can't get my new 2D10 working with DSO software under Win11.
Windows Device Manager shows properly installed USB device driver but Keysight Connection Expert 2022 still doesn't recognize the scope 

[vistorik]

Can't get my new 2D10 working with DSO software under Win11.

The DSO software is not compatible with Win11. Try Win10. See some posts above.

[coromonadalix]

Try compatibility mode

[simba15]

So with regards to the noise that is picked up by the scope.

Its not too bad (with proper ground) but it is certainly noticeable when looking at small signals or compared to other devices.

Is there a remedy for this? I have see lots of ideas in this thread but it seems there is no definitive solution

I seem to have the older power supply design.

Thanks.

[michael41742]

So with regards to the noise that is picked up by the scope.

Is there a remedy for this? I have see lots of ideas in this thread but it seems there is no definitive solution

I seem to have the older power supply design.

Thanks.

The noise is about 250uV with no probes attached.
You could use probe with ground spring to minimize RF-noise pickup.
Unfortunately Hantek probes come without ground spring but you can easily do it yourself.

[simba15]

Thanks, I will try some old TEK ones and see if that improves.

Any other improvements that could be made to the Power supply?

[masta_k74]

There is not much that can be done to improve the power supply as far as interference is concerned. I bought a decent oscilloscope (Siglent SDS 1104X-E, hacked to 1204X-E) for home use. I took my Hantek device with me to our hobby car workshop. For measurements on a car, the device is absolutely sufficient, as it is very rarely a matter of such small signals that the interferences could become a problem. Here, an expensive oscilloscope would also be much too bad, because you can certainly imagine how the device will look after some use.

[Prerunning]

Mine was "bricked / boot looped". Upping the points to 400K+ regularly crashed it but a few days ago it finally boot looped so bad i couldn't change any setting or hit stop before the scope would lock up.
Reboot.
Repeat.
I had to recover with FEL using the CLI tools from this post.
My OG backup is safe. When i restore it carries over the higher memory depth and same boot loop. But the calibration should be good?
The AFG is pretty much unusable now. Im still working on extracting the calibration from my backup, but i got side tracked once it stopped crashing...

FYI
I updated the fpga fw which fixed my HORRIBLE crashing issue. The scope is actually useable now. I can use 8m on both channels and the scope hasnt crashed since.
I tried the basic software update and applied the 150mhz hack a few months ago with a usb stick in the front port but it didnt do much for the crashing issue and noisy signal.
This scope really seemed like a broken design. Pretty discouraging when the Hantek update didnt fix the freezing or anything else, but DONT give up. This is a great hobbyist scope once it stops crashing. Update the fpga fw then crank up the points and enjoy.

[coromonadalix]

@Geoff

On Win11   for the keysight connection software,  i had a bug for my 34410a meter with them,    i was suggested  a rhode shwartz  visa driver package

Worked fine,  when starting R&S   you have to select wich driver you want to use,  and keysight  will work with it in my case ...

my 2 cents


RS_VISA_Setup_Win_5_12_8.exe
https://www.rohde-schwarz.com/ca/driver-pages/remote-control/3-visa-and-tools_231388.html

[DavidAlfa]

Is it really a bootloop or it just freezes at Hantek screen?
PM your backup, I'll try to retrieve your cal data.
Actually will burn it to my scope and get them from the serial port.

[Prerunning]

Is it really a bootloop or it just freezes at Hantek screen?
PM your backup, I'll try to retrieve your cal data.
Actually will burn it to my scope and get them from the serial port.

Im not sure the correct term. It boots like normal but instantly locks up after initialization. If you reboot and press default or channel off it still instantly locks up.
Soft bricked?
Ill send you the backup rn.

[DavidAlfa]

It boots like normal but instantly locks up after initialization.

Yeah, corrupted settings crashing the system on booting. Happens from time to time, Hantek didn't provide any simple safe booting method to overcome this.
PM sent with restore files.
Consider installing the Factory Reset Daemon mod to avoid this in the future.