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

2017-06-13 Thread Arnaud Quette 
2017-04-30 13:38 GMT+02:00 Jim Klimov :

> On April 28, 2017 9:11:59 AM GMT+03:00, "Александр Борисович" <
> vtk-al...@mail.ru> wrote:
> >Hello all!
>

privet Alexander


> >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:  at usbus0
> >uhid0:  >addr 3> on usbus0
> >uhid0:  >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.00 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.00 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.00 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@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?
>

to complete Jim's answer (you should really try 2.7.4):
* as per NUT HCL, recent Powercom units are supported through USB with
usbhid-ups, so that path is still to be followed
http://networkupstools.org/stable-hcl.html?manufacturer=Powercom

* the actual issue is around "Unable to get Report descriptor: Input/output
error"
I'd be interested in a test in debug level 5 (i.e. -D) to get a bit
more visibility

cheers
Arno
-- 
Eaton Data Center Automation Solutions - Opensource Leader -
http://42ity.org
NUT (Network UPS Tools) Project Leader - http://www.networkupstools.org
Debian Developer - http://www.debian.org
Free Software Developer - http://arnaud.quette.fr
___
Nut-upsdev mailing list
Nut-upsdev@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsdev

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

2017-05-01 Thread Александр Борисович 

>Sunday, 30 april 2017, 14:42 +03:00 Jim Klimov  wrote:
>
>On April 28, 2017 9:11:59 AM GMT+03:00, "Александр Борисович" < 
>vtk-al...@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:  at usbus0
>>uhid0: >addr 3> on usbus0
>>uhid0: >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.00 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.00 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.00 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@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
Yes. I've downloaded new version of nut and compiled it but it gave no result. 
I tried all *usb drivers:
my simple usb.conf:
[BNT2000]
driver = blazer_usb
#driver = bcmxcp_usb
#driver = nutdrv_atcl_usb
#driver = richcomm_usb
#driver = riello_usb
#driver = tripplite_usb
port = auto
desc = "POWERCOM BNT-2000AP"

And here is the results:
# bcmxcp_usb -a BNT2000 -DDD
Network UPS Tools - BCMXCP UPS driver 0.31 (2.7.4)
USB communication subdriver 0.22
0.00 debug level is '3'
0.000509 entering nutusb_open()
0.000669 Can't open POWERWARE USB device
0.000678 Can't open POWERWARE USB device
0.000682 Can't open POWERWARE USB device
0.000686 Can't open POWERWARE USB device
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).
0.000700 Fatal error: unusable configuration

# blazer_usb -a BNT2000 -DDD
Network UPS Tools - Megatec/Q1 protocol USB driver 0.12 (2.7.4)
0.00 debug level is '3'
0.000618 Checking device (0D9F/0004) (/dev/usb//dev/ugen0.3)
0.030823 - VendorID: 0d9f
0.030831 - ProductID: 0004
0.030835 - Manufacturer: unknown
0.030838 - Product: unknown
0.030842 - Serial Number: unknown
0.030846 - Bus: /dev/usb
0.030850 - Device release number: 0001
0.030854 Trying to match device
0.030859 Device does not match - skipping
0.030873 No appropriate HID device found
0.030880 No supported devices found. Please check your device availability

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

2017-04-30 Thread Jim Klimov 
On April 28, 2017 9:11:59 AM GMT+03:00, "Александр Борисович" 
 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:  at usbus0
>uhid0: addr 3> on usbus0
>uhid0: 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.00 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.00 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.00 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@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

___
Nut-upsdev mailing list
Nut-upsdev@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsdev

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

2017-04-28 Thread Александр Борисович 
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:  at usbus0
uhid0:  on 
usbus0
uhid0:  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.00 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.00 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.00 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@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsdev