similar to: Nut-upsuser Digest, Vol 133, Issue 8

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.

On Jul 14, 2016, at 7:34 AM, Jeff Silberberg <jms at compudesigns.net> wrote: > > >> On Wed, Jul 13, 2016 at 11:28 PM, Charles Lepple <clepple at gmail.com> wrote: >> It sounds like the UPS is connected. Since you mentioned libusb0.dll, make sure that the UPS is not being recognized as a regular HID UPS (instead, it should be claimed by libusb) >> >>

Looking at the project site the latest Windows Binary is a few back - 2.6.5.6 Has any one built a more recent version 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

On Aug 13, 2017, at 10:29 PM, Jeff Silberberg <jms at dapage.net> wrote: > Looking at the project site the latest Windows Binary is a few back - 2.6.5.6 > > Has any one built a more recent version 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

I was doing some testing with the 2.6.0-1 beta Windows installer and a Cyber Power CP1350PFCLCD UPS, and ran into an infinite loop in the usbhid-ups driver if the UPS is lost on the UPS bus. This is on a Windows XP SP3 system. USB device access is via libusb 1.2.4.0 (driver mode, not filter) in case that matters. Everything seems to work just fine so far while the UPS is connected (so kudos,

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

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:

On Sep 14, 2016, at 9:29 AM, Jeff Bowman <jeff.bowman at intexx.com> wrote: > C:\Users\Admin>upsc ups at localhost > battery.charge: 100 ... > ups.status: OL If ups.status follows the state of line power, the driver is working (and upsc talks to upsd, so that connection is working as well). > So this all represents significant progress. But we're not out of the woods

Hello! I tried NUT 2.6.5-1 (Windows port) with my APC Back UPS ES. It seems I have configured NUT properly, nut-scanner found my UPS: [nutdev1] driver = "usbhid-ups" port = "auto" vendorid = "051D" productid = "0002" product = "Back-UPS ES 525 FW:851.t3.I USB FW:t3" serial = "8B0745R23575

> I suspect you will want the newer version for production (there was some > issue regarding the popups when certain events happen), but let's get this > version working first before changing another variable. Appreciate that. Agreed. > For reference, I think the source code to NUT.exe is here: > https://github.com/networkupstools/nut/blob/Windows-v2.6.5- >

I've been able to get the latest Windows port installed on my Hyper-V 2012 R2 instance and start the service. But as I'm an absolute beginner I'm not sure how to proceed further. I've browsed the archives, but discussions here tend to assume at least an intermediate level of understanding; thus it's still quite a bit over my head. Your patience and slow explanations are

Hello! I have tested APC Back UPS ES 700 and NUT 2.6.5-3 a few days ago and I have got some news. This device is detected by nut-scanner as: [nutdev1] driver = "usbhid-ups" port = "auto" vendorid = "051D" productid = "0002" product = "Back-UPS ES 700 FW:829.D2 .I USB FW:D2 " serial =

> > How does this work in conjunction with the UPS hardware? Does NUT > > immediately send a command to the UPS to wait for 300 seconds and 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

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-1.2.6.0 installed and

Hi, I've got a question about managing two UPSes under NUT. I have two similar model APC usb-connected UPSes to work with, but don't know how to manage them simultaneously from under Windows. Long story short, my ups.conf looks like this: --- ups.conf --- [ups1] driver= usbhid-ups port= auto serial=AS1054340323 [ups2] driver= usbhid-ups port= auto serial=AS1026662626 ---

Windows 7 x64 NUT 2.6.5-4 Eaton 5PX1500RT Using explore did not yield any additional output. This UPS is on the compatibility list, so hopefully not a big deal. I double-checked that the 3S still works with the same USB cable. I'll check mge-shut over serial next. Regards. -------------- next part -------------- Network UPS Tools - Generic HID driver 0.37 (2.6.5-3780M) USB communication

Hello, windows10pro version 1511 os build 10586.29 nut 2.6.5-6 windows binary package device ups: poweron vs 950 when I do testing shutdown it does not shutdown. Thank's. driver debug output: C:\Program Files (x86)\NUT\bin>blazer_usb -DD -a myups Network UPS Tools - Megatec/Q1 protocol USB driver 0.10 (Windows-v2.6.5-5-7-g72f380c) 0.000000 debug level is '2' 0.000000

On Oct 5, 2016, at 10:59 PM, Jeff Bowman wrote: > >> 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

On 10/5/2016 10:59 PM, Jeff Bowman wrote: > >>> How does this work in conjunction with the UPS hardware? Does NUT >>> immediately send a command to the UPS to wait for 300 seconds and then >>> shut itself down, thereby allowing the server enough time to safely >>> shut itself down as well? >> >> Yes. > > Very good, thank you. > >

> On Sep 11, 2016, at 3:37 PM, Jeff Bowman <jeff.bowman at intexx.com> wrote: > > > > Using subdriver: APC HID 0.95 > > > > ...and then hangs for 45 seconds before returning to a command prompt. No > UPS hardware information is printed. > > It can take about that long to read the descriptors. The non-Windows NUT > drivers will print that message,