search for: dischrg

...and observed a wall message and status change - unplugged again and observed another wall message and status change - waited for the battery to run down - here's an extract from that log: {"time": "2020-07-22T02:20:22", "charge": 3, "status": "OB DISCHRG", "runtime": 138} {"time": "2020-07-22T02:20:32", "charge": 3, "status": "OB DISCHRG", "runtime": 128} {"time": "2020-07-22T02:20:42", "charge": 3, "status": "OB DISCHRG", &q...

...he mge-utalk (serial) driver on NetBSD 3.1 . I had a very strange occurance in my basement datacenter this early AM. the following was logged by upslog: 20080219 023452 100.0 123.0 049.0 [OL CHRG] NA 60.00 20080219 023522 100.0 122.8 049.0 [OL CHRG] NA 60.00 20080219 023552 098.0 123.0 049.0 [OL DISCHRG] NA 60.00 20080219 023622 097.0 123.0 049.0 [OL DISCHRG] NA 60.00 ... 20080219 063429 019.0 122.6 049.0 [OL DISCHRG] NA 60.00 20080219 063459 019.0 122.8 049.0 [OL DISCHRG] NA 60.00 20080219 183013 100.0 121.1 050.0 [OL CHRG] NA 60.00 20080219 183043 100.0 120.9 049.0 [OL CHRG] NA 60.00 the good...

On Sat, Jun 27, 2020, at 23:11, Manuel Wolfshant wrote: > On 6/28/20 5:54 AM, Scott Colby wrote: >> >> I'm not convinced this is the problem; I think that pfSense has an alternative way of running the NUT components: # ps aux | grep ups root 45456 0.0 0.1 6796 884 - Is 02:22 0:00.01 /usr/local/sbin/upsmon uucp 45751 0.0 0.1 6796 772 - S 02:22

Hi Charles, 2015-03-29 0:44 GMT+01:00 Charles Lepple <clepple at gmail.com>: > On Mar 25, 2015, at 4:11 AM, Arnaud Quette <arnaud.quette at gmail.com> > wrote: > > > 1) Keep the legacy CHRG / DISCHRG status bits for ups.status, along with > the complementary ones for battery.charger.status. And advocate (document) > for the use of / switch to the latter, that is more suitable for publishing > such information. All that with an impact on all the NUT driver, and a > transition period...

...and observed a wall message and status change - unplugged again and observed another wall message and status change - waited for the battery to run down - here's an extract from that log: {"time": "2020-07-22T02:20:22", "charge": 3, "status": "OB DISCHRG", "runtime": 138} {"time": "2020-07-22T02:20:32", "charge": 3, "status": "OB DISCHRG", "runtime": 128} {"time": "2020-07-22T02:20:42", "charge": 3, "status": "OB DISCHRG", &q...

