similar to: Nut v2.7.3 - how to force shutdown for a specifc ups only

On Sep 29, 2015, at 3:29 PM, Juergen Edner <juergen at eisfair.org> wrote: > > Now I wonder why it isn't possible to send a forced shutdown command > to a specific UPS only. It is possible - simply send a "shutdown.reboot" or "shutdown.stayoff" command via `upscmd`. Other instant commands (which may or may not be implemented on your UPS):

Hi all, I'm using Nut v2.7.3 on my Linux server to monitor two UPS at the same time, which are used to secure several different network devices. This set-up works fine for several month now. Due to the fact that different devices, connected to different UPS are generating a different load, the batteries of each UPS are discharged with a different speed. I now want to react on the events of

On Oct 5, 2016, at 10:59 PM, Jeff Bowman wrote: > >> The command is "upsdrvctl shutdown". > > That's what I thought, but I get this: > > Can't claim USB device [051d:0003]: libusb0-dll:err [claim_interface] could not > claim interface 0, win error: The requested resource is in use. > > Driver failed to start (exit status=1) > > I

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". When I changed it my system was abe to at least stay off, and stopped making an instant power recycling.

> >> I see at http://networkupstools.org/ddl/Cyber_Power_Systems/Value_800E.html that >> the Value 800E does not have variables such as >> load.off.delay - Turn off the load with a delay (seconds) >> load.on.delay - Turn on the load with a delay (seconds) >> >> What does command ? upscmd -l <UPS> ? report? > > I'll try this tonight when

Hi all, I'm trying to configure Nut to connect to an APC BackUPS Pro 900VA. This ups uses a serial port on which _simple_ or _smart_ signaling should be spoken. I've connected the UPS to a serial port using the original 940_0128A cable from APC. Unfortunately I've not yet managed to read any data from the ups. If I try to load the apcsmart driver it tells me that it cannot communicate

On 10/14/2015 12:18 PM, Roger Price wrote: > Is there any command in the list provided by "upscmd -l myups" which is accepted > by this UPS? None of the command sin the list successfully completes, not even beeper.toggle. My list: # upscmd -l myups Instant commands supported on UPS [myups]: beeper.toggle - Toggle the UPS beeper load.off - Turn off the load

2015-03-11 14:21 GMT+01:00 Jakub Scepka <jakub.scepka at gmail.com>: > Would you be so kind and provide some examples (commands), please? > I would run them today in the evening and report back with the logs. First, be sure to have in upsd.users a valid entry to set vars and execute instant commands: [<username>] password = <password> actions = SET instcmds = ALL where

Thank you for the commands... Please find attached log... Im not sure if the Load.on worked, because in the end I had to manually start the UPS (with button). Anyway, let me know should I need to perform some steps again (probably yes, since I believe it was off). Jakub On 11.03.2015 20:11, hyouko at gmail.com wrote: > 2015-03-11 14:21 GMT+01:00 Jakub Scepka <jakub.scepka at

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

Hello. I have a PW9120 hooked up via a serial cable running NUT 2.0.4. When running upsc I cant see any parameter that looks like it would trigger a shutdown. Theres is nothing like "battery.charge.low: 30" or "battery.charge.warning: 30". I get: ambient.temperature battery.(charge|runtime|voltage) driver.(misc) input.(misc) output.(misc)

Hello! I use online UPS MV-1000 LT http://www.230v.ru/catalogue/?id=production/ups-sm/master-vision for the power of my Linux server SLES 10 SP1. I downloaded, compiled and configured diver nut 2.4.1 from this link http://www.networkupstools.org/source/2.4/nut-2.4.1.tar.gz Here are my configuration files: --- srv:/usr/local/ups # cat etc/ups.conf [npower] driver = megatec port = /dev/ttyS0

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

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 investigation I found the problem is a bug on the ups - TSSHARA > model, driver nutdrv_qx: every time I shutdown with return, and

Hi I am considering adding support in the bcmxcp driver for the following commands available in bcmxcp specification : #define PW_UPS_ON .. /* UPS on command. length 1-2 */ #define PW_UPS_ON_TIME .. /* Scheduled UPS on in n minutes. length 3-4 */ #define PW_UPS_ON_AT_TIME .. /* Schedule UPS on at specified date and time. length 7-8 */ #define

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

Charles, thanks for your detailed answer. >> Occasionally, i get these in daemon.log: Dec 4 03:11:54 afs1 >> usbhid-ups[21973]: libusb_get_interrupt: could not claim interface >> 0: Device or resource busy > > This isn't great, but I don't think it's related. > > It is normal to get a "could not claim interface 0" error once after >

Good Day Roger AA. notice that during the test, you have little or no load, since despite being in state OB DISCHRG the battery.charge is still 100. It's best to perform such tests with a dummy load such as a table lamp and an old fashioned incandescent 100 watt bulb. ==> Yes. I got it and try to ascend load as below results dinow-All-Series:~# upsc pcmups Init SSL without

Good Day Roger AA. notice that during the test, you have little or no load, since despite being in state OB DISCHRG the battery.charge is still 100. It's best to perform such tests with a dummy load such as a table lamp and an old fashioned incandescent 100 watt bulb. ==> Yes. I got it and try to ascend load as below results dinow-All-Series:~# upsc pcmups Init SSL without

- OS name and version: Ubuntu 12.04 - exact NUT version: 2.6.3 - NUT installation method: from Ubuntu package "nut 2.6.3-1ubuntu1.1" - exact device name and related information: AtlantisLand Host Power 851 (A03-HP851 rev.1.1) - driver: blazer_usb I have no problems with the operation of NUT. My only problem is that I would like to change the behavior of the NUT driver