search for: stayoff

Nut-names.txt states that 1. ups.start.auto controls whether the UPS starts when mains is (re)applied. 2. shutdown.stayoff causes "turn off the load possibly after a delay and remain even if power returns". 3. shutdown.return causes "turn off the load possibly after a delay and return when power is back". 1 seems to conflict with 2 and 3. That is, 2 implies that ups.start.auto=no and 3 impl...

...ty is missing, the system is automatically turned off, the load is disconnected for a few seconds and then reloaded when power returns. If you instead turn off the system normally (manually), the UPS remains always with the load on. I would instead that the load should be permanently disconnected (stayoff) both in the case of a normal shutdown that in the case of a shutdown due to a lack of electric current. Basically I want the UPS, after those operations, switches in the state where only recharges the battery (with the load off). How to do? I hope I was clear enough despite my poor English. Tha...

...up that the UPS manufacturer is using can't handle any values. To this end it appears that they use different Descriptor Indexes to acieve the desired effects. 0x18 Performs a shutdown.return with 30s delay and 10s delay before restart 0x1a Cancels the shutdown.return request (but not shutdown.stayoff) 0x20 = shutdown.stayoff with 30s delay 0x28 = shutdown.return with 40s delay 0x2a = cancel.shutdown.stayoff 0x24 = load.on 0x30 = shutdown.stayoff with 40s delay and so on with different indexes giving different delays. I'm in the process of mapping all of these commands at the moment and up...

...- as root (this should generete the log we are after): nutdrv_qx -a ups -DDDDD >> /path/to/my/precious/log 2>&1 And keep it running all the time till the tests are over. - terminal #2 - as root: upsd -D This one too is expected to be kept alive all the time. - terminal #3: # shutdown.stayoff with ups.delay.shutdown set to 30 seconds; upsrw -s ups.delay.shutdown=30 -u <username> -p <password> ups upscmd -u <username> -p <password> ups shutdown.stayoff # shutdown.stayoff with ups.delay.shutdown set to 60 seconds; upsrw -s ups.delay.shutdown=60 -u <username>...

...39;lsusb -vvv -d 0001:0000' (as root)? > > > > > > So far, so good! > However, I need a little more testing before I can merge this into master. > > If possible, I'd like you to test and report back the logs (still with > a debug level of 5) of: > - shutdown.stayoff with ups.delay.shutdown set to 30 seconds; > - shutdown.stayoff with ups.delay.shutdown set to 60 seconds; > - shutdown.return with ups.delay.shutdown set to 30 seconds and > ups.delay.start set to 60 seconds; > - shutdown.return with ups.delay.shutdown set to 30 seconds and > ups.de...

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". hmm.. no. In plain megatec protocol there's no such a thing as 'shutdown...

...ng can't handle any values. >> To this end it appears that they use different Descriptor Indexes to acieve the desired effects. >> >> 0x18 Performs a shutdown.return with 30s delay and 10s delay before restart >> 0x1a Cancels the shutdown.return request (but not shutdown.stayoff) >> 0x20 = shutdown.stayoff with 30s delay >> 0x28 = shutdown.return with 40s delay >> 0x2a = cancel.shutdown.stayoff >> 0x24 = load.on >> 0x30 = shutdown.stayoff with 40s delay >> >> and so on with different indexes giving different delays. >> >&g...

...acturer is using can't handle any values. > To this end it appears that they use different Descriptor Indexes to acieve the desired effects. > > 0x18 Performs a shutdown.return with 30s delay and 10s delay before restart > 0x1a Cancels the shutdown.return request (but not shutdown.stayoff) > 0x20 = shutdown.stayoff with 30s delay > 0x28 = shutdown.return with 40s delay > 0x2a = cancel.shutdown.stayoff > 0x24 = load.on > 0x30 = shutdown.stayoff with 40s delay > > and so on with different indexes giving different delays. > > I'm in the process of map...

...wn.return? I only tested the following case, but yes: 1) removed power 2) ran shutdown.return 3) waited for 30-second shutdown timer; UPS turns off 4) reconnected power 5) before 180 second power-on timer elapses, run load.on 6) UPS turns on > 3. (OK, I lied - 3 things more) does the shutdown.stayoff command > ('SnR0000') work? shutdown.stayoff does not work - the UPS turns on immediately after its usual (~5 second) self-test. I tried it with both the default 30-second ups.delay.shutdown (S.5R0000), as well as 60 seconds (S01R0000). I don't think this is a regression for my mo...

...>> Also, what's the output of 'lsusb -vvv -d 0001:0000' (as root)? > > So far, so good! However, I need a little more testing before I can merge this into master. If possible, I'd like you to test and report back the logs (still with a debug level of 5) of: - shutdown.stayoff with ups.delay.shutdown set to 30 seconds; - shutdown.stayoff with ups.delay.shutdown set to 60 seconds; - shutdown.return with ups.delay.shutdown set to 30 seconds and ups.delay.start set to 60 seconds; - shutdown.return with ups.delay.shutdown set to 30 seconds and ups.delay.start set to 0 second...

