search for: pw5115

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] password = xxxxxxxx upsmon master *upsmon.conf:* MONITOR PW5115 at 192.168.1.12 1 monuser xxxxxxxx master MI...

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 given timeout, patch already included in 7.0 (http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/dev/usb/ugen.c.diff?r1=1.109;...

...have changed significantly between 2.4.1 and 2.6.0. While I can see some improvements, bcmxcp_usb 2.6.0 does not appear to handle a USB cable unplug-plug correctly. Does anyone know if this has been fixed in subsequent releases? Here are the details. When the USB cable between my server and my PW5115 UPS is removed, bcmxcp_usb reports DATASTALE (as it should) and continues to respond to PING (as it should). When the USB cable is reattached, bcmxcp_usb continues to report DATASTALE in response to DUMPALL even though lsusb indicates that the PW5115 is indeed connected and DATAOK is never reporte...

...driver does report remaining runtime. I don't how how accurate it is, but the LS3 software allows to configure a shutdown time required by OS. Can I configure nut to shut down a few minutes earlier? battery.charge: 93 battery.runtime: 1693 battery.voltage: 12.71 device.mfr: Eaton device.model: PW5115 500i device.serial: XcensoredX device.type: ups driver.name: bcmxcp driver.parameter.pollinterval: 2 driver.parameter.port: /dev/ttyu0 driver.version: 2.6.1 driver.version.internal: 0.24 [current input/output] ups.beeper.status: enabled ups.firmware: Cont:01.00 Inve:10.04 ups.load: 20.4 ups.mfr: E...

...UPS Tools - BCMXCP UPS driver 0.10 (2.0.3) Communications with UPS lost: Error executing command Communications with UPS lost: Error executing command Communications with UPS lost: Error executing command Communications with UPS re-established Connected to UPS on /dev/ttyS0 baudrate: 9600 Model = PW5115 750i 750VA Firmware = 01.00 Shutdown delay = 120 seconds b. I try to start upsd as root. root at kirkonmaki:/home/juuri# upsd Network UPS Tools upsd 2.0.3 /etc/nut/upsd.conf is world readable Can't connect to UPS [powerware] (bcmxcp-ttyS0): Permission denied /etc/nut/upsd.users is wo...

...UPS Tools - BCMXCP UPS driver 0.10 (2.0.3) Communications with UPS lost: Error executing command Communications with UPS lost: Error executing command Communications with UPS lost: Error executing command Communications with UPS re-established Connected to UPS on /dev/ttyS0 baudrate: 9600 Model = PW5115 750i 750VA Firmware = 01.00 Shutdown delay = 120 seconds b. I try to start upsd as root. root at kirkonmaki:/home/juuri# upsd Network UPS Tools upsd 2.0.3 /etc/nut/upsd.conf is world readable Can't connect to UPS [powerware] (bcmxcp-ttyS0): Permission denied /etc/nut/upsd.users is wo...

...OS 7.3 machine with following packages installed: nut-client-2.7.2-3.el7.x86_64 nut-2.7.2-3.el7.x86_64 nut-cgi-2.7.2-3.el7.x86_64 $ upsc eaton5115 ambient.temperature: 43 ambient.temperature.high: 75 battery.charge: 100 battery.runtime: 24171 battery.voltage: 40.96 device.mfr: Eaton device.model: PW5115 RM 1500i device.part: XXXXXXXXX-XXXX device.serial: XXXXXXXXXX device.type: ups driver.name: bcmxcp_usb driver.parameter.pollinterval: 2 driver.parameter.port: auto driver.version: 2.7.2 driver.version.internal: 0.28 input.frequency: 50.00 input.frequency.high: 55 input.frequency.low: 45 input.freq...

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

I ran into a portability issue with drivers/bcmxcp.c in nut-2.4.1 on my UnixWare 7.1.4 machine. The error I get is ..... UX:acomp: ERROR: "/opt/src/utils/nut-2.4.1/drivers/bcmxcp.c", line 835: integral constant expression expected ..... Looking at the code we see ..... int init_outlet(unsigned char len) { unsigned char answer[len]; ..... Although gcc can handle it, it's not

...nicely. Serial ports belong to dialout group and nut user is a member. What is taking the /dev/ttyS6 serial port during the boot? Could this me some timing problem? Installed nut and nut-client from standard Fedora repositories (I have not yet defined any 3rd party repos). UPS is PowerWare/Eaton PW5115 1000i, connected with a serial cable to /dev/ttyS6, which is Titan Electronics Inc VScom 400H 8-port serial controller sitting in PCI bus. Everything has been rock solid reliable for years, I have been running Fedora and nut for a long time. Output of 'bcmxcp -DD -a PowerWare_5115' in atta...

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 |

Hi I have a HP R3000 XR UPS which NUT never says is at 100% battery. It seems stuck in 98 or 99 . something percentage. How accurate should i expect the reports to be? All my other UPSes has been and is at 100%, even those i have retired. My monitor system runs debian. The host that is physically connected to this ups runs: nut 2.2.2-6.4 The web script runs nut-cgi 2.0.4-4 JonB

...ough I'm not sure of the exact support level we'll have with HAL. But it gives me more visibility, and that's a good point. thanks. > > I lack much visibility on our supported devices capabilities to make > > some implementation decisions... > > > The output from a PW5115 would show more data. I'm interested in... > > One more note: I'm convinced that the nut future lies in such approach. > > This combined with some legacy support (discussed with D. Zeuthen, the > > HAL PL, to configure manually the support for serial devices) and some &g...

...to start. But have you started the daemon (upsd)? > $ sudo upsc myups at localhost > Error: Driver not connected Then you have to start the upsmon to monitor the ups. --------- Check with: ps xau |grep nut nut 5324 0.0 0.0 12428 508 ? Ss 09:41 0:00 /lib/nut/bcmxcp -a pw5115 nut 5348 0.0 0.0 40528 864 ? Ss 09:41 0:00 /usr/sbin/upsd nut 5367 0.0 0.0 40496 1148 ? S 09:41 0:00 /usr/sbin/upsmon ------------- You may also do: ps xau |grep ups Then you see that upsmon have two instants. One as nut and one as root. Regards Kjell...

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:

...ups.firmware "Cont:01.20 Inve:01.02" 7.048329 send_to_all: SETINFO ups.power.nominal "750" 7.048387 send_to_all: SETINFO output.phases "1" 7.048465 send_to_all: SETINFO ups.mfr "Eaton" 7.048594 send_to_all: SETINFO ups.model "PW5115 RM 750i" 7.048652 Length of meter map: 81 7.048682 Index Offset Format NUT 7.048739 0021 0000 f0 None 7.048807 0023 0004 f0 ups.power 7.048851 0027 0008 52 output.frequency 7.048904 0028 0012 52 input.f...