From: Xiaofan C. <xia...@gm...> - 2018-09-12 07:11:20
|
On Wed, Sep 12, 2018 at 3:05 PM Xiaofan Chen <xia...@gm...> wrote: > > On Wed, Sep 12, 2018 at 2:38 PM Dmitry Donskoy <ad...@da...> wrote: > > > > The thing is that before I install libusb-win32, Windows uses "HID UPS > > Battery", that works stable (doesn't disconnect and connect), though it > > doesn't work with NUT. > > > > I understand -- this means that the NUT program and the "HID UPS Battery" > application behaves differently and that probably affects the device to go > into some kind of fault and then can not handling the Windows request > properly. Still libusb-win32 itself can not help you -- it does not handling > the Windows enumeration. > > BTW, I think NUT program should be upgraded to use HIDAPI > instead of libusb-0.1 API or even libusb-1.0 API to be have better > support under Windows and Mac OS X. > You can try some software or HW USB analyzer to debug the issue to see why the device goes to fault. https://docs.microsoft.com/en-us/windows-hardware/drivers/usbcon/usb-event-tracing-for-windows libusb-win32 debug version may help a bit as well -- you need to use Microsoft DebugView to see the se debug printout to see the communication between NUT and the device. -- Xiaofan |