On Sat, Oct 31, 2020 at 2:42 PM Tim Dawson <tadawson at tpcsvc.com> wrote:> I'm going to guess that since your test runtime of 305 is very close to > the low limit of 300, that's the warning. Not yet a fail, but very, very > close. >I tried setting override.battery.runtime.low = 60 in ups.conf, and waited for the UPS to reach 100% charge, and ups.status to report only OL. I initiated another test.battery.start.quick. Same kind of result: battery.charge: 31 battery.charge.low: 10 battery.charge.warning: 20 battery.mfr.date: CPS battery.runtime: 255 battery.runtime.low: 60 battery.type: PbAcid battery.voltage: 16.0 battery.voltage.nominal: 24 device.mfr: CP1350PFCLCD device.model: CRCA102\#BJ1 device.serial: CPS device.type: ups driver.name: usbhid-ups driver.parameter.pollfreq: 30 driver.parameter.pollinterval: 5 driver.parameter.port: auto driver.parameter.vendorid: 0764 driver.version: 2.7.2 driver.version.data: CyberPower HID 0.3 driver.version.internal: 0.38 input.transfer.high: 139 input.transfer.low: 88 input.voltage: 122.0 input.voltage.nominal: 120 output.voltage: 138.0 ups.beeper.status: disabled ups.delay.shutdown: 20 ups.delay.start: 30 ups.load: 36 ups.mfr: CP1350PFCLCD ups.model: CRCA102#BJ1 ups.productid: 0501 ups.realpower.nominal: 810 ups.serial: CPS ups.status: OL CHRG LB ups.test.result: Done and warning ups.timer.shutdown: -60 ups.timer.start: -60 ups.vendorid: 0764 I'm trying to determine if I need to replace the batteries/device, its out of warranty at this rate anyway. Any more ideas? -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://alioth-lists.debian.net/pipermail/nut-upsuser/attachments/20201031/4210675e/attachment-0001.html>
On Saturday 31 October 2020 20:13:48 Rick Dicaire wrote:> On Sat, Oct 31, 2020 at 2:42 PM Tim Dawson <tadawson at tpcsvc.com> wrote: > > I'm going to guess that since your test runtime of 305 is very close > > to the low limit of 300, that's the warning. Not yet a fail, but > > very, very close. > > I tried setting > override.battery.runtime.low = 60 > in ups.conf, and waited for the UPS to reach 100% charge, and > ups.status to report only OL. > > I initiated another test.battery.start.quick. > Same kind of result: > > battery.charge: 31 > battery.charge.low: 10 > battery.charge.warning: 20 > battery.mfr.date: CPS > battery.runtime: 255 > battery.runtime.low: 60 > battery.type: PbAcid > battery.voltage: 16.0At that voltage, 5 of the 12 cells are shorted> battery.voltage.nominal: 24 > device.mfr: CP1350PFCLCD > device.model: CRCA102\#BJ1 > device.serial: CPS > device.type: ups > driver.name: usbhid-ups > driver.parameter.pollfreq: 30 > driver.parameter.pollinterval: 5 > driver.parameter.port: auto > driver.parameter.vendorid: 0764 > driver.version: 2.7.2 > driver.version.data: CyberPower HID 0.3 > driver.version.internal: 0.38 > input.transfer.high: 139 > input.transfer.low: 88 > input.voltage: 122.0 > input.voltage.nominal: 120 > output.voltage: 138.0too high by about 15 volts> ups.beeper.status: disabled > ups.delay.shutdown: 20 > ups.delay.start: 30 > ups.load: 36 > ups.mfr: CP1350PFCLCD > ups.model: CRCA102#BJ1 > ups.productid: 0501 > ups.realpower.nominal: 810 > ups.serial: CPS > ups.status: OL CHRG LB > ups.test.result: Done and warning > ups.timer.shutdown: -60 > ups.timer.start: -60 > ups.vendorid: 0764 > > I'm trying to determine if I need to replace the batteries/device, its > out of warranty at this rate anyway. > Any more ideas?Wow! That battery is beyond toasted, shoulda been replaced months ago. And the output voltage is a bit much if its truthfull. Cheers, Gene Heskett -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author) If we desire respect for the law, we must first make the law respectable. - Louis D. Brandeis Genes Web page <http://geneslinuxbox.net:6309/gene>
> > > > battery.voltage: 16.0 > At that voltage, 5 of the 12 cells are shorted > > output.voltage: 138.0 > too high by about 15 volts > > Wow! That battery is beyond toasted, shoulda been replaced months ago. > And the output voltage is a bit much if its truthfull. >Thanks for the response Gene! I've ordered a replacement unit. I'm not sure about the output voltage readings, I have four CyberPower CP1500AVRLCDa UPSs and they all show 136-139v output. My CyberPower OR1500LCDMRM1U reports 124v. I still don't know what triggers the warning in the test though... -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://alioth-lists.debian.net/pipermail/nut-upsuser/attachments/20201031/6a64e827/attachment.html>
On Oct 31, 2020, at 8:30 PM, Gene Heskett <gheskett at shentel.net> wrote:> >> battery.voltage: 16.0 > At that voltage, 5 of the 12 cells are shorted >> battery.voltage.nominal: 24The 16.0 is a scaled version of the fixed (bogus) 24.0 V reading, similar to this unit: https://networkupstools.org/ddl/Cyber_Power_Systems/CP1500PFCLCD.html I think we even "fixed" that after NUT 2.7.2, before I realized that many units are providing a bogus value: https://github.com/networkupstools/nut/commit/c8950dee9c91ce45d05d8f220ea26891fb92329e>> output.voltage: 138.0 > too high by about 15 volts >From the other CPS UPS thread on Monday:> This is another known CyberPower issue, and fixing it properly requires making some changes deep in the core USB HID code (that would require a lot of testing on other vendors' equipment) for what is basically a cosmetic issue: > > https://github.com/networkupstools/nut/issues/439https://alioth-lists.debian.net/pipermail/nut-upsuser/2020-October/012126.html
On Oct 31, 2020, at 8:13 PM, Rick Dicaire <kritek at gmail.com> wrote:> > On Sat, Oct 31, 2020 at 2:42 PM Tim Dawson <tadawson at tpcsvc.com <mailto:tadawson at tpcsvc.com>> wrote: > I'm going to guess that since your test runtime of 305 is very close to the low limit of 300, that's the warning. Not yet a fail, but very, very close. >Rick, unfortunately, we don't get a ton of information back from the UPS about battery test results, so Tim's assessment is likely the explanation. (Your UPS is literally sending back "2" for the test result, which maps to that message: https://github.com/networkupstools/nut/blob/master/drivers/usbhid-ups.c#L352 <https://github.com/networkupstools/nut/blob/master/drivers/usbhid-ups.c#L352> . That's part of the USB HID PDC standard - if there are other vendor-specific results returned by CyberPower UPSes, we aren't yet aware of them.)> I tried setting > override.battery.runtime.low = 60The override.* settings are basically used in upsd to replace the values that the driver sends through upsd to clients like upsc and upsmon. The values don't go back down through the driver to the UPS hardware (the intent is to mask bad values sent in the other direction). In order to change a value stored in the UPS, you can use upsrw on the value. (Related: many CyberPower UPS models require the shutdown/startup timer values to be rounded up to the next multiple of 60 seconds.) The one case where you can set override.battery.runtime.low and change the shutdown behavior is when you also set the "ignorelb" option. (I don't see that listed in the driver.parameter.* section of the upsc output.) If you were not having any luck changing that variable with upsrw to affect the shutdown threshold, you could use "ignorelb" to let upsd determine when to send the shutdown command to the UPS (instead of just sending it when the UPS reports LB). https://networkupstools.org/docs/man/ups.conf.html#_ups_fields <https://networkupstools.org/docs/man/ups.conf.html#_ups_fields>> in ups.conf, and waited for the UPS to reach 100% charge, and ups.status to report only OL. > > I initiated another test.battery.start.quick. > Same kind of result: > > battery.charge: 31 > battery.charge.low: 10 > battery.charge.warning: 20 > battery.mfr.date: CPSIt is still possible that the battery is old, and needs to be replaced. The usual guideline is 3-5 years for a lead-acid battery in an UPS. Note that this is a case where you can stash the date you changed out the battery by overriding the "battery.mfr.date: CPS" variable's value with an actual date.> _______________________________________________ > Nut-upsuser mailing list > Nut-upsuser at alioth-lists.debian.net > https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsuser-------------- next part -------------- An HTML attachment was scrubbed... URL: <http://alioth-lists.debian.net/pipermail/nut-upsuser/attachments/20201031/5c9c34dd/attachment.html>