similar to: Adding tripplite smart1500 UPS to tripplite_usb

Hello, We have a Tripplite SMART1500RMXL2U and nut-2.2.0-6.el5 installed on Centos 5.3. I've been unsuccessful on getting upsmon to work. usdrvctl seems to start despite some warnings/errors: # upsdrvctl start smart1500 Network UPS Tools - UPS driver controller 2.2.0- Network UPS Tools - Tripp Lite OMNIVS and SMARTPRO driver 0.11.1 (2.2.0-) Warning: This is an experimental driver. Some

Hello, Does anyone know the settings to get this UPS talking to nut? I'm trying to get it working over the serial port, and I've tried using genericups type 5. When I do this, the driver seems to initialize, but then upsc shows the status to be OB LB. When I unplugged the UPS, there was no change in the status. I noticed on the Tripp Lite web site that this uses a different cable. It is

I have a Tripp Lite SMART1500 RMXL2U UPS and I'd love to be able to access it via USB. I found that the latest NUT sources in CVS has a driver that looks like it might work. Any chance that driver would work the my UPS? I tried running it and it's not working: failed to detach kernel driver from USB device... trying again to claim USB device... failed to claim USB device, trying 1

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

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 May 25, 2016, at 9:42 PM, Larry Fahnoe <fahnoe at fahnoetech.com> wrote: > > So the current NUT can't cause this UPS to power off the load while it is on line power, correct? I will update the nut-server init script with the sleep/reboot logic per FAQ #51. Correct. > My larger concern is testing the UPS to ensure it shuts down correctly and comes back up correctly as

On May 25, 2016, at 3:43 PM, Larry Fahnoe wrote: > > 0.016075 Initiating UPS shutdown > 0.016117 soft_shutdown(offdelay=64): N > 0.016137 send_cmd(msg_len=4, type='N') The delay command ('N') was sent successfully, so the UPS is receiving commands. > 2.117586 send_cmd(msg_len=2, type='G') > 3.219418

Hi, I'm using nut 2.2.1 on Ubuntu Hardy. Everything is fine, upsc works, upsmon is working. Then, after twenty minutes or an hour or maybe even longer, it all breaks down and I see these messages in the log: May 22 13:39:04 logicserver upsmon[28319]: Poll UPS [tripplite at localhost] failed - Driver not connected Restarting upsd fixes the problem temporarily. Any ideas? Thanks, Forest

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

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

On Dec 16, 2008, at 10:36 AM, Bradley Feldman wrote: > Looking at the syslog, I noticed that the tripplite_usb driver > segfaulted > once it switched to battery (see below). I'm not sure whether you > still > maintain the driver or if I need to file a bug somewhere. I still have the unit in question; however, since the segfault happened inside libc, I won't be able

He everyone, I have a Tripplite SMART700DVa using the tripplite_usb from NUT 2.5 (rev 2217) driver running in Solaris 10x86. My driver hangs when trying to connect. Once the driver sends the watchdog command ("W\0"), it can no longer receive any signals and eventually exits. The UPS responds to other watchdog commands ("W5" for example), but there doesn't seem to be

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

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

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

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