similar to: libusb drops connection to my Tripp Lite SMART500T1U

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

<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

Hello Charles, Thanks for the feedback. I will try to answer some of these questions: > 09AE/0001 is essentially a USB-to-serial converter, and is not > compatible with usbhid-ups. (Theoretically, we could have a companion > driver that talks the same protocols over a real RS-232 port, but the > hardware I used to develop the tripplite_usb driver only has a USB > port.) Ah, that

On Jan 6, 2015, at 3:44 PM, Steve Ballantyne <steve.ballantyne at gmail.com> wrote: > Does this snippet of a failure tell you anything? Is there something > I can do to tell the libusb to wait a little longer for the device to > come back? > > 3118.555755 libusb_get_interrupt: Connection timed out > 3118.557454 libusb_get_interrupt() returned 0 instead of 8 while

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

Howdy, I had this working with lots of help for a developer before (Charles Lepple), but after upgrading to a somewhat more current version of FreeBSD the patched-up version stopped working. Seeing as this was more than a few years ago, I thought I'd give a new libusb and NUT a try to see if it might work out of the box. So far, no luck. Some info: FreeBSD 6.3 libusb 0.1.12 NUT 2.4.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 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

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

On Thu, Jun 26, 2014 at 10:20 PM, Steve Ballantyne <steve.ballantyne at gmail.com> wrote: >> However, we don't have all of the 09AE/0001 protocols decoded in the >> tripplite_usb driver. > > I can try to help out on this front? :-) Definitely. >> > 9.783126 Unknown input voltage range: 0x02 >> > 9.783308 Unknown number of switchable

On Tue, Jan 6, 2015 at 9:46 PM, Charles Lepple <clepple at gmail.com> wrote: > However, for the notifications, you could use "upssched" to only notify you if the UPS is disconnected for longer than the usual reconnection time. > Hello Charles, For my purposes, I will take an even easier route to resolution ... I will just comment this line out of my upsmon.conf file.

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

On Thu, Jan 8, 2015 at 11:37 PM, Charles Lepple <clepple at gmail.com> wrote: > Although this tends to happen more with x86 systems and/or USB3, you might want to see if the disconnects are less frequent with a shorter or higher-quality USB cable. The more I look into this ... the more I think that it's exclusively Tripp-Lite weirdness! There are some things that I explored as far

On Jan 7, 2015, at 12:49 PM, Steve Ballantyne <steve.ballantyne at gmail.com> wrote: > I would like to get to the root of the problem though. I may tweak > the code a bit and see if I can get better results. Although you are > right about the broken pipe. If the device is "unplugging" ... not > much you can do to fix that other than to just ignore it. Although this

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

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

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

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