Displaying 20 results from an estimated 138 matches for "wdescriptorlength".
2020 Mar 07
2
Power Shield Defender 1200 - The Story Continues
Hi,
Sometime ago [ June 2018 ] I posted a message about getting trying to
get NUT to work with a Power Shield Defender 1200VA UPS. This model
appears in the HCL at https://networkupstools.org/stable-hcl.html
That UPS reported the following when queried using 'lsusb' on an iMac
running macOS [ 10.15 ]
Bus 001 Device 008: ID 0665:5161 Cypress Semiconductor USB to Serial
Device Descriptor:
2006 Feb 03
1
APC Smart-UPS 1000 RM USB problems with newhidups
...stem from the fact that the
Report Descriptor is much larger than any other UPS I've seen (61939 bytes).
Here is the quick fix that I put in libusb.c after getting the HID
descriptor, and before getting the Report descriptor, which seems to work
okay:
if (desc->wDescriptorLength > 4096) {
desc->wDescriptorLength = 4096;
}
I'm sure there is a better way to handle this. I'm just wondering if this
is okay to do, and if anyone had a better way to fix it. Thanks!
2020 Mar 07
0
Power Shield Defender 1200 - The Story Continues [HCL]
...the instability of the old model.
Further down in the lsusb output should be some information about the HID interface. A good distinguishing factor between Power Device Class (PDC) HID devices and simpler serial-over-HID devices is the size of the HID descriptor. What does the newer model show for wDescriptorLength? Here's an example for an APC:
Bus 006 Device 002: ID 051d:0003 American Power Conversion UPS
Device Descriptor:
[...]
bNumConfigurations 1
Configuration Descriptor:
[...]
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber...
2016 Jul 26
0
Two UPS with same vendor ID
...4 Sample HID
HID Device Descriptor:
bLength 9
bDescriptorType 33
bcdHID 1.00
bCountryCode 0 Not supported
bNumDescriptors 1
bDescriptorType 34 Report
wDescriptorLength 27
Report Descriptors:
** UNAVAILABLE **
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 3
Transfer Type Interrupt...
2017 Jun 07
2
Unable to use nut-2.7.4 with Eaton 5E1500I USB
...Interface 0
HID Device Descriptor:
bLength 9
bDescriptorType 33
bcdHID 1.10
bCountryCode 33 US
bNumDescriptors 1
bDescriptorType 34 Report
wDescriptorLength 549
Warning: incomplete report descriptor
Report Descriptor: (length is 9)
Item(Main ): (null), data=none
Item(Main ): (null), data=none
Item(Main ): (null), data=none
Item(Main ): (null), data=none
Item(...
2017 Jun 19
2
Unable to use nut-2.7.4 with Eaton 5E1500I USB
...Interface 0
HID Device Descriptor:
bLength 9
bDescriptorType 33
bcdHID 1.10
bCountryCode 33 US
bNumDescriptors 1
bDescriptorType 34 Report
wDescriptorLength 549
Warning: incomplete report descriptor
Report Descriptor: (length is 9)
Item(Main ): (null), data=none
Item(Main ): (null), data=none
Item(Main ): (null), data=none
Item(Main ): (null), data=none
Item(...
2009 Mar 04
3
Nut with megatec_usb
...erface 0
HID Device Descriptor:
bLength 9
bDescriptorType 33
bcdHID 1.00
bCountryCode 0 Not supported
bNumDescriptors 1
bDescriptorType 34 Report
wDescriptorLength 37
Report Descriptors:
** UNAVAILABLE **
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 3
Transfer Type Interrupt
Synch...
2009 Mar 04
3
Nut with megatec_usb
...erface 0
HID Device Descriptor:
bLength 9
bDescriptorType 33
bcdHID 1.00
bCountryCode 0 Not supported
bNumDescriptors 1
bDescriptorType 34 Report
wDescriptorLength 37
Report Descriptors:
** UNAVAILABLE **
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 3
Transfer Type Interrupt
Synch...
2017 Jun 13
2
Unable to use nut-2.7.4 with Eaton 5E1500I USB
...matters, the OS is a fully updated CentOS 6.9 and this
> (latest stable ) version of nut was packaged by me. The problem appears on
> any of the USB ports ( well, I tried the 2 in front and one in the back of
> the server ).
> >
> > lsusb -v reports:
> ...
> > wDescriptorLength 549
> > Warning: incomplete report descriptor
> > Report Descriptor: (length is 9)
> > Item(Main ): (null), data=none
>
> Because both NUT and lsusb are having trouble retrieving the HID Report
> Descriptor, I think the problem is at a lo...
2007 Feb 23
2
how do I find the association between a usb port and a /dev entry?
...iInterface 0
HID Device Descriptor:
bLength 9
bDescriptorType 33
bcdHID 1.00
bCountryCode 33 US
bNumDescriptors 1
bDescriptorType 34 Report
wDescriptorLength 820
Report Descriptors:
** UNAVAILABLE **
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 3
Transfer Type Interrupt
Synch...
2016 May 31
2
cannot get APC ups status change via usb cable from RaspberryPi
Hi All,
I get very strange UPS problem from RspberryPI mode B
(both version 2 and 3).
Here is our environment:
OS: Raspbian 8.0, Ubuntu 16.04 and Ubuntu 14.04
Platform: RaspberryPi Mode B version 2 and
version 3
NUT: tested version 2.6.3, 2.7.1
and 2.7.2 (from
2007 Nov 25
2
Nut problems with Centos and Belkin UPS
...iInterface 0
HID Device Descriptor:
bLength 9
bDescriptorType 33
bcdHID 1.11
bCountryCode 33 US
bNumDescriptors 1
bDescriptorType 34 Report
wDescriptorLength 801
Report Descriptors:
** UNAVAILABLE **
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 3
Transfer Type Interrupt
Synch...
2007 Jul 01
3
ST7 RS232 USB Bridge (STMicroelectronics) UPS
...iInterface 0
HID Device Descriptor:
bLength 9
bDescriptorType 33
bcdHID 1.10
bCountryCode 33 US
bNumDescriptors 1
bDescriptorType 34 Report
wDescriptorLength 29
Report Descriptors:
** UNAVAILABLE **
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 3
Transfer Type Interrupt
Synch...
2011 May 30
2
UPS Liebert GXT3 config
...erface 5
HID Device Descriptor:
bLength 9
bDescriptorType 33
bcdHID 1.00
bCountryCode 0 Not supported
bNumDescriptors 1
bDescriptorType 34 Report
wDescriptorLength 260
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type...
2017 Oct 11
4
Junda-tech
Hi,
I have an UPS with only the marking D1000 on it and it came with
Junda-Tech's UpsMate.
Its USB id is 3344:0025, which is apparently a microprocessor.
I've could get some of the HID interactions as described on the website,
but there are some outstanding.
Junda-Tech does not respond to any queries.
Does anybody else have the same or a similar UPS with more information?
What is the
2012 Jan 02
7
Problem with detecting "Mustek PowerMust 2000VA"
Hello,
i try to setup NUT service to read/control my UPS but without success.
Problem is when i try to start "/usr/local/ups/bin/upsdrvctl -DDDD -u
root start" i got:
/Network UPS Tools - UPS driver controller 2.6.2/
/ 0.000000/
/If you're not a NUT core developer, chances are that you're
told to enable debugging/
/to see why a driver
2008 Feb 01
2
Four UPS's via usb.
> Hello everyone. I try to connect four PowerMust 2000 ups's via usb to one
> computer using megatec_usb driver. But megatec_usb completly ignores port
> directive in ups.conf, I even try port = /dev/null and megatec_usb founds
> ups and it works.
The 'port' is not used for USB connected devices, it's only needed for
compatibility reasons.
> Problem is that
2007 Oct 31
0
NUT usbhid -- trying to write USB (sub)drivers
...evice Descriptor:
> bLength 9
> bDescriptorType 33
> bcdHID 1.00
> bCountryCode 0 Not supported
> bNumDescriptors 1
> bDescriptorType 34 Report
> wDescriptorLength 78
> Report Descriptors:
> ** UNAVAILABLE **
> Endpoint Descriptor:
> bLength 7
> bDescriptorType 5
> bEndpointAddress 0x81 EP 1 IN
> bmAttributes 3
> Transfer Ty...
2006 Apr 14
1
Mustek Powermust 600USB and newhidups
...erface 0
HID Device Descriptor:
bLength 9
bDescriptorType 33
bcdHID 1.11
bCountryCode 0 Not supported
bNumDescriptors 1
bDescriptorType 34 Report
wDescriptorLength 27
Report Descriptor: (length is 27)
Item(Global): Usage Page, data= [ 0x00 0xff ] 65280
(null)
Item(Local ): Usage, data= [ 0x01 ] 1
(null)
Item(Main ): Collection, data= [ 0x01 ] 1...
2023 Feb 20
1
Issue with two UPS APC managed from a single PC.
Is that with both UPSes on same machine?
A quick guess would be that insufficient data points to identify the device
are configured (vendorid, productid, serial...) in ups.conf, so both
drivers connect to the first match. I'd expect them to conflict and one
would die or both loop reconnecting, if both are running at once, though.
Also, which NUT version? Custom build from GitHub or an