> Subject: [Nut-upsuser] CyberPower DX600E won't switch up after power > is back > Message-ID: <3c530815d1ea602efdfec0d67eb1e0b1 at secretfatty.net> > Content-Type: text/plain; charset=UTF-8; format=flowed > > Hello > I have an issue with an CyberPower DX600E, > it doesn't switch up when the power is back; after it has been > unloaded; > is it because of one of those variables ? > regards > Franck > > #upsc myups > battery.charge: 100 > battery.charge.low: 10 > battery.charge.warning: 20 > battery.mfr.date: CPS > battery.runtime: 1380 > battery.runtime.low: 300 > battery.type: PbAcid > battery.voltage: 4.7 > battery.voltage.nominal: 12 > device.mfr: CPS > device.model: DX600E > 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: 0 > input.transfer.low: 0 > input.voltage: 230.0 > input.voltage.nominal: 230 > output.voltage: 238.0 > ups.beeper.status: enabled > ups.delay.shutdown: 20 > ups.delay.start: 30 > ups.load: 31 > ups.mfr: CPS > ups.model: DX600E > ups.productid: 0501 > ups.realpower.nominal: 360 > ups.status: OL > ups.timer.shutdown: -60 > ups.timer.start: 0 > ups.vendorid: 0764 > > > --- > I'm http://secretfatty.net CEO, bitch ! > >Am i suppose to run a "shutdown.return" command ? Does it make sense to do it in the script triggering (for example when receiving "low battery" ?
Arnaud Quette
2012-Nov-26 17:39 UTC
[Nut-upsuser] CyberPower DX600E won't switch up after power
Hi Franck 2012/11/23 Franck <franck at secretfatty.net>> Subject: [Nut-upsuser] CyberPower DX600E won't switch up after power >> is back >> Message-ID: <3c530815d1ea602efdfec0d67eb1e**0b1 at secretfatty.net<3c530815d1ea602efdfec0d67eb1e0b1 at secretfatty.net> >> > >> Content-Type: text/plain; charset=UTF-8; format=flowed >> >> Hello >> I have an issue with an CyberPower DX600E, >> it doesn't switch up when the power is back; after it has been >> unloaded; >> is it because of one of those variables ? >> regards >> Franck >> >> #upsc myups >> battery.charge: 100 >> battery.charge.low: 10 >> battery.charge.warning: 20 >> battery.mfr.date: CPS >> battery.runtime: 1380 >> battery.runtime.low: 300 >> battery.type: PbAcid >> battery.voltage: 4.7 >> battery.voltage.nominal: 12 >> device.mfr: CPS >> device.model: DX600E >> 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: 0 >> input.transfer.low: 0 >> input.voltage: 230.0 >> input.voltage.nominal: 230 >> output.voltage: 238.0 >> ups.beeper.status: enabled >> ups.delay.shutdown: 20 >> ups.delay.start: 30 >> ups.load: 31 >> ups.mfr: CPS >> ups.model: DX600E >> ups.productid: 0501 >> ups.realpower.nominal: 360 >> ups.status: OL >> ups.timer.shutdown: -60 >> ups.timer.start: 0 >> ups.vendorid: 0764 >> >> >> > Am i suppose to run a "shutdown.return" command ? > > Does it make sense to do it in the script triggering (for example when > receiving "low battery" ? >depending on your exact OS / distros, this should be handled by NUT initscripts and probably the halt one. what is yours? some generic info on how shutdown works with NUT: http://www.networkupstools.org/docs/user-manual.chunked/ar01s06.html#Shutdown_design cheers, Arnaud -- NUT (Network UPS Tools) Project Leader - http://www.networkupstools.org Debian Developer - http://www.debian.org Free Software Developer - http://arnaud.quette.fr -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20121126/46bca19d/attachment.html>
> Date: Mon, 26 Nov 2012 19:34:28 +0100 > From: Arnaud Quette <aquette.dev at gmail.com> > To: Franck <franck at secretfatty.net> > Cc: nut-upsuser at lists.alioth.debian.org > Subject: Re: [Nut-upsuser] CyberPower DX600E won't switch up after > power > > > right. we need to monitor the UPS while it's shutting down... >Well I'd like to try that; but I'm 2000km from my UPS and It seems to be problematic for me to have the test done. But anyway I just got this reply to my quite random inquiry to CyberPower (wrong country) support: "I can only make vague guesses because I have never seen the product you have, and I am not familiar with the software you used to generate that data. The following values stand out to me. battery.voltage: 4.7 battery.voltage.nominal: 12 ups.load: 31 If I am interpreting them correctly your battery should be at 12 volts, but it is only at 4.7 volts? And the UPS load is 31%? If the battery is at 4.7 volts it will not pass the power on self-test. It needs to be somewhere above 10 volts (Perhaps 10.5 or 11)before it will pass the self-test and let the ups turn on. Other possibilities. If you have the computers set to auto start when power is restored, they will turn on simultaneously, if there has been a power loss that significantly drained the batteries, they will have very little energy when the power is restored. The power on self test checks the CyberPower?s ability to run on battery by stopping access to wall power and forcing the UPS on to battery power. If the batteries are very low and the auto startup of the computers hits while they are being tested then the load of the computers on the weak battery could cause the voltage to drop and the self-test would fail. One or both of your computers has an Active PFC power supply and your UPS is not a sine wave ups. If you are not familiar with this problem, just search the internet on the terms ?active pfc? and ?sine? The battery in the UPS could be defective. Again. I do not know the product you are asking about so I can?t provide an accurate diagnosis. I can only suggest possibilities. " So if the guy os right and this might be a battery problem.