similar to: No run cmd /usbhid-ups -k !

Set with upsrw: ups.delay.shutdown=60 is the same as offdelay = 30. This time was done correctly by UPS. Set with upsrw: ups.delay.start=90 is the same as ondelay = 40. The UPS shut down and reset and forget about the settings. If I use the program in Win 10 settings in the program from Eaton are stable!? Jan. > -----Original Message----- > From: Nut-upsuser

I used strace and the result is bus is busy: clock_gettime(CLOCK_MONOTONIC, {8158, 708518222}) = 0 timerfd_settime(11, TFD_TIMER_ABSTIME, {it_interval={0, 0}, it_value={8159, 708518000}}, NULL) = 0 ioctl(12, USBDEVFS_SUBMITURB, 0x40810) = 0 poll([{fd=7, events=POLLIN}, {fd=9, events=POLLIN}, {fd=11, events=POLLIN}, {fd=12, events=POLLOUT}], 4, 60000) = 1 ([{fd=12, revents=POLLOUT}]) ioctl(12,

Good day. Can not perform shutdowns Ups. Please help. Details of our installation are: OS: Turris Omnia (TO) NUT version: 2.7.4-5 Installation method: from package UPS device: EATON UPS 5SC 500i , 230V, 350W, 500VA, USB bought in jun 2018 If you connect to TO UPS via USB, the /dev/hidraw0 device will be created. No any programs from NUT package is not running. When I run: /lib/nut/usbhid-ups

On 01/07/2018 11.53, icingaj at gmail.com wrote: > Good day. > > Can not perform shutdowns Ups. Please help. > > Details of our installation are: > OS: Turris Omnia (TO) > NUT version: 2.7.4-5 > Installation method: from package > UPS device: EATON UPS 5SC 500i , 230V, 350W, 500VA, USB bought in jun 2018 > > If you connect to TO UPS via USB, the /dev/hidraw0

On Tue, 3 Jul 2018, rakoi at mail.telekom.sk wrote: > UPS is Eaton 5SC 500i. > Please do not know how to write some parameters permanently to UPS? Read man ups.conf and man usbhid-ups and try setting the required values in ups.conf. For example [Eaton] driver = usbhid-ups port = auto desc = "Eaton 5sc 500i" offdelay = 30 ondelay =

I'm trying to setup a server controlling 8 ups, 6 APC Smartups 1500 and two 1000. Because of the number of ups, i connected them using usb cables. I'm using Debian Etch AMD64 and nut 2.2.0 from testing (already tried 2.0 from stable, but had problems reading the ups serials and all the following problems of 2.2). This is my ups.conf: [ups2] driver = usbhid-ups port =

Angel Tsankov wrote, On 12/24/2013 1:22 AM: > On 12/06/2013 10:57 PM, Kris Jordan wrote: > > [...] >> (*) Some UPS's do provide extra options to determine when they will >> restore power to load. > > That would be a nice feature. > > Anyway, it is a strange thing that I can set the waiting time for > power to be restored if main power comes back before

Hi, I'm struggling with a peculiar issue with my UPS. After a power outage, the devices powered by it properly shut down via nut. Eventually, the UPS also goes down. Power is still out, however, roughly 40 seconds after the UPS shut down, it turns back on and it starts supplying power to the load, thus turning back on the devices attached to it. This is obviously not something I want. In

Are there any plans to allow us to specify UPS variables in ups.conf, eg: [evo_s_3000] driver = usbhid-ups port = auto desc = "Eaton Evolution S 3000" vendorid = 0463 productid = ffff ups.delay.shutdown = 120 ups.delay.start = 130 The reason I ask is that I'm using FreeBSD & gmirror and need to extend the gracetime

After issuing this command: /upsrw -s ups.delay.shutdown=180 -u admin -p mypassword myups /I obtain this error:/ Unexpected response from upsd: ERR READONLY /After issuing this command:/ upsrw myups /I obtain no output./ /In my /upsd.users/ file I have these settings: /[admin]// //password = mypassword// //actions = SET// //instcmds = ALL// // //[myuser]// //password = mypassword//

Greetings Charles; I hope you had a nice Christmas, and will have a happy and prosperous new year in 2016. You mentioned upsrw in a message earlier, so I ran it, and found the shutdown timeout was only 20 seconds. gene at coyote:~$ upsrw myups [input.transfer.high] High voltage transfer point (V) Type: STRING Value: 140 [input.transfer.low] Low voltage transfer point (V) Type: STRING Value:

On Tue, Oct 2, 2018 at 3:59 PM Charles Lepple <clepple at gmail.com> wrote: > > On Sep 27, 2018, at 6:59 PM, Gabriel <jarod125 at gmail.com> wrote: > > > > Hi, > > > > I'm struggling with a peculiar issue with my UPS. After a power > > outage, the devices powered by it properly shut down via nut. > > Eventually, the UPS also goes down.

The REDi Blazer 600VA (BLAZER600c) UPS found here [ro_RO]: http://www.emag.ro/ups-redi-blazer-600va-blazer600c/pd/EX5X2BBBM/ which is actually a Centralion Blazer 600VA [en_TW]: http://www.centralion.com/html/product/back-Product-ups-blazer400.htm works with the blazer_ser driver ----------shell output---------- # upsrw ups # upscmd -l ups Instant commands supported on UPS [ups]: beeper.toggle -

On 12/06/2013 10:57 PM, Kris Jordan wrote: > [...] > (*) Some UPS's do provide extra options to determine when they will > restore power to load. That would be a nice feature. Anyway, it is a strange thing that I can set the waiting time for power to be restored if main power comes back before offdelay has elapsed, but the UPS ignores this setting if main power comes back after

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,

while finishing some work on the HAL integration (I'm now mapping DBus method with NUT commands, to allow at least the final UPS poweroff), I was horrified to realize (and so late) the changes in usbhid-ups->upsdrv_shutdown(). We've lost a lot there, but making a generic code, instead of keeping the subdrivers delegation. For example, the shutdown.return command (which is or should be

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,

An HTML attachment was scrubbed... URL: <http://alioth-lists.debian.net/pipermail/nut-upsuser/attachments/20200217/b486de30/attachment.html> -------------- next part -------------- A non-text attachment was scrubbed... Name: usbhid.zip Type: application/zip Size: 4031 bytes Desc: not available URL:

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

Hi, I am trying to talk to an MGE Pulsar Extreme UPS over RS232 with the mge-shut driver but I'm having some problems. It appears to init OK but I can't, say, turn the outlets off, eg.. harrow:~>upsc mge@localhost battery.charge: 78 battery.charge.low: 20 battery.runtime: 05760 driver.name: mge-shut driver.parameter.port: /dev/cuad1 driver.version: 2.0.3 driver.version.internal: 0.65