search for: baud_rat

Hi, I have an HP R5500XR and a Compaq R3000XR that I would like to use with nut. I searched the compatibility lists and the mail list archives but couldn't find anything. They both have 9 pin serial ports. Can anyone give me any information about them, and if they are supported by nut? Thanks, Denny Fox

...Fatal error: unusable configuration CLOSING Driver failed to start (exit status=1) ==================================================================== My ups.conf looks like this user=admin [PowerWare] driver = bcmxcp_usb port = auto desc = "PowerWare 5115 UPS" #pollinterval=1 baud_rate = 9600 I have tried various configurations but nothing seems to work. Once I receive this error I need to disconnect and reconnect the USB cable to get any further. Is there anything I can try? UPS work correctly on a Windows Vista/2008. Over the next few days I will try and install NUT on ubu...

...to not be working with nut. It's not in the current "supported hardware" list, but the old bcmxcp page lists it as being a UPS that speaks that protocol. I have the following in my ups.conf [powerware] driver = bcmxcp port = /dev/ttyS0 desc = "Powerware Prestige 9 EXT" baud_rate = 2400 And when I start the driver I get root% upsdrvctl -v start Network UPS Tools - UPS driver controller 2.0.4 exec: /lib/nut/bcmxcp -a powerware Network UPS Tools - BCMXCP UPS driver 0.10 (2.0.4) Connected to UPS on /dev/ttyS0 baudrate: 2400 Model = Powerware Prestige 1000VA Firmware = 01.0...

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

...t localhost |Enter new value for outlet.1.delay.shutdown: 10 |OK | |# upsc PW5125 at localhost | grep "outlet.1.delay.shutdown" |outlet.1.delay.shutdown: -1 | | | | |Am I missing something obvious? ============= Forgot to add ups.conf: [PW5125] driver = bcmxcp port = /dev/cuau0 baud_rate = 9600 desc = "PW 5125 - 1500"

NUT 2.6.5 on FreeBSD 9.1 Why isn't the variable outlet.1.delay.shutdown set with the following command? # upsc PW5125 at localhost | grep "outlet.1.delay.shutdown" outlet.1.delay.shutdown: -1 # upsrw -u au -p ap -s outlet.1.delay.shutdown PW5125 at localhost Enter new value for outlet.1.delay.shutdown: 10 OK # upsc PW5125 at localhost | grep "outlet.1.delay.shutdown"

...lost: Error executing command Communications with UPS lost: Error executing command Can't find the UPS on port /dev/ttyS0! Driver failed to start (exit status=1) Here are my /etc/nut/ups.conf: [ups] driver = bcmxcp port = /dev/ttyS0 desc = "PowerWare 5125" baud_rate = 9600 With the generic driver it works, sort of. I mean it signals I'm running on battery (which is not true) and the battery is low and then shut downs. Also, I can connect with the minicom to the UPS. Any ideas how to get the bcmxcp driver up?

...d the Development tag from CVS, and now it's working! Great! > > [root@encoda02 root]# /usr/local/ups/bin/upsc hpr5500@localhost > ambient.temperature: 26.5 > battery.charge: 99.3 > battery.runtime: 1153 > battery.voltage: 256.8 > driver.name: bcmxcp > driver.parameter.baud_rate: 19200 > driver.parameter.port: /dev/ttyS0 > driver.version: 2.1.0 > driver.version.internal: 0.10 > input.frequency: 59.8 > input.voltage: 199.7 > output.current: 11.5 > output.frequency: 60.0 > output.voltage: 197.0 > ups.firmware: 01.03 > ups.load: 45.6 > ups....

...he HP straight-through serial cable (or is it just a serial extension cable?) that came with the UPS. That cable bears the following identifying information: HP 397237-002 SPARES P/N 397642-001 5006 ups.conf looks like this: [tokamak] driver = bcmxcp port = /dev/tty00 baud_rate = 19200 desc = HP R3000XR (main rack) This is where things start going pear-shaped. I apparently cannot communicate with the UPS. I can start the bcmxcp driver, but it fails to communicate at 9600, and "autodetects" a rate of 19200: babylon4:root:/opt/nut/etc:9 # ../b...

...ne power My NOTIFYCMD is just #! /bin/sh echo "$*" | mailx -s "UPS ${UPSNAME} notification: ${NOTIFYTYPE}" EMAIL In case the rest of upsc is useful: ambient.temperature: 52 battery.charge: 95 battery.runtime: 1003 battery.voltage: 52.26 driver.name: bcmxcp driver.parameter.baud_rate: 9600 driver.parameter.pollinterval: 2 driver.parameter.port: /dev/ttyS0 driver.version: 2.2.2 driver.version.internal: 0.14 input.frequency: 50.00 input.voltage: 240 output.current: 3.2 output.frequency: 50.00 output.phases: 1 output.voltage: 209 output.voltage.nominal: 230 ups.firmware: Cont:01...

