search for: ff860080

...on fault. Here is a sample of the last bit of output from "/usr/local/ups/bin/newhidups -u nut -DDD /dev/hiddev0" (nothing about the process death is in syslog): ================= Object: UPS.PresentStatus.VoltageNotRegulated = 0 entering path_to_string() Looking up 00840002 Looking up ff860080 Object: UPS.PresentStatus.ff860080 = 0 entering path_to_string() Looking up 00840002 Object: UPS.PresentStatus. = 0 entering path_to_string() Looking up 00840002 Object: UPS.PresentStatus. = 0 entering path_to_string() Looking up 00840002 Object: UPS.PresentStatus. = 0 =>Got 16 HID Objects... O...

Hello, I'm using the stable amd64 port of Debian Linux. I installed (the latest) nut-2.0.1-4 and nut-usb packages for utilizing an APC Smart-UPS 1500 USB. I tried "apcupsd" first but "nut" makes an even more sophisticated impression on me and has more security options. I had problems with the newhidups driver. It didn't find a device with matching VendorID. And

...; > 0.000000 > > Path: UPS.PowerSummary.PresentStatus.VoltageNotRegulated, Type: > > Input, > > Value: 0.000000 > > Path: UPS.PowerSummary.PresentStatus.VoltageNotRegulated, Type: > > Feature, > > Value: 0.000000 > > Path: UPS.PowerSummary.PresentStatus.ff860080, Type: Input, Value: > > 0.000000 > > Path: UPS.PowerSummary.PresentStatus.ff860080, Type: Feature, Value: > > 0.000000 > > Path: UPS.PowerSummary.PresentStatus., Type: Input > > Path: UPS.PowerSummary.PresentStatus., Type: Input > > Path: UPS.PowerSummary.Presen...

Peter Selinger wrote: > Hm. I need more information, as NUT seems to garble the values even > before I can see them. I am not so worried about the date and > temperatures (although, strangely, the battery replacement date > appears to be Sept 25, 2001, which makes no sense). But the voltage is > definitely important. > > [...] > Thanks Peter - I'll send the new

...driver 0.31 Using subdriver: APC HID 0.95 libusb_get_report: Unknown error Can't initialize data from HID UPS Driver failed to start (exit status=1) /usr/local/etc/rc.d/nut: WARNING: failed precmd routine for nut 1.115408 Report[buf]: (3 bytes) => 33 0c 00 1.115423 Path: UPS.PresentStatus.ff860080, Type: Input, ReportID: 0x33, Offset: 12, Size: 1, Value: 0 1.115430 Report[buf]: (3 bytes) => 33 0c 00 1.115438 Path: UPS.PresentStatus.ff860080, Type: Feature, ReportID: 0x33, Offset: 12, Size: 1, Value: 0 1.118990 Report[get]: (3 bytes) => 60 00 00 1.119025 Path: UPS.ff860001.ff860023,...

Hello I recently switched from apcupsd to NUT2.2.2 without any troubles. I tried to figure out how I can configure the self-test intervall. The command upsrw lists only the variables battery.charge.low battery.runtime.low ups.delay.shutdown ups.delay.start The command usbhid-ups -D and the listing under http://obsvermes.org/cgi-bin/nut/upsstats.cgi?host=apcsmart at localhost&treemode

..., Size: 1, Value: 0 0.944796 Report[buf]: (3 bytes) => 07 8c 00 0.944803 Path: UPS.PowerSummary.PresentStatus.VoltageNotRegulated, Type: Feature, ReportID: 0x07, Offset: 11, Size: 1, Value: 0 0.944808 Report[buf]: (3 bytes) => 07 8c 00 0.944851 Path: UPS.PowerSummary.PresentStatus.ff860080, Type: Input, ReportID: 0x07, Offset: 12, Size: 1, Value: 0 0.944856 Report[buf]: (3 bytes) => 07 8c 00 0.944863 Path: UPS.PowerSummary.PresentStatus.ff860080, Type: Feature, ReportID: 0x07, Offset: 12, Size: 1, Value: 0 0.950479 Report[get]: (2 bytes) => 16 06 0.950501 Path: UPS....

On Jan 8, 2015, at 11:43 PM, Graham Menhennitt <graham at menhennitt.com.au> wrote: > Hello Nutters, > > I'm running nut 2.7.2 on FreeBSD 10-stable (via the FreeBSD port) with an APC Back-UPS CS 350 connected via USB. I get persistent (every few minutes) messages logged "battery is low" but I don't understand why. I don't think it's for the reason

...876 Path: UPS.PowerSummary.PresentStatus.Overload, Type: Input, ReportID: 0x07, Offset: 10, Size: 1, Value: 0 775.643970 Path: UPS.PowerSummary.PresentStatus.VoltageNotRegulated, Type: Input, ReportID: 0x07, Offset: 11, Size: 1, Value: 0 775.644027 Path: UPS.PowerSummary.PresentStatus.ff860080, Type: Input, ReportID: 0x07, Offset: 12, Size: 1, Value: 0 775.644114 Quick update... 775.653814 Path: UPS.PowerSummary.DelayBeforeShutdown, Type: Feature, ReportID: 0x12, Offset: 0, Size: 16, Value: -1 775.664837 Path: UPS.PowerSummary.DelayBeforeReboot, Type: Feature, ReportID: 0x...

I've acquired and installed NUT 2.4.1 on a D-Link DNS323 NAS. With exception of Load and Battery Temp readings all works well. A upsc ups at localhost command returns; battery.charge: 100 battery.charge.low: 10 battery.charge.warning: 50 battery.date: 2001/09/25 battery.mfr.date: 2008/06/05 battery.runtime: 2122 battery.runtime.low: 120 battery.temperature: 3022999999999998800 battery.type:

Hello Nutters, I'm running nut 2.7.2 on FreeBSD 10-stable (via the FreeBSD port) with an APC Back-UPS CS 350 connected via USB. I get persistent (every few minutes) messages logged "battery is low" but I don't understand why. I don't think it's for the reason described in the FAQ (but I'm not 100% sure). In the trace output I can see that

....PowerSummary.PresentStatus.VoltageNotRegulated, Type: Feature, ReportID: 0x07, Offset: 11, Size: 1 0.105218 libusb_get_report: error sending control message: Protocol error 0.105323 Can't retrieve Report 07: Protocol error 0.105425 Path: UPS.PowerSummary.PresentStatus.ff860080, Type: Input, ReportID: 0x07, Offset: 12, Size: 1 0.106218 libusb_get_report: error sending control message: Protocol error 0.106324 Can't retrieve Report 07: Protocol error 0.106438 Path: UPS.PowerSummary.PresentStatus.ff860080, Type: Feature, ReportID: 0x07, Offset:...

> 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

...21 Path: UPS.PowerSummary.PresentStatus.VoltageNotRegulated, Type: Input, ReportID: 0x07, Offset: 11, Size: 1, Value: 0 0.076421 Path: UPS.PowerSummary.PresentStatus.VoltageNotRegulated, Type: Feature, ReportID: 0x07, 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 attach...