-
Notifications
You must be signed in to change notification settings - Fork 101
USB scale not working on Mac #180
Comments
I'm impressed you could claim the device... I'm getting this in an Apple OS X 10.11 VM:
Seems to be a duplicate of |
I initially received the Access Denied error as well. I'm not exactly sure how I got around this, as I did nothing besides basic troubleshooting such as restarting the browser and QZ Tray. I would like to note that I am receiving almost the exact error on Ubuntu 14.04 Ubuntu 14.04
|
It appears Apple fixed some of the USB issues with software updates and my VM is behind... Updating now... Possible upstream bug report libusb/libusb#96. |
More information about this bug... https://github.com/libusb/libusb/wiki/FAQ#How_can_I_run_libusb_applications_under_Mac_OS_X_if_there_is_already_a_kernel_extension_installed_for_the_device Edit: Kext signing request submitted to Apple. Follow-up: 636837176 |
I think I got it via 2.0...tresf:2.0 Note, until Apple approves my request for developer signing rights for kernel extensions (
Notes:
|
Can you you start in debug mode and tell is where the Also, despite that, can you still claim the device? |
I cannot claim the device. I get "Identifier cannot be empty."
|
@bberenz I'm going to need some help to fix the I've narrowed it down to the fact that this USB device on Mac for some reason has no "Active" configuration. The work-around for this was to setup a helper function to grab the active configuration and if public static UsbConfiguration getUsbConfiguration(UsbDevice device) throws UsbException {
UsbConfiguration config = device.getActiveUsbConfiguration();
if (config != null) {
return config;
}
for (Object o : device.getUsbConfigurations()) {
if (o != null) {
return (UsbConfiguration)o;
}
}
throw new UsbException("UsbConfiguration not found for vendorId/productId");
} However, a strict mandate of the USB library is to only allow the claiming of an active configuration. This means when we click My attempts to workaround this have all failed, but mostly due to my lack of understanding of the way this library works. The JSR says you can call public void open(byte ifc) throws UsbException {
- iface = device.getActiveUsbConfiguration().getUsbInterface(ifc);
+ iface = UsbUtilities.getUsbConfiguration(device).getUsbInterface(ifc);
+
+ // FIXME
+ // Sets the interface index, alternate settings index incase the interface isn't active
+ //if (!iface.isActive()) {
+ // StandardRequest.setInterface(device, ifc, (byte)0x00);
+ //}
+
iface.claim();
} Help appreciated. |
Turns out the New installer link has been provided as well. Note, this still suffers the Research on #180 (comment) suggests |
Still banging my head on this... Filed upstream bug report to ask for help.usb4java/usb4java#51 |
Low-level API didn't help at all. After re-reading some I signed up for the OS X beta program.... Installing now... |
Update: 10.11.4 still does NOT fix this issue. Edit filed an upstream bug report over at |
Well, I made every valiant attempt possible to no avail. Closing as The long history of trial and error is better documented with the Here's the last working kernel extension build if we ever have to go back on it... https://github.com/tresf/qz-print/commit/f70c1a5dc27526d7274542671c89a3e8e6ba9399 This feature will be added using official HID support when |
As a status update on this, We're unlikely to use it for claiming HID devices on Mac, but it's available in case we encounter hardware that requires it.
Update: HID support has been started in the |
Mac OS X El Capitan 10.11.3
Chrome, Firefox, and Safari
I am using a Stamps.com Model 510 that works successfully on Windows
I am able to Claim Device and Open Stream properly:
After Open Stream is selected, the Read Data screen is displayed, and no values are read off of the scale. Nothing is displayed in the console at this point.
When clicking "Read as Weight" the Raw data dialogue does not change and the below console errors are shown. This error indefinitely happens until Read as Raw is selected.
Chrome Console
Firefox Console
The text was updated successfully, but these errors were encountered: