search for: shutdown_delay

...compiled and installed fine system shall - broadcast a message and shut down if ups on battery for 30+ s - wait 120 s - broadcast another message - give system 120 s to shut down, then power off bcmxcp is running as /usr/bin/bcmxcp -a PW9125 with ups.conf [PW9125] driver = bcmxcp port = /dev/cua0 shutdown_delay = 120 desc = "tfp-8" upsd and upsmon are running, too upssched is used and works fine, e.g. AT ONBATT * START-TIMER a-onbat 30 AT ONBATT * START-TIMER a-onbat2 120 do alright Problem: When shutting down, shutdown_delay is not recognized, system is powered off immed...

...id not contain expected field bios_strings. Struct did not contain expected field protection_policy. Struct did not contain expected field is_snapshot_from_vmpp. Struct did not contain expected field appliance. Struct did not contain expected field start_delay. Struct did not contain expected field shutdown_delay. Struct did not contain expected field order. Struct did not contain expected field VGPUs. Struct did not contain expected field attached_PCIs. Struct did not contain expected field suspend_SR. Struct did not contain expected field version. 0 Control domain on host: xenserver-4 running Struct...

...busy testing the Powerware9120 and am stuck at the powering down of the UPS. I'm running the latest Debian Lenny and here is my versions Network UPS Tools - UPS driver controller 2.2.2 Network UPS Tools - BCMXCP UPS driver 0.14 (2.2.2) ups.conf [pw] driver = bcmxcp_usb port = auto shutdown_delay = 60 I get all the correct info from the UPS and NUT works great and PC shutsdown on low battery. The only problem is that the UPS itself does not shut down, so the PC will never come back up when the power is restored. I have also tried the bcmxcp and upscode2 drivers from some posts that I saw i...

Hi Denny. Nice, i have entered the HP R5500 XR to the drivers.list in the Testing and Development tree. Some info for you when you setup the nut. The shutdown_delay of the driver is internal to the ups. It calculate the time it can run after low-battery with the load. So when it comes to OB LB it starts the shutdown_delay and power off after it runs out. This is the normal way, as you would like the ups to wait as long as possible to get the line power back....

