Nut upsdev - Jan 2010 - Tripplite_usb

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
a way to disable it once enabled. From my communication with Tripp Lite,
it doesn't seem that the SMARTPRO 3003 protocol officially supports
Watchdog. I made some modification to tripplite_usb.c. This modified
code checks which protocol the UPS is using and then resets the watchdog
if it is not SMARTPRO protocol.

 

=====================================================================
Tripplite_usb.c

977,987d977

<             /* Reset watchdog: */

<             ret = send_cmd(w_msg, sizeof(w_msg), w_value,
sizeof(w_value)-1);

<             if(ret <= 0) {

<                             if(ret == -EPIPE) {

<                                             fatalx(EXIT_FAILURE,
"Could not reset watchdog. Please check and"

<                                                             "see if
usbhid-ups(8) works with this UPS.");

<                             } else {

<                                             upslogx(3, "Could not
reset watchdog. Please send model "

<
"information to nut-upsdev mailing list");

<                             }

<             }

990d979

< 

1005a995,1010
>             /* Reset watchdog: */
>             /* Watchdog not supported on TRIPP_LITE_SMARTPRO models */
>             if(tl_model != TRIPP_LITE_SMARTPRO ) {
>                             ret = send_cmd(w_msg, sizeof(w_msg),
w_value, sizeof(w_value)-1);
>                             if(ret <= 0) {
>                                             if(ret == -EPIPE) {
>
fatalx(EXIT_FAILURE, "Could not reset watchdog. Please check and"
>
"see if usbhid-ups(8) works with this UPS.");
>                                             } else {
>                                                             upslogx(3,
"Could not reset watchdog. Please send model "
>
"information to nut-upsdev mailing list");
>                                             }
>                             }
>             }
==========================================================================
 

I have had problems with Sun's libusb, so my issue might be with that.
But I am fairly confident that the SMARTPRO doesn't have a watchdog.
Does anyone have a Tripplite UPS with the SMARTPRO protocol that can
test this?

 

Chase Wallis

519 SMXS / MXDEA

Air Force Civilian

Phone: (801) 586 5600

Address: 6137 Wardleigh Road, Bldg. 1515 Rm 178, Hill AFB UT, 84056-5843

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.alioth.debian.org/pipermail/nut-upsdev/attachments/20100112/0ec721eb/attachment-0001.htm>

On Tue, Jan 12, 2010 at 3:13 PM, Wallis, Chase Civ USAF AFMC 519
SMXS/MXDEA <Chase.Wallis at hill.af.mil> wrote:
> 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 a way to
> disable it once enabled. From my communication with Tripp Lite, it doesn?t
> seem that the SMARTPRO 3003 protocol officially supports Watchdog. I made
> some modification to tripplite_usb.c. This modified code checks which
> protocol the UPS is using and then resets the watchdog if it is not
SMARTPRO
> protocol.
I have no problems with the patch - that watchdog code was added
before someone pointed me to another document which mentioned the "get
protocol" command.

Added as r2242 (I had to apply the patch manually, but it looks the same).

Thanks for pointing this out,

-- 
- Charles Lepple