Closed alexjoyner closed 1 year ago
Once the program loaded successfully, but only after several attempts
Then the USB access rights for the Hantek should be ok. Some Ideas that come to my mind:
OpenHantek --verbose 4
and report the output.Thanks @Ho-Ro!
So I was able to get the program running, but I'm not sure I would call this closed yet.
The app opened more consistently if I closed OpenHantek, then plugged in the USB and re-launched the program after everything was connected. This is opposed to what I was doing before which was running the program, then connecting the device and selecting it from the dropdown. However; I would still sometimes get the error listed before, and sometimes I would get this new error:
Here's a short video of the finickiness I would run into from closing and re-opening the program with the USB connected:
I tried this using several different cables and got the same results.
Also, a quick note if others run into this:
If this doesn't help try to start the program from a termial window with OpenHantek --verbose 4 and report the output.
For this to work, I think I would have to set up a path to OpenHantek because I get OpenHantek command not found
. For me it was easier to run: open -n ./OpenHantek.app --args --verbose 4
Note: I haven't run the open command from the terminal in a while and this might not have picked up the verbose arg because I got no output despite the program launching successfully
I propose to connect the device and then start the program - this is at least my typical use case. The FW upload is only needed once, successive program starts after closing the program just start with FW already in place.
There hasn't been any activity on this issue recently, and in order to prioritize active issues, it will be marked as stale. Please make sure to update to the latest version and check if that solves the issue. Let us know if that works for you by leaving a comment. Because this issue is marked as stale, it will be closed and locked in 7 days if no further activity occurs. Thank you for your contributions!
Hi! I just wanted to say that I also have the same problem. OpenHantek6022 worked flawlessly for me in February of this year. At that point I was on macOS 12.6 Monterrey.
I have since upgraded to macOS 13.3 Ventura, and now I have trouble connecting my Hantek6022BL via USB. Previously, the OpenHantek software recognized my oscilloscope immediately, even though it was plugged into my –admittedly overcrowded– Thunderbolt3 dock. Now I was only able to get a connection after rebooting my computer without any peripherals plugged in, and connecting directly to USB port (I still had to use a simple tiny USB-A to USB-C adapter since the MacbookPro doesn't come with any USB-A ports).
The red LED doesn't come on when I try to connect the oscilloscope except on one occasion when it was blinking. It still didn't connect though. The LED works when I put it in LA-mode and connect to PulseView.
Update 2023-05-22: After leaving my computer in sleep mode a few days (no reboots), it has worked 8 times in a row (and still counting), connected through my Thunderbolt dock. But I really can't understand why...
Describe the bug Trying to OpenHantek for a 6022BE model scope and got this error
Connection Failed! UploadFirmware: libusb_claim_interface() failed: LIB_USB_ERROR_NOT_FOUND
To Reproduce IMPORTANT: Always unplug and replug the scope if used before with a different application, e.g. sigrok or the original Hantek software. -> I have only used this with OpenHantek. Once the program loaded successfully, but only after several attempts No support for non-Linux related issues unless a volunteer steps in! -> Understood! I might try to fix this myself, but this would be my first issue in this repo, so any pointing in the right direction would be super helpful!
Steps to reproduce the behavior: This occurred during the startup screen, so all I did was load open Hantek, plug in the device, and select 6022BE
Expected behavior Successful program load
Screenshots
Computer environment (please complete the following information):
Scope device (please complete the following information):
Additional context Program just run from the applications folder