similar to: Tripplite UPS

On Wed, Apr 1, 2009 at 10:54 PM, Lelsie Rhorer <lrhorer at satx.rr.com> wrote: > > Gentlemen, > > I am running a Tripp Lite OMNISV1500XL under NUT using the > tripplite_usb driver on a Debian "Lenny" Linux system. The platform is an > AMD Athlon 64 x 2 processor running kernel 2.6.26. The driver is up and > running, but there are several issues.

For my Smart 2200, a charged battery string is anywhere between 25.6 and 26.8 volts. I'm seeing nut report 13.0 volts, which seems suspicious. Even if the UPS were reporting half of the actual battery voltage to keep protocol compatibility with models having a 12V battery system, the value of exactly 13.0 seems unlikely. According to the page at

I'm having problems creating a UPS connection to my Tripp Lite UPS System: Ubuntu 8.04.2 Nut 2.4.1 freshly compiled from source. When I do upsdrvctl start everything appears to work and I get :Detected a UPS: TRIPP LITE/TRIPP LITE UPS Using OMNIVS 2001 protocol (2001) Unit ID not retrieved (not available on all models) Attached to Tripp Lite UPS But

Gentlemen, ??????????? I am running a Tripp Lite OMNISV1500XL under NUT using the tripplite_usb driver on a Debian "Lenny" Linux system.? The platform is an AMD Athlon 64 x 2 processor running kernel 2.6.26.? The driver is up and running, but there are several issues. ??????????? First, the system drops communications with the UPS regularly - typically 2 or three times an hour.?

So a month or more ago, I posted about continual disconnect messages from this UPS (roughly 2/hour), using nut 2.2.0 on debian etch. Now, I've finally gotten around to running tripplite_usb in debug mode, and these are the results: ... send_cmd(msg_len=2, type='L') send_cmd(msg_len=2, type='S') send_cmd(msg_len=2, type='B') send_cmd(msg_len=2, type='L')

Hello, I've got Tripplite Smart Int 1000 UPS with lan4.1 serial interface. Quite sympathetic UPS, I must say from first glance. I have made a proper serial cable (btw i hate all those constructor's decisions to make distinct serial wiring for each and every UPS type from each and every manufacturer!) I use [tripplite] driver for NUT and I can use upsc to get report from UPS, but

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

I have added preliminary support for the TrippLite protocol number 2001 into tripplite_usb.c. The attached file is supplied as a patch against today's SVN. This patch adds support for TrippLite SMART550USB and some Omni models. Tested are On Line, On Battery, Battery Good, and Battery Bad indication. Everything else seems to work, but this UPS is attached to a critical system, and I can

I have been having a few issues recently. I'm running Nut 2.4.3 on Solaris 10 (10/09) using a TrippLite SMART700DVa UPS. Everything seems to be working fine except for some random issues. During a power cycle (UPS online to offline to online) NUT will occasionally get disconnected from the UPS. A call to it using upsc results in "Error: Data stale". And running dmesg has the

Hello, I have a Tripplite SMART1500 UPS, and I'm having a little luck with the tripplite_usb driver. Only a LITTLE though. It's working better than any of the other drivers I've tried, but I'm not getting a status from it. Here's the output of upsc: battery.voltage: 0.00 battery.voltage.nominal: 36 driver.name: tripplite_usb driver.parameter.port: /dev/hiddev0

Hello, I wanted to see if there's any chance that NUT will support a few new TrippLite UPSes that we just bought: Sep 9 01:42:25 miko /kernel: uhid0: TRIPP LITE TRIPP LITE OMNIVS1500XL, rev 1.1 I grabbed the devel sources via cvs, but am having trouble building it when I enable the "newhidups" driver: gmake[1]: Leaving directory `/usr/local/src/nut/common' drivers/

The Compatibility page lists the OMNIVS1000 as supported, but the tripplite_usb driver doesn't seem to recognize my UPS. Below is the debug dump from attempting to load the driver. I am using the nut package from Debian: 2.2.1-2.1 and I was wondering if this was a known issue? maroon:/lib/nut# /lib/nut/tripplite_usb -DDDDD -a usbups Network UPS Tools - Tripp Lite OMNIVS and SMARTPRO driver

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

Hi, I'm running the latest version of NUT and with the above UPS and I keep getting the following error: "tripplite_usb[3308]: Error reading B value: Device detached? (error 0: could not claim interface 0: Device or resource busy)" The device keeps disconnecting and re-connecting until fails. I've tried to see if others are getting this - but I could not locate a

I am running Debian Etch, with the nut 2.0.4 packages, and I get a segmentation fault from tripplite_usb. # /lib/nut/tripplite_usb -u root -DDDDD auto Network UPS Tools - Tripp Lite OMNIVS and SMARTPRO driver 0.6 (2.0.4) Warning: This is an experimental driver. Some features may not function correctly. debug level is '5' Checking device (09AE/0001) (002/004) - VendorID: 09ae -

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

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

The tripplite driver was developed on a machine with a reliable serial connection, and inherited the assumption that the serial line connection would not drop, reorder, or fail character read and writes. This patch adds significantly improved failure mode handling and also does basic checks of data validity. There's also a few minor cleanups/beautification. I've tested this code on my

Hello, I am try to get my "new" UPS running with NUT on my OpenMediaVault device but only receive error meassages on several configurations I try. Your support is really appreciated for getting it solved. Best Regards, Olaf *lsusb* Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 001: ID

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