similar to: Problem OMNIVS1000 USB uses tripplite_usb or usbhid-ups

I purchased a TrippLite ECO550UPS from Amazon a few days ago thinking I was going to use it for my Windows Media Center HTPC. I've since changed my mind and decided to use Mythbuntu but it I can't get my UPS working with nut. I've tried all of the tripplite drivers and the usbhid-ups driver. The tripplite_usb and usbhid_ups output is listed below. The tripplite and tripplitesu 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

Hey Charles, Many months ago you assisted me in making some code changes to get my Tripp Lite up and running. Thank you for that. Those changes you committed to the repository work very well. I just built a new image for a Raspberry Pi running the latest Raspbian OS and the latest nut-master. I have everything working ... except I seem to be losing my device periodically. So if I enable my

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

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

<nut-upsuser at lists.alioth.debian.org> I am doing my best to avoid have to spend $280 for a network monitoring card to put into a $190 UPS just to have some good remote monitoring capabilities. Rather, I would like to monitor my many 1U Tripp Lite's on my network using a Raspberry Pi running Raspian and using NUT. However, I cannot seem to get it working. And I while the hardware

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

Hello, I have a TrippLite SMART1500RMXL2U that I'm trying to get running with Nut 2.2.1. Running upsdrvctl start works, upsd works, but upsc has "issues": je-nas:~/src/nut-2.2.1# upsdrvctl start Network UPS Tools - UPS driver controller 2.2.1- Network UPS Tools - Tripp Lite OMNIVS and SMARTPRO driver 0.11 (2.2.1-) Warning: This is an experimental driver. Some features may not

Hi, I recently purchased a Tripp Lite SMART1000RM2U UPS (http://www.tripplite.com/en/products/model.cfm?txtSeriesID=744&txtModelID=2657) and tried to configure the NUT with tripplite_usb driver and encounter the following problems: 1. battery.charge doesn't report correct charge level when the UPS is On Batter. It just reports 0. Even though it will report 100 when on line power. 2. I

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

Good afternoon, I'm trying without much success to monitor a Tripp Lite OMNIVS1500XL using NUT. I checked the compatibility list and saw that this UPS is supported by tripplite_usb. The system is running Debian Stable, but I've downloaded NUT 2.0.3 and compiled from source since the packaged 2.0.1 doesn't include tripplite_usb. I compiled --with-user=nut. My first attempt at

Hi I have a Tripp lite smartusb550 using fedora 3 (2.6.12-1.1381_FC3smp). Managed to establish communication with the ups using the tripplite_usb driver but get the following errors Any help to make it work will be appreciated cheers Julio -----------------------------------------------------------------------------------------------------------------------------------------------------

I'm running FreeBSD 6.2 with Nut 2.0.5 installed from ports... I have a TrippLite OmniVS1500XL plugged in, but I'm having little luck with the tripplite_usb module. I have already built and booted a new kernel with UHID disabled so that libusb can grab /dev/ugen0. At first I was able to get the following out of the driver: # USB_DEBUG=5 /usr/local/libexec/nut/tripplite_usb -u root

I got FreeBSD up and running last night (many thanks to Charles Sprickman for a ton of useful suggestions along the way), and took a look at tripplite_usb on an OMNIVS1000. The tripplite_usb driver basically sends old-school Tripp Lite serial commands to the UPS via HID SetReport packets, and receives responses over the first Interrupt IN pipe. Later UPSes seem to be more deterministic in this

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

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 Charles, I think we are making progress! I grabbed nut using git, and applied your patch without any problems. Getting to the point that I could run a configure on my RPi - was something else. I found this blog post, which was very helpful (for anyone else that may try it): http://atelier-orchard.blogspot.com/2013/11/raspberry-pixf86-video-fbdev.html It's not in English, but you get

Has anyone gotten this model of tripp-lite to work? sudo /usr/local/bin/upsdrvctl -DDDDD -u root start Network UPS Tools - UPS driver controller 2.0.5 Starting UPS: tripplite exec: /usr/local/bin/tripplite_usb -a tripplite Network UPS Tools - Tripp Lite OMNIVS and SMARTPRO driver 0.7 (2.0.5) Warning: This is an experimental driver. Some features may not function correctly. Detected a UPS: TRIPP

Hello all; I am new to this list. Recently we have been getting these cheap new Tripp-Lite "LCD" style UPS'es around here, and I was surprised to find the lack of Linux support. The model name is OMNI650LCD. Anyway, I tried the tripplite_usb driver and got a message instructing me to contact this mailing list. I might try to fix the problem myself, if I was more familiar with the

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