Jul 08,  · HantekBL that could have been downloaded from our website for free. HantekBL is developed for Windows XP/7/8/10/11 environment, bit version. The following version: was the most frequently downloaded one by the program users. This free program is a product of hantek. Oct 14,  · jakob_nik Publish time BL signed drivers for Windows10 I have recently purchaced a PC oscilloscope BL but unfortunately I can’t get it to work because the drivers are not signed for windows Is it possible to get signed driver files for windows 10 for this Hantek BL scope. Apr 08,  · The control section has to send a ground voltage to the base of the PNP transistor at pin 11 to make it turn on Hantek: Hantek: BE: Hantek: DSO BL: Hantek: BE: Hantek: DSOB: Oscilloscope: Hantek: DSO ScopeMeter: Hantek: DSOB: Hantek: DSO Kit VIII The normal marketing software offers only the visible features but .
 
 

Hantek 6022bl driver windows 10.How to install PC Oscilloscope (Hantek 6022BE) on Windows 10 and 11

 
High performance, MS/s real-time sampling, 20MHzMHz bandwidth. Operating System: Windows 10, Windows 8, Windows 7, Windows NT, Windows XP, VISTA. If you’ve had some trouble installing the drivers from Hantek for windows 10, there’s a few issues that need to be resolved.

Hantek 6022bl driver windows 10 –

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community. Already on GitHub? Sign in to your account. Using the latest openhantek 3. Still I get the error “Connection failed! Couldn’t open device: Operation not supported or unimplemented on this platform”, but there’s a twist: when I select “DSOBL” from the drop-down in openhantek initial window btw, it shows green , it immediately says “The device is ready for use”, and this text stays up for less than a second, then the drop-down automatically changes to “DEMO” and the “Connection failed!

Now, if I’m fast enough to click OK during these milliseconds when “The device is ready for use” shows, the main window opens and it’s almost functional, except that there’s no graph, and I see “ERR” messages in place of the graph. The text was updated successfully, but these errors were encountered:. Sorry, something went wrong.

As said in windows-usb-access you must not use the original driver! Go do device manager and select Uninstall Device and ensure you tick “Delete the driver software for this device”.

Then follow the steps to install the Zadig driver twice! The screen shot shows measured values at the bottom of the scope this means the USB communication is up and running. Hi DaPa , thank you for the input and sorry for the confusion. I did not use the original driver.

If you take a look at my initial message in this issue, I did follow the instructions for the Zadig driver, did it twice! Next, I was advised by zen67 to install the driver that comes along with the OpenHantek not the original driver from the Hantek manufacturer, I never installed it actually. So I did that, and was still having the described issue. I will again outline my full set of steps to avoid confusion.

I’m thinking maybe this is some kind of unsupported flavor of BL? Hi Ho-Ro , just tried the switches, you were right, –useGLES helps to remove errors and there’s a graph now, thank you! I will see if I can fix my OpenGL. My guess is maybe the name is pulled from device itself? In any case, it should not matter if the driver is the same, should it? I guess we can say this issue is almost solved.

Almost because I still have to quickly press “OK” on the device selection screen after selecting DSOBL and before the error appears, to enter main window. If anyone runs into similar issue, the solution is:. Are there more devices visible in this list the list on the top of the window? I tried all 3, no diffierence I’m not using a USB hub. The only thing I didn’t try is replacing the cable, the computer is at the remote location, I will try to do it once I’m there.

Please check if the latest windows artifacts solve your problem. I have finally not only caught the symptom of bogus VIDs but now correctly ignore the demo device when detecting the devices available on USB. This version without new functionality as b is available in unstable. Thanks for your help to make OH more robust.

Skip to content. Star New issue. Jump to bottom. Connection failed with BL on Win10 20H2, used zadig, read the docs and comments Labels Windows Windows related, wontfix unless a volunteer steps in. Copy link. Now, if I’m fast enough to click OK during these milliseconds when “The device is ready for use” shows, the main window opens and it’s almost functional, except that there’s no graph, and I see “ERR” messages in place of the graph The text was updated successfully, but these errors were encountered:.

All reactions. Nope, didn’t work unfortunately. Here’s what I did: removed all devices related to Hantek in device manager with “show hidden devices” under Universal serial bus devices installed driver from the OpenHantek archive rebooted verified that the right driver is being used for Hantek devices it has Korean signature, hope it is the right one – see screenshot?

Here are the screenshots All reactions. My setup: Windows 10 20H2 build Couldn’t open device: Operation not supported or unimplemented on this platform” with the twist described in my first issue Repeated these set of steps for libusb-win32, libusbK – the problem was still persisting.

Set of steps suggested by zen67 in his comment removed all devices related to Hantek in device manager with “show hidden devices” under Universal serial bus devices installed driver from the OpenHantek archive rebooted verified that the right driver is being used for Hantek devices it has Korean signature, hope it is the right one – see screenshot?

Opened openhantek. Couldn’t open device: Operation not supported or unimplemented on this platform” appears. Waited for success. Started openhantek. I did not use the original driver Ho-Ro added the Windows Windows related, wontfix unless a volunteer steps in label Dec 21, Strange, I never saw this behaviour under Linux. What do you mean with Some thoughts: If you have any other devices connected to the USB busses then please remove them.

Is this an USB3 connector on your laptop? Connect the scope to a different USB plug. Use a different USB cable. Do you connect via an USB hub? The only thing I didn’t try is replacing the cable, the computer is at the remote location, I will try to do it once I’m there All reactions. Update: tried replacing the cable, made no difference All reactions.

Ho-Ro added a commit that referenced this issue Dec 27, This was it. I tried b and the issue is solved. Thank you. Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment. Windows Windows related, wontfix unless a volunteer steps in. You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window.

Here are the screenshots. Update: tried replacing the cable, made no difference.