[Nut-upsdev] Powercom BNT-2000AP(USB)

[Jim Klimov]

On April 28, 2017 9:11:59 AM GMT+03:00, "Александр Борисович" <vtk-alexb at mail.ru> wrote:
>Hello all!
>
>Some days ago we received new UPS Powercom BNT-2000AP with USB
>interface to replace an old staff and I've spent four last days trying
>to connect it with NUT. I have a FreeBSD 8.4 box with NUT 2.7.2.
>
># dmesg|grep -i powercom
>ugen0.3: <POWERCOM Co.,LTD> at usbus0
>uhid0: <POWERCOM Co.,LTD HID UPS Battery, class 0/0, rev 1.10/0.01,
>addr 3> on usbus0
>uhid0: <POWERCOM Co.,LTD HID UPS Battery, class 0/0, rev 1.10/0.01,
>addr 3> on usbus0
> 
>I know that it's absent in hardware list, but I can't change anything
>now for nearest 2-3 months. And I don't want to leave server
>unmanaged. 
>I tried all powercom drivers and all of them were unsuccsessful.
># /usr/local/libexec/nut/powercom -a BNT2000 -x type=BNT-other -x
>port=/dev/ugen0.3 -DDD
>Network UPS Tools - PowerCom protocol UPS driver 0.14 (2.7.2)
>   0.000000 debug level is '3'
>   0.000670 tcgetattr(/dev/ugen0.3): Inappropriate ioctl for device
>I believe that it's right...
>
>The "best" results I received with usbhid-ups driver:
># /usr/local/libexec/nut/usbhid-ups -a BNT2000 -DDD
>Network UPS Tools - Generic HID driver 0.38 (2.7.2)
>USB communication driver 0.32
>   0.000000 debug level is '3'
>   0.000557 upsdrv_initups...
>   0.000744 Checking device (0D9F/0004) (/dev/usb//dev/ugen0.3)
>   0.031233 - VendorID: 0d9f
>   0.031240 - ProductID: 0004
>   0.031245 - Manufacturer: unknown
>   0.031248 - Product: unknown
>   0.031252 - Serial Number: unknown
>   0.031256 - Bus: /dev/usb
>   0.031260 Trying to match device
>   0.031268 Device matches
>   0.080235 Unable to get HID descriptor (Unknown error)
>   0.080248 HID descriptor, method 2: (9 bytes) => 09 21 00 01 00 01 22
>c6 03
>   0.080252 HID descriptor length 966
>   0.090278 Unable to get Report descriptor: Input/output error
>   0.090299 No appropriate HID device found
>   0.090306 No matching HID UPS found
>
>Someone recommended me to try driver megatec smth like:
>[ups]
>    driver = megatec_usb
>    port = "/dev/ugen0.2"
>
>But there is no driver megatec_usb nither in driver.list no in the
>hardware list on the site. However, I tried
>
># /usr/local/libexec/nut/blazer_usb -a BNT2000 -x protocol=megatec -DDD
>Network UPS Tools - Megatec/Q1 protocol USB driver 0.11 (2.7.2)
>   0.000000     debug level is '3'
>   0.000634     Checking device (0D9F/0004) (/dev/usb//dev/ugen0.3)
>   0.030633     - VendorID: 0d9f
>   0.030641     - ProductID: 0004
>   0.030645     - Manufacturer: unknown
>   0.030649     - Product: unknown
>   0.030653     - Serial Number: unknown
>   0.030657     - Bus: /dev/usb
>   0.030661     Trying to match device
>   0.030666     Device does not match - skipping
>   0.030680     No appropriate HID device found
>   0.030686     No supported devices found.
>
>Can anybody help me? I'm ready to provide any data/information on your
>request and even to become a tester! :)
>-- 
>Thnx! Alexander
>_______________________________________________
>Nut-upsdev mailing list
>Nut-upsdev at lists.alioth.debian.org
>http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsdev

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?

Jim
--
Typos courtesy of K-9 Mail on my Redmi Android