similar to: Tripp-Lite AVRX500U issues

Does the github link not come through (https://github.com/networkupstools/nut/issues/799)? All the documentation that Tripp-Lite sent me on the 2012 protocol and my configuration files are on that issue. I doubt this mailing list will allow me to attach any files. It's the NUT github page. At any rate ups.conf just has this in it. No offdelay or ondelay entries: [ups] driver =

David, Thank you. I created a Github issue (https://github.com/networkupstools/nut/issues/808). I don't know who monitors those tickets, but no one has responded to my previous issue on that project repository about the AVRX550U, so it's unclear if the right person is going to see this one. Can you tell me what other models use the 3024 protocol? Listing those may help provide

Thanks for chiming in @David Zomaya. Tripp Lite replaced my AVRX550U once thinking that the powering back on was a defective unit, but the replacement does the same thing. The SN on the first one is 2935AVHOM87BB00152. NUT has my model listed as protocol 2010, so that needs to be corrected to 2012, but I'm not sure if anyone is doing active development on it right now. I also have a

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

Thank you David. I think the end goal of making this UPS compatible with NUT helps both Tripp-Lite and NUT users in that greater compatibility insures more users purchase Tripp-Lite products. I do understand Tripp-Lite wanting to do their due diligence to protect IP, however, it seems like unless NUT devs can get a hold of some sort of documentation, it's more difficult to make this and

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

Well, I have good news and bad news. I have a Tripp Lite SmartPro UPS attached to a Linux server running Ubuntu 5.10, and I'm running the just-released nut 2.0.3. I had error -71 from the UPS, which Charles Lepple correctly called out as a likely cable problem (thank you, Charles.) The cable provided with the UPS by Tripp Lite was just plain bad. Not too long, mind you- defective. I

Hi, I can confirm that with my AVR750U connected to my Windows machine using the TrippLite Power Alert software, I can configure it to do the behavior I want: turn off at a low power level and turn back on when the power is reconnected, so I guess it's now a question of if NUT can be adapted to the 3024 protocol. I am not the most experienced C programmer out there, but given there are

Hi, I'm running Fedora Core 6 and need to monitor a Tripp Lite SMART2200RMXL2U. I've loaded the nut-2.0.3-2.1 RPM. The UPS is connected via the provided USB cable, and that much appears to work: # dmesg | grep -i tripp hiddev96: USB HID v1.10 Device [Tripp Lite TRIPP LITE SMART2200RMXL2U ] on usb-0000:00:1f.4-2 # lspci | grep -i usb 00:1f.4 USB Controller: Intel Corporation 82801BA/BAM

Hello, I am trying to get a SMART500RT1U working on CentOS and just receiving the following message when attempting to start the driver: Network UPS Tools - Tripp Lite OMNIVS / SMARTPRO driver 0.20 (2.6.5) Warning: This is an experimental driver. Some features may not function correctly. Detected a UPS: Tripp Lite /TRIPP LITE SMART500RT1U Unknown input voltage range: 0x02 Unknown number of

Good afternoon, I'm trying without much success to monitor a Tripp Lite OMNIVS1500XL using NUT. I checked the compatibility list and saw that this UPS is supported by tripplite_usb. The system is running Debian Stable, but I've downloaded NUT 2.0.3 and compiled from source since the packaged 2.0.1 doesn't include tripplite_usb. I compiled --with-user=nut. My first attempt at

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)

On Thu, Jan 8, 2015 at 11:37 PM, Charles Lepple <clepple at gmail.com> wrote: > Although this tends to happen more with x86 systems and/or USB3, you might want to see if the disconnects are less frequent with a shorter or higher-quality USB cable. The more I look into this ... the more I think that it's exclusively Tripp-Lite weirdness! There are some things that I explored as far

Hi Patrick, in February, you tried to post the below message to the nut-upsuser list, but the post was rejected because you were not subscribed to the list. Unfortunately, you did not subscribe and re-post it. Anyway, I have been working on Tripp-Lite support for newhidups recently, and I wonder if you have any feedback. Did you ever get this device to work? >From the information you sent,

Re: "Does it work well with NUT?" Assuming it is the SU5000RT4UHV, the similar units I've tried seemed to work fine. For reference, the SU5000RT4UHV should be a 4004 USB protocol. ________________________________ From: David Zomaya Sent: Wednesday, March 25, 2020 5:21 PM To: Lee Damon; nut-upsuser Mailing List Subject: Re: [EXTERNAL] [Nut-upsuser] thoughts on tripp lite Smart

On Mar 6, 2015, at 12:51 PM, Eric Cobb <Eric_Cobb at tripplite.com> wrote: > Network UPS Tools - Tripp Lite OMNIVS / SMARTPRO driver 0.20 (2.6.5) > Warning: This is an experimental driver. > Some features may not function correctly. > > Detected a UPS: Tripp Lite /TRIPP LITE SMART500RT1U > Unknown input voltage range: 0x02 > Unknown number of switchable load banks:

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 -----------------------------------------------------------------------------------------------------------------------------------------------------

I'm running Raspbian Buster, but given that the error seems to be "higher order" than a hardware issue - one of parsing the protocol?  I suspect that Ubuntu would be a decent "lookalike" to model the issue.  ---- On Tue, 19 May 2020 22:31:56 -0400 David Zomaya <David_Zomaya at tripplite.com> wrote ---- If I installed and tested against Ubuntu, how useful would

On March 6, 2015, at 6:17pm, Charles Leppe ,cleppe at gmail.com> wrote: If this is the same protocol 3005 that we saw in mid-2014 (USB ID: 09AE:0001), then support will be part of the upcoming NUT 2.7.3 release. You wouldn't happen to know anyone who would be able to publish the specs of that protocol, would you? ;-) That would help remove the "experimental driver" warning.

Did it stay stable this time? It looks like the restart of the service restored communication. If it reoccurs: >>> Bus 001 Device 011: ID 09ae:3024 Tripp Lite I wonder if this is the same device number after? Something to keep an eye on Thank you, David Zomaya ________________________________ This message is for the addressee's use only. It may contain confidential information. If