search for: v_interval

...bv = hex2d(d_value+3, 2) * battery_voltage_nominal / 120.0 ; - + // bv is 48V nominal rather than 12V + dstate_setinfo("battery.voltage", "%.2f", bv); + if(tl_model == TRIPP_LITE_SMARTPRO) { + if (bv / 4 >= V_interval[1]) + bp = 100; + else if (bv / 4 <= V_interval[0]) + bp = 10; + else + bp = (int)(100*sqrt((bv / 4 - V_interval[0]) +...

...o relative to a 12V battery. > - > + // bv is 48V nominal rather than 12V > + > dstate_setinfo("battery.voltage", "%.2f", bv); > > + if(tl_model == TRIPP_LITE_SMARTPRO) { > + if (bv / 4 >= V_interval[1]) > + bp = 100; > + else if (bv / 4 <= V_interval[0]) > + bp = 10; > + else > + bp = (int)(100*sqrt((bv / 4 - V_interval[0]) > +...

...> > + // bv is 48V nominal rather than 12V > > + > > dstate_setinfo("battery.voltage", "%.2f", bv); > > > > + if(tl_model == TRIPP_LITE_SMARTPRO) { > > + if (bv / 4 >= V_interval[1]) > > + bp = 100; > > + else if (bv / 4 <= V_interval[0]) > > + bp = 10; > > + else > > + bp = (int)(100*sqrt((bv / 4 - V_int...

...Sorry, I wasn't clear. I meant to say that the voltage value read from the UPS is a voltage scaled to match a single 12V battery, and that there is a multiplier in the "V" response which determines the battery_voltage_nominal value. See attached. Still doesn't have the writable V_interval values, but I probably won't have time to test that until later. Don't worry about the battery physical properties for now - the problem there is that we don't have enough information from the UPS to do a proper calculation. With the V_interval[] settings, you can tweak the new state-o...

Hello, At 09:24 -0400 on 2014-5-23 Charles Lepple wrote: > > See attached. Still doesn't have the writable V_interval values, > but I probably won't have time to test that until later. Thank you for the patch. > Don't worry about the battery physical properties for now - the > problem there is that we don't have enough information from the UPS > to do a proper calculation. With the V_...

On May 15, 2014, at 9:39 PM, Stefan Bruda wrote: > What bugs be though is that I cannot seem to be able to read the > remaining run time on battery. The battery charge is also widely > inaccurate (it drops to zero really fast and stays there). I read > somewhere that the usb.debug numbers may hold the key to this (at > least to the running time that is), but I don't know what

On May 24, 2014, at 5:49 PM, Stefan Bruda wrote: >> Don't worry about the battery physical properties for now - the >> problem there is that we don't have enough information from the UPS >> to do a proper calculation. With the V_interval[] settings, you 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. > > Yes, the V_interval[] being exposed is a very good idea and does seem > the only sensible worka...

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:

...ring software. - * - * The discharge curve should be the same for any given battery chemistry, - * so it should only be necessary to specify the minimum and maximum - * voltages likely to be seen in operation. - */ - -/* Interval notation for Q% = 10% <= [minV, maxV] <= 100% */ -static float V_interval[2] = {MIN_VOLT, MAX_VOLT}; - /* Time in seconds to delay before shutting down. */ static unsigned int offdelay = DEFAULT_OFFDELAY; static unsigned int startdelay = DEFAULT_STARTDELAY; @@ -143,9 +119,15 @@ static unsigned int bootdelay = DEFAULT_ static int hex2d(char *start, unsigned int len)...

...le wrote: > > On May 24, 2014, at 5:49 PM, Stefan Bruda wrote: > > >> Don't worry about the battery physical properties for now - the > >> problem there is that we don't have enough information from the UPS > >> to do a proper calculation. With the V_interval[] settings, you 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. > > > > Yes, the V_interval[] being exposed is a very good idea and does see...

...t; >> On May 24, 2014, at 5:49 PM, Stefan Bruda wrote: >> >>>> Don't worry about the battery physical properties for now - the >>>> problem there is that we don't have enough information from the UPS >>>> to do a proper calculation. With the V_interval[] settings, you 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. >>> >>> Yes, the V_interval[] being exposed is a very good idea an...