Hi Arnaud, Thanks for continuing to look at this. Much appreciated!
I compiled the driver on my QNAP as I didn't have time to muck around with Ubuntu. Here is my output ============================ [/] # /usr/local/ups/bin/bcmxcp_usb -DDDD -a qnapups -u admin Network UPS Tools - BCMXCP UPS driver 0.22 (2.4.1) USB communication subdriver 0.17 0.000000 debug level is '4' 0.008527 device 007 opened successfully 0.627638 Communications with UPS lost: Receive error (data): got 17 bytes instead of 116!!! 1.635224 Communications with UPS lost: Receive error (Request command): BLOCK: 0, COMMAND: 31! 1.667626 Communications with UPS lost: Receive error (Request command): BLOCK: 0, COMMAND: 31! 2.677716 Communications with UPS lost: Receive error (Request command): COMMAND: 31 2.677812 RECONNECT USB DEVICE 5.717704 device 007 opened successfully 5.718507 Can't reset POWERWARE USB endpoint: could not clear/halt ep 129: Broken pipe Unable to find POWERWARE UPS device on USB bus (USB) Things to try: - Connect UPS device to USB bus - Run this driver as another user (upsdrvctl -u or 'user=...' in ups.conf). See upsdrvctl(8) and ups.conf(5). 5.756653 Fatal error: unusable configuration 5.756726 CLOSING ============================== It look similar to the issue I had originally but remember I am on the QNAP. Thanks again, Greg From: Arnaud Quette Sent: Tuesday, October 06, 2009 8:15 PM To: Greg Vickers ; Thomas Zulliger Cc: NUT Users Subject: [Nut-upsuser] Powerware USB issue solved (bcmxcp_usb) 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 development release: http://buildbot.ghz.cc/~buildbot/docs/r2003-144/website/download.html Note that you don't need to install nut ; simply running from the build directory is sufficient, using: $ drivers/bcmxcp_usb -DD -a <ups name> will tell you if your issue is solved. And I'm very confident that it will indeed be solved. cheers, Arnaud -- Linux / Unix Expert R&D - Eaton - http://www.eaton.com/mgeops Network UPS Tools (NUT) Project Leader - http://www.networkupstools.org/ Debian Developer - http://www.debian.org Free Software Developer - http://arnaud.quette.free.fr/ -------------------------------------------------------------------------------- _______________________________________________ Nut-upsuser mailing list [email protected] http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser __________ Information from ESET Smart Security, version of virus signature database 4485 (20091006) __________ The message was checked by ESET Smart Security. http://www.eset.com __________ Information from ESET Smart Security, version of virus signature database 4486 (20091007) __________ The message was checked by ESET Smart Security. http://www.eset.com
_______________________________________________ Nut-upsuser mailing list [email protected] http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
