similar to: Question about voltage threshold setting in NUT

On Jun 3, 2014, at 5:16 PM, Shen Chuan wrote: > We have an Eaton 3S 550 UPS using NUT tool to send power loss event. By default the power voltage threshold is set to 85 volts. If the voltage is less than 85 volts, it will trigger ONBATT event from NUT. Is there a way in NUT we can change the threshold from 85 volts to a lower voltage like 40 volts? It might be possible with upsrw - try

Hello Charles, Thank you so much for your reply. Yes. 40v was too low. In windows, those range started from 76v, 85v, and 96v. Just tried upsrw command to modify input.transfer.low and input.transfer.boost.low. There were some error messages returned. Tried another one battery.charge.low and it returns ok. $ sudo upsrw -s input.transfer.low=70 -u * -p * ups Unexpected response from upsd: ERR

Hello, We have an Eaton 3S 550 UPS using NUT tool to send power loss event. By default the power voltage threshold is set to 85 volts. If the voltage is less than 85 volts, it will trigger ONBATT event from NUT. Is there a way in NUT we can change the threshold from 85 volts to a lower voltage like 40 volts? We were trying to change ups.conf to modify the output of upsc ..., but looks like it

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,

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,

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

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

On Jun 5, 2014, at 10:53 PM, Charles Lepple wrote: > As you have seen, the "default.*" and "overwrite.*" names are not actual variables: they are configuration options to change what is returned from upsc. That is why you get VAR-NOT-SUPPORTED. typo; should have been "override.*" -- Charles Lepple clepple at gmail

Hello Charles, Thank you for your reply. For the discrete value thing, this morning I did try to run sudo upsrw -s input.transfer.low=x -u * -p * ups I changed "x" value from 60 to 96 then checked upsc result. All the script return OK but only 84 and 96 got picked up and working. Out model is Eaton 3S 500. And in windows it has a Eaton Personal Solution Pac. In Battery transfer

On Jun 5, 2014, at 4:22 PM, Shen Chuan wrote: > 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. As you have seen, the "default.*" and "overwrite.*" names are not actual

Hello Charles, Thank you for your comment. Just tried to use ups.delay.shutdown to postpone the UPS shutdown. The thing is that if the PC shutdown first, then the UPS, it wasn't able to send "shutdown.reboot" any more because everything is power off after the UPS shuts down. Also play on the watchdog for Tripp Lite. Looks like it has the command of reset.watchdog but not

On Dec 1, 2014, at 4:11 AM, Victor Porton <porton at narod.ru> wrote: > battery.voltage: 13.70 > battery.voltage.high: 13.00 > battery.voltage.low: 10.40 These are the voltage thresholds for the UPS, so theoretically the UPS will send the LB signal when the battery voltage goes lower than 10.40 Volts. Also, if battery.charge works, you can use "ignorelb" if you want to

[updated] OpenBSD 6.1/amd64 NUT 2.7.4p0 (from OpenBSD package) Results of upsc: battery.charge: 100 battery.charge.low: 10 battery.charge.warning: 20 battery.mfr.date: CPS battery.runtime: 2902 battery.runtime.low: 300 battery.type: PbAcid battery.voltage: 26.9 battery.voltage.nominal: 24 device.mfr: CPS device.model: CP1500AVRLCDa device.serial: CTHGN200xxxx device.type: ups driver.name:

Hello, We are trying to develop a mechanism to power cycle Tripp Lite UPS. When we checked the upscmd, looks like the only command we can use is shutdown.reboot(sudo upscmd -u user -p password ups shutdown.reboot). Because the PC is connected to UPS directly and we would prefer shutdown PC before power cycle the UPS. But if we run shutdown PC first it won't run the power cycle the UPS script

Hello, We are trying to develop a mechanism to power cycle Tripp Lite UPS. When we checked the upscmd, looks like the only command we can use is shutdown.reboot(sudo upscmd -u user -p password ups shutdown.reboot). Because the PC is connected to UPS directly and we would prefer shutdown PC before power cycle the UPS. But if we run shutdown PC first it won't run the power cycle the UPS script

On 5/21/2017 10:39 AM, Charles Lepple wrote: > Mike, > > Thanks for the info. I have enough to add an entry to the DDL, but I have a few more questions inline. > > On May 14, 2017, at 1:21 PM, Mike wrote: >> >> [updated] >> >> OpenBSD 6.1/amd64 >> NUT 2.7.4p0 (from OpenBSD package) >> >> >> Results of upsc: >> >>

01.12.2014, 06:18, "Charles Lepple" <clepple at gmail.com>: > On Nov 29, 2014, at 7:32 AM, Victor Porton <porton at narod.ru> wrote: >> ?On Debian Linux jessie: >> >> ?After buying an UPS and installation of nut-server and nut-client at my PC and configuring the ports and the protocol, do I need to adjust time and/or percentage parameters, to be sure my

At the company I work for, we are using many TrippLite OMNI900LCD UPSs and are having difficulty setting the lower transfer threshold voltage. On our other model, the Eaton MGE-3S550, this can be set using upsrw to set the input.transfer.lowsetting, but on the Omni900, this option is not available. In our testing, it defaults to ~95v but we want to set it to 84v. More info: - OS = OpenSuse 13.1 -

[moving this to nut-upsuser, since other users of Tripp Lite equipment may have specific experience with this.] On Jun 17, 2014, at 7:51 PM, Shen Chuan <shen at minutekey.com> wrote: > We are trying to develop a mechanism to power cycle Tripp Lite UPS. When we checked the upscmd, looks like the only command we can use is shutdown.reboot(sudo upscmd -u user -p password ups

For my Smart 2200, a charged battery string is anywhere between 25.6 and 26.8 volts. I'm seeing nut report 13.0 volts, which seems suspicious. Even if the UPS were reporting half of the actual battery voltage to keep protocol compatibility with models having a 12V battery system, the value of exactly 13.0 seems unlikely. According to the page at