similar to: Tripp-Lite AVR-900U

Hi all, As requested by upsdrvctl, I'm reporting on my results connecting a Tripp Lite UPS (G1010USB). This server is running on Ubuntu Lucid, nut version is 2.4.3-1ubuntu3.1. With ups.conf: [ups] driver = usbhid-ups port = auto Results: # upsdrvctl start Network UPS Tools - UPS driver controller 2.4.3 Network UPS Tools - Generic HID driver 0.34 (2.4.3) USB communication driver 0.31

Hi, I'm running the latest stable nut (2.4.3). It doesn't appear to provide support for the Tripp Lite SmartOnline SU1000XLA. [sups] driver = usbhid-ups port = auto vendorid = 09ae productid = 4004 4337# upsdrvctl start Network UPS Tools - UPS driver controller 2.4.3 Network UPS Tools - Generic HID driver 0.34 (2.4.3) USB communication driver 0.31 Using subdriver:

Hi, I kludged support for the TrippLite SU2200XLA into nut-2.4.3 as follows: --- ./drivers/tripplite-hid.c.0 2010-03-03 15:53:20.000000000 -0500 +++ ./drivers/tripplite-hid.c 2010-03-03 15:53:40.000000000 -0500 @@ -81,6 +81,8 @@ { USB_DEVICE(TRIPPLITE_VENDORID, 0x4002), battery_scale_1dot0 }, /* e.g. TrippLite SmartOnline SU1500RTXL2ua */ {

I have the following UPS that I'm trying to get to work with NUT: SU3000RTXL3U I have it connected via USB. My ups.conf looks like: [test] driver = usbhid-ups vendorid = 09ae port = auto When I run upsdrvctl -DD start, I get: Network UPS Tools - UPS driver controller 2.4.1 Starting UPS: test exec: /lib/nut/usbhid-ups -a test Network UPS Tools - Generic HID driver 0.34 (2.4.1)

Device manufacturer and name: Tripp-Lite OmniSmart500 upsc output: matt at backup:/etc$ sudo upsc tripplite battery.charge: 100 battery.test.status: Battery OK battery.voltage: 14.56 battery.voltage.nominal: 12 device.mfr: Tripp Lite device.model: OMNISMART500 device.type: ups driver.name: tripplite_usb driver.parameter.pollinterval: 2 driver.parameter.port: auto driver.version: 2.4.3

Trying to get a Tripp-Lite to work with nut--Ubuntu 10.10. I was getting the error message "unable to claim USB device", tried to unbind the drivers to that device, and had the following delightful experience. In short, continue to get the same problem, and the drivers bound themselves back. Any suggestions? ----------- usb.conf has the following: [Tripp-Lite] driver = usbhid-ups port

I have been working on supporting the TrippLite Internet350SER (serial connection only using communication protocol 1004) in nuts.2.4.1. I sent a patch around 2009/11/9. I just look at the 2.4.3 release and the support for this model does not look to be added in either tripplite driver. Can I help to add support in the project? -- Pat This electronic message may contain proprietary and

Hey all, I am trying to use NUT for a Tripplite Smart1200 LCD on a fresh copy of Debian 6.0.2.1. I installed NUT version 2.4.3 and I have pored through pages and pages of other posts, but for the life of me I can not get it to recognize the Tripplite. I know its an 09ae:2009 device and I've tried to add a rule in /lib/udev/rules.d/52-nut-usbups.rules as according to some posts, but to no

I have an SMX1500SLT running on USB just fine. I not want to buy/add a SMARTINT1500. However before doing so I was trying to make sure there was a chance it would work under Nut. The SMX1500SLT has both serial and USB, but the SMARTINT1500 has only serial. I was therefore trying to switch the SMX1500SLT to serial to ensure the server comms were ok, and that there was some chance that the

I'm trying to set up a single host to monitor the state of several UPS in my data center. I have a mix of several APC and Tripp-Lite in production. The former are great, the latter are not so much. With the APCs (using usbhid-ups), I can set up configs for each based on the value they report from ups.serial. With the Tripp-Lites (using tripplite_usb), there is no value returned for

Hello List members, Are there any other commands available for this UPS, I've been searching without success... I know I use an old UPS, and when I do: "upscmd -l pbx at 192.168.1.18" for instance, I get the answer: "Instant commands supported on UPS [pbx]: shutdown.return - Turn off the load and return when power is back" If I send this command it works, shutdowns

Hello! I am currently having issues monitoring a Tripp-Lite AVR900U. First, here are a few system details: > Manjaro Linux - kernel 5.4.30-1 > network-ups-tools 2.7.4-5 (built from Arch User Repository) > (lsusb output) Bus 003 Device 003: ID 09ae:3024 Tripp Lite AVR900U Contents of /etc/ups/ups.conf: > [tripplite] > driver =  usbhid-ups > port = auto Contents of

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

If I installed and tested against Ubuntu, how useful would that be in general and in this specific case? I think we've seen a few reports of issues with the newer 3024 protocols and I'd like to help get them sorted out. Thank you, David Zomaya Tripp Lite ________________________________ From: Nut-upsuser <nut-upsuser-bounces+david_zomaya=tripplite.com at

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

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:

Hello List, David: I’ thanking you … :-) I’m using the tripplite_usb driver and the barcode on mine says: 9347AIOBC470902728 or 9347A10BC470902728. with pictures… https://drive.google.com/file/d/1SJWDr0g95KOD-FpbOPHUyl9bsbOKePlD/view?usp=sharing https://drive.google.com/file/d/1SFMT-GbZRcRO03gEy_7SszZ43-LYmEZM/view?usp=sharing

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

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

That would be great.  If there is something I can do to collect data or troubleshoot, please let me know. ---- On Wed, 20 May 2020 08:51:14 -0400 David Zomaya <David_Zomaya at tripplite.com> wrote ---- I'm still working remotely, but I should be able to get something set up soon. I'll reply all here once I have something to report. Thank you, David Zomaya Tripp