search for: shutdownimm

...cityMode, Type: Feature, Value: 2.000000 Path: UPS.PowerSummary.RemainingCapacity, Type: Input, Value: 83.000000 Path: UPS.PowerSummary.RemainingCapacity, Type: Feature, Value: 83.000000 Path: UPS.PowerSummary.FullChargeCapacity, Type: Feature, Value: 100.000000 Path: UPS.PowerSummary.PresentStatus.ShutdownImminent, Type: Input, Value: 0.000000 Can't find object UPS.PowerSummary.PresentStatus.TLACPresent Path: UPS.PowerSummary.PresentStatus.TLACPresent, Type: Input Can't find object UPS.PowerSummary.PresentStatus.TLCharging Path: UPS.PowerSummary.PresentStatus.TLCharging, Type: Input Can't fi...

On Jan 11, 2015, at 11:48 PM, Graham Menhennitt <graham at menhennitt.com.au> wrote: >> The file drivers/usbhid-ups.c is looking for any of the following conditions to declare LB: >> >> ? STATUS(LOWBATT) >> ? STATUS(TIMELIMITEXP) >> ? STATUS(SHUTDOWNIMM) >> >> The mapping to HID Path names will depend on the model, but STATUS(LOWBATT) can come from ...BelowRemainingCapacityLimit, which is 0 in both instances in your log. STATUS(TIMELIMITEXP) maps to ...RemainingTimeLimitExpired, which I don't see, and STATUS(SHUTDOWNIMM) would cau...

...to fail. Following are the logs: [root@xa000000 root]# newhidups -a ups_on_usb -DD <...> Time range from 15mn to 6 hours, depending... upsdrv_updateinfo... Waiting for notifications... process_status_info: online process_status_info: !dischrg process_status_info: chrg process_status_info: !shutdownimm process_status_info: !lowbatt upsdrv_updateinfo... Waiting for notifications... process_status_info: online process_status_info: !dischrg process_status_info: chrg process_status_info: !shutdownimm Can't retrieve Report 1 (-32/32): Broken pipe ==================================================...

...u_find_infoval: searching for value =3D 0 > > > > hu_find_infoval: found !chrg (value: 0) > > > > process_status_info: !chrg > > entering string_to_path() > > Looking up UPS > > Looking up PowerSummary > > Looking up PresentStatus > > Looking up ShutdownImminent > > Report : (8 bytes) =3D> 00 00 9C F3 00 03 10 D2 > > hu_find_infoval: searching for value =3D 0 > > > > hu_find_infoval: found !shutdownimm (value: 0) > > > > process_status_info: !shutdownimm > > entering string_to_path() > > Looking up UP...

Arnaud, > first, even if your battery is full, and your ups is online, there is a > small amount of power drawn. So having always is CHRG status is normal. > In fact, these complementary status are more interesting for higher end > UPSs. > > second, these status need not to be handled like LB, as each one clears the > other. While LB had no pending event (!LB) before... >

...a time >> when low battery is reported: > > hmm, are you sure that this log matches the time of the LB event? > > The file drivers/usbhid-ups.c is looking for any of the following > conditions to declare LB: > > ? STATUS(LOWBATT) > ? STATUS(TIMELIMITEXP) > ? STATUS(SHUTDOWNIMM) > > The mapping to HID Path names will depend on the model, but > STATUS(LOWBATT) can come from ...BelowRemainingCapacityLimit, which is > 0 in both instances in your log. STATUS(TIMELIMITEXP) maps to > ...RemainingTimeLimitExpired, which I don't see, and > STATUS(SHUTDOWNIMM...

.../usr/local/libexec/nut/usbhid-ups -a maxell -DD at a time when low battery is reported: hmm, are you sure that this log matches the time of the LB event? The file drivers/usbhid-ups.c is looking for any of the following conditions to declare LB: ? STATUS(LOWBATT) ? STATUS(TIMELIMITEXP) ? STATUS(SHUTDOWNIMM) The mapping to HID Path names will depend on the model, but STATUS(LOWBATT) can come from ...BelowRemainingCapacityLimit, which is 0 in both instances in your log. STATUS(TIMELIMITEXP) maps to ...RemainingTimeLimitExpired, which I don't see, and STATUS(SHUTDOWNIMM) would cause an ups.alarm me...

