similar to: your Tripp-Lite AVR550U

Hi Patrick, I didn't get further bug reports from you, so I have now listed your device as "supported" by newhidups. Last I saw as of your below message, the driver was working as expected. If there are any future problems, let me know! -- Peter Patrick Nolan wrote: > > Remember me? Back in May we exchanged some messages about my Tripp-Lite > UPS. My boss has gone on

Hi Patrick, Patrick Nolan wrote: > > Remember me? Back in May we exchanged some messages about my Tripp-Lite > UPS. My boss has gone on vacation, so I finally got a chance to take a > look at this. > > Peter Selinger wrote: > ... > > In case you feel like experimenting with this, I am attaching a patch > > that *might* enable this device to be supported by the

I have a Tripp Lite OMNI900LCD. It has a usb connector and claims to be USB/HID. I haven't been able to get it to work with newusbhid or tripplite_usb. Here's lsusb -v output: Bus 001 Device 013: ID 09ae:2005 Tripp Lite Device Descriptor: bLength 18 bDescriptorType 1 bcdUSB 1.10 bDeviceClass 0 (Defined at Interface level)

Thanks Kjell for the help with the build problem. Thanks for your input, too, Charles. Now I have a new problem that I think has already been solved. I have Tripp Lite Smart1000LCD UPS (usb), but I can't get the newhidups driver to communicate correctly. I found a thread on the development list from last December where Jonathan Freedman described had a problem with this UPS in a thread

Some of my messages never went through since I hit a message size limit. I'm resending them in the hopes they are under the limit. Charles, The lsusb command did not trigger a disconnect. The output of that command is below. I ran "usbhid-ups -a upsunit -DDD &> output.log" and I have attached the /var/log/messages and output.log to this email. Before running this test

Bonjour, Je souheterais utilis? la version qui permet le '-x generic',mais je ne sais pas ou la recuperer car ca devrait solutionner mon probleme (cf mail ci-dessous) DaneZ _____ From: DaneZ [mailto:david.guillotte@danez.no-ip.org] To: arnaud.quette@mgeups.com Sent: Sat, 08 Jul 2006 23:24:06 +0200 Subject: Fw: INFOSEC 500 XP en USB _____ Bonjour Arnaud, Je me

I used a brazilian UPS from "TS-Shara" which uses the megatec serial protocol and it works perfectly. Now I have another one from the same brand (TS-Shara) and it uses a USB cable. I found the following: T: Bus=01 Lev=01 Prnt=01 Port=01 Cnt=01 Dev#= 3 Spd=1.5 MxCh= 0 D: Ver= 1.10 Cls=00(>ifc ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1 P: Vendor=0483 ProdID=0035 Rev= 2.00 S:

Hi I have a Tripp lite smartusb550 using fedora 3 (2.6.12-1.1381_FC3smp). Managed to establish communication with the ups using the tripplite_usb driver but get the following errors Any help to make it work will be appreciated cheers Julio -----------------------------------------------------------------------------------------------------------------------------------------------------

Here is what I get: # usbconfig -u 1 -a 3 dump_curr_config_desc ugen1.3: <Tripp Lite TRIPP LITE UPS> at usbus1, cfg=0 md=HOST spd=LOW (1.5Mbps) pwr=ON (100mA) Configuration index 0 bLength = 0x0009 bDescriptorType = 0x0002 wTotalLength = 0x0022 bNumInterfaces = 0x0001 bConfigurationValue = 0x0001 iConfiguration = 0x0000 <no string> bmAttributes =

So, I have this Mustek Powermust 600USB (no serial port) here temporarily. It seems to be a hid device. The output from "lsusb -v" and "newhidups -DDDDD" (with "generic" and "vendorid=06da") are (respectively): ----------------------------------------------------------------------------------------------- Bus 001 Device 002: ID 06da:0003 Phoenixtec Power

Has anyone gotten this model of tripp-lite to work? sudo /usr/local/bin/upsdrvctl -DDDDD -u root start Network UPS Tools - UPS driver controller 2.0.5 Starting UPS: tripplite exec: /usr/local/bin/tripplite_usb -a tripplite Network UPS Tools - Tripp Lite OMNIVS and SMARTPRO driver 0.7 (2.0.5) Warning: This is an experimental driver. Some features may not function correctly. Detected a UPS: TRIPP

Greetings, Any suggestions? I think I'm close but I can't quite get tripplite_usb to talk to my OMNI1000LCD. I'm new to NUT and couldn't find an answer using Google. With any luck, I've simply missed the obvious. The system I'm using, kaylee, is a debian stable system with some debian testing installed and a 2.6.15.4 kernel. I downloaded NUT 2.0.3 and built it from

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

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

Here are all the usbconfig outputs you have requested. I have left a message with the Dev for NAS4Free to give up the ./configure for NUT portion.? I am hoping they will... usbconfig -u 0 -a 5 dump_device_desc? datanas: ~# usbconfig -u 0 -a 5 dump_device_desc ugen0.5: <TRIPP LITE UPS Tripp Lite> at usbus0, cfg=0 md=HOST spd=LOW (1.5Mbps) pwr=ON (100mA)? bLength = 0x0012 ? bDescriptorType =

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

>Just for grins, can you try adding "usb_set_altinterface" to the ups.conf section for your UPS, and see if that changes this part of the log? (That is, after "[upstl1300]"). Here is the output with the usb_set_altinterface?added to ups.conf or at least partially output because it keeps going in a loop. ? 46.820206???? Checking device (09AE/3016) (/dev/usb//dev/ugen0.5) ?

I looked through the faq, but couldn't find an answer to this. I'm trying to configure nut-2.0.4-26 on SuSE linux 10.2. In ups.conf, I have [myups] driver = belkinunv port = /dev/undefined desc = "Local UPS" I'm trying to find out what the port should be set to. lsusb shows: Bus 001 Device 005: ID 050d:0980 Belkin Components Device Descriptor: bLength

Since version 2.0.5 the AVR550U is supported. The X version however is not. The difference, as far as I can see, is the voltage 120V (non-X) vs 230V (X). Is there a way to fake the productid of the X version? Or, alternatively will the X version be supported in the future? Checking device (09AE/1009) (001/004) - VendorID: 09ae - ProductID: 1009 - Manufacturer: Tripp Lite - Product: TRIPP LITE

i just purchased a tripp lite OMNIVS1500XL and have been attempting to get it working with the usb drivers since it doesn't have a serial port. it hasn't been anywhere near successful and i was hoping someone might be able to point me in the right direction. i run gentoo and this is what i currenlty have installed: nut 2.0.2 libusb 0.1.10a (gentoo modified) usbutils 0.11-r5