similar to: Re: Tripp Lite LCD models w/ NUT

James, thanks, this is useful info. Comments below. -- Peter James Pooton wrote: > > > I saw on the list that you were looking for some details. Sorry I'm not > part of the list, but here are my results: > > > [root@blackhole bin]# ./newhidups -DDD -u root ups@127.0.0.1 > Network UPS Tools: 0.28 USB communication driver 0.28 - core 0.30 (2.1.0) > > debug

Hi Mauel, No dice. The config does not show up config: --8<-- [tripp] driver = usbhid-ups port = auto vendorid = 09ae productid = 2009 bus = 001 desc = "Tripp Lite SMX1000LCD" runtimecal = 660,100,180,50 -->8-- output: --8<-- upsc tripp Init SSL without certificate database battery.charge: 100 battery.runtime: 736 battery.type: PbAc

I'm happy to have had a quick look at this thread... 2007/5/17, Peter Selinger <selinger at mathstat.dal.ca>: > ... > as you know, I haven't had much time to work on NUT. Now my wife is > expecting our first baby in 1 week, so I don't think I will get back > to it in the foreseeable future. I didn't knew before! what a good news: all my congratulations to you

Hi, This is a newbie post so please bear with me. After loosing my router to a random Subminute outage. I looked around for a fanless UPS and bought Tripp Lite SMX1000LCD The above constellation works. But I have some questions about outputs. Please see attache nut report for the config. upsc output: --8<-- fourpi01:~# upsc tripp Init SSL without certificate database battery.charge: 100

Hello all; I am new to this list. Recently we have been getting these cheap new Tripp-Lite "LCD" style UPS'es around here, and I was surprised to find the lack of Linux support. The model name is OMNI650LCD. Anyway, I tried the tripplite_usb driver and got a message instructing me to contact this mailing list. I might try to fix the problem myself, if I was more familiar with the

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?

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

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

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

On 5/15/20 12:13 PM, Yogesh Bhanu wrote: > [...] > # Is it possible to calculate /estimate how much time is left when on > battery ? When the UPS does not report that, you can ask nut to provide an estimate by using the runtimecal directive. For instance I have in ups.conf on a system where I use an Inform low-end UPS:         runtimecal = 120,100,480,50        

On 5/19/20 10:39 AM, Yogesh Bhanu wrote: > Hi Manuel et.al, > > Going thru the documentation -- it seems this configuration specific > to blazer_ups. > https://networkupstools.org/docs/man/blazer_usb.html > > Kind Regards, Other drivrs support that option as well. Here is a quote from the same config as before: [guardian]         driver = nutdrv_qx         port = auto

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-

I wrote a while back about the inability to kill the following command with anything but "kill -9" and the apparent high speed polling rate. # /lib/nut/usbhid-ups -u root -DDD -a trippy The setup I have worked on a previous version of nut, but I have forgotten at what point it stopped working. (I believe it was around Nov, 2007 that I noticed things were not working correctly.) I

Hi Manuel et.al, Going thru the documentation -- it seems this configuration specific to blazer_ups. https://networkupstools.org/docs/man/blazer_usb.html Kind Regards, Yogesh On Fri, May 15, 2020 at 12:53 PM Manuel Wolfshant <wolfy at nobugconsulting.ro> wrote: > > On 5/15/20 12:13 PM, Yogesh Bhanu wrote: > > [...] > > # Is it possible to calculate /estimate how much

Hello, We are trying to develop a mechanism to power cycle Tripp Lite UPS. When we checked the upscmd, looks like the only command we can use is shutdown.reboot(sudo upscmd -u user -p password ups shutdown.reboot). Because the PC is connected to UPS directly and we would prefer shutdown PC before power cycle the UPS. But if we run shutdown PC first it won't run the power cycle the UPS script

Hello, We are trying to develop a mechanism to power cycle Tripp Lite UPS. When we checked the upscmd, looks like the only command we can use is shutdown.reboot(sudo upscmd -u user -p password ups shutdown.reboot). Because the PC is connected to UPS directly and we would prefer shutdown PC before power cycle the UPS. But if we run shutdown PC first it won't run the power cycle the UPS script

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)

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,

We're looking at replacing some old APC SmartUPS 5000s with something that has USB so NUT can more easily talk with it (and yes, I've tried USB-RS232 adapters and every one I tried started kicking out errors within a few hours). One of the bids we have is for a "Tripp Lite UPS Smart Online 5000VA 4500W Rackmount 5kVA 200V/240V" as the potential replacement unit. I have no