Re: [Nut-upsuser] Cyberpower CP850PFCLCD 120% battery charge
Citeren Justin Ellison jus...@techadvise.com: Attached is a -DDD log of the driver. Did you look at it before sending it? If not, look now... :-) We need the output of both stdout and stderr: /path/to/usbhid-ups -DDD -a upsname CyberPower_CP850.log 21 The first 30 seconds worth of output should be enough. If you need anything else, let me know. See above. Best regards, Arjen -- Please keep list traffic on the list (off-list replies will be rejected) ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] Cyberpower CP850PFCLCD 120% battery charge
Attached is a -DDD log of the driver. If you need anything else, let me know. Justin On Fri, Apr 1, 2011 at 2:20 AM, Arjen de Korte nut+us...@de-korte.org wrote: Citeren Justin Ellison jus...@techadvise.com: When I tested it out tonight, I made a point to watch the LED on the unit in comparison to the battery.charge indicator from nut. Almost instant I unplugged it, battery.charge went from 120 to 91, and immediately fell in sync with what the LED was showing. In that case, we should probably just clamp the value to 100%. Another thing is that the battery voltage doesn't seem to change at all, it is fixed at 16.0 V (due to an internal conversion factor of 2/3 that is needed on some other models). Best regards, Arjen -- Please keep list traffic on the list (off-list replies will be rejected) ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser CP850PFCLCD.log Description: Binary data ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] Cyberpower CP850PFCLCD 120% battery charge
Citeren Charles Lepple clep...@gmail.com: in the current version of cps-hid.c, it looks like FullChargeCapacity, DesignCapacity and CapacityMode are unmapped. This is intentional. The capacity mode determines the units in which FullChargeCapacity and DesignCapacity will be reported. Generally, this will be '2' so values are reported in percent (%). In many cases they will read 100% at all times (I have yet to find a UPS where the FullChargeCapacity drops with aging batteries). Or, it could be that the firmware designers confused the RemainingCapacity value with AbsoluteStateOfCharge, which is allowed to be greater than 100%. (Pages 36-38 of the PDC spec.) That could also be the case. Given the fact that this is a highly loaded UPS (56%), it wouldn't be strange that you would need more than 81% charge left if you set the low battery level to a runtime remaining of 300 seconds. Are two -D flags sufficient to see the report descriptor information and relevant reports? With just two '-D' flags, you'll get a dump of all HID paths that are supported by the UPS. We need three '-D' flags however to see the raw report descriptor, which I would like to archive for future use. Best regards, Arjen -- Please keep list traffic on the list (off-list replies will be rejected) ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] Cyberpower CP850PFCLCD 120% battery charge
Citeren Justin Ellison jus...@techadvise.com: When I tested it out tonight, I made a point to watch the LED on the unit in comparison to the battery.charge indicator from nut. Almost instant I unplugged it, battery.charge went from 120 to 91, and immediately fell in sync with what the LED was showing. In that case, we should probably just clamp the value to 100%. Another thing is that the battery voltage doesn't seem to change at all, it is fixed at 16.0 V (due to an internal conversion factor of 2/3 that is needed on some other models). Best regards, Arjen -- Please keep list traffic on the list (off-list replies will be rejected) ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] Cyberpower CP850PFCLCD 120% battery charge
Citeren Justin Ellison jus...@techadvise.com: I have a CyberPower Systems CP850PFCLCD that I'm hooking up to NUT 2.4.3 from apt running under Ubuntu 10.04. Using the usbhid-ups driver, things *seem* to work at first glance, but there are some odd issues. The most notable issue is that the battery.charge indicator reads 120 when at full charge. I came across this post here: http://lists.alioth.debian.org/pipermail/nut-upsuser/2007-September/003222.htmlbut it looks like the user never supplied the necessary data. For whatever reason the people that made the UPS firmware decided that they didn't need to follow the USB HID PDC specifications. From the data you sent, it looks like the value for battery charge that is reported by the UPS needs some conversion (coefficient and/or offset) to get to the true battery charge. Most likely, this is present in the bundled software for the UPS, but sadly we don't know them. So unless you're going to change that, the situation is unlikely to improve. It looks like '120' means 100% charge, but one data point is not enough to find (at least) two missing parameters. The other issue that I found was that the LB flag is sent way to early when I unplugged the UPS from the outlet. I don't think so. The data you posted indicated that about the time the UPS started reporsing LB (low battery), the runtime fell below the battery.runtime.low, so this is about right. If you don't need 5 minutes to shutdown your system, you might try lowering this value (if the UPS supports that) and see if this increases the useable time on battery. Best regards, Arjen -- Please keep list traffic on the list (off-list replies will be rejected) ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] Cyberpower CP850PFCLCD 120% battery charge
Good news, this model appears to work perfectly, save for an odd factory default. I only have 55% of a load on this thing, but the minute I unplug it, I have right around 5 mins of battery time. That was causing the LB flag to be set almost immediately(because the factory default for low runtime was 300). I was able to set a new bettery.runtime.low of 120 using upsrw. On Thu, Mar 31, 2011 at 2:09 PM, Arjen de Korte nut+us...@de-korte.org wrote: For whatever reason the people that made the UPS firmware decided that they didn't need to follow the USB HID PDC specifications. From the data you sent, it looks like the value for battery charge that is reported by the UPS needs some conversion (coefficient and/or offset) to get to the true battery charge. Most likely, this is present in the bundled software for the UPS, but sadly we don't know them. So unless you're going to change that, the situation is unlikely to improve. It looks like '120' means 100% charge, but one data point is not enough to find (at least) two missing parameters. When I tested it out tonight, I made a point to watch the LED on the unit in comparison to the battery.charge indicator from nut. Almost instant I unplugged it, battery.charge went from 120 to 91, and immediately fell in sync with what the LED was showing. The other issue that I found was that the LB flag is sent way to early when I unplugged the UPS from the outlet. I don't think so. The data you posted indicated that about the time the UPS started reporsing LB (low battery), the runtime fell below the battery.runtime.low, so this is about right. If you don't need 5 minutes to shutdown your system, you might try lowering this value (if the UPS supports that) and see if this increases the useable time on battery. Aside from the minor annoyance of the 120 battery.charge when full, this UPS works perfectly with Nut. Nice work guys! Justin ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
[Nut-upsuser] Cyberpower CP850PFCLCD 120% battery charge
Hello all, I have a CyberPower Systems CP850PFCLCD that I'm hooking up to NUT 2.4.3 from apt running under Ubuntu 10.04. Using the usbhid-ups driver, things *seem* to work at first glance, but there are some odd issues. The most notable issue is that the battery.charge indicator reads 120 when at full charge. I came across this post here: http://lists.alioth.debian.org/pipermail/nut-upsuser/2007-September/003222.htmlbut it looks like the user never supplied the necessary data. The other issue that I found was that the LB flag is sent way to early when I unplugged the UPS from the outlet. I captured a log of upsc polling every 5 seconds and I'm attaching to this message. I'm more than happy to supply debug output, but I don't know if you want me to unplug the UPS from the outlet during that debug or not. Thanks in advance for any help, Justin ue Mar 29 23:30:39 CDT 2011 battery.charge: 120 battery.charge.low: 10 battery.charge.warning: 20 battery.mfr.date: CPS battery.runtime: 450 battery.runtime.low: 300 battery.type: PbAcid battery.voltage: 16.0 battery.voltage.nominal: 24 device.mfr: CP850PFCLCD device.model: CRDA103.981 device.serial: CPS device.type: ups driver.name: usbhid-ups driver.parameter.pollfreq: 30 driver.parameter.pollinterval: 2 driver.parameter.port: auto driver.version: 2.4.3 driver.version.data: CyberPower HID 0.3 driver.version.internal: 0.34 input.transfer.high: 139 input.transfer.low: 88 input.voltage: 117.0 input.voltage.nominal: 120 output.voltage: 117.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: OL ups.test.result: No test initiated ups.timer.shutdown: -60 ups.timer.start: -60 ups.vendorid: 0764 Tue Mar 29 23:30:44 CDT 2011 battery.charge: 105 battery.charge.low: 10 battery.charge.warning: 20 battery.mfr.date: CPS battery.runtime: 367 battery.runtime.low: 300 battery.type: PbAcid battery.voltage: 16.0 battery.voltage.nominal: 24 device.mfr: CP850PFCLCD device.model: CRDA103.981 device.serial: CPS device.type: ups driver.name: usbhid-ups driver.parameter.pollfreq: 30 driver.parameter.pollinterval: 2 driver.parameter.port: auto driver.version: 2.4.3 driver.version.data: CyberPower HID 0.3 driver.version.internal: 0.34 input.transfer.high: 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.voltage: 16.0 battery.voltage.nominal: 24 device.mfr: CP850PFCLCD device.model: CRDA103.981 device.serial: CPS device.type: ups driver.name: usbhid-ups driver.parameter.pollfreq: 30 driver.parameter.pollinterval: 2 driver.parameter.port: auto driver.version: 2.4.3 driver.version.data: CyberPower HID 0.3 driver.version.internal: 0.34 input.transfer.high: 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:54 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.voltage: 16.0 battery.voltage.nominal: 24 device.mfr: CP850PFCLCD device.model: CRDA103.981 device.serial: CPS device.type: ups driver.name: usbhid-ups driver.parameter.pollfreq: 30 driver.parameter.pollinterval: 2 driver.parameter.port: auto driver.version: 2.4.3 driver.version.data: CyberPower HID 0.3 driver.version.internal: 0.34 input.transfer.high: 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:59 CDT 2011 battery.charge: 87 battery.charge.low: 10 battery.charge.warning: 20 battery.mfr.date: CPS battery.runtime: 304 battery.runtime.low: 300 battery.type: PbAcid battery.voltage: 16.0 battery.voltage.nominal: 24 device.mfr: CP850PFCLCD device.model: CRDA103.981
Re: [Nut-upsuser] Cyberpower CP850PFCLCD 120% battery charge
On Mar 30, 2011, at 9:53 PM, Justin Ellison wrote: Tue Mar 29 23:31:14 CDT 2011 battery.charge: 81 battery.charge.low: 10 battery.charge.warning: 20 battery.mfr.date: CPS battery.runtime: 283 battery.runtime.low: 300 Not sure about the 120% charge issue. The UPS decides when to signal a low battery condition, and at this point in the logs, the UPS's estimation of remaining runtime has dropped below the limit. I'd guess that the LB flag is set when either the runtime or the charge goes below its limit. You should[*] be able to use upsrw to adjust battery.runtime.low, but be sure to account for the amount of time needed to sync filesystems and kill processes. [*] Both battery.runtime.low and battery.charge.low are flagged as writable by the driver, but the actual result depends on the UPS firmware. ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
