search for: smart500t1u

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

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

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.

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

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