search for: shutdownrequest

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

...: 1.000000 > > Path: UPS.PowerSummary.PresentStatus.BelowRemainingCapacityLimit, > Type: > > Input, Value: 0.000000 > > Path: UPS.PowerSummary.PresentStatus.BelowRemainingCapacityLimit, > Type: > > Feature, Value: 0.000000 > > Path: UPS.PowerSummary.PresentStatus.ShutdownRequested, Type: Input, > > Value: 0.000000 > > Path: UPS.PowerSummary.PresentStatus.ShutdownRequested, Type: > > Feature, > > Value: 0.000000 > > Path: UPS.PowerSummary.PresentStatus.ShutdownImminent, Type: Input, > > Value: 0.000000 > > Path: UPS.PowerSummary.Pr...

Charles, to your specific points : > The other HID drivers seem to trigger shutdown by writing to the various timers (e.g. UPS.PowerSummary.DelayBeforeReboot). Your firmware seems to have UPS.PowerSummary.PresentStatus.ShutdownRequested, which according to the HID PDC spec, is read/write. I wonder if the firmware responds to this? So are you suggesting if I modify openups-hid.c to include this specific command as an instant command, it may respond? I could give it a try if you confirm that?s what you mean. > Out of curiosit...

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

...any HU_TYPE_CMD entries in openups-hid.c. I latched on to the other error you mentioned (about claiming the device). The other HID drivers seem to trigger shutdown by writing to the various timers (e.g. UPS.PowerSummary.DelayBeforeReboot). Your firmware seems to have UPS.PowerSummary.PresentStatus.ShutdownRequested, which according to the HID PDC spec, is read/write. I wonder if the firmware responds to this? > Also from the trace I sent you, it appears that after the ?RunTimeToEmpty? query, the interface tries to read a Report b1 of size 248 which results in a broken pipe. Is that correct and what woul...

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

...UPS.PowerSummary.PresentStatus.VoltageNotRegulated, Type: Input, ReportID: 0x0a, Offset: 7, Size: 1, Value: 0 0.130647 Path: UPS.PowerSummary.PresentStatus.VoltageNotRegulated, Type: Feature, ReportID: 0x0a, Offset: 7, Size: 1, Value: 0 0.130652 Path: UPS.PowerSummary.PresentStatus.ShutdownRequested, Type: Input, ReportID: 0x0a, Offset: 8, Size: 1, Value: 0 0.130657 Path: UPS.PowerSummary.PresentStatus.ShutdownRequested, Type: Feature, ReportID: 0x0a, Offset: 8, Size: 1, Value: 0 0.130663 Path: UPS.PowerSummary.PresentStatus.ShutdownImminent, Type: Input, ReportID: 0x0a, Off...

...t output that was not particularly useful, and I'm not sure where to go from here. Here is all the output: driver.name: newhidups driver.parameter.port: auto driver.parameter.vendorid: 0d9f driver.version: 2.0.5-pre1 ups.delay.shutdown: 0 ups.delay.start: 0 ups.mfr: Powercom UPS.PowerConverter.ShutdownRequested: 2 ups.serial: ups.test.result: Done and passed Here is the source file: /* powercom-hid.c - subdriver to monitor Powercom USB/HID devices with NUT * * Copyright (C) * 2003 - 2005 Arnaud Quette <arnaud.quette@free.fr> * 2005 - 2006 Peter Selinger <selinger@users.sourceforge.net...

...1, Value: 0 0.944627 Report[buf]: (3 bytes) => 07 8c 00 0.944633 Path: UPS.PowerSummary.PresentStatus.BelowRemainingCapacityLimit, Type: Feature, ReportID: 0x07, Offset: 4, Size: 1, Value: 0 0.944639 Report[buf]: (3 bytes) => 07 8c 00 0.944645 Path: UPS.PowerSummary.PresentStatus.ShutdownRequested, Type: Input, ReportID: 0x07, Offset: 5, Size: 1, Value: 0 0.944651 Report[buf]: (3 bytes) => 07 8c 00 0.944657 Path: UPS.PowerSummary.PresentStatus.ShutdownRequested, Type: Feature, ReportID: 0x07, Offset: 5, Size: 1, Value: 0 0.944662 Report[buf]: (3 bytes) => 07 8c 00 0.94466...

