search for: tripp_lite_smartpro

...--- --- nut.20061011/drivers/tripplite_usb.c 2006-10-11 14:51:04.000000000 -0500 +++ nut.20061004/drivers/tripplite_usb.c 2006-10-04 20:41:57.000000000 -0500 @@ -243,7 +243,8 @@ #include <math.h> #include <ctype.h> -static enum tl_model_t { TRIPP_LITE_UNKNOWN = 0, TRIPP_LITE_OMNIVS, TRIPP_LITE_SMARTPRO } +static enum tl_model_t { TRIPP_LITE_UNKNOWN = 0, TRIPP_LITE_OMNIVS, TRIPP_LITE_OMNIVS2, +TRIPP_LITE_SMARTPRO} tl_model = TRIPP_LITE_UNKNOWN; /*!@brief If a character is not printable, return a dot. */ @@ -387,6 +388,9 @@ case 0x1001: upslogx(3, "Using OMNIVS protocol (%x)",...

...> Here's where the battery.charge variable is calculated: > > https://github.com/networkupstools/nut/blob/master/drivers/tripplite_usb.c#L1099 > > battery_charge = (unsigned)(s_value[5]); > > (In that file, the 3003 protocol is denoted by "tl_model == TRIPP_LITE_SMARTPRO".) > > Due to the command prefix characters in the protocol, the > ups.debug.S hex values are actually indexed from 1 as follows: > > 1 2 3 4 5 6 7 > > ups.debug.S: 31 30 30 00 28 30 0d '100..0.' > > Hence, your s_value[5] yiel...

...longer find that piece of information...). Here's where the battery.charge variable is calculated: https://github.com/networkupstools/nut/blob/master/drivers/tripplite_usb.c#L1099 battery_charge = (unsigned)(s_value[5]); (In that file, the 3003 protocol is denoted by "tl_model == TRIPP_LITE_SMARTPRO".) Due to the command prefix characters in the protocol, the ups.debug.S hex values are actually indexed from 1 as follows: 1 2 3 4 5 6 7 ups.debug.S: 31 30 30 00 28 30 0d '100..0.' Hence, your s_value[5] yields 0x28 == 40%. That said, a lot of information was...

...ne: > > ------ begin patch ------ > --- tripplite_usb.c.original 2014-05-19 16:20:58.251634449 -0400 > +++ tripplite_usb.c 2014-05-19 16:53:54.806609602 -0400 > @@ -1098,8 +1098,8 @@ > > - /* This may not be right... */ > - if(tl_model == TRIPP_LITE_SMARTPRO) { > - battery_charge = (unsigned)(s_value[5]); > - dstate_setinfo("battery.charge", "%u", battery_charge); > - } > } > > @@ -1167,9 +1167,22 @@ > hex2d(d_value...

Hello, I own an older Tripp Lite SMART3000RM2U (protocol 3003). It does not work with usbhid-ups but it mostly works with the tripplite_usb driver (nut 2.7.1, the latest in the Gentoo tree), in the sense that the status (on line, on battery, etc.) is detected correctly, the machine is shut down on critical battery, and I can even get some information from the UPS. This is how it all looks:

...pslogx(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) { > fata...

...---- > > --- tripplite_usb.c.original 2014-05-19 16:20:58.251634449 -0400 > > +++ tripplite_usb.c 2014-05-19 16:53:54.806609602 -0400 > > @@ -1098,8 +1098,8 @@ > > > > - /* This may not be right... */ > > - if(tl_model == TRIPP_LITE_SMARTPRO) { > > - battery_charge = (unsigned)(s_value[5]); > > - dstate_setinfo("battery.charge", "%u", battery_charge); > > - } > > } > > > > @@ -1167,9 +1167,22 @@ > >...

...can tweak the new state-of-charge calculation to match what you see via upsc when the battery is fully charged, so that's better than nothing. > It should apply, but somebody more familiar with the thing should > verify the code. For instance is this only applicable to tl_model == > TRIPP_LITE_SMARTPRO (as in my code)? How about tl_model == > TRIPP_LITE_SMART_0004? This one supposedly also responds to a "D" > message with (again supposedly) the same kind of response, but maybe > s_value[5] is better in this case. In my patch I simply did not care > about it and I would no...