similar to: thoughts on tripp lite Smart Online UPSs?

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

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?

Thanks. I haven't used that unit specifically with Network UPS Tools, but have used similar (from a protocol perspective) units. I'm working remotely for a while, but on the off chance I get into the position to connect a unit via USB, what Operating System are you using? If the opportunity arises, I can try to set up a basic test. Thank you, David Zomaya Business/Quality Analyst-

On 3/25/20 3:31 PM, David Zomaya wrote: > Just to confirm, it sounds like you are looking at the SU5000RT4UHV, > correct? > > https://www.tripplite.com/smartonline-208-240v-5kva-4.5kw-double-conversion-ups-4u-rack-tower-extended-run-snmpwebcard-option-usb-db9-serial~SU5000RT4UHV > That does seem to be the one they are quoting, yes. thanks, nomad

At the company I work for, we are using many TrippLite OMNI900LCD UPSs and are having difficulty setting the lower transfer threshold voltage. On our other model, the Eaton MGE-3S550, this can be set using upsrw to set the input.transfer.lowsetting, but on the Omni900, this option is not available. In our testing, it defaults to ~95v but we want to set it to 84v. More info: - OS = OpenSuse 13.1 -

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

I've been looking over the documentation and several installation guides for NUT, and I'm starting to get a little bit of a feel for what it is. But I'm still not clear whether what I'd *like* to accomplish is actually practical using NUT. Perhaps someone here can tell me if they've done something similar, or if I'm way off base. I would like to set up a Linux host as a

> > battery.charge: 3 > battery.charge.low: 10 > battery.charge.warning: 30 > battery.runtime: 93 > battery.temperature: 32.9 > battery.type: PbAC > battery.voltage: 46.4 > battery.voltage.nominal: 48.0 Is it possible that battery.charge is really 30% rather than 3%? The 3016 protocol models have issues with scaling on some of the voltages and frequencies. You can see

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

OS = NAS4Free (FreeBSD Revision: 199506) NUT Version = 2.7.3 for other parts of NUT version is listed below NUT is part of the NAS4Free distribution Device = Tripp Lite SMART1300LCDT URL http://www.tripplite.com/line-interactive-ups-system-desktop-tower-1300va-120v-usb-port-lcd-screen~SMART1300LCDT/ PROBLEM: NUT is ABLE to see the UPS BUT it is not getting the right(?) descriptor? I am using

Hi all, My apologies if this has been asked, but is there anyone who would be willing to help me figure out what to 'edit' in what and which (all?) '.conf' files in /etc/nut to be able to use my new Tripp Lite Smart1300LCD please? I have/need just the most basic setup. It's only me using my computer and only this one computer and a few peripherals being used on the

People, A couple of decades before I was retired and was still working for other people I had cause to install UPSs and they usually had RS232 ports to allow the setting up of shutdown scripts to UNIX / Linux servers. Now, after not having to be concerned by those issues for some time - most of my little web sites have been on Digital Ocean or other suppliers VMs for a long time - I am

People, A couple of decades before I was retired and was still working for other people I had cause to install UPSs and they usually had RS232 ports to allow the setting up of shutdown scripts to UNIX / Linux servers. Now, after not having to be concerned by those issues for some time - most of my little web sites have been on Digital Ocean or other suppliers VMs for a long time - I am

One of the 3 ups's that I am trying to configure is a Tripp Lite SU5000RT4UHV. The ups is recognized by the IETF 1.4 MIB, but I am getting Unhandled ASN 0x80 and 0x81 when starting upsdrvctl with the -D option. When I do a upsc {name of ups} the message returned is Error: Connection failure: Connection refused. Thank you for your support V/R Bill -------------- next part

I'm having trouble with a TrippLite SU3000XLCD. I'm using a Raspberry Pi running Raspbian (wheezy) with NUT 2.6.4. I can monitor my older TrippLite UPSs, mostly SU1000RT2Us, with this Pi and a USB to serial adapter. My first thought with the SU3000XLCD was to use the USB port instead of the serial port as that's the "modern" thing to do. When I plugged the USB cable in

    Lately I replaced my 10+-year-old server with a nano-ITX-type one that has USB but not old serial ports.  I connected my FE700VA to DB25-to-9-to-USB cables, but haven't been able to set it up. Apparently my DB9-to-USB cable (Prolific Technology, Inc. PL2303 Serial Port) has issues needing old software (setserial?) and some new software (fconfigure) being changed.  Has anyone managed

Using this UPS in the UK on 240V mains. Connected via USB: Bus 001 Device 002: ID 09ae:0001 Tripp Lite Requires tripplite_usb driver as it is (Product ID: 0001). There is an entry in the compatibity list for OMNIVS800 USB (protocol 2012) using usbhid-ups which is little misleading (although I guess maybe correct for some instances of the UPS). OMNIVS1000 USB (older; product ID: 0001) is

On 22:17, Thu 25 Sep 14, Charles Lepple wrote: > > I think the OMNIVS800 protocol 2012 entry came from Tripp Lite test results. (There have definitely been naming collisions in the past; hence, the messages in the drivers if you accidentally choose the wrong one.) > > Confusingly, if the USB ProductID is 0001, the Tripp Lite specific "Protocol" number (shown in

That's certainly on the list of options. I'm doing data gathering right now to see what options there are. I'd prefer not to rashly decide to run off in a direction only to discover this is already a Solved Problem. nomad On Thu, May 14, 2020 at 1:13 PM Bart J. Smit <bart at smits.co.uk> wrote: > What about the REST API to do a graceful shutdown of your VM’s and the >

On Sep 25, 2014, at 5:51 PM, Dave Williams <dave at opensourcesolutions.co.uk> wrote: > Using this UPS in the UK on 240V mains. > > Connected via USB: > Bus 001 Device 002: ID 09ae:0001 Tripp Lite > > Requires tripplite_usb driver as it is (Product ID: 0001). There is an > entry in the compatibity list for OMNIVS800 USB (protocol 2012) using > usbhid-ups which is