search for: cp1500avrlcda

...md64 NUT 2.7.4p0 (from OpenBSD package) Results of upsc: battery.charge: 100 battery.charge.low: 10 battery.charge.warning: 20 battery.mfr.date: CPS battery.runtime: 2902 battery.runtime.low: 300 battery.type: PbAcid battery.voltage: 26.9 battery.voltage.nominal: 24 device.mfr: CPS device.model: CP1500AVRLCDa device.serial: CTHGN200xxxx device.type: ups driver.name: usbhid-ups driver.parameter.pollfreq: 30 driver.parameter.pollinterval: 2 driver.parameter.port: auto driver.parameter.product: CP1500AVRLCDa driver.parameter.productid: 0501 driver.parameter.serial: CTHGN200xxxx driver.parameter.synchronous...

...set up with FreeBSD 11.0 (AMD64), nut-2.7.4_1 from the FreeBSD pkg. :) dmseg excerpt for the UPS: ugen1.2: <CPS> at usbus1 Result of the command, where "n" is incremented in a loop: # usbconfig -u 1 -a 2 dump_string n STRING_0x00 = 0x04, 0x03, 0x09, 0x04 STRING_0x01 = <CP1500AVRLCDa> STRING_0x02 = <CTHGN200xxxx> STRING_0x03 = <CPS> STRING_0x04 = <PbAcid> STRING_0x05 = <BF01512BA31> STRING_0x06 = <read error> STRING_0x07 = <read error> STRING_0x08 = <read error> STRING_0x09 = <read error> STRING_0x0a = <read error&g...

...md64 NUT 2.7.4p0 (from OpenBSD package) Results of upsc: battery.charge: 100 battery.charge.low: 10 battery.charge.warning: 20 battery.mfr.date: CPS battery.runtime: 2902 battery.runtime.low: 300 battery.type: PbAcid battery.voltage: 26.9 battery.voltage.nominal: 24 device.mfr: CPS device.model: CP1500AVRLCDa device.serial: CTHGN200xxxx device.type: ups driver.name: usbhid-ups driver.parameter.pollfreq: 30 driver.parameter.pollinterval: 2 driver.parameter.port: auto driver.parameter.product: CP1500AVRLCDa driver.parameter.productid: 0501 driver.parameter.serial: CTHGN200xxxx driver.parameter.synchronous...

...; > > Results of upsc: > > battery.charge: 100 > battery.charge.low: 10 > battery.charge.warning: 20 > battery.mfr.date: CPS Let me know if you're interested in figuring out if the battery.mfr.date value is stored somewhere else. > device.mfr: CPS > device.model: CP1500AVRLCDa > device.serial: CTHGN200xxxx ... > driver.version: 2.7.4 > driver.version.data: CyberPower HID 0.4 > driver.version.internal: 0.41 > input.voltage: 121.0 > input.voltage.nominal: 120 > output.voltage: 137.0 The output voltage seems a little high. Is this UPS configured to boo...

On Jun 5, 2017, at 11:21 AM, Mike <the.lists at mgm51.com> wrote: > > Result of the command, where "n" is incremented in a loop: > > # usbconfig -u 1 -a 2 dump_string n > STRING_0x00 = 0x04, 0x03, 0x09, 0x04 > STRING_0x01 = <CP1500AVRLCDa> > STRING_0x02 = <CTHGN200xxxx> > STRING_0x03 = <CPS> > STRING_0x04 = <PbAcid> > STRING_0x05 = <BF01512BA31> > STRING_0x06 = <read error> > STRING_0x07 = <read error> > STRING_0x08 = <read error> > STRING_0x09 = <read e...

...usual recommendations apply (let it run for 30 seconds, and gzip the logs), but the serial numbers might be labeled differently - so perhaps grep for the first few characters, rather than relying on a "serial" label. > >> >>> device.mfr: CPS >>> device.model: CP1500AVRLCDa >>> device.serial: CTHGN200xxxx >> ... >>> driver.version: 2.7.4 >>> driver.version.data: CyberPower HID 0.4 >>> driver.version.internal: 0.41 >>> input.voltage: 121.0 >>> input.voltage.nominal: 120 >>> output.voltage: 137.0 >&...

...7 121.1 120 142.0 118.0 > 140.8 122.8 139 136.0 139.0 > 121.7 122.1 121 136.0 120.0 This is starting to come back to me - I think we saw this with several other CPS devices. Here's an excerpt from the CP1500AVRLCDa HID descriptor: Collection(Physical) Report ID(16) Usage(LowVoltageTransfer) Logical Minimum(97) Logical Maximum(103) Feature(Data,Variable,Absolute) Usage(LowVoltageTransfer) Input(Constant,Variable,Absolute) Usage(HighVoltageTransfer)...

...9;re interested in figuring out if the battery.mfr.date value is stored somewhere else. Of course. The UPS is in production (ie., powering the servers in my house), so it may be a few days before I can ~play~. Let me know what I need to do. > >> device.mfr: CPS >> device.model: CP1500AVRLCDa >> device.serial: CTHGN200xxxx > ... >> driver.version: 2.7.4 >> driver.version.data: CyberPower HID 0.4 >> driver.version.internal: 0.41 >> input.voltage: 121.0 >> input.voltage.nominal: 120 >> output.voltage: 137.0 > > The output voltage seems a...

On 5/30/2017 10:47 PM, Charles Lepple wrote: > On May 22, 2017, at 11:13 AM, Mike <the.lists at mgm51.com> wrote: >> >> On 5/21/2017 10:39 AM, Charles Lepple wrote: [snip] > Even though the CPS sub-driver has been written already, I would like to take a look at the raw "explore" mode output: > >

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: 24 The 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

...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/attachm...

?? Ubuntu Server 16.04.1 LTS NUT 2.7.2-4ubuntu1 NUT installed from apt CP1500AVRLCDa Complete problem description, with any relevant traces, like system log excerpts, and driver debug output. You can obtain the latter using the following command, as root and after having stopped NUT: Problem Description: Ubuntu is able to communicate fine with the ups for several hours. However, t...

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