similar to: PW9120 - Shutdown condition?

On 19/09/13 01:30, Kris Jordan wrote: > Luke-Jr wrote, On 9/18/2013 1:02 PM: >> I wanted to suggest some rating for functionality. I got the UPS >> available >> that seemed to have the best possible rating from NUT's list (Eaton >> Powerware >> UPS 1500), and found out it doesn't support telling me battery level or >> runtime! :/ > > I'm

Hi Michael, I've forwarded your patch to Kjell, who's maintaining the bcmxcp driver, and to the nut development list. Kjell and others have more knowledges of the xcp protocol and will be able to analyze your patch. 2008/1/4, michalwd1979 <michalwd1979 at o2.pl>: > Hello Arnaud, > I am sending You a small patch to bcmxcp.c and bcmxcp.h files from nut-2.2.0. I written this

Hello... I have a PowerWare 9120 attached via USB to my Debian system. My ups.conf looks like this: [ups1] driver = bcmxcp_usb port = auto desc = "PowerWare 9120" When testing the driver with "upsdrvctl -u root start" I get: Network UPS Tools - UPS driver controller 2.0.4 Network UPS Tools - BCMXCP UPS driver 0.10 (2.0.4) Communications with UPS

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

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

- 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

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. Thank you. Jakub S. On Tue, Mar 10, 2015 at 11:44 PM, hyouko at gmail.com <hyouko at gmail.com> wrote: > mmh.. it looks like someone forgot to hit 'reply all'. > > - relaying the originally attached files (gzipped, minus the two >

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

mmh.. it looks like someone forgot to hit 'reply all'. - relaying the originally attached files (gzipped, minus the two screenshots, to keep size down). 2015-03-09 23:20 GMT+01:00 Jakub Scepka (private) <jakub.scepka at gmail.com>: > Hi everyone! > > Here is summary for our fellows wit the same/similar UPS to save them 3 > weeks of life :) > > First of all I'm

On Dec 7, 2013, at 2:38 PM, Christian wrote: > Dear list, > > I have an APC Smart-UPS 1500 hooked up via the USB port. Recently, when > we had a power outage, the only entry in the logs was: > > Dec 3 14:43:43 afs1 upsmon[3035]: UPS apc at localhost on battery > > and then the machine seems to have run until the battery was empty. It > only notices the "battery

Hello! I'm a total noob in the NUT world, and have 0 experience dealing with Linux distributions. Since NUT is poorly ported to Windows it's driving me crazy, I hope you can help me. I have, after 3 days of painful reading, testing and failing, successfully set up NUT to communicate with my cheap-ass line-interactive 1000VA Chinese UPS (just no brand at all, it is a locally rebranded UPS,

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

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

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 >

I'm doing testing of the UPS-side code, including being able to tell the UPS to shutdown and then come 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

Hello all NUT users and developers! Have some questions about nut suite: 1. Does upscmd provide only device-specific commands? Or commands like shutdown.stayoff are general and good for all ups models? When i see output of 'upscmd -l' - is this general commands that supported by given device or this is unique commands of this device? For example, i have APC SmartUPS-750 and it shows me

Hi all, I just acquired a new UPS and have been trying to get it to work with NUT. It's an Eaton/Powerware 9120 700i with both USB and RS-232 interfaces. I first tried the USB interface (using bcmxcp_usb) and found that the UPS worked fine for a few minutes but then NUT lost communication and didn't get it back. In addition the UPS itself seemed to lock up at one point such that the

This UPS is already listed in the compatibility list. But I wanted to add the instant commands supported by upscmd: ============================ Instant commands supported on UPS [PW5125]: beeper.disable - Disable the UPS beeper beeper.enable - Enable the UPS beeper beeper.mute - Temporarily mute the UPS beeper load.on - Turn on the load immediately outlet.1.load.off - Turn off the load on

Hi Rob I still have an unset draft answer to your previous mail... but you seem to have progressed... 2015-03-20 16:32 GMT+01:00 Rob Groner <rgroner at rtd.com>: > I?m doing testing of the UPS-side code, including being able to tell the > UPS to shutdown and then come back up after a while (if power has returned). > > > > I?m trying to use upscmd so that I don?t have to

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 reconnect the usb after the power is back it would start another shudown.return cycle. When I used my