[Nut-upsuser] Windows usbhid-ups driver
jeff.bowman at intexx.com
Fri Dec 9 19:44:47 UTC 2016
I had a similar problem getting NUT to run on my Hyper-V 2012 R2 machine.
You may want to read through this thread:
The ultimate solution (in my case at least) is here:
Note that you'll probably want to dig around and find the official download location(s) for LIBEAY32 and SSLEAY32. I'm certain the place I found isn't it.
Keep in mind that I'm far from knowledgeable on NUT-my expertise begins and ends with this thread. And as you can see<http://lists.alioth.debian.org/pipermail/nut-upsuser/2016-September/thread.html>, it took me a week of near-constant fiddling to get it to work. Hopefully my pain can save you some.
From: Nut-upsuser [mailto:nut-upsuser-bounces+jeff.bowman=intexx.com at lists.alioth.debian.org] On Behalf Of Fairfax, Charles A.
Sent: Friday, December 9, 2016 8:31 AM
To: nut-upsuser at lists.alioth.debian.org
Subject: [Nut-upsuser] Windows usbhid-ups driver
I'm having trouble with the usbhid-ups driver and Windows. NUT won't connect to an APC SmartUPS 3000 via USB.
I've had good success with NUT and Raspbian as well as NUT and Windows using the tripplitesu driver.
The current system is:
Windows 7 Enterprise 64 bit
NUT 2.6.5-6 installed from MSI installer downloaded from networkupstools.org
libusb-win32-bin-126.96.36.199 installed and appears to work.
APC Smart-UPS 3000 RM XL FW:691.19.D USB FW:7.4 is listed under libusb-win32 devices in device manager.
testlibusb-win also returns this info along with manufacturer, serial number, bus/device.
driver = usbhid-ups
port = auto
# vendorid = 051D
desc = "UPS-0031"
When I try to run UPSDRVCTL this is what I get:
C:\Program 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 question to ask? I'm hoping someone has done this and can point me in the right direction.
I could just buy a Raspberry Pi for this but the Windows box is right there and I feel like I must be close to getting this figured out.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Nut-upsuser