similar to: 2.6.0 bcmxcp_usb recovery question

Hello. I've tried to configure Windows (complete port, Beta): Windows MSI installer 2.6.0-1 with my Powerware 5115 connected via USB port but have no luck. Here is my config files: *nut.conf:* MODE = netserver *ups.conf:* [PW5115] driver = bcmxcp_usb port = notUsed desc = "PowerWare 5115" *upsd.conf:* LISTEN 192.168.1.12 3493 *upsd.users:* [monuser]

Greetings, I have been using the bcmxcp_usb driver heavily over the last two years as part of a very successful product, first from NUT 2.4.1 and now from NUT 2.6.0. Now I have a need to do setvar of the outlet.n.delay.start variables, so recently I modified bcmxcp.c to do that. I've tested it and it works well for my purposes. My plans are to begin shipping that modified driver as part

Hi I have PW 5115 500 UPS which has both RS232 and USB connectors. bcmxcp driver works fine with serial connection but bcmxcp_usb does not with USB one. After some USB sniffing on windows box I've found that PW5115 communicates in other way than supposed in driver. Applying attached patch makes driver to work properly. System: FreeBSD 6.2 but ugen driver needs patching in order to respect

I am seeing some problems when using the Powerware 5115 UPS when connected to the Patsburg USB controller and would like to know if anyone has a solution. The symptom is that PING messages sent to the bcmxcp_usb driver take as long as 25 seconds to complete. The configuration is a Romley patform (a.k.a., Sandy Bridge + Patsburg) running Debian 6 with 2.6.39 kernel with NUT 2.6.4 in which the

I tried switching to the USB version of bcmxcp_usb and get this error when I try starting up upsdrvctl or bcmxcp_usb like so: /etc/nut/bcmxcp_usb -DDDD -a powerware -u nut I used this for ups.conf: [powerware] driver = bcmxcp_usb port = auto With the serial/usb dongle, I used this successfully: [powerware] driver = bcmxcp port = /dev/ttyUSB0 What devices does

Hi everyone, First of all a big thank you for the NUT package, I've been using it for years and couldn't get by without it! I have two Powerware UPS's here, a 9120/1500va and a 5110/700va. The 9120 has used a hacked bcmxcp driver (serial) from the 2.0.2 nut version for about a year now (which I'll explain more about in a seperate email to the dev list), and the 5110 which I just

Hi I'm having a problem with the bcmxcp_usb driver FSD command: everything seems to work apart from: upsmon -c fsd Environment: Ubuntu 7.04, nut 2.0.5-1, nut-usb 2.0.5-1, Powerware 3105 UPS. upsd appears to send the FSD command to the UPS, upsmon then runs my NOTIFYCMD (which halts my PC) but the UPS just doesn't turn off. Here are the /var/log/daemon.log entries: Jul 24 23:13:16

Hi Greg, Thomas and the list, I've not forgotten you nor your issue. It just took some time to gather a "faulty" unit and a bit of time to reproduce your issue. The good news is that I've commited a fix to the NUT development branch (aka Subversion), in the release r2015. The bad news is that your test and feedback is welcome ;-) For more info on getting and compiling the

I can't find a way to configure bcmxcp_usb to communicate with 2 UPS units. Maybe more simply, I can't find a way to tell the driver to only talk to one of the units on the bus. That is, I cannot find that the driver configuration file supports "serial =" or "bus = " or other such discriminators that other drivers do (usb_apc, etc.). So, I can't assign one Eaton

Hi, I recently downgraded my kernel to 2.4 series (2.4.32-rc2). Now I can't get nut running. It was fine with 2.6.14. It say's: --------------------- # ./bcmxcp_usb -uroot AUTO Network UPS Tools - BCMXCP UPS driver 0.10 (2.1.0) Can't reset POWERWARE USB endpoint Unable to find POWERWARE UPS device on USB bus ... --------------------- I've straced it in nut_usb.c

Good evening, I tried getting this to work a couple years back but didn't have enough time to do all the debugging that was needed (apologies to the devs who tried to help at that time). It's working much better now, but I'm still not able to get an answer from upsc. Can anyone help me work out why I'm getting the error when querying with upsc: Error: Data stale My

Good evening, I tried getting this to work a couple years back but didn't have enough time to do all the debugging that was needed (apologies to the devs who tried to help at that time). It's working much better now, but I'm still not able to get an answer from upsc. Can anyone help me work out why I'm getting the error when querying with upsc: Error: Data stale My

Kjell Claesson wrote: > Then i have a problem. My computer is down due to a > faulty mainboard, Youch. I hate it when that heppens. Hope it wasn't because you got a power spike ;-) Let me or Georg know if you want us to run any debug code. Feels like a bcmxcp_usb driver bug to me since the bcmcxp serial driver works fine and all my other USB devices work fine (wifi adapter, memory

Hi, I have got a Powerware 5110 UPS which has a usb interface on it. I have downloaded and compiled nut-2.0.3-pre2 with the usb drivers enabled on RedHat Enterprise V3 however I have been unable to get nut to connect to the UPS. I have tried executing the driver directly (using bcmxcp_usb -DD -u root /proc/bus/usb/002/002) as well as using upsdrvctl with the port set to auto (am I correct in

Hello, ppl! I try configure NUT for communicate with my Powerware 5115 UPS. As root I run '/lib/nut/bcmxcp_usb -DDDD -u root -a ups', but driver can't connect to my UPS. Some output: Network UPS Tools - BCMXCP UPS driver 0.10 (2.0.4) debug level is '4' usb_set_debug: Setting debugging level to 3 (on) usb_os_init: Found USB VFS at /dev/bus/usb usb_os_find_busses: Found 001

<nut-upsuser at lists.alioth.debian.org> I am doing my best to avoid have to spend $280 for a network monitoring card to put into a $190 UPS just to have some good remote monitoring capabilities. Rather, I would like to monitor my many 1U Tripp Lite's on my network using a Raspberry Pi running Raspian and using NUT. However, I cannot seem to get it working. And I while the hardware

Hi, I have set up a RaspberryPi computer to do monitoring of two UPSs. One is an MGE evolution 800, one is an Eaton Powerware 5110. The MGE was being monitored by another Linux (Ubuntu 12.04) computer, and I just copied and pasted in the relevant nut config and it works just fine with nut. I've tried to set up the Powerware 5110 with nut, and the bcmxcp_usb driver can't communicate

Hi, I'm trying to get a Powerware 5115 to communicate with the NUT via USB under Debian Linux and need help. Here is the output that I see. co-nh5:/tmp/mnt/projects/pwusb/nut-2.4.1# /usr/local/ups/bin/upsdrvctl -u root start Network UPS Tools - UPS driver controller 2.4.1 Network UPS Tools - BCMXCP UPS driver 0.21 (2.4.1) USB communication subdriver 0.17 Communications with UPS lost:

cmd test.battery.start.deep was not tested yet. cmd test.battery.start.quick works as expected. cmd test.battery.start 120 works as expected. cmd test.battery.stop works as expected. cmd beeper.toggle works as expected. cmd shutdown.return works as expected. cmd shutdown.reboot does not work entirely. After a minute, UPS is shut down but didn't come back. (Issuing shutdown.stop power up it

Hi Andrew, thanks to subscribe to nut-upsuser and continue on this one: http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser The solution to your problem depends on the way you installed NUT. It's possibly one of these: https://launchpad.net/distros/ubuntu/+source/nut/+bug/6679 https://launchpad.net/distros/ubuntu/+source/nut/+bug/6585 Andrew Wallace wrote: > Hi > > I've