New Hantek DSO2X1X models?

[Pierre74]

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

Unfortunately this didn't help. I tried every possible combination of FW/SW also low level tools but the problem persist. Interesting is, if i change the vertical position of a channel, the change is not proportional. Like if i set vertical position to 0V on channel A, nothing connected to the probe, the yellow line stays at 2V. If is set offset to 1V, the yellow line moves to 2.1V. At about 2.2 V they meet, and then at 3V the yellow line is now 2.3V or something like that. The other channel behaves the same but with different proportions.
It seem as if a channel had a fix offset voltage and the vertical position now changed another offset on top of that but with much less power.
Since both channels does the same, and this happened during use, not after an upgrade, i suspect it's a hardware issue... Maybe somewhere in the offset signal generation part, around the opamp U20.2 - that's the only common thing in both channels offset circuit...

[DavidAlfa]

Then it seems a hardware failure...

[morgan_flint]

OK, my scope is back up and running...
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.

Congrats! Good to know the optocoupler is prone to failure.

...
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 ...

Somebody also reported freezes when the power supply's TR signal (for line trigger) was absent, this could also be the cause of your freezing but, on the other hand, I've tested grounding this signal and the scope booted without problems

[dirtmover]

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

According to the warranty card that came with mine it's 3 years on the scope and 1 year on accessories. Of course, given the abysmal level of ongoing customer support they currently provide, I expect that warranty probably isn't worth the paper it's written on.

[DavidAlfa]

Huh? Probably stolen paper, printed by kidnapped kids.

[badbod]

DSO2D15 arriving tomorrow...   eeekk..  can't wait....  seriously,   who could?  I mean, let's be real,  DOOM !!!!!!!

il do the boring stuff first, check some wave forms and whatever,  dump the firmware with DavidAlphas hard work and upload it etc,  but then the serious work, the whole reason we are here,  DOOM!!!!

hmm given the scope does seem a bit noisy (by all accounts) then I guess it is gonna be hard to work out idle time,  think DOOM Screensaver!!!!

BaDboD

[DavidAlfa]

That's a pretty expensive DOOM running device though

[badbod]

getting a good framerate , 1993, PC eerr, yah no comparison, this is way cheap. Wonder if we can get Jetpac (ZX-Spectrum) qemu Z80?  nope, DOOM!!! enough. Ideas on making it a screensaver, pretty sure some answer to the fact the CPU is never idle.

can we hook the trigger event?  Squinting at code apprehensively, but if there is an event for trigger, and we dont see any for a while,  BOOM!!  DOOM!!

[badbod]

What governor is the kernel using?

 (prelim investigation while awaiting arrival of the specimen to give it a good probing)

[DavidAlfa]

All the keys are functional, there's a picture in the Doom folder showing them.
Governor? 100% speed all the time.

[badbod]

ok, it has arrived.

DSO2D15
Software: 1.0.2.0.0(220831.00)
Hardware: 003.002.001.000.000.000.000.001
Firmware: 3205

now to bone up on the FAQ and back it up before I start pounding it looking for bugs  :-)
I think IIRC the soft and firm are the latest you already have? FAQ time.

[badbod]

Anyone know how to get the Hantek software working?
Keysight Connection manager does not see it, the device is shown in device manager after installing Keysight IO Suite ( Hantek supplied and the latest from Keysight ):
  USB Test and Measurement Device(IVI)

Windows 11 22H2

Searches are fruitless :-(

[DavidAlfa]

Try latest IO library suite from Keysight.
Working for me, also with Win11 Pro 21H2
Tested in several USB ports, 2.0 and 3.0, the device was instantly recogniced in all of them.

I remember having a lot of trouble with the Hantek-supplied version, having to re-install the suite everytime I plugged the scope.

[DavidAlfa]

So I did my best to figure out a safe and simple way of triggering a factory reset from inside.
Relying on a computer to fix it is very inconvenient, what if you don't have any nearby?
So I used a early system poweroff/reset detection.
If the system hangs after the second Hantek logo, or the user interface stops responding, power it off several times following the instructions.
I added visual feedback by toggling the backlight when the detection is triggered.

Hopefully, with Factory Reset Daemon, we will rarely need to use Platform-tools again!
As always, available on the FAQ section.

Procedure in action:

[badbod]

 yes, thanks for confirming. That was the the first one I tried, then the Hantek supplied one (just an older version)  Very weird, I got it working anyway with the latest 2022 update 2 from Keysight after removing/re-installing every driver for every device in the system, not used to having problems installing drivers for anything, was a real 'remove driver, update driver, re-install drivers many times' fest.

First problem (hardware), being detected as a device by windows.

USB2 Mainboard, will not detect in one port, fine in the port next to it, fine with unpowered hub of any USB version in both ports.
USB3 Mainboard,  ^^^^^   exactly the same no difference some ports fine other nada, all good with a hub
Extension cables or  A->B cables: only supplied cable worked, all cables work if hub (powered or not,USB2 or 3)

-- Works fine in either USB2 or USB3 and generally if you have any problems you NEED a hub? err , hmm, yeh

Second problem (windows) once correctly detected as shown by device manager;  getting it detected by Keysight IO connection expert.

Something in the driver stack refused to allow keysight IO to talk to the device even though correctly detected by windows. Event Viewer was it's usual 'as helpful as a stab in the eye' I still don't know what the fix was. Not my initial suspicion of Core Isolation or WSL2 (desktop runs in 'virtual' if you install WSL2)  nor safe boot, which it wouldn't be anyway, the IO libraries are recent and signed.

good news though, the Hantek 6022BE worked fine no matter what I did, could not get it to fail. both hardware and software are way more robust. :-)

Did you want a copy of this backup? You seem to have these or newer version already. But if there is anything to be gleamed from a current factory state backup, it is all yours if you want it. The scope has been on for 24 hours, I have been twiddling asll the knobs, no crashing or bugs as I can find.
 I would need to step back through the various threads and test each scenario, but everything seems fine, offset all good,  low noise (earth needs checking , low noise with USB cable plugged in or attaching an earth anywhere actually so I think it is not connected in the unit? obs quite noisy without an earth)


Regards
BaDboD

[DavidAlfa]

If your software or firmware versions are already available, I don't need anything, but thanks anyways!

[Russ3000]

I'm currently at work on my V2 version. (Attachment Link) (Attachment Link)

I modified the native power supply, the result is positive, it heats up less and the signals become cleaner.

[DavidAlfa]

I did the same long time ago, added more ferrite beads, placed lots of tantalum capacitors all over the board, no difference.
Some people have tried toroidal transformers with linear regulators, also with minimal impact.

Likely the noise is induced by the board itself by nearby digital signals from the SPI, i2c, LCD...

Perhabs adding a ferrite bead to the LCD rubbing cable would help, but I definitely don't expect easy miracles.

Also this is a 2-layer board, where a 4-layer pcb would provide much better shielding.

[Russ3000]

I replaced the diodes on the secondary side of the power supply with more powerful and faster ones, this helped with its overheating, and at the same time improved the quality of the power supply and the picture on the screen. It's a pity, but I did not take pictures of the screen before the rework for comparison.

[DavidAlfa]

People is obsessed with these diodes.
Not denying the temperature, but I'm still waiting for the first case of failure

[badbod]

R.E the unreliable USB, the supplied USB cable is junk. Lucky my grandad had one of these antiques lying around I could test with. Ill have to see if these relics of yore can still be obtained in a high quality version but I imagine even gold plate, audiophile grade USB connectors, would have rusted from the inside by now.  Ill do that after I finish demagnetizing my CD collection for less hiss, broader sound-stage and lower THD.   :-)


BaDboD

[Russ3000]

That's a pretty expensive DOOM running device though

Convenient phone charger. 

[BillyO]

Convenient phone charger. 

But not reliable. 

[Russ3000]

DSO2D15
SN 221002902xxxx
S  1.0.2.0.0.(220921.00)
H  003.002.001.000.000.000.000.001
F  3205

What is missing?

[DavidAlfa]

Seems fine 

Edit: New software update available: 2022.10.28