Gentlemee, I have just encountered a problem with low battery status in newhidups. Here is the situation: 1) The system goes through the shutdown sequence due to low battery, the UPS receives the shutdown.return and shuts off power, 2) After power returns, the UPS turns on power before its battery reserves have reached low battery level (a potentially risky situation if we get another

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

...GE-Ellipse -u root #here we receive VERY long output, the lust lines are: Entering libusb_get_report =>> Before exponent: 0, 0/0) =>> After conversion: 0.000000 (0), 0/0) Report : (8 bytes) => 02 00 E8 03 00 00 00 00 hu_find_infoval: searching for value = 0 hu_find_infoval: found !shutdownimm (value: 0) process_status_info: !shutdownimm entering string_to_path() parsing UPS Looking up UPS hid_lookup_usage: found 840004 parsing PowerSummary Looking up PowerSummary hid_lookup_usage: found 840024 parsing PresentStatus Looking up PresentStatus hid_lookup_usage: found 840002 parsing BelowRe...

...gt; > Following is a copy&paste of the last lines of konsole output: > > /lib/nut/newhidups -a mge -DD -u nut > ---8<--- > Waiting for notifications... > process_status_info: online > process_status_info: !dischrg > process_status_info: chrg > process_status_info: !shutdownimm > process_status_info: !lowbatt > upsdrv_updateinfo... > Waiting for notifications... > Can't retrieve Report 1 (-32/32): Broken pipe > ================================================== > = device has been disconnected, try to reconnect = > ================================...

Arjen de Korte wrote: > > + * drivers/apc-hid.c: > + - Commented out the 'fullycharged' status. If anyone can explain the > + use of this, please step forward. This flag is defined on p.36 of the "Universal Serial Bus Usage Tables for HID Power Devices", Release 1.0 November 1, 1997, a USB standards document available on the web. The document defines this

Hello i tried to connect my netys 2000 pr ups to ubuntu 11.10 and i have a problem connecting it. After readin a few post i realized to dianosse the connection. I need help resolving the connextion issue So here is the response to??/lib/nut/usbhid-ups -u root -DDDDD -a netys: Network UPS Tools - Generic HID driver 0.35 (2.6.1) USB communication driver 0.31 ? ?0.000000 ? ? send_to_all: SETINFO

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

...ainingCapacity, Type: Feature, ReportID: 0x34, Offset: 0, Size: 8, Value: 100.000000 Report[r]: (2 bytes) => 37 64 Path: UPS.PowerSummary.FullChargeCapacity, Type: Feature, ReportID: 0x37, Offset: 0, Size: 8, Value: 100.000000 Report[r]: (2 bytes) => 32 06 Path: UPS.PowerSummary.PresentStatus.ShutdownImminent, Type: Input, ReportID: 0x32, Offset: 0, Size: 1, Value: 0.000000 Can't find object UPS.PowerSummary.PresentStatus.TLACPresent Path: UPS.PowerSummary.PresentStatus.TLACPresent, Type: Input, ReportID: 0x32, Offset: 1, Size: 1 Can't find object UPS.PowerSummary.PresentStatus.TLCharging P...

...PS.PowerSummary.RunTimeToEmpty, Type: Feature, ReportID: 0x35, Offset: 0, Size: 16, Value: 1789.000000 Report[r]: (4 bytes) => 32 00 00 11 Path: UPS.PowerSummary.PresentStatus.InternalFailure, Type: Input, ReportID: 0x32, Offset: 7, Size: 1, Value: 0.000000 Path: UPS.PowerSummary.PresentStatus.ShutdownImminent, Type: Input, ReportID: 0x32, Offset: 9, Size: 1, Value: 0.000000 Path: UPS.PowerSummary.PresentStatus.ACPresent, Type: Input, ReportID: 0x32, Offset: 16, Size: 1, Value: 1.000000 Path: UPS.PowerSummary.PresentStatus.BelowRemainingCapacityLimit, Type: Input, ReportID: 0x32, Offset: 18, Size...

...> 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.PresentStatus.ShutdownImminent, Type: > > Feature, > > Value: 0.000000 > > Path: UPS.PowerSummary.PresentStatus.RemainingTimeLimitExpired, Type: > > Input, Value: 0.000000 > > Path: UPS.Powe...