Hi there. At the moment I'm trying to get my HP T1500 XR (Powerware 5125) UPS to work with NUT. NUT registers that the UPS is on battery/online, but I just cant get the program to shut down the computer I'm using the original cable (thus I didn't enter anything in the ups.conf file) If I remove the cable and run the daemon/program the computer will shutdown after x minutes defined in

...tatus."); > *************** > *** 564,571 **** > { > upslogx(LOG_INFO, "Shutting down UPS immediately."); > > ! ser_send_pace(upsfd, SEND_PACE, "C%c", ENDCHAR); > ! ser_send_pace(upsfd, SEND_PACE, "S%02dR%04d%c", > shutdown_delay, start_delay, ENDCHAR); > } > > > --- 569,576 ---- > { > upslogx(LOG_INFO, "Shutting down UPS immediately."); > > ! comm->send("C%c", ENDCHAR); > ! comm->send("S%02dR%04d%c%c", shutdown_delay, start_delay,...

...just purchased is using the new bcmxcp_usb from 2.0.4 ... which brings me to the point of the post... The upsc output shows a blank serial number, and no battery.runtime at all, see below: [rohbags@dvr drivers]# upsc pw5110@localhost battery.voltage: 13.5 driver.name: bcmxcp_usb driver.parameter.shutdown_delay: 90 driver.version: 2.0.4 driver.version.internal: 0.10 input.frequency: 50.1 input.voltage: 230 output.current: 0.3 output.frequency: 50.1 output.voltage: 230 ups.firmware: 00.50 ups.load: 16.7 ups.model: POWERWARE UPS 700VA ups.power.nominal: 700 ups.serial: ups.status: OL ups.voltage.nom...

...le if not for the fact that the shutdown.stayoff instant command works -- turns ups off immediately and that notifications are returned from the UPS. The bcmxcp_usb driver reports the following status: # upsc pw3105 at localhost driver.name: bcmxcp_usb driver.parameter.port: auto driver.parameter.shutdown_delay: 120 driver.version: 2.0.5 driver.version.internal: 0.11 input.phases: 1 ups.firmware: 00.80 ups.model: POWERWARE UPS 500VA ups.power.nominal: 500 ups.serial: ups.status: OL ups.voltage.nominal: 240 One peculiarity -- even though the test.battery.start instant command is listed it puts this in...

...ure.high: 29 ambient.temperature.low: 206 battery.charge.low: 11 battery.voltage: 13.5 battery.voltage.low: 10 device.mfr: Eaton device.model: POWERWARE UPS 500i device.serial: device.type: ups driver.name: bcmxcp_usb driver.parameter.pollinterval: 2 driver.parameter.port: auto driver.parameter.shutdown_delay: 50 driver.version: 2.6.5-161-g1e76ba8 driver.version.internal: 0.26 input.frequency: 49.9 input.frequency.high: 55 input.frequency.low: 45 input.frequency.nominal: 50 input.transfer.boost.high: 207 input.transfer.high: 275 input.transfer.low: 178 input.transfer.trim.low: 250 input.voltage: 240 in...

...quot;megatec.h" #include <stdio.h> @@ -44,9 +43,6 @@ #define IDENT_MAXTRIES 5 #define IDENT_MINSUCCESS 3 -#define SEND_PACE 100000 /* 100ms interval between chars */ -#define READ_TIMEOUT 2 /* 2 seconds timeout on read */ - #define MAX_START_DELAY 9999 #define MAX_SHUTDOWN_DELAY 99 @@ -167,7 +163,6 @@ /* I know, macros should evaluate their arguments only once */ #define CLAMP(x, min, max) (((x) < (min)) ? (min) : (((x) > (max)) ? (max) : (x))) - static float batt_charge_pct(float battvolt) { float value; @@ -178,15 +173,14 @@ return value * 100; } -...

...quot; before and after i plugged in the powerware usb cable and did a diff on the results of the two which was: -- 322c322 < Port 2: 0000.0100 power --- > Port 2: 0001.0301 C_CONNECT lowspeed power connect -- current ups.conf is: -- [pw5110] driver = bcmxcp_usb port = auto shutdown_delay = 60 desc = "USB ups" -- did some diagnosis: sudo /lib/nut/bcmxcp_usb -DDDDD -a pw5110 Network UPS Tools - BCMXCP UPS driver 0.11 (2.0.5) debug level is '5' Can't open POWERWARE USB device, retrying ... Can't open POWERWARE USB device, retrying ... Can't open POW...

Hi, So far I've gleaned heaps of useful info from the list and got mostly running with NUT. There was a thread by Paul Battaglia and Kjell Claesson about the R3000 which has helped me get so far, but now with the patched driver I still have this on startup: # /usr/local/ups/bin/upsdrvctl start Network UPS Tools - UPS driver controller 2.0.5 Network UPS Tools - BCMXCP UPS driver 0.11

Hi I had to close pull request 33, due to misspelling of commit messages. Charles helped me to fix it, and I have made a new pull request. The new pull request is : https://github.com/networkupstools/nut/pull/35 Regards Alf

I learned earlier from Roger Price's excellent explanation that a proper configuration includes sending a 'delayed shutdown' signal to the UPS hardware prior to shutting down the server. How is this accomplished? Does the USB driver handle this for us or must we do something additional? Thanks, Jeff Bowman Fairbanks, Alaska

.... > Hi Jeff. > How is this accomplished? Does the USB driver handle this for us or must we > do something additional? It depends on the driver. Look in the manual for your driver and check if it have any extra arguments. For example the driver I was involved in "bcmxcp" has a shutdown_delay that set the time between receiving the command and actually shutting off. USBHID-UPS have a offdelay. " offdelay=num Set the timer before the UPS is turned off after the kill power command is sent (via the -k switch). The default value is 20 (in seconds). Usually this must be lower than...

Hi, Does anyone know how to make NUT works with Powerware 5125? I already tried serial communication (genericups and bcmxcp) and USB (usbhid-ups and bcmxcp_usb), but without success. I'm using the latest version of NUT (2.6.5) under Debian amd64. Can anyone help me? Thanks. Daniel -------------- next part -------------- An HTML attachment was scrubbed... URL:

...mperature.low: 30 battery.charge.low: 11 battery.voltage: 13.5 battery.voltage.low: 10 device.mfr: Eaton device.model: POWERWARE UPS 500i device.part: 103004261-5591 device.serial: device.type: ups driver.name: bcmxcp_usb driver.parameter.pollinterval: 2 driver.parameter.port: auto driver.parameter.shutdown_delay: 50 driver.version: 2.6.5-170-g3f72709 driver.version.internal: 0.28 input.frequency: 49.9 input.frequency.high: 55 input.frequency.low: 45 input.frequency.nominal: 50 input.transfer.boost.high: 207 input.transfer.high: 275 input.transfer.low: 178 input.transfer.trim.low: 250 input.voltage: 238 inp...

=?ISO-8859-1?Q?Alf_H=F8gemark?= <alf at i100.no> writes: > I am working on improving the bcmxcp driver, to add more data reported > from the driver, and also add support for sending more commands to the ups. > The code changes are currently not part of any release, but they are in > github, and some more are on the way. > Would you be able to do some testing on your HP R3000

Hi, I've been getting emails from upsmon saying: Subject: UPS PW5125 at localhost notification: ONBATT UPS PW5125 at localhost on battery But then the machines on the UPS stay on for hours; we haven't got that kind of runtime, more like 10-20 minutes. After a few occurrences, it now happened at a time where I could log in to see in real time what is happening and: $ upsc PW5125 |

I have an FC5 system with a powerware 5110 usb ups. The system seems to find the UPS ------------------------------ [root@b1 src]# lsusb Bus 004 Device 001: ID 0000:0000 Bus 003 Device 002: ID 0592:0002 Powerware Corp. Bus 003 Device 001: ID 0000:0000 Bus 002 Device 001: ID 0000:0000 Bus 005 Device 001: ID 0000:0000 Bus 001 Device 001: ID 0000:0000 ------------------------------- [root@b1