...To this end it appears that they use different Descriptor Indexes to >>> acieve the desired effects. >>> >>> 0x18 Performs a shutdown.return with 30s delay and 10s delay before >>> restart >>> 0x1a Cancels the shutdown.return request (but not shutdown.stayoff) >>> 0x20 = shutdown.stayoff with 30s delay >>> 0x28 = shutdown.return with 40s delay >>> 0x2a = cancel.shutdown.stayoff >>> 0x24 = load.on >>> 0x30 = shutdown.stayoff with 40s delay >>> >>> and so on with different indexes giving diffe...

...sion of NUT/nutdrv_qx? > NUT: 2.7.4 nutdrv_qx:0.28 megatec 0.06 > > Is the monitoring system (the one running nutdrv_qx) turned off by the > shutdown process? > Yes. Same behavior when I kill all service and use just nutdrv_qx -k > Does this odd behaviour happen even if the 'stayoff' flag is used? Even worst, the ups just cycle the power and turn on again. > > > > > I tested the shutdown.return using the upscmd and I didn't see this > > behavior, so I finally find out that is I sent a dummy command to the USP > > after the shutdown.return i...

...s on when battery is critically low or when ups is overloaded) 3: Haven't a clue it's set all the time, nothing seems to change it 2: Haven't a clue it's always off 1: Shutdown active 0: Beeper status After more testing the indexes work as follows 0x0a = load.on / cancel.shutdown.stayoff / cancel.shutdown.return 0x10 and 0x18 are shutdown.stayoff and shutdown.return respectively both with 30 sec delay 0x20 and 0x28 = 35 sec delay 0x30 and 0x38 = 40 sec delay 0x40 and 0x48 = 45 sec delay 0x50 and 0x58 = 52.5 sec delay 0x60 and 0x68 = 60 sec delay 0x70 and 0x78 = 2 min delay ..........

...back up after a while (if power has returned). I'm trying to use upscmd so that I don't have to do an actual shutdown, but when I have it list the commands for my UPS, I just see 4 commands, and they're not the ones I thought I had specified. load.on load.off shutdown.return shutdown.stayoff I looked in the usbhid-ups file, and I see where, if it finds load.on.delay or load.off.delay, then it adds the 4 commands shown above. Now, load.on.delay and load.off.delay are the only two commands I *want* to support. So I put them in my hid2nut table: /* Commands to control UPS */ { "...

...are after): > nutdrv_qx -a ups -DDDDD >> /path/to/my/precious/log 2>&1 > And keep it running all the time till the tests are over. > > - terminal #2 - as root: > upsd -D > This one too is expected to be kept alive all the time. > > - terminal #3: > # shutdown.stayoff with ups.delay.shutdown set to 30 seconds; > upsrw -s ups.delay.shutdown=30 -u <username> -p <password> ups > upscmd -u <username> -p <password> ups shutdown.stayoff > > # shutdown.stayoff with ups.delay.shutdown set to 60 seconds; > upsrw -s ups.delay.shutdow...

...ControlConserveBattery), which is currently mapped to "shutdown.return" > >>>> # turn off UP gracefully (APC) (stays off even if power is restored) >>>> #UPS_OID=".1.3.6.1.4.1.318.1.1.1.6.2.1.0 integer 3" > > This should map to the "shutdown.stayoff" instant command. And this means that the current code in the repository would not work as expected, without fixing the above discrepancies first? Right? Thanks, //Jim Klimov

...led > even if the status bit fom the ups has changed state. Probably because the driver updates the beeper status only every 'pollfreq' (default 30) seconds, so it may have missed the change. > After more testing the indexes work as follows > > 0x0a = load.on / cancel.shutdown.stayoff / cancel.shutdown.return For future reference only (since the following ones are not used in the subdriver): - 0x1A -> cancel shutdown.return, - 0x2A -> cancel shutdown.stayoff, - 0x24 -> load on Are these still valid? > 0x10 and 0x18 are shutdown.stayoff and shutdown.return respectiv...

On Feb 27, 2014, at 9:43 AM, Jim Klimov wrote: >>>>> # turn off UP gracefully (APC) (stays off even if power is restored) >>>>> #UPS_OID=".1.3.6.1.4.1.318.1.1.1.6.2.1.0 integer 3" >> >> This should map to the "shutdown.stayoff" instant command. > > And this means that the current code in the repository would not work > as expected, without fixing the above discrepancies first? Right? I wasn't very clear there: .1.3.6.1.4.1.318.1.1.1.6.2.1.0 *does* currently map to "shutdown.stayoff". (We sh...

...se, but yes: > > 1) removed power > 2) ran shutdown.return > 3) waited for 30-second shutdown timer; UPS turns off > 4) reconnected power > 5) before 180 second power-on timer elapses, run load.on > 6) UPS turns on > >> 3. (OK, I lied - 3 things more) does the shutdown.stayoff command >> ('SnR0000') work? > > shutdown.stayoff does not work - the UPS turns on immediately after > its usual (~5 second) self-test. > > I tried it with both the default 30-second ups.delay.shutdown > (S.5R0000), as well as 60 seconds (S01R0000). > > I don...

On Mar 20, 2015, at 11:32 AM, Rob Groner <rgroner at RTD.com> wrote: > 3) Finally?what is the usefulness of shutdown.stayoff? It tells the UPS to shut off its load and not to turn it back on when the power comes back. If so?how does the UPS ever know to turn that load back on? You would have to hook a different PC to the UPS and run nut just to send the ?load.on? command? If the goal is just to perform a clean shutdo...