search for: recv_tri

Displaying 6 results from an estimated 6 matches for "recv_tri".

Did you mean: recv_try
2007 Sep 21
2
TrippLite 1500XL problems, continued.
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')
2007 Mar 04
1
OMNIVS1500XL and FreeBSD
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
2006 Jan 13
1
help with TRIPP LITE SMART550USB
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 -----------------------------------------------------------------------------------------------------------------------------------------------------
2007 May 11
11
tripp lite smart2200RMXL2U error reading protocol
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
2009 Nov 08
1
Tripplite INTERNETX525
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
2011 Oct 03
2
patch: Replace many usleep and some sleep calls with nanosleep
...00 @@ -680,7 +680,8 @@ static int send_cmd(const unsigned char } #if ! defined(__FreeBSD__) - if(!done) { usleep(1000*100); /* TODO: nanosleep */ } + struct timespec delay = {0, 100e6}; + if(!done) nanosleep(&delay, NULL); #endif for(recv_try=0; !done && recv_try < MAX_RECV_TRIES; recv_try++) { Index: b/drivers/apcsmart.h =================================================================== --- a/drivers/apcsmart.h 2011-05-31 13:36:49.000000000 +0300 +++ b/drivers/apcsmart.h 2011-08-17 01:15:16.000000000 +0300 @@ -40,8 +40,10 @@ /* alert characters we care about - OL, OB,...