search for: offdelay

...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 revision: 1.5 Manufacturing date: 2003/06/03 The unit can be monitored with NUT, no problem at this. But when turning it off an back on, the "offdelay" and "ondelay" parameters from "ups.conf" aren't honored. This unit uses a different HID path than the stardard one for sending a "load.on.delay" command. As the driver (usbhid-ups) can't find this command, it has to revert to rebooting the UPS. The HID p...

...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 when time is up from FSD command). file ups.conf [apc]         driver = usbhid-ups         port = auto         desc = "APC"         override.battery.charge.low = 90         offdelay = 90         ondelay = 120 UPS always cut off power...

...old off the load indefinitely (and it's also stated in nutdrv_qx's manpage, 'Known problems' section). > When I changed it my system was abe to at least stay off, and stopped making > an instant power recycling. Try the following things and let's see what happens: - 'offdelay=30', 'ondelay=0' (the driver will send 'S.5' to the device), - 'offdelay=120', 'ondelay=0' (the driver will send 'S02' to the device), - 'offdelay=30', 'ondelay=180' (the driver will send 'S.5R0003' to the device), - 'offdelay=...

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,

...ho "Unmounting local file systems." /bin/umount -v -a -t no,proc,sysfs ... I also set in the ups.conf file that the UPS should be killed 3 minutes after issuing the kill inverter command: # ups.conf [Eaton5E650iUSB] driver = usbhid-ups port = auto desc = "UPS Eaton5E650iUSBDIN" offdelay=180 ondelay=200 On power failure the shutdown process reaches the kill inverter commands in rc.6, issues them and in several seconds shuts down the UPS, obviously ignoring the offdelay setting. Furthermore, it does not proceed to issue the remaining rc.6 commands, but seems to hang at shutting dow...

...3 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 offdelay has elapsed. To me it seems intuitive to restore power only after ondelay has elapsed no matter if main power has come back before or after offdelay. I can see that my UPS (MGE Protection Center 675) has a par...

...k and detailed reply! I've added my answers and details inline. Sorry this reply wasn't as quick. > On 22.1.2015 04:46, Charles Lepple wrote: >> On Jan 21, 2015, at 9:15 AM, Sebastian Hosche <sebastian.hosche at web.de> wrote: >>> First issue: whatever I set as the offdelay, seems to be ignored and the UPS just cuts the power about 2sec after receiving the shutdown command. >> What values have you tried? I wonder if it is rounding down to 0 seconds. > Great idea! I did some testing and it appears anything lower than 60 for offdelay simply gets ignored. In fac...

...ged the ondelay argument in ups.conf (and restarted NUT) the above > parameters have always been set equal to ondelay. Therefore, I would > assume that ups.delay.start cannot help. Do you have any reason to > consider this assumption might be wrong? ondelay maps to ups.delay.start, and offdelay maps to ups.delay.shutdown. offdelay needs to be greater than ondelay. I'm using 600 & 615 on a Win2k3 server I have connected to an Evolution 850. If the power comes back on during the offdelay period, the ups will do a reboot cycle with a 15s wait. If the power is off for more than o...

...7 PM, Karol Olszewski <karol.olszewski at ipflow.pl> wrote: > > I'm send debug file /lib/nut/usbhid-ups -a apc -DDD in attachement. > I tested two different ones APC BackUPS CS 650 and on both problem occurred. > I borrowed PowerWalker (driver blazer_usb), and all function + offdelay, > ondelay works perfectly. unfortunately, it looks like there are several different places where the offdelay value could be applied: 1.478906 Report[get]: (3 bytes) => 26 00 00 1.478968 Path: UPS.Output.APCShutdownAfterDelay, Type: Feature, ReportID: 0x26, Offset: 0, Size: 16, Value...

...shutdown.return", 0, 0, "UPS.Output.APCDelayBeforeShutdown", NULL, "120", HU_TYPE_CMD, NULL }, Now, UPS shutdown after 120sec from FSD command, and start from hibernation automaticaly when power is back. Excelent! (I tested 120,180,300 all work) I'm try to set DEFAULT_OFFDELAY and define in ups.conf time to poweroff (offdelay and ondelay), but this is not work. UPS set to poweroff after ~20sec I think this line set to 20sec off time: usbhid-ups.h:#define DEFAULT_OFFDELAY   "20"    /* Delay before power off, in seconds */ Where DEFAULT_OFFDELAY is change to va...

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

...Charles, Thanks so much for your quick and detailed reply! I've added my answers and details inline. On 22.1.2015 04:46, Charles Lepple wrote: > On Jan 21, 2015, at 9:15 AM, Sebastian Hosche <sebastian.hosche at web.de> > wrote: > >> First issue: whatever I set as the offdelay, seems to be ignored and >> the UPS just cuts the power about 2sec after receiving the shutdown >> command. > > What values have you tried? I wonder if it is rounding down to 0 > seconds. Great idea! I did some testing and it appears anything lower than 60 for offdelay sim...

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

...> [...] >> (*) 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 offdelay has elapsed. To me it seems intuitive to restore power > only after ondelay has elapsed no matter if main power has come back > before or after offdelay. Depends a lot on the UPS's firmwar...

Hi, My Cyber Power reports these two values. Each pair has the same value. Would they normally be the same thing? Thanks Alan

...s. Each pair has the same value. > > > > Would they normally be the same thing? > > Without any intervening `upsrw` changes, yes. `driver.parameter.*` corresponds to the initial value from ups.conf or `-x` command-line flags. > > For usbhid-ups (and a few other drivers), the offdelay parameter sets ups.delay.shutdown when the driver starts: > > https://github.com/networkupstools/nut/blob/v2.8.1/drivers/usbhid-ups.c#L1300-L1306 > > and likewise for ondelay and ups.delay.start. > > -- > Charles Lepple > clepple at gmail > > > Nut-upsuser mailing l...

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:

...gt; 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 shutdown command. What values have you tried? I wonder if it is rounding down to 0 seconds. > Second issue: When the UPS is on battery power and I issue the shutdown, it goes off, but after about 15sec it comes...

...oday github sync and compile (Ubuntu 18.04): Network UPS Tools - Generic HID driver 0.42 (2.7.4-490-g5dc80953) /lib/nut/usbhid-ups -a apc -DDD -k  > Log attachement. root at vbox1804:/home/karol# upsc apc at localhost | grep driver.param Init SSL without certificate database driver.parameter.offdelay: 90 driver.parameter.ondelay: 120 driver.parameter.pollfreq: 30 driver.parameter.pollinterval: 2 driver.parameter.port: auto driver.parameter.synchronous: no UPS cut off power after 60sec after FSD command from driver, when power back start after ~2sec. -- Karol Olszewski ipflow.pl ------------...

...al machine, NUT installed using apt. I configured NUT to run as a netserver, installed the ESXi nut .vib, configured the shutdowncmd in the VM to do nothing, so that the ESXi host would close that virtual machine last and only before it would shut down, it would call the poweroff command. I set the offdelay option of the ups to 300s and ondelay option to 600s and here comes in my problem, whenever the battery.low condition or the upssched script calls the FSD action, everything will beging to shut down normally, except that the UPS will turn off the load in about 100 seconds (while the ESXi host still...