Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

hantek 6022be connection failed win 10 #301

Closed
seraphie21 opened this issue Jul 7, 2019 · 6 comments
Closed

hantek 6022be connection failed win 10 #301

seraphie21 opened this issue Jul 7, 2019 · 6 comments

Comments

@seraphie21
Copy link

hey, recently i'm searching for replacement software for the hantek 6022be and i found openhantek, but everytime its always say connection failed, i've tried this on 4 diff pc with win 10 and always get the same problem

@Ho-Ro
Copy link
Member

Ho-Ro commented Jul 8, 2019

openhantek ist unmaintained (#277) and deprecated. Pleased try my OpenHantek6022. For windows you have to follow the driver installation procedure: https://github.com/OpenHantek/OpenHantek6022/blob/master/docs/build.md#windows
As I don't use windows I checked it only very limited in a virtual win7 installation.
IIRC you have to install the drivers with zadig two times - 1st for the newly plugged scope without firmware (VID/PID 04B4/6022) and then a 2nd time for the scope with firmware uploaded (VID/PID 04B5/6022).

@seraphie21
Copy link
Author

seraphie21 commented Nov 26, 2019

hey, sorry for long reply, because i forgot the email for this acc, anyways, thanks for your help, but i still cant make it work, and you mentioned that "2nd time for the scope with firmware uploaded", what's that mean and is it not included at zadig ?

@Ho-Ro
Copy link
Member

Ho-Ro commented Nov 26, 2019

When you connect the scope, it starts without firmware and shows USB vendor / product ID 04B4/6022. When openhantek detects this device, the firmware is uploaded into the scope's RAM and the scope disconnects and automatically connects to USB, but this time (with FW in RAM) as USB vendor / product ID 04B5/6022.
For Windows it looks like two different devices, both (with/without FW) use libusb for USB communication and therefore both must be handled by zadig - 1st time 04B4/6022, 2nd time 04B5/6022.
Read more.

@seraphie21
Copy link
Author

seraphie21 commented Nov 27, 2019

hey, i've already tried that, and i just read raxis13's success report, and apparently it just work with the build 68, but for the newer version it always failed, so yeah, thank you for your help and time, hopefully there's a new build for window and support for x100 probe,, thank you so much 😄 😄 😄

@Ho-Ro
Copy link
Member

Ho-Ro commented Dec 5, 2019

@seraphie21
Please close here as nobody will fix it for openhantek right now. Your concern is handled by this issue:
Hang/crash at device detection when OS != Linux (Was: Cant Install windows pre-built version) #38

@seraphie21
Copy link
Author

@Ho-Ro okay, i'll close this, thanks for the help :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants