<br><br><div class="gmail_quote">2012/11/26 Franck <span dir="ltr"><<a href="mailto:franck@secretfatty.net" target="_blank">franck@secretfatty.net</a>></span><br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
On 2012-11-26 19:34, Arnaud Quette wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
2012/11/26 Franck <<a href="mailto:franck@secretfatty.net" target="_blank">franck@secretfatty.net</a> [4]><br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im">
On 2012-11-26 18:39, Arnaud Quette wrote:<br>
<br>
</div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hi Franck<br>
<br>
2012/11/23 Franck <<a href="mailto:franck@secretfatty.net" target="_blank">franck@secretfatty.net</a> [3] [3]><br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div class="h5">
Subject: [Nut-upsuser] CyberPower DX600E wont switch up after<br>
<br>
power<br>
is back<br>
Message-ID: <<a href="mailto:3c530815d1ea602efdfec0d67eb1e0b1@secretfatty.net" target="_blank">3c530815d1ea602efdfec0d67eb1e<u></u>0b1@secretfatty.net</a><br>
[1]<br>
[1]><br>
<br>
Content-Type: text/plain; charset=UTF-8; format=flowed<br>
<br>
Hello<br>
I have an issue with an CyberPower DX600E,<br>
it doesnt switch up when the power is back; after it has been<br>
<br>
unloaded;<br>
is it because of one of those variables ?<br>
regards<br>
Franck<br>
<br>
#upsc myups<br>
battery.charge: 100<br>
battery.charge.low: 10<br>
battery.charge.warning: 20<br>
battery.mfr.date: CPS<br>
battery.runtime: 1380<br>
battery.runtime.low: 300<br>
battery.type: PbAcid<br>
battery.voltage: 4.7<br>
battery.voltage.nominal: 12<br>
device.mfr: CPS<br>
device.model: DX600E<br>
device.type: ups<br>
</div></div><a href="http://driver.name" target="_blank">driver.name</a> [2] [2]: usbhid-ups<div><div class="h5"><br>
<br>
driver.parameter.pollfreq: 30<br>
driver.parameter.pollinterval: 2<br>
driver.parameter.port: auto<br>
driver.version: 2.4.3<br>
driver.version.data: CyberPower HID 0.3<br>
driver.version.internal: 0.34<br>
input.transfer.high: 0<br>
input.transfer.low: 0<br>
input.voltage: 230.0<br>
input.voltage.nominal: 230<br>
output.voltage: 238.0<br>
ups.beeper.status: enabled<br>
ups.delay.shutdown: 20<br>
ups.delay.start: 30<br>
ups.load: 31<br>
ups.mfr: CPS<br>
ups.model: DX600E<br>
ups.productid: 0501<br>
ups.realpower.nominal: 360<br>
ups.status: OL<br>
ups.timer.shutdown: -60<br>
ups.timer.start: 0<br>
ups.vendorid: 0764<br>
</div></div></blockquote><div><div class="h5">
<br>
Am i suppose to run a "shutdown.return" command ?<br>
<br>
Does it make sense to do it in the script triggering (for<br>
example<br>
when receiving "low battery" ?<br>
</div></div></blockquote><div><div class="h5">
<br>
depending on your exact OS / distros, this should be handled by<br>
NUT<br>
initscripts and probably the halt one.<br>
what is yours?<br>
</div></div></blockquote><div><div class="h5">
<br>
Thanks for your reply Arnaud;<br>
I have a debian squeeze.<br>
</div></div></blockquote><div><div class="h5">
<br>
looking again at your upsc output, I suspect more an issue with the<br>
UPS than with Squeeze.<br>
<br>
a good test would be to:<br>
- remove your PC from the UPS,<br>
</div></div></blockquote>
<br>
Just to check I understood well:<br>
You mean I would plug the PC directly to the power source, and connect the UPS with the PC only using the USB ?</blockquote><div><br>right. we need to monitor the UPS while it's shutting down...<br> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="im">
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
- stop NUT after the reboot,<br>
- restart the driver in debug more (/lib/nut/usbhid-ups -DDDDD myups)<br>
and upsd (simply type "upsd") in another term<br>
- then execute "upscmd -u ... -p ... myups shutdown.return"<br>
- leave it half a minute, then Ctrl+C in the driver term.<br>
and send back the driver output, in compressed form.<br>
you can then restart everything as usual...<br>
<br>
Id like to see how the data behind "ups.timer.shutdown" and<br>
"ups.timer.start" behave.<br>
<br>
</blockquote>
<br></div></blockquote><div><br>-- Arno <br><br></div></div><br>