Re: [Nut-upsuser] UPS Atlantis OnePower - VT12094S
Citeren Andrea krog...@gmail.com: Exactly what benefit can i have using the new driver with this hack? If nothing changes i can wait for nut 2.6.1 ;-) It would help to confirm that this is indeed the problem so that nut-2.6.1 will work out-of-the box for you (and all others using this model). Other than that, see 'man 8 blazer' for more information on the additional commands for this driver. The runtime estimation is something the megatec(_usb) driver didn't support for instance. 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] UPS Atlantis OnePower - VT12094S
* Service upsdrv starting Network UPS Tools - UPS driver controller 2.6.0 Network UPS Tools - Megatec/Q1 protocol USB driver 0.03 (2.6.0) Can't claim USB device [:]: could not detach kernel driver from interface 0: Operation not permitted Driver failed to start (exit status=1) Failed to start UPS drivers! Maybe i'm doing something wrong during compilation of the sources... Thanks in advice, Andrea 2011/3/30 Arjen de Korte nut+us...@de-korte.org: Citeren Andrea krog...@gmail.com: Exactly what benefit can i have using the new driver with this hack? If nothing changes i can wait for nut 2.6.1 ;-) It would help to confirm that this is indeed the problem so that nut-2.6.1 will work out-of-the box for you (and all others using this model). Other than that, see 'man 8 blazer' for more information on the additional commands for this driver. The runtime estimation is something the megatec(_usb) driver didn't support for instance. 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] UPS Atlantis OnePower - VT12094S
Citeren Andrea krog...@gmail.com: * Service upsdrv starting Network UPS Tools - UPS driver controller 2.6.0 Network UPS Tools - Megatec/Q1 protocol USB driver 0.03 (2.6.0) Can't claim USB device [:]: could not detach kernel driver from interface 0: Operation not permitted Driver failed to start (exit status=1) Failed to start UPS drivers! Maybe i'm doing something wrong during compilation of the sources... Most likely, this is a permissions error from not configuring properly. For now, just fix this by running the driver as root: /path/to/blazer_usb -u root -DDD -a upsname Best regards, Arjen PS Please do not top-post on this mailing list. -- 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
[Nut-upsuser] Information required for adding a ups to the compatibility list
Just wondering what information is required for adding a ups to the compatability list... Is upsc output enough? I've got a Inform Sinus SS 210 ( http://www.informups.com/sinus_1_phase_technics.html ) that seems to be working allright with the blazer_ser driver Here is the upsc output: battery.charge: 100 battery.runtime: 1379 battery.voltage: 41.40 battery.voltage.nominal: 36.0 beeper.status: disabled device.mfr: Inform device.model: SINUS1KURM device.type: ups driver.name: blazer_ser driver.parameter.pollinterval: 2 driver.parameter.port: /dev/ttyS0 driver.parameter.runtimecal: 480,100,1200,50 driver.version: 2.4.3 driver.version.internal: 1.51 input.current.nominal: 5.0 input.frequency: 50.0 input.frequency.nominal: 50 input.voltage: 243.1 input.voltage.fault: 190.0 input.voltage.nominal: 220 output.voltage: 220.0 ups.delay.shutdown: 30 ups.delay.start: 180 ups.firmware: MS02035C ups.load: 45 ups.mfr: Inform ups.model: SINUS1KURM ups.status: OL ups.temperature: 40.5 ups.type: online ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] Information required for adding a ups to the compatibility list
Citeren Garðar Arnarsson gar...@giraffi.net: Just wondering what information is required for adding a ups to the compatability list... Is upsc output enough? No, we also need to know if the UPS supports shuts down automatically, both when on mains and on battery. To check this, issue the upsmon -c fsd command from the upsmon master system, first with and then without mains present. In the first case, the UPS should cycle the power and in the second wait until the power returns. You'll want to make sure all systems powered from the UPS are ready to lose power. 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
[Nut-upsuser] Startup timing issue with CyberPower CP425HG UPS
Hi all - I'm running into a small problem with the CyberPower CP425HG UPS and NUT 2.4 on Fedora 11. For whatever reason, at system startup this UPS registers as a USB device very late in the boot process, *after* all the services have started. So at boot up when the ups service in init.d tries to start upsdrvctl, it fails because no USB UPS device cannot be found. Hence the auto-shutdown on low battery does not work. This all works great if I start the ups service manually (service ups start) after the system has booted up. 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? System information: Fedora 11, Kernel 2.6.30, NUT 2.4.3 UPS product page: http://www.cyberpowersystems.com/products/ups-systems/soho-ups/CP425HG.html Thanks, Arun ___ 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
