search for: tripp_lite_smart_0004

.....). > > Not much has changed between 2.7.1 and 2.7.2+git, so it might not > be that bad. 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 not know whether to care or not since I don't have access to this kind of UPS....

...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 not know whether to care or not since I don't > have access to...

On May 19, 2014, at 7:12 PM, Stefan Bruda wrote: > Hello, > > First of all thank you so much for the information. No problem, glad it is useful. > [...] > Therefore as far as my UPS is concerned s_value[5] is wildly > incorrect. So it turns out that the RM15002U also does not report anything useful for s_value[5]:

Hello, First of all thank you so much for the information. At 22:43 -0400 on 2014-5-15 Charles Lepple wrote: > > 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