search for: i_in

Displaying 2 results from an estimated 2 matches for "i_in".

Did you mean: hi_in
2018 Feb 04
0
[PATCH 3/3] OpenUPS: fix current calculations
...l line input current is + * determined from the charger power plus the current fed to the LTC3780 + * buck/boost. + */ +static const char *openups_scale_input_current_fun(double value) { - snprintf(openups_scratch_buf, sizeof(openups_scratch_buf), "%.3f", value * ccharge_scale); + double i_in; + + if (on_input && v_in != 0) + i_in = (v_bat * value * ccharge_scale) / (v_in * .9) + i_ltc; + else + i_in = 0; + + snprintf(openups_scratch_buf, sizeof(openups_scratch_buf), "%.3f", i_in); return openups_scratch_buf; } -static const char *openups_scale_cdischarge_fun(do...
2018 Feb 04
5
[PATCH 0/3] OpenUPS updates
Hi, I've been checking out NUT with an OpenUPS board over the last couple of weekends, and have noticed that it doesn't seem to report sensible values. This lead me to investigate usbhid-ups and delve into various issues. As mentioned in a github issue, one of the problems is with the report descriptor - dumping this from the usbhid-ups debug output and picking through it reveals that