similar to: Tripp-Lite SU2200XLA problem

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

Citeren Arnaud Quette <aquette op alioth.debian.org>: > Modified: trunk/drivers/tripplite-hid.c > ============================================================================== > --- trunk/drivers/tripplite-hid.c (original) > +++ trunk/drivers/tripplite-hid.c Sun Mar 1 19:56:31 2009 > @@ -84,6 +84,8 @@ > > /* HP R/T 2200 INTL (like SMART2200RMXL2U) */ > {

On Tue, Mar 09, 2010 at 07:14:59PM -0500, Charles Lepple wrote: > On Mar 9, 2010, at 5:54 PM, Kelvin Ku wrote: > >> However, if I try to run usbhid-ups as user "nut", I get: >> >> $ sudo -u nut ./usbhid-ups -a usb > [...] >> Whereas if I run it as root: >> >> $ sudo ./usbhid-ups -a usb -u root > > Did you pass "--with-user=nut"

I have a HP T1500 INTL that isn't picked up under 2.4.3. I added the USB device ID to tripplite-hid.c like: /* HP T1500 INTL */ { USB_DEVICE(HP_VENDORID, 0x1f09), battery_scale_1dot0 }, and it seems to work just fine: # upsc UPS1 at localhost battery.charge: 100 battery.charge.low: 10 battery.charge.warning: 30 battery.temperature: 23.9 battery.type: battery.voltage: 40.9

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

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

Good afternoon all, I have a Tripp-Lite SmartOnline SU1500RTXL2ua UPS that I had previously tried to get up and running with NUT earlier this year. Peter Selinger had been working with this, but he had to devote time to more important things, and I did too, so it got pushed to the back burner. I saw in the release announcement of 2.2 that the UPS is now supported and decided I would try once

Hi Matt, first, note that Russell (Kroll) is retired for long. Support request should go to the NUT Users list, which needs subscription. 2010/6/23 matt <matt at mattevans.org> > Experts, > > I have gotten nut to work this evening, with usbhid-ups, and a small > addition to udev, on my new TrippLite SmartOnline model. I am on Ubuntu > 10.04. This is the 2U rackmount 800W

All: I am having a devil of a time getting nut to work on freebsd. Here is what I have done. I am trying to load the drivers, and here is my ups.conf file: [tripplite] driver=trippliteesu port=auto When I dmesg on freebsd 7.1 for my usb device: uhid0: <Tripp Lite TRIPP LITE UPS, class 0/0, rev 1.10/0.00, addr 2> on uhub0 using the usbdevs -v command: Controller /dev/usb0: addr 1:

To all, I attempted to configure the UPS tools for the Tripp-Lite SmartOnline 1500VA 2U rackmount UPS. I followed the instructions from the 'upsdrvctl start' output and posted the diagnostic information below. Is my UPS using an unknown product ID as reported? From the mailing list archive, I have found another posting for the same UPS with device model '09AE/4003', whereas

My UPS has a usb interface with USB-to-Serial chip. But ucycom driver doesn't recognize it. uhid driver does, but it doesn't help me, I need a virtual com port. (output below is without uhid loaded) What can I do to get it working? udi = '/org/freedesktop/Hal/devices/usb_device_665_5161_noserial' freebsd.device_file = '/dev/ugen1' (string) freebsd.driver =

Hi! I'm having problems connecting Ippon Smart power pro 1000 UPS to nut via usb under FreeBSD 7-stable The UPS uses megatec protocol and works fine via RS232 (UPS has RS232 and USB connectors) When I connect USB /dev/uhid0 is created. Tried port=/dev/uhid0 - doesn't work. Kernel rebuild w/o option uhid. On connect I get 2 devices /dev/ugen1, /dev/ugen1.1. Tried both of them.

[was: svn commit r915 - in trunk: . drivers] Hi Kjell, sorry, I'm still much late in emptying my mail stack... 2007/5/25, Kjell Claesson <kjell.claesson at epost.tidanet.se>: > Den Friday 25 May 2007 08.52.20 skrev Arnaud Quette: > > > > I would be interested in some more info: > > - lshal -u <your device's UDI> > > the UDI can be obtained for ex.

Good afternoon, I am trying to communicate with a new Tripp-Lite UPS via usb and having little luck. After more than a week on this I've decided to ask for help. I am very inexperienced at posting information to message boards, so hopefully I'm doing this right. I assume this is the correct place to post this message. I will start with the equipment I have. I am using Debian Sarge

When running 'sudo upsmon -c fsd' UPS turns off then back on after a delay as expected. But when power is disconnected and the command is ran, the UPS turns off but still turns back on again. Changing 'ondelay' to -1 or 0 does not change the behavior. How can I get the UPS load to stay turned off if there is no power? Or am I misunderstanding how to test this functionality?

I'm trying to set up nut-2.6 with a SMX1000 ups unit from APC on a CentOS 4.8 server. It's connected via USB, and Linux has detected it as a HID device. Nut was built from source code. T: Bus=03 Lev=01 Prnt=01 Port=01 Cnt=01 Dev#= 21 Spd=12 MxCh= 0 D: Ver= 2.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS=64 #Cfgs= 1 P: Vendor=051d ProdID=0003 Rev= 1.06 S: Manufacturer=American Power

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

Hi all, Here's a brief history of my adventure: I purchased a CyberPower 685 AVR and decided to connect it through USB to my Gentoo linux machine running kernel 2.6.22. While the device was detected properly and added to /dev, it was added with the wrong permissions (gid was set to 'usb' instead of 'nut', as it was expected to be according to the rules under

Greetings everyone, Firstly, sorry for the huge length of this message. The support page said send debug traces, and so debug traces shall be sent. OS name and version - Arch Linux - updated today. exact NUT version - 2.7.4 (Network UPS Tools - Generic HID driver 0.41 (2.7.4) USB communication driver 0.33) NUT installation method - Arch User Repository build script updated to use latest NUT