...0 0.336559 Path: UPS.PowerSummary.PresentStatus.OverCharged, Type: Feature, ReportID: 0x40, Offset: 4, Size: 1, Value: 0 0.336571 Path: UPS.PowerSummary.PresentStatus.OverTemperature, Type: Feature, ReportID: 0x40, Offset: 5, Size: 1, Value: 0 0.336583 Path: UPS.PowerSummary.PresentStatus.ShutdownRequested, Type: Feature, ReportID: 0x40, Offset: 6, Size: 1, Value: 0 0.336595 Path: UPS.PowerSummary.PresentStatus.ShutdownImminent, Type: Feature, ReportID: 0x40, Offset: 7, Size: 1, Value: 0 0.336608 Path: UPS.PowerSummary.PresentStatus.BelowRemainingCapacityLimit, Type: Feature, ReportID: 0x40,...

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

...: UPS.PowerSummary.PresentStatus.BatteryPresent, Type: Input, ReportID: 0x07, Offset: 3, Size: 1, Value: 1 775.643467 Path: UPS.PowerSummary.PresentStatus.BelowRemainingCapacityLimit, Type: Input, ReportID: 0x07, Offset: 4, Size: 1, Value: 0 775.643504 Path: UPS.PowerSummary.PresentStatus.ShutdownRequested, Type: Input, ReportID: 0x07, Offset: 5, Size: 1, Value: 0 775.643539 Path: UPS.PowerSummary.PresentStatus.ShutdownImminent, Type: Input, ReportID: 0x07, Offset: 6, Size: 1, Value: 0 775.643576 Path: UPS.PowerSummary.PresentStatus.RemainingTimeLimitExpired, Type: Input, ReportID: 0x07,...

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

...ummary.PresentStatus.BelowRemainingCapacityLimit, Type: Feature, ReportID: 0x07, Offset: 4, Size: 1 0.091221 libusb_get_report: error sending control message: Protocol error 0.091325 Can't retrieve Report 07: Protocol error 0.091427 Path: UPS.PowerSummary.PresentStatus.ShutdownRequested, Type: Input, ReportID: 0x07, Offset: 5, Size: 1 0.092220 libusb_get_report: error sending control message: Protocol error 0.092326 Can't retrieve Report 07: Protocol error 0.092441 Path: UPS.PowerSummary.PresentStatus.ShutdownRequested, Type: Feature, ReportID: 0x0...

> 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

...owerSummary.PresentStatus.BelowRemainingCapacityLimit, Type: Input, ReportID: 0x07, Offset: 4, Size: 1, Value: 0 0.076421 Path: UPS.PowerSummary.PresentStatus.BelowRemainingCapacityLimit, Type: Feature, ReportID: 0x07, Offset: 4, Size: 1, Value: 0 0.076421 Path: UPS.PowerSummary.PresentStatus.ShutdownRequested, Type: Input, ReportID: 0x07, Offset: 5, Size: 1, Value: 0 0.076421 Path: UPS.PowerSummary.PresentStatus.ShutdownRequested, Type: Feature, ReportID: 0x07, Offset: 5, Size: 1, Value: 0 0.076421 Path: UPS.PowerSummary.PresentStatus.ShutdownImminent, Type: Input, ReportID: 0x07, Offset: 6, Siz...

Charles, Did you get chance to look at the data I sent you, please? I?ve done some more work myself and the conclusion I?ve reached is that if the minibus OpenUPS doesn?t support instant commands, then sending ?upsdrvctl shutdown? won?t ever work, as it would need to send instant commands! Also from the trace I sent you, it appears that after the ?RunTimeToEmpty? query, the interface tries to

Charles, Thanks again for your help, and sorry I didn?t :cc - noted for the future! I?m suspicious that the OpenUPS doesn?t behave properly in a number of ways, of which the USB traffic is the one of immediate concern. It seems to me that NUT can read from it but probably not write to it: and the OpenUPS doesn?t flag ?low battery? conditions correctly either. It does shut itself down at a