similar to: Multiple Tripplite OMNI900LCD

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 -

These patches allow this device to function in nut.. diff --git a/trunk/drivers/tripplite-hid.c b/new/drivers/tripplite-hid.c index c36da98..dddd13c 100644 --- a/trunk/drivers/tripplite-hid.c +++ b/new/drivers/tripplite-hid.c @@ -71,6 +71,8 @@ static usb_device_id_t tripplite_usb_device_table[] = { { USB_DEVICE(TRIPPLITE_VENDORID, 0x2005), battery_scale_0dot1 }, /* e.g. TrippLite

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)

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

I've having trouble understanding the NUT compatibility page. Is it compatible with the OMNISMART300? Or the OMNI900LCD? The compatibility page said for instance SMART550 -- tripplite_usb SmartUPS -- tripplite OMNI650LCD -- usbhid_ups so I'm not sure if an OMNISMART300 is like a Smart, or a SMART, or an OMNI, or even if it's supported at all. Thanks in advance for any help!

I am having an issue running NUT and using an TrippLite OMNI900LCD. When I run ./upsdrvctl start I get : [player@V0002-S002 bin]$./upsdrvctl start Network UPS Tools - UPS driver controller 2.1.0 Network UPS Tools: 0.28 USB communication driver 0.28 - core 0.30 (2.1.0) Detected a UPS: Tripp Lite /TRIPP LITE UPS Using subdriver: TrippLite HID 0.1 (experimental) dstate_setflags: base variable

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

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

[please use reply-all to include the list - the headers are not mangled] On Oct 20, 2016, at 3:22 PM, Fairfax, Charles A. wrote: > > 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. Interesting, we don't

Hello NUT ! In order to fill info structure I'm putting in the drivers, I need to gather a lot of information. The information I need, at best, is : - For each USB UPS, the pair VendorID ProductID - For each pair Driver/UPS supported, how was made the driver ? By the manufacturer, by reverse engineering, ... - Who contributed to which driver - Who is the "maintener" of each driver

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-

Hi David and fellows, I'm reviving this important thread about a common power management. To sum up, the first aim is to allow a better user experience on Linux by bridging NUT with Linux HAL, and Gnome Power Management / any PM GUI. But it also initiate a bigger investigation about how to integrate NUT support for UPSs into the native OS Power Management infrastructure for all supported

I'm setting up a NUT server. During testing, I have deployed it on both CentOS and SUSE. I have both servers looking at two physical UPSs and two "dummy" UPSs. My NUT client is running on Solaris and is rigged to look at the "dummy" UPSs. As I toggle states on the dummy UPSs, the client correctly detects the changes and throws a message of the type: > Broadcast

Hi Guys, I'd like to submit a patch to enable NUT to communicate with APC 5G UPSs. The current usbhid-ups driver recognises APC UPSs by the Vendor ID and Product ID of 0x051D and 0x0002. This needs to be amended with the new Product ID of 0x0003. (See attached file: apc-hid.patch) Secondly, when Nut polls the UPS via the interrupt channel, these will time out, resulting in frequent lost

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

Dear Daniele, thanks a lot for your support, i have some things that are not so clear for me: - I can send you the whole sources for our UPSs, do you need only Headers and C files or also other files (i suppose Driver list)? - Seen that we had some problems with the Blazer driver (the battery voltage calculation were not correct for our UPSs) we copied it and modified a bit while changing the

I have a couple EMC relabled ACBEL/Polytech UPSs which I'm unable to find anything about. What I do know is that ACBEL/Polytech is CoolerMaster, however, they don't make UPSs that I know of. These UPSs were used as part of an EMC Clarion array. Does anyone know anything about these? Thanks, Mark. -------------- next part -------------- An HTML attachment was scrubbed... URL:

Ah! So I can detect the source UPS in the upssched.conf and pass it as a distinct event to the shell script. That sounds like an excellent approach. Thanks! GMH From: O'Shaughnessy, Mike [mailto:Mike.OShaughnessy at gd-ms.com] Sent: Tuesday, October 31, 2017 12:46 PM To: Garrett Michael Hayes <Garrett at VerbalImaging.com>; nut-upsuser at lists.alioth.debian.org Subject: RE: Email

Hi to everybody. Some days ago, I bought an UPS by Forza Power Technologies, model SL-1001. This Forza SL-1001 is line-interactive, has 14,4 A/h charge and is rated at 1000VA. Before, I had a TrippLite Omni 500 (or something like that), a simple contact-closure UPS, and I used nut with the simple genericupsdriver, so I'm new with this type of UPSs. NUT doesn't list Forza as a

Greetings Gentlebeings, I have started deploying a number of NUT instances on Raspberry Pi machines (Raspbian Jessie) across my network. The purpose of these "nutcases" as we refer to them is to monitor the status of the UPSs supporting our network switching infrastructure and notify us of power and battery events via email. No shutdown or other actions are required. Everything is