...Error executing command Communications with UPS lost: Error executing command Communications with UPS lost: Error executing command Communications with UPS lost: Error executing command Can't find the UPS on port /dev/cuaa0! Driver failed to start (exit status=1) -- I tried several values for baud_rate but with the same result. ups.conf contains: -- [compaq] driver = bcmxcp port = /dev/cuaa0 desc = "Compaq T700h" -- I'm assuming that the UPS and cable are OK since Windows XP detects the presence of a Powerware UPS. Any suggestions or pointers would be...

UPS: HP R3000 XR with HP UPS Management Module What I Want: I just want the UPS to shut down the client called "tor" before the UPS power drains out, I'd prefer to use a direct serial cable instead of network, in case the network doesn't work. I'll manage the UPS trough the ethernet using the built-in HTTP webinterface in the HP UPS Management Module. I've created a

Hi all, I know there are some howto's about Powerware 5115 and Ubuntu, but I can't still get that thing working. Can someone give some light... 1. Powerware 5115, serial port (ttyS0) 2. Ubuntu 6.06.1 as LTSP-server As reference: http://gentoo-wiki.com/HOWTO_NUT http://keystoneit.wordpress.com/2006/09/25/network-ups-tools-nut-on-ubuntu/ --- a. I try to start driver as root. root at

Hi all, I know there are some howto's about Powerware 5115 and Ubuntu, but I can't still get that thing working. Can someone give some light... 1. Powerware 5115, serial port (ttyS0) 2. Ubuntu 6.06.1 as LTSP-server As reference: http://gentoo-wiki.com/HOWTO_NUT http://keystoneit.wordpress.com/2006/09/25/network-ups-tools-nut-on-ubuntu/ --- a. I try to start driver as root. root at

...W5125 at localhost | grep "outlet.1.delay.shutdown" > |outlet.1.delay.shutdown: -1 > | > | > | > | > |Am I missing something obvious? > ============= > > > Forgot to add ups.conf: > > > [PW5125] > driver = bcmxcp > port = /dev/cuau0 > baud_rate = 9600 > desc = "PW 5125 - 1500" I was just going to gripe about the lack of driver information :-) Sounds similar to Pascal's question: http://lists.alioth.debian.org/pipermail/nut-upsuser/2013-June/008462.html Do you see anything from syslog at LOG_NOTICE? In theory, the b...

I'm currently testing the bcmxcp driver for NUT, and it causes me some trouble. And when scanning the archives it seems like the 3110 USB problem reported recently. The bcmxcp daemon stops running, and the logs shows the following: Oct 6 14:22:32 host.dom.tld bcmxcp[82628]: Communications with UPS lost: Receive error (data): got -1 bytes instead of 28!!! Oct 6 14:22:33 host.dom.tld

...error (Request command): 0!!! Aug 27 10:43:38 sv18 bcmxcp[6373]: Communications with UPS lost: Receive error (Request command): 0!!! After about 15 hours the driver exits and has to be restarted. Here is my ups.conf: [ups2] driver = bcmxcp port = /dev/ttyS1 desc = "HP R3000 XR" baud_rate = 19200 The system is running Slackware Linux 12.1 and nut was built from source. Any ideas? Thanks, David -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20090827/1b13077c/attachment.htm>

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:

..., I hope it will run well. HP R5000 upsc output: ambient.temperature: 27.4 ambient.temperature.high: 45 battery.charge: 99.0 battery.runtime: 536 battery.voltage: 236.3 device.mfr: Eaton device.model: HP R5000 5000i device.serial: 3C81520083 device.type: ups driver.name: bcmxcp driver.parameter.baud_rate: 9600 driver.parameter.pollinterval: 2 driver.parameter.port: /dev/ttyS0 driver.version: 2.4.3 driver.version.internal: 0.23 input.current: 18.1 input.frequency: 50.0 input.frequency.high: 54 input.frequency.low: 46 input.frequency.nominal: 50 input.transfer.boost.high: 202 input.transfer.high: 2...

...st | grep "outlet.1.delay.shutdown" |> |outlet.1.delay.shutdown: -1 |> | |> | |> | |> | |> |Am I missing something obvious? |> ============= |> |> |> Forgot to add ups.conf: |> |> |> [PW5125] |> driver = bcmxcp |> port = /dev/cuau0 |> baud_rate = 9600 |> desc = "PW 5125 - 1500" | | |[snip] | |Do you see anything from syslog at LOG_NOTICE? In theory, the bcmxcp |driver should log a message if the parameter change is refused by the UPS. | |If not, you could try re-running the driver with a few -D flags. That will |show some i...