similar to: Delayed UPS start up after shutdown?

Hi, I own one a MGE Protection Center 675. You can change the parameter ups.delay.start into your UPS to set the "Interval to wait before (re)starting the load (seconds)" use upsset to change the value. Regards, Ren? Le 2013-12-06 15:14, Angel Tsankov a ?crit : > Hello. > > I am faced with a configuration where the OS (Debian 6.0.8) and the PC > shut down before

Hello, Ren?. > You can change the parameter > ups.delay.start into your UPS to set the "Interval to wait before > (re)starting the load (seconds)" > > use upsset to change the value. So far, the ups.delay.start parameter in my MGE Protection Center 675 has always been equal to the driver.parameter.ondelay parameter (which equals the ondelay argument in ups.conf).

> Le 2013-12-06 15:14, Angel Tsankov a ?crit?: > ...if main power comes back within 10 seconds after the UPS has been > shut down, the UPS will power up the PC but the latter will not start. On Fri, 6 Dec 2013, Rene Garcia wrote: > .... You can change the parameter ups.delay.start into your UPS to set > the "Interval to wait before (re)starting the load (seconds)" >

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

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

Angel Tsankov wrote, On 12/6/2013 12:31 PM: > Hello, Ren?. > >> You can change the parameter >> ups.delay.start into your UPS to set the "Interval to wait before >> (re)starting the load (seconds)" >> >> use upsset to change the value. > > So far, the ups.delay.start parameter in my MGE Protection Center 675 > has always been equal to the

On 12/25/2013 12:16 AM, Kris Jordan wrote: > Angel Tsankov wrote, On 12/24/2013 1:22 AM: [...] >> I can see that my UPS (MGE Protection Center 675) has a parameter >> ups.timer.start (currently holding the strange value of -10). Any idea >> if this could help and how this parameter can be changed? > > in upsrw? In upsc only. Here's the complete output:

On 12/25/2013 11:42 PM, Kris Jordan wrote: > Angel Tsankov wrote, On 12/25/2013 12:16 AM: >> >> What did you mean by "load.on.delay"? > > upscmd -l <ups> > > load.on.delay - Turn on the load with a delay (seconds) Alright, but... how does this command work? Once it has been executed, will the UPS wait the specified period before turning the load on

Angel Tsankov wrote, On 12/25/2013 12:16 AM: > > What did you mean by "load.on.delay"? > upscmd -l <ups> load.on.delay - Turn on the load with a delay (seconds) ---- ups.timer.shutdown: 0 ups.timer.start: 0 are my upsc values. I'll have to pay more attention to those next time I test.

Hi there, I've replaced yesterday my old UPS with a brand new "Eaton Ellipse MAX 600 USBS". I've choosed the Eaton (previously MGE) both because I've always been extremely satisfied with MGE UPSes of all kinds at work, and because of the involvement of MGE (with Arnaud) in nut development, which made me quite sure that I would have no trouble with an Eaton (MGE) UPS and

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.

2018-02-28 21:11 GMT+01:00 Jairo Rotava <jairo.rotava at gmail.com>: > Hello, > > I think that on this file nutdrv_qx_megatec.c the definition for > shutdown.stayoff may be wrong. In the file the definition is "S%sR0000\r"m > while on the megatec protocol description ( > http://networkupstools.org/protocols/megatec.html) the command is just > "S%s\r".

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

Since there is apparently no immediate solution to upsstats.cgi not reading the output voltage correctly, I have moved on to trying to use upsset.cgi. To recap the UPS is a CyberPower CyberPower CP1500PFCLCD UPS running on a headless server running Slackware 14.1 with the 3.10.7 kernel. The version of NUT is 2.71 and I am using usbhid-ups for communication with the UPS The problem is that when

I have an Ellipse USBS connected via serial cable to a CentOS 3 box. Do I need to turn off the UPS as the final stage of shutdown, or will the UPS power itself off, before the battery reaches a level to low to safely recharge from? I notice there is the option for the UPS to turn itself off (and on again) unattended if power is restored during shutdown, but there doesn't seem to be an option

On Jul 31, 2013, at 3:36 AM, Pavel Potcheptsov (EKTOS) wrote: > Does it looks good? I think so - 40.8 volts with a nominal of 36 volts is 13.6 V/cell, which agrees with the 100% charge value. Hopefully the line voltages and frequency make sense for your region. > Another question what does riello experimental driver warning mean? We add that to all new drivers. This driver was written by

Thank you very much!! I have tried configure downloaded source with # ./configure --with-user=_ups --with-group=_ups --with-statepath=/var/db/nut/ and then build driver and copy again. but this doesn't help (driver pid still in the /var/state/ups). Maybe I must add more arguments to change driver's pid location, but I did next, I changed this argument in openbsd ports: # pkg_delete nut #

Answers bellow. 2018-02-28 1:41 GMT-03:00 Daniele Pezzini <hyouko at gmail.com>: > 2018-02-27 14:51 GMT+01:00 Jairo Rotava <jairo.rotava at gmail.com>: > > Hi, > > > > I had an issue where after returning the power from a shutdown.return the > > ups would do another shutdown.return during the boot, and kept this > forever. > > After some

I'm access nut online via localhost. But I have the following problems. When I click on Statistics I get cannot open /etc/hosts.conf. When I click on settings I get: Error: Can't open upsset.conf to verify security settings. Refusing to start until this is fixed. I have .htaccess in cgi-bin with the following: <Files upsset.cgi> deny from all allow from 127.0.0.1 </Files>

Hello, looking for replacements for some older Powerware equipment I found the MGE Pulsar Extreme 1000C and I'm currently testing one with nut-2.0.3 on a self-brewn i386-linux. Upto now everything seems to work fine - except I can't get the power outlets switching on again after mains returns. As this works with Personal Solution-Pac 2 on W2k I thought that there might be a way to