>> But I noticed two other details: >> 1. I was a bit wrong with step 7 and 8 - Looks like the UPS is "OL CHRG" (according to display) at first but goes to battery ("OL DISCHRG" according to nut) right when the RasPi (and nut) is booting. >> 2. When I pull the plug of the RasPi after UPS went down before main power comes back (so between step 5 and 6), the UPS comes up in state "OL CHRG" and is stable. >> >> Maybe nut is sending `upsdrvctl...

...t/tree/pull_158_bcmxcp_rebased It has introduced the battery.charger.status variable, which is something I wanted to implement since around 2007. However, while considering a similar implementation for usbhid-ups, and thinking a bit more broadly, this new variable tends to collide with the CHRG / DISCHRG status bits from ups.status, and adding 2 more (floating and resting). There, we have 2 options: 1) Keep the legacy CHRG / DISCHRG status bits for ups.status, along with the complementary ones for battery.charger.status. And advocate (document) for the use of / switch to the latter, that is more s...

...appens if you use the default values of offdelay=20 and ondelay=30 > seconds, or longer? With defaults its the same. But I noticed two other details: 1. I was a bit wrong with step 7 and 8 - Looks like the UPS is "OL CHRG" (according to display) at first but goes to battery ("OL DISCHRG" according to nut) right when the RasPi (and nut) is booting. 2. When I pull the plug of the RasPi after UPS went down before main power comes back (so between step 5 and 6), the UPS comes up in state "OL CHRG" and is stable. Maybe nut is sending `upsdrvctl shutdown` right after boo...

On Mar 25, 2015, at 4:11 AM, Arnaud Quette <arnaud.quette at gmail.com> wrote: > 1) Keep the legacy CHRG / DISCHRG status bits for ups.status, along with the complementary ones for battery.charger.status. And advocate (document) for the use of / switch to the latter, that is more suitable for publishing such information. All that with an impact on all the NUT driver, and a transition period to address that clea...

Peter, Here are the transitions that I have tested with your latest changes (on the APC/Back-UPS ES 650): 1) OL ==> OB DISCHRG followed by OB DISCHRG ==> OL (no CHRG inbetween) 2) OL CHRG ==> OL 3) OL CHRG ==> OL CHRG LB (by manipulating battery.charge.low) 4) OL CHRG LB ==> OL CHRG (i.e. transition from below) 5) OB DISCHRG ==> FSD OB DISCHRG LB followed by proper shutdown In other words, as far as I can se...

...is. Chris Pratt Development Infrastructure Manager T: +44 118 929 4176 | M: +44 7979 854 307 | F: +44 118 929 4001 -----Original Message----- From: Charles Lepple [mailto:clepple at gmail.com] Sent: 16 July 2013 00:32 To: Pratt Chris Subject: Re: [Nut-upsuser] HP R12000/3 UPS reports status as OL DISCHRG OB On Jul 15, 2013, at 9:35 AM, Pratt Chris wrote: > Debug output attached. Sorry, didn't appear to be attached. -- Charles Lepple clepple at gmail Disclaimer: This message and any attachments thereto are intended solely for the addressed recipient(s) and may contain confidential inf...

...104730 => value: 3 0.104823 getting data: ups.status (.1.3.6.1.4.1.232.165.3.2.5.0) 0.104919 su_ups_get: ups.status .1.3.6.1.4.1.232.165.3.2.5.0 0.105028 nut_snmp_get(.1.3.6.1.4.1.232.165.3.2.5.0) 0.107134 SNMP UPS driver : entering su_status_set() 0.107231 su_find_infoval: found DISCHRG (value: 2) 0.107319 => value: 2 0.107412 getting data: ups.status (.1.3.6.1.4.1.232.165.3.7.3.0) 0.107507 su_ups_get: ups.status .1.3.6.1.4.1.232.165.3.7.3.0 0.107616 nut_snmp_get(.1.3.6.1.4.1.232.165.3.7.3.0) 0.109529 SNMP UPS driver : entering su_status_set() 0.109630 su_fin...

...working on it again now. Hi Chris, Is this the patch you are referring to? http://thread.gmane.org/gmane.comp.monitoring.nut.user/7514/focus=7546 > I?m at the point where I can start the driver with upsdrvctl and start the daemon with upsd. When I check the UPS status though it shows as OL DISCHRG OB, which can?t be right (it should just be OL). Please send the debug output from starting the snmp-ups driver directly (rather than through upsdrvctl). That should explain why the driver is getting those particular status bits. Bonus points if you can show the output for both online as well as o...

...00/3 UPS. Unfortunately shortly after I had to take quite a lot of sick leave so wasn't able to progress it, but I'm working on it again now. I'm at the point where I can start the driver with upsdrvctl and start the daemon with upsd. When I check the UPS status though it shows as OL DISCHRG OB, which can't be right (it should just be OL). Any suggestions? Console output attached. Chris. Chris Pratt Development Infrastructure Manager Comptel Corporation 69 Suttons Business Park, Sutton Park Avenue, Reading, RG6 1AZ, UK T: +44 118 929 4176 | M: +44 7979 854 307 | F: +44 118 929...

...icating something else. > [/soapbox] fully right, and mea culpa. This goes back a long time ago, and I never got back on this. since this is a battery information, it clearly belongs to the battery collection. but I still hesitate between: - battery.charging (yes/no): simply address the CHRG / DISCHRG problem. - battery.status: would wrap a bigger scope and complete ups.status: CHRG - The battery is charging DISCHRG - The battery is discharging RB - The battery needs to be replaced and possibly duplicating: LB - Low battery Though RB and LB fits fine into ups.s...

...500U FW3.A4. All works almost fine but here are some troubles: when I pull the plug then upsd immediately starts (after FINALDELAY delaying) the procedure of shutdown as if UPS have low battery. What I see after pulling the plug: ./upsc xen-home battery.charge 72 ./upsc xen-home ups.status OB DISCHRG OB status is correct but why is there DISCHRG status?! This flag, as I think, cause immediately begin of shutdown although the battery is not discharged and has 72 percent of charge. Is DISCHRG exactly from UPS or is it an inaccurate interpretation of obtained status from WOW-500U? TIA, Serge...

...sock /var/state/ups/newhidups-auto open on fd 5 upsdrv_updateinfo... Waiting for notifications... =>Got 1 HID Objects... battery.charge = 83 upsdrv_updateinfo... Waiting for notifications... =>Got 8 HID Objects... ups.status = !shutdownimm ups.status = online ups.status = chrg ups.status = !dischrg ups.status = !replacebatt find_hid_info: unknown variable: UPS.PowerSummary.PresentStatus. find_hid_info: unknown variable: UPS.PowerSummary.PresentStatus. find_hid_info: unknown variable: UPS.PowerSummary.PresentStatus. upsdrv_updateinfo... Waiting for notifications... =>Got 1 HID Objects.....

Hello all, as users of certain (primarily CyberPower and APC) devices know, some firmwares report both "online" and "discharging" in some situations. These depend on the device, vendor and firmware, but cases seen in practice include: * calibration (APC), * being on-battery (CPS), * having got charged to 100% (APC) Recent attention to this area culminated in PR

...139 input.transfer.low: 88 input.voltage: 0.0 input.voltage.nominal: 120 output.voltage: 120.0 ups.beeper.status: enabled ups.delay.shutdown: 20 ups.delay.start: 30 ups.load: 56 ups.mfr: CP850PFCLCD ups.model: CRDA103.981 ups.productid: 0501 ups.realpower.nominal: 510 ups.serial: CPS ups.status: OB DISCHRG ups.test.result: No test initiated ups.timer.shutdown: -60 ups.timer.start: -60 ups.vendorid: 0764 Tue Mar 29 23:30:49 CDT 2011 battery.charge: 96 battery.charge.low: 10 battery.charge.warning: 20 battery.mfr.date: CPS battery.runtime: 360 battery.runtime.low: 300 battery.type: PbAcid battery.volt...

...lt values of offdelay=20 and ondelay=30 >> seconds, or longer? > With defaults its the same. > > > But I noticed two other details: > 1. I was a bit wrong with step 7 and 8 - Looks like the UPS is "OL CHRG" (according to display) at first but goes to battery ("OL DISCHRG" according to nut) right when the RasPi (and nut) is booting. > 2. When I pull the plug of the RasPi after UPS went down before main power comes back (so between step 5 and 6), the UPS comes up in state "OL CHRG" and is stable. > > Maybe nut is sending `upsdrvctl shutdown` r...