search for: minutekey

...thing 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 enable.watchdog. Do you guys know the command to enable the watchdog for Tripp Lite UPS(TrippLite HID 0.8)? Thank you so much for your help Regards Shen Minutekey Inc On Wed, Jun 18, 2014 at 7:03 AM, Charles Lepple <clepple at gmail.com> wrote: > [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:...

...utdown PC before power cycle the UPS. But if we run shutdown PC first it won't run the power cycle the UPS script any more. Wonder if there is a delaed power cycle command for Tripp Lite to give PC some time to shutdown itself? Attached the upscmd -l and upsc ups. Thank you for your help Shen Minutekey Inc sudo upscmd -l ups beeper.disable - Disable the UPS beeper beeper.enable - Enable the UPS beeper beeper.mute - Temporarily mute the UPS beeper beeper.off - Obsolete (use beeper.disable or beeper.mute) beeper.on - Obsolete (use beeper.enable) load.off - Turn off the load immediately load.off.de...

...utdown PC before power cycle the UPS. But if we run shutdown PC first it won't run the power cycle the UPS script any more. Wonder if there is a delaed power cycle command for Tripp Lite to give PC some time to shutdown itself? Attached the upscmd -l and upsc ups. Thank you for your help Shen Minutekey Inc sudo upscmd -l ups beeper.disable - Disable the UPS beeper beeper.enable - Enable the UPS beeper beeper.mute - Temporarily mute the UPS beeper beeper.off - Obsolete (use beeper.disable or beeper.mute) beeper.on - Obsolete (use beeper.enable) load.off - Turn off the load immediately load.off.de...

[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 shutdown.reboot). Because the PC is connected to UPS directly and we would prefer shutdo...

...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...

...t = nut-2.6.5-6.1.5.x86_64 (installed package from repo) - Driver = usbhid-ups - UPS = TrippLite OMNI900LCD Are there other ways to set this value, or other drivers to try? We would like to avoid writing a middleware layer to support this feature. Thanks much, Todd Bernhard *Software Engineer* *MinuteKey, Inc* -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20140611/3a9e6ec3/attachment.html>

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,

...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...

On Thu, Jan 8, 2015 at 11:37 PM, Charles Lepple <clepple at gmail.com> wrote: > Although this tends to happen more with x86 systems and/or USB3, you might want to see if the disconnects are less frequent with a shorter or higher-quality USB cable. The more I look into this ... the more I think that it's exclusively Tripp-Lite weirdness! There are some things that I explored as far

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 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

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 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