-
Notifications
You must be signed in to change notification settings - Fork 159
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
Communication failure windows 10 #103
Comments
It is very difficult for to follow your description and get the necessary info to help with your problem. Please be concise - all provided files have a name.
Which "Hantek driver"? Does it have a name? I do not provide a driver, the Windows port of my project OpenHantek6022 links the executable OpenHantek.exe with the dynamic library libusb-1.0.dll to communicate with the hardware. For Windows you have to enable the USB access as mentioned in the documentation. Did you follow these steps?
What happens?
What does "the Hantek software" mean - OpenHantek.exe? But then again, which "driver packaged with the program"? Martin |
My Zadig.log is quite long. I tried several times. Note I cleared it the first time, this is just what I did today. |
Michael, I see two times an entry for VID_04B5, PID_6022, REV_0000 - this could indicate that the (original supplied by) Hantek driver is still active and blocks OpenHantek. But I do not use Windows at all and cannot check it here.
The hardware of Hantek DSO-6022 mainly consists of a Cypress EzUSB chip, which - when switched on - reports VID/PID 04B4/6022 (these values are stored in the EEPROM). In normal operation OpenHantek claims this USB device and uploads my own firmware into RAM, that finally switches the scope device from VID 04B4 to 04B5, reporting VID_04B5, PID_6022, REV_0207. Please apply Zadig twice:
If you do not see the 1st VID/PID combination after plugging the original Hantek has probably grabbed it as soon you plug the device in - in this case please remove the Hantek driver! Martin |
No reaction for a week - either the problem is solved or Michael has lost interest. I'm closing for now, please reopen if you're still interested and new information is available. |
Describe the bug
Red blinky light when software opens, Upload Firmware: Operation not supported or unimplemented on the platform. Did Hantek brick your upload?
To Reproduce
IMPORTANT: Always unplug and replug the scope if used before with a different application, e.g. sigrok or the original Hantek software.
Yup, that was done. I can load the Hantek software, and it sorta works as much as that software does.
I tried the Hantek driver as downloaded. That didnt want to work at all. I then signed the driver myself and it allowed the Hantek software to work.
The driver I installed was the one packaged with the program.
Steps to reproduce the behavior:
Expected behavior
A clear and concise description of what you expected to happen.
Green blinky light and working software able to connect.
Screenshots
If applicable, add screenshots or a video to help explain your problem.
Computer environment (please complete the following information):
Scope device (please complete the following information):
The text was updated successfully, but these errors were encountered: