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
Re: [Nut-upsuser] Startup timing issue with CyberPower CP425HG UPS
On Mar 30, 2011, at 9:46 PM, Arun wrote: I'm not sure how to fix this, other than to perhaps start the ups service from the udev rules file if a known USB UPS device has been found, but that seems like a rather ugly way to go about this. Does anyone have any thoughts? I have had a sneaking suspicion that in some situations, starting a USB driver from hotplug or udev might work better, and this is definitely one of those cases. Before you get too far into this, you probably want to make sure that when power returns, your UPS will wait until the battery is charged to some threshold before powering on its outlets. Otherwise, if the power goes off-on-off (with a shutdown after the first power failure), the UPS might try to start the computer up with a discharged battery, and due to the delay in connecting to the UPS, NUT would not get the low battery signal in time to shut down properly the second time. The other trick is that the current NUT USB drivers will attempt to reattach to a device if it disappears. Especially during testing, it is helpful to be able to unplug and re-plug the UPS into the USB port. For this to work, the udev script could kill the driver which is waiting around for the UPS to come back. (That would only do the right thing on a single-UPS system.) Alternatively, you could check in the udev script to see if any of the USB drivers are running (look for the PID files, and run kill -0 to see if the process is still around without actually terminating it). On the other hand, you can also look into whether your startup scripts have configurable dependencies, and tell the NUT init.d script to start after the USB service has fully initialized. Not sure how that works in Fedora. ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
