similar to: UPS Tripp Lite Internet 350 SER

---------- Forwarded Message ---------- Subject: [PATCH] New to nut project Date: Friday, 6. November 2009 From: Patrick Levesque <patrickl at verint.com> To: Thomas Jarosch <thomas.jarosch at intra2net.com> As requested, here is my patch file including all my modification to the 2.4.1 tarball from the web site. On Friday 06 November 2009 05:41:29 you wrote: > Hello Patrick,

Hello, I'm newbie with NUT, I'm trying to get work a *Tripp-Lite Internet350Ser*, a small UPS with serial port. The only reference about, is a modification patch that Mr. Patrick Levesque did for NUT 2.4.1 but the actual 2.6.1 looks to not have it yet. I tried all tripp and generic drivers but no success. Has anyone luck with this Tripp-Lite model? Thanks! Iv?n Escobar

I have tried to support a TrippLite Internet350SER UPS using a serial cable (The only connection on this model) using the 2.4 code branch. It uses the Protocol 1004 from the tripplite specification that can be use either used on serial or USB device. Since my device was only serial, I worked only on the serial integration. Since I found nothing in tripplite.c, tripplite-hid.c, tripplitesu.c to

Hi I have to support a TrippLite InternetOffice 350 (Small serial only ups). The communication protocol used by the device is 2005. Is anybody know if it is already supported by the nut project? This specific device was using protocol 1004 previously but newer device uses the new 2005 protocol. Thank you -- Patrick Levesque This electronic message may contain proprietary and confidential

I have gone through Two Tripp-Lite AVRX550U units trying to troubleshoot issues. There are two separate (but possibly related issues that I am finding. I’ve created an issue on the Github page, but it’s not clear that anyone looks at those issues (https://github.com/networkupstools/nut/issues/799) 1. According to Tripp-lite, the AVRX550U uses the 2012 protocol, but it’s listed in NUT as

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

Greetings, I have a Tripp-Lite SU6000RT4U unit connected via USB and RS-232. # tripplitesu -DD -u root -a tl6000 Unable to detect Tripp Lite SmartOnline UPS on port /dev/ttyS0 # tripplite -DD -u root -a tl6000 Failed to find UPS - giving up... # newhidups -DD -u root -a tl6000 Checking device (09AE/4002) (001/003) - VendorID: 09ae - ProductID: 4002 - Manufacturer: Tripp Lite - Product: TRIPP

I've having no success trying to use the tripplite driver to communicate with a Tripp-Lite SMART1500XL via the serial port. I'm using the cable that was included with the UPS. The tripplite driver simply returns "Failed - giving up..." after 20 seconds. I have verified that the tripplite driver is sending ":W" out the serial port. I am able to use Tripp-Lite's

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

On Mar 25, 2020, at 6:09 PM, Lee Damon <nomad at ee.washington.edu> wrote: > > I have no experience with Tripp Lite UPSs and the reviews I've found online are scant and fairly mixed so I thought I'd ask here... It's always hard to get a good read on whether a particular UPS brand is problematic, or if there is more noise on the lists because people are trying to make

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

Hi James, thanks for the feedback. The output you get seems generally fine, except for battery.voltage: 0.0 and output.voltage: 164.0; these values are consistent with what Phil DeBoest reported. Upsmon normally executes the shutdown command when you reach the "low battery" threshold, as decided by the UPS and/or driver. It does so by looking at ups.status, not battery.charge. --

I'm obviously biased but I like Tripp Lite stuff. I try to pitch in and help with Network UPS Tools issues related to Tripp Lite when I can too (albeit the developers and users on this list are usually more helpful than me). Just to confirm, it sounds like you are looking at the SU5000RT4UHV, correct?

I have a new SMART1050SLT Tripp Lite UPS that both tripplite and tripplitesu drivers hate. Both simply time out with a "can't find" message. Does anyone know about the SmartPro series?

I have 2 SmartUOS1050SLT's that apparently protocol 3004, has there been any progress on getting these units supported under nut? I am running version 2.4.1, and get the following output when starting the driver. #lsusb Bus 005 Device 002: ID 09ae:0001 Tripp Lite # upsdrvctl -DDDD start Network UPS Tools - UPS driver controller 2.4.1 Starting UPS: tripplite exec: /lib/nut/tripplite_usb -a

Hello. I'm new to nut and don't know if I've missed something in setting it up or if my ups isn't quite supported. I'm using these: - svn version of nut (downloaded on 9/13/06) - a tripp lite SMART2200RMXL2U - debian sarge with 2.6.8 kernel - the tripplite_usb driver (newhidups says my ups is not supported) I figured out how to get the device perms correct.

Test machine: Windows 7 Pro x64, NUT 2.6.5-3 UPS model: Tripp-Lite Internet Office UPS (INTERNET525U) I needed a UPS and I had this old, but lightly used Tripp-Lite in storage. On the compatibility list I see a (?similar?) INTERNETOFFICE700 using the tripplite_usb driver. But the driver is not liking this particular model that I have. I'll be receiving a 3S550 soon, so I'm not

On Jan 7, 2015, at 12:49 PM, Steve Ballantyne <steve.ballantyne at gmail.com> wrote: > I would like to get to the root of the problem though. I may tweak > the code a bit and see if I can get better results. Although you are > right about the broken pipe. If the device is "unplugging" ... not > much you can do to fix that other than to just ignore it. Although this

Hi all, I'm from Tripp Lite. Many of our smaller standby and line-interactive have recently changed from 20xx protocol numbers to 302x protocol numbers. This has caused issues for a few people on the users mailing list, for example: https://alioth-lists.debian.net/pipermail/nut-upsuser/2020-June/011876.html https://alioth-lists.debian.net/pipermail/nut-upsuser/2020-June/011878.html

I am not sure if this is a polling/communication problem or not. Running NUT 2.7.4 Driver used usbhid-ups Driver version 2.7.4 Driver version internal 0.41 This is the information the driver is able to pull UPS status OL UPS model TRIPP LITE UPS Manufacturer Tripp Lite Vendor ID 09ae Product ID 3016 OS is FreeBSD/XigmaNAS v11.2 The issue is that for every 30sec that the driver is able to