similar to: UPS Losing Connection

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

Ok, so I have made some progress that seems to suggest the initial “fix” I stumbled upon isn’t required. I haven’t yet worked backwards to figure out reasons why our customers have had similar complaints or solve the problem on the CentOS VM yet, but that is on the todo list. I am hoping it ends up just being not enabling the service on startup, but I can’t say that explains away all the symptoms

Thanks for the inputs. I’ll get CentOS 7.6 installed on a physical machine this week and follow up. Few responses and notes below in the interim. ”The log format looks okay, but I may not have been clear that I was looking for the log at the same time as when the kernel errors occur. So without the udev rules would be good.” Ah, sorry. Attached are these two files: 1-

I haven't tried it on RaspberryPi, but if there's some specific Tripp Lite information I can help with, let me know. David Zomaya Tripp Lite ________________________________ From: Nut-upsuser <nut-upsuser-bounces+david_zomaya=tripplite.com at alioth-lists.debian.net> on behalf of Charles Lepple <clepple at gmail.com> Sent: Sunday, December 8, 2019 8:36 PM To: Layne Fowler

Thought I'd follow up in case someone else runs into this issue. In the end what worked for me was tweaking the udev rules. I have had no USB disconnects or stale data warnings so far. I only used one rule for my UPS: # /etc/udev/rules.d/62-nut-usbups.rules SUBSYSTEM!="usb", GOTO="nut-usbups_rules_end" # TrippLite # e.g. TrippLite SMART1500LCD - usbhid-ups

I recently purchased a UPS from http://www.microcenter.com/product/470131/5E_1,100W_2,200VA_6-Outlet_UPS It's sold as an Eaton 5E 1,100W 2,200VA 6-Outlet UPS SKU: 147140 Mfr Part #: 5E2200USB-LA UPC: 743172064875 "The Eaton 5E is an essential line interactive UPS that provides cost effective and reliable power protection against power outages and bad power quality. Thanks to its small

Hi Everyone, I'm having trouble getting TrippLite SMX1500LCDT to work on FreeBSD 11.2, nut 2.7.4 installed from FreeBSD port. The debug output is rather big when I'm starting usbhid-ups initially, Please find that attached (gzipped to comply with message size limit). Subsequently, until I unplug and replug the USB cable, I'm geting a shorter debug output, like this: Network UPS

On Sep 22, 2014, at 11:14 AM, Shade Alabsa <shade34321 at gmail.com> wrote: > These machines are exact replicas of each other and are fairly old and have a Core 2 Duo E8400 CPU in them. Is there anything else you need or anything I can do to help fix this? Thanks! Also, Barry Skrypnyk mentioned that Fedora was one of the Linux distributions that Tripp Lite claims to support. I recommend

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

Thanks Ken. I'll plan to sit down and look up the protocol information over the next week or so and follow up. ________________________________ From: Ken Olum <kdo at cosmos.phy.tufts.edu> Sent: Tuesday, January 14, 2020 1:35:10 PM To: David Zomaya Cc: kdo at cosmos.phy.tufts.edu; layne.fowler at gmail.com; nut-upsuser at alioth-lists.debian.net Subject: [EXTERNAL] Re: [Nut-upsuser]

OS: Debian 3.16.36 Nut version: 2.7.4 from the ?stretch? distribution (this was to solve another problem ? which it did) Install method: apt-get Device: TRIPPLITE SMART1300LCDT using usbhid-ups driver Problem: I keep getting the message UPS tripplite at localhost is unavailable If I do? service nut-server stop service nut-server start Then everything is fine again for a while.

On Sep 6, 2014, at 4:16 PM, Leslie Rhorer <lrhorer at mygrande.net> wrote: > Oh, hey! That seems to have worked. I'm sure the UPS got plugged into a different port one of the (many) times the server was removed from the relay rack, and it was on a USB 3.0 port. I moved it to a 1.0 port and everything seems to be working just fine. The specifics of the motherboard and its USB

On 9/6/2014 12:47 PM, Charles Lepple wrote: > On Sep 6, 2014, at 12:39 PM, Leslie Rhorer <lrhorer at mygrande.net> wrote: > >> I made a number of hardware and software changes, including an upgrade to the latest software versions for that distro (Debian Wheezy), > > Can you be more specific about the changes? Well, I did an automated upgrade (apt-get upgrade), I changed

# usbconfig -d ugen0.2 dump_device_desc ugen0.2: <TRIPP LITE SMART1500RMXL2Ua TRIPP LITE> at usbus0, cfg=0 md=HOST spd=LOW (1.5Mbps) pwr=ON (60mA) bLength = 0x0012 bDescriptorType = 0x0001 bcdUSB = 0x0110 bDeviceClass = 0x0000 <Probed by interface class> bDeviceSubClass = 0x0000 bDeviceProtocol = 0x0000 bMaxPacketSize0 = 0x0008 idVendor = 0x09ae idProduct = 0x0001

Hi Everyone, I recently bought a Tripp-Lite SMART1500LCD for my Linux Mint 19.3 machine, connected via a USB cable. I installed Nut 2.7.4 from the Mint package repository via sudo apt update && sudo apt install nut. Everything works great: NUT issues low battery warning when it reaches the set low battery point and then issues shutdown commands...computer shuts down..then the UPS shuts

On Sun, 7 Jun 2015, Charles Lepple wrote: > [please use reply-all to include the list, as the list does not override the Reply-To header.] > > On Jun 7, 2015, at 5:02 PM, Greg Hersch <hersch.greg at gmail.com> wrote: > >> Here is the driver debug log. If I just let it run, it pops up with >> libusb_get_string_invalid argument over and over again, mixed in the

Hi Network UPS Tools Support, I'm not sure if this is a question for the "user group" or the developer group". My name is David Zomaya and I work at Tripp Lite in our technical support department. Copied on this email are Eric Cobb from our Product Management group & Jonathan Manzanilla tech support subject matter expert for our single phase UPS product lines. Recently,

Hi Network UPS Tools Support, I'm not sure if this is a question for the "user group" or the developer group". My name is David Zomaya and I work at Tripp Lite in our technical support department. Copied on this email are Eric Cobb from our Product Management group & Jonathan Manzanilla tech support subject matter expert for our single phase UPS product lines. Recently,

> What does that revision number correspond to in FreeBSD release numbers? (e.g. 9.3, 10.0) FreeBSD 10.2-RELEASE #0 r286738M the last person probably wasn't able to give the ./configure probably because most people uses the precompiled iso to install NAS4Free.? if you need the ./configure I might have to look for their source on GitHub or something. /usr/local/libexec/nut/usbhid-ups -a

Attached are config.log and usbhid-ups output with -u root (gzipped). Now driver output looks a lot like the one from port build. On Mon, Aug 20, 2018 at 1:42 PM, Charles Lepple <clepple at gmail.com> wrote: > On Aug 20, 2018, at 1:03 AM, Valentin Merkulov <schnobel at ickis.net> wrote: >> >> 0.033412 [D3] nut_usb_claim_interface: failed to claim USB >>