-
-
Notifications
You must be signed in to change notification settings - Fork 401
Closed
Labels
CyberPower (CPS)Incorrect or missing readingsOn some devices driver-reported values are systemically off (e.g. x10, x0.1, const+Value, etc.)On some devices driver-reported values are systemically off (e.g. x10, x0.1, const+Value, etc.)USBUSB-HID encoding/LogMin/LogMaxIssues and solutions (PRs) specifically about incorrect values in bitstreamIssues and solutions (PRs) specifically about incorrect values in bitstreamfeature
Milestone
Description
Observed in issue #337 (comment)
and on nut-upsuser.
Report ID 18 seems to be inheriting Logical Minimum/Logical Maximum from Report ID 16:
Collection(Physical)
Report ID(16)
Usage(LowVoltageTransfer)
Logical Minimum(97)
Logical Maximum(103)
Feature(Data,Variable,Absolute)
Usage(LowVoltageTransfer)
Input(Constant,Variable,Absolute)
Usage(HighVoltageTransfer)
Logical Minimum(136)
Logical Maximum(142)
Feature(Data,Variable,Absolute)
Usage(HighVoltageTransfer)
Input(Constant,Variable,Absolute)
Report ID(18)
Usage(Voltage)
Feature(Constant,Variable,Absolute)
Report Size(8)
Logical Minimum(0)
Logical Maximum(255)
Unit(SI Linear: ...)
Unit Exponent(0)
I'm pretty sure this is not a bug in the NUT HID parser, but feel free to correct me. (There are other places in the CPS HID Report Descriptor that seem to mix up the locations of the parser tokens relative to Input/Output/Feature.)
ravron
Metadata
Metadata
Assignees
Labels
CyberPower (CPS)Incorrect or missing readingsOn some devices driver-reported values are systemically off (e.g. x10, x0.1, const+Value, etc.)On some devices driver-reported values are systemically off (e.g. x10, x0.1, const+Value, etc.)USBUSB-HID encoding/LogMin/LogMaxIssues and solutions (PRs) specifically about incorrect values in bitstreamIssues and solutions (PRs) specifically about incorrect values in bitstreamfeature