search for: cthgn200xxxx

...D 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: no driver.parameter.vendor...

...D 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: no driver.parameter.vendor...

...t-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> I wasn't sure how high I sho...

...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 little high. Is this UPS configured...

...; > 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 boost voltage? Do either the input o...

...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 error> > STRING_0x0a = <read err...

...r 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 >> >> 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: > >