Hi Greg<br><br>first, a thank to Kjell too...<br><br><div class="gmail_quote">2009/7/12 Greg Vickers <span dir="ltr"><<a href="mailto:daehenoc@optusnet.com.au" target="_blank">daehenoc@optusnet.com.au</a>></span><br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Hi Kjell,<div><div></div><div><br>
<br>
Kjell Claesson wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Hi all,<br>
</blockquote>
Hi Greg,<br>
<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
I've got a Powerware 5110 UPS that I'm trying to set up with nut in<br>
Ubuntu. Â I've installed nut and configured the first two files:<br>
<br>
$ cat /etc/nut/nut.conf<br>
MODE=standalone<br>
$ cat /etc/nut/ups.conf<br>
[pw5110]<br>
    driver = bcmxcp_usb<br>
    port = auto<br>
# Â Â Â port = /dev/bus/usb/002/002<br>
</blockquote>
Yes the port should be auto.<br>
And if you use the latest libusb you should have a device<br>
at /dev/bus/usb/002/002 that you have found.<br>
 <br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
When I try to test this configuration with the following command:<br>
$ sudo upsdrvctl start pw5110<br>
Network UPS Tools - UPS driver controller 2.4.1<br>
Network UPS Tools - BCMXCP UPS driver 0.21 (2.4.1)<br>
USB communication subdriver 0.17<br>
Can't set POWERWARE USB configuration<br>
Unable to find POWERWARE UPS device on USB bus<br>
<br>
</blockquote>
<br>
To make a real test that it read the usb you can do the following.<br>
Set libusb debug to 3.<br>
sudo export LIBUSB_DEBUG=3<br>
<br>
Then run the driver in debug (not by upsdrvctl).<br>
sudo /path/to/bcmxcp_usb -DD -u -a pw5110<br>
<br>
Now it should spit out some info. You end it by ctrl-c.<br>
<br>
Report back and we can have a look.<br>
<br>
We may have a bug here, but it is not confirmed as our tests<br>
does not reveal it.<br>
</blockquote>
<br></div></div>
After leaving my Ubuntu host overnight, I've turned it on and the nut daemon was running when I tried the above check. Â I stopped that daemon and the above test worked just fine! Â I didn't change anything and now it's working just fine.<br>
<br>
Thank you for the information about the debug test! Â All OK now! :)<br>
</blockquote><div><br>well, ok now, but there is still something under the hood!<br>my guess is that the udev update change introduced by Scott James doesn't fully refresh the udev rights.<br>I've not taken the time to validate it though, so mea culpa.<br>
the result is basically that if you don't unplug/replug your device or reboot your system after nut installation, the udev rule is not applied.<br><br>I'll try to check that tomorrow, and make some more progress on 2.4.1-4, which will be a major Debian update.<br>
</div></div><br>Arnaud<br>-- <br>Linux / Unix Expert R&D - Eaton - <a href="http://www.eaton.com/mgeops" target="_blank">http://www.eaton.com/mgeops</a><br>Network UPS Tools (NUT) Project Leader - <a href="http://www.networkupstools.org/" target="_blank">http://www.networkupstools.org/</a><br>
Debian Developer - <a href="http://www.debian.org" target="_blank">http://www.debian.org</a><br>Free Software Developer - <a href="http://arnaud.quette.free.fr/" target="_blank">http://arnaud.quette.free.fr/</a><br>--<br>
Conseiller Municipal - Saint Bernard du Touvet -<br>
<a href="http://www.SaintBernardDuTouvet.fr/" target="_blank">http://www.SaintBernardDuTouvet.fr/</a><br>en charge de la Communication, de l'Informatique et des Technologies<br>