search for: smart1500lcdxls

this probably has no relevance to the subject but i have run a OMNIVS1500XL with the tripplite_usb driver for several years with no problem i am using a a powered usb hub if that make any difference

Unfortunately I do not use the latest versions of NUT, the driver I created, solis, was changed, not by me, and now does not work on my nobreak, which I used to create the driver. greetings Silvino B. Magalhaes Em qua, 19 de jun de 2019 às 03:39, Manuel Wolfshant < wolfy at nobugconsulting.ro> escreveu: > On 6/19/19 5:59 AM, Charles Lepple wrote: > > > “The

On Jun 19, 2019, at 4:16 PM, David Zomaya wrote: > > Interestingly, I did some tinkering with openSUSE 15.1 Leap on a physical box and saw the same drops there, but was able to get them to stop after installing NUT and just doing the “standard” configuration. However, I ran into some connection refused messages, e.g.: > > user at linux-nxmm:/dev/bus> sudo upsc -l > Error:

On 6/19/19 5:59 AM, Charles Lepple wrote: >> >> “The 62-nut-usbups.rules file looks pretty standard. Do you know if the changes to 42-usb-hd-pm.rules are needed? It seems like none of the USB devices would have the right permissions if 62-nut-usbups.rules isn't sufficient (though this happened in Debian once).” >> >> My means of testing wasn’t the most rigorous,

On Mon, Jun 17, 2019 at 6:10 PM David Zomaya <David_Zomaya at tripplite.com> wrote: > 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

On Jun 17, 2019, at 3:00 PM, David Zomaya <David_Zomaya at tripplite.com> wrote: > > Hi Network UPS Tools Support, > > I’m not sure if this is a question for the “user group” or the developer group”. The config files will be useful for -users, but I'd say the development list is probably better for discussing potential changes. > My name is David Zomaya and I work at

Updates on this: 1) Making progress in the related Dev list thread here: https://alioth-lists.debian.net/pipermail/nut-upsdev/2019-June/007440.html I’ll keep that thread up to date with progress as I go. But if there are specific things it would make sense to test here, just let me know. Otherwise, I figure reducing redundancy makes sense? 2) I tried disabling usbcore.autosuspend, but

To try and work through the initial drops, I repeated the previous steps that worked on the physical machine on the CentOS 7.6 virtual machine. The drops continued to occur, but it seems that the driver always reconnects. My initial inclination is to work through and see at what point I get the drops to stop, and I think I will do that next (inputs welcome). From a standpoint of “how much does

Hi Greg, I haven’t but I will give that a shot later this week and advise. Thanks for the tip. Thank you, David Zomaya Technical Support [cid:image007.png at 01D525AF.B38D63F0] 1111 W. 35th Street | Chicago, IL 60609 USA 773.869.1156 | david_zomaya at tripplite.com [cid:image008.png at 01D525AF.B38D63F0]<http://www.tripplite.com/> From: Nut-upsuser

On Jun 18, 2019, at 1:47 PM, David Zomaya wrote: > > Charles and Wolfy, > > Thanks for the replies. > > I added some responses below. > I think I got the driver debugging right, but let me know if it is off. > > I should note: > The CentOS 7.6 machine I have been testing with is a virtual machine (running on VMware ESXi 7.6). At least 1 customer and I have seen

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

Hey all, I've read through as many relevant mailing list posts and public blog posts as I could, but I can't seem to find an answer to my issue. I currently have 2x Tripp Lite SMART1500LCDXLs, and I am attempting to monitor both of them with the same Raspberry Pi using NUT. The problem I have is there doesn't seem to be any way in the nut.conf to differentiate between the two UPS via USB other than Vendor/Product/Serial. Unfortunately, I cannot leverage Vendor/Product filtering, bec...

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-

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,

Charles and Wolfy, Thanks for the replies. I added some responses below. I think I got the driver debugging right, but let me know if it is off. I should note: The CentOS 7.6 machine I have been testing with is a virtual machine (running on VMware ESXi 7.6). At least 1 customer and I have seen the same issue on VMs and physical boxes, so I don’t think that matters, but if it does let me know.

...11 Oct 2020 01:57:16 +0200 "Julian H. Stacey" wrote: > > > I've read through as many relevant mailing list posts and public blog = > > posts as I could, but I can't seem to find an answer to my issue. > > >=20 > > > I currently have 2x Tripp Lite SMART1500LCDXLs, and I am attempting to = > > monitor both of them with the same Raspberry Pi using NUT. > > Rasp. Pi, x86 or amd is irrelevant as Pi runs Linux & BSD etc. > Relevant is: What OS ? > > If you connect a USB device (mem stick, triplite ups or disc whatevere) > to a FreeB...

On Oct 9, 2020, at 8:07 PM, Rusty Bower wrote: > > Hey all, > > I've read through as many relevant mailing list posts and public blog posts as I could, but I can't seem to find an answer to my issue. > > I currently have 2x Tripp Lite SMART1500LCDXLs, and I am attempting to monitor both of them with the same Raspberry Pi using NUT. The problem I have is there doesn't seem to be any way in the nut.conf to differentiate between the two UPS via USB other than Vendor/Product/Serial. Unfortunately, I cannot leverage Vendor/Product filtering, bec...