similar to: driver.parameter.offdelay vs ups.delay.shutdown / driver.parameter.ondelay vs ups.delay.start

Thanks On Sat, 16 Mar 2024 at 18:57, Charles Lepple <clepple_at_gmail.com_chribonn at duck.com> wrote: > > On Mar 14, 2024, at 11:41?AM, Alan via Nut-upsuser <nut-upsuser at alioth-lists.debian.net> wrote: > > > Hi, > > > > My Cyber Power reports these two values. Each pair has the same value. > > > > Would they normally be the same thing? >

Hello there. Have been experimenting with an APC Smart-UPS 1500 RM and would like to share the results of my research. I hope this could be of help to people having this kind of units. I would also like to give something back to the NUT community. :) Here are the details of the unit in question (a 1500 VA rack mountable one): Model: Smart-UPS 1500 RM Firmware revision: 617.3.I USB firmware

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

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

Dear All, I am running Slackware64-14.1(Linux marto 3.10.17 #1 SMP Fri Feb 14 16:39:21 CST 2014 x86_64 Intel(R) Pentium(R) CPU G3250 @ 3.20GHz GenuineIntel GNU/Linux) with kernel 3.10.17 and nut package nut-2.6.5-x86_64-1_SBo, buit from source using the build script http://slackbuilds.org/repository/14.1/system/nut/ In the README.Slackware it is suggested that the commands for killing the

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

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

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

W dniu 24.08.2018 o 13:10, Charles Lepple pisze: > Sorry, I didn't mean to imply that the master branch was necessarily going to be different, just wanted to make sure you had everything set up to recompile. The real test is to see if things change after commenting out that line (such as by changing it to start with "//"): > > // { "shutdown.return", 0, 0,

On Wed, 4 Jun 2014, Mick wrote: >> Some of the variables (those with HU_FLAG_ABSENT) are apparently not stored >> on the UPS itself-- they are sent to the UPS when the shutdown command is >> executed. Sending the value starts the timer, in some cases, but I think >> the ups.delay.start value should be safe to send at the time when it is >> set. > > I see. So if

Hi there, I just purchased a CyberPower BR850ELCD and while setting NUT up with the install instructions from the homepage was pretty straightforward, and the UPS was detected by the usbhid-ups driver, I'm having problems getting the UPS to work properly. First issue: whatever I set as the offdelay, seems to be ignored and the UPS just cuts the power about 2sec after receiving the

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

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

Are there plans to change the default offdelay/ondelay for the Windows versions of NUT since it can't be invoked at the end of shutdown? E.g. I have a Win2k3 server that takes just over 4min to shut down, so I set my offdelay to 600 (ondelay is +15 that) to be extra safe. Maybe a 2 min by default would be good? Most (all?) APC non-smart UPS's are hard-coded at an annoying 1min delay,

Welcome, Acctualy, I'm try to poweroff my ESXi (6.7). Virtual machine with Ubuntu and redirected USB port with APC Back UPS CS 650, have nut-server and send info to ESXi. When battery is low, ESXi poweroff gracefully all VM and same ESX go down. This work fine and don't have any problem. But important to me, is set to more offdelay on UPS than the default 60 sec. (cut off power socket

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.

On Jan 21, 2015, at 9:15 AM, Sebastian Hosche <sebastian.hosche at web.de> wrote: > Hi there, > > I just purchased a CyberPower BR850ELCD and while setting NUT up with the install instructions from the homepage was pretty straightforward, and the UPS was detected by the usbhid-ups driver, I'm having problems getting the UPS to work properly. > > First issue: whatever I

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

> When a UPS unit performs a delayed power off (NUT sets the delay to 20 seconds > by default) it deconnects its power outlets which in some UPS units produces an > audible "clunk". The display of lights on the front panel changes, and the > beeping stops. The delayed power off can be demonstrated with a light bulb or a > mains circuit tester connected to one of the

W dniu 22.08.2018 o 14:41, Charles Lepple pisze: > /lib/nut/usbhid-ups -a apc -DDD -k Please see attachement. -- Karol Olszewski ipflow.pl -------------- next part -------------- A non-text attachment was scrubbed... Name: APC_BackUPS_CS_650_fsd.log.gz Type: application/gzip Size: 5735 bytes Desc: not available URL: