search for: hiddata

...r); > + HIDFreeRegexMatcher(regex_matcher); > } > > /********************************************************************** > @@ -1004,6 +1011,23 @@ > switch (mode) > { > /* Device capabilities enumeration */ > + case HU_WALKMODE_RESET: > + if (item->hiddata == NULL) > + continue; > + > + /* Reset the NUT-to-HID translation */ > + item->hiddata = NULL; > + > + /* If this was a command, remove it... */ > + if (item->hidflags & HU_TYPE_CMD) { > + dstate_delcmd(item->info_type); > + continue; > +...

...igVoltage of 0x48 (72 V) seem reasonable, but somewhere else in the HID Report Descriptor, the voltages are getting scaled to a "Logical" range of 0-1. Can you temporarily comment out line 383 in drivers/libhid.c and rebuild? It currently looks like this: *Value = logical_to_physical(hiddata, hValue); If that works, we can add a flag to ignore logical-to-physical mappings. -- Charles Lepple clepple at gmail

2014-11-07 0:16 GMT-03:00 Charles Lepple <clepple at gmail.com>: > On Nov 6, 2014, at 5:56 PM, Marcelo Fernandez <marcelo.fidel.fernandez at gmail.com> wrote: > >> battery.voltage: 10000000. >> battery.voltage.nominal: 0.0 > > Well, these are certainly interesting values ;-) > > I suspect the correction for earlier units has failed. Can you please start

...(72 V) seem reasonable, but somewhere else in the HID Report Descriptor, the voltages are getting scaled to a "Logical" range of 0-1. > > Can you temporarily comment out line 383 in drivers/libhid.c and rebuild? It currently looks like this: > > *Value = logical_to_physical(hiddata, hValue); > > If that works, we can add a flag to ignore logical-to-physical mappings. > Hello Charles, Now it seems I'm getting the same values but formatted differently in the output: root at nut:/usr/local/ups/bin# ./upsc liebert battery.charge: 100 battery.charge.low: 20 battery...