search for: v_in

Displaying 3 results from an estimated 3 matches for "v_in".

Did you mean: f_in
2018 Feb 04
0
[PATCH 3/3] OpenUPS: fix current calculations
...it a/drivers/openups-hid.c b/drivers/openups-hid.c index 6bd00b6..30e9f26 100644 --- a/drivers/openups-hid.c +++ b/drivers/openups-hid.c @@ -42,6 +42,8 @@ static double vin_scale = 1; static double vout_scale= 1; static double ccharge_scale = 1; static double cdischarge_scale = 1; +static double v_in, v_bat, v_out, i_ltc; +static int on_input; static char openups_scratch_buf[20]; @@ -129,9 +131,9 @@ static const char *openups_off_fun(double value); static const char *openups_scale_vin_fun(double value); static const char *openups_scale_vout_fun(double value); -/* static const char *ope...
2010 Oct 13
1
[LLVMdev] EXC_BAD_ACCESS: invalid MemoryBuffer from ContentCache::getBuffer
I'm using the latest llvm/clang 2.8 releases and am getting EXC_BAD_ACCESS crashes in ContentCache::getBuffer. This happens when I'm printing out errors from a compilation run and iterating over TextDiagnosticBuffer returned errors. When checking the errors, I construct a FullSourceLoc and do: int LineNum = SourceLoc.getInstantiationLineNumber(); int ColNum =
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