[Nut-upsdev] [Nut-upsuser] Tripplite OMNIVS1500 Woes
jonb88 at gmail.com
Thu Aug 14 03:09:27 UTC 2008
Ok, Thanks for explaining the differences between the USB HID and hiddev -
the hiddev0 device does indeed disappear as you said.
I will do my homework (sort of doing it now too :] ) if the decision of
which UPS to purchase falls into my hands in the future. Thanks for the
I can definitely try to recompile the driver as you said,
I have just a couple questions on how to do this:
Should I be using th latest trunk tripplite_usb.c?
Does changing the,
#define MAX_SEND_TRIES 3
#define MAX_SEND_TRIES 10
and recompiling the driver do the trick? Does the # cause the line to be
I will give this a go on Friday - THANK YOU SO MUCH!
On Wed, Aug 13, 2008 at 10:22 PM, Charles Lepple <clepple at gmail.com> wrote:
> On Aug 13, 2008, at 10:14 AM, Jon Bougher wrote:
> send_cmd(msg_len=2, type='B')
> send_cmd: sending 3a 42 bd 0d 00 00 00 00 '.B......'
> send_cmd: received 53 31 34 30 31 00 30 0d 'S1401.0.' (bad)
> send_cmd: send_try = 3, recv_try = 10
> Error reading B value: Device detached? (error 0: No error)
> What if you increase MAX_SEND_TRIES? Under normal operation, this should
> not slow things down, but increasing it to 5, 10 or 20 might help if the UPS
> is busy and can't respond immediately.
> I think remember where the "error 0" part came from. The USB-to-serial
> converter always returns 8 bytes if it can, but those bytes may be stale
> (see above - we sent the 'B' command, but got the leftover 'S' status
> Arjen had some suggestions about how to rework the reconnection scheme, and
> based on the error above, it's not going to be simple.
> Charles Lepple
> clepple at gmail
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Nut-upsdev