hidapi

hidapi copied to clipboard

What does it mean when a computer shows winusb instead of hidusb? I have users that have winusb and my application does not work. My application is using the hidapi.dll to send data but with a system that has winusb installed, that is not going to work? I package the hidapi.dll with my application so I would assume that it uses that but maybe the system is using winusb and somehow messing things up?

Is winusb now able to communicate with HID devices? Last I was aware, it was not.

I think that is the point of this project https://github.com/madwizard-thomas/winusbnet/tree/master/WinUSBNet but there is also this http://janaxelson.com/winusb.htm

I wondering if I choose the option to build the dll in to the application if this will fix it? I currently leave it outside.

winusb, as far as I know, will not open HID devices, even though HID devices are USB. It blocks the opening of HID devices.

This was the case last I looked.

I wonder why winusb is causing issue with this project then? It definitely opens the device but communication is all bugged. Maybe hidapp.dll is opening it but winusb is communicating? So your project has a option to build whit hiapi.dll, ill try that.

If your application uses HIDAPI and the user's device is not using the HID driver (not HID device), then of course your application will not work. How can you open the device if the driver is WinUSB?