search for: pw3105

...XCP_usb > > /mnt/HD_a2/packages # lsusb > Bus 002 Device 001: ID 0000:0000 > Bus 001 Device 002: ID 0592:0002 Powerware Corp. > Bus 001 Device 001: ID 0000:0000 > > /mnt/HD_a2/packages # upsdrvctl -DD start > Network UPS Tools - UPS driver controller 2.4.1 > Starting UPS: pw3105 > exec: /ffp/bin/bcmxcp_usb -a pw3105 > Network UPS Tools - BCMXCP UPS driver 0.21 (2.4.1) > USB communication subdriver 0.17 > Can't claim POWERWARE USB interface > Unable to find POWERWARE UPS device on USB bus > Things to try: > - Connect UPS device to USB bus > - R...

Hi all, Have a strange behaviour that I don't know how to debug. This is when I use the Eaton PW5125 ups. I have it connected And running in standby. Starting up the drivers (pw3105 and pw5125) and they run. Start up the upsd and can read info from both of them. The 3105 is supplying the computer and the 5125 have a dummy load. The 5125 is showing that it is off line. Now when I hit the on line button on the ups, the upsd segfaults. The driver is still running. And I only h...

Hi, I'm trying to get a Powerware 3105 UPS working on SuSE 10.0. I have compiled nut from the current Subversion repository. This UPS uses the bcmxcp_usb driver. I cannot get the driver to find the ups on the USB bus. The error message I get is:- -------------- bcmxcp_usb -u nut -DDDDD -a pw3105 -------------------- Network UPS Tools - BCMXCP UPS driver 0.10 (2.1.0) debug level is '5' Can't set POWERWARE USB configuration Unable to find POWERWARE UPS device on USB bus ------------------------------------------------------------------------------------------------- My ups.conf...

...he 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 kea upsmon[5226]: Signal 10: User requested FSD Jul 24 23:13:16 kea upsd[5223]: Client monuser at 127.0.0.1 set FSD on UPS [pw3105] Jul 24 23:13:16 kea upsmon[5226]: Executing automatic power-fail shutdown Jul 24 23:13:16 kea upsmon[5226]: Auto logout and shutdown proceeding Jul 24 23:13:21 kea upsd[5223]: Host 127.0.0.1 disconnected (read failure) : Jul 24 23:13:28 kea upsd[5223]: Signal 15: exiting I might have suspected...

Hi, I have an UPS Powerware 5110 ( usb connection ), on Linux OS is Debian 4.0 The /etc/ups.conf file setting is: [myups] driver = bcmxcp_usb port = auto desc = "UPS Powerware 5110 1500 VA" When the daemon starts it displays the following message: "Starting Network UPS Tools: (upsdrvctl failed)." Looking at /var/log/syslog I found the following line

...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;r2=1.110) maybe it will be backported in future. However I'm unsure whether PW3105 and PW5110 (those two used with bcmxcp_usb driver) will work after this change. -- ~syhpoon -------------- next part -------------- A non-text attachment was scrubbed... Name: patch-drivers-bcmxcp_usb.c Type: application/octet-stream Size: 890 bytes Desc: not available Url : http://lists.alioth.d...

This is just to let the list know that I have had success getting my FC3 system talking to my USB PW3105. I used nut 2.0.3 and recompiled from source so as to get the bcmxcp_usb driver. After that it was just a matter of following the (very good) INSTALL instructions provided in the tarball. Although I haven't got the hotplug scripts working yet (the samples provided are not a good fit on a FC3 sy...

...This is the problem. I can ask a bcmxcp ups what commands it support, if the firmware is after revision AE. I was thinking about to use this in the driver. For example ' a ups that don't support battery_test would not have this command enabled.' The hex responce look like this from a PW3105: 0c <-- first byte is the number of commands (12) 01 <-- How many bytes reported below for each command 31 <-- PW_ID_BLOCK_REQ 33 <-- PW_STATUS_REQ 34 <-- PW_METER_BLOCK_REQ 35 <-- PW_CUR_ALARM_REQ 36 <-- PW_CONFIG_BLOC_REQ 3c <-- PW_LIMIT_BLOCK_REQ 40 <...

Hi Does there exist any work on getting the powerware driver to work with USB devices under freebsd? I have tryed with the usb enabled newhidups driver for freebsd but it does not seem to work. $ newhidups -a newhid -DD Network UPS Tools: New USB/HID UPS driver 0.23 (2.0.2) debug level is '2' found 0 (-1) No USB/HID UPS found //erlis -------------- next part -------------- An HTML

...late that support for Powerware devices is only available for the serial interface. Since the protocols over serial and USB seem to be identical, it was not too difficult to modify the bcmxcp driver to support USB. The new and changed files can be found here: ftp://ftp.weo1.de/pub/software/nut-pw3105/ Is there any interest in that driver? Should I combine the serial and the USB driver? Perhaps it makes sense to have separate binaries because of library dependencies. But besides the command IO functions the drivers are identical. Since I'm new to USB programming I'm not sure whether th...

Short description: when upsmon starts it logs this to /var/log/messages: Jul 11 12:35:55 sorcerer upsmon[23902]: Startup successful Jul 11 12:35:55 sorcerer upsmon[23902]: user monuser not found Near as I can tell upsd is running properly. Long description: Centos 5 system (x86_64), built nut 2.2.2 from stable source with ./configure --with-usb --with-user=nut --with-group-nut make

...n_bcd = 512 (0x200) (int) > > usb2 device but run on a usb1.1 port. > > > - an upsc output of your device. > > - some details about your device capabilities in therm of delayed > > shutdown, and status reporting (ie, is it reporting only ups.status?) > > > upsc pw3105 at localhost > driver.name: bcmxcp_usb > driver.parameter.pollinterval: 2 > driver.parameter.port: auto > driver.parameter.shutdown_delay: 60 > driver.version: 2.1.0 > driver.version.internal: 0.11 > output.phases: 1 > ups.alarm: > ups.firmware: Cont:00.80 Inve:00.60 >...

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