similar to: tripplite smart2000rmxl2u product id 3014

I'm read through the archives trying to figure out how to get a Tripplite SmartPro SLT 1500 configured with NUT using the USB interface (it also has a serial interface but I'd rather not). The thread which this link belonged to seemed most instructive: http://lists.alioth.debian.org/pipermail/nut-upsdev/2007-January/001656.html and I followed it as best I could. I'm running a

Hi Raphael, btw, are you 2 bugs today a simple coincidence with my linkedIn invitation yesterday? ;-) 2008/10/4 Raphael Geissert <atomo64 at gmail.com>: > Package: nut > Version: 2.2.2-8 > Severity: wishlist > Tags: patch > > Attached is a patch adding "support" for tripplite's avr750u UPS. > Issues: > * productid still needs to be specified in

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

Please ignore the previous message as I sent it before it was complete. Hello, I have a Tripplite SMART2200VS that isn't being shut down when the nut master asks it to. My initial test was simply upsmon -c fsd which did cause the system to shut down, however the UPS remained on and providing power to its loads. Looking in the logs (daemon and syslog) it was not clear to me that NUT was

Hello, I have a Tripplite SMART2200VS that isn't being shut down when the nut master asks it to. My initial test was simply upsmon -c fsd which caused the system to shut down, but the UPS remained on and providing power to its loads. Looking in the logs (daemon and syslog) it was not clear to me that NUT was telling the UPS to shut down (I was expecting to see "Shutting down the UPS

I'm trying to get a SMART2200CRMXL to work with nut, using a USB cable. tripplite_usb -a upsname returns: Network UPS Tools - Tripp Lite OMNIVS and SMARTPRO driver 0.11.1 (2.2.2) Warning: This is an experimental driver. Some features may not function correctly. No matching USB/HID UPS found My system info: CentOS 5.5 nut installed from repo upsd version 2.2.2 TrippLite SMART2200CRMXL

Charles, maybe we are getting closer :-) > The tripplite_serial_protocol branch has some debug statements that will show up if you run "sudo drivers/tripplite -D -a name-of-ups" from the nut directory. Network UPS Tools - Tripp-Lite SmartUPS driver 0.91 (2.7.4-432-gafd90f5a) ?? 0.000000??? [D1] debug level is '1' ?? 0.177766??? [D1] W value = 0x86 ?? 0.177782??? [D1] L

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

Hello, Somewhat off-topic, but seeking some input from other tech folk on this list. I have a Tripp-Lite SMART 2200 (a white tower that looks similar to, but predates the black SMART2200NET) that just failed its monthly battery test so I bought new batteries and replaced the old ones. Sadly once put back together, plugged in and enabled it did not power up--no lights, sounds, smoke, etc. I took

Hey all, I am trying to use NUT for a Tripplite Smart1200 LCD on a fresh copy of Debian 6.0.2.1. I installed NUT version 2.4.3 and I have pored through pages and pages of other posts, but for the life of me I can not get it to recognize the Tripplite. I know its an 09ae:2009 device and I've tried to add a rule in /lib/udev/rules.d/52-nut-usbups.rules as according to some posts, but to no

> > > 2.117586 send_cmd(msg_len=2, type='G') > > 3.219418 libusb_get_interrupt: Connection timed out > > 3.219474 libusb_get_interrupt() returned 0 instead of 8 while > sending 3a 47 b8 0d 00 00 00 00 '.G......' > > 4.219593 libusb_get_interrupt: Connection timed out > > 4.219661 libusb_get_interrupt() returned

Hi list- I'm having problems with TrippLite SMX1500LCD not being detected by NUT under FreeBSD 6.3-RC2. NUT 2.2.1 was installed from ports with the following options: WITH_USB=true WITH_SNMP=true WITHOUT_IPV6=true WITH_LIBUPSCLIENT=true WITH_CGI=true I use USB cable shipped with TrippLite and 'usbdevs -v' shows the following: ... Controller /dev/usb2: addr 1: full speed, self

Hello list- Anyone with Tripplite SMX1500XLRT2U (http://www.tripplite.com/EN/products/model.cfm?txtModelID=2687) successfully integrated with NUT through serial port? I'm trying to connect to SMX1500XLRT2U using serial cable shipped with UPS under FreeBSD 6.3-STABLE and NUT 2.2.2 installed from ports. Unfortunately, it looks like it couldn't be recognized. %dmesg | grep sio sio0:

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 -

I'm working on a gentoo server with Nut 2.0.5-r1 and libusb-0.1.12. I originally tried the hidups driver which seemed to work, but produced a large amount of unhandled events. Then I tried the newhidups which told me my ups wasn't supported. When I try using tripplite_usb -u root -DDDD /proc/bus/usb/002/002 I get that there isn't a match. But when I try using tripplite_usb -DDDD

Leslie, This message is most appropriate for the NUT user list. I kept Rik Faith's and Nicholas Kain's copyright information because the tripplite_usb driver borrows heavily from the tripplite (serial) driver, but they are not responsible for the mess that I made in the USB driver. See below. On Dec 28, 2008, at 5:28 PM, Lelsie Rhorer wrote: > Gentlemen, > >

OpenBSD 6.1/amd64 nut-2.7.4p0 (from OpenBSD package) UPS: Tripp-Lite OMNI1500LCDT I cannot get the driver for the UPS to load without error. Here are the commands, with the output, and the config files: ======================================================= # upsdrvctl start Network UPS Tools - UPS driver controller 2.7.4 Network UPS Tools - Generic HID driver 0.41 (2.7.4) USB communication

I've tried looking for documentation on configuring NUT for Ubuntu 12.04 over SNMP with a Tripplite UPS, but there isn't a lot of SNMP configurations tutorials out there from what I've seen. I haven't been able to get automatic shutdown to work. The driver I've been using is usbhid-ups which is generic for Tripplite, but I've reviewed several other UPS driver names and some

Hello list! I can't seem to get this running via RS232 monitoring; I've been told that NUT won't support serial connections, and find this hard to verify. Does anyone else have this running on the SU10KRT3U via RS232? If so, what driver did you use? I'm getting no satisfaction from the "tripplite" driver; upon upsdrvctl start, I get "Failed to find UPS - giving

Hi Charles and Jonathan, I am going through my over 300 unread NUT messages, and I just discovered this one from mid-December. At the time, I was trying to clean up the tripplite subdriver of newhidups, but never got the information I needed. I have enabled this driver now, but it is marked "experimental". The driver is still incomplete, in the sense that there are many unmapped device