search for: openups_scratch_buf

.....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 *openups_scale_vbat_fun(double value); */ -static const char *openups_scale_ccharge...

...330, Boston, MA 02111-1307 USA + */ + +#include "usbhid-ups.h" +#include "openups-hid.h" +#include "main.h" /* for getval() */ +#include "usb-common.h" + +#define OPENUPS_HID_VERSION "openUPS HID 0.1" +#define OPENUPS_VENDORID 0x04d8 + +static char openups_scratch_buf[20]; + +/* USB IDs device table */ +static usb_device_id_t openups_usb_device_table[] = { + /* openUPS minimum required firmware 1.4 */ + {USB_DEVICE(OPENUPS_VENDORID, 0xd004), NULL}, + + /* Terminating entry */ + {-1, -1, NULL} +}; + +static const char *openups_charging_fun(double value); +static...

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