<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">2017-04-30 13:38 GMT+02:00 Jim Klimov <span dir="ltr"><<a target="_blank" href="mailto:jimklimov@cos.ru">jimklimov@cos.ru</a>></span>:<br><blockquote style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex" class="gmail_quote">On April 28, 2017 9:11:59 AM GMT+03:00, "Александр Борисович" <<a href="mailto:vtk-alexb@mail.ru">vtk-alexb@mail.ru</a>> wrote:<br>
>Hello all!<br></blockquote><div><br></div><div>privet Alexander</div><div> </div><blockquote style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex" class="gmail_quote">
>Some days ago we received new UPS Powercom BNT-2000AP with USB<br>
>interface to replace an old staff and I've spent four last days trying<br>
>to connect it with NUT. I have a FreeBSD 8.4 box with NUT 2.7.2.<br>
><br>
># dmesg|grep -i powercom<br>
>ugen0.3: <POWERCOM Co.,LTD> at usbus0<br>
>uhid0: <POWERCOM Co.,LTD HID UPS Battery, class 0/0, rev 1.10/0.01,<br>
>addr 3> on usbus0<br>
>uhid0: <POWERCOM Co.,LTD HID UPS Battery, class 0/0, rev 1.10/0.01,<br>
>addr 3> on usbus0<br>
> <br>
>I know that it's absent in hardware list, but I can't change anything<br>
>now for nearest 2-3 months. And I don't want to leave server<br>
>unmanaged. <br>
>I tried all powercom drivers and all of them were unsuccsessful.<br>
># /usr/local/libexec/nut/<wbr>powercom -a BNT2000 -x type=BNT-other -x<br>
>port=/dev/ugen0.3 -DDD<br>
>Network UPS Tools - PowerCom protocol UPS driver 0.14 (2.7.2)<br>
> 0.000000 debug level is '3'<br>
> 0.000670 tcgetattr(/dev/ugen0.3): Inappropriate ioctl for device<br>
>I believe that it's right...<br>
><br>
>The "best" results I received with usbhid-ups driver:<br>
># /usr/local/libexec/nut/usbhid-<wbr>ups -a BNT2000 -DDD<br>
>Network UPS Tools - Generic HID driver 0.38 (2.7.2)<br>
>USB communication driver 0.32<br>
> 0.000000 debug level is '3'<br>
> 0.000557 upsdrv_initups...<br>
> 0.000744 Checking device (0D9F/0004) (/dev/usb//dev/ugen0.3)<br>
> 0.031233 - VendorID: 0d9f<br>
> 0.031240 - ProductID: 0004<br>
> 0.031245 - Manufacturer: unknown<br>
> 0.031248 - Product: unknown<br>
> 0.031252 - Serial Number: unknown<br>
> 0.031256 - Bus: /dev/usb<br>
> 0.031260 Trying to match device<br>
> 0.031268 Device matches<br>
> 0.080235 Unable to get HID descriptor (Unknown error)<br>
> 0.080248 HID descriptor, method 2: (9 bytes) => 09 21 00 01 00 01 22<br>
>c6 03<br>
> 0.080252 HID descriptor length 966<br>
> 0.090278 Unable to get Report descriptor: Input/output error<br>
> 0.090299 No appropriate HID device found<br>
> 0.090306 No matching HID UPS found<br>
><br>
>Someone recommended me to try driver megatec smth like:<br>
>[ups]<br>
> driver = megatec_usb<br>
> port = "/dev/ugen0.2"<br>
><br>
>But there is no driver megatec_usb nither in driver.list no in the<br>
>hardware list on the site. However, I tried<br>
><br>
># /usr/local/libexec/nut/blazer_<wbr>usb -a BNT2000 -x protocol=megatec -DDD<br>
>Network UPS Tools - Megatec/Q1 protocol USB driver 0.11 (2.7.2)<br>
> 0.000000 debug level is '3'<br>
> 0.000634 Checking device (0D9F/0004) (/dev/usb//dev/ugen0.3)<br>
> 0.030633 - VendorID: 0d9f<br>
> 0.030641 - ProductID: 0004<br>
> 0.030645 - Manufacturer: unknown<br>
> 0.030649 - Product: unknown<br>
> 0.030653 - Serial Number: unknown<br>
> 0.030657 - Bus: /dev/usb<br>
> 0.030661 Trying to match device<br>
> 0.030666 Device does not match - skipping<br>
> 0.030680 No appropriate HID device found<br>
> 0.030686 No supported devices found.<br>
><br>
>Can anybody help me? I'm ready to provide any data/information on your<br>
>request and even to become a tester! :)<br>
>-- <br>
>Thnx! Alexander<br>
>_____________________________<wbr>__________________<br>
>Nut-upsdev mailing list<br>
><a href="mailto:Nut-upsdev@lists.alioth.debian.org">Nut-upsdev@lists.alioth.<wbr>debian.org</a><br>
><a target="_blank" rel="noreferrer" href="http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsdev">http://lists.alioth.debian.<wbr>org/cgi-bin/mailman/listinfo/<wbr>nut-upsdev</a><br>
<br>
Just in case, one thing that stands out in your post is nut-2.7.2. It is pretty old, meaning that newer releases or the github master can have more HW support. Did you try (or can you build and retry) your experiments with this newer code?<br clear="all"></blockquote></div><br></div><div class="gmail_extra">to complete Jim's answer (you should really try 2.7.4):<br></div><div class="gmail_extra">* as per NUT HCL, recent Powercom units are supported through USB with usbhid-ups, so that path is still to be followed<br></div><div class="gmail_extra"><a href="http://networkupstools.org/stable-hcl.html?manufacturer=Powercom">http://networkupstools.org/stable-hcl.html?manufacturer=Powercom</a><br><br></div><div class="gmail_extra">* the actual issue is around "Unable to get Report descriptor: Input/output error"<br></div><div class="gmail_extra">I'd be interested in a test in debug level 5 (i.e. -DDDDD) to get a bit more visibility<br></div><div class="gmail_extra"><br></div><div class="gmail_extra">cheers<br></div><div class="gmail_extra">Arno<br></div><div class="gmail_extra">-- <br><div class="gmail_signature">Eaton Data Center Automation Solutions - Opensource Leader - <a target="_blank" href="http://42ity.org">http://42ity.org</a><br>NUT (Network UPS Tools) Project Leader - <a target="_blank" href="http://www.networkupstools.org">http://www.networkupstools.org</a><br>Debian Developer - <a target="_blank" href="http://www.debian.org">http://www.debian.org</a><br>Free Software Developer - <a target="_blank" href="http://arnaud.quette.fr">http://arnaud.quette.fr</a><br></div>
</div></div>