[Nut-upsuser] CyberPower DX600E won't switch up after power

[Franck]

On 2012-11-26 19:34, Arnaud Quette wrote:
> 2012/11/26 Franck <franck at secretfatty.net [4]>
>
>> On 2012-11-26 18:39, Arnaud Quette wrote:
>>
>>> Hi Franck
>>>
>>> 2012/11/23 Franck <franck at secretfatty.net [3] [3]>
>>>
>>>>> Subject: [Nut-upsuser] CyberPower DX600E wont switch up after
>>>>>
>>>>> power
>>>>>         is back
>>>>> Message-ID: <3c530815d1ea602efdfec0d67eb1e0b1 at secretfatty.net
>>>>> [1]
>>>>> [1]>
>>>>>
>>>>> Content-Type: text/plain; charset=UTF-8; format=flowed
>>>>>
>>>>> Hello
>>>>> I have an issue with an CyberPower DX600E,
>>>>> it doesnt 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 [2] [2]: 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?
>>
>> Thanks for your reply Arnaud;
>> I have a debian squeeze.
>
> looking again at your upsc output, I suspect more an issue with the
> UPS than with Squeeze.
>
> a good test would be to:
> - remove your PC from the UPS,

Just to check I understood well:
You mean I would plug the PC directly to the power source, and connect 
the UPS with the PC only using the USB ?

> - stop NUT after the reboot,
> - restart the driver in debug more (/lib/nut/usbhid-ups -DDDDD myups)
> and upsd (simply type "upsd") in another term
>  - then execute "upscmd -u ... -p ... myups shutdown.return"
> - leave it half a minute, then Ctrl+C in the driver term.
> and send back the driver output, in compressed form.
> you can then restart everything as usual...
>
> Id like to see how the data behind "ups.timer.shutdown" and
> "ups.timer.start" behave.
>


---
http://secretfatty.net