search for: libusb0

...375 Quick update... 0.234375 upsdrv_updateinfo... 0.500000 Got 0 HID objects... 0.500000 Quick update... 0.500000 upsdrv_updateinfo... (... above repeated during normal operation - varying HID object count ...) (*** I pulled the cable here ***) 4.984375 libusb_get_interrupt: libusb0-dll:err [_usb_reap_async] reaping request failed, win error: A device attached to the system is not functioning. 4.984375 Got 0 HID objects... 4.984375 Quick update... 4.984375 upsdrv_updateinfo... 5.234375 Got 0 HID objects... 5.234375 Quick update... 5.250000 upsdrv_updateinfo.....

...uld I check to fix ACCESS-DENIED error? 2. UPSHID-UPS fails with output: Network UPS Tools - Generic HID driver 0.37 (2.6.5-3691:3709M) USB communication driver 0.31 0.000000 debug level is '3' 0.000000 upsdrv_initups... 0.031200 Checking device (051D/0002) (bus-0/\\.\libusb0-0001--0x051d-0x0002) 0.109200 - VendorID: 051d 0.109200 - ProductID: 0002 0.109200 - Manufacturer: American Power Conversion 0.124800 - Product: Back-UPS ES 525 FW:851.t3.I USB FW:t3 0.124800 - Serial Number: 8B0745R23575 0.140400 - Bus: bus-0 0.140400...

Good evening, Hoping someone can point me in the right direction.. I downloaded and installed the 2.6.5-6 Windows MSI and it installed fine, although I nee to also get a libusb0.dll. Connected USB to a Triplite, I could go to the Devices and Printers and see the USB installed. But no matter what I did I could not get nut to work. I tried various commands, and got various errors. my config has -- [myups1] driver = usbhid-ups port = auto ven...

...on that they can upload and update the Project site ? Looking for Windows 7 / Windows 8, not running Windows 10 on any of my tool Laptops and I need to check some battery packs and overall status on a series of UPS units in shelters, The build 2.6.5.6 gives my grirf in a number of areas including libusb0.dll http://networkupstools.org/download.html TIA --- -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20170813/2478751a/attachment.html>

Hi I have installed nut 2.6.5-6 using the msi installer, but during the install popped up a box asking me to manually install libusb0.dll The msi package doesn't seem to contain the libusb0.dll, the question is, where do I get it from? Thx -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20160719/e8e4a3b5/attachment.html>

...<EF4B5804A5BD494E8327526D5D261C819ED75531 at CWVM02.cashwaggner.local > > > Content-Type: text/plain; charset="us-ascii" > > Hi > > I have installed nut 2.6.5-6 using the msi installer, but during the > install popped up a box asking me to manually install libusb0.dll > The msi package doesn't seem to contain the libusb0.dll, the question is, > where do I get it from? > > Thx > > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20160720/3...

Windows 7 Pro x64 Tripp-lite SMART1050SLT (USBHID) NUT 2.6.4-5 Driver is malfunctioning if the UPS goes on-battery (quick test or otherwise). usbhid-ups - libusb_get_report: libusb0-dll:err [control_msg] sending control message failed, win error: A device attached to the system is not functioning. (from event log) libusb_get_interrupt: libusb0-dll:err [_usb_reap_async] reaping request failed, win error: A device attached to the system is not functioning. 5D log attached....

...then > > shut itself down, thereby allowing the server enough time to safely > > shut itself down as well? > > Yes. Very good, thank you. > The command is "upsdrvctl shutdown". That's what I thought, but I get this: Can't claim USB device [051d:0003]: libusb0-dll:err [claim_interface] could not claim interface 0, win error: The requested resource is in use. Driver failed to start (exit status=1) I don't know why it thinks I'm trying to start the driver. > The 300 seconds start when the effect of "upsdrvctl shutdown" reaches...

...the absence of the discovery/announcement of the UPS model under 'upsdrvctl start' as previously discussed, I'm still not 100% confident it's working correctly. In fact I'm sure it's not: C:\Users\Admin>usbhid-ups.exe -a ups -DD ... 0.063421 libusb_get_report: libusb0-dll:err [control_msg] sending control message failed, win error: A device attached to the system is not functioning. 0.063421 Can't retrieve Report 89: Input/output error [A device attached to the system is not functioning. ] 0.063421 Path: UPS.ff8600fd, Type: Input, ReportID: 0x89, Offse...

...the driver code. Someone must have changed it from a printf() to a debug log statement. Noted: https://github.com/networkupstools/nut/issues/316 > In fact I'm sure it's not: > > C:\Users\Admin>usbhid-ups.exe -a ups -DD > > ... > > 0.063421 libusb_get_report: libusb0-dll:err [control_msg] sending control message failed, win error: A device attached to the system is not functioning. > 0.063421 Can't retrieve Report 89: Input/output error [A device attached to the system is not functioning. ] > 0.063421 Path: UPS.ff8600fd, Type: Input, ReportID: 0x8...

...sume at least an intermediate level of understanding; thus it's still quite a bit over my head. Your patience and slow explanations are appreciated. I presently have four issues: 1. CLI error: I get an error when running 'upsdrvctl start': "Can't claim USB device [051d:0003]: libusb0-dll:err [claim_interface] could not claim interface 0, win error: The requested resource is in use." 2. Event log errors: As noted the service starts fine, but I'm getting these two errors on service stop--"Error stopping upsd (2)" and "Error stopping upsmon (2)." 3. I...

?Hello, There is a new intermediate Windows binaries release available at : http://www.networkupstools.org/package/windows/NUT-Installer-2.6.5-2.msi This fixes three regressions: - upssched was not working - Event logging was not working (unless for NUT service binary itself) - usbhid-ups was not working with Back-UPS ES ups. Feedback is highly appreciated. Regards, Fred -- Eaton

...02" product = "Back-UPS ES 700 FW:829.D2 .I USB FW:D2 " serial = "5B0811T33088 " vendor = "APC" bus = "bus-0" First of all, this version does not work properly with the device, usbhid-ups returns "libusb_get_report: libusb0-dll:err [control_msg] sending control message failed, win error: A device attached to the system is not functioning" (apc_bu_es700_usbhid_ups.txt). I decided that the problem is related to the tweak for ES 525 model and I rebuilt NUT with TWEAK_BACK_UPS_ES define that was equal to "Back...

...gram Files (x86)\NUT\bin>upsdrvctl -D start Network UPS Tools - UPS driver controller Windows-v2.6.5-5-7-g72f380c 0.000000 Starting UPS: UPS-0031 Network UPS Tools - Generic HID driver 0.38 (Windows-v2.6.5-5-7-g72f380c) USB communication driver 0.32 Can't claim USB device [051d:0002]: libusb0-dll:err [claim_interface] could not claim interface 0, win error: The requested resource is in use. 0.087000 Driver failed to start (exit status=1) If the problem is that interface 0 is in use is there a way to direct the NUT driver to claim a different interface? Is that even the right q...

...pecs in ups.conf caused error: "GenerateConsoleCtrlEvent error : 87". Issuing usbhid-ups -a ups1 or usbhid-ups -a ups2 works, but 1. exclusively - I can see only one UPS at a time (trying to run second ups while the first is running gives: "Can't claim USB device [051d:0003]: libusb0-dll:err [claim_interface] could not claim interface 0, win error: The requested resource is in use) 2. randomly - This means that no matter what I put into ups.conf NUT will pick anything that responds first. which eventually is useless. Thus my question is whether it is an error of usblib or N...

...following: C:\Program Files (x86)\NUT\bin>usbhid-ups.exe -a xs1500 -DD Network UPS Tools - Generic HID driver 0.37 (2.6.5-3723:3731M) USB communication driver 0.31 0.000000 debug level is '2' 0.000000 upsdrv_initups... 0.000000 Checking device (051D/0002) (bus-0/\\.\libusb0-0001--0x051d-0x0002) 0.015628 - VendorID: 051d 0.015628 - ProductID: 0002 0.031251 - Manufacturer: American Power Conversion 0.031251 - Product: Back-UPS BX1500G FW:866.L5 .D USB FW:L5 0.031251 - Serial Number: 3B1045X04728 0.046933 - Bus: bus-0 0.046933...

...at localhost Only a blank line echoes to the screen, presumable because the other *usb* processes aren't running. Note that when I run upsdrvctl start as indicated on pp21 of the NUT User Manual (PDF), I get the conflict error I described earlier: Can't claim USB device [051d:0003]: libusb0-dll:err [claim_interface] could not claim interface 0, win error: The requested resource is in use. Driver failed to start (exit status=1) Running the .MSI setup on Windows results in a service (daemon) being created, one that starts and maintains an executable named NUT.exe. I'm not...

...Offset: 11, Size: 1, Value: 0 0.076421 Path: UPS.PowerSummary.PresentStatus.ff860080, Type: Input, ReportID: 0x07, Offset: 12, Size: 1, Value: 0 0.076421 Path: UPS.PowerSummary.PresentStatus.ff860080, Type: Feature, ReportID: 0x07, Offset: 12, Size: 1, Value: 0 0.076421 libusb_get_report: libusb0-dll:err [control_msg] sending control message failed, win error: A device attached to the system is not functioning. 0.076421 Can't retrieve Report 89: Input/output error [A device attached to the system is not functioning. ] 0.076421 Path: UPS.ff8600fd, Type: Input, ReportID: 0x89, Of...

...that there is more than the regularly mentioned "interface >> number" to juggle here. >> >> So if you manage to reliably pinpoint which interface concept applies >> where, and add configurability to that with `addvar()` in >> `drivers/libusb1.c` (and `drivers/libusb0.c` if applicable/possible there) >> and `docs/man/nut_usb_addvars.txt` -- so this change applies consistently >> to all USB-aware drivers, and if it all works - that would be a welcome >> improvement :D >> >> Jim >> >> >> On Sun, Nov 5, 2023 at 11:29?...

Hello. I've tried to configure Windows (complete port, Beta): Windows MSI installer 2.6.0-1 with my Powerware 5115 connected via USB port but have no luck. Here is my config files: *nut.conf:* MODE = netserver *ups.conf:* [PW5115] driver = bcmxcp_usb port = notUsed desc = "PowerWare 5115" *upsd.conf:* LISTEN 192.168.1.12 3493 *upsd.users:* [monuser]