Re: [Nut-upsuser] UPS Liebert GXT-3
Kris Jordan nut.kj at sagebrushnetworks.com writes: Marcelo Roccasalva wrote, On 3/1/2013 12:10 PM: On Thu, Feb 28, 2013 at 6:17 PM, Marcelo Roccasalva roccas at gmail.com wrote: On Tue, Feb 26, 2013 at 10:56 PM, Charles Lepple clepple at gmail.com wrote: On Feb 21, 2013, at 6:21 PM, Marcelo Roccasalva wrote: I'll try the windows monitoring program tomorrow... Any luck? Haven't tried... An Emerson support person sent me an updated version of their software, which offers me an USB port to connect but it fails to communicate with the UPS... Tomorrow will be windows tested... windows xp software tells me I need an UPS connected for the software to work... The usb port has to be damaged... Thanks for your support. Does Windows even notice the USB connection being made? Try resetting the UPS by unplugging, disconnecting batteries, and pressing/holding all the buttons to make sure the UPS is completely discharged. Does that help? Hi all, if I can just inject into this thread - I am willing to help if I can... I just purchased an Emerson/Liebert PSA UPS with USB interface and wanted it to power my NAS Box (running FreeNAS 8 - a FreeBSD implementation), and have found similar issues with my UPS. From reading around and from what I can see for myself, it does appear that the underlying problem is that the HID descriptor is 255 bytes and that somewhere in the USB driver chain there is code that expects it to be 255 bytes or less and gives up when it comes across something larger. My issue is that I don't understand enough about FreeBSD USB or NUT in order to ascertain what needs fixing, but I am confident that the root cause is the length of the HID Descriptor. So, is the problem in NUT, or is the problem in the underlying USB drivers? How do we find out, and what do we do to fix? I will try and get some output from my UPS when I get home tonight and will post back. Best Regards, Paul Smith ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] UPS Liebert GXT-3
On Thu, Feb 28, 2013 at 6:17 PM, Marcelo Roccasalva roc...@gmail.com wrote: On Tue, Feb 26, 2013 at 10:56 PM, Charles Lepple clep...@gmail.com wrote: On Feb 21, 2013, at 6:21 PM, Marcelo Roccasalva wrote: I'll try the windows monitoring program tomorrow... Any luck? Haven't tried... An Emerson support person sent me an updated version of their software, which offers me an USB port to connect but it fails to communicate with the UPS... Tomorrow will be windows tested... windows xp software tells me I need an UPS connected for the software to work... The usb port has to be damaged... Thanks for your support. -- Marcelo ¿No será acaso que esta vida moderna está teniendo más de moderna que de vida? (Mafalda) ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] UPS Liebert GXT-3
Marcelo Roccasalva wrote, On 3/1/2013 12:10 PM: On Thu, Feb 28, 2013 at 6:17 PM, Marcelo Roccasalva roc...@gmail.com wrote: On Tue, Feb 26, 2013 at 10:56 PM, Charles Lepple clep...@gmail.com wrote: On Feb 21, 2013, at 6:21 PM, Marcelo Roccasalva wrote: I'll try the windows monitoring program tomorrow... Any luck? Haven't tried... An Emerson support person sent me an updated version of their software, which offers me an USB port to connect but it fails to communicate with the UPS... Tomorrow will be windows tested... windows xp software tells me I need an UPS connected for the software to work... The usb port has to be damaged... Thanks for your support. Does Windows even notice the USB connection being made? Try resetting the UPS by unplugging, disconnecting batteries, and pressing/holding all the buttons to make sure the UPS is completely discharged. Does that help? ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] UPS Liebert GXT-3
On Tue, Feb 26, 2013 at 10:56 PM, Charles Lepple clep...@gmail.com wrote: On Feb 21, 2013, at 6:21 PM, Marcelo Roccasalva wrote: I'll try the windows monitoring program tomorrow... Any luck? Haven't tried... An Emerson support person sent me an updated version of their software, which offers me an USB port to connect but it fails to communicate with the UPS... Tomorrow will be windows tested... -- Charles Lepple clepple@gmail -- Marcelo ¿No será acaso que esta vida moderna está teniendo más de moderna que de vida? (Mafalda) ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] UPS Liebert GXT-3
On Feb 21, 2013, at 6:21 PM, Marcelo Roccasalva wrote: I'll try the windows monitoring program tomorrow... Any luck? -- Charles Lepple clepple@gmail ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] UPS Liebert GXT-3
On Thu, Feb 21, 2013 at 12:56 AM, Charles Lepple clep...@gmail.com wrote:
On Feb 20, 2013, at 12:37 PM, Marcelo Roccasalva wrote:
I'm not sure what the udev rule is trying to achieve but I installed
the following rule:
ACTION==add, SUBSYSTEM==usb, ATTR{idVendor}==10af,
ATTR{idProduct}==0008, MODE=664, GROUP=dialout
to get the following device:
crw-rw-r--. 1 root dialout 189, 385 Feb 20 14:27 /dev/bus/usb/004/002
It's setting the Unix group to dialout, and setting those permissions. It
appears to have worked, although we have another issue.
Excelent, it did...
0.212098 Checking device (10AF/0008) (004/002)
0.215980 - VendorID: 10af
0.215993 - ProductID: 0008
0.215999 - Manufacturer: unknown
0.216006 - Product: unknown
0.216012 - Serial Number: unknown
0.216018 - Bus: 004
0.216023 Trying to match device
0.216068 Device matches
0.217972 Unable to get HID descriptor (error sending control
message: Protocol error)
0.217986 HID descriptor length 260
0.218978 Unable to get Report descriptor: Protocol error
^ This is NUT checking your UPS, and not being able to get enough information
to continue. Can you try running lsusb -vvv -d 10af:0008 as root? We're
looking for something more than Report Descriptors: ** UNAVAILABLE **.
# lsusb -vvv -d 10af:0008
Bus 004 Device 002: ID 10af:0008 Liebert Corp. PowerSure Interactive UPS
Device Descriptor:
bLength18
bDescriptorType 1
bcdUSB 1.10
bDeviceClass0 (Defined at Interface level)
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 8
idVendor 0x10af Liebert Corp.
idProduct 0x0008 PowerSure Interactive UPS
bcdDevice0.00
iManufacturer 1
iProduct2
iSerial 3
bNumConfigurations 1
OTG Descriptor:
bLength 3
bDescriptorType 9
bmAttributes 0x00
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 37
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 4
bmAttributes 0x40
(Missing must-be-set bit!)
Self Powered
MaxPower0mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber0
bAlternateSetting 0
bNumEndpoints 1
bInterfaceClass 3 Human Interface Device
bInterfaceSubClass 0 No Subclass
bInterfaceProtocol 0 None
iInterface 5
HID Device Descriptor:
bLength 9
bDescriptorType33
bcdHID 1.00
bCountryCode0 Not supported
bNumDescriptors 1
bDescriptorType34 Report
wDescriptorLength 260
Warning: incomplete report descriptor
Report Descriptor: (length is 99)
Item(Main ): (null), data=none
Item(Main ): (null), data=none
Item(Main ): (null), data=none
Item(Main ): (null), data=none
Item(Main ): (null), data=none
Item(Main ): (null), data=none
Item(Main ): (null), data=none
Item(Main ): (null), data=none
Item(Main ): (null), data=none
Item(Main ): (null), data=none
Item(Main ): (null), data=none
Item(Main ): (null), data=none
Item(Main ): (null), data=none
Item(Main ): (null), data=none
Item(Main ): (null), data=none
Item(Main ): (null), data=none
Item(Main ): (null), data=none
Item(Main ): (null), data=none
Item(Main ): (null), data=none
Item(Main ): (null), data=none
Item(Main ): (null), data=none
Item(Main ): (null), data=none
Item(Main ): (null), data=none
Item(Main ): (null), data=none
Item(Main ): Collection, data=none
Vendor defined
Item(reserved): (null), data= [ 0x90 0x00 0x00 0x00 ] 144
Item(Main ): (null), data=none
Item(Main ): (null), data=none
Item(Main ): (null), data=none
Item(Global): (null), data= [ 0xbb 0x85 0xff 0x7f ] 2147452347
Item(Main ): (null), data=none
Item(Main ): (null), data=none
Item(reserved): (null), data=none
Item(Main ): Feature, data= [ 0x95 0x84 ] 33941
Constant Array Relative No_Wrap Non_Linear
Preferred_State No_Null_Position Volatile Bitfield
Item(reserved): (null), data= [ 0x7f ] 127
Item(Main ): (null), data=none
Item(Main ): (null), data=none
Re: [Nut-upsuser] UPS Liebert GXT-3
On Feb 21, 2013, at 3:18 PM, Marcelo Roccasalva wrote: wDescriptorLength 260 Warning: incomplete report descriptor Report Descriptor: (length is 99) This is not good. I don't know much about this UPS - if it has a serial port, have you ever gotten that to work? (Some other vendors tend to only support using one interface after the UPS starts up.) Also, are there any lines in dmesg that seem to refer to this UPS? If the NUT driver is doing something that the UPS firmware doesn't expect during initialization, we might be able to attack this from another angle by capturing the communication with the vendor monitoring program. (However, it is disconcerting that standard USB queries for retrieving descriptors are not working properly.) -- Charles Lepple clepple@gmail ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] UPS Liebert GXT-3
On Thu, Feb 21, 2013 at 7:35 PM, Charles Lepple clep...@gmail.com wrote: On Feb 21, 2013, at 3:18 PM, Marcelo Roccasalva wrote: wDescriptorLength 260 Warning: incomplete report descriptor Report Descriptor: (length is 99) This is not good. I don't know much about this UPS - if it has a serial port, have you ever gotten that to work? (Some other vendors tend to only support using one interface after the UPS starts up.) Tomorrow I'll be there, but I think there's no serial port... Also, are there any lines in dmesg that seem to refer to this UPS? nope... If the NUT driver is doing something that the UPS firmware doesn't expect during initialization, we might be able to attack this from another angle by capturing the communication with the vendor monitoring program. (However, it is disconcerting that standard USB queries for retrieving descriptors are not working properly.) This was the start of the story: the vendor monitoring program installer doesn't offer me the usb connection option (among other restrictions)... Vendor support hasn't solved their issue... I'll try the windows monitoring program tomorrow... -- Marcelo ¿No será acaso que esta vida moderna está teniendo más de moderna que de vida? (Mafalda) ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] UPS Liebert GXT-3
On Wed, Feb 20, 2013 at 12:19 AM, Kris Jordan
nut...@sagebrushnetworks.com wrote:
Charles Lepple wrote, On 2/19/2013 6:35 PM:
On Feb 19, 2013, at 3:07 PM, Marcelo Roccasalva wrote:
Bus 004 Device 002: ID 10af:0008 Liebert Corp. PowerSure Interactive UPS
Not sure if you tried this yet, but what if you set productid=0008 in
ups.conf? You will also need to temporarily start the driver with -u root
or add this vendor/product ID pair to the udev file (sorry, not sure where
that lives on CentOS) since that isn't one of the known USB Product IDs.
/etc/udev/rules.d
Centos5 will require syntax alternations, if using 52-nut-usbups.rules from
NUT 2.6.5.
I'm not sure what the udev rule is trying to achieve but I installed
the following rule:
ACTION==add, SUBSYSTEM==usb, ATTR{idVendor}==10af,
ATTR{idProduct}==0008, MODE=664, GROUP=dialout
to get the following device:
crw-rw-r--. 1 root dialout 189, 385 Feb 20 14:27 /dev/bus/usb/004/002
I edited /etc/ups/ups.conf:
[liebert]
driver=usbhid-ups
port=/dev/bus/usb/004/002
productid=0008
# usbhid-ups -a liebert -DD
Network UPS Tools - Generic HID driver 0.37 (2.6.5)
USB communication driver 0.31
0.00 debug level is '2'
0.001512 upsdrv_initups...
0.211700 Checking device (1D6B/0001) (008/001)
0.211740 - VendorID: 1d6b
0.211748 - ProductID: 0001
0.211754 - Manufacturer: unknown
0.211760 - Product: unknown
0.211765 - Serial Number: unknown
0.211771 - Bus: 008
0.211777 Trying to match device
0.211798 Device does not match - skipping
0.211809 Checking device (1D6B/0001) (007/001)
0.211831 - VendorID: 1d6b
0.211838 - ProductID: 0001
0.211844 - Manufacturer: unknown
0.211850 - Product: unknown
0.211856 - Serial Number: unknown
0.211861 - Bus: 007
0.211867 Trying to match device
0.211874 Device does not match - skipping
0.211882 Checking device (/) (006/002)
0.211904 - VendorID:
0.211911 - ProductID:
0.211917 - Manufacturer: unknown
0.211923 - Product: unknown
0.211929 - Serial Number: unknown
0.211934 - Bus: 006
0.211940 Trying to match device
0.211947 Device does not match - skipping
0.211955 Checking device (1D6B/0001) (006/001)
0.211976 - VendorID: 1d6b
0.211983 - ProductID: 0001
0.211989 - Manufacturer: unknown
0.211995 - Product: unknown
0.212000 - Serial Number: unknown
0.212006 - Bus: 006
0.212012 Trying to match device
0.212018 Device does not match - skipping
0.212027 Checking device (1D6B/0001) (005/001)
0.212047 - VendorID: 1d6b
0.212054 - ProductID: 0001
0.212060 - Manufacturer: unknown
0.212066 - Product: unknown
0.212072 - Serial Number: unknown
0.212078 - Bus: 005
0.212083 Trying to match device
0.212090 Device does not match - skipping
0.212098 Checking device (10AF/0008) (004/002)
0.215980 - VendorID: 10af
0.215993 - ProductID: 0008
0.215999 - Manufacturer: unknown
0.216006 - Product: unknown
0.216012 - Serial Number: unknown
0.216018 - Bus: 004
0.216023 Trying to match device
0.216068 Device matches
0.217972 Unable to get HID descriptor (error sending control
message: Protocol error)
0.217986 HID descriptor length 260
0.218978 Unable to get Report descriptor: Protocol error
0.219015 Checking device (1D6B/0001) (004/001)
0.219052 - VendorID: 1d6b
0.219059 - ProductID: 0001
0.219065 - Manufacturer: unknown
0.219071 - Product: unknown
0.219077 - Serial Number: unknown
0.219083 - Bus: 004
0.219089 Trying to match device
0.219099 Device does not match - skipping
0.219109 Checking device (1D6B/0001) (003/001)
0.219132 - VendorID: 1d6b
0.219139 - ProductID: 0001
0.219145 - Manufacturer: unknown
0.219151 - Product: unknown
0.219157 - Serial Number: unknown
0.219163 - Bus: 003
0.219168 Trying to match device
0.219175 Device does not match - skipping
0.219185 Checking device (1D6B/0002) (002/001)
0.219207 - VendorID: 1d6b
0.219214 - ProductID: 0002
0.219220 - Manufacturer: unknown
0.219226 - Product: unknown
0.219232 - Serial Number: unknown
0.219238 - Bus: 002
0.219244 Trying to match device
0.219250 Device does not match - skipping
0.219259 Checking device (1D6B/0002) (001/001)
0.219282 - VendorID: 1d6b
0.219289 - ProductID: 0002
0.219295 - Manufacturer: unknown
0.219301 - Product: unknown
0.219307 - Serial Number: unknown
0.219313 - Bus: 001
0.219318 Trying to match device
0.219325 Device does not match - skipping
0.219333 No appropriate HID device found
0.219342 No matching HID UPS found
Most of the time, I don't know what I'm doing, so any insight would be
appreciated...
--
Marcelo
¿No será acaso que esta vida moderna está teniendo más de moderna que de
vida? (Mafalda)
___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
Re: [Nut-upsuser] UPS Liebert GXT-3
On Feb 20, 2013, at 12:37 PM, Marcelo Roccasalva wrote:
I'm not sure what the udev rule is trying to achieve but I installed
the following rule:
ACTION==add, SUBSYSTEM==usb, ATTR{idVendor}==10af,
ATTR{idProduct}==0008, MODE=664, GROUP=dialout
to get the following device:
crw-rw-r--. 1 root dialout 189, 385 Feb 20 14:27 /dev/bus/usb/004/002
It's setting the Unix group to dialout, and setting those permissions. It
appears to have worked, although we have another issue.
0.212098 Checking device (10AF/0008) (004/002)
0.215980 - VendorID: 10af
0.215993 - ProductID: 0008
0.215999 - Manufacturer: unknown
0.216006 - Product: unknown
0.216012 - Serial Number: unknown
0.216018 - Bus: 004
0.216023 Trying to match device
0.216068 Device matches
0.217972 Unable to get HID descriptor (error sending control
message: Protocol error)
0.217986 HID descriptor length 260
0.218978 Unable to get Report descriptor: Protocol error
^ This is NUT checking your UPS, and not being able to get enough information
to continue. Can you try running lsusb -vvv -d 10af:0008 as root? We're
looking for something more than Report Descriptors: ** UNAVAILABLE **.
--
Charles Lepple
clepple@gmail
___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser
[Nut-upsuser] UPS Liebert GXT-3
Hello, I (now) own an Emerson Liebert GXT3 6000VA conected via USB. I've searched the web trying to configure nut (nut-2.6.5-1.el6.x86_64 epel rpm on CentOS 6.3) to monitor the UPS, but couldn't find a successful configuration. I'm running kernel 2.6.32-279.14.1.el6.x86_64. The UPS is connected with an USB cable: Bus 004 Device 002: ID 10af:0008 Liebert Corp. PowerSure Interactive UPS Device Descriptor: bLength18 bDescriptorType 1 bcdUSB 1.10 bDeviceClass0 (Defined at Interface level) bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize0 8 idVendor 0x10af Liebert Corp. idProduct 0x0008 PowerSure Interactive UPS bcdDevice0.00 iManufacturer 1 iProduct2 iSerial 3 bNumConfigurations 1 OTG Descriptor: bLength 3 bDescriptorType 9 bmAttributes 0x00 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 37 bNumInterfaces 1 bConfigurationValue 1 iConfiguration 4 bmAttributes 0x40 (Missing must-be-set bit!) Self Powered MaxPower0mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber0 bAlternateSetting 0 bNumEndpoints 1 bInterfaceClass 3 Human Interface Device bInterfaceSubClass 0 No Subclass bInterfaceProtocol 0 None iInterface 5 HID Device Descriptor: bLength 9 bDescriptorType33 bcdHID 1.00 bCountryCode0 Not supported bNumDescriptors 1 bDescriptorType34 Report wDescriptorLength 260 Report Descriptors: ** UNAVAILABLE ** Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x81 EP 1 IN bmAttributes3 Transfer TypeInterrupt Synch Type None Usage Type Data wMaxPacketSize 0x0008 1x 8 bytes bInterval 32 Device Status: 0x (Bus Powered) Any help would be very apreciated! -- Marcelo ¿No será acaso que esta vida moderna está teniendo más de moderna que de vida? (Mafalda) ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] UPS Liebert GXT-3
On Feb 19, 2013, at 3:07 PM, Marcelo Roccasalva wrote: Bus 004 Device 002: ID 10af:0008 Liebert Corp. PowerSure Interactive UPS Not sure if you tried this yet, but what if you set productid=0008 in ups.conf? You will also need to temporarily start the driver with -u root or add this vendor/product ID pair to the udev file (sorry, not sure where that lives on CentOS) since that isn't one of the known USB Product IDs. -- Charles Lepple clepple@gmail ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] UPS Liebert GXT-3
Charles Lepple wrote, On 2/19/2013 6:35 PM: On Feb 19, 2013, at 3:07 PM, Marcelo Roccasalva wrote: Bus 004 Device 002: ID 10af:0008 Liebert Corp. PowerSure Interactive UPS Not sure if you tried this yet, but what if you set productid=0008 in ups.conf? You will also need to temporarily start the driver with -u root or add this vendor/product ID pair to the udev file (sorry, not sure where that lives on CentOS) since that isn't one of the known USB Product IDs. /etc/udev/rules.d Centos5 will require syntax alternations, if using 52-nut-usbups.rules from NUT 2.6.5. ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser
