[Nut-upsdev] Question about voltage threshold setting in NUT

[Shen Chuan]

Hey Charles,

Looks like after take out default.input.transfer.low, upsrw script *DOES*
work, the only thing for Eaton 3S 500 is that it is only accept certain
voltage values for input.transfer.low, 84v and 96v are two of them.
Otherwise the value never gets picked up.

Thank you for all your help

Shen


On Thu, Jun 5, 2014 at 12:07 PM, Shen Chuan <shen at minutekey.com> wrote:

> Hey Charles,
>
> Latest update. Looks like in ups.conf I setup default.input.transfer.low =
> 84. After I took that line out, restart upsdrvctl, upsmon, and upsd, the
> command of
>
> sudo upsrw -s input.transfer.low=70 -u * -p * ups
> return OK. Still need to verify if it works by using voltage regulator and
> will keep you updated.
>
> Thank you for your help
>
> Regards
>
> Shen
>
>
>
>
> On Thu, Jun 5, 2014 at 8:54 AM, Shen Chuan <shen at minutekey.com> wrote:
>
>> Hello Charles,
>>
>> Thank you so much for your help. Just run upsc and it is possible that
>> input.transfer.low is the one because we used power regulator to bring down
>> the power around 84v and then the ups sent the power loss message to PC. Do
>> you think some others may take effect for the low voltage? Just have the
>> upsc result attached.
>>
>> Then I retried input.transfer.low, default.input.transfer.low,
>> overwrite.input.transfer.low. Looks like it still can not write to those
>> params.
>>
>> $  sudo upsrw -s input.transfer.low=70 -u * -p * ups
>> Unexpected response from upsd: ERR READONLY
>>
>> $  sudo upsrw -s default.input.transfer.low=70 -u * -p * ups
>> Unexpected response from upsd: ERR VAR-NOT-SUPPORTED
>>
>> $ sudo upsrw -s overwrite.input.transfer.low=70 -u * -p * ups
>> Unexpected response from upsd: ERR VAR-NOT-SUPPORTED
>>
>> battery.charge: 100
>> battery.charge.low: 20
>> battery.runtime: 1087
>> battery.type: PbAc
>> device.mfr: EATON
>> device.model: Eaton 3S 550
>> device.serial: 000000000
>> device.type: ups
>> driver.name: usbhid-ups
>> driver.parameter.offdelay: 90
>> driver.parameter.ondelay: 120
>> driver.parameter.pollfreq: 30
>> driver.parameter.pollinterval: 2
>> driver.parameter.port: auto
>> driver.parameter.vendorid: 0463
>> driver.version: 2.6.5
>> driver.version.data: MGE HID 1.31
>> driver.version.internal: 0.37
>> input.transfer.high: 142
>> *input.transfer.low: 84*
>> outlet.1.desc: PowerShare Outlet 1
>> outlet.1.id: 2
>> outlet.1.status: on
>> outlet.1.switchable: yes
>> outlet.2.desc: PowerShare Outlet 2
>> outlet.2.id: 3
>> outlet.2.status: off
>> outlet.2.switchable: yes
>> outlet.desc: Main Outlet
>> outlet.id: 1
>> outlet.switchable: no
>> output.frequency.nominal: 60
>> output.voltage: 115.0
>> output.voltage.nominal: 115
>> ups.beeper.status: enabled
>> ups.delay.shutdown: 90
>> ups.delay.start: 120
>> ups.firmware: 02
>> ups.load: 23
>> ups.mfr: EATON
>> ups.model: Eaton 3S 550
>> ups.power.nominal: 550
>> ups.productid: ffff
>> ups.serial: 000000000
>> ups.status: OL CHRG
>> ups.timer.shutdown: 0
>> ups.timer.start: 0
>> ups.vendorid: 0463
>>
>> Thank you again for your help. Kind of running out of ideas.
>>
>> Regards,
>>
>> Shen
>>
>>
>>
>>
>> On Wed, Jun 4, 2014 at 9:24 PM, Charles Lepple <clepple at gmail.com> wrote:
>>
>>> On Jun 4, 2014, at 6:38 PM, Shen Chuan wrote:
>>>
>>> > $ sudo upsrw -s battery.charge.low=70 -u * -p * ups
>>> > OK
>>>
>>> Not sure this does what you originally asked, though.
>>>
>>> Does upsc show any settings related to sensitivity?
>>>
>>> --
>>> Charles Lepple
>>> clepple at gmail
>>>
>>>
>>>
>>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.alioth.debian.org/pipermail/nut-upsdev/attachments/20140605/2744f0a9/attachment-0001.html>