search for: intexx

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

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, then return...

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....

> On Thu, 8 Sep 2016, Jeff Bowman wrote: > > > (Note: running > > 'upsc ups at localhost' echoes only a blank line to the screen, as do > > both 'upsmon' and 'upsd.') > > Something is wrong here. Is the daemon upsd running? On a Unix/Linux > system, the command ps aux | grep ups gives the report > > upsd 3196 0.0 0.0 13228

> 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- >

> 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 > driver...

I'm facing a looming deadline for getting this working, so I'm hoping someone experienced can weigh in on this. I'm getting errors in the Event Log when stopping the service: 1. Error stopping upsd (2) 2. Error stopping upsmon (2) Is there a detailed log somewhere? How can I track this down and find out what they mean? Or does someone know? Also, these three commands result in

I'm facing a looming deadline for getting this working, so I'm hoping someone experienced can weigh in on this. I'm getting errors in the Event Log when stopping the service: 1. Error stopping upsd (2) 2. Error stopping upsmon (2) Is there a detailed log somewhere? How can I track this down and find out what they mean? Or does someone know? Also, these three commands result in

I learned earlier from Roger Price's excellent explanation that a proper configuration includes sending a 'delayed shutdown' signal to the UPS hardware prior to shutting down the server. How is this accomplished? Does the USB driver handle this for us or must we do something additional? Thanks, Jeff Bowman Fairbanks, Alaska

Is the CGI feature available under the Windows build? If so, how to configure and access it? Thanks, Jeff Bowman Fairbanks, Alaska -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20160915/f5cc1e06/attachment-0001.html>

> > 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). This is very good news. Thank you for the clarification. > > It doesn't display the UPS model as indicated on p.21 in the PDF documentation: > > Unfortunately, the text on that page (from NUT 2.4.1) does

I'm trying to better understand OffDelay and OnDelay: http://networkupstools.org/docs/man/usbhid-ups.html#_extra_arguments My server requires ~3? minutes to shut itself down. Considering this I'm comfortable setting OffDelay to 300 (five minutes). 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

> > 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'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

Thank you VERY much, Roger, for your detailed explanations. I'm going to choose to heed your warning. > On Thu, 8 Sep 2016, Jeff Bowman wrote: > > > 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.? The