Installed a new Tripplite Smart1500LCD on a CentOS 7 host using the usb connector. Nut does connect: $upsc ups battery.charge: 100 battery.runtime: 1407 battery.type: PbAC ... But after a half hour or so the connection is lost. Restarting nut re-establishes the connection. Any idea what might be causing the dissconnection?
Can you send me the serial number (at least 1st 12 characters, see: https://www.tripplite.com/support/identify-products) and lsusb -v output for the UPS? Thank you, David Zomaya Tripp Lite From: Nut-upsuser <nut-upsuser-bounces+david_zomaya=tripplite.com at alioth-lists.debian.net> on behalf of Kirk Bocek <t004 at kbocek.com> Sent: Tuesday, September 22, 2020 11:55 AM To: nut-upsuser at lists.alioth.debian.org Subject: [EXTERNAL] [Nut-upsuser] UPS Losing Connection This is an EXTERNAL email. Please take a moment and think before clicking any links or opening any attachments from this email. If suspicious, please forward to ishelpdesk at tripplite.com for review. ______________________________________________________________________ Installed a new Tripplite Smart1500LCD on a CentOS 7 host using the usb connector. Nut does connect: $upsc ups battery.charge: 100 battery.runtime: 1407 battery.type: PbAC ... But after a half hour or so the connection is lost. Restarting nut re-establishes the connection. Any idea what might be causing the dissconnection? _______________________________________________ Nut-upsuser mailing list Nut-upsuser at alioth-lists.debian.net https://urldefense.proofpoint.com/v2/url?u=https-3A__alioth-2Dlists.debian.net_cgi-2Dbin_mailman_listinfo_nut-2Dupsuser&d=DwIGaQ&c=f9s1WCuF-N6cmD_YaZ7gBg&r=lhr3k4au5dVQgHY_iS-v_t9g8PHVkn8Px_wyaupZGfQ&m=YgsSMN2tZcUb2W8G-3MvL5txRabN6Sd0lgenRmzXATw&s=J0z3xS-S2_LD301UwRudwTAmIZSOU7B3U4_ZD5s1Fk0&e ________________________________ This message is for the addressee's use only. It may contain confidential information. If you receive this message in error, please delete it and notify the sender. Tripp Lite disclaims all warranties and liabilities, and assumes no responsibility for viruses which may infect an email sent to you from Tripp Lite and which damage your electronic systems or information. It is your responsibility to maintain virus detection systems to prevent damage to your electronic systems and information.
On 9/22/2020 10:01 AM, David Zomaya wrote:> Can you send me the serial number (at least 1st 12 characters, see: https://www.tripplite.com/support/identify-products) and lsusb -v output for the UPS? > > Thank you, > David Zomaya > Tripp Lite >Oh cool, someone from Tripplite. Serial number 3021EYOSM886901200. lsusb -v for just the Tripplite: Bus 003 Device 057: ID 09ae:2012 Tripp Lite Device Descriptor: bLength 18 bDescriptorType 1 bcdUSB 1.10 bDeviceClass 0 (Defined at Interface level) bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize0 8 idVendor 0x09ae Tripp Lite idProduct 0x2012 bcdDevice 0.09 iManufacturer 1 Tripp Lite iProduct 2 Tripp Lite UPS iSerial 0 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 34 bNumInterfaces 1 bConfigurationValue 1 iConfiguration 0 bmAttributes 0xe0 Self Powered Remote Wakeup MaxPower 0mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 0 bAlternateSetting 0 bNumEndpoints 1 bInterfaceClass 3 Human Interface Device bInterfaceSubClass 0 No Subclass bInterfaceProtocol 0 None iInterface 0 HID Device Descriptor: bLength 9 bDescriptorType 33 bcdHID 1.10 bCountryCode 0 Not supported bNumDescriptors 1 bDescriptorType 34 Report wDescriptorLength 662 Report Descriptors: ** UNAVAILABLE ** Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x81 EP 1 IN bmAttributes 3 Transfer Type Interrupt Synch Type None Usage Type Data wMaxPacketSize 0x0008 1x 8 bytes bInterval 40 Device Status: 0x0001 Self Powered
I solved this problem a few years back. https://github.com/sdgathman/trippfix The short answer is USB is broken on the model (but the power management is excellent, handling switchover to generator power without a hitch). The workaround is to do a usb port power off when the Tripplite USB hangs. But hubs that actually implement this mandatory feature (must at least support powering all ports off) are getting hard to find. The USB chips implement it just fine. The hubs don't bother connecting the pins and just wire to +5V. The good news is that with CentOS-8, the kernel automatically does the port power off, so you don't need my kludgey software fix when you go to 8. You still need an actual standard conforming USB hub however. If the port on your server isn't, you can buy an external hub like I did. On Tue, 22 Sep 2020, Kirk Bocek wrote:> Installed a new Tripplite Smart1500LCD on a CentOS 7 host using the usb > connector. Nut does connect: > > $upsc ups > battery.charge: 100 > battery.runtime: 1407 > battery.type: PbAC > ... > > > But after a half hour or so the connection is lost. Restarting nut > re-establishes the connection. > > Any idea what might be causing the dissconnection?
On 9/23/2020 1:09 PM, Stuart D. Gathman wrote:> I solved this problem a few years back. > > https://github.com/sdgathman/trippfix > > The short answer is USB is broken on the model (but the power management > is excellent, handling switchover to generator power without a hitch). > > The workaround is to do a usb port power off when the Tripplite USB > hangs. But hubs that actually implement this mandatory feature (must at > least support powering all ports off) are getting hard to find. The USB > chips implement it just fine. The hubs don't bother connecting the pins > and just wire to +5V. > > The good news is that with CentOS-8, the kernel automatically does the > port power off, so you don't need my kludgey software fix when you go to > 8. You still need an actual standard conforming USB hub however. > If the port on your server isn't, you can buy an external hub > like I did. > >Stuart, I haven't tried your program yet. However the UPS appears to have dropped off completely. lsusb no longer shows the unit at all. So I physically unplugged and replugged it: #dmesg ... [252389.354190] hid-generic 0003:0557:2419.0002: usb_submit_urb(ctrl) failed: -19 [252389.403568] xhci_hcd 0000:00:14.0: USB bus 3 deregistered [252389.405712] xhci_hcd 0000:00:14.0: xHCI Host Controller [252389.407225] xhci_hcd 0000:00:14.0: new USB bus registered, assigned bus number 3 [252405.901391] xhci_hcd 0000:00:14.0: can't setup: -110 [252405.902631] xhci_hcd 0000:00:14.0: USB bus 3 deregistered [252405.903033] xhci_hcd 0000:00:14.0: init 0000:00:14.0 fail, -110 [252405.903038] xhci_hcd: probe of 0000:00:14.0 failed with error -110 And it's still not there: $lsusb Bus 002 Device 002: ID 8087:8002 Intel Corp. Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 8087:800a Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub So is this a faulty Tripplite that needs to be returned?