search for: cp1350pfclcd

Arjen, all, I just built and installed network-ups-tools-git-v2.7.4.r161.g7bf209a on Archlinux for a CyberPower CP1350PFCLCD ups. After hitting the FAQ 29. "My USB UPS is supported but doesn?t work!" udev issue because the UPS was plugged in when nut was installed bug, running upsc I get: battery.charge: 100 battery.charge.low: 10 battery.charge.warning: 20 battery.mfr.date: CPS battery.runtime: 3450 battery.r...

nut 2.7.2 linux 3.18.7 CyberPower CP1350PFCLCD The LCD shows the same for input and output, my multimeter also matches the input voltage. But nut is giving me different numbers. How do I debug this? input.voltage: 122.0 output.voltage: 138.0 I still need to check what it does on battery and what the other readings are. But the voltage stuck...

Hi folks, new to list... nut 2.7.2 on Ubuntu 16.04 with Cyberpowersystems CP1350PFCLCD. After performing upscmd cp1350 at localhost test.battery.start.quick the result was "Done and warning". I searched through syslog but could find no additional information. What is the warning? Battery charge was 100% before test was performed. Here's the full output from upsc afte...

[please use reply-all to include the list. thanks!] > On Nov 26, 2015, at 9:47 AM, Weedy <weedy2887 at gmail.com> wrote: > > nut 2.7.2 > linux 3.18.7 > CyberPower CP1350PFCLCD > > The LCD shows the same for input and output, my multimeter also > matches the input voltage. > But nut is giving me different numbers. How do I debug this? > > input.voltage: 122.0 > output.voltage: 138.0 > > I still need to check what it does on battery and what t...

...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. On October 31, 2020 11:41:39 AM CDT, Rick Dicaire <kritek at gmail.com> wrote: >Hi folks, new to list... >nut 2.7.2 on Ubuntu 16.04 with Cyberpowersystems CP1350PFCLCD. > >After performing upscmd cp1350 at localhost test.battery.start.quick the >result was "Done and warning". I searched through syslog but could find no >additional information. > >What is the warning? > >Battery charge was 100% before test was performed. >Here&...

...rt 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....

...rge: 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 At 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.da...

I was doing some testing with the 2.6.0-1 beta Windows installer and a Cyber Power CP1350PFCLCD UPS, and ran into an infinite loop in the usbhid-ups driver if the UPS is lost on the UPS bus. This is on a Windows XP SP3 system. USB device access is via libusb 1.2.4.0 (driver mode, not filter) in case that matters. Everything seems to work just fine so far while the UPS is connected